1|P a g e

Jawad Saleem

Teamcenter
Notes
2|P a g e
Jawad Saleem

Contents
Introduction.....................................................................................................................................................4

Teamcenter Architecture.................................................................................................................................4

My Teamcenter ...............................................................................................................................................8

Teamcenter: ................................................................................................................................................8

Item: ............................................................................................................................................................8

Item Revision:.............................................................................................................................................8

Item master-form: .......................................................................................................................................9

Item Revision Master-form: .......................................................................................................................9

Dataset: .......................................................................................................................................................9

Purge:..........................................................................................................................................................9

Check-Out & Check-In:..............................................................................................................................9

Named References: ...................................................................................................................................10

Organization .................................................................................................................................................10

Structure Manager.........................................................................................................................................11

Comparison:..............................................................................................................................................12

Precise and Imprecise: ..............................................................................................................................12

Pack and Unpack: .....................................................................................................................................13

Variant: .....................................................................................................................................................13

Classic Variants: ...................................................................................................................................13

Modular Variants:.................................................................................................................................14

Effectivity: ................................................................................................................................................14

Occurrence Effectivity: ........................................................................................................................14

Revision Rule: ......................................................................................................................................15

Revision Effectivity: .............................................................................................................................15

Command Suppression .................................................................................................................................16

Authorization ................................................................................................................................................16

Query Builder ...............................................................................................................................................17

Utilities References ......................................................................................................................................18

PLM XML Export and Import ......................................................................................................................18

3|P a g e
Jawad Saleem

Classification ................................................................................................................................................19

Workflow ......................................................................................................................................................24

Handlers ....................................................................................................................................................28

Action Handler: ........................................................................................................................................28

Rule Handlers: ..........................................................................................................................................29

BMIDE (Business Modeler Integrated Development Environment) ............................................................30

Rules: ........................................................................................................................................................31

Naming rules: .......................................................................................................................................31

GRM rule:.............................................................................................................................................31

DEEP COPY RULE: ............................................................................................................................32

Display Rule: ........................................................................................................................................33

Types of Properties/Attributes ..................................................................................................................34

Lists of Values (LOVs).............................................................................................................................37

Style Sheet: ...................................................................................................................................................39

Deployments: ............................................................................................................................................46
4|P a g e
Jawad Saleem

Introduction
Product life cycle management (PLM) is a tool or a process of managing entire lifecycle of a
product from inception(idea) through engineering design and manufacture to service and
disposal of manufacturing products. It connects different departments like design,
manufacturing, service, sales at common origin where product information flows across them
and manages the data.

Purpose: To ensure company develops has optimum quality, profitability, and customer
impact.

Functions:

• Manages documents related to a product such as design, blueprint, and bill of

material.
• Storing Project data and electronic files.
• Assigning tasks to team members.
• Controlling accessors
• Identifying and streamlining a specific workflow

Teamcenter Architecture
Teamcenter Architecture:

Teamcenter consists of two types of Architecture.

• 2-Tier Teamcenter architecture.

1. Client tier (End user machine)-
This layer contains rich client, Teamcenter server and executables and other
additional applications like TCVIS, NX that integrate with rich client.
2. Resources tier (Database & volume data server)-
This layer contains metadata and files managed by the system. It
accommodates Database server, volume, file server.
• 4-Tier Teamcenter architecture.
1. Client tier –
5|P a g e
Jawad Saleem

This layer contains client application process user interface input & output and
host secure file cache. It has also other additional applications that integrate
with both rich client, thin client and also Teamcenter network.
2. Web tier –
This layer handles client installation, process logon request, transfer client
request to business logic, server’s static content to client and handles
communication between the client and enterprise tier.
▪ Java based and served on a J2EE web application server such as
WebLogic.
▪ .NET based and served on IIS server./.NET web-based application
server.
3. Enterprise tier –
Host business logic, applies security rules, retrieves data from and stores data
in the database and serves dynamics content to client. A pool of server process
managed by a server manager (Four tier architecture only)
▪ Transient volumes.
4. Resource tier –
This layer stores persistent metadata and files managed by Teamcenter.
▪ Database server & Database, standard volumes.

Comparison of 2-tier & 4-tier:

2-Tier 4-Tier

1.It contains 1.It contains

-Client tier -Client tier

-Resource tier -Web tier

-Enterprise tier

-Resource tier

2.On opening one can find TAO window 2.On opening one can find TAO window
present. NOT present.

3.It support rich client interface. 3.It support rich client & thin client.
6|P a g e
Jawad Saleem

4.It recommended to work on LAN 4.It is recommended to work on high-

environment. latency WAN’s.

5.It require low latency (ping time) 5.Any client does not present on the same
between client tier and the resource tier. LAN as the web & enterprise tiers should
be deployed as 4-tier.

6.For latencies under 5ms, it is preferred. 6.For latencies up to 300ms,it is preferred.

FMS (File Management System):

File management system is one of the Teamcenter components for managing files in
Teamcenter. FMS is responsible for all transaction related to files from Teamcenter server
and client server.

• FMS is independent tool which run as service in server and client machine.
• Teamcenter application tier and client tier interact with FMS framework HTTP or
HTTPS protocol.

FSC (FMS server cache):

FSC is service which running in server side or basically cache file in server machine.

FCC (FMS client cache):

FCC is service which running in client side or basically cache file in client machine.

TCCS (Teamcenter client communication system):

Teamcenter client communication system (TCCS) manages communication and file transfers
between Teamcenter clients and servers.

