Basic Teamcenter

02 May 2022 16:39

Dataset
Pdm vs plm
Datasets are used to store physical files in the
PDM focuses on managing design data as it relates to product development Teamcenter. For each file type, a separate dataset is
processes, PLM centers on reengineering product development and available in the Teamcenter. You can attach multiple files
manufacturing processes as they relate to product lifecycles. to a single dataset. Each file associated with Dataset is
called a named reference. All these physical files are
stored in the volume. Datasets are generally attached to
Basic features Item or Item Revision with Specification, Reference,
- What is part? Rendering, or Manifestation relation.
Form
- What is item?
Forms are used to store additional information about the
an object that is commonly used to show the product, part, assembly, sub- Item or Item Revision. Item Master Form and Item Revision
assembly, component, etc. Item is the essential element in Teamcenter because it Master Form are the default forms attached to Item and
helps to categorize various data file Item Revision. You can create your own custom form
Item is an object in Teamcenter which represents a part of an assembly. Each Item has a using BMIDE.
Folder
unique Item ID assigned to it. Using Item id we can differentiate different items. You can
create your own custom Item Types based on OOTB items using BMIDE. Teamcenter Folder is similar to the windows folder.
- What is revision? Folders are used as a container to hold different objects.
Item Revision is a Revision of Item in the Teamcenter. Item Revision is always associated You can create your own custom folder using BMIDE.
with an Item. Item can have multiple revisions associated with it. You cannot create
Relation
independent Item Revision in the Teamcenter. Item Revision is used to manages and trace
changes in product, part, or document. Relations are used to define the associativity between
Volume and data base different objects. Objects are connected with each other
VOLUME in Teamcenter is a physical vault where all your files like the documents, Drawing Files, Models, etc. are stored with the help of relations. Specification, Rendering,
in a physical mode as we store the files on our own PCs in the Drives or Folders. DATABASE is a bit different in its way of Manifestation, References, etc. are some of the OOTB (out
storing the files like it stores the Metadata of the physical files that you must have stored in your volume. Metadata is a of the box) relations available in the Teamcenter. Each
term describes as the Data about Data, forex. Meta-data of a document could be the details like when it is created, last relation has its own importance and uses. You can create
modified, location of the document, owner of the document, your own custom relation using BMIDE.
- What is physical file?
Object Properties

- What is pseudo folder? Properties are used to store metadata information about
Pseudo Folders Pseudo-folders are special containers that. store and display Item and an object like name, ID, description, date, Owning User.
Item Revision relations in My Teamcenter. When an Item or Item Revision is created, a These properties are available on the Objects. There are
different types of properties available in the Teamcenter
pseudo-folder is automatically created for each type of Item and Item Revision relation. such as Persistent Property, Compound Property,
Runtime Property, Relation Property, Table Property. You
What is folder? can create your own custom properties of these types
Folders are containers. Because each user has their own My Teamcenter, object folders using BMIDE.
are an extremely flexible way to organize your product information. Object folders can BOMLine Properties
contain any other object including other object folders.
- BOM View? BOMLine properties are stored in the context of the BOM.
Bill of materials (BOM) management capabilities in Teamcenter can help your Find Number, Quantity are some of the OOTB BOMLine
properties. You can create your own custom BOMLine
customers know about their products and understand whether they consist of 10 parts properties using the BOMLine object in the BMIDE.
managed with basic processes and tools, or more complex products containing millions Preferences
of parts, requiring more advanced tools, flexibility and scalability.
- BOM View Revision? Preferences are the configuration settings of the
Teamcenter behavior of the functionalities.
Bill of Material Concept
BOM management is most important functionality of PLM system. BOM is most critical component in Site-level preference and Group level preference are the
a product based industry and managing it is still most challenging aspect in PLM system. The two types of preferences available in the Teamcenter. All
complexity increases as BOM lifecycle doesn’t reside just in one system or domain but in multiple the users can modify the site level preference. Users can
Enterprise systems. Also Bill of Material for a given Product or Part means different to different section modify group level preference if that user belongs to the
of people in the company based on their perspective and functionality for the given BOM. In this blog, required group. To access the Teamcenter preferences,
I will discuss BOM basic, variation and challenge for managing it in any enterprise. go to the Edit menu and click on Options.
Status
Concept of Bill of Material: BOM is defined as “A comprehensive list of raw materials, components and
assemblies required to build or manufacture a product”. Hence it is a detail recipe of product which Status represents the state of an object. If the object is
help to define, build and maintain a product. Since product goes through various lifecycle and interacts released, means it’s finalized and no further modification
with various discipline or domain from Design to Manufacturing to Service to Finance, Bill of material needed. Different statuses are applied to the business
also goes through similar lifecycle and various discipline or domain. Hence for a given product there object during the workflow process. You can create your
resides many BOM based on the lifecycle and discipline which required using it. For example Design own custom status and icon using BMIDE
Engineer mainly deals with Functional aspect of product where as Manufacture Engineer deals with
manufacturability aspect of product. Hence the way the Design Engineer look same BOM is different Workflow
from manufacture engineer. Same is true for Service Engineer, Procurement etc. Each one has his own
Workflow is a sequence of different tasks that are
way of looking of BOM. There is numerous ways for defining the BOM for same product. In technical
performed on the target attachment. Different statuses are
terms, BOM can mainly classified as follow applied to the target object during the workflow execution.
a) Design BOM (EBOM): This deal with functional aspect of product. This is mainly first steps of The workflow template is designed using the workflow
designer application of the Teamcenter.
BOM creation for a product. The design BOM usually originates from CAD model or Functional
Search Queries
architecture breakdown. Manufacturing BOM usually derived from Design BOM.\
Searched queries are used to retrieve information from
b) Manufacturing BOM (MBOM): This BOM deals with manufacturing aspect of Product. Hence it the Teamcenter Database. Different criteria are provided in
can have detail related to manufacture information along with part detail of product. For example the search queries to narrow down the output results.
Tools or Fixture can be part of Manufacturing BOM (or it can be reference in the Part). Also some Custom search queries can be developed using the Query
single design part can be consider combination of component ( Ex : Welding two plates ). Builder application of the Teamcenter.

