100% found this document useful (3 votes)

7K views642 pages

Team Center Engineering v10 Admin

UGS and Teamcenter are registered trademarks or trademarks of UGS Corp. Or its subsidiaries in the United States and in other countries. Java and all Java-based marks are trademarks or registered trademarks of sun microsystems, Inc. In the United States and other countries.

Uploaded by

Jason Meyers

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (3 votes)

7K views642 pages

Team Center Engineering v10 Admin

Uploaded by

Jason Meyers

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 642

Teamcenter Engineering Application Administration

Student Guide January 2006 MT14350 Version 10.0

Publication Number MT14350-SG-100

Manual History

Manual Product RevisionVersion A B C V9.0 V9.1.2 V10.0

Publication Date March 2004 September 2004 January 2006

This edition obsoletes all previous editions.

Software Copyright and Trademark Notices

2006 UGS Corp. All Rights Reserved. This software and related documentation are proprietary to UGS Corp. UGS and Teamcenter are registered trademarks or trademarks of UGS Corp. or its subsidiaries in the United States and in other countries. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All other trademarks or registered trademarks belong to their respective holders.

Contents

Manual History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 Software Copyright and Trademark Notices . . . . . . . . . . . . . . . . . . . . 2 Course Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Course Description . . . . Course Objectives . . . . . Key Benets . . . . . . . . . Participants . . . . . . . . . Student Responsibilities How to Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 11 12 12 12 13

The Teamcenter Engineering Environment . . . . . . . . . . . . . . . . . . . 1-1 Teamcenter Engineering Interfaces . . . . . . . . . . . . . . . . . . . . Teamcenter Engineering Installation Directories . . . . . . . . . . Teamcenter Engineering Rich Client . . . . . . . . . . . . . . . . Teamcenter Engineering Base Installation (IMAN_ROOT) Database Conguration Settings Directory (IMAN_DATA) Teamcenter Engineering Environment Variables . . . . . . . . . . Setting the Teamcenter Engineering Environment . . . . . . . . Setting the Classroom Teamcenter Engineering Environment Activity: Get Acquainted with your TcEng Installation . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 . 1-3 . 1-4 . 1-5 . 1-6 . 1-7 . 1-8 . 1-9 1-10 1-12

User Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 Person, User, Role and Group . . . . . . . . . . . . . . . . The infodba Account and its Privileges . . . . . . . . . System Administration Accounts . . . . . . . . . . . . . Creating an Account . . . . . . . . . . . . . . . . . . . . . . . Creating a Role . . . . . . . . . . . . . . . . . . . . . . . . Creating a Group . . . . . . . . . . . . . . . . . . . . . . Creating a Sub-Group . . . . . . . . . . . . . . . . . . . Creating a Person . . . . . . . . . . . . . . . . . . . . . . Creating a User . . . . . . . . . . . . . . . . . . . . . . . . Tips in Creating your Organization . . . . . . . . . . . . Activity: Add a User to the dba Group . . . . . . . Activity: Interactively Create a Group and Role Teamcenter Engineering Volumes . . . . . . . . . . . . . Creating a Volume . . . . . . . . . . . . . . . . . . . . . .
UGS, All Rights Reserved

. . . . . . . . . . . . . .

. 2-2 . 2-5 . 2-6 . 2-7 . 2-8 . 2-9 2-10 2-12 2-13 2-16 2-18 2-23 2-28 2-31
3

Teamcenter Engineering Application Administration

Contents

Activity: Interactively Create a Volume . . . . . . . . . . . . . . . Steps Required to Enable Volume Access through FMS . . . Creating Accounts with the make_user Utility . . . . . . . . . . . . Class Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity: Create User, Group, Role using make_user . . . . . Activity: Create Organization using a script . . . . . . . . . . . Optional Activity: Create Hierarchical Group Organization Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . .

2-36 2-38 2-39 2-44 2-45 2-46 2-50 2-52

Form Types and LOVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 Form Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity: Automatic Form using Form Type Wizard . . . . . . . Activity: Create Automatic Form using Form Type Wizard . . Classes, Types and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . Optional Activity: Form Storage Class Types and Properties Lists of Values (LOV) for Form data . . . . . . . . . . . . . . . . . . . . . Activity: Create LOV for ChangeReason property . . . . . . . . Activity: Create Hierarchy of LOVs for ChargeCode property Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2 . 3-7 3-13 3-14 3-16 3-18 3-20 3-25 3-31

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

Dataset Types and Importing Non-CAD Data . . . . . . . . . . . . . . . . . 5-1 Dataset Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Dataset Creation/Modication Process . . . . . . . . . . . . . . . . . . . . . Creating Dataset Types and Tools . . . . . . . . . . . . . . . . . . . . . . . . . Activity: Dataset Type Using the Wizard . . . . . . . . . . . . . . . . . Activity: Creating Dataset Types Using the make_datasettype utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity: Creating Dataset Types Using the Standard Method . Importing Non-CAD Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Files Interactively . . . . . . . . . . . . . . . . . . . . . . . . . . Importing Files Using the import_le Utility . . . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 5-3 5-5 5-6

5-10 5-12 5-19 5-20 5-26 5-31

Product Structure Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 Units of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Contents

Occurrence Note Types . . . . . . . . . . . . . . . . . Activity: Creating Units of Measure . . . . Activity: Creating Occurrence Note Types PSView Types . . . . . . . . . . . . . . . . . . . . . . . . Activity: Creating PSView Types . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . .

. 6-4 . 6-6 . 6-7 . 6-9 6-11 6-12

Creating and Modifying Preferences . . . . . . . . . . . . . . . . . . . . . . . . 7-1 Preferences . . . . . . . . . . . . . . . . . . . . . Important Preferences to Consider . . . Creating and Modifying Preferences . . Activity: Modify a Site Preference . Activity: Create a User Preference . Activity: Create a Group Preference The preference_manager utility . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 . 7-3 . 7-4 . 7-5 . 7-8 7-12 7-17 7-18

Queries and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1 Dening Saved Queries . . . . . . . . . . . . . . . . . . . . . . . . Activity: Create a Query that Finds Home Folders . Query Access to Other Users . . . . . . . . . . . . . . . . . . . . Activity: Modify Access of the Find Homes Query . Activity: Custom Item Type Query . . . . . . . . . . . . Importing/Exporting Queries . . . . . . . . . . . . . . . . . . . Activity: Import a query . . . . . . . . . . . . . . . . . . . . Creating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . Activity: Create a Report using the EndItem query Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 . 8-7 8-12 8-14 8-17 8-25 8-26 8-28 8-30 8-41

Status Types and Revision Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Status Types for Release Status . . . . . . . . . . . . . . . . Activity: Create Status Types . . . . . . . . . . . . . . . Revision Rules Review . . . . . . . . . . . . . . . . . . . . . . . Revision Rules Setup . . . . . . . . . . . . . . . . . . . . . . . . Activity: Create Revision Rules . . . . . . . . . . . . . . Activity: Verify Revision Rule Preference Settings Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2 . 9-5 . 9-6 . 9-8 9-14 9-19 9-21

Access Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1 Teamcenter Engineering Data Protections . . . . Viewing Data Privileges . . . . . . . . . . . . . . . . . Activity: View Default Protections . . . . . . . Setting Object Based Exception Privilege Data Activity: Modify Single Object Protections . How Rules-Based Protections Work . . . . . . . . .
UGS, All Rights Reserved

. . . . . .

. 10-2 . 10-4 . 10-6 . 10-9 10-10 10-13

MT14350-SG-100

Contents

Activity: Import the 1600 Wheel Assembly . . . . . . . . . . Import a Non-Master Drawing File . . . . . . . . . . . . . . . . . . . Activity: Import the 1250 Axle Drawing . . . . . . . . . . . . . Import Files Associated to a (Master) Part File . . . . . . . . . . Activity: Import the 1250 Axle Associated Files . . . . . . . Import Files Associated to the DWG (Non-Master) Part File Activity: Import the Axle Drawing Associated Files . . . . Import Files Using a Full Map File . . . . . . . . . . . . . . . . . . . Activity: Import 2105 Frame Assy with Mapping File . . Importing Non-CAD Files into an Item . . . . . . . . . . . . . . . . Activity: Import the Heat Treat Text File . . . . . . . . . . . . Releasing Previously Imported NX Data . . . . . . . . . . . . . . . Activity: Release the 2111 Item Revision . . . . . . . . . . . . Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . .

16-29 16-30 16-31 16-33 16-35 16-36 16-37 16-38 16-42 16-44 16-45 16-46 16-47 16-49

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

Course Overview
Course Description
Teamcenter Application Administration addresses setup of the Teamcenter Engineering environment through realistic data and process implementation scenarios. You will learn how to dene business data and process models in a Teamcenter Engineering database. This course illustrates a best practice process for dening a companys data and process models in Teamcenter Engineering. It also illustrates managing the Teamcenter Engineering environment and importing legacy data into Teamcenter Engineering

Course Objectives
Overview of Teamcenter Engineering System Environment Build Group/User/Role Organization Model Item Data, Form Data, and Dataset Data Model Product Structure Data Dene Statuses and Conguration Rules Extend Query Tools and Create Reports Dene Access Rules Create Projects and Control Access to Project Data Design Workow Templates and Model Change Management Data Dene Type Display, Naming, Extension, Property, Compound Property and Deep Copy Rules Set Site, Group, Role and User Preferences and Options Congure an NX Integration Import Legacy Data
UGS, All Rights Reserved Teamcenter Engineering Application Administration 11

Key Benets

Key Benets
Increase productivity by learning through realistic projects. Participate in hands-on work sessions with Teamcenter Engineering and NX Integration Benet from personal assistance of a UGS-certied instructor Demonstrate best practices for implementing and using Teamcenter Engineering

Participants
Anyone responsible for dening, conguring 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

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 benet, 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

Lesson

The Teamcenter Engineering Environment

Purpose The purpose of this lesson is to acquaint you with some important parts of 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 congure 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

The Teamcenter Engineering Environment

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. Rich Client The main Rich Client interface is for the person who deals primarily with Conguration Management, Workow, Change Management, and Product Structure creation and maintenance. Start-up scripts:
Windows: Unix: portal.bat start_portal

NX Manager NX Manager 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 Rich Client interface with limited Workow, Change Management, and Product Structure capabilities. Start-up scripts:
Windows: Unix: ugmanager_portal.bat start_ugmanager_portal

Thin Client

The Thin Client is intended for those users who will be mostly viewing and reviewing. There are limited signoff and application access capabilities.

1-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

The Teamcenter Engineering Environment

gs_info directory

The IMAN_DATA directory also contains other les maintained on the operating system and tied to a particular database. More explanation of the les and sub-directories in the IMAN_DATA directory will be discussed as the course progresses.

1-6

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

The Teamcenter Engineering Environment

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 le: iman_prolevars (Unix) or iman_prolevars.bat (Windows). The Unix version of this script can be executed directly by Bourne or Korn shells.

The following environment variables must be set before using iman_prolevars. 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. Directory containing Teamcenter Engineering data les. This variable is set during Teamcenter Engineering installation and added to IMAN_DATA/iman_prolevars.

IMAN_DATA

The following are some of the environment variables set with iman_prolevars. IMAN_BIN ORACLE_SERVER ORACLE_SID IMAN_DB_CONNECT Location of the Teamcenter Engineering utilities. Oracle server network node. Unique name of Oracle database instance associated with IMAN_DATA. The userid and password the Teamcenter Engineering software uses when it interacts with the Oracle software.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

1-7

The Teamcenter Engineering Environment

Setting the Teamcenter Engineering Environment

The command line interface utilities documented in this class run from the command line inside operating system command shells. 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 congured 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 specied 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 Shell C Shell

IMAN_ROOT=/usr/tceng2005; export IMAN_ROOT IMAN_DATA=/usr/tceng2005/imandata; export IMAN_DATA . $IMAN_DATA/iman_profilevars

setenv IMAN_ROOT /usr/tceng2005 setenv IMAN_DATA /usr/tceng2005/imandata source $IMAN_DATA/iman_cshvars set IMAN_ROOT=d:\tceng2005 set IMAN_DATA=d:\tceng2005\imandata call %IMAN_DATA%\iman_profilevars

Windows

1-8

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

The Teamcenter Engineering Environment

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_prolevars inside env-sitea.
IMAN_BIN=/usr/tceng2005/bin IMAN_DATA=/disk1/imandata <- set by env_sitea IMAN_DB_CONNECT=imandev1:tbwiabd@devli IMAN_HELP_FILE=/usr/tceng2005/help/imanhelp.hlp IMAN_INCLUDE=/usr/tceng2005/include IMAN_LANGUAGE=/usr/tceng2005/lang IMAN_LIBRARY=/usr/tceng2005/lib IMAN_LOG=/disk1/imandata/log_sltrora_devli IMAN_ONLINE_HELP=/usr/tceng2005/help/imanhelp/imanhelp.ksh IMAN_PRINTER=/usr/bin/lp IMAN_ROOT=/usr/tceng2005 <- set by env_sitea ORACLE_SERVER=sltrora ORACLE_SID=devli POM_SCHEMA=/disk1/imandata/pom_schema_sltrora_devli POM_TRANSMIT_DIR=/usr/tceng2005/pom_transmit PATH=/usr/tceng2005/bin:/usr/tceng2005/bin: /disk1/imandata/local/bin:/usr/eds130/bin/ SHLIB_PATH=/usr/tceng2005/lib/CC:/usr/tceng2005/lib/oracle: /usr/tceng2005/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

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

1-9

The Teamcenter Engineering Environment

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: Step 2: Login to your workstation. 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: Windows: env | grep IMAN set iman

Notice that there are no Teamcenter Engineering environment variables dened. Close the command prompt window. Set the Teamcenter Engineering environment variables for this class. Unix: Windows: Type . env-sitea in current window Double-click env-sitea.bat

The env-sitea script has been written specically 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: Windows: Step 3: env | grep IMAN set iman

Look at how the Teamcenter Engineering environment variables are set. Identify the location of the IMAN_DATA directory. View/list the les in the IMAN_DATA directory.

1-10

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

The Teamcenter Engineering Environment

Notice the iman_prolevars or iman_prolevars.bat le. Open the iman_prolevars le in a text editor. This le 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 ling. Step 4: Look at the Teamcenter Engineering install directories by using the IMAN_ROOT environment variable. Identify the location of IMAN_ROOT. View/list the les 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. make_user, install, import_le, 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

1-11

The Teamcenter Engineering Environment

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 congure a Teamcenter Engineering site. The process to prepare Teamcenter Engineering Environment for command line interface tools.

1-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Lesson

User Organization
Purpose The purpose of this lesson is to manage the User Organization in the Teamcenter Engineering database. Objectives Upon completion of this lesson, you will be able to: 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

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-1

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, Robert Green, who is employed at a Company. In the Company organization matrix, Robert Green primarily works in the high_performance product group, but he is also assigned to the standards group. Robert Green has many skills that he applies appropriately while working in her assigned groups with roles: Engineering Manager, Design Engineer, Standards Engineer.

Robert Green 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 individuals who work at your site. A Person contains properties such as Person Name, Street Address, and Employee Number. Each Person Name must be unique. What is a User? The User is a Person with an account know to the Teamcenter Engineering system. One person can have several user accounts in Teamcenter Engineering. The Teamcenter Engineering implementation of user is completely separate from any OS user account. Each user must belong to a group. Person
Green,Robert 10824 Elm Street Wheeling, Il 60021

Person
Green,Robert 10824 Elm Street Wheeling, Il 60021 Organization: Company BB Employee Number: 150 Email: [email protected]

User
green Default Group= high_performance

2-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

2-5

User Organization

System Administration Accounts

Person Green, Robert 10842 Elm Street Wheeling, Il 60021 User Green, Robert Default Group= high_performance

Group Member Green, Robert (green) Group=high_performance Role=Engineering Manager Role=Design Manager

Group Member Green, Robert (green) Group=standards Role=Standards Engineer

Group Member Green, Robert (green) Group=dba Role=DBA

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

DBA Role

2-6

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Creating an Account
If you are a new Teamcenter Engineering site, follow the recommended order. Create Organization Structure 1. Create role(s). 2. Create volume(s). 3. Enable FMS Control of new volumes. 4. Create group(s) and sub-groups. Create Persons and Users next as they start using TcEng 1. Create person denition(s). 2. Create user account(s) Independent Denitions Roles, Volumes, and Persons are independent denitions. Any of these can be created without consideration of the other denitions. Dependent Denitions Groups and Users are dependent denitions. To create the Group and User denitions, other denitions must exist as follows: Group denitions require a Role to be dened. Group denitions suggest a Volume to be dened. User account denitions require a Person denition. User account denitions require a Group denition.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-7

User Organization

Creating a Role
By default, the DBA role is dened 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 eld. Choose Create.

The Role name can be up to 32 characters and the Description can be up to 240 characters. There are some out-of-the-box roles dened to support Teamcenter Engineering Projects. Do not delete these roles from the database under any circumstances. Teamcenter Engineering will not function properly without this group.

2-8

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

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-15

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 eld blank. This will ensure that project data les are stored in a central location (for example, the group volume). Otherwise, project data les 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 dene appropriate roles within those groups before considering which users should be assigned to those roles (populating a group with members).

2-16

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

Step 3:

Create a User. Double-click on Users in the bottom section of the Organization window and the Users are displayed.

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 This is only intended for use in this class. Previously created scripts expect the username and password to be the same.. Select the Default Group icon. In most cases, User ID, OS Name, and Password are the same, but may be different if desired.

2-20

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 specied, therefore, les 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 (in addition to infodba).

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-21

User Organization

Step 4:

Exit Teamcenter Engineering. Choose FileExit.

Choose Yes to the "Is it OK to Exit?" 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.

This concludes the activity.

2-22

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Activity: Interactively Create a Group and Role

In this activity, you will interactively create a group (standards), and role (Standards Engineer). You will also add your User to the new group with the new role and assume group administrator privilages. Step 1: Step 2: Verify that you are in the Organization application. Create a Role named Standards Engineer. Select Roles (bottom section of Organization window). Enter the following information: Role: Standards Engineer Description: <optional>

Choose Create. The new role is created.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-23

User Organization

Step 3:

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 pdm_vol listing.

Select the Standards Engineer role from the List of Dened Roles, then choose .

The role is added to the List of Selected Roles.

2-24

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Choose Create. The standards group is created.

Step 4:

Add your User to the standards group. Expand the standards group in the upper section of the Organization application. 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-25

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. Expand the Standards Engineer role under the standards group to see your User ID listed.

Your database now has the standards group with you as a user.

2-26

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Step 5:

Assume the responsibilities of Group Administrator for the standards group. Expand the standards group in the upper section of the Organization application.

Expand the Standards Engineer role and select Green, Robert.

Select the Group Administrator button in Group Member Settings.

Choose

to save the change.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-27

User Organization

Teamcenter Engineering Volumes

Teamcenter Engineering employs FMS (File Management System) to provide le storage, caching, distribution, and the access system to manage uploading and downloading le data between clients and volumes. It works in conjunction with TCFS (Teamcenter File Services), which provides a variety of volume-related services. Volumes are directories that are created and used by Teamcenter Engineering to store les created while running integrated applications from Teamcenter Engineering. Volumes are also used to store other les created during a Teamcenter Engineering session. The database retains the information for the volume location and the le name in the volume. Users cannot directly access les 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 le, the new le is created within a Teamcenter Engineering volume. This allows the database to control the le and ensure that it will be there when it is needed. Files in a Teamcenter Engineering volume are never modied, they are always versioned. The distinction is that Teamcenter Engineering creates or deletes les but never modies a le in place (i.e., saves changes to an existing le). A Teamcenter Engineering volume is an operating system directory controlled by Teamcenter Engineering. Volumes are used to store les 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.

2-28

Teamcenter Engineering Application Administration

2-31

User Organization

Adding a New Volume to FMS Although Application Administrators are able to create data volumes, FMS is managed by a system administration level account. This dictates the need for new volume information to be manually added to the fmsmaster_fsc_id.xml le, which is read when the FMS services are started. When creating a new volume, a Organization application user will receive a warning message stating the new volume id and root path.

The line which displays the volume id denition may be selected and then copied to the OS clipboard, using the CTRL-C keyboard command. In an installation where the user account creating the volume is the same as the account that owns the FMS services, the line may be pasted directly into the fmsmaster_fsc_id.xml le. More often, as is the case in this classroom environment, the account that manages the FMS services is not a general user account. The process for adding a newly created volume to FMS control is covered in the Teamcenter Engineering Installation course. A more detailed explanation of the FMS system architecture and functions can also be found in the Installation CD Help les.

2-32

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Fail-Safe Volume(s) Each user will have a volume where les 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 les, the User Settings dialog (EditUser Setting...Session Settings), can be used to select a different volume (set up specically 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-33

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 les. Volume access can be revoked by rst selecting a user or group and the choosing the Revoke button. The example shown above applies to a typical installation where each group has a volume of their own.

2-34

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Monitoring Volume Disk Usage Selecting a Volume from the Organization List tree displays the Volume elds. The elds are used to create and manage Volume denitions.

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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-35

User Organization

Activity: Interactively Create a Volume

In this activity, you will interactively create a volume. Step 1: Create a Volume that will be used to demonstrate the process of creation and FMS Double-click on Volumes in the bottom section of the Organization application. Select pdm_vol. Modify the pdm_vol elds to reect the following: Volume Name: test_vol Node Name: (same as pdm_vol node name) Machine Type: (same as pdm_vol Machine Type) Change end of Path Name from pdm_vol to test_vol.

Choose Create. The new volume is created.

2-36

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Step 2:

Note the FMS Conguration Information warning. When you press Create, the system will respond with the warning similar to the one shown below

In order to gain access to the volume, you must use the system account which owns the FMS processes to edit the fmsmaster_fsc_id.xml le with the line of information provided in the warning. Select OK to close the warning. All user accounts in this classroom do not have the privileges necessary to edit the fmsmaster_fsc_id.xml le. This is typically a system administration function, since it may involve security, hardware and networking issues. Therefore, conguration of additional volumes must be a joint effort involving both system and application level support. Although we will not complete this process in the activity, the steps required to do so are listed at the end of this lesson for your reference. If you ignore or forget the FMS Conguration Information warning, you will be reminded when you attempt to save data to the new volume by this error message.

Step 3:

Exit Teamcenter Engineering. Choose FileExit. Choose Yes.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-37

User Organization

Steps Required to Enable Volume Access through FMS

1. Open the fmsmaster_fsc_id.xml le in Wordpad. 2. Create a new volume id line with the information copied from the FMS Conguration Information warning message. 3. Save the fmsmaster_fsc_id.xml le. 4. Choose StartSettingsControl Panel. Open the Administrative Tools window and select Services. Locate the Teamcenter FSC Service FSC_host_id service and Stop, then Restart the service. 5. The volume is now under FMS control. If the Teamcenter FSC Service does not start, or starts and then stops, there is either a problem with the edit you made or the wrong user account was used to perform the edit.

2-38

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 nd 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-39

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> -password=<password> -group=<group_name> -person=<person_name> -role=<role_name> -volume=<volume_name> -node=<node_name> -path=<path_name> -le=<le_name> New user that will be created. Password for the new user. Group that new user will be added to. Person associated with the new user. Role the new user will be assigned to. New volume to be created. Network node where the new volume will be located. Full path where the new volume will be located. After other arguments are processed; read le <le_name> to create users. Each record in the le contains: person|user|password|group|role|

If a password is not specied it will be the same as the user id. 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 specied 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 specied, then all of the groups that are created will be granted access to the volume. If the specied group already exists and does not have a default volume, then the volume will be designated as the groups default volume. The source code for the make_user utility is supplied with the Teamcenter Engineering product as the le make_user_main.cxx in IMAN_ROOT/sample/utilities. This code can be modied, compiled and linked to operate based on customer requirements. Creating Volumes with the make_user utility still requires that the appropriate user account enables recognition of the new volumes as described in the Activity: Interactively Create a Volume.

2-40

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 specic role.
make_user -person="Smith, John" -user=smith -group=design -role=engineer -v

The rst role specied 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

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-41

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 high_performance corrective_action Default Role Product_Engineer Product_Engineer

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

IMAN_BIN/make_user -user=green -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=green -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

2-42

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Using the make_user utility with the input le argument The input le (-le=) 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 le 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 le:

IMAN_BIN/make_user -file=supplier_users.txt

The le argument can not be used to create Volumes.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-43

User Organization

Teamcenter Engineering Application Administration

2-47

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.

2-48

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

User Organization

Step 5:

Assign the responsibilities of Group Administrator for the high performance group. Expand the high_performance group in the upper section of the Organization application.

Expand the Design Engineer role and select Select Group Administrator and Default Role in the Group Member Settings.

Choose

to save the change.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

2-49

User Organization

Optional Activity: Create Hierarchical Group Organization

Lesson

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 Upon completion of this lesson, you will be able to: Create Form Types Create Lists of Values (LOVs) including hierarchical LOVs

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

3-1

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 specically meant for handling small amounts of information in a xed format. Forms typically store their data in the Oracle database as opposed to a le on the volume.

3-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 specied 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 workow handler Form objects may be created automatically during a workow process by using the EPM-create-form action handler. Handlers for workow process will be discussed later on in this course.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

3-3

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 denition (JAVA) has been dened. Step 1: Create the Form Type. Start the Admin/Type application.

Select Form Type in the Types tree.

Choose the

icon.

The Form Type Wizard dialog appears. Step 1 of the wizard is used to dene 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. 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

3-7

Form Types and LOVs

Choose Next. Step 2 of the wizard is used to dene 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.

MT14350-SG-100

Form Types and LOVs

Activity: Create Automatic Form using Form Type Wizard

Using the Form Type Wizard, create and test the Form Type described below.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

3-13

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.

3-14

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Form Types and LOVs

Key Denitions The following terms are used to describe classes, types and properties. Class A class is the denition of an object implemented in the Teamcenter Engineering data model. A class has a set of attributes, some of which are inherited from parent classes and some of which are dened directly for the class. An attribute is a persistent piece of information that characterizes all objects in the same class. A type is the specialization of a Teamcenter Engineering class based on properties and behavior 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 dened by using the install_types utility. 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. 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.

Attribute Type Primary Type

Suggestive

Range

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

3-19

Form Types and LOVs

Activity: Create LOV for ChangeReason property

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. Start Teamcenter Engineering. 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: Description: LOV Type: Usage: Choose TR Change Reason ChangeReason on Change Description Form LisitOfValuesString Exhaustive (on the far right) to add an entry line.

3-20

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Form Types and LOVs

In the Value eld, enter Product Improvement

Continue to add the following entries: Marketing Request Field Request Cost Reduction Safety Engineering Error

If wanted, values can be moved up or down in the list by selecting the line and choosing the proper arrow.

Choose Step 3:

to create the LOV.

Attach the LOV to the ChangeReason Property. Notice, that after creating the LOV, it shows No Attachment at the bottom of the window.

Choose No Attachment.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 3-21

Activity: Create Hierarchy of LOVs for ChargeCode property

In this activity, you will create a hierarchy of List of Values (LOVs) for the ChargeCode Property of the Change Description Form.

Step 1:

Create the rst level LOV. Return to the Admin/List of Values application. Enter the following LOV parameters: Name: Description: LOV Type: Usage: Choose TR Charge Code L1 Level 1 ChargeCode Reason on Change Description Form LisitOfValuesString Exhaustive (on the far right) three times to add three lines.

In the Value elds, enter the following values. A10 A20 A30

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

3-25

3-28

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Form Types and LOVs

Double-click TR Charge Code L2 in the list.

Notice, that the L2 LOV has been added as a level below the L1 LOV.

Repeat the process until the A20 and A30 sub-levels have be created.

When nished, choose Step 5: Test the hierarchical LOV.

Return to the Teamcenter/My Navigator application. In your Home folder, double-click on the Change Description Test form.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

3-29

Form Types and LOVs

Notice, that the ChargeCode eld now displays a different LOV icon.

Select the new LOV and expand the rst level options.

Options from the second level are selected by double-clicking. Choose Cancel to close the form.

This concludes the activity.

3-30

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Form Types and LOVs

Summary
In this lesson you: Created Form Types Created Lists of Values (LOV) including hierarchical LOVs

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

3-31

Lesson

Item Data Types

Purpose The purpose of this lesson is to prepare the Teamcenter Engineering database with Types for Items. Objectives Upon completion of this lesson, you will be able to: Create Item Types Create POM Schema Classes for Form Data Add Custom Attributes for Item Creation

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-1

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 Specication, 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 dened 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 dened 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.
UGS, All Rights Reserved MT14350-SG-100

4-2

Teamcenter Engineering Application Administration

Item Data Types

Extending Item Types The Type application within the Portal Admin program group can be used to dene 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 nd 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 congured 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 denitions.

In the example below, a new Type of Item (EndItem) has been dened so that the customer can dene customer specic 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)

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-3

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 Type in the Types list.

