Teamcenter 13.

Deploying
Aerospace and
Defense
PLM00569 - 13.0
 Contents

Overview of Teamcenter Aerospace and Defense 1-1

Installing Aerospace and Defense

Install Aerospace and Defense ───────────────────────────── 2-1
Install Aerospace and Defense on Active Workspace ─────────────── 2-2

Configuring Aerospace and Defense

Assign an owning organization for an object ──────────────────── 3-1
Configuring part management ───────────────────────────── 3-1
Configure a source document for a document-centric program ───────────── 3-1
Assign roles to users for working with Aerospace and Defense ───────────── 3-3
Configure standard parts and preferred standard parts ────────────────── 3-3
Configure standard notes ─────────────────────────────────── 3-4
Configure custom notes ──────────────────────────────────── 3-6
Configure a single notes section for items in Active Workspace ───────────── 3-8
Configuring CAGE codes and company locations ───────────────── 3-9
Configure creating CAGE codes for a company location ───────────────── 3-9
Assign a company location to users and groups ───────────────────── 3-11
Configure adding finishes to item revisions ──────────────────── 3-13
Configuring contract data management ────────────────────── 3-14
Configure attaching a DRI or its revision to a contract ────────────────── 3-14
Configure attaching a submittal or its revision to a submittal task ────────── 3-14
Configuring a Multi-Site Collaboration environment ────────────── 3-15
Overview of configuring the Multi-Site Collaboration environment ───────── 3-15
Configure a multisite collaboration environment to support data exchange ──── 3-15

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 2

© 2020 Siemens
 1. Overview of Teamcenter 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 the Teamcenter Aerospace and Defense solution with other Teamcenter
optional modules.

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 1-1

© 2020 Siemens
 1. Overview of Teamcenter Aerospace and Defense

1-2 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 2. Installing Aerospace and Defense
Install Aerospace and Defense
Install the Teamcenter Aerospace and Defense solution using Teamcenter Environment Manager.

Prerequisites

Teamcenter Managing Vendor Data in Rich Client is a prerequisite for installing the Aerospace and
Defense solution.

You must have administrator privileges to configure the solution.

To install Aerospace and Defense:

1. In Teamcenter Environment Manager, select the appropriate options until you reach the Features
panel.

2. In the Features panel, expand the Extensions navigation tree.

3. Under Supplier Relationship Management, select Vendor Management.

4. Under Aerospace and Defense, select Aerospace and Defense Foundation

5. (Optional) Select Aerospace and Defense Training.

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.

6. (Optional) Select Aerospace and Defense Change Management.

Aerospace and Defense Change Management is only enabled if you select Change
Management under Enterprise Knowledge Management.

7. Choose the following under Enterprise Knowledge Management:

• (Optional) Change Management

The Teamcenter Change Management functionality enables you to initiate, administer, review,
approve, and execute changes to your product throughout its life cycle.

• (Optional) Contract Data Management

Contract data management helps the contractor manage the creation, review, and delivery of
data deliverables, such as the reports and documents that are required as a part of a contract.

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 2-1

© 2020 Siemens
 2. Installing Aerospace and Defense

• (Optional) Finish Management

Finish management helps designers create and manage finishes in Teamcenter.

• (Optional) Stock Material

This functionality helps manage stock materials in Teamcenter, performing actions like creating
libraries of stock materials and assigning stock materials to parts.

• (Optional) Work Package Management

Install Aerospace and Defense on Active Workspace

Prerequisites

Before you install Aerospace and Defense on Active Workspace, you must:

1. Install the Aerospace and Defense platform features.

2. Install Active Workspace on the Teamcenter server that has the Teamcenter Foundation feature
installed.
This makes Active Workspace features available for installation in Teamcenter Environment
Manager (TEM).
For detailed instructions on installing or updating Active Workspace, refer to the Active Workspace
Deployment and Configuration help.

Install Aerospace and Defense on Active Workspace

Select the following features under Active Workspace Server Extensions and Active Workspace Client
features.

Active Workspace Server Extensions features are available in the Features panel under Base
Install→Active Workspace→Server Extensions.

• Vendor Management

• Workflow

• (Enabled only after you select the earlier options) Aerospace and Defense:

• Aerospace and Defense Foundation

• (Optional) Aerospace and Defense Change Management

• (Optional) Finish Management

Installs finish management support for Active Workspace. A finish represents a finishing process on a
part. It may be used to improve properties such as appearance, adhesion, corrosion resistance, tarnish
resistance, chemical resistance, and wear resistance and remove burrs.

2-2 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 Install Aerospace and Defense on Active Workspace

• (Optional) Stock Material

