TC12-My TC (My Help)

My Teamcenter
This section describes the My Teamcenter objects, terms, and concepts used to create and manage your product information and tasks. My Teamcenter
is an application in Teamcenter Rich Client.
Folders
Folders are containers. Because each user has their own My Teamcenter, object folders are an extremely flexible way to organize your product
information. Object folders can contain any other object including other object folders. You can create a nested folder structure that stores product
information in the most convenient location for you.
Double-clicking a closed object folder expands it and displays the objects inside it; double-clicking an open folder closes (collapses) it.
Note While we have said that object folders contain other objects (because that is what you see), it is more accurate to say that folders contain
pointers or references to other objects. The distinction is subtle but very important. Several folders can contain references to the same object;
however, that object is only stored once in the database. Therefore, these folders provide multiple paths to the same product information.
My Teamcenter has three primary object foldersHome, Newstuff, and Mailbox. These three folders are automatically created for each user. You cannot
delete these folders.
Primary Folder Description

The Home folder is the top-level folder in the My Teamcenter tree.
Note My Teamcenter opens with the last object that was opened prior when you logged out
of your last work session.
The Mailbox is where you receive mail from other Teamcenter users. When your user account
is created, your personal mailbox is automatically created under your home folder.
The Newstuff folder is the default folder for newly created objects if you do not specify another
location. You can drop and drag objects in your Newstuff folder to other locations or you can
use the cut, copy, and paste menu options.
Teamcenter Objects
Objects are used to create, manage, and store data about your products. Click the name of the object in the table to access detailed information about
creating and managing the object.
Object Description
Folders Folders are objects that are used to organize product information in My Teamcenter. Folders can
contain any other object, including other object folders.
Item and Item Revisions Items and Item Revisions are the fundamental objects used to manage information in Teamcenter.
Items are structures that are generally used to represent a product, part or component. Items can
contain other objects, including other Items and object folders.
Item Revisions are objects used to manage changes (revisions) to Items
Datasets Datasets are objects used to manage data files created by other software applications. Each dataset
references at least two other objects: a dataset type, which is an object containing a list of tools that can
operate on a particular dataset, and a tool, which is the tool used to create or modify the dataset. Each
dataset can manage multiple operating system files. Each type of operating system file is called a
named reference.
Forms and Master Forms Forms and Master forms are objects used to display specific product information (properties) in a
predefined template. Forms are often used to create an electronic facsimile of an existing hard copy
form in Teamcenter. Master forms are used to display specific product information in a standardized
format.
BOM View and BOM View Revisions BOMViews are used to manage product structure information for Items.
BOMView Revisions are used to manage product structure for Item Revisions.
Item and Item Revision Relations Enterprises typically use many pieces of information that in some way describe or relate to an Item or
Item Revision. Teamcenter uses the concept of a relation to describe these associations (relationships).
Pseudo Folders Pseudo-folders are special containers that store and display Item and Item Revision relations in My
Teamcenter. When an Item or Item Revision is created, a pseudo-folder is automatically created for
each type of Item and Item Revision relation.
Address List An address list is any combination of valid users, groups, and/or external email addresses.
Envelopes Envelopes are objects used to represent Teamcenter mail messages sent to you from other Teamcenter
users. Envelopes can be used to send object references as well as simple text messages to other
Teamcenter users. This is extremely useful for sharing data throughout your enterprise.
Terms and Concepts

The following table describes the terms and concepts associated with My Teamcenter.
Concept Description
1 од 3
Named References Datasets often manage several different file types. These file types
are the named references of that dataset. Datasets are the only
objects that use named references.
Versions When an encapsulated software application runs during a

Teamcenter session, save commands are intercepted and new
versions of these datasets are created, rather than allowing the
software application to overwrite the contents of dataset. These
versions can be used to track changes to these datasets and to
revert to a previous version of the dataset (for example, undo
changes).
Teamcenter Options Teamcenter options (formerly known as preferences) are additional
environment variables used to configure and control aspects of an
Teamcenter session. Application-specific options enable you to
customize D-Teamcenter , Structure Manager, and Workflow.
Teamcenter Properties Teamcenter properties contain detailed information about a selected
object. You can view and/or modify the information for a selected
object type.
Based-On Relationship to When you duplicate an Item, Item Revision, or Dataset using
the Original Object File>Save As, the new Item, Item Revision, or Dataset has a based-
on relationship to the original object.
Inbox Terms and Concepts
Terms or Concept Description

Responsible Party The user who initiates a process becomes the responsible party for the process. The
root task of the process is placed in the user's Inbox. The initiator is also the responsible
party for all the process tasks. Thus, it is up to the initiator to assign users to any signoff
teams required for the process.
Resource Pool In the context of a workflow process, a resource can be a User, a Group, a Role, or a
Role in Group. When a resource is a Group, Role or Group in Role, any person in the
Group or Role becomes a member of that Group's or Role's Resource Pool.
Any member of a Resource Pool can assume responsibility for a task assigned to the
Resource Pool. A Resource Pool member is able to act as the Responsible Party for a
task and/or perform any task assigned to the Resource Pool.
Privileged User A privileged user is a member of a System Administration group.
Process The automation of a business procedure, describing the individual tasks and task
sequences required to complete a business procedure.
Task Tasks are the fundamental building blocks used to construct a process. Each task
defines a set of actions, rules, and resources used to accomplish that task. User actions
cause tasks to move from one state to another, and as a result, the overall process
moves forward (or backward).
Do Task Do tasks include the EPM-hold handler, which stops the task from automatically
completing when it is started.
Review Task Review tasks include select-signoff-team and perform-signoffs subtasks. Each of these
subtasks contain their own dialog box for executing the respective processes.
Select Signoff Team Subtask Select Signoff Team subtasks allow you to assign specific users to perform the signoff for
a specified task.
Perform Signoff Team Subtask Perform Signoff Team subtasks allow you to perform a signoff on a specified task.
Add Status Task Add Status tasks create and add a release status to the target objects of the process.
There is no dialog box associated with this template.
Quorum A quorum may be specified for each release level specifying the number of users that
must vote to approve in order for that task to be approved, allowing the process to
progress to the next task.
If a quorum is set to All, all signoffs must approve for the process to move forward.
Task Handlers A handler is a small ITK program or function. Handlers are the lowest level building
blocks in EPM. They are used to extend and customize tasks.
There are two types of handlers: action handlers and rule handlers.
Initiate a Process After you create an object, you will initiate a process (reference data) for the object. This
is the action of attaching reference data to target (an object).
Target data is the subject of the release. Target data can be any object type, but typically
they are Item Revisions and their specifications (for example, datasets). By default,
target data cannot be added or removed once the job has started.
Note The System Administrator can modify the procedure to allow targets to be added
or removed after the job has started by removing the disallow-adding targets
and/or disallow-removing-target handlers on the root task. This may be
necessary for companies using CR throughout an object's life-cycle. Careful
consideration must be give this this behavior. Reference data is supporting data
that anyone can add or remove at any stage during the job; this data can be any
2 од 3
object type. This action is called initiating a process.
Search Terms and Concepts
Term or Concep Description

Query Form Query forms are predefined queries that you can use to quickly search the database without having
to build your own custom query. Query forms limit your search criteria to those fields displayed in the
form. If you require additional search capabilities, you must build your own custom query.
Query Options Query options, such as sorting options, case sensitivity for search criteria, and targeting remote sites,
are specified by the user when a query is selected.
Query Result Pseudo Folder The pseudo folder is not a Teamcenter component folder, but a folder place holder designed to
display your search results. You cannot perform simple tasks, such as refresh, save, cut, copy, or
paste within this folder. The folder name that appears in the Find Tree changes each time you do a
search to reflect the total number of objects found.
© 2017 Siemens Product Lifecycle Management Software Inc.
3 од 3
e
Active Workspace
Active Workspace features a simplified interface that is highly configurable to an industry, group, role, or individual user.
Note Your home page may look different than the example. In addition, when Active Workspace is embedded in another application, some functionality may not be available. For example,
when Active Workspace is embedded in the Teamcenter rich client, the Sign out button is removed.
1 Global navigation buttons
Returns you to the home page.
Allows you to change the theme (colors and image, if applicable) of the interface.
2 Displays your user credentials, including your project, group, and role.
To log off Teamcenter, click your user name and select Sign out.
3 Displays the location within the client (for example, Teamcenter, Search, or Inbox).
Returns you to the previous screen.
4 Search box, with suggestions and prefilters.
5 Main work area.

The tiles on the main work area allow you to perform many tasks, such as access your inbox, your Home folder, and your saved searches.
Active Workspace is a minimal-install web client that brings a broad set of Teamcenter functionality to a wide range of browsers and mobile devices. Active Workspace benefits include:
• Requires minimal installation.
• Requires no plug-in, such as ActiveX or Java.
• Leverages the capabilities of a browser to provide a highly interactive client, including 3D visualization without any client installation.
• Runs on virtually any device with a browser that supports HTML5 and CSS3.
• Performs well even with high latency connections or massive amounts of data.

Configure the Active Workspace home page
There are many ways to configure the user interface. Here are a few ways you can give the Active Workspace home page the look you want.
Resize a tile
You can make the tiles larger or smaller to accomondate the number of tiles on your home page.
1. Right-click the tile, or press and hold the tile on a touch device, until you see additional controls on the corners of the tile.
2. Click the arrow button in the lower-right corner of the tile you want to resize.
3. To save your changes, click in a blank area on the home page.
Pin an object to the home page

You can pin object tiles and saved searches to your home page.
1. Select an object from a page such as your favorites or search results.
2. On the toolbar, click the Pin button .

The object appears as a tile on your home page.
Unpin a tile from the home page

Note Be careful which tiles you unpin. Most home page tiles require you to use the rich client to recover the tile.
1. Right-click the tile, or press and hold the tile on a touch device, until you see additional controls on the corners of the tile.
2. Click the Unpin button in the upper right corner of the tile.
Rearrange tiles
You can drag tiles from one location to another, and create new groupings of tiles.
Note To select a tile to be moved, right-click with the mouse, or press and hold on touch devices.
To move a tile from one group to another:

1. Select a tile.
2. Drag it to the new group and position near an existing tile, until you see the outline indicating the new tile position.
To move a tile and create a new group:

1. Select a tile.
2. Drag it to an area between existing groups until you see the vertical bar indicating the the new group position.
The tile is displayed in the new group.

Teamcenter rich client
Teamcenter rich client features a rich product interface that presents both product management capabilities as well as application administration configurability in one platform. The
complexity and robustness of the capabilities available make this interface more suitable to power users and application administrators.
The rich client interface has a standard menu bar and toolbar with options that vary depending on the currently active application perspective. You can place the cursor over a rich client
toolbar button to display a tooltip description.
1 Back and Forward buttons The Back and Forward buttons allow you to move between loaded Teamcenter applications. The small arrows next
to the buttons let you select from the list of currently loaded applications.
2 Application banner The application banner shows the name of the active application and lists the current user and role. You can double-
click the user and role to display the User Settings dialog box in which you can change your current role if multiple
roles are available to your user.
3 Search box The Search box provides predefined quick searches using dataset, item ID, item name, keyword search, and
advanced search features.
4 Navigation pane The navigation pane provides quick access to the data you use most. In addition to finding, organizing, and
accessing your data, you can configure the display of the Teamcenter perspective buttons in the navigation pane to
display only those perspectives that you use regularly to perform your tasks.
Click the reorder button above the Search box to display the Navigation Section Ordering dialog box that lets
you hide sections or change the order of sections in the navigation pane.
5 Application pane The application pane displays the application perspectives that are open in your Teamcenter session. By default, the
Getting Started application perspective displays a single Getting Started view.
Note Application perspectives are composed of views that can be moved elsewhere in the Teamcenter window or
can be dragged to the desktop. Such detached views remain connected to Teamcenter and continue to
function in concert with other views.
6 Getting Started application button Provides access to the Getting Started application.
7 Application buttons Application buttons provide access to your most frequently used Teamcenter application perspectives.
8 Application button bar The application button bar provides access to Teamcenter application buttons that do not fit in the application button
area of the navigation pane.
9 Clipboard button The clipboard button displays the Clipboard Contents dialog box, which contains references to objects that have
been cut or copied from your workspace. The total number of objects on the clipboard is displayed to the right of the
symbol.

NX/Structure Manager Linkup
Teamcenter Integration enables you to use NX assemblies and the Teamcenter Structure Manager together, to edit a single product structure database.
Teamcenter Integration does this by keeping the NX internal data structures synchronized with the Teamcenter database. The Teamcenter product
structure data is considered to be the master.
You can edit this single product structure from either NX or Teamcenter Structure Manager.
Benefits
The benefits of using this facility include:
Access to the Where Used function for NX assemblies.

Availability of bill of materials information within the database without having to use NX to view or edit it, so reports or interfaces to other systems for
example, MRP can be built.
Note Be careful when editing in both NX and Structure Manager simultaneously. We recommend that you edit from one application, save and close,
then edit from the other application as normal practice. This avoids possible confusion about which edits have been saved and propagated into
current sessions of the other tool.
The NX data structures, which can be kept synchronized with the database, are the components instances and the Parts List entries in part files. By
default, components in the Structure Manager bill, which have quantity 1 and no Default Unit Of Measure UOM, appear as components in the NX
assembly and others appear only in Parts Lists.
Note This is only done for master part files since Teamcenter does not maintain this data for non-master part files.
The NX/Teamcenter Linkup figure later in this topic illustrates the linkup between Teamcenter components, NX components and the NX Parts List.
Refer to it when reading the sections discussing how these three behave in conjunction with each other.
Defaults and Preferences

There are three NX customer defaults that affect the action of the functions described in this topic:
Structure Update On Load

Structure Update On Save
Callout Management
There is also an Teamcenter preference for the selective load function that may be placed in your user, group or site preference file:
IMAN_show_open_in_ug_button
When viewing items in Structure Manager, the following Teamcenter preference assigns the same Find No. to an item that has the same ID as one that
already exists in the BOMView. If the ID is diffferent, the item is given a new Find No.
PS_new_seqno_mode=existing
The synchronization actions are carried out at various points in the NX session as follows:
NX Session Action
During the load The NX part file data structures are updated to reflect edits made to the Teamcenter product
structure since it was last loaded by NX.
During the save The Teamcenter product structure is updated to reflect product structure and attribute edits made
in the part file during the current session.
While editing the Parts List and attributes The Teamcenter product structure is examined and if updates made are likely not to be
compatible with the database, warning messages are given.
Positioning new components New components that are noted as having been added in the Teamcenter product structure, are
marked as having been positioned.
The actions in the first three situations are described further in this topic.
Terminology
There are a number of terms that are used in different ways in Teamcenter and NX. The following is a list of potentially confusing terms and a short
description of each of their meanings within this topic:
Component - a single-level usage of one part within another. In NX this is called a component and in Teamcenter an occurrence.
Packed - display option to allow multiple components to be shown as one line in the Structure Manager BOM.
Aggregate - a component in Structure Manager that has non-unit quantity or whose child part has units of measure.
BomView Revision - the single level bill of materials for an item revision in Teamcenter.
NX and Teamcenter Component Properties

There are a number of properties of NX components that appear also as properties of Teamcenter components. These are:
Reference Set - This can be set by the user in NX as normal. If the note type UG REF SET is defined in the Teamcenter database, then it is filled
when saved with the current reference set name for each component. If this is edited in Teamcenter, then the reference set changes for the NX
component as part of the update next time the part is loaded. If the new value of the note does not match any reference set, the reference set does
not change and a warning is displayed. The check is case-independent.
Transform - Each component has a transform that may be a result of evaluating a mating condition. This is written to the transform field on the
corresponding Teamcenter component. This cannot be edited from Teamcenter Structure Manager.
Component Name - The NX component name is synchronized with Teamcenter Structure Manager and can be edited with either one.
1 од 2
The component name in NX is identified in the Component Properties dialog box. The name is defined in the Name box on the General tab
and is snychronized to the Structure Manager. After changing the name in the Name box, click Apply Name to All Occurrences in the Actions
group to apply the name to the NX instance.
The component name in Structure Manager is a note whose type is UG NAME case-independent match) as there is no component name
concept supported directly by Structure Manager. If this is defined in the Teamcenter database, it is used; otherwise, no synchronization takes
place.
2 од 2
What are preferences?
Preferences are special environment variables stored in the Teamcenter database. Preference instances are used to control the behavior and display of Teamcenter applications.
Video
This video explains how preferences are structured and how they are viewed and modified.
Teamcenter provides thousands of preferences that you can use to configure the product to your specific needs.
Administrator and nonadministrator users can configure many aspects of a session, such as the checkout directory and how often Teamcenter checks for new system mail. Preferences can apply
to the entire site, a specific user, a group, or a role.
Preferences control the behavior of Teamcenter clients and servers. The rich client provides an Options dialog box that lets you interactively select to specify behaviors.
Note In the rich client, another set of preferences are provided by the Window→Preferences menu command. These client preferences, which are displayed and edited in the Preferences dialog
box, are local to the user. These preferences are documented in the context of the applications to which they apply.
An example of preference hierarchy
Everything in this example is based on a single preference, one which registers a style sheet to a business object for the summary view. It
could be any preference as all preferences behave the same way. Since this preference definition's protection scope is User, you can create
instances at the Site, Group, Role, and User location. This means you can control its value based on your users' current group, role, or
even user name.
Example: I want the summary view's property layout for item revisions to depend on my users' login information
Following are the details of this example.
You have three groups: Engineering, Manufacturing, and Testing.
Each group has three roles: Manager, Designer, and Viewer.
You want a default style sheet that everyone will use unless otherwise specified.
Your technical users need an extended set of properties.
Your managers need a page of workflow information.
Your designers need classification information.
You have users that just need a simplified layout for viewing.
You have Conner. Conner is a power-user.
Conner needs a special layout regardless of which group or role he's in.
Style sheet datasets

Five style sheet datasets are considered.
ItemRevSummary
Configured to be the default style sheet for the Item Revision summary page. This applies to everyone unless overridden.
IRSumTech
Configured to provides the extra properties for the Engineering and Manufacturing groups, but not for any other groups.
IRSumMgr
Configured to display workflow information for the Manager role, regardless of group.
IRSumDes
Configured to show the classification trace for the Designer role, regardless of group.
ConnersIRSum
Configured for Conner. Conner has his own requirements
Preference instances
Assign the style sheets to the various groups and roles, and even users if desired, by creating each preference instance with the value
pointing to the respective style sheet. In this example, there are 6 preference instances created.
User preferences Conner: ConnersIRSum
Role preferences Manager: IRSumMgr

Designer: IRSumDes
Group preferences Engineering: IRSumTech

Manufacturing: IRSumTech
Site preference value: ItemRevSum
The Viewer role and the Tester group have no preference instances created for their location.
How does Teamcenter choose which preference to use?

In this example, Alice selects a DocumentRevision business object and uses the Summary tab. When she does this, Teamcenter
performs a few steps to determine which style sheet to use.
1. Based on the object type and the view location, the system knows the name of the preference instances to retrieve.
In this example, DocumentRevision.SUMMARYRENDERING.
There are two instances: one at the Site location, and one at the Manager Role location.
2. Based on the user's current session information, Teamcenter chooses the appropriate preference instance.
Less specific locations are overridden by more specific locations.
3. The value of the chosen preference instance is read, providing the name of the style sheet to retrieve.
4. Teamcenter uses the style sheet to render the view.
Result
Your users see a different set of information based on what group or role they are in because the client uses different style sheets.
User - Group / Role Preference instance build-up Resulting style sheet
Alice: none
Manager: IRSumMgr
Alice — Engineering / Manager IRSumMgr
Engineering: IRSumTech
Site: ItemRevSum
Ted: none
Manager: IRSumMgr
Ted — Manufacturing / Manager IRSumMgr
Manufacturing: IRSumTech
Site: ItemRevSum
Sue: none
Manager: IRSumMgr
Sue — Testing / Manager IRSumMgr
Testing: none
Site: ItemRevSum
Bob: none
Designer: IRSumDes
Bob — Engineering / Designer IRSumDes
Site: ItemRevSum
Carol: none
Viewer: none
Carol — Engineering / Viewer IRSumTech
Site: ItemRevSum
Pat: none
Viewer: none
Pat — Testing / Viewer ItemRevSum
Testing: none
Site: ItemRevSum
User - Group / Role Preference instance build-up Resulting style sheet
Conner: ConnersIRSum
Manager: IRSumMgr
Conner — Engineering / Manager ConnersIRSum
Site: ItemRevSum
Conner: ConnersIRSum
Viewer: none
Conner — Testing / Viewer ConnersIRSum
Testing: none
Site: ItemRevSum
Alice sees the style sheet for Managers because she does not have a user preference set to supercede it. The site preference is
overridden by the Engineering group preference, which is overridden by the Manager role preference. Ted has the same result; the
Manufacturing group preference is overridden by the Manager preference. Sue doesn't have a group preference, but she still gets the
Manager role preference.
Bob sees the style sheet for Designers because of his role, similar to the preceding example.
Carol sees the tech style sheet because there is no role preference for Viewers.
Pat's group and role do not have preferences associated with them, and neither does she have a user preference, so she gets the
default style sheet defined by the site preference.
Conner gets Conner's style sheet regardless of which group or role he's in, since a user preference supercedes all others.
There are several sources from which to retrieve a list of preferences and their definitions.
Administration data report
You can find the Administration Data Report in the Developer References for Customization in the Teamcenter
section of Doc Center. In this report, you will find a complete list of all preferences shipped with Teamcenter.
When you install additional features, like Dispatcher, NX Integration, 4th Generation Design, and so on,
additional preferences will be added to your site. To get the most accurate and up-to-date listing of
preferences contained in your site, you must create your own Administration Data Documentation report.
Rich client
You can use the various tabs of the rich client's Edit→Options menu to interact directly with preferences,
including a report of which preferences have changed since installation.
Raw XML export
You can produce an XML file containing preference information using the preferences_manager utility.
Attributes
Teamcenter Integration allows the use of attributes on components that are synchronized between NX and Teamcenter. The attributes on the Teamcenter
side are Structure Manager notes on components. There are also some NX part attributes that are specially treated.
General Behavior
In Teamcenter, the set of allowable note types on components is common to all components. It can be changed, but it is a database-wide set. In NX,
there is no predefined set. You can create an attribute with any title without predeclaring the title.
Note Attributes on components in Teamcenter are propagated up the assembly tree, but attributes on NX components are only present within the
displayed part that was current when the attribute was created. Teamcenter Integration synchronizes only NX attributes that are on first level
components within a given displayed part. If you set an attribute on a non-first-level component, then this is not saved to the database, and the
value is restored to the database value next time the part is loaded, if you have update on Load enabled.
At load time, when a note has been added, removed or modified in the Teamcenter component, this is reflected in the attribute set on the NX component
equivalent to it.
Matching Rules
The set of allowed characters for attribute titles in NX is smaller than the allowed set for note types in Teamcenter. Because of this, we have the following
rules for matching NX attribute titles with Teamcenter note types:
Match is case-independent for alphabetic characters.