Enter EndItem in the Item type name eld. Choose Create. The new Item type is listed in the Item Type node of the Types list.

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: Step 2: Start the Admin/Schema Editor application. 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 toggled on. Choose Next.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-9

Item Data Types

For Step 2, enter TREndItemMaster for Sub Class Name. Spaces cannot be used in Class names. Choose Next. For Step 3, dene the following Attributes for the Class. Unless otherwise specied, leave the other parameters at their default values. Name: Type: Name: Type: Type: Type: Customer String Shipped Logical PartType String

When nished dening attributes, choose Next.

Item Data Types

Select Yes to create another Sub class, then choose Next.

For Step 2, enter TREndItemRevMaster for Sub Class Name, then choose Next. Ensure that you have entered the name correctly with Rev.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-11

Item Data Types

For Step 3, dene the following Attributes for the Class. Unless otherwise specied, leave the other parameters at their default values Name: Type: Name: Type: Name: Type: Contract String Weight Double DateWeighed Date

When nished dening attributes, choose Next.

For Step 4, choose No, then choose Next.

4-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Item Data Types

To complete Step 4, choose Yes.

Choose OK.

For Step 5, choose No, then choose Finish.

Choose Close on the Schema Editor Wizard dialog.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-13

Item Data Types

Browse the Class tree and verify the creation of the two classes.

Step 3:

Modify the Form Type Denitions. Go to the Admin/Type application. Expand the Form Type node. Select EndItem Master in the Form types list. Change the POM class setting to TREndItemMaster.

Choose Modify.

4-14

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Item Data Types

Select EndItem Revision Master in the Form types list. Change the POM class setting to TREndItemRevMaster.

Choose Modify. Close the Admin/Type application. Step 4: Test the EndItem Item type usage. Start the Teamcenter/My Navigator application. Select your Home folder. Choose FileNewItem... Choose Select Type to display the list of Item Types.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-15

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: Rev: Name: EI001 001 EndItem Test

Choose Finish. Choose Close on the New Item window. Expand the Item and ItemRevision objects.

4-16

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 activate the windows.

In a subsequent activity, you will use the Item Type Wizard to customize the New Item window so that end-users can provide Master form values during the creation of new Items.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-17

Item Data Types

Activity: LOV for Item Type Form

In this activity, you will create and attach two exhaustive LOVs for the Customer and PartType elds of the EndItem Master form. EndItem Master Form:

Before LOV:

After LOV:

You may want to refer to the Create LOV for ChangeReason property activity in the previous lesson.

4-18

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Item Data Types

Step 1:

Create and Attach LOV for Customer Attribute using LOV Application Enter the values in the tables below as shown. LOV parameters: Name: LOV Type: Usage: Values: TR Customers ListOfValuesString Exhaustive Customer Customer Customer Customer Customer A B C D E

Attached to:

Customer property of TREndItemMaster type

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-19

Item Data Types

Step 2:

Create and Attach LOV for PartType Attribute using LOV Application Name: LOV Type: Usage: Values: TR PartType ListOfValuesString Exhaustive Machining Casting Forging Plastic Composite Undecided PartType property of TREndItemMaster type

Attached to:

This concludes the activity.

4-20

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Item Data Types

Item Type Wizard

Following the denition of Item Types, and denition 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 and add default values for optional attributes.

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

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-21

Item Data Types

Activity: Customizing the New Item Dialog

In this activity, you will use the Item Wizard to add mandatory attributes and default values to the New Item dialog. Step 1: Step 2: Start the Admin/Type application. Set up custom attributes using the Item Wizard. Expand the Item Type node and select the EndItem type.

Select the

icon.

This invokes the Custom Attributes Wizard.

For Step 1, leave Add an attribute selected. Choose Next.

4-22

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Item Data Types

For Step 2, dene the following Custom Attributes:

When nished dening the attributes, choose Next. For Step 3, choose Yes to Save the Custom Attributes. Choose OK on the Add Custom Attribute(s) window. You are returned to Step 1 of the Wizard,

Choose Close to terminate the Wizard.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-23

4-26

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Item Data Types

Summary
In this lesson you: Created Item Types Created POM Classes for Form data Added attributes for the New Item dialog

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

4-27

Lesson

Dataset Types and Importing Non-CAD Data

Purpose The purpose of this lesson is to establish new Types for Dataset objects in your Teamcenter Engineering database environment and to import non-CAD le data into the Teamcenter Engineering environment.. Objectives Upon completion of this lesson, you will be able to: Create a new Dataset Type using the Dataset Type Wizard method Create or modify a Dataset Type using the standard method Create a new Dataset Type with the make_datasettype utility Import le data into Teamcenter Engineering using the Rich Client interface Import le data into Teamcenter Engineering using the import_le command line interface utility

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-1

Dataset Types and Importing Non-CAD Data

Dataset Objects
What is a Dataset? Datasets are objects used to manage le data associated with external software applications. They typically consist of a single application data le or logical groupings of application data les. There are numerous Types of datasets predened in TcEng. However, your site may need to add more Types to be able to manage your sites specic application data les and the viewing/editing software applications associated with these les.

What are Named References? Named References are Teamcenter Engineering objects that relate to a specic data le. A single dataset object may have one or more Named References. To view the Named References of a Dataset from Rich Client, select the Dataset object and choose ViewNamed References... from the Rich Client 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.

5-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Dataset Creation/Modication Process

The standard dataset creation/modication 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 les stored on a Teamcenter Engineering volume.

When a Rich Client 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 modication 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 dened in the Rich Client start-up script (portal.bat for Windows). Since initially there is no le associated with the dataset, Teamcenter Engineering will create a 0-size le and Export the le to the temporary OS directory. The format of the le (binary/text) and the extension of the le are as dened in the References part of the dataset type denition. Teamcenter Engineering executes the OS software application associated with the Dataset Types corresponding Teamcenter EngineeringTcEng Tool denition and passes the le to the application as a Parameter.

What the user sees: The OS software application executes with the 0-size le loaded. The user modies the le using the OS software application. When a modied le is saved (without terminating the application), the modied le is written back to the temporary OS directory overwriting the initial Exported 0-sized le. Each save performed (without terminating the application) continues to overwrite the le in the temporary directory without updating the data le stored in Teamcenter Engineering. The user terminates the OS software application.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

Dataset Types and Importing Non-CAD Data

For Step 3, provide the following Tool parameters: Name: Description: Format: MIME/Type: WizTextEditor <optional> ASCII text/plain

After entering the information, choose Next. For Step 4, choose Yes to dene the Tool, create the Dataset Type, add the Reference Type and add the Open Action. The Dataset Type Created message appears.

Choose OK.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-7

Dataset Types and Importing Non-CAD Data

Dataset Types and Importing Non-CAD Data

Select

to import a PDF le into the database.

Browse to the aa_class\dataset_types directory and select the NXCAM.pdf le to import.

Choose OK. Double-click on the Close the pdf. dataset to open it.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-11

Dataset Types and Importing Non-CAD Data

Activity: Creating Dataset Types Using the Standard Method

In this activity, you will dene a new Dataset Type and Tool using the Standard (Non-Wizard) approach. Step 1: Step 2: Go to the Admin/Type application. Create the Tool. Select Tool in the Types list.

Enter StdTextEditor for the Tool name. In the Formats section, enter ASCII in the Input eld, then choose . .

Enter ASCII in the Output eld, then choose Enter text/plain in the MIME/Type eld.

5-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

The window should look like the following:

Choose Create. Verify StdTextEditor appears in the Tool listing.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-13

Dataset Types and Importing Non-CAD Data

Step 3:

Create the Dataset Type and assign a Tool. Select Dataset Type in the Types list.

Enter StdText in the Dataset type name eld. In the Tools panel, select StdTextEditor in the List of dened tools. Choose to move the tool to the List of selected tools.

The window should look like the following:

Choose Create.

5-14

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Step 4:

Dene References for the Dataset Type. Locate and select StdText in the Dataset list.

Choose References The References window appears.

icon.

Choose

to dene a Reference.

In the row that was added, enter/verify the following parameters: Reference: File/Object: File: Format: Text File *.txt TEXT

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-15

Dataset Types and Importing Non-CAD Data

The window should look like the following:

Choose OK. Step 5: Dene Parameters (and Operations) for the Dataset Type. Choose Parameters in the window.

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 section, choose

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 dened during the previous step of this activity.

5-16

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

The window should look like the following:

Choose Create to nish dening 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. Go to the Teamcenter/My Navigator application. Select your Home folder and choose FileNewDataset...

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-17

Dataset Types and Importing Non-CAD Data

Use the More... link to locate and select the StdText type.

Enter test stdtext in the Name eld. Choose OK. Double-click on the dataset to open it in a text editor. Add some text. Save the le and exit the text editor. Open the dataset again to verify your edit to the le was indeed saved.

This concludes the activity.

5-18

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Importing Non-CAD Data

You can use Teamcenter Engineering to manage information created in the native environment. Importing data is the introduction of les or objects into Teamcenter Engineering. When you import les, a dataset is created with named references to a copy of the original les located in an Teamcenter Engineering volume. You may import les 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 les The import_le utility for batch importing les The ug_import utility, which will be discussed later, is recommended for importing NX part les. Key Points You can import more than one le into one dataset. You can use the Named References window to add additional les 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-19

Dataset Types and Importing Non-CAD Data

Importing Files Interactively

You can use either of the following methods for interactively importing les 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 le into it all at the same time. Import File into an existing Dataset This interactive File Import method allows you to import a le into a dataset that currently resides in the Teamcenter Engineering database.

5-20

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Activity: Create New Dataset and Import File In this activity, you will interactively import an ASCII le 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 le into Teamcenter Engineering. Select the Newstuff folder. Choose FileNewDataset... The New Dataset dialog is displayed. Enter Rubber Specs 1 in the Name eld. Change the Type to Text.

Select Import File. The Import File window is displayed.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-21

Dataset Types and Importing Non-CAD Data

Navigate to the ...aa_class/import_le directory.

Select the rubber_specs.txt le, then choose Import (or simply double-click on rubber_specs.txt). The Import File dialog disappears. Notice the rubber_specs.txt le name in the New Dataset window. Also, notice that the directory path is listed in the Import eld.

Choose OK. This completes the Import process. The text dataset should now be in your Newstuff folder.

5-22

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Step 3:

Review the imported le. 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 le 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 le.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-23

Dataset Types and Importing Non-CAD Data

Activity: Import File into Existing Dataset In this activity, you will interactively import a native le into an existing dataset in Teamcenter Engineering. Step 1: First, create an empty dataset. Select the Newstuff folder. Choose FileNewDataset... The New Dataset window is displayed. Enter Rubber Specs 2 in the Name eld. 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 le 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 Import... The Import File dialog is displayed.

5-24

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Navigate to the aa_class/import_le directory.

Select the rubber_specs.txt le. Choose the Import button. The Import File window disappears and the rubber_specs.txt le is now listed in the Named References window.

Choose Close. Open the rubber_specs.txt le. Review the le contents. Exit the editor application without making any changes.

This concludes the activity.

Dataset Types and Importing Non-CAD Data

Importing Files Using the import_le Utility

The import_le utility allows you to import les into the Teamcenter Engineering database according to a set of user-specied arguments. These arguments supply user identication information and dataset information to be associated with the imported le. The arguments may be specied on the command line for a single le import or in a command le for multiple les (bulk) import. Important Concepts This utility imports one le at a time into a dataset. You can subsequently add more les to a dataset. Use the import_le utility to import various les. The dataset is placed in the Newstuff folder. The import_le utility will set User and Group ownership on the newly created dataset.

In this case the import_le utility will be used to import a single ASCII text le. The following arguments are necessary.
IMAN_ROOT/bin/import_file -u=user-id -p=password -g=group -f=file-name -type=datasettype -d=dataset-name -ref=named-reference

The following example demonstrates using the import_le utility: 1. To import a single operating system le 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

5-26

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Arguments
-u =<username>

Species the user ID username. This is generally a user with administration privileges. If this argument is used without a value, the operating system user name is used. Species the password password. If used without a value, the system assumes a null value. If this argument is not used, the system assumes the user-name value to be the password. Species the group groupassociated with the user. If used without a value, the users default group is assumed. Import a single le filename into Teamcenter Engineering. The full path must be provided if the le does not reside in the current working directory. The -f and -i arguments are mutually exclusive. Imports multiple les into Teamcenter Engineering using a specied import le that contains the following information: -f=bike1.dat -d=my_bike1_dataset -type=UGPART -ref=UGPART -f=bike2.dat -d=my_bike2_dataset -type=UGPART -ref=UGPART The -f and -i arguments are mutually exclusive Runs utility in verbose mode. Displays maximum amount of information. Non-verbose sessions only display error messages. Log created datasets to <filename>. Otherwise -log=- can be used to print to your terminal window. Creates a log of items and datasets created. Type of named reference associated with the le. Each dataset type denes one or more Named References associated with it. Log created datasets to <filename>. Otherwise -log=- can be used to print to your terminal window.

-p=<password>

-g=<group>

-f=<filename>

-i=<filename>

-vb

-log=<filename>

-log -ref=names_reference

-log=<filename>

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-27

Dataset Types and Importing Non-CAD Data

-type=<datasettype>

Denes the dataset type in Teamcenter Engineering, for example, TEXT or UGPART datasets. Dataset you are importing the le to. Indicates that a dataset exists. Used when a dataset of the same name already exists. Species that a new dataset be added even if one with the same name exists. If it does exist, it is added to the same item folder. Species that the dataset should be added if it already exists and that this dataset type supports multiple instances of the same dataset. Species that the imported le be added as a named reference to the existing dataset. When this is done, a new dataset version that contains the additional imported named reference le is created. Species that a new dataset revision be created and referenced only to the imported le. Species the ItemID of the item containing the dataset that references the imported le. Species the item revision number and revision ID. Species behavior if the item already exists. Species that the dataset will not be added if the item already exists. Species that the dataset may be added if the item already exists. If the item exists, but the item revision does not, an item revision is created. Species a user-dened text description of an item that is created by the import function. If the import_le utility is creating a new revision of an existing item, this is the description of the item revision. Species the full path of the Teamcenter Engineering volume where the imported le is placed.

-d=<dataset_name> -de={n|e|a|r}

-item=<itemid>

-revision=<item-rev-num>

-ie={n|y} =n

-desc=<string>

-v=<volume-name>

To override the default object ownership, use the -u=<user> -p=<password> -g=<group> arguments. Make sure the le will be imported to the desired volume.

5-28

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Activity: Import File using import_le Utility In this activity, you will import other les into the Teamcenter Engineering database using the import_le utility. To do this activity you will execute a pre-written script that contains the import_le command. The import_le command used by the script is listed in the activity. Step 1: Import a le using the import_le utility If necessary, locate and modify the import_le.scr.bat (import_le.scr on Unix) script per the instructors instructions Open a terminal window with the Teamcenter Engineering environment set. Use the cd command to navigate to the aa_class directory. Type: cd import_le

Type: import_le.scr.bat (import_le.scr on Unix)

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-29

Dataset Types and Importing Non-CAD Data

The following command is used in the script to import the plastic_specs.txt le.
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 le. 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 le. Review the le. Exit the editor application without making any changes.

You have successfully imported the Plastic Specs le.

This concludes the activity.

5-30

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Dataset Types and Importing Non-CAD Data

Summary
In this lesson you: Created a Dataset Type using the Dataset Type Wizard Created a Dataset Type using the Standard Method Created a Dataset Types Using the make_datasettype utility Imported le data into Teamcenter Engineering using the Rich Client interface Imported le data into Teamcenter Engineering using the import_le command line interface utility

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

5-31

Lesson

Product Structure Data Types

Purpose The purpose of this lesson is to setup the Teamcenter Engineering database with Types that model Product Structure. Objectives Upon completion of this lesson, you will be able to: Create Item Unit of Measure Choices Create Specialized Note Types for Product Structure Occurrences Extend Types for PSView Objects

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

6-1

Product Structure Data 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 dene 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 eld of either the New Item (Revision) or Properties dialogs, the user is restricted to entering one of the pre-dened values. Choosing Unit of Measure from the Type application dialog displays the Units of Measure elds.

The Symbol eld is for the Unit of Measure symbol. The Name eld is for the Unit of Measure name. In PSE, if no specic quantity value is associated with Items, the default quantity is each (one component). In PSE, if UOM is anything other than <null>, the component will not open in NX.

6-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Product Structure Data Types

Units of Measure you will dene in your system: Units of Measure Symbol in oz Name inches 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

6-3

Product Structure Data Types

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 dened for the site. The Occurrence Note Types that are dened 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 elds.

Note type name This eld is for the Note Type name. Note description This eld 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 dene a list of values for the Note type. Default value: This allows you to dene 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.

6-4

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Product Structure Data Types

Note Types you will add to your system: SFCode This Note Type is used to apply a three digit numeric nish code in accordance with standard material processing requirement documentation. Note type name Note type description Default Value List of Values SFCode Standard nish code <none> <none>

Attach Value List? No

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 modied during assembly fabrication. IR is used to identify "Interchangeability Required" and IS is used to identify "Interchangeability Suggested" Note type name Note type description Default Value List of Values ICode Interchangeability code IR IR IS

Attach Value List? Yes

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

6-5

Product Structure Data Types

Activity: Creating Units of Measure

In this activity, you will create various Units of Measure. Step 1: Step 2: Start the Admin/Type application. Create two Units of Measure. Select in the Types Tree.

The Unit of Measure elds 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.

This concludes the activity.

6-6

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Product Structure Data Types

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 elds appear. For Note type name, enter: SFCode For Note description, enter: Standard nish 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 eld, enter IR, then choose .

In the Value eld, enter IS, then choose In the List of Values section, select IR. Choose Set Default.

Notice that IR appears (greyed out) in the Default value eld, just above the List of Values section.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 6-7

Product Structure Data Types

Choose Create. The new ICode and SFCode Note Types have been created in your database.

This concludes the activity.

6-8

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Product Structure Data Types

PSView Types
A PSView type is a denition 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 Type from the Type application dialog displays the PSView type name eld. The default conguration is a single PSView type dened for the entire site called view.

During the class, you will add two other PSView types. 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 dened. From that point forward, different groups and users could use the most appropriate PSView to model their data.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

6-9

Product Structure Data Types

Related Preferences In the EditOptions menu you may examine the default PSView type, which 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 EditOptions menu you may examine the default PSView type, which 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.

6-10

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Product Structure Data Types

Activity: Creating PSView Types

In this activity, you will create two new PSView types.

PSView Types you will dene: PSView Types PSView type name shipping engineering Purpose represents shipping view of product represents engineering view of product

Step 1:

Create a new PSView type for shipping. In the PSView type name eld, enter shipping. Choose Create.

Step 2:

Create a new PSView type for engineering. In the PSView type name eld, enter engineering. Choose Create.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

6-11

Product Structure Data Types

Summary
In this lesson you: Created Item Unit of Measures Created Occurrence Note Types Created PSView Types

6-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Lesson

Creating and Modifying Preferences

Purpose The purpose of this lesson is to modify and create User, Role, Group and Site preferences. Command Suppression of menu options will also be covered. Objectives Upon completion of this lesson, you will be able to: Set Preferences for Users, Roles, Groups and Sites

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

7-1

Creating and Modifying Preferences

Preferences
Preferences are environment variables stored in the Teamcenter Engineering database and read whenever a preference value is set or modied. Preferences allow you to congure many aspects of a session such as user login names and the columns displayed by default in a properties table. Basic system behavior such as business rules and security access are also determined by preferences. Preferences are managed using the Options window (EditOptions). This window is used to search for preferences, set preference values, create new preferences, and remove existing preferences. Preferences can also be manually modied in the tc_preferences.xml le, which is a le that is read automatically during installation and upgrades. It may be required to have different values for the same preferences for different Groups, Roles or even Users. To accommodate this requirement, Teamcenter Engineering allows for preferences to be set to handle each of these situations. The following list is shown in order of the precedence hierarchy used to resolve setting conicts in multiple locations, with 1 being the highest. 1. User preference. 2. Role preference. 3. Group preference. 4. Site preference. Preferences can also be imported or exported using the Options window (EditOptions).

7-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Creating and Modifying Preferences

Important Preferences to Consider

IMAN_cong_rule_users lists Teamcenter Engineering users that are allowed to create, delete, and modify preset conguration rules. It accepts one or more strings as value(s); each string must be a valid Teamcenter Engineering user. Preference(s): Default:
IMAN_config_rule_users unset

PSE_default_view_type 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): Default:
PSE_default_view_type view

AE_dataset_default_keep_limit 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): Default:
AE_dataset_default_keep_limit 3

IMAN_cong_rule_name sets default revision (conguration) 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. Preference(s): Default:
IMAN_config_rule_name Latest Working

IMAN_auto_login 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): Possible Values: Default:
IMAN_auto_login TRUE (Enable auto login)

FALSE