c) Material BOM: This BOM mainly managed in ERP system for inventory and process planning. Home Folder
They deal with actual physical aspect of parts. Design or Manufacturing BOM can have component
which might not be real or perishables item. For example MBOM can have component for The home folder is an actual working location of a user.
intermediate manufacturing operation which doesn’t exist as storage or tangible part. Each user in the Teamcenter has a separate home folder.
Generally, user creates new objects by selecting the home
d) Service BOM: This BOM deals with Serviceability of Product. This BOM has only that information folder, so that it gets created under the home folder and
can be easily accessible. The home folder is available in
which defines the service aspect of Product. Hence it deals only with list of part which

PLM Page 1
 They deal with actual physical aspect of parts. Design or Manufacturing BOM can have component
which might not be real or perishables item. For example MBOM can have component for The home folder is an actual working location of a user.
intermediate manufacturing operation which doesn’t exist as storage or tangible part. Each user in the Teamcenter has a separate home folder.
Generally, user creates new objects by selecting the home
d) Service BOM: This BOM deals with Serviceability of Product. This BOM has only that information folder, so that it gets created under the home folder and
can be easily accessible. The home folder is available in
which defines the service aspect of Product. Hence it deals only with list of part which
the My Teamcenter application.
is serviceable. Therefore this BOM doesn’t have detail for subassembly which constitute as a single
part from service perspective.
New Stuff Folder
Apart from above BOM type there are some other BOM type like Order BOM, Procurement BOM etc
which are derivatives of above BOMs with some variation. Also BOM can also be distinguishing based If the user doesn’t select anything in the Teamcenter and
on configurability of BOM. creates the objects, then these objects appear under the
NewStuff folder. New objects created by the user in the
Configurable BOM: From single BOM, based on certain rules or condition you can derive various
Teamcenter using CAD applications also appear under the
resultants BOM. For example for a given model of a car, you can multiple versions. The Configurable NewStuff folder. The NewStuff folder is available in the My
BOM is used to dynamically create "end-items" that a company sells. The rule as basically variant and Teamcenter application.
condition are option for those variant. For example based on engine type, power train can be selected Mailbox Folder
in a given BOM. Configurable BOM provide a means to company to manage single BOM for multiple
products variant. This saves considerable time and cost to company. All major PLM tools provide Teamcenter provides its own mail functionality. You can
configurable BOM management modules. access Teamcenter mails from the mailbox folder. The
mailbox folder is available in the My Teamcenter
Application.
Checked-In and Checked-Out

To modify any information of the objects, user first needs

