0% found this document useful (0 votes)

52 views168 pages

As - Built - Manager

The document provides a comprehensive guide to the As-Built Manager in Teamcenter 13.0, detailing its features, installation, configuration, and usage. It covers essential tasks such as creating and managing as-built structures, comparing them with product definitions, and visualizing physical structures. Additionally, it addresses data sharing and collaboration in multi-site environments.

Uploaded by

cad cad

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

52 views168 pages

As - Built - Manager

Uploaded by

cad cad

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 168

Teamcenter 13.

As-Built Manager
PLM00124 - 13.0
Contents

Getting started with As-Built Manager

Getting started with As-Built Manager ──────────────────────── 1-1
Before you begin ────────────────────────────────────── 1-1
As-Built Manager interface ─────────────────────────────── 1-2
As-Built Manager perspective ─────────────────────────────────
1-2
As-Built Manager menus ──────────────────────────────────── 1-3
As-Built Manager buttons and symbols ───────────────────────────
1-8
What are perspectives and views? ─────────────────────────────
1-11
Basic concepts for using As-Built Manager ───────────────────── 1-11
Search for As-Built Manager objects ───────────────────────── 1-13
Basic tasks for using As-Built Manager ─────────────────────── 1-13
As-Built Manager process task flow ───────────────────────── 1-14

Installing and configuring As-Built Manager

Installing As-Built Manager ─────────────────────────────── 2-1
Install As-Built Manager ───────────────────────────────── 2-1
Configuring As-Built Manager ───────────────────────────── 2-3
Setting as-built preferences ─────────────────────────────── 2-3
Setting as-built global and property constants ─────────────────── 2-4
Setting as-built global and property constants ─────────────────────── 2-4
Set up automated creation of part logistics forms ───────────────────── 2-4
Define default values for part logistics form ──────────────────────── 2-5
Define part logistics form name prefix ──────────────────────────── 2-5
Define usage property ───────────────────────────────────── 2-5
Reuse an authorized deviation ──────────────────────────────── 2-6
Setting as-built business object constants ────────────────────── 2-6
Setting as-built business object constants ────────────────────────── 2-6
Identify neutral item types ─────────────────────────────────── 2-6
Define physical part types ─────────────────────────────────── 2-7
Setting up as-built naming rules ──────────────────────────── 2-7
Setting as-built lists of values (LOVs) ───────────────────────── 2-8
Setting as-built lists of values (LOVs) ───────────────────────────── 2-8
Define valid deviation status list ─────────────────────────────── 2-8
Define deviation authority list ───────────────────────────────── 2-8
Configuring as-built workflows ───────────────────────────── 2-9

Creating neutral structures

What is the neutral structure? ───────────────────────────── 3-1
Creating product structures ─────────────────────────────── 3-2
Creating product structures ────────────────────────────────── 3-2
Creating neutral structures ────────────────────────────────── 3-3
Defining global alternates ─────────────────────────────────── 3-3

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 2

Defining substitute parts ──────────────────────────────────── 3-4

Creating and managing part logistics data ───────────────────── 3-5
Creating and managing part logistics data ───────────────────────── 3-5
Managing part logistics forms ───────────────────────────────── 3-5
Edit part logistics data ───────────────────────────────────── 3-8
Override part logistics data in context ──────────────────────────── 3-9
Defining parts for tracking ────────────────────────────────── 3-10
Create a lot definition ───────────────────────────────────── 3-10
Create a serial number generator ────────────────────────────── 3-11
Set or unset generic serial number generator ─────────────────────── 3-12
Define part usage ─────────────────────────────────────── 3-14

Generating as-built physical structures

Generating as-built physical structures ──────────────────────── 4-1
Generate a partial or entire as-built structure (top down) ──────────── 4-3
Build an as-built physical structure (bottom up) ────────────────── 4-5
View the neutral structure details ─────────────────────────── 4-5
Duplicate an as-built structure ───────────────────────────── 4-6
Generate an as-maintained structure from an as-built structure ──────── 4-8
Generate an as-built structure from an as-maintained structure ──────── 4-9

Setting up as-built physical structures

Setting up as-built physical structures ──────────────────────── 5-1
Resolving missing parts ───────────────────────────────── 5-2
Update physical part properties ──────────────────────────── 5-2
Assign a serial number ────────────────────────────────── 5-3
Assign a manufacturer ID ──────────────────────────────── 5-4
Assign a lot number ──────────────────────────────────── 5-4
Rename a physical part ────────────────────────────────── 5-5
Install a physical part ─────────────────────────────────── 5-6
Uninstall a physical part ──────────────────────────────── 5-10
Replace a physical part ───────────────────────────────── 5-11
Rebasing physical parts ───────────────────────────────── 5-15
Rebase a physical part ────────────────────────────────── 5-17
Delete a physical part ────────────────────────────────── 5-17
Implementing deviations ──────────────────────────────── 5-18
Implementing deviations ─────────────────────────────────── 5-18
Create a deviation authority item ──────────────────────────────
5-18
Set up a deviation ─────────────────────────────────────── 5-19
Send the deviation authority item through the required workflow ──────────
5-19
Install a deviated part ─────────────────────────────────────
5-20
View the deviation authorization information ──────────────────────
5-22
Release an as-built physical structure ──────────────────────── 5-23
Rebuilding an as-built structure ─────────────────────────── 5-24
Rebuild an as-built structure ────────────────────────────── 5-26
View untraced structures ──────────────────────────────── 5-27

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3

Comparing as-built structures

Comparing as-built structures ───────────────────────────── 6-1
Comparing structures with or without context ─────────────────── 6-1
Comparing with context ──────────────────────────────────── 6-1
Set compare with context preferences ─────────────────────────── 6-2
Perform compare with context ──────────────────────────────── 6-2
Comparing without context ────────────────────────────────── 6-4
Set compare without context preferences ───────────────────────── 6-4
Perform compare without context ────────────────────────────── 6-5
Clear comparison ───────────────────────────────────── 6-6
Comparing a neutral structure to a physical structure ────────────── 6-6
Comparing as-built physical structures to neutral structures ─────────────── 6-6
Compare with context example between a neutral structure and a physical structure
─────────────────────────────────────────────── 6-7
Compare without context example between a neutral structure and a physical structure
─────────────────────────────────────────────── 6-9
Comparing two physical structures ───────────────────────── 6-11
Comparing two as-built physical structures ──────────────────────── 6-11
Compare with context example between two physical structures ─────────── 6-11
Compare without context example between two physical structures ──────── 6-13

Visualizing as-built physical structures

Visualizing as-built physical structures ──────────────────────── 7-1
Associating image file datasets ──────────────────────────── 7-2
Visualize the as-built structure model ──────────────────────── 7-2
Using the graphics menu ──────────────────────────────── 7-4

Navigating the 3D model 8-1

Sharing As-Built Manager data

Sharing As-Built Manager data ───────────────────────────── 9-1
Export an as-built structure ─────────────────────────────── 9-1
Importing as-built structures ────────────────────────────── 9-3
Importing as-built structures ───────────────────────────────── 9-3
Import an as-built structure ────────────────────────────────── 9-4
Import as-built structure exceptions ───────────────────────────── 9-5
Re-import as-built structure behavior ──────────────────────────── 9-6
Managing As-Built Manager data for Multi-Site Collaboration ───────── 9-8
Managing As-Built Manager data for Multi-Site Collaboration ────────────── 9-8
Multi-Site Collaboration support for as-built structures ────────────────── 9-9
As-Built Manager actions on stub and replica objects ────────────────── 9-10

As-Built Manager preferences

4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

SLM core preferences

Glossary C-1

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5

© 2020 Siemens
6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0
© 2020 Siemens
1. Getting started with As-Built Manager
Getting started with As-Built Manager
As-Built Manager is a separately licensed application that is installed as an optional overlay on top of the
standard Teamcenter product. This application allows you to manage the as-built configuration of an
asset realized from a product definition structure, such as a design or manufacturing structure. You can
use As-Built Manager to:

• Create the as-built physical product instantiation for any configured product structure.

• Store and manage additional information about the as-built physical part structure that is not tracked
on the product definition structure, such as serial numbers and lot numbers.

• Reconcile the as-built structure with a configured product definition structure to identify parts that
are missing, alternates, substitutes, or deviations.

• Compare the as-built structure to the product definition structure or to another as-built structure.

• View the as-designed product structure and the as-built physical structure configuration side-by-side
or by using the embedded viewer available in the rich client.

• Import an as-built structure from an external manufacturing execution system (MES) or an enterprise
resource planning (ERP) system in PLM XML.

• Export an as-built structure to an Teamcenter Enterprise Service Lifecycle Management (SLM) system
using Data Exchange.

• Manage as-built structures in a Multi-Site Collaboration environment.

Before you begin

Prerequisites The As-Built Manager application requires a separate license in

addition to the standard Teamcenter product license. You
must obtain and install the appropriate licenses required to
run the As-Built Manager application.

Enable As-Built Manager As-Built Manager does not need to be enabled before you use
it, but you must select this feature and the associated
components during installation.
If you have trouble accessing As-Built Manager, see your
system administrator; it may be a licensing issue. The As-Built
Manager application requires a separate license in addition to
the standard Teamcenter product license.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 1-1

Configure As-Built Manager There are additional steps you must perform to configure As-
Built Manager before you can use it.

Start As-Built Manager Click As-Built Manager in the navigation pane.

As-Built Manager interface

As-Built Manager perspective

1 Teamcenter component pane Shows the Teamcenter folders and components.

2 Data pane Allows you to view data about the selected line. To display
a different data pane, click its tab.

As-Built Manager uses the Teamcenter rich client interface.

Not all of the following menu commands and buttons may be available on your system, as the
administrator can hide or reveal only those commands and buttons that are appropriate for your site.

1-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

As-Built Manager menus

File menu

Command Description

New → Workflow Process (Ctrl+P) Creates a new workflow process.

New → Item Creates a new item.

New → Folder Creates a new folder.

New → Dataset Creates a new dataset.

Duplicate As-Built Structure Creates a duplicate of the as-built physical structure.

Close Closes the As-Built Manager application.

Open (Ctrl+O) Opens the selected structure.

Exit Ends the rich client session.

Edit menu

Command Description

Cut (Ctrl+X) Marks the selected lines for removal and copies the content to
the clipboard. Cut lines are only removed once pasted elsewhere
in the structure.

Copy (Ctrl+C) Copies the selected lines to the clipboard.

Paste (Ctrl+V) Inserts the Clipboard contents below the selected item.

Paste Special Allows you to specify a relation type rather than using the
default paste relation when pasting an object reference into an
item or item revision.

Delete Deletes the selected object from the database.

User Setting Displays the User Settings dialog box, where you can change
your group, role, or volume assignments, and your application
logging and journaling options.

Options Changes your user interface settings that affect all applications,
not only As-Built Manager.

Toggle In-Context Mode Enables or disables editing in context mode, allowing creation
of absolute occurrences for the selected assembly.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 1-3

View menu

Command Description

Refresh (F5) Updates the information displayed for a selected line and all of
its children.

Refresh Window Synchronizes the currently displayed as-built structure with the
database. The displayed structure refreshes with changes that
have been made in other sessions and saved since you loaded
the currently displayed as-built structure.

Properties Displays the properties for the selected item.

Access... Displays the user access for the selected item.

Show Data Panel Shows or hides the data pane containing, for example,
properties data or the embedded viewer.

Show/Hide Second Structure Displays a second structure pane below the first. You can set the
Panel size of each structure pane by moving the horizontal split bar
between the panes. If the second structure pane is displayed,
this button hides the lower pane.

Show/Hide Collaboration Panel Shows or hides the collaboration panel.

Expand Expands the substructure immediately below the selected lines.

Expand Below Expands the complete substructure below the selected lines.

Expand Below... Expands the substructure below the selected lines to a user-
selected level. You can also collapse an expanded substructure
when you choose this option (hide certain child lines).

Collapse Below Collapses the complete substructure below the selected lines
(hide all child lines).

Pack (Ctrl+Shift+M) Packs the selected lines so that all lines with the same item
revision and find number are displayed as a single line. The
actual quantity of lines appended to the node.

Unpack (Ctrl+Shift+N) Unpacks the selected packed lines so that they are displayed as
separate lines, one for each occurrence.

Pack All Packs all packable lines in the displayed structure.

Unpack All Packs all packable lines in the displayed structure.

Show Unconfigured Variants Shows or hides unconfigured variant components.

Show Unconfigured Assigned Shows assigned objects that were configured out by the variant
Occurrences rules of the structures from which the objects were assigned.
You can only use this command with composition structures.

1-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Command Description

Note:
This command does not automatically refresh. Any
changes to the assigned objects are not reflected in the
structure until you execute this command again.

Show Unconfigured Changes Shows unconfigured changes. If you hide unconfigured

changes, only those changes configured by the current revision
rule are visible.

Show Unconfigured By Shows or hides components that are not configured when using
Occurrence Effectivity occurrence effectivity.

Show Untraced Parts Shows or hides the neutral parts that are not traceable in the
physical structure.

Tools menu

Command Description

Check-In/Out → Check-Out Checks a selected component out of the database.

Check-In/Out → Check-In Checks a selected component into the database.

Check-In/Out → Cancel Check-out Cancels a request checkout action.

Check-In/Out → Transfer Check- Transfers a selected, checked-out component to another user.

out

Check-In/Out → Notification List Allows you to view or edit the list of users who are informed if
the selected component is checked in or checked out.

Check-In/Out → Check-Out Allows you to view the history of checkout actions for the
History selected component.

Id Display Rule → View/Set Allows you to view the ID display rule currently applied to the
Current selected structure or set a different ID display rule.

Id Display Rule → Modify Current Modifies the ID display rule currently applied to the selected
structure.

Id Display Rule → Create/Edit Creates a new ID display rule or modify an existing ID rule.

Revision Rule → View/Set Current Allows you to view or set the revision rule for the currently
displayed structure.

Revision Rule → Set Date/Unit/End Sets the date, unit number, or end item to configure the
Item structure, if the current rule allows.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 1-5

Command Description

Revision Rule → Set Override Sets an override folder to override item revisions that would
folder otherwise be selected by other criteria.

Revision Rule → Modify Current Modifies the current revision rule and apply the modified rule to
the current structure. You can save the change if you have write
access to the original rule.

Revision Rule → Create/Edit Creates or edits a revision rule.

Variants → Configure Variants Allows you to configure or edit a variant structure for the
selected top level module.

Variants → Only Configure Root Allows you to set to on to only display options for the top-level
module, regardless of the line selected. Set to off to configure
the structure for a lower level module.

Variants → Search Searches for an existing variant item.

Variants → Count Modules Counts the modules defined for the selected variant structure.

Arrangements → View/Set Allows you to view or set the current NX arrangements.

Current

Export → Objects Exports selected objects in Teamcenter format, STEP format or a

new or available application interface. When you export an
object in Teamcenter or STEP format, you move all internal data
associated with that object.

Export → To PLMXML Exports the selected structure and its attachments in the PLM
XML format to a selected export directory. You must choose the
appropriate transfer mode for the destination system.
If you export a structure in which substitute components are
defined, the substitutes are also exported.

Export → Objects to Excel Exports the selected structure lines to an Excel spreadsheet.

Import → Templates Imports a specification, object, or Excel template.

Import → Objects Imports objects in a Teamcenter format or STEP format to your

Teamcenter database.

Import → From PLMXML Imports objects in the PLMXML format to your Teamcenter
database.

Import → Remote Imports objects from a remote site using Multi-Site

Collaboration.

Rebase Physical Part Updates the physical part to the latest design of the neutral
structure.

1-6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Command Description

Compare Compares two as-built structures or compares the as-built

structure to the neutral product structure in separate windows.

Clear Clears the results of comparing two structures.

Find in Other Structure Finds the selected object in another structure pane. The search
follows the closest match rule if it does not find an exact match.

Rename Physical Part Allows you to change the part number and serial number of a
physical part.

Create Lot Allows you to create lot information when you select a part
defined as a lot part. Lot information includes lot number,
manufacturer ID, and lot size.

Create Serial Number Generator Allows you to create numbering scheme information for a serial
number on a neutral part that is defined as a serialized part. The
numbering scheme information is used for serial number
generation on physical parts generated from that neutral part.
For example, you can define a prefix, suffix, or maximum
number for the serial numbers generated.

