Presentation Transcript

1. Teamcenter Unified Architecture Margaret Kubitschek, Solution Architect Sam Brewster, Customer Delivery Manager Dennis Keating, Account Executive Siemens PLM Software 16 March 2010
2. Agenda Goals Business Objective Site Survey Assessment (As-Is) PLMVDM Methodology Conceptual Architecture (To-Be) Assumptions Risks Discussion
3. Goals Review architecture assessment Discuss PLM Value Delivery Methodology Review deployment plan with open discussion
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. 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. Scientists Administrators Project Managers Engineers/Designers/ Technicians Organization View Teamcenter Platform Parts/Classification & BOM Management Change Management Requirements Management CAD Integration & Visualization Document Management
7. PLM VDM Methodology
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. The Pre-Align PhaseExecuted in parallel to the sales process Goal To define the Solution Outline and a high level Statement of Work 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
10. The Align Phase Goal Customer acceptance of use cases and requirements Authorization for work to proceed 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
11. The Align Phase
12. The Plan Phase Goal Baseline System Architecture Review & Baseline Project Plans Functional & Design Specs 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
13. The Plan Phase
14. The Plan PhaseDetailed Step Sample
15. The Build Phase Goal The solution is ready for customer testing 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
16. The Build Phase
17. The Test Phase Goal Solution is ready for deployment into production environment. Solution is accepted by the customer Major Tasks Verify that solution fulfills the requirements. Validate that system is ready for production use. Get user acceptance through functional and system tests
18. The Test Phase
19. The Deploy Phase Goal To hand over solution to the customer for production use Major Tasks Deliverproduction-ready solution to end users Migrate data to the production environment Deploy solution with all interfaces Train Users and help desk teams
20. The Deploy Phase
21. The Close Phase Goal Complete all administrative aspects of the project Major Tasks Complete & Archive Project documents Conduct Project post-mortem review Capture & document lessons learned Release project team
22. The Close Phase
23. 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 PLM Value Delivery Methodology
24. Functional View Single Source of Product Data Teamcenter CAD DATA MANAGEMENT AutoCAD, NX, Solid Edge Drawing & 3D BOM MANAGEMENT Design Re-use Variants / Options ACCESS CONTROL Information Security INTEGRATED VISUALIZATION Access 2D & 3D Drawing Sectioning / Measure / Clearance Check No CAD Tool Required MS Office Integration COLLABORATION Share Documents, Conference RELEASE MANAGEMENT Engineering Release Process
25. Fermi Engineering Process: To-Be
26. IT View Preliminary
27. Deployment View Preliminary
28. Phase I Phase II Phase III Technology Enablers Migrate TDM Solution Capability Stages Migration: TDM to TcU I-deas to NX Teamcenter Content Migration Mgr Migrate TDMs to TcU Migrate I-deas to NX Upgrade TcEng Upgrade TcEng to TcU: Reuse Development and Test Teamcenter Advanced Product Configuration Workflow Change Management OOTB Capability Foundation: Rapid return on OOTB Teamcenter Unified & Community Part, BOM and Document Mgmt MCAD/MSOffice integration Visualization Project Collaboration Timeline Deployment ViewPhased Benefits Plan
29. Assumptions CAD packages may have to be upgraded may delay the project Visualization will still have to be installed on all workstations
30. Risks Power in the computer room to host at FCC building Disk storage space for CAD file
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. Siemens TDM Migration offers Installation assistance Project alignment with our checklist Software configuration Sample data migration System validation Administrative mentoring Production rollout support
33. Your Questions Answered Any Solid Edge issues? Some at Tc Express and 2007 but patched. 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 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. Should redundant license servers be implemented? The license server will be on the FMS/Volume server which should be RAID 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. What primary platform is Tc developed on? Tc8 was developed primarily on Windows. QA has increased testing. Is there performance issues between 2 vs 4tier RAC? 2tier works in LAN < 5ms latency and small assemblies. 4tier works best in WAN and latencies of >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. Is AutoCAD LT supported? No
34. Tentative Roadmap (Fermi)
35. Teamcenter Unified Architecture Thank You