to checked-out the object, modify the information then
Checked-In the object. Checked-Out functionality retrieves
the object from the Teamcenter database for modification.
This object no longer available for modification to other
users unless user performs a Checked-In operation.

My Worklist

My Worklist is like an inbox of the Teamcenter user. Users

can see the assigned workflow tasks by going into My
Worklist.
Clipboard

If the user performs a copy or cuts operation on the

objects in the Teamcenter then these objects appear in
the clipboard. User can see the clipboard at the lower
rightmost corner of the Teamcenter.
Master BOM: Looking at so many BOMs variant for a given product, it is always a night mare for the company to manage all Access
BOM and synchronize all when there is any change in either upstream (Design) or downstream (Service). To overcome this
challenge, the concept of Master BOM has come. Master Bill of Material can be defined as single source of BOM having all
aspect of information for various configuration and discipline. Hence Master BOM by definition is single source of truth for all Access is the most important terminology of any PLM
BOM. Industry is still struggling to find the exact solution in term of defining and managing Master BOM. Also it become more software application. The sole purpose of the PLM
complex due to the facts that different BOM types are managed in different systems. PLM vendors including Siemens PLM has application is data integrity and data security. This can be
come various solution and tools, but still required to show the success and maturity of managing Master BOM as a single achieved by giving the right access to the right person at
source of truth across various BOM lifecycle and discipline. the right time. Access to different functionalities of
Teamcenter is controlled by using the Access Manager
- change objects? rule tree, BMIDE rules, Authorization, and Command
- Effectivity? Suppression modules.
Effectivity is defined for a build element root when your administrator creates the Views
manufacturing model for a unit (for example, vessel). So, when you create build elements, activities,
process/manufacturing elements, and select a product subset, the effectivity is already set. Views are very important to access detailed information
An effectivity is a common name used to describe what are the conditions for the validity of about an object. Different views are available in the
items or relations in the BOM (product structure). The effectivity typically can come as name (eg. Teamcenter application to fetch different information such
configuration), data (from/to), or serial (the part number or serial number). as Summary View, Viewer, Impact Analysis, Details, etc.
You can close and access these views as per your
convenience. To access these views, go into
- Release status?
the Window menu and click on the Show View option. You
- Revision Rule? will see the list of available views. Once you select the
- Precise & Imprecise? view, it will appear on your screen.
recise assembly is used when BOM is near to final stages and hence specific revisions of items are used to
represent BOM. On the other hand imprecise assembly is used when BOM is at initial or development stage , From <https://technolads.com/20-important-teamcenter-terminologies-you-must-know/>
because of which the whole item container is used to represnt parts in BOM.

- Purge & Immune?

- Workflow tasks & types?
A workflow in Teamcenter allows you to manage one's processes related to product data and
helps in accommodating one's business procedures. For Example: An Automobile company decides
to implement Part Testing Process workflow to shorten the testing time and strengthening business performance.
- Types of handler & description for each?
Workflow Handlers are single or set of ITK programs to extend and customize the behavior of
the task in the workflow. Handlers take the arguments as input and process as per the business logic is
written in the code.

- Relation Vs Attributes Vs Reference Properties?

There are four types of properties in BMIDE. and Those are Persistent, Runtime, Compound, and
Relation. All properties are in the right place to business objects, and attributes belong to classes. Persistent
properties are properties of business object that remain constant on the object.

- Revise Vs Save As?

When you save a part, assembly, drawing, and so on to Teamcenter, it results in the creation of a Teamcenter Item
and a number of other objects. The Item contains manifestations, requirements, an Item master form, and an Item
Revsion. Each Item Revision stores its own manifestation and specification, and an Item Revision master form. A
UGMASTER dataset is created as a specification of the Item Revision. The dataset contains the NX geometry for the
part.
When you create a new item, the information from the New Item dialog box (number, revision, and so on) is kept as
part of the item. When you save the item (File tab→Save→Save) the first time, the Name Parts dialog box is
displayed to provide an opportunity for you to review and change that information before it is saved to the
Teamcenter database.
If you have selected a folder before saving the part, the new part is placed in that folder. Otherwise, it's placed in
your Newstuff folder.

PLM Page 2
- Tc Architecture?
- Two-tier architecture
- Four-tier architecture

- Details all different architecture?

T
The Client Tier contains:
• Rich Client
• The TcServer process and the Teamcenter executables
• An optional application that integrates with the rich client like NX
Teamcenter manages the resource tier stores persistent metadata and files. The
resource tier contains:
• Database server and database
• Volumes
• File server