The character $ may appear in an Teamcenter note type but is not allowed in an NX attribute title. So if a $ character appears, it is matched with _ in
NX titles.
For example, the attribute title PAINT COLOR matches the Teamcenter note type Paint Color, and the attribute title _3 matches the Teamcenter note type
$3.
If there is more than one note type in Teamcenter that matches a particular attribute title in NX, then one of the Teamcenter note types is used at random.
At save time, when an attribute on an NX component or Parts List entry has been added, modified or removed, and that attribute's title matches the title
of one of the note types in the Teamcenter set, this change is reflected in the Teamcenter component.
On save, if the NX attribute type is not a string, then the value converts to a string before being written to Teamcenter. When loading and updating from
Teamcenter, if the attribute is present already on the NX object i.e., value change), its current type is used, if possible. If not possible or the attribute is
not present, then an attribute of type string is created, and the old attribute deleted.
If there are multiple attributes with the same title and different value types on an NX component, then the following priority of types is used:
String, Integer, Real, Date, Null
The attribute with the value type first in this list is used to update the Teamcenter component on save, and updated from the Teamcenter component on
load. On load, only one attribute with a given title is replaced.
NX Read-Only Attributes
Certain attribute titles are designated read-only in NX. These are attributes on components and parts that are set by the system to match values in
Teamcenter, and may not be edited by a user. They are:
Attribute Description
DB_PART_NO Mapped to the Teamcenter Item ID
DB_PART_REV Mapped to the Teamcenter Item Revision id
DB_UNITS Mapped to the Teamcenter Item default unit of measure
DB_PART_NAME Mapped to the Teamcenter Item name
DB_PART_DESC Mapped to the Teamcenter Item description
The reason that Teamcenter Integration has these attributes is so that they can be used in Parts List reports to represent these values.
Note Values for read-only attribute titles can be entered as values for Parts List entries when using the Add To Parts List function, and must
correspond to genuine Teamcenter item/item revisions. If they do not, then the owning Parts List entry is ignored when synchronizing with the
database.
Find No. and Callout

The NX attribute CALLOUT is synchronized with the Teamcenter Find No. for a component by default. This default can be changed to synchronize
CALLOUT with a particular note type on Teamcenter components by setting the NX customer default Callout Management.
See Callout Management for additional information.
Teamcenter Note Types

There are several note types in Teamcenter that are specially treated. They are predefined in the system when it is delivered. They are:
Teamcenter Note Type Description

UG REF SET Synchronized with the NX component reference set.
UG NAME Synchronized with the NX component name.
The characters that can appear in an NX reference set name or component name are limited. They must be alphanumeric or from the set _-#&. If any of
these characters appear in a note of these types in Structure Manager, it is converted to _ for use with NX.
1 од 2
About new items and datasets
Teamcenter Rapid Start uses a single object called an item to represent a part and link to
datasets (files that define the part). Revisions are linked to the item and represent the
revisions of the item (part). You can have different types of items to represent different types
of parts (for example, standard parts). Datasets related to an item revision are linked by
relationships. The following figure illustrates the relationship between items.
Relationships between items

Create an item
1. Select your Home folder as the place to create your new item.
2. Choose File→New→Item.
The New Item wizard appears.
3. In the Select the Item that you want to create section of the window, click Item.
Optionally, you can also create standard parts, documents, and so on.
4. Click Next.
5. Click Assign to automatically fill in the Item ID and Number boxes.
Note If intelligent part numbering is configured, ID values are assigned automatically.

You can specify additional properties required for ID generation, then click Finish
to create the item.
6. Click Assign to automatically fill in the Revision ID boxes.

7. Type the name and description of the item.
The description of the item can be used for searching later.
8. Click Next to enter information in the Item Master Form and the Revision Master Form
(optional).
9. Click Finish.
10. Close the New Item wizard.
The new item appears in your Home folder.
Create a dataset
1. Expand the item to which you want to add the new dataset.
2. Expand and click the revision.
Once expanded, you see the Item Master form.
3. Choose File→New→Dataset.
The New Dataset wizard appears.
4. Click MSWordX.
This defines Microsoft Word as the application for editing the dataset.
If MSWordX does not display in the left side of the dialog box, click More and select MSWordX.
5. Optionally, create other dataset parts. Click More, select the type of part you want to create, and enter a
description (the dataset name is automatically created).
6. Optionally, import a file from the operating system by clicking .
7. Click OK.
Teamcenter Rapid Start creates a dataset, attaches it to the item revision, and closes the wizard.
Edit a dataset
1.Choose File→Open or double-click the dataset.
The application associated with the dataset opens (in this example, it is Microsoft Word).
2.Edit the dataset.
3.Save and close the dataset.

Step 1: Create the item that contains the assembly
information
1. Select your Home folder as the location in which to create your new item.
2. Choose File→New→Item.
3. In the Select the item that you want to create section of the window, click Item.
4. Click Next.
5. Click Assign to automatically fill in the Item ID and Revision ID boxes.
6. Enter the name and description of the assembly.
Information included in the description can be modified later and used for searching.
7. Click Next to optionally enter information in the Item Master Form and the Revision Master Form.
8. Click Finish.
The new item appears in your Home folder.
Step 2: Open the new item in Structure Manager

Right-click the new item and choose Send To→Structure Manager.
The Structure Manager application opens with the item revision representing the assembly as the only entry.
Step 3: Add a new item to the structure

1. Select the item and choose File→New→Item.
2. Enter the information for the new part.
3. Click Finish.
The newly created part is attached to the assembly.
Note This method of creating a new part creates the item in the database, but does not display it in your Home
folder. If you want to see the part in your Home folder (for example, within a specific folder), create the part
in your Home folder first, and copy and paste it into Structure Manager.
4. Repeat the process to create additional parts for the assembly.

6. Choose File→Save.
Saving the structure in Structure Manager creates a new entry in the item and the item revision.
◦ The button within the item is a shortcut to the latest item revision structure.
◦ The button within the item revision represents the structure of that specific item revision.
◦ Double-clicking the button takes you to the corresponding structure.

Step 4: Add an existing part to the structure
1. Locate the part you want to add to the structure.

This part can be in your Home folder or be located using Search.
2. Select the item revision of the part you want to add and click Copy .
3. Click the Structure Manager button to return to Structure Manager.
4. Make sure the assembly is selected and click Paste .
The existing part is added to the structure.
Note You can copy multiple item revisions and paste them into Structure Manager in one operation.
Step 5: Create the subassembly