(Disable auto login

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

7-3

Creating and Modifying Preferences

Site Preferences Site preferences are those preferences that are used across an entire Teamcenter Engineering site. Only those users who belong to a dba group can create or change Site preferences. User Preferences User preferences are those preferences that can be created and set only for the individual user. A user preference takes the highest priority of the preferences, overriding any Site, Group or Role preferences. Group and Role Preferences Group and Role preferences are those preferences that can be assigned to be used only by a particular group or role. Only those users who have been assigned as the Group Administrator can create or modify group or role preferences. If a user is the Group Administrator, they will see the following additional (Scope) options when modifying or creating preferences.

7-4

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Creating and Modifying Preferences

Activity: Modify a Site Preference

In this activity, as a member of the dba group, you will modify existing Site preferences according to Product Structure View types created in the previous lesson. Step 1: Access the Modify the PSE_default_view_type preference. Continue using your dba account. Choose EditOptions. The Options window appears.

Choose Index (bottom left). Notice that the Options window changes to show the Preferences elds.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

7-5

Creating and Modifying Preferences

In the Search on preferences name eld, slowly enter PSE_. Notice that as you type, the system is dynamically searching for preferences and displaying them in the Preferences list. The window should now look like the following, which shows all the existing preferences that begin with PSE_.

Step 2:

Modify the PSE_default_view_type preference. Select the PSE_default_view_type preference from the list and see that the elds are populated with the settings for the PSE_default_view_type preference.

7-6

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Creating and Modifying Preferences

Notice the following key information. 1. The indication whether the preference is Site, User, Role or Group. 2. The current value of the preference. 3. The Modify and Delete options.

Change the value from view to engineering. Choose Modify. Choose Cancel to close the Options window. The PSE_default_view_type Site preference has now been revised. Now, when creating BOMviews, all users will default to the engineering view.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

7-7

Creating and Modifying Preferences

Activity: Create a User Preference

In this activity, as a regular user, you will create a User preference for the default view type, which will take precedence over the Site preference set in the previous activity. Step 1: Change to a user account. Log out of Teamcenter Engineering and your dba account. Log back into Teamcenter Engineering/My Navigator using the balltr account (password=balltr). Notice that for the balltr account, the default group is corrective_action and the default role is Planner.

Step 2:

Validate the Site preference created in the previous activity. Select the Home folder. Choose FileNewItem. In the New Item window, make sure Item is selected, then choose Next. Enter the following: ItemID = pref-1 Rev = A Name = test Choose Finish to create the Item, then Close the New Item window. Expand the pref-1 Item and select the ItemRevision.

Choose FileNewBOMView Revision.

Creating and Modifying Preferences

Notice in the New BOMView Revision window, the default is set to engineering. This is because of the site preference that we set in the previous activity. Choose Cancel to close the New BOMView Revision window. Step 3: Create the user preference. Choose EditOptions. Choose Index. In the Search on preferences name eld, enter PSE_default. Notice that since you entered more information this time, there is only one preference showing in Preferences list. Select PSE_default_view_type in the preference list. Notice the value of engineering that was set by the dba account and that this is still a Site preference.

With PSE_default_view_type still selected, choose CTRL-C to copy the preference name.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

7-9

Creating and Modifying Preferences

Select New (bottom middle), click in the Name eld and choose CTRL-V to paste the preference name.

Make sure the Type is set to String and Multiple values is set to False. Enter shipping in the Values eld. Choose Create, but do not close the Preferences window. Step 4: View the results. In the Preferences window, choose Details (next to the New option). In the Search on preferences name eld, enter PSE_default. Notice that this time there are two preferences with the same name listed. One is the Site preference and one is the newly created User preference.

Select each of the preferences and notice the elds update to show their values and the type of preference (Site or User). Choose Cancel to close the Options/Preferences window.

7-10

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Creating and Modifying Preferences

Step 5:

Validate the new User preference. Log out and back into Teamcenter Engineering/My Navigator using the balltr account. Expand the pref-1 Item and select the ItemRevision.

Choose FileNewBOMView Revision.

Notice that this time, the default is set to shipping. This is because of the user preference that now takes precedence over the site preference that is set to engineering. Choose Cancel to close the New BOMView Revision window.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

7-11

Creating and Modifying Preferences

Activity: Create a Group Preference

In this activity, you will use the tracytr account to create a Group preference for the high_performance group. Step 1: Review the tracytr user account setup. The following is key information about the tracytr account. 1. The tracytr user is a member of the high_performance group with the role of Product Engineer. 2. The tracytr user is also a member of the corrective_action group and also with the roles of Design Engineer and Product Engineer. 3. The default group for tracytr is the high_performance group. 4. In the Organization lesson, tracytr was made the Group Administrator for the high_performance. Step 2: Change to the tracytr account. Log out and back into Teamcenter Engineering/My Navigator using the tracytr account. Notice that the default group is high_performance and the default role is Product Engineer.

Choose EditUser Setting. Change role to Design Engineer. Choose OK. Step 3: Create a test Item and check the site settings. Select the Home folder. Choose FileNewItem. In the New Item window, make sure Item is selected, then choose Next.

7-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Creating and Modifying Preferences

Enter the following: ItemID = pref-2 Rev = A Name = test Choose Finish to create the Item, then Close the New Item window. Expand the pref-2 Item and select the ItemRevision.

Choose FileNewBOMView Revision.

Notice in the New BOMView Revision window, the default is set to engineering. This is because of the site preference that was set previously. Choose Cancel to close the New BOMView Revision window. Step 4: Create the group preference. Choose EditOptions. Choose Index. In the Search on preferences name eld, enter PSE_default. Select PSE_default_view_type in the preference list.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

7-13

Creating and Modifying Preferences

Again, notice the default site preference value of engineering.

With PSE_default_view_type still selected, choose CTRL-C to copy the preference name. Select New (bottom middle), click in the Name eld and choose CTRL-V to paste the preference name. Notice, that since tracytr, using the Design Engineer role, is a Group Administrator, the Scope options are visible. The User option is the default with the Site option not available since tracytr is not a member of a dba group.

Set the Scope to Group. Make sure Type is set to String and Multiple values is set to False. Enter shipping in the Values eld. Choose Create, but do not close the Preferences window.

7-14

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Creating and Modifying Preferences

Step 5:

View the results. In the Preferences window, choose Details (next to the New option). In the Search on preferences name eld, enter PSE_default. Notice that this time there are two preferences with the same name listed. One is the Site preference and one is the newly created Group preference.

Select each of the preferences and notice the elds update to show their values and the type of preference (Site or Group). Choose Cancel to close the Options/Preferences window. Step 6: Validate the new Group preference. Log out and back into Teamcenter Engineering/My Navigator using the tracytr account. Expand the pref-2 Item and select the ItemRevision.

Choose FileNewBOMView Revision.

Notice that this time, the default is set to shipping. This is because of the group preference that now takes precedence over the site preference that is set to engineering. Choose Cancel to close the New BOMView Revision window.
7-15

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

Creating and Modifying Preferences

Step 7:

Validate that the new Group preference does not affect the corrective_action group. Choose EditUser Setting. Change the Group to corrective_action, then choose OK. Select the pref-2/A ItemRevision.

Choose FileNewBOMView Revision.

Notice that the default is set back to the site preference value of engineering. Choose Cancel to close the New BOMView Revision window. Log out of Teamcenter Engineering.

This concludes the activity.

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 exible the search capabilities, the easier it is for you to quickly nd product information in the database. Teamcenter Engineering searching functions are found using the My Navigator application. in

The Teamcenter Engineering search feature is a exible 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.

8-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 dened 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 denes 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 dened 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 subject is covered later in the lesson. The Name and Type attributes are dened directly to the WorkspaceOject class. In a search that you will dene in an activity, all workspace objects with Name=Home and Type=Folder will be found.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-3

Queries and Reports

Query Builder Dialog The Admin/Query Builder application displays the Query Builder dialog. This dialog allows you to create, modify and delete queries.

8-4

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Elements of the Query Builder Dialog Element Name Description Description Name of the saved query that you selected from the Saved Query. Text eld where typically information about what the query does or other pertinent information is recorded. Imports a query denition from a XML le. Exports a query denition to a XML le. 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. This is a list of the various queries that come with the installation. LQ Query will be executed against the local database. UQ Indicates a query that is run by calling #USER_execute_saved_query that returns objects for display. KSQ Indicates a query that performs keyword searches using a search engine. RQ Query will be executed against the published objects in the ODS. UEQ Indicates a query that is run by calling #USER_query_execute that returns column-value triples for display. BOMSQ Indicates a query that generates BOM reports. eQ Indicates a query that is created through the eIntegrator application that is run against an external database.

Import Export Search Class icon

Query Types: Local Query User Query

Key Search Query Remote Query User Exit Query

BOM Structure Query eIntegrator Query

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-5

Queries and Reports

Element Attribute Selection Tree

Display Settings:

Class Attributes All Attributes Display Names Real Names Search Criteria Table Boolean Rules Attributes User Entry L10N Key

User Entry Name

Logical Operators Default Values Gain Precedence icon (up arrow) Lose Precedence icon (down arrow)

Description The attributes of the search class displays in the Attributes Selection tree. Depending on the type of display setting selected, this tree can display all inherited class attributes or just the class attributes. You will choose this icon to indicate how you want queries to display in the window. The Display Setting dialog displays with two options. Set Class Attributes to view only the class attributes. Set All Attributes to view all of the attributes. Set Display Names to display the presentation name of the attribute. Set Real Names to displays the actual attribute name as it appears in the database. Displays the search criteria that can be modied. The Boolean Rules (AND/OR) are used to combine clauses to create a custom query. The selected database attribute displays in the Attributes eld. Species the localization key used to look up user entry names. The localization keys-value pairs are dened in the qry_user_entry_names_locale.xml le. The value in this column can be modied. Displays the query eld 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 dened in the qry_user_entry_names_locale.xml le, 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 modied. Matching values can be: =, !=, <, >, IS_NULL, and IS_NOT_NULL Required when you do not specify the User Entry L10N Key when creating a query. Move search clauses up a row in the table to gain precedence. Moves search clauses down a row in the table to lose precedence.

8-6

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Activity: Create a Query that Finds Home Folders

In this activity, you will create a Query to nd all the Home folders dened in the database. This is a useful query for Teamcenter Engineering Administrators. The query will use the Folder class with the attributes Name and Type. Step 1: Step 2: Log into Teamcenter Engineering with your dba account. Begin creating the query. Start the Admin/Query Builder application. Enter Find Home Folders in the Name eld. Enter Find all Home folders in the database in the Description eld. Step 3: Choose the Query Search Class. Choose the Search Class selector. Type in the value Folder, then use Find select the Folder class. to locate and

Close the Class/Attribute Selection Pop-up window (

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-7

Queries and Reports

Step 4:

Build the Name clause for the query. Choose .

Set the Display Settings to All Attributes and Display Names.

Close the Display Settings window (

In Attribute Selection area, double-click Name to add a line in the Search Criteria section.

Enter Home in the Default Value eld, then press Enter.

8-8

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Step 5:

Build the Type clause and then save the query. In the Attribute Selection area, double-click on Type to add another line in the Search Criteria section. Select Folder from the drop-down list in the Default Value eld. The completed query should look like the following. Notice the AND conditional was used.

Choose Create to save the query.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-9

Queries and Reports

Step 6:

Test the query. Go to the Teamcenter/My Navigator application. Choose .

From the pull-down menu on the Search panel, choose RemainingFind Home Folders. The Search elds now show the Find Home Folders options.

Choose Execute Query. The Find Home Folders (1) tab appears with the results. Step 7: Add the Find Home Folders query to the Favorites List. At the bottom of the Search panel, choose Options... In the Favorite Options tab of the Options window, locate and check Find Home Folders.

Choose OK.

8-10

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Step 8:

Test the Favorites setting. Choose ViewRefresh Window. Open the Query selector.

The Find Home Folders query should be on the initial list.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-11

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 dene protections on a query form. Selecting a query from the list and choosing the Access... menu displays the Protection dialog for the query.

The Access Control List

8-12 Teamcenter Engineering Application Administration

can be used to modify the current access.

Queries and Reports

If you have Change access, the default access denition.

With these additional protections, the Find Home Folders query is only usable (and visible) by System Administrators.

This concludes the activity.

8-16

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Activity: Custom Item Type Query

In this activity, you will use the Query Builder application to create a specialized query for nding Items of Type EndItem.

Step 1:

Name and describe the query. Go to the Admin/Query Builder application. Choose Clear. Enter the following parameters: Name: Description: EndItem Search for EndItems

Step 2:

Choose the Query Search Class. Choose Enter Item, then choose Class. . to locate and select the Item

Close the Class Selection Pop-up window.

Queries and Reports

Step 3:

Build the Type clause for the query. Set the to show All Attributes.

Close the Display Settings dialog. In the Attribute Selection area, double-click on Type.

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.

8-18

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Choose EndItem in the Default Value eld.

Your Search Criteria form should appear as shown below.

Step 4:

Build the Part Number clause. In the Attribute Selection area, double-click on ID.

Type Part Number in the User Entry L10N Key eld, then press Enter.

Leave the Default Value eld empty. The end-user will provide the value for this clause during query execution.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-19

Queries and Reports

Step 5:

Build the Customer clause. In the Attribute Selection area, double-click on Item Masters.

In the Class Selection Dialog, select Form inside the Workspace Branch.

In the Attribute Selection area, doubleclick on Attributes.

8-20

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

In the Class Selection Dialog, locate and select TREndItemMaster.

Choose OK. Back in the Attributes listings, in the expanded Item Masters listing, expand the attributes node and double-click Customer to add the clause to the query.

Leave the Default Value eld empty.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-21

Queries and Reports

Step 6:

Build the Shipped clause. Again, in the Attribute Selection area, in the expanded Item Masters listing, double-click Shipped to add the clause to the query.

In the Default Value eld, enter TRUE (all caps), then press Enter. The query should look like the following.

Step 7:

Save the query. Choose the Create icon to save the query. Close the Admin/Query Builder application.

Step 8:

Test the query. Enter the Teamcenter/My Navigator application. If necessary, choose .

8-22

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Select the EndItem query from the Query selector list. The EndItem query elds will appear.

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

Step 9:

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. Choose ViewRefresh Window.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-23

Queries and Reports

Step 10: 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.

This concludes the activity.

8-24

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Importing/Exporting Queries
Query denitions 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 les, with the .xml extension. Importing a query denition is the most critical action. The XML les to be imported are rst parsed and veried before the data is allowed to be imported. Even if the query data is correctly formatted in the XML le, it may not be compatible with the local database schema. An incompatible import le will result in errors when you attempt to create the query denition. The following are key icons used in the Import dialog. Import le used to locate the query le in the OS directory structure. Verify used to validate the POM class matches existing classes in the database before importing.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-25

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. Go to the Admin/Query Builder application. If necessary, choose Step 2: Import a query. Choose the Import button. .

In the Import window, choose Import File. In the Read Query Denition window, navigate to the workow_designer folder in the aa_class directory.

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 nd 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 eld. Enter This report returns needed EndItem information in the Design Description eld. From the Saved Query pull-down list, select EndItem. At this point, the elds should look like the following.

8-30

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Choose Query Denition. This launches the Query Denition window, which is the same as the Query Builder window. This shows the denitions for the existing EndItem query.

Choose

to close the Query Denition window.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-31

Queries and Reports

Step 2:

Access and arrange the Property Format Finder window. Choose Property Format Finder. The Property Format Finder window appears.

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

8-32

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Stretch the window until all panels are easy to view.

Step 3:

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 eld. Change the Description to: This Pff denes 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, and choose .

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-33

Queries and Reports

Again, in the Search Criteria section, select the WorkspaceObject.last_mod_date listing and choose .

The window should now look like the following, with only ve listings in the Search Criteria section.

In the Property Selection panel, locate and double-click on Object.

8-34

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

The Report Dialog appears.

If the default_xml_template.xsl format le 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 Designer application.

This concludes the activity.

8-40

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Queries and Reports

Summary
In this lesson you: Created New Saved Queries Managed End-User Access to Queries Imported Queries Created Reports

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

8-41

Lesson

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 Upon completion of this lesson, you will be able to: Create Status Types Create Revision Rules

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-1

Status Types and Revision Rules

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 reect 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

Enter Released in the Status type name eld. 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 nished, the Status list should look like the following.

You now have more Status Types dened in the database.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-5

Status Types and Revision Rules

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 dened by a privileged user, and made available to certain other users. Item Revision conguration selects which one of the revisions of an Item is to be congured (i.e., meets the criteria in the Revision Rule). Revision Conguration Terms Imprecise Assembly Precise Assembly A single-level assembly that has Items as the components. The particular Revision is determined by the Revision Rule settings. A single-level assembly that has specic Item Revisions as the components. It is also subject to the Revision Rule, but the precisely specied Item Revision is congured by a Precise entry in a 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. 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 conguration. 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. An attribute assigned to an object after successfully going through a release. Item Revisions can be congured according to their status. The status can optionally contain effectivity data for revision conguration. 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.

Revision Rule

Rule Entry

Override List

Release Status

Working Revision

The Revision Rule must always be set to determine which revision to load into PSE. The variant and occurrence effectivity conguration rules are optional.
9-6 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Status Types and Revision Rules

Revision Rules Provided with Teamcenter Engineering Name Any Status, No Working Any Status; Working Description Selects the latest released revisions, no working revisions selected. Selects the latest released revisions, if none exist, then select working revisions. This is useful when you want to congure a released structure, but want to be aware of items that will become used in the structure, but are not released yet. Selects Precise references if they exist, and for Imprecise assemblies, selects the latest working revisions, if none exist, then latest released revisions. Selects the latest revisions according to the revision id, sorted alphanumerical, regardless of whether they are working or released. Selects the latest revisions according to the date they were created, regardless of whether they are working or released. Selects the precise references to specic item revisions in Precise assemblies. Selects the precise references to specic item revisions in Precise assemblies. If Imprecise assemblies are present, the latest revisions with any status are selected. Selects the precise references to specic item revisions in Precise assemblies. If Imprecise assemblies are present, only working revisions are selected. Selects only the latest working revisions owned 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 congure only the working data within their team. Selects only the latest working revisions owned 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 congure only their own working data. Selects the latest working revisions, if none exist, then select the latest released revisions.

Latest Working Latest by Alpha Rev Order Latest by Creation Date Precise Only Precise; Any Status Precise; Working Working (Curr Group); Any Status

Working (Curr User); Any Status

Working; Any Status

Revision Rules Added during the training class Name Released Description 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-7

Status Types and Revision Rules

Revision Rules Setup

Revision Rules are modied 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 window Use Create 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 Modify, 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 modied as required. This also allows the name of the Rule to be changed. Use Delete to remove a Revision Rule. This will then be removed from all users who had access to it.

9-8

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Status Types and Revision Rules

Creating Revision Rules This Create New Revision Rules window allows users to create Revision Rules. Default Access Manager Rules shipped with Teamcenter Engineering dene 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 modied.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-9

Status Types and Revision Rules

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 congured revision of the Item is successfully obtained. Once a revision is found that satises 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 specic via the following settings: Owning User - If an Owning User is specied within a Working entry, the latest revision owned by the specied User will be congured. The owning User can be also set to current, meaning that latest revision owned by the current Teamcenter Engineering User is congured. Owning Group - If an Owning Group is specied within a Working entry, the latest revision owned by the specied Group will be congured. The Owning Group can be also set to current, meaning that latest revision owned by the Users current Teamcenter Engineering Group is congured. More than one Working entry may be present within a Revision Rule. For example, a Rule might try to congure the current Users working revision, and if none is found, then congure the current groups instead. If a User changes their Group, they will need to re-apply the Revision Rule to congure the appropriate revisions for the Group they have changed to.

9-10

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Status Types and Revision Rules

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 congured, regardless of which status it is. Selected Status - The latest Item Revision with status of the selected type is congured. Allows you to congure a structure that only contains Item Revisions that have reached a specied 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 dened on the Release Status. Effective Unit No. - The latest Item Revision is selected according to unit numbers dened on the Release Status. Effective Dates/Units are dened 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 conures at a specic data or Today. This will prevent Users from setting a data (using Revision RuleSet Date) to congure 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 conguring Item Revision with status using Unit No Effectivity. This will prevent Users setting a unit number (using Revision RuleSet Unit No) to congure 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-11

Status Types and Revision Rules

Precise - A Precise entry is used to select the precisely specied 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 congured - 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 conguration. If you want to congure a structure that contains both Imprecise and Precise assemblies, and you want to congure 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 congure 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 congured.

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

9-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Status Types and Revision Rules

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 dened statuses. The latest item revision with either of the statuses is congured.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-13

Status Types and Revision Rules

Activity: Create Revision Rules

In this activity, you will create the Released Revision Rule. Step 1: Step 2: Start the Teamcenter/PSE application. 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.

Status Types and Revision Rules

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 Open by Name. The Open by Name dialog appears. Enter * in the Status Type eld, then choose

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 Open by Name again.

Double-click the Pre-Released status. Choose .

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-15

Status Types and Revision Rules

Step 5:

Add the Working entry. Select Working from the Entry Type selector.

To add the entry, choose

The window should look like the following.

9-16

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Status Types and Revision Rules

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 window.

Choose Close to dismiss the Revision Rules window.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-17

Status Types and Revision Rules

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 menu selection; EditOptionsIndex. 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 denes the type of BOM (Precise/Imprecise) users will create by default from PSE and Unigraphics
IMAN_BOM_Precision_Preference= Imprecise

9-18

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Status Types and Revision Rules

Activity: Verify Revision Rule Preference Settings

In this activity, you will verify Revision Rule preference settings. Step 1: Select EditOptionsfrom the pull-down menu as shown. Press Index on the Preferences form.

Step 2:

Verify Default Revision Rule setting. Enter the following preference name in the search eld as shown to view the preference setting.
IMAN_config_rule_name= Latest Working

This sets the user Revision Rule to the shown value by default.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

9-19

Status Types and Revision Rules

Step 3:

Verify BOM Precision preference setting. Enter the following preference name in the search eld as shown to view the preference setting.
IMAN_BOM_Precision_Preference= Imprecise

10-1

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, modication and deletion. Data protections are established with the database and not by the OS le protections. Teamcenter Engineering implements two different tiers of data protections: Rules-Based Protections Object-Based Protections

Rules-Based Protections The Teamcenter Engineering system administrator denes 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 dened 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.

10-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

Object-Based Protections 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 specic object. With Object-Based protections, settings are added to and controlled by the object to implement case-by-case exceptions to the access dened 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-3

Access Manager

Viewing Data Privileges

To view access privileges for an object, select the object, then choose ViewAccess... or .

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 specic Access Control List (ACL) that has been derived from the Rule Tree.

10-4

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

Teamcenter Engineering Privileges Access Privilege Read (R) Write (W) Delete (D) Description You can open and view (read) an object. You can modify (write changes to) an object. 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. 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. You can move a task ahead (promote it) in a workow job. You can move a task back (demote it) in a workow job. You can print an object, perform a FileSave As on an object and mark an object for archive. You can change ownership on an object. You can make the object available to other Teamcenter Engineering sites. You can subscribe to an object. You can export objects from your Teamcenter Engineering database. You can import objects into your Teamcenter Engineering database. You can transfer ownership of objects exported from your database. You can become the new owner of objects imported into your Teamcenter Engineering database. You can Write in-Class Instances

Change (C)

Promote (p) Demote (d) Copy (c) Change Ownership Publish Subscribe Export (X) Import (I) Transfer Out (x) Transfer In (i) Write ICOs

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-5

Access Manager

Activity: View Default Protections

In this activity you will create a new Item and view the default Access Manager dened privileges. Step 1: Step 2: Start the Engineering/My Navigator application. 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. Select your Home folder. Choose FileNewItem... The New Item window is displayed. Choose Item as the Type. Choose Next, then enter the following: Item ID 1234

Revision Name Description

000 Test Item (leave blank)

10-6

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

Choose Finish. A reference to the new Item is placed in your Home folder. Close the New Item window. Step 4: Review the Protections of the new Item. Select the 1234-Test Item.

Choose Access

from the tool bar.

The Access window displays your access to the object.

Review privileges on the Item.

A greyed out icon means the privilege is denied.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-7

Access Manager

Step 5:

View the Access Control List (ACL) for the Item. Choose in the Access window.

The complete Access Control List displays.

This window displays the complete Access Control List for the 1234-Test Item. From this window, you can derive any users privilege setting for this object. , For example, by locating the Write access column you can see 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 window. Close the Access window.

This concludes the activity.

10-8

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 specic objects. To change an objects protections, select the object and choose ViewAccess...

You can also use

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 specic 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.

To set the exception protection, select and a new Access Control Entry (ACE) will be added to the list. By double-clicking in the cells of the ACE you can dene the Accessor Type, Accessor ID and grant/deny privileges. Once added, the object-based ACEs will be identied 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-9

Access Manager

Activity: Modify Single Object Protections

In this activity, you will dene object specic Access Control List data to remove Write access from a single user. Step 1: Check your ability to add object specic ACL data. Select the 1234-Test Item.

Choose

from tool bar.

The Access dialog displays your access to the object.

Notice that you have

privilege for the Item.

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

10-10

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

The complete Access Control List displays.

Because you have

privilege, the

is active.

From this dialog you can also identify what AM rule is giving privilege. In this case the Working Named you the to the Owning User (you). ACL has granted Choose on the Access Control List window.

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 window. Close the Access window.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-11

Access Manager

Step 3:

Test the Object ACL Select the 1234-Test Item, then choose .

The Access window displays your access to the object.

Select Astaire, Fran(astairetr) from the User drop-down listing. The Access window 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 window.

This concludes the activity.

10-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

How Rules-Based Protections Work

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 specic ACEs

10-16

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

Pre-Dened Conditions (Rules) Condition Has Attribute Value Description

class:attribute=value Object has the value Eg: specied for the NoteType:name=UG* attribute of the given class. true or false class name User has bypass set. Object is of this Teamcenter Engineering class. Object has this description.

Has Bypass Has Class

Has Description Has Form Attribute Has Item ID Has Name Has Object ACL Has Status Has Type

text string accepts wildcards

item ID (accepts wildcards) text string accepts wildcards true or false status name accepts null entry (null=all) type name Object has this name. Object has an object ACL. Object has this status type attached. Object is of this Teamcenter Engineering type.

Has View Type In Job

BOMView type name Object is associated with this BOM View type. true or false Object is a target object in a workow job. Object is a member of the dened project. Object is archived. User is a group administrator in the current group.

In Project Is Archived Is GA

project ID true or false true or false

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-17

Access Manager

Is Local

true or false

Object resides in this database. Used with Distributed Teamcenter Engineering. User is a member of the project. User is currently logged in as a member of a system administration group. Object is owned by this group. Owning group of the object has a given security string. Object is owned by this site. Used with Global TcEng. Object is owned by this user.

Is Project Member Is SA

true or false true or false

Owning Group Owning Group Has Security Owning Site

group name security string

site name

Owning User user ID

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 dened 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.

10-22

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-23

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.
10-24 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

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 indicating the rule tree has been modied. name 4. Choose to save the changes to the AM Rule Tree le.

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 modied. 4. Choose to save the changes to the AM Rule Tree le.

Deleting an AM Rule 1. Select the desired rule to delete in the Rule tree. 2. Once the rule is selected, choose Delete. An asterisk appears next to the Access Manager name indicating the rule tree has been modied. 4. Choose to save the changes to the AM Rule Tree le.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-25

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 Choose Move Down to move the rule up one level in the Rule tree. to move the rule down one level in the Rule tree.

An asterisk appears next to the Access Manager name indicating the rule tree has been modied. 4. Choose to save the changes to the AM Rule Tree le.

10-26

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

Activity: Add Access Manager Rule

In this activity, you will use the Access Manager application to add a Company specic 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 dened 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 modiable 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 denition 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 deciency in the manufacturing center (1234/001 Item Revision).

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-27

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 dened 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. Change your Group/Role to dba/DBA. Choose EditUser Setting... 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.

Step 1:

Choose the

icon.

The Access Manager editor screen appears with the rule tree and named ACL editor screen is displayed.
10-28 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Access Manager

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 denition: The Condition, the Value, and the Named ACL. You will now create and attach a new named ACL to this branch.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-29

Access Manager

Enter CAMod in the ACL Name eld. Choose Create adjacent to that eld.

Next, choose to the right of the ACL contents window to add the rst 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).

10-30

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

Choose Choose

in Named ACL window to save the ACL. to modify the branch.

The new named ACL has been attached to the (Has Class) Item branch.

Step 5:

Save the modication to the rule tree. Choose on the Access Manager Tool bar.

The complete rule tree/named ACL denition has been written to the Database and a Backup has been saved to an OS le in the IMAN_DATA/am directory. Step 6: Test the Rule Tree change. Go to the Engineering/My Navigator Application. Select the 1234-Test Item.

Choose the tool bar The Access window displays your access to the object.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-31

Access Manager

Step 7:

View the Access Control List (ACL) for the Item. Choose in the Access window.

The complete Access Control List displays.

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 window. Choose Close on the Access window.

This concludes the activity.

10-32

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

Exporting and Importing the Rule Tree from a File

The Access Manager Rule tree can be exported as an ASCII le 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 modications (such as, adding or deleting branches, relocating branches, and so on). If, after many modications, 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 denitions 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 le format when the user chooses the Save icon from the Access Manager application. Guidelines and Recommendations Never modify rule tree les with a text editor. Although rule tree les are simple ASCII les that can be read using any text editor, you must never modify them with a text editor. These les 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 le. If there is any incompatibility, Teamcenter Engineering will immediately terminate the read operation (at the rst discrepancy) and display an error message. If you encounter schema compatibility problems when loading a Rule tree from a le, open that Rule Tree le with a text editor. Either print the le or make note of the types, roles, and groups referenced in that le. Then, dene these exact types, roles, and groups for your site.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-33

Access Manager

Exporting the Access Manager Rule Tree

From the Access Manager application... 1. Choose FileExport... A dialog is displayed.

2. Type in the lename for the rule tree being exported and choose a directory path. 3. Choose Export.

A conrmation dialog appears indicating the export was successful.

10-34

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

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 le to be used for the import. 3. Choose Import.

A conrmation dialog appears to indicate that the import was successful.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

10-35

Access Manager

Activity: Reset the Rule Tree from a File

In this activity, you will reset your Access Manager Rule Tree to the initial denition. Step 1: Locate the Rule Tree denition le. Using a command window or graphical le navigator, list the contents of your IMAN_DATA directory and notice the iman_am_rule_tree.default le. Step 2: Reset the Rule Tree. Start the Admin/Access Manager application. Choose FileImport... A le browser application displays. Navigate to the IMAN_DATA directory. Locate the iman_am_rule_tree.default le. Select the le, 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.

10-36

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Access Manager

Notice the Has Class(Item) branch no longer contains the CAMod Named ACL. The complete rule tree/named ACL denition has been written to an OS le in the IMAN_DATA/am directory. Step 4: Review the ACL for the Test Item in Navigator. Go to the Engineering/My Navigator application.

Select the 1234-Test Item and choose

Choose

in the Access window.

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 window. Choose Close on the Access window.

This concludes the activity.

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

The following table lists Project terms and denitions. Concept Project Denition 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. Rules dening how secondary objects are managed based upon its dened relation to the primary object. Teamcenter Engineering user with privileges to administer Projects using the Project application. Creates, modies and deletes Project information and team members. Project team member with privileges to modify 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 Project team members with privileges to assign or team 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.

Relation propagation rules Project administrator

Project team administrator

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 Add User.

11-6

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

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 .

(Wayne, Joan is used as an example only.) 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 window. Your User ID now appears in the Project Administrators list.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

11-7

Project Creation, Administration and Control

Step 2:

Create a Project Enter the Admin/Project application (may have to choose More... to add it to the Application list).

The Project Denition panel appears.

Enter Project A in the ID eld. Enter Test Project in the Name eld. 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.
11-8 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Project Creation, Administration and Control

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

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

11-9

Project Creation, Administration and Control

The standards group, is added to the Team.

Step 4:

Assign a team administrator. Choose Select a project team administrator from the bottom right of the menu. 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.

11-10

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

Step 5:

Assign privileged team members. Choose Select privileged team members from the bottom right of the menu. 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

11-11

Project Creation, Administration and Control

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.

This concludes the activity.

11-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

Project Security
Setting Security Rules The project administrator can dene 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 dened and added to the rule tree. The sub-tree under the In Project rule is the only tree that can be modied by a project administrator. Alternatively, a system administrator can dene 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

11-13

Project Creation, Administration and Control

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 eld is set to In Project.

Set the Value eld to Project A.

Select the blank eld from the pull-down list (on the right side of the ACL Name eld). This will set up the form to create a new Named ACL.

Type Project A in the ACL Name eld.

Choose

, to the right of the ACL Name eld.

Choose to add a line, then dene the following entry for the World.

11-14

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

Choose again to add another line, and then dene the following entry for the Current Project Team.

The ID of Accessor eld is automatically lled in with Project A-Test Project. Choose to the right of the ACL Name eld to save the Named ACL. Choose the AM tree. at the bottom of the panel to add the rule to

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

on the main toolbar.

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

This concludes the activity.

Project Creation, Administration and Control

Assigning Objects
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 eld 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 eld. 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.

11-16

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

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 specied 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 dened using the EditOptionsProject dialog.

Relation propagation rules can only be dened by System Administrators and they apply to the entire site.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

11-17

Project Creation, Administration and Control

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 Teamcenter/My Navigator application using the davistr account. Choose EditUser Setting... and make the selections shown.

Choose OK to close the form.

11-18

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

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-Test Project from the list of Projects for Selection. Choose > to move Project A-Test Project to the list of Selected Projects.

Choose Finish. After the Item is created, Close the New Item window.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 11-19

Project Creation, Administration and Control

Step 3:

Use the Properties window to verify that the newly created Item is part of Project A. Select the new Item. Choose ViewProperties. The Properties window appears.

Scroll down until you see the Project IDs eld and notice Project A is listed. You may have to choose All to see all the properties. 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.

11-20

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

11-21

Project Creation, Administration and Control

Locate and select Project IDs, then choose

The Project IDs property is moved to the Selected listing.

Choose Finish. Close the Insert Columns window. 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.

11-22

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Project Creation, Administration and Control

Step 5:

Verify the Security Rule. Select the Item object you just created.

Select

on the main toolbar.

The Access window appears.

Select List.

on the Access window to look at the Access Control

The ACL Control List window appears. Observe the entries in the list. Choose Cancel to close the ACL Control List window. Close the Access window. Log out of Teamcenter Engineering and log back in with your student userID.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

11-23

Project Creation, Administration and Control

Summary
In this lesson you: Established Project Administrators Created Projects and assigned team members Dened security rules for Project data Added objects to an existing Project

11-24

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Lesson

12 Workow Process Modeling

Purpose The purpose of this lesson is to build Teamcenter Engineering Workow Process Templates. Objectives Upon completion of this lesson, you will be able to: Create Generic Workow Process Templates. Add Handlers to Workow Processes. Create Workow Process Templates for Change Management. Import Process Templates Use Secure Tasks in Processes Use Resource Pools in Processes. Use Conditional Tasks in Processes Use the release_man Utility to add or remove Status

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-1

Workow Process Modeling

Overview of Teamcenter Engineering Workow

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

A Workow process uses dened 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 dened based on current company procedures for data signoff. A Workow 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.

12-2

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 rst sub-task would be to select the specic 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 dened 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. Predened processes that have to be followed.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-3

Workow Process Modeling

Process Terms and Functionality

Process Templates are templates that dene a Workow process. A Process denes a set of Tasks and a user prole (Group and Role) for each task. The user prole 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 dene the data required for that Job and assigns real Persons to perform Tasks according to their user prole. 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 dened for a Job are completed, the Job is complete.

12-4

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 at 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 Specication 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 specic requirements.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-5

Workow Process Modeling

Workow Process Modeling

Process Denitions
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 workow process. Tasks Tasks are the fundamental building block used to construct a process. Each task denes a set of actions, rules, and resources used to accomplish that task. A Task Template is a blueprint of a workow 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 specic Users to perform the signoffs who meet the Group/Role criteria dened 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-9

Workow Process Modeling

Creating new Workow Processes

Creating a Workow Process is started from the Workow 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 dene the process.

12-10

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 Workow Designer application, the process will remain in this state until it is made available for general use. This is done when exiting the Workow 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-11

Workow Process Modeling

Modifying existing Workow Processes

When modifying existing Workow Processes, it is important how the process is accessed. To modify a process, enter the Workow Designer and select the workow to be modied from the Process Template list. After choosing the Edit Mode icon, you have the option whether or not to take the process ofine.

Choosing Yes, will take the template ofine for modication. This is indicated by the Construction icon next to the process in the templates list. In this mode, all modication are saved. If a mistake is made, you can not cancel the modications.

Choosing No, will not take the template ofine. Instead, a copy is created for modication. 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 Workow Designer application, process templates are saved when you make them available when existing. Taking the process ofine is the only way to not save modications to a template once open for edit. To not save the modications, the template needs to be taken ofine and then the Delete icon in Workow Designer can be used to delete only the construction copy and cancel the modications. The original process template remains.

12-12

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 workow 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-13

Workow Process Modeling

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 Task Signoff Panel displays the Signoff Proles window.

The Signoff Proles window allows you to select the Group and Role for the correct signoff user. The user that matches this prole will be assigned later during the execution of the process.

12-14

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 eld allows you to dene the number of sign-offs that are required to complete the task. Leaving the Quorum eld blank or entering ALL species that approval must be unanimous, meaning all users must sign off. Any other positive integer species the quorum.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-15

Workow Process Modeling

Activity: Create a Quick Release Process

In this activity, you will learn how to create the Quick Release process. Step 1: Open the Workow Designer application window. Choose Admin. Choose Workow Designer. The Workow Designer window displays. Step 2: Create a New Process. Choose FileNew Root Template... The New Root Template window is displayed.

Enter Quick Release in the New Root Template Name eld. Select Review Process from the Based On Root Template list.

12-16

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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

The Attributes window appears. Select Released from the Release Status drop-down.

Close the Attributes window. 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.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 12-17

Workow Process Modeling

Choose OK. Step 4: Test the new Quick Release process by rst creating a Text dataset. Go to the Teamcenter/My Navigator application. Select your Home folder. Choose FileNewDataset... Set the Type to Text. Enter QR document in the Name eld. Choose OK. Step 5: Release the QR document dataset. Select the QR document dataset. (If asked, choose No on Create New File window.) Choose FileNewProcess...

12-18

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

The New Process window is displayed.

Notice the Process Name eld 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 dened for releasing certain data without a signoff. You will use this process again in a later lesson to release imported data.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-19

Workow Process Modeling

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. Step 1: Create a New Process. Enter the Admin/Workow Designer application. Choose FileNew Root Template... The New Root Template Dialog is displayed. Enter Import Release in the New Root Template Name eld. 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 Workow Designer window (just to the right of the green Start task). The New Review Task 1 task is created.
12-20 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Workow Process Modeling

Enter Import Review in the Name eld, 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-21

Workow Process Modeling

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 Workow 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: Dene the signoff team criteria. Expand the Import Review task and select the select-signoff-team.

12-22

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Choose the Task Signoffs Panel icon. The Signoff Proles wnidow is displayed.

Set the Group eld to dba. Set the Role eld 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
UGS, All Rights Reserved Teamcenter Engineering Application Administration 12-23

Workow Process Modeling

Choose

The Signoff Proles window should look like the following.

Choose the X in the top right corner of the Signoff Proles window to close it. Step 5: Set the Release Status. Select the Import Release (top level) task.

Select Task Attributes.

12-24

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Set Released Status to Released. Close the Attributes window. 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 dened in the database. You will use this process to release imported parts.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-25

Workow Process Modeling

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 les 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 le to the Teamcenter Engineering volume, a simple process will be adequate. Three release techniques could be used, depending on the specic data: The Quick Release (no reviewers) A Single Level Release (a reviewer in one level) Command line release (using the release_man utility).

12-26

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

release_man Utility
The release_man utility is used to status objects in batch mode without creating jobs and audit les. 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_specication 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 Specications and BOMViewRevisions of an Item Revision in the release folder are released along with the Item Revision. Remove the status type identied by the -status argument. If the object to be released has already been released, retain the original release date. Valid Status Type to be applied to all objects. Release folder name. Folder must reside in the Home folder of the user executing the utility.

-unrelease -retain_release_date -status -folder

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-27

Workow Process Modeling

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

12-28

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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. Start the Teamcenter/My Navigator application. Expand your Newstuff folder to show the Plastic Specs dataset.

Select the Plastic Specs dataset. Choose FileNewProcess... The New Process window appears.

Notice the Plastic Specs dataset is listed in the Targets area. Select Quick Release from the process template list.

Choose OK.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 12-29

Workow Process Modeling

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.

This concludes the activity.

12-30

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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. In the command window, execute the following command:
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.

This concludes the activity.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-31

Workow Process Modeling

Using Task Handlers in a Process Template

-person

Makes the user whose name is specied the responsible party for the task to which this handler is added. Accepts a single valid Teamcenter Engineering person name.

-owner -resourcepool

Makes the initiator (owner) of the process the responsible party for the task to which this handler is added. Makes members of the specied resource pool the responsible party for the task to which this handler is added. Resource pools can be dened in the form of group::role, role or group:: Accepts a valid Teamcenter Engineering resource pool name or one of the following keywords: $GROUP, $ROLE, $TARGETGROUP and $ROLEINGROUP.

The recommended placement of this handler is the Start action.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-35

Workow Process Modeling

Notify This action handler will inform users of a tasks status via OS e-mail. If the -attachment argument is included in the denition of the notify handler, then the recipients will also receive Teamcenter Engineering mail, and the OS e-mail will include a notication 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): Task reviewers that will receive notication. 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 postxed to the string identied 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: The Workow target attachment(s) will be included in $TARGET the TcEng mail. The Workow process will be included in the TcEng mail. $PROCESS -recipient

12-36

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

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.

This concludes the activity.

12-40

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Using Handlers to Create JT data

The EPM-tessellation-handler is used for creating DirectModel datasets from UGMASTER datasets. The placement of this handler can vary depending on the processing method (foreground or background) and the associated arguments used. This handler uses the following arguments. -continue -signoff Continues the review process, even when tessellation is unsuccessful. Use for non-critical tessellation processes. Completes the perform-signoff task if the handler was placed on the Complete action of the perform-signoff task. Completes the process if the handler was placed on the Complete action of the root task. Executes tessellation in the background. Status type to be applied to a rendered child.

-background -status

The following modes are available for tessellating UGMASTER or UGALTREP datasets when they are released. Foreground Background/ Synchronous No specic placement required. Use the background and signoff arguments and place the handler in the Complete action of the perform-signoff task of the Review task. The workow will wait for tessellation to complete before continuing. Use the background argument and place the handler in the Complete action of the root task.

Background/ Asynchronous

Sample placement shown below.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-41

Workow Process Modeling

System Setup prior to Tessellation Before Tessellation can be accomplished, there several system setup operations that need to be in place. NX environment variables, Teamcenter Engineering preferences, and server denitions should be established so that the tessellation can be preformed properly. Environment Variables There are two key environment variables that need to set before tessellation can take place. These relate to the location of the NX installation.
UGII_ROOT_DIR UGII_BASE_DIR

Preferences There are two key preferences that need to set before tessellation can take place.
EPM_tessellation_servers= NONE

This preference setting is used to identify the Tessellation Server. If a server is used, this should be set to <hostname>:<portno>, where hostname corresponds to the machine where the Tessellation Server runs and the portno corresponds to the port where it listens to the request. The default setting of NONE represents the stand alone mode of Tessellation Server.
EPM_tessellation_target_type= UGMASTER UGALTREP

This preference setting is used to identify the EPM Tessellation Targets. The valid targets are UGMASTER and UGALTREP datasets.

12-42

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Server Setup Tessellating datasets can be done from a server or from a standalone system. If a server is used, the Tessellation service must be installed. This is done via the Database Daemons option in the installation Setup window.

After a few setup questions, the Tessellation Service option is displayed.

Once installed, the service will be listed in the Services window.

For this class, we will not use the Tessellation Service option.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-43

Workow Process Modeling

Activity: Review the system setup

In this activity, you will review the necessary system setup for successfully tessellating UGMASTER datasets. Step 1: Check the NX environment variables. Use the right-mouse button on the My Computer icon on the desktop. Choose Properties. Choose the Advanced tab. Choose Environment Variables. Scroll down in the Environment Variables window to make sure the UGII_ROOT_DIR and UGII_BASE_DIR variables are set. Close the two windows. Step 2: Check the tessellation preferences. Select EditOptions from the pull-down menu. Select Index at the bottom of the form as shown.

12-44

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Type EPM_t in the Search on Preference name eld and click on the EPM_tessellation_servers preference listed in the Preferences List.

Make sure it is set to NONE. If the Tessellation Service was installed on a server, the hostname and port number would be listed here. Example: dtcld18:2098

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-45

Workow Process Modeling

Click on EPM_tessellation_target_type in the preference list. Make sure UGMASTER and UGALTREP are present in the Current Values list.

To close the Preferences form, select Cancel.

This concludes the activity.

12-46

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Activity: Add the tessellation Handler to the Quick Release process

In this activity, you will add the tessellation handler to the Quick Release process that was created in a previous activity. Then you will test the handler. Step 1: Access the Quick Release process for modication. Enter the Admin/Workow Designer application. Set the Process Template to Quick Release.

Choose Edit Mode. Choose Yes to take the Process Template ofine. Step 2: Add the tessellation handler. Make sure the Quick Release root task is selected. Choose Task Handlers. In the Handlers window, select the Complete task. Set the Action Handler eld to EPM-tessellation-handler.

Choose

at the bottom of the window.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-47

Workow Process Modeling

The Handler window should now look like the following.

Close the Handlers window. Step 3: Save the workow process. Choose FileClose. Select the Quick Release process from the left list and choose the right arrow. The process should now be on the right list. Choose OK to save the process and close the Workow Designer application. Step 4: Test the handler by rst creating a new Item. Go to the Teamcenter/My Navigator application. Select the Home folder. Choose FileNewItem. In the New Item window, make sure Item is selected, then choose Next. Enter the following. ItemID: tess001 Rev: Name: 001 test

Choose Finish to create the Item. Close the New Item window.
12-48 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Workow Process Modeling

Step 5:

Create a UGMASTER Dataset. Expand the tess0001 Item. Select the tess001/001 ItemRevision. Choose FileNewDataset. In the New Dataset window, make sure the Type is set to UGMASTER. Replace the slash (/) in the Name with a dash (-) so that it is tess0001-001 The Item structure and naming should look like the following. Choose OK.

In order for a UGMASTER dataset to be tessellated, the ItemID can not contain spaces. Also, the UGMASTER dataset can not contain a slash (/). Step 6: Add a part to the UGMASTER dataset. Select the tess0001-001 dataset. Choose ViewNamed References. In the Named References, choose Import... In the Import File window, navigate to the .../aa_class/workow_designer folder. Select the tess.prt le, then choose Import. Notice the tess.prt le now shows in the Named References window. Close the Named References window. Step 7: Create the jt data by releasing the ItemRevision. Select the tess0001/001 ItemRevision. Choose FileNewProcess. In the New Process window, set the Process Template to Quick Release.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 12-49

Workow Process Modeling

Choose OK. A window will appear showing that the tessellation process, which is running in Foreground mode, is logging into NX Manager. When the tessellation is complete, check to see if the DirectModel dataset was created.

This concludes the activity.

12-50

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 Workow ACLs which can be created and attached to the different tasks within a process.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-51

Workow Process Modeling

Using ACLs in a Process Template

Selecting Task Attributes with a particular task. displays the Attributes window associated

By selecting the Named ACL eld, 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 window, shown below.

Modifying a Named ACL will modify it for the Database, so it is recommended to create new Named ACLs for Workows.

12-52

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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. Step 1: Create a New Process. Enter the Admin/Workow Designer application. Choose FileNew Root Template... The New Root Template window is displayed. Enter TR Change Notice in the New Root Template Name eld. Leave the Based on Root Template eld set to Empty Template. Choose OK.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-53

Workow Process Modeling

Step 2:

Create the Process Tasks. Select Do Task Template 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 eld and press Enter. The task name changes to Prepare Change.

Select Add Status Task Template

on the toolbar.

12-54

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 eld and press Enter. The task name changes to ECPending Status Obtained.

Select Review Task Template

on the toolbar.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-55

Workow Process Modeling

Double-click in the Task Flow section just to the right of the Prepare Change task. The New Review Task 1 task is created. Enter Initial Change Review in the Name eld and press Enter. The task name changes to Initial Change Review.

Select Do Task Template

To move process tasks, click in the blue strip at the top of the task box. Step 4: Dene the Reviewer proles 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.

12-60

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

The Signoff Proles window is displayed.

Set the Group eld to high_performance. Set the Role eld to Engineering Manager. Verify Number of Reviewers =1 Choose to attached the signoff prole.

Close the Signoff Proles window.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-61

Workow Process Modeling

Expand the Final Change Review task in the Task Hierarchy Tree and click on select-signoff-team task.

Select Display the Task Signoffs Panel. The Signoff Proles window is displayed. Set the Group eld to high_performance. Set the Role eld to Engineering Manager. Verify Number of Reviewers =1 Choose .

Close the Signoff Proles window. Step 5: Dene the Release status values to be applied/modied. Select the ECPending Status Obtained task in the Task Hierarchy Tree.

Select Task Attributes.

12-62

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Change the Released Status to ECPending. Close the Attributes dialog. Select the Released Status Obtained task.

Choose Display the Task Handlers. The Handlers panel is displayed.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-63

Workow Process Modeling

In the Start action, select the create-status handler, then choose Delete (at the bottom).

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

Select the Complete Task Action. Set the Action Handler eld 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 (at the bottom) to add the handler.

12-64

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 Task Attributes. The Attributes windowis displayed. Choose the icon (Vault) adjacent to Named ACL.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-65

Workow Process Modeling

The Named ACL window is displayed.

Set ACL Name to blank

Enter Change Review in the ACL Name eld.

Choose

to the right of the ACL Name eld.

On the far right side of the window, select the + sign to add a new line. Double-click in the Type of Accessor box and select World.

12-66

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Set the protections as shown below by double-clicking in each box.

Select the + sign on the far right side 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 window should look like the following.

Choose

Choose Assign. Notice the Assigned ACL Name eld (bottom of Named ACL window) changes to Change Review. Close the Named ACL window. Notice the Named ACL setting in the Attributes window changes to show the new Change Review ACL.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 12-67

Workow Process Modeling

Close the Attributes window. 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 dened in the database.

This concludes the activity.

12-68

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Importing/Exporting Workow Processes

All Workow 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 Workow Templates window. From here, the destination directory and xml lename 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 Workow Templates window. From here, an import directory and xml lename can be identied.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-69

Workow Process Modeling

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 le. In a directory structure type window (i.e., Explorer for Windows), navigate to the aa_class/workow_designer folder. Locate the import_templates.xml le 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 green, you would locate the two incidents of change_userid and replace them with green, as shown in the following gures.

Before:

After:

Save and exit the templates le. Step 2: Import the workow processes. Enter the Admin/Workow Designer application. Choose ToolsImport. The Import Workow Templates window is displayed. Choose Import.

12-70

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

In the Select Directory window, navigate to the aa_class/workow_designer directory.

Select the import_templates.xml le, then choose Select. The import_templates.xml le is now displayed in the Import File eld.

Choose OK. Choose Yes to view the log le. After reviewing the le, choose Close. Step 3: Review the appended procedures. Choose ViewRefresh Window to view the newly imported processes.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-71

Workow Process Modeling

Workow Process Modeling

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. Start the Admin/Workow Designer application. 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-75

Workow Process Modeling

Select the Authenticated-Do task in the process ow diagram.

Choose Display Task Handlers. Select the require-authentication handler to observe its usage in the Perform action of the task.

Close the Handlers window. 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.

12-76

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Step 2:

Test the AA-Secure Tasks Process. Select the Home tab in the My Navigator application.

Expand the Item used in the previous activities and select the ItemRevision.

Choose FileNewProcess... 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.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 12-77

Workow Process Modeling

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.

12-78

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Observe the addition to the user interface of the Password entry eld.

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 eld is not present on this task.

Select Done, then choose Apply. Select the perform-signoffs task in your Inbox.

From the Viewer tab, choose the No Decision link in the Decision column.

Observe the addition of the Password eld in the user interface for the perform-signoffs task.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 12-79

Workow Process Modeling

Select Approve, enter your password, then choose OK. Select the perform-signoffs task in the dba/DBA Inbox.

From the Viewer tab, choose the No Decision link in the Decision column.

Observe the omission of the Password eld on the user interface for the perform-signoffs task.

Select Approve, then choose OK. Select the perform-signoffs task in your Inbox.
12-80 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Workow Process Modeling

From the Viewer tab, choose the Not Acknowledged link in the Decision column.

Observe the Password eld on the user interface for the perform-signoffs task.

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.

12-84

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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 Display the Inboxes tab. Go to the Teamcenter/My Navigator application.

Step 1:

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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-85

Workow Process Modeling

Choose

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/Workow Designer application.

Choose AA-Resource Pool from the Process Template.

12-86

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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.

Workow Process Modeling

Choose Display Task Handlers Panel.

to display the Handlers

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.

Close the Handlers window. Under the Auto Assigned RP for Review task, select the select-signoff-team task.

Choose Display Task Handlers. In the Start section, select the CR-ll-in-reviewers handler.

12-88

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Notice that this handler will automatically assign the dba/DBA resource pool as a Reviewer.

Close the Handlers window. Step 4: Test the AA-Resource Pool process template. In the Teamcenter/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.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 12-89

Workow Process Modeling

Close the New Item dialog. Expand the new Item object and select the ItemRevision object.

Choose FileNewProcess... 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.

12-90

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Select the Do task labeled Manually Assigned RP for Do.

Choose ActionsAssign... Set Group to dba. 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-91

Workow Process Modeling

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 ow and that the task was automatically assigned to the resource pool.

Select the Auto Assigned RP for Do task. Select Done, then choose Apply to complete the task.
12-92 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Workow Process Modeling

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 Proles list.

In the User drop-down selector, set the User to *.

Choose the + icon. Notice the new listing of * dba/DBA.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-93

Workow Process Modeling

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-ll-in-reviewers handler in the process template. Select the perform-signoffs task. From the Viewer tab, choose the No Decision link in the Decision column.

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

This concludes the activity.

Workow Process Modeling

Conditional Tasks
The Workow Designer Condition Task template is used to branch process ow according to some dened 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 congured to proceed manually require a user action before the task can proceed to completion. When the workow reaches this tasks Start action, the task appears in the selected users Inbox. The user completes the instructions, denes the condition path as either True or False, then clicks OK to complete the task and allow the workow 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 workow process. Do not dene a condition query or any custom handler that will dene a result for the task.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-98

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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/Workow 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.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-99

Workow Process Modeling

In the Viewer tab, toggle to Process View.

The current task (circled) precedes the manual condition task.

Toggle back to the Task View.

Select Done, then choose Apply to complete the task.

The next task to appear in the Task to Perform folder is the Manual Condition Task.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-103

Workow Process Modeling

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 owed through the correct branch to the next task when the conditional task was manually set to true.

Toggle back to the Task View.

12-104

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Select Done, then choose Apply to complete the task.

All tasks for the AA-Manual Condition Task process have now been completed. Step 3: Browse the AA-Automatic Condition Task Process. Enter the Admin/Workow Designer application. Choose AA-Automatic Condition Task from the Process Template drop-down.

Read the description of the process.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-105

Workow Process Modeling

Select the Automatic Condition Task task (circled) from the process diagram.

Choose ViewTask Properties...

12-106

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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.

Workow Process Modeling

Close the Task Properties dialog. Step 4: Test the AA-Automatic Condition Task Process. Select the Home tab in the My Navigator application.

Expand the Item and ItemRevision that was created earlier. Double-click the ItemRevision Master.

The ItemRevision Master form appears.

In the user_data_3 eld, enter MAKE. Choose OK to save and close the form. Select the ItemRevision object.

Choose FileNewProcess...

12-108

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Set the Process Template to AA-Automatic Condition Task.

Choose OK on the New Process dialog. Select the Inboxes tab in My Navigator. Expand your Tasks to Perform folder. Select the Standard Do task.

In the Viewer tab, toggle Process View.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-109

Workow Process Modeling

The current task precedes the automatic condition task.

Toggle back to the Task View.

Select Done, then choose Apply to complete the task.

The next task to appear in the Tasks to Perform folder is the IF Condition is TRUE task.

12-110

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

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

Select Done, then choose Apply to complete the task.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-111

Workow Process Modeling

If you wish to test the False condition, clear the user_data_3 eld, and then send the ItemRevision through the AA-Automatic Condition Task process again.

With the user_data_3 attribute eld blank (or with an entry different than MAKE), the process should automatically take the False branch.

This concludes the activity.

12-112

Teamcenter Engineering Application Administration

UGS, All Rights Reserved

MT14350-SG-100

Workow Process Modeling

Assigning Default Process Templates

Once you create Process Templates, you can assign specic 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 eld as a user initiates a certain type of data while working within a certain group when choosing the Assigned process template lter button.

Group and Role Preference Files Process Templates are assigned by using Preferences for the specied group.
IMAN_ItemRevision_release_procedure= Import Release

The Workow Designer application provides a graphical interface for creating the preference. From the Workow Designer application choose EditTemplate Filter.

With the example shown above, the following preference would be added to the high_performance group preferences
IMAN_ItemRevision_release_procedure= TR Change Notice Import Release

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-113

Workow Process Modeling

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.

Choose Index (bottom left). Notice that the Options window changes to show the Preferences elds.

In the Search on preferences name eld, slowly enter CR. Notice that as you type, the system is dynamically searching for preferences and displaying them in the Preferences list. Select the CR_allow_alternate_procedures preference. The window should now look like the following, which shows the all of the existing preferences that begin with CR.

UGS, All Rights Reserved

Teamcenter Engineering Application Administration

12-117

Workow Process Modeling

Change the Current values from any to none if necessary.

Choose Choose Step 3:

to save the change. to close the Options window.

Verify that your work has inuenced the FileNew Process dialog behavior. Go the Teamcenter/My Navigator application. Expand a previously created Item and select the ItemRevision.

Choose FileNewProcess... 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.

This concludes the activity.

Workow Process Modeling

Summary
In this lesson you: Created Generic Workow Process Templates. Added Handlers to enhance Workow Processes. Created Workow Process Templates for Change Management. Used the release_man Utility to add and remove Status Imported Process Templates Used Secure Tasks in Processes Used Resource Pools in Processes. Used Conditional Tasks in Processes

Teamcenter Engineering Application Administration

12-119

Lesson

13 Change Management
Purpose The purpose of this lesson is to demonstrate how to model Change Management (CM) Change Types. Objectives Upon completion of this lesson, you will be able to: Create a Change Type Add Handlers to a CM Workow Process

Teamcenter Engineering Application Administration

13-1

Change Management

Benets 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)