From <https://plmcoach.com/teamcenter-plm-architecture/#Teamcenter_PLM_Architecture_Overview>

Teamcenter handles the files and persistent metadata stored by the resource tier.
The resource tier is comprised of:
• Database server and database
• Standard volumes
• File servers for shared configuration and binary executables.

PLM Page 3
 From <https://plmcoach.com/teamcenter-plm-architecture/#Teamcenter_PLM_Architecture_Overview>

- Logical reason for save as & revise?

- BMIDE?
BMIDE is the heart of the Teamcenter application. BMIDE stands for Business Modular Integrated Development
Environment. Using BMIDE you can design and develop the data model of the Teamcenter aplication.

Business Objects
Business objects are nothing but the entities, that are used to store the information related
to part, product or assembly. As per business use cases, Teamcenter provides different
business objects such as Item, Item Revision, Datasets, Identifiers, Change Objects,
Folders, Forms, etc. Each of these object types has its own significance. You can also
create your own custom business objects if needed using BMIDE. You can control the
behavior of all business objects in the Teamcenter using BMIDE.

○ Naming Rule?
Naming rules define the data entry format for a business object property when the new object is created, for
example, when you create a new Revision (Revise) or copy an existing Item. Naming rules can be attached to
the properties: Item ID, Item Revision, and Name in Item Types.
Naming rules applied to the Item ID are only shown when the item is created (on the New Document dialog
box). Naming rules applied to a revision are shown at creation (on the New Document dialog box), or when
you revise the document (on the Revise Document dialog box). Naming rules applied to the Item Name are
available for edit after the document is created (on the Upload Document dialog box) which includes upload
and check-in.
Naming rules consist of two components: a pattern and a counter. The pattern is a variable that defines the
format (Example: NNNNN), and the counter is used to define the increment each time it is used.
Both the Item ID and Revision properties are dependent on the selected Item Type. When naming rules are
applied to these two properties, at least one pattern is defined, the pattern can be conditional, and the pattern
is governed by a generator. The naming and number pattern list is populated with the applicable value for the
selected Item Type.
The Item Name and Item Revision Name properties can have more than one pattern defined, the pattern can

PLM Page 4
 The Item Name and Item Revision Name properties can have more than one pattern defined, the pattern can
be conditional, but the pattern is not governed by a generator

Naming rule patterns

Naming rule patterns are composed of literal strings of characters, lists of patterns using lists of values
(LOVs) as literal variables, and pattern variables composed of existing naming rules. Each pattern can consist
of combinations of the following:

Character Pattern match

& Alphanumeric value.
X Uppercase alphanumeric value.
x Lowercase alphanumeric value.
N Numeric value.
n Numeric value.
@ Alphabetic value.
A Uppercase alphabetic value.
a Lowercase alphabetic value.
“string” String delimiters.
Example:
If you want the word Part to appear in the naming rule, define it as “Part” in the naming
rule pattern.
? Any single character value.
\ The next character to have a literal meaning. This character is only required when using
delimiters inside of other delimiters.
Example:
“A\”Special\”Name”, which matches [A “Special” Name].
${system- Substitutes the value of a Teamcenter system variable.
variable}
{variable- Literal variable delimiters {Type:Name}
type:variable
-name}
[variable- Pattern variable delimiters [Type:Name]
type:pattern-
name]
Regular Allows names to be validated, not generated, using standard regular expressions. This
expressions delimiter cannot be used in a pattern that automatically generates counters. The regular
expression delimiter is %, which indicates that the rest of the pattern is a regular expression.
For example, the pattern for an Item ID with two uppercase alphabetic characters followed by
one digit is AAn.
Once a naming rule pattern has been created, it must be attached to the business object property. The
creation and attachment of naming rules is done using the Teamcenter Business Modeler IDE.
From <http://www.soliddna.com/SEHelp/ST5/EN/w_z/x

Identifying naming rules

Buttons in the cells of common property dialog boxes such as the New Document dialog box communicate
the details of the valid patterns for that row or column.

Button Type Definition

Naming Rule + Required Naming rule applied to a required property such as Item ID,
Property Revision, Item Name, or Item Revision Name.
Naming Rule Naming rule applied to a property that is not a required property.