Generate As-Built Structure Creates a physical as-built structure from the selected neutral
structure.

Name Occurrence Assigns a name to the occurrence for the selected neutral part
using the predefined naming rules.

Assign Lot Assigns a lot number to the selected physical part.

Install Physical Part Adds or installs a copied physical part into the current as-built
structure.

Uninstall Physical Part Uninstalls and removes the selected lines from the as-built
structure completely and does not place them on the clipboard.

Replace Physical Part Replaces a selected physical part in the current as-built structure
with a copied part.

Setup Deviation Opens the Setup Deviation wizard. Use the Setup Deviation
wizard to search for a deviation document to associate to the
physical part.

Rebuild Physical Structure Creates a new build revision of a physical part.

Generate As-Maintained Generates an as-maintained physical structure from an as-built

Structure physical structure.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 1-7

As-Built Manager buttons and symbols

Note:
You can add buttons that are not displayed on the main toolbar by right-clicking the toolbar,
choosing Customize, and selecting the buttons you want to add. Once you have added buttons to
the toolbars, they are displayed in future sessions. Consider adding buttons that:

• You use frequently.

• Provide a shortcut to menu commands that are not primary selections, for example,
Tools → Revision Rule → Set Date/Unit/End Item....

Button Purpose

These standard buttons are located on the main toolbar at the top of the as-built structure pane.

Soft abort If enabled, allows you to terminate the current operation

without closing As-Built Manager or losing data.

Cut Cuts the selected lines from the structure and places them
on the clipboard.

Copy Copies the selected lines in the structure and places them on
the clipboard.

Paste Pastes the components from the clipboard as children of the

currently selected (assembly) line in the structure.

Delete Deletes the selected object from the database.

Show/Hide data pane Shows or hides the data pane containing, for example,
properties data or the embedded viewer.

Show/Hide the lower Displays a second structure pane below the first. You can set
structure pane the size of each structure pane by moving the horizontal split
bar between the panes. If the second structure pane is
displayed, this button hides the lower pane.

Show/Hide the Displays or hides the collaboration pane, which provides

collaboration pane advanced features for configuring structures. These features
relate primarily to Multi-Structure Manager.

Create lot Allows you to create lot information when you select a part
defined as a lot part. Lot information includes lot number,
manufacturer ID, and lot size.

Show untraced parts Shows or hides the neutral parts that are not traceable in the
physical structure.

1-8 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Button Purpose

Create serial number Allows you to create numbering scheme information for a
generator serial number on a neutral part that is defined as a serialized
part. The numbering scheme information is used for serial
number generation on physical parts generated from that
neutral part. For example, you can define a prefix, suffix, or
maximum number for the serial numbers generated.

Generate as-built Creates a physical as-built structure from the selected neutral
structure structure.

Name occurrence Assigns a name to the occurrence for the selected line using
the predefined naming rules.

View/Set current Allows you to view or set the revision rule on the current
line.

Configure variants Allows you to view and configure the variant option values
for the selected line.

Refresh Updates the information displayed for a selected line and all
of its children.

Find selected in other When you select a component in the BOM in one structure
panel pane and click this button, you can search for the component
in the BOM in the other structure pane. The search follows
the closest match rule if it does not find an exact match.

Pack selected line Packs the selected lines so that all lines with the same item
revision and find number are displayed as a single line. The
actual quantity of lines appended to the node.

Unpack selected line Unpacks the selected packed lines so that they are displayed
as separate lines, one for each occurrence.

Install physical part Adds or installs a physical part into the current as-built
structure.

Uninstall physical part Uninstalls and removes the selected lines from the as-built
structure completely and does not place them on the
clipboard.

Replace physical part Replaces the physical part into the current as-built structure.

Setup deviation Opens the Setup Deviation wizard. Use the Setup Deviation
wizard to search for a deviation document to associate to the
physical part.

Rebuild physical structure Creates a new build revision of the physical structure.

Navigation Pane Displays or hides the navigation pane.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 1-9

Button Purpose

Advanced Search Allows you to select a search form that includes multiple
search criteria relevant to the type of information or object
being sought.

The following buttons are located at the bottom left corner of the as-built structure navigation tree
pane.

Most recently used Shows a list of your most recently accessed structures. If you
(MRU) list select an entry from the list, As-Built Manager loads the
structure into the structure pane. You can configure the
number of entries shown in the MRU list by right-clicking the
button and moving the slider to the desired number.

Open by name Browses for and opens a specific structure by name.

Open structure context Browses for and opens a specific structure context by name.
by name

Most recently used Selects a revision rule to apply to the current product
(MRU) revision rules list structure from a list of the rules you have used recently. You
can configure the number of entries shown in the MRU by
right-clicking the button and moving the slider to the desired
number.

List substitute Adds or removes substitute components or set the preferred

components substitute.
This button is enabled if the selected line may have
substitutes; otherwise, it is disabled.

Manage global alternates Shows a list of the global alternates available for the selected
line. You can add alternates and select a preferred alternate.
The preferred global alternate is indicated by an asterisk.

Find in display Searches for matching lines (components) in the displayed

Shows if the item or revision represented by the line is

currently classified.

What are perspectives and views?

Within the rich client user interface, application functionality is provided in perspectives and views.

View The basic display component that displays related information in a UI window.
Perspective A collection of one or more views and their layout.

Some applications use a perspective with multiple views to arrange how functionality is presented.
Other applications use a perspective with a single view.

You can use the HiddenPerspectives preference to prevent the display of some Teamcenter
perspectives in the rich client.

If your site has online help installed, you can access application and view help from the rich client Help
menu or by pressing F1.

Basic concepts for using As-Built Manager

Before creating or modifying the product structure, read Getting Started with Product Structure, which
describes the basic concepts behind product structure and includes advanced information on how to use
and administer it.

To take full advantage of As-Built Manager, you should be familiar with the Teamcenter elements that
are used to define and present product structure, the basic process of creating product structure, and
how item revisions relate to how you manage default and multiple product views. Product structures are
not created or modified in As-Built Manager, but these structures are used as the definition for the as-
built structure.

The following are elements of As-Built Manager:

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 1-11

Element Description

As-built structure The representation of an individual physical asset. A single neutral

structure can result in many as-built structures, one for each physical
asset. The as-built structure contains additional asset-specific
information and records authorized differences from the product
definition.

Deviation document A document that authorizes the installation of a physical part which
is a deviation from the design structure.

Deviated physical part A physical part installed in a physical structure which is not the
preferred part or designated as a valid alternate or substitute to the
preferred part.

Deviation workflow The process flow, reviewer’s list, and business validations required to
route a deviation document for review and approval.

Lot Group of physical parts controlled by the same number. A lot number
is similar to a serial number. The difference between the two is that
the same lot number can identify multiple physical parts, but no
more than the total number of physical parts specified by the lot size.

Lot part Physical part or assembly identified by a lot number.

Neutral part An item defined in the neutral structure representing a part

definition. It can be a part object or any other item type configured as
a valid neutral item type in the Business Modeler IDE.

Neutral structure A hierarchy of neutral parts representing the asset independent

product definition structure, such as the manufacturing or design
structure.

Part logistics data Information added to the neutral part that will support the realization
of physical parts in as-built or as-maintained representations of the
product. For example, part logistics data determines whether the part
is traceable, serialized, or lot. Part logistics data is added to each
neutral part using the part logistics form.

Physical part The representation of a built or manufactured physical asset realized

from the neutral part. The physical part captures the asset
information such as its serial number, manufacturer, lot number. It
also inherits the part number from the neutral part from which it is
realized.

Physical structure A structure composed of physical parts.

Physical realization The relation between a physical part and the neutral part revision
that it was realized from.

Serial number generator A number generator that can be configured on a neutral part to
create serial numbers for every instance of a physical part. You can
set characteristics for the serial numbers, such as a prefix, suffix, the

1-12 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Element Description

number increment, and the maximum number of characters in the

serial number. During the instantiation of the physical structure from
the neutral structure, you can choose to automatically assign the
serial numbers to the newly created physical parts.

Serialized part Approved product structure that includes part information.

Usage Defines the position that the physical part occupies within the as-
built structure.

Search for As-Built Manager objects

You can search for the following As-Built Manager objects using advanced search:

• MRO Deviation Document

• MRO Item
• MRO Lot
• MRO Neutral Part
• MRO Physical Part
• MRO Serial Number Generator

1. Choose Advanced from the quick Search menu at the top of the navigation pane.

2. On the Search pane toolbar, click to select a search type.

3. Click More to display the system defined searches.

4. Under System Defined Searches, select the object you want to search for.

5. Click OK.

The dialog box that contains the object properties appears.

6. Type the values for the object properties that you want to search for.

7. Click the button to search.

Basic tasks for using As-Built Manager

The basic tasks for using As-Built Manager are:

1. Configuring As-Built Manager by setting global and business object constants, LOVs, and
preferences.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 1-13

2. Creating the neutral structure definition.

3. Generating the physical structure from the neutral structure.

4. Setting up and configuring the physical structure.

As-Built Manager process task flow

1-14 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
2. Installing and configuring As-Built
Manager
Installing As-Built Manager
As a system administrator, you must install and configure As-Built Manager using Teamcenter
Environment Manager (TEM). As the following figure shows, you must install As-Built Manager on the
server and on the rich clients that use the application.

Install As-Built Manager

As a system administrator, you must install and configure As-Built Manager using Teamcenter
Environment Manager (TEM). As the following figure shows, you must install As-Built Manager on the
server and on the rich clients that use the application.

For more information about planning your installation and installing Teamcenter, see Teamcenter Server
Installation on Linux or Teamcenter Server Installation on Windows.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 2-1

1. Start Teamcenter Environment Manager (TEM).

For more information about launching Teamcenter Environment Manager, see the Teamcenter
Server Installation on Linux or the Teamcenter Server Installation on Windows.

2. Select the appropriate options until you reach the Features panel.

Note:
The configuration installed is dependent on the options that you choose in the Solutions
panel of the TEM installation windows, such as Corporate Server, Rich Client 2–Tier, and
Business Modeler IDE. You can also add any of the options available in the Solutions panel
from the Features panel.

3. In the Features panel, under Extensions — Service Lifecycle Management, select the following
features.

Feature Description Prerequisite features

As-Built Installs the As-Built Management Teamcenter Foundation

Management functionality.

4. If you want to configure your system using the Business Modeler IDE:

a. Click Next. Select appropriate options until you reach the Business Modeler IDE Templates
panel.

b. In the Business Modeler IDE Templates panel, select the following templates.

Template Description

Teamcenter Foundation Installs the Teamcenter Foundation template.

As-Built Management Installs the As-Built templates.

For more information about installing the Business Modeler IDE, see Teamcenter Server
Installation on Linux or Teamcenter Server Installation on Windows.

5. Click Next.

Select appropriate options until you complete the installation.

For more information, see Teamcenter Server Installation on Linux or Teamcenter Server
Installation on Windows.

2-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Configuring As-Built Manager

The Teamcenter administrator configures the As-Built Manager according to company needs and
organization requirements as shown in the following figure.

You can configure:

• As-Built Manager preferences.

• Global and property constants that control part logistics information and define part usage properties.

• Business object constants that identify neutral item types.

• Naming rules for occurrences.

• Lists of values (LOVs) that define deviation authority documents and status lists.

• As-Built Manager workflows.

You use the Business Modeler IDE to configure global and property constants, business object constants,
naming rules, and LOVs. An administrator creates and configures a custom template based on the As-
Built Manager or other templates provided with the As-Built Manager application. You must deploy the
custom template after making the changes.

Setting as-built preferences

As an administrator or Teamcenter user, you can set the SLM and As-Built Manager preferences
according to your needs. Preferences are special environment variables stored in the Teamcenter
database and are read during Teamcenter application usage.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 2-3

Setting as-built global and property constants

Global constants provide consistent definitions that can be used throughout the system. These
constants have only one value, either the default value or the value you set. You use the Business
Modeler IDE to configure the global constants in the custom template that you define. You must deploy
the custom template after making the changes.

You can configure the following as-built global constants:

• AutoCreatePartLogisticsForm
Set this value to automatically create part logistics forms and relate them to a neutral item.

• PartLogisticsFormNamePrefix
Set this value to automatically create a prefix in part logistics form names.

• UsageAttributeName
Set this value to the property of PSOccurrence that is to contain the value for the generated physical
part's usage.

• ReuseAuthorizedDeviation
Set this value to reuse an authorized deviation information when duplicating physical structures.

You can configure the following as-built property constant:

• InitialValue
Set this value to set the defaults for the properties of the part logistics form.

Set up automated creation of part logistics forms

As an administrator, you can set the AutoCreatePartLogisticsForm global constant to true to configure
part logistics forms to be automatically created and related to a neutral item during creation. The part
logistics form is related to the neutral item with a References relation.

Example:
Because a part object by default is classified as a neutral item, a part logistics form is automatically
created and related to a newly created part.

Global constant Default value

AutoCreatePartLogisticsForm True

2-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Define default values for part logistics form

As an administrator, you can set the defaults for values contained in the part logistics form by setting the
property constant InitialValue for any of the properties of the PartLogisticsForm business object.

Example:
You may want to set the InitialValue for the IsSerialized property to True, to require all physical
parts to have a serial number on one system, but not on another system.

Define part logistics form name prefix

As an administrator, you can set the PartLogisticsFormNamePrefix global constant to a prefix that is
used for part logistics form names.

Example:
If you want part logistics form names to contain the prefix PL, set PartLogisticsFormNamePrefix
to PL.

Global constant Default value

PartLogisticsFormNamePrefix NULL

Define usage property

As an administrator, you can set the UsageAttributeName global constant to the property of
PSOccurrence that populates the value of the physical part's usage when the as-built physical structure
is generated.

Example:
You may want to set the UsageAttributeName global constant to ref_designator. When you set
the value of ref_designator to RD1234, the value of usage is populated with that same value
RD1234 for the generated physical part.

The allowed properties are:

• occurrence_name

• ref_designator

• seq_no

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 2-5

Note:
The seq_no property corresponds to the value for the Find No. property in the Service Manager
interface.

Global constant Default value

UsageAttributeName occurrence_name

Reuse an authorized deviation

As an administrator, you can set the ReuseAuthorizedDeviation global constant to True to reuse an
authorized deviation when duplicating a physical structure . If the value is set to True, the deviated and
extra to design parts from the original structure are copied to the duplicated structure.

Global constant Default value

ReuseAuthorizedDeviation True

Setting as-built business object constants

Business object constants provide default values to business objects that define the behavior for a
specific business object. Because these constants are attached to business objects, they are inherited,
just like properties. These constants have only one value, either the default value or the value you set.
Use the Business Modeler IDE to configure the business object constants in the custom template that
you define. You must deploy the custom template after making the changes.

You can configure the following as-built business object constants:

• IsSLMNeutralType
Set this value to automatically configure which items are defined as neutral items.

• PhysicalPartTypeForCreate
Set this value to the physical part type created from a neutral item.

Identify neutral item types

As an administrator, you can set the IsSLMNeutralType business object constant to true to configure
which items are defined as neutral items. Physical parts are only generated from neutral items.

2-6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Example:
Because IsSLMNeutralType is false for the document business object, physical parts cannot be
generated from documents.

Business Object Constant Default value

IsSLMNeutralType false for business object item

IsSLMNeutralType true for business object part

Define physical part types

As an administrator, you can set the PhysicalPartTypeForCreate business object constant to represent
the physical part type that is generated from a neutral item.

Example:
You may want to create a new neutral item called Aircraft to represent an aircraft assembly and a
new physical part subtype called PhysicalAircraft to represent a physical aircraft assembly. If you
set the PhysicalPartTypeForCreate business object constant to PhysicalAircraft for the neutral
item Aircraft, the physical part is set to the type PhysicalAircraft when the as-built structure is
generated.

Business object constant Default value

PhysicalPartTypeForCreate Physical Part for business object item

Setting up as-built naming rules

As an administrator, you can create naming rules that define the data entry format for a business object
property. A naming rule consists of rule patterns and a counter. Before creating a naming rule, you
should be familiar with the pattern and counter formats. After you create a naming rule, you must
attach it to the business object property. You use the Business Modeler IDE to create the naming rules in
a custom template that you define. You must deploy the custom template after making the changes.

