NEX - Teamcenter Superuser Course Presentation - v06 PDF

Teamcenter Superuser
15.05.2017, 16.05.2017, 29.05.2017

Digitread AS
4500
LICENSES
20
EMPLOYEES
Sandvika
125
CUSTOMERS
Digitread Confidential - Use of this information is restricted by the Statement of Confidentiality. The information provided by Digitread and/or
Siemens is strictly confidential and is supplied on the understanding that it will be held confidentially and not disclosed to third parties.
Denne presentasjonen er Digitread copyright.
Materialet er kun til privat bruk som notat fra deltatt kurs. Skal ikke
brukes til opplæring eller kommersielt bruk.
This presentation is copyright to Digitread.

The material is only for private use as notes from
participated course and shall not be used for training
or commercial use.
Digitread Confidential - Use of this information is restricted by the Statement of Confidentiality. The information provided
by Digitread and/or Siemens is strictly confidential and is supplied on the understanding that it will be held confidentially
and not disclosed to third parties.
Introduction round
• Name
• Work responsibilities and
experience
• Former experience with PLM
Expectations
What do you expect to gain from attending this course?

Take a couple of minutes to write down at least 2 things you
want to learn from this course.
Agenda (Super User) Introduction
Crash course in Teamcenter Rich Client
Change Management (intro)
Schedule Management (intro)
Requirements (intro)
Introduction to administration
Teamcenter Infrastructure
Teamcenter Data Model
Organization
Queries
Preferences
Access Manager
Projects
Workflow administration
Practical Administration
Plan for the day
Start at 09:00
End at 15:00 – 16:00
10 minutes break every hour
Lunch from 11:30 – 12:15
INTRODUCTION
Teamcenter superuser course
INTRODUCTION TO PLM
Todays challenges
Finding information Information flow Information quality Complex products
• Where can I find the documentation related to this part?

• In what assemblies is this part used?
• I need to find all the PDF documents we have created regarding Project 123.
Engineer 1
Purchase
Engineer 2
Production
Quality
Project Manager Economy
Supplier
• Is this the latest version of this document?

• Is this part approved and ready to be produced?
• Is this document finished?
• Is the assembly ready to be sent to the customer?
1960 2010
3 000 200 000
How many components?
Drawing
Marketing Drawing Drawing
Sheet A
GD&T Pictures Sheet A Sheet A
Product
Vision Assembly
Model Site A
Assembly
Instructions Drawing
What happens
Engineering
if I Process
Sheets
change Reports
this? Facets
Assembly
Model
Tool Paths Drawing
GD&T
Structural
Drawing
Simulation Facets Tooling
Assembly
Motion
Simulation Drawing Solid
Model Tooling
Solid Machinery
Models
Model
Facets User Defined Standard
Solid Parts
Features
Material Model
Facets Digitread Confidential - Use of this information is restricted by the Statement of Confidentiality. The information provided
bySpecs
Digitread and/or Siemens is strictly confidential and is supplied on the understanding that it will be held confidentially
Site B
Current situation at Nexans
Difficult to find correct

information
Can’t trust the data found
Creating duplicate data

How to implement Teamcenter in the
Re-usability: 70 – 80% best possible way, in order to solve the
described issues?
Master model principle
Projects
Assembly Documents
Master Model
Drawings CAE
Renderings
Teamcenter
CR
Teamcenter
Engineer 1
Purchasing Engineer 2
Project
Manager Quality
Production
Economy
Supplier
Teamcenter clients
Office Client
Active
Workspace
Rich Client
Inventor integration
Active workspace
NX integration
Active Workspace
Digitread Support
21.4.2017
How to contact Digitread Support
digitread.com/support/
Manned telephone support (workdays 08:00 – 16:00)
Monitored email support Remote assistance using
Remote Desktop and a Virtual Private Network where available
How support cases are processed
If you call us:

• We will do our best to help solve your issues per phone. If necessary we will connect to your
machine with TeamViewer.
• If we are not able to solve the issue in the initial phone call you will receive a mail with a Ticket
ID. This ID will be used to track the call from here on.
If you send us a mail:

• When you contact Digitread Support per mail you will always receive an answer with a Ticket ID.
• All written communication for each case will go through the Ticket IDs.
• If you have any questions about the status of a support case -> Reply to the Ticket ID. (Please do not change
the subject in the mail)
What should be included when creating a new Ticket ID
The more information we receive when the Ticket ID is created the faster the case will be solved.
- Always include the following

• A detailed description of the issue
• A relevant title
• Which application and command the issue is related to
• Steps to reproduce the issue (preferably using printscreens or/and video)
• Version of the software the issue occurs in
• Other information you think may be relevant (the more information the better)
- Always include the following information when applicable

• Log files
• If this is a file specific issue, include the relevant files (Part files, xml, xlsx, etc)
Note: Please keep cases separated. Don’t list several issues in one Ticket ID unless they are very closely
related.
Incident Report (IR)
From GTAC:
Every contact with GTAC is regarded as an Incident Report (IR). GTAC logs this as an IR and assigns an IR-number in the GTAC support handling system
TAC (Technical Access Center). Only one issue should be reported per IR. If a customer has multiple issues to report then it is expected and more
beneficial to open multiple IR’s
When we contact GTAC we always create an Incident Report. We will update the customer as soon as we
hear back from GTAC. We will also inform you if the IR has been converted into a PR or an ER.
Problem Reports (PR)
From GTAC:
Problem Report - PR: The software delivers wrong result, hangs, or in other ways behaves incorrectly
PRs report software defects verified by GTAC and these are always investigated by Development and closed with an official response, whether it is fixed
or determined to be user error/not reproducible. This is part of the maintenance agreement to provide solutions to software defects.
When a case is registered as a PR it is closed from Digitread’s side, but we will provide an update to the
customer when we hear back from GTAC. If you want an update in a case, reply to the Ticket ID and we
can ask GTAC for a status update.
Enhancement Requests (ER)
From GTAC:
Enhancement Request - ER: The software does not have the desired functionality
When an ER is raised there is no commitment to provide implementation of this and that is essentially the end of the loop for the vast majority of ERs. A response to
the ER should not be expected as this is only done if the ER is specifically implemented, then Development have the capability to advise the customer. Raising an ER
is purely a suggestion of what customer may wish to see in the software it is not a demand requiring a response like a PR is. Occasionally, for some smaller simpler
product areas such as CAD integrations the product manger will respond to all ERs but this is the exception rather than the rule.
The few ERs that get implemented are either those where it was already intended as part of the Development plan to implement, or any that have a significant
business critical advantage that usually have been escalated by an account manager.
When a case is registered as an ER it is closed from Digitread’s side, but we will provide an update to the
customer if we hear back from GTAC. If you want an update in a case, reply to the Ticket ID and we can ask
GTAC for a status update.
CRASH COURSE
TEAMCENTER RICH CLIENT
Crash course - Teamcenter Rich client
• User interface
• Applications
• Group/role
• Create folder
• Create Item
• Create Datasets
• Msword
• PDF
• Look at item in AWC
• Workflow/status
• Save As/Revise
• Structure manager
• Rev rules
• Datapanel
• BOM Report
Home Page
RAC Home Page
Finding Information
The Teamcenter search functionality lets you find data in Teamcenter to view or update. Use the
simple search box when you know the item identifier, name, or a keyword. Filters allow you to limit
your search results.
Finding Information
Active Workspace: Searches in indexed SOLR database: only contains “selective data”
Rich Client – Advanced Search
Searches in Teamcenter Database.