Revision Naming Rule + Only implemented in the Revision column on a required property
Required Property (Exhaustive that is configured with a revision naming rule from an exhaustive
LOV) list of values.
Revision Naming Rule + Only implemented in the Revision column on a required property
Required Property (Suggestive that is configured with a revision naming rule from a suggestive list
LOV) of values.
When the button is clicked, a message box is displayed containing the available pattern details for that row or
column.

Revision naming rules

A revision naming rule is a business rule that defines the naming convention and sequence for the revision
property. This functionality is sometimes used to satisfy the strict naming requirements demanded by some
industries. When revision naming rules are created, you have the option to exclude the characters I, O, Q, S,
X, Z from a revision. These characters are commonly omitted in the aerospace industry.

○ GRM Rule?
GRM rules(Generic Relationship Manager)
GRM rules (Generic Relationship Manager)
Generic Relationship Management (GRM) rules is used to apply constraints on the relationship between two
business objects.
Using Generic Relationship Management (GRM) rules we can apply limit what objects can be pasted to other
objects.
For example, if you do not want a certain type of object to have a specification relation to another type, you can
set the cardinality to 0 to deny pasting of one type of object to another with the specification relation.
When you create a GRM rule, you select the primary business objects and 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.

Cardinality : Determines the number of allowed occurrences of the primary object in relation to the secondary
object, and of the secondary object in relation to the primary object.
When you create a GRM rule, type a number in the Primary Cardinality or Secondary Cardinality, allowed
numbers are:
-1 or * = Allow an unlimited number of relationships.
0 = Do not allow any relationships.
1, or 2, or 3, and so on = Allow the specified number of relationships.

Inheritance of GRM rules

The GRM rule applies for all children of the primary and secondary objects. However, rules defined for a sub-
business object take precedence over the relation rules defined for a parent object.
For Example :
If the ItemRevision business object is chosen as the primary object, and the DirectModel dataset is chosen as
the secondary object, then all children of these objects that have the relationship inherit the rule.
Therefore, all instances of the children of ItemRevision that are related by the relation specified in the rule to
any instance of children of DirectModel are subject to the constraints defined by the rule.

From <https://teamcenterrac.blogspot.com/2021/01/grm-rulesgeneric-relationship-manager.html>

PLM Page 5
 ○ Extension Rule?
○ ID Rule?
○ Conditions?
○ LOV?
○ Type of LOV?
○ Cascade LOV?
An interdependent lov is setting a property value for each level, there must be an lov attached for
each level or the BMIDE won't let you create it. Once you have all levels defined it will work
○ Interdependent LOV?
When you have a drop-down whose values depend on another drop-down then, in this
case, you can create a cascading List Of Values (LOV). For example, select the Oracle Office country from first
LOV and populate city into second LOV based on the Country selected. The second LOV values are
dependent on the first LOV
○ Custom Icons?
○ Release Status?
○ Global constants?
○ Property constants?
○ Mandatory attributes configuration?
 Permanent?
 During Creation/Save?
- Attributes Mapping
- Template definition
- Translator configuration
- Part family for various cad
-

