Service - Manager
Service - Manager
Service Manager
PLM00170 - 13.0
Contents
Glossary B-1
• Create the as-maintained physical product instantiation for any configured product definition
structure.
• Store and manage additional information about the as-maintained physical part structure that is not
tracked on the product definition structure, such as serial numbers and lot numbers.
• Reconcile the as-maintained structure with a configured product definition structure to identify parts
that are missing, alternates, substitutes, or deviations.
• Manually update the as-maintained structure with changes that occur over the lifetime of the physical
asset.
• Compare the as-maintained structure to the product definition structure or to another as-maintained
structure.
• View the as-designed product structure and the as-maintained physical structure configuration side-
by-side or by using the embedded viewer available in the rich client.
Service Event Management is a separately licensed extension of the Service Manager application that
allows you to manage service events that affect the as-maintained configuration. You can use Service
Manager with the Service Event Management extension to:
• Define service group structures to efficiently identify maintenance events that have occurred on an
asset.
• Record service events, such as an inspection, overhaul, repair, or other type of service.
• Maintain service history by recording service event data such as work scope, approval, resource
information, maintenance times, and cost.
• Record and track part discrepancies and failures and the associated corrective action service events.
• Record part movement transactions such as install, uninstall, and replace for both tracked and
nontracked parts.
• Record utilization information (life, date, and observation characteristic values) on service events and
apply these values to the as-maintained structure upon approval of these service events.
• Apply configuration updates to the as-maintained structure driven by approved service events.
Enable Service Manager Service Manager does not need to be enabled before you use
it, but you must select the appropriate components during
installation.
If you have trouble accessing Service Manager, see your
system administrator; it may be a licensing issue. The Service
Manager application (as-maintained management) and the
Service Event Management extension each require separate
licenses in addition to the standard Teamcenter product
license.
Configure Service Manager There are additional steps you must perform to configure
Service Manager before you can use it.
2 Service Editor pane Allows you to view data about the selected line. To display
a different data pane, click its tab.
3 Service details and utilization Allows you to view the service details and utilization for the
pane selected line.
4 Physical part and disposition Allows you to view the physical part and disposition history
history pane for the selected line.
Service Manager uses the Teamcenter rich client interface and provides the Service Editor view. The
interface items for Service Manager are described in the Service Manager menus, buttons, and symbols
topics.
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.
File menu
Command Description
New → Life Characteristic Creates a new life characteristic for a neutral part.
New → Date Characteristic Creates a new date characteristic for a neutral part.
Note:
This menu command is available only if the Service Event
Management extension for Service Manager is installed
and licensed.
Note:
This menu command is available only if the Service Event
Management extension for Service Manager is installed
and licensed.
Command Description
Note:
This menu command is available only if the Service Event
Management extension for Service Manager is installed
and licensed.
Note:
This menu command is available only if the Service Event
Management extension for Service Manager is installed
and licensed.
Note:
This menu command is available only if the Service Event
Management extension for Service Manager is installed
and licensed.
Note:
This menu command is available only if the Service Event
Management extension for Service Manager is installed
and licensed.
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.
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.
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 Service Manager.
Toggle In-Context Mode Enables or disables editing in context mode, allowing creation of
absolute occurrences for the selected assembly.
View menu
Command Description
Refresh (F5) Updates the information displayed for a selected line and all of
its children.
Show Data Panel Shows or hides the data pane containing, for example,
properties data or the embedded viewer.
Show/Hide Second Structure Shows or hides a second structure pane below the first. You can
Panel set the size of each structure pane by moving the horizontal split
bar between the panes. If the second structure pane is
displayed, this command hides the lower pane.
Command Description
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.
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.
Note:
This command does not automatically refresh. Any
changes to the assigned objects are not reflected in the
structure until you run this command again.
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 → 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.
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.
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 → Count Modules Counts the modules defined for the selected variant structure.
Command Description
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 → From PLMXML Imports objects in the PLMXML format to your Teamcenter
database.
Rebase Physical Part Updates the physical part to the latest design of the neutral
structure.
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.
Install Physical Part Adds or installs a copied physical part into the current as-
maintained structure.
Uninstall Physical Part Uninstalls and removes the selected lines from the as-
maintained structure completely and does not place them on
the clipboard.
Command Description
Replace Physical Part Replaces a selected physical part in the current as-maintained
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.
Show Top Physical Part Displays the top-most physical part parent for the selected
physical part.
Change Disposition Changes the state of a physical part. These states are classified
as operational or nonoperational.
Move From Cuts the selected physical part from the current physical
location and places it on the clipboard.
Move To Moves the physical part from the current physical location into
the selected physical location.
Show Physical Part Usage History Displays the physical part usage history for the selected physical
part.
Show Disposition History Displays the history of disposition states for the selected
physical part.
Show Utilization Displays the utilization information for the selected physical
part.
Show Log Entries Displays the log entries for the selected physical part.
Generate As-Built Structure Generates an as-built structure from the selected as-maintained
structure.
Name Occurrence Assigns a name to the occurrence for the selected neutral part
using the predefined naming rules.
Set Preferred Location Sets the selected physical location as the preferred location.
Unset Preferred Location Changes the selected physical location so that it is no longer the
preferred location.
Show Contains View Displays the physical parts contained in the selected physical
location or the selected asset group.
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 add buttons to the
toolbars, they are displayed in future sessions. Consider adding buttons that:
• 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 Service Manager structure
pane.
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.
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
structure pane set 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 untraced parts Shows or hides the neutral parts that are not traceable in
the physical structure.
Button Purpose
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 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.
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.
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.
Setup deviation Opens the Setup Deviation wizard. Use the Setup
Deviation wizard to search for a deviation document to
associate to the physical part.
Install physical part Adds or installs a copied physical part into the current as-
maintained structure.
Replace physical part Replaces a selected physical part in the current as-
maintained structure with a copied part.
Button Purpose
Uninstall physical part Uninstalls and removes the selected lines from the as-
maintained structure completely and does not place them
on the clipboard.
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 Service Manager structure
navigation tree pane.
Most recently used Shows a list of your most recently accessed structures. If
(MRU) list you select an entry from the list, Service 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 structure context Browses for and opens a specific structure context by
by name 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.
Manage global Shows a list of the global alternates available for the
alternates selected line. You can add alternates and select a
preferred alternate. The preferred global alternate is
indicated by an asterisk.
The following symbols are displayed at the bottom right corner of the product structure pane and
show the current status of the selected line.
Button Purpose
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.
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 Service Manager, you should be familiar with the Teamcenter elements that
are used to define and present product structure and how to manage multiple product views. Product
structures are not created or modified in Service Manager, but these structures are used as the
definition for the as-maintained structure.
Element Description
Characteristics definition Information related to a neutral part that is important for service
organizations maintaining assets. You can create characteristic
definitions that contain information to be measured against the
physical part, such as how long a product has been in use. You can
also create characteristic definitions that contain data to be
measured against a physical part, such as temperature or oil
pressure.
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.
Element Description
Log book A collection of log entries recorded against a specific physical asset. A
physical asset may have more than one associated log book.
Log entry A record of data collected about a physical asset and recorded by a
certain person at a certain time. The log entry is associated to a
single asset but may record characteristic values for several
components within that asset.
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.
Part logistics data Information added to the neutral part that will support the realization
of physical parts in Service Manager 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 location An area where physical parts are stored. A location can be a site,
region, inventory, customer, contractor, or shop.
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
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.
Element Description
Usage Defines the position that the physical part occupies within the as-
maintained structure.
Service event management is available only if you have installed and obtained the proper license for the
Service Event Management extension for Service Manager.
Element Description
Activity entry value A characteristic definition value logged to a service event to capture
life, date, or observation characteristics for the associated physical
part. Characteristic definitions are defined on the neutral structure.
Service event Informational data that is captured as a result of service activity that
is performed by an external source.
• MRO Lot
• MRO Observation Characteristics
• MRO Physical Location
• MRO Physical Part
• MRO Serial Number Generator
• MRO Service Discrepancy
• MRO Service Event
• MRO Service Group
• MRO Service Group and Event
1. Choose Advanced from the quick Search menu at the top of the navigation pane.
4. Under System Defined Searches, select the object you want to search for.
5. Click OK.
6. Type the values for the object properties that you want to search for.
1. Configuring Service Manager by setting global and business object constants, LOVs, and
preferences.
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 or Rich
Client 4–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, expand Service Lifecycle Management and select from
the following features.
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
Service Event Management Installs the Service Event Management templates. This
template is available only if you have purchased and have
a license for Service Event Management.
As-Built and As-Maintained Installs the template for the operability functionality
Alignment between the As-Built Management and As-Maintained
Management applications. This template is available only
if you have purchased and have a license for As-Built
Management and As-Maintained Management.
5. Click Next.
• Global and property constants that control part logistics information, define part usage properties,
and set a default disposition.
• Business object constants that identify neutral item types and physical part types.
• Lists of values (LOVs) that define physical location types, deviation authority documents, and status
lists. The Service Event Management extension for Service Manager also provides LOVs to define
service information, such as type of service, severity of a service discrepancy, and the new neutral
part class to use when creating a part movement.
• Workflows.
Note:
As a best practice, use command suppression to limit the use of the rebase command to Service
Lifecycle Management super users.
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-
Maintained Management, Service Event Management, or another template. You must deploy the
custom template after making the changes.
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 a custom template that you define. You must deploy
the custom template after making the changes.
• 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.
• PhysicalPartDefaultDisposition
Set this value to the default disposition for physical parts.
• 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.
• InitialValue
Set this value to set the defaults for the properties of the part logistics form.
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.
AutoCreatePartLogisticsForm True
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.
As an administrator, you can set the PartLogisticsFormNamePrefix global constant to a prefix that is
used for part logistics form names.
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.
PartLogisticsFormNamePrefix NULL
Example:
You may want to set the PhysicalPartDefaultDisposition global constant to In-Repair.
PhysicalPartDefaultDisposition In-Service
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-maintained 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.
• occurrence_name
• ref_designator
• seq_no
Note:
The seq_no property corresponds to the value for the Find No. property in the Service Manager
interface.
UsageAttributeName occurrence_name
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.
ReuseAuthorizedDeviation True
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.
You use the Business Modeler IDE to configure the business object constants in a custom template that
you define. You must deploy the custom template after making the changes.
• 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.
As an administrator, you can set the IsMRONeutralType business object constant to true to configure
which items are defined as neutral items. Physical parts are only generated from neutral items.
Example:
Because IsMRONeutralType is false for the document business object, physical parts cannot be
generated from documents.
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 a create 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-maintained
structure is generated.
As an administrator, you can set LOVs located in the LOV folder in the Extensions view in the Business
Modeler IDE. 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.
Additional LOVs are also available in the Service Event Management template available with the
Service Event Management extension for Service Manager. The Service Event Management extension
for Service Manager is a separately-licensed option.
If you have installed the Service Event Management extension for Service Manager and have obtained
the appropriate license, you can configure the following Service Event Management LOVs:
• sem_inspection_types
Set this list of values to define the type of inspection performed on a physical part.
• sem_overhaul_types
Set this list of values to define the type of overhaul performed on a physical part.
• sem_repair_types
Set this list of values to define the type of repair performed on a physical part.
• sem_other_types
Set this list of values to define the type of work performed on a physical part that is not an
inspection, overhaul, or repair.
• MRO Severity
Set this list of values to define service discrepancy severity levels.
As an administrator, you can set the MRO Valid Deviation Status List LOV to the list of status values
needed on the deviation authority to validate the authorized installation of a deviated part. The deviated
authority item must be at the approved status before a deviated physical part can be installed.
Example:
You may want to include an additional status value such as Complete to validate a deviation.
MRO Valid Specifies the list of status values needed on TCM Released
Deviation the deviation authority to validate the
Status List authorized installation of a deviated part.
As an administrator, you can set the MRO Deviation Authority List LOV to the list of item classes used
to authorize a deviation.
Example:
You may want to use a manufacturing document in addition to a deviation document to authorize
deviations. If you have installed Service Event Management, ServiceEvent is a valid deviation
authority.
As an administrator, you can set the Physical Location Type LOV to a list of valid physical location types
that are used when creating a physical location.
Example:
You may want to add a physical location type called Warehouse to represent physical parts stored
in a warehouse.
The MRO Transaction Type LOV is an uneditable list of valid types of service performed on a physical
part. The service types, Inspection, Overhaul, Other, and Repair, are available as default values for this
LOV. You can define more specific types within these categories using the sem_inspection_type,
sem_other_type, sem_overhaul_type, and sem_repair_type LOVs. The values for the MRO
Transaction Type LOV are available as Action Type when creating a service event.
Note:
The following LOVs are not available unless you have installed the Service Event Management
extension for Service Manager and have the appropriate license.
• Inspection type
As an administrator, you can set the sem_inspection_type LOV to define specific types of inspections
performed on a physical part.
• Other type
As an administrator, you can set the sem_other_type LOV to specify user-defined types of service,
other than inspection, overhaul, or repair, performed on a physical part. The sem_other_type LOV is a
subset of the MRO Transaction Type LOV.
• Overhaul type
As an administrator, you can set the sem_overhaul_type LOV to define specific types of overhaul
service performed on a physical part. The sem_overhaul_type LOV is a subset of the MRO
Transaction Type LOV.
• Repair type
As an administrator, you can set the sem_repair_type LOV to define specific types of repair service
performed on a physical part. The sem_repair_type LOV is a subset of the MRO Transaction Type
LOV.
As an administrator, you can set the MRO Severity LOV to a list of valid severity levels for a service
discrepancy.
Note:
The following LOV is not available unless you have installed the Service Event Management
extension for Service Manager and have the appropriate license.
As an administrator, you can set the MRO New Part Class LOV to a list of valid types of neutral part
classes to use when creating a part movement.
Note:
The following LOV is not available unless you have installed the Service Event Management
extension for Service Manager and have the appropriate license.
MRO New Part Class Specifies the type of neutral part Part
class to use when creating a new
part for tracking part movement.
The value used for this LOV must be
a valid SLM neutral part, so
• 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 workflow
The Release As-Maintained Structure workflow is provided with Service Manager. You can configure
this workflow or create your own to set up the process flow, reviewers, and business validations
required to release an as-maintained structure.
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.
• 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.
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.
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.
You must create the neutral structure before you can generate the as-maintained 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.
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.
Note:
A global alternate part does not require an authorized deviation when installed as an alternate
physical part in the as-maintained physical structure.
Note:
A substitute part does not require an authorized deviation when installed as a substitute physical
part in the as-maintained physical structure.
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.
• Creating and managing part logistics forms attached to the neutral part.
• 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.
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.
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.
Traceable Defines if a physical part will be generated from the neutral true
part.
Preserve Defines if one physical part with the quantity defined can false
Quantity represent a multi quantity neutral part.
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.
2. Locate the neutral part you want to create a part logistics form for.
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.
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.
To view the part logistics form properties using the Viewer pane:
1. From the tree pane or Details table, select the part logistics form that you want to display.
You edit part logistics data in Service 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 Service Manager:
• Serialized
• Traceable
• Lot
• Consumable
• Rotable
• Preserve Quantity
1. Open the neutral structure in the Service Editor view by one of the following methods:
• From the navigation pane, click Service Manager, then from the Service Editor 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 → Service Manager.
2. From the Service Editor view, select the BOM line containing the neutral part.
b. Double-click the cell containing the part logistics value and type the new value.
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.
2. From the Service Editor 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 Service Editor 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.
• 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.
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.
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-maintained 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.
2. From the Service Editor view, select the BOM line containing the neutral part.
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
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.
2. From the Service Editor view, select the BOM line containing the neutral part.
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
2. Right-click the desired serial number generator and select Set As Generic Serial Number
Generator.
2. Right-click any serial number generator and select Unset Generic Serial Number Generator.
Note:
Selecting a generic serial number generator that is already set makes the Unset As Generic
Serial Number Generator option available.
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.
2. From the Service Editor view, select the BOM line containing the neutral part.
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.
A characteristic definition is information related to a neutral part that is important for service
organizations maintaining mission critical assets. You can create characteristic definitions that contain
information such as how many hours a part has been used, the date the asset was put into commission,
or the operating temperature of the part.
As the following figure shows, you can create characteristic definitions that define life, date, and
observation characteristics for a physical part. You can also create derived characteristics which are
characteristics values that are calculated by the system based on formulas or expressions. Only life and
observation characteristics can be defined as derived characteristics by specifying the evaluation
expression.
The characteristic definitions must be assigned to the neutral part. The generated physical part inherits
the characteristic definitions that are used for recording utilizations.
be propagated throughout an entire physical structure providing the child physical parts share the
same life characteristic definitions.
A life characteristic defines the individual characteristics that measure the life of a physical part.
Example:
You may want to track the number of landings for an aircraft using a life characteristic. When the
number of landings reaches a specific value, scheduled maintenance on the aircraft is performed.
• Select a folder where you want to create the new life characteristic.
• Select one or more neutral parts from your home folder or from the Service Editor view where
you want to assign the life characteristic.
5. In the Derived Expression box, type the expression or formula for the derived characteristic or
click the button to use the wizard.
A date characteristic defines the a date when a specific action occurred on a physical part.
Example:
You may want to capture the commission date or warranty date of a physical part.
• Select a folder where you want to create the new date characteristic.
• Select one or more neutral parts from your home folder or from the Service Editor view where
you want to assign the date characteristic.
An observation characteristic defines the operational characteristics observed about a physical part.
Example:
You may want to record any cracks or record the operating temperature for a specific physical part.
When the gap distance or operating temperature exceed certain values, maintenance must be
performed.
• Select a folder where you want to create the new observation characteristic.
• Select one or more neutral parts from your home folder or from the Service Editor view where
you want to assign the observation characteristic.
5. In the Derived Expression box, type the expression or formula for the derived characteristic or
click the button to use the wizard.
Derived characteristics values are calculated by the system based on formulas or expressions. You can
use existing life or observation characteristics when you define the formula for the derived
characteristic.
Note:
Derived characteristics are not propagated.
Example:
An aircraft engine can have different life characteristics, such as in-flight usage and number of
landings, while in use. The actual life of the engine is a combination of these values based on
some predefined formulas. You can define a formula to calculate the derived life characteristic
value based on the two base life characteristic values that you provide. The derived life
characteristic value can then be used for calculating maintenance schedules.
2. Create a new life or observation characteristic and fill in the required fields.
Note:
If you want to use a life or observation characteristic in the formula for the derived
characteristic, you must create those characteristics before defining the derived
characteristic.
Characteristics Names of existing Click the button and select the life or
life or observation observation characteristic you want to
characteristics you use in the expression. Click Append to
wish to use in the append the characteristic definition in
formula for the the Derived Expression box.
derived expression.
4. Click OK to create the life or observation characteristic using the derived characteristic.
4. Select one or more neutral parts from your home folder or from the Service Editor view where you
want to assign the characteristic definition.
Note:
If you are in the Service Editor view, you can also choose Paste Characteristics to assign the
characteristics.
The characteristic definitions are related to the selected neutral parts, as shown below:
5. Click OK or Apply to change the characteristic definition properties. Alternatively, click Cancel to
exit.
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-maintained physical
structure evolves as the asset changes over time. This physical structure contains other traceable
physical parts that represent the subassemblies 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.
An imprecise structural relationship exists between the as-maintained assembly and the components.
The physical parts are related back to the neutral parts with a PhysicalRealization relation.
Note:
Physical parts with a green background in the as-maintained structure belong to a precise neutral
structure.
The following tasks are required steps before generating an as-maintained physical structure:
• Creating the neutral structure and populating the part logistics information assigned to the neutral
parts.
• Generate an as-maintained physical structure top down from the top-level neutral structure.
• Generate an as-maintained physical structure bottom up by installing physical parts at various levels
in the structure.
• 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.
Disposition types are classified as operational or nonoperational depending on the state of the physical
part. As an administrator, you define the disposition types for physical parts. For example, you may want
to create a operational disposition type called Issueable and a nonoperational disposition type called In-
Repair.
5. Select the Operational check box to specify the physical part is serviceable in the new disposition
state.
6. Select the Is Active check box to specify the disposition is an active disposition type and can be
used as a valid disposition type when generating an as-maintained structure.
7. Click OK to create the new disposition type. Alternatively, click Cancel to exit.
Emphasize the new In-Repair disposition is not an operational disposition since the operational check
box is not selected.
5. Click OK or Apply to change the disposition type properties. Alternatively, click Cancel to exit.
A physical location is an area where physical parts are stored. A location can be a site, region, inventory,
customer, contractor, or shop. Locations can be of various types and as an administrator, you define
location types based on your requirements. You can relate locations to one another because of their
structured nature. The locations are assigned to the physical parts when you create the as-maintained
structure. You must set preferred locations before generating the as-maintained physical structure.
The following location types are provided with the As-Maintained Management application:
• Contractor
• Customer
• In-Service
• Inventory
• Region
• Shop
• Site
You can define additional physical location types by configuring the Physical Location Type LOV.
You create physical locations and physical location structures according to your requirements and assign
the physical parts to the locations when creating the as-maintained structure. A location structure is
comprised of sublocations created in the context of a parent location.
You can optionally link a physical location to a defined company location. The physical location will
display the properties of the company location such as Street, City, and State.
Location Type The type of physical location Types are defined by the
(required). Physical Location Type LOV.
3. From the Service Editor view, click Open by Name to open the physical location where you
want to create the sublocation.
4. Select the physical location where you want to add the sublocation.
Location Type The type of physical location Types are defined by the
(required). Physical Location Type LOV.
Fort Chesternn
Fort Chester Shopnn sublocation
2. Select the company location you want to link to the physical location.
You must set a preferred location before generating the as-maintained physical structure. You can set
more than one preferred location.
b. From the Service Editor view, click Open by Name to open the physical location.
b. From the Service Editor view, click Open by Name to open the physical location.
Delete a location
Remove a location
3. Select the physical location structure where you want to remove a sublocation.
5. From the Service Editor view, select the physical sublocation line in the containing the parent
physical location.
2. Configure the neutral structure by setting revision rules and/or variant rules.
3. From the Service Editor view, select the top-level part from the neutral structure.
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 Time Installation date for physical Click the Set Date button
structure. The installation date and select a date from the
must be after the manufacturing calendar.
date.
Note:
If the
Disposition_Propagate_To_
Child preference is set to
true, the disposition is also
applied to the children parts
of the structure.
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-maintained physical structure that have defined serial
number generators. If you have defined a generic serial number generator, 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.
BH001–nn/MTrucknn–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
The Details pane appears at the bottom and displays the neutral structure and context information
used to generate the physical structure.
The properties of the neutral structure from which the physical structure is realized, are displayed.
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.
• 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.
• 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:
• 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.
2. Click Open by Name to open the as-maintained 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-Maintained Structure or right-click the physical part and choose
Duplicate As-Maintained Structure.
5. In the Duplicate As-Maintained Structure dialog box, enter the following information.
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.
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.
Location Name The location of the physical part. Alphanumeric (1–128 characters)
Note:
If the
Disposition_Propagate_To_Chi
ld preference is set to true, the
disposition is also applied to the
children parts of the structure.
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-maintained 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.
5. Click Set Date and select a date from the calendar when the as-maintained structure was
created.
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.
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.
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.
• Resolving missing parts by adding serial number, lot, or manufacturing information to the physical
part.
• Implementing deviations.
A physical part has the Parts Used column set to Missing for the following conditions:
• The lot number or serial number is missing for a serialized lot part.
• The child physical part has been uninstalled from the physical structure.
You can update a physical part using either Service Manager or My Teamcenter. The physical part
properties that can be updated are shown in the following table.
From My Teamcenter:
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.
5. To save and check in the modified properties, click Save and Check-In.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open By Name to open the physical structure or part.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure or part.
5. To add a serial number, double-click in the Serial Number column 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
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor 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 column and type the manufacturer
ID.
The manufacturer ID property is set for the physical part and the Part Used column is set to
Preferred.
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.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure or part.
4. Select the BOM line containing the physical part. Right-click and choose Assign Lot.
5. In the Assign Lot dialog box, select a lot number from the Lot Number list.
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 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.
Note:
You cannot install a physical part under a released physical part.
To install a physical part, you simply copy the physical part you want to install, navigate to the as-
maintained structure where you want to install the physical part, and install the copied physical part into
the as-maintained structure.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure or part you
want to install.
4. Choose one of the following methods to identify the physical part you want to install:
b. Select the physical structure where you want to install the 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 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 physical part. If the physical part is
an addition to the physical structure, select Extra to Design as the usage.
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 Install Physical Part on
the main toolbar at the top of the Service Manager pane.
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:
B. Click the Search tab and enter the following information you want to use as filters for
searching.
C. Click Find.
The results display the valid preferred, alternate, substitute and 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.
5. Click Set Date to set the installation date when the installation occurred.
6. 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.
If the installed Preferred part is a Preserve Quantity part, the quantity is checked against the
neutral structure.
• 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.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor 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.
The Uninstall Physical Part dialog box appears.
5. Click Set Date to set the uninstallation date when the uninstallation occurred.
6. Select the disposition value to set the disposition type for the uninstalled physical part.
7. Select the location name to set the physical location for the uninstalled physical part.
• If the quantities match, the physical part is uninstalled from the structure.
• If the quantity is less than allowed, the uninstallation is completed, and a missing part is
generated with the remaining quantity.
Note:
If the physical part to uninstall is set as Extra to Design, the uninstall action uninstalls the
selected physical part and removes the selected lines from the as-maintained structure
completely. Otherwise, the physical part is uninstalled and the Part Used is set to Missing.
BH012-nn/A Preferred
BH013-nn/A Preferred
BH014–nn/SHnn–001–A Preferred
BH020–nn/A Missing
• 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.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure where you
want to replace the physical part.
4. Choose one of the following methods to identify the physical part you want to use as the
replacement.
c. Right-click the physical part you want to replace and choose Replace Physical Part or click
Replace Physical Part on the main toolbar at the top of the Service Manager pane.
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
Replace Physical Part on the main toolbar at the top of the Service Manager pane.
b. Perform the following steps to search for the physical part that will be used as the
replacement.
B. Click the Search tab and enter the following information you want to use as filters for
searching.
C. Click Find.
The results display the valid preferred, alternate, substitute, and deviated physical
parts that can be used to replace the physical part.
D. Select the physical part from the results and click OK.
The Replace Physical Part dialog box reappears with the To be Installed Physical
Part field set to the selected physical part.
5. Click Set Date to set the replacement date when the replacement occurred.
6. Select the disposition value to set the disposition type for the replaced physical part.
7. Select the location name to set the physical location for the replaced physical part.
If the installed Preferred part is a Preserve Quantity part, the quantity is checked against the neutral
structure.
• 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.
Note:
The physical part must have a Released status before you can rebase it.
• If the component exists in the rebased neutral structure, the rebased physical part is assigned the
same usage as specified in the neutral structure.
• 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.
A rebase can be performed on any level within the physical and corresponding neutral structure.
However, the following two rebase scenarios cause a warning message to be displayed, although you
can proceed with the rebase action once you acknowledge the warning:
• If the selected neutral part is different from the selected physical part. For example, if you try to
rebase the old air conditioner to the new, redesigned air conditioner, which has a different part
number.
• If the occurrences between the selected neutral and physical part are different. For example, if you try
to rebase the left wheel occurrence to the right wheel occurrence.
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.
When rebasing the top-level parent in a physical structure, the following occurs:
• Because the rebase action only works on a single level of the structure and does not traverse the
entire structure, the physical structure modifications occur only one level below the selected top-level
parent.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the neutral part to be used to
rebase the physical part.
5. Click Show/Hide lower Structure Panel located at the top of the application to display the
neutral part and physical part using split structure panes.
9. Click Set Date to set the rebase date when the rebase occurred.
10. (Optional) Type the name of the structure context used to store the neutral product configuration
information in the Structure Context Name box 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.
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.
Note:
You can delete a physical part only from My Teamcenter.
Implementing deviations
Implementing deviations
Deviations occur when you install a physical part that is not a preferred, alternate, or substitute physical
part into an as-maintained 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-maintained 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.
1. Click My Teamcenter.
3. From the New Item dialog box, select Deviation Document and click Next.
5. Click Finish.
6. Click Close to close the screen or repeat steps 1–5 to create an additional deviation document.
Set up a deviation
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the deviated part.
5. From the Service Editor view, click Open by Name to open the physical structure where you
want to install the deviated part.
Note:
The deviation authority item must not be released to set up a deviation.
8. Search for the deviation authority item ID using the search dialog box. You can use wildcards for
searching.
3. In the New Process Dialog window, type the process name in the Process Name box.
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.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the deviated part.
4. Choose one of the following methods to identify the deviated physical part you want to install:
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 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.
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.
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:
B. Click the Search tab and enter the following information you want to use as filters for
searching.
C. Click Find.
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.
You can view the authorizing deviation item for a deviated part.
2. Select the physical structure containing the deviated part and choose Send to → My Teamcenter.
The Deviation Authority field shows the deviation authority item used to authorize the deviation.
1. From My Teamcenter or Service Manager, select the as-maintained structure you want to release.
3. In the New Process Dialog box, choose Release As-Maintained Structure from the Process
Template list.
Note:
The Release As-Maintained Structure option is the standard workflow provided with the As-
Maintained Management application. This workflow also validates for any missing physical
parts.
You can configure this workflow or create your own to set up the process flow, reviewers, and
business validations required to release an as-maintained structure.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the released physical structure.
4. Change the physical structure by uninstalling, installing, replacing, or rebasing the physical parts
within the structure.
• Part number
• Serial number
• 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.
• 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.
2. Click Open by Name to open the physical part you want to rename.
New Part New part number for the renamed Alphanumeric (1–128
Number physical part. characters)
The following occurs when you display an untraced structure in Service 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-maintained structure using visualization, you can also display the untraced parts.
2. Click Open by Name to open the physical structure that you want to display the untraced parts
for.
4. Choose View → Show Untraced Parts or click the Show Untraced Parts button on the main
toolbar at the top of the Service Manager pane.
BH001/InTest–A
BH012/A
BH013/A
BH014/A
BH015/A
BH016/A untraced part
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.
• Display the physical parts that are operational or nonoperational. When you set up a revision rule to
see only the operational structure, the system does not display the structure if the top-level physical
part is in a nonoperational state.
After you create the revision rule, you must set the revision rule to apply the rule to your structure.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the structure that you want to
apply the revision rule to.
6. Choose Create.
The New Revision Rule dialog box appears.
8. Click the Set Date button to set the effective date for the configuration. Select the Current
check box to set the current date.
9. Select the Show only Operational Configuration check box to display only operational structures.
10. Select the status for the state of the configuration you want to display. Select the Any check box to
display all the states.
11. Click OK to create the revision rule. Alternatively, click Cancel to exit.
The View/Set Current Revision Rule dialog box appears.
12. (Optional) Click Apply Rule if you want to set the revision rule.
a. From the Rules pane in the View/Set Current Revision Rule dialog box, select the revision
rule you want to edit. Click Modify.
The Modify Revision Rule dialog box appears.
b. Change the fields as required. Click OK to save the changes. Alternatively, click Cancel to exit.
• From the Rules pane in the View/Set Current Revision Rule dialog box, select the revision rule
you want to delete. Click Delete.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the structure that you want to
apply the revision rule to.
6. From the Rules pane in the View/Set Current Revision Rule dialog box, select the revision rule you
want to set.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the structure that you want to
apply the revision rule to.
6. Click the Set Date button to set the effective date for the configuration or select the Current
check box to set the current date.
7. Select the Show only Operational Configuration check box to display only operational structures.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the structure that you want to
apply the revision rule to.
6. Change the fields as required. Click OK to save the changes. Alternatively, click Cancel to exit.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure or physical
part.
• Managing physical part location movement by moving physical parts from one physical location to
another.
• Managing part disposition data by changing part dispositions and viewing disposition history to track
when a physical part changed dispositions.
• Managing assets by a user such as a asset manager that includes the following tasks:
Note:
If the physical part is installed in a physical structure and is not the top-level parent, you cannot
move the physical part to a different location.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From your home folder or from the Service Editor view, select all the physical parts you want to
change the location for.
7. Click the Set Date button to set the move date when the physical part was moved to the new
location.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open By Name to open the physical location.
6. Click next to the column and select a value to filter the results. You can filter the results by one
or more of the following properties:
• Object Name
• Type
• Part Number
• Serial Number
• Lot
• Manufacturer's ID
Disposition data captures different states of a physical part. These states are classified as operational or
nonoperational. You can manage part disposition data by:
• Changing the disposition for a physical part. For example, you may want to change the disposition
from a operational disposition such as In-Service to a nonoperational disposition such as In-Repair.
• Viewing the disposition history that is tracked for the physical part.
The following information is displayed in the disposition history view for the physical part.
Disposition Start Time Specifies the date when the disposition type
was assigned.
Disposition End Time Specifies the date when the disposition type
was removed or changed.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From your home folder or from the Service Editor view, select all the physical parts you want to
change the disposition for.
If you select a parent part and the Disposition_Propagate_To_Child preference is set to true, the
disposition change is also applied to the child parts.
6. Click the Set Date button to set the disposition date when the disposition changed.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure or physical
part.
5. Right-click the physical part BOM line and choose Show Disposition History.
The Disposition History pane appears.
A user such as an operator can record and track part utilization information based on life, observation
and date characteristic definitions defined for the neutral part. You can record values for the physical
part for all the characteristics related to the related neutral part. If you have purchased and have a
license for Service Event Management, utilization values are automatically recorded by creating service
events and activity entries; otherwise, you manually enter the values by using the Record Utilization
menu command.
Life characteristics are cumulated for the physical part and can be propagated throughout the entire
physical structure if any of the child physical parts share the same life characteristics. Date and
observation characteristics are not cumulated or propagated.
You must create a logbook before recording utilization information. The recorded information is stored
in the logbook log entries.
Create a logbook
4. In the New Log Book dialog box, enter the following information for the new logbook.
Record utilization
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure or physical
part.
4. Select the BOM line of the physical part you want to record the utilization for.
8. Click the Set Date button and select a date from the calendar of utilization.
9. Select the Propagate check box to propagate the same data to any child physical part that shares
the same life characteristic definitions
• For a date characteristic, click the Set Date button and select a date from the calendar.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure or physical
part.
4. Select the BOM line of the physical part you want to view the utilization for.
The Show Utilization pane appears and shows the utilization data.
Time Since New Specifies the sum of all recorded values for a life
characteristic definition. If a revision rule is being
used, the value is the sum of all recorded values
since the revision rule date.
Last Utilization Date Specifies the latest date the utilization values were
recorded.
When you view the log entries for a physical part, the following information is displayed:
Recording Time Date and time that the utilization was recorded.
Creation date Date and time when value was first entered.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open By Name to open the physical structure or physical
part.
4. Select the BOM line of the physical part you want to view the log entries for.
6. Expand the log entry to view all the characteristic definitions and their values.
The administrator can do the following to allow any user to update a log entry.
1. Add an ACL rule for the CharacteristicValue business object from Access Manager.
2. Give write privilege to desired users or roles, and restrict privileges for the world.
3. From the Service Editor view, click Open by Name to open the physical structure or physical
part.
4. Right-click the BOM line of the physical part for which you want to view the log entries, and choose
Show Log Entries.
The Log Entries pane appears.
5. Expand the log entry to view all the characteristic definitions and their values.
8. Select the Propagate check box to propagate the same data to any child physical part that shares
the same life characteristic definitions.
9. Update the characteristic values to invalidate the old value and record the new utilization.
• For a date characteristic, click Set Date and select a date from the calendar.
The following part usage information is displayed when you show the usage for a physical part.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the physical structure or physical
part.
4. Select the BOM line of the physical part you want to view the part usage for.
Managing assets
Asset groups are collections of physical assets that define a logical grouping of physical parts. For
example, you may want to create an asset group defining a fleet of aircraft or ships.
Asset hierarchies are used to build a nested hierarchy of asset groups within asset groups. The following
figure shows an example of an asset hierarchy.
2. Select a folder where you want to create the new asset group.
1. From My Teamcenter, select the parent asset group where you want the nested asset group.
3. Choose Window → Show View → Service Editor to open the Service Editor view.
2. Select the physical part that you want to add as a member of the asset group.
Note:
You must select the physical part, not the physical part revision.
4. Select the asset group you want the physical part to be a member of.
2. Choose Window → Show View → Service Editor to open the Service Editor view.
3. From the Service Editor view, click Open by Name to open the asset group.
6. To filter the results, click the button next to the column in the Contains pane.
You can delete an asset group if it is not the parent of a nested asset group and does not contain any
physical parts.
You can use the Service Event Management extension for Service Manager to:
• Create service groups and service group structures to organize the service performed on the physical
parts in your organization.
• Capture irregularities or discrepancies for physical parts and create associated corrective action
service events for those discrepancies.
• Track physical parts installed and uninstalled in the physical structure as a result of service performed.
• Approve service events to apply any associated changes to the as-maintained structure.
You must install the appropriate components and licenses for Service Manager (as-maintained
management) and Service Event Management and perform any configuration tasks prior to using this
functionality. You must also perform any tasks needed to create your neutral structure and as-
maintained structure prior to recording any service data.
A service group is a collection of service events and service discrepancies that you can create to organize
service data for one or more physical parts. You can create a single service group or a hierarchy of
service groups called a service group structure by creating one or more service groups within a service
group. You can create a service group without a relation to a physical part, or you can create a service
group and relate it to one or more physical parts.
3. From the Service Editor view, create a service group in one of the following ways:
• Select the folder where you want to create the new service group or select the physical part to
relate to the service group and choose File → New → Service Group.
• Right-click the physical part to relate to the service group and choose New Service Group.
Note:
You can also select an existing service group to create this new service group in to create a
service structure hierarchy.
Contained In Parent service group to associate to this Click and select one of the
service group.
following values:
In Progress Physical part or physical parts associated Click and select one of the
Physical Parts with this service group.
following values:
5. Click Finish to create the service group. Alternatively, click Cancel to exit.
1. From the Service Editor view, select the service group to edit.
A service event is informational data that is captured as a result of service activity performed on a
physical part by an external source. A service event captures information such as the service type, work
scope, resource information, maintenance time, and cost. When you create a service event, you can
associate it to a service group or create it without a parent service group, but you must associate it to a
single physical part. After a service event is approved, you can edit it, but you cannot delete it or add
service data to it.
3. From the Service Editor view, click Open By Name to open the physical structure or physical
part.
4. From the Service Editor view, create a service event in one of the following ways:
• Select the folder where you want to create the new service event or select the physical part or
service group to relate to the service event and choose File → New → Service Event.
• Right-click the physical part or service group to relate to the service event and choose New
Service Event.
Contained In Parent service group to associate to this Click and select one of the
service event.
following values:
Action Type Type of service completed for this service Select one of the following
event. values:
• Overhaul
• Inspection
• Repair
• Other
Authorized By Name of the person that authorized the Alphanumeric string (1–40
service. characters).
Work Start Date Date that the work starts. Click the Set Date button and
select a date from the calendar.
Needed By Date Date that the work needs to be complete. Click the Set Date button and
select a date from the calendar.
Zones Zone where the service event occurred. Alphanumeric string (1–256
characters).
Job Cards Job cards associated to the service event. Alphanumeric string (long
string).
Work Location Location that the work occurred. Alphanumeric string (long
string).
Signed Off By Name of the person that signed approval Alphanumeric string (1–40
for the service. characters).
In Progress Physical part associated with this service Click and select one of the
Physical Part event (required).
following values:
6. Click Finish to create the service event. Alternatively, click Cancel to exit.
1. From the Service Editor view, select the service event to edit.
You can capture life, date, or observation characteristic type data on a service event for an associated
physical part. You must create characteristics definitions on the neutral structure before you can capture
this information on a service event. These characteristics are referred to as activity entry values on a
service event and record utilization information for the associated physical part. The utilization
information for the physical part is not updated until the service event is approved. An activity entry
value can only be contained within a service event.
1. From the Service Editor view, select the service event to add the activity entry values to.
Service Event Parent service event associated to this Click and select one of the
activity entry value (required).
following values:
Name Name of the activity entry value (required). Click and select the activity
entry name.
Characteristic Date that the characteristic was observed Click the Set Date button
Date during maintenance. and select a date from the
calendar.
3. From the Service Editor view, click Open by Name to open the physical structure or physical
part.
4. Select the BOM line of the physical part you want to view the utilization for.
You can capture actual time and cost information for a service event. Use Access Manager to allow only
authorized users to view or update the actual time and cost information for a service event.
Discrepancies are irregularities or observations that are discovered with regard to maintenance of assets
or physical parts. Discrepancies can also identify if there was a failure with the physical part. For each
service discrepancy, you must create an associated corrective action service event to address the service
discrepancy. You can associate one or more fault codes to a discrepancy. When you create a service
discrepancy, you must relate it to a physical part. You can also select a parent service group or service
event to relate to the service discrepancy when you create the service discrepancy.
A service discrepancy can also contain fault information about the part. This fault information, or fault
code, is an identifier that indicates an itemized fault or problem that a manufacturer has identified with
a part. Physical parts can also report fault codes as a result of internal diagnostics.
3. From the Service Editor view, click Open by Name to open the physical structure or physical
part.
4. From the Service Editor view, create a service discrepancy in one of the following ways:
• Select the folder where you want to create the new service discrepancy or select the physical
part, service group, or service event to relate to the service discrepancy and choose File → New
→ Service Discrepancy.
• Right-click the physical part, service group, or service event to relate to the service discrepancy
and choose New Service Discrepancy.
5. Complete the following information for the service discrepancy. Some values may already be
supplied.
Contained In Parent service group or service event to Click and select one of the
associate to this service discrepancy.
following values:
Initiation Date Date that the discrepancy is first recorded. Click the Set Date button and
select a date from the calendar.
• Critical
• Major
• Minor
Discovered By Name of the person that discovered the Alphanumeric string (1–40
discrepancy. characters).
Discovery Date Date that the discrepancy was discovered. Click the Set Date button and
select a date from the calendar.
Due Date Date that the corrective action work needs Click the Set Date button and
to be complete. select a date from the calendar.
Physical Part In Physical part associated with this service Click and select one of the
Progress discrepancy (required).
following values:
Fault Code Associated fault codes for this service Click and select one of the
discrepancy.
following values:
6. Click Finish to create the service discrepancy. Alternatively, click Cancel to exit.
1. From the Service Editor view, select the service discrepancy to edit.
3. From the Service Editor view, select the service discrepancy to associate with the new corrective
action service event.
6. Click Finish to create the corrective action service event. Alternatively, click Cancel to exit.
3. From the Service Editor view, create a fault code in one of the following ways:
• Select the folder where you want to create the new fault code or select the physical part or
service discrepancy to relate to the fault code and choose File → New → Fault Code.
• Right-click the physical part or service discrepancy to relate to the fault code and choose New
Fault Code.
Service Parent service discrepancy associated to Click and select one of the
Discrepancy this fault code (required).
following values:
Name Name of the activity entry value (required). Alphanumeric string (1–128
characters).
5. Click Finish to create the fault code. Alternatively, click Cancel to exit.
Part movement is a record of each physical part that is installed, replaced, or uninstalled as a result of a
service event.
Part movements can be categorized as traceable or untraceable. Traceable part movements are
necessary for parts that affect the physical structure. The changes to the physical structure from a
traceable part movement are not applied until the parent service event is approved. Untraceable part
movements capture only the part number and serial number of the physical part and are used for parts
that do not affect the physical structure, such as a filter change.
Part movements must be approved to execute the changes to the physical structure. If the approval
fails, all changes are rolled back and the process is terminated.
The install and replace part movement records contains a Is New option.
• If the Is New option is set to a value of true, you need to specify an existing neutral part to be used as
the basis for the new physical part. After approval, the new physical part is created and used for the
installation or replacement.
• If the Is New option is set to a value of false, you need to specify an existing physical part. After
approval, the specified physical part is used for the installation or replacement.
3. From the Service Editor view, select the service event or physical part to associate with the new
part movement.
5. In the Create Part Movement dialog box, complete the following information for the part
movement.
Parent Parent service event associated with this Click and select one of the
part movement (required).
following values:
Part Movement The type of part movement (required). Select Uninstall to create an
Type uninstall part movement.
Action Date The date of the part movement. Click the Set Date button and
select a date from the calendar.
Note:
If you do not enter a value for the
action date, the date is set from the
current date/time on the server
where the part movement is created.
6. Click Show As-Maintained Structure to open the Maintenance tree pane and load the as-
maintained physical structure related to the service event.
7. From the Maintenance tree pane, select the physical part you want to uninstall.
Note:
If a part in the physical structure is missing and has no generated physical part, the part is
highlighted in red and is represented by a neutral part. You cannot select that part for the
uninstallation.
• The Parent Physical Element field now contains the physical structure parent part.
• The Usage Name field now contains usage of the selected physical part.
Part Number The part number of the new physical part. Alphanumeric string (1–128
The part number is valid only if the field Is characters).
Traceable is set to false indicating the part
you are uninstalling does not exist as a
neutral part in the database.
Serial Number The serial number of the new physical part. Alphanumeric string (1–128
The part number is valid only if the field Is characters).
Traceable is set to false indicating the part
Lot Number The lot number of the new physical part. Alphanumeric string (1–128
The part number is valid only if the field Is characters).
Traceable is set to false indicating the part
you are uninstalling does not exist as a
neutral part in the database.
Uninstall The physical location of the uninstalled Click and select one of the
Location part.
following values:
10. Click Finish to create the uninstall part movement. Alternately, click Cancel to exit.
The applicable part movement changes are not applied to the physical structure until the parent
service event is approved. After approval, the physical part is uninstalled from the structure.
3. From the Service Editor view, select the service event or physical part to associate with the new
part movement.
5. In the Create Part Movement dialog box, complete the following information for the part
movement.
Parent The parent service event associated to this Click and select one of the
part movement (required).
following values:
Part Movement The type of part movement (required). Select Install to create an install
Type part movement.
Select Replace to create a
replacement part movement.
Action Date The date of the part installation. Click the Set Date button and
select a date from the calendar.
Note:
If you do not enter a value for the
action date, the date is set from the
current date/time on the server
where the part movement is created.
6. Click Show As-Maintained Structure to open the Maintenance tree pane and load the as-
maintained physical structure related to the service event.
• If the Part Movement Type field is set to Install, select the physical part to identify the usage of
the part you want to install.
• If the Part Movement Type field is set to Replace, select the physical part to identify the usage
of the part you want to uninstall and replace.
Note:
If the Part Movement Type field is set to Replace, you cannot select a part for
replacement that is uninstalled or missing.
Note:
• If Is Extra to Design is set to true, select the physical part parent of the structure where
you want to install the extra to design part.
• If a part in the physical structure is missing and has no generated physical part, the part is
highlighted in red and is represented by a neutral part. You cannot select that part for
replacement.
• The Parent Physical Element field now contains the physical structure parent part.
• The Usage Name field now contains usage of the selected physical part.
9. From Create Part Movement pane, complete the following information for the part movement.
Neutral Part The neutral part that is used to create the Click and select one of the
new physical part to be installed.
following values:
Note:
• Add allows you to search for
This field is only valid if Is New is set an existing neutral part.
to true indicating the neutral part • Clear clears any neutral part
does not have a realized physical that is contained in this field.
part.
Physical Part The physical part to install. Click and select one of the
following values:
Note:
This field is only valid for the • Add allows you to search for
following conditions: an existing physical part to
install.
• The field Is New is set to false The search results display the
indicating the physical part valid preferred, alternate,
selected for the install already substitute, and deviated
exists. physical parts that can be
installed.
• The field Is Traceable is set to • Clear clears any physical part
true indicating it is traceable part that is contained in this field.
movement.
Part Number The part number of the new physical part. Alphanumeric string (1–128
The part number is valid only if the field Is characters).
Traceable is set to false indicating the part
you are installing does not exist as a
neutral part in the database.
Serial Number The serial number of the new physical Alphanumeric string (1–128
part. The part number is valid only if the characters).
field Is Traceable is set to false indicating
the part you are installing does not exist as
a neutral part in the database.
Lot Number The lot number of the new physical part. Alphanumeric string (1–128
The part number is valid only if the field Is characters).
Traceable is set to false indicating the part
you are installing does not exist as a
neutral part in the database.
Uninstall The physical location of the uninstalled Click and select one of the
Location part.
following values:
Note:
• Add to select the physical
This field is only available if the Part location from the displayed list
Movement Type field is set to of preferred physical locations.
Uninstall or Replace. • Clear to clear the physical
location that is contained in
this field.
10. Click Finish to create the install part movement. Alternately, click Cancel to exit.
The applicable part movement changes are not applied to the physical structure until the parent
service event is approved. After approval, the physical part is uninstalled from the structure.
• Service groups
When you approve a service group, the approval process is applied to all of the service groups, service
events, and service discrepancies contained within that parent service group.
• Service events
If a service event is part of a service group, it can be approved as part of the approval process for the
parent service group.
• Service discrepancies
If a service discrepancy is related to a service group or service event, it can only be approved by
approving the parent service group or service event. A service discrepancy that does not have an
associated corrective action service event cannot be approved.
Note:
Service groups, service events, and service discrepancies can only be approved by a user that
shares the same role as the creating user. Users outside the role of the creating user cannot
approve the object.
If the service data objects are part of a service group structure, you can only approve the top level
of the structure. Approval of leaf nodes is not permitted. You can approve the above service data
objects individually if they are not part of a service group structure. When service data objects are
approved, they are locked, and you cannot add additional information.
• Right-click the service group, service event, or service discrepancy that you want to approve and
choose Approve.
• Route the service group, service event, or service discrepancy that you want to approve to a workflow
created in Workflow Designer that uses the SERVICEPROCESSING-approve-service-structure
workflow handler for approval.
• The approval attribute for the approved service data is set to Approved.
• The In-Process relationship between each transaction element and the related physical part master is
removed and a Completed relationship is added to the physical part revision.
• If the category of a service event is set to Overhaul, the date and time of the last overhaul is set to
the completion date and time of the service event.
• If the category of a service event is set to Repair, the date and time of the last repair is set to the
completion date and time of the service event.
• The service data objects are locked, and you cannot add additional information.
• Property details
Details that display the properties of the service event management object.
3. From the Service Editor view, select the service event object that you want to display the service
details for.
5. To display service events that are in progress for a physical structure or part, click next to the
button in the Service Details window and select Show In-Progress.
6. To display service events that are completed for a physical structure or part, click next to the
button in the Service Details window and select Completed.
7. To display part movement information for a service event, click next to the button in the
Service Details window and select Show Part Movements.
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.
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 Service
Editor window for the parts in the neutral structure. This comparison is similar to an accountability
check between structures using Multi-Structure Manager. 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.
To specify the default and additional properties used for comparing as-maintained structures with
context, an administrator sets the DefaultAsMaintainedAccCheckProperties and
AdditionalAsMaintainedAccCheckProperties preferences.
DefaultAsMaintainedAccCheckProperties phbl_part_number
phbl_part_used_is
phbl_design_rev_id
AdditionalAsMaintainedAccCheckProperties phbl_part_usage_name
You compare two as-maintained structures in the Service Editor view using two separate panes.
1. From the navigation pane, click Service Manager to open the source structure in the bottom pane
and the target structure in the top pane.
b. Choose Window → Show View → Service Editor to open the Service Editor view.
c. From the Service Editor 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-maintained structures in the appropriate panes, configure them by setting
the revision rule and/or variant rule in each pane.
• If you want to reverse source and target as-maintained structures, select Flip source and target.
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.
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.
• 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.
• 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.
• 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.
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 using Structure Manager. 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.
• Property preferences
To specify the default and additional properties used for comparing as-maintained structures without
context, an administrator sets the sets the DefaultAsMaintainedCompareProperties and
AdditionalAsMaintainedCompareProperties preferences.
DefaultAsMaintainedCompareProperties phbl_part_number
phbl_part_usage_name
AdditionalAsMaintainedCompareProperties phbl_part_used_is
phbl_design_rev_id
• 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.
PSEAdditionColorPref red
PSEChangedColorPref orange
You compare two as-maintained structures in the Service Editor view using two separate panes.
1. From the navigation pane, click Service Manager to open the source structure in the bottom pane
and the target structure in the top pane.
b. Choose Window → Show View → Service Editor to open the Service Editor view.
c. From the Service Editor 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-maintained structures in the appropriate panes, configure them by setting
the revision rule and/or variant rule in each pane.
Note:
You compare only the visible structures displayed in the panes.
• If you want to reverse source and target as-maintained structures, select Flip source and target.
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.
Note:
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.
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.
You can compare an as-maintained neutral structure with an as-maintained physical structure. For
example, you may want to highlight the following as differences:
• Nontraceable parts
• Substitute parts
• Deviated parts
To compare a neutral structure with a physical structure with context, set up the comparison as
described in Perform compare with context.
To compare a neutral structure with a physical structure without context, set up the comparison as
described in Perform compare without context.
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.
The color green indicates a full match. The following parts show differences.
BH014A Physical Light blue indicating the The alternate part for the
physical part is an alternate 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.
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: neutral structure in the top pane for the bearing housing assembly.
• Target structure: physical structure in the bottom pane for the bearing housing assembly.
• Display options:
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.
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.
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.
You can compare two as-maintained physical structures. For example, you may want to highlight the
differences between two installations of the same physical structure.
To compare two physical structures with context, set up the comparison as described in Perform
compare with context.
To compare two physical structures without context, set up the comparison as described in Perform
compare without context.
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.
The color green indicates a full match. The following parts show differences.
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.
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.
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.
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:
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.
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
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
BH015 MTruck Red indicating no match The substitute part for the
shaft was installed in the
physical structure used in the
supply truck.
You use the embedded viewer in the Service Editor 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 Service Editor 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.
3. From the Service Editor view, click Open By Name to open the as-maintained physical
structure or neutral structure.
To display split structure panes for two structures, click Show/Hide lower Structure Panel
located at the top of the application.
4. Choose View → Show Data Panel, or click the Show/Hide Data Panel button on the toolbar.
5. Click the Assembly Viewer tab to visualize the 3D models for the structure.
3 Graphical viewing window Displays the 3D model associated with the product
structure.
Change visibility
• 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 want
structure 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.
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 → Unblank All Makes all objects loaded in the viewer visible.
Command Description
Visibility → Reverse Blank All Makes any currently visible objects invisible, while
simultaneously making visible any loaded objects which are
currently invisible.
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 → Persistent Modifies the physical location of a part (or set of parts) in an
Transformation owning assembly.
Command Description
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.
Clearance → Preferences → Clear Adjusts the clearance results preferences to change the
ance Results appearance and behavior of clearance results.
Pan Examine Fly Pan the model in the plane of the viewing window.
Explore
Zoom Examine Move closer to or farther from the model.
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.
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
• Importing as-maintained physical structures and service event management data from third-party
systems or other Teamcenter sites into Teamcenter using the PLM XML format.
• Exporting as-maintained physical structures and service event management data from Teamcenter to
other Teamcenter sites or third party systems using the PLM XML format.
• Using Multi-Site Collaboration to share Service Manager data between multiple Teamcenter sites.
You can export as-maintained physical structures in the PLM XML format.
Exported data includes:
• Deviation information.
• Characteristics
• Characteristic values
• Log book
• Log entries
You can export the following service event management objects in the PLM XML format:
• Service group
• Service event
• Service discrepancy
• Fault codes
• Part movements
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.
6. (Optional) Click Select Languages to display the Language Selection dialog box for the languages
configured at your site.
• 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 reorder the languages in the Selected Additional Languages box, select a language
and use the move buttons as required.
3. Click OK or Apply.
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.
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.
A user such as a production planner can import Service Manager data from Teamcenter to other
Teamcenter sites or third party systems.
You can import as-maintained and service event management data into Teamcenter from any third-
party system if it conforms to the PLM XML schema.
When you import as-maintained structures, the following information is also imported:
• Disposition information.
Refer to the following table for PLM XML elements and the associated Teamcenter as-maintained
classes.
RealizedProductRevision PhysicalPartRevision
Deviation DeviationDocument
DeviationRevision DeviationDocumentRevision
CharacteristicDefinition, CharacteristicDefinition
CharacteristicDefinitionRevision
CharacteristicValue CharacteristicValue
SLMLocation PhysicalLocation
SLMLocationRevision PhysicalLocationRevision
Because the physical structure does not have one-to-one mapping in PLM XML, the following combined
PLM XML elements provide the information for the entire physical structure:
• InstanceGraph
• ProductRevisionView
• RealisedProductInstance
• Before you import an as-maintained 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, PLM XML processes the structure relationship without the alignment relation.
• If the lot information is provided and the lot is not defined in Teamcenter, PLM XML creates and
assigns the physical part to the new lot. If the lot exists, the physical part is assigned to the existing
lot.
• When importing a part movement using PLM XML, the Uninstall Location field is blank and the
following values are used:
Refer to the following table for PLM XML elements and the associated Teamcenter service event
management classes.
ServiceGroupType ServiceGroup
ServiceDiscrepancyType ServiceDiscrepancy
TCServiceEventType ServiceEvent
PartMovementType PartMovement
FaultCodeType FaultCode
ActivityCostType ActivityCost
ActivityEntryValueType ActivtyEntryValue
Note:
Before you import an as-maintained structure, the neutral structure and the part logistics
information must exist on the importing site.
You can import Service Manager data (as-maintained or service event management) into Teamcenter
from a third-party system using PLM XML by performing the following steps:
3. Select PLM XML File (.xml) from the Files of type list.
4. Navigate to the directory containing the file and select the file.
The system displays the file name in the Directory name box.
5. Click Select.
The system displays the path to the selected file in the Importing Object box of the dialog box.
7. (Optional) Select the View Log File check box to view the log file when the data transfer is
complete.
8. 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 in to Teamcenter. Teamcenter
provides 128 bytes for item IDs and names.
When you import an as-maintained structure into Teamcenter from a third-party system and the physical
part parent is at a status of released in Teamcenter, the revision of the parent is revised only if there are
structural additions to the existing structure.
As the following figure shows, because the parent physical part Aircraft #100 has a status of released
before the import, it is revised after the import because Engine #300 was added to the structure in a
different position.
Released parent physical part revision is revised in Teamcenter after structural addition
When you re-import an as-maintained structure into Teamcenter from a third-party system, be aware of
the following behaviors:
• Re-import after the physical part is added to the as-maintained structure on third-party systems.
As the following figure shows, when the third-party as-maintained structure is re-imported with the
newly added physical part Pump #300, the additional part is imported into Teamcenter.
• Re-import after the physical part is deleted from the as-maintained structure on third-party systems.
As the following figure shows, when the third-party as-maintained structure Aircraft #100 is re-
imported to Teamcenter with the physical part Pump #300 removed, the physical part is not removed
in Teamcenter.
Using Multi-Site Collaboration, you can share Service Manager data between multiple Teamcenter sites.
Each Teamcenter site has its own independent database with its own set of users and groups, data
models, 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.
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 owner’s site, transmit it over the network, and import it into the destination site.
When you export as-maintained structures and related Service 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 Service Manager object and
whether the related object is optional or required.
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 Service Manager actions that can be performed on object replicas and stubs.
Name occurrence No No
Setup deviation No No
Assign lot No No
Display location structure Yes Yes Stubs are displayed as remote lines.
Structures below stubs are not displayed.
Set default location No Yes The compared structures should not have
any stubs.
Display utilization No Yes Characteristic values that are stubs are not
displayed.
When you import service event management objects using Multi-Site Collaboration, you must set the
Include Reference option to import the following related objects. The option is set by clicking the
Advanced tab in the Import Remote Options dialog box. The table summarizes which relations and
corresponding related objects are imported for each service event management object and whether the
related object is optional or required.
Service Event Management is a separately licensed extension of the Service Manager application. You
must obtain and install the appropriate licenses required to run the Service Event Management
extension.
AdditionalAsMaintainedAccCheckProperties
DESCRIPTION
VALID VALUES
Accepts one or more stings as values. Each string must be a valid BOM line property and a valid as-
maintained BOM line property.
DEFAULT VALUES
phbl_part_usage_name
Site preference.
AdditionalAsMaintainedCompareProperties
DESCRIPTION
VALID VALUES
Accepts one or more stings as values. Each string must be a valid BOM line property and a valid as-
maintained BOM line property.
DEFAULT VALUES
phbl_part_used_is
Site preference.
DefaultAsMaintainedAccCheckProperties
DESCRIPTION
VALID VALUES
Accepts one or more stings as values. Each string must be a valid neutral BOM line property and a valid
as-maintained BOM line property.
DEFAULT VALUES
phbl_part_number
phbl_part_used_is
Site preference.
DefaultAsMaintainedCompareProperties
DESCRIPTION
VALID VALUES
Accepts one or more stings as values. Each string must be a valid neutral BOM line property and a valid
as-maintained BOM line property.
DEFAULT VALUES
phbl_part_number
phbl_part_usage_name
Site preference.
Disposition_Propagate_To_Child
DESCRIPTION
Determines if the disposition defined during the generation or duplication of the as-maintained
structure is propagated to all of the children parts generated.
VALID VALUES
DEFAULT VALUES
false
Site preference.
SLMConfigRuleName
DESCRIPTION
Specifies the default configuration rule to use when opening as-maintained physical part revisions. If
this rule does not exist, the system defaults to Today Serviceable.
VALID VALUES
Accepts a string as a value. Each string must be a valid as-maintained revision rule name.
DEFAULT VALUES
Today Serviceable
Site preference.
SLMDefaultLocations
DESCRIPTION
Specifies the default locations to use for the Generate As-Maintained Structure and Un-Install
Physical Part actions.
VALID VALUES
Accepts one or more strings as values. Each string must be a valid location name from the physical
location object.
DEFAULT VALUES
None.
Site preference.
PhysicalLocation_CompanyLocation_default_relation
DESCRIPTION
Defines the default relationship between a company location and a physical location.
VALID VALUES
Accepts one or more strings as a value. Each string must be a valid Teamcenter object.
DEFAULT VALUES
PhysicalLocationDetails
Site preference.
PhysicalLocationContainsColumnsShownPref
DESCRIPTION
Specifies the columns displayed in the Contains view when the selected component is a physical
location.
VALID VALUES
DEFAULT VALUES
partNumber
serialNumber
lotNumber
manufacturerOrgId
manufacturingDate
Site preference.
PhysicalLocation_DefaultChildProperties
DESCRIPTION
VALID VALUES
Accepts one or more strings as values. Each string must be a valid Teamcenter property name.
DEFAULT VALUES
IMAN_master_form
bom_view_tags
revision_list
IMAN_requirement
IMAN_manifestation
IMAN_reference
IMAN_MEView
IMAN_vi_sos
IMAN_external_object_link
PhysicalElementOwner
PhysicalLocationDetails
Site preference.
ServiceManagerAssetGroupColumnsShownPref
DESCRIPTION
Specifies the list of columns displayed for an asset group in Service Manager in left to right order.
VALID VALUES
Accepts one or more strings as values. Each string must be a valid asset group property.
DEFAULT VALUES
object_name
object_desc
Site preference.
ServiceManagerAssetGroupColumnWidthsPref
DESCRIPTION
Specifies the column widths displayed for an asset group in Service Manager in left to right order.
VALID VALUES
One or more integers as values; each integer defines the column width in characters. The first value set
in this preference defines the column width of the first value set in the
ServiceManagerAssetGroupColumnsShownPref user preference and so forth.
DEFAULT VALUES
20
20
Site preference.
ServiceManagerColumnsShownPref
DESCRIPTION
Specifies the columns displayed for physical parts opened in Service Manager in left to right order.
VALID VALUES
Accepts one or more stings as values. Each string must be a valid as-maintained BOM line property.
DEFAULT VALUES
bl_indented_title
bl_item_object_type
phbl_part_used_is
phbl_part_usage_name
phnl_serial_number
phbl_lot_number
phbl_part_number
phbl_installation_time
phbl_mfg_date
phbl_mfgr_org_id
phbl_physical_quantity
phbl_physical_uid
bl_item_item_id
Site preference.
ServiceManagerShownColumnWidthsPref
DESCRIPTION
Specifies the column widths displayed for physical parts in Service Manager in left to right order.
VALID VALUES
One or more integers as values; each integer defines the column width in characters. The first value set
in this preference defines the column width of the first value set in the
ServiceManagerShownColumnWidthsPref user preference and so forth.
DEFAULT VALUES
20
10
10
10
10
10
10
15
15
10
10
15
10
Site preference.
ServiceManagerPhysicalLocationColumnsShownPref
DESCRIPTION
VALID VALUES
Accepts one or more stings as values. Each string must be a valid as-maintained BOM line property.
DEFAULT VALUES
plbl_location_name
plbl_location_description
plbl_location_type
Site preference.
ServiceManagerPhysicalLocationColumnWidthsPref
DESCRIPTION
Specifies the column widths displayed for the physical location in left to right order.
VALID VALUES
One or more integers as values; each integer defines the column width in characters. The first value set
in this preference defines the column width of the first value set in the
ServiceManagerPhysicalLocationColumnWidthsPref user preference and so forth.
DEFAULT VALUES
20
20
20
Site preference.
ActivityCost.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for activity cost objects.
VALID VALUES
DEFAULT VALUES
ActivityCost
Site preference.
ActivityCost.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for activity cost objects.
VALID VALUES
DEFAULT VALUES
ActivityCostSummary
Site preference.
ActivityEntryValue.SLMCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for activity entry value objects.
VALID VALUES
DEFAULT VALUES
ActivityEntryValueCreate
Site preference.
ActivityEntryValue.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for activity entry value objects.
VALID VALUES
DEFAULT VALUES
ActivityEntryValue
Site preference.
ActivityEntryValue.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for activity entry value objects.
VALID VALUES
DEFAULT VALUES
ActivityEntryValueSummary
Site preference.
FaultCode.SLMCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for fault code objects.
VALID VALUES
DEFAULT VALUES
FaultCodeCreate
Site preference.
FaultCode.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for fault code objects.
VALID VALUES
DEFAULT VALUES
FaultCode
Site preference.
FaultCode.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for fault code objects.
VALID VALUES
DEFAULT VALUES
FaultCodeSummary
Site preference.
SLMDefaultLogBook
DESCRIPTION
Determines the registration of the create style sheet for service discrepancy objects.
VALID VALUES
DEFAULT VALUES
ServiceLogBook
Site preference.
PartMovement_DefaultChildProperties
DESCRIPTION
VALID VALUES
DEFAULT VALUES
MovedPart
Site preference.
PartMovementDefaultRemoveLocation
DESCRIPTION
Determines the default physical location to use when you create a service event that is related to a part
movement.
VALID VALUES
DEFAULT VALUES
None.
Site preference.
PartMovement.ENABLE_PROPERTIES_EDIT
DESCRIPTION
Allows edits to the part movement properties. To allow edits, set the value to false.
VALID VALUES
DEFAULT VALUES
false
Site preference.
PartMovement.SLMCREATERENDERING
DESCRIPTION
Determines the registration of the summary style sheet for part movement objects.
VALID VALUES
DEFAULT VALUES
PartMovementCreate
Site preference.
PartMovement.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for part movement objects.
VALID VALUES
DEFAULT VALUES
PartMovement
Site preference.
PartMovement.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for part movement objects.
VALID VALUES
DEFAULT VALUES
PartMovementSummary
Site preference.
ServiceAction.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for service action objects.
VALID VALUES
DEFAULT VALUES
ServiceAction
Site preference.
ServiceAction.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for service action objects.
VALID VALUES
DEFAULT VALUES
ServiceActionSummary
Site preference.
ServiceDiscrepancy_DefaultChildProperties
DESCRIPTION
VALID VALUES
DEFAULT VALUES
CorrectiveAction
InProgress
fault_code
Site preference.
ServiceDiscrepancy.ENABLE_PROPERTIES_EDIT
DESCRIPTION
Allows edits to the service discrepancy properties. To allow edits, set the value to true.
VALID VALUES
DEFAULT VALUES
false
Site preference.
ServiceDiscrepancy_FaultCode_default_relation
DESCRIPTION
VALID VALUES
DEFAULT VALUES
fault_code
Site preference.
ServiceDiscrepancy.SLMCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for service discrepancy objects.
VALID VALUES
DEFAULT VALUES
ServiceDiscrepancyCreate
Site preference.
ServiceDiscrepancy.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for service discrepancy objects.
VALID VALUES
DEFAULT VALUES
ServiceDiscrepancy
Site preference.
ServiceDiscrepancy_ServiceEvent_default_relation
DESCRIPTION
VALID VALUES
DEFAULT VALUES
CorrectiveAction
Site preference.
ServiceDiscrepancy_ServiceGroup_default_relation
DESCRIPTION
VALID VALUES
DEFAULT VALUES
InvalidRelation
Site preference.
ServiceDiscrepancy.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for service discrepancy objects.
VALID VALUES
DEFAULT VALUES
ServiceDiscrepancySummary
Site preference.
ServiceEvent_DefaultChildProperties
DESCRIPTION
VALID VALUES
DEFAULT VALUES
Completed
InProgress
CorrectiveAction
HMSOStructure
activity_entry_value
Site preference.
ServiceEvent.ENABLE_PROPERTIES_EDIT
DESCRIPTION
Allows edits to the service event properties. To allow edits, set the value to true.
VALID VALUES
DEFAULT VALUES
false
Site preference.
ServiceEvent.SLMCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for service event objects.
VALID VALUES
DEFAULT VALUES
ServiceEventCreate
Site preference.
ServiceEvent.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for service event objects.
VALID VALUES
DEFAULT VALUES
ServiceEvent
Site preference.
ServiceEvent.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for service event objects.
VALID VALUES
DEFAULT VALUES
ServiceEventSummary
Site preference.
ServiceGroup.ENABLE_PROPERTIES_EDIT
DESCRIPTION
Allows edits to the service group properties. To allow edits, set the value to true.
VALID VALUES
DEFAULT VALUES
false
Site preference.
ServiceGroup.SLMCREATERENDERING
DESCRIPTION
Determines the registration of the create style sheet for service group objects.
VALID VALUES
DEFAULT VALUES
ServiceGroupCreate
Site preference.
ServiceGroup.RENDERING
DESCRIPTION
Determines the registration of the viewer style sheet for service group objects.
VALID VALUES
DEFAULT VALUES
ServiceGroup
Site preference.
ServiceGroup.SUMMARYRENDERING
DESCRIPTION
Determines the registration of the summary style sheet for service group objects.
VALID VALUES
DEFAULT VALUES
ServiceGroupSummary
Site preference.
TransactionElement.COLUMNS_SHOW
DESCRIPTION
Determines which columns are displayed in the transaction element structure in left to right order.
VALID VALUES
DEFAULT VALUES
object_name
transaction_id
Site preference.
TransactionElement.COLUMNS_WIDTH
DESCRIPTION
Determines the widths for the columns displayed in the transaction element structure in left to right
order.
VALID VALUES
DEFAULT VALUES
20
20
Site preference.
TransactionElement_DefaultChildProperties
DESCRIPTION
VALID VALUES
DEFAULT VALUES
InProgress
HWSOStructure
Site preference.
TransactionElement_Document_default_relation
DESCRIPTION
VALID VALUES
DEFAULT VALUES
IMAN_reference
Site preference.
TransactionElement_DocumentRevision_default_relation
DESCRIPTION
VALID VALUES
DEFAULT VALUES
IMAN_reference
Site preference.
TransactionElement_PhysicalElement_default_relation
DESCRIPTION
VALID VALUES
DEFAULT VALUES
InProgress
Site preference.
TransactionElement_PhysicalElementRevision_default_relation
DESCRIPTION
Defines the relationship between a transaction element and a physical element revision.
VALID VALUES
DEFAULT VALUES
InvalidRelation
Site preference.
as-maintained structure
Physical configuration of a manufactured product evolving through its serviceable lifetime. A single
neutral structure can result in many as-maintained structures, one for each physical asset.
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.
asset group
Collection of physical assets that define a logical grouping of physical products. You can create asset
groups and asset hierarchies. Asset hierarchies are used to build a nested hierarchy of asset groups
within asset groups.
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
Teamcenter object used to manage product structure information for an item.
BVR
See BOM view revision (BVR).
C
characteristic definition
Information related to a neutral part that is important for service organizations maintaining assets. You
can create characteristic definitions that contain information to be measured against the physical part,
such as how long a product has been in use. You can also create characteristic definitions that contain
data to be measured against a physical part, such as temperature or oil pressure.
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.
consumable part
Nonrepairable item or repair part that can be discarded more economically than it can be repaired.
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.
deviation document
Document that authorizes the installation of a physical part that is a deviation from the design structure.
E
end item
Top-level node of an assembly that can represent a product or a factory structure.
F
fault code
Identifier that indicates an itemized fault or problem that a manufacturer has identified with a part.
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.
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
log book
Collection of log entries recorded against a specific physical asset. A physical asset may have more than
one associated log book.
log entry
Record of data collected about a physical asset and recorded by a certain person at a certain time. The
log entry is associated to a single asset but may record characteristic values for several components
within that asset.
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.
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.
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.
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.
rotable part
Repairable component or inventory item that can be repeatedly restored to a fully operational condition
and reused over the normal life cycle of the parent equipment to which it is related.
S
serialized part
Physical part or assembly identified by a serial number.
service discrepancy
An irregularity or observation discovered with regard to maintenance of a physical part. Discrepancies
can also identify if there was a failure with the physical part.
service event
Informational data that is captured as a result of service activity that is performed by an external source.
service group
Collection of service events and service discrepancies used to organize the service records of one or
more physical parts.
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.
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.
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