All data available
Can create custom Admin searches
Item
• Item is the typical storage container

in Teamcenter.
• It stores data and information
associated with your product.
• Upon creation of an Item, an
ItemRevision is automatically
created within it.
Item revision
• An Item will contain at least

one Item Revision
• Item Revisions are used to
manage different stages of
the product.
Item revision
Clevis
Clevis /A
Clevis /B
Item revision N
Need to decrease
the hole size
Item types
GENERAL TERM AT NEXANS
ITEM DESIGN DOCUMENT REQUIREMENTS PR, ECR, ECN
REVISION A REVISION A REVISION A REVISION A REVISION A

REVISION B REVISION B REVISION B REVISION B REVISION B
REVISION X REVISION X REVISION X REVISION X REVISION X
• CAD files • Documents related to a • Customer Requirements • Change Management:

• Solid Edge, inventor project • Broken down • PR (Problem Report)
• Created from the • ECR (Engineering Change Request)
respective CAD program • ECN (Engineering Change Notice)
Create Item
Exercise
• Create Item in Rich Client

• Open Active Workspace and find your Item
Attachments (Datasets)
Clevis
Clevis /A
3D model /A
Clevis /B
3D model /B
Text document /B
Need to decrease Item revision N

the hole size
3D model /N
Text document /N
Attachments in Active Workspace
• Attachments are available from a separate tab

• If you have added a pdf as an attachment, a new «PDF» tab will be available, previewing the pdf.
Datasets (attachments) in Rich Client
• File – New – Dataset

• Ctrl + D
• Drag n Drop (to Revision!!)
Data model
Database Volume
Clevis
Clevis /A
3D model /A Clevis.prt
Clevis /B
3D model /B Clevis.prt
Text document /B Specification.docx
Exercise dataset
• Create Word Dataset in Rich Client in the Project Doc

Revision from previous exercise
• Open word doc in Office Client from Active Workspace.
Save and check in. See that PDF is generated.
Mini test
1. What is the difference between Item and Item Revision?

2. What is a dataset used for?
Answers:
1. Item is a information container for the product, while Item Revision is a
information container for a phase in the development process.
2. Datasets are containers for files outside the Teamcenter environment. They will
open in the associated program.
Properties
• Properties are information that defines

the product.
• Properties on an Item defines the entire
product.
• Properties on the revision defines the
specific revision.
• Some properties are automatically filled
in, e.g. date created and owning user
• It is possible to create custom properties
(System Administrator)
CHECK-IN AND CHECK-OUT
Protect and access data
Check-out and Check-in basics
You can check objects into and out of the

Teamcenter database, reserving exclusive access
and preventing the data from being modified by
other users.
• The Check-Out option locks an object in the database so that only you can modify it.
• The Check-In option releases the lock, allowing other users to access the object.
• Only your administrator can circumvent the security that the checkout function provides.
A checkout is either explicit or implicit.
• Explicit checkout occurs when you use a menu command or button to check out an
object. You must then choose to check in the object when you are finished with your
modifications.
• Implicit checkout occurs when you double-click to open a dataset. Implicit

checkout only occurs if the object is not already checked out. Checkin occurs
automatically when you close the document.
The following objects can be checked into and out of the database:
• Items and item revisions
• Datasets
• Forms
• BOM views and BOM view revisions
Check in / Check out
DBA role can override checkout. All unsaved work is lost
Relations
Relations shows how the objects are

associated to each other. By using relations
you can easily see where the objects are
used and referenced.
Impact analysis
Where referenced
Where used (assemblies)
Impact analysis
Where referenced
Where used (assemblies)
WORKFLOWS
Business process
• Workflow is the automation of business

processes to accomplish an objective.
• A workflow process is initiated by a user
by submitting an item to the workflow.
• Workflow tasks, such as approvals
(signoffs), reviews, and assignments to
complete work, are assigned to users.
CREATE/UPDATE
START REVIEW PRODUCT REVIEW RELEASE
PRODUCT
Teamcenter RapidStart workflows
• The first step is to generate the data needed.

CREATE DATA
Example: Document, 3D model, excel sheet etc.
30 DEVELOPMENT • The 30 Development release is an internal review, providing the data with status
RELEASE 30.
60 PRODUCTION • The 60 Production release gives the data status 60, which indicates that this is
RELEASE ready for production.
90 OBSOLECENCE • When data is replaced or not valid, it is given the status 90, which indicates that it
RELEASE is obsolete.
ENGINEERING • A Workflow when performing changes on data after PPOP state. Manager needs
ORDER to approve the change before the actual work is performed.
Neuman’s workflows
CREATE DATA
Rejected
30 DEVELOPMENT Approved 30 DEVELOPMENT

START SELF REVIEW CHECKER REVIEW
RELEASE RELEASE
60 PRODUCTION
RELEASE
90 OBSOLECENCE
RELEASE
Neuman’s workflows
CREATE DATA
30 DEVELOPMENT 30 DEVELOPMENT
RELEASE RELEASE
60 PRODUCTION 60 PRODUCTION
RELEASE RELEASE
90 OBSOLECENCE 90 OBSOLECENCE
RELEASE RELEASE
States of release
Data in the system can be in one of three life cycle