You can configure the following as-built naming rules:

• Automatically name occurrences

You can create a naming rule and attach it to the business object property occurrence_name for the
PSOccurrence business object. This rule automatically names occurrences when a Teamcenter user
chooses the Name Occurrence command. The naming rule can also be based on conditions.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 2-7

Setting as-built lists of values (LOVs)

As an administrator, you can set LOVs located in LOV folder in the Extensions view. LOVs are commonly
accessed by Teamcenter users from a menu at the end of a data entry box. After you create a list of
values, you must attach it to a property on a business object.You use the Business Modeler IDE to set the
LOVs in a custom template that you define. You must deploy the custom template after making the
changes.

You can configure the following as-built global LOVs:

• MRO Valid Deviation Status List

Set this list of values to configure the approved status list for deviations.

• MRO Deviation Authority List

Set this list of values to configure items used to authorize a deviation.

Define valid deviation status list

As an administrator, you can set the MRO Valid Deviation Status List LOV to the list of authorized status
values used for deviations. The deviated authority item must be at the approved status before a deviated
physical part can be installed. You can also configure LOVs.

Example:
You may want to include an additional status value such as Complete to validate a deviation.

LOV Default value Description

MRO Valid Deviation TCM Released Released status

Status List

Define deviation authority list

As an administrator, you can set the MRO Deviation Authority List LOV to the list of item classes used
to authorize a deviation. You can also configure LOVs

Example:
You may want to use a manufacturing document in addition to a deviation document to authorize
deviations.

2-8 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

LOV Default values Description

MRO Deviation Authority DeviationDoc Deviation document

List

Cm0DevRqst Deviation request

ADc0DevRqst ADS deviation request

Service Event Service event

Configuring as-built workflows

As an administrator, you can configure the following workflows to support your as-built installation:

• Deviation workflow
The TCM Release Process workflow is provided with the Teamcenter Foundation feature. You can
configure this workflow or create your own to set up the process flow, reviewers, and business
validations required to route a deviation document for review and approval.

• Release as-built structure workflow

The Release AsBuilt Structure workflow is provided with the As-Built Manager feature. You can
configure this workflow or create your own to set up the process flow, reviewers, and business
validations required to release an as-built structure.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 2-9

2-10 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
3. Creating neutral structures
What is the neutral structure?
The neutral structure is the item or part structure representing the asset-independent product definition
structure. It provides the basis for the physical structure that is generated from the neutral structure. The
neutral structure can be created with Structure Manager, Multi-Structure Manager, or imported from
your CAD system.

You can populate the neutral structure in a way that is useful for servicing your physical assets. After
populating the neutral structure, you can attach other items or datasets to these neutral structure
elements. For example, you can attach documents such as design documents, specifications, and
service bulletins.

As shown in the figure, the neutral structure tasks include:

• Creating the product structure with valid global alternate and substitute parts by a user such as a
design engineer.

• Creating and managing the part logistic data by a user such as a logistics engineer. Part logistics data
includes information such as serial and lot definitions and part usages.

• Creating the characteristic definitions by a user such as a logistics engineer.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3-1

Creating product structures

A user such as a design engineer creates the neutral product structure as well as any substitute or global
alternate parts. The following figure shows the product structure tasks.

A neutral structure is the product structure that you create with Structure Manager, Multi-Structure
Manager, or import from your CAD system. The product structure, is sometimes referred as the bill of
materials (BOM).

The following figure shows an example of a neutral structure for a bearing housing assembly.

Teamcenter allows you to view an indented listing of the assemblies and piece parts that comprise the
product structure; the indenting allows you to interpret the relationship between the assemblies and
piece parts. The physical structure is generated from the neutral structure.

You can specify global alternates of a component, one of which is designated as the preferred global
alternate. Global alternates may be used in any product and are not defined in the context of a particular
assembly. Global alternates do not require an authorized deviation when installed as a alternate physical
part in the as-maintained physical structure.

3-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

You can also specify substitute components, which are components that can be used interchangeably
within an occurrence, typically for manufacturing purposes. The preferred substitute is displayed in the
structure. In contrast with global alternates, substitutes may only be used in the context of a particular
assembly. Substitute parts do not require an authorized deviation when installed as a substitute physical
part in the as-maintained physical structure.

Creating neutral structures

You must create the neutral structure before you can generate the as-built physical structure. After you
create the structure, you modify it as necessary to reflect any changes to the product design.

Note:
Do not add physical parts to neutral structures in Structure Manager, Multi-Structure Manager, or
other BVR applications. Active Workspace cannot handle these types of structures and will produce
an error when trying to view them.

The following bill of material is an example of a neutral structure.

BH001/A;1–BH Assembly (view)

BH012/A;1–Blade Front
BH013/A;1–Blade Rear
BH014/A;1–Shaft
BH015/A;1–Heat Shield
BH016/A;1–B Housing
BH017 /A;1–Cover Ring
BH018 /A;1–Piston
BH019/A;1–Journal Bearing X 2
BH020A;1–Retaining Ring

Defining global alternates

A global alternate part is interchangeable with another part in all circumstances, regardless of where the
other part is used in the product structure. A global alternate applies to any revision of the part and is
independent of any views.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3-3

Note:
A global alternate part does not require an authorized deviation when installed as an alternate
physical part in the as-maintained physical structure.

Defining substitute parts

A substitute part is a part that is interchangeable with a particular component in an assembly.

Substitutes are often defined for manufacturing purposes, allowing use of the substitute if the preferred
part is unavailable, for example, due to a stock shortage.

Note:
A substitute part does not require an authorized deviation when installed as a substitute physical
part in the as-maintained physical structure.

3-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Creating and managing part logistics data

Part logistics data is the logistical information defined for a neutral structure that is used by the
generated physical structure. Part logistics data includes information such as serial and lot definitions
and part usages. A user such as a logistics engineer populates the part logistic data before the as-
maintained physical structure is generated. The following figure shows the part logistic data tasks.

You can create and manage part logistics data by:

• Creating and managing part logistics forms attached to the neutral part.

• Overriding part logistics data in the context of a structure.

• Creating lot definitions for the neutral part used for the generated physical part.

• Creating serial number definitions for the neutral part used for the generated physical part.

• Defining occurrence information for the neutral part that is the part usage for the generated physical
part.

Managing part logistics forms

What is a part logistics form?

The part logistics form contains some of the logistical information required for the neutral part. It must
be attached to the neutral part item using a References relation to generate a physical part.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3-5

Note:
The part logistics form is automatically created and attached to a valid neutral item during neutral
item creation if the AutoCreatePartLogisticsForm global constant is true. If this constant is false,
you must manually create and attach part logistics forms to the neutral parts that generate
physical parts.

Property Definition Default

Traceable Defines if a physical part will be generated from the neutral true
part.

Serialized Defines if a physical part requires a serial number. false

Lot Defines if a physical part requires a lot number. false

Rotable Defines if a physical part can be easily repaired. false

Consumable Defines if a physical part can be used and discarded. false

Preserve Defines if one physical part with the quantity defined can false
Quantity represent a multi quantity neutral part.

Life Limited Defines if a physical part has a finite life. false

Manually create a part logistics form

3-6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

1. From the navigation pane, click My Teamcenter.

2. Locate the neutral part you want to create a part logistics form for.

3. Select the neutral part and choose File → New → Form.

4. Select Part Logistics Form from the list of forms.

5. Enter the following information for the new form.

Field name Definition Valid values

Name Name for the part logistics form. Alphanumeric (1–128

characters)

Description Description of the new form Alphanumeric (1–240

(optional). characters)

6. Click OK or Apply to create the new form. Click Cancel to exit without creating a new form.

The part logistics form is related to the neutral part with a References relation.

Note:
If you created the part logistics form without selecting the neutral part, you must relate the form
to the neutral part.

Display part logistics form properties

To view the part logistics form properties using the Properties dialog box:

1. From the tree pane or Details table, select the part logistics form that you want to display.

2. Double-click the part logistics form associated to the neutral part.

The properties are displayed.

To view the part logistics form properties using the Viewer pane:

1. Select the part logistics form.

2. Click the Viewer tab.

The system displays the properties of the part logistics form in the Viewer pane.

Edit part logistics form properties

1. From the tree pane or Details table, select the part logistics form that you want to display.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3-7

2. Double-click the form to display the properties.

3. Click Checkout and Edit.

4. Modify the form property values, as required.

5. Click Save and Check-In or Save.

Edit part logistics data

You edit part logistics data in As-Built Manager by selecting the BOM line for the neutral part and
changing the cell data containing the part logistic value. You can also change part logistics data by
editing the part logistic form properties.

The following part logistic values can be changed using As-Built Manager:

• Serialized

• Traceable

• Lot

• Consumable

• Rotable

• Preserve Quantity

1. Open the neutral structure in the As-Built Manager view by one of the following methods:

• From the navigation pane, click As-Built Manager, then from the As-Built Manager view, click
Open by Name .

• If you are viewing the structure in the Structure Manager view, right-click the structure parent
and choose Send to → As-Built Manager.

2. From the As-Built Manager view, select the BOM line containing the neutral part.

a. Double-click the cell containing the part logistics value.

b. Double-click the cell containing the part logistics value and type the new value.

3-8 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Override part logistics data in context

You can override part logistics data in the context of the top-level or lower level neutral structures. For
example, you may not want a physical part to be generated in the context of a specific neutral structure.
To do this, you set the neutral structure in context and override the Traceable value from Y, which is
true, to N, which is false for that neutral part in the structure.

The following part logistic values can be changed in the context of a neutral structure:

• Serialized

• Traceable

• Consumable

• Rotable

• Preserve Quantity

• Life Limited

Note:
The part logistic value Lot cannot be changed in the context of a neutral structure.

1. Open the neutral structure in the As-Built Manager view.

2. From the As-Built Manager view, select the BOM line containing the top-level or lower level
parent.

3. Right-click and choose Toggle in-Context Mode to set the structure in context.

4. From the As-Built Manager view, select the BOM line containing the neutral part.

• To override the Traceable value, double-click the Traceable cell. Type the new value.

• To override the Serialized value, double-click the Serialized cell. Type the new value.

Note:
A serial number generator may never be assigned to a non serial part even though it may
be marked serialized in context.

• To override the Consumable value, double-click the Consumable cell. Type the new value.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3-9

• To override the Rotable value, double-click the Rotable cell. Type the new value.

• To override the Preserve Quantity value, double-click the Preserve Quantity cell. Type the new
value.

• To override the Life Limited value, double-click the Life Limited cell. Type the new value.

Defining parts for tracking

To track physical parts, you must set the Traceable value to true to generate physical parts from neutral
parts. The value can be changed in the part logistics form.

Note:
Physical parts are not generated for traceable neutral parts that are children of nontraceable parts.

Create a lot definition

A lot contains a group of physical parts controlled by the same lot number. You can define the maximum
number of parts that a lot can contain. Based on this information, you can assign lot numbers to the
physical parts that make up the as-built physical structure. The lot usage value increments for every
physical part assigned to that lot. When the lot usage is more than the maximum number of parts
available, the lot cannot be used further. You can also define an expiration date for the lot. For example,
you can store parts from a particular manufacturer in a lot that is identified by a lot number. You can
then use this lot number to track the parts that belong to that particular manufacturer.

Note:
Lots can be assigned only if the part logistics lot property is true for the neutral part.

1. Open the neutral structure in the As-Built Manager view.

2. From the As-Built Manager view, select the BOM line containing the neutral part.

3. Right-click and choose New → Lot.

The New Lot dialog box appears.

4. Enter the following information for the new lot.

3-10 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Field name Definition Valid values

Lot Number Unique lot ID number Alphanumeric (1–32

characters)

Manufacturer's ID Lot manufacturer ID Alphanumeric (1–128

characters)

Lot Size Number of items in the lot Integer

Note:
If you set the lot size value to
0 (zero) or leave it blank, the
lot size is set to infinite.

Expiration Date Lot expiration date Click the Set Date button
and select a date from the
calendar.

5. Click OK to create the lot under the New Stuff folder. Alternatively, click Cancel to exit.

Newstuff
BH020–01/RRLot01 Lot

Create a serial number generator

Serialized physical parts have a unique serial number for a given Manufacturer's ID. For example, you
may have two engines with the same serial number but are manufactured by different companies.

You can type the serial number for the physical part or you can optionally create a serial number
generator. The serial number generator is defined for the neutral parts and automatically assigns the
serial numbers to the newly created physical parts in the as-maintained physical structure.

Note:
Serial numbers can be assigned only if the part logistics serialized property is true for the neutral
part.

1. Open the neutral structure in the As-Built Manager view.

2. From the As-Built Manager view, select the BOM line containing the neutral part.

3. Right-click and choose New → Serial Number Generator.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3-11

The New Serial Number Generator dialog box appears.

4. Enter the following information.

Field name Definition Valid values

Series Prefix Prefix for the generated serial Alphanumeric (1–32

number. characters)

Series Suffix Suffix for the generated serial Alphanumeric (1–32

number. characters)

Series Current Starting numeric value for the Integer

generated serial number.

Series Maximum Maximum numeric value for the Integer

generated serial number.

Increment Increment between the generated Integer

serial numbers.

Series Characters Number of characters for the Integer

generated serial number. Numeric
values are preceded by zeros to
meet the character limit.

5. Click OK to create the serial number generator under the New Stuff folder. Alternatively, click
Cancel to exit.

Newstuff
BH014–nn-Shaft Serial number generator

Set or unset generic serial number generator

Set a generic serial number generator

1. Search for an existing serial number generator.

2. Right-click the desired serial number generator and select Set As Generic Serial Number
Generator.

3-12 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

If a generic serial number generator is already set, it is now replaced.

Unset a generic serial number generator

1. Search for an existing serial number generator.

2. Right-click any serial number generator and select Unset Generic Serial Number Generator.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3-13

Note:
Selecting a generic serial number generator that is already set makes the Unset As Generic
Serial Number Generator option available.

Define part usage

The usage of a physical part in an as-maintained structure defines the position that the physical part
occupies within the structure. You define the usage of a physical part by:

• Entering a value for the neutral structure occurrence property used to define the physical part usage.
This can be defined by the UsageAttributeName global constant. The default property is set to
occurrence_name.

• Defining a naming rule to auto name the occurrences. The occurrence_name property can only be
used if a naming rule for occurrences has been created.

1. Open the neutral structure in the As-Built Manager view.

2. From the As-Built Manager view, select the BOM line containing the neutral part.

3. • If you use an occurrence naming rule:

Right-click and choose Name Occurrence.

3-14 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

• If you do not use an occurrence naming rule:

Double-click the Occurrence Name cell and type the usage value.

Note:
The occurrence_name property is the default property used to set the usage for the
physical part. The ref_designator or seq_no properties can be used only if the
UsageAttributeName global constant is set to one of those values.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 3-15

3-16 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
4. Generating as-built physical structures
Generating as-built physical structures
A user such as a production planner generates the as-built physical structures.

A physical structure refers to an asset's product structure information. Each asset that your organization
manufactures or owns can be represented by one physical structure. An as-built physical structure
evolves as the asset changes over time. This physical structure contains other traceable physical parts
that represent the sub-assemblies and components that make up the asset. Each physical part within the
structure links back to the neutral part that provides its engineering and logistics definition. Part logistics
information includes if a part is traceable and should be included in the physical structure as well as if
the part should have a recorded serial number, lot number, or both.

The following figure shows an example of a physical structure for a bearing housing assembly. In this
example, all the physical parts are serialized.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 4-1

The as-built physical structures are precise structures comprising physical part revisions. The physical
parts are related back to the neutral parts with a PhysicalRealization relation.

The following tasks are required steps before generating an as-built physical structure:

• Create the neutral structure.

• Populate the part logistics information assigned to the neutral parts.

A user such as a production planner can:

• Generate an as-built physical structure top down from the top-level neutral structure.

• Generate an as-built physical structure bottom up by installing physical parts at various levels in the
structure.

• Duplicate an as-built physical structure.

4-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

• Generate an as-maintained physical structure from an as-built physical structure if you have
purchased and have a license for both the As-Built Manager and the Service Manager (as-maintained)
applications.