Installs stock material management support in Active Workspace for performing actions, such as using
libraries of stock materials and assigning stock materials to parts.

• (Optional) Contract Data Management

Installs contract data management support in Active Workspace, which helps contractors manage the
creation, review, and delivery of contracts. A contract is a structured procurement document that lists
milestones and schedule dates.

• (Optional) Work Package Management

Installs work package management support in Active Workspace. A work package or package is a
collection of CAD files and documentation that an outsourcing partner uses for building, testing, or
maintaining a component or subassembly of a larger product. This package serves as a revisable
collection or a container of product information and can be used in a variety of contexts.

Active Workspace Client features are available in the Features panel under Base Install→Active
Workspace→Client.

• Vendor Management

• Workflow

• Active Content

• Aerospace and Defense Foundation

• (Optional) Finish Management

• (Optional) Stock Material

• (Optional) Contract Data Management

• (Optional) Work Package Management

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 2-3

© 2020 Siemens
 2. Installing Aerospace and Defense

2-4 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 3. Configuring Aerospace and Defense
Assign an owning organization for an object
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. To create organizations, create groups using the Teamcenter Organization
functionality.

Aerospace and Defense uses the TcSetOwningOrganization global constant and the
AutoAssignOwningOrg business object constant to automatically set the owning organization for an
object. You set the owning organization as the one corresponding to the logon group of the user.

The following example explains the setting of the ADSPart business object organization when the
values of the TcSetOwningOrganization and AutoAssignOwningOrg constants are set to true or false.

TcSetOwning AutoAssign
Organization OwningOrg Behavior

true true Automatic setting of owning organization for ADS

part types is enabled.

true false The owning organization is not set for the ADS
part type.

false true The owning organization is not set for ADS part
types because the system does not mandate that
the owning organization for business objects be
set automatically.

Configuring part management

Configure a source document for a document-centric program

In Aerospace and Defense, programs can be document centric or part centric. A document-centric
program requires that you create a source document before you create an ADS object, such as a part,
design, or drawing. By default, a technical document is used as the source document. However, you can
configure Teamcenter Aerospace and Defense to select a custom type of document as a source
document.

Additionally, document-centric programs are conditional. You must add the program name to the
Ads0IsDocumentCentric condition in Business Modeler IDE to make it document centric.

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 3-1

© 2020 Siemens
 3. Configuring Aerospace and Defense

Example:
u.project_name="ProgramLH" or u.group_name="Engineering"

Here, ProgramLH is the name of the program.

To specify a custom document type as a source document

1. In Business Modeler IDE, create a custom document type, for example, Ads0Email of type Email.

2. In Business Modeler IDE, open the part, design, or drawing (ADSPart, ADSDesign, ADSDrawing) for
which you want to add a custom document type.

a. Click the Main tab.

b. In the Business Object Constants tab, set the value of the

AdsAllowAttachingDocTypesToADSObjs business object constant to the custom document
type that you created.

Example:
Consider you want to add Ads0Email as a source document for a part. Open ADSPart in
Business Modeler IDE and in the Business Object Constants tab, add AdsEmail to the
AdsAllowAttachingDocTypesToADSObjs constant.

3. For the DocumentRevision object, create the same Generic Relationship Manager (GRM) rules that
are available for the ADSTechDocumentRevision object. The DocumentRevision object is the
parent of the custom document type.

For example, for the part object:

a. In BMIDE, open the DocumentRevision object.

b. In the GRM Rules tab, add a GRM rule with the following options:

Field name Value

Secondary Object AdsPart Revision

Relation Object ADS_Lists_PartRevisions

Condition Select an appropriate condition, for example, isTrue.

Ensure that the Primary and Secondary columns contain the same objects for each rule as
the ones for the ADSTechDocumentRevision object.

3-2 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 Assign roles to users for working with Aerospace and Defense

4. Set the value of the ADSTechDocument_subtype_autocreate preference as the name of the

custom document type.

For example, set the value of ADSTechDocument_subtype_autocreate as Ads0Email.

Assign roles to users for working with Aerospace and Defense

You must grant relevant authorization to users to create, revise, and save Aerospace and Defense
business objects. Authority is based on your user's current role. When this user creates or revises a
technical document, part, design, or drawing, Teamcenter compares the user's role to the roles defined
in the authority list of values (LOV) that applies to the object being created or revised. If the role is
defined in the LOV, the user is granted the permission to create or revise the object.

Using Business Modeler IDE and LOVs, you can specify the user roles that can create, revise, and save
Aerospace and Defense business objects, such as ADSTechDocument, ADSPart, ADSDesign,
ADSDrawing, and Ads0StdNote.

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