1. Create a new part in the assembly.
This part represents the subassembly.
2. Select the new part so that it is highlighted.
Highlighting controls where future parts are added to the structure.
3. Create the components of your subassembly, either by creating new parts or by pasting existing parts.
The components are attached under the highlighted subassembly.
Glossary
4GD
See 4th Generation Design.
4th Generation Design
Teamcenter application that allows designers to work together on the design of a large product such as a ship.
absolute occurrence
Relationship between a parent assembly and an item one or more levels down in the structure. The parent assembly is the context in which the absolute occurrence exists. When you select the
context assembly and view the structure, you can define data on the absolute occurrence that overrides the data stored on the parent. Compare to occurrence.
abstract class
Classification class used to combine common attributes for use in storage classes. Classification instances cannot be stored in abstract classes. Compare to storage class.
abstract smart folders
Pseudofolders that serve as filters for project data. See also pseudofolder
access control entry (ACE)
In Access Manager, each pairing in the access control list of an accessor with the granted privileges.
access control list (ACL)
Access Manager component that contains a list of accessors and, for each accessor, the privileges granted, denied, and not set.
Access Manager (AM)
Teamcenter application that enables the system administrator to grant users access to Teamcenter objects.
accessor
Access Manager component that grants or denies privileges to clusters of users who share certain common traits (for example, perform the same function or work on the same project).
ACE
See access control entry (ACE).
ACL
See access control list (ACL).
action chain
In Global Services, a logical method to group action components into a flow within application maps. Action chains can be invoked only within response chains or other action chains; they
cannot be called from a link. Action chains act like a subroutine and usually return to the response chain or action chain from which they are invoked. Similar to response chains, action chains
define chain options that apply to all action components embedded in the action chain. See also action component and response chain.
action component
Java code that calls the business logic associated with a request in order to produce data that is displayed in a page. Action components read and interpret request data, start Enterprise
Services, and create data beans. Action components populate a set of data beans that are used by JSP pages. Teamcenter provides standard action components; customizers can write
additional action components.
action handler
Handler used to extend and customize workflow task actions. Action handlers perform such actions as displaying information, retrieving the results of previous tasks (inherit), notifying users,
setting object protections, and launching applications. See also task handler.
action rule
Business rule that defines the actions required in different time phases (precondition, preaction, and postaction) for create, save as, and delete operations. Action rules are applied to items,
item revisions, and datasets.
active mode
Management of application files that allows their use by both an application and Teamcenter. There are two categories of active interaction between Teamcenter and an application:
encapsulation and Integration. Compare with passive mode.
active unit
In Classification, the measurement unit in which a classification object (ICO) is currently displayed. This may not be the measurement unit in which it is stored.
activity (manufacturing)
Individual action to be performed within an operation. Each activity is associated with a start time and duration. The total time for the operation is based on the cumulative duration of all
activities within the operation.
Activities can be sequenced using time data and predecessor activities.
activity (Service Planner)
Individual action to be performed within a work card. The total time for the work card is based on the cumulative duration of all activities within the work card.
ADA License
Teamcenter application that administers International Traffic in Arms Regulations (ITAR), intellectual property (IP), and exclude licenses. It provides enhanced control and new attributes for
these licenses. ADA stands for Authorized Data Access.
add status task
Task template that creates and adds a release status to the target objects of a workflow process. There is no dialog box associated with this template.
ad hoc partition
In site planning, a partition that does not have a fixed source or definition. Users create ad hoc partitions and identify them by name. Contrast with formal partition.
ad hoc process modification
Functionality that allows users to add tasks to, or delete tasks from, an active workflow process.
administrative data synchronization
Signifies that whenever administrative data is modified in Oracle Manufacturing, corresponding data is updated in Teamcenter.
ADS
See Aerospace and Defense.
ADS design
Represents the computer-aided design (CAD) data of an ADS part, component, or assembly.
Aerospace and Defense
Solution or template installed as an overlay on top of the standard Teamcenter product that provides the necessary additional object types and other data necessary for the Aerospace and
Defense industry.
aggregate business object
Global Services business object containing some attributes stored in one data source and other attributes stored in another data source.
An aggregate business object is defined with multiple data-segment elements.
Contrast with multisource business object.
aggregate occurrence
Single occurrence using the quantity attribute to represent multiple uses of the same component item. An aggregate occurrence is used where separate occurrences are not required to
distinguish individual uses (for example, transforms in NX). Rivets are typically shown as an aggregate occurrence.
AIF
See Application Integration Framework (AIF).
alias ID
Identifier of a part that is similar to the current part. You can use it as a substitute part in the product structure. Contrast with alternate ID.
alias ID rule
Business rule that stores part numbers and other attribute information for similar parts.
allocation
Relationship between constituents of two structural views of a product, for example, a relationship between constituents of the functional breakdown and the physical breakdown of a product.
alternate ID
Different identifier for the current part, but one that represents the same part. Different organizations and suppliers can have their own part numbers. With alternate IDs, you are able to find the
part you are looking for using your naming scheme. Contrast with alias ID.
alternate ID rule
Alternate identifiers that store information about part numbers and attributes of the same part from different perspectives. They allow different user communities to identify and display an item
or item revision according to their own rules rather than by the rules of the user who created the object.
AM
See Access Manager (AM).
Analysis pane
CAE Manager pane used for creating and managing CAEAnalysis and CAEResult items and item revisions.
analyst
Issue Manager user who assesses the technical feasibility of an issue or the technical feasibility of implementing the low-level details of an issue. An analyst also participates in the execution of
an issue by carrying out the tasks identified in the implementation plan for the issue.
ancestor relation
Relation between objects originally created in Teamcenter Enterprise and transferred to Teamcenter for ownership. In case of Teamcenter Enterprise to Teamcenter data transfers, such
relations are not infer deleted. See also infer delete.
ancestor replica
Object created in Teamcenter Enterprise and transferred to Teamcenter for ownership. This object becomes an ancestor replica in Teamcenter Enterprise. If this object is modified in
Teamcenter and transferred to Teamcenter Enterprise for reference, only selective attributes of the object are updated in Teamcenter Enterprise.
AP212
See STEP AP212.
appearance
Sequence of occurrences that describes a unique path through an exploded structure. An appearance corresponds to a unique instance of the component that is referenced by the leaf node of
the path within the top-level assembly. An appearance may have spatial data associated with it, allowing spatial searches.
appearance checker package
Primary update package that validates one or more appearance sets against the corresponding structures configured in Structure Manager. An appearance checker package chooses what to
configure and validate based on the information generated by the audit packages.
Appearance Configuration
Teamcenter application used to configure the use of appearance:
• Defining the appearance sets for which the site tracks appearances.
• Configuring the mapping of occurrence notes into appearance attributes.
appearance group
Subassembly composed of appearances. The components of the subassembly are defined in their position relative to the end item.
appearance path node
Architecture object created for each BOM line when the architecture structure is saved. An appearance path node ensures that each line of the architecture breakdown has a reference to the
top-level architecture item.
appearance root
Object in the database containing the set of parameters that define an appearance set: root item, configuration context, and view.
appearances
Cache of configured BOM lines in the context of a specific top-line item. Appearances are created to allow quick searches of the entire structure.
appearance set
Collection of objects that define the use of every part ever included in an end item. The appearance set enables Teamcenter to rapidly search the product structure of a family of related
configurations without caching the entire product structure for each configuration. The appearance set is optional and typically maintained for a few end items that represent large assemblies
when fast searching is critical. The system administrator defines the items requiring appearance sets.
application
Related functional elements collected and arranged in a software package, designed to accomplish specified tasks. See also perspective.
application extension point
Extension that allows for the configuration of applications using a decision table. This extension point defines the table and the inputs and outputs that customers can configure against it.
application extension rule
Business rule that determines when an application extension point is used and defines inputs and outputs.
Application Integration Framework (AIF)
Integration framework that enables developers to build custom interfaces to applications for Teamcenter and NX. This framework provides the foundation through which applications can be
launched and executed in a standard manner. It also provides the basic design for applications, the base classes and methods, and a methodology for creating and handling events generated
by the user interface. In addition, the AIF provides tools to handle the registration of components, represented by Java beans, and a mechanism for locating and passing messages to those
components.
Application Interface Viewer
Viewer data tab in applications that allows users to monitor and control PLM XML data exchanges between Teamcenter and another application through a collaboration context.
application map
Set of XML files that provide application-specific behavior. This behavior is provided by specifying a mapping between web client requests and handlers that couple the request with business or
application logic. The controller reads this file when the controller is initialized. The application map contains logical IDs that map to action components, page handlers, and JSP pages to call
for each incoming HTTP request.
approver
User who has a signoff in a workflow process regardless of role and group membership. In Access Manager, the approver accessor is used to allocate privileges that apply to all signoffs (for
example, read access). See also RIG approver, role approver, and group approver.
architecture
Set of decisions, patterns, and principles for a product suite. The architecture provides a framework for application development within that product suite and is independent of specific
functions.
architecture (Platform Designer)
Top-level object in a Platform Designer structure.
architecture breakdown
Structure used to lay out, plan, and control evolution of product structures. An architecture breakdown displays product information in terms of engineering content and product variability,
including variant options and values and defining variant conditions for occurrences.
architecture element
Generic component or a placeholder for a component in the product. Each architecture element is associated with a line of usage (LOU) to allow completeness checking.
architecture item
Type of item and class accepting attributes used to store architecture information.
artwork
In Consumer Packaged Goods, an assembly of the copy, technical specification, and graphical elements. An artwork represents the labels on packages or the images and information printed
on packages.
As-Built Manager
Teamcenter application that allows you to manage the as-built configuration of an asset realized from a product definition structure, such as a design or manufacturing structure.
as-built structure
Physical asset structure representing the neutral structure that it was realized from. The as-built structure is a precise structure that represents the physical asset structure at the as-built phase
and does not retain date or time evolution history.
as-maintained structure
Physical configuration of a manufactured product evolving through its serviceable lifetime. A single neutral structure can result in many as-maintained structures, one for each physical asset.
assembled item
Represents products that are created by assembling discrete components. Mechanical, electronic, and electromechanical assemblies can be represented using the assembled item.
assembly
Compound object that is assembled from other objects and may add additional information to their interpretation.
• In the context of an assembly, other assemblies are called subassemblies, while noncompound objects are called components.
• A single-level compound object that is distinct from a multilevel product structure or bill of materials, which is a hierarchy of assemblies. Assembly data is stored in a BOM view revision.
assembly classification
Resource assembly ID and name of the class where the assembly is classified. An assembly classification is also the process of associating an assembly with a class and entering the attribute
values that characterize it within its class.
assembly file
3D CAD assembly file that contains an index of the geometry of constituent 3D model files.
assembly view
View of the product data. See also BOM and manufacturing view.
asset
Extension of a Visio shape that exposes data in Teamcenter.
asset group
Collection of physical assets that define a logical grouping of physical products. You can create asset groups and asset hierarchies. Asset hierarchies are used to build a nested hierarchy of
asset groups within asset groups.
assigned FSC
FMS server cache assigned as the volume or cache server for an FMS client cache. Each FMS client cache requires an assigned FSC to provide it with access to files. An assigned FSC is
typically the FSC nearest to the client host. In small deployments, an assigned FSC can also serve as the parent FSC.
attribute
Named storage variable that describes an object and is stored with the object. Users can search the database for objects using object attributes.
In an object, an attribute is a name/value pair. In the database, an attribute is a field.
attribute (Classification)
Characteristic that distinguishes one instance of a class, subclass, or view from another. For example, within the Sheet Metal Screws class, the length, diameter, and thread attributes
distinguish one sheet metal screw from another. Classification Admin is used to define and store classification attributes.
attribute data name
Name of a business object attribute as defined in a data source. The data name can be the same as or different from the attribute external name.
attribute dictionary
Repository for Classification attribute definitions. An attribute 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.
attribute external name
Name of a business object attribute as defined in Global Services.
attribute inheritance
Process by which a new class automatically inherits all the attributes defined for all its ancestor classes.
attribute propagation
Process of transferring attribute values from one object to another. In Resource Manager, attribute values are propagated from a propagation start point up the assembly structure to the
assembly object. For example, on a cutting tool, the cutting material of the insert, the cutting diameter of the extension, and the holder type of the machine adapter can all be propagated to the
assembly level. This provides a mechanism to make all attributes required for a cutting tool definition available at the tool assembly level.
attribute substitution
Substitution of run-time instance attribute values into the business object link or data segment where clause definitions.
audit definition
Object that creates audit logs to track selected properties for specified actions in the database. These properties can include custom properties added by a system administrator.
Audit Manager
Teamcenter application that enables a system administrator to create audit definition objects, enable/disable audit trail logging, and control audit log access. Audit definition objects create audit
logs that users can view from Teamcenter applications. Users can audit any Teamcenter object and event type with an audit definition.
audit package
Primary update package that stores information in the database about how users are using appearances. An audit package is generated when a user performs a search in Structure Manager.
When processed, it stores information in the database about the relevant appearance root and date and unit-number configuration.
Authorization
Teamcenter application that enables access control of administrative applications and utilities.
authorization rule
Allows you to control access to Teamcenter administrative applications and utilities by group. System-level rules are delivered as part of your Teamcenter installation, and you can create
additional rules to support your business processes using the Authorization application.
background part
Component loaded into a design session as background to a work part. Background parts are not intended for modification in the design session.
base calendar
Master calendar used when creating schedules.
baseline
Collection of items and the relationships between the items that is established to ensure their continued existence. It enables their configuration to be reconstructed and audited. Baselines are
often created to preserve the state of a design at a particular checkpoint. You can baseline precise or imprecise structures.
baseline appearance set
Initial appearance set created for a product for a specified appearance root. It defines the root item and configuration context to be tracked.
base product view
The as designed bill of materials of the product. Contrast with manufacturing bill of materials.
basic deployment (HSE)
Basic deployment on an enterprise (Java EE) application server. The HTTP web server (H), servlet container (S), and Enterprise JavaBean (EJB) container (E) are all provided on the same
platform as part of the same process. The Teamcenter web tier application (EAR file bundling the WAR file) is deployed on a Java EE application server that has a built-in HTTP listener, such
as JBoss Application Server, Oracle WebLogic Server, and IBM WebSphere Application Server.
Deploying a separate HTTP web server to listen to the incoming request is not required.
basic deployment with front-end HTTP web server (H-SE)
Stand-alone HTTP web server is configured as the front-end to a Java EE application server.
batch mesh
Teamcenter feature that allows meshing of component CAD files without using a traditional meshing application.
bid
Contains line items supplied to vendors to submit quotes.
bind
In Visualization Illustration, the user action that defines the combination of transfer mode and alias Teamcenter uses when an asset is populated. See also asset.
BLOB
Binary large object; attribute type of undefined structure. BLOBs are stored as binary images within an object.
blobby volume
Alternate volume used to store data while backing up volumes and databases. The blobby volume provides continuous Teamcenter availability.
BOM
Bill of materials.
• 100% BOM
The as sold product configuration, for example, the configuration of a car to be built and shipped to the dealer.
• 120% BOM
Partial overlay of selected variant conditions. You cannot build the product from a 120% BOM.
• 150% BOM
Overlays of all possible variant configurations. You cannot build the product from a 150% BOM.
See also design bill of materials and manufacturing bill of materials.
BOM view
Teamcenter object used to manage product structure information for an item.
BOM view revision (BVR)
Workspace object that stores the single-level assembly structure of an item revision. Access can be controlled on the structure (BOM view revision) independently of other data. BOM view
revisions are meaningful only in the context of the item revisions for which they are created.
bootstrap package
Primary update package created when the baseline appearance set is created.
BOS wildcard
Wildcard specified in the BOS box configuration file. The user interface (UI) uses the BOS wildcard in its forms and when invoking operations on the BOS. Custom clients should also use the
BOS wildcards when interacting with the BOS. See also connector wildcard.
BPV
See base product view.
brand
Set of digital assets that includes brand collateral, such as marketing brief, theme board, and so on, and brand assets such as logo, messages, and so on.
build platform
Platform required to build a customization. Compare with certified platform and supported platform.
bulk data
Physical information represented in the database by a data item. Examples of bulk data are file system items, paper documents, and microfiche. The Teamcenter database describes the bulk
data. The bulk data resides elsewhere, for example, in a file system or in a filing cabinet. See also data item.
business context
Context that defines the user groups to whom a rule applies.
business logic reactor
See reactor.
Business Modeler IDE
Teamcenter application that enables a customer to define data model objects such as business objects, classes, attributes, lists of values, and rules.
business object
Logical grouping of data attributes and properties that are manipulated at the enterprise level.
A Global Services business object allows users to query for and update information in multiple data sources.
business object constant
Constants that provide default values to business objects. Because these constants are attached to business objects, they are inherited and can be overridden in the hierarchy.
business object definition file
File that contains the XML-based definition of a Global Services business object.
business object display rule
Business rule that allows an administrator to control the business objects that are available for creation in Teamcenter.
business object server connector
Global Services component that defines one standard method for retrieving data from all data source systems, resulting in the ability to change or replace a data source system without
affecting other data sources in the Global Services environment.
The business object server connector is an Enterprise JavaBean.
business operation
Action performed against an object, such as creating, saving, or setting a property value.
BVR
See BOM view revision.
CAD manager
Teamcenter interface to the specific CAD authoring tool. The CAD manager provides the CAD specific knowledge for data interaction, normally to check out and edit, and to check back into
Teamcenter. The CAD manager is used by Dispatcher components for gathering the dependent CAD items required for a translation.
I-deas – NXMI CAD Manager
NX – NX CAD Manager
Pro/ENGINEER – IPEM CAD Manager
CATIA – EB Solutions CAD Manager
CAE analysis
Workspace objects that define the type of analysis to be done and the solver used to perform the analysis. The CAEAnalysis item revision consists of solver parameters and relationship to the
non-CAE, CAEModel, and CAEResult item revisions. The datasets attached to the CAEAnalysis item revision store the solver-specific input deck file and/or the tool-specific simulation file.
CAE geometry
Workspace object that contains the geometry used to generate mesh data for performing engineering analysis. The contents of the CAEGeometry item can be created from the geometry
contained in a non-CAE item revision. It can often have simplifications such as feature suppressions to the original product geometry to facilitate the analysis process. A CAEGeometry item
can act as a source representation upon which the CAEModel item is built.
CAE Manager
Teamcenter application used to create and manage engineering analysis data. CAE Manager enables the creation and modification of CAEModel, CAEAnalysis, and CAEResult items and
item revisions, and generates CAE model structures based on the input product structures using the data map and/or structure map definitions.
CAE model
Workspace object that defines the mesh data used for performing engineering analysis. A CAEModel item revision can have a relationship to the target non-CAE item revision. It can also have
a relationship to a source CAEGeometry item revision or a source non-CAE item revision. A CAEModel item can participate in a hierarchical structure that defines a CAE structure. The
datasets attached to the CAEModel item revision store the mesh representation of the assembly or the component.
CAE result
Workspace object that defines a CAEResult item object that is used for managing results of the CAE analysis from different solvers. The CAEResult item revision can have a relationship to
the driving CAEAnalysis item revision.
CAGE Code
See Commercial And Government Entity (CAGE) Code.
calendar
Defines working times.
certified platform
Platform the base product is certified to operate on. Compare with supported platform.
CGM
Computer Graphics Metafile (CGM) is a file format for 2D vector graphics, raster graphics, and text.
change
Temporary or permanent change to a configuration, design requirement, or documentation.
changed effectivity package
Primary update package resulting from a user editing effectivity.
changed revisions package
Secondary update package created when the user releases a change to the product structure by releasing new assembly item revisions.
Change Manager
Teamcenter application used to track changes to a product throughout its life cycle. The user proposes a change to a product and then manages the entire cycle of review, approval, and
implementation of the change. The user can articulate the work required to implement a change, assess its impact on any managed business items, and notify life cycle participants about
proposed and authorized changes. Before and after product configurations can also be compared.
change notification
Notice to vendors, manufacturing, marketing, and other entities describing part or all of the implemented change to a single change order. A change notification can also provide information
about the effectivity of the change order.
change order
Teamcenter object that references the problem, originating change requests, solutions, and related information. A change order contains sufficient information to incorporate the change.
change request
Teamcenter object that requests a change, reference the problem, proposed solutions, and related information. A change request contains sufficient information to allow a decision to proceed
further with the change.
change review board
Group of users who review and authorize an issue. A review board provides a checkpoint for determining whether an issue should proceed.
change specialist
Issue Manager user who manages the processing of issues from their initiation until their final resolution.
change type
Template of a change process. Change types are created by a system administrator using the Business Modeler IDE.
Change Viewer
Teamcenter application used to manage the process of controlling changes to a product's definition and configuration. Change Viewer provides an auditable history of the objects used in a
process, making an object's uses traceable. A site can use Change Viewer to propose, incorporate, review, and approve changes. Change Viewer can also be used to track and report change
history and to notify members of changes to their organization.
characteristic definition
Information related to a neutral part that is important for service organizations maintaining assets. You can create characteristic definitions that contain information to be measured against the
physical part, such as how long a product has been in use. You can also create characteristic definitions that contain data to be measured against a physical part, such as temperature or oil
pressure.
Chemical Abstracts Service number
Unique number assigned to a substance by the Chemical Abstracts Service organization.
class
Set of objects that share the same list of attributes but distinguishable by the value of the attributes for specific objects.
class folder
Representation of aggregation of objects. In the Classification and Classification Search dialog class hierarchies, classes are displayed with class folder icons because they represent an
aggregation of objects.
class hierarchy
Structure defining subclasses that inherit the attributes of their superclasses, also called their parents or ancestors.
classification
Process of categorizing objects according to similarity in characteristics. While the objects in one class share the same characteristics, the values of these characteristics may differ. For
example, drill bits all share the length and diameter characteristics, but drill bit objects differ in length and diameter.
Classification
Teamcenter application that utilizes a classification hierarchy to categorize product data.
Classification Admin
Teamcenter application that enables a system administrator to define the groups, classes, subclasses, and views that form the Classification hierarchy.
classification hierarchy
Structure used to categorize a company's data by common attributes.
classification hierarchy tree
Display of the classification structure—groups, classes, subclasses, and views—in a tree-like structure to maintain context during use of Classification Admin.
classification instance
Lowest-level component of the classification hierarchy. Also referred to as an ICO (internal classification object).
classification object (ICO)
Representation of a Teamcenter object within the classification system that extends the object with classification data. ICOs specify the values of attributes defined by a particular storage class
within the classification hierarchy.
cleanup phase
Phase when necessary repair actions on third sites and the ODS are performed. In addition, external site repair actions can be performed along with any actions required to address volume
data. If the source site is to be decommissioned, it is done as the final action of this phase. See also execution phase.
clearance database
Teamcenter database that stores the results of clearance analyses performed on assemblies in the rich client Design Context, Structure Manager, and Multi-Structure Manager applications.
clearance database server
Server required to enable users to perform clearance analysis in the rich client Design Context, Structure Manager, and Multi-Structure Manager applications. A batch process performs a
clearance analysis on an assembly and Teamcenter stores the results in the clearance database.
ClearCase Integration
Teamcenter integration to the IBM Rational ClearCase software configuration management tool.
client
Role played by a software component of a system when it requests particular services be performed on its behalf by another entity, a server. See also server.
client tier
Teamcenter architectural tier that comprises the Teamcenter clients, Teamcenter integrations with third-party applications, and the third-party applications associated with the integrations.
clone and reference
Copy action rule when using templates to create process structures. The object is copied to the database and a reference is made to the database clone. The reference is the same type as the
one in the template.
cloning rules
In a collaboration context, a set of rules that defines how structures are created when copying other structures of the same type. A cloning rule can also be applied when creating a structure
from a template.
closure rule
Definition or rule that allows the Teamcenter traversal algorithm to identify the additional objects required for a specific principal object.
clustered deployment (H*-SE)
Multiple HTTP servers configured in a cluster. All requests are sent to the cluster, which routes the request to a Java EE application server that is available to process the request. The
Teamcenter web tier application (EAR file bundling the WAR file) is deployed in each application server instance in the cluster.
clustered deployment with front-end, load-balanced HTTP web servers (H*-SE*)
Multiple HTTP web server instances are configured with a load balancer and a cluster of Java EE application server instances. A load balancer in front of the HTTP web servers balances the
load for incoming requests and HTTP web servers route that request to the cluster of application servers.
In this configuration, the Teamcenter web tier application (EAR file bundling the WAR file) is deployed in each application server instance in the cluster. Typically, HTTP web servers must be
configured for this type of distributed environment.
clustered deployment with front-end HTTP web server (H-SE*)
Stand-alone HTTP web server is configured with a cluster of web application server instances. The HTTP web server routes requests to a cluster of Java EE application servers. The
Teamcenter web tier application (EAR file bundling the WAR file) is deployed in each application server instance in the cluster.
CM Viewer (Classic)
See Change Viewer.
collaboration context
Teamcenter object that holds a collection of data contained in structure and configurator contexts. This data allows you to capture multiple different Teamcenter structures in one container. You
can open a collaboration context in the Multi-Structure Manager application, in Manufacturing Process Planner, or in Part Planner. You can also use a collaboration context to collect data to
share with a third-party application. See also structure context.
Command Suppression
Teamcenter application that enables the system administrator to control the display of menu and toolbar commands within Teamcenter applications. Command Suppression allows suppressing
the display of commands for an entire group hierarchy or a specific role within the hierarchy, for entire groups of users, and for users who are assigned a role within a group. It also allows
suppressing the display of specific commands on a designated menu or the display of entire menus.
Commercial And Government Entity (CAGE) Code
Unique five-character identifier assigned as part of the NATO Codification Systems (NCS) to suppliers to various government or defence agencies. CAGE Codes provide a standardized
method of identifying a given facility at a specific location. This reference enables users of the NCS to determine who supplies any given part. A CAGE Code chart provided by the NATO
AC/135 committee (the group of National Directors on Codification) describes the syntax of CAGE Codes in various countries.
CommercialPart
Business object type related to a Part object type by a structure relation. A commercial part is made externally by a vendor who resells, builds, or designs and builds the part for the OEM
(original equipment manufacturer). Commercial parts may be off-the-shelf market parts or custom-designed parts. A commercial part is a part whose form, fit, and function may be satisfied by
one or more vendor parts that the OEM may source from one or more vendors.
comparing tool
External software that can be run from Content Management to compare differences in topics. The comparing tool is installed on the client.
compliance officer
Role provided in Substance Compliance to perform various tasks, such as requesting material substance declarations from suppliers, reviewing the material substance declarations received
from the suppliers, and applying exemptions.
complying object
Object that must partially or completely fulfill a condition specified by a defining object. See trace link and defining object.
component
• Objects used to build up an assembly or subassembly.
• Part in a product structure defined in Teamcenter. A component is the lowest level part in the product structure: it cannot be broken down into subparts.
Component Process Manager (CPM)
Third-party application from PE International that is used for grading a part or BOM. CPM is referred to as substance compliance checker in Teamcenter.
composed document
Object containing the assembled content of a publication or topic after it is published. Similar to a reviewer document, you can use both types of documents to distinguish between those that
have been processed through the review process (composed documents) and those that have not (reviewer documents).
composition
Special kind of structure context that allows components to be added from one or more structure contexts, each of which may contain a different product structure. Compositions are used for
design studies and manufacturing processes that contain data from both product and plant structures.
compound property rule
Business rule that defines run-time properties on an object that references and relates to a property on a source object. Compound property rules relate to the property associated with type
components. Applied types are item, item revision, dataset, and form.
condition
Conditional statement that resolves to true or false based on the evaluation of an expression.
conditional link
Link that depends on the run-time values of business object attributes.
confidential material
Material that a supplier certifies as nonrestricted but wants the substance composition to be kept confidential for competitive reasons. The supplier provides the substance breakdown of the
confidential material; however, only authorized users can access the material composition.
configuration context (Appearance Configuration)
In Appearance Configuration, a revision rule used to configure the structure. Configuration context can contain only release status entries.
configuration context (Multi-Structure Manager)
In Multi-Structure Manager, a revision rule, variant rule, and closure rule applied to a collaboration context. See also collaboration context.
configuration context relationship
Teamcenter-defined Collaboration Foundation relationship. The configuration context relationship limits the view of a BOM to the parts and relationships that need to be transmitted to an ERP
system through the workflow process.
configuration rule
Rule that configures a structure. There are two kinds of configuration rules: revision rule and variant rule.
configuration specification
ClearCase file describing the versions of files that should be current in the specification’s associated view. The specification can contain general rules to get the latest version of all the files or a
specific version of a specific file in the archive.
Configurator rule
Condition that specifies the features or combinations of features not allowed. A configurator rule check is attached to an item revision.
connection
Object that defines the connectivity between two or more terminals in a physical model.
connection name
Automatically generated or user-provided name that identifies the connection between Teamcenter and Teamcenter Integration for AutoCAD.
connector (Global Services)
Global Services component that accesses information from a data source. Each connector accesses information from a particular type of data source. For example, Global Services provides a
connector for communicating with JDBC-compliant databases. Global Services offers optional connectors.
One implementation of a connector can communicate with multiple data sources by using different connector configuration files.
Global Services connectors are Enterprise JavaBeans. Enterprise customizers can create connectors to data sources using the Global Services connector APIs.
connector configuration file
XML-based file that specifies the data source a connector communicates with to obtain information.
For each instance of a connector, Global Services administrators create connector configuration files that describe the data sources the connector communicates with.
connector to Teamcenter
Enterprise JavaBean that connects Global Services with Teamcenter. The optional connector to Teamcenter is provided as a part of the Global Services connectors and supports both two-tier
and four-tier deployment configurations.
connector to Teamcenter Enterprise
Enterprise JavaBean that connects Global Services with Teamcenter Enterprise. The optional connector to Teamcenter Enterprise is provided as a part of the Global Services connectors.
connector wildcard
Wildcard used by a specific data source within the Global Services environment. The business object server (BOS) maps a BOS wildcard submitted by users to the connector wildcard used by
each data source. If the BOS is bypassed at the BOSClient layer, the connector wildcards must be used. See also BOS wildcard.
consolidation information
Data comprising a source site’s definition data and its product data that will be moved to the target site during the site consolidation process.
consolidation third site
Site that is not the source or target site in the consolidation. There are two categories—external site and other site.
constant
Configuration point within the data model. There are three kinds of constants: global constants, business object constants, and property constants.
constituent
Lowest level of the PLM material structure hierarchy (Formulated Item→Raw Material→Constituent).
consumable part
Nonrepairable item or repair part that can be discarded more economically than it can be repaired.
consumed item
Item that is required during a manufacturing process or operation and must be ordered regularly to meet the production quota. A consumed item can include parts or components from the
product structure in addition to materials such as oil, grease, and gloves.
container object
Any Teamcenter object used to hold other objects and organize product information. For example, folders and items are container objects.
Content Management
Teamcenter application that enables users to manage SGML and XML information stored in a Teamcenter database and publish documents in multiple formats using SGML/XML editing and
publishing tools. Content Management is used to collect and publish content, storing the content as components that can be reused in multiple publications, while links are maintained between
components. The application includes processes for structuring publications so that they can be stored, published, and used for different purposes. Content Management also stores and
manages graphics for use in publications, provides content revision control, and can incorporate Teamcenter workflows to facilitate the content development process.
coordinator
Schedule role in which members have both read and write access to the schedule.
copy
In Consumer Packaged Goods, an assembly of copy elements. Copy is mostly textual but can contain images and symbols that are printed on the package. It is the main form of
communication between the manufacturer and the consumer who buys the product. Because of the legal nature of the text, such as claims, the copy review process is an important step in the
package development life cycle.
copy action rule
Predefined rule that defines how a template is used to generate processes. Actions commonly performed include ignore, reference, and clone.
Copy by Reference
Copy action rule when using templates to create process structures. The same database object is referenced in the clone. The relation type is the same as in the template.
copy element
Individual piece of information that constitutes the package label.
corporate server
Host computer at the center of a Teamcenter network. This host contains the Teamcenter application root directory, Teamcenter data directory, licensing, File Management System (FMS), and
volumes. For installations that include the web tier (four-tier architecture), the corporate server also contains the Teamcenter server manager. Multiple application clients can map to or mount
the corporate server.
CPM
See Component Process Manager (CPM).
credentials file
XML file that defines a Global Services user name and maps the Global Services user name to the user's sign-on credentials for each data source connector in the Global Services
environment. There is one credentials file for each Global Services user.
The credentials file functions only with the Global Services XML credentials service. The Global Services LDAP credentials service accesses sign-on credentials from an LDAP database.
credentials service
Global Services component that finds and provides a Global Services user's sign-on credentials for a data source in the Global Services environment. Global Services provides two credentials
services, XML and lightweight directory access protocol (LDAP), and APIs for creating a custom credentials service.
credentials service configuration file
XML file that configures credentials services for each data source connector in the Global Services environment.
credentials service factory
Global Services component that manages credentials service objects and maintains mapping between data source connectors and associated credentials services.
Dashboard
Teamcenter application that provides an interface to Teamcenter reporting and analytics in Report Builder.
Database Utilities
Teamcenter application providing volume information, for example, the node name and the volume name.
data-driven smart folders
Pseudofolders representing the leaf nodes in the project hierarchy. Data-driven smart folders display project data objects.
Data Integration Services Adapter
Teamcenter software component that integrates Teamcenter lifecycle visualization with the rich client.
data item
Teamcenter object representing bulk data defined and manipulated by application products, for example, papers that reside in a filing cabinet, directories and files that reside in a file system,
Microsoft Excel spreadsheets, and CAD model and drawing files. Metadata for the data item resides in the Teamcenter database. See also bulk data and metadata.
data map rule
Rule that describes items that are linked with each other, the relation between these items, and the information in the input item that must be transferred to an output item.
data model
Abstract model that describes how data is represented and used.
data segment
Portion of a Global Services business object definition that describes the data from one data source.
dataset
Teamcenter workspace object used to manage data files created by other software applications. Each dataset can manage multiple operating system files, and each dataset references a
dataset tool object and a dataset business object.
dataset business object
Teamcenter object that contains a list of tools that can operate on a dataset.
dataset tool
Teamcenter object that is the tool used to create or modify a dataset.
data source
System that manages enterprise data and can be accessed by Teamcenter. Examples are product knowledge management (PKM) systems, product lifecycle management systems, relational
databases, enterprise resource planning (ERP) systems, component and supplier management (CSM) systems, mechanical design automation (MDA) systems, purchasing systems, systems
engineering GroupWare, and Service Lifecycle Management (SLM) systems.
datastore
Java Database Connectivity (JDBC) database instance used to store the Global Services configuration and business object definition (BOD) information. The majority of the objects in the
datastore are stored as serialized objects for improved performance. The configuration and BOD files are serialized during the process of uploading them to the datastore. Global Services
users with administrator privileges can access the Configuration Object form in Global Services that allows them to add, remove, and update objects in the datastore. See also business object
definition file.
data transfer plan
Plan that consists of defining the following site consolidation topics:
• Partitions
• FMS or volume structure set up to support the volume strategy
• Partitions to be moved in each execution increment
• Mappings to be accomplished during product data transfer
datum
Line, point, or plane that provides a reference location. In manufacturing, datum points are used to help place parts in a fixture or jig.
deep copy rule
Business rule that defines whether relational type objects can be copied as object, copied as reference, or not copied when the user performs a save-as or revise operation.
defining object
Object that specifies a condition that a product or a component must fulfill. See trace link and complying object.
delegated service request
Identifies work that needs to be done by another service organization. A primary service request can have multiple delegate service requests, but a delegate can only belong to one primary
service request.
delivery unit
Subassembly that is manufactured separately and delivered to the assembly plant as a consumed part. One of the operations in the assembly process uses the delivery unit as a consumed
part. The components of a delivery unit are not consumed in any of the operations.
dependent object
Object that, if it exists, must be included in the set of objects implied by the principal object and the closure rules to correctly form the island of data. See also island of data. Contrast with
principal object.
derived default
Default value that depends on a condition (for example, radio = stereo IF car type = GLX). Compare with fixed default.
derived visualization data
File objects created by translating source data to other formats to support actions such as viewing and markups. Also called presentation data and neutral data. For example:
• An item revision with a Microsoft Word dataset is rendered and the Microsoft Word dataset file is translated to a PDF file.
• A large image is rendered as a thumbnail image.
• An NX PRT file is translated and rendered as a JT file.
See translate and render.
design bill of materials
List of components and subassemblies used to define an assembly structure, and the representation of the assembly structure. Compare with manufacturing bill of materials.
design brief
Captures the creative and technical design aspects of the package design.
design component
Occurrence of a design item within a product design.
design concept
Represents early-stage sketches of the packaging structure.
Design Context
Teamcenter application that enables users to quickly focus on a particular work part and any parts affected within the context of a change to that part. Users can select a product item and
configure revisions of components, configure variants of the assembly, review the set of components, retrieve the components, and initialize their display in a CAD application or a visualization
application.
design item occurrence
Design representation of a component in a product. Design item occurrences typically maintain geometric data and are authored in CAD systems.
deviated physical part
Physical part installed in a physical structure that is not the preferred part or designated as a valid alternate or substitute to the preferred part.
deviation document
Document that authorizes the installation of a physical part that is a deviation from the design structure.
deviation request
Request that seeks consent to deviate from a solution in production to resolve a set of problems to initiate improvements. Typically, it either requests a deviation or a waiver.
deviation workflow
Process flow, reviewer’s list, and business validations required to route a deviation document for review and approval.
device
Complex assembly that is represented as a simple component. A device is designed to work as part of a machine tool or robot.
digitally sign
Teamcenter action that lets you add your digital signature to an electronic document using third-party software, for example, Adobe Acrobat/Reader for an Adobe Portable Document Format
(PDF) file.
digital signature
Mathematical stamp on an object used to indicate if that object has been modified after the signature was applied. It also identifies who applied the digital signature.
A type of digital signature, PKI digital signature, requires public key infrastructure (PKI) authentication when applying the digital signature.
Direct Materials Sourcing revision line item
Part of a Direct Materials Sourcing revision; contains an assembly or part with specific context rules.
direct model dataset
Dataset containing a JT (visualization) file.
discipline
Set of users who have a common behavior, for example, developers that have expertise in UNIX.
dispatcher client
Solution that runs the Dispatcher to perform CAD translation and create required relationships in Teamcenter.
Dispatcher request
Embeds information about the source file location and type of translation.
Dispatcher Server
Component that handles the specific computational and pipeline mechanisms to execute translation tasks.
Dispatcher service configuration
Object that defines the visualization file format that a dataset file is translated into.
disposition (change management)
Decision about how to proceed with a change object. A disposition may reflect a business implementation or technical decision about a change object (None, Investigate, Approved,
Disapproved, Deferred).
disposition (Service Manager)
Defines whether the physical part is in an operational or a nonoperational state. For example, the part disposition can be an operational disposition such as In-Service or a nonoperational
disposition such as In-Repair.
distribution server
See rich client distribution server instance.
distribution server instance
See rich client distribution server instance.
DITA (Darwin Information Typing Architecture)
XML-based architecture for developing technical publications. It includes an architectural specification, language specification, and DTD and schema implementations of the language.
document
Subtype of an item that represents all revisions of a real-world document. This item type supports documentation for products, processes, standards, and other aspects of a business, typically
from applications such as Microsoft Word, Microsoft Excel, and so on.
document-centric program
Program that requires parts to be linked to a source document.
document management
Management of real-world documents through the use of item revision definition configuration (IRDC) objects to configure document management behavior. IRDC simplifies user interaction
with information and reduces the need for users to understand the Teamcenter data model and relationship model. See also item revision definition configuration (IRDC) objects.
domain
Name of the business object type in a multifield key. For example, in the Part{item_id} key, Part is the domain. Because all children of a business object type inherit the domain part of the key,
they belong to the same domain. See also multifield key.
Do task
Task template that includes the EPM-hold handler, which stops the task from automatically completing when the task is started. This template has a customized dialog box that allows
administrators to set a check box to indicate when the task is complete.
DPV Admin
Teamcenter application that enables the extended enterprise to collect, manage, dimensionally analyze, and report on quality measurement information in Dimensional Planning and Validation.
drawing file
Teamcenter CAD file containing a 2D vector image or 2D raster image.
DTD
Type of schema used to validate XML content.
DWG
Default extension used by Autodesk for its AutoCAD drawing files in MS-DOS and Windows.
DXF
Drawing eXchange format.
dynamic attribute value
Attribute value that varies based on the values of other attributes. A Tool Command Language (Tcl) script determines the attribute value by performing operations on the values of other
attributes.
dynamic participant
Participant who is automatically assigned to perform workflow tasks based on the participant type, such as Analyst or ChangeSpecialist. Dynamic participants are assigned through workflow
handlers.
dynamic storage data
eIntegrator Admin method of data storage in which mapped properties of data stored by proxy are run-time properties. This method of storing data minimizes Teamcenter storage requirements
by storing only the keys for retrieving external data in subsequent sessions, rather than storing the external data in the database. Data retrieval from the external source is performed each time
the form is opened. Compare with persistent storage data.
ECU
See electronic control unit.
editing tool
External software used to author and edit XML and SGML content. It is installed on the client and launched when editing a topic in Content Management.
effectivity
Identification of the valid use of an aspect of product data tracked by unit, date, or intent. You can specify a start definition, end definition, or both for a particular effectivity. There are three
types of effectivities:
• Unit effectivity specifies the range of item units or serial numbers.
• Date effectivity specifies the range of dates. This is also known as an incorporation point.
• Intent effectivity specifies a purpose, target, or milestone, for example, Production, Prototype, or Carryover.
effectivity release date configuration transition
Dividing line in the product structure between unit number effectivity configuration (above the line) and date released (below the line). Parts above the line are typically identified by some
attribute on the item master form attribute.
effectivity rule
Rule used to set effective dates on released products and processes with a released status.
eIntegrator Admin
Teamcenter application that provides a simple integration mechanism you can use to integrate external data with Teamcenter. eIntegrator Admin maps external data systems into equivalent
objects in its database. The data can then be imported into the database as forms.
eIntegrator Admin form type
Specialized form type for eIntegrator Admin in which form information is obtained from an external source and form type mapping information is stored in a mapping object. Each new
eIntegrator Admin form type creates a system-generated subclass of the foreign data class.
elaboration
Division of a change request into a number of manageable tasks.
electronic control unit
Self-containing processor unit that controls electromechanical functions within a product structure.
Embedded Software Solutions
Optional extension to Structure Manager and My Teamcenter that allows you to manage embedded software binaries as part of the product structure.
eM-Planner interface
Interface between Teamcenter manufacturing process management and Tecnomatix eM-Planner that allows data exchange.
encapsulation
Active-mode relationship between an application and Teamcenter in which the application is brought into the Teamcenter environment. Encapsulation allows you to launch the application using
a Teamcenter dataset object, export data to the application, work in the application, and import data back into the Teamcenter database during a session. The import and export operations
between Teamcenter and the encapsulated application are executed from within Teamcenter and the actual transfer of files is transparent to the user. See also active mode and Integration.
end item
Top-level node of an assembly that can represent a product or a factory structure.
end item effectivity
Date or unit number suggesting when the released configuration is used for production of the specified end item.
engineering change notice (ECN)
Provides a detailed work plan to resolve one or more enterprise change requests (ECRs) or a portion of one ECR. An ECN identifies all items and documents affected by a change and
authorizes the actions that address a change.
engineering change request (ECR)
Initiates proposals that recommend changes and capture business decisions associated with the change. Change requests state the cost estimates and benefits of a change and provide
recommended actions. Change requests are sometimes responses to problem reports.
enterprise archive (EAR)
Enterprise application that requires a Java EE application server.
enterprise BOM
Bill of materials that includes the lines of usage (LOUs) for all configurations and effectivities in the product. See also line of usage (LOU).
enterprise process modeling
Modeling used to accomplish workflow objectives. Enterprise process modeling models workflow processes, allocates resources, and manages data according to business rules.
enterprise tier
Teamcenter architectural tier that comprises a configurable pool of Teamcenter C++ server processes and a server manager. Larger sites can distribute the pool of server processes across
multiple hosts. Smaller sites can run the pool of servers on the same host as the web tier.
envelope
Teamcenter workspace object that represents a mail message sent by a Teamcenter user. Envelopes can be used to send workspace object references as well as text messages.
environment variables script
Teamcenter script (tc_profilevars) that sets variables for the Teamcenter environment. This script sets all Teamcenter environment variables except TC_ROOT and TC_DATA.
equipment
Description of the equipment used to perform manufacturing operations.
ERCT
See effectivity release date configuration transition.
erp_object
Teamcenter construct used in the mapping schema to map Teamcenter objects (for example, item revision or BOM) to the corresponding objects in the receiving ERP system (for example, part
master and BOM). It also defines which attributes are to be transferred, how their value is stored in Teamcenter, and various associated parameters (for example, default value and LOV). The
value may be defined on an existing Teamcenter attribute (for example, item ID), or user-defined, typically in a form (for example, MRP type).
ERP Connect Toolkit
Teamcenter toolkit that can be configured to create an interface between Teamcenter and ERP systems.
ERP Connect to SAP
Teamcenter integration that allows the controlled, auditable transfer of product information from Teamcenter to SAP.
ERP form
Form that is defined in the mapping schema.
error ID
Randomly generated number unique to each Global Services exception (a 9-digit number in 3 groups of 3). Global Services displays the error ID and a general message to the Global Services
user and includes the same error ID with a more detailed description for the administrator or customizer in the Global Services message log.
Exclude_License
Denies specific users or groups access to the attached workspace objects for a period of time.
execution
Process of implementing the change (change request and tasks) once the change is authorized.
execution increment
Subphase of the site consolidation execution phase that consists of:
• The initial time period when the product data is replicated from the source to the target site.
• The time critical period when the ownership changes occur for the replicated data.
See also execution phase.
execution phase
Phase following the preparation phase when the consolidation activity of transferring source site product data and users to the target site is performed. For large source sites, multiple execution
increments may be necessary to compete this phase. This phase is followed by the cleanup phase. See also cleanup phase.
exemption
Exemptions to a regulation are granted to narrowly defined applications for which the elimination of prohibited substances is technically or scientifically impracticable. Exemptions are also
applied to a regulation when the only available substitution produces more negative results than positive benefits to the environment, health, or consumer safety.
export record
imanExportRecord object that is attached to the master object or replicated objects and identifies sites that have replicas.
extensible
To fit customer specific requirements or customizations not covered in the out-of-the-box solution, Dispatcher supports extensions to the complete system for how the data is collected, adding a
new translator, and loading of the generated data back into the PDM system. Java documents and example implementations are provided for ease of customization.
extension
Method or listener implemented for an extension point.
extension point
Event or capability in the system, such as a precondition, preaction, or postaction, that allow you to implement custom behavior.
extension rule
Business rule that adds predefined behavior to a business object's operation and fires as a precondition, preaction, or postaction.
external extension
Extension created by a user to implement customized behavior.
facility
Physical location in an enterprise (for example, manufacturing plant or design center). One facility can comprise multiple sites. Compare with site.
family
Attribute of a product item revision with a set of allowed features (for example, family = engine: 1200, 1600). Families are used when specifying variant data to configure a variant of the
product. Feature names are unique within the product but not within the database.
fast track change
Change process in which the user can plan a change, approve it, and begin execution without the review or approval by a separate Change Review Board. Fast track is normally designated for
changes that meet prescribed criteria such as low risk or low cost.
fault code
Identifier that indicates an itemized fault or problem that a manufacturer has identified with a part.
FCC
See FMS client cache (FCC).
FCC configuration file
File that configures an individual FMS client cache (fcc.xml). The FCC configuration file defines such values as the parent FMS server cache location and the location and size of the client
caches. Values defined in the FCC configuration file can override default values defined in the FSC configuration file.
feature
Physical or geometric object associated with a product, component, or part. Alternatively, a logical attribute of a product, component, or part. Examples: a weld point, a signal, or a geometric
pattern. A feature may be represented by a generic design element (GDE) in a BOM. See also generic design element.
File Management System (FMS)
System that manages uploading and downloading file data between clients and volumes in both two-tier and four-tier architecture deployments.
• FMS provides volume servers for file management, a shared server-level performance cache for shared data access between multiple users, a client-based private user cache for rich
clients, and a transient datastore mechanism for transporting reports, PLM XML, and other nonvolume data between the enterprise and client tiers.
• FMS file caching enables placing the data close to the user, while maintaining a central file volume and database store.
filter rule (Simulation Process Management)
Structure map rule that provides a mechanism to filter or remove components from a structure.
filter rules (PLM XML)
Rules that allow a fine level of control over which data is translated, in PLM XML format, along with the primary objects by specifying that a user-written function be called to determine the
operation applied against a specified object.
find number
Number that identifies individual occurrences (or groups of occurrences) within a single-level assembly. Components are ordered by find number within an assembly.
finished product
Assembly of two or more items with a unique package associated with it. A finished product represents consumer units and shipping units. It can contain other finished products and can have
an associated trade item.
first class attribute
Attribute where the attribute name is attached directly to the class object. For example, PartNumber is a first class attribute attached to the Part class.
First class attributes can be viewed and queried both in SQL and Teamcenter query dialog boxes. In Teamcenter Integration for NX I-deas, queries can be performed on first class attributes.
Some first class attributes can be modified and others are read-only. See also attribute and second class attribute.
fixed default
Default value for an option (for example, engine = 1200). A fixed default is attached to an item revision but is global to the BOM loaded in a Structure Manager window. Compare with derived
default.
FMS
See File Management System (FMS).
FMS client cache (FCC)
FMS process that runs on a client host, uploading files to an FMS server cache process, requesting files from an FMS server cache process, and caching files on the client host. The FCC
process manages two caches of whole files: a write cache containing files uploaded to a Teamcenter volume and a read cache containing files downloaded from a Teamcenter volume. It also
manages one segment file cache for Teamcenter lifecycle visualization. Each Teamcenter rich client host requires a local FMS client cache.
FMS master configuration file
File that configures FMS (fmsmaster.xml). The FMS master configuration file describes the FMS network and defines groups of server caches. It can also define default values for server
caches and client caches, such as maximum sizes. Values defined in the server cache configuration file and in the client cache configuration file can override the default values defined in the
master configuration file.
FMS master host
Host that contains the FMS master configuration file (fmsmaster.xml). This file is optionally mounted at each FSC server.
FMS server cache (FSC)
FMS process that runs on a server host and performs as a volume server (when running on a host where a volume is located or directly mounted) or a cache server (when running on a host
where a volume is not located or directly mounted) and a configuration server. As a volume or cache server, the FSC checks all file access requests for a ticket that Teamcenter generates to
authorize file access. As a cache server, it manages two segment file caches, one for downloading files and one for uploading files. As a configuration server, it provides FMS configuration
information to file client caches and other FSCs. As a transient server, it delivers PLM XML and other transient files to clients. A minimum of one FSC must be deployed in any Teamcenter
installation. Multiple FSCs can be deployed, with each FSC performing one designated purpose as either a volume, a cache, or a configuration server.
folder
Graphical representation of an aggregation of objects, such as a group, class, or subclass. For easy distinction in the class hierarchy, each of these aggregations has a different type of folder
icon associated with it: a group folder icon, a class folder icon, or a subclass folder icon.
form
Teamcenter workspace object used to display product information (properties) in a predefined template. Forms are often used to create an electronic facsimile of a hardcopy form in
Teamcenter. See also master form.
formal partition
In site planning, a partition that is created from a partition item or another partition. A formal partition has an identifier that can be queried. Contrast with ad hoc partition.
formal relationship
Relationship modeled and maintained by a data source. To navigate a formal relationship, a request must be made to the data source.
form type
Special type of the general POM Form class, which can have its own set of properties (attributes) associated.
formula spec
Type of specification that represents the composition of the ingredients that make up the material.
formulated item
Represents the final or intermediate formulated material that has a unique formula and a unique process to make it.
four-tier architecture
Teamcenter architecture that includes four tiers: resource tier, client tier, web tier, and enterprise tier. Contrast with two-tier architecture.
four-tier deployment
Deployment of the Teamcenter four-tier architecture. The web tier, enterprise tier, resource tier, and client tier can each be hosted on the same or separate computers.
frequency
Interval or period that defines when a maintenance requirement is due.
FSC
See FMS server cache (FSC).
FSC configuration file
File that configures an individual FMS server cache (fsc.xml). The FSC configuration file defines such values as the address of the master FSC, the maximum sizes of the segment file caches,
and the upload time-out value. It can also define default values for FCCs and other FSCs.
FSC group
Group of server caches defined in the FMS master configuration file.
Gantt chart
Visual representation of a schedule's tasks.
gate
Special task that provides criteria to determine if the phase is completed.
GDE
See generic design element.
genealogy
History, or supersedure trail, of a part.
generic design element
BOM item that cannot have different revisions. See also feature.
Generic Relationship Management rule
Rule that defines the relationship between two business objects. The rule has the following constraints: cardinality, changeability, attachability, and detachability.
geometric cut
Technique for modeling the removal or subtraction of material from one geometric body, based on the shape of another geometric body (typically a tool). It is used to model through-holes and
bores.
Getting Started
Teamcenter application that provides a point from which to quickly start working in Teamcenter. Lets you search for a part, open your worklist, view or edit product structure, or view or edit
classification data.
global alternate
Alternate that is interchangeable with another part, regardless of where the part is used in the product structure. A global alternate applies to any revision of the part and is independent of
views.
global constants
Constants that provide consistent definitions that can be used throughout the system. These constants have only one value, either the default value or the value you set.
Global Services adapter
eIntegrator Admin adapter connects eIntegrator Admin to Teamcenter Global Services, a Web-based application enabling clients to access information stored in virtually any type of data
source that manages site data.
Global Services connector
Global Services component that accesses information from a data source. Each connector accesses information from a particular type of data source. For example, Global Services provides a
connector for communicating with JDBC-compliant databases. Global Services offers optional connectors.
One implementation of a connector can communicate with multiple data sources by using different connector configuration files.
Global Services connectors are Enterprise JavaBeans. Enterprise customizers can create connectors to data sources using the Global Services connector APIs.
Global Services Foundation
web application that enables your enterprise to access information stored in virtually any type of electronic data source that manages your enterprise data.
Running on a standard commercial web application server, the server components of Global Services Foundation enable communication among the data sources and between users and the
data sources. All components of Global Services Foundation use standard web technology: Extensible Markup Language (XML), Extensible Stylesheet Language (XSL), and the Java
programming language. Users access Global Services Foundation from a commercial web browser using the standard technologies of web browsers, primarily support for HyperText Markup
Language (HTML) forms and small Java applets.
Global Services message receiver
Global Services component that pulls messages out of an action queue on a JMS message server and posts the results to a response queue on the JMS message server.
The Global Services message receiver is used when an optional third-party JMS message server is included in the Global Services architecture.
Global Services message server
Global Services component that provides a communication doorway between Global Services and messages initiating in a data source system. The message server provides message
distribution, logging, and recovery services for Global Services.
The Global Services message server is an Enterprise JavaBean. Compare with JMS message server.
global setting attribute
Element in a mapping file used to define global data to control transfer and set default values.
graphical element
Represents the images that appear on the package.
graphical reports
Technical portfolios that have been saved to the Report Server for viewing as reports from the DPV Viewer Web Part. A graphical report can contain DPV Reporting & Analysis annotations and
3D model data. The report is updated with the latest engineering data either on a schedule, when triggered by an event, or on demand as the report is opened. It can be viewed in HTML or
PDF format.
graphic attribute mapping
Object that controls how a file name or attributes on a graphic file being imported are mapped to properties in Content Management. A graphic attribute mapping can map file names or
attributes to both graphic options and graphic items.
graphic item
Parent object that has one or more graphic files related to it. The graphic files contain the same image but are of different file types.
graphic option
Graphic object of a specific file type, for example, .png and .bmp. It is related to a graphic item, which is the parent object of graphic options that have the same image but are of different file
types.
graphic priority list
Object that specifies the priority with which graphic options are selected when content is viewed or published.
graphic translation
Object that is created when a graphic is included with topics that are translated and received.
GRM rule
See Generic Relationship Management rule.
group (Classification)
Container used to organize large sets of related classes in Classification Admin. Groups reside at the highest level in the classification hierarchy and can be nested to include other groups.
group (Organization)
Organizational grouping of users at a site. Users can belong to multiple groups and must be assigned to a default group.
group administrator
User with special maintenance privileges for a group.
group approver
User who is a signoff in a workflow process with a specific group of users. In Access Manager, the group approver accessor is used in Workflow ACLs and matches the signoff definition (that
is, group) for the release level associated with the Workflow ACL. The group approver accessor ensures that only signoffs are given privileges, not a user who matches the group. See also
approver, RIG approver, and role approver.
group folder
In the classification hierarchy, group folders represent a group of related classes.
group preference
Teamcenter preference applying to an entire group.
H*-SE
See clustered deployment (H*-SE).
H*-SE*
See clustered deployment with front-end, load-balanced HTTP web servers (H*-SE).
harness
Assembly of insulated conductors formed to a predetermined pattern or configuration; also called a wiring harness.
heterogeneous network environment
Teamcenter network environment consisting of hosts that do not all run the same platform, for example, a corporate server running on a UNIX host, a web application server running on a Linux
host, and workstations running on Microsoft Windows.
Contrast with homogeneous network environment.
hierarchy
Structure in which each node can have only one parent but possibly multiple siblings and children.
historical revision
Any revision other than the latest.
historical summary reports
Access measurement data stored in the DPV SQL Server Analysis Services (DPV-SSAS) cube. The reports can include information about measurement data, as well as standard statistical
summary charts for different time ranges (daily, weekly, and monthly). The data is based on the latest revision of the routine in Teamcenter, and you can view your revisions within the report.
historyless appearance set
Appearance set that does not record history. Its status differs from the status of the production appearance set.
homogeneous network environment
Teamcenter network environment in which all hosts run the same platform, for example, a corporate server, web tier, and Teamcenter clients all running on Microsoft Windows or all running on
SUSE Linux.
Contrast with heterogeneous network environment.
HSE
See basic deployment (HSE).
H-SE
See basic deployment with front-end HTTP web server (H-SE).
H-SE*
See clustered deployment with front-end HTTP web server (H-SE*).
IBI adapter
Adapter used with eIntegrator to connect to IBI-supported systems. This adapter provides a link to IBI systems from Teamcenter.
ICM root folder
Root folder in the classification hierarchy. There is one root per database.
ICO
See classification object (ICO).
ID context rule
Context that defines when you use unique item IDs. ID contexts are used when you create alias or alternate IDs.
I-deas
Siemens PLM Software’s integrated CAD/CAM/CAE solution that is used to design, analyze, test, and manufacture products.
IDSM
Integrated Distributed Services Manager. It acts as an object transporter in a Multi-Site Collaboration network. It provides the mechanism used to export an object from the owning site, transmit
it over the network, and import it into the destination site.
IDSM server
Integrated Distributed Services Manager, a network node that runs a daemon process to handle the transfer of data objects among sites in a Multi-Site Collaboration network. One IDSM server
node must be designated for each Teamcenter database from which objects are published; each server node can act for one database only.
IGES
Initial Graphics Exchange Specification (IGES) defines a neutral data format that allows the digital exchange of information among CAD systems.
Ignore
Copy action rule when using templates to create process structures. No action is taken to duplicate the object in the cloned structure.
immutable revision
Revision whose state is preserved and protected from further modification.
impacted item
Item revision to be changed as a result of the change process. It may be a detailed part or an assembly. A release status is attached by the workflow process the change is put through.
impacted part
Physical part impacted by service work. An impacted part will likely be revised to record the execution of a service request.
implemented by
Change notice that corrects the problem addressed by the change request or the change request that addresses the problem in the problem report. They are stored in the Implemented By
folder of the implemented object in Change Manager. For example, the change request’s Implemented By folder contains the change notice.
implements item
Problem report that is addressed by a change request or a change request that is addressed by a change notice. They are stored in the Implements folder of the implementing object in
Change Manager. For example, the change notice’s Implements folder contains the change request.
imprecise assembly
Single-level assembly that has items as the components. The revision is determined by the revision rule settings. Compare with precise assembly.
imprecise reference
Reference to a revisable instance, independent of any revision.
inactive and invisible program
Program in which the associated data cannot be viewed or modified by the program team members.
inactive program
Program in which the associated data is read-only; that is, data is visible to the program team members, but it cannot be modified.
Include rule
Structure map rule that provides a mechanism to add and position an existing item revision as part of the output structure that was not a part of the input structure.
incremental change
Engineering change that collects several individual changes to components or attachments in a structure, allowing them to be released simultaneously. An incremental change is released and
effectivity is applied to it by attaching an appropriate release status.
infer delete
Mechanism of deleting relations between objects that were present in the earlier import but not present in the current import. This mechanism informs the importing site about any relation
deletion that occurred in the exporting site.
informal relationship
Relationship navigated by the Global Services business object server using foreign key data browsing.
initiating user
PDM user in the local PDM domain with active logons to the home application and to Global Services.
initiator
Data source component that sends data source messages to the Global Services message server through an HTTP or HTTPS request.
An initiator is required only when the data source must provide information to other data sources in a Global Services environment.
The initiator is not an integral part of the data source system; it is created by Global Services customizers.
in-process model
Product resulting from application of a manufacturing operation.
input data
In-process model and other data generated from the previous steps in an operation.
installation assembly
• Assembly that defines the purpose of a component in a product structure. The collective set of installation assemblies for a product represent the generic structure of the product. Within a
product development process, the installation assembly is an engineering building block that collects components of a close physical relationship in the context of the end product.
Installation assemblies do not contain background parts. Appearances of components are defined in a single installation assembly per product structure.
• Node in the CAD structure to which design solutions are added and variant conditions applied, according to the named variant expression selected on the architecture element. An
installation assembly (IA) can be associated with an architecture element to guide the designer by limiting the named variant expressions from which to choose when adding a design to
the product. Any structures above an installation assembly are for organizational and navigational purposes only—there are no transforms or geometry above an IA. IAs are designed in
product space and are therefore all positioned correctly relative to one another when viewed together.
instance
Single data object that is associated to a class. The instance can correspond to a line in the BOM.
Integration
Active-mode relationship between an application and Teamcenter in which Teamcenter is brought into the application. The application drives Teamcenter to provide the functionality, such as
implicit checkout when data is modified, and reading and writing data directly from Teamcenter in a secured way. Data is exported (pushed) and imported (pulled) as needed.
Integration Toolkit (ITK)
Set of software tools provided by Siemens PLM Software used to customize Teamcenter or to integrate third-party or user-developed applications with Teamcenter. The ITK is a set of C
functions used directly by Teamcenter and NX.
interface port
Single access point to the functionality of a piece of equipment, for example, a USB port that provides an interface to a computer.
internal extension
Extension delivered as part of the Teamcenter product, also known as a canned method.
IP_License
Grants discretionary access to specific users or groups to workspace objects that have IP classification. It grants the access for a specified period of time.
IRDC
See item revision definition configuration (IRDC) objects.
island of data
Fundamental unit of transfer for moving data objects between sites. It consists of a principal object and the additional objects on which it depends (identified by closure rules) for its correct
functional definition and usage within Teamcenter. See also principal object and dependent object.
issue
Concern that does not appear to require product structure changes or extensive change management. Issues may be converted to problems. Contrast with problem. See also issue report.
issue list
Displays a set of issues based on defined search criteria such as particular status or type of issue. You can have as many issue lists as you like.
Issue Manager
Teamcenter application that enables customers to track and view problems or issues with a product. Use it for problems with highly visual information or those that do not need to be addressed
through an extensive, standardized change management process, such as the one that Change Manager supports.
issue report
Object used to track and fix problems with a product. It contains information about the problem, including relevant parts, snapshots, and reference data. It records reviewer’s decisions and
comments about the issue. Reviewers can approve, fix, reject, defer, close, or approve issue reports.
ITAR license
Grants discretionary access to specific users or groups to workspace objects with ITAR classifications for a specified period of time. It is typically used to grant access for a specific time period
to citizens of other countries, United States (U.S.) citizens physically located outside the U.S., or organizations that are named in an effective Technical Assistance Agreement (TAA) through an
International Traffic in Arms Regulations (ITAR) license.
item
Workspace object generally used to represent a product, part, or component. Items can contain other workspace objects including other items and object folders.
item_id
Workspace object property that defines an item ID. This property is associated with a product, part, or component. The item_id property can be used in conjunction with other properties to
create a unique multifield key ID. See also multifield key.
item export record
ItemExportRecord object that contains the import or export options used when exporting an item.
item relation
Description of an association between a Teamcenter item and a piece of information that describes or is related to the item.
item revision
Workspace object generally used to manage revisions to items.
item revision definition configuration (IRDC) objects
Objects that define how item revisions are handled at specific times in the life cycle, such as at item creation, checkin, checkout, save as, and revise. IRDC objects are defined in the
Teamcenter Business Modeler IDE application. Any item can be associated with an IRDC. For example, IRDC objects typically support business processes by managing document checkin and
checkout and by specifying rendering of visualization or markup versions from source datasets.
item revision relation
Description of an association between a Teamcenter item revision and a piece of information that describes or is related to the item revision.
ITK
See Integration Toolkit (ITK).
ITXR
Item export record (ItemExportRecord object) that contains the import or export options used when exporting an item.
IXR
Export record (imanExportRecord object) that is attached to the master object or replicated objects and identifies the sites that have replicas.
JDBC connector
Enterprise JavaBean that connects Global Services to data sources using the Java Database Connectivity (JDBC) API.
The JDBC connector is provided as part of Global Services.
JMS message server
Optional third-party message server that conforms to the Java Message Service (JMS) API. Adding a JMS message server assures delivery of data synchronization messages and allows you
to manage the number of messages allowed into the system at one time.
Compare with Global Services message server.
job card
Specific service action on a physical asset that is carried out by a service technician to fulfill a work order.
job task
Service action steps performed by a service technician to complete the service work documented in a job card or another job task.
KBL
KabelBaumListe (wire harness description list), an industry standard for wiring models. KBL is based on the STEP AP212 object model.
key
Field in a record holding unique data that identifies the record from all other records in the file or database. Each key value must be unique in each record.
key-LOV
List of legal values that can be associated with an attribute definition. Key-LOVs differ from standard Teamcenter LOVs in that each value entry in the list has an associated key ID. It is this key
ID, rather than the value, that is stored in the database with the attribute. Therefore, if a value must be changed globally within the classification system, the system administrator can modify the
description of the value for a key-LOV ID/key combination.
keyword
Defines attribute values and global settings, and typically represents properties (for example, IRM:attr 1 is used to get the attr 1 value from the Item Revision Master form).
label (ClearCase Integration)

