140 likes | 376 Views
Teamcenter Global Deployment Options for India Collaboration. Margaret Kubitschek, Solution Architect Sam Brewster, Customer Delivery Manager Dennis Keating, Account Executive Siemens PLM Software 19 March 2010. Objectives Assumptions Options with Pros and Cons Risks Discussion.
E N D
Teamcenter Global Deployment Options for India Collaboration Margaret Kubitschek, Solution Architect Sam Brewster, Customer Delivery Manager Dennis Keating, Account Executive Siemens PLM Software 19 March 2010
Objectives Assumptions Options with Pros and Cons Risks Discussion Agenda
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 Objectives
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 Assumptions
Objectives: Phase 1: Features • Collaboration • NX CAD • Document Mgmt
Option 1: Teamcenter Community • 4 servers needed – 2 DEV, 2 PROD • May be able to leverage existing servers • Will deploy a new SharePoint instance
Option 1: Teamcenter Community • Cons • Not CM tool • No workflow • Business rules have to be setup • No NX integration • Manual translation for JT files • Pros • Less time to install • Easy to use • Collaboration site • Less hardware and software 2 days + 3 days + 10 days + 2 days + 3 days = 20 days Deployment Schedule Reference Only
Option 2: Teamcenter Unified • 4 servers (min) PROD; 1 server possible for DEV • 2 new servers needed (TBD); may be able to leverage existing servers
Option 2: Teamcenter Unified • 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 • Pros • Configuration Mgmt for NX CAD (OOTB) • Can setup one-step Release Process • Can translate CAD files • Begin to leverage 4 tier architecture 5 days + 5 days + 20 days + 5 days + 10 days = 45 days Deployment Schedule Reference Only
Option 3: Teamcenter Community and Unified • 7 servers (min) PROD; 4 DEV
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 Deployment Schedule Reference Only
Application Integrations • Recommend NX 6.x available at all current TcU releases
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) Risks
Teamcenter Global Deployment Options for • India Collaboration Thank You