The Home folder is the top-level folder in the My Teamcenter tree.

 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.

Folders are objects that are used to organize product information in My Teamcenter. Folders can contain any other object, including other object folders.

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

BOMViews are used to manage product structure information for Items.

BOMView Revisions are used to manage product structure for Item Revisions.

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

An address list is any combination of valid users, groups, and/or external email addresses.

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.

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.

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 (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 , PSE, and Workflow.

Teamcenter properties contain detailed information about a selected object. You can view and/or modify the information for a selected object type.

When you duplicate an Item, Item Revision, or Dataset using File>Save As, the new Item, Item Revision, or Dataset has a based-on relationship to the original object.

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.

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.

A privileged user is a member of a System Administration group.

The automation of a business procedure, describing the individual tasks and task sequences required to complete a business procedure.

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 tasks include the EPM-hold handler, which stops the task from automatically completing when it is started.

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 subtasks allow you to assign specific users to perform the signoff for a specified task.

Perform Signoff Team subtasks allow you to perform a signoff on a specified 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.

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.

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.

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.

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, such as sorting options, case sensitivity for search criteria, and targeting remote sites, are specified by the user when a query is selected.

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.