String designating a state of software maturity applied to a group of ClearCase software files. In ClearCase, a label might be applied, for example, to a group of files designating a beta or a
release version of a software product.
label (Global Services)
Text displayed to the user for a Global Services business object or attribute name; often a translated version of the name for display in the user's locale.
Launch Pad
Teamcenter application that provides a visual desktop to place items and notes, called nodes, for quick reference in either a carousel or grid display mode.
Lifecycle Viewer
Teamcenter application that provides multiple views to display and work with design data typically stored in CAD-data formats.
Lifecycle Visualization
Visualization components available in the rich client and as a stand-alone application. A scalable solution for the viewing and analysis of 2D and 3D product data, Lifecycle Visualization is
available in a number of configurations to meet the requirements of different organizations.
line of assembly
(Also called assembly component tree). Relation that represents one level of an assembly breakdown and contains attributes that are only pertinent to the corresponding level.
line of usage (LOU)
Business logic entity summarizing all configuration conditions that select a given part for a usage address in the product. The information referenced by a line of usage may include a part
identifier for the line of usage, a partition identifier, quantity, valid configuration and effectivity conditions, and business attributes. The LOU describes the incorporation of a part and its CAD
solution into the product for a given configuration and effectivity.
link
Manifestation of a business object relation in an end-user interface.
A link can represent a defined business object relation or a direct URL link.
link asset
Type of asset used to create links to Teamcenter objects. See also asset.
linked task
Task that represents a task from another schedule. Linked tasks demonstrate cross-schedule dependencies.
List of Values (LOV)
Pick list of values accessed by end users from a menu at the end of a data field. LOVs ensure consistent data entries in the rich client.
local server
Set of processes required to serve a single rich client installed on the same host computer as the rich client. Teamcenter Integration for NX/NX Integration configuration requires a local server.
log book
Collection of log entries recorded against a specific physical asset. A physical asset may have more than one associated log book.
log entry
Record of data collected about a physical asset and recorded by a certain person at a certain time. The log entry is associated to a single asset but may record characteristic values for several
components within that asset.
logical designator
Designator that distinguishes content in a partition. The user may assign logical designators to suitable content in a partition.
logical identity
Combination of the usage address and position designator of an absolute occurrence. See also position designator and usage address.
Log Manager
Common logging service framework that several components such as the Java middle tier and the Dispatcher use for logging the process and tasks.
lot
Group of physical parts controlled by the same number. A lot number is similar to a serial number. The difference between the two is that the same lot number can identify multiple physical
parts, but no more than the total number of physical parts specified by the lot size.
lot part
Physical part or assembly identified by a lot number.
LOU
See line of usage (LOU).
LOV
See List of Values (LOV).
LOV tree
Tree view of List of Values objects.
make/buy
Indicator that shows whether you manufacture a part or purchase it from a supplier.
managed occurrence
Central control authority for absolute occurrences of an item and its children in a context. A managed occurrence can only control data in a single context but may be revised and released.
managed site
Supplier site that uses Teamcenter to manage product data. A supplier site may be online (participates in a Data Exchange or Multi-Site environment) or offline (transfers data using briefcase
files). Compare with unmanaged site.
manifest file
File that records and maintains information about the rich client image files, including a list of the files and a version for each file.
ManufacturerPart
Business object type that is related to a CommercialPart object type by a Satisfies relation. A manufacturer part, which can be obtained from one or more vendors, has a part number
assigned by the actual builder of the part. The ManufacturerPart object is represented in the Teamcenter user interface by the term Vendor Part.
manufacturing bill of materials
Defines how the product is manufactured, rather than how it is designed. Compare with design bill of materials.
manufacturing feature
Teamcenter item. A collection of geometry and geometric references and attributes that provide the means for creating work instructions for a manufacturing process. There are several types of
features, including holes, pockets, weld points, and die faces. A manufacturing operation typically addresses several features of the same type. See also feature.
manufacturing process
Collection of manufacturing subprocesses, operations, and activities that make up a process plan. Processes can have both sequential and parallel ordering. They are associated with a
product and a work area.
Manufacturing Process Planner
Teamcenter manufacturing process management application that enables a user to design a plan detailing how to manufacture a product.
manufacturing view
Hierarchical structure of occurrence groups. The manufacturing view describes the components and subassemblies used by the assembly operations.
The components of subassemblies in the manufacturing view represent references to lines in the targeted product structure. These components can be consumed in operations if their parent
assembly is not consumed.
See also assembly view.
mapped attribute
Occurrence note mapped to an appearance attribute so that changes in the values can be tracked.
mapping file
ASCII file that contains the mapping schema. This file is edited to configure ERP Connect. The tc_erp_schema program is run with the mapping file to make the changes to the database (for
example, to create ERP forms defined in the mapping file).
mapping schema
Defines global settings (for example, send_file_path), erp_objects constructs to be transferred, and form types to store manufacturing attributes. The schema has a defined syntax and makes
use of keywords used to define the attribute values.
markup data
File objects containing annotations based on specific derived visualization data.
markup management
Part of document management concerned with creating and retaining annotations on presentation data.
master form
Teamcenter workspace object used to display product information (properties) in a predefined template. Master forms are used to display product information in a standardized format.
master FSC
FMS server cache that reads the master configuration file directly from the FMS master host. An FSC is configured either to read the master configuration file directly from the master host or to
download it from another FSC with access to it.
master object
Controlling object in a Multi-Site Collaboration network.
When an object is created and saved, that instance is the master object until it is exported with transfer of ownership. There can be only one master object in a Multi-Site Collaboration network,
and only the master object can be modified. If a master object is replicated, it cannot be deleted until all replicated objects are deleted.
master schedule
Schedule that contains one or more subschedules.
master schedule template
Schedule template that contains one or more subschedule templates.
material
Comprised of one or more substances, for example, carbon steel, cast iron, and so on. Each material to substance relation contains composition that can be definite or in range.
materials analyst
Role provided in Materials Management to perform various tasks, such as creating materials, exporting and importing materials, classifying materials, and so on.
Materials Management
Teamcenter application that stores approved materials and substance information imported from a third-party database (for example, Granta or IMDS) into a materials library in the Teamcenter
database. The materials and substances can also be created by a materials analyst using the My Teamcenter interface.
materials property
Represents chemical, physical, sensory, and nutritional properties of materials. The whole formulated materials development process is centered on the materials property concept.
material substance declaration
Form that lists the materials and substances contained in a supplier part. The material substance declaration (MSD) also specifies the threshold level for each substance and the environmental
regulations that establish the threshold levels.
MatML
Extensible markup language that is used for exchanging material information.
mature business objects
Business objects that have undergone an approval process and are approved for use in the product structure.
maturity state
Defines the degree of completion of the open change object. The states are elaborating, reviewing, executing, and complete.
MBOM
See manufacturing bill of materials.
Mechatronics
Integration of mechanical engineering with electronics and intelligent computer control in the design and manufacture of products and processes.
mediating application
PDM application (such as Global Services) that creates a trust relationship with a target application.
Mentor Graphics Integration
Teamcenter integration that allows users to store and manage Mentor Graphics Design Manager objects in Teamcenter.
message
In Global Services, a group of simple signals. A message is the payload data segment in a frame. The frame conforms to a standard protocol such as CAN_HS, CAN-LS, FlexRay or MOST.
message map
XML-configured mapping of message type to reactors (including notifier).
The Global Services message server uses this map to determine the reactors subscribed to a message.
message receiver
See Global Services message receiver.
message server
See Global Services message server and JMS message server.
message server log
Record of messages received by the Global Services message server and the status of attempts to send messages to subscribed reactors.
The Global Services message server uses this log to republish messages it was unable to send.
metadata
Object description in the Teamcenter database.
method
Description of how equipment is used to perform work on a feature. Each method can be used by several manufacturing operations to perform work on different features.
milestone
Task with zero duration.
model
Depending on the application, may represent an item or assembly, a set of functions in a system, a manufacturing process, a fixture, or an assembly line. See also product.
model geometry
3D positionable model content.
most recently used (MRU)
Shortcut list of the objects you have accessed most recently with the particular application.
MRU
See most recently used (MRU).
multifield key
Identifier assigned to an object to ensure uniqueness in the database. The multifield key is composed of a domain name (the name of the business object type) and a combination of object
properties. For example, the default multifield key for item business objects is Item{item_id}. See also domain.
Multi-Site (MS) Federation
Environment consisting of multiple Teamcenter sites known to each other, and sharing product data facilitated by IDSM and ODS.
Multi-Site Collaboration
Teamcenter capability that allows the exchange of data objects among several Teamcenter databases. Transfer of objects among databases is controlled by daemon processes running on
designated servers. Objects are replicated by exporting them from their original database and importing them into the requesting database. Configuration of Multi-Site Collaboration is optional.
Multi-Site Collaboration network
Network of independent Teamcenter sites that are within the same enterprise and share data using Multi-Site Collaboration.
multisource business object
Global Services business object containing at least one attribute that may exist in multiple data sources.
A multisource business object is defined with multiple data-source elements.
Contrast with aggregate business object.
Multi-Structure Manager
Teamcenter application that enables users to view and manipulate data in a specific context.
My Teamcenter
In the Teamcenter rich client, application that is the main access point for managing product information. My Teamcenter provides the functionality for creating objects in the Teamcenter
database, querying the database for objects, checking in and checking out objects, and managing tasks. Users can also open objects, automatically launching the related application.
Each user has a personal My Teamcenter window that displays product information as graphical objects. Although users share product information across the enterprise, they organize this
information individually in personal workspaces.
named ACL
Named group of access controls. See also access control list (ACL).
named reference
File types that are managed by a dataset. Datasets are the only workspace objects that use named references.
named variant condition template
Template for defining a load-if variant expression. Named variant condition templates are used to generate variant conditions for occurrences.
named variant expression
Defined variant condition specifying the option values required to configure the occurrence.
naming rule
Business rule that defines the naming conventions for the string property value in different type objects. Naming rules can be attached to the following properties:
• Item ID, item revision ID, and name in item types
• Dataset name, ID, and revision number in dataset types
• Name form types
naming service
Service that maintains a list of names and the objects associated with them. For the Teamcenter rich client, the naming service maintains a list of servers and the objects and methods used by
those services. The naming service is an integral part of the server directory.
navigation pane
Rich client framework component that displays buttons of the applications available for use in the rich client. Clicking the application button launches the application.
near network entity
Physical objects (users, volumes, servers, or clients) are near in the network when they are connected over a reliable network with latencies and bandwidth having typical LAN characteristics.
They are nearer if the latency is lower or the bandwidth is higher.
nesting schedules
Process of inserting an existing published schedule into another schedule.
network load balancer (NLB)
HTTP web servers are configured to allow each HTTP web server in the load balanced cluster to respond to a virtual IP address. Requests to this virtual IP are intercepted and routed to a
machine running one of the web servers in the cluster.
neutral data
See derived visualization data.
neutral part
Item defined in the neutral structure representing a part definition. It can be a part object or any other item type configured as a valid neutral item type in the Business Modeler IDE.
neutral structure
Hierarchy of neutral parts representing the asset-independent product definition structure, such as the manufacturing or design structure.
NLB
See network load balancer (NLB).
node
Point of interest in a harness. It may represent the beginning or end of a segment.
nonlibrary material
Material that is not maintained in the Teamcenter materials library. For these materials, the material mass and substance composition are not declared.
note
Assembly-related textual data associated with an occurrence. A note specifies a value associated with the assembly-component relationship, for example, the torque value for a bolt of 10 Ft Lb
in one assembly and 15 Ft Lb in another assembly.
note type
Type created by the system administrator that is associated with an occurrence in a product structure and enables users to specify a note.
notice
Informative message such as a note, caution, warning, or hazardous material that is specified for a work card or activity.
notification
Object that informs users of important events associated with selected objects. Compare with subscription (Schedule Manager, Service Scheduler).
notifier
Global Services component that allows a Global Services administrator to configure automatic email notification of Global Services messages to a list of subscribers.
The notifier can also log text to a file and contain Java code that executes a command when an event occurs.
A notifier is a specialized Global Services reactor.
notifier rule file
XML file that contains rules for the notifier reactor. Each rule in the file describes whether a Global Services message requires e-mail notification and who is to be notified.
Global Services administrators create the notifier rule file.
See also notifier and rule engine.
NS
See naming service.
NX
Siemens PLM Software's next-generation digital product development system that helps companies transform the product life cycle. It provides the complete life cycle of development
processes in product design, manufacturing, and simulation.
NX Advanced FEM
Open CAE environment that enables rapid creation and review of finite element simulations in a geometrically complex, multi-CAD, multiphysics environment.
NX Advanced Simulation
Solution set that combines the power of an integrated NX Nastran solver with NX Advanced FEM, a broad set of model creation and review tools. Extensive geometry idealization and
abstraction capabilities enable the rapid development of complex mathematical models that enable design decisions to be based on insight into real product performance.
NX Integration
Integration between Teamcenter and NX. NX Integration users have full access to the Teamcenter user interface from NX, and they can also access NX from the Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user interface in NX. The difference between the two products is the level of Teamcenter functionality available.
Teamcenter Integration for NX excludes certain Teamcenter functionality, such as workflow and product structure editing.
NX Nastran
Defines the world standard for advanced FEA solvers. NX Nastran is available stand-alone or seamlessly integrated at the core of many NX Digital Simulation products.
NX Remote Manager
Teamcenter component for managing the import and export of documents into Teamcenter. NX Remote Manager is a common component across integrations that include applications in fields
such as CAE and ME.
object-based protection
Use of access control lists to create exceptions to rules-based protection on an object-by-object basis. Object access control lists are most useful for either granting wider access or limiting
access to a specific object.
Object Directory Service (ODS)
Teamcenter Object Directory Services database. The ODS is either a Teamcenter site or part of a Teamcenter site that stores publication records for objects published to a Teamcenter
multisite deployment.
object directory services server
Multi-Site Collaboration network node that runs a daemon process to handle publication of data objects within a Multi-Site Collaboration environment. One ODS server node must be
designated for each object directory services site and each server node can act only for one object directory services site.
object directory services site
Site with the database that maintains a record of each object in a Multi-Site Collaboration network. At least one Teamcenter database on a Multi-Site Collaboration network must be designated
as an ODS site. This site is used to store publication records for the data objects.
object launcher
Launches another Teamcenter product from a linked object. Each Teamcenter product has an object launcher. See also remote workflow.
objects
Discrete logical groupings of metadata.
observer
Schedule role in which members have read-only access to a schedule.
occurrence
Hierarchical structure relationship between the immediate parent assembly and its child component item or item revision in a precise assembly. Sometimes called relative occurrence.
occurrence effectivity
Method of configuring the occurrences in a structure with effectivity. See also effectivity.
occurrence group
Collection of occurrences and absolute occurrences in the BOM. An occurrence group typically represents an assembly.
occurrence path
Representation of the path from a top-level assembly to an occurrence of a component or subassembly. An occurrence path is unique to the context of a specific BOM; different BOMs cannot
contain the same occurrence paths. The occurrence path does not change if the configuration of the BOM changes.
occurrence type
Object used to distinguish how items occur in a product structure. An occurrence consists of one component in an assembly including its relative position with respect to its parent assembly.
Occurrence types are representations of the PSOccurrence business object.
ODBC adapter
Adapter used with eIntegrator Admin to connect to ODBC-compliant applications. This adapter provides a link to ODBC-compliant applications from Teamcenter.
ODBC driver
Teamcenter integration that allows ODBC-compliant applications such as Actuate Report Writer, Crystal Reports, Microsoft Excel, and Access to extract data from a Teamcenter database for
building reports.
ODS
Object Directory Services (ODS) site that maintains a record of each object in the entire Multi-Site Collaboration network. The ODS does not store the objects, but rather maintains a record that
is similar to a library card; it identifies which site is currently storing an object and enough additional information to allow you to decide if you have found the correct object.
ODS server
See object directory services server.
ODS site
See object directory services site.
offline site
Site that does not have a network connection to other Teamcenter sites that is required for them to participate in a Data Exchange or Multi-Site environment. Offline sites must transfer product
data to other sites by exporting the data to a file system in a format supported by Teamcenter, such as TC XML (briefcase file) or PLM XML.
option
Attribute of an item revision with a set of allowed values (for example, engine: 1200, 1600). Options are used when specifying variant data to configure a variant of an assembly. Option names
are unique within an item revision, but not within the database.
Oracle home
Directory in which Oracle software is installed on the Oracle server node.
Oracle server
Single installation of Oracle able to service queries from several Teamcenter workstations. The ORACLE_SERVER environment variable defines this Oracle service node. For large-scale
installations, the Oracle server is typically a dedicated high performance workstation that is optimized specifically for running Oracle software.
Oracle system identifier (SID)
Alphanumeric word used to identify a collection of processes and associated memory structures as belonging to a particular Oracle database instance. The ORACLE_SID environment variable
defines the Teamcenter-Oracle system identifier.
order string
Set of options that defines the buildable configuration of the product.
organization
ERP system site that has a part inventory it wants to manufacture.
Organization
Teamcenter application that enables a system administrator to create and manage critical Teamcenter files and database entries. It is the point of access for creating a company's virtual
organization and for performing system administration activities such as volume creation, maintenance, and site administration. Organization enables creation and management of person, user,
role, and group definitions; definition of the hierarchical structure of the Teamcenter organization; management of data volumes; and establishment and maintenance of Teamcenter sites.
organization tree
Graphic display of the Teamcenter organization structure. Expanding and collapsing branches of the tree enables viewing and managing the organizational structure. Selecting a node starts
Organization wizards used to create groups, subgroups, roles, users, and persons.
orphan objects
Object in the Teamcenter database that cannot be navigated to given a principal object and the closure rules. See also principal object and closure rules.
output data
Siemens Documentation: Glossary Page 21 of 35
Data generated as a result of applying instructions to input data. Output data can be the resulting in-process model and any instructions for the next step.
override list
Item revisions in a workspace folder that is referenced from a revision rule. The item revisions in the folder override the revision that would otherwise be loaded by the revision rule.
override request
Changes a validation result from fail to pass or vice versa if allowed by a user in the override approver role. The override can be permanent until removed by the requestor or a temporary one
that is automatically removed when the test is run again.
Over-the-Web Installer
Installation program that downloads the rich client software from a distribution server instance to the user’s workstation over the web.
owner
User that owns an object, initially the user who created it. Ownership can be transferred from the owner to another user. An object owner usually has privileges that are not granted to other
users (for example, the privilege to delete the object).
ownership manager
Responsible for facilitating ownership transfer for objects and files that move between the systems.
owning group
Group that owns an object, usually the group of the user creating the object. Because users commonly share data with other members of a group, additional privileges may be granted to the
owning group (for example, the privilege to write to the object).
owning site
Multi-Site Collaboration site where the master object resides. The owning site is the only site where the object can be modified.
package concept
Two-dimensional sketch showing how the product works, for example, a sketch showing how liquid soap is dispensed from the bottle.
package item
Assembly of package structure, label, and artwork. A package item can represent packages of all levels: primary, secondary, and tertiary; or consumer and shipping.
package structure
Structure that holds the product, for example, a bottle assembly containing bottle and cap.
PAL
See process assignment list.
PAR
See publication audit record.
parameter
Qualifies an attribute defined in a mapping schema. Attribute parameters are used to define types, set and manipulate values, validate values, or set display names.
parsing script
Translates the raw measurement data from inspection devices to the standard loading format (Document Markup Language) so the data can be stored in Teamcenter for analysis and backup.
DPV provides standard scripts for translating data from the most common inspection devices. DPV administrators can also create custom parsing scripts.
part
Business object type that can participate in a structure as an assembly or component, with or without attached datasets. In Teamcenter, a business item managed in a company’s part releasing
system. Typically, the assembly or component is designed and built by the OEM.
part (Materials Management)
Comprised of one or more materials, for example, screw, bolt, and so on. Each part to material relation contains the mass of the material.
part application
Business logic entity containing attributes that are common to all the lines of usage (LOUs) for a given part within a subdivision, usage address, or vehicle partition.
part-centric program
Program that allows parts to be independent of the source document.
participant (Schedule Manager)
Schedule role in which members can modify only the schedule execution data, for example, Work Complete.
participant (workflow)
Different types of users involved in various phases of the change process, such as requestor, analyst, change specialist, change review board, and change implementation board.
partition (4th Generation Design)
Element in a product design that organizes and groups other elements as part of a hierarchical breakdown.
partition (Manufacturing Process Planner)
Subdivision of a structure. Typically used to group a subset of the structure occurrences in a context. Partitions may be used to arrange the structure organizationally, for example, by physical
areas of the product.
partition (site consolidation)
Segmentation of the source site’s consolidation information that, based on business considerations, is to be moved in a single instance or increment of the execution phase. See also execution
phase.
partition breakdown
Predefined hierarchical organization of partition members in the context of a product design. A product design typically has multiple partition breakdowns.
partition item
Item that maintains data about a partition. A partition item can be instanced into multiple breakdowns in multiple product designs. Customers may create types of partition items for particular
purposes, for example, Zone, System, Functional, or Manufacturing.
partition scheme
Taxonomy or hierarchical view that categorizes the contents of a product design. A product design may include several schemes. A scheme references a particular breakdown and maintains
common business rules and properties for the breakdown.
partition template
Represents a context-independent architecture for a specific class of product. Any partition architecture can serve as a partition template for any other partition architecture of the same type,
depending on business rules.
part logistics data
Information added to the neutral part that supports the realization of physical parts in as-built or as-maintained representations of the product. For example, part logistics data determines
whether the part is traceable, serialized, or lot. Part logistics data is added to each neutral part using the Part Logistics Form.
part master
Business logic entity containing data that applies to every instance of the part and part design, for example, weight or cost.
Part Planner
Teamcenter manufacturing process management application that enables a user to design a plan detailing how to manufacture a part.
passive mode
http://plmvti:8282/tdoc/tc/12/help 11-Mar-20
Management of application files from outside an application. Users do not have access to Teamcenter while running the application in passive mode. Data must be exported (pushed) from
Teamcenter to the application before it can be worked on and then imported (pulled) into Teamcenter after it has been modified. Compare with active mode.
PDM domain
Set of Teamcenter applications with a common administrator operating under the umbrella of a single Teamcenter Security Services deployment. PDM is an acronym for product data
management. Separate domains may be in different countries and may have different owners, with distinct and possibly disjointed user communities. For example, they may be geographically
or logically separated domains within one corporation, or they may be separately owned, such as by a customer and a supplier.
penetration request
Requests that a penetration be made to the structure of a ship (for example, for a routed system to pass through steel structures). You can create and manage penetration requests in both NX
and Teamcenter.
persistent object manager (POM)
Interface between Teamcenter objects and the Relational Database Management System (RDBMS). The persistent object manager provides definition of classes by inheritance from other
classes and definition of attributes, manipulation of in-memory objects and support for their saving and retrieval to and from the underlying RDBMS, support for applications accessing the same
data concurrently, protection against the deletion of data used by more than one application, and support for the access control lists attributed to objects.
persistent storage data
eIntegrator Admin method of data storage in which data is stored within the database; the retrieved data is always available from Teamcenter. This method of storing data provides quick
access to the data. Refresh operations retrieve the latest values from the external data source and overwrite the persistent data. After key data is imported as a persistent object, its properties
cannot be modified. Compare with dynamic storage data.
person
Definition 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.
perspective
Container in the rich client user interface for a set of views and editors collected to accomplish specified tasks. See also view.
phase
In Schedule Manager, a summary task that has one or more subtasks associated with it.
phase gate initiative
Special type of schedule.
physical part
Representation of a built or manufactured physical asset realized from the neutral part. The physical part captures asset information such as its serial number, manufacturer ID, and lot number.
It also inherits the part number from the neutral part from which it is realized.
physical realization
Relation between a physical part and the neutral part revision that it was realized from.
physical structure
Approved product structure that includes part information.
piece part
Part with no structure (no associated BOM view revision).
plan item
Schedule that defines tasks in a work breakdown structure.
plant
Manufacturing facility described by a hierarchical structure of work areas.
Plant Designer
Teamcenter manufacturing process management application that allows users to design, modify, import, and export a factory structure.
plant structure
Hierarchy of the physical layout of a work area. Different levels in the hierarchy represent the plant, a work cell, and individual workstations. Compare with product structure and process
structure.
Platform Designer
Teamcenter application that provides a mechanism to plan and control the evolution of product structures at your site by building generic structures of your products that contain a high degree
of variability. Platform Designer uses architecture breakdowns to create and disseminate design content and product variability.
PLM XML
Siemens PLM Software format for facilitating product life cycle interoperability using XML. PLM XML is open and based on standard W3C XML schemas. Representing a variety of product data
both explicitly and via references, PLM XML provides a lightweight, extensible, and flexible mechanism for transporting high-content product data over the Internet.
PLM XML/TC XML Export Import Administration
Teamcenter application that enables administrators to create PLM XML import and export rules used to configure the import and export of data in PLM XML format.
POM
See persistent object manager (POM).
populate
In Visualization Illustration, the action of creating a fully defined asset on a publishing page by specifying a Teamcenter object and a bound asset.
port
Occurrence of an interface port that represents the access point of a functional module in a given context, for example, a USB 2.0 port on a computer processor.
portfolio
In Visualization Illustration, an organized collection of publishing pages.
position designator
Value that represents the position of a single part from a line of usage. For example, if the line of usage references four wheels, there are four position designators—one for each wheel.
postprocessor
CAE tool used to evaluate and analyze solver results. It is typically used to generate results that provide conclusions based on the analysis results.
postprocessor translator
Converts the translated data from the main process to more formats useful for customers. For example, it generates JPEG from JT, which is generated from CAD data.
PR
• For Multi-Site Collaboration, see publication record.
• For Change Manager, see problem report.
precise assembly
Single-level assembly that has item revisions as the components. The item revision is configured by a precise entry in a revision rule. Compare with imprecise assembly.
predecessor task
Task linked to a later task in a task dependency relationship. See successor task.
preference
Configuration variable stored in a Teamcenter database and read when a Teamcenter session is initiated. Preferences allow administrators and users to configure many aspects of a session,
such as user logon names and the columns displayed by default in a properties table.
preference protection scope