TCCS contains the FMS client cache (FCC), which uploads files from a workstation to a
Teamcenter volume and also downloads requested files from the volume to a workstation.

tc volume:

It is Teamcenter directory which stores the physical file such as pdf, excel files etc. We can
do operation on it

tc route:
7|P a g e
Jawad Saleem

It is a Teamcenter application directory which contains Teamcenter binary executive tables

and files-based installation.

It stores Item id and data in tabular form that is metadata we cannot perform operation on it.

tc data:

It is Teamcenter data directory which contains RDBMS (Rational Database Management).

Difference between Volume and Database

• Volume is used to store physical files such as pdf, draft.

• Databases are used to store metadata files (data like Item Name, Item Id).

Rich client & Thin client:

• Rich client:
It is the application with large sets of configurations where client machine is directly
communicated with the database.
The rich client interface is mostly used by authors, manufacturing authors,
administrators to
o Manage the design and configuration of product data.
o Construct and preserve Teamcenter process & structures.
o Design and preserve Teamcenter.
o Access data stored in the Teamcenter database.
o It is available on 2-tier & 4-tier as well.
• Thin client:
It is the browser-based application with lighter configuration where request is sent
from client to web application server, then web application server to business logic
application server via pool manager then to database.
o The thin client interface is used by consumers, manufacturing consumers and
reviewers to
▪ look data, including product structure and variant information in web
based.
8|P a g e
Jawad Saleem

▪ Approve data attached to a workflow task.

▪ Visualize 2D drawings & 3D model
o It is only applicable to 4-tier.
o The thin client interface is ideal for suppliers, production staff and other users,
who do not require extensive authority or administrative access to Teamcenter.
o It does not support administrative functions or integrations with other
applications.

My Teamcenter
Teamcenter:
Teamcenter is a Product Lifecycle Management platform. Teamcenter is used to organize
your product information, create objects, perform CICO (Check In/Check Out), task
management, query execution, perform and track tasks in your inbox, send and receive
TcEng mail, conduct searches, create, and manage data.
OR
Teamcenter is a Product Lifecycle Management tool. It allows user to edit product data and
processes such as 3D design, embedded software, documentation, and bill of material.

Item:
An item is a fundamental object used to manage information in Teamcenter Engineering.
OR
It is a folder that contains all the information required to manufacture a product.
An item is a fundamental object which contain all the information required to manufacture a
product.

Steps to create item: shortcut (crtl + t)

➢ Select Home in my Teamcenter
➢ Open File, select new
➢ Select Item
➢ Select type of the object “ex. Item”
➢ Enter details
➢ Finish

Item Revision:
Item revisions are used to manage and store specific information about a particular revision
of an Item.
An item revision can contain different types of Forms and Datasets.
9|P a g e
Jawad Saleem

Step to create revise:

➢ Select revision
➢ Open “File” select revise
➢ Enter details
➢ Finish

Item master-form:
All the properties related to the item is stored in the master-form.

Item Revision Master-form:

All the properties of item revision stored in item revision master form.

Dataset:
Dataset used to manage data files created by non-Teamcenter Engineering applications.
Datasets typically stored in Item Revisions.
A dataset is an object that stores and manages a collection of data files for a particular
application and purpose.

Steps to attach dataset: shortcut (ctrl + d)

➢ Select item revision
➢ Open “File” selects new
➢ Select Dataset
➢ Enter name or descriptions
➢ Select file type from left side column or more
➢ Import file form directory
➢ Select item relation (default relation is “specification”)
➢ OK / Apply

Purge:
Purge is used to permanently remove old version of a dataset from the dataset.
We can select whether to purge all old version or specific version of a dataset.

Check-Out & Check-In:

Check-Out >>>>Editing the object
Check-In >>>>>>Saving edited object
Check-Out and Check-In procedures used to ensure that two users do not simultaneously
update database objects.
Implicit Check-Out: An Implicit Check-Out is performed automatically by the system.
Explicit Check-Out: An Explicit Check-Out is performed manually by the user.
10 | P a g e
Jawad Saleem

Named References:
Named Reference are Teamcenter objects that relate to a specific data file. (It is associated
with the physical file)
A single dataset object may have one or more Named References. To see this in my TC click
on View-Named Reference.
Named References is used to manage dataset files.
Steps to change or add named references:
➢ Select dataset
➢ Check-Out dataset
➢ Right click on dataset select name references
➢ Upload or delete or change name references
➢ Close
➢ Check-In dataset

Organization
Organization is a module of Teamcenter used to create group, roles, and users according to
organization needs.
Organization window has:
Organization tree: To view Structure of Organization
Organization List tree: To view manage the components of our organization by
listing group, roles discipline, users, and person.

Person: Definition is containing real-world information about each Teamcenter user, such
as name, address, and telephone number. Person definitions are stored as simple text
strings so that they can be easily changed and updated. The name must be unique.

User: Definition that is the mechanism by which Teamcenter identifies and interacts
with each user. User definitions contain a name (derived from the person definition),
user ID, operating system name, and password.

Role: In Teamcenter Engineering, a role is an object that models the type of work a user is
expected to perform in a particular Teamcenter Engineering group. One group can have
many roles.

Group: A group defines a list of selected roles for the group. There can be multiple roles per
group.
11 | P a g e
Jawad Saleem

Steps to create group:

➢ Open organization module
➢ Select organization in middle column
➢ Enter group name or description
➢ Default volume “volume”
➢ Click create group
Steps to create role or sub-group:
➢ Select group in which you want to create role or sub-group
➢ Click add role or add sub-group
➢ Select add new role to group
➢ Enter name or description
➢ Finish
Steps to create user:
➢ Select role in which you want to create user
➢ Clock add user
➢ Select add new user in role
➢ Enter person name, user ID, OS name and password
➢ Finish