• Generate an as-built physical structure from an as-maintained physical structure if you have
purchased and have a license for both the As-Built Manager and the Service Manager (as-maintained)
applications.

Generate a partial or entire as-built structure (top down)

1. Open the neutral structure in the As-Built Manager view by one of the following methods:

• From the navigation pane, click As-Built Manager. Click Open By Name to open the
structure.

• If you are viewing the structure in the Structure Manager view, right-click the structure parent
and choose Send to → As-Built Manager.

2. Select the top-level part from the neutral structure.

3. Right-click the top-level part and select Generate As-Built Structure or click the Generate As-Built
Structure button on the main toolbar at the top of the As-Built Manager pane.
Teamcenter displays the Generate As-Built Structure dialog box

4. Enter the following information:

Field name Definition Valid values

Serial Number Serial number for the generated Alphanumeric (1–128

physical part. characters)
This field is optional or unavailable
in the following situations:

• Optional if a serial number

generator is defined for the
neutral part.

• Unavailable if the Serialized

property is set to false in the
part logistics form that is
attached to the neutral part.

Lot Number Lot number for the generated Alphanumeric (1–128

physical part. characters)

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 4-3

Field name Definition Valid values

You must first create the lot for the

neutral part.
The Lot list is unavailable if the Lot
property is set to false in the part
logistics form that is attached to
the neutral part.

Manufacturer's Manufacturer of the physical part. Alphanumeric (1–128

ID characters)
The Manufacturer's ID box is
automatically populated if you
entered a lot number.

Structure The name of the structure context Alphanumeric (1–128

Context Name used to store the neutral product characters)
configuration information.
The structure context name is
automatically named with the part
number of the neutral part. If the
physical part is serialized and you
are not using a serial number
generator, the structure context
name is automatically named
using part number/serial number.
You can use these values or type in
a new value.

Manufacturing Manufacturing date for physical Click the Set Date button
Date structure. The manufacturing date and select a date from the
must be before the installation calendar.
date.

Installation Installation time and date for Click the Set Date button
Time physical structure. The installation and select a date from the
time and date must be after the calendar.
manufacturing date.

Number of Number of levels to be generated Integer or All

Levels for the physical structure. If you
want to generate physical parts for
the entire structure, type All in the
Number of Levels box.

Quantity Number of physical parts to Number

generate for the top-level part.
If it is a lot part, the quantity, if a
whole number, is deducted from
the lot. If the quantity is not a

4-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Field name Definition Valid values

whole number, it is not deducted

from the lot.
To set the quantity, the Preserve
Quantity property for the neutral
part must be set to true.

5. If you define the serial number generator in the neutral part, click True to enable it. The serial
number generator automatically creates serial numbers for the entire as-built physical structure. If
you have defined a generic serial number generator, then the serial number will be created for the
serialized parts for which serial number generator is not defined, and you will be informed that the
generic serial number generator is being used.

6. Click OK to generate the as-built physical structure or click Cancel to exit.

The physical structure is generated from the neutral structure.

BH001–nn/InTestnn–A
BH012-nn/A
BH013-nn/A
BH014–nn/SHnn–001–A
BH015-nn/A
BH016-nn/A
BH017-nn/A
BH018-nn/A
BH019–nn/JBnn–001–A
BH019–nn/JBnn–002–A
BH020–nn/A

Build an as-built physical structure (bottom up)

You can build an as-built physical structure by installing existing physical parts in the structure.

View the neutral structure details

You can view the neutral structure and the structure context information from which the physical
structure is realized.

1. From the navigation pane, click As-Built Manager.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 4-5

2. Click Open by Name to open the physical structure or part.

3. Select the physical structure parent part.

4. Right-click the physical part and choose Open with → Details.

The Details pane appears at the bottom and displays the neutral structure and context information
used to generate the physical structure.

5. In the Details pane, select the neutral structure.

6. Right-click and choose View Properties.

The properties of the neutral structure from which the physical structure is realized, are displayed.

7. Click Cancel to close the properties window.

8. In the Details pane, select the structure context.

9. Right-click and choose Send to → Multi-Structure Manager.

The neutral structure is displayed in Multi-Structure Manager. Multi-Structure Manager displays the
configured variants and options that were used when generating the physical structure.

Duplicate an as-built structure

You can duplicate an as-built physical structure to create a copy of an existing physical structure. The
copied physical structure contains the installed alternate, substitute, deviated, and extra to design parts
from the original structure.

When you duplicate an as-built physical structure, the following occurs:

• The duplicate physical structure uses the same structure context as the original structure.

• The duplicate physical structure is validated for a unique serial number and manufacturing ID, if those
values are entered.

4-6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

• The child parts of the duplicate physical structure inherit the manufacturing ID from the parent.

• The Part Used column for all the child parts of the duplicate physical structure is set to Missing
except in the following cases where the Part Used is set to Preferred:

• Parts that do not require a serial or lot number.

• Serialized parts that have a serial number generator.

• The deviated parts in the original structure are:

• Copied to the duplicate physical structure, if the ReUseAuthorizedDeviation global constant is set
to True, to reuse the same deviation.

• Ignored and the preferred parts are used in the duplicate physical structure, if the
ReUseAuthorizedDeviation global constant is set to False.

1. From the navigation pane, click As-Built Manager.

2. Click Open by Name to open the as-built physical structure or physical part that you want to
copy.

3. Select the top-level part from the physical structure if you want to duplicate the entire structure or
select the physical part if you want to copy only the physical part.

4. Choose File → Duplicate As-Built Structure or right-click the physical part and choose Duplicate
As-Built Structure.

5. In the Duplicate As-Built Structure dialog box, enter the following information.

Field name Definition Valid values

Serial Number Serial number for the copied physical Alphanumeric (1–128 characters)
structure or part.
This field is unavailable if the original
physical structure or part did not
require a serial number.

Lot Lot number for the copied physical Alphanumeric (1–128 characters)
structure or part.
This field is unavailable if the original
physical structure or part did not
require a lot number.

Manufacturer's ID Manufacturer of the physical part. Alphanumeric (1–128 characters)

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 4-7

Field name Definition Valid values

The Manufacturer's ID box is

automatically populated if you
entered a lot number.

Manufacturing Manufacturing date for physical Click the Set Date button and
Date structure. The manufacturing date select a date from the calendar.
must be before the installation date.

Installation Time Installation date for physical structure. Click the Set Date button and
The installation date must be after the select a date from the calendar.
manufacturing date.

Number of Levels Number of levels to be generated for Integer or All

the physical structure. If you want to
generate physical parts for the entire
structure, type All in the Number of
Levels box.

6. If you have defined a serial number generator for the neutral part, select the Use Serial Number
Generators check box to enable it. The serial number generator automatically creates serial
numbers for all the parts within the as-built physical structure that have defined serial number
generators. If you have defined a generic serial number generator, then the serial number will be
created for the serialized parts for which the serial number generator is not defined, and you will
be informed that generic serial number generator is being used.

7. Click OK to duplicate the physical structure or part.

Generate an as-maintained structure from an as-built structure

If you have purchased and have a license for the As-Maintained Management application, you can
generate an as-maintained structure from an as-built structure. The as-built structure must be at a
Released state.

1. From the navigation pane, click As-Built Manager.

2. Click Open by Name to open the released as-built physical structure.

3. Select the top-level part from the as-built physical structure.

4. Right-click and choose Generate As-Maintained Structure.

Teamcenter displays the Generate As-Maintained Structure dialog box.

5. Click Set Date and select a date from the calendar when the as-maintained structure was
created.

4-8 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

6. Choose the location where the physical parts are stored.

7. Choose the disposition of the physical part.

Note:
If the Disposition_Propagate_To_Child preference is set to true, the disposition is also
applied to the children parts of the structure.

8. Type the number of levels you want to generate for the physical structure in the Number of Levels
box. If you want to generate physical parts for the entire structure, type All.

9. Click OK to generate the as-maintained physical structure or click Cancel to exit.

Generate an as-built structure from an as-maintained structure

If you have purchased and have a license for the As-Maintained Management application, you can
generate an as-built structure from an as-maintained structure. The as-maintained structure must be at
a Released state.

1. From the navigation pane, click Service Manager.

2. Click Open by Name to open the released as-maintained physical structure.

3. Choose Window → Show View → Service Editor to open the Service Editor view.

4. From the Service Editor view, select the top-level part from the as-maintained physical structure.

5. Right-click and choose Generate As-Built Structure.

Teamcenter displays the Generate As-Built Structure dialog box.

6. Click Set Date to set the rebuild date.

7. Type the number of levels you want to generate for the physical structure in the Number of Levels
box. If you want to generate physical parts for the entire structure, type All.

8. Click OK to generate the as-built physical structure or click Cancel to exit.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 4-9

4-10 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
5. Setting up as-built physical structures
Setting up as-built physical structures
A user such as production planner manages the as-built physical structure according to organization
needs and requirements as shown in the following figure.

You can set up and manipulate physical structures by:

• Updating physical part properties.

• Resolving missing parts by adding serial number, lot, or manufacturing information to the physical
part.

• Assigning lot numbers to physical parts.

• Installing and uninstalling physical parts from an as-built structure.

• Renaming as-built physical parts.

• Replacing physical parts in an as-built structure.

• Rebasing physical parts in an as-built structure.

• Deleting physical parts.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-1

• Implementing deviations.

• Releasing as-built physical structures.

• Rebuilding as-built physical structures.

• Updating as-built physical structures using Excel Live.

• Viewing untraced structures.

Resolving missing parts

After you generate the as-built structure, a Missing status for the Parts Used column occurs if there is
missing information for the child physical parts. Missing information may include a missing serial
number, lot number or manufacturer id for the physical part. When you enter the missing information,
the Parts Used column is automatically changed to Preferred.

A physical part has the Parts Used column set to Missing for the following conditions:

• The lot number is missing for a lot physical part.

• The serial number is missing for a serialized physical part.

• The manufacturer ID is missing for a nonserialized, nonlot part.

• The lot number or serial number is missing for a serialized lot part.

Editable property Property description Editable in As-Built Editable in My

Manager Teamcenter

Manufacturing date The date the physical Yes Yes

part was manufactured.

Installation date The date the physical Yes Yes

part was installed.

Physical Part UID Unique UID for the Yes No

physical part. Once the
UID is assigned, it
cannot be edited again.

From My Teamcenter:

1. Search for the physical part.

2. Right-click the physical part in the results list and choose Edit Properties.

3. From the Checkout dialog box, click Yes to check out the physical part.

4. From the Edit Properties dialog box, modify the properties.

5. To save and check in the modified properties, click Save and Check-In.

From As-Built Manager:

1. From the navigation pane, click As-Built Manager.

2. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

3. From the As-Built Manager view, click Open By Name to open the physical structure or part.

4. Select the BOM line containing the physical part.

5. Double-click the property cell and type the new value.

Assign a serial number

1. From the navigation pane, click As-Built Manager.

2. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

3. From the As-Built Manager view, click Open by Name to open the physical structure or part.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-3

4. Select the BOM line containing the serialized physical part with the missing serial number.

5. To add a serial number, double-click the Serial Number cell and type the serial number.
The serial property for the serialized physical part is assigned and the Part Used column is set to
Preferred.

Assign a manufacturer ID
1. From the navigation pane, click As-Built Manager.

2. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

3. From the As-Built Manager view, click Open by Name to open the physical structure or part.
Select the physical part.

4. To add a manufacturer ID, double-click the Manufacturer's ID cell and type the manufacturer ID.
The manufacturer ID property is set for the physical part and the Part Used column is set to
Preferred.

Assign a lot number

In As-Built Manager, you can assign a lot number to a physical part or change a physical part lot number.

When you assign a lot number to a physical part, the physical part's manufacturer changes to the lot
manufacturer.

After you assign a lot number to a physical part, the lot usage property of the specified lot is also
updated. Lot usage is a property that tracks the number of physical parts associated to a specified lot.

Note:
You must create a lot definition for the neutral part before you can assign a lot number to a
physical part.

1. From the navigation pane, click As-Built Manager

2. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

3. From the As-Built Manager view, click Open by Name to open the physical structure or part.

4. Select the BOM line containing the lot physical part with the missing lot number. Right-click and
choose Assign Lot.

5. In the Assign Lot dialog box, select a lot number from the Lot list.

5-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

6. In the Quantity box, type the number of physical parts to assign to the lot.

If the part is a Preserve Quantity part, the quantity is checked against the expected quantity (the
quantity from the neutral structure and the nonmissing parts from the occurrence).

• If the quantity is the same as the expected quantity, Teamcenter assigns the lot and marks the
physical part as Preferred.
If the quantity is a whole number, it is deducted from the lot. If the quantity is not a whole
number, it is not deducted from the lot.

• If the quantity is less than expected, a missing part is generated with the remaining quantity.

• If the quantity is greater than expected, Teamcenter displays an error.

• If the identified (nonmissing) parts are installed under the selected missing part and the quantity
is not the expected quantity, Teamcenter displays an error.

• If you are assigning a new lot to the selected physical part that already has a lot assigned, the
quantity is not changed, only the lot information.

7. Click OK.

The lot property for the physical part contains the assigned lot and the Part Used column is set to
Preferred.

Rename a physical part

You can rename an existing physical part to change the following properties:

• Part number

• Serial number

Note:
You cannot rename a physical part that is released.

When you rename a physical part, the following occurs:

• The new serial number is checked for uniqueness.

• If a physical part is renamed using a different part number, the system does not check the existence
of a neutral item with the new part number.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-5

• The physical realization relation remains intact between the original physical part (before renaming)
and the original neutral part.

Note:
If you want to relate the physical part or structure to a different neutral configuration, you need
to rebase the physical part.

1. From the navigation pane, click As-Built Manager.

2. Click Open by Name to open the physical part you want to rename.

3. Choose Tools → Rename Physical Part.

The Rename Physical Part dialog box appears.

4. Enter the following information.

Field name Definition Valid values

New Part New part number for the renamed Alphanumeric (1–128
Number physical part. characters)

New Serial New serial number for the Alphanumeric (1–128

Number renamed physical part. characters)
This field is unavailable if the part
did not require a serial number.

5. Click OK to rename the physical part.

Install a physical part

You can install an existing physical part in a physical location at a specified usage into an as-built
physical structure. If the installed physical part is not a valid preferred, alternate, or substitute, you must
set up a deviation to install the deviated part.

Note:
You cannot install a physical part under a released physical part.

1. From the navigation pane, click As-Built Manager.

2. From the As-Built Manager view, click Open By Name to open the physical structure where
you want to install the physical part.

5-6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

3. Choose one of the following methods to identify the physical part you want to install:

• Copy the physical part you want to install.

a. Click Open By Name to open the physical part you want to install.

b. Right-click the physical part and choose Copy.

c. Select the physical structure where you want to install the physical part.

d. Right-click the parent and choose Install Physical Part or click the Install Physical Part
button on the main toolbar at the top of the As-Built Manager pane.

The Install Physical Part dialog box appears.

The To Be Installed Physical Part field is set to the copied physical part.

e. Select the usage name to set the usage for the installed physical part. If the physical part is
an addition to the physical structure, select Extra to Design as the usage.

• Search for the physical part you want to install.

a. Select the physical structure where you want to install the physical part.

b. Right-click the parent and choose Install Physical Part or click the Install Physical Part
button on the main toolbar at the top of the As-Built Manager pane.

The Install Physical Part dialog box appears.

c. Select the usage name to set the usage for the installed physical part. If the physical part is
an addition to the physical structure, select Extra to Design as the usage.

d. Perform the following steps to search for the physical part to be installed:

A. Click and select Add.

Manufactured After Manufacturing date Click the Set Date

used to filter physical
button and select a date
parts with
from the calendar.
manufacturing dates
greater than the date
entered.

Manufactured Before Manufacturing date Click the Set Date

used to filter physical
button and select a date
parts with
from the calendar.
manufacturing dates
before the date entered.

C. Click Find.

The results display the valid preferred, alternate, substitute, and deviated physical
parts that can be installed.

5-8 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

D. Select the physical part from the results and click OK.

The Install Physical Part dialog reappears with the To be Installed Physical Part field
set to the selected physical part.

4. Click the Set Date button to set the installation date when the installation occurred.

5. If the Usage Name is set to Extra to Design in the Extra to Design Usage Name box, type the
usage name for the installed physical part.