The following table lists the LOVs that you can update for specific business objects.

For business object Update LOV

ADSTechDocument ADSTechDocAuthority

ADSPart and ADSDesign ADSComponentAuthority

ADSDrawing ADSDrawingAuthority

Ads0StdNote Ads0CreateStandardNoteAuthority

Configure standard parts and preferred standard parts

Standard parts are parts that may be used across multiple programs and whose design is controlled by a
standard specification.

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

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 3-3

© 2020 Siemens
 3. Configuring Aerospace and Defense

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

Enable standard parts to be used as preferred parts for a program

To enable a standard part as a preferred part of a program, use GRM rules to set the
TC_Program_Preferred_Items relation between the standard part and the program.

When creating the GRM rule, add the following information to the GRM Rule dialog box.

Field name Value

Primary Object TC_Project

Secondary Object The object to be used as the preferred

standard part

Relation Object TC_Program_Preferred_Items

Enable a program to use preferred standard parts

Update the TCProgramsUsingPreferredTypes LOV with the name of the program that must use
preferred standard parts in their assemblies.

Configure standard notes

In Aerospace and Defense, standard notes are parametric variable values established by the Standards
Engineering group to conform to the design practices of a program. Designers apply these to multiple
parts and documents. Standard notes are often categorized and maintained in a library. Design
engineers associate these notes with items, such as parts, technical documents, designs, and drawings.

You can perform the following configurations for standard notes:

Configure 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 the
roles.

3-4 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 Configure standard notes

Set the delimiter that separates parameters in a standard note text

A standard note contains both text and parameters and also contains applicable values for the
parameters in the following syntax:

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

Example:
Quench in oil from [Temperature: 400, 500, 600] C and hold for [Time: 5, 10, 15] min

The default delimiter for parameters in the note text is a comma (,). To change this delimiter, add the
appropriate delimiter to the Fnd0ParamReqDelimiter global constant.

Enable multiple revisions of a standard note to be attached to items or item revisions

By default, only a single revision of a standard note can be attached to an item or item revision.

You can enable multiple revisions of the same standard note to be attached to an item or item revision
or attach both the master and the revision of the standard note to an item or item revision.

Settings Resultant action

AWC_Ads1AllowedAddNotesTypes preference is You can attach both the master and the
set to Ads0StdNote, Ads0StdNoteRevision revision of the standard note to an
item.

AllowMultipleRevisionsofStdNotes global You can attach multiple revisions of a

constant is set to true standard note to an item.

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 3-5

© 2020 Siemens
 3. Configuring Aerospace and Defense

Configure custom notes

Custom notes contain data that is unique to a part or a document. A designer responsible for a technical
document or part can create a custom note.

You can configure the following behavior for custom notes:

3-6 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 Configure custom notes

Enable multiple revisions of a custom note to be attached to items or item revisions

By default, you can attach a custom note only to a single item or revision of the same item.

Set the following global constants and preferences to attach the same custom note to multiple parts or
items or their revisions.

Settings Resultant action

The Fnd0AllowMultiRevOfCustomNote global You can attach multiple revisions of a

constant is set to true custom note to a part revision.

The Fnd0AttachCustomNoteToMultiItems global You can attach an existing custom note

constant is set to false to multiple parts or item revisions.

The Fnd0AttachCustomNoteToMultiItems global You can reuse (clone) an existing

constant is set to false custom note and attach it to another
part or document.

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 3-7

© 2020 Siemens
 3. Configuring Aerospace and Defense

Settings Resultant action

and
The Allow_Custom_Note_Cloning preference is
set to true

Configure a single notes section for items in Active Workspace

You can configure a single Notes section for both standard notes and custom notes in Active Workspace:

1. Set the value of the AWC_Ads1AllowedAddNotesTypes preference to specify both standard and
custom note revisions.

Example:
Set AWC_Ads1AllowedAddNotesTypes to
Ads0StdNoteRevision,Ads0CustomNoteRevision.

2. Add Fnd0ListsCustomNotes.Ads0CustomNoteRevision to the objectSet attribute in the style

sheet that you use to configure object sets.

<objectSet source="Fnd0ListsParamReqments.Ads0StdNote,
Fnd0ListsParamReqments.Ads0StdNoteRevision,
Fnd0ListsParamReqments.Fnd0ParamReqOcc,
Fnd0ListsParamReqments.Ads0CustomNoteRevision"
defaultdisplay="tableDisplay" sortdirection="descending">

3-8 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 Configure creating CAGE codes for a company location

Note:
The Ads1OnlyNotesSection.xml sample style sheet is available in %TC-DATA%\xrts folder.