Structure Manager
Structure manager is an admin application which is used to create and edit product assembly.

Structure Manager allows you to create generic product structures that can be configured to
show the

product structure at a particular time or for a certain unit, for example:

• The current production design of the product.

• The product structure that was effective on a certain date.
• A particular customer variant.

EBOM: Engineering Bill of Materials, It contain engineering design items

MBOM: Manufacturing BOM, in this BOM item manufacture or design by our company and
it also has EBOM items. the MBOM is focused on the parts that are needed to manufacture a
product.

Steps to open item in structure manager:

➢ In my Teamcenter
➢ Right click on item which you want to open in structure manager
12 | P a g e
Jawad Saleem

➢ Open send to and select structure manager

➢ File is open in structure manager

Comparison:
This function is used to compare two different BOM or items assembly in structure manager.

Streps to use comparison:

➢ Open item in structure manager

➢ Click “split the window in two” it is open new window.

➢ Click on new window, after click open my teamcenter and open item you want to
compare
➢ Click on any item open “Tools”
➢ Click “Compare”
➢ Select Mode: multi-level (with find no)
➢ Apply
➢ To clear comparison in “Tool” click “clear compare”

Precise and Imprecise:

Precise: We use precise option to fix or freeze the BOM view structure even after user makes
some modifications in the structure. Or changes the precision of the selected assembly (line).

− Only Precise Structure will be used for manufacturing purpose.

Imprecise: Imprecise option is used to show the structure as per the Revision Rule.

Steps to apply precise and imprecise: shortcut (ctrl + shift + F)

➢ In structure manager
➢ select item or multiple items which you want to apply precise
➢ open “Edit” select “Toggle Precise/imprecise”
➢ Colour of selected items line will change if precise is apply (to Green Colour).
➢ To remove precise repeat above same steps
13 | P a g e
Jawad Saleem

Pack and Unpack:

Pack: Packs the selected lines so that all lines with the same item revision and find number
are displayed as a single line. The actual quantity of lines is appended to the node.

Unpack: Unpacks the selected packed lines so that they are displayed as separate lines, one
for each occurrence.

For Packing lines, certain attributes should need to match. For example, Find Number,
Revision Number etc.

Variant:
It is the functionality for managing sub-assemblies that allows you to create the options and
its values and associate there with item revision.

Classic Variants:
Classic Variants allow you to create options (for example, color) and allowed values of those
options (for example, red and blue) and associate them with an item revision. You usually do
this at a top-level assembly, but you can implement variants anywhere in the structure. You
then define a variant condition (for example, only load IF option color = value red is
specified in the variant rule) on those occurrences that are subject to variant rules.

Steps to apply classic variants:

➢ In structure manager
➢ Fist we have to create variant condition

▪ Click Show/Hide data panel on toolbar

▪ Click on Show Legacy variant data panel

▪ Select “options”
▪ Enter Name and Description
▪ Enter “values” and click add Button (plus logo)

▪ After entering all values click add option

▪ Click save variant data

➢ Apply the variant condition
▪ Select item which you want to attach condition
▪ Open “Edit”
▪ Click “variant condition”
14 | P a g e
Jawad Saleem

▪ In option select variant

▪ In value select value

▪ Click “Appends after last line”

▪ Ok
➢ To view specific variant value items, we have to select custom variant search
▪ Select parent item

▪ Click “set option value of selected module”

▪ In “option” select variant
▪ In “value” select value
▪ Ok
▪ Open “View”
▪ Click “show unconfigured variants”

Modular Variants:
Modular Variants enable Option definitions and Constraints to be encapsulated to that area of
the structure, the Module, where the option definitions are used.

Effectivity:
Effectivity is used to configure the product structure. We use effectivity to set if a Revision
should appear in the structure or not. Or Effectivity is used to Manage the BOM view
structure in an item.

Occurrence Effectivity:
We configure either we want some particular item revision should occur in the structure or not.
Steps to apply occurrence effectivity:
➢ Add effectivity to revisions
▪ Select sub\child revision (occurrence effectivity does not attached to root\parent
revision)
▪ Open “Tools”
▪ In “Effectivity” open “Occurrence Effectivity” select “View Edit and Create”
▪ Enter revision Id
▪ Add dates in (From Date or To Dates)
▪ Ok
➢ Add revision rule to view specific date revisions
▪ Open “Tool”
15 | P a g e
Jawad Saleem

▪ Open “Revision rule” and select “Set Date/unit/end item”

▪ Effective date: enter specific date you want to set
▪ End item: enter parent/root Id
▪ Ok
➢ To view set date revision
▪ Open “View”
▪ Check “Show Unconfigured by Occurrence Effectivity”

Revision Rule:
We use Revision Rule to set which particular revision should occur or appear in the structure.
Revision configuration allows you to select appropriate revision of the components in the
product structure.
Steps to create or modify the revision rule:
➢ Open “Tool”
➢ Click on “Revision Rule” and select “Create\Edit” option
➢ After window open click “create” option.
➢ Enter details name, decs.
➢ Open option on bottom right and select type of “revision rule”.
➢ After selecting revision rule criteria click “append” option, you can add multiple
criteria.
➢ Click OK.

Revision Effectivity:
We use Revision Effectivity to fix to which particular revision should appear in the structure
for user defined range of dates/units. To put revision effectivity the Revision must have
released status.

