Teamcenter 10.

Aerospace and Defense Solution Guide

Publication Number
PLM00111 G
Proprietary and restricted rights notice

This software and related documentation are proprietary to Siemens Product

Lifecycle Management Software Inc.
© 2013 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.
Siemens and the Siemens logo are registered trademarks of Siemens AG. Teamcenter
is a trademark or registered trademark of Siemens Product Lifecycle Management
Software Inc. or its subsidiaries in the United States and in other countries. All
other trademarks, registered trademarks, or service marks belong to their respective
holders.

2 Aerospace and Defense Solution Guide PLM00111 G

Contents

Proprietary and restricted rights notice . . . . . . . . . . . . . . . . . . . . . . . . . 2

Getting started with Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . 1-1

Getting started with Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Aerospace and Defense interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Basic concepts for using Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . 1-4
Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

Configuring Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Configuring organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Configuring rules and lists of values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Configuring programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Configuring part management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Configuring Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Configuring CAGE and location codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Configuring Aerospace and Defense objects with multifield keys . . . . . . . . . . . 2-16
Configuring authorized data access (ADA) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Configuring the Multi-Site Collaboration environment . . . . . . . . . . . . . . . . . . 2-18

Defining session settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Using CAGE codes and company location codes . . . . . . . . . . . . . . . . . . 4-1

Register company location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Edit company location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Add company code to an item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Working with Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . 5-1

Creating Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Revise Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Modify Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Delete Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Attaching preferred standard parts to programs . . . . . . . . . . . . . . . . . . . . . . 5-18
Associate preferred standard parts to programs . . . . . . . . . . . . . . . . . . . . . . . 5-19
Remove preferred parts from assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
Remove preferred parts from programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Building an assembly for a document-centric program . . . . . . . . . . . . . . . . . . 5-20

Generate part-centric parts list reports . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Working with notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Working with standard notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Working with custom notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

PLM00111 G Aerospace and Defense Solution Guide 3

Contents

