1. Margaret Kubitschek, Solution Architect Sam Brewster, Customer Delivery Manager Dennis Keating, Account Executive Siemens PLM Software16 March 2010 Teamcenter Unified Architecture

2. Page 2 Agenda  Goals  Business Objective  Site Survey Assessment (As-Is)  PLMVDM Methodology  Conceptual Architecture (To-Be)  Assumptions  Risks  Discussion

3. Page 3 Goals  Review architecture assessment  Discuss PLM Value Delivery Methodology  Review deployment plan with open discussion

4. Page 4 Business Objectives  Provide a lab wide Engineering Data Manager  Provide a enough licenses to support the users  Provide a cost-effective fully functional solution  Deploy Teamcenter Unified in early 2010

5. Page 5 Site Assessment  5-Production Teamcenter Data Manager databases and I-deas v12 to migrate multiple locations (Reference Siemens Audit Report November 2005)  2 -Teamcenter Engineering 2007 to migrate (Dev and Test)  1800 Teamcenter users in 5yrs  Today 2-Tier architecture: Clients on Windows XP, Macs, Linux, Oracle on Solaris, Volumes on Windows servers/BlueArc NAS  Network backbone bandwidth is 20-40gb, internet 10g  In-house Single-Sign-On authentication using Kerbose  BlueArc NAS is RAID 5

6. Page 6 Organization View Teamcenter Platform Engineers/Designers/ Technicians Project Managers Scientists Administrators Document Management Parts/Classification & BOM Management Change Management Requirements Management CAD Integration & Visualization

7. Page 7 PLM VDM Methodology

8. Page 8 Benefits Ensures Project Success through  Structured approach  Success criteria aligned with your business goals  Mutually agreed quality gates and milestone reviews  Clear & defined project governance model  Template based project documentation  Best practices from previous projects accelerates deployment  Enables global projects through common work process  Risk is reduced due to increased repeatability  Siemens PLM Software has a single methodology adopted globally across the services organisations

9. Page 9 The Pre-Align Phase Executed in parallel to the sales process Major Tasks Understand customer requirements Establish overall project scope Determine preliminary project schedule Define the services strategy Conduct an infrastructure assessment Develop initial project budget Goal  To define the Solution Outline and a high level Statement of Work

10. Page 10 The Align Phase Major Tasks Capture complete, accurate project definition through technical workshops, use case definition and rapid prototyping Align solution requirements to OOTB (out-of-the-box) product capabilities Transform solution concepts defined during Pre-Align activities into a well defined overall solution architecture Goal  Customer acceptance of use cases and requirements  Authorization for work to proceed

11. Page 11 The Align Phase

12. Page 12 The Plan Phase Major Tasks Develop documents that are used to execute and control the project and to develop technical design Define the detailed plans for scope, schedule, cost, skills, resources, risks, quality, and communication depending on the complexity of the solution Baseline test environment, training environment & the system infrastructure Goal  Baseline System Architecture  Review & Baseline Project Plans  Functional & Design Specs

13. Page 13 The Plan Phase

14. Page 14 The Plan Phase Detailed Step Sample

15. Page 15 The Build Phase Major Tasks Create the solution with strict adherence to requirements Configure & test solution with the technical team Implement data migration strategy Start development of the training materials Perform unit & integration testing with internal project team Goal  The solution is ready for customer testing

16. Page 16 The Build Phase

17. Page 17 The Test Phase Major Tasks Verify that solution fulfills the requirements. Validate that system is ready for production use. Get user acceptance through functional and system tests Goal  Solution is ready for deployment into production environment.  Solution is accepted by the customer

18. Page 18 The Test Phase

19. Page 19 The Deploy Phase Major Tasks Deliver production-ready solution to end users Migrate data to the production environment Deploy solution with all interfaces Train Users and help desk teams Goal  To hand over solution to the customer for production use

20. Page 20 The Deploy Phase

21. Page 21 The Close Phase Major Tasks Complete & Archive Project documents Conduct Project post-mortem review Capture & document lessons learned Release project team Goal  Complete all administrative aspects of the project

22. Page 22 The Close Phase

23. Page 23 PLM Value Delivery Methodology Summary   Siemens PLM Software has a single methodology adopted globally across the services organizations  This ensures project success and results in real business impact and faster time to value

