1. Margaret Kubitschek, Solution Architect Sam Brewster, Customer Delivery Manager Dennis Keating, Account Executive Siemens PLM Software19 March 2010 Teamcenter Global Deployment Options for India Collaboration

2. Page 2 Agenda  Objectives  Assumptions  Options with Pros and Cons  Risks  Discussion

3. Page 3 Objectives  Support a collaboration project between Fermilab and India  Support 25 Users, 15 in India and 10 Fermilab  Manage NX models, assemblies, parts, and drawings, about 1800 files total of about 1GB design package not including revisions  Provide a quick Release process of status  Provide JT and CGM files (manually or through translation server)  Deploy Production in mid May 2010  This deployment is Phase 1 rollout of Fermilab’s long range Teamcenter implementation that needs to scale for 5 years

4. Page 4 Assumptions  Limited capability to manage NX files only  Rolling out to only the India Collaboration Project team only (25 total users)  No migration of Ideas v12 files to NX for Phase 1  IT Infrastructure of network and servers is acceptable and stable  Only Siemens provides services for accelerated implementation (knowledge transfer and mentoring moved to later phase)  Must leverage on-line training

5. Page 5 Objectives: Phase 1: Features Collaboration NX CAD Document Mgmt

6. Page 6 Option 1: Teamcenter Community Qty ServerSPECint_ rate_base 2006 CPU (GHz) Proces sors RAM (GB) HDD (GB) Users # Recommendation 1TcCna3GHz+24 GB+100 GB+25 Reuse TcEng Server, Windows 2003 Server SP2/SP3,32bit/64 bit, MS IIS 6.0. TcC/MOSS) 1TcC MSSQLna3GHz+24 GB100 GB +25 Existing cluster,Windows 2003 Enterprise Edition Server SP1, 64bit,3par 25 4 Tier Rich Clientna3.4 GHzna 4GB w/NX 150- 250GB25 XP Pro SP2 32/64bit,Visualization, Tc Integration to NX,Client FCC(RAC)  4 servers needed – 2 DEV, 2 PROD  May be able to leverage existing servers  Will deploy a new SharePoint instance

7. Page 7 Option 1: Teamcenter Community Pros  Less time to install  Easy to use  Collaboration site  Less hardware and software Cons  Not CM tool  No workflow  Business rules have to be setup  No NX integration  Manual translation for JT files 2 days + 3 days + 10 days + 2 days + 3 days = 20 days

8. Page 8 Option 2: Teamcenter Unified Qty ServerSPECint_ rate_base 2006 CPU (GHz) Processo rs RAM (GB)HDD (GB) Users#Recommendation 1TcU Web and TcServer142GHz+2+4+gb 25Reuse Windows 2003 Server SP2/SP3,32/64 bit, 2 (TBD) FMS/Volume/License Serverna2.5GHz+24 GB4gb25 Reuse BlueArc, Add Disks,TBD a File/Volume Servers in Chicago and/or India. 1(TBD)File Server Cachena2+22GBTBD25 Windows 2003 Server SP2 or SP3,32bit or 64 bit, or for CAD files transfers. 1Dispather Serverna2.5GHz+24gb100mb9 Reuse ETS,Windows 2003 Server SP2/SP3,32/64 bit, Translate NX models and assemblies to Jt, and drawings to CGM 1TcU Oracle42 GHZ+24 + gb 3 GB + (base)25Solaris Oracle 254 Tier Rich Clientna3.4 GHzna4GB w/NX150-250GB25XP Pro SP2 32 or 64bit  4 servers (min) PROD; 1 server possible for DEV  2 new servers needed (TBD); may be able to leverage existing servers

9. Page 9 Option 2: Teamcenter Unified Pros  Configuration Mgmt for NX CAD (OOTB)  Can setup one-step Release Process  Can translate CAD files  Begin to leverage 4 tier architecture Cons  Increased training for TcUA and NX to Users and Admins  Increased time to setup and configure  Additional hardware/software  Limited feature rollout to NX only (no Req., Doc Mgmt, Change, Mgmt, other CAD pkg. Mgmt…) compared to full deployment  No migration; only import of existing NX  Additional technical risk to full Fermi deployment 5 days + 5 days + 20 days + 5 days + 10 days = 45 days

10. Page 10 Option 3: Teamcenter Community and Unified Qty ServerSPECint_r ate_base2 006 CPU (GHz)ProcessorsRAM (GB)HDD (GB)Users#Recommendation 1TcC and TcU Webna3GHz+24 GB4 GB +25 New,Windows 2003 Server SP2 or SP3,32bit or 64 bit 2 (TBD) FMS/Volume/License Serverna2.5GHz+24 GB 25 Reuse BlueArc, Add Disks,TBD a File/Volume Servers in Chicago and/or India. 1(TBD)File Server Cachena2+GHz22GBTBD25 Windows 2003 Server SP2 or SP3,32bit or 64 bit, or for CAD files transfers. 1Dispather Serverna2.5GHz+24GB100MB9 Reuse ETS,Windows 2003 Server SP2/SP3,32/64 bit, Translate NX models and assemblies to Jt, and drawings to CGM 1TcU Oracle42 GHZ+24+GB3 GB +25Solaris Oracle 1TcC MSSQLna3GHz+24 GB100+GB25 Existing cluster,Windows 2003 Enterprise Edition Server SP1, 64bit,3par 1TcC Conferencena3 GHz+24 GB100MB25 New,Linux SUSE Enterprise Server (SLES) 9 SP2, SP3, and 10 254 Tier Rich Clientna3.4 GHzna4GB w/NX150-250GB25XP Pro SP2 32 or 64bit  7 servers (min) PROD; 4 DEV

11. Page 11 Option 3: Teamcenter Community and Unified Pros  Collaboration site  Conferencing available  Configuration Mgmt for NX  Can setup one-step Release Process  Can translation cad files  Begin to leverage 4 tier architecture Cons  Business rules have to be setup  More learning time on TcU for Users and Admins  More time to setup and configure  More hardware/software  Limited feature rollout to NX only (no Req., Doc Mgmt, Change, Mgmt, other CAD pkg. Mgmt…)  No migration; only import of existing NX  Additional technical risk to full Fermi deployment 10 days + 10days + 25 days + 5 days + 10 days = 60 days

12. Page 12 Application Integrations TcU SW IntegrationAs-Is at FermilabTcU 2007.1TcU 8.0TcU 8.1 AutoCAD2004-2010 2007,2008,2009,2010 (tc2007.1mp3)2008,2009,2010Not available AutoCAD Mechanical 2007,2008,2009,2010 (tc2007.1mp3)2008,2009,2010Not available Inventor Few seats version unknown 10,11,2008,2009, Pending20102008,2009,2010Not available Solid Edge20 V21upate3(Tc2007.1.2), ST,ST2ST2Pending ST2, ST3 NXna NX 4,5,6,7.0(Limited compatibility,Not Recommended,Tc2007.1MP 7b and 8.0.1)) 6.0.3 or > (pairs w/NX I- deas 6) 6.0.4 MP1(pairs w/NX I- deas6), 7.01 (NX I-deas 6.1)  Recommend NX 6.x available at all current TcU releases

13. Page 13 Risks  Fix Power in the computer room to host at FCC building  Fix Disk storage space for CAD file  Unknown network performance from/to India  Reuse of existing hardware servers  Fermilab support tier for the time zone difference (12 hours)

14. Thank You Teamcenter Global Deployment Options for India Collaboration