Teamcenter Engineering Application Administration

13-5

Change Management

Creating Change Types

Change Types are created from the Admin application group. application within the

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. Identication - You will dene naming rules for the Change object and dene the behavior of the New Change dialog Assign ID/Rev functions. Associated Form Type(s) - You will identify 1 or more 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 dene 1 or more number of Process Templates created using the Process Designer application to be associated with your Change Type.

13-6

Teamcenter Engineering Application Administration

MT14350-SG-100

Change Management

Enter the Change Type Name in the Change Type name eld. 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 dene the Change Type.

Teamcenter Engineering Application Administration

13-7

Change Management

Activity: Create the TRCN Change Type

In this activity, you will congure 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.

13-8

Teamcenter Engineering Application Administration

MT14350-SG-100

Change Management

Step 2:

Dene the settings for Change Id. You will dene 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:

Dene the running value, starting with 00001, for Change Id. Select the + sign next to Change Id, again.

Teamcenter Engineering Application Administration

13-9

Change Management

Enter the Range: 5-9 Enter the Value: 00001 Select the Format: Running Step 4: Dene 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 elds 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 Dened 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.

13-10

Teamcenter Engineering Application Administration

MT14350-SG-100

Change Management

Step 6:

Select the Process Templates to be associated with the Change Type. From the list of Dened process templates, select TR Change Notice, then choose the + sign.

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. Start the Teamcenter/My Navigator application. Select your Home folder in the Home tab. Choose FileNewChange...