24. Page 24 Functional View CAD DATA MANAGEMENT AutoCAD, NX, Solid Edge Drawing & 3D ACCESS CONTROL Information Security INTEGRATED VISUALIZATION Access 2D & 3D Drawing Sectioning / Measure / Clearance Check No CAD Tool Required COLLABORATION Share Documents, Conference BOM MANAGEMENT Design Re-use Variants / Options RELEASE MANAGEMENT Engineering Release Process Teamcenter Single Source of Product Data MS Office Integration

25. Page 25 Fermi Engineering Process: To-Be

26. Page 26 IT View Preliminary

27. Page 27 Qty Server SPECint_rate _base2006 CPU (GHz) Processo rs RAM (GB) HDD (GB)Users#Recommendation 1+n Tc Server- Corporate371na 144 GB Win, 288GB Linux1.5GB-3GB1200 Windows 2003 Server SP2/SP3,32bit or 64 bit, or Linux64 SuSE Ent.9.0SP2/SP3,10.0 (no performance specs) for CAD 1 FMS / Volume / License Serverna2.5GHz+24 GB324 TB1200 Windows 2003 Server SP2 or SP3,32bit or 64 bit, or for CAD files 1+nDispather Serverna2.5GHz+28 GB500 MB75 Windows 2003 Server SP2 or SP3,32bit or 64 bit 1+nTcC and TcU Webna3GHz+24 GB4 GB +1200 Windows 2003 Server SP2 or SP3,32bit or 64 bit 1TcU Oracle68 non-RACna 16 GB 3 GB + (base)1200 Solaris 10 or Linux SUSE with Oracle 10.2.0.1 or 11g 1TcC MSSQLna3GHz+24 GB100 GB +300 Windows 2003 Enterprise Edition Server SP1, 64bit 1TcC Conferencena3 GHz+24 GB Linux SUSE Enterprise Server (SLES) 9 SP2, SP3, and 10 9004 Tier Rich Clientna3.4 GHzna 4GB w/NX150-250GB900XP Pro SP2 32 or 64bit 300Thin Clientna 2-4GB100 GB +300 XP Pro SP2, MS IE or Mozilla Firefox, Apple Safari Deployment View Preliminary

28. Page 28 Migration: TDM to TcU I-deas to NX Migrate TDM Phase III Upgrade TcEng to TcU: Reuse Development and Test Upgrade TcEng Phase II Deployment View Phased Benefits Plan Timeline Solution Capability Stages Foundation: Rapid return on OOTB OOTB Capability Phase I Teamcenter Unified & Community Part, BOM and Document Mgmt MCAD/MSOffice integration Visualization Project Collaboration Technology Enablers Teamcenter Advanced Product Configuration Workflow Change Management Teamcenter Content Migration Mgr Migrate TDMs to TcU Migrate I-deas to NX

29. Page 29 Assumptions  CAD packages may have to be upgraded may delay the project  Visualization will still have to be installed on all workstations

30. Page 30 Risks  Power in the computer room to host at FCC building  Disk storage space for CAD file

31. Page 31 Rich Client Additional Functionality Export to Word Live Export to Excel Live View Requirement Content with Object Template Applied Export Specification with Object Template Overwrite Creation Excel / Object / Spec Templates Import Spec by Keyword Integration to NX Integration to MSOffice File Client Cache

32. Page 32 Siemens TDM Migration offers 1.Installation assistance 2.Project alignment with our checklist 3.Software configuration 4.Sample data migration 5.System validation 6.Administrative mentoring 7.Production rollout support

33. Page 33 Your Questions Answered 1.Any Solid Edge issues? Some at Tc Express and 2007 but patched. 2.Any risks starting Beta testing? I recommend not working on Beta Tc code. That would be 8.2 or 8.3 and probably delay rollout 3.What are Thin vs Rich client limitations? (see next slide and Client Interface guide) Thin client use http/http, 4tier is installed OTW or TEM. Thin client only supported in 4tier architecture. 4.Should redundant license servers be implemented? The license server will be on the FMS/Volume server which should be RAID 5.Is Linux Red Hat Enterprise supported? Red Hat Enterprise isn’t supported but SUSE is, it is noted in the table and will require more memory on the Tc pool servers. 6.What primary platform is Tc developed on? Tc8 was developed primarily on Windows. QA has increased testing. 7.Is there performance issues between 2 vs 4tier RAC? 2tier works in LAN 5-10ms.4tier Rich is affected by some virus scanners monitoring all HTTP traffic from a host. Suggest deactivating feature. MSOffice display problem when rich client installed on virtual drive. 8.Is AutoCAD LT supported? No

34. Page 34 Tentative Roadmap (Fermi)

35. Thank You Teamcenter Unified Architecture