Steps to apply revision effectivity:

➢ Note: revision effectivity only applies to release items

➢ Open “Tool”
➢ Open “Effectivity” and select “Revision Effectivity”.
➢ Select Release status and click “Edit”
➢ Add range of date or quantity of unit.
➢
16 | P a g e
Jawad Saleem

Command Suppression
It is used to restrict functionality of Teamcenter for specific group or role Ex, creating new
items. Or it is used to suppress the display of menus and commands.

Steps:

1. Open the Command Suppression application in Teamcenter

2. Select the Organization
3. Select the Group and Role
4. Select the Application which want to Hide/Show
5. Select the menu bar want to Hide/Show
6. Save and login with group selected.

Authorization
It is used to give administrative authorization or full access of modules and functions to
specific group or roles.

It is the application in Teamcenter which is used to grant user access to administrative

applications and utilities.

It is helpful in giving administrative application access to non-DBA user.

Steps:

1. Open the Authorization application in Teamcenter

2. Select the Group and role
3. Select the Application to give full access
4. Drag it from left to right
5. Save
6. Login from same group user and access the application.
17 | P a g e
Jawad Saleem

Query Builder
The Query Builder application in Teamcenter allows you to create customized searches for
objects in both local and remote Teamcenter databases.

Building query definitions requires knowledge of the Teamcenter POM (persistent object
manager) schema, which is a hierarchical arrangement of classes, subclasses, and attributes.
Query definitions, also called saved queries.

Saved Queries: One of the most important features that any PDM solution can provide is the
ability to search the database for various kind of product information.

Attributes:

User Entry L10N Key:

Name:

Operators:

Default Value:

Steps:

1. Open Query Builder module

2. Select any query from saved query list and click “Clear”.
3. Enter Name and Description.
4. Select “Search Type”, Ex. Item, Item Revision, Custom Item.
5. Modifiable Query type: Local Query.
6. Display Setting: All Properties, Real Name.
7. Add Search Criteria by double clicking on Property Selection files, ex. Item_id,
object_name.
8. After All selection click “Create” option.
18 | P a g e
Jawad Saleem

Utilities References
Utilities references is the module in Teamcenter where you can perform the various action
and task of Teamcenter by using command line.

Steps:

1. Open tc_config1 Command Prompt

2. Enter cd.. click enter after that enter cd bin enter, after this write you commands.
Command for login is -u=user, -p=password, -g=group.
• Creating User
o This utilities is used to create user .
o make_user.exe -u=infodba -p=infodba -g=dba -user=user name -
group=group name -person=person name.
• plmxml export and import
o This utilite is used to export data to PLM XML format.
o Plmxml_export.exe -u=infodba -p=infodba -g=dba -xml_file=file path
• export dataset
• export workflow template

PLM XML Export and Import

It is used to export and import data from Teamcenter in PLM XML format.

• Transfer mode
o Transfer mode is the logical groupe of clouser rules claouses. Transfer modes
allow end user to export or import data by knowing that only the transfer mode
name that they must use.
• closer rule
• Filter rule
• Property set
o Property set define the properties you want to export in the report.

Export custom item

Export custom properties item

19 | P a g e
Jawad Saleem

Classification
The Classification application utilizes a classification hierarchy to categorize company’s
product data. As the system administrator, you use Classification Administration to define the
groups, classes, and views that form the classification hierarchy.
Classification is uses to categorized and classify Teamcenter object.

Classification Hierarchy:
The classification hierarchy shows a tree structure of nested classes. It provides an overview
of all classification classes contained in the database. These classes contain a compilation of
attributes related to a group of objects.

Group:
Groups are the highest level in the classification hierarchy. A group labeled fasteners could
be established to organize all the fasteners used by your company. Groups can also be nested
to include other groups.

Classes:
Classes represent the next level in the classification hierarchy. A class defines, and is defined
by, the composite attributes of all storage classes associated with the class. A class can have
multiple alias names, allowing you to search for it by one of these names in addition to its
primary name. These names are indicated in the class tool tip in the classification hierarchy.

*Limit of string in Classification is 256 Characters only.

Create a class
The process of creating a class consists of identifying the class in the database, assigning
attributes to the class, assigning properties to the attributes, and saving the class definition.

1. Click the Hierarchy tab. Teamcenter displays the Hierarchy pane.

2. Display the Add New Class dialog box using one of the following methods:
a. Choose the group, abstract class, or storage class in the hierarchy tree that will be
the parent of the new class.
b. Click the Add Class button located at the bottom of the class definitionpane.
20 | P a g e
Jawad Saleem

3. Enter a class ID in the Add New Class dialog box and click OK
4. Type a name for the class in the Name box.
5. Click metric, nonmetric, or both to specify the system of measure to be applied to the
attributes of the class.
6. Specify whether the class is abstract or storage.
7. Save the model
21 | P a g e
Jawad Saleem
22 | P a g e
Jawad Saleem

Abstract classes:
Abstract classes are typically used to store objects that share a major set of characteristics
(attributes). The attributes assigned to the abstract class are then inherited by any and all child
classes. Abstract classes can have other abstract classes as well as storage classes as children.
OR
Class used to combine common attributes for use in storage classes. Classification instances
cannot be stored in abstract classes.