states:
• WORKING (empty value)
If the item revision has no value for status, it is
working data, meaning that someone is working on
the data contained in the item revision.
• IN-PROCESS
The object is in a workflow process.
• STATUSED
Data stored with item revisions that have obtained
this status are considered production data.
The data is generally in a write-protected mode,
meaning it cannot be changed unless a new revision
letter is created.
Workflow
Workflow
Inbox / My Worklist
Workflow – Task View
Workflow – Process View
Workflow – Select Signoff team – Perform Signoff
Release status – in process
Release status
• 30 – Development Release
• 60 – Production Release
• 90 – Obsolete
Exercise
• Send your Project Document to workflow «60 – Production Release»

• Send it to another person in the training room for «Checker Review»
Revise or Save As
• You can revise or duplicate data

from Active Workspace, by
clicking the ”Save As or Revise”
button.
• The dialog box has two tabs –
”Revision” and ”New”
• By selecting project first, the
newly created data can be added
to another project
• Duplicated data will be stored in
you ”Newstuff” folder
Revise or Save As
• Select Revision
– File – Revise
– File – Save As
Exercise
• Revise your Item

• See that Word document is copied to Revision B
• Is the PDF copied?
Visualization
Use the Viewer to find the

parts you are looking for
using the list/table with
Summary option.
Structure Manager data panel
Structure Manager data

panel assembles all single
JT files into an assembly
Structure Manager data panel
Structure Manager data

panel assembles all single
JT files into an assembly
BOM Reports
Select top level of assembly

– Generate Report
BOM Reports
Excel or HTML format
Select Revision Rule
exercise
• Search for item Revision ?????????????/A

• Open BOMView in Structure Manager
• Open Datapanel to see visualization data
• Generate BOM Report
REVISION RULES
Revision Rules
Revision rules is used to define how the

product structure is displayed (in which
state).
Default:
Latest working
Precise BOM structure
Rev. A
– Static structure
– Locked to the state it was when B A
C
released
– Locked to specific Revisions
D A B A
Rev. B
– To revise a component, all sub

assemblies and assemblies above,
D B A
must also be revised
– Then the assembly, sub-assemblies
and components can be released in
its new condition E A B A
– Possible to have track of how
component were produced at a
certain time.
Rev. A
– Static structure
– Locked to the state it was when B A
C
released
D A B A
Status = Released
Imprecise and Precise BOM
Imprecise BOM
• Dynamic structure of item revisions.
• Allow you to configure the BOM according to the revision rule you choose in structure
manager
• ItemID is locked, ItemRevisions change according to revision rule
• BOM will be automatically updated with newest revisions
• Typically used during development
Precise BOM
• Fixed structures of specific item revisions.
• To modify a child component to a new revision, you must revise the parent first to be
allowed to edit child component revision
• Manually update the assembly by replacing the old revision of the component and adding
the new revision.
• Typically used when releasing something for Production / Sendt to customer
Revision rules
When searching, you can select to between

revision rules.
Some examples:
– Latest Working
Display data in its latest state, regardless if it is
released or not
– Precise Only
Will only display a precise BOM structure of
assemblies (just released revisions)
– Any Status; Working

Will first show latest released Revision. If no
Released Revision exist it will show “Working”
Revision rules
Exercise
• Open 10002993/A in Structure Manager

• Change Revision Rules
– Latest Working
– Status 60
Change management
ENGINEERING ORDER
Engineering Order
- Engineering Order is change management in Teamcenter RapidStart (preconfigured

Teamcenter)
- Used for changes on items with production status (60)
- Engineering Order is a separate Item type in Teamcenter
- “Simple version” of Change Management (full feature in Teamcenter) but principles
are the same
CREATE THE START THE WORKFLOW

GET APPROVAL FROM
NEED FOR A CHANGE ENGINEERING ORDER PROCESS ON THE E.O. PERFORM THE CHANGES REVIEW THE WORK
MANAGER
ITEM ITEM REVISION
• Separate Item type • Separate Workflow process • The manager eiter approves • An user is selected to perform • A Checker Review is
• All data related to the change • The workflow initiator or rejects the change the actual work. performed to ensure the
is stored on this item describes the change. • The Engineering Order item • This could be another user quality of the work
• The work is done within the will be stored in both cases than the initiator or manager • This step is equal to the other
workflow workflows
Create Engineering Order item
Engineering Order is a separate Item With it’s own ID numbering Engineering Order is also a separate
type in Teamcenter EOXXXXXX Workflow template
Engineering Order Workflow
• The workflow initiator If the Change request is

completes the Change denied, the Engineering Order
Request form to describe the Item will still be stored with all
change of the information.
• If necessary, reference data is
added to 'Reference Data'
folder.
• Manager of the Project is • The Manager selects the Author • Select Reviewer Statuses are set
automatically assigned for this task, which: • The Manager selects the the design changes
• Review according to definition in
• Manager either rejects or • Completes the Engineeringchecker for this task, that:
as per change request the “Perform Change”
approves the Engineering Order Order form • Approves / Rejects change step
request with comments if
• Makes the necessary design
changes necessary.
Engineering Order tab
No status
60
60
90
No status
No status
Engineering Order Item
Exercises Engineering Order
1. Create an Engineering Order for an assembly. Change one ItemRevision with a new ItemRevision
2. Send it to Manager for «Manager approval»
3. Perform the change (Engineering Order) yourself
4. Send it to Checker for «Checker Review»
Engineering Order Workflow
1. What is the ID of the Engineering Order performed on Design Revision 1000163/A

2. Who signed off for the «checker review» for Design Revision 1000163/A
3. What is the Effectivity Date the Change Notice?
1. What is the ID of the Engineering Order performed on Design Revision 10002677/B

2. Who signed off for the «checker review» for Design Revision 10002677/B
3. What are the instructions for the Change Notice?
Tips:
Where referenced
Process history
Change Notice in viewer tab
Change Management
Change Management
Change Management
Change Management Roles
Change Management Workflow example
Change Management object status
SCHEDULE MANAGER
Schedule Management
Teamcenter enables product teams to

plan your programs in terms of their
schedules, work tasks, dependencies,
milestones, baselines and constraints
and then execute your projects in
accordance with these trackable
expectations.
• Create schedule
Schedule Management
• Add schedules from templates