Teamcenter Engineering Application Administration

13-11

Change Management

The Create/Revise Change window 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 workow process listed in the eld, 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.
13-12 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Change Management

Step 8:

View the Change object in the CM Viewer application Select the TRCN00001-Test change object. Choose Open. This launches the CM Viewer application.

Select the tab to view the Change Costs and Change Description forms associated with the Change Type.

Teamcenter Engineering Application Administration

13-13

13-16

Teamcenter Engineering Application Administration

MT14350-SG-100

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 workow process. Step 1: Access the TR Change Notice process. Start the Admin/Workow Designer application. Choose TR Change Notice from the Process Template list.

Select Edit Mode. Choose Yes to take the process template ofine. 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. The Handlers panel is displayed. Select the Complete Task Action. Set the Action Handler eld to ECM-add-affected-irs-as-target. Choose at the bottom of the dialog.

Teamcenter Engineering Application Administration

13-17

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 eld to EPM-attach-related-objects. Enter the following arguments:

Choose

at the bottom of the window.

Select the EPM-attach-related-objects Action Handler that was just created. Change the Argument elds to:

13-18

Teamcenter Engineering Application Administration

MT14350-SG-100

Change Management

Choose

at the bottom of the window.

Again, select the EPM-attach-related-objects Action Handler that was just created. Change the Argument elds to:

Choose

at the bottom of the window.

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.

Teamcenter Engineering Application Administration

13-19

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 ensure that newly created ItemRevisions added to the affected/solution Item folders will be added as process targets.

This concludes the activity.

13-20

Teamcenter Engineering Application Administration

MT14350-SG-100

Change Management

Summary
In this lesson you: Created the Change Management (CM) Change Types. Added Handlers to a CM Workow Process

Teamcenter Engineering Application Administration

13-21

Lesson

14 Command Suppression and Business Modeler

Purpose The purpose of this lesson is to use the Business Modeler application to model site specic Rules associated with creating and revising data. Objectives Upon completion of this lesson, you will be able to: Grant or Deny access to specic functions using Command Suppression Create Type Display Rules Create Naming Rules Create Property Rules Create Compound Property Rules Create Extension Rules Create Deep Copy Rules Export and Import Business Rules Import Business Rules

Teamcenter Engineering Application Administration

14-1

Command Suppression and Business Modeler

Command Suppression
Command suppression allows you to remove (suppress) one or more menu options from the default Teamcenter Engineering 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. Some sites may choose to 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 dened 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.

14-2

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Command Suppression Dialog You can use the Command Suppression application from the Teamcenter Engineering Admin application group to dene which command entries should be suppressed for each dened 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 icons. When nished dening the menus suppressed for a specic group and/or role, you must use FileSave. The Command Suppression denitions are saved as entries in the database.

Teamcenter Engineering Application Administration

14-3

Command Suppression and Business Modeler

Activity: Modify Command Suppression Denitions

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. In the Command Tree on the right, expand the Tools menu. Select Import.

14-4

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Choose Hide. Notice there is now a red line through Import. Choose Save. Step 3: Change your group and role to verify the suppressed entries. Choose EditUser Setting... 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. Go to the Teamcenter/My Navigator application. Select the Tools pull-down menu.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 14-5

Command Suppression and Business Modeler

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 EditUser Setting... and change yours settings back to he dba group and the DBA role. Choose OK the save the settings and choose OK for any warning 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.

This concludes the activity.

14-6

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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 the Rich Client. The application allows you to dene 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 Denes the naming conventions for the string property values of different type objects.

Deep Copy Rules Denes 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 Rules GRM Rules Allows dening run-time like properties on an object referencing and relating to a property on a source object. 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 afliate the following constraints with it: Cardinality, Changeability, Attachability and Detachability (Cut/Paste Rules). Allow you to limit the types of objects that are available for creation for particular groups or roles-in-group. Determine behavior when creating alternate and alias identiers by combining valid combinations of identier type, ID context, and identiable type. Allow you to control access to and the behavior of object properties. Allow you to use custom functions and predened methods to extend Teamcenter Engineering behavior. Denes the actions needed to be done in different time phases (pre-condition, pre-action and post action) for different operations (Create, Save As, Delete).

Type Display Rules IdContext Rules

Property Rules Extension Rules

In this lesson, we will cover some of the Business Modeler interfaces, but not all.

Teamcenter Engineering Application Administration

14-7

Command Suppression and 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 specic role in a group. Type Display Rules can be applied to the following base object types and their associated subtypes. Alias Dataset Folder Form Identier 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.

14-8

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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.

Teamcenter Engineering Application Administration

14-9

Command Suppression and Business Modeler

With the Product Engineer role selected, select Item from the list of Base Types. Choose Apply and close the Select Types window.

Use the CTRL key to select both the EndItem and Item types in the Shown Types list.

Choose Choose

to remove them from the Shown Types list. to save the rule.

14-10

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Step 2:

Test the Type Display Rules. Log out of Teamcenter Engineering. Log back in to the Teamcenter/My Navigator application. Use the tracytr userid. Notice, that the default role for tracytr in the high_performance group is Design Engineer

Select the Home folder, then choose FileNewItem.. Notice that all the Item types are available when using the Design Engineer role.

Close the New Item dialog. Choose EditUser Setting... In the User Settings window, change the Role to Product Engineer.

Teamcenter Engineering Application Administration

14-11

Command Suppression and Business Modeler

Choose OK to save the settings and close the window. Select the Home folder, then choose FileNewItem.. Notice, this time that only the Document and Functionality Item types are available using the Product Engineer role.

Close the New Item dialog. Log out of Teamcenter Engineering and log back in using your student (privileged) userid.

This concludes the activity.

14-12

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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 dene 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 dene 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 dened. The Naming Rule Operation panel has two tabs. These tabs are: Edit Naming Rule - Dene a Naming rule, with patterns to be matched. Attach Naming Rule - Attach a Naming rule to a property.

Teamcenter Engineering Application Administration

14-13

Command Suppression and Business Modeler

Creating a Naming Rule

Enter a new Naming Rule name. Select the Create icon.

Add Patterns to the Naming Rule. Select the + icon with the Naming Rule selected from the list. Add acceptable patterns to the Naming Rule using the following format

Select OK. Toggle on Generate Counters and ll in initial and maximum values if appropriate.

14-14

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Attaching a Naming rule. Select the Object (Item ID, Rev ID, Name, or Description for Items) Select the Case needed. Select the rule from the list. Select attach.

Teamcenter Engineering Application Administration

14-15

Command Suppression and 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 = ve 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. Start the Admin/Business Modeler application.

Make sure the Edit Naming Rules tab inside the Naming Rules tab is selected (default). Type Item ID in the Rule Name eld, and then choose the Create icon (far right).

14-16

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Choose

to create the rst pattern denition.

The Add Rule Pattern dialog appears.

Enter "P"NNNNN (no spaces) in the top eld of the Add Rule Pattern dialog.

Choose OK. This adds the rst allowed pattern to the display.

Choose

to create the second pattern denition.

Type "T"NNNNN (no spaces) in the top eld of the Add Rule Pattern dialog.

Teamcenter Engineering Application Administration

14-17

Command Suppression and Business Modeler

Choose OK. This adds the second allowed pattern denition to the display.

Choose

to create the third pattern denition.

Type "L"NNNNN (no spaces) in the top eld of the Add Rule Pattern dialog. Choose OK. This adds the third allowed pattern denition to the display.

Toggle Generate Counters to ON and provide the following: Initial Value: P00001 Maximum Value: P99999

Choose

to save the rule.

14-18

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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 eld. Choose Create. Choose to dene the pattern denition.

Type NNN in the top eld of the Add Rule Pattern dialog.

Choose OK. This adds the pattern denition to the display.

Teamcenter Engineering Application Administration

14-19

Command Suppression and Business Modeler

Toggle Generate Counters to ON and provide the following: Initial Value: 000 Maximum Value: 999

Choose Step 3:

to save the rule.

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 eld. Choose Create. This rule does not have a Pattern or a Generate Counters denition. 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.

14-20

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Expand the Item Class and Item Type nodes.

Select Item ID from the list (in the bottom window). Set Case to Upper, then select Item ID from the Rule Name drop-down list.

Choose the Attach icon.

Teamcenter Engineering Application Administration

14-21

Command Suppression and Business Modeler

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. Choose the Attach icon. 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. Choose the Attach icon. Step 7: Close the Business Modeler application.

This concludes the activity.

14-22

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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. Start the Teamcenter/My Navigator application. 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 elds.

Enter test item (lowercase) in the Name eld. Choose Finish to create the Item. Close the New Item dialog. Notice the Name has been converted to uppercase.

Teamcenter Engineering Application Administration

14-23

Command Suppression and 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, t 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.

Command Suppression and Business Modeler

To quickly check what format the Item ID should be, place the cursor in the Item ID eld and a hint will appear.

This works the same for the Revision eld. Close the New Item window.

This concludes the activity.

Teamcenter Engineering Application Administration

14-25

Command Suppression and Business Modeler

Property and Compound Property Rules

Property Rules Property rules allow you to control access to and the behavior of object properties. You can control whether a property is modiable, visible, enabled, or required. In addition, you can set an initial value for a property and dene complex properties comprised of a combination of properties and constant strings that assign a value to the property. Once congured, property rules apply to properties as displayed in both the Rich Client and Thin Client interfaces. Property rules dened on base Property rules dened on base types are inherited by subtypes. For example, a property rule dened on the Item type is inherited by the Document type.

The following rules can be applied to object properties: Modiable Allows you to place restrictions on the modiability 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 Allows you to specify the initial value to be assigned to a property Value when the corresponding object is created. The initial value rule applies only to the following object types: Item, ItemRevision, Alias, Identier, Dataset, and Form. Visible Allows you to specify whether a specic 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 specic object property. Applies only to: Item, ItemRevision, Alias, Identier, Dataset, and Form. Valid values: True and False. Complex Allows you to specify a combination of properties and constant property 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, Identier, Dataset, and Form.

14-26

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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 dened and resides on another object. The following terms are used for Compound Properties. Display Object Source Object Source Property The object on which the Compound Property is displayed. The object on which the property actually resides. 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 modiable, then the Compound Property will also be modiable. However, if a ReadOnly ag is set on the Compound Property Rule, the Compound Property will be a non-modiable property even if the Source Property is modiable. Appears disabled on the Display Object, if the property on the Source Object is not modiable. 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.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 14-27

Command Suppression and Business Modeler

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. 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-modiable 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 eld.

14-28

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Activity: Creating Item Property Rules

In this activity, you will rst 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. Start the Admin/Business Modeler application.

Select the Property Rules tab. Select the Item class from the list.

Choose

on the far right to create an empty row.

Select in the Property Name eld to access the LOVs, and then choose object_desc from the list.

Select in the Modiable eld to access the LOVs, and then choose Write from the list.

Teamcenter Engineering Application Administration

14-29

Command Suppression and Business Modeler

Enter Company Part in the Initial Value eld.

Make sure the Visible eld is checked, with the other elds unchanged.

Choose Step 2:

to save the rule.

Test the Default Description Property Rule. Start the Teamcenter/My Navigator application. Select your Home folder, then choose FileNewItem. Select Item for the Item Type, then choose Next.

14-30

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Notice the Description is already lled in with Company Part, which was dened by the Property Rule just created.

Choose Assign to populate the ItemID and Revision elds.

Enter test rule in the Name eld. Change the Description to Test Company. Choose Finish to create the Item. Close the New Item dialog.

Teamcenter Engineering Application Administration

14-31

Command Suppression and Business Modeler

In the Home folder, right-click on the newly created ItemRevision 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 Modiable eld set to Write. Choose Cancel to close the Properties window. Step 3: Change the Property Rule to set an unchangeable Description. Go to the Admin/Business Modeler application.

Select the Property Rules tab. Select the Item class from the list.

14-32

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Remove the text from the Initial Value eld.

Change the Modiable eld to Read Only.

In the Complex Property eld, enter: $item_id+/Company Part/+$object_name

Make sure the Visible eld is checked, with the other elds unchanged.

Choose Step 4:

Test the modied Property Rule. Start the Teamcenter/My Navigator application. Select your Home folder, then choose FileNewItem. Select Item for the Item Type, then choose Next.

Teamcenter Engineering Application Administration

14-33

Command Suppression and Business Modeler

Notice this time, the Description is blank because the Initial Value eld was cleared.

Choose the Assign icon to populate the ItemID and Revision elds.

Enter test rule in the Name eld. Try to enter Test Company in the Description eld, and note that you cannot edit it. This was not allowed due to the Property Rule

14-34

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Choose Finish to create the Item. Close the New Item dialog. 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 eld. Choose Cancel to close the Properties window.

Teamcenter Engineering Application Administration

14-35

Command Suppression and Business Modeler

Step 5:

Clear the Property Rule on the Item class. Go to the Admin/Business Modeler application.

Select the Property Rules tab. Select the Item class from the list.

Select any of the elds to select the whole rule.

Choose the

icon on the far right to remove the elds.

Choose

This concludes the activity.

14-36

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Activity: Creating Compound Property Rule between EndItem properties and Items
In this activity, you will rst 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).

Teamcenter Engineering Application Administration

14-37

Command Suppression and Business Modeler

In the Rule Operation panel, expand Item Masters.

Expand the EndItem Master and Attributes nodes, 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.

14-38

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

The Compound Property is attached to the EndItem.

Again, under EndItem Master, do the same for the PartType and Shipped Attributes Properties.

Now, three of the EndItem Master form properties are attached to the EndItem.

Step 2:

Test the Compound Properties. Start the Teamcenter/My Navigator application. In your Home folder, select EndItem EI001.

Choose ViewProperties....

Teamcenter Engineering Application Administration

14-39

Command Suppression and 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, the AA-Part Type to Machining, and AA-Shipped property to true.

Choose OK.

This concludes the activity.

14-40

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Extension Rules
Extension Rules Remove later: BMF_SUPPRESS_ACTION_RULES_DISPLAY (value=ON or OFF) to display Action rule tab Extension rules allow you to customize system behavior by applying extensions to extension points that are related to business operations in Teamcenter Engineering. Business operations are actions performed in the system, such as creating and saving an item, fetching or setting a property value, or invoking a user exit. Extension points are events in the system, such as a postaction on an operation or a user exit, that allow you to implement custom behavior. Extensions contain information about functions associated with Teamcenter Engineering types and properties. Business operations can expose one or more extensions points, which in turn can contain zero or more extensions. Extensions within an extension point display the following characteristics: Extensions can be arranged to execute in a specic sequence. Each extension can have a set of arguments that is unique within the extension point. Extensions can be activated and deactivated within an extension point. External extensions can be congured in the same manner as the core extensions delivered with the Teamcenter Engineering product. An extension can be included more than once in a single extension point and can also be included in multiple extension points. User exit operations can only be congured from the base extension point.

Extension Rule Inheritance Extensions on type operations dened for or assigned to a parent type are inherited by any and all subtypes of that type. For example, if the Document item type has two derived subtypes, SpecDocument and QADocument, any extensions dened for the Document item type are inherited by the SpecDocument and QADocument subtypes. Extensions can also be dened specically for a particular subtype. These extensions exist in addition to any extensions inherited from the parent object type. By default, subtypes inherit the extension rules from a parent type higher in the hierarchy. To override this default behavior, a subtype can be selected and have extension rules congured. In this case, all existing extension rules from the super type of the extension point are copied to the type in which the extension is congured. At
UGS, All Rights Reserved Teamcenter Engineering Application Administration 14-41

Command Suppression and Business Modeler

that point, modication of the extension rules on that super type for the given extension point are no longer propagated down to this subtype. To remove any override that is congured, remove all congured extensions from the subtype and apply the changes. You are prompted to conrm that you are removing the override and that rules are again inherited from the parent type Dening Extensions External extensions can be dened to customize Teamcenter Engineering behavior. Before dening the extension in Business Modeler, you must rst write the custom function in C or C++ and store it in a either a common library or a specic library. You can dene a single library or multiple libraries to store the functions that you associate with extensions. For more information, see the Integration Toolkit (ITK) Programmers Guide. In addition, you must determine the parameters that are passed to the program when it is executed. Specify the values for these parameters when you assign the extension. Values can be user-dened or derived from a saved query or List of Values (LOV). When dening the extension, you must also specify the type operations, property operations, and extension points for which the extension is valid. Assigning Extensions This section describes the process used to congure dened method extensions, including: Displaying, adding, modifying, or removing extensions from an extension point. Specifying argument values for dened arguments of an extension in an extension point. Ordering the extensions congured for a specic extension point. Activating an extension within an extension point. Overriding extension assignments inherited from a parent type.

14-42

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Some extension points for primary types have congured internal extension rules. Although these extensions are visible in the extension assignment table, they must not be removed. If you override this operation for a subtype, the internal rule is inherited by the subtype and you must take care that it is not deleted by default. For example, the ImanRelation::assert_unique internal extension is congured for the ImanRelation Create Pre-Condition extension point. This cannot be removed. If a relation type, for example, Iman_Specication, has this overridden, the ImanRelation::assert_unique extension is congured for the Iman_Specication relation by default. You must not remove this extension from the extension point. List of existing values for the BMF_CLASS_AND_TYPE_DISPLAY_LIST preference. Appearance, BOMLine, ERP, File, FileServer, ImanQuery, ImanRelation, PLMXML, PublicationRecord, PSOccurrence, Report, Session, SingleFileRecovery, Site, StorageMedia, User, ValidationResult, View

Internal Extensions There are two varieties of extensions: internal extensions and external extensions. Internal extensions are predened methods delivered as part of the Teamcenter Engineering product. These extensions cannot be modied. External extensions are custom extensions that you add to the database. The following internal extensions are delivered as part of your Teamcenter Engineering installation: autoAssignToProject checkLatestReleased copyVariantExpr createCAEObjects createObjects setIdentierProperties

