Teamcenter Admin

Teamcenter Engineering
Application Administration
Student Guide
September 2004
MT14350 Version 9.1.2
Publication Number
MT14350SG0912
Manual History
Manual Product Publication

Revision Version Date
A V9.0 March 2004
B V9.1.2 September 2004
This edition obsoletes all previous editions.
UGS
All rights reserved.
Printed in the United States of America.
2 Teamcenter Engineering Application Administration MT14350SG0912

Proprietary and Restricted Rights Notices
The following proprietary and restricted rights notices apply.
2004 UGS PLM Solutions Inc. All Rights Reserved. This software
and related documentation are proprietary to UGS PLM Solutions Inc.
LIMITATIONS TO U.S. GOVERNMENT RIGHTS. UNPUBLISHED
- RIGHTS RESERVED UNDER THE COPYRIGHT LAWS OF THE
UNITED STATES. This computer software and related computer software
documentation have been developed exclusively at private expense and are
provided subject to the following rights: If this computer software and
computer software documentation qualify as "commercial items" (as that
term is defined in FAR 2.101), their use, duplication or disclosure by the
U.S. Government is subject to the protections and restrictions as set forth
in the UGS PLM Solutions Inc. commercial license for the software and/or
documentation, as prescribed in FAR 12.212 and FAR 27.405(b)(2)(i) (for
civilian agencies) and in DFARS 227.7202-1(a) and DFARS 227.7202-3(a)
(for the Department of Defense), or any successor or similar regulation, as
applicable or as amended from time to time. If this computer software and
computer documentation do not qualify as "commercial items," then they are
"restricted computer software" and are provided with "restrictive rights," and
their use, duplication or disclosure by the U.S. Government is subject to the
protections and restrictions as set forth in FAR 27.404(b) and FAR 52-227-14
(for civilian agencies), and DFARS 227.7203-5(c) and DFARS 252.227-7014
(for the Department of Defense), or any successor or similar regulation, as
applicable or as amended from time to time. UGS PLM Solutions Inc., 5400
Legacy Drive, Plano, Texas 75024.
All trademarks belong to their respective holders.
MT14350SG0912 Teamcenter Engineering Application Administration 3

Contents
Course Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Course Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Course Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Key Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Student Responsibilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
How to Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Teamcenter Engineering Environment . . . . . . . . . . . . . . . . . . . . . . 1-1

Getting Acquainted with the TcEng Environment . . . . . . . . . . . . . . . 1-2
Teamcenter Engineering Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Teamcenter Engineering Installation Directories . . . . . . . . . . . . . . . . 1-4
Teamcenter Engineering Portal Client (IPR, IDR) . . . . . . . . . . . . 1-5
Teamcenter Engineering Base Installation (IMAN_ROOT) . . . . . . 1-6
TcEng Database Configuration Settings Directory
(IMAN_DATA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Teamcenter Engineering Environment Variables . . . . . . . . . . . . . . . . 1-9
Setting the Teamcenter Engineering Environment . . . . . . . . . . . . . 1-10
Setting the Classroom Teamcenter Engineering Environment . . . . . 1-11
Activity: Get Acquainted with your TcEng Installation . . . . . . . . 1-12
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
User Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Building User Organization in Teamcenter Engineering . . . . . . . . . . 2-2
Person, User, Role and Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
The infodba Account and its Privileges . . . . . . . . . . . . . . . . . . . . . . . 2-6
System Administration Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Creating an Account Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Creating a Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Creating a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Creating a Sub-Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Creating a Person . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Creating a User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Tips in Creating your Organization . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Activity: Add a User to the dba Group . . . . . . . . . . . . . . . . . . . . 2-19
Teamcenter Engineering Volumes . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Creating a Volume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Fail-Safe Volume(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
UGS, All Rights Reserved Teamcenter Engineering Application Administration 5

Contents
Activity: Interactively Create a Volume, Group and Role . . . . . . 2-32

Activity: Interactively Create more Volumes . . . . . . . . . . . . . . . 2-39
Creating Accounts with the make_user Utility . . . . . . . . . . . . . . . . 2-41
Class Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Activity: Create User, Group, Role using make_user . . . . . . . . . 2-47
Activity: Create Organization using a script . . . . . . . . . . . . . . . 2-48
Activity: Create Hierarchical Group Organization . . . . . . . . . . . 2-51
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
Form Types and LOVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Form Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Activity: Automatic Form using Form Type Wizard . . . . . . . . . . . 3-6
Activity: Create Automatic Form using Form Type Wizard . . . . . 3-11
Classes, Types and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Activity: Form Storage Class Types and Properties . . . . . . . . . . 3-14
Lists of Values (LOV) for Form data . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Activity: Lists of Value (LOV) for Form Usage . . . . . . . . . . . . . . 3-18
Activity: Lists of Values (LOV) for Form Usage . . . . . . . . . . . . . 3-22
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Item Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Item Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Activity: Creating Item (and Master Form) Types . . . . . . . . . . . . 4-4
Using Schema Editor to add POM Classes for Forms . . . . . . . . . . . . . 4-6
Activity: Classes for Forms Using the Schema Editor . . . . . . . . . . 4-9
Activity: LOV for Item Type Form . . . . . . . . . . . . . . . . . . . . . . . 4-19
Item Type Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Activity: Customizing the New Item Dialog . . . . . . . . . . . . . . . . 4-21
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
Dataset Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Creating Dataset Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Dataset Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Dataset Creation/Modification Process . . . . . . . . . . . . . . . . . . . . . . . 5-4
Creating Dataset Types and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Activity: Dataset Type Using the Wizard . . . . . . . . . . . . . . . . . . . 5-7
Activity: Creating Dataset Types Using the Standard Method . . 5-12
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Product Structure Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Creating Product Structure Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Units of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Activity: Creating Units of Measure . . . . . . . . . . . . . . . . . . . . . . 6-5
Occurrence Note Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Activity: Creating Occurrence Note Types . . . . . . . . . . . . . . . . . . 6-8
6 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912

Contents
PSView Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Activity: Creating PSView Types . . . . . . . . . . . . . . . . . . . . . . . . 6-12
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14
Queries and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Creating Saved Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Defining Saved Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Activity: Create a Query that Finds Home Folders . . . . . . . . . . . . 7-7
Query Access to Other Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
Activity: Modify Access of the Find Homes Query . . . . . . . . . . . 7-13
Activity: Custom Item Type Query . . . . . . . . . . . . . . . . . . . . . . . 7-16
Full Text Searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Importing/Exporting Queries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Activity: Import a query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Creating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Activity: Create a Report using the EndItem query . . . . . . . . . . 7-29
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Status Types and Revision Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Creating Status Types and Revision Rules . . . . . . . . . . . . . . . . . . . . . 8-2
Status Types for Release Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Activity: Create Status Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Revision Rules Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Revision Rules Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Activity: Create Revision Rules . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Activity: Verify Revision Rule Preference Settings . . . . . . . . . . . 8-21
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Access Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Teamcenter Engineering Access Manager . . . . . . . . . . . . . . . . . . . . . 9-2
Teamcenter Engineering Data Protections . . . . . . . . . . . . . . . . . . . . . 9-3
Viewing Data Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Activity: View Default Protections . . . . . . . . . . . . . . . . . . . . . . . . 9-7
How Rules-Based Protections Work . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Editing the Rule Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Activity: Add Access Manager Rule . . . . . . . . . . . . . . . . . . . . . . 9-24
Setting Object Based Exception Privilege Data . . . . . . . . . . . . . . . . 9-31
Activity: Modify Single Object Protections . . . . . . . . . . . . . . . . . 9-33
Exporting and Importing the Rule Tree from a File . . . . . . . . . . . . . 9-36
Exporting the Access Manager Rule Tree . . . . . . . . . . . . . . . . . . . . 9-37
Importing an Access Manager Rule Tree . . . . . . . . . . . . . . . . . . . . . 9-38
Activity: Reset the Rule Tree from a File . . . . . . . . . . . . . . . . . . 9-39
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-41

Contents
Project Creation, Administration and Control . . . . . . . . . . . . . . . 10-1

Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Activity: Create a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
......................... . . . . . . . . . . . . . . . . . . . . . . . 10-13
Activity: Setting Security Rules . . . . . . . . . . . . . . . . . . . . . . . . 10-14
......................... . . . . . . . . . . . . . . . . . . . . . . . 10-16
Activity: Add objects to a Project . . . . . . . . . . . . . . . . . . . . . . . 10-18
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Workflow Process Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Create Workflow Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Overview of Teamcenter Engineering Workflow . . . . . . . . . . . . . . . . 11-3
Review of the Teamcenter Engineering Process Model . . . . . . . . . . . 11-4
Process Terms and Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Result of Releasing Data with a Process . . . . . . . . . . . . . . . . . . . 11-6
Two Usage Modes with Workflow . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Controlling the Workflow with Process Templates . . . . . . . . . . . 11-8
Creating Process Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Process Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Creating new Workflow Processes . . . . . . . . . . . . . . . . . . . . . . 11-11
Modifying existing Workflow Processes . . . . . . . . . . . . . . . . . . 11-13
Create a Process Template That Does Not Require Signoff . . . . 11-14
Activity: Create a Quick Release Process . . . . . . . . . . . . . . . . . 11-15
Creating a Single Signoff Release Process . . . . . . . . . . . . . . . . . . . 11-19
Activity: Create a Single Signoff Release Process . . . . . . . . . . . 11-21
Using Task Handlers in a Process Template . . . . . . . . . . . . . . . . . 11-27
Some Useful Canned Handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-28
Activity: Add a Handler to a Process . . . . . . . . . . . . . . . . . . . . 11-32
Creating a Multi Task Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-35
Using ACLs in a Process Template . . . . . . . . . . . . . . . . . . . . . . . . 11-36
Activity: Create a Process Template for CM . . . . . . . . . . . . . . . 11-37
Importing/Exporting Workflow Processes . . . . . . . . . . . . . . . . . . . 11-53
Activity: Importing process templates . . . . . . . . . . . . . . . . . . . 11-54
Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-57
Activity: Resource Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-60
Conditional Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-70
Activity: Conditional Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-74
Secure Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-88
Activity: Secure Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-90
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-98
Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Overview of Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Benefits of the CM Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Review of Change Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Contents
Review of Types of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Review of Change Object Folder Structure . . . . . . . . . . . . . . . . . . . 12-6
Creating Change Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Activity: Create the TRCN Change Type . . . . . . . . . . . . . . . . . . 12-9
Process Model Design for Change Management . . . . . . . . . . . . . . . 12-16
TR Change Notice Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
Activity: Add CM Handlers to TR Change Notice . . . . . . . . . . . 12-18
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-22
Business Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Business Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Type Display Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Activity: Creating Type Display Rules . . . . . . . . . . . . . . . . . . . . 13-4
Naming Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Activity: Creating and Attaching Item Naming Rules . . . . . . . . 13-9
Activity: Test Item Naming Rules . . . . . . . . . . . . . . . . . . . . . . 13-16
Property Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Activity: Creating Item Property Rules . . . . . . . . . . . . . . . . . . 13-20
Compound Property Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-28
Activity: Creating Compound Property Rule between EndItem
properties and Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-30
Action Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
Activity: Default Item Create and Display Behavior . . . . . . . . . 13-36
Activity: Create Item Action Rules . . . . . . . . . . . . . . . . . . . . . 13-39
Activity: Test Item Action Rules . . . . . . . . . . . . . . . . . . . . . . . 13-43
Deep Copy Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-45
Activity: Observe Default Item Revise and Save As . . . . . . . . . 13-46
Activity: Create Deep Copy Rules for Items . . . . . . . . . . . . . . . 13-48
Activity: Test Deep Copy Rules for Items . . . . . . . . . . . . . . . . . 13-49
Business Modeler Import/Export Rules . . . . . . . . . . . . . . . . . . . . . 13-52
Activity: Use the UI to Export Business Rules . . . . . . . . . . . . . 13-53
Activity: Use the UI to Import Business Rules . . . . . . . . . . . . . 13-55
The import_export_business_rules utility . . . . . . . . . . . . . . . . 13-59
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-60
Preferences and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Setting Preferences and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

Activity: Modify Command Suppression Definitions . . . . . . . . . . 14-5
Assigning Default Process Templates . . . . . . . . . . . . . . . . . . . . . . . 14-8
Activity: Assign Default Process Templates . . . . . . . . . . . . . . . 14-11
Preference Settings Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-14
Preference Settings to Consider . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15
Environment Variable Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-17
Environment Variables Settings to Consider . . . . . . . . . . . . . . . . . 14-18
Activity: Modify Site/Group/Role Preferences . . . . . . . . . . . . . . 14-19

Contents
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
Import Non-CAD Data into Teamcenter Engineering . . . . . . . . . . 15-1

Import Existing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2
Overview of Importing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Importing Files Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
Activity: Create New Dataset and Import File . . . . . . . . . . . . . . 15-5
Activity: Import File into Existing Dataset . . . . . . . . . . . . . . . . 15-8
Importing Files Using the import_file Utility . . . . . . . . . . . . . . . . . 15-10
Activity: Import File using import_file Utility . . . . . . . . . . . . . 15-12
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-14
Status Imported Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Protecting Imported Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Quick Release Technique . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Activity: Status data using Quick Release Process . . . . . . . . . . 16-4
release_man Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
Activity: Using release_man to Status Data . . . . . . . . . . . . . . . . 16-8
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
Setup for NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

NX/Teamcenter Engineering Integration Overview . . . . . . . . . . . . . 17-2
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Item Structure and Named References . . . . . . . . . . . . . . . . . . . . . . 17-4
Create Part Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Storage of Associated Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Access Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
UGMASTER / UGPART Behavior . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
Setup for NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
Seed Part Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
Seed Part Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Activity: Organize the NX Seed Parts folder . . . . . . . . . . . . . . 17-16
Mapping TcEng Attributes to NX Part Attributes . . . . . . . . . . . . . 17-18
Default Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Extending Attribute Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Attribute Mapping Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Comments and Contexts Symbols . . . . . . . . . . . . . . . . . . . . . . . . . 17-23
Activity: Teamcenter Engineering/NX Attribute Mapping . . . . 17-24
Process Templates for NX Related Data . . . . . . . . . . . . . . . . . . . . . 17-32
Setting NX Manager Preferences . . . . . . . . . . . . . . . . . . . . . . . . . 17-34
Preference Settings for NX Manager . . . . . . . . . . . . . . . . . . . . . . . 17-35
Preference Settings to Consider for NX Manager . . . . . . . . . . . . . . 17-36
Environment Variable Settings for NX Manager . . . . . . . . . . . . . . 17-37
NX Customer Default Files for NX Manager . . . . . . . . . . . . . . . . . 17-38
Activity: Modify NX Manager Preferences . . . . . . . . . . . . . . . . 17-39

Contents
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-41
NX Manager Import and Data Release . . . . . . . . . . . . . . . . . . . . . . 18-1

Import Unigraphics Data into the Database . . . . . . . . . . . . . . . . . . 18-2
Introduction to Unigraphics Data Import . . . . . . . . . . . . . . . . . . . . 18-3
Parts and Assemblies to be Imported . . . . . . . . . . . . . . . . . . . . . . . . 18-4
Prepare to Import Unigraphics Data . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Recognize the Unigraphics Files and Attribute Data . . . . . . . . . 18-7
Overview of the ug_import Capabilities . . . . . . . . . . . . . . . . . . . . . 18-12
Introduction to Using Mapping Files . . . . . . . . . . . . . . . . . . . . 18-13
Introduction to Using Command Line Keywords . . . . . . . . . . . 18-14
Using (Directory) Search Files . . . . . . . . . . . . . . . . . . . . . . . . . 18-15
Importing Non-Master and Associated Unigraphics Files . . . . . 18-16
Understanding Various NX Manager Import Scenarios . . . . . . . . . 18-17
Command Line Keywords With ug_import . . . . . . . . . . . . . . . . . . 18-20
Import Component/Assembly Parts without a Map File . . . . . . . . . 18-21
Import an Assembly using a Map File and Search File . . . . . . . . . . 18-23
The Import Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-28
Activity: Using ug_import to Import the Seed Parts . . . . . . . . . 18-29
Activity: Import the 1600 Wheel Assembly . . . . . . . . . . . . . . . 18-32
Import a Non-Master Drawing File . . . . . . . . . . . . . . . . . . . . . . . . 18-33
Import Files Associated to a (Master) Part File . . . . . . . . . . . . . . . 18-34
Import Files Associated to the DWG (Non-Master) Part File . . . . . 18-36
Activity: Import the 1250 Axle Associated Files . . . . . . . . . . . . 18-37
Activity: Import the 1250 Axle Drawing . . . . . . . . . . . . . . . . . . 18-38
Activity: Import the Axle Drawing Associated Files . . . . . . . . . 18-40
Import Files Using a Full Map File . . . . . . . . . . . . . . . . . . . . . . . . 18-41
Activity: Import 2105 Frame Assy with Mapping File . . . . . . . 18-45
Importing Non-Unigraphics Files into an Item . . . . . . . . . . . . . . . 18-47
Activity: Import the Heat Treat Text File . . . . . . . . . . . . . . . . . 18-48
Releasing Previously Imported Unigraphics Data . . . . . . . . . . . . . 18-49
Activity: Release the 2111 Item Revision . . . . . . . . . . . . . . . . . 18-50
Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-52
Student Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

UNIX Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
vi Editor Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Teamcenter Engineering and NX Manager Environment

Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Teamcenter Engineering Environment Variable List (sample) . . . . . B-2
Teamcenter Engineering Preference List (sample) . . . . . . . . . . . . . . B-4
NX Manager Preferences (sample) . . . . . . . . . . . . . . . . . . . . . . . . . B-9

Contents
Teamcenter Engineering Notes and Utility Quick Reference . . . . C-1

System Administration Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Common Command Line Arguments . . . . . . . . . . . . . . . . . . . . . . . . C-5
System Administration User Accounts and Groups . . . . . . . . . . . . . C-6
Setting the Teamcenter Engineering Environment . . . . . . . . . . . . . C-7
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Course Overview
Course Description
Teamcenter Engineering Application Administration addresses setup of the
Teamcenter Engineering environment to meet your company needs through
realistic data and process implementation scenarios. You will learn how
to define business data and process models in a Teamcenter Engineering
database.
This course illustrates a best practice process for defining a companys data
and process models in Teamcenter Engineering. It also illustrates managing
the Teamcenter Engineering environment and importing legacy data into
Course Objectives
Overview of Teamcenter Engineering System Environment
Building Group/User/Role Organization
Modeling Item Data, Form Data, and Dataset Data
Modeling Product Structure Data
Defining Statuses and Configuration Rules
Extending Query Tools and Creating Reports
Defining Access Rules
Creating Projects and Controlling Access to Project Data
Designing Workflow Templates and Modeling Change Management Data
Defining Naming, Action and Deep Copy Rules
Setting Site, Group, Role and User Preferences and Options
Importing Legacy Data
Configuring a Unigraphics Integration

Key Benefits
Key Benefits
Increase productivity by learning through realistic projects.
Participate in hands-on work sessions with Teamcenter Engineering

and NX Manager
Benefit from personal assistance of a EDS-certified instructor
Demonstrate best practices for implementing and using Teamcenter

Engineering
Participants
Anyone responsible for defining, configuring or maintaining a Teamcenter
Engineering implementation, in particular, implementation planners,
application administrators, UNIX/Windows system administrators and
Oracle DBAs.
Student Responsibilities
Be on time
Participate in class
Stay with the subject matter
Listen attentively and take notes
Practice on the job what you have learned
Have fun

Course Overview
How to Use This Manual

Inside each lesson are sections that include key concepts followed by an
activity to allow you to practice the concepts.
The format of the activities is consistent throughout this manual. Steps are
labeled and specify what will be accomplished at any given point in the
activity. Below each step are action boxes which emphasize the individual
actions that must be taken to accomplish the step.
Activity Example
For your benefit, each activity is organized in the following manner.
Activity: Login to Teamcenter Engineering

In this activity, you will login to Teamcenter Engineering.
Step 1: Login to Teamcenter Engineering
Choose the Admin application.
Choose the Organization icon.
Enter the UserID and Password assigned to you
The Step is intended to be an increment to complete the activity.

Indented from each step is a series of actions, represented by square bullets.
These actions are intended to provide the button pushes to complete the step.
Each lesson ends with a Summary page.

Lesson
1 Teamcenter Engineering
Environment
Purpose
The purpose of this lesson is to acquaint you with the Teamcenter Engineering
system environment.
Objectives
Upon completion of this lesson, you will be able to:
Identify the different types of user interfaces for accessing and working in
Teamcenter Engineering.
Locate key directories containing data you need to configure a Teamcenter

Engineering site.
Prepare the Teamcenter Engineering system environment for command

line interface tools.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 1-1

Teamcenter Engineering Environment
Getting Acquainted with the TcEng Environment
Why do you need to know this topic?
So you can locate installation directories that contain data you will modify
to configure your site.
So you can prepare the necessary system environment for using command
line interface utilities.
The following will be discussed on the next few pages.

Teamcenter Engineering Interfaces
Teamcenter Engineering Installation Directories
Teamcenter Engineering Environment Variables
Setting Teamcenter Engineering Environment Variables
Setting the Classroom Environment
1-2 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912
Teamcenter Engineering Interfaces

There are different user interfaces for accessing and working in
Teamcenter Engineering. Depending on the type of access needed,
a person can be assigned to log in and use one of these interfaces.
Portal The main Portal interface is for the person who deals
primarily with Configuration Management, Workflow,
Change Management, and Product Structure creation
and maintenance.
Start-up scripts:
Windows: portal.bat
Unix: start_portal
Portal Lite Portal Lite is designed for the person who spends a large
portion of their time in a CAD application. The interface
is a scaled down version of the full Portal interface with
limited Workflow, Change Management, and Product
Structure capabilities. Portal Lite is also referred to as
NX Manager mode.
Start-up scripts:
Windows: ugmanager_portal.bat
Unix: start_ugmanager_portal
Web Access The Web interface is intended for those users who will be
mostly viewing and reviewing. There are limited signoff
and application access capabilities. The Web interface
uses both Internet Explorer (HTML and DHTML on
Windows) and Netscape (only HTML on Unix).

Teamcenter Engineering Installation Directories

The following material will describe three installation directories that
contain data used by the administrative user to configure the Teamcenter
Engineering implementation:
Teamcenter Engineering Portal Client (IPR, IDR)
Teamcenter Engineering Base Installation (IMAN_ROOT)
Teamcenter Engineering Database Configuration Settings Directory

(IMAN_DATA)
Teamcenter Engineering Portal Client (IPR, IDR)
The Teamcenter Engineering Portal client software is located

in a directory identified by system environment variables
IPR (short for IMAN_PORTAL_ROOT) and IDR (short for
IMAN_DEPOT_ROOT). These directories contain the JAVA binaries
for the client application and numerous properties files that can
be modified to change the default behavior of the portal software.
The following files will be discussed as the course progresses:
portal.jar The JAVA archive of the Portal application.

When un-archived, included properties files
can be used to change the default behavior
of the Portal application.
portal.properties Contains high level Portal defaults. The
Application listings within the Portal
GUI can be added or subtracted from the
interface using settings in this file.
client_specific.properties Defines settings that affect the Portal
Viewer application and choices for the
database selections on the Teamcenter
Engineering logon dialog.

Teamcenter Engineering Base Installation (IMAN_ROOT)
The Teamcenter Engineering base installation is identified by the

IMAN_ROOT system environment variable. This directory contains the core
Teamcenter Engineering product binary executables.
The IMAN_ROOT directory has a specific directory structure and content
when the product is shipped. It is very important that this structure and
content is maintained.
Maintaining integrity (directories and files) allows technical support
personnel to quickly troubleshoot a problem and determine if the problem is
caused by customization or if the problem is a defect of the core product.
Modifying the directory structure or the files contained in these directories
can greatly affect product support. Therefore, we strongly recommend
adhering to the following guidelines for customizing Teamcenter Engineering.
The following table list some of the IMAN_ROOT directories we will be
exposed to during this course.
Directory Remarks
IMAN_ROOT/bin Contains the core product binary files including
command line interface utilities.
IMAN_ROOT/data Contains default values for an IMAN_DATA
directory shipped with the product.
IMAN_ROOT/lang Contains the /textserver directory which contains
XML files used for localization of Teamcenter
Engineering.
IMAN_ROOT/web Contains the Web access application for
IMAN_ROOT/local Refer to the next page.
The IMAN_ROOT/bin directory contains many Teamcenter

Engineering utilities that will be used in this class.
IMAN_ROOT/local Directories
In order to maintain integrity of the core product and allow for customization,
the Teamcenter Engineering developers have provided several directories for
storing customization files. These directories are created during installation
and allow programmers, system administrators, and users to create and
store the various profile, environment, and user interface files required to
customize Teamcenter Engineering. These sub-directories are the only
recommended locations for customization files.
The following table lists and describes the IMAN_ROOT/local sub-directories.
Directory Remarks
IMAN_ROOT/local/bin Contains custom ITK programs. Core Teamcenter
Engineering does not access this directory, it is
just a consistent location to store these programs.
IMAN_ROOT/local/data Contains iman_local_setup for setting custom
environment variables.
IMAN_ROOT/local/lang Contains modified IMAN_ROOT/lang data.
IMAN_ROOT/local/lib Contains libuser_exits.sl, etc.
IMAN_ROOT/local/tools Contains user-defined software applications
(tools).

TcEng Database Configuration Settings Directory (IMAN_DATA)
The IMAN_DATA directory is created (based on a copy of the

IMAN_ROOT/data) directory during the database installation and initial
configuration.
An IMAN_DATA directory is created and used for each database instance
a site may have created - for example, prod (Production), test (Test), and
trng (Training).
The IMAN_DATA directory contains files and sub-directories that are
intended to be modified to support configuration. Among these are:
.iman_env Stores Teamcenter Engineering site preferences.
gpfiles directory Stores Teamcenter Engineering group preference

files.
rpfiles directory Stores Teamcenter Engineering role preference

files.
am directory Stores backup definitions of the Access Manager

setup.
gs_info directory Stores definitions of Dataset types.
The IMAN_DATA directory also contains other files maintained on the

operating system and tied to a particular database. More explanation of the
files and sub-directories in the IMAN_DATA directory will be discussed as
the course progresses.
Teamcenter Engineering Environment Variables

A working knowledge of Teamcenter Engineering environment variables
is essential for Teamcenter Engineering administrators. The following
paragraphs discuss the basic concepts and terminology used to document
Teamcenter Engineering environment variables.
Teamcenter Engineering stores environment variable settings in a script file:
iman_profilevars (Unix) or iman_profilevars.bat (Windows). This
script can be executed directly by Bourne, Korn and DOS shells.
The following environment variables must be set before using

iman_profilevars.
IMAN_ROOT Top (root) directory of the Teamcenter Engineering

directory structure. This environment variable
must be set before running the Teamcenter
Engineering application or command line utilities.
IMAN_DATA Directory containing Teamcenter Engineering
data files. This variable is set during
Teamcenter Engineering installation and added to
IMAN_DATA/iman_profilevars.
The following are some of the environment variables set with

iman_profilevars.
IMAN_BIN Location of the Teamcenter Engineering utilities.

ORACLE_SERVER Oracle server network node.
ORACLE_SID Unique name of Oracle database instance
associated with IMAN_DATA.
IMAN_DB_CONNECT The userid and password the Teamcenter
Engineering software uses when it interacts with
the Oracle software.

Setting the Teamcenter Engineering Environment

The command line interface utilities documented in this class run from the
command line inside operating system command shells. Because a Portal
session is not running, the Teamcenter Engineering environment must be set
manually before these utilities can be run. It is only necessary to perform
this procedure once for each shell session. The environment will remain
configured until the shell is closed or the settings are overridden by other
shell commands.
Each Teamcenter Engineering utility documents the environment required to
successfully run. The environment information included with each utility
assumes that the Teamcenter Engineering environment has been set as
described in the following paragraphs.
In the following procedures default path names are used. If
other path names were specified during Teamcenter Engineering
installation, use those path names instead.
To set the environment, do the following:

1. Open a command prompt window on your workstation.
2. Type one of the following sets of commands:
Bourne/Korn IMAN_ROOT=/usr/iman0912; export IMAN_ROOT

Shell IMAN_DATA=/usr/iman0912/imandata; export IMAN_DATA
. $IMAN_DATA/iman_profilevars
C Shell setenv IMAN_ROOT /usr/iman0912

setenv IMAN_DATA /usr/iman0912/imandata
source $IMAN_DATA/iman_cshvars
Windows set IMAN_ROOT=d:\iman0912

set IMAN_DATA=d:\iman0912\imandata
call %IMAN_DATA%\iman_profilevars
Setting the Classroom Teamcenter Engineering Environment

A script has been written to set environment variables for this class named
env-sitea.
env-sitea (Unix) env-sitea.bat (Windows)
Utilities used in this class require that the Teamcenter Engineering

environment variables be set. Using env-sitea sets up the Teamcenter
Engineering environment variables and paths for the utilities.
IMAN_ROOT, IMAN_DATA, and certain other environment
variables (as designated below) are set with env-sitea and then
the rest of the Teamcenter Engineering environment variables are
set by sourcing IMAN_DATA/iman_profilevars inside env-sitea.
IMAN_BIN=/usr/iman0912/bin
IMAN_DATA=/disk1/imandata <- set by env_sitea
IMAN_DB_CONNECT=imandev1:tbwiabd@devli
IMAN_HELP_FILE=/usr/iman0912/help/imanhelp.hlp
IMAN_INCLUDE=/usr/iman0912/include
IMAN_LANGUAGE=/usr/iman0912/lang
IMAN_LIBRARY=/usr/iman0912/lib
IMAN_LOG=/disk1/imandata/log_sltrora_devli
IMAN_ONLINE_HELP=/usr/iman0912/help/imanhelp/imanhelp.ksh
IMAN_PRINTER=/usr/bin/lp
IMAN_ROOT=/usr/iman0912 <- set by env_sitea
ORACLE_SERVER=sltrora
ORACLE_SID=devli
POM_SCHEMA=/disk1/imandata/pom_schema_sltrora_devli
POM_TRANSMIT_DIR=/usr/iman0912/pom_transmit
PATH=/usr/iman0912/bin:/usr/iman0912/bin:
/disk1/imandata/local/bin:/usr/eds130/bin/
SHLIB_PATH=/usr/iman0912/lib/CC:/usr/iman0912/lib/oracle:
/usr/iman0912/lib:/usr/lib
XBMLANGPATH=/disk1/imandata/bitmaps/%B
XFILESEARCHPATH=:/disk1/imandata/bitmaps/%N:/disk1/imandata/%N%S:
/usr/lib/X11/app-defaults/%N%S_=/usr/bin/env

Activity: Get Acquainted with your TcEng Installation
In this activity, you will login to your workstation and get acquainted
with the Teamcenter Engineering installation for this classroom.
Step 1: Login to your workstation.
Step 2: Look at the environment variables for your workstation, paying

close attention to those used for Teamcenter Engineering.
Open a command prompt window and use the appropriate
commands to display the Teamcenter Engineering environment
variables.
Type:
Unix: env | grep IMAN

Windows: set iman
Notice that there are no Teamcenter Engineering environment

variables defined.
If you need help with command window commands,

refer to Appendix A.
Close the command prompt window.
Set the Teamcenter Engineering environment variables for

this class.
Unix: Type . env-sitea in current window

Windows: Double-click env-sitea.bat
The env-sitea script has been written specifically for

this class. Use it to set the Teamcenter Engineering
environment variables in this class. Environment
variables must be set to run the Teamcenter
Engineering utilities.
Use the appropriate commands to display the Teamcenter

Engineering environment variables.
Unix: env | grep IMAN

Windows: set iman
Step 3: Look at how the Teamcenter Engineering environment variables

are set.
Identify the location of the IMAN_DATA directory.
View/list the files in the IMAN_DATA directory.

Notice the iman_profilevars or iman_profilevars.bat file.
Open the iman_profilevars file in a text editor.

This file shows how the Teamcenter Engineering environment
variables have been set.
Find the IMAN_DB_CONNECT environment variable setting.

Notice the setting.
IMAN_DB_CONNECT=infodba:tbwiabd@prod (may be different)
IMAN_DB_CONNECT is set to the Oracle user account that

performs database transactions, i.e., infodba. The word
prod represents the name of the database the Teamcenter
Engineering user is connecting to.
Exit the editor application without filing.
Step 4: Look at the Teamcenter Engineering preference settings in the

.iman_env file.
View/list the files in the IMAN_DATA directory.
Notice the .iman_env file.
Open the .iman_env file in a text editor.
Find the IMAN_ROLE_PFILE preference setting.

The IMAN_DATA/rpfiles sub-directory is the role preference
files location.
Find the IMAN_GROUP_PFILE preference setting.

The IMAN_DATA/gpfiles sub-directory is the group preference
files location.
Exit the editor application without filing.

Step 5: Locate the Role and Group preference file directories.

Locate and expand the IMAN_DATA directory.
Notice the rpfiles and gpfiles directories.
These files/directories were reviewed at this time for you to

understand where Site, Group, and Role preferences are stored.
In later lessons you will learn more about specific Teamcenter
Engineering preferences.
Step 6: Look at the Teamcenter Engineering install directories by using

the IMAN_ROOT environment variable.
Identify the location of IMAN_ROOT.
View/list the files in the IMAN_ROOT directory.

Notice the subdirectories that were explained earlier.
View the contents of the bin directory

Notice the Teamcenter Engineering utilities. You will be using
some of these utilities this week (e.g. clearlocks,
make_user, install, import_file, lock_db, unlock_db).
You are now acquainted with the classroom setup and

ready for the rest of the course activities.
This concludes the activity.
Summary
In this lesson you got an overview of:
The different Teamcenter Engineering interfaces and their key uses.
The location and content of key directories containing data used to

configure a Teamcenter Engineering site.
The process to prepare Teamcenter Engineering Environment for

command line interface tools.

Lesson
2 User Organization
Purpose
The purpose of this lesson is to manage the User Organization in the
Teamcenter Engineering database.
Objectives
Use the Organization Application to manage Persons, Users, Groups,
Roles and Volumes
Use the make_user utility to manage Persons, Users, Groups, Roles

and Volumes

User Organization
Building User Organization in Teamcenter Engineering
... so that you can use best practices to build

User Organization in Teamcenter Engineering.

Person, User, Role and Group
The infodba Account and its Privileges
System Administration Accounts
Creating an Account Interactively
Teamcenter Engineering Volumes
Creating Accounts with the make_user Utility
User Organization
Person, User, Role and Group

In order to explain the basic Teamcenter Engineering concepts of persons,
users, groups and roles, we will consider an individual, Joan Wayne, who
is employed at a Company.
In the Company organization matrix, Joan Wayne primarily works
in the high_performance product group, but she is also assigned to the
standards group.
Joan Wayne has many skills that she applies appropriately while
working in her assigned groups with roles: Engineering Manager, Design
Engineer, Standards Engineer.
Joan Wayne also is an Administrator for the Teamcenter

Engineering implementation and has access to the administration
group (dba) and applies her administration skills (DBA role).
What is a Person?
The Person name describes the Person
individuals who work at your site. Wayne,Joan
A Person contains properties such 10824 Elm Street
as Person Name, Street Address, Wheeling, Il 60021
and Employee Number. Each Organization: Company BB
Person Name must be unique. Employee Number: 150
Email: joanw@bblades.com
What is a User?
The User is a Person with an Person
account know to the Teamcenter Wayne,Joan
Engineering system. One person 10824 Elm Street
can have several user accounts in Wheeling, Il 60021
The Teamcenter Engineering User

implementation of user is waynetr
completely separate from any OS Default Group=
user account. high_performance
Each user must belong to a group.

User Organization
What is a Role?
In Teamcenter Engineering, Group
a role is an object that Group=
models the type of work a high_performance
user is expected to perform Roles=
in a particular Teamcenter Engineering Manager
Engineering group. One group Design Manager
can have many roles.
What is a Group and a

Group Member?
In Teamcenter Engineering, a Person
group serves two purposes: Wayne,Joan
10824 Elm Street
Wheeling, Il 60021
1. A group defines a list of User

selected roles for the group. waynetr
There can be multiple roles Default Group=
per group. high_performance
2. A Group Member defines a

user with an assigned role in a
Group. There can be multiple
group members in a group,
providing multiple users with
multiple roles.
Group Member Group Member
Wayne,Joan Wayne,Joan
(waynetr) (waynetr)
Group= Group=
high_performance standards
Roles= Role=
Engineering Manager Standards Engineer
Design Manager
One user can be a member of many groups. For example, Joan Wayne can
belong to the high_performance and standards groups.
One user can perform multiple roles in a group. For example, Joan Wayne is
an Engineering Manager. In addition to her responsibilities as Engineering
Manager, Joan must also perform design work from time to time. Therefore,
user waynetr has been assigned two Teamcenter Engineering roles in the
high_performance group: Engineering Manager and Design Engineer.
Groups can be organized by function or project.
User Organization
What is a Sub-Group?
In Teamcenter Engineering, Parent
a Sub-Group is a Group with Group
another Group designated as Group=suppliers
its parent. A Sub-Group can
also be designated as a Parent
Group itself. The position
of Sub-Groups within the
organization hierarchy can be
managed by parenting and
re-parenting Groups.
Sub-Group Sub-Group
Group=abc Group=acme

User Organization
The infodba Account and its Privileges

The infodba account is the only
account inTeamcenter Engineering
after the installation. Person
infodba
The infodba accout consists of:

A Person object named infodba User
infodba
A User object named infodba
A Group object named dba
A Role object named DBA and a
group Member object
The infodba account has all the Group

Teamcenter Engineering system level Member
privileges, including a Bypass switch infodba (infodba)
to override access protections. Group=dba
Role=DBA
Users in the dba group have a Bypass toggle which can

be turned On with the User Setting dialog (EditUser
Setting...Administrative). Bypass privilege supercedes other privileges.
User Organization
System Administration Accounts

Person
Wayne,Joan
10824 Elm Street
Wheeling, Il 60021
User
Wayne,Joan
Default Group=
high_performance
Group Member Group Member Group Member

Wayne,Joan (waynetr) Wayne,Joan (waynetr) Wayne,Joan (waynetr)
Group= Group= Group=
high_performance standards dba
Roles= Role= Role=
Engineering Manager Standards Engineer DBA
Design Manager
Using the earlier example with Joan Wayne, an account could be created as
shown above (for example, Person object named Wayne, Joan; User object
named waynetr; Group object named dba; Role object named DBA).
Then the waynetr account has all the Teamcenter Engineering system level
privileges, including the Bypass switch to override access protections, when
Joan switches to the dba group.
Administrator Privileges
Setting Privileges
System Member of the dba All system administration
Administrator group or another dba privileges
group
Group Set as a group Special access privileges for data
Administrator administrator in the owned by the group.
group member dialog
DBA Role Set as the role of a user The DBA role for a user in a
in a group non-dba group has no additional
privileges

User Organization
Creating an Account Interactively

If you are a new Teamcenter Engineering site, follow the recommended order.
Create Organization Structure

1. Create role(s).
2. Create volume(s).
3. Create group(s) and sub-groups.
Create Persons and Users next as they start using TcEng

1. Create person definition(s).
2. Create user account(s)
Independent Definitions
Roles, Volumes, and Persons are independent definitions. Any of these can be
created without consideration of the other definitions.
Dependent Definitions
Groups and Users are dependent definitions. To create the Group and User
definitions, other definitions must exist as follows:
Group definitions require a Role to be defined.

Group definitions suggest a Volume to be defined.
User account definitions require a Person definition.

User account definitions require a Group definition.
User Organization
Creating a Role
By default, the DBA role is defined during installation. The DBA role
provides no administrative privileges. Administrative privileges are provided
with the dba Group membership.
To create a role:
Select Roles.
Enter the name in the Role field.
Choose Create.
The Role name can be up to 32 characters and the Description can

be up to 240 characters.

User Organization
Creating a Group
Double-clicking on Groups in the Organization application expands to show

the groups previously defined in Teamcenter Engineering. As you select each
group, its corresponding information is displayed the Group fields. If this is a
new installation, only the dba and system groups are listed.
When the Default Volume setting is used to specify a volume, a sub-directory

is created within the volumes defined path. The sub-directorys name is
the group Name.
All members of a System Administration group (dba) have System
Administration privileges. System administrators are allowed to perform
Teamcenter Engineering maintenance like upgrades and troubleshooting.
User Organization
Teamcenter Engineering provides a special "system"group which is used for

performing specialized tasks in an overall administration strategy. Currently,
members of the system group are primarily responsible for archiving and
restoring objects. Although any Teamcenter Engineering user can mark an
object for archive or restore, only members of the system group are allowed
to perform the actual object archive and restore operations.
Do not delete the system group from the database under any
circumstances. Teamcenter Engineering will not function properly
without this group.

User Organization
Creating a Sub-Group
There are two methods for creating Sub-Groups.
Method 1
One method is to identify an existing Parent Group when the Group is

created for the first time (or edited thereafter). This is done by selecting the
Parent Group button in the Group creation dialog (as shown below) and then
choosing the Parent Group from the list of existing Groups.
User Organization
Method 2
A second method for creating Sub-Groups is done in the Organization area
of the Organization application. First, select the Group you wish to be the
Parent Group (as shown below). Then choose the Add Sub-Group button
that appears at the bottom of the dialog. The Add Sub-Group option allows
you to add an existing Group or create a new Group, which is then added
as a Sub-Group.

User Organization
Creating a Person
A Person is a Teamcenter Engineering object associated with a real-world

individual. A person is an individual who contributes to the company and
may have more than one user account. Each Person Name must be unique.
To create a Person:
Select Persons.
Enter the appropriate person information (minimum of Lastname,

Firstname in the Name field).
Choose Create.
Double-clicking on Persons in the Organization dialog expands to show the

Persons previously defined in Teamcenter Engineering. As you select each
person, their corresponding information is displayed the Person fields. If this
is a new installation, only infodba is listed.
User Organization
Creating a User
To create a User:
Select Users.
Enter the appropriate user information.
Choose Create.
If this is a new installation, infodba is the only user listed.
The Teamcenter Engineering implementation of user is completely separate

from any OS user account.
Double-clicking on Users in the Organization dialog expands to show the
Users previously defined in Teamcenter Engineering. As you select each user,
their corresponding information is displayed in the User fields. These fields
are also used to modify user information.

User Organization
Passwords
When creating a user account and assigning a password, Teamcenter
Engineering provides companies the ability to specify particular requirements
that their passwords must meet. These password restrictions are controlled
through preferences settings in the .iman_env file.
The following are examples of these preferences.
Minimum Length required.
PASSWORD_minimum_characters=
0
Mixed case required.

PASSWORD_mixed_case_required=
false
Minimum number of alpha characters required.

PASSWORD_minimum_alpha=
0
Minimum number of numeric characters required.

PASSWORD_minimum_digits=
0
What non alphanumeric characters are considered acceptable special

characters.
PASSWORD_special_characters=
#,*,%
Minimum number of special characters required.

PASSWORD_minimum_special_chars=
0
User Organization
Tips in Creating your Organization
Person Names
Consider creating all persons at your site using the following naming
convention:
<Last Name>, <First Name>, <Middle Initial>
This will allow alphabetic sorting of persons by last name.
Assign Default Volumes to Groups; Do Not Assign Them to Users
When creating new users, leave the Default Volume field blank. This will
ensure that project data files are stored in a central location (for example,
the group volume). Otherwise, project data files will be stored in each users
volume.
Create Groups Along Project Lines

It is recommended that you create your Teamcenter Engineering groups
along project lines, not functional lines. This will greatly enhance group and
role functionality, as well as make Teamcenter Engineering much easier
to maintain.
Create Roles Along Functional Lines

It is recommended that you create your Teamcenter Engineering roles along
functional lines (for example, real-world job descriptions, skills and/or
responsibilities). This will allow users to move freely from project to project
simply by adding them to the appropriate group.
User Must be in System Group for Archive/Restore
Most users will mark an object to be archived or restored. A few system

users will be designated to actually archive or restore objects. These users
should be added to the system group.
Best Practice
Typically System Administrators will want to create the necessary groups
and define appropriate roles within those groups before considering which
users should be assigned to those roles (populating a group with members).

User Organization
Important Workflow Impact

Changing existing group and role names in the database can impact workflow
functionality. Workflow jobs will not complete if the group and/or role names
are changed after they are started. Therefore, all workflow processes must
be modified to reflect any changes in group and/or role names or they will
fail. Additionally, all current (i.e., started) EPM jobs affected by group and/or
role name changes must be terminated and new jobs must be started from
updated procedure templates.
Important Policy with dba group and DBA role

A site policy should be in place that no one applies an ACL entry against the
dba group or the DBA role. Nothing prevents users from removing access to
the dba group. If users remove access to the dba group, then the dba group
cannot fix anything (unless the By-pass option is turned on).
User Organization
Activity: Add a User to the dba Group
In this activity, you will interactively add yourself to the "dba" group.
Step 1: Enter the Organization application.

Start Teamcenter Engineering.
From the Application Manager section of the Default

Application Window, choose Admin.
Choose Organization.
Login to Teamcenter Engineering as infodba. The password

is infodba.
The Organization application displays.

User Organization
Step 2: Create a Person.

Double-click on Persons in the bottom section of the
Organization window.
The existing Persons are displayed (only infodba).
Using the format, Your Last Name, Your First Name, enter
your Person Name in the Name field.
Choose Create.
Step 3: Create a User.

Double-click on Users in the bottom section of the Organization
window and the Users are displayed.
User Organization
Enter your Person Name (or use the icon to select your Person
Name by double-clicking on it).
Enter your Teamcenter Engineering User ID (Provided by

your instructor).
Enter your OS Name (Provided by your instructor).
Enter your Teamcenter Engineering Password (Provided by

your instructor).
Select the Default Group icon.

User Organization
The Default Groups dialog appears.
Double-click on the dba group.
Choose Create.
The new User is created.
A Default Volume was not specified, therefore, files

created by this account, while in the dba group, will
be written to the volume used by the dba group.
You have now added a second user to the dba group for DBA
work (instead of infodba).
User Organization
Step 4: Exit Teamcenter Engineering Portal.

Choose FileExit.
Choose Yes to the "Exit Portal?" question.
Step 5: Test the new account.

Start Teamcenter Engineering again.
In the Default Application window, choose the Admin

application group.
Choose Organization.
Login to Teamcenter Engineering using your new User ID

and Password.
From this point on, you will no longer use the infodba account
to do Administrator tasks. You will use your new account.

User Organization
Teamcenter Engineering Volumes

Volumes are directories that are created and used by Teamcenter Engineering
to store files created while running integrated applications from Teamcenter
Engineering. Volumes are also used to store other files created during a
Teamcenter Engineering session. The database retains the information for
the volume location and the file name in the volume. Users cannot directly
access files in Teamcenter Engineering volumes but instead do so via a
Teamcenter Engineering session.
When a user performs an action that causes Teamcenter Engineering to
create a new file, the new file is created within a Teamcenter Engineering
volume. This allows the database to control the file and ensure that it will
be there when it is needed.
Files in a Teamcenter Engineering volume are never modified, they are
always versioned. The distinction is that Teamcenter Engineering creates
or deletes files but never modifies a file in place (i.e., saves changes to an
existing file).
A Teamcenter Engineering volume is an operating system directory controlled
by Teamcenter Engineering. Volumes are used to store files that Teamcenter
Engineering is managing. Teamcenter Engineering supports UNIX and
Windows volumes in homogeneous and heterogeneous environments. A
Teamcenter Engineering volume is controlled by one and only one database.
Teamcenter Engineering volumes can be anywhere on the network.
User Organization
Volume Management
Sound volume management practices are an essential element of a
Teamcenter Engineering administration strategy. Volume management is
designed to be flexible in order to allow each administrator to determine
where files will be stored.
Suggestions for volume management:
Place the volumes on large centralized file servers and use one volume
for each team.
Setup group access to volumes because this is easier to manage. This

seems to be a popular strategy among Teamcenter Engineering sites.
When a volume becomes full, it can either be moved to a larger disk or

have its write access revoked and create a new volume on another disk.
Data Access
Access to volumes is not the same as and must not be confused with
controlling access to objects. If Teamcenter Engineering determines that a
user has Read access to an object (based on the Access Manager), that user
will be able to read the associated operating system file in the Teamcenter
Engineering volume. If the same user has Write access to that object, the
new version of that file would be written to the current volume they access.
Volume Access
When a new file is created, its location is dependent upon how the user
or group is defined.
When a user is defined, the administrator has the option of assigning them a
default volume. If assigned, a sub-directory for the user will be created under
the full path name for the volume. The sub-directory name is the user name.
When a group is defined, the system administrator has the option of
assigning it a default volume. If assigned, a sub-directory for the group
will be created under the full path name for the volume. The sub-directory
name is based on the group name.
If the default volume is assigned to the user, all files created by the user will
be written to the path name and volume sub-directory used by the user. Using
this technique will produce files in multiple directories (one for each user).
If the default volume is assigned to the group,all files created by the user
will be written to the path name and volume sub-directory used by the group.
Using this technique will produce all files in one group directory (even
though the files were created by different users).

User Organization
Files will continue to be written to the default volume until the current
volume is changed in one of the following ways:
When the user changes their group with group volume access in use.
When the user changes their current volume to another volume in which
they have access.
If Teamcenter Engineering cannot read or write a file, an error will be

reported to the user.
Access to volumes must be granted to users or groups in order to allow

them to write files to Teamcenter Engineering volumes.
When a user is granted access to a Teamcenter Engineering volume,

a new sub-directory is created with that users name. The system
administrator granting access to volumes must be logged into the
Teamcenter Engineering dba group.
User Organization
Creating a Volume
To create a Volume:
Select Volumes.
Enter the appropriate volume information.
Choose Create.
The Volume Name field is a unique and descriptive character string.

The Node Name field is the network node name that will physically contain
the new volume.
The Path Name fields are the full UNIX and/or Windows path of the new
volume.
All but the last directory of the specified path name must already exist.
Teamcenter Engineering will create the last directory of the path name,
which coincides to the created volume. It is good practice to have the Volume
Name and last directory of the specified path name be the same.

User Organization
Teamcenter Engineering volumes and group names should be lower

case to accommodate some applications that load lower case file
names. Create the volume on the machine where the disk physically
resides. It is very important that you choose a location that all users
will be able to access Teamcenter Engineering volumes in order to
access Teamcenter Engineering files.
User Organization
Fail-Safe Volume(s)
Each user will have a volume where files are written based on the users
current group setting. If this volume should become full or some other reason
Teamcenter Engineering cannot write to the volume a No Access error
will be displayed.
To continue to save files, the User Settings dialog (EditUser
Setting...Session Settings), can be used to select a different volume (set up
specifically by the Administrator for temporary use). The failsafe_vol shown
below is used temporarily by users as required.
When the original volume becomes available again, the user can reset the
current volume in the User Settings dialog. This will automatically be reset
each time the user logs into Teamcenter Engineering.

User Organization
Setting Volume Access
The Accessors area of the Volumes dialog allows you to Grant (or Revoke)
group and user access to an Teamcenter Engineering volume.
The Grant button allows you to grant Write access to a selected user or
group. Once the Grant button is selected, the appropriate Group can be
chosen from the list.
When access is granted, a sub-directory is created in the volume for that
group. This directory will be used for the saved files.
Volume access can be revoked by first selecting a user or group and the
choosing the Revoke button.
User Organization
Monitoring Volume Disk Usage

Selecting a Volume from the Organization List tree displays the Volume
fields. The fields are used to create and manage Volume definitions.
The Statistics area (in the center section of the Volume panel) displays
information about the disk (not the volume) that the volume resides on, such
as, size, disk space used, and percentage full.

User Organization
Activity: Interactively Create a Volume, Group and Role

In this activity, you will interactively create a volume (standards_vol),
group (standards), and role (Standards Engineer). You
will also add your User to the new group with the new role.
Step 1: Verify that you are in the Organization application.
Step 2: Create a Volume that will be used for the standards group.
Double-click on Volumes in the bottom section of the
Organization application.
Select dba_vol.
Modify the dba_vol fields to reflect the following:

Volume Name: standards_vol
Node Name: (same as dba_vol node name)
Machine Type: (same as dba_vol Machine Type)
Change end of Path Name from dba_vol to standards_vol.
Choose Create.
The new volume is created.
User Organization
Step 3: Revoke the dba group from the Accessors list for the new
standards_vol.
Highlight standards_vol in the Volumes list.
From the list of Accessors, select dba.
Choose Revoke.
Step 4: Create a Role named Standards Engineer for the standards group.
Select Roles (bottom section of Organization window).
Enter the following information:

Role: Standards Engineer
Description: <optional>
Choose Create.

User Organization
The new role is created.
Step 5: Create a standards group with the previously created role.

Double-click Groups in the bottom section of the Organization
application.
Enter standards (in lowercase) for Name.
Enter a Description <optional>.
Choose the Default Volume button.
Double-click on the standards_vol listing.
Select the Standards Engineer role from the List of Defined

Roles and choose the icon.
User Organization
The role is added to the List of Selected Roles.
Choose Create.

User Organization
The standards group is created.
Step 6: Add your User to the standards group.

Expand the standards group in the upper section of the
Select the role of Standards Engineer.
Choose the Add User button.

The Organization User Wizard dialog is displayed.
Make sure the Add existing user to the group/role button

is selected, then choose Next.
User Organization
Select your User ID from the list of Existing Users and choose
to move the user to the Selected Users list.
Choose Finish.
Choose Yes to Do you want to add selected user(s)?
Choose OK to The user(s) have been successfully added! dialog.
Close the Organization User Wizard dialog.

User Organization
Expand the Standards Engineer role under the standards

group to see your User ID listed.
Your database now has the standards group and

standards_vol volume with you as a user.
User Organization
Activity: Interactively Create more Volumes
In this activity, you will interactively create more volumes

prior to running the make_user utility in the next section.
Step 1: Create five more volumes.

Double-click on Volumes in the bottom section of the
Select dba_vol.
Like the standards_vol, use the dba_vol volume as a template

to create the following volumes.
Make sure you choose Create and not Modify.
Volume Names: assembly_vol

corrective_action_vol
high_performance_vol
tooling_vol
hockey_vol
Node Names: (same as dba_vol)
Machine Types: (same as dba_vol)
Change end of Path from dba_vol to assembly_vol

Name:
from dba_vol to corrective_action_vol
from dba_vol to high_performance_vol
from dba_vol to tooling_vol
from dba_vol to hockey_vol
Remember to revoke the dba group from the

Accessors list of each volume, but only after creating
the volume.

User Organization
When finished, the following volumes should be created.
Step 2: Exit Teamcenter Engineering.

Choose FileExit.
Choose Yes.
User Organization
Creating Accounts with the make_user Utility

The make_user (or make_user.exe) utility (IMAN_ROOT/bin) is a program
that allows you to create Teamcenter Engineering users, groups, persons,
roles and volumes from the command line. You can use this utility to set up
your organization with accounts in the Teamcenter Engineering database.
The make_user utility can also be placed inside a shell script and used to
set up an organization in Teamcenter Engineering quickly. The script can
be maintained for records and also used to set up additional databases with
the same organization, if necessary.
Furthermore, creating a simple shell script will allow you to maintain a
separate (disaster) backup copy of this information outside of Teamcenter
Engineering. Because you can re-run make_user as often as necessary,
many Teamcenter Engineering administrators find that maintaining an
up-to-date copy of the make_user shell script is a fast way to completely
restore this information during installations.
Important concepts about the make_user utility:
It can be run in batch mode.
It can be run multiple times.
It can be used to set defaults.
It cannot be used to delete/remove Users, Roles, Persons, and other

organization objects.
It requires the Teamcenter Engineering environment to be set.

User Organization
The format for the command is:

IMAN_ROOT/bin/make_user -u=<user_id> -p=<password>
-g=<group> [-user=<user_id>] [-group=<group_name>]
[-person=<person_name>] [-role=<role_name>]
[-volume=<volume_name>] [-node=<node_name>]
[-path=<path_name>] [-v] [-h]
Uses common command line arguments listed in

the synopsis and the following other arguments:
-user=<user_id> New user that will be created.

-password=<password> Password for the new user.
-group=<group_name> Group that new user will be added to.
-person=<person_name> Person associated with the new user.
-role=<role_name> Role the new user will be assigned to.
-volume=<volume_name> New volume to be created.
-node=<node_name> Network node where the new volume will
be located.
-path=<path_name> Full path where the new volume will be
located.
-file=<file_name> After other arguments are processed; read
file <file_name> to create users. Each
record in the file contains:
person|user|password|group|role|
If you specify a user and group, the user will be made a member of that
group. If you do not specify a person, a person will be created with the same
name as the specified user. If you specify a role as well a user and group,
then the member created will be given that role.
If the -volume switch is specified, then all of the groups that are created
will be granted access to the volume. If the specified group already exists
and does not have a default volume, then the volume will be designed as
the groups default volume.
The source code for the make_user utility is supplied with the
Teamcenter Engineering product as the file make_user_main.cxx
in IMAN_ROOT/sample/utilities. This code can be modified,
compiled and linked to operate based on customer requirements.
User Organization
The following examples demonstrate how you can use the make_user utility
in a variety of different situations.
1. Create a person and user and add them to a group with a specific role.
make_user -person="Smith, John" -user=smith -group=design
-role=engineer -v
The first role specified when creating a group member (user with a
role in a group) will be the default role for that group. This role will
show in the Workspace banner as the default role.
2. Assign a user to another group.

make_user -v -user=smith -group=dba -role=DBA
This adds existing user smith to the group dba with the role DBA.
User IDs must be unique.
3. Create a volume as a default to a group.

make_user -group=design -volume=design_vol -node=node1
-path=/user/volumes/design_vol

User Organization
Using the make_user utility in a Script

These commands can be placed in a script that can be run to create an entire
organization or a new project beginning to use Teamcenter Engineering.
Below is an example:
Make Users in Group(s) with Role(s)

IMAN_BIN/make_user -user=tracytr -person="Tracy, Stacy"
-group=high_performance -role=Product_Engineer -v
IMAN_BIN/make_user -user=tracytr
-group=corrective_action -role=Product_Engineer -v
In the case above, tracytr will have the high_performance default group.
Also tracytr will have the default roles:
Group Default Role

high_performance Product_Engineer
corrective_action Product_Engineer
Put an infodba-like user in Tooling group with DBA role.

IMAN_BIN/make_user -user=waynetr -group=tooling
-role=DBA -v
Put additional user in dba group with DBA role.

IMAN_BIN/make_user -user=tracytr -group=dba
-role=DBA -v
Put additional user in system group with DBA role.

This is to allow these users to do Archive and Restore.
IMAN_BIN/make_user -user=waynetr -group=system
-role=DBA -v
Create Volume for Tooling Group.

IMAN_BIN/make_user -group=tooling -volume=tooling_vol
-path="$ES_VOLS/tooling_vol" -node="$NFS_SERVER" -v
User Organization
Using the make_user utility with the input file argument

The input file (-file=) argument allows you to create multiple Users and
assign them to Groups with a single execution of the make_user executable.
The format of the input file is multiple lines of information
delimited by the | character in the following order:
person|user|password|group|role|
Below is an example of using the make_user utility with an input file:
IMAN_BIN/make_user -file=supplier_users.txt
Contents of supplier_users.txt:
Acme, David|x22222|x22222|acme.suppliers|Viewer|
Jones, Mary|x33333|x33333|abc.suppliers|Author|
Davis, Jeff|x44444|x44444|abc.suppliers|Viewer|
The file argument can not be used to create Volumes.

User Organization
Class Organization
User Organization
Activity: Create User, Group, Role using make_user
In this activity, you will use the make_user utility to

create a single User, Group and Role for the organization.
Step 1: Create the user and related organizational data.

Open a command window with Teamcenter Engineering
environment set.
Enter the following command:
make_user -u=(your userid) -p=(your password) -g=dba

-person="Smith, John" -user=smith -group=design
-role=Engineer -v
Step 2: Log into Teamcenter Engineering and use the Organization

application windows to review the results.
From the Admin group, select the Organization application.
Login with your UserID.
Browse through the application expanding Groups, Roles,

Users and Persons to view the results of the make_user
command for John Smith.
Step 3: Close the Organization Application.

Choose FileExit.

User Organization
Activity: Create Organization using a script

In this activity, you will create Organization in the Teamcenter
Engineering database using the make_user utility in a script.
Step 1: View/edit the make_user script.

Locate the mu.scr.bat file (mu.scr if on Unix) in the
aa_class/make_user directory.
Open the mu.scr.bat file (mu.scr if on Unix) in a text editor.
If required, set the DBAUSER variable to your userID, as

described by your instructor.
Notice, that the make_user command is executed five times to

assign new groups to existing volumes (created interactively
in a previous section).
Also, notice that the make_user command is executed only

once to create all the remaining users in the database. This
is because of the use of the file argument, which accesses a
text file containing the user definitions.
Finally, notice that the make_user command is executed

several times to assign your student userID to each group with
the role of DBA. This could have been done in the mu.txt
file, but was included here to eliminate modifications to the
mu.txt file to add your userID.
Close and save the script file.
Step 2: View the file associate with the file argument in the make_user
script.
Locate the mu.txt file in the aa_class/make_user directory.
Open the mu.txt file in a text editor.
Notice, the first section of the file creates the necessary users
in the database, along with assigning them to a group with a
particular role.
Next, notice that the second section assigns the existing

infodba user to all groups with the role of DBA.
Finally, notice that the last section creates a new user account
called legacy and assigns it to all groups with the role of DBA.
User Organization
This account will be used in the activities for the part files
import lesson.
Close the file without saving.
Step 3: Use the script to create the organization.

environment set.
Use the cd command to navigate to the aa_class directory
Type the following command: cd make_user
Type the following command: mu.scr.bat (mu.scr if on Unix)
Wait until the script completes to move on to the next step.
Step 4: Verify the additional organization objects.

Log back in to Teamcenter Engineering.
Choose the Admin group.
In the Admin group, choose Organization.
Login using your UserID.

User Organization
Expand Groups, Roles, Users, Persons, Volumes, etc. to view

the organization created by the make_user script.
The Organization is now fully built in the database.
User Organization
Activity: Create Hierarchical Group Organization
In this activity, you will create a hierarchical group structure using a

combination of the Organization application and the make_user utility.
Step 1: Create the Group/Role structure and one User using the
Create a suppliers_vol volume similar to the dba_vol volume.
Using the top-down-wizard approach, create the following

organization structure, assigned to the suppliers_vol volume.
Close the Organization application (FileClose).
Step 2: Populate the suppliers organization with Users by using the

make_user utility with the -file argument.
Open suppliers_users.txt (in the ...aa_class/make_user
directory) in a text editor and review the file format.
Close the text editor.

environment set.
Use the cd command to navigate to the aa_class directory.
Type the following command: cd make_user
Execute the following command:

make_user -u=(your userid) -p=(your password) -g=dba
-file=suppliers_users.txt

User Organization
Log back in to the Admin/Organization application.
Observe the three users that were added to the suppliers

group organization.
User Organization
Summary
In this lesson you got an overview of:
Building the User Organization in Teamcenter Engineering

Lesson
3 Form Types and LOVs
Purpose
The purpose of this lesson is to prepare the Teamcenter Engineering
database with Types for Forms and Lists of Values (LOVs).
Objectives
Create Form Types
Create Lists of Values (LOVs)

Form Types and LOVs
Form Types
Review of Forms
Forms are one of the various ways of storing information in Teamcenter
Engineering. Generally, the information manipulated through forms is of a
similar format. Forms are specifically meant for handling small amounts of
information in a fixed format. Forms typically store their data in the Oracle
database as opposed to a file on the volume.
Form Types and LOVs
End-User Form Creation

Forms are most often created by one or more of the following functions:
FileNewForm Used to create a stand-alone form object in a
container (like a Folder) or a form associated with an existing Item or
Item Revision object. End-users select the type of form they are creating
from the list of form types on the New Form dialog.
FileNewItem When an Item is created, at least two form objects are

also created; the Item Master and Item Revision Master. In addition
to these forms, additional forms for the Item Revision object can be
automatically created if specified using the Action Rules section of the
Business Modeler application.
FileNewChange When change objects are created, one to n number

of forms may be automatically created for the Change Revision object.
How many forms and of what type, is setup using the Change Type
section of the Type application.
Via workflow handler Form objects may be created automatically

during a workflow process by using the EPM-create-form action handler.
Handlers for workflow process will be discussed later on in this course.

Form Types and LOVs
Creating Form Types

Form Types can be created or modified from the Admin application group,
Type application.
The Form Type dialog is used to create a new form type.
The Form type name field is used to specify the form type name that will
be selected by the users. This type name is best used to reflect the general
purpose of the form instances as they are created by the users.
The POM class field is used to save the form content data to a pre-defined
Class established in the Teamcenter Engineering Persistent Object Model
(POM) schema. The POM schema Class defines the list and style of attributes
for data stored with the form.
The Class definition table shows the attribute list for the displayed POM
class.
Form Types and LOVs
Using the Form Type Wizard

The Form Type Wizard will walk you through all the necessary steps to
create a new Form Type including the creation of a new POM Schema Class
for storage of the forms data.
Important Considerations:
The Form Type name must be unique and different than the POM Class
name. When the Form Definition Class is added to the Persistent Object
Model (POM), a default Type is automatically created with the same name
as the Form Definition Class name.
Creating a new Class is an important decision. Extending the Teamcenter

Engineering POM schema by adding Classes can affect performance.
Once a Class is instanced, it cannot be deleted.
New Classes added to the POM schema cannot have spaces in their
names. Also, the name for new POM schema Classes should be unique in
the current environment as well as for future possible additions made
during base Teamcenter Engineering version upgrades. A common
approach to naming Classes added to the POM schema is to begin the
name with the initials of the company or the underscore (_) character.
Names for attributes for POM schema Classes cannot contain spaces.
Automatic Form
An Automatic form is a form for which no custom User Interface (UI) has
been specifically developed. The base Portal UI code includes definition for
displaying forms. The default display for an automatic form is similar to the
standard Portal Properties dialog.
All Form Types defined during this course will leverage the Automatic form
concept. The topic of creating custom UI for a new Form Type is beyond the
scope of this course as it requires understanding and usage of the JAVA
programming language.

Form Types and LOVs
Activity: Automatic Form using Form Type Wizard
In this activity, you will create a new Form Type using the
Form Type Wizard. An automatic form is a form for which no
custom user interface display definition (JAVA) has been defined.
Step 1: Create the Form Type.

Start the Admin/Type application.
Select Form in the Types tree.
Choose the icon.

The Form Type Wizard dialog appears.
Step 1 of the wizard is used to define the Form Type Name
and the name of the POM Schema Class that will store the
form data.
Enter Change Description for the Form Type Name.
Enter TRChangeDescription (no spaces) for the Class Name.
Form Types and LOVs
Spaces cannot be used in POM Schema Class names.

TR stands for Training. In actual practice you may
want to use your company initials or an underscore
character at the beginning of the Class name to
ensure uniqueness.
Choose Next.
Step 2 of the wizard is used to define the list of attributes for
the POM Schema Class (TRChangeDescription) associated
with the Form Type.
In the initial row of the dialog, create the following:

Name: AuthorizingDocument
Type: String
Leave the remaining attribute parameters at their default

values.
Choose the icon to add another attribute row.
In the new row, create the following:

Name: ChangeReason
Type: String
Leave the remaining attribute parameters at their default

values.

Form Types and LOVs
Continue to add attributes as shown below.
Remember, spaces cannot be used in attribute names.
Choose Next to continue.

Step 3 of the wizard asks for confirmation to create the Form
Type.
Choose Yes.
Choose OK in the Form Type Created dialog.
Step 2: Verify the creation of the Form Type.

Expand the Form node of the Types list and locate the new
Form Type.
Form Types and LOVs
Select Change Description and verify the definition of the

Form Type.
Step 3: Test the Form Type.

Go to the Engineering/My Navigator application.
Select your Home folder.
Choose FileNewForm...
Choose More... in the New Form dialog to display the list

of Form Types.

Form Types and LOVs
Select the Change Description form type.
Enter Change Description Test in the Name field, then choose

OK to create the form.
The new form object appears in the Home folder.
Viewing or editing the form can be done two different ways.

1. Select the form object, then select the Viewer tab.
2. Double-click the form object to access the dialog window.
Form Types and LOVs
Activity: Create Automatic Form using Form Type Wizard
Create and test the Form Type described below using the Form Type Wizard.

Form Types and LOVs
Classes, Types and Properties
The Persistent Object Model
The following is an abbreviated view of the Teamcenter Engineering

Persistent Object Model (POM) Schema.
Form Types and LOVs
Key Definitions
The following terms are used to describe classes, types and properties.
Class A is the definition of an object implemented in the

Teamcenter Engineering data model. A has a set of
attributes, some of which are inherited from parent
classes and some of which are defined directly for the
class.
Attribute An attribute is a persistent piece of information that
characterizes all objects in the same class.
Type A type is the specialization of a Teamcenter Engineering
class based on properties and behavior
Primary Type A primary type is a default ImanType that directly
corresponds to each POM class (i.e., the primary type
name is the same as the POM class name). Teamcenter
Engineering will automatically create the primary type
when a new POM class is instantiated. The primary type
can also be defined by using the install_types utility.
Sub-Type Sub-types are all types except the primary type that
belong to the same POM class. Sub-types inherit all the
properties and behavior of the primary type. Sub-types
model the actual objects that end-users create.
Property A property is a piece of information that characterizes all
objects of the same type. As a minimum, all Sub-types
have properties that correspond to the attributes for the
associated class.
Before we can attach a List of Values (LOV) to one of the attributes, we

must make sure there is a corresponding primary type for the new classes
created while using the Form Type Wizard. We will use the install_types
utility to perform this task.

Form Types and LOVs
Activity: Form Storage Class Types and Properties
In this activity, you will create the Primary Type and Properties that
correspond to the Classes and Attributes that were created earlier
using the Form Type Wizard. This must be done before we can
attach a List of Values (LOV) to the display of an automatic form.
Step 1: Create the Primary Type (and Properties) for the

TRChangeDescription Class.
This POM Schema Class will be associated with the Change
Description Form Type.
Exit Teamcenter Engineering.

environment set.
In the command window, execute the following command:

install_types -u=infodba -p=infodba -g=dba -f=add
-c=TRChangeDescription -t=TRChangeDescription
Step 2: Create the Primary Type (and Properties) for the TRChangeCosts
Class.
This POM Schema Class will be associated with the Change
Costs Form Type.
Form Types and LOVs

-c=TRChangeCosts -t=TRChangeCosts
Step 3: Regenerate the POM Schema file in the IMAN_DATA directory.

The Form Type Wizard during the previous activity actually
did this for us. The command shown below is how this step is
manually performed using the command line interface. If your
site has two IMAN_DATA directories (UNIX and Windows), you
would have to run this command for the IMAN_DATA directory
not affected by the Form Type Wizard.

install -regen_schema_file infodba infodba dba

Form Types and LOVs
Lists of Values (LOV) for Form data

Lists of Values (LOVs) are used to assist users with entering data into the
system. Often, Teamcenter Engineering is expecting a particular kind of entry
in a field as opposed to a user-defined text entry. In these situations, it makes
a great deal of sense to assist users by implementing an LOV for these fields.
The default Teamcenter Engineering configuration already extensively
implements LOVs for the default Persistent Object Model (POM) schema.
However, anytime you extend your POM schema by adding additional classes
or attributes, there are potentially additional areas where LOVs can be
used at your site.
When you implement an LOV for a dialog field, a LOV button ( ) is

displayed next to that field as shown below:
The user simply clicks the LOV button and an object selection dialog is
displayed that lists allowable entries for that field. Consider that a small
amount of effort setting up LOVs can greatly improve productivity at your
site and prevent incorrect user data entries.
When you associate an LOV, you link this LOV to any field where that data
can be entered and display an LOV button to the user.
Value Types
There are six valid value types used to construct LOVs. Each LOV can
contain only one of these value types (i.e., value types cannot be mixed in the
same LOV). These value types are:
Integer Whole number

Double Double-precision floating point decimal
number (sometimes called a "real")
Char Single ASCII character
String String of ASCII characters
Date Date and time in the format used at your
site
Reference Reference to a list of unique tags in the
database (for example, Item ID)
Form Types and LOVs
Usage Types
Each LOV must also be assigned one of three usage types:
Exhaustive Used to define all allowable entries. If

a user tries to enter a value that is not
contained in an exhaustive LOV, an error
will be displayed to the user.
Suggestive Used to provide a suggested list of allowable
values. For example, a suggestion LOV
could be used to list commonly used
description strings. Because Description
fields typically accept any user-defined
string, the user can select one of the
suggested description strings from the LOV
or enter another user-defined string.
Range Used to provide the user with a constrained
subset of allowable entries. For example,
a range LOV could be used to construct a
small consecutive list of serial numbers.
If a user tries to enter a value that is not
contained in range LOV, an error will be
displayed to the user.

Form Types and LOVs
Activity: Lists of Value (LOV) for Form Usage
In this activity, you will create a List of Values (LOV) for the
ChangeReason Property of the Change Description Form.
Step 1: Log in to the List of Values application.

Choose the Admin application group.
Choose the List of Values application.
Enter your User ID and Password.
Step 2: Create the LOV.

Enter the following LOV parameters:
Name: TR Change Reason

Description: ChangeReason on Change Description Form
Value Type: String
LOV Type: LisitOfValuesString
Usage: Exhaustive
Reference Class: <blank>
Reference Attribute: <blank>
Form Types and LOVs
In the Value field, in the lower right part of the LOV panel,
enter Product Improvement
Choose the icon to add the entry into the list (or simple use
the Enter key).
Continue to add the following entries:

Marketing Request
Field Request
Cost Reduction
Safety
Engineering Error
Choose the icon to sort the list.
Choose the icon to create the LOV.
Step 3: Attach the LOV to the ChangeReason Property.

Select the TR Change Reason LOV from the list of LOVs.
Choose the icon (lower right).

Form Types and LOVs
This dialog lists all Types and their corresponding Properties.

In a previous activity, you created two new Primary Types (and
their corresponding Properties) using the install_types utility.
Scroll down the list to locate the TRChangeDescription Type.
Expand the TRChangeDescription Type.
Select the ChangeReason Property, then choose the icon to

attach the LOV to this Property.
It may take a moment to attach.
The LOV is now attached to the ChangeReason Property.
Close the LOV Property Attachment panel.
Close the LOV application.
Form Types and LOVs
Step 4: Test the LOV usage.

Start the Engineering/My Navigator application.
In your Home folder, double-click on the Change Description

Test form you created earlier.
The Change Description Test form appears.
A drop-down selector should now appear in the

ChangeReason field with the values from the LOV.
Choose Cancel to close the form.

Form Types and LOVs
Activity: Lists of Values (LOV) for Form Usage
In this activity, you will create, attach, and test an exhaustive LOV for the
ChargeCode Property of the Change Description form (as shown below).
Form Types and LOVs
Summary
In this lesson you:
Created Form Types
Created Lists of Values (LOV)

Lesson
4 Item Data Types
Purpose
The purpose of this lesson is to prepare the Teamcenter Engineering database
with Types for Items.
Objectives
Create Item Types
Create POM Schema Classes for Form Data
Add Custom Attribute Display on New Item dialog

Item Data Types
Item Types
Items are the fundamental object used to model data in Teamcenter
Engineering. They are commonly used to identify an element of product
(component, assembly, end-item) or other data such as Procurement
Specification, Test Procedure, Standard Part, Shop Tooling, Engineering
Change, etc.
Data modeled using the Item object is generally "revision controlled" data and
all revisions of the information must be maintained, tracked and recoverable.
Data must also be modeled using the Teamcenter Engineering concept of Item
if it is desired to build structure of the Items as in building Bill of Material
(BOM) for Items that represent product.
In the initial setup for Teamcenter Engineering, two Types of Items have
been provided:
Item Generally used for data that represents an element of product

that is CAD defined and for which Product Structure (BOM) data is
maintained in the system.
Document Generally used for all other data that is considered "revision
controlled" but not necessarily considered "product" or is not defined
using CAD applications.
Basic Item Data Model
An Item in Teamcenter Engineering is a structure of related objects. The

basic structure of any Item consist 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 to include data unique to the customer.
Item Revision 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 to include data
unique to the customer.
Item Data Types
Extending Item Types

The Type application within the Portal Admin program group can be used to
define more Item Types in addition to those provided with base Teamcenter
Engineering (Item and Document).
Reasons for extending the Types for Items:
Having more types for Items may be a useful approach of categorizing
data making it easier for users to find data and understand the differences
between different kinds of data stored in the system.
Different rules for naming convention, action rules and deep copy rules,
etc., can be configured for one Type of Item compared to another Type.
Default process model association for one Type of Item versus another is
easier to implement.
Different "designs" for the Item Master and ItemRevision Master forms
may be desired. Each Type of Item can have unique and different
"Master" form definitions.
In the example below, a new Type of Item (EndItem) has been defined so that
the customer can define customer specific attribute data that TcEng will
store for this kind of data.
EndItem
EndItem Master (Form)
EndItem Revision
EndItem Revision Master (Form)
EndItem Master (Form) EndItem Revision Master (Form)

Item Data Types
Activity: Creating Item (and Master Form) Types
In this activity, you will create a new Item type and

corresponding Master Form types for the new Item Type.
Step 1: Start the Admin/Type application.
Step 2: Create the Item Type.

Select Item in the Types list.
Enter EndItem in the Item type name field.
Choose Create.
The new Item type is listed in the Item node of the Types list.
Step 3: Verify the creation of the Form types.

Expand the Form node of the Types list.
Locate the new EndItem Master and EndItem Revision Master

Form types.
Item Data Types
Select EndItem Master and observe the definition of the Form

type.
Initially, the EndItem Master Form type definition is

identical to the Item Master Form type definition. We will
change this in a subsequent activity.
Select EndItem Revision Master and observe the definition of

the Form type.
Initially, the EndItem Revision Master Form type definition is
identical to the ItemRevision Master Form type definition. We
will change this in a subsequent activity.
Step 4: Close the Admin/Type Application.

In a subsequent activity, you will use the Schema Editor
application to create new POM Schema Classes for
these Form types and then go back to the Admin/Type
application to modify the Form type definitions.

Item Data Types
Using Schema Editor to add POM Classes for Forms

The Schema Editor provides a graphical method of creating and viewing the
Teamcenter Engineering POM schema. The display and interaction with the
database schema is a useful feature within a PDM system.
The TcEng Administrator will use Schema Editor to create, modify, and view
database schema definitions and attributes.
You use the Application Manager to launch Schema Editor. To use Schema
Editor, you must have DBA status. Users without DBA status will have view
only access upon launching Schema Editor.
The Schema Editor window is displayed on the next page. You can view the
POM schema definitions from it conveniently.
View Classes
The Schema Tree displays the POM class hierarchy in a tree style format.
When you click on a class within the tree, the Class Attribute Tree will
display that class and its attributes.
You will also notice that some classes will have a plus sign (+) in front of it.
This is indicating that there are sub-classes attached to that class. Click the
+ and the list of sub-classes will expand.
View an Attribute
The Class Attribute Tree is similar to the Schema Tree. Its purpose is to
display the class currently selected on the Schema tree and its attributes.
The icons contained within the Class Attribute Tree symbolize their type,
therefore if an attribute is of the type String, then the icon for that attribute
will be a string.
Item Data Types
Schema Editor Window
Create a Class
The TcEng Administrator uses Schema Editor and the Schema Editor Wizard
to create new classes and attributes in the database. The new class and
attributes will display in the Class Attribute Navigation Tree.
To create a new SubClass and attributes, select a POM class from the Class
Navigation Tree and choose Create Class Button.
The Schema Editor Wizard displays. Follow the steps to continue the create
operation.

Item Data Types
Delete a Class
Only those classes that are created or extended and have no objects created
in the database, un-referenced classes, and classes for which there are no
objects present can be deleted from the database.
To delete a class, select a class from within the Class Navigation Tree and
choose Delete Class Button.
The system displays a message asking you to confirm this delete operation.
Click Yes to complete the delete operation.
Schema Editor deletes the class and displays a confirmation message if
the operation completed successfully. The class is removed from the Class
Navigation Tree. If the operation was not successful, an error message will
display.
Item Data Types
Activity: Classes for Forms Using the Schema Editor
In this activity, you will create new POM Schema Classes using the Schema
Editor application. You will create a new Class each for the EndItem Master
and EndItem Revision Master Form types you created in the previous activity.
Step 1: Start the Admin/Schema Editor application.
Step 2: Create the Classes for the form types.

Select POM_object in the Class tree.
Choose the Create Class icon .

This launches the Schema Editor Wizard dialog.
For Step 1, leave Create a Sub Class.
Choose Next.

Item Data Types
For Step 2, enter TREndItemMaster for Sub Class Name.

Spaces cannot be used in Class names.
Choose Next.
For Step 3, define the following Attributes for the Class.

Unless otherwise specified, leave the other parameters at
their default values.
Name: Customer
Type: String
Name: Shipped
Type: Logical
Item Data Types
When finished defining attributes, choose Next.
For Step 4, choose Yes, then choose Next.

Item Data Types
For Step 2, enter TREndItemRevMaster for Sub Class Name,

then choose Next.
For Step 3, define the following Attributes for the Class.

Unless otherwise specified, leave the other parameters at
their default values
Name: Contract
Type: String
Name: Weight
Type: Double
Name: DateWeighed
Type: Date
Item Data Types
When finished defining attributes, choose Next.
For Step 4, choose No, then choose Next.
To complete Step 4, choose Yes.
Choose OK.

Item Data Types
For Step 5, choose No, then choose Finish.
Choose Close on the Schema Editor Wizard dialog.
Browse the Class tree and verify the creation of the two classes.
Item Data Types
Step 4: Create Types for the new Classes.

environment set.
In the command window, execute the following command

(use exact case shown)
-c=TREndItemMaster -t=TREndItemMaster
In the command window, execute the following command

(use exact case shown)
-c=TREndItemRevMaster -t=TREndItemRevMaster
Step 5: Modify the Form Type Definitions.

Log in to the Admin/Type application.
Expand the Form node.
Select EndItem Master in the Form types list.

Item Data Types
Change the POM class setting to TREndItemMaster.
Choose Modify.
Select EndItem Revision Master in the Form types list.
Change the POM class setting to TREndItemRevMaster.
Choose Modify.
Close the Admin/Type application.
Step 6: Test the EndItem Item type usage.

Choose FileNewItem...
Choose Select Type to display the list of Item Types.
Item Data Types
Select EndItem from the list, then choose Next.

The Select Type dialog changes to the Enter Item Information
dialog.
Enter the following values:
ItemID: EI001
Rev: 001
Name: EndItem Test
Choose Finish.
Choose Close on the New Item dialog.
Expand the Item and Item Revision objects.

Item Data Types
View both Item Master and ItemRevision Master Forms by

selecting them with the Viewer tab active or by double-clicking
them to create dialog windows.
In a subsequent activity, you will use the Item Type Wizard to

customize the New Item dialog so that end-users can provide
Master form values during the creation of new Items.
Item Data Types
Activity: LOV for Item Type Form
In this activity, you will create and attach an exhaustive LOV for the
Customer field of the EndItem Master form.
EndItem Master Form:
Before LOV: After LOV:
LOV parameters:
Name: TR Customers
Value Type: String
LOV Type: ListOfValuesString
Usage: Exhaustive
Values: Customer A
Customer B
Customer C
Customer D
Customer E
Attached to: Customer property of TREndItemMaster type

Item Data Types
Item Type Wizard

Following the definition of Item Types, and definition of their associated
Master forms, the Item Type Wizard may be used to customize the New
Item dialog. The Item Type Wizard is used to add mandatory attribute
requirements to the New Item dialog.
The Wizard is used to identify a subset (or all) of the attributes from either
or both the Master and Revision Master forms that should be considered
mandatory attributes.
ItemMaster Form Data ItemRevision Master Form Data
Item Data Types
Activity: Customizing the New Item Dialog
In this activity, you will use the Item Wizard to

add mandatory attributes to the New Item dialog.
Step 2: Set up custom attributes using the Item Wizard.

Expand the Item node and select the EndItem type.
Select the icon.

This invokes the Custom Attributes Wizard dialog.
For Step 1, leave Add an attribute selected.
Choose Next.

Item Data Types
For Step 2, define the following Custom Attributes:
When finished defining the attributes, choose Next.
Item Data Types
For Step 3, choose Yes.
Choose OK on the Add Custom Attribute(s) dialog.
You are returned to Step 1 of the Wizard,
Choose Close to terminate the Wizard.
Step 3: Observe the stored definition of the Custom Attributes.

Choose the icon.
Select General... from the query selector.
Clear all Fields .
Enter item types custom attributes in the Name field, then
execute the query .
Close the Search panel.
Expand the Item Types Custom Attributes folder in the

General...(1) tab.

Item Data Types
Open the Item Type Custom Data Text dataset.
Review the contents of the file, then close the text editor.
The Item Type Custom Data dataset stores the custom
attribute setup you performed using the Item Wizard in the
Type application. You had to find the folder (and dataset) since
the folder is referenced by default in infodbas Home folder.
Step 4: Test the Setup.

Select your Home folder and choose FileNewItem...
Select Item for the Item Type.

Notice the Enter Item Master Information and Enter Rev
Master Form Information listings do not appear as mandatory
input (no triangles).
Select EndItem for the Item Type.

Notice that now the Enter Item Master Information and Enter
Rev Master Form Information listings appear as mandatory
input (triangles).
Item Data Types
With the EndItem type selected, choose Next.
Choose the Assign button to automatically assign the ItemID

and Rev, then enter Test for the Name.
Notice that all mandatory fields are now highlighted.
Choose Next.
Choose Yes to create the Item.

Item Data Types
Fill out the Item Master Form by selecting Customer A.
Choose Next.
Fill out the Rev Master Form by entering 12345678 in the

Contract field.
Choose Finish to create the EndItem.
Close the New Item dialog.
Expand the newly created EndItem and EndItem Revision and

open the EndItem Master and EndItem Revision Master forms.
Notice the existing values stored on these forms you provided on

the pre-set mandatory forms of the New Item... dialog.
Item Data Types
Summary
In this lesson you:
Created Item Types
Created POM Classes for Form data
Added mandatory attribute requirements for the New Item dialog

Lesson
5 Dataset Types
Purpose
The purpose of this lesson is to establish new Types for Dataset objects in
your Teamcenter Engineering database environment.
Objectives
Create a new Dataset Type using the Dataset Type Wizard method
Create or modify a Dataset Type using the standard method

Dataset Types
Creating Dataset Types
... Teamcenter Engineering is shipped with some existing Types for Datasets
that are ready to use for common word processing, spreadsheet, CAD and
visualization file data. Your site may need to manage different types of file
data and use software applications for which there is not a ready to use
Dataset Type defined in base Teamcenter Engineering. If this is the case,
you will need to define new Dataset Types unique to your requirements.

Dataset Objects
Dataset Creation/Modification Process
Creating Dataset Types and Tools
Dataset Types
Dataset Objects
What is a Dataset?
Datasets are objects used to manage file data associated with external
software applications. They typically consist of a single application data file
or logical groupings of application data files. There are numerous Types of
datasets predefined in TcEng. However, your site may need to add more
Types to be able to manage your sites specific application data files and the
viewing/editing software applications associated with these files.
What are Named References?

Named References are TcEng objects that relate to a specific data file. A
single dataset object may have one or more Named References. To view the
Named References of a Dataset from Portal, select the Dataset object and
choose ViewNamed References... from the Portal pull-down Menu area.
Named References can also be viewed from the pop-up menu when using the
right mouse button on a Dataset object.

Dataset Types
Dataset Creation/Modification Process

The standard dataset creation/modification process (also referred to as the
Generic Shell process) is described as follows:
When a new dataset is created, initially there are no Named References
for the dataset or physical files stored on a Teamcenter Engineering
volume.
When a Portal user Opens the new dataset, the following chain of events
take place:
If the user has write access to the dataset object, an implicit (automatic)
check-out occurs. Thereby the user maintains exclusive write access to
the data during the modification session.
What happens next is not directly visible to the user:

Teamcenter Engineering creates a temporary operating system (OS)
directory in the %IPR%/temp directory. %IPR% is defined in the Portal
start-up script (portal.bat for Windows).
Since initially there is no file associated with the dataset, Teamcenter

Engineering will create a 0-size file and Export the file to the temporary
OS directory. The format of the file (binary/text) and the extension of the
file are as defined in the References part of the dataset type definition.
Teamcenter Engineering executes the OS software application associated

with the Dataset Types corresponding Teamcenter EngineeringTcEng
Tool definition and passes the file to the application as a Parameter.
What the user sees:

The OS software application executes with the 0-size file loaded.
The user modifies the file using the OS software application.
When a modified file is saved (without terminating the application), the

modified file is written back to the temporary OS directory overwriting the
initial Exported 0-sized file. Each save performed (without terminating
the application) continues to overwrite the file in the temporary directory
without updating the data file stored in Teamcenter Engineering.
The user terminates the OS software application.
Dataset Types
What happens next is not directly visible to the user:

TcEng senses that the application process has terminated and checks the
temporary OS directory to see if the file it originally Exported there has
been changed or if new files have been added to the directory.
If there are changed or new files, TcEng will Import these files back to
TcEng and create the next Version of the dataset object.
The implicit check-out on the dataset object is reversed (implicit check-in).
If the dataset is opened again, the same process is repeated with the exception
that the current file for the dataset is Exported instead of a 0-size file.

Dataset Types
Creating Dataset Types and Tools

There are three methods to create new Dataset Types and Tools in
The Wizard Method (GUI)
The Standard Method (GUI)
Using the make_datasettype command line interface utility
Regardless of the method used, the procedure to create a dataset type will
require you to create or define the following:
Dataset type name - What you specify as the Dataset type name is what
the end-user will see when choosing the Type from the New Dataset dialog.
The Type name is also useful during searches and is used to specify a unique
GUI icon for the Type.
Dataset type description - This is optional information you can provide to
describe the purpose or function of the Dataset type.
References - A Reference definition consists of the following:
A default Reference name for each Reference associated with the dataset
type
Whether the Reference is a File or Object (e.g. Form)
File template naming restrictions (e.g. *.txt, *.pdf)
Format of the file (either TEXT or BINARY)
Tool - The term Tool describes a software application behaving in a

specific manner. The Teamcenter Engineering Tool definition relates to the
OS application by specifying the MIME/Type definition for the software
application on the workstation.
Parameters - When using the parameters dialogs you will identify the
behavior of Operations (Open, Open..., Print, etc.) by specifying which
files to export during an Operation and what Parameters to pass to the
Tool during the operation.
Dataset Types
Activity: Dataset Type Using the Wizard
In this activity, you will define a new Dataset Type and Tool using the
Dataset Type Wizard.
Step 2: Create the new Dataset Type using the Wizard.

Select Dataset in the Types listing.
Choose the Wizard icon.
The Dataset Types Wizard dialog appears.
For Step 1, enter the following:
Name: WizText
File Template: *.txt

Dataset Types
Choose Next on the Wizard dialog.
For Step 2, select Define a new tool, then choose Next.
For Step 3, provide the following Tool parameters:
Name: WizTextEditor
Format: ASCII
MIME/Type: text/plain
Dataset Types
Choose Next.
For Step 4, choose Yes to define the Tool, create the Dataset
Type, add the Reference Type and add the Open Action.
The Dataset Type Created message appears.
Choose OK.

Dataset Types
Expand the Dataset and Tool Types to see the additions.
Step 3: Test the new Dataset Type.

Select your Home folder, then choose FileNewDataset...
Dataset Types
Use the More... link to locate and select the WizText Type.
Enter test wiztext in the Name field.
Choose OK.
Double-click on the new dataset to open it in a text editor.
Enter some text.
Save the file and exit the text editor.
Open the dataset again to verify that the text you added to the
file was saved.

Dataset Types
Activity: Creating Dataset Types Using the Standard Method
In this activity, you will define a new Dataset Type and Tool using the
Standard (Non-Wizard) approach.
Step 2: Create the Tool.

Select Tool in the Types list.
Enter StdTextEditor for the Tool name.
In the Formats section, enter ASCII in the Input field, then

choose the icon.
Enter ASCII in the Output field, then choose the icon.
Enter text/plain in the MIME/Type field.
Dataset Types
The Tool definition dialog should look like the following:
Choose Create.
Verify StdTextEditor appears in the Tool listing.

Dataset Types
Step 3: Create the Dataset Type.

Select Dataset in the Types list.
Enter StdText in the Dataset type name field.
In the Tools panel, select StdTextEditor in the List of defined

tools.
Choose the icon to move the tool to the List of selected

tools.
The dialog should look like the following:
Choose Create.
Dataset Types
Step 4: Define References for the Dataset Type.

Locate and select StdText in the Dataset list.
Choose the References button in the dialog.

The References dialog appears.
Choose the icon to define a Reference.
In the row added to the dialog, enter/verify the following

parameters:
Reference: Text
File/Object: File
File: *.txt
Format: TEXT

Dataset Types
Choose OK.
Step 5: Define Parameters (and Operations) for the Dataset Type.
Choose the Parameters button in the dialog.
Select StdTextEditor in the Tools list.
Verify the Operations setting is Open.
In the References List, check the boxes for Select and Export.
In the Parameters List, choose the icon.

The row in the parameters list acts as a pull down box.
Double-click the row and select $Text from the list.

$Text is the Reference you defined during the
previous step of this activity.
Dataset Types
Choose Create to finish defining the Open operation

parameters.
Notice the addition of the Open operation to the StdTextEditor
tool in the Tools list. Although two listings for Open may
appear, only one will remain after closing the dialog.
Choose Close to close the Parameters dialog.
Step 6: Test the new Dataset Type.

Select your Home folder and choose FileNewDataset...

Dataset Types
Use the More... link to locate and select the StdText type.
Enter test stdtext in the Name field.
Choose OK.
Double-click on the dataset to open it in a text editor.
Add some text.
Save the file and exit the text editor.
Open the dataset again to verify your edit to the file was
indeed saved.
Dataset Types
Summary
In this lesson you:
Created a Dataset Type using the Dataset Type Wizard
Created a Dataset Type using the Standard Method

Lesson
6 Product Structure Data Types
Purpose
The purpose of this lesson is to setup the Teamcenter Engineering database
with Types that model Product Structure.
Objectives
Create Item Unit of Measure Choices
Create Specialized Note Types for Product Structure Occurrences
Extend Types for PSView Objects
Set Product Structure Related Preferences

Product Structure Data Types
Creating Product Structure Types
... so you can perform the Teamcenter Engineering database setup for Product
Structure storage and usage.
Units of Measure, Note Types, and BOMView Types are used with
Items and PSE Occurrences of Items to enable users to define
Bill of Material (BOM) data within Teamcenter Engineering.

Units of Measure
Occurrence Note Types
BOMView Types
Units of Measure
By default, Items have no Units of Measure (UOM). This implies that Item
quantities are expressed in terms of each or pieces. In other words they refer
to a discrete number of component parts. Additional Units of Measure may
be needed to define an accurate Bill of Material (BOM).
Units of Measure (UOMs) are created so that Items and Item Revisions can
be expressed in standardized units (e.g., inches, millimeters, etc.) across an
entireTeamcenter Engineering site. When a user chooses the selector in the
Unit of Measure field of either the New Item (Revision) or Properties dialogs,
the user is restricted to entering one of the pre-defined values.
Choosing Units of Measure from the Type application dialog displays the
Units of Measure fields.
The Symbol field is for the Unit of Measure symbol.

The Name field is for the Unit of Measure name.
In PSE, if no specific quantity value is associated with Items, the
default quantity is 1 component.
In PSE, if UOM is anything other than <null>, the component will

not open in NX.

Units of Measure you will define in your system:
Units of Measure
Symbol Name
in inches
oz ounces
The Symbol in will be used to specify linear quantity of certain

materials in a BOM and the Symbol oz to specify the quantity of
certain bulk materials.
Activity: Creating Units of Measure
In this activity, you will create various Units of Measure.
Step 2: Create two Units of Measure.
Select in the Types Tree.

The Unit of Measure fields appear.
For Symbol, enter: in
For Name, enter: inches
Choose Create.
For Symbol, enter: oz
For Name, enter: ounces
Choose Create.
The new Units of Measure have been created in the database.

Occurrence Note Types

Occurrence Note Types may be associated with an Occurrence in a PSE Bill of
Material (BOM). Users will then be able to specify a value for any Note Type
that has been defined for the site.
The Occurrence Note Types that are defined will be listed in the PSE
Columns, BOMLine Properties, and Notes Editor dialogs. The user can use
any of these dialogs to enter a value for a particular occurrence.
Choosing Note from the Type application dialog displays the Note Type fields.
Note type name This field is for the Note Type name.
Note description This field is for the Note Type description.
Attach Value List? This is initially set to No. If toggled to Yes, the
dialog will change to allow you to define a list of values for the Note type.
Default value: This allows you to define a default value whether or

not a List of Values is used.
The initial list of Note Types shown are standard Note Types
supplied with the system that are required for Teamcenter
Manufacturing and for synchronizing object attributes from NX.
These should not be deleted.
Note Types you will add to your system:

SFCode This Note Type is used to apply a three digit numeric finish
code in accordance with standard material processing requirement
documentation.
Note type name SFCode

Note type description Standard finish code
Attach Value List? No
Default Value <none>
List of Values <none>
ICode This Note Type is used to apply a two character code to an

occurrence in the BOM to identify a condition where it is either "required"
or "suggested" that the component not be modified during assembly
fabrication. IR is used to identify "Interchangeability Required" and IS is
used to identify "Interchangeability Suggested"
Note type name ICode

Note type description Interchangeability code
Attach Value List? Yes
Default Value IR
List of Values IR
IS

Activity: Creating Occurrence Note Types
In this activity, you will create Note Types in your database.
Step 1: Create the SFCode Note Type.
Select in the Types tree.

The Note Type fields appear.
For Note type name, enter: SFCode
For Note description, enter: Standard finish code
Leave Attach Value List? set to No.
Choose Create.
Step 2: Create the ICode Note Type.

For Note type name, enter: ICode
For Note description, enter: Interchangeability code
Toggle Attach Value List? to Yes.
In the Value field, enter IR, then choose the + icon.
In the Value field, enter IS , then choose the + icon.
In the List of Values section, select IR.
Choose the Set Default icon.

Notice that IR appears (greyed out) in the Default Value field,
just above the List of Values section.
Choose Create.
The new ICode and SFCode Note Types have been created in
your database.

PSView Types
A PSView type is a definition that controls the name of a PSView object. The
PSView object works with an Item and Item Revision to maintain product
structure information in Teamcenter Engineering.
Default View Type Named "view"

Choosing View from the Type application dialog displays the PSView type
name field.
The default configuration is a single PSView type defined for the entire
site called view.
During the class, you will add another PSView type entry and change the
generic view type name to engineering.
This should be done before importing any parts (Items). The
ps_rename_bvrs utility can be used to change any existing
PSView type names.
Multiple View Types

Consider a site that has used PSE primarily for modeling engineering data. If
transitioning to multiple PSViews, this site should consider renaming view
to something that will be more meaningful in the context of multiple PSViews
and that will also appropriately describe the legacy product structure data.
In this case, engineering might be a good choice. This would allow another
PSView such as shipping to be defined. From that point forward, different
groups and users could use the most appropriate PSView to model their data.
Related Preferences
In the IMAN_DATA/.iman_env file, the default PSView type is set for PSE
with the PSE_default_view_type preference. Initially, this preference is
set to the following:
PSE_default_view_type=
view
In the IMAN_DATA/.iman_env file, the default PSView type is set for

Unigraphics with the IMAN_UG_View_Type preference. Initially, this
preference is set to the following:
IMAN_UG_View_Type=
view
If you rename and/or add View Types, these preferences may need to be
changed to other values.

Activity: Creating PSView Types

In this activity, you will change the Default View Type from the default
installation PSView type named view to a more meaningful name,
engineering.
Additionally, you will create one more PSView Type named shipping.
PSView Types you will define:
PSView Types
PSView type name Purpose
engineering represents engineering view of product
shipping represents shipping view of product
Step 1: Rename the view PSView type to engineering.

Enter the Admin/Type application.
Double-click in the Types tree to expand and see

the View types.
Select view from the list.

The PSView type name field appears with view listed.
Change the name from view to engineering.
Choose Modify.
Step 2: Create a new PSView type.

In the PSView type name field, enter shipping.
Choose Create.
Step 3: Modify .iman_env to show the new engineering PSView type.

Locate the .iman_env file in the IMAN_DATA directory.
Open the .iman_env file in a text editor.
Search for the IMAN_UG_View_Type preference.
Change the IMAN_UG_View_Type preference setting from

view to engineering.
Search for the PSE_default_view_type preference and change

this setting from view to engineering.
Search for ItemRevision_DefaultChildProperties preference

and change the view setting to engineering.
Save and exit the .iman_env file.

Summary
In this lesson you:
Created Item Unit of Measures
Created Occurrence Note Types
Created BOM View Types
Modified Product Structure Related Preferences
Lesson
7 Queries and Reports
Purpose
The purpose of this lesson is to set up the Teamcenter Engineering database
with predefined queries and reports.
Objectives
Create New Queries
Manage End-User Access to Queries
Understand the basics of Full Text Search setup and execution
Import a Query
Create Reports

Queries and Reports
Creating Saved Queries
... so that you can create Saved Queries that can be used by end-users.
To show you how to create Saved Queries, this section will create a query
to find all Home folders in the database. This type of query is useful for
the Administrator since occasionally there is a need to work with all the
users Home folders.
Also this section will show you how to set ACLs on an object to make the
object read-only to a System Administrator. Specifically, the new Saved
Query should not be readable by all users, so the ACLs are set to block read
for all users.
Defining Saved Queries
Saved Queries Access to Other Users
Queries and Reports
Defining Saved Queries

One of the most important features that any PDM solution can provide is
the ability to search the database for various kinds of product information.
Generally, the more powerful and flexible the search capabilities, the easier it
is for you to quickly find product information in the database.
Teamcenter Engineering searching functions are found using the

icon in the My Navigator application.
The Teamcenter Engineering search feature is a flexible general-purpose

query engine that allows you to search the database for many kinds of data.
In order to enhance usability, the search feature allows queries to be saved as
query forms for future use.
In most cases, the Teamcenter Engineering administrator will
create query forms for the entire site.
In order to enhance usability, your site may want to limit the

number of query forms saved in the database and/or restrict the
number of users allowed to create, modify and delete query forms.

Queries and Reports
Teamcenter Engineering Properties for Workspace Objects

In order to create Saved Queries, you must understand the Teamcenter
Engineering database class structure and the attributes defined on each
class. Since there are many classes in the database, each with many
attributes, we will begin with understanding the WorkspaceObject class.
The WorkspaceObject class defines the common attributes of all the
workspace objects: folder, form, dataset, Item, Item Revision.
Some other attributes for the WorkspaceObject class are inherited from
parent classes, but where these attributes are actually defined does not
concern us at this time.
Below is a diagram showing all the WorkspaceObject attributes.
The attributes without

the + symbol can be
directly set when searching
for WorkspaceObjects.
The attributes with the +

symbol refer to another class
in the class structure, which
may have direct attributes , or
may have more attributes with
+ symbols... this gets complex
and is saved for a later course.
The Name and Type attributes are defined directly to the WorkspaceOject
class. In a search that you will define in an activity, all workspace objects
with Name=Home and Type=Folder will be found.
Query Builder Dialog

The Admin/Query Builder application displays the Query Builder dialog.
This dialog allows you to create, modify and delete queries.
Queries and Reports
Elements of the Query Builder Dialog
Element Description
Name Name of the saved query that you selected from the
Saved Query.
Description Text field where typically information about what
the query does or other pertinent information is
recorded.
Import Imports a query definition from a XML file.
Export Exports a query definition to a XML file.
Search Class icon You will click this icon to access the Class Selection
dialog. This dialog lists all of the schema classes
that are available. You must select a schema class
when creating a query.
Show Hints Displays the dialog window used to select query
hints that assist in navigating the schema and
object relationship.
Local Query Option You will set this option to specify that the query will
be executed against the local database.

Queries and Reports
Remote Query Option Set this option to specify that the query will be
executed against the published objects in the ODS.
Attribute Selection The attributes of the search class displays in the
Tree Attributes Selection tree. Depending on the type
of display setting selected, this tree can display all
inherited class attributes or just the class attributes.
Display Settings: You will choose this icon to indicate how you
want queries to display in the window. The
Display Setting dialog displays with two options.
Class Attributes Set Class Attributes to view only the class attributes.
All Attributes Set All Attributes to view all of the attributes.
Display Names Set Display Names to display the
presentation name of the attribute.
Real Names Set Real Names to displays the actual attribute
name as it appears in the database.
Search Criteria Table Displays the search criteria that can be modified.
Boolean Rules The Boolean Rules (AND/OR) are used to combine
clauses to create a custom query.
Attributes The selected database attribute displays in the
Attributes field.
User Entry L10N Key Specifies the localization key used to look up user
entry names. The localization keys-value pairs are
defined in the qry_user_entry_names_locale.xml
file. The value in this column can be modified.
User Entry Name Displays the query field names as they appear as
labels in the search form. The user name is the
value of the localization key entered in the User
Entry L10N Key column. If the key-value pair is
not defined in the qry_user_entry_names_locale.xml
file, the user entry name is the same as the key
entered in the User Entry L10N Key column. The
value in this column cannot be modified.
Logical Operators Matching values can be: =, !=, <, >, IS_NULL, and
IS_NOT_NULL
Default Values Required when you do not specify the User Entry
L10N Key when creating a query.
Gain Precedence icon Move search clauses up a row in the table to gain
(up arrow) precedence.
Lose Precedence icon Moves search clauses down a row in the table to lose
(down arrow) precedence.
Queries and Reports
Activity: Create a Query that Finds Home Folders
In this activity, you will create a Query to find all the Home folders defined in
the database. This is a useful query for TcEng Administrators. You will use
the Query Builder application to create the query.
The query will use the Folder class with the attributes Name and Type.
Step 1: Start the Admin/Query Builder application.
Step 2: Begin creating the query to find the Home folders.

Enter Find Home Folders in the Name field.
Enter Find all Home folders in the database in the Description

field.
A description must be entered if order for a query to
be seen by Teamcenter Engineering Web Access users.
Step 3: Choose the Query Search Class.
Choose the Search Class selector.
Type in the value Folder, then use the Find Class icon to
locate and select the Folder class.
Close the Class Selection Pop-up dialog ( ).

Queries and Reports
Step 4: Build the Name clause for the query.
Choose the icon.
Set the Display Settings to show All Attributes.
Close the Display Settings dialog ( ).
Double-click Name in Attribute Selection area to add a Search

Criteria line.
Enter Home in the Default Value field, then press Enter.
Step 5: Build the Type clause and then save the query.
Double-click on Type in the Attribute Selection area.
Select Folder from the drop-down list in the Default Value field.
Queries and Reports
The completed query should look like the following. Notice the
AND conditional was used.
Choose Create to save the query.
Step 6: Test the query.

Choose .
From the pull-down menu on the Search panel, choose

RemainingFind Home Folders.
The Search fields now show the Find Home Folders options.

Queries and Reports
Chooses the Execute Query icon.

The Find Home Folders (1) tab appears with the results.
Step 7: Put the Find Home Folders query on your Favorites List.
At the bottom of the Search panel, choose the Options... icon.
Scroll down in the Favorite Options list to locate and check

Find Home Folders.
Choose OK.
Step 8: Test the Favorites setting.

Open the Query selector.
The Find Home Folders query should be on the initial list.
Queries and Reports
Query Access to Other Users

When a new Query is created, the default Rule tree will provide read access
for all users to the query object. The Find Home Folders Query is very
useful for administrators, but you may not want the query to be available
to all users.
The Access... menu allows you to define protections on a query form.

Selecting a query from the list and choosing the Access... menu displays
the Protection dialog for the query.
To modify the current access, the Access Control List icon can be
selected.

Queries and Reports
If you have Change access, the dialog will have an active icon and you can
change the default access definition.
To revoke read access to the World, but maintain read access

for the System Administrator accessor, use these two steps.
1. Add an object-based ACL to maintain read access for the System

Administrator accessor.
2. Add an object-based ACL to revoke read access for the world.
Queries and Reports
Activity: Modify Access of the Find Homes Query
In this activity, you will change the protections on the new query to make
it useable only by Administrators.
Step 2: Show the current ACL Entries on the new Query.

Put the cursor on Find Home Folders and right-click.
Choose Access... from the pop-up menu.
The Access dialog appears.
Choose the Get access control list icon.

Queries and Reports
The Access Control List dialog for the Find Home Folders
query is displayed.
Step 3: Modify the ACL Entries on the new Query.
Choose the icon twice.

Notice the addition of two rows in the list with Object listed
in the Named ACL column.
Queries and Reports
Double-click the empty cells to select the values for the Type of
Accessor and setting for Read privilege as shown in the last
two lines shown in the following image.
The additional World setting revokes read privileges from all

users. The additional System Administrator setting allows
Administrators to use the query.
Choose OK on the ACL Control List dialog.
Choose Close to exit the Access dialog.
With these additional protections, the Find Home Folders

query is only usable (visible) by System Administrators.

Queries and Reports
Activity: Custom Item Type Query
In this activity, you will use the Query Builder application to create a
specialized query for finding Items of Type EndItem.
Step 2: Name and describe the query.

Choose the Clear icon.
Enter the following parameters:
Name: EndItem
Description: Search for EndItems
Step 3: Choose the Query Search Class.
Choose .
Enter Item, then choose the Find Class icon to locate and
select the Item Class.
Close the Class Selection Pop-up dialog.
Queries and Reports
Step 4: Build the Type clause for the query.
Set the to show All Attributes.
Close the Display Settings dialog.
Double-click on Type in Attribute Selection area.

This will add a row to the Search Criteria area.
In the Search Criteria area, clear the User Entry L10N Key.
By leaving User Entry L10N Key blank, the Type
clause will be hidden from the end-user.
Choose EndItem in the Default Value field.
Step 5: Build the Part Number clause.

Double-click on ID in the Attribute Selection area.
Type Part Number in the User Entry L10N Key field.
Leave the Default Value field empty.

Queries and Reports
The end-user will provide the value for this clause

during query execution.
Step 6: Build the Customer clause.

Double-click on Item Masters in the Attribute Selection area.
Locate and select Form in the Class Selection Dialog.
Choose OK on the Class Selection dialog.
Locate and double-click Attributes within the Item Masters

node.
Locate and select TREndItemMaster in the Class Selection

Dialog.
Choose OK on the Class Selection dialog.
Within in the Attributes listings, double-click Customer to

add the clause to the query.
Leave the Default Value field empty.
Step 7: Build the Shipped clause.

Double-click Shipped in the Attribute Selection area to add the
clause to the query.
In the Default Value field, enter TRUE (all caps), then press
Enter.
The query should look like the following.
Make sure Part Number is still listed in the User Entry L10N
Key field. If not, re-enter it.
Queries and Reports
Step 8: Save the query.

Choose the Create icon to save the query.
Close the Admin/Query Builder application.
Step 9: Test the query.

Enter the Engineering/My Navigator application.
If necessary, choose the icon.
Select the EndItem query from the Query selector list.

The EndItem query fields will appear.
Clear all Fields.
Execute the query.
The query should find all Items of Type EndItem that exist in
your database at this time.

Queries and Reports
Step 10: Put the EndItem query on your Favorites List.

At the bottom of the Search panel, choose Options...
Scroll down the Favorite Options list and check EndItem.
Choose OK.
Step 11: Test the Favorites setting.

Open the Query selector.
The EndItem query should be on the initial list.
Close the Search application by choosing the Search icon
Close all Search results tabs.
Queries and Reports
Full Text Searches

Full-text searches allow you to search for dataset files based on keywords
contained within the files. This type of search is performed using the
standard Keyword Search form found in Teamcenter Engineering.
Installing and Configuring

Before Full Text searching can be possible with Teamcenter Engineering, it
is necessary to install and/or configure the Autonomy Dynamic Reasoning
Engine (DRE) full text search engine. The full text search engine enables
users to specify searches on metadata values, as well as full text retrieval
searches on both metadata and common forms of text data.
As shown in the Teamcenter Engineering Setup Options window, there are
two choices for installing and/or configuring the full text search engine.
1. If Autonomy DRE is not installed and running on the workstation, use

the the Load and Configure Full Text Search (FTS) option.
2. If Autonomy DRE is installed and running on the workstation, use the

Configure Full Text Search (FTS) option.

Queries and Reports
Building search indexes

Once the Autonomy search engine has been installed, indexes need to be
built. This is done using the build_fts_index utility. This utility builds
keyword indexes for the Autonomy search engine on an object-by-object basis.
These indexes enable full-text keyword searching and can index both the
properties of dataset objects and the contents of dataset files. For current
information, the indexes need to be updated on a regular basis.
Supported word processing file types.
HTML, SGML, XML, TEXT, RTF, WML
Adobe PDF, ASCII text, ANSI text
Microsoft RTF, Word
Supported spreadsheet file types.

Microsoft Works and Excel
Supported presentation graphics file types.

Shockwave Flash (with Autonomy Flashslave), Microsoft PowerPoint
See the Teamcenter Engineering documentation for a list of
certified file types and more details on the build_fts_index
arguments.
The following shows the build_fts_index utility and its arguments.

build_fts_index
-u=(username) -p=(password) -g=(group)
-type -ext -filter -workdir -slavedir
-idx -filenumber -lang -query
-entry -value -log -f
-maxresults -maxbatch -report -db
The following example indexes Text type datasets. Only the dataset files with
txt extensions are indexed.
$IMAN_BIN/build_fts_index
-u=username -p=password -g=group
-file=Text -ext=*txt. -filenumber=500
Queries and Reports
Searching
Full Text searches are performed using the standard Teamcenter Engineering
Keyword Search form. To run a full-text search, perform the following steps.
1. Choose the Search button on the My Navigator toolbar.
2. In the Search pane, choose the Keyword Search form from the query list
(located in the upper-left portion of the Search pane).
3. In the Keyword Search form, enter one or more keywords in the Keyword
field.
Boolean operators, bracketed expressions, and partial words combined
with wildcard characters can be used to define the search parameters.
Searches for partial keywords without wildcard characters is not
supported. In addition, the keyword search is not sensitive to type case.
4. Choose the Execute this query button.
The system then executes the search with the results being displayed in
a separate tabbed pane.

Queries and Reports
Importing/Exporting Queries
Query definitions can be exported and shared with other Teamcenter
Engineering sites. Conversely, query data from other Teamcenter
Engineering sites can be imported into your site. Exported queries must be
saved as XML files, with the .xml extension.
Importing a query definition is the most critical action. The XML files to
be imported are first parsed and verified before the data is allowed to be
imported. Even if the query data is correctly formatted in the XML file, it may
not be compatible with the local database schema. An incompatible import
file will result in errors when you attempt to create the query definition.
The following are key icons used in the Import dialog.
Import file used to locate the query file in

the OS directory structure.
Verify used to validate the POM class

matches existing classes in the database
before importing.
Queries and Reports
Activity: Import a query
In this activity, you will import a query that will be used in a later lesson. The
query will be used to evaluate user input on the ItemRevision Master form.
Step 1: Begin the query import process.
Start the Admin/Query Builder application.
If necessary, choose the Clear icon.
Step 2: Import a query.

Choose the Import button.
In the Import dialog, choose the Import File icon.
In the Read Query Definition window, navigate to the

workflow_designer folder in the aa_class directory.
Select the user_data_3_equal_MAKE.xml file, then choose

Import.
The query is loaded into the Import dialog.

Queries and Reports
Choose Verify to validate the classes.

Since the query to be imported has POM classes that match
the existing classes in the database, no errors are reported.
Choose OK to import the query.
To activate the Create button, select anywhere in the bottom

listing (blue field).
Choose Create.
The imported query is now displayed in the query list.
Queries and Reports
Creating Reports
Once a Query is created, it can be used in the design of a Report. This
is accomplished by using the Report Designer application in the Admin
application group.
Report Design objects are templates, used by the Report Wizard in My
Navigator, that allow users to extract information from the Teamcenter
Engineering database. Report designs consist of three components:
Saved query definition object
Property format finder (PFF) object
Format file (optional)
Saved Query Definitions
Saved queries are used to search for the values of direct or reference attributes
associated with a class in the Teamcenter Engineering Persistent Object
Manager (POM) schema. Saved queries are used to construct report designs.
The query definition window can be accessed from Report Designer, allowing
you to modify or create definitions without leaving Report Designer.
Property Format Finder (PFF) Objects
Property Format Finder (PFF) objects allow you to gather and report data
related to the objects returned by a query. PFF objects provide the necessary
links and relationships required to locate data without reformatting the query
instance. These objects also enable you to acquire additional information that
a single query would be incapable of rendering.
Report Formatters
Microsoft Excel (.xlt) and Extensible Stylesheet Language (.xsl) files can be
imported into and edited from within Report Designer. When generating
reports in My Navigator, users optionally select one of the files associated
with the design to format the report data. If a format file is not selected, the
data is output as a comma-separated file.

Queries and Reports
The Report Designer window is divided into two main panes, the report
design tree pane and the report design definition pane.
There are four main functions that can be performed in the Report Designer
application.
Launch query definition window.
Launch property format finder (PFF) editor.
Import defined formatter.
Open formatter.
Queries and Reports
Activity: Create a Report using the EndItem query
In this activity, you will create a report using the EndItem query that was
created previously.
As a reminder, the EndItem query allows you to find all EndItems with a
particular Part Number, Customer Name, and whether the Item has been
Shipped or not.
Step 1: Begin the report creation process.

Start the Admin/Report Designer application.
Select the Report Designs folder.
Enter EndItem Report in the Design Name field.
Enter This report returns needed EndItem information in the

Design Description field.
From the Saved Query pull-down list, select EndItem.

At this point, the fields should look like the following.

Queries and Reports
Choose the Query Definition icon.

This launches the Query Definition window, which is the same
as the Query Builder window. This shows the definitions for
the existing EndItem query.
Choose to close the Query Definition window.
Step 2: Create the Property Format Finder (PFF) object.
Choose the Property Format Finder icon.
Queries and Reports
The Property Format Finder window appears.
Step 3: Adjust the Properties Format Finder window.

Dislodge the window by double-clicking on the top (grey) bar.
The window is now dislodged (top bar is blue) and will allow
adjustments.

Queries and Reports
Stretch the window until all panels are easy to view.
Step 4: Create the EndItem report PFF.
Select the Admin - Object Ownership listing.

You will use this PFF as the basis for the EndItem PFF.
Enter EndItemPff in the Name field.
Change the Description to: This Pff defines what object

attributes are included for the EndItem report.
Leave Principle Query Object and Add Clauses From set

to WorkspaceObject.
In the Search Criteria section, select the

WorkspaceObject.object_type listing, then choose .
Queries and Reports
Again, in the Search Criteria section, select the

WorkspaceObject.last_mod_date listing, then choose .
The window should now look like the following, with only five
listings in the Search Criteria section.
In the Property Selection panel, double-click on Object.

Queries and Reports
A new listing appears at the bottom of the Search Criteria

panel.
Select the new WorkspaceObject.object_string listing

in the Property Path column and change the name to
WorkspaceObject.item_id.
Change the Column Names field to EndItem.
Move this new listing to the top by using the up arrow.

Moving this new listing to the top will make it appear
in the left column of the report.
The Search Criteria section should now look like the following.
Choose Create.
Queries and Reports
The new EndItem PFF appears in the list.
Close the Property Format Finder window.
Step 5: Assign the new PFF and Report Formatters.

The new EndItem PFF can now be displayed in the list Property
Finder Formatter field.
Choose EndItemPff from the pull-down list.
From the list of Defined Formatters, double-click on

default_xml_template.xsl.
This sends it to the Selected Formatters panel.

Queries and Reports
The Report Designer window should now look like the

following.
Choose Create.
The new EndItem Report appears in the list.
Step 6: Test the report.

Choose ToolsReports.
The Report Creation Wizard appears.
Queries and Reports
Select EndItem Report from the list.
Choose Fill in Criteria (from list on the left).
If necessary, choose the More... link to show all the fields.
Clear all the fields.

Queries and Reports
Choose Select Format to list the available report (output)

formats.
Choose Finish. (Do not select default_xml_template.xsl.)

The alert window displays the number of object found.
Choose Yes to create the report.
Queries and Reports
The Report Dialog appears.
If the default_xml_template.xsl format file had been selected

before choosing Finish, and if an html viewer was available,
the following report would have been generated.
Close the Report Dialog.
Close the Report Creation Wizard.

Queries and Reports
Summary
In this lesson you:
Created New Saved Queries
Managed End-User Access to Queries
Reviewed the basics of Full Text Search setup and execution
Imported Queries
Created Reports
Lesson
8 Status Types and Revision Rules
Purpose
The purpose of this lesson is to set-up the Teamcenter Engineering database
Release Status types and Revision Rules.
Objectives
Create Status Types
Create Revision Rules

Status Types and Revision Rules
Creating Status Types and Revision Rules
... so that you can continue the Teamcenter Engineering database setup
for data necessary to support Workflow and Configuration Management
functions.
The Status Types and Revision Rules are used for the Workflow modules and
configuring product structure in PSE and Unigraphics. The configuring is
based on the Status.
Status Types for Release Status
Revision Rules Review
Revision Rules Setup
Status Types for Release Status
Review of Release Status
A Status Type (or Release Status) can be set on almost any Teamcenter
Engineering data upon completion of a release. An objects properties reflect
the status by name and the Release Status date. The dialogs below show data
that has been released to a Status Type named Released.
Release Status set on data
Release Status utilized by Revision Rules

NX Load Options
Revision Rules used by PSE

After parts have been released, the Product Structure Editor (PSE) can
be used to display different Bill of Materials (BOMs) in different stages
of development. PSE can also display Work-in-Process parts, which are
those that have not had a final Release Status applied. PSE (and the UG
integration) can load assemblies based on the Release Status list of Status
Types.
Create the Status Type

Status Types are created from the Admin/Type application. You must be a
System Administrator user to be able to create or modify Status Types.
Expanding the Status Type icon will display the current list of Status types
for your site. To create a new Status Type, select the Status Type icon, Fill in
the Status Type name and choose the Create icon.
Status Types are created with a character Name value. The Name value is
set to an objects Release Status attribute when the object is released. The
actual names of the Status Types are arbitrary and in practice would be
defined by your company.
Status Types you will create during the training class
Name Purpose
Released Applied to Item Revisions that represent
Part data that have been approved for
Production usage.
Pre-Released Applied to Item Revisions that represent
Part data that have not been approved for
Production usage but have been released
to freeze the data. This status is typically
used when preliminary data has been made
available for supplier usage.
Approved Applied to Item Revisions that represent
Document data (i.e. Change Proposals,
Product Specifications)
ECPending Applied to Item Revisions that represent
Part data that have progressed through the
first step of an Change process. This status
is renamed to Released at the end of the
Change process.

Activity: Create Status Types
In this activity, you will create four Status Types necessary for use in Release
Process and Revision Rule definitions.
Step 2: Create a Status Type.
Double-click in the Types tree to expand the list.
Enter Released in the Status type name field.
Choose
The new Status Type displays in the Types tree.
Step 3: Repeat Step 2 to create the Pre-Released, Approved, and

ECPending Status Types.
When finished, the Status list should look like the following.
You now have Status Types defined in the database.
Revision Rules Review

A Revision Rule is a set of parameters that determine which revision of an
Item is loaded into a particular PSE window or Unigraphics session. A preset
Revision Rule is a named Revision Rule with various settings that has been
defined by a privileged user, and made available to certain other users.
Item Revision configuration selects which one of the revisions of an Item is to
be configured (i.e., meets the criteria in the Revision Rule).
Revision Configuration Terms

Imprecise Assembly - A single-level assembly that has Items as the
components. The particular Revision is determined by the Revision Rule
settings.
Precise Assembly - A single-level assembly that has specific Item Revisions
as the components. It is also subject to the Revision Rule, but the precisely
specified Item Revision is configured by a Precise entry in a Revision Rule.
Revision Rule - The parameters set by the User that determine which
Revision of an Item is loaded into a particular PSE window. A Revision Rule
can also be saved as a Workspace object for use in other applications.
Rule Entry - A Revision Rule is made up of an ordered list of Rule entries.
Each type of Rule entry is concerned with a particular type of configuration.
Override List - The User places Item Revisions in a Workspace folder that
is referenced from the Revision Rule and used to override the revision that
would normally be loaded by the Revision Rule.
Release Status - An attribute assigned to an object after successfully going
through a release. Item Revisions can be configured according to their status.
The status can optionally contain effectivity data for revision configuration.
Working Revision - A revision that can be freely changed by a User with
write privileges. No record of intermediate states of a working revision is
maintained by Teamcenter Engineering.
The Revision Rule must always be set to determine which revision to load into
PSE. The variant and occurrence effectivity configuration rules are optional.

Revision Rules Provided with Teamcenter Engineering
Name Description
Any Status, No Working Selects the latest released revisions, no working
revisions selected.
Any Status; Working Selects the latest released revisions, if none exist,
then select working revisions. This is useful when
you want to configure a released structure, but
want to be aware of items that will become used in
the structure, but are not released yet.
Latest Working Selects Precise references if they exist, and for
Imprecise assemblies, selects the latest working
revisions, if none exist, then latest released
revisions.
Latest by Alpha Rev Selects the latest revisions according to the
Order revision id, sorted alphanumerical, regardless of
whether they are working or released.
Latest by Creation Date Selects the latest revisions according to the date
they were created, regardless of whether they are
working or released.
Precise Only Selects the precise references to specific item
revisions in Precise assemblies.
Precise; Any Status Selects the precise references to specific item
revisions in Precise assemblies. If Imprecise
assemblies are present, the latest revisions with
any status are selected.
Precise; Working Selects the precise references to specific item
revisions in Precise assemblies. If Imprecise
assemblies are present, only working revisions are
selected.
Working (Curr Group); Selects only the latest working revisions owned
Any Status by the Group the User running the Teamcenter
Engineering session is currently logged into,
if none exist, then select the latest released
revisions. This is a simple and powerful Rule
allowing users to configure only the working data
within their team.
Working (Curr User); Selects only the latest working revisions owned
Any Status by the User running the Teamcenter Engineering
session, if none exist, then select the latest
released revisions. This is a simple and powerful
Rule allowing Users to configure only their own
working data.
Working; Any Status Selects the latest working revisions, if none exist,
then select the latest released revisions.
Revision Rules Added during the training class
Name Description
Released Selects the latest revisions with Release Status
of Released, if none exist, then select the latest
revisions with Release Status ofPre-Released,
if non exist, then select the latest working
revision.

Revision Rules Setup

Revision Rules are modified or created from the Engineering/PSE application.
Choose ToolsRevision RulesCreate/Edit... to create, modify, delete, and
copy Preset Revision Rules.
For a new database, this dialog is initially populated with the 11 Revision
Rules shipped with Teamcenter Engineering.
Revision Rules dialog

Use the Create icon to display the Create New Revision Rule dialog. Enter a
Name, set the criteria required, and then select OK to see this new Revision
Rule added to the list in the initial dialog. Note that Revision Rule Names
must be unique.
Use the Modify icon, which will display the same dialog as Create, but
pre-populate it with the Revision Rule Name and the settings that correspond
to the Rule. These can then be modified as required. This also allows the
name of the Rule to be changed.
Use the Delete icon to remove a Revision Rule. This will then be removed
from all users who had access to it.
Creating Revision Rules

This Create New Revision Rules dialog allows users to create Revision Rules.
Default Access Manager Rules shipped with Teamcenter Engineering define
who can Read and therefore use a Revision Rule after it has been created.
If the Revision Rule is created by a member of the dba group, the Revision
Rule will be selectable by all Teamcenter Engineering users (World)
If the Revision Rule is created by any other user, only that user and
System Administrators will be able to view/select the Rule.
Shown below is the Create New Revision Rule dialog.
The upper section allows a name to be entered, which will be the name
the user will see.
The middle section is the area where entries are ordered and possibly
grouped
The lower section is where Rule entries are constructed and modified.

Revision Rule Entries
A Revision Rule is made up of a sequential list of entries. Evaluation of the

Rule involves evaluating each of the entries, in top-to-bottom order, until a
configured revision of the Item is successfully obtained. Once a revision is
found that satisfies an entry, the evaluation of entries below that entry is
stopped. A Revision Rule may be made with any combination of the following
entry types.
Working - A Working entry is used to select working Item Revisions (those

without any Release Status). The latest Working Revision of the Item is
selected according to the date it was created. The revision chosen can be
made more specific via the following settings:
Owning User - If an Owning User is specified within a Working entry,

the latest revision owned by the specified User will be configured (if there
is such a revision). The owning User can be also set to current, meaning
that latest revision owned by the current Teamcenter Engineering User
is configured.
Owning Group - If an Owning Group is specified within a Working

entry, the latest revision owned by the specified Group will be configured
(if there is such a revision). The Owning Group can be also set to current,
meaning that latest revision owned by the Users current Teamcenter
Engineering Group is configured.
More than one Working entry may be present within a Revision

Rule. For example a Rule might try to configure the current
Users working revision, and if none is found configure the
current groups instead. If a User changes their Group, they will
need to re-apply the Revision Rule to configure the appropriate
revisions for the Group they have changed to.
Status - A Status entry is used to select Item Revisions that have been
released with a particular status. The following settings are available for
Status entries:
Any Release Status - The latest Item Revision with status is configured,
regardless of which status it is.
Selected Status - The latest Item Revision with status of the selected
type is configured. Allows you to configure a structure that only contains
Item Revisions that have reached a specified Status. These are selected
from the list of available statuses in the list menu.
More than one Status entry may be present in a Revision Rule.
Release Date - The latest Item Revision is selected according to the date
the revision was released (the date that the particular status was added).
Effective Date - The latest Item Revision is selected according to

effectivity dates defined on the Release Status.
Effective Unit No. - The latest Item Revision is selected according to

unit numbers defined on the Release Status.
Effective Dates/Units are defined by privileged users using
ViewRevision Effectivity... in the PSE application.
Override - An Override entry allows particular Item Revisions to override

those that would be selected by the other criteria. The Item Revisions to be
used are simply copied into a Workspace folder which you then reference from
the Override entry (paste into the entry). You add an Override entry if you
want to create a Rule referencing an Override folder. Typically you will leave
the folder argument blank, which allows Users to set an Override folder at
run time, using the ToolsRevision RuleSet Override folder... Command.
Date A Date entry is used when you want to create a Revision Rule which
confiures at a specific data or Today. This will prevent Users from setting
a data (using Revision RuleSet Date) to configure by at run-time. If you
want a Revision Rule which allows Users to set the date, then do not use a
Date entry.
Unit Number A Unit No entry is used to specify the Unit No to match
against when configuring Item Revision with status using Unit No Effectivity.
This will prevent Users setting a unit number (using Revision RuleSet Unit
No) to configure by at run-time. If you want a Revision Rule which allows
users to set the unit number, then do not use a Unit No entry.

Precise - A Precise entry is used to select the precisely specified Item

Revisions in a Precise BOMView Revision. The entry has no effect on
Imprecise Bills. If you apply a Revision Rule without a Precise entry to
Precise structures, they will be dynamically configured - this can be very
powerful, but could also give unexpected results which may not be desired.
Any entry placed above the Precise entry in a Revision Rule will in
effect override the Precise references.
A Revision Rule containing only a Precise entry can be used to do

purely Precise configuration.
If you want to configure a structure that contains both Imprecise

and Precise assemblies, and you want to configure the precise
references in the Precise assemblies, add a Precise entry at the top
of your Revision Rule. The other entries in the Rule will be used to
configure the Imprecise assemblies.
Latest - A Latest entry is used to select Item Revisions irrespective of
whether they have been released. There is no differentiation between
Working revisions and those with status. The following settings are available
for Latest entries:
Creation Date - The latest Item Revision is selected according to the
date the revision was created.
Alphanumeric Revision ID - The latest Item Revision is selected in

alphabetic order of Revision ID. This will order numeric Revision IDs
alphanumerical, (i.e., 1, 10, 2, etc.).
Numeric Revision ID - The latest Item Revision is selected in numeric

order of Revision ID. Revisions with non-numeric IDs will not be
configured.
Ordering Rule Entries

The order of entries within a Revision Rule is very important. The
top-to-bottom order defines a precedence that will affect the outcome of what
item revision the Rule will configure. Entries at the top of the Rule take
precedence over entries below. As soon as an entry is capable of configuring
an item revision, the entries below are not evaluated.
Grouping Rule Entries

To give entries equal precedence, they may be grouped together with brackets
in the entry dialog.
For example, consider the Rule entries below:
Grouping these entries gives no precedence to item revisions with either of

the defined statuses. The latest item revision with either of the statuses is
configured.

Activity: Create Revision Rules
In this activity, you will create the Released Revision Rule.

Step 1: Start the Engineering/PSE application.
Step 2: Create a Released Revision Rule.

Choose ToolsRevision RuleCreate/Edit...
The Revision Rules dialog is shown with the default Revision
Rule selected.
Select the Precise Only rule, then choose Create.

The Create New Revision Rule dialog appears with the settings
for the Precise Only rule. This rule will be used as a starting
point to create a new rule.
Change the name to Released.
In the middle panel, select the Precise listing.
Choose the Remove button, which is now activated.
Step 3: Add the Status entry for Released status.

Select Status from the Entry Type selector.
Choose the Open by Name icon.

The Open by Name dialog appears.
Enter * in the Status Type field, then choose the icon.

The Released Status Types that were created in an earlier
activity are displayed.
Double-click the Released status.
To add the entry, choose .
Step 4: Add the Status entry for Pre-Released status.
Choose the Open by Name icon again.
Double-click the Pre-Released status.

Choose .
Step 5: Add the Working entry.

Select Working from the Entry Type selector.
To add the entry to the Entry dialog, choose .

The entry dialog should look like this.
Step 6: Save the new Revision Rule.

Click the OK to save your Rule.
The Released Rule should now be viewable from the Revision

Rules dialog.
Choose Cancel to dismiss the Revision Rules dialog.

Setup Considerations
Teamcenter Engineering is delivered with a base setup which allows the
product to be used with the Revision Rule, Latest Working.
To use other Revision Rules, you may consider modifying the following
preferences in the IMAN_DATA/.iman_env file.
The preference below establishes the Revision Rule a user will have in effect
by default. The default could be changed to a different Revision Rule for the
whole site, groups, roles or users.
IMAN_config_rule_name=
Latest Working
The preference below defines the type of BOM (Precise/Imprecise) users will
create by default from PSE and Unigraphics
IMAN_BOM_Precision_Preference=
Imprecise
Activity: Verify Revision Rule Preference Settings
In this activity, you will verify Revision Rule preference settings.

Step 1: Open the IMAN_DATA/.iman_env file in a Text editor.
Step 2: Verify Default Revision Rule setting.

Using the Text editor search/find function, locate the following
preference.
IMAN_config_rule_name=
Latest Working
This sets the user Revision Rule to the shown value by default.
Step 3: Verify BOM Precision preference setting.

Locate the following preference.
IMAN_BOM_Precision_Preference=
Imprecise
This setting defaults all newly created BOMs to either Precise

or Imprecise (the default).
Step 4: Close the text editor.

Summary
In this lesson you:
Created Status Types
Created Revision Rules
Lesson
9 Access Manager
Purpose
The purpose of this lesson is to establish unique data access requirements
using the Teamcenter Engineering Access Manager application
Objectives
Identify access permissions established with the default Access Manager
Create additional Access Manager rules to define Company specific data

access Requirements
Make an exception to the Access Manager rules for an individual object
Save and restore Access Manager rule definitions

Access Manager
Teamcenter Engineering Access Manager

... so that you can setup your database with a secure protection mechanism
for the data created by all the end-users.
The following will be discussed in this lesson.
Teamcenter Engineering Data Protections
Rules-Based Protections
Object-Based Protections
Viewing Data Privileges
Teamcenter Engineering Privileges
How Rules-Based Protections Work
Editing the Rule Tree
Setting Object Based Exception Privilege Data
Exporting and Importing the Rule Tree from a File
Access Manager
Teamcenter Engineering Data Protections

Object protection and ownership are extremely important in a distributed
computing environment. Because objects represent actual product
information in the database, they must be protected from unauthorized or
accidental access, modification and deletion.
Data protections are established with the database and not by the OS file
protections. Teamcenter Engineering implements two different tiers of data
protections:
The Teamcenter Engineering system administrator defines various conditions
or rules that control who can or cannot access various objects. These rules are
global (they affect your entire Teamcenter Engineering site) and are defined
using the Access Manager (AM) application.
As a User interacts with Teamcenter Engineering data, access is determined

by using the Users Accessor information, the objects Meta Data (properties),
and some System information. This information is tested in the conditional
Rule Tree which returns the access results.
This is a great advantage because, in most cases, end-users wont have to
think about explicitly protecting data - it will be done automatically.

Access Manager
Object based protection Access Control Lists (ACLs) can be set on objects to
create exceptions to rules-based protection. Object ACLs are most useful
when you need to either grant wider access or limit access to a specific object.
With Object-Based protections, settings are added to and controlled by the
object to implement case-by-case exceptions to the access defined by the
Access Manager rule tree. After the object is created, Exception protections
or Access Control Lists (ACLs) can be added to the object by anyone
having Change (Key icon) access to the object after the object is created.
Access Manager
Viewing Data Privileges

To view access privileges for an object,
select the object and choose ViewAccess...
... or the ACL icon

The current protections for that object are displayed in the Access window.
The initial protections are determined by the Rule Tree.
When necessary, the ACL button can be selected to show the specific Access
Control List (ACL) that has been derived from the Rule Tree.

Access Manager
Teamcenter Engineering Privileges
Access Privilege Description

Read (R) You can open and view (read) an object.
Write (W) You can modify (write changes to) an object.
Delete (D) You can completely and permanently remove
(delete) an object from the database. Because
this is potentially destructive, delete privilege is
usually only granted to the owner and Teamcenter
Engineering system administrators.
Change (C) You can modify (change) object protections.
Any accessor with change privilege can grant
themselves any other privilege. Therefore,
change privilege should be tightly controlled. For
example, you should not allow another group to
have change privilege on your groups data.
Promote (p) You can move a task ahead (promote it) in a
workflow job.
Demote (d) You can move a task back (demote it) in a workflow
job.
Copy (c) You can print an object, perform a FileSave As
on an object and mark an object for archive.
Change Ownership You can change ownership on an object.
Publish You can make the object available to other
Teamcenter Engineering sites.
Subscribe You can subscribe to an object.
Export (X) You can export objects from your Teamcenter
Engineering database.
Import (I) You can import objects into your Teamcenter
Transfer Out (x) You can transfer ownership of objects exported
from your database.
Transfer In (i) You can become the new owner of objects imported
into your Teamcenter Engineering database.
Write ICOs You can Write in-Class Instances
Access Manager
Activity: View Default Protections
In this activity you will create a new Item and view the default Access
Manager defined privileges.
Step 1: Start the Engineering/My Navigator application.
Step 2: Change your Group/Role.

Choose EditUser Setting...
Make sure Session is checked.
Change Group to high_performance and role to DBA.
Choose OK.
Step 3: Create an Item.

Choose FileNewItem...
The New Item dialog is displayed.
Choose Item as the Type.
Choose Next , then enter the following:
Item ID 1234
Revision 000
Name Test Item
Description (leave blank)

Access Manager
Choose Finish.
A reference to the new Item is placed in your Home folder.
Step 4: Review the Protections of the new Item.

Select the 1234-Test Item.
Choose the Access tool bar icon.

The Access dialog displays your access to the object.
Review privileges on the Item.
Access Manager
A greyed out icon means the privilege is denied.
Step 5: View the Access Control List (ACL) for the Item.
Choose the ACL icon in the Access dialog.

The complete Access Control List displays.
This dialog displays the complete Access Control List for the
1234-Test Item. From this dialog, you can derive any users
privilege setting for this object.
For example, by locating the Write access column , you

can determine that the Owning User and the Owning Group
(high_performance) have been granted Write access ( ) to
the Item and that all other users (World) are denied Write
access ( ).
Choose Cancel on the ACL Control List dialog.
Close the Access dialog.

Access Manager
How Rules-Based Protections Work

This section will explain how rules-based protections work by covering the
following topics:
The AM Rule Tree
Named ACLs and ACEs
Pre-Defined Conditions (Rules)
Accessor Precedence
Building the Effective ACL
The AM Rule Tree
Choosing the Access Manager icon (shown on the left) from the Admin
program group displays the AM Rule Tree window (shown on the right). This
window displays all existing AM rules in force at your site in the form of a tree
in one window pane with named ACL definitions in the other window pane.
When rules-based protections are needed on an object (in choosing

Protections, Opening, Copying, Exporting, etc.) the rule tree is evaluated.
The rule tree evaluation starts from the top and works downward checking
conditions. When the conditions are met, the ACL(s) are applied. The next
page shows the full default rule tree likely to be on your system.
Access Manager
The following is a section of the AM Rule Tree

Access Manager
The Named ACLs

The right side of the Access Manager application displays the Named ACL
pane.
There are numerous Predefined Named ACLs with the default Access
Manager setup. By using the selector to choose a different Named ACL, you
can view/edit the other predefined Named ACLs
Access Manager
Access Rule Tree, Named ACLs, and ACEs

Shown below the Rule Tree and Named ACLs control what protections get
set on objects when accessed by a user. The exact access is based on the
object and the user.
The Rule Tree shows

the conditions and
the Named ACLs
Below, the Named ACLs

show the specific ACEs

Access Manager
Pre-Defined Conditions (Rules)
Condition Value Description

Has Attribute class:attribute=value Eg: Object has the value specified
NoteType:name=UG* for the attribute of the given
class.
Has Bypass true or false User has bypass set.
Has Class class name Object is of this Teamcenter
Engineering class.
Has text string accepts Object has this description.
Description wildcards
Has Form
Attribute
Has Item ID item ID (accepts wildcards)
Has Name text string accepts Object has this name.
wildcards
Has Object true or false Object has an object ACL.
ACL
Has Status status name accepts null Object has this status type
entry (null=all) attached.
Has Type type name Object is of this Teamcenter
Engineering type.
Has View BOMView type name Object is associated with this
Type BOM View type.
In Job true or false Object is a target object in a
workflow job.
In Project project ID Object is a member of the
defined project.
Is Archived true or false Object is archived.
Is GA true or false User is a group administrator
in the current group.
Is Local true or false Object resides in this database.
Used with Distributed
Is Project true or false User is a member of the
Member project.
Is SA true or false User is currently logged in
as a member of a system
administration group.
Owning group name Object is owned by this group.
Group
Access Manager
Owning security string Owning group of the object has

Group Has a given security string.
Security
Owning Site site name Object is owned by this site.
Used with Global TcEng.
Owning User user ID Object is owned by this user.

Access Manager
ACL Buildup - Precedence

Evaluating which privileges are finally granted depends on two criteria:
Precedence of the Conditional Statements in the Rule Tree
Accessor Precedence in the Named ACL
The result is an Effective ACL, which controls the access to the object.
This Effective ACL is the cumulative buildup of all the Named ACLs
appropriate to that object within the Rule Tree.
Precedence of Conditional Statements in the Rule Tree

Use the following steps to build an Effective ACL for an Object.
1. Remove from the Rule Tree all lines with rules that do not apply to the
object. This will usually leave you will only a few lines (rules) to evaluate.
2. The Effective ACL is now built up from those Named ACLs left in the
trimmed tree.
3. Order of traversal of lines (rules) is determined by:

Always visit the children of a line before the line itself.
Always visit sibling children in order from top to bottom.
4. Build up the Effective ACL by putting together the Named ACLs on

the lines (in order of traversal).
Access Manager
Rule Tree Precedence Example
Accessor Precedence in the Named ACL

The following chart lists each accessor in order of precedence.
Approver (RIG)
Approver (Role)
Most Precedence
Approver (Group)
Approver
Owning User
User
Group Administrator
Role in Owning Group
Role in Group
Role
Owning Group
Least Precedence
System Administrator
Group
Project Team
Groups with Security
Project Teams
World
Site
Remote Site

Access Manager
Example: Building an Effective ACL for a UGMASTER dataset

1. Remove from the Rule Tree all lines with rules that do not apply to the
object.
Trimmed Rule Tree
2. .The Effective ACL is now built up from those Named ACLs left in the
trimmed tree.
3. Order the traversal of lines (rules).
Access Manager
4. Build up the Effective ACL by putting together the Named ACLs on

the lines (in order of traversal).
The Effective ACL will be shown to the user as shown below. The shaded
privilege settings will not be seen. The Owning Group row will not be seen
since there are no privileges set in the row.
The shaded privilege settings are not actually shown in the ACL window since
they are already encompassed by a high preceding accessor. Said another
way, the upper World accessor already includes all users, therefore the
privileges defined in the upper World (W, C, c) have been set and do not have
to be shown for the lower accessors of Owning User, Group Administrator,
Owning Group, System Administrator, and the lower World.

Access Manager
Evaluating the Effective ACL for the UGMASTER

Remove all the lines from the Effective ACL that do not apply to you.
Assume you are a Designer in the Owning Group of the UGMASTER dataset.
You are not the Owning User, not generically in the Owning Group, and not a
Group Administrator or System Administrator.
For each privilege work down through the remaining ACL lines until you hit
a Y or a N. This will tell you whether you are granted or denied the privilege.
Therefore you will have these privileges:

Granted: Read, Write, Copy
Denied: Delete, Change, Promote, Demote
Access Manager
Editing the Rule Tree
Guidelines and Recommendations

Do not modify named ACLs referenced by rules on or within the "System
Objects" branch. These rules are used for internal purposes and changes
could result in unpredictable behavior or loss of data.
Do not delete or change the order of the branches in the upper area of the
Rule tree. This could result in unpredictable behavior or loss of data.
Add new rules for working data below the "Working" branch. This is the
proper location to add new rules for working data types at your site.
Named ACLs are optional. When adding a new rule, if you do not enter
a Named ACL you will create an inactive stub that can be further
customized by adding additional rules as sub-branches. Until you add
additional sub-branches or modify this rule to apply a Named ACL, it will
have no effect on object protections.
Browsing the AM Rule Tree

Only users with System Administration privileges can modify Access Manager
rules. To browse the AM Rule tree, select the Teamcenter Engineering Admin
button in the Applications Manager, and then select the Access Manager
application. The AM Rule tree is displayed. To browse the AM Rule tree,
select a Rule tree branch. When it is selected, the rule and its relevant
information is displayed in the Access Manager Rule tree and Rule panel.

Access Manager
Adding an AM Rule to the Tree

1. Select the Parent rule that the new node will be added to.
2. Set the condition, value and named ACL for the new rule.
3. Choose Add.
This creates the new rule and adds it to the selected parent in the Rule tree.
When the rule is added, an asterisk appears next to the Access Manager
name indicating the rule tree has been modified.
4. Choose FileSave (or ) to save the changes to the AM Rule Tree file.
Modifying an AM Rule
1. Select the desired rule to modify in the Rule tree.
2. Set the appropriate values within the Rule pane.
3. Choose Modify.
An asterisk appears next to the Access Manager name
indicating the rule tree has been modified.
Deleting an AM Rule
1. Select the desired rule to delete in the Rule tree.
2. Once the rule is selected, choose Delete .

Access Manager
Moving an AM Rule
1. Select the rule you want to move in the Rule tree.
2. Once the rule is selected:
Choose Move Up to move the rule up one level in the Rule tree.
Choose Move Down to move the rule down one level in the Rule tree.

Access Manager
Activity: Add Access Manager Rule
In this activity, you will use the Access Manager application to add a
Company specific Access rule.
Current Access
With the out-of-the-box Teamcenter Engineering Rule Tree, all objects of class
POM_application_object are granted Write access by the owning user and the
owning group while they are considered working data.
Working data is generally defined as data not in-process or has not been
released (has a Release Status value). The following branch establishes
this in the Rule Tree.
(Has Class) POM_application_object>Working

The class Item is a sub-class of POM_application_object, so we can deduce
that Items are only modifiable by the Items owning user or owning group.
Desired Access
The process for modifying Items requires us to retain owning group Write
access to Items but, in addition, we need to allow the corrective_action group
the ability to make revisions to Items to resolve manufacturing-related
design issues.
For example, the 1234-Test Item shown below was initially created by a
member of the high_performance product definition group as part of a new
product development (1234/000 Item Revision). The part is subsequently
being revised by a member of the corrective_action group to correct a design
deficiency in the manufacturing center (1234/001 Item Revision).
Access Manager
What needs to be done to the Rule Tree?

You may think that a change needs to be made to the Working ACL to add an
Access Control Entry (ACE) that allows the corrective_action group Write
access, as shown below.
However, this would have the affect of allowing the corrective_action group
Write access to all objects of class POM_application_object. This includes any
dataset, folder, form, BOM, etc., created by any group!
This is obviously not desired.
Instead, we want to allow the corrective_action group Write access for Item
objects only (not all objects defined by the POM_application_object class).
To enable this we must do two things:
Create a new Named ACL that grants the corrective_action group Write
access.
Modify the Rule Tree to attach this new Named ACL to the existing
(Has Class) Item... branch.
Step 1: Change your Group/Role to dba/DBA.

Choose the Session listing.
Change your Group to dba and Role to DBA.
Choose OK.
Step 2: Start the Admin/Access Manager application.

Choose the Admin program group icon in the Application
Manager.
Choose the icon.

Access Manager
The Access Manager editor screen appears with the rule tree
and named ACL editor screen is displayed.
Step 3: Locate the Has Class(Item) rule tree branch.

Choose the symbol to expand the following branch.
The node expands and the Has Class(Item) branch is visible.
Step 4: Modify the Has Class(Item) rule tree branch.

Select the Has Class(Item) branch.
The branch editor screen displays the three parts of this branch
definition: The Condition, the Value, and the Named ACL. You
will now create and attach a new named ACL to this branch.
Access Manager
Enter CAMod in the ACL Name field.
Choose the Create icon adjacent to that field.
Next, choose the icon to the right of the ACL contents

window to add the first Access Control Entry (ACE).
Double-click the empty ACE cells to set the values for Type of
Accessor and ID of Accessor, then set the Write privilege (as
shown in the following image).

Access Manager
Choose the Save icon in Named ACL dialog to save the

ACL.
Choose the icon to modify the branch.

The new named ACL has been attached to the (Has Class)
Item branch.
Access Manager
Step 5: Save the modification to the rule tree.
Choose the Save icon on the Access Manager Tool bar.

The complete rule tree/named ACL definition has been written
to an OS file in the IMAN_DATA/am directory.
Step 6: Test the Rule Tree change.

Go to the Engineering/My Navigator Application.

Step 7: View the Access Control List (ACL) for the Item.

Access Manager
You should see the complete Access Control List (ACL) for
the 1234-Test Item. Notice that the corrective_action group
accessor is listed with the Write access privilege granted.
Also, notice that the CAMod ACL is listed above the Working
ACL. This is because the (Has Class) Item branch that
applies the CAMod ACL takes precedence over the (Has
Class) POM_application_object branch that applies the
Working ACL.
Choose Cancel on the Access Control List dialog.
Choose Close on the Access Dialog.
Access Manager
Setting Object Based Exception Privilege Data

While the Rule Tree can be changed to affect protections for the entire site,
object protections can be changed by a user on specific objects. To change an
objects protections, select the object and choose ViewAccess...
You can also use the Access icon from the tool bar.
The current protections (from the Rule Tree) for that object are displayed in
the Protection window for your user account.
The Access Control List ( ) opens another window to list full ACL and
to makes unique object based protection entries.
To change a specific objects protections, select the ACL button at the bottom
of the Protection window to display the Access Control List dialog. If you
have Change privilege, the Add/Delete ACL buttons will be active and you
will be able to Add or Delete an object-based ACE.

Access Manager
To set the exception protection, select the Add icon and a new Access
Control Entry (ACE) will be added to the list. By double-clicking in the cells
of the ACE you can define the Accessor Type, Accessor ID and grant/deny
privileges.
Once added, the object-based ACEs will be identified by the name OBJECT
in the Named ACL column. If you have Change access, you will be able to
Add, Modify, or Delete an object-based ACE.
Access Manager
Activity: Modify Single Object Protections
In this activity, you will define object specific Access Control List data to
remove Write access from a single user.
Step 1: Check your ability to add object specific ACL data.

Notice that you have privilege for the Item.

This privilege allows you to add entries to the default ACL
defined by the Access Manager rule tree. Any additions you
make in this manner will only apply to this object.
Step 2: Add the object specific Access Control List (ACL) data for the Item.

Access Manager
Because you have privilege, the icon is active.

From this dialog you can also identify what AM rule is giving
you the privilege. In this case the Working ACL has
granted to the Owning User (you).
Choose the icon on the Access Control List Dialog.
A new line appears at the bottom of the list with Object listed
in the Named ACL column.
Double-click the empty ACE cells to choose values for Type

of Accessor, ID of Accessor, and setting for Write privilege
as shown in the highlighted line below.
Choose OK on the Access Control List Dialog.
Close the Access Dialog.
Access Manager
Step 3: Test the Object ACL
Select the 1234-Test Item, then choose the Access icon.

Select Astaire, Fran(astairetr) from the User drop-down listing.

The Access dialog updates to display the Access for astairetr.
Notice that Write access is denied for astairetr. If not, re-select

the Field Service Engineer Role to update the window.
Close on the Access Dialog.

Access Manager
Exporting and Importing the Rule Tree from a File

The Access Manager Rule tree can be exported as an ASCII file to a directory
outside of Teamcenter Engineering and, conversely, be imported back into the
Teamcenter Engineering environment.
The export and import feature can be used for the purpose of archiving or
safeguarding a Rule tree prior to making extensive modifications (such as,
adding or deleting branches, relocating branches, and so on). If, after many
modifications, it is found that the original Rule tree is desired, it can be
reinstated.
This capability is also useful for copying the Access Manager rule definitions
from one Teamcenter Engineering site to another.
Rule tree edits from the Access Manager application are automatically saved
in the IMAN_DATA/am directory in the exported file format when the user
chooses the Save icon from the Access Manager application.
Guidelines and Recommendations

Never modify rule tree files with a text editor. Although rule tree files are
simple ASCII files that can be read using any text editor, you must never
modify them with a text editor. These files must conform to a particular
format and can be easily corrupted.
In order to successfully load (read-in) a new Rule tree from a different

Teamcenter Engineering site, your site must have the same types, roles,
and groups as those referenced in the Rule Tree file. If there is any
incompatibility, Teamcenter Engineering will immediately terminate the
read operation (at the first discrepancy) and display an error message. If
you encounter schema compatibility problems when loading a Rule tree
from a file, open that Rule Tree file with a text editor. Either print the file
or make note of the types, roles, and groups referenced in that file. Then,
define these exact types, roles, and groups for your site.
Access Manager
Exporting the Access Manager Rule Tree

From the Access Manager application...
1. Choose FileExport...
A dialog is displayed.
2. Type in the filename for the rule tree being exported and choose a
directory path.
3. Choose Export.
A confirmation dialog appears indicating the export was successful.

Access Manager
Importing an Access Manager Rule Tree

From the Access Manager application...
1. Choose FileImport...
A dialog is displayed.
2. Navigate and select the file to be used for the import.
3. Choose Import.
A confirmation dialog appears to indicate that the import was successful.
Access Manager
Activity: Reset the Rule Tree from a File

In this activity, you will reset your Access Manager Rule Tree to the initial
definition.
Step 1: Locate the Rule Tree definition file.
Using a command window or graphical file navigator, list
the contents of your IMAN_DATA directory and notice the
iman_am_rule_tree.default file.
Step 2: Reset the Rule Tree.

Start the Admin/Access Manager application.
Choose FileImport...
A file browser application displays.
Navigate to the IMAN_DATA directory.
Locate the iman_am_rule_tree.default file.
Select the file, then choose Import.

In a few seconds the Import AMRule Tree dialog appears.
Choose OK.
Step 3: Verify the Import.

Choose ViewRefresh Window.
Choose the symbol to expand the following branch and locate

the Has Class(Item) listing.

Access Manager
Notice the Has Class(Item) branch no longer contains the

CAMod Named ACL.
The complete rule tree/named ACL definition has been written
to an OS file in the IMAN_DATA/am directory.
Step 4: Review the ACL for the Test Item in Navigator.

Select the 1234-Test Item and choose .
Choose the Get ACL button in the Access dialog.

Notice that the entry for the corrective_action group is no
longer present.
However, the object ACL for Fran Astaire is still present.
Resetting the AM rule tree does not remove object-based ACL
entries.
Choose Cancel on the ACL Control List dialog.
Choose Close on the Access Dialog.
Access Manager
Summary
In this lesson you:
Identified Access Permissions Established With the Default Access
Manager
Created Additional Access Manager Rules to Define Company Specific

Data Access Requirements.
Made an Exception to the Access Manager Rules for an Individual Object.
Saved and Restored your Access Manager Rule Definitions.

Lesson
10 Project Creation, Administration

and Control
Purpose
The purpose of this session is to understand the functionality and use of
Projects as they apply to Teamcenter Engineering.
Objectives
Upon completion of this session, you will be able to:
Establish Project Administrators
Create Projects and assign team members
Define security rules for Project data
Add objects to an existing Project

Project Creation, Administration and Control
Projects
Projects allow Teamcenter Engineering sites to control access to objects by
multiple organizations, such as project teams, development teams, suppliers
and customers. Access is controlled on a project by project basis.
Project level security can provide an additional level of security while allowing
non-site employees access to objects in the Teamcenter Engineering database.
Projects are defined by Project Administrators in the Admin/Project
application. After Projects have been created, privileged team members need
to assign Teamcenter Engineering data to the Project using My Navigator in
Portal and the project functionality buttons in Web Access.
While Project is an administrative application, the specific group/role of
Project Administration/Project Administrator is required to create and
modify Projects and Project team members. A system administrator must
populate this group/role in Organization before users intended as Project
administrators can log in to Portal with this group/role and create Projects.
Project creation and administration is done in the following order.
1. A Project Administrator is added to the Project Administration group by
the Teamcenter Engineering administrator.
2. A Project is created with specific Groups, Users or Roles assigned as

Viewers or Privileged Users.
3. As database objects are created, they can be assigned to the Project by

Privileged Users.
The following table lists Project terms and definitions.
Concept Definition
Project Basis for identifying a group of objects available
to multiple organizations (i.e., project teams,
development teams, suppliers, and customers) for
a particular piece of work.
Relation Rules defining how secondary objects are managed
propagation rules based upon its defined relation to the primary
object.
Project Teamcenter Engineering user with privileges to
administrator administer Projects using the Project application.
Creates, modifies and deletes Project information
and team members.
Project team Project team member with privileges to modify
administrator Project information and team members of Projects
to which he has been assigned.
Can assign privileged team members only to
Projects to which he has been assigned as the
Project team administrator. There can be only one
Project team administrator per Project.
Privileged team Project team members with privileges to assign or
members remove objects from Projects to which they have
been assigned.
Team members Project team members with read privileges to
objects within Projects to which they have been
assigned.

Creating a Project
A Project is created or modified by performing the following steps:
Creating or modifying the Project ID, Project name and description.
Assigning team members.
Defining security rules.
A Project administrator uses the top portion of the Project Definition panel
to define the Projects identification information and to make the Project
active or inactive.
Selecting Project team members

A Project administrator uses the Member Selection portion of the Project
Definition panel to define the Projects team members. Team members for a
particular Project can include; Project team administrator, Privileged team
members, and (regular) Team members
Entire groups, individual users, and roles can be added as team members
of a Project. Users are first assigned as team members, with a project team
administrator and privileged team members being selected from the list
of users assigned to the Project. A user with the group/role of Project
Administration/Project Administrator is automatically added as the team
administrator.
Copying a Project
You can copy a Project, using the copy to be the basis of a new Project.
Typically you will select a Project with settings similar to the Project
you want to create, modify the Project ID and the Project name, then
change the team member assignments and/or the security rules as required.
Setting Security Rules

The Project administrator can define project security rules for a
particular Project in the Project application using the AM Rule tab.
Assigning data to a Project

After a Project is created, the Project administrator, Project team
administrator and privileged team members need to assign Teamcenter
Engineering data to the Project. Objects are assigned to Projects by
performing the following steps:
Assigning new or existing objects to a Project.
Defining relation propagation rules.

Activity: Create a Project
In this activity, you will make your account a Project Administrator

and then create a Project and assign users to that Project.
Step 1: Add your user to the Project Administration group.

Enter the Admin/Organization application.
In the Organization pane, expand the Project Administration

group.
Expand the Project Administrator role.
By default, the infodba user has been added to the Project

Administration group with a role of Project Administrator.
Select the Project Administrator role.
Choose .
The Organization User Wizard dialog appears.
Choose Next to accept the default to Add existing user.
Locate your User ID in the list of Existing Users.
Select your User ID, then choose .

The user is added to the Selected Users list.
Choose Finish.
Choose Yes to add selected user.
Choose OK on the User(s) added message.
Close the Organization User Wizard dialog.

Your User ID now appears in the Project Administrators list.
Step 2: Create a Project

Enter the Admin/Project application (may have to choose
More... to add it to the Application list).
The Project Definition panel appears.
Enter Project A in the ID field.
Enter Test Project in the Name field.
Step 3: Assign the project team members.

In the Organization Groups section of the Member Selection
panel, expand the high_performance group.
In the high_performance group, expand the Design Engineer

role.
Select the davistr user, then choose .

The davistr user, in the role of Design Engineer, is added to
the Team.
In the high_performance group, expand the Engineering

Manager role.
Select the waynetr user, then choose .

The waynetr user, in the role of Engineering Manager, is added
to the Team.
Select the standards group, then choose .

The standards group, is added to the Team.
Step 4: Assign a team administrator.
Choose the Select a project team administrator icon .

The Select a Team Administrator window appears.
Select davistr from the list, then choose OK.

Notice, that the Selected Members panel updates to show a
Person icon ( ) by davistr instead of an X. This indicates that
davistr is now a Team Administrator.
Step 5: Assign privileged team members.
Choose the Select privileged team members icon .

The Select Privileged Team Members window appears.
Notice, that since davistr was added as the Team

Administrator, davistr already appears in the Selected Team
Members list. By default, your userid should also be listed are
a Privileged Team member.
Select waynetr from the list, then choose >.

The list of Selected Team Members now includes waynetr.
Choosing >> will move all team members to the

Selected Team Members list.
Choose OK.

Notice, that the Selected Members panel updates to show a

check mark by waynetr instead of an X. This indicates that
waynetr is now a privileged member.
Step 6: Save the Team settings.

Choose Create.
Project A is now displayed in the Project Tree panel.
Setting Security Rules

The project administrator can define project security rules for a particular
project in the Project application using the AM Rule tab. The AM Rules tab
displays the In Project security rule tree. Additional branches can be defined
and added to the rule tree. The sub-tree under the In Project rule is the only
tree that can be modified by a project administrator.
Alternatively, a system administrator can define project security rules, or
any other access rules, using the Access Manager application. Using this
application, a system administrator has full access to all the AM rules at your
site. Using Access Manager, the system administrator can move the location
of the In Project rule within the site rule tree to meet the requirements at
your site. The system administrator can also change the order of child rules
within the In Project rule tree.
Default Security Rule

By default, the In Project ( )->Projects security rule is applied to all data in
all projects. The Projects Named ACL provides project team members read
privilege to all data assigned to the project. Thus, there is no need to modify
the default ACL table for each new project unless the default security rule of
allowing all team member access does not meet your sites requirements.

Activity: Setting Security Rules
In this activity, you will establish a security rule that grants Read access to
data assigned to Project A to only members of Project A.
Step 1: Create the Access Rule.
Select the AM Rules tab.
Verify the Condition field is set to In Project.
Set the Value field to Project A.
Type Project A in the ACL Name field.
Choose the Create icon to the right of the ACL Name field.
Choose the Add entry icon , and then define the following
entry for the World.
Choose the Add entry icon again, and then define the
following entry for the Members of Project A.
Choose the Save icon to the right of the ACL Name field
to save the Named ACL.
Choose the Add icon at the bottom of the panel to

add the rule to the AM tree.
The new rule is added to the AM tree.
Step 2: Save the Access Rule.

The asterisk in the application header indicates that the AM
rule tree edit needs to be saved.
Choose the Save icon on the Portal toolbar.

Once the AM rule tree is saved, the asterisk disappears..

Assigning Objects to a Project

New items, item revisions, and engineering change objects can be assigned to
projects during the creation process. All other workspace objects can only be
assigned to projects after they are created.
Assigning New Objects to a Project
Privileged team members can assign items to a project during creation using
the Assign to Project tab in the New Item, Revise Item and Save As Item
dialogs. The Projects for Selection field displays all the projects of which
the user is a privileged team member. The team member selects one or more
projects to assign the item to and moves these projects to the Selected
Projects field.
Assigning Existing Objects to a Project

Privileged team members can assign existing objects to projects by selecting
the objects in the My Navigator object tree or Properties table and then using
the ToolsProjectAssign menu function.
Removing Existing Objects from a Project

Privileged team members can remove existing objects from projects by
selecting the objects in the My Navigator object tree or Properties table and
then using the ToolsProjectRemove menu function.
Relation Propagation Rules

Relation propagation rules are used to automate the addition of secondary
objects to a project when related primary objects are assigned to projects.
When a primary object (for example, an Item or Item Revision) is assigned
to a project, the secondary attachment objects (for example, an Item
Revision Master, UGMASTER, DirectModel) may also be assigned if
specified in the relation propagation rules.
When a secondary attachment object is cut from the primary object, the
attachment object is removed from the projects to which the primary
object is assigned.
When a secondary attachment is pasted to a primary object, this

attachment will be assigned to the projects of the primary object.
Relation propagation rules are defined using the EditOptionsProject

dialog.
Relation propagation rules can only be defined by System Administrators and

they apply to the entire site.

Activity: Add objects to a Project
In this activity, you will create database objects and assign them to a Project.
Step 1: Log into Teamcenter Engineering as a Privileged Project team
member.
Log out of Teamcenter Engineering.
Log back into the Engineering/My Navigator application using

the davistr account.
Step 2: Create a new Item object and assign it to Project A.

Select the Home folder, then choose FileNewItem...
In the New Item window, make sure Select Type is set to Item.
Choose Next.
Choose Assign.
Enter Project Part for the Item Name.
Select Assign to Projects from the list.
Select Project A from the list of Projects for Selection.
Choose > to move Project A to the list of Selected Projects.
Choose Finish.
After the Item is created, Close the New Item dialog.
Step 3: Use the Properties window to verify the new Item is part of
Project A.
Select the new Item.
Choose ViewProperties.
The Properties window appears.
Scroll down until you see the Project IDs field and notice
Project A is listed.
Choose Cancel to close the Properties window.

Step 4: Use Columns to verify the new Item is part of Project A.

In the Properties table, place the cursor in the Type column
heading, then press the right mouse button.
Select Insert column(s) ... from the Table Function Menu

pop-up.
The Insert Columns dialog appears.
Select Item, then choose Next.
The Insert Columns dialog changes.
Select Item again, then choose Next.

The Insert Columns dialog changes once again.
Locate and select Project IDs, then choose .

The Project IDs property is moved to the Selected listing.
Choose Finish.
Close the Insert Columns dialog.
Select the Home folder.

Notice the Project IDs column has been added to the Properties
table and now shows that the new Item is part of Project A.
Step 5: Test the Security Rule.

Select the Item object you just created.
Select the Access icon on the Portal toolbar.

The Access dialog appears.
Select the Get ACL icon on the Access dialog.
The ACL Control List dialog appears.
Observe the 2nd and 3rd entries in the list.
These entries are present for this item because this item is
assigned to Project A.
Choose Cancel to close the ACL Control List dialog.
Close the Access dialog.
Log out of Teamcenter Engineering and log back in with your

student userID.

Summary
In this lesson you:
Established Project Administrators
Created Projects and assigned team members
Defined security rules for Project data
Added objects to an existing Project
Lesson
11 Workflow Process Modeling
Purpose
The purpose of this lesson is to build Teamcenter Engineering Workflow
Process Templates.
Objectives
Create Generic Workflow Process Templates.
Create Workflow Process Templates for Change Management.
Import Process Templates
Use Resource Pools in Processes.
Use Conditional Tasks in Processes
Use Secure Tasks in Processes

Workflow Process Modeling
Create Workflow Processes
... so that you can create a process to release data.

... so that you can create a process that accurately
mimics a Change Management business workflow.

Overview of Teamcenter Engineering Workflow
Review of the Teamcenter Engineering Process Model
Controlling the Workflow with Process Templates
Creating Process Templates
Creating a Process Template That Does Not Require a Signoff
Creating a Single Signoff Process Template
Using Task Handlers in a Process Template
Creating a CM Process Template
Using ACLs in a Process Template
Importing Processes Templates
Using Resource Pools
Using Conditional and Secure Tasks
Overview of Teamcenter Engineering Workflow

Workflow stems from the concept that all work flows through one or more
processes in order to accomplish an objective. Workflow is the automation of
those business processes. Using workflow, documents, information, and tasks
are passed between participants during the completion of a particular process.
Enterprise Process Modeling (EPM) is used to model workflow processes,
allocate resources, and manage data according to business rules. In other
words, EPM is the software engine that Teamcenter Engineering uses to
accomplish workflow objectives.
The EPM module provides two applications used to accomplish Workflow
objectives:
Workflow Designer A graphical Workflow Designer application.
System Administrators use Workflow Designer to graphically create
process templates which end users can then use to initiate Workflow
processes.
Workflow Viewer Allows end users to view the progress of a Workflow

process, even if they are not a participating member of that particular
process.
A Workflow process uses defined tasks to automatically notify selected users

requesting work signoff. The requests are tracked through an electronic In
Box and each request maintains pointers to the data being approved. The
exact task must be defined based on current company procedures for data
signoff.
A Workflow process can have any number of tasks arranged in a serial or
parallel progression. At the time of signoff, each Review Task will have
a list of users allocated for signoff.

Review of the Teamcenter Engineering Process Model

A Process is made up of tasks. Some tasks may be sub-tasks associated
with a main task.
For example, a main task may require a Design Engineer to review the data
associated with a product change and give their approval. The first sub-task
would be to select the specific Design Engineer associated with the project.
When the work is automatically sent to that Design Engineer, the next
sub-task would be to view the data and perform the signoff (as shown below).
When tasks and sub-tasks are performed, the process advances to the next
set of tasks. After all the tasks have been completed, the release process ends.
Advantages of Using Release Processes

Electronic distribution of tasks to defined users required for sign-off.
Reduced engineering change cycle time thus reducing costs and improving
product development/change cycle time.
Permanent record of all activities during an engineering change.
Predefined processes that have to be followed.
Process Terms and Functionality

Process Templates are templates that define a Workflow process. A Process
defines a set of Tasks and a user profile (Group and Role) for each task. The
user profile is an abstract and doesnt correspond to a real Person in a process.
A Job is an instance of a Process. A new Job is created each time a Process
is run. Jobs define the data required for that Job and assigns real Persons
to perform Tasks according to their user profile.
An Approver is a user responsible for approving a task.
An Attachment is a Teamcenter object associated with a Process job.
There are two kinds of attachments: target objects and reference objects.
Attachments are always attached to the tasks of a Process job.
A Target Object attachment is any Object (e.g., ItemRevision, Dataset)
that will be released via a Process job. Typically, target objects are
assigned a release status when the Process job completes.
A Reference Object attachment is an object attached to a Process job

that allows you to provide information to the sign-off team. Reference
Objects are not released when the Process job completes, but are kept in
the Job object for historical purposes.
Tasks are used to perform actions within a Job. When all Tasks defined for a
Job are completed, the Job is complete.

Result of Releasing Data with a Process
Most common user interaction data like folders, forms, datasets,

ItemRevisions, and BOMView revisions can be initiated and released with a
Process. Other data like distribution lists are less likely to be released.
When the data is initiated and released the following typically occurs.
The Release Status and Date Released attributes will get values.
The released data will become read only.
Releasing flat objects (e.g. datasets, forms) will just release the object.
Releasing a Folder will just release the Folder (not its contents).
Releasing an ItemRevision will release the ItemRevision, BOMView

Revision, and all of the Specification relation objects.
The last feature is done through the use of a handler in the release procedure
template. You can remove or change the handler to get other desired
functionality. Other handlers (which will be discussed later) can be written to
meet specific requirements.
Two Usage Modes with Workflow
There are two different approaches to using Workflow:

As a review and approve mechanism, or
As a task controller for work in progress.
When Workflow is used as a review and approve tool, the user would create
and complete the updates to any data (including parts), then start a review
process on the data.
Alternately, Workflow can be used for data in work. As the process progresses,
appropriate data would be updated or added to the process and approved.

Controlling the Workflow with Process Templates
Every Workflow is controlled by its process template. The process template

specifies the following:
Number of tasks in the process
Groups, roles and approvers required to complete each task
Protections and privileges of groups, roles and approvers
Release Status set on released data
Follow-up actions that may accompany or follow the release
Tasks in a process can be for anything an organization needs. The purpose of

a typical task could be for checking or editing a dataset, or simply reviewing
material before production. A task is usually named for what it is intended,
such as Engineering Approval or Project Review.
Default Procedures for Groups based on Object Type

Groups can have default process templates for various types of data. This
default can be overridden, if necessary, based on your site preferences.
For example, a Text document may use a process template having a two task
sign-off by the engineer and manager. In the same group, an ItemRevision
may use a process template having three tasks of sign-off by engineers,
drafters, manufacturing engineers, and managers. Another group could have
different defaults for these data types.
Creating Process Templates

Process Templates are created using the Workflow Designer application.

Process Definitions
A Process is the automation of a business procedure, describing the individual

tasks and task sequences required to complete a business procedure.
A Process Template is a blueprint of a workflow process.
Tasks
Tasks are the fundamental building block used to construct a process. Each
task defines a set of actions, rules, and resources used to accomplish that task.
A Task Template is a blueprint of a workflow task.
A Do Task is a task template which includes the EPM-hold handler,

which stops this task from automatically completing when the task is
started. This template has a customized dialog which allows you to set a
check box to indicate when the task is complete.
A Review Task is a task template which includes select-signoff-team

and perform-signoffs subtasks. Each of these subtasks contain their own
dialog for executing the respective processes.
An Add Status Task is a task template which creates and adds a release
status to the target objects of the process. There is no dialog associated
with this template.
Signoff related tasks

Select Signoff - allocates specific Users to perform the signoffs
who meet the Group/Role criteria defined in the task template.
Perform Signoff - Allows a signoff team member to make one of three

decisions: Approve, Reject, No Decision. Comments can also be added to
the task.
Creating new Workflow Processes
Creating a Workflow Process is started from the Workflow Designer

Application by choosing FileNew Root Template.
You are then presented with the New Root Template dialog.
Once you enter a new process name and select the process template it will be
based on, you can begin to add the various tasks needed to define the process.

While creating or modifying a process, it has an Under Construction status,

as indicated by the icon to the left of the listed process.
Whether exiting or entering the Workflow Designer application, the process

will remain in this state until it is made available for general use. This is
done when exiting the Workflow Designer application (FileClose), and you
are asked to make the template available for all users. If you do not make it
available for all users, it will stay in an under construction mode.
Modifying existing Workflow Processes
When modifying existing Workflow Processes, it is important how the process

is accessed. To modify a process, enter the Workflow Designer and select the
workflow to be modified from the Process Template list. After choosing the
Edit Mode icon, you have the option whether or not to take the process offline.
Choosing Yes, will take the template offline for modification. This is indicated
by the Construction icon next to the process in the templates list. In this
mode, all modification are saved. If a mistake is made, you can not cancel
the modifications.
Choosing No, will not take the template offline. Instead, a copy is created
for modification. This is indicated by an additional listing of the process
with the Construction icon next to it.
Since there is no Save icon in the Workflow Designer application, process

templates are saved when you make them available when existing. Taking
the process offline is the only way to not save modifications to a template
once open for edit. To not save the modifications, the template needs to be
taken offline and then the Delete icon in Workflow Designer can be used to
delete only the construction copy and cancel the modifications. The original
process template remains.

Create a Process Template That Does Not Require Signoff
Although the primary purpose of this lesson is to teach you how to create
multi-task process templates, a process template without signoffs may be
created for certain reasons, releasing data without electronic review is
sometimes necessary for the following reasons:
When you have data imported into Teamcenter Engineering from existing
systems where it was previously released.
When you have data that has been reviewed outside of Teamcenter
Engineering and is simply released in Teamcenter Engineering.
When you are gradually phasing into the electronic workflow system.
As shown below, a process template that does not require a signoff

is a simple process. It can have as little as two nodes, Start and
Finish, which are the minimum requirements for any process. This
only other necessity is the assignment of the correct Release Status.
Activity: Create a Quick Release Process
In this activity, you will learn how to create the Quick Release process.
Step 1: Open the Workflow Designer application window.
Choose Admin.
Choose Workflow Designer.

The Workflow Designer window displays.
Step 2: Create a New Process.

Choose FileNew Root Template...
The New Root Template dialog is displayed.
Enter Quick Release in the New Root Template Name field.
Select Review Process from the Based On Root Template list.

Choose OK.
Step 3: Choose the Status the process will apply.
Select the Task Attributes icon (bottom left).

The Attributes window appears.
Select Released from the Release Status drop-down.
Close the Attributes dialog ( ).
Choose FileClose.
Select the Quick Release process in the Under Construction

Templates list, then choose the right arrow to copy it to the
Templates to be made Available list.
Choose OK.
Step 4: Test the new Quick Release process by first creating a Text dataset.
Choose FileNewDataset...
Set the Type to Text.
Enter QR document in the Name field.
Choose OK.
Step 5: Release the QR document dataset.

Select the QR document dataset. (If asked, choose No on
Create New File dialog.)
Choose FileNewProcess...

The New Process dialog is displayed.
Notice the Process Name field defaults to the same name as

the target object being released.
Notice the QR document is listed in the Attachments section

as a Target to be released.
Set the Process Template to Quick Release.
Choose OK.
The Release Flag appears on the QR document dataset.
You now have a Quick Release process defined for releasing

certain data without a formal signoff. You will use this process
again in a later lesson to release imported data.
Creating a Single Signoff Release Process

Like the No-signoff release process, a Single signoff release process is
relatively simple. However, it must include a Review Task which allows for
the selecting of a signoff team and the performing of the signoff operation.
Like the No-signoff release process, it must be assigned a Release Status.
Creating the Signoff Team
Selecting the Task Signoff Panel icon ( ) displays the Signoff Profiles
dialog.
The Signoff Profiles dialog allows you to select the Group and Role for the
correct signoff user. The user that matches this profile will be assigned later
during the execution of the process.

The Number of Reviewers represents how many users with the same type
of Group and Role are needed to sign off on the task. For example, if you
needed three (3) Design Engineers in the high_performance group to sign
off, you would simply create a listing for Group=high_performance and
Role=Design Engineer and set the Number of Reviewers to three (3).
The Quorum field allows you to define the number of sign-offs that are
required to complete the task. Leaving the Quorum field blank or entering
ALL specifies that approval must be unanimous, meaning all users must sign
off. Any other positive integer specifies the quorum.
Activity: Create a Single Signoff Release Process
In this activity, you will create a single signoff release process to be used
when releasing previously imported data.
Enter the Admin/Workflow Designer application.

The New Root Template Dialog is displayed.
Enter Import Release in the New Root Template Name field.
Set the Based on Root Template to Review Process.
Choose OK.
Step 2: Create the Review Task.
Verify that Edit Mode is selected.
Select Review Task Template on the toolbar.

Double-click in the Task Flow section of the Workflow Designer

window (just to the right of the green Start task).
The New Review Task 1 task is created.
Enter Import Review in the Name field, then press Enter.

Notice that the task name is changed to Import Review.
Step 3: Link tasks from Start to Finish

Place the cursor over the Start task (not on the blue strip) and
press the left mouse button. While keeping the left mouse
button pressed, drag the cursor to the Import Review task
and release.
An arrow appears between the tasks indicating they are linked.
Place the cursor over the Import Review task and press the left
mouse button. Drag the cursor to the Finish task and release.
The Workflow Designer window should look like this.

To move a process task, hold the left mouse button

down on the blue strip at the top of the task box and
then move the cursor.
Step 4: Define the signoff team criteria.

Expand the Import Review task and select the
select-signoff-team.
Choose the Task Signoffs Panel icon.

The Signoff Profiles dialog is displayed.
Set the Group field to dba.
Set the Role field to DBA.
Although, you will use the dba group and DBA

role in this course, your site should use the group
that owns the parts to be released (for example,
high_performance) and the role responsible for
signoff (for example, Product Engineer).
Leave Number of Reviewers set to 1
Choose the icon.

The Signoff Profiles dialog should look like the following.
Choose the X in the top right corner of the Signoff Profiles

dialog to close it.
Step 5: Set the Release Status.

Select the Import Release (top level) task.
Select the Task Attributes icon.

Set Released Status to Released.
Close the Attributes dialog.
Step 6: Save the Process Template.

Choose FileClose.
Select the Import Release process in the left pane, then choose
the right arrow to copy it to the right pane.
Choose OK.
The Import Release process is now defined in the database.

You will use this process to release imported parts.
Using Task Handlers in a Process Template

Process Templates are actually comprised of task handlers, or building
blocks, that precisely define the work done during a task. Task handlers are
small ITK programs or functions. Task handlers are the lowest level building
blocks in EPM. They are used to extend and customize tasks.
There are two kinds of handlers:
An Action handler which does the executable and returns.
A Rule handler which executes and returns either a GO orNOGO decision.
Each Task has a number of Task Actions (for example, to Assign a user to
perform a Task). These Actions can be constrained by Business Rules.
According to the Actions that have been performed, the Task is in some State
(unassigned, started or completed, for example).
Selecting the Task Handler icon displays the Handlers Panel associated
with a particular task.

Some Useful Canned Handlers
EPM Attach ItemRevision Targets
The EPM-attach-item-targets handler attaches all objects with

specification relation to the ItemRevision as target objects. BOMView
Revisions are also attached as targets to the job.
This handler is typically added to the root task Start action so
that the list of target attachments is updated at job initiation.
EPM-attach-item-revision-targets
Demote On Reject
The demote-on-reject handler demotes the current task when the approval
quorum cannot be met.
The recommended placement for this handler is
the perform-signoff task Perform action.
demote-on-reject
Disallow Adding Targets and Disallow Removing Targets

The disallow-adding-targets handler prevents targets from being added to
a job after the job has been started.
The disallow-removing-targets handler prevents targets from being
removed from a job after the job has been started.
The recommended placement of these handlers is the root task Perform
action.
Generally, it is a good practice to leave these handlers
attached to the root task Perform action in order to ensure
that target objects are not added to a job once it is started.
disallow-adding-targets
disallow-moving-targets
CR Assert Targets Checked-In

The CR-assert-targets-checked-in handler verifies that all target objects
in this job are checked-in.
The recommended placement of this handler is the root task Complete action.
CR-assert-targets-checked-in
CR Fill In Reviewers
The CR-fill-in-reviewers handler automatically fills in reviewers that meet
specified user, group, or role criteria for the specified release level.
The recommended placement of this handler is
attached to the select-signoff-team task Start action.
CR-fill-in-reviewers -reviewer={User:<user_id>| \
Group:<group>|Role:<role> \
|$USER|$GROUP|$ROLE|$REVIEWERS} \
[-level=<level_name>]
This handler uses the following argument(s):
-reviewer User_id, group, or role criteria of the reviewers or other

keywords as shown.
-level Level name
The following examples demonstrate using this handler:

1. The following example designates user daytr and all the members of the
standards group as reviewers for Import_Review.
CR-fill-in-reviewers -reviewer=User:daytr
-reviewer=Group:standards
-level=Import_Review
Notify
This action handler will inform users of a tasks status via OS e-mail. If the
-attachment argument is included in the definition of the notify handler,
then the recipients will also receive Teamcenter Engineering mail, and the
OS e-mail will include a notification that the user has received Teamcenter
Engineering mail. Arguments used with the notify handler must be separated
by a comma.

When $REVIEWERS is used as the key word in conjunction with

the DistributionList argument, the recommended placement of
this handler is attached to the perform-signoff tasks start or
complete action. Otherwise, there is no recommended placement
notify
-recipient=
{OS:<value>|User:<value>|Group:<value>|Role:<value>|
DistributionList:{<value>|$USER|$GROUP|$ROLE|$REVIEWERS}}
[-subject=<string>]
[-comments=<string>]
[-attachment=$TARGET|$PROCESS]
[log]
This handler uses the following argument(s):
-recipient Task reviewers that will receive notification.

Accepts one of the following values.
OS Where <value> is a single valid user name.
User Where <value> is a single valid TcEng user ID.
Group Where <value> is a single valid TcEng group.
Role Where <value> is a single valid TcEng role.
DistributionList Where <value> is a single valid entry that
represents a distribution list. This entry may
either be the name of a valid TcEng Address
List, or it may be any one of several keywords
that represent a distribution list.
-subject When the OS e-mail is delivered, it will use
the task name for the subject by default. If
the -subject argument is added, then the task
name will be enclosed within brackets [ ], and
the resulting string will be postfixed to the
string identified by the -subject argument to
form the e-mail subject line.
-attachment This argument will cause an attachment to
be included in an TcEng mail. The type of
attachment will be one of the following:
$TARGET The Workflow target attachment(s) will be
included in the TcEng mail.
$PROCESS The Workflow process will be included in the
TcEng mail.
The following example demonstrate using this handler:

1. The following handler syntax designates Teamcenter Engineering user
daytr as recipient of an OS e-mail and Teamcenter Engineering mail
with targets attached. This handler will be added to the Import Review
process to notify the data migrator when review and release of imported
data has been completed
notify\
-attachment=$TARGET,
-subject=Imported data reviewed and released,
-recipient=User:daytr
There are other options in using notify that are not shown here.

Activity: Add a Handler to a Process

In this activity, you will learn how to add Handlers to the Import Release
process.
Step 1: Access the Import Release process.
Enter the Admin/Workflow Designer Application.
Select the Import Release process from the Process Template

field list.
Step 2: Add the CR-fill-in-reviewers handler to the Import Release release

procedure.
Choose the Edit Mode icon.
Choose Yes to take the Process Template offline.
Expand the Import Review task.
Select the select-signoff-team task, then choose .

The Handlers panel is displayed.
Select the Start Task Action.
Set the Action Handler field to CR-fill-in-reviewers.
In the existing row of the Argument table, enter:
Use your userid (which is in the dba group). Example:

User:waynetr
Choose the icon (at the bottom of the dialog) to add the
handler to the Start action.
The CR-fill-in-reviewers handler is added to the Start Task
Action.
Close the Handlers window.

Step 3: Save the Release Process.

Choose FileClose.
Select the Import Release process in the left pane, then choose
the right arrow to copy it to the right pane.
Choose OK.
Now the Import Release process will

not require a select-signoff-team task.
Creating a Multi Task Process

Multi task processes are a collection of many tasks. These tasks can be
made up of a variety of process tasks. Some tasks can be for selecting and
performing signoffs. Others for simply checking the work and moving it
forward, no signoff required. The arrangement of tasks and complexity of
handlers will vary depending on the business process the process is trying to
model.
Setting Access privileges as data moves through a process

An important concept of a release process is the ability to alter the privileges
on the data for the different users who need to work within the boundaries of
the process. To do this, Teamcenter Engineering uses Workflow ACLs which
can be created and attached to the different tasks within a process.

Using ACLs in a Process Template
Selecting the Task Attributes icon displays the Attributes dialog

associated with a particular task.
By selecting the Named ACL field, a user can create a new ACL by selecting
the Type of Accessor, ID of Accessor, and setting the type of access the
Accessor will need in order to work within the process. This is done through
the Named ACL dialog, shown below.
Activity: Create a Process Template for CM
In this activity, you will create a multi-task process template that models a
basic Change Management process. This process template will be used for
the Change object type you will model in a later lesson.

The New Root Template dialog is displayed.
Enter TR Change Notice in the New Root Template Name field.
Leave the Based on Root Template field set to Empty

Template.
Choose OK.

Step 2: Create the Process Tasks.
Select the Do Task Template icon on the toolbar.
Double-click in the Task Flow section, just to the right of the

green Start task.
The New Do Task 1 task is created.
Enter Prepare Change in the Name field and press Enter.

The task name changes to Prepare Change.
Select the Add Status Task Template icon on the toolbar.
Double-click in the Task Flow section just below the Prepare

Change task.
The New Add Status Task 1 task is created.
Enter ECPending Status Obtained in the Name field and

press Enter.
The task name changes to ECPending Status Obtained.

Double-click in the Task Flow section just to the right of the

Prepare Change task.
Enter Initial Change Review in the Name field and press Enter.
The task name changes to Initial Change Review.
Select the Do Task Template icon on the toolbar.
Double-click in the Task Flow section of the Workflow Designer

window just to the right of the Initial Change Review task.
The New Do Task 1 task is created.
Enter Finalize Change in the Name field and press Enter.

The task name changes to Finalize Change.

Double-click in the Task Flow section just to the right of the

Finalize Change task.
Enter Final Change Review in the Name field and press Enter.
The task name changes to Final Change Review.
Select the Add Status Task template icon.
Double-click in the Task Flow section just below the Final

Change Review task.
The New Add Status Task 1 task is created.
Enter Released Status Obtained in the Name field and press

Enter.
The task name changes to Released Status Obtained.
Step 3: Link tasks from Start to Finish
Place the cursor over the Start node and press the left mouse
button and while keeping the left mouse button pressed, drag
the cursor to the Prepare Change task and release.
An arrow should now appear between the two tasks indicating
they are linked.
Place the cursor over the Prepare Change task and press the
left mouse button. Drag the cursor to the ECPending Status
Obtained task and release.

Repeat the process until all tasks are linked and your process
looks like the following.
To move process tasks, click in the blue strip at the

top of the task box.
Step 4: Define the Reviewer profiles for the Review tasks.

Expand the Initial Change Review task in the Task Hierarchy
Tree and select the select-signoff-team task.
Select Display the Task Signoffs Panel .
Set the Group field to high_performance.
Set the Role field to Engineering Manager.
Verify Number of Reviewers =1
Choose the icon to attached the signoff profile.
Close the Signoff Profiles dialog.

Expand the Final Change Review task in the Task Hierarchy

Tree and click on select-signoff-team task.
Select Display the Task Signoffs Panel .

Set the Group field to high_performance.
Set the Role field to Engineering Manager.
Verify Number of Reviewers =1
Choose the icon.
Close the Signoff Profiles dialog
Step 5: Define the Release status values to be applied/modified.

Select the ECPending Status Obtained task in the Task
Hierarchy Tree.
Select the Task Attributes icon.
Change the Released Status to ECPending.
Select the Released Status Obtained task.
Choose the Display the Task Handlers icon .


In the Start action, select the create-status handler, then

choose the Delete icon (at the bottom).
In the Complete action, select the add-status handler and then

the Delete icon (at the bottom).
Select the Complete Task Action.
Set the Action Handler field to set-status.
In the Argument table, enter the following.
This handler will change the status on the targets from

ECPending to Released, prior to completing to the process.
Choose the icon (at the bottom) to add the handler.
The set-status handler is added to the Complete Task Action.
Close the Handlers panel.
Step 6: Add rules based access for the Final Change Review Task
Select the Final Change Review task.
Select the Task Attributes icon .

The Attributes dialog is displayed.
Choose the icon (Vault) adjacent to Named ACL.

The Named ACL dialog is displayed.
Enter Change Review in the ACL Name field.
Choose the icon to the right of the ACL Name field.
On the far right side of the dialog, select the + sign to add
a new line.
Double-click in the Type of Accessor box and select World.
Set the protections as shown below by double-clicking in each

box.
Select the + sign on the far right side of the dialog to add
another line.
Double-click in the Type of Accessor box and select

Approver(RIG). RIG stands for Role In Group.
Double-click in the ID of Accessor box and set it to

Engineering Manager in high_performance.
Set the access to allow Promote privilege.

The Named ACL dialog should look like the following.
Choose the Assign button.

Notice the Assigned ACL Name field (bottom of Named ACL
dialog) changes to Change Review.

Close the Named ACL dialog.

Notice the Named ACL setting in the Attributes dialog changes
to show the new Change Review ACL.
Step 7: Save your work.

Choose FileClose.
Select the TC Change Notice process in the left pane, then

choose the right arrow to copy it to the right pane.
Choose OK.
The TR Change Notice process template

is now defined in the database.
Importing/Exporting Workflow Processes

All Workflow processes are stored in the database, but they can be exported
for use between different Teamcenter Engineering sites. The Export and
Import commands are accessed through the Tools menu.
Choosing ToolsExport accesses the Export Workflow Templates window.

From here, the destination directory and xml filename are entered. The
Continue On Error option allows the export to continue if one or more
templates fail to export. Failed templates are bypassed. If this option is
ignored, the export stops when a template fails, however any templates
exported before the failure are exported.
Choosing ToolsImport accesses the Import Workflow Templates window.

From here, an import directory and xml filename can be identified.

Activity: Importing process templates
In this activity, you will use the Import function to import the procedures
that will be needed in the last topics of this lesson.
Step 1: Locate and edit the template file.
In a directory structure type window (i.e., Explorer for
Windows), navigate to the aa_class/workflow_designer folder.
Locate the import_templates.xml file and open it in a text

editor.
Find the two incidents of change_userid and change them

to your userid.
For example, if your userid was waynetr, you would locate
the two incidents of change_userid and replace them with
waynetr, as shown in the following figures.
Before:
After:
Save and exit the templates file.
Step 2: Import the workflow processes.

Choose ToolsImport
The Import Workflow Templates dialog is displayed.
Choose the Import icon.
In the Select Directory window, navigate to the

aa_class/workflow_designer directory.
Select the import_templates.xml file, then choose Select.

The import_templates.xml file is now displayed in the Import
File field.
Choose OK.
Step 3: Review the appended procedures.

Choose ViewRefresh Window to view the newly imported
processes.

Select the pull-down list from the Process Template field.
Notice there are four new processes listed, all starting with
AA ( for Application Administration).
AA-Automatic Condition Task
AA-Manual Condition Task
AA-Resource Pool
AA-Secure Tasks
These were imported into the database from

the import_templates.xml file. They will
be used in the activities in the next topics.
Resource Pools
A Resource Pool is a Group, Role in a Group, or a Role which can be
assigned tasks the same way an individual User is assigned tasks
A Resource Pool is a conceptual definition of a set of users. Resource
Pools are not directly created by Teamcenter Engineering Administrators.
Instead, they are implicitly defined when the Administrator defines the
Group/Role/User organization for the site. Resource Pools are used only
in the context of workflow.
Resource Pools are useful in modeling workflow tasks that cannot be
directly assigned to a single user, either automatically, or at run-time by the
responsible user. Instead, the task is assigned to a pool of users, one of whom
will in pull the task or assign the task to themselves.
Subscribing to a Resource Pool Inbox

In order to see and perform tasks that have been assigned to Resource Pools,
users need to add the display of the Resource Pool Inbox to their Inbox tab.
From the My Navigator application, choose ToolsResource Pool
Subscription... to open the Resource Pool Subscription dialog.
In the following example, the user can set the Role to Engineering Manager
and choose the Subscribe a Resource Pool button (+) to set up a resource
pool Inbox for that specific role.
Delegating Tasks
A task in the */Engineering Manager (Resource Pool) Inbox can be viewed and
performed by multiple users who have subscribed to that Inbox. Delegating
the task to a specific user Inbox will avoid duplication of effort and should be
done when it will take an long time to perform the task.
Users can delegate tasks from a Resource Pool Inbox to their personal Inbox
and vice versa.

From Resource Pool Inbox to Personal Inbox

Assigning Resource Pool tasks to a particular user can be performed in the
following manner.
1. Select the desired task from the desired Resource Pool Inbox.
2. Select the desired link from the User-Group/Role listing.

The Delegate signoff dialog will appear.
3. Select the desired User from the drop-down list, then choose OK.
4. The task is removed from the */Engineering Manager Inbox and placed in
the users Tasks to Perform folder. The responsibility of this task has
been transferred to the selected user.

Activity: Resource Pools

In this activity, you will perform the following tasks:
Add a Resource Pool Inbox to your Inbox display
Browse tasks that require end-users to (manually) assign resource pools

and tasks that automatically assign resource pools
Execute and test the process template
Step 1: Display the Inboxes tab.

Choose the Open Inbox icon.

The Inboxes tab appears with your user Inbox displayed.
Step 2: Add the Inbox for the dba/DBA resource pool.

Choose ToolsResource Pool Subscription...
Set toggle to All.
Set the Group to dba.
Set the Role to DBA.
Choose the icon.

The dba/DBA Inbox appears in the Inboxes list.
Choose Cancel.
The Inbox tab now displays two Inboxes. One for your user ID
and the other for the dba/DBA group/role resource pool.
Step 3: Browse the AA-Resource Pool process template.

Go to the Admin/Workflow Designer application.
Choose AA-Resource Pool from the Process Template.

Expand all tasks in the Task Tree.
Select each task in the tree and read the

Description/Instructions.
Select the Auto Assigned RP for Do task.
Choose the Display Task Handlers icon to display the

Handlers Panel.
Select the auto-assign handler in the Start section.

Observe the usage of the auto-assign handler to automatically
assign the task to the dba/DBA resource pool.
Under the Auto Assigned RP for Review task, select the

select-signoff-team task.
Choose the Display Task Handlers icon .
In the Start section, select the CR-fill-in-reviewers handler.

Notice that this handler will automatically assign the dba/DBA

resource pool as a Reviewer.
Step 4: Test the AA-Resource Pool process template.

In the Engineering/My Navigator application, select the Home
tab.
Select the Home folder, then choose FileNewItem...
Set the Item Type to Item.
Choose Next.
Choose the Assign button on the New Item dialog.
Enter a Name for the Item, then choose Finish.
Expand the new Item object and select the ItemRevision object.
Choose AA-Resource Pool from the Process Template

drop-down.
Choose OK on the New Process Dialog.
Select the Inboxes tab in My Navigator.
Under your userid Inbox, expand the Tasks to Perform folder.

Select the Do task labeled Manually Assigned RP for Do.
Choose ActionsAssign...
Manually assign the task to a resource pool by setting User to *.
Choose OK.
Notice the task is removed from your Tasks to Perform folder.
Expand the dba/DBA Inbox and the Tasks to Perform folder

under it.
Observe the task is now assigned to the resource pool.
Select the Manually Assigned RP for Do task, then choose

the Viewer tab.
Select Done, then choose Apply to complete the task.
Observe that the previous task has been replaced by the next
task in the process flow and that the task was automatically
assigned to the resource pool.
Select the Auto Assigned RP for Do task.
Expand your Inbox and then the Tasks to Perform folder.

The next task in the process demonstrates how end-users
manually select a resource pool for a Review Task.
Select the select-signoff-team task.

From the Viewer tab, select the dba/DBA/1 node in the Profiles
list.
In the User drop-down selector, set the User to *.
Choose the + icon.

Notice the new listing of * dba/DBA.
Choose Apply to complete the task assignment.

Notice the associated perform-signoffs task appears in the
resource pool Inbox.
Select the perform-signoffs task.
From the Viewer tab, choose the No Decision link in the

Decision column.
In the Signoff Decision dialog, set the Decision to Approve,

then choose OK.
The next task in the Process is again a perform-signoffs
task, only this time the task was automatically assigned to
the resource pool by the CR-fill-in-reviewers handler in the
process template.

Decision column.
Set the Decision to Approve, then choose OK.
All tasks have now been completed and are removed from
the dba/DBA Inbox.

Conditional Tasks
The Workflow Designer Condition Task template is used to branch process
flow according to some defined criteria. Condition tasks have a result
attribute than can be set to one of the following values: True, False,
Unset. The initial setting of the Condition task is Unset, until it is either
automatically or manually set to True or False. Successor tasks require the
Condition task to be set to either True or False before they can start.
Manual Condition Task

Condition tasks configured to proceed manually require a user action
before the task can proceed to completion. When the workflow reaches this
tasks Start action, the task appears in the selected users Inbox. The user
completes the instructions, defines the condition path as either True or False,
then clicks OK to complete the task and allow the workflow to continue. You
should enter text in the Task Instructions that pose a question or set of
parameters that require a True/False answer. If the User selects Unset,
the task will not complete.
Create a manual Condition task by inserting the Condition Task template

into the workflow process. Do not define a condition query or any custom
handler that will define a result for the task.
Define the T/F branching for successor task by using the Task Properties
dialog for the successor tasks.
Choose the Conditional Path button on the Task Properties dialog.
The Condition Paths dialog is used to toggle the T/F branching for the
successor task.

Automatic Condition Task

Condition tasks configured to proceed automatically act only as visual
milestones in the workflow process. There is no action for a user to perform,
and thus no dialog box associated with the automatic Condition Task.
Use an automatic Condition task when a database query can be defined for
the decision branch.
Create an automatic Condition task by inserting the Condition task template
into the process template, then selecting a condition query for the task using
the Task Properties dialog.
The Condition Query dialog allows you to build a new query or select an
exiting query for the task.
The Condition Query dialog allows you to set the True condition when the
query is executed against the process target list. The True condition can be
set for any of the following query results:
The query must find All of the targets.
The query must find Any of the targets.
The query must not find any of the targets (None).

Activity: Conditional Tasks
In this activity, you will browse the designs and then test processes that use
both manual and automatic conditional tasks.
Step 1: Browse the AA-Manual Condition Task Process.
Start the Admin/Workflow Designer application.
Choose AA-Manual Condition Task from the Process Template

drop-down.
Select the AA-Manual Condition Task node in the task tree

and read the description of the process.
Select Manual Condition Task from the process diagram.
Choose ViewTask Properties...

Notice that there is no query associated with this conditional
task. This conditional task requires end-user action to
determine the downstream conditional branching.

Close the Task Properties Dialog.
Select the IF Condition is TRUE task in the process diagram.
Choose the Display conditional path values button.
This displays the Condition Paths dialog which is used to

toggle the condition setting for the branch flowing into the
task as either True or False.
Close the Condition Paths dialog.
Close the Task Properties Dialog.
Step 2: Test the AA-Manual Condition Task Process

Select the Home tab in the My Navigator application.
Expand the Item that was created in the previous lesson,

then select the ItemRevision.
Set the Process Template to AA-Manual Condition Task.
Choose OK.
Expand your users Tasks to Perform folder.

Select the Standard DO Task in the Task to Perform folder.
In the Viewer tab, toggle to Process View.
The current task (circled) precedes the manual condition task.
Toggle back to the Task View.
The next task to appear in the Task to Perform folder is the

Manual Condition Task.
With the new task selected, verify the Viewer tab is still set to
Task View.
Observe the user interface for setting the value of the condition
(bottom of window).
Set the Task Result to true, then choose Apply.

A new task appears in the users Task to Perform folder.
With the new task selected, toggle Process View in the Viewer
tab.
Verify that the process flowed through the correct branch to the
next task when the conditional task was manually set to true.

All tasks for the AA-Manual Condition Task process have now
been completed.
Step 3: Browse the AA-Automatic Condition Task Process.

Choose AA-Automatic Condition Task from the Process

Template drop-down.
Read the description of the process.
Select the Automatic Condition Task task (circled) from the

process diagram.

Notice that there is a query associated with this conditional

task. This conditional task does not require end-user action to
determine the downstream conditional branching.
Choose the user_data_3_equal_MAKE Condition Query.

The Condition Query dialog allows you to build a new query or
select an exiting query for the task. It also allows you to set
the true condition for when the query is executed against the
process target list. The true condition can be set for any of the
following query results: All, Any, or None of the Targets.
Close the Condition Query Dialog.
Close the Task Properties dialog.
Step 4: Test the AA-Automatic Condition Task Process.

Expand the Item and ItemRevision that was created earlier.
Double-click the ItemRevision Master.
The ItemRevision Master form appears.
In the user_data_3 field, enter MAKE.
Choose OK to save and close the form.
Select the ItemRevision object.

Set the Process Template to AA-Automatic Condition Task.
Choose OK on the New Process dialog.
Expand your Tasks to Perform folder.
Select the Standard Do task.
In the Viewer tab, toggle Process View.
The current task precedes the automatic condition task.
The next task to appear in the Tasks to Perform folder is the

IF Condition is TRUE task.
With the task selected, toggle to Process View in the Viewer

tab.
Observe the conditional task has been automatically
performed. The condition was set to true because the value
of the user_data_3 attribute on the ItemRevision Master
form was equal to MAKE.

Toggle back to the Task View
If you wish to test the False condition, clear the user_data_3

field, and then send the ItemRevision through the
AA-Automatic Condition Task process again.
With the user_data_3 attribute field blank (or with an entry

different than MAKE), the process should automatically take
the False branch.

Secure Tasks
A secure task is a task which uses the require-authentication handler. The
usage of this handler with task types that have end-user interfaces will
require the end-user to provide their TcEng password at the time they
execute their task. Usage of this handler ensures that the task is actually
performed by the assigned user.
Below is a perform-signoffs task with the require-authentication handler.
Notice the appearance of the Password field.
Below is a perform-signoffs task without the require-authentication handler.

There is no Password field shown.
The require-authentication handler can be used to provide the password

secured user interface for the following task types:
Review task (perform-signoffs sub-task)
Acknowledge task (perform-signoffs sub-task)
Do task
Manual Condition task
The require-authentication handler should be added to the Perform action of

the specific task with associated with the end-user interface. These tasks
include:
Do tasks
perform-signoffs tasks (for Review and Acknowledge)
Condition tasks (manual only)
In the example below, the require-authentication handler has been added

to the Perform action of a Do task:

Activity: Secure Tasks
In this activity, you will browse the design and test a process that uses the
require-authentication handler to enable password-secured tasks.
Step 1: Browse the AA-Secure Tasks Process.
Choose AA-Secure Tasks from the Process Template

drop-down.
In this process, the tasks along the top of the diagram include
the require-authentication handler while the task along the
bottom of the diagram do not.
Select the Authenticated-Do task in the process flow diagram.
Choose the Display Task Handlers icon.
Select the require-authentication handler to observe its usage

in the Perform action of the task.
Expand the Authenticated-Review and

Authenticated-Acknowledge tasks.
Locate the require-authentication handler that has been added

to the Perform action in the perform-signoffs sub-tasks of the
each of these tasks.

Step 2: Test the AA-Secure Tasks Process.

Expand the Item used in the previous activities and select the
ItemRevision.
Set the Process Template to AA-Secure Tasks.
Choose OK.
Select the Inboxes tab.
Expand the Tasks to Perform folders in your users Inbox and

the dba/DBA Inbox.
Select the Authenticated-Do task in your Inbox.
Select the Process View button.
The tasks at the top of the process diagram are the tasks with
the require-authentication handler. They will be automatically
assigned to your users Inbox.
The tasks at the bottom of the process diagram are the tasks
without the require-authentication handler. They will be
automatically assigned to the dba/DBA Inbox
Select the Task View button.
Make sure the Authenticated-Do task in your Inbox is still

selected.

Observe the addition to the user interface of the Password

entry field.
Complete the Authenticated-Do task in your Inbox, by selecting

Done, entering your password, and then choosing Apply.
Select the Do task in the dba/DBA Inbox.
Observe that the password field is not present on this task.
Select Done, then choose Apply.
Select the perform-signoffs task in your Inbox.

Decision column.
Observe the addition of the Password field in the user interface

for the perform-signoffs task.
Select Approve, enter your password, then choose OK.
Select the perform-signoffs task in the dba/DBA Inbox.

Decision column.
Observe the omission of the Password field on the user

interface for the perform-signoffs task.

Select Approve, then choose OK.
Select the perform-signoffs task in your Inbox.
From the Viewer tab, choose the Not Acknowledged link in

the Decision column.
Observe the Password field on the user interface for the

perform-signoffs task.
Select Acknowledged, enter your password, then choose OK.
Select the perform-signoffs task in the dba/DBA Inbox.
From the Viewer tab, choose the Not Acknowledged link in

the Decision column.
Observe the omission of the Password field on the user

interface for the perform-signoffs task.
Select Acknowledged, then choose OK.

Summary
In this lesson you:
Created Generic Workflow Process Templates.
Created Workflow Process Templates for Change Management.
Imported Process Templates
Used Resource Pools in Processes.
Used Conditional Tasks in Processes
Used Secure Tasks in Processes
Lesson
12 Change Management
Purpose
The purpose of this lesson is to demonstrate how to model Change
Management (CM) Change Types.
Objectives
Create a Change Type
Add Handlers to a CM Workflow Process

Change Management
Overview of Change Management
... so that you can model the Change Types that will be used at your company.
Change Management (CM) is the formal process of proposing, controlling and
approving changes to a products definition and configuration.
The CM application collects all the information relative to why a
part changed, including who was involved in the change process.

Benefits of the CM Application
Review of Change Objects
Review of Change Types
Review of Change Object Folder Structure
Creating Change Types
Process Model Design for Change Management
Change Management
Benefits of the CM Application

Collects all data related to the change
Used to propose Solutions, manage Problem Items and track Affected

Items
Easily track the process that the Change Object is going through
Track BOM changes (Adds and Cancels)

The Change Management application is not limited to
engineering data. You can implement a change against any
object model in the database.

Change Management
Review of Change Objects

A Change object is used to control all changes to a products definition and
configuration during its life-cycle.
Key Points
A Change object is a special Item Type (EngChange)
A Change object is viewed in the CM Viewer application
A Change object is represented by a blue "delta" icon
Contains default folders used to collect all the information about the
change
Change Management
Review of Types of Changes

Most companies have different numbering conventions and signature
approval levels for different types of changes. These are referred to as change
classifications.
Some changes are simple and may require only one person to signoff. Other
changes are more complex and may require approval from multiple people,
including external government bodies, suppliers, etc.
Each Change Type has its own unique numbering convention.
Three Change Types are provided with the default Teamcenter Engineering
installation.
CR - Modeled using CMII Change Request (CR) process requirements.
CN - Modeled using CMII Change Notice (CN) process requirements.
WA - Work Authorization (WA)
The setup of these types can be changed or new types can be created based on
the requirements of your business.

Change Management
Review of Change Object Folder Structure

Inside the Change object is a built-in folder structure for the change. You use
these folders to manage the different types of objects in your Change process.
Problem Items
Problem Item data is existing data for which change is being proposed
or implemented.
This data is usually already statused (production) data at the time the
change is started, and therefore is not considered "Target" data in the
workflow process associated with the Change object.
Affected Items
Affected Item data is new data created to replace data identified as
Problem Item data. For example, if 1234 Rev A is identified as Problem
Item data, the new 1234 Rev B would be identified as Affected Item data.
Can be an assembly or piece part.
Since Affected Item data is new data, it is usually identified as Target

data for the workflow process associated with the Change object.
Solution Items
Solution Item data is new data created to implement change to the
Problem Item data, however it is not directly replacing the Problem Item
data. An example of Solution Item data is a new part created for an
assembly identified as Affected Item.
Since Solution Item data is new data, it is usually identified as Target

data for the workflow process associated with the Change object.
Change Management
Creating Change Types
Change Types are created from the application within the Admin
application group.
Choosing Change Type from the Type application dialog box displays the
dialog necessary to model a Change Type.
The modeling of a Change Type is managed using the following variables.
Identification - You will define naming rules for the Change object and
define the behavior of the New Change dialog Assign ID/Rev functions.
Associated Form Type(s) - You will identify 1 to n number of Form Type

instances to be automatically created with the Change object when it is
created. Design of Form Types was covered earlier in this course.
Associated Process Template(s) - You will define 1 to n number of

Process Templates created using the Process Designer application to be
associated with your Change Type.

Change Management
Enter the Change Type Name in the Change Type name field.
Specify whether Effectivity will be shared by toggling Yes or No.
Specify the criteria for Change Id and Rev Id.
Specify which Form Types and Process Templates you will use.
Once you have entered the information describing the Change Type, you can
choose Create to define the Change Type.
Change Management
Activity: Create the TRCN Change Type
In this activity, you will configure a Change Type named TRCN (Training
Change Notice). You will identify for this Change Type two Form Types and a
Process Template you created earlier in the course.
Step 1: Create the TRCN Change Type.
Start the Admin/Type application
Select Change.
Enter the Change Type name: TRCN
Toggle Is Effectivity Shared to Yes.

Change Management
Step 2: Define the settings for Change Id.

You will define the following naming convention for the Change
object of type TRCN.
Use the up arrow to set the length of the Change Id to 9.
Select the + sign next to Change Id.
Enter Range: 1-4
Enter Value: TRCN
From the Format pull-down menu, choose Static.
Step 3: Define the running value, starting with 00001, for Change Id.
Select the + sign next to Change Id, again.
Change Management
Enter the Range: 5-9
Enter the Value: 00001
Select the Format: Running
Step 4: Define the settings for the Rev Id.

Click the + sign next to the value for Rev Id.
Enter the Range: 1
Enter the Value: 0
Select the Format: Running

The fields should now look like the following.
Step 5: Select the Form Types to be associated with the Change Type.
In the Form Types section, select Change Costs from the list of
Defined form types, then choose the + sign.
Select Change Description, then choose the + sign.
Change Costs and Change Description are Form

Types you created earlier in the course.
Step 6: Select the Process Templates to be associated with the Change

Type.
From the list of Defined process templates, select TR Change
Notice, then choose the + sign.

Change Management
Now that you have entered the required data, choose Create.
Step 7: Verify your work by creating a Change object in the My Navigator

application.
Select your Home folder in the Home tab.
Choose FileNewChange...
Change Management
The Create/Revise Change dialog appears.
If necessary, choose More... to set the Change Type to TRCN.
Choose the Assign button for Change Id.

The Change ID TRCN00001 should appear.
Leave the Change Revision ID set to 0.
Enter a Change Name (example: Test).
Use the More Attributes tab and check the Start Process
on Create box.
Checking this box will automatically start the workflow process
listed in the field, which is TR Change Notice.
Select the Description tab and enter a Change Description

of Test TRCN Change Type.
Choose OK.
The new Change object appears in your Home folder.

Change Management
Step 8: View the Change object in the CM Viewer application

Select the TRCN00001-Test change object.
Choose the Open icon.

This launches the CM Viewer application.
Select the tab to view the Change Costs and

Change Description forms associated with the Change Type.
Select the tab to verify the TR Change Notice

process has been started.
Change Management

Change Management
Process Model Design for Change Management

Special workflow handlers are provided with Teamcenter Engineering for
use in process models designed for the Change Management application.
ECM-add-affected-irs-as-target
This handler attaches all ItemRevisions in the "Affected Items"
and "Solution Items" folders to the "Target" folder of the workflow
process. This handler may be used several times in a process.
ECM-att-new-status-for-aff-revs
This handler attaches a separate release status object for each
affected ItemRevision of the targeted EngChange Revision.
ECM-copy-end-item-effectivity
This handler copies effectivity from one affected
revision of the target EC Revision to any other affected
revisions which dont share the same release status.
ECM-notify-competing-changes
This handler notifies a site-defined list of recipients
about competing changes for each affected revision.
ECM-start-new-sub-processes
This handler starts a new process for all
affected revisions of the targeted EC Revision.
EPM-attach-related-objects
This handler attaches the specified related objects of the target objects as
target/reference attachments to the process.
Change Management
TR Change Notice Process

New product definition (new Item Revisions) can be identified and added to
the Affected/Solution Item folders at three possible locations of the TR
Change Notice workflow process.
At the time the Change Object is being created.
During the Prepare Change Do task.
During the Finalize Change Do task.
Since it is possible for new ItemRevisions to be identified after the start of

the process, it will be necessary to add handlers to the process model. These
handlers will notice newly added ItemRevisions and add them and their
contents to the Target list of the process so they will obtain Release Status
properties.
(Complete Action)
ECM-add-affected-irs-as-target
EPM-attached-related-objects

Change Management
Activity: Add CM Handlers to TR Change Notice
In this activity, you will modify the TR Change Notice process template
to add handlers necessary to attach the Affected/Solution Item folder
contents as targets of the workflow process.
Step 1: Access the TR Change Notice process.
Choose TR Change Notice from the Process Template list.
Select Edit Mode .
Choose Yes to take the process template offline.
Step 2: Add handlers to the Prepare Change task.

Select the Prepare Change task in the Task Hierarchy Tree.
Choose the Display the Task Handlers icon .

Select the Complete Task Action.
Set the Action Handler field to ECM-add-affected-irs-as-target.
Choose the icon at the bottom of the dialog.
Change Management
The ECM-add-affected-irs-as-target handler is added to

the Complete Task Action.
Re-select the Complete Task Action.
Set the Action Handler field to EPM-attach-related-objects.
Enter the following arguments:
Select the EPM-attach-related-objects Action Handler that

was just created.
Change the Argument fields to:

Change Management
Again, select the EPM-attach-related-objects Action Handler

that was just created.
Change the Argument fields to:

The Handlers panel should now look similar to the following.
Close the Handlers panel.
Step 3: Repeat Step 2 to add handlers to the Finalize Change task.
Change Management
Step 4: Save your work.

Make sure the Handlers window is closed.
Choose FileClose.
Move the TR Change Notice template to the Available list.
Chose OK.
These handlers ensures that newly created

ItemRevisions added to the affected/solution
Item folders will be added as process targets.

Change Management
Summary
In this lesson you:
Created the Change Management (CM) Change Types.
Added Handlers to a CM Workflow Process
Lesson
13 Business Modeler
Purpose
The purpose of this lesson is to use the Business Modeler application to model
site specific Rules associated with creating and revising data.
Objectives
Create Naming Rules
Create Property Rules
Create Action Rules
Create Deep Copy Rules
Export and Import Business Rules

Business Modeler
Business Modeler
Business Modeler is found in the Admin section of the Application Manager.
This application is a menu-driven system that helps the Teamcenter
Engineering Administrator perform tasks relating to business Rules creation
in Portal. The application allows you to define a set of business Rules to help
administrate the data model behavior in Teamcenter Engineering. You have
the ability to change the Rules on the data model in Teamcenter Engineering
by using menus instead of writing code.
The following are displayed as tabs in the Business Modeler application
Naming Rules Defines the naming conventions for the string

property values of different type objects.
Action Rules Defines the actions needed to be done in
different time phases (pre-condition, pre-action
and post action) for different operations
(Create, Save As, Delete).
Deep Copy Rules Defines whether the Item Revision relational
objects will be copied as object, copied as
reference, or not copied when users perform
Save-As and Revise operations.
Compound Property Allows defining run-time like properties on an
Rules object referencing and relating to a property
on a source object.
GRM Rules GRM (Generic Relationship Management)
rules provides a way for an Administrator to
form a rule (a triplet consists of primary type,
secondary type and relation type) and affiliate
the following constraints with it: Cardinality,
Changeability, Attachability and Detachability
(Cut/Paste Rules).
Type Display Rules Allow you to limit the types of objects that are
available for creation for particular groups or
roles-in-group.
IdContext Rules Determine behavior when creating alternate
and alias identifiers by combining valid
combinations of identifier type, ID context, and
identifiable type.
Property Rules Allow you to control access to and the behavior
of object properties.
In this lesson, we will cover most of the Business Modeler interfaces, but
not all.
Business Modeler
Type Display Rules

Type display rules allow you to control the object types that are available for
creation in Teamcenter Engineering. These rules restrict the display of object
types in the creation dialog windows and can be applied to an entire site, a
particular group, or a specific role in a group.
Type Display Rules can be applied to the following base object types and
their associated subtypes.
Alias
Dataset
Folder
Form
Identifier
Item
MEActivity
MEOP
MEProcess
MEWorkarea
Site, group, and role-in-group display rules are applied using the Type
Display Rules tab in the Business Modeler interface.

Business Modeler
Activity: Creating Type Display Rules
In this activity, you will establish a Type Display Rule to hide Item and
EndItem Item types from the Product Engineer role in the high_performance
group. This rule will allow Product Engineers to only create Document and
Functionality Item types.
Step 1: Create the Type Display Rule.
Start the Admin/Business Modeler application.
Choose the Type Display Rules tab.
Expand the high_performance group listing in the

Organization table.
Select Product Engineer role.
With the Product Engineer role selected, select Item from

the list of Base Types.
Business Modeler
Use the CTRL key to select both the EndItem and Item types in
the Shown Types list.
Choose to remove them from the Shown Types list.
Choose the icon to save the rule.
Step 2: Test the Type Display Rules.

Log out of Teamcenter Engineering.
Log back in to the Engineering/My Navigator application.
Use the tracytr userid (username: tracytr, password: tracytr).
Notice, that the default role for tracytr in the high_performance

group is Design Engineer

Business Modeler
Select the Home folder, then choose FileNewItem..

Notice that all the Item types are available when using the
Design Engineer role.
In the User Settings window, change the Role to Product

Engineer.
Choose OK to save the settings and close the window.
Select the Home folder, then choose FileNewItem..
Business Modeler
Notice, this time that only the Document and Functionality

Item types are available using the Product Engineer role.
Log out of Teamcenter Engineering and log back in using your

student (privileged) userid.

Business Modeler
Naming Rules
Naming Rules allow you to specify valid patterns for naming conventions for
Items, Item Revisions, Datasets, and Forms. End users will get an error
message if the value entered does not match the pattern. At the same time
Naming Rules can be used to force conversion of user input to all uppercase
or all lowercase characters and is used to define the result of using the Assign
feature of New Item and Dataset dialogs.
Naming Rules can be attached to the following properties:
Item ID, Item Revision ID, and Name in Item types
Dataset Name, ID and Revision Number in Dataset types
Name in Form types
Naming Rules allow you to define the pattern for generating IDs. For certain
properties like Item ID and Revision IDs, when you click the Assign icon, the
system generates the ID, based on the pattern defined.
The Naming Rule Operation panel has two tabs. These tabs are:
Edit Naming Rule - Define a Naming rule, with patterns to be matched.
Attach Naming Rule - Attach a Naming rule to a property.
Business Modeler
Activity: Creating and Attaching Item Naming Rules
In this activity, you will establish the following Naming Rules for the Item
type Item.
Item ID: @NNNNN

@ = alpha character: P (production), T (test)
or L (layout)
NNNNN = five numeric characters
Example: P12345, T12345, L12345
Initial value: P00001
Max value: P99999
Convert user input to uppercase
Item Revision ID: NNN

NNN = three numeric characters
Example: 000, 001, 002
Initial value: 000
Max value: 999
Item Name: Free form user input

Convert user input to uppercase
Step 1: Create the Naming Rule for Item ID.

Make sure the Edit Naming Rules tab inside the Naming
Rules tab is selected (default).
Type Item ID in the Rule Name field, and then choose the
Create icon (far right).
Choose the icon to create the first pattern definition.

Business Modeler
The Add Rule Pattern dialog appears.
Enter "P"NNNNN (no spaces) in the top field of the Add Rule
Pattern dialog.
Choose OK.
This adds the first allowed pattern to the display.
Choose the icon to create the second pattern definition.
Type "T"NNNNN (no spaces) in the top field of the Add Rule
Pattern dialog.
Choose OK.
Business Modeler
This adds the second allowed pattern definition to the display.
Choose the icon to create the third pattern definition.
Type "L"NNNNN (no spaces) in the top field of the Add Rule
Pattern dialog.
Choose OK.
This adds the third allowed pattern definition to the display.
Toggle Generate Counters to ON and provide the following:

Initial Value: P00001
Maximum Value: P99999

Business Modeler
Step 2: Create the Naming Rule for Item Revision ID.

Use the drop-down selector for Rule Name to choose the
blank line.
Enter Item Revision ID in the Rule Name field.
Choose the Create icon.
Choose the icon to define the pattern definition.
Type NNN in the top field of the Add Rule Pattern dialog.
Choose OK.
This adds the pattern definition to the display.
Business Modeler
Toggle Generate Counters to ON and provide the following:

Initial Value: 000
Maximum Value: 999
Step 3: Create the Naming Rule for Item Name.

Use the drop-down selector for Rule Name to choose the
blank line.
Enter Item Name in the Rule Name field.
Choose the Create icon.

This rule does not have a Pattern or a Generate
Counters definition. However it is necessary to create
this rule so that when attached, the user input data
can be forced to be all uppercase.
Step 4: Attach the Naming Rule for Item ID.

Choose the Attach Naming Rules tab.

Business Modeler
Expand the Item Class and Item Type nodes.
Select Item ID from the list.
Set Case to Upper, then select Item ID from the Rule Name
drop-down list.
Choose the Attach icon.
Step 5: Attach the Naming Rule for Item Revision ID.

Select Item Revision ID from the list.
Choose Item Revision ID from the Rule Name drop-down list.
Business Modeler
Step 6: Attach the Naming Rule for Item Name.

Select Name from the list.
Set Case to Upper.
Choose Item Name from the Rule Name drop-down list.
Step 7: Close the Business Modeler application.

Business Modeler
Activity: Test Item Naming Rules
In this activity, you will test the Item Naming Rules created and attached in
the preceding activity.
Step 1: Test the Item Naming Rules setup.
Select your Home folder, then choose FileNewItem..
Select Item for the Item Type, then choose Next.
Choose the Assign icon.

Notice the automatic format of the ItemID and Rev fields.
Enter test item (lowercase) in the Name field.
Choose Finish to create the Item.
Notice the Name has been converted to uppercase.
Business Modeler
Try to create an Item by manually inputting the following

parameters:
ID = t12345
Rev = 000
Name = test item
You are able to create the Item because the t, along with
the 5 numeric characters, fit the format, therefore the t
is converted to upper case.
Try to create an another Item by manually inputting the

following parameters:
ID = m12345
Rev = 000
Name = test item
You should NOT be successful because m does not satisfy the

alpha character requirements.
Choose More.
This message lists the valid Item ID requirements.
Choose OK to dismiss the message.
Choose Back.

Business Modeler
To quickly check what format the Item ID should be, place the
cursor in the Item ID field and a hint will appear.
This works the same for the Revision field.
Business Modeler
Property Rules
Property rules allow you to control access to and the behavior of object
properties. You can control whether a property is modifiable, visible, enabled,
or required. In addition, you can set an initial value for a property and define
complex properties comprised of a combination of properties and constant
strings that assign a value to the property. Once configured, property rules
apply to properties as displayed in both the Portal and Web Access interfaces.
Property rules defined on base Property rules defined on base types are
inherited by subtypes. For example, a property rule defined on the Item type
is inherited by the Document type.
The following rules can be applied to object properties:
Modifiable Allows you to place restrictions on the modifiability of an

object property. The following restrictions can be applied:
Read Only Allows users to view the value of the
property but does not allow them to modify the value.
Write Allows users to modify the value of the

property if they have write access to the object to
which the property belongs.
Write Only if Null Allows users to modify the

property only if the existing value is null, or empty.
Initial Value Allows you to specify the initial value to be assigned to
a property when the corresponding object is created.
The initial value rule applies only to the following object
types: Item, ItemRevision, Alias, Identifier, Dataset, and
Form.
Visible Allows you to specify whether a specific object property
is visible in the interface. For example, you can add
runtime properties for internal purposes and set the
visible rule to False to hide them from users. Valid
values: True and False.
Enabled Allows you to specify whether a property is enabled in
the interface. Valid values: True and False.
Required Allows you to specify whether a value must be entered
for a specific object property. Applies only to: Item,
ItemRevision, Alias, Identifier, Dataset, and Form. Valid
values: True and False.
Complex Allows you to specify a combination of properties and
property constant strings to assign a value to a selected property.
Complex properties are derived from one or more
properties depending on the pattern of the rule, for
example $prop1+"string literal"+$prop2. Applies only to:
Item, ItemRevision, Alias, Identifier, Dataset, and Form.

Business Modeler
Activity: Creating Item Property Rules
In this activity, you will first create a Property Rule that establishes a
default Description for the Item type Item. Second, you will modify the
Property Rule to remove the default Description and create a Description
automatically when an Item is created.
Step 1: Create the Property Rule for an Item type.
Select the Property Rules tab.
Select the Item class from the list.
Choose the icon on the far right to create an empty set

of fields.
Business Modeler
Single-click in the Property Name field to access the LOVs,

and then choose object_desc from the list.
Single-click in the Modifiable field to access the LOVs, and

then choose Write from the list.
Enter Company Part in the Initial Value field.
Make sure the Visible field is checked, with the other fields
unchanged.
Step 2: Test the Default Description Property Rule.


Business Modeler
Notice the Description is already filled in with Company Part,

which was defined by the Property Rule just created.
Choose Assign to populate the ItemID and Revision fields.
Enter test rule in the Name field.
Change the Description to Test Company.
Business Modeler
In the Home folder, right-click on the newly created Item and

choose Properties... from the list.
Scroll down in the Properties window and notice that the

Description is Test Company.
This validates that the Default Description of Company Part,

set by the Properties Rule, is still allowed to be changed, due
the Modifiable field set to Write.
Step 3: Change the Property Rule to set an unchangeable Description.

Go to the Admin/Business Modeler application.

Business Modeler
Remove the text from the Initial Value field.
Change the Modifiable field to Read Only.
In the Complex Property field, enter: $item_id+/Company

Part/+$object_name
Make sure the Visible field is checked, with the other fields
unchanged.
Step 4: Test the modified Property Rule.

Business Modeler
Notice this time, the Description is blank because the Initial

Value field was cleared.
Choose the Assign icon to populate the ItemID and Revision

fields.
Enter test rule in the Name field.
Enter Test Company in the Description field.

Business Modeler
In the Home folder, right-click on the newly created Item and

choose Properties... from the list.
Scroll down in the Properties window and notice that the

Description is ItemID/Company Part/TEST RULE.
This validates that the Properties Rule is working. It created

a description from the ItemID, Company Part (text), and the
Item Name, established from the criteria in the Complex
Property field.
Also, even though you entered a description of Test Company,
it was not allowed due to the Property Rule.
Step 5: Clear the Property Rule on the Item class.

Business Modeler
Select any of the fields to select the whole rule.
Choose the icon on the far right to remove the fields.
Close the Business Modeler application.

Business Modeler
Compound Property Rules

The Compound Property Rules functionality enables you to add new
properties to Teamcenter Engineering Types without custom coding and
without having to use the Run-time Properties functionality. However,
Compound Property Rules is not a complete alternative to Run-time
Properties. In more complex scenarios, tou may still prefer to use Run-time
Properties to add complex properties to Teamcenter Engineering Types.
What is a Compound Property?
A Compound Property is a property that can be displayed on an object,

though it is actually defined and resides on another object.
The following terms are used for Compound Properties.
Display Object The object on which the Compound Property is

displayed.
Source Object The object on which the property actually resides.
Source Property The property on the Source Object.
A Compound Property on an object displays the following behavior:

Has default SET and ASK methods.
Inherits access rules from the Source Object.
By default, the read/write permissions of a Compound Property on the

Display Object is the same as that of the Source Object. You can change
the Compound Propertys protection on the Display Object.
If the Source Property is modifiable, then the Compound Property will

also be modifiable. However, if a ReadOnly flag is set on the Compound
Property Rule, the Compound Property will be a non-modifiable property
even if the Source Property is modifiable.
Appears disabled on the Display Object, if the property on the Source

Object is not modifiable.
A default string (such as "****") will be displayed on the Display Object to

indicate that the property is not readable, if the property on the Source
Object is not readable.
A Compound Propertys name and the UI display name can be different

from the property name and property UI display name on the Source
Object.
Business Modeler
The value type of a compound property is the same as that of its

source property. For example, if the value type of the Source Property
is PROP_string, then value type of Compound Property will also be
PROP_string.
If the Source Property is a VLA (Variable Length Array), then the

compound property will also be a VLA.
If an LOV is attached to the Source Property, the same LOV will be

attached to the Compound Property as well.
If the user does not have Write privileges on the object on which the
Compound Property exists, then the Compound Property will be a
non-modifiable property.
If the user does not have Write privileges on the object on which the
Source Property exists, then the user cannot modify the value of the
Compound Property.
To obtain the value(s) of the compound property, the system will traverse
the object hierarchy mentioned in the compound property rule. While
traversing the object hierarchy, if the system fails to reach the Source
Property, the value of the Compound Property cannot be retrieved. An
error message will be displayed and the value will be displayed as a
blank field.

Business Modeler
Activity: Creating Compound Property Rule between EndItem properties

and Items
In this activity, you will first create a Compound Property Rule on the
Item Master form that attaches the Customer and Shipped attributes created
earlier for the EndItem Master form.
Step 1: Create the Property Rule for an Item type.
Choose the Compound Property Rules tab.
Expand the Item class in the Rules tree list and select the
EndItem Type.
Notice, the list of available attributes for the EndItem Type are
displayed in the Rule Operation panel (on the right).
Business Modeler
In the Rule Operation panel, expand IMAN_master_form.
Expand EndItem Master and select the Customer property.
Change the Compound Property Name to AA-Customer.
Choose on the left side of the Rule Operation panel to

create the new Compound Property Rule.

Business Modeler
The Compound Property is attached to the EndItem.
Again, under EndItem Master, select the Shipped property.
Change the name to AA-Shipped, then choose .

Now, two of the EndItem Master form properties are attached
to the EndItem.
Step 2: Test the Compound Properties.

In your Home folder, select EndItem EI001.
Choose ViewProperties....
Business Modeler
Scroll to the bottom of the Properties window and choose

More... (on the left).
Scroll to the top of the Properties window and notice that the
newly attached EndItem properties are displayed.
Set the AA-Customer property to Customer A and AA-Shipped

property to true.
Choose OK.

Business Modeler
Step 3: Delete the Compound Property Rule on the Item type.

Choose the Compound Property Rules tab.
Expand the Item class and the EndItem type to see the
properties.
Select the AA-Customer property and choose delete.
Choose Yes to confirm the delete.
Select the AA-Shipped property and choose delete.
Choose Yes to confirm the delete.
Business Modeler
Action Rules
Action Rules define the actions executed in different time phases
(pre-condition, pre-action, and post action) for different operations (such as
Create, Save as, and Delete). These action Rules are applied to Items, Item
Revisions, and Datasets.
Pre-Defined methods
Teamcenter Engineering provides functionality to apply pre-defined methods
on objects in order to extend the Teamcenter Engineering data model. These
pre-defined methods are part of the base Teamcenter Engineering product.
Canned Method to create objects while creating a new Item or Item
Revision.
Canned Method to check whether the latest Revision of an Item is

released, before creating a new Revision.
Canned Method to copy a variant expression block from a source Item

to a new Item.

Business Modeler
Activity: Default Item Create and Display Behavior
In this activity, you will observe default Item create and display behavior and
modify preferences that control the Item display behavior.
Step 1: Create an Item of Type = Document.
Select Document for the Item Type, then choose Next.
Enter Test Document in the Name field.
Choose Finish to create the Document, then close the New

Item dialog.
Expand the Document and Document Revision objects.
Observe the default objects created when an Item of Type

= Document is created. Document Master and Document
Revision Master forms were created.
Step 2: Modify Document display preferences.

Choose EditOptions...
Select Item in the General list.
On the General tab of the dialog, set Select item type to

Document.
Business Modeler
Select Item Masters in the Shown Relations window, then

choose .
Choose Apply on the Options dialog.
Observe the difference in the Document display.
Before: Document Master After: Document Master form

form is displayed. is now hidden.
Select Item Revision in the General list of the Options dialog.
On the General tab of the dialog, set Select item revision

type to DocumentRevision.
Using the Ctrl key, select ItemRevision Master, engineering,

and Release Status in the Shown Relations window.

Business Modeler
Choose to remove them from the Shown Relations list.
Choose Apply on the Options dialog.
Observe the difference in the Document display.
Before: DocumentRevision After: DocumentRevision

Master form and view are Master form and view are now
displayed. hidden.
Choose Cancel on the Options dialog.

In this activity, you observed that the default Item
create function creates four objects (Item, Item Master,
ItemRevision, and ItemRevision Master). You also
used the Options dialog to hide the two Master forms
and the engineering psuedo folder in the display.
In the next activity, you will use the Business

Modeler application to extend the create action
functions for Items of Type = Document.
Business Modeler
Activity: Create Item Action Rules

In this activity, you will use the Business Modeler application to modify the
Create and Revise characteristics for the Item of type Document to:
Only allow a single Working (no Release Status) Document Revision.
Automatically create a Text dataset for the Document Revision when it

is created.
This activity utilizes pre-packaged methods provided with core
Step 1: Define an Action Rule to cause automatic creation of Text datasets

when Document Revisions are created.
Select the Action Rules tab.
Fully expand the Item RevisionDocumentRevision nodes

as shown below.
Highlight createObjects in the CreatePost-Action branch.

It may take a moment for the dialog to appear.
In the dialog, check the Do you want to apply this canned

method? box.

Business Modeler
Set Object Type To Create to Text.
Set Relation To Attach With to IMAN_specification.
Choose the icon.

Your dialog should look like the following.
Choose Apply.
The following warning message appears.
Choose Yes.
Business Modeler
Step 2: Define an Action Rule to prevent more than a single Working

Document Revision.
Highlight checkLatestReleased in the CreatePre-Condition
branch.
In the dialog, check the Do you want to apply this canned

method? box.
Set Maximum Allowable Working Revisions to 1.
Choose the icon.

Your dialog should look like the following.
Choose Apply.
Choose Yes.
Repeat the previous set-up for checkLatestReleased option in

the RevisePre-Condition branch.

Business Modeler
Your screen should look like the following.
Business Modeler
Activity: Test Item Action Rules
In this activity, you will test the Business Modeler Action Rules for the
Create and Revise characteristics for the Item of Type = Document. The
new Action Rules:
Automatically create a Text dataset for a new Document Revision.
Only allow a single Working (no Release Status) Document Revision.
Step 1: Test automatic Text dataset creation.

Select your Home folder, then choose FileNewItem...
Enter Test Action Rule in the Name field.
Choose Finish to create the Document Item, then close the

New Item dialog.
With the Action Rule set, the Text dataset was created
automatically when the Document Item was created.
Step 2: Test prevention of multiple Working Document Revisions.

Highlight the Document Revision object
Choose FileRevise...
Choose Assign, to populate the Revision field with B, then

choose Finish.

Business Modeler
The following error dialogs appear because you are attempting

to create the next revision (B) of the Document before the
current revision (A) is statused.
Choose OK to dismiss the error dialog, then Close the New

Item dialog.
Highlight the Document Revision object.
Set the Process Template to Quick Release, then choose OK.
You may need to choose ViewRefresh to observe the

application of Status.
Highlight the Document Revision object again.
Choose Assign, to get Revision B, then choose Finish.

This time the Revise action was successful.
Business Modeler
Deep Copy Rules

Deep Copy Rules are used in conjunction with the creation of Item Revisions
using the Save As and Revise menu commands. The setup of Deep Copy
Rules defines what happens to the contents of the Item Revisions (Datasets,
Folders, and Forms, for example).
The Deep Copy Rules tab is used for the Deep Copy System Administration.
It provides a method to set Relation/Type objects that the user can copy from
one revision to another and in what manner will the data be copied. Deep
Copy Rules are only applied to different Item Revision types.
There are three kinds of "Copy" behaviors possible:
Copy as Object - A brand new object of the same type and relation as
the original object is created. An object created by this method will be
totally independent of the original object. This essentially means that any
changes in the copied object will not be reflected in the original object.
Copy as Reference - When the Deep Copy Rule specifies Copy as

Reference a new object is not created for the new Item Revision. A new
reference of the same object is added to the new Item Revision.
Dont Copy - If any of the attachments are specified as Dont Copy, then
these attachments will not be copied forward to the newly created Item
Revision either as a new object or an added reference.

Business Modeler
Activity: Observe Default Item Revise and Save As
In this activity, you will observe the default Rules for the Item Revise and
Save As commands.
Step 1: Observe default Rule for the Revise command.
In the last activity, you used the Revise command to create
Revision B of your Test Action Rule Document.
Expand Revision B of your Document.
Notice that the Revise command did not create a new Text
dataset. The same dataset that is referenced in Revision A, is
also referenced in Revision B. The default for the Item Revise
command is to Copy Reference for all objects contained
in the Item Revision.
Step 2: Observe the default Rule for the Save As command.

The Save As command is used when a user wishes to create a new
Item (ID vs. Rev) from the definition of an existing Item Revision.
Highlight Revision B of your Test Action Rule Document.
Choose FileSave As...
Choose Assign to generate a new unique ID and initial Rev ID.
Change the Name to Default Save As.
Choose Finish, then close the New Item dialog when the Item
has been created.
Business Modeler
Because you had a Document Revision selected when you created

the new document, a reference of the new Document is not added
to the selected object. Instead, the reference is added to your
Newstuff folder.
Fully expand the Document and Document Revision object in
your Newstuff folder.
Like the Revise command, the Save As command did not create a
new Text dataset. The same dataset that is referenced in Revision
B of the first Item is also referenced in Revision A of the new Item.
The default for the Item Save As command is to Copy Reference
for all objects contained in the baseline Item Revision.
In the next activity, you will use the Deep Copy component
of the Business Modeler application to change
the default Copy Reference behavior to Copy Object.

Business Modeler
Activity: Create Deep Copy Rules for Items
In this activity, you will create Deep Copy Rules for the DocumentRevision to
Copy as Object objects with relation of IMAN_specification.
Step 1: Define Deep Copy Rules for DocumentRevision Save As.
Choose the Deep Copy Rules tab.
Expand the DocumentRevision node in the Deep Copy Rules

tree.
Highlight Save As.
In the dialog, set Relation Types to Specifications.
Check the Required check box.
Choose the icon to the right of the Copy As Object window.

Your dialog should look like this.
Choose Apply.
Choose Yes to save the change.
Establish the same Rule as above for the Revise command

for DocumentRevision.
Business Modeler
Activity: Test Deep Copy Rules for Items
In this activity, you will test the Deep Copy Rules for the DocumentRevision
to Copy as Object objects with relation of IMAN_specification.
Step 1: Start the Engineering/My Navigator application.
Step 2: Test the Deep Copy Rule for Revise.

Select your Home folder, then choose FileNewItem...
Enter Test Revise in the Name field.
Choose Finish, then Close the New Item dialog.
Highlight the Document Revision object.
Observe the application of status.
Highlight the Document Revision object (only).
Choose Assign.
Choose Finish, then close the New Item dialog.

Business Modeler
This time, the Revise command has created a new Text dataset.
The Revise command did create a new dataset,

however, the name of the new dataset is the same as
the original. You can tell it is a new dataset because it
does not have a Status flag, like the original dataset.
The name of the new dataset could be changed to a
different value using the Properties dialog
In the last activity, the Revise command did not create a new
Text dataset.
Last activity:
Step 3: Test the Deep Copy Rule for Save As.

Highlight Revision A of your Test Revise Document.
Choose FileSave As...
Choose Assign to generate a new unique ID and initial Rev ID.
Change the Name to Test Save As.
Choose Finish, then close the New Item dialog.
Business Modeler
Because you have a Document Revision selected while you are

creating a new Document, a reference of the new Document
is not added to the selected object. Instead, the reference is
added to your Newstuff folder.
Fully expand the Test Save As Document and Document

Revision object in your Newstuff folder.
This time, the Save As command has created a new Text

dataset.
Like the Revise command, the Save As command
did create a new dataset, however, the name of the
new dataset is the same as the original. Again, you
can tell it is a new dataset because it does not have
a Status flag, like the original dataset. The name
of the new dataset could be changed to a different
value using the Properties dialog
In the last activity, the Save As command did not create
a new Text dataset.
Last activity:

Business Modeler
Business Modeler Import/Export Rules

The Business Modeler Application gives you the capability to import and
export Business Rules. This allows Business Rules configured and applied
at one company site to be exported to an XML file and imported into the
Business Rules Application of a different company site.
Importing Business Rules may overwrite the existing Business Rules
configuration at a site. To avoid overwriting the Business Rules configuration
at the current site, it is strongly recommended that the current configuration
be exported to another XML file, which can then be compared or merged with
the new XML file intended to be imported. The merged XML file can be
imported into your Business Modeler to apply the new configuration.
Business Modeler
Activity: Use the UI to Export Business Rules
In this activity, you will interactively export the current Business Rules
defined in the Business Modeler application.
Step 1: Export All Business Rules
Open the Admin/Business Modeler application.
Choose the Export icon (bottom right).
In the Export dialog, make sure All Business Rules is checked.
Navigate OS directories to the ...aa_class/business_rules

directory.
Enter all_business_rules.xml in the File Name field.
Choose Export.
Locate and open the all_business_rules.xml file in a text

editor.
After reviewing the file, close the text editor.
Step 2: Export Naming Rules only.

In the Business Modeler application, again choose the Export
icon.

Business Modeler
Make sure only the Naming Rules button is toggled on.
Verify you are still in the ...aa_class/business_rules directory.
Enter naming_rules.xml in the File Name field.
Choose Export.
Locate and open the naming_rules.xml file in a text editor.
After reviewing the file, exit the editor without saving.
Business Modeler
Activity: Use the UI to Import Business Rules
In this activity, you will interactively import a Naming Rules file that will
detach the Item ID, Item Revision ID and Item Name naming rules from their
respective data objects. This must be done in order to return to the default
naming rules for the remainder of the course.
Step 1: Access the Import window.
In the Business Modeler application, make sure the Naming
Rules tab is selected.
Choose .
The Import window appears.
Step 2: Access the naming rules import file.

In the Import window, navigate to the
...aa_class/business_rules directory.
Select the undo_naming_rules.xml file.
Choose Compare and Import.
Choose Import.

Business Modeler
The Business Rules Import Comparison Dialog appears.
This window allows you to analyze the differences between the

existing Naming Rules and the ones to be imported. You can
display both Old and New together or just the differences in
the rules. You can also display just the New rules or just the
Original rules.
Step 3: Analyze the differences in rules and then import the rules.
Make sure Display as Old/New is set.
Business Modeler
Scroll down to view the differences in the existing rules on the

left and the rules to be imported on the right.
Choose OK to import the Naming rules.
Step 4: Verify that the Naming Rules are detached.

Choose the Attach Naming Rules tab.

Business Modeler
Expand the Item Class and Item Type nodes.
Select Item ID from the list.

There should be no rule listed.
Select Item Revision ID and Item Name from the list to make
sure there are no rules attached.
Business Modeler
The import_export_business_rules utility
Another method provided by Teamcenter Engineering for both

importing and exporting business rules to and from the database is the
import_export_business_rules utility. This utility allows for the importing
and exporting of business rules without having to log into the Business
Modeler application in the Portal interface.
As with the interactive import function, the import_export_business_rules
utility may overwrite existing Business Rules. To avoid the possibility
of losing existing rules, one recommended method is that the current
configuration be exported first (as a backup) and then merged with the (new
rules) XML file to be imported before using the import_export_business_rules
utility. The exception may be if using the merge_add option. Still, as a
precaution, it is good practice to export (to save) all rules before making any
modifications to the existing Business Rules using the import functions.
The syntax is as follows.
import_export_business_rules
-u=userID
-p=password
-g=group
-file=xml_file_name
-action=import
[-merge_add] | -merge_replace | -replace]
-action=export
[-type=type_name]
[-rule=(valid_rule_class_name)]
-h

Business Modeler
Summary
In this lesson you:
Created Naming Rules
Created Property Rules
Created Action Rules
Created Deep Copy Rules
Interactively Exported Rules Definitions
Interactively Imported Rules Definitions
Reviewed the import_export_business_rules utility
Lesson
14 Preferences and Options
Purpose
The purpose of this lesson is to modify the system preferences and options.
Certain preferences can be set for the site and different groups, roles, and
users.
Objectives
Suppress Menu Commands from the Portal Interface
Assign Default Process Templates
Set Preferences and Options for Groups and Roles

Preferences and Options
Setting Preferences and Options
... so that you can alter the default Teamcenter Engineering system for
groups, roles, and users.
The My Navigator, Product Structure Editor, etc., applications can
be changed by removing menu options from these applications for
certain Groups and/or Roles. Additional settings can alter the default
Teamcenter Engineering system for site, groups, roles, and users.

Command Suppression
Assigning Default Process Templates
Preference Settings Hierarchy
Preference Settings to Consider
Environment Variable Settings
Command Suppression
Command suppression allows you to remove (suppress) one or more menu
options from the default Teamcenter Engineering Portal applications. This
can be useful if you determine that certain functions at your site should only
be performed by a particular Teamcenter Engineering role or group.
Often small sites remove such menu options as ToolsImport from
application menus because they do not operate in a global environment.
Conversely, large sites often allow all users to perform these actions
because they may have multiple Teamcenter Engineering sites. Command
suppression allows each site to implement these and other Teamcenter
Engineering functions according to their needs.
Command suppression is implemented as a tree of shown and hidden menu
options for a defined Teamcenter Engineering role and/or group.
Users can change their group/role during a Teamcenter Engineering session
by choosing EditUser Setting...Session. If they choose another Role or
Group, the appropriate menu entries will be hidden or shown.
Important Caveat
The following caveat applies to customizing Teamcenter Engineering with

Command Suppression:
The Command Suppression dialog cannot be used to move options from
one menu to another or to add menu options. Menu entries can only
be suppressed.

Command Suppression Dialog

You can use the Command Suppression application from the Teamcenter
Engineering Admin application group to define which command entries
should be suppressed for each defined Teamcenter Engineering role and/or
group.
Choosing an application from the Application Tree (upper left pane)

causes the Command Tree (right pane) to display the available menus
and commands for the selected application. Use the Organization Tree
(lower left pane) , select the group, role or group/role combination. From the
Command Tree select a menu or command and choose the Show or Hide
button.
When finished defining the menus suppressed for a specific group and/or role,
you must use FileSave. The Command Suppression definitions are saved
as entries in the IMAN_DATA/.iman_env file.
Activity: Modify Command Suppression Definitions
In this activity, you will change the shown menu entries for the Standards
Engineer role.
Step 1: Set up Command Suppression for the Standards Engineer role.
Start the Admin/Command Suppression application (may
have to use the More... option).
Under Applications, choose My Navigator.
Under Organization, expand the standards group and select

the Standards Engineer role.
Step 2: Suppress the Import command under the Tools menu.

Expand the Tools menu.
Select Import.

Choose the Hide button.

Notice there is now a red line through Import.
Choose the Save icon.
Step 3: Change your group and role to verify the suppressed entries.
Choose Session.
Select the standards group.
Select the Standards Engineer role.
Choose OK.
Choose OK for the message dialogs that result from your

change in user status.
Step 4: Review the result of Command Suppression.

Select the Tools pull-down menu.
Notice the Import entry is missing.
You may need to close and re-open the My Navigator

Application to view the effects.
Step 5: Change back to the dba group.

Choose Session.
Select the dba group.
Select the DBA role.
Choose OK.
Choose OK for the message dialogs that result from your

change in user status.
Select Tools.
Notice the Import entry is present.

The Command Suppression for the Standards
Engineer role has been setup in the database.

Assigning Default Process Templates

Once you create Process Templates, you can assign specific process templates
for a group. The group can have multiple assigned process templates with
each process template based on the type of object being initiated from the
FileNewProcess... window.
The assigned process template will be placed in the Process Template field as
a user initiates a certain type of data while working within a certain group
when choosing the Assigned process template filter button.
Group and Role Preference Files

Process Templates are assigned by using IMAN_DATA/gpfiles for
the specified group. If an assigned process template was set for the
high_performance group, the following file would be created with the
preference setting defined.
IMAN_DATA/gpfiles/high_performance.iman_env
IMAN_ItemRevision_release_procedure=
Import Release
The file name format is <group>.iman_env. The preference allows multiple

values to suggest a list of assigned process templates for the given object type.
The Workflow Designer application provides a graphical interface for creating
the IMAN_DATA/gpfiles/<group>.iman_env file. From the Workflow Designer
application choose EditTemplate Filter.
Choose Group
Choose Type
Setup Assigned
Templates
With the example shown above, the following preference would be added to
the IMAN_DATA/gpfiles/high_performance.iman_env file. If the file did
not exist, it would be created first.
TR Change Notice
Import Release

Blocking Users from Choosing from All Process Templates

A preference can be set to disable users from choosing any process template
when choosing FileNewProcess... This assumes that process templates
have been assigned.
Setting CR_allow_alternate_procedures=any allows the All Process Template
Filter button to be selected.
Setting CR_allow_alternate_procedures=none will remove the

All/Assigned buttons from the FileNewProcess... dialog.
Preference(s): CR_allow_alternate_procedures
File(s): $IMAN_DATA/.iman_env
Default: any
Activity: Assign Default Process Templates
In this activity, you will establish default process templates for

data types initiated by certain groups by setting the following:
Group Data Type Process Template

dba Text Quick Release
dba Item Revision Import Release
Group Data Type Procedure

high_performance Item Revision TR Change Notice
Step 1: Create the dba group preference file in the IMAN_DATA/gpfiles

directory.
Go to the IMAN_DATA/gpfiles directory.
Create a new text file named dba.iman_env
Open the file in a text editor and add the following entries
IMAN_Text_release_procedure=
Quick Release
Import Release
The exact spelling, spaces and case of the Process

Templates must be the same as created earlier.
Save and close the text editor.
Step 2: Create the high_performance group preference file in the

IMAN_DATA/gpfiles directory.
In the same directory (gpfiles), create a new text file named
high_performance.iman_env.

Open the file in a text editor and add the following entries
TR Change Notice
The exact spelling, spaces and case of the Process
Templates must be the same as created earlier.
Step 3: Use Workflow Designer Template Filter tool to assign defaults.

Choose EditTemplate Filter.

It may take a moment for the contents of the dialog
to populate.
The Process Template Filter Dialog appears.
Set the Group Name to corrective_action.
Set the Object Type to ItemRevision.
Select TR Change Notice from the Defined Process Template

list.
Choose the left-pointing arrow to move it to the Assigned

Process Template list.
Choose OK.
Locate and view the corrective_action.iman_env file in the

IMAN_DATA/gpfiles directory.
Step 4: Verify that your work has influenced the FileNew Process
dialog behavior.
Go the Engineering/My Navigator application.
Expand a previously created Item and select the ItemRevision.
Choose the Assigned button.
Notice the Process Template automatically changes to the

Import Release process. This is because the default process
for an Item Revision being release by someone from the dba
group is set to Import Release.
Choose Cancel to close the Process window.

Preference Settings Hierarchy

It may be required to have different values for preferences for different
Groups, Roles or even Users. To accommodate this requirement, Teamcenter
Engineering allows for preferences to be set in a variety of possible locations.
The following list and table identify these locations and define the precedence
hierarchy used to resolve setting conflicts in multiple locations.
1. A preference set via shell commands.
2. A preference set in a user preference file
3. A preference set in a role preference file.
4. A preference set in a group preference file.
5. A preference set in the site preference file.
Summary of the Preference Hierarchy (Order)
Setting Files
1 Shell In Shell n/a
2 User IMAN_USER_PFILE IMAN_DATA/upfiles/<user>.iman_env
3 Role IMAN_ROLE_PFILE IMAN_DATA/rpfiles/<role>.iman_env
4 Group IMAN_GROUP_PFILE IMAN_DATA/gpfiles/<group>.iman_env
5 Site n/a IMAN_DATA/.iman_env
To easily set a group or role preference, first

use EditOptions to set the preference inside
IMAN_USER_PFILE/<user>.iman_env, then copy the preference
from your IMAN_USER_PFILE/<user>.iman_env to the desired
file(s) inside IMAN_DATA/gpfiles, IMAN_DATA/rpfiles or
IMAN_DATA.
Preference Settings to Consider
Users Allowed to Create/Modify Preset Revision Rules
The IMAN_config_rule_users preference lists Teamcenter Engineering

users that are allowed to create, delete, and modify preset configuration
rules. It accepts one or more strings as value(s); each string must be a valid
Teamcenter Engineering user.
Preference(s): IMAN_config_rule_users
File(s): $IMAN_DATA/.iman_env SITE preferences file
Default: unset
BOMView Type to Open in PSE

The PSE_default_view_type preference sets the default BOM view used
when opening PSE or pasting in an assembly when more than one BOM view
is used at the site. This preference accepts a single string as a value; the
string must be a valid BOM view type.
Preference(s): PSE_default_view_type
File(s): .iman_env
Default: view
Number of Dataset Versions to Keep

TheAE_dataset_default_keep_limit preference sets the number of old
dataset versions to store in database. When this number is exceeded, the
oldest dataset version is deleted if it is not referenced. This preference
accepts a single integer as a value.
Preference(s): AE_dataset_default_keep_limit
Default: 3

Status to Use with Open or Print PSE

The IMAN_config_rule_name preference sets default revision
(configuration) rule that is used when opening and printing BOMView or
BOMViewRevisions. This preference accepts one or more strings as value(s);
each string must be a valid revision rule. If not set, Latest Working/Any
Release Status is used. It may be placed in the user, group or site preference
file.
Preference(s): IMAN_config_rule_name
File(s): .iman_env
Default: Latest Working
User Auto Login

The IMAN_auto_login preference enables or suppresses auto-login feature
for the entire site. Auto login uses operating system user names and
passwords to log into Teamcenter Engineering.
Preference(s): IMAN_auto_login
Possible Values: TRUE (Enable auto login)
Default: FALSE (Disable auto login
Environment Variable Settings

Teamcenter Engineering software uses many environment variables. These
variables allow Teamcenter Engineering to be quickly adapted and configured
to any site.
Teamcenter Engineering stores environment variable settings in a script
file: IMAN_DATA/iman_profilevars. Recall these Teamcenter Engineering
environment variables from an earlier lesson.
IMAN_ROOT - Top (root) directory of the Teamcenter Engineering
directory structure. This environment variable must be set before running
the Teamcenter Engineering application or command line utilities.
IMAN_DATA - Directory containing Teamcenter Engineering data files.

This variable is set during Teamcenter Engineering installation and
added to IMAN_DATA/iman_profilevars.
IMAN_BIN - Location of the Teamcenter Engineering utilities.
ORACLE_SERVER - Oracle server network node.
ORACLE_SID - Unique name of Oracle database instance associated

with IMAN_DATA.
You may also have custom environment variables that are used during a
session. These custom environment variables can be set in various ways,
including:
Using the IMAN_ROOT/local/data/iman_local_setup file
Writing a custom script that sets environment variables
To set customer environment variables in the first option, the

file IMAN_ROOT/local/data/iman_local_setup is executed by
IMAN_DATA/iman_profilevars as Teamcenter Engineering starts or as
IMAN_DATA/iman_profilevars is sourced.
Instead of using the file IMAN_ROOT/local/data/iman_local_setup, a
script can be written and executed by users to set environment variables.
Since the script(s) would be separate from IMAN_ROOT, different databases
can be started having different environment variable settings.

Environment Variables Settings to Consider
User Preference File Location
The IMAN_USER_PFILE environment variable is set to a directory

containing the users .iman_env preference file. This variable accepts a single
string as a value which must be the full operating system path to the directory.
Environment Variable: IMAN_USER_PFILE

Default: IMAN_DATA/upfiles
Teamcenter Engineering SysLog File

The IMAN_TMP_DIR environment variable is set to a directory for storing
application log files. This variable accepts a single string as a value; this
string must be the full operating system path to the directory. If this variable
is not set, the /tmp directory is used.
Environment Variable: IMAN_TMP_DIR

Default: not set
The IMAN_KEEP_SYSTEM_LOG environment variable is used to determine

whether Teamcenter Engineering log files are kept when there were no
errors. This variable is set to any string as a value. If set, logs files are kept.
Environment Variable: IMAN_KEEP_SYSTEM_LOG

Default: not set
Activity: Modify Site/Group/Role Preferences
In this activity, you will set group and role preferences for your
implementation.
Step 1: Locate the IMAN_DATA/gpfiles directory.
The current group preference files are listed. You will create a
new file.
Step 2: Add the assembly group preference for PSE_default_view_type.

From an earlier activity, the IMAN_DATA/.iman_env site
preference file has PSE_default_view_type=engineering.
Therefore engineering is the default for the site.
Create a new text file named assembly.iman_env
Add the following lines to the file:

shipping
Step 3: Add a Manufacturing Engineer role preference.

Locate the IMAN_DATA/rpfiles directory.
Create a new text file named manufacturing_engineer.iman_env

The preference file name is lower case and an
underscore is used in place of the space in the role
name.
Add the following lines to the file.

shipping
Save and close the editor.

The preference file for the Manufacturing Manager
role could be easily created by copying the current file
to manufacturing_manager.iman_env.

Summary
In this lesson you:
Suppressed Menu Commands from the Portal Interface
Assigned Default Process Templates
Set Preferences and Options for Groups and Roles
Lesson
15 Import Non-CAD Data into

Purpose
The purpose of this lesson is to import non-CAD file data into the Teamcenter
Engineering environment.
Objectives

Import file data into Teamcenter Engineering using the Portal interface
Import file data into Teamcenter Engineering using the import_file

command line interface utility

Import Non-CAD Data into Teamcenter Engineering
Import Existing Files

... so that you can import existing files into the Teamcenter Engineering
database.

Overview of Importing Files
Importing Files Interactively
Importing Files Using the import_file Utility
Overview of Importing Files

You can use Teamcenter Engineering to manage information created in the
native environment. Importing data is the introduction of files or objects into
Teamcenter Engineering. When you import files, a dataset is created with
named references to a copy of the original files located in an Teamcenter
Engineering volume.
You may import files for these reasons:
Import document/image data
Migrating legacy data
Placing data created outside of Teamcenter Engineering into the database
You can use both interactive and batch mechanisms to import data. Any of
the following approaches are available to you for importing data:
Interactive File Import for importing files
The import_file utility for batch importing files

The ug_import utility, which will be discussed later, is
recommended for importing Unigraphics NX part files.
Key Points
You can import more than one file into one dataset.
You can use the Named References window to add additional files to the
dataset after the initial import process.
The import process will set User and Group ownership on the newly
created dataset. Make sure you are in the correct group for appropriate
ownership.

Importing Files Interactively

You can use either of the following methods for interactively importing files
into Teamcenter Engineering.
Create New Dataset and Import File at the same time

This interactive File Import method allows you to create a dataset and import
the file into it all at the same time.
Import File into an existing Dataset

This interactive File Import method allows you to import a file into a dataset
that currently resides in the Teamcenter Engineering database.
Activity: Create New Dataset and Import File
In this activity, you will import an ASCII file into Teamcenter Engineering.
Step 1: Change your current group so that the dataset created during the
import will be owned by the standards group.
Start My Navigator application.
Choose EditUser Setting....
Select Session.
Set the Group to standards.
Choose OK.
Step 2: Import the selected file into Teamcenter Engineering.

Select the Newstuff folder.
The New Dataset dialog is displayed.
Enter Rubber Specs 1 in the Name field.
Change the Type to Text.
Select the Import File icon.

The Import File dialog is displayed.

Navigate to the ...aa_class/import_file directory.
Select the rubber_specs.txt file, then choose Import (or simply

double-click on rubber_specs.txt).
The Import File dialog disappears. Notice the
rubber_specs.txt file name in the New Dataset dialog. Also,
notice that the directory path is listed in the Import field.
Choose OK.
This completes the Import process. The text dataset should
now be in your Newstuff folder.
Step 3: Review the imported file.

Expand the Newstuff folder.
If the new dataset is not visible, select the Newstuff
folder and choose ViewRefresh.
Open the Rubber Specs 1 dataset.
Review the file contents.
Exit the editor application without making any changes.
Step 4: Change back to the dba group.

Choose EditUser Setting....
Make sure Session is selected.
Set the Group to dba.
Choose OK.
You have successfully imported the rubber_specs.txt file.

Activity: Import File into Existing Dataset
In this activity, you will import a native file into an existing dataset in
Step 1: First, create an empty dataset.
Select the Newstuff folder.
The New Dataset dialog is displayed.
Enter Rubber Specs 2 in the Name field.
Make sure Type is set to Text.
Choose OK.
The Text dataset is created in your Newstuff folder.
Step 2: Import the rubber_specs.txt file into the dataset.

Select the Rubber Specs 2 dataset.
Choose ViewNamed References...

The Named References dialog is displayed with a warning that
No named references are found.
Choose OK to close the warning message window.
Select the Import... button.

The Import File dialog is displayed.
Navigate to the aa_class/import_file directory.
Select the rubber_specs.txt file.
Choose the Import button.

The Import File dialog disappears and the rubber_specs.txt
file is now listed in the Named References dialog.
Choose Close.

Importing Files Using the import_file Utility

The import_file utility allows you to import files into the Teamcenter
Engineering database according to a set of user-specified arguments. These
arguments supply user identification information and dataset information
to be associated with the imported file. The arguments may be specified on
the command line for a single file import or in a command file for multiple
files (bulk) import.
Important Concepts
This utility imports one file at a time into a dataset.
You can subsequently add more files to a dataset.
Use the import_file utility to import various files.
The dataset is placed in the Newstuff folder.
The import_file utility will set User and Group ownership on the newly
created dataset.
In this case the import_file utility will be used to import a single ASCII text
file. The following arguments are necessary. In a later lesson the import_file
utility will be used for more advanced features.
IMAN_ROOT/bin/import_file -f=<filename>
-type=<datasettype> -d=<dataset_name>
-ref=<named_reference> [-vb] [-log=<filename>]
Arguments
-f=<filename> Import a single file filename into

Teamcenter Engineering. The full path
must be provided if the file does not reside
in the current working directory. The -f
and -i arguments are mutually exclusive.
-d=<dataset_name> Dataset you are importing the file to.
-type=datasettype Define dataset type in Teamcenter
Engineering (e.g., Text).
-ref=names_reference Type of named reference associated with
the file. Each dataset type defines one or
more Named References associated with it.
-vb Verbose mode. Displays maximum amount

of information. Non-verbose sessions only
display error messages.
-log=<filename> Log created datasets to <filename>.
Otherwise -log=- can be used to print to
your terminal window.
To override the default object ownership, use the -u=<user>

-p=<password> -g=<group> arguments. Make sure the file will
be imported to the desired volume.
The following example demonstrates using the import_file utility:
1. To import a single operating system file report.dat into Teamcenter
Engineering as Text dataset report1, enter the following command on a
single line:
IMAN_ROOT/bin/import_file -f=report.dat -type=Text
-d=report1 -ref=Text -vb -log=import.log

Activity: Import File using import_file Utility
In this activity, you will import other files into the Teamcenter Engineering
database using the import_file utility.
To do this activity you will execute a pre-written script that contains the
import_file command. The import_file command used by the script is listed
in the activity.
Step 1: Import a file using the import_file utility
If necessary, locate and modify the import_file.scr.bat
(import_file.scr on Unix) script per the instructors instructions
Open a terminal window with the Teamcenter Engineering

environment set.
Type: cd import_file
Type: import_file.scr.bat (import_file.scr on Unix)
The following command is used in the script to import the

plastic_specs.txt file.
import_file -f=plastic_specs.txt -d="Plastic Specs"
-type=Text -ref=Text -log=-
The -u=<user> -p=<password> -g=<group>

arguments have also been used to set the object group
ownership to standards (-group=standards).
Close the terminal window.
Step 2: Review the imported file.

Expand the Newstuff folder.
If the new dataset is not visible, select the Newstuff folder

and choose ViewRefresh.
Double-click on the Plastic Specs dataset to view the file.
Review the file.
Exit the editor application without making any changes.
You have successfully imported the Plastic Specs file.

Summary
In this lesson you:
Imported file data into Teamcenter Engineering using the Portal interface
Imported file data into Teamcenter Engineering using the import_file

command line interface utility
Lesson
16 Status Imported Data
Purpose
The purpose of this lesson is to show the different methods of protecting
migrated legacy data
Objectives
Use a Quick Release Process to Status data
Use the release_man Utility to Status data

Status Imported Data
Protecting Imported Data

... so that you can ensure proper protection for migrated/imported data.

Quick Release Technique
The release_man command interface utility
Quick Release Technique

After data has been imported into Teamcenter Engineering you may choose to
status the data. The import step only imports the data and usually leaves the
data in a unreleased, writable state.
The imported files may have been in a statused state outside of Teamcenter
Engineering and now that the data has been imported to Teamcenter
Engineering it must be statused there.
Since the import process merely created a dataset in Teamcenter Engineering
and copied the native file to the Teamcenter Engineering volume, a simple
process will be adequate.
Two release techniques could be used, depending on the specific data:
The Quick Release (no reviewers)
A Single Level Release (a reviewer in one level)

Activity: Status data using Quick Release Process
In this activity, you will use the Quick Release process to status data
previously imported.
Step 1: Release the Plastic Specs Text dataset previously imported.
Expand your Newstuff folder to show the Plastic Specs

dataset.
Select the Plastic Specs Text dataset.
The New Process dialog appears.
Notice the Plastic Specs dataset is listed in the Targets area.
Choose Assigned for the Process Template Filter.
Notice the Process Template changes to Quick Release because

of the preferences you set in an earlier lesson.
Choose OK.
Step 2: Check the Release Status.

In My Navigator, select the Plastic Specs dataset.
Choose ViewRefresh.
The Status Flag should be visible.
The Plastic Specs dataset is released in the database.

release_man Utility
The release_man utility is used to status objects in batch mode without
creating jobs and audit files.
Important Concepts
Only a userid with administrative rights can execute this utility.
Objects to be statused must be placed in a folder that resides in the Home

folder of the user executing the utility.
If the objects in the folder are Item Revisions, the contents of the Item
Revision with IMAN_specification relation and BOMView Revision objects
can be statused also by using the -spec argument.
The release_man utility can also be used to "un-status" data.
Synopsis
$IMAN_ROOT/bin/release_man -u=<user_id> -p=<password> -g=dba
[-spec] [-unrelease] -retain_release_date
-status= -folder=<folder_name>
Arguments
-spec Specifications and BOMViewRevisions of
an Item Revision in the release folder are
released along with the Item Revision.
-unrelease Remove the status type identified by the
-status argument.
-retain_release_date If the object to be released has already been
released, retain the original release date.
-status Valid Status Type to be applied to all
objects.
-folder Release folder name. Folder must reside in
the Home folder of the user executing the
utility.
The following example demonstrates using the release_man utility to

apply a status of "Released" to all the objects residing in the folder named
"to_release." This folder is referenced in waynetrs Home folder and waynetr
is a member of the dba group.
IMAN_ROOT/bin/release_man -u=waynetr -p=waynetr -g=dba
-status=Released -folder=to_release
The following example demonstrates using the release_man utility to remove

the status "Released" from all the objects residing in the folder named
"to_unrelease." This folder is referenced in waynetrs Home folder and
waynetr is a member of the dba group.
IMAN_ROOT/bin/release_man -u=waynetr -p=waynetr -g=dba
-status=Released -folder=to_unrelease -unrelease

Activity: Using release_man to Status Data
In this activity, you will use the release_man utility to apply status.
Step 1: Populate a release folder
Create a folder in your Home folder named release_man.
Copy Rubber Specs 1 and Rubber Specs 2 from your Newstuff

folder to the release_man folder.
Step 2: Execute the release_man utility to status data.

Open a command window with the Teamcenter Engineering
environment set.

release_man -u=<your userid> -p=<your password>
-g=dba -status=Released -folder=release_man
In My Navigator, choose ViewRefresh Window.

The Status Flags should now be visible.
Step 3: Execute the release_man utility to un-status data.

Return to the command window and enter following:
release_man -u=<your userid> -p=<your password>
-g=dba -status=Released
-folder=release_man -unrelease
In My Navigator, choose ViewRefresh Window.

The Status Flags should now be removed from datasets.
Summary
In this lesson you:
Used a Quick Release Process to Status data
Used the release_man Utility to Status data

Lesson
17 Setup for NX Integration
Purpose
The purpose of this lesson is to configure your system for NX specific
requirements.
Objectives
Make Decisions Regarding the NX Data Model at Your Site
Setup Seed Part Files for NX
Define NX -to- Teamcenter Engineering Attribute Mappings
Set NX Manager Preferences and Options
Use Unique Process Template Features for NX Data

Setup for NX Integration
NX/Teamcenter Engineering Integration Overview
... so that you understand the integration between Teamcenter

Engineering and NX (NX Manager) and can make decisions regarding
the modeling of NX data within Teamcenter Engineering at your site.

Terminology
Item Structure and Named References
Create Part Files
Storage of Associated Files
Access Control
UGMASTER / UGPART Behavior
Terminology
The table below lists several NX terms along with the corresponding
Teamcenter Engineering term.
Unigraphics Teamcenter Engineering

Part Item
Part Revision Item Revision
Part File Dataset
Part Number Item ID
Master Part File UGMASTER Dataset
Non-master Part File (specification UGPART Dataset
or manifestation)
Non-master Part File (altrep) UGALTREP Dataset
Component Occurrence
Lock (part file geometry) Check-Out (Dataset)
Unlock (part file geometry) Check-In (Dataset)
Lock (part file structure) Check-Out (BOMView Revision)
Unlock (part file structure) Check-In (BOMView Revision)
When you work in NX, you manipulate Parts, Part Revisions and Part Files.
These correspond to Items, Item Revisions and Datasets in the Teamcenter
Engineering.

Item Structure and Named References

The figure below shows the typical structure of an Item that contains NX
data. This is the 2111 Frame part, currently with a 000 ItemRevision.
Inside the ItemRevision is the 2111/000 UGMASTER for the master part file.
Additionally the ItemRevision contains the 2111_DWG and 2111_MFG for the
non-master drawing and NC programming part files.
Each dataset contains files, or named references.
The named references for the 2111 datasets are shown below.
Named
References
for
2111_DWG
Name
References
for
2111_MFG
Name
References
for
2111000

BOM Views and BOM View Revisions

BOM Views are used to manage product structure information for an Item.
Similarly, BOM View Revisions are used to manage product structure for
Item Revisions.
When you add a component to an assembly, you are creating an occurrence of
that Item or Item Revision in the assembly. This occurrence is displayed as
a line in the BOM.
Each assembly revision has its own BOMView Revision (BVR). If you expand
an Item Revision in Teamcenter Engineering, you will see the BOMView
Revision, which is the object in which the occurrence information is stored.
The BOMView Revision for the 2920_xx/000 Frame Assembly is shown
below.
Create Part Files

This section describes what happens in the Teamcenter Engineering database
when you create a new part file in NX when running in NX Manager mode.
Note that the database is only affected when you save a new part file. If you
create a new part in your NX session, and then terminate the session without
saving it, no new Items, revisions or datasets are created in the database.
Brand New Part

When you create a brand new part (that is, a new master part file, with a
new part number and a new part revision) in NX and save it, an Item, its
first Item Revision and a UGMASTER Dataset are created in the Teamcenter
Engineering database. The dataset is referenced as a specification of the
new Item Revision.
The following information concerning Item and dataset creation applies
whenever a new Item Revision is created from NX; such as in the FileNew
and FileSaveAs operations.
The table below shows the values which NX sets in the Teamcenter
Engineering fields that you would usually fill when you create an Item and a
dataset from Teamcenter Engineering.
Field Value set by NX

Item ID Part Number specified by user in the NX Manager
Part Selection dialog.
Item Name Part Name specified in the Edit Database Attributes
dialog.
Revision ID Revision specified in the Part Selection dialog.
Item description Part Description specified in the Edit Database
Attributes dialog.

New Part Revision

When you create a new revision of an existing part in NX and save it, a new
Item Revision and a new UGMASTER Dataset are created in the Teamcenter
The values which NX Manager sets in the Teamcenter Engineering fields
that you would usually fill when you create an Item and a dataset from
Teamcenter Engineering are shown in the table on the previous page. Note
that the dataset is referenced as a specification of the new Item Revision.
The values which the system sets used for necessary fields are the same as
given above for new parts.
New Non-master Part File

When you create a new non-master part file for an existing part revision in
NX, a new UGPART Dataset or UGALTREP Dataset is created in Teamcenter
Engineering. The name given to the new UGPART dataset is the name which
you specify in the NX Manager Part Selection dialog.
You choose a part file type with Part File Type in the Part Selection dialog.
If the file type is specification, the new dataset is referenced as a specification
in the Item Revision. Similarly, if you specify a part file type of manifestation,
the dataset is referenced as a manifestation in the Item Revision.
The following table shows which dataset and relationship types correspond to
each of the part file types.
Part File Type Dataset Type Relationship Type

master UGMASTER specification
specification UGPART specification
manifestation UGPART manifestation
altrep UGALTREP altrep
Storage of Associated Files

Associated (dependent) files are files which are related to a part file, but are
separate from it. For example, you may have produced a shaded image of
your part in NX. The shaded image is stored as a file with the extension .tif.
This file is separate from the part file, but is related to it (because it is an
image of your part).
Associated files are stored in a dataset with the NX part file in Teamcenter
Engineering. They are stored as named references in the dataset. The named
references specify the different types of file you can store with the part file.
When you open a part file from NX with file export enabled, NX Manager
creates a directory for the part and exports the associated files governed by
the current NX Manager role to that directory. The NX part files with the
.prt suffix are not exported.
When you save or close the part file, any new or changed files in the directory
are saved in the Teamcenter Engineering dataset corresponding to the NX
part file.

Access Control
NX Manager locks the geometry for a NX part file as soon as you start to
modify it. If the part is a master part file (and an assembly), the structure
also becomes locked. The locking ensures that no other user can modify the
part file at the same time.
When you create a new non-master part file in NX, you must have write
access to the Item Revision, otherwise the reference to the newly created
dataset cannot be added. Similarly, when you create a new part and place it
into a folder, you must have write access to the target folder, otherwise the
reference from the folder to the new part cannot be created.
Access and Locking Geometry

When checking your access rights for a NX part file, NX Manager looks at
the protections on the corresponding dataset in Teamcenter Engineering. If
you have write access to the dataset, then you are granted write access to
the part file in NX.
When NX Manager locks the geometry for a part file in your NX session, what
is actually happening in the database is that the dataset corresponding to
the part file is being checked out. When NX Manager unlocks the part files
geometry, the Teamcenter Engineering dataset is checked back in.
Locking Structure
When NX Manager locks the structure for a part file, the corresponding BOM
View Revision is locked in the database. The structure locking is carried out
in the same way that Teamcenter Engineering PSE locks structure, so that
PSE inter-session locking on product structure can be maintained.
UGMASTER / UGPART Behavior

We recommend that you always use UGMASTER datasets with NX Manager
for master part files; especially for parts that are used as components in an
assembly. If you need to use UGPART datasets instead of (or in addition
to) UGMASTER datasets, you need to be aware of the following important
differences in the way the datasets are used in Teamcenter Engineering.
Master File
A UGMASTER dataset should be created only in the context of an Item
Revision.
One and only one UGMASTER dataset should be referenced as a

specification of a particular Item Revision.
Non-Master File(s)
More than one UGPART dataset may be referenced as a specification of

an Item Revision.
Loading from NX Manager

When NX Manager loads a specific Item Revision as a component of
an assembly, it looks first for a UGMASTER dataset referenced by the
revision as a specification. If it cannot find one, it loads the first UGPART
dataset that it finds in the list of objects referenced as specifications.
NX Manager does not provide a means of loading a specific version of a

dataset as a component, nor does it provide a means of opening it from
NX. The latest configured version of a dataset is always used

... so that you configure the NX/Teamcenter

Engineering Integration for your site

Seed Part Setup
Mapping Teamcenter Engineering Attributes to NX Part Attributes
Process Templates for NX Related Data
Setting Environment and Preferences
Seed Part Setup

When a user creates a new part in NX Manager, they must select a seed part
to be used as the basis for their part. A seed part may be either:
Generic (available for use as the basis for a part file of any type), or
Specific to a particular type of part file. For example, a seed part that
may be used as the basis for part files of type specification only.
As a Site Administrator, you can set up any number of seed parts to be

available for users.
Initial seed part setup is generally established during
the initial database installation by execution of the
IMAN_ROOT/bin/ugmgr_add_note_types utility.
How Seed Parts are Stored in Teamcenter Engineering

In Teamcenter Engineering, a folder named NX seed parts is used to contain
all seed part information. The dialog below shows the default structure
of the NX seed parts folder.
After installation, the NX seed parts folder contains the following:

Two Items (parts), named Metric and Inch.
A folder called manifestation.
A folder called specification, containing two Items named Metric_dwg

and Inch_dwg.
A folder called master.

The two Items named Inch and Metric are generic seed parts. A generic
seed part is a part that can be used as the basis for any type of part file. If
you create more generic seed parts (in addition to the two mentioned), they
should be placed directly in the NX seed parts folder.
NX Manager displays the seed part Name, not the Part ID.
The manifestation folder contains seed parts that can be used as the
basis for non-master part files of type manifestation only. Initially, the
manifestation folder is empty. You should place any seed parts used to create
new manifestation part files (only) in this folder.
The specification folder contains seed parts that can be used to create new
part files of type specification only. The specification folder initially stores
two parts, Inch_dwg and Metric_dwg. These two seed parts can be used to
create new drawings with imperial or metric units respectively. You should
place any seed parts used to create new part files of type specification (only)
in this folder.
The master folder contains seed parts that can be used as the basis for part
files of type master only. Initially, the master folder is empty. You should
place any seed parts used to create new master part files (only) in this folder.
NX Manager expects seed parts to be contained in the folders
named NX seed parts, master, specification, and manifestation
only. If seed parts are created in other folders within the NX seed
parts folder, they are ignored.
Seed Part Example

The NX Manager seed part selection display can show multiple parts with
one heading. This would be useful when two groups need different drawing
seed parts, but would both like to select the name Drawing. This setup is
easily done with two parts with different Part IDs and with the same Part
Name. Each part would only be read by the appropriate group due to the
parts protections.
Seed Part Preferences
Display Seed Part Dialog
This preference specifies whether the NX Manager Select Seed Part dialog is
displayed when a part which has been created in Teamcenter Engineering is
opened in NX for the first time. If set to yes, or always, the dialog is always
displayed. When the value is no, or never, the dialog is never displayed, and
the default seed specified by UGMGR_SeedPartName is used as the basis for
new part files. If set to top, the dialog is displayed only for the top part in an
assembly; for component parts, the dialog is not displayed, and the default
seed specified by UGMGR_SeedPartName is used instead.
Preference(s): UGMGR_DisplaySeedDialog
File(s): ug_english.def, ug_metric.def
Possible values: yes, always, no, never, top
Default: yes
Default Seed Part

This preference specifies the default seed part which will be used as the
basis for new part files created in NX. The part name (not the part number)
of the seed part should be specified. Note that you must have read access
to the seed part.
Preference(s): UGMGR_SeedPartName
File(s): ug_english.def, ug_metric.def
Possible values: Metric, Inch, Metric_dwg, Inch_dwg, or
any seed part which has been defined
and you have access to
Default: Inch

Activity: Organize the NX Seed Parts folder
In this activity, you will organize the NX seed parts folder.
Step 1: Put a reference to the NX seed parts folder in your Home Folder.
Choose the Search icon.

This brings up the Search window.
Choose General... from the query pull-down list.
Choose Clear this query form.
Enter Unigraphics seed parts in the Name field.
Choose Execute this query.

The Unigraphics seed parts folder appears in the General Tab.
Copy the Unigraphics seed parts folder to your Home folder.
Choose again, to close the Search window.
Step 2: Create a folder to keep unused seed parts organized within the
Unigraphics seed parts folder.
Select the Unigraphics seed parts folder.
Choose FileNewFolder...
Enter the Name: not used
Choose OK.
The folder is created.
You have write privileges to the Unigraphics seed parts

folder since you are in the dba group.
Step 3: Organize the Unigraphics seed parts folder.

Expand the Unigraphics seed parts folder.
Cut and Paste the Metric Item into the not used folder.
Expand the specification folder.
Cut and Paste the Metric_dwg Item into the not used folder.
The Unigraphics seed parts folder should now be organized
like the following.

Mapping TcEng Attributes to NX Part Attributes

Using mapping definition files, NX Part attributes can be stored in the
Teamcenter Engineering database and displayed and modified both in NX
and in Teamcenter Engineering.
Database attributes are not limited to properties of the datasets
corresponding to NX Part file, instead they can be any of the following, as
specified in the mapping definition file:
Properties of other Teamcenter Engineering objects. The mapping
definition specifies how to find the object beginning with the original
dataset or related Item or Item Revision and traversing a path from
one Teamcenter Engineering object to another. The final step in the
path produces a value, which can be an integer, a double, a string, a
date, or an object. Each step may be a property, named reference,
generic relationship, job, or signoff. You cannot define the attribute to
be a property of an arbitrary Teamcenter Engineering object. The object
must be accessible from the original dataset, Item, or Item Revision
by a series of steps.
Teamcenter Engineering Preference Values. The mapping definition

indicates the scope and name of the preference.
Constants. The mapping definition indicates the constant value. A

copyright notice is an example of a constant.
The set of mappings that apply to a particular dataset can be dependent on

the type of dataset and/or the type of the related Item. (The NX Manager
application assumes that the dataset is attached to an Item Revision for
which there is always a related Item.)
The mappings are stored permanently in the Teamcenter Engineering
database and are available when NX is running in NX Manager mode. These
mappings are not available in native NX sessions.
Mappings can be either real or test. Real mappings are those that the
user can view within the application. Test mappings are used to verify the
accuracy of the mapping file before implementation.
Each mapping definition has a title and description that are used when
displaying the attribute value in NX. There are also optional qualifiers that
affect the behavior of the mapping, such as which application has write
control and whether a default value is created for a NX Part file attribute if
none exists in Teamcenter Engineering.
Default Mappings
The default mappings between Teamcenter Engineering and NX Part
attributes are described in the following table:
UG Part Attribute Description TcEng Attribute

DB_PART_NO Part Number Item ID
DB_PART_REV Part Revision Item Revision ID
DB_PART_TYPE Part Type Item Type
DB_PART_NAME Part Name Item Name
DB_PART_DESC Part Description Item Description
DB_UNITS Part Unit of Measure Item Unit of Measure
You cannot delete the default attribute mappings.

Extending Attribute Mappings

Mappings of NX Part attributes to Teamcenter Engineering attributes
are stored in the Teamcenter Engineering database and are extended by
importing a modified mapping definition file into the database. The existing
file is overwritten each time a new file is imported.
NOTE: It is recommended that this task be performed when all users are
logged out of NX Manager. If this is not possible, any users who were logged
into NX Manager at the time the new mapping file was imported must reload
the database attributes using the NX Manager Reload command.
Use the following steps to extend the attribute mapping:
Export the existing mapping to a text file, using the export_attr_mappings
utility.
Edit the file to add, remove, or modify mappings.
Import the modified mapping file as test mappings, using the

import_attr_mappings utility. This allows you to verify the attribute
mappings without affecting the existing real mapping definitions.
Verify the test mappings by setting the

IMAN_USE_TEST_ATTR_MAPPINGS preference to any
non-zero value (either as an environment variable or in the .iman_env
file). This will cause Teamcenter Engineering to pick up the test
mappings rather than the real mappings.
When finished testing the mappings, import the modified mapping file as
real mappings using the import_attr_mappings utility.
Attribute Mapping Syntax

There are four syntax forms for the specification of Teamcenter Engineering
attribute mappings:
<Part_Attr_Name> : <Path_Step>(s).<IMAN_Property>/<Qualifier>(s)
<Part_Attr_Name> : <Abbreviated_Path>.<IMAN_Property>/<Qualifier>(s)
<Part_Attr_Name> : CONST (value)/<Qualifier>(s)
<Part_Attr_Name> : PREF ( [<scope> : ] <value> )/<Qualifier>(s)
<Part_Attr_Name> is the name of a NX part attribute. Format must be all

uppercase without spaces.
<Path_Step>(s) is one or more of the following separated with a (.) character
(i.e., Item.GRM):
NR ( <named_reference_type> [, <form_type> ]) - A named reference
of the current object. The particular reference is identified by the type of
the referenced object (not the name of the reference).
ItemRevision - The Item Revision object which owns the current object;
that is, the Item Revision to which the current object is associated via a
GRM link.
Item - The Item object corresponding to the current owning Item Revision
object.
GRM( <relation_type> [, <object_type> ]) - A GRM relation whose

type is <relation_type> and whose primary object is the current object
and whose secondary object gives the next object. In the case that more
than one relation of the given type is associated with the current object,
the optional second argument <object_type> is used to identify the type
of the referenced object.
Job - The job in which the current object is included; or, if there is no
current job, then the most recent job that the object was in (assuming the
job has not been deleted).
SIGNOFF( [<level> , ] <role> ) - A completed signoff whose group

members roles have the name <role>. If the same role has been specified
for assignees in more than one level of the process definition, the optional
argument <level> further identifies a specific level.

<IMAN_Property> - The name of the Teamcenter Engineering property to

be synchronized with the NX part attribute.
<Qualifier> - Specifies various controls or conditions for the particular
attribute synchronization and can be any one of the following:
/description=<note> - NX will display the content of <note>, which is
a character string enclosed in single or double quotes, to show the user
what significance the attribute has.
/write_once - NX Manager can write a value for the attribute to

Teamcenter Engineering if the attribute does not already have a value.
/master=cad - Only the CAD application, i.e. NX, is allowed to modify

the attribute value.
/master=iman - Only Teamcenter Engineering is allowed to modify

the value for the attribute.
/master=both - Both NX Manager and Teamcenter Engineering can

modify the attribute value.
/master=none - Neither can modify the attribute value.
/freezable - This directs NX to ignore the Teamcenter Engineering

attribute value, as stored in the Teamcenter Engineering database, but to
use the value stored in the part file if the related Teamcenter Engineering
object is frozen.
<Abbreviated_Path> is one of the following:

IM - abbreviation for Item.GRM(IMAN_master_form, Item Master)
IRM - abbreviation for ItemRevision.GRM(IMAN_master_form,

ItemRevision Master)
CONST - Represents a constant value specification which the NX part

attribute will assume. Its specification is: CONST ( <value> ) where
<value> is a character string enclosed in single or double quotes.
PREF ( [ <scope> : ] <value> ) produces the <value> preference value,
optionally within the given preference scope. The scope can be one of the
following: ENV, USER, ROLE, GROUP, or SITE.
Comments and Contexts Symbols

Comments are introduced by the (#) symbol. Anything on the line after this
symbol is not part of the mapping definition and is ignored.
Contexts begin with the left bracket ({) symbol followed by a context specifier
which states the context for the following mappings, either Dataset type or
Item type context, as follows:
Dataset type = <dataset-type>
Item type = <item-type>
Contexts end with the right bracket (}) symbol.

Contexts can be nested. For example, you can define an Item-type-based
context within a dataset-type-based context. The mappings defined within
this nested context are then only applied to datasets of the specified type that
are associated with Items of the specified type.
Example:
Top of File...
Mappings located here apply to any Dataset type in context of any Item type
{Dataset type=UGMASTER
Mappings located here apply only to UGMASTER Dataset types in context of

any Item type.
{Item Type=Item
Mappings located here apply to only UGMASTER Dataset types only in

context of Item Item types (For example, not Document Item types)
}
... Bottom of file

Activity: Teamcenter Engineering/NX Attribute Mapping

In this activity, you will modify the Teamcenter Engineering / NX attribute
mapping definitions.
Step 2: Verify bi-directional synchronization mode is set.

Ask your instructor for the location of UGII_ROOT_DIR.
Open the ugii_env.dat (.ugii_env on Unix) file in

UGII_ROOT_DIR in a text editor.
Search the file for the UGII_UGMGR_ATTR_SYNC setting.
Make sure this variable is set to NEW.
Step 3: Export current mappings to a text file.

Open a command window with the TcEng environment set.
Use the cd command to navigate to aa_class.
Type: cd ug_attr_sync

export_attr_mappings -u=infodba -p=infodba -g=dba
-file=current_mappings.txt
Open the new current_mappings.txt file in a text editor.
Review the UGMASTER and UGPART dataset sections.
Step 4: Review a modified mappings definition file.

To save time, a modified version of the current_mappings.txt
file has been prepared for you. In this step, you will open the
new_mappings.txt.v9 file and review the additional mappings
defined in this file.
Open the new_mappings.txt.v9 file (in the

.../aa_class/ug_attr_sync directory) in a text editor.
Compare the file to the current_mappings.txt file and observe

additions in the UGMASTER and UGPART sections.
Close the text editor application for both files.
Step 5: Import new mappings as a test mappings.

Return to the command window with TcEng environment set.
Verify you are still in the ug_attr_sync directory.

import_attr_mappings -u=infodba -p=infodba -g=dba
-file=new_mappings.txt.v9 -test
Step 6: Set environment for test mapping usage.

Add the following setting to the bottom of the
IMAN_DATA/upfiles/<your user name>.iman_env file:
IMAN_USE_TEST_ATTR_MAPPINGS=
Y
Save the file.
Step 7: Start NX and test the UGMASTER mappings.

Log in to the Engineering/My Navigator application and make
sure nothing is selected (use CTRL and mouse to unselect).
Choose the Open in NX icon to start NX.
In NX, choose the New icon to create a new file.
Use the following parameters:
Part Type: Item

Part Number: 13690
Part Revision: 000
Part File Type: master
Part File Name: <unset>
Seed Part: Inch
Choose OK.

The Edit Database Attributes dialog appears. Notice the 7

new entries in the Write Enabled section. These are 7 of the 9
new mappings defined by importing the new_mappings.txt file
(The other 2 mappings apply only for UGPART type datasets).
Press Enter to accept the default values for Part Name and
Part Description.
Set the value of each of the remaining attributes to from ug.
When finished, choose OK.
Save (FileSave), then Close (FileCloseAll Parts) the part

file (Do not exit NX).
Step 8: Observe UGMASTER partfile attribute data stored in TcEng.
In My Navigator, expand the 13690 Item and ItemRevision

(may have to Refresh the Home folder).
View the ItemRevision Master form by double-clicking it or by

selecting it with the Viewer tab raised.
You should see data provided for each attribute as provided

from the NX interface.
Change all attribute values on the form to from tc.
Choose OK to save the edits.
Step 9: Verify UGMASTER update from TcEng edit.

From NX, open the 13690/000 UGMASTER part file.
Choose FormatDatabase Attributes....
Choose the Assign button on the Database Attributes dialog.

Observe the values for the attributes in the Write Enabled

section of the dialog. The values should appear as the values
you applied to the ItemRevision Master form in the Teamcenter
Engineering interface.
Using the Edit Database Attributes dialog, change the value

for each attribute value to from ug again.
Choose OK on the Edit Database Attributes dialog.
Choose OK on the Database Attributes dialog.
Save, then Close the part file (Do not exit NX).
Step 10: Verify Teamcenter Engineering update from UGMASTER edit.

In Teamcenter Engineering, select the ItemRevision Master
form and choose ViewRefresh.
Open the ItemRevision Master form again to review the

attributes that were changed.
If the ItemRevision Master form is selected or the form

dialog is still open from a previous step, you will have to
reopen the dialog or select another object and re-select
the ItemRevision Master form to see the current values
for the form fields.
Step 11: Test the UGPART mappings.
From NX, choose the New icon to create a new file.
Use the following parameters:
Part Type: Item

Part Number: 13690
Part Revision: 000
Part File Type: specification
Part File Name: DWG13690
Seed Part: Inch
Choose OK.
Choose OK on the Add Master to: dialog.
Choose FormatDatabase Attributes...
Choose Assign.
The following message appears.
The attributes mapped to the UGPART dataset type were

defined using the /master=iman qualifier, and therefore
cannot obtain values from the NX interface.
Choose OK on the No Write Enabled Attributes dialog.
Save, then Close the part file (Do not exit NX).

From My Navigator, highlight the 13690/000 ItemRevision.
The ItemRevision, UGMASTER and UGPART dataset should

all have Status flags.
From NX, open the DWG13690 UGPART partfile.
Choose FormatDatabase Attributes...
Choose the List button on the Database Attributes dialog.

Observe the values for the attributes in the Read Only section
of the dialog. The DATE_RELEASED and RELEASE_STATUS
attributes should have values.
Close the Information window and exit NX.
Step 12: Import new mappings as real mappings.

Environment set.
Verify you are in the .../aa_class/ug_attr_sync directory.

import_attr_mappings -u=infodba -p=infodba -g=dba
-file=new_mappings.txt.v9
This is the same command you executed earlier in

the lesson, only this time the -test option is not
being used.
Step 13: Unset environment for test mapping usage.

Remove the following setting from the bottom of the
IMAN_DATA/upfiles/<your_userid>.iman_env file.
IMAN_USE_TEST_ATTR_MAPPINGS=
Y
Save the IMAN_DATA/upfiles/<your_userid>.iman_env file.

Process Templates for NX Related Data

Special workflow handlers are provided with Teamcenter Engineering for use
in process models designed for UG data.
EPM-attach-item-revision-targets
When releasing Item Revisions that contain a UGMASTER as a Specification
relation, the UGMASTER should be released at the same time.
To accommodate this requirement, Teamcenter Engineering provides the
canned handler EPM-attach-item-revision-targets in the process templates.
This handler attaches all objects with specification relation to the Item
Revision as target objects.
EPM-attach-related-objects
This handler attaches the specified related objects of the target objects as
target/reference attachments to the process. This handler goes through all
the target objects, finds the secondary objects with the specified relation and
type (if specified) and adds them as target/reference attachments.
This handler is more generic than EPM-attach-item-revision-targets
and can be used to attach objects with customized relations, also.
EPM-generate-image
Another useful handler is EPM-generate-image. The EPM-generate-image
handler generates NX part images for display by Teamcenter Engineering
Web. This handler calls an external NX User Function program (no license
required) to accomplish this. The images are stored as named references
to the UGMASTER dataset; image types and sizes are specified in the
.iman_env preference file.
EPM-tessellation-handler
This handler generates .jt files for viewing with Teamcenter Vis products.
The handler is intended to be added to the Item Revision and/or UGMASTER
review process(es).
When an Item Revision or UGMASTER undergoes a review process, this
handler retrieves the UG Part files belonging to the UGMASTER dataset and
creates Vis files (.jt files).
EPM-generate-ugcgm-drawing
This handler generates Drawing sheet datasets (CGM images) of UG
drawings.
This handler must be added to a process template as an action handler.
The process template containing this action handler should be initiated by
selecting the UGPART/UGMASTER dataset.
This handler calls an external NX User Function program to generate the
CGM images of the drawing sheets in the part. The generated images are
stored as named references to the UGMASTER dataset.

Setting NX Manager Preferences

Preference Settings for NX Manager
Preference Settings to Consider for NX Manager
Environment Variables Settings for NX Manager
NX Customer Defaults Files for NX Manager
Preference Settings for NX Manager
Locating the NX Manager Preferences
For review, the following preference hierarchy is followed:

1. A preference set via shell commands.
2. User:
a) Directory pointed to by IMAN_USER_PFILE
b) Current working directory
Between these two, IMAN_USER_PFILE has precedence.
3. Role: IMAN_DATA/rpfiles/<role>.iman_env
4. Group: IMAN_DATA/gpfiles/<group>.iman_env
5. UGMAN Site: IMAN_DATA/.iman_ugman_env
6. Site: IMAN_DATA/.iman_env
Summary of the Preference Hierarchy for NX Manager
Setting Files
1 User In Shell n/a
2a User IMAN_USER_PFILE IMAN_DATA/upfiles/
<userid>.iman_env the directory
2b User IMAN startup directory where Teamcenter Engineering
starts
3 Role IMAN_ROLE_PFILE IMAN_DATA/rpfiles/
<role>.iman_env
4 Group IMAN_GROUP_PFILE IMAN_DATA/gpfiles/
<group>.iman_env
5 UGMan n/a IMAN_DATA/.iman_ugman_env
6 Site n/a IMAN_DATA/.iman_env

Preference Settings to Consider for NX Manager

While there are many preferences available to customize NX Manager,
the following were reviewed and considered for the discussion during this
training course.
NX Manager Default View Type

The IMAN_UG_View_Type preference sets the BOM view type that NX
Manager will use to read and write product structure information. This
preference accepts a single string as a value; the string must be a valid
Teamcenter Engineering BOM view type. It may be placed in the user, group
or site preference file.
Preference(s): IMAN_UG_View_Type
File(s): IMAN_DATA/.iman_env (SITE preferences file)
Default: view (Set to engineering in an earlier
lesson.)
NX Manager will error with File-Save operations if the

IMAN_UG_View_Type is not a valid Teamcenter Engineering
BOMView Type.
Default UGMASTER Dataset Separator Character

The IMAN_ugmaster_name_separator preference allows you to control
UGMASTER dataset name created by NX Manager. The dataset name should
follow the same format to enable better searches.
To make the UGMASTER dataset name format be consistent, set
IMAN_ugmaster_name_separator preference to be the same as
FLColumnCatIVFSeparatorPref which is "/" by default.
If you change FLColumnCatIVFSeparatorPref, also update the
IMAN_ugmaster_name_separator preference.
Preference(s): IMAN_ugmaster_name_separator
File(s): IMAN_DATA/.iman_env (SITE preferences file)
Default: not set
Environment Variable Settings for NX Manager
Locating the NX Defaults File
The default NX Manager environment variables are read from the file
.ugii_env. The default .ugii_env file is located in the directory set by
UGII_ROOT_DIR. A .ugii_env file could also be used as a users preference
file, commonly in the users home directory.
The following variables must be set in the users environment or
with a startup script. These are set in the class with the env-sitea
script.
UGII_BASE_DIR
UGII_ROOT_DIR
UGII_LICENSE_FILE
Interpreting the File Specifications
The configuration variable UGII_OPTION in the .ugii_env file sets how

to interpret and convert file specifications. This preference accepts one of
the following values:
NONE File specifications are interpreted without converting case (i.e.,
as-is).
LOWER Converts entire file specification (directory and file name) to
all lower case.
Default = LOWER.
Other settings available: UPPER, HINAME, LONAME
We recommend lower case (UGII_OPTION=LOWER) for NX Manager part
files and volume names when the volume is going to be used for NX Manager
part files. Additionally we recommend that Teamcenter Engineering volumes
and group names be lower case.
This preference can affect IMANFS if these recommendations are
not followed.

NX Customer Default Files for NX Manager

NX Manager enables you to use NX and Teamcenter Engineering together.
For this reason, some NX Manager customer defaults are located in the
NX customer defaults file.
Locating the NX Defaults File

The standard NX customer defaults file is named ug_english.def or
ug_metric.def.
The location of the NX customer defaults file is specified by the
UGII_DEFAULTS_FILE variable inside the .ugii_env file.
Possible Settings
The seed part settings UGMGR_DisplaySeedDialog and
UGMGR_SeedPartName were discussed earlier.
By Pass Request to Position Components

The UGMGR_AutoPositionComps customer default allows you to bypass
being prompted in NX to position each component which you have added
in PSE.
UGMGR_AutoPositionComps has two possible values:
on and off. By default, this customer default is set to off, which forces a
request to position every new component which you have added in PSE.
When it is set to on, the UGMGR_AutoPositionComps default causes each
component which has been added to the assembly in PSE to be automatically
placed at the origin in NX.
Preference(s): UGMGR_AutoPositionComps
File(s): ug_english.def and ug_metric.def
Default: OFF
Activity: Modify NX Manager Preferences
In this activity, you will set the NX Manager preferences.

Step 1: Verify the following site preferences in the IMAN_DATA/.iman_env
file.
Locate the IMAN_DATA/.iman_env file
Open the .iman_env file in a text editor
Find the setting for IMAN_UG_View_Type
Notice the current setting of engineering, which was set

earlier in the course.
Step 2: Add the following site preference to the IMAN_DATA/.iman_env

file.
Add the following at the end of the .iman_env file.
IMAN_ugmaster_name_separator=
/
The preference must be spelled correctly, otherwise

Teamcenter Engineering will not use the preference.

Step 3: Save the file and exit the editor application.

Save the .iman_env file.
Exit the editor application.
You the NX Manager preferences are set for your database.
Summary
In this lesson you:
Setup Seed Part Files for NX
Defined NX-to-TcEng; Attribute Mappings
Set NX Manager Preferences and Options

Lesson
18 NX Manager Import and

Data Release
Purpose
The purpose of this lesson is to import native Unigraphics files and other
related data into Teamcenter Engineering.
Objectives
Import Unigraphics Data into the Database
Release Imported Unigraphics Data

NX Manager Import and Data Release
Import Unigraphics Data into the Database

... so that you can import existing part
files into the Teamcenter Engineering database.

Introduction to Unigraphics Data Import
Prepare to Import Unigraphics Data
Overview of the ug_import capabilities
Understanding Various NX Manager Import Scenarios
Command Line Keywords With ug_import
Import Component Parts or Assembly Parts without a Map File
Import an Assembly using a Map File and Search File
The Import Log File
Import a Non-Master Drawing File
Import Files Associated to a Part File
Import Files Associated to the DWG (Non-Master) Part File
Import Files Using a Full Map File
Importing Non-Unigraphics Files into an Item
Introduction to Unigraphics Data Import

In standard NX, your parts are stored in operating system directories.NX
Manager, however, does not search for your parts in operating system
directories. Instead, it retrieves part files from the Teamcenter Engineering
database. Therefore, in order for NX Manager to locate your parts, they
need to exist in the Teamcenter Engineering database. The ug_import
utility is used to make copies of your standard NX assemblies in Teamcenter
Engineering.
The ug_import utility is commonly used to import NX part files and
assemblies. The result is the creation of Items and the included UGMASTER
and/or UGPART datasets which have the file Named References for the
part file data.
You should use the ug_import utility whenever you are importing NX data.
The ug_import utility does the following:
Imports an entire part tree when the top level assembly Item is specified.
Creates an Item structure for data plus a dataset.
Imports NX assembly and master model data.
A mapping file is typically used to provide settings for the many options.
Can use a mapping file suited for NX parts.
Can use a search path file to locate NX parts.

Parts and Assemblies to be Imported

For your reference these parts and assemblies will be discussed and imported
in this lesson.
Other files (e.g. seed files) will also be imported and will be explained
appropriately during the lesson discussion.
Wheel Assembly
The wheel assembly below contains the components as listed in the Assembly
Navigator.
Frame Assembly
The frame assembly below contains the components as listed in the Assembly
Navigator.

Prepare to Import Unigraphics Data

Preparations are usually required before using the ug_import utility to have
a successful import. The next few pages will use various native NX files
to show the necessary preparation.
The first and most important step is to understand what files there are to be
imported. Various types are listed:
Components
Assemblies
Master associated files (e.g. TIF, HTML files)
Non-master part files (Drawing and NC ".prt" files)
Non-master associated files (e.g. NC, CLSF, PTP files)
Non-NX files (e.g. DOD requirements, part testing results)
Product (part) attributes
Because ug_import works slightly different for these file types, you must
ask these questions:
What setup requirements are there?
What mapping files must be written?
How to use ug_import?
Consider the example directory below of native NX files that must be

imported.
1250_axle_000.tif 1600_wheel_assy_000.prt
1250_axle_000.prt 1700_spacer_000.prt
1250_axle_000_dwg.prt border_b_seed.prt
1250_000_dwg.cgm border_c_seed.prt
1300_bearing_000.prt m243_heat_treat.txt
1400_wheel_000.prt
The 1400_wheel_000.prt is in a directory at a different location.

How is the import set up, and then how is the import accomplished?
Recognize the Unigraphics Files and Attribute Data
The directory below must be divided into the categories shown in order to
properly use ug_import and its arguments.
Components and Assemblies

1600_wheel_assy_000.prt
1700_spacer_000.prt
1250_axle_000.prt border_b_seed.prt
border_c_seed.prt
1300_bearing_000.prt
1400_wheel_000.prt
The ug_import utility essentially works the same for component and assembly
parts, but the utility performs a database login each time it is executed. The
login can take a fair amount of time. Therefore, preferably you would like to
know the assembly parts and execute ug_import on the top level assemblies.
The NX utility ugpc can be run on the part (.prt) files
in the directory to get a output listing of the assemblies
and their components, as shown in the following example.
1600_wheel_assy_000.prt
./1250_axle_000.prt
./1700_spacer_000.prt
./1300_bearing_000.prt
./1400_wheel_000.prt
For example, you could simply use:

ug_import -part=border_b_seed.prt
ug_import -part=border_c_seed.prt
ug_import -part=1600_wheel_assy_000.prt
As you will see the components and assembly master files can be imported
with one command line ug_import execution and a mapping file to convert all
files to the proper database Part ID and Revision.

Master Associated Files (e.g. files like TIF, HTML)

1250_axle_000.tif
Next begin to recognize the files associated to the components and assemblies.
These files would be like TIF or HTML files.
These files can be placed in an individual directory and imported with one
extra argument on the command line or one extra keyword in a mapping file.
ug_import -part=1250_axle_000.prt -id=1250 -rev=000

-assoc_files=yes
where the 1250_axle_000.tif file would be in a sub-directory named 1250 to

correspond to the part id (-id=1250).
Non-Master Part Files (drawing and nc ".prt" files)

1250_axle_000_dwg.prt
Next recognize the non-master part files that work with the component and
assemblies. These files would be drawings and manufacturing part (.prt) files.
Non-master part files can reside in the same directory as their master part
files, but must be imported with their own ug_import execution.
For these part files you must specify the relation to the master part (e.g.
specification, manifestation, etc.) and the name of the UGPART dataset
created with the import.
ug_import -part=1250_axle_000_dwg.prt -id=1250 -rev=000

-name=1250_DWG -type=manifestation
Non-Master Associated Files

1250_axle_000_dwg.cgm
Next begin to recognize the files associated to the non-master part files (e.g.,
CLSF, PTP files). These files would be like CGM files that are associated to a
drawing or the common CAM related files for manufacturing operations.
Like before, these files can be placed in an individual directory and imported
with one extra argument on the command line or one extra keyword in
a mapping file.
ug_import -part=1250_axle_000_dwg.cgm -id=1250 -rev=000

-name=1250_DWG -type=manifestation -assoc_files=yes
where the 1250_000_dwg.cgm file would be in a sub-directory named

1250_m_1250_dwg to correspond to the part id (-id=1250) + m
(-type=manifestation) + 1250_dwg (-name=1250_DWG). Each of these
portions are separated with an underscore ( _ ), giving the full sub-directory
1250_m_1250_dwg.
Non-NX Files
Examples of Non-Unigraphics Files are DOD requirements and part testing

results.
m243_heat_treat.txt
Finally importing the non-NX files can easily be done by importing the files
into the Item or Item Revision with the import_file utility. This utility was
used earlier in the course.

Product and Part Attributes

Product or part attributes may exist in the part file or inside another
application (e.g. MRP). Importing NX part attributes is done automatically
with the ug_import utility, after a preference is setup with the list of attribute
names. Importing attributes from other applications usually requires
exporting the attributes to a neutral file and then using a custom TcEng
program to import the attributes into the database.
Example Import Directories and Files

Original directory and files.
1250_axle_000.tif 1600_wheel_assy_000.prt
1250_000_dwg.cgm border_c_seed.prt
1400_wheel_000.prt
Rearranged directories and files.

1250/ 1600_wheel_assy_000.prt
1250_m_1250_dwg/ border_c_seed.prt
1600_search.txt 1600_wheel_assy.map
1400_wheel_000.prt
As you can see the master part files for the 1600_wheel_assy_000.prt and
the seed parts still remain in their original directories. The non-master part
file (1250_axle_000_dwg.prt) and the non-NX file (m243_heat_treat.txt)
also remain in the original directory.
To convert the files names to database Part IDs and Revisions, the
1600_wheel_assy.map file has been added and will be used during the import.
Also the 1600_search.txt file has been added to locate the 1400_wheel_000.prt.
Two sub-directories have been created for the associated files. The
sub-directory contents are shown below.
1250/
1250_axle_000.tif
1250_axle_000_dwg/
1250_000_dwg.cgm

Overview of the ug_import Capabilities
Basic Usage of ug_import
The ug_import utility takes your standard NX assembly and recreates both
the parts and the structure in Teamcenter Engineering. For each NX part,
ug_import creates items, item revisions and datasets as necessary.
The simplest import is carried out by specifying the command:
This imports an assembly named 1600_wheel_assy_000.prt and all of

its component parts from the current directory into the Teamcenter
Engineering database. If the assembly is located outside the current
directory, you need to specify the full pathname of the assembly, for example:
ug_import -part=/users/daytr/1600_wheel_assy_000.prt
The default behavior of ug_import is to create all the parts in the NX

assembly as master parts of type "Item" in the Teamcenter Engineering
database. The parts are named as follows:
ug_import removes the directory prefix and the .prt extension from the
standard NX filename to form the Item ID.
the item revision is set to "A".
The native filename /users/daytr/parts/1600_wheel_assy_000.prt becomes

1600_wheel_assy_000/A in TcEng.
The ug_import utility allows you to fine-tune the creation of the assembly
and each of its components by specifying extra command line keywords and
through the use of mapping files.
Introduction to Using Mapping Files
A mapping file can set the individual components without affecting other
components in the assembly.
Mapping file syntax

[Defaults]
import_folder = "Import Project"
db_part_no=$STRIPPED_LEAFNAME
existing_data=$USE_EXISTING
[CA_36245.prt]
db_part_no="CA_36245_000"
db_part_rev="000"
assoc_files=yes
assoc_files_dir="CA_36245_files"
[ENG_83475.prt]
existing_data=$OVERWRITE_EXISTING
db_part_no="ENG_83475_000"
db_part_rev="000"
assoc_files=no

Introduction to Using Command Line Keywords
Depending on the command line keyword the entire assembly or just the
top part of the assembly are affected.
Command line keyword syntax

ug_import -part=<part name>
[-u=<username>]
[-p=<password>]
[-g=<group>]
[-search=<search file name>]
[-mapping=<mapping file name>]
[-import_folder=<folder name>]
[-id=<Item ID>]
[-rev=<Item Revision>]
[-part_type=<Item Type>]
[-type=<relationship type>]
[-name=<dataset name>]
[-assoc_files=<yes/no>]
[-assoc_root_dir=<associated files root dir>]
[-dryrun]
The details of these will be explained on later pages by using real world
examples.
Using (Directory) Search Files
Your site may not keep all the components of all assemblies in the same
directory. If you specify the name of a search list file on the command line,
NX Manager searches the directories listed in the search list file for the
component parts of the assembly.

Importing Non-Master and Associated Unigraphics Files
You may have other files that are used with your part files (e.g. machining
operation files).
In addition to importing part files, you can import other types of NX files
associated with a part file from operating system directories.
Understanding Various NX Manager Import Scenarios

The following import scenarios will be discussed to import native part file
data.
1. Import Component Parts or Assembly Parts without a Map File
2. Import an Assembly using a Map File and Search File
3. Import a Non-Master Drawing and NC Part File
4. Import Files Associated to a Component (Master) Part File
5. Import Files Associated to the DWG (Non-Master) Part File
6. Import Files Using a Full Map File
To run ug_import, use the following command syntax:
ug_import -part=<part name>
[-dryrun]
[-id=<Item ID>]
[-rev=<Item Revision>]
[-search=<search file name>]

[-mapping=<mapping file name>]
[-import_folder=<folder name>]
[-type=<relationship type>]
[-name=<dataset name>]
[-assoc_files=<yes/no>]
[-assoc_root_dir=<associated files root dir>]
The following tables give a brief description of the value corresponding to

each command line keyword, and the title of the subheading under which
further information can be found.

Import Component or Assembly Parts without a Map File
KEYWORD VALUE
-part= The operating system pathname of the top level part
in the NX assembly which is to be imported.
-dryrun Indicates whether the import will proceed as
expected, without actually doing the import.
-id= The TcEng Item ID which is given to the standard NX
part specified on the command line.
-rev= The Teamcenter Engineering Revision which is given
to the standard NX part specified on the command
line.
-import_folder= The name of the Teamcenter Engineering folder
which stores the imported assembly and all of its
components.
KEYWORD VALUE
-mapping= The operating system pathname of the file containing
details of the way in which individual components in
your assembly should be imported.
-search= The operating system pathname of the file which
lists operating system directories to search for the
components of your assembly.
Import a Non-Master Drawing and NC Part File
KEYWORD VALUE
-type= The type of non-master part file created in
-name= The name of the non-master part file created in
Import Files Associated to a Component (Master) Part File and to the NC

(Non-Master) Part File
KEYWORD VALUE
-assoc_files= Used to instruct ug_import whether to import files
associated with the specified assembly and all of its
components.
-assoc_root_dir= The name of the operating system directory under
which sub-directories containing associated files
belonging to the assembly and all of its components
are located.

Command Line Keywords With ug_import
Use of Quotation Marks
If you have any characters other than letters, digits, underscores, and
hyphens in the value that you specify for a particular keyword, it is
recommended that you enclose the value in quotation marks "" to avoid
import errors. For example, if you wish to import the part "chassis.prt" into a
folder in Teamcenter Engineering called "Concept Car" (note the space in the
folder name), it is advisable to specify the command:
ug_import -part=chassis.prt -import_folder="Concept Car"
Note that the Teamcenter Engineering folder name is surrounded by quotes.
Maximum Length Limit
There is a maximum length limit for the values corresponding to some of

the keywords used by ug_import.
Field Keyword Limit

Part Number -id= 26 characters
Revision -rev= 32 characters
Dataset Name -name= 32 characters
In addition, the combined (Part Name+Revision+Dataset Name) length must

not exceed 50 characters.
Login Keywords
If you have autologin enabled, -part= is the only keyword that must be
specified on the command line. All the other keywords listed in the table are
optional. However, if autologin is disabled the -u= and -p= keywords are
also required. For example,
ug_import -part=1400_wheel_000.prt -u=<user> -p=<password>
where <user> and <password> are the Teamcenter Engineering database

user and password.
Import Component/Assembly Parts without a Map File

Scenario 1
In this scenario, seed part files will be imported.
ug_import -part=border_b_seed.prt -id=B-size -rev=000
-import_folder="Seed Parts" [-dryrun]
ug_import -part=border_c_seed.prt -id=C-size -rev=000
-import_folder="Seed Parts" [-dryrun]
Import a New Master Part File

By default, ug_import imports your assembly (that is, the part file specified
on the command line) as follows:
All parts are imported as a master part file into the Newstuff folder.
The top part in the assembly is overwritten, but any component parts
which already exist in the database are not overwritten.
In order to change the default import behavior for the component parts,
you must specify a mapping file. Therefore assemblies will most likely
be imported with a mapping file.
The -part= keyword specifies the operating system pathname of the top part
in the NX assembly which is to be imported into Teamcenter Engineering.
Both master and non-master part files can be imported.
You must always specify the full pathname of the operating system part
file corresponding to the top level part in your assembly on the ug_import
command line unless the part is located in your current directory. For
example,
ug_import -part=/users/daytr/parts/1600_wheel_assy_000.prt
ug_import searches for the part files corresponding to the components of

your assembly in the same directory as the top part. If the component part
files are not located in the same operating system directory as the top part,
you must specify a search-list file so that ug_import can successfully locate
the components.
The following command line keywords can be used to change the default
import behavior for the top part in the assembly (only):
id=
rev=
The -id= and -rev= keywords can be used to import the part specified on the
command line (only) with a different part number and revision respectively.

Import Part Files into a Folder

The default behavior of ug_import is to import your standard NX assembly
into the folder named Newstuff in your Home folder in Teamcenter
Engineering. You can change the behavior of ug_import so that it
imports your assembly into a different folder. You do this by specifying the
-import_folder= keyword on the command line. For example:
-import_folder="1600 Wheel Assembly"
Note that the -import_folder= keyword causes the assembly and all of its
components to be imported into the specified folder. If you wish individual
components in the assembly to be imported into different folders, you must
specify the -import_folder directive in a mapping file instead.
Checking the Import
The -dryrun keyword allows you to see whether your import will progress
as you expect. It runs through the import procedure without actually
importing any parts into the Teamcenter Engineering database. The normal
ug_import messages are displayed, allowing you to check whether there will
be any errors when you do import the assembly, and to correct them before
proceeding.
The -dryrun keyword is particularly useful if you intend to import a large
assembly because the import checks are performed much faster than a full
import.
Scenario 2
In this scenario, a Wheel Assembly will be imported. A map file will be used
to convert all the part file names to their database part ID. Additionally a
search file will be used, since the parts are in various directories.
ug_import -part=1600_wheel_assy_000.prt -search=1600_search.txt
-mapping=1600_wheel_assy.map [-dryrun]
Search-List File
A search-list file is a text file which lists the operating system directories
which ug_import should search in order to locate the part files corresponding
to component parts in an assembly. The filename of a search-list file is
specified on the ug_import command line using the -search= keyword. For
example,
-search=1600_search.txt
You need to provide a search-list file if any part files corresponding to the
components of your assembly are located in different directories from the part
file which stores the top part in the assembly.
A search-list file simply lists the operating system directories which should be
searched to locate the component files of the assembly. Each directory should
be specified on a new line. If a directory name ends in "/...", all directories
beneath the specified directory also are searched.
For example, a search-list file with the contents:
.
/iman/daytr/v5_sitea/ug_import_files/...
/iman/class-default/v5_sitea_parts
would cause ug_import to search in the following order.

1. The current directory.
2. The directory named /iman/daytr/v5_sitea/ug_import_files and all of

the directories beneath it.
3. The /iman/class-default/v5_sitea_parts directory.

Mapping Files
A mapping file is an optional file that may be specified for the import utility.
The purpose of a mapping file is to allow you to specify exactly how individual
components in an assembly are imported into Teamcenter Engineering.
Mapping File Format
A mapping file is a simple text file which instructs ug_import how to import
the components in your assembly. The text in a mapping file may comprise
expressions, file names, directory names, and the names of parts and
revisions in the database.
A mapping file is divided into sections of the format:
[SECTION_NAME]
KEYWORD=VALUE
KEYWORD=VALUE
An example mapping file is shown below:
! Mapping file for importing chassis assembly
[Defaults]
import_folder = "Import Folder"
db_part_no=$STRIPPED_LEAFNAME
[CA_36245.prt]
db_part_no="CA_36245_000"
db_part_rev="000"
[ENG_83475.prt]
existing_data=$OVERWRITE_EXISTING
db_part_no="ENG_83475_000"
db_part_rev="000"
Key Points
There are a few general points to note when using mapping files:
An exclamation mark (!) at the beginning of a line specifies the line
as a comment line.
Mapping files can contain blank lines.
ug_import ignores leading spaces at the beginning of a line.
The maximum length of a line in a mapping file is restricted to 132

characters, including spaces.
If you wish to include spaces in a field, then you must enclose the field in
double quotes.
Each [SECTION_NAME] and KEYWORD=VALUE directive must be

specified on a separate line.
Using the SECTION_NAME
The SECTION_NAME field can be specified as either [Defaults] or the name

of a NX part file.
If you specify a SECTION_NAME of [Defaults], any KEYWORD=VALUE
mapping file directives specified in this section affect all of the components in
your assembly, unless they are deliberately overridden by specifying a section
corresponding to a NX part name.
For example, in the mapping file above, the directives in the [Defaults]
section affect all the parts to be imported. However, the directives in the
sections entitled [CA_36245.prt] and [ENG_83475.prt] are applied to those
parts only, and override the directives in the [Defaults] section.
A NX part number may be specified in a section by either the full operating
system pathname or just the part number.
You cannot use environment variables in filenames in a mapping
file.

Using the KEYWORD AND VALUE

The KEYWORD field in a mapping file is one of a number of reserved
keywords. These keywords are tabulated below:
Keyword: db_part_no
Description: TcEng part (Item) ID
Valid Expression: $STRIPPED_LEAFNAME
$EXPORTED_PART_NO
Default: If the part has been previously exported from NX
Manager, defaults to the value it had when exported.
Otherwise, defaults to $STRIPPED_LEAFNAME
Keyword: db_part_rev
Description: TcEng part revision
Valid Expression: $EXPORTED_PART_REV
Default: Defaults to A
Keyword: db_part_name
Description: TcEng part name
Valid Expression: $STRIPPED_LEAFNAME
$IMPORTED_PART_NO
Default: If the part has been previously exported from NX
Manager, defaults to the value it had when exported.
Otherwise, defaults to the same value as db_part_no.
Keyword: db_part_desc
Description: TcEng part description
Valid Expression:
Default: Defaults to the same value as db_part_no, if
specified in a mapping file. Otherwise, defaults to
$STRIPPED_LEAFNAME (the file name of the
UG part without the leading directory and the .prt
extension).
Keyword: import_folder
Description: TcEng folder where imported parts are placed.
Valid Expression: $DEFAULT_IMPORT_FOLDER
Default: Your Newstuff folder. Note that -import_folder
specified on the command line takes precedence over
import_folder specified in a mapping file.
Keyword: existing_data
Description: What to do if parts already exist in TcEng
Valid Expression: $FAIL_IF_PART_EXISTS
$FAIL_IF_REV_EXISTS
$OVERWRITE_EXISTING
$USE_EXISTING
Default: Overwrite the existing top part (only) in the assembly,
$OVERWRITE_EXISTING.
For all the component parts in the assembly, use the
existing data $USE_EXISTING.
The VALUE consists of part file names and optional reserved

EXPRESSION(s).
The reserved expressions are described below:
EXPRESSION EXPANDS TO:

$STRIPPED_LEAFNAME OS filename of the component (not
assembly) stripped of any prefix ending
in / (UNIX) or : (VMS) and the .prt
suffix. For example:
"/tmp/top_level_a.prt" "top_level_a"
$STRIPPED___LEAFNAME OS filename of the component stripped
of any prefix ending in / (UNIX) or :
(Note that there are (VMS) and the suffix (delimited by _), if
threeunderscores) present. For example:
"/tmp/top_level_a.prt" "top_level"
$IMPORTED_PART_NO The part number, if the part is being
imported as it will be in TcEng (i.e., after
any renaming specified by the mapping
file has occurred).
$DEFAULT_IMPORT_FOLDER Global default TcEng target folder.
$FAIL_IF_PART_EXISTS If the Part (Item) exists, do not save the
assembly.
$FAIL_IF_REV_EXISTS If Part Revision (Item Revision) exists,
do not save the assembly.
$OVERWRITE_EXISTING If the part data exists, overwrite it.
$USE_EXISTING If a component already exists in TcEng,
use the database copy in the current
assembly.

The Import Log File

Below is an example log file (always named import.log) that is
created during the use of ug_import. Also a syslogfile is created
with more system information and placed in the /tmp directory.
**************** UG Import Utility ****************

Using UG V1.0.0.21
Using assembly load options - Load from directory.
Using supplied mapping file: [wf.map]
Loaded assembly [1600_wheel_assy_000.prt]
Connecting to the database...
Import parts to database using NX Manager V9.0
Connected to the database.
The UG assembly [1600_wheel_assy_000.prt] comprises [5] part(s)

Part # 1, [/users/waynetr/ug_import_files/1600_wheel_assy_000.prt]
NX Manager part number is [1600/000] in folder [Newstuff]
Part will be created with type [Item].
Part # 2, [/users/waynetr/ug_import_files/1250_axle_000.prt]
NX Manager part number [1250/000] already exists.
Using the existing copy.
Existing part type [Item] will be retained.
Part # 3, [/users/waynetr/ug_import_files/1300_bearing_000.prt]
Part # 4, [/users/waynetr/ug_import_files/1400_wheel_000.prt]
Part # 5, [/users/waynetr/ug_import_files/1700_spacer_000.prt]
NX Managerpart number is [1700/000] in folder [Newstuff]
Creating 1600/000
Creating 1300/000
Creating 1400/000
Creating 1700/000
Starting Save.............
Saved part [1300/000] successfully.

All parts were successfully saved.
************ UG_IMPORT finished without error ************
Activity: Using ug_import to Import the Seed Parts

In this activity, you will use the ug_import utility to import a part
file into a dataset. Specifically, you will import additional seed parts
for drawings. Once the parts are inside Teamcenter Engineering,
they will also be placed inside the Unigraphics seed parts folder.
Step 1: Import the seed part files.

In a text editor, view the ug_import.scr.bat script
(ug_import.scr on Unix) in the aa_class/ug_import_files
directory.
Notice, that the DBAUSER variable is already defined using

the legacy userid that was created with the make_user script
in the Organization lesson. All parts will be imported using
this account.
After reviewing the script, exit the text editor without saving.
Open a terminal window with the Teamcenter Engineering/NX

environment set.
Type: cd ug_import_files
Type: ug_import.scr.bat seeds (ug_import.scr seeds on Unix)

The following commands are used in the script to import the
drawing seed part files.
ug_import -part=border_b_seed.prt
-id=B-Size -rev=000 -import_folder="Seed Parts"
ug_import -part=border_c_seed.prt
-id=C-Size -rev=000 -import_folder="Seed Parts"
Step 2: View the import results.

Login to the My Navigator application using the legacy account
(User ID: legacy, Password: legacy, leave Group blank).
Expand the Seed Parts folder in the Home folder.

Step 3: Add the Unigraphics seed parts folder to the Home folder.
Choose the Search icon.

This brings up the Search window.
Choose General... from the query pull-down list.
Choose Clear this query form.
Enter Unigraphics seed parts in the Name field.
Choose Execute this query.

The Unigraphics seed parts folder appears in the General Tab.
Copy the Unigraphics seed parts folder to your Home folder.
Choose the Search icon again to close the Search window.
Step 4: Put the import results in the Unigraphics seed parts folder.
Expand the Seed Parts folder to show the B-Size and C-Size
Items.
Expand the Unigraphics seed parts folder and then the

manifestation folder.
Use EditCut and EditPaste to put the B-Size and C-Size

Items in the manifestation folder.
Step 5: Delete the Seed Parts folder.

Select the Seed Parts folder.
Choose EditDelete.
Choose Yes to confirm.

Activity: Import the 1600 Wheel Assembly
In this activity, you will use ug_import to import an assembly part file and its
components into the database. You will use a mapping file to convert the part
file names to appropriate part numbers.
Step 1: Import the 1600 Wheel Assembly.
Continue to work from the Teamcenter Engineering
environment command window and the ug_import_files
directory.
Type: ug_import.scr.bat 1600 (ug_import.scr 1600 on Unix)

The following command is used to import files for the 1600
Wheel Assembly.
-search=1600_search.txt
-mapping=1600_wheel_assy.map
Step 2: Verify import in My Navigator.

Select your Home folder and choose ViewRefresh.
Expand the Wheel Assembly Parts folder to show the

assembly parts.
Step 3: Review the 1600 Wheel assembly in NX Manager.

Expand the 1600-Wheel Assembly Item.
Expand the 1600/000-Wheel Assembly ItemRevision.
Double-click on the 1600/000 UGMASTER.

NX Manager starts and loads the 1600-Wheel Assembly.
Import a Non-Master Drawing File
Scenario 3
In this scenario, a Drawing file will be imported. To import this non-master
part file the following ug_import arguments will be used.
ug_import -part=1250_axle_000_dwg.prt -id=1250 -rev=000
-name=1250_DWG -type=manifestation [-dryrun]
Explanation
The ug_import utility cannot automatically detect whether a standard NX
part file is a master part file or a non-master part file, unless the master
part file has previously been exported from Teamcenter Engineering using
ug_export.
Using Command Line Keywords
A number of command-line keywords are provided that can be used to notify

ug_import of the type of part file to be imported:
KEYWORD VALUE
-id= The item ID of the master part file
which the non-master part file is to
belong to.
-rev= The item revision which is given to
your im ported non-master part file.
-type= The type of non-master part file.
This may be: specification (or spec
for short) ,or manifestation (man for
short).
-name= The name of the specification or
manifestation.
The keywords -id and -type must both be present for new non-master parts.
The -rev and -name keywords are optional, but are commonly used to provide
specific part revision and non-master dataset name.
Note that if -rev is omitted, and the revision is not specified in a mapping file,
the configured revision (according to the default configuration rule) is used. If
there is no configured revision, then revision "A" is used.
If the -name keyword is absent from the command line, the name of the
dataset defaults to the "stripped leafname" of the top part of the assembly.

Import Files Associated to a (Master) Part File

Scenario 4
In this scenario, some files that are associated to parts will be imported. To
import these files associated to a part file the following ug_import arguments
will be used.
ug_import -part=1250_axle_a.prt -id=1250 -rev=000
-mapping=1600_wheel_assy.map -assoc_files=yes [-dryrun]
Explanation
The ug_import utility allows you to import dependent files that are associated
with both master and non-master part files. In this case dependent files
will be imported as named references into the 1250/000 UGMASTER. The
-mapping is used to map the Axle name of the 1250 part.
Using Command Line Keywords

Two further command-line arguments provide this capability:
KEYWORD VALUE
-assoc_files= Used to instruct ug_import whether to import
associated files belonging to the specified part and
associated files belonging to all of its components.
The value must be "yes" or "no".
-assoc_root_dir= Specifies the root directory under which
sub-directories containing the associated files
belonging to all parts in the spe cified assembly
are located. The directory must already exist.
Both -assoc_files and -assoc_root_dir are optional arguments to ug_import.

If you do not specify -assoc_root_dir on the command line, but you still want
associated files to be imported, you must specify -assoc_files=yes on the
command line. The ug_import utility then searches the following locations
(in the order shown) for the sub-directories containing associated files for
individual parts:
the directory specified by the assoc_files_dir keyword in a mapping file
(if present).
your current directory.
When the -assoc_root_dir argument is specified on the command line,

ug_import assumes that you wish to import associated files belonging to the
part specified on the command line, and the associated files belonging to each
of its components. The associated files are imported from sub-directories
beneath the directory specified by -assoc_root_dir.
If the specified associated files directory cannot be located, the import is

aborted.
Sub-directory Example
When using -assoc_files=yes without -assoc_root_dir= the dependent files will
be imported from the directory 1250. The 1250 is determined from the Part
ID (1250). The dependent files must be in this directory for ug_import to
find them.

Import Files Associated to the DWG (Non-Master) Part File
Scenario 5
In this scenario, some files that are associated to drawings will be imported.
To import the files associated to a non-master part file the following
ug_import arguments will be used. What does this usage do?
ug_import -part=1250_axle_a.prt -id=1250 -rev=000
-name=1250_DWG -type=manifestation -assoc_files=yes
Explanation
The ug_import utility allows you to import dependent files that are associated
with non-master part files. In this case dependent files will be imported as
named references into the 1250_DWG UGPART.
Sub-directory Example
When using -assoc_files=yes without -assoc_root_dir= the dependent
files will be imported from the directory /1250_m_1250_dwg. The
1250_m_1250_dwg is determined from part id (1250) + type (m for
manifestation) + drawing name (1250_dwg) with an underscore between
each section. This gives the sub-directory 1250_m_1250_dwg.
The dependent files must be in this directory for ug_import to find them.
Activity: Import the 1250 Axle Associated Files
In this activity, you will use the ug_import utility to import the 1250.tif file
associated to the 1250 Axle. This part was imported in the previous activity
with the 1600 Wheel Assembly.
Step 1: Import the 1250 Axle Associated files.
Continue working from Teamcenter Engineering environment
command window and the ug_import_files directory.
Type: ug_import.scr.bat 1250axleassoc (ug_import.scr

1250axleassoc on Unix)
The following command is used to import the 1250.tif file
from 1250 sub-directory.
ug_import -part=1250_axle_000.prt -id=1250
-rev=000 -mapping=1600_wheel_assy.map
-assoc_files=yes
Step 2: Review the 1250 Axle Named References in My Navigator.

Locate and select the 1250/000 UGMASTER.
Choose ViewRefresh to update the new file(s) in the

1250/000 UGMASTER.
Using ViewRefresh is necessary since the
1250/000 UGMASTER was previous loaded in

The Named References window displays showing the part files,
including the new 1250_axle_000.tif file.
Choose Close to close the Named References window.

Activity: Import the 1250 Axle Drawing
In this activity, you will import the 1250_axle_000_dwg.prt drawing file

as a non-master UGPART to the 1250 Axle Part.
Step 1: Import the 1250 Axle Drawing.
Continue working from the TcEng environment command
window and the ug_import_files directory.
Type: ug_import.scr.bat 1250axledwg (ug_import.scr

1250axledwg on Unix)
The following command is used to import the
1250_axle_000_dwg.prt file.
ug_import -part=1250_axle_000_dwg.prt
-id=1250 -rev=000 -name=1250_DWG
-type=manifestation
Step 2: Review the 1250 Axle Drawing in My Navigator.

If necessary, expand the Wheel Assembly Parts folder to show
the 1250 Axle Item.
If necessary, expand the 1250 Item to show the 1250/000

ItemRevision.
Select the 1250/000 ItemRevision and choose ViewRefresh to

display the new 1250_DWG UGPART dataset
Select the 1250_DWG UGPART dataset and then choose

ViewNamed References...
The Named References dialog displays showing the drawing
part file.
Step 3: Review the 1250 Axle Drawing using NX Manager

To make this more clear, in NX Manager close all parts. Choose
FileCloseAll Parts.
Choose Yes to confirm the closing of all parts.

Next Open the 1250 Axle Drawing.
Choose FileOpen...
Expand the Wheel Assembly Parts folder and 1250 Item

structure.
Select the 1250_DWG dataset.
Choose OK.
The axle drawing is loaded into the graphics window.

Activity: Import the Axle Drawing Associated Files
In this activity, you will use the ug_import utility to import the
1250_000_dwg.cgm file associated to the 1250 Axle Drawing.
Step 1: Import the 1250 Axle Drawing Associated files.
Continue working in command window.
Type: ug_import.scr.bat 1250axledwgassoc (ug_import.scr

1250axledwgassoc on Unix)
The following command imports the 1250_000_dwg.cgm file
from the 1250_m_1250_dwg sub-directory.
ug_import -part=1250_axle_000_dwg.prt
-id=1250 -rev=000 -assoc_files=yes
Step 2: Review the 1250 Axle Drawing Named References.

In My Navigator, expand the Wheel Assembly Parts folder
structure to show the 1250 Axle Item.
Expand the 1250 Item.
Expand the 1250/000 ItemRevision.
Select the 1250_DWG UGPART dataset and then choose

ViewRefresh to update the new file(s).

The Named References dialog displays showing the files,
including the new 1250_000_dwg.cgm file.
Import Files Using a Full Map File
Scenario 6
In this scenario, all the part files (master, non-master, and associated) will
be imported. To import all these files the following ug_import commands
will be used.
ug_import -part=2105_000.prt -mapping=2105_000.map

ug_import -part=2111_000_dwg.prt -mapping=2105_000.map
ug_import -part=2111_000_nc.prt -mapping=2105_000.map
The one map file will control the parameters for all these part files:
components
assemblies
master part files
non-master part files
associated files to masters
associated files to non-masters
KEYWORDs for the Master Parts

These KEYWORDs are used in the mapping file to control the Part ID,
Revision, Part Name, and Part Description for the Item, Item Revision, and
UGMASTER created during the import.
KEYWORD DESCRIPTION DEFAULT

db_part_no TcEng part (Item) If the part has been previously
ID exported from NX Manager,
defaults to the value it had when
exported. Otherwise, defaults to
$STRIPPED_LEAFNAME
db_part_rev TcEng part Defaults to A
revision


db_part_name TcEng part name If the part has been previously
exported from NX Manager, defaults
to the value it had when exported.
Otherwise, defaults to the same
value as db_part_no.
db_part_desc TcEng part Defaults to the same value as
description db_part_no, if specified in a
mapping file. Otherwise, defaults
to $STRIPPED_LEAFNAME (the
file name of the UG part without
the leading directory and the .prt
extension).
KEYWORDs for the Non-Master Parts

These KEYWORDs are used in the mapping file to control the name of the
UGPART (non-master) and determine the placement of the UGPART inside
the Item Revision (e.g. Specification, Manifestation relation).
db_model_name TcEng dataset No default value (not required for

name master model type)
db_model_type TcEng model type The model can be: specification (or
spec for short) or manifestation (man
for short). If not specified the model
type defaults to master.
KEYWORDs for Associated Files for Master/Non-Master Parts

These KEYWORDs are used in the mapping file to control the import of
associated files (e.g. TIF, CGM, HTML, and other NX files). Specifying
assoc_files=yes will cause ug_import to import files into the UGMASTER
or UGPART as additional named references.

assoc_files Used to instruct No default value. If assoc_files_dir
ug_import is not specified, defaults to a name
whether to resembling the part filename. For
import files example, the associated files for a
associated with part named 2111.prt are located in a
the specified sub-directory named 2111.
assembly and all
of its components.
assoc_files_dir The sub-directory The full path directory containing the
under the current associated files or the sub-directory
directory where name from the current directory
associated files containing the associated files.
for the specified
part can be found.
General purpose KEYWORDs

These general purposed KEYWORDs are used in the mapping file to
control what folder imported parts are put into and whether components
are overridden.
import_folder TcEng folder Your Newstuff folder. Note that

where imported -import_folder specified on the
parts are placed. command line takes precedence over
import_folder specified in a mapping
file.
existing_data What to do if Overwrite the existing top
parts already part (only) in the assembly,
exists in TcEng $OVERWRITE_EXISTING. For
all the component parts in the
assembly, use the existing data
$USE_EXISTING.

Below is an example map file. This mapping file will specify the ID and
Revision for the components but will also state the Model Type, Model Name,
and whether the part has Associated Files.
[Defaults]
import_folder="2105 Assembly"
assoc_files=no
[2105_000.prt]
db_part_id=2105
db_part_name="Skate Assembly"
db_part_rev=000
[1101_000.prt]
db_part_id=1101
db_part_name="Wheel Assembly"
db_part_rev=000
assoc_files=yes
[1150_000.prt]
db_part_id=1150
db_part_name="Axle"
db_part_rev=000
[1113_000.prt]
db_part_id=1113
db_part_name="Hub"
db_part_rev=000
[1110_000.prt]
db_part_id=1110
db_part_name="Wheel"
db_part_rev=000
[2111_000.prt]
db_part_id=2111
db_part_name="Frame"
db_part_rev=000
assoc_files=yes
[2111_000_dwg.prt]
db_part_id=2111
db_part_rev=000
db_model_type=manifestation
db_model_name=2111_DWG
assoc_files=yes
[2111_000_nc.prt]
db_part_id=2111
db_part_rev=000
db_model_type=manifestation
db_model_name=2111_CAM
assoc_files=yes
Activity: Import 2105 Frame Assy with Mapping File

In this activity, you will use the ug_import to import the 2105 Frame
Assembly by using a mapping file for all the master parts, non-master parts,
and associated files.
Step 1: Import the 2105 Frame Assembly and all of its other files.
In the command window, change to the ug_import_2105
directory, located in the aa_class directory.
Open the ug_import_2105.scr.bat script (ug_import_2105.scr

on Unix) in a text editor.
After reviewing the script, exit the text editor without saving.
Type: ug_import_2105.scr.bat (ug_import_2105.scr on Unix)

The following commands are used to import the assembly files.
ug_import -part=2105_000.prt
-mapping=2105_assy.map -assoc_files=yes
ug_import -part=2111_000_dwg.prt
ug_import -part=2111_000_nc.prt
Step 2: Review the 2105 Frame Assembly in My Navigator.

When the script is finished, select the Home folder and choose
ViewRefresh.
The 2105 Assembly folder show now be visible.
Expand the 2105 Assembly folder to show the assembly parts.
Step 3: As desired, review the 2105 Frame Assembly using NX Manager.

To make this more clear, in NX Manager, choose
FileCloseAll Parts.
Next Open the 2105 Frame Assembly.
Choose FileOpen...
Expand the 2105 Assembly folder and 2105 Item structure.
Select the 2105/000 UGMASTER dataset.
Choose OK.
The 2105 Frame Assembly loads into the graphics window.

Step 4: Review the non-master 2111 Frame Drawing.

From NX, choose FileOpen...
Expand the 2105 Assembly folder and 2111 Item structure.
Select the 2111_DWG dataset.
Choose OK.
The frame drawing loads into the graphics window.
Step 5: Close NX Manager.

From NX, choose FileExit
Choose Yes to confirm the exit.
Importing Non-Unigraphics Files into an Item

The M243_Heat_Treat text file should be imported into the database to be
a reference of the 1250 axle part.
The import_file utility allows you to import files into the Teamcenter
Engineering database according to a set of user-specified arguments. These
arguments will supply:
user identification information
dataset information
Item information to be associated with the imported file
The latter is new in this class for the use of import_file. In supplying the
Item information, a Dataset and Item will be created and the dataset will
be placed inside the Item.
In practice this utility is used:
1. To import files into Teamcenter Engineering just as datasets (as seem in
a previous lesson).
2. To import files into Teamcenter Engineering as datasets and automatically

place the dataset inside an Item or Item Revision. The Item can be
created or already exist.
3. To import other CAD files into Teamcenter Engineering as datasets and

place the file inside an Item Revision.
The import_file options for importing a dataset:
IMAN_ROOT/bin/import_file -f=<filename>
-type=<datasettype> -d=<dataset_name>
-ref=<named_reference> [-item=<item_id>]
[-revision=<item_rev>] [-ie={n | y}] [-log=<file>]

Activity: Import the Heat Treat Text File
In this activity, you will use the import_file utility to import a text file into
the database to be a reference of the 1250 Axle part.
Step 1: Import the m243_heat_treat.txt text file.
In the command window, change back to the ug_import_files
directory located in the aa_class directory.
Type: ug_import.scr.bat heattreat ( ug_import.scr heattreat

on Unix)
The following command is used to import m243_heat_treat.txt
into the 1250/000 Axle ItemRevision as a Reference.
IMAN_ROOT/bin/import_file -f=m243_heat_treat.txt
-d=M243_Heat_Treat -type=Text -ref=Text -de=a
-item=1250 -revision=000 -ie=y -log=-
Step 2: Review the imported file inside the 1250 Axle.

Expand the Wheel Assembly Parts folder.
Expand the 1250 Item and 1250/000 ItemRevision.
Select the 1250/000 ItemRevision and choose ViewRefresh to

display the new M243_Heat_Treat dataset.
Double-click on the M243_Heat_Treat dataset.

The M243_Heat_Treat dataset is opened into the default editor.
Review the file, then exit the text editor.
Releasing Previously Imported Unigraphics Data

After the NX data has been imported into Teamcenter Engineering you may
choose to release the data. The import step only imports the data and usually
leaves the data in an unreleased, writable state.
Normally the release process would require review and signoff by one or more
employees. In this case the data may have already been in a release state
outside of Teamcenter Engineering and the data has just been imported.
Especially for CAD/CAM data, in this case the NX data, there may be a
stronger need for a Single Level Release. Before providing the signoff, the
responsible user may want to open the UGMASTER being released with the
Item Revision.
Considerations in Releasing Item Revisions
When releasing Item Revisions, the Specification relation objects are released
together with the handler EPM-attach-target-objects.
Considerations in Releasing Non-specification Data
When non-specification data is released the reviewers defined in the

procedure may be different than the reviewer defined in the procedure for
master and specification data.
When releasing non-specification data immediately after the data has been
imported, the data could be released in the same procedure as the master and
specification data. This could be accomplished by initiating the Item Revision
and pasting the non-specification data into the Job (before the Job is started).

Activity: Release the 2111 Item Revision
In this activity, you will use the Import Release process template to release
some of your previously imported data.
Step 1: Initiate the 2111 Frame ItemRevision.
If necessary, expand the 2105 Assembly folder.
Expand the 2111-Frame Item to show the 2111/000-Frame

ItemRevision.
Select the 2111/000 Frame ItemRevision.
The New Process dialog appears. The Process Name defaults
to the object name.
Optionally enter a Description: releasing imported data
Set the Process Template Filter to Assigned.

Notice the Process Template defaults to Import Release
because of preferences you set in an earlier lesson.
Choose OK.
Step 2: Review the data from your Inbox and perform the signoff.
Choose the Open Inbox icon.
Expand your Tasks to Perform Folder
The perform-signoffs task was automatically assigned to you

because of the CR-fill-in-reviewers handler you added to the
Import Release process template in an earlier lesson.
View the Attachments.
Choose the No Decision link.
Choose Approve, then Apply.
In the Home folder, select the 2111/000-Frame ItemRevision

and choose ViewRefresh.
If necessary, select the 2111/000 UGMASTER and choose

ViewRefresh.
Notice that the status flags have now been set.

Summary
In this lesson you:
Imported Unigraphics Data into the Database
Released Imported Unigraphics Data
Appendix
A Student Helpful Hints
The following topics are explained to help you understand the environment
that you will be using this week. This classroom environment is likely to be
similar to your future working environment.
UNIX Commands
vi Editor Review
UGS, All Rights Reserved Teamcenter Engineering Application Administration A-1

Student Helpful Hints
UNIX Commands
This page is to be used as a review of certain UNIX commands that will
be used in activities.
Syntax used here and throughout this book:
<filename> = value inside brackets and italicized
means this is a variable and you should enter the actual value instead of the
variable filename. The actual value will be stated in the courseware or
will be known.
UNIX COMMAND WHAT DOES IT DO?

start_portal starts TcEng (unix)
env-sitea sets the TcEng environment variables in the shell
env | sort lists the environment variables alphabetically
env | grep IMAN lists environment variables with the "IMAN"
string
cd changes to your home directory
cd dir changes to the dir directory
echo $IMAN_DATA shows the value of the $IMAN_DATA env. var.
cd $IMAN_DATA changes to the directory of the $IMAN_DATA
value
ls lists the files in the current directory
ls -ald lists the files in the current directory with details
clearlocks runs the clearlocks utility (same for any utility)
install -user infodba runs the install utility with arguments -user
infodba
./make_user.scr runs make_user.scr from the current directory
editor edit or view a file name filename
cp copy sourcefile to newfile
chmod 755 change file protections to user: read, write,
execute; group: read, execute; world: read, execute
more to list the filename contents
lp to print the filename
rm to delete the filename
The text file editor has been set up as an alias to use the system
$EDITOR environment variable. If using the text editor does not
work, please ask the instructor for assistance.
A-2 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912
Specific operations are shown below:
OPERATION UNIX COMMANDS

change to directory cd <dir>
list files ls
edit file editor <filename>
edit a file with vi vi <filename>
Command Line Entry Tips

These tips may only apply if your terminal has been properly set up.
Cut and Paste operations can easily be done with the following sequence:
1. Hold down the left mouse button and drag over preferred text. The text
should highlight.
2. With the text highlighted and the courser at the text insert point, select
the middle mouse button. The text should be entered.
Your keypad has been setup to easily repeat previous commands by using the
following sequence.
1. Push the Esc button..
2. Push the k key, to roll back to a previous command. Push the k key again
to roll back previous commands.
3. Push the j key, to roll forward in command history.
4. Once you are at the desired command, Push Enter.

vi Editor Review
The most popular UNIX editor is vi. It is the only editor described
in this course.
vi is considered difficult to learn, but very powerful.
There are three modes in operating vi:

Command Mode
Last Line Mode (ex)
Input Mode
A-4 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912

Appendix
B Teamcenter Engineering and NX

Manager Environment Settings
The following topics are explained to help you understand the environment
that you will be using this week. This classroom environment is likely to be
similar to your future working environment.
Teamcenter Engineering Environment Variable List
Teamcenter Engineering Preference List
UG/Manager Preference List
UGS, All Rights Reserved Teamcenter Engineering Application Administration B-1

Teamcenter Engineering and NX Manager Environment Settings
Teamcenter Engineering Environment Variable List (sample)

The following environment variables are protected in iman_profilevars:
IMAN_BIN
IMAN_DATA
IMAN_DB_CONNECT
IMAN_INCLUDE
IMAN_PRINTER
IMAN_USER_TOOLS
ORACLE_SERVER
ORACLE_SID
POM_SCHEMA
POM_TRANSMIT_DIR
XFILESEARCHPATH
This remainder of this section provides an alphabetically-sorted listing of

Teamcenter Engineering environment variables.
IMAN_BIN
IMAN_APP_UID_DIR
IMAN_DATA
IMAN_DB_CONNECT
IMAN_HELP_FILE
IMAN_INCLUDE
IMAN_KEEP_SYSTEM_LOG
IMAN_LANGUAGE
IMAN_LIBRARY
IMAN_LOG
IMAN_PRINTER
IMAN_ROOT
IMAN_TMP_DIR
IMAN_UG_DEFAULT_PART
IMAN_USER_LIB
IMAN_USER_UID_DIR
IMAN_USER_TOOLS
B-2 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912
LANG
LD_LIBRARY_PATH
LIB_PATH
LIBMODE
MB_CHARS
MGC_IMAN_CONFIG_FILE
MGC_HOME
MGC_LOCATION_MAP
MGLS_LICENSE_FILE
MODE
ORACLE_SERVER
ORACLE_SID
PATH
POM_SCHEMA
POM_TRANSMIT_DIR
SHLIB_PATH
ROSE
ROSE_DB
UGII_APISERVER_PROGRAM
UGII_BASE_DIR
UGII_USERFCN
XBMLANGPATH
XFILESEARCHPATH

Teamcenter Engineering Preference List (sample)

This section provides an alphabetically-sorted listing of Teamcenter
Engineering preferences.
AE_dataset_default_keep_limit
IMAN_Administration_Logging
IMAN_Application_Logging
IMAN_Auto_Checkout
IMAN_auto_login
IMAN__Tool
IMAN__Tool_List
IMAN__Volume
IMAN_DISABLE_FLASH
IMAN_effectivity_users
IMAN_effectivity_roles
IMAN_FLASH_FILE
IMAN_GROUP_PFILE
IMAN_inbox_interval
IMAN_initial_window
IMAN_Installation_Logging
IMAN_Journalling
IMAN_Journal_Modules
IMAN_mail_interval
IMAN_markup_named_ref
IMAN_max_number_of_retries
IMAN_name_delimiter
IMAN_name_sequence
IMAN_NFS
IMAN_organization_id
IMAN_POM_JOURNALLING
IMAN_retry_time
IMAN_ROLE_PFILE
IMAN_Security_Level
IMAN_Security_Logging
IMAN_STAGING_AREA
IMAN_System_Logging
IMAN_transfer_area
IMAN_UG_ATTRIBUTES_FORM
_relation_primary
RECOVER_TO_UNRELEASED_STATUS
RECOVER_TO_VOLUME
WS__bg
WS__fg
WSOM_find_set_search_limit
WSshowToolBar
WsoFolderSavePref
WsoInsertSelectionsPref
WsoInsertNoSelectionsPref
IMAN_checkout_and_export
IMAN_check_out_dir
IMAN_remove_file_on_check_in
DatasetTypesPref
FormTypesPref
IMAN_ignore_case_on_search
OpenAfterCreatePref
IMAN_display_real_prop_names
IMAN_pattern_match_style
WS_expand_on_paste
WSColumnsShownPref
WSShownColumnWidthsPref
WSColumnsHiddenPref
WSHiddenColumnWidthsPref
FLColumnCatIVFSeparatorPref
FLColumnCatObjSeparatorPref
WSDisplayTypePref

WS_icon_placement
_shown_relations
_relations_as_folders
_default_relation
_relation_primary
config_status_list
IMAN_BOM_Precision_Preference
IMAN_config_rule_name
IMAN_config_rule_users
IMAN_show_open_in_ug_button
PSEshowToolBar
PSEColumnsShownPref
PSEShownColumnWidthsPref
PSEColumnsHiddenPref
PSEHiddenColumnWidthsPref
PSEDisplayTypePref
PSE_icon_placement
PSEPreciseColorPref
PSEImpreciseColorPref
PSEAlternateColorPref
PSEAutoPackPref
PSEShowAlternatesPref
_object_columns_shown
_object_widths_shown
_object_columns_hidden
_object_widths_hidden
CR_allow_alternate_procedures
CR_UIF_preload_group_filter
IMAN_CM_STATUS
IMAN_CM_approver_modifier_roles
CR_UIF_spacing
CR_UIF_user_name_display
CR_UIF_group_role_shown
CR_UIF_responsible_party_shown
INBOX_has_tasks_button_fg
INBOX_has_tasks_button_bg
INBOX_has_new_tasks_button_fg
INBOX_has_new_tasks_button_bg
INBOX_is_empty_button_fg
INBOX_is_empty_button_bg
INBOX_new_tasks_icon_fg
INBOX_new_tasks_icon_bg
INBOX_new_task_fg
INBOX_new_task_bg
INBOXDisplayTypePref
INBOX_icon_placement
INBOXColumnsShownPref
INBOXhownColumnWidthsPref
INBOXColumnsHiddenPref
INBOXHiddenColumnWidthsPref
INBOX_not_sorted_columns
INBOX_not_sorted_flags
INBOX_sorted_columns
INBOX_sorted_flags
ORG_UIF_spacing
ORG_UIF_user_name_display
IDSM_permitted_sites
IDSM_permitted_transfer_sites
IDSM_restricted_sites
IMAN_ods_client_def_timeout
IMAN_ods_client_initial_timeout
IMAN_publishable_classes
ODS_permitted_sites
ODS_restricted_sites

ODS_searchable_sites
ODS_searchable_sites_excluded
ODS_site
WEB_default_site_server
WEB_fullsize_image_display_type
WEB_fullsize_image_generate_type
WEB_image_size_vert
WEB_image_size_horiz
WEB_inbox_columns
WEB_max_search_results
WEB_package_multipart
WEB_packaging_extension
WEB_psm_columns
WEB_po_columns
WEB_show_thumbnail_image
WEB_thumbnail_image_display_type
WEB_thumbnail_image_generate_type
WEB_unpackage_multipart
WEB_wso_columns
STEP_approved_status
STEP_cad_filename_pref
STEP_design_specification_pref
STEP_drawing_pref
STEP_export_data_format
STEP_export_directory
STEP_import_directory
STEP_make_or_buy_attr
STEP_material_specification_pref
STEP_not_yet_approved_status
STEP_part_items
STEP_process_specification_pref
STEP_surface_finish_specification_pref
NX Manager Preferences (sample)

PURPOSE CUSTOMER DEFAULT(S) DEFAULT
VALUES
Associated File UGMGR_Export On
Management UGMGR_UserRole All
Product UGMGR_StructureUpdateOnLoad On
Structure
UGMGR_StructureUpdateOnSave On
Synchronization
Auto-Positioning UGMGR_AutoPositionComps Off
of New PSE
Components
Callout UGMGR_CalloutAttribute Sequence
Management Number
Default Seed Part UGMGR_SeedPartName No default value
Display of Select UGMGR_DisplaySeedDialog Yes
Seed Part dialog
Display of the UGMGR_DisplaySaveasDialog Yes
SaveAs Non
Master Part Files
dialog
Default Part UGMGR_PartDisplayPreference NumberName
Display Format
in Part Selection
dialog

The following table lists the TCEng preferences which can be added to the
.iman_env preferences file.
PURPOSE PREFERENCE(S) SITE, GROUP

OR USER
.iman_env
PREFERENCE
FILE?
Default tool for IMAN_UGMASTER_Tool Site
datasets
IMAN_UGPART_Tool
Default separator IMAN_ugmaster_name_separator Site
character displayed
between item ID
and revision ID
Part types displayed IMAN_part_types_display_filter Group, Site
to a user
Default Part Type IMAN_default_part_type User, Site
Display of the "Open IMAN_show_open_in_ug_button User, Site
in UG" button in
PSE DEFAULT: false
Default IMAN_config_rule_name User, Site
configuration rule
Use of precise IMAN_BOM_Precision_Preference User, Site
or imprecise
assemblies DEFAULT: Imprecise
The following table lists the TcEng preferences whihc should only be added to
the .iman_ugman_env preferences file.
PURPOSE PREFERENCE(S)
Default dataset UGMAN_UGPartNameWRev
name on part
creation DEFAULT: 1
Automatic checkout UGMAN_CheckOut
of datasets on
creation DEFAULT: 0
Default type of UGMAN_PartType
dataset created with
a part DEFAULT: UGMASTER
Display of Part Type UGMAN_ShowPartType
option in Create
Part dialog DEFAULT: 0
The following table lists three TcEng environment variables which are used
to control plotting.
PURPOSE ENVIRONMENT VARIABLES DEFAULT

VALUES
Control of plotter UGII_PLOT_NODE
queues and drawing
names IMAN_UG_PLOTTER
IMAN_UG_DRAWING
Summary of the Preference Hierarchy
Setting Files User

1 User In Shell n/a
2a User IMAN_USER_PFILE IMAN_DATA/upfiles/.iman_env
2b User IMAN startup directory the directory where i-Man starts
3 Role IMAN_ROLE_PFILE IMAN_DATA/rp_files/.iman_env
4 Group IMAN_GROUP_PFILE IMAN_DATA/gp_files/.iman_env
5 Site n/a IMAN_DATA./.iman_env

Appendix
C Teamcenter Engineering Notes

and Utility Quick Reference
The following topics are provided:

Teamcenter Engineering System Administration Utilities (Quick
Reference)
Common Command Line Arguments
Teamcenter Engineering System Administration User Accounts and

Groups
Setting the TcEng Environment
UGS, All Rights Reserved Teamcenter Engineering Application Administration C-1

Teamcenter Engineering Notes and Utility Quick Reference
System Administration Utilities

In addition to the functions provided in Admin application in Portal,
Teamcenter Engineering provides several stand-alone utilities that are
run outside of an Teamcenter Engineering session from an operating
system command shell. This chapter discusses the basic concepts of using
Teamcenter Engineering utilities, provides a quick reference for locating
utilities in this chapter, and provides detailed information for each utility.
The following table provides a quick reference to some of the more frequently
usedTeamcenter Engineering utilities. The table lists each utility and the
intended function. This quick reference is intended to assist you with locating
the proper utility to perform a function or correct a problem. You should
thoroughly understand each utility before using it.
Utility Function
am_install_tree Allows you to install an AM rule tree for your
site.
clearlocks Clears dead process locks from the database.
database_verify Compares any two Global Teamcenter
Engineering sites for compatibility. Used with
Global Teamcenter Engineering only.
dataset_cleanup Allows you to repair corrupted datasets and
revision anchors.
default_queries Allows you to re-install one or more of the default
query forms
export_recovery Allows you to recover and restore exported
objects to your database under certain
conditions.
iman_backup Performs complete, cumulative, and incremental
backup and restore of Teamcenter Engineering
volumes and data files.
iman_dbconfig Creates new Teamcenter Engineering database
or upgrades an existing Teamcenter Engineering
3.x database.
iman_sync Updates remote objects on a class-by-class basis.
Used with Global Teamcenter Engineering only.
imanhelp Accesses verbose Teamcenter Engineering error
message information.
import_file Imports single or multiple data files into the
database.
install Allows you to perform limited Teamcenter
Engineering maintenance and Oracle database
administration.
install_types Adds or deletes types from the database.
C-2 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912
Utility Function
item_export Exports Items from Teamcenter Engineering
singularly or in batch mode. Companion utility
to item_import.
item_import Imports Items into Teamcenter Engineering
in batch mode only. Companion utility to
item_export.
list_users Creates a list of users currently logged into
make_datasettype Creates new dataset types and tools singularly
or in batch mode
make_user Creates new Teamcenter Engineering users,
groups, persons, roles, and volumes.
makeuil Generates Motif User Interface Library (UIL)
form from a form description input file.
object_archive Performs batch processing of object archive
transfer pending requests. Companion utility
to object_restore.
object_backup Selectively backs up Teamcenter Engineering
objects from the database. Companion utility to
object_recover.
object_recover Selectively recovers Teamcenter Engineering
objects from storage media. Companion utility
to object_backup.
object_restore Performs batch processing of object restore
transfer pending requests. Companion utility
to object_archive.
ps_rename_bvrs Renames BOMView Revisions (BVRs) using the
current default naming scheme.
purge_datasets Cleans up (purges) old datasets from the
database.
purge_mirror_volumes Cleans up (purges) mirrored volumes. Used with
IMANFS only.
purge_volumes Deletes operating system files associated with
deleted Teamcenter Engineering objects.
refile_info Generates a list of identifiers of every Item
Revision in the default volume.
report_volume Lists the operating system path of all existing
Teamcenter Engineering volumes.
reset_protection Synchronizes UGPARTand
UGMASTERprotection attributes.

Utility Function
review_volumes Allows you to to review volume file space
allocation and to remove un-referenced files from
these volumes.
sb Allows you to view, create, and manage
object classes in Teamcenter Engineering.
Character-based (VT100).
schema_browser Allows you to view, create, and manage object
classes in Teamcenter Engineering. Motif-based.
step_export Allows you to export Teamcenter Engineering
data from the Teamcenter Engineering database
to STEP-compliant physical files.
step_import Allows you to import product information
from STEP-compliant physical files into the
Teamcenter Engineering database.
taxonomy Generates a summary of POM class hierarchy.
Common Command Line Arguments

Most of the utilities documented in this chapter use common command line
arguments. These common command line arguments are so prevalent and
necessary (e.g., -p=password) that they will be documented here instead
of being redundantly documented for each utility. Not all utilities accept or
require all these arguments. Optional and unique command line arguments
are documented for each utility.
-u=<user_id> Teamcenter Engineering user ID. In most cases

the Teamcenter Engineering user ID will be
infodba or another Teamcenter Engineering user
ID with similar privileges.
If -u= is used without providing the value,
Teamcenter Engineering will use the operating
system username. This is consistent with
autologin behavior.
-p=<password> Teamcenter Engineering password associated
with the -u=<user_id> argument.
If -p= is used without providing the value,
Teamcenter Engineering will use a NULL value
for the password.
If -p= is not supplied, Teamcenter Engineering
will use the value for the password.
-g=<group> Teamcenter Engineering group associated with
the -u=<user_id> argument. In most cases the
group will be dba.
If -g= is used without providing the value,
Teamcenter Engineering will use the users default
Teamcenter Engineering group.
-noprompt Disables interactive login for this utility session.
If this argument is supplied, your -u=<user_id>,
-p=<password>, and -g=<group> arguments
must be valid (i.e., result in a successful login)
or this utility will not run and you will not be
prompted for correct information.
-h Display help text for the utility.
-v Run utility in verbose mode. Display maximum
amount of information. Typically, non-verbose
utility sessions only display error messages.

System Administration User Accounts and Groups

Several of the examples in this chapter use the default Teamcenter
Engineering system user account (infodba), password, and the default
system administration group (dba). The example command line typically
includes these arguments:
-u=infodba -p=<password> -g=dba
Unless stated otherwise, you may use any other Teamcenter Engineering
system administration user account and/or system administration group
to run these utilities.
Setting the Teamcenter Engineering Environment

The utilities documented in this chapter run from the command line inside
operating system command shells. Because an Teamcenter Engineering
session is not running, the Teamcenter Engineering environment must be set
manually before these utilities can be run. It is only necessary to perform
this procedure once for each shell session. The environment will remain
configured until the shell is closed or the settings are overridden by other
shell commands.
Each Teamcenter Engineering utility documents the environment required
to successfully run it. The environment information included with each
utility assumes that the Teamcenter Engineering environment has been set
as described in the following paragraphs.
In the following procedures, default path names are used. If
other path names were specified during Teamcenter Engineering
installation, use those path names instead.
UNIX
1. Open a command shell on your workstation.
2. Enter one of the following sets of commands:
Bourne/Korn IMAN_ROOT=/usr/iman0900; export IMAN_ROOT

Shell IMAN_DATA=/usr/iman0900/imandata; export IMAN_DATA
. $IMAN_DATA/iman_profilevars
C Shell setenv IMAN_ROOT /usr/iman0900
setenv IMAN_DATA /usr/iman0900/imandata
source $IMAN_DATA/iman_cshvars

Index
A Command Suppression Dialog . . . . 14-4

Access control . . . . . . . . . . . . . . . 17-10 Compound Property Rules . . . . . . 13-28
Access Control . . . . . . . . . . . . . . . 17-10 establishing . . . . . . . . . . . . . . . 13-30
AM Rule Tree . . . . . . . . . . . . . . . . 9-10 Controlling the Workflow with Process
Assigning Default Process Templates . . . . . . . . . . . . . . . . . . 11-8
Templates . . . . . . . . . . . . . 14-8, 14-11 Course Description
Associated files Introduction
import class overview . . . . . . . . . . . . 13
ug_import . . . . . . . . 18-34, 18-36 Create a Query that Finds Home
attribute . . . . . . . . . . . . . . . . . . . . 3-13 Folders . . . . . . . . . . . . . . . . . . . . . 7-7
Create New Dataset and Import
File . . . . . . . . . . . . . . . . . . . . . . . 15-5
B
Create Part Files . . . . . . . . . . . . . . 17-7
Benefits of the CM Application Create Status Types . . . . . . . . . . . . . 8-6
Benefits of the ECM Creating a Group . . . . . . . . . . . . . . 2-10
Application . . . . . . . . . . . . . . 12-3 Creating a Multi-Task Process . . . . 11-35
BOMView Types . . . . . . . . . . . . . . 6-10 Creating a Person . . . . . . . . . . . . . 2-14
BOMViews and BOMView Creating a Process Template that Does
Revisions . . . . . . . . . . . . . . . . . . . 17-6 Not Require Signoff
Build the Blazing Blades Organization in Creating a Process Template that Does
TcEng Not Require Signof . . . . . . . . 11-14
Build the Blazing Blades Organization Creating a Single Signoff Release
in i-Man . . . . . . . . . . . . . . . . . 2-2 Process . . . . . . . . . . . . . . . . . . . . 11-19
Business Modeler . . . . . . . . . . . . . . 13-2 Creating a Sub-Group . . . . . . . . . . 2-12
Business Modeler Action Rules . . 13-35 Creating a User . . . . . . . . . . . . . . . 2-15
Business Modeler Deep Copy Creating a Volume . . . . . . . . . . . . . 2-27
Rules . . . . . . . . . . . . . . . . . . . . . 13-45 Creating Accounts with the make_user
Business Modeler Import/Export Utility . . . . . . . . . . . . . . . . . . . . . 2-41
Rules . . . . . . . . . . . . . . . . . . . . . 13-52 Creating an Account Interactively . . 2-8
Creating Change Types . . . . . . . . . 12-7
C Creating Process Templates . . . . . . 11-9
Creating Saved Queries . . . . . . . . . . 7-3
Change Object Folder Structure
Creating the Item and PSE Support
EC Folder Structure . . . . . . 12-2, 12-6
Data . . . . . . . . . . . . . . . . . . . . . . . 6-2
Class Attribute Tree . . . . . . . . . . . . . 4-6
Creating Workflow Processes . . . . . 11-2
Classes, Types and Properties . . . . 3-12
Command Line Keywords with
ug_import . . . . . . . . . . . . . . . . . 18-20 D
Command Suppression . . . . . . . . . 14-3 Dataset Objects . . . . . . . . . . . . . . . . 5-3
UGS, All Rights Reserved Teamcenter Engineering Application Administration Index-1

Index
Dataset Type using the Standard IMAN_ugmaster_name_separator . . 17-36

Method . . . . . . . . . . . . . . . . . . . . 5-12 Import
Dataset Type using the Wizard . . . . . 5-7 part files
Defaults into folder other than
standard NX defaults file . . . . . 17-38 Newstuff . . . . . . . . . . . . 18-22
Import a Non-Master Drawing
E File . . . . . . . . . . . . . . . . . . . . . . 18-33
Import Assembly with Map File and
EC Folder Structure Search File . . . . . . . . . . . . . . . . . 18-23
Affected Items . . . . . . . . . . . . . . 12-6 Import Component/Assembly Parts
Problem Items . . . . . . . . . . . . . . 12-6 without a Map File . . . . . . . . . . . 18-21
Solution Items . . . . . . . . . . . . . . 12-6 Import Files Associated to a Master Part
Editing the Rule Tree . . . . . . . . . . . 9-21 File . . . . . . . . . . . . . . . . . . . . . . 18-34
Environment Variable Settings . . 14-17 Import Files Associated to the DWG
Environment Variable Settings for NX (Non-Master) Part File . . . . . . . . 18-36
Manager . . . . . . . . . . . . . . . . . . 17-37 Import Files Using a Full Map
Exporting and Importing the Rule Tree File . . . . . . . . . . . . . . . . . . . . . . 18-41
from a File . . . . . . . . . . . . . . . . . . 9-36 Import Log File . . . . . . . . . . . . . . 18-28
Exporting the Access Manager Rule import_export_business_rules
Tree . . . . . . . . . . . . . . . . . . . . . . . 9-37 utility . . . . . . . . . . . . . . . . . . . . 13-59
Importing an Access Manager Rule
F Tree . . . . . . . . . . . . . . . . . . . . . . . 9-38
Fail-safe Volumes . . . . . . . . . . . . . . 2-29 Importing Files Interactively . . . . . 15-4
Files Importing Files Using the import_file
ug_import Utility . . . . . . . . . . . . . . . . . . . . 15-10
mapping files . . . . . . . . . . . 18-24 Importing Non-Unigraphics Files into an
Form Types . . . . . . . . . . . . . . . . . . . 3-2 Item . . . . . . . . . . . . . . . . . . . . . . 18-47
Forms Introduction to Using Command Line
using schema editor to add POM Keywords . . . . . . . . . . . . . . . . . . 18-14
classes . . . . . . . . . . . . . . . . . . . 4-6 Introduction to Using Mapping
Files . . . . . . . . . . . . . . . . . . . . . 18-13
H Item Structure and Named
References . . . . . . . . . . . . . . . . . . 17-4
Handlers, EPM Item Type Wizard . . . . . . . . . . . . . 4-20
CR-assert-targets-checked-in . . . 11-29 Item Types . . . . . . . . . . . . . . . . . . . . 4-2
demote on reject . . . . . . . . . . . . . 11-28
disallow-adding-targets . . . . . . . 11-28 L
How Rules-Based Protections
Work . . . . . . . . . . . . . . . . . . . . . . 9-10 List of Values for Form Data . . . . . 3-16
How to Use this Manual . . . . . . . . . . 15 Lock part files . . . . . . . . . . . . . . . 17-10
LOV . . . . . . . . . . . . . . . . . . . . . . . 3-16
I
M
IMAN_DATA Directory . . . . . . . 1-4, 1-8
IMAN_ROOT Mapping files
local directories . . . . . . . . . . . . . . 1-7 ug_import . . . . . . . . . . . . . . . . . 18-24
IMAN_ROOT Directory . . . . . . . 1-41-6 Methods
Index-2 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912
Index
key definitions . . . . . . . . . . . . . . 3-13 seed

Modify Access to a Query . . . . . . . . 7-13 Seed parts . . . . . . . . . . . . . 17-13
Modify Command Suppression Parts and Assemblies to be
Definitions . . . . . . . . . . . . . . . . . . 14-5 Imported . . . . . . . . . . . . . . . . . . . 18-4
Modify Single Object Protections . . 9-33 Person, User, Role and Group . . . . . . 2-3
Modify the Blazing Blades Preference Setting Hierarchy . . . . 14-14
Preferences . . . . . . . . . . . . . . . . 14-19 Preference Settings for NX
Manager . . . . . . . . . . . . . . . . . . 17-35
N Preference Settings to Consider . . 14-15
Preference Settings to Consider for NX
Named ACLs . . . . . . . . . . . . . . . . . 9-12 Manager . . . . . . . . . . . . . . . . . . 17-36
Naming Rules . . . . . . . . . . . . . . . . 13-8 Preferences
establishing . . . . . . . . . . . . . . . . 13-9 IMAN
NX / TcEng Terms . . . . . . . . . . . . . 17-3 IMAN_ugmaster_name_separator . . 17-36
NX Customer Default Files for NX Prepare to Import Unigraphics
Manager . . . . . . . . . . . . . . . . . . 17-38 Data . . . . . . . . . . . . . . . . . . . . . . 18-6
NX Manager Import Scenarios . . . 18-17 primary type . . . . . . . . . . . . . . . . . 3-13
Process Model Design for Change
O Management
EC Folder Structure . . . . . . . . . 12-16
Object-based Protections . . . . . . . . . 9-4 Process Templates for NX Related
Objects Data . . . . . . . . . . . . . . . . . . . . . 17-32
Workspace Process Terms and Functionality . . 11-5
manifestations . . . . . . . . . . 17-14 Product Structure Editor (PSE)
specifications . . . . . . . . . . . 17-14 revision rule criteria . . . . . . 8-148-15
Occurrence Note Types . . . . . . . . . . . 6-6 Properties
Organization key definitions . . . . . . . . . . . . . . 3-13
tips in creating . . . . . . . . . . . . . . 2-17 property . . . . . . . . . . . . . . . . . . . . 3-13
Organize the NX Seed Parts Property Rules . . . . . . . . . . . . . . . 13-19
Folder . . . . . . . . . . . . . . . . . . . . 17-16 establishing . . . . . . . . . . . . . . . 13-20
Overview of Importing Files . . . . . . 15-3 Protection of objects . . . . . . . . . . . 17-10
Overview of TcEng Workflow . . . . . 11-3
Overview of ug_import
Capabilities . . . . . . . . . . . . . . . . 18-12 Q
Query
P Searching the database . . . . . . . . . 7-3
Quick Release Technique . . . . 16-3, 16-6
Part files
import
R
into folder other than
Newstuff . . . . . . . . . . . . 18-22 Releasing Previously Imported
lock . . . . . . . . . . . . . . . . . . . . . 17-10 Data . . . . . . . . . . . . . . . . . . . . . 18-49
Parts Result of Releasing Data with a
create from UG Process . . . . . . . . . . . . . . . . . . . . 11-6
what happens in TcEng . . . . 17-7 Review of the TcEng Process
revisions Model . . . . . . . . . . . . . . . . . . . . . . 11-4
what happens in TcEng . . . . 17-8 Revision rules

Index
PSE criteria . . . . . . . . . . . . 8-148-15 type . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Revision Rules Review . . . . . . . . . . . 8-7 Type Display Rules . . . . . . . . . . . . 13-3
Revision Rules Setup . . . . . . . . . . . 8-10 establishing . . . . . . . . . . . . . . . . 13-4
Rules-based Protections . . . . . . . . . . 9-3 Types
key definitions . . . . . . . . . . . . . . 3-13
Types of Engineering Changes
S
Change Types . . . . . . . . . . . . . . . 12-5
Schema Editor
Schema Editor Utility U
Create a Class . . . . . . . . . . . . 4-7
Delete a Class . . . . . . . . . . . . 4-8 ug_import
Schema Tree . . . . . . . . . . . . . . . . . . 4-6 associated files . . . . . . . . 18-34, 18-36
Search check import . . . . . . . . . . . . . . . 18-22
Searching the database . . . . . . . . . 7-3 command syntax . . . . . . . . . . . . 18-17
Searching the database . . . . . . . . . . 7-3 keywords . . . . . . . . . . . . . . . . . 18-17
Seed Part Preferences . . . . . . . . . 17-15 login keywords . . . . . . . . . . . . . 18-20
Seed Part Setup . . . . . . . . . . . . . . 17-13 specify part files . . . . . . . . . . . . 18-21
Seed parts . . . . . . . . . . . . . . . . . . 17-13 UGMASTER / UGPART
TcEng storage . . . . . . . . . . . . . . 17-13 Behavior . . . . . . . . . . . . . . . . . . . 17-11
Setting Object-based Exception Privilege Unigraphics Data Import
Data . . . . . . . . . . . . . . . . . . . . . . 9-31 introduction to . . . . . . . . . . . . . . 18-3
Setting the TcEng Classroom Units of Measure . . . . . . . . . . . . . . . 6-3
Environment . . . . . . . . . . . . . . . . 1-11 Units of Measure (UOM)
Some Useful Canned Handlers . . . . 11-28 definition of . . . . . . . . . . . . . . . . . 6-3
Status Types for Release Status . . . . 8-3 Use ug_import to Import the Seed
Storage of Associated Files . . . . . . . 17-9 Parts . . . . . . . . . . . . . . . . . . . . . 18-29
Structure Using (Directory) Search Files . . . 18-15
lock . . . . . . . . . . . . . . . . . . . . . 17-10 Using ACLs in a Process
Student Responsibilities . . . . . . . . . 14 Template . . . . . . . . . . . . . . . . . . . 11-36
Sub-type . . . . . . . . . . . . . . . . . . . . 3-13 Using Task Handlers in a Process
Template . . . . . . . . . . . . . . . . . . . 11-27
Utilities
T
database_verify . . . . . . . . . . . . . . C-2
TcEng Data Protections iman_sync . . . . . . . . . . . . . . . . . . C-2
TcEngi-Man Data Protections . . . . 9-3 make_user . . . . . . . . . . . . . . . . . 2-41
TcEng Environment Variables . . . . . 1-9 ps_rename_bvrs . . . . . . . . . . . . . . C-3
TcEng Install Directory Structures . . 1-4 setting the TcEng environment
IMAN_ROOT . . . . . . . . . . . . . 1-41-6 AA . . . . . . . . . . . . . . . . . . . . 1-10
TcEng Volumes step_export . . . . . . . . . . . . . . . . . . C-4
i-Man Volumes . . . . . . . . . . . . . . 2-24 step_import . . . . . . . . . . . . . . . . . C-4
Teamcenter Engineering Access Manager
i-Man Access Manager . . . . . . . . . 9-2 V
Tips in Creating your
Organization . . . . . . . . . . . . . . . . 2-17 Verify Revision Rule Preference
TR Change Notice Process . . . . . . 12-17 Settings . . . . . . . . . . . . . . . . . . . . 8-21
Two Usage Modes with Workflow . . 11-7 Viewing Data Privileges . . . . . . . . . . 9-5
Index-4 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912
Index
Volume management W
viewing detailed volume
information . . . . . . . . . . . . . . 2-31 What is a Change Object? . . . . . . . 12-4

Reference Chart Tear Outs
These tear out reference charts are provided for your convenience.
Teamcenter Engineering Application Administration Student Profile
Name ________________________________________________ Date _____________________

Employer _______________________________________________________________________
U.S. Citizen? Yes / No
When is your planned departure time? ________ am/pm
Please answer the following questions as honestly as you can. We are

concerned about providing training that meets your needs. If you have
any additional comments please write them on the back of this form.
1. Job title: _______________________________________________________________________
2. Current responsibilities: _________________________________________________________

________________________________________________________________________________
3. How long have you held these responsibilities? Years ______
4. How long have you been working with CAD/CAM & PDM systems? Years ______
5. What other PDM systems are you familiar with? __________________________________

________________________________________________________________________________
6. What other CAD/CAM systems are you familiar with? _____________________________

________________________________________________________________________________
7. Are you currently using TcEng _______ Version _______ Hours per week? ______
8. Are you currently using Unigraphics? _______ Version _______ Hours per week? ______
9. What are the primary uses of TcEng at your site? __________________________________

________________________________________________________________________________
10. What do you model in your Unigraphics part files (castings, assemblies, etc.)?
________________________________________________________________________________
________________________________________________________________________________
11. Please list other completed CAD/CAM or PDM courses and the provider including
Unigraphics CBT and CAST:
Course Provider
12. Please check the box that best describes your current skill level in the various
TcEng/Unigraphics disciplines listed below.
none novice intermediate advanced future
Unigraphics User
NX Manager User
TcEng User
TcEng System Admin
TcEng Application
Admin
TcEng Development
(ITK)
Additional Comments: _____________________________________________________

________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
________________________________________________________________________________
V9.1.2 Teamcenter Engineering Application Administration Course Agenda
Day 1 ______ Morning

Introduction Course Overview
Lesson 1 Teamcenter Engineering Environment
Lesson 2 User Organization
Lesson 3 Form Types and LOVs
Afternoon
Lesson 4 Item Data Types

Lesson 5 Dataset Types
Lesson 6 Product Structure Data Types
Afternoon
Lesson 7 Queries and Reports
Lesson 8 Status Types and Revision Rules

Lesson 9 Access Manager
Lesson 10 Projects
Afternoon
Lesson 11 Workflow Process Modeling

Lesson 12 Change Management
Lesson 13 Business Modeler
Afternoon
Lesson 14 Preferences and Options
Lesson 15 Importing Non-CAD data
Lesson 16 Status Imported Data

Lesson 17 Setup For Unigraphics Integration
Afternoon
Lesson 18 NX Manager Unigraphics Import and Release
Course Evaluation
You may instead complete this evaluation online at:
http://training.ugs.com/eval
The online evaluation will require you to enter a session ID for this class. This should be provided
by your instructor and noted here: Session ID __________________
Course Name___________________________________ Course #___________

Dates thru
Please share your opinion in all of the following sections with a check in the appropriate box:
SOMEWHAT
SOMEWHAT
STRONGLY
STRONGLY
DISAGREE
DISAGREE
DISAGREE
Instructor: R
AGREE
AGREE
AGREE
If there were 2 instructors, please evaluate the 2nd instructor with Xs
Instructor: T
1. clearly explained the course objectives
2. was knowledgeable about the subject
3. answered my questions appropriately
4. encouraged questions in class
5. was well spoken and a good communicator
6. was well prepared to deliver the course
7. made good use of the training time
8. conducted themselves professionally
9. used examples relevant to the course and audience
10. provided enough time to complete the exercises
11. used review and summary to emphasize important information
12. did all they could to help the class meet the course objectives
Comments on overall impression of instructor(s):

Overall impression of instructor(s) Poor Excellent
Suggestions for improvement of course delivery:
What you liked best about the course delivery:
Class Logistics:
1. The training facilities were comfortable, clean, and provided a good learning
environment
2. The computer equipment was reliable
3. The software performed properly
4. The overhead projection unit was clear and working properly
5. The registration and confirmation process was efficient
SEE BACK
Rev-9/10/04-glk
Course Evaluation
Course Name______________________________________ Course #__________
Dates thru
Please share your opinion for all of the following sections with a check in the appropriate box:
SOMEWHAT
SOMEWHAT
STRONGLY
STRONGLY
DISAGREE
DISAGREE
DISAGREE
AGREE
AGREE
AGREE
Material:
1. The training material supported the course and lesson objectives
2. The training material contained all topics needed to complete the projects
3. The training material provided clear and descriptive directions
4. The training material was easy to read and understand
5. The course flowed in a logical and meaningful manner
6. How appropriate was the length of the course relative to the material? Too short Too long Just right
Comments on Course and Material:
Overall impression of course Poor Excellent
Hotels: (We try to leverage this information to better accommodate our customers)
1. Name of the hotel Best hotel Ive stayed at
2. Was this hotel recommended during your registration process? YES NO
3. Problem? (brief description)
Student:
1. I met the prerequisites for the class (I had the skills I needed)
2. My objectives were consistent with the course objectives
3. I will be able to use the skills I have learned on my job
4. My expectations for this course were met
5. I am confident that with practice I will become proficient
Student Name (optional): Location/room
Please check this box if you would like your comments featured in our training publications.
Please check this box if you would like to receive more information on our other courses and services.
Thank you for your business.

We hope to continue to provide your training and personal development for the future!
Rev-9/10/04-btr

Teamcenter Admin

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Teamcenter Admin

Încărcat de

Drepturi de autor:

Formate disponibile

Teamcenter Engineering

Manual Product Publication

This edition obsoletes all previous editions.

2 Teamcenter Engineering Application Administration MT14350SG0912

MT14350SG0912 Teamcenter Engineering Application Administration 3

Teamcenter Engineering Environment . . . . . . . . . . . . . . . . . . . . . . 1-1

User Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

UGS, All Rights Reserved Teamcenter Engineering Application Administration 5

Activity: Interactively Create a Volume, Group and Role . . . . . . 2-32

Form Types and LOVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Item Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Dataset Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Product Structure Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912

PSView Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Queries and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Status Types and Revision Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Access Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

UGS, All Rights Reserved Teamcenter Engineering Application Administration 7

Project Creation, Administration and Control . . . . . . . . . . . . . . . 10-1

Workflow Process Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Change Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

8 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912

Review of Types of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Business Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Business Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Preferences and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Setting Preferences and Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2

UGS, All Rights Reserved Teamcenter Engineering Application Administration 9

Import Non-CAD Data into Teamcenter Engineering . . . . . . . . . . 15-1

Status Imported Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Setup for NX Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1

10 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912

NX Manager Import and Data Release . . . . . . . . . . . . . . . . . . . . . . 18-1

Student Helpful Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Teamcenter Engineering and NX Manager Environment

UGS, All Rights Reserved Teamcenter Engineering Application Administration 11

Teamcenter Engineering Notes and Utility Quick Reference . . . . C-1

12 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912

Building Group/User/Role Organization

Modeling Item Data, Form Data, and Dataset Data

Modeling Product Structure Data

Defining Statuses and Configuration Rules

Extending Query Tools and Creating Reports

Defining Access Rules

Creating Projects and Controlling Access to Project Data

Designing Workflow Templates and Modeling Change Management Data

Defining Naming, Action and Deep Copy Rules

Setting Site, Group, Role and User Preferences and Options

Importing Legacy Data

Configuring a Unigraphics Integration

UGS, All Rights Reserved Teamcenter Engineering Application Administration 13

Participate in hands-on work sessions with Teamcenter Engineering

Benefit from personal assistance of a EDS-certified instructor

Demonstrate best practices for implementing and using Teamcenter

Stay with the subject matter

Listen attentively and take notes

Practice on the job what you have learned

14 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350SG0912

How to Use This Manual

Activity: Login to Teamcenter Engineering

Choose the Organization icon.

Enter the UserID and Password assigned to you

The Step is intended to be an increment to complete the activity.