Hierarchical range for which a Teamcenter preference can be set. The protection scope of a hierarchical preference can be site, group, role, or user.
preferred standard part
Standard part that is preferred for the program's assembly.
preparation phase
Site consolidation phase during which the involved Teamcenter sites are analyzed and prepared for consolidation.
preprocessor
CAE tool used to define a representative model to be analyzed and the specific conditions to perform a CAE analysis.
preprocessor translator
Runs before the main translation process. It prepares and sanitizes the data for the main translation process.
presentation data
See derived visualization data.
primary data segment
First data segment defined for an aggregate business object.
The primary data segment defines the master data source of information.
The data set returned from the primary data source constitutes the base for all business object instances.
primary document
File object that does not rely on other documents and can be opened in an application such as Teamcenter lifecycle visualization or Adobe Acrobat. Also called a base document.
A primary document can have secondary types of documents that depend on it, such as markups or snapshots, but the primary document itself is not dependent upon any other file. Primary
documents usually consist of one file, such as a PDF file or a logical set of files such as an assembly and parts.
primary queue
Queue that determines the processing order of primary update packages. The queue is stored persistently in the database and can be queried.
primary service request
Identifies service work to be done for a customer.
primary update package
Update package that exists on the primary queue and defines a set of changes that can apply to any number of appearance sets.
principal object
Initial object that can be used to start the traversal to determine an island of data. See also island of data. Contrast with dependent object.
privileged team member
Project team member with privileges to assign and remove objects from that project. Compare with project team member.
privileged user
First user to start working on a task when more than one resource is assigned to the task, as can occur in Schedule Manager and Service Scheduler.
privileged user (workflow)
Responsible party, process owner, or member of the system administration group. Privileged users have greater control over workflow tasks. For example, they can promote, demote, and skip
workflow tasks.
privileges
Type and degree of access to data. Privileges can be granted to groups, roles, users, teams, and projects.
problem
Concern that requires extensive change management and that may require product structure changes. Issues may be converted to problems. Contrast with issue. See also problem item.
problem item
Item revision that the impacted item revision is replacing, typically the latest released revision of the impacted item. The problem item is compared with the impacted item to generate the
changes (BOM change objects) when the edits to the impacted item are saved. This item is displayed in the Structure Manager right-hand pane to show removed components (highlighted in
red).
problem part
Physical part where a problem has been identified. A problem part may be removed during the execution of a requested activity, in response to a service request.
problem report
Change object that defines a problem or enhancement. One or more problem reports can be the basis for a change request.
procedure
Object that contains a stylesheet file used in attribute mappings and transformation policies to perform certain functions with content.
process
Automation of a business procedure, describing the individual tasks and task sequences required to complete a business procedure.
process assignment list
Distribution list associated with workflow process templates that assigns resources to all tasks in a workflow process. It can be used to assign resources to single-user tasks, such as Do tasks,
and to multiple-user tasks, such as perform-signoffs tasks.
process operation
Step in the manufacturing process executed at a specific work area. It is the lowest revisable element in the manufacturing process structure.
process owner
User who initiates the workflow process; also known as the process initiator. When the process is initiated, the process owner becomes the responsible party for the process. Whenever any
task in the process is not explicitly assigned to another user, person, or resource pool, the responsible party for the task defaults to the process owner.
process revision
Modified version of a process. A process revision can be used to handle different configurations of assemblies, alternative methods for building the target item, or changes to methods.
process structure
Hierarchy of manufacturing processes and operations with a sequenced relationship that together describe how a related product is manufactured. Compare with product structure.
process template
Blueprint of a workflow process defined by placing workflow and/or change management tasks (for example, do, perform signoff, route, and checklist) in the required order of performance.
Additional process requirements, such as quorums and duration times are defined in the template using workflow handlers.
product
Item or assembly (hierarchy of components and subassemblies) to be manufactured.
product appearance
Persistent representation of a product line. All appearances of a product are collected into a set that is associated with one revision rule. This allows one set of appearances that can be
configured by the effectivity of the part they represent.
product claim
Statement about the performance or uniqueness of the product to differentiate it in the marketplace. Claims are used in product advertisement and on packaging. Companies have to
substantiate the claims through product testing before they make the claim.
Product Communication Layer (PCL) server

