1. 1 Teamcenter: Engineering Data Management System UG NX: Transition to New Mechanical CAD System Rich Stanek On behalf of the Teamcenter/NX Implementation Team

2. 2 What is Teamcenter? Software tool to help us do our jobs better Commercial, Product Lifecycle Management (PLM) software (Siemens) Document and Process centric relational database (Oracle) Used by many large, internationally based manufacturing companies Also used by DESY for the XFEL project (TC Enterprise) CERN study on EDMS identified TC as upgrade to their present system Why are we transitioning to UG NX from I-Deas? I-Deas is at the end of its life cycle (has been known for some time) Scheduled to be decommissioned in the next few years No development/enhancements are going into I-Deas New features all going into NX UG NX (also a Siemens product) is one of the market leaders in CAD All licenses are dual functional (I-Deas and NX)  reduces cost to switch Easiest transition since many features are common Introduction

3. 3 Who will be affected by move to Teamcenter? Lab’s technical, procurement and fabrication staff Scientists, engineers, designers, technicians, machinists, QC, ES&H & procurement personnel Mechanical, electrical, and civil disciplines Used for projects and for internal engineering data Allow access for Collaborators (project-related eng. documents) Who will be affected by move to NX? Mechanical design work in progress will continue in I-Deas All new mechanical project work will be started in NX Software tools exist to convert I-Deas data files to NX format Eventually want all mechanical design groups  NX Want to explore how much ECAD work can be done in NX as well Goal is to get down to two CAD systems NX and AutoCAD Always exceptions to the rule Need to explore the needs of the electrical community Introduction (cont’d)

4. 4 What problems are we trying to solve with Teamcenter? Lack of a common EDMS  Many DocDB instances and ad hoc systems Makes collaboration (even between Divisions) difficult CAD files are disjointed  mechanical, electrical, civil all handled differently Hard to find information, engineering reports, analysis on previous designs… “Reinvent the wheel” far too often Loss of data/information when people retire or move to another project Reviews and Signoffs require a manual process Often without full information available to the approver What problem are we trying to solve with NX? Not a problem per se but an opportunity Replace I-Deas with system that has similar (or better) functionality and bring more consistency to design process Introduction (cont’d)

5. 5 Why did we choose Teamcenter and NX? Started off within the CAD Tools Committee as a means to replace our mechanical CAD (I-Deas) TDM Needed software that could handle all of our common file formats NX, AutoCAD, MS Office, pdf, JT, as well as ECAD formats Wanted a system with a proven track record Something with all the capabilities we will need Minimize customization to limit problems with updates Teamcenter and NX have a very strong integration (built in) Why Teamcenter

6. 6 What type of documents will be stored in Teamcenter? Focus on engineering documents and data CAD files, specifications, requirements documents, engineering calculations & analysis, safety documents, QC reports, vendor data... Will this be our only Document Management System? No. Lab is also pursuing SharePoint as a more general DMS Teamcenter will be integrated with SharePoint There may be other systems that will be linked in as well Goal is one common access point for documents “one stop shopping” Integrated Document Management

7. Licensing  Teamcenter Named user licenses Have licenses for FNAL personnel + some collaborators 1200 Author, 600 Consumer  Plan for how to grant access to Teamcenter by collaborators who do not have FNAL access rights is still under development  Current I-Deas licenses will convert to NX Current I-Deas Licenses  32 Solid Modeling, 65 Drafting Current # of Designers  ~ 42 mech., 6 elec., 13 civil/ACAD But, we are pushing mechanical design towards a more 3D centric environment  more solid modeling  Will need more modeling licenses  Divisions (AD, PPD, TD) & Projects will be asked to contribute 2010047

8. Short Answer Combination of SharePoint and Teamcenter should replace DocDB instances and provide much more functionality and consistency Will also give an opportunity for more concurrent engineering and less dependence on paper signoffs Move to NX should bring more consistency and efficiency to the way we do mechanical design Will also give an opportunity to integrate some ECAD 2010048

9. Organizational View 9

10. 10 Engineering Process & Teamcenter Teamcenter - EDMP

11. Core Team and Steering Committee Members 11 Division/Section Core Team Members Steering Committee Members CD Bob Andree Tony Metz Scott Nolan/Julie Trumbo Nelly Stanfield Simon Kwan Bill Boroski Rich Karuhn Tony Metz Bob Tschirhart TD James Blowers Tom Nicol Dave Harding AD - Mechanical Tony Parker Salman Tariq Paul Czarapata AD - ElectricalRich Divelbiss AD – Cryogenics Alex Martinez Phil Pfund (safety) PPD – MechanicalDave Pushka Peter Wilson PPD - ElectricalMarcus Larwill ES&H Jody Federwitz Cindy Rogers Directorate Rich Stanek, Kathryn Grim (PR)Rich Stanek FESSJim Niehoff Randy Ortgiesen ManufacturingEd Hagler Project ManagementElaine McCluskey Integration PartnerSiemens

12. Working Groups 20100412 Working GroupLeaderScope WG1E. McCluskeyGroups/Roles/Access WG2A.MartinezDocument Item Types WG3J. BlowersEngineering Doc Storage WG4D. Pushka S Kwan Engineering Applications WG5T. ParkerNX CAD Preparations WG6C. RogersES&H Safety Documents Additional WG will be formed as required

13. 13 Core Team has been meeting for several months Getting good participation and feedback Not easy to map out a plan for something that has been so disorganized Working Groups are active Used their initial reports as input for Alignment Phase Met with India Labs’ representatives (IIFC) Working on details of how Multi-Site system can be configured Understand infrastructure and security limitations Contract for consulting services (Siemens) is in place Will use “industry best practices” to help establish data schema First “Alignment” session was held two weeks ago Actively working on configuration Building up hardware architecture Utilize existing infrastructure as well as new hardware purchase High availability, scalable, redundancy Working with the SharePoint Team to assure smooth integration Current Status

14. Schedule  Currently in the process of going through the standard Siemens Value Delivery Methodology Plan to have Teamcenter ready for limited production use by March 2011 Core Team/Working Groups providing valuable input  Same time frame, we will move from I-Deas to NX Integration of NX in Teamcenter is better Gives us time to train our design staff appropriately Allows us to “configure” NX to maximize design efficiency  Hopefully SharePoint is ready on the same timescale to provide an integrated approach and we have solution for dealing with “named user” collaborators 20100414

15. 15 Teamcenter will be the Lab’s EDMS and NX will be the Lab’s new mechanical CAD software Have a plan for how to proceed Established project charter/roadmap to guide implementation This program has Director’s support Funding for hardware, software and consulting services Team has formed to align and implement the software Strong representation from around the Lab Needed for success Commitment from D/S/C and Department Heads Acceptance from the engineering and technical staff Resources for training, data migration and testing Summary