Teamcenter Engineering Application Administration

14-43

Command Suppression and 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 Document Item. Select your Home folder, then choose FileNewItem. Select Document for the Item Type, then choose Next. Choose the Assign icon. Enter Test Document in the Name eld. Choose Finish to create the Document, then close the New Item dialog. Expand the Document and Document Revision objects.

Observe that the default objects created when an Document Item is created, are Document Master and Document Revision Master forms. Step 2: Modify Document display preferences. Choose EditOptions... Select Item in the General list.

14-44

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

On the General tab of the dialog, set Select item type to Document. 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 form is displayed. After: Document Master form 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.

Teamcenter Engineering Application Administration

14-45

Command Suppression and Business Modeler

Using the Ctrl key, select ItemRevision Master, engineering, and Release Status in the Shown Relations window.

Choose

to remove them from the Shown Relations list.

Choose Apply on the Options dialog. Observe the difference in the Document display. Before: After:

DocumentRevision Master DocumentRevision Master form and view are displayed. form and view are now 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.

This concludes the activity.

14-46

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Activity: Assign an Extension Rule

Since writing programs and dening the extension rules for those programs is beyond the scope of this course, in this activity, you will use the Business Modeler application to assign an existing extension rule (shipped with Teamcenter Engineering) to modify the Create and Revise characteristics for a Document ItemRevision. The modication will : Automatically create a Text dataset for the Document Revision when it is created. Only allow a single Working (no Release Status) Document Revision. Review an existing predened Extension Rule. Start the Admin/Business Modeler application.

Step 1:

Select the Extension Rules tab.

Select the Dene Extensions tab.

Select createObjects from the list of Dened Extensions.

Notice the different Extension Details elds, such as, the type of programming language the extension was written in and whether it is an internal or external extension.

Teamcenter Engineering Application Administration

14-47

Command Suppression and Business Modeler

Also, notice the different actions available to the createObject extension.

Step 2:

Assign an Extension Rule to cause automatic creation of Text datasets when Document Revisions are created. Select the Assign Extensions tab next to the Dene Extensions tab.

In the Extension Point Selection tree, expand the WorkspaceObjectItemRevision and select DocumentRevision.

Make sure the Type or Property option is set to Type.

14-48

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Set the Operation option to Create Revision and the Extension Point option to Post-Action.

Choose

to add a new line in the select types panel.

Double-click in the Extension Name eld and select createObjects from the list.

In the new elds that appeared, set the objectType Text and the relationType to Specications.

Choose

to add the settings in the Arguments eld.

Teamcenter Engineering Application Administration

14-49

Command Suppression and Business Modeler

Notice that the settings are also added in the select types panel.

Choose Apply. Choose Yes on the Override warning. Step 3: Assign and Extension Rule to prevent more than a single Working Document Revision. With the DocumentRevision still selected, leave the Operation set to Create Revision, but change the Extension Point to Pre-Condition.

Choose

to add a new line in the select types panel.

Double-click in the Extension Name eld and select checkLatestReleased from the list.

In the new elds that appeared, in the maxAllowedWorkRevs eld, enter 1. Choose to add the settings in the Arguments eld.

14-50

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Notice that the settings are also added in the select types panel.

Choose Apply. Step 4: Repeat the previous set-up for checkLatestReleased using the Revise and Pre-Condition options. Use the following settings.

When nished, close the Business Modeler application.

This concludes the activity.

Teamcenter Engineering Application Administration

14-51

Command Suppression and Business Modeler

Activity: Test Extension Rule Assignment

In this activity, you will test the assigned Extension Rule for the Create and Revise characteristics for the Document Item, which will: Automatically create a Text dataset for a new Document Revision. Only allow a single Working (no Release Status) Document Revision. Test automatic Text dataset creation. Start the Teamcenter/My Navigator application. Select your Home folder, then choose FileNewItem... Select Document for the Item Type, then choose Next. Choose the Assign icon. Enter Test Extension Rule in the Name eld. Choose Finish to create the Document Item, then close the New Item dialog. Expand the Document and Document Revision objects.

Step 1:

With the Extension Rule assigned, the Text dataset was created automatically when the Document Item was created. Step 2: Test prevention of multiple Working Document Revisions. Select the Document Revision object

Choose FileRevise... Notice that by default, the Revision eld is automatically populated with B. Choose Finish.

14-52

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

The following error dialog appears because you are attempting to create the next revision (B) of the Document before the current revision (A) has a status.

Choose OK to dismiss the error dialog, then Close the New Item dialog. Select the Document Revision object.

Choose FileNewProcess... Set the Process Template to Quick Release, then choose OK. You may need to choose ViewRefresh to observe the application of Status. Select the Document Revision object again.

Choose FileRevise... Notice again that the Revision eld is automatically populated with B. Choose Finish. Close the New Item dialog. This time the Revise action was successful.

This concludes the activity.

Command Suppression and 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 denes 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 reected in the original object. Copy as Reference - When the Deep Copy Rule species 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 specied 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.

14-54

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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 Extension 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 denition of an existing Item Revision. Highlight Revision B of your Test Extension 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.

Teamcenter Engineering Application Administration

14-55

Command Suppression and 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 rst 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.

This concludes the activity.

14-56

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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_specication. Step 1: Dene Deep Copy Rules for DocumentRevision Save As. Start the Admin/Business Modeler application. Choose the Deep Copy Rules tab. Expand the ItemRevision node in the Deep Copy Rules tree, and select DocumentRevision. Select Save As. In the dialog, set Relation Types to Specications. Check the Required check box. Choose to the right of the Copy As Object window.

Your window should look like this.

Choose Apply. Choose Yes to save the change. Establish the same Rule as above for the Revise command for DocumentRevision. Step 2: Close the Business Modeler application.

This concludes the activity.

Teamcenter Engineering Application Administration

14-57

Command Suppression and 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_specication. Step 1: Step 2: Start the Engineering/My Navigator application. Test the Deep Copy Rule for Revise. Select your Home folder, then choose FileNewItem... Select Document for the Item Type, then choose Next. Choose the Assign icon. Enter Test Revise in the Name eld. Choose Finish, then Close the New Item dialog. Expand the Document and Document Revision objects.

Highlight the Document Revision object. Choose FileNewProcess... Set the Process Template to Quick Release, then choose OK. Observe the application of status. Select the Document Revision object (only). Choose FileRevise... Choose Finish, then close the New Item dialog.

14-58

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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 ag, 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. Select 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.

Teamcenter Engineering Application Administration

14-59

Command Suppression and 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 ag, 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:

This concludes the activity.

14-60

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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 congured and applied at one company site to be exported to an XML le and imported into the Business Rules Application of a different company site. Importing Business Rules may overwrite the existing Business Rules conguration at a site. To avoid overwriting the Business Rules conguration at the current site, it is strongly recommended that the current conguration be exported to another XML le, which can then be compared or merged with the new XML le intended to be imported. The merged XML le can be imported into your Business Modeler to apply the new conguration.

Teamcenter Engineering Application Administration

14-61

Command Suppression and Business Modeler

Activity: Use the UI to Export Business Rules

In this activity, you will interactively export the current Business Rules dened in the Business Modeler application. Step 1: Export All Business Rules Open the Admin/Business Modeler application.

Choose Export (bottom right). In the Export window, 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 eld. Choose Export. Locate and open the all_business_rules.xml le in a text editor. After reviewing the le, close the text editor.

14-62

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Step 2:

Export Naming Rules only. In the Business Modeler application, again choose Export. 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 eld. Choose Export. Locate and open the naming_rules.xml le in a text editor. After reviewing the le, exit the editor without saving.

This concludes the activity.

Teamcenter Engineering Application Administration

14-63

Command Suppression and Business Modeler

Activity: Use the UI to Import Business Rules

In this activity, you will interactively import a Naming Rules le 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 le. In the Import window, navigate to the ...aa_class/business_rules directory. Select the undo_naming_rules.xml le.

Choose Compare and Import.

Choose Import.

14-64

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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.

Teamcenter Engineering Application Administration

14-65

Command Suppression and 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. Select Item in the Naming Rules tree.

14-66

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and 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. Close the Business Modeler application.

This concludes the activity.

Teamcenter Engineering Application Administration

14-67

Command Suppression and 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 Rich Client 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 conguration be exported rst (as a backup) and then merged with the (new rules) XML le 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 modications 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

14-68

Teamcenter Engineering Application Administration

MT14350-SG-100

Command Suppression and Business Modeler

Summary
In this lesson you: Managed access to specic functions using Command Suppression Created Type Display Rules Created Naming Rules Created Property Rules Created Compound Property Rules Create Extension Rules Created Deep Copy Rules Interactively Exported Rules Denitions Interactively Imported Rules Denitions Reviewed the import_export_business_rules utility

Teamcenter Engineering Application Administration

14-69

Lesson

15 Setup for NX Integration

Purpose The purpose of this lesson is to congure your system for NX specic requirements. Objectives Upon completion of this lesson, you will be able to: Make Decisions Regarding the NX Data Model at Your Site Setup Seed Part Files for NX Dene NX -to- Teamcenter Engineering Attribute Mappings Set NX Integration Preferences and Options Use Unique Process Template Features for NX Data

Teamcenter Engineering Application Administration

15-1

Setup for NX Integration

Terminology
The table below lists several NX terms along with the corresponding Teamcenter Engineering term. Unigraphics Part Part Revision Part File Part Number Master Part File Non-master Part File (specication or manifestation) Non-master Part File (altrep) Component Lock (part le geometry) Unlock (part le geometry) Lock (part le structure) Unlock (part le structure) Teamcenter Engineering Item Item Revision Dataset Item ID UGMASTER Dataset UGPART Dataset

UGALTREP Dataset Occurrence Check-Out (Dataset) Check-In (Dataset) Check-Out (BOMView Revision) 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.

15-2

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Item Structure and Named References

The gure 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 le. Additionally the ItemRevision contains the 2111_DWG and 2111_MFG for the non-master drawing and NC programming part les.

Each dataset contains les, or named references.

Teamcenter Engineering Application Administration

15-3

Setup for NX Integration

The named references for the 2111 datasets are shown below.

Named References for 2111_DWG

Name References for 2111_MFG

Name References for 2111000

15-4

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

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 2105/000 Frame Assembly is shown below.

Teamcenter Engineering Application Administration

15-5

Setup for NX Integration

Create Part Files

This section describes what happens in the Teamcenter Engineering database when you create a new part le in NX when running in NX Integration mode. Note that the database is only affected when you save a new part le. 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 le, with a new part number and a new part revision) in NX and save it, an Item, its rst Item Revision and a UGMASTER Dataset are created in the Teamcenter Engineering database. The dataset is referenced as a specication 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 elds that you would usually ll when you create an Item and a dataset from Teamcenter Engineering. Field Item ID Item Name Revision ID Item description Value set by NX Part Number specied by user in the NX Integration Part Selection dialog. Part Name specied in the Edit Database Attributes dialog. Revision specied in the Part Selection dialog. Part Description specied in the Edit Database Attributes dialog.

15-6

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

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 Engineering database. The values which NX Integration sets in the Teamcenter Engineering elds that you would usually ll 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 specication of the new Item Revision. The values which the system sets used for necessary elds are the same as given above for new parts. New Non-master Part File When you create a new non-master part le 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 Integration Part Selection dialog. You choose a part le type with Part File Type in the Part Selection dialog. If the le type is specication, the new dataset is referenced as a specication in the Item Revision. Similarly, if you specify a part le 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 le types. Part File Type master specication manifestation altrep Dataset Type UGMASTER UGPART UGPART UGALTREP Relationship Type specication specication manifestation altrep

Teamcenter Engineering Application Administration

15-7

Setup for NX Integration

Storage of Associated Files

Associated (dependent) les are les which are related to a part le, 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 le with the extension .tif. This le is separate from the part le, but is related to it (because it is an image of your part). Associated les are stored in a dataset with the NX part le in Teamcenter Engineering. They are stored as named references in the dataset. The named references specify the different types of le you can store with the part le.

When you open a part le from NX with le export enabled, NX Integration creates a directory for the part and exports the associated les governed by the current NX Integration role to that directory. The NX part les with the .prt sufx are not exported. When you save or close the part le, any new or changed les in the directory are saved in the Teamcenter Engineering dataset corresponding to the NX part le.

15-8

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Access Control
NX Integration locks the geometry for a NX part le as soon as you start to modify it. If the part is a master part le (and an assembly), the structure also becomes locked. The locking ensures that no other user can modify the part le at the same time. When you create a new non-master part le 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 le, NX Integration 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 le in NX. When NX Integration locks the geometry for a part le in your NX session, what is actually happening in the database is that the dataset corresponding to the part le is being checked out. When NX Integration unlocks the part les geometry, the Teamcenter Engineering dataset is checked back in.

Locking Structure When NX Integration locks the structure for a part le, 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.

Teamcenter Engineering Application Administration

15-9

Setup for NX Integration

UGMASTER / UGPART Behavior

We recommend that you always use UGMASTER datasets with NX Integration for master part les; 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 specication of a particular Item Revision.

Non-Master File(s) More than one UGPART dataset may be referenced as a specication of an Item Revision.

Loading from NX Integration When NX Integration loads a specic Item Revision as a component of an assembly, it looks rst for a UGMASTER dataset referenced by the revision as a specication. If it cannot nd one, it loads the rst UGPART dataset that it nds in the list of objects referenced as specications. NX Integration does not provide a means of loading a specic version of a dataset as a component, nor does it provide a means of opening it from NX. The latest congured version of a dataset is always used

15-10

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Seed Part Setup

When a user creates a new part in NX Integration, 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 le of any type), or Specic to a particular type of part le. For example, a seed part that may be used as the basis for part les of type specication 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 specication, containing two Items named Metric_dwg and Inch_dwg. A folder called master.

Teamcenter Engineering Application Administration

15-11

Setup for NX Integration

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 le. 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 Integration 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 les of type manifestation only. Initially, the manifestation folder is empty. You should place any seed parts used to create new manifestation part les (only) in this folder. The specication folder contains seed parts that can be used to create new part les of type specication only. The specication 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 les of type specication (only) in this folder. The master folder contains seed parts that can be used as the basis for part les of type master only. Initially, the master folder is empty. You should place any seed parts used to create new master part les (only) in this folder. NX Integration expects seed parts to be contained in the folders named NX seed parts, master, specication, 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 Integration 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.

15-12

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Seed Part Preferences

Display Seed Part Dialog This preference species whether the NX Integration Select Seed Part dialog is displayed when a part which has been created in Teamcenter Engineering is opened in NX for the rst 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 specied by UGMGR_SeedPartName is used as the basis for new part les. 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 specied by UGMGR_SeedPartName is used instead. Preference(s): File(s): Possible values: Default: Default Seed Part This preference species the default seed part which will be used as the basis for new part les created in NX. The part name (not the part number) of the seed part should be specied. Note that you must have read access to the seed part. Preference(s):
UGMGR_SeedPartName UGMGR_DisplaySeedDialog ug_english.def, ug_metric.def yes, always, no, never, top yes

File(s): Possible values: Default:

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Default Mappings
The default mappings between Teamcenter Engineering and NX Part attributes are described in the following table: UG Part Attribute DB_PART_NO DB_PART_REV DB_PART_TYPE DB_PART_NAME DB_PART_DESC DB_UNITS Description Part Number Part Revision Part Type Part Name Part Description TcEng Attribute Item ID Item Revision ID Item Type Item Name Item Description

Part Unit of Measure Item Unit of Measure

You cannot delete the default attribute mappings.

Teamcenter Engineering Application Administration

15-17

Setup for NX Integration

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 modied mapping denition le into the database. The existing le is overwritten each time a new le is imported. NOTE: It is recommended that this task be performed when all users are logged out of NX Integration. If this is not possible, any users who were logged into NX Integration at the time the new mapping le was imported must reload the database attributes using the NX Integration Reload command. Use the following steps to extend the attribute mapping: Export the existing mapping to a text le, using the export_attr_mappings utility. Edit the le to add, remove, or modify mappings. Import the modied mapping le as test mappings, using the import_attr_mappings utility. This allows you to verify the attribute mappings without affecting the existing real mapping denitions. 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 preferences dialog). This will cause Teamcenter Engineering to pick up the test mappings rather than the real mappings. When nished testing the mappings, import the modied mapping le as real mappings using the import_attr_mappings utility.

15-18

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Attribute Mapping Syntax

There are four syntax forms for the specication 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) (i.e., Item.GRM):

is one or more of the following separated with a (.) character

NR ( <named_reference_type> [, <form_type> ]) - A named reference of the current object. The particular reference is identied 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 specied for assignees in more than one level of the process denition, the optional argument <level> further identies a specic level.

Teamcenter Engineering Application Administration

15-19

Setup for NX Integration

<IMAN_Property> - The name of the Teamcenter Engineering property to be synchronized with the NX part attribute. <Qualier> - Species 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 signicance the attribute has. /write_once - NX Integration 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. This should not be used with Item Master Forms. /master=iman - Only Teamcenter Engineering is allowed to modify the value for the attribute. /master=both - Both NX Integration 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 le 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 specication which the NX part attribute will assume. Its specication 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.

15-20

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Comments and Contexts Symbols

Comments are introduced by the (#) symbol. Anything on the line after this symbol is not part of the mapping denition and is ignored. Contexts begin with the left bracket ({) symbol followed by a context specier 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 dene an Item-type-based context within a dataset-type-based context. The mappings dened within this nested context are then only applied to datasets of the specied type that are associated with Items of the specied 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 le

Teamcenter Engineering Application Administration

15-21

Setup for NX Integration

Activity: Teamcenter Engineering/NX Attribute Mapping

In this activity, you will modify the Teamcenter Engineering / NX attribute mapping denitions. Step 1: Step 2: Exit Teamcenter Engineering. 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) le in UGII_ROOT_DIR in a text editor. Search the le for the UGII_UGMGR_ATTR_SYNC setting. Make sure this variable is set to NEW. Close the text editor. Step 3: Export current mappings to a text le. Open a command window with the Teamcenter Engineering environment set. Use the cd command to navigate to aa_class. Type: cd ug_attr_sync Execute the following command: export_attr_mappings -u=infodba -p=infodba -g=dba -le=current_mappings.txt Open the new current_mappings.txt le in a text editor. Review the UGMASTER and UGPART dataset sections. Step 4: Review a modied mappings denition le. To save time, a modied version of the current_mappings.txt le has been prepared for you. In this step, you will open the new_mappings.txt le and review the additional mappings dened in this le. Open the new_mappings.txt le (in the .../aa_class/ug_attr_sync directory) in a text editor. Compare the le to the current_mappings.txt le and observe additions in the UGMASTER and UGPART sections.
15-22 Teamcenter Engineering Application Administration UGS, All Rights Reserved MT14350-SG-100

Setup for NX Integration

Close the text editor application for both les. Step 5: Import new mappings as a test mappings. Return to the command window with Teamcenter Engineering environment set. Verify you are still in the ug_attr_sync directory. Execute the following command: import_attr_mappings -u=infodba -p=infodba -g=dba -le=new_mappings.txt.v9 -test Step 6: Set environment for test mapping usage. Log in to the Teamcenter/My Navigator application and make sure nothing is selected (use CTRL and mouse to unselect). It may be necessary to use the Teamcenter Engineering 2 Tier Rich Client to perform this part of the activity. Ask your instructor. Select EditOptions from the pull-down menu

Select Index at the bottom left of the form. Select New Enter the preference name: IMAN_USE_TEST_ATTR_MAPPINGS as shown. Select String for the Type and enter Y for the Value.

Teamcenter Engineering Application Administration

15-23

Setup for NX Integration

Select Select Step 7:

to create the preference. to close the form.

Start NX and test the UGMASTER mappings. Choose the Open in NX In NX, choose the New

icon to start NX.

Use the following parameters: Part Type: Part Number: Part Revision: Part File Name: Seed Part: Choose OK. Choose OK on the Add Master to: dialog. Choose FormatDatabase Attributes... Item 13690 000 DWG13690 Inch

Part File Type: specication

Choose Assign. The following message appears.

The attributes mapped to the UGPART dataset type were dened using the /master=iman qualier, and therefore cannot obtain values from the NX interface. Choose OK on the No Write Enabled Attributes dialog. Save, then Close the part le (Do not exit NX).

15-28

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

From My Navigator, highlight the 13690/000 ItemRevision.

Choose FileNewProcess... Set the Process Template to Quick Release, then choose OK. The ItemRevision, UGMASTER and UGPART dataset should all have Status ags.

From NX, open the DWG13690 UGPART partle. 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. Open a command window with Teamcenter Engineering Environment set. Verify you are in the .../aa_class/ug_attr_sync directory. Execute the following command: import_attr_mappings -u=infodba -p=infodba -g=dba -le=new_mappings.txt This is the same command you executed earlier in the lesson, only this time the -test option is not being used.

Teamcenter Engineering Application Administration

15-29

Setup for NX Integration

Step 13: Unset environment for test mapping usage. Open the Preferences dialog and enter IMAN_US in the Search on preference name eld. Select the IMAN_USE_TEST_ATTR_MAPPINGS preference in the preference list. Select Delete on the form and OK from the Delete Preference question pop-up.

Select

to close the Preferences dialog.

This concludes the activity.

15-30

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Process Templates for NX Related Data

Special workow 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 Specication 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 specication relation to the Item Revision as target objects.

EPM-attach-related-objects This handler attaches the specied related objects of the target objects as target/reference attachments to the process. This handler goes through all the target objects, nds the secondary objects with the specied relation and type (if specied) 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.

Teamcenter Engineering Application Administration

15-31

Setup for NX Integration

EPM-tessellation-handler This handler generates .jt les 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 les belonging to the UGMASTER dataset and creates Vis les (.jt les). 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.

15-32

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Preference Settings for NX Integration

Locating the NX Integration Preferences For review, the following preference hierarchy is followed: 1. A preference set via shell commands. 2. User: 3. Role: 4. Group: 5. Site: Summary of the Preference Hierarchy for NX Integration Setting 1 2 3 4 5 6 User User Role Group UGMan Site In Shell Determined by Login and session settings. Determined by Login and session settings. Determined by Login and session settings. n/a n/a

Teamcenter Engineering Application Administration

15-33

Setup for NX Integration

Preference Settings to Consider for NX Integration

While there are many preferences available to customize NX Integration, the following were reviewed and considered for the discussion during this training course. NX Integration Default View Type The IMAN_UG_View_Type preference sets the BOM view type that NX Integration 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. Preference(s): Default:
IMAN_UG_View_Type view (Set to engineering in an earlier lesson.)

NX Integration 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 Integration. 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): Default:
IMAN_ugmaster_name_separator not set

15-34

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Environment Variable Settings for NX Integration

Locating the NX Defaults File The default NX Integration environment variables are read from the le ugii_env.dat. The default ugii_env.dat le is located in the directory set by UGII_ROOT_DIR. A ugii_env.dat le could also be used as a users preference le, 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 Specications The conguration variable UGII_OPTION in the ugii_env.dat le sets how to interpret and convert le specications. This preference accepts one of the following values: NONE File specications are interpreted without converting case (i.e., as-is). LOWER Converts entire le specication (directory and le name) to all lower case. Default = LOWER. Other settings available: UPPER, HINAME, LONAME We recommend lower case (UGII_OPTION=LOWER) for NX Integration part les and volume names when the volume is going to be used for NX Integration part les. Additionally we recommend that Teamcenter Engineering volumes and group names be lower case. This preference can affect TCFS if these recommendations are not followed.

Teamcenter Engineering Application Administration

15-35

Setup for NX Integration

NX Customer Default Files for NX Integration

NX Integration enables you to use NX and Teamcenter Engineering together. For this reason, some NX Integration customer defaults are located in the NX customer defaults le or can be edited in NX Customer Defaults. NX Customer Defaults NX customer defaults may be set by an administrator (site) or edited locally (user) if desired. Local edits may be disabled if desired. Possible Settings The seed part settings UGMGR_DisplaySeedDialog and UGMGR_SeedPartName were discussed earlier. By Pass Request to Position Components The Autoposition New Product Structure Components preference allows you to bypass NX prompting you to position each component which you have added in PSE. Autoposition New Product Structure Components 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, each component which has been added to the assembly in PSE is automatically placed at the origin in NX. This preference may be edited in NX by choosing FileUtilitiesCustomer Defaults and selecting Autoposition New Product Structure Components.

15-36

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Activity: Modify NX Integration Preferences

In this activity, you will set the NX Integration preferences. Step 1: Verify the following site preferences in the Preferences dialog. Open the Preferences dialog using EDITOptions from the pull-down menu.

Select INDEX Enter IMAN_UG_View_Type in the Search on preference name eld.

Notice the current setting of engineering, which was set earlier in the course. Leave the dialog open for the next step.

Teamcenter Engineering Application Administration

15-37

Setup for NX Integration

Step 2:

Add the following site preference. Add the following in the Preferences dialog.
IMAN_ugmaster_name_separator= /

The preference must be spelled correctly, otherwise Teamcenter Engineering will not use the preference. Select New Enter the preference name: IMAN_ugmaster_name_separator as shown. Select the Site button as shown for the preference Scope. Select String for the Type and enter / for the Value.

Select Select

to create the preference. to close the form.

This concludes the activity.

15-38

Teamcenter Engineering Application Administration

MT14350-SG-100

Setup for NX Integration

Summary
In this lesson you: Setup Seed Part Files for NX Dened NX-to-TcEng; Attribute Mappings Set NX Integration Preferences and Options

Teamcenter Engineering Application Administration

15-39

Lesson

16 NX Integration Import and Data Release

Purpose The purpose of this lesson is to import native NX les and other related data into Teamcenter Engineering. Objectives Upon completion of this lesson, you will be able to: Import NX Data into the Database Release Imported NX Data