6. Click OK to install the physical part.

If the installed Preferred part is a Preserve Quantity part, the quantity is checked against the
neutral structure.

• If the quantities match, the physical part is installed in the structure.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-9

• If the quantity is greater than allowed, the installation is prevented.

• If the quantity is less than allowed, the installation is completed, and a missing part is generated
with the remaining quantity.

The Part Used column for the physical part is set to one of the following values after installing a physical
part:

• Preferred
If the newly installed physical part is a valid preferred physical part for the selected usage, the Part
Used column is set to Preferred.

• Substitute
If the newly installed physical part is a valid substitute, the Part Used column is set to Substitute.

• Alternate
If the newly installed physical part is a valid alternate, the Part Used column is set to Alternate.

• Deviated
If the newly installed physical part is an approved deviation from the design and is not a valid
substitute or alternate for selected usage, the Part Used column is set to Deviated.

• Extra to Design
If the newly installed physical part is an approved deviation and does not exist in the design structure,
the Part Used column is set to Extra to Design.

Uninstall a physical part

You can uninstall a child physical part from a parent physical part in the as-built structure.

1. From the navigation pane, click As-Built Manager.

2. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

3. From the As-Built Manager view, click Open by Name to open the physical structure where
you want to uninstall the physical part.

4. Select the child physical part. Right-click and choose Uninstall Physical Part.
A dialog box is displayed asking you if you are sure you want to uninstall the physical part.

5. Click Yes to uninstall the physical part.

The physical part in uninstalled from the structure and Part Used column is set to Missing.
If there is more than one missing part, then a single missing part is created with the total allowed
remaining quantity, and the other missing parts are deleted.

5-10 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

As-Built Structure Part Used

BH001–nn/MTrucknn–A Preferred

BH012-nn/A Preferred

BH013-nn/A Preferred

BH014–nn/SHnn–001–A Preferred

BH020–nn/A Missing

Replace a physical part

You can replace an existing or missing physical part with a different physical part in an as-built structure.
When you replace a physical part, the following occurs:

• The original physical part is removed from the structure and replaced with the new physical part.

• The installation time on the replacement physical part is updated with the date the physical part was
replaced.

• The uninstall time on the original physical part is updated with the date the physical part was
replaced.

Note:
If the replacement part is not a valid preferred, substitute, or alternate part, you must set up an
authorized deviation.

1. From the navigation pane, click As-Built Manager.

2. From the As-Built Manager view, click Open by Name to open the physical structure where
you want to replace the physical part.

3. Choose one of the following methods to identify the physical part you want to use as the
replacement:

• Copy the physical part you want to use as the replacement.

a. Click Open by Name to open the replacement physical part.

b. Right-click the replacement physical part and choose Copy.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-11

c. Right-click the physical part you want to replace and choose Replace Physical Part or click
the Replace Physical Part button on the main toolbar at the top of the As-Built
Manager pane.

The Replace Physical Part dialog box appears.

The To Be Installed Physical Part field is set to the copied physical part.

• Search for the physical part you want to use as the replacement.

a. Right-click the physical part you want to replace and choose Replace Physical Part or click
the Replace Physical Part button on the main toolbar at the top of the As-Built
Manager pane.

The Replace Physical Part dialog box appears.

b. Perform the following steps to search for the physical part to be installed:

A. Click and select Add.

The Installable Physical Parts dialog box appears.

B. Click the Search tab and enter the following information you want to use as filters for
searching.

Field name Definition Valid values

The Replace Physical Part dialog box reappears with the To be Installed Physical
Part field set to the selected physical part.

5-14 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

4. Click the Set Date button to set the replace date when the replacement occurred.

5. Click OK to replace the physical part.

If the installed Preferred part is a Preserve Quantity part, the quantity is checked against the
neutral structure.

• If the quantities match, the original physical part is replaced.

• If the quantity is greater than allowed, the replacement is prevented.

• If the quantity is less than allowed, the replacement is completed, any existing missing parts are
deleted, and a missing part is generated with the remaining quantity.

Rebasing physical parts

Rebasing a physical part relates the as-built structure to a different configuration of a neutral structure.
The new rebased structure uses the new configuration for its structure context.

Note:
The physical part must have a Released status before you can rebase it.

The following apply to usages in the rebased physical configuration:

• If the component exists in the rebased neutral structure, the rebased physical part is assigned the
same usage as specified in the neutral structure.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-15

• If the corresponding usage of a component is not present in the rebased neutral structure. the usage
of the rebased physical part is set to extra to design and requires no deviation authorization.

• If the component and usage is new in the rebased neutral structure, the usage of the physical part is
set to missing.

Example:
You may want to rebase a physical structure to the same neutral structure but with a different
variant.
The original physical structure was generated from the bearing housing assembly neutral structure
that contained the regular bearing housing. It was rebased to the bearing housing assembly
neutral structure with the heavy duty bearing housing. As the following figure shows, because the
rebased neutral structure contains the heavy duty bearing housing, the physical structure now
contains a missing part for the heavy duty bearing housing and the regular bearing housing is
installed as extra to design.

5-16 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Rebase a physical part

1. From the navigation pane, click As-Built Manager.

2. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

3. From the As-Built Manager view, click Open by Name to open the neutral structure or part to
be used to rebase the physical structure or part.

4. Click Open by Name to open the released physical structure or part to be rebased.

5. Click Show/Hide lower Structure Panel located at the top of the application to display the
neutral and physical parts or structures using split structure panes.

6. Select the neutral part. If you are rebasing a physical structure to a different neutral structure,
select the neutral structure parent part.

7. Select the released physical part. If you are rebasing a physical structure, select the physical
structure parent part.

8. Choose Tools → Rebase Physical Part.

The Rebase Physical Part dialog box appears.

9. Click the Set Date button to set the rebase date when the rebase occurred.

10. In the Structure Context Name box, type the name of the structure context used to store the
neutral product configuration information or use the name that is automatically generated.
The structure context name is automatically created using the part number of the rebased neutral
part. If the physical part has a serial number, the structure context name is automatically named as
part number/serial number.

11. Click OK to rebase the physical part.

Teamcenter checks the quantities of the parts installed in the rebased structure.

• If the quantity is over the allowed limit, the part is changed to a Extra to Design part.

• If the quantity is under the allowed limit, the part is shown as installed in the correct position, but a
new missing part is generated with the remaining quantity.

Delete a physical part

You can delete a physical part if it has no child physical parts. To delete a physical part with child physical
parts, you must delete the last child physical part first and work your way up to the parent physical part.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-17

Note:
You can delete a physical part only from My Teamcenter.

1. In My Teamcenter, select the physical part to delete.

2. Choose Edit → Delete.

Implementing deviations

Deviations occur when you install a physical part that is not a preferred, alternate, or substitute physical
part into an as-built structure. An authorized deviation can be used only once. If you uninstall and
reinstall a deviated physical part, a new authorization must be created.

The workflow to add a deviated physical part to your as-built structure is as follows:

1. Create the deviation authority item class for the physical part.
A deviation authority item class authorizes the installation of a physical part that is a deviation from
the design structure. The MRO Deviation Authority List LOV determines the list of item classes
that can be used to authorize a deviation.
By default, the item classes that can be used as a deviation authority item are:

• Deviation document
• Deviation request
• Service event
• Aerospace and Defense deviation request

2. Set up the deviation to specify the authorized deviation item class used for the deviated physical
part. The authorized deviation item must not be released to set up a deviation.

3. Route the authorized deviation item through the appropriate workflow.

4. Install the deviated physical part into your as-built structure.

Create a deviation authority item

1. Click My Teamcenter.

2. Choose File → New → Item.

3. From the New Item dialog box, select Deviation Document and click Next.

4. Enter information into all the required fields and click Finish.

5-18 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

5. If you do not want to create another deviation document, click Finish.

If you want to create another deviation document, repeat steps 2–4.

Set up a deviation

1. From the navigation pane, click As-Built Manager.

2. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

3. From the As-Built Manager view, click Open by Name to open the deviated part.

4. Select the deviated part. Right-click and choose Copy.

5. From the As-Built Manager view, click Open by Name to open the physical structure where
you want to install the deviated part.

6. Right-click the parent physical part and choose Setup Deviation or click the Setup Deviation
button on the main toolbar at the top of the As-Built Manager pane.
The Setup Deviation dialog box appears.

7. Click to set the value of Document Id and select Add.

The Search dialog appears.

Note:
The deviation authority item must not be released to set up a deviation.

8. Click Find to search for the deviation authority item ID using the search dialog box. You can use
wildcards for searching.

9. Click OK to set up the deviation. Alternatively, click Cancel to exit.

Send the deviation authority item through the required workflow

1. From the navigation pane, select the deviation authority item.

2. Choose File → New → Workflow Process.

3. In the New Process Dialog box, type the process name in the Process Name box.

4. From the Process Template list, select TCM Release Process.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-19

Note:
The TCM Release Process workflow is provided with the Teamcenter Foundation feature.
You can configure this workflow or create your own to set up the process flow, reviewers,
and business validations required to route a deviation document for review and approval.

5. Click OK. Alternatively, click Cancel to exit.

Install a deviated part

1. From the navigation pane, click As-Built Manager.

2. From the As-Built Manager view, click Open by Name to open the deviated part.

3. Choose one of the following methods to identify the deviated physical part you want to install:

• Copy the deviated physical part you want to install.

a. Right-click the physical part and choose Copy.

b. Select the physical structure where you want to install the deviated physical part.

c. Right-click the parent and choose Install Physical Part or click the Install Physical Part
button on the main toolbar at the top of the Service Manager pane.

The Install Physical Part dialog box appears. The To Be Installed Physical Part field is set
to the copied physical part.

d. Select the usage name to set the usage for the installed deviated physical part. If the
physical part is an addition to the physical structure, select Extra to Design as the usage.

• Search for the physical part you want to install.

a. Select the physical structure where you want to install the deviated physical part.

b. Right-click the parent and choose Install Physical Part or click the Install Physical Part
button on the main toolbar at the top of the Service Manager pane.

The Install Physical Part dialog box appears.

c. Select the usage name to set the usage for the installed deviated physical part. If the
physical part is an addition to the physical structure, select Extra to Design as the usage.

d. Perform the following steps to search for the physical part to be installed:

5-20 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

A. Click and select Add.

The Installable Physical Parts dialog box appears.

B. Click the Search tab and enter the following information you want to use as filters for
searching.

Field name Definition Valid values

The results display the valid deviated physical parts that can be installed.

D. Select the physical part from the results and click OK.

The Install Physical Part dialog box reappears with the To be Installed Physical Part
field set to the selected physical part.

e. Click the Set Date button to set the installation date when the installation occurred.

f. If the Usage Name is set to Extra to Design, in the Extra to Design Usage Name box, type
the usage name for the installed physical part.

g. Click OK to install the deviated physical part.

The deviated physical part is installed in the structure.

View the deviation authorization information

You can view the authorizing deviation item for a deviated part.

1. From the navigation pane, click As-Built Manager.

2. Select the physical structure containing the deviated part and choose Send to → My Teamcenter.

3. Click the Details tab.

The Allowed Deviation relation is displayed.

4. Select the deviated part.

5-22 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

5. Right-click and choose Properties on Relation....

The properties of the Allowed Deviation relation are displayed.

The Deviation Authority field shows the deviation authority item used to authorize the deviation.

Release an as-built physical structure

You can release the as-built structure after you finish building it.

1. From the navigation pane, select the as-built structure you want to release.

2. Choose File → New → Workflow Process.

3. In the New Process Dialog box, choose Release AsBuilt Structure from the Process Template list.

Note:
The Release AsBuilt Structure option is the standard workflow provided with As-Built
Manager. This workflow also validates for any missing physical parts.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-23

You can configure this workflow or create your own to set up the process flow, reviewers, and
business validations required to release an as-built structure.

4. Click OK. Alternatively, click Cancel to exit.

Rebuilding an as-built structure

You can rebuild an as-built physical structure to create a new revision. The new revision of the physical
structure represents a new refurbished build of the physical asset. New build revisions are created when
the physical parts are at a Released state.

Note:
The MaturityStatuses constant defines the release status for rebuilding an as-built physical
structure.

When you select a child part of a physical structure for rebuild, the following scenarios apply:

• The structure is traversed upward and new build revisions are created for each parent physical part
that is displayed in As-Built Manager and is released.
The following figure shows the shaft as the selected part for rebuild. The parent physical parts for the
turboengine and bearing housing are created with a new build revision B.

5-24 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

• While traversing the displayed physical structure upward in As-Built Manager, if any of the physical
parts are not released, the rebuild will not traverse above the unreleased part revision.

• While traversing the displayed physical structure upward in As-Built Manager, and a parent physical
part is not released, the unreleased revision of the parent will be related to the new build revision of
the child part. The previous relationship between the child part and the unreleased parent will no
longer exist.
The following figure shows the bearing housing as the selected part for rebuild. The parent physical
part for the turboengine is not released. A new relationship is created between the new revision B of
the bearing housing and the unreleased revision A of the turboengine.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-25

Rebuild an as-built structure

1. From the navigation pane, click As-Built Manager.

2. Click Open by Name to open the released as-built physical structure or physical part that you
want to rebuild.

3. Select the part from the physical structure.

4. Choose Tools → Rebuild As-Built Structure or click the Rebuild As-Built Structure button on
the main toolbar at the top of the As-Built Manager pane.

The Rebuild As-Built Structure dialog box appears.

5. If you select a child part of the physical structure, the following dialog box appears:

5-26 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Click Yes to continue.

6. Click the Set Date button to set the rebuild date when the new revision of the physical
structure was created.

7. Click OK to rebuild the physical structure.

View untraced structures

You can display the parts in the neutral structure that are not traceable in the related physical structure.
Parts that are not traceable have the part logistics property Traceable set to False in context of the
parent physical structure and a physical part is not generated for that neutral part.

The following occurs when you display an untraced structure in As-Built Manager:

• The untraced parts are displayed as neutral parts in the physical structure.

• Any action that can be run on neutral parts is available on the displayed untraced parts.

When viewing an as-built structure using visualization, you can also display the untraced parts.

1. From the navigation pane, click As-Built Manager.

2. Click Open by Name to open the physical structure that you want to display the untraced parts
for.

3. Select the parent part of the physical structure.

4. Choose View → Show Untraced Parts or click the Show Untraced Parts button on the main
toolbar at the top of the As-Built Manager pane.

The untraced parts are displayed.

BH001/InTest–A
BH012/A
BH013/A
BH014/A

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 5-27

BH015/A
BH016/A untraced part

Updating structures using Excel Live

You can update physical structures using Excel Live. Teamcenter Extensions for Microsoft Office provides
synchronous access to Teamcenter workspace objects through Microsoft Office Excel. With the live
Excel, Extensions for Office gives Excel direct connectivity to the Teamcenter server and allows you to
edit physical structures using Excel.

To generate a file in live Excel, you choose the related option when exporting data for selected objects in
the Teamcenter rich client. The following occurs after export:

• The data exported to the output file consists of property values for the objects.

• The exported property values are synchronized with the corresponding values in Teamcenter.

• Values that you edit in the output file are changed interactively in Teamcenter.

5-28 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
6. Comparing as-built structures
Comparing as-built structures
As shown in the following figure, a user such as a production planner can compare two physical
structures or a physical with a neutral structure to identify changes or differences between two product
structures.

For example, you can compare the neutral structure and the physical structure to highlight the missing
and nontraceable parts or compare two different installations of the same physical structure to show
differences. The differences are displayed using colors that represent full, partial, or no matches
between the structures. You can also optionally generate a report summarizing the differences.

Comparing structures with or without context

Comparing with context

As-Built structures can be compared with or without context.

If you select the compare (with context) option, you are comparing the parts in position in the physical
or neutral structures. For example, you can use compare with context to determine if the left and right
engines were swapped. A compare without context would not detect those differences.

For this comparison to work properly, you must set a value in the ID in Context column in the As-Built
Manager window for the parts in the neutral structure. This comparison is similar to an accountability
check between structures described in the Multi-Structure Manager Guide. You can select additional
properties for comparison and set the context ID to match any source and target line that have the same
absolute occurrence identifier.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 6-1

Set compare with context preferences