Storage classes:
Storage classes are defined by a combination of the inherited attributes of the parent classes
along with attributes that are specific to the storage class. Storage classes can hold parent,
child, and leaf node positions in the hierarchy.
OR
Class in which Classification instances (ICOs) are stored. Storage classes can be positioned
anywhere in the hierarchy, including the leaf node position.
Dictionary:
Dictionary ensures that there is a consistent definition for all attributes regardless of the
classes in which they are used.
• Classification Admin enables users to view the attributes contained in the dictionary
and use the search function to locate attributes.
• Create classification instances of workspace objects by associating the objects with a
specific class and assigning values to the attributes corresponding to the class.

LOV’s:
1) Click the Key LOVs tab. Teamcenter displays the LOVs tab.
2) Create a new instance, LOV id tab open.
3) Enter the id and ok,
4) Enter the name of LOV
5) Add the values in same LOV
6) Save the data.
23 | P a g e
Jawad Saleem
24 | P a g e
Jawad Saleem

Workflow
Workflow is used to manage production procedure activity in which document, information
and task is pass from one user to another user in mode that is set of standards well define
according to rules and action.

A workflow in Teamcenter allow you to manage one is related to product data and help in
accommodating one’s business procedure.

It is an application in the TC Eng. which allows you to create, modify and delete the
workflow process templates.

Workflow designer allows user to graphically create workflow procedure and set key
characteristics about the procedure.

Workflow Process Templates

Workflow process templates are blueprints of a workflow process defined by workflow such
as perform signoff, route, and checklist in the required order of performance. Addition to
process requirement, such as quorums and duration time is also done by workflow handler.

Workflow Task Templates

It is the blueprint of workflow task. A task is a fundamental building block used to construct
a process. Each task defines the set of actions, rule, and resource to accomplish the task.

• Do Task
o Most frequently used task. Use the Do task to define actions for a user to
complete. It has “EPM-Hold” rule handler to stop the task automatically for
the user to perform a manual activity. It supports success and failure paths.
Complete confirms the completion of a task and triggers the branching to a
success path. Unable to Complete indicates the task is unable to complete and
triggers the branching to a failure path.

• Review Task
25 | P a g e
Jawad Saleem

o Use the Review task to route workflow targets for review. The task includes
two subtasks, “select-signoff-team” and “perform-signoffs”.
▪ The select-signoff-team subtask requires the workflow process
initiator to select the users who will perform the review (the signoff
team).
▪ The perform-signoffs subtask is then distributed to the selected
signoff team, prompting them to review the target objects and signoff.
o When this task is performed in a workflow process, the perform-signoffs task
displays three options to each signoff team member: Approve, Reject, and No
Decision. Selecting either Approve or Reject performs the task. No Decision
is the default selection, selecting this option does not perform the task.

• Status Task
o Use the Add Status task template to create and add a Release status to the
target objects of the workflow process. This template is a visual milestone in
the workflow process. The task comes with EPM-create-status and EPM-set-
status action handler by default. Configure this handler with status to be
applied on the target object.

• Or Task
o Use an Or task template to continue the workflow process when any one of its
multiple task predecessors is completed or promoted. There is no limit to the
number of predecessors an Or task may have.
26 | P a g e
Jawad Saleem

• Acknowledge Task
o Use the Acknowledge task to define the Signoff Team profiles with which a
user complies to assign acknowledgment responsibilities to other users. This
template provides the perform-signoffs task for the Signoff Team members to
complete. When this task is performed in a workflow process, the
Acknowledge task displays two decision commands to members of the
selected signoff team: Acknowledged and No Decision. Signoff team
members choose one of the above commands to perform the signoff.

• Condition Task
o Use the Condition Task template to branch your workflow process according
to defined criteria. This task template is used to branch workflow process
flow, you must always create at least two paths branching off from the task.
The paths can be either success paths, failure paths, or a combination of the
two.
o Condition task has EPM-check-condition rule handler to check the condition.
o Automatic Condition Task: Query or action handler is defined to set a task
result for the condition task. Based on the task result the path is determined,
and branching takes place. I have blogged how to set automatic condition
using query and handlers.
o Manual Condition Task: No query or action handler is defined, user has to
manually select an option during workflow execution.

• Validate Task
o The Validate task branches a workflow along two or more paths. The path
followed is determined by whether specified errors occur during a workflow.
This task is used when errors are anticipated, and branching has to be done
based on the error. Will do a separate blog how to configure validate task
based on error.
27 | P a g e
Jawad Saleem

• Route task
o Use the Route task as a router sheet with which a user assigns review,
acknowledge and notification responsibilities to specified users. Route task
has three subtasks: Review, Acknowledge, and Notify.

• Custom Task
o Use it as a starting point for creating your own custom tasks, such as tasks to
carry your custom forms or other site-specific tasks for users to complete. Will
do a separate blog how to configure forms in custom task.

Steps for creating and attaching of workflow process template:

➢ Steps for creating workflow template

▪ Login by other than “Infodba” user and user should had administrative access.
▪ Open workflow designer module.
28 | P a g e
Jawad Saleem

▪ Open “File” Select “new root template”

▪ Enter template name and ok.
▪ Select any “Task” from task list
▪ Double click on template window task is added to template
▪

Handlers
Handlers are the small ITK (Integration Tool Kit) programs used to customized task in
workflow designer. Handlers are essential for designing flexible, complex workflows.

There are two types of handlers.

1) Action Handler

2) Rule Handler

Action Handler:
Action Handlers are used to perform actions such as attaching objects or send e-mails and
proceed accordingly.

• EPM-Adhoc sign off

o Add to Review task :-- select-signoff-team :-- Start
Arguments values
-assignee user: name of user / role:xyz
-auto_complete
-Quorum 50% / 2

