tc plm overview v4 070710

8/12/2019 TC PLM Overview v4 070710

1/14

Introduction

Engineering Manual/Process

Views of Teamcenter

Strategy

Process

Current Status

Summary

1

Teamcenter: Engineering Data Management System

Agenda

Rich Stanek

On behalf of the Teamcenter Implementation Team


2/14

2

What is Teamcenter? Software tool to help us do our jobs better Commercial Product !ifecycle Management "P!M# software "Siemens#

Document and Process centric relational data$ase "%racle# &sed $y many large internationally $ased manufacturing com'anies Also used $y DES( for t)e *+E! 'ro,ect "TC Enter'rise# CE-. study on EDMS identified TC as u'grade to t)eir 'resent system

Who will it affect? !a$s tec)nical 'rocurement and fa$rication staff

Scientists engineers designers tec)nicians mac)inists 0C

ES12 1 Procurement 'ersonnel Mec)anical electrical and ci3il disci'lines

&sed for 'ro,ects and for internal engineering data Allow access for Colla$orators "'ro,ect4related eng5 documents#

Introduction


3/14

3

Product Lifecycle Management

Product Lifecycle Management (PLM) isthe process of managing the entirelifecycle of a component and its associated

data from conception, through design andmanufacture, to service and maintenance,and finally disposal.

provides an engineering informationbacbone for companies and theire!tended enterprise.


4/14

4

What type of documents will be stored in Teamcenter? +ocus on engineeringdocuments and data

CAD files s'ecifications re6uirements documents engineering

calculations 1 analysis safety documents 0C re'orts 3endor data555

Will this be our only Document Management System? No5 !a$ is also 'ursuing S)arePoint as a more general DMS Teamcenter will $e integrated wit) S)arePoint T)ere may $e a few ot)er systems t)at will $e integrated as well

7oal is one common access 'oint for documents8one sto' s)o''ing9

Introduction "contd#


5/14

5

What problems are we trying to solve?

!ac of a common EDMSMany DocD; instances and ad )oc systems Maes colla$oration "e3en $etween Di3isions# difficult

CAD files are dis,ointed mec)anical electrical ci3il all )andled differently

2ard to find information engineering re'orts analysis on 're3ious designs< 8-ein3ent t)e w)eel9 far too often

!oss of data/information w)en 'eo'le retire or mo3e to anot)er 'ro,ect

-e3iews and Signoffs re6uire a manual 'rocess %ften wit)out full information a3aila$le to t)e a''ro3er



6/14

6

Why did we choose Teamcenter? Started off wit)in t)e CAD Tools Committee as a means to re'lace our

mec)anical CAD "I4deas# TDM)as grown into somet)ing muc) $igger

.eeded software t)at could )andle all of our common file formats .* AutoCAD MS %ffice 'df =T as well as a 3ariety of ECAD formats

>anted a system wit) a 'ro3en trac record t)at )ad all t)e ca'a$ilities Minimi?e customi?ation to limit 'ro$lems wit) u'dates

>ere a$le to 8'artner9 wit) Siemens to create an afforda$le solution



7/14

7

Engineering Manual

Archiving and Control (page 30)

In the future, ermilab !ill implement a lab"!i#e $lectronic %ocument &ana'ement S()tem

*$%&S+ Thi) !ill pro-i#e a central location an#common metho# for #ocument )tora'e, #ocumenti#entification, !orkflo!, confi'uration control,chan'e mana'ement an# #ocument retrie-al.

The future is now and the EDMS is Teamcenter


8/14

/

Engineering Process 1 Teamcenter

Teamcenter " $%&0


9/14

%rgani?ational View


10/14

1

% %T &$&$T, uto%%ra!in' 8 3%

$SS OTRO9Information Securit(

IT$RT$% :IS;9Iuire#

O99?ORTIOShare %ocument),

onference

?O& &$&$T%e)i'n Re"u)e

:ariant) = Option)

R$9$S$ &$&$T$n'ineerin' Relea)e 0roce))

Teamcenter

Sin'le Source of 0ro#uct %ata

&S Office

Inte'ration

+unctional View


11/14

Core Team and Steering Committee Mem$ers

11

Division/Section Core Team Members Steering Committee Members

CD

Bob AndreeTony MetzScott Nolan/Julie TrumboNelly StanfeldSimon KwanBill Borosi

Rich KaruhnTony MetzBob Tschirhart

TDJames BlowersTom Nicol

Dave Harding

AD ! Mec"anicalTony #arer

Salman Tari$

Paul Czarapata

AD ! %lectrical &ic" Divelbiss

AD ' Cryo(enicsAle) Martinez#"il #*und +sa*ety,

##D ' Mec"anical Dave #us"a Peter ilson

##D ! %lectrical Marcus -arwill

%S. Jody 0ederwitzCindy &o(ers

Directorate &ic" Stane1 Kathryn !rim "PR# Rich Stane$

0%SS Jim Nie"o2 Randy %rtgiesen

Manu*acturin( %d a(ler

#ro3ect Mana(ement %laine McClusey

4nte(ration #artner Siemens


12/14

?e'in 9ab tran)ition ofI%ea) to

*&echanical %+


13/14

13

Core Team has met a few times Still in 8disco3ery ')ase9

>ill start to $rea into smaller >oring 7rou's .eed to understand

2ow engineering data is currently )andled in eac) grou' Systems/software t)at are in 'lace and s)ould $e continued

Meeting with India abs! representatives >or on details of )ow 'ilot 'ro,ect system can $e configured &nderstand infrastructure limitations

Initiating contract for consulting services for final system

>ill use 8industry $est 'ractices9 to )el' esta$lis) data sc)ema "uilding up hardware architecture

&tili?e e@isting infrastructure as well as new )ardware 'urc)ase 2ig) a3aila$ility scala$le redundancy

Wor#ing with the Share$oint Team to assure smooth integration

Current Status


14/14

14

Teamcenter will be the ab!s %DMS

2a3e a 'lan for )ow to 'roceed Purc)ased t)e re6uired software licenses Esta$lis)ed 'rogram ')ases

C)arter/-oadma' will guide im'lementation 'rocess This program has

Directors su''ort +unding for )ardware software licenses and consulting Team is forming to align and im'lement t)e software

Strong re'resentation from around t)e !a$

Needed for success Commitment from D/S/C and De'artment 2eads Acce'tance from t)e engineering and tec)nical staff -esources for training data migration and testing

Summary

tc plm overview v4 070710

Documents