LOVs
LOV stands for the List Of Values. It’s a simple dropdown values list, provided
while filling the attribute values. The user has to select values from the list
provided. Using BMIDE you can create different types of LOV as per business
process requirements. Classic LOV, Batch LOV, Dynamic LOV, Cascading LOV,
Interdependent LOV are some of the frequently used LOV.
Constants
Property Constant and Business Object Constant are the two main types of
constants available in the Teamcenter. Property constant controls the behavior of
individual property available on the object. Initial Value, Visible, Modifiable, and
Enabled are some of the regularly used property constants. Business object
constant controls the behavior of the individual business object. Each constant has
its own defined behavior and uses case.
Statuses
Release statuses are really important to identify the state of an object. Whether the
object is in Work in Progress state, released state, Rework State, Cancelled, or
Rejected state is identified using Status applied. You can create your own custom
status and icon using BMIDE. Statuses are applied during the workflow process.
When the object is released means it is final and no further modification can be
performed on the object. Released objects are considered to be used for Teamcenter Workflow designer is one of the most important
production. Teamcenter applications that every organization needs. You
Naming Rules can develop the custom workflow process using different tasks
available in the workflow designer application. You can utilize
Naming rules are the defined patterns using which objects are named. Mostly existing tasks to design particular activities at the different
naming rules are applied on the item_id property of an object. While creating an stages of the workflow process.
object, the id value is automatically generated based on the naming rule defined in
the BMIDE. At a time only one naming rule can be attached to a property. But you Following is the list of activities you can perform using workflow
designer:
can define multiple naming patterns for one rule. You can use Revision Naming
Rule to define the revision naming behavior of an Item Revision. You can also use 1. Develop a custom workflow template
the concept of Intelligent Part Numbering in BMIDE to generate a naming pattern 2. Define the sequence of the tasks.
for an object. In Intelligent Part Numbering Item ID value is generated based on 3. Assign responsible users or groups to a particular task.
the values of multiple properties. 4. Define automatic actions that need to be performed on each
task.
Business Rules 5. Add validations at different stages of the workflow process.
6. Perform automatic actions or trigger external actions at the
Rules are defined using BMIDE which applied to the business object while required step.
performing any operation on it. Deep Copy Rule, GRM Rules, Display Rule are 7. Define required access to stakeholders of the workflow process.
regularly used BMIDE rules defined using BMIDE. Deep Copy rules validate which
objects to be carried forward while performing save-as or revise operation on the What are the different tasks
Item Revision. GRM rules define the relationship between a primary object and a
secondary object. Using Display rules, you can define which users, role and
available in the Teamcenter
groups from the organization can create particular object. Workflow Designer module?
Extensions
Siemens has provided the list of the different inbuilt tasks in the
The extension is a sequence of operations or behavior invoked as a Pre-Condition, workflow designer. These tasks are very useful while designing
Pre-Action, or Post action of a business object. You can add a new extension or the workflow process. Each task has its own significance.
overwrite the behavior of existing operations such as Item_Create, Item_save, etc. Do Task:
These extensions can be written using ITK API in C or C++ programming
language. If the user is required to perform a certain action on the target
objects such as attaching an object, updating property values,
Conditions etc then you can use Do Task. Do Task completes when the

PLM Page 6
 overwrite the behavior of existing operations such as Item_Create, Item_save, etc. Do Task:
These extensions can be written using ITK API in C or C++ programming
language. If the user is required to perform a certain action on the target
objects such as attaching an object, updating property values,
Conditions etc then you can use Do Task. Do Task completes when the
user selects a complete option.
Before performing any operation on the business object, if the business process Review Task:
wants that certain conditions must be satisfied then you can define these
conditions using BMIDE. There are already predefined generic conditions available If approval is needed on the performed changes then use the
in the BMIDE, that you can reuse. You can also create custom conditions if Review task. The review task contains two default sub-tasks i.e.
needed using BMIDE. select signoff team and perform signoffs. At select signoff, the
IRDC user can select the reviewers from the organization who will
review the job. At perform-signoff, reviewers will review the job
and take their decision.
IRDC stands for Item Revision Document Configuration. IRDC is a part of
Document Management. If you want that dataset must be created with a default Condition Task:
template and attached to Item Revision with specific relation when Item is created
in the Teamcenter. Then you can achieve this behavior using IRDC. For detail As the name suggests, you can use this task when the decision
stepwise procedure to Create a Template and use IRDC, kindly refer to Siemens is required based on the condition. Condition task branches
Business Modular Integrated Development Environment guile from the official workflow into multiple directions.
website. Or Task:
From <https://technolads.com/teamcenter-bmide/> The user cannot perform any action on Or task. It is used to
combine different paths of the workflow process. You cannot
point multiple tasks to a single task without the use of Or task.