3. By default, Aerospace and Defense supports standard notes and their revisions. Adding
Fnd0ListsCustomNotes.Ads0CustomNoteRevision enables support for custom note revisions.

(Optional) If you also want to support adding custom notes in the Notes section, you need to add a
Generic Relationship Manager (GRM) rule. To do this:

a. In BMIDE, open the ItemRevision object.

b. In the GRM rules tab, add a GRM rule with the following options:

Field name Value

Secondary Object Ads0CustomNote

Relation Object Fnd0ListsParamReqments

Condition Select an appropriate condition, for example, isTrue.

4. Add Fnd0ListsCustomNotes.Ads0CustomNote to the objectSet attribute in the style sheet that

you use to configure object sets.

<objectSet source="Fnd0ListsParamReqments.Ads0StdNote,
Fnd0ListsParamReqments.Ads0StdNoteRevision,
Fnd0ListsParamReqments.Fnd0ParamReqOcc,
Fnd0ListsParamReqments.Ads0CustomNoteRevision,
,Fnd0ListsCustomNotes.Ads0CustomNote"
defaultdisplay="tableDisplay" sortdirection="descending">

Configuring CAGE codes and company locations

Configure creating CAGE codes for a company location

A Commercial And Government Entity (CAGE) code is a unique identifier assigned to suppliers and to
government or defense agencies by the Defense Logistics Agency (DLA), a combat support agency in
the United States Department of Defense. A CAGE code is a standardized method of identifying a facility
at a specific location. This reference helps identify the supplier for a part.

Perform the following configurations for creating and managing CAGE codes:

Set business constants

Set the following global constants using Business Modeler IDE to regulate the creation of CAGE codes:

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 3-9

© 2020 Siemens
 3. Configuring Aerospace and Defense

Fnd0MaintainUniqueLocationCode
Maintains a unique CAGE code for each company location. This is used when an end user creates a
new CompanyLocation business object and must enter a CAGE code in the Company Location
field.

Value Description

false (default) The system creates the new company location with the entered
CAGE code.

true The system checks if there is any other company location that exists
with same CAGE code. If yes, the system displays an error message:

The Location Code already exists. Please

choose different
Location Code.

If no, the system creates the new company location with the
entered CAGE code.

Fnd0AllowSuggestiveLocationCode
Determines whether an end user is allowed to enter a location code that does not exist for any
company location when creating a new CompanyLocation business object.

Value Description

true (default) When a user enters a new CAGE code in the Company Location
field, 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 Yes, the new CAGE code is created and saved.

false The end user must select from the list of existing CAGE codes. If
they enter 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.

Fnd0DisplayLocationCodeLov
Determines if the Location Code box in the User Setting field should be a text box or should
display a list of values (LOV) with CAGE codes.

3-10 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 Assign a company location to users and groups

Value Description

false (default) Location Code is a text box.

Users can enter a CAGE code or search for and select any existing
CAGE code.

true Location Code is an LOV.

Users can select from only those CAGE codes that are assigned to
them.

Make CAGE codes visible

To make the CAGE code visible when an end user creates and edits items and item revisions, set the
fnd0OriginalLocationCode attribute of the item or item revision using Business Modeler IDE. You can
make the attribute visible and mandatory.

Hide the company location assign functionality

You can hide the Assign Company Location functionality from specified groups or roles using the
Command Suppression feature.

Assign a company location to users and groups

You must assign company locations to users and groups.

Note:
Ensure that you have created company locations first. For details on how to create a company
location, see the Managing Vendor Data in Rich Client help.

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

The Assign Company Location dialog box is displayed.

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 3-11

© 2020 Siemens
 3. Configuring Aerospace and Defense

2. Select the appropriate groups or users from the Organization list.

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.

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

5. In the Select A Relation dialog box, select one of the following relations.

Relation Description

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.

Design Authority Choose this option if the groups or users assigned to the company
Affiliation 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 the company location.

3-12 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 Configure adding finishes to item revisions

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 Assign Company Location dialog box.

Option Description

User and Group Shows both users and groups in the Company Location list.

Group Shows only groups in the Company Location list.

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.

If the default company location is not set, this functionality uses the following rules to set the default
company location:

• If there are multiple company locations with design authority but only one company location with
true affiliation, the company location with true affiliation is chosen.

• If there are multiple company locations with true affiliation, the first company location with true
affiliation is chosen.

• If there is only one company location, this location is chosen irrespective of whether it is true
affiliation or design authority.

• If there are multiple company locations with design authority but no company location with true
affiliation, the default company location is not set.

Configure adding finishes to item revisions