or copy them from an existing
schedule
Schedule Management
• Manage schedule attributes
Schedule Management
• Add, modify, delete, and

manage dependencies of
tasks.
Schedule Management
Configure order of tasks using

traditional cut and paste functions.
Includes task planning and execution

properties, and workflow
assignments.
Schedule Management
• Task management
• Maintain task dependencies and

members.
Schedule Management
• Manage affected items for a

schedule task..
Gantt Diagram
In Teamcenter 11.2.3 you can now display and manage scheduled tasks as Gantt charts. You can
view, add, and delete tasks; indent and outdent tasks; create and delete dependencies; reassign
tasks; and edit task properties.
Tender schedule
Tender projects follow a schedule or list of actions. This needs to be created for a new project –
either from different templates and/or ad-hoc – to make sure the project progresses with the right
tasks.
• Team members need to be assigned to tasks if they are not by default from the template
• Deliverables needs to be added to the tasks if they are not by default from the template
• A lot of schedule specific tools are available in Schedule Manager in Teamcenter
A schedule consists of tasks in context of a time frame. This will allow the tender manager to set
due dates on the tender specific tasks.
Tender schedule
A schedule consists of tasks in context of a time frame. This will allow the tender manager to set
due dates on the tender specific tasks.
In Teamcenter, a schedule consists of tasks. These tasks are related to deliverables and the
responsible member(s). The tasks are progressed with the time dimension in combination with
workflows.
Schedule Management Features
Nested Schedules
Schedule Management Features
Membership
REQUIREMENTS
Requirements Management
Requirements perform the important role of speaking for the customer.

Requirements are how you know when:
- your done.
- your building the right thing.
- you’ve built it right.
Teamcenter Requirements ties the requiremnts to influence design as it happens.
Requirement Specifications
Requirement specifications are comprised of requirement and paragraphs and even

other specifications. You add content such as text or graphics to the requirement using
either a plain text editor, rich text editor, or Microsoft Word, depending on how your
administrator has configured the environment.
Active Workspace Requirements
Active Workspace Requirements allows you to:

- Compare requirement content via Word
- Static export to Excel
- Traceability
- Ties requirements together
Requirment - Architecture
Requirement - Commentary
Add Questions and

Answers to the
Requirements.
Requirement – Markup
Use the integrated

Markup tool in Active
Workspace to quick and
easy make comments
and edits.
Export to Excel & Word
Export your
Requirements directly
from AWC to Excel
or/and Word.
Requirements – Rich Client
• Import from Word

• Based on «Headings»
• Traceability Matrix
• Export to Excel
OFFICE INTEGRATION
Client for Office
• Gives you direct access to Teamcenter directly through Office programs

• Installs a custom ribbon
• Independent of Teamcenter client
Client for Office
• Save and edit Office documents

• Browse for Teamcenter objects
• Insert Teamcenter property value
• Subject documents to workflows
• Perform sign-offs
Creating
• File→New
• Save Local datasets to Teamcenter
Insert
Searching
• Simple search
• Advanced search
Teamcenter’s Extensions for Office
• Synchronous access
• Live Excel and Live Word
Organization
Queries
Preferences
Access Manager
Projects
Configuring Teamcenter
BMIDE Applications
Configuring the data model and Use Teamcenter applications to
business rules do administrative tasks
Business Modeler IDE (BMIDE)
• Configure the data model

• Use templates to deploy the data model
Teamcenter Applications
• Access Manager
• Command Suppression
• My Teamcenter
• Organization
• PLM XML Export Import
• Project
• Query Builder
• Report Builder
• Workflow designer
BMIDE configuration
• Item types
• Properties
• Rules (itemID, Revision ID)
• Active Workspace
Indexing/filtering
• List of values
• Add new document templates
• Requires admin knowledge to do

changes
– At the start:
• Consultancy/Operations
– Later:
• Teamcenter admin/owner
BMIDE configuration databook
• Data model configurations – important to keep updated
BMIDE configuration databook
• Data model configurations – important to keep updated
Teamcenter admin applications
• Options/Preferences
• Workflows
• Interface
• Reports
• Organization
• Access Manager
• Edit Document Templates
Tip
• Administrative users / Superusers

• Have both an engineer role and a dba role
• Default role as engineer, switch to dba when needed
Best practices
• Have one test database and one production database
• Many of the applications are capable of exporting and importing files that are already made.
• This way you can test on a test database and then import them into the production database
• For example:
• Create a workflow in TEST and when it is finished, import into PROD
• Create Search in TEST, import in PROD
• Document what has been done and why
TEAMCENTER INFRASTRUCTURE
Teamcenter Architecture
Teamcenter Architecture
• Two different type of architecture are available with Teamcenter

• 2-tier (Admin client on server)
• 4-tier (Rich Client, Active Workspace)
2-tier
• Client Tier:
• Rich client
• Teamcenter Server process
• Optional applications that integrates with rich client
• Resource Tier: Stores persistent metadata and files
• Database server and database
• Volumes
• File servers
4-tier
• Client Tier
• Web Tier
• Enterprise Tier
• Resource Tier
Client tier
• Client Applications
• Processes user interface input and output
• Host secure file caches
• Available clients include

• Rich client
• Office Client
• NX integration
• Active Workspace
Web Tier
• Web tier handles:

• client installs
• process logon requests
• routes client request to business logic
• communication between client and
enterprise tier
Enterprise Tier
• Enterprise tier hosts:

• Business logic
• Applies security rules
• Retrieves data from and
stores data in the database
• Serves dynamic content to
clients
• Composed of
• Shared binary executables
• Shared data directories and
files
• License server
• A pool of server processes
managed by a server
manager
Resource Tier
• Stores persistent metadata and files

managed by the environment
• Contains
• Database server and database
• Volumes
• File servers
File transfer (FMS/FCC/FSC)
• Teamcenter stores files on volumes (location on server)

• Files are transfered to and from volumes by FMS (File Managment System).
• On the client FCC (FMS client cache) is running and handles file transfers.
• FSC (FMS server cache) are running on the server and handles file transfers.
• FCC is communicating with FSC to transfer files to/from Teamcenter.
Server
TEAMCENTER INFRASTRUCTURE
Important folders
• C:\Siemens\Teamcenter\Tc11.2
• Where Teamcenter is installed. Also called %TC_ROOT%
• Common vaule: D:\Siemens\Teamcenter\Tc11.2
• X:\DATA\TCPROD\tcdata11
• database configuration settings: Do not modify
• C:\Siemens\Teamcenter\TC_TMP
• Temporary teamcenter files
• X:\DATA\tcprod\volume
• Where files (named reference on dataset) in Teamcenter are stored. Do not modify
Services running on server
• Depending on setup, not all services

