11 The Ultimate Upgrade Nicholas Garcia Bell Helicopter Textron.

Slides:



Advertisements
Similar presentations
MLAN Maguire Local Area Network Version 2.0, May 1998.
Advertisements

Microsoft ® Official Course First Look Clinic Overview of Windows 8 By Ragowo Riantory, S.Kom, MCP.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1.
OVERVIEW TEAM5 SOFTWARE The TEAM5 software manages personnel and test data for personal ESD grounding devices. Test and personnel data may be viewed/reported.
Crew Management, Operations Control & Commercial Planning System
Skyward Server Management Options Mike Bianco. Agenda: Managed Services Overview OpenEdge Management / OpenEdge Explorer OpenEdge Managed Demo.
Microsoft Software Assurance for Academic Licensing Programs.
Novell Server Linux vs. windows server 2008 By: Gabe Miller.
Centricity™ Group Management Technology Discussion
Teraserver Darrel Sharpe Matt Todd Rob Neff Mentor: Dr. Palaniappan.
Lesson 5-Accessing Networks. Overview Introduction to Windows XP Professional. Introduction to Novell Client. Introduction to Red Hat Linux workstation.
Use of Thin Clients in an Industrial Environment Foxboro Southeast User’s Group Birmingham, Al February 10-11, 2009 Walter Conner Senior Plant Engineer.
Microsoft ® Application Virtualization 4.5 Infrastructure Planning and Design Series.
Virtual Network Servers. What is a Server? 1. A software application that provides a specific one or more services to other computers  Example: Apache.
Cap 333 Network Administration. Grades  20 marks distributed on  Assignments / Project Activities Individual Pairs  1 or 2 tutorial quizzes.
© 2012 The McGraw-Hill Companies, Inc. All rights reserved. 1 Third Edition Chapter 3 Desktop Virtualization McGraw-Hill.
Moving to Win 7 Considerations Dean Steichen A2CAT 2010.
XenData Digital Archives Simplify your video archive workflow XenData LTO Video Archive Solutions Overview © Copyright 2013 XenData Limited.
Microsoft ® Application Virtualization 4.6 Infrastructure Planning and Design Published: September 2008 Updated: February 2010.
Debunking the Top 10 Myths of Small Business Server: Using Windows SBS in Larger Environments Abstract: This session will debunk some of the common myths.
A Balancing Act: Managing Oracle Applications Scott Dines Oracle Systems Manager Boral Bricks Inc.
Effective Methods for Software and Systems Integration
1 CHEMS ANNUAL TRAINING Topics For Today CHEMS Status CHEMSPRO, The Next Step.
Fundamentals of Networking Discovery 1, Chapter 2 Operating Systems.
Technology Expectations in an Aeros Environment October 15, 2014.
Margaret Kubitschek, Solution Architect Sam Brewster, Customer Delivery Manager Dennis Keating, Account Executive Siemens PLM Software19 March 2010 Teamcenter.
SOFTWARE.
XA R7.8 Upgrade Process and Technical Overview Ruth Anne Pharr Sr. IT Consultant, CISTECH Inc.
11 INSTALLING WINDOWS XP PROFESSIONAL Chapter 2. Chapter 2: INSTALLING WINDOWS XP PROFESSIONAL2 OVERVIEW  Install Windows XP Professional  Upgrade from.
Microsoft ® Application Virtualization 4.6 Infrastructure Planning and Design Published: September 2008 Updated: November 2011.
Operating Systems. Operating systems  Between the hardware and the application software lies the operating system. The operating system is a program.
Tutorial 11 Installing, Updating, and Configuring Software
How to buy a PC Brad Leach David Howarth James Sawruk Andrew U.
Operating Systems  A collection of programs that  Coordinates computer usage among users  Manages computer resources  Handle Common Tasks.
Plant Engineering Workbench 5.3 New Features. 2 Workbench 5.3 ▼ New Features in 5.3 are: –New 3D Model Management module –Additions to the Admin module.
Chapter Fourteen Windows XP Professional Fault Tolerance.
Windows Server ® 2008 File Services Infrastructure Planning and Design Published: October 2008 Updated: July 2009.
Why does my perfectly working App Crash and Burn in Production? Matt Kramer Project Manager, STL Boeing Scalability Test Lab cell.
SMS 2003 Deployment and Managing Windows Security Rafal Otto Internet Services Group Department of Information Technology CERN 26 May 2016.
SERVER I SLIDE: 1. Anders Dahl Valgreen Data technician in Royal Danish Airforce IT Teacher at Mercantec Systems administrator at Technical College, Skjern,
RMS Update to TAC May 8, RMS Update to TAC ► At April 9 RMS Meeting:  Antitrust Training  RMS Voting Items: ► NPRR097Changes to Section 8 to Incorporate.
Business Intelligence Appliance Powerful pay as you grow BI solutions with Engineered Systems.
Linux Panel Panel Moderator: Sandra Vucinic. Panel Members Michael Brown - Glen Raven, Inc. Mark Farnham - Rightsizing, Inc. Rich Niemiec – TUSC Sandra.
Status of Windows 2000 deployment at CERN Alberto Pace, for the IT/IS group - April 2002
Cap 333 Network Administration. Grades  20 marks distributed on  Assignments / Project Activities Individual Pairs  1 or 2 tutorial quizzes.
Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill Technology Education Copyright © 2006 by The McGraw-Hill Companies,
WCL303 Business Desktop Deployment (BDD) 2007: Part 2, Deploying the 2007 Office system Michael Niehaus Systems Design Engineer Microsoft
14 th April 1999CERN Site Report, HEPiX RAL. A.Silverman CERN Site Report HEPiX April 1999 RAL Alan Silverman CERN/IT/DIS.
Randy MelenApril 14, Stanford Linear Accelerator Center Site Report April 1999 Randy Melen SLAC Computing Services/Systems HPC Team Leader.
Waste Management Inspection Tracking System (WMITS)
1 Evolution and Revolution: Windows 7 and Desktop Virtualization Changing the Desktop Support Landscape Denise Harrison, CIO and Vice President.
John Samuels October, Why Now?  Vista Problems  New Features  >4GB Memory Support  Experience.
Office 365 is cloud- based productivity, hosted by Microsoft. Business-class Gain large, 50GB mailboxes that can send messages up to 25MB in size,
Virtual Server Server Self Service Center (S3C) JI July.
Wyoming Technology Readiness February Agenda Wyoming Training - Feb Technology Readiness  Schedule of events  Components and System Requirements.
Windows Vista Configuration MCTS : Installing and Upgrading.
ProStoria DATA-AS-A-SERVICE FOR DEVOPS. Agenda: ProStoria presentation Contact data.
CyberPatriots 2016 Student Handbook.
System Migration Guy “Randy” Fleegman
Installing CareerScope V10
Experiences and Outlook Data Preservation and Long Term Analysis
Windows 7 deployment at CERN
Malcolm Days Mark Miners James Farnhill
Debunking the Top 10 Myths of Small Business Server: Using Windows SBS in Larger Environments Abstract: This session will debunk some of the common myths.
CERN Windows Roadmap Tim Bell 8th June 2011.
Upgrading to Microsoft SQL Server 2014
HP Quality Center 10 Hottest Features and Project Harmonization
SharePoint 2019 Changes Point of View.
"Cloud services" - what it is.
Presentation transcript:

11 The Ultimate Upgrade Nicholas Garcia Bell Helicopter Textron

2 Agenda  Who am I?  What are we doing?  Why are we doing it?  How are we doing it?  Are we going to do this again?  Questions

33 Who am I?  Nicholas Garcia  Bell Helicopter Textron  IT CAD/CAM  Fort Worth, TX   (817)

44 Who am I?

5 What are we doing?  Upgrade from NX 1 to NX 5  Upgrade from Teamcenter Engineering to Teamcenter Engineering 2007  Migrate workstations from AIX Unix to Windows XP  Migrate from 32-bit to 64-bit  Migrate servers from AIX to Windows  Decommission Multi-site

6 Why are we doing it? Current Environment  ~200 AIX 5.3 Workstations  NX 1 on AIX  Teamcenter Engineering 9 on AIX and Oracle 9i  2.5 Terabytes of NX Data  Multi-site for WAN

7 Why are we doing it?

8 Issues  Loading times unacceptable  Multi-site sync issues  NX 1 “no patch” issues  No disk space for growth  “View” only capabilities  Users want to be current  No-support/EOL on current software versions

9 Why are we doing it? Future Environment  ~200 Windows XP 64-bit Workstations  NX 5 64-bit on Windows  Teamcenter 2007 on Windows  4 Terabytes total disk space  2-tier for “local” sites (DFW Area)  4-tier w/Site Cache for remote sites  No Multi-site!!!

10 Why are we doing it?

11 How did we do it? Background  Oct 2006 Project initiation  Upgrade from TCe 8 to TCe 9  Move from HP-UX to AIX  NX 3 or NX 4?  What are the real issues?

12 How did we do it? Review Current Environment  Users  ~200 Users  4 Sites  Data  2.4 Terabytes  Multisite between sites  Very large assemblies that do not open

13 How did we do it? Review Current Environment  Processes  Over 70 customizations in NX  10 Customizations in TCe  Hardware  AIX Servers  AIX Storage  Oracle Database

14 How did we do it? Review Solutions  NX 3 vs NX 4 vs NX 5 (remember this was around July 2007)  Begin testing of Windows 32/64-bit vs AIX 32/64-bit  Compare NX 4 and NX 5 (NX 3 decided to be outdated)  Test everything with TCe 9