Teamcenter Engineering Application Administration

16-1

NX Integration Import and Data Release

Introduction to NX Data Import

In standard NX, your parts are stored in operating system directories. NX Integration, however, does not search for your parts in operating system directories. Instead, it retrieves part les from the Teamcenter Engineering database. Therefore, in order for NX Integration 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 les and assemblies. The result is the creation of Items and the included UGMASTER and/or UGPART datasets which have the le Named References for the part le 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 specied. Creates an Item structure for data plus a dataset. Imports NX assembly and master model data. A mapping le is typically used to provide settings for the many options. Can use a mapping le suited for NX parts. Can use a search path le to locate NX parts.

16-2

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Parts and Assemblies to be Imported

For your reference these parts and assemblies will be discussed and imported in this lesson. Other les (e.g. seed les) 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.

Teamcenter Engineering Application Administration

16-3

NX Integration Import and Data Release

Frame Assembly The frame assembly below contains the components as listed in the Assembly Navigator.

16-4

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Prepare to Import NX 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 les to show the necessary preparation. The rst and most important step is to understand what les there are to be imported. Various types are listed: Components Assemblies Master associated les (e.g. TIF, HTML les) Non-master part les (Drawing and NC ".prt" les) Non-master associated les (e.g. NC, CLSF, PTP les) Non-NX les (e.g. DOD requirements, part testing results) Product (part) attributes

Because ug_import works slightly different for these le types, you must ask these questions: What setup requirements are there? What mapping les must be written? How to use ug_import?

Consider the example directory below of native NX les that must be imported.
1250_axle_000.tif 1250_axle_000.prt 1250_axle_000_dwg.prt 1250_000_dwg.cgm 1300_bearing_000.prt 1400_wheel_000.prt 1600_wheel_assy_000.prt 1700_spacer_000.prt border_b_seed.prt border_c_seed.prt m243_heat_treat.txt

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?

Teamcenter Engineering Application Administration

16-5

NX Integration Import and Data Release

Recognize the NX 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 border_b_seed.prt border_c_seed.prt

1250_axle_000.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) les 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 les can be imported with one command line ug_import execution and a mapping le to convert all les to the proper database Part ID and Revision.

16-6

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Master Associated Files (e.g. les like TIF, HTML)

1250_axle_000.tif

Next begin to recognize the les associated to the components and assemblies. These les would be like TIF or HTML les. These les can be placed in an individual directory and imported with one extra argument on the command line or one extra keyword in a mapping le. For example, you could simply use:
ug_import -part=1250_axle_000.prt -id=1250 -rev=000 -assoc_files=yes

where the 1250_axle_000.tif le would be in a sub-directory named 1250 to correspond to the part id (-id=1250). Non-Master Part Files (drawing and nc ".prt" les)
1250_axle_000_dwg.prt

Next recognize the non-master part les that work with the component and assemblies. These les would be drawings and manufacturing part (.prt) les. Non-master part les can reside in the same directory as their master part les, but must be imported with their own ug_import execution. For these part les you must specify the relation to the master part (e.g. specication, manifestation, etc.) and the name of the UGPART dataset created with the import. For example, you could simply use:
ug_import -part=1250_axle_000_dwg.prt -id=1250 -rev=000 -name=1250_DWG -type=manifestation

Teamcenter Engineering Application Administration

16-7

NX Integration Import and Data Release

Non-Master Associated Files

1250_axle_000_dwg.cgm

Next begin to recognize the les associated to the non-master part les (e.g., CLSF, PTP les). These les would be like CGM les that are associated to a drawing or the common CAM related les for manufacturing operations. Like before, these les can be placed in an individual directory and imported with one extra argument on the command line or one extra keyword in a mapping le. For example, you could simply use:
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 le 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 les can easily be done by importing the les into the Item or Item Revision with the import_le utility. This utility was used earlier in the course. Product and Part Attributes Product or part attributes may exist in the part le 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 le and then using a custom Teamcenter Engineering program to import the attributes into the database.

16-8

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Example Import Directories and Files Original directory and les.

1250_axle_000.tif 1250_axle_000.prt 1250_axle_000_dwg.prt 1250_000_dwg.cgm 1300_bearing_000.prt 1400_wheel_000.prt 1600_wheel_assy_000.prt 1700_spacer_000.prt border_b_seed.prt border_c_seed.prt m243_heat_treat.txt

Rearranged directories and les.

1250/ 1250_axle_000.prt 1250_axle_000_dwg.prt 1250_m_1250_dwg/ 1300_bearing_000.prt 1600_search.txt 1400_wheel_000.prt 1600_wheel_assy_000.prt 1700_spacer_000.prt border_b_seed.prt border_c_seed.prt m243_heat_treat.txt 1600_wheel_assy.map

As you can see the master part les for the 1600_wheel_assy_000.prt and the seed parts still remain in their original directories. The non-master part le (1250_axle_000_dwg.prt) and the non-NX le (m243_heat_treat.txt) also remain in the original directory. To convert the les names to database Part IDs and Revisions, the 1600_wheel_assy.map le has been added and will be used during the import. Also the 1600_search.txt le has been added to locate the 1400_wheel_000.prt. Two sub-directories have been created for the associated les. The sub-directory contents are shown below.
1250/ 1250_axle_000.tif 1250_axle_000_dwg/ 1250_000_dwg.cgm

Teamcenter Engineering Application Administration

16-9

NX Integration Import and Data Release

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:
ug_import -part=1600_wheel_assy_000.prt

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 prex and the .prt extension from the standard NX lename to form the Item ID. the item revision is set to "A".

The native lename /users/daytr/parts/1600_wheel_assy_000.prt becomes 1600_wheel_assy_000/A in Teamcenter Engineering. The ug_import utility allows you to ne-tune the creation of the assembly and each of its components by specifying extra command line keywords and through the use of mapping les.

16-10

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Introduction to Using Mapping Files

A mapping le can set the individual components without affecting other components in the assembly. Mapping le 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

Teamcenter Engineering Application Administration

16-11

NX Integration Import and Data Release

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 le on the command line, NX Integration searches the directories listed in the search list le for the component parts of the assembly. Importing Non-Master and Associated NX Files You may have other les that are used with your part les (e.g. machining operation les). In addition to importing part les, you can import other types of NX les associated with a part le from operating system directories.

16-12

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Understanding Various NX Integration Import Scenarios

The following import scenarios will be discussed to import native part le data. Import Component Parts or Assembly Parts without a Map File Import an Assembly using a Map File and Search File Import a Non-Master Drawing and NC Part File Import Files Associated to a Component (Master) Part File Import Files Associated to the DWG (Non-Master) Part File 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.

Teamcenter Engineering Application Administration

16-13

NX Integration Import and Data Release

Import Component or Assembly Parts without a Map File KEYWORD -part= VALUE The operating system pathname of the top level part in the NX assembly which is to be imported. Indicates whether the import will proceed as expected, without actually doing the import. The Item ID which is given to the standard NX part specied on the command line. The Teamcenter Engineering revision which is given to the standard NX part specied on the command line. The name of the Teamcenter Engineering folder which stores the imported assembly and all of its components.

-dryrun

-id=

-rev=

-import_folder=

Import an Assembly using a Map File and Search File KEYWORD -mapping= VALUE The operating system pathname of the le containing details of the way in which individual components in your assembly should be imported. The operating system pathname of the le which lists operating system directories to search for the components of your assembly.

-search=

16-14

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Import a Non-Master Drawing and NC Part KEYWORD -type= -name= VALUE The type of non-master part le created in Teamcenter Engineering. The name of the non-master part le created in Teamcenter Engineering.

Import Files Associated to a Part and to the NC (Non-Master) Part KEYWORD -assoc_les= VALUE Used to instruct ug_import whether to import les associated with the specied assembly and all of its components.

-assoc_root_dir= The operating system directory under which sub-directories containing associated les belonging to the assembly and all of its components are located.

Teamcenter Engineering Application Administration

16-15

NX Integration Import and Data Release

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 Part Number Revision Dataset Name Keyword -id= -rev= -name= Limit 26 characters 32 characters 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 specied 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.

16-16

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Import Component/Assembly Parts without a Map File

Scenario In this scenario, seed part les 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 le specied on the command line) as follows: All parts are imported as a master part le 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 le. Therefore assemblies will most likely be imported with a mapping le.

The -part= keyword species 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 les can be imported. You must always specify the full pathname of the operating system part le 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 les corresponding to the components of your assembly in the same directory as the top part. If the component part les are not located in the same operating system directory as the top part, you must specify a search-list le 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 specied on the command line (only) with a different part number and revision respectively.
UGS, All Rights Reserved Teamcenter Engineering Application Administration 16-17

NX Integration Import and Data Release

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:
ug_import -part=1600_wheel_assy_000.prt -import_folder="1600 Wheel Assembly"

Note that the -import_folder= keyword causes the assembly and all of its components to be imported into the specied 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 le 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.

16-18

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Import an Assembly using a Map File and Search File

Scenario In this scenario, a Wheel Assembly will be imported. A map le will be used to convert all the part le names to their database part ID. Additionally a search le 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 le is a text le which lists the operating system directories which ug_import should search in order to locate the part les corresponding to component parts in an assembly. The lename of a search-list le is specied on the ug_import command line using the -search= keyword. For example,
ug_import -part=1600_wheel_assy_000.prt -search=1600_search.txt

You need to provide a search-list le if any part les corresponding to the components of your assembly are located in different directories from the part le which stores the top part in the assembly. A search-list le simply lists the operating system directories which should be searched to locate the component les of the assembly. Each directory should be specied on a new line. If a directory name ends in "/...", all directories beneath the specied directory also are searched. For example, a search-list le 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_les and all of the directories beneath it. 3. The /iman/class-default/v5_sitea_parts directory.

Teamcenter Engineering Application Administration

16-19

NX Integration Import and Data Release

Mapping Files A mapping le is an optional le that may be specied for the import utility. The purpose of a mapping le is to allow you to specify exactly how individual components in an assembly are imported into Teamcenter Engineering. Mapping File Format A mapping le is a simple text le which instructs ug_import how to import the components in your assembly. The text in a mapping le may comprise expressions, le names, directory names, and the names of parts and revisions in the database. A mapping le is divided into sections of the format:
[SECTION_NAME] KEYWORD=VALUE KEYWORD=VALUE

An example mapping le is shown below:

! Mapping file for importing chassis assembly [Defaults] import_folder = "Import Folder" db_part_no=$STRIPPED_LEAFNAME existing_data=$USE_EXISTING [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"

16-20

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Key Points There are a few general points to note when using mapping les: An exclamation mark (!) at the beginning of a line species the line as a comment line. Mapping les can contain blank lines. ug_import ignores leading spaces at the beginning of a line. The maximum length of a line in a mapping le is restricted to 132 characters, including spaces. If you wish to include spaces in a eld, then you must enclose the eld in double quotes. Each [SECTION_NAME] and KEYWORD=VALUE directive must be specied on a separate line.

Using the SECTION_NAME The SECTION_NAME eld can be specied as either [Defaults] or the name of a NX part le. If you specify a SECTION_NAME of [Defaults], any KEYWORD=VALUE mapping le directives specied 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 le 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 specied in a section by either the full operating system pathname or just the part number. You cannot use environment variables in lenames in a mapping le.

Teamcenter Engineering Application Administration

16-21

NX Integration Import and Data Release

Using the KEYWORD AND VALUE The KEYWORD eld in a mapping le is one of a number of reserved keywords. These keywords are tabulated below: Keyword: Description: Valid Expression: Default: db_part_no TcEng part (Item) ID $STRIPPED_LEAFNAME $EXPORTED_PART_NO If the part has been previously exported from NX Integration, defaults to the value it had when exported. Otherwise, defaults to $STRIPPED_LEAFNAME db_part_rev TcEng part revision $EXPORTED_PART_REV Defaults to A db_part_name TcEng part name $STRIPPED_LEAFNAME $IMPORTED_PART_NO Default: If the part has been previously exported from NX Integration, defaults to the value it had when exported. Otherwise, defaults to the same value as db_part_no. db_part_desc TcEng part description Defaults to the same value as db_part_no, if specied in a mapping le. Otherwise, defaults to $STRIPPED_LEAFNAME (the le name of the UG part without the leading directory and the .prt extension).

Keyword: Description: Valid Expression: Default: Keyword: Description: Valid Expression:

Keyword: Description: Valid Expression: Default:

16-22

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Keyword: Description: Valid Expression: Default:

import_folder TcEng folder where imported parts are placed. $DEFAULT_IMPORT_FOLDER Your Newstuff folder. Note that -import_folder specied on the command line takes precedence over import_folder specied in a mapping le. existing_data What to do if parts already exist in TcEng $FAIL_IF_PART_EXISTS $FAIL_IF_REV_EXISTS $OVERWRITE_EXISTING $USE_EXISTING

Keyword: Description: Valid Expression:

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.

Teamcenter Engineering Application Administration

16-23

NX Integration Import and Data Release

The VALUE consists of part le names and optional reserved EXPRESSION(s). The reserved expressions are described below: EXPRESSION $STRIPPED_LEAFNAME EXPANDS TO: OS lename of the component (not assembly) stripped of any prex ending in / (UNIX) or : (VMS) and the .prt sufx. For example: "/tmp/top_level_a.prt" "top_level_a" $STRIPPED___LEAFNAME (Note that there are three underscores) OS lename of the component stripped of any prex ending in / (UNIX) or : (VMS) and the sufx (delimited by _), if 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 specied by the mapping le has occurred). If the Part (Item) exists, do not save the assembly. If Part Revision (Item Revision) exists, do not save the assembly. If the part data exists, overwrite it. If a component already exists in TcEng, use the database copy in the current assembly.

$DEFAULT_IMPORT_FOLDER Global default TcEng target folder. $FAIL_IF_PART_EXISTS $FAIL_IF_REV_EXISTS $OVERWRITE_EXISTING $USE_EXISTING

16-24

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

The Import Log File

Below is an example log le (always named import.log) that is created during the use of ug_import. Also a syslogle 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/legacy/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/legacy/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/legacy/ug_import_files/1300_bearing_000.prt] NX Manager part number is [1300/000] in folder [Newstuff] Part will be created with type [Item]. Part # 4, [/users/legacy/ug_import_files/1400_wheel_000.prt] NX Manager part number is [1400/000] in folder [Newstuff] Part will be created with type [Item]. Part # 5, [/users/legacy/ug_import_files/1700_spacer_000.prt] NX Managerpart number is [1700/000] in folder [Newstuff] Part will be created with type [Item]. Creating Creating Creating Creating 1600/000 1300/000 1400/000 1700/000

Starting Save............. Saved Saved Saved Saved part part part part [1300/000] [1400/000] [1700/000] [1600/000] successfully. successfully. successfully. successfully.

All parts were successfully saved. ************ UG_IMPORT finished without error ************

Teamcenter Engineering Application Administration

16-25

NX Integration Import and Data Release

Activity: Using ug_import to Import the Seed Parts

In this activity, you will use the ug_import utility to import a part le into a dataset. Specically, 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 les. In a text editor, view the ug_import.scr.bat script (ug_import.scr on Unix) in the aa_class/ug_import_les directory. Notice, that the DBAUSER variable is already dened 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. Use the cd command to navigate to the aa_class directory. Type: cd ug_import_les 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 les.
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.

16-26

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

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 eld.

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.

Teamcenter Engineering Application Administration

16-27

NX Integration Import and Data Release

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 conrm.

This concludes the activity.

16-28

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Activity: Import the 1600 Wheel Assembly

In this activity, you will use ug_import to import an assembly part le and its components into the database. You will use a mapping le to convert the part le 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_les directory. Type: ug_import.scr.bat 1600 (ug_import.scr 1600 on Unix) The following command is used to import les for the 1600 Wheel Assembly.
ug_import -part=1600_wheel_assy_000.prt -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 Integration. Expand the 1600-Wheel Assembly Item. Expand the 1600/000-Wheel Assembly ItemRevision. Double-click on the 1600/000 UGMASTER. NX Integration starts and loads the 1600-Wheel Assembly.

This concludes the activity.

Teamcenter Engineering Application Administration

16-29

NX Integration Import and Data Release

Import a Non-Master Drawing File

Scenario In this scenario, a Drawing le will be imported. To import this non-master part le 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 le is a master part le or a non-master part le, unless the master part le 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 le to be imported: KEYWORD -id= VALUE The item ID of the master part le which the non-master part le is to belong to. The item revision which is given to your im ported non-master part le. The type of non-master part le. This may be: specication (or spec for short) ,or manifestation (man for short). The name of the specication or manifestation.

-rev=

-type=

-name=

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 specic part revision and non-master dataset name. Note that if -rev is omitted, and the revision is not specied in a mapping le, the congured revision (according to the default conguration rule) is used. If there is no congured 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.

16-30

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Activity: Import the 1250 Axle Drawing

In this activity, you will import the 1250_axle_000_dwg.prt drawing le 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_les 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 le.
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 le. Choose Close to close the Named References window.

Teamcenter Engineering Application Administration

16-31

NX Integration Import and Data Release

Step 3:

Review the 1250 Axle Drawing using NX Integration To make this more clear, in NX Integration close all parts. Choose FileCloseAll Parts. Choose Yes to conrm 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.

This concludes the activity.

16-32

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Import Files Associated to a (Master) Part File

Scenario In this scenario, some les that are associated to parts will be imported. To import these les associated to a part le 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 les that are associated with both master and non-master part les. In this case dependent les 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 -assoc_les VALUE Used to instruct ug_import whether to import associated les belonging to the specied part and associated les belonging to all of its components. The value must be "yes" or "no". Species the root directory under which sub-directories containing the associated les belonging to all parts in the spe cied assembly are located. The directory must already exist.

-assoc_root_dir

Both -assoc_les 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 les to be imported, you must specify -assoc_les=yes on the command line. The ug_import utility then searches the following locations (in the order shown) for the sub-directories containing associated les for individual parts: the directory specied by the assoc_les_dir keyword in a mapping le (if present). your current directory.

When the -assoc_root_dir argument is specied on the command line, ug_import assumes that you wish to import associated les belonging to the
UGS, All Rights Reserved Teamcenter Engineering Application Administration 16-33

NX Integration Import and Data Release

part specied on the command line, and the associated les belonging to each of its components. The associated les are imported from sub-directories beneath the directory specied by -assoc_root_dir. If the specied associated les directory cannot be located, the import is aborted. Sub-directory Example When using -assoc_les=yes without -assoc_root_dir= the dependent les will be imported from the directory 1250. The 1250 is determined from the Part ID (1250). The dependent les must be in this directory for ug_import to nd them.

16-34

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Activity: Import the 1250 Axle Associated Files

In this activity, you will use the ug_import utility to import the 1250.tif le 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 les. Continue working from Teamcenter Engineering environment command window and the ug_import_les directory. Type: ug_import.scr.bat 1250axleassoc (ug_import.scr 1250axleassoc on Unix) The following command is used to import the 1250.tif le 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 le(s) in the 1250/000 UGMASTER. Using ViewRefresh is necessary since the 1250/000 UGMASTER was previous loaded in Teamcenter Engineering. Choose ViewNamed References... The Named References window displays showing the part les, including the new 1250_axle_000.tif le. Choose Close to close the Named References window.

This concludes the activity.

Teamcenter Engineering Application Administration

16-35

NX Integration Import and Data Release

Import Files Associated to the DWG (Non-Master) Part File

Scenario In this scenario, some les that are associated to drawings will be imported. To import the les associated to a non-master part le 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 les that are associated with non-master part les. In this case dependent les will be imported as named references into the 1250_DWG UGPART. Sub-directory Example When using -assoc_les=yes without -assoc_root_dir= the dependent les 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 les must be in this directory for ug_import to nd them.

16-36

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Activity: Import the Axle Drawing Associated Files

In this activity, you will use the ug_import utility to import the 1250_000_dwg.cgm le associated to the 1250 Axle Drawing. Step 1: Import the 1250 Axle Drawing Associated les. 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 le 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 le(s). Choose ViewNamed References... The Named References dialog displays showing the les, including the new 1250_000_dwg.cgm le. Choose Close to close the Named References window.

This concludes the activity.

Teamcenter Engineering Application Administration

16-37

NX Integration Import and Data Release

Import Files Using a Full Map File

Scenario 6 In this scenario, all the part les (master, non-master, and associated) will be imported. To import all these les 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 le will control the parameters for all these part les: components assemblies master part les non-master part les associated les to masters associated les to non-masters

16-38

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

KEYWORDs for the Master Parts These KEYWORDs are used in the mapping le to control the Part ID, Revision, Part Name, and Part Description for the Item, Item Revision, and UGMASTER created during the import. KEYWORD db_part_no DESCRIPTION DEFAULT TcEng part (Item) ID If the part has been previously exported from NX Integration, defaults to the value it had when exported. Otherwise, defaults to $STRIPPED_LEAFNAME Defaults to A

db_part_rev db_part_name

TcEng part revision

TcEng part name If the part has been previously exported from NX Integration, defaults to the value it had when exported. Otherwise, defaults to the same value as db_part_no. TcEng part description Defaults to the same value as db_part_no, if specied in a mapping le. Otherwise, defaults to $STRIPPED_LEAFNAME (the le name of the UG part without the leading directory and the .prt extension).

db_part_desc

KEYWORDs for the Non-Master Parts These KEYWORDs are used in the mapping le to control the name of the UGPART (non-master) and determine the placement of the UGPART inside the Item Revision (e.g. Specication, Manifestation relation). db_model_name db_model_type TcEng dataset name TcEng model type No default value (not required for master model type) The model can be: specication (or spec for short) or manifestation (man for short). If not specied the model type defaults to master.

Teamcenter Engineering Application Administration

16-39

NX Integration Import and Data Release

KEYWORDs for Associated Files for Master/Non-Master Parts These KEYWORDs are used in the mapping le to control the import of associated les (e.g. TIF, CGM, HTML, and other NX les). Specifying assoc_les=yes will cause ug_import to import les into the UGMASTER or UGPART as additional named references. KEYWORD assoc_les DESCRIPTION DEFAULT Used to instruct ug_import whether to import les associated with the specied assembly and all of its components. The sub-directory under the current directory where associated les for the specied part can be found. No default value. If assoc_les_dir is not specied, defaults to a name resembling the part lename. For example, the associated les for a part named 2111.prt are located in a sub-directory named 2111.

assoc_les_dir

The full path directory containing the associated les or the sub-directory name from the current directory containing the associated les.

General purpose KEYWORDs These general purposed KEYWORDs are used in the mapping le 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 specied on the parts are placed. command line takes precedence over import_folder specied in a mapping le. What to do if parts already exists in TcEng 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.

existing_data

16-40

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Below is an example map le. This mapping le 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] existing_data=$USE_EXISTING 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

Teamcenter Engineering Application Administration

16-41

NX Integration Import and Data Release

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 le for all the master parts, non-master parts, and associated les. Step 1: Import the 2105 Frame Assembly and all of its other les. 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 les.
ug_import -part=2105_000.prt -mapping=2105_assy.map -assoc_files=yes ug_import -part=2111_000_dwg.prt -mapping=2105_assy.map -assoc_files=yes ug_import -part=2111_000_nc.prt -mapping=2105_assy.map -assoc_files=yes

Step 2:

Review the 2105 Frame Assembly in My Navigator. When the script is nished, 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 Integration. To make this more clear, in NX Integration, 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.

16-42

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

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 conrm the exit.

This concludes the activity.

Teamcenter Engineering Application Administration

16-43

NX Integration Import and Data Release

Importing Non-CAD Files into an Item

The M243_Heat_Treat text le should be imported into the database to be a reference of the 1250 axle part. The import_le utility allows you to import les into the Teamcenter Engineering database according to a set of user-specied arguments. These arguments will supply: user identication information dataset information Item information to be associated with the imported le

The latter is new in this class for the use of import_le. 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 les into Teamcenter Engineering just as datasets (as seem in a previous lesson). 2. To import les 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 les into Teamcenter Engineering as datasets and place the le inside an Item Revision. The import_le 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>]

16-44

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Activity: Import the Heat Treat Text File

In this activity, you will use the import_le utility to import a text le into the database to be a reference of the 1250 Axle part. Step 1: Import the m243_heat_treat.txt text le. In the command window, change back to the ug_import_les 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 le 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 le, then exit the text editor.

This concludes the activity.

Teamcenter Engineering Application Administration

16-45

NX Integration Import and Data Release

Releasing Previously Imported NX 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 ItemRevisions, the Specication relation objects are released together with the handler EPM-attach-target-objects. Considerations in Releasing Non-specication Data When non-specication data is released the reviewers dened in the procedure may be different than the reviewer dened in the procedure for master and specication data. When releasing non-specication data immediately after the data has been imported, the data could be released in the same procedure as the master and specication data. This could be accomplished by initiating the Item Revision and pasting the non-specication data into the Job (before the Job is started).

16-46

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

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. Choose FileNewProcess... 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-ll-in-reviewers handler you added to the Import Release process template in an earlier lesson. Select the perform-signoffs task.

Teamcenter Engineering Application Administration

16-47

NX Integration Import and Data Release

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 ags have now been set.

This concludes the activity.

16-48

Teamcenter Engineering Application Administration

MT14350-SG-100

NX Integration Import and Data Release

Summary
In this lesson you: Imported NX Data into the Database Released Imported NX Data

Teamcenter Engineering Application Administration

16-49

Index