To specify the default and additional properties used for comparing as-built structures with context, an
administrator sets the DefaultAsBuiltAccCheckProperties and AdditionalAsBuiltAccCheckProperties
preferences.

Global constant Default value

DefaultAsBuiltAccCheckProperties phbl_part_number
phbl_part_used_is

AdditionalAsBuiltAccCheckProperties phbl_part_usage_name

Perform compare with context

You compare two as-built structures in the As-Built Manager view using two separate panes.

1. From the navigation pane, click As-Built Manager to open the source structure in the bottom pane
and the target structure in the top pane.

a. From the navigation pane, click As-Built Manager.

b. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

c. From the As-Built Manager view, click Open by Name to open the source structure.

d. Click Show/Hide lower structure panel located at the top of the application window to
create a new empty (target) pane. The source structure appears in the bottom pane.

e. Click Open by Name to open the second structure in the top pane.

2. After you open the as-built structures in the appropriate panes, configure them by setting the
revision rule and/or variant rule in each pane.

3. Expand and collapse assemblies to define the scope of the comparison.

4. Choose Tools → Compare.

The Compare dialog box appears.

5. Do one of the following:

• If you want to reverse source and target as-built structures, select Flip source and target.

• To compare as-built structures with context, select Compare (with context).

6-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

6. Select Display Options to change comparison color scheme. When you compare two structures,
the results are displayed in a variety of colors that you can change using the display options. To
help users who cannot differentiate colors, a tool tip shows the name of the color. If the name is
not available, the tool tip displays the RGB (red, green, blue) value.

• Check the display options you require.

Display option Description

Full match If all properties of a source object are identical to the

properties of a target object, both objects are set to the
same background color. The default color is green.

Partial match If part of the properties of a source object is identical to the

properties of a target object, both objects are set to the
same background color. The default color is yellow.

Multiple match If the properties of a source object are identical to the

properties of target objects, all objects are set to the same
background color. The default color is orange.

Multiple partial If part of the properties of a source object is identical to the

match properties of target objects, all objects are set to the same
background color. The default color is pink.

Missing target If the properties of a source object are not found by target
objects, the source object is set to this color. The default
color is red.

Missing source If the properties of a target object do not meet properties of

any source objects, the target object is set to this color. The
default color is white.

• Change the default color by clicking next to the color. Set the colors by selecting a color
swatch, and setting HSB (hue, saturation, brilliance) or RGB (red, green, blue) values.

7. Select Compare Options to change properties.

• To compare any source line and target line that have the same absolute occurrence identifier,
select the Treat same ID in context as same check box. If not selected, the compare does not
match lines with different absolute occurrences, even if they share the same absolute
occurrence identifier.

• To match lines in the source and target that have the same properties as those you choose in the
Selected Properties list, select the Compare Additional Properties check box. If not selected,
the compare includes only those default options defined by your administrator.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 6-3

• Use the button to select the properties from the Available Properties list and move them
to the Selected Properties list. Use the button to remove the properties from the
Selected Properties list and move them back to the Available Properties list.

8. Click Check to begin the comparison. Alternatively, click Cancel to exit.

Comparing without context

As-Built structures can be compared with or without context.

If you choose the Compare (without context) option, you can compare structures at the at the
assembly or subassembly levels and set the level or mode of comparison. This comparison is similar to
comparing two structures in the Structure Manager view described in the Structure Manager Guide.
When Teamcenter compares the displayed product structures (BOMs); it compares each level that is
visible. Consequently, you can compare different views or configurations by expanding the structure to
the desired level. Also, if you collapse assemblies in the product structure, the comparison excludes the
content of those assemblies. You can use this feature to limit the scope of a comparison.

Set compare without context preferences

• Property preferences
To specify the default and additional properties used for comparing as-built structures without
context, an administrator sets the DefaultAsBuiltCompareProperties and
AdditionalAsBuiltCompareProperties preferences.

Global constant Default value

DefaultAsBuiltCompareProperties phbl_part_number
phbl_part_usage_name

AdditionalAsBuiltCompareProperties phbl_part_used_is

• Display preferences
Because the display options are unavailable when comparing without context, an administrator can
change the colors displayed for added and changed occurrences by setting the PSEAdditionColorPref
and PSEChangedColorPref preferences. No colors are displayed for full matches.

Global constant Default value

PSEAdditionColorPref red

PSEChangedColorPref orange

6-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Perform compare without context

You compare two as-built structures in the As-Built Manager view using two separate panes.

1. From the navigation pane, click As-Built Manager to open the source structure in the bottom pane
and the target structure in the top pane.

a. From the navigation pane, click As-Built Manager.

b. Choose Window → Show View → As-Built Manager to open the As-Built Manager view.

c. From the As-Built Manager view, click Open by Name to open the source structure.

d. Click Show/Hide lower structure panel located at the top of the application window to
create a new empty (target) pane. The source structure appears in the bottom pane.

e. Click Open by Name to open the second structure in the top pane.

2. After you open the as-built structures in the appropriate panes, configure them by setting the
revision rule and/or variant rule in each pane.

3. Expand and collapse assemblies to define the scope of the comparison.

Note:
You compare only the visible structures displayed in the panes.

4. Choose Tools → Compare.

The Compare dialog box appears.

5. Do one of the following:

• If you want to reverse source and target as-built structures, select Flip source and target.

• To compare as-built structures without context, select Compare (without context).

6. Select Compare Options to change compare modes.

• Select the compare mode to set the level of comparison.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 6-5

Mode Description

Single Level Compares only the first levels of the product structures.

Multi Level Performs a single-level comparison at the top level, and then
starts further single-level comparisons on any subassemblies that
match between the two product structures. This process is
repeated successively down the product structure.

Lowest Level Compares only the lowest level items of the product structures,
ignoring all intermediate assemblies. This is useful for verifying
that piece parts are consistent.

7. If you want to display a report window summarizing the differences between the structures, select
the Report check box.
The Print window appears after the compare is complete.

8. To print the report, choose Print the file . To save the report to a local text file, from the report
window, choose Saves to a user specified file . To close the window, choose Close.

• In single-level mode and lowest level mode, the reports are flat lists of differences.

• In multilevel mode, the report is an indented output is produced, showing the parent assemblies
of any changed items.

9. Click Check to begin the comparison. Alternatively, click Cancel to exit.

Clear comparison
• To clear the highlighting colors, choose Tools → Clear.

Note:
If you start a new comparison before clearing the results of the previous comparison, the
existing results are automatically cleared.

Comparing a neutral structure to a physical structure

Comparing as-built physical structures to neutral structures

You can compare an as-built neutral structure with an as-built physical structure. For example, you may
want to highlight the following as differences:

• Nontraceable parts

6-6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

• Missing physical parts

• Substitute parts

• Deviated parts

• Global alternate parts

Compare with context example between a neutral structure and a physical

structure

The following compare information and figure show the result of a compare with context between the
neutral structure and the physical structure for the bearing housing assembly.

• Source structure: physical structure in the top pane for the bearing housing assembly.

• Target structure: neutral structure in the bottom pane for the bearing housing assembly.

• All the display options are selected.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 6-7

Comparing as-built physical and neutral structures with context

The color green indicates a full match. The following parts show differences.

Part ID Structure Color Why?

BH014 Neutral Yellow indicating a partial Some properties are identical

match because the alternate part for
the shaft was installed in the
physical structure.

BH014A Physical Cyan indicating the physical The alternate part for the
part is an alternate shaft was installed in the
physical structure.

6-8 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Part ID Structure Color Why?

BH015 Neutral Yellow indicating a partial Some properties are identical

match because the substitute part
for the shaft was installed in
the physical structure.

BH015S Physical Royal blue indicating the The substitute part for the
physical part is a substitute shaft was installed in the
physical structure.

BH021 Neutral Light blue indicating a The physical part for the
missing source. hardware is missing from the
source physical structure.

Compare without context example between a neutral structure and a

physical structure

The following compare information and figure show the result of a compare without context between
the neutral structure and the physical structure for the bearing housing assembly.

• Source structure: physical structure in the top pane for the bearing housing assembly.

• Target structure: neutral structure in the bottompane for the bearing housing assembly.

• Display options:

• Set to Multi Level.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 6-9

Comparing as-built physical and neutral structures without context

No color indicates a full match. Because compare without context compares the parts that are visible
and does not compare properties, the following parts show differences.

Part ID Structure Color Why?

BH014 Neutral Red indicating no match The alternate part for the
shaft was installed in the
physical structure.

BH014A Physical Cyan indicating the physical The alternate part for the
part is an alternate shaft was installed in the
physical structure.

6-10 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Part ID Structure Color Why?

BH015 Neutral Red indicating no match The substitute part for the
shaft was installed in the
physical structure.

BH015S Physical Royal blue indicating the The substitute part for the
physical part is a substitute shaft was installed in the
physical structure.

BH021 Neutral Red indicating no match The hardware does not exist
in the physical structure.

Comparing two physical structures

Comparing two as-built physical structures

You can compare two as-built physical structures. For example, you may want to highlight the
differences between two installations of the same physical structure.

Compare with context example between two physical structures

The following figure shows the result of a compare with context between two physical structures for the
bearing housing assembly.

• Source structure: The bearing housing assembly in the bottom pane used in the missile truck. The
serial number is set to MTruck.

• Target structure: The bearing housing assembly in the top pane used in the supply truck. The serial
number is set to STruck.

• All display options are selected.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 6-11

Comparing two as-built physical structures with context

The color green indicates a full match. The following parts show differences.

Part ID Structure Color Why?

BH014 MTruck Yellow indicating a partial Some properties are identical

match because the alternate part for
the shaft was installed in the
physical structure used in the
supply truck.

BH014A STruck Cyan indicating the physical The alternate part for the
part is an alternate shaft was installed in the
physical structure used in the
supply truck.

6-12 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Part ID Structure Color Why?

BH015 MTruck Yellow indicating a partial Some properties are identical

match because the substitute part
for the shaft was installed in
the physical structure used in
the supply truck.

BH015S STruck Royal blue indicating the The substitute part for the
physical part is a substitute shaft was installed in the
physical structure used in the
supply truck.

BH016 STruck Light blue indicating a The regular bearing housing

missing source. does not exist in the source
physical structure used in the
missile truck.

BH016HD MTruck Red indicating a missing The heavy duty bearing

target. housing does not exist in the
target physical structure used
in the supply truck.

BH020D MTruck Yellow indicating the physical The deviated redesigned part
part is a deviation for the retaining ring was
installed in the physical
structure used in the missile
truck.

BH020 STruck Yellow indicating a partial Some properties are identical

match because the deviated
redesigned part for the
retaining ring was installed in
the physical structure used in
the missile truck.

Compare without context example between two physical structures

The following figure shows the result of a compare without context between two physical structures for
the bearing housing assembly.

• Source structure: The bearing housing assembly in the bottom pane used in the missile truck. The
serial number is set to MTruck.

• Target structure: The bearing housing assembly in the top pane used in the supply truck. The serial
number is set to STruck.

• Display options:

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 6-13

• Set to Multi Level.

Comparing two as-built physical structures without context

No color indicates a full match. Because compare without context compares the parts that are visible
and does not compare properties, the following parts show differences.

Part ID Structure Color Why?

BH014A STruck Cyan indicating the physical The alternate part for the
part is an alternate shaft was installed in the
physical structure used in the
supply truck.

BH014 MTruck Red indicating no match The alternate part for the
shaft was installed in the

6-14 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Part ID Structure Color Why?

physical structure used in the

supply truck.

BH015S STruck Royal blue indicating the The substitute part for the
physical part is a substitute shaft was installed in the
physical structure used in the
supply truck.

BH015 MTruck Red indicating no match The substitute part for the
shaft was installed in the
physical structure used in the
supply truck.

BH016 STruck Red indicating no match The heavy duty bearing

housing is installed in the
physical structure used in the
missile truck.

BH016HD MTruck Red indicating no match The regular bearing housing

is installed in the physical
structure used in the supply
truck.

BH020 STruck Red indicating no match The deviated redesigned part

for the retaining ring was
installed in the physical
structure used in the missile
truck.

BH020D MTruck Red indicating no match The deviated redesigned part

for the retaining ring was
installed in the physical
structure used in the missile
truck.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 6-15

6-16 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
7. Visualizing as-built physical structures
Visualizing as-built physical structures
You can visualize the as_built neutral and physical structures from the As-Built Manager view with the
embedded viewer. You can also view any untraced parts in the as-built physical structure. When you
visualize the as-built physical structure, you are looking at the data associated with its linked neutral
structure. The visualization data is only associated to the design parts of the neutral structure and not to
the related as-built physical structure.

You use the embedded viewer in the As-Built Manager view in the same way as the embedded viewer
in the Structure Manager view. If you want to use the enhanced capabilities of Lifecycle Visualization or
the embedded viewer, you must purchase and install the necessary additional licenses.

Note:
Physical parts with Part Used status set to Missing do not display any visualization.

The following figure shows an example where you can visualize both the neutral and physical structures
in the As-Built Manager view with a split window. You may want to use a split window to see what the
missing physical parts look like by viewing the visualization of their related neutral part item revisions.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 7-1

Visualizing as-built neutral and physical structures

Associating image file datasets

To visualize the neutral or as-built physical structure, you must create DirectModel datasets containing
the image (JT) files. You attach the datasets with the Rendering relationship to the neutral part item
revisions that compose the neutral structure. When you visualize the physical structure, you are
accessing the same datasets attached to its linked neutral structure. A DirectModel dataset can contain
several JT files with different names, so you should set rules that determine the file to display.

Visualize the as-built structure model

The lines in the project workspace are shown with a check box to the left of the part. You select the
check boxes next to the part and assembly names in the assembly tree to choose which parts and
assemblies to load and make visible. By default, they are all unchecked.

7-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

1 Project workspace Displays the product structure.

2 Navigation toolbar Toolbar used to navigate the 3D model.

3 Graphical viewing window Displays the 3D model associated with the product
structure.

1. Open the structure in the As-Built Manager view by one of the following methods:

• From the navigation pane, click As-Built Manager and click Open by Name to open the
structure.

• If you are viewing the structure in the Structure Manager view, right-click the structure parent
and choose Send to → As-Built Manager.

2. Choose View → Show Data Panel, or click the Show/Hide Data Panel button on the toolbar.

3. Click the Assembly Viewer tab to visualize the 3D models for the as-built assembly structure.

4. (Optional) To view a split window, click Show/Hide lower Structure Panel located at the top of
the application.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 7-3

5. To display or hide entire models, assemblies, or individual parts, you can do any of the following:

To Do this

View the entire structure Select the check box for the top-level line in the structure to
load the graphics for every line in the structure.

View a selected part of the Select the check boxes only for those lines for which you
structure want to load the graphics.

View only the part Select the check box for the line for a part.

View an assembly Select the check box for a line representing the assembly.

Hide the entire structure Clear the check boxes.

Using the graphics menu

The Graphics menu appears when you click the Assembly Viewer tab.

Command Description

Selection → Select All Selects all the objects displayed in the viewer.

Selection → Select None Clears any objects currently selected in the viewer.

Selection → Reverse Selection Selects all objects not selected in the viewer, while
simultaneously unselecting any objects currently selected in the
viewer.

Visibility → View Selected Blanks and unblanks objects loaded in the viewer.

Note:
The term loaded refers to an object whose JT file has been
loaded in the viewer. A loaded object may or may not be
visible, depending on whether it has been blanked or
unblanked.

Visibility → Blank Selected Makes any objects selected in the viewer invisible.

Visibility → Blank All Makes all objects in the viewer invisible.

Visibility → Unblank All Makes all objects loaded in the viewer visible.

Visibility → Reverse Blank All Makes any currently visible objects invisible, while
simultaneously making visible any loaded objects which are
currently invisible.

Visibility → Unload Selected Unloads any objects selected in the viewer.

7-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Command Description

Edit Color/Translucency Modifies the color, transparency, and shine of selected objects in
the viewer. These settings only apply to the currently loaded
objects. The next time the edited object is loaded, the settings
revert to the default color and translucency.

Insert Allows you to insert JT, stereolithography (.stl), and VRML (.wrl)
files as reference graphics.

Insert → Insert from File Inserts a reference graphic from the operating system, using the
Open by Name dialog box.

Insert → Insert from Clipboard Inserts a reference graphics object from the clipboard.