Validate Task:
Validate task divides workflow into multiple branches i.e.
success path and failure paths. If there is an error that occurs at
My Teamcenter a particular task then you can route the path of workflow based
on the error code.
As a name suggest it’s your quick working area or you can say, your home location Acknowledge Task:
in the Teamcenter. This application provides basic functionalities like creating
objects and search objects using queries. You can easily access your mailbox, Acknowledge tasks can be used to assign acknowledgment
worklist. You can also create folders under the Home folder and store required responsibility to certain users or managers. This task has two
information for quick reference. This is a default application and you don’t need to sub-tasks i.e. select-signoff-team and perform-signoff. While
install separate features and don’t need a separate license to use this application. performing the action users gets two options to select i.e.
You must get used to the features of this application for your daily work. Acknowledged and Not Acknowledged.
2. Structure Manager
The structure is an assembly of the product which contains subassemblies and
components. Using the structure manager application, you can create a Bill of
Material (BOM) of the product. You can create and arrange BOM lines to create a
hierarchical structure. Find No attribute helps you to create different levels of the
product structure. Structure Manager provides very useful features such as variant
management, effectivity management, occurrence, substitute, and alternates, etc.
Using the structure manager, you can create 150% of the BOM then use variant
conditions to create 100% BOM of different variants.
3. Workflow Designer
Workflow as the name suggests is the sequence of operations or tasks performed
by an individual to complete the process. All tasks are performed sequentially.
Using Teamcenter Designer module, you can create a workflow process which
contains different tasks as per business process requirement. Do task, Review
Task, Condition task, Or Task, Validation task, and Status task are some of the
regularly used tasks to design workflow process. Each task has its own
importance. You can create as many tasks as required and arrange them
sequentially.
Each task consists of handlers. Handlers are the server-side codes that are
executed on the workflow objects when the task is started. You must have
administrative rights to use this application.
4. Manufacturing Process Planner
Use this module if you want to manage the manufacturing process-related
information. Manufacturing information such as Plant, Lines, Workstations, Tools,
labor information, time to complete the operation, etc. can be easily handled using
MPP. You can use a PERT chart to manage the sequence of operations to be
performed on the raw part. You can create a separate Manufacturing BOM (M-
BOM) and relate it with E-BOM which is created using structure manager. E-BOM
is used to store design-related information and M-BOM is used to store
manufacturing-related information. Organizations need to purchase separate
licenses to use this module.
5. Change Management
Change Management is a very crucial process for any product based organization.
Whenever any product is developed, it goes into multiple iterations before its final
product is developed. These iterations are nothing but the changes in the product.
And these changes are managed using the Change Management process. Some
changes may occur after the final product is produced. There are various reasons,
which cause a change in the product or process. Some of them are listed below:
• Cost Reduction
• Quality Improvement
• Customer Feedback
• The problem in the existing part
• Part replacement
• New technology adoption
Teamcenter provides a separate Change Manager module to manage change

PLM Page 7
Teamcenter provides a separate Change Manager module to manage change
related to the product. Organizations need to purchase a separate license to use
this module.
6. Query Builder
Using queries, you can search for data in the Teamcenter database. Query builder
is a user-friendly application that allows you to develop custom queries based on
your requirement.
You can define the search class and search criteria to fetch the required data. It
automatically fetches the required attributes and relations from the data model.
This application also allows you to export and import queries from one Teamcenter
Application to another. To use a query builder, you don’t need to purchase a
separate license.
7. Access Manager
Teamcenter is like a data hub. It stores all the data related to the product. All
information is available at one location, so it also becomes really important and
critical to protecting this information from misuse and mishandling. Users must
access the information or modify the information only if they have the required
privileges. So here Access Manager application comes to your rescue. Using this
application, you can restrict data access to certain users, groups, and roles as per
requirement. Access Manager application contains the rule tree. This rule tree is
applied to all the objects available in the Teamcenter. You must have
administrative rights to use this application.
8. Report Builder
Where ever there is data, there are reports. Teamcenter provides a Report Builder
application to design your own custom reports based on business process
requirements. You can generate reports in the form of HTML, excel, or word. To
use this application, you must have a good understanding of the PLM XML import-
export administrator module, PLM XML, and XSLT stylesheet. You don’t need to
purchase a separate license to use this application.
9. Schedule Manager
As the name suggests, using schedule manager you can schedule activities in the
Teamcenter. In a schedule, you can create different tasks, sequence them, assign
dates and time duration for the tasks. For example, some of the companies
execute preventive maintenance cycles on their heavy machinery in each quarter.
These cycles can be started and executed using a schedule manager application
in each quarter without human intervention. Task or activity will be started at the
scheduled time and for the assigned duration. You must have administrative rights
to use this application.
10. Organization
An organization is a hierarchical structure of the governing body of an enterprise.
You can create different groups, roles, and users based on the departments of an
enterprise. Users responsible for creating, changing, or reading data from
Teamcenter, must be created in the Teamcenter using the Organization module.
You can provide the required license level for users using this module. You can
create a hierarchical structure of the department and assign roles and respective
users to the groups. Ownership and access of data into Teamcenter is dependent
on the organization structure. It’s a default module of Teamcenter, you don’t need
to purchase a license to use this module. You must have administrative rights to
use this application.
From <https://technolads.com/10-important-teamcenter-modules/>

PLM Page 8