A Access control . . . . . . . . . . . . . . . . 15-9 Access Control . . . . . . . . . . . . . . . . 15-9 Adding a New Volume to FMS . . . . 2-32 AM Rule Tree . . . . . . . . . . . . . . . 10-13 Assigning Default Process Templates . . . . . . . . . . . 12-113, 12-115 Associated les import ug_import . . . . . . . . 16-33, 16-36 attribute . . . . . . . . . . . . . . . . . . . . 3-15 Auto Assign . . . . . . . . . . . . . . . . . 12-35 B Benets of the CM Application Benets of the ECM Application . . . . . . . . . . . . BOMView Types . . . . . . . . . . . . BOMViews and BOMView Revisions . . . . . . . . . . . . . . . . . Business Modeler . . . . . . . . . . . . Business Modeler Deep Copy Rules . . . . . . . . . . . . . . . . . . . . Business Modeler Extension Rules . . . . . . . . . . . . . . . . . . . . Business Modeler Import/Export Rules . . . . . . . . . . . . . . . . . . . . C Change Object Folder Structure EC Folder Structure . . . . . . . class . . . . . . . . . . . . . . . . . . . . Class Attribute Tree . . . . . . . . Classes, Types and Properties . Command Line Keywords with ug_import . . . . . . . . . . . . . . . Command Suppression . . . . . . . . . . . . . . . . . . 13-5 3-15 . 4-6 3-14

. . 13-2 . . . 6-9 . . 15-5 . . 14-7 . 14-54 . 14-41 . 14-61

Command Suppression Dialog . . . . 14-3 Compound Property Rules . . . . . . 14-27 establishing . . . . . . . . . . . . . . . 14-37 Controlling the Workow with Process Templates . . . . . . . . . . . . . . . . . . 12-7 Course Description Introduction class overview . . . . . . . . . . . . 11 Create a Query that Finds Home Folders . . . . . . . . . . . . . . . . . . . . . . 8-7 Create New Dataset and Import File . . . . . . . . . . . . . . . . . . . . . . . 5-21 Create Part Files . . . . . . . . . . . . . . 15-6 Create Status Types . . . . . . . . . . . . . 9-5 Creating a Group . . . . . . . . . . . . . . . 2-9 Creating a Multi-Task Process . . . 12-51 Creating a Person . . . . . . . . . . . . . 2-12 Creating a Process Template that Does Not Require Signoff Creating a Process Template that Does Not Require Signof . . . . . . . 12-13 Creating a Single Signoff Release Process . . . . . . . . . . . . . . . . . . . 12-14 Creating a Sub-Group . . . . . . . . . . 2-10 Creating a User . . . . . . . . . . . . . . . 2-13 Creating a Volume . . . . . . . . . . . . . 2-31 Creating Accounts with the make_user Utility . . . . . . . . . . . . . . . . . . . . . 2-39 Creating an Account Interactively . . 2-7 Creating Change Types . . . . . . . . . 13-6 Creating Process Templates . . . . . . 12-8 Creating Saved Queries . . . . . . . . . . 8-2 D Dataset Objects . . . . . . . . . . . . . . . . 5-2 Dataset Type using the Standard Method . . . . . . . . . . . . . . . . . . . . 5-12 Dataset Type using the Wizard . . . . 5-6
Teamcenter Engineering Application Administration Index-1

. . 16-16 . . . 14-2

Index

Defaults standard NX defaults . . . . . . . . 15-36 E EC Folder Structure Affected Items . . . . . . . . . . . . . . 13-5 Problem Items . . . . . . . . . . . . . . 13-5 Solution Items . . . . . . . . . . . . . . 13-5 Editing the Rule Tree . . . . . . . . . . 10-24 Environment Variable Settings for NX Integration . . . . . . . . . . . . . . . . . 15-35 Exporting and Importing the Rule Tree from a File . . . . . . . . . . . . . . . . . 10-33 Exporting the Access Manager Rule Tree . . . . . . . . . . . . . . . . . . . . . . 10-34 F Fail-safe Volumes . . . . . . . . . . . . . . File Management System FMS . . . . . . . . . . . . . . . . . . . . . . File Management System (FMS) . . Files ug_import mapping les . . . . . . . . . . . Form Types . . . . . . . . . . . . . . . . . . Forms using schema editor to add POM classes . . . . . . . . . . . . . . . . . . H Handlers, EPM CR-assert-targets-checked-in demote on reject . . . . . . . . . . disallow-adding-targets . . . . How Rules-Based Protections Work . . . . . . . . . . . . . . . . . . . How to Use this Manual . . . . . . I IMAN_DATA Directory . . . . . . . 1-3, 1-6 IMAN_ROOT Directory . . . . . . . 1-31-5 IMAN_ugmaster_name_separator . . 15-34 Import
Index-2 Teamcenter Engineering Application Administration

2-33 2-28 2-29

16-20 . 3-2

. 4-6

part les into folder other than Newstuff . . . . . . . . . . . . 16-18 Import a Non-Master Drawing File . . . . . . . . . . . . . . . . . . . . . . 16-30 Import Assembly with Map File and Search File . . . . . . . . . . . . . . . . . 16-19 Import Component/Assembly Parts without a Map File . . . . . . . . . . . 16-17 Import Files Associated to a Master Part File . . . . . . . . . . . . . . . . . . . . . . 16-33 Import Files Associated to the DWG (Non-Master) Part File . . . . . . . . 16-36 Import Files Using a Full Map File . . . . . . . . . . . . . . . . . . . . . . 16-38 Import Log File . . . . . . . . . . . . . . 16-25 import_export_business_rules utility . . . . . . . . . . . . . . . . . . . . 14-68 Importing an Access Manager Rule Tree . . . . . . . . . . . . . . . . . . . . . . 10-35 Importing Files Interactively . . . . . 5-20 Importing Files Using the import_le Utility . . . . . . . . . . . . . . . . . . . . . 5-26 Importing Non-CAD Files into an Item . . . . . . . . . . . . . . . . . . . . . . 16-44 Introduction to Using Command Line Keywords . . . . . . . . . . . . . . . . . . 16-12 Introduction to Using Mapping Files . . . . . . . . . . . . . . . . . . . . . 16-11 Item Structure and Named References . . . . . . . . . . . . . . . . . . 15-3 Item Type Wizard . . . . . . . . . . . . . 4-21 Item Types . . . . . . . . . . . . . . . . . . . 4-2 L List of Values for Form Data . . . . . 3-18 Lock part les . . . . . . . . . . . . . . . . 15-9 LOV . . . . . . . . . . . . . . . . . . . . . . . 3-18 M Mapping les ug_import . . . . . . . . . . . . . . . . . 16-20 Methods key denitions . . . . . . . . . . . . . . 3-15
UGS, All Rights Reserved MT14350-SG-100

. . 12-34 . . 12-33 . . 12-34 . . 10-13 . . . . 13

Index

Modify Access to a Query . . . . . . . . 8-14 Modify Command Suppression Denitions . . . . . . . . . . . . . . . . . . 14-4 Modify Single Object Protections . . 10-10 Modify the Blazing Blades Preferences . . . . . . . . . . . 7-5, 7-8, 7-12 N Named ACLs . . . . . . . . . . . . . . . . Naming Rules . . . . . . . . . . . . . . . establishing . . . . . . . . . . . . . . . NX / TcEng Terms . . . . . . . . . . . . . NX Customer Default Files for NX Integration . . . . . . . . . . . . . . . . . NX Data Import introduction to . . . . . . . . . . . . . . NX Integration Import Scenarios . . . . . . . . . . . . . . . . . . O Object-based Protections . . . Objects Workspace manifestations . . . . . . specications . . . . . . . Occurrence Note Types . . . . Organization tips in creating . . . . . . . . . Organize the NX Seed Parts Folder . . . . . . . . . . . . . . . . Overview of Importing Files . Overview of TcEng Workow Overview of ug_import Capabilities . . . . . . . . . . . . P Part les import into folder other than Newstuff . . . . . . . . . . . . 16-18 lock . . . . . . . . . . . . . . . . . . . . . . 15-9 Parts create from UG what happens in TcEng . . . . 15-6 revisions
UGS, All Rights Reserved

10-15 14-13 14-16 15-2 15-36 16-2 16-13

. . . . . 10-3

. . . . 15-12 . . . . 15-12 . . . . . . 6-4 . . . . . 2-16 . . . . 15-14 . . . . . 5-19 . . . . . 12-2 . . . . 16-10

what happens in TcEng . . . . 15-7 seed Seed parts . . . . . . . . . . . . . 15-11 Parts and Assemblies to be Imported . . . . . . . . . . . . . . . . . . . 16-3 Person, User, Role and Group . . . . . . 2-2 Preference Setting Hierarchy . . . . . . 7-2 Preference Settings for NX Integration . . . . . . . . . . . . . . . . . 15-33 Preference Settings to Consider . . . . 7-3 Preference Settings to Consider for NX Integration . . . . . . . . . . . . . . . . . 15-34 Preferences IMAN IMAN_ugmaster_name_separator . . 15-34 Prepare to Import Unigraphics Data . . . . . . . . . . . . . . . . . . . . . . 16-5 primary type . . . . . . . . . . . . . . . . . 3-15 Process Model Design for Change Management EC Folder Structure . . . . . . . . . 13-15 Process Templates for NX Related Data . . . . . . . . . . . . . . . . . . . . . 15-31 Process Terms and Functionality . . 12-4 Product Structure Editor (PSE) revision rule criteria . . . . . . 9-129-13 Properties key denitions . . . . . . . . . . . . . . 3-15 property . . . . . . . . . . . . . . . . . . . . 3-15 Property Rules . . . . . . . . . . . . . . . 14-26 establishing . . . . . . . . . . . . . . . 14-29 Protection of objects . . . . . . . . . . . . 15-9 Q Query Searching the database . . . . . . . . . 8-2 Quick Release Technique . . 12-2612-27 R Releasing Previously Imported Data . . . . . . . . . . . . . . . . . . . . . 16-46 Result of Releasing Data with a Process . . . . . . . . . . . . . . . . . . . . 12-5 Review of the TcEng Process Model . . . . . . . . . . . . . . . . . . . . . . 12-3
Teamcenter Engineering Application Administration Index-3

Index

Revision rules PSE criteria . . . . . . . Revision Rules Review . Revision Rules Setup . . Rules-based Protections S

. . . .

9-129-13 . . . . . 9-6 . . . . . 9-8 . . . . 10-2

type . . . . . . . . . . . . . . . . . . . . Type Display Rules . . . . . . . . establishing . . . . . . . . . . . . Types key denitions . . . . . . . . . . Types of Engineering Changes Change Types . . . . . . . . . . . U

. . . . 3-15 . . . . 14-8 . . . . 14-9 . . . . 3-15 . . . . 13-4

Schema Editor Schema Editor Utility Create a Class . . . . . . . . . . . . 4-7 Delete a Class . . . . . . . . . . . . 4-8 Schema Tree . . . . . . . . . . . . . . . . . . 4-6 Search Searching the database . . . . . . . . . 8-2 Searching the database . . . . . . . . . . 8-2 Seed Part Preferences . . . . . . . . . 15-13 Seed Part Setup . . . . . . . . . . . . . . 15-11 Seed parts . . . . . . . . . . . . . . . . . . 15-11 TcEng storage . . . . . . . . . . . . . 15-11 Setting Object-based Exception Privilege Data . . . . . . . . . . . . . . . . . . . . . . 10-9 Setting the TcEng Classroom Environment . . . . . . . . . . . . . . . . . 1-9 Some Useful Canned Handlers . . . 12-33 Status Types for Release Status . . . . 9-2 Storage of Associated Files . . . . . . . 15-8 Structure lock . . . . . . . . . . . . . . . . . . . . . . 15-9 Student Responsibilities . . . . . . . . . 12 Sub-type . . . . . . . . . . . . . . . . . . . . 3-15 T TcEng Data Protections TcEngi-Man Data Protections . . . 10-2 TcEng Environment Variables . . . . . 1-7 TcEng Install Directory Structures . . 1-3 IMAN_ROOT . . . . . . . . . . . . . 1-31-5 TcEng Volumes i-Man Volumes . . . . . . . . . . . . . . 2-28 Tips in Creating your Organization . . . . . . . . . . . . . . . . 2-16 TR Change Notice Process . . . . . . 13-16 Two Usage Modes with Workow . . 12-6

ug_import associated les . . . . . . . . 16-33, 16-36 check import . . . . . . . . . . . . . . . 16-18 command syntax . . . . . . . . . . . . 16-13 keywords . . . . . . . . . . . . . . . . . 16-13 login keywords . . . . . . . . . . . . . 16-16 specify part les . . . . . . . . . . . . 16-17 UGMASTER / UGPART Behavior . . . . . . . . . . . . . . . . . . 15-10 Units of Measure . . . . . . . . . . . . . . . 6-2 Units of Measure (UOM) denition of . . . . . . . . . . . . . . . . . 6-2 Use ug_import to Import the Seed Parts . . . . . . . . . . . . . . . . . . . . . 16-26 Using (Directory) Search Files . . . 16-12 Using ACLs in a Process Template . . . . . . . . . . . . . . . . . . 12-52 Using Task Handlers in a Process Template . . . . . . . . . . . . . . . . . . 12-32 Utilities make_user . . . . . . . . . . . . . . . . . 2-39 setting the TcEng environment AA . . . . . . . . . . . . . . . . . . . . . 1-8 V Verify Revision Rule Preference Settings . . . . . . . . . . . . . . . . . . . . 9-19 Viewing Data Privileges . . . . . . . . . 10-4 Volume management viewing detailed volume information . . . . . . . . . . . . . . 2-35 W What is a Change Object? . . . . . . . 13-3

Index-4

Teamcenter Engineering Application Administration

MT14350-SG-100

Reference Chart Tear Outs

These tear out reference charts are provided for your convenience.

Teamcenter Engineering Application Administration Student Prole

Name ______________________________________ Date _ Employer _____________________________________________________________ U.S. Citizen? Yes / No

When is your planned departure time? ________ am/pm In order to give the instructor and idea of your background and experience, please answer the following questions. 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 NX? _______ Version _______ Hours per week? ______ 9. What are the primary uses of TcEng at your site? __________________________________ ________________________________________________________________________________ 10. What do you model in your NX part les (castings, assemblies, etc.)? ________________________________________________________________________________ ________________________________________________________________________________

11. Please list other completed CAD/CAM or PDM courses and the provider. Course Provider

12. Please check the box that best describes your current skill level in the various TcEng/NX disciplines listed below. none NX User NX Manager User TcEng User TcEng System Admin TcEng Application Admin TcEng Development (ITK) novice intermediate advanced

Additional Comments: ____________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________ ________________________________________________________________________________

V10 Teamcenter Engineering Application Administration Course Agenda Day 1 ______

Intro Lesson 1 Lesson 2 Lesson 3 Lesson 4 Lesson 5 Course Overview Teamcenter Engineering Environment User Organization Form Types and LOVs Item Data Types Dataset Types

Day 2 ______
Lesson Lesson Lesson Lesson Lesson 5 6 7 8 9 Dataset Types(cont) Product Structure Data Types Creating and Modifying Preferences Queries and Reports Status Types and Revision Rules

Day 3 ______
Lesson 10 Lesson 11 Lesson 12 Access Manager Projects Workflow Process Modeling

Day 4 ______
Lesson 12 Lesson 13 Lesson 14 Workflow Process Modeling (cont) Change Management Business Modeler

Day 5 ______
Lesson 15 Lesson 16 Setup For NX Integration NX Integration Import and Release

Solutions For Kinematics, Dynamics, and Design of Machinery (3rd Edition) by Kenneth Waldron & Gary Kinzel
0% (1)
Solutions For Kinematics, Dynamics, and Design of Machinery (3rd Edition) by Kenneth Waldron & Gary Kinzel
54 pages
Teamcenter Client Customization Programmers Guide
No ratings yet
Teamcenter Client Customization Programmers Guide
464 pages
BMIDE
No ratings yet
BMIDE
935 pages
Rich Client Interface Guide
No ratings yet
Rich Client Interface Guide
357 pages
Teamcenter User Manual, Item Create and Workflow
100% (1)
Teamcenter User Manual, Item Create and Workflow
44 pages
Teamcenter Installation Document
0% (2)
Teamcenter Installation Document
530 pages
Server Customization Programmers Guide
100% (1)
Server Customization Programmers Guide
243 pages
Rich Client Customization Programmers Guide
No ratings yet
Rich Client Customization Programmers Guide
324 pages
Teamcenter Integration For CATIAV5 InstallationGuide PDF
No ratings yet
Teamcenter Integration For CATIAV5 InstallationGuide PDF
520 pages
Teamcenter Reporting and Analytics 13.1
No ratings yet
Teamcenter Reporting and Analytics 13.1
10 pages
TC12.2 Installation Server Windows PDF
100% (1)
TC12.2 Installation Server Windows PDF
298 pages
Whats Best Precise - Imprecise in BOM - Teamcenter Refresh Yourself
100% (1)
Whats Best Precise - Imprecise in BOM - Teamcenter Refresh Yourself
6 pages
Teamcenter Installation Document PDF
No ratings yet
Teamcenter Installation Document PDF
530 pages
Ultrasonic Examination of CNG Vehicle Cylinders As An Alternative To Periodic Hydrostatic Testing
No ratings yet
Ultrasonic Examination of CNG Vehicle Cylinders As An Alternative To Periodic Hydrostatic Testing
2 pages
TCEng Data-Management Student Guide V9
No ratings yet
TCEng Data-Management Student Guide V9
564 pages
Teamcenter Engineering Product Data Management Student Guide
100% (1)
Teamcenter Engineering Product Data Management Student Guide
620 pages
Teamcenter Admin
100% (1)
Teamcenter Admin
658 pages
Teamcenter Installation: Siemens Siemens Siemens
No ratings yet
Teamcenter Installation: Siemens Siemens Siemens
528 pages
Team Center Manufacturing User and Administrator Manual
No ratings yet
Team Center Manufacturing User and Administrator Manual
137 pages
Application Admin
No ratings yet
Application Admin
300 pages
Team Center
No ratings yet
Team Center
284 pages
Getting Started Teamcenter
No ratings yet
Getting Started Teamcenter
28 pages
Teamcenter 11.2 Getting Started With Customization: Siemens Siemens Siemens
No ratings yet
Teamcenter 11.2 Getting Started With Customization: Siemens Siemens Siemens
54 pages
Teamcenter
No ratings yet
Teamcenter
481 pages
Getting Started Dispatcher Translation MGMT
No ratings yet
Getting Started Dispatcher Translation MGMT
104 pages
FAQ Industry Professional On Teamcenter Training
No ratings yet
FAQ Industry Professional On Teamcenter Training
11 pages
TC12 Customization - (Blog 2013) PDF
No ratings yet
TC12 Customization - (Blog 2013) PDF
14 pages
NX Import Pax Files
No ratings yet
NX Import Pax Files
4 pages
Teamcenter Options and Variants
No ratings yet
Teamcenter Options and Variants
7 pages
Teamcenter PDF
No ratings yet
Teamcenter PDF
22 pages
Autologin of Teamcenter
No ratings yet
Autologin of Teamcenter
1 page
Structure Manager
0% (1)
Structure Manager
563 pages
MyTeamcenter Training Manual
No ratings yet
MyTeamcenter Training Manual
63 pages
Business Modeler
No ratings yet
Business Modeler
136 pages
Teamcenter Gateway-Installation Guide
No ratings yet
Teamcenter Gateway-Installation Guide
72 pages
Teamcenter Manufacturing. Teamcenter Active Workspace. Teamcenter UA. Teamcenter Visualization. Teamcenter MRO. Teamcenter Product Costing.
No ratings yet
Teamcenter Manufacturing. Teamcenter Active Workspace. Teamcenter UA. Teamcenter Visualization. Teamcenter MRO. Teamcenter Product Costing.
32 pages
Access Manager
No ratings yet
Access Manager
178 pages
TC Dispatcher Install and Debug With Async and NX
100% (3)
TC Dispatcher Install and Debug With Async and NX
20 pages
Create Assembly Model Top Down
No ratings yet
Create Assembly Model Top Down
8 pages
Teamcenter For Project and Program
No ratings yet
Teamcenter For Project and Program
1 page
PLM XML Export Import Admin PDF
No ratings yet
PLM XML Export Import Admin PDF
131 pages
Basic ITK Customization Concept Part-01
No ratings yet
Basic ITK Customization Concept Part-01
1 page
Access Manager PDF
100% (2)
Access Manager PDF
159 pages
client_customization_programmers_guide
No ratings yet
client_customization_programmers_guide
276 pages
NX Environment Variables
No ratings yet
NX Environment Variables
6 pages
Itk, PLM, Tcua, Teamcenter
50% (2)
Itk, PLM, Tcua, Teamcenter
4 pages
Shared Memory Best Practices Guide V1.0
No ratings yet
Shared Memory Best Practices Guide V1.0
20 pages
Best Practices Document For Project Level Security
No ratings yet
Best Practices Document For Project Level Security
7 pages
Teamcenter 10.1: Publication Number PLM00046 I
No ratings yet
Teamcenter 10.1: Publication Number PLM00046 I
481 pages
TC Create A New Tile in AW
No ratings yet
TC Create A New Tile in AW
5 pages
Workflow Designer Handlers
No ratings yet
Workflow Designer Handlers
736 pages
Workflow Designer
No ratings yet
Workflow Designer
652 pages
Report Builder
No ratings yet
Report Builder
20 pages
SolidWorks CAM 2024 Black Book
From Everand
SolidWorks CAM 2024 Black Book
Gaurav Verma
5/5 (1)
Using TC
No ratings yet
Using TC
770 pages
Software Patterns Made Easy
From Everand
Software Patterns Made Easy
Justice Nanhou
No ratings yet
ChatGPT for Business: Strategies for Success
From Everand
ChatGPT for Business: Strategies for Success
Matthew C. Smith
No ratings yet
Teamcenter 10 Utilities Reference
No ratings yet
Teamcenter 10 Utilities Reference
970 pages
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
From Everand
Blog Smarter, Not Harder: SEO, Blogging, and AI Strategies to Skyrocket Your Traffic
Jay Nans
No ratings yet
Teamcenter Installation Document PDF
No ratings yet
Teamcenter Installation Document PDF
530 pages
Teamcenter Start Guide TCM
No ratings yet
Teamcenter Start Guide TCM
146 pages
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
From Everand
Securing ChatGPT: Best Practices for Protecting Sensitive Data in AI Language Models
Matthew C. Smith
No ratings yet
Astm F50 92 1996
No ratings yet
Astm F50 92 1996
2 pages
TM - A5mwc - 1701 PDF
No ratings yet
TM - A5mwc - 1701 PDF
53 pages
TABLE-OF-SPECIFICATION-FOURTH - Quarter-Grade-1-Final
No ratings yet
TABLE-OF-SPECIFICATION-FOURTH - Quarter-Grade-1-Final
12 pages
G
No ratings yet
G
2 pages
Indifference Curves
No ratings yet
Indifference Curves
18 pages
CHAPTER - 3 - Logic - Circuits
No ratings yet
CHAPTER - 3 - Logic - Circuits
12 pages
ClearSpan-Specs-Span-Chart
No ratings yet
ClearSpan-Specs-Span-Chart
4 pages
SOR_Description_CC18276
No ratings yet
SOR_Description_CC18276
21 pages
Class 11 Physics Sample Paper Set 11
No ratings yet
Class 11 Physics Sample Paper Set 11
12 pages
Electricneutron-Star Delta Motor Connection
No ratings yet
Electricneutron-Star Delta Motor Connection
7 pages
9780133354690
No ratings yet
9780133354690
3 pages
Manual EN
No ratings yet
Manual EN
11 pages
Baulkham Hills 2014
No ratings yet
Baulkham Hills 2014
21 pages
The Scoop On Poop 2019 Country Living Expo Classes #123 & #223
No ratings yet
The Scoop On Poop 2019 Country Living Expo Classes #123 & #223
33 pages
Lna Project PDF
No ratings yet
Lna Project PDF
56 pages
Chem Ch6 NIE Premium NOtes
No ratings yet
Chem Ch6 NIE Premium NOtes
17 pages
Case Problem Rubrics (SIDM)
No ratings yet
Case Problem Rubrics (SIDM)
1 page
Your Newly Designed Bill: At-a-Glance Bill Summary
No ratings yet
Your Newly Designed Bill: At-a-Glance Bill Summary
2 pages
ACtivity 4
No ratings yet
ACtivity 4
2 pages
Advances in Optical Metalenses: Nature Photonics
No ratings yet
Advances in Optical Metalenses: Nature Photonics
10 pages
Influence of Transformers On Harmonics: Equation (1) Dyn5
No ratings yet
Influence of Transformers On Harmonics: Equation (1) Dyn5
4 pages
How Do Tornadoes Form
No ratings yet
How Do Tornadoes Form
1 page
Identifying and Analyzing Safety Critical Maneuvers From High Resolution AIS Data
No ratings yet
Identifying and Analyzing Safety Critical Maneuvers From High Resolution AIS Data
9 pages
Implemen Ntation of Fofdmb Baseband T Transmitt Fpga Ter Compli Iant IEEE E STD 802.1 16d On
No ratings yet
Implemen Ntation of Fofdmb Baseband T Transmitt Fpga Ter Compli Iant IEEE E STD 802.1 16d On
5 pages
Chemistry Chapter 4
No ratings yet
Chemistry Chapter 4
15 pages
Roger Penrose - Is Quantum Mechanics Relevant To Understanding Consciousness
No ratings yet
Roger Penrose - Is Quantum Mechanics Relevant To Understanding Consciousness
7 pages
Support Material - Grade 7 Comparing Quantities
No ratings yet
Support Material - Grade 7 Comparing Quantities
5 pages
Inkscape Keyboard Shortcuts
No ratings yet
Inkscape Keyboard Shortcuts
39 pages