• EPM-Create-status
o Add to status task :- start
Arguments values
-status (real name of custom status from BMID)

• EPM-set-status
o Add to status task :- Complete
Arguments values
-action (enter append, delete, replace)

• EPM-demote
o Add to Review task:- start task:- undo.
29 | P a g e
Jawad Saleem

Argument values
-target_task Target task name

• EPM-demote-on-rejection
o Add to Review task:-- perform-sognoffs :-- perform.
Argument values
-num_rejections 2

• EPM-auto assign

Rule Handlers:
Rule handler confirms that a defined rule has been satisfied. If the designed rule is met the
handler returns the EPM-go command allowing the task to complete. It returns EPM-No go
command presenting task to complete.

• EPM-check-related-object
o Check the target object contain required secondary objects with valid status.
o Add to Start task :-- Start
Argument values
-include_type ItemRevision
-Secondary_type Dataset
-relation IMAN_specification
-allowed_status Released

• EPM-check target object…...check condition

o Checks the status of the object to determine whether to allow the action.
o Add at start.
• EPM-check signoff
o Checks decisions of all the signoffs attached to this task. If the number of
approvals is greater than, or equal to, the quorum
Arguments values
-Quorum N numbers

• EPM-check-object-properties
Argument values
-include_type Object type
-property
-attachment TARGET
-value
30 | P a g e
Jawad Saleem

BMIDE (Business Modeler Integrated Development

Environment)
The Business Modeler IDE (Integrated Development Environment) is a tool for configuring
and extending the data model of your Teamcenter installation. The data model objects define
the objects and rules used in Teamcenter.

Business Modeler IDE used:

The Business Modeler IDE is a tool for adding your own data model objects on top of the
default Teamcenter data model objects. The Business Modeler IDE accomplishes this by
separating your data model into its own set of files that are kept apart from the standard data
model, known as the COTS (commercial off-the-shelf) data model. Data model objects are
collected into templates that contain the data model for an application (also known as a
solution). For example, the foundation template. xml Template is a xml file format used for
data model for a BMIDE application.

Data Model:

A data model is a structured organization of abstract objects to represent business data. A

data model represents the part designs, design documents, and relationships between them, as
well as the business processes applied to them. Teamcenter has its own data model that you
extend using the Business Modeler IDE.

Business objects:

• Business objects are the fundamental objects used to model business data.
• It is the first building block of Teamcenter unified data model.
• Business objects are related to each other through relation.
• Business object can hold multiple properties.
• Business object behavior is control through BMIDE rules

Classes:

• A class is the logical data model and maps the storage of a business object to the
database.
• Every class has a business object by the same name.

“Classes are the logical data model; business objects are the objects that the user works with
in the clients.”
31 | P a g e
Jawad Saleem

Difference between Schema and non-Schema:

Schema refers to classes and attributes managed by the Business Modeler IDE template. Non-
schema refers to all elements managed by the Business Modeler IDE template except for
classes and attributes

Rules:
The system uses various rules, defined by a system administrator, for determining its
behaviors at a site. Creating rules is also known as business behaviors modelling.

Naming rules:
Naming rules define the data entry format for a business object property. Naming rules can be
used to name items, item revisions, datasets, forms, projects, and work contexts. They can
also be used to name any persistent string property. A naming rule consists of rule patterns
and a counter.

Example: You can create a naming rule for an item ID that starts with AM- plus a four-digit
number, so that it generates numbers from AM-0001 to AM-9999.

*Naming rules attach to an ITEM only.

GRM rule:
A Generic Relationship Management (GRM) rule applies constraints on the relationship
between two business objects. When you create a GRM rule, you select the primary and
32 | P a g e
Jawad Saleem

secondary business objects for the relationship, the relationship they have to one another, and
the constraints to be applied. Available relationships are children of the Iman Relation
business object. You can use Generic Relationship Management (GRM) rules to limit what
objects can be pasted to other objects.

DEEP COPY RULE:

Defines whether the Item Revision relational objects will be copied as object, copied as
reference, or not copied when users perform Save-As and Revise operations. This Rule is
applied on only Item Revision. Or the Deep copy rule is defined whether object belonging to
an item revision can be copied as object, copied as reference, or not copy when user perform
save as/ revise on item revision. Relation Type-Iman specification & Iman reference, Object
Type- Text, Word file, etc.

Action-

• Copy as Object,
• Copy as Reference,
• No Copy
33 | P a g e
Jawad Saleem

Display Rule:
Display rule is used to hide your specific item type, form type, dataset type (customized item,
dataset) from particular group or role. If we go for command suppression then it would hide
all item type, form type, dataset type hence if we wanted to hide particular customized item
type then we use display rule. This is used for Hide the Business object.
34 | P a g e
Jawad Saleem

Property Constant:
Property constant controls the behavior of individual property available on the object.

Global Constant:
Global constant provides consistent definition that can be used throughout the system. These
constants have only one value either the default value or value you set.

Business Constant:
Business object constants provide default values to business objects.

Types of Properties/Attributes

1) Persistent:
Persistent properties are properties of business objects that remain constant on the object. A
simple value (for example, integer, string, or date). The value is stored in the database as an
attribute and mapped to the property.

2) Runtime:
A property that is defined at run time and attached to types. Run-time properties are derived
each time the property is displayed. Run-time properties do not map directly to persistent
attributes, references, or relations. Their data is derived from one or more pieces of system
information (for example, date or time) that are not stored in the Teamcenter database. Run-
time properties can also be used to display a property of one type as if it were a property of
another type.