Software that performs the first phase of data migration processing to convert I-deas data for use in Teamcenter Integration for NX. The PCL server exposes the I-deas project metadata to the
TDS server for interpretation.
product context
Set of item revisions of a given product item representing the same generic product structure.
product data
Product definition data stored and managed by Teamcenter site, related descriptive metadata, and associated volume data existing at a site (owned or replicated). These data are commonly
referred to as items in Teamcenter.
product design
Design model of a product, typically a large complex structure such as a ship or automobile. It comprises many design components, possibly more than 1 million.
product item
Top-level item associated with an assembly structure representing a generic product, for example, a midsize sports utility vehicle program for a given model year.
product lifecycle management (PLM)
Product lifecycle management (PLM) is an essential element in effectively creating and using global innovation networks to enable organizations and their partners to collaborate at every stage
of the product life cycle. PLM provides businesses with unified information at every stage of the product life cycle including planning, development, execution, and support.
Product pane
CAE Manager pane used to view and manage non-CAE item revisions. It enables generation of CAE model structures based on the input product structures using the data map and/or
structure map definitions.
product physical part
Asset at the level that it is managed by a service organization, whether the asset is a specific type of machine or a component of a particular machine.
product structure
Hierarchy of assembly parts and component parts with a geometric relationship between them, for example, a bill of materials (BOM). Variant and revision rules define the generic BOM. This
BOM can then be loaded to display the configured variant.
product view
Saved configuration of the assembly viewer, including the selection of objects, zoom factor, rotation angle, and pan displacements.
program
Basis for identifying a group of objects available to multiple organizations, such as program teams, development teams, suppliers, and customers for a particular piece of work.
Program administrator
Teamcenter user with privileges to administer programs using Program. A Program administrator creates, modifies, and deletes program information and team members.
Program application
Teamcenter application used to define programs and assign program team members, program team administrators, and privileged team members.
program team administrator
Program team member with privileges to modify program information and program team members for that program. Only one program team administrator is allowed per program.
program team member
Team member (user) who does not have privileges to assign objects to or remove objects from their programs. Compare with privileged team member.
program view
View that provides a read-only view of tasks across multiple schedules.
project
Basis for identifying a group of objects available to multiple organizations, such as project teams, development teams, suppliers, and customers for a particular piece of work.
Project
Teamcenter application used to define projects and assign project team members, project team administrators, and privileged team members.
Project administrator
Teamcenter super user with unrestricted access to administer projects they create using the Project application. A Project administrator creates, modifies, and deletes project information and
team members.
project team administrator
Project team member with privileges to modify project information and project team members for that project. Only one project team administrator is allowed per project.
project team member
Team member who does not have privileges to assign objects to or remove objects from their projects. Compare with privileged team member.
propagation
Process of transferring characteristics of one object to another object.
propagation start point
Component within an assembly structure that is the starting location for propagation.
properties
Keys and values that specify the configuration settings for an application in the Teamcenter rich client.
properties file
File containing the attributes (keys and values) that specify how an application is to behave in the Teamcenter rich client.
property constant
Configuration point within the data model that provides default values to business object properties. You can define a property constant to have a specific scope so that it is available only on
certain properties on certain business objects.
property format finder (PFF)
Feature that allows you to gather and report data related to the objects returned by a query. PFF objects provide the necessary links and relationships required to locate arbitrary data without
reformatting the query instance. PFF objects also enable you to acquire additional information that a single query would be incapable of rendering.
property rule
Business rule that allows an administrator to control access to and the behavior of object properties.
property set rules
Nonprogrammatic way to control what is placed in the user data element. See also user data element
proprietary material
Material that a supplier certifies as nonrestricted but wants the substance composition to be kept confidential for competitive reasons. The supplier does not provide the substance breakdown
of a proprietary material. A Teamcenter user cannot see the material composition. The supplier provides a certificate, such as a waiver, stating that the supplier will take complete responsibility
of the material composition.
pseudo application ID
Application ID presented to Security Services by a mediating application that encodes a level of authorization depending on the identities of the initiating Teamcenter user, each of the
participating PDM applications, and the nature of the access. A given pseudo application ID is associated with a particular target application, but it is not the real application ID for that
application.
pseudofolder
Special container in Teamcenter that stores and displays item and item revision relations in My Teamcenter. See also smart folder.
PSP
See propagation start point.
publication
In Base Content Management, an object that holds all the contents of an XML publication. A publication contains topics and subtopics, such as the cover page, back page, header, footer, and
sections or chapters.
publication audit record
PublicationAuditRecord object that is attached to the master object of a published object and that is used to determine when an object must be republished.
publication record
PublicationRecord object that is stored on the ODS site for each published object in a multisite environment. A publication record allows remote sites in the multisite environment to locate
remote objects.
publication type
In Base Content Management, the topmost object in the underlying XML structure that defines how authors can assemble publications. A publication type can have topic types, stylesheets,
XML attribute mappings, and transformation policies as related items.
published object
Object available to other sites in a Multi-Site Collaboration network. Publishing an object creates a record in the ODS site database that can be read and searched by other sites. Until an object
is published, it can be seen only by the owning site.
publishing
Makes an object available to other sites. When you publish an object, a publication record is created in the ODS that can be read and searched by other sites. Until you publish an object, it can
only be seen by the local owning site; other sites are not aware that it exists.
publishing tool
XML publishing application that is used to render content to PDF, HTML, or other formats and is launched when publishing a topic in Content Management.
QPL
See quick part locator.
QPL server
Quick part locator server. It provides a qpl daemon that can be used with Design Context in the rich client. The qpl daemon coexists with all Teamcenter daemons. Without this daemon Design
Context does not work.
Query Builder
Teamcenter application that enables a system administrator to create and maintain customized searches for objects in the Teamcenter databases, both local and remote. Saved queries are
subject to standard object protection and can be accessed by users through the search feature in My Teamcenter.
query form
Predefined query used in My Teamcenter to quickly search the database without building a custom query. Query forms limit search criteria to boxes displayed in the form. Accessing additional
search capabilities requires building a custom query.
quick part locator
Component of Repeatable Digital Validation (RDV) that creates and queries tables in a Teamcenter database. The quick part locator enables rapid lookup of components in an assembly. The
tables cache precomputed results of location, attributes, and spatial relationship of all components in a product assembly. The quick part locator provides one of the search engines used by
Design Context.
quorum
Number of users who must vote to approve a task for that task to be approved.
quote
Response to a bid.
R1 conflict
Conflict that must be resolved to avoid ambiguity and potential failure during the site consolidation process execution phase. Examples include intersite inconsistencies such as:
• Source and target site both claiming ownership of an object.
• Source and target sites both having export records for the same item.
• Objects at the source site with synchronous site transfer (SST) datasets.
R2 conflict
Conflict that must be resolved to avoid introducing a new ownership issue in a postconsolidation operation.
raw material
Initial in-process model before any manufacturing operations are performed.
RDV
See Repeatable Digital Validation.
RDV assembly
Product structure corresponding to a product item.
REACH
Registration, Evaluation, Authorisation and Restriction of Chemicals regulation protects human health and environment by identifying the intrinsic properties of chemical substances.
reactor
Global Services component that implements business logic and receives messages from the Global Services message server.
Customizers create a reactor for each data source system in the Teamcenter environment using Teamcenter toolkit Java APIs.
Reactors are Enterprise JavaBeans.
realization
Process of representing data from a source model into a target model.
recipe
Stored search criteria that query the contents of a product design or part of a product design, for example, partitions.
recipe spec
Type of specification that represents the process instructions to make the material.
reference designator
Identifier appended to part attributes in the product structure. It allows unique identification when the part is used several times in the same structure. Reference designators need only be
unique across a single level of the product structure.
reference geometry
Geometric features that are copied from one CAD design to another, with references back to the original geometry. Typically used to model surfaces, lines, and planes.
reference item
Teamcenter object that contains information related to the problem report, change request, or change notice. For example, it can be an analysis document or system log. Any Teamcenter
object, including a dataset, can be a reference item.
Registry Editor
Teamcenter application that enables editing Teamcenter rich client registry files. This application is used only for editing registry files that are used for internationalization, dynamic class
invocation, and configuration in the rich client framework.
registry file
Properties (.properties) file that contains the user-defined configuration settings (keys and values) that are relative to how the application displays and performs in the Teamcenter rich client.
Each application registered in the rich client has a .properties file known as a registry file.
regulation
Directive that restricts the usage of banned or hazardous substances. A regulation can be a legal restriction promulgated by a government authority, self-regulation by an industry, social
regulation, or market regulation, for example, Restriction of Hazardous Substance (RoHS); and Registration, Evaluation, Authorisation and Restriction of Chemicals (REACH). Each regulation
has a set of exemptions and rules associated with it.
relation
Description of an association between a Teamcenter object and a piece of information that describes or is related to the object.
Relation Browser
Teamcenter application that provides views used to perform basic tasks such browsing object relations, viewing 2D images, locating an object graphically in a map of relations, and examining
the properties of a selected object.
relative occurrence
See occurrence.
release status
Status associated with a workspace object when it is released through a workflow process.
remote action
Action that is performed from independent sites without actually logging on to the site. Remote actions are performed within the Teamcenter managed host/server sites.
remote method invocation (RMI)
Java-to-Java way to call methods of an object or class that is running on another platform. RMI comes with the Java Development Kit (JDK).
remote search
Search for published objects in the ODS. The remote search returns the publication record for the object searched.
remote workflow
Teamcenter component that enables users to create links between Teamcenter objects and objects in other Teamcenter products, such as Teamcenter portfolio, program and project
management. Users can then launch the linked Teamcenter product from within the rich client.
render
Process that invokes the data translations specified for an item, such as a document revision, to generate derived visualization data. Translate is an action on a dataset. Render is an action
taken on an object, such as a document. See also translate.
Repeatable Digital Validation
Combination of software and processes that enables on-demand digital mockups for use throughout the product development lifecycle. Repeatable Digital Validation services are required for
using QPL-based Design Context.
replica
Replication is the act of creating an exact copy of an object, known as a replica, at a specific site. Replicas are objects that are not owned by Teamcenter.
replica data
Objects existing at a site that are identified as owned by another site.
replicated object
Copy of master object residing at sites within a Multi-Site Collaboration network. See also master object.
Report Builder
Teamcenter application used by administrators to build summary, item, and custom reports.
reported discrepancy
Identifies work that is the result of part discrepancy and records any irregularities that a service request is intended to correct.
Report Generator
Teamcenter manufacturing process management application that provides a format for producing reports about information in Teamcenter manufacturing process management.
requested activity
Defines the scope of work for a service request.
requestor
User who creates a change object or is delegated a change object by another requestor. The requestor is responsible for elaborating the definition of a change.
resource
Item used to perform an operation or define a process. Examples of resources include robots, tools, and machines. Both standard equipment and custom tools can be identified as resources.
resource assembly
Set of resource components and/or subassemblies that are grouped to create an assembly to be used in a process, such as a manufacturing process.
Resource Browser
Plug-in component that allows users to retrieve classification-related data, such as a hierarchy with corresponding groups, classes, and classification objects from a Teamcenter database when
working in an external application.
resource component
Object that is a component of a resource assembly or subassembly.
Resource Manager
Teamcenter manufacturing process management application that enables a user to store and retrieve resource-related data such as tools, fixtures, machines, and process templates from a
company-wide accessible database.
resource structure
Structure in which resource assemblies are hierarchically built.
resource tier
Teamcenter architectural tier comprising the database server, database, file servers, and volumes.
response chain
Logical way to group action components and action chains into a flow within application maps. Response chains represent a go to routine, typically directing the action to a page or an ID
representing another destination, such as a response chain or action chain. A response chain contains one or more action components. The controller iterates through the response chain
handing control to action components. If there are multiple action components, they can in turn be placed within action chains, subroutines used to further group action components into a flow
within application maps. See also action chain, action component, and application map.
reuse rule
Structure map rule that provides a mechanism to reuse item revisions that is already associated with an input item to be used in an output structure if they meet specific criteria.
reviewer document
Object containing the assembled content of a publication or topic after it is published. Similar to a composed document, a reviewer document is named differently to distinguish it as a document
that has not been processed through a review workflow.
review task
Task template that includes the select-signoff-team and perform-signoffs subtasks. Each subtask contains a unique dialog box for executing the process.
revision filter
Filter used to configure the display of items and item revisions based on established revision rules.
revision naming rule
Business rule that defines the naming convention and sequence for a revision property.
revision rule
Parameter set by the user that determines which revision of an item is used to configure product context.
rich client
Java-based user interface to Teamcenter installed on user workstations. The rich client accesses Teamcenter databases using a remote or local server.
rich client distribution server
Software that manages the connection between distribution server instances, the web server, and the user’s workstation when a rich client is deployed over the web. The Over-the-Web
Installer contacts the distribution server for the rich client files to download to the user's workstation.
rich client distribution server instance
Rich client software to be installed on user’s workstations over the web. Administrators create one instance for each server.
rich client framework
Component of the rich client that integrates and runs various applications from a common platform. These applications can be off-the-shelf applications such as NX CAD/CAM/CAE, Microsoft
Office, custom applications, and Java plug-ins.
RIG approver
User who is a signoff in a workflow process with a specified role and group. In Access Manager, the RIG approver accessor is used in Workflow ACLs and matches the signoff definition (that is,
role in group) for the release level associated with the Workflow ACL. This accessor ensures that only signoffs are given privileges, not a user who matches the role in group. See also
approver, group approver, and role approver.
RMI
See remote method invocation (RMI).
RoHS
Restriction of Hazardous Substance regulation restricts the use of hazardous substances in electrical and electronic appliances.
role
Function-oriented cluster of users that models skills and/or responsibilities. The same roles are typically found in many groups. In Access Manager, role is an accessor used to grant privileges
to all users with the same skills and/or responsibilities regardless of project.
role approver
User who is a signoff in a workflow process with a specific role. In Access Manager, the role approver accessor is used in Workflow ACLs and matches the sign-off definition (that is, role in
group) for the release level associated with the Workflow ACL. This accessor ensures that only signoffs are given privileges, not a user who matches the role. See also approver, group
approver, and RIG approver.
role in group
Specific role in a specific group. In Access Manager, role in group is an accessor used to grant privileges to all users with the same skills and/or responsibilities in the same group.
role in owning group
Specific role in the object's owning group. In Access Manager, role in owning group is an accessor used to grant privileges to users with the same skills and/or responsibilities on the same
project. For example, all designers in the owning group are usually granted write privilege on their development data.
role preference
Teamcenter preference applying to an entire role.
root
Starting point of a hierarchy. Hierarchies are usually displayed as hanging trees with the root of the structure at the top and the leaves at the bottom.
root item
Top-level item of the product. Typically this is also the end item for unit effectivity.
rotable part
Repairable component or inventory item that can be repeatedly restored to a fully operational condition and reused over the normal life cycle of the parent equipment to which it is related.
route
Course taken by wire or connection from a starting point to a destination.
rule
In Substance Compliance, rules describe how substances, materials, and substance compliance status are rolled up across BOMs. Rules check the amount of a substance, compare it to a
specified threshold value, and set a specific compliance status on the object.
rule engine
Global Services component that maintains a set of rules for the notifier.
Global Services customizers create the rule engine using a Global Services Java interface.
See also notifier and notifier rule file.
rule handler
Handler used to integrate workflow business rules into Enterprise Process Modeling processes at the task level. Rule handlers attach conditions to an action. See also task handler.
rules-based protection
Conditions or rules that control who can or cannot access objects. These rules are global (that is, they affect the entire Teamcenter site) and are enforced by the Access Manager. These rules
are defined by a system administrator.
rule tree
Access Manager component the system administrator uses to grant users access to Teamcenter objects. It is a tree of rules and access permissions that when processed determines the
access that each user has to a specified object.
S1000D
Standard for technical publications that are developed with XML or SGML. S1000D Content Management, an optional Teamcenter solution, enables management of documentation for the
S1000D standard.
schedule baseline
Snapshot of a schedule at a given time.
schedule calendar
Calendar to define days off, holidays, and working times in a day for the current schedule.
Schedule Manager
Teamcenter application that provides the ability to define and manage schedules for projects.
scheduler
Regulates translation tasks to the translation modules.
schedule summary task
Top-level task that contains the planning and execution summary of the entire schedule. It is not shown separately in Schedule Manager.
schedule user calendar
Calendar to define days off, holidays, and working times in a day for a user in that schedule.
schema
Object that defines the basic structure of elements and attributes used in a topic. Types of schemas include: DTD, character entity map, example content, SGML catalog file, SGML declaration
file, and SGML DTD.
secondary data segment
Second and following data segments defined for an aggregate business object.
Secondary data segments are queried in the order in which they are defined.
secondary document
File object that is meaningful only in the context of another document. Also called a derived document. For example, markup data and snapshot files can be viewed only in the context of a
primary document, such as a JT file.
secondary queue
Queue that contains the list of secondary update packages to be processed. The queue is stored persistently in the database and can be queried.
secondary update package
Update package that exists on the secondary queue and defines a set of changes that apply to one appearance set.
second class attribute
Set of related attributes stored as BLOB data in a single attribute. For example, UserAttributes is a second class attribute attached to product structure classes.
Second class attributes cannot be individually queried and are accessible only through specific display and edit routines, such as the Properties Update dialog box in the I-deas Navigator.
Compare with first class attribute.
Security Services
Services that eliminate prompts for logon credentials when users switch Teamcenter products within a user session. Authentication is performed by an external identity service provider, such
as lightweight directory access protocol (LDAP), instead of the Teamcenter product. At a site that deploys multiple Teamcenter products and Security Services, users log on once to access all
participating Teamcenter products.
Security Services application token
Token that is consumed by Teamcenter applications in the process of joining an SSO session. This token has a configurable lifetime.
Security Services session
Includes all application-level sessions of Teamcenter applications involved during a single user work session.
Security Services token
Type of credential that represents an authenticated user. There are three token types: SSOAppToken, HttpCookieToken, and HttpHeaderToken.
segment
Section of a connection where no intermediate electrical contacts appear.
serialized part
Physical part or assembly identified by a serial number.
serial number generator
Number generator that can be configured on a neutral part to create serial numbers for every instance of a physical part. You can set characteristics for the serial numbers, such as a prefix, a
suffix, the number increment, and the maximum number of characters in the serial number. During the instantiation of the physical structure from the neutral structure, you can choose to
automatically assign the serial numbers to the newly created physical parts.
server
System software component that performs a specifically defined set of software services on behalf of one or more clients. In a typical Teamcenter installation, servers are centralized on
dedicated hosts that support a large number of clients. Clients are distributed on hosts connected to the servers via various networking techniques. See also client.
server exits
Exit points from standard Teamcenter functionality to Java. These exit points are also known as user services. Use them when you want to call your functions from Java in the Teamcenter rich
client.
server manager
Process that manages a pool of Teamcenter server processes in a deployment of the four-tier architecture. The server manager starts and times out a configurable number of server processes
to communicate with the Teamcenter database. A server assigner process assigns available server processes to user sessions. The server manager communicates with the web tier
application using either TCP or multicast protocol.
server pool
Pool of Teamcenter server processes running in the enterprise tier. A small deployment may have only one pool of server processes. For larger deployments, the pool of server processes is
distributed as subpools across multiple hosts, with a server manager for each subpool. Server pools are applicable for deployments of the Teamcenter four-tier architecture only.
service catalog
Collection of standard services, called service offerings, that are performed by a service organization on a product physical part that is realized from the neutral part. The service catalog is
assigned to a neutral part.
service discrepancy
An irregularity or observation discovered with regard to maintenance of a physical part. Discrepancies can also identify if there was a failure with the physical part.
service event
Informational data that is captured as a result of service activity that is performed by an external source.
service group
Collection of service events and service discrepancies used to organize the service records of one or more physical parts.
Service Manager
Teamcenter application that supports as-maintained structure management and service event management capabilities.
service offering
Standard service offered by a service provider.
service partition
Hierarchical grouping of service requirements. A service plan always has a root service partition. A service partition can have sub-service partitions.
service plan
High-level container that holds the service requirements for a product. It is associated to a neutral structure.
Service Planner
Teamcenter application used to create and manage service plans, service requirements, work cards, activities, and other information to support the service planning process.
Service Request Manager
Teamcenter application that lets service providers manage customer requests for service from initiation through completion.
service requirement
Requirement for scheduled or on-condition maintenance. Scheduled service requirements have an associated frequency that defines when the maintenance should be performed. You can
define dependencies between service requirements.
Session Agent
Standalone, separately installed Java application on Teamcenter client machines used to facilitate single sign-on between rich clients. It is also used by rich clients when Teamcenter is
deployed behind an authenticating gateway.
setup
In a manufacturing environment, configuration of the work area. The setup also identifies the parts consumed and the resources used.
Setup Wizard
Teamcenter application that facilitates postinstallation setup of a Teamcenter database using an input file to populate the information required to create the basic components of the
Teamcenter organization. Using Setup Wizard, a system administrator can create user/person definitions, assign a group/role to a user, and optionally define a default volume for assigned
groups.
signal
Physical representation of a message or an information flow being generated, processed, or conveyed within an electrotechnical system.
simulation
Process to predict aspects of the behavior of a system by creating an approximate (mathematical) model of it.
single sign-on
Mechanism that allows a user to log on once to multiple services. Following a single sign-on to Teamcenter, the user is connected to multiple services without logging on to each service.
single-source business object
Global Services business object that exists in one data source with all data contained in one addressable element. A single-source business object is defined with one data segment.
site
Individual installation of Teamcenter comprising a single Teamcenter database, all users accessing that database, and additional resources such as hardware, networking capabilities, and
third-party software applications (tools) required to implement Teamcenter at that site.
site consolidation
Task of moving all the required information from the source site to the target site and performing cleanup and source site retirement. Site consolidation has three major phases—preparation,
execution, and cleanup and retirement.
site definition data
Information (site administrative, system, organization, and schema data) used to organize and control the site managed data.
site ID
Unique identifier of a Teamcenter site. The site ID is used to generate internal identifiers for Teamcenter objects that must be unique throughout an enterprise. Once established, site IDs
should not be modified.
site managed data (product data)
Customer product definition data, related descriptive metadata, and associated volume data existing at a site (owned or replica). Site managed data are commonly referred to as items in
Teamcenter.
site name
Unique name of a Teamcenter site stored in the database as a user-defined character string.
site preference
Teamcenter preference that applies to the entire site.
skill
Qualification that a person might have for performing or signing off on a service requirement, a work card, or an activity. A skill must have an associated discipline object.
slot
Mechanism that groups the cavity objects of a connector housing.
smart folder
Pseudofolders configured in a hierarchical structure used to apply hierarchical levels of filtering to project data. See also pseudofolder .
SML class
Legacy class type used in the Classification application. Do not use this type of class to create data. Use abstract and storage classes instead.
snapshot
Folder that contains all the revisions of a configured product structure. A snapshot can be used to redisplay the as-saved structure.
Solid Edge Manager
Teamcenter integration that enables users to use Teamcenter to manage files from within Solid Edge.
solution item
New item revision released with the change that has a release status attached. The item revision may be a new component part which replaces the old component in the parent impacted item.
It may also be a new assembly that is being released.
solution part
Physical part introduced to a physical product as a solution to a service request. A solution part includes any new parts that are created as a result of a requested activity.
solver
CAE tool used to execute the defined CAE analysis and provide the results information.
source data
In document management and visualization, the original data format from which derived visualization data is produced, for example, a CAD assembly and part files, Word documents, and
spreadsheet files.
source Teamcenter site
Teamcenter installation containing data and users that are being consolidated to another Teamcenter location or Teamcenter installation. Both source and target must be at the same version.
Compare to target Teamcenter site.
spare part
Small item that in Resource Manager is commonly entered as other components are. Examples include nuts, bolts, washers, and screws.
spatial data
Either NX true shape files or PLM visualization JT files that define the volume of the part as a set of cubes. The cube size is set in the CAD programs defaults file. The CAD files do not set
absolute position; this is defined when the files are associated with an appearance.
spec element
Spec section is composed of one or more spec elements. A spec element can be a property, text, an image, or other commonly used data types.
specification
In Consumer Packaged Goods and Food and Beverage industry, specifications capture the complete definition of products and how to manufacture them. Raw material spec, formula spec,
intermediate and final product specifications, package spec, recipe spec, testing spec, and nutritional spec are some of the types of specifications.
Specification Manager
Teamcenter application used to view and work with specifications that capture the complete definition of products and how to manufacture them.
spec section
Specifications are composed of one or more spec sections. A spec section can be reused across specifications.
SQL
See Structured Query Language.
standard part
Part that may be used across multiple programs and whose design is controlled by a standard specification. The standard specification can be provided by a company, an industry, or the
military.
standard track change
Fine-grained change process with the ability to support the process for problem reports, change requests, change notices, implementation plans, and tasks. The process also manages the
entire cycle of review, approval, and implementation of a change.
state vector
Combination of a change object’s maturity state, disposition (level of approval), and closure status.
status (change management)
Implementation status of a change object. It can be started, in progress, completed, or deferred.
status (workflow)
State applied to an object after it goes through a workflow. Typical statuses are Pending and Approved.
STEP AP212
Standard for the Exchange of Product Model Data (STEP) for the Industrial Automation Systems and Integration – Product Data Representation and Exchange international standard (ISO
10303). This standard provides a framework through which industries can exchange and share product information within and between enterprises. AP212 is an application of this standard and
describes the information necessary to customize electrotechnical products.
STEP Translator
Teamcenter application that enables users to import product information into a Teamcenter database and to export Teamcenter data via STEP-compliant physical files.
storage class
Classification class capable of storing classification instances. Compare to abstract class.
storage media
Storage device category such as a hard disk or optical device. It is a data model object type used by third-party content-storage systems.
storage unit
In Classification, the measurement unit in which a classification object (ICO) is saved.
structure
Representation of multiple objects and their interdependencies. For example, a classification structure represents classes and their inheritance dependencies, and an assembly structure
represents how components and subassemblies are associated to build up an assembly. The structure can be viewed in several applications, including Structure Manager, Manufacturing
Process Planner, Part Planner, Multi-Structure Manager, and Resource Manager.
In Resource Manager, most structures are hierarchical. For example, they acquire the form of a tree where each node can have only one parent but multiple siblings and children.
structure context
BOM or assembly structure contained in a collaboration context. The structure context can contain occurrence groups, items, and item revisions. See also collaboration context.
Structured Query Language
ANSI standard command and embedded language for manipulating data in a relational database.
Structure Manager
Teamcenter application that enables creation of generic product structures that can be configured to show the product structure that is in production, effective on a certain date, used by a
particular customer, and so forth. Structure Manager enables creation and modification of a product structure and its associated occurrence data, display of a product structure in a multilevel
indented format, and viewing graphics tightly coupled to the structure for easy identification of a component by location in the structure or in the embedded viewer.
structure map
Workspace object that defines a StructureMap item used for managing structure map rules. The dataset attached with the StructureMap item revision contains the structure map rules. The
structure map rules translate an input product structure to a CAE model structure.
structure map rule
Rule used to manipulate the output structure when translating an input BOM view to an output BOM view using the underlying data map rules.
stub
Proxy object that is used to represent an object that is excluded while exporting a larger object such as an item or an assembly.
study
Collection of elements instantiated from one or more collaborative designs and other design items to support a particular activity, for example, a review.
stylesheet
Object that contains formatting information used to render, edit, or transform a topic or document.
style type
Object used to organize and manage the style sheets associated with publications. The style type helps manage which style sheets appear in preview or publish functions.
subassembly
Assembly that is built into the assembly structure of another assembly or intended for that use. In a manufacturing view, either a delivery unit or a workpiece. See also delivery unit and
workpiece.
subclass
In the Classification Search Dialog, subclass instances represent a subset of attributes corresponding to a class. Subclasses inherit the attributes of their parent classes. Unlike classes, which
inherit every attribute of their parent classes and cannot be edited, users can define the inherited attributes assigned to a subclass.
subschedule
Schedule that is contained in another schedule. The contained schedule can be a part of many other schedules.
subschedule template
Schedule template that is contained in another schedule template. The contained schedule template can be a part of many other schedules.
subscription
Combination of a workspace object and an event for which a Teamcenter user requests notification of occurrence. Teamcenter notifies a subscribed user when the event occurs in association
with the object. Users can subscribe to objects from Teamcenter applications, such as My Teamcenter and Structure Manager.
subscription (Schedule Manager, Service Scheduler)
Object that informs only the creator of the subscription when a specific task-related event occurs. Compare with notification.
Subscription Administration
Teamcenter application that enables a system administrator to query subscriptions created in the database, to monitor and delete subscription events and actions, and to generate statistical
reports in either text or bar chart format regarding subscriptions, events, and actions.
Subscription Manager
Tool used to find, delete, and modify active subscriptions.
subset
Collection of elements or a recipe for collecting elements from a single collaborative design.
substance
Basic form of matter that cannot be disintegrated further using a mechanical or physical process, for example, iron, carbon, cadmium, and so on. Each substance has a unique identifier called
the Chemical Abstracts Service (CAS) number.
Substance Compliance
Teamcenter environmental compliance solution that enables companies to conform to environmental laws, regulations, standards, and other requirements for their own parts and for the parts
manufactured or supplied from an external source.
substance compliance result object
Object that the substance compliance checker returns to Teamcenter after a substance compliance check.
substance compliance status
During a substance compliance check, the substance compliance checker returns the substance compliance object that contains the substance compliance status. The substance compliance
status is returned for all items on which rules are run (for example, vendor part, commercial parts, and all items in the BOM).
substitute
Component that can be used interchangeably within an occurrence, typically for manufacturing purposes. The preferred substitute is displayed in the structure.
subusage
Partial configuration associated with a line of usage that can be satisfied by a single CAD item. For example, there may be two subusages for a particular truck, one for the long wheelbase
model and one for the short wheelbase model; each has a differently positioned CAD item. The subusage is a container for the CAD solution and its position designators for a particular
configuration. Sometimes called a usage primitive. See also line of usage (LOU).
successor task
Task linked to a previous task in a task dependency relationship. See predecessor task.
summary table
Displays the reports, charts, and other documents available in the report server for a measurement routine, cluster, or cluster group. Summary tables are in the DPV Viewer Web Part.
summary task
Task that has one or more subtasks associated with it.
supersedure
Manually created relation that graphically displays deleted components and the components that replace them. A supersedure is always created in the context of a parent assembly. Therefore,
a single component can be used in more than one supersedure if it is used in different parent assemblies. A supersedure can be created for changes of part number or of quantity, but not for
changes in a part revision.
supersedure report
Report containing the progression of supersedures from the original part to the latest part within a specific product or across different products. It also contains the incorporation history of a
specific part on a specific product or across different products.
supported platform
Platform configuration supported by GTAC.
synchronization
Process of updating replicas. When a master object is replicated at other sites, you must update the replicas whenever the master object is modified. See also replica.
Synchronous Site Transfer (SST)
Transfer protocol used to mitigate ownership problems, such as no owner or dual-site ownership, that could occur when an object’s ownership is transferred between Teamcenter sites.
system administrator
Teamcenter user who is a member of the system administration group.
Systems Engineering
Teamcenter application used to identify, allocate, and maintain product requirements.
target application
PDM application (for example, a Teamcenter Security Services-enabled application) accessed indirectly via a mediating application. The access is via an alias user ID that confers some level
of rights amplification or restriction to the underlying real user.
target relationship
Relationship between a target application and a mediating application. The mediating application presents an alias user ID to the target, and the target trusts that the mediating application has
authenticated and authorized the underlying user represented by the alias user ID.
target Teamcenter site
Teamcenter installation that will host the data and users of the source Teamcenter site after site consolidation. Compare to source Teamcenter site.
task (workflow)
Fundamental building block used to construct a process. Each task defines a set of actions, rules, and resources used to accomplish that task.
task dependency
Link between two tasks creating an order of completion.
task handler
Small Integration Toolkit program or function. Handlers are the lowest level building blocks in Enterprise Process Modeling. They are used to extend and customize tasks. There are two kinds
of handlers: action handlers and rule handlers. See also action handler and rule handler.
task ID
Number automatically assigned to a task in the task table.
task table
Table that displays all tasks, milestones, and their properties.
task template
Blueprint of a workflow task.
TC XML
XML format used to import and export Teamcenter data into and out of a Teamcenter site. For example, this format is required for Data Exchange transfers and allows mapping of objects
between two sites that have different data models.
Team Browser
Client application that provides a graphical interface to I-deas Enterprise, the product that integrates Teamcenter and I-deas Enterprise. The Team Browser enables users to view and manage
the data in their personal workspaces and teams and to interact with vaults. See also Teamcenter Integration for NX I-deas.
Teamcenter adapter
Adapter used with eIntegrator Admin to connect to ODBC-based systems using a common interface.
Teamcenter Application Registry
Independent web-based service that allows a Teamcenter product to look up other available Teamcenter products for launching a linked object. Administrators can register and unregister
installed instances of a Teamcenter product in the registry.
Teamcenter application root directory
Directory location of the Teamcenter shared binary executables. The TC_ROOT environment variable defines this location. Generally, the contents of this directory change only with a new
version of Teamcenter.
Teamcenter data directory
Directory location of the Teamcenter shared data subdirectories and files. The TC_DATA environment variable defines this location. Each data directory is associated with a single database
instance.
Teamcenter Environment Manager (TEM)
Tool with a wizard-style interface that installs Teamcenter servers and two-tier and four-tier rich clients. TEM also performs maintenance operations, such as upgrading servers, applying
maintenance packs, and installing patches. Teamcenter installers launch TEM using the tem.bat command (on Windows systems) or the tem.sh command (on UNIX or Linux systems).
Teamcenter file structure
File structure of an installed Teamcenter node; it separates homogeneously shared binary executables from heterogeneously shared data.
Teamcenter Integration for AutoCAD
Teamcenter integration that provides transparent management of AutoCAD part files and assemblies, including the synchronization of metadata (product structure and attributes), multiple
import and export capability, and the ability to use seed files when creating Teamcenter datasets.
Teamcenter Integration for NX
NX-based entry-level set of Teamcenter data management functions, such as vaulting, checking in, checking out, revision management, attribute synchronization, and searching CAD data.
Teamcenter Integration for NX manages NX files and their data without exposing the user to full Teamcenter functionality. Teamcenter Integration for NX users have only limited access to the
Teamcenter user interface.
Teamcenter Integration for NX and NX Integration have the identical user interface in NX. The difference between the two products is the level of Teamcenter functionality available.
Teamcenter Integration for NX excludes certain Teamcenter functionality, such as workflow and product structure editing.
Teamcenter Integration for NX I-deas
Product that integrates Teamcenter and I-deas to provide a single data management environment for users. Teamcenter Integration for NX I-deas users author their data in I-deas and manage
the data in Teamcenter. Teamcenter Integration for NX I-deas includes the My Teamcenter user interface and the I-deas Data Services (IDS) and Team Data Sharing (TDS) modules. See also
I-deas.
Teamcenter Integration for NX I-deas host
Teamcenter host that functions as the gateway through which the Migration Wizard initiates communications with the TDS server for data migration processing.
Teamcenter location
Physical location that hosts a database and possibly other server-side components for one or more Teamcenter sites.
Teamcenter manufacturing process management
Teamcenter manufacturing process design and management system. Teamcenter manufacturing process management comprises several user applications, for example, Manufacturing
Process Planner, Part Planner, Report Generator, and Resource Manager.
Teamcenter option
See preference and user preference.
Teamcenter Services
Set of services that allow customers to connect their applications to Teamcenter. Teamcenter Services use service-oriented architecture (SOA).
Teamcenter site
Teamcenter deployment that has its own server-side components, such as a database, volumes, and a corporate server.
Teamcenter visual issue
Captures and tracks design problems with 2D images and 3D models. You can create and view visual issues in the stand-alone viewer or the Lifecycle Viewer. You manage visual issues in
Issue Manager.
team folder
Logical storage area for team data.
technical brief
Captures dimensions, material properties, packaging structure technologies (existing, new, and emerging), printing technologies, primary, secondary, and tertiary requirements, and packaging
display requirements.
technical document
Written form of technical information, such as reports, drawings, parts, lists, and so on.
tech spec
Represents the bar code, finished product code, and color numbers.
TEM
See Teamcenter Environment Manager (TEM).
tessellation
Process that translates a CAD file to a visualization file.
time-critical period
Period of time during which user activity is restricted in the source and target site database. See also execution phase.
tool
Object that represents a software application, such as Microsoft Word or Adobe Acrobat. You associate a tool with a type of dataset so you can launch the dataset file from Teamcenter.
topic
In Base Content Management, an object that may be part of one or more publications. A topic can contain text, tables, graphics and subtopics. The term topic is also used in Content
Management to refer to certain S1000D and DITA objects.
topic type
In Base Content Management, a component of a publication type in the underlying XML structure that defines how authors can assemble publications. A topic type can have topic types,
stylesheets, XML attribute mappings, and transformation policies as related items. In S1000D and DITA Content Management, topic types are predefined to match the objects for those
standards.
top level
Object at the root of a product structure where a process plan is being developed. The top level can be either an end product being manufactured or a subassembly used in the end product (for
example, an engine for a tractor where the tractor is the end product).
trace link
Directional relationship between two objects; the relationship is conveyed by the terms defining and complying. See defining object and complying object.
trade item
Represents a product or service that has a unique Global Trade Item Number (GTIN). GTIN is used to retrieve information about the product or service.
transaction log
Tracks solution transactions from Teamcenter to . The transaction log provides information on each transaction including messages from . The information in this log is used to monitor the
success of solution transactions and to gain insight into reasons for transaction failure.
transfer folder
Temporary folder created during workflow into which references to all the ERP forms and any BOM view revisions are pasted. The contents of this folder are transferred to ERP where you can
remove objects you do not want to send.
transfer mode
Objects composed of rules that configure PLM XML import and export operations. Transfer mode allows users to import and export data with little knowledge other than the name of the transfer
mode object.
transfer option set
Stored set of transfer options for remote export or import of data.
transformation policy
Object used to make arbitrary modifications to XML or SGML contents during the fetching or storing of content. A transformation policy includes a user action, an optional tool name, and either
a style sheet or a procedure that is applied to the content when the action is used.
transient volume
Operating system directory controlled by Teamcenter and used to store temporary data for transport of reports, PLM XML, and other nonvolume data between the web tier and client tier in a
deployment of the Teamcenter four-tier architecture.
translate
Process that converts data from one file format into another file format. In the context of Teamcenter document management, source data is converted to derived visualization data formats. The
conversion is based on available translators. Translate is an action on a dataset. Render is an action taken on an object, such as a document. See render.
translation control object
Configuration control object in Document Manager that defines the rendering processes for various types of file input and specifies the order in which the processes should be applied.
translation module
Launches the translators that perform the translation. Each module resides on one hardware node on the network and is connected to the translation scheduler.
translation order
Object stored in Content Management that contains information for the process of translating content, including the translation office assigned and the requested delivery date.
translation server
Web-accessible, scalable, and configurable software that performs translation from and to various file formats.
translator wrapper
Java wrappers that enclose the translator API. The wrapper provides threading, process control (start, stop), status checking, error handling, and completion status and/or messaging.
transmodule properties file
Property file that allows you to specify the URL of the scheduler or file server, number of tries for connecting to the scheduler, location of the staging directory, maximum number of services or
translations running on a machine, and other parameters.
two-tier architecture
Teamcenter architecture that includes a resource tier and a client tier. The resource tier comprises the database server and database. The client tier comprises the Teamcenter rich client, third-
party applications that integrate with the rich client, and a local server. This architecture supports only the Teamcenter rich client. Contrast with four-tier architecture.
two-tier deployment
Deployment of the Teamcenter two-tier architecture. In a typical deployment of the two-tier architecture, the rich client and its local server are installed on a user's workstation as are third-party
applications that integrate with the rich client. The database server and the Teamcenter corporate server are installed on one or more separate computers.
type display rule
Business rule that allows an administrator to control the object types that are available for creation in Teamcenter.
unincorporated change
Change that has been incorporated into one revision of an item but still must be incorporated into another revision. For example, the change has been incorporated into a supplemental revision
(Revision A01) but still must be incorporated into the main revision (Revision B).
unit of measure
Measurement category (for example, inches, millimeters, and so on). Create a unit of measure (UOM) when you need a new measurement for users.
unmanaged site
Supplier site that does not use Teamcenter to manage product data. These sites are always offline and use Briefcase Browser and briefcase files to manage and transfer product data.
Compare with managed site. See also offline site.
unpublished object
Object not available to other sites in a Multi-Site Collaboration network. Users can unpublish previously published objects so they are once again accessible only to the owning site.
unpublishing
Makes an object invisible to other sites. The object is accessible only by the local owning site.
Update Manager
Multiprocess system responsible for ensuring product structure changes are appropriately applied to appearances; includes the supervisor and updater processes.
update package
Discrete package of change information applied to appearance sets, either primary or secondary. Typically, update packages are created by the APPR-update-from-targets handler on the
workflow process. They are also created when the user saves the baseline appearance set or changes effectivity.
usage
Occurrence property that defines the position that the physical part occupies within the as-built structure.
usage address
Type of object that occupies an occurrence in the structure, for example, wheel.
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.
user calendar
Calendar for individual users. User calendars specify holidays and working times in a day.
user data element
Container for a list of name-value pairs that allows any attribute or property in a Teamcenter object that is not in the PLM XML equivalent to be stored.
user exits
Exit points from standard Teamcenter end-user functionality to a C program. These exit points are also known as custom hooks. Use them when you want to call your customizations directly
from a Teamcenter interactive session.
user preference
Teamcenter preference applying to a specific user.
validation agent
Teamcenter object that defines a validation application, such as NX Check-Mate, for use with Teamcenter. A validation agent can have one or multiple validation checkers, depending on the
logic in each integrated validation application.
validation checker
Teamcenter object that defines the parameters that the agent checks and produces the results of those checks. A validation checker is created in Teamcenter under its associated validation
agent.
Validation Manager
Teamcenter application that lets you view and manage validation results. It provides a decision mechanism to let users ensure a target meets compliance before it is released. Once validation
processes are configured, users can select a target in Teamcenter and confirm its compliance with the business rules defined at your site.
validation results
Information about a validation target object that can be used as the basis to determine whether a target conforms to standards and can be released. Validation Manager lets you view and
manage the validation results.
validation rule
Rule that defines the criteria needed to verify that all required checkers were executed against a certain target and that the expected results were achieved. For each checker, use rules to
define the test to be performed, the target to be tested, and the results to expect.
Valid Overlays Only
Option for configuring background part appearances that automatically filters out matching background parts known never to coexist in any possible variant combination with any of the target
appearances.
value
Content of a field or variable. It can refer to alphabetic, numeric, or alphanumeric data.
value map
Global Services XML-based file that maps data source attribute values to Global Services attribute values.
variability
Complete set of features referenced by a set of named variant condition templates.
variant BOM
BOM configured by applying a variant rule.
variant condition
• Rules applicable to one component in a product structure.
• Condition set on an occurrence to specify the features required to configure that occurrence (for example, Load IF engine = 1200).
variant rule
Collection of features used in determining the variant of the BOM to be configured (for example, car type = GLS, engine = 1200, gearbox = manual).
variant rule option
Description of product variations that are usually applied to higher level assemblies or the product itself.
vendor
Business object type; provider of parts or services. In Teamcenter, a vendor can take on one or more roles. Role definitions are not fixed in the data model, and can be adjusted to meet
customer business mode. Vendor roles, for example, can include:
• Distributor: Resells, but does not make, parts.
• Supplier: Makes parts to order for OEM.
• Manufacturer: Makes parts for the general market.
Vendor Management
Software functionality used to model vendor contributions to a product by letting users capture information about the vendors and the vendor parts they provide to satisfy the form, fit, and
function of commercial parts.
VendorPart
Business object type that is related to a CommercialPart object type by a Satisfies relation. A vendor part can be obtained from one or more vendors, but the actual builder of the part assigns
a part number.
versioned object base (VOB)
ClearCase storage mechanism that contains all the archived files and directories.
version GUID
Distinct GUID assigned to each separate version of an I-deas data item in the data item series. The version GUID uniquely identifies the data item.
view
Software element in a rich client user interface perspective. It provides the ability to navigate hierarchies of information, display information about selected objects, open an editor, or display
properties. See also perspective.
view (Classification)
Tailored representation of attributes within a class. Views are associated with abstract and storage classes. Attribute properties can also be applied. For example, a class may define the
physical and accounting attributes for its objects, but a view for tool designers may display only the physical attributes, and a view for accountants may display only pricing and order number
attributes.
view (ClearCase Integration)
Select version of a file in the archive as defined by a configuration specification. A view also contains generated files from the build process as well as any new files generated by the user.
viewing tool
External application used to view topics in Content Management in various output formats.
view type
Attribute of a BOM view revision. The view type specifies the BOM view revision's intended use (for example, design or manufacture). The view type distinguishes one BOM view revision from
another BOM view revision of the same item revision.
VisAutomationApp
Configuration of Teamcenter lifecycle visualization, similar to Teamcenter lifecycle visualization mockup, but has no menus or toolbars. It processes graphical reports created in Visualization
Illustration.
visualization
Ability to display a realistic, real time, graphical visualization of geometric data.
Visualization Automation Server
Often referred to as the Graphical Report Server (GRS), reads graphical report templates (VSD and VTP) and measurement data from Teamcenter. It updates the DPV Reporting & Analysis
charts in templates using the latest measurement data and publishes it to the Web.
volume
Operating system directory controlled by Teamcenter and used to store the files managed by Teamcenter. When a user performs an action that causes Teamcenter to create a file, the file is
created in the Teamcenter volume. Users cannot directly access the files in Teamcenter volumes; they must do so via a Teamcenter session.
Volume Management
Teamcenter application used by administrators to improve performance by creating migration policies that move lower priority files to either destination volumes or third-party storage systems.
volume reassignment
Reassignment of volumes containing relevant file data from the source site to the target site.
volume trickle
Volume handling technique used during the execution phase that allows volume data to remain in storage shared by the source and target sites. See also execution phase.
Web Application Manager