Managing changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Managing changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Create a problem report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Create a change request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Create a deviation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Create a change notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Create a work breakdown using Schedule Manager . . . . . . . . . . . . . . . . . . . . 8-6
Managing unincorporated changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Managing contract data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Managing contract data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Defining data item descriptions (DIDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Create a contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Scheduling contract events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Working with data requirement items (DRIs) . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Defining submittal delivery schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11
Copy contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Providing feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Managing stock materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Basic concepts about stock materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Install stock materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Configure the display of the Made From folder . . . . . . . . . . . . . . . . . . . . . . . 10-2
Creating a classification library for stock materials . . . . . . . . . . . . . . . . . . . . 10-3
Create stock materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Add stock materials to the stock material library . . . . . . . . . . . . . . . . . . . . . . 10-4
Set stock material as program preferred stock material . . . . . . . . . . . . . . . . . 10-4
Assign stock material or standard part to a part . . . . . . . . . . . . . . . . . . . . . . 10-5
Assign stock materials to parts by using the copy-paste and drag drop
functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Managing stock materials using thin client . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9

Managing work packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Basic concepts about work packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Install work packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
Create a work package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2
Add objects to a work package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Managing work packages using the thin client . . . . . . . . . . . . . . . . . . . . . . . 11-3

Managing finishes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Basic concepts about finishes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Install finishes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Configure finishes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Create a library of finish and finish groups . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Create a finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Create a finish group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Add finishes to a finish group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5
Apply a finish or finish group to an item revision . . . . . . . . . . . . . . . . . . . . . . 12-5
Apply a finish or finish group to an item revision using the drag drop or copy-paste
functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7
Apply a finish or finish group to an item occurrence . . . . . . . . . . . . . . . . . . . . 12-7

4 Aerospace and Defense Solution Guide PLM00111 G

 Contents

Managing finishes using the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Managing configuration audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Basic concepts about configuration audits . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Setting up configuration audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Create a configuration audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3
Create an action item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Associating related objects with the configuration audit and action item . . . . . 13-5
Managing configuration audits using the thin client . . . . . . . . . . . . . . . . . . . 13-5

Searching for Aerospace and Defense items . . . . . . . . . . . . . . . . . . . . . 14-1

Aerospace and Defense Training Program . . . . . . . . . . . . . . . . . . . . . . . A-1

Aerospace and Defense training program . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Install the training program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Training program reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Aerospace and Defense data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Aerospace and Defense data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Preconditions and postactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
ADSTechDocument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
ADSPart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
ADSDesign . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
ADSDrawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
CommercialPart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
Aerospace and Defense template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21
Contract data management objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37
Stock material objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-50
Work package objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-51
Finish objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-51
Data model for Aerospace and Defense relations . . . . . . . . . . . . . . . . . . . . . B-52
Lists of values for Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . . B-57

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

PLM00111 G Aerospace and Defense Solution Guide 5

Chapter

1 Getting started with Aerospace

and Defense

Getting started with Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Before you begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Aerospace and Defense interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Basic concepts for using Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . 1-4

Program management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Part management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Change management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Aerospace and Defense administration functionality . . . . . . . . . . . . . . . . 1-6
CAGE codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Contract data management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

PLM00111 G Aerospace and Defense Solution Guide

Chapter

1 Getting started with Aerospace

and Defense

Getting started with Aerospace and Defense

The Aerospace and Defense solution provides data model extensions and features
that you access through standard Teamcenter applications, such as My Teamcenter,
Change Manager, Schedule Manager, and Structure Manager. The solution provides
multiple industry-specific features that enable you to:
• Execute complex document-centric or part-centric development programs.

• Manage parts lists and standard parts.

• Use standard and custom notes to provide additional design details about parts
and documents.

• Manage the program life cycle and its data, including program requirements,
deliverable schedules, and related changes.

• Protect intellectual property and national security while promoting collaboration.

In addition, you can extend Teamcenter Aerospace and Defense solution with other
Teamcenter capabilities including:
• Systems Engineering and Requirements Management

• Simulation Process Management

• Manufacturing Process Management

• Content Management

• Maintenance, Repair, and Overhaul

Before you begin

Prerequisites Teamcenter vendor management is a prerequisite
for the Aerospace and Defense solution.
You do not need special privileges to use
Aerospace and Defense. However, configuring and
customizing tasks require administrator privileges.

PLM00111 G Aerospace and Defense Solution Guide 1-1

Chapter 1 Getting started with Aerospace and Defense

Enable Aerospace and While installing Teamcenter on your machine, you

Defense must choose to install the following features in the
Select Features panel in Teamcenter Environment
Manager (TEM) to enable Aerospace and Defense:
• Teamcenter Foundation

• Vendor Management

• Aerospace and Defense Foundation

• (Optional) Aerospace and Defense Training

• (Optional) Change Management

• (Optional) Aerospace and Defense Change

Management

• (Optional) Contract Data Management

Note • Select the Aerospace and Defense
Training feature only if you want to
install the default training program
that is provided along with the
Aerospace and Defense Foundation
template. The training program is a
template that includes a program and
corresponding business rules, lists of
values, and conditions that you can
use as a basis for creating your own
programs.

• Select the Change Management and

Aerospace and Defense Change
Management features only if you
want to install the Change Manager
application.

• Select the Contract Data Management

features only if you want to install
the Contract Data Management
application.

For more information about installing Teamcenter

on Microsoft Windows servers, see the Installation
on Windows Servers Guide.

1-2 Aerospace and Defense Solution Guide PLM00111 G

 Getting started with Aerospace and Defense

For more information about installing Teamcenter

on UNIX servers, see the Installation on UNIX and
Linux Servers Guide.
For more information about installing Teamcenter
on Microsoft Windows clients, see the Installation
on Windows Clients Guide.
For more information about installing Teamcenter
on Linux clients, see the Installation on Linux
Clients Guide.
Note Aerospace and Defense participates in
the Teamcenter named user licensing
scheme. When a user logs on, a named user
license of the appropriate category must be
available or access to the system is denied.
The system administrator assigns licenses
according to each user’s access needs, as
described in the Organization Guide. For
example, a user who views, approves,
rejects, or comments on information may
be assigned one level of license, while
a user who creates or edits information
must be assigned another type of license.
Each administrator (including infodba)
requires the highest level of license.
Configure Aerospace and Aerospace and Defense is installed using
Defense Teamcenter Environment Manager (TEM).
After it is installed, you can use administrative
tools such as:
• Business Modeler IDE to define business
objects, lists of values (LOVs), and rules that
model your company’s business processes.

• Organization to model your company’s

organization in Teamcenter.

• Workflow Designer to define workflow processes

to manage your data.

• Access Manager to implement data security.

For more information, see Configuring Aerospace

and Defense.
Also, see the Business Modeler IDE Guide,
Organization Guide, and Workflow Designer Guide.

PLM00111 G Aerospace and Defense Solution Guide 1-3

Chapter 1 Getting started with Aerospace and Defense

Aerospace and Defense interface

The Aerospace and Defense solution uses the Teamcenter interface.
For information about common Teamcenter elements, see Getting Started with
Teamcenter.

Basic concepts for using Aerospace and Defense

Program management

A program identifies a collection of resources and assets bound by a common

objective, for example the design and development of a new aircraft.
Using programs you can:
• Segregate data and users.
You can create, search, and modify only those objects of a program for which
you have access.

• Write business rules based on programs.

Business rules consist of naming rules, conditions, display rules, lists of values,
and so on.
For more information, see Configuring rules and lists of values.

• Write access rules based on programs.

You can enable program-level security to restrict access to program data.
You can extend the default security rules to the program team members on
a program-by-program basis.

1-4 Aerospace and Defense Solution Guide PLM00111 G

 Getting started with Aerospace and Defense

For more information about program-level security, see the Security

Administration Guide.

• Configure items to be used as preferred parts in a program.

• Create document-centric or part-centric programs.

A document-centric program requires you to create a source document (technical
document) before you create a part. A part-centric program does not require you
to create a source document when creating parts.

Part management
The parts management functionality offers the following features:
• Parts
Aerospace and Defense solution provides three business objects relating to parts.
These business objects contain attributes specific to Aerospace and Defense.

Part Represents a product, part, or component. Parts represent

the physical parts that make up the products of your
enterprise. Parts can comprise assemblies, components,
standard parts, and so on. Each part can have one or more
computer-aided designs (CAD) associated with it.
Components represent the individual pieces of a product.
They are the lowest level of the product structure. A
component could be any item used in an assembly as part
of the assembly’s product structure.
Design Represents the design of a component, assembly, or part.
Drawing Represents a technical illustration that details out one or
more assemblies and parts created on a source technical
document.

• Technical documents
Technical documents are the written form of technical information such as part
lists, drawings, procurement specifications, and schematics. A document-centric
program requires a source document to create a part, assembly, design, or
drawing. Aerospace and Defense uses the technical document as the source
document.
The Technical Document object represents a technical document.

• Assemblies
Assemblies represent groupings of parts. It can include other assemblies,
components, standard parts, and so on. The assembly structure can be built
either through Structure Manager or through CAD applications.

• Standard parts
Standard parts are specific to the Aerospace and Defense industry. They
represent parts that are used across multiple programs and whose design is
controlled by a standard specification specified by the military, an industry, or a
company. You can set a standard part as a preferred part for a program.

PLM00111 G Aerospace and Defense Solution Guide 1-5

Chapter 1 Getting started with Aerospace and Defense

In the Aerospace and Defense solution, the Commercial part object represents
a standard part.
Note You can only use the Commercial part in an assembly if the part is a
preferred part to all the programs to which the assembly is associated
with.

• Reports
You can generate part-centric part list reports.
The part centric parts list reports show the details of the structure of an
assembly.

• Notes
You can enhance the source document and parts with notes. Notes provide
additional design details about the product structure and configuration. Notes
can be of the following types:
Notes can be of the following types:

Standard notes Contain generic information that is applicable globally and

can be associated with multiple source documents or parts.
Custom notes Are defined for a specific document or part and provide
specific information about that document or part.

Change management
You can create change objects containing Aerospace and Defense specific attributes
using the Change Manager application. Aerospace and Defense supports the
following change objects:
• Problem report

• Change request

• Change notice

• Deviation request

• Work breakdown

For more information, see Managing changes.

Aerospace and Defense administration functionality

The Aerospace and Defense solution offers the following administration functionality:
• Naming rules
A naming rule defines how objects are named, including how IDs and revision
IDs are automatically assigned when objects are created.

• Revision naming rules

1-6 Aerospace and Defense Solution Guide PLM00111 G

 Getting started with Aerospace and Defense

A revision naming rule is a business rule that defines the naming convention
and sequence for a revision property. You can create revision naming rules that
confirm to Aerospace and Defense revisioning schemes.

• Program administration functionality

Programs provide the following administration functionality:

o Define data and user access based on a program.

o Define business rules based on a program.

o Define naming rules based on a program.

o Define extension rules based on a program.

o Define list of values based on a program.

CAGE codes
A CAGE Code is a 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.
With the Aerospace and Defense solution, you can:
• Register CAGE code for a company location.

• Set a default CAGE code preference for a user.

• Assign CAGE code to a part.

• Upgrade legacy data to populate CAGE code from the owning organization.

• Assign CAGE code to a part through CAD integrations.

For more information, see Using CAGE codes and company location codes.

Contract data management

Contracts are pivots that drive business across different industry sectors. A contract
is a structured procurement document listing the milestones and the schedule dates
of the contract event. This procurement document can be a list of data requirement
items, such as design information, drawings, status reports, and so on.
After the contract is created, the data analyst creates a workflow schedule to collate
the feedback and the review comments that are generated during the data item
approval process. This is done by initiating correspondence related to the contract.
A graphical representation of managing contract data through Teamcenter is shown
in the following figure.

PLM00111 G Aerospace and Defense Solution Guide 1-7

Chapter 1 Getting started with Aerospace and Defense

The sequence of steps is as follows:

1. Create data item descriptions (DIDs).
DIDs are predefined contract forms that specify data content, data format, and
other specific instructions for the suppliers.
You can maintain a DID repository to associate a data requirement item (DRI) to
the contract.

2. Create a contract.
The administrator or the data analyst creates a contract and contract revision in
Teamcenter. You can also choose to create a contract event for scheduling the
contract review and feedback process.

3. Create data requirement items.

You must attach a data requirement item (DRI) to the contract. A DRI
is a technical document or deliverable that forms the basis for structured
procurement. It represents a single contractual data item as described in DID.

4. Define submittal delivery schedule for the deliverable.

After the DRI is specified, you must initiate the review process. Submittal
represents the data item submittal package or documentation that relates to the
actual documents submitted.

1-8 Aerospace and Defense Solution Guide PLM00111 G

 Getting started with Aerospace and Defense

5. Provide feedback.
It is important to monitor the correspondence and feedback related to the data
item submittal package between you and the supplier.

Aerospace and Defense objects

In the Aerospace and Defense solution, objects are used to represent product data,
such as parts, assemblies, documents, drawings, designs, product requirements,
and specifications. These objects are stored in the database and can be accessed
by users across the enterprise.
Objects can be associated with each other. The association between the objects is
defined through a relationship.
The following table lists the Aerospace and Defense solution data model objects.

Symbol Object Description

Technical Document Are the written (printed or digital) form
(ADSTechDocument) of technical information such as reports,
drawings, procurement specifications, parts,
lists, interface control documents, and
schematics.
Technical documents serve as a source for
creating parts and assemblies for a product.
Part (ADSPart) Are components or assemblies that are
included in the product.
A component is typically the smallest discrete
piece considered in the design and production
processes. An assembly comprises several
components and (optionally) other assemblies.
Design (ADSDesign) Represents the computer-aided design (CAD)
of a component or assembly or an ADS part.
Drawing Represents a drawing. They are related to
(ADSDrawing) technical documents.
Commercial part Represents a standard part. Standard parts
(CommercialPart) represent commonly used parts that have been
identified as a standard design by a company,
an industry, or the military.
Note The commercial part business object
is included in the vendor management
template.
Standard Note Represents the notes established by the
(Ads0StdNote) Standards Engineering organization that
conform to the design practices of a program.
Standard notes can be used by all designers.

PLM00111 G Aerospace and Defense Solution Guide 1-9

Chapter 1 Getting started with Aerospace and Defense

Symbol Object Description

Custom Note Represents the unique notes for an individual
(Ads0CustomNote) part or document and are created by the
designer responsible for the part or document.
Contract data Represents the contract document used in
(Cdm0Contract) document-centric programs.
Contract revision Represents the association of the contract
(Cdm0Contract revision data with data requirement item.
Revision)
Data Represents an individual data requirement in
requirement item a data requirement list.
(Cdm0DataReqItem)
Data requirement Represents the specifications of the data item
item revision requirement.
(Cdm0DataReqItem
Revision)
Data item description Are predefined contract forms that specify
(Cdm0DID) data content, data format, and other specific
instructions for the suppliers.
Maintain a DID repository to associate a data
requirement item (DRI) to the contract.
Data item Represents the specifications of the data item
description revision description.
(Cdm0DIDRevision)
Submittal Represents the data item submittal package
(Cdm0Submittal) or documentation that relates to the actual
documents submitted. The data analyst
creates a submittal delivery schedule for the
tasks.
Submittal revision Represents the specifications of the submittal.
(Cdm0Submittal
Revision)
Correspondence Represents the feedback received from
(Cdm0 customers. The data analyst attaches offline
Correspondence) feedback from customers to the correspondence
object that is created in Teamcenter.
Correspondence Represents the specifications of the
revision data (Cdm0 correspondence.
Correspondence
Revision)
Tabular data table This object is created to store the rows for
(Fnd0StaticTable) tabular data.
Event data table This object is created to store event data in the
(Cdm0Events data requirement item (DRI) event table.
Table)

1-10 Aerospace and Defense Solution Guide PLM00111 G

 Getting started with Aerospace and Defense

The following table describes the Aerospace and Defense solution object relation
types.

Relationship Description
ADS lists parts revisions relation Defines the relationship between a technical
(ADS_Lists_PartsRevisions) document revision and an ADS part or ADS
design revision.
An ADS part or an ADS design that is created
on a given technical document is associated to
the technical document revision through the
ADS_Lists_PartsRevisions relation.
ADS lists parts relation Defines the relationship between a technical
(ADS_Lists_Parts) document revision and an ADS part or ADS
design item.
Items corresponding to an ADS part or ADS
design are created on a technical document
and are used on an assembly. They are
associated with the technical document
revision corresponding to the assembly
through the ADS_Lists_Parts relation.
ADS lists drawing revisions Defines the relationship between a technical
relation document revision and an ADS drawing
(ADS_Lists_DrawingRevisions) revision.
When ADS drawings are created on a given
technical document, they are associated with it
through the ADS_Lists_DrawingRevisions
relation.
Program preferred items relation Defines the relationship between a business
(TC_Program_Preferred_Items) object and a program.
When business objects are set up as
preferred parts to programs, they are
associated to the programs through the
TC_Program_Preferred_Items relation.
Parametric requirements lists Defines the relationship between a business
(ListStandardNotes) object and a standard note.
A standard note or a standard note revision
is attached to a business object through the
ListStandardNotes relation.
Parametric requirements lists Defines the relationship between a business
(ListsCustomNotes) object and a custom note.
A custom note or a custom note revision is
attached to a business object through the
ListsCustomNotes relation.

PLM00111 G Aerospace and Defense Solution Guide 1-11

Chapter 1 Getting started with Aerospace and Defense

Relationship Description
Described by data item description Defines the relation between the
(Cdm0IsDescribedbyDID) objects, Cdm0DIDRevision and
Cdm0DataReqItem Revision.
This will be used to support the requirement
of creating data requirement item revision
and associating it with contract revision.
List data requirement Defines the relation between data requirement
item submittal schedule item revision and submittal delivery schedule.
(Cdm0ListsDRISubmittalSch)
Lists data requirement Defines the relation between the objects,
item submittal Cdm0DataReqItemRevision and
(Cdm0ListsDRISubmittal) submittal.
List correspondence submittal Defines the relation between the
(Cdm0ListsCorspSubmittals) objects, Cdm0SubmittalRevision and
Cdm0CorpondenceRevision.
Lists correspondence revision Defines the relation between the objects,
and contract revision Cdm0CorpondenceRevision and
(Cdm0ListsCorspRefItems) Cdm0ContractRevision.
Lists contract data requirement Defines the relation between the
item (Cdm0ListsContractDRI) objects, Cdm0ContractRevision and
Cdm0DataReqItemRevision.

1-12 Aerospace and Defense Solution Guide PLM00111 G

Chapter

2 Configuring Aerospace and

Defense

Configuring organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Configuring organizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Automatically assign an organization to an object . . . . . . . . . . . . . . . . . . 2-1

Configuring rules and lists of values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Configuring rules and lists of values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Configuring naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Configuring revision naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Configuring display rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Configuring extension rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Configuring conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Configuring list of values (LOVs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Configuring programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Configuring part management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Configuring document-centric programs . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Configuring technical documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Specifying who can work with Aerospace and Defense objects . . . . . . . . . . 2-7
Configuring standard and preferred standard parts . . . . . . . . . . . . . . . . . 2-8
Configuring standard notes and custom notes . . . . . . . . . . . . . . . . . . . . . 2-9
Configuring standard notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Configuring custom notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Configuring Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Configuring Change Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Configure a group to create change requests and change notices . . . . . . . . 2-10
Create change forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Adding properties to change objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Define business objects to be associated with a change notice . . . . . . . . . . 2-12

Configuring CAGE and location codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Configuring CAGE and location codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Assign company location to users and groups . . . . . . . . . . . . . . . . . . . . . . 2-14

Configuring Aerospace and Defense objects with multifield keys . . . . . . . . . . . 2-16

Configuring authorized data access (ADA) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Configuring authorized data access (ADA) . . . . . . . . . . . . . . . . . . . . . . . . 2-16

PLM00111 G Aerospace and Defense Solution Guide

 Basic tasks for configuring and administering authorized data access for IP
data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Basic tasks for configuring and administering authorized data access for ITAR
restricted data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Configuring the Multi-Site Collaboration environment . . . . . . . . . . . . . . . . . . 2-18

Configure the Is Owned By Program rule to support Aerospace and Defense data
exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Importing and exporting project or program data in a Multi-Site Collaboration
environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Aerospace and Defense Solution Guide PLM00111 G

Chapter

2 Configuring Aerospace and

Defense

Configuring organizations

Configuring organizations
Organizations provide an industry-compliant format for uniquely identifying entities.
An organization can be an internal entity, such as a Research and Development
organization, or an external entity, such as a supplier or customer.
Use the Teamcenter Organization functionality to set up and manage your
organization.
For more information, see the Organization Guide.

Creating organizations
To create organizations, create groups using Organization functionality and assign
Authorized Data Access (ADA) and International Traffic in Arms Regulations (ITAR)
attributes to the group.
For more information about creating organizations, see Organization Guide.
For more information about implementing authorized data access for classified data,
see the Security Administration Guide.

Automatically assign an organization to an object

The TcSetOwningOrganization global constant enforces that the owning
organization for an object is set automatically. This global constant works
in conjunction with the AutoAssignOwningOrg business object constant,
which specifies which business objects are affected (by default, all children of
the WorkspaceObject business object). The owning organization is set as the
organization corresponding to the logon group of the user.
The following example explains the behavior of the TcSetOwningOrganization
and AutoAssignOwningOrg constants for the ADSPart business object.

PLM00111 G Aerospace and Defense Solution Guide 2-1

Chapter 2 Configuring Aerospace and Defense

Business TcSetOwning AutoAssign

object Organization OwningOrg Behavior
global constant business constant
ADS part true true Automatic setting of owning
organization for ADS part types is
enabled.
ADS part true false The owning organization is not set for
ADS part types because automatic
setting of owning organization for
ADS parts is not enabled.
ADS part false true The owning organization is not set
for ADS part types because the
system does not enforce owning
organization for business objects to
be set automatically.

Configuring rules and lists of values

Configuring rules and lists of values

Rules govern the behavior of business objects, including how they are named, what
actions can be undertaken on them, and so on. The system administrator defines
rules using the Business Modeler IDE.
You can use the following rules to configure your Aerospace and Defense
environment:
• Naming rules

• Revision naming rules

• Display rules

• Extension rules

• Conditions

For more information about rules, see Business Modeler IDE Guide.
Lists of values (LOVs) are pick lists of data entry items which are accessed by
Teamcenter users from a menu at the end of a data entry box. They are used to
ensure consistent data entry in Teamcenter.
For more information about rules, see Business Modeler IDE Guide.

Configuring naming rules

Naming rules consist of rule patterns and counters that determine:
• How objects are named.

• How IDs are automatically assigned when an object is created.

2-2 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

For example, if you want all document object names to include the prefix Document_
followed by an incremental number, you can create a naming rule that automatically
assigns the prefix when users create document objects.
Naming rules can be applied to:
• Items

• Item revisions

• Datasets

• Forms

• Programs

• Work contexts

For more information about naming rules, see the Business Modeler IDE Guide.

Configuring revision naming rules

Business objects are revised repeatedly. Each time an object is revised, the revision
ID increments to indicate that the object has been revised and the new revision
supersedes the previous revision. Revision naming rules make it easy to maintain
the revision scheme for business objects. The revision naming rules are specific
to the Aerospace and Defense industry.
As a Teamcenter administrator, you can define revision naming rules. There are
three revision types that can be defined for a revision naming rule: initial, secondary,
and supplemental. The initial revision type is mandatory, whereas the secondary
and supplemental revision types are optional.
When an object is created, the system automatically assigns the starting revision ID
as defined in the initial revision type.
When the object is revised, the next available revision ID options are displayed for
selection. You can select the revision ID from the available options or type a new
revision ID for the object. Revision ID options are provided by the revision naming
rule attached to the business object.
The following example assumes that a revision naming rule is attached to the
part business object. The revision naming rule defines initial, secondary, and
supplemental revision types for parts. The initial revision type is numeric and starts
at 01. It is applied when a part is in the design phase. The secondary revision type
is alphabetic and starts at A. It is applied when a part has been released. The
supplemental revision type is alphanumeric and starts at A01; it is applied for
minor changes.
Assume that a designer creates a part. The part is created and is in the design
phase. Therefore, the revision is 01. As the part is worked on, multiple iterations are
frozen and revised so that there is always a backup of the latest work.
After the part has been frozen, more work needs to be done on the part for the
design phase so it is revised. When revising the part, the designer selects the initial
revision type, 02 Design, because the work is done in the design phase. Therefore,
the revision is 02.

PLM00111 G Aerospace and Defense Solution Guide 2-3

Chapter 2 Configuring Aerospace and Defense

The designer completes working on the part and freezes it. The design work is
complete and the part is ready to be released. Therefore, the designer revises the
part selecting the secondary revision type, A Released. The revision value is now
A. The part is checked in and is frozen.
In the testing phase, the test conducted on the part indicates that some rework
might be required. The designer revises the part choosing the supplemental revision
type, A01 Rework. The revision value is now A01. When the rework is complete,
the part is checked in and frozen.
When the reworked part is approved for release, the designer revises the part and
selects the secondary revision type, B Released. The revision value is now B. The
part is checked in and frozen.
For more information about revision naming rules, see the Business Modeler IDE
Guide.

Configuring display rules

Business object display rules limit the types of objects that can be created by users
in particular groups or roles.
• The Display Rules view shows the groups that can view a business object in the
create menus in the Teamcenter user interface. These groups are allowed to
create the selected type of business object.

• Display rules can be based on a condition. If the condition is met, the business
object is not displayed to the specified groups or roles in the Create menus in
the Teamcenter user interface.

• The display rules can be applied to the following business objects and their
children:
o Alias

o Dataset

o Folder

o Form

o Identifier

o Item

For more information about display rules, see the Business Modeler IDE Guide.

Configuring extension rules

Extension rules allow you to customize system behavior by applying extensions to
extension points that are related to business operations in Teamcenter. Business
operations are actions performed in the system, such as creating and saving an item,
fetching or setting a property value, or invoking a user exit. Extension points are
events in the system, such as a post action on an operation or a user exit, that allow
you to implement custom behavior. Extensions contain information about functions
associated with Teamcenter business objects and properties.

2-4 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

Extension points include:

• Pre-Condition
Places limits before an action. For example, limit individual users by their work
context to create only a certain item type. Preconditions are executed first in an
operation dispatch. If any of the preconditions fails, the operation is aborted.
Typical examples of preconditions are naming rules.

• Pre-Action
Executes code before an action. For example, add user information to the session
prior to translation. Pre-actions are executed after preconditions and before the
base-action. If any of the pre-actions fails, the operation is aborted. A typical
example is an initial value rule that needs to set an initial value before the
save base-action is invoked.

• Base-Action
Executes code for an action. The base-action is the actual operation
implementation, and cannot be replaced.

• Post-Action
Executes code after an action. For example, automatically start an item in a
workflow. If any of the post-actions fail, the operation is aborted.

Extension rules can be defined and attached to a business object operation or a

business object property operation so that it is invoked at a particular extension
point when a given condition is satisfied.
For information about extension rules, see the Business Modeler IDE Guide.

Configuring conditions
Conditions are conditional statements that are run with rules and resolve to true
or false. Conditions can be used to evaluate objects or user sessions to deliver only
certain results.
A condition resolves to TRUE if the statement is valid or FALSE if it is not. Rules
use conditions to describe the types of objects to which the rules apply.
When a rule that uses a condition is run against an object, it is divided into two parts
that you can think of as an IF clause and a THEN clause. The condition (IF clause)
examines the object with Boolean logic, and the rule (THEN clause) describes an
action or access permission on the object.
For example:
IF the current program for the user session = ‘F18’
THEN naming rule (NR1) be applied to the ADSTechDoc business object.

Note You can configure naming rules, revision naming rules, display rules,
extension rules and List of Values based on conditions.

For information about conditions, see the Business Modeler IDE Guide.

PLM00111 G Aerospace and Defense Solution Guide 2-5

Chapter 2 Configuring Aerospace and Defense

Configuring list of values (LOVs)

Lists of values (LOVs) are pick lists of data entry items that:
• Are commonly accessed by Teamcenter users from a menu at the end of a data
entry box. They are used to ensure consistent data entry in Teamcenter.

• Must be attached to a property on a business object after creation. LOVs can be

attached to a property of a business object based on a condition.

• May have sub-LOVs (cascading LOVs) attached to the main LOV.

For reference information about LOVs, see the Business Modeler IDE Guide.
For information about LOVs introduced by the Aerospace and Defense solution, see
Lists of values for Aerospace and Defense.

Configuring programs
Use the Project and Program application to set up and manage your projects.
For more information, see the Project and Program Guide.

Configuring part management

Configuring document-centric programs

In Aerospace and Defense, programs can be document-centric or part-centric. A
document-centric program requires that you create a source document (technical
document) before you create a part, design, or drawing. Part-centric programs do not
require you to specify the source document when creating parts.
Using document-centric programs you can:
• Ensure that proper relationships are maintained between documents and parts.

• Manage parts list documents that are revised independently of the part.

• Have a single source document list multiple parts.

To make a program document-centric, update the ADSDocumentCentricPrograms

LOV with the name of the program.
For more information about updating a LOV, see the Business Modeler IDE Guide.

Configuring technical documents

You can configure Teamcenter to:
• Automatically select a technical document when you create Aerospace and
Defense items in a document-centric program.
This configuration allows you to create an item without having to select a
technical document.

2-6 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

To configure automatic selection of a technical document when an Aerospace and

Defense item is created, set the value of the ADSAutoSelectTechdoc global
constant to true.

• Automatically create a technical document when you create Aerospace and

Defense items in a document-centric program.
This configuration allows you to create an item without creating a technical
document before item creation.
To configure automatic creation of a technical document when an item is created,
set the value of the ADSAutoCreateTechdoc global constant to true.

For information about changing the value of a global constant, see the Business
Modeler IDE Guide.

Specifying who can work with Aerospace and Defense objects

Users must be granted authority to create, revise, and save Aerospace and Defense
business objects. Authority is based on the user’s current role. When you create or
revise an Aerospace and Defense technical document, part, design, or drawing,
Teamcenter compares your role to the roles defined in the authority list of values
(LOV) that applies to the object you are creating or revising. If your role is defined in
the LOV, permission to the object is granted.
Using the Business Modeler IDE, administrators can specify the user roles that can
create, revise, and save business objects that are specific to Aerospace and Defense,
such as ADSTechDocument, ADSPart, and ADSDesign objects. This is done
using lists of values (LOVs).
The following table lists the LOVs that can be updated to specify which user roles
can create, revise, and save the corresponding Aerospace and Defense business
object types.

Business object List of values Notes

ADSTechDocument ADSTechDocAuthority Use the ADSTechDocAuthority LOV to
specify the user roles that are authorized
to create or revise technical documents.
ADSPart and ADSDesign ADSComponentAuthority Use the ADSComponentAuthority LOV
to specify the user roles that are authorized
to create or revise ADS parts and ADS
designs.
ADSDrawing ADSDrawingAuthority Use the ADSDrawingAuthority LOV to
specify the user roles that are authorized
to create or revise ADS drawings.
Ads0StdNote Ads0CreateStandardNoteAuthority Use the
Ads0CreateStandardNoteAuthority
LOV to specify the user roles that are
authorized to create or revise standard
notes.

Note The default value of these LOVs is an asterisk (*), indicating that all user
roles can create or revise Aerospace and Defense objects.

PLM00111 G Aerospace and Defense Solution Guide 2-7

Chapter 2 Configuring Aerospace and Defense

Configuring standard and preferred standard parts

Standard parts represent parts that may be used across multiple programs and
whose design is controlled by a standard specification. The standard specification
can be:
• Company

• Industry

• Military

Standard parts are maintained by an Engineering Standards group. The

Engineering Standards group creates and maintains a library of standard parts
to be used by designers.

Configuring objects to be used as standard parts

By default, the commercial part business object (provided by the vendor management
template) is configured as a standard part in the Aerospace and Defense Foundation
template.
You can configure an object to be used as a standard part by adding the object name
to the TCProgramPreferredTypes LOV.
For more information about adding a value to a LOV, see the Business Modeler
IDE Guide.

Enabling standard parts to be used as preferred parts for programs

To enable a standard part as a preferred part of a program, establish the
TC_Program_Preferred_Items relation between the standard part and the
program.
You can create this relationship using GRM rules. When creating the GRM rule, add
the following information to the GRM Rule dialog box:

GRM Rule dialog box field Value

Primary Object TC_Project
Secondary Object Object to be used as the prefferred standard
part
Relation Object TC_Program_Preferred_Items

For more information about GRM rules, see the Business Modeler IDE Guide.

Enabling programs to use preferred standard parts

Update the TCProgramsUsingPreferredTypes LOV with the name of the
programs that must use preferred standard parts in their assemblies.
For more information about adding a value to a LOV, see the Business Modeler
IDE Guide.

2-8 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

Configuring standard notes and custom notes

Configuring standard notes

Configuring who can create standard notes

You can specify the roles that are allowed to create notes and requirements and then
specify access privileges based on these roles.
To specify the roles that are allowed to create standard notes and parametric
requirements, add the roles to the Ads0CreateStandardNoteAuthority LOV. You
can then grant access privileges based on those roles.
For more information about updating the LOV, see the Business Modeler IDE Guide.
For information about applying access privileges, see the Access Manager Guide.

Setting the delimiter that separates parameters in standard note text

A standard note or parametric requirement contains:
• Text

• A parameter and applicable values, using the following syntax:

text [parameter name: parametric value1 delimiter parametric
value2 delimiter ..... parametric value n]

The default delimiter separating the parameters in the note is a comma (,). To
change the delimiter, set the Fnd0ParamReqDelimiter global constant.
For more information about setting global constants, see the Business Modeler IDE
Guide.

Enabling multiple revisions of a standard note to be attached to an item

or item revision
By default, only one revision of a standard note or parametric can be attached to
an item or item revision.
You can enable multiple revisions of the same standard note or parametric
requirement to be attached to an item or item revision by setting the value of the
AllowMultipleRevisionsofStdNotes global constant to true.
For more information about setting global constants, see the Business Modeler IDE
Guide.

Configuring custom notes

Custom notes provide unique information about an individual part or document,
and they can be attached to an item or item revision. The following behavior can
be configured for custom notes:
• By default, a custom note item can be attached to a single item or multiple
revisions of the same item. A custom note item cannot be attached to multiple
items or to revisions of multiple items.

PLM00111 G Aerospace and Defense Solution Guide 2-9

Chapter 2 Configuring Aerospace and Defense

To enable a custom note item to be attached to multiple items or revisions

of multiple items, set the Fnd0AttachCustomNoteToMultiItems business
constant to true.

• By default, multiple revisions of a custom note cannot be attached to an item

or item revision.
To enable multiple revisions of a custom note to be attached to an item or item
revision, set the Fnd0AllowMultipleRevofCustomNote global constant to
true.

For more information about setting global constants, see the Business Modeler IDE
Guide.

Configuring Change Manager

Configuring Change Manager
You can configure Change Manager to meet your business needs and help you follow
your documented process.
For a complete description of the tasks for customizing and configuring Change
Manager, see the Change Manager Guide.

Configure a group to create change requests and change notices

1. In Organization, create a group that contains users who work with change
objects and add those users to the group. For example, create the Change
Management group.
For more information about creating groups and adding users, see the
Organization Guide.

2. Open the Business Modeler IDE.

3. Access the Advanced perspective by choosing Window→Open

Perspective→Other→Advanced.

4. In the Extensions view, select the project in which you want to create the
condition. Right-click the project and choose Organize→Set active extension
file. Select the file where you want to save the data model changes.

5. Expand the project and the Rules→Conditions folders.

6. Double-click the isChangeRequestCreatable condition.

7. In the Expression box, type the following after the existing text:
OR u.group_name = "new-group"

If you use the example group from step 1, type the following:
OR u.group_name = "Change Management"

8. Double-click the isAdc0ChangeRqstCreatable condition.

2-10 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

9. In the Expression box, type the following after the existing text:
OR u.group_name = "new-group"

If you use the example group from step 1, type the following:
OR u.group_name = "Change Management"

10. Double-click the isChangeNoticeCreatable condition.

11. In the Expression box, type the following after the existing text:
OR u.group_name = "new-group"

If you use the example group from step 1, type the following:
OR u.group_name = "Change Management"

12. Double-click the isAdc0ChangeNoticeCreatable condition.

13. In the Expression box, type the following after the existing text:
OR u.group_name = "new-group"

If you use the example group from step 1, type the following:
OR u.group_name = "Change Management"

14. Double-click the isCm0DevRqstCreatable condition.

15. In the Expression box, type the following after the existing text:
OR u.group_name = "new-group"

If you use the example group from step 1, type the following:
OR u.group_name = "Change Management"

16. Double-click the isAdc0DevRqstCreatable condition.

17. In the Expression box, type the following after the existing text:
OR u.group_name = "new-group"

If you use the example group from step 1, type the following:
OR u.group_name = "Change Management"

18. To save the changes to the data model, choose File→Save Data Model, or click
the Save Data Model button on the main toolbar.

19. Deploy the data model to the database.

Users in the Change Management and dba groups can create change requests
and change notices.

Create change forms

1. Select the change object you want to create the form for.

2. Choose File→New→Form.

PLM00111 G Aerospace and Defense Solution Guide 2-11

Chapter 2 Configuring Aerospace and Defense

3. In the New Form dialog box, select one of the following form types:
• Adc0ChangeRqst Master

• Adc0ChangeRqstRevision Master

• Adc0ChangeNotice Master

• Adc0ChangeNoticeRevision Master

• Adc0DevRqst Master

• Adc0DevRqstRevision Master

• ProblemReport Master

• ProblemReportRevision Master

4. In the Name box, type a name. Optionally, type a description in the Description
box.

5. If you do not want the form to open after you create it, clear the Open on Create
check box.

6. Click OK.

Forms attached to a change item are displayed in the Change Home and Teamcenter
Component views. Forms attached to a change item revision are displayed in the My
Open Changes and My Open Tasks folders and the Change Home and Teamcenter
Component views.
For more information about creating forms, see the My Teamcenter Guide.

Adding properties to change objects

If you want to add persistent properties to change objects, you can extend business
classes directly using the Business Modeler IDE. You can also create a dialog box
definition by specifying the required and optional properties for an instance creation.
Subclasses that do not have their own dialog box definition inherit the dialog box
definition of their parent class. To display new properties, you must add them to the
style sheets defined for the change object.
For more information about adding properties using the Business Modeler IDE,
see the Business Modeler IDE Guide.

Define business objects to be associated with a change notice

Change notices specify a detailed work plan to resolve a set of requests (change
requests and deviation requests). The change notice identifies all the items and
documents affected by a change and it also authorizes the actions that address the
change. When you create or revise a business object, you can associate it with a
change notice that specifies the work plan to approve the changes.
To define business objects to be associated with a change notice, set the
Adc0AssociateWithChangeNotice business object constant to true.

2-12 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

When the Adc0AssociateWithChangeNotice business object constant is set

to true, the change notice that is set for your user session is associated with the
business object.
For information about setting the change notice preference for the user session,
see Defining session settings.

Configuring CAGE and location codes

Configuring CAGE and location codes

Setting constants
• Set the value of the following global constants for regulating the creation of
location codes:
o Fnd0MaintainUniqueLocationCode
Maintains a unique location code for each company location. This is used
when an end user creates a new CompanyLocation business object and
must enter a location code in the Company Location box.
The default value is false. If the value is false, the system creates the new
company location with the entered location code. If the value is true, the
system checks if there is any other company location that exists with same
location code, and if yes, the system displays the following message:
The Location Code already exists. Please choose different Location Code.

o Fnd0AllowSuggestiveLocationCode
Determines if an end user is allowed to enter a location code that does not
exist on any company location when creating a new CompanyLocation
business object. By default, the value of the constant is true. If the value of
this constant is true, and a user enters a new location code to the Company
Location box, the following message is displayed:
The Location Code entered does not exist on any Company Location.
Do you want to continue?

When the user clicks the Yes button, the new location code is saved.
If the value of the constant is false, the end user must select from the list
of existing location codes. If an end user enters a new location code, the
following message is displayed:
The Location Code entered does not exist on any Company Location.
Please enter a valid Location Code.

o Fnd0DisplayLocationCodeLov
Determines if the Location Code box in the User Setting dialog should be
a text box or display a list of values (LOV) with CAGE codes. By default,
the value is set to false, making it a text box. Set it to true to have the
box display a list of values.
For more information about changing the value of a global constant, see the
Business Modeler IDE Guide.

PLM00111 G Aerospace and Defense Solution Guide 2-13

Chapter 2 Configuring Aerospace and Defense

Making the location code visible

To make the location code visible when you create and edit items and item revisions,
modify the fnd0OriginalLocationCode attribute of the item or item revision using
Business Modeler IDE. You can make the attribute visible and mandatory.
For more information, see the Business Modeler IDE Guide.

Hiding the company location assign functionality

You can hide the Assign Company Location functionality from specified groups or
roles using the Command Suppression feature.
For more information about suppressing commands, see the Application
Administration Guide.

Assign company location to users and groups

Administrators can assign company locations to users and groups. When users
are assigned company locations, they only see the company locations that they are
assigned to.
Note Ensure that you have created company locations.
For more information about creating company locations, see Register
company location.

1. From My Teamcenter, choose Tools→Assign Company Location.

The Assign Company Location dialog box is displayed.

2. Select groups or users from the Organization list.

2-14 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

To select users, expand the Group node and the Role node.

3. Select the company location to which you want to assign groups or users from
the Company Location list.
Note You cannot assign multiple groups or users to multiple company
locations. You can assign multiple groups or users to a single company
location or you can assign a single group or user to multiple company
locations.

4. Click the button to assign groups or users to company location.

The Select A Relation dialog box is displayed.

5. In the Select A Relation dialog box, select one of the following relations:
a. True Company Affiliation
Choose this option if the groups or users assigned to the company location
are employees. This relation specifies that a part is created internally.

b. Design Authority Affiliation

Choose this option if the groups or users assigned to the company location
are Original Equipment Manufacturers or external entities. This relation
specifies that a part is created by an external vendor.

6. Click OK.
The Assign Company Location dialog box is displayed.

7. Click OK.
Groups and users are assigned to a company location.

8. To filter what you see in the Company Location list, select the following options
from the list located at the top right of the Asign Company Location dialog box:
a. User and Group
Shows both users and groups in the Company Location list.

b. Group
Shows only groups in the Company Location list.

c. User
Shows only users in the Company Location list.

Note You can hide the Assign Company Location functionality from specified
groups or roles using the Command Suppression feature.
For more information about suppressing commands, see the Application
Administration Guide.

PLM00111 G Aerospace and Defense Solution Guide 2-15

Chapter 2 Configuring Aerospace and Defense

Configuring Aerospace and Defense objects with multifield keys

Multifield keys allow you to create multiple items using the same item ID. Multifield
keys are identifiers assigned to each object to ensure their uniqueness in the
database. Administrators use the MultiFieldKey business object constant to
assign the key definitions to different business object types. Administrators can
add multiple properties to define a key.
The multifield key is composed of a domain name (the name of the business object
type) and a combination of the object’s properties:
domain{properties}
For example, the default multifield key definition for Item business objects is
Item{item_id}. Because children business object types inherit the key definition
from their parent, they belong to the same domain as the parent business object.
You can configure multifield keys that allow end users to create multiple related
items using the same item ID. For example, suppose end users want to refer to a
part and drawing using the same item ID. Previous to Teamcenter 10, you could not
do this because both part and drawing types are children of the item type, and are
both considered items. However, now you can do this by setting up multifield key
definitions per domain or object type. For example, in the case of part and drawing,
the administrator could define the unique key for part business objects and their
children as Part{item_id} and for drawing business objects and their children as
Drawing{item_id}. When these definitions are applied, it results in a unique
key identifier for each instance of an object type in the database, even though the
different object types can share the same item ID.
For more information about multifield keys, see the Business Modeler IDE Guide.

Configuring authorized data access (ADA)

Configuring authorized data access (ADA)

Authorized data access (ADA) is a security solution that complements other
Teamcenter security features, such as Access Manager rules and access control lists
(ACLs). Authorized data access controls sensitive data through the use of data
classification, user clearance, and authorizing documents. When users or groups
attempt to access classified data in Teamcenter, their clearance level is evaluated
against the classification of the object based on Access Manager rules. If the user
or group clearance level is equal to or greater than the classification on the object,
access is granted.
There are three types of licenses for authorized data access:
• IP license
Grants discretionary access to data for a specific user for a specific period of time.
You can configure the rule tree to check for a valid IP license associated with an
object and user. If found, other access checks are bypassed.

• Exclude license
A mechanism for denying users access to data for a specific period of time.

2-16 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

You can configure the rule tree to check for a valid execution license associated
with an object and user. If found, other access checks are bypassed.

• ITAR (International Traffic in Arms) license

Grants access for U.S. nationals outside the United States or foreign nationals
named by an effective Technical Assistance Agreement to access protected
product data, which in the United States could contain technical information
that is restricted by ITAR.

The ADA concepts described in the previous paragraphs assume that data is stored
in and accessed from within the Teamcenter environment. You can also configure
logging and menu suppression (blocking) to be applied when classified data is loaded
in Teamcenter Integration for NX. Logging provides an audit of actions performed on
exporting data, and blocking suppresses NX menus to prevent geometric data from
being exported outside of the NX/Teamcenter environment.
Note In this context, export refers to performing an operation, such as creating
a copy or printing data, that moves the data outside of the Teamcenter
environment.

As a user with an ADA administrator role (IP Admin or ITAR Admin), you use
the ADA License application to create and maintain licenses. Once created, access
is either granted or denied to users and groups by associating the license directly
with the data object.

Basic tasks for configuring and administering authorized data access

for IP data
The following basic tasks must be performed when configuring and administering
authorized data access for intellectual property (IP) data:
• Enable authorized data access.

• Configure logging and blocking in NX.

• Define IP clearance and classification levels.

• Assign users to the IP Admin role and grant IP Admin privileges.

• Assign users to classify data using the IP Classifier role and granting
IP_Classifier privileges.

• Assign clearance levels to users.

• Create intellectual property (IP) licenses.

• Assign classification values to data objects.

• Associate licenses with data objects.

For more information, see the Security Administration Guide and the Authorized
Data Access License Guide.

PLM00111 G Aerospace and Defense Solution Guide 2-17

Chapter 2 Configuring Aerospace and Defense

Basic tasks for configuring and administering authorized data access

for ITAR restricted data
The following basic tasks must be performed when configuring and administering
authorized data access for intellectual property data:
• Enable authorized data access.

• Configure logging and blocking in NX.

• Define ITAR clearance and classification levels.

• Assign users to the ITAR Admin role and grant ITAR Admin privileges.

• Assign users to classify data using the ITAR Classifier role and granting the
ITAR_Classifier privileges.

• Assign clearance levels, geographic location, nationality, and technology transfer

certification dates to users.

• Assign geographic locations to sites.

• Assign nationality to groups.

• Create ITAR licenses.

• Assign government classification values to data objects.

• Associate licenses with data objects.

For more information, see the Security Administration Guide and the Authorized
Data Access License Guide.

Configuring the Multi-Site Collaboration environment

You can use Multi-Site Collaboration to easily share product information across your
entire enterprise. Multi-Site Collaboration allows the exchange of Teamcenter data
objects between databases. Each database should be easily accessible using TCP/IP,
either over the Internet or through your company intranet.
For more information about Multi-Site Collaboration, see the Multi-Site
Collaboration Guide.
In Aerospace and Defense, when the data objects are exchanged between databases,
ensure that the user who is initiating the exchange is the member of the program
whose objects are being exchanged. Also, ensure that a user who belongs to the
DBA group in Teamcenter and has DBA privileges in Teamcenter is running the
Integrated Distributed Services Manager (IDSM) service.
Alternatively, you can also create an Access Manager rule for the program whose
objects are being exchanged using the Access Manager application.
For more information, see Configure the Is Owned By Program rule to support
Aerospace and Defense data exchange.

2-18 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

Note To exchange data objects, the owning group and the organization of the data
object that is being exchanged must be defined at the remote site; that is, the
group hierarchy at both the sites must be similar.
For information about the other points that must be considered when
importing and exporting data, see the Importing and exporting project or
program data in a Multi-Site Collaboration environment.

Configure the Is Owned By Program rule to support Aerospace and

Defense data exchange
Use this procedure to configure the Is Owned By Program rule to grant the
privileges required to exchange Aerospace and Defense data between databases in a
Multi-Site Collaboration environment.
1. Start the Access Manager application.

2. Select the parent tree rule to which the new node will be added.

3. In the Condition box, select Is Owned By Program.

4. Leave the Value box blank.

5. In the ACL Name box, type the ACL name.

6. Click the Create button to the right of the ACL Name box.

7. Click the Save button to the right of the ACL Name box.

8. Click Add to add a new row to the access control entry (ACE) table.

9. Double-click the cell in the Type of Accessor column and select the accessor
as User.

10. Double-click the cell in the ID of Accessor column and choose the ID of the
user who installed Teamcenter.

11. Grant the search, import, export, publish, transfer in, and transfer out privileges
as shown in the following figure:

User

12. Click Save .

13. Select the rule in the rule tree and place the rule between the In Job (true)
and the In Current Program (false) access rules. You can use the Move Up
and Move Down buttons on the toolbar to move the rule up or down
in the rule tree.

PLM00111 G Aerospace and Defense Solution Guide 2-19

Chapter 2 Configuring Aerospace and Defense

14. Click Save .

Importing and exporting project or program data in a Multi-Site

Collaboration environment
The following points should be considered when importing and exporting project or
program data in a Multi-Site Collaboration environment:
• Project and program IDs are case sensitive and must match exactly across sites.
Siemens PLM Software recommends that you duplicate projects and programs
across sites before attempting to share project or program data.

• Users, groups, projects, and programs must be replicated at all sites that share
project or program data. You can use the dsa_util utility to replicate users and
groups. Projects and programs must either be replicated individually, using
the Project or Program application or using the create_project utility, which
enables you to create projects or programs individually based on command line
input, or in batch using input from a text file.

• When an object that is assigned to a project or program is exported, the

explicitly assigned ID of the project or program is exported along with the other
data associated with the object. When that object (replica) is imported at the
receiving site, it is assigned to the project or program with the same ID. If an
imported object is assigned to multiple projects or programs, it is assigned to the
corresponding projects or programs at the importing site.

• When an imported object (replica) is assigned to a project or program, the

associated secondary objects are also assigned to the project or program
according to the propagation rules in effect at the receiving site.

• When a replicated object is imported to a remote site by a

user who is not a privileged team member, the value of the
TC_multi_site_project_member_bypass preference determines whether the
object is assigned to the project or program. If the value of the preference is true,
the replicated object is assigned to the defined project or program upon import.
If the value of the preference is false, the replicated object is not assigned to
the project or program upon import.
Note The TC_multi_site_project_member_bypass preference is not
included in your Teamcenter installation. You must add it to the
database.
For information about adding preferences, see the Rich Client Interface
Guide.

• When a document-centric part (a part that is associated with a document-centric

program) is imported, the corresponding technical document associated with the
part must be present at the importing site.
Note If the corresponding technical document is not found at the importing
site, Teamcenter displays an error message and the part is not imported.
When the corresponding technical document is present at the importing
site, the part is associated with the technical document.

2-20 Aerospace and Defense Solution Guide PLM00111 G

 Configuring Aerospace and Defense

• When an object is exported, Teamcenter checks for the matching owning

organization of the object at the remote site. If no matching owning organization
is found at the remote site, Teamcenter issues an error message and stops the
transfer.

PLM00111 G Aerospace and Defense Solution Guide 2-21

Chapter

3 Defining session settings

PLM00111 G Aerospace and Defense Solution Guide

Chapter

3 Defining session settings

You can define the following user settings for your Teamcenter session:

• Group
A user group is a set of users who have a common set of rules. You can use groups
to consolidate rules. Rules that are common to multiple users can be written for a
group instead of separately for each user. You can assign users to several groups.
Groups are created by administrators in the Organization application. If you do
not specify a group, the default group associated with the user account is used.

• Role
You can write rules that apply to roles without regard to the project, then create
role assignments that link users to the roles within each project. The software
uses the role assignments to control access and messaging.
Roles are created by administrators in the Organization application. If you do
not specify a role, the default role associated with the user account is used.

• Current project or program

If your administrator has specified a default program for you, that program is
displayed when you log on to Teamcenter. This setting allows you to switch
between the programs that you are a member of.

• Volume
Specifies the repository for storing data.

• Commercial And Government Entity Code

You must specify the Commercial And Government Entity (CAGE) code or
location code of the business objects. CAGE code or location code helps to identify
the place from where the business objects are sourced.

• Organization
In the aerospace and defense industry, data must be created within the context
of an organization. Organizations uniquely identify a group of users in an
ISO 6523–compliant format. By default, the organization is set as the group
you specified when you logged on to Teamcenter. If your log on group is not
designated as an organization, or if the group does not belong to a parent
organization, the Organization field is blank.

PLM00111 G Aerospace and Defense Solution Guide 3-1

Chapter 3 Defining session settings

Note o All data creation activities are linked to the organization specified for
your user session. When you create an item, the owning organization
of the item is the organization specified for the user session.

o You can only specify an organization for your user session if your
system is configured to require data to be created in the context of
an organization.

o Setting the organization preference enables you to create data in the

context of an organization to which you do not belong.

o Your default organization is set to the group you specified when

you logged on to Teamcenter. If the group is not designated as an
organization or if the group does not belong to an organization, the
organization preference is blank.

• Application Logging
Specifies the record of logging request to the server.

• Journalling
Specifies the detail records of the application logging and the changes
incorporated.

• Change notice
Specifies the change notices that you have permission to write to.
Note This field is visible only when you have the Change Manager application
installed.

For more information about defining session settings, see the Rich Client Interface
Guide.

3-2 Aerospace and Defense Solution Guide PLM00111 G

Chapter

4 Using CAGE codes and company

location codes

Register company location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Edit company location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Add company code to an item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

PLM00111 G Aerospace and Defense Solution Guide

Chapter

4 Using CAGE codes and company

location codes

Register company location

Note You must first assign a location code to a company. The Aerospace and
Defense application evaluates the Fnd0MaintainUniqueLocationCode
global constant to verify the uniqueness of the location code.
For more information, see Configuring CAGE and location codes.

1. Open My Teamcenter.

2. From the menu bar, chooseFile→New→Other.

3. In the New Business Object dialog box, expand Complete List.

4. Select Company Location and click Next .

5. Define information for the company location, as follows:

Name Specifies the name of the company location.

CAGE Code Specifies the position code assigned by the
Government. This code is unique for each
company location.
Location Type Specifies the type of location code, for example,
CAGE (Commercial And Government Entity),
GLN (Global Location Number), and so on.
Street Specifies the street name where the company
is located.
City Specifies the city where the company is
located.
State / Province Specifies the state or province where the
company is located.
Postal Code Specifies the ZIP code.
Country Specifies the country where the company is
located.
Region Specifies the region where the company is
located.
URL Specifies the company URL.

PLM00111 G Aerospace and Defense Solution Guide 4-1

Chapter 4 Using CAGE codes and company location codes

Description Describes the company. Use a description

that helps to distinguish the purpose of the
company and the nature of its business.
Name Specifies the name of the company.

6. Click Finish.

Edit company location

1. In the Quick Links pane, click Home.

2. In the Home pane, select the company location object that you have created.

3. In the Application pane, click the icon.

4. (Optional) In the Check-Out dialog box, define the following and then click Yes
to continue.

Change ID Specifies the ID of the changed company

location.
Comments Specifies comments about the change ID.

5. In the Application pane, select the Viewer tab to edit the company location
information.
For more information about the description of the fields, see Register company
location.

6. Click Finish.

Add company code to an item

To add a company location to an item during item creation, add the value of the
location code to the Original Location Code field. This option is available in the
Define additional item information dialog box of the New item dialog box.
For more information about creating an item, see the My Teamcenter Guide.

4-2 Aerospace and Defense Solution Guide PLM00111 G

Chapter

5 Working with Aerospace and

Defense objects

Creating Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Create a technical document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Create a part or a commercial part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Create a design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Create a drawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Creating Aerospace and Defense business objects in document-centric
programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Revise Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16

Revising parts and documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Modify Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Delete Aerospace and Defense objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Attaching preferred standard parts to programs . . . . . . . . . . . . . . . . . . . . . . 5-18

Associate preferred standard parts to programs . . . . . . . . . . . . . . . . . . . . . . . 5-19

Remove preferred parts from assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Remove preferred parts from programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

Building an assembly for a document-centric program . . . . . . . . . . . . . . . . . . 5-20

Build an assembly for a document-centric program . . . . . . . . . . . . . . . . . 5-21

PLM00111 G Aerospace and Defense Solution Guide

Chapter

5 Working with Aerospace and

Defense objects

Creating Aerospace and Defense objects

Create a technical document

1. Open My Teamcenter.

2. Choose File→New→Item.

3. In the New Item dialog box, select Technical Document.

4. Define the basic information for the new item, as follows:

In the Naming and Numbering Pattern section:

ID Specifies the naming and the numbering

pattern for the part.
Note The naming and the numbering rules
are set in Business Modeler IDE.
For more information about
configuring naming rules, see
Configuring naming rules.
Revision Specifies the revision pattern of the part.

In the Item Information section:

PLM00111 G Aerospace and Defense Solution Guide 5-1

Chapter 5 Working with Aerospace and Defense objects

ID/Revision - Name Specifies the ID, revision ID, and name of the
part. This is a mandatory field.
Note Click the Assign button to
automatically generate the item
ID and revision identifiers.
The Assign button is active only
if naming rules and automatic
generation have been implemented for
the selected object type.
The ID is based on the numbering
pattern you selected in the Naming
and Numbering Pattern section.
Description Describes the part. Use a description that
helps to distinguish the purpose of the part.

Unit of measure Specifies the metric of the part.

5. Click Next .

6. Define additional item information, as follows:

Category A user defined attribute for classifying the

technical document.
Original CAGE Code Specifies the location code assigned to an item
when it was first created.
Note This box is not available by default.
For information on enabling this box,
see Configuring CAGE and location
codes.
Technical Document category Specifies the category of the technical
document, for example, assembly drawing,
wire list, material specification, and so on.

Title Specifies the title of the technical document.

Author Specifies the author or the originator of

the technical document. The author or the
originator of a document is the person, office,
or designated position responsible for its
creation or issuance.

5-2 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

Subject Specifies the subject of the technical document.

Keywords Specifies a word or phrase used for indexing or

cataloging the technical document.

7. Click Next.

8. (Optional) Define additional item revision information, as follows:

Custodial organization Specifies the name of the organization that has

Name the custody of the technical documents.
Design Level Specifies the conceptual or developmental
design, production prototype or limited
production design, and engineering drawings
required for the production of an item or a
system.
Document Author Specifies the author or the originator of
the technical document. The author or the
originator of a document is the person, office or
designated position responsible for its creation
or issuance.
Document Subject Specifies the theme of the technical document.

Document Title Specifies the heading of the technical document.

Undimensioned Specifies whether a drawing defines the

undimensioned flat patterns for parts.

Title Specifies the title of the technical document.

Author Specifies the author or the originator of

the technical document. The author or the
originator of a document is the person, office, or
designated position responsible for its creation
or issuance.
Subject Specifies the subject of the technical document.

PLM00111 G Aerospace and Defense Solution Guide 5-3

Chapter 5 Working with Aerospace and Defense objects

Keywords Specifies a word or phrase used for indexing or

cataloging the technical document.

9. Click Next to create an alternate identifier, if enabled.

10. (Optional) Select the program that you want to assign from the list of programs.
Note You can assign objects to programs only if you are a privileged program
team member.

11. Select one or more programs from the Programs for Selection list.

12. Click the right-arrow button to move the programs to the Selected Programs
list.

13. Click Next.

14. (Optional) Define the display options to create a new Aerospace and Defense
technical document in the selected folder in My Teamcenter, as follows:

Show as a new root Specifies that the newly created object is

opened as a root object. It is not pasted to
the selected item. If you do not select this
option, the new item is pasted as the child of
the selected item.
Use item identifier as default Specifies item identifier as a default display
display object.
Use revision identifier as Specifies that the alternate identifier for the
default display item is the default display object.
Check-Out Item Revision on Specifies that the item revision is checked out
Create automatically after creation.
Note You must check out the item revision
before you modify it.

15. Click Finish.

Create a part or a commercial part

1. Open My Teamcenter.

2. Choose File→New→Part.

3. In the New Part dialog box:

a. Choose Part for creating a part.

b. Choose Commercial Part for creating a commercial part.

4. Click Next.

5-4 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

5. Define basic information for a part, as follows:

In the Naming and Numbering Pattern section:

ID Specifies the naming and the numbering

pattern for the part.
Note The naming and the numbering rules
are set in Business Modeler IDE.
For more information about
configuring naming rules, see
Configuring naming rules.
Revision Specifies the revision pattern of the part.

In the Part Information section:

ID/Revision - Name Specifies the ID, revision ID, and name of the
part. This is a mandatory field.
Note Click the Assign button to
automatically generate the item
ID and revision identifiers.
The Assign button is active only
if naming rules and automatic
generation have been implemented for
the selected object type.
The ID is based on the numbering
pattern you selected in the Naming
and Numbering Pattern section.
Description Describes the part. Use a description that
helps to distinguish the purpose of the part.

Unit of measure Specifies the metric of the part.

6. Click Next.

PLM00111 G Aerospace and Defense Solution Guide 5-5

Chapter 5 Working with Aerospace and Defense objects

Note The following happens when you click Next, Back or the Finish button:
If you have enabled automatic selection and multifield keys for technical
documents and if there are multiple technical documents matching the
criterion:
• You see the select Unique Source Document dialog box. This dialog
box displays the list of technical documents matching the criteria
you specified for technical documents.

• To select a technical document, double-click the row that contains

the technical document you want.

• You can change the technical document in the Define additional part
information pane.

7. Define additional part information, as follows:

Original CAGE Code Specifies the location code assigned to an item

when it was first created.
Note This box is not available by default.
For information on enabling this box,
see Configuring CAGE and location
codes.

Part Category Specifies the category of part for the program,

for example, supplier part, government
furnished equipment, or military standard
part.
Source Document category Specifies the user-defined attribute for
classifying document items.

Source Document ID Specifies the unique identifier of the document

associated with the part.

Source Document Revision Specifies the revision of the document

associated with the part.

Source Technical Document Specifies the category of the technical

Category document, for example, assembly drawing,
wire list, material specification, and so on.

5-6 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

Design Required Specifies whether a CAD design is required for

the part. The Aerospace and Defense solution
validates the designs for the part. This
property is usually selected for consumables
that have a representation in the parts list
but no geometric representation. For example,
glue, paint, grease, and so on.

Note You must specify the source document details and the attribute values
before you create the part in document-centric programs.
Enter the values for source document properties in the language
specified by the master locale. You can copy master locale values from the
respective source document properties using the Localization button .

8. Click Next.
Note The following happens when you click Next, Back or the Finish button
and you have configured multifield keys for technical documents.
If there are multiple technical documents matching the criteria
for technical documents you specified in the Define additional part
information dialog box:
• You see the select Unique Source Document dialog box. This dialog
box displays the list of technical documents matching the criteria
you specified for technical documents.

• To select a technical document, double-click the row that contains

the technical document you want.

9. (Optional) Define additional part revision information, as follows:

Make/Buy Specifies whether the part is manufactured

internally or sourced from a vendor.

10. Click Next to create an alternate identifier, if enabled.

11. (Optional) Select the program that you want to assign from the list of programs.
Note You can assign objects to programs only if you are a privileged program
team member.

12. Select one or more programs from the Programs for Selection list.

13. Click the right-arrow button to move the programs to the Selected Programs
list.

14. Click Next.

15. (Optional) Define the display options to create a new Aerospace and Defense
technical document in the selected folder in My Teamcenter, as follows:

PLM00111 G Aerospace and Defense Solution Guide 5-7

Chapter 5 Working with Aerospace and Defense objects

Show as a new root Specifies that the newly created object is

opened as a root object. It is not pasted to
the selected item. If you do not select this
option, the new item is pasted as the child of
the selected item.
Use item identifier as default Specifies the item identifier as a default
display display object.
Use revision identifier as Specifies that the alternate identifier for the
default display item is the default display object.
Check-Out Item Revision on Specifies that the item revision is checked out
Create automatically after creation.
Note You must check out the item revision
before you modify it.

16. Click Finish.

Create a design
1. Open My Teamcenter.

2. Choose File→New→Design.

3. In the New Design dialog box, select Design.

4. Define basic information for a new design, as follows:

In the Naming and Numbering Pattern section:

ID Specifies the naming and the numbering

pattern for the part.
Note The naming and the numbering rules
are set in Business Modeler IDE.
For more information about
configuring naming rules, see
Configuring naming rules.
Revision Specifies the revision pattern of the part.

In the Design Information section:

5-8 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

ID/Revision - Name Specifies the ID, revision ID, and name of the
part. This is a mandatory field.
Note Click the Assign button to
automatically generate the item
ID and revision identifiers.
The Assign button is active only
if naming rules and automatic
generation have been implemented for
the selected object type.
The ID is based on the numbering
pattern you selected in the Naming
and Numbering Pattern section.
Description Describes the part. Use a description that
helps to distinguish the purpose of the part.

Unit of measure Specifies the metric of the part.

5. Click Next .
Note The following happens when you click Next, Back or the Finish button:
If you have enabled automatic selection and multifield keys for technical
documents and if there are multiple technical documents matching the
criterion:
• You see the select Unique Source Document dialog box. This dialog
box displays the list of technical documents matching the criteria
you specified for technical documents.

• To select a technical document, double-click the row that contains

the technical document you want.

• You can change the technical document in the Define additional part
information pane.

6. Define the additional design information, as follows:

Design Category Specifies the category of part for the program,

for example, supplier part, government
furnished equipment, or military standard
part.

PLM00111 G Aerospace and Defense Solution Guide 5-9

Chapter 5 Working with Aerospace and Defense objects

Original CAGE Code Specifies the location code assigned to an item

when it was first created.
Note This box is not available by default.
For information on enabling this box,
see Configuring CAGE and location
codes.
Source Document category Specifies the user-defined attribute for
classifying document items.

Source Document ID Specifies the unique identifier of the document

associated with the design.

Source Document Revision Specifies the revision of the source document

that must be used to create the design.

Source Technical Document Specifies the category of the technical

Category document, for example, assembly drawing,
wire list, material specification, and so on.

Note You must specify the source document details and the attribute values
before you create the design in document-centric programs.
Enter the values for source document properties in the language
specified by the master locale. You can copy master locale values from the
respective source document properties using the Localization button .

7. Click Next.
Note The following happens when you click Next, Back or the Finish button
and you have configured multifield keys for technical documents.
If there are multiple technical documents matching the criteria
for technical documents you specified in the Define additional part
information dialog box:
• You see the select Unique Source Document dialog box. This dialog
box displays the list of technical documents matching the criteria
you specified for technical documents.

• To select a technical document, double-click the row that contains

the technical document you want.

8. (Optional) Define additional design revision information, as follows:

Make/Buy Specifies whether the part is manufactured

internally or sourced from a vendor.

9. Click Next to create an alternate identifier, if enabled.

5-10 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

10. (Optional) Select the program that you want to assign from the list of programs.
Note You can assign objects to programs only if you are a privileged program
team member.

11. Select one or more programs from the Programs for Selection list.

12. Click the right-arrow button to move the programs to the Selected Programs
list.

13. Click Next.

14. (Optional) Define the display options to create a new Aerospace and Defense
technical document in the selected folder in My Teamcenter, as follows:

Show as a new root Specifies that the newly created object is

opened as a root object. It is not pasted to
the selected item. If you do not select this
option, the new item is pasted as the child of
the selected item.
Use item identifier as default Specifies item identifier as a default display
display object.
Use revision identifier as Specifies that the alternate identifier for the
default display item is the default display object.
Check-Out Item Revision on Specifies that the item revision is checked out
Create automatically after creation.
Note You must check out the item revision
before you modify it.

15. Click Finish.

Create a drawing
While creating a drawing, you must mention the source document number. If there
are multiple source documents available with the same number, provide additional
information, such as source document category, and source technical document
category.
1. Open My Teamcenter.

2. Choose File→New→Drawing.

3. Define basic information for the new item, as follows:

In the Naming and Numbering Pattern section:

PLM00111 G Aerospace and Defense Solution Guide 5-11

Chapter 5 Working with Aerospace and Defense objects

ID Specifies the naming and the numbering

pattern for the part.
Note The naming and the numbering rules
are set in Business Modeler IDE.
For more information about
configuring naming rules, see
Configuring naming rules.
Revision Specifies the revision pattern of the part.

In the Item Information section:

ID/Revision - Name Specifies the ID, revision ID, and name of the
part. This is a mandatory field.
Note Click the Assign button to
automatically generate the item
ID and revision identifiers.
The Assign button is active only
if naming rules and automatic
generation have been implemented for
the selected object type.
The ID is based on the numbering
pattern you selected in the Naming
and Numbering Pattern section.
Description Describes the part. Use a description that
helps to distinguish the purpose of the part.

Unit of measure Specifies the metric of the part.

4. Click Next .
Note The following happens when you click Next, Back or the Finish button:
If you have enabled automatic selection and multifield keys for technical
documents and if there are multiple technical documents matching the
criterion:
• You see the select Unique Source Document dialog box. This dialog
box displays the list of technical documents matching the criteria
you specified for technical documents.

• To select a technical document, double-click the row that contains

the technical document you want.

• You can change the technical document in the Define additional part
information pane.

5-12 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

5. Define the additional item information, as follows:

Original CAGE Code Specifies the location code assigned to an item

when it was first created.
Note This box is not available by default.
For information on enabling this box,
see Configuring CAGE and location
codes.
Source Document category Specifies the user-defined attribute for
classifying document items.

Source Document ID Specifies the ID of the source document.

Source Document Revision Specifies the revision of the source document

that must be used to create the drawing.

Source Technical Document Specifies the category of the technical

Category document, for example, assembly drawing,
wire list, material specification, and so on.

Note In document-centric programs, you must specify the source document

details and the attribute values before you create the drawing.
Values for source document properties must be entered in the language
specified by the master locale. You can copy master locale values from the
respective source document properties using the Localization button .

6. Click Next.
Note The following happens when you click Next, Back or the Finish button
and you have configured multifield keys for technical documents.
If there are multiple technical documents matching the criteria
for technical documents you specified in the Define additional part
information dialog box:
• You see the select Unique Source Document dialog box. This dialog
box displays the list of technical documents matching the criteria
you specified for technical documents.

• To select a technical document, double-click the row that contains

the technical document you want.

7. (Optional) Define additional item revision information, as follows:

PLM00111 G Aerospace and Defense Solution Guide 5-13

Chapter 5 Working with Aerospace and Defense objects

Drawing Type Specifies the format of the drawing. For

example, PDF, Microsoft Word, and so on.
Drawing can be manufacturing drawing,
schematic drawing, and so on.

8. Click Next to create an alternate identifier, if enabled.

9. (Optional) Select the program that you want to assign from the list of programs.
Note You can assign objects to programs only if you are a privileged program
team member.

10. Select one or more programs from the Programs for Selection list.

11. Click the right-arrow button, ( ) to move the programs to the Selected Programs
list.

12. Click Next.

13. (Optional) Define the display options to create a new Aerospace and Defense
technical document in the selected folder in My Teamcenter, as follows:

Show as a new root Specifies that the newly created object is

opened as a root object. It is not pasted to
the selected item. If you do not select this
option, the new item is pasted as the child of
the selected item.
Use item identifier as default Specifies item identifier as a default display
display object.
Use revision identifier as Specifies that the alternate identifier for the
default display item is the default display object.
Check-Out Item Revision on Specifies that the item revision is checked out
Create automatically after creation.
Note You must check out the item revision
before you modify it.

14. Click Finish.

Creating Aerospace and Defense business objects in

document-centric programs
Document-centric programs require you to specify a source document while creating
Aerospace and Defense business objects such as parts, designs, and drawings.
When creating a business object in a document-centric program, you must fill the
Source Document property of the business object with the document number of
an existing document.
In document-centric programs, when a part is created, the part is associated with
the technical document through the ADS_Lists_PartRevisions relation. When a

5-14 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

drawing is created, the drawing is associated with the technical document through
the ADS_Lists_DrawingRevisions relation.
A single source document can list multiple parts. A document-centric program
manages parts list documents that are revised independently of the part.
The behavior of the source technical document varies during creation of Aerospace
and Defense business objects in a document-centric program when:
• Automatic selection of source technical documents is enabled and automatic
creation of source technical documents is disabled.
If you do not specify the source document ID, the system extracts the document
ID from the item ID.
However, if you specify both the source document ID and source document
details, the system uses the details provided in the Enter additional part/design
information pane to select the source technical document.
Note The string before the last hyphen in the item ID is the ID of the source
technical document.
If two or more technical documents exist with the same ID, you must
provide specific details about the technical document by entering the
source document category, and revision ID.
The system displays an error message if:
o The source document details are not provided.

o The details provided do not correspond to an existing technical

document.

• Automatic creation of source technical document is enabled and automatic

selection of source technical document is disabled.
If you provide the source document details, such as the source document category,
and source document revision when you create a part, design, or drawing, the
system automatically creates a new technical document corresponding to the
source document details and associates it with the new business object through
an appropriate relation.
Automatic creation of technical document works only after the system ensures
that:

o An existing document cannot be selected from the source document

ID provided as a part of the part, design or drawing ID in the Enter
part/design/drawing information pane because automatic selection is
disabled.

o The details provided in the Enter additional part/design/drawing information

pane does not match any of the existing technical documents.

• Both automatic selection and automatic creation of source technical document

are enabled.
When you specify the source document ID while creating Aerospace and Defense
business objects, the system automatically selects the technical document
corresponding to the source document ID. You do not need to manually specify

PLM00111 G Aerospace and Defense Solution Guide 5-15

Chapter 5 Working with Aerospace and Defense objects

the source document details. The new business object is associated to the
automatically selected technical document through an appropriate relation.
However, if you specify both the source document ID and source document
details, the system uses the details provided to select the source technical
document.
If the given source document details do not match any of the existing technical
documents, the system automatically creates a new technical document based
on the details you provided when creating the object and associates it with the
new business object through an appropriate relation.
Note If you do not specify the document ID, Teamcenter creates the document
ID based on the ID of the part, design, or drawing.

• Both automatic selection and automatic creation are disabled.

When you specify the source document details, the system searches for the
corresponding source document and updates the other attributes, such as the
source document category, and source document revision. The selected technical
document is associated to the new business object through an appropriate
relation.
When you specify details about the source document and the details do not
match any of the existing source documents, the system fails to create the
business object because automatic creation of source technical document is
disabled and displays an error message.

Revise Aerospace and Defense objects

1. Open My Teamcenter.

2. Select the Aerospace and Defense business object item revision that you want to
revise and choose File→Revise.
The Revise dialog box appears.

3. In the Define the basic information for the new item revision pane, type the
name of the new revision.
The system generates a new revision ID based on the existing one.

4. Click Next or click the Enter Additional Item Revision Information link in the
left pane of the Revise dialog box.
The Define additional item revision information pane appears.

5. (Optional) Type the title, author, subject, and keywords in the Define additional
item information pane.

6. Click Next or click the Define Attached Objects link in the left pane of the
Revise dialog box.
The Define attached objects pane displays the source revision and attachments
and the destination revision and attachments. By default, all objects are copied
forward to the new (destination) revision.

5-16 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

7. (Optional) In the left pane of the Revise dialog box, click the Assign to Programs
link.

8. (Optional) Assign the new revision to a different project or program.

9. (Optional) Click the Define Options link and select the appropriate open, display,
and checkout options.

10. Click Finish.

Note When a business object that must be associated with a change notice is
revised, all revision activities on the business object are associated with the
change notice that is set as the preferred change notice for your user session.
For information about setting the change notice for a user session, see
Defining session settings.

Revising parts and documents

In a document-centric program, items or item revisions are associated with each
other through appropriate relations. Revision behavior of associated parts and
documents can be specified by configuring the deep copy rules for the relations in the
Business Modeler IDE.
Document revisions and part revisions are associated through the
ADS_Lists_PartRevisions relation. Consider the following revision behaviors
before revising associated parts and documents:
• Both a part and its associated source technical document can be revised
independently of each other.

• A technical document item revision whose item is associated to a part or part

revision can be revised independently of the part.

• When revising a part revision that has an associated technical document item,
the relation with the previous revision of the part is deleted and only the new
revision of the part is carried forward.

• When revising a technical document item revision that has associated technical
document items, the associations are carried forward to the new revision.

Modify Aerospace and Defense objects

1. Open My Teamcenter.

2. Select the Aerospace and Defense object that you want to modify and choose
View→Properties or right-click the object and choose Properties.
The Properties dialog box appears.

3. Click the Check out and Edit button.

The CheckOut dialog box appears.

4. In the Change ID box, type a change ID.

PLM00111 G Aerospace and Defense Solution Guide 5-17

Chapter 5 Working with Aerospace and Defense objects

5. (Optional) Type comments about the change in the Comment box.

6. Click Yes to confirm checkout.

The Edit Properties dialog box appears.

7. Type the values in the Object, Name, and Description fields.

8. Verify the Owner, Group ID, and Last modified user information and click Save.

9. Click Check-In to check in the modified item.

10. Click Yes to confirm checkin.

The existing Aerospace and Defense object is modified.

Delete Aerospace and Defense objects

Note You cannot delete a business object if it is referenced by other objects. For
example, if an ADS part is associated with a source technical document
through the ADS_Lists_PartsRevisions relation in a document-centric
program, it cannot be deleted. You must first select the part revision
displayed under the ADS_Lists_PartsRevisions relation and click the
button on the toolbar to remove the part from the relation. The part is now
independent of the technical document and can be deleted.

1. Open My Teamcenter.

2. Select the ADS item business object that you want to delete.

3. Choose Edit→Delete, or click .

The Confirmation dialog box appears.

4. Click Yes to confirm deletion.

Attaching preferred standard parts to programs

To add a preferred standard part to a program:
1. Configure an item business object as a preferred standard part for the program.
For more information, see Configuring standard and preferred standard parts.
Note You must be an administrator or a user with DBA privileges to enable an
item business object as a preferred standard part.

2. Create the item business object that has been configured as a preferred standard
part.
• For more information about creating an item, see the My Teamcenter Guide.

5-18 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

• For more information about creating Aerospace and Defense objects, see
Creating Aerospace and Defense objects.

3. Associate the preferred standard part with the program.

For more information, see Associate preferred standard parts to programs.

Associate preferred standard parts to programs

1. Open My Teamcenter.

2. Select the standard part and choose Edit→Copy.

3. Select the program to which you want to attach the preferred standard part.
Note
You can search for a program by clicking the Search button on the My
Teamcenter toolbar.

4. Expand the program tree in the Search Result pane and navigate to the
TC_Program_Preferred_Items relation.

5. Right-click the TC_Program_Preferred_Items relation and click Paste.

The preferred standard part is attached to the program.

Remove preferred parts from assemblies

1. Open My Teamcenter.

2. Select the preferred part.

Note You can search for the preferred part by clicking the Search button
on the toolbar.

3. Double-click the preferred part to open it in the Impact Analysis view.

The Impact Analysis pane displays the assemblies that use the selected
preferred part.

4. Right-click the assembly and choose Send to→Structure Manager.

The assembly appears in the Structure Manager window.

5. Select the preferred part and click the Remove a Line button on the toolbar.
Note Ensure that you remove the preferred part from all the assemblies
that use it.

6. Choose File→Save to save the changes in the Structure Manager window.

PLM00111 G Aerospace and Defense Solution Guide 5-19

Chapter 5 Working with Aerospace and Defense objects

Remove preferred parts from programs

1. Open My Teamcenter.

2. Select the program that uses the preferred part.

Note
You can search for the program by clicking the Search button on
the toolbar.

3. Expand the program tree and navigate to the Tc_Program_Preferred_Items

relation.

4. Select the preferred part that appears under the Tc_Program_Preferred_Items

relation and click or choose Edit→Cut.
Note Ensure that you cut the relation in all the programs that use the
preferred part.

Building an assembly for a document-centric program

You can add parts, components, and other assemblies to build a new assembly in your
current (active) program. In document-centric programs, assemblies can consist of:
• ADS parts or designs belonging to the same source document as that of the
assembly.

• Foreign components. ADS parts or designs that belong to a different source

document but not to the assembly’s source document are considered to be foreign
components.
The foreign components are related to the assembly’s source technical document
through the ADS_Lists_Parts relation.

The Aerospace and Defense solution template helps you build an assembly by:
• Automatically identifying foreign components when they are added to the
assembly and allowing them to be associated with the assembly’s source
technical document revision through the ADS_Lists_Parts relation.

• Allowing a single component to be associated with multiple assemblies belonging

to the same source document through a single relation (ADS_Lists_Parts). You
can remove the part or design from one assembly without having to remove the
relation that exists until you remove the part from all the assemblies.

5-20 Aerospace and Defense Solution Guide PLM00111 G

 Working with Aerospace and Defense objects

Build an assembly for a document-centric program

Note An assembly can include multiple parts. You can copy the parts that you
want to include in the new assembly from the business objects list in My
Teamcenter and paste them in the assembly in the Structure Manager.
You must paste all the components on the first component that was sent to
the Structure Manager and not on any of the components pasted under
the first component in the assembly.
The system automatically identifies the first component’s source technical
document as the assembly’s source technical document and associates
the foreign components to the source technical document through the
ADS_Lists_Parts relation.

1. Open My Teamcenter.

2. Right-click the first component to be added to the assembly and choose Send
to→Structure Manager.
The Structure Manager opens and displays the first component. This component
is considered to be the parent component in the assembly.

3. Switch to My Teamcenter, select the second component that you want to include
in the new assembly under the parent component, and choose Edit→Copy.

4. Switch to Structure Manager, select the parent component of the assembly, and
choose Edit→Paste or right-click the parent component and choose Paste.
The second component is added to the assembly in the Structure Manager.

5. Choose File→Save to save the changes in the Structure Manager window.

The new assembly is saved as BOM view revisions in the source technical
document in My Teamcenter.

PLM00111 G Aerospace and Defense Solution Guide 5-21

Chapter

6 Generate part-centric parts

list reports

PLM00111 G Aerospace and Defense Solution Guide

Chapter

6 Generate part-centric parts

list reports

1. Open My Teamcenter.

2. Right-click the assembly for which you want to generate the part-centric parts
list report and choose Send To→Structure Manager.

3. (Optional) Configure the revision rule and effectivity for the assembly, as
required.

4. Open the Structure Manager from the left pane of the Favorites view in My
Teamcenter.
The selected assembly appears in the BOM line view in the Structure Manager.

5. In the BOM line view, select the assembly.

6. Choose File→Print to generate the parts list report. Select the output contents
for the report.
The report appears in the report pane.
Note The report contains:
• The assembly from which the report is generated.

• The parts in the first level of the product structure.

• The creation date of the parts list report.

• The part number, revision, and sequence of the assembly that the
part-centric parts list report is created for.

The following details are also available for each component and
subassembly:
• Find number

• Part number

• Nomenclature

• Quantity

PLM00111 G Aerospace and Defense Solution Guide 6-1

Chapter 6 Generate part-centric parts list reports

• Remark

The report is available in plain text, XML, and HTML.

6-2 Aerospace and Defense Solution Guide PLM00111 G

Chapter

7 Working with notes

Working with standard notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Basic concepts about standard notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Create a standard note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Specify standard note text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Attach a standard note to an item or item revision . . . . . . . . . . . . . . . . . . 7-5
View parametric values in standard notes . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Revise a standard note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Replace a standard note revision with another revision . . . . . . . . . . . . . . 7-8
Validate whether a note is qualified for a technical document . . . . . . . . . . 7-8

Working with custom notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Basic concepts about custom notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Create a custom note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Add or edit custom note text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Attach a custom note to an item or item revision . . . . . . . . . . . . . . . . . . . 7-12
View and edit a custom note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
Revise a custom note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

PLM00111 G Aerospace and Defense Solution Guide

Chapter

7 Working with notes

Working with standard notes

Basic concepts about standard notes

Standard notes represent the notes established by the Standards Engineering
group that conform to the design practices of a program. Standard notes are often
categorized and maintained in a library for use by design engineers in the creation
of parts lists.
For more information about categorizing standard notes, see the Classification Guide
and the Classification Administration Guide.
The following concepts apply to standard notes:
• Standard notes specify parametric variable values that designers select when
attaching the note to an item or an item revision.

• Standard notes are associated with items, such as parts or documents, through
the Standard Notes Lists relation where the part or document revision is the
primary object and the standard note or standard note revision is the secondary
object.

• The parameters for the note are specified in the Note Text property of the note
revision.
Note Text cannot be modified after it is saved. You must create a new revision
of the standard note and make changes to the Note Text property of
the new revision.

• The text of the note revision contains text, parameters, and applicable values
using the syntax shown below.
text [parameter name: parametric value1 delimiter parametric
value2 delimiter... parametric value n]

Example Round all sharp corners to [Radius: 0.4, 0.5, 0.6] inch
and heat treat to [Temperature: 200, 220, 230] degrees Fahrenheit.

• The default delimiter for parameters in the note text is a comma (,). However,
your Teamcenter administrator can configure the delimiter to use a different
character.
For more information, see Setting the delimiter that separates parameters in
standard note text.

PLM00111 G Aerospace and Defense Solution Guide 7-1

Chapter 7 Working with notes

• When a standard note is created, a Standard Note Text dataset is created that
contains the text. The dataset is attached to the standard note revision.
Note You cannot delete the dataset or detach the dataset from the standard
note revision.

• Standard notes are used to associate parts with documents.

• Standard notes and standard note revisions can be related to multiple items
or item revisions.

• You can export parameters and parametric values of standard notes using the
Export to Excelor tcxml export feature only.
For more information about exporting to excel, see the Systems Engineering
Guide.
For more information about exporting to tcxml, see the PLM XML/TC XML
Export Import Administration Guide.

• You can export parameters and parametric values of standard notes using the
Export to Excel or tcxml export feature only.
For more information about exporting to excel, see the Systems Engineering
Guide.
For more information about exporting to tcxml, see the PLM XML/TC XML
Export Import Administration Guide.

• Only a single revision of a standard note can be attached to an item or item

revision. By default, you cannot attach multiple revisions of the same note to an
item or item revision.
Note Your Teamcenter administrator can configure the system to
allow multiple revisions of a standard note to be attached
to an item or item revision by setting the value of the
AllowMultipleRevisionsofStdNotes global constant to true.

Create a standard note

Note To create standard notes, you must have DBA privileges with administrative
bypass set, or you must fill a role that your Teamcenter administrator has
designated as having standard note creation privileges.
For more information, see Configuring who can create standard notes.

1. Open My Teamcenter.

2. Choose File→New→Item.
The New Item dialog box appears.

3. In the New Item dialog box, select the Standard Note item type.

4. Click Next.
The system displays the Define basic information for new item pane.

7-2 Aerospace and Defense Solution Guide PLM00111 G

 Working with notes

5. Type an item ID, revision ID, and name for the standard note, or click Assign to
automatically generate the item ID and revision identifiers.
Note The Assign button is active only if naming rules and automatic
generation are implemented.

6. (Optional) Type a description of the standard note and select a unit of measure.

7. Click Next.
The Define additional item information pane appears.

8. In the Note Category box, choose a category for the standard note.

9. (Optional) Enter values for the note attributes.

10. Click Next.

The Define additional item revision information pane appears.

11. (Optional) Enter values for the revision attributes.

12. In the left pane of the New Item dialog box, click the Assign to Programs link.
The system displays the list of programs to which the standard note can be
assigned.
Note You can assign objects to programs only if you are a privileged program
team member.

13. (Optional) Select one or more programs from the Programs for Selection list and
move them to the Selected Program list.

14. (Optional) Click Next or click the Define Options link in the left pane of the
New Item dialog box.

15. (Optional) Select open, display, and checkout options.

16. Click Finish.

A new standard note is created in the selected folder in My Teamcenter. It
consists of a:

• Standard note master form

• Standard note revision

• Standard note revision master form

• Standard note text dataset

PLM00111 G Aerospace and Defense Solution Guide 7-3

Chapter 7 Working with notes

Specify standard note text

Note To specify standard note text, you must have DBA privileges with
administrative bypass set, or you must fill a role that your Teamcenter
administrator has designated as having standard note definition privileges.
For more information, see Configuring who can create standard notes.

1. Open My Teamcenter.

2. Right-click the standard note revision and choose Properties. Alternatively,

select the standard note revision and choose View → Properties.
Note You cannot double-click the note text dataset to open it. Although the
note text is stored in the dataset, you must enter the data in the note
revision properties.

The Properties dialog box appears.

3. Click the Check-Out and Edit button.

The Check-Out dialog box appears.

4. In the Change ID box, type the change ID.

5. In the Comments box, type notes for checkout.

6. Click Yes.
The Edit Properties dialog box appears.

7. Click the All link in the Edit Properties dialog box, and scroll to the Note Text
box.

8. In the Note Text box, type the note using the following syntax:
text [parameter name: parametric value1 delimiter parametric
value2 delimiter ..... parametric value n]

7-4 Aerospace and Defense Solution Guide PLM00111 G

 Working with notes

Example Round all sharp corners to [Radius: 0.01, 0.02, 0.03] inches
and heat treat to [Temperature: 100, 120, 130] degrees Fahrenheit.

Note The delimiter used when specifying parametric values is defined by your
Teamcenter administrator. The default delimiter is a comma (,).

9. Click Save.
Note You cannot modify the text after it has been saved. To update
parameters, you must create a new revision of the standard note.

10. Click the Check-In button.

The Check-In dialog box appears.

11. Click Yes.

Attach a standard note to an item or item revision

Note You do not need DBA privileges or special role access to attach a standard
note to an item or item revision.

1. Open My Teamcenter.

2. Right-click the standard note or the standard note revision that you want to
attach and choose Copy. Alternatively, select the standard note and choose
Edit → Copy.

3. Select the destination item or item revision and choose Edit → Attach
Requirements/Notes → Parametric Requirement.
The Input Parametric Values dialog box displays the parameters and values
defined for the note.

4. Choose values for the parameters.

5. (Optional) Select the Flag Note option.

6. Click OK.
The standard note revision is attached to the selected object (item or item
revision) through the Standard Notes Lists relation.

PLM00111 G Aerospace and Defense Solution Guide 7-5

Chapter 7 Working with notes

Note If the note is not visible under the item or item revision to which it is
attached, you must specify Standard Notes Lists as a shown relation for
the item and item revision. To do this:
1. Choose Edit→Options.

2. Expand the Options tree and expand the General folder.

3. Click the Item or Item Revision node.

4. In the General options tab, choose Standard Notes Lists from the
Available Relations list.

5. Click to move it to the Shown Relations list.

6. Click OK.

View parametric values in standard notes

To view the parametric values in a standard note which is attached to an item or
item revision:
1. In My Teamcenter, select the standard note revision and choose Window→Show
View→Other.

2. In the Show View dialog box, expand the Teamcenter navigation tree and select
MS Word.

3. Click OK.
You can see the parametric values of the standard note in a new view.

Revise a standard note

To modify the data associated with a standard note, you must first create a new
revision of the standard note.
1. Open My Teamcenter.

2. Select the standard note revision that you want to revise and choose
File→Revise.
The Revise dialog box appears.

3. (Optional) In the Define the basic information for the new item revision pane,
type the name of the new revision.

4. (Optional) Type a description of the revision and choose a unit of measure for
the revision.

5. Click Next.
The Define additional item revision information pane is displayed.

6. (Optional) Enter values for the note revision attributes.

7-6 Aerospace and Defense Solution Guide PLM00111 G

 Working with notes

7. Click Next.
The Define attached objects pane displays the source revision and attachments
and the destination revision and attachments of the destination revision. By
default, all objects are copied forward to the new (destination) revision.

8. (Optional) Choose copy options for the objects related to the source revision by
clicking the icon to the right of the object in the tree.

Don’t Copy
Allows you to selectively copy objects from one revision to
another. Objects that are designated as Don’t Copy appear
with a line through them in the Destination tree.
Copy as Object
Creates a new object of the same type and relation to the
parent object. Objects created by this method are totally
independent of the parent object. Therefore, any changes to
the copied object are not reflected in the original object.
Copied objects appear in bold in the Destination tree and
can be renamed.
Copy as Reference
Copies the object as a reference to the original object. All
changes to the reference copy affect the original object. The
names of attachments that are copied as references cannot
be modified.

9. Click Next.
The Select projects or programs that you want to assign new object to pane
is displayed.

10. (Optional) Assign the new revision to a different project or program.

11. Click Next.

The Select open option and alternate id display option pane is displayed.

12. (Optional) Set the open, display, or checkout option for the new revision.

13. Click Finish.

The new revision is created as a copy of the previous revision object. The new
revision is independent of the source revision. Modifications to the new revision
are not reflected in the source revision, which allows you to edit the note text
for each revision.

14. Specify the note data.

For more information, see Specify standard note text.

PLM00111 G Aerospace and Defense Solution Guide 7-7

Chapter 7 Working with notes

Replace a standard note revision with another revision

By default, only one revision of a standard note can be associated with an item or
item revision. However, you can replace an existing note with a new revision of
the note.
1. Open My Teamcenter.

2. Right-click the revision of the standard note that will replace the revision
attached to the item or item revision, and choose Copy.

3. Expand the item or item revision and select the standard note revision that you
want to replace.

4. Choose Edit→ Replace ParametricRequirement Revision.

If there are parametric values defined for the note, the Input Parametric Values
dialog box appears.

5. Choose values for the parameters.

6. (Optional) Select the Flag Note option.

7. Click OK.
The standard note revision attached to the item or item revision is replaced by
the new revision of the note.

Validate whether a note is qualified for a technical document

When working in document-centric programs, designers are required to identify the
notes that are applicable to various parts from among the qualified standard notes
for their technical document.
To validate a note:
1. Open My Teamcenter.

2. Copy the standard note or the standard note revision.

3. Select the technical document revision and choose Edit → Attach

Requirements/Notes → Parametric Requirement.

4. Expand the technical document revision to which the standard note is attached
and expand the appropriate relations folder. For example, for an ADS part,
expand the ADS_Lists_PartRevisions folder.

5. Right-click the corresponding item revision (ADS part revision, ADS drawing
revision, or ADS design revision) and click Properties on Relation.
Note If you chose the ADS_Lists_PartRevisions in step 4, right-click the
ADS part revision.

The Properties on Relations dialog box appears.

6. In the Properties on Relations dialog box, click the Expand to Modify button
adjacent to the Notes box.

7-8 Aerospace and Defense Solution Guide PLM00111 G

 Working with notes

7. Click the Add objects from Clipboard button.

The standard note is pasted in the Notes box.

8. Click Apply.

9. Click OK.
The system verifies if the note that is pasted in the Notes box is associated with
the technical document. If the note is not associated with the technical document
revision, an error message is displayed.

Working with custom notes

Basic concepts about custom notes

Custom notes represent the unique notes for an individual parts list technical
document or part. Unlike standard notes, which must be created and maintained
by users with special privileges, custom notes are created by the designers who are
responsible for the parts list technical document or part.
The following concepts apply to custom notes:
• Custom notes specify data that is unique to a part or document.

• Custom notes can be related to a single item or to multiple revisions of a single

item.
Example Custom Note 0001 is attached to Item 0001/A.
Or
Custom Note 0001 is attached to Item 0001/A, Item 0001/B, and
Item 0001/C.

• Custom notes cannot be attached to multiple items or to revisions of multiple

items.
Example Custom Note 0001 is attached to Item 0001/A; therefore, Custom
Note 0001 cannot also be attached to Item 0002/A.

• Custom notes are associated with an item, such as a part or document, through
the Custom Notes Lists relation where the part revision or document revision
is the primary object and the custom note or custom note revision is the
secondary object.

• The text for custom note data is specified in the Note Text property of the note
revision.

• Custom notes can be created in the context of another item, such as a parts list
technical document or a part (assembly, component, standard part, and so on).

• When a custom note is created, a Custom Note Text dataset is created. This
dataset contains the text and is attached to the custom note revision.

PLM00111 G Aerospace and Defense Solution Guide 7-9

Chapter 7 Working with notes

Note You cannot delete the dataset or detach the dataset from the custom
note revision.

Create a custom note

1. Select the object to which the custom note applies.

2. Choose File→New→Custom Note or click the Custom Note button .

3. Select Custom Note as the type, and then click Next.

4. Type the revision ID, revision, and name for the custom note.
Note You must type a name for the custom note in the Name box. If you leave
the Requirement ID and Revision boxes blank, the values are filled in
automatically when you click Finish to create the custom note.

5. (Optional) Type a description for the custom note.

6. Click Finish.

The custom note symbol appears in the Custom Notes column for the
selected item.

Add or edit custom note text

1. Open My Teamcenter.

2. Specify the custom note text in one of the following formats.

Plain text a. Right-click the custom note revision and choose Edit
format Properties.
The Check-Out dialog box appears.

b. In the Change ID box, type the change ID.

c. In the Comments box, type notes for checkout.

d. Click Yes.
The Edit Properties dialog box appears.

e. Click the All link in the Edit Properties dialog box.

7-10 Aerospace and Defense Solution Guide PLM00111 G

 Working with notes

f. Scroll to the Text box and type the custom note. For
example:
Verify axel tolerance using company standard test methods.

g. Click Save and Check-In.

The Check-In dialog box appears.

h. Click Yes.
The custom note is checked in and the new text appears
in Body Cleartext property. The Body Cleartext property
is displayed on the Overview tab in the Summary view.
Rich text Note To open the dataset in rich text format, you must
format have Microsoft Office 2007 installed on your
machine.
a. Double-click the Full Text dataset associated with
the note revision, or select the dataset and choose
File→Open.
The note opens in Microsoft Word 2007.
Note Before you can create full text dataset,
Teamcenter must be configured correctly.
For more information, see the Systems
Engineering Guide.

b. Type the note text and then click Save.

c. Close the Microsoft Word document.

PLM00111 G Aerospace and Defense Solution Guide 7-11

Chapter 7 Working with notes

Note After a note has been specified or updated in

rich text format, it cannot be edited in plain text
format.

Attach a custom note to an item or item revision

1. Open My Teamcenter.

2. Right-click the custom note or the custom note revision that you want to attach
and click Copy.

3. Select the item or item revision and choose Edit→Attach

Requirements/Notes→Custom Note.
The custom note revision is attached to the selected object (item or item revision)
through the Complying Objects relation.
Note If the note is not visible under the item or item revision, you must specify
Complying Objects as a shown relation for the item and item revision.
1. Choose Edit→Options.

2. Expand the Options tree and expand the General folder.

3. Click the Item or Item Revision node.

4. In the General options tab, choose Complying Objects from the

Available Relations list.

5. Click to move it to the Shown Relations list.

6. Click OK.

7. Choose View→Refresh or View→Refresh Window to refresh the display.

View and edit a custom note

1. Open My Teamcenter.

2. View or edit the custom note text in either of the following formats.

7-12 Aerospace and Defense Solution Guide PLM00111 G

 Working with notes

Plain text format a. Right-click the custom note revision and click
Properties. Alternatively, select the custom note
revision and choose View→Properties.
The Properties dialog box appears.

b. Click the Check-Out and Edit button.

The Check-Out dialog box appears.

c. In the Change ID box, type the change ID.

d. In the Comments box, type notes for checkout.

e. Click Yes.
The Edit Properties dialog box appears.

f. Click the All link in the Edit Properties dialog box

and scroll to the Text box.

g. In the Text box, edit the custom note.

Note If the note text was defined in Microsoft
Word, the Text box displays a message
stating that you must edit the note using
Microsoft Word.

h. Click Save.

i. Click the Check-In button.

The Check-In dialog box appears.

j. Click Yes.

PLM00111 G Aerospace and Defense Solution Guide 7-13

Chapter 7 Working with notes

Rich text format Note To open the dataset in the rich text format,
you must have Microsoft Office 2007 installed
on your machine.
a. Double-click the Full Text dataset associated with
the custom note revision, or select the dataset and
choose File→Open.
The note opens in Microsoft Word 2007.

b. Edit the note text and click Save.

c. Close the Microsoft Word document.

Note After a note is specified or updated in rich
text format, it cannot be edited in plain
text format.

Revise a custom note

1. Select the custom note revision that you want to revise and choose File→Revise.
The Revise dialog box appears.

2. (Optional) In the Define the basic information for the new item revision pane,
type the name of the new revision.

3. (Optional) Type a description of the revision and choose a unit of measure for
the revision.

4. Click Next.
The Define additional item revision information pane is displayed.

5. (Optional) Enter values for the note revision attributes.

6. Click Next.
The Define attached objects pane displays the source revision and attachments
and the destination revision and attachments. By default, all objects are copied
forward to the new (destination) revision.

7. (Optional) Click the Copy as object option set button to the right of each object
in the revision tree and select the desired copy option.

Don’t Copy
Allows you to selectively copy objects from one revision to
another. Objects that are designated as Don’t Copy appear
with a line through them in the Destination tree.

7-14 Aerospace and Defense Solution Guide PLM00111 G

 Working with notes

Copy as Object
Creates a new object of the same type and relation to the
parent object. Objects created by this method are totally
independent of the parent object. Therefore, any changes to
the copied object are not reflected in the original object.
Copied objects appear in bold in the Destination tree and
can be renamed.
Copy as Reference
Copies the object as a reference to the original object. All
changes to the reference copy affect the original object. The
names of attachments that are copied as references cannot
be modified.

8. Click Next.
The Select projects or programs that you want to assign new object to pane
is displayed.

9. (Optional) Assign the new revision to a different project or program.

10. Click Next.

The Select open option and alternate id display option pane is displayed.

11. (Optional) Set the open, display, or checkout option for the new revision.

12. Click Finish.

The new revision is created as a copy of the previous revision object. The new
revision is independent of the source revision. Modifications to the new revision
are not reflected in the source revision, which allows you to edit the note text
for each revision.

PLM00111 G Aerospace and Defense Solution Guide 7-15

Chapter

8 Managing changes

Managing changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Create a problem report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Create a change request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Create a deviation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

Create a change notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Create a work breakdown using Schedule Manager . . . . . . . . . . . . . . . . . . . . 8-6

Managing unincorporated changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . 8-7

About incorporating changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . 8-7
Example of incorporating changes . . . . . . . . . . . . . . . . . . . . . . . . . ... . 8-8
Conditions that must be to met to set Incorporation status . . . . . . . . ... . 8-11
Set the Incorporation status of an object . . . . . . . . . . . . . . . . . . . . . ... . 8-13
General process for incorporating change items in an ECN . . . . . . . . ... . 8-14
General process for incorporating markups in an ECN . . . . . . . . . . . ... . 8-18
Configure a folder to display Incorporation status . . . . . . . . . . . . . . ... . 8-21
Viewing Incorporation status and history . . . . . . . . . . . . . . . . . . . . ... . 8-22
View Incorporation status and history . . . . . . . . . . . . . . . . . . . . ... . 8-22
Understanding the columns in the Change History dashboard for an
ECN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . 8-23
Understanding the columns in the Change History dashboard for an
item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ... . 8-24
Configure the Change History dashboard . . . . . . . . . . . . . . . . . ... . 8-25

PLM00111 G Aerospace and Defense Solution Guide

Chapter

8 Managing changes

Managing changes
The Aerospace and Defense solution extends the change management data model
and adds attributes specific to the aerospace and defense industry to the following
change objects:
• Change requests and change request revisions

• Change notices and change notice revisions

• Tasks and task revisions

• Deviation requests and deviation request revisions

For more information, see Aerospace and Defense template.

Change Manager can be easily configured to use your change process.
• Use Change Manager to manage your change objects.
For more information about Change Manager, see the Change Manager Guide.

• Use Change Manager with Workflow Designer to track the evolution of changes
through your organization according to a controlled, repeatable process.
For more information about defining processes, see the Workflow Designer Guide.

• Use Change Manager with Schedule Manager to create work breakdown

structures you can use to plan and schedule the changes you are making to
your product.
For more information about work breakdown tasks, see the Schedule Manager
Guide.

Create a problem report

There are three different contexts in which to create a problem report.
For information about the different contexts, see the Change Manager Guide.
1. (Optional) Select the item revision that you want to create a problem report for.

2. Choose File→New→Change or right-click the item revision and choose New

Change in context.

3. In the New Change dialog box, select Problem Report and click Next.

PLM00111 G Aerospace and Defense Solution Guide 8-1

Chapter 8 Managing changes

4. Type a name in the Synopsis box and a description of the problem in the
Description box. You can also type a problem report ID and revision in the
PR No. and Revision boxes. If you do not provide an ID and revision number,
Teamcenter provides them automatically.

5. Click Finish.
If you created the problem report by right-clicking the item revision and choosing
New Change in context, the item revision is automatically copied into the
problem report Problem Items folder.

Create a change request

There are three different contexts in which to create a problem report.
For information about the different contexts, see the Change Manager Guide.
1. (Optional) Select the item revision or problem report revision that you want to
create a change request for. You can select multiple problem report revisions.

2. Create the change request in one of the following ways:

• Choose File→New→Change.

• Right-click an item revision and choose New Change in context.

• Select one or more problem report revisions, right-click, and choose Derive
Change.
The problem report revisions must have their properties set to:

Property Must be
Maturity Reviewing
Disposition Approved

Closure Open

You can configure which change object you can derive from the problem
report revision with the CM_change_derivations preference.

3. In the New Change dialog box, select Change Request and click Next.

4. If this is a new change, type a name in the Synopsis box and a description
of the change request in the Description box. If this is a derived change, the
boxes contain the name and description from the problem report revision. You
can edit these boxes.
You can also type a change request ID and revision in the ECR No. and Revision
boxes. If you do not provide an ID and revision number, Teamcenter provides
them automatically.
If you derived this change request from a single problem report, the Propagate
relations check box is available. If you want to copy the relationships (such

8-2 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

as reference items and problem items) from the problem report to the change
request, select the check box.
Note Propagate relations is available only when a change request is derived
from a single problem report. When more than one problem report
exists, this relationship must be created manually.

You can configure which relations to propagate when you

derive a change object from a problem report with the
CM_ProblemReportRevision_Relations_To_Propagate preference.

5. In the Change Type box, type the acronym that designates the type of change
documentation used on a program.

6. In the Change Class box, type the government or company change classification
code.

7. In the Change Category box, type the specific category of the change.

8. In the Change Item Affected? box, click either True or False to indicate if the
change item affects other configuration items.

9. In the Warranty Affected? box, click either True or False to indicate if the
change item affects the warranty.

10. In the In Production? box, click either True or False to indicate if the change
item is in production.

11. In the Is Primary Change? box, click either True or False to indicate if the
change item is a primary change.

12. In the Retrofit Required? box, click either True or False to indicate if the change
item requires a retrofit.

13. Click Finish.

If you created the change request by right-clicking the item revision and choosing
New Change in context, the item revision is automatically copied into the
change request Problem Items folder.

Create a deviation request

There are three different contexts in which to create a problem report.
For information about the different contexts, see the Change Manager Guide.
1. (Optional) Select the item revision or problem report revision that you want to
create a deviation request for. You can select multiple problem report revisions.

2. Create the deviation request in one of the following ways:

• Choose File→New→Change.

• Right-click an item revision and choose New Change in context.

PLM00111 G Aerospace and Defense Solution Guide 8-3

Chapter 8 Managing changes

• Select one or more problem report revisions, right-click, and choose Derive
Change.
The problem report revisions must have their properties set to:

Property Must be
Maturity Reviewing
Disposition Approved
Closure Open

You can configure which change object you can derive from the problem
report revision with the CM_change_derivations preference.

3. In the New Change dialog box, select Deviation Request and click Next.

4. If this is a new change, type a name in the Synopsis box and a description of
the deviation request in the Description box. If this is a derived change, the
boxes contain the name and description from the problem report revision. You
can edit these boxes.
You can also type a deviation request ID and revision in the ECR No. and
Revision boxes. If you do not provide an ID and revision number, Teamcenter
provides them automatically.
Enter the change in the Change Type box. You can enter RFD for a request for
deviation or RFW for a request for waiver.
If this deviation is recurring, select the Is deviation recurring? check box and
type the reason in the Rationale box.
If you derived this deviation request from a single problem report, the Propagate
relations check box is available. If you want to copy the relationships (such as
reference items and problem items) from the problem report to the deviation
request, select the check box.
You can configure which relations to propagate when you
derive a change object from a problem report with the
CM_ProblemReportRevision_Relations_To_Propagate preference.

5. In the Change Item Affected? box, click either True or False to indicate if the
change item affects other configuration items.

6. In the Warranty Affected? box, click either True or False to indicate if the
change item affects the warranty.

7. Click Finish.
If you created the deviation request by right-clicking the item revision and
choosing New Change in context, the item revision is automatically copied into
the deviation request Problem Items folder.

Create a change notice

There are three different contexts in which to create a problem report.

8-4 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

For information about the different contexts, see the Change Manager Guide.
1. (Optional) Select the problem item revision or change request revision that
you want to create a change notice for.

2. Create the change notice in one of the following ways:

• Choose File→New→Change.

• Select the item revision, right-click, and choose New Change in context.

• Select one or more change request revisions, right-click, and choose Derive
Change.
The change request revisions must have their properties set to:

Property Must be
Maturity Reviewing
Disposition Approved
Closure Open

You can configure which change object you can derive from the change
request revision with the CM_change_derivations preference.

3. In the New Change dialog box, select Change Notice and click Next.

4. Type a name in the Synopsis box and a description of the change notice in the
Description box. You can also type a change notice ID and revision in the ECN
No. and Revision boxes. If you do not provide an ID and revision number,
Teamcenter provides them automatically.
If you derived this change notice from a single change request, the Propagate
relations check box is available. If you want to copy the relationships (such
as reference items and problem items) from the change request to the change
notice, select the Propagate relations check box.
You can configure which relations to propagate when you
derive a change object from a change request with the
CM_ChangeRequestRevision_Relations_To_Propagate preference.

5. In the Change Type box, type the acronym that designates the type of change
documentation used on a program.

6. In the Paper Change? box, select either True or False to indicate if the change
notice is an unincorporated change.

7. In the Change Class box, type the government or company change classification
code.

8. In the Category box, type the specific category of the change.

9. Click Finish.
If you created the change notice by right-clicking the item revision and choosing
New Change in context, the item revision is automatically copied into the
change notice Problem Items folder.

PLM00111 G Aerospace and Defense Solution Guide 8-5

Chapter 8 Managing changes

Create a work breakdown using Schedule Manager

Note You can copy an existing schedule but it can only be associated with one
change object.

1. Select the Plan Items folder of the change request or change notice that you
want to create a work breakdown for.
For a CR or CN, you can add objects to the Plan Items folder if you are an
assigned participant. The change object property settings are as follows.

Assigned
participant Closure Disposition Maturity
Analyst Open None Elaborating
or
Open Investigate Reviewing

2. Choose File→New→Schedule.
This starts the New Schedule wizard in Schedule Manager where you create
your work breakdowns. You can create several schedules to help you analyze the
change.
For more information about creating schedules, see the Schedule Manager Guide.
Note You must be an Author user to create schedules.

3. In the Open Change view, select the schedule in the Plan Items folder and click
the Open Schedule button .
The Schedule Manager view is displayed.

4. Add tasks to your schedules.

For more information about adding tasks, see the Schedule Manager Guide.
When you create a task, add the following Aerospace and Defense specific
attributes in the Select task type, start, and finish dates dialog box.

a. In the Administrative Task? box, click True or False to indicate if the task is
an administrative task.

b. In the Category box, type the category of the task.

c. In the Complexity box, type the category of the change, document, or part.

d. In the Impact Assessment Required box, click True or False to indicate if

the task requires impact assessment.

e. In the Proposed Task? box, click True or False to indicate if the task is a
proposed task versus an implemented task.

5. Assign resources to tasks, including selecting responsible people using the

Membership button .

8-6 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

For more information about managing resources and assigning resources to

tasks, see the Schedule Manager Guide.

6. In the Schedule Manager view, click the View Task folders button .
The system displays the Open Task view.

7. Add item revisions to the task folders as necessary.

8. (Optional) Roll up the item revisions in your task folders to the change object
folders.
For more information about rolling up objects, see the Change Manager Guide.

Managing unincorporated changes

About incorporating changes

An unincorporated change is a change that is approved but not yet incorporated in
the design of a product. Usually, changes are not incorporated fully because there
is not enough time, importance, or budget to incorporate the changes completely
through the development process.
Note • The unincorporated change functionality is intended to track
unincorporated changes to existing designs. It does not support tracking
unfinished work of new, unreleased designs.

• Unincorporated changes can only be applied to ECNs.

Example A designer releases Revision A of Item1 for production, and begins

working on a new revision (Revision B). On the shop floor, a minor
modification is performed over Revision A and production starts. This
changed version needs to be recorded in Teamcenter. Therefore, a new
supplemental revision (A01) is created and released. Because the change
still needs to be incorporated into the main release, (revision B, in this
case), the change is considered partially incorporated.

An ECN can also either partially or fully incorporate markups. However, a markup
is considered fully incorporated into all the solution items of the incorporating ECN,
which has the change partially incorporated into the same item.

PLM00111 G Aerospace and Defense Solution Guide 8-7

Chapter 8 Managing changes

Example A designer creates a ECN (CN1), with a markup (MU1) as a solution

item. The designer sets the Incorporation status of several of the
impacted items to Partially Incorporated.
The designer then creates a second ECN (CN2) to incorporate markup
MUI. The designer creates an incorporates relation between CN2 and
MU1.
CN1/MU1 are now considered fully incorporated into the solution
items of CN2 that belong to the impacted items of CN1 and have an
Incorporation status of Partially Incorporated.

For a full example of incorporating changes, see Example of incorporating changes.

Example of incorporating changes

The following is an example showing the steps to incorporate changes partially and
then fully when an enterprise change notice (ECN) impacts multiple change items.

Step 1 – Create enterprise change notice implementing changes

Company ABC creates an ECN (Change Notice Main) to implement a change needed
on two items (Item 1 and Item 2). The item revision of the items in the Solutions
folder is Revision b.
The ECN change state is Open, Executing, and Approved.

The following shows the status for the items as it would appear in the Change
History dashboard.

For more information about the Change History dashboard, see Viewing
Incorporation status and history.
Note ECN CN0 in the Change History dashboard is not shown in the figures to
avoid complexity. CN0 is the ECN that initially created Item 1, Revision a,
and Item 2, Revision a as solution items.

8-8 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

Step 2 – Make the partially incorporated changes

On the shop floor, a minor modification is done over Revision a of the two items
(Item 1 and Item 2) and production is started. Company ABC needs to immediately
incorporate the change into Teamcenter. The items have work-in-process revisions
so the change cannot be incorporated into these.
Therefore, a designer creates new revisions to incorporate the shop-floor changes and
starts a new change notice (Change Notice Partial) to manage the implementation.
The designer sets the incorporation status on the items in the Impacted Items folder
of Change Notice Partial to Partially Incorporated.
The designer closes Change Notice Partial after creating Revision a01 of Item 1
and Item 2.
Work still continues on Revision b in Change Notice Main, and it remains open.

The change states of the ECNs are:

• Change Notice Main – Open, Executing, and Approved

• Change Notice Partial – Closed, Complete, and Approved

PLM00111 G Aerospace and Defense Solution Guide 8-9

Chapter 8 Managing changes

Step 3 – Incorporate changes from Item 1, Revision a01, into Revision b in

Change Notice Main
The designer finishes the work in Change Notice Main on Revision b of the items.
The designer wants to incorporate the change to Item 1 in Change Notice Partial
into Revision b of Change Notice Main, but not the change that was done to Item2.
To indicate this, the designer creates an Incorporates this relation between Change
Notice Main and Revision a01.

The change states of the ECNs are both Closed, Complete, and Approved.

Step 4 – Incorporate changes from Item 2, Revision a01, into Revision b in

Change Notice Additional
Much later, more changes are recommended for Item 1 and Item 2. Therefore,
Company ABC creates a third change notice (Change Notice Additional). During
that change, the designer implements the changes that were in Change Notice
Partial for Item 2 into Revision c.
At this point, all change notices are closed.

8-10 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

The change states of the ECNs are all Closed, Complete, and Approved.

Conditions that must be to met to set Incorporation status

The following conditions must be met before you can set the Incorporation status
of an item revision. By default, all impacted items in the Impacted Items folder of
an ECN are set to Unincorporated. In addition, when an ECN is closed through
a workflow, all impacted items with a status of Unincorporated are automatically
set to Incorporated.

PLM00111 G Aerospace and Defense Solution Guide 8-11

Chapter 8 Managing changes

Conditions required for a change to be partially incorporated

A change authorized by an ECN revision is considered partially incorporated in an
item revision if the following are met:
• The item revision is a solution item of the ECN (in its Solution Items folder). If
it is, then it meets the Business Modeler IDE condition CMHasSolutionItem.

• The ECN has an impacted item in its Impacted Items folder and its Incorporation
status is set to Partially Incorporated.
The CMHasImpactedItem relation object has the ECN revision as its
primary object and an item revision of the same item as its secondary object
In addition, the value of the property Cm0IncorporationStatus on the
CMHasImpactedItem relation object is set to Partially Incorporated.

Conditions required for fully incorporating a change

A change previously partially incorporated into an item revision, (for example,
Revision a01) is considered fully incorporated into another item revision (for
example, Revision b) of the same item if all the following are met:
• The ECN authorizing the item revision (in this example, Revision b) is a primary
object of a Cm0Incorporates relation object and the previous revision (for
example, Revision a01) is the secondary object.

• The ECN has an impacted item in its Impacted Items folder and its incorporation
status is set to Incorporated.
The CMHasImpactedItem relation object has the ECN as the primary object
and an item revision of the same item as its secondary object. In addition, the
value of the property Cm0IncorporationStatus on the CMHasImpactedItem
relation object is set to Incorporated.

• The ECN revision authorizing the item revision (in this case, Revision b) is
closed.

Conditions required for incorporating markups

An ECN incorporates a markup partially or fully in the same way it does item
revisions, as explained in the two earlier sections. However, a markup is considered
fully incorporated into all the solution items of the incorporating ECN that has the
change partially incorporated into the same item.
Example A markup (MU1) is a solution item of an ECN (CN1) and the incorporation
status of a few of the impacted items of CN1 is set to Partially
Incorporated.
A designer later creates an Incorporates relation between a new ECN
(CN2) and the markup MU1.
Now CN1 and MU1 are considered fully incorporated into the solution
items of CN2, which belong to the impacted items of CN1 with the
Incorporation status set to Partially Incorporated.

8-12 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

Set the Incorporation status of an object

Before you can set the Incorporation status of an item revision, the item revision
must be related to an enterprise change notice (ECN) as an item that it impacts.
For more information about:
• Setting relations of change objects, see the Change Manager Guide.

• The conditions that must be met to set the Incorporation status of item revisions,
see Conditions that must be to met to set Incorporation status.
Note By default, the Incorporates relation is not displayed as a folder under the
ECN revision.
For information about displaying a folder with this relation under the ECN,
see Configure a folder to display Incorporation status.

1. In My Teamcenter or Change Manager, right-click the item revision and choose

Properties on Relation.

2. In the Properties dialog box, scroll to Incorporation Status and set it to one
of the following:

• Unincorporated
The change has not been incorporated.

• Partially Incorporated
The change as defined has been partially incorporated. It may or may not
already be fully incorporated by a subsequent change.

• Incorporated
The change as defined has been fully incorporated. No subsequent changes
are required to fully incorporate the defined change.

PLM00111 G Aerospace and Defense Solution Guide 8-13

Chapter 8 Managing changes

• Cancelled
The change as defined is not incorporated in any way. This value indicates
that an item has been identified as an impacted item, but the change as
defined is not applied to that item. This status can be applied before a
change solution definition or change execution has begun, or it can be
updated after the change execution has begun.

3. Click OK.

General process for incorporating change items in an ECN

The following shows the general process for incorporating change items in an
enterprise change notice (ECN). It is followed by a summary of the steps.

Note The examples use primary revisions. We recommend that you use secondary
revisions when partially incorporating change items. For example, use A01
or A02 and not A, B, and C.

1. Create the ECN to completely incorporate the item revision.

a. Create the ECN.

b. Add the item revision to be incorporated to its Impacted Items folder.

8-14 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

c. Assign participants and start a workflow.

2. Create the new item revision.

a. Use the Revise Impacted Items(s) command to create a new revision of the
item revision and add it to the Solutions Items folder.
The following properties must be met:

Assigned Closure/Disposition/Maturity
participant property settings
Analyst Open/Approved/Executing

For more information about revising an impacted item, see the Change
Manager Guide.

PLM00111 G Aerospace and Defense Solution Guide 8-15

Chapter 8 Managing changes

3. Create the second ECN that is to incorporate the item revision partially (the
partially incorporated ECN).
a. Create the partially incorporated ECN.

b. Assign participants and start a workflow.

4. Set the Incorporation status and make the change.

a. Use the Properties on Relation command to set the Incorporation status of
the item revision to Partially incorporated

For more information about setting the Incorporation status of a change

item, see Set the Incorporation status of an object.

b. Use the Revise Impacted Items(s) command to create a new revision of the
item revision and add it to the Solutions Items folder.
The following properties must be met:

Assigned Closure/Disposition/Maturity
participant property settings
Analyst Open/Approved/Executing

8-16 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

For more information about revising an impacted item, see the Change
Manager Guide.

c. Make the change.

5. Add solution item to incorporation ECN.

a. Add the item revision from the Solutions Items folder of the second ECN to
the Incorporates folder of the first ECN that will incorporate all changes.
The following properties must be set to add the item revision to the
Incorporates folder:

Assigned Closure/Disposition/Maturity
participant property settings
Analyst Open/Approved/Elaborating

For information about displaying the Incorporates folder, see Configure a

folder to display Incorporation status.

6. Close the incorporation ECN.

a. Close the first ECN that incorporates the solution item. Closing the
ECN automatically sets the Incorporated status of the solution item to
Incorporated as shown in the Change History dashboard. .

PLM00111 G Aerospace and Defense Solution Guide 8-17

Chapter 8 Managing changes

For more information about the Change History dashboard, see Viewing
Incorporation status and history.

General process for incorporating markups in an ECN

The following provides the general process for incorporating change items in an
enterprise change notice (ECN) when the solution item is a markup of the impacted
item (they are different items; not revisions of each other).
Note The examples use primary revisions. We recommend that you use secondary
revisions when partially incorporating change items. For example, use A01
or A02 and not A, B, and C.

1. Create the ECN to completely incorporate the change.

a. Create the ECN.

b. Add the item revision to be incorporated to its Impacted Items folder.

8-18 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

c. Assign participants and start a workflow.

d. Use the Revise Impacted Items(s) command to create a new revision of the
item revision and add it to the Solutions Items folder.
The following properties must be met:

Assigned Closure/Disposition/Maturity
participant property settings
Analyst Open/Approved/Executing

For more information about revising an impacted item, see the Change
Manager Guide.

2. Create a second ECN that is to incorporate the item revision partially and make
the partial change. The following shows the completed ECN with different
impacted and solution items.

a. Create the second ECN.

PLM00111 G Aerospace and Defense Solution Guide 8-19

Chapter 8 Managing changes

b. Add the item revision to be partially incorporated to its Impacted Items

and Solutions Items folders. In this case, they are different items that are
unrelated.

c. Assign participants and start a workflow.

d. Use the Properties on Relation command to set the Incorporation status of

the item revision in the Impacted Items folder to Partially incorporated
For more information about setting the Incorporation status of a change
item, see Set the Incorporation status of an object.

e. Use the Relate Solution Item to Impacted Item command to relate the
solution item to the impacted item, which creates a link between them, as
shown in the Change History dashboard.

For more information about the Change History dashboard, see Viewing
Incorporation status and history.

f. Make the change and close the ECN.

3. Add the item revision from the Solutions Items folder of the second ECN to the
Incorporates folder of the first ECN that will incorporate all changes.
The following properties must be set to add the item revision to the Incorporates
folder:

Assigned Closure/Disposition/Maturity
participant property settings
Analyst Open/Approved/Elaborating

8-20 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

4. Close the first ECN that incorporates the solution item. Closing the ECN
automatically sets the Incorporated status of the solution item to Incorporated
as shown in the Change History dashboard. .

For more information about the Change History dashboard, see Viewing
Incorporation status and history.

Configure a folder to display Incorporation status

By default, the Incorporation status Incorporates is not displayed as a folder under
an enterprise change notice (ECN) revision.

Use the Options dialog box to specify that the Incorporates property should be
displayed for an ECN.
1. Choose Edit→Options.

PLM00111 G Aerospace and Defense Solution Guide 8-21

Chapter 8 Managing changes

2. In the list on the left, select General and then select Item Revision.

3. Click the Related Object tab.

4. Set Select Item revision type to Change Notice Revision.

5. In the Available Relations list, double-click Incorporates.

Incorporates moves to the Shown Relations list.

6. Now click the General tab, and set up that the same relations be shown following
Steps 4 and 5.

7. Click OK.

For more information, see the Rich Client Interface Guide.

Viewing Incorporation status and history

View Incorporation status and history

You can view the incorporation status of an enterprise change notice (ECN) or an
item revision using the Change History dashboard of the Summary tab.
Note The Change History dashboard must be configured.
For more information, see Configure the Change History dashboard.

1. In My Teamcenter or Change Manager, select an item or ECN.

2. Click the Summary tab.

8-22 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

3. Click the Change History tab.

The following shows the Change History dashboard when an item revision is
selected.

Each row in the dashboard represents one revision of the item or the ECN
authorizing the revision (no two rows represent the same revision). The
columns in the dashboard change depending on whether you selected to view
the incorporation history of an item revision or ECN.
For more information about the columns in the Change History dashboard, see:

• Understanding the columns in the Change History dashboard for an ECN

• Understanding the columns in the Change History dashboard for an item

Understanding the columns in the Change History dashboard for an ECN

When you select to view the Incorporation status of an enterprise change notice
(ECN) in the Change History tab of the Summary tab, the Change History
dashboard appears with the following columns.

The column Displays

Solution Item The name of the solution item of the
ECN.

Impacted Item The name of the Impacted Item in the

ECN.
Incorporates Changes of The names of the item revisions or
markups that the ECN is incorporating.
Incorporated by The name of the ECN revision that
is incorporating the object listed in
Solution Item column.

PLM00111 G Aerospace and Defense Solution Guide 8-23

Chapter 8 Managing changes

The column Displays

Incorporated into The Incorporation property of the ECN
revision.
Incorporation Status The Incorporation status of the impacted
item, except if the Incorporation status
is set to Partially Incorporated. Then,
this indicates that another ECN has
incorporated the change fully.

Understanding the columns in the Change History dashboard for an item

When you select to view the Incorporation status of an item in the Change History
tab of the Summary tab, the Change History dashboard appears with the following
columns.

The column Displays

Revision/Solution Item The ID and name of the solution item.
Impacted Item The ID and name of the impacted item.
Markup The name and ID of any markup.
Authorizing Change Notice The name of the ECN revision.
Closure The Closure of the ECN.
Maturity The Maturity of the ECN revision.
Disposition The Disposition of the ECN revision.
Incorporates Changes of IDs of the item revision or the name of
the markup being incorporated by the
ECN revision.
Incorporated by The name of the incorporating ECN
revision.
Incorporated into The ID of the revision the change was
incorporated into.
Incorporation Status of Change Shows the Incorporation status set
on the impacted item, except if the
Incorporation status is set to Partially
Incorporated. Then, this indicates
that another ECN has incorporated the
change fully.

8-24 Aerospace and Defense Solution Guide PLM00111 G

 Managing changes

Configure the Change History dashboard

• Associate the Change History tab with more workspace objects.

Change Manager associates the Change History tab with all standard workspace
objects involved in a change management process, such as item revisions and
change objects. If you want to display the Change History dashboard for other
workspace objects, such as document revisions, you can modify the style sheet
for the Summary view of the object by adding the following code.
<page titleKey="tc_xrt_ChangeHistory" title="Change
History" visibleWhen="{pref:CM_Change_History_Enable}==true">
<section titleKey="tc_xrt_ChangeHistory"
title="Change History" initialstate="expanded">
<customPanel
java="com.teamcenter.rac.cm.views.ItemChangeHistoryPanel"
js="displayItemCustomPanel" />
</section>
</page>

Note If you have modified the style sheet of a subtype of Item/ItemRevision,

the Change History would not appear in its Summary view, and you
need to add the code shown.

For more information about using style sheets, see the Client Customization
Programmer’s Guide.

• Turn on and off the display of Change History dashboard.

Use the CM_Change_History_Enable preference to turn on or off the display
of the Change History dashboard.
For more information, see the Preferences and Environment Variables Guide.

• Change the columns in the dashboard and their order.

o CM_Item_ChangeHistory_Columns
Changes the columns displayed for an item revision.

o CM_CNR_ChangeHistory_Columns
Changes the columns displayed for an enterprise change notice.
For more information, see the Preferences and Environment Variables Guide.

PLM00111 G Aerospace and Defense Solution Guide 8-25

Chapter

9 Managing contract data

Managing contract data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Defining data item descriptions (DIDs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Create a data item description (DID) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Associate documents with data item descriptions (DIDs) . . . . . . . . . . . . . 9-3

Create a contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

Scheduling contract events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

Schedule contract events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Working with data requirement items (DRIs) . . . . . . . . . . . . . . . . . . . . . . . . 9-6

Create a data requirement item (DRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6
Associate a contract event list with a data requirement item (DRI) . . . . . . 9-9

Defining submittal delivery schedule . . . . . . . . . . .... . . . . . . . . . . . . . . . . 9-11

Generate a submittal delivery schedule . . . . . . .... . . . . . . . . . . . . . . . . 9-12
Create submittals manually . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . 9-12
Associate submittals with schedule deliverables ... . . . . . . . . . . . . . . . . 9-14

Copy contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15

Providing feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

Create correspondence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16
Associate correspondence revision with a submittal revision . . . . . . . . . . . 9-17
Associate correspondence with a contract revision . . . . . . . . . . . . . . . . . . 9-17

PLM00111 G Aerospace and Defense Solution Guide

Chapter

9 Managing contract data

Managing contract data

Contracts are pivots that drive business across different industry sectors. A contract
is a structured procurement document listing the milestones and the schedule dates
of the contract event. This procurement document can be a list of data requirement
items, such as design information, drawings, status reports, and so on.
After the contract is created, the data analyst creates a workflow schedule to collate
the feedback and the review comments that are generated during the data item
approval process. This is done by initiating correspondence related to the contract.
A graphical representation of managing contract data through Teamcenter is shown
in the following figure.

The sequence of steps is as follows:

PLM00111 G Aerospace and Defense Solution Guide 9-1

Chapter 9 Managing contract data

1. Create data item descriptions (DIDs).

DIDs are predefined contract forms that specify data content, data format, and
other specific instructions for the suppliers.
You can maintain a DID repository to associate a data requirement item (DRI) to
the contract.

2. Create a contract.
The administrator or the data analyst creates a contract and contract revision in
Teamcenter. You can also choose to create a contract event for scheduling the
contract review and feedback process.

3. Create data requirement items.

You must attach a data requirement item (DRI) to the contract. A DRI
is a technical document or deliverable that forms the basis for structured
procurement. It represents a single contractual data item as described in DID.

4. Define submittal delivery schedule for the deliverable.

After the DRI is specified, you must initiate the review process. Submittal
represents the data item submittal package or documentation that relates to the
actual documents submitted.

5. Provide feedback.
It is important to monitor the correspondence related to the data item submittal
package between you and the supplier.

Defining data item descriptions (DIDs)

A data item description specifies the content and the format of the data item
requirement item. It is typically a published industry standard and often has an
associated template. You can also create a repository of DID for DRI creation.
When creating a data requirement item, you can optionally provide the item number
of an existing data item description to populate the DID Number attribute for the
data requirement item. Therefore, if a data item description is going to be specified
on the data requirement item, the data item description must be created before the
data requirement item can be created.

Create a data item description (DID)

Data item descriptions define the data content, data format, preparation
instructions, and intended use.
1. From the menu bar, choose File→New→Item.

2. In the New Item dialog box, select Data Item Description and then click Next.

3. Define basic information for the new item, as follows:

9-2 Aerospace and Defense Solution Guide PLM00111 G

 Managing contract data

ID/Revision - Name Specifies the identity of the data item

description and the data item description
revision. This is a mandatory field.
Description Describes the data item description. Use
a description that helps to distinguish the
purpose of the DID.

4. Click Next.

5. Define additional item information, as follows:

DID Type Specifies an attribute for classifying the

document item.
Program Phases Specifies the program application for the
specified DID type.

6. Click Next.

7. Define additional item revision information, as follows:

Document Author Specifies the DID author.

Document Subject Specifies the DID subject.

Document Title Specifies the title of the DID.

8. Click Finish.
Note You can also choose to click Finish after step 5.

Associate documents with data item descriptions (DIDs)

The contract administrator must add or attach the template or format to the DID as
datasets.
1. From the menu bar, choose File→New→Dataset... to create a dataset.
For information about datasets, see the Getting Started with Teamcenter.

2. Right-click and copy the dataset.

3. Select the DID revision item and choose Edit→Paste Special.

4. In the Paste Special dialog box, choose the appropriate attribute and then click
OK.

Create a contract
A contract is signed between a customer and a supplier. Each contract defines a set of
required deliverables, such as a purchase order or other procurement documentation.

PLM00111 G Aerospace and Defense Solution Guide 9-3

Chapter 9 Managing contract data

The administrator creates a contract object in Teamcenter, defines a master schedule

with milestones, and associates that with the contract. The fields marked with an
asterisk are required.
1. Open My Teamcenter.

2. From the menu bar, choose File→New→Item.

3. In the New Item dialog box, select Contract and then click Next.

4. Define the basic information for the item, as follows:

ID / Revision - Name Specifies the identity of the contract and the

contract revision. This is a mandatory field.
Note If naming rules are configured at your
site, you can click the Assign button
to automatically generate the contract
ID and revision.
Description Describes the contract item. Use a description
that helps to distinguish the purpose of the
item.

5. Click Next.

6. Define additional item information details, as follows:

Contract Category Specifies the type of contract.

• CONTRACT
Represents any contract documents used
for procurement.

• TWO
Represents temporary work order.

• PO
Represents purchase order.

Title Specifies the title of the procurement

document.
Author Specifies the name of the person who has
drafted the contract.
Subject Specifies the content of the contract.

7. Click Next.

8. Define additional item revision information, as follows:

9-4 Aerospace and Defense Solution Guide PLM00111 G

 Managing contract data

Comments Specifies any special remarks related to the

contract.
Contract Cost Specifies the total cost of the contract.
Contract cost also includes the addition to the
cost delta incurred due to modification.
Contract Cost Delta Specifies the relationship between the current
contract cost and the inherent future contract
cost that may arise due to modification of the
contract.
Contract Event schedule Specifies the milestones for the contract.
Contract Pricing Model Specifies the payment forms for the contract,
for example, cost plus fixed fee.
Effective Date Specifies the date from which the contract is
effective.
Office Primary Resp Specifies the name of the person or a role
responsible for the review and acceptance of
the contract.
Period of Performance Specifies the duration of the contract, which
is the time period as specified in the contract
in months.
Recurring Cost Specifies whether the contract cost is recurring
cost.
SOW Affected Specifies whether the statement of work
for the contract is affected due to contract
modification.

9. Click Next.

10. Select a program for the new object and then click Next.

11. Define the options for the contract and then click Finish.

12. Close the New Item dialog box.

Note You can also choose to click Finish after step 8.

Scheduling contract events

You can associate a contract revision with a contract event schedule. Specifying
milestones with schedule dates for the contract event aids in tracking the deliverable
through the contract event cycle.
The contract event schedule is based on schedule templates. The administrator
can choose to display either all the templates or only certain templates related to
the current project set.
To display all the templates, set the value of the
dm0UseCurrentProjSchTemplates global constant to False.

PLM00111 G Aerospace and Defense Solution Guide 9-5

Chapter 9 Managing contract data

For more information about setting values, see the Business Modeler IDE Guide.
However, if you do not select any schedule template, the application creates a default
contract event schedule and associates that with contract revision.
You cannot generate two schedules on the same contract revision object. An error
message is displayed to indicate that the schedule exists.

Schedule contract events

1. In the Quick Links pane, click Home.

2. In the Home pane, navigate to the contract object that you have created and
expand the contract object→contract revision object.

3. Click to expand the contract object.

4. Right-click the contract revision object and choose Add Contract Event Schedule.

5. In the Add Contract Event Schedule dialog box, select a schedule template from
the Schedule Template list.
Note To display all the templates, set the value of the
Cdm0UseCurrentProjSchTemplates global constant to
False.
Set the value to True if you want to display only specific schedule
templates related to the project.

Working with data requirement items (DRIs)

A contract administrator or data analyst user creates a list of data requirement
items (DRIs) for a contract. A data requirement item represents an individual data
requirement in a data requirement list. You create a data requirement item for
each deliverable stated in the contract using the dates and frequencies stated in
the contract.
You must provide the contract ID to associate the DRI with the contract. For each
data requirement item, the supplier must submit documents at particular intervals
as specified in the submittal delivery schedule. The submittal delivery schedule is
based on the events specified by the user on each DRI.

Create a data requirement item (DRI)

A contract deliverable can be submitted either by the customer or the supplier.
To associate the DRI with a contract, you must specify the contract ID, the data
requirement item type, the data requirement item revision properties, and
optionally, the DID when creating the DRI.
1. From the menu bar, choose File→New→Data Requirement Item.

2. Define basic information for the new item, as follows:

9-6 Aerospace and Defense Solution Guide PLM00111 G

 Managing contract data

ID / Revision - Name Specifies the identity of the data requirement

item and the data requirement item revision.
This is a mandatory field.
Note If naming rules are configured at your
site, you can click the Assign button
to automatically generate the data
requirement item ID and revision.
Description Describes the data requirement item. Use
a description that helps to distinguish the
purpose of the item.

3. Click Next.

4. Define additional data requirement item, as follows:

Contract Line Item Number Specifies the section ID within the contract.
This section describes how a specific task must
be accomplished.
Contract Reference Specifies the contract ID. The DRI is
associated with the contract ID specified.
Provide Contract Deliverable Specifies the type of contract data deliverable
that is submitted by the customer or the
supplier.
Select True to provide the contract deliverable
for the supplier to review.
Select False to receive the contract deliverable
from the supplier.
Reference Citation Specifies the ID of a specific reference content
in the document.

5. Click Next.
Note The following happens when you click Next, Back or the Finish button
and you have configured multifield keys for contracts:
If there are multiple contracts matching the criteria for contracts you
specified in the Define additional item information dialog box:
• You see the select Unique Source Document dialog box. This dialog
box displays the list of contracts matching the criteria you specified
for technical documents.

• To select a contract, double-click the row which contains the contract

you want.

6. Define any additional data requirement item revision, as follows:

Addressee Specifies the list of contacts needed to review

the contract.

PLM00111 G Aerospace and Defense Solution Guide 9-7

Chapter 9 Managing contract data

Approval Code Specifies the approval code for the data

requirement item revision.
Approval Required Specifies whether the customer must approve
the data item.
Cert Required Specifies whether the submitted data item
requires certification.
Comments Specifies any comments concerning the item.
DID Title Specifies the title of the document.
Data Management Due Offset Specifies the offset of the data management
due date.
Data Requirement Item Specifies the subtitle of the data requirement
Subtitle item.
Delivery Address Specifies the delivery address of the customer
or the supplier.
Delivery Mechanism Specifies the mode of delivery of the contract.
Distribution Required Specifies whether any documentation related
to the item should be distributed.
Effective Cutoff Date Specifies the last date for data collection.
Effective Cutoff Event Desc. Specifies through explanation the last date for
data collection. Use a description that helps
you understand the purpose of selecting the
cutoff date.
Event List Specifies the event table for generating event
schedule.
Exhibit Name Specifies the ID of a particular data item in a
data item description document.
Media Type Specifies the format of the data, for example,
electrostatic, microfilm, and so on.
OPR Notif Due Offset Specifies the last date for the creation of
the notification to the office of the primary
reviewers.
Office Primary Resp Specifies the name of the contacts, groups, or
role responsible for reviewing the data item.
Response Due Offset Specifies the offset to the response due date.
Shipping Document Reqd Specifies whether DD Form 250 is required for
the delivery of the data item.
Submit Flow Thru Specifies whether a supplier’s data
requirement item should be submitted as a
customer’s data requirement item.
Submit Purpose Specifies the purpose of the submitted data
item.
Submit Quantity Specifies the number of copies required for
submission.

9-8 Aerospace and Defense Solution Guide PLM00111 G

 Managing contract data

7. Click Next.

8. Select a program for the new object and then click Next.

9. Define the options and then click Finish.

10. Click Finish.

Associate a contract event list with a data requirement item (DRI)

The supplier must submit documents on specified dates. You can define the
submittal delivery events for the data requirement item after creating the DRI.
The data for submittal delivery events is used by the application to generate a
preliminary submittal delivery schedule.
Note You must define the Event List to generate the event schedule.

1. In the Home pane, expand contract item→data requirement item.

2. Right-click the data requirement item revision and choose Check

In/Out→Check-Out.

3. Click the Viewer tab to display the data requirement item.

4. In the Check-Out dialog box, fill in the relevant fields and then click yes.

5. Click OK to edit the DRI in the Viewer pane.

6. In the Viewer pane, you can define the following fields:

Name Specifies the name of the data requirement

item.
Revision Specifies the revision ID. This is to track the
revision frequency.
Description Describes the DRI.
Event List Specifies the event table for generating an
event schedule. The data defined in the event
table sets the submittal delivery schedule.
Click the Add button to add a row to define
the following fields:
• Event Name
Denotes the contract event name.

• Start Date
Denotes the event start date.

• End Date
Denotes the event end date.

PLM00111 G Aerospace and Defense Solution Guide 9-9

Chapter 9 Managing contract data

• Offset
Denotes the offset used for calculating the
submittal due date for calculating the first
submittal delivery.

• Relative To
Denotes the relation of the offset to either
the start date or the end date.

• Recurrence: Denotes frequency of the

submittal delivery event.

• Recurrence End Date

Specifies the last date for event schedule.
DID Title Specifies the title of the document.
Exhibit Name Specifies the ID of a particular data item in a
data item description document.
Submit Purpose Specifies the purpose of the submitted data
item.
Cert Required Specifies whether the submitted data item
requires certification.
Distribution Required Specifies whether any documentation related
to the item should be distributed.
Office Primary Resp Specifies the name of the contacts, groups, or
role responsible for reviewing the data item.
Submit Flow Thru Specifies whether a supplier’s data
requirement item should be submitted as a
customer’s data requirement item.
Delivery Mechanism Specifies the mode of delivery of the contract.
Delivery Address Specifies the delivery address of the customer
or the supplier.
Submit Quantity Specifies the number of copies required for
submission.
Approval Required Specifies whether the customer needs to
approve the data item.
Media Type Specifies the format of the data, for example,
electrostatic, microfilm, and so on.
Shipping Document Reqd Specifies whether DD Form 250 is required for
the delivery of the data item.
Effective Cutoff Date Specifies the last date for data collection.
Comments Specifies any comments concerning the item.

9-10 Aerospace and Defense Solution Guide PLM00111 G

 Managing contract data

Effective Cutoff Event Desc. Specifies through explanation the last date for
data collection. Use a description that helps
you understand the purpose of selecting the
cutoff date.
Data Management Due Offset Specifies the offset of the data management
due date.
Response Due Offset Specifies offset to the response due date.
OPR Notif Due Offset Specifies the last date for the creation of
the notification to the office of the primary
reviewers.
Addressee Specifies the list of contacts needed to review
the contract.
Data Requirement Item Specifies the subtitle of the data requirement
Subtitle item.
Approval Code Specifies the approval code to be applied.

7. Click Save and Check-In.

Note • You must save any modification to the DRI before navigating to other
objects.

• The Cancel CheckOut button is unavailable.

Defining submittal delivery schedule

The tasks related to the contract are routed for review and approval through the
process of submittal. You must define a event list in the data requirement item to
generate submittal delivery schedule.
The submittal delivery schedule is based on a workflow process template. The
application assigns a workflow template automatically if it is not predefined.
For more information about creating workflow process templates, see the Workflow
Designer Guide.
Submittal represents the data item submittal package or documentation that relates
to the actual documents submitted. The data analyst creates a submittal delivery
schedule for the tasks. The supplier or the customer gets an idea about what to
deliver for each of the tasks assigned to them.
A submittal schedule is generated for each data requirement item based on the
submittal frequencies of the events as defined in the DRI. There can be one or more
submittals for each data requirement item depending on the frequency of delivery
dates.
Submittals are autogenerated and are then associated with tasks to generate
submittal delivery schedule. The data analyst user can also manually create a
submittal to generate a submittal delivery schedule.

PLM00111 G Aerospace and Defense Solution Guide 9-11

Chapter 9 Managing contract data

Generate a submittal delivery schedule

The data analyst user modifies the DRI revision to define the submittal delivery
events. This data is then used by the system to generate a draft submittal delivery
schedule.
The submittal is automatically created after the data analyst generates the submittal
delivery schedule. You can then modify this autogenerated schedule, if required.
1. In the Home pane, expand the data requirement item.

2. Right-click the data requirement item revision item and choose Generate
Submittal Delivery Schedule.

3. In the Generate Submittal Delivery Schedule dialog box, define the following
fields:

Process Specifies the task or the tasks sequence required to be followed.

Template
Note The application automatically creates a workflow
process if you do not have a predefined process
template to associate submittal schedule.
For more information about creating workflow process
templates, see the Workflow Designer Guide.
Task Duration Specifies the duration of the task.
Align Task Specifies the task coordination date.
Submittal Specifies the submittal type. The submittal value is selected
Type automatically.
Note If you have custom submittal types, perform the
following prerequisite tasks:
• Add the custom submittal types to the
ScheduleDeliverableWSOTypes preference.

• To set the default submittal type in the

Submittal Type list, create a preference named
DefaultSubmittalType with Protection Scope
as Group. Add the display name of your custom
submittal as the value of this preference.

4. Click OK.

Create submittals manually

You can also manually create a submittal schedule. The submittal monitors and
notifies the customer or the supplier regarding the pending tasks and what is
required to be delivered for each task assigned to them. After you create a submittal,
you must attach it to the submittal delivery schedule task.
1. From the menu bar, choose File→New→Item.

2. In the New Item dialog box, select submittal and then click Next.

9-12 Aerospace and Defense Solution Guide PLM00111 G

 Managing contract data

3. Define basic information for the new item, as follows:

ID/Revision - Name Specifies the submittal item identity and the

submittal item revision description. This is a
mandatory field.
Description Describes the submittal item. Use a
description that helps to distinguish the
purpose of the submittal item.

4. Click Next.

5. Define additional item information, as follows:

Title Specifies the title of the submittal object.

Author Specifies the name of the person, group, or the
role who initiated the submittal.
Subject Specifies the subject of the submittal.

6. Click Next.

7. Define additional item revision information, as follows:

DRI Item Type Specifies whether the data item requirement

is from a customer or a supplier.

Disposition Specifies the unique identifier for DD form 250

prepared for the contract deliveries.

Disposition Date Specifies the disposition or the incorporation

level of a change or submittal.

Document Author Specifies the author of the DRI.

Document Subject Specifies the subject of the DRI.

Document Title Specifies the title of the DRI.
Office Primary Resp Specifies the person, group, or the role
responsible for reviewing and acknowledging
the data item submittal.

Received Date Specifies the date when an item is received

from the supplier or a date when the item is
sent to a customer.
Resubmit Comments Specifies the customer’s comments during
resubmittal.
Resubmit Due Date Specifies the due date of the contract data
item to the customer.

PLM00111 G Aerospace and Defense Solution Guide 9-13

Chapter 9 Managing contract data

Resubmit Required Specifies whether the data item must be

submitted again.
Shipping Document Required Specifies the ID of DD Form 250 that is
prepared to support contract deliveries.
Submit Due Date Specifies the due date of the contract data
item to the customer.
Submittal Type Specifies the data item submittal stage, for
example, draft or final.

8. Click Finish.

Associate submittals with schedule deliverables

You can relate the data that is to be delivered to the submittal through Schedule
Manager. You must first associate the submitted deliverable to a schedule and then
initiate a task.
1. Open Schedule Manager to locate the submittal object.

2. Select the submittal object and then choose Schedule→Schedule Deliverables.

3. In the Schedule Deliverables dialog box, click the Add button to define the
following:

Name Specifies the name of the schedule deliverable.

Type Select Submittal.
Deliverable Specifies the submittal object that is
associated with a DRI.

Click the button to search for the

deliverable.

4. Click OK.

5. Expand the submittal object and select the task object.

6. Choose Schedule→Task Deliverables.

7. In the Task Deliverables dialog box, click the Add button to define the following:

Schedule Deliverable Specifies the name of the schedule deliverable.

9-14 Aerospace and Defense Solution Guide PLM00111 G

 Managing contract data

Submit Type Specifies the type of task.

Target
Select this to attach the deliverable as a
target attachment to the task workflow.

Reference
Select this to attach the deliverable as a
reference attachment to the task workflow.

Do Not Submit
Select this when no deliverable is attached
to the task workflow.
Deliverable Specifies the submittal object that is
associated with a DRI.

Click the button to search for the

deliverable.

8. Click OK.

9. Double-click the task deliverable object to define the workflow process.

10. In the Properties dialog box, edit the schedule tasks to define the workflow
process.
You can select a workflow template from the Workflow Template list.

11. Click OK.

Copy contracts
You can copy an existing contract along with the associated master schedule to
create a new contract and then modify appropriately. You must associate a DRI
and schedule it for submittal.
For more information about creating contract, see Create a contract.
1. From the Home pane, copy the contract item.

2. Choose File→Save As.

3. In the Save Item As dialog box, define the following:

ID / Revision - Name Specifies the identity of the contract and the

contract revision. This is a mandatory field.
Note If naming rules are configured at your
site, you can click the Assign button
to automatically generate the contract
ID and revision.

PLM00111 G Aerospace and Defense Solution Guide 9-15

Chapter 9 Managing contract data

Description Describes the contract item. Use a description

that helps to distinguish the purpose of the
item.

4. Click OK.

Providing feedback
Correspondence refers to any memo or letter related to the contract that requires
tracking between sender and receiver. It is often used when communication between
two or more organization must be tracked.
The data analyst receives offline feedback from customers. These feedback
documents are attached to the correspondence object that is created in Teamcenter.
The correspondence can be associated either to submittals or contracts.

Create correspondence
The data analyst creates a correspondence in Teamcenter and attaches the feedback
documents to the correspondence object.
1. From the menu bar, choose File→New→Item.

2. In the New Item dialog box, select Correspondence and then click Next.

3. Define basic information for the new item, as follows:

ID/Revision - Name Specifies the identity of the correspondence

and the correspondence item description
revision. This is a mandatory field.
Description Describes the correspondence item. Use a
description that helps you distinguish the
purpose of the correspondence item.

4. Click Next.

5. Define additional item information, as follows:

Correspondence Type Specifies a category of similar technical

documents, for example, assembly drawing,
wire list, or material specification.

6. Click Next.

7. Define additional item revision information, as follows:

Category Specifies correspondence category, for

example, memo.

9-16 Aerospace and Defense Solution Guide PLM00111 G

 Managing contract data

Correspondence Direction Specifies whether it is an incoming or an

outgoing correspondence.

Document Author Specifies the name of the person or the role

who initiated the correspondence.

Document Subject Specifies the subject of the correspondence.

Document Title Specifies the title of the correspondence.
Priority Specifies the priority level for accomplishing
the task.
Received Org Name Specifies the name of the receiving
organization.
Received or Sent Date Specifies the date of correspondence from the
supplier or the customer.
Reference Specifies the list of references.
Reply Requested Date Specifies the date of expected reply.
Reply Required Specifies whether a reply is required or not.
Responsible Party Specifies the person or roles responsible for
replying.

8. Click Finish.

Associate correspondence revision with a submittal revision

Communication related to the scheduled tasks should be associated with a submittal
revision.
1. Expand the correspondence object to locate the correspondence revision item.

2. Right-click to copy the correspondence revision item.

3. Navigate to submittal revision item.

4. Choose Edit→Paste Special.

5. In the Paste Special dialog box, select Correspondences from the Add As: list.

6. Click OK.

Associate correspondence with a contract revision

Communication related to the contract should be associated with correspondence
revision.
1. Expand the contract object to locate the contract revision item.

2. Right-click to copy the contract revision item.

3. Navigate to the correspondence revision item.

PLM00111 G Aerospace and Defense Solution Guide 9-17

Chapter 9 Managing contract data

4. Choose Edit→Paste Special.

5. In the Paste Special dialog box, select Contracts from the Add As: list.

6. Click OK.

9-18 Aerospace and Defense Solution Guide PLM00111 G

Chapter

10 Managing stock materials

Basic concepts about stock materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Install stock materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Configure the display of the Made From folder . . . . . . . . . . . . . . . . . . . . . . . 10-2

Creating a classification library for stock materials . . . . . . . . . . . . . . . . . . . . 10-3

Create stock materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

Add stock materials to the stock material library . . . . . . . . . . . . . . . . . . . . . . 10-4

Set stock material as program preferred stock material . . . . . . . . . . . . . . . . . 10-4

Assign stock material or standard part to a part . . . . . . . . . . . . . . . . . . . . . . 10-5

Assign stock materials to parts by using the copy-paste and drag drop
functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8

Managing stock materials using thin client . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9

Create stock material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Specify the stock material the part is made from . . . . . . . . . . . . . . . . . . 10-10

PLM00111 G Aerospace and Defense Solution Guide

Chapter

10 Managing stock materials

Basic concepts about stock materials

In the Aerospace and Defense industry many parts are made from stock materials
such as bar stock, tubing stock, and sheet stock. You can manage stock materials
in Teamcenter by:
• Creating a library of stock materials.

• Making the stock material the preferred stock material of a program.

• Assigning the stock material to a part.

The Aerospace and Defense industry typically manages stock materials as follows:
• The Teamcenter administrator creates a classification hierarchy or stock
material library using the Classification application.
For more information, see Creating a classification library for stock materials.

• The materials manager creates stock materials and adds them to the stock
material library.
For more information, see Create stock materials.

• The program administrator specifies the stock materials that are preferred to
the program. By doing this, only approved stock materials can be used in the
program.
For more information, see Set stock material as program preferred stock material.

• The design engineer creates a part and associates the part with the stock
material and specifies the dimensional properties of the stock material.
For more information, see Assign stock material or standard part to a part.

Install stock materials

1. Start Teamcenter Environment Manager (TEM).

2. Select the appropriate options until you reach the Select Features panel.

3. In the Select Features panel, expand the Extensions navigation tree.

4. Under Enterprise Knowledge Foundation, select Stock Materials to install the

stock material management functionality.

PLM00111 G Aerospace and Defense Solution Guide 10-1

Chapter 10 Managing stock materials

5. Click Next.

6. Select the appropriate options until you reach the Business Modeler IDE
Templates panel.

7. In the Business Modeler IDE Templates panel, select Stock Materials.

8. Click Next and select the appropriate options until you complete the installation.
For more information, see the Installation on UNIX and Linux Servers Guide or
Installation on Windows Servers Guide and Teamcenter Environment Manager
Help.

9. After completing the TEM installation, install the Web tier and deploy the web
applications.
For more information, see the Installation on UNIX and Linux Servers Guide or
Installation on Windows Servers Guide.

Configure the display of the Made From folder

To add the Made From relation to an object and add the Made From folder to an
object:
1. In My Teamcenter, choose Edit→Options.
The Options dialog box is displayed.

2. Choose General→Item Revision.

3. Click the General tab and do the following:

a. From the Item Revision type list, select the object that must have the Made
From relation, for example, ItemRevision or Part Revision.

b. From the Available Relations list, choose Made From and add it to the
Shown Relations list.

4. Click the Related Object tab and do the following:

a. From the Item Revision type list, select the object which must have the
Made From folder, for example, ItemRevision or Part Revision.

b. From the Available Relations list, choose Made From and add it to the
Shown Relations list.

5. Click OK.

The Made From relation and folder is added to the object.

10-2 Aerospace and Defense Solution Guide PLM00111 G

 Managing stock materials

Creating a classification library for stock materials

Use the Classification Administration application to create a stock material library.
• In Classification Administration, create a class.
Ensure that you unselect the Abstract option.

• To add attributes to the class, click the Add Attributes button.

For example, a stock material called Sheet can have an attribute called thickness.

• If the attributes are not available, you can create the attributes using the
Dictionary feature.

For more information about creating a class and adding attributes to it, see the
Classification Administration Guide.

Create stock materials

1. From My Teamcenter, choose File→New→Item.

2. Select Stock Material from the New Item dialog box.

Click Next.

3. In the Object Create Information dialog box enter the following information:
Configuration Item?
Specifies if the stock material is a configuration item.
Description
Describes the stock material.
ID
Specifies the stock material ID.
(Optional) Click the Assign button to auto assign the ID.
Name
Specifies the name of the stock material.

PLM00111 G Aerospace and Defense Solution Guide 10-3

Chapter 10 Managing stock materials

Unit of Measure
Specifies the metric for the stock material.

4. Click Next.
Specify additional information about the stock material in the following dialogs.

5. Click Finish.

Add stock materials to the stock material library

1. Right-click the stock material and choose Send To→Classification.
The Classification application displays a message asking if you want to classify
the object.

2. Click Yes in the Classify Object dialog box.

The dialog box closes and the object ID is displayed in the Properties pane.

3. Browse the hierarchy tree to locate the stock material class that best matches
the characteristics of the stock material being classified.

4. Right-click the storage class and choose Select. You can also double-click the
storage class to display the attributes.
The attributes associated with the selected stock material library are displayed
in the Properties pane.

5. Type values for the stock material attributes in the Attribute values section.
You can only enter Attribute values if you have added Attribute values for the
classification class.

6. Click the Save button on the toolbar to add the stock material to the stock
material library.

For more information about classifying objects, see the Classification Guide.

Set stock material as program preferred stock material

1. In My Teamcenter, select the stock material and choose Copy.

2. In the Program application, expand the program where you want to add the
stock material.

3. Select the Preferred Items folder and choose Paste.

The stock material is now the preferred stock material of the program.

10-4 Aerospace and Defense Solution Guide PLM00111 G

 Managing stock materials

Assign stock material or standard part to a part

1. In My Teamcenter, right-click the part revision to which you want to add the
stock material, and choose Make From.
The My Teamcenter application shows the Make From dialog box.

2. Select Stock Material or Part from the Make From list.

3. Click any one of the following options from Select Search:

a. Classification: To search for stock materials in the classification hierarchy.

b. By Name: To search for stock materials by name.

4. Click the button next to the Select Stock Material box.

5. If you select the Classification option, the Classification Search dialog box
appears.

a. Type the search criteria in the search fields and click Search.
The search results appear in the Table tab.

PLM00111 G Aerospace and Defense Solution Guide 10-5

Chapter 10 Managing stock materials

For more information about Classification search, see the Classification

Guide.

b. Select the stock material you want and click OK.

The stock material appears in the Select Stock Material box.

6. If you select the By Name option, the Open By Name dialog box appears.

a. Type the name of stock material in the Name box and click the Find button.

b. Select the stock material you want and click OK.

The stock material appears in the Select Stock Material box.

10-6 Aerospace and Defense Solution Guide PLM00111 G

 Managing stock materials

7. In the Make From dialog box, type the values for the following dimensions:

a. Cut Length

b. Cut Thickness

c. Cut Width

d. Quantity

8. Type the quantity of the stock material required in the Quantity box.

9. Select the unit of measure for the stock material from the Unit of Measure list.

10. Click OK.

The stock material appears in the Made From pseudo folder of the part revision.

Note The Make From list supports only Stock Material and Part. To add other
objects to the Made From pseudo folder, see Assign stock materials to parts
by using the copy-paste and drag drop functionality.
The custom properties you add to the Make From relation are not available
when you assign a stock material using the Make From dialog box. To
get these custom properties, assign stock materials using the copy-paste
special functionality. The custom properties are shown in the Properties on
Relation dialog box.

PLM00111 G Aerospace and Defense Solution Guide 10-7

Chapter 10 Managing stock materials

Assign stock materials to parts by using the copy-paste and drag

drop functionality
Assign stock materials to parts, using the copy-paste functionality
1. Right-click the stock material and choose Copy.

2. Right-click the Made From folder of the part revision and choose Paste.
The Made From dialog box appears.

3. In the Made From dialog box, type the values for the following dimensions:
a. Cut Length

b. Cut Thickness

c. Cut Width

d. Stock Quantity

4. Select the unit of measure for the stock material from the Unit of Measure list.

5. Click Finish.
Assign stock materials to parts, using the copy and paste special
functionality
1. Right-click the stock material and choose Copy.

2. Select the part revision and choose Edit→Paste Special.

10-8 Aerospace and Defense Solution Guide PLM00111 G

 Managing stock materials

3. From the Paste Special dialog, select Made From.

The Made From dialog box appears.

4. In the Made From dialog box, type the values for the following dimensions:
a. Cut Length

b. Cut Thickness

c. Cut Width

d. Stock Quantity

5. Select the unit of measure for the stock material from the Unit of Measure list.

6. Click Finish.
Assign stock materials to parts, using the drag drop functionality
1. Drag the stock material to the Made From folder of the part revision.
The Made From dialog box appears.

2. In the Made From dialog box, type the values for the following dimensions:
a. Cut Length

b. Cut Thickness

c. Cut Width

d. Stock Quantity

3. Select the unit of measure for the stock material from the Unit of Measure list.

Teamcenter adds the stock material to the Made From folder of the part revision.

Managing stock materials using thin client

Create stock material
1. In My Teamcenter, choose New→Item.

2. In the New Item dialog, select Stock Material from the Type list.
Click Next.

3. In the Stock Material Information tab, add the following information:

a. ID: Specifies the ID of the stock material.

b. Revision: Specifies the revision ID of the stock material.

c. Name: Specifies the name of the stock material.

d. Description: Describes the stock material.

PLM00111 G Aerospace and Defense Solution Guide 10-9

Chapter 10 Managing stock materials

e. Unit of Measure: Specifies the metric for the stock material.

4. Click Next.
Specify additional information about the stock material in the following dialogs.

5. Click Finish.

Specify the stock material the part is made from

1. From My Teamcenter, select a part or item revision and choose Tools→Make
From.
Teamcenter displays the Make From dialog box.

2. Select Stock Material or Part from the Make From list.

3. Search for the stock material from the Select Stock Material box.
Teamcenter shows the cut dimension boxes depending on the stock material
you select.

4. Type values for the cut dimensions of the stock material.

5. Type the quantity of the stock material required in the Stock Quantity box.

6. Select the unit of measure for the stock material from the Unit of Measure list.

7. Click OK.

The stock material is added to the MakeFrom folder of the part or item revision.
Note The custom properties you add to the Make From relation are not available
when you assign a stock material, using the Make From dialog box. To get
these custom properties, assign stock materials using the copy and paste
special functionality. The custom properties are shown in the Properties on
Relation dialog box.

10-10 Aerospace and Defense Solution Guide PLM00111 G

Chapter

11 Managing work packages

Basic concepts about work packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Install work packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Create a work package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Add objects to a work package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3

Managing work packages using the thin client . . . . . . . . . . . . . . . . . . . . . . . 11-3

Create a work package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Add objects to work package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

PLM00111 G Aerospace and Defense Solution Guide

Chapter

11 Managing work packages

Basic concepts about work packages

A work package or package is typically any collection of CAD files and documentation
that an outsourcing partner requires to build, test, or maintain a component or
subassembly of a larger product.
A package serves as a revisable collection of product information and can be used
in a variety of contexts.
The Aerospace and Defense industry typically uses work packages as follows:
• The Designer creates a work package and specifies the work associated with
the work package.
For more information, see Create a work package.

• The Designer adds objects to work packages. The objects can have static or
dynamic relationship with the work package.
Objects that have static relationship are generally reference items and do not
change over time, for example, a design document.
Objects that have a dynamic relationship always show the latest revision.
For more information, see Add objects to a work package.

• The Designer submits the work package to a workflow.

For more information about initiating a workflow, see the My Teamcenter Guide.

• When the work associated with the work package is complete, it is released with
a maturity status indicating the completion of work.
You can use a workflow or change management functionalities to release the
work package.

Install work packages

1. Start Teamcenter Environment Manager (TEM).

2. Select the appropriate options until you reach the Select Features panel.

3. In the Select Features panel, expand the Extensions navigation tree.

4. Under Enterprise Knowledge Foundation, select Work Packages to install the

stock material management functionality.

PLM00111 G Aerospace and Defense Solution Guide 11-1

Chapter 11 Managing work packages

5. Click Next.

6. Select the appropriate options until you reach the Business Modeler IDE
Templates panel.

7. In the Business Modeler IDE Templates panel, select Work Packages.

8. Click Next and select the appropriate options until you complete the installation.
For more information, see the Installation on UNIX and Linux Servers Guide or
Installation on Windows Servers Guide and Teamcenter Environment Manager
Help.

9. After completing the TEM installation, install the Web tier and deploy the web
applications.
For more information, see the Installation on UNIX and Linux Servers Guide or
Installation on Windows Servers Guide.

Create a work package

1. From My Teamcenter, choose File→New→Item.

2. Select Work Package from the New Item dialog box.

Click Next.

3. In the Object Create Information dialog box, enter the following information:
Configuration Specifies if the work package is a configuration item.
Item?
Description Describes the work package.
ID Specifies the ID of the work package.
Click the Assign button to auto assign the ID.
Name Specifies the name of the work package.
Unit of Specifies the metric for the work package.
Measure
Work Package Specifies the level of difficulty for executing the work package.
Complexity
Work Package Specifies the security level of the work package.
Security
Work Package Specifies if the work package is executed internally or by a
Type supplier.
Work Package Specifies the name of the vendor executing the work package.
Vendor

4. Click Next.
Specify additional information about the work package in the following dialogs.

5. Click Finish.

11-2 Aerospace and Defense Solution Guide PLM00111 G

 Managing work packages

Add objects to a work package

Objects can have a static or dynamic relationship with the work package.
Static relations show objects with the original revision in the work package. To create
a static relationship, add the object to the Static Contents folder of the work package.
Dynamic relations always show objects with the latest revision. When you revise the
objects outside the work package, the work package will show the latest revision. To
create a dynamic relationship, add the object to the Dynamic Contents folder.
You can add objects to the work package in the following ways:

Drag the object to the work package

• Drag the object to the Static Contents or the Dynamic Contents folder of he
work package.

Copy and paste the object to the work package

• Copy and paste the object to the Static Contents or the Dynamic Contents folder
of the work package.

Use copy and paste special functionality to add objects to the work package
• Right-click the object and choose Copy.

• Select the work package and choose Edit→Paste Special.

• From the Paste Special dialog box, choose Static Contents to create a static
relationship or Dynamic Contents to create a dynamic relationship.

Managing work packages using the thin client

Create a work package

1. In My Teamcenter, choose New→Item.

2. In the New Item dialog, select Work Package from the Type list.
Click Next.

3. In the Work Package Information tab, add the following information:

ID Specifies the ID of the work package.
Click the Assign button to auto assign the ID.
Revision Specifies the revision ID of the work package.
Click the Assign button to auto assign the revision ID.
Name Specifies the name of the work package.
Description Describes the work package.
Unit of Specifies the metric for the work package.
Measure

PLM00111 G Aerospace and Defense Solution Guide 11-3

Chapter 11 Managing work packages

4. Click Next.
In the Additional Work Package Information dialog box, add the following
information:

Work Package Specifies if the work package is executed internally or by a

Type supplier.
Work Package Specifies the security level of the work package.
Security
Work Package Specifies the name of the vendor executing the work package.
Vendor
Work Package Specifies the level of difficulty for executing the work package.
Complexity

5. Click Next.
Specify additional information about the stock material in the following dialogs.

6. Click Finish.

Add objects to work package

Objects can have static or dynamic relationship with the work package.
Static relations show objects with the original revision in the work package. To create
a static relationship, add the object to the Static Contents folder of the work package.
Dynamic relations always show objects with the latest revision. Even when you
revise the objects outside the work package, the work package will show the latest
revision. To create a dynamic relationship, add the object to the Dynamic Contents
folder.
You can add objects to the work package in the following ways:

Copy and paste the object to the work package

• Copy and paste the object to the Static Contents or the Dynamic Contents folder
of the work package.

Use copy and paste special functionality to add objects to the work package
• Select the object and choose Edit→Copy.

• Select the work package and choose Edit→Paste Special.

• From the Paste Special dialog box, choose Static Contents to create a static
relationship or Dynamic Contents to create a dynamic relationship.

11-4 Aerospace and Defense Solution Guide PLM00111 G

Chapter

12 Managing finishes

Basic concepts about finishes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Install finishes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Configure finishes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Create a library of finish and finish groups . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Create a finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Create a finish group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4

Add finishes to a finish group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

Apply a finish or finish group to an item revision . . . . . . . . . . . . . . . . . . . . . . 12-5

Apply a finish or finish group to an item revision using the drag drop or copy-paste
functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

Apply a finish or finish group to an item occurrence . . . . . . . . . . . . . . . . . . . . 12-7

Managing finishes using the thin client . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Create a finish . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Create a finish group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8
Apply a finish or finish group to an item revision . . . . . . . . . . . . . . . . . . . 12-9
Apply a finish or finish group to an item occurrence . . . . . . . . . . . . . . . . . 12-9

PLM00111 G Aerospace and Defense Solution Guide

Chapter

12 Managing finishes

Basic concepts about finishes

A finish represents a finishing process on a part. It may be used to improve
appearance, adhesion, corrosion resistance, tarnish resistance, chemical resistance,
wear resistance, remove burrs, and so on. For example, you can apply a finishing
process on a part by cleaning, priming, and painting it.
You can group the finishes together to create a finish group. You can specify the
order of execution of finishes in the finish group. For example, you can create a finish
group called Preserve that contains finishes named Clean, Prime, and Paint.
The following is an example process of how finishes are used:
• The finish manager creates a library of finish and finish groups, using the
Classification application.
For more information, see Create a library of finish and finish groups.

• The finish manager creates a finish.

For more information, see Create a finish.

• The finish manager creates a finish group.

For more information, see Create a finish group.

• The design engineer applies the finish and finish group to a part.
For more information, see Apply a finish or finish group to an item revision.

• The design engineer applies the finish or finish group to a part occurrence.
For more information, see Apply a finish or finish group to an item occurrence.

• The manufacturing engineer views the finishes and performs the finish job on
the part.

PLM00111 G Aerospace and Defense Solution Guide 12-1

Chapter 12 Managing finishes

Install finishes
1. Start Teamcenter Environment Manager (TEM).

2. Select the appropriate options until you reach the Select Features panel.

3. In the Select Features panel, expand the Extensions navigation tree.

4. Under Enterprise Knowledge Foundation, select Finish Management to install

the finish management functionality.

5. Click Next.

6. Select the appropriate options until you reach the Business Modeler IDE
Templates panel.

7. In the Business Modeler IDE Templates panel, select Finish Management.

8. Click Next and select the appropriate options until you complete the installation.
For more information, see the Installation on UNIX and Linux Servers Guide or
Installation on Windows Servers Guide and Teamcenter Environment Manager
Help.

9. After completing the TEM installation, install the Web tier and deploy the web
applications.
For more information, see the Installation on UNIX and Linux Servers Guide or
Installation on Windows Servers Guide.

Configure finishes
Update the values of the following preferences to configure finishes:
• UsingAssignFinishDialog
Update the value to TRUE to see the Open by Name dialog box or FALSE to
see the Classification Search dialog box when you choose the Assign Finish
command.
By default, the value of this preference is set to TRUE.

• ItemRevision_DefaultChildProperties
Update the preference with the value Fsh0FinishRel to add the finish object as
the child of an item revision.
This preference along with the ItemRevision_PseudoFolder preference allows
you to create the Finishes folder under item revision.
To add the finish as a child of other objects, update the respective child property
preferences of the objects. For example, to add the finish as a child of the part
revision object, update the PartRevision_ DefaultChildProperties preference
with the value Fsh0FinishRel.

12-2 Aerospace and Defense Solution Guide PLM00111 G

 Managing finishes

Note When you update this preference with the Fsh0FinishRel value, the
finish is added as a child property of the finish revision object.
To remove finish as a child property of finish relation:
1. Open the Options dialog box using the Edit→Options menu
command.

2. Select General→Item Revision.

3. Select the General tab.

4. Select Finish Revision from the Select Item Revision type list.

5. Remove Finishes from the Shown Relations list.

• ItemRevision_PseudoFolder
Update the preference with the value Fsh0FinishRel to add the Finishes folder
under item revision.
To add the Finishes folder to other objects, update the respective
folder preferences of the objects. For example, update the
PartRevision_PseudoFolder preference with the value Fsh0FinishRel to
add the Finishes folder under part revision object.
Note When you update this preference with the Fsh0FinishRel value, the
Finishes folder is also added to the finish revision object.
To remove the Finishes folder from finish revision:
1. Open the Options dialog box, using the Edit→Options menu
command.

2. Select General→Item Revision.

3. Select the Related Object tab.

4. Select Finish Revision from the Select Item Revision type list.

5. Remove Finishes from the Shown Relations list.

Create a library of finish and finish groups

Use the Classification Administration application to create a library for finish and
finish groups.

• In Classification Administration, create a class.

Ensure that you unselect the Abstract option.

For more information about creating a class and adding attributes to it, see the
Classification Administration Guide.

PLM00111 G Aerospace and Defense Solution Guide 12-3

Chapter 12 Managing finishes

Create a finish
1. From My Teamcenter, choose File→New→Item.

2. Select Finish from the New Item dialog box.

Click Next.

3. In the Object Create Information dialog box, enter the following information:
Finish ID Specifies the ID of the finish.
Revision Specifies the revision ID of the finish.
Name Specifies the name of the finish.
Description Describes the finish.

4. Click Next.
Specify additional information about the finish in the following dialogs.

5. Click Finish.

Create a finish group

Note Copy the finishes that you want to add to the finish group before creating it.

1. From My Teamcenter, choose File→New→Item.

2. Select Finish Group from the New Item dialog box.

Click Next.

3. In the Object Create Information dialog box, enter the following information:
Finish Group Specifies the ID of the finish group.
ID
Revision Specifies the revision ID of the finish group.
Name Specifies the name of the finish group.
Description Describes the finish group.
Finish Items Specifies the finishes to be associated with the finish group.
To add finishes, ensure that you copy the finishes to the
clipboard.
a. Click the Expand to modify button .

b. Click the Add objects from Clipboard button .

Teamcenter adds the finish objects to the Finish Items list.

4. Click Next.
Specify additional information about the work package in the following dialogs.

12-4 Aerospace and Defense Solution Guide PLM00111 G

 Managing finishes

5. Click Finish.

Add finishes to a finish group

After creating a finish group, you can add finishes to the finish group as follows:
1. Right-click a finish group revision and choose Check-In/Out→Check Out

2. Click Yes in the Check-Out dialog box to check out the finish group.

3. Select the Summary view of the finish revision and choose the Finishes tab.

4. Click Add Finish button to open the Add Finish dialog.

5. Search for the finish in the Add Finish dialog box and click Find.

6. Select the finishes you want and click OK.

The finishes are added in the Finishes section.

7. To reorder the sequence of finishes in the Finish Sequence section:

a. Click the Expand to modify button .

b. Select the finish and move it up or down the sequence by using the Move
selected objects up or Move selected objects up buttons.

8. Right-click the finish group revision and choose Check-In/Out→Check In.

9. Click the Yes button in the Check-In dialog box.

The finishes are now added to the finish group.

Apply a finish or finish group to an item revision

1. Right-click an item revision and choose Assign Finish.

PLM00111 G Aerospace and Defense Solution Guide 12-5

Chapter 12 Managing finishes

If the value set in the UsingAssignFinishDialog preference is TRUE, you see

the Assign Finish/Finish Groups dialog box and if the value is FALSE, you see
the Classification Search dialog box.

2. If you see the Assign Finish/Finish Groups dialog box, type the name of the
finish or finish group in the Name box.
OR
Type the ID of the finish or finish group in the Finish ID box.
Click Find.

3. Select the finishes you want and click OK.

The selected finish and finish groups are added to the Finishes folder of the
item revision.

4. If you see the Classification Search dialog box, type the search criteria in the
search fields and click Search.
The search results appear in the Table tab.

For more information about Classification search, see the Classification Guide.

5. Select the finishes you want and click OK.

12-6 Aerospace and Defense Solution Guide PLM00111 G

 Managing finishes

The selected finish and finish groups are added to the Finishes folder of the
item revision.

Apply a finish or finish group to an item revision using the drag drop
or copy-paste functionality
Drag the finish or finish group to the item revision

• Drag the finish or finish group to the Finishes folder of the item revision.

Copy and paste the finish or finish group to the item revision

• Copy and paste the finish or finish group to the Finishes folder of the item
revision.
Use the copy and paste special functionality to add finish or finish group
to the item revision

• Right-click the finish or finish group and choose Copy.

• Select the item revision and choose Edit→Paste Special.

• From the Paste Special dialog box, choose Finishes.

The finish or finish group is added to the Finishes folder of the item revision.

Apply a finish or finish group to an item occurrence

Ensure that trace links are enabled.
For more information about enabling and creating trace links, see the Systems
Engineering Guide.
1. Open a product structure in Structure Manager and set in-context mode on the
applicable parent line.

2. Select the source object and choose Tools→Trace Link→Start Trace Link.

3. In My Teamcenter, select the finish or finish group and choose Tools→Trace

Link→End Trace Link....
The Create Trace Link dialog box appears.

4. In the list of subtypes on the left, select Finishes.

5. Type the name and description for the trace link in the Name and Description
boxes respectively.

6. Click OK.

A finish is now applied to an item occurrence.

PLM00111 G Aerospace and Defense Solution Guide 12-7

Chapter 12 Managing finishes

Managing finishes using the thin client

Create a finish
1. In My Teamcenter, choose New→Item.

2. In the New Item dialog, select Finish from the Type list.
Click Next.

3. In the Finish Group Information tab, add the following information:

Finish ID Specifies the ID of the finish.
Revision Specifies the revision ID of the finish.
Name Specifies the name of the finish.
Description Describes the finish.

4. Click Next.
Specify additional information about the finish in the dialogs that appear
subsequently.

5. Click Finish.

Create a finish group

Note If you want to add finish to finish groups, copy the finishes to the clipboard
before creating the finish group.

1. In My Teamcenter, choose New→Item.

2. In the New Item dialog, select Finish Group from the Type list.
Click Next.

3. In the Finish Group Information tab, add the following information:

Finish Group Specifies the ID of the finish group.
ID
Revision Specifies the revision ID of the finish group.
Name Specifies the name of the finish group.
Description Describes the finish group.
Finish Items Adds finishes to the finish group.
To add finishes, ensure that you copy the finishes to the
clipboard.
• Click the Paste button to add finishes.

4. Click Next.
Specify additional information about the finish group in the following dialogs.

5. Click Finish.

12-8 Aerospace and Defense Solution Guide PLM00111 G

 Managing finishes

Apply a finish or finish group to an item revision

1. In My Teamcenter, select an item revision and choose New→Assign Finish.
The Item dialog box appears.

2. Search for finishes or finish groups and click Find.

3. In the Search Results dialog box, select the finish or finish group.
Click OK.

The finish or finish group is added to the Finishes folder to the item revision.

Apply a finish or finish group to an item occurrence

Ensure that trace links are enabled.
1. In My Teamcenter, select the source object and choose Tools→Start Trace Link.

2. In My Teamcenter, select the finish or finish group and choose Tools→End Trace
Link.

A finish is now applied to an item occurrence.

PLM00111 G Aerospace and Defense Solution Guide 12-9

Chapter

13 Managing configuration audits

Basic concepts about configuration audits . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Setting up configuration audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Create a configuration audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Create an action item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Associating related objects with the configuration audit and action item . . . . . 13-5

Managing configuration audits using the thin client . . . . . . . . . . . . . . . . . . . 13-5

Create a configuration audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Create an action item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Associating related objects with the configuration audit . . . . . . . . . . . . . . 13-7

PLM00111 G Aerospace and Defense Solution Guide

Chapter

13 Managing configuration audits

Basic concepts about configuration audits

Configuration audits helps validate if the functional and physical requirements of a
product meet the requirements specified in the product configuration documentation.
Configuration audit helps to:
• Ensure that the product design provides the agreed-to performance.

• Validate the consistency between a product and its associated configuration

documentation.

• Determine that adequate processes are in place to support production.

You can perform different types of configuration audits such as Functional

Configuration Audit (FCA) and Physical Configuration Audits (PCA).
The findings of the configuration audit results in action items. The action items
represent the request for actions raised during the audit.
The following is an example process of how configuration audits are performed:
• The compliance auditor performs a configuration audit on a product or
deliverable and creates a configuration audit item in Teamcenter.
The auditor adds the objects being audited to the Audits Item folder of the
configuration audit and adds the objects affected by the audit to the Impacted
Items folder of the configuration audit. Example: If an engine assembly is
audited, it is added to the Audits Item folder and the subassemblies of the
engine such as motor assembly and blade assembly are added to the Impacted
Items folder.

Based on the findings of the audit, the auditor suggests action items.

PLM00111 G Aerospace and Defense Solution Guide 13-1

Chapter 13 Managing configuration audits

• The change manager creates action items and associates the action item with
the configuration audit.

• The change manager also associates the action item with the affected item.
Example: The affected item, the blade assembly is added to the Problem Items
folder of the action item.

• The change manager associates the action item to a change request and then
sends the change request through a change management workflow process.
If the action item is resolved using a formal change process, the items in the
folders of the action item are propagated to the change request by using the
Derive functionality.

Setting up configuration audits

Set the following business object constants:
• Cm0AuditsItemCreCondition
Specifies the condition to use for checking the status of the configuration audit
before the creation of an Audits Items relation.

• Cm0HasContractCreCondition
Specifies the condition to use for checking the status of the configuration audit
before the creation of a Has Contract relation.

• Cm0RaisesActionItemsCreCondition
Specifies the condition to use for checking if the closure status of the
configuration audit is open and the Audits Item relationship is established before
the creation of the Raises Action Item relation.

For more information about business objects constants, see the Business Modeler
IDE Guide.

13-2 Aerospace and Defense Solution Guide PLM00111 G

 Managing configuration audits

Create a configuration audit

1. From My Teamcenter, choose File→New→Audit.

2. Select Configuration Audit from the New Item dialog box.

Click Next.

3. In the New Audit dialog box, enter the following information:

Audit Number
Specifies the ID for the configuration audit.
Revision
Specifies the revision ID for the configuration audit.
Synopsis
Specifies the name of the configuration audit.
Description
Describes the configuration audit.
Audit Type
Specifies the type of audit. You can choose from the following audit types:
a. PCA
Specifies a Physical Configuration Audit.

b. FCA
Specifies a Functional Configuration Audit.

c. CDR
Specifies a Critical Design Review.

d. PDR
Specifies a Preliminary Design Review.

e. TRR
Specifies a Test Readiness Review.

Process Date
Specifies the date on which the configuration audit is conducted.
Comments
Specifies any other information about the configuration audit.

4. Click Finish.

After creating a configuration audit, add the object being audited to the Audits Item
folder of the configuration audit item. You can add objects to the Audits Item folder
using the copy-paste method.
You can also initiate a change management workflow on the configuration audit.

PLM00111 G Aerospace and Defense Solution Guide 13-3

Chapter 13 Managing configuration audits

Create an action item

Note Ensure that the object being audited is added to the Audits Item folder of the
configuration audit item. If you do not do this, the action items will not be
added to the Raises Action Items folder of the configuration audit item.
Use the copy-paste method to add the object being audited to the Audits
Item folder.

1. Right-click a configuration audit revision and choose Raise Action Item.

2. Select Action Item from the Add New Action Item dialog box.
Click Next.

3. In the Add New Action Item dialog box, add the following information:
Action Item Number
Specifies the ID for the action item.
Revision
Specifies the revision ID for the action item.
Synopsis
Specifies the name of the action item.
Description
Describes the action item.
Action Type
Specifies the type of action item. You can choose from the following action
types:
a. Audit
Specifies an audit.

b. CCR
Specifies a Configuration Change Request.

c. RFA
Specifies a Request for Action.

d. RFI
Specifies a Request for Information.

Comments
Specifies any other information about the action item.
Impacts
Specifies the impacted item.
Office Primary Responsible
Specifies the person or office responsible for the action item.

13-4 Aerospace and Defense Solution Guide PLM00111 G

 Managing configuration audits

Zones
Specifies the product zones affected by the action item.

4. Click Finish.

The action item is added to the Raises Action Items folder of the configuration audit.

Associating related objects with the configuration audit and action

item
To associate objects to a configuration audit, copy-paste or drag the object to the
relevant folder of the configuration audit. You can add objects to the following folders:
• Impacted Items
Add objects that are impacted by the audit.

• Audits Item
Add objects that are being audited.

• Contract
Add contract documents for the objects being audited.

To associate objects to an action item, copy-paste or drag the object to the relevant
folder of the action item revision. You can add objects to the following folders:
• Problem Items
Add part revisions that the action item is meant to address.

• Reference Items
Add any Teamcenter object, including datasets, that reference related
information.

• Implemented By
Add change object revisions that are referenced by the action item.

• Raised by Audit
Contains the configuration audit item.

Managing configuration audits using the thin client

Create a configuration audit
1. In My Teamcenter, choose New→Audit.

2. In the New Item dialog, select Configuration Audit from the Type list.
Click Next.

3. In the Configuration Audit Information tab, add the following information:

PLM00111 G Aerospace and Defense Solution Guide 13-5

Chapter 13 Managing configuration audits

Audit Number
Specifies the ID for the configuration audit.
Revision
Specifies the revision ID for the configuration audit.
Synopsis
Specifies the name of the configuration audit.
Description
Describes the configuration audit.
Audit Type
Specifies the type of audit. You can choose from the following audit types:
a. PCA
Specifies a Physical Configuration Audit.

b. FCA
Specifies a Functional Configuration Audit.

c. CDR
Specifies a Critical Design Review.

d. PDR
Specifies a Preliminary Design Review.

e. TRR
Specifies a Test Readiness Review.

Process Date
Specifies the date on which the configuration audit is conducted.
Comments
Specifies any other information about the configuration audit.

4. Click Finish.

Create an action item

1. In My Teamcenter, select a configuration audit revision and choose Tools→Raise
Action Item.

2. In the New Action Item dialog box, select Action Item from the Type list.
Click Next.

3. In the Configuration Audit Information tab, add the following information:

Action Item Number
Specifies the ID for the action item.

13-6 Aerospace and Defense Solution Guide PLM00111 G

 Managing configuration audits

Revision
Specifies the revision ID for the action item.
Synopsis
Specifies the name of the action item.
Description
Describes the action item.
Action Type
Specifies the type of action item.
Comments
Specifies any other information about the action item.
Impacts
Specifies what items are impacted by the action item.
Office Primary Responsible
Specifies the person or office responsible for the action item.
Zones
Specifies the product zones affected by the action item.

4. Click Finish.

Associating related objects with the configuration audit

To associate objects to a configuration audit, copy-paste the object to the relevant
folder of the configuration audit. You can add objects to the following folders:
• Impacted Items
Add objects which are impacted by the audit.

• Audits Items
Add objects which are being audited.

• Contract
Add contract documents for the objects being audited.

PLM00111 G Aerospace and Defense Solution Guide 13-7

Chapter

14 Searching for Aerospace and

Defense items

PLM00111 G Aerospace and Defense Solution Guide

Chapter

14 Searching for Aerospace and

Defense items

You can use the Teamcenter search functionality to search for Aerospace and
Defense items.
For more information about using search, see the Rich Client Interface Guide.
In addition to Teamcenter search, you can use the following Aerospace and Defense
search forms:

Search form Description

Find ADSDesign Returns design items according to the criteria
you specify.
Find ADSDrawing Returns drawing items according to the criteria
you specify.
Find ADSPart Returns part items according to the criteria you
specify.
FindADSTechDocument Returns technical document items according to
the criteria you specify.
Find All Change Notice Returns all change notice revisions. You do not
Revisions specify criteria for this query.
Find Organization Returns the list of organizations. You do not
specify criteria for this query.

The GroupBasedProjects search form in the standard Teamcenter installation

can be used with programs. This query returns the list of programs that a specified
group is working on.
Note Standard change item searches do not return the Aerospace and Defense
change items. You must configure search forms to work with Aerospace
and Defense change items.

PLM00111 G Aerospace and Defense Solution Guide 14-1

Appendix

A Aerospace and Defense Training

Program

Aerospace and Defense training program . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Install the training program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Training program reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
ADSTrngCondition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
AnDCMTrainingProgramCondition . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
TrngNamingRule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Adc0TrngNamingRule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Revision naming rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
TrngRevNamingRule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Adc0TrngRevNamingRule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Lists of values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Adc0Change Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Adc0Change Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Adc0CN Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Adc0CR Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Adc0DR Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Adc0Production Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
Adc0Quotation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Adc0Task Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
ADS Trng Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
ADS Trng DOC Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
ADS Trng DWG Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
ADS Trng PL Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
ADS Trng SDRL Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
ADS Trng Design Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13
ADS Trng Dist Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14
ADS Trng Part Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

PLM00111 G Aerospace and Defense Solution Guide

Appendix

A Aerospace and Defense Training

Program

Aerospace and Defense training program

The Training program is a default program that is created on your system when
you choose to install the Aerospace and Defense Training Program template
along with the Aerospace and Defense Foundation template. The training
program helps you learn how to create and organize necessary data in the context
of a program.
Note The Aerospace and Defense Training Program template is dependent
on the Aerospace and Defense Foundation template.

Install the training program

1. Access the Teamcenter Environment Manager (TEM) installer.

2. In the Solutions pane, select Aerospace and Defense.

3. In the Select Features pane, select Vendor Management, Aerospace and

Defense Foundation, and Aerospace and Defense Training Program.
Note The Aerospace and Defense Training Program template is
dependent on the Aerospace and Defense Foundation template. You
must select both the features to install the training program.

4. If this is a new installation, enter the directory in which you want to install
Teamcenter in the Installation Directory box. Specify a directory that does
not exist. Teamcenter Environment Manager (TEM) creates the directory you
specify.
On successful installation, two training programs are created in the database.

Program ID Description
Training Provides an example of how to create and
organize data for a document-centric program.
Training-Part Centric Provides an example of how to create and
organize data for a part-centric program.

PLM00111 G Aerospace and Defense Solution Guide A-1

Appendix A Aerospace and Defense Training Program

Training program reference

Aerospace and Defense Training Program provides a preconfigured
program with rules and lists of values that are saved in the
adstrainingprogram_template.xml file.
The following components are included in the template:
• Conditions

• Naming rules

• Revision naming rules

• Lists of values

Programs
Programs provide a mechanism for organizing data and implementing access control
based on program membership. Data assigned to programs can be searched for and
viewed in the context of the program and can be distributed across multiple sites.
To work with programs, you must perform additional configurations like assigning
users to programs, setting a program as the default program of the user, setting the
program security and son on.
For more information about configuring programs, see Configuring programs.
The Training program is provided by the Aerospace and Defense Training
Program template.

Training
Description This is the default program that is provided by the Aerospace
and DefenseTraining Program template. The program
is document-centric with program-level security enabled.
The program is preconfigured with conditions, naming rules,
revision naming rules, and lists of values.
Program type Document-centric.
Program-level Enabled.
security
Notes None.

Training-Part Centric
Description This is the default program that is provided by the Aerospace
and DefenseTraining Program template. The program is
part-centric with program-level security enabled. The program
is preconfigured with conditions, naming rules, revision
naming rules, and lists of values.
Program type Part-centric.
Program-level Enabled.
security

A-2 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense Training Program

Notes None.

Conditions
Conditions are conditional statements that are run with rules; they resolve to true
or false. Conditions can be used to evaluate objects or user sessions to deliver only
certain results.
For more information about conditions, see the Business Modeler IDE Guide.

ADSTrngCondition

Description This condition is configured for the Training and

Training-Part Centric programs.
Expression o.project_name = "Training”
o is the parameter name and the parameter type is
UserSession.
Notes The condition evaluates to true when the active program for
the user session is the Training or Training-Part Centric
program; otherwise, the condition evaluates to false.
Where used This condition is used in naming rules, revision naming rules,
and lists of values.

AnDCMTrainingProgramCondition

Description This condition is configured to make the ADS

Training Program data model applicable to
change objects.
Expression o.project_name = "Training”
o is the parameter name and the parameter type
is UserSession.
Notes The condition evaluates to true when the
active program for the user session is the
Training program; otherwise, the condition
evaluates to false. The condition is provided
by the Aerospace and Defense Change
Management template.
Where used This condition is used in naming rules, revision
naming rules, and lists of values.

Naming rules
Naming rules provide a way for applying custom naming conventions to items, item
revisions, identifiers, datasets, forms, projects, and work contexts. In addition,
naming rules can be used to define patterns for automatically generating IDs when

PLM00111 G Aerospace and Defense Solution Guide A-3

Appendix A Aerospace and Defense Training Program

creating objects. A naming rule consists of multiple naming rule patterns and a
counter.
For more information about naming rules, see Configuring naming rules.
TrngNamingRule is a naming rule provided by the Aerospace and Defense
Training Program template and is attached to the Training and Training-Part
Centric programs.

TrngNamingRule

Description This naming rule is attached to the item_id property of all

ADS business objects. The ADSTrngCondition condition is
evaluated to determine whether the naming rule is applied.
The naming rule is attached to the business object property
when the condition evaluates to true.

Business objects The naming rule is attached to the following business objects:
• ADSTechDocument

• ADSPart

• ADSDesign

• ADSDrawing
Business object item_id
property
Pattern “01–”NNNN
“02–”NNNN
“01–”NNNN”-”NNN
Counter Enabled.
Condition ADSTrngCondition
Notes For the “01–”NNNN pattern, the initial value is 01–0000 and
the maximum value is 01–9999.
For the “02–”NNNN pattern, the initial value is 02–0000 and
the maximum value is 02–9999.
For the “01–”NNNN”-”NNN pattern, the initial value is
01–0000–000 and the maximum value is 01–9999–999.

A-4 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense Training Program

Adc0TrngNamingRule

Description This naming rule is attached to the

item_id property of all change objects.
The AnDCMTrainingProgramCondition
condition is evaluated to determine whether
the naming rule is applied. The naming rule is
attached to the business object property when
the condition evaluates to true.
Business objects The naming rule is attached to the following
business objects:
• Adc0ChangeNotice

• Adc0ChangeRqst

• Adc0DevRqst

• ProblemReport
Business object property item_id
Pattern “01–”NNNN
“02–”NNNN
Counter Enabled.
Condition AnDCMTrainingProgramCondition
Notes For the “01–”NNNN pattern, the initial value is
01–0000 and the maximum value is 01–9999.
For the “02–”NNNN pattern, the initial value is
02–0000 and the maximum value is 02–9999.
This rule is included in the Aerospace and
Defense Change Management template.

Revision naming rules

Revision naming rules make it easy to maintain the revision scheme for business
objects. Each time an object is revised, the revision ID increments to indicate that
the object has been revised and the new revision supersedes the previous revision.
For more information about revision naming rules, see Configuring revision naming
rules.
TrngRevNamingRule is a revision naming rule provided by the Aerospace
and Defense Training Program template and is attached to the Training and
Training-Part Centric programs.

PLM00111 G Aerospace and Defense Solution Guide A-5

Appendix A Aerospace and Defense Training Program

TrngRevNamingRule

Description This revision naming rule is attached to the item_revision_id

property of all ADS business objects. The ADSTrngCondition
condition is evaluated to determine whether the revision naming
rule is applied. The revision naming rule is attached to the
business object property when the condition evaluates to true.
Business objects The revision naming rule is attached to the following business
objects:
• ADSTechDocument

• ADSPart

• ADSDesign

• ADSDrawing
Business object item_revision_id
property
Exclude skip True
letters
Condition ADSTrngCondition
Initial revision The initial revision type is numeric and the starting value is 1.
details
Secondary The secondary revision type is alphabetic and the starting value
revision details is -.
Supplemental The supplemental revision format is
revision details NextRevLetterFixedTwoDigitsZeroFill.
Notes None

Adc0TrngRevNamingRule

Description This revision naming rule is attached

to the item_revision_id property of
all the ADS business objects. The
AnDCMTrainingProgramCondition
condition is evaluated to determine whether the
revision naming rule is applied. The revision
naming rule is attached to the business object
property when the condition evaluates to true.

A-6 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense Training Program

Business objects The revision naming rule is attached to the

following business objects:
• Adc0ChangeNoticeRevision

• Adc0ChangeRqstRevision

• Adc0DevRqstRevision

• ProblemReportRevision
Business object property item_revision_id
Exclude skip letters True
Condition AnDCMTrainingProgramCondition
Initial revision details The initial revision type is numeric and the
starting value is 1.
Secondary revision details The secondary revision type is alphabetic and
the starting value is -.
Supplemental revision details The supplemental revision format is
NextRevLetterFixedTwoDigitsZeroFill.
Notes This rule is included in the Aerospace and
Defense Change Management template.

Lists of values
Lists of values (LOVs) ensure consistent data entry in Teamcenter. The list entries
are created either by referencing existing data or by entering custom site data. After
it is created, the LOV is implemented throughout the interface by attaching the
LOV to one or more properties. Creating LOVs and implementing them throughout
Teamcenter can greatly improve productivity at your site and help prevent incorrect
user entries.
This section describes the LOVs that are provided by the Aerospace and Defense
Training Program template and attached to the Training and Training-Part
Centric programs.
For more information about LOVs, see Configuring list of values (LOVs).

Adc0Change Class

Description Designates the government’s or customer’s

classification to a change. For example, I or II.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeNoticeRevision.Adc0change_class
Adc0ChangeRqstRevision.Adc0change_class
Adc0DevRqstRevision.Adc0change_class
Business object condition AnDCMTrainingProgramCondition

PLM00111 G Aerospace and Defense Solution Guide A-7

Appendix A Aerospace and Defense Training Program

Default values I
II
Valid values Accepts string as a value. It must be a valid
classification.
Notes This LOV is included in the
adschangemanagement template.

Adc0Change Category

Description Designates the specific category of change within

the change classification.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeRqstRevision.Adc0change_category
Adc0ChangeNoticeRevision.Adc0category
Adc0DevRqstRevision.Adc0change_category
Business object condition AnDCMTrainingProgramCondition
Default values 1
2
A
B
C
D
E
M
Valid values Accepts string as a value.
Notes This LOV is included in the
adschangemanagement template.

Adc0CN Types

Description Specifies acronyms for the types of change

documentation used on a program for a change
notice.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeNotice.Adc0change_type
Business object condition AnDCMTrainingProgramCondition

A-8 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense Training Program

Default values ADCN

AMR
DCN
DCR
DRN
ICN
PCD
PMD
REDLINE
RR
VAR
Valid values Accepts string as a value. It must be a valid
acronym that specifies the type of change
documentation.
Notes This LOV is included in the
adschangemanagement template.

Adc0CR Types

Description Specifies the change request types. For example,

development change or engineering change
process.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeRqst.Adc0change_type
Business object condition AnDCMTrainingProgramCondition
Default values CA

CRBD

DEV

ECP

IPCD

RFD

RFW
Valid values Accepts string as a value. It must be a valid
change request type.
Notes This LOV is included in the
adschangemanagement template.

PLM00111 G Aerospace and Defense Solution Guide A-9

Appendix A Aerospace and Defense Training Program

Adc0DR Types

Description Specifies acronyms for the types of change

documentation used on a program for a deviation
request, for example, RFD or RFW.
Type ListOfValuesString
Usage Exhaustive.
Business object property Cm0DevRqst.Cm0change_type
Business object condition AnDCMTrainingProgramCondition
Default values RFD
Request for Deviation

RFW
Request for Waiver
Valid values Accepts string as a value. It must be a valid
acronym that specifies the type of change
documentation.
Notes This LOV is included in the
adschangemanagement template.

Adc0Production Systems

Description Displays the list of systems or subsystems for an

item. A product system denotes a group of parts
that perform a common function. For example,
Electrical, Environmental Control, and
Weapons.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0DevRqstRevision.Adc0product_systems
Adc0ChangeRqstRevision.Adc0product_systems
Adc0ChangeNoticeRevision.Adc0product_systems
Business object condition AnDCMTrainingProgramCondition
Default values Electrical

Environmental Control

Hydraulic

Fuel

Weapons
Valid values Accepts string as a value. It must be a valid
system or subsystem.

A-10 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense Training Program

Notes This LOV is included in the

adschangemanagement template.

Adc0Quotation Type

Description Specifies the quotation type for the change

impact, for example, Supplier ROM, Buyer
Estimate, or Supplier Firm.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeRqstRevision.Adc0quotation_type
Adc0DevRqstRevision.Adc0quotation_type
Business object condition AnDCMTrainingProgramCondition
Default values NTE
ROM
Valid values Accepts string as a value. It must be a valid
quotation type.
Notes This LOV is included in the
adschangemanagement template.

Adc0Task Category

Description Specifies the various task categories, for

example, Agenda Event, Planning, and QA.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0Task.Adc0task_category
Business object condition AnDCMTrainingProgramCondition
Default values Agenda Event
Engineering
ILS
Major Subcontr
Manufacturing
Non-Std Event
Part
Planning
QA
Subcontract
Valid values Accepts string as a value. It must be a valid task
category.
Notes This LOV is included in the
adschangemanagement template.

PLM00111 G Aerospace and Defense Solution Guide A-11

Appendix A Aerospace and Defense Training Program

ADS Trng Categories

Description Specifies the valid values for the ADS document category. This
is a cascading list.
Type ListOfValuesString
Usage Exhaustive.
Business object ADSTechDocument.adscategory
property ADSPart.adssource_tdoc_category
ADSDesign.adssource_tdoc_category
ADSDrawing.adssource_tdoc_category
Business object ADSTrngCondition
condition
Default values ALOO
DL Document list
DOC Document
DWG Drawing
MFG
PL Parts list
SDL
SDRL Supplier definition requirements list
SOW Statement of work
SPEC Specification
Valid values Any valid document category.
Notes Each value contains a sub-LOV.

ADS Trng DOC Categories

Description Sub-LOV that specifies the list of values if the ADS category
is document.
Type ListOfValuesString

Usage Exhaustive.
Default values Dwg Design Data
Interface Control Document
Text Report
Weapon System Specification
Valid values Any valid drawing.
Notes None.

A-12 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense Training Program

ADS Trng DWG Categories

Description Sub-LOV that specifies the list of values if the ADS category
is drawing.
Type ListOfValuesString

Usage Exhaustive.
Default values Assembly Drawing
Design Drawing
Detail Drawing
Tube Drawing
Zone Drawing
Valid values Any valid drawing.
Notes None.

ADS Trng PL Categories

Description Sub-LOV that specifies the list of values if the ADS category
is part.
Type ListOfValuesString

Usage Exhaustive.
Default values Assembly Drawing
Detail Drawing
Tube Drawing
Zone Drawing
Valid values Any valid drawing.
Notes None.

ADS Trng SDRL Categories

Description Sub-LOV that specifies the list of values if the ADS category
is SDRL.
Type ListOfValuesString

Usage Exhaustive.
Default values Requirement List
Valid values Any valid document type.
Notes None.

ADS Trng Design Categories

Description Specifies valid values for the ADS design category.

Type ListOfValuesString

PLM00111 G Aerospace and Defense Solution Guide A-13

Appendix A Aerospace and Defense Training Program

Usage Exhaustive.
Business object ADSDesign.adsdesign_category
property
Business object ADSTrngCondition
condition
Default values Program
Design
Domestic
Supplier
GFE
Valid values Any valid design category.
Notes None.

ADS Trng Dist Code

Description Specifies valid values for the distribution code.

Type ListOfValuesString
Usage Exhaustive.
Business object ADSTechDocument.adsdistribution_code
property ADSPart.adsdistribution_code
ADSDesign.adsdistribution_code
ADSDrawing.adsdistribution_code
Business object ADSTrngCondition
condition
Default values A01
Valid values Any valid distribution code.
Notes None.

ADS Trng Part Categories

Description Specifies valid values for the ADS part category.

Type ListOfValuesString
Usage Exhaustive.

Business object ADSPart.adspart_category

property
Business object ADSTrngCondition
condition
Default values Program
Design
Domestic
Supplier
GFE
Valid values Any valid part category.

A-14 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense Training Program

Notes None.

PLM00111 G Aerospace and Defense Solution Guide A-15

Appendix

B Aerospace and Defense data

model

Aerospace and Defense data model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Preconditions and postactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

ADSTechDocument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
ADSTechDocument attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
ADSTechDocument Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Preconditions and postactions on ADSTechDocument . . . . . . . . . . . . . . . . B-3
ADSTechDocument Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
ADSTechDocumentVerMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

ADSPart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
ADSPart attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
ADSPartMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-7
Preconditions and postactions on ADSPart . . . . . . . . . . . . . . . . . . . . . . . B-7
ADSPart Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9
ADSPartVerMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-9

ADSDesign . . . . . . . . . . . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . . . B-9

ADSDesign attributes . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . . B-10
ADSDesignMaster . . . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . . B-11
Preconditions and postactions on ADSDesign ... . . . . . . . . . . . . . . . . . B-12
ADSDesign Revision . . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . . B-13
ADSDesignVerMaster . . . . . . . . . . . . . . . . .... . . . . . . . . . . . . . . . . . B-14

ADSDrawing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-14
ADSDrawing attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
ADSDrawingMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
Preconditions and postactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-16
ADSDrawing Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-17

CommercialPart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
CommercialPart attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-18
CommercialPartMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19
Preconditions and postactions for CommercialPart . . . . . . . . . . . . . . . . . B-19
CommercialPart Revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-20

Aerospace and Defense template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-21

Adc0ChangeNotice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22
Adc0ChangeNotice attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22
Adc0ChangeNoticeMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22

PLM00111 G Aerospace and Defense Solution Guide

 Preconditions and postactions on Adc0ChangeNotice . . . . . . . . . . . . . . . B-23
Adc0ChangeNoticeRevision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-23
Adc0ChangeNoticeRevision attributes . . . . . . . . . . . . . . . . . . . . . . . . . B-24
Adc0ChangeNoticeRevMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25
Adc0GnChangeRqst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25
Adc0GnChangeRqst attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25
Adc0GnChangeRqstMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Adc0GnChangeRqstRevision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-26
Adc0GnChangeRqstRevMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27
Adc0GnChangeRqstRevision attributes . . . . . . . . . . . . . . . . . . . . . . . . . B-27
Adc0ChangeRqst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
Adc0ChangeRqst attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
Adc0ChangeRqstMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-29
Adc0ChangeRqstRevision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-30
Adc0ChangeRqstRevision attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . B-30
Adc0DevRqst . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-31
Adc0DevRqstMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32
Adc0DevRqstRevision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-32
Adc0DevRqstRevision attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-33
Adc0DevRqstRevMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-34
Adc0Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-35
Adc0Task attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-35
Adc0TaskMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Adc0TaskRevision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-36
Adc0TaskRevisionMaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37

Contract data management objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-37

Cdm0Contract attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38
Cdm0ContractRevision attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-38
Cdm0DataReqItem attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-39
Cdm0DataReqItemRevision attribute . . . . . . . . . . . . . . . . . . . . . . . . . . B-40
Fnd0StaticTable attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-42
Cdm0EventsTable attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-43
Cdm0DID attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44
Cdm0DIDRevision attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-44
Cdm0Submittal attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-45
Cdm0SubmittalRevision attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-45
Cdm0Correspondence attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-47
Cdm0CorrespondenceRevision attribute . . . . . . . . . . . . . . . . . . . . . . . . B-47
Cdm0IsDescribedbyDID attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-48
Cdm0ListsDRISubmittalSch attribute . . . . . . . . . . . . . . . . . . . . . . . . . B-48
Cdm0ListsDRISubmittal attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-49
Cdm0ListsCorspSubmittals attribute . . . . . . . . . . . . . . . . . . . . . . . . . . B-49
Cdm0ListsCorspRefItems attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . B-50
Cdm0ListsContractDRI attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-50

Stock material objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-50

Work package objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-51

Finish objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-51

Data model for Aerospace and Defense relations . . . . . . . . . . . . . . . . . . . . . B-52

ADS_Lists_Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-52

Aerospace and Defense Solution Guide PLM00111 G

 ADS_Lists_PartRevisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-53
ADS_Lists_DrawingRevisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-54
TC_Program_Preferred_Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-55
Fnd0LocationForUser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-56
Fnd0LocationForGroup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-57

Lists of values for Aerospace and Defense . . . . . . . . . . . . . . . . . . . . . . . . . . B-57

Adc0Change Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-57
Adc0Change Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-58
Adc0CN Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-58
Adc0CR Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-59
Adc0DR Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-59
Adc0Production Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-60
Adc0Quotation Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-60
Adc0Task Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-61
Ads0CreateStandardNoteAuthority . . . . . . . . . . . . . . . . . . . . . . . . . . . B-61
ADS Assembly Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-62
ADSComponentAuthority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-62
ADS Design Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-62
ADSDocumentCentricPrograms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-63
ADSDrawingAuthority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-63
ADSTechDocAuthority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-64
TCProgramPreferredTypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-64
TCProgramsUsingPreferredTypes . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-64
TcRevisionSkipLetters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-64

PLM00111 G Aerospace and Defense Solution Guide

Appendix

B Aerospace and Defense data

model

Aerospace and Defense data model

The following structure is used to describe the objects:
Object type Describes the data model of the object that represents the parent
class and the subclass of the object.
Object type Describes the attributes of the object that provides it a unique
number identifier.
Object type Describes the class model of the object that represents the
master attributes of the object.
Preconditions Describes the preconditions and postactions that should be defined
and during the creation of the object/component.
postactions
Template Describes the template in which the functionality of the object is
information available.
List of values Describes the program-independent list of values for the master
form and the revision master form.
Object type Describes the item revision corresponding to an object.
revision

Preconditions and postactions

Extension Describes the application extensions that allow for the
point configuration of applications using a decision table. Application
extensions can be used to configure business logic on the server,
a Teamcenter rich client application (such as My Teamcenter), a
Teamcenter thin client, or any application. You can use application
extensions for anything that calls an input and output, from user
interface changes, such as icons and colors, to actions.
Operation Describes the operation to be placed on the business object.
name
Extension Determines when an application extension point is used and
rule name defines inputs and outputs. When the input is matched, the
rule engine returns the output to the application that called the
extension point.

PLM00111 G Aerospace and Defense Solution Guide B-1

Appendix B Aerospace and Defense data model

Parameters Describes the parameters to be passed to the extension.

Description Describes the application extension point.

ADSTechDocument
ADSTechDocument is a subtype of the Document item type and represents the
technical document used in document-centric programs.
ADSTechDocument is a primary business object that represents a variety of
printed or digital entities that contain technical information about some aspect of
the product or a component of the product. These may include documents such as
technical reports, drawings, procurement specifications, parts lists, interface control
documents, and schematics.
Technical documents serve as the source documents for creating parts and
assemblies. All parts must be associated with a technical document using an
appropriate relationship.
The following figure illustrates the ADSTechDocument data model.

ADSTechDocument attributes
ADSTechDocument items are uniquely identified in the system by an item_id
property. The item_id property denotes the technical document number.
The ADSTechDocument item is provided by the adsfoundation template.
The following table describes the attributes of the ADSTechDocument class.

Attribute name Storage type Description

adscategory String [32] Classifies document items, for example,
DOC, DWG, PL, and SPEC.

The attribute values must be configured

based on the individual program. There are
no default values.

B-2 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Attribute name Storage type Description

adstech_doc_category String [32] Designates a category of similar technical
documents, for example, Dwg Design
Data, Weapon System Specification,
Assembly Drawing, Design Drawing,
Detail Drawing, and Requirements List.

The attribute values must be configured

based on the individual program. The valid
values for this attribute are dependent on the
value specified for the category attribute.
adsgovt_data_right String [32] Specifies the nature of the government
technical data rights-in-data for a document
or software.

The attribute values must be configured

based on the individual program. There are
no default values.
adsdistribution_code String [32] Specifies the distribution statement that
is affixed to the document or viewable file
to indicate the authorized circulation or
dissemination of the information contained
within the item.

ADSTechDocument Master
ADSTechDocument Master is the storage class of the item master form
corresponding to the ADSTechDocument item. The following figure illustrates the
schema definition and attributes of the ADSTechDocument Master class.

Preconditions and postactions on ADSTechDocument

The following table describes the preconditions that are defined on the
ADSTechDocument business object.

Extension rule name Operation name Parameters

authorizationCheckOnSaveAs ITEM_create_from_rev ADSTechDocAuthority

Checks the user permission while saving an

ADSTechDocument.

PLM00111 G Aerospace and Defense Solution Guide B-3

Appendix B Aerospace and Defense data model

Extension rule name Operation name Parameters

checkAdsAttachment IMAN_delete ADSTechDocAuthority

Checks whether or not the selected source document is

associated with other items during deletion.
validateOrgOnCreation ITEM_create

Checks the value of the TcSetOwningOrganization ITEM_create_from_rev

global constant and the AutoAssignOwningOrg
business constant. When the value is set to true and
the current user group belongs to an organization, the
workspace object is created.
validateImport TIE_deserialize

Checks the value of the TcSetOwningOrganization

global constant and the AutoAssignOwningOrg
business constant. Data is imported when the value of
the constants is true and the data belongs to the same
organization at the both the sites.
authorizationCheckOnRevise ITEM_copy_rev

Checks the user permission during the revision of

ADSTechDocument Revision.

The following table describes the postactions that are defined on the
ADSTechDocument business object.

Extension rule name Operation name Parameters

autoAssignToProject ITEM_create

Assigns the object to the current project. IMAN_import

ITEM_create_from_rev

setOrgOnCreation ITEM_create

Checks the value of the TcSetOwningOrganization ITEM_create_from_rev

global constant and the AutoAssignOwningOrg
business constant. When the value of the constants is
true and the current group belongs to an organization,
the owning_organization attribute value of the object
is automatically updated.

ADSTechDocument Revision
ADSTechDocument Revision is a subtype of the Document Revision business
object and represents revisions corresponding to a technical document.
ADSTechDocument Revision is a primary business object.
The following figure illustrates the ADSTechDocument Revision business object
data model.

B-4 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

ADSTechDocumentVerMaster
ADSTechDocumentVerMaster is the storage class of the item revision master
form corresponding to the ADSTechDocumentRevision business object.
The following figure illustrates the schema definition and attributes of the
ADSTechDocumentVerMaster class.

ADSPart
ADSPart is a subtype of the Part item type, which represents a component of a
product. It is a primary business object.
Note The terms part and component are used interchangeably.

In document-centric programs, ADSPart objects are created on a source technical

document and are related to the technical document through an ADS_Lists_Parts
relationship.
The following figure illustrates the ADSPart data model.

PLM00111 G Aerospace and Defense Solution Guide B-5

Appendix B Aerospace and Defense data model

ADSPart attributes
ADSPart items are uniquely identified in the system by an item_id property. The
item_id property denotes the ADS part number.
The ADSPart item is provided by the adsfoundation template.
The following table describes the attributes of the ADSPart class.

Attribute name Storage type Description

ads0source_doc_ref TypedReference Specifies the technical
document.
adssource_document String [128] The unique identifier for
the document the part is
created on. ADS source
document is a text field
that can contain up to 80
characters.
adssource_doc_revision String [32] Specifies the revision
of the ADS source
document.
adssource_doc_category String [32] A user-defined attribute
for classifying document
items.
adssource_tdoc_category String [32] Designates a category
of similar technical
documents, for example,
assembly drawing,
wire list, or material
specification.
adssource_doc_org String [32] Specifies organization
name of source
document.

B-6 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Attribute name Storage type Description

adsqualification_req Boolean Indicates whether or
not a part requires
qualification testing
before it can be installed
in the product.
adsinstallation Boolean Indicates whether the
assembly object is an
installation.

ADSPartMaster
ADSPartMaster is the storage class of the item master form corresponding to the
ADSPart item. The following figure illustrates the schema definition and attributes
of the ADSPartMaster class.

Preconditions and postactions on ADSPart

The following table describes preconditions for the ADSPart object.

Extension rule name Operation name Parameters

authorizationCheckOnSaveAs ITEM_create_from_rev

Checks the user permission while saving an

ADS part.

DCPCheckMandatoryValuesSaveas ITEM_create_from_rev ADSComponentAuthority

Checks if the mandatory values are entered for

a document-centric program.
validateOrgOnCreation ITEM_create

Checks the value of the ITEM_create_from_rev

TcSetOwningOrganization global constant
and the AutoAssignOwningOrg business ITEM_copy_rev
constant. When the value is set to true and the
ITEM_baseline_rev
current user group belongs to an organization,
the workspace object is created. ITEM_copy_rev_to_existing

ITEM_create_rev

PLM00111 G Aerospace and Defense Solution Guide B-7

Appendix B Aerospace and Defense data model

Extension rule name Operation name Parameters

validateImport TIE_deserialize

Checks the value of the

TcSetOwningOrganization global constant
and the AutoAssignOwningOrg business
constant. Data is imported when the value of
the constants is true and the data belongs to
the same organization at the both the sites.
checkTechDocPrivilege ITEM_copy_rev

Checks if the ADS part has access to the ITEM_baseline_rev

technical document.
ITEM_copy_rev_to_existing

ITEM_create_rev
authorizationCheckOnRevise ITEM_copy_rev

Checks the user permission during the revision

of an ADS part.
checkLatest_Released ITEM_copy_rev_to_existing

ITEM_create_rev

The following table describes postactions for the ADSPart object.

Extension rule name Operation name Parameters

cmpSrcDocRelationOnSaveAs ITEM_create_from_rev ADSComponentAuthority

Creates a relation between ADS part and the

source document when the part is saved.
cmpSrcDocRelationOnCreate ITEM_create ADSComponentAuthority

Creates a relation between ADS part and the

source document while creation of a part.
autoAssignToProject IMAN_import

Assigns the object to the current project. ITEM_create

ITEM_create_from_rev

ITEM_copy_rev

ITEM_baseline_rev

ITEM_copy_rev_to_existing

ITEM_create_rev
setOrgOnCreation ITEM_create

Checks the value of the ITEM_create_from_rev

TcSetOwningOrganization global constant
and the AutoAssignOwningOrg business ITEM_copy_rev
constant. When the value of the constants is true
ITEM_baseline_rev
and the current group belongs to an organization,
the owning_organization attribute value of ITEM_copy_rev_to_existing
the object is automatically updated.
ITEM_create_rev

B-8 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Extension rule name Operation name Parameters

cmpSrcDocRelationOnRevise ITEM_copy_rev

Creates a relation between ADS part and the ITEM_baseline_rev

source document when the part is revised.
ITEM_copy_rev_to_existing

ITEM_create_rev
Ads0AssociateChangeNotice ITEM_copy_rev

ITEM_baseline_rev

ITEM_copy_rev_to_existing

ITEM_create_rev

ADSPart Revision
ADSPart Revision is a subtype of the Part Revision business object and
represents revisions corresponding to an ADSPart. The following figure illustrates
the ADSPart Revision business object data model.

ADSPartVerMaster
ADSPartVerMaster is the storage class of the item revision master form
corresponding to the ADSPartVerMaster business object.

ADSDesign
ADSDesign is a subtype of the Design item type that represents the geometric
data of a component or assembly.
ADSDesign is a primary business object.
In document-centric programs, ADSDesign are created on a source technical
document and are related to the technical document through an ADS_Lists_Parts
relationship.
The following figure illustrates the ADSDesign data model.

PLM00111 G Aerospace and Defense Solution Guide B-9

Appendix B Aerospace and Defense data model

ADSDesign attributes
ADSDesign objects are uniquely identified in the system by an item_id property.
The item_id property denotes the ADS design number.
The ADSDesign item is provided by the adsfoundation template.
The following table describes the attributes of the ADSDesign object.

Attribute name Storage type Description

ads0source_doc_ref TypedReference Specifies the technical
document.
adsdesign_category String [32] Designates the category
of the design for the
program.
adsassembly_type String [32] Identifies the type
of assembly for the
part. Valid values
are Separable and
Inseparable

An inseparable
assembly part cannot be
disassembled without
causing physical harm
to at least one of the
constituent parts in the
assembly.

B-10 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Attribute name Storage type Description

adsdistribution_code String [32] Specifies the distribution
statement that
is affixed to the
document or viewable
file to indicate the
authorized circulation
or dissemination of the
information contained
within the item.
adsspecial_handling Boolean Indicates whether or not
a part requires special
handling.
adsqualification_req Boolean Indicates whether or
not a part requires
qualification testing
before it can be installed
in the product.
adsinstallation Boolean Indicates whether the
assembly object is an
installation.
adssource_doc_revision String [32] Specifies the revision
of the ADS source
document.
adssource_doc_category String [32] A user-defined attribute
for classifying document
items.
adssource_tdoc_category String [32] Designates a category
of similar technical
documents, for example,
assembly drawing,
wire list, or material
specification.
adssource_doc_org String [32] Specifies the
organization name of
source document.
adssource_document String [128] The unique identifier of
the document on which
the part is created.

ADSDesignMaster
ADSDesignMaster is the storage class of the item master form corresponding to
the ADSDesign item.
The following figure illustrates the schema definition and attributes of the
ADSDesignMaster class.

PLM00111 G Aerospace and Defense Solution Guide B-11

Appendix B Aerospace and Defense data model

Preconditions and postactions on ADSDesign

The following table describes preconditions for the ADSDesign object.

Extension rule name Operation name Parameters

DCPCheckMandatoryValuesSaveas ITEM_create_from_rev ADSComponentAuthority

Checks if the mandatory values are entered for

a document-centric program.
authorizationCheckOnSaveAs ITEM_create_from_rev

Checks the user permission while saving an

ADSDesign.

validateOrgOnCreation ITEM_create

Checks the value of the ITEM_create_from_rev

TcSetOwningOrganization global constant
and the AutoAssignOwningOrg business ITEM_copy_rev
constant. If the value is set to true and the
ITEM_baseline_rev
current user group belongs to an organization,
the workspace object is created. ITEM_copy_rev_to_existing

ITEM_create_rev
validateImport TIE_deserialize

Checks the value of the

TcSetOwningOrganization global constant
and the AutoAssignOwningOrg business
constant. Data is imported when the value of
the constants is true and the data belongs to the
same organization at the both the sites.
authorizationCheckOnRevise ITEM_copy_rev

Checks the user permission during the revision

of an ADSDesign.

checkTechDocPrivilege ITEM_copy_rev

Checks if ADSDesign has access to the technical ITEM_baseline_rev

document.
ITEM_copy_rev_to_existing

ITEM_create_rev

B-12 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Extension rule name Operation name Parameters

checkLatest_Released ITEM_copy_rev_to_existing

ITEM_create_rev

The following table describes postactions for the ADSDesign object.

Extension rule name Operation name Parameters

cmpSrcDocRelationOnSaveAs ITEM_create_from_rev

Creates a relation between ADSDesign and the

source document when the design is saved.
cmpSrcDocRelationOnCreate ITEM_create

Creates a relation between ADSDesign and the

source document when the design is created.
autoAssignToProject IMAN_import

Assigns the object to the current project. ITEM_create

ITEM_create_from_rev

ITEM_copy_rev

ITEM_baseline_rev

ITEM_copy_rev_to_existing

ITEM_create_rev
setOrgOnCreation ITEM_create

Checks the value of the ITEM_create_from_rev

TcSetOwningOrganization global constant and
the AutoAssignOwningOrg business constant. ITEM_copy_rev
When the value of the constants is true and the
ITEM_baseline_rev
current group belongs to an organization, the
owning_organization attribute value of the object ITEM_copy_rev_to_existing
is automatically updated.
ITEM_create_rev
cmpSrcDocRelationOnRevise ITEM_copy_rev

Creates a relation between ADSDesign and the ITEM_baseline_rev

source document when the design is revised.
ITEM_copy_rev_to_existing

ITEM_create_rev
Ads0AssociateChangeNotice ITEM_copy_rev

ITEM_baseline_rev

ITEM_copy_rev_to_existing

ITEM_create_rev

ADSDesign Revision
ADSDesign Revision is a subtype of Design Revision business object and
represents the revisions corresponding to ADSDesign.

PLM00111 G Aerospace and Defense Solution Guide B-13

Appendix B Aerospace and Defense data model

The following figure illustrates the ADSDesign Revision data model.

Users must manually associate ADSDesign Revision with the corresponding

ADSPart Revision using the TC_Is_Represented_By relation type.

ADSDesignVerMaster
ADSDesignVerMaster is the storage class of the item revision master form
corresponding to the ADSDesign Revision business object.

ADSDrawing
ADSDrawing is a subtype of the Drawing item type. In document-centric
programs, ADSDrawing are created in the context of a source technical document.
These are referred to as assembly drawings. There can be one or more drawings
for a given technical document, and a single drawing can detail out one or more
assemblies or parts created with that technical document as their source document.
The assemblies created on a given source document that have minor differences in
their product structure configuration are detailed out on a single drawing.
The following figure illustrates the ADSDrawing data model.

B-14 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

ADSDrawing attributes
ADSDrawing objects are uniquely identified in the system by an item_id property.
The item_id property denotes the ADS drawing number.
The ADSDrawing business object is provided by the adsfoundation template.
The following table describes the attributes of the ADSDrawing object.

Attribute name Storage type Description

ads0source_doc_ref TypedReference Specifies the technical
document.
adsdistribution_code String [32] Specifies the distribution
statement that is affixed to
the document or viewable file
to indicate the authorized
circulation or dissemination
of the information contained
within the item.
adsqualification_req Boolean Indicates whether or not a
part requires qualification
testing before it can be
installed in the product.
adssource_document String [128] The unique identifier for the
document on which the part
is created.
adssource_doc_revision String [32] Revision of the source
document.
adssource_doc_category String [32] User-defined attribute used
to classify Document items.
adssource_tdoc_category String [32] Designates a category of
similar technical documents,
for example, assembly
drawing, wire list, or
material specification.
adssource_doc_org Typed reference [32] Specifies organization name
of the source document.

ADSDrawingMaster
ADSDrawingMaster is the storage class of the item master form corresponding to
the ADSDrawing item. The following figure illustrates the schema definition and
attributes of the ADSDrawingMaster class.

PLM00111 G Aerospace and Defense Solution Guide B-15

Appendix B Aerospace and Defense data model

Preconditions and postactions

The following table describes preconditions for the ADSDrawing object.

Extension rule name Operation name Parameters

DCPCheckMandatoryValuesSaveas ITEM_create_from_rev ADSDrawingAuthority

Checks if the mandatory values are entered for

a document-centric program.
validateOrgOnCreation ITEM_create

Checks the value of the ITEM_create_from_rev

TcSetOwningOrganization global constant
and the AutoAssignOwningOrg business ITEM_copy_rev
constant. If the value is set to true and the
ITEM_baseline_rev
current user group belongs to an organization,
the workspace object is created. ITEM_copy_rev_to_existing

ITEM_create_rev
authorizationCheckOnSaveAs ITEM_create_from_rev

Checks the user permission while saving an

ADSDrawing.
validateImport TIE_deserialize

Checks the value of the

TcSetOwningOrganization global constant
and the AutoAssignOwningOrg business
constant. Data is imported when the value of
the constants is true and the data belongs to the
same organization at the both the sites.
authorizationCheckOnRevise ITEM_copy_rev

Checks the user permission during the revision

of an ADSDrawing.
checkTechDocPrivilege ITEM_copy_rev

Checks if ADS drawing has access to the ITEM_baseline_rev

technical document.
ITEM_copy_rev_to_existing

ITEM_create_rev
checkLatest_Released ITEM_copy_rev_to_existing

ITEM_create_rev

The following table describes postactions for the ADSDrawing object.

Extension rule name Operation name Parameters

cmpSrcDocRelationOnSaveAs ITEM_create_from_rev ADSDrawingAuthority

Creates a relation between ADS drawing and the

source document when the drawing is saved.
cmpSrcDocRelationOnCreate ITEM_create ADSDrawingAuthority

Creates a relation between ADS drawing and the

source document when the drawing is created.

B-16 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Extension rule name Operation name Parameters

autoAssignToProject ITEM_import

Assigns the object to the current project. ITEM_create

ITEM_create_from_rev

ITEM_copy_rev

ITEM_baseline_rev

ITEM_copy_rev_to_existing

ITEM_create_rev
setOrgOnCreation ITEM_create

Checks the value of the TcSetOwningOrganization ITEM_create_from_rev

global constant and the AutoAssignOwningOrg
business constant. When the value of the constants is ITEM_copy_rev
true and the current group belongs to an organization,
ITEM_baseline_rev
the owning_organization attribute value of the
object is automatically updated. ITEM_copy_rev_to_existing

ITEM_create_rev
Ads0AssociateChangeNotice ITEM_copy_rev

ITEM_baseline_rev

ITEM_copy_rev_to_existing

ITEM_create_rev
cmpSrcDocRelationOnRevise ITEM_copy_rev

Creates a relation between ADS drawing and the ITEM_baseline_rev

source document when the drawing is revised.
ITEM_copy_rev_to_existing

ITEM_create_rev

ADSDrawing Revision
ADSDrawing Revision is a subtype of the Drawing Revision business object
and represents revisions corresponding to an ADS drawing. The following figure
illustrates the ADSDrawing Revision business object data model.

PLM00111 G Aerospace and Defense Solution Guide B-17

Appendix B Aerospace and Defense data model

CommercialPart
CommercialPart is a subtype of the Part item type. It represents the
common-use parts that have been identified as standard design by a company,
an industry, or the military. Standard parts are associated to programs with the
TC_Program_Preferred_Parts relation. The following figure illustrates the
CommercialPart data model.

CommercialPart attributes
CommercialPart objects are uniquely identified in the system by the item_id,
property.
The CommercialPart business object is provided by the vendormanagement
template.
The following table describes the attributes of the CommercialPart object.

Attribute name Storage type Description

adspart_category String [32] Designates the category
of part for the program,
for example, supplier part,
government furnished
equipment, or military
standard part.
adsassembly_type String [32] Identifies the type of
assembly for the part.
Valid values are Separable
and Inseparable.

An inseparable assembly
part cannot be disassembled
without causing physical
harm to at least one of the
constituent parts in the
assembly.
adsspecial_handling String [32] Indicates whether or not
a part requires special
handling.
adsdistribution_code String [32]

B-18 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

CommercialPartMaster
CommercialPartMaster is the storage class of the item master form corresponding
to the CommercialPart item. The following figure illustrates the schema definition
and attributes of the CommercialPartMaster class.

Preconditions and postactions for CommercialPart

The following table describes preconditions for the CommercialPart object.

Operation name
Extension rule name Parameters
validateImport TIE_deserialize

Checks the value of the TcSetOwningOrganization

global constant and the AutoAssignOwningOrg business
constant. Data is imported when the value of the constants
is true and the data belongs to the same organization at the
both the sites.
validateOrgOnCreation ITEM_create

Checks the value of the TcSetOwningOrganization ITEM_create_from_rev

global constant and the AutoAssignOwningOrg business
constant. If the value is set to true and the current user ITEM_copy_rev
group belongs to an organization, the workspace object is
ITEM_baseline_rev
created.
ITEM_copy_rev_to_existing

ITEM_create_rev
checkLatest_Released ITEM_copy_rev

ITEM_copy_rev_to_existing

ITEM_create_rev

The following table describes postactions for the CommercialPart object.

PLM00111 G Aerospace and Defense Solution Guide B-19

Appendix B Aerospace and Defense data model

Extension rule name Operation name Parameters

autoAssignToProject ITEM_create NA

Assigns the object to the current project. IMAN_import

ITEM_create_from_rev

ITEM_copy_rev

ITEM_baseline_rev

ITEM_copy_rev_to_existing

ITEM_create_rev
setOrgOnCreation ITEM_create

Checks the value of the ITEM_create_from_rev

TcSetOwningOrganization global
constant and the AutoAssignOwningOrg ITEM_copy_rev
business constant. When the value of
ITEM_baseline_rev
the constants is true and the current
group belongs to an organization, the ITEM_copy_rev_to_existing
owning_organization attribute value of
the object is automatically updated. ITEM_create_rev

Ads0AssociateChangeNotice ITEM_copy_rev

ITEM_baseline_rev

ITEM_copy_rev_to_existing

ITEM_create_rev

CommercialPart Revision
CommercialPart Revision is a subtype of the Part Revision business object and
represents revisions corresponding to an commercial part. The following figure
illustrates the CommercialPart Revision business object data model.

B-20 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Aerospace and Defense template

The adschangemanagement template includes the classes shown in the following
diagram.

PLM00111 G Aerospace and Defense Solution Guide B-21

Appendix B Aerospace and Defense data model

Adc0ChangeNotice
Adc0ChangeNotice is a subtype of the ChangeNotice item type.
The following figure illustrates the Adc0ChangeNotice data model.

Adc0ChangeNotice attributes
The Adc0ChangeNotice item is provided by the adschangemanagement
template.
The following table describes the attributes of the Adc0ChangeNotice class.

Attribute name Storage type Description

Adc0change_type String [32] List of values that
specifies the type of
change documentation
for the program, for
example, ADCN, DCN,
and Redline.
Adc0paper_change Boolean If true, change is
incorporated. If
false, change is not
incorporated.

Adc0ChangeNoticeMaster
Adc0ChangeNoticeMaster is the storage class of the item master form
corresponding to the Adc0ChangeNotice item. The following figure illustrates the
schema definition and attributes of the Adc0ChangeNoticeMaster class.

B-22 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Preconditions and postactions on Adc0ChangeNotice

The following table describes preconditions for the Adc0ChangeNotice object.

Extension rule name Description Operation name

validateOrgOnCreation Checks the value of the ITEM_create
TcSetOwningOrganization
global constant and the ITEM_create_from_rev
AutoAssignOwningOrg business
constant. When the value is set to
true and the current user group
belongs to an organization, the
workspace object is created.
validateImport Checks the value of the TIE_deserialize
TcSetOwningOrganization
global constant and the
AutoAssignOwningOrg business
constant. Data is imported when
the value of the constants is true
and the data belongs to the same
organization at the both the sites.

The following table describes postactions for the Adc0ChangeNotice object.

Extension rule name Description Operation name

autoAssignToProject Assigns the object to the current IMAN_import
project.
ITEM_create

ITEM_create_from_rev
setOrgOnCreation Checks the value of the ITEM_create
TcSetOwningOrganization
global constant and the ITEM_create_from_rev
AutoAssignOwningOrg business
constant. When the value of the
constants is true and the current
group belongs to an organization,
the owning_organization attribute
value of the object is automatically
updated.
setOrgOnImport Checks the value of the TIE_deserialize
TcSetOwningOrganization
global constant and the
AutoAssignOwningOrg business
constant. When the value of the
constants is true and the current
group belongs to an organization,
the owning_organization attribute
value of the object is automatically
updated.

Adc0ChangeNoticeRevision
Adc0ChangeNoticeRevision is a subtype of the ChangeNoticeRevision
business object and represents revisions corresponding to an Adc0ChangeNotice.
The following figure illustrates the Adc0ChangeNoticeRevision business object
data model.

PLM00111 G Aerospace and Defense Solution Guide B-23

Appendix B Aerospace and Defense data model

Adc0ChangeNoticeRevision attributes
The Adc0ChangeNoticeRevision item is provided by the
adschangemanagement template.
The following table describes the attributes of the Adc0ChangeNoticeRevision
class.

Attribute name Storage type Description

Adc0category String [32] Designates the specific
category of change
within the change
classification.
Adc0change_class String [15] List of values that
designates the
government’s or
customer’s classification
to a change, for example,
I or II.
Adc0product_systems String [40] List of values that
designates the systems
or subsystems for an
item. A product system
denotes a group of
parts that perform a
common function, for
example, Electrical,
Environmental
Control, and Weapons.

B-24 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Attribute name Storage type Description

Adc0product_zones String [40] Designates the zones for
an item. A zone denotes
an area or section of
the product used in
managing multiple
system interfaces and
structural interferences.
For example, Baggage
Compartment,
Electrical, and
Plumbing.

Adc0ChangeNoticeRevMaster
Adc0ChangeNoticeRevMaster is the storage class of the item revision master
form.

Adc0GnChangeRqst
Adc0GnChangeRqst is a subtype of the ChangeRequest item type.
The following figure illustrates the Adc0GnChangeRqst data model.

Adc0GnChangeRqst attributes
The Adc0GnChangeRqst item is provided by the adschangemanagement
template.

PLM00111 G Aerospace and Defense Solution Guide B-25

Appendix B Aerospace and Defense data model

The following table describes the attributes of the Adc0GnChangeRqst class.

Attribute name Storage type Description

Adc0change_type String [32] List of values that
specifies the type of
change documentation
for the program, for
example, ADCN, DCN,
and Redline.

Adc0GnChangeRqstMaster
Adc0GnChangeRqstMaster is the storage class of the item master form
corresponding to the Adc0GnChangeRqst item. The following figure illustrates
the schema definition and attributes of the Adc0GnChangeRqstMaster class.

Adc0GnChangeRqstRevision
Adc0GnChangeRqstRevision is a subtype of the ChangeRequestRevision
business object and represents revisions corresponding to an Adc0GnChangeRqst.
The following figure illustrates the Adc0GnChangeRqstRevision business object
data model.

B-26 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Adc0GnChangeRqstRevMaster
Adc0GnChangeRqstRevMaster is the storage class of the item revision master
form.

Adc0GnChangeRqstRevision attributes
The Adc0GnChangeRqstRevision item is provided by the
adschangemanagement template.

PLM00111 G Aerospace and Defense Solution Guide B-27

Appendix B Aerospace and Defense data model

The following table describes the attributes of the Adc0GnChangeRqstRevision

class.

Attribute name Storage type Description

Adc0category String [32] Designates the specific
category of change
within the change
classification.
Adc0change_class String [15] List of values that
designates the
government’s or
customer’s classification
to a change, for example,
I or II.
Adc0effect_on_delivery LongString Details the effects of the
change on the delivery
schedule.
Adc0effect_on_ils LongString Details the effects of the
change on affected parts,
materials, and software.

Adc0implementation_category String [32] Designates the specific

category of the change
implementation, for
example, Prior to first
flight or Post flight
test.
Adc0is_other_ci_affected Boolean If true, other systems
or configuration items
are affected. If false,
no other systems or
configuration items are
affected by this change.
Adc0product_systems String [40] List of values that
designates the systems
or subsystems for an
item. A product system
denotes a group of
parts that perform a
common function, for
example, Electrical,
Environmental
Control, and Weapons.
Adc0product_zones String [40] Designates the zones for
an item. A zone denotes
an area or section of
the product used in
managing multiple
system interfaces and
structural interferences,
for example, Baggage
Compartment,
Electrical, and
Plumbing.

B-28 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Attribute name Storage type Description

Adc0quotation_date Date Designates the date
the quotation type was
assigned.
Adc0quotation_type String [15] Designates the quotation
type for the change
impact. For example,
Supplier ROM, Buyer
Estimate, or Supplier
Firm.

Adc0ChangeRqst
Adc0ChangeRqst is a subtype of the Adc0GnChangeRqst item type.
The following figure illustrates the Adc0ChangeRqst data model.

Adc0ChangeRqst attributes
The Adc0ChangeRqst item is provided by the adschangemanagement template.
The following table describes the attributes of the AAdc0ChangeRqst class.

Attribute name Storage type Description

Adc0change_type String [32] List of values that
specifies the type of
change documentation
for the program, for
example, ADCN, DCN,
and Redline.

Adc0ChangeRqstMaster
Adc0ChangeRqstMaster is the storage class of the item master form.
The following figure illustrates the schema definition and attributes of the
Adc0ChangeRqstMaster class.

PLM00111 G Aerospace and Defense Solution Guide B-29

Appendix B Aerospace and Defense data model

Adc0ChangeRqstRevision
Adc0ChangeRqstRevision is a subtype of the Adc0GnChangeRqstRevision
business object and represents revisions corresponding to an
Adc0ChangeRqstRevision. The following figure illustrates the
Adc0ChangeRqstRevision business object data model.

Adc0ChangeRqstRevision attributes
The Adc0ChangeRqstRevision item is provided by the adschangemanagement
template.
The following table describes the attributes of the Adc0ChangeRqstRevision class.

B-30 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Attribute name Storage type Description

Adc0costest_undercontract Integer Designates the
estimated cost under
contract for approving
and implementing the
change request. The
number is expressed in
currency, for example,
dollars or euros.
Adc0disapproval_conseq LongString Details the consequences
if the change is not
approved.
Adc0effect_on_config LongString Details the effect on
the configuration
specification for the
change.
Adc0effect_on_performance LongString Details the effect on the
product performance for
the change.
Adc0in_production Boolean If true, the change has
been implemented to
production. If false,
the change is not yet in
production.
Adc0is_primary_change Boolean If true, this is the
primary change with
related changes. If false,
this is a secondary or
subsidiary change.
Adc0is_retrofit_required Boolean If true, the change
recommends retrofit of
existing units. If false,
no retrofit is required.
Adc0justification String [32] Details the justification
or reason for the
preparation of the
change.

Adc0DevRqst
Adc0DevRqst is a subtype of the CMm0ChangeRqst item type.
The following figure illustrates the Adc0DevRqst data model.

PLM00111 G Aerospace and Defense Solution Guide B-31

Appendix B Aerospace and Defense data model

Adc0DevRqstMaster
Adc0DevRqstMaster is the storage class of the item master form. The following
figure illustrates the schema definition and attributes of the Adc0DevRqstMaster
class.

Adc0DevRqstRevision
Adc0DevRqstRevision is a subtype of the Cm0DevRqstRevision business object
and represents revisions corresponding to an Adc0DevRqst. The following figure
illustrates the Adc0DevRqstRevision business object data model.

B-32 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Adc0DevRqstRevision attributes
The Adc0DevRqstRevision item is provided by the adschangemanagement
template.
The following table describes the attributes of the Adc0DevRqstRevision class.

Attribute name Storage type Description

Adc0category String [32] Designates the specific
category of change
within the change
classification.
Adc0change_class String [15] List of values that
designates the
government’s or
customer’s classification
to a change, for example,
I or II.
Adc0effect_on_delivery LongString Details the effects of the
change on the delivery
schedule.
Adc0effect_on_ils LongString Details the effects of the
change on affected parts,
materials, and software.

PLM00111 G Aerospace and Defense Solution Guide B-33

Appendix B Aerospace and Defense data model

Attribute name Storage type Description

Adc0implementation_category String [32] Designates the specific
category of the change
implementation, for
example, Prior to first
flight or Post flight
test.
Adc0is_controlled_forexport Boolean If true, change is under
export control. If false,
change is not under
export control.
Adc0is_other_ci_affected Boolean If true, other systems
or configuration items
are affected. If false,
no other systems or
configuration items are
affected by this change.
Adc0product_systems String [40] List of values that
designates the systems
or subsystems for an
item. A product system
denotes a group of
parts that perform a
common function, for
example, Electrical,
Environmental
Control, and Weapons.
Adc0product_zones String [40] Designates the zones for
an item. A zone denotes
an area or section of
the product used in
managing multiple
system interfaces and
structural interferences,
for example, Baggage
Compartment,
Electrical, and
Plumbing.
Adc0quotation_date Date Designates the date
the quotation type was
assigned.
Adc0quotation_type String [15] Designates the quotation
type for the change
impact, for example,
Supplier ROM, Buyer
Estimate, or Supplier
Firm.

Adc0DevRqstRevMaster
Adc0DevRqstRevMaster is the storage class of the item master form
corresponding to the Adc0DevRqstRev item. The following figure illustrates the
schema definition and attributes of the Adc0DevRqstRevMaster class.

B-34 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Adc0Task
Adc0Task is a subtype of the ScheduleTask item type.
The following figure illustrates the Adc0Task data model.

Adc0Task attributes
The Adc0Task item is provided by the adschangemanagement template.
The following table describes the attributes of the Adc0Task class.

Attribute name Storage type Description

Adc0complexity String [15] Designates the
complexity of the task,
for example, high,
medium, or low.

PLM00111 G Aerospace and Defense Solution Guide B-35

Appendix B Aerospace and Defense data model

Attribute name Storage type Description

Adc0is_admin_task Boolean If true, this task
is assigned to an
administrator to
complete. If false, it
is assigned to any user
to complete.
Adc0is_ia_required Boolean If true, impact analysis
is required by impacted
supplier or organization.
If false, no impact
analysis is required.
Adc0is_proposed_task Boolean If true, this task is only
proposed and many
not be completed. If
false, this task will be
completed.
Adc0task_category String [32] List of values that
designates the category
of the task, for example,
Agenda Event,
Planning, or QA.

Adc0TaskMaster
Adc0TaskMaster is the storage class of the item master form corresponding to
the Adc0Task item. The following figure illustrates the schema definition and
attributes of the Adc0TaskMaster class.

Adc0TaskRevision
The following figure illustrates the Adc0TaskRevision business object data model.

B-36 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Adc0TaskRevisionMaster
The following figure illustrates the schema definition and attributes of the
Adc0ChangeRqstMaster class.

Contract data management objects

Cdm0Contract is a subtype of the Document item type and represents the
contract document used in document-centric programs.
Cdm0Contract is a primary business object that stores and represents contract
data. A contract is a structured procurement document listing the milestones and
the schedule dates of the contract event.
The following figure illustrates the Cdm0Contract data model.

PLM00111 G Aerospace and Defense Solution Guide B-37

Appendix B Aerospace and Defense data model

Cdm0Contract attributes
Cdm0Contract items are identified in the system by a Cdm0 property. The
Cdm0Contract item is provided by the contractmanagement template.
The following table lists the attributes of the Cdm0 class.

Attribute name Storage type Description

Cdm0Contract String(32) Classifies contract item, for example,
Category CONTRACT, TWO, and PO.

Cdm0ContractRevision attribute
The Cdm0ContractRevision class is used to store and represent contractrevision
data. Data requirement items are associated with the contract revision data.

The following table lists the attributes of the Cdm0ContractRevision class.

Attribute name Storage type Description

Cdm0ContractCost Double Specifies the total cost of the contract.
Contract cost also includes the
addition to the cost delta incurred due
to modification.

B-38 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Attribute name Storage type Description

Cdm0Contract String(32) Specifies the payment forms for the
PricingModel contract, for example, cost plus fixed
fee.
Cdm0EffectiveDate Date Specifies the date from which the
contract is effective.
Cdm0Contract Typed Specifies the milestones for the
EventSch Reference contract.
(Contract event
schedule)
Cdm0Comments String(256) Specifies any special remarks related
to the contract.
Cdm0Contract Double Specifies the relationship between the
CostDelta current contract cost and the inherent
future contract cost that may arise
due to modification of the contract.
Cdm0Office String(128) Specifies the name of the person or
PrimaryResp a role responsible for the review and
acceptance of the contract.
Cdm0Period Double Specifies the duration of the contract.
OfPerformance The duration the time period as
specified in the contract. It is
expressed in months.
Cdm0Recurring Logical Specifies whether the contract cost is
Cost recurring cost.
Cdm0SOWAffected Logical Specifies whether the statement of
work for the contract is affected due
to contract modification.

Cdm0DataReqItem attribute
The Cdm0DataReqItem class is used to store and represent data requirement item
data. Data requirement items data are associated with the contract revision.

PLM00111 G Aerospace and Defense Solution Guide B-39

Appendix B Aerospace and Defense data model

The following table lists the attributes of the Cdm0DataReqItem class.

Attribute name Storage type Description

Cdm0ContractLine String(32) Specifies the section ID within the
ItemNumber contract. This section describes how a
specific task must be accomplished.
Cdm0Contract String(128) The unique identifier for the contract on
Reference which the part is created.
Cdm0Contract TypedReferenceSpecifies the contract.
TypedRef
cdm0ProvideRec Boolean Specifies the type of contract data
ContractDel deliverable that is submitted by the
customer or the supplier.
SelectTrue to provide contract
deliverable for the supplier to review.
Select False to receive contract
deliverable from the supplier.
Cdm0Reference String(32) Specifies the ID of a specific reference
Citation content in the document.

Cdm0DataReqItemRevision attribute
The Cdm0DataReqItemRevision class is used to store and represent data
requirement item revision data.

B-40 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

The following table lists the attributes of the Cdm0DataReqItemRevision class.

Attribute name Storage type Description

cdm0Addressee Typed reference Specifies the list of contacts who
(company contact) receive the contract documents.
cdm0ApprovalCode String(32) Specifies the approval code for the
data requirement item revision.
cdm0Approval Logical Specifies whether the customer must
Required approve the data item.
cdm0CertRequired Logical Specifies whether the submitted data
item requires certification.
cdm0Comments String(256) Specifies any comments concerning
the item.
cdm0Contact String(32) Specifies the ID of the contact
Reference reference.
cdm0DataMgmt Integer Specifies the offset of the data
DueOffset management due date.
cdm0Delivery String(128) Specifies the delivery address of the
Address customer or the supplier.

PLM00111 G Aerospace and Defense Solution Guide B-41

Appendix B Aerospace and Defense data model

Attribute name Storage type Description

cdm0Delivery String(32) Specifies the mode of delivery of the
Mechanism contract.
cdm0DIDTitle String(64) Specifies the title of the data item
description document.
cdm0Distribution Logical Specifies whether any documentation
Required related to the item should be
distributed.
cdm0DRISubTitle String(64) Specifies the subtitle of the data
requirement item.
cdm0EffCutoff String(256) Specifies the date that data collection
EventDesc for the document is to stop.
cdm0Effective Date Specifies the last date for data
CutoffDate collection.
cdm0EventList Typed Reference Specifies the event table for
(Fnd0StaticTable) generating event schedule.
Cdm0ExhibitName String(32) Specifies the ID of a particular data
item in a data item description
document.
Cdm0MediaType String Specifies the format of the data, for
example, electrostatic, microfilm, and
so on.
Cdm0OfficePriResp String(128) Specifies the name of the contacts,
groups, or role responsible for
reviewing the data item.
Cdm0OPRNotifDue Integer Specifies the last date for the creation
Offset of the notification to the office of the
primary reviewers.
Cdm0Response Integer Specifies the offset to the response
DueOffset due date.
Cdm0Shipping Logical Specifies whether DD Form 250 is
DocumentReqd required for the delivery of the data
item.
Cdm0SubmitFlow Logical Specifies whether a supplier’s data
Thru requirement item should be submitted
as a customer’s data requirement
item.
Cdm0Submit String(32) Specifies the purpose of the submitted
Purpose data item.
Cdm0Submit Integer Specifies the number of copies
Quantity required for submission.

Fnd0StaticTable attribute

The Fnd0StaticTable class is used to store the rows for tabular data.

B-42 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

The following table lists the attributes of the Fnd0StaticTable class.

Attribute name Storage type Description

fnd0StaticTable TypedReference Specifies the variable length array
Data (TableProperties) attribute of the TableProperties
class that stores the rows for the data
in the event table.

Cdm0EventsTable attribute

The Cdm0EventsTable class is used to store event data in the data requirement
item (DRI) event table.

The following table lists the attributes of the Cdm0EventsTable class.

Attribute name Storage type Description

cdm0EndDate Date Specifies the event end date.
cdm0EventName String(64) Specifies the contract event name.

PLM00111 G Aerospace and Defense Solution Guide B-43

Appendix B Aerospace and Defense data model

Attribute name Storage type Description

cdm0OffSet Integer Specifies the offset used for calculating
the submittal due date for calculating
the first submittal delivery.
cdm0Recurrence String(32) Specifies frequency of the submittal
delivery event.
cdm0StartDate Date Specifies the event start date.
cdm0RelativeTo String(32) Denotes the relation of the offset to
either the start date or the end date.
cdm0Recurrence Date Specifies the last date for event
EndDate schedule.

Cdm0DID attribute
The Cdm0DID class is used to store and represent data item description data.
A data item description specifies the content and the format of the data item
requirement item.

The following table lists the attributes of the Cdm0EventsTable class.

Attribute name Storage type Description

Cdm0DIDDocCategoryString(32) Specifies user-defined attribute for
classifying document items.
Cdm0ProgramPhases String(32) Specifies the program application for the
specified DID type.

Cdm0DIDRevision attribute
The Cdm0DIDRevision class is used to represent relation between the data item
description and Cdm0DataReqItemRevision class.

B-44 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Cdm0Submittal attribute
The Cdm0Submittal class is used to store and represent data item submittal
package or document to support the requirement of generating submittal delivery
schedule for data requirement item. Submittal represents the data item submittal
package or documentation that relates to the actual documents submitted.

Cdm0SubmittalRevision attribute
The Cdm0SubmittalRevision class is used to store and represent submittal
revision data.

PLM00111 G Aerospace and Defense Solution Guide B-45

Appendix B Aerospace and Defense data model

The following table lists the attributes of the Cdm0SubmittalRevision class.

Attribute name Storage type Description

Cdm0Disposition String(32) Specifies the unique identifier for DD
Form 250 prepared for the contract
deliveries.
Cdm0ReceivedDate Date Specifies the date when an item is
received from the supplier or a date when
the item is sent to a customer.
Cdm0Resubmit Date Specifies the due date of the contract data
DueDate item to the customer.
Cdm0Submit Date Specifies the due date of the contract data
DueDate item to the customer.
Cdm0Submittal String(32) Specifies the data item submittal stage,
Maturity for example, draft, or final.
Cdm0Disposition Date Specifies the disposition or the
Date incorporation level of a change or
submittal.

B-46 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Attribute name Storage type Description

Cdm0OfficePriResp String(128) Specifies the person, group, or the role
responsible for reviewing acknowledging
the data item submittal.
Cdm0Resubmit String(256) Specifies customer’s comments during
Comments resubmittal.
Cdm0Resubmit Logical Specifies whether the data item must be
Required submitted again.
Cdm0DRLItemType String(32) Specifies whether the data item
requirement is from a customer or a
supplier.
Cdm0Shipping String(128) Specifies the ID of DD Form 250 that is
DocumentName prepared to support contract deliveries.

Cdm0Correspondence attribute
The Cdm0Corspondence class is used to store and represent correspondence data.

The following table lists the attributes of the Cdm0Corspondence class.

Attribute name Storage type Description

Cdm0CorrespDoc String(32) Specifies a category of similar technical
Category documents, for example, assembly
drawing, wire list, or material
specification.

Cdm0CorrespondenceRevision attribute
The Cdm0CorspondenceRevision class is used to store and represent
correspondence revision data.
The following table lists the attributes of the Cdm0CorspondenceRevision class.

PLM00111 G Aerospace and Defense Solution Guide B-47

Appendix B Aerospace and Defense data model

Attribute name Storage type Description

Cdm0Category String(32) Specifies correspondence category,
for example, memo.
Cdm0Correspondence String(32) Specifies whether it is an incoming
Direction or an outgoing correspondence.
Cdm0Priority String(32) Specifies the priority level for
accomplishing the task.
Cdm0ReceivedorSent Date Specifies the date of correspondence
Date from the supplier or the customer.
Cdm0ReceivedOrgName String(32) Specifies the name of the receiving
organization.
Cdm0References String(32) Specifies the list of references.
Cdm0ReplyRequested Date Specifies the date of expected reply.
Date
Cdm0ReplyRequired Logical Specifies whether a reply is required
or not.
Cdm0ResponsibleParty String(32) Specifies the person or roles
responsible for replying.

Cdm0IsDescribedbyDID attribute
The Cdm0IsDescribedbyDID class is used to represent relation between
Cdm0DIDRevision and Cdm0DataReqItem Revision to support the
requirement of creating the data requirement item revision and associating it with
the contract revision.

Cdm0ListsDRISubmittalSch attribute
The Cdm0ListsDRISubmittalSch class is used to represent relation between the
data requirement item revision and the submittal delivery schedule.

B-48 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Cdm0ListsDRISubmittal attribute
The Cdm0ListsDRISubmittalSch class is used to represent relation between
Cdm0DataReqItemRevision and submittal of the data item submittal package or
documentation that relates to the actual documents submitted.

Cdm0ListsCorspSubmittals attribute
The Cdm0ListsCorspSubmittals class is used to represent relation between
Cdm0SubmittalRevision and Cdm0CorspondenceRevision.

PLM00111 G Aerospace and Defense Solution Guide B-49

Appendix B Aerospace and Defense data model

The following table lists the attributes of the Cdm0ListsCorspSubmittals class.

Attribute name Storage type Description

Cdm0Comments String(256) Specifies any comments concerning
the item.
Cdm0References String [-1] (32) Specifies the list of references.

Cdm0ListsCorspRefItems attribute
The Cdm0ListsCorspRefItems class is used to represent relation between
Cdm0CorpondenceRevision and Cdm0ContractRevision.

Cdm0ListsContractDRI attribute
The Cdm0ListsContractDRI class is used to represent relation between
Cdm0ContractRevision and Cdm0DataReqItemRevision.

Stock material objects

The following table lists the stock material data model objects.

Symbol Object Description

Stock Material Represents a stock material object.
(SM0StockMaterial)

B-50 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Symbol Object Description

Stock Material Represents a stock material object revision.
Revision (Stock
Material Revision)

The following table describes the stock material object relation types.

Relationship Description
Made From Defines the relationship between an item
(SM0MadeFrom) revision and a stock material revision or
an item revision and a part revision, which
specifies that the item is made from a stock
material or part.

Work package objects

The following table lists the work package data model objects.

Symbol Object Description

Work Package Represents a work package object.
(Wpm0WorkPackage)
Work Package Represents a work package object revision.
Revision
(Wpm0WorkPackage
Revision)

The following table describes the work package object relation types.

Relationship Description
Static Contents Defines the relationship between a work
(Wpm0WorkPkg package revision and another object.
ContainsStatic)
This relationship specifies that if the contents
of the work package change when they are
outside the work package, the contents inside
the work package do not change.
Dynamic Contents Defines the relationship between a work
(Wpm0WorkPkg package revision and another object.
ContainsDynamic)
This relationship specifies that if contents
of the work package change when they are
outside the work package, the contents inside
the work package reflect the change.

Finish objects
The following table lists the finish data model objects.

PLM00111 G Aerospace and Defense Solution Guide B-51

Appendix B Aerospace and Defense data model

Symbol Object Description

Finish (Fsh0Finish) Represents a finish object.
Finish Revision Represents a finish object revision.
(Fsh0FinishRevision)
Finish Group Represents a finish group.
(Fsh0FinishGroup)
Finish Group Revision Represents a finish group revision.
(Fsh0FinishGroupRevision)

The following table describes the finish object relation types.

Relationship Description
Finishes Defines the relationship between a finish
(Fsh0FinishRel) or finish group with an item revision or its
subclass.
This relation is a subclass of the trace link
relation.

Data model for Aerospace and Defense relations

ADS_Lists_Parts
This relation represents the association between a technical document revision
and an ADS part or ADSDesign item.
The following table describes the components of the ADS_Lists_Parts relation.

Relation name ADS_Lists_Parts

Relation type IMAN Relation
Association ADSTechDocument Revision and ADSPart or ADSDesign
Primary object ADSTechDocument Revision
Secondary object ADSPart or ADSDesign

The following figure illustrates the ADS_Lists_Parts relation data model.

B-52 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

• Multiple ADSPart and ADSDesign items can be associated with a given

technical document using this relation.

• When a primary object is revised, the association is carried forward to a new

revision of the technical document.

The following table describes the attributes of the ADS_Lists_Parts relation.

Attribute name Storage Type Description

adsdrawing_find_number String [32] Specifies the numeric identifier, assigned
to a part, that is used to identify the part
on the face of the installation drawing
instead of the actual part number.
ads0notenumber String [128] List of flag notes on the parts list that are
referenced by the part.
adsdrawing_zone String [32] Specifies the drawing sheets and/or zones
where a part’s number or find number
is displayed. The letter designates the
vertical coordinate and the number
designates the horizontal coordinate.
adsremarks String [32] Textual optional information entered by
the user.

ADS_Lists_PartRevisions
This relation represents the association between a technical document revision and
ADS part revisions or ADSDesign revisions.
ADS_Lists_PartRevisions associates all ADSPart and ADSDesign objects
created on a given technical document with the technical document revision.
Using this relation:

• Multiple ADS part revisions or ADS design revisions can be associated with a
given ADS technical document revision.

• When a primary object is revised, the association is carried forward to a new

revision of the technical document.

PLM00111 G Aerospace and Defense Solution Guide B-53

Appendix B Aerospace and Defense data model

• When a primary object has an immature revision, the associated secondary

object can be revised independently and the revision is associated to the
immature primary object revision.

• When a primary object has an immature revision, the primary object must be
revised to revise the secondary object.

The following table describes the attributes of the ADS_Lists_PartRevisions

relation.

Attribute name Storage Type Description

adsdrawing_find_number String [32] Specifies the numeric identifier, assigned
to a part, that is used to identify the part
on the face of the installation drawing
instead of the actual part number.
ads0notenumber String [128] List of flag notes on the parts list that are
referenced by the part.
adsdrawing_zone String [32] Specifies the drawing sheets and/or zones
where a part’s number or find number
is displayed. The letter designates the
vertical coordinate and the number
designates the horizontal coordinate.
adsremarks String [32] Textual optional information entered by
the user.

ADS_Lists_DrawingRevisions
This relation represents the association between a technical document revision
and an ADS drawing revision.
The TC_Lists_DrawingRevisions relation helps in associating all the
ADSDrawing items created for a given technical document with the technical
document revision.
The following table describes the components of the TC_Lists_Drawings relation.

Relation name TC_Lists_Drawings

Relation type IMAN Relation

Association ADSTechDocument Revision andADSDrawing Revision
Primary object ADSTechDocument Revision
Secondary object ADSDrawing Revision

The following figure displays the TC_Lists_DrawingRevision relation data model.

B-54 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

• Multiple ADSDrawing Revision objects can be associated to a given technical

document revision with this relation.

• When a primary object is revised, the association is carried forward to a new

revision of the technical document.

• When the primary object has an immature revision, the associated secondary
object can be revised independently and the revision is associated to the
immature primary object revision.

• When the primary object does not have any immature revision, the primary
object needs to be revised to revise the secondary object.

The following table describes the attributes of the TC_Lists_DrawingRevisions

object.

Attribute name Storage Type Description

adsdrawing_find_number String [32] Specifies the numeric identifier, assigned
to a part, that is used to identify the part
on the face of the installation drawing
instead of the actual part number.
ads0notenumber String [128] List of flag notes on the parts list that are
referenced by the part.
adsdrawing_zone String [32] Specifies the drawing sheets and/or zones
where a part’s number or find number
is displayed. The letter designates the
vertical coordinate and the number
designates the horizontal coordinate.
adsremarks String [32] Textual optional information entered by
the user.

TC_Program_Preferred_Parts
This relation represents the association between a standard part and a program.
Multiple standard parts can be associated with a given program using this relation.
The following table describes the components of the TC_Program_Preferred_Parts
relation.

PLM00111 G Aerospace and Defense Solution Guide B-55

Appendix B Aerospace and Defense data model

Relation name TC_Program_Preferred_Parts

Relation type IMAN Relation
Association CommercialPart Item and TCProject
Primary object TCProject
Secondary object CommercialPart Item

The following figure displays the data model for the TC_Program_Preferred_Parts
relation.

The following table describes the attributes of the TC_Program_Preferred_Parts

relation.

Attribute Description
Limited Use Specifies whether the part is in use. The valid values
are Yes or No.
Limitation Specifies the limitation on the part.

Fnd0LocationForUser
This relation represents the association between a company location and a user.
Using this relation you can specify the nature of association between the company
location and the user. The association can be either true company affiliation or
design authority affiliation.
The following table describes the attribute of the Fnd0LocationForUser relation.

Attribute Storage Type Description

fnd0LocationAffiliation String [32] Specifiesthe nature of association between

the company location and the user. The valid
values are true company affiliation or design
authority affiliation.

B-56 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Fnd0LocationForGroup
This relation represents the association between a company location and a user.
Using this relation you can specify the nature of association between the company
location and the group. The association can be either true company affiliation or
design authority affiliation.
The following table describes the attribute of the Fnd0LocationForGroup relation.

Attribute Storage Type Description

fnd0LocationAffiliation
String [32] Specifiesthe nature of association between the
company location and the group. The valid
values are true company affiliation or design
authority affiliation.

Lists of values for Aerospace and Defense

Lists of values (LOVs) are used to ensure consistent data entry in Teamcenter. The
list entries are created either by referencing existing data or by entering customized
site data. After it is created, the LOV is implemented throughout the interface by
attaching the LOV to one or more properties. Creating LOVs and implementing
them throughout Teamcenter can greatly improve productivity at your site and help
prevent incorrect user entries.
For more information about creating and attaching LOVs, see Configuring list
of values (LOVs).
The Aerospace and Defense solution provides LOVs that are specific to the Aerospace
and Defense industry. Use these LOVs to configure and modify the behavior of
the template.

Adc0Change Class
Description Designates the government’s or customer’s
classification to a change. For example, I or II.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeNoticeRevision.Adc0change_class
Adc0ChangeRqstRevision.Adc0change_class
Adc0DevRqstRevision.Adc0change_class
Business object condition AnDCMTrainingProgramCondition
Default values I
II
Valid values Accepts string as a value. It must be a valid
classification.
Notes This LOV is included in the
adschangemanagement template.

PLM00111 G Aerospace and Defense Solution Guide B-57

Appendix B Aerospace and Defense data model

Adc0Change Category
Description Designates the specific category of change within
the change classification.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeRqstRevision.Adc0change_category
Adc0ChangeNoticeRevision.Adc0category
Adc0DevRqstRevision.Adc0change_category
Business object condition AnDCMTrainingProgramCondition
Default values 1
2
A
B
C
D
E
M
Valid values Accepts string as a value.
Notes This LOV is included in the
adschangemanagement template.

Adc0CN Types
Description Specifies acronyms for the types of change
documentation used on a program for a change
notice.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeNotice.Adc0change_type
Business object condition AnDCMTrainingProgramCondition
Default values ADCN
AMR
DCN
DCR
DRN
ICN
PCD
PMD
REDLINE
RR
VAR
Valid values Accepts string as a value. It must be a valid
acronym that specifies the type of change
documentation.

B-58 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Notes This LOV is included in the

adschangemanagement template.

Adc0CR Types
Description Specifies the change request types. For example,
development change or engineering change
process.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeRqst.Adc0change_type
Business object condition AnDCMTrainingProgramCondition
Default values CA

CRBD

DEV

ECP

IPCD

RFD

RFW
Valid values Accepts string as a value. It must be a valid
change request type.
Notes This LOV is included in the
adschangemanagement template.

Adc0DR Types
Description Specifies acronyms for the types of change
documentation used on a program for a deviation
request, for example, RFD or RFW.
Type ListOfValuesString
Usage Exhaustive.
Business object property Cm0DevRqst.Cm0change_type
Business object condition AnDCMTrainingProgramCondition
Default values RFD
Request for Deviation

RFW
Request for Waiver

PLM00111 G Aerospace and Defense Solution Guide B-59

Appendix B Aerospace and Defense data model

Valid values Accepts string as a value. It must be a valid

acronym that specifies the type of change
documentation.
Notes This LOV is included in the
adschangemanagement template.

Adc0Production Systems
Description Displays the list of systems or subsystems for an
item. A product system denotes a group of parts
that perform a common function. For example,
Electrical, Environmental Control, and
Weapons.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0DevRqstRevision.Adc0product_systems
Adc0ChangeRqstRevision.Adc0product_systems
Adc0ChangeNoticeRevision.Adc0product_systems
Business object condition AnDCMTrainingProgramCondition
Default values Electrical

Environmental Control

Hydraulic

Fuel

Weapons
Valid values Accepts string as a value. It must be a valid
system or subsystem.
Notes This LOV is included in the
adschangemanagement template.

Adc0Quotation Type
Description Specifies the quotation type for the change
impact, for example, Supplier ROM, Buyer
Estimate, or Supplier Firm.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0ChangeRqstRevision.Adc0quotation_type
Adc0DevRqstRevision.Adc0quotation_type
Business object condition AnDCMTrainingProgramCondition

B-60 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Default values NTE

ROM
Valid values Accepts string as a value. It must be a valid
quotation type.
Notes This LOV is included in the
adschangemanagement template.

Adc0Task Category
Description Specifies the various task categories, for
example, Agenda Event, Planning, and QA.
Type ListOfValuesString
Usage Exhaustive.
Business object property Adc0Task.Adc0task_category
Business object condition AnDCMTrainingProgramCondition
Default values Agenda Event
Engineering
ILS
Major Subcontr
Manufacturing
Non-Std Event
Part
Planning
QA
Subcontract
Valid values Accepts string as a value. It must be a valid task
category.
Notes This LOV is included in the
adschangemanagement template.

Ads0CreateStandardNoteAuthority
Description List of authorized roles for creation of StandardNote.
Type ListofValuesString
Usage Suggestive.
Business object None.
property
Business object None.
condition
Valid Values Any valid Teamcenter role.
Default Values *

PLM00111 G Aerospace and Defense Solution Guide B-61

Appendix B Aerospace and Defense data model

Notes Specifies the roles that are authorized to create or revise

standard note objects. An asterisk (*) indicates that any
Teamcenter user can create or revise standard note objects.
Apart from the user roles that are mentioned as values in the
LOV, users with DBA permission are authorized to create,
revise, update, and delete standard notes.

ADS Assembly Types

Description List of ADS assembly types.
Type ListofValuesString
Usage Exhaustive.
Business object ADSDesign.adsassembly_type
property
Business object isTrue
condition
Valid Values Any valid assembly type.
Default Values Separable
Inseparable
Notes An inseparable assembly part cannot be disassembled without
causing physical harm to at least one of the constituent parts in
the assembly.

ADSComponentAuthority
Description List of ADSComponent authorities.
Type ListofValuesString
Usage Exhaustive.
Business object None.
property
Business object None.
condition
Valid Values Any valid Teamcenter role.
Default Values *
Notes Specifies the roles that are authorized to create or revise ADS
parts or ADS design objects. An asterisk (*) indicates that any
Teamcenter user can create or revise ADS parts or ADS design
objects.

ADS Design Levels

Description List of ADS Design levels.
Type ListofValuesString

B-62 Aerospace and Defense Solution Guide PLM00111 G

 Aerospace and Defense data model

Usage Exhaustive.
Business object ADSTechDocument Revision.adsdesign_level
property
Business object isTrue
condition
Valid Values Any valid design level.
Default Values Conceptual
Prototype
Production
Notes None.

ADSDocumentCentricPrograms
Description List of ADS document-centric programs.

Type ListofValuesString

Usage Exhaustive.

Business object None.

property
Business object None.
condition
Valid Values Any valid Teamcenter program.

Default Values Training

Notes It specifies the programs that are document centric.

ADSDrawingAuthority
Description List of ADSDrawing authorities.
Type ListofValuesString
Usage Exhaustive.
Business object None.
property
Business object None.
condition
Valid Values Any valid Teamcenter role.
Default Values *
Notes Specifies the roles that are authorized to create or revise ADS
drawing objects. An asterisk (*) indicates that any Teamcenter
user can create or revise drawing objects.

PLM00111 G Aerospace and Defense Solution Guide B-63

Appendix B Aerospace and Defense data model

ADSTechDocAuthority
Description List of ADSTechDoc authorities.
Type ListofValuesString
Usage Exhaustive.
Business object None.
property
Business object None.
condition
Valid Values Any valid Teamcenter role.
Default Values *
Notes Specifies the roles that are authorized to create or revise ADS
technical document objects. An asterisk (*) indicates that any
Teamcenter user can create or revise technical document objects.

TCProgramPreferredTypes
Description Specifies the part types that are treated as preferred part types
while creating assemblies.
Valid Values Accepts string as a value. It must be a valid Teamcenter part
type.
Default Values CommercialPart
Template foundation template.

TCProgramsUsingPreferredTypes
Description Specifies the programs that use preferred parts while creating
assemblies of these parts.
Valid Values Accepts string as a value. It must be a valid Teamcenter
program.
Default Values
Template foundation template.

TcRevisionSkipLetters
Description Specifies the characters to be excluded from the revision naming
rule.
Valid Values Alphabets.
Default Values I, O, Q, S, X, Z
Template foundation template.

B-64 Aerospace and Defense Solution Guide PLM00111 G

Index

A Adc0DevRqstMaster
Adc0DevRqstMaster schema class . . . B-32
Adc0Change Category LOV . . . . . A-8, B-58 Adc0DevRqstRevision . . . . . . . . . . . . . B-32
Adc0Change Class LOV . . . . . . . . A-7, B-57 Adc0category . . . . . . . . . . . . . . . . . . B-33
Adc0ChangeNotice Adc0change_class . . . . . . . . . . . . . . B-33
Adc0change_type . . . . . . . . . . . . . . . B-22 Adc0DevRqstRevision data model . . . B-33
Adc0ChangeNotice model . . . . . . . . . B-22 Adc0effect_on_delivery . . . . . . . . . . . B-33
Adc0paper_change . . . . . . . . . . . . . . B-22 Adc0effect_on_ils . . . . . . . . . . . . . . . B-33
Adc0ChangeNotice attributes . . . . . . . . B-22 Adc0implementation_category . . . . . B-34
Adc0ChangeNoticeMaster . . . . . . . . . . B-22 Adc0is_controlled_forexport . . . . . . . B-34
Adc0ChangeNoticeMaster schema Adc0is_other_ci_affected . . . . . . . . . . B-34
class . . . . . . . . . . . . . . . . . . . . . . B-22 Adc0product_systems . . . . . . . . . . . . B-34
Adc0ChangeNoticeRevision . . . . . . . . . B-23 Adc0product_zones . . . . . . . . . . . . . . B-34
Adc0category . . . . . . . . . . . . . . . . . . B-24 Adc0quotation_date . . . . . . . . . . . . . B-34
Adc0change_class . . . . . . . . . . . . . . B-24 Adc0DevRqstRevision attributes . . . . . B-33
Adc0ChangeNoticeRevision data Adc0DevRqstRevMaster . . . . . . . . . . . B-34
model . . . . . . . . . . . . . . . . . . . . . B-24 Adc0DevRqstRevMaster schema
Adc0product_systems . . . . . . . . . . . . B-24 class . . . . . . . . . . . . . . . . . . . . . . B-35
Adc0product_zones . . . . . . . . . . . . . . B-25 Adc0DR Types LOV . . . . . . . . . . A-10, B-59
Adc0ChangeNoticeRevision Adc0GnChangeRqst
attributes . . . . . . . . . . . . . . . . . . . . . B-24 Adc0change_type . . . . . . . . . . . . . . . B-26
Adc0ChangeNoticeRevMaster . . . . . . . B-25 Adc0GnChangeRqst model . . . . . . . . B-25
Adc0ChangeRqst Adc0GnChangeRqst attributes . . . . . . . B-25
Adc0change_type . . . . . . . . . . . . . . . B-29 Adc0GnChangeRqstMaster
Adc0ChangeRqst model . . . . . . . . . . B-29 Adc0GnChangeRqstMaster schema
Adc0ChangeRqst attributes . . . . . . . . . B-29 class . . . . . . . . . . . . . . . . . . . . . . B-26
Adc0ChangeRqstMaster . . B-26, B-29, B-32 Adc0GnChangeRqstRevision . . . . . . . . B-26
Adc0ChangeRqstMaster schema Adc0category . . . . . . . . . . . . . . . . . . B-28
class . . . . . . . . . . . . . . . . . . . . . . B-30 Adc0change_class . . . . . . . . . . . . . . B-28
Adc0ChangeRqstRevision . . . . . . . . . . B-30 Adc0effect_on_delivery . . . . . . . . . . . B-28
Adc0ChangeRqstRevision data Adc0effect_on_ils . . . . . . . . . . . . . . . B-28
model . . . . . . . . . . . . . . . . . . . . . B-30 Adc0GnChangeRqstRevision data
Adc0costest_undercontract . . . . . . . . B-31 model . . . . . . . . . . . . . . . . . . . . . B-27
Adc0disapproval_conseq . . . . . . . . . . B-31 Adc0implementation_category . . . . . B-28
Adc0effect_on_config . . . . . . . . . . . . B-31 Adc0is_other_ci_affected . . . . . . . . . . B-28
Adc0effect_on_performance . . . . . . . . B-31 Adc0product_systems . . . . . . . . . . . . B-28
Adc0in_production . . . . . . . . . . . . . . B-31 Adc0product_zones . . . . . . . . . . . . . . B-28
Adc0is_primary_change . . . . . . . . . . B-31 Adc0quotation_date . . . . . . . . . . . . . B-29
Adc0is_retrofit_required . . . . . . . . . . B-31 Adc0quotation_type . . . . . . . . B-29, B-34
Adc0justification . . . . . . . . . . . . . . . B-31 Adc0GnChangeRqstRevision
Adc0ChangeRqstRevision attributes . . . B-30 attributes . . . . . . . . . . . . . . . . . . . . . B-27
Adc0CN Types LOV . . . . . . . . . . A-8, B-58 Adc0GnChangeRqstRevMaster . . . . . . B-27
Adc0CR Types LOV . . . . . . . . . . . A-9, B-59 Adc0Production Systems LOV . . A-10, B-60
Adc0DevRqst Adc0Quotation Type LOV . . . . . A-11, B-60
Adc0DevRqst model . . . . . . . . . . . . . B-32

PLM00111 G Aerospace and Defense Solution Guide Index-1

Index

Adc0Task ADS_Lists_Parts relation attributes

Adc0complexity . . . . . . . . . . . . . . . . B-35 ads0notenumber . . . . . . . . . . . . . . . B-55
Adc0is_admin_task . . . . . . . . . . . . . B-36 ADS_Lists_Parts relation attributes
Adc0is_ia_required . . . . . . . . . . . . . . B-36 adsremarks . . . . . . . . . . . . . . . . . . . B-55
Adc0is_proposed_task . . . . . . . . . . . B-36 ADS_Lists_Parts relation attributes
Adc0Task model . . . . . . . . . . . . . . . . B-35 adsremarks . . . . . . . . . . . . . . . . . . . B-53
Adc0task_category . . . . . . . . . . . . . . B-36 ADS_Lists_Parts relation attributes
Adc0Task attributes . . . . . . . . . . . . . . B-35 adsdrawing_find_number . . . . . . . . . B-53
Adc0Task Category LOV . . . . . . A-11, B-61 ADS_Lists_PartsRevisions relation
Adc0TaskMaster . . . . . . . . . . . . . . . . . B-36 Attributes . . . . . . . . . . . . . . . . . . . . B-54
Adc0TaskMaster schema class . . . . . B-36 Ads0CreateStandardNoteAuthority
Adc0TaskRevision . . . . . . . . . . . . . . . . B-36 LOV . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Adc0TaskRevision data model . . . . . . B-37 adschangemanagement template . . . . . B-21
Adc0TaskRevisionMaster . . . . . . . . . . . B-37 ADSComponentAuthority LOV . . . . . . . . 2-7
Adc0TaskRevisionMaster schema ADSDesign . . . . . . . . . . . . . . . . . . . . . B-9
class . . . . . . . . . . . . . . . . . . . . . . B-37 ads0source_doc_ref . . . . . . . . . . . . . B-10
Adc0TrngNamingRule naming rule . . . A-5 adsassembly_type . . . . . . . . . . . . . . B-10
Adc0TrngRevNamingRule revision naming adsdesign_category . . . . . . . . . . . . . B-10
rule . . . . . . . . . . . . . . . . . . . . . . . . . A-6 adsdistribution_code . . . . . . . . . . . . B-11
Adding properties . . . . . . . . . . . . . . . . 2-12 adsinstallation . . . . . . . . . . . . . . . . . B-11
Adding standard preferred parts to adsqualification_req . . . . . . . . . . . . . B-11
programs . . . . . . . . . . . . . . . . . . . . . 5-18 adssource_doc_category . . . . . . . . . . B-11
ADS Trng Categories LOV . . . . . . . . . . A-12 adssource_doc_org . . . . . . . . . . . . . . B-11
ADS Trng Design Categories LOV . . . . A-13 adssource_doc_revision . . . . . . . . . . . B-11
ADS Trng Dist Code LOV . . . . . . . . . . A-14 adssource_document . . . . . . . . . . . . B-11
ADS Trng DOC Categories LOV . . . . . . A-12 adssource_tdoc_category . . . . . . . . . . B-11
ADS Trng DWG Categories LOV . . . . . A-13 adsspecial_handling . . . . . . . . . . . . . B-11
ADS Trng Part Categories LOV . . . . . . A-14 Attributes . . . . . . . . . . . . . . . . . . . . B-10
ADS Trng PL Categories LOV . . . . . . . A-13 ADSDesign attributes . . . . . . . . . . . . . B-10
ADS Trng SDRL Categories LOV . . . . . A-13 ADSDesign Revision
ADS_Lists_DrawingRevisions Data model . . . . . . . . . . . . . . . . . . . B-14
relation . . . . . . . . . . . . . . . . . . . . . . B-54 TC_Is_Represented_By relation . . . . B-14
ADS_Lists_DrawingRevisions relation ADSDesignMaster . . . . . . . . . . . . . . . B-11
Attributes . . . . . . . . . . . . . . . . . . . . B-55 ADSDesignVerMaster . . . . . . . . . . . . . B-14
ADS_Lists_PartRevisions relation . . . . B-53 ADSDrawing . . . . . . . . . . . . . . . . . . . B-14
ADS_Lists_Parts relation . . . . . . . . . . . B-52 ADSDrawing attributes . . . . . . . . . . B-15
Attributes . . . . . . . . . . . . . . . . . . . . B-53 ADSDrawing data model . . . . . . . . . B-14
Data model . . . . . . . . . . . . . . . . . . . B-52 ADSDrawing attributes . . . . . . . . . . . . B-14
ADS_Lists_Parts relation attributes ADSDrawing Master
adsdrawing_find_number . . . . . . . . . B-55 ADSDrawing Master schema class . . B-15
ADS_Lists_Parts relation attributes ADSDrawing Revision . . . . . . . . . . . . . B-17
adsdrawing_zone . . . . . . . . . . . . . . . B-55 ads0source_doc_ref . . . . . . . . . . . . . B-15
ADS_Lists_Parts relation attributes adsdistribution_code . . . . . . . . . . . . B-15
ads0notenumber . . . . . . . . . . . . . . . B-53 ADSDrawingRevision data model . . . B-17
ADS_Lists_Parts relation attributes adsqualification_req . . . . . . . . . . . . . B-15
adsdrawing_zone . . . . . . . . . . . . . . . B-54 adssource_doc_category . . . . . . . . . . B-15
ADS_Lists_Parts relation attributes adssource_doc_org . . . . . . . . . . . . . . B-15
adsdrawing_zone . . . . . . . . . . . . . . . B-53 adssource_doc_revision . . . . . . . . . . . B-15
ADS_Lists_Parts relation attributes adssource_document . . . . . . . . . . . . B-15
adsdrawing_find_number . . . . . . . . . B-54 adssource_tdoc_category . . . . . . . . . . B-15
ADS_Lists_Parts relation attributes ADSDrawingAuthority LOV . . . . . . . . . . 2-7
adsremarks . . . . . . . . . . . . . . . . . . . B-54 ADSDrawingMaster . . . . . . . . . . . . . . B-15
ADS_Lists_Parts relation attributes ADSPart . . . . . . . . . . . . . . . . . . . . . . B-5
ads0notenumber . . . . . . . . . . . . . . . B-54 ADS_Lists_Parts . . . . . . . . . . . . . . . B-5

Index-2 Aerospace and Defense Solution Guide PLM00111 G

 Index

ads0source_doc_ref . . . . . . . . . . . . . B-6 List of values . . . . . . . . . . . . . . . . . . B-1

adsinstallation . . . . . . . . . . . . . . . . . B-7 Object type . . . . . . . . . . . . . . . . . . . B-1
ADSPart data model . . . . . . . . . . . . B-5 Object type master . . . . . . . . . . . . . . B-1
adsqualification_req . . . . . . . . . . . . . B-7 Object type number . . . . . . . . . . . . . B-1
adssource_doc_category . . . . . . . . . . B-6 Object type revision . . . . . . . . . . . . . B-1
adssource_doc_org . . . . . . . . . . . . . . B-6 Preconditions and postactions . . . . . . B-1
adssource_doc_revision . . . . . . . . . . . B-6 Template information . . . . . . . . . . . . B-1
adssource_document . . . . . . . . . . . . B-6 Aerospace and Defense Foundation . . . . . 1-2
adssource_tdoc_category . . . . . . . . . . B-6 Aerospace and Defense relations . . . . . 1-11
ADSPart attributes . . . . . . . . . . . . . . . B-6 ADS_Lists_DrawingRevisions . . . . . . 1-11
ADSPart Revision . . . . . . . . . . . . . . . . B-9 ADS_Lists_Parts . . . . . . . . . . . . . . . 1-11
ADSPart Revision data model . . . . . . B-9 ADS_Lists_PartsRevisions . . . . . . . . 1-11
ADSPartMaster . . . . . . . . . . . . . . . . . B-7 Cdm0IsDescribedbyDID . . . . . . . . . . 1-12
ADSPartMaster schema class . . . . . . B-7 Cdm0ListsContractDRI . . . . . . . . . . 1-12
ADSPartVerMaster . . . . . . . . . . . . . . . B-9 Cdm0ListsCorspRefItems . . . . . . . . . 1-12
ADSTechDocAuthority LOV . . . . . . . . . . 2-7 Cdm0ListsCorspSubmittals . . . . . . . 1-12
ADSTechDocument . . . . . . . . . . . . . . . B-2 Cdm0ListsDRISubmittal . . . . . . . . . 1-12
ADS TechDocument attributes . . . . . B-2 Cdm0ListsDRISubmittalSch . . . . . . . 1-12
adscategory . . . . . . . . . . . . . . . . . . . B-2 ListsCustomNotes . . . . . . . . . . . . . . 1-11
adsdistribution_code . . . . . . . . . . . . B-3 ListStandardNotes . . . . . . . . . . . . . . 1-11
adsgovt_data_right . . . . . . . . . . . . . B-3 TC_Program_Preferred_Items . . . . . . 1-11
adstech_doc_category . . . . . . . . . . . . B-3 Aerospace and Defense Training . . . . . . . 1-2
ADSTechDocument data model . . . . . B-2 Aerospace and Defense Training
ADSTechDocument attributes . . . . . . . B-2 Program . . . . . . . . . . . . . . . . . . . . . . A-1
ADSTechDocument Master . . . . . . . . . B-3 AnDCMTrainingProgramCondition
ADSTechDocument Master schema condition . . . . . . . . . . . . . . . . . . . . . . A-3
class . . . . . . . . . . . . . . . . . . . . . . B-3 Assign location code . . . . . . . . . . . . . . . 4-1
ADSTechDocument Revision . . . . . . . . B-4 Associating preferred standard parts to
ADSTechDocument Revision data programs . . . . . . . . . . . . . . . . . . . . . 5-19
model . . . . . . . . . . . . . . . . . . . . . B-4 Authorized data access . . . . . . . . . . . . 2-16
ADSTechDocumentVerMaster . . . . . . . B-5 Authorized data access (IP) basic
adstrainingprogram_template.xml file . . A-2 tasks . . . . . . . . . . . . . . . . . . . . . . . . 2-17
ADSTrngCondition condition . . . . . . . . A-3 Authorized data access (ITAR) basic
Aerospace and Defense business objects tasks . . . . . . . . . . . . . . . . . . . . . . . . 2-17
ADSDesign . . . . . . . . . . . . . . . . . . . . 1-9
CommercialPart . . . . . . . . . . . . . . . . . 1-9 B
Contract data . . . . . . . . . . . . . . . . . 1-10
Contract revision . . . . . . . . . . . . . . . 1-10 Basic tasks
Correspondence . . . . . . . . . . . . . . . . 1-10 Authorized data access (IP) . . . . . . . . 2-17
Correspondence revision . . . . . . . . . . 1-10 Authorized data access (ITAR) . . . . . 2-17
Custom Note . . . . . . . . . . . . . . . . . . 1-10 Build an assembly for a document-centric
Data item description . . . . . . . . . . . . 1-10 program . . . . . . . . . . . . . . . . . . . . . . 5-20
Data item description revision . . . . . . 1-10 Build an assembly for a document-centric
Data item requirement revision . . . . . 1-10 program
Data requirement item . . . . . . . . . . . 1-10 My Teamcenter . . . . . . . . . . . . . . . . 5-21
Drawing . . . . . . . . . . . . . . . . . . . . . . 1-9 Building an assembly for a document-centric
Event data table . . . . . . . . . . . . . . . 1-10 program
Part . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 ADS_Lists_Parts . . . . . . . . . . . . . . . 5-20
Standard Note . . . . . . . . . . . . . . . . . . 1-9 Business Modeler IDE . . . . . . . . . 2-10–2-12
Submittal . . . . . . . . . . . . . . . . . . . . 1-10
Submittal revision . . . . . . . . . . . . . . 1-10 C
Tabular data table . . . . . . . . . . . . . . 1-10
Technical document . . . . . . . . . . . . . . 1-9 Change forms . . . . . . . . . . . . . . . . . . . 2-11
Aerospace and Defense data model . . . . B-1 Change Home . . . . . . . . . . . . . . . . . . . 2-11

PLM00111 G Aerospace and Defense Solution Guide Index-3

Index

Change notices . . . . . . . . . . . . . . . . . . 2-10 Enterprise change notices

Change object naming rules . . . . . . . . . A-5 Creating . . . . . . . . . . . . . . . . . . . . . . 8-4
Change requests . . . . . . . . . . . . . . . . . 2-10 Exclude licenses . . . . . . . . . . . . . . . . . 2-16
CommercialPart . . . . . . . . . . . . . . . . . B-17 Extension rules
CommercialPart attributes . . . . . . . . B-18 Base-Action . . . . . . . . . . . . . . . . . . . . 2-5
CommercialPart data model . . . . . . . B-18 Post-Action . . . . . . . . . . . . . . . . . . . . 2-5
TC_Program_Preferred_Parts Pre-Action . . . . . . . . . . . . . . . . . . . . . 2-5
relation . . . . . . . . . . . . . . . . . . . B-18 Pre-Condition . . . . . . . . . . . . . . . . . . 2-5
CommercialPart attributes . . . . . . . . . B-18
adsassembly_type . . . . . . . . . . . . . . B-18 F
adsdistribution_code . . . . . . . . . . . . B-18
adspart_category . . . . . . . . . . . . . . . B-18 Finishes
adsspecial_handling . . . . . . . . . . . . . B-18 Apply to item occurrence . . . . . . . . . 12-7
CommercialPart Master Apply to item revision . . . . . . . . . . . 12-5
CommercialPartMaster schema Basic concepts . . . . . . . . . . . . . . . . . 12-1
class . . . . . . . . . . . . . . . . . . . . . . B-19 Configure . . . . . . . . . . . . . . . . . . . . 12-2
CommercialPart Revision . . . . . . . . . . B-20 Create finish . . . . . . . . . . . . . . . . . . 12-4
CommercialPartMaster . . . . . . . . . . . . B-19 Create finish group . . . . . . . . . . . . . 12-4
Configuration audits Create library . . . . . . . . . . . . . . . . . 12-3
Action item . . . . . . . . . . . . . . . . . . . 13-4 Install . . . . . . . . . . . . . . . . . . . . . . . 12-2
Associate related objects . . . . . . . . . . 13-5 Interface . . . . . . . . . . . . . . . . . . . . . 12-5
Basic concepts . . . . . . . . . . . . . . . . . 13-1 Thin client
Configure . . . . . . . . . . . . . . . . . . . . 13-2 Apply to item occurrence . . . . . . 12-9
Create . . . . . . . . . . . . . . . . . . . . . . . 13-3 Apply to item revision . . . . . . . . 12-9
Thin client Create finish . . . . . . . . . . . . . . . 12-8
AssociatE related objects . . . . . . 13-7 Create finish group . . . . . . . . . . 12-8
Create . . . . . . . . . . . . . . . . . . . 13-5 Interface . . . . . . . . . . . . . . . . . . 12-7
Create action item . . . . . . . . . . . 13-6 Fnd0LocationForGroup
Configuring Aerospace and Defense . . . . 1-3 fnd0LocationAffiliation . . . . . . . . . . . B-57
Configuring the Multi-Site Collaboration Fnd0LocationForUser . . . . . . . . B-56–B-57
environment . . . . . . . . . . . . . . . . . . . 2-18 fnd0LocationAffiliation . . . . . . . . . . . B-56
Create change notices . . . . . . . . . . . . . 2-10 Forms . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Create change requests . . . . . . . . . . . . 2-10
Create company location . . . . . . . . . . . . 4-1 G
Creating deviation requests . . . . . . . . . . 8-3
Creating enterprise change notices . . . . . 8-4 Generating reports
Custom note BOM line view . . . . . . . . . . . . . . . . . . 6-1
View and edit a custom note . . . . . . . 7-12 Favorites . . . . . . . . . . . . . . . . . . . . . . 6-1
Custom notes . . . . . . . . . . . . . . . . . . . . 7-9 Find number . . . . . . . . . . . . . . . . . . . 6-2
Add or edit custom note text . . . . . . . 7-10 Nomenclature . . . . . . . . . . . . . . . . . . 6-2
Attach a custom note . . . . . . . . . . . . 7-12 Part number . . . . . . . . . . . . . . . . . . . 6-2
Create a custom note . . . . . . . . . . . . 7-10 Quantity . . . . . . . . . . . . . . . . . . . . . . 6-2
Revise a custom note . . . . . . . . . . . . 7-14 Remark . . . . . . . . . . . . . . . . . . . . . . . 6-2
Structure Manager . . . . . . . . . . . . . . . 6-1
D
I
Deviation requests
Creating . . . . . . . . . . . . . . . . . . . . . . 8-3 IDSM service . . . . . . . . . . . . . . . . . . . 2-18
Installing training program . . . . . . . . . A-1
E Integrated Distributed Services Manager
(IDSM) service . . . . . . . . . . . . . . . . . 2-18
Edit company location . . . . . . . . . . . . . . 4-2 IP licenses . . . . . . . . . . . . . . . . . . . . . 2-16
Enabling Aerospace and Defense . . . . . . 1-2 Is Owned By Program access rule . . . . . 2-19
Entering standard note data . . . . . . . . . 7-3 ITAR licenses . . . . . . . . . . . . . . . . . . . 2-17

Index-4 Aerospace and Defense Solution Guide PLM00111 G

 Index

L Ads0AssociateChangeNotice . . . . . . . B-20
Licenses authorizationCheckOnRevise . . . . . . B-16
Exclude . . . . . . . . . . . . . . . . . . . . . . 2-16 authorizationCheckOnSaveAs . . . . . . B-16
IP . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16 autoAssignToProject . . . . . . . . B-17, B-20
ITAR . . . . . . . . . . . . . . . . . . . . . . . 2-17 checkLatest_Released . . . . . . . B-16, B-19
List of Values for Aerospace and checkTechDocPrivilege . . . . . . . . . . . B-16
Defense . . . . . . . . . . . . . . . . . . . . . . B-57 cmpSrcDocRelationOnCreate . . . . . . B-16
ADS Assembly Types . . . . . . . . . . . . B-62 cmpSrcDocRelationOnRevise . . . . . . B-17
ADS Design Levels . . . . . . . . . . . . . . B-62 cmpSrcDocRelationOnSaveAs . . . . . . B-16
Ads0CreateStandardNoteAuthority . . B-61 DCPCheckMandatoryValuesSaveas . . B-16
ADSDocumentCentricPrograms . . . . B-63 Description . . . . . . . . . . . . . . . . . . . B-2
ADSDrawingAuthority . . . . . . . . . . . B-63 Extension point . . . . . . . . . . . . . . . . B-1
ADSTechDocAuthority . . . . . . . . . . . B-64 Extension rule name . . . . . . . . . . . . B-1
TCProgramPreferredTypes . . . . . . . . B-64 Operation name . . . . . . . . . . . . . . . . B-1
TCProgramsUsingPreferredTypes . . . B-64 Parameters . . . . . . . . . . . . . . . . . . . B-2
TcRevisionSkipLetters . . . . . . . . . . . B-64 setOrgOnCreation . . . . . . . . . B-17, B-20
LOVs validateImport . . . . . . . . . . . . B-16, B-19
Adc0Change Category . . . . . . . A-8, B-58 validateOrgOnCreation . . . . . B-16, B-19
Adc0Change Class . . . . . . . . . . A-7, B-57 Preconditions and postactions on
Adc0CN Types . . . . . . . . . . . . . A-8, B-58 Adc0ChangeNotice . . . . . . . . . . . . . . B-22
Adc0CR Types . . . . . . . . . . . . . A-9, B-59 autoAssignToProject . . . . . . . . . . . . . B-23
Adc0DR Types . . . . . . . . . . . . A-10, B-59 postactions of Adc0ChangeNotice . . . B-23
Adc0Production Systems . . . . A-10, B-60 Preconditions on
Adc0Quotation Type . . . . . . . . A-11, B-60 Adc0ChangeNotice . . . . . . . . . . . B-23
Adc0Task Category . . . . . . . . A-11, B-61 setOrgOnCreation . . . . . . . . . . . . . . B-23
ADS Trng Categories . . . . . . . . . . . . A-12 setOrgOnImport . . . . . . . . . . . . . . . B-23
ADS Trng Design Categories . . . . . . . A-13 validateImport . . . . . . . . . . . . . . . . . B-23
ADS Trng Dist Code . . . . . . . . . . . . . A-14 validateOrgOnCreation . . . . . . . . . . B-23
ADS Trng DOC Categories . . . . . . . . A-12 Preconditions and postactions on
ADS Trng DWG Categories . . . . . . . . A-13 ADSDesign . . . . . . . . . . . . . . . . . . . . B-12
ADS Trng Part Categories . . . . . . . . A-14 Ads0AssociateChangeNotice . . B-13, B-17
ADS Trng PL Categories . . . . . . . . . A-13 authorizationCheckOnRevise . . . . . . B-12
ADS Trng SDRL Categories . . . . . . . A-13 authorizationCheckOnSaveAs . . . . . . B-12
Ads0CreateStandardNoteAuthority . . . 2-7 autoAssignToProject . . . . . . . . . . . . . B-13
ADSComponentAuthority . . . . . . . . . . 2-7 checkLatest_Released . . . . . . . . . . . . B-13
ADSDrawingAuthority . . . . . . . . . . . . 2-7 checkTechDocPrivilege . . . . . . . . . . . B-12
ADSTechDocAuthority . . . . . . . . . . . . 2-7 cmpSrcDocRelationOnCreate . . . . . . B-13
cmpSrcDocRelationOnRevise . . . . . . B-13
cmpSrcDocRelationOnSaveAs . . . . . . B-13
M DCPCheckMandatoryValuesSaveas . . B-12
Microsoft Office 2003 access to setOrgOnCreation . . . . . . . . . . . . . . B-13
Teamcenter . . . . . . . . . . . . . . 2-2, 2-6, 5-8 validateImport . . . . . . . . . . . . . . . . . B-12
Multi-Site Collaboration . . . . . . . . . . . 2-18 validateOrgOnCreation . . . . . . . . . . B-12
Preconditions and postactions on
N ADSPart . . . . . . . . . . . . . . . . . . . . . . B-7
Naming rules . . . . . . . . . . . . . . . . . . . A-5 Ads0AssociateChangeNotice . . . . . . . B-9
Notes authorizationCheckOnRevise . . . . . . B-8
Standard notes . . . . . . . . . . . . . . . . . 7-1 authorizationCheckOnSaveAs . . . . . . B-7
autoAssignToProject . . . . . . . . . . . . . B-8
checkLatest_Released . . . . . . . . . . . . B-8
P checkTechDocPrivilege . . . . . . . . . . . B-8
Preconditions and postactions . . . . . . . B-1, cmpSrcDocRelationOnCreate . . . . . . B-8
B-15–B-16, B-19 cmpSrcDocRelationOnRevise . . . . . . B-9

PLM00111 G Aerospace and Defense Solution Guide Index-5

Index

cmpSrcDocRelationOnSaveAs . . . . . . B-8 Replace standard note revision . . . . . . 7-7

DCPCheckMandatoryValuesSaveas . . B-7 Starting ****OBSOLETE**** . . . . . . . 2-12
postactions of ADSPart . . . . . . . . . . . B-8 Stock materials
Preconditions on ADSPart . . . . . . . . B-7 Add to library . . . . . . . . . . . . . . . . . 10-4
setOrgOnCreation . . . . . . . . . . . . . . B-8 Basic concepts . . . . . . . . . . . . . . . . . 10-1
validateImport . . . . . . . . . . . . . . . . . B-8 Configure pseudo folder display . . . . . 10-2
validateOrgOnCreation . . . . . . . . . . B-7 Create . . . . . . . . . . . . . . . . . . . . . . . 10-3
Preconditions and postactions on Create library . . . . . . . . . . . . . . . . . 10-3
ADSTechDocument . . . . . . . . . . . . . . B-3 Install . . . . . . . . . . . . . . . . . . . . . . . 10-1
authorizationCheckOnRevise . . . . . . B-4 Made from . . . . . . . . . . . . . . . . . . . . 10-5
authorizationCheckOnSaveAs . . . . . . B-3 Program preferred . . . . . . . . . . . . . . 10-4
autoAssignToProject . . . . . . . . . . . . . B-4 Query . . . . . . . . . . . . . . . . . . . . . . . 10-8
checkAdsAttachment . . . . . . . . . . . . B-4 Thin Client
setOrgOnCreation . . . . . . . . . . . . . . B-4 Create . . . . . . . . . . . . . . . . . . . 10-9
validateImport . . . . . . . . . . . . . . . . . B-4 Made from . . . . . . . . . . . . . . . 10-10
validateOrgOnCreation . . . . . . . . . . B-4 Syntax
Prerequisites for Aerospace and Standard note text . . . . . . . . . . . . . . . 7-1
Defense . . . . . . . . . . . . . . . . . . . . . . . 1-1
Project-level security T
Multi-Site Collaboration import and
export . . . . . . . . . . . . . . . . . . . . 2-20 Tabs
Projects Change Home . . . . . . . . . . . . . . . . . 2-11
Multi-Site Collaboration TC_Program_Preferred_Parts . . . . . . . B-55
environment . . . . . . . . . . . . . . . . 2-20 Limitation . . . . . . . . . . . . . . . . . . . . B-56
Properties, adding . . . . . . . . . . . . . . . . 2-12 Limited Use . . . . . . . . . . . . . . . . . . B-56
TC_Program_Preferred_Parts
R components . . . . . . . . . . . . . . . . B-55
Teamcenter Environment Manager
Removing preferred parts from installer . . . . . . . . . . . . . . . . . . . . . . A-1
assemblies . . . . . . . . . . . . . . . . . . . . 5-19 Teamcenter Foundation . . . . . . . . . . . . . 1-2
Removing preferred parts from Teamcenter vendor management . . . . . . 1-1
programs . . . . . . . . . . . . . . . . . . . . . 5-20 Training program . . . . . . . . . . . . . A-1–A-2
TrngNamingRule naming rule . . . . . . . A-4
S TrngRevNamingRule revision naming
rule . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Search
Program data . . . . . . . . . . . . . . . . . 14-1
Search forms V
Programs . . . . . . . . . . . . . . . . . . . . 14-1 Validating standard notes for technical
Searching for program data . . . . . . . . . 14-1 documents . . . . . . . . . . . . . . . . . . . . . 7-8
Select Features panel . . . . . . . . . . . . . . 1-2 Vendor management template . . . . . . . . 1-9
Split the preferred part from assemblies
Impact Analysis . . . . . . . . . . . . . . . . 5-19
W
Split the preferred part from programs
Tc_Program_Preferred_Items . . . . . . 5-20 Work packages
Standard note Add objects . . . . . . . . . . . . . . . . . . . 11-3
Revise a standard note . . . . . . . . . . . . 7-6 Basic concepts . . . . . . . . . . . . . . . . . 11-1
View parametric values . . . . . . . . . . . 7-6 Create . . . . . . . . . . . . . . . . . . . . . . . 11-2
Standard note text syntax . . . . . . . . . . . 7-1 Install . . . . . . . . . . . . . . . . . . . . . . . 11-1
Standard notes Thin client
Attach a standard note . . . . . . . . . . . . 7-5 Add items . . . . . . . . . . . . . . . . . 11-4
Create a standard note item . . . . . . . . 7-2 Create . . . . . . . . . . . . . . . . . . . 11-3
Entering data . . . . . . . . . . . . . . . . . . 7-3

Index-6 Aerospace and Defense Solution Guide PLM00111 G