need to be running on same server.
• SQL services
• File Master Service
• Handling file transfers from/to clients
and server
• Pool Manager
• Web service
• License service
Services
Important to notice:
• Log On As – user for the Teamcenter FSC service.
• This user is owner of files on volume!!
• This is set as the user installing Teamcenter on the
server
• Recommended that this is done by a domain
administrator user «infodba»
Ports and Services
Ports and Services
Client
CLIENT INSTALLATIONS
Important folders
• C:\Siemens\Teamcenter\Tc11.2
• Installation location
• C:\Siemens\Teamcenter\Tc11.2 \portal
• Program location. Portal.bat
• C:\Users\<userid>\Teamcenter\RAC
• Configuration files to make startup faster
• C:\Users\ \<userid>\FCCCache
• Cache folder for files (cad, msoffice, pdf…)
• No need to download again if latest version is available
• C:\Siemens\NX11.0
• NX installation
Installed programs – Control Panel
Control Panel\Programs\Programs and Features
Important windows environment variables
• FMS_HOME=C:\Siemens\Teamcenter\Tc11.2
• Teamcenter File Management System
• JRE64_HOME=C:\Siemens\Java\Jre1.8.0_66
• Teamcenter Java location
• SPLM_LICENSE_SERVER=28000@nrc-tc02
• NX License server
• UGII_BASE_DIR=C:\Siemens\NX11.0
• NX base folder
• UGII_PATH=V:\NX11config
• NX Shared environment
• Customer defaults
• Drawing templates
Client installation – map network drive
Client installation
Switch environments – TEST and PROD
Organization
Queries
Preferences
Access Manager
Projects
Teamcenter superuser course expextations
• Begrepsforståelse
• Arbeidsflyt I hele systemet
• Admin/config
• Hvordan systemet er skrudd sammen
• Støtte superbrukere
• Active Workspace vs RAC
• Hva gjør superbruker
• Config
• Tilganger Client/config
• Hva kan gjøres selv
TEAMCENTER DATA MODEL
• Updates are made in BMIDE

• Business Modeler Integrated Development Environment
• The data model defines Teamcenter objects

• Item types
• Properties
• Rules
• Relations
• List of values
• Examples
• Add extra property «Cut length» for ItemRevisions
• Add namingrule «DT123456» for Items
• Add naming rule «DOC123456» for Documents
• Add list of values for «colours»
• Green
• Red
• Blue
Can be updated via Live update:
Updating BMIDE template
LOVs
LOV attachments to properties
• Customer creates a custom template
Compound property rules
• NEX9_Nexans_config
Deep copy rules
• NEX9_ prefix to all custom objects Display rules
• Full Model Update Extension rules
• Deploy a new template GRM rules
• Update existing template ID context rules
• Requires downtime Naming rules
• Live update – «Hot deploy» Conditions
• Some things can be updated without downtime +++
• «non schema data»
Properties
• Can add custom properties

• String
• Integer/double
• LOV
• Compound properties
• Can «link» properties from
e.g. Project to ItemRevision
• Runtime property
• Can get input from custom
code
Rules
• Naming rules
• Hide Display rules
• Deep copy rules
Relations
• Specification – IMAN_specification
• Requirement – IMAN_requirement
• Manifestation – IMAN_manifestation
• Reference
• EO Checklist - RTN9_EOChecklist
• PDF_reference
• To differentiate from other reference relation
Relations
• The IMAN_specification business object defines this relation. Specification

• relations are detailed methods, designs, processes, and procedures used to satisfy
• requirements. A specification relationship can only be established with an
• item revision, not an item. Although requirements may remain fairly constant
• for a product (item), actual manufacturing methods, designs, processes, and
• procedures may change drastically from model to model (item revisions).
• The IMAN_requirement business object defines this relation. Requirement

• relations are criteria that must be satisfied by this item or item revision.
• However, requirements often do not specify how this criteria should be satisfied.
• For example, a requirements relation may specify maximum weight for an item
• revision but not how to construct it. Extend the business object to create your
• own specification relations.
Relations
• The IMAN_manifestation business object defines this relation. Manifestation

• relations are nondefining snapshots of a particular aspect of an item or item
• revision at a particular moment in time. For example, numerically controlled
• (NC) program files are a common manifestation. Consider that they represent
• one aspect of an item revision (that is, machining information) and that this
• information is only accurate as long as the item revision does not change. If
• the item revision does change, the NC program files may no longer be accurate
• and may need to be re-created.
• The IMAN_reference business object defines this relation. Reference relations

• describe a general nondefining relationship of a workspace object to an item or
• item revision. This relation type can be thought of as a miscellaneous relation
• type. Typical examples of reference relations are white
List of values - LOV
• LOV
• Dynamic
• Create new item type – e.g. CustomerItem
• Create CustomerItems in Teamcenter to populate LOV
• Querys database to create a list of all CustomerItems
• New in Tc10.1
• Not currently in use at Raufoss
• Classic
• Values are changed in BMIDE and must be deployed
via Live update or full model update
• Can be changed later…
Dynamic LOV
This feature was added in Teamcenter 10.1

and provides the ability for you to define
an LOV that will query Teamcenter product
data to build its list of values.
In this case the LOV values are not pre-
defined in a BMIDE template, only the LOV
query definition is pre-defined.
As an example the LOV can be configured
to build a list of Item IDs from Items that
are released.
When a user clicks on the LOV button in

the user client, the system will perform
the query and get the latest set of Item IDs
that are released from your product data.
As the list of released data changes over
time, the LOV stays in synch with this, thus
you will not need to take the system down
to update LOV values.
Conditions
• isTrue = happens every time

• RTN9_TeamDocRevision_Word = happens if property «Template = Word»
• All new document templates must
have a condition
IRDC – Item Revision Definition Configuration
Document Templates
• Used to create dataset automatically