Note:
Only item revisions (not items) can be displayed as
reference graphics.

Views → Views Control Creates, edits, and displays standard views, using the Rotate and
Standard Views dialog boxes.

Draw Children Displays the components of a subassembly. You can also access
this command if you right-click in the BOM.

Show Subcomponents Breaks down solids in the corresponding monolithic JT files and
make the subcomponents independently controllable. This
function is available only for only leaf and unpacked BOM line
nodes.

Hide Subcomponents Removes all merged subcomponents and the one-level tree from
the tree. You can load or unload the monolithic JT file related to
this BOM line node in the normal way.

Export 3D File Exports the current visible objects to a STEP or VRML file.

Replace JT File Replaces the JT file that represents an item revision. You can
choose a replacement file from one of the JT files associated with
the current BOM line item.

Transformation → Temporary Generates an exploded view for use in technical illustrations.

Transformation

Transformation → Persistent Modifies the physical location of a part (or set of parts) in an
Transformation owning assembly.

Clearance → Preferences → Calc Specifies the precision and nature of the clearance check.
ulator Settings

Clearance → Preferences → Clear Defines the clearance conditions based on the metadata of the
ance Requirements structure or elements.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 7-5

Command Description

Clearance → Preferences → Clear Adjusts the clearance results preferences to change the
ance Results appearance and behavior of clearance results.

Clearance → Preferences → Togg Displays the clearance results window.

le Results Window

Performance Sets rendering, culling and general performance preferences.

Preferences Sets clearance analysis and general viewer preferences.

7-6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
8. Navigating the 3D model
When you visualize the 3D model associated to the physical or neutral structure. the 3D navigator
toolbar appears at the top of the Assembly Viewer window. It is used to manipulate the 3D view.

Option name Mode Use this button to

Fly Explore Enable Examine mode.
Examine
Examine Explore Enable Fly mode.
Fly
Examine Fly Enable Explore mode.
Explore
Examine Fly Return to the last static view.
Previous View Explore
Examine Fly Move to the next static view
Next View Explore
Fit All Examine Fly Fit all visible parts of the model into the viewing
Explore window.
Zoom Area Examine Fly Zoom to a specific area of the model.
Explore
seek Examine Fly Center a point of the model. This point becomes the
Explore center of rotation.
Rotate Examine Rotate your model in the viewing window.

Pan Examine Fly Pan the model in the plane of the viewing window.
Explore
Zoom Examine Move closer to or farther from the model.

Position Explore Choose your position in the model.

Level Fly Explore Align the view to the up vector.

Terrain Following Fly Explore Remain a specified distance above the floor upon
which you are moving.
Collision Detection Fly Explore Stop moving through your model when you come into
contact with a part.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 8-1

Go Home Explore Return to the location and position you were at when
you last selected Set Home.
Set Home Explore Set the current location and position as the home
location.
Preferences Examine Fly Set mode preferences.
Explore

8-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

• Importing as-built physical structures from third-party systems or other Teamcenter sites into
Teamcenter using PLM XML format.

• Exporting as-built physical structures data from Teamcenter to other Teamcenter sites or third-party
systems using PLM XML format.

• Using Multi-Site Collaboration to share As-Built Manager data between multiple Teamcenter sites.

Export an as-built structure

A user such as a production planner can export as-built data from Teamcenter to other Teamcenter sites
or third-party systems.

Exported data includes:

• Physical parts with revisions.

• Physical realization information.

• As-built structures including installation date.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 9-1

• Physical alignment relations.

• Lot information if assigned to a physical part.

• Deviation information.

1. Select the physical structure to be exported.

2. Choose Tools → Export → To PLMXML.

The system displays the PLM XML Export dialog box.

3. In the Export Directory box, select the directory in which to place the PLM XML file. Click Browse
to locate the directory.

4. Specify the name of the export file in the Export Filename box.

5. Choose a transfer mode from the Transfer Mode list.

The transfer mode AsBuiltDataExport is provided with As-Built Manager for exporting as-built
structure information.

6. (Optional) Click Select Languages to display the Language Selection dialog box for the languages
configured at your site.

• Main Language is the site master language. This cannot be changed.

• The Available Languages box lists the languages you can select as additional languages for
export.

• The Select Additional Languages box lists the preconfigured languages for the selected
transfer mode.

To select additional languages for export, follow these steps:

a. Select a language in the Available Languages box.

b. Click the Add button .

• The selected language is added to the Selected Additional Languages box.

• To reorder the languages in the Selected Additional Languages box, select a language
and use the move buttons as required.

c. Click OK or Apply.

9-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

The languages selected for export are displayed in the Languages box.

Note:
If you change the transfer mode, the Languages entries remains unchanged. You can
use the Language Selection dialog box again to add or remove more languages.

7. (Optional) Select a revision rule to configure the assembly to be exported.

8. If you do not apply a revision rule, only the parent item revision is exported.

9. (Optional) Select Open PLM XML File to view the file when the export operation is complete.

10. (Optional) Select the View Log File check box to view the log file when the data translation is
complete.

11. (Optional) Select the Perform Export In Background check box to perform an asynchronous
export.

12. Click OK to export the objects in the Object List and close the dialog box.

Importing as-built structures

A user such as a production planner can import as-built data from a third-party systems or other into
Teamcenter sites into Teamcenter.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 9-3

You can import as-built physical structure data into Teamcenter from any third-party system if it
conforms to the PLM XML schema. Data Exchange creates the as-built structure using the
RealizedProduct, RealizedProductRevision, Lot, LotRevision, RealizedProductUsage,
AllowedDeviation, Deviation, and DeviationRevision elements. Before you import an as-built
structure, the neutral structure and the part logistics information must exist on the importing site.

If the occurrence information is provided along with the occurrence name, the alignment relation is
created. If the occurrence name is not provided or the occurrence name does not match the neutral part
occurrence name, Data Exchange processes the structure relationship without the alignment relation.

If the lot information is provided and the lot is not defined in Teamcenter, Data Exchange creates and
assigns the physical part to the new lot. If the lot exists, the physical part is assigned to the existing lot.

Import an as-built structure

Note:
Before you import an as-built structure, the neutral structure and the part logistics information
must exist on the importing site.

You can import an as-built structure into Teamcenter from a third-party system by performing the
following steps:

1. Choose Tools → Import → From PLMXML.

The system displays the PLM XML Import dialog box.

2. Click Browse to the right of the Importing XML File box.

The system displays the Select Object dialog box.

3. Navigate to the directory containing the file and select the file.
The system displays the file name in the Directory name box.

4. Click Select.
The system displays the path to the selected file in the Importing Object box of the dialog box.

5. Select the transfer mode to be used to configure the import operation.

Note:
The transfer mode AsBuiltDataImport is provided with As-Built Manager for importing as-
built structure information from a third-party system into Teamcenter.

6. (Optional) Select the View Log File check box to view the log file when the data transfer is
complete.

9-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

7. Click Apply to start the import operation and retain the dialog box, or click OK to start the import
operation and exit the dialog box.
The system imports the data as follows:

• By default, the imported object has no container reference. You can use relevant search criteria
to find the imported object and so you can copy it to a folder.

• To have Teamcenter import objects into your Newstuff folder, create the
PLMXML_put_objects_in_newstuff_on_import preference and set the value to TRUE.
Imported objects are placed in a folder with the same name as the imported XML file.

Note:
If object names or IDs are encountered that exceed the character limit for those fields in
Teamcenter, the name and/or ID is truncated when imported into Teamcenter. Teamcenter
provides 128 bytes for item IDs and names.

Import as-built structure exceptions

When you import an as-built structure into Teamcenter from a third-party system and a physical part has
a status of released in Teamcenter, the import fails for that physical part. The relationship is not created
between the as-built structure parent and the child physical part that is released. The import continues
for the remaining components.

As the following figure shows, the relationship between the parent physical part Aircraft #100 and the
physical part Engine #200 is not created in Teamcenter because Aircraft #100 has a status of released.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 9-5

Component physical part is released in Teamcenter

Re-import as-built structure behavior

When you re-import an as-built structure into Teamcenter from a third-party system, be aware of the
following behaviors:

• Re-import after physical part is added to as-built structure on third-party system.

As the following figure shows, when the third-party as-built structure is re-imported with the newly
added physical part Pump #300, the additional part is imported into Teamcenter.

9-6 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Re-import into Teamcenter with additional physical part

• Re-import after physical part is deleted from as-built structure on 3rd party system.
As the following figure shows, when the third-party as-built structure Aircraft #100 is re-imported to
Teamcenter with the physical part Pump #300 removed, the physical part is not removed on
Teamcenter.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 9-7

Re-import into Teamcenter with physical part removed

Managing As-Built Manager data for Multi-Site Collaboration

Using Multi-Site Collaboration, you can share As-Built Manager data between multiple Teamcenter sites.
Each Teamcenter site has its own independent database with its own set of users and groups, data
model, business rules, and business processes.

Data sharing is done through object replication where an exact copy of an object is made at a remote
site using remote export and import functions. The replicas are synchronized when the master copy is
modified.

9-8 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

The Object Directory Services server (ODS) site maintains a record of each object in the entire Multi-Site
Collaboration network.

The Integrated Distributed Services Manager (IDSM) provides the mechanism used to export an object
from the owning site, transmit it over the network, and import it into the destination site.

Multi-Site Collaboration support for as-built structures

When you export as-built structures and related As-Built Manager data using Multi-Site Collaboration,
Data Exchange also exports the relations and the related objects. The table summarizes which relations
and corresponding related objects are exported for each As-Built Manager object and whether the
related object is optional or required.

Exported As-Built Manager Exported related Optional or

object Exported relation object required

Item IMAN references Part logistics form Optional

Has characteristics Characteristic Optional

definitions

Physical part Physical Characteristic Required

characteristics values

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 9-9

Exported As-Built Manager Exported related Optional or

object Exported relation object required

Physical part Optional

revision (by
creation date)

Allowed deviation Physical Part Required

(Child)

Contains Asset group Required

Physical part in Physical location Required

location

Disposition Disposition Required

applicability

Allowed deviation Tag Deviation Required

document

Physical part revision Tag Physical part Required

Physical realization Item revision Optional

Physical context Structure context Required

Tag Lot Required

As-built structure Physical part Optional

Physical structure Physical structure Occurrence Optional

alignment

Lot Tag Item Required

Physical location Physical location Optional

revision by
creation date

Physical location revision Tag Physical location Required

As-built structure Physical location Optional

As-Built Manager actions on stub and replica objects

Data sharing in Multi-Site Collaboration is done by replicating objects to remote databases through
export and import functions. In addition, during Multi-Site Collaboration import, Teamcenter uses the
persistent object model (POM) to create stubs for all referenced instances on the object. The following
table shows the As-Built Manager actions that can be performed on object replicas and stubs.

9-10 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

Actions Stub Replica Exceptions

Name occurrence No No

Create lot No Yes

Create serial number No No

generator

Generate as-built structure No Yes If any stubs are found in the neutral
structure during generation, the action
exits and does not process any partial
structures.

Install physical part No No

Uninstall physical part No No

Setup deviation No No

Assign lot No No

Compare No Yes The compared structures should not

have any stubs.

Visualization No Yes Visualization is not supported for stubs

within the neutral or physical structures.

Display as-built structure Yes Yes Stubs are displayed as remote lines.
Structures below stubs are not
displayed.

Release physical structure No Yes Structure must be transferred with

ownership.

Where installed No Yes

DEFAULT PROTECTION SCOPE

Site preference.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 A-7

A-8 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

B-10 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

ManufacturingIdCharsForPhysicalPartIdPref
DESCRIPTION

Specifies the number of characters to use from the manufacturing ID when generating the physical part
item ID. The physical part item ID is a combination of characters from part number, serial number, and
manufacturing ID properties. The total number of characters for the physical part item ID should not
exceed 128 characters. The first entry in the preference is the number of characters to use from the
manufacturing ID property for the physical part item ID. The second entry in the preference indicates
whether to use the characters from the beginning of the manufacturing ID (a value of 0) or from the end
of the part number (a value of 1).

If this preference is not found, the last 40 characters of the manufacturing ID are used.

VALID VALUES

Any positive integers.

DEFAULT VALUES

40
1

DEFAULT PROTECTION SCOPE

Site preference.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 B-11

MROAlternateColorPref
DESCRIPTION

Specifies the color to use when displaying an alternate physical part.

Determines the registration of the summary style sheet for part logistics form objects.

VALID VALUES

Accepts a string as a value. Each string must be a valid style sheet dataset object name.

DEFAULT VALUES

PartLogisticsFormSummary

DEFAULT PROTECTION SCOPE

Site preference.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 B-17

PartNumberCharsForPhysicalPartIdPref
DESCRIPTION

Specifies the number of characters to use from the part number when generating the physical part item
ID. The physical part item ID is a combination of characters from part number, serial number, and
manufacturing ID properties. The total number of characters for the physical part item ID should not
exceed 128 characters. The first entry in the preference is the number of characters to use from the part
number property for the physical part item ID. The second entry in the preference indicates whether to
use the characters from the beginning of the part number (a value of 0) or from the end of the part
number (a value of 1).

If this preference is not found, the last 40 characters of the part number are used.

VALID VALUES

Any positive integers.

DEFAULT VALUES

40
1

DEFAULT PROTECTION SCOPE

Site preference.

B-18 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

PhysicalContext_relation_primary
DESCRIPTION

Site preference.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 B-23

PhysicalPart.SUMMARYRENDERING
DESCRIPTION

Determines the registration for the physical part object's summary style sheet.

VALID VALUES

Accepts a single string as a value, which must be a valid dataset name.

DEFAULT VALUES

PhysicalPartSummary

DEFAULT PROTECTION SCOPE

Site preference.

B-24 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

PhysicalPartRevision_DefaultChildProperties
DESCRIPTION

Determines the properties that can be used as children for the indicated type.

VALID VALUES

Accepts one or more stings as values. Each string must be a valid Teamcenter relation object.

DEFAULT VALUES

PhysicalContext
PhysicalRealization

DEFAULT PROTECTION SCOPE

util_time_since_repair
util_time_since_overhaul

DEFAULT PROTECTION SCOPE

Site preference.

B-32 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
C. Glossary
A
as-built structure
Physical asset structure representing the neutral structure that it was realized from. The as-built
structure is a precise structure that represents the physical asset structure at the as-built phase and does
not retain date or time evolution history.

assembly
Single-level compound object as distinct from a multilevel product structure or bill of material, which is a
hierarchy of assemblies. Assembly data is stored in a BOM view revision.

B
BOM
Bill of materials.

• 100% BOM
The as sold product configuration, for example, the configuration of a car to be built and shipped to
the dealer.

• 120% BOM
Partial overlay of selected variant conditions. You cannot build the product from a 120% BOM.

• 150% BOM
Overlays of all possible variant configurations. You cannot build the product from a 150% BOM.

BOM view revision (BVR)

Workspace object that stores the single-level assembly structure of an item revision. Access can be
controlled on the structure (BOM view revision) independently of other data. BOM view revisions are
meaningful only in the context of the item revisions for which they are created.

BVR
See BOM view revision (BVR).

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 C-1

C
collaboration context
Teamcenter object that holds a collection of data contained in structure and configurator contexts. This
data allows you to capture multiple different Teamcenter structures in one container. You can open a
collaboration context in the Multi-Structure Manager application, in Manufacturing Process Planner, or
in Part Planner. You can also use a collaboration context to collect data to share with a third-party
application. See also structure context.

configuration rule
Rule that configures a structure. There are two kinds of configuration rules: revision rule and variant
rule.

D
design bill of materials
List of components and subassemblies used to define an assembly structure, and the representation of
the assembly structure. Compare with manufacturing bill of materials.

deviated physical part

Physical part installed in a physical structure that is not the preferred part or designated as a valid
alternate or substitute to the preferred part.

deviation document
Document that authorizes the installation of a physical part that is a deviation from the design structure.

deviation workflow
Process flow, reviewer’s list, and business validations required to route a deviation document for review
and approval.

E
end item
Top-level node of an assembly that can represent a product or a factory structure.

F
find number
Number that identifies individual occurrences (or groups of occurrences) within a single-level assembly.
Components are ordered by find number within an assembly.

