Teamcenter System Architecture
Teamcenter System Architecture
Teamcenter System Architecture
Date: 7/25/2013
Readership:
Summary
Amendment History
Approval:
Table of Contents
Table of Contents is automatically generated. To update table based on changes in the document, select the table and hit F9.
1 OBJECTIVE........................................................................................................................................................................... 6
2 AUDIENCE............................................................................................................................................................................. 6
3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS..........................................................................................................6
4 NOTATIONS........................................................................................................................................................................... 7
5 INTRODUCTION.................................................................................................................................................................... 7
5.1 EXECUTIVE SUMMARY........................................................................................................................................................ 7
5.2 SOLUTION OVERVIEW......................................................................................................................................................... 8
5.3 DOCUMENT REFERENCES................................................................................................................................................... 9
TEAMCENTER STANDARD DESKTOP REQUIREMENTS........................................................................................................9
6 DESIGN OBJECTIVES........................................................................................................................................................ 10
6.1 SCOPE............................................................................................................................................................................ 10
6.2 BUSINESS REQUIREMENTS............................................................................................................................................... 10
6.3 CURRENT FUNCTIONALITY................................................................................................................................................ 10
6.4 NEW FUNCTIONALITY....................................................................................................................................................... 10
7 DESIGN DECISIONS AND CONSIDERATIONS.................................................................................................................10
7.1 DECISIONS...................................................................................................................................................................... 10
7.2 DEVIATIONS FROM THE HIGH-LEVEL DESIGN...................................................................................................................... 10
7.3 ASSUMPTIONS................................................................................................................................................................. 10
7.4 RISKS............................................................................................................................................................................. 10
7.5 SERVICE CLASS CONSIDERATIONS.................................................................................................................................... 11
8 DESIGN................................................................................................................................................................................ 11
8.1 PROCESS VIEW................................................................................................................................................................ 11
8.2 LOGICAL VIEW................................................................................................................................................................. 11
8.3 PHYSICAL VIEW............................................................................................................................................................... 13
8.3.1 Configuration management.................................................................................................................................... 14
8.3.2 Infrastructure.......................................................................................................................................................... 15
8.3.3 Storage.................................................................................................................................................................. 16
8.4 DEVELOPMENT VIEW........................................................................................................................................................ 16
8.5 SCENARIOS..................................................................................................................................................................... 16
8.6 SUMMARY SOLUTION DIAGRAM......................................................................................................................................... 16
9 DETAILED DESIGN............................................................................................................................................................. 16
9.1 DATA MODEL................................................................................................................................................................... 16
9.1.1 Data dictionary....................................................................................................................................................... 17
9.1.2 Data retention........................................................................................................................................................ 17
9.2 OBJECT MODEL............................................................................................................................................................... 18
9.3 SECURITY MODEL............................................................................................................................................................ 18
9.3.1 User Access........................................................................................................................................................... 18
9.3.2 Physical Access..................................................................................................................................................... 23
9.3.3 Data Security Components.................................................................................................................................... 23
9.4 TEAMCENTER – DETAIL.................................................................................................................................................... 23
9.4.1 Basic responsibilities.............................................................................................................................................. 23
9.4.2 Business rules........................................................................................................................................................ 23
9.4.3 Data sources.......................................................................................................................................................... 23
9.4.4 Sequence diagram................................................................................................................................................. 24
9.4.5 User interface......................................................................................................................................................... 24
9.4.6 Errors and exceptions............................................................................................................................................ 25
9.4.7 Logging.................................................................................................................................................................. 25
9.4.8 Business continuity................................................................................................................................................ 25
9.5 REPORTING..................................................................................................................................................................... 25
©2011 FERMILAB Doc Type: Template Version: 1.0 Practice:
For Internal Use Only DocDB- September
Doc ID: Effective Date:
5161 2013
Table of Contents-4
System Architecture Document
Teamcenter
9.5.1 User....................................................................................................................................................................... 25
9.5.2 Administrative........................................................................................................................................................ 25
10 PERFORMANCE AND VOLUME..................................................................................................................................... 26
10.1 PERFORMANCE EXPECTATIONS..................................................................................................................................... 26
10.1.1 Growth expectations........................................................................................................................................... 26
10.2 VOLUME AND LOAD EXPECTATIONS............................................................................................................................... 26
11 APPLICATION SUPPORT AND MONITORING..............................................................................................................26
11.1 SUPPORT FOR MONITORING.......................................................................................................................................... 26
11.2 SUPPORT FOR ALERTING.............................................................................................................................................. 26
12 OPERATIONAL REQUIREMENTS AND REPORTING...................................................................................................26
12.1 SERVICE LEVEL AGREEMENT (SLA).............................................................................................................................. 26
12.2 SUPPORT FOR METRICS............................................................................................................................................... 26
13 Appendix A – (not used at this time)................................................................................................................................. 27
1 Objective
This document provides a comprehensive and detailed architectural overview of the system, using a number of
different architectural views to depict different aspects of the system. It is intended to capture and convey the
significant architectural decisions that have been made on the system.
This section defines the role or purpose of the Architectural Design in the overall project documentation, and briefly
describes the structure of the document. The specific audiences for the document are identified, with an indication of
how they are expected to use the document.
The Detail Design begins with section 5, Introduction.
2 Audience
Identify the intended audience for this document. It should include the following groups:
Enterprise Architecture
Business Sponsor
Project Manager and Project Team
Build Team
Support Team
FMS – The File Management System manages uploading and downloading file data between clients and volumes in
both two-tier and four-tier architecture deployments. FMS provides volume servers for file management, a shared
server-level performance cache for shared data access between multiple users, a client-based private user cache for
rich clients, and a transient datastore mechanism for transporting reports, PLM XML, and other nonvolume data
between the enterprise and client tiers. FMS file caching enables placing the data close to the user, while maintaining
a central file volume and database store.
FSC – File Server Cache is a process that runs on a server host and performs as a volume server (when running on
a host where a volume is located or directly mounted) or a cache server (when running on a host where a volume is
not located or directly mounted) and a configuration server. As a volume or cache server, the FSC checks all file
access requests for a ticket that Teamcenter generates to authorize file access. As a cache server, it manages two
segment file caches, one for downloading files and one for uploading files.
J2EE – Java 2 Platform Enterprise Edition is a platform-independent, Java-centric environment from Sun for
developing, building and deploying Web-based enterprise applications online. The J2EE platform consists of a set of
services, APIs, and protocols that provide the functionality for developing multitiered, Web-based applications.
FCC - The FMS client cache (FCC) is the name of the FMS client cache server process. The FCC provides a private
user-level cache, just as Web browsers provide a read file cache. The FCC provides a high performance cache for
both downloaded and uploaded files.
Class - A class is the definition of an object implemented in the Teamcenter data model.
Primary type - A primary type is a default ImanType that directly corresponds to each POM
Class.
Subtype- Subtypes are all types except the primary type that belong to the same POM
class. Subtypes inherit all the properties and behavior of the primary type.
Property - A property is a piece of information that characterizes all objects of the same
type.
Method - A method is the execution of a message that is particular to that object type.
4 Notations
No additional notations are described here at this time.
5 Introduction
5.1 Executive summary
The business problem we are trying to solve is how to centralize engineering data into a small number of laboratory
locations. Existing engineering data is located in a wide array of locations and stored in many different data formats.
This creates difficulty in finding engineering data in a timely and efficient manner.
We plan on solving this issue by implementing a common Engineering Data Management System (EDMS) called
Teamcenter; the Teamcenter body of work is large and is broken down into a number of implementation phases. The
Teamcenter roadmap started in 2009 and plans to complete by 2016.
Teamcenter captures all elements of the approved Fermilab engineering process and the associated documents it
generates. This system, as envisioned, will connect and control engineering specifications, design analysis, CAD
drawings, safety documentation, and Quality Control reports in a central repository to allow for more efficient data
sharing across organizations.
The intention is for Teamcenter to automate standard engineering processes via workflow, and to provide a common
data repository for use by scientists, engineers, designers, technicians, manufacturing, procurement and quality
control personnel in order to improve the efficiency of the overall engineering process and production. Teamcenter is
envisioned to be engineering-document specific, and not a robust document management system for other laboratory
purposes (e.g., medical records, scientific records, etc.).
Items 1 through 9 below are required inputs to the High Level Design
Teamcenter https://sharepoint.fnal.gov/project/T
Standard eamCenter/Shared
Tony Metz
2. Requirements Document Desktop Documents/Desktop
Requirements Install/TeamcenterStandardDesktopI
nstallRequirements.docx
https://sharepoint.fnal.gov/project/T
eamCenter/Shared
3. Functional Design Functional Design Margaret Documents/Alignment/Alignment
Specification Specification Kubitschek Documents/209816_Fermi
Tc_Functional_Design_Specification
_v1.0.docx
https://sharepoint.fnal.gov/project/T
Margaret eamCenter/Shared
Test Cases for TcUA Kubitschek Documents/Testing/Final Production
4. Use Cases
Workflow Testing/209816_Fermi_Phase-1 Test
Cases TcUA Workflow v1.2 Aug
26,2011-New
https://sharepoint.fnal.gov/project/T
eamCenter/Shared
Mercury Marine
5. Case Study Mercury Marine Documents/Community/Mercury
case study Marine
Information/SiemensCaseStudy.pdf
https://sharepoint.fnal.gov/project/T
eamCenter/Shared
Documents/Alignment/Alignment
Alignment Margaret
6. Alignment Specification Documents/209816_Fermi
Specification Kubitschek Tc_Alignment_Specification_v2.1_Fer
mi_Modifications-Siemens
Response.docx
Teamcenter Risk
7. Teamcenter Risk Register Tony Metz Teamcenter Risk Register
Register
10.
11.
6 Design Objectives
Teamcenter is a commercial application with a proprietary schema. This document will cover the additions made to
the Out Of The Box (OOTB) schema and configuration.
6.1 Scope
The scope of this detail design will cover the enhancements made to the OOTB software.
7.3 Assumptions
No assumptions have been documented from the high level design.
7.4 Risks
See risk register for description of Teamcenter service implementation risks
8 Design
Users create and store data for later retrieval. Users have either Author or Consumer rights. Authors can create and
manipulate data and Consumers can read that data.
The Teamcenter service uses a number of workflow processes to apply status to a document or set of documents.
This document will display the two main workflow processes; the FNAL review workflow and the FNAL approve
workflow. Additional workflow processes will be added during the next review of this system architecture document.
The Rich Client, a Java-based client, provides access to all Teamcenter features and functions. A lightweight FCC
process executes on the users’ workstation. The Web Application, Business Logic and Resources layers execute on
separate systems. The Web Application Server being used is Weblogic. The resource layer includes an Oracle
database and data file services. The enterprise tier comprises a configurable pool of Teamcenter C++ server
processes (tcserver), and a server manager that manages the pool of the tcserver processes.
The http server is deployed as an integral component of the Teamcenter web tier as shown in Figure3. This is a fully
J2EE compliant Web Application Server (WAS) with support for UNIX and Windows platforms including Weblogic.
The J2EE web-tier correctly manages the sessions between http rich clients and the pool of tcserver processes.
Clients communicate with the J2EE server via http; the J2EE server communicates with the tcserver pools via
CORBA (IIOP).
minimum of 4 GB of RAM. The minimum network connection for Teamcenter clients is 100 MB with all the servers
having a connection of 1 GB. The files are stored on BlueArc in one Teamcenter volume. Teamcenter connects to
the Oracle 11G database on tcora10p which is running RHEL version 5.5.
The Teamcenter Web Application Server (WAS) tcweb01p is running Weblogic 10.3 and servers up the Teamcenter
Single Sign On (SSO) which connects to the LDAP Authentification services. The workstations tcapp04p, tcapp05p
and tcapp06p are Content Migration Manager (CMM) computers to convert Ideas data stored in Team Data Manager
(TDM) to NX data stored in Teamcenter.
server they are on are stored in Harvest under the UNIQUE folder in a sub-folder named for the server they are on.
Changes are processed as packages through the following default states in Harvest:
Development
Test/QA Review
Apply to Test/QA
Production Review
Apply to Production
Release to Production
8.3.2 Infrastructure
Infrastructure is the combination of servers, networking, devices and other hardware applications that are needed for
the Teamcenter service to operate. The following sub-bullets describe these infrastructure components.
8.3.2.1 Servers
Corporate Teamcenter Server - 4 CPU’s, 48 GB RAM, 160 GB Hard Disk Space (50 GB free space for temp files)
8.3.2.2 Network
The minimum network connection for Teamcenter clients is 100 MB with all the Teamcenter servers having a
connection of 1 GB. The recommended connection is 1 GB for clients and multiple 1 GB connections for servers. For
optimal performance, Siemens PLM Software recommends that Teamcenter application servers reside on the same
Gbit LAN as the database server.
8.3.2.3 Devices
The devices that are part of the application are desktop computers and laptops. Different client installation scripts are
required depending on the Operating System. The Teamcenter clients need to be running Windows 7 32-bit with a
minimum of 4 GB of RAM and clients running Windows 7 64-bit need a minimum of 8 GB of RAM.
A single user 32 bit Rich Client workstation configured in 4-tier mode should be equipped with a SPECint_rate2006
value of at least 17.6 to provide some excess capacity, again without regard to other applications.
8.3.3 Storage
The storage requirement for the Teamcenter on the application server is 6.0 GB for the application. An additional 50
GB of free space is required for Temp space for smooth running of Pool Manager. The volume requirements for
Teamcenter depend on the amount of CAD data. Currently, we are utilizing space under the threshold limit of 1 TB.
We have additional space allocated that can be added to a total of 4 TB. The volume data is currently stored on a
NAS cluster ITNAS-A-1 which is a BlueArc Titan 3210.
8.5 Scenarios
Scenario use case views of the Teamcenter service will be created during the next review of this document.
9 Detailed Design
9.1 Data model
The Teamcenter persistent object manager (POM) defines the architecture (schema)
using classes and business objects:
• Classes - The persistent representations of the schema. Classes can be seen in the Classes view
of the Business Modeler IDE.
• Business objects - The logical representations of the classes, also known as types. Business
objects can be seen in the Business Objects view of the Business Modeler IDE. Each class is
mapped to a primary business object whose name is the same as the Class name.
A primary business object corresponds to each POM class, and the primary business
object name is the same as the POM class name. The primary business object uses
its corresponding POM class to store its data.
Access Description
Privilege
Delete (D) Allows you to completely and permanently remove an object from the database. Because this is
potentially destructive, delete privilege is generally granted only to the owner and Teamcenter
administrators.
Change (C) Allows you to modify object protections. Any accessor with change privilege can grant themselves
any other privilege; therefore, change privilege must be tightly controlled. For example, you must
not allow another group to have change privileges to data belonging to your group.
Copy (c) Allows you to print objects, save objects as new objects, and mark objects for archive.
Export (X) Allows you to export objects from the Teamcenter database.
Transfer-out (x) Allows you to transfer ownership of objects exported from your database.
Transfer-in (i) Allows you to become the new owner of objects imported in to the Teamcenter database.
Publish Allows you to grant or restrict publishing privileges for users or groups.
Custom acc
Privileges
Columns A B C D E F G H I J K
FNAL FNAL FNAL FNAL FNAL FNAL FNAL FNAL FNAL FNAL
Data Type: Draftsmen Designers Engineers Technicians Welders Machinists Admin Purchasing Scientists TM/CC
-Progress)
Drawings
(Approved) R-W-M R-W-M-A R-W-M-A R R R R R R-W
FEA Results
(Preliminary) R-W-M R-W-M-A R-W-M-A R NONE NONE R NONE R-W
FEA Results
(Final) R-W-M R-W-M-A R-W-M-A R NONE NONE R R R-W
Calculations
(public) R-W-M R-W-M-A R-W-M-A R NONE NONE R R R-W
Calculations
(non-public) R R-W-M-A R-W-M-A R NONE NONE R NONE R-W
Specifications
(Draft) R-W-M R-W-M-A R-W-M-A R NONE NONE R R R-W
Specifications
(Final) R-W-M R-W-M-A R-W-M-A R R R R R R-W
Cost
Estimates
(Preliminary) R-W-M R-W-M-A R-W-M-A R NONE NONE R NONE R-W
Cost
Estimates
(BOE - Final) R-W-M R-W-M-A R-W-M-A R NONE NONE R R R-W
Columns
A L M N O P Q R S T U
FNA FNAL
L FNAL FNAL Sub-
ESH Computi Projec Projec Non- Non- Non- Non-
FNAL Spec ng t t FNAL FNAL FNAL FNAL FNAL
Draft ialis Professi Mana Mana Manage Drafts Desig Engin Technic
Data Type: smen ts onals gers gers ment men ners eers ians
R-W-
Parts M R-A R-A R R R R-W-A R
R-W-
Assemblies M R-A R-A R R R R-W-A R
Drawings R-W-
(Approved) M R-A R-A R R R R-W-A R
FEA Results
(Preliminary R-W-
) M R-A R-A R R R R-W-A NONE
Calculations R-W-
(public) M R-A R-A R R R R-W-A R
Calculations
(non-public) R R-A R-A R R R R-W-A NONE
Specificatio R-W-
ns (Draft) M R-A R-A R R R R-W-A NONE
Cost
Estimates R-W- R-W- R-W-
(BOE - Final) M M-A M-A R n/a R R-W-A NONE
Columns
A V W X Y Z AA AB AC AD AE
Non-
Non- Non- FNAL
Non- Non- FNA Non- Non- Revie FNAL Sub-
FNAL FNAL FNAL L FNAL FNAL w Project Project
Draft Weld Machini Adm Purchas Scienti Vend Panel Manag Manag
Data Type: smen ers sts in ing sts ors s ers ers
R-W-
Parts M R R R R R-W R R R-A R-A
R-W-
Assemblies M R R R R R-W R R R-A R-A
Drawings R-W-
(Approved) M R R R R R-W R R R-A R-A
FEA Results
(Preliminary R-W- NON
) M NONE NONE E NONE R-W NONE R R-A R-A
Calculations R-W-
(public) M NONE NONE R R R-W R R R-A R-A
Calculations NON
(non-public) R NONE NONE E NONE R-W NONE R R-A R-A
ns (Draft) M E
Cost
Estimates
(Preliminary R-W- NON R-W- R-W-
) M NONE NONE E NONE R-W NONE R M-A M-A
Cost
Estimates R-W- R-W- R-W-
(BOE - Final) M NONE NONE R R R-W NONE R M-A M-A
The rich client interface is used by authors, manufacturing authors, administrators, and other users to:
The Business Modeler IDE is used by administrators to customize the Teamcenter data model.
Client for Office allows you to access Teamcenter directly through Microsoft Office Word, Excel, PowerPoint, and
Outlook.
The login mechanism uses SSO (Single Sign On) which allows users to log in using their Services account and
password.
N/A
9.4.7 Logging
The log entries will be placed in a file called RTEvents.txt located on Teamcenter server TCAPP01P in the directory
C:\Siemens\tc83\pool_manager\logs\MLD\process.
The elements on each line of the resulting log file are:
‘INFO’
A UTC date-timestamp in format ‘yyyy/MM/dd-HH:mm:ss,SSS UTC’.
{machine-name}
The Java class where instrumentation is implemented.
The name of the instrumented action.
The type of filter being logged.
The response time statistics.
9.5 Reporting
Teamcenter Service does not create any formal reports at this time. This section will be reviewed and updated when
formal reporting is required.
9.5.1 User
N/A
9.5.2 Administrative
N/A