Using TC

Using Teamcenter
Student Guide
July 2013
MT25150 – Teamcenter 10.1
Publication Number
MT25150_S_101
Proprietary and restricted rights
notice; Trademarks
Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens Product
Lifecycle Management Software Inc.
© 2013 Siemens Product Lifecycle Management Software Inc.
Trademarks
Siemens and the Siemens logo are registered trademarks of Siemens AG.
Teamcenter is a trademark or registered trademark of Siemens Product
Lifecycle Management Software Inc. or its subsidiaries in the United States
and in other countries. All other trademarks, registered trademarks, or
service marks belong to their respective holders.
2 Using Teamcenter MT25150_S_101

Contents
Proprietary and restricted rights notice; Trademarks . . . . . . . . . . . 2
Course overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Key benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Learning tracks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Training materials provided . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Accessing Teamcenter online help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Training scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Introduction to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Product lifecycle management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Basic concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Basic tasks using rich client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Teamcenter interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Rich client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Starting Teamcenter sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Logging on to the Teamcenter rich client . . . . . . . . . . . . . . . . . . . . . 1-11
Using the Getting Started application . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Working with the rich client navigation pane . . . . . . . . . . . . . . . . . . . . 1-13
Teamcenter perspectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Teamcenter rich client perspectives and views . . . . . . . . . . . . . . . . . . . 1-18
Open a rich client perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Switch between open perspectives . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Save, reset, or close a rich client perspective . . . . . . . . . . . . . . . . . . 1-21
Configuring the display of applications . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Display primary and secondary applications . . . . . . . . . . . . . . . . . . 1-23
Set your own user variables for the classroom activities . . . . . . . . . . . . 1-24
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-26
Working in My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Basic My Teamcenter concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Basic My Teamcenter tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
My Teamcenter views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Searching in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Using Teamcenter 3
Contents
Organize data in folders and pseudofolders . . . . . . . . . . . . . . . . . . . . . . . 2-6

Home, Newstuff, and Mailbox folders . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Working with folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Create a new folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Rename a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Reorder objects in a folder or view . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Print a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Delete a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Add favorites to organize your data . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Add a subfolder to your Favorites list . . . . . . . . . . . . . . . . . . . . . . . 2-17
Rename a folder in the Favorites list . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Remove a link or folder from the Favorites list . . . . . . . . . . . . . . . . . 2-19
Object references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Cutting, copying, pasting, and deleting data objects . . . . . . . . . . . . . . . 2-21
Cut data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Copy data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Pasting data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Paste the contents of the clipboard . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
Paste an item or item revision and specify the relation type . . . . . . . 2-26
Pasting object references to applications outside the Teamcenter
environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Dragging and dropping data objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Working with items in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Items and item revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Basic item structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Item types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Creating items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Create an item example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Creating new items based on existing items or item revisions . . . . . . . . 3-12
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Creating item revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Create a new revision of an item . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Sequence ID display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Managing revision sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Item and item revision relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Automatically defined relation types . . . . . . . . . . . . . . . . . . . . . . . . 3-21
User-specified relation types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Managing alternate and alias identifiers . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Initial identifier attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Alias identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

Contents
Alternate identifiers . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . 3-27

Open items and item revisions in My Teamcenter ... . . . . . . . . . . . . . . 3-28
Filter the item revision display in My Teamcenter .. . . . . . . . . . . . . . . 3-29
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . 3-30
Viewing and modifying object properties . . . . . . . . . . . . . . . . . . . . 4-1
Overview of object properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

View property values in the Details table . . . . . . . . . . . . . . . . . . . . . 4-5
View properties of a single object in the Properties dialog box . . . . . . 4-6
View properties of multiple objects in the Properties dialog box . . . . . 4-7
Modify the properties of a single object . . . . . . . . . . . . . . . . . . . . . . . 4-8
Modify the properties of multiple objects simultaneously . . . . . . . . . 4-10
Find and replace property values and add prefixes and suffixes . . . . 4-12
Relation properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Modify the properties of a single relation object . . . . . . . . . . . . . . . . 4-14
Configuring table data display in the rich client . . . . . . . . . . . . . . . . . . 4-15
Configure the Details view table . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Reposition columns in a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Sort data in a table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Printing information about your data . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Print object information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Print object information from the Properties dialog box . . . . . . . . . . 4-24
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Creating and managing datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Dataset objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Creating datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Create a new dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Create a new dataset by drag-and-drop . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Dataset named references . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
View and modify named references . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
Dataset versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Key points about dataset versions . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Revert to a previous dataset version . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Purge dataset versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Creating new datasets based on existing datasets . . . . . . . . . . . . . . . . . 5-18
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Applying data security practices . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Using Teamcenter 5
Contents
User groups and roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Key points about groups and roles . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Change your group and role setting . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Set your default group and role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Overview of checkout and checkin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8
Explicit checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Implicit checkout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
Check out an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Check in an object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Transfer checkout to another user . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16
Canceling a checkout request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17
View the checkout history of an object . . . . . . . . . . . . . . . . . . . . . . . 6-18
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19
Managing object protection and ownership . . . . . . . . . . . . . . . . . . . . . . 6-20
Rules-based protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21
Object-based protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22
Controlling object access working with ACLs . . . . . . . . . . . . . . . . . 6-23
View access privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-24
View access privileges example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25
Add accessors and grant privileges . . . . . . . . . . . . . . . . . . . . . . . . . 6-26
Modify access privileges on an object you own . . . . . . . . . . . . . . . . . 6-28
Authorized data access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29
About configuring authorized data access (ADA) . . . . . . . . . . . . . . . . . . 6-30
Using the information center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-33
Performing and managing searches . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Searching in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Using the Search view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Change your search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Using search types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Providing search input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Using wildcard characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Using quick search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Perform a quick search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Using simple search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Perform an advanced search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Query for dataset sequences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16
Working with search output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Working with search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Using the Search Results view . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Navigate the search results and adjust the display setting . . . . . . . . 7-21
Rename search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Close search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

Contents
Compare search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

Printing search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Print a snapshot of the search results tree . . . . . . . . . . . . . . . . . . . . 7-27
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
Saving searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29
Save search results to your My Saved Searches folder . . . . . . . . . . . 7-30
Save search results to a subfolder of My Saved Searches . . . . . . . . . 7-31
My Saved Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Perform a saved search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Customize saved searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Share saved searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Running reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Examples of reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Generate a Report Builder report . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Item report examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Generate an item report on a Teamcenter object . . . . . . . . . . . . . . . 7-42
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Working in projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Introduction to projects and programs . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Project administrators and team members . . . . . . . . . . . . . . . . . . . . 8-3
Viewing project data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Project smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Apply project smart folder filtering . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9
Assigning objects to projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Assign objects to projects from the tree or Details table . . . . . . . . . . 8-11
Assign objects to projects from search results . . . . . . . . . . . . . . . . . 8-12
Assigning secondary objects to projects . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Secondary object propagation rules for projects . . . . . . . . . . . . . . . . 8-14
Secondary object relations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Automatically assigning objects to projects . . . . . . . . . . . . . . . . . . . . . . 8-16
Considerations for automatic assignment of objects to projects . . . . . 8-17
Removing objects from projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Remove objects from projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Finding projects and project data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Find projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Find objects in projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
Opening and viewing product structures . . . . . . . . . . . . . . . . . . . . . 9-1
Using Teamcenter 7
Contents
Understanding product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Basic tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Structure Manager interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
BOM view objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
BOM view types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
View a product structure in Structure Manager . . . . . . . . . . . . . . . . . . . 9-8
Product structure display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Adjust the product structure columns display . . . . . . . . . . . . . . . . . . . . 9-12
Viewing product structure properties . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Insert or remove a property column . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
Managing column configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Expanding or collapsing an assembly . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Expand an assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Collapse an assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18
Sorting the structure tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19
Print the product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20
View assembly components in Structure Manager . . . . . . . . . . . . . . . . . 9-21
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
Controlling assembly configuration views . . . . . . . . . . . . . . . . . . . 10-1

Introduction to revision control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Release status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Release status types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Revision rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Revision rules list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Changing the default revision rule setting . . . . . . . . . . . . . . . . . . . . . . 10-7
Setting an ad hoc revision rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Understanding precise and imprecise product structures . . . . . . . . . . 10-10
Using precise and imprecise assembly structures . . . . . . . . . . . . . 10-11
Product structure background color . . . . . . . . . . . . . . . . . . . . . . . . 10-12
Revising precise assembly structures . . . . . . . . . . . . . . . . . . . . . . 10-13
Revising imprecise assembly structures . . . . . . . . . . . . . . . . . . . . 10-14
Changing between precise and imprecise . . . . . . . . . . . . . . . . . . . . 10-15
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Understanding revision effectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17
Revision effectivity configuration algorithm . . . . . . . . . . . . . . . . . . 10-18
Using date effectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Using unit number effectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-21
Displaying and editing revision effectivity . . . . . . . . . . . . . . . . . . . 10-22
Best practices when applying effectivity . . . . . . . . . . . . . . . . . . . . 10-24
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
Creating and managing product structures . . . . . . . . . . . . . . . . . . 11-1

Contents
Build and edit product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Create a new BOM view revision automatically . . . . . . . . . . . . . . . . 11-3
Setting find numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Save product structure changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Saving changes with multiple windows . . . . . . . . . . . . . . . . . . . . . . 11-6
Refresh the Structure Manager window and resynchronize to
database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Close the product structure window . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Finding a component by property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Find components by property . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Modify a product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Add components to a product structure . . . . . . . . . . . . . . . . . . . . . 11-14
Concurrent updates safeguard . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Copying and pasting objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
Add existing components to selected BOM lines . . . . . . . . . . . . . . . 11-19
Paste a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Remove a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
Move a component to another assembly . . . . . . . . . . . . . . . . . . . . . 11-22
Working with replacements, global alternates and substitute parts . . . 11-23
Replacing a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-24
Replace a component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25
Managing global alternates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
Working with global alternates . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-30
Substitute components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-32
Using substitutes in Structure Manager . . . . . . . . . . . . . . . . . . . . 11-33
Create substitute component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-34
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-36
Working with product structures . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Packing multiple components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Unpack structure lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Viewing occurrence notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Pack structure lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Restrictions on packed lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6
Modify quantity for multiple components . . . . . . . . . . . . . . . . . . . . 12-7
Comparing product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Product structure comparison modes . . . . . . . . . . . . . . . . . . . . . . . 12-10
Compare product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Example result of a structure comparison . . . . . . . . . . . . . . . . . . . 12-13
Initiating the graphical comparison . . . . . . . . . . . . . . . . . . . . . . . . 12-14
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Cloning a product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
Clone a product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
Editing a product structure clone . . . . . . . . . . . . . . . . . . . . . . . . . 12-21
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Using Teamcenter 9
Contents
Marking up the product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23

Enable markup mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-24
Create and insert general markup . . . . . . . . . . . . . . . . . . . . . . . . . 12-25
Review and comment on markup . . . . . . . . . . . . . . . . . . . . . . . . . . 12-27
Apply markup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28
Apply all markups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30
Carrying forward markups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31
Delete markup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-32
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-33
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-34
Configuring a product structure with variants . . . . . . . . . . . . . . . 13-1
Using classic variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Example of using classic variants . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Creating basic variant data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Create options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Change option values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Create variant conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Modifying variant conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-14
Insert a clause before another clause . . . . . . . . . . . . . . . . . . . . . . . 13-15
Replace or remove a clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Move a clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17
Group a clause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18
Setting variant rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Set or unset the required variant rule . . . . . . . . . . . . . . . . . . . . . . 13-20
Show and hide unconfigured components . . . . . . . . . . . . . . . . . . . . . . 13-23
Show unconfigured components . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
Hide unconfigured components . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-25
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27
Navigating the relation hierarchy of an object . . . . . . . . . . . . . . . 14-1
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Access Relation Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Relation Browser user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Using the Relation Browser view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5
Using the Image Preview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8
Using the Graph Overview view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9
Using the Properties view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10
Where-referenced and where-used searches . . . . . . . . . . . . . . . . . . . . 14-11
Perform a graphical where-referenced search . . . . . . . . . . . . . . . . 14-12
Where-used searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-16
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23

Contents
Classifying and using standard data . . . . . . . . . . . . . . . . . . . . . . . 15-1
Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Basic concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Basic tasks using Classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
Classification interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Classification panes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Classification symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Classification hierarchy structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Displaying the classification hierarchy . . . . . . . . . . . . . . . . . . . . . 15-10
Displaying a subset of the hierarchy . . . . . . . . . . . . . . . . . . . . . . . 15-11
Set a node as root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Display a node as temporary root . . . . . . . . . . . . . . . . . . . . . . . . . 15-13
Display information in the Properties pane . . . . . . . . . . . . . . . . . . 15-14
Preview available attribute values . . . . . . . . . . . . . . . . . . . . . . . . 15-15
Change the active measurement system . . . . . . . . . . . . . . . . . . . . 15-16
Viewing the tree graphically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-17
Classifying Teamcenter objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18
Create a classification object (ICO) . . . . . . . . . . . . . . . . . . . . . . . . 15-19
Classifying an object multiple times . . . . . . . . . . . . . . . . . . . . . . . 15-20
Create multiple classification instances of an object . . . . . . . . . . . . 15-21
Revising classified items or item revisions . . . . . . . . . . . . . . . . . . . 15-22
Modifying attribute values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-23
Modify attribute values of a specific ICO . . . . . . . . . . . . . . . . . . . . 15-24
Finding an ICO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-25
Classification search buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-26
Search by object ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-27
Search by object type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-28
Apply a revision rule to the search . . . . . . . . . . . . . . . . . . . . . . . . 15-29
Searching based on a group or class . . . . . . . . . . . . . . . . . . . . . . . . . . 15-30
Use the Search Class dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . 15-31
Use the quick search feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-33
Search all ICOs in a selected class . . . . . . . . . . . . . . . . . . . . . . . . . 15-34
Search for ICOs in a selected class by attribute value . . . . . . . . . . 15-35
View Classification search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-36
Use the Search Results box to navigate to a specific ICO . . . . . . . . 15-37
Viewing search results in the Properties pane . . . . . . . . . . . . . . . . 15-38
Viewing the active unit of measure attribute . . . . . . . . . . . . . . . . . 15-39
Viewing search results in the Table pane . . . . . . . . . . . . . . . . . . . . 15-40
Displaying associated data in the viewers . . . . . . . . . . . . . . . . . . . . . . 15-41
Copying classification objects and classified BOM lines . . . . . . . . . . . . 15-42
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-43
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-44
Viewing and working with visualization files . . . . . . . . . . . . . . . . 16-1
Locate and view visualization data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Using Teamcenter 11
Contents
3D navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Set view preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
View preferences – General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
View preferences – Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-8
View preferences – Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
Work with parts in the embedded viewer . . . . . . . . . . . . . . . . . . . . . . 16-12
Embedded viewer – Select parts . . . . . . . . . . . . . . . . . . . . . . . . . . 16-13
Embedded viewer – Set selection preferences . . . . . . . . . . . . . . . . 16-14
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-15
Adjust performance settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-16
Use predefined performance settings . . . . . . . . . . . . . . . . . . . . . . . 16-17
Set performance settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-18
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-20
Initiating a workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
Overview of workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Workflow process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Workflow process branching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
Check in data before starting a workflow . . . . . . . . . . . . . . . . . . . . . . . 17-5
Initiate a workflow process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
Complete the New Process Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Attachments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Process Template tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Assign All Tasks tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Creating workflow subprocesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
Create a workflow subprocess . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Review workflow tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Viewing process information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Tracking process status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Managing workflow task assignments . . . . . . . . . . . . . . . . . . . . . . 18-1
Select signoff teams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

Select a signoff team during workflow creation . . . . . . . . . . . . . . . . 18-3
Select a signoff team for active tasks . . . . . . . . . . . . . . . . . . . . . . . . 18-5
Use process assignment lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-8
Select a signoff team for pending tasks . . . . . . . . . . . . . . . . . . . . . . 18-9
Select a signoff team automatically . . . . . . . . . . . . . . . . . . . . . . . . 18-10
Assign the signoff to a resource pool . . . . . . . . . . . . . . . . . . . . . . . . . . 18-11
Types of signoff tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-12

Contents
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-13
Perform a signoff task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-14
Using the perform-signoffs Task View . . . . . . . . . . . . . . . . . . . . . . 18-15
Approve a review signoff task . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-17
Reject a review signoff task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-18
Make no decision on a review signoff task . . . . . . . . . . . . . . . . . . . 18-19
Acknowledge a signoff task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-20
Do not acknowledge a signoff task . . . . . . . . . . . . . . . . . . . . . . . . . 18-21
Using resource pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-22
Subscribe to a resource pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-23
Delegate tasks from a resource pool . . . . . . . . . . . . . . . . . . . . . . . . 18-24
Delegate a signoff task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-25
Use Out of Office Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-26
Creating a workflow surrogate user . . . . . . . . . . . . . . . . . . . . . . . . . . 18-27
Release states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
Status types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-29
Reviewing workflow by viewing the process history . . . . . . . . . . . . . . . 18-30
View workflow audit logs in My Teamcenter . . . . . . . . . . . . . . . . . . . . 18-31
Process reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-32
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-33
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-34
Managing Teamcenter data through the Microsoft Office

integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-2
Manage data with Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-3
Client for Office interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-4
Basic tasks for Client for Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Browse Teamcenter Home folder . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Create folders, items, and datasets . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Find objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Open datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-10
Update datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Insert Teamcenter objects into an Office document . . . . . . . . . . . . 19-13
Insert Teamcenter markups for Word documents . . . . . . . . . . . . . . 19-14
Managing your Teamcenter settings in Microsoft Office . . . . . . . . . 19-15
Open and update datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-16
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-19
Manage workflow with Microsoft Office . . . . . . . . . . . . . . . . . . . . . . . . 19-20
Initiate a workflow process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-21
Browse workflow task assignments . . . . . . . . . . . . . . . . . . . . . . . . 19-22
Synchronize your workflow tasks with Outlook . . . . . . . . . . . . . . . 19-23
Perform a workflow task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-24
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-25
Manage BOM with live Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Basic concepts of live Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Using Teamcenter 13
Contents
Basic tasks for live Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28

Export BOM to live Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29
Update live Excel data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-31
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-32
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-33
Using Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-2
Change Manager interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-3
Change Manager tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-4
Basic concepts for using Change Manager . . . . . . . . . . . . . . . . . . . . . . . 20-5
Managing the change cycle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-6
Change management data objects . . . . . . . . . . . . . . . . . . . . . . . . . . 20-7
What kind of changes can you create? . . . . . . . . . . . . . . . . . . . . . . . 20-8
Relationship between change objects . . . . . . . . . . . . . . . . . . . . . . . 20-10
Classifying changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-12
About the participants in the change process . . . . . . . . . . . . . . . . . 20-13
What can you do in Change Manager? . . . . . . . . . . . . . . . . . . . . . . . . 20-14
Change management process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-16
Problem report (PR) process example . . . . . . . . . . . . . . . . . . . . . . 20-19
Change request fast track process example . . . . . . . . . . . . . . . . . . 20-20
Change request standard track process example . . . . . . . . . . . . . . 20-21
Change notice process example . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-23
Change states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-25
Initial change state configuration . . . . . . . . . . . . . . . . . . . . . . . . . 20-26
Change states values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-27
Example of the state changes of a problem report . . . . . . . . . . . . . 20-29
Example of the state changes in a fast track change request . . . . . 20-30
Example of the state changes in a standard track change request . . 20-32
Example of the state changes in a change notice . . . . . . . . . . . . . . 20-34
Searching for existing change objects . . . . . . . . . . . . . . . . . . . . . . . . . 20-36
Managing change object searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-37
Executing and deleting change object searches . . . . . . . . . . . . . . . 20-38
Organizing the Change Home view . . . . . . . . . . . . . . . . . . . . . . . . 20-39
Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-41
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-42
Creating and managing change objects . . . . . . . . . . . . . . . . . . . . . 21-1
Creating a change object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

Create a problem report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-3
Create a change request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-5
Create a change notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-7
Managing a change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-9
Relating items to a change and the properties required . . . . . . . . . 21-10
Assign participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-13

Contents
Create a work breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-15

Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-18
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-19
Elaborating and executing the change . . . . . . . . . . . . . . . . . . . . . . 22-1
Executing the change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2

Adding an affected item revision to change folders . . . . . . . . . . . . . . . . 22-3
Create new or replacement items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-4
Relating a solution item to an impacted item . . . . . . . . . . . . . . . . . . . . 22-5
Relate a solution item to an impacted item manually . . . . . . . . . . . . . . 22-6
Manage replacements through supersedures . . . . . . . . . . . . . . . . . . . . 22-7
Create supersedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-8
View supersedure data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-10
Assign effectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-11
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-13
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-14
Working in the Teamcenter thin client . . . . . . . . . . . . . . . . . . . . . . 23-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-2
Differences between the rich and thin client . . . . . . . . . . . . . . . . . . 23-3
Teamcenter functionality available in the thin client . . . . . . . . . . . . 23-4
Teamcenter functionality not available in the thin client . . . . . . . . . 23-5
Thin client interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-6
Start and stop a Teamcenter thin client session . . . . . . . . . . . . . . . . 23-8
Managing your thin client interface . . . . . . . . . . . . . . . . . . . . . . . 23-10
Using the top navigation bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-11
Working with objects in the thin client component pane . . . . . . . . . 23-12
Working with tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-14
Using dynamic menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-16
Set your display options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-17
Column management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-18
Searching in the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-19
Perform a quick search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-20
Perform an advanced search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-21
Share saved searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-23
Use shared saved searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-25
Managing basic data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-26
Create a folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-27
Create a new item in thin client . . . . . . . . . . . . . . . . . . . . . . . . . . 23-28
Creating new items based on existing items in the thin client . . . . 23-30
Revising an item revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-32
Create a dataset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-33
Navigating structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-37
Managing product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-38
Using Change Manager in the thin client . . . . . . . . . . . . . . . . . . . . . . 23-39
Using Teamcenter 15
Contents
Working with change objects in the thin client . . . . . . . . . . . . . . . . 23-40

Create a problem report in the thin client . . . . . . . . . . . . . . . . . . . 23-41
Create a change request in the thin client . . . . . . . . . . . . . . . . . . . 23-43
Create a change notice in the thin client . . . . . . . . . . . . . . . . . . . . 23-45
Assign participants in the thin client . . . . . . . . . . . . . . . . . . . . . . . 23-47
View BOM changes, supersedures, and genealogy in the thin
client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-49
Managing your workflow tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-50
Using worklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-51
Performing interactive tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-53
Selecting members of the signoff team . . . . . . . . . . . . . . . . . . . . . . 23-54
View a workflow process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-55
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-58
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23-59
Course summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1
Managing views, layouts, and view networks . . . . . . . . . . . . . . . . A-1

Managing views, layouts, and view networks . . . . . . . . . . . . . . . . . . . . A-2
Recognizing primary and secondary views . . . . . . . . . . . . . . . . . . . . A-5
Changing view network color presentation . . . . . . . . . . . . . . . . . . . A-7
Display and move a view in the rich client . . . . . . . . . . . . . . . . . . . . A-8
Change the view association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Hide and display views and view folders . . . . . . . . . . . . . . . . . . . . A-14
Managing views, layouts, and view networks . . . . . . . . . . . . . . . . . . . A-16
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Course overview
Using Teamcenter introduces the concept of product lifecycle management

(PLM), provides instruction on working in the rich client interface, and
the basics of using a suite of Teamcenter® software applications and
perspectives. These perspectives include My Teamcenter, Structure Manager,
Classification, embedded viewer, Change Manager, and Relation Browser.
Course objectives
To learn the basics of using Teamcenter and the most commonly used
Teamcenter software perspectives.
• To learn the basic concepts of product lifecycle management.
• To use the rich client user interface to perform basic user tasks, such as
creating and working with Teamcenter items and item revisions, and
using various navigation methods to locate, view, and report on data.
• To organize, manage, and secure product data.
• To use Structure Manager to view, build and edit product structure.
• To navigate the classification hierarchy and use standard product data in

product structures.
• To use the embedded viewers within Teamcenter to locate and view

visualization data.
• To assign tasks, perform tasks, and track the completion of tasks in a

workflow process.
• To create change objects and track a change object through the change
process to completion.
• To manage Teamcenter objects using Microsoft Office and live Excel.
• To use the thin client to manage and navigate to various Teamcenter

objects and functions.
Using Teamcenter 17
Course overview
Key benefits
Key benefits for completing the course objectives include:
• Working in a product lifecycle management environment to organize,
manage, and secure product data throughout the product lifecycle.
• Perform basic user tasks and organize product data.
• Configuring the navigation pane for efficient access to frequently used

product data and functions.
• Creating Teamcenter items and managing the item revisions.
• Viewing, creating and maintaining bill of materials (BOM) data using

Structure Manager.
• Viewing and manipulating 2D and 3D visualization data using

the embedded viewers within Teamcenter perspectives such as My
Teamcenter, and Structure Manager.
• Submitting data to a workflow process and tracking it to completion.
• Working with change objects to manage change.
Prerequisites
• Familiarity with basic Windows operating system commands.
Note
The Using Teamcenter course is a prerequisite for the following courses:
• Application Administration
• Data Model Administration
• Teamcenter Manufacturing Assembly Process Planning

Course overview
Audience
The primary audience for this course includes users who design, configure
and release data using Teamcenter, such as designers, design engineers,
configuration managers.
Learning tracks
Learning tracks for the Teamcenter application are found on the Siemens
PLM Software training Web site:
http://training.industrysoftware.automation.siemens.com/tracks/index.cfm
Using Teamcenter 19
Course overview
Training materials provided

Material Description
Contains all content.
Is yours to keep and make notes.
Reference tear-out pages in the back of the book
include the:
• Course agenda.
Student Guide • Classroom data sheet.
• Student logon user IDs and numbers.
• Student profile, to help us better meet your

training needs.
• Course evaluation, which is also provided online.

Activities are provided online in electronic format
and designed to appear on the left of the monitor.
Activities
Ask your instructor how to access the activities
following the conclusion of the class.
Using Teamcenter 21
Course overview
Accessing Teamcenter online help

The Teamcenter Help Library covers functionality from end-user tasks to
customization instructions.
To access the Teamcenter Help Library:
• In the rich client, choose Help®Help Library or press the F2 key.
• In the thin client, choose Help®Web Collection to access the thin client
help, or choose Help®General Collection to access the full library.
To access help for the current application:

• In the rich client, choose Help®Current Application or press the F1 key.
Note
You cannot access application-specific help in the thin client.
Training scenario
This course uses the Classic Car Company scenario as background for
administering and using Teamcenter in a training environment.
Classic Car Company (CCC)
CCC has been in business for 20 years as one of the first companies to
successfully design and sell classic kit cars. Because of the increased demand
for their product, the company has grown from 5 employees to more than 80
employees. The company operates out of offices in the United States and
Europe.
CCC designs and manufactures a variety of classic cars in the following
categories:
• High Performance – racing car
• Best of Show – show car
CCC currently delivers 100 cars per year; the process takes 18 months from
concept to delivery. CCC wants to:
• Increase their output.
• Reduce time to market.
• Reduce development costs.

Course overview
CCC began to experience problems managing their large amounts of data

and tracking project and assembly information. Problems they began to
experience include:
• Lost data.
• Duplicate data resulting in higher labor costs.
• Working with the wrong revision of the part causing assembly problems
and quality problems.
• Lengthy product development cycles.
• Poor communication, both internally and externally.
CCC needed a tool to allow their employees to share accurate, up-to-date

information at any point in the product development life cycle. Consultants
recommended they investigate the use of a product lifecycle management
system to track the data and information required to design, manufacture,
and support their products.
CCC chose Teamcenter as their tool; the Teamcenter software was recently
installed.
The Teamcenter administrator manages the Teamcenter data model. CCC
has decided to use as much standard functionality as possible, but some
extensions to the data model were performed to suit CCC business processes.
Using Teamcenter 23
Lesson
1 Introduction to Teamcenter
Purpose
This lesson introduces the basic concepts of the Teamcenter product lifecycle
management software and some commonly used Teamcenter perspectives.
Objectives
After you complete this lesson, you should be familiar with:
• Basic concepts of product lifecycle management (PLM).
• Working in perspectives and views.
• How to configure the navigation pane.
Help topics
Additional information for this lesson can be found in:
• Getting Started with Teamcenter
• My Teamcenter Guide
• Thin Client Interface Guide
Using Teamcenter 1-1

Introduction to Teamcenter
1.1 Product lifecycle management

Product lifecycle management (PLM) is an essential element in effectively
creating and using global innovation networks to enable organizations and
their partners to collaborate at every stage of the product lifecycle. PLM
provides businesses with unified information at every stage of the product life
cycle include planning, development, execution, and support.
1-2 Using Teamcenter MT25150_S_101

1.2 Basic concepts

Teamcenter is a suite of digital product lifecycle management solutions built
on an open PLM foundation.
The Teamcenter solution portfolio can be configured to achieve your PLM
vision by:
• Integrating idea management and requirements planning into the digital
life cycle management, product development, and manufacturing process.
• Linking partners and suppliers with secure global access to your product
knowledge based on access rules.
• Enabling consistent, repeatable processes and commonality.
Teamcenter supports all phases of the product life cycle, including planning,
development, execution, and support by providing tools for:
• Systems engineering and requirements management
• Product structure and configuration management
• Workflow and change management
• Content management and managing document behavior
• Managing contract data
• Vendor management
• Product visualization
• Manufacturing process management
• Classification and reuse
• CAE Manager
• Repeatable Digital Validation
• Maintenance, repair, and overhaul
• Industry solutions
• Dimensional Planning and Validation (DPV)
• Electronic Design Automation (EDA)
• Data sharing

1.3 Basic tasks using rich client

Use the rich client to:
• Work with Teamcenter applications perspectives and views.
• Create and manage data.
• Print information about your data
• Search for data in the Teamcenter database.
• Exchange data between Teamcenter and external applications.
• Set options and preferences.

1.4 Getting started

Teamcenter is a virtual gateway to your company’s product information
connecting all who need to collaborate with product and process knowledge.
Teamcenter enables you to digitally manage your product and manufacturing
data in the context of the product life cycle.
Using Teamcenter software, you can:
• Provide all users in your global organization access to data in real time.
• Connect people, processes, and information while integrating with current

business systems.
• Establish a flexible solution to manage change in a globally distributed

environment.
• Create, capture, secure, and manage corporate knowledge for greatest

corporate leverage.
• Provide information to downstream applications, such as enterprise

resource planning (ERP) systems.

1.5 Teamcenter interfaces

The rich client interface is used by authors, manufacturing authors,
administrators, and other users to:
• Manage the design and configuration of product data.
• Create and maintain processes and process structures.
• Configure and maintain Teamcenter.
• Access data stored in the Teamcenter database.
The thin client interface is used by consumers, manufacturing consumers,

and reviewers to:
• View data, including product structure and variant information.
• Approve data attached to a workflow task.
• Visualize 2D drawings and 3D model.
The thin client interface is ideal for suppliers, production staff, and other
users who do not require extensive authoring or administrative access to
Teamcenter.

1.5.1 Rich client interface
The rich client interface has a standard menu bar and toolbar with options
that vary depending on the currently active perspective. You can place the
cursor over a rich client toolbar button to display a tooltip description.
1 Menu Each perspective provides some common menu

commands and other menu commands specific to
the perspective.
2 Toolbar Each perspective provides some common toolbars
specific to that perspective.
3 Application The application banner shows the name of the
banner active perspective and lists the current user and
role. You can click the user and role to display the
User Settings dialog box in which you can change
your current role if multiple roles are available to
your user.
4 Back and The Back and Forward buttons allow you to move
Forward between loaded Teamcenter perspectives. The
small arrows next to the buttons let you select from
the list of currently loaded perspectives.
5 Quick Search The Search box provides predefined quick searches
box using dataset, item ID, item name, keyword search,
and advanced search features.

6 Navigation The navigation pane provides quick access to

pane the data you use most. In addition to finding,
organizing, and accessing your data, you can
configure the display of the Teamcenter perspective
buttons in the navigation pane to display only those
perspectives that you use regularly to perform your
tasks.
7 Primary Primary application buttons provide access to your
applications most frequently used Teamcenter perspectives.
8 Secondary Secondary application buttons provide access to
applications Teamcenter perspectives you use infrequently.
9 Information Information center symbols convey where-used and
center where-referenced, access privilege, child count, and
status information about the selected object. To
display the information, point to the symbol. The
information displays in the form of a tooltip.
10 Clipboard The clipboard button displays the Clipboard
button Contents dialog box, which contains references
to objects that have been cut or copied from your
workspace. The total number of objects on the
clipboard is displayed to the right of the symbol.
Note
On Windows systems, operational status for the rich client interface
and the Teamcenter server is provided by the Teamcenter icon in
the system tray.
To display the running status dialog box, click the Teamcenter icon
in the system tray.

The server and user interface condition symbols show the current
status of the rich client interface and the Teamcenter server.
• The server status indicates the state of the Teamcenter server:
o The server is ready, but there is no current communication
between the client and the server.
o The server is busy.
o The server appears to be idle.
o The server appears to be disconnected.
• The client status indicates the condition of the rich client:

o The user interface is responsive.
o The user interface is unresponsive.

1.6 Starting Teamcenter sessions

When you log on to a Teamcenter client, you establish a Teamcenter session.
After the session is established and Teamcenter is running, you open the
application perspectives (rich client) or applications (thin client) used to
perform your tasks.

1.6.1 Logging on to the Teamcenter rich client
The rich client logon window has the following fields:

• User ID
This is a required value. User accounts are created by administrators in
the Organization application.
You must provide a valid account ID to interact with Teamcenter.
• Password
Passwords are created by administrators in the Organization application.
• Group
This is an optional value. A group is an organizational collection of users
who share data. A user account can belong to multiple groups and must
be assigned to a default group. Groups are created by administrators in
the Organization application. If you do not specify a group, the default
group associated with the user account is used.
• Role
This is an optional value. Function-oriented cluster of users that models
skills and/or responsibilities. The same roles are typically found in
many groups. Roles are created by administrators in the Organization
application. If you do not specify a role, the default role associated with
the group is used.
• Server
Specify the server to provide database access for your rich client session.
Servers are configured during installation.
Note
Depending on whether your site uses proxy servers, multiple
environments, or Security Services components such as single sign-on,
you may be required to select an environment or respond to one or more
additional authentication dialog boxes.

1.7 Using the Getting Started application

The Getting Started application lets you begin your work.
You can search for a part, open your worklist, view or edit product structure,
or view or edit classification data.
1 Find a part This option is the same as the Search box in the
navigation pane.
2 Open My Loads My Teamcenter with your worklist displayed,
Teamcenter if it has any tasks to perform or track, or loads My
or Worklist Teamcenter with your Home folder displayed.
3 View/Edit Loads and displays the Structure Manager application.

a product
structure
4 View/Edit my Loads and displays the Classification application.
company’s
classification
data
Note
The navigation pane also lets you start an application or search for data.

1.8 Working with the rich client navigation pane

The rich client navigation pane provides quick access to the data you use
most. You can use the rich client navigation pane to find and organize your
data and to help you perform common tasks, such as creating a part, creating
a dataset, or applying a status to a part.

1 Upper part of the • The reorder button above the Search

navigation pane box lets you display the Navigation Section
Ordering dialog box to hide sections or
change the order of sections in navigation
pane.
• Quick-open Search provides predefined

searches using dataset, item ID, item
name, keyword search, and advanced
search features.
• Quick Links provide access to your Home

folder, worklist, saved searches, and web
links.
• Open Items displays links to items that

are open in an active perspective.
• History displays links to Teamcenter

objects that you opened in the past. Links
are displayed with the most recently closed
object displayed at the top of the History
list.
• Favorites displays links to Teamcenter

objects that you have designated as
favorites.
• I Want To provides links to the tools

used to complete tasks that you perform
repeatedly, such as initiating a process or
change.
2 Primary application Provide access to your most frequently used
buttons Teamcenter applications.
3 Secondary application Provide access to the Teamcenter applications
buttons that you use infrequently.
4 Configure Provides access to the tools you can use to
Applications button configure the display of primary and secondary
applications.

Note
You can also show or hide the navigation pane.
To show or hide the navigation pane:
• Choose Window ® Navigation Pane.

1.9 Teamcenter perspectives

Some of the most commonly used Teamcenter perspectives include My
Teamcenter, Structure Manager, embedded viewer, Workflow Viewer, and
Change Manager.
• My Teamcenter is the workspace you use to manage your product
information, such as parts, documents, specifications, requirements.
My Teamcenter serves as the main access point for many commonly used
functions, such as creation of items, checkin/checkout, task management,
and query execution.
Note
Much of the basic functionality present in My Teamcenter is
available in many of the Teamcenter perspectives.
• Use Structure Manager to create, view, and modify product structures.

Structure Manager also manages product structures that were created in
an MCAD program such as NX. Addtionally, Structure Manager allows
creation of generic bills of materials that show different configurations
of components.
• The visualization tools available in Teamcenter, both the embedded

viewer and stand-alone Lifecycle Visualization, enable nontechnical users
to interpret design data, review product structure, and mark up issues
for collaboration.
• Workflow Viewer presents a dynamic user interface to view the progress

of a workflow process for an object, whether it is currently in process or
has already achieved its final status.
• Change Manager enables functionality to initiate, administer, review,

approve, and execute product changes.
By automating the change process, Change Manager can minimize
change-related rework and coordinate tasks to be performed by
individuals across the organization.

The rich client is configurable on a per-user basis with user-based client

configuration persistent between sessions.
You can:
• Include additional views in a perspective.
• Save provided perspectives in new configurations.
• Create new perspectives based on provided perspectives with views

removed or added.
• Display different views of the same data or rearrange views to display

multiple sets of information simultaneously.

1.10 Teamcenter rich client perspectives and views

Within the Teamcenter rich client user interface, functionality is provided
in perspectives and views. Some applications use perspectives and views to
rearrange how the functionality is presented. Other applications use a single
perspective and view to present information.
• Perspectives
Are containers for a set of views and editors that exist within the
perspective.
o A perspective exists in a window along with any number of other

perspectives, but only one perspective can be displayed at a time.
o In applications that use multiple views, you can add and rearrange
views to display multiple sets of information simultaneously within a
perspective.
o You can save a rearranged perspective with the current name, or

create a new perspective by saving the new arrangement of views
with a new name.
• Views and view networks

In some Teamcenter applications, using rich client views and view
networks, you can navigate to a hierarchy of information, display
information about selected objects, open an editor, or display properties.
o Views that work with related information typically react to selection

changes in other views.
o Changes to data made in a view can be saved immediately.
o Any view can be opened in any perspective, and any combination of

views can be saved in a current perspective or in a new perspective.
o A view network consists of a primary view and one or more secondary

views that are associated. View networks can be arranged in a single
view folder or in multiple view folders.

1.10.1 Open a rich client perspective
You open an application perspective in the rich client in any of the following
ways:
• Click the application button in the navigation pane.
• Select the perspective from the Window→Open Perspective menu.
• Select an object in a navigation view and use the Send To shortcut menu
command to select an application.
• Double-click an object in a navigation view to open the perspective

associated with that object type.
For example, to open My Teamcenter in the rich client, click My Teamcenter

in the navigation pane.
If you do not see My Teamcenter listed as a primary application, check for
the My Teamcenter button in the secondary application button bar at the
bottom of the navigation pane. You can use Configure Applications ( )
at the bottom of the navigation pane to find and place the My Teamcenter
button in the navigation pane.

1.10.2 Switch between open perspectives
Use any of the following methods to change from the currently displayed open
perspective to another open perspective:
• Use the Back button in the toolbar, its associated menu, , or
Ctrl+Shift+F8 to display an application opened before the current
application.
• Use the Forward button in the toolbar, its associated menu, , or

Ctrl+F8 to display an application opened before the current application.
• Hold down Ctrl+F8 to display a Perspectives menu, and then release F8

and use your mouse or your keyboard arrows to select the perspective to
display.

1.10.3 Save, reset, or close a rich client perspective
To save the currently active perspective when you have arranged a useful
layout of views and view networks:
1. Choose Window®Save Perspective As.
2. Enter a new name for the perspective.
3. Click OK.
To restore a perspective to its default state, choose Window®Reset

Perspective. This returns all default views to their original locations.
You close an application perspective in rich client in any of the following ways:
• Click the X in the application banner.
Note
If you click the X in a view tab, only the selected view is closed and
the application perspective remains active.
• Select the application, and then select Window®Close Perspective.

1.11 Configuring the display of applications

You can configure the display of applications in the navigation pane by
choosing a command from the Configure Applications menu at the
bottom of the navigation pane. Menu commands include the following:
• Show More Applications
Shows more applications in the listings for primary applications and
secondary applications.
• Show Fewer Applications

Shows fewer applications to the listings for primary applications and
secondary applications.
• Navigation Pane Options

Specifies and organizes applications for listing as primary applications
and secondary applications.
• Add or Remove buttons in the Navigation Pane Options dialog box.

Moves applications between the primary applications and the secondary
applications list.
Note
You can drag the sash up or down in the navigation pane to adjust
the number of application buttons that appear in the primary and
secondary application lists. If the secondary application area cannot
contain all the applications, the applications that do not fit are
displayed at the bottom of the Configure Applications menu .

1.11.1 Display primary and secondary applications
For each application you want to display in the navigation pane as primary or
secondary applications, follow these steps:
1. Click at the bottom of the navigation pane and choose Navigation

Pane Options.
2. In the Navigation Pane Options dialog box, select applications from the
Available Applications list and move them to the Primary Applications
list or Secondary Applications list using the button.
Tip
You can change the display order of the applications using the
up arrow and down arrow buttons located next to the Primary
Applications or Secondary Applications lists.
3. Click OK.

1.12 Set your own user variables for the classroom activities
A user number and user ID are assigned to each student in class.
Prior to working with activities, you MUST enter your own user information
on the title page of the electronic activities. Your user variables then appear
in the activities.
Set them as supplied by your instructor.
Make sure to click Save to save your user variables.

1.13 Activity
In the Introduction to Teamcenter section, do the following activity:
• Start Teamcenter and open the My Teamcenter perspective.

1.14 Summary
The following topics were taught in this lesson:
• Basic concepts of product lifecycle management (PLM)
• An overview of some commonly used Teamcenter perspectives
• How to configure the navigation pane

Lesson
2 Working in My Teamcenter
Purpose
The purpose of this lesson is to introduce the basics of working in My
Teamcenter and organizing your working environment.
Objectives
After you complete this lesson, you should be able to:
• Work in My Teamcenter views.
• Organize data in folders.
• Use various commands to work with data.
Help topics

Working in My Teamcenter
2.1 Basic My Teamcenter concepts

My Teamcenter displays product information as various graphical objects.
Each user has a unique personal My Teamcenter perspective. Therefore,
although you may share product information across the enterprise with other
users, you can always organize this information in the way that best meets
your individual needs.
The My Teamcenter perspective consists of component views, for selecting
objects and navigating hierarchies, and various related views for displaying
and working with summaries, details, impact analyses, and related
information.
Along with the various views, the user interface consists of menus, toolbar
icons, symbols, and display panes. Some of these are generally available in
Teamcenter, while others are specific to My Teamcenter or to a particular
scenario in My Teamcenter.

2.2 Basic My Teamcenter tasks

You can use My Teamcenter to perform the following tasks:
• Create folders to organize commonly referenced objects.
• View the contents of your Home folder, My Worklist, My Projects, My

Links, My Saved Searches, and My View/Markup.
• Perform and track tasks.
• Send and receive mail.
• Open objects, automatically launching the related Teamcenter application.
• Search for objects, both in your local site database and at remote sites,
using predefined queries.
• Compare search results to other searches or other open search results.
• Create and manage items, item revisions, and datasets.

2.3 My Teamcenter views

The Teamcenter rich client provides the My Teamcenter perspective
consisting of multiple views.
By default, the My Teamcenter perspective displays the Home component
view beside the navigation pane, and the Summary, Details, Impact Analysis,
Viewer, JT Preview, and Process History views. Additional views can be
used in the My Teamcenter perspective, such as the MS Word, Search, and
Simple Search views.
For a list of views provided with the My Teamcenter perspective, choose
Window®Show View®Other to display the Show View dialog box, and then
expand the Teamcenter folder.

2.4 Searching in Teamcenter

The Teamcenter search functionality lets you find data in the Teamcenter
database.
The Quick Search feature in the navigation pane lets you search for data by
specifying the dataset name, item ID, item name, or a keyword.
Note
Quick search results cannot be saved to your saved searches list.
You can use saved queries to search for your work in the Teamcenter database
or in databases that are part of a Multi-Site Collaboration network. Saved
queries are grouped into three categories:
• My Saved Searches
This category contains queries that you ran previously and chose to save
for later use.
You can save the results of a search and add the search to your My Saved
Searches list. In both the rich client and thin client, you can share a
saved search. In the rich client, you can restrict sharing to specified
groups of users.
• System Defined Searches

This category contains both standard queries and custom queries defined
by your Teamcenter administrator. Standard queries allow you to search
by common parameters such as item identifier. Custom queries allow you
to search for data that is unique to your site or company.
• Search History
This category contains the most recently run queries. By default, the
last eight queries are listed, but you or the administrator can change the
number of queries shown.

2.5 Organize data in folders and pseudofolders

A folder is a container for an aggregation of objects. Some folders, such as
the default Home , Mailbox , and Newstuff folders, have unique icons.
You can use folders to organize both company-wide and individual user data.
• Your company may create a visual method of organizing data using folders.
• Folders can be nested to practically any extent desired.
• Data, such as your parts, documents, drawings, can be referenced by any

number of folders.
• A folder in Teamcenter is not the same as a directory in the operating

system. When you delete a folder in Teamcenter, only the folder is deleted,
not the contents of the folder.

A pseudofolder is a special container that stores and displays item and

item revision relations in My Teamcenter.
Pseudofolders let you easily see and navigate to objects related to the current
object, because pseudofolders are configured in hierarchical structures.
• Teamcenter automatically creates pseudofolders to display relations for
many item types.
• You can use preferences to specify properties displayed as a pseudofolder

under a node for an object.
Note
Pseudofolders show relations, but pseudofolders are not physical folder
objects in Teamcenter.

2.5.1 Home, Newstuff, and Mailbox folders
The My Teamcenter application always contains the three default folders:

Home , Mailbox , and Newstuff . These folders are automatically
created by the system.
• Home
The objects you want to work with in the My Teamcenter application
can be placed within your Home folder or within some folder structure
beneath the Home folder.
• Mailbox
The Mailbox folder is the receiving point for any Teamcenter mail that
has been sent to you. When you receive new Teamcenter mail, you see an
envelope object in your Mailbox folder.
• Newstuff
The Newstuff folder is the default folder for newly created database
objects. You can designate other folders as the default location for newly
created database objects. Objects remain in a folder until you move or
remove them.

2.5.2 Working with folders
Folders are a flexible way to organize your product information. Folders can
contain references to other objects including other folders.
Use Teamcenter to:
• Create a new folder.
• Rename a folder.
• Print a folder.
• Delete a folder.

2.5.3 Create a new folder
1. Choose File®New®Folder to create a new folder.
2. Set Type to Folder for general-purpose folders.
3. Click Next to proceed.

Key points
Key points about the New Folder dialog box:

• A red asterisk indicates a required entry.
• Enter a short descriptive name. The limit is 128 ASCII characters.
• (Optional) You can enter a general text description of up to 240 ASCII

characters.

2.5.4 Rename a folder
1. To change the name of a folder, right-click the folder object and choose
Edit Properties.
The Check-Out dialog box appears.
2. (Optional) Type a value in the Change ID box and add comments.
3. Click Yes to check out the object.

The Edit Properties dialog box for the selected folder object appears.
4. In the Edit Properties dialog box, you can enter a new name and/or
description for the folder, if desired.
Note
You may need to scroll down to access the Name and/or Description
boxes to edit.
5. Click Save and Check-In , Save , Cancel Check-Out , or Close .

2.5.5 Reorder objects in a folder or view
You can reorder objects in a folder or view in My Teamcenter using the Move
command.
1. Select an object in a My Teamcenter folder or view.
2. Click View Menu for the folder or view.
3. Choose the applicable Move command.

For example, choose Move→Up to move the object closer to the top of the
list of objects in the My Teamcenter folder or view.

2.5.6 Print a folder
• Select the folder and choose File®Print or File®Print....
Choose File®Print to print the folder name and a listing of the folder contents.
Choose File®Print... to access additional print options.

2.5.7 Delete a folder
1. Select the folder object and click Delete .

A confirmation dialog box appears so you can confirm the deletion.
2. Click More to list the object or objects selected for deletion.
3. Click Yes if you want to delete the folder.

Note
When deleting a folder, the contents of the folder are not deleted.
The folder contents remain in the database and can be located and
retrieved using the search feature in My Teamcenter.

2.6 Add favorites to organize your data

You can use favorites to track objects you access frequently, such as parts,
forms, or processes.
In the rich client, use either of the following methods to add the objects to
your Favorites list in the navigation pane:
• Right-click the object and choose Add to Favorites .
• Select the object in any hierarchy or detail view and drag it to a folder in
the Favorites list in the navigation pane.
In the thin client, use the following method to add the objects to your
Favorites list in the navigation pane:
1. Hold the cursor over the object to display the action menu .
2. Choose Add to Favorites .
To display the object, click the link in the Favorites list. The file is opened in
the application associated with the object or data type. For example, clicking
a link to a Word document opens the file in Microsoft Word. Clicking a link to
an item revision opens the item revision in My Teamcenter.
Note
You can organize your favorites into folders using the Organize
Favorites dialog box. Click Organize in the Favorites section to access
the Organize Favorites dialog box.

2.6.1 Add a subfolder to your Favorites list
1. Click the Organize link in Favorites section.
2. In the Organize Favorites dialog box, click Create New Folder .
3. Type a name for the new folder and click OK.
4. Click Close.

2.6.2 Rename a folder in the Favorites list
1. Click the Organize link in Favorites section.
2. In the Organize Favorites dialog box, select the folder to rename.
3. Click Rename .
The Rename favorites folder dialog box appears.
4. Type the new folder name in the New name box.
5. Click OK.
6. Click Close.

2.6.3 Remove a link or folder from the Favorites list
1. Click the Organize link in the Favorites section.
2. In the Organize Favorites dialog box, select the link or folder from the list.
3. Click Delete .
4. Click Close.

2.7 Object references

While it appears that object folders contain other objects (because that is
what you see) the folders actually contain references to the objects.
The distinction is subtle but very important. Several folders can contain
references to the same object, however, that object is only stored once in the
Teamcenter database.
Therefore, these folders provide references to the same product information.
References allow product information to be shared throughout your enterprise
without having to make multiple physical copies of the data.

2.8 Cutting, copying, pasting, and deleting data objects

You can use cutting, copying, and pasting to move data in your workspace by:
• Cutting an information object from one application and pasting it into
another Teamcenter application.
• Copying data to the clipboard and pasting it into another Teamcenter

application.
• Copying data to the clipboard and pasting it into an application outside

the Teamcenter environment.
If you have delete permission for an object, you can also delete data from the
Teamcenter database, but you cannot delete an object from the database if
that object is referenced in multiple locations.
To delete an object from the database, you may need to:
• Perform a where-referenced search to locate all references to the object.
• Contact all the owners of the references and ask them to delete their
references to the object.
• When there are no remaining references, you can delete an object for
which you have delete permission.
Note
An object contained in multiple folders can be deleted by a single action
if the object is not referenced by other nonfolder objects.

2.8.1 Cut data objects
Select the objects that you want to cut, and do one of the following:
• Click Cut on the toolbar
• Press Ctrl+X
• Choose Cut from the shortcut menu
• Choose Edit®Cut.
The object reference is removed from its current location and placed on the
clipboard.
Note
The Cut menu command removes a reference to an information object,
but it does not delete the actual object from the database. To delete an
object from the database, use the Delete option.

2.8.2 Copy data objects
Select the objects that you want to copy, and do one of the following:
• The Copy on the toolbar
• Press Ctrl+C
• Choose Copy from the shortcut menu
• Choose Edit®Copy.
A reference to the object is copied from its current location and placed on both
the Teamcenter and system clipboards.

2.8.3 Pasting data objects
The Edit menu paste commands create a relation between a copied object and
the destination object, such as selected folder or item.
When the system pastes an object reference into an item or item revision
container, a relationship is established. This relationship is referred to as the
default relation type.
Because data objects are complex entities, the paste options are more complex
than similar options in other software applications.
Menu Description
command
Paste Creates a relation between a copied object and the
destination object.
It is important to select the proper destination for the
data object reference before choosing the Paste menu
command. You must have read and write privileges to
the destination object.
Paste Special Allows you to specify a relation type rather than using
the default paste relation when pasting an object
reference into an item or item revision.

2.8.4 Paste the contents of the clipboard
1. Cut or copy the data object to the clipboard.
2. Select the destination container for the copied object reference and do
one of the following:
• Click Paste on the toolbar
• Press Ctrl+V
• Choose Paste from the shortcut menu
• Choose Edit®Paste.

2.8.5 Paste an item or item revision and specify the relation type
1. Cut or copy the data object to the clipboard.
2. Select the destination container for the copied object reference.
3. Choose Edit→Paste Special.
4. In the Paste Special dialog box, select a relation type from the list and
click OK.
Note
If your Teamcenter administrator has configured mandatory
properties (attributes) for the relation type you select, the
Properties dialog box appears. If the Properties dialog box appears,
enter values for the mandatory properties and click OK.

2.8.6 Pasting object references to applications outside the Teamcenter

environment
References to objects that have been copied to the system clipboard can be
pasted outside of the Teamcenter environment as URLs.
Outside of the Teamcenter environment, you can access the data object by
clicking the URL. This launches Teamcenter and displays the data in My
Teamcenter.
Note
To access objects from a URL, the Teamcenter rich client must be
installed on your machine and you must have a valid user ID and
password.

2.9 Dragging and dropping data objects

In situations where drag-and-drop capabilities are supported by the current
application, you can move data in the Teamcenter rich client by:
• Dragging a data object from one location to another.
For example, you can add an item to your favorites list by selecting it in My
Teamcenter and dragging it to the Favorites area in the navigation pane.
Note
When you drag and drop an object in a structure management
application such as Structure Manager, the system makes a copy of
the object in the new location and does not move the original object.
• Dragging a data object from one application to another application.
Note
Drag-and-drop capabilities vary by rich client application. For example:
• In the My Teamcenter Summary view, you can drag and drop a
dataset file on the view header to attach the dataset to the currently
selected item revision object.
• In the My Teamcenter Viewer view, drag-and-drop capabilities are

not available for dropping dataset files on the view header.
• In Structure Manager, if you drag and drop a dataset onto a BOM

line, the dataset is not attached, although it is created in the
Newstuff folder.
You can also open applications by dragging an object and dropping it on the
application button in the navigation pane.
For example, you can drag an item revision representing a subassembly from
the My Teamcenter tree and drop it on the Structure Manager button in
the navigation pane. The system opens the Structure Manager application
and shows the subassembly structure.

You can select multiple files and use drag and drop to link them to a business
object. For each file a dataset is created and linked to the item revision.
• When you drop files on an item in Teamcenter, the New Datasets for
Multiple Files dialog box displays file information in a table.
• The table populates the most suitable Dataset Type, Tools, and Reference
based on the Default_dataset_type preference set by your administrator.
In the rich client you can drop multiple files on following types of object and
their subtypes:
• Items and item revisions
The relation between the item or item revision and the dataset is
automatically selected, based on the default paste relation for the item
or item revision type.
• Folders
Datasets are pasted in corresponding folders.
• BOM line objects

Created objects are pasted in the user Newstuff folder.

2.10 Activities
In the Working in My Teamcenter section, do the following activities:
• Find items and add them to a favorites folder.
• Create and rename a folder.

2.11 Summary
• Working in My Teamcenter views
• Organizing data in folders
• Using various commands to work with data

Lesson
3 Working with items in Teamcenter
Purpose
The purpose of this lesson is to learn the basics of working with Teamcenter
item and item revision objects.
Objectives
• Identify items and the item structure.
• Create an item and populate it with master data.
• Create a new item revision.
• Create new items or item revisions based on existing data.
Help topics

Working with items in Teamcenter
3.1 Items and item revisions

Items and item revisions are the fundamental data objects used to manage
information in Teamcenter.
• Items are structures that are generally used to represent a product, part,
or component. Items can contain other data objects including other items
and folders.
Items can contain other data objects including other items and folders.
You can group and organize product information for each product, part, or
component.
An item always contains the same data objects, regardless of which user’s
workspace displays the item.
• Item revisions are data objects used to manage revisions to items.
• Each item revision has one or more associated sequence IDs. Checkout
actions increment the sequence ID for the item revision, with the most
recent sequence ID becoming the default.
• Naming rules that control the format of the item ID, item revision ID, and
name may be in effect at your site. These rules are managed by your
administrator using the Business Modeler IDE application.
Key points
• An item can be thought of as a package that contains all data related
to that item.
• Each item has at least one item revision.
• Each item revision has at least one sequence ID.
• Items store all revisions of the item.

3.1.1 Basic item structure
An item in Teamcenter is a structure of related objects. The basic structure of

any item consists of the following minimum objects:
Item
Item Master (Form)
ItemRevision
ItemRevision Master (Form)
• Item
Collects data that is globally applicable to all revisions of the item.
• Item Master (Form)

A form object that is often used to extend the stored property data for
an item.
• ItemRevision
Collects data that is applicable to a single revision of the item.
• ItemRevision Master (Form)

A form object that is often used to extend the stored property data for
an item revision.
Note
Customer properties can be added to the Item and ItemRevision
and their children. Siemens PLM Software recommends not to use
customer-specific attributes in the Item Master and ItemRevision
Master forms.

3.1.2 Item types
The term item is used to generically describe all types of items that exist in
the system.
The system comes with several generic item types including:
• Item
• Document
• EngChange
Note
Many customers define additional item types in their system. This
allows for more specific categorization of data beyond these types.

3.2 Creating items

The New Item dialog box provides a wizard-like tool for creating items,
entering item and item revision attribute information, and assigning the
item to a project.
The New Item dialog box is displayed by the File®New Item menu command.
• You can select the appropriate business object type.

• You can then enter item information, such as item ID, Revision, Name
and Description.
(Optional) You can also define custom attributes, as implemented at your
site, by expanding the Additional Item Information and Item Revision
Information sections.

Key points
Steps required to create a new item are indicated by a red asterisk. Once the
required steps are performed, you can continue through the remaining steps
in order, select individual steps from the list, or exit the wizard.
• You do not have to work through the steps sequentially, nor is it necessary
to complete all of the steps.
• If required item or item revision attributes are defined for the item
business object, values must be entered before the system can create the
item.

3.2.1 Create an item example
1. Select a container for the item, such as a folder or another item.
2. Choose File→New→Item.
The system displays the New Item dialog box.
3. In the Business Object Type step, select the item type that you want
to create.
Note
The item types displayed in this dialog box are controlled by your
administrator. It is possible that you may be unable to create item
types that are visible to you in your workspace.
4. Click Next.

5. In the Object Create Information step, under the Item Information

section, do the following:
• Type a name for the item.
• Enter an ID and revision for the item, or click Assign to automatically

generate the item ID and revision identifiers.
Note
If left blank, the ID and Revision values are automatically
generated. Description and Unit of Measure are optional.
Note
The Name and Description boxes may contain initial values
determined by property rules implemented at your site. You can
replace such values, but you cannot specify a null value by clearing
the box. If you clear the box, the initial value is reapplied to the
property when you save the new item.

6. (Optional) You can also expand the Additional Item Information and
Item Revision Information sections and define custom attributes, as
implemented at your site.
Note
Your administrator can create custom attributes (properties) to
apply to the item or item revision as defined and implemented at
your company.
7. At this point, you have provided all of the information necessary to define
the item.
Click Next to move to the next step and further define the item or click
Finish to create the item immediately.
Note
The item is not created until you click Finish.

3.3 Activity
In the Working with items in Teamcenter section, do the following activity:
• Create an item and edit properties.

3.4 Creating new items based on existing items or item revisions

You can create new items from existing items or item revisions.
The Save As menu command creates new items from existing items or item
revisions. The copy options for the objects related to the item revision differ
depending on whether an item or item revision is selected as the basis for
the new item.
• When you use an item as the basis, most of the objects related to the
selected item revision are copied as references. The exceptions are the
item revision master and BOM view revision. These are copied as new
objects.
• When you use an item revision as the basis, you have the option to copy
the related objects as references, as new objects, or not to copy the selected
objects.

3.5 Activity
• Create a new item based on existing data.

3.6 Creating item revisions

The initial item revision associated with an item is automatically created
when the item is created.
To create subsequent revisions for the item, select an existing item revision
and choose File®Revise.
• Creating a new revision copies the objects and object references related
to the existing item revision to the new revision based on your corporate
configuration.
• The related objects can be copied as references, new objects, or not at all.
Note
The method of handling related objects when revisions are created
may be automatically configured for your site, and you may not
be able to change it.

3.6.1 Create a new revision of an item
1. Select an item revision in the tree or Details table to be the basis of the
new revision.
Note
To create a revision of an item, you must have write privileges to
the item.
2. Choose File®Revise.
The system displays the Revise dialog box.
3. (Optional) Enter a description of the new revision.

Note
The unit of measure is carried over from the original item and
cannot be modified.
At this point, you have provided all of the information necessary to create
the item revision.
4. Click Next to move to the next step and further define the item revision or
click Finish to create the item revision immediately.
Tip
The item revision is not created until you click Finish. If mandatory
item revision master attributes are defined for the item type, you
must click Next and enter attribute information before you can click
Finish.

3.7 Activity
• Create a new item revision.

3.8 Sequences
You use sequences if your business requires additional management of
progress within revisions.
• A sequence is an iteration of the object, complete with properties and
relations. A sequence of a revision is similar to a version of a file, but the
sequence encompasses all information about the object.
• Sequences record a sequence of changes to a work-in-progress. The

information contained in each sequence varies depending on the
modifications made to the new sequence.
• A sequence is complete and represents a single point for the object as

it is prepared for release.
When you create an item revision, an initial sequence, to which Teamcenter

assigns an initial sequence ID, is also created. This sequence becomes the
active, or default, sequence.
• Checkout actions increment the sequence ID for the item revision, with
the most recent sequence ID becoming the default.
• The default sequence is the only sequence you can check in and check out.
Attempting to check out a nondefault sequence results in an error.
• Only one sequence can be active at any given time for an item revision.
• A sequence does not track incremental changes.
• Canceling a checkout decrements the sequence ID and discards any

changes that have been saved to the database.

3.8.1 Sequence ID display
Teamcenter displays the sequence ID appended to the item ID and revision,

separated from the item revision by a semicolon (;). The sequence ID is
followed by a hyphen (-) and the object name. For example, the third checkin
for item revision 3540/A of part Bumper is displayed as follows:
3540/A;3-Bumper
• By default, the system displays only the active sequence.
• All sequences for an item revision can be found and displayed using
a search query.
Note
Sequence IDs can be hidden from view by your site administrator.

3.8.2 Managing revision sequences
• When you create a new item revision, such as from revision A to revision
B, the new revision starts with the first sequence ID.
• At checkin, the system automatically removes the oldest sequence when

you reach the limit.
• You can set immunity for sequences to prevent their automatic removal.
• You can remove sequences from an item revision by using either the
delete or purge actions.

3.9 Item and item revision relations

There are typically many pieces of information that describe or are related to
an item or item revision. Teamcenter uses relations to define the correlation
between data objects and items or item revisions.

3.9.1 Automatically defined relation types
Many item or item revision relations are automatically defined when you
create or add certain objects to an item or item revision structure.
For example, when you add a new item revision to an item, the new item
revision is automatically defined as a revision relation.
The automatically defined relation types are:
• Revision
• Item master and item revision master
• BOM view and BOM view revision
• Alternate ID
• JTSESSION and 3DMarkup

These relation types apply to datasets.
• IMAN_Drawing
Specifies the relationship between an NX part and a drawing dataset.
Note
Your site may be configured to automatically create relation types other
than those listed here.

3.9.2 User-specified relation types
In addition to the automatically defined relation types, the user-specified

relation types relate objects to items and item revisions.
These relationships are typically defined when you paste an object reference
into an item or item revision using the Edit→Paste or Edit→Paste Special
menu commands.
Note
If your administrator has defined mandatory properties for the type of
relation object you are creating, a dialog box lets you define attribute
values for the objects.
Relation type Description

Specification Detailed methods, designs, processes, and procedures
relations used to satisfy requirements.
Specification relationships can only be established with
item revisions, not with items. 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).
Requirement Criteria that must be satisfied by the item or item
relations revision. However, requirements often do not specify
how the criteria should be satisfied.
For example, an object related by a requirement
relation might specify maximum weight of a component
associated, but not how the component is constructed.
Attaches relations The Attaches relation is the default relation for
referencing a dataset to a document revision. These
relations are created between document revisions and
datasets.
Manifestation Nondefining snapshots of a particular aspect of an item
relations 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 (for example,
machining information) and that this information is
only accurate so long as the item revision does not
change. If the item revision changes, the NC program
files may no longer be accurate and may need to be
recreated.

Relation type Description

Reference General nondefining relationships of data objects to
relations items or item revisions. This relation type can be
thought of as a miscellaneous relation type.
Typical examples of reference relations are white
papers, field reports, trade articles, customer letters,
and lab notes.
Alias relations Specifies the relationship between an item or item
revision and an identifier object. It signifies how an
alias is defined.

3.10 Managing alternate and alias identifiers

Items and item revisions can be identified in a number of ways to match the
business practices of your enterprise and those of your business partners.
Initial identifier attributes, alternate identifiers, and alias identifiers are all
used to communicate information about items and item revisions.
Note
You can do this only if your administrator defined alternate and alias
identifiers in the database.

3.10.1 Initial identifier attributes
When an item or item revision is created, an initial identifier (ID) attribute is

assigned to the object.
Initial identifier attributes have the following characteristics:
• They are required.
• They are not case-sensitive.
• They are unique within the Teamcenter database.
• The identifier attribute cannot be modified if any revision of the item

has been released.

3.10.2 Alias identifiers
Alias identifiers store part numbers and other attribute information for
similar parts, and they can be associated with many items or item revisions.
Alias IDs let you store information about external entities.
For example, alias IDs can be used to do any of the following:
• Store parts according to internal naming conventions and also according
to the naming conventions of other companies, such as suppliers.
• Maintain a cross reference of the relationships between other

manufacturer’s part numbers and the part numbers used by your
organization.
• Distinguish between parts tracked in other systems.

For example, you can use the alias ID to indicate that a Teamcenter item
has information stored in an external database of part attributes. Based
on the alias ID, you know whether the Teamcenter item has information
stored in the separate database. This information can also be useful in
workflows.

3.10.3 Alternate identifiers

Alternate identifiers store information about part numbers and attributes
of the same part from different perspectives. They allow different user
communities to identify and display an item or item revision according to
their own rules rather than according to the rules of the user who created
the object.
Assigning alternate identifiers to a part at different stages of development
and production allows you to maintain a history of the lifecycle of the part.
Both alias and alternate identifiers are created within a context. The context
is used to denote a specific organizational focus, such as a supplier or a
department in your organization. You can also use identifiers to store custom
information, such as a supplier’s name and address or cost data.
Alternate identifiers have the following characteristics:
• An alternate ID identifies only one item or item revision in the database.
• Once created, the context and owning item revision cannot be modified.
• The identifier cannot be modified if any revision of the alternate has been
released.
• The item alternate cannot be deleted if any of the revision alternates

cannot be deleted.
• The last revision alternate of an item alternate cannot be deleted.
Alternate IDs let you define additional identifiers for an item that are then
useful for setting up appropriate display contexts. For example, the design
department can use item IDs, but other departments or other companies may
have other IDs. A single item can be assigned any number of IDs, each unique
within its context and controlled and assigned by its own naming rules.
The following example shows possible alternated IDs for an item:
MyItem123
123456789@dept01
K9999999999@company01
0000-9999999@company02
• A user in department 01 can set the display context to see all items with
their dept01 number.
• A manager that deals primarily with company 01 can set the context to
show all items with the company01 ID values.
• A designer can switch between display contexts, depending on the current

situation.

3.11 Open items and item revisions in My Teamcenter

Opening an item or item revision in My Teamcenter allows you to display
the object data in a tri-pane window.
In the tri-pane window, you can apply revision rule filters to sort through the
item revisions generated during the design process.
The tri-pane window displays the Item tree (upper-left) and Item Revision
tree (lower-left), as well as the standard panes and views (right).
• When you open an item, the item and all its related item revisions are
displayed in the Item tree, and the latest item revision is displayed in the
Item Revision tree.
• When you open an item revision, the associated item and all related item
revisions are displayed in the Item tree, and the item revision that you
opened is displayed in the Item Revision tree.
To open an item or item revision in My Teamcenter:

1. Select an item or item revision in the My Teamcenter tree.
2. Choose File→Open.
The selected object appears in the tri-pane window.

3.12 Filter the item revision display in My Teamcenter
Use Revision selection in My Teamcenter to filter the item revision

display.
The item revision display can be filtered by revision rules and by released,
in-process, or working revision status.
Note
Revision rules and status are explained in later lessons.
To filter the item revision display in My Teamcenter:
1. Select an item or item revision in the My Teamcenter tree.
2. Choose File→Open, or select Send To®My Teamcenter from the shortcut

menu.
3. Select the item or an item revision from the tree in the upper-left or
lower-left pane in the tri-pane window.
4. Click Revision selection on the toolbar between the upper and lower
panes.
The system displays the Revision Selection dialog box.
5. Select the filter to be applied to the display list using Released,

In-Process, or Working, or select a revision rule from the Revision rule
list.
The item revisions matching the filtering criteria are displayed in the
dialog box, arranged from latest to earliest revision.
6. Select an object in the Revision Selection list to display it in the Item

Revision pane.

3.13 Summary
• Identifying items and the item structure
• Creating an item and populating it with master data
• Creating a new item revision
• Creating new items or item revisions based on existing data

Lesson
4 Viewing and modifying object

properties
Purpose
The purpose of this lesson is to learn how to use various methods to view and
modify Teamcenter object properties.
Objectives
• View objects and their properties.
• Modify object properties.
• Configure table data display.
• Print information about your data.
Help topics

Viewing and modifying object properties
4.1 Overview of object properties

Objects have properties.
The properties associated with your data objects can be viewed in the Details
table or in the Properties dialog box.
• Object properties, such as ownership, description, and unit of measure,
can be viewed and modified, either for a single object or for multiple
objects, using the Properties dialog box.
o Click Check-Out and Edit or press Alt+E to check out the objects.
o Click Cancel or press Alt+C to cancel changes and close the dialog box.

• Property modifications can automatically be propagated to related objects

using type and relation filters.
For object properties, the Properties dialog box can incorporate a Check-Out
and Edit button that lets you quickly check out an object and edit applicable
information in an Edit Properties dialog box.

You can then:

• Click Save and Check-In or press Alt+I to save changes, check in the
object, and close the dialog box.
• Click Save or press Alt+S to save the changes and retain the dialog box.
Note
If you click Save or press Alt+S, and then click Cancel Check-Out
or press Alt+O, the changes are reverted and the checkout status
for the object is canceled.
• Click Cancel Check-Out or press Alt+O to cancel the checkout without

saving the changes and close the dialog box.
• Click Close or press Alt+C to close the dialog box.

4.1.1 View property values in the Details table
1. In the component view or tree pane, select the parent of the object or
objects that you want to display.
2. Click the Details tab.

The system displays the properties of the children of the selected object
in the Details table.

4.1.2 View properties of a single object in the Properties dialog box
1. In the component view or tree pane or Details table, select the object that
you want to display.
2. Choose View→Properties or right-click the object and choose View

Properties.
The system displays the properties of the selected object in the Properties
dialog box.
• Click Check-Out and Edit or press Alt+E to check out the objects.
• Click Cancel or press Alt+C to cancel changes and close the dialog box.
Note
The Properties dialog box for a dataset may display read-only boxes
for relationships such as UG Expressions, UG WAVE Geometry, and
various others. These boxes, which are normally blank, are used to
display relationship information stored in the database.

4.1.3 View properties of multiple objects in the Properties dialog box
1. In the component view, tree pane, or Details table, select those objects for
which you want to view properties.
Tip
To select contiguous objects, click the first object, press the Shift
key, and select the last object.
To select multiple noncontiguous objects, click the first object, press
the Control key, and select the remaining objects.
2. Choose View→Properties or right-click the selected objects and choose

View Properties.
The system displays the properties of the selected objects in the Common
modifiable properties dialog box.
• Click Check-Out and Edit or press Alt+E to check out the objects.
• Click Cancel or press Alt+C to cancel changes and close the dialog box.

4.1.4 Modify the properties of a single object
1. Select the object that you want to modify from the tree or Details table.
2. Choose Edit→Properties or right-click the object and choose Edit

Properties.
In the Check-Out confirmation dialog box:

a. (Optional) Type a value for Change ID and add comments.
b. Click Yes to check out the object.

The system displays the properties of the selected object in the Edit
Properties dialog box. The properties that can be modified vary from
object to object, and you must have write access to make modifications.
Note
You cannot change ownership of the selected object from the
Properties dialog box. You must use the Change Ownership option
on the Edit menu.
3. Modify the property values, as required.

If errors occur during the update process, a dialog box displays the objects
and properties on which the failure occurred and states the cause of the
failure. This error report can be saved or printed to an HTML or text file.

4.1.5 Modify the properties of multiple objects simultaneously
1. Select the objects in the tree or Details table.

Note
You must have write access to modify object properties. If you do
not have access to one or more of the selected objects, an error
message is displayed.
2. Choose Edit→Properties or right-click the object and choose Edit

Properties.
If you have previously applied filters for propagating property
modifications to related objects, the affected objects are displayed as
children of the selected objects.
3. In the Check-Out confirmation dialog box:
a. (Optional) Type a value in the Change ID box and add comments.
b. Click Yes to check out the object.
The Common Modifiable Properties dialog box displays only those

modifiable properties that are common to all of the selected objects.

4. Select the cells corresponding to the property values that you want to
modify.
You can select a single cell, multiple cells in the same column, or all cells
in a column. To select all cells, click the column header.
Note
The ID properties of multiple objects cannot be modified, because
duplicate object IDs are not permitted in Teamcenter.
5. In the Additional Options box at the top of the dialog box, enter or
select a new value.
• This area displays either a box or a list depending on whether the

values associated with the selected properties are strings or lists of
values.
• When using the box to enter string values, you can click Cancel
Changes to revert to the last submitted value at any time prior to
submitting the changes.
6. Click Submit Changes or press the Enter key.

The modifications are reflected in the table but are not updated in the
database until you click Apply or OK.

If errors occur during the update process, a dialog box displays the objects
and properties on which the failure occurred and states the cause of the
failure. This error report can be saved or printed to an HTML or text file.
Note
Save and Check-In and Save apply changes for all rows, not
just the selected rows.

4.1.6 Find and replace property values and add prefixes and suffixes
• When modifying string properties, you can click Additional Options

to find and replace a specific text string or add a prefix or suffix to a
property value.
Note
The system displays the Change Owner/Group dialog box when the
Additional Options feature is used to modify the Owner or Group ID
properties.

4.1.7 Relation properties
Objects are associated by relations.

For example, datasets (secondary objects) are associated with item revisions
(primary objects) using relation objects. The meaning of the secondary object
may vary from one context to another. Properties on relations enable you to
record information specific to the association or context in which the object
is used.
Your administrator can create custom attributes (properties) to apply to
relation business objects in the system.
A single item can be associated to multiple items or contexts. Objects are
associated by relations, and the meaning of the relation may vary from one
context to another.

4.1.8 Modify the properties of a single relation object
1. In the component view, tree pane, or Details table, select the secondary
object for which you want to view relation properties.
2. Choose Edit→Properties on Relation or right-click the object and choose

Properties on Relation.
The system displays the properties of the relation between the selected
secondary object and the primary object.
Note
You must have write access to modify relation properties.
3. Modify the property values, as required.
4. Click OK or Apply.

4.2 Configuring table data display in the rich client

You can configure the way data is displayed in tables throughout the rich
client interface. The method of configuring data display in application table
panes, such as in Structure Manager, differs from the method of configuring
data display in view tables, such as the Details view in My Teamcenter.
After you configure the table data display using either method, you can:
• Apply the configuration to the current table.
• Save the configuration and apply it another time you want to view data.
To configure the data display in an applications table pane, right-click a

column header and choose the applicable command from the Table Function
Menu.
To configure the data display in a view table, click View Menu and choose
the applicable command from the view menu.

4.2.1 Configure the Details view table
1. In the Details view, click View Menu and then choose Column from
the view menu.
The Column Management dialog box appears.
2. Add or remove columns from the Details view table.

a. To add a column, select a property from the Available Properties list
and click Add to Displayed Columns .
b. To remove a column, select a property in the Displayed Columns list

and click Remove from Displayed Columns .
3. (Optional) Click Move Up and Move Down , to the right of the

Displayed Columns list, to adjust the order of the displayed columns.
4. Click Apply to apply the configuration to the current view, or click Save to
save the configuration for later use.

Note
You can use the Apply Column Configuration command on the
view menu to:
• Apply a saved configuration.
• Restore the default configuration. This is the only way to restore

columns removed using the right-click Remove this column
command.
You can use the Save Column Configuration command on the view
menu to save the current configuration of the table display.
5. Click Close to close the Column Management dialog box.

4.2.2 Reposition columns in a table
1. Click the header of the column that you want to move and hold the mouse
button.
Note
For ease of use, leave the Object and Type columns in the first and
second positions in the table.
2. Drag the column to the desired position in the table and release the
mouse button.
The column appears in the new position.

4.2.3 Sort data in a table
1. Click View Menu in a table view.
2. Choose Sort from the menu.

The Sort dialog box appears.
Table data can be sorted in ascending or descending order using up to

three properties as sort criteria.
3. Select the primary property to be sorted on from the list in the Sort By
section. Select Ascending or Descending to designate how to sort the
property values.
4. (Optional) Select up to two additional properties to use as sort criteria by

selecting a property from the list in each of the Then By sections of the
dialog box. Select Ascending or Descending to designate how to sort
the property values.
5. Click OK to sort the property values in the table display or click Cancel to
close the Sort dialog box without sorting the property values.

4.3 Activity
In the Viewing and modifying object properties section, do the following
activity:
• Customize the Details view data display.

4.4 Printing information about your data

Use the Print and Print... commands on the File menu to display, format, save,
and/or print the following types of information about your Teamcenter objects:
• The hierarchical structure of a selected object and its descendant objects.
For example, you can select a folder and display all of the first-level
descendants or you can enter a level of descendants to be displayed. This
allows you to display and print any level of the structure.
• The hierarchical structure of a selected object (first-level descendant

objects only), including the object properties and corresponding values.
• The properties of a selected object and their corresponding values.
• The active Teamcenter table, as it appears in the application window.
Note
You can only print information related to a single selected object.
The following table describes the printing options and the expected output
for each option based on the selected object type.
Note
The following table describes only the Object Properties and Contents
options in the Print dialog box. The Application options in the Print
dialog box enable you to print the active table, tree display as it appears
in your Teamcenter window.
Selected
object type File®
®Print File®
®Print...®
®
Folder Displays the folder Objects Properties displays the folder
and its first-level properties.
descendant objects.
Contents displays the folder and its
descendant objects to the level in the
hierarchy that you specify.
Form Displays the form Object Properties displays the
properties. properties associated with the form.
Form Properties displays the property
values of the specific form.

Selected
object type File®®Print File®
®Print...® ®
Item or item Displays the item Object Properties displays the
revision or item revision properties of the item or item revision.
and its first-level
descendant objects. Contents displays the item or item
revision and its descendant objects
to the level in the hierarchy that you
specify.
BOM line Displays the BOM Object Properties displays the BOM
line structure line properties.
currently displayed
in Structure Contents displays the structure of
Manager. the BOM line as it is displayed in
Structure Manager.
Dataset Displays the Object Properties displays the
properties of the properties of the dataset.
dataset.
Data launches the tool associated with
the dataset and displays the contents
within the tool.
For example, if you select
a text dataset and choose
File→Print...→Data, you can select
the text editor in Tool Used and view
the contents of the file associated with
the dataset.
Other Displays the Object Properties displays the
properties of the properties of the selected workspace
workspace object. object.
Contents displays the object and its
descendant objects to the level in the
hierarchy that you specify.

4.4.1 Print object information
1. Select the object in the tree structure or Details table and choose
File→Print....
Note
The contents of the dialog box differ depending on the type of object
you select.
2. Select one of the following content options:
Object Properties Creates a report of the properties of the

selected object.
Contents Creates a report of the contents of the selected
object. When the Contents option is selected,
the Level text box is activated so that you can
define the level of content to be reported.
Increasing the content level is similar to
expanding nodes in a tree structure.
For example, if you type 1 in the Level
box, the selected object and its primary
components are included in the report. If you
type 2 in the Level box, the selected object,
its primary components, and the children of
the primary components are included in the
report. You can continue to increase the level
until you reach the bottom of the structure.
Application (HTML/Text) Creates a tabular report of the properties of
the selected object in HTML format.
Application (Graphics) Creates a graphical report of the active table
as it appears in the application window.
When this option is selected, the results are
sent directly to the printer. There are no
options for previewing and formatting the
report.
3. Click OK.
4. (Optional) Modify the print format settings.
5. Click Print or Save to print or save the output.
6. Click Close.

4.4.2 Print object information from the Properties dialog box
1. Select an object from the tree or Details table.
2. Choose View→Properties.
3. Click Print located in the lower-right corner of the dialog box.

The system displays the Print dialog box.
4. (Optional) Change the print format to Text. (HTML is the default print
format.)
5. (Optional) Modify the print format settings.
6. To save the file, open it in a Web browser or send it to a printer and

complete the process that is appropriate to the file type and desired
output.
Open HTML files in a Web browser
a. Click Open in Web Browser .

The system displays a web browser window.
b. Execute your browser’s print command.
c. Return to the Teamcenter window and click Close.
Print a text or HTML file
a. Click Print in the lower-right corner of the Print dialog box.

The system displays the Print dialog box.
b. Define the printer to which the file is sent.

You can accept the default printer or select a different printer from
the list.
c. Click Print.
d. Click Close.

Save output to a user-specified (HTML or text) file
a. Click Save in the lower-right corner of the Print dialog box.

The system displays the Save dialog box.
b. Navigate to the directory location where you want to save the file.
c. Type the name of the file, including the .htm, .html, or .txt extension,
in the File name box.
d. Click Save.
e. Click Close.

4.5 Activity
In the Viewing and modifying object properties section, do the following
activity:
• Print information about your data.

4.6 Summary
• Viewing objects and their properties
• Modifying object properties
• Configuring table data display
• Printing information about your data

Lesson
5 Creating and managing datasets
Purpose
The purpose of this lesson is to learn the basics of working with Teamcenter
dataset objects.
Objectives
• Identify datasets and dataset types.
• Create datasets using various methods.
• Understand and work with versions.
Help topics
Additional information for this module can be found in:

Creating and managing datasets
5.1 Dataset objects

Datasets are objects that manage files generated from non-Teamcenter
applications, such as, NX, Microsoft Word and Excel, WordPad, and so forth.
Double-clicking a dataset object launches the associated software application
and loads the file in the application.
Datasets are typically related to item revisions.
Examples of some dataset types:
Symbol Type File Purpose

Text .txt Text document
Microsoft Word .doc Microsoft Word document
Microsoft Excel .xls Microsoft Excel spreadsheet
DirectModel .jt 3D visualization model
UGMASTER .prt NX part file

5.2 Creating datasets

You can create a dataset using one of the following methods:
• By using menu commands
• By dragging a file from an operating system file manager onto a

Teamcenter folder, an item, or an item revision
In addition to being able to select dataset type before you import files, you can
also select files to import before selecting a dataset type.
• When you select a dataset type, and then click the import button, only the
files that match the selected dataset type are displayed.
• When you select Import first, only the dataset types that match the
selected file name extensions are available.

5.2.1 Create a new dataset
1. Select the folder, item, or item revision under which the new dataset
will reside.
2. Choose File→New→Dataset or press Ctrl+D.

The New Dataset dialog box appears.
Note
You can create a new dataset from a file by using the Import option
on the New Dataset dialog box.
3. Type a descriptive name (up to 128 ASCII characters) in the Name box.
This name is used as a label in the object area.
Tip
It is good practice to keep the names short so that you can see the
entire name in the My Teamcenter tree.
4. (Optional) Type a description (up to 240 ASCII characters) to help identify

this dataset in the Description box.

5. Select a dataset type from the Type bar by clicking the icon.
The Type bar displays the dataset types that you use the most.
If you do not see the type you are looking for, click More to display all
defined dataset types.
Note
The dataset types displayed in this dialog box are controlled by your
administrator. Therefore, you may be unable to create dataset types
that are visible to you in your workspace.
6. Select the Tool Used option to edit the dataset file if more than one option
is available.
Note
(Optional) You can also change Relation from the Relation list of
relations.

7. To select a file, click Select an import file to the right of the Import box.
The Upload File dialog box appears.
8. Navigate to the file to be imported, select the file, and click Upload.
The system closes the Upload File dialog box, and the path to the file
appears in the Import box.

9. Select Open on Create to launch the tool associated with the dataset and
immediately open the file upon creation.
10. Complete the procedure:

• To close the dialog box without saving the information you entered,
click Cancel.
• Click OK or Apply to save the information in the database.

The Paste dialog box appears.
Note
Clicking Stop ends the dataset creation process.
The new dataset object appears in your My Teamcenter tree.

If you selected the Open on Create option, the system launches the
tool associated with the dataset and opens the file.

5.3 Activity
In the Creating and managing datasets section, do the following activity:
• Create a dataset.

5.4 Create a new dataset by drag-and-drop

1. In a Teamcenter component hierarchy view, folder view, or table, display
the folder, item, or item revision under which the new dataset will reside.
2. In a file system window, select the file to add and drag it over the
Teamcenter folder, item, or item revision.
The New Datasets for Multiple Files dialog box is displayed.
3. (Optional) Edit information as needed.

• Accept the name or type a descriptive name (up to 128 ASCII
characters) in the Dataset Name box.
• Type a description (up to 240 ASCII characters) to help identify this

dataset in the Description box.
• Change the values in the Dataset Type, Reference, and Tool Used
boxes.
4. Click OK.
The system displays the new dataset object under the drop-target object.

5.5 Activity
• Create a dataset using a drag and drop method.

5.6 Dataset named references
• Datasets are often used to manage several different types of files.
• The files managed by datasets are referred to as named references.
• Datasets are the only Teamcenter objects that use named references.

5.6.1 View and modify named references
1. Select the dataset in the tree or Details table.
2. Choose View®Named References.

The Named References dialog box appears, listing all the named
references of the selected dataset.
3. (Optional) You can delete, cut, copy, paste, import, and export named
reference files.

5.7 Activity
• Import a dataset.

5.8 Dataset versions

Edits to a dataset are captured in versions. When you save changes to
datasets, new versions of the datasets are created.
Teamcenter continues to add dataset versions until the version limit is
reached.
The version limit, which can be set by the Teamcenter administrator, specifies
the maximum number of dataset versions that are stored in the database.

5.8.1 Key points about dataset versions
• As you successively modify a dataset, new versions are added to the

database, but version 0 (no value) always references the latest version of
the dataset.
• Because Teamcenter hides other dataset versions to reduce clutter,

normally, you only see the version 0 dataset.
• The default version is the latest.
• Dataset versions can be used to revert to a previous version of the dataset.
• Dataset versions can be used as the basis for creating a duplicate of an

existing dataset.
• When the version limit is exceeded, the earliest version of the dataset is
purged from the database.

5.8.2 Revert to a previous dataset version
Revert to a previous dataset version to track changes and undo changes to a

dataset.
1. Select the dataset.
2. Choose File®Open With.
Using the Open With dialog box, you can specify a particular version of a
dataset and/or a specific software application (tool) to use for the current
editing session.

5.8.3 Purge dataset versions
Use the Edit®Purge command to explicitly remove old versions of a dataset

from the database.
• To purge a dataset, you must have read, write, and delete privileges on
the versions of the dataset that you want to purge.
• The Purge command completely and permanently removes old versions of

a dataset from the database.
Note
When a dataset is assigned a release status, all earlier versions are
purged automatically.

5.9 Creating new datasets based on existing datasets

Using the Save As command on the File menu, you can create a new dataset
based on another dataset.
Caution
When using the Save As command to duplicate a dataset, the new
dataset is of the same type and uses the same software application
(tool) as the original dataset. You cannot change these characteristics
during this procedure.

5.10 Activity
• Modify a dataset and work with versions.

5.11 Summary
• Identifying datasets and dataset types
• Creating a dataset and working with versions
• Creating a new dataset from existing data

Lesson
6 Applying data security practices
Purpose
The purpose of this lesson is to learn how data is secured and access is
controlled when working in a collaborative data management environment.
Objectives
• Identify your group and role.
• Change your group and role setting.
• Check in and check out data.
• View data access settings.
Help topics

Applying data security practices
6.1 User groups and roles

Your account is set up by your application administrator. The account
includes the following:
• Person Name
Your actual name and e-mail address.
• User ID
Your Teamcenter account name.
Your application administrator also sets up the necessary groups in

Teamcenter.
• A user may be in multiple groups.
• One group is designated as your default group.
• Inside a group, you (as a user) can perform multiple roles.
The user name, group, and role for the logged-on user appears in the My
Teamcenter application banner, as shown in the following example.

In this example, the person name is Maria Andretti. The user name for
this person is de00.
Maria is in two groups, high performance and shop floor.

• Inside the high performance group, Maria performs the Design
Engineer role.
• Inside the shop floor group, Maria fulfills the Crew Chief and Shop
Engineer roles.

6.1.1 Key points about groups and roles
Groups and roles can be applied to:

• Manage data access privileges (read, write, and delete) per group and role.
• Define and control review/approve processes based on group and role.
• Organize data according to which group created it.

6.1.2 Change your group and role setting
Typically you work in your default group and role, and the data you create is
owned by that group. During a logon session, you may need to change your
group or role, so you can find and access data owned by another group.
1. Choose Edit®User Setting.
The User Settings dialog box appears.
2. Select the desired group and role setting from the respective menus.
Note
Only the groups of which you are a member and your possible roles
are available for selection.
3. Click OK.

6.1.3 Set your default group and role

You can set the group and role you typically work in as the default setting.
This is used by the system at logon.
1. Choose Edit®User Setting.
The User Settings dialog box appears.
2. Click Login.
3. Set your default group and role.

• In the Default Group box, select the default group for logon.
Note
Only the groups of which you are a member are available for
selection.
• In the Default Role section of the dialog box, select the default role for
the group.
Note
If desired, you can select a default role for each of the groups
you are a member.
4. Click OK.
Note
You can also change your password from the User Settings dialog box
by clicking Change Password.

6.2 Activity
In the Applying data security practices section, do the following activity:
• Change your group setting.

6.3 Overview of checkout and checkin

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 from the
rich client or click Edit beside a dataset file in the thin client. 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:
• Folders
• Items and item revisions
• Datasets
• Forms
• BOM views and BOM view revisions

6.3.1 Explicit checkout
When you check out an object by using the Check-In/Out commands on the
Tools menu, or when you use Check-Out and Edit in a view, you explicitly
check out the object from the database. Explicit checkout ensures exclusive
modification access to an object.
You define the checkout directory by choosing Edit→Options and setting the
General Check-In/Check-Out options.
To explicitly check out an object, the following conditions must be met:
• The object must not be checked out by another user.
• You must have write access to the object.
• The object cannot be archived.

6.3.2 Implicit checkout
When you double-click a dataset object in Teamcenter, the system

automatically creates an implicit checkout to ensure that two processes are
not allowed to simultaneously update the dataset.
Implicit checkout differs from explicit checkout in the following ways:
• Implicit checkout is automatic and occurs when you open a dataset
for modification. When the modifications are completed, the dataset is
automatically checked back into the database.
• You cannot use a menu command to initiate an implicit checkout

operation.
• Implicit checkout actions are not logged in a history file.
• Users included on notification lists are not notified when implicit checkout
takes place.
• An implicit checkout in the Viewer view is released when you select a

different object while the Viewer view is active. The checkout lock is not
released if you only select another view such as the Summary or Details
view.
Note
The implicit checkout lock is released automatically when you
return to Viewer and close the object, or select another object to
open in the Viewer view.

6.3.3 Check out an object
1. Select objects in the My Teamcenter tree or a BOM line in Structure

Manager.
2. Choose Tools→Check-In/Out→Check-Out.
The system displays the Check-Out dialog box.
3. If you want to check out only those objects displayed in the dialog box (no
attachments or component objects), go to step 5.

4. (Optional) Check out component objects or attachments along with the

selected objects.
a. Click Explore Selected Component(s) .
The system displays the component structure of the selected object

in the Explore dialog box along with a pane for defining rules that
determine which related objects are included.

b. Select the related objects, using one of the following methods:

• By individual selection
Select the check box corresponding to the component in the tree.
• By selecting all components
Click Select all component(s) located beneath the tree.
5. Click Yes (in the Check-Out dialog box) to check out the selected objects.
If an error occurs during the process, Error in the right margin of the
dialog box (opposite the object) is displayed. You can double-click Error
to display details about the error.
The checkout symbol next to the object indicates that the process
was successfully completed.

6.3.4 Check in an object

1. Select one or more objects that are currently checked out or select a
checked-out part or assembly represented by a BOM line in Structure
Manager.
The Check-In option unlocks objects in the database, including assemblies
in Structure Manager, that were previously checked out.
2. Choose Tools→Check-In/Out→Check-In.
The Check-In dialog box appears.
3. If you want to check in only those objects displayed in the dialog box (no
attachments or component objects), go to step 5.
4. (Optional) Check in component objects or attachments along with the

selected objects.
a. Click Explore Selected Component(s) .

The system displays the component structure of the selected object
in the Explore dialog box along with a pane for defining rules that
determine which related objects are included.

b. Select the related objects, using one of the following methods:

• By individual selection
Select the check box corresponding to the component in the tree.
• By selecting all components
Click Select all component(s) located beneath the tree.
5. Click Yes (in the Check-In dialog box) to check in the selected objects.
The button in the right margin of the dialog box (opposite the object)
indicates whether the process was successfully completed. If an error
occurs during the process, the error button is displayed for that object.

6.3.5 Transfer checkout to another user
1. Select an object that has been checked out of the database.
2. Choose Tools→Check-In/Out→Transfer Check-Out.

The system displays the Transfer Check-Out dialog box.
3. Select a user name from the New User list.
The user is designated as the New User to whom checkout will be

transferred.
4. Click Yes to transfer checkout.

6.3.6 Canceling a checkout request
You can select a dataset that is checked out and right-click to choose the
Check-In/Out→Cancel Check-Out... command.
The system displays the Cancel Check-Out confirmation dialog box.
• Click Yes to cancel the checkout.
• Click No to stop the cancellation operation.
Note
The Cancel Check-Out command cancels only explicit dataset checkout.

6.3.7 View the checkout history of an object
1. Select the object in the tree and choose Tools→Check-In/Out→Check-Out

History.
The system displays the Check-Out History dialog box containing the
following information:
• Date and time of each checkout transaction
• User ID of the user who performed the checkout
• Status of each transaction: checkin, checkout, transfer checkout, or

cancel checkout
• Change ID and comments
2. Click Close to exit the Check-Out History dialog box.

6.4 Activities
In the Applying data security practices section, do the following activities:
• Use implicit and explicit checkout.
• View the checkout history of an object.

6.5 Managing object protection and ownership

Managing object protection and ownership is crucial in a
distributed-computing environment. Because workspace objects represent
actual product information in the database, they must be protected from
unauthorized or accidental access, modification, and deletion.
Teamcenter implements two different tiers of data protection:
Rules-based Rules-based protection is configured by your
protection administrator and includes conditions or rules that
control access to objects. These rules affect your entire
Teamcenter site and are enforced by the Access Manager
(AM).
Object-based Object-based protection uses access control lists (ACL)
protection to create exceptions to rules-based protection on an
object-by-object basis. Object ACLs are most useful
for either granting wider access or limiting access to a
specific object.

6.5.1 Rules-based protection
Rules provide security for your Teamcenter data by:

• Controlling access to data on a global basis.
• Determining whether a user has permission to view or perform an action

on an object.
• Filtering data according to the attributes of the data.
• Granting privileges to the data according to the users’ IDs and their
session context (the group and role they used to log on).
Note
Rules do not control the creation of objects. They only determine what
operations can be performed on existing objects.

6.5.2 Object-based protection
Object-based protection uses access control lists (ACLs) to create exceptions

to rules-based protection on an object-by-object basis.
Object ACLs are most useful when you need to:
• Grant wider access to a specific object.
• Limit access to a specific object.
Teamcenter uses ACLs to determine access to an object. Users with proper

permissions can override the ACL for an object to grant or deny permissions
for certain users but only when the rule tree allows.
For example, the rule tree does not allow object-based access rules to override
the rules-based protection when:
• An object has an assigned status.
• The object access rule is granted in a workflow.
Note
ACLs do not control the creation of objects. They only determine what
operations can be performed on existing objects.
• Each ACL contains a list of accessors and the privileges granted,
denied, or not set for each accessor.
• Each individual pairing of an accessor with their privileges is

considered a single access control entry (ACE).

6.5.3 Controlling object access working with ACLs
You work with access control lists (ACLs) to view, modify, add, or delete
privileges on an object.
You can grant or deny various types of access privileges on an object you own
if you have the proper permissions on that object.

6.5.4 View access privileges
Use the Access dialog box to determine the access privileges you have to an
object. You can also view the access privileges for another user.
1. In My Teamcenter, select the object affected by the access rule and choose
View→Access.
Tip
You can also right-click the object and choose Access from the
shortcut menu, or you can click Access on the toolbar.
The Access dialog box appears, showing the privileges that the logged-on
user has to the selected object.
2. To view privileges assigned to your other roles and groups, select the role
or group from the lists in the Access dialog box.
The system updates the Access table to reflect the privileges of the
selected group and role.
3. To view the privileges of a different user, select the user, group, and role
from the lists in the Access dialog box.
The system updates the Access table to reflect the privileges of the
selected user, group, and role.

6.5.5 View access privileges example
In this example, you see privileges for two users for one object.
1. To view access on a selected object, choose View→Access.
The Access dialog box shows the user taylor has several privileges, such
as Delete, Read, and Write privileges to the 000017/A item.
2. To view the privileges of a different user, select the user, group, and role
from the lists in the Access dialog box.
The Access dialog box shows the user smith has Read and Write
privileges but does not have Delete privileges to the 000017/A item.

6.5.6 Add accessors and grant privileges
1. Select an object in a tree pane or component view and click Access on

the toolbar or right-click the object and choose Access.
The system displays the Access dialog box, showing the access properties
assigned to the owner of the object.
2. Click Get access control list in the lower-right corner of the Access
dialog box to display the ACL Control List dialog box.
3. Click Add access control entry to ACL to add a blank row to the list.
The system displays a blank row at the bottom of the ACL list. You can
click this button more than once to add multiple entries.
4. Select the accessor type, as follows:
a. Double-click the blank box in the Type of Accessor column to

display the list of predefined accessor types.
b. Choose the accessor type that you want to add to the list.
5. (Optional) Double-click the blank box in the ID of Accessor column to

access the list of predefined accessor IDs, and choose an ID from the list.

6. Grant or deny privileges for the accessor by double-clicking in the column

corresponding to the privilege you want to grant. Select to grant a
privilege or to deny the privilege.
Note
To clear a privilege box, double-click in the box and select the blank
entry.
7. Click OK to save the list.

6.5.7 Modify access privileges on an object you own
1. Select an object in the tree or component view, and click Access on

the toolbar or right-click the object and choose Access.
The system displays the Access dialog box.
2. Click Get access control list in the lower-right corner of the Access
dialog box.
The system displays the ACL Control List dialog box.
3. In the ACL Control List dialog box, choose the entry that you want to
modify.
Note
You can only change entries you have created or entries you have
been given permission to change by the Teamcenter administrator.
4. Grant or deny privileges for the type of accessor by double-clicking in the

column corresponding to the privilege you want to modify.
• Select the check mark to grant a privilege.
• Select to deny the privilege.
Note
To clear a privilege box, double-click in the box and select the blank
entry from the list.
5. Click OK to save the list.

6.6 Authorized data access
Authorized data access (ADA) is a generic term that applies to the

configuration of Teamcenter security for intellectual property (IP) data
and for data that is deemed military in nature and is, therefore, subject to
International Traffic in Arms Regulations (ITAR) policies.
ADA controls access to classified data using user clearance and ADA license
that grant limited-time access to specific users or groups of users.
ADA facilitates data access control by:
• Identification of users as restricted.
• Identification of data as restricted.
• Authorization of access to restricted data by restricted users using

ADA license, Technical Assistance Agreement (TAA), nondisclosure
agreements, and contracts.
ADA assesses validation during any access attempt by a restricted user.

6.7 About configuring authorized data access (ADA)

Authorized data access (ADA) is a security solution that complements other
Teamcenter security features, such as Access Manager rules and access
control lists (ACLs). Authorized data access controls sensitive data through
the use of data classification, user clearance, and authorizing documents.
When users or groups attempt to access classified data in Teamcenter, their
clearance level is evaluated against the classification of the object based on
Access Manager rules. If the user or group clearance level is equal to or
greater than the classification on the object, access is granted.
There are three types of licenses for authorized data access:
• IP license
Grants discretionary access to data for a specific user for a specific period
of time.
Your administrator can configure the rule tree to check for a valid IP
license associated with an object and user. If found, other access checks
are bypassed.
• Exclude license
A mechanism for denying users access to data for a specific period of time.
Your administrator can configure the rule tree to check for a valid
execution license associated with an object and user. If found, other access
checks are bypassed.
• ITAR (International Traffic in Arms) license

Grants discretionary access to data for a specific user or group with
International Traffic in Arms Regulations (ITAR) classifications for a
specified period of time. Typically it is used to grant access for a specific
time period to citizens of other countries, United States (U.S.) citizens
physically located outside the U.S., or organizations that are named in an
effective Technical Assistance Agreement (TAA) through an ITAR license.
Your administrator can configure the applying of logging and menu

suppression (blocking) when classified data is loaded in Teamcenter
Integration for NX.
An administrator with an ADA administrator role (IP Admin or ITAR
Admin) uses the ADA License application to create and maintain licenses.
Once created, access is either granted or denied to users and groups by
associating the license directly with the data object.

6.8 Using the information center

When you select an object, such as an item, in a Teamcenter rich client
application, information about the selected object is shown in the information
center. The information center is located at the bottom of the Teamcenter
window, to the left of the clipboard.
Information center symbols convey where-used and where-referenced, access
privilege, child count, and status information about the selected object. To
display the information, point to the symbol. The information displays in
the form of a tooltip.
Note
The indicator in the upper-right corner of any of the symbols in the

information center indicates that the status represented by the symbol
does not apply to the selected object.
For example, the indicator in the corner of the In Process symbol

indicates that the object is not in process.
Symbol Description
Object access: Write access is permitted on the selected object.
Object access: Delete access is permitted on the selected object.
Object access: Change access is permitted on the selected object.
Object state: The object is the target of an active workflow process.
Object state: The object is checked out of the database.
Object state: The object is released.
Object state: The object is published.
Object state: The object is classified.
Where used: Where-used count for the currently selected object.
Where referenced: Where-referenced count for the currently
selected object.
Children: Number of children of the selected component.

6.9 Activity
In the Applying data security practices section, do the following activity:
• View access privileges for an object.

6.10 Summary
• Identifying your group and role
• Change your group and role setting
• Protecting data using checkin and checkout
• Viewing data access settings

Lesson
7 Performing and managing

searches
Purpose
The purpose of this lesson is to use various methods to locate and view
Teamcenter data.
Objectives
• Perform queries.
• View search results.
• Generate reports on Teamcenter data.
Help topics

Performing and managing searches
7.1 Searching in Teamcenter

The Teamcenter search functionality lets you find data in the Teamcenter
database.
The Quick Search feature in the navigation pane lets you search for data by
specifying the dataset name, item ID, item name, or a keyword.
Note
Quick search results cannot be saved to your saved searches list.
You can use saved queries to search for your work in the Teamcenter database
or in databases that are part of a Multi-Site Collaboration network. Saved
queries are grouped into three categories:
• My Saved Searches
This category contains queries that you ran previously and chose to save
for later use.
You can save the results of a search and add the search to your My Saved
Searches list. In both the rich client and thin client, you can share a
saved search. In the rich client, you can restrict sharing to specified
groups of users.
• System Defined Searches

This category contains both standard queries and custom queries defined
by your Teamcenter administrator. Standard queries allow you to search
by common parameters such as item identifier. Custom queries allow you
to search for data that is unique to your site or company.
• Search History
This category contains the most recently run queries. By default, the
last eight queries are listed, but you or the administrator can change the
number of queries shown.

7.1.1 Using the Search view
Use the Search view to enter criteria and execute a search.

The Search view, which provides access to search functionality and a wide
range of predefined search criteria queries, has a standard tab, a toolbar with
options and a menu, a title, and a criteria area.
1 Search view Contains the following options:

toolbar
• Executes the search and displays the results in
the search result view
• Change search from search history
• Select a Search
• Re-execute search. Show results in currently

open search view pane
• Clear all search fields
• Add Search to My Saved Searches
• Organize My Saved Searches
• Sort

• Menu
o Lock Search
Locks the current search criteria pane when
you open an executed query by switching
between search entries in the Open Items
area in the navigation pane.
o View Search Criteria Definition

Lets you view current search criteria in a
query clause format.
o Change Search Criteria Definition

Lets administrators modify query criteria.
o Extended Multi-Application Search

Lets you perform advanced searches spanning
multiple applications. For example, you can
run a Classification search with multiple
applications in the target list.
o Options
Launch the Options dialog box.
2 Search title Indicates the name of the current search.
3 Search Contains input boxes and lists of values for search
criteria criteria.

7.1.2 Change your search
1. In the Search pane, click Select a Search .

The Change Search dialog box appears.
2. Select a new search from the System Defined Searches or My Saved

Searches categories.
3. Click OK.
The search form with the criteria for the selected search appears in the
Search pane.

7.1.3 Using search types
A search in Teamcenter involves selecting a search type, which in turn

specifies criteria for a database query and distinguishes the databases to be
queried. For example, the following search types produce different query
behavior:
• An Item ID search queries the Teamcenter database for the specified
item ID.
• An Item Name search queries the Teamcenter database for the specified
item name.
• A Dataset Name search queries the Teamcenter database for a dataset

name.
• A Dataset search queries the Teamcenter database for attributes and the
index search engine database for dataset content.
Keywords for full-text searches on dataset files, if the search engine is
installed and configured at your site.
Note
Other types of searches may be available, depending on your available
applications and the information desired.
For example, where-used and where-referenced searches are available in
the My Teamcenter application Impact Analysis view.
• Where-used searches identify assemblies that contain an item or
item revision.
• Where-referenced searches determine which objects in the database

reference a selected object.

7.1.4 Providing search input
You can use the following as search input:

• Multiple values in search criteria boxes.
• The contents of table columns or rows.
• Lists of objects derived from other applications or from the results of a

search.
• Wildcard characters and limits on the number of results that are loaded.
• Search definitions modified by advanced editing.

7.1.5 Using wildcard characters
Wildcard characters, such as * and ?, broaden your searches by allowing

you to match a single character or multiple characters occupying specific
positions in a search string.
Each box in the search form corresponds to an attribute of the search class.
This attribute can be a string, date, integer, or logical type. Date, integer,
and logical type search boxes do not support wildcard characters. Wildcard
characters can only be used in boxes corresponding to string attributes.
* The asterisk wildcard searches for the root of a word
followed by one or more characters.
For example, a search for communicat* returns items
containing terms such as communicate, communicates,
communicated, communication, communications, and
communicating.
? The question mark wildcard searches for the root of a
word with the question mark as a substitute for any other
character.
For example, a search for Anders?n returns items that
contain terms such as anderson, andersun, andersen, and
andersin.

7.2 Using quick search

Use the quick Search input box, Perform Search button, and menu
at the top of the navigation pane to locate objects
in the Teamcenter database. A quick search can be performed based on item
ID or other search criteria listed in the quick Search menu.
Tip
You can use wildcard characters such as * and ? in the value you enter
in the Search input box for your search criteria.
• Item ID
Type an item ID to search the Teamcenter database for item ID attributes.
• Keyword Search
Type a keyword to search indexed classes for attributes and indexed class
content.
• Item Name
Type an item name to search the Teamcenter database for all item name
attributes.
• Dataset Name
Type a dataset name to search the Teamcenter database for all dataset
name attributes.
• Advanced
Access the advanced search capabilities and predefined search forms.

7.2.1 Perform a quick search
1. Locate the quick Search input box and Perform Search button and menu
at the top of the navigation pane.
2. Click the menu button and select a search type.

Note
Item ID is the default search type.
3. Type the appropriate value for your search criteria in the Search box.
Note
You can use wildcard characters such as * and ? in the value you
enter in the Search input box for your search criteria.
4. Click Perform Search to execute the search.

When the search succeeds and returns more than one object, the Quick
Open Results dialog box appears. If only one object is returned, the object
is retrieved and opened in a My Teamcenter tri-pane view.
Note
If you do not find the object you seek using the quick search, click
Cancel. You can use advanced search to access predefined search
forms with additional search criteria.
5. In the Quick Open Results dialog box, you can either double-click an
object to open it or select an object in the list and click Open.
The object is retrieved and opened in a My Teamcenter tri-pane view.

7.2.2 Using simple search
The rich client Simple Search view lets you create business object searches
based on one or more property values. You first select the object type, and
then build a search by selecting properties and specifying criteria.
• Choose properties to build search criteria.

You can use attribute properties and typed reference properties, but not
run-time properties, relation properties, or compound properties.
• The scope of the search is limited to the local Teamcenter database.
• You can execute a simple search, but it cannot be saved or reused by

other users.
• Ad hoc and classification searches are not supported for business object
searches.
• The search results are displayed in the Search Results view, and users
can refresh, compare, save, and assign to project the results.
• Current search preferences are applied to the simple search being

executed.

Note
To set search preferences, use the Simple Search view menu
Options command to display the Preferences (Filtered) dialog
box.
Note
The Simple Search view is available from the toolbar in the rich
client My Teamcenter perspective, and in other perspectives through
the Window®Show View®Other®Teamcenter®Simple Search menu
command.
The Simple Search functionality is not available in the thin client.

7.2.2.1 Perform a simple search
Use the Simple Search view to find objects in Teamcenter based on business
object properties.
1. In My Teamcenter, click Simple Search .
The Simple Search view is displayed.
2. Select or enter a business object type.

3. Select a property and choose an operator and a value for the edit clause.
You can repeat this step as many times as needed to create the search
criteria.
4. Click Search.
The Search Results view is displayed with objects that meet the specified
criteria.

7.2.3 Perform an advanced search
1. Click Search on the toolbar or select Advanced from the search menu
at the top of the navigation pane.
The Search pane appears showing the default search name and
description followed by the search criteria form.
Note
The software ships with Item ID selected as the default search. The
Item ID search form has only the Item ID box for criteria.
2. (Optional) On the Search pane toolbar, click to select a search from

the list of search types.
The search form with the criteria for the selected type appears in the
Search pane.
3. (Optional) Click to clear the content of all boxes on the search form.
4. Type the values for the search criteria in the boxes on the search form.
Tip
You can use wildcard characters such as * and ? in the value you
enter for your search criteria.
5. Click to perform the search.

Tip
The Progress Information dialog box appears showing the progress
of the search. You can click Cancel on this dialog box to stop the
search before the processing is complete.
Results appear in the Search Results view.

7.2.4 Query for dataset sequences
1. Click Search on the Teamcenter toolbar or choose Advanced from the

quick search menu to display the Search pane.
2. Click Select a Search in the My Teamcenter application to display the

Change Search dialog box.
3. In the System Defined Searches, select either All Sequences or Specific

Sequence.
• All Sequences returns all previous sequences for objects that match
the specified criteria.
• Specific Sequence returns the specified sequence.

7.3 Working with search output

You can:
• Print search results.
• Lock the search pane to view results panes without overwriting search
criteria.
• Work with objects in search results panes that persist from session to
session.
• Rename and save search criteria to My Saved Searches or another folder.
• Compare results to the contents of your Home folder, My Worklist view,

or to other recent search results.
• Use the property finder formatter (PFF) to view additional data related to
the objects listed in the search results.

7.3.1 Working with search results
In My Teamcenter, search results appear in the Search Results view.
Each time you execute a search, the results of the latest search appear in the
Search Results view, replacing the results of the previous search. Right-click
the search name at the top of the list of search results to access the shortcut
menu.
From this menu, you can perform various actions on the search results
including assigning the objects to a project and comparing the results to those
of another search.

7.3.2 Using the Search Results view
Use the Search Results view to examine the list of objects that satisfy
the search criteria.
1 Search Contains the following options:

Results view
toolbar • Rerun current search
• Show Previous Searches
• Export Objects to Excel
• Select PFF
• Refresh property formatter search
• Edit property formatter
• Run Adhoc from Property Formatter
• View Menu→Options
2 Search title Indicates the name of the current search and the
number of items returned.
3 Search Contains the following options:
Results view
page toolbar • Previous page
• Next page
• Load all
• Collapse to the root object
• Expand the selected object(s)

• Expands the selected object(s) to all levels

4 Search Lists objects that meet search criteria.
results

7.3.3 Navigate the search results and adjust the display setting
When you run a search, the total number of objects found and the relative
position of the displayed objects within that total appears at the top of the
search results.
Item ... - Result: Page 1 of 2 objects found Number of items
Navigational buttons
Item ID (1) Search results (version)

standard_thread_inch
cap_screw_cb_inch
• You can see the number of items displayed and the total number of items
found.
• You can move back and forth through the results by clicking the
navigational buttons and load all buttons located in the search results
pane.
• You can see the search results version (for example, 1). When searches
are run multiple times, the version number distinguishes each result.

7.3.4 Rename search results
If you plan to keep a search open in your My Teamcenter window for an

extended period of time, or if you have multiple queries open, renaming the
search results is a convenient way to make your My Teamcenter window
more manageable.
1. Right-click the search name at the top of the list of search results.
The Explorer Popup Menu appears.
2. Choose Rename from the menu.
3. Type a new name for the search results.
4. Press Enter.
The name of the search is changed to reflect the new name.

7.3.5 Close search results

Note
Search results that have not been saved to a folder are lost when you
close the pane.
2. Choose Close to close the current search or select Close All to close all
open searches.

7.4 Compare search results

Search results can be compared to the results of other searches.
1. Execute the applicable search to display the search results list you want
to compare.
3. Choose Compare To to access a list of open searches.

• Select an open item from the list or, if the list is extensive, from the
expanded list.
• If the number of open items is difficult to navigate from the menu list,
select Compare to Search Result List.
The Compare To dialog box appears. You can use this dialog box to
scroll through the open items and make a selection.
4. Select a search name from the Compare To list or dialog box.

The Compare Report dialog box appears showing the contents of the
selected search results. Differences between the components in the
selected search results lists are highlighted in green, identical objects
have a transparent background, and the object currently selected is
highlighted in blue.

5. (Optional) Browse the differences using the navigation buttons at the

lower-right corner of each pane. This can be useful when comparing
components containing a large number of objects.
6. (Optional) Select the Differences check box to display only the differences
between the components.
7. Click Close to exit the dialog box.

7.5 Printing search results

You can:
• Print a snapshot of the search results tree.
• Print the properties of an object in the search results tree.

7.5.1 Print a snapshot of the search results tree
2. Choose Print.
The Print dialog box appears.
3. (Optional) Modify the print options and properties.
4. Click OK.
The list of objects in the search results tree is printed. If the tree displays
all of the results, all results are printed. If the tree only displays one page
of results, only that page is printed.

7.6 Activity
In the Performing and managing searches section, do the following activity:
• Perform an advanced search.

7.7 Saving searches

You can save searches to the My Saved Searches folder, or you can create a
hierarchy of subfolders in which to save searches.
Note
If the Search pane is not open, you can access your saved searches
from the My Saved Searches expand button under Quick Links in
the navigation pane.

7.7.1 Save search results to your My Saved Searches folder
1. In the Search pane, display the desired search form and set the criteria
to the values for the search you want to save.
2. Click to perform the search to verify the criteria values are set
accurately for the intended search results.
3. Click Save at the top of the Search pane.

The Add Search to My Saved Searches dialog box appears.
4. Type a unique name for the search in the Name box.
5. Click OK.
The search is saved and listed in your My Saved Searches folder.

7.7.2 Save search results to a subfolder of My Saved Searches

1. In the Search pane, display the desired search form and set the criteria to
the applicable values for the search you want to save.
2. Click to perform the search to verify the criteria values are set
accurately for the intended search results.
3. Click Save at the top of the Search pane.

The Add Search to My Saved Searches dialog box appears.
4. Type a unique name for the search in the Name box.
5. Click Create In.

The Add Search to My Saved Searches dialog box expands to show the
saved searches folders.
6. Select a folder to save the search in or, if you want to create a new folder,
select a folder to create the new folder in and click New Folder.
A new subfolder is created in the selected folder.
With the new subfolder selected, click Rename and type a new name
for the subfolder.
7. Click OK.
The saved search is listed in the subfolder of the My Saved Searches
folder structure in the Change Search dialog box.
The saved search is also listed in the navigation pane under Quick Links
in My Saved Searches.

7.8 My Saved Searches

Searches saved from the Search pane are listed in the My Saved Searches
menu in the Quick Links section in the navigation pane.

7.8.1 Perform a saved search
1. Expand the My Saved Searches menu in the Quick Links section in

the navigation pane.
2. Select a saved search.

The results of the search appear in the Search Results view.

7.8.2 Customize saved searches
1. Click the My Saved Searches text in the Quick Links section on the
navigation pane.
The Customize My Saved Searches dialog box appears.
2. Select a saved search from the list of saved searches.
3. Use the buttons to delete or rename the saved searches.
4. Click OK to accept your changes and close the dialog box; or Cancel to
discard changes and close the dialog box.

7.8.3 Share saved searches

You can:
• Create new shared searches.
• Share existing saved searches with other users.
• Use saved searches that others users have shared.
1. Click Search on the My Teamcenter toolbar in the rich client.
2. In the Search view, click Select a Search .

The Change Search dialog box is displayed.
3. Select a search type and provide search criteria, and then click Perform
Search .
4. Click Add Search to My Saved Searches .

The system displays the Add Search to My Saved Searches dialog box.
5. Type a name for the search.
6. Select Is Shared to create a shared search.
7. Click Create In to expand the dialog box to display existing saved searches
and folders.
In the expanded area, you can create new folders, rename or delete
searches or folders, or specify access privileges for searches.
8. Click OK to create the shared search.

Note
By default, saved searches are private. You must select Is Shared in
the Add Search to My Saved Searches dialog box for others to view
your saved searches.

7.9 Activities
In the Performing and managing searches section, do the following activities:
• Rename and save a search.
• Perform a search for checked-out objects.

7.10 Running reports

Teamcenter provides a number of standard report designs that you can use
to extract information and generate reports based on saved queries of the
database. For example, you can generate a report to show:
• All items of a specified type that have achieved a particular release status.
• Information, such as name, address, and employee number for specific

users in your organization.
The report generation wizard in My Teamcenter guides you through the steps
required to generate a report including:
• Selecting a design format.
• Specifying the information you want to extract from the database.
• Choosing an output format.
In addition to the standard report designs, Teamcenter administrators can

create custom reports using Report Builder.
Reporting and Analytics is a stand-alone reporting application. When it is
installed and deployed in a Teamcenter environment, it integrates with
Report Builder and displays reports in the TcRA Reports folder. A separate
application is added to Teamcenter which shows contents of the Teamcenter
Reporting and Analytics dashboard.

7.10.1 Examples of reports
Several reports are provided with Teamcenter.
Report name Description

Admin - Employee Returns employee information of a specified
Information person/user.
Admin - Group/Role Returns membership information for a
Membership specific group/role.
Admin - Item Ownership Returns items of a specified type that are
owned by a specified user/group.
Admin - Items By Status Returns items of a specified type released to a
specified status.
Admin - Object Ownership Returns objects of a specified type that are
owned by a specified user/group.
Admin - Objects By Status Returns objects of a specified type released
to a specified status.
Business Objects Details This is a sample COTS report to display any
business object details.
Item Revision Structure Provides the hierarchical information of the
Information item revision.

7.10.2 Generate a Report Builder report
Report Builder reports are created from saved or dynamic queries. When
you select a Report Builder report from a list of available reports, you are
prompted to input query criteria.
1. In My Teamcenter, choose Tools→Reports→Report Builder Reports.
The system displays the Report Generation Wizard.
The Report Type menu lets you choose to display all reports, summary
reports, or custom reports.
If no reports are listed, no reports have been created by your system
administrator.
2. Select a report.
3. Click Next.

4. Fill in criteria for the query. Only the objects that match the query are
placed into the report.
5. If you want to choose the format for the report, click the arrow in the
Report Stylesheets box to select a style sheet.
6. If you want to save the report as a file, select Create Dataset and type
a name in the Dataset Name box.
7. Click Finish.
If you did not choose a style sheet, the report is displayed in your default
XML application. If you chose an HTML spreadsheet, the report is
displayed in a Web browser.
If you saved the report as dataset, the report is saved in your Newstuff
folder.

7.10.3 Item report examples
Several item reports are provided with Teamcenter.
Report name Description

ECO Details Report Returns engineering change order details for
the specified item revision.
ECO Signoff Details Returns engineering change order signoff
details for the specified item revision.
Item Revision master form Shows the data of the master forms associated
data with the item revisions.
PS-BOM Structure Returns unpacked BOM information for a
specified item revision.

7.10.4 Generate an item report on a Teamcenter object
Generate an item report from My Teamcenter by choosing one or more

Teamcenter objects, such as an item revision. Only objects with associated
reports have report definitions displayed in the selection wizard. When you
select an item report from a list of available reports, you may be prompted for
additional parameters.
1. In My Teamcenter, choose a Teamcenter object, such as an item revision.
2. Right-click the object and choose Generate Report.

The system displays the Report Generation Wizard.
If no reports are listed, no reports have been created by your system
administrator for the selected object type. Teamcenter has standard item
report definitions for item revisions.
3. Select an item report.
4. Click Next.
5. Fill in criteria for the query. Only the objects that match the query are
placed into the report.
• To select the display locale, select the locale from the Report Display
Locale list.

• If you want to choose the format for the report, click the arrow in the
Report Stylesheets box to select a stylesheet.
• If you want to save the report as a file, select Create Dataset and type
a name in the Dataset Name box.
6. Click Finish.
If you did not choose a style sheet, the report is displayed in your default
XML application. If you chose an HTML spreadsheet, the report is
displayed in a Web browser.
If you saved the report as a dataset, the report file is saved in your
Newstuff folder.

7.11 Activities
In the Performing and managing searches section, do the following activities:
• Generate a report of items by status.
• Generate a BOM structure report.

7.12 Summary
• Performing queries
• Viewing search results
• Generating reports on Teamcenter data

Lesson
8 Working in projects
Purpose
The purpose of this lesson is to learn the basics of working with project data.
Objectives
• View project data.
• Assign objects to projects.
• Assign secondary objects to projects.
• Remove objects from projects.
Help topics
• Project Guide

Working in projects
8.1 Introduction to projects and programs

Projects, also called programs in some industries, are used to represent and
control access to data objects that may be accessible to multiple organizations,
such as project groups, development groups, suppliers, and customers.
Projects are represented as nodes in a tree, or project smart folder hierarchy.
• Project smart folders are defined by project administrators to support
navigating project data based on functional and subfunctional units.
• For any selected item assigned to a project, the hierarchy can be followed
up to the top-level folder and can be expanded to display lower levels of
the hierarchy, as configured by the project administrator.
• Smart folders are pseudofolders configured in a hierarchical structure;

they are not physical folder objects in Teamcenter.
• Project data filtering can also be applied in the absence of a project smart
folder hierarchy. You can filter project data based on object type.

Working in projects
8.1.1 Project administrators and team members
The following table describes the project administrators and team members
who can create, manage, and use projects.
Team role Definition

Project Teamcenter user with privileges to create and
Administrator administer projects.
role in Project
Administration Users in the Project Administrator role can:
group • Modify projects.
• Delete projects.
• Add team members to projects.
• Assign privileges to team members.
• Remove team members from projects.
Note
These privileges only apply to projects that
the project administrator owns.
Team Administrator Project team members with privileges to modify
role in Project project information. These privileges apply to
Administration the project metadata, not to the data assigned to
group projects.
Users in the Team Administrator role can:
• Add team members to projects in which the
team administrator is also a member.
• Remove team members from projects in which

the team administrator is also a member.
Note
You can designate multiple team
administrators for each project. This is often
necessary to balance resource management
tasks for large projects.
Privileged team Project team members with privileges to assign or
members remove objects from their projects.

Working in projects
Team role Definition

Team members Team members (users) who do not have privileges
to assign objects to or remove objects from their
projects.
The following diagram illustrates a typical project hierarchy.
Project Selected Members
Privileged Team
Team Administrator Team Members
Members
Gordon, Jack Jones, Paul Franklin, Wendy
Belcher, Sarah Tracey, Don
Smith, William

Working in projects
8.2 Viewing project data

You can click the My Projects link in the navigation pane to view your projects
and associated data. This view is determined by the project administrator.
The My Projects view is similar to My Teamcenter views but with the

following differences:
• Project Smart Folder Hierarchy
Displays the smart folder hierarchy as configured by the administrator,
and provides a filter button to display the Apply filters dialog box.
Note
The Apply filters dialog box lets you apply filtering based on source
types, properties, and values.
You select a project from the hierarchy to display information in the other
My Projects panes.
• Summary
The summary view consists of two tabs:
o Project Data
Displays the filtered objects assigned to the selected project.
o Team
Displays the project team associated with the selected project.

Working in projects
8.2.1 Project smart folder filtering
The following considerations apply to project filtering:

• It is not necessary to have an established smart folder hierarchy to apply
filters to your project data. In the absence of a smart folder hierarchy,
project objects are treated as abstract folders.
• Filters defined in My Teamcenter cannot be saved for future use. You

must add and remove them as required.
• Multiple filter criteria can be applied to a data-driven smart folder .

When multiple filter criteria are applied, all data that meets the criteria
appears under the project or program. A logical OR is applied between
each row in the filter table to determine the display results.
• Only one filter criteria can be applied to an abstract smart folder . If

multiple filters are applied to an abstract smart folder, no project data
is displayed.

Working in projects
8.2.2 Apply project smart folder filtering
1. Click My Projects in the Quick Links section of the navigation pane in

My Teamcenter.
The My Projects view appears.
2. In the My Projects view, expand a project object to view the data

associated with the project.
Note
Objects are displayed according to the project smart folder hierarchy
configuration defined by the project administrator and/or by any
filters that you apply.
If a smart folder hierarchy is configured for your project, you see
folders when you expand your project. Expand these folders to
reveal your project data.
3. To apply filters, select the project object in the My Projects view.

The Summary view shows details of the project object. The contents of the
Summary view vary according to the type of object selected.
4. Click the filter button to apply a filter to refine the list of objects for
the selected project.
The Apply filters dialog box appears.
5. Click the Add a filter button to populate a row in the table.

Working in projects
6. Choose filter criteria by clicking the Source Type, Property, and/or Value
cells and selecting a value from the list.
For example, you can add a filter to display the project data owned by the
Engineering group.
Note
You can remove rows from the filter table by clicking the Remove
the selected filter button . Click the Clear the filters button to
remove all values from the table.
7. Click OK to apply the filter.

The list of objects in the My Projects view is updated to reflect the applied
filters.
Note
The filters you apply remain until you remove them. However, you
cannot save a filter configuration and retrieve it for future use.

Working in projects
8.3 Activity
In the Working in projects section, do the following activity:
• Investigate available projects.

Working in projects
8.4 Assigning objects to projects

Items, item revisions, and engineering change objects can be assigned to
a project when the object is created. All other objects can be assigned to a
project only after the object is created.
Note
You can only assign objects to projects if the privilege to do so has been
granted by the project administrator.
Objects you can assign to projects include:

• Items, item revisions, and engineering change objects.
• Datasets and forms.
• Folders and their contents.
After objects have been created, you can assign them to projects by selecting
the objects from a hierarchy tree, a Details table, or the Search Results view.

Working in projects
8.4.1 Assign objects to projects from the tree or Details table
1. Select one or more objects in the tree display or Details table.
2. Right-click and choose Project→Assign or choose Tools→Project→Assign.

If you select multiple objects in step 1, the system displays the Assign
Objects to Project dialog box.
If you select a single object, the system displays the Assign an Object to
Project dialog box. The projects of which you are a privileged member are
displayed in the Project for Selection list.
Note
The objects you selected in step 1 may already be assigned to one or
more projects. You can click the My Projects link in the navigation
pane to view your projects and associated data.
3. Select the project or projects to which the objects will be assigned and
move them to the Selected Project list using the right-arrow button. To
select all projects in the list, click the double-arrow button.
4. Click Apply to assign the objects to the projects and retain the dialog box.
Click OK to assign the projects and exit the dialog box.

Working in projects
8.4.2 Assign objects to projects from search results
To assign all objects found in a search to projects:

1. In the Search Results tab, right-click the search name at the top of the
list of objects found and choose Project→Assign.
The system displays the Assign Objects to Project dialog box.
2. Select the project or projects to which the objects will be assigned and
move them to the Selected Project list using the right-arrow button. To
select all projects in the list, click the double-arrow button.
3. Select the objects to be assigned by selecting either Current Page or All

Found Objects.
4. Click Apply to assign the objects to the projects and retain the dialog box.
Click OK to assign the projects and exit the dialog box.
To selectively assign objects displayed in the Search Results tab to projects:

1. Select the object or objects in the Search Results tab.
2. Perform the steps described in the Assign objects to projects from the tree
or Details table procedure, beginning with step 2.

Working in projects
8.5 Assigning secondary objects to projects

Teamcenter administrators can configure Teamcenter to implicitly assign
related objects to a project when the primary object is assigned to a project.
For example, a propagation rule can be defined to assign datasets (secondary
objects) to a project when it has a specific relationship to an item revision
(primary object) assigned to the project. This is level-one propagation.

Working in projects
8.5.1 Secondary object propagation rules for projects
The propagation rules are valid when the following actions take place in
Teamcenter:
• When an item or item revision is assigned to a project, the related objects
are also assigned.
• When a related object is cut from the object assigned to the project, the
related object is removed from the project.
• When an attachment (related object) is pasted to an object, the attachment

is assigned to the project to which the primary object is assigned.
• When an item is imported in a Multi-Site Collaboration environment.
• When an imported object (replica) is assigned to a project, the associated

secondary objects are also assigned to the project according to the
propagation rules in effect at the receiving site.

Working in projects
8.5.2 Secondary object relations
When an object is assigned to a project, attachment objects, as defined by the

propagation rules, are also assigned to the project. Propagation rules are
determined by include and exclude relations lists. By default, the include
relation list contains the following relation types:
• Specification
• Manifestation
• Attaches
• AltRep
• EC_affected_item_rel
• EC_solution_item_rel

Working in projects
8.6 Automatically assigning objects to projects

Teamcenter administrators can configure Teamcenter to automatically assign
certain types of objects to a project when the specified objects are created
by privileged team members.
The following object types can be configured for automatic assignment:
• Item and item revision subtypes, such as engineering changes and
documents
• Forms
• Datasets
For example, Teamcenter can be configured to assign new item revisions to

the current project of the user who creates the new item revision.
Your current project is defined in the User Settings dialog box. You can
choose Edit→User Setting to access change your current project.

Working in projects
8.6.1 Considerations for automatic assignment of objects to projects
• Automatic project assignment applies only to object creation; whereas,

propagation of related objects (level-one propagation only) occurs any time
a relation between two objects is created, modified, or deleted.
• Automatic assignment of objects to projects is explicit; therefore, the

object can only be removed from the project explicitly by using the
Project→Remove command.
• Propagation rules implicitly assign secondary objects to projects;

therefore, when the primary object is removed from the project, the
secondary object is also removed.

Working in projects
8.7 Removing objects from projects

Objects can be removed from projects by selecting the object in the tree or
Details table or from the Search Results view.
Note
Two standard search forms can be used to locate objects for removal
from a project:
• The Projects search form
• The Objects in Projects search form.

Working in projects
8.7.1 Remove objects from projects
1. Select one or more objects in the tree display, Details table, or Search
Results tab.
2. Right-click and choose Project→Remove or choose

Tools→Project→Remove.
• If you select multiple objects in step 1, the system displays the
Remove Objects from Project dialog box.
• If you select a single object, the system displays the Remove an Object
from Project dialog box.
The projects in which the selected objects are assigned, and in which you
are a privileged member, are displayed in the Projects for Selection list.
3. Select the project or projects from which the objects will be removed and
move them to the Selected Project list using the right-arrow button.
Note
To select all projects in the list, click the double-arrow button.
4. Do one of the following:

• To remove the objects from the projects and retain the dialog box,
click Apply.
• To remove the projects and exit the dialog box, click OK.

Working in projects
8.8 Activity
• Add an object to a project.

Working in projects
8.9 Finding projects and project data

Two standard search forms, the Projects search form and the Objects in
Projects search form, can be used to locate projects and objects assigned to
projects.

Working in projects
8.9.1 Find projects
1. Click Search on the toolbar or select Advanced from the perform

search menu at the top of the navigation pane.

3. Select Projects from the System Defined Searches folder.

The Projects search form appears in the Search view.
4. Click Clear all search fields to clear the contents of the search form
boxes.
5. Type the project search criteria in the applicable search form boxes.
6. Click Execute the search .

A list of the project or projects that match the search criteria appears in
the Search Results view.

Working in projects
8.9.2 Find objects in projects
1. Click Search on the toolbar or select Advanced from the perform

search menu at the top of the navigation pane.

3. Select Objects in Projects from the System Defined Searches folder.
4. Click Clear all search fields to clear the contents of the search form
boxes.
5. Type the project search criteria in the applicable search form boxes.

Working in projects
6. Click Execute the search .

A list of the objects assigned to the project or projects that match the
search criteria appears in the Search Results view.

Working in projects
8.10 Activity
• Find objects in a project.

Working in projects
8.11 Summary
• Viewing project data
• Assigning objects to projects
• Assigning secondary objects to projects
• Removing objects from projects

Lesson
9 Opening and viewing product

structures
Purpose
In this lesson, you learn the basics of using Structure Manager to open and
view product structures.
Objectives
• Identify BOM view objects.
• Open a product structure in Structure Manager.
• View and print a product structure.
• View assembly components in Structure Manager.
Help topics
• Getting Started with Product Structure
• Structure Manager Guide

Opening and viewing product structures
9.1 Understanding product structure

In Structure Manager, you can create, view, and modify a product structure,
sometimes called a bill of materials (BOM).
An indented view of the assemblies and piece parts that comprise the product
structure illustrates the relationship between the assemblies and piece parts.
An assembly has structure of its own; a piece part has no structure.
In My Teamcenter, you can attach CAD files, specification documents, or
other information to the top-level assembly (the product itself), or to any of
the assemblies or piece parts.
You can build, view, and manipulate the product structure in Structure
Manager or you can import it from an MCAD system such as NX.
Using Structure Manager, you can visualize assemblies, make visual
comparison, and analyze clearances and tolerances.

9.2 Basic tasks

Use Structure Manager to create, view, and modify product structure (an
engineering bill of material) and its associated occurrence data.
Task Overview
Browse product You can view the assembly structure of a product,
structure bill of navigate around the structure, and find components
material (BOM) in the structure.
From any point in the structure, you can access the
associated data, for example, datasets.
Visualize product You can display a graphical representation of the
structure product, if the relevant DirectModel dataset image
is associated with the product structure. Selecting a
component in the viewer highlights the component in
the product structure and vice versa.
Build and edit You can create and modify BOM using Cut, Copy,
structure Paste, and Remove commands. You can specify
related information, such as torque settings, for any
component.
Note
If another user is editing an assembly (single
level) within the product structure, Teamcenter
prevents you from making changes until the
other user has saved and, if applicable, checked
in the changes.
Make where-used A where-used search reports all assemblies in which a
searches part is used. Perform this search in the Referencers
pane.
Compare product You can compare two Structure Manager structures,
structures each configured as required, to highlight any changes.
Use item revision You can set a revision rule that determines the revision
configuration of each component that Teamcenter configures. This
allows you to configure a structure as it was or will
be on a particular date, for example, by utilizing
effectivity data on each item revision (release status).
Configure variant You can set a variant rule to determine which
products variant components are configured in the structure.
Teamcenter references variant data you create on
the structure to determine the appropriate variant
components.

Task Overview
Open a structure in You can load a complete BOM or selected components
NX or Teamcenter from the structure into NX directly from Structure
lifecycle Manager, if you use Teamcenter Integration for NX.
visualization
Teamcenter Integration for NX allows you to make
changes to the assembly structure in NX and
synchronizes the changes into the Teamcenter
database.
Note
You can also manage product structures
created in other CAD packages, if you have the
appropriate integration software.
For more information, contact your Siemens
PLM Software representative.

9.3 Structure Manager interface
1 Structure navigation Allows you to navigate BOM, expanding or

tree collapsing nodes to view the appropriate
data. The images in the tree indicate the
purpose of each node.
2 Data pane Allows you to view data about the selected
line. To display a different data pane, click
its tab.
3 Search area Allows you to search for a structure and
configure it with commonly used data.
Not all menu commands and buttons may be visible on your system, as the
administrator can hide or reveal only those commands and buttons that are
appropriate for your site.

9.4 BOM view objects

Teamcenter stores product structure and occurrence property data in BOM
view revision objects associated with item revisions.
• When an item is an assembly, you see a BOM view object that exists for
the item, and a BOM view revision object that exists for the item revision.
Note
This is true for all revisable objects in Teamcenter including product
Item and Item Revision, MEProcess and MEProcess Revision,
and MEWorkarea and MEWorkarea Revision objects.
• The BOM view object symbol, , identifies the BOM view and BOM
view revision objects.
• Teamcenter automatically creates a BOM view revision when you initially

create the structure in Structure Manager or Manufacturing Process
Planner.
• BOM view revisions are only meaningful in the context of the item
revision in which they are created.
You can paste references to BOM view revisions into a regular folder, for
example, to collect together objects to submit to a release. However, you
cannot copy references of BOM view revisions into other item revisions.
• The BOM view object is a reference to the latest BOM view revision object.
• Use Structure Manager or Manufacturing Process Planner to view and

work with the data that resides in the BOM view revision object.

9.5 BOM view types

The view type is an attribute of a BOM view revision that specifies its
intended usage, for example, design or manufacture.
• Teamcenter comes with defined BOM view types.
• The administrator defines a set of view types for each site.
• Any number of view types can be defined, but most companies only
require a single view type.
The default BOM view type view is used in this training material. This type
is standard with Teamcenter.

9.6 View a product structure in Structure Manager

There are several ways to launch Structure Manager and view a product
structure:
• Double-click the BOM view revision object.
• Select the BOM view revision object and click the Open button .
• Right-click the desired item, item revision, or BOM view revision object
and choose Send To®Structure Manager.
When you launch Structure Manager, the menus and toolbars include options
specific to the Structure Manager application.

9.7 Product structure display

Product structure appears in an indented BOM format similar to those used
in many CAD and ERP systems.
The product structure shows each component (line in the BOM) represented
by a node.
By viewing the product structure, you can see which components are piece
parts and which are assemblies.
• Each component (node) in the tree lists several properties which may
include:
o Item ID and name

Depending on your company’s data, an item may represent a part or
assembly, a CAD design, or both.
For example, 2212/A;1–R-Wheel in the example is a part.
o Item revision
If no configured revision is found in a precise structure, Teamcenter
displays ??? for the revision. If this is an assembly, it cannot be
expanded.
o Item type
o Quantity
This is the total quantity represented by the line, which is greater
than one if the line is packed or represents an aggregate occurrence. If
any of the values are As Required, the quantity is shown as A/R.
o View type for assemblies
o Other properties configured for your site or you have added to the
display.

• Assembly nodes have a + (plus) or – (minus) symbol:

o + (plus) symbol indicates the structure is not expanded.
Double-click the node, click the + symbol, or choose View→Expand
Below to expand the structure
o – (minus) symbol indicates the structure is expanded.

Double-click the node, click the – symbol or choose View→Collapse
Below to collapse the structure.
o Nodes with substitute components have a symbol.
o Nodes with global alternate components have a symbol.

o Nodes that are variant components have a symbol.
o Teamcenter also uses colors to indicate a particular status of the

certain lines in the product structure, as follows:
Imprecise assemblies
The structure line appears in white.
Precise assemblies
The structure line appears in green.
Substitute occurrence
The structure line appears in gray.
Note
All colors are defaults and may be changed by editing the
relevant user preference.

9.8 Adjust the product structure columns display

You can adjust the columns shown in the BOM display for the product
structure. You can click a column header and drag it to a new location. You
can also right-click a column header and choose the desired command from
the Table Function Menu.

9.9 Viewing product structure properties

A line in the product structure includes multiple properties, including:
• Item properties
• Item revision properties
• BOM view revision properties
• Occurrence properties
The use of an item revision in the context of its parent assembly.
• Display properties
Properties calculated to show the state of some other property.

9.9.1 Insert or remove a property column
You can add a new column to the structure tree from a list of Structure
Manager properties:
1. Right-click any column header and Teamcenter displays a shortcut menu.
2. Choose Insert Column from the shortcut menu and Teamcenter displays
the Change Columns dialog box.
3. In the Change Columns dialog box, highlight the required properties and
click Add to transfer these properties to the right-hand pane.
4. Click Apply to add these properties as new columns.
To remove a column, right-click in the column and choose Remove this

column from the shortcut menu.

9.10 Managing column configurations

Your administrator can save and apply column configurations available for
your group and configure your view of Structure Manager to view and edit
only those properties that your group deals with. Depending on your role,
you can save column configurations.
• A site administrator can save configurations with the scope set to User,
Group, or Site.
• A group administrator can only save configurations with the scope set
as User and Group.
• If a site has multiple levels of groups, users can access the site
configurations and configurations for all groups to which they belong.

9.11 Expanding or collapsing an assembly

When working on a structure, it may be convenient to load the entire
assembly structure or a major section of it at the same time.
Any further expansion or collapsing of the structure is faster, because this
only requires a change to the display of the structure, not a full reload.

9.11.1 Expand an assembly
• Choose View→Expand Below... to expand all nodes below the currently

selected node or nodes. Teamcenter displays the Expand to level dialog
box, allowing you to enter the desired number of levels to which you want
to expand the structure.
The structure expands to the piece parts, where appropriate. Teamcenter

loads any necessary components from the database.
Note
If you try to expand the structure by fewer levels than the existing
expansion, the display does not change unless you select the Collapse
to level check box in the dialog box.
If you try to expand a large assembly, Structure Manager displays an
Expanding the tree may take a long time. Do you want to continue?
message. Click Yes to continue with the expansion.
If expansion of selected BOM line types is restricted by a closure rule,

Structure Manager displays a Cannot expand BOM line message.

9.11.2 Collapse an assembly
Collapse an expanded assembly in one of two ways:

• Select the expanded node and choose View→Collapse Below.
Or
1. Select the expanded node and choose View→Expand Below.... Teamcenter
displays the Expand to level dialog box.
2. Enter the level to which you want to collapse the assembly, select Collapse
lower level and click OK.
For example, if the assembly is expanded to five levels and you enter 3,
Teamcenter collapses the assembly to three levels.

9.12 Sorting the structure tree

You can sort the product structure tree on the value of a column in the tree
table, by clicking the header of the selected column. Teamcenter resorts each
level of the table accorded to the values displayed in the selected column
within an assembly level.
• The first time you click a column, the tree is sorted in ascending order;
each subsequent time you click the column header, the tree table is
re-sorted in descending, unsorted, and then ascending order.
• An arrow appears in the column header to indicate the column according

to which the tree is sorted.
The direction of the arrow indicates if it is sorted in ascending, descending
or unsorted order.
Note
Once you sort the tree according to a column value, it remains sorted,
even if you add structure lines. If you paste a line into a sorted tree, the
newly pasted line appears at its correct (sorted) location within the tree.

9.13 Print the product structure

There are several ways you can print the product structure depending on
what level of information you want to print.
To print the current view of the product structure, as shown in the Structure
Manager window, select a BOM line and choose File®Print....
• Select Object Properties to print the properties from the database.
• Select Contents (Current Display) to generate the report shown previously.
• Select Application (HTML/Text) to generate a report showing the column

headings and values for the BOM lines.
• Select Application (Graphics) to generate a graphic of the product

structure including the BOM lines and values. The graphic is printed
according to the current setup you define.
You can choose to send the output to a Web page, a printer, or a file.
You can also print the product structure using File®Print..

9.14 View assembly components in Structure Manager

While browsing the BOM of a product, you may need to find out more specific
information about individual components of the assembly.
You can view visualization data in Structure Manager and other data in
My Teamcenter.
• You can view visualization data for the BOM assembly and components
using Show/Hide Data Panel in Structure Manager.
• You can view other assembly components in the My Teamcenter tri-pane

window.

9.15 Activity
In the Opening and viewing product structures section, do the following
activity:
• View a product structure.

9.16 Summary
• Identifying BOM view objects
• Opening a product structure in Structure Manager
• Viewing and printing a product structure
• Viewing assembly components in Structure Manager

Lesson
10 Controlling assembly
configuration views
Purpose
In this lesson, you learn how to control assembly configurations using the
Structure Manager application.
Objectives
• Recognize the types of release status.
• Change revision rules for the product structure and view the results.
• Use revision effectivity to control when various revisions of an item are

in effect.
• Differentiate between a precise and imprecise structure.
Help topics

Controlling assembly configuration views
10.1 Introduction to revision control

Teamcenter allows you to manage changes to the product structure by
revisioning of items.
An item revision defines the state of an item at a particular time. When the
item moves to a new life cycle stage, typically with a changed state, a new
item revision is generated in Teamcenter.
Changes that may necessitate a new item revision include:
• Addition or removal of (product structure) components
• Changes to encapsulated data (datasets) as well as to the metadata that

describes the item.
For changes that do not affect the form, fit, or function of the item, a new
item revision is created.
For changes that affect form, fit, or function, a new item is created and the
assembly revision is incremented, if it is released ( for example, released
to production).
This approach ensures interchangeability is maintained. This method of

change control is widely used for large, complex structures with many layers
of nested subassemblies or components.
You can set the configuration of the structure for a specific time by applying
the appropriate revision rule. A revision rule consists of any number of rule
entries, each defining a parameter Teamcenter uses when evaluating the
revision to configured.
You cannot view multiple configurations at the same time; if you want to see
another configuration, you must apply a different revision rule.

10.2 Release status

Each item revision has a release status property.
• In Structure Manager, the release status of an item revision is shown in
the Item Rev Status column.
• In My Teamcenter, the release status of an item revision is shown in the

Release Status column in the Details tab.

10.2.1 Release status types
The Teamcenter software is delivered with several standard release status

types. Status types can also be defined by your application administrator.
The release status types defined for this training include:
• (Empty value)
If the item revision has no value for status, it is said to be working data.
This is the default status the data gets upon creation.
• Approved
Data stored with item revisions that have obtained this status are
considered production data. The data is in a write-protected mode
meaning it cannot be changed unless a new item revision is created.
• Validation
Data stored with item revisions that have obtained this status are also
in a write-protected mode and cannot be changed unless a new revision
letter is created, however, the data is not intended for production use. The
designer or engineer can arbitrarily apply this status to freeze the data
for use in building prototypes or providing preliminary data to customers
and suppliers.
• Pending
Data stored with item revisions that have obtained this status are not in a
write-protected mode and can still be changed. This status informs the
consumer of the data that this revision is currently in an engineering
change process. At the successful completion of the process, the release
status value automatically changes to Approved.
Note
This list of release status types is an example developed for this
training material. Your company may have different release status
types with different meanings.

10.3 Revision rules

Revision configuration allows you to select the appropriate revision of
components in the product structure.
A revision rule sets the criteria for selecting the revision, as follows:
• Selects working revisions and, optionally, specifies the owning user or
group.
• Selects released revisions by specific status, according to a status

hierarchy or latest status (by date released).
• Optionally, specifies the date or unit number effectivity of the revisions.
• Selects the latest revisions according to the revision ID, by

alphanumeric/numeric order or creation date.
This selection is independent of whether revisions are working or released.
Each of the above criteria is defined by a revision rule entry. The order of the
rule entries can be modified to change the precedence used when evaluating
the revision rule.
In Structure Manager, the current revision rule setting displays to the right
of the item revision name, in the line above the column headings.
The following graphic shows the revision rule setting is Latest Working.
Examples of revision rule definitions:

Revision rule Definition
Precise
Working ( )
Latest Working
Has Status (Any Release Status, Configured
Using Released Date )
Any Status, No Has Status(Any Release Status, Configured
Working Using Released Date )
Note
The application administrator for your site can add, remove, or modify
the revision rules and their definitions.

10.3.1 Revision rules list
Revision rules used in this training configure assembly product structures as

follows:
• Any Status; Working
Loads the latest revision to which a release status was assigned or, if
none exists, the working revision.
• Latest Working
If an imprecise assembly, loads the latest item revision regardless of its
release status. With this rule in effect, you can view work-in-progress
item revisions.
If a precise assembly, loads the specific item revision that was in effect
the last time the assembly item revision was saved. If newer revisions
of the assembly components have been created since the last time the
assembly was saved, they do not display regardless of whether they have
a release status value.
• Precise Only
If a precise assembly, loads the specific item revision that was in effect
the last time the assembly item revision was saved. If newer revisions
of the assembly components have been created since the last time the
assembly was saved, they do not display.
If an imprecise assembly, there’s no configured revision to display.
• Any Status, No Working

Loads the latest item revision with a release status. With this rule in
effect, you only view item revisions that have been released.
Note
This list of revision rules is an example used in this training. Your
company may have a different list of revision rules.

10.4 Changing the default revision rule setting

When you log on to the system, a revision rule is in effect that controls which
item revisions you see listed when you view the assembly structure. A default
revision rule is set by your application administrator.
1. Choose Edit®Options and select Product Structure.
2. Select the desired revision rule from the Default Revision Rule list to
change your default revision rule setting to another available rule.
3. Click OK.

10.4.1 Setting an ad hoc revision rule
Instead of changing your default revision rule, you can change the revision
rule in effect on an ad hoc or as needed basis, while viewing a product
structure. In the Structure Manager window, choose Tools®Revision
Rule® View/Set Current from the menu bar or click .
The View/Set Current Revision Rule dialog box appears showing the list of
available revision rules. Select the desired rule and click OK.
The corresponding change to the assembly appears in the Structure Manager

window.

10.5 Activity
In the Controlling assembly configuration views section, do the following
activity:
• Configure product structure using revision rules.

10.6 Understanding precise and imprecise product structures

In Teamcenter, you can create and manage assembly structures as precise or
imprecise product structures.
• Precise assembly
Precise assembly structures are fixed structures of items configured with
specific item revisions.
A precise assembly has links (occurrences) to item revisions of its

components.
When you modify a component to a new revision, you must manually

update the assembly by removing the old revision of the component
and adding the new revision.
You configure the precise references with a revision rule containing a

Precise rule entry.
However, you can dynamically configure a precise assembly (treat it
as imprecise) by applying a revision rule that does not contain the
precise rule entry, or has the entry at a lower precedence.
• Imprecise assembly
Imprecise assembly structures are dynamic structures of items configured
by a revision rule to determine the item revision included in the structure.
An imprecise assembly has links (occurrences) to items of its

components.
Teamcenter automatically reconfigures an imprecise structure when

new parts are released or created, or other changes are made.
Consequently, it is not necessary to make a copy of the structure and
manually update it if you make changes.

10.6.1 Using precise and imprecise assembly structures

Precise Assembly 01
Precise assembly structures are useful when Assembly 01/A
the product structure (BOM) configuration Part 01/B
must be closely controlled. Part 02/A
For example, assembly structures must Particular revisions are
be closely controlled during the product explicitly connected.
design phase or in aerospace manufacturing
environments.
Imprecise Assembly 02
Imprecise assembly structures are useful Assembly 02/A
in situations where the BOM has the same Part 03
underlying product structure but is configured Part 03/A
to suit a user’s particular need. Part 03/B
Part 04
For example, an engineer can view the BOM
configured with item revisions that have been Part 04/A
released for production or, alternatively, the Part 04/B
latest working item revision of components in Part 04/C
the BOM.
No particular revisions
are connected. A revision
rule sets the applicable
revisions.

10.6.2 Product structure background color
• By default, a precise assembly structure appears with a green background

color when viewed in Structure Manager.
• By default, an imprecise assembly structure appears with a white

background color when viewed in Structure Manager.
Your administrator can modify the background colors.

10.6.3 Revising precise assembly structures
• When the parent assemblies are released and consequently can no longer
be modified, any change requires manual updates to revisions of related
assemblies.
• When the parent assemblies are released and can no longer be modified,
any change may result in significant revision ripple.
If you incorporate a new revision of a component, you must manually
revise every affected parent assembly up to the top of the precise product
structure.

10.6.4 Revising imprecise assembly structures
• When the parent assemblies are released and consequently can no longer
be modified, any change automatically updates the revisions of related
assemblies according to the selected revision rule.
• If you incorporate a new revision of a component, no manual revisions

are required to the affected parent assemblies in an imprecise product
structure.

10.6.5 Changing between precise and imprecise
Depending on your business practices, it may be necessary to change from

precise to imprecise as the assembly reaches different stages in the product
life cycle.
For example, you may want to change from precise to imprecise when the
assembly is released from engineering to manufacturing.
You can use the Edit®Toggle Precise/Imprecise command in Structure
Manager to change the assembly structure from precise to imprecise and back
again within the following constraints:
• The assembly BOM view revision has not been released.
• You have modification privileges to the assembly.

10.7 Activity
In the Controlling assembly configuration views section, do the following
activity:
• Toggle between a precise and imprecise assembly.

10.8 Understanding revision effectivity

You can use revision effectivity to control when various revisions of an item
are in effect. The product structure can be configured for a particular date
or unit (serial) number by the application of a revision rule. The following
example shows an application of revision effectivity.
Rev A does not make it to
PRODUCTION
start of production
(Effectivity)
Time lag between approval No end for

and start of production rev B planned
effectivity of
rev B
No end for
rev C planned
effectivity of
rev C
Release Rev B Rev C effective for

Status effective for production from here.
production At this point, rev B is no
from here longer effective
Approved for
(Release Status)
production
rev B rev C Rev C approved, but small
DESIGN
amount of time elapses before

planned start ofproduction
Released for
review
rev A
Start of
development Development of Rev A does not An improvement needs to be
the item starts pass review stage, made to the item, so rev C started
here with rev A so rev B started
When you set an effectivity range, consider the following:

• You express effectivity as a start to end range of dates or unit numbers,
for example, 1–May-2007 to 31–May-2007.
• You can configure open-ended effectivity with an infinite end date or unit
number (UP) or until stock is out (SO).
For example, 1–May-2007 to UP or 1–May-2007 to SO. UP and SO are
both provided to aid integration with ERP systems but, in Teamcenter,
they are functionally the same.
• Effectivity may be discontinuous, for example, 1–May-2005 to

31–May-2007, 1–July-2007 to UP.
• Effectivity can be shared. A reusable effectivity has an identifier.
• You must qualify unit effectivity by an end item, for example, Unit 10
to UP, End Item A1000.

10.8.1 Revision effectivity configuration algorithm
You can use Has Status revision rule entries to configure revisions by their
effectivities. A revision rule entry is qualified by one of the following:
• Configured by effective date
• Configured by effective unit
For any item, a revision rule must configure only one revision, but revisions
may have overlapping effectivities.
Typical effectivity unit configuration
The following is an example of effectivity ranges for three revisions of
an item with open-ended unit number effectivity. If the structure is
configured at unit 7, revision A is configured. If the structure is configured
at unit 15, revision B is configured.
Rev C - Unit 20 - UP
Rev B - Unit 10 - UP
Rev A - Unit 1 - UP
7 10 15 20 Unit
Effective Point (Unit)

Revision effectivity configuration algorithm with closed range

The following is an example of effectivity ranges for three revisions of an
item with closed range effectivity, that is, with an end unit or date set.
A check mark (tick) indicates the particular revision that is configured
for a given effectivity point.
• When the effective point line crosses only one revision, the revision is
configured, as shown for revisions A and D.
• If the effective point line crosses more than one revision, the revision
with the latest start date or unit is configured, as shown for revision B.
• If two or more revisions have the same start date (for example,
revisions C and D), the revision with the latest release date is
configured, as shown for revision D.
Rev D
Rev C
Rev B
Rev A
Effective Point (Date/Unit)

10.8.2 Using date effectivity
Date effectivity allows you to specify a valid range of dates for a particular
item revision. The effectivity definition may be:
• Open
For example, an item revision may be valid from 05 January onward.
• Closed
For example, an item revision may be valid from 01 January to 30 April.

10.8.3 Using unit number effectivity
Unit effectivity allows you to specify a valid range of unit numbers for a
particular item revision.
• Unit effectivity is always specified in the context of an end item to which
the units apply.
• You can specify a discrete, noncontinuous range, if appropriate.

10.8.4 Displaying and editing revision effectivity
By default, revision effectivity data is not displayed in the Structure Manager

properties table. Before editing revision effectivity, you must first display
the data.
If you are working with revision effectivity, you may want to display the
Revision Effectivity property.

10.8.4.1 Display revision effectivity data
1. Select the line whose item revision effectivity data (ranges of dates or unit
numbers for which the revision is effective) you want to view.
2. Choose Tools→Effectivity→Revision Effectivity.

Teamcenter displays the Effectivity dialog box. This dialog box lists all
the effectivity ranges for each status attached to the item revision.
Note
While you can set date effectivity without an end item, unit
effectivity must always have an end item.

10.8.5 Best practices when applying effectivity
Some suggestions for managing effectivity follow:

• Revision effectivity allows you to see the status of the product structure at
any point in its development.
• Revision effectivity is simpler and easier to manage than occurrence

(structure) effectivity. It works well with NX and other CAD integrations.
• If you configure mixed unit and date effectivity schemes, implement

unit effectivity on the higher levels of the product structure and date
effectivity on the lower levels.

10.9 Summary
• Recognizing the types of release status
• Changing revision rules for the product structure and viewing the results
• Using revision effectivity to control when various revisions of an item

are in effect
• Differentiating between a precise and imprecise structure

Lesson
11 Creating and managing

product structures
Purpose
The purpose of this lesson is to learn how to control assembly configurations
using the Structure Manager application.
Objectives
• Create a product structure.
• Find a component in a structure.
• Modify a product structure.
• Add replacement, alternate, or substitute components to a structure.
Help topics

Creating and managing product structures
11.1 Build and edit product structures
Using Structure Manager, you can:

• Create new product structures manually.
• Duplicate an existing product structure to create a new one.
• Work with structures generated from CAD systems.
After a product structure is created, you can modify it using the Structure
Manager application, as necessary, to reflect any changes to the product
design.

11.1.1 Create a new BOM view revision automatically
If there is no BOM view revision in an assembly item revision when you

add the first component, Teamcenter automatically creates one. It sets the
precision (precise/imprecise) of the BOM view revision as follows:
• If the item revision is a component, the precision is that of the parent
assembly in the current window.
• If the item revision is at the top-level of the structure, the precision is set
according to your default BOM view precision option.

11.1.2 Setting find numbers
Teamcenter assigns a unique find number to each line in the product

structure. They provide an additional identifier or label for organizing the
items in a single-level structure relationship.
• When you add an item to the product structure, the line receives the next
available find number in the defined sequence.
By default, the numbers are assigned in increments of 10; that is, if the
previous line added was assigned a find number of 20, Teamcenter assigns
a find number of 30 to the next line added.
• Depending on your CAD environment, each find number may map to a

callout number or a line number in the CAD design.
If the find number is linked to the callout, changes of quantity made in
the CAD design may directly update the quantity shown in the product
structure.
• If appropriate, you can rearrange the structure in find numbers by

clicking the Find Number column header.
This rearrangement persists for future Structure Manager sessions until
you make another selection.
Your Teamcenter administrator can configure find number processing.

• Change the way find numbers are assigned to BOM views and BOM
view revisions.
• Allow Teamcenter to validate that find numbers are not zero and unique
within the same parent.
• Disable updating of duplicate find numbers of the same item.

11.2 Save product structure changes
In Structure Manager, use Save to save all the changes made in the
currently displayed structure window. Changes to the structure result in
a modification to BOM view revisions, for example, adding or removing
components or changing occurrence attributes such as notes and find
numbers.
An asterisk in the Structure Manager tab indicates a modification to the

structure has been made, but not saved. Saving the structure removes the
asterisk.
Teamcenter prevents you from accidentally closing a structure window

without saving changes.

11.2.1 Saving changes with multiple windows
You can open multiple windows by using the split window button .
• If you make structure changes, only those changes made in the window
where you choose the Save command are saved. If you create additional
windows and open structures in those windows, changes made in the
other windows are not saved.
• If you want to save changes made in other windows, you must explicitly
choose the Save command in the window in which the structure changes
were made.
Window 1 B C Window 2 D
K F J L J M L
M E F Z E T
Z E T
Example of saving in multiple windows

• In window 1, remove E from M. This also causes E to be removed from
M in window 2.
• In window 2, remove L from D and change a note on J. Add a note to Z

in M and this change is also seen in window 1.
• In window 1, save the product structure. This action saves changes to

assembly M but not D.
Note
Changes are saved, regardless of where they are made. Therefore,
the changes made in window 2 to M are also saved. The save action
in window 1 thus causes a partial save of the changes made in
window 2, on those assemblies that are also seen in window 1.
• In window 2, save the product structure. This action saves changes to

assembly D.

11.2.2 Refresh the Structure Manager window and resynchronize to

database
Structure changes you make are propagated across all product structure
windows in a particular session. However, changes are not propagated across
sessions.
• Choose View→Refresh Window to resynchronize the current window to
the database. This action picks up changes made in other sessions and
saved since you loaded the product structure. This function does not cause
your own changes to be saved or lost.
Note
Teamcenter does not permit other users to change any BOM view
revision that you are editing. The BOM view revision is locked by the
first person to make a change, whether this is adding or removing a
component or modifying any of the occurrence attributes of any of the
components.

11.2.3 Close the product structure window
If unsaved changes are made in a product structure window, and you choose
the File→Close menu command, Teamcenter displays the Close Application
- Save Modifications dialog box.
The unsaved modifications display and are selected for update.

• Click OK to save all selected items and close the dialog box.
• Updates to items not selected are lost when you click OK.
• Click Cancel to return to the Structure Manager session without saving

changes.

11.3 Finding a component by property

You can search the displayed product structure to find one or more specified
components.
This capability is useful if you are not familiar with the structure and want
to navigate quickly to a particular component. You can construct a search
expression from any combination of the properties displayed in the columns
in the product structure tree.

11.3.1 Find components by property
1. Expand the displayed structure fully for those assemblies you want
to search. The search function does not find hidden components in
unexpanded assemblies.
2. Click Find component(s) in display at the lower left of the Structure

Manager window.
Teamcenter displays the Find in Display dialog box.
Note
The search starts at the top-level item in the structure, not at
the currently selected line. You do not select an assembly in
which to look for the component. If you want to restrict the
search to a particular assembly, open the subassembly in a new
Structure Manager window by selecting it and choosing File→Open.
Alternatively, you can collapse all other assemblies except the one
you want to search.
3. Double-click the Property Name text box to select a property from the list
of available columns.

4. Double-click the = box to select a different operator.

Tip
You can use the following relational operators to define property
searches:
Relational operator Definition

= or = = Equal to
> Greater than
< Less than
>= Greater than or equal to
<= Less than or equal to
!= Not equal to
– Range
| OR
“” Exact string
& AND
The operators <, <= ,>, >= apply to numeric properties only.
5. Click the Searching Value text box and type the value you want to search
for.
Note
Partial matches are selected for string properties. Wildcards are not
supported, and the search is not case sensitive.
6. Add further clauses to the search condition by clicking .

You can also double-click AND to change it to OR.
7. If necessary, reorder clauses by clicking and .
8. When the search condition definition is complete, click Find .

Teamcenter highlights the first line it finds that matches the search
condition, and the Find dialog box shows a count of the total number of
matching lines found.

9. Click Find next one and Find previous one to step through the
matching lines one at a time. Alternatively, you can click Load All to
select all matching lines at once.

11.4 Modify a product structure

Any modification you make to the product structure changes the BOM view
revision in the parent assembly. Modifications that change the BOM view
include:
• Add a component.
• Remove a component.
• Move a component to another assembly.
• Replace a component.
• Substitute a component.
To modify a product structure, you must have write access to the BOM view
revision.

11.4.1 Add components to a product structure
There are several ways you can add components to the product structure:
Copy and paste Allows you to copy existing items, parts, and designs, and
objects. paste references into the product structure.
Use quick add Allows you to add new components by typing in the item,
part, and design identifiers.
Add a Allows you to specify additional data about the use of a
component to an component as you add it to the structure, for example,
assembly using a quantity or find number.
Edit®Add...
Create a new item Allows you to use a top-down approach by simultaneously
or item revisions modelling structure and creating new items, parts, and
designs.

11.4.2 Concurrent updates safeguard
If another user is editing a single-level assembly within the product structure,

Teamcenter prevents you making changes until the other user has saved
the changes.
• A warning message identifies the other user working on the assembly.
• This safeguard does not prevent you making changes to other assemblies
that are not being worked on.

11.4.3 Copying and pasting objects
The Teamcenter clipboard is shared by all applications. For example,

objects you place on the clipboard by copying them in My Teamcenter may
subsequently be pasted into the product structure in Structure Manager.
You can also edit the product structure with the Remove, Copy, Paste, and
Paste Special commands.
When you paste an item or item revision from the clipboard, Teamcenter
creates corresponding components in the selected assembly in the product
structure. Structure Manager allows you to paste items and item revisions
(including parts, designs, and their revisions), structure lines, and item
elements; other objects are ignored if you attempt to paste them.
If you cut and paste structure lines, the pending lines are removed from the
clipboard after you choose Paste or Paste Special. If the cut lines are in the
same structure as the target, Teamcenter performs a move action, rather
than a cut and paste action.

11.4.3.1 Copy and paste an item or item revision
1. Select and copy the item or item revision (including parts, designs, and
their revisions) from elsewhere in the product structure displayed in
Structure Manager or from another application such as My Teamcenter.
You can copy the item or item revision by clicking Copy , choosing
Edit→Copy, or pressing the Ctrl+C keys. This action places the item
or item revision on the clipboard.
2. In Structure Manager, select the assembly into which you want to add
the component.
3. Paste the item or item revision by clicking Paste , choosing Edit→Paste

or pressing the Ctrl+V keys.
Pasting does not remove the object from the clipboard. Therefore, you can
click Paste again to add another line of the same item revision to the
assembly. Another Copy operation replaces the previous clipboard contents
with the new object.

11.4.3.2 Copying and pasting occurrence attributes of components
When you copy a component from an assembly and then paste it elsewhere:
• The occurrence attributes (for example, the quantity and any notes) are
also copied and pasted.
• The find number is not copied.

Teamcenter automatically generates the find number according to the
position of the component in the target assembly.
• If the component has an associated substitute list, this is also copied and
pasted.
If you paste the component into My Teamcenter, rather than Structure

Manager, Teamcenter pastes the lines as individual item revisions.

11.4.4 Add existing components to selected BOM lines
Often it is more convenient to insert the component by typing its identifier

instead of pasting it from the clipboard.
1. Select the assembly into which you want to add the component.
2. Click the text box in the lower left of the Structure Manager application
window.
3. Enter the component ID and click .
You can only use Quick Add for adding existing items.
If there is no match for the entered component ID in Teamcenter, the
following dialog box appears.
To create a new item and add it to the structure, choose File→New→Item.

11.4.5 Paste a component
You can specify additional data about the use of a component as you add it to
the structure, for example, a quantity or find number.
• Choose the Edit→Paste Special to insert an existing component that you
copied to the clipboard into the structure.
Unlike Add..., Teamcenter prepopulates the Item ID, Revision ID, and
Name boxes of the Paste Special dialog box with item or item revision
information from the clipboard.

11.4.6 Remove a component
1. Select the component or group of components to remove from the product

structure tree.
2. Click Remove a line , choose Edit®Remove, or press Ctrl+R.

The selected components are removed from the structure. If you select a
line that has substitutes, those are also removed.
Note
This action does not place the selected line or lines on the clipboard.

11.4.7 Move a component to another assembly
1. Select the component or group of components to move to another assembly.
2. Click Cut on the toolbar, or choose Edit®Cut, or press Ctrl+X to place

the selected components on the clipboard. The affected component lines
are unavailable.
3. Select the target assembly.
4. Click Paste on the toolbar, choose Edit®Paste, or press Ctrl+V.

New component lines appear under the selected assembly, and the
unavailable lines are removed from the structure.
Note
Lines unavailable after a cut command are not actually removed
from the structure until you paste them elsewhere in the structure.
If you place another object on the clipboard before pasting, the
unavailable lines are restored to their previous state and are
removed from the clipboard.

11.5 Working with replacements, global alternates and substitute

parts
Modifications to a product structure can include:
• Replacements
Replace a part without losing
the occurrence data. Use
this method when replacing
an old revision with a newer
revision of the part, and you
want to retain the occurrence
attributes.
• Global alternates
Indicate the part is
interchangeable with another
part everywhere the part is
used in the product structure.
Alternates are used when
the same part is coming
from multiple suppliers, and
you want those parts to be
interchangeable anywhere in
your product structure.
• Substitutes
Indicate the part is
interchangeable with another
part in a particular structure
in the product structure.
Substitutes are used when
stock for an item runs out.

11.5.1 Replacing a component
You can make the following replacements in a product structure:

• Replace a component without losing the occurrence data.
You can change an item revision in an assembly by cutting out the
old item revision and pasting in the new item revision. However, this
method breaks the occurrence link to the old component, so you lose any
occurrence attributes including notes and the find number of the old
component. A replacement retains the occurrence data.
• Change the revision of a component item in precise assemblies.
You cannot replace one component with two or more components. However,
you can select multiple components and replace each with a single component.
Note
Teamcenter does not verify if the replacement request is valid for your
business data. If necessary, check the validity of the replacement action
with the Teamcenter administrator.

11.5.2 Replace a component
1. Select the component to replace in the product structure.
2. Optionally, copy the replacement component to the clipboard. This action

prepopulates the Replace dialog box with the item identifier and revision
of the replacement component.
3. Choose Edit→Replace....
Teamcenter displays the Replace dialog box. The lower pane of the dialog
box contains details of the selected component to replace.
4. In the upper pane of the dialog box, enter the item identifier of the
replacement component.
If you copied the replacement component to the clipboard, the Item ID,
Revision ID and Name boxes are already populated with those of the
copied component. You can change the identifier if required, but not the
item name; the item name is derived from the item identifier you enter.
You can specify a revision in some circumstances, depending on whether
the parent assembly BOM view revision of the component replaced is
precise or imprecise:
• If the BOM view revision of the parent assembly is precise, you can
specify a revision.
In this situation, you can use the replace command to replace one
component item revision with another item revision or to replace the
component with a revision of a different item. If an item is taken from
the clipboard, Teamcenter determines the revision by the revision rule.

• If the BOM view revision of the parent assembly is imprecise, you

cannot specify the revision. In this situation, you use the replace
command to replace one component item with another item.
If there is not a revision that satisfies the revision rule when you add
the component to the structure, Teamcenter displays the revision as
???.
5. Optionally, use the bottom section of the Replace dialog box to change the
scope of the replacement by clicking one of the following:
• All in parent assembly
Replaces all components of the selected item revision that are in the
parent assembly.
• Single Component
Replaces only the selected component.

Alternatively, to replace one or more items (parts) for another:

1. Select one or more source lines that represent items, and choose
Edit→Copy.
2. Select target lines that represents the same types of item and choose
Edit→Replace.
If you copied more than one source line to the clipboard, but only selected
a single target line, Teamcenter displays the select object for Replace
dialog box. Otherwise, it replaces the targets with the sources and
updates the find numbers, as appropriate. If you attempt to replace an
item or item element with a line of another type, Teamcenter displays an
error message and does not replace any of the selected lines.
3. If Teamcenter displays the select object for Replace dialog box, select the
required source from those listed and click Replace.

11.5.3 Managing global alternates
A global alternate part is interchangeable with another part in all

circumstances, regardless of where the other part is used in the product
structure. A global alternate applies to any revision of the part and is
independent of any views.
Parts and their global alternates are related only in a single direction.
For example, if part A has three global alternates (parts B, C, and D), then B,
C, and D are each a global alternate of A. However, part A is not an alternate
of B, C, or D, as shown next.
Is NOT a Global
Alternate of
Part B
Is a Global
Alternate of
Is NOT a Global
Alternate of
Part A Part C
Is a Global
Alternate of
Is NOT a Global
Alternate of
Part D
Is a Global
Alternate of
Global alternates – single direction

One part can be a global alternate of more than one other part. For example,
part B may be a global alternate of parts E and F, as well as a global
alternate of part A, as shown next.
Is NOT a Global
Is NOT a Global Alternate of
Alternate of Part E
Part A Is a Global
Is a Global Alternate of
Alternate of
Part B
Is NOT a Global
Alternate of
Part F
Is a Global
Alternate of
Global alternates – multiple alternates

Global alternate relationships are not shared. For example, part C is not a
global alternate of part B, even though they are both global alternates of
part A, as shown next.
Is NOT a Global
Alternate of
Part B
Is a Global
Alternate of
Part A Is NOT a Global

Alternate of
Is NOT a Global
Alternate of
Part C
Is a Global
Alternate of
Global alternates – nonsharing

Likewise, global alternate relationships are not chained. For example, if part
B is a global alternate of part A, and part C is a global alternate of part B,
part C is not a global alternate of part A, as shown next.
Is NOT a Global Is NOT a Global

Alternate of Alternate of
Part B Part C
Is a Global Is a Global
Part A Alternate of Alternate of
Is NOT a Global
Alternate of
Global alternates – chaining

11.5.4 Working with global alternates
When working with global alternates, you can do the following:

• List global alternates
1. Select a part in the structure that has global alternates .
2. Click Global Alternates at the bottom of the pane. The Manage

Global Alternates dialog box appears with a list of alternate parts
for the item. The preferred global alternate (if any) is marked with
a check mark.
• Add global alternates
o In the Manage Global Alternates dialog box, click Open to find

and add parts to the list.

• Remove global alternates

o In the Manage Global Alternates dialog box, select a part and click
Remove to remove the part from the list.
Note
If you remove all the global alternates from an item, the
corresponding line in the product structure no longer shows the
symbol.
• Set preferred global alternate

o In the Manage Global Alternates dialog box, select a part and click
Prefer to designate the part as the preferred global alternate.
Note
Once you designate a global alternate as preferred, you cannot
remove this designation. However, you can change the preferred
global alternate to achieve the same effect. In this situation, one
global alternate is always preferred.

11.5.5 Substitute components
Substitute components are parts that are interchangeable with a particular

component in an assembly. Substitutes are often defined for manufacturing
purposes, allowing use of the substitute if the preferred part is unavailable,
for example, due to a stock shortage. Substitutes are specific to a single
occurrence within an assembly.
• Substitute components are item revisions in a precise assembly and items
for an imprecise assembly.
• In an imprecise assembly, the revision rule selects the correct revision

of a substitute component.
Substitute components are identified with the substitute symbol in the

BOM line.

11.5.6 Using substitutes in Structure Manager
• Adding a substitute is a modification to the BOM view revision object, and

you must therefore have write access.
• Substitutes of one occurrence all share the same occurrence attributes, for
example, find number, quantity, and notes, as specified for the substituted
part.
• You can add any number of substitute components for a particular line in
the product structure.
• One of the substitutes is the preferred substitute and is always listed in

the product structure.
Changing the preferred substitute is allowed during the session, but the
change can only be saved if you have write access.
• You can change the preferred substitute.
• Substitutes are unique to the product structure. This means that

identifying a part as a substitute of another part only applies in the
current product structure. Occurrences of the part in other product
structures are not affected.
• To view the substitute components for a part, select the component and
click the List Substitutes button .

11.5.7 Create substitute component
1. Copy the substitute item revision to the clipboard in Structure Manager

or another application.
2. Select the line in the product structure in Structure Manager for which
you want to define this item revision as a substitute.
You can also add a substitute to more than one line in a single operation
by selecting all the necessary lines. If the lines are packed, unpack them
before you select them.
3. Choose Edit®Paste Substitute to paste the substitute directly. You can

also choose Edit®Paste Special and click As Substitute of Selected Line
in the resulting dialog box.
Another method for creating a substitute is to select the line in the BOM
for which you want to add a substitute and choose Edit®Add.... Click As
Substitute of Selected Line in the resulting dialog box.

11.6 Activities
In the Creating and managing product structures section, do the following
activities:
• Create a product structure.
• Modify a product structure.

11.7 Summary
• Creating a product structure
• Finding a component in a structure
• Modifying a product structure
• Adding replacement, alternating, or substituting components to a

structure

Lesson
12 Working with product structures
Purpose
The purpose of this lesson is to learn how to manage assembly configurations
using the Structure Manager application.
Objectives
• Pack and unpack structure lines.
• Mark up and apply markups to a structure.
• Compare product structures.
• Clone a product structure.
Help topics

Working with product structures
12.1 Packing multiple components

Grouping multiple identical components in one level of an assembly is known
as packing. You can pack components if they satisfy all of the following
requirements:
• They have the same item revision.
• They have the same find number.
• None have variant conditions, or they all have the same variant condition.
For example, if a bicycle designer is working on a wheel hub design, it

is time-consuming to negotiate five individual spokes within the wheel
assembly, if each spoke is identical except for its position. All that is necessary
is a Spoke x 5 entry.
Wheel Hub
Spoke x 5
By default, when you pack the product structure, Teamcenter packs by find
number, item ID, and variant condition. This allows you to pack two or
more occurrences of the same item, if each occurrence has the same find
number, item ID, and variant condition. To pack structure lines, they must
all have the same occurrence effectivity object or objects; that is, they must
have shared effectivity; it is not sufficient for the lines to only have the same
effectivity ranges.
Your administrator can define if occurrences are packed on your workstation.
Your administrator may also customize Teamcenter behavior so that the
structure is packed by criteria other than find number.

12.1.1 Unpack structure lines
To unpack lines in the structure, right-click the single packed line and choose
the Unpack menu command, or press the CTRL+SHIFT+N keys.
The packed line separates into individual structure lines, each with its own
set of attributes. You can edit these individual attributes.
By default, all components are initially packed to save space.
Wheel Hub
Spoke
Spoke
Spoke
Spoke
Spoke

12.1.2 Viewing occurrence notes
When you create an occurrence note in the Structure Manager window on

a particular line, Teamcenter populates the value of the corresponding note
with the default value of the note type, if one exists. If a list of values (LOV)
is attached to the note type, you can select a value from the list when you
create a note.
To view occurrence notes:
1. Select the appropriate line in the product structure.
2. Choose View→Notes.
The Notes dialog box appears.

12.1.3 Pack structure lines
To pack lines in the structure that meet the packing criteria, select any one
of the lines and choose View→Pack. Alternatively, you can click the Pack
button in the toolbar.
In the case of the bicycle example, this action collapses the five lines in the
product structure into one line representing all spokes.
A x 5 property is appended in the node of the single line and the Quantity
box shows the value 5. Teamcenter shows True in the Packed column, if that
column is displayed.
Wheel Hub
Spoke x 5
Note
Teamcenter makes no distinction between the sum of a number of
separate occurrences or an aggregate occurrence displayed in the
Quantity column. However, the Pack Count column shows the number
of lines that are packed.

12.1.4 Restrictions on packed lines
The following restrictions apply to all lines in the structure that are packed:
• You cannot edit the Quantity value.
• If any of the packed lines have notes, the notes are replaced by the text
Packed Notes. If none of the packed lines has notes, the notes are blank.
In both cases, you cannot edit the notes.
• Item and item revision attributes such as part name, weight, and cost
remain visible and can be edited if you have the appropriate permissions.
• You can modify the find number. Any such modification applies to each
line in the structure and is visible if the structure is unpacked.
• If any of the packed lines has a substitute, the packed line shows Packed
Substitutes in the Substitute column. The pack count includes the
substitutes.
Your administrator can set specific preferences so that occurrences are

displayed packed when you initially expand the assembly (but not when they
are first added).

12.1.5 Modify quantity for multiple components
In Structure Manager, you specify the value of the Quantity occurrence

property in the units of measure for the component item (for example, 1.5 L
for an Oil item). Unit of measure is an attribute of the item.
Example
The oil component is a part of an engine assembly. The engine needs
two liters of oil. Oil cans are available in 1.5 liters. Therefore, we need
two of them to fill the oil reserve, and we need to specify two occurrences
of the oil component with a quantity of 1.5 liters per can.
Alternatively, you can specify the unit of measure as each, that is, a numerical
value. In this case, you must specify the value as a whole number (for
example, 500).
To increase the number of occurrences in the structure:
1. Copy the 4501/A;1 – Engine Oil item revision.
2. Unpack the engine structure.
3. Select the parent assembly.
4. Choose Edit→Paste Special.
5. In the Paste Special dialog box, enter the quantity to add and adjust
the find number, if needed.
6. Click OK.

To decrease the number of occurrences in the structure:

1. Unpack the structure.
2. Select the line to remove.
3. Click Remove a BOM line .
4. In the Remove dialog box, click Yes.

12.2 Comparing product structures

You can compare two structures to identify changes or differences between
two product structures, for example, to:
• Identify component changes between assemblies
• Test for consistency between multiple views of the same item
• Find differences between differently configured structures
Teamcenter allows you to compare structures in two ways.

• You can compare two product structures (BOMs) in separate Structure
Manager windows.
The differences are highlighted in the product structure trees.
• You can also perform a graphical comparison of two structures.

Teamcenter highlights differences in the viewer.

12.2.1 Product structure comparison modes
You can compare product structures using one of the following standard
modes:
• Single-level mode
Compares only the first level of the product structures. You can choose to
include find numbers in the comparison or exclude them.
• Multilevel mode
Performs a single-level comparison at the top level of the structure.
Teamcenter then makes further single-level comparisons of any
subassemblies that are expanded in the two product structures. You can
choose to include find numbers in the comparison or exclude them.
• Lowest level mode

Compares only the lowest level items of the product structures, ignoring
all intermediate assemblies.
Note
Your Teamcenter administrator may define other comparison modes
for your site.

12.2.2 Compare product structures
You compare two configured structures displayed in separate Structure

Manager windows.
1. Open the source structure in the left window and the target structure
in the right window.
a. Search for and open the source structure in Structure Manager.
b. Click the Split Window button located at the upper right corner
of the Structure Manager perspective to create a new empty (target)
window.
c. Select the empty target window.

Note
A bold black line inside the perimeter of the window frame
indicates the window is selected.
d. Search for and open the target product structure in the target window.
2. After you open the structures in the source and target windows, configure
the structures for comparison. Do this by setting the applicable revision
rule and/or variant rule in each window.
3. Expand and collapse the applicable assemblies in each window to define

the scope of the comparison.
Note
Only the expanded assemblies are included in the comparison.
4. Choose Tools®Compare....
The BOM Compare dialog box appears.
5. In the BOM Compare dialog box, select the comparison mode from the
Mode list.
6. Select the Report check box if you want to display the report pane
summarizing the differences between the structures.

7. Click Apply to begin the comparison.

• Differences in the structures are highlighted in the windows for easy
comparison.
• A red highlight denotes additions to the target with respect to the

source.
• An orange highlight denotes changes in quantity or revision.
• Differences are also listed in the report pane at the bottom of the
window.
Note
Your administrator can modify the colors used to denote differences.

12.2.3 Example result of a structure comparison
The following figure shows the result of a single-level comparison between

two revisions of the same structure.
The difference is also listed in the report pane.

12.2.4 Initiating the graphical comparison
To access graphical comparison feature, load the two parts, or configured

structures in separate Structure Manager windows, and choose
Tools® Graphical BOM Compare.
Teamcenter displays the Graphical BOM Compare dialog box, allowing you to
manipulate the results.
After running the comparison, Teamcenter highlights the following

differences between the two windows in the viewer:
• Adds
Objects that are in the target window but not the source.
• Cancels
Objects that are in the source window but not in the target.
• Moves
Objects that are in different positions in the source and target windows
(the transformation matrix has changed).
• Reshapes
Objects that have an alternative representation between the source and
target windows.

Note
However, if you run the Graphical BOM Compare against two parts
and not two configured structures, the Graphical BOM Compare dialog
box looks differently. You do not see Adds, Cancels, Moves, Reshapes,
and All if you load two parts.
You can use the comparison sliders in the Graphical BOM Compare dialog
box to dynamically view the changes. Parts that are added, canceled, moved,
or reshaped from one revision to another move across the window as the
respective slider is slid from one revision to another.
Also, the parts are color-coded, depending on whether they are added,
canceled, moved, or reshaped.
After you create the graphical history, you can capture it to export or print.

12.3 Activity
In the Working with product structures section, do the following activity:
• Compare two product structures.

12.4 Cloning a product structure

A product structure can be duplicated to create a new structure. This is
referred to as cloning the product structure. This is useful, for example, if a
new product structure is similar to an existing product structure.
• The entire product structure or a selected subassembly can be cloned.
• If you do not have access rights to a substructure in the original structure

being cloned, the substructure cannot be duplicated. Instead, Teamcenter
creates references to the substructure in the clone.
• Cloning a precise structure creates a precise copy; likewise, cloning an

imprecise structure creates an imprecise copy.
• The cloning operation uses deep copy rules, defined by your Teamcenter
administrator, to determine how datasets and attachments are copied.
• The cloning process does not support occurrence effectivity, and any
configuration of the structure with occurrence effectivity does not carry
forward to the clone.
Note
As an alternative to cloning a structure, a product structure template
can be created to use as the basis for new product structures.

12.4.1 Clone a product structure
1. Open the product structure in Structure Manager and configure it, as

needed.
2. Select the top line of the structure or the top line of the assembly you
want to duplicate.
Note
The selected line and everything below it are copied to the clone.
3. Choose File®Duplicate.
The Duplicate dialog box appears.
4. To refine the contents of the clone, select or clear the check box located to
the left of each line in the structure.
• If an item is selected, the item is copied to create a new object.
• If an item is not selected, a reference to the original object is created

in the new structure.
Tip
To select all objects in the structure, select the Duplicate all items
check box.

5. In the Duplicate dialog box, select one or more of the check boxes to define
how the clone is created.
Automatically assign new IDs to all items
Do nothing in the New Item ID by Selection and Default ID Mapping
sections.
Assign new IDs by selecting the items you want to assign them
to
a. Use the Ctrl key and click to select the items in the structure to
which you want to assign IDs.
b. In the New Item ID by Selection section, either select Assign

New IDs to automatically assign IDs, or enter one or more of the
following:
Prefix Adds a prefix to the original ID of each duplicated

item, for example, new_.
Suffix Adds a suffix after the original ID of each
duplicated item, for example _A1.
Replace Replaces a specified substring in the original
item ID with another defined string in the
With
duplicated item ID.
For example, you could replace 00 with 99.
c. Click Apply.
Assign new IDs by using the Default check boxes in the

structure

a. Select the Default check box for each item in the structure to which
you want to assign IDs.
b. In the Default ID Mapping section, either select Assign New IDs to

automatically assign IDs, or enter one or more of the following:
Prefix Adds a prefix to the original ID of each duplicated

item, for example, new_.
Suffix Adds a suffix after the original ID of each
duplicated item, for example _A1.
Replace Replaces a specified substring in the original
item ID with another defined string in the
With
duplicated item ID. For example, you could
replace 00 with 99.
c. Click Apply.
Click OK.
The clone is created according to your selections and saved.
Any items that could not be duplicated, but were created in the clone
as references, are listed in the Duplicate Results dialog box.

12.4.2 Editing a product structure clone
The following rules apply to editing a product structure clone:

• The user who executes the File®Duplicate command to create the clone
owns the product structure clone.
• Any elements of the original structure that were referenced rather than
copied to the clone remain owned by their original owner.
• Access rights and ACL rules on structure lines are not carried forward
from the original structure to the clone.
• You can edit any of the items, item revisions, datasets, and attachments
to which you have permissions in the cloned product structure without
affecting the original structure.

12.5 Activities
In the Working with product structures section, do the following activities:
• Clone a product structure
• Edit a product structure clone.

12.6 Marking up the product structure

You can:
• Mark proposed changes on the product structure or an assembly.
• Save the markup in a persistent workspace object.
• Route the assembly with its markup object for review, and apply the
proposed changes.
• Add more proposed changes and comments to a previously marked-up

structure and save them in the existing markup object.
The markup is related to the BOM view revision (BVR) of the structure. The
BVR may have multiple markups associated with it, but only one markup
may be active; once a markup is applied, it ceases to be active.
A markup change represents a single proposed change to the BVR or one of
its child lines. A markup change always references a markup, and a markup
may include multiple markup changes. The author and the date and time
of each markup change is tracked.
The following proposed changes to the structure can be included in a markup:
• Addition or removal of an occurrence.
• Addition or removal of a substitute for a line.
• Replacement of a line (a change to the item revision when in precise mode

or to the item when in imprecise mode).
• Change to the value of certain occurrence properties, for example, name,

notes, quantity, sequence number, unit of measure, reference designator,
and variant condition.
Note
The markup commands are not available if Teamcenter is tracking
pending edits to the structure in the active pane. Save or cancel any
pending changes before inserting the markup. Editing a structure with
markups may obsolete or remove impacted markups.
You cannot propose changes to an existing markup change. You should
create a general markup with your comments or delete the existing
markup change and create a new one.

12.6.1 Enable markup mode
• To turn on markup mode, choose Tools®Markup®Markup Mode or click

.
Any existing markups to the structure are loaded and displayed.
Note
You can only turn on markup mode if your administrator enabled
this feature.
You cannot turn on markup mode if you have Display Markups for
pending edits enabled by your option (preference) settings. You
must save or cancel those edits first.
You cannot turn markup mode on if you have uncommitted changes.

You must save or cancel those changes first.
• To turn off markup mode, choose Tools®Markup®Markup Mode again

or click .

12.6.2 Create and insert general markup
1. Ensure you are in markup mode.
2. Select the structure line where you want to add the general markup.
3. Choose Tools®Markup®Show Markup View or click .

The BOM Markup View dialog box appears.
4. Click Create General Markup Change next to the Show changes

for this line pane.
Teamcenter adds a new line in the pane.

5. Under Show changes for this line, enter an appropriate comment (for
example, a general description of the proposed change).
Teamcenter saves this general comment to the markup object.

12.6.3 Review and comment on markup
1. Select the top-level assembly that contains the markup and then choose
Tools®Markup®Show Markup View or click .
Note
You can also choose Structure Manager→Window→Show
View→Other→Teamcenter→BOM Markup View to display the
markup view.
2. In Show markup for this level, type a text comment in the Purpose and
Comments box.
Teamcenter saves the comment to the markup object.

12.6.4 Apply markup
You can save (commit to the database) all changes recorded in the markup
that are related to the current line.
This does not affect any changes recorded in markup objects related to the
child lines below it.
1. Select the top-level assembly that contains the markup and choose
Tools®Markup® Apply Markup (this level).
Alternatively, you can right-click the line and choose Apply Markup (this
level).
Teamcenter displays a confirmation dialog box.
2. Click Yes.
Teamcenter applies the changes in the markup to the structure.
Once a markup is applied, it ceases to be active and any future markups
are captured in a new markup object.
A markup cannot be applied more than once, although the results of an
applied markup are visible in the structure.

Alternatively, you can apply a markup at the selected level as follows:

1. Select the top-level assembly that contains the markup and then choose
2. Review the details of the markup, then choose Tools→Markup→Apply

markup (this level).
Teamcenter applies the changes in the markup to the structure.
If the apply action causes full or partial errors, Teamcenter displays a dialog
box that lists the errors and the failed components. You must evaluate the
error descriptions and decide how to fix them.
For example, if the error results from access restrictions, you can ask another
user with suitable access rights to apply the markup or revise the item
revision to obtain access.

12.6.5 Apply all markups
You can save (commit to the database) all changes in the markup that are
related to the current line and also changes in any markups related to the
lines below it.
Caution
Applying multiple markups to a large structure may take a considerable
time.
1. Select the top-level assembly that contains the markup and choose
Tools®Markup®Apply Markup (all levels).
2. Click Yes.
Teamcenter applies the changes in the markups to the structure.
Once a markup is applied, it ceases to be active and any future markups
are captured in a new markup object.
A markup cannot be applied more than once, although an applied markup
remains visible in the structure.

12.6.6 Carrying forward markups
Active markups may be automatically carried forward, depending on how

you copy the structure:
• Baselining or revising
Markups are copied.
• Cloning
Markups are not copied, because closure rules do not apply to a structure
clone.
• Sequencing
Markups are not copied.
• Saving the item or BVR using the Save As command.

Markups are not copied.

12.6.7 Delete markup
1. Select the top-level assembly that contains the markup you want to delete
and choose Tools®Markup®Delete Markup (this level).
Alternatively, right-click the top BOM line and choose Delete Markup
(this level).
2. Click Yes.
Teamcenter deletes the active markup related to the selected line.
When a markup is deleted, all of its markup changes are also deleted.
Alternatively, you can delete a markup at the selected level as follows:

1. Select a line with a related markup and then choose
2. Review the details of the markup, and then choose Delete the Markup
Change .
Teamcenter deletes the active markup related to the selected line.

12.7 Activity
In the Working with product structures section, do the following activity:
• Create and apply markup.

12.8 Summary
• Packing and unpacking structure lines
• Marking up and applying markups to a structure
• Comparing product structures
• Cloning a product structure

Lesson
13 Configuring a product structure

with variants
Purpose
The purpose of this course is to learn how to configure product structures
with classic variants.
Objectives
After you complete this course, you should be able to:
• Describe elements of classic variants.
• View and edit variant data.
• Identify and locate variant data in a product structure.
• Understand the guidelines for the location of variant data.
• Configure a product structure using variants.
Help topics
Additional information for this course can be found in:

Configuring a product structure with variants
13.1 Using classic variants

Variants allow you to:
• Create options (for example, color).
• Create allowed values of those options (for example, red and blue).
• Associate them with an item revision for an assembly or a component in

a BOM.
You usually do this at a top-level BOM, but you can implement variants
anywhere in the structure. You then define a variant condition (for example,
only load IF option color = value red is specified in the variant rule) on
those occurrences that are subject to variant rules.
To configure a particular variant of an assembly or product, set a variant rule
(a group of options and values such as color = red, material = cotton). This
can be stored in the database and retrieved later.
To specify option values or combinations that are not allowed, you can also
set default option values (for example, color = blue) for the variant rule
and create variant rule checks (for example, error if color = green AND
material = cotton). This functionality supports:
• Options that are a mandatory choice or an accessory.
• Components that are configured by more than one option.
• Variant assemblies that are shared between products.
Changes to variant data are controlled by association with item revisions and
BOM view revisions.

13.1.1 Example of using classic variants
In this basic example of how to use variants, a top-level assembly is identified

as Car Model G. It includes a body assembly and two choices of engine (1200
and 1600). You create variant data on the structure to allow configuration
of one or the other engine.
Options and Allowed Values

car type = GLX, GLS, LS
engine = 1200, 1600
gearbox = manual, automatic
fog lights = yes, no
Car Variant Condition

Model G Option Value
A01000
Load IF engine = 1200
Load IF engine = 1600
Body 1200 1600

Assy Engine Engine
A020 E1200 E1600
Creating variant data on the structure

13.2 Creating basic variant data

To create the necessary basic variant data, do the following:
• Define options
Create an engine option on the item Car Model G with allowed values
1200 and 1600. You can later create other necessary options and allowed
values. These options configure components lower in the structure.
• Add variant conditions

Having defined the options that determine different configurations of the
car, you now specify a variant condition on each engine component to
configure it appropriately.
For the 1200 Engine component, you define a condition that loads this
component only if the option engine is set to a value of 1200 (that is, Load
IF engine = 1200). Similarly, define a condition for the 1600 Engine
(that is, Load IF engine = 1600).
You have now created all the static variant data necessary to configure a
variant BOM. These steps are typically performed by design engineers or
a specialized configuration department.
Note
A specific option value does not necessarily relate to a single
component. Variant conditions including a single option value can
cause any number of components at different places in the structure
to be configured or not configured.

13.3 Create options

You can create, modify, rename, remove or delete options for variants.
Define the options of the structure, as follows.
The examples refer to the structure of A01000 - Car Model G.
1. Choose View→Show/Hide Data Panel or click Show/Hide Data Panel

on the toolbar.
Teamcenter opens the data pane.
2. Click the Variants tab and select the BOM line representing the owning
item revision that stores the variant data.
Typically this is the top-level BOM in the structure, in this example,
A01000 - Car Model G.
3. Click the Options branch in the variant data tree.
Teamcenter displays the Option dialog box.

4. In the Option dialog box, enter the necessary options, for example:
• In the Name box, type engine.
• (Optional) In the Description box, enter the engine size.
• Type an allowed value (1200) and press Enter or + (plus) symbol.

Teamcenter displays the allowed value 1200 in the list of allowed
values.
• Type the other allowed value (1600) and press Enter.
5. Click Create to create the option.

A + (plus) symbol appears against the Options branch in the variant data
tree indicating that Teamcenter created the options.
6. Repeat steps 4 and 5 to define the other options on the same assembly,
for example:
Option Allowed values Owning item

car type GLS, GLX, LS A01000 - Car Model G
gearbox automatic, A01000 - Car Model G
manual
fog lights yes, no A01000 - Car Model G

7. Repeat steps 2 through 6 to define the options on other assemblies, for

example, the following body and dashboard assemblies:
A0200 - Body Assy A020 - Dashboard Assy
Option Allowed values Owning item

aerial standard, electric A0200 - Body Assy
radio none, mono, stereo A020 - Dashboard Assy
8. Click Save to save the changes.

A Y appears in the Has Classic Variant Data (HCVD) column for Car
Model G.

13.3.1 Change option values
1. If necessary, choose View→Show/Hide Data Panel or click Show/Hide

Data Panel on the toolbar.
Teamcenter opens the data pane.
2. Click the Variants tab and select the BOM line with the item revision that
owns (stores) the option whose values you want to change. If you are
unsure of the owning item, you can identify this from the Variant Rule
dialog box.
3. Expand the Options branch in the variant data tree.
4. Select the option whose values you want to change.

Teamcenter displays the allowed values in the Option dialog box.
5. In the Option dialog box, do one of the following:

• Enter another allowed value and press the Enter key.
• Select the value and click – (minus button) to remove an allowed value
from an option.
6. Click Modify and Teamcenter modifies the option value.
7. Click Save to save the changes.
Note
Any variant data that references removed option values can no longer be
set as these values are not available for selection. You typically create a
new revision of the item if you need to preserve the historic data.

13.4 Activity
In the Configuring a product structure with variants section, do the following
activity:
• Create variant options.

13.5 Create variant conditions

After you define the options, you must create variant conditions on the
variant components.
1. Ensure you have displayed the Variant Formula property in the structure
tree in Structure Manager.
2. Select the structure line for the option for which you want to create
variant conditions, for example, P060 - Cigar Lighter.
3. Click Variant Condition on the toolbar, choose Edit→Variant

Condition, or double-click the Variant Formula property cell.
Teamcenter displays the Variant Condition dialog box.

The upper part of the dialog box shows the individual clauses that
comprise a variant condition. You can use the buttons to move clauses up
or down, delete a clause, or bracket clauses. The lower part of the dialog
box allows you to define a clause, and you can use the following buttons to
control how a clause is added to the list in the upper area:
• Replace
• Insert
• Append
• Clear
4. Enter the option, for example, car type.

To view available options, click the list of values to display a list of options.
Click the desired option to select a value and automatically populate the
Item box.
Teamcenter lists only options that are loaded in the current window
because their item is loaded or they are used in a variant condition in
the structure.

5. Use the following operators to construct a variant condition:

= Equal to
!= Not equal to
> Greater than
>= Greater than or equal to
< Less than
<= Less than or equal to
Note
If you use >, > = , <, or < = operators, the values of the associated
option must be numeric and only decimal values are permitted.
Not (!) is higher than AND (&); AND (&) higher than OR (|).
That is, A OR B AND A = A OR (B AND A).
6. Enter the value of the option, for example, GLS.
7. Select the list of values to display the allowed values for the radio option
and click the required value.
8. Click Append .
Teamcenter adds the condition to the list.
The Value box is cleared, and it now shows the option’s owning item, for
example, [A01000].
9. Click OR.
Teamcenter constructs a variant condition from the defined clauses joined
by AND and OR operators.

10. Enter the value of another option, for example, GLX, and click Return
or Append .
Teamcenter displays the second clause in the list in the upper part of
the dialog box.
Note
If you only specify one clause (for example, radio = mono) in a
condition, you can set the AND switch or the OR switch.
11. Click OK to create the variant condition on the occurrence.

If a line is packed, Teamcenter applies the condition to each of the packed
occurrences.

13.5.1 Modifying variant conditions
A variant condition is made up of one or more clauses, for example:

aerial = standard
AND aerial = electric
You can modify a condition by inserting, replacing or removing clauses.

13.5.2 Insert a clause before another clause
1. Specify the new clause.
2. Select the clause before which you want to insert the new clause.
3. Click Insert .
Teamcenter inserts the new clause above the selected clause.

13.5.3 Replace or remove a clause
Replacing a clause can be very useful with large compound conditions

containing many clauses because this action does not change the order.
Preserving clause order maintains the algebra and makes scanning for
occurrences with similar conditions easier.
1. Specify the replacement clause.
2. Select the clause to be replaced in the list.
3. Click Replace .
Teamcenter replaces the original clause with the new one.
4. To remove a clause, select the clause and click Delete .

13.5.4 Move a clause
To change the position of a clause within a condition, select the clause and
click Up or Down .
You can move multiple clauses in a single operation by selecting a range of
clauses before clicking the appropriate arrow button.

13.5.5 Group a clause
You can change the grouping of clauses by adding and removing brackets.
Note
Teamcenter supports multiple levels of grouping.
• To add brackets around a range of clauses, select the range of clauses

and click (…).
• To remove brackets from around a range of clauses, select the range of

clauses, including the lines that contain both the opening and closing
brackets, and click (…).

13.6 Setting variant rules

You can set and unset variant rules to manage variability.
You use a variant rule to configure a particular variant of a structure.
• The variant rule contains all the options that are used in the structure
and you can then set required values for applicable options.
• You do not have to specify a value for every option and some options
may remain unset; typically, you set all options to completely configure
a variant structure.
• Some options may appear already set because they have a default value
that Teamcenter automatically sets. Structure Manager shows the item
to which the specified default is attached.
Teamcenter only sets default values if the item to which the default is
attached is loaded.
• If you specify an option value that is disallowed by a variant rule check,

Teamcenter displays an error message that states the problem and the
applicable variant rule.

13.6.1 Set or unset the required variant rule
• To set a variant rule and configure a particular variant of the structure,

click Variant Rule on the toolbar or choose Tools→Variant Rule.
Teamcenter displays the Variant Rule dialog box.
You can sort the options in the dialog box by any of the columns, such as
Option, by clicking the column header.

13.6.1.1 Set a variant rule
1. Click the Value box of the option you want to set (for example, engine).
Teamcenter displays the allowed values for that option.
2. Click the required value (for example, 1200).

Teamcenter displays the selected value in the box and changes the state
of the option from Unset to Set by User.

13.6.1.2 Unset an option value
1. Click the Value box of the option whose value you want to unset.
2. Click a blank value.

Teamcenter clears the value of the option and changes the state of the
option to Unset.
Note
If the option has a default value, it returns to that default, allowing
you to easily return to the default value after you have overridden it.

13.7 Show and hide unconfigured components

• You can show or hide all unconfigured components by choosing
View→Show Unconfigured Variants.
When you choose this command, Teamcenter toggles between showing and
hiding all unconfigured components in the structure.

13.7.1 Show unconfigured components
• You can display all components in the structure by choosing the Show
Unconfigured Variants menu command. You can then use the VOC -
Variant Occ. Config’d column in the properties table to identify the
configured components.
This column shows a Y if the component is configured, is blank if it is not
configured, or ? if Teamcenter cannot determine if it is configured.
The ? indicator appears when a variant condition contains options that

are unset in the variant rule.
Note
Teamcenter displays only options that are loaded. To ensure you see all
used options, you must completely expand the structure.

13.7.2 Hide unconfigured components
• You can hide all unconfigured variant components in the structure display
by choosing the Show Unconfigured Variants command again.
Components marked ? in the VOC column are displayed when
unconfigured components are hidden.

13.8 Activities
In the Configuring a product structure with variants section, do the following
activities:
• Set variant conditions.
• Configure the assembly.

13.9 Summary
• Elements of classic variants
• Viewing and editing classic variant data
• Identifying and locating variant data in a product structure
• The guidelines for the location of variant data
• Configuring a product structure using variants.

Lesson
14 Navigating the relation hierarchy

of an object
Purpose
The purpose of this lesson is to view and navigate the relation hierarchy
of an object.
Objectives
• Navigate the relation hierarchy of an object in the Relation Browser view.
• Review the properties of an object in the Properties view.
• View the 2D preview image of any node in the hierarchy with an

associated 2D preview image.
• Identify the location of the selected node within the overall object relation
hierarchy using the Graph Overview view.
• Perform where-referenced and where-used searches.
Help topics

Navigating the relation hierarchy of an object
14.1 Getting started

The Relation Browser view is part of the Relation Browser perspective. The
Relation Browser view lets you traverse relationship hierarchies in either
direction and supports the inversion of the current selection in the Impact
Analysis view in My Teamcenter.
In conjunction with the Image Preview, Graph Overview, and Properties
views, you use the Relation Browser view to perform basic tasks including:
• Browsing object relations.
• Viewing 2D images.
• Locating an object graphically in a map of relations.
• Examining the properties of a selected object.

14.2 Access Relation Browser

Access the Relation Browser perspective using one of the following methods:
• Click Relation Browser in the navigation pane.
Note
Depending on your configuration, Relation Browser may appear as
primary application, a secondary application, or as an available
application.
• Choose Window®Open Perspective®Relation Browser.
• Select an item in the Folders pane and right-click and choose Send
To®Relation Browser.
Note
In any perspective, you can choose Window®Show View®Relation
Browser or any of the associated Image Preview, Properties, and
Graph Overview views.

14.3 Relation Browser user interface

The Relation Browser perspective displays four views.
1 Relation Browser When you send an item to the Relation Browser

view view, it becomes the root node in that view.
2 Image Preview When a selected node has an associated 2D preview
view image, the preview image is displayed in the Image
Preview view.
3 Graph Overview When you zoom in on a complicated graph in the
view Relation Browser view, the Graph Overview view
shows your display location within the graph. You
can pan around the display in the Graph Overview
view to examine other objects.
4 Properties view When you select an object in the Relation Browser
view, the Properties view displays properties of
the object.

14.4 Using the Relation Browser view

The Relation Browser view displays objects related to selected nodes.
Use the Relation Browser view to traverse relationship hierarchies.

• Double-click a node, or right-click the node and use shortcut menu
commands to browse further related objects.
• Choose a context from the Relation Browser view menu .
Menu command Description

Contexts→Default View structure relations in the Relation
Browser view.
In this context, defined structure relations
display when you show successors or
predecessors.
This is the default view context.


Contexts→Traceability View trace links in the Relation Browser
view.
In this context, defined trace links appear
when you show successors.
• Use the Relation Browser View Menu to select the layout and
orientation.

Hierarchic Layout→ Creates a graph beginning with a top node
Top-to-Bottom and flowing to the bottom.
Hierarchic Layout→ Creates a graph beginning with node at

Right-to-Left the right and flowing to the left.
Hierarchic Layout→ Creates a graph beginning with a node at

Left-to-Right the left and flowing to the right.
Hierarchic Layout→ Creates a graph beginning with a node at

Bottom-to-Top the bottom and flowing to the top.
Hierarchic Layout→ Creates a graph beginning with a top node

Incremental in the upper-left corner and flowing to the
bottom and to the right.
Circular Layout Displays group and tree structures within
a network in a ring and star pattern.
Orthographic Layout Creates compact graphs with no overlaps,
few crossings, and few bends.
It is most appropriate for medium-sized
sparse graphs.
Organic Layout Creates a layout with the nodes spaced as
far away from each other as possible, still
while minimizing this distance.
It is most appropriate for undirected,
complex graphs.
Balloon Layout Creates a layout with a central node and
child nodes extending from this in a radial
fashion.
It is most appropriate for large,
hierarchical structures.
• Use zoom in , zoom out , and fit content buttons to adjust the view.

• You can select any node to browse further related objects one level at
a time.
• If any node has an associated 2D preview image, the preview image can be
displayed as a thumbnail image along with the text string in the Relation
Browser layout and is also displayed in the Image Preview view.
• Right-click a node in the Relation Browser view to access the shortcut

menu commands associated with the object type.
In addition to the standard shortcut commands for the object type, the
Hide/Show Predecessors, Hide/Show Successors, Show Predecessors,
Hide Predecessors, Hide Successors, and Show Successors menu
commands are available in the Relation Browser view.
• Each node in the Relation Browser view can have predecessors and
successors based on the application with which the object is associated.
You can select an object and use the applicable shortcut menu commands
to expand or collapse predecessors and successors.
For example, an application can show predecessors as where-referenced
objects and can show successors by showing default children context.

14.5 Using the Image Preview view

The Image Preview view displays 2D images related to the selected node.
The Image Preview view supports raster images only, such as bitmap
(.bmp), JPEG (.jpg, .jpeg), and TIFF (.tif, .tiff) files. Vector formats are
not supported.

14.6 Using the Graph Overview view

The Graph Overview view identifies the location of the nodes displayed in the
Relation Browser view within the overall relation hierarchy of the root object.
When you select an object in the navigation pane, the Relation Browser view
and the Graph Overview view display the newly selected object as the root
object.
• When you zoom in on a node or area of the graph in the Relation Browser
view, the Graph Overview view shows the location of the area within the
overall hierarchy of the root object.
• Drag the view box in the Graph Overview view to examine other objects
in the Relation Browser view.

14.7 Using the Properties view

The Properties view provides an adaptable listing of property values for
the selected object.
The Properties view menu includes the following commands also available on
the Properties view toolbar:
• Show Categories
Sort and display properties in categories. For example, properties with
assigned values are listed separately from Unassigned properties.
• Show Advanced Properties

Display all properties.
When the properties for a checked-out node appear in the Properties view,
you can edit the values for properties with appropriate permissions. Click
in the property box to begin editing; the Restore Default Values button
is available.

14.8 Where-referenced and where-used searches

In addition to locating your data, you can also perform where-used searches
and where-referenced searches. These searches are available in the Impact
Analysis view in My Teamcenter.
Using these searches, you can determine the effect that modifying an item or
item revision have on assemblies and database objects. You can assess the
impact of engineering changes to the product structure and determine if
changes in one assembly affect other assemblies.
• Where-referenced searches determine where a part or component is

referenced within the Teamcenter database.
The database objects that include a reference to the item or item revision
are found.
• Where-used searches enable you to identify all assemblies that contain, or

use, a particular item or item revision.
All assemblies that contain, or use, an item or item revision are found.

14.8.1 Perform a graphical where-referenced search
1. Select the Impact Analysis view.
2. Select an object in the tree view.

The selected object appears in the Impact Analysis view.
3. Select Referenced from the Where option list, located in the upper left
area of the pane.
4. Select a depth level from the Depth option list.
• One Level
Reports only immediate parent components of the object.
Note
With this level selected, you also have the option to set the Type
and Relation filters.
• All Levels
Reports all parent components of the object, up to the top-level
directory.
• Top Level
Reports only the top-level component.
5. (Optional) If you selected a depth of one level, you can also select a search
filter from the Type and Relation options.
6. Double-click the object in the view pane to activate the search.

The object and the objects by which it is referenced are displayed in

graphical format. The results can be used as the basis for another
where-used or where-referenced search, or they can be formatted and
printed.

14.8.1.1 Perform a where-referenced search using the Referencers Print Wizard
1. Select the Impact Analysis view.
2. Select an object in the tree view.

The selected object appears in the Impact Analysis view.
3. Select Where-Used/Referenced Report from the View menu in the

upper-right of the Impact Analysis view.
The Referencers Print Wizard dialog box appears showing the first step of
the wizard.
4. Select the Where Referenced option.
5. Click Next.
Step 2 of the wizard appears in the dialog box.
6. Select a depth level.

One Level Reports only the immediate parent component of the
object.
All Levels Reports all parent components of the object, up to the
top-level directory.
Top Level Reports only the top-level parent component.
7. Click Next.
Step 3 of the wizard appears in the dialog box.
In this step, the object to be used as the basis of the search is shown along
with report generation options.

8. Select a report generation option:

Generate Presents the where-referenced results in HTML format
HTML/Text in the Print dialog box. From this window, you can
report format the report and either print it or save it to a file.
Generate the Presents the where-referenced results in tree format
structure report in the Report dialog box.
9. Click Yes.
The where-referenced search is generated and the results are displayed.
At this point, you can format, save, or print your report.

14.8.2 Where-used searches
Where-used searches let you identify all the assemblies that contain an item
or item revision.
You can do this to assess the impact of engineering changes to the product
structure or to check if changes in one assembly affect other assemblies.
A where-used search can take into account the revision rule when searching
the product structures, and you can choose one of the following outputs:
• All revisions
Reports all item revisions that have an occurrence of the source item
revision. This search result displays all combinations of usage that can
possibly occur; when a particular set of revision rules is applied not all
paths may be realized.
• Only the revision configured by a selected revision rule

The search result is filtered to include only those revisions configured by
the selected revision rule.
Note
Revision rules and status are explained in later lessons.

14.8.2.1 Perform a where-used search to display a graphical result
1. Select an item or item revision in a component or details view.
2. In My Teamcenter, select the Impact Analysis view.
3. Select Used from the Where option list, located in the upper left of the
pane.
4. Select a rule from the Rule list.

This rule provides parameters to locate the assemblies in which the item
or item revision is used.
For example, if you select the Any Status; Working rule, only the latest
released revision of the assembly is retrieved if it exists. Otherwise, the
latest working revision is retrieved. Released assemblies and earlier
versions of the assembly are not retrieved when this rule is selected.
5. Select one of the following depth levels from the Depth list located in the
bottom-right corner of the window:
• One Level
• All Levels
directory.
• Top Level

6. Double-click the object to start the search.

• If the item or item revision is not part of an assembly that matches
the selected revision rule, the system displays a message to that effect.
• If the item or item revision is part of a configured assembly, the

structure is displayed in graphical format.
The results can be used as a basis for another where-used or

where-referenced search, or they can be formatted and printed.

14.8.2.2 Perform a where-used search to create a text or HTML report
1. Select an item or item revision in the tree or Details table.
2. In My Teamcenter, select the Impact Analysis view.
3. Select Where-Used/Referenced Report from the View menu in the

upper-right of the Impact Analysis view.
4. Select the Where Used option to generate a where-used report and click
Next.
5. Select one of the following Depth level options and click Next:
• One Level
• All Levels
directory.
• Top Level
6. Select a Where-Used rule and click Next.

The Where-Used rule provides parameters to locate the assemblies in
which the item or item revision is used. For example, if you select the
Latest Working rule, only the latest working revision of the assembly is
retrieved. Released assemblies and earlier versions of the assembly are
not retrieved when the Latest Working rule is selected.
7. Select the item type to filter by.

8. Confirm that the required items, item revisions, and revision rules are
shown correctly, and then select a report generation option.
• Generate the HTML/Text report
Presents the where-used results in HTML format in the Print dialog
box. From this dialog box, you can format the report and either print
it or save it to a file.
• Generate the structure report

Presents the where-used results in tree format.
9. Select the item or item revision properties to include in the report and
click Next.
The system displays the item or item revision and selected revision rule
that is the basis of the search, together with report generation options.
Note
The preselected properties are those used when you last ran the
wizard. You can change them as necessary.
10. Click Yes.

Teamcenter runs the where-used search and displays the results. At this
point, you can format, save, and print your report.
• (Optional) Change the print format.

o HTML
Displays results in the default print format.
o HTML Table
Displays results in tabular format. This improves readability for
large reports.
o Text Format
Displays results as text.

• (Optional) Format the report by performing the following steps:
a. Click Set Result Format in the upper-right corner of the Print

dialog box.
Teamcenter displays the Print Format dialog box. The formatting
options vary depending on the type of object selected and whether
you are printing in HTML, HTML table, or text format.
b. Modify the result format.
c. Click Update.
d. Close the Print Format dialog box.
11. To save or print the report, complete the appropriate process.
• Print a text or HTML file.
a. Click Print .
b. Define the printer to which the file will be sent.

You can accept the default printer that is displayed in the Name
box or select a different printer from the list.
c. Click OK to print the file and exit the dialog box.
d. Click Close to exit the Print dialog box.
• Save output to an HTML or text file.
a. Click Save (located in the lower-right corner of the Print dialog

box).
The Save dialog box appears.
b. Navigate to the directory location where you want to save the file.
c. Type the name of the file, including the .htm, .html, or .txt
extension, in the File name box.
d. Click Save to save the file and exit the dialog box.
e. Click Close to exit the Print dialog box.

14.9 Activities
In the Navigating the relation hierarchy of an object section, do the following
activities:
• View and navigate a relation hierarchy.
• Perform where-used and where-referenced searches.

14.10 Summary
• Navigating the relation hierarchy of an object in the Relation Browser
view
• Reviewing the properties of an object in the Properties view
• Viewing the 2D preview image of any node in the hierarchy with an

associated 2D preview image
• Identifying the location of the selected node within the overall object
relation hierarchy using the Graph Overview view
• Performing where-referenced and where-used searches

Lesson
15 Classifying and using

standard data
Purpose
The purpose of this lesson is to learn how to create and find classification
objects (ICOs) to use as standard data in product structures.
Objectives
• Navigate the classification hierarchy.
• Find classification objects using various criteria.
• Add instances of classifications objects to a product structure.
Help topics
• Classification Guide

Classifying and using standard data
15.1 Getting started

Classification of your company’s product data (standard parts, technology
data, and manufacturing equipment) saves time by making component data
easier to find and retrieve and reduces costs by allowing you to reuse existing
parts and consolidate or eliminate duplicate or outdated parts. Classification
is used to create and maintain a hierarchical classification structure based
on the attribute values of your workspace objects.
You can use Classification to:
• Add classification objects (ICOs) to the classification hierarchy.
• Classify workspace objects.
• Find classification objects.
• Modify the attribute values of Classification objects.
• Delete classification objects from the classification hierarchy.
You can classify objects using the rich or thin client interface.
Prerequisites Your classification administrator must have already

created a classification hierarchy in the Classification
Administration application before you can use
Classification.
Start
Classification Click Classification in the navigation pane.
If you are not licensed to run the application, you see
an error message and you are not able to perform any
application functions.

15.1.1 Basic concepts
Classification enables creation of a digital library of product definition data.

• The classification hierarchy uses groups and classes to categorize a
company’s data.
• Hierarchical class definitions include attributes and attribute values used

to identify an object within a group of objects.
For example, the nut height and thread diameter attributes can be
used to distinguish particular nuts within a group of nuts.
• The hierarchy and its components, groups, and classes are defined and
maintained by an application administrator using the Classification
Administration application.
• Instances of Teamcenter classification objects (ICOs) are created by

associating the objects with a specific class and assigning applicable
values to attributes defined for that class.
• Attributes can be used as search criteria to locate ICOs to reuse in other

applications and perspectives.

15.2 Basic tasks using Classification

Classification is used to create and maintain a hierarchical classification
structure based on the attribute values of Teamcenter objects.
Use Classification to:
• Classify Teamcenter objects to create instances of classification objects
(ICOs).
• Search the classification hierarchy to find ICOs based on attributes and

attribute values.
• Copy and reuse ICOs in different applications and perspectives, such as

Structure Manager.
• View data associated with your workspace object. View many types of
data, including GIF, TIFF, PNG, HTML, and text documents in the
classification viewers.
• Modify the attribute values of ICOs.
• Delete ICOs from the classification hierarchy.

15.3 Classification interface
1 Classification hierarchy Categorizes your company’s data using

groups and classes.
2 Object ID search box Searches the entire classification hierarchy
for the specified object ID or part of the
object ID.
3 Properties form Displays the values of attributes associated
with a specific classification ICO.
4 Class viewer Shows an image associated with a class.
5 Instance viewer Shows documents or images associated
with the classified workspace object (for
example, item or item revision) of the ICO.
This includes a multitude of data types,
such as GIF or JPEG images, JT image files,
HTML files, Microsoft Office documents, or
NX part files.

15.3.1 Classification panes

Pane Description
Properties Displays the Properties pane used to view, define, and
edit the values of attributes associated with a specific
Classification ICO. The class and instance viewers are
also located in this pane.
To enlarge the image, click the maximize button .
By default, images are shown. To prevent this, click the
Panel Menu button and clear Show Image.
In the instance image window, JT assemblies are
shown by default, if one exists in the classified object.
To deactivate this, click the Panel Menu button and
clear Show Assemblies.
The active measurement unit is displayed in the title
bar of the attribute search criteria pane.
Table Displays the properties of ICOs in tabular format.
Multiple Instance Displays Classification data associated with one of
multiple ICOs of a single workspace object.
(ICO)

15.3.2 Classification symbols

Note
Group and class symbols can be customized; therefore, the default
symbols displayed in the following table may not represent those used
at your site.
Symbol Description
Displays the root or anchor of the Classification system.
There is one root per database.
Displays a group which is a collection of related classes.
Displays an abstract class that is used to combine common
attributes for use in storage classes. Classification ICOs
cannot be stored in abstract classes.
Displays a storage class in which Classification instances
can be saved. Storage classes can be positioned anywhere
in the hierarchy, including the leaf node position.
Displays an SML class that is used in the legacy SML
hierarchy structure to store subclasses and other classes.
ICOs cannot be stored in SML classes.
Note
If possible, do not use SML classes. Use abstract and
storage classes.
Displays an SML subclass that contains the subset of
attributes corresponding to an SML class.
Displays an attribute value that is mandatory; it requires
an entry to save the classification object.
Displays an attribute value that a Classification user
cannot change. It is protected by the Classification
administrator.
Displays an attribute value that requires an entry to
save the classification object, but the Classification user
cannot provide the entry. It is set by the Classification
administrator using a default value.
Displays an attribute value that is automatically computed
based on custom logic assigned in the Business Modeler
IDE application.

Symbol Description
Requires an attribute value that is within a specific range.
Displays an attribute value that falls outside of an

allowable range.
Displays a key-LOV value that is deprecated and should
not be used to set an attribute value when classifying
an object. However, you can use deprecated key-LOV
values when searching to find objects that were previously
classified with this attribute value.

15.4 Classification hierarchy structure

Classification uses groups, classes, views, and classification objects (ICOs) to
structure the classification hierarchy and classify Teamcenter objects.
• Groups are the highest level of a classification hierarchy. Groups
categorize a particular arrangement of related classes.
A group labeled fasteners could be established to organize all the
fasteners used by your company.
Groups can also be nested to include other groups. For example, if the
fasteners are standard parts, you could create a group called standard
parts and associate the fasteners group as a subgroup of standard
parts.
There is no limit to the level to which groups can be nested.
• Classes are the next level of a classification hierarchy. Classes are

a compilation and arrangement of attributes related to objects in a
particular group.
Abstract classes are typically used to store objects that share a major set
of characteristics (attributes). The attributes assigned to the abstract
class are then inherited by any and all child classes. Abstract classes can
have other abstract classes as well as storage classes as children.
Storage classes are defined by a combination of the inherited attributes of
the parent classes along with attributes that are specific to the storage
class. Storage classes can hold parent, child, and leaf node positions in
the hierarchy.
• Views display and provide access to class attributes on a user or group

basis. View objects are defined by your Classification administrator.
• Classification objects (ICOs) are representations of Teamcenter objects

extended with classification data. ICOs assign values to the attributes
defined for the associated class.
Note
The system automatically generates an object ID to identify a new
ICO.
The ICO object ID corresponds to the Teamcenter item ID on which
it is based and cannot be modified.

15.4.1 Displaying the classification hierarchy
The classification hierarchy tree provides a graphical display of the

classification hierarchy structure. The tree structure of nested classes
provides an overview of all classification classes contained in the database.
When you first open Classification, the hierarchy on the left is still closed.
You can only see the root node.
1. Double-click the root node of the hierarchy.
2. Move down the hierarchy by clicking the plus sign in front of the name of
the class you want to open.

15.4.2 Displaying a subset of the hierarchy
You can select any point in the hierarchy and set that node as the root node,
blending out all of the node’s parent classes and groups. This can be useful
when viewing a complex hierarchy.
You can:
• Store nodes for subsequent selection as root.
• Display a node as a temporary root.

15.4.3 Set a node as root
1. In the title bar of the hierarchy pane, click to display the root node
selection. By default, this list contains only Classification Root.
2. Select the node that you designate as the new root node in your
classification tree.
Teamcenter displays the name and symbol of the new root class in the
title bar.
3. (Optional) Display the full tree again by selecting Classification Root

from the options list.

15.4.4 Display a node as temporary root
1. Right-click the class in the hierarchy that you want as the temporary
hierarchy root node and choose Set Root Node.
Teamcenter displays this class as the root node but does not add the class
name to the root node selection list.
2. (Optional) Return to viewing the complete tree by selecting Classification

Root from the root node selection list.

15.4.5 Display information in the Properties pane
You can only see information in the Properties pane after you select a class
in the hierarchy.
To select a class in a hierarchy, you can do one of the following:
• Double-click a storage class in the hierarchy.
• Right-click a class from the hierarchy and choose Select from the shortcut
menu.
Note
The selected class name appears in bold text. This is the only way to
verify which class in the hierarchy is selected.

15.4.6 Preview available attribute values
You can activate a filter that allows you to preview those attribute values
available in the currently selected class. This is especially useful when you
are searching as you can select an existing value and search for it.
1. Select a class in the classification hierarchy.

Teamcenter displays the attributes in the Properties pane.
2. Click the Autofilter button .

Teamcenter displays the List of Values dialog box containing a list of all
the attribute values stored for this attribute.
The attribute preview indicates whether the value is stored as a metric

or nonmetric unit.
• Select a value and click OK.

Teamcenter closes the List of Values dialog box and populates the
attribute value box with the selected value.
• Click Clear.
Teamcenter closes the List of Values dialog box and removes any value
that was in the attribute value box.
• Click Cancel.
Teamcenter closes the List of Values dialog box without making any
changes to the attribute value box.

15.4.7 Change the active measurement system
When displaying ICOs in the Properties pane (view mode), you can change
the measurement system that is displayed.
• Click the Active unit button and select the measurement system.
Note
You can do this only if your administrator has specified that the class
can contain both metric and nonmetric values.

15.4.8 Viewing the tree graphically
You can use the graphical browser to navigate through the classification
hierarchy.
• To open the graphical browser, click the Graphical Browser tab.
• To modify the graphic size, move the slider at the right of the browser
pane to the right to enlarge the graphic and to the left to make it smaller.
• You can switch back and forth between the tree structure and the
graphical browser.
• The class that is currently selected in the graphical browser is

automatically selected in the tree hierarchy and vise versa.

15.5 Classifying Teamcenter objects

By classifying Teamcenter objects, products, parts, and components can be
categorized according to their common characteristics. This classification
allows you to search for parts independent of the location in the product
structure.
Classification objects (ICOs) are created based on the attributes assigned to
the storage class. Therefore, you must first determine the appropriate class
for the object being classified, in accordance with your company’s established
classification standards.
Note
Siemens PLM Software recommends classifying item and item revision
objects only. Classification of datasets, forms, and folders is not
recommended. If, however, you are planning to perform appearance
searches in Structure Manager, you must classify items, not item
revisions.

15.5.1 Create a classification object (ICO)

Note
Special permissions are required to create an ICO.
1. Use one of the following methods to choose the object to be classified (item
or item revision):
• Select the item or item revision in the tree structure or properties
table of another application, such as My Teamcenter, and drop it on
the Classification button in the navigation pane.
The Classification application appears and a message asks if you want
to create classification information.
• Select the item or item revision in the tree structure or properties

table of another application, such as My Teamcenter, and copy it to the
clipboard. Open Classification, click the Clipboard button, and choose
the object from the Contents menu.
A message asks if you want to create the classification information
for this object.
• Right-click the item or item revision in the tree structure or Properties

table of another application, such as My Teamcenter, and choose Send
To from the shortcut menu. Choose Classification from the list of
applications displayed on the Send To menu.
The Classification application displays a message asking if you want
to create classification information.
2. Click OK in the Create Classification Object dialog box.

The dialog box closes and the object ID is displayed in the Properties pane.
3. Browse the hierarchy tree to locate the storage class that best matches
the characteristics of the object being classified.
4. Right-click the storage class and choose Select. You can also double-click
the storage class to display the attributes.
The attributes associated with the selected subclass are displayed in the
Properties pane.
5. Type values for the attributes. If the class can accept both metric and
nonmetric units of measurement, you can switch between these using the
Active Unit list. Classification converts the values where required.
6. Click Save on the toolbar to create the ICO and save it to the database.

15.5.2 Classifying an object multiple times
A single object can be classified multiple times in different classes. Attributes

that are common across the classes, and their values, are synchronized across
the multiple ICOs.
For example, Part 1 is classified in Class 1, Class 2, and Class 3. All three
classes contain the vendor attribute. If the value for vendor is changed in
the ICO stored in Class 1, the values are also updated in the ICOs stored in
Class 2 and Class 3.
Note
When multiple ICOs exist for an object, tabs corresponding to each of
the ICOs, appear at the bottom of the Properties pane.

15.5.3 Create multiple classification instances of an object
1. Display the classification object that you want to classify in the Properties
pane.
2. Click Add a new Instance to the Current object .
3. Browse the hierarchy tree to locate the storage class that best matches
the characteristics of the object being classified.
4. Right-click the storage class and choose Select or double-click the

storage class.
The attributes associated with the selected subclass appear in the
Properties pane.
5. Click Save on the toolbar to create the ICO and save it to the database.

15.5.4 Revising classified items or item revisions
If an item must be revised due to a change in form, fit, or function, the

classification of the new revision is as follows.
Classified item Classified item revision

Item ® ICO ICO
Item with revision/A Item revision/A ® ICO A
Item with revision/B Item revision/B ® ICO B
• If the item is classified, there is no effect on the classification information

for this item. All revisions reference the item’s ICO.
• If the item revision is classified, Teamcenter creates a copy of the revision’s

ICO and uses this to classify the new revision. If you change attributes
in the new ICO, this has no effect on the classification information for
the original revision.

15.6 Modifying attribute values

It may be necessary to modify the attribute values of an ICO. For example,
when an object is classified early in the design process, additional attribute
information may become available later.
Using the Classification edit function, you can modify the attribute values
of a specific ICO.
Note
ICOs maintain the protection settings of the Teamcenter object from
which they are created. Therefore, you must have write access to the
object to modify a classification ICO.

15.6.1 Modify attribute values of a specific ICO
1. In the Properties pane, display the ICO to be modified.
2. Click Edit on the toolbar to activate the Properties pane.
3. Add, delete, or modify the attribute values of the ICO.

If an attribute value is not available for modification, your administrator
may have set a fixed default value; or, if you use key-LOVs, a value may
be deprecated.
Note
If you do not want to save your changes, click Cancel. This clears
any changes you have made to the ICO in the current editing
session. Previously saved data is restored.
4. Click Save on the toolbar to save the modifications to the database.

15.7 Finding an ICO

Use the following general method to find a classification object (ICO) in the
Teamcenter database:
1. Search the classification hierarchy.
The search can be based on one or a combination of the following:
• Object ID
If you know at least a portion of the object ID of an ICO, you can use
the object ID search feature. An object ID search encompasses the
entire classification hierarchy and cannot be limited to the contents
of a particular class or subclass.
• Object type
• Groups or classes
• Attribute values
A revision rule can also be applied to the search. This limits the search
results to include only those revisions you require.
2. Navigate the search results.
3. Select the ICO you want to view, reuse, or modify.

15.7.1 Classification search buttons
There are two search buttons in the Classification user interface:

• Click the Search button to the right of the Object ID text box to search
the entire classification hierarchy.
• Click the Search button at the bottom of the Properties pane

to search within a selected class. This type of search can include any
search refining features, such as object ID, attribute value, or search by
type.

15.7.2 Search by object ID
1. Click the Properties pane located to the right of the hierarchy tree.
2. Type the object ID for the search in the Object ID box located at the top of
the Properties pane.
Note
Classification uses the standard wildcard characters defined for your
site. These wildcard characters can be used in any search text box.
3. (Optional) Select an object type to narrow the search to ICOs of that type.
4. (Optional) Apply a revision rule to narrow the search to ICOs with that
revision rule setting.
Note
If a specific revision is typed in the Object ID box, the revision rule
setting is ignored.
5. Click Search to the right of the Object ID box.

• The ICOs found by the object ID search are listed in alphanumeric
order.
• The first ICO found appears in the Properties pane.
• The total number of ICOs found is displayed in the Search Results

box.
6. Navigate through the search results to locate and select the desired ICO.
Note
When navigating through the ICOs, the class and subclass to which
the ICO belongs are highlighted in the classification hierarchy tree.
7. (Optional) To perform subsequent searches, click Clear to remove the

values from the Properties pane. Repeat this procedure beginning with
step 2.

15.7.3 Search by object type
1. In the classification tree, expand the desired class and select it by:
• Double-clicking if it is a leaf node.
• Right-clicking and choosing Select if it is not a leaf node.
The class names are highlighted in the tree.
2. Type a component ID, a component class ID, or attribute values.
3. Click Drag .
4. Select an object type.
Click To
Search among all classification instances. This is the default
search method.
Search among all classification instances that classify a
workspace object.
Search among all classification instances that do not classify a
workspace object.
Search among all classification instances that classify an item.
Search among all classification instances that classify an item
revision.
Search among all classification instances that classify a process.
Search among all classification instances that classify a process
revision.
Note
If a specific revision is typed in the Object ID box, the revision rule
setting is ignored.
6. Click Search at the bottom of the Properties pane to list all

matching instances within the class.
The total number of instances that match the search criteria is displayed
at the bottom of the pane.

15.7.4 Apply a revision rule to the search
1. In the the Properties pane, click Revision rule link.

Note
The link shows Click to add a revision rule or the name of a revision
rule, if a rule is set as the default.
The View/Set Current Revision Rule dialog box appears listing the
existing revision rules.
2. Select a revision rule and click OK.
3. Click beside the Revision rule link.

A list with configuration options appears.
4. Select one of the following options.
Configuration options Description

Use revision rule Enables or disables the currently selected
revision rule for the search.
Save as default Saves the currently selected revision rule
as the default rule for this application. The
default revision rule is directly selected
and enabled for the search the next time
you launch the application.
Restore default Selects and enables the saved default
revision rule. The Use Revision Rule
menu command is also automatically
selected.

15.8 Searching based on a group or class

To search for a classification object based on a class, you must find and select
the class in which to search. The following methods can be used to find the
group or class in which to search:
• Navigate through the classification hierarchy manually, expanding the
groups and classes until you find the desired class.
• Use the quick search feature.
• Use the Search Class dialog box.

15.8.1 Use the Search Class dialog box
1. Click Find Class located beneath the hierarchy tree.

The Search Class dialog box appears.
Note
To move the dialog box, double-click the title bar and drag it to
another location.
2. Define the search criteria by performing the following steps:

a. Select a property to search from the list at the upper-left corner of
the dialog box.
Note
You can use the Name, Class ID, and alias properties to search
for groups and classes. When searching by attribute, the results
include the class in which the attribute is defined and any
subclasses in which the attribute is used.
b. Type search text corresponding to the selected property.

Note
Wildcard characters can be used in the search string.
3. Click Search in the upper-right corner of the dialog box or press Enter
to start the search.
The search results appear in the message area of the dialog box, sorted
in the same order as the hierarchy tree display.
4. Double-click an item in the results list to view it in the classification

hierarchy.
The hierarchy tree expands to display the selected group, class, or
subclass.
5. Click the left and right arrow keys beneath the class hierarchy tree
to move through the search results to locate the desired class
or group.

6. Right-click the class you want to search in the hierarchy tree and choose
Select.
Tip
If the class or subclass you want to search is a leaf node (lowest level
node) in the hierarchy, double-click the node to select it instead of
using the shortcut menu.
Attributes associated with the selected class appear in the Properties pane
as search criteria. Associated images, if any, appear in the viewer panes.

15.8.2 Use the quick search feature
1. In the search box located beneath the hierarchy tree, type text
corresponding to the name of the group or class that you want to locate.
You can also search by ID by typing id=xxx in the text box, where xxx
is the class ID.
The search text can be the exact name or ID of the group or class you are
looking for, a class alias name, or you can use character strings combined
with wildcard characters.
2. Press Enter to start the search.

The hierarchy tree expands to display the first object in the hierarchy that
matches the search criteria. The path of the group, class, or subclass is
indicated in bold text. If multiple objects are found, the arrow buttons at
the bottom of the hierarchy tree are enabled.
3. Click the left-arrow and right-arrow buttons to display the

matching objects, one at a time. This highlights the classes found in the
hierarchy tree. The right-arrow button moves down the hierarchy tree,
and the left-arrow key moves up the tree.
Note
If you prefer to view a list of the results, you can display the Search
Class dialog box by clicking the magnifying glass button located
beneath the hierarchy tree.
4. Right-click the class you want to search in the hierarchy tree and choose
Select.
Tip
If the class or subclass you want to search is a leaf node (lowest level
node) in the hierarchy, double-click the node to select it instead of
using right-click select.
Attributes associated with the selected class appear in the Properties pane
as search criteria. Associated images, if any, appear in the view panes.

15.8.3 Search all ICOs in a selected class
1. Select the class you want to search in the hierarchy tree.
3. (Optional) Click Search Scope at the bottom of the Properties pane to

set the scope of the search.
• Set the scope to Hierarchy to search within the selected class and
all related child classes.
Note
This is the default.
• Set the scope to Class to search only within the selected class.
4. (Optional) Narrow the search based on unit of measure setting. Click

Unit System at the bottom of the Properties pane and select from the
following.
Click To
Search only in metric classes.
Search only in nonmetric classes.
Search in both metric or nonmetric classes.
5. Click Search .
The total number of ICOs that match the search criteria appears at the
bottom of the Properties pane.

search criteria values from the Properties pane and repeat this procedure.

15.8.4 Search for ICOs in a selected class by attribute value
1. Select the class you want to search in the hierarchy tree.
3. Type the value to search on in the box corresponding to the attribute

or attributes you want to search.
Tip
Wildcard characters and relational operators can be used in the
search string for attributes.
Note
If the attribute you want to search is not listed, one of the following
reasons may apply:
• It is a reference attribute.
• It may already have a default value assigned in Classification

Administration.
• It may be encrypted in the database.
4. (Optional) Click Search Scope at the bottom of the Properties pane, to

set the scope of the search.
5. (Optional) Click Unit System at the bottom of the Properties pane to

narrow the search based on unit of measure setting.
6. Click Search .
The total number of ICOs that match the search criteria appears at the
bottom of the Properties pane.

search criteria values from the Properties pane and repeat this procedure.

15.9 View Classification search results

After you perform a search, you can view the search results in the Properties
pane or the Table pane.
1. Click the Properties or Table pane.
2. Navigate to the desired ICO.

• In the Properties pane, use the navigation arrows. The system shows
all attributes and the attribute values for each ICO.
• In the Table pane, you can:

o Select the ICO by clicking it.
o Double-click the ICO.
o Select multiple ICOs.
The system switches to the Properties pane and shows all attributes
and attribute values for the selected ICO.

15.9.1 Use the Search Results box to navigate to a specific ICO
1. Type the relative position of the ICO in the Search Results box .
2. Press Enter.

15.9.2 Viewing search results in the Properties pane
When viewing an ICO in the Properties pane, the placement of the ICO
within the hierarchy is reflected in the hierarchy tree. Two modes are used
for updating the classification hierarchy when viewing the search results:
• Click the View in class stored button to display the class in which
the item is stored.
• Click the View in class searched button to display the class you
selected as the basis for the search.
If multiple ICOs exist for an object, tabs corresponding to each ICO appear at
the bottom of the pane. The red exclamation point indicates the master ICO
that matches the search criteria. The related ICOs may or may not be stored
in the class or subclass in which the search originated.
Note
The View Mode feature does not apply to viewing multiple ICOs of
a single object.

15.9.3 Viewing the active unit of measure attribute
The active unit of measurement attribute value for an ICO appears in the
title bar of the Properties pane. In the Table pane, the attribute value
appears at the beginning of the row for each ICO.
The following symbols are used to identify the active unit of measurement
attribute value for an ICO.
Symbol Description
The ICO is currently displayed and stored in a metric system of
measurement.
The ICO is currently displayed and stored in a nonmetric system
of measurement.
The ICO is currently displayed in metric but was originally stored
in a nonmetric measurement system.
The ICO is currently displayed in a nonmetric measurement
system but was originally stored in a metric system.

15.9.4 Viewing search results in the Table pane
The object ID and attributes of each ICO in the search results can be viewed
collectively using the Table pane.
View search results in the Table pane using the following techniques:
• Click to load the next page of found ICOs into the table.
The ICOs are appended to those currently displayed.
• Click to load all matches into the table.
• Use the scroll bars to move through the found ICOs.
• (Optional) Sort the table data; double-click the column header

corresponding to the property to switch between ascending and descending
sort order.
• Double-click the ICO in the table to view it.

The system opens this ICO in the Properties pane and opens the tree
to the position of this ICO in the tree, highlighting the class containing
the ICO.

15.10 Displaying associated data in the viewers

Images and other types of file-based data associated with a specific class or
ICO appear in the Properties pane viewers. These viewers assist you in
better identifying the ICOs with which to work.
• Class viewer
Shows an image associated with the selected class in the upper-right
portion of the Properties pane.
• Instance viewer
Shows documents or images associated with the classified workspace
object (for example, item or item revision) of the ICO. The instance viewer
is located in the lower-right portion of the Properties pane.

15.11 Copying classification objects and classified BOM lines

Use Copy classified Teamcenter object to Clipboard on the Classification
toolbar to copy the classified BOM objects (not the ICOs) from the
Classification Table pane and paste them into other perspectives, such as
into Structure Manager.
1. In Classification, perform a search to find the classified objects to reuse.
2. Display the search results in the Classification Table pane.
3. In the Table pane, select the row or rows for the objects you want to copy.
4. On the Classification toolbar, click Copy classified Teamcenter object

to Clipboard .
The object is copied to the Clipboard.

Note
Copying subsequent objects overwrites the contents of the clipboard.
On the Classification toolbar, use Append classified Teamcenter
object to the Clipboard to copy more objects to the clipboard.
5. Open the desired perspective, such as Structure Manager, and paste the
data using standard paste commands.
Note
Data displayed on the Classification Table pane can also be copied then
pasted into Microsoft Word or Excel.

15.12 Activities
In the Classifying and using standard data section, do the following activities:
• Search all ICOs in a selected class.
• Search the classification hierarchy for a class.
• Add classified objects to a product structure.

15.13 Summary
• Navigating the classification hierarchy
• Finding a classification object using various criteria
• Adding instances of classified objects to a product structure

Lesson
16 Viewing and working with

visualization files
Purpose
The purpose of this lesson is to learn the basics of the visualization tools
available in the Teamcenter embedded viewer.
Objectives
• Locate and view visualization data.
• Set view preferences.
• Work with parts in the embedded viewer.
• Adjust performance settings.
Help topics
• Getting Started with Product Visualization

Viewing and working with visualization files
16.1 Locate and view visualization data

Teamcenter supports many 2D and 3D file formats for viewing. The 2D and
3D visualization data exists as dataset objects within an item revision.
• The DirectModel dataset symbol is used to identify a .jt file, the

standard file type for 3D visualization data.
• The DrawingSheet dataset symbol is used to identify a standard

file type for 2D visualization data.
You can open 2D and 3D datasets and view the associated 2D image or 3D
model in the Viewer view. The options and tools available to you in the Viewer
view depend on which type of file you open.

16.2 3D navigation
When you open a 3D model in the Viewer view, the 3D navigation, examine
mode, is activated by default. In examine mode, you can control how you
view the model in the following ways:
Rotate Navigate
Pan Fit All
Zoom Area Seek
Rotate The camera moves around the target, the target remains
stationary, and the magnification does not change. After
clicking Rotate, it remains active until you click Pan
or Navigate.
Click Rotate and drag in the middle of the viewing
window. As you move the mouse, the model appears to
tumble in 3D space.
Click Rotate and drag near the edge of the viewing
window. As you move the mouse, the model appears to
rotate in the plane of the viewing window.
Alternative method
Press and hold the Ctrl and Shift keys while panning
or zooming.
Pan The model appears to move in the plane of the viewing
window. When you pan, you move both the camera
and target relative to the model. The viewing direction
remains perpendicular to the viewing plane. The
camera moves, the target moves, and magnification does
not change.
Pan remains active until you change to Rotate or Zoom.
Alternative method
There are two ways you can pan at any time without
choosing the Pan command:
• Press and hold the Ctrl a key while rotating or
zooming.
• If you have a three-button mouse, you can press and

hold down the middle button to pan.

Navigate Dynamically change magnification. The model appears

to get bigger or smaller. The camera moves closer to or
further from the target; the target does not move; and
the magnification changes.
Navigate remains active until you change to Rotate or
Pan.
Click and drag in the viewing window. Move the mouse
pointer vertically in the viewing window to zoom in and
out. The model appears to move closer and further away.
Move the cursor up to simulate moving away and down
to simulate moving closer.
Alternative method
There are two ways you can pan at any time without
choosing the Pan command:
• Press and hold the Shift a key while rotating or
panning.
• If you have a three-button mouse, you can press

and hold down both the left and middle buttons to
navigate.
Fit All Change magnification so all visible parts fit in the
viewing window. The view may also pan so all visible
parts appear in the middle of the viewing window. The
camera moves closer or further from the target; the
target may move, and the magnification changes.
Seek Select a point to be the new target. Seek is a variation
of Pan. The view is centered on the selected point. The
camera moves, the target moves, and the magnification
does not change.
Note
This is a temporary center of rotation that gets
reset when Fit All is selected.
Zoom Area Zoom to a specific area of the model.
Click and drag to draw a rectangle around the area in
the viewing window. The camera moves, the target
moves, and the magnification changes.

16.3 Activity
In the Viewing and working with visualization files section, do the following
activity:
• Navigate the Viewer view.

16.4 Set view preferences
With view preferences, you can control four viewing characteristics:

• General features, such as model appearance and window background
color.
• Display features, such as model display and feature line options.
• Grid features, such as grid lines, emphasis lines, and labels. This is not
covered in this lesson.
• Selection features, such as selection style, color, and preview.

16.4.1 View preferences – General
This tab is divided into two sections:

• Model
o Two-sided lighting adds light to both faces (or sides) of polygons in
the viewing window.
o View interpolation causes one view to slide to the next when change
views using snapshots. This also causes your initial view of a model
to gradually zoom to fit the viewing window.
o Draw trihedron displays the graphic showing the current directional

orientation of your view.
• Window
o Controls the appearance of the background of the viewing window.

16.4.2 View preferences – Display
This tab is divided into three sections:

• Model Tessellation lines
o Controls the appearance of
models in the viewing window.
o Shaded displays geometry as

a solid model.
o Tessellation Lines shows the

edges of the polygons that form
the surfaces of the model. You
can change the color of the
tessellation lines.
o Feature Lines shows edges or Brep

outlines of the parts. You can
change the color of the feature
lines.
o Hidden Lines settings also

apply when you turn off
Shaded mode for individual
parts.
• Feature Line Options

o Controls the appearance of
feature lines. Feature lines
only appear when Feature
Lines display mode is active.
o With silhouette lines adds

lines that are not surface edges
but are needed to complete the
outline of a part. The lines
representing the sides of a
cylinder are silhouette lines.
o Use B-rep if available

uses original boundary
representation data to
generate feature lines if
available.

o Feature Angle sets the

maximum angle between two
triangles for inclusion as a
feature line. Enter a number
between 0 and 180. The default
value is 18.
• See-Thru/Transparency
o Controls the transparency
color.

16.4.3 View preferences – Selection
This tab is divided into two sections:

• Selection
o Style controls how parts appear when selected.
o Material Color changes the part color, or Bounding Box encloses parts.
o Color is the color of the part or bounding box.
• Selection Preview
o You can display highlights, geometric types, and construction lines.

16.5 Activity
activity:
• Adjust view preferences.

16.6 Work with parts in the embedded viewer

In the embedded viewer, you can:
• Select parts through various methods.
• Adjust performance settings to control image quality and memory use.

16.6.1 Embedded viewer – Select parts

Before you can perform tasks with
individual parts of your 3D model, you
must select the parts. You can:
• Select a part from the viewing
window.
• Select a part from the assembly

list.
• Select multiple parts.
• Select an assembly.
• Select an entire model.
• Deselect a part.
• Deselect all parts.

16.6.2 Embedded viewer – Set selection preferences
• When you select a part, its appearance changes in the viewing window to
show you that the part is selected.
• Selection preference settings control how the part appearance changes.
• To set your preferences: right-click in the background of the viewing

window, choose Preferences, and then click the Selection tab.
• There are two selection options:

o Change the material color of the part.
o Display a bounding box around the selected part.

16.7 Activity
activity:
• Select parts and assemblies.

16.8 Adjust performance settings

A basic understanding of performance settings is necessary to balance image
quality and navigation speed.
• Model size, model complexity, computer speed, RAM, and graphic card
capabilities are factors that affect performance.
• There are three predefined combinations of performance settings. You can

edit the preset performance settings and add two more.

16.8.1 Use predefined performance settings
The three predefined combinations of performance settings are:

• Part Investigation
Provides the highest level of image quality. Typically used for viewing
models at the individual part level.
• Assembly Investigation
Provides a slightly lower level of image quality but a higher level of system
performance. Typically used for viewing models at the assembly level.
• Model Exploration
Provides a lower level of image quality while trying to maximize system
performance. Typically used for viewing models when your not interested
in smaller component parts.

16.8.2 Set performance settings
1. Right-click the background of the viewing window.
2. Choose Performance.
The Performance dialog box appears.
3. Click Toolbar.
Choose the setting that gives you the best balance between image quality
and navigation speed. You may use different setting with different models.

16.9 Activity
activity:
• Adjust performance settings.

16.10 Summary
• Locating and viewing visualization data
• Setting view preferences
• Working with parts in the embedded viewer
• Adjusting performance settings

Lesson
17 Initiating a workflow
Purpose
The purpose of this lesson is to use Workflow Viewer to initiate a workflow
process and assign a workflow task.
Objectives
• Initiate a workflow process and assign a workflow task.
• Review workflow tasks.
• Track process status.
Help topics
• Workflow Viewer Guide

Initiating a workflow
17.1 Overview of workflow

Workflow consists of:
• The automation of the flow of business processes to accomplish a defined
objective.
• Documents, information, and tasks passing between participants during

the completion of a particular process.
• Processes that can have any number of tasks arranged in a serial or

parallel progression.
• Processes that use defined tasks to automatically notify selected

individuals requesting work signoff.

17.2 Workflow process

Workflow processes are created based on a process template, which functions
as a blueprint of the workflow process. A specific process is defined by placing
workflow and/or change management tasks in the order they should be
performed. Process templates are created using Workflow Designer.
1. Check in data you want to submit to the workflow.
Note
Not all workflow definitions require data to be checked in.
2. Initiate the workflow process.
3. Select a signoff team.
4. Perform the reviews and signoffs to complete the workflow.

17.2.1 Workflow process branching
Workflow processes contain a series of tasks that step the user through a
process.
Branching capabilities allow for different paths through the process based on:
• User signoff
• Condition processing
• Error processing
The example process shows serial, parallel, and failure path branching. If the
Incorporate Markups task is signed off as Unable to Complete, the failure
path takes the process to the Problem Resolution task.

17.3 Check in data before starting a workflow

Depending on how a workflow is defined, the data to be submitted to workflow
may need to be checked in.
To remove the checked-out status of data when you are finished working on
it, you can use either Check-In or Cancel Check-Out.

17.4 Initiate a workflow process
1. Select the object to submit to the workflow.
2. Choose File®New®Workflow Process.

The New Process Dialog appears.
Note
The selected object is placed in the Targets folder in the task
attachments.
3. Complete the New Process Dialog.
4. Click OK to initiate the workflow process.
This results in the selected data being submitted to the workflow, as

indicated by the process symbol.
Note
Assignments are delivered to the assignees My Worklist (inbox).

17.4.1 Complete the New Process Dialog
When completing the New Process Dialog, consider the following:

• Process Name
By default, the process name is based on the object you selected. However,
you can change it. The process name should be short and descriptive.
• Description
This is optional and can be used to describe the process.
• Process Template
Select the applicable workflow process for the workflow you want to
initiate.
Note
Process templates are assigned based on your company practices.
They are created in Workflow Designer by your application
administrator.

17.4.2 Attachments
An attachment is an object associated with a workflow process. There are two

kinds of attachments, target objects and reference objects.
Target objects are:
• Released through a process.
• Assigned a release status when the process is complete.

Note
Typically, a release status is assigned to the target object at the
completion of a process. Release status assignment depends on
business requirements and the process template definition.
Reference objects:
• Provide information to those performing tasks.
• Are not assigned a status change when the process completes.

17.4.3 Process Template tab
You can review the definition of the selected process template.

To determine if it is the correct workflow for the process you want to initiate,
click the Process Template tab to view:
• A list of the tasks in the workflow process.
• A description of the process and information on how it is defined in

Workflow Designer.
Note
When a task in the workflow is selected, the Description box
includes instructions on how to complete the task.
• A graphical representation of the workflow process.

17.4.4 Assign All Tasks tab
To review and assign the task assignments for the selected process template,
click the Assign All Tasks tab.

17.5 Creating workflow subprocesses
Subprocesses are child workflow processes of a parent workflow process.

You can create subprocesses while performing tasks from your worklist.
When created in this manner, parent workflow processes are dependent on
subprocesses; they cannot complete until the subprocess completes.
A typical scenario is one in which you receive a task in your worklist that is
dependent upon the completion of an additional workflow process. You decide
to create a workflow subprocess to track the work which must be completed
before you can complete the task in the parent workflow.
Generally, any user can create a workflow subprocess from a task within their
worklist. This functionality is not limited to privileged users.
When you create a workflow subprocess from an in-process task in your
worklist, you create a dependency between the selected task in the parent
process and the newly created subprocess.

17.5.1 Create a workflow subprocess

You can create workflow subprocesses while performing tasks from your
worklist or Workflow Viewer.
1. In the My Worklist tree, under the Inbox→Tasks to Perform folder, select
the task for which you want to create a subprocess.
The task you select becomes dependent upon the workflow subprocess. It
cannot complete until the workflow subprocess completes.
2. Right-click the task and choose Create New Workflow Sub-Process.

The New Sub-Process dialog box appears.
3. In the New Sub-Process dialog box. do the following:
• Type a name for the process in the Sub-Process Name box.
• Type a description to identify the process in the Description box.
• (Optional) Select a Process Template Filter option.

o To include process templates currently under construction in
the Process Template list, select the Show Under Construction
Templates check box.
o To display all available process templates in the Process Template

list, select All.

o To display only those process templates assigned to your group in

the Process Template list, select Assigned.
o Click the Process Template list to view available workflow process

templates and make a selection.
Your selection determines the workflow to be initiated as a
workflow subprocess.
o (Optional) Select the Inherit Targets check box if you want the
new workflow subprocess to include all the targets of the parent
workflow process.
o (Optional) Click the Attachments tab to view or assign target and

reference attachments.
o (Optional) Click the Process Template tab to view the process

template selected as the basis of the new process.
o (Optional) Assign all tasks in the process.
o Click OK to initiate the process.

Note
Click Cancel at any time to cancel the operation without
initiating a process.

17.6 Activity
In the Initiating a workflow section, do the following activity:
• Initiate a workflow process and assign a task.

17.7 Review workflow tasks
After you initiate the workflow process, you can access your assignments from
My Worklist (inbox) and view the process in the Viewer view.
• To view task instructions, select the task within the Tasks to Perform or
Tasks to Track folder and select Task View in the Viewer view.
• To view a list of tasks and assignments in the workflow process and a

graphic of the states in the workflow process, select Process View.

17.7.1 Viewing process information
The Process View in the Viewer view activates a graphical display of the
overall process as it moves through the different stages of release.
• Do Task
Includes a dialog box that allows the user to set a check box to indicate
when the task is complete. When the task has a failure path defined, an
Unable to Complete check box appears in the dialog box.
• Review Task
A task template that includes select-signoff-team and perform-signoffs
subtasks.
Each of these subtasks has its own dialog box for executing its respective
processes.
• Acknowledge Task
Similar to a Review Task, a task template that includes
select-signoff-team and perform-signoffs subtasks.

Each of these subtasks has its own dialog box for executing its respective
processes.
In the figure, the Initiate Workflow task is a Do Task and Design Review is
a Review Task.
Note
Place your cursor over the user to see who is responsible for that task.

17.7.2 Tracking process status
Graphic symbols indicate the state of each node in the workflow process.
• A flag symbol indicates the task has successfully completed.
• A green traffic light symbol denotes the active task in the process.
Note
A red traffic light symbol indicates work on the task is suspended.
• A document with a red X symbol indicates the failure conditions are

met.
• An hourglass symbol indicates the task has not been started, it is

pending.

17.8 Activity
In the Initiating a workflow section, do the following activity:
• Review workflow tasks.

17.9 Summary
• Initiating a workflow process and assigning a task
• Reviewing workflow tasks
• Tracking process status

Lesson
18 Managing workflow task

assignments
Purpose
The purpose of this lesson is to assign workflow review tasks and manage
your assigned tasks in a workflow process.
Objectives
• Select signoff teams for tasks.
• Use resource pools.
• Perform review and acknowledge tasks.
• Delegate a task.
• Set your out of office status.
• Assign a workflow surrogate.
• Track release states.
• Review the audit log.
Help topics
• Workflow Viewer Guide

Managing workflow task assignments
18.1 Select signoff teams

Review tasks and acknowledge tasks require a signoff team. Signoff teams are
assigned during a workflow or by the administrator for each process template.
Signoff teams can be assigned at different times and by different methods
during a workflow process.
• When tasks become active (green traffic light symbol )
The responsible party receives a task to assign the signoff team for the
step before it can proceed.
• At workflow creation using the New Process Dialog and the Assign All
Tasks pane
The workflow initiator assigns signoff teams using assignment lists or
individually.
• When the task is pending (hourglass symbol )

During any previous active task, the responsible party assigns signoff
teams from the Workflow Viewer or the inbox Process View using the
Actions®Perform command.
• Automatically, as defined by the process template

Workflow administrators can define signoff teams in the process template
using workflow handlers.

18.1.1 Select a signoff team during workflow creation
1. In the New Process Dialog box, click the Assign All Tasks tab.
2. In the left pane, select a profile or Users under the task to assign.
In the right pane, the Organization pane appears.

3. In the Organization pane, select the group, role, or user to perform the
signoff.
4. Click Add to assign the selected group, role, or user.

The group, role, or user appears in the selected area under the task.
5. Repeat group, role, or user selection until all members are added to the
task and the Profile signoffs met note appears.
6. Click Apply.

18.1.2 Select a signoff team for active tasks
1. In My Worklist, in the Tasks to Perform folder, select the

select–signoff–team task.
2. Click the Viewer tab.

The Viewer view appears with the Task View selected.

signoff.

The group, role, or user appears in the selected area under Signoff Team.

6. Repeat group, role, or user selection until all required members are added
to the signoff team and the Profile signoffs met note appears.
7. Click Apply.

18.1.3 Use process assignment lists
Signoff teams can also be assigned using a process assignment list.

• Choose Tools®Process Assignment List®Create/Edit to access the
Create /Edit Assignment List dialog box.
A process assignment list:

• Is related to a process template.
• Is used to assign individuals to all workflow tasks in the process from

a single dialog box.
• Can be shared among site or group members.

Shared assignment lists are created by the Teamcenter site or group
administrator.
• Can be created for personal use and not available to others.

Personal assignment lists are created by the user.

18.1.4 Select a signoff team for pending tasks
1. In the Process View, select the select–signoff–team task under a

pending task.
2. Choose Actions®Perform.
The Select Signoff Team dialog box appears.
signoff.

The group, role, or user appears in the selected area under Signoff Team.
6. Repeat group, role, or user selection until all members have been added to
the signoff team and the Profile signoffs met note appears.
7. Click Apply, and then click Close.

18.1.5 Select a signoff team automatically
Workflow administrators can automatically assign signoff team members to

a task. In this example, members of the high performance group with the
Manufacturing Engineer role receive the signoff assignment.

18.2 Assign the signoff to a resource pool

A resource pool is a group, role, or role in a group that can be assigned tasks
the same way an individual user is assigned tasks.
Select a group or role in the Organization tab and click Add to assign the
signoff to a resource pool.
In this example, the resource pool is made up of any member of the high
performance group with the Manager role.
During the review process, users in the resource pool can subscribe to the
resource pool using the Tools®Resource Pool Subscription command and
then claim or delegate the signoff task.

18.3 Types of signoff tasks

Two types of signoff tasks
Review tasks:
Require that you examine
task attachments, such as a
document, and record your
signoff decision as:
• Approve
• Reject
• No Decision
Acknowledge tasks:
Require that you acknowledge
task attachments and record
your signoff decision as:
• Acknowledge
• Not Acknowledged

18.4 Activity
In the Managing workflow task assignments section, do the following activity:
• Select the signoff team.

18.5 Perform a signoff task

Once the designer submits data for review or acknowledgement, the
perform-signoffs task is distributed to the appropriate users’ Worklist
(inbox).
1. Click My Worklist (inbox).
2. Expand the Tasks to Perform folder.
3. Select the perform-signoffs task.

Note
Make sure your group and role settings are correct before you
perform a signoff.
4. Work in the perform-signoffs Task View pane to record your signoff

decision.

18.5.1 Using the perform-signoffs Task View

The perform-signoffs Task View pane includes key information about the task
and links to dialog boxes where you can view or modify the task information.
• Responsible Party
The person assigned to complete the task. (The task can be reassigned.)
• For Review
Click the Attachments link to view the target and reference objects
attached to the task.
• Instructions
Review Instructions to see what you need to do to complete the task.
• User-Group/Role
Specifies the group and role in which the responsible party is a member.
(The group/role setting can be modified.)
• Decision
Click the link in the Decision column to access the Signoff Decision
dialog box. This is where you record your signoff decision.

The decision options differ depending on whether the signoff task is a

review task or an acknowledge task.
Note
Recording a comment associated with the decision is optional.
However, application administrators can write rules to require
a comment.

18.5.2 Approve a review signoff task
Selecting Approve performs a signoff on the review task.

• If you are the only one assigned to approve, or the last one required to
approve, the process moves to the next step.
• If you are one of a number of people assigned to approve, and the others
have not yet approved, the perform-signoff task moves to your Tasks
to Track folder.

18.5.3 Reject a review signoff task
Selecting Reject does not approve the signoff on the task. If the quorum
requires all signoff tasks to be approved, selecting Reject stops the process.
Depending on how the process is designed, selecting Reject does one of the
following:
• Removes the perform-signoff task from your Worklist (inbox) and returns
the process to a prior task or a designated failure path.
• Moves your perform-signoff task to your Tasks to Track folder but keeps
the current review task the active process task.

18.5.4 Make no decision on a review signoff task
Selecting No Decision does not approve nor reject the signoff on the review
task.
If the quorum requires all signoff tasks to be approved, selecting No Decision
stops the process.
• Comments can be added when No Decision is selected.

18.5.5 Acknowledge a signoff task
Select Acknowledged to acknowledge the task attachments for an

acknowledge signoff task.
• If you are the only one assigned to acknowledge, or the last one required
to acknowledge, the process moves to the next step.
• If you are one of a number of people assigned to acknowledge, and the

others have not yet acknowledged, the perform-signoff task moves to
your Tasks to Track folder.

18.5.6 Do not acknowledge a signoff task
Select Not Acknowledged to indicate you do not acknowledge the attachments

for an acknowledge signoff task. If the quorum requires all signoff tasks to be
acknowledged, selecting Not Acknowledged stops the process.
Depending on how the process is designed, selecting Not Acknowledged does
one of the following:
• Removes the perform-signoff task from your Worklist (inbox) and returns
the process to a prior task or a designated failure path.
• Moves your perform-signoff task to your Tasks to Track folder but retains
the current acknowledge task as the active process task.

18.6 Using resource pools

You can use resource pools to balance workflow tasks between groups of users.
• Resource pools let you balance workflow task assignments. They allow
open-ended assignments, permitting any user to accept responsibility for
a task that is assigned to a group, role, or a role in a group.
• All users can subscribe to resource pool inboxes; however, they can only
perform tasks if they are valid members of the group or are assigned
the appropriate role. Your administrator can also subscribe users to
resource pools.
• Tasks assigned to a resource pool appear in the Tasks to Perform folder

and the Tasks to Track folder of the appropriate resource pool inbox. Any
member of the resource pool can then accept responsibility and perform
the task.

18.6.1 Subscribe to a resource pool
1. In your My Worklist (inbox), choose Tools®Resource Pool Subscription.

The Resource Pool Subscription dialog box appears.
2. Select the applicable group and role for the resource pool.
3. Click Add to subscribe to the resource pool for the selected group and role.
A folder for the resource pool is added to your My Worklist (inbox).
4. Click Cancel.

18.6.2 Delegate tasks from a resource pool
You can delegate tasks from a resource pool to your personal My Worklist
(inbox) and vice versa. Delegate tasks:
• When it will take an extended period of time to perform the task.
• To avoid duplication of effort.

18.6.3 Delegate a signoff task
You can delegate a signoff task from a resource pool to yourself.

1. In your My Worklist (inbox), expand the folder for the applicable resource
pool to which you subscribed.
2. Expand the Tasks to Perform folder in the resource pool folder.
3. Select the perform-signoffs task.
4. Select Task View in the Viewer view.
5. Click the link to the assigned resource pool in the User-Group/Role

column of the Task View window.
The Delegate Signoff dialog box appears.
6. Select your user ID from the User list.
7. Click OK.
• The task is removed from the resource pool folder and placed in the
Tasks to Perform folder in your My Worklist (inbox).
• The responsibility of the task is transferred to you as the delegated

user.

18.7 Use Out of Office Assistant

Use Out of Office Assistant to forward your tasks to another user’s inbox
while you are out of the office.
1. Click My Worklist (inbox).
2. Choose Tools→Out of Office Assistant.
3. Set the Out of Office Dates absence from date and time.
4. Set the Out of Office Dates absence to date and time.
5. Set New Task Recipient by selecting the Group, Role, and User name of
the person to whom the assigned tasks are forwarded.
Note
Users currently assigned out of office status cannot be selected as
a recipient.
6. Click OK.

18.8 Creating a workflow surrogate user

You can create a list of surrogate users who are authorized to perform your
workflow tasks. This is useful when you are out of the office or otherwise
unable to perform assigned tasks.
A link to your inbox appears in the inbox of the surrogate user. The surrogate
user can:
• Claim responsibility for a task or designate themselves as the active
surrogate user.
• The active surrogate user can perform any of the tasks in your inbox
provided their group and role matches the group and role profile for the
task.
To create a surrogate user, in your My Worklist (inbox), choose

Tools®Workflow Surrogate.

18.9 Release states

Teamcenter data used in this training can be in one of three states:
• Statused
Data stored with item revisions that have obtained this state are
considered production data. The data is generally in a write-protected
mode meaning it cannot be changed unless a new item revision is created.
• In-Process
The object is currently in a workflow process.
• (Empty value)
Default state. If no other state is defined for the data, the system displays
an empty value. If the item revision has no value for the release state, it
is said to be working data.
Note
Companies can supply or modify their own state symbols, and define
what each symbol represents.

18.9.1 Status types
When working with the status of data, consider the following:

• A status type (or release status) can be set on almost any data upon
completion of a workflow process.
• When a status type is set for an object, the object is said to have been
statused.
• The Release Status and Date Released are included in the object’s
properties.
• Status types are defined based on your company practices and created
by your site administrator.

18.10 Reviewing workflow by viewing the process history

The Process History view displays the Workflow process of the business object
selected in the Home, My Worklist, or Search Results view in My Teamcenter.
• If there is no audit data for the business object, the view displays a No
process history data available for selected object. message.
• If the selected object has passed through more than one workflow process,
you can choose which process to display from the list to the right of the tab.
In the Process History view, you can review the progress of a workflow and
do the following:
• Determine the progress of an object in a workflow and who has
responsibility for the object.
• Review comments by other workflow participants.
• Verify that the appropriate participants completed the required reviews.
• Debug a workflow that proceeded down an unexpected path.
• Identify workflows that require attention to continue processing.
• Review user activity to verify the appropriate users signed off.

18.11 View workflow audit logs in My Teamcenter

You can view the workflow audit logs in the Summary view in the Audit Logs
tab in My Teamcenter.
1. Select an item revision, workflow object or process template.
2. Click the Summary tab, and then click the Audit Logs tab.
Workflow Logs for the selected object appears.
You can also export audit logs to Microsoft Excel or CSV.

18.11.1 Process reports

The following audit reports are available when you choose the
Tools®Reports®Report Builder Reports menu command in My Teamcenter:
• Audit - Workflow Attachment Report
Displays all attachment object details for the specified workflow process.
• Audit - Workflow Detailed Report

Displays all actions and their statuses for the specified workflow process.
• Audit - Workflow Signoff Report

Displays the signoff results and comments for the specified object in
a workflow process.
• Audit - Workflow Summary Report

Displays the start, complete, approve, rejected, release status, demote,
promote, fail, and update actions for the specified workflow process.
• WF - Filtered Audit
Displays the start, complete, approve, and rejected actions for the specified
workflow process. For more detailed information about this set of actions,
including group and role of the performer and assignee information, use
Audit -Workflow Summary Report.
• WF - Items In Process
Displays the items currently in a workflow process and where they are in
their respective processes.
• WF - Objects In Process
Displays the objects currently in a workflow process and where they are in
their respective processes.
• WF - Signoffs
Displays the signoff results and comments for the specified object in a
workflow process. For more detailed information, use Audit - Workflow
Signoff Report.
• WF - Unfiltered Audit
Displays all actions and their statuses for the specified workflow process.
For more detailed information about this set of actions, including group
and role of the performer and assignee information, use Audit - Workflow
Detailed Report.

18.12 Activities
In the Managing workflow task assignments section, do the following
activities:
• Perform the design review.
• Perform the standards review.
• Perform the manufacturing review.
• Perform the manager acknowledge review.

18.13 Summary
• Selecting signoff teams for tasks
• Using resource pools
• Performing review and acknowledging tasks
• Delegating a task
• Setting your out of office status
• Assigning a workflow surrogate
• Tracking release states
• Reviewing the audit log

Lesson
19 Managing Teamcenter data

through the Microsoft Office
integration
Purpose
The purpose of this lesson is to manage Teamcenter objects using Microsoft
Office and live Excel. You manage workflow tasks and perform sign-offs using
Microsoft Outlook.
Objectives
• Manage Teamcenter data in real time with Microsoft Office applications.
• Update BOM properties in real time with live Excel.
• Submit a document to a workflow, manage tasks, and sign off tasks with
Microsoft Office.
Help topics
• Client for Microsoft Office Guide
• Extensions for Microsoft Office Guide

Managing Teamcenter data through the Microsoft Office integration
19.1 Introduction
You can manage Teamcenter workspace objects in real time with Teamcenter
Client for Microsoft Office.
• Client for Office gives you access to Teamcenter directly through Office
applications.
It adds a custom Teamcenter tab to the ribbon in Word, Outlook, Excel,
and PowerPoint.
• Teamcenter Extensions for Microsoft Office provides synchronous access

to Teamcenter workspace objects through Microsoft Excel and Word. With
the live Excel and live Word features, Extensions for Office gives Excel
and Word direct connectivity to the Teamcenter server.
Teamcenter Microsoft Excel
Client for Office is independent of the Teamcenter rich client. You can work
in Office while the rich client is running. Or, you can work solely through
Office without running the rich client.
The first time you start an Office application after the Client for Office
installation, the Microsoft Office Customization Installer displays a message
stating that Siemens PLM Software is the publisher and asking if you want
to install the customization.
• Click Install to install the Teamcenter add-in for the application.
Your administrator can configure Microsoft Office Excel for live Excel.
Additional configuration is required to run reports in live Excel.
You do not need to configure Client for Office, but your administrator can
configure single sign-on (SSO) to avoid multiple logons.

19.2 Manage data with Microsoft Office

Client for Office gives you direct access to Office documents that are stored in
Teamcenter. You can work in Client for Office without running Teamcenter.
Use Client for Office to work with Office documents of the following types:
• For Word, .docx and .doc
• For Excel, .xlsx and .xls
• For PowerPoint, .pptx and .ppt
• For Outlook, .msgx and .msg.

19.2.1 Client for Office interface
Client for Office incorporates a Teamcenter tab on the ribbon of the Word,
Excel, and PowerPoint application windows.
On the Office ribbon, the Teamcenter tab contains button groups, each with
their own set of options.
Microsoft Word ribbon
Note
The Microsoft PowerPoint ribbon is the same as the Microsoft Word
ribbon, except Markup is not available.
Microsoft Excel ribbon
Note
The Import button group is displayed only in Excel. This feature
is designed primarily for Teamcenter Systems Engineering and
Requirements Management. Markup is not available in Excel.

19.2.2 Basic tasks for Client for Office
Use Client for Office to perform the following Teamcenter tasks:

• Save and edit Office documents in Teamcenter.
• Browse to and search for Office documents and other Teamcenter objects.
• Create folders, items, and item revisions in Teamcenter.

Note
You can create items that use cascading and interdependent lists
of values (LOVs), if the Teamcenter administrator configures such
item types in the Business Modeler IDE.
• Create and edit Office datasets in Teamcenter.
• Insert Teamcenter object property values, search results, pictures, JT

files, and hyperlinks in Office documents.
• Check out and check in Office documents in Teamcenter.
• Delete Teamcenter objects.
• Submit Office documents to Teamcenter workflows.
• Perform Teamcenter sign-offs.
• Import data from Excel to create and modify structures and objects in
Teamcenter.
• Review Word documents using the Teamcenter Markup Manager view

to work with markup comments.

19.2.3 Browse Teamcenter Home folder
1. Click Navigate ®Browse 1. Click the Navigate button to

see the navigation pane with your
to see the navigation pane Teamcenter Home folder.
with your Teamcenter Home
folder. All the expanded content appears
in the navigation pane.
2. Click a folder to expand the
contents. The top of the
navigation pane contains the
path to the current folder.
Note
The first time you access Teamcenter, you must enter your Teamcenter
user ID and password.

19.2.4 Create folders, items, and datasets
There are several ways to create new content in Teamcenter through

Microsoft Office.
• Create new folders to organize

objects in your Home folder.
• Create new item type objects,

like items, documents, or parts
using the New Item wizard.
• Save new local dataset objects,

like Word documents or Excel
spreadsheets, to Teamcenter.
Select the location to save the
dataset.
• Save changes to objects

stored in Teamcenter. You are
asked to check in with the save.

• Create new revisions of

objects in Teamcenter.

19.2.5 Find objects
To find Teamcenter workspace objects, you can search in two ways:

1. Perform a simple search in the Navigation view.
2. Perform an advanced search in the Advanced Search view.
Results appear in a separate tab.

19.2.6 Open datasets
To open Teamcenter datasets, you can open in two ways:

• Open an Office dataset from the shortcut menu.
o Right-click the dataset and choose Open and Check-Out File or Open
File (read-only).
The file opens in a new Office window.
• Open an Office dataset from the Teamcenter Open dialog box.

1. Click Open in the Data Management toolbar.
The Teamcenter Open dialog box appears.
2. Select a file location in the Home tree.

The file appears in the top right of the window.

3. Choose Open and Check-Out or Open File (read-only).
The file opens in a new Office window.

19.2.7 Update datasets

As in Teamcenter, you must check
out a document before making

updates.
The Teamcenter Check-In/Out
view shows the available options.
You can check in the object, cancel
the checkout, or transfer the
checkout when you are finished
with the updates.
Upon checkout, the object is
reserved so only you can make
updates.
A checkout symbol appears to

the right of the checked-out dataset
and its parent item revision.

19.2.8 Insert Teamcenter objects into an Office document
1. Select a location in the dataset.
2. Right-click the object and choose Insert.
In this Word document, part revision properties are inserted into a table and
a direct model JT file is inserted as a graphic.
Note
JT2Go is required to insert a JT file as embedded.

19.2.9 Insert Teamcenter markups for Word documents
Client for Office provides markup features for all stages of a Word document
review cycle. On the Teamcenter tab of the Office ribbon, the Markup button
displays the Teamcenter Markup Manager view.

Note
• Client for Office markup features work with Word’s built-in markup
features, which are available on the Review tab of the Office ribbon.
• The document displays Teamcenter Markup Manager comments

according to your Tracking settings on the Review tab.
Using the Teamcenter Markup Manager view, Teamcenter users can perform
tasks such as:
• Prepare a document for review.
• Add and delete comments.
• Modify comment text and

comment types.
• View comments.
• Revise content according to

reviewer comments.
Caution
Siemens PLM Software recommends against setting Protect Document
restrictions on the Word Review tab.

19.2.10 Managing your Teamcenter settings in Microsoft Office
The Current Settings options allow you to manage your session, preferences,
locale, and logging on and off Teamcenter.
If you are logged onto

Teamcenter from Office,
the Logout option appears.
If you have not logged onto
Teamcenter, the Login
option appears.
The Session option

displays your current
group and role and allows
you to change your group
and role for the session.
The Basic Teamcenter Preferences option allows you to control how objects
are inserted into documents, properties displayed during an insert, and
available file types.

19.2.11 Open and update datasets
You can open and update a dataset from the rich client using Client for Office.
Additionally, you can edit a dataset from the thin client using Client for Office.
The Teamcenter tab appears and the buttons are active.

• Save new Microsoft Office datasets in Teamcenter

To save documents from Microsoft Office in Teamcenter as a new dataset,
click Save As®Dataset on the on the Teamcenter tab, not Save in
Microsoft Office.

• Save modifications to existing Microsoft Office datasets in

Teamcenter
Note
You must first log on to Teamcenter from Microsoft Office.
o If you open a document in Microsoft Office and want to save changes
in Teamcenter, click Save on the on the Teamcenter tab or Save

in Microsoft Office.
o If you open a document from Teamcenter in Microsoft Office and
want to save changes in Teamcenter, click Save on the on the

Teamcenter tab or Save in Microsoft Office.
o If you want to save an existing Microsoft Office document as a

new dataset in Teamcenter, click Save As®Dataset on the on the
Teamcenter tab to save the document as a new dataset in Teamcenter
with a new name.

19.3 Activities
In the Managing Teamcenter data through the Microsoft Office integration
section, do the following activities:
• Import a new Word document to Teamcenter.
• Insert Teamcenter data into a Word document.

19.4 Manage workflow with Microsoft Office

In Client for Office, you manage your workflow by doing the following:
• Initiate a workflow process for a Teamcenter object.
• Synchronize your Teamcenter workflow tasks with your Outlook tasks.
• Browse your Teamcenter inbox.
• Perform workflow tasks.
• Reassign and delegate tasks.
• Select a sign-off team.
• Send an Outlook message containing Teamcenter task data.
• Perform Teamcenter sign-offs.
• View all reviewer comments for a workflow task.

19.4.1 Initiate a workflow process
You can initiate a workflow from any Office application with the Teamcenter
ribbon.
1. Right-click the object

in the Folder View, the
Navigation view, or the
Search Results view and
choose New Workflow
Process.
If the object is open in the
active Office application,
click New Workflow
Process on the
Teamcenter ribbon.
The process name defaults to

the object name.
2. Select a process template
from the list.
3. Click OK to initiate the

process.

19.4.2 Browse workflow task assignments
You can view workflow assignments from any Office application with the
Teamcenter ribbon.
• The tasks appear in the users

inbox.
The workflow symbol

appears to the right of the
object submitted to the
workflow process.
• Click My Worklist on the

Teamcenter ribbon to see your
Inbox.
Then, click your Inbox to view
Tasks to Perform.

19.4.3 Synchronize your workflow tasks with Outlook
The main window in Outlook contains a Teamcenter custom tab that allows
you to access to Teamcenter workflow features.
1. Click Synchronize
Teamcenter Tasks to
display workflow tasks
in Outlook.
The workflow task
appears in your
Outlook Tasks and
To-Do Bar.
Note
Unless SSO is
enabled, you are
required to log on to
Teamcenter.
2. Click Navigate
®Browse
to open the Navigation
in Outlook.
3. Expand the My
Worklist and then your
Inbox to see Tasks to
Perform and Tasks to
Track.

19.4.4 Perform a workflow task
1. To perform a task from Outlook in the Navigation – Folder View:
• Right-click the task and

choose View/Perform Task.
The Perform Workflow Task
view appears.
2. Complete the assignment.
• View all reviewer sign-offs

and comments.
• Open the target object.
• Select the target object link

to open the object in the thin
client.
• Select the sign-off team for

select-signoff-team task.
• Select the sign-off action for

Review and Do tasks.
• Reassign or delegate the

task.

19.5 Activities
section, do the following activities:
• Initiate a workflow process from Office.
• Complete the review tasks.

19.6 Manage BOM with live Excel

Use Extensions for Office to edit properties of Teamcenter workspace objects
directly from Microsoft Office Excel and Word.
Create live Excel files by exporting object data from the following Teamcenter
rich client applications:
• Systems Engineering
• Structure Manager
• Multi-Structure Manager
• My Teamcenter (the Details view and the navigation pane)
Teamcenter Microsoft Excel

19.6.1 Basic concepts of live Excel
Use Teamcenter live Excel to edit properties of Teamcenter structure objects

directly from Microsoft Office Excel.
• Live Excel spreadsheets contain exported property data for selected
objects in a structure.
• You can edit the property values in a spreadsheet to change the data for
the corresponding objects.
You can export object data to live Excel in the following output modes:
• Interactive mode
o While the Teamcenter rich client is running, the spreadsheet data is
synchronized with the object data in the structure.
o Changes are applied dynamically between the spreadsheet and the

structure in both directions.
• Bulk mode
Multiple live Excel edits are committed to Teamcenter at the same time,
reducing overhead in updating a large amount of data.
• Offline mode
o An offline spreadsheet is stored outside of Teamcenter, for example,
on a local or shared drive.
o Changes in the spreadsheet are independent of the rich client and are
accumulated for later application to the structure.

19.6.2 Basic tasks for live Excel

The live Excel export file contains a row for each selected object and a
column for each specified property. The file gives you synchronous access to
Teamcenter for the following tasks:
• Change property cell values and copy or move values to other cells.
When you leave the updated cell, the properties are updated in the
database.
• Save export files locally to use for other live Excel sessions.
You can open these files to start sessions with or without running the
Teamcenter rich client.
• Navigate to a workspace object from a live Excel file.

The object is highlighted in the Teamcenter rich client.
Note
You may need to log on to Teamcenter.
• Run live Excel reports on Teamcenter objects based on predefined

templates that you select.
You can edit report cells to change the corresponding property values in
Teamcenter without running the rich client or thin client.
The template determines:
o Which Teamcenter objects are exported to the report.
o Which properties are included for the objects.
Reports that are saved locally cannot be reconnected to Teamcenter when

they are reopened. Reports cannot be generated from other live Excel
files. You must export object data to a new live Excel file.
Only persistent properties of workspace objects can be changed in
Teamcenter. Properties of run-time objects such as BOM lines cannot be
modified from the report.
Note
Siemens PLM Software recommends that the Teamcenter
administrator define Excel templates to export only workspace
objects, such as items and item revisions, and their persistent
properties.
Live Excel report generation must be configured before you can run
reports.

19.6.3 Export BOM to live Excel
You can generate new live Excel files by exporting object data from
Teamcenter Structure Manager.
1. Select the object or structure to export.
2. Choose Tools→Export→Objects to Excel.
3. Under Output, select Live integration with Excel (Interactive).
You can optionally select the Check out objects before export check box.
• The objects are explicitly checked out from Teamcenter before the live
Excel spreadsheet is generated.
• You reserve access to the objects until you check them in, either when
you commit changes to the structure or cancel the changes.

4. Under Output Template, select Export All Visible Columns.
5. Click OK.
Excel opens with the objects exported. In the Home column, select the
number to open the item in Teamcenter.

19.6.4 Update live Excel data

You can change property
cell values and copy or
move values to other cells.
This method requires the
rich client to be running.
When you move the cursor

out of the updated cell, the
properties are updated in
Teamcenter.
Save the product structure to commit the changes to the database.

19.7 Activity
section, do the following activity:
• Export BOM and update the live Excel spreadsheet.

19.8 Summary
• Managing Teamcenter data in real time with Microsoft Office applications
• Updating BOM properties in real time with live Excel
• Submitting a document to a workflow, managing tasks, and signing off

tasks with Microsoft Office

Lesson
20 Using Change Manager
Purpose
The purpose of this lesson is to introduce basic change concepts and tasks.
Objectives
• List the available change objects.
• Follow a change object through a change process.
• Identify the basic change tasks.
• Identify the change state options.
Help topics
• Change Manager Guide

Using Change Manager
20.1 Introduction
Using Change Manager, you can track changes to a product throughout its
life cycle. You can propose a change to a product and then manage the entire
cycle of review, approval, and implementation of the change.
Change Manager is used by a wide range of users. Anyone who uses
Teamcenter can create a problem report (PR) to identify and formally track
an issue with your product information. Others who are involved in the
change process can review and confirm the problem and provide input into
what business objects must be updated to resolve the issue. Members of a
change review or change implementation board can review and approve or
disapprove the changes.
Change Manager enables an organization to continuously improve its
products by building them according to released documents, and then
creating, changing, and approving the documents.
• Use Change Manager with the Workflow Viewer application to track the
evolution of product changes through your organization according to a
controlled, repeatable process.
• Use Change Manager with the Schedule Manager application to create

work breakdown structures you can use to plan and schedule product
changes.

20.1.1 Change Manager interface
1 Change Home view Contains saved searches for change objects

defined by system administrators and
users. The default search is My Open
Changes.
2 Change Manager Contains views to display change
perspective properties, related items, BOM changes,
change effectivity, and work breakdown
tasks.

20.1.2 Change Manager tabs

Tab Description
Summary Displays the property information of the
selected object.
Details Displays the children of the selected component
in the Change tree.
Viewer Displays the registered viewer for the selected
component in the Change tree. When a change
revision is selected, the Viewer tab displays a
user-defined list of change properties and also
displays change forms in a tabular format.
Impact Analysis Provides graphical where-used and
where-referenced search capabilities.
BOM Changes Displays changes to the structure of the selected
object, based on the displayed engineering
change.
Change Effectivity Displays the end item effectivity information for
the selected impacted/solution items. End item
effectivity information is created, modified,
and displayed in this view. Clicking the Create
button opens the Create Effectivity dialog box.
Use this dialog box to search for end items and
to set unit and date effectivities.

20.2 Basic concepts for using Change Manager

Change Manager provides a change management foundation as well as a
preconfigured change management state model that enforces default business
rules.
The preconfigured model in Change Manager is based on the industry
standard precepts of the CMII closed-loop change model.
• CMII is the root of many Change Manager features including the
fast track classification, change states, participants, and overall work
processes.
• To enable greater flexibility to meet diverse customer needs, Change

Manager does not fully conform to CMII nor is it CMII certified.
Using Change Manager, your company can create consistent, controlled,

closed-loop processes to manage change and continuous improvement
according to its business model.

20.2.1 Managing the change cycle
Using Change Manager, you can propose a change to a product and then
manage the entire cycle of investigation, elaboration, review, approval, and
implementation of the change. You articulate the work required to:
• Implement a change.
• Assess its impact on any managed business items such as parts or

documents.
• Notify life cycle participants about proposed and authorized changes.
• Track progress and completion of work.
• Compare before and after product configurations.
These tasks are typically controlled by workflows that flexibly guide the
change through the change process.

20.2.2 Change management data objects
Change objects capture the necessary change information either as part of

their properties or through establishing relations with other objects.
The change management solution is supported using the following change
object types:
• Problem report (PR)
• Change request (ECR)
• Change notice (ECN)
• Deviation request

20.2.3 What kind of changes can you create?
The change management solution is supported using the following change

objects:
Change object Description

Problem report (PR) Initiates a change.
A PR captures information about a problem or
an enhancement. It includes the information
necessary to confirm and reproduce any
problems observed or to document the specifics
of a request for an enhancement. Additional
attributes document the perceived severity of
the problem and set the priority for addressing
the issue relative to other PRs.
The processing of a PR sometimes leads to the
creation of a change request (CR).
Creating a PR is an optional step in the change
process. Depending on the conventions at
your site, you may first identify a problem or
enhancement with a CR, not a PR.
A PR may be addressed by one or more CRs.
Change request (CR) Initiates a proposal that recommends a change
and captures business decisions associated with
the change.
A CR proposes a solution to the problem with
cost estimates and benefits of making the
change. The actual solution (for example, a new
item revision) is implemented in the change
notice (CN).
A CR is typically a response to a PR unless the
PR stage is skipped.
A single CR may logically group and address
issues identified in multiple PRs.
An CR may be addressed by one or more CNs.

Change object Description

Change notice (CN) Implements a change.
It provides a detailed work plan to resolve one
or more CRs or a portion of one CR.
A CN identifies all items and documents
affected by a change and authorizes the actions
that address a change.
Deviation request Seeks consent to deviate from a solution in
production to resolve a set of problems to
initiate improvements. Typically, there are two
types of deviation requests:
• Request for deviation
Seeks consent to deviate from a part
solution.
• Request for waiver

Seeks consent to accept a non-conforming
part.

20.2.4 Relationship between change objects
During the change process, Change Manager allows other business objects
(such as items, schedules, assemblies) to be related to change objects (PRs,
ECRs, or ECNs) or change objects to be related to each other through
relationships. Relationships are represented graphically as folders, often
referred to as pseudofolders. The folders help you track all business objects
related to the change.
The following figure illustrates the relationship between these objects in the
preconfigured Change Manager model.
Each change object shows these relationships in the Implements and

Implemented By folders.

Issues identified in one or more PRs can be implemented by a single ECR.

Similarly, issues identified in one or more ECRs can be implemented by a
single ECN. Likewise, a single ECR can be split and implemented by two or
more ECNs, as shown. Using Change Manager, you can create very complex
structures of changes to satisfy specific change requirements, providing you
with the flexibility you need.

20.2.5 Classifying changes
Product changes can be classified to indicate the applicable change process to

implement the change. Teamcenter provides a property that directs changes
on one of two tracks:
• Fast track classification empowers a user to plan a change, approve it,
and begin execution without the change being reviewed and approved by
a separate review board. Fast track changes meet prescribed criteria
such as low risk or low cost.
• Standard track classification follows a more formal change process to

manage the entire cycle of review, approval, and implementation of a
change, including change and implementation review boards.

20.2.6 About the participants in the change process
Different types of users are involved in various phases of the change process.
For example, at the start of the change process, a requestor creates a change
object. During the life of the change object, analysts review it, provide input,
and implement the change; and change specialists (change administrators)
facilitate its movement through the change process. Members of a change
review or change implementation board may review and approve or
disapprove the change.
The terms requestor, analyst, specialist (administrator), implementation
board, and review board refer to roles that participants perform at different
steps of the change process. Depending on the complexity of a change, the
same person may perform many roles, or many people may perform the same
role.
A change specialist assigns users for each participant type used in the
change object. A change management workflow can then be configured to
automatically assign workflow tasks to the appropriate users based on their
participant type on the change object.
For example, the workflow can automatically assign the analyst to perform
the Implement Change workflow task. These users are referred to as
dynamic participants.
Note
• See your workflow administrator for information about how your
company’s change management workflows are configured.

20.3 What can you do in Change Manager?
Identify a problem
If you are requesting a change or reviewing a recommended solution or plan

as a member of change review board:
• Create a problem report to identify a problem or enhancement, provide

a preliminary assessment, and show the steps necessary to reproduce
the problem.
• Create an change request (CR) to address the problem report.
• Create a new change notice (CN) to address the approved change request
or associate the change request with an existing change notice.
Review a solution
• Review CRs and CNs and make a business decision to approve or reject.
Manage the change process
If you are the change specialist managing the implementation of the change:
• Initiate a workflow to guide a change through the phases of a change

process.
• Assign participants as the analyst and reviewers.
• Assign effectivity to specify when a CN takes effect.
• Close CRs and CNs.
Develop or implement a solution
If you are the analyst determining how to implement a solution or if you are
implementing the solution:
• Define change properties.
• Relate problem and reference items.
• Create a work breakdown using Schedule Manager.
• Implement the change by creating and revising affected items.

Administer the change management process

If you are administering Change Manager, you can:
• Install and set up Change Manager.
• Set Change Manager options.
• Set up users and the organization and roles.
• Define custom change management objects.
• Control the actions of participants through conditions.
• Create workflows.

20.4 Change management process

You can manage your changes in the way that works best for your company’s
processes. The change process must be designed to impose the appropriate
level of rigor and control, based on the level of risk, cost, and the business
items impacted by the change.
You can classify a change as fast track or standard track. In a fast track
process, the change does not go through a formal review process, while a
standard track follows a more rigorous process, and may include a schedule to
manage the required tasks.
Siemens PLM Software does not provide change workflows — you must create
your own. Change processes can be designed and managed in the way that
works best for your business processes.
This example shows the flow of a typical standard track process.
1. Author a problem report.

A requestor creates a problem report to identify a problem or
enhancement, provide a preliminary assessment, and show the steps
necessary to reproduce the problem.
2. Approve a problem report.

A change specialist or administrator assigns a priority to the problem
report and assigns it to an analyst for technical review. The specialist or
analyst recommends a disposition, such as Approved.

3. Create a change request.

A requestor (who may be the analyst associated with the problem report)
creates a change request to address the problem report.
Note
The change request can address more than one problem report.
4. Evaluate the impacts.

The change specialist assigns the change request to an analyst. The
analyst identifies the items impacted by the change, prepares supporting
documentation, and prepares a high-level proposal for the actions
required to implement the change.
5. Make a business decision.

A change specialist submits the change request to a change review
board who decides if the change will be made. The change review board
either approves the change request, rejects it, or requires additional
investigation. If this is a fast track change, the review board is the owner
of the change and the process moves to the execute change step.
At this stage, a decision is made about whether to revise or create new
items, according to the form, fit and function, and interoperability.
6. Create a change notice. (Not used in fast track processes.)

The requestor (who may be the analyst of the change request) either
derives a new change notice to address the approved change request or
associates the change request with an existing change notice. The change
notice addresses the implementation details of the change. It may address
multiple change requests. The requestor can delegate responsibility for
elaborating the details of the implementation plan.
7. Prepare an implementation plan. (Not used in fast track processes.)

The analyst develops a detailed plan to address the set of approved
change requests addressed by the change notice.
At this stage the agreed solution is implemented in the new/revised items.
8. Approve the change notice. (Not used in fast track processes.)

The change implementation board reviews and approves the plan to
address the change.

9. Assign an effectivity. (Not used in fast track processes.)

A change specialist assigns effectivities to the change notice. The
effectivities specify the timing of when the change takes effect.
10. Execute the change.

The analyst closes the associated levels of the implementation plan. When
all the actions associated with each level of the implementation plan are
complete, a change specialist closes the change.
11. Close the change.

The analyst closes the associated levels of the implementation plan. When
all the actions associated with each level of the implementation plan are
complete, a change administrator closes the change.

20.4.1 Problem report (PR) process example
After you create a PR, assign a specialist, and submit it to a workflow, you:
• Validate the Problem Report
The assigned specialist reviews the PR properties.
• Assign Analyst
The assigned specialist assigns an analyst.
• Analyze PR / Approve/Reject
The assigned analyst reviews the PR and approves or rejects the problem.

20.4.2 Change request fast track process example
The following fast track example shows a process for managing an ECR
through fast track.
After you create an ECR, assign a specialist and submit it to a workflow, you:
• Classify/Assign Analyst
The assigned specialist classifies the ECR as fast track, determines if
more planning is required, and assigns an analyst.
Note
Change Manager conditions control who can assign the analyst.
The default condition allows the current change analyst to assign a
new analyst or allows the change specialist to assign an analyst.
• Complete Planning
At this stage, the analyst develops a solution or several alternative
solutions. The analyst does this by creating markups on documents, Word
documents, presentations, and so on. No decision has been made at this
stage about whether to proceed or what new items or item revisions may
be required.
If more planning is required, the assigned analyst completes it. The ECR
returns to the specialist to determine if planning is complete.
• Derive Change
The assigned change specialist derives an ECN to implement the solution.
• ECN Process
The assigned specialist begins a fast track ECN process so the change can
be executed, and the solution items added.

20.4.3 Change request standard track process example
The following standard track example shows a process for managing an ECR
through standard track.
After you create an ECR, assign a specialist, and submit it to a workflow, you:
The assigned specialist classifies the ECR as standard track, determines
if more planning is required, and assigns an analyst.
At this stage, the analyst develops a solution or several alternative
solutions.
The analyst does this by creating markups on documents, Word
documents, presentations, and so on. No decision has been made at this
stage about whether to proceed or what new Items or item revisions are
required.
If more planning is required, the assigned analyst completes it. The ECR
returns to the specialist to determine if planning is complete.
• CRB Review
If the planning is complete, the assigned change review board reviews the
change and signs off as approved or rejected with comments.
• Record Business Decision

The assigned specialist reviews CRB signoffs and comments and records
the business decision.

• Disposition
If approval criteria are met, the ECR is approved. The ECN process is
executed.
If the ECR is deferred, it is placed on hold.
If the ECR is rejected, it is closed.
If the ECR is not ready, it is sent for rework and returns to the CRB
review step.

20.4.4 Change notice process example

The following example shows a process for managing an ECN for
implementing an ECR that goes through the standard track process.
You can also develop an ECN process for an ECR that goes through a fast
track process. That ECN would not include a formal review by the change
implementation board. It would also be implemented by the same analyst
assigned to the ECR.
After you create an ECN, assign a specialist, and submit it to a workflow, you:
The assigned specialist determines if more planning is required and
assigns an analyst.
The analyst develops a solution or several alternative solutions. The
analyst does this by creating markups on documents, Word documents,
presentations, and so on.
No decision has been made at this stage about whether to proceed or what
new items or item revisions may be required.
If more planning is required, the assigned analyst completes the planning.
The ECN returns to the specialist to determine if planning is complete.
• Change Implementation Board Review

If the planning is complete, the assigned change implementation board
reviews the change and signs off as approved or rejected with comments.
• Record Implementation Decision

The assigned specialist reviews change implementation board signoffs
and comments and records the implementation decision.

• Disposition
If approval criteria are met, the ECN is approved.
If the ECN is deferred, it is placed on hold.
If the ECN is rejected, it is closed.
If the ECN is not ready, it is sent for rework and returns to the CIB
review step.
Note
The Disposition state applies to all change objects.
• Execute Change
If the ECN is approved, the assigned resources (for example, designers)
implement the change according to the plan. They edit the models
according to the engineer’s directions as documented in the ECR. The
design changes are approved as part of the process.
• Close Change
The assigned specialist reviews the changes. If all tasks are complete, the
ECN is closed.

20.5 Change states

Change states define the status, degree of completion, and the business
decision during change processing.
• Change Manager is delivered with a change model initially configured
with three key states: Closure, Maturity, and Disposition.
• A change object progresses from one state to the next during the change
process.
• The states and transition methods between states are configurable.

Note
Change states are managed using workflow handlers that can be
created and modified by your Teamcenter administrator.
• Your company may choose to use the initial configuration delivered with
Change Manager or design its own.

20.5.1 Initial change state configuration
The initial configuration of change states in Change Manager progresses as

follows:
• At the beginning of the process, the Closure state is set to open. This is
the state in which a problem report (PR), change request (ECR), or change
notice (ECN) is created.
• When the closure state is Open, the change object moves through the
phases of the maturity and disposition states of the change process.
During these phases, decisions about the change are made.
• The Closure state remains open until the change object progresses
through all phases of the change process. When the change process is
complete, the closure state is set to its final state.

20.5.2 Change states values
There are three key change states for change objects in the Change Manager
initial configuration. Each type of change object (PR, ECR, ECN) has its own
change states and must be closed individually through the process.
Note
Although these states are defined on each object (PR, ECR, and ECN),
the values apply to the overall change process. Therefore, the Closure
state would not be set to Closed until the change has been completed,
at which stage the closure and other states needs to be set on the PR
and ECR, as appropriate.
• Closure defines the status of the change object. Change objects start
with an open state and remain there until the change is complete unless
a decision is made to defer or cancel the change. The Closure change
state can be one of the following:
o Open (default value on newly created change objects)
o Closed
o On hold
o Cancelled
• Maturity defines the degree of completion of the overall change process.

The elaborating state is the investigation phase. The reviewing state can
be informal where one user approves the change or formal where a review
board must approve. Reviewers can decide the change is not ready and
send it back to the planning phase or approve the change. Once approved,
the change moves to the executing state and the actual changes begin
with the creation of new items and item revisions. Finally, when all the
necessary data has been created and approved, the change is considered
complete.
The Maturity change state can be one of the following:
o Elaborating (default value on newly created change objects)
o Reviewing
o Executing
o Complete

• Disposition represents a technical, business, or implementation decision

by a person or review board about a change object’s approval.
When a change object is created, the Disposition value is set to None
(no disposition), which is the default. During review, the value should be
set to Investigate and once a decision has been made, the value set to
Approved, Disapproved, or possibly Deferred.
The Disposition change state can be one of the following:
o None (default value on newly created change objects)
o Investigate
o Approved
o Disapproved
o Deferred

20.5.3 Example of the state changes of a problem report
The following example shows how the default state properties change as the
problem report progresses through the steps in the workflow. The change
states in your organization may vary.
Step Closure Maturity Disposition

Start Open Elaborating None
Validate the Open Elaborating None
Problem Report
Assign Analyst Open Elaborating None
Analyze PR Open Elaborating None
Approve/Reject Open Reviewing None
End Open Reviewing One of these:
• Approved
• Disapproved
• Deferred
• Investigate
The state property settings restrict permissions to add items to the problem
report’s folders. For example, the closure, maturity, and disposition property
settings must be Open, Elaborating, and None for a Requestor to add an
item revision to the problem report’s Problem Items folder.
The Change Manager Guide specifies all the required property settings.
Note
A workflow handler is used to change the state properties. State
property values cannot be set by users.

20.5.4 Example of the state changes in a fast track change request
The following example shows how the state properties change as the change
request progresses through the steps in the workflow. The change states in
your organization may vary.
Release
Step Closure Maturity Disposition state
Start Open Elaborating None Pending
Classify/Assign Open Elaborating None Pending
Analyst
Complete Open Elaborating None Pending
Planning
Execute Open Executing Approved Pending
Change
Close Change Open Executing Approved Pending
End One of these: One of these: One of these: Released
• Closed • Complete • Approved
• Canceled • Elaborating • Disapproved
• On hold • Executing • Deferred

The state property settings restrict permissions to add items to the change
request’s folders. For example, the closure, maturity, and disposition property
settings must be Open, Executing, and Approved for an Analyst to add an
item revision to the change request’s Solution Items folder.
Note

20.5.5 Example of the state changes in a standard track change request
The following example shows how the state properties change as the
ECR progresses through the workflow steps. The change states in your
organization may vary.
Release
Analyst
Planning
CRB review Open Reviewing None Pending
Record Open Reviewing One of these: Pending
Business
Decision • Approved
• Disapproved
• Deferred
• Investigate
Rework Open Elaborating Investigate Pending
End One of these: One of these: One of these: Pending
• Open • Reviewing • Approved
• On hold • Executing • Deferred
The state property settings restrict permissions to add items to the enterprise
change request’s folders. For example, the closure, maturity, and disposition

property settings must be Open, Elaborating, and None for a Requestor

to add a problem report to a change request. The PR state settings have
restrictions as well (Open, Reviewing, Approved).
Note

20.5.6 Example of the state changes in a change notice
The following is an example of how state properties change as the change

notice progresses through the steps in the workflow. The change states in
your organization may vary.
Release
Analyst
Planning
CIB Review Open Reviewing None Pending
Record Open Reviewing One of these: Pending
Implementation
Decision • Approved
• Disapproved
• Deferred
• Investigate
Set Open Reviewing Approved Pending
Effectivity
Rework Open Elaborating Investigate Pending
Execute Open Executing Approved Pending
Change
Close Change Open Executing Approved Pending

Release
End One of these: One of these: One of these: Released
• Closed • Complete • Approved
• On hold • Reviewing • Deferred
• Executing
The state property settings restrict permissions to add items to the change
notice’s folders.
For example, the closure, maturity, and disposition property settings must be
Open, Elaborating, and None for a Requestor to add a change request
(CR) to a change notice (CN). The CR state settings have restrictions as well
(Open, Reviewing, Approved).
To relate a revision to an CN, the closure, maturity, and disposition property
settings must be Open, Reviewing, and Approved as well as the release
state must be something other than null or Released (for example, Pending).
Note

20.6 Searching for existing change objects

System-defined and user-defined searches can be used to find existing change
objects in Change Manager.
System-defined searches:
• Can be created, modified, or deleted only by a Teamcenter site
administrator.
• Are shared by all users at the site.
• Are populated by saved queries and do not require users to provide search
criteria.
• Appear as folders in the Change Home view.
Note
The My Open Changes system-defined search is standard with
Teamcenter and appears as a folder in the Change Home view.
User-defined searches:
• Are created by individual users for their own personal use.
• Are populated by the searches in the user’s My Saved Searches list.
• Appear as folders in the Change Home view.

20.7 Managing change object searches
The Change Home view contains saved searches for change objects. Use
the Change Home view to:
• Execute saved searches to find change objects.
• Add and show saved searches for change objects.
• Remove and hide saved searches for change objects.
Change object search results appear in the Change Home view tree.

20.7.1 Executing and deleting change object searches
Use the Change Home view to execute and delete your change object searches.
To execute a search, either:
• Expand the applicable search folder.
• Right-click an expanded search folder and choose Refresh.
To delete a search:
1. Right-click a search folder and choose Delete.
2. In the Delete dialog box, click OK.
Note
System-defined searches can be deleted only by a Teamcenter site
administrator.

20.7.2 Organizing the Change Home view

Use the Manage saved searches dialog box to organize the saved searches
in the Change Home view.
1. In the Change Home view, click Manage Change Home saved searches
.
2. In the Manage Saved Searches dialog box, click Add.
3. The default type is User-defined.

If you are an administrator, you can select System-defined from the list if
you want the search available to all users.
4. Click the Assigned search list to select the search that is assigned to
the folder.
The list contains your user-defined saved searches.
Note
If you add a search that requires the user to provide additional
information, an error is displayed when that search folder is opened
by a user.
Several system-defined searches are available; however, the only one you
should use is My Open Changes.
All other system-defined searches require additional information and
display an error if a user attempts to open them.
5. The Search name defaults to the name of the search you selected in the
Assigned search list.
Optionally, you can change it.

6. To hide a search, clear the search’s Show check box in the in the Manage
Saved Searches dialog box.
7. To show a hidden search, select the search’s Show check box.
8. Click OK.

20.8 Activity
In the Using Change Manager section, do the following activity:
• Find and view a problem report

20.9 Summary
• Available change objects
• Change process examples
• Basic change tasks
• Change state options

Lesson
21 Creating and managing

change objects
Purpose
The purpose of this lesson is to create and elaborate change objects through a
predefined change process.
Objectives
• Create and complete a problem report and submit it to a change process.
• Create a change request and submit it to a change process.
• Identify the key participants in a change process.
• Perform tasks in the change process.
• Relate change data to change folders.
Help topics

Creating and managing change objects
21.1 Creating a change object

Initially, any user can create a problem report, but only members of the
administrator group can create change requests or change notices. By using
groups and roles and by setting conditions in the Business Modeler IDE,
however, your Teamcenter administrator can configure which users are
authorized to create the various change objects.
The following methods can be used to create a change object:
• Individually
• In the context of an impacted or problem item revision
• Derived from another change object

Note
Only ECRs and ECNs can be derived from another change object.

21.1.1 Create a problem report

• Select the folder to contain the PR, and choose File→New→Change.
• Right-click an item revision and choose New Change in context.
2. In the New Change dialog box, select Problem Report and click Next.

3. Type a name in the Synopsis box and a description of the problem in

the Description box.
You can also type a problem report ID and revision in the PR Number
and Revision boxes. If you do not provide an ID and revision number,
Teamcenter provides them automatically.
4. Click Finish.
If you created the problem report by right-clicking the item revision and
choosing New Change in context, the item revision is automatically
copied to the problem report Problem Items folder.

21.1.2 Create a change request
1. Create the change request in one of the following ways:

• Select the folder to contain the ECR, and choose File→New→Change.
• Right-click an item revision and choose New Change in context.
• Select one or more problem report revisions, right-click, and choose

Derive Change.
The problem report revisions must have their properties set to:
Property Must be
Maturity Reviewing
Disposition Approved
Closure Open
2. In the dialog box, select Change Request and click Next.
3. If this is a new change, type a name in the Synopsis box and a description
of the change request in the Description box.
If this is a derived change, the boxes contain the name and description
from the problem report revision. You can edit these boxes.
You can also type a change request ID and revision in the ECR No.

If you derived this change request from a single problem report, the
Propagate relations check box is available. If you want to copy the
relationships (such as reference items and problem items) from the
problem report to the change request, select the check box.
Note
Propagate relations is available only when a change request is
derived from a single problem report. When more than one problem
report exists, this relationship must be created manually.
4. Click Finish.
If you created the change request by right-clicking the item revision and
copied into the change request Problem Items folder.

21.1.3 Create a change notice

1. Create the change notice in one of the following ways:
• Choose File→New→Change.
• Select an item revision, right-click, and choose New Change in context.
• Select one or more change request revisions, right-click, and choose

Derive Change.
The change request revisions must have their properties set to:
Property Must be
Maturity Reviewing
Closure Open
2. In the dialog box, select Change Notice and click Next.
3. Type a name in the Synopsis box and a description of the change notice
in the Description box.
You can also type a change notice ID and revision in the ECN Number
If this is a derived change, the boxes contain the name and description
from the change request revision. You can edit these boxes.
If you derived this change notice from a single ECR, the Propagate
relations check box is available. If you want to copy the relationships

(such as reference items and problem items) from the change request to
the change notice, select the check box.
4. Click Finish.
If you created the change notice by right-clicking the item revision and
copied into the change notice Problem Items folder.

21.2 Managing a change

Using Change Manager, you can propose a change to a product and then
manage the entire cycle of investigation, elaboration, review, approval, and
implementation of the change.
You articulate the work required to:
• Implement a change.
• Assess its impact on any managed business items, such as parts or

documents.
• Notify life cycle participants about proposed or authorized changes.
• Track progress and completion of the change.
These tasks are typically controlled by workflows that flexibly guide the
change through the four phases of the change process: authoring, review
and approval, execution, and closure.
Note
By default, users must be in the dba group to perform change specialist
actions to manage changes. You can control the specialist groups by
configuring the conditions in the Business Modeler IDE.

21.2.1 Relating items to a change and the properties required
During the change process, you elaborate a change object by relating other
objects to it.
For example, you may need to add reference documents to a problem report
(PR) or specify which item revisions are impacted by an change revision
(ECR) as shown. When you implement a change, new item revisions must
be related as solution items.
Your administrator can configure the types of relations to be propagated

when change objects are derived. Because the derivation action can only be
performed on a single selected change object, any relationships you want from
other change objects must be manually created.
For example, if one ECR is used to implement multiple PRs, you must add the
other PRs to the ECR Implements folder as well as add related items to its
other folders, such as adding problem items to its Problem Items folder.
You create the appropriate relations by adding objects to the folders of
the change object. You do this as you would add objects to any folder in
Teamcenter.

Change folder Description

Problem Items
Contains item revisions To create a relationship between an item revision
with the problems that and a change object (PR, ECR, or ECN), add the
the change is to address. item revision to the change object’s Problem Items
This could be the parent folder.
assembly.
Impacted Items
Contains item revisions 1. To create a relationship between an item
that are being changed revision that an change request (ECR) or
as a result of the change change notice (ECN) affects and the ECR or
process. ECN.
2. To add the item revision to the ECR or ECN’s

Impacted Items folder.
Solution Items
Contains item revisions To create a relationship between an item revision
that are generated as and the ECN that implements the change, add the
a result of the change item revision to the ECN’s Solution Items folder.
(for example, the new
piece parts and the new
revision of the parent
assembly to contain
them).
Reference Items
Contains any To associate related information (such as analysis
Teamcenter object, documents and system logs) with a PR, ECR,
including datasets, or ECN, add any Teamcenter object, including
that reference related datasets, to the Reference Items folder.
information (such as
analysis documents and
system logs).
Implements
Contains change object Note
revisions that reference
this change object. An A PR does not have a Implements folder
ECR implements PRs. because it does not implement a problem,
An ECN implements only identifies one.
ECRs.
Usually, the Implements folder is automatically
populated as part of the change process, but you
can add to it if you are an assigned participant.

Change folder Description

Implemented By
Contains change object Usually, the Implemented By folder is
revisions that are automatically populated as part of the change
referenced by this process, but you can add to it if you are an
change object. A PR is assigned participant.
implemented by ECRs.
An ECR is implemented
by ECNs.

21.2.2 Assign participants
1. Select the change object that you want to assign participants to.
2. Choose Tools→Assign Participants.
3. In the Assign Participants dialog box, select the participant type (for
example, Change Specialist I).
4. Click either the Organization or Project Teams tab and select a user
to assign to the participant type.
You can search for a group, role, or user in the box below the tabs.
Use Resource Pool Options to assign a set of group or role members as
participants instead of individual users. When a group or role is selected,
additional options become available.
• If you select a group, you can click Any Member so any member of the
group can be the participant for that type.
• If you select Proposed Reviewers, Change Review Board, or Change

Implementation Board, and then select a group, you can click All
Members to assign all members of the group.

• If you select a role under a group, you can click Any Member and
choose Specific Group to assign any member of the combined group
and role as the participant type or choose Any Group to assign any
member of any group and the selected role as the participant type.
5. To remove a user as a participant, select the user under the participant

type and click Remove.
6. To change a participant, select the user under the participant type, select
the new user in the Organization or Project Teams tab, and click Modify.
7. Click Add.
8. When you are finished assigning participants, click OK.

21.3 Create a work breakdown

Note
You can copy an existing schedule, but it can only be associated with
one change object.
1. Select the Plan Items folder of the change request (ECR) or change notice
(ECN) for which you want to create a work breakdown.
For an ECR or ECN, you can add objects to the Plan Items folder if you
are an assigned participant and the change object property settings are as
follows.
Assigned
participant Closure Disposition Maturity
Analyst Open None Elaborating
or
Open Investigate Reviewing

2. Choose File→New→Schedule.
This starts the New Schedule wizard where you create your work
breakdowns.
Complete the steps in the New Schedule wizard to create the new
schedule.
You can create several schedules to help you analyze the change.
3. In the Open Change view, select the schedule in the Plan Items folder
and click Open Schedule .
The schedule is displayed.
4. Add tasks to your schedules.

5. Assign resources to tasks, including selecting responsible people using

the Membership button .
6. In the Schedule Manager view, click View Task folders .

Change Manager displays the Open Task view.
7. Add item revisions to the task folders as necessary.
8. (Optional) Roll up the item revisions in your task folders to the change
object folders.

21.4 Activities
In the Creating and managing change objects section, do the following
activities:
• Create a change request.
• Elaborate the change request.
• Review and approve the change request.

21.5 Summary
• Creating a change object and submitting it to a change process
• Identifying the key participants in the change process
• Relating change data to change folders

Lesson
22 Elaborating and executing

the change
Purpose
The purpose of this lesson is to elaborate and execute the change.
Objectives
• Perform tasks in the change process.
• Create new or replacement items.
• Relate a solution item to an impacted item.
• Manage replacements through supersedures.
Help topics

Elaborating and executing the change
22.1 Executing the change

Product changes occur during the change execution step of the change process.
Before a change occurs, a problem is be identified and the change is approved.
1. Create new or replacement items to address the problem.
2. Roll up objects from the work breakdown structure to the change object.
3. Relate solution items to impacted items.
4. Create, update, and remove BOM lines for the impacted items as
necessary.
5. Create supersedures to define and track the history of replacement parts.

22.2 Adding an affected item revision to change folders

During the change process, you elaborate change objects by relating other
objects to it. For example, you may need to add reference documents to
a PR or specify which item revisions are impacted by an ECR. When you
implement a change, new item revisions need to be related as solution items.
• The Problem Items folder contains item revisions with the problems that
the change is to address.
• The Impacted Items folder contains the assembly item revisions that
have the problem components that are being changed as a result of the
change process.
• The Solution Items folder contains item revisions that are generated as a
result of the change (for example, the new piece parts and the new revision
of the parent assembly to contain them).
You create the appropriate relations by adding objects to these folders from
other Teamcenter views, including Change Home, Teamcenter Component,
and Search Results.

22.3 Create new or replacement items

You can use one of the following methods to create a new or replacement
item to address the change:
• Create a new item using the File®New command.
• Revise the problem or impacted item.
• Copy an existing item.

22.4 Relating a solution item to an impacted item

To create BOM change and supersedure records for a change, there must be
an exact correspondence between the solution and impacted item revisions.
You must create the relation before the solution item is sent to Structure
Manager.
• If the change has a single impacted item revision and a single solution
item revision for the same item, the BOM change relationship is created
automatically.
• If there is more than one revision of the same item in either or both
the Impacted Items and Solution Items folders, you must create the
relationship manually.
• Supersedure relationships are always created manually.

22.5 Relate a solution item to an impacted item manually

1. Double-click the ECN revision to open in the Open Change view and
make it the root of Change Manager, as shown.
2. Right-click the item revision and choose Relate Solution Item to

Impacted Item.
Note
If the solution item is not related to an impacted item and you send
the solution item to Structure Manager, the Relate Solution Item to
Impacted Item dialog box appears. You must create the relation before
the solution item is sent to Structure Manager.

22.6 Manage replacements through supersedures
• Supersedures are created to define and track the history of replacement

parts.
• Supersedures are created and viewed in Structure Manager.
• The Supersedures pane in Structure Manager shows the additions and

cancellations to the impacted item revision.
• In the Supersedure pane, you can view a graphical representation of the

replacement history for a given occurrence in a product structure.

22.7 Create supersedures

1. In the Open Change view, with the ECN and its Solution Items folder
expanded, select the solution item revision, click View Menu and choose
Open in Structure Manager with Supersedure window.
2. In the Confirmation Dialog dialog box, click Yes.

Note
If this dialog box does not appear, close Structure Manager and
perform the previous step again.
The split window showing BOM changes appears in Structure Manager.

3. Select the replacement (added) and canceled parts.
4. With both components selected, click Create a new Supersedure .

Note
This button is in the lower portion of the Structure Manager pane,
on the right side of the section where the Supersedures folder
appears.
The supersedure appears under the Supersedures folder.
This is essentially a product structure compare, which shows you what

parts were added and what parts were canceled.
5. Expand the new supersedure item and the Adds and Cancels folders.
The item symbol with a + sign represents the added component. The
item symbol with a – sign represents the component being canceled.

22.8 View supersedure data

Supersedure data can be viewed from Structure Manager.
1. Click the Show/Hide the data panel button in Structure Manager

to display the data panel.
The data pane display includes a Supersedure tab.
2. Click the Supersedure tab.
3. Select the BOM line in Structure Manager whose supersedure data you
want to view.
Use the scroll bars in the Supersedure pane to locate and view the
supersedure diagram showing the additions and cancellations to the
affected item revision.
Note
If no supersedure exists for the selected BOM line assembly, a
message with this information appears in the Information box in
the Supersedure pane.

22.9 Assign effectivity

1. Select the change notice revision that you want to assign an effectivity to.
To set an effectivity, the change notice must have the following:
• You must be assigned as a change specialist for the change notice.
• The change notice must have a Released status.
• The change notice Disposition state must be set to Approved.
• The change notice Maturity state must be set to Reviewing.
2. Click the Change Effectivity pane.
3. Click Create.
4. Click Units or Dates effectivity, as appropriate, and define the range.
5. Define an end item to qualify the effectivity range. You must use this with
the unit effectivity range to specify a product, module, or subsystem that
carries the unit number to which this effectivity refers.

You can select an end item in one of the following ways:

• Click Open by Name adjacent to the End Item box and search for
an item by identifier and/or name.
• Copy an item to the clipboard and click Paste adjacent to the End
Item box.
• Click MRU adjacent to the End Item box.
Note
To remove the entered end item, click Clear adjacent to the End
Item box.
Once you select the end item, select the revision from the list to the right
of Clear .
6. When you are finished, click OK.

22.10 Activities
In the Elaborating and executing the change section, do the following
activities:
• Create a change notice.
• Create the implementation plan.
• Review and approve the implementation plan.
• Complete the execution phase.
• Verify the change is in place.

22.11 Summary
• Performing tasks in the change process
• Creating new or replacement items
• Relating a solution item to an impacted item
• Managing replacements through supersedures

Lesson
23 Working in the Teamcenter

thin client
Purpose
The purpose of this lesson is to manage Teamcenter objects using the
Teamcenter thin client.
Objectives
After you complete this lesson, should be able to:
• Use the thin client to navigate to various Teamcenter objects and
functions.
• Manage your thin client interface.
• Search in the thin client.
• Create or revise items or item revisions and perform basic data

management tasks in the thin client.
• Manage change in the thin client.
• Use workflows in the thin client.
Help topics
• Thin Client Interface Guide

Working in the Teamcenter thin client
23.1 Introduction
Use the thin client to navigate to various Teamcenter objects and functions.
The Teamcenter thin client is a Web-based interface. It provides an access
point to your data over the Web using a Web browser. Access is available to
the same Teamcenter server and data as the rich client uses. No thin client
software is required on a Teamcenter client.
The thin client interface can be used to perform many of the same tasks you
can perform in the rich client interface. However, there are fewer distinct
applications available in the thin client, and administrative tasks cannot be
performed in this interface.

23.1.1 Differences between the rich and thin client
Rich client • Requires Teamcenter client software installed on the

local (client) computer.
• Communicates with the Teamcenter server only as

needed, performing a variety of processing tasks
locally.
• Displays the date and time of an action based on the

time zone identified on the system where the rich
client is installed.
o Interprets dates and times entered by the
user based on the time zone identified on the
system where the rich client is installed.
o Interprets search criteria entered by the user in

the rich client time zone.
• Supports a broader set of Teamcenter administrative

and user tasks.
Thin client • Does not require Teamcenter client software installed

on the local (client) computer.
• Communicates with the Teamcenter server for most

interactions, performing almost all processing tasks
on the Teamcenter server.
• Displays the date and time of an action based on the

time zone in effect on the server.
Interprets dates and times entered by the user,
including search criteria, based on the time zone in
effect on the server.
• Supports a subset of applications and Teamcenter

user tasks but does not support many administrative
tasks.

23.1.2 Teamcenter functionality available in the thin client
Many commonly performed user tasks can be performed using the thin client,
including:
• Creating and managing basic data such as items, item revisions, datasets,
documents, vendor data, and other business objects.
• Participating in workflows.
• Searching in Teamcenter and managing reports.
• Navigating structures such as projects, occurrence groups, and structure

contexts.
• Creating and managing change objects, product structures, manufacturing

data, classification data, requirements, DesignContext data, schedule
data, collaboration context data, and electromechanical structures.
• Viewing audit logs.
• Viewing graphic data using embedded visualization.
• Importing and exporting data.

23.1.3 Teamcenter functionality not available in the thin client
Administration and configuration capabilities are typically not available in

the thin client. Administrative applications not available through thin client
include:
• Access Manager
• Audit Manager
• Organization
• Program
• Volume Management

23.1.4 Thin client interface
The thin client interface has a standard menu bar and toolbar with options
that vary depending on the currently active application. You can place the
cursor over a thin client toolbar button to display a tooltip description.
1 Menu bar and Provides access to menu and button commands

button bar and lists the current user name, group, role,
revision rule, and server.
2 Navigation pane Provides search functionality, link groups, and
application buttons.
You can expand and collapse the entire pane and
pane groups, select what is displayed in primary
and secondary areas, and configure the display
of applications.
3 Component pane Displays component hierarchies in a tree view.
You can resize this pane to be wider or narrower.

4 Data pane The data pane displays tabbed information.

• Depending on the type of object selected and
the configuration, you may see tabs such
as Overview, Details, Related Datasets,
Attachments, History, Change History, Where
Used, Structure, Impact Analysis, Available
Revisions, and Viewer.
• Each group of information can be configured to

display in table, list, or thumbnail. Each group
can also be supported by action command
buttons such as Cut and Copy.
• You can configure the columns in the Details

tab.
The default layout for thin client applications has a header bar containing
menus, command buttons, and session information above three panes,
arranged vertically side-by-side. Some thin client applications arrange the
component pane and the data pane horizontally.
The layout configuration for a thin client application can only be changed
by customization.

23.1.5 Start and stop a Teamcenter thin client session
Starting a thin client session requires a Web browser, for example, Microsoft
Internet Explorer or Mozilla Firefox.
Note
For approved Web browsers, see the Siemens PLM Software
Certification Database.
1. Open the Web browser

and type the URL of
the Web server in the
address box.
2. Press Enter.
Teamcenter displays
the logon page.
3. Type your user name

and password.
4. Click Login.
If logon is successful, the

thin client displays your
home page.
If the user name or
password is incorrect, the
thin client displays an
error message.
To change your current or

default group and roles
once you are logged on,
select your user name on
the application banner
or choose Edit→User
Settings.

Teamcenter displays the

User Settings dialog box.
To log off, click the Logout

button in the top right
corner of the Web browser.
Your administrator may modify the page that appears once you log on. By
default, it is set to your home page but may be set to display your worklist, a
specific search page, or a custom location.
If your browser is set to disable ActiveX controls, you may see an error
message when you attempt to select from a list of values (LOV).

23.1.6 Managing your thin client interface
The thin client home page is typically the default page that appears when you
log on. It serves as a starting point to allow you to navigate to other functions.
When you log on, the home page initially displays the contents of your Home
folder in the tree pane.
• The Home folder is the root object (topmost) on the page. You can
subsequently navigate to any other object that you have permission to
access and view this object as the root object on the page.
• Any children of the root object display below the object. The object may
be, for example, a dataset, structure, or collaboration context.
Note
You can expand and collapse the root object with the expand (+) and
collapse (–) buttons.

23.1.7 Using the top navigation bar
The top navigation bar displays:

• Menu commands relevant to the currently active application.
• Your user context data to the right of the page, typically the current user
name, group, role, and default revision rule.
• The Logout button , which logs you off Teamcenter.

23.1.8 Working with objects in the thin client component pane
You can select objects in the thin client component pane.

• Select an object in the component pane to display information about it in
the data pane.
• Click the expand button to expand an object.
• Double-click the object to open it as the root for the component pane.
• Hold the cursor over the object to display the action menu .
The action menu in the component pane provides the following commands:
• Open
Selects the object and makes it the root object in the component pane.
Note
Use this command to create URL links to objects.
When you open an object to make it the root object in the component
pane, the URL in the browser address field is updated. You can cut
and paste the URL to create a link to the object that can be included
in documents such as e-mails and spreadsheets.
• Cut
Selects the object to cut for pasting elsewhere.
• Copy
Creates a copy of the object that can pasted elsewhere in the thin client.

• Paste
Pastes the current content of the Teamcenter clipboard.
• Delete
Selects and deletes the link to the object from the current location.
• Check-In/Out
o Check-Out
Checks out the object if not already checked out.
o Check-In
Checks in the object if checked out already.
o Cancel Check-Out
Cancels the checkout for the current user.
• Properties
Displays the properties dialog box for the object. You can use this dialog
box to view information or to check out the object and edit information.
• Add to Favorites
Adds the object to the Favorites list in the navigation pane.

23.1.9 Working with tables

Some pages in the thin client present data in a table that contains the various
elements of the page. Tables can contain the following elements:
• Columns
Columns displayed within a page list various object properties, for
example, type and date modified.
o To change which columns are visible, choose Edit→Options and click

the Column Management tab.
o To resize a column, drag the column border in the appropriate

direction. Changes made to the column width in the thin client are
maintained throughout the thin client session.
o To sort table data, click a column header.
• Page components (rows)

The components within a page are displayed in rows.
In some tables, you can select multiple rows that are contiguous (a range
of rows) or noncontiguous (any random selection of rows).
o Single-click a row to clear any previous selection and select the row.
o Hold down the Ctrl key and click to toggle the selection state of the row.
o Hold down the Shift key and click to select a range of rows, from the
first selected row up to and including the current row. This action
clears any previous selection.
o Hold down the Ctrl and Shift keys and click to select a range of rows
from the last selected row up to and including the current row.
• Child rows
Children of a row are displayed indented under the row.
o The types of objects displayed as children depend on the type of object

selected.
For example, the children of a row displaying a folder are the folder
contents.
o The child rows of an object are displayed in a tree-like structure.
o You can show or hide child rows by expanding or collapsing the display
structure.

Use the + and – buttons to the left of the object display to expand
and collapse the tree structure.
• Scroll bar
The scroll bar is visible when the contents of the table are too large for
the browser window.
It appears on the right of the table. It allows you to scroll through the
contents of the table without scrolling any part of the page above, below
or to the side of the table.
Useful features, such as menus, are always visible.
• Dialog boxes
Dialog boxes show details of objects and allow you to enter data for simple
actions.
• Links
If a detailed page or action is associated with the object, it is hyperlinked
to the object.
Clicking the link has an particular action, depending on the type of the
object.
Object type Description

Folder Displays the selected folder as the root object.
Item Displays the selected item as the root object.
Item revision Displays the selected item revision as the root object.
Dataset Displays the selected dataset as the root object.
Form Displays the Form dialog box.
Web link Displays a dialog box containing details of the
underlying Web form.
Named Displays the file represented by the named reference.
reference
BOM view Displays the product structure, with the selected BVR
revision (BVR) as the root object.
User Opens a dialog box containing the user’s details.
Task Opens a dialog box that allows you to complete the
specific task.

23.1.10 Using dynamic menus
The thin client includes dynamic menus—the menu commands change

according to the task you are performing. For example, the menu commands
on your home page differs from the ones on your worklist page.
Note
Your administrator may suppress some menu commands that are not
relevant to your site. Features described in this help system may be
unavailable if menu commands are suppressed.
There are three basic types of actions that you can perform with these menus:
• Navigate to a new URL, replacing the current page, for example, to go
to your worklist.
• Open a dialog box on top of the current page, for example, to create a
new item.
• Execute an action within the current page, for example, clipboard actions
such as cut, copy, and paste.

23.1.11 Set your display options
Display options allow you to set whether all revisions, item relations, and
item revision relations are displayed. You can also choose your status symbols
and column sizes for Structure Manager. It also allows you to set whether
first column and menu entries appear in a new window when clicked. You can
also enable or disable the display of the contents of the Home folder and My
Worklist inbox in the Quick Links pane.
1. To open the Options dialog box, choose Edit→Options.
2. To view and set a display option, select the option from the list in the
Display tab.

23.1.12 Column management
Column management allows you to customize the appearance of columns.

If you add or remove columns, change the order of columns, or resize column
width in the thin client, the changes are maintained throughout the thin
client session.
Note
Resizing column widths are maintained only in the thin client and are
not reflected in the rich client.
1. To open the Options dialog box, choose Edit→Options.
2. Click the Column Management tab.
3. To view and set a display option, select the option from the list in the
Column Management tab.

23.2 Searching in the thin client

You can search the Teamcenter database for objects that match specific
criteria. Your administrator may define and save frequently used queries to
allow fast searches of the database.
Use dates
You can use dates as a criteria for narrowing searches. However, you must
enter all dates in the exact format defined by your administrator. This is the
same date format as shown on your home page.
Search for metadata or text

You can search for metadata (for example, the identifier of an item) or for text
(for example, the title of or keywords in a document). The Keyword Search
query form allows you to combine full-text and metadata searches into a single
query. This allows you to, for example, search for all documents containing a
given keyword that were created within a specified range of dates.
View search results

Search results display in a table on the results page. Each object found
appears on a separate line of the table. They are not displayed in a tree
hierarchy, so there are no child lines associated with any object. You can
open any of the objects displayed as the root object in the page by clicking
the link to the object.

23.2.1 Perform a quick search
You can perform a basic search for an item or dataset using the name, ID,
or keyword.
1. In the navigation pane,

select the type of search you
require from the list (for
example, Item ID).
2. Type a value for the search

criteria, for example, an
item identifier.
You can use wildcard
characters to define more
flexible search criteria;
type * to match multiple
characters or ? to match
exactly one character.
The search string may
be case sensitive or case
insensitive, as determined
by your option settings.
3. Click Go .
On completion of the search,
the results are listed in the
main window.
You can open any of the listed items from the search results list.
To return to the search results, click the Back button on your

browser.

23.2.2 Perform an advanced search
1. In the navigation pane, under Quick Search, select Advanced Search,

and select one of the search options.
The following example displays Item Revision advanced search criteria.

The criteria is modified to add an Item ID value and clear the Owning
User and Owning Group values.
2. Optionally, click Clear to remove the selected search criteria and specify a
new search.

3. Click Find to start the search.
You can open any of the listed objects from the search results list.
To return to the search results, click the Back button on your

browser.

23.2.3 Share saved searches
You can:
Create new shared searches
1. Click Save Search on

the relevant dialog box to
display the Add Search to
My Saved Searches dialog
box. Select a folder and
then type a name for the
saved search.
2. Select Shared to share your

saved search.
You can also create a new
folder by clicking New
Folder and typing a new
folder name in the Create
New Folder dialog box.
3. Click OK.
The search appears in the
My Saved Searches tab in
the Change Search dialog
box.
The search is now a shared
search.

Share existing saved searches with other users.
1. In the navigation pane, under

the Quick Search menu, choose
Advanced Search®More.
2. Click My Saved Searches in

the Change Search dialog box.
3. Select a search and click

Modify.
The system displays the
Rename My Saved Search
dialog box.
4. Select Shared.
5. Click OK.
The search is now a shared
search.

23.2.4 Use shared saved searches
You can:
• Use saved searches that others users have shared.
1. In the navigation pane,

under the Quick Search,
choose Advanced Search
®More.
2. Click My Saved Searches

in the Change Search
dialog box.
3. Select a search.
Note
By default, saved searches are private. You must select Shared in the
appropriate dialog box for others to view your saved searches.

23.3 Managing basic data
After you log on, click My Worklist under the Quick Links to open your
worklist. The worklist contains a list of assignments that you are responsible
for authoring, reviewing, acknowledging, or approving.
As you work with your assignments in thin client, you may need to:
• Create or revise items or item revisions.
• Work with datasets and forms.
• Perform basic data management tasks.

23.3.1 Create a folder
1. Go to your home page and select the object below which you want to create
the folder, and then choose New→Folder. For example, select an existing
item to contain the new folder.
Teamcenter displays the New Folder dialog box.
2. Enter the following information for the new folder:

• Name
Type a name for the folder.
• Description
Optionally, type a description of the new folder and its contents.
3. Click Finish to create the new folder. Alternatively, click Cancel to exit
without creating a new folder.

23.3.2 Create a new item in thin client
Creating a new item in thin client is similar to creating a new item in rich
client. In the thin client, the New Item dialog box displays tabs for each step
in the creation process.
In the following example, you create a new item in your Newstuff folder.
1. In your home page, select

the Newstuff folder.
2. Choose New→Item.
3. On the Type tab, select

the Item type.
4. Click Next or the General

tab.
5. On the General tab, type

a name for the item.
If left blank, the ID and
Revision values are
automatically generated.
Description and Unit of
Measure are optional.
6. Click Finish to create the

new item.

The new item appears in the

Newstuff folder.

23.3.3 Creating new items based on existing items in the thin client
Creating a new item based on an existing item or item revision in the thin
client is similar to creating an item based on an existing item in the rich client.
In the following example, you create a new item from an existing item. You
can also create a new item based on an existing item revision.

the item as the basis for
the new item.
2. Choose Edit→Save As.
3. Type a name for the item.

Revision values are
The properties for the new
revision are automatically
generated.

new item.
Newstuff folder.

In the following example, you create a new item based on an existing item
revision.

the item revision as the
basis for the new item.
2. Choose Edit→Save As.
3. In the Item Information

tab, type a name for the
item.
Revision values are
generated.
Additional tabs are
available to specify
property values.

new item.
Newstuff folder.

23.3.4 Revising an item revision
Creating a new item revision in the thin client is similar to creating an item
revision in the rich client.
In the following example, you create a new item revision based on an existing
item revision.

the item revision as the
basis for the new item
revision.
2. Choose Edit→Revise.
3. If left blank, the Revision

value is automatically
generated.
The Name value defaults
to the original revision
name but is modifiable.
generated.
Additional tabs are
available to specify
property values.

new item revision.
The new item revision appears
under the revised item.
Refresh the display by
collapsing and expanding the
Newstuff folder.
Note
With the Latest Working
rule applied, only
revision B appears.

23.3.5 Create a dataset

1. Select the object below
which you want to create
the dataset, and choose
New→Dataset.
For example, select an
existing folder to contain the
new object.
Teamcenter displays the New
Dataset dialog box.
2. On the Type tab, select the

type of the new dataset from
the list of available types.
For example, select MSWord.
3. On the Information tab,

provide:
• Name
Type a name for the
dataset.
• Description
Optionally, type a
description of the new
dataset.
4. On the Named Reference

tab, select or drop a file in the
Upload File text box.
Note
You can also specify the
Reference value.

new dataset. Alternatively,
click Cancel to exit without
creating a new dataset.

You can also create a new dataset by copying an existing dataset and choosing
the Paste As menu command. You are prompted for a name for the new
dataset.

23.3.5.1 Attach a named reference to the dataset
If you create a dataset with no associated named reference (data file), you can
explicitly attach the appropriate named reference to the dataset, as follows:
1. Double-click the dataset to which you want to attach the named reference.
Teamcenter displays the Upload File and Reference boxes.

• Enter the full path and file name for the data file.
• Click Browse and navigate the system folders to locate the file.
• Drag and drop a file onto the Upload File box.
3. Click Upload to upload the file and attach it to the dataset.

23.3.5.2 Edit datasets in the thin client
You can edit a dataset from the thin client using Client for Office.
The Teamcenter tab appears and the buttons are active. To save changes
to the dataset, click Save on the Teamcenter tab, not Microsoft Office
Save .
Note
Your administrator can configure single sign-on (SSO) to avoid multiple
logons.

23.4 Navigating structures

The thin client allows you to:
• Group work or tasks into projects or occurrence groups.
• View the properties of items in a structure, view forms, and manage

incremental changes.
• View a structure in context.

23.4.1 Managing product structure
The product structure page displays the structure of a product or subassembly.

You can use the product structure page to create, view, and edit product
structures.
Note
The thin client does not extensively check for cyclic product structures.
Do not create structures using the thin client if you are concerned about
cyclic structure avoidance.
To display the product structure of an item revision (the root item):

1. Select the item on your home page.
2. Either click Structure Manager in the navigation pane or choose

View® Structure.
You can then copy and paste other items under the root item to modify the
product structure. The children of a line in the product structure page are
the children of the item in the BOM.
• Teamcenter displays lines with defined variant conditions with a different
background color.
• A symbol to the left of the name of each line indicates its type, for example,
item or item revision.
• If a line includes a © symbol, the revision is configured by the current

revision rule; otherwise, it is not configured.

23.5 Using Change Manager in the thin client

Change Manager in the thin client works the same way as Change Manager
in the rich client, with a slight variation of the user interface. You can create:
• Problem reports
• Change requests
• Change notices
• Deviation requests
Change Manager is not listed in the navigation bar. To open Change Manager
in the thin client, select a change object, such as a problem report. If there
are no change objects available, you must first create a change object.

23.5.1 Working with change objects in the thin client
Any user can create a problem report. Initially, only members of the dba
group can create change requests or change notices.
However, your administrator can configure which users can create the
various change objects using groups and roles along with conditions in the
Business Modeler IDE to configure which change objects can be created by
authorized users.
You can create a change object three different ways:
• Independently
• In the context of an impacted or problem item revision
• Derived from another change object; only ECRs and ECNs can be created
this way

23.5.2 Create a problem report in the thin client
1. (Optional) Select the item revision that you want to create a problem
report for.
2. If you selected an item revision, choose New®Change® Create In

Context.
Otherwise, choose New®Change® Create.
3. In the Type list, select Problem Report.
4. Click Next or click the General Information tab.


You can also type a problem report ID and revision in the PR Number
6. Click Finish.

23.5.3 Create a change request in the thin client
1. (Optional) Select the item revision that you want to create a change
request for.
2. Create the change request in one of the following ways:

• Choose New®Change® Create.
• Select an item revision and choose New®Change® Create In

Context.
• Select one or more problem report revisions and choose

New®Change® Derive Change.
The problem report revisions must have their properties set to:
Property Must be
Maturity Reviewing
Closure Open
Your administrator can configure which change object you can derive
from the problem report revision.
3. In the Type list, select Change Request.


You can also type a change request ID and revision in the ECR Number
6. Click Finish.

23.5.4 Create a change notice in the thin client
1. (Optional) Select the item revision that you want to create a change
notice for.
2. Create the change notice in one of the following ways:

• Choose New®Change® Create.
• Select an item revision and choose New®Change® Create In

Context.
• Select one or more change request revisions and choose

New®Change® Derive Change.
The change request revisions must have their properties set to:
Property Must be
Maturity Reviewing
Closure Open
Your administrator can configure which change object you can derive
from the change request revision.
3. In the Type list, select Change Notice.


You can also type a change notice ID and revision in the ECN Number
6. Click Finish.

23.5.5 Assign participants in the thin client

Note
• To use the Assign Participants menu command to assign review
members based on their roles, a workflow must be configured to
use dynamic participants.
For information about how your company’s change management
workflows are configured, see your workflow administrator.
• You must have permission to assign participants.

For information about your permissions, see your workflow
administrator.
1. In your home page, double-click the change object that you want to assign
participants to.
The object appears in Change Manager.
2. Choose Tools→Assign Participants.
3. In the Assign Participants dialog box, click the Users button next to
the participant type (for example, Analyst) to assign a user.

4. In the Participant Users dialog box, select a group, role, and user from
the respective lists and click Add.
To select users from a project team, select the Select members from
Project Team check box.
5. To remove a user as a participant, select the user in the Selection list

and click Remove.
6. When you are done selecting the user for that participant type, click OK.
7. Repeat step 4 for all participant types that you want to assign users to.
8. After you finish assigning participants, click OK in the Assign

Participants dialog box.

23.5.6 View BOM changes, supersedures, and genealogy in the thin client
1. Select the change object that you want to view.

You cannot update change requests or change notices in the thin client.
2. Click the BOM Changes tab to view the BOM changes. You cannot make
changes to the information in this tab from the thin client.
Problem reports do not have BOM changes, so this tab is not visible for
problem reports.
3. Click the Supersedures tab to view the supersedure. You cannot make
changes to the information in this tab from the thin client.
Problem reports do not have supersedures, so this tab is not visible for
problem reports.
4. Click the Supersedures tab, then click the supersedure line, and click the
Show Genealogy button to view the genealogy.
The genealogy is displayed in a new browser.

23.6 Managing your workflow tasks

Use your worklist to view workflow jobs and task information.
Your worklist page includes:
• Your own user worklist.
• Any remote worklists.
• Resource pools worklists to which you are subscribed.
Each worklist includes three lists:

• Tasks to Perform
Any tasks you are assigned appear in the Tasks to Perform list of the
appropriate worklist. Once the completion criteria of a task are met (for
example, the required quorum of approvals for a Perform Signoff task are
granted), the task is complete and is removed from the list.
• Tasks to Track
If you initiate a process but are not responsible for the currently active
task, Teamcenter places the task in the Tasks to Track list of the
appropriate worklist. When the completion criteria of the task are met,
the task is complete and is removed from the list.
• Schedule Tasks
Any nonworkflow schedule tasks that you are assigned appear in this list.
Schedule tasks in a workflow that you are assigned appear in either the
Tasks to Perform or Tasks to Track list.

23.6.1 Using worklists
Tasks assigned to you are listed in your worklist, including any unviewed
tasks for resource pools to which you are subscribed.
If another user assigns you a task, you generally receive E-mail notification
from Teamcenter. You can open the assignment from your worklist and
perform the assigned work.
• When you finish your work, you sign off the assignment or reassign it
to another user.
A task can remain in your worklist if it is in an incomplete state; such
a task may be incomplete because other assignees have not completed
their tasks.
• When you have an assigned task that you have not completed, a link to
the task is displayed in the Tasks to Perform list.
o Click the link to go to the task action page; for example, clicking a
Perform Signoffs link takes you to the signoff page.
o Click the + button to view items such as documents that are attached
to the assignment.
Gordon, Jack (jgordon) Inbox

Tasks to Perform
perform-signoffs
Author Technical Recommendation
Tasks to Track
Schedule Tasks
Note
New (unviewed) tasks are shown in bold type
• When you complete an assignment, but other assignees have not

completed their tasks, the task is move to the Tasks to Track list.
o Click the link to view the current status of the task.
The task is removed from your the Tasks to Track list when all
assignees have completed their work.

Note
Teamcenter lets administrators modify workflow processes as they are
running.
• Modifications to the workflow do not take effect when the
modifications relate to an active task currently in your worklist.
• Modifications to the workflow do take effect when a workflow

process returns later to a modified task (for example, by a backward
branch or a demoted task).

23.6.2 Performing interactive tasks
You can use workflow to complete assigned interactive tasks. For example,
you can review and approve a change to a product or process.
• You use your My Worklist inbox to complete tasks assigned to you,
including those originating at a remote site, and you can use and manage
address lists and resource pools. For example, you can perform a
select-signoff-team task.
• You can also complete tasks using the Workflow Viewer.
Interactive tasks are displayed in your Tasks to Perform folder.
Gordon, Jack (jgordon) Inbox

Tasks to Perform
perform-signoffs
Targets
000002/A;1–Item2
References
Tasks to Track

23.6.3 Selecting members of the signoff team
If you are assigned a Select Signoff task, you select users as members of a
signoff team.
• Signoff team members are assigned the responsibility of signing off a
target object, such as a document
• You can assign signoff responsibility to an entire address list or resource

pool of users, as well as individual users.
The user who initiates the workflow process must select a signoff team. As
the process progresses, a Select Signoff task appears in the Tasks to Perform
list of the process initiator’s worklist each time a task requiring a signoff team
reaches a Started state. There are two tasks that require signoff teams:
• Route task
• Review task
You can assign signoff responsibility by completing predefined profiles or by

ad hoc selection.

23.6.4 View a workflow process
Use the process viewer to examine the status of a workflow process and its
constituent tasks graphically. The tasks are color-coded, allowing you to
easily identify the state of each task. Process flow lines connect the tasks and
are also color-coded.
Note
The process viewer requires that the Adobe Flash Player is installed on
your workstation. The process viewer is supported by Scalable Vector
Graphics (SVG) Web for Internet Explorer and by native SVG for the
Firefox and Safari browsers.
The process viewer uses the following color and graphical conventions to
depict the state of the tasks:
• Workflow process tasks are color-coded to indicate their current state, as

follows:
o Gray indicates a pending state.
o Yellow indicates a started state.
o Green indicates a skipped or completed state.
Your administrator may changes these default color settings by editing

the appropriate style sheet.

• A line runs through each task and is color-coded to indicate the state of
each task, as follows:
o A green line indicates the task is completed.
o A gray line indicates a task that is not yet completed.
Your administrator may changes these default color settings by editing

• When you select a workflow task in the process viewer, it is outlined in

blue in the process viewer and (at the same time) selected in the worklist.
Conversely, when you select a task in the worklist, it is selected in the
process viewer.
Your administrator may change the default blue color setting by editing
1. Open the process viewer in one of the following ways:

• Select the box to the left of the task from the Tasks to Track list
or the Tasks to Perform list on the worklist page, and choose
View→Workflow Process.
• Click the job name in the task row.
The workflow process opens in the process viewer window at the bottom
of the worklist page.

2. Change the view of the workflow process as follows:

• View a subtask within the main task by selecting a subtask in the
process viewer and choosing View→Sub-Task.
The selected subtask enlarges within the process viewer.
• Change the size of the view by right-clicking within the viewer. From
the menu, you can choose to zoom in, zoom out, or show the entire
process.
Note
Some viewers do not allow the right-click menu. Use the
View→Sub-Task menu to zoom into a task and View→Sub-Task
Parent to zoom out.
If your viewer allows, you can use the Alt key to move the
process and the Ctrl key to zoom into a selected area.
3. Complete a task or subtask by clicking the relevant box and choosing

Actions→Perform.

23.7 Activities
In the Working in the Teamcenter thin client section, do the following
activities:
• Start the thin client and search for an item.
• Create a new item in the thin client.

23.8 Summary
• Using the thin client to navigate to various Teamcenter objects and
functions
• Managing your thin client interface
• Searching in the thin client
• Creating or revising items or item revisions and performing basic data

management tasks in the thin client
• Managing change in the thin client
• Using workflows in the thin client

Lesson
24 Course summary
Course objectives
The overall objectives of this course were to learn the basics of using
Teamcenter and the most commonly used Teamcenter software perspectives.
• To learn the basic concepts of product lifecycle management.
• To use Teamcenter to perform basic user tasks.
• To create and work with Teamcenter items and item revisions.
• To organize, manage, and secure product data.
• To use various navigation methods to locate, view, and report on product

data.
• To use the Structure Manager application to view, build, and edit product
structure.
• To navigate the classification hierarchy and use standard product data in

product structures.
• To use the embedded viewer to locate and view visualization data.
• To use Workflow Viewer to assign tasks, perform tasks, and track the
completion of tasks in a workflow process.
• To use Change Manager to create change objects and track a change

object through the change process to completion.
• To use the thin client to manage and navigate to various Teamcenter

objects and functions.

Appendix
A Managing views, layouts, and

view networks
Purpose
The basics of managing views, layouts, and view networks are taught in
this lesson.
Objectives
• Recognizie primary and secondary views.
• Change view network color presentation.
• Display and move a view in rich client.
• Change the view association.
• Hide and display views and view folders.
Help topics
Using Teamcenter A-1

Managing views, layouts, and view networks
A.1 Managing views, layouts, and view networks

In the rich client, a view is always displayed in the context of a perspective.
Each perspective always displays one or more views.
For example, by default, in My Teamcenter , the Home component view

is displayed in a view folder to the right of the navigation pane, and the
Summary, Details, Impact Analysis, and Viewer views are displayed in a
view folder to the right of the Home component view.
Note
You can open additional views of the same type by right-clicking the
object and choosing Open With.
• A layout is the arrangement of the views and view folders in a perspective.

Each perspective has a default layout.
o You can rearrange the views in a perspective and add or remove views
to create new layouts.
o You can save new layouts and redisplay them later.

Each layout has a current state and a saved state.
• A view folder is set of one or more views displayed in a specific area in the
Teamcenter window.
A-2 Using Teamcenter MT25150_S_101

For example, by default, My Teamcenter displays component views in a

view folder immediately to the right of the navigation pane. A second view
folder contains the Summary, Details, Impact Analysis, and Viewer views.
Moving a view to a new area, such as the bottom of the window, creates a
new view folder in that location. You can move views between view folders.
• A view network consists of a primary view and one or more secondary

views that are associated. View networks can be arranged in a single view
folder or in multiple view folders.
• You associate a secondary view with a primary view by choosing Associate

from the view menu and choosing a primary view.
• A primary view, such as a component view, lets you make selections that
cause other views to react.
For example, a Teamcenter component view displays a hierarchical view
of lists of objects and their attachments. When you select an object, such
as an item revision, a secondary view reacts by displaying information
relevant to the selection in the primary view. Secondary views can be
associated with a primary views.
• A secondary view, such as a Details or Summary view, displays information

relevant to the selection in a primary view.
o An associated secondary view reacts to a single, specific primary view
in a view network. You can change a view association by choosing
Associate from the view menu and choosing None or a different
primary view.
o A secondary view associated with a specific primary view reacts to the

current selection in that primary view. The associated view closes
automatically when its primary view is closed.
o Depending on the particular views involved, a secondary view can also

react to other secondary views in its network.
o A secondary view not associated with a specific primary view reacts to

the selection in the most recently selected primary view.

Note
View tab tooltips indicate:
• The root selection in a primary view.
• The source primary view for a secondary view.

A.1.1 Recognizing primary and secondary views

A primary view has a distinctive border color. This border color is also
displayed by all secondary views that display content based on the primary
view.
Note
To open an additional view, such as a second or third Summary view to
use in a view network, select an object in a component view and then
use the shortcut menu Open with command.
A currently selected view has a dark background tab and a distinctive color
border.
• When a secondary view is not associated with a specific primary view,
that secondary view:
o Displays content based on the currently selected primary view.
o Has a border the same color as the primary view to which it is reacting.
o Has a dashed-line border at the top of the view tab.
• When a secondary view is associated with a specific primary view, that

secondary view:

o Displays content based only on the primary view with which it is

associated.
o Has a solid-line border at the top of the view tab.
Object selection in one view can change the selection in another view.
• Selecting an object in a primary view changes the displayed information
in currently related secondary views.
• Selecting an object in a secondary view may change the selection in a

related primary view, if the object selected in the secondary view is
currently visible in the primary view.
• Selecting an object in a primary view may change the selection in other

primary views, if the object selected in the first primary view is also
already displayed in the other primary views.

A.1.2 Changing view network color presentation
Choose Window®Preferences®View Network Presentation®Teamcenter to

display the color control options for view networks.
You can specify 12 sets from 156 color and pattern options.
Each set is used in turn as you create new view networks.

A.1.3 Display and move a view in the rich client

This procedure uses the example of opening and moving the Image Thumbnail
Preview view in the My Teamcenter perspective.
1. With the My Teamcenter application open, choose Window→Show
View→Image Thumbnail Preview.
The Image Thumbnail Preview view appears in the My Teamcenter
perspective.
2. Click the Image Thumbnail Preview tab. Do not release the mouse button.
3. Move the mouse to drag the tab to another area in the perspective or
outside the Teamcenter window entirely.
Note
The stack cursor appears as you drag the view across other
view tabs.
4. Release the mouse button to drop the view in the desired location.
As you move the view around the current perspective, the mouse pointer
changes to the appropriate drop cursor to indicate where the view is
docked when you release the mouse button.
You can resize views in a perspective by dragging the border between
the views.
If you select a location where the is no view folder yet, a new view folder is
created.
Note
If a view is moved outside the Teamcenter window, you can click
and drag the view tab into the application perspective to return it to
the Teamcenter window.
Drop
cursor Description
The view is placed at the top of the window.
The view is placed at the bottom of the window.
The view is placed on the left side of the window.
The view is placed on the right side of the window.
The view is placed in the stack of views in the current area.

Drop
cursor Description
The view is detached and moved outside the Teamcenter
window.
The view cannot be placed in the current area.
Note
On most systems, you can use the Move shortcut menu command to
move a view, or the Detached shortcut menu command to open a view
in its own window.

A.1.4 Change the view association
Do one of the following:

• In the secondary view, click the Associate button and select the view to
which you want to associate the secondary view from a list of all primary
views currently open.
o If you activate the Disable response to selections button , the
Associate button is not available.
o If the Disable response to selections button is not available (if

the secondary view is responding to selections), when you change
selection, the secondary view changes its content based on that new
selection in these cases:
The secondary view is not associated to any view.
The secondary view is associated to the active view (where the

selection change occurred).
The secondary view and the active view (where the selection
change occurred) are both associated to the same primary view.
• Select the line in the primary view to which you want to associate the
secondary view, and click the Set input to recent selection button to
set the scope for a secondary view.
You can use the Set input to recent selection button from any view,
regardless of the association state.
o If you set the scope from the primary view to which the secondary view
is associated, the secondary view is still associated to that primary
view.
o If the secondary view is not associated to any primary view when you
set the scope, Teamcenter performs no association.
o If the secondary view is associated to primary view A and you set

the scope from primary view B, the secondary view is associated to
primary view B.
Teamcenter associates the secondary view with the selected primary view.

A.1.4.1 Associate views
• Click Associate and select an object in the list.

This secondary view is associated to the selected object in the primary
view.

A.1.4.2 Disable and enable response to selection
1. Click Disable response to selection .

The secondary view does not change when you select a different object
in the primary view.
2. Click Enable response to selection .

The secondary view changes when you select a different object in the
primary view.

A.1.4.3 Set input to recent selection
• Click Set input to recent selection .

The secondary view changes to the currently selected object in the primary
view even if you have disabled the response to the selection.

A.1.5 Hide and display views and view folders
You can manage visibility of views and view folders.

• Click the view folder menu Show List to display all the views in a view
folder. Currently hidden views are indicated by bold text.
• To control visibility of individual views, use the Fast View command in

view tab shortcut menu.
This puts a Fast View button representing the view in the bottom border
of the Teamcenter window.
o Click the Fast View button to redisplay or hide the view temporarily.
o Right-click the button and clear the Fast View command to restore the
view to its original view folder and location.

• To control visibility of an entire view folder, use the view folder Minimize,
Restore, and Maximize commands.
The Minimize and Maximize commands are available in the upper-right
corner of the view folder, to the right of the view tab area, and in the
view folder tab bar shortcut menu.
The Restore command is available when a view folder is maximized or
minimized.

A.2 Managing views, layouts, and view networks

• Recognizing primary and secondary views
• Changing view network color presentation
• Displaying and moving a view in rich client
• Changing the view association
• Hiding and displaying views and view folders

Index
A Assembly structures
Abstract class symbol . . . . . . . . . . . 15-7 Change between precise and
Abstract classes . . . . . . . . . . . . . . . 15-9 imprecise . . . . . . . . . . . . . . . 10-15
Access control entries (ACEs) Precise/Imprecise . . . . . . 10-10–10-11
Adding . . . . . . . . . . . . . . . . . . . . 6-26 Revising . . . . . . . . . . . . . 10-13–10-14
Modifying . . . . . . . . . . . . . . . . . . 6-28 Assigned work, finding . . . . . . . . . 23-26
Access control entry (ACE) . . . . . . . 6-22 Assigning
Access control list (ACL) . . . . . . . . 6-22 Effectivity . . . . . . . . . . . . . . . . 22-11
Access privileges Objects to projects . . . . . . . . . . . 8-10
Example of viewing . . . . . . . . . . 6-25 Participants . . . . . . . . . . . . . . . 21-13
Viewing . . . . . . . . . . . . . . . . . . . 6-24 Participants in the thin client . . 23-47
ACE (access control entry) . . . . . . . 6-22 Assigning related objects to
ACL (access control list) . . . . . . . . . 6-22 projects . . . . . . . . . . . . . . . . . . . . 8-13
Active unit . . . . . . . . 15-19, 15-34–15-35 Associate secondary view to primary
Ad hoc view . . . . . . . . . . . . . . . . . . . . . . . A-11
Revision rule setting . . . . . . . . . . 10-8 Attribute values
Add a new Instance to the Current object Modify ICO . . . . . . . . . . . . . . . . 15-23
button . . . . . . . . . . . . . . . . . . . . 15-21 Authorized data access . . . . . . 6-29–6-30
Adding autoAssignToProject
Access control entries (ACEs) . . . 6-26 extension . . . . . . . . . . . . . . . 8-16–8-17
Advanced search . . . . . . . . . . . . . . 7-15 Autofilter . . . . . . . . . . . . . . . . . . . 15-15
Alias identifiers . . . . . . . . . . . . . . . 3-26 Automatically assigning data to projects
Alternate identifiers . . . . . . . . . . . . 3-27 autoAssignToProject extension . . 8-16
Analyst Eligible data types . . . . . . . . . . . 8-16
Assigning . . . . . . . . . . . . . . . . . 20-13
Application banner . . . . . . . . . . . . . 1-7 B
Applications Back and forward buttons . . . . . . . . 1-7
Configuring display of . . . . . . . . . 1-22 Background color
Display as primary . . . . . . . . . . . 1-23 Product structure . . . . . . . . . . . 10-12
Display as secondary . . . . . . . . . 1-23 Basic concepts . . . . . . . . . . . . . . . . . 1-3
Primary . . . . . . . . . . . . . . . . . . . 1-23 Product visualization . . . . . . . . . 1-16
Secondary . . . . . . . . . . . . . . . . . 1-23 Workflow . . . . . . . . . . . . . . . . . . 1-16
Approved state . . . . . . . . . . . . . . . 20-28 Basic concepts of Extensions for
Assembly Office . . . . . . . . . . . . . . . . . . . . . 19-27
Collapse . . . . . . . . . . . . . . . . . . . 9-18 Basic tasks . . . . . . . . . . . . . . 1-4, 20-14
Expand . . . . . . . . . . . . . . . . . . . 9-17 Basic tasks, My Teamcenter . . . . . . . 2-3
Assembly structure Best practices
Background color . . . . . . . . . . . 10-12 Effectivity . . . . . . . . . . . . . . . . 10-24
Using Teamcenter Index-1

Index
BOM changes . . . . . . . . . . . . . . . 23-49 Executing . . . . . . . . . . . . . . . . . 20-38

BOM Changes tab . . . . . . . . . . . . . 20-4 Change objects
BOM line About managing . . . . . . . . . . . . . 21-9
Quantity . . . . . . . . . . . . . . . . . . 12-7 authorization . . . . . . . . . . . . . . . 21-2
BOM view revision . . . . . . . . . . . . . . 9-6 creating . . . . . . . . . . . . . . . . . . . 21-2
icon . . . . . . . . . . . . . . . . . . . . . . . 9-6 Finding . . . . . . . . . . . . . . . . . . 20-37
BOM view types . . . . . . . . . . . . . . . . 9-7 Relationship between . . . . . . . . 20-10
Box, Search Results . . . . . . . . . . . 15-37 Thin client . . . . . . . . . . . . . . . . 23-40
Browse product structure . . . . . . . . . 9-3 Types of . . . . . . . . . . . . . . . . . . . 20-8
Build and edit structures . . . . . . . . . 9-3 Change requests, see Enterprise change
Business object type requests
Search . . . . . . . . . . . . . . . . . . . . 7-13 Change review board
Buttons Assigning . . . . . . . . . . . . . . . . . 20-13
Add a new Instance to the Current Change specialist
object . . . . . . . . . . . . . . . . . 15-21 Assigning . . . . . . . . . . . . . . . . . 20-13
Cancel . . . . . . . . . . . . . . . . . . . 15-24 Change states
Clipboard . . . . . . . . . . . . . . . . . 15-19 Closure . . . . . . . . . . . . . . 20-25–20-26
Edit . . . . . . . . . . . . . . . . . . . . . 15-24 Disposition . . . . . . . . . . . 20-25–20-26
Relate Solution Item to Impacted Examples of . . . . . 20-30, 20-32, 20-34
Item . . . . . . . . . . . . . . . . . . . 22-6 Maturity . . . . . . . . . . . . 20-25–20-26
Save . . . . . . . . . . . 15-19, 15-21, 15-24 Changes
View Mode . . . . . . . . . . . . . . . . 15-38 Managing . . . . . . . . . . . . . . . . . . 21-9
Relating items to . . . . . . . . . . . 21-10
C Check in an object . . . . . . . . . . . . . 6-14
Check out an object . . . . . . . . . . . . 6-11
Cancel button . . . . . . . . . . . . . . . 15-24 Check-Out and Edit button . . . . . . . 4-3
Cancel checkout requests . . . . . . . . 6-17 Checkin
Cancelled state . . . . . . . . . . . . . . 20-27 Client for Office . . . . . . . . . . . . 19-12
Change Checkin and checkout, data . . . . . . . 6-8
Search . . . . . . . . . . . . . . . . . . . . . 7-5 Checkout
Change administrator Cancel . . . . . . . . . . . . . . . . . . . . 6-17
Assigning, see Change specialist Client for Office . . . . . . . . . . . . 19-12
Change Effectivity tab . . . . . 20-4, 22-11 Defining checkout directory . . . . . 6-9
Change home . . . . . . . . . . . . . . . . 20-39 Differences between implicit and
Change Home view . . . . . . . 20-3, 20-36 explicit . . . . . . . . . . . . . . . . . 6-10
Change implementation board Explicit . . . . . . . . . . . . . . . . . . . . 6-9
Assigning . . . . . . . . . . . . . . . . . 20-13 Implicit . . . . . . . . . . . . . . . . . . . 6-10
Change Manager Transferring . . . . . . . . . . . . . . . . 6-16
Basic tasks . . . . . . . . . . . . . . . . 20-14 Checkout history . . . . . . . . . . . . . . 6-18
data objects . . . . . . . . . . . . . . . . 20-7 Class scope . . . . . . . . . . . . . . . . . 15-34
Change Managerl Classes
Basic concepts . . . . . . . . . . . . . . 20-5 Abstract . . . . . . . . . . . . . . . . . . . 15-9
Change notices, see Enterprise change SML . . . . . . . . . . . . . . . . . . . . . . 15-7
notices Storage . . . . . . . . . . . . . . . . . . . . 15-9
Change object searches Classic variants
Deleting . . . . . . . . . . . . . . . . . . 20-38 Creating basic data . . . . . . . . . . . 13-4
Index-2 Using Teamcenter MT25150_S_101

Index
Example . . . . . . . . . . . . . . . . . . . 13-3 Navigate to a specific ICO . . . . . 15-37

Explanation . . . . . . . . . . . . . . . . 13-2 Classify
Classification Teamcenter objects . . . . . . . . . . 15-18
Basic concepts . . . . . . . . . . . . . . 15-3 Clauses
Classifying Teamcenter objects . . 15-9 Group . . . . . . . . . . . . . . . . . . . . 13-18
Copy classification objects . . . . . 15-42 Insert . . . . . . . . . . . . . . . . . . . . 13-15
Find a class . . . . . . . . . . . . . . . 15-31 Move . . . . . . . . . . . . . . . . . . . . 13-17
Find an ICO in selected class . . 15-34 Remove . . . . . . . . . . . . . . . . . . 13-16
Find ICO in selected class . . . . . 15-35 Replace . . . . . . . . . . . . . . . . . . 13-16
Getting started . . . . . . . . . . . . . . 15-2 Client for Office
Panes . . . . . . . . . . . . . . . . . . . . . 15-6 Basic tasks . . . . . . . . . . . . . . . . . 19-5
Paste classification objects . . . . 15-42 Browse . . . . . . . . . . . . . . . . . . . . 19-6
Quick search . . . . . . . . . . . . . . 15-33 Checkin . . . . . . . . . . . . . . . . . . 19-12
Reuse classification objects . . . . 15-42 Checkout . . . . . . . . . . . . . . . . . 19-12
Search . . . . . . . . . . . . . . . . . . . 15-27 Create objects . . . . . . . . . . . . . . . 19-7
Search buttons . . . . . . . . . . . . . 15-26 Current settings . . . . . . . . . . . . 19-15
Search by object type . . . . . . . . 15-28 Dataset types . . . . . . . . . . . . . . . 19-3
Search, apply revision rule . . . . 15-29 Initiate workflow . . . . . . . . . . . 19-21
Symbols . . . . . . . . . . . . . . . . . . . 15-7 Insert data . . . . . . . . . . . . . . . . 19-13
Tasks . . . . . . . . . . . . . . . . . . . . . 15-4 Interface . . . . . . . . . . . . . . . . . . 19-4
Classification dialog box . . . . . . . . 15-21 Introduction . . . . . . . . . . . . . . . . 19-2
Classification hierarchy Markups . . . . . . . . . . . . . . . . . 19-14
Display a subset . . . . . . . . . . . . 15-11 Open dataset . . . . . . . . . . . . . . 19-10
Display in Properties pane . . . . 15-14 Perform a task . . . . . . . . . . . . . 19-24
Displaying . . . . . . . . . . . . . . . . 15-10 Search . . . . . . . . . . . . . . . . . . . . 19-9
Set node as root . . . . . . . . . . . . 15-12 Synchronize tasks . . . . . . . . . . . 19-23
Viewing the tree graphically . . . 15-17 Task assignments . . . . . . . . . . . 19-22
Classification object Update dataset . . . . . . . . . . . . . 19-12
Active unit of measurement . . . 15-39 Workflow . . . . . . . . . . . . . . . . . 19-20
Finding . . . . . . . . . . . . . . . . . . 15-25 Clipboard
Revision . . . . . . . . . . . . . . . . . . 15-22 Pasting contents . . . . . . . . . . . . . 2-25
Searching the classification Clipboard button . . . . . . . . . . . . . 15-19
hierarchy . . . . . . . . . . . . . . . 15-30 Description . . . . . . . . . . . . . . . . . . 1-8
Classification object (ICO) Closed state . . . . . . . . . . . . . . . . . 20-27
Classify multiple times . . . . . . . 15-20 Closing search results . . . . . . . . . . 7-23
Create . . . . . . . . . . . . . . . . . . . 15-19 Closure change state . . . . . 20-25–20-26
Classification objects Cancelled . . . . . . . . . . . . . . . . . 20-27
Creating . . . . . . . . . . . . . . . . . . 15-19 Closed . . . . . . . . . . . . . . . . . . . 20-27
Creating multiple instances . . . 15-21 On hold . . . . . . . . . . . . . . . . . . 20-27
Classification Properties pane Open . . . . . . . . . . . . . . . . . . . . 20-27
Image viewers . . . . . . . . . . . . . 15-41 Column configurations, properties
Classification search results Managing . . . . . . . . . . . . . . . . . . 9-15
Navigating . . . . . . . . . . . . . . . . 15-36 Column display
View in Properties pane . . . . . . 15-38 Table columns . . . . . . . . . . . . . 23-14
View in Table pane . . . . . . . . . . 15-40 Columns . . . . . . . . . . . . . . . . . . . 23-14
Classification Search Results box Repositioning . . . . . . . . . . . . . . . 4-18

Index
Compare product structures . . . . . . . 9-3 Creating change requests in the thin

Compare search results . . . . . . . . . 7-24 client . . . . . . . . . . . . . . . . . . . . . 23-43
Comparing Creating datasets . . . . . . . 5-4, 5-9, 5-18
Search results . . . . . . . . . . . . . . 7-24 Creating problem reports in the thin
Complete state . . . . . . . . . . . . . . . 20-27 client . . . . . . . . . . . . . . . . . . . . . 23-41
Component Creating workflow
Find by property . . . . . . . . . . . . 11-10 subprocesses . . . . . . . . . . 17-11–17-12
Finding . . . . . . . . . . . . . . . . . . . 11-9 Cutting objects from the
Component pane . . . . . . . . . . . . . . 23-6 workspace . . . . . . . . . . . . . . . . . . 2-22
Components
Paste . . . . . . . . . . . . . . . . . . . . 11-20 D
Replacing . . . . . . . . . . . . . . . . . 11-24 Dashboard
Concepts Reporting and Analytics . . . . . . . 7-37
Live Excel . . . . . . . . . . . . . . . . 19-27 Data
Conditions Checkin and checkout . . . . . . . . . . 6-8
Create . . . . . . . . . . . . . . . . . . . 13-10 Data model . . . . . . . . . . . . . . . . . . . 3-3
Modifying . . . . . . . . . . . . . . . . . 13-14 Data pane . . . . . . . . . . . . . . . . . . . 23-7
Configure Applications button . . . . 1-14 Database
Configure Applications menu . . . . . 1-22 Searching by advanced
Configure variant products . . . . . . . . 9-3 criteria . . . . . . . . . . . . . . . . 23-21
Configuring table panes . . . . . . . . . 4-15 Searching by simple item
Configuring view tables . . . . . 4-15–4-16 criteria . . . . . . . . . . . . . . . . 23-20
Contents menu . . . . . . . . . . . . . . 15-19 Searching for items . . . . . . . . . . 23-19
Copy item . . . . . . . . . . . . . . . . . . 11-17 Database objects
Copy item revision . . . . . . . . . . . . 11-17 Reference . . . . . . . . . . . . . . . . . . 2-20
Copying objects . . . . . . . . . . 2-23, 11-16 Dataset
Create Attaching named reference . . . . 23-35
Folder . . . . . . . . . . . . . . . . . . . . . 2-10 Creating . . . . . . . . . . . . . . . . . . 23-33
Supersedure . . . . . . . . . . . . . . . . 22-8 Named references . . . . . . . . . . . . 5-11
Create Classification Object dialog Object behavior . . . . . . . . . . . . . . 5-2
box . . . . . . . . . . . . . . . . . . . . . . . 15-19 Objects . . . . . . . . . . . . . . . . . . . . . 5-2
Create objects Versions . . . . . . . . . . . . . . . . . . . 5-16
Client for Office . . . . . . . . . . . . . 19-7 Datasets
Creating Create by drag and drop . . . . . . . . 5-9
Classification objects . . . . . . . . 15-19 Create by menu commands . . . . . . 5-4
Datasets . . . . . . . . . . . . . . . 5-3, 23-33 Create by Save As . . . . . . . . . . . . 5-18
Enterprise change notices . . . . . . 21-7 Creating . . . . . . . . . . . . . . . . . . . . 5-3
Enterprise change requests . . . . . 21-5 Date effectivity . . . . . . . . . . . . . . 10-20
Folders . . . . . . . . . . . . . . . . . . . 23-27 Deferred state . . . . . . . . . . . . . . . 20-28
Items . . . . . . . . . . . . . . . . . 3-8, 23-28 Defining
Multiple classification objects . . 15-21 Checkout directory . . . . . . . . . . . . 6-9
Problem reports . . . . . . . . . . . . . 21-3 Delete
Work breakdowns . . . . . . . . . . . 21-15 Folder . . . . . . . . . . . . . . . . . . . . . 2-15
Creating change notices in the thin Deleting objects . . . . . . . . . . . . . . . 2-21
client . . . . . . . . . . . . . . . . . . . . . 23-45 Detach a view . . . . . . . . . . . . . . . . . A-9
Details tab . . . . . . . . . . . . . . . . . . . 20-4

Index
Deviation requests Creating in the thin client . . . . . 23-43

About . . . . . . . . . . . . . . . . . . . . . 20-8 Example change states in fast
Relationships to other objects . . 20-10 track . . . . . . . . . . . . . . . . . . 20-30
Dialog boxes Example change states in standard
Classification . . . . . . . . . . . . . . 15-21 track . . . . . . . . . . . . . . . . . . 20-32
Create Classification Object . . . 15-19 Example process . . . . . . . 20-20–20-21
New item . . . . . . . . . . . . . . . . . . . 3-5 Relating items to . . . . . . . . . . . 21-10
Search Class . . . . . . . . . . 15-30, 15-33 Relationships to other objects . . 20-10
Differences between implicit and explicit Examples of
checkout . . . . . . . . . . . . . . . . . . . 6-10 change states . . . . 20-30, 20-32, 20-34
Disable response to selection . . . . . A-12 Excel
Disapproved state . . . . . . . . . . . . 20-28 Live Excel
Displaying Basic concepts . . . . . . . . . . 19-27
Search results . . . . . . . . . . 7-18, 7-21 Exclude licenses . . . . . . . . . . . . . . . 6-30
Disposition change state . . 20-25–20-26 Executing state . . . . . . . . . . . . . . 20-27
Approved . . . . . . . . . . . . . . . . . 20-28 Explicit checkout . . . . . . . . . . . . . . . 6-9
Deferred . . . . . . . . . . . . . . . . . . 20-28 Explore dialog box . . . . . . . . . 6-12, 6-14
Disapproved . . . . . . . . . . . . . . . 20-28 Explore Selected Components
Investigate . . . . . . . . . . . . . . . . 20-28 option . . . . . . . . . . . . . . . . . 6-12, 6-14
None . . . . . . . . . . . . . . . . . . . . 20-28 Extensions for Office
Drag and drop data . . . . . . . . . . . . 2-28 Basic concepts . . . . . . . . . . . . . 19-27
Dynamic menus . . . . . . . . . . . . . . 23-16
F
E Fast track . . . . . . . . . . . . . 20-12, 20-16
Edit button . . . . . . . . . . . . . . . . . 15-24 Example process . . . . . . . . . . . . 20-20
Effectivity . . . . . . . . . . . . . . . . . . 20-16 Fast View command . . . . . . . . . . . . A-14
Assigning . . . . . . . . . . . . . . . . . 22-11 Favorites . . . . . . . . . . . . . . . . . . . . 1-14
Best practices . . . . . . . . . . . . . . 10-24 Rich client . . . . . . . . . . . . . 1-14, 2-16
Date . . . . . . . . . . . . . . . . . . . . . 10-20 Thin client . . . . . . . . . . . . . . . . . 2-16
Revision, display data . . . . . . . . 10-23 Favorites folder
Unit number . . . . . . . . . . . . . . 10-21 Rename . . . . . . . . . . . . . . . . . . . 2-18
Elaborating Find a class
Change objects . . . . . . . . . . . . . 21-10 Use Search Class dialog box . . . 15-31
Elaborating state . . . . . . . . . . . . . 20-27 Find classification object
Enable response to selection . . . . . . A-12 By attribute value . . . . . 15-34–15-35
Enterprise change notices . . . . . . 20-16 Search selected class . . . . . . . . . 15-34
About . . . . . . . . . . . . . . . . . . . . . 20-8 Find in display . . . . . . . . . . . . . . . 11-10
Creating . . . . . . . . . . . . . . . . . . . 21-7 Find numbers . . . . . . . . . . . . . . . . 11-4
Creating in the thin client . . . . . 23-45 Finding
Example change states . . . . . . . 20-34 Classification objects . . . . . . . . 15-25
Example process . . . . . . . . . . . . 20-23 ICOs . . . . . . . . . . . . . . . . . . . . 15-25
Relating items to . . . . . . . . . . . 21-10 Folder
Relationships to other objects . . 20-10 Create . . . . . . . . . . . . . . . . . . . . 2-10
Enterprise change requests . . . . . 20-16 Delete . . . . . . . . . . . . . . . . . . . . 2-15
About . . . . . . . . . . . . . . . . . . . . . 20-8 Home, Newstuff and Mailbox
Creating . . . . . . . . . . . . . . . . . . . 21-5 folders . . . . . . . . . . . . . . . . . . . 2-8

Index
Print . . . . . . . . . . . . . . . . . . . . . 2-14 Tasks to Perform list . . . . . . . . . 23-50

Rename . . . . . . . . . . . . . . . . . . . 2-12 Tasks to Track list . . . . . . . . . . 23-50
Folders Viewing a workflow process . . . 23-55
Creating . . . . . . . . . . . . . . . . . . 23-27 Information center, symbols . . . . . . 6-31
Impacted Items . . . . . . . . . 22-5–22-6 Information center, using . . . . . . . . 6-31
Solution Items . . . . . . . . . . 22-5–22-6 Initiate workflow
Working with . . . . . . . . . . . . . . . . 2-9 Client for Office . . . . . . . . . . . . 19-21
Form-based Interface . . . . . . . . . . . . . . . . . . . . 20-3
Search . . . . . . . . . . . . . . . . . . . . 7-15 Interfaces
Functionality not available in thin Rich client . . . . . . . . . . . . . . . . . . 1-7
client . . . . . . . . . . . . . . . . . . . . . . 23-5 Thin client . . . . . . . . . . . . . . . . . 23-6
Investigate state . . . . . . . . . . . . . 20-28
G IP licenses . . . . . . . . . . . . . . . . . . . 6-30
ITAR licenses . . . . . . . . . . . . . . . . . 6-30
Genealogy . . . . . . . . . . . . . . . . . . 23-49
Item
Getting started . . . . . . . . . . . . . . . 20-2
Relations . . . . . . . . . . . . . . . . . . 3-20
Global alternates . . . . . . . . 11-23, 11-30
Item identifiers, initial . . . . . . . . . . 3-25
Managing . . . . . . . . . . . . . . . . . 11-28
Item reports
Graph Overview view . . . . . . . 14-4, 14-9
Rich client . . . . . . . . . . . . . . . . . 7-42
Graphical comparison
Item revision display
Initiate . . . . . . . . . . . . . . . . . . . 12-14
Filtering . . . . . . . . . . . . . . . . . . . 3-29
Group
Item revisions
Rich client logon . . . . . . . . . . . . . 1-11
Copy . . . . . . . . . . . . . . . . . . . . . 11-17
Group symbol . . . . . . . . . . . . . . . . 15-7
Opening . . . . . . . . . . . . . . . . . . . 3-28
Paste . . . . . . . . . . . . . . . . . . . . 11-17
H
Item structure
Hierarchy scope . . . . . . . . . . . . . . 15-34 Objects . . . . . . . . . . . . . . . . . . . . . 3-3
History links . . . . . . . . . . . . . . . . . 1-14 Item types . . . . . . . . . . . . . . . . . . . . 3-4
Home folder . . . . . . . . . . . . . . . . . . . 2-8 Items
Copy . . . . . . . . . . . . . . . . . . . . . 11-17
I Creating . . . . . . . . . . . . . . . 3-8, 23-28
I Want To links . . . . . . . . . . . . . . . 1-14 Finding in database . . . . 23-19–23-21
Rich client . . . . . . . . . . . . . . . . . 1-14 Opening . . . . . . . . . . . . . . . . . . . 3-28
ICM root symbol . . . . . . . . . . . . . . 15-7 Paste . . . . . . . . . . . . . . . . . . . . 11-17
ICO Revising . . . . . . . . . . . . . 23-30, 23-32
Finding . . . . . . . . . . . . . . . . . . 15-25
Identifiers L
Alias . . . . . . . . . . . . . . . . . . . . . 3-26 Layout
Alternate . . . . . . . . . . . . . . . . . . 3-27 Saving . . . . . . . . . . . . . . . . . . . . 1-21
Attributes . . . . . . . . . . . . . . . . . . 3-25 Licenses
Image Preview view . . . . . . . . 14-4, 14-8 Exclude . . . . . . . . . . . . . . . . . . . 6-30
Impact Analysis tab . . . . . . . . . . . . 20-4 IP . . . . . . . . . . . . . . . . . . . . . . . . 6-30
Impacted Items folders . . . . . . 22-5–22-6 ITAR . . . . . . . . . . . . . . . . . . . . . 6-30
Implicit checkout . . . . . . . . . . . . . . 6-10 Live Excel
Inbox Basic concepts . . . . . . . . . . . . . 19-27
Schedule Tasks list . . . . . . . . . . 23-50 Basic tasks . . . . . . . . . . . . . . . . 19-28

Index
Export to Excel . . . . . . . . . . . . . 19-29 Single object properties . . . . . . . . . 4-8

Introduction . . . . . . . . . . . . . . . 19-26 Modifying single object . . . . . . . . . . 4-14
Update data . . . . . . . . . . . . . . . 19-31 Move
Load search results . . . . . . . . . . . . 7-21 Objects . . . . . . . . . . . . . . . . . . . . 2-13
Logon, Rich client . . . . . . . . . . . . . 1-11 Move a view . . . . . . . . . . . . . . . . . . . A-8
Moving data . . . . . . . . . . . . . 2-21, 2-28
M My Projects view
Mailbox Using . . . . . . . . . . . . . . . . . . . . . . 8-7
folder . . . . . . . . . . . . . . . . . . . . . . 2-8 My Teamcenter
Make where-used searches . . . . . . . . 9-3 Basic concepts . . . . . . . . . . . . . . . 2-2
Managing Basic tasks . . . . . . . . . . . . . . . . . . 2-3
Workflow tasks . . . . . . . . . . . . . 23-50 Open . . . . . . . . . . . . . . . . . . . . . 1-19
Managing change objects . . . . . . . . 21-9 Overview . . . . . . . . . . . . . . . . . . . 2-2
Marking up product structure My Teamcenter user interface . . . . . 2-4
Apply all markups . . . . . . . . . . 12-30
Apply markup . . . . . . . . . . . . . 12-28 N
Carrying forward markups . . . . 12-31 Named reference, attaching to
Comment on markup . . . . . . . . 12-27 dataset . . . . . . . . . . . . . . . . . . . . 23-35
Concepts . . . . . . . . . . . . . . . . . 12-23 Named references . . . . . . . . . . . . . 5-11
Create markup . . . . . . . . . . . . . 12-25 Modify . . . . . . . . . . . . . . . . . . . . 5-12
Delete markup . . . . . . . . . . . . . 12-32 View . . . . . . . . . . . . . . . . . . . . . . 5-12
Enabling . . . . . . . . . . . . . . . . . 12-24 Navigation
Review markup . . . . . . . . . . . . 12-27 Top navigation bar . . . . . . . . . . 23-11
Markups Navigation pane . . . . . . . . . . . 1-8, 23-6
Client for Office . . . . . . . . . . . . 19-14 Rich client . . . . . . . . . . . . . . . . . . 1-8
Maturity change state . . . . 20-25–20-26 New item dialog box . . . . . . . . . . . . . 3-5
Complete . . . . . . . . . . . . . . . . . 20-27 Newstuff folder . . . . . . . . . . . . . . . . 2-8
Elaborating . . . . . . . . . . . . . . . 20-27 Non-privileged project team
Executing . . . . . . . . . . . . . . . . . 20-27 member . . . . . . . . . . . . . . . . . . . . . 8-4
Reviewing . . . . . . . . . . . . . . . . 20-27 None state . . . . . . . . . . . . . . . . . . 20-28
Measurement unit . . 15-19, 15-34–15-35
Change active . . . . . . . . . . . . . . 15-16
O
Menu bar . . . . . . . . . . . . . . . . . 1-7, 23-6
Rich client . . . . . . . . . . . . . . . . . . 1-7 Object
Thin client . . . . . . . . . . . . . . . . . 23-6 Check in . . . . . . . . . . . . . . . . . . . 6-14
Menu commands Check out . . . . . . . . . . . . . . . . . . 6-11
Paste Special . . . . . . . . . . . . . . . 2-24 Object references . . . . . . . . . . . . . . 2-20
Menus Object-based protection . . . . . . . . . 6-22
Contents . . . . . . . . . . . . . . . . . 15-19 Objects
Dynamic . . . . . . . . . . . . . . . . . . 23-16 Copying . . . . . . . . . . . . . . 2-23, 11-16
Send To . . . . . . . . . . . . . . . . . . 15-19 Cutting . . . . . . . . . . . . . . . . . . . 2-22
Modify ICO Deleting . . . . . . . . . . . . . . . . . . . 2-21
Attribute values . . . . . . . . . . . . 15-23 Moving . . . . . . . . . . . . . . . . . . . . 2-21
Modifying Pasting . . . . . . . . . . . . . . . . . . . 11-16
Access control entries (ACEs) . . . 6-28 Printing . . . . . . . . . . . . . . . . . . . 4-23
Object properties . . . . . . . . . . . . 4-10 Objects in projects

Index
Find . . . . . . . . . . . . . . . . . . . . . . 8-23 Paste item . . . . . . . . . . . . . . . . . . 11-17

Occurrence notes Paste item revision . . . . . . . . . . . 11-17
View . . . . . . . . . . . . . . . . . . . . . . 12-4 Pasting
Occurrences Clipboard contents . . . . . . . . . . . 2-25
Attributes . . . . . . . . . . . . . . . . . 11-18 Pasting objects . . . . . . . . . . . . . . . 11-16
On hold state . . . . . . . . . . . . . . . . 20-27 Perform a task
Open Client for Office . . . . . . . . . . . . 19-24
My Teamcenter . . . . . . . . . . . . . . 1-19 Performing advanced searches . . . . 7-15
Open Change view . . . . . . . . . . . . . 20-3 Performing quick searches . . . . . . . 7-10
Open dataset Perspectives
Client for Office . . . . . . . . . . . . 19-10 Closing . . . . . . . . . . . . . . . . . . . . 1-21
Rich client . . . . . . . . . . . . . . . . 19-16 In general . . . . . . . . . . . . . . . . . . 1-18
Thin client . . . . . . . . . . . . . . . . 23-36 Opening . . . . . . . . . . . . . . . . . . . 1-19
Open items . . . . . . . . . . . . . . . . . . 1-14 Reset . . . . . . . . . . . . . . . . . . . . . 1-21
Open state . . . . . . . . . . . . . . . . . . 20-27 Saving . . . . . . . . . . . . . . . . . . . . 1-21
Open Task view . . . . . . . . . . . . . . . 20-3 Switch between open
Opening perspectives . . . . . . . . . . . . . . 1-20
Item revisions . . . . . . . . . . . . . . . 3-28 Precise/Imprecise
Items . . . . . . . . . . . . . . . . . . . . . 3-28 Product structures . . . . . . . . . . 10-10
Options Preferences
Change values . . . . . . . . . . . . . . 13-8 TC_Dataset_Import_Exclude_
Create . . . . . . . . . . . . . . . . . . . . 13-5 Wildcard . . . . . . . . . . . . . . . . . 5-3
Send To . . . . . . . . . . . . . . . . . . 15-19 Prefix property value . . . . . . . . . . . 4-12
Overview Prerequisites for Classification . . . . 15-2
My Teamcenter . . . . . . . . . . . . . . . 2-2 Previewing attribute values . . . . . 15-15
Primary application buttons . . . 1-8, 1-14
P Rich client . . . . . . . . . . . . . . . . . . 1-8
Primary applications . . . . . . . . . . . 1-23
Pack structure lines . . . . . . . . . . . . 12-5 Primary perspective buttons
Packing structure lines . . . . . . . . . 12-2 Rich client . . . . . . . . . . . . . . . . . 1-14
Page components, see Table rows Print
Panes Folder . . . . . . . . . . . . . . . . . . . . . 2-14
Classification . . . . . . . . . . . . . . . 15-6 Product structure BOM . . . . . . . 9-20
Properties . . . . . . . . . . . . 15-6, 15-19, Printing
15-21, 15-24, 15-32–15-33 Object properties . . . . . . . . . . . . 4-24
Participants Objects . . . . . . . . . . . . . . . . . . . . 4-23
Assigning . . . . . . . . . . . . 20-13, 21-13 Search results tree . . . . . . . . . . . 7-27
Assigning in the thin client . . . . 23-47 Privileged team member . . . . . . . .. 8-3
Password Problem reports . . . . . . . . . . . . . . 20-16
Rich client logon . . . . . . . . . . . . . 1-11 About . . . . . . . . . . . . . . . . . . . . . 20-8
Paste Creating . . . . . . . . . . . . . . . . . . . 21-3
Outside Teamcenter . . . . . . . . . . 2-27 Creating in the thin client . . . . . 23-41
Specify relation type . . . . . . . . . . 2-26 Example change states . . . . . . . 20-29
URLs . . . . . . . . . . . . . . . . . . . . . 2-27 Example process . . . . . . . . . . . . 20-19
Paste command Relating items to . . . . . . . . . . . 21-10
Relations . . . . . . . . . . . . . . . . . . 3-22 Relationships to other objects . . 20-10

Index
Process viewer (workflow) . . . . . . 23-55 Finding . . . . . . . . . . . . . . . . . . . 8-21

Product structure Propagation rules . . . . . . . . . . . . 8-13
Apply all markups . . . . . . . . . . 12-30 Removing objects from . . . . . . . . 8-18
Apply markup . . . . . . . . . . . . . 12-28 Smart folder hierarchy . . . . . . . . . 8-2
Background color . . . . . . . . . . . 10-12 Projects data
Browse . . . . . . . . . . . . . . . . . . . . . 9-3 Finding . . . . . . . . . . . . . . . . . . . 8-21
Build . . . . . . . . . . . . . . . . . . . . . . 9-3 Propagation rules . . . . . . . . . . . . . 8-13
Carrying forward markups . . . . 12-31 Properties
Close window . . . . . . . . . . . . . . . 11-8 Column configurations . . . . . . . . 9-15
Comment on markup . . . . . . . . 12-27 Find components by . . . . . . . . . 11-10
Compare . . . . . . . . . . 9-3, 12-9, 12-11 Modifying . . . . . . . . . . . . . . . 4-8, 4-10
Create mark up . . . . . . . . . . . . 12-25 Prefixes . . . . . . . . . . . . . . . . . . . 4-12
Delete markup . . . . . . . . . . . . . 12-32 Printing . . . . . . . . . . . . . . . . . . . 4-24
Display . . . . . . . . . . . . . . . . . . . . . 9-9 Product structure . . . . . . . . . . . . 9-13
Edit . . . . . . . . . . . . . . . . . . . . . . . 9-3 Suffixes . . . . . . . . . . . . . . . . . . . 4-12
Enabling markup mode . . . . . . 12-24 Properties dialog box . . . . . . . . . . . . 4-3
Marking up . . . . . . . . . . . . . . . 12-23 Properties dialog box, printing . . . . 4-24
Modify columns . . . . . . . . . . . . . 9-12 Properties pane . . . . . . . . . . 15-6, 15-19,
Print the BOM . . . . . . . . . . . . . . 9-20 15-21, 15-24, 15-32–15-33
Properties . . . . . . . . . . . . . . . . . 9-13 Classification image viewers . . . 15-41
Refresh window . . . . . . . . . . . . . 11-7 Viewing Classification search
Review markup mode . . . . . . . . 12-27 results . . . . . . . . . . . . . . . . . 15-38
View . . . . . . . . . . . . . . . . . . . . . . . 9-8 Properties table . . . . . . . . . . . . . . 15-19
Viewing . . . . . . . . . . . . . . . . . . 23-38 Properties view . . . . . . . . . . 14-4, 14-10
Product structures Property column
Precise/Imprecise . . . . . . . . . . . 10-10 Insert . . . . . . . . . . . . . . . . . . . . . 9-14
Product visualization . . . . . . . . . . . 1-16 Remove . . . . . . . . . . . . . . . . . . . 9-14
Project Property values
Filters . . . . . . . . . . . . . . . . . . 8-6–8-7 Find and replace . . . . . . . . . . . . . 4-12
Privileged team member . . . . . . . . 8-3
Project administrator . . . . . . . . . . 8-3 Q
Project team administrators . . . . . 8-3
Smart folders . . . . . . . . . . . . . 8-6–8-7 Quantity
Project administrator . . . . . . . . . . . . 8-3 Modify . . . . . . . . . . . . . . . . . . . . 12-7
Project propagation rules . . . . . . . . 8-13 Query
Project team administrators . . . . . . . 8-3 Cancel . . . . . . . . . . . . . . . . . . . . 7-15
Project-level security tasks Quick add . . . . . . . . . . . . . . . . . . 11-19
Configuring assignment of related Quick links . . . . . . . . . . . . . . . . . . 1-14
objects . . . . . . . . . . . . . . . . . . 8-13 Rich client . . . . . . . . . . . . . . . . . 1-14
Configuring automatic assignment to Quick open results
projects . . . . . . . . . . . . . . . . . 8-16 Search . . . . . . . . . . . . . . . . . . . . 7-10
Projects Quick Open search . . . . . . . . . . . . . 1-14
Assigning objects to . . . . . . . . . . 8-10 Rich client . . . . . . . . . . . . . . . . . 1-14
Assigning related objects . . . . . . 8-13 Quick search . . . . . . . . . . . . . . . . . 7-10
Automatically assigning data to . . 8-16 Classification . . . . . . . . . . . . . . 15-33
Find . . . . . . . . . . . . . . . . . . . . . . 8-22 Rich client . . . . . . . . . . . . . . . . . . 1-7

Index
R Resize a view . . . . . . . . . . . . . . . . . . A-8

Reference Reviewing state . . . . . . . . . . . . . . 20-27
Database objects . . . . . . . . . . . . . 2-20 Revising items . . . . . . . . . . 23-30, 23-32
References Revision configuration . . . . . . . . . . . 9-3
Named . . . . . . . . . . . . . . . . . . . . 5-11 Revision control . . . . . . . . . . . . . . . 10-2
Relate Solution Item to Impacted Item Revision effectivity . . . . . . . . . . . . 10-21
button . . . . . . . . . . . . . . . . . . . . . 22-6 Display data . . . . . . . . . . . . . . . 10-23
Relating items to a change . . . . . . 21-10 Revision rule setting
Relation Browser Ad hoc . . . . . . . . . . . . . . . . . . . . 10-8
Accessing . . . . . . . . . . . . . . . . . . 14-3 Change default . . . . . . . . . . . . . . 10-7
User interface . . . . . . . . . . . . . . . 14-4 Default . . . . . . . . . . . . . . . . . . . . 10-7
Using . . . . . . . . . . . . . . . . . . . . . 14-2 Rich client
Relation Browser view . . . . . . 14-4–14-5 Back and forward buttons . . . . . . . 1-7
Relation object properties . . . . 4-13–4-14 Clipboard button . . . . . . . . . . . . . 1-8
Relations Configure Applications button . . . 1-14
Automatically defined . . . . . . . . . 3-21 Favorites . . . . . . . . . . . . . . 1-14, 2-16
Created by Paste command . . . . . 3-22 History links . . . . . . . . . . . . . . . 1-14
Item and item revision . . . . . . . . 3-20 I Want To links . . . . . . . . . . . . . . 1-14
Relationship between change Information center . . . . . . . . 1-8, 6-31
objects . . . . . . . . . . . . . . . . . . . . 20-10 Item reports . . . . . . . . . . . . . . . . 7-42
Removing Menu bar . . . . . . . . . . . . . . . . . . . 1-7
Objects from projects . . . . . . . . . 8-18 Navigation pane . . . . . . . . . . . . . . 1-8
Rename Open dataset . . . . . . . . . . . . . . 19-16
Favorites folder . . . . . . . . . . . . . 2-18 Open items . . . . . . . . . . . . . . . . . 1-14
Folder . . . . . . . . . . . . . . . . . . . . . 2-12 perspective banner . . . . . . . . . . . . 1-7
Rename search results . . . . . . . . . . 7-22 Primary application buttons . . . . . 1-8,
Renaming 1-14
Search results . . . . . . . . . . . . . . 7-22 Quick links . . . . . . . . . . . . . . . . . 1-14
Reorder Quick Open search . . . . . . . . . . . 1-14
Objects . . . . . . . . . . . . . . . . . . . . 2-13 Report Builder reports . . . . . . . . 7-39
Replacements . . . . . . . . . . . . . . . 11-23 Search . . . . . . . . . . . . . . . . . . . . . 7-3
Replacing component . . . . . . . . . . 11-24 Search field . . . . . . . . . . . . . . . . . 1-7
Report Builder . . . . . . . . . . . . . . . . 7-37 Search results . . . . . . . . . . . . . . 7-19
Report Builder reports Secondary application buttons . . . 1-8,
Rich client . . . . . . . . . . . . . . . . . 7-39 1-14
Reporting and Analytics Server condition symbol . . . . . . . . 1-9
Dashboard . . . . . . . . . . . . . . . . . 7-37 Teamcenter logon . . . . . . . . . . . . 1-11
Reports . . . . . . . . . . . . . . . . . 7-37–7-38 Toolbar . . . . . . . . . . . . . . . . . . . . . 1-7
Item reports . . . . . . . . . . . . . . . . 7-41 User interface condition symbol . . 1-9
Reports, live Excel Rich client interface . . . . . . . . . . . . . 1-7
Run Teamcenter reports . . . . . . 19-28 Rich client perspectives
Repositioning columns . . . . . . . . . . 4-18 Closing . . . . . . . . . . . . . . . . . . . . 1-21
Requestor Opening . . . . . . . . . . . . . . . . . . . 1-19
Assigning . . . . . . . . . . . . . . . . . 20-13 Reset . . . . . . . . . . . . . . . . . . . . . 1-21
Resize Saving . . . . . . . . . . . . . . . . . . . . 1-21
Table columns . . . . . . . . . . . . . 23-14 Rich client perspectives and views . . 1-18

Index
Rich client views . . . . . . . . . . . . . . 1-18 Displaying . . . . . . . . . . . . . 7-18, 7-21

Role Navigating Classification search
Rich client logon . . . . . . . . . . . . . 1-11 results . . . . . . . . . . . . . . . . . 15-36
Rules Printing results tree . . . . . . . . . . 7-27
Definition . . . . . . . . . . . . . . . . . . 6-21 Rename . . . . . . . . . . . . . . . . . . . 7-22
Rules-based protection . . . . . . . . . . 6-21 Renaming . . . . . . . . . . . . . . . . . . 7-22
Run Teamcenter reports, live Save to My Saved Searches . . . . . 7-30
Excel . . . . . . . . . . . . . . . . . . . . . 19-28 Saving to a folder . . . . . . . . . . . . 7-31
Search Results box . . . . . . . . . . . . 15-37
S Search results view . . . . . . . . . . . . 7-19
Search type
Save button . . . . . . . 15-19, 15-21, 15-24 Advanced . . . . . . . . . . . . . . . . . . . 7-9
Save search results . . . . . . . . . . . . 7-30 Dataset Name . . . . . . . . . . . . . . . 7-9
Saving Item ID . . . . . . . . . . . . . . . . . . . . 7-9
Search results to a folder . . . . . . 7-31 Item name . . . . . . . . . . . . . . . . . . 7-9
Saving changes, multiple Keyword . . . . . . . . . . . . . . . . . . . . 7-9
windows . . . . . . . . . . . . . . . . . . . . 11-6 Searches . . . . . . . . . . . . . . . . . . . 20-36
Schedule Manager Advanced criteria . . . . . . . . . . . 23-21
Creating work breakdowns Cancel . . . . . . . . . . . . . . . . . . . . 7-15
using . . . . . . . . . . . . . . . . . . 21-15 Items . . . . . . . . . . . . . . . . . . . . 23-19
Schedule Tasks list . . . . . . . . . . . 23-50 Loading results . . . . . . . . . . . . . . 7-21
Schedules Share saved searches . . . . . . . . . 7-35,
Creating . . . . . . . . . . . . . . . . . . 21-15 23-23, 23-25
Scope Simple item criteria . . . . . . . . . 23-20
Class . . . . . . . . . . . . . . . . . . . . 15-34 Where-used . . . . . . . . . . . . . . . 14-16
Hierarchy . . . . . . . . . . . . . . . . . 15-34 Searching
Search . . . . . . . . . . . . . . . . . . . . 2-5, 7-2 Wildcard support . . . . . . . . . . . . . 7-8
Advanced . . . . . . . . . . . . . . . . . . 7-15 Secondary application buttons . . . . . 1-8,
Change . . . . . . . . . . . . . . . . . . . . . 7-5 1-14
Classification . . . . . . . . . . . . . . 15-26 Secondary applications . . . . . . . . . 1-23
Classification object ID . . . . . . . 15-27 Select signoff task . . . . . . . . . . . . 23-54
Client for Office . . . . . . . . . . . . . 19-9 Selecting related components . . . . . 6-12,
Form-based . . . . . . . . . . . . . . . . 7-15 6-14
Input . . . . . . . . . . . . . . . . . . . . . . 7-7 Send To menu . . . . . . . . . . . . . . . 15-19
overview . . . . . . . . . . . . . . . . . . . . 7-6 Send To option . . . . . . . . . . . . . . . 15-19
Quick . . . . . . . . . . . . . . . . . . . . . 7-10 Sequences
Quick open results . . . . . . . . . . . 7-10 Using . . . . . . . . . . . . . . . . . . . . . 3-17
types . . . . . . . . . . . . . . . . . . . . . . 7-6 Server
View . . . . . . . . . . . . . . . . . . . . . . . 7-3 Rich client logon . . . . . . . . . . . . . 1-11
Search Class dialog box . . . . . . . . 15-33 Server condition symbol . . . . . . . . . . 1-9
Find a class . . . . . . . . . . . . . . . 15-31 Sessions, perspectives, and
Search field . . . . . . . . . . . . . . . . . . . 1-7 applications . . . . . . . . . . . . . . . . . 1-10
Search results Set input to recent selection . . . . . . A-13
Closing . . . . . . . . . . . . . . . . . . . . 7-23 Show Assemblies . . . . . . . . . . . . . . 15-6
Compare . . . . . . . . . . . . . . . . . . 7-24 Show Image . . . . . . . . . . . . . . . . . . 15-6
Comparing . . . . . . . . . . . . . . . . . 7-24 Signoff team . . . . . . . . . . . . . . . . 23-54

Index
Active tasks . . . . . . . . . . . . . . . . 18-5 Create . . . . . . . . . . . . . . . . . . . . 22-8

Pending tasks . . . . . . . . . . . . . . . 18-9 Definition . . . . . . . . . . . . . . . . . . 22-7
Process template . . . . . . . . . . . 18-10 View . . . . . . . . . . . . . . . . . . . . . 22-10
Workflow creation . . . . . . . . . . . . 18-3 Symbols
Simple Search Abstract class . . . . . . . . . . . . . . . 15-7
Overview . . . . . . . . . . . . . . . . . . 7-11 Classification . . . . . . . . . . . . . . . 15-7
Perform . . . . . . . . . . . . . . . . . . . 7-13 Group . . . . . . . . . . . . . . . . . . . . . 15-7
Smart folder hierarchy ICM root . . . . . . . . . . . . . . . . . . 15-7
Projects . . . . . . . . . . . . . . . . . . . . 8-2 SML class . . . . . . . . . . . . . . . . . . 15-7
SML class . . . . . . . . . . . . . . . . . . . 15-7 Storage class . . . . . . . . . . . . . . . 15-7
SML class symbol . . . . . . . . . . . . . 15-7 Storage Class . . . . . . . . . 15-19, 15-21
Solution Items folder . . . . . . . 22-5–22-6 Subclass . . . . . . . . . . . . . . . . . . . 15-7
Sort System-defined searches . . . . . . . 20-36
Table columns . . . . . . . . . . . . . 23-14
Table data . . . . . . . . . . . . . . . . . 4-19 T
Sorting data in the Table pane . . . 15-40
Specify relation type Table child rows . . . . . . . . . . . . . . 23-14
Paste . . . . . . . . . . . . . . . . . . . . . 2-26 Table columns . . . . . . . . . . . . . . . 23-14
Standard track . . . . . . . . . 20-12, 20-16 Column display . . . . . . . . . . . . 23-14
Example process . . . . . . . . . . . . 20-21 Resize . . . . . . . . . . . . . . . . . . . 23-14
Starting Classification . . . . . . . . . . 15-2 Sort . . . . . . . . . . . . . . . . . . . . . 23-14
Starting the thin client . . . . . . . . . 23-8 Table links . . . . . . . . . . . . . . . . . . 23-15
Storage class symbol . . . . . . . . . . . 15-7 Table pane
Storage Class symbol . . . . . 15-19, 15-21 Sorting data . . . . . . . . . . . . . . . 15-40
Storage classes . . . . . . . . . . . . . . . 15-9 View Classification search
Structure comparison results . . . . . . . . . . . . . . . . . 15-40
Example results . . . . . . . . . . . . 12-13 Table panes
Structure lines Configuring . . . . . . . . . . . . . . . . 4-15
Pack . . . . . . . . . . . . . . . . . . 12-2, 12-5 Table rows . . . . . . . . . . . . . . . . . . 23-14
Packing restrictions . . . . . . . . . . 12-6 Table scroll bars . . . . . . . . . . . . . . 23-15
Unpack . . . . . . . . . . . . . . . . . . . 12-3 Tables
Structure Manager Configure view tables data
Capabilities . . . . . . . . . . . . . . . . . 9-3 display . . . . . . . . . . . . . . . . . 4-16
Definition . . . . . . . . . . . . . . . . . . . 9-3 Configuring data display . . . . . . . 4-15
Interface . . . . . . . . . . . . . . . . . . . 9-5 Properties . . . . . . . . . . . . . . . . 15-19
Launch . . . . . . . . . . . . . . . . . . . . . 9-8 Repositioning columns . . . . . . . . 4-18
Structure tree Sorting data . . . . . . . . . . . . . . . . 4-19
Sorting . . . . . . . . . . . . . . . . . . . . 9-19 Tables, using . . . . . . . . . . . . . . . . 23-14
Subclass symbol . . . . . . . . . . . . . . . 15-7 Tabs
Subprocess creation . . . . . . 17-11–17-12 BOM Changes . . . . . . . . . . . . . . 20-4
Substitute . . . . . . . . . . . . . . . . . . 11-23 Change Effectivity . . . . . . 20-4, 22-11
Substitute components Details . . . . . . . . . . . . . . . . . . . . 20-4
Substitute occurrences . . . . . . . 11-32 Impact Analysis . . . . . . . . . . . . . 20-4
Suffix property value . . . . . . . . . . . 4-12 Schedule Manager . . . . . . . . . . . 20-4
Summary tab . . . . . . . . . . . . . . . . . 20-4 Summary . . . . . . . . . . . . . . . . . . 20-4
Supersedure . . . . . . . . . . . . . . . . 23-49 Viewer . . . . . . . . . . . . . . . . . . . . 20-4

Index
Task assignments Hiding . . . . . . . . . . . . . . . . . . . 13-23

Client for Office . . . . . . . . . . . . 19-22 Showing . . . . . . . . . . . . . . . . . . 13-23
Tasks Unit of measure . . . . 15-19, 15-34–15-35
Workflow . . . . . . . . . . . . . . . . . 23-50 Unit of measurement
Tasks to Perform list . . . . . . . . . . 23-50 Classification object . . . . . . . . . 15-39
Tasks to Track list . . . . . . . . . . . . 23-50 Unpacking structure lines . . . . . . . 12-3
TC_Dataset_Import_Exclude_Wildcard Update dataset
preference . . . . . . . . . . . . . . . . . . . 5-3 Client for Office . . . . . . . . . . . . 19-12
Team members URLs
Privileged team member . . . . . . . . 8-3 Paste . . . . . . . . . . . . . . . . . . . . . 2-27
Project administrator . . . . . . . . . . 8-3 User ID
Project team administrators . . . . . 8-3 Rich client logon . . . . . . . . . . . . . 1-11
Teamcenter User Interface
Search . . . . . . . . . . . . . . . . . . . . . 7-3 My Teamcenter . . . . . . . . . . . . . . . 2-4
Search results . . . . . . . . . . . . . . 7-19 User interface condition symbol . . . . 1-9
Teamcenter functionality not in thin User interface elements . . . . . . . . 23-10
client . . . . . . . . . . . . . . . . . . . . . . 23-5 User-defined searches . . . . . . . . . 20-36
Teamcenter interfaces User-specified relations . . . . . . . . . 3-22
Rich client . . . . . . . . . . . . . . . . . . 1-7
Thin client . . . . . . . . . . . . . . . . . 23-6 V
Teamcenter overview . . . . . . . . . . . . 1-3
Variant conditions
Teamcenter perspectives and
Create . . . . . . . . . . . . . . . . . . . 13-10
views . . . . . . . . . . . . . . . . . . . . . . 1-18
Modifying . . . . . . . . . . . . . . . . . 13-14
Teamcenter sessions . . . . . . . . . . . 1-10
Variant rule
Thin client . . . . . . . . . . . . . . . . . . 23-39
Set . . . . . . . . . . . . . . . . . . . . . . 13-21
Component pane . . . . . . . . . . . . . 23-6
Set required rule . . . . . . . . . . . 13-20
Data pane . . . . . . . . . . . . . . . . . 23-7
Setting . . . . . . . . . . . . . . . . . . . 13-19
Favorites . . . . . . . . . . . . . . . . . . 2-16
Unset option value . . . . . . . . . . 13-22
Menu bar . . . . . . . . . . . . . . . . . . 23-6
Unset required rule . . . . . . . . . 13-20
Navigation pane . . . . . . . . . . . . . 23-6
Variant rules
Open dataset . . . . . . . . . . . . . . 23-36
classic variants . . . . . . . . . . . . . . 13-2
Starting . . . . . . . . . . . . . . . . . . . 23-8
Variants . . . . . . . . . . . . . . . . . . . . . 9-3
Toolbar . . . . . . . . . . . . . . . . . . . . 23-6
Creating data (classic variants) . . 13-4
Thin client functionality . . . . . . . . . 23-4
Example of classic variants . . . . . 13-3
Thin client interface . . . . . . . . . . . . 23-6
Using classic variants . . . . . . . . . 13-2
Thin client versus rich client . . . . . 23-3
Versions
Thin Client window . . . . . . . . . . . . 23-6
Dataset . . . . . . . . . . . . . . . . . . . 5-16
Toolbar . . . . . . . . . . . . . . . . . . 1-7, 23-6
Specify a version . . . . . . . . . . . . . 5-16
Top navigation bar . . . . . . . . . . . . 23-11
View
Topic
Detached . . . . . . . . . . . . . . . . . . . A-9
Subtopic . . . . . . . . . . . . . . . . . . . 18-2
Display using Fast View . . . . . . . A-14
Transferring checkout . . . . . . . . . . 6-16
Graph Overview . . . . . . . . . . . . . 14-4
Types of change objects . . . . . . . . . 20-8
Image Preview . . . . . . . . . . . . . . 14-4
Move . . . . . . . . . . . . . . . . . . . . . . A-8
U Product structure . . . . . . . . . . . . . 9-8
Unconfigured components Relation Browser . . . . . . . . . . . . 14-4

Index
Supersedure . . . . . . . . . . . . . . . 22-10 W
View Folder
Minimize . . . . . . . . . . . . . . . . . . A-15 Where-used searches . . . . . . . 9-3, 14-16
View Mode button . . . . . . . . . . . . 15-38 Wildcard characters . . . . . . . . . . . . . 7-8
View tables Work Breakdown tab . . . . . . . . . . . 20-4
Configuring . . . . . . . . . . . . 4-15–4-16 Work breakdowns
Viewer tab . . . . . . . . . . . . . . . . . . . 20-4 Creating . . . . . . . . . . . . . . . . . . 21-15
Viewers Work, finding . . . . . . . . . . . . . . . . 23-26
Classification Properties pane . . 15-41 workflow
Viewing branching . . . . . . . . . . . . . . . . . . 17-4
Checkout history . . . . . . . . . . . . 6-18 Workflow
Workflow processes . . . . . . . . . . 23-55 Audit log . . . . . . . . . . . . . . . . . 18-31
Viewing access privileges Client for Office . . . . . . . . . . . . 19-20
Example of . . . . . . . . . . . . . . . . . 6-25 Managing tasks . . . . . . . . . . . . 23-50
How to . . . . . . . . . . . . . . . . . . . . 6-24 Out of Office Assistant . . . . . . . 18-26
Viewing multiple ICOs of single Process assignment lists . . . . . . . 18-8
object . . . . . . . . . . . . . . . . . . . . . 15-38 Signoff team . . . . . . . . . . . . . . . 23-54
Views Surrogate . . . . . . . . . . . . . . . . . 18-27
Change Home . . . . . . . . . . . . . . 20-36 Viewing a workflow process . . . 23-55
Rich client . . . . . . . . . . . . . . . . . 1-18 Workflow process
Search . . . . . . . . . . . . . . . . . . . . . 7-3 Initiate . . . . . . . . . . . . . . . . . . . . 17-6
Search results . . . . . . . . . . . . . . 7-19 Workflow subprocesses . . . . 17-11–17-12
Visualize product structure . . . . . . . 9-3 Workflow Viewer . . . . . . . . . . . . . . 1-16

Reference tear-out pages
These reference tear-out pages are provided for your convenience.
Course agenda
Day 1 Morning
Introduction
Course
overview
Lesson 1 Introduction to Teamcenter
Lesson 2 Working in My Teamcenter
Afternoon
Lesson 3 Working with items in Teamcenter
Lesson 4 Viewing and modifying object properties
Lesson 5 Creating and managing datasets
Lesson 6 Applying data security practices
Day 2 Morning
Lesson 7 Performing and managing searches
Lesson 8 Working in projects
Lesson 9 Opening and viewing product structures
Afternoon
Lesson 10 Controlling assembly configuration views
Lesson 11 Creating and managing product structures
Lesson 12 Working with product structures
Day 3 Morning
Lesson 13 Configuring a product structure with variants
Lesson 14 Navigating the relation hierarchy of an object
Lesson 15 Classifying and using standard product data
Afternoon
Lesson 16 Viewing and working with visualization files
Lesson 17 Initiating a workflow
Lesson 18 Managing workflow task assignments
Day 4 Morning
Managing Teamcenter data through the Microsoft
Lesson 19
Office integration
Lesson 20 Using Change Manager
Afternoon
Lesson 21 Creating and managing change objects
Lesson 22 Elaborating and executing the change
Lesson 23 Working in the Teamcenter thin client
Course
summary
Classroom data sheet
This table is provided so students can record their classroom setup, as
described by the instructor. Optionally, instructors may hand out a preprinted
data sheet.
Data item Data value Domain
OS user ID
OS password
Teamcenter user ID
Teamcenter password
STUDENT_HOME
Student user IDs and numbers
A user ID and the associated number is assigned to each student in class.
• Your assigned user ID doubles as your Teamcenter login password.
• Your user number is applied when performing various activities in class.
User number User ID / password User name

01 de01 Allison, Buddy
02 de02 Astaire, Fran
03 de03 Baker, Bobby
04 de04 Ball, Larry
05 de05 Burns, Georgia
06 de06 Burton, Jay
07 de07 Davis, Brett
08 de08 Day, Boris
09 de09 Earnhardt, David
10 de10 Fonda, Henrietta
11 de11 Foyt, Andy
12 de12 Grable, Freddy
13 de13 Heston, Charlotte
14 de14 Hope, Roberta
15 de15 Jarret, Debbie
16 de16 Kahne, Cary
17 de17 Kelly, Jean
18 de18 Kenseth, Mark
19 de19 Lewis, Merry
20 de20 Loren, Soapy
21 de21 Martin, Mary
22 de22 Monroe, Mervin
23 de23 Park, Sally
24 de24 Patrick, Daniel
25 de25 Peck, Ginger
26 de26 Petty, Karla
27 de27 Rogers, Gene
28 de28 Russel, Shane
29 de29 Sadler, Eddie
30 de30 Stewart, Tonya
31 de31 Tracy, Stacy
32 de32 Wallace, Randy
33 de33 Wayne, Joan
Instructor user ID and number
This user ID and number is reserved for use by instructors:
User number User ID / password User name
00 de00 Andretti, Maria
Student profile
Course evaluation

Using TC

Uploaded by

Copyright:

Available Formats

Using TC

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Using TC

Uploaded by

Copyright:

Available Formats

Using Teamcenter

Proprietary and restricted rights notice

2 Using Teamcenter MT25150_S_101

Proprietary and restricted rights notice; Trademarks . . . . . . . . . . . 2

Introduction to Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Working in My Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Organize data in folders and pseudofolders . . . . . . . . . . . . . . . . . . . . . . . 2-6

Working with items in Teamcenter . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

4 Using Teamcenter MT25150_S_101

Alternate identifiers . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . . . . . . 3-27

Viewing and modifying object properties . . . . . . . . . . . . . . . . . . . . 4-1

Overview of object properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Creating and managing datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Dataset objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Applying data security practices . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

User groups and roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Performing and managing searches . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

6 Using Teamcenter MT25150_S_101

Compare search results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

Working in projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Opening and viewing product structures . . . . . . . . . . . . . . . . . . . . . 9-1

Understanding product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Controlling assembly configuration views . . . . . . . . . . . . . . . . . . . 10-1

Creating and managing product structures . . . . . . . . . . . . . . . . . . 11-1

8 Using Teamcenter MT25150_S_101

Build and edit product structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Working with product structures . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Marking up the product structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23

Configuring a product structure with variants . . . . . . . . . . . . . . . 13-1

Using classic variants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Navigating the relation hierarchy of an object . . . . . . . . . . . . . . . 14-1

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

10 Using Teamcenter MT25150_S_101

Classifying and using standard data . . . . . . . . . . . . . . . . . . . . . . . 15-1

Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Viewing and working with visualization files . . . . . . . . . . . . . . . . 16-1

Locate and view visualization data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Initiating a workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

Overview of workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2

Managing workflow task assignments . . . . . . . . . . . . . . . . . . . . . . 18-1

Select signoff teams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2

12 Using Teamcenter MT25150_S_101

Managing Teamcenter data through the Microsoft Office

Basic tasks for live Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28

Using Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20-1

Creating and managing change objects . . . . . . . . . . . . . . . . . . . . . 21-1

Creating a change object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-2

14 Using Teamcenter MT25150_S_101

Create a work breakdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21-15

Elaborating and executing the change . . . . . . . . . . . . . . . . . . . . . . 22-1

Executing the change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22-2

Working in the Teamcenter thin client . . . . . . . . . . . . . . . . . . . . . . 23-1

Working with change objects in the thin client . . . . . . . . . . . . . . . . 23-40

Course summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24-1

Managing views, layouts, and view networks . . . . . . . . . . . . . . . . A-1

16 Using Teamcenter MT25150_S_101

Using Teamcenter introduces the concept of product lifecycle management

• To organize, manage, and secure product data.

• To use Structure Manager to view, build and edit product structure.