3) Compound:
Compound properties are properties on business objects that can be displayed as properties of
an object (the display object) although they are defined and reside on a different object (the
source object).Though run-time properties can be used to display such a property, they
require custom coding to do so. Compound properties allow you to create such properties
without custom coding.

4) Relation:
Relation properties are properties that define the relationship between objects. For example, a
dataset can be attached to an item revision with a specification, requirement, or reference
35 | P a g e
Jawad Saleem

relation, among many others. The reference is stored in the database as a relation type and is
derived from that ImanRelation business object.

Steps to create new relation:

1. Open BMIDE and load the custom template.

2. Search for ImanRelation in Business object tab.
3. Right click ImanRelation -> New Business Object.
4. Type in the Name (real name) and Display Name (This name will be shown to end
user for pseudo folder name).

5. Click Finish to create the relation object

6. Next step is to add the relation object to the Primary business object for which you
want to relate secondary object with this new relation.
7. Open the primary business object in BMIDE.
8. Go to Properties tab and click Add button to create property.
9. In New Property window, select Relation property and click Next.
10. In Relation property tab, browse and select the new relation object created in above
steps. Click Finish

Teamcenter Preferences to see related objects and pseudo folder

36 | P a g e
Jawad Saleem

By default, Teamcenter does not display the secondary objects related to primary object. This
is because we have added with new relation which Teamcenter is not configured for.
Teamcenter preference has to be created for this.

Option 1:

• Open My Teamcenter -> Edit -> Options

• In Options, under General -> Item Revision.
• In Right panel, select the primary business object in "Items revision type selected"
field.
• Add the custom relation from Available relations to Shown Relations.
• Click Apply. This should display the related objects with our relation
• Go to Related Object panel.
• Select the primary business object in "Items revision type selected" field.
• Add the custom relation from Available relations to Shown Relations.
• Click Apply. This should show the related objects under relation pseudo folder.

5) Table:
To display the properties in Table format. Table property can be added to Workspace object
or any of its sub business objects.

Each column in the table is defined as a property. You can include persistent and run-time
properties in such a table, but not compound or relation properties. However, you can attach
lists of values (LOVs) to properties in a table as well as use property constants.

A table property can only be displayed on the Summary tab of the business object. To display
the table, you must add the property to the summary XML rendering style sheet of the
business object.
37 | P a g e
Jawad Saleem

6) Name-Value:
Name-value properties display name-value pairs in a tabular format to represent ad hoc
characteristics not defined in the persistent properties for the business object.

End users can add, edit, or remove rows of names and values in the table. Each row in the
table is unique by name and can contain different kinds of primitive data, such as Boolean,
date, double, integer, and string. In other words, a name-value property table can show rows
of heterogeneous data. (In a table property, the type of data in each row is of the same type.)

A name-value property can only be displayed on the Summary tab of the business object. To
display the table, you must add the property to the summary XML rendering style sheet of the
business object.

Relation between item and revision: Relations used to travers from item to revision and Vis
versa. We use traversing in compound property and query etc.

Item_tag: It is reference relation used for traversing from “revision” to “item”.

Revision_List: It is the reference relation used for traversing from “item” to “revision”.

Lists of Values (LOVs)

Lists of values (LOVs) are pick lists of data entry items. They are commonly accessed by
Teamcenter users when they click an arrow in a data entry box.

The list entries are created either by referencing existing data or by entering custom site data.
Once created, the LOV is implemented throughout the interface by attaching the LOV to one
or more properties. Creating LOVs and implementing them throughout Teamcenter can
improve productivity at your site and help prevent incorrect user entries.
38 | P a g e
Jawad Saleem

In the Business Modeler IDE, the Extensions folder contains an LOV folder. There are three
main types of lists of values:

• Classic: Store the LOV values in the template.

o Lists of values (LOVs) are lists on property boxes in the user interface. Classic
lists of values (LOVs) store the LOV values in the template.
o Usage types. Based on the requirement select any one of them.
▪ Exhaustive - Indicates that the list contains all possible choices.
▪ Suggestive - Specifies that the list contains suggested choices. The user
can enter their own value if they want.
▪ Range - Indicates that the list falls within a range of numeric values.
o Allows creating cascading LOVs, select show cascading view and create lovs.
[Will blog how to create cascading LOV]

• Batch: Store the LOV values in the Teamcenter database rather than storing them in
the template
o List of values that are managed externally outside BMIDE templates.
o Once batch LOV is deployed to the database, you can subsequently extract its
values to an XML file, modify the file, and then update from the file to the
database without having to shut down the database.
o Type of values supported on batch LOV are limited to string, double, char,
date and integer.
o Usage types supported are Exhaustive and Suggestive.
o Classic LOV can be converted into Batch LOV and vice versa using bmide
options.

• Dynamic: Read the LOV values dynamically by querying the database at runtime.
o List of values that are managed externally outside BMIDE templates.
o Once batch LOV is deployed to the database, you can subsequently extract its
values to an XML file, modify the file, and then update from the file to the
database without having to shut down the database.
o Type of values supported on batch LOV are limited to string, double, char,
date and integer.
o Usage types supported are Exhaustive and Suggestive.
39 | P a g e
Jawad Saleem

o Classic LOV can be converted into Batch LOV and vice versa using bmide
options

Cascade LOV:

Style Sheet:
Style Sheets are XML document stored in XMLRenderingStylesheet datasets.
This gives more control to site rendering how dialog boxes are displayed.

The XML code allows sites to define a subset of properties to display, the display order, the
user interface regarding component to be used.