A finish represents a finishing process on a part. It may be used to improve appearance, adhesion, and
resistance to corrosives, tarnishing, chemicals, wear and tear, to remove burrs, and so on.

To configure finishes, update the values of the following preferences.

UsingAssignFinishDialog

Value Description

TRUE (default) To make the Open by Name dialog box available when an end user
chooses the Assign Finish command.

FALSE To make the Classification Search dialog box available when an

end user chooses the Assign Finish command.

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 3-13

© 2020 Siemens
 3. Configuring Aerospace and Defense

ItemRevision_DefaultChildProperties

• Set the value of the preference to Fsh0FinishRel to add the finish object as a child of an item
revision.

• This preference along with the ItemRevision_PseudoFolder preference allows an end user to
create the Finishes folder under an item revision.

• To add the finish as a child of other objects, update the respective child property preferences
(ObjectRevision_DefaultChildProperties) 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.

ItemRevision_PseudoFolder

• Set the value of the preference to Fsh0FinishRel to add the Finishes folder under an item
revision.

• To add the Finishes folder to other objects, update the values of the folder preferences
(ObjectRevision_PseudoFolder) of those respective objects. For example, set the value of the
PartRevision_PseudoFolder preference to Fsh0FinishRel to add the Finishes folder under the
part revision object.

Configuring contract data management

Configure attaching a DRI or its revision to a contract

You can attach a data requirement item (DRI) or its item revision to a contract. This is controlled using
the preference Cdm0AllowedDRIType.

The default value of this preference is Cdm0DataReqItem. This attaches a DRI to a contract. To attach the
item revision to the contract instead, modify the value of this preference to Cdm0DataReqItemRevision.

Configure attaching a submittal or its revision to a submittal task

You can attach a submittal or its item revision to a submittal task on generating a submittal delivery
schedule. This is controlled using the preference AttachSubmittalTypeRev.

The default value of this preference is false. This attaches the submittal to a submittal task. To attach the
submittal revision to a submittal task instead, modify the value of this preference to true.

3-14 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
 Overview of configuring the Multi-Site Collaboration environment

Configuring a Multi-Site Collaboration environment

Overview of configuring the Multi-Site Collaboration environment

Multi-Site Collaboration helps to easily share product information across your entire enterprise by
allowing exchange of Teamcenter data objects between databases. To do this, each database must be
easily accessible using TCP/IP, either over the Internet or through your company intranet.

In Aerospace and Defense, when the data objects are exchanged between databases, ensure that the
user who is initiating the data exchange is a member of the program whose objects are being
exchanged. In addition, ensure that the user who belongs to the DBA group with DBA privileges in
Teamcenter is running the Integrated Distributed Services Manager (IDSM) service.

Alternatively, you can use access rules for the program whose objects are being exchanged.

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.

Configure a multisite collaboration environment to support data exchange

Use this procedure to configure the Is Owned By Program rule to grant the privileges required to
exchange data between databases in a Multi-Site Collaboration environment.

1. Start the Access Manager application.

2. Select the parent tree rule to which you wish to add the new node.

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.

Deploying Aerospace and Defense, Teamcenter 13.0 PLM00569 13.0 3-15

© 2020 Siemens
 3. Configuring Aerospace and Defense

11. Grant the search, import, export, publish, transfer in, and transfer out privileges as follows.

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 the rule tree.

14. Click Save .

3-16 PLM00569 13.0 Deploying Aerospace and Defense, Teamcenter 13.0

© 2020 Siemens
Siemens Digital Industries Software
Headquarters Europe
Granite Park One Stephenson House
5800 Granite Parkway Sir William Siemens Square
Suite 600 Frimley, Camberley
Plano, TX 75024 Surrey, GU16 8QD
USA +44 (0) 1276 413200
+1 972 987 3000

Asia-Pacific
Americas Suites 4301-4302, 43/F
Granite Park One AIA Kowloon Tower, Landmark East
5800 Granite Parkway 100 How Ming Street
Suite 600 Kwun Tong, Kowloon
Plano, TX 75024 Hong Kong
USA +852 2230 3308
+1 314 264 8499

About Siemens Digital Industries Software

Siemens Digital Industries Software is a leading global provider of product life cycle management
(PLM) software and services with 7 million licensed seats and 71,000 customers worldwide.
Headquartered in Plano, Texas, Siemens Digital Industries Software works collaboratively with
companies to deliver open solutions that help them turn more ideas into successful products. For
more information on Siemens Digital Industries Software products and services, visit
www.siemens.com/plm.
This software and related documentation are proprietary and confidential to Siemens.
© 2020 Siemens. A list of relevant Siemens trademarks is available. Other trademarks belong to
their respective owners.