Graphical installation utility that generates supporting web files (WAR format) for a named web application.
web archive (WAR)
Web application that requires an HTTP web server and servlet engine.
Web Browser
Teamcenter application that provides access to Internet web pages from within the rich client framework. The Web Browser is a rich client window that acts as a web browser, enabling you to
navigate and view web pages within the rich client rather than switching to a separate web browser. Web Browser also provides the ability to access MIME (Multipurpose Internet Mail
Extension) file types and to view files created in other applications, such as Microsoft Word and Excel.
web tier
Teamcenter architectural tier that comprises a Java application running in a Java Platform, Enterprise Edition (Java EE) application server. The web tier is responsible for communication
between the client tier and enterprise tier.
weld
Junction or joint. Welds are used in manufacturing to connect two or more parts that are joined by fusing or melting materials together.
wire
Physical device that realizes a connection in a physical model.
wiring harness
See harness.
work area
Plant location performing an operation. The work area can represent the entire plant, the work line, an individual work cell, or a station within the plant. Work areas are described by their
location on the shop floor and the process capabilities they provide. Users can generate a hierarchy of work areas that is unique to their organizations.
work card
Defines the steps required to accomplish a service requirement. It contains the information about the tasks, required resources, time estimates, and cost estimates required to perform the
tasks. A service requirement can have one or more work cards. A work card always has a root activity, which can contain one or more activities.
work context
Object containing user, group, role, and project requirements for a particular task. Work contexts streamline the definition of the correct user settings required to perform tasks. For example, a
user typically assigned three types of tasks can create three work contexts reflecting the required group/role settings. Rather than logging out and logging back in with the required group/role
settings, right-clicking a task displays the user’s defined work contexts. Selecting the appropriate work context automatically changes the user’s group/role settings. Work contexts can also
define the current project, if project functionality is used at the site.
workflow
Automation of the concept that all work flows through one or more business processes to accomplish an objective. Using workflow, documents, information, and tasks are passed between
participants during the completion of a particular process.
Workflow Designer
Teamcenter application that enables administrators to graphically design workflow process templates, incorporating company business practices and procedures into the templates.
Teamcenter users initiate workflow processes using these templates.
Workflow Viewer
Teamcenter application that enables users to view the progress of a workflow process. Users are not required to be participating members of the process being viewed. Depending on
preference settings, Workflow Viewer also allows ad hoc process modification. See also ad hoc process modification.
working item content
When the CAD designer modifies an item structure that is instanced into a collaborative design, working item content is created. The designer intends to overlay the working item in the context
of the collaborative design or study.
working revision
Revision that can be changed by a user with write privileges. No record of intermediate states of a working revision is maintained by Teamcenter.
work instruction (manufacturing)
Document that describes how an operation should be completed at a work area. There are two categories of work instructions:
• Human readable instructions are primarily used to provide information to the operator about how to perform the operation.
• Machine instructions are program files that include numerical code used to run numerically controlled machines, such as robots and NC machines.
work instruction (Service Request Manager)
Document that describes how a service requirement, work card, or activity should be completed. It can contain information from elements of the service plan, including service requirements,
frequency, work cards, activities, notices, characteristics, narratives, part movements, zones, and required skills.
work order
Definition of the service work that is performed on one or more physical assets. Each work order has a single schedule associated with it to track the progress of the defined service work.
work part
Component intended to be the focus of a design or design review session.
workpiece
Intermediate state of the product during the manufacturing process. In each step of the manufacturing process, the workpiece is positioned in the work area and the work instructions are
performed. The resulting workpiece then flows to the next operation in the sequence, where the next operation is performed.
workset
Composition of design content from collaborative designs and item structures.
world
All users regardless of group or role.
XML attribute mapping