A. Search for style sheets

To find style sheets in the rich client, search for XMLRenderingStylesheet datasets.
1. Click the Open Search View button .
2. Click the arrow on the Select a Search button and choose General.

Figure 0-1 Starting the search for style sheets

3. In the Type box, type XMLRenderingStylesheet.

If you are looking for style sheets for a particular kind of object, enter a string in the
Name box to look for those kinds of style sheets. For example, if you want to fin d all
style sheets for items or item revisions, type *Item* in the Name box.
40 | P a g e
Jawad Saleem

Figure 0-2 Searching for XMLRenderingStylesheet datasets

4. Press the Enter key or click the Execute the Search button. The results are displayed
in the Search Results view.
41 | P a g e
Jawad Saleem

Viewing the search results for XMLRenderingStylesheet datasets

5. In the Search Results tab, select the style sheet you want to view. Click the Viewer tab
to see the style sheet.

Note:

Do not double-click a style sheet (XMLRenderingStylesheet dataset file) in an

attempt to open it. If you do, you receive an Unable to open error message. Instead,
select the style sheet and view its contents in the Viewer view.

B. Stylesheet Creation
Create a custom style sheet based on an existing style sheet You can create your own
custom style sheet.
For example, you create a custom business object in the Business Modeler IDE and
install it to the rich client, and you want to create a unique style sheet to display the
custom properties. To create the style sheet, in the rich client, search for
XMLRenderingStylesheet datasets, save one as your own custom style sheet dataset,
and then register the custom style sheet for use with the custom business object.
➢ In the rich client, search for a style sheet you can base your new stylesheet on.
42 | P a g e
Jawad Saleem

➢ In the Search Results view, select the style sheet you want to use, choose File→Save
As, and rename it. For example, if you want to create a style sheet to be used with a
custom A5_MyItem business object, you could name the style sheet A5_MyItem.

The new stylesheet dataset is saved in your Newstuff folder in the “Home” view and is still
displayed in the Viewer tab.

➢ Edit the style sheet.

• Change the named reference for the file by selecting the style sheet dataset and
choosing View→Named References. In the Name column in the Named
References dialog box, change the old name of the file to the new save as file
name.
• In the Viewer tab, click the arrow in the Registered Type box and select the
business object type you want to register it to. For example, if you have a custom
A5_MyItem business object added to your server, select A5_MyItem from the list.
• Edit the style sheet in the Viewer tab to include the elements you want displayed
in the layout.

For example, if you want to display custom properties, add them where you want them to
appear on the page, like this:

<page title="General" titleKey="tc_xrt_General">

<column>
<property name="object_string" column="32"/>
<separator/>
<property name="object_name" column="32"/>
<property name="object_desc" />
<separator/>
<property name="owning_user" renderingHint="objectlink" modifiable="false" />
<property name="owning_group" renderingHint="objectlink" modifiable="false" />
<property name="last_mod_user" />
<property name="a5_MyDate"/>
<property name="a5_MyDouble"/>
<property name="a5_MyFlag"/>
<property name="a5_MyLongString"/>
<property name="a5_MyLOV"/>
43 | P a g e
Jawad Saleem

<property name="a5_MyRef"/>
</column>
<column>
<image/>
</column>
</page>
• To change the style sheet type, click the arrow in the Stylesheet Type box. You can
choose one of the following types:
− Property
− Form
− Summary
− Create
➢ When you are done making changes, click the Apply button in the lower right corner
of the view.
44 | P a g e
Jawad Saleem

Create a custom style sheet

Because you used the Registered Type box on the Viewer tab to register the style sheet with a
business object type, two new preferences are created (a REGISTEREDTO preference and a
RENDERING preference). These preferences apply the style sheet to the business object so
that the style sheet is displayed in the situation you set it for (for example, for display of the
business object's property, summary, form, or create information).

➢ To see the two new preferences, choose Edit→Options and at the bottom of the dialog
box, click Search.

Viewing the <dataset_name>. REGISTEREDTO and <type_name>. RENDERING

preferences

Notice how in the Current Values box of the <type_name>. RENDERING preference there is
a number in parentheses after the name of the business object. That is a GUID number that
identifies that unique business object, and that GUID number is set in the
<dataset_name(dataset-UID)>. REGISTEREDTO preference. This ensures that the style
sheet is applied to the correct business object.
45 | P a g e
Jawad Saleem

➢ To see the style sheet changes in the clients, clear the client's cache. Exit the rich
client and restart it using the -clean command argument to remove the old
configuration from cache.
To make the new stylesheets available for quick loading to clients, run the
generate_client_meta_cache utility to add the new stylesheets to client cache, for example:
generate_client_meta_cache –u=infodba –p=infodba –g=dba update stylesheets
46 | P a g e
Jawad Saleem

Deployments:
The Business Modeler IDE is a tool for extending Teamcenter with new business objects,
properties, and business behavior. As you create extensions, the Business Modeler IDE stores
them in a template. The template organizes your extensions as a single unit that encapsulates
your individual extensions. You can deploy this template as a single unit to any Teamcenter
database server for testing or production usage. The deployment process ensures that all of
your extensions are added to the default Teamcenter configuration

Types of Deployment:

1. Hot Deployment: If we are deploying anything directly in the production

environment is known as hot deployment.
2. Cold Deployment: In cold Deployment, first we are deploying the changes in the
development environment and in the testing environment. If the results of both the
environment are successful, then we are deploying same changes in the production
environment with the help of tem batch file. (Teamcenter Environment Management).