C-2 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
G
global alternate
Alternate that is interchangeable with another part, regardless of where the part is used in the product
structure. A global alternate applies to any revision of the part and is independent of views.

I
item
Workspace object generally used to represent a product, part, or component. Items can contain other
workspace objects including other items and object folders.

L
lot
Group of physical parts controlled by the same number. A lot number is similar to a serial number. The
difference between the two is that the same lot number can identify multiple physical parts, but no
more than the total number of physical parts specified by the lot size.

lot part
Physical part or assembly identified by a lot number.

M
manufacturing bill of materials
Defines how the product is manufactured, rather than how it is designed. Compare with design bill of
materials.

N
neutral part
Item defined in the neutral structure representing a part definition. It can be a part object or any other
item type configured as a valid neutral item type in the Business Modeler IDE.

neutral structure
Hierarchy of neutral parts representing the asset-independent product definition structure, such as the
manufacturing or design structure.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 C-3

O
occurrence
Hierarchical structure relationship between the immediate parent assembly and its child component
item or item revision in a precise assembly. Sometimes called relative occurrence.

occurrence group
Collection of occurrences and absolute occurrences in the BOM. An occurrence group typically
represents an assembly.

occurrence path
Representation of the path from a top-level assembly to an occurrence of a component or subassembly.
An occurrence path is unique to the context of a specific BOM; different BOMs cannot contain the same
occurrence paths. The occurrence path does not change if the configuration of the BOM changes.

override list
Item revisions in a workspace folder that is referenced from a revision rule. The item revisions in the
folder override the revision that would otherwise be loaded by the revision rule.

P
part logistics data
Information added to the neutral part that supports the realization of physical parts in as-built or as-
maintained representations of the product. For example, part logistics data determines whether the part
is traceable, serialized, or lot. Part logistics data is added to each neutral part using the Part Logistics
Form.

physical part
Representation of a built or manufactured physical asset realized from the neutral part. The physical part
captures asset information such as its serial number, manufacturer ID, and lot number. It also inherits
the part number from the neutral part from which it is realized.

physical realization
Relation between a physical part and the neutral part revision that it was realized from.

physical structure
Approved product structure that includes part information.

product structure
Hierarchy of assembly parts and component parts with a geometric relationship between them, for
example, a bill of materials (BOM). Variant and revision rules define the generic BOM. This BOM can
then be loaded to display the configured variant.

C-4 PLM00124 13.0 As-Built Manager, Teamcenter 13.0

© 2020 Siemens
product view
Saved configuration of the assembly viewer, including the selection of objects, zoom factor, rotation
angle, and pan displacements.

properties
Keys and values that specify the configuration settings for an application in the Teamcenter rich client.

R
release status
Status associated with a workspace object when it is released through a workflow process.

revision rule
Parameter set by the user that determines which revision of an item is used to configure product
context.

S
serialized part
Physical part or assembly identified by a serial number.

serial number generator

Number generator that can be configured on a neutral part to create serial numbers for every instance
of a physical part. You can set characteristics for the serial numbers, such as a prefix, a suffix, the
number increment, and the maximum number of characters in the serial number. During the
instantiation of the physical structure from the neutral structure, you can choose to automatically assign
the serial numbers to the newly created physical parts.

structure
Representation of multiple objects and their interdependencies. For example, a classification structure
represents classes and their inheritance dependencies, and an assembly structure represents how
components and subassemblies are associated to build up an assembly. The structure can be viewed in
several applications, including Structure Manager, Manufacturing Process Planner, Part Planner, Multi-
Structure Manager, and Resource Manager.
In Resource Manager, most structures are hierarchical. For example, they acquire the form of a tree
where each node can have only one parent but multiple siblings and children.

structure context
BOM or assembly structure contained in a collaboration context. The structure context can contain
occurrence groups, items, and item revisions. See also collaboration context.

substitute
Component that can be used interchangeably within an occurrence, typically for manufacturing
purposes. The preferred substitute is displayed in the structure.

As-Built Manager, Teamcenter 13.0 PLM00124 13.0 C-5

T
top level
Object at the root of a product structure where a process plan is being developed. The top level can be
either an end product being manufactured or a subassembly used in the end product (for example, an
engine for a tractor where the tractor is the end product).

U
usage
Occurrence property that defines the position that the physical part occupies within the as-built
structure.

V
view (Classification)
Tailored representation of attributes within a class. Views are associated with abstract and storage
classes. Attribute properties can also be applied. For example, a class may define the physical and
accounting attributes for its objects, but a view for tool designers may display only the physical
attributes, and a view for accountants may display only pricing and order number attributes.

view type
Attribute of a BOM view revision. The view type specifies the BOM view revision's intended use (for
example, design or manufacture). The view type distinguishes one BOM view revision from another
BOM view revision of the same item revision.

W
working revision
Revision that can be changed by a user with write privileges. No record of intermediate states of a
working revision is maintained by Teamcenter.

C-6 PLM00124 13.0 As-Built Manager, 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.

Multi Step Nonlinear
No ratings yet
Multi Step Nonlinear
624 pages
Easy Plan
No ratings yet
Easy Plan
470 pages
Dbom Ebom Alignment Usage
No ratings yet
Dbom Ebom Alignment Usage
60 pages
A320 - Amm - 01-Feb-2023 - List of Abbreviations
No ratings yet
A320 - Amm - 01-Feb-2023 - List of Abbreviations
94 pages
Questa Sim Ref
No ratings yet
Questa Sim Ref
1,166 pages
ASME Y14.36 2018 Uufajf
No ratings yet
ASME Y14.36 2018 Uufajf
22 pages
Teamcenter Gateway For Enterprise Applications - Active Workspace Add-Ons Installation and Setup Guide
No ratings yet
Teamcenter Gateway For Enterprise Applications - Active Workspace Add-Ons Installation and Setup Guide
141 pages
Process Simulate On Teamcenter
No ratings yet
Process Simulate On Teamcenter
2,745 pages
Teamcenter Gateway For Enterprise Applications - Connectivity Guide
No ratings yet
Teamcenter Gateway For Enterprise Applications - Connectivity Guide
85 pages
Concept of Operations Concept of Operations
No ratings yet
Concept of Operations Concept of Operations
154 pages
VPM A320 USER Guide
No ratings yet
VPM A320 USER Guide
251 pages
ENOVIA CompatibilityMatrix-2022x
No ratings yet
ENOVIA CompatibilityMatrix-2022x
162 pages
Aerospace Defense On Rich Client
No ratings yet
Aerospace Defense On Rich Client
234 pages
Basic Nonlinear Analysis User's Guide 2024
No ratings yet
Basic Nonlinear Analysis User's Guide 2024
157 pages
Getting Started With Customization
No ratings yet
Getting Started With Customization
14 pages
Design Bom Alignment Admin
No ratings yet
Design Bom Alignment Admin
92 pages
Oracle: Question & Answers
No ratings yet
Oracle: Question & Answers
22 pages
3DX Platform Training V0.1
No ratings yet
3DX Platform Training V0.1
114 pages
Control Plan 1
No ratings yet
Control Plan 1
112 pages
Designs and Structure Management
No ratings yet
Designs and Structure Management
155 pages
Odata Api Framework
No ratings yet
Odata Api Framework
84 pages
Clearancedb Admin Guide
No ratings yet
Clearancedb Admin Guide
275 pages
Administrator and User Help
No ratings yet
Administrator and User Help
2,462 pages
Classification
No ratings yet
Classification
90 pages
Managing Preferences
No ratings yet
Managing Preferences
28 pages
Apqp On Program Planning 1
No ratings yet
Apqp On Program Planning 1
32 pages
Configuration and Extensibility
No ratings yet
Configuration and Extensibility
456 pages
Consumer Packaged Goods Install Config
No ratings yet
Consumer Packaged Goods Install Config
28 pages
Structure Discovery Admin
No ratings yet
Structure Discovery Admin
58 pages
(ENG) Product Structure Definition
No ratings yet
(ENG) Product Structure Definition
45 pages
As Built Manager
No ratings yet
As Built Manager
141 pages
DevOps Master Program PDF
0% (1)
DevOps Master Program PDF
5 pages
Ecad - Viewer
No ratings yet
Ecad - Viewer
126 pages
As Built Manager
No ratings yet
As Built Manager
156 pages
Customizing Solidworks
100% (1)
Customizing Solidworks
60 pages
Designs and Structure Management
No ratings yet
Designs and Structure Management
120 pages
As Built Manager
No ratings yet
As Built Manager
154 pages
Mega - Manual de Mantenimiento
No ratings yet
Mega - Manual de Mantenimiento
70 pages
Gs - Product - Visualization
No ratings yet
Gs - Product - Visualization
288 pages
CATIA Composites: 3DEXPERIENCE® R2019x
No ratings yet
CATIA Composites: 3DEXPERIENCE® R2019x
51 pages
GB3098 13
No ratings yet
GB3098 13
5 pages
Service Manager PDF
No ratings yet
Service Manager PDF
221 pages
Design Assistant PDF
No ratings yet
Design Assistant PDF
4 pages
Client For Ms Office
No ratings yet
Client For Ms Office
136 pages
Use Design Assistant
No ratings yet
Use Design Assistant
8 pages
Deploying Document Management
No ratings yet
Deploying Document Management
112 pages
Aerospace and Defense Install Config
No ratings yet
Aerospace and Defense Install Config
26 pages
DS WhitePapers Concurrent Engineering With 3DEXPERIENCE
No ratings yet
DS WhitePapers Concurrent Engineering With 3DEXPERIENCE
34 pages
3DXML User Guide
No ratings yet
3DXML User Guide
82 pages
SmarTeam-Epdm Migration Tools 21nov2016 v1
No ratings yet
SmarTeam-Epdm Migration Tools 21nov2016 v1
13 pages
Sap Gui PDF
No ratings yet
Sap Gui PDF
9 pages
BP 2009 Metro Availability PDF
No ratings yet
BP 2009 Metro Availability PDF
66 pages
PhotoView 360 Tutorial 2011
No ratings yet
PhotoView 360 Tutorial 2011
8 pages
87 Eng
No ratings yet
87 Eng
35 pages
NAS 808 Standard
No ratings yet
NAS 808 Standard
6 pages
Brochure Wiring Harness Engineering Solutions
No ratings yet
Brochure Wiring Harness Engineering Solutions
12 pages
Part Design 2019x
No ratings yet
Part Design 2019x
28 pages
044-05393 OM Online Software Manual Rev B
100% (1)
044-05393 OM Online Software Manual Rev B
238 pages
NX WAVE Geometry Linker
No ratings yet
NX WAVE Geometry Linker
13 pages
Red Hat OpenStack Platform-11-High Availability For Compute Instances-En-US
No ratings yet
Red Hat OpenStack Platform-11-High Availability For Compute Instances-En-US
14 pages
Simulia 3dorchestrate: Windows/Derby On Premises Installation
No ratings yet
Simulia 3dorchestrate: Windows/Derby On Premises Installation
30 pages
4.3-4 Run Diagnostic
No ratings yet
4.3-4 Run Diagnostic
42 pages
Bash Made Easy - A Beginners Handbook To Easily Learn Bash, 2021
No ratings yet
Bash Made Easy - A Beginners Handbook To Easily Learn Bash, 2021
440 pages
Solidworks Bubu Stool Tutorial
No ratings yet
Solidworks Bubu Stool Tutorial
33 pages
Sketcher: Airbus Industrie Manual
No ratings yet
Sketcher: Airbus Industrie Manual
10 pages
Developers Guide
No ratings yet
Developers Guide
29 pages
Program Planning
No ratings yet
Program Planning
160 pages
Oracle GoldenGate 11gr2 IE and Oracle DG - Switchover-Fail-over Ops v1.1-ID1436913.1
No ratings yet
Oracle GoldenGate 11gr2 IE and Oracle DG - Switchover-Fail-over Ops v1.1-ID1436913.1
24 pages
Clearance - DB - Admin
No ratings yet
Clearance - DB - Admin
260 pages
In This Solidworks Tutorial, You Will Create Helical Gear
No ratings yet
In This Solidworks Tutorial, You Will Create Helical Gear
11 pages
Designcontext
No ratings yet
Designcontext
52 pages
Catia v5
No ratings yet
Catia v5
35 pages
Assembly Arrangements With Unigraphics NX2
No ratings yet
Assembly Arrangements With Unigraphics NX2
13 pages
Dec30023 Computer Networking Fundamentals Pw2
No ratings yet
Dec30023 Computer Networking Fundamentals Pw2
16 pages
AP2080 Main Module
No ratings yet
AP2080 Main Module
11 pages
BZ 8002953
No ratings yet
BZ 8002953
15 pages
How To Use Epsilon
No ratings yet
How To Use Epsilon
22 pages
Service - Manager
No ratings yet
Service - Manager
256 pages
Content MGMT
No ratings yet
Content MGMT
286 pages
Fortianalyzer v6.4.2 Upgrade Guide
No ratings yet
Fortianalyzer v6.4.2 Upgrade Guide
26 pages
Service - Planner
No ratings yet
Service - Planner
192 pages
HUAWEI GRA-L09C432B317 Software Upgrade Guideline
No ratings yet
HUAWEI GRA-L09C432B317 Software Upgrade Guideline
9 pages
Upgrade Assistant in Teamcenter 14
No ratings yet
Upgrade Assistant in Teamcenter 14
4 pages
Gs - Customization
No ratings yet
Gs - Customization
12 pages
DPV Tutorial
No ratings yet
DPV Tutorial
36 pages
Service - Execution
No ratings yet
Service - Execution
148 pages
Clearancedb Admin Guide
No ratings yet
Clearancedb Admin Guide
220 pages
DDB - DOS Batch File Tutorial PDF
No ratings yet
DDB - DOS Batch File Tutorial PDF
13 pages
An Introduction To The C SHELL
No ratings yet
An Introduction To The C SHELL
43 pages
Data Share Manager
No ratings yet
Data Share Manager
36 pages
Configuring Shared Resources: This Lab Contains The Following Exercises and Activities
No ratings yet
Configuring Shared Resources: This Lab Contains The Following Exercises and Activities
8 pages
Village Finder - Minecraft App
No ratings yet
Village Finder - Minecraft App
1 page
T1 7.0 SD-Card Upgrade User Guide: Huawei Technologies Co., LTD
No ratings yet
T1 7.0 SD-Card Upgrade User Guide: Huawei Technologies Co., LTD
8 pages
Print Provider
No ratings yet
Print Provider
5 pages
Dispatcher Install and Configure
No ratings yet
Dispatcher Install and Configure
106 pages
Phstat2 Version 2.8.1 Readme
No ratings yet
Phstat2 Version 2.8.1 Readme
5 pages
How To Test BLE Adapters
No ratings yet
How To Test BLE Adapters
7 pages
Blackboard Web Services: Lance Neumann, Senior Software Architect, Blackboard Inc
No ratings yet
Blackboard Web Services: Lance Neumann, Senior Software Architect, Blackboard Inc
19 pages
Cacheless Search Deployment
No ratings yet
Cacheless Search Deployment
52 pages
Manufacturing Based On Feature Recognition Using N
No ratings yet
Manufacturing Based On Feature Recognition Using N
6 pages
Game Crash
No ratings yet
Game Crash
52 pages
Rman
No ratings yet
Rman
3 pages
GSIS User Manual V2.12
No ratings yet
GSIS User Manual V2.12
88 pages
Netmeeting - User Guide: 1. To Host A Meeting
No ratings yet
Netmeeting - User Guide: 1. To Host A Meeting
11 pages
Command Prompt - 11 Basic Commands You Should Know (CD, Dir, Mkdir, Etc.)
No ratings yet
Command Prompt - 11 Basic Commands You Should Know (CD, Dir, Mkdir, Etc.)
3 pages
Ebook Cloud Landscape and Smart Platform Decisions
No ratings yet
Ebook Cloud Landscape and Smart Platform Decisions
16 pages
JT2Go Desktop Frequently Asked Questions
No ratings yet
JT2Go Desktop Frequently Asked Questions
6 pages
Lib Burst Generated
No ratings yet
Lib Burst Generated
2 pages
Smart Browser - Help Guide
No ratings yet
Smart Browser - Help Guide
8 pages
SolidWorks Simulation 2023 Black Book
From Everand
SolidWorks Simulation 2023 Black Book
Gaurav Verma
No ratings yet