Object that enables the transfer of data between topic attributes in the XML tag content and database object properties and vice versa.
XML object list
Data Integration Services Adapter file that is formatted in XML and provides a list of the parts and assemblies to be populated into the JT cache.
zone
Occurrences in a neutral structure that are related to the maintenance. See also neutral structure.

TC12-My TC (My Help)

Uploaded by

Copyright:

Available Formats

TC12-My TC (My Help)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TC12-My TC (My Help)

Uploaded by

Copyright:

Available Formats

My Teamcenter

Primary Folder Description

Terms and Concepts

Versions When an encapsulated software application runs during a

Inbox Terms and Concepts

Terms or Concept Description

Search Terms and Concepts

Term or Concep Description

© 2017 Siemens Product Lifecycle Management Software Inc.

1 Global navigation buttons

Returns you to the home page.

Returns you to the previous screen.

4 Search box, with suggestions and prefilters.

5 Main work area.

© 2018 Siemens Product Lifecycle Management Software Inc.

Pin an object to the home page

2. On the toolbar, click the Pin button .

Unpin a tile from the home page

To move a tile from one group to another:

To move a tile and create a new group:

The tile is displayed in the new group.

© 2018 Siemens Product Lifecycle Management Software Inc.

© 2018 Siemens Product Lifecycle Management Software Inc.

Access to the Where Used function for NX assemblies.

Defaults and Preferences

Structure Update On Load

NX and Teamcenter Component Properties

© 2017 Siemens Product Lifecycle Management Software Inc.

Style sheet datasets

User preferences Conner: ConnersIRSum

Role preferences Manager: IRSumMgr

Group preferences Engineering: IRSumTech

Site preference value: ItemRevSum

How does Teamcenter choose which preference to use?

User - Group / Role Preference instance build-up Resulting style sheet

© 2018 Siemens Product Lifecycle Management Software Inc.

Administration data report

Raw XML export

Match is case-independent for alphabetic characters.

Find No. and Callout

See Callout Management for additional information.

Teamcenter Note Types

Teamcenter Note Type Description

Relationships between items

Note If intelligent part numbering is configured, ID values are assigned automatically.

6. Click Assign to automatically fill in the Revision ID boxes.

1.Choose File→Open or double-click the dataset.

2.Edit the dataset.

3.Save and close the dataset.

Step 2: Open the new item in Structure Manager

Step 3: Add a new item to the structure

4. Repeat the process to create additional parts for the assembly.

◦ Double-clicking the button takes you to the corresponding structure.

1. Locate the part you want to add to the structure.

Step 5: Create the subassembly

label (ClearCase Integration)

preference protection scope

Product Communication Layer (PCL) server