Margaret Kubitschek, Solution ArchitectSam Brewster, Customer Delivery ManagerDennis Keating, Account Executive

Siemens PLM Software 16 March 2010

Teamcenter Unified Architecture

Page 2

Agenda

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

Page 3

Goals

Review architecture assessment

Discuss PLM Value Delivery Methodology

Review deployment plan with open discussion

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

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

Page 6

Organization View

Teamcenter Platform

Engineers/Designers/Technicians

Project Managers

ScientistsAdministrators

DocumentManagement

Parts/Classification & BOM

Management

ChangeManagement

RequirementsManagement

CAD Integration &Visualization

Page 7

PLM VDM Methodology

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

Page 9

The Pre-Align Phase Executed in parallel to the sales process

Major TasksUnderstand 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

Page 10

The Align Phase

Major TasksCapture 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

Page 11

The Align Phase

Page 12

The Plan Phase

Major TasksDevelop documents that are used to execute and control the

project and to develop technical designDefine the detailed plans for scope, schedule, cost, skills, resources,

risks, quality, and communication depending on the complexity of the

solutionBaseline test environment, training environment & the system

infrastructure

Goal Baseline System Architecture Review & Baseline Project Plans Functional & Design Specs

Page 13

The Plan Phase

Page 14

The Plan PhaseDetailed Step Sample

Page 15

The Build Phase

Major TasksCreate the solution with strict adherence to requirementsConfigure & test solution with the technical team Implement data migration strategyStart development of the training materialsPerform unit & integration testing with internal project team

Goal The solution is ready for customer

testing

Page 16

The Build Phase

Page 17

The Test Phase

Major TasksVerify 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

Page 18

The Test Phase

Page 19

The Deploy Phase

Major TasksDeliver production-ready solution to end users Migrate data to the production environmentDeploy solution with all interfacesTrain Users and help desk teams

Goal To hand over solution to the customer

for production use

Page 20

The Deploy Phase

Page 21

The Close Phase

Major TasksComplete & Archive Project documentsConduct Project post-mortem review Capture & document lessons learned

Release project team

Goal Complete all administrative aspects of

the project

Page 22

The Close Phase

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

Page 24

Functional View

CAD DATA MANAGEMENTAutoCAD, NX, Solid Edge

Drawing & 3D

ACCESS CONTROLInformation Security

INTEGRATED VISUALIZATIONAccess 2D & 3D Drawing

Sectioning / Measure / Clearance CheckNo CAD Tool Required

COLLABORATIONShare Documents,

Conference

BOM MANAGEMENTDesign Re-use

Variants / Options

RELEASE MANAGEMENTEngineering Release Process

Teamcenter

Single Source of Product Data

MS OfficeIntegration

Page 25

Fermi Engineering Process: To-Be

Page 26

IT View

Prelim

inary

Page 27

Qty ServerSPECint_rate

_base2006CPU (GHz)

Processors

RAM (GB)

HDD (GB) Users# Recommendation

1+nTc Server-Corporate 371 na na

144 GB Win,

288GB Linux 1.5GB-3GB 1200

Windows 2003 Server SP2/SP3,32bit or 64 bit, or Linux64 SuSE Ent.9.0SP2/SP3,10.0 (no performance specs) for CAD

1FMS / Volume / License Server na 2.5GHz+ 2 4 GB 324 TB 1200

Windows 2003 Server SP2 or SP3,32bit or 64 bit, or for CAD files

1+n Dispather Server na 2.5GHz+ 2 8 GB 500 MB 75Windows 2003 Server SP2 or SP3,32bit or 64 bit

1+n TcC and TcU Web na 3GHz+ 2 4 GB 4 GB + 1200Windows 2003 Server SP2 or SP3,32bit or 64 bit

1 TcU Oracle 68 non-RAC na na 16 GB3 GB + (base) 1200

Solaris 10 or Linux SUSE with Oracle 10.2.0.1 or 11g

1 TcC MSSQL na 3GHz+ 2 4 GB 100 GB + 300Windows 2003 Enterprise Edition Server SP1, 64bit

1 TcC Conference na 3 GHz+ 2 4 GB Linux SUSE Enterprise Server (SLES) 9 SP2, SP3, and 10

900 4 Tier Rich Client na 3.4 GHz na4GB

w/NX 150-250GB 900 XP Pro SP2 32 or 64bit

300 Thin Client na na na 2-4GB 100 GB + 300XP Pro SP2, MS IE or Mozilla Firefox, Apple Safari

Deployment View

Prelim

inary

Page 28

Migration:TDM to TcUI-deas to NX

MigrateTDM

Phase III

Upgrade TcEng to TcU: Reuse Development and Test

UpgradeTcEng

Phase II

Deployment ViewPhased Benefits Plan

Timeline

Sol

utio

n C

apab

ility

Sta

ges

Foundation: Rapid return on OOTB

OOTBCapability

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

Page 29

Assumptions

CAD packages may have to be upgraded may delay the project Visualization will still have to be installed on all workstations

Page 30

Risks

Power in the computer room to host at FCC building Disk storage space for CAD file

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

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

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 < 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.

8. Is AutoCAD LT supported? No

Page 34

Tentative Roadmap (Fermi)

Thank You

Teamcenter Unified Architecture