• Word, excel, PPT templates
• Deliverable PAM Document Templates
LOVs and condition/IRDC listing for Deliverable PAM (work in progress…)
Global constants
• CreateDataWithNoActiveProgram = false
• Users must have selected project to be able to create data
– Will get error message if trying to create Revision with no active
project
Post-actions
• Things that happen when you perform an
action
• Save
• saveAs
• Create new
• …
• autoAssignToProject
• Revisions + datasets automatically assigned
to active project
• RTN9_msofficetopdf
• Create request to create automatic PDF
• (dispatcher)
ORGANIZATION
Organization
Organization Description
Person Individual
Person with Teamcenter
User
account(s)
Contains users with role(s) in
Group
the group
Have another group as parent,
and inherits access, volumes,
Subgroup
and preferences from their
parent.
•Data access is based on groups, roles and projects
Organization
• Sites
• Volumes
• Roles
• Groups
• Persons
• Users
Groups (Sites)
• Halden
• Oslo
• Paris ?
• Subgroups =
Departments?
Groups / Roles
• A user is usually member of 1 group

(+ dba group for superusers)
• A user can have many roles
Users
• Best way to create user is from what should be «Default Role»

• User id should be same as Active Directory name – e.g. «paulsefr» or «boiesd»
• Licensing level – Author, Consumer
Person
• Automatically created when creating User

• Only need to fill in email address
Tip
• Sub groups
• Inherits rights, volumes and preferencers from the parent group.
• Password
• Possible to have restrictions on user passwords. Length, lower and uppercase letters etc.
• Teamcenter Security Services will later be implemented.
• Active Directory manages passwords
Infodba
• System user with all system privilieges

• User with most power
• Bypass
Infodba
• Infodba is a special user in Teamcenter with more rights than normal users.
• Is used for administrative tasks only
• Can be used to bypass rules to fix access problems
Licensing information
• 1 license used per «active named user» in Teamcenter

• (not floating like NX)
• Users can be set «inactive» to release the license

• NB: License released 1. day of the next month after the user was last logged in
• If user logged in 1. apr, and user is set inactive 1.apr -> license released 1. may
• If user logged in 1. mar, and user is set inactive 1.apr -> license released 1. apr
• Author
• Can create data (items, datasets, workflows +++) and do «everything»
• Consumer
• Can NOT create data. Can be member in workflow
• Admin
• Infodba
• Dcproxy (dispatcher admin user)
Exercises Organization
• Create new user (if enough licenses…)

• Set Default group (not dba..) + Role to «Project»
• Set user inactive
• Fill in Email for your own «person»
COMMAND SUPPRESSION
• Used to hide menu options in Rich Client
• Not very big need for this because Active Workspace is main client for Raufoss
QUERY BUILDER DEFINITIONS
Query Builder
• Query definitions identify search criteria to find information in Teamcenter.

• Administrators defines queries for end users.
• Example queries:
• Find all folders named Home.
• Find all Items created by a specific user
• Find dataset of a specified type
• Find ProjectDocRevisions
• Find Engineering Order Revisions
• Find all objects in project XXX
Query Builder
• Creating queries requires knowledge of the Teamcenter Data Model.

• Tip: Create new queries based on existing
Possibilities
• Search on many attributes at the same time

• Default values
• Values that the user cannot see and change (hidden)
• Limit who can execute certain searches
• Create searches only for administrators
• Nested searches, e.g. find items where item revisions contains dataset of type pdf
• Import/Export searches
OPTIONS AND PREFERENCES
Preferences
• Configuration variables stored in the Teamcenter database.

• Allows configuration of many aspects, e.g:
• User interface
• Some preferences are created by users when doing something in Teamcenter, e.g:
• History is saved as preference
• Column width in Structure Manager
Preferences
• Preferences are configuration variables

• Edit->Options to view preferences
• Options: Limited set of preferences
• Index and search: Find preferences based on searching
• Organization: View preferences available to group, role, and user.
Preferences
• Users can change some of the preferences

• Reference: preferences_environment_variables.pdf
Preferences
• Examples:
• TC_Auto_Checkout
• TC_show_checkout_objects_on_exit
• HistoryTitleList
NX icon for users
• TC_show_open_in_nx_button
Location for preferences
• Site
• Everyone (admin preferences)
• Group
• NRC.Product and Process Engineering
• Role
• Team -> Team Role can only create «Team Documents»
• User
• mmoi
Best practices for preferences
• Check the documentation before modifying preferences.

• Do not modify the preferences without a good reason.
• Be aware that changing some preferences to ”wrong” values can have unintended effects.
ACCESS MANAGER
Protecting data
• Important to protect data in a distributed computing environment

• Objects must be protected from unauthorized access, deletion and modification.
• Data protection can be:

• Rules-based protection
• Object-based protection
• Focus on Rules-Based
Rules-based protection
• Administrators defines various conditions or rules to control who can access various objects
• Rules are defined in Access Manager and affects on site level.
Rules-based protection
• Controls access to objects (data)

• Defined by a condition with value and an access control list (ACL)
Access Control List
Rule tree
Access manager rule tree
Depth first search
ACL precedence
Object ACL
Important access definitions
• Bypass
• POM object (System objects)
• In Job (Workflow determines
protections)
• Has status (status determines the
protections)
• Has Object ACL (overrules working)
• In project (projects determines
access)
Object based protection
• Users with change access to an object can create exceptions to rules-based protection on this
object.
• Useful to grant wider access or limit access to a specific object.
PROJECTS TO CONTROL ACCESS
Projects
• Mecanism to organize data and protection of data
• Examples:
• Objects in project «001-Secret Nuclear Development Project» is hidden from all users that are not
members of the Project Team
• Project Team Members have Write Access to all objects in «002-Collaboration» even though they
are in different groups (e.g. Engineering and Manufacturing).
Project roles
Project administrator (create and modify projects)

Project team administrator (modify project information)
Priviledged team members (add/remove objects)
Team members (read rights)
Projects
• Only privileged members can add

data to projects
• Data can be manual added to
project or automatically added
when the data is created.
• Objects can be in several projects
at the same time
• Reuse of data
• Possible to add security rules
Define project
• Project administrator • Select «Active
creates project Project»
• Add team members
• Add project • Data automatically
administrator • Set membership added to project
• Set project properties • Add security
Data added to
Create project
active project
Raufoss projects
• Change Group/role to
• DBA
• Project Administrator
• Regular users does not have access to edit projects
• Start «Project»
application
Edit existing project
• Select Project in list