15 How did we do it? Decisions  October 2007  Loading capabilities with Windows showed to be greatly improved  NX 4  Teamcenter 9  How do we rollout?

16 How did we do it? Rollout options  Upgrade to NX 4 on AIX then migrate to Windows as needed  Migrate to Windows with NX 1 then upgrade to NX 4  Mix environments with some users on Windows and some on Unix  Final Decision: Full Migration to NX 4, TCe 2005 and Windows in one weekend

17 How did we do it? Getting Started  Current skillset and past experiences (NX 1 upgrade) showed that we needed assistance  INCAT contracted to provide technical expertise, coding upgrades and training  CSC supports Bell infrastructure  Goal was for Mid-year 2008 rollout, which changes the targets

18 How did we do it? Moore’s Law  12+ months since project first started  NX was available  Teamcenter 2007 was available  New Hardware (Quad Core) for Windows PC’s All this means change in scope!

19 How did we do it? Hardware Definition and Acquisition  Compare 64-bit CAD compatible PC’s  Define and order  Servers  Disk Storage  Workstations

20 How did we do it? PC Workstations  New at Bell  Windows XP 64-bit  Dual Quad Core Intel  8 GB Memory  2 x 250 GB Raid 1 Hard Drive (great for caching)

21 How did we do it? Now for the fun stuff  Customizations  Server installation  Client installation  Training  Testing  Results?  Go Live

22 How did we do it? Customizations  Needed before any testing can occur  Gather all source code (very little in source control)  Give to Incat to upgrade and migrate  Answer lots of questions about purpose, functionality and processes  Some don’t work because no longer on AIX  How do we handle these?

23 How did we do it? Server Installation  3 Environments  Sandbox (Development)  Test (Full copy of production, during project only)  Production  Multi-site Decommission  Stop creation of new parts at external site  Migrate all data back to single site (not an easy task)

24 How did we do it? Server Installation Sandbox  Proof of Concept  Functionality only testing  Limited dataset  Use of existing desktop for immediate rollout

25 How did we do it? Server Installation Test  Production server hardware  Full copy of production  Data migration  200GB Limit for backup/restore  4TB at 200GB = 20 different mounts  2 weeks to migrate data from Unix  Database migration

26 How did we do it? Server Installation Test  Install Teamcenter 9 to verify database connections  Install Teamcenter 2007 on Server  Perform upgrade to Teamcenter 2007  NX 5 data upgrade? On the fly upon opening

27 How did we do it? Client Installation  Create similar share on Windows  Installation process automated as much as possible with batch files, which reduced install time from 2 hours to 25 minutes  Small quirks are annoying  NX installation warning  Adding user id to XML install file  No silent install for patches

28 How did we do it? Client Installation  150 PC Workstations ordered, imaged, and delivered  60 were “refreshes”  2 months to rollout  All were ready prior to go live

29 How did we do it? Training  Outsourced, onsite training  6 weeks, 3 locations, 150+ users, 32 hours each  Pilot training class with Super Users in Engineering and Manufacturing  Courses available online after classes  Documentation, CAST, I.GET.IT for additional functionality

30 How did we do it? Testing  Basic Functionality performed by core team  Sandbox used for code verification  Test system used for performance, load and timing tests  Pilot training class users asked to do “real” work in test system  Refresh of test system with production data

31 How did we do it? Testing  Printing and Plotting changes  New functionality  Non-Project related issues  Moving to Windows  Downstream processes  64-bit  Integrations with other systems  How to support Windows

32 How did we do it? Results P/N Load & Save Times (s) NX1 (UNIX) (baseline) NX5 - 1st (Initial load in Windows) NX5 - 2nd (Same w/s - cached) DFW Part Part Part Part Part Part Part AMA Part Part Part Part Part

33 How did we do it? Go Live  2 Dry Runs to ensure timing  Perform “sync” between production and test system volumes  Copy production database to test  Perform upgrade and ensure timing is correct  Everything is ready prior to go live

34 How did we do it? Go Live  June 16 th  Friday 3:30 pm – Monday 6 am  Coordination across 5 Plants, 2 cities  Coordination between 3 companies: Bell, CSC, Incat  1 Team to make it happen

35 How did we do it? Lessons Learned  Get help if needed  Hardware migration is hard  Dry Runs are useful for timing  64-bit migration may have issues  Hardware/software changes quickly

36 What did we do again?  Upgraded NX 4 versions  Upgraded Teamcenter 3 versions  Migrated from Windows to Unix on Clients  Migrated from Windows to Unix on Servers  Migrated from 32-bit to 64-bit All in one weekend!

37 Are we going to do this again? NO

38 Are we going to do this again?  Install Patches  Review new releases of TCe and NX  Review new hardware  Continual process improvements

39 Questions? Nicholas Garcia (817)