• 000 – DBA
• 002 – Team Area
• 003 – Steering Docs
Edit Project Properties
• ID
• Project ID – generated from Excel sheet and manually input in TC ??
• Status
• Active
• Inactive
• Inactive and invisible
• User Program Security
• Must always be checked
Raufoss projects – Edit Project Properties
• Right click project – View properties
Raufoss projects – Add Team Members
• Project Administrator
• Can create projects
• Project Team Administrator
• Can add people to the project
• Privileged members
• Can add data
• Un-privileged members
• Read Access
• Always add «infodba» from DBA group
Add Team Members
• Browse to the user you want to add

• NRN – Product and process engineering –
Project - omhelmen
– NB: Important to choose correct role
• Project
• Team
• Steering
• Select [+]
• See user appears on right hand side as «non-
privileged»
• Double click user to make «privileged»
• Can select entire groups/roles to add

• Can search on top for username
• Remember to select «Modify» to save

changes!!!
Exercise
• Create a project
and select The
Team Memebers
ADMINISTERING WORKFLOW PROCESSES
Workflows
• All work goes through one or more processes to accomplish an objective

• Workflow is the automation of these business processes.
• Documents, information and tasks are passed between participants
Workflows
EPM (Enterprise Process Modeling)
• EPM (Enterprise Process

Modeling) is used to model
Workflow processes
• Each EPM process is a group of

nested tasks
Process Template
Task Template
Example tasks
Releasing data with a process
When data is released, the following typically occurs:

• Release status and date released gets values
• Released data becoms read only
Release_man utility
• Manual Release utility
• Can set status on many item revisions at the same time without going through workflows
• Can also be used to unrelease item revisions
• Only for DBA users

• Status must be valid
• The release folder must be a single folder inside the excecuting user’s Home folder.
Using release_man utility
Release_man
• Create folder • Status are added
• Copy data that • Run release_man
should be released
into folder
Prepare Result
Do task
• Task that the user must complete.

• Do task dialog box displays instructions
Review Task
• Review the work
• Signoff
• Three decisions
Acknowledge task
Resource pool
• Resource pool is a group, role in a group, or a role that can be assigned tasks
• Useful when the task can not be directly assigned to an user
• Possible to create that a minimum number of members in the resource pool must perform the
task.
Workflow Designer
• Edit - Template Filter

• Adds filter for
specific groups for
specific objects
• Example:
• Quick release can
only be used by
Group «dba»
• Only workflows
specified in filter are
available for
specified revision
Workflow Designer
• Workflow handlers
• Action handler
• Rule handler
Workflow Designer
• Signoff Profile
• Who can approve
• «Checker» role for
«Checker Review» task
• How many?
Workflow Designer
• Create Status
• Status 60
• Status 30
• Status 90
Workflow Designer
• Access rules during

workflow
• RTN_In_Job_Access
• Gives access to
responsible party ++
Workflow Designer
• Automatically assign
Manager Review
• Eng Order
• St Doc Change
Workflow Designer
• Set property
• Maturity
• How far in EO WF is open
EOs?
Workflow Designer
• Automatically assign
Manager Approval task to
manager role in
owning_project
Summary
• Teamcenter Data Model

• Preferences
• LOV
• Relations
• Business Objects
• Rules
• Organization
• Groups, roles, users, persons
• Queries
• Create new queries
• Default values, hidden values
• Preferences
• Edit – Options
• General - UI – sys admin – Real property names
• Search *
• Organization
• Location: Site / group / User
Summary
• Access Manager • Workflow Administration

• Depth First Search • Workflow Designer
• Rule Tree • File – New process template
• ACL – Access control list • Based on existing template
• read from the top • Edit offline – set stage to available
• Blank values – skip to next line • Handlers
• V to give right • Action
• X to remove right • Rules
• Bypass – infodba • Workflow designer documentation
• In_Job_Access • Workflow Template Filter
• Has Status • Group – Object
• Working • Available WFs list
• Projects
Course Agenda
Course Introduction
Organization
Queries
Preferences
Access Manager
Projects
REPORT BUILDER
DISPATCHER SERVER
DISPATCHER SERVER
See Teamcenter Admin Guide
DISPATCHER SERVER
PRACTICAL ADMINISTRATION
Stop and delete workflows that are wrong.
Delete Objects
• Only «Owning user» or System Administrators can delete objects

• «Referenced» objects can not be deleted
• Revision can not be content in a «Home» or «Newstuff» folder (Item can be.. Legacy…)
Must be «cut» before deletion
• Used in a structure – must be removed from BOM View before delete (Remove Line)
• Approved by workflow – Must delete workflow first!
• The point is that noone should be able to delete anything someone else has used/can use
Delete Objects – Revision in user home folder
• Revisions created directly in AWC is pasted to users «Home» folder

• Delete must be done in Rich Client
• Select Item - Delete
• Get Error message

• The instance is referenced
• The object is referenced by «Home (Morten Moi)»
• To be able to delete it we must «cut» it from home folder
• Select ItemRevision – Impact Analysis – Where Referenced

• Right click Home (Morten Moi) folder – Send to My Teamcenter
• Double click itemRevision to Open in new tab

• Cut from Users Home Folder
• Select Item from opened tab - Delete
• Double click itemRevision to Open in new tab

• Cut from Users Home Folder
• Select Item from opened tab - Delete
Delete Objects – Revision with status
• Impact analysis
• Delete workflow
• Then delete Item
Force workflows through the system in cases where they are hanging (stopped by missing user input).
Support users that have questions related to the system.
Add/modify choices to the different drop down list for all properties (areas, sectors, line, department, etc…)
• Done in BMIDE
• Teamcenter administrator/owner job
• Consultancy
• Show example of adding «Directed Buy» to Make/Buy for ItemRevision
• Update PLM Databook document
Teamcenter superuser course expextations
• Begrepsforståelse
• Arbeidsflyt I hele systemet
• Admin/config
• Hvordan systemet er skrudd sammen
• Støtte superbrukere
• Active Workspace vs RAC
• Hva gjør superbruker
• Config
• Tilganger Client/config
• Hva kan gjøres selv
MANAGEMENT CONSOLE
Management console
• See Admin Documentation
LOG FILES
SUPPORT VS OPERATIONS
SIEMENS GTAC IR PR ER
PROBLEM SOLVING
FCC not started
• This means that it is not possible to open/save files in Teamcenter on the machine.
• FCC can be checked by opening a command prompt and running the following command:
C:\Siemens\Teamcenter\tccs\bin\fccstat –status
• If OK will give a overview of status
• If not OK: FCC Offline
• Running fccstat –start can give indication what is wrong
• This process blocks the deleting of RAC folder. To shut down: fccstat -kill
• This is most often a problem on new installations or reinstallations where some wrong settings
have been done.
Error messages in Teamcenter
• If a user gets an error message in Teamcenter, then investigate this:

• Doing the same operation again gives the same error message?
• Log in as another Teamcenter user and see if that gives the same error.
• Log in as the same user on another computer and test again.
• This helps rule out if this is a computer specific problem or a Teamcenter specific problem
• Some error messages gives information what needs to be done.

• Click the red X or «more…» for more information about error
Problems with deleting/copying data
LOG FILES
Where is log files stored
• Press Help-About
Log files are saved on the
server machine. So notice
the host name.
File names ar random and

sorting on date is a good
thing to find them quick.
Log files: Other information
• Log files are normally deleted if no errors in them.

• Controlled by property
• Log files are often deleted periodically on the server (depending on setup).
• Common setup:
• Logfiles older than 3 days are deleted by a scheduled task in windows
• Task Scheduler – Cleanup TC_TMP
• Runs at 00:00 every night
• Best Practice:
• Set environment variable TC_TEMP=D:\SIEMENS\TC_TMP on the teamcenter server
• This puts all TC log files in this folder and the old ones can be deleted by scheduled task.
OTHER TIPS
Environment variables
• FMS_HOME=C:\Siemens\Teamcenter\Tc10.1\tccs
• Important to be able to start Teamcenter’
• Both for server and client
• Start cmd
• Cd %fms_home%
• SPLM_License_server=28000@wintrain
• 28000 = port
• Wintrain = servername
• Points to the License server
License server
•• SPLM_License_server=28000@wintrain
• C:\Siemens\SPLM License Server
• Start – LMTOOLS
Java
• Use 64-bit java for 64-bit Teamcenter
• Auto updating Java 8 deletes the old java folder by default and installs to a new location
• C:\Program Files\Java\jre1.8.0_45
• C:\Program Files\Java\jre1.8.0_60
• Teamcenter uses environment variables and files to point to Java install folder
• These must be updated after JAVA upgrade….
• Variables
• JAVA_HOME=C:\Siemens\Java\jre1.8.0_45
• JRE64_HOME=C:\Siemens\Java\jre1.8.0_45
• Files
• C:\Siemens\Teamcenter\Tc10.1\install\tem_init.bat
Temp folders
• Can be deleted to solve problems:
• Server
• %temp%\V10000.****
• (Requires restart of Teamcenter Server Manager service, kicks out all users)
• Client
• C:\Users\<username>\Teamcenter\RAC SOA TAO
• C:\Users\<username>\FCCCache
• Requires shutdown of FCC (if running)

• Start task manager – End process «java.exe»
Useful resources
• Siemens: http://support.industrysoftware.automation.siemens.com/gtac.shtml
• Download software, get documentation etc.
Documentation
• Installed with Teamcenter

• Also available at Siemens page
• Admin documentation typically found at Teamcenter server

• D:\Siemens\Install_media\Teamcenter\Base_install\Tc10.1\pub
• Here is a folder named PDF
• Use tchelp.pdx to search in all PDF files
• One document for each Teamcenter Application
FORVENTNINGER TEAMCENTER SUPERUSER
21.09.2015
OVERSIKT OVER SYSTEMET

SAMMENHENGEN
DAGENS RUTINER INN I SYSTEMET
PRAKTISK BRUK / EFFEKTIV BRUK
ERP INTEGRASJON
ARBEIDSPROSESSER
OPPSETT PROSJEKT
MULIGHETER
Finished

NEX - Teamcenter Superuser Course Presentation - v06 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

NEX - Teamcenter Superuser Course Presentation - v06 PDF

Caricato da

Copyright:

Formati disponibili

Teamcenter Superuser

15.05.2017, 16.05.2017, 29.05.2017

This presentation is copyright to Digitread.

What do you expect to gain from attending this course?

10 minutes break every hour

Lunch from 11:30 – 12:15

Teamcenter superuser course

Finding information Information flow Information quality Complex products

• Where can I find the documentation related to this part?

• Is this the latest version of this document?

3 000 200 000

How many components?

Difficult to find correct

Can’t trust the data found

Creating duplicate data

Manned telephone support (workdays 08:00 – 16:00)

Monitored email support Remote assistance using

Remote Desktop and a Virtual Private Network where available

If you call us:

If you send us a mail:

- Always include the following

- Always include the following information when applicable

Rich Client – Advanced Search

Searches in Teamcenter Database.

Can create custom Admin searches

• Item is the typical storage container

• An Item will contain at least

GENERAL TERM AT NEXANS

ITEM DESIGN DOCUMENT REQUIREMENTS PR, ECR, ECN

REVISION A REVISION A REVISION A REVISION A REVISION A

REVISION X REVISION X REVISION X REVISION X REVISION X

• CAD files • Documents related to a • Customer Requirements • Change Management:

• Create Item in Rich Client

Need to decrease Item revision N

• Attachments are available from a separate tab

• File – New – Dataset

• Create Word Dataset in Rich Client in the Project Doc

1. What is the difference between Item and Item Revision?

• Properties are information that defines

Check-out and Check-in basics

You can check objects into and out of the

A checkout is either explicit or implicit.

• Implicit checkout occurs when you double-click to open a dataset. Implicit

DBA role can override checkout. All unsaved work is lost

Relations shows how the objects are

Where used (assemblies)

Where used (assemblies)

• Workflow is the automation of business

• The first step is to generate the data needed.

30 DEVELOPMENT Approved 30 DEVELOPMENT

Data in the system can be in one of three life cycle

• Send your Project Document to workflow «60 – Production Release»

• You can revise or duplicate data

• Revise your Item

Use the Viewer to find the

Structure Manager data

Structure Manager data

Select top level of assembly

Excel or HTML format

Select Revision Rule

• Search for item Revision ?????????????/A

Revision rules is used to define how the

– To revise a component, all sub