100% found this document useful (1 vote)

374 views204 pages

Administering Manufacturing Planning

Uploaded by

xianlei yang

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

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (1 vote)

374 views204 pages

Administering Manufacturing Planning

Uploaded by

xianlei yang

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

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 204

Teamcenter

manufacturing
process
management 13.0

Administering
Manufacturing
Planning
PLM00260 - 13.0
Contents

Getting started with administering Manufacturing Process Planner

1-1

General configuration and customizing tasks

Configure the commands in the context menu ─────────────────── 2-1
Configuring the business object types in the New dialog boxes ──────── 2-5
Hide a custom perspective ──────────────────────────────── 2-5
Defining which occurrence types display in paste and assign resource
commands ───────────────────────────────────── 2-6
Configure the update of multiple product views ────────────────── 2-6
Set up Manufacturing Process Planner for Product Configurator ──────── 2-7
Set up 4D planning ──────────────────────────────────── 2-8
Creating new search criteria for a broken link search ────────────── 2-10
Customizing the BOM line quantity ───────────────────────── 2-12
Specify a property value to be a combination of other property values ── 2-12
Configure incremental changes ─────────────────────────── 2-13
Make manufacturing change notices mandatory for BOP structures ──── 2-14
Configure manufacturing change notices (MCNs) ──────────────── 2-14
Restructure BOP product views using an upgrade utility ──────────── 2-16

Setting up the Custom Process View

Configure the Custom Process View ────────────────────────── 3-1
Modify the view using preferences ────────────────────────── 3-2
Modifying style sheets ────────────────────────────────── 3-3
Specify the tables and content ───────────────────────────── 3-4

Configuring 4G design in manufacturing

Configuring the comparison of design to manufacturing features ────── 4-1
Mapping property and attribute groups between design elements and BOM
lines ────────────────────────────────────────── 4-1

Administering 3D PDF generation

Configuring 3D PDF generation ──────────────────────────── 5-1
Import customized templates ────────────────────────────── 5-2
Upgrade the 3D PDF solution ────────────────────────────── 5-4
Configure 3D PDF report generation ───────────────────────── 5-4
3D PDF Report prerequisites ────────────────────────────── 5-5
Turn off generation of a printable report ────────────────────── 5-5
3D PDF reports ─────────────────────────────────────── 5-6
Customizing 3D PDF reports ────────────────────────────────── 5-6

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2

Create a 3D PDF report template ─────────────────────────────── 5-6

3D PDF report preferences ─────────────────────────────────── 5-7
Modifying the import script input file ──────────────────────────── 5-7
Customizable components ─────────────────────────────────── 5-8
Creating a template with LiveCycle Designer ──────────────────────── 5-8
Objects to retain in sample templates ──────────────────────────── 5-9
Adding new controls from the object library ─────────────────────── 5-11
Modifying JavaScript elements ─────────────────────────────── 5-11
Initializing the style sheet ────────────────────────────────── 5-11
Modifying the style sheet ─────────────────────────────────── 5-12

Administering standard text

Standard text overview ───────────────────────────────── 6-1
Prerequisites to using the standard text feature ────────────────── 6-2
Set up standard text ──────────────────────────────────── 6-2
Understanding the standard text template ───────────────────── 6-5
Using the standard text template ─────────────────────────── 6-6
Edit standard text templates ────────────────────────────── 6-6
Remove customization ────────────────────────────────── 6-8
Restore customization ────────────────────────────────── 6-9
Editing options ────────────────────────────────────── 6-10
Add BOM line properties ──────────────────────────────── 6-10
Add or modify template styles ──────────────────────────── 6-14
Remove symbols section ──────────────────────────────── 6-14
Add symbol section ─────────────────────────────────── 6-15
Specifying the location of the Add Symbol button ──────────────── 6-16
Importing standard text library structures from a legacy system ────── 6-17
Updating standard text instances using the update_stx_elements utility ─ 6-19

Administering structure cloning

Creating structures from templates overview ─────────────────── 7-1
Reusing process templates ─────────────────────────────── 7-1
Carrying over future incremental change when cloning ───────────── 7-2
Configuring how assemblies in context are cloned and replaced ─────── 7-3
Defining cloning rules ────────────────────────────────── 7-4

Administering manufacturing publish

Configuring the publish feature ──────────────────────────── 8-1
Understanding roles ─────────────────────────────────── 8-1
Example: creating a customized publish role ──────────────────── 8-2
Set preferences and environment variables ───────────────────── 8-3
Installing the transfer mode ────────────────────────────── 8-5
Defining alias files ───────────────────────────────────── 8-6
Building a sample alias file ─────────────────────────────── 8-7
Specifying end objects ───────────────────────────────── 8-14

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 3

© 2020 Siemens
Navigating through a PLM XML file ───────────────────────── 8-15
Strategies for working with alias files ──────────────────────── 8-16
Create a new publishing alias dataset ──────────────────────── 8-17
Update a publishing alias ──────────────────────────────── 8-17
Load or reload the alias file ────────────────────────────── 8-18
Create or edit publishing pages ──────────────────────────── 8-18
Creating manufacturing documentation in batch mode overview ────── 8-19
Enabling batch processing of publishing pages ────────────────── 8-19
Troubleshooting the PublishBatch translator ─────────────────── 8-20

Setting up enterprise bill of process (BOP)

Configuring the enterprise BOP ──────────────────────────── 9-1
Setting up scheduled part assignment resolution ───────────────── 9-4
Setting up logistics planning ────────────────────────────── 9-5
Line balancing reports ────────────────────────────────── 9-6
Customizing a line balancing report ───────────────────────────── 9-6
Customize the contents of the reports ──────────────────────────── 9-6
Line balancing report parameters ────────────────────────────── 9-7

Administering time data in the Time view

Configure new categories in the Time view ──────────────────── 10-1
MTM data card ────────────────────────────────────── 10-3
Configuring an MTM data card ─────────────────────────────── 10-3
Install MTM data cards ──────────────────────────────────── 10-4
Create your own data card ────────────────────────────────── 10-4
TiCon integration ───────────────────────────────────── 10-5
Understanding the Teamcenter to TiCon mapping ──────────────────── 10-5
Map attributes of time elements to activity properties ───────────────── 10-6

Configuring studies
Enable Study Manager ───────────────────────────────── 11-1
Set up study synchronization ───────────────────────────── 11-1
Study Manager preferences ────────────────────────────── 11-3

Administering EBOM and MBOM

Reasons for creating an MBOM ──────────────────────────── 12-1
Comparing the EBOM and MBOM ────────────────────────── 12-1
EBOM-MBOM preferences ─────────────────────────────── 12-2
Automatically creating an MBOM from an EBOM ───────────────── 12-4
Create an MBOM from a recipe ──────────────────────────── 12-6
Creating an MBOM using the me_create_mbom utility ───────────── 12-9
Reconciling EBOM and MBOM in a Multi-Site environment ───────── 12-18
EBOM to MBOM effectivity options ───────────────────────── 12-19
Delegating, overriding, or copying line properties from MBOM to BOP ── 12-23

4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Administering CAD BOM and part BOM alignments

Part BOM requirements ───────────────────────────────── 13-1
Set up CAD BOM smart search criteria ─────────────────────── 13-1
CAD and part BOM action handlers ───────────────────────── 13-2

Configuring in-context IDs (IDIC)

Understanding equivalence and in-context ID (IDIC) ────────────── 14-1
Setting up the search for components in other structures ─────────── 14-1
Understanding ID in context and assigned products ────────────── 14-2
Configuring the generation of smart IDICs ───────────────────── 14-5
Generate smart IDICs ────────────────────────────────── 14-5
Configuring the IDIC mechanism when using shared assemblies ────── 14-6
Stamp missing IDIC strings ─────────────────────────────── 14-6

Administering the import and export of manufacturing structures

Configuring PLM XML export ───────────────────────────── 15-1
Configuring custom primary objects for use with DIPA ───────────── 15-1
Configuring the import and export of dynamic in-process assemblies ─── 15-1
Configuring the export of end item assemblies ────────────────── 15-2

Configuring briefcase exchange of collaboration context

Key preferences for configuring briefcase exchange of collaboration context
───────────────────────────────────────────── 16-1
Configuring recursive ownership transfer ───────────────────── 16-2
Configuring automatic APN creation during export ─────────────── 16-3

Administering GD&T symbols

Displaying GD&T symbols and rich text in forms ───────────────── 17-1
Configure GD&T symbols and rich text in forms ───────────────── 17-1

Setting up rich client reports

Creating reports ───────────────────────────────────── 18-1
Troubleshooting reports in the rich client ───────────────────── 18-1
Configure reports in the rich client ───────────────────────── 18-3
View or print rich client reports with a Web browser ────────────── 18-5
Creating reports in the rich client ────────────────────────── 18-5

Configuring the accountability check

Setting up the accountability check ───────────────────────── 19-1
Publish accountability check settings ──────────────────────── 19-1
Configuring the inclusion rules ──────────────────────────── 19-2
Customize accountability check reports using a temporary XML file ──── 19-4
Add or remove accountability check report stylesheets ──────────── 19-6

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5

© 2020 Siemens
Configure the accountability check to use net effectivity ─────────── 19-8
Display an icon to indicate revision mismatches on BOP lines ───────── 19-8
Customizing the net effectivity user exit ────────────────────── 19-8
Accountability check batch mode ────────────────────────── 19-8
Running an accountability check in batch mode ───────────────────── 19-8
Running an accountability check or propagation at a specified time ───────── 19-9
Running an accountability check in batch mode using the acc_check_client utility
─────────────────────────────────────────────── 19-9
Run the acc_check_client utility from a script ────────────────────── 19-10
Using dynamic equivalence to locate matching EBOM and MBOM lines ─ 19-10
Modify accountability check closure rules to exclude dynamic in-process
assemblies ──────────────────────────────────── 19-11
Set up the accountability check to compare to intermediate data captures
──────────────────────────────────────────── 19-11
Using the two-tier accountability check utility ────────────────── 19-12

Glossary A-1

6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
1. Getting started with administering
Manufacturing Process Planner
Manufacturing Process Planner allows you to design a plan that details how to manufacture a product.
The manufacturing process plan includes a top-level structure of the process needed to manufacture the
product, as well as a detailed design of the individual processes and activities to be included in the plan.

As you build the process structure, you can assign resources to the various processes, operations, and
activities. You can also identify the specific locations within the plant where each operation and activity
will be performed.

You typically use Manufacturing Process Planner to design and manage the manufacturing processes for
large assemblies. Common tasks are:

• Assigning an engineering bill of materials (BOM) to a manufacturing BOM.

• Using enterprise bills of process (BOPs) to capture standards and best practices across the business as
generic processes and operations.

• Consuming 4GD design data into manufacturing process structures.

• Performing line balancing and time way planning.

• Creating work instructions for process data.

• Comparing structures to find missing parts in source or targets or differences in properties of the two
structures.

For many of these tasks, you must configure aspects of your installation, including setting various
preferences. For example:

• Configuring the enterprise BOP

• Configuring the accountability check

• Administering standard text

• Administering 3D PDF generation

Additionally, you can customize Manufacturing Process Planner features to suit your business needs. For
example:

• 3D PDF reports

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 1-1

• Add or remove accountability check report stylesheets

• Line balancing reports

1-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
2. General configuration and customizing
tasks
Configure the commands in the context menu
You can customize which menu commands are displayed in the context menu (the menu that appears
when you right-click an object) so that only the menu commands relevant to your tasks appear. You can
specify that the commands that appear when you right-click an object in a view housed in one
perspective are different than those that appear when you click the same type of object in a different
perspective. This allows you to tailor the user interface to different workflows and user needs.

You must have DBA privileges to complete this task.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-1

Context menu — before suppression Context menu — after suppression

1. Display the required menu command by adding the following extension to the plugin.xml file
located in portal\plugins\com.teamcenter.siemens.lookandfeel_10000.1.0:

<extension point="org.eclipse.ui.menus">
<menuContribution
allPopups="false"

2-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

locationURI="menu:window?after=additions">
<command
commandId="com.teamcenter.rac.cme.contextSuppression"
mode="FORCE_TEXT"
style="push">
<visibleWhen>
<reference
definitionId="com.teamcenter.rac.cme.mpp.inMainView">
</reference>
</visibleWhen>
</command>
</menuContribution>
</extension>

Note:
To activate the command you may need to register your client by double clicking on
genregxml under ..\Teamcenter Root\portal\registry. Without this the command will not be
visible.

2. Choose Window→Suppress Context Menus.

Note:
This command may be hidden in your installation. Your administration can display it.

Teamcenter displays the Save dialog box where you can create an XML file that stores the
suppression data or select an existing XML file that you want to modify.

3. Type the name of a new file or select an existing file to modify and click Save.

Teamcenter displays the Suppress Context Menus dialog box. This dialog box allows you to
specify the type of object for which the context menu is customized. Additionally, you select the
view, perspective, and application in which this customization is visible.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-3

4. Select the application, perspective, view, and type of selected object for which you want to limit
the context menu commands.

You can select any of the Open With commands to suppress entries in the Open With context
menu.

You can also suppress context menus in customized Manufacturing Process Planner perspectives.

5. Add the commands by typing their names in the Commands dialog box, selecting them from the
commands list, and adding them to the list on the right with the arrow.

6. Click OK.

Teamcenter saves the results in the XML file.

2-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

7. Make the configured menu available to different groups, roles, or users as follows:

a. Save the XML file from the previous step to a Context Menu Suppression dataset.

b. Add the name of the dataset to the TC_ContextMenuSuppression preference and publish
this preference to the required group, role or user.

Configuring the business object types in the New dialog boxes

To reduce the chance of error when Manufacturing Process Planner users select a new business object
type to create, you can specify which object types are available in the New dialog boxes for specific
users, groups, or roles. The filtering is dependent upon the type of New dialog box and selected object
type. You perform this configuration using the following preference:

MEFilteredChildTypes_type-of-new-dialog_type-of-selected-component

For example:

• MEFilteredChildTypes_Item_Item for the New Item dialog box opened on a selected item
• MEFilteredChildTypes_OP_Process for the New Operation dialog box opened on a selected process
• MEFilteredChildTypes_Item_None for the New Item dialog box when no selection is active

You then publish the preference to the appropriate user, group, or role.

Hide a custom perspective

As with all Teamcenter perspectives, you can hide a Manufacturing Process Planner perspective so that
users cannot see it in the user interface using the HiddenPerspectives preference. If you create your
own Manufacturing Process Planner perspective, you must perform the following steps to hide this
perspective using the HiddenPerspectives preference. The example uses a new perspective called
MyCustomizedPerspective.

1. Add the following information to the org.eclipse.ui.activities extension:

<activity
description="Turn off MyCustomizedPerspective
perspective"
id=”ID-of–MyCustomizedPerspective”
name=”MyCustomizedPerspective”
</activity>
<activityPatternBinding

activityId="com.teamcenter.rac.cme.mpp.MyCustomizedPerspective"
pattern="com\.teamcenter\.rac\.cme\.mpp/
com.teamcenter.rac.cme.mpp.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-5

MyCustomizedPerspective">
</activityPatternBinding>

The ID is the value assigned in the perspective definition in the plugin.xml file.

The pattern value is derived from the value of the ID in the customized perspective definition in the
plugin.xml file.

For example, if the customized perspective definition ID value is

com.rcpcompany.demo.ui.views.History, the pattern is then .*/com\.rcpcompany\.demo\.ui
\.views\.History.

2. Add the perspective name (MyCustomizedPerspective in the example) to the

HiddenPerspectives preference.

Teamcenter hides the custom perspective in the user interface.

Defining which occurrence types display in paste and assign

resource commands
In the MEDisplayOccurrenceType preference, you can define conditions to display which occurrence
types appear when pasting objects in the Manufacturing Process Planner rich client. This preference is
used, for example, when end users access the Paste As, Paste Special, and Assign Resource
commands and in the Occurrence Type column visible in bill of materials (BOM) views.

Note:
Regardless of how you configure the preference, when pasting objects with multiple occurrence
types, the system will only show occurrence types common to both the source and target. If no
common occurrence types are found, the end user receives a message informing him of that fact.

Configure the update of multiple product views

Teamcenter uses the Dispatcher infrastructure to update multiple product views. In addition to installing
this software using Teamcenter Environment Manager, you must also install the translator specific to
creating multiple product views—the Update Mass Product Views translator.

1. Check that VisAutomationApp is installed on the same machine on which Dispatcher is installed.

2. Set FMS_HOME as a system environment variable with the appropriate value and restart the
Dispatcher machine.

3. Install the Update Mass Product Views translator using the TEM installer.

4. Verify that the ACL rule for Dispatcher is set in Teamcenter.

2-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

5. Open Dispatcher_Root_Directory\Module\conf\translator.xml in a text editor and ensure the

isActive attribute in the TcUpdateProductViews extension is set to true.

6. Open Windows services and restart the following two services in the following order:

a. Dispatcher Scheduler

b. Dispatcher Module

7. Run Dispatcher client manually by starting Dispatcher_Root_Dir\DispatcherClient\bin

\runDispatcherClient.bat.

Teamcenter opens a console.

Set up Manufacturing Process Planner for Product Configurator

Note:
If you already have Product Configurator available for Structure Manager there is no need to
perform any of the following steps.

The administrator must install the following features using Teamcenter Environment Manager to
connect Product Configurator to Manufacturing Process Planner and Structure Manager.

1. Run Teamcenter Environment Manager (TEM) and navigate to the Features list.

2. Navigate to the Extensions branch and select Product Configurator and Product Configurator
Support for Structure Manager.

3. Complete the installation of the features in TEM.

The features you added provide access to Product Configurator.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-7

4. Restart Teamcenter and log on as administrator.

The restart is required to activate the new features.

5. Choose Edit→Options to open the preferences dialog box and set the Product Configurator
preference.

6. Click the Search button and type PSM in the Search On Keywords box.

Preferences that begin with PSM are listed.

7. Select PSM_enable_product_configurator and click Edit.

8. Type True in the Value box and click Save.

9. Click Close.

Set up 4D planning
Adding a time component to process planning to simulate and visualize construction over an extended
period of time is referred to as 4D planning. 4D planning is used in very large structures to ascertain
what parts are already assembled on a specific date in a specific part of the structure. For example, if
you build a ship, you may want to begin fitting the cabins with furniture. It is necessary to know if the
piping and electrical work is complete by April 30th to begin subsequent work. You can query your
structure, taking the date into consideration, to see what has been assembled by April 30th.

Teamcenter uses an embedded Schedule Manager view to help you associate scheduling information
with process planning operations. The Manufacturing – 4D Scheduling perspective already contains
this view, in addition to structure views to assist you. This is the same view that is contained in the
Schedule Manager application. Making a change in one changes the data in the other.

2-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

To configure 4D planning:

1. Install the 4D Planning extension using Teamcenter Environment Manager (TEM).

2. Set the time zone on the computer running the rich client to UTC (GMT). This is the only supported
time zone.

3. In the rich client, open the Organization application and modify the Calendar setting.

a. Set the calendar time zone to GMT (GMT +00:00).

b. Remove lunch breaks in the calendar by clicking Details next to the weekday entries and
modifying the times.

4. Set the following preferences:

Preference Value

MECopyIdInContextToAssignedLine true

SiteTimeZone Etc/UTC or Etc/GMT

ScheduleTaskAvailableAttributesWithRelations ScheduleTask.fdp0AssociatedProcesses

QS_QSEARCH_ENABLED true

QSEARCH_update_enabled true

QS_BBOX_GENERATION_ENABLED true

QS_BBOX_GENERATION_FROM_NX_ENABLED true

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-9

Preference Value

QS_TRUSHAPE_GENERATION_ENABLED true

QS_SPATIAL_ENABLED true

QSEARCH_foreground_processing_halted false

Teamcenter sets the following preferences for you automatically.

Preference Value

ME4DResultsViewDisplayNameColumnsShownPref Mfg0BvrProcess.bl_indented_title

Mfg0BvrProcess.ScheduledStartDate

Mfg0BvrProcess.ScheduledFinishDate

Mfg0BvrProcess.ScheduledCalculatedDuration

ME4DResultsViewColumnsWidthPref 45, 15, 15, 15

ME4DSearchCriteriaDate fdp0ScheduledStartDate

MEProcessIconPropertyNames start_date

MECopyIdInContextToAssignedLine true

Creating new search criteria for a broken link search

The Broken Links dialog box allows you to select a search criteria. All available search criteria are stored
in the MPP_BrokenLinkSearchCriteriaList preference. Each value in this preference is, in turn, a
preference that holds a list of properties contained in the search criteria. As an administrative user, you
can create your own search criteria and save them under a new criteria name. Doing so creates a new
preference of the same name as the search criteria that holds the list of properties you specified.
Teamcenter adds the name of the new preference to the list of available search criteria in the
MPP_DefaultCandidateSearchCriteria preference. In this way, the new search criteria that you created
is available to every user.

2-10 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Nonadministrative users can see these search criteria in the Broken Links dialog box. They can modify
them and save their changes to a user preference with the same name as the original search criteria
preference. The next time they use the search criteria, they see the values stored in the user preference
including their modifications. If they want to use the original search criteria that the administrative user
saved, they must delete the user preference.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-11

Customizing the BOM line quantity

Certain sites add dimensions at the end of each part name, resulting in a long BOM line name. These
dimensions at the end of the BOM Line column and the value in the Quantity column may run into
each other and confuse the user.

To avoid this, you can use the BOM Line Title column instead of the BOM Line column. Add the BOM
Line Title column, move it to the far left, and then remove the BOM Line column from the display.

You should then choose Tools → Options in Structure Manager and enter a custom title in the BOM
Line Title format for Items of type: Item box. For example, the following entry shows only the item ID
and name separated by two dashes, but no quantity value:

$bl_item_item_id — — $bl_item_object_name

Note:
As the Options dialog box lists only actual item types in Structure Manager, you cannot customize
process or manufacturing item types directly in this window. To do this, you must first choose
Options → Preferences and create a new preference for each applicable item type, for example,
BOMLine_Title_Format_OP or BOMLine_Title_Format_Process. You can then define the current
value of the preference name in the format shown in the example.

Specify a property value to be a combination of other property

values
You can automate the generation a property value for BOM lines to be based on the concatenation of
other properties of the BOM line. The combination of these properties results in a unique string that
Teamcenter assigns as a new property value.

2-12 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• Define the properties that are combined to create the new property value in the
MEIdGenerationPropertySetting preference.
These can be any single-valued BOM line property. If the property value is empty, Teamcenter uses
that empty value. Two typical properties that you may combine are item ID and absolute
transformation matrix.

• Define tolerances for translation and rotation in the following preferences:

ME_angular_tolerance
ME_translation_tolerance

Note:
If you use a CAD integration with Catia or other CAD application and use BOM (Bill of Materials)
to BOM or BOM to BOE (Bill of Equipment), updates sometimes cause small BOM CAD tolerance
variations so that many parts in the model show as changed during advanced accountability
checks. To reduce the number of outliers during such checks, increase the
ME_angular_tolerance and ME_translation_tolerance values to reduce the tolerances.

Alternatively, you can:

• Run the me_stamp_ids utility to generate the new property value for an entire structure, based on a
closure rule.

• Create a workflow process based on the ME-stamp-ids-AH action handler to automate the process
from the user interface.

When using the utility or action handler, you can specify whether Teamcenter allows duplicate property
values in the MEIdGenerationAllowDuplicates preference.

Configure incremental changes

If you plan to use incremental changes to control the manufacturing process, you must complete the
following steps:

1. By default, incremental changes are not enabled. To enable incremental changes, set the
Incremental_Change_Management preference to true.

2. Configure the change types to use with incremental change with the Change Viewer application.

3. By default, all incremental changes (configured and unconfigured) are visible to the user. To hide
unconfigured changes, set the ShowUnconfiguredByChangeEffectivity preference to true.

4. Define a release status that is attached to an incremental change when the user first creates it. For
example, the following setting creates each incremental change with a Pending status.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-13

Incremental_Change_ReleaseStatus=Pending

The status must already exist and have an Access Manager rule that allows write access to objects
with this status.

5. Ensure an In IC Context rule is available in Access Manager, allowing a user write access to a
released structure.

Make manufacturing change notices mandatory for BOP structures

You can configure the database so that Manufacturing Process Planner and Part Planner end users must
set a manufacturing change notice (MCN) before they can edit certain types of BOPs. If they attempt to
edit a BOP in this configuration, or open a collaboration context containing such a BOP, they will receive
a warning.

A Change Notice must be set before editing this structure.

Assuming that change management is installed and the site preference

MEMCN_management_enabled is set to true, you can configure the types of structures for which the
warning is displayed by adding the item type of the BOP's top line to the role-based preference
MEMCN_change_notice_mandatory_types.

Example:
Process

Mfg0MEPlantBOP

You can also set MCN requirements by a structure's root node type and release status name.

Configure manufacturing change notices (MCNs)

An engineering change notice (ECN) records engineering design changes to a product. Manufacturing
change notices (MCNs) are essentially ECNs that are specifically intended for manufacturing rather than
engineering needs. An MCN is not a COTS (commercial-off-the-shelf) object and can be any custom
change notice revision that overrides the following business object constants.

As an administrator, you can modify the constants as shown.

2-14 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Note:
MCN capabilities require a special license and installation to work in Teamcenter. After installation,
set the MEMCN_management_enabled preference to true to enable change notice revision
commands in Manufacturing Process Planner.

To allow users to set statuses on an MCN, change notices must have valid release statuses defined in the
MEMCN_release_statuses preference.

You can make change notices mandatory before users may edit certain types of structures. To configure
such types of structures, adding the item type of the structure's top line to the role-based
MEMCN_change_notice_mandatory_types preference.

Example:
Process

Mfg0MEPlantBOP

Use the MEMCN_release_revision_mode preference to control how statuses are created on item
revisions being tracked by a change notice revision. Use closure rules, such as a rule to exclude tools
with a status of TCM Released, to exclude items from being captured by a change notice.

Tip:
You can customize change notice report layout and elements using preferences with the suffix
MECTRev.

Note:
When a subassembly node is assigned from an EBOM to an MBOM, change notices track the
assigned node and all of its children because the default value of the preference
MEMCN_solution_object_collection_rule is GetChangedProcessLines. To add custom business
objects to change notices, you must add them to the closure rule GetChangedProcessLines. If an
EBOM line type is different from MBOM (for example, part versus item), you can modify the
closure rule in this preference to define which lines are assigned and which are not. For example,
to keep the assigned line of type PART from being added to the change notice, define the closure
rule:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-15

BOMLine:BOMLine:bl_all_child_lines:SKIP:PRIMARY.bl_item_object_type=
=
"Part"

Restructure BOP product views using an upgrade utility

If you are upgrading from earlier versions of Teamcenter to the 11.6 release, you may encounter some
problems with product views. You can use the upgrade_pv_with_visiblelineinfos utility to identify and
correct broken product views.

Using the utility with various mode types lets you upgrade product views in different ways. When
mode=bopwithpv, you can generate an XML file that lists all affected product views.

Example:
C:\Siemens\Tc116\tcroot\tc_menu> upgrade_pv_with_visiblelineinfos -u=zz -p=zz g=myGroup -
mode=bopwithpv -outputfile=13Nov2018.xml -log=13Nov.log

The file lists each individual BOP with its itemID and other attributes, along with each affected product
view (PV). You can compare the product views in the XML by opening the BOPs in Teamcenter and
performing a product view search.

You can also extract item IDs for product views that need to be upgraded by setting -
mode=pvsneedingmigration. The XML file can be used to upgrade all affected product views reported in
a BOP by running the utility once more and setting rootitemid to the BOP itemID.

Example:
C:\Siemens\Tc116\tcroot\tc_menu> upgrade_pv_with_visiblelineinfos -u=zz -p=zz g=myGroup
rootitemid=L029084 -log=13Nov.log

Once you have run the utility, you can verify that the product views have been upgraded by running the
utility again as in the first example. If fixed, the product views do not appear in the resulting XML file.

You can also batch update all BOPs in the XML file by setting -mode=upgradepv and specifying the XML
file as the inputfile.

2-16 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Example:
C:\Siemens\Tc116\tcroot\tc_menu> upgrade_pv_with_visiblelineinfos -u=zz -p=zz g=myGroup -
mode=upgradepv -inputfile=13Nov2018.xml -log=13Nov.log

If you have a collaboration context (CC) that contains multiple BOPs, you can also use the utility to
upgrade all BOPs contained in it by extracting BOP IDs.

Example:
C:\Siemens\Tc116\tcroot\tc_menu> upgrade_pv_with_visiblelineinfos -u=zz -p=zz g=myGroup -
cc=myCC -log=13Nov.log

To force upgrades to affected views in a BOP and thereby verify all are updated, you can set -
mode=upgradeallpvs

Example:
C:\Siemens\Tc116\tcroot\tc_menu> upgrade_pv_with_visiblelineinfos -u=zz -p=zz g=myGroup -
mode=upgradeallpvs -log=13Nov.log

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 2-17

2-18 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
3. Setting up the Custom Process View
Configure the Custom Process View
You can view a process plan in an alternative view called the Custom Process View. This view is based
on configurable style sheets. Additionally, a variety of preferences define the information displayed in
the view.

To configure the Custom Process View, you can do any of the following:

• Modify style sheets for the Mfg0BvrProcessSummary and Mfg0BvrOperationSummary datasets.

• Modify the types of tables on the right side of the view and the occurrence types that are displayed in
these tables.

• Modify the commands available in the toolbars of the child lines and consumed items tables.
You can add or remove commands by setting the preferences selected in the
MECustomViewChildLinesCommandNames and
MECustomViewConsumedItemsCommandNames preferences.

• Set the preference MECustomViewShowMfgFeatures to True to enable the Consumed

Manufacturing Features section of the Custom Process View. This section contains Weld Point, Arc
Weld, and Datum tabs for users who want to see immediate details on manufacturing features
included in the station or operation selected in the Content section.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 3-1

Modify the view using preferences

Use the Preferences By Filters dialog box to access and modify the toolbars and tabs in the Custom
Product View.

Note:
To view all related preferences, choose Edit→Options, select Search, and type mecustomv in the
top Preference By Filters line.

You can use the following preferences to define the appearance of the Customer Process View.

• Define the names of the style sheet datasets in the following preferences:

Mfg0BvrProcess.SUMMARYRENDERING

Mfg0BvrOperation.SUMMARYRENDERING

• Define the commands available for the main table on the left. These commands are shown above the
table.

MECustomViewChildLinesCommandNames

• Define the commands available for each of the child tables on the right in this preference:

3-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

MECustomViewConsumedItemsCommandNames

• Define the tables available on the right side:

MECustomViewConsumedItemsOccTypes

• Define the properties shown as columns and the widths of these columns in the main table on the
left:

MECustomViewChildLinesColumnsShownPref

MECustomViewChildLinesColumnWidthsPref

• Define the properties shown as columns and the widths of these columns in the tables on the right:

MECustomViewConsumedItemsColumnsShownPref

MECustomViewConsumedItemsColumnWidthPref

Modifying style sheets

1. Open My Teamcenter.

2. In the quick search, search for the Mfg0BvrProcessSummary or the Mfg0BvrOperationSummary

dataset.

3. Open the dataset in the Viewer view.

Teamcenter displays the XML content of the style sheet.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 3-3

4. Modify the existing tags and click Apply.

Ensure that you have a backup copy of each of the style sheets in order to return to the default
configuration if necessary.

5. Send a process from My Teamcenter to Manufacturing Process Planner. If the Custom Process
View is already open, close it.

6. Open the Custom Process View view for that process line by right-clicking the process and
choosing Open With→Custom Process View.

The changes you made in My Teamcenter are visible in the Custom Process View in the order specified
in the XML.

Specify the tables and content

The list of tables that appear on the right side of the Custom Process View is specified in the
MECustomViewConsumedItemsOccTypes preference. The following table lists the values you must
specify in this preference to display various tables.

3-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

The preference values have the following format:

relation-property-type:occurrence-type

Table type relation-property-type occurrence-type

All Materials Mfg0all_material MEAssemble

MEAssign
MEConsumed
MEDisassemble
MEHandle
MEOther
METarget

Allocated Features Mfg0allocated_features MEFeatureAssign

MEWeldPoint

Assigned Work Area Mfg0assigned_workarea MEWorkArea

Consumed Material Mfg0consumed_material MEConsumed

Disassembled Material Mfg0disassembled_material MEDisassemble

Handled Material Mfg0handled_material MEHandle

Other Material Mfg0other_material MEOther

METarget

Used Equipment Mfg0used_equipment MECompoundResource

MEPlantSpecificTool
MEResource
METool

You can add additional table types by checking the Business Modeler IDE for more occurrence types.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 3-5

3-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
4. Configuring 4G design in manufacturing
Configuring the comparison of design to manufacturing features
If you work with design features in 4th Generation Design (4GD), you can assign these features to the
MBOM when working in Manufacturing Process Planner. The design features are stored in design
container elements in 4GD. During the assignment action, Teamcenter copies the mapped property
values from the design feature to the corresponding properties on the BOM line of the manufacturing
feature. The mapped attribute group properties are copied to their corresponding form properties on the
item revision. The forms themselves that contain mapped properties to be copied are created as part of
the assign process.

To enable the comparison, you must configure the mapping of the properties between the design
features and the manufacturing features.

The following constants affect the behavior of the assignment process:

• Cpd0DFToBOMPropertyMapping global constant

Specifies the design feature properties that are mapped to form properties on a BOM line.

• Cpd0DFPropertiesForMBOM global constant

Specifies the initial set of properties carried over during assignment. Your administrator can define a
different set of properties for assignment based on a feature type.

• CPD0AttachToItemRevision business constant

Specifies whether attachments are associated to the item revision or BOM line in the context of the
root level.

• Cpd0ItemTypeForDesignFeature business constant

Specifies what type of item is automatically created when the corresponding design feature is
assigned to the MBOM.

Mapping property and attribute groups between design elements

and BOM lines
When assigning a design element into a manufacturing structure, some of the properties of the design
element are copied into the new BOM line. The mapping of design element properties to BOM line
properties is based on the values of the Cpd0DEToBOMPropertyMapping global constant in the
Business Modeler IDE. This constant has the following format:

BOM-line-property:design-element-property

For example:

Bl_absolute_transform:DE_absolute_transform

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 4-1

Bl_effectivity:DE_effectivity
Bl_note_type1:DE_custom_attribute1

The selection of properties that are carried forward during the assign process is specified in the
Cpd0DEPropertiesForMBOM global constant. The value of this constant consists of a list of design
element properties, for example:

DE_absolute_transform
DE_effectivity
DE_custom_attribute1

The properties that are carried forward to the BOM line are the properties that are available for
propagation after running an accountability check.

Additionally, if the design element has an associated attribute group, these attributes are copied to a
designated form on the BOM line. The mapping between attribute group and form type is specified in
the Cpd0DEAttrGroupTypeToFormType global constant. This constant has the following format:

attribute-group:form-type

For example:

EngAttributes:FormEngAttributes

Caution:
You should only map one attribute group to one form. Mapping multiple attribute groups to one
form results in errors in the partial match report of the accountability check.

4-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
5. Administering 3D PDF generation
Configuring 3D PDF generation
Teamcenter enables you to create interactive 3D documentation reports that derive directly from
process data stored in the Teamcenter database. The reports are in PDF format and contain process
information and 3D data. 3D PDF reports always consist of a single page.

Teamcenter uses graphic data stored in datasets attached to the process structure. The data originates
from Teamcenter or Process Simulate. The recipients of the report do not require Teamcenter to view
them; Adobe Acrobat Reader (Version 9.4.3 or later) is sufficient.

Additionally, you can do the following:

• Update existing reports after making changes to the process in Teamcenter.

• Distribute reports as work instructions for the shop floor.

To assist you in quickly creating and formatting effective 3D PDF reports, Siemens provides the following
standard templates:

• Templates for use when data originates in Teamcenter:

• 3DPDF Work Instructions

• 3DPDF Rich Textual Work Instructions

• 2DPDF Work-instructions

• 2DPDF Work Instructions with 2D Images

• Templates for use when data originates in Process Simulate:

• 3DPDF Work Instructions (Process Simulate)

• Animated PDF Work Instructions

Creating a typical 3D PDF report can be time-consuming. Therefore, the Teamcenter external server
(ETS), consisting of Dispatcher Server and translators, is used to generate the report remotely and free
up your computer for other tasks.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-1

Import customized templates

Teamcenter is installed with default 3D PDF templates to suit many needs. If, however, you design your
own customized 3D PDF templates, you must import them, as follows:

1. Prepare the following import files:

• PDF report file

• Thumbnail image file in JPG format

This is used by the 3D PDF wizard to represent the template. The recommended size is 94x85
pixels.

• Style sheet file in XSL format

• JavaScript file in JS format (not required for 2D reports)

• Transfer name file in XML format

The name of this file is used to name the transfer mode dataset.

The import files for the default templates are located at Teamcenter_root_directory\ install
\cmtmes\pdftemplates. You can duplicate any of these and use them as a starting point for your
customized files.

2. Compose an XML file listing the import files and other information, as shown in the following
example:

<?xml version=”1.0” encoding=”utf-8” ?>

-<ME_3DPDF_ImportData>

-<Templates>

-<TemplateInput name=”PDF_Template”>

-<PDF file=”.\PDF_Template.jpg” type="binary”/>

-<Thumbnail file=”.\PDF_TemplatePreview.jpg” type=”binary”/>

-<Stylesheet file=”.\PDF_Stylesheet.xsl” type="text”/>

-<DynamicsJS file=”.\PDF_JavaScript.js” type="text”/>

-<TM name=”.\PDF_ExportTM” file=”.\ME_Gen3DPDF_ExportTM.xml”

overwrite=”false”/>

5-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

-<Contain2D val=”False”/>

-<Contain3D val=”True”/>

-<ContainSimulation val=”False”/>

-<DataSource val=”TC”/>

-</TemplateInput>

-</Templates>

-</ME_3DPDF_ImportData>

The first entry contains the TemplateInput name node. This is the name of the dataset in
Teamcenter and is displayed by the 3D PDF wizard when creating the report.

• Nest the import files under the TemplateInput name node.

• Configure the following parameters:

• Contain 2D
Set to True if the 3D PDF report contains 2D elements; otherwise, set to False.

• Contain 3D
Set to True if the 3D PDF report contains 3D elements; otherwise, set to False.

Note:
If your report contains both 2D and 3D elements, set Contain 2D and Contain 3D to
True.

• ContainSimulation
Set to True if the 3D PDF report contains simulations originating in Process Simulate;
otherwise, set to False.

Note:
If the data source for the report is Teamcenter, set ContainSimulation to False.

• DataSource
If the data source for the report is Teamcenter, set this parameter to TC; if the data source is
Process Simulate, set it to PS.

• Run the install_mes_templates.exe import script to install the template.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-3

• The script is located at Teamcenter_root_directory\bin\.

• Run the following command from the command line: install_mes_templates -u -p -g -file.

■ -u=administrative_user

■ -p=password

■ -g=group

■ -file=inputFile.xml

3. Add the names of the new templates to the ME3DPDFAllowedReportTemplates preference.

Upgrade the 3D PDF solution

After upgrading to the next version of Teamcenter, you must perform several steps to upgrade the 3D
PDF solution.

For more information, consult the Help_Patching_3D_PDF_Solution.txt file found in the following
directory:

Teamcenter-root\install\cmtmes

Caution:
Do not overwrite 3D PDF templates as they may be replaced when you upgrade to the next
software version. Make a copy and modify the copy.

Configure 3D PDF report generation

Teamcenter uses the Dispatcher infrastructure to generate 3D PDF reports.

1. Verify that the VisAutomationApp and Professional or Mockup components of Lifecycle

Visualization are installed on the same host on which 3DPDF Translator is installed.

2. On the same host, define the TC3DSS_ENABLE_PRUNED_LAUNCH system variable and set it to
True.

3. Set FMS_HOME as a system environment variable with the appropriate value and restart the
Dispatcher host.

4. Use TEM to do the following:

• Install Dispatcher Client for Rich Client, Dispatcher Server, and Dispatcher Client.

5-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• Install the Generate 3D PDF Reports translator.

• Install the Work Instruction templates.

5. For four-tier installations, use the Web Application Manager to add Dispatcher Client for Rich
Client Solution to the third stage.

6. Verify that the ACL rule for Dispatcher is set in Teamcenter.

7. Open Dispatcher_Root_Directory\Module\conf\translator.xml in a text editor and ensure the

isActive attribute in the Tc3DPDFTrans extension is set to true.

8. Open Windows services and restart the following two services in the following order:

a. Dispatcher Scheduler

b. Dispatcher Module

9. Run the Dispatcher client manually by starting Dispatcher_Root_Dir/DispatcherClient/bin/

runDispatcherClient.bat.

Teamcenter opens a console.

3D PDF Report prerequisites

The following are required to execute and view 3D PDF reports:

• Lifecycle Visualization license (Teamcenter lifecycle visualization professional or Teamcenter lifecycle

visualization mockup) on the translator machine

• Acrobat Reader (version 9.4.3 or later) on the client machine

• Teamcenter Manufacturing 3D PDF documentation license on the same machine as the Teamcenter
licenses

Turn off generation of a printable report

When a 2DPDF Work Instructions report is generated, by default, Teamcenter additionally creates a
printable version of this report and attaches it as a dataset to the selected process line for which the
report is being generated. You can turn off the generation of this printable report in the template’s
properties.

1. In My Teamcenter, search for and open the 2DPDF Work-instructions dataset.

2. Check out the properties.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-5

3. In the Template Specification property, click the Expand to Modify button.

4. Select PRINT_VERSION=TRUE and modify to PRINT_VERSION=FALSE.

5. Click the Replace Selected Objects button .

6. Click Save and Check-In in the Edit Properties dialog box to save the changes.

3D PDF reports

Customizing 3D PDF reports

By default, Teamcenter delivers a variety of templates that it uses to create 3D PDF reports. You can use
these templates as a basis to create your own templates that reflect the business needs of your
company.

Caution:
Do not overwrite these templates as they may be replaced when you upgrade to the next software
version. Make a copy and modify the copy.

The 3D PDF mechanism is based on having a dataset that contains specific document types and
relations. When creating your own template, you must be careful to include all the required documents
and create the required relations so that the mechanism functions properly.

To assist you with creating the required files and relations, Teamcenter provides you with an import
utility, install_mes_templates.exe, that creates the dataset containing files and relations that you can
modify. As input, this utility uses an XML file that describes the contents of the dataset.

Create a 3D PDF report template

1. Run a dataset search on the *PDF* string to locate all 3D PDF report datasets in My Teamcenter
and choose the one that most closely resembles the report you want to create.

2. Open the named references and locate each of the files contained in the named reference list. The
following files are contained in the dataset:

5-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• A JavaScript file that you can use to modify various control behaviors.

• A PDF file whose layout you can modify using Adobe LiveCycle Designer.

• An XSL style sheet that you can use to modify the format of the report and to add new
properties.

• A JPEG file that is used as a thumbnail to display the new report template in the list of available
templates in the Generate 3D PDF Report wizard.

3. Copy each of these files under a new name and place them in the same directory as the originals.

4. Modify the XML file that specifies how to populate the dataset.

5. Run a dataset search on the *PDF* string to locate the dataset in My Teamcenter.

6. Open the named references and identify the following files in the dataset:

7. Modify the 3D PDF preferences. In particular, add the template name to the
ME3DPDFAllowedReportTemplates preference.

3D PDF report preferences

The following preferences affect the behavior of the 3D PDF report generation:

• ME3DPDFAllowedReportTemplates
Lists all 3D PDF report templates. If you add a new template, you must add the new template name to
this preference. By default, it lists all the templates included with the Teamcenter installation.

• M33DPDFReportDatasetType
Specifies the dataset type of the 3D PDF report. You generally do not have to change the value of this
preference.

• ME3DPDFAllowedImageDatasetTypes
Lists supported Teamcenter image types for 2D PDF reports.

Modifying the import script input file

The import utility is used to create a dataset containing all the files and relations required for a 3D PDF
report. You must create an XML file as input. The XML file contains the paths to the required files and
additional parameters required to create the dataset. You can view the following sample file:

tc_root_directory\install\cmtmes\pdftemplates\TemplateInfo.xml

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-7

Customizable components

You can customize the following components when using 3D PDF templates:

• PDF template default

You can modify PDF templates and create new PDF templates using Adobe LiveCycle Designer, a tool
installed with the Acrobat Pro Extended software. It is a simple WYSIWYG editor that helps with the
authoring of PDF templates. Using this tool, you can create your own report layout, use various
controls such as text boxes, list boxes, drop down lists, and tables. Each control in the PDF template
has an option to add JavaScript that is executed on different events.

Note:
Multipage reports are Acrobat forms and are created using Adobe Acrobat Pro only. They are not
created using LiveCycle Designer.

• Style sheet
PLM XML exported from Teamcenter is not hierarchical. You must write an XSL style sheet that parses
the PLM XML and extracts and rearranges data as required. The PDF template reads this XML using
JavaScript and populates different controls.

• Closure rules
Closure rules are part of the standard Teamcenter infrastructure. Closure rules help you interpret the
PLM XML. You may need to create new closure rules or modify existing ones to export custom
attributes or existing attributes that are currently not exported. For example, sample closure rules
provided with setup include a new closure rule defined for the default implementation. You must
create this rule before using the report. You can add additional clauses to the closure rule as needed.

Creating a template with LiveCycle Designer

Teamcenter delivers two Process Simulate and four Teamcenter templates that you can modify to create
a template reflecting your needs. You find these in the cmtmes\install\pdftemplates directory.

The following figure displays a Process Simulate template.

5-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

You create templates using Adobe LiveCycle Designer. You can either start from a blank template by
choosing Use a Blank Form or start by importing existing templates. Siemens Digital Industries
Software recommends that you build a new template based on one of the sample templates provided.
This ensures that the core JavaScript support required for some basic features is automatically imported.

Objects to retain in sample templates

There are several objects that are essential to the proper functioning of 3D PDF document generation. To
ensure that your new template works properly, you must retain some objects in the sample templates.
This example uses the U3D template to describe these objects as it is a superset of all such objects that
are used for 3D PDF document generation with U3D or PRC data.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-9

• A3DR_3DFrame
This button is replaced with the 3D annotation at runtime during report generation. The dimensions
of the button are used for the 3D annotation area. It is essential that the caption of the button is
retained as A3DR_3DFrame. You can change the size of the button or the 3D annotation to suit your
needs.

• Populate Steps
This is a hidden button responsible for initializing the PDF the first time it opens. This is handled by
the JavaScript on the initialize event of this button.

• Setup3DButton
This is a hidden button responsible for setting up 3D annotation and setting the view associated with
the first step in the 3D annotation. This is achieved by the JavaScript on the docReady event of this
button.

• Change3DViewButton
This is a hidden button responsible for switching views in the 3D area on step selection. Views
(snapshots in Process Simulate) can be associated with operations during generation of the U3D/PRC
files using the Create 3D Documentation command in Process Simulate. This is achieved by the
JavaScript on the form::ready event of this button.

• TextField1
This stores the index used to retrieve the global variables from the global variable list.

5-10 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• 3D simulation buttons
Each button has associated JavaScript on the click event that has code to achieve the required
behavior.

• Button1 (Rewind)

• Button2 (Pause)

• Button3 (Play)

• Button4 (Play All)

Adding new controls from the object library

You can choose from a variety of controls to design your PDF template. Drag the desired control from
the Object Library area to the Design View area.

Modifying JavaScript elements

You can use the script editor included with Adobe LiveCycle Designer to view and modify JavaScript code
on various controls.

Initializing the style sheet

You can modify the style sheet to suit your needs but you cannot modify the following sections of the
style sheet. These sections are required by the Generate 3D PDF Report wizard.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-11

When you create a 3D PDF, Teamcenter creates an Adobe XML file. The following section parses that
XML file:

var doc=event.target;
//For consistent highlighting of report fields
app.runtimeHighlight=false;
var inputStream=doc.getDataObjectContents(“TCXMLData”);
var A3DXMLData=util.stringFromStream(inputStream);
A3DXMLData=A3DXMLData.substring(A3DXMLData.indexOf(“<TCXML”));
myTCxml=newXML(A3DXMLData);

The following initializes or adds a global variable to the global variable list. This is necessary to work
around a problem with the 3D PDF where Adobe updates all open PDFs.

if(typeof indexCounter===”undefined”)
{
indexCounter=1;
objectsListArray=newArray();
ViewListArray=newArray();
}
else
{
indexCounter=indexCounter+1;
}
objectsListArray[indexCounter]=newObject();
ViewListArray[indexCounter]=newObject();
TCXMLProcessStep.TextField1.rawValue=indexCounter.to.String();

Modifying the style sheet

Every template has its associated style sheet. You can modify this style sheet by changing the format or
adding new properties to the report.

The following extensions are exposed by the translator.

Mandatory extensions

• isIdAvailable
This extension is used in Process Simulate based templates and in Teamcenter templates for product
views only. In the Generate 3D PDF wizard, a user can select which process, operations, and product
view are available in the report. Similarly, a user can select such objects in Process Simulate during
creation of 3D PDF data. This information is stored in XML files. During parsing of the PLM XML using
XSL, this API is used to identify whether the given object is selected by the user.
Syntax

Boolean isIdAvailable(int-type, string absolute_occcurence_id)

5-12 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Input

Parameter Description

int-type Specifies the type of the input. Possible values are:

1 Represents a process or operation.

2 Represents a product view or snapshot.

absolute_occcurence_id Specifies the absolute occurrence ID of the object in

question.

Output

Output Description

True Object is selected by user.

False Object is not selected by user.

Example
Refer to the style sheet contained in the 3DPDF Work instructions (Process Simulate) dataset.

• AddOccIdToCloneStableIdMap
This extension can be used in Teamcenter based templates only. In the Generate 3D PDF wizard, a
user can select which process, operations, and product view are available in the report. This
information is stored in XML files. During parsing of the PLM XML using XSL, this API is used to
identify whether the given object is selected by the user. Additionally, this API also allows part and
tool selection in the generated 3D PDF report. To do this, call this API for parts and tools during
parsing of the PLM XML.
Syntax

Boolean AddOccIdToCloneStableIdMap (string curr-occurrence-ID, string parent-occurrence-

ID, string current-cloneStableID, string type)

Input

Parameter Description

curr-occurrence-ID Occurrence ID of currently parsed line (process, operation,

part, or tool)

parent-occurrence-ID Occurrence ID of parent process or operation

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-13

Parameter Description

current-cloneStableID Clone stable ID of the currently parsed line

type Type of the object. This is an optional parameter that you pass
for process and operation revision only. To use this API for
parts and tools, you do not have to pass this parameter.
The following options are possible:

4 If currently parsed line is a process revision

8 If currently parsed line is an operation revision

20 If currently parsed line is a direct child process of a

root line

24 If currently parsed line is a direct child operation of a

root line

32 Include even if it is not selected by the user for a

process and operation

Output

Output Description

True Object is selected by user.

False Object is not selected by user.

For parts and tools, this API does not return any value.
Example
Refer to the style sheet contained in the 3DPDF Work instructions dataset.

Optional extensions

• getDefaultView
This extension returns the default product view or snapshot the user has selected for the current
process or operation revision.
Syntax

string getDefaultView(string curr-occurrence-ID)

Input

5-14 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Parameter Description

curr-occurrence-ID Absolute occurrence ID of the currently parsed line

(process or operation)

Output
Returns the UID (for Teamcenter templates) or name (for Process Simulate templates) of the snapshot
or default view selected by the user.
Example
Refer to the style sheet contained in the 3DPDF Work instructions dataset (for Teamcenter) and the
3DPDF Work instructions (Process Simulate) (for Process Simulate).

• isOfRequiredType
This extension identifies whether the currently parsed element is a part or a tool. This is required
because Teamcenter differentiates between parts and tools according to a preference that can be
modified.
Syntax

string isOfRequiredType (int-type, string occurrence_type)

Input

Parameter Description

int-type Specifies the object to check.

0 Checks for tools

1 Checks for parts

occurrence_type Occurrence type of the currently parsed line

Output

Output Description

True occurrence_type matches the specified int-type

False occurrence_type does not match the specified int-type

Example
Refer to the style sheet contained in the 3DPDF Work instructions dataset (for Teamcenter) and the
3DPDF Work instructions (Process Simulate) (for Process Simulate).

• generateGDTConversion

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-15

This extension converts the given string to HTML format that represents the correct replacement of
GD&T symbols. Teamcenter checks whether the given string contains any GD&T character and
converts it to the proper format so it can be displayed in the PDF report (text field with rich text
support).
Syntax

string generateGDTConversion (string description)

Input

Parameter Description

description string that can contain GD&T symbols

Output
Returns a formatted HTML string that can be displayed in the report text field.
Example
Refer to the style sheet contained in the 3DPDF Work instructions dataset (for Teamcenter) and the
3DPDF Work instructions (Process Simulate) (for Process Simulate).

• ImportImage
This extension imports the given image in the PDF report as an attachment that can later be accessed
by the report.
Syntax

string ImportImage (string UID)

Input

Parameter Description

UID UID of the image file that is to be imported

Output
Returns the name with which the image file is imported into the 3D PDF report. This name is used in
the 3D PDF report to access the imported file.
Example
Refer to the style sheet and PDF file template contained in the 2DPDF Work-instructions dataset

• ImportTWIPDFFile
This extension imports the specified textual work instructions (in PDF format) into the 3D PDF report
without any content loss.
Syntax

string ImportTWIPDFFile (string UID)

5-16 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Input

Parameter Description

UID UID of the textual work instruction PDF that needs to be

converted

Output
Returns the name with which the textual work instruction is imported into the 3D PDF report. This
name is used in the 3D PDF report to access the imported file.
Example
Refer to the style sheet and PDF file template contained in the 3DPDF Rich textual work instructions
dataset

• addSpecific
This extension adds specified product views to the PDF report, even if they are not selected by the
user in the wizard.
Normally, when you use the IsIdavailable API for a product view, Teamcenter checks whether the
user has selected the specified product view in the wizard or in Process Simulate and if selected,
returns a value of true. If, however, you want a product view in the 3D PDF report even if it is not
selected by the user in the wizard, or want only one product view in the report even if the user selects
all product views in the wizard, you can use this API to specify the desired product views.
Syntax

addSpecific(int-type, string absolute_occcurence_id)

Input

Parameter Description

int-type Type of the object. Only one type is supported:

2 Represents product views or snapshots

absolute_occcurence_id Absolute occurrence ID of the currently parsed line

(process or operation)

Example
Refer to the style sheet contained in the Part list with 3D dataset

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 5-17

5-18 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
6. Administering standard text
Standard text overview
Teamcenter enables creating work instructions using standard text as building blocks. These work
instructions are associated with operations or processes in the process structure.

The standard text library is a Teamcenter structure comprised of standard text folders and standard text
elements nested under the folders. Standard text is associated with standard text elements and is
accessible in the Teamcenter Attachment pane.

The benefits of standard text include:

• Standardization and consistency of work instructions throughout the entire organization.

• Managing standard text content. Standard text enables you to write once only and reuse the same
text many times.

• Easy maintenance of up-to-date work instructions when products are upgraded. Make a single change
in a procedure and propagate the change through all the relevant documents.

• Improved accuracy. Work instructions are intrinsically connected with the process structure; they are a
textual expression of the manufacturing process.

• Work instructions are composed by the planners or engineers who designed the product, increasing
accuracy.

• Standard text is stored in the Teamcenter database, enabling you to search for text by its ID, name, or
the text itself.

• Easy localization.

• Easy transfer of documents between different virtual engineering systems.

Typically, there are three user roles involved in creating work instructions:

• Administrator
Responsible for creating and maintaining standard text and work instruction templates. If required,
the administrator can configure different system templates for standard text and work instructions.
The administrator can change these templates or create new ones according to organizational
requirements. The templates are in Microsoft Word DOCX format and are associated with a dataset
object.

• Librarian

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-1

Responsible for creating standard text libraries, managing standard text folders and elements, writing
standard text, and creating and managing standard text symbols. Standard text is written in a generic
style so that it can be reused in varying contexts. An example of standard text is a procedure
describing how to mount a wheel on a car and this can be reused in multiple projects. The librarian
uses the standard text editor to write standard text elements and the standard text library interface to
manage them. Additionally, the librarian may use the Teamcenter Search view and the Results
window as aids.

• Planner or engineer
Uses standard text as building blocks to compose work instructions. Planners cannot edit standard
text in the standard text library; however, they may copy and edit standard text and save it in a new
document associated with an operation or process in the process structure. Additionally, the planner
may use process structure, the textual work instructions editor, Teamcenter Search view, and the
Results window as aids.

Administrators must configure Teamcenter to enable the standard text feature.

Prerequisites to using the standard text feature

• The Teamcenter client must be installed on a Microsoft Windows platform (this limitation does not
apply to the Teamcenter server).

• Requires Microsoft Word. For certified versions, see the Hardware and Software Certifications
knowledge base article on Support Center.

• Requires a Teamcenter Manufacturing Documentation license.

You can use Access Manager to configure various permissions for different roles. Siemens Digital
Industries Software recommends using the scenario of administrator, librarian, and planner, as
described.

Set up standard text

1. Using Teamcenter Environment Manager, install the standard text templates. By default, the same
template is used by both the Standard Text and Textual Work Instructions views; however, you
can set up the system to use different templates for each view.

Note:
During installation, Teamcenter imports the following work instruction templates to
Teamcenter Environment Manager:

• Default_WIObjectTemplate.docx

6-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• STX_TC91OOTB_spec_template

• WI_TC91OOTB_spec_template

• TWI_TC101OOTB_spec_template

• TWIfor3DPDF_TC101OOTB_spec_template

Note:
• During installation, Teamcenter updates the MEWiStandardTextTemplate preference
that defines the template to be used by the Standard Text view and the
MEWiWorkInstructionTemplate preference that defines the template to be used by the
Textual Work Instructions view. These preferences enable you to use different templates
for the Standard Text and Textual Work Instructions views. Both preferences are
updated to the TWI_TC101OOTB_spec_template value.

• If the textual work instructions are created to be used as part of the 3DPDF Rich Textual
Work Instructions report, set the MEWiWorkInstructionTemplate preference to
TWIfor3DPDF_TC101OOTB_spec_template.

2. If Microsoft security bulletin MS09-073 is installed on your machine, you may encounter the
following error messages when loading work instructions. Microsoft has provided complete
information on this issue at:

http://support.microsoft.com/kb/973904/.

• Converter mswrd632

Open Regedit and do one of the following:

• For a 32-bit machine, delete the following registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\
Text Converters\Import\MSWord6.wpc

• For a 64-bit machine, delete the following registry entry:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Shared Tools\
Text Converters\Import\MSWord6.wpc

• Windows 6.0 files

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-3

Open Regedit and do one of the following:

• For a 32-bit machine, add the following registry entry:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
Applets\Wordpad

• For a 64-bit machine, add the following registry entry:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Microsoft\Windows\
CurrentVersion\Applets\Wordpad

• For both 32-bit and 64-bit machines, do the following:

a. Select the new entry in Regedit, choose Edit→New, and select DWORD Value.

b. Type AllowConversion for the name of the DWORD value, and press the Enter key.

c. Right-click AllowConversion and choose Modify.

d. In the Value data box, type 1 and click OK.

e. Close Regedit.

3. Customize List of Values Data Collection type.

a. In the Business Modeler IDE:

A. Create an LOV business object of any basic type: String, Integer, and so on (for example,
ProjectStatusLOV: Green/Yellow/Red).

B. Create a subclass of Mes0MELOVDCDForm (for example,

ProjectStatusDataCollection).

C. For ProjectStatusDataCollection:

i. Create a property of the same type as the LOV basic type (for example, Value).

ii. Connect the property to the ProjectStatusLOV LOV.

b. Deploy the changes to the database.

4. Customize the List of Values Planner Input Field type.

6-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

a. In the Business Modeler IDE:

A. Create an LOV business object of any basic type: String (for example, ProjectStatusLOV:
Green/Yellow/Red).

B. Create a subclass of Mes0MELOVPFBaseForm (for example,

ProjectStatusPlannerInputField).

C. For ProjectStatusPlannerInputField:

i. Connect the property mes0Value to the ProjectStatusLOV LOV.

ii. Connect the property mes0DefaultValue to the ProjectStatusLOV LOV.

b. Deploy the changes to the database.

Understanding the standard text template

By default, a single template is defined for both the standard text and work instructions editors. The
template contains the following:

• Symbols section
Symbols associated with the standard text or the work instructions are displayed in a dedicated
symbols section at the top of the document. When editing templates, leave this section at the top of
the document (first line) or remove it if symbols should not be displayed. Do not insert the symbols
section in the header or footer.

• Character styles
Use these to create the look-and-feel of the document. You can edit these styles, but you must retain
the same style names.

• WIDataCollectionStyle
Applied to the placeholder string of data collection definitions. The formatting is: Font: Calibri, Size:
11 points, Color: Gray-50%, Bold.

• WIPlannerFieldStyle
Applied to the value of planner input fields. The formatting is: Font: Calibri, Size: 11 points, Italic.

• WIInvalidPlannerFieldStyle
Applied to invalid planner input fields identified while running the Validate PIF command.
The formatting is: Font: Calibri, Size: 11 points, Italic, Color: Red.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-5

Note:
If you add new styles, ensure that Style type is Character. If you add new styles whose Style
type is Paragraph, errors may occur.

• Header and footer

By default, this is empty. You can add your company logo or any other pertinent information. You can
also add BOM line properties.

Using the standard text template

When using the standard text template to create standard text, the following Microsoft Word commands
are available on the General and Font Style tabs.

Edit standard text templates

Standard text templates are stored by default in the %Root%\install\cmtmes directory and are also
imported to Teamcenter as part of the installation. They are the responsibility of the system
administrator. The administrator can format the default standard text template and create more
templates by copying existing ones and editing them for different uses. Some editing functions can be
performed directly on standard text templates from Teamcenter. Other editing functions require that
you access the template from the %Root%\install\cmtmes directory and perform the following three-
stage procedure on the template:

• Remove the user interface customization that limits the available Microsoft Word commands.

• Edit the template.

• Restore user interface customization.

6-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Note:
When creating new templates, always use one of the document templates supplied with the
Teamcenter installation as your starting point. Either copy one of these templates, rename it, and
edit it; or open a template, edit it, and perform a Save As operation. You can clone a template in
one of the following ways:

• Use a template from the installation directory:

1. Select a template from the %Root%\install\cmtmes directory and copy it to an accessible

location.

2. Clear the read-only attribute of the file.

3. Modify the file name so that you can import it later; the import fails if there is already a
template with this name.

4. Perform the following modifications:

a. Remove the user interface customization that limits the available Microsoft Word
commands.

b. Edit the template.

c. Restore user interface customization.

5. In My Teamcenter, choose Tools→Import→Templates→Specification Template to

import the new template into Teamcenter.

• Clone a template within Teamcenter:

1. In My Teamcenter, locate the template by choosing Home→Standard Text

Templates→Standard Text Spec Template.

Note:
If using OOTB templates, you should only use the latest template file available –
TWI_TC1017OOTB_spec_template.

Warning:
Old templates for past versions of Teamcenter have known issues in newer versions.

2. In the Summary view, click Save As.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-7

3. Modify the file name so that you can import it later, the import fails if there is already a
template with this name.

4. Click Finish.

The specification template is created under the Newstuff folder. You can move it to a
dedicated folder.

Note:
User interface customization ensures document standardization throughout your organization.

After importing the template, define which templates are to be used by the Standard Text and Textual
Work Instructions views:

1. Edit the MEWiStandardTextTemplate preference so that it contains the name of the new standard
text template (without the .docx suffix). This template becomes the default template for creating
standard text.

2. Edit the MEWiWorkInstructionTemplate preference so that it contains the name of the new work
instructions template (without the .docx suffix). This template becomes the default template for
creating work instructions.

Remove customization
1. Change the template file name to include the .7z extension. For example, rename
TWI_TC10OOTB_spec_template.docx to TWI_TC10OOTB_spec_template.docx.7z.

The system recognizes the template file as an archive file.

2. Open the archive file in 7-Zip, extract customUI.xml, customUI14.xml, and .rels, and store these
files for later use.

3. Delete customUI.xml and customUI14.xml from the archive and close 7-Zip.

Note:
User interface customization ensures document standardization throughout your
organization. Siemens Digital Industries Software recommends retaining the default
customization. However, you can edit the customUI.xml file to change the customization, or
delete the customUI.xml file to remove customization.

4. Remove the .7z suffix from the template file name.

6-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Deleting customUI.xml removes all customization from the template file. You can now edit it as
you would any other Microsoft Word file.

Restore customization
1. Save the modifications and close the document.

2. Change the template file name to include the .zip suffix. For example, rename
WI_TC9OOTB_spec_template.docx as WI_TC9OOTB_spec_template.docx.zip.

The system recognizes the template file as an archive file.

3. Locate the customUI.xml, customUI14.xml, and .rels files that you saved when you removed the
customization, right-click, and choose Add to archive....

4. Type the template ZIP file name in the Archive name box and click OK.

Note:
Siemens Digital Industries Software recommends restoring the customUI.xml and
customUI14.xml files. This restores the default customization. However, you can edit the
customUI.xml and customUI14.xml files to change the customization or not restore the
customUI.xml and customUI14.xml files to remove customization.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-9

5. Remove the .zip suffix from the template file name.

Editing options
This topic details all the template editing functions. For each one, it notes whether the procedure can be
performed directly from Teamcenter or whether you must access the template from the %Root%\install
\cmtmes directory. To modify the template directly in Teamcenter, access My Teamcenter, expand under
the specification template up to the FullText element, and double-click the FullText item.

Add BOM line properties

Administrators can add operation or process BOM line properties to the template header or footer. This
can be useful, for example, to facilitate quick identification of different documents. This can be done
directly from Teamcenter.

1. Launch Microsoft Word.

Note:
This instance of Word is independent of Teamcenter.

2. Open a blank Word document, and click the Developer tab.

6-10 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

If the Developer tab is not available, in Microsoft Word, do the following:

a. Choose File→Options→Customize Ribbon.

b. From the Customize Ribbon list on the right, select Main Tabs, and select Developer.

c. Click OK to accept the change and exit the Word Options dialog box.

3. Double-click the top of the document.

The document header becomes active.

4. Click the Developer tab.

5. Click the Plain Text Content control button.

Word places an empty plain text content control in the header.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-11

If the property you want to add requires more than a single paragraph, use a Rich Text Content
control. For example, the description property may require multiple paragraphs.

6. Select the new text control and click Properties.

The Content Control Properties dialog box appears.

7. In the Title box, type a name for the property title.

The Title text is used for the content control’s name.

6-12 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

8. In the Tag box, type the name of the BOM line property you want to insert in the template header.
To retrieve the property name, proceed as follows:

a. Right-click the column area in Manufacturing Process Planner and choose Insert Column. The
Change Columns dialog box appears.

b. Copy the desired BOM line property name to the clipboard.

c. In the Change Columns dialog box, click Cancel.

9. In the Tag box, paste the BOM line property name.

10. In the Tag box, preface the BOM line property name with one of the following:

• LNP_ for a line property, for example, LNP_bl_rev_object_name for a line object name or
LNP_bl_rev_item_revision_id for a line revision identification number

• LPP_ for a line parent property, for example, LPP_bl_rev_object_name for a parent object name

11. In the Content Control Properties dialog box, click OK.

Note:
Ignore the Locking and Plain Text Properties sections.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-13

12. Open the target template and double-click the top to activate the header area.

13. Type the name of the property you want to insert in the template header.

14. From the Word document, copy the content control you created and paste it after the property
name you typed.

15. Add as many BOM line properties as you want to the template header.

Note:
You can add a table to the document header and insert the BOM line properties into the
table. This enables you to add multiple properties in an orderly way.

16. Save and close the template.

17. Discard the original Word document in which you created the content control.

Add or modify template styles

This procedure can be performed directly from Teamcenter.

1. Add or modify styles as needed.

2. Close and save the template file.

Remove symbols section

This procedure requires you to access the template from the %Root%\install\cmtmes directory.

Symbols associated with the standard text or the work instructions are displayed in a dedicated symbols
section at the top of the document. When editing templates, leave this section at the top of the
document (first line) or remove it if symbols should not be displayed. Do not insert the symbols section
in the header or footer.

By default, the symbol section exists in the template and is protected. To prevent symbols from
appearing, delete the symbol section as follows:

1. In Word, choose Options→Popular and select Show Developer tab in the Ribbon.

6-14 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

2. Click the Developer tab.

3. The symbol section is not visible, therefore, to place your cursor inside the symbol section, click
anywhere in the body of the document and then press the Home key and the right arrow (→) key.

The symbol section becomes active.

4. From the Controls section, click Properties.

The Content Control Properties dialog box appears.

5. Clear the Content control cannot be deleted and Contents cannot be edited check boxes.

6. Click OK.

7. Select the symbol section and press the Delete key.

Siemens Digital Industries Software recommends deleting any empty lines in your template file.

Add symbol section

To add a symbol section if you deleted it:

1. From the Developer tab, choose Controls→RichText .

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-15

Word adds a new control.

Note:
Word automatically places the new control at the top of the document, below the header.

2. Type a single space in the new control.

3. Right-click the control and choose Properties.

The Content Control Properties dialog box appears.

4. Edit the Title box, adding, for example, Symbols Section.

5. In the Tag box, type SymbolsSection.

Note:
You must type SymbolsSection exactly or the symbol section does not work.

6. Select the Content control cannot be deleted and Contents cannot be edited check boxes.

7. Click OK.

Word creates the symbol section.

Specifying the location of the Add Symbol button

When preparing to use the textual work instructions feature, you must determine in advance whether to
enable adding symbols in standard text elements (in the Standard Text view by the librarian) or instead
to textual work instructions (in the Textual Work Instructions view by the planner). This decision is
applicable to all users of the feature. You cannot add symbols in both locations.

• Add a symbol to the standard text element in the Standard Text view. You subsequently add the
standard text element to the work instruction.

6-16 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• Add a symbol directly to the work instruction in the Textual Work Instructions view.

The position of this button is defined in the MEWiEnableAddSymbolCommand preference. The valid
values for this preference are STXView or TWIView.

Importing standard text library structures from a legacy system

If you have a standard text library structure in a system other than Teamcenter, you can re-create this
structure in Teamcenter using the tcexcel_import utility. You define the full library structure containing
folders and standard text elements in a Microsoft Excel spreadsheet and save it to a tab-delineated file.
This file is then used as input for the tcexcel_import utility that creates the structure and attaches
documents to the standard text elements. In the spreadsheet, you specify the paths to the documents
that are to be attached to the standard text elements. The textual content for each of the standard text
elements can come from:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-17

• TXT files containing only rich text.

• DOCX files containing tables, images, formatting, header and footer content.

After import, a standard text librarian can modify the library structure and an author can modify the
documents and save the modifications.

The following is an example of an input file with a simple library structure. The first four columns
represent the structure of the standard text library. The last column, the StxFilePath column, contains
the path to the document that will be attached to the standard text element.

Header1 Item Item Item StxFilePath

Header2 Mes0MESTXLibrar Mes0MESTXFolder Mes0MESTXElement
y
Header3 Mes0MESTXLibrar Mes0MESTXFolder Mes0MESTXElement
y
Title Root Sub1 Sub2 Sub3
Library
Safety instructions
STX1 D:\temp\goggles.docx
STX2 D:\temp\boots.docx
STX3 D:\temp\helmet.docx
Folder2
STX4 D:\temp\magnet.docx
STX5 D:\temp\table_example.docx
STX6 D:\temp\rich_text_example.docx
STX7 D:\temp\helmet.docx
STX8 D:\temp\helmet.docx

Note:
This example imports only DOCX files, but both DOCX and TXT files are supported.

You can import this structure into Teamcenter by saving the Microsoft Excel spreadsheet as a text file
and import that file into Teamcenter using the following tcexcel_import utility call:

tcexcel_import -u=username -p=password -g=dba -i=path-to-txt-file

The resulting structure appears as follows in Teamcenter.

6-18 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Note that the standard text elements have documents attached. You can modify these documents, save
them, and continue to work with them in the customary fashion.

Note:
You can only use the tcexcel_import utility to create new library structures. You cannot use it to
update structures.

Updating standard text instances using the update_stx_elements

utility
When an individual standard text library object changes, you can use the command line
update_stx_elements utility to find and update textual work instruction preview datasets attached to
process or operation revisions. Any of these preview datasets impacted by changes to a single, selected
standard text object are updated when you run the utility.

Requirements

After a standard text library object has been revised, updated and approved, it is a valid candidate for
the textual work instructions (TWI) bulk update utility.

• The update_stx_elements utility requires a Microsoft Office version compatible with the Teamcenter
version you have installed.

• You must run the utility from a Teamcenter server.

• To provide controlled and predictable results, it is strongly recommended that you update only a
single standard library object prior to executing the bulk update. Because an individual TWI document
may contain references to multiple standard library elements, all standard library elements referenced
within a TWI document are regenerated within an updated TWI document.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 6-19

• You should run the utility at a time when users are not authoring TWI documents, and you should
prenotify users of expected changes. The TWI documents may be in a working or released state.

Caveats

The following are not part of the update_stx_elements utility process and must be addressed
separately:

• Manufacturing Execution System (MES) integration.

• Change management.
Teamcenter recommends that you set a single manufacturing change notice (MCN) on a single
standard text library object. An in-depth understanding of the nature of changes made by the
update_stx_elements utility is essential to successful results. The TWI preview dataset used by TWI
and Electronic Work Instructions (EWI) supports one of several formats: PDF (default), MHT, docx, and
rtf, based on the Teamcenter preference MEWiPreviewFormat. Changes made to the TWI preview
dataset attached to an Process/OP item revision are absolute and datasets have no revision history.

• The utility does not support standard symbol library objects.

• If a standard text library object change requires additional changes to the BOP, such as changes to the
number of operations or changes to consumed parts, this is not a valid use of the bulk update utility.

6-20 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
7. Administering structure cloning
Creating structures from templates overview
You can create a product structure from a product template, a plant structure from a plant template, and
process structure from a process template. You may choose to define a generic product structure that
does not represent an actual manufactured product because it contains generic placeholders in place of
variable parts. These placeholders are identified by absolute occurrences that are populated when an
actual product structure is created from the template.

If you create a generic manufacturing process structure from the generic product structure, the
occurrences in the generic product structure are consumed in the generic process structure.

In a template process, although no real parts are consumed in the operations that comprise the generic
process, each consumed item has an identity. This identity of the item in the process structure is the
same as it is in the product structure. Consequently, if you use this process structure as a template for
the creation of a new process structure for manufacturing a product that maps exactly to the generic
product structure, the product and process share the same absolute occurrences. The new process that
you create from the template consumes the parts from the real product structure with the same
absolute occurrences.

Similarly, if you define a mapping between the plant structure referenced by the template and the actual
plant structure, generic work areas are substituted with specific absolute occurrences.

Reusing process templates

In many manufacturing environments, process planners design standard processes that are reused
several times for different products. For example, the basic structure of the manufacturing process for a
car is similar for a basic model or a premium model.

You can use any process as a template for a new structure. However, if you have many of these
processes, it can be more efficient to save such manufacturing processes as templates in a library, and
then use the templates as the basis of new manufacturing processes for similar products. The template
may include configuration rules that map the product data to process operations, and may include
references to standard resources. You can classify the templates in the Classification application for easy
retrieval later.

When you create a new process operation, you can browse the available templates and select one to
create the process operation. After it is created, you can attach the geometry of the part to be
processed.

Similarly, you can create assembly setup templates containing assembly information for a typical
assembly setup. When you initialize a setup from a template, Teamcenter loads the related method,
equipment, features, and manufacturing operations.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 7-1

Note:
By default, classify immediately is disabled for a root item in Manufacturing Process Planner.

Carrying over future incremental change when cloning

When cloning, you have the option to carry over future effective incremental changes. If you are using
date effectivity, future is anything falling after the date set in cloning dialog box. If you are using unit
effectivity, future is anything after the unit number set in the cloning dialog box. Incremental changes
that are currently effective are merged with the currently set incremental change. Those that are
effective in the future are carried forward to the new cloned structure or re-created under new
incremental change revisions. Any incremental changes whose effectivities are in the past are dropped
from the cloned incremental change.

Note:
• Specify the release status type that is assigned to any newly created incremental change
revisions during cloning in the Clone_Pending_Release_Status preference.

• Specify the release status type that should be considered as secure in the
Clone_Secured_Release_Status preference.

In the following figure, the vertical line represents the point of cloning.

Cloning with incremental changes

7-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

1 IC1 Incremental change 1 whose effectivity lies in the past.

2 IC2 Incremental change 2 that is secure and configured.

3 IC3 Incremental change 3 is the current IC (set at the bottom of the pane) that is
configured and pending. This is the target IC.

4 IC4 Incremental change 4 is pending and unconfigured.

After cloning, Teamcenter:

• Disregards IC1.

• Clones IC2 to a new IC5 and the change elements in IC2 (that is, add or remove) that are associated
with the cloned object are cloned and added to IC5. IC5 then has a pending status.

• IC4 is left alone and the new change elements are added to it. This is not cloned because the status is
pending and the out effectivity does not match the currently set IC revision (IC3).

Configuring how assemblies in context are cloned and replaced

The Clone Assembly in Context and Replace Assembly with Any Item Type commands are available
in Teamcenter MBOM Product or Workarea views when you choose Edit→In Context. How you
configure these commands affects how structures are cloned in context within the same MBOM and
how items and item types are replaced within in-context assemblies.

Clone Assembly in Context

By default, the Clone Assembly in Context command clones an MBOM subassembly and pastes the
clone within the same MBOM. This command:

• Retains all in-context edits in the cloned subassembly.

• Lets the MBOM author copy, reference, or exclude in-context attachments from the structure being
cloned, and optionally, split occurrence effectivity dates or ranges between the assembly being
cloned and the cloned assembly.

Direct and in-context attachments of the new (cloned) line, cloning of children below the new line, and
attachments on referenced children below the line added in the context of lines above the new line, are
controlled by cloning rules. Cloning rule names are listed in the preference
MECopyAssemblyInContextTemplates.

Paste Assembly in Context

This command pastes a copied assembly with in-context edits elsewhere in the same MBOM, creating a
new absolute occurrence of the assembly while retaining in-context edits and attachments.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 7-3

Copied and referenced children are again controlled by cloning rules. Cloning rule names are listed in
the preference MEDuplicateAssemblyInContextTemplates.

Replace Assembly with Any Item Type

The Replace Assembly with Any Item Type command replaces an MBOM subassembly item with a new
item of a different item type while retaining the original subassembly's in-context edits. The procedure
is similar to the File→New item command, but retains in-context edits and also copies, references, or
excludes attachments from its original structure.

The Replace Assembly with Any Item Type command always preserves in-context attachments of the
new line. Direct attachments of the replaced line, cloning of children below the replaced line, and
attachments on children below the replaced line—in the context of lines above the replaced line—are
controlled by cloning rules. Cloning rule names are listed in the
MEReplaceAssemblyInContextTemplates preference. Properties on the new line can be mapped from
properties on the replaced line using the MEReplaceAssemblyInContextAlignProperties preference.

Defining cloning rules

To clone structures from templates or other structures, you must define cloning rules that allow
Manufacturing Process Management to determine how to map objects between the structures. These
cloning rules are defined by preferences and the defined rules are available to users when creating an
actual structure. The location of the cloning rule preferences for a specific user is determined by a
preference.

You can define three cloning rule preferences, one each for process templates, product templates, and
plant templates. You can associate multiple action rules with each preference.

When Manufacturing Process Management encounters an object that is mapped between the template
and the actual structure, it determines if a substitution is necessary and takes one of four actions,
according to the mapping of the object type:

• Clone
Copies the object referenced by the template to a new object in the structure.

• Reference
The structure references the same object as the template.

• Ignore
The new structure does not reference the object.

• Map
The system maps the template to a replacement structure. For example, this allows you to create a
process structure from an existing process or from a process template. Optionally, this rule may be
allowed by a second (default) action: Reference or Ignore.

You can also define a cloning rule to ignore the cloning of an MBOM recipe.

7-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Example:
*:*:Relation.Mfg0MEAssignmentRecipeRel:Ignore

Note:
You cannot apply a Reference action to an MBOM recipe. A Reference action will log an error and
ignore the cloning.

Manufacturing Process Management only takes the specified action if an absolute occurrence or its ID is
the same in the template and the structure. If the same absolute occurrence appears more than once,
only the first matched instance is mapped.

You can specify a second action after the Map action. The second action is the default action and is
taken if the mapping fails. For example:

*:*:OccType.MEConsumed:Map.Ignore
*:*:OccType.MEWorkArea:Map.Reference

In this example, the MEConsumed occurrence type is mapped to the occurrence in the new structure.
Manufacturing Process Management uses the absolute occurrence referenced from the template and
finds the corresponding occurrence in the new product. It links the consumed items for that operation
to the occurrence in the new product. When there is no mapping for the Consumed item,
Manufacturing Process Management ignores it. When there is no mapping for the WorkArea item,
Manufacturing Process Management creates a reference to the item from the cloned element.

Note:
By default, the MEConsumed occurrence type maps consumed items to the corresponding
occurrences. The site administrator can change the controllingOccsForProcessConfiguration
preference to map another occurrence type. Alternatively, this preference may be left unassigned,
in which case the configuration of consumed items does not affect the configuration of
operations.

Each site can define a set of cloning rules from which users may select. In addition, individual users may
change the cloning action rules by editing their preference file.

Note:
These rules determine if objects are cloned, referenced or ignored. You cannot change this
behavior with the Business Modeler IDE application.

The general format of the cloning rule preferences is as follows:

Process.Template=
Action_Rule_Name1

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 7-5

Action_Rule_Name2
.
.
Product.Template=
Action_Rule_Name3
Action_Rule_Name4
.
.
Plant.Template=
Action_Rule_Name5
Action_Rule_Name6

For each set of action rules, you must define a new variable. The following example shows a typical
Action_Rule_Name1 variable for the Process.Template variable:

Process.Template.Action_Rule_Name1=
*:*:Attribute.items_tag:Clone
*:*:Attribute.structure_revisions:Clone
*:*:Attribute.bom_view:Clone
*:*:Attribute.parent_item:Clone

The following example shows two cloning rules (Mapping_Consumes and Ignore_Consumes) for
process templates:

Process.Template=
Mapping_Consumes
Ignoring_Consumes
Process.Template.Mapping_Consumes=
*:*:Attribute.items_tag:Clone
*:*:Attribute.structure_revisions:Clone
*:*:Attribute.bom_view:Clone
*:*:Attribute.parent_item:Clone
*:*:Attribute.variant_expression_block:Clone
*:*:OccType.Null:Clone
*:*:OccType.MEConsumed:Map.Ignore
*:*:OccType.MEWorkpiece:Ignore
*:*:OccType.*:Reference
*:*:Relation.TC_Rendering:Clone
*:*:Relation.TC_specification:Clone
*:class.MEActivity:Relation.TC_MEFolder:Clone
class.MEActivity:*:Attribute.contents:Clone
class.Folder:*:Attribute.contents:Reference
Process.Template.Ignoring_Consumes=
*:*:Attribute.items_tag:Clone
*:*:Attribute.structure_revisions:Clone
*:*:Attribute.bom_view:Clone
*:*:Attribute.parent_item:Clone
*:*:Attribute.variant_expression_block:Clone

7-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

*:*:OccType.Null:Clone
*:*:OccType.MEConsumed:Ignore
*:*:OccType.MEWorkpiece:Ignore
*:*:OccType.*:Reference
*:*:Relation.TC_Rendering:Clone
*:*:Relation.TC_specification:Clone
*:class.MEActivity:Relation.TC_MEFolder:Clone
class.MEActivity:*:Attribute.contents:Clone
class.Folder:*:Attribute.contents:Reference

The syntax for adding an entry to a cloning rule is as follows:

parent-object:object:relation:action

For example:

*:type.MEPSDRevision:Occtype.*:Reference

In this example, the system searches through any parent (*), and when it finds a child of type
MEPSDRevision (type.MEPSDRevision), with any occurrence relation (Occtype.*), it creates a new
reference to that MEPSD element (Reference).

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 7-7

7-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
8. Administering manufacturing publish
Configuring the publish feature
Manufacturing Process Management allows you to create publishing pages that can be viewed or
printed by nontechnical users with limited computer skills, such as assembly personnel. Publishing
pages is a general term for any document used by manufacturing personnel, including work
instructions, maintenance instructions, assembly instructions or any other documentation needed for
your processes.

To create or view manufacturing documentation, install Microsoft Visio on each workstation where you
author publishing pages. Both Visio Standard and Visio Professional are supported. You can install Visio
before or after the Teamcenter installation. For certified versions, see the Hardware and Software
Certifications knowledge base article on Support Center.

Publishing pages can be published to PDF or HTML so that they can be viewed independently of
Teamcenter or Visio.

You create a template for each of the publishing page types needed in your organization from assets
(Visio shapes) that are bound to Teamcenter data. The process planners use these templates to create
publishing pages that may include text, tables, graphics, 2D or 3D snapshot (product views), and link
assets. When all the publishing pages are complete, the process planner can collect them into a
technical portfolio that may contain all the activity, operation, and process documentation for a
particular assembly line. Users manipulate publishing pages and portfolios in the Manufacturing Process
Planner, Part Planner, Resource Manager, Plant Designer, and Multi-Structure Manager applications. They
may also add 3D annotations where appropriate. For detailed procedures, see the procedures for
viewing, creating, and editing manufacturing documentation in the guides for those applications.

In addition to creating manufacturing documentation in Microsoft Visio, you can create links that point
to manufacturing documentation in Microsoft Word and text files.

You can optionally publish manufacturing documentation in PDF format. If you publish a PDF of a
portfolio, Teamcenter attaches the PDF dataset to the portfolio. If you create a PDF of a publishing page,
Teamcenter attaches the PDF dataset to the page dataset. You must install PDF generation software to
use this feature, for example, one of the Adobe products or the freeware GhostScript utility.

Understanding roles
Publishing pages have content that reflects a specific purpose or role. By default, Teamcenter supports
two roles, Work Instructions and Product Manual. You can customize Teamcenter to support any
desired roles, for example, Repair Manual. The same dataset types are used for all roles. When
publishing pages are attached to BOM lines or item revisions, the role is determined by the type of
relation that attaches the dataset to the parent item revision. Multiple datasets can be attached to an
item revision and the datasets can fulfill different roles according to the relation type. When a publishing
page is attached to an activity, its role is determined by a preference setting. All publishing pages
attached to an activity fulfill the same role. When a portfolio is generated from a structure, the pages

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-1

that are added to it are determined by the role that the user specifies for that portfolio. Internally, each
role is typically associated with:

• A relation type used to attach a publishing page dataset to a revision.

• A transfer mode for generating a portfolio for this role.

• One or more alias files for populating assets.

A set of preferences associates the role with the relation type, the transfer mode, and the default alias
files, as well as the following:

• The list of roles in the portfolio generation dialog box

• A set of useful alias files

• The user’s favorite list of templates

You can create a custom roles to reflect your company’s needs. There are two steps necessary to do this:

• Add a new relation object for the new role using the Business Modeler IDE.

• Add a new rich client plug-in that extends the

com.teamcenter.rac.cme.tcpublishwrapper.publishingPageViewRoles extension point.

Example: creating a customized publish role

The following is an example plugin.xml file for adding a new Teamcenter publish role named
Fnd0MyPersonalRole. The Teamcenter publish wrapper extension point requires both a role and a
view. The plug-in must define both. The view must be added to a Teamcenter menu. This example
shows adding the view as an entry to the Open With menu command where the current Work
Instruction menu command exists.

<?xml version="1.0" encoding="UTF-8"?>

<?eclipse version="3.4"?>
<plugin>
<extension
point="com.teamcenter.rac.vns.viewDef">
<view alwaysUseSetRootInputObject="true"
id="com.myCompany.viewId"
selectionInPrimaryEffectsInvisbleSecondary="false"
selectionInSecondaryEffectsPrimary="false">
<viewType type="secondary"></viewType>
</view>
</extension>
<extension
point="org.eclipse.ui.views">
<view allowMultiple="true"
category="com.teamcenter.rac.aifrcp.manufacturingCategory"
class="com.teamcenter.rac.cme.tcpublishwrapper.PublishingPageView"

8-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

icon="icons/workinstructions_view_16.png"
id="com.myCompany.viewId"
name="%viewId.VIEW">
</view>
</extension>
<extension
point="com.teamcenter.rac.cme.tcpublishwrapper.publishingPageViewRoles">
<viewRoleType
tcPublishRole="Fnd0MyPersonalRole"
viewId="com.myCompany.viewId">
</viewRoleType>
</extension>
<extension
point="com.teamcenter.rac.aifrcp.openWithViewMenuDef">
<menuItem groupId="secondary"
icon="icons/workinstructions_view_16.png"
label="%viewId.VIEW"
viewId="com.myCompany.viewId">
<visibleWhen>
<and>
<count value="1"/>
<iterate ifEmpty="false" operator="and">
<with variable="rac_command_suppression">
<not>
<iterate operator="or">
<equals value="com.teamcenter.rac.openWith"/>
</iterate>
</not>
</with>
<adapt type="com.teamcenter.rac.kernel.TCComponent">
<test
property="com.teamcenter.rac.kernel.TCComponent.typeClass"
value="ImanItemBOPLine,BOMLine,CfgAttachmentLine,MEActivity"/
>
</adapt>
</iterate>
</and>
</visibleWhen>
</menuItem>
</extension>
</plugin>

Set preferences and environment variables

• IMAN_MEWorkInstruction_relation_primary
Lists the object classes that can be pasted into a work instruction using this relation.

• AppInterface_TCPublishingTechnicalPortfolio_default_relation
Defines the default relation used when a TCPublishingTechnicalPortfolio dataset is pasted under an
intermediate data capture (IDC) while creating technical portfolios.

• AppInterface_TCPublishingTechnicalPortfolio_shown_relations
Defines the relations available when pasting a TCPublishingTechnicalPortfolio dataset under an
intermediate data capture (IDC) while creating technical portfolios.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-3

• IMAN_PublishingPageAssetContext_relation_primary
Defines which Teamcenter objects can be used with a IMAN_PublishingPageAssetContext relation.

• IMAN_TCPublishedPortfolio_relation_primary
Defines which Teamcenter objects are used as primary objects with a IMAN_TCPublishedPortfolio
relation.

• ItemRevision_TCPublishingPage_default_relation
Defines the default relation created when a publishing page is pasted within an item revision.

• <TC Publishing Technical Portfolio type>_DefaultChildProperties

Determines which properties are children of the indicated technical portfolio type. Each type requires
its own preference.

• <TC Publishing Page type>_DefaultChildProperties

Determines which properties are children of the indicated publishing page type. Each type requires its
own preference.

• IMAN_PortfolioConfiguredPage_relation_primary
Defines which Teamcenter objects are used as primary objects with a
IMAN_PortfolioConfiguredPage relation.

• IMAN_PortfolioPage_relation_primary
Defines which Teamcenter objects are used as primary objects with a IMAN_PortfolioPage relation.

• TechnicalPortfolioRoles
Use this preference to define the roles of technical portfolios.

• TechnicalPortfolioTransferMode_IMAN_MEWorkInstruction
Defines the transfer mode of the specified technical portfolio. TransferMode objects control the
related data exported into a PLM XML document.

• TCPublishing_Default_Alias_File
The name of the installed alias file, as described later. Defines the default alias file loaded when a new
publishing page is viewed.

• TCPublishing_Aliases.IMAN_MEWorkInstruction
The names of the available alias files for work instruction pages. If this preference is not set, the user
can choose from any alias file in the database.

• TCPublishing_Activities_Role
Defines the role of all publishing page datasets that are attached to activities in Manufacturing
Process Planner, for example, IMAN_MEWorkInstructions (the default setting). The role determines
the tab name shown in Manufacturing Process Planner and also how portfolios are generated. If you
change the relation name defined in this preference, you must define a new closure rule and transfer
mode to generate portfolios. You must also add the new role to the TechnicalPortfolioRoles
preference.

8-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• TCPublishing_Aliases.Activities
Contains the names of the alias file datasets that appear when the user wants to load alias files for
activity pages.

You should also ensure that the Dataset_DefaultChildProperties preference for each user contains the
following settings:

TC_PublishingPageAssetContext
TC_PortfolioPage
TC_PortfolioConfiguredPage

These settings allow users to cut and paste publishing pages and portfolios.

The following environment variables are set during installation and you should not normally change
their values.

• PUBLISH_PDF_TIMEOUT
This environment variable sets a time-out period for stalled PDF conversions. Enter a number of
milliseconds after which the conversion is terminated, enter 120000 for 2 minutes. If you require an
infinite time-out, set this environment variable to INFINITE.

• PUBLISH_PDF_MAX_JOBS
Defines the maximum number of outstanding PDF conversion jobs that are allowed to run
simultaneously. This environment variable is effective only when you publish a portfolio to PDF and
select multiple PDFs.

• PUBLISH_PDF_INTERVAL
This environment variable defines the number of milliseconds Teamcenter waits before issuing each
subsequent PDF conversion job. Set a value that ensures there are no conflicts between PDF jobs
starting simultaneously. Typically, you do not need to change the default value of 1000 (one second).
This environment variable is effective only when you publish a portfolio to PDF and select multiple
PDFs.

Installing the transfer mode

When you install Teamcenter, the necessary default PLM XML transfer modes are provided. The transfer
mode for publishing is defaultTransferModes.xml, which is located in the TC_DATA data directory of
the base installation (TC_BASE).

If necessary, you can reinstall this transfer mode by running the following command from a Teamcenter
shell:

%TC_BIN%\plmxml_import -u=infodba -p=infodba -g=dba -xml_file=

%TC_BIN%\defaultTransfermodes.xml

Ensure you enter the complete path for the xml_file argument, for example:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-5

file=C:\Tc2007\tcdata\mfg\defaultTransfermodes.xml

You would only reinstall the file if you make system-specific changes, for example, you customize the
mode for your site environment.

Defining alias files

To view Teamcenter-managed data in a publishing page, you have to create an asset, bind it, and
populate it. When you bind the asset, the Bind dialog box contains a list of transfer modes and a
number of choices, called aliases, from which you can select. The choice you make for each asset
defines how Publish finds the data that is displayed in the asset when you populate it.

When you select an object in Teamcenter, and then populate an asset, a number of things happen.

1. If the selected object is a BOM line, Publish creates a structure context object in the database to
persist the selection.

2. Publish creates a PLM XML file that contains information about the selected persistent object and
about related objects. This additional content about the related objects is determined by the
definition of the transfer mode that was assigned to the asset in the Bind dialog box.

3. Publish searches through the PLM XML file’s content to find the exact data to expose in the asset.
To do this, it retrieves the alias definition for the alias that was bound to the asset. The definition
contains a list of paths. Publish attempts to follow each path from the root object in the PLM XML
file until it finds some valid data. This data can consist of anything from a string, such as a form
attribute value, to a file containing an image.

4. Teamcenter creates a snapshot of the data in the asset on the Visio pane.

5. Teamcenter stores the ID of the selected persistent object in the Visio file, associating it with the
asset, for later retrieval during an update operation.

The transfer modes and aliases that are available in the Bind dialog box are all defined in the alias file.
Each transfer mode functions as a recipe for what is included in the PLM XML file. The definition of each
alias functions as a recipe that tells Teamcenter which parts of the exported PLM XML information to
expose in an asset.

The snapshot of Teamcenter’s data is visible whenever you open the page file for viewing. You can also
update an asset so that it displays changes that were made in Teamcenter since the asset was first
populated. When the asset is updated, new PLM XML is generated from the same selected object using
the same transfer mode, and the same alias is then used to find the exact data from that PLM XML to be
displayed in the asset.

A sample set of alias definitions is provided with the default installation, but you should create alias
definitions and transfer modes to support other situations. To do this, you should:

8-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• Ensure that the information appears in the PLM XML file. If it does not, create or modify a transfer
mode so that the information is visible.

• Ensure that an alias definition correctly extracts this information from the PLM XML file. If not, modify
existing aliases or create new aliases. The default alias definition file contains instructions and
examples of aliases.

Teamcenter includes a default alias file (TcPublishSystemAlias.xml) that you can use as the basis for
your own mapping files and its location is defined in the TCPublishing_Default_Alias_File preference.
The comments within this file contain detailed notes on the structure and usage of the alias file. Read
these before beginning with customization.

Caution:
Do not edit this file directly. Create your own alias dataset and work in this file.

Building a sample alias file

The following figure shows a publishing page with a single table asset that has been populated with the
Name property of child items and the Description property of an attached form from each child item.

Example result – table asset populated with child item names and form descriptions

This example starts with a simple product structure containing a parent item with two direct child items.
Each child item has an attached form. This scenario is shown in the following figure.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-7

Sample product structure

To populate the table asset with data, you must assign a binding to the table asset. The binding used is
ProductPartList & Name and ProductPartList & FormDescription, as shown in the following figure.

Publish Bind dialog box

You can find the sample alias file that was used to create this example
(ProjectTcPublishSystemAlias.xml), as well as the PLM XML code generated by the selected transfer

8-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

mode (tcm_export.xml) in the Sample directory of your installation. This must be installed separately.
If you do not have a Sample directory, contact your Teamcenter administrator.

In the example, the second binding involves the Description property of a form attached to the child
item. The default alias file does not provide a definition for attaching the Description field of a form to a
child item so you must modify this alias file.

In the following figure, notice the new FormDescription alias entry.

Expanded ProductPartList alias showing FormDescription entry

This new entry is created by adding a new top level alias definition into the alias file. The following code
shows excerpts from the DefaultTcPublishSystemAlias.xml file. The line shown in bold print results in
the new entry in the Bind dialog box shown in the figure. The statements in italics refer to other alias
definitions.

<Alias name="ProductPartList" assetType="8" toolTip="product data"
qualifier="2" accumulate="Quantity">
&OCC-ATTR-DEF;
</Alias>

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-9

<!-- properties that you want to see on an occurrence.

Entity definition is used to avoid lot of typing-->
<!ENTITY OCC-ATTR-DEF "
<Alias name='ID' default='No ID'/>
<Alias name='Description' default='No description'/>
<Alias name='Name' default='no name'/>
<Alias name='Rev' default='A'/>
<Alias name='Transform' default='Identity'/>
<Alias name='RevSubType' default='ItemRevision'/>
<Alias name='LogicalID' default='Logical Identity'/>
<Alias name='SequenceNumber' default='No find#'/>
<Alias name='Quantity' default='1'/>
<Alias name='ParentName' default='No parent'/>
<Alias name='Type' default='No type'/>
&FORM-MASTER-ATTR-DEF;
&ICO-ATTR-DEF;
">
<!ENTITY FORM-MASTER-ATTR-DEF "
<Alias name='project_id' default='cannot get project_id'/>
<Alias name='previous_item_id' default='cannot get previous itemid'/>
<Alias name='item_comment' default='cannot get comment'/>
<Alias name='serial_number' default='cannot get serial_number'/>
<Alias name='UserData1' default='cannot get user_data_1'/>
<Alias name='UserData2' default='cannot get user_data_2'/>
<Alias name='UserData3' default='cannot get user_data_3'/>
<Alias name='rev_project_id' default='cannot get project_id'/>
<Alias name='rev_previous_item_id' default='cannot get previous itemid'/>
<Alias name='rev_item_comment' default='cannot get comment'/>
<Alias name='rev_serial_number' default='cannot get serial_number'/>
<Alias name='rev_UserData1' default='cannot get user_data_1'/>
<Alias name='rev_UserData2' default='cannot get user_data_2'/>
<Alias name='rev_UserData3' default='cannot get user_data_3'/>
<Alias name='FormDescription' default='No description'/>
">

For the new alias definition to traverse the PLM XML file, another edit is necessary. The following entry
shows the traversal performed by the new alias definition. This entry is added to the <!ENTITY FORM-
MASTER-ATTR "> section of the alias file.

<Alias name='FormDescription'>
<Path>*:AssociatedAttachment[@role='IMAN_specification']:@associatedAttachmentRefs</
Path>
<Path>*:Form:@attachmentRef</Path>
<Xpath>Description</Xpath>
</Alias>

To determine what to add and how the traversal works, reference the PLM XML file generated by the
example and found in the Samples directory.

In the binding, ProductPartsList & FormDescription was selected. Find the Alias and AliasAlternate
sections for ProductPartsList in the alias file. The following code section shows the relevant lines from
the generated PLM XML file. All PLM XML files have a traverseRootRef entry like this:

<Header id="id1" traverseRootRefs="#id3" transferContext="tcm_export"></Header>

8-10 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

#id3 is the start node for the traversal. The transferContext transfer mode is used to generate this PLM
XML code.

The start node is AssociatedAttachment.

Look through the alias file in the ProductPartsList section for all alias definitions that have a primary
object specifying an AssociatedAttachment node. The following code contains the first one:

<!--#########Starting at a structure context as a root to a top level

item#################-->
<AliasAlternate name="ProductPartList">
<Path>AssociatedAttachment:AssociatedAttachment[@role='contents']:@childRefs</
Path>
<Path>AssociatedAttachment:*:@attachmentRef</Path>
<Path depth="1..1">*:*:@occurrenceRefs</Path>
&OCC-ATTR;
&FORM–MASTER-ATTR;
&ICO-ATTR;
</AliasAlternate>

The traversal tries each alias rule that has a primary object matching the start node and traverses
through each path statement until it gets to the Xpath statements. If any Path statement fails during
the traversal, the traversal tries the next matching alias statement. The first Path statement is:

<Path>AssociatedAttachment:AssociatedAttachment[@role='contents']:@childRefs</Path>

This statement causes the traversal to proceed to AssociatedAttachment nodes with role=contents via
the childRefs attribute in the PLM XML file. The PLM XML statement childRef attribute is:

childRefs="#id4 #id72">

Therefore, the traversal moves to PLM XML nodes with id4 and id72, if they match the role=contents
condition. The PLM XML node containing id4 is:

<AssociatedAttachment id="id4" attachmentRef="#id9" role="contents">

The next Path statement in the alias definition is:

<Path>AssociatedAttachment:*:@attachmentRef</Path>

This Path statement indicates that the system expected AssociatedAttachment nodes as results from
the last statement. If it did not, this alias definition would fail at this point.

The current Path statement tells the system to use the attachmentRef and return whatever is there.
The * symbol is a wildcard indicating that any node is sufficient. Consequently, the traversal proceeds to
the node containing #id9.

<Occurrence id="id9" instancedRef="#id43" associatedAttachmentRefs="#id45 #id46 #id49

#id67"
occurrenceRefs="id12 id32">

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-11

<ApplicationRef application="Teamcenter" label="SIEhslreBrSpAA/ScFh8BEQBrSpAA"></

ApplicationRef>
<UserData id="id10" type="AttributesInContext">
<UserValue value="" title="AO_ID"></UserValue>
<UserValue value="" title="SequenceNumber"></UserValue>
<UserValue value="" title="OccurrenceName"></UserValue>
<UserValue value="" title="Quantity"></UserValue></UserData>
<Transform id="id8">1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1</Transform></Occurrence>

Node 9 is an occurrence.

The next Path statement is:

<Path depth="1..1">*:*:@occurrenceRefs</Path>

This Path statement tells the system to go to the nodes referenced by the occurenceRefs attribute.
Again, the * wildcard is used, so the traversal picks up whatever node is contained in the PLM XML. The
first node ID is #12.

<Occurrence id="id12" instancedRef="#id14" associatedAttachmentRefs="#id19 #id22 #id25

#id30"
parentRef="#id9">

This node is also an occurrence. The first line contains all the relevant reference information.

The next statement in the alias definition is:

&OCC-ATTR;

This is a macro statement that implies that the traversal expects to be on an occurrence node at this
point and is getting ready to traverse its attributes.

At this point, the traversal again encounters alias names as shown for OCC-ATTR, ID, Description,
Name, and so on.

Remember that the binding specified was ProductPartsList & FormDescription. The traversal started at
the ProductPartsList node and arrived at this point. Now, it must find an alias name matching
FormDescription to find any additional XML traversal rules to use. Going through the OCC-ATTR
statement, the traversal cannot find any alias names that match FormDescription because the edit was
not added to that entry. Therefore, the traversal continues on to the next entry in the original alias
definition.

<!ENTITY OCC-ATTR "

<Alias name='ID'>
<Path>*:*:@instancedRef</Path>
<Path>*:*:@masterRef</Path>
<Xpath>@catalogueId|@productId</Xpath>
</Alias>
<Alias name='Description'>
<Path>*:*:@instancedRef</Path>
<Xpath>Description</Xpath>

8-12 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

</Alias>

<Alias name='Name'>
<Path>*:*:@instancedRef</Path>
<Xpath>@name</Xpath>
</Alias>
… many more Occurrence attribute Alias Names
“>

The next alias rule is:

&FORM-MASTER-ATTR;

The traversal looks in the alias file for this macro and starts traversing through the macro looking for an
alias named FormDescription. The traversal finds the newly added alias as follows:

<Alias name='FormDescription'>
<Path>*:AssociatedAttachment[@role='IMAN_specification']:@associatedAttachmentRefs</
Path>
<Path>*:Form:@attachmentRef</Path>
<Xpath>Description</Xpath>
</Alias>

Remember that the last node collected was:

<Occurrence id="id12" instancedRef="#id14" associatedAttachmentRefs="#id19 #id22 #id25

#id30"
parentRef="#id9">

Now the first Path statement in the current alias rule is this:

<Path>*:AssociatedAttachment[@role='IMAN_specification']:@associatedAttachmentRefs</Path>

This means the traversal is looking for AssociatedAttachment nodes with an IMAN_specification role.
This should be available through the AssociatedAttachmentRefs statement. In this case, the only node
that matches these criteria is the one with #id22 shown here.

<AssociatedAttachment id="id22" attachmentRef="#id23" role="IMAN_specification">

The next alias rule is:

<Path>*:Form:@attachmentRef</Path>

This means that using the attachmentRef attribute, the traversal expects to move to a form. #id23
indicates the node for which the traversal needs to search.

<Form id="id23" name="ATestForm" accessRefs="#id15" subType="OfficeDocForm"

subClass="OfficeDocForm">
<Description>ChildItem 1 Description</Description>
<ApplicationRef version="SYNhstU9BrSpAA" application="Teamcenter"
label="SYNhstU9BrSpAA"></ApplicationRef>
<UserData id="id24" type="FormAttributes">

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-13

<UserValue value="" title="Title"></UserValue>

This shows that #id23 is a form.

At this point, the traversal has successfully executed all the Path statements and ends with a final
destination node. The next statement in the alias rule is:

<Xpath>Description</Xpath>

The Xpath statements describe what information to take from the resulting node to use in the
publishing page. In the example, the property originally sought was the Description property of the
form attached to the ChildItem item. This Xpath statement says to return the data for the Description
entry for the current node. Looking at the PLM XML, this is:

<Description>ChildItem 1 Description</Description>

Looking at the populated publishing page in the figure entitled Example result – table asset populated
with child item names and form descriptions, you see the same description in the FormDescription
column for ChildItem 1. This accomplishes the goal of the example.

The Path statements are used to traverse from the start node to the final node. The Xpath statements
are used to extract information from the final node. There are potentially several valid paths from the
start node to the final node in the PLM XML. You need to determine any valid set of path statements to
reach the final node.

Specifying end objects

To specify which object is the end object that is exposed in an asset, you must mark it in a Path element
in the alias definition. The following example shows an existing alias alternate for populating a 2D asset:

<AliasAlternate name="2DGraphic">
<Path>AssociatedAttachment:AssociatedAttachment[@role='contents']:@childRefs</Path>
<Path>AssociatedAttachment:ConfiguredOccurreceGroup:@attachmentRef</Path>
<Path>ConfiguredOccurrenceGroup:*:@childRefs</Path>
<Path>Occurrence:AssociatedAttachment:@associatedAttachmentRefs</Path>
<Path>AssociatedAttachment:DataSet[@type='Image']:@attachmentRef</Path>
<Path>DataSet:ExternalFile[@format='jpg' or @format='jpeg' or
@format='gif' or @format='bmp']:@memberRefs</Path>
&FILE-ATTR;
</AliasAlternate>

8-14 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

To identify the end object, use the createRelation attribute on the last Path element:

This causes the end object UID to be sent back through Lifecycle Visualization to the Teamcenter rich
client, along with the createRelation identifier. The rich client then creates the
VisAssetPopulatedByEndobj relation from the publishing page dataset to the end object.

To create two different relationships to the same end object, use this syntax:

When customizing alias definitions, you can identify the end object for any asset and Teamcenter
creates the relation specified. You can define your own custom relations and have them created too by
adding appropriate createRelation clauses or by adding additional relation names to existing
createRelation clauses.

Navigating through a PLM XML file

One approach to determine the path statements needed for your alias definition is to find the final node
in the PLM XML file. Search the file for references to its ID. From this current node, find the node or
nodes that reference it. Continue this backward traversal making sure you can get to the start node.
Remember the start node is the node referenced by the traverseRootRef attribute. After you find a path
using the backward traversal from the final node to the start node, go back and record the type of each
node in the path. Use this information to build the path statements needed for an alias to your final
node. Additionally, look at existing alias path definitions for examples of how to traverse from one type
of node to another. A backward traversal using our example in pseudo XML would look something like
this:

1. The ChildItem 1 Description node, the data you want to expose in the asset, is in the Form
id=id23 node.

2. The Id23 node is referenced by AssociatedAttachment id=id22 as an attachmentRef type.

3. The Id22 node is referenced by the Occurrence id=id12 statement as an

associatedAttachmentRef type.

4. The Id12 node is referenced by the Occurrence id=id9 statement as an occurrenceRef type.

5. The Id9 node is referenced by the AssocatedAttachment id=id4 statement as an AttachmentRef

type.

6. The Id4 node is referenced by the AssociatedAttachment id=id3 statement as a childRef type.

7. The Id3 node is the traverseRootRef node from which traversal always starts.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-15

There is another reference to id22, but if you follow it back you see a pseudofolder. Pseudofolders are
generally not useful in a path traversal and can be ignored. After a while, it is useful to recognize what
entities in the rich client relate to which nodes in the PLM XML file. Through some experimentation,
these relationships become clearer. If you compare this pseudo XML code with the actual Path XML
statements traversed in the example, you can see how they relate to each other. Therefore, when you
need to update an alias file, if you can first determine a set of pseudo XML statements, it is easier to
write the Path and XPath statements needed to edit the alias file.

Strategies for working with alias files

The following are a few high-level tips and strategies about working with the alias file.

• Define a use case to work from.

1. Determine what will be selected and what you want to see in what type of asset.

2. When creating a template that will be used repeatedly, it is easier if the user can select a single
object with which to populate all of the data in the work instruction.

3. Find an example of the data in the database that you can select, for example, a BOM. If possible,
make it unique so you can find it easily in the PLM XML file.

4. Determine whether to use an existing alias or to add a new one to the Bind dialog box.

5. Determine what alias file to use. You can develop an alias file for this user or this use case only
that is simple to use and contains only one transfer mode, or you can add to an existing alias file.

• Identify a suitable transfer mode.

1. Generate a PLM XML file by populating an asset with the transfer mode that you think will work.

2. Examine the resulting file and make sure it has the data that you want to expose in the asset. If it
does not, you must find a better transfer mode, or you must modify the transfer mode’s closure
rules to include your data.

3. In some cases, it makes sense to create a custom transfer mode whose closure rules are
optimized to efficiently generate XML that supports only the assets in a single template.

• Examine the PLM XML file and identify the nodes that provide a path from the root ref to the data in
which you are interested.

• Define an alias alternate that follows the node path. To save time, test the alias definition using the
stand-alone test utility on the generated PLM XML file. The utility is described in the alias file header.

• Decide what other use cases need to be supported by your alias definition.

8-16 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

1. The data may be attached to the object in more than one way.

2. The user may start with a different populating object.

• Create a new use case and repeat this process.

Create a new publishing alias dataset

To create a new publishing alias from an existing alias file, do the following in My Teamcenter:

1. Use the Search button to find the Installed Alias dataset.

2. Export the TcPublishSystemAlias.xml file to your local disk using the Named References dialog
box.

3. Rename the local XML file to something meaningful, such as AliasTutorial.xml.

4. Choose File→New→Dataset.
Teamcenter displays the New Dataset dialog box.

5. In the list of dataset types, select TCPublishingAliases, and then type a name and description for
the new dataset.

6. Click the Import button, browse to the renamed alias file and click OK.
Teamcenter creates the new publishing alias.

7. Load the XML file into a text editor and read the notes at the top of the file.

Note:
Each time you create an alias dataset, you must load the alias file.
You can optionally include packing of tables in the alias definition. If you choose to pack tables,
lines that are identical except for quantity are collapsed into a single line. Two aliases with
collapsed tables are provided as templates, CollapsedProductPartList and
OperationConsumedParts.

Update a publishing alias

To update an existing publishing alias from a modified alias file, do the following in My Teamcenter:

1. Right-click the dataset and choose Named References.

2. Choose Edit→Cut to remove the existing named reference for this alias.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-17

3. Click the Import button, browse to the modified alias file and click OK or Apply. Teamcenter
updates the publishing alias.

Note:
Each time you modify an alias dataset, you must reload the alias file.

Load or reload the alias file

1. In My Teamcenter, create a new TCPublishingPage or load one of the publishing page templates.

2. Select the viewer pane and verify that the publishing page is loaded.

3. In your embedded Visio application, choose File→Load Alias.

Teamcenter displays the Load Alias File dialog box, with available aliases listed in the left-hand
pane and loaded aliases listed in the right-hand pane.
To load a newly created alias dataset that is not already listed in the Available Aliases pane, click
the Add File by Name button and browse to the newly created alias dataset.

4. To load a new alias file, select it in the Available Aliases pane and click the + button. To remove
(unload) an existing alias, select it in the Loaded Aliases pane and click the – button.
When the aliases are listed correctly, click OK or Apply to load and unload alias files as necessary.

Note:
If you update an existing alias dataset by replacing its named reference, reload it by selecting the
Reload aliases check box and clicking OK or Apply.

Create or edit publishing pages

1. Open a configured structure in the Manufacturing Process Planner, Part Planner, Plant Designer, or
Multi-Structure Manager application and select an occurrence.

2. Show the data tabs and select the tab for the required type of publishing page. You can configure
Teamcenter to show each publishing context in a separate tab. For example, a user clicks the Work
Instructions tab and the tab shows all the publishing pages associated with the occurrence by an
MEWorkInstructions relationship. If none exist, an empty page is displayed.

Note:
You can create publishing pages for activities only in Manufacturing Process Planner.

3. Browse though the existing publishing pages or create a new publishing page from a defined
template.

8-18 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

When editing an existing publishing page, the user can add, remove or edit Visio shapes and
associate them with Teamcenter assets. An asset is typically 3D geometry, a 2D or 3D snapshot, a
2D image, or a link to a Microsoft Word file or a text file.

4. Save the new or changed publishing page to associate it with the selected occurrence.

Creating manufacturing documentation in batch mode overview

You can create and update Teamcenter work instructions and portfolios in batch mode, processing
multiple documents using the Teamcenter Publish Batch dialog box. You do not need to process
individual documents manually. You can schedule these tasks to take place immediately or at a later
date.

Batch processing uses the Dispatcher infrastructure for scheduling create and update features.
Additionally, Dispatcher has built-in status, logging, and error reporting features. You can use the
Request Administrator Console dialog box to obtain status information about the submitted task. Find
this in the Translation menu of My Teamcenter after you install Dispatcher.

You must set up the batch processing in the Manufacturing Process Planner or Multi-Structure Manager
applications. You can use My Teamcenter to modify the scheduling of the batch process.

Enabling batch processing of publishing pages

Teamcenter batch processing of publishing pages uses Dispatcher infrastructure for scheduling create
and update features. You must install the PublishBatch translator to take advantage of this feature. This
enables the PublishBatch service.

There are several prerequisites for running the batch feature.

• The translator is installed on a Windows machine.

• VisAutomationApp, Microsoft Visio, FMS file client cache (FCC), and the Teamcenter service-oriented
architecture (SOA) client are installed on the translator machine. VisAutomationApp is installed
automatically when you install Lifecycle Visualization.

• The startPublishBatch.bat file is installed in a directory that is specified during installation of the
PublishBatch translator. Each setting in this file must be modified as specified in the file.

• The transmodule.properties file in the module/conf directory has a MaximumTasks setting that
defaults to 3. This defines the maximum number of instances of publish batch tasks that can run
simultaneously. Do not increase this value above 3.

• The clients and Dispatcher Server should point to the common staging directory, and both should
have read/write permissions to that directory.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-19

Troubleshooting the PublishBatch translator

The startPublishBatch.bat file is installed in a directory that is specified during installation of the
PublishBatch translator. As described in the file, if you add -log to the %TRANS_PATH%
\tcpublish_batch line, Teamcenter adds detailed progress and error entries to the task’s log file.
Teamcenter stores the log files in the directory you specify during installation.

8-20 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 8-21

8-22 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
9. Setting up enterprise bill of process
(BOP)
Configuring the enterprise BOP
You can use the following preferences, global constants, and cloning rules to configure the operation of
the enterprise BOP for your site.

The following global constants and preferences configure the logical designator form.

Preference/Constant Purpose

Mfg0OperationLD Specifies the type of form that represents the

logical designator of an operation. If empty,
logical designators are not created for
operations.

Mfg0ProcessLD Specifies the type of form that represents the

logical designator of a process. If empty, logical
designators are not created for processes.

Mfg0ProcessPartitionLD Specifies the type of form that represents the

logical designator of a process partition. If empty,
logical designators are not created for process
partitions.

MELogicalDesignatorDelimiter Specifies the delimiter in the display string of the

logical designator.

MELogicalDesignatorForm Specifies the suffix to the logical designator form

NameSuffix name.

The following preferences configure cloning of generic BOPs and product BOPs.

Preference Purpose

GenericBOPTemplate Contains the default cloning rule when using a

generic BOP as the template for creating a
product BOP.

ProductBOPTemplate Contains the default cloning rule when using a

product BOP as the template for creating another
product BOP.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 9-1

Preference Purpose

PlantBOPTemplate Contains the default cloning rule when using a

plant BOP as the template for creating another
plant BOP.

GenericBOPAllowedTemplates Contains a list of the cloning rules that are

available when using a generic BOP as a
template for creating a product BOP.

ProductBOPAllowedTemplates Contains a list of the cloning rules that are

available when using a product BOP as a
template for creating another product BOP.

PlantBOPAllowedTemplates Contains a list of the cloning rules that are

available when using a plant BOP as a template
for creating a plant BOP.

MEGenericBOP.MEGenericBOP. Contains the default cloning rule used when

PasteDuplicateTemplate executing the Paste Duplicate command from a
generic BOP context to another generic BOP
context.

MEGenericBOP.MEProductBOP. Contains the default cloning rule used when

PasteDuplicateTemplate executing the Paste Duplicate command from a
generic BOP context to a product BOP context.

MEProductBOP.MEProductBOP. Contains the default cloning rule used when

PasteDuplicateTemplate executing the Paste Duplicate command from a
product BOP context to a product BOP context.

MEProductBOP.MEGenericBOP. Contains the default cloning rule used when

PasteDuplicateTemplate executing the Paste Duplicate command from a
product BOP context to a generic BOP context.

PasteDuplicateTemplates Contains a list of cloning rules that are

considered by the Paste Duplicate command.

PasteDuplicateAllowedPlantBOP Contains a list of cloning rules names to be used

Templates when pasting duplicate objects (clones) between
different types of plant bills of process.

MEGenericBOP.Mfg0MEPlantBOP. Contains the default cloning rule used when the

PasteDuplicateTemplate Paste Duplicate command is executed between
a generic BOP context and a plant BOP context.

MEProductBOP.Mfg0MEPlantBOP. Contains the default cloning rule used when the

PasteDuplicateTemplate Paste Duplicate command is executed between
a product BOP context and a plant BOP context.

Mfg0MEPlantBOP.Mfg0MEPlantBOP. Contains the default cloning rule used when the

PasteDuplicateTemplate Paste Duplicate command is executed between
a plant BOP context and a plant BOP context.

9-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Preference Purpose

ProductBOPAllocationTemplate Contains the default cloning rule used when

allocating from a product BOP to a plant BOP.

ProductBOPAllocationCloningRule Contains the name of the cloning rule used for

allocating from a product BOP to a plant BOP.

The following preferences configure the allocation mechanism between product BOP and plant BOP.

Preference Purpose

MEAllocationLevel Contains the type of process area that can have

an operation or process allocation. If no type is
defined, there is no limitation on the operation
allocation.

MEProcessIconPropertyNames Specifies whether plant BOP structures display an

allocation indication symbol for processes if they
were allocated from a product BOP.

MEOperationIconPropertyNames Specifies whether plant BOP structures display an

allocation indication symbol for operations if
they were allocated from a product BOP.

The following preferences configure the expansion and display of the BOP.

Preference Purpose

typeAndRuleForProcessConfiguration BOP expand relies on this preference to evaluate

whether to filter out the consumed item parent
(typically an operation or process). This
preference includes what types and rules to
consider in order to run the evaluation (a server
intensive activity). By default, this preference
includes values that are OOTB types. If there is
no need to filter operations or processes while
expanding, you should leave the preference
empty.

MEBopDisplayAssyAsEndItems This preference improves BOP Display in the

embedded viewer while using Manufacturing
Process Planner. All consumed items in the BOP
structure are considered as an enditem while
being displayed in the embedded viewer. This
preference enables the lightweight loading of
the BOP structure where the traversal of the
BOM consumed under the process will be done
faster as it is being displayed in the embedded

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 9-3

Preference Purpose

viewer while using Manufacturing Process

Planner.

MEBopDisplayOccTypesList This preference defines occurrence types used

for the behavior displayed by the
MEBopDisplayAssyAsEndItems preference. The
default value is MEConsumed.

Two cloning actions are provided for enterprise BOP structures:

• EBOPCreate
Indicates the origin link relation. For example, this is used when cloning a product BOP from a generic
BOP.

• EBOPReference
Indicates that a product BOP origin link is used as a reference to construct the generic BOP link.

For these actions, configure the following copy action rule entries to use when cloning enterprise BOP
structures:

• MapLD.Ignore
Map according to logical designator equivalence. If unsuccessful, do not add the occurrence to the
clone.

• MAPLDAO.Reference
(Default action) Map according to logical designator equivalence. If unsuccessful, map according to
the absolute occurrence ID. If one is not found, the clone references the source.

• MAPLDAO.Ignore
Map according to logical designator equivalence. If unsuccessful, map according to the absolute
occurrence ID. If one is not found, do not add the occurrence to the source.

Setting up scheduled part assignment resolution

You can schedule the resolution of part assignments to run at a later date or time or at a specific
recurring time. This is helpful if you are resolving large structures where the action is time-consuming or
if you resolve structures on a regular basis. Teamcenter uses the Dispatcher application to run the
resolution—at a time you specify.

To use this feature, your administrator must configure the asynchronous services.

The asynchronous services require the installation of Teamcenter Dispatcher.

9-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Note:
Because asynchronous tasks run in a separate session, the current rich client session is not
updated to reflect any changes that are made. If you choose to execute the task immediately, you
do not see all of the results in the current session. Refreshing the window or reloading the
structure after the task is complete updates your session to see the changes made by the
asynchronous process. This is not an issue for sessions that start after asynchronous processing is
complete.

Setting up logistics planning

To set up the logistics management feature in Manufacturing Process Planner, there are the following
installation prerequisites:

• Vendor management

• Enterprise bill of process

Additionally, you must select the following TEM options:

• Logistic Process Planning

• Logistics for Rich Client

Teamcenter installs or modifies the following preferences when installing this solution. Normally, you
should not need to modify these preferences:

MEPlantRevision.RENDERING
MEPlantRevision.SUMMARYRENDERING
MEPlantRevision_DefaultChildProperties
MEPlantRevision_CompanyLocation_default_relation
MEAssignCustomizedOccurrenceType

To set up a basic logistics structure, the following is required:

• Vendor items set up in the vendor management system representing each supplier, including an exact
street address for each one

• An address specified in the Summary view for each plant revision

• A logistic BOP structure containing a linked plant and plant BOP structure

To allow the logistics station resolver to function properly with a collapsed plant BOP, you must ensure
that the in-context ID is populated on all the consumed lines of the plant BOP. Set the
MECopyIdInContextToAssignedLine preference to true before you assign any objects to the plant BOP
structure.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 9-5

Line balancing reports

Customizing a line balancing report

Line balancing is a method to improve the throughput of assembly lines while reducing manpower
requirements and costs. Line balancing addresses the problem of assigning operations to work stations
along an assembly line in such a way that the assignment be optimized in some sense. You perform line
balancing in Manufacturing Process Planner.

During the line balancing planning activities, you can create a variety of reports.

Line balancing uses the Teamcenter report framework to generate reports. The reports are created in
the Microsoft Excel XML format and saved in datasets. By default, the dataset is attached to the scope of
the view from which the report is launched. There is a defined default report definition and style sheet
associated with each report type. These are defined in preferences.

Preference for report

Report definition ID Preference for style sheet name

Constraints MELBConstraints MELBConstraintsConsistency

Consistency ConsistencyReportID Stylesheet
Check

Constraints MELBConstraints MELBConstraintsViolation

Violation Check ViolationReportID Stylesheet

Balancing MELBBalancing MELBBalancingOverview

Overview OverviewReportID Stylesheet

Line Detail MELBLine MELBLineDetailStylesheet

DetailReportID

You can create a new report definition in the Report Builder application and modify the report
preference to point to that new definition. You can modify the report definition to change parameters or
add style sheets.

Customize the contents of the reports

You can customize the following in a report definition:

• Hide a section of the report.

• Hide a column of the report.

• Add a column to show a BOMLine property.

1. Open the relevant report definition in Report Builder.

9-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

2. In the Parameters section, modify the parameters using the following parameters.

Name Meaning Example

HIDE Specifies a section of the HIDE CONSTRAINTS_DEFINITION

default report that is not
HIDE PROCESS_AREA_INFO
displayed.

HIDE_COLUMN Specifies a column of the HIDE UTILIZATION

default report that is not
HIDE CATEGORY_NVABR
displayed.

SHOW_COLUMN Specifies a BOM line SHOW_COLUMN bl_resequence_no

property that is added as an
additional column.

Line balancing report parameters

Constraints Consistency Check Report

Enter this To

HIDE CONSTRAINTS_DEFINITION Hide the Constraints Definition section of the report

Constraints Violation Check Report

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 9-7

Enter this To

HIDE CONSTRAINTS_DEFINITION Hide the Constraints Definition section of the report.

HIDE PROCESS_AREA_INFO Hide the Process Area section of the report.

Balancing Overview Report and Balancing Line Detail Report

9-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Enter this To

HIDE_COLUMN CAPACITY Hide the Capacity column.

HIDE_COLUMN WORK_CONTENT Hide the Work Content column.

HIDE_COLUMN ALLOCATED_TIME Hide the Allocated Time column.

HIDE_COLUMN REMAINING_TIME Hide the Remaining Time column.

HIDE_COLUMN Hide the Number of Workers column.

NUMBER_OF_WORKERS

HIDE_COLUMN CATEGORY_VA Hide the VA column.

HIDE_COLUMN CATEGORY_NVA Hide the NVA column.

HIDE_COLUMN CATEGORY_NVABR Hide the NVABR column.

SHOW_COLUMN BOM-line-property- Display a column for the specified BOM line property.
name

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 9-9

9-10 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
10. Administering time data in the Time
view
Configure new categories in the Time view
1. In the Business Modeler IDE, open the Advanced perspective by choosing Window→Open
Perspective→Other→Advanced.

2. Open the Activity Category in the Classic LOV folder in the Extensions view.

3. Add a new category, giving it a name and optional description.

4. Save and deploy the project.

Teamcenter adds a new category to the Time view.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 10-1

5. (Optional) Change the color of the category in the Options pane.

10-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

MTM data card

Configuring an MTM data card

You can add predefined activities based on information available in the Methods Time Measurement
(MTM) system to operations in the Time view in Manufacturing Process Planner. This system sets
industry-standard times required to perform standard manual tasks. The standards include a list of time
elements where each element represents a specific and short step a worker can perform as part of the
execution of an operation. Typically, the time elements are organized into groups according to types,
distance, and difficulty. The standards are based on repeated measurements done on real production
lines.

In the Time view, you can open a data card and select individual tasks containing a set time. Each of
these tasks is added as a separate activity. You can then use these standard times to run time
calculations and analyses.

The standard MTM data cards hold times in TMU (time measurement units). Teamcenter stores times in
seconds. The METimeDataCardConversionFactor preference specifies the factor to convert from data
card time units to seconds.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 10-3

You can also replace the MTM data card with a customized one that includes times required for tasks
that are specific to your company. If your customized data card contains times in units other than TMU,
you must define the conversion rate between your data card units to seconds in the
METimeDataCardConversionFactor preference.

Note:
Please be aware that the proper use of the time data card functionality does require thorough
training in MTM methodology. Without such training the user activities may lead to erroneous
results and does not represent a true MTM analysis.
For MTM training please contact your local MTM association.

Install MTM data cards

You must install the data cards using Teamcenter Environment Manager before you can use them in
Manufacturing Process Planner. The default data cards are not available until you install them.

Create your own data card

1. Create a Microsoft Excel spreadsheet containing the data card information.

Each cell holding the time data must contain a hyperlink with the following format:

usercode://code1|time_as_double|description

Where Is

code1 The time code that appears in the Code column in the
Activities table.

time_as_double The time required for the activity expressed as a double

format.

description The description of the activity. Teamcenter copies the

description and uses it as the name of the activity.

Note:
You must use the pipe character (|) as a separator. To prevent illegal characters, you can use
the ASCII hexadecimal representation %7C. You can use other hexadecimal symbols to
replace special symbols in your URL text if you get incorrect results.

2. In Excel, choose File→Save As... to save the spreadsheet as a Web page (HTM or HTML extension).

3. Type the path to the HTM or HTML file in the METimeDataCardPath preference.

10-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

4. Make sure that the METimeDataCardConversionFactor preference is correctly set.

If you enter seconds as the unit in the Excel sheet, set this factor to 1.

Tip:
You can also find these preferences in the Data Card section of the Time tab of the
Manufacturing section of the preference Options dialog box.

5. Restart Teamcenter.

When you open a data card in the Time view, Teamcenter displays a tab for each sheet in the Excel
file. When you click an activity cell in the data card, the activity time is displayed in the Activities
table of the Time view.

TiCon integration

Understanding the Teamcenter to TiCon mapping

You can access time data from TiCon, an external time management system, and assign it to activities in
Manufacturing Process Planner using a Web service. You can search for time elements in TiCon, create
new activities, or overwrite existing activities with the timing data of time elements, and update
activities assigned to time elements that were changed in TiCon. You can use the existing time
management features to calculate time analysis based on the TiCon data.

By default, Teamcenter uses the following internal mapping system to map Teamcenter activity
properties to TiCon time element attributes:

<?xml version="1.0" encoding="UTF-8"?>

<xsi:Configuration xmlns:xsi="http://www.siemens.com/plm/Teamcenter/MSE/
TimeFieldMap">
<FieldMapping>
<Field TeamcenterProperty="al_activity_object_name"
TimeSystemAttribute="description"/>
<Field TeamcenterProperty="al_activity_time_system_unit_time"
TimeSystemAttribute="tg"/>
<Field TeamcenterProperty="al_activity_time_system_category"
TimeSystemAttribute="indicator1id">
<Value TeamcenterPropertyValue="NA" TimeSystemAttributeValue="1"/>
<Value TeamcenterPropertyValue="VA"
TimeSystemAttributeValue="10000"/>
<Value TeamcenterPropertyValue="NVA"
TimeSystemAttributeValue="10001"/>
</Field>
</FieldMapping>
</xsi:Configuration>

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 10-5

You can use the default mapping as a starting point to create your own mapping file. You can modify
the default mapping to map your company’s activity properties to the TiCon time element attributes.

Map attributes of time elements to activity properties

1. Create a mapping file to map activity properties used by your company to TiCon time elements.

2. Create a dataset in Teamcenter and import the mapping file to it.

Siemens Digital Industries Software recommends you create a Text dataset as it is easiest to edit.

Note:
You must create this dataset within a folder.

3. Add the name of this dataset, its type, and reference type to the
METimeSystemFieldMappingDataset preference.

10-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
11. Configuring studies
Enable Study Manager
To enable Manufacturing Process Planner Study Manager, you must install Active Workspace on top of
Teamcenter and deploy Teamcenter Manufacturing Access as follows.

1. From the Teamcenter Manufacturing Access kit_location folder, unzip wntx64\tc\tca0tcmaccess.zip

or lnx64\tc\tca0tcmaccess.zip into a tca0tcmaccess temporary folder.

2. Copy the .jar files from the tca0tcmaccess folder.

3. On the Teamcenter 4-tier client, paste the .jar files into the TC_ROOT\portal\plugins folder.

4. In the Teamcenter rich client, set the following preferences.

• Set MEStudyManagerEnabled to true.

• Update the Default_StructureContext_Type value to

Mfg0MEStudy:Mfg0StudyStructureContext.

• Define the ActiveWorkspaceHosting.PS.URL and TCMAccessHosting.RAC.URL values.

Set up study synchronization

You must set up the study synchronization rules before publishing or synchronizing a study.

Note:
You must have DBA privileges to perform this task.

The synchronization rules are set up using a combination of object type and property that are to be
considered.

1. Choose Advanced→Study Synchronization Rules.

2. Select the synchronization mode.

• Event-Based
Performs a partial synchronization or publish of only the selected properties.

• Time-Based
Performs a full synchronization or publish.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 11-1

3. Select the direction in which the changes are synchronized.

• Select To Study to set up synchronization changes from the source process structure to the
study.

• Select From Study to set up publish changes from the study to the source process structure.

4. Choose whether to include or exclude the properties you select in the list.

• To exclude properties from synchronization:

a. Select Exclude the following properties. Include the rest.

b. Press Ctrl and select the object type and property name of each property you do not want
to include.

Tip:
To perform a full Time-Based synchronization, select Exclude the following properties
and remove all entries from the properties list.

• To include properties in synchronization:

a. Select Include the following properties.

b. Select the object type and property name.

c. Click Add.

d. Click each newly highlighted cell and open the list of entries by clicking the down arrow.

e. Select the desired object type and property name.

Tip:
To synchronize children of selected structures, select the object type and the
Mfg0sub_elements property.

5. Click Save.

Teamcenter saves the settings in study preferences. You do not need to modify these preferences
manually.

11-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Note:
You can set up custom synchronization rules by adding modes to the Mfg0SimStudyRuleMode
global list of values (LOV) in the Business Modeler IDE. By default, this LOV contains only Time-
Based and Event-Based entries. Your new mode is then displayed in the Manage
Synchronization Rules dialog box, and you can create corresponding synchronization and publish
rules for the custom mode.

Study Manager preferences

If the Teamcenter Manufacturing Additions package (Teamcenter Manufacturing Access Services) is
installed, as well as Active Workspace, you can use the following preferences to enable Study Manager.

• MEStudyManagerEnabled
Indicates if the Study Manager is enabled and prevents studies connected to a collaboration context
with the relation specified in the preference
CCObject_Mfg0StudyStructureContext_default_relation from loading in Manufacturing Process
Planner directly. By default, this preference is true.

• Default_StructureContext_Type
Determines which type of structure context will be the default for an item type. Accepts one or more
strings as values; each string must make valid use of the following format:
<item_type>:<StructureContext_type>
Values:
Process:MEProcessContext
OP:MEProcessContext
WorkArea:MEPlantContext Item:MEProductContext
MEGenericBOP:MEProcessContext MEProductBOP:MEProcessContext
Mes0MESTXLibrary:MEProcessContext
Mfg0MEProdPrgCol:Mfg0MEProdPrgContext
Mfg0MEStudy:CompositionContext

Note:
To enable Study Manager in the Teamcenter rich client, the Mfg0MEStudy value must be set to
Mfg0StudyStructureContext.

• ActiveWorkspaceHosting.PS.URL
Specifies the URL used by Process Simulate to communicate with the Teamcenter environment for the
Teamcenter Manufacturing Access application.

Example:
http://pnv6s1325:7333/tcmaccess

• TCMAAccessHosting.RAC.URL

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 11-3

Specifies the URL used by Teamcenter rich client for showing the Study Manager view via the
Teamcenter Manufacturing Access application.

• TCMAccessHosting.RAC.URL
Specifies the URL used by the Teamcenter rich client to show the Study Manager view of the
Teamcenter Manufacturing Access application. Default value: empty. After installing Teamcenter
Manufacturing Access, you must update this preference with the correct URL.

• CCObject_Mfg0StudyStructureContext_default_relation
Specifies the relation that has to be created when Mfg0StudyStructureContex is pasted under a
collaboration context object. The relation specified is the default relation between the source and
target. Default value: Mfg0CCStudyRel.

• CCObject_DefaultChildProperties
Lists properties that can be used as children for the indicated type (collaboration context object). By
default, Mfg0CCStudyRel is added to the list in order to show all studies in the collaboration context
tree and in My Teamcenter. After installing Teamcenter Manufacturing Access, you must change this
preference and remove Mfg0CCStudyRel using the following format:

<TypeName>_DefaultChildProperties=my_property

• Mfg0MEShdStudyRevision.CellProperties
Defines the list of properties to be displayed under a cell for objects of the type
Mfg0MEShdStudyRevision in the Active Workspace client. Valid values are property internal names.
Default values: object_name, item_id, and item_revision_id.

• Mfg0MESimStudyRevision.CellProperties
Defines the list of properties to be displayed under a cell for objects of the type
Mfg0MESimStudyRevision in the Active Workspace client. Valid values are property internal names.
Default values: object_name, item_id, and item_revision_id.

• AWC_Mfg0MEShdStudy.CREATERENDERING
Defines the rendering stylesheet for the Mfg0MEShdStudyCreate wizard. Default value:
Awp0Mfg0MEShdStudyCreate.

• AWC_Mfg0MESimStudy.CREATERENDERING
Defines the rendering stylesheet for the Mfg0MESimStudyCreate wizard. Default value:
Awp0Mfg0MESimStudyCreate.

• CCObject_VisStructureContext_default_relation
The Mfg0CCStudyRel value sets the relation for VisStructureContext to Study Manager.

• CCObject_DefaultChildProperties
When the value Mfg0CCStudyRel is added to this preference, a study structure context under the
collaboration context tree is displayed.

• CCObject_VisStructureContext_default_relation

11-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

When the value Mfg0CCStudyRel is added to this preference, the default relation for
VisStructureContext is Mfg0CCStudyRel and not IMAN_CCObject.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 11-5

11-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
12. Administering EBOM and MBOM
Reasons for creating an MBOM
When working in the manufacturing environment, Siemens Digital Industries Software recommends
that you create a manufacturing bill of materials (MBOM) from your engineering bill of materials
(EBOM). There are several reasons for this:

• Generally, manufacturing engineers do not have write privileges on the EBOM and cannot modify it.
For example, a design engineer may specify that a part is going to be purchased and sets a property
value to buy. Subsequently, the manufacturing department determines that it is more economical for
them to make this part. They want to change that property to make but do not have the privilege to
do so.

• Assembling a part requires a structure that is different from the EBOM structure. For example, in the
BOM, the exhaust manifold is part of the engine compartment. During assembly, however, the
exhaust manifold must be added after the body is built onto the chassis as the exhaust pipe must be
put through the bumper. This type of regrouping and adding of manufacturing-specific parts is most
efficiently performed in a separate manufacturing BOM structure.

• Especially for final assembly, companies often have manufacturing parts that they consume in
different MBOMs. These can only be created in a structure to which you have write access.

• There may be changes to an EBOM that should not immediately be reflected in the process structure.
For example, you may want to continue manufacturing using the current parts to use up existing
inventory. By using an MBOM, the manufacturing engineers have control over when the changes to
the EBOM are reflected in the manufacturing process.

• Some companies do not author the EBOM in Teamcenter. It is imported from another system so that
the EBOM in Teamcenter is a replication of the status of the EBOM in another system. Using an MBOM
provides you with a buffer for these changes so that you can monitor and process them in a
controlled manner.

Comparing the EBOM and MBOM

The manufacturing engineer creates a manufacturing structure (MBOM or manufacturing bill of
materials) from the product structure (EBOM or engineering bill of materials). The MBOM is a different
arrangement of the EBOM that can be optimized for manufacturing purposes. You must specify two
structures to be the EBOM and MBOM using the Link Structures command. When you link an EBOM
with an MBOM, their BOM view revisions are linked by an METarget relation.

To ensure that all required parts in the EBOM are contained in the MBOM you can run an advanced
accountability check. This feature uses the in-context ID (IDIC represented by the AbsOccID property) to
establish logical equivalence between aligned occurrences. If you want to use this feature, you cannot
use the in-context ID for any other purpose. Using an accountability check, you can see if parts have

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-1

been added or removed from the EBOM, discern any property changes, propagate any changes from the
EBOM to the MBOM, or run the accountability check at a scheduled time.

If you use Multi-Site Collaboration and want to consume a remote EBOM in the MBOM, you must create
the in-context IDs for the BOM lines to be consumed at the owning site before you export the EBOM to a
remote site. Otherwise, a check does not report differences between the structures.

Caution:
• You cannot link an EBOM to an MBOM contained in a composition structure context. If you use
a structure context to hold the MBOM, you cannot use the alignment check feature.

• Cutting and pasting the same line back into an MBOM creates a new occurrence without an in-
context ID. This removes the equivalence between the new occurrence and the original source
part in the EBOM and causes the pasted line to be displayed as missing in the other structure in
an accountability check.

EBOM-MBOM preferences

Preference Description

MEAlignedPropertiesList Defines the list of BOM line properties considered

during alignment, comparison, and synchronization
of aligned occurrences. By default, the AbsOccID,
Child Item, Notes, Quantity, Unit of Measure,
Transform, Substitute List, Source, and Occurrence
Type properties are considered. Do not add
properties to this preference unless you ensure
methods exist to read from and write to them.

MEAlignedPropertiestoExcludeFrom- Defines a list of BOM line properties that are not

Detection compared when aligning occurrences in the EBOM
and MBOM.

MEAlignedPropertiestoExcludeFrom- Defines the list of BOM line properties that are not
Initialization copied to an MBOM when the part is originally
assigned from the EBOM to the MBOM.

MEAlignedPropertiestoExcludeFromSync Defines a list of BOM line properties that are not

copied to the aligned target occurrence during
synchronization.

MEAlignmentCheckReportLocation Defines if a persisted EBOM-MBOM alignment report

is stored in a dataset in the My Teamcenter Newstuff
folder or if it is attached to the item revision of the
top line of the target window.

MEAlignmentCheckReportDefinition Contains the name of the report definition that

controls the creation of the EBOM-MBOM alignment

12-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Preference Description

check report. A default report definition is provided

but you can supply a custom report definition if
necessary.

MEAlignmentCheckReportStylesheet Contains the name of the Microsoft Excel style sheet

on which the EBOM-MBOM alignment check report is
based. A default style sheet is provided, but you can
supply a custom style sheet if necessary.

MEAssignAttachmentAndRelationTo- Specifies which attachment and relation types are

UseInCopyRule referenced when you carry forward attachments that
are associated in-context in the source structure.

MEAssignAttachmentContext Specifies the context of the in-context attachments

after assignment.

MECreateIdInContextforAssignedchildlines Assigns an IDIC to the child lines when assigning the

parent from the EBOM to the MBOM.
If you assign a line containing children from the
EBOM to the MBOM, by default, only the parent line
is given an IDIC. If you remove that parent line from
that MBOM, the children move up a level in the
hierarchy, but because they do not have an IDIC, they
do not show up as a match when running an
accountability check between EBOM and MBOM. You
can change this behavior in the
MECreateIdInContextforAssignedchildlines
preference.

MEEffectivityAssignmentMode Defines the assignment behavior from an

Engineering BOM (EBOM) to a Manufacturing BOM
(MBOM) for the BOMline property
bl_occ_effectivity.
0 (Default) Keep the default Teamcenter behavior.
1 Inherit assignment behavior from parent.
2 Apply calculated net effectivity behavior.

MEMBOM_Mirror_MakeRules Specifies a BOM Line property, such as

bl_item_object_type, and property value pair that
serve as input for the decision as to whether to
create a manufacturing-specific part.
There are two ways to view defined BOM Line
property names: 1. In the BMIDE, you can check the
properties defined for the object BOM Line. 2. In
Structure Manager, if you right-click on the column

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-3

Preference Description

title line and choose Insert Column(s)…, you get a list

of the defined BOM Line properties.
A common criteria may be, for example, whether you
make or buy a part. Any parts designated as make in
the EBOM are replaced by manufacturing-specific
parts in the MBOM.

MEMBOM_Mirror_RemoveLineWithIDIC Specifies that if a line in the EBOM is removed using

the me_create_mbom utility, its counterpart in the
MBOM is removed at update if it is already stamped
with an IDIC.

MEMBOM_Mirror_TypePrefixSuffix Specifies the item type for the new manufacturing-

specific item and any prefix or suffix to add to the
name of the part in the EBOM that is being replaced
by a new part in the MBOM using the
me_create_mbom utility.

MEMBOM_Mirror_ReplaceMakeOnChange Enables the replacement of manufacturing BOM

(MBOM) lines that were changed from Make to Buy
in the engineering BOM (EBOM) during the MBOM
update from the EBOM using the me_create_mbom
utility.

RollUp_Variant_Traverse_Level_Is_- Determines the level to which rolled-up variant

InstallationAssembly conditions are calculated.

Automatically creating an MBOM from an EBOM

Teamcenter provides you with several automatic methods to create a manufacturing bill of materials
(MBOM) from an EBOM (engineering bill of materials).

• Create an MBOM from a recipe

Create an MBOM from a template that contains a recipe for searching the EBOM for required parts.
The recipe can contain a variety of search attributes such as an attribute search, spatial search, ID
search, or combinations of search criteria.
This type of creation mechanism works well for make to shelf industries where the products are
standardized such as the automotive or home appliance industries.

• Use the me_create_mbom utility

The me_create_mbom utility creates an MBOM based on a specific EBOM but replaces make parts or
phantom levels in the EBOM with manufacturing-specific parts and directly copies over buy parts.
Your administrator can take advantage of user exits in this utility that allow you to embed your own
logic into the utility that specify:

12-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• What constitutes a make part using the USER_create_or_ref_item user exit (exposed in Business
Modeler IDE using the BMF_ITEM_create_or_ref_id operation on an Item object).

• How to synchronize equivalent lines and align properties using the USER_synch_item user exit
(exposed in Business Modeler IDE using the BMF_ITEM_sync operation on an Item object).

• What constitutes equivalent lines if there is no in-context ID or occurrence thread using the
USER_item_find_equivalent_line user exit (exposed in Business Modeler IDE using the
BMF_ITEM_find_eqv_line operation on an Item object).

• Which action to take on a released MBOM Item Revision object during update using the
USER_item_action_on_release user exit (exposed in Business Modeler IDE using the
BMF_ITEM_action_on_release operation on an Item object).

For more information, see Integration Toolkit Function Reference.

Your administrator can create a workflow to run this utility using the ME-create-mirror-AH and the
ME-update-mirror-mbom-A action handlers.
This type of MBOM creation method works well for configure to order customers such as heavy
machinery.

Note:
Neither of the methods to create MBOMs supports part replacement through propagation.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-5

Create an MBOM from a recipe

You can automatically create an MBOM based on a recipe. A recipe consists of search criteria saved on
each node of an MBOM template that define the parts to assign to that specific node.

Beginning with an MBOM template that contains phantom levels, you define a recipe for each part that
is to be manufactured. When you run the search, Teamcenter searches in the specified EBOM for parts
that fulfill the criteria and assigns them to the MBOM.

Unless a cloning rule is set up to ignore MBOM recipes, wWhen you clone an MBOM that contains
recipes, Teamcenter clones the recipes as well.

1. Open the MBOM template on which you want to save recipes.

This MBOM must already be linked to an EBOM structure.

12-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

2. Right-click a node on which you want to save a search criteria and choose Open With→BOM
Recipes.

3. In the BOM Recipes view, click Create/Update Recipe .

4. In the BOM Recipe Details view, enter a name for the search and the search criteria that describe
the parts that you want to add to the MBOM at the selected node.

What you enter as search criteria is company-specific but may include usage address, position
designator, or a function-based numbering scheme making up the ID.

You can add multiple criteria to one search box by separating them with a semicolon.

5. Click Validate BOM Recipe .

Teamcenter runs the search on the EBOM and lists the parts that fulfill the search criteria in the
BOM Recipe Validation Results view. Use this step to verify that you have entered the correct
criteria.

6. In the BOM Recipe Details view, click Create New Recipe .

Teamcenter lists the new recipe in the BOM Recipes view. You can save multiple recipes on an
MBOM node.

7. Do one of the following:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-7

• To resolve one node of the MBOM template, select the recipe in the BOM Recipes view and click
Resolve BOM Recipe .

• To resolve multiple nodes of the MBOM template, select a node in the MBOM template and
choose Tools→Resolve BOM Recipe.

8. In the Resolve BOM Recipe dialog box, select whether to remove the previously assigned parts
and click OK. If you open the dialog box from the Tools menu, you can choose to resolve all nodes
underneath the selected node by selecting Resolve recipe recursively.

Teamcenter adds the parts from the EBOM that fulfill the search criteria to the MBOM.

Additionally, the resolved parts are listed under the recipe in the BOM Recipes view.

You cannot directly copy a BOM recipe. You can, however, select a recipe in the BOM Recipes view, and
then select a different node in the MBOM. The search criteria are still visible in the BOM Recipe Details
view where you can save them as a new recipe on a different MBOM node.

12-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Creating an MBOM using the me_create_mbom utility

The me_create_mbom utility creates an MBOM based on a specific EBOM, but replaces make parts or
phantom levels in the EBOM with manufacturing-specific parts and directly copies over buy parts.

Do not use this utility to update the MBOM. To update an MBOM, use an accountability check or an
advanced accountability check.

You can create a manufacturing bill of materials (MBOM) from an engineering bill of materials (EBOM)
automatically using the me_create_mbom utility. This utility creates a new MBOM root node, and then
either:

• Copies over engineering parts that are designated as Buy or Phantom.

• Replaces the parts designated as Make with new manufacturing parts containing the same in-context
ID (IDIC) as the engineering part for future comparison.

Example:
me_create_mbom -u=kj -p=kj -g=Engineering -
key="item_id=000159,object_type=Item" -revrule="Latest Working" -
mrevrule="Latest Working" -log=D:\workdir\create3.csv –usemfk

Caution:
Log off any interactive session that uses the same structures as the structures you update with the
utility before you use the utility to avoid failures due to locking of objects in that user session.

The utility is affected by the values of these preferences:

• MEMBOM_Mirror_MakeRules
This preference specifies a BOM Line property, such as bl_item_object_type, and property value pair
that serve as input for the decision as to whether to create a manufacturing-specific part.
There are two ways to view defined BOM Line property names:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-9

1. In the BMIDE, you can check the properties defined for the object BOM Line.

2. In Structure Manager, if you right-click on the column title line and choose Insert Column(s)…,
you get a list of the defined BOM Line properties.

Preference syntax
KEY:<BOMLinePropertyInternalName>,VALUE:<PropertyValue>,ACTION:<ActionValue>

• <BOMLinePropertyInternalName> is the property on which the value criterion will apply (e.g. "GCS
CP").

• <PropertyValue> is the value used by the criterion.

• <ActionValue> is the action to undertake on the BOM node.

Valid values are PartLink (links a Design node to Part node) and PartAssign (links and assigns a
Design node Under a Part node).

Note:
ACTION is only meant for Design/Part like structures. If more than one value for a given
property can determine the action, the operator OR ('|') can be used as follows:
"KEY:<BOMLinePropertyInternalName>,VALUE:<PropertyValue1>,ACTION:<ActionValue1>|
VALUE:<PropertyValue2>,ACTION:< ActionValue2>" (e.g. "KEY:GCS CP,VALUE:Make|
VALUE:MakePart,ACTION:PartAssign|VALUE:MakeLink,ACTION:PartLink"). If there is no
preference value, the item is shared between Engineering BOM (EBOM) and Manufacturing
BOM (MBOM) structures.

A common criteria may be, for example, whether you make or buy a part. Any parts designated as
Make or Phantom (for organizational purposes) in the EBOM are replaced by manufacturing-specific
parts in the MBOM. In this case, the value of this preference may look like this:

KEY:Usage_MakeOrPurchase,VALUE:Make|VALUE:Phantom

You can use a custom property in this preference. If you do not assign any value, the utility carries
over the parts from the EBOM directly.

Note:
You should write your own Business Modeler Framework extension to control a make or buy
decision.

• MEMBOM_Mirror_TypePrefixSuffix
This preference specifies the item type for the new manufacturing-specific item and any prefix or
suffix to add to the item ID of the part in the EBOM that is being replaced by a new part in the MBOM.
If you use custom manufacturing business object types, you can add this type to the value of this
preference.

12-10 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

The default value of -usemfk is false. If true, and only the object type is present in
MEMBOM_Mirror_TypePrefixSuffix, use that type and the ebom item id for MFK value. If you set the
command line option -usemfk to true and specify only the item type, you can enter multifield keys.
If your company uses naming rules for new items, you must ensure that the prefix that you assign in
this preference corresponds to the naming rules for the manufacturing item. Alternatively, you can
remove all naming rules for manufacturing items. A conflict with item naming rules leads to this error
message:

• MEMBOM_Mirror_ReplaceMakeOnChange
This preference specifies the behavior when, after creation of an MBOM, you change a make/buy
property value from Make to Buy. At update, by default, Teamcenter simply appends the buy part to
the existing structure without removing the make part already in the MBOM. If you set this preference
to TRUE, at update, Teamcenter replaces the make part in the MBOM with the buy part from the
EBOM, avoiding duplication of parts.

• MEMBOM_Mirror_RemoveLineWithIDIC
This preference is applicable to updating an MBOM with the utility. It specifies that if the in-context ID
(IDIC) of a line in the MBOM is not found in the EBOM, or if a line in the MBOM has no IDIC, it is not
removed at update if it is already stamped with an IDIC.

• MEMBOM_Mirror_IDICOnChildren
This preference determines whether the IDIC is retained on a make part in the MBOM when updating
it using the utility after changing a make part to a buy part in the EBOM. When updating, if the
MEMBOM_Mirror_ReplaceMakeOnChange preference is set to FALSE, both the original make part
and the buy part exist in the MBOM after updating. This causes the accountability check to display
multiple matches. Removing the IDIC on the make part ensures that there is only one match in an
accountability check. If the MEMBOM_Mirror_ReplaceMakeOnChange preference is set to TRUE,
the make line is replaced with the buy line from the EBOM so this preference is irrelevant.

• MEMBOM_Mirror_IgnoreRules
This preference uses the keyword ACTION to skip an EBOM node or to traverse below an EBOM node
while ignoring that EBOM node. The children of the traversed EBOM node become the children of the
corresponding MBOM parent.

• MEMBOM_Mirror_AlignProperties
This preference controls which properties and attachments are copied from the EBOM to the MBOM
by enabling the alignment of properties on Make items and revisions. The Make nodes are of
different types than the original EBOM nodes.

The following examples of running the utility demonstrate its use and the differences in output caused
by changing the utility arguments. The initial values of the preferences are as follows.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-11

MEMBOM_MakeRules=KEY:Usage_Product,VALUE:Make|VALUE:Phantom

MEMBOM_RemoveLineWithIDIC=FALSE

MEMBOM_TypePrefixSuffix=Company,,

Note:
No prefix is used in this course due to the naming rule conflict.

Creating an MBOM

For the following EBOM:

Run the utility:

me_create_mbom -u=user-name -p=password -g=group -ebomroot=000202

-revrule="Latest Working" -mrevrule="Latest Working"

Produces the following MBOM:

12-12 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Note the following:

• The top-level node is replaced with a manufacturing-specific part.

• The make and phantom parts are replaced with new manufacturing-specific parts.

• The buy parts of the EBOM are directly copied over to the MBOM.

• An IDIC is generated for all parts except for those below a buy part.

• The in-context ID (IDIC) of the new parts is the same as the original part in the EBOM. This is true if
the IDIC is already present in the EBOM part.

• When you right-click the top node of the EBOM or MBOM and choose Link/Associate→Link
Structures, you can see that the utility has linked the two structures.

Creating the MBOM to a specific level

For the following EBOM:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-13

Run the utility:

me_create_mbom -u=user-name -p=password -g=group -ebomroot=000202

-revrule="Latest Working" -mrevrule="Latest Working" -depth=2

Produces the following MBOM:

Note that the new MBOM contains only two levels of structure. The remaining levels in the EBOM are
ignored.

Updating the MBOM from a specific line

You now update the MBOM above, but only for the M_000225 line and down, requiring the following
utility command:

me_create_mbom -u=your-user-name -p=your-password -g=your-group

-ebomroot=000202 -scopeid=000225 -revrule="Latest Working"
-mbomroot=M_000202 -mrevrule="Latest Working"

The utility creates the following MBOM:

12-14 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Changing Make to Buy and Buy to Make in the EBOM

For the following EBOM and MBOM:

You change the Make value to Buy for the drive gears and change the Buy value to Make for the rcvr
remote control in the EBOM and run the utility as follows:

me_create_mbom -u=user-name -p=password -g=group -ebomroot=000202

-scopeid=000225 -revrule="Latest Working" -mbomroot=M_000202
-mrevrule="Latest Working" -update

The results are as follows:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-15

When the rcvr remote control part is changed from a Buy to a Make, the utility replaces the buy part in
the MBOM during update. Buy to make behavior is not affected by preference settings. For the make to
buy change (the drive gears), the behavior depends on two preferences:

• The MEMBOM_Mirror_ReplaceMakeOnChange preference is set to FALSE. The make part is not

removed from the MBOM. The buy part is added to the structure.
The IDIC values on the make part are determined by the MEMBOM_Mirror_IDICOnChildren
preference.

• If MEMBOM_Mirror_IDICOnChildren is set to FALSE (or does not exist), the IDIC on the make part
in the MBOM is retained. Performing an accountability check between the EBOM and MBOM results
in multiple matches as the MBOM contains both a make and a buy part with the same IDIC.

• If MEMBOM_Mirror_IDICOnChildren is set to TRUE, the IDIC on the make part in the MBOM is
deleted and an accountability check displays the make part as missing in source.

Caution:
You must exercise caution when removing an IDIC on any part. This can cause problems in
other areas, for example, if the part is consumed in an process structure, you lose the link to
that line.

• The MEMBOM_Mirror_ReplaceMakeOnChange preference is set to TRUE.

The buy part (drive gears) replaces the make part. The result of the MBOM after update is as follows:

12-16 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

In summary, the behavior of the preferences is as follows:

MEMBOM_Mirror_ReplaceMakeOnChange FALSE The buy part is added to MBOM and

the previous make part is kept in the
MEMBOM_Mirror_IDICOnChildren TRUE structure but its IDIC is removed.

MEMBOM_Mirror_ReplaceMakeOnChange FALSE The buy part is added to MBOM and

the previous make part is kept in the
MEMBOM_Mirror_IDICOnChildren FALSE structure but its IDIC is not removed.

MEMBOM_Mirror_ReplaceMakeOnChange TRUE The buy part is added to MBOM and

the previous make part is removed in
MEMBOM_Mirror_IDICOnChildren TRUE/FALSE the structure, irrespective of the
value of
MEMBOM_Mirror_IDICOnChildren.

Updating a released node in the MBOM

In the following EBOM and MBOM, M_000229/A;1–M_rear_drive_asm is released and then the
make/buy property on its child, 000230/A;2–rear_axle, is changed from Buy to Make.

You revise the MBOM part so you have write access and run the update utility.

You run the utility with the -actiononrelease argument set to 2.

me_create_mbom -u=your-user-name -p=your-password -g=your-group

-ebomroot=000202 -scopeid=000225 -revrule="Latest Working"
-mbomroot=M_000202 -mrevrule="Latest Working" -actiononrelease=2 -update

The results are as follows:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-17

The utility revises the part and replaces the old revision with the new one.

Changing properties in the EBOM

To detect property changes in the EBOM, run an accountability check between the EBOM and MBOM.
You can propagate any property differences using the accountability check mechanism.

Attachments

Attachments are always synchronized as the attachment is created as a reference on the new make part.
Any changes to the attachments on the EBOM side are automatically reflected in the MBOM. If you add a
new attachment to the EBOM, you must run the update to see it in the MBOM part.

Reconciling EBOM and MBOM in a Multi-Site environment

The determination of equivalence between the engineering bill of materials (EBOM) and the
manufacturing bill of materials (MBOM) is based on the in-context ID (IDIC, also referred to as the
absolute occurrence ID). When you paste a part from the EBOM to the MBOM, Teamcenter generates an
identical, unique absolute occurrence ID for the part on both the EBOM and the MBOM. This mechanism
is used when aligning structures to determine whether parts are missing in the source or target
structures.

12-18 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

The ID is generated in the context of the top-level item. Even if you do not have write access to the top
level of the EBOM, Teamcenter allows this ID to be generated and saved with the top-level item. If you
are using Multi-Site and the EBOM is at the remote site, however, this mechanism does not work as
Teamcenter must be able to check out the top level to generate the ID. A similar problem arises if you
want to assign from an EBOM that exists on a remote site to a local process.

To enable a remote site to use the EBOM-MBOM mechanism in these situations, you can generate in-
context IDs on the EBOM that are available when you paste parts to the MBOM. Use the bom_expand
utility to generate these IDs on the EBOM. For the EBOM shown in the figure, enter this command:

bom_expand -u=user-id -p=password -g=group -item=000035 -create_absocc_ids

Generate these IDs on a regular basis, for example, nightly, so that they are up-to-date when users
assign parts from the EBOM to MBOM.

Caution:
Attaching an in-context ID to a line in a structure creates several new objects in the database. If
you work with large amounts of data, this may have a detrimental affect on performance or
scalability. You should only pregenerate these IDs if you use EBOM and MBOM in a Multi-Site
environment.

EBOM to MBOM effectivity options

When end users are assigning BOM lines from an EBOM to a linked MBOM, you can set how the unit-
based effectivity of the source EBOM is handled in the target MBOM after the assignments are complete.
This option helps to avoid errors resulting from user attempts to manually enter the occurrence
effectivities themselves.

The MEEffectivityAssignmentMode preference defines the assignment behavior from an engineering

BOM (EBOM) to a manufacturing BOM (MBOM) for the BOM line property bl_occ_effectivity. The
default preference value of 0 ensures that when an EBOM line is assigned to the MBOM, the assigned
line inherits only the occurrence effectivity defined on the EBOM line, if such effectivity exists.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-19

Example:
Assigning EBOM line 000155/A;1-c7 to the linked MBOM inherits its effectivity from that line, not
from any line with a different effectivity higher in the structure.

Set the value of MEEffectivityAssignmentMode to 1 to make an assigned line with no effectivity

inherit the effectivity of its parent. You must also add the bl_occ_effectivity value to the
MEAlignedPropertiesList preference and ensure that no preference beginning with the text
MEAlignedPropertiesToExclude... has the value bl_occ_effectivity.

Example:
Assigning EBOM line 000156/A;1-c8 to a linked MBOM results in the assigned line inheriting its
effectivity from its parent line because it has no effectivity. If you assign EBOM line 000156/A;1-c7
to the MBOM, it retains its own effectivity of 11-25.

12-20 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Net effectivity calculates the intersection of effectivities set on the path from the EBOM line to be
assigned up the parent chain. Starting from the selected EBOM line, and including the EBOM line itself,
net effectivity traverses up the parent chain until it finds the first parent with an explicitly defined
occurrence effectivity. The occurrence effectivity defined on that parent becomes the MBOM line’s net
effectivity. If an effectivity is defined in the BOM window’s revision rule, the computation intersects the
parent’s occurrence effectivity with that defined in the revision rule. The result of the intersection is the
final net effectivity.

To apply calculated net effectivity behavior, set the value of MEEffectivityAssignmentMode to 2 and
add the value bl_occ_effectivity to the MEAlignedPropertiesList preference. You must also ensure that
no preference beginning with the text MEAlignedPropertiesToExclude... has the value
bl_occ_effectivity, and turn on net effectivity calculations using the Business Modeler IDE.

Example:
The top line of the EBOM shown is associated with a multi-unit configured effectivity group with
values of 1–10 (not visible). Line 000156/A;1-c8 has no effectivity, but its parent, 000154/A;1-
Deform has a value of 1–20. Net effectivity calculates the available range shared by the multi-unit
configured effectivity group value (1–10) and the 000154/A;1-Deform value (1–20), which is 1–
10.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-21

12-22 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Delegating, overriding, or copying line properties from MBOM to

BOP
End users can override some delegated manufacturing bill of materials (MBOM) line properties in a bill
of process (BOP). Delegated properties reference the MBOM and appear in the BOP on assigned
(consumed) lines if the MBOM is loaded. To keep the BOP synchronous with the engineering bill of
materials (EBOM), administrators can mark a subset of these properties so that MBOM values are
delegatable using the MEDelegatedOccurrenceProperties preference.

By default, this preference delegates the following properties: bl_occ_effectivity (occurrence

effectivity), bl_quantity (quantity), bl_plmxml_abs_xform (absolute transformation matrix),
bl_occ_name (occurrence name), and bl_all_notes (all note types). If a property that was copied over in
previous versions is not defined in the MEDelegatedOccurrenceProperties preference, that property is
copied over.

Note:
• End users can edit the relative transform matrix in the BOP to align the absolute transformation
matrix.

• By default, quantity is copied to the BOP. If end users delete a quantity value in the BOP, the
quantity value is delegated from the MBOM.

Additional properties that can be delegated include bl_formula (variant formula), bl_abs_occ_all_ids
(ID in context, all levels), and bl_variant_condition (variant condition).

If the MEDelegatedOccurrenceProperties preference is absent, no properties are delegated. If your

organization prefers to copy rather than delegate line properties from the MBOM to the BOP, the
property names should be removed from the MEDelegatedOccurrenceProperties preference and
added to the MEAssignProperties preference. Properties in MEDelegatedOccurrenceProperties take
precedence over properties in MEAssignProperties.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 12-23

12-24 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
13. Administering CAD BOM and part BOM
alignments
Part BOM requirements
To create a part BOM from a CAD BOM:

• The MEDesignToBom_Enabled preference must be set to true (default = false).

• Part structures that are created in a part BOM using heavy alignment have parts with BOM view
revisions (BVRs) that are not actually assemblies. Change any existing customizations to treat parts
with BVRs as leaf lines if they are to be marked as end items.

• The CAD BOM design items and structures must either be created in a CAD system or empty design
items created by a manufacturing engineer as a work order for the designer.

• The CAD BOM must consist of design object types.

• The part BOM must consist of part object types.

• In the part BOM, add a precise clause to the top of the revision rules.

Example:
The group feature can be used to create the following clause: Has Item Type (Design)
{Precise}.

To calculate rolled-up variant conditions from the CAD BOM and add the logically equivalent variant
condition to the aligned part line, add the bl_condition_tag property to the
MEDesignToBomAlignmentProperties preference.

To avoid errors during heavy alignments, if you are using the TCAllowedChildTypes_<Part> preference,
you must modify it to allow design items. Similarly, if you use the TCAllowedParentTypes_<Design>
preference, modify it to allow part Items.

Set up CAD BOM smart search criteria

While the system defines some search criteria to locate unlinked or broken alignments between a part
BOM and CAD BOM, you can set the MEDesignToBomFindDesignsSearchCriteriaProperties preference
to help end users search for CAD objects based on additional attribute criteria and then create heavy or
light alignments based on search results.

For broken links, the system looks for the following in order.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 13-1

1. Matching ID in context (IDIC).

2. Matching item ID.

3. Matching Absolute Transformation Matrix (ATM).

4. The MEDesignToBomFindDesignsSearchCriteriaProperties preference properties.

Example:
AIE_OCC_ID and AIEAIE_OCC_NAME.

If any of these do not match, the CAD object is excluded from the end user's search results. If the part
object was never linked to the CAD object, the system looks for the following in order.

1. The MEDesignToBomFindDesignsSearchCriteriaProperties preference settings.

2. A matching ATM value.

Note:
If no previous alignment exists and there is a change to the CAD part (for example, the ATM has
changed), the search may not locate the object.

CAD and part BOM action handlers

Two action handlers are provided to make CAD BOM (design) to part BOM alignment easier.

ME_update_part_alignment_on_design_change-AH

This action handler updates part revisions in a part BOM related to an input CAD BOM design revision.

• The target folder requires a new design revision.

• The reference folder can optionally contain a previous design revision. If a reference folder is not
provided, the handler tries to find a previously linked design revision.

• Action handler mandatory argument: -forceupdate

• Allowed values:

0 Error if part is not writeable.

1 Force update if part is not writeable.
2 Revise part and update if part is not writeable.

13-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

/**
@returns
<ul>
<li>#ITK_ok on success.
<li>#EPM_invalid_argument_value if 'forceupdate' argument is not
'0 or
1 or 2'.
<li>#EPM_wrong_number_of_arguments if more than one Design
Revision
is provided.
<li>#EPM_target_object_not_attached if an invalid Design
Revision is
provided.
<li>Possibly other errors
</ul>
*/
extern ME_API int
ME_update_part_alignment_on_design_change_action_handler (
EPM_action_message_t msg );

ME_update_part_bom_alignment_to_mature_design-AH

This action handler recursively aligns previously aligned part lines in a part BOM to a currently
configured design revision in a CAD BOM that matches maturity criterion. If the
MEDesignToBom_check_maturity preference value is false, the alignment considers the currently
configured design revision as mature. The target folder requires a collaboration context containing one
design scope line and one part scope line.

/**
Action handler to update part bom for mature designs in design bom.
@returns
<ul>
<li>#ITK_ok on success.
<li>#EPM_target_object_not_attached if an invalid Collaboration
Context is provided.
<li>Possibly other errors
</ul>
*/
extern ME_API int
ME_update_part_bom_alignment_to_mature_design_action_handler(
EPM_action_message_t msg );

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 13-3

13-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
14. Configuring in-context IDs (IDIC)
Understanding equivalence and in-context ID (IDIC)
Teamcenter has several features that depend on finding parts that are considered equivalent. This
equivalency is often dependent on the in-context ID (IDIC), also known as the absolute occurrence ID.
The in-context ID is a unique identifier, generally alphanumeric, that determines if two parts or
processes are equivalent.

You can view the in-context ID by displaying the ID in Context Top Level column. It is usually
automatically generated, and you should exercise caution in modifying its value.

The following features depend on the in-context ID:

• Reconciling and engineering bill of process (EBOM) with a manufacturing bill of process (MBOM)

• Finding products in processes that are not yet expanded

• Running an accountability check to verify line equivalence

• Assigning parts to a cloned process structure

• Comparing structures to intermediate data captures

An in-context ID is automatically generated in the following situations:

• When you assign a bill of materials (BOM) to a BOM or a bill of process (BOP) to a BOP

• When you assign a BOM to a BOP or enterprise BOP (EBOP) structure if the
MECopyIdInContextToAssignedLine preference is set to true

An in-context ID is not generated when you assign from an EBOP structure to an EBOP structure.

Caution:
If a line has an in-context ID and you cut it and paste the same line back into the structure,
Teamcenter creates a new occurrence without an in-context ID. Therefore, any of the above
comparisons based on the in-context ID no longer work.

Setting up the search for components in other structures

You can select one or more objects in the following areas of the user interface and search for them in a
different structure.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 14-1

• Lines in a view

• Consumed parts in a process

• An object in the Navigation pane (Favorites, History, Open Items)

• Objects in the Home folder

• Objects in the My Worklist folder

• Items attached to a Teamcenter mail

• Lines in the Summary view

• Objects in the Graphics view

Whether you need to expand a target structure before choosing the Find in All Visible Views menu
command depends on the settings of the following two preferences:

MECopyIdInContextToAssignedLine
MECopyIdInContextLowerLevels

Note:
Whether you need to expand a structure before a found component can be highlighted within it
depends on the value of the MEExpandToSelection preference. If this preference is set to false,
you must manually expand the target structure to highlight lines found within that structure.

Understanding ID in context and assigned products

When assigning a product to a process or copying processes or operations from one process structure to
another, Teamcenter can assign the same ID in context (IDIC) to the structure lines in the source and
target structure. Doing so provides a method for Teamcenter to find the assigned objects in the other
structure, for instance, when using the Find in All Visible Views menu command or running an
accountability check.

This mechanism is controlled by two preferences:

• MECopyIdInContextToAssignedLine
If set to True, Teamcenter copies any existing in-context IDs to the target structure when assigning a
product to a process or copying a process or operation from one structure to another. If an in-context
ID does not exist, Teamcenter creates one on the source and copies it to the target object. Any
generated IDs are unique within the source and target structures.
If set to False, no in-context ID is copied.

• MECopyIdInContextLowerLevels

14-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

If set to True, Teamcenter copies any existing in-context IDs of consumed items under subprocesses
and suboperations to the target structure when copying a process or operation from one structure to
another. If an in-context ID does not exist, Teamcenter does not create one.
If set to False, no in-context ID gets copied for the consumed items under subprocesses and
suboperations, even if one is present.

Note:
The MECopyIdInContextLowerLevels preference is considered only if
MECopyIdInContextToAssignedLine is set to True.

In the following example, if you copy process P1.1 from Proc1 in the upper pane to Proc4 in the lower
pane:

• Teamcenter only generates an in-context ID for the process that is being copied. It never generates an
in-context ID for subprocesses, suboperations, or their consumed items, regardless of the settings for
these preferences.

• If MECopyIdInContextToAssignedLine = false and MECopyIdInContextLowerLevels = false,

Teamcenter does not copy any in-context ID.

Note:
For P1.1, the ID is not generated at the source if it is not present (in the following example, it is
already generated).

After copying, under the Proc4 process, note that there are no in-context IDs in the ID In Context
(Top Level) column.

• If MECopyIdInContextToAssignedLine = true and MECopyIdInContextLowerLevels = false, the in-

context ID for P1.1 and I1.1 only are copied. The existing in-context ID for I1.2 is not copied because
I1.2 is the consumed item of a lower level.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 14-3

Note:
For P1.1, the in-context ID is generated at the source if it is not present and then copied. For
I1.1, the ID is not generated if it is not present.

• If MECopyIdInContextToAssignedLine = true and MECopyIdInContextLowerLevels = true, the IDs

for P1.1, I1.1, and I1.2 are all copied.

Note:
For P1.1 the ID is generated at the source if it is not present and then copied. For I1.1 and I1.2,
if the ID is not present, it is not generated, but if it is present, it is copied.

14-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Configuring the generation of smart IDICs

Different solutions in Teamcenter are based on the in-context ID (IDIC). It is useful to generate an IDIC
on a structure to be certain that these IDs are available for subsequent actions, for example:

• You want to assign parts to a relevant process or operation where the parts in the BOM are changing
often resulting in a loss of occurrence information and you want to avoid having to assign the new
parts to the same process or operation manually.

• You want to clone an existing structure and automatically assign the same parts to the new cloned
structure.

• You want to compare an intermediate data capture to the structure from which it was made to see
what changes have occurred since you created the intermediate data capture.

• You want to compare an EBOM to an EBOM or a process to a process.

• When performing EBOM-MBOM maintenance, for example, by overwriting existing IDIC values in a
BOM to ensure consistency.

You can automate the generation of IDICs for BOM lines to be based on the concatenation of other
properties of the BOM line. The combination of these properties results in a unique string that
Teamcenter assigns as an IDIC.

Generate smart IDICs

• Define the properties that are combined to create the IDIC in the MEIdGenerationPropertySetting
preference.
These can be any single-valued BOM line property. If the property value is empty, Teamcenter uses
that empty value. Two typical properties that you may combine are Usage Address and Position
Designator. These are used when resolving logical assignments in enterprise bill of process
structures.

• Define tolerances for translation and rotation in the following preferences:

• ME_angular_tolerance
• ME_translation_tolerance

Note:
If you use a CAD integration with Catia or other CAD application and use a bill of materials
(BOM) to BOM or BOM to bill of equipment (BOE), updates sometimes cause small BOM CAD
tolerance variations so that parts in the model show as incorrectly changed during advanced
accountability checks. To reduce the number of outliers during such checks, increase the
ME_angular_tolerance and ME_translation_tolerance values.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 14-5

• Specify whether the MEIdGenerationPropertySetting preference is to be used to generate in-

context IDs during the assign action by setting the MEIdGenerationOnAssignEnabled preference to
true.

Caution:
You may notice performance issues when setting this preference.

Alternatively, you can:

• Run the me_stamp_ids utility to generate IDICs for an entire structure, based on a closure rule.

• Create a workflow process based on the ME-stamp-ids-AH action handler to automate the process
from the user interface.

When using the utility or action handler, you can specify whether Teamcenter allows duplicate IDICs in
the MEIdGenerationAllowDuplicates preference.

Configuring the IDIC mechanism when using shared assemblies

Some engineering bills of material (EBOMs) contain shared assemblies. The same assembly is used
multiple times in the EBOM but only one is configured in and assigned to the manufacturing BOM
(MBOM). If you set the MEIDGenerationInSharedAssembly preference to true, at the time of
assignment, Teamcenter searches the EBOM for all other visible (configured in by revision rule or any of
the Show Unconfigured... buttons) instances of the same assembly and stamps them with the same
IDIC.

Stamp missing IDIC strings

You can use the me_fix_idic utility to stamp ID in context (IDIC) strings from a stable manufacturing bill
of materials (MBOM) structure to an engineering bill of materials (EBOM) structure in which the IDIC
strings are somehow deleted. You can also use the utility to stamp IDICs from a product or plant
structure to a process structure.

Note:
• The command may take some time to complete its task.

• After the command completes you must restart Manufacturing Process Planner to see the
changes.

Warning:
IDIC values are not stamped if:

14-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• There are multiple empty IDICs in the EBOM or assigned lines in the process structure for a given
itemid and propertyset (that is, for the same itemid and the transform for multiple lines with
no IDIC).

• An IDIC on a target line exists but is different from the source IDIC, even though the itemid and
propertyset values match.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 14-7

14-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
15. Administering the import and export of
manufacturing structures
Configuring PLM XML export
It can take hours to export large structures using PLM XML export. You can improve the performance of
these jobs by setting the PLMXML_Pre_Expand_BOP_Rule_Name preference to the PreExpandProcess
closure rule. This feature works by pre-expanding the process structure by closure rule prior to PLM XML
traversal. The pre-expansion performs bulk loading of BOM lines, reducing the number of calls to the
Oracle server. The closure rule can be customized for maximum performance. The reduction in Oracle
calls reduces the load on the rest of the system that, in turn, speeds up concurrent jobs and increases
the capacity of the system to run more jobs simultaneously without sacrificing performance.

You can configure the PreExpandProcess closure rule to suit your needs.

Configuring custom primary objects for use with DIPA

When you create custom primary objects such as custom plant BOPs, processes, process areas, lines,
operations, and items, you must first make configuration changes using dynamic in-process assembly
(DIPA) preferences and closure rules to ensure that they import correctly.

• For custom root (top level) items, the preference MEDynamicIPARootItemTypes needs to include all
object types included in the assembly. This preference specifies the types of root items allowed in a
DIPA (default = Item).

• For custom processes, do one of the following:

• Change the preference MEDynamicIPATraversalClosureRule, to point to a new closure rule to be

used for traversal of the process structure to calculate the DIPA.

• Modify the DynamicIPAProcessOnlyWithPA preference to allow the custom process object types.

• To recursively generate the DIPA, modify the MEDynamicIPARecursiveCreateProcessTypes

preference to include any new custom Bill of Process (BOP) object types.

Configuring the import and export of dynamic in-process

assemblies
To ensure that scope flows are imported and exported along with dynamic in-process assemblies
(DIPAs), you must make some changes to the PLM XML transfer modes:

• To export DIPAs:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 15-1

• If you use the ConfiguredDataFilesExportDefault transfer mode, you must add the following
closure rule:

• If you use the ConfiguredDataExportDefault transfer mode, you do not need to make any
changes.

• To import DIPAs:

• If you use the incremental_import transfer mode, you do not need to make any changes.

• If you use any other transfer mode, including ConfiguredDataImportDefault, you must add the
following closure rule:

Configuring the export of end item assemblies

When using PLM XML export and the bomwriter utility, the export of lines under end item assemblies is
controlled by closure rules. If you want to suppress the export of the lines under an end item assembly,
apply conditional clauses to the closure rule clause that traverses from parent line to child lines. Ensure
that there are no other overlapping clauses that export the children. The conditional clause impacts the
objects that are exported. For example, in the following structure:

Top
Sub/A
EndItem/A
Child1/A
Child2/A
Child3/A

• If you want to export Top and Sub and suppress everything from the EndItem level (including
EndItem), use the following conditional clause:

SECONDARY.fnd0bl_is_mono_override!= "1"

• If you want to export Top, Sub, and EndItem and suppress everything below the EndItem level (but
not EndItem), use the following conditional clause:

PRIMARY.fnd0bl_is_mono_override!= "1"

15-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

The following is an example of a complete closure rule clause:

CLASS.BOMLine:CLASS.BOMLine:PROPERTY.bl_child_lines:PROCESS+
TRAVERSE:PRIMARY.fnd0bl_is_mono_override != "1"

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 15-3

15-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
16. Configuring briefcase exchange of
collaboration context
Key preferences for configuring briefcase exchange of
collaboration context
The following are important preferences for configuring a successful briefcase exchange of a
collaboration context:

• MEDefaultExportTransferOptionSet
Specifies the list values to be made available in the Export to Briefcase dialog box transfer option set
drop-down list. The values displayed are dependent on the values in the
MEDefaultExportTransferOptionSet preference and the values of the transfer mode in the
TC_gms_export_default_transfermode preference.
If TC_gms_export_default_transfermode has a value of TIEExportDefaultTM, there are two cases:

• Only the values that are specified in this preference and have a transfer mode value of
TIEExportDefaultTM are displayed in the Export to Briefcase dialog box transfer option set drop-
down list.

• If none of the transfer option set names specified in this preference have a transfer mode value of
TIEExportDefaultTM, all transfer option sets with a transfer mode value of TIEExportDefaultTM
are displayed in the Export to Briefcase dialog box transfer option set drop-down list.

Default values for the transfer option set drop-down list are:

• MfgConfiguredExportDefault — use this for briefcase configured export.

• MfgUnconfiguredExportDefault — use this for briefcase unconfigured export.

Note:
The first value specified in this preference defaults to the selected transfer option set in the
Export to Briefcase dialog box.

• MECCBriefcaseExportWithMultipleVariantRules
Enables the briefcase export of a collaboration context containing a product structure with multiple
variant rules. The default value is false.

• MERuleForBriefcaseExport
Defines the rule to govern creation of an appearance path node (APN) for the BOM lines during
briefcase export of a collaboration context. This helps the recipient of exported data perform certain
operations, such as the consumption of product to bills of process (BOPs) where if a particular object

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 16-1

does not have ownership, Teamcenter does not allow it to create an APN there. Therefore, in such
cases, it can use the created APN during export using this preference.
The default values for this preference are:

• Type:Item; ClosureRule:; Lines:AllLines;

• Type:Workarea; ClosureRule:; Lines:AllLines;

• Type:Mfg0MEPlantBOP; ClosureRule:; Lines:AllLines;

• MEAutomaticOwnershipTransferClosureRules
Specifies the closure rule to be used in recursive ownership transfer of export to briefcase
functionality for collaboration context objects. The default value is MfgDefaultOTCR.

Configuring recursive ownership transfer

The closure rule for defining recursive ownership transfer behavior can be specified in the
MEAutomaticOwnershipTransferClosureRules preference. By default, it is governed by a closure rule
named MfgDefaultOTCR. You can either modify it or create a new one.

The closure rule governing recursive ownership transfer should be based on BOM line to BOM line
traversal. Do not use any persistent object for defining traversal for recursive ownership transfer. For
example, the clause shown allows traversal from the parent BOM line to child BOM line when the parent
is of type MEProcessRevision and the child is either MEProcessRevision, MEOPRevision, or
MEWorkAreaRevision.

16-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

In the example, if a parent line of type MEProcessRevision is marked for ownership transfer, any child
line with types MEProcessRevision, MEOPRevision, or MEWorkAreaRevision are considered for
ownership transfer as well when the recursive ownership check box is selected while exporting the
collaboration context.

Configuring automatic APN creation during export

This functionality is based on the MERuleForBriefcaseExport preference. By default, APNs are created
for all structures present in a collaboration context being exported, but it can be configured to create
APNs as per requirement.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 16-3

16-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
17. Administering GD&T symbols
Displaying GD&T symbols and rich text in forms
You can configure any form to contain geometric dimensioning and tolerance symbols or rich text in
forms. It is possible to include geometric dimensioning and tolerance symbols in any box of a form but,
in practice, you would restrict them to fields intended for engineering data. For example, a box titled
Work Instruction is be a good candidate for geometric dimensioning and tolerance symbols, while a
box titled Quantity is not. To define fields that may contain geometric dimensioning and tolerance
symbols, you add their names to the GDT_properties preference. Once a box is added to this
preference, a user can add geometric dimensioning and tolerance symbols to the box in any instance of
the form.

You can activate geometric dimensioning and tolerance symbols for any type of form, including master
forms for a Teamcenter object. You can apply normal Access Manager rules to any form that contains
geometric dimensioning and tolerance symbols.

Users may only edit or add geometric dimensioning and tolerance symbols or rich text in a box after
clicking the edit button next to the relevant box. They may then enter symbols, control characters or
font formatting from the buttons provided or the keyboard. When editing or additions are complete, the
user saves changes and leaves edit mode. This feature is available in any application that allows viewing
of forms, including Manufacturing Process Planner, Part Planner, and Multi-Structure Manager. Detailed
usage information is given in the guides for the applications that support this feature.

You can print and view reports that are generated from forms that contain geometric dimensioning and
tolerance symbols or rich text. You can generate forms in two formats:

• HTML
Teamcenter generates a PLM XML file from the process structure, which is parsed, interpreted with
XSL style sheets, and converted to HTML files.

• PDF
Teamcenter generates a PLM XML file from the process structure, which is parsed, interpreted with
XSL style sheets, and converted to Formatting Object (FO) files. The information must then be
converted to PDF format by a third-party formatting tool.

Configure GD&T symbols and rich text in forms

Activate GD&T symbols and rich text in forms by implementing XML style sheets.

Note:
This feature is only supported on Microsoft Windows systems.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 17-1

Ensure you have a supported browser installed on your workstation if you want to view or print
HTML reports of information containing GD&T symbols.

1. Prepare the names of GD&T and rich text properties as follows:

a. In My Teamcenter, choose Edit→Option-→Search and find the GDT_properties preference.

If the preference does not exist, create it at the SITE level or above.

b. For this preference, enter the names of the GD&T and rich text form fields you want
Teamcenter to recognize in the Values box, for example, work_instruction and tolerance.

c. Similarly, create a new preference at the SITE level or above called GDT_formtypes, and enter
a list of form type names as the value of this preference. Teamcenter recognizes these form
types and, if a form of one of these types has a GDT box (that is, the name of the box is
defined in the GDT_properties preference), it renders this field as a GD&T/rich text box.

You have now defined names of GD&T/rich text attributes (fields) and form types. By default,
Teamcenter renders GD&T and rich text fields as specified by the GDT_properties and
GDT_formtypes preference entries. You can also use the XML style sheet mechanism to override
these settings, as described in step 4.

2. Create the form types that can display geometric dimensioning and tolerance symbols or rich text,
as follows:

a. Start the Business Modeler IDE and create new classes that have attributes listed in the
previous step under POM_object. For example, you might create a new class called
DemoGdtForm. Define the attributes for GD&T and rich text as String type with the
maximum length possible.

b. In the Business Modeler IDE, create new form types that use the class you created as the
underlying POM class. Similarly, you can also create item master forms or item revision master
forms to support GD&T and rich text in those master forms.

3. Copy the gdtex.ttf font file from the rich client installation directory to the FONTS directory of your
Microsoft Windows system.

Note:
You must install this font file on every workstation where HTML are generated, viewed or
printed.

4. Define an XML style sheet for the form type that contains GD&T or rich text fields. Enter gdtpanel
as the rendering hint of the intended GD&T and rich text fields. If you do not give a rendering hint,
Teamcenter uses the default renderer (it checks if a box contains GD&T or rich text by looking at
the preference settings).

17-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

The following XML example shows a style sheet for a form. In this example, comments and
tolerance are rendered GD&T or rich text, while work_instruction is rendered as a text area. These
rendering hints override any conflicting preference settings.

<rendering>
<page title="General" titleKey="General" format="TwoColumn">
>firstcolumn>
<property name="Quantity" modifiable="false"/>
<property name="comments" renderingHint="gdtpanel" modifiable="true"/>
<separator/>
<property name="tolerance" renderingHint="gdtpanel" modifiable="false" />
</firstcolumn>
<secondcolumn>
<property name="work_instruction" renderingHint="textarea"
modifiable="false"/>
</secondcolumn>
</page>
<page title="Reservation" titleKey="Reservation">
</page>
<page title="Project" titleKey="Project">
</page>
<page title="All" titleKey="All">
</page>
</rendering>

5. Verify you can now display and edit geometric dimensioning and tolerance symbols or rich text on
the appropriate forms and can export the data into reports.

Note:
If Teamcenter indicates it cannot find the corojdk11.dll library, locate this file on the
Teamcenter installation CD, and copy it into your system path.
If the display of GD&T and rich text becomes unstable when you type quickly, increase the
value of the EDITOR_UPDATE_LATENCY variable in the com\teamcenter\rac\form\gdt
\gdt.properties file from the default value of 50 and restart Teamcenter. This instability
occurs on slower machines.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 17-3

17-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
18. Setting up rich client reports
Creating reports
You can create reports in the rich client and attach them to appropriate nodes in your process structures.

Troubleshooting reports in the rich client

If the embedded viewer does not work correctly, an Applet CMEReportJTViewerApplet not
initiated error message may be displayed in the browser status line. If so, open the Java console in
the system tray and check for Java exception codes that may indicate the cause of the problem, as
follows:

• NoClassDefFoundError
Java cannot access the embedded viewer JAR files. This error is identified by an error message similar
to the following:

java.lang.NoClassDefFoundError:
com/ugs/plmvis/components/<AnyClassName>

Possible solutions:

• Check the Java console and verify the correct classpath is set, as described previously. Ensure the
SingleEmbeddedViewer.jar file is included in the classpath.
To view the classpath, open the Java console and type s to dump all system properties. Note the
displayed value of the javaplugin.vm.options property and check that it contains the classpath
string you entered when you configured the Java console.

• If the classpath is not correct, there may be more than one Java control panel; you may not have
modified the correct one. Choose Start→Settings→Control Panel and select the button that
matches the version number in the Java console window. Modify the classpath for this Java control
panel.

• Verify there are no typographical errors or unnecessary spaces in the classpath definition. For
example, ensure there is an = character between -classpath and the path name. Also, if you have
multiple classpath entries, ensure they are separated by ; characters.

• If none of the solutions work, copy the SingleEmeddedViewer.jar file manually from PV _Base_Dir
\Program to JRE_HOME\lib\ext folder. Close all Internet Explorer browser instances, restart the
browser and try again.

• NoClassDefFoundError: com/eai/visweb/components/...
You are trying to run reports from a previous version of Teamcenter. You should convert your reports
to use the current embedded viewer.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 18-1

• Could not load library jawt.dll

Java does not have permission to execute the jawt.dll file. Verify that you have updated the Java
security policy file correctly.

• VerifyError
The JRE version is incompatible with the HTML page. This error is identified by an error message
similar to the following:

java.lang.VerifyError: (class:CMEReportJTViewerApplet,
method: destroy signature: ()V)
Incompatible object argument for function call
at java.lang.Class.getDeclaredConstructors0(Native Method)

Possible solutions:

• Ensure you have installed the supported JRE version, as specified in the installation guide for your
operating system, and update it if necessary.

• Verify you have installed the correct version of the CMEReportJTViewer.jar file and update it if
necessary.

• Viewer window has no image

The viewer window shows a green background and the icons are visible, but there is no image in the
window.
To resolve this problem, try right-clicking in the JT window and choosing All On or Fit All from the
menu.

• EXCEPTION_ACCESS_VIOLATION
The version of the embedded viewer you have installed is not compatible with the
CMEReportJTViewer.jar file in the reports directory. This error is identified by an error message
similar to the following:

An unexpected exception has been detected

Unexpected Signal : EXCEPTION_ACCESS_VIOLATION
(0xc0000005) occurred at PC=0x6FD24D6
Function=Java_com_teamcenter_visweb_components_PMI3D_nativeHideEntity
+0x1D9
Library=C:\WINDOWS\system32\VisWeb.dll
Current Java thread:
at
com.teamcenter.visweb.components.PrimaryViewer.nativeDestroyViewerDone
(Native Method)
at
com.teamcenter.visweb.components.Viewer3D.shutdown(Viewer3D.java:718)
- locked <0x108c3938> (a java.lang.Object)
at
com.teamcenter.visweb.components.Module.removeNotify(Module.java:285)

18-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Possible solutions:

• Ensure you have the correct version of the embedded viewer. You must also update the PATH
environment variable and modify the classpath for the new version.

• Ensure you have the latest version of the CMEReportJTViewer.jar file in the reports directory.

• java.security.AccessControlException
If you see a blank HTML page with the following error in the Java console window, the Java policy file
is not edited correctly. Check the file and edit.

java.security.AccessControlException: access denied

(java.lang.RuntimePermission
getenv.JRE_HOME)
at java.security.AccessControlContext.checkPermission(Unknown
Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.System.getenv(Unknown Source)
at
com.ugs.plmvis.components.VisView.loadLibraries(VisView.java:2665)
at com.ugs.plmvis.components.VisView.init(VisView.java:2580)
at com.ugs.plmvis.components.VisView.<init>(VisView.java:241)
at com.ugs.plmvis.components.VisView.getInstance(VisView.java:205)

• To help protect your security, IE has restricted… message

If you see a To help protect your security, Internet Explorer has restricted this file from showing
active content that could access your computer. Click here for options… message in a yellow box
instead of the viewer, you have not allowed Internet Explorer to run active content. Repeat the
browser configuration procedure.

• Java Applet Support Required... message

If you see a Java Applet Support Required (If you are seeing this message, you need to turn on
applet support in your browser) message in a box instead of the viewer, you have not configured
applet tag support. Repeat the browser configuration procedure.

• Nothing is displayed in Firefox

If only a single box is displayed in Firefox, you have not enabled Java. Choose Tools→Options in
Firefox, click the Content button, and ensure the Enable Java check box is selected.

Configure reports in the rich client

If you use the Report Generator application to create reports and view JT files, Teamcenter runs a Java
applet that allows you to manipulate the view (rotate, pan, and zoom), gather measurement data, and
mark up the image. For correct operation of this functionality, you must configure your Web browser
and related settings, as follows:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 18-3

Note:
The following instructions assume you are configuring a Microsoft Windows system. Similar
configuration steps are necessary if you are using another operating system.
Some of the steps may vary depending on which operating system, browser, or JRE version you
use.

• If you are using the Microsoft Internet Explorer browser, modify the Internet properties, as follows:

1. In Windows, choose Start→Control_Panel→Internet Options

Windows displays the Internet Properties dialog box.

2. Click the Advanced tab.

3. Select the Allow active content to run in files on My Computer check box in the Security
group of entries and the Java console enabled check box in the Microsoft VM group of entries.

4. Click OK or Apply, and then close and reopen the browser to complete any changes.

Note:
If you are using the Firefox browser, this procedure is not required. However, if you encounter
problems viewing reports with Firefox, choose Tools→Options and verify the Enable Java
check box on the Content pane is selected.

• Install the embedded viewer and run its setup program, if you did not already do so when you ran
Teamcenter Environment Manager (TEM). During installation, avoid spaces in installation directory
names, as these may cause incorrect operation in certain circumstances.

• Ensure that the JRE version you have installed is at least version 1.6.0_20 or later.

• Click the Advanced tab of the Java control panel and ensure the Place Java icon in system tray
check box in the Miscellaneous group is selected. This ensures the Java console is always present in
the Windows system tray, allowing easy access to it for troubleshooting.
When troubleshooting, you can also select the Enable tracing and Enable logging check boxes in the
Debugging group. This displays more detailed information in the Java console window that may help
you debug problems.
Optionally, you can click the Show Console button in the Java Console group to open the Java
console for debugging purposes whenever the applet is active.

• Click the Browser tab and ensure that the check box for your browser is selected. If you have more
than one browser on your system, check each applicable check box.
If you changed the Java run-time parameters in the previous step, clear your current browser, click
Apply, then recheck the current browser and click Apply again. This loads the new environment
variable setting into the browser.

18-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• Modify the Java security settings to allow the browser to open the DLL files for the embedded viewer
and JT files in one of the following ways:

• Edit the java.policy file in your JRE_HOME\lib\security directory with a text editor, not a word
processor. Add the following entry to this file:

grant {
permission java.security.AllPermission;
};

• Use the policytool.exe application in your JRE_HOME\bin directory to grant the same permissions.
See the Sun documentation for information on using this tool.

If you have more than one version of the JRE on your system, or if you also have the Java Software
Development Kit (SDK) installed, there may be more than one copy of the java.policy file. If possible,
identify the version that is used by the browser. Identify the policy deployment directory by opening
the Java console, typing s to dump all system properties, and noting the displayed value of the
application.home property. Place your modified java.policy file in the directory indicated by this
property; if the directory does not exist, create it. Alternatively, if you are using Internet Explorer, you
can modify the file pointed to by the deployment.system.security.policy value.

Note:
Close all browsers before testing changes.

View or print rich client reports with a Web browser

1. Select the process or operation on which you want a report and open the Report view.

2. Click the button next to the Type box and select a report from the list of available types.

3. Click the Generate Reports button to create the report. Optionally, you can click the Save button
to save the report you generated.

4. Open the Attachments view. The generated report is shown as an attachment to the process or
operation item revision. You can double-click the report to open and view it.

Creating reports in the rich client

Manufacturing Process Management provides a framework on which you can create reports that are
relevant to your manufacturing processes and the Report Generator application that produces the
predefined reports.

For example, you may want to create a report that details the usage of various machined components in
assembly operations. From the definition of the product structure, Teamcenter extracts the following
information:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 18-5

• The name or identification of each part consumed in the manufacturing process. Thumbnail pictures
can also be included if required.

• Detailed information about each part, such as the dimensions, quantity, and Make/Buy status.

• A graphical representation of the manufacturing structures and assemblies. Each part is linked to
others to show the hierarchy in the assembly structure.

A summary page may define the total number of components, welds, and the comparative number of
bought and manufactured parts.

18-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
19. Configuring the accountability check
Setting up the accountability check
Using the accountability check, you can compare two structures in various ways. You can, for example,
ensure all lines in the EBOM structure are assigned to the MBOM structure, or you can compare the
product structure and the process structure to ensure that all occurrences of product components and
features are used in the process structure as consumed items. You can also compare a set of properties
that you specify to see if they match. When running an accountability check, you can compare the entire
assembly or only a subassembly to the selected process.

When running the accountability check, it is helpful to have the selection between the Accountability
Check Results view and the structure view synchronized—selecting a line in the results view selects the
same line in the process view. You can control selection synchronization using the
MEExpandToSelection preference. Set it to True if you want a selection on the results pane to select
the equivalent line in the BOM. This can be set in the Options dialog box in the Manufacturing pane.

Publish accountability check settings

When you save an accountability check as an available setting, Teamcenter stores the setting in a
dataset. It also automatically creates a preference that references this dataset. The name of this
preference depends on the types of structures that you used as the scope of the accountability check for
which you saved the setting. For example, if you opened an engineering BOM and a manufacturing
BOM, selected accountability check options for these two structures, and saved them as an available
setting, the resulting setting is stored in the MEAccountabilityCheckSettings.BOM.BOM preference. If
you used a product BOP and a plant BOP to create the setting, the setting is saved in the
MEAccountabilityCheckSettings.PBOP.PlantBOP preference. An administrator can create a new
instance of each of these preferences and assign it to a person, role, or group. The setting is then
available to those members for use when running a simple accountability check.

You must be logged on as an administrative user to perform this task.

1. Search for the MEAccountabilityCheckSettings<structureType>.<structureType> preference that

holds the setting you want to publish.

2. Choose Edit→Options and click the Organization tab.

3. Select the user, role, or group for whom the setting should be available.

4. Create a new instance of the preference by clicking .

5. Save the new instance of the preference.

When that user, role, or group signs in, the setting is available for them when they want to run an
accountability check on structures of the same type.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 19-1

The mechanism used to manage these preferences is common to all Teamcenter preferences.

Configuring the inclusion rules

You can filter the source and target structures before you compare them to limit the number of
comparisons required in an accountability check, therefore limiting the scope of the search. The filter
mechanism is based on closure rules that traverse the structures and take only those objects specified in
the closure rules into consideration for the check.

You may need to create new or modify existing closure rules for your own business use case. The closure
rules you create for the accountability check are referred to as inclusion rules and are not available for
importing and exporting. You can create and modify closure rules in the PLM XML/TC XML Export Import
Administration application.

19-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Note:
Expanding a structure based on closure rules also plays a role in which objects are taken into
consideration in the accountability check. If you expand using an appropriate closure rule, you
may not have to set an inclusion rule when running an accountability check.

All the existing closure rules created for the accountability check begin with Accountability or AC. When
creating new closure rules, note the following:

• The scope of traversal is Export.

• The output schema format is TCXML.

• If you want a line in the structure to be considered in the accountability check, set the Action Type
entry to PROCESS.

If the Show Unconfigured view options are set to show the unconfigured structure and you want to
only consider the configured lines for the accountability check (using closure rules mode), adding the
following clause to the existing list of closure rule clauses causes the accountability check to skip the
unconfigured lines.

Primary Object CLASS

Class Type

Primary Object BOMLine

Secondary Object CLASS

Class Type

Secondary Object BOMLine

Relation Type PROPERTY

Related Property bl_child_lines

Or Object

Action Type SKIP

Conditional Clause SECONDARY.bl_is_occ_configured=="false"||SECONDARY.bl_variant_state==""

If you create your own inclusion rules for the accountability check, you must add them to the following
preferences to have them displayed in the Accountability Check dialog box.

• MEAccountabilityCheckSourceStructureExpansionFilterRules
List of closure rules that are displayed in the Accountability Check dialog box.

• MEAccountabilityCheckTargetStructureExpansionFilterRules
List of closure rules that are displayed in the Accountability Check dialog box.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 19-3

You can also set the maximum number of lines to be returned by the accountability check using the
preference MEAccountabilityCheckMaximumAllowedLines. If the actual number exceeds the
maximum, a printable report is generated and attached to the accountability check target structure.

Customize accountability check reports using a temporary XML file

When Teamcenter creates the accountability check report including report generation, it does the
following:

• Creates a temporary XML file.

• Applies the stylesheet to create the Excel report.

• Deletes the XML file on your local directory.

If you want to customize the report using the temporary XML file before Teamcenter deletes it, do the
following.

1. Log in to Teamcenter with administrative privileges.

2. Open the Report Builder application and in the Reports Home pane, expand the Teamcenter
Reports node.

3. From the Teamcenter Reports list, select Accountability Check Report.

4. In the right panel, click the Report Data tab.

5. From the Selected Stylesheets section, select the default stylesheet and click .

19-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

6. Click Modify.

7. Run an accountability check including report generation.

8. Find the XML file in the your-TMP-folder\user\2TierTransientVolume folder.

9. Use this XML file to help you customize the stylesheet and then give it a unique name (for example,
my_acc_chk_rpt_excel.xsl).

10. Click and in the Import Stylesheet dialog box, from the Dataset Type list, select MSExcel.

11. Browse to the custom stylesheet you want to use and click OK.

12. From the Defined Stylesheets list, select the custom stylesheet and click to add it to the
Selected Stylesheets list.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 19-5

13. Set the value of the preference AccountabilityCheckReportStylesheetName to the name of your
custom stylesheet.

14. Click Modify, log out of Teamcenter, and then log in again.

When you now generate an accountability Check Excel report, Teamcenter will use the customized
stylesheet. The above steps need to be executed every time you change the stylesheet.

Add or remove accountability check report stylesheets

To customize the accountability check report that you generate as an Excel file when executing the
accountability check command, you must first create a new custom stylesheet. Do the following to add
or remove stylesheets for use with your accountability check reports.

1. Log on to Teamcenter with administrative priveleges.

2. Open the Report Builder application and in the Reports Home pane, expand the Teamcenter
Reports node.

3. From the Teamcenter Reports list, select Accountability Check Report.

4. In the right panel, click the Report Data tab.

5. Click and in the Import Stylesheet dialog box, from the Dataset Type list, select MSExcel.

6. Browse to the custom stylesheet you want to use and click OK.

7. From the Defined Stylesheets list, select the custom stylesheet and click to add it to the
Selected Stylesheets list.

8. Set the value of the preference AccountabilityCheckReportStylesheetName to the name of your

custom stylesheet.

9. Click Modify, log out of Teamcenter, and then log in again.

When you now generate an accountability Check Excel report, Teamcenter will use the customized
stylesheet. The above steps need to be executed every time you change the stylesheet.

Note:
If you created a custom stylesheet prior to upgrading to Teamcenter 11.4 or greater, by default,
the Excel report uses a new stylesheet called acc_chk_rpt_excel.xsl. Your customized stylesheet
must have a different, unique name (for example, my_acc_chk_rpt_excel.xsl). When the value of
the preference MEAccountabilityCheckReportCombineLines is true (default), the generated xml

19-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

file will not support legacy stylesheets. To generate legacy data xml files, change the preference
value to false.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 19-7

Configure the accountability check to use net effectivity

1. Configure unit effectivity to be valid for multiple effectivities.

2. Set the MEAccountabilityCheckEnableNetEffectivity preference.

This controls whether the accountability check mechanism checks for net effectivity.

3. Implement a user exit and register a method for it in the Business Modeler IDE.

Display an icon to indicate revision mismatches on BOP lines

In some cases, bill of materials (BOM) items that are consumed in a bill of process (BOP) do not
immediately allow users to recognize revision mismatches. Set the value of the preference
MECompositionMismatchPropertyName to fnd0CompositionRevMismatch to display an icon in
BOPs to indicate line mismatches.

By default, the preference value is empty. The preference is at the site location but each user can create
his own copy and modify the value since the protection scope is set to user. The user must restart
Teamcenter after setting its value.

Customizing the net effectivity user exit

Teamcenter provides you with customized code to help you implement net effectivity. The method
returns the net effectivity that results when you intersect the effectivity defined on an occurrence (or if
there is none, the effectivity of its parent) with the effectivity configured in the revision rule.

You must configure this user exit in the Business Modeler IDE application. When doing so, note that the
extension point is Fnd0BOMLINE_ask_effectivity_by_parent and the method is
BMF_BOMLINE_compute_net_effectivity.

Accountability check batch mode

Running an accountability check in batch mode

Teamcenter offers you two separate methods for running an accountability check in batch mode.

• Run an accountability check in the rich client using the Accountability Check→Schedule
Accountability Check and Accountability Check→Schedule Structure Propagation commands.
Use this method if:

• You want an easy way to schedule an accountability check at a specific time.

19-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

• You do not have administrative privileges.

• Run an accountability check using a command line utility, acc_check_client.

Use this method if:

• You want to output to both Microsoft Excel and occurrence groups simultaneously.

• You want to output occurrence groups to both the source and target structures. For example, you
can get Missing in Source results that you cannot get with the rich client commands or with a
regular accountability check.

• You have administrative privileges.

Running an accountability check or propagation at a specified time

You can schedule an accountability check or structure propagation to run at a later date or time or at a
specific recurring time. This is helpful if you are comparing large structures where the action is time-
consuming or if you require comparison results on a regular basis. Teamcenter uses the Dispatcher
application to run the comparison and propagation at a time you specify.

To use this feature, your administrator must configure the asynchronous services.

The asynchronous services require the installation of Teamcenter Dispatcher.

Running an accountability check in batch mode using the acc_check_client

utility

Running an accountability check of the product can take several hours. You can use the
acc_check_client utility to run the accountability check if you:

• Want to output to both Microsoft Excel and occurrence groups simultaneously.

• Want to output occurrence groups to both the source and target structures. For example, you can get
Missing in Source results that you cannot get with the rich client commands or with a regular
accountability check.

• Have administrative privileges.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 19-9

You can run this utility offline, after hours, using the operating system scheduling to provide up-to-date
reports for Teamcenter users the following day. This utility logs onto Teamcenter, performs an
accountability check, stores the results in occurrence groups and/or an Excel report and logs off. You can
run this utility from a Teamcenter command window or from a batch file that is developed to perform a
specific check on two specific structures.

Running the acc_check_client utility creates the same output that is obtained by running the
accountability check in rich client. Teamcenter stores results in one or both of the following:

• Results are stored in occurrence groups that are created on the source and (optionally) the target
structures. These occurrence groups appear as tabs when the top item or revision is opened in
Manufacturing Process Planner. If structure contexts are used as input arguments, the occurrence
groups appear as tabs when the structure contexts are opened in Manufacturing Process Planner.

• Results are stored in an Excel report. The report appears in a dataset that is attached to the target
structure’s top line item revision. You can find the dataset by opening the structure, selecting the top
line, and viewing the Attachments tab. You can view the Excel content by opening the dataset.

Run the acc_check_client utility from a script

Using the acc_check_client utility, you can run checks on a nightly basis and use them to update
existing occurrence groups and/or excel reports. To run checks in a two-tier environment:

1. Create a script that simplifies the input of parameters. In this script:

a. Set the Teamcenter environment, including the TC_ROOT directory.

b. Send standard output to a log file.

c. For a two-tier environment: start the server on the specific port with ID.

d. Start the utility executable and specify that port and ID or a four-tier connection.

e. Test the script by running it.

2. For nightly runs, schedule a job to run the script so that the results are updated nightly.

Using dynamic equivalence to locate matching EBOM and MBOM

lines
In some cases, end users may want to locate matching BOM lines in a linked engineering bill of materials
(EBOM) and manufacturing bill of materials (MBOM) that have slightly different properties and therefore
are not reported as equivalent when they run an advanced accountability check. For example, the lines
may have different ID in context values, but the manufacturing engineer wants to find them to ensure
that they have the same material quantity, and later address the difference in the ID in context values.

19-10 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

Using the MEAccountabilityCheckDynamicIDICProperties preference, you can define a list of internal

BOM line properties to be used as dynamic equivalence criteria when searching for equivalent lines
between EBOM and MBOM. For example, to compare absolute transform values, you can add the line
bl_plmxml_abs_xform to the preference and the lines are reported as equivalent when you run an
advanced accountability check. In the Advanced Accountability Check dialog box, on the Equivalence
tab, end users can then select the Dynamic Equivalence check box to enable a dynamic equivalence
check.

Note:
Selecting the Dynamic Equivalence check box automatically selects the Multiple Match
checkbox in the Display Options group on the Reporting tab of the Advanced Accountability
Check dialog box. When Dynamic Equivalence is deselected, check boxes in the Display Options
group return to their previous selections.

If no values are defrined in MEAccountabilityCheckDynamicIDICProperties preference, then item ID is

the default attribute for comparison.

Modify accountability check closure rules to exclude dynamic in-

process assemblies
When running accountability checks between structures that contain dynamic in-process assemblies
(DIPAs), the default traversal rules used to determine the scope of the accountability check exclude the
DIPA structures from the check. If you run accountability checks using customized closure rules, you
must modify these to exclude the DIPA structures.

• Add a line in the transfer mode that skips the DIPA structures, for example:

CLASS.BOMLine:CLASS.AppGroupBOPLine:PROPERTY.bl_all_child_lines:SKIP:
SECONDARY.bl_line_object_class==”Mfg0MEDynamicIPA”

Set up the accountability check to compare to intermediate data

captures
You can create an intermediate data capture (IDC) of a structure that captures the current state of a
configured structure in a PLM XML file. If you then continue to work on the structure, you may want to
compare it at a later point to the IDC to see what changes have taken place. To do this, the original
structure must contain in-context IDs before you create the IDC.

• If you want to compare the entire structure, create the in-context IDs using the bom_expand utility.

• If you want to compare only partial structures, when writing the PLM XML transfer mode for IDC
creation, include a line in the transfer mode that creates in-context IDs on the desired lines in the
structure. For example:

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 19-11

"CLASS.BOMLine : CLASS.AbsOccGenerator : PROPERTY.bl_absocc_generator:

PROCESS:

Using the two-tier accountability check utility

Use the accountability_check utility to run the rough equivalent of an advanced accountability check
and generate Microsoft Excel and occurrence group reports in a two-tier Teamcenter environment. The
utility lets you check line equivalance between several types of structures, including EBOM/MBOM, CAD
BOM/design EBOM, MBOM/BOP, and product BOP/plant BOP.

Similar to the acc_check_client utility that is intended for the service-oriented architecture (SOA) client,
the accountability_check utility allows you to run accountability checks on sandbox machines without
having to set up a four-tier infrastructure that requires you to maintain processes such as pool managers
on each machine. This capability lets you run many accountability checks simultaneously and to manage
the loads yourself. The utility also outputs occurrence groups to both the source and target structures,
while the rich client advanced accountability check can only output occurrence groups to the source.

19-12 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
A. Glossary
A
absolute occurrence
Relationship between a parent assembly and an item one or more levels down in the structure. The
parent assembly is the context in which the absolute occurrence exists. When you select the context
assembly and view the structure, you can define data on the absolute occurrence that overrides the data
stored on the parent. Compare to occurrence.

activity (manufacturing)
Individual action to be performed within an operation. Each activity is associated with a start time and
duration. The total time for the operation is based on the cumulative duration of all activities within the
operation.
Activities can be sequenced using time data and predecessor activities.

appearances
Cache of configured BOM lines in the context of a specific top-line item. Appearances are created to
allow quick searches of the entire structure.

appearance set
Collection of objects that define the use of every part ever included in an end item. The appearance set
enables Teamcenter to rapidly search the product structure of a family of related configurations without
caching the entire product structure for each configuration. The appearance set is optional and typically
maintained for a few end items that represent large assemblies when fast searching is critical. The
system administrator defines the items requiring appearance sets.

Application Interface Viewer

Viewer data tab in applications that allows users to monitor and control PLM XML data exchanges
between Teamcenter and another application through a collaboration context.

assembly
Compound object that is assembled from other objects and may add additional information to their
interpretation.

• In the context of an assembly, other assemblies are called subassemblies, while noncompound
objects are called components.

• A single-level compound object that is distinct from a multilevel product structure or bill of materials,
which is a hierarchy of assemblies. Assembly data is stored in a BOM view revision.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 A-1

assembly classification
Resource assembly ID and name of the class where the assembly is classified. An assembly classification
is also the process of associating an assembly with a class and entering the attribute values that
characterize it within its class.

assembly view
View of the product data. See also BOM and manufacturing view.

attribute
Named storage variable that describes an object and is stored with the object. Users can search the
database for objects using object attributes.
In an object, an attribute is a name/value pair. In the database, an attribute is a field.

attribute propagation
Process of transferring attribute values from one object to another. In Resource Manager, attribute
values are propagated from a propagation start point up the assembly structure to the assembly object.
For example, on a cutting tool, the cutting material of the insert, the cutting diameter of the extension,
and the holder type of the machine adapter can all be propagated to the assembly level. This provides a
mechanism to make all attributes required for a cutting tool definition available at the tool assembly
level.

B
base product view
The as designed bill of materials of the product. Contrast with manufacturing bill of materials.

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.

A-2 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
C
class
Set of objects that share the same list of attributes but distinguishable by the value of the attributes for
specific objects.

class folder
Representation of aggregation of objects. In the Classification and Classification Search dialog class
hierarchies, classes are displayed with class folder icons because they represent an aggregation of
objects.

class hierarchy
Structure defining subclasses that inherit the attributes of their superclasses, also called their parents or
ancestors.

classification
Process of categorizing objects according to similarity in characteristics. While the objects in one class
share the same characteristics, the values of these characteristics may differ. For example, drill bits all
share the length and diameter characteristics, but drill bit objects differ in length and diameter.

classification hierarchy
Structure used to categorize a company's data by common attributes.

classification instance
Lowest-level component of the classification hierarchy. Also referred to as an ICO (internal classification
object).

client tier
Teamcenter architectural tier that comprises the Teamcenter clients, Teamcenter integrations with third-
party applications, and the third-party applications associated with the integrations.

clone and reference

Copy action rule when using templates to create process structures. The object is copied to the database
and a reference is made to the database clone. The reference is the same type as the one in the
template.

cloning rules
In a collaboration context, a set of rules that defines how structures are created when copying other
structures of the same type. A cloning rule can also be applied when creating a structure from a
template.

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

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 A-3

in Part Planner. You can also use a collaboration context to collect data to share with a third-party
application. See also structure context.

component
• Objects used to build up an assembly or subassembly.

• Part in a product structure defined in Teamcenter. A component is the lowest level part in the product
structure: it cannot be broken down into subparts.

composition
Special kind of structure context that allows components to be added from one or more structure
contexts, each of which may contain a different product structure. Compositions are used for design
studies and manufacturing processes that contain data from both product and plant structures.

configuration context (Multi-Structure Manager)

In Multi-Structure Manager, a revision rule, variant rule, and closure rule applied to a collaboration
context. See also collaboration context.

consumed item
Item that is required during a manufacturing process or operation and must be ordered regularly to
meet the production quota. A consumed item can include parts or components from the product
structure in addition to materials such as oil, grease, and gloves.

copy action rule

Predefined rule that defines how a template is used to generate processes. Actions commonly
performed include ignore, reference, and clone.

Copy by Reference
Copy action rule when using templates to create process structures. The same database object is
referenced in the clone. The relation type is the same as in the template.

D
delivery unit
Subassembly that is manufactured separately and delivered to the assembly plant as a consumed part.
One of the operations in the assembly process uses the delivery unit as a consumed part. The
components of a delivery unit are not consumed in any of the operations.

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.

A-4 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
device
Complex assembly that is represented as a simple component. A device is designed to work as part of a
machine tool or robot.

E
effectivity rule
Rule used to set effective dates on released products and processes with a released status.

end item
Top-level node of an assembly that can represent a product or a factory structure.

enterprise tier
Teamcenter architectural tier that comprises a configurable pool of Teamcenter C++ server processes
and a server manager. Larger sites can distribute the pool of server processes across multiple hosts.
Smaller sites can run the pool of servers on the same host as the web tier.

equipment
Description of the equipment used to perform manufacturing operations.

F
feature
Physical or geometric object associated with a product, component, or part. Alternatively, a logical
attribute of a product, component, or part. Examples: a weld point, a signal, or a geometric pattern. A
feature may be represented by a generic design element (GDE) in a BOM. See also generic design
element.

folder
Graphical representation of an aggregation of objects, such as a group, class, or subclass. For easy
distinction in the class hierarchy, each of these aggregations has a different type of folder icon
associated with it: a group folder icon, a class folder icon, or a subclass folder icon.

four-tier architecture
Teamcenter architecture that includes four tiers: resource tier, client tier, web tier, and enterprise tier.
Contrast with two-tier architecture.

four-tier deployment
Deployment of the Teamcenter four-tier architecture. The web tier, enterprise tier, resource tier, and
client tier can each be hosted on the same or separate computers.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 A-5

G
GDE
See generic design element.

generic design element

BOM item that cannot have different revisions. See also feature.

group
Type of class that does not have a list of attributes associated with it; highest level in the classification
hierarchy.

group folder
In the classification hierarchy, group folders represent a group of related classes.

H
hierarchy
Structure in which each node can have only one parent but possibly multiple siblings and children.

I
ICM root folder
Root folder in the classification hierarchy. There is one root per database.

Ignore
Copy action rule when using templates to create process structures. No action is taken to duplicate the
object in the cloned structure.

in-process model
Product resulting from application of a manufacturing operation.

input data
In-process model and other data generated from the previous steps in an operation.

instance
Single data object that is associated to a class. The instance can correspond to a line in the BOM.

A-6 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
M
manufacturing bill of materials
Defines how the product is manufactured, rather than how it is designed. Compare with design bill of
materials.

manufacturing process
Collection of manufacturing subprocesses, operations, and activities that make up a process plan.
Processes can have both sequential and parallel ordering. They are associated with a product and a work
area.

Manufacturing Process Planner

Teamcenter manufacturing process management application that enables a user to design a plan
detailing how to manufacture a product.

manufacturing view
Hierarchical structure of occurrence groups. The manufacturing view describes the components and
subassemblies used by the assembly operations.
The components of subassemblies in the manufacturing view represent references to lines in the
targeted product structure. These components can be consumed in operations if their parent assembly
is not consumed.
See also assembly view.

MBOM
See manufacturing bill of materials.

method
Description of how equipment is used to perform work on a feature. Each method can be used by
several manufacturing operations to perform work on different features.

Multi-Structure Manager
Teamcenter application that enables users to view and manipulate data in a specific context.

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.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 A-7

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.

output data
Data generated as a result of applying instructions to input data. Output data can be the resulting in-
process model and any instructions for the next step.

P
Part Planner
Teamcenter manufacturing process management application that enables a user to design a plan
detailing how to manufacture a part.

plant
Manufacturing facility described by a hierarchical structure of work areas.

plant structure
Hierarchy of the physical layout of a work area. Different levels in the hierarchy represent the plant, a
work cell, and individual workstations. Compare with product structure and process structure.

process operation
Step in the manufacturing process executed at a specific work area. It is the lowest revisable element in
the manufacturing process structure.

process revision
Modified version of a process. A process revision can be used to handle different configurations of
assemblies, alternative methods for building the target item, or changes to methods.

process structure
Hierarchy of manufacturing processes and operations with a sequenced relationship that together
describe how a related product is manufactured. Compare with product structure.

product
Item or assembly (hierarchy of components and subassemblies) to be manufactured.

product appearance
Persistent representation of a product line. All appearances of a product are collected into a set that is
associated with one revision rule. This allows one set of appearances that can be configured by the
effectivity of the part they represent.

A-8 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
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.

propagation
Process of transferring characteristics of one object to another object.

propagation start point

Component within an assembly structure that is the starting location for propagation.

PSP
See propagation start point.

R
raw material
Initial in-process model before any manufacturing operations are performed.

relative occurrence
See occurrence.

Report Generator
Teamcenter manufacturing process management application that provides a format for producing
reports about information in Teamcenter manufacturing process management.

resource
Item used to perform an operation or define a process. Examples of resources include robots, tools, and
machines. Both standard equipment and custom tools can be identified as resources.

resource assembly
Set of resource components and/or subassemblies that are grouped to create an assembly to be used in
a process, such as a manufacturing process.

Resource Browser
Plug-in component that allows users to retrieve classification-related data, such as a hierarchy with
corresponding groups, classes, and classification objects from a Teamcenter database when working in
an external application.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 A-9

resource component
Object that is a component of a resource assembly or subassembly.

Resource Manager
Teamcenter manufacturing process management application that enables a user to store and retrieve
resource-related data such as tools, fixtures, machines, and process templates from a company-wide
accessible database.

resource structure
Structure in which resource assemblies are hierarchically built.

resource tier
Teamcenter architectural tier comprising the database server, database, file servers, and volumes.

root
Starting point of a hierarchy. Hierarchies are usually displayed as hanging trees with the root of the
structure at the top and the leaves at the bottom.

S
setup
In a manufacturing environment, configuration of the work area. The setup also identifies the parts
consumed and the resources used.

spare part
Small item that in Resource Manager is commonly entered as other components are. Examples include
nuts, bolts, washers, and screws.

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.

subassembly
Assembly that is built into the assembly structure of another assembly or intended for that use. In a
manufacturing view, either a delivery unit or a workpiece. See also delivery unit and workpiece.

A-10 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

© 2020 Siemens
subclass
In the Classification Search Dialog, subclass instances represent a subset of attributes corresponding to a
class. Subclasses inherit the attributes of their parent classes. Unlike classes, which inherit every
attribute of their parent classes and cannot be edited, users can define the inherited attributes assigned
to a subclass.

T
Teamcenter Environment Manager (TEM)
Tool with a wizard-style interface that installs Teamcenter servers and two-tier and four-tier rich clients.
TEM also performs maintenance operations, such as upgrading servers and installing patches.
Teamcenter installers launch TEM using the tem.bat command (on Windows systems) or the tem.sh
command (on Linux systems).

TEM
See Teamcenter Environment Manager (TEM).

top level
Object at the root of a product structure where a process plan is being developed. The top level can be
either an end product being manufactured or a subassembly used in the end product (for example, an
engine for a tractor where the tractor is the end product).

two-tier architecture
Teamcenter architecture that includes a resource tier and a client tier. The resource tier comprises the
database server and database. The client tier comprises the Teamcenter rich client, third-party
applications that integrate with the rich client, and a local server. This architecture supports only the
Teamcenter rich client. Contrast with four-tier architecture.

V
variant condition
• Rules applicable to one component in a product structure.

• Condition set on an occurrence to specify the features required to configure that occurrence (for
example, Load IF engine = 1200).

variant rule option

Description of product variations that are usually applied to higher level assemblies or the product itself.

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.

Administering Manufacturing Planning, Teamcenter 13.0 PLM00260 13.0 A-11

W
web tier
Teamcenter architectural tier that comprises a Java application running in a Java Platform, Enterprise
Edition (Java EE) application server. The web tier is responsible for communication between the client
tier and enterprise tier.

work area
Plant location performing an operation. The work area can represent the entire plant, the work line, an
individual work cell, or a station within the plant. Work areas are described by their location on the shop
floor and the process capabilities they provide. Users can generate a hierarchy of work areas that is
unique to their organizations.

work instruction (manufacturing)

Document that describes how an operation should be completed at a work area. There are two
categories of work instructions:

• Human readable instructions are primarily used to provide information to the operator about how to
perform the operation.

• Machine instructions are program files that include numerical code used to run numerically controlled
machines, such as robots and NC machines.

workpiece
Intermediate state of the product during the manufacturing process. In each step of the manufacturing
process, the workpiece is positioned in the work area and the work instructions are performed. The
resulting workpiece then flows to the next operation in the sequence, where the next operation is
performed.

A-12 PLM00260 13.0 Administering Manufacturing Planning, Teamcenter 13.0

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

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

About Siemens Digital Industries Software

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

Travel Agents in Mumbai
75% (12)
Travel Agents in Mumbai
7 pages
Teamcenter Gateway For Enterprise Applications - Connectivity Guide
No ratings yet
Teamcenter Gateway For Enterprise Applications - Connectivity Guide
85 pages
installingTcDc (2412)
No ratings yet
installingTcDc (2412)
310 pages
Design of Cassions
100% (1)
Design of Cassions
31 pages
Getting Started Visualization
No ratings yet
Getting Started Visualization
276 pages
Schedule Manager
No ratings yet
Schedule Manager
168 pages
Teamcenter Integrated Material Management
No ratings yet
Teamcenter Integrated Material Management
67 pages
Teamcenter Polarion Integration
No ratings yet
Teamcenter Polarion Integration
24 pages
Basic Teamcenter: Bill of Material Concept
No ratings yet
Basic Teamcenter: Bill of Material Concept
8 pages
Getting Started Manuf Process MGMT
No ratings yet
Getting Started Manuf Process MGMT
130 pages
Schedule Manager For Process Execution
No ratings yet
Schedule Manager For Process Execution
59 pages
Teamcenter Gateway For SAP-Configuration Guide
100% (2)
Teamcenter Gateway For SAP-Configuration Guide
218 pages
API 1104 Sample Questions
80% (5)
API 1104 Sample Questions
12 pages
Team Center Manufacturing User and Administrator Manual
No ratings yet
Team Center Manufacturing User and Administrator Manual
137 pages
Getting Started With Customization
No ratings yet
Getting Started With Customization
48 pages
Active Workspace Fundamentals
No ratings yet
Active Workspace Fundamentals
222 pages
Teamcenter Engineering Product Data Management Student Guide
100% (1)
Teamcenter Engineering Product Data Management Student Guide
620 pages
GettingStartedwith Teamcenter12
No ratings yet
GettingStartedwith Teamcenter12
30 pages
TCEng Data-Management Student Guide V9
No ratings yet
TCEng Data-Management Student Guide V9
564 pages
Service Scheduler PDF
No ratings yet
Service Scheduler PDF
210 pages
Change Manager
No ratings yet
Change Manager
328 pages
4HANA - SAP Preparation Guide
No ratings yet
4HANA - SAP Preparation Guide
39 pages
Tc14.0.0.0 ActiveWorkspace6.2.2 README
No ratings yet
Tc14.0.0.0 ActiveWorkspace6.2.2 README
5 pages
Workflow Designer Handlers
No ratings yet
Workflow Designer Handlers
736 pages
SEECAdmin Guide
No ratings yet
SEECAdmin Guide
174 pages
Server Win
No ratings yet
Server Win
388 pages
Team Center
100% (1)
Team Center
406 pages
Access Manager
No ratings yet
Access Manager
178 pages
FAQ Industry Professional On Teamcenter Training
No ratings yet
FAQ Industry Professional On Teamcenter Training
11 pages
PLM Case Study
No ratings yet
PLM Case Study
9 pages
Teamcenter View
No ratings yet
Teamcenter View
9 pages
Teamcenter: Simplifying PLM
No ratings yet
Teamcenter: Simplifying PLM
16 pages
Tc14.2.0.0 README
No ratings yet
Tc14.2.0.0 README
15 pages
What's New Teamcenter 2312
No ratings yet
What's New Teamcenter 2312
48 pages
Materials Management Solution Guide
No ratings yet
Materials Management Solution Guide
75 pages
Structure Discovery Admin
No ratings yet
Structure Discovery Admin
58 pages
Control Plan 1
No ratings yet
Control Plan 1
112 pages
Configuration and Extensibility
No ratings yet
Configuration and Extensibility
456 pages
MyTeamcenter Training Manual
No ratings yet
MyTeamcenter Training Manual
61 pages
Project and Program
No ratings yet
Project and Program
96 pages
Teamcenter 11.2 Windows Server Installation: Siemens Siemens Siemens
No ratings yet
Teamcenter 11.2 Windows Server Installation: Siemens Siemens Siemens
390 pages
Digital Transformation in Your Manufacturing Business
No ratings yet
Digital Transformation in Your Manufacturing Business
185 pages
Data Science For Modern Manufacturing
No ratings yet
Data Science For Modern Manufacturing
36 pages
Installing TC DC
No ratings yet
Installing TC DC
296 pages
TC12-My TC (My Help)
No ratings yet
TC12-My TC (My Help)
53 pages
Administrator and User Help
No ratings yet
Administrator and User Help
2,462 pages
2052 PLMEurope 24.10.17-17-30 BALASUNDARAM-KANTHI INTELIZIGN ENGINEERING SERV Active Workspace For External Data Aggregation and Search
No ratings yet
2052 PLMEurope 24.10.17-17-30 BALASUNDARAM-KANTHI INTELIZIGN ENGINEERING SERV Active Workspace For External Data Aggregation and Search
18 pages
Business Modeler Ide Guide
No ratings yet
Business Modeler Ide Guide
1,306 pages
Deploying Document Management
No ratings yet
Deploying Document Management
196 pages
T4S4-AW Add-On Installation Guide
No ratings yet
T4S4-AW Add-On Installation Guide
62 pages
Deployment
No ratings yet
Deployment
198 pages
Teamcenter PDF
No ratings yet
Teamcenter PDF
22 pages
Clearancedb Admin Guide
No ratings yet
Clearancedb Admin Guide
275 pages
Cantier Profile With MES - Industry 4.0 (Partners)
No ratings yet
Cantier Profile With MES - Industry 4.0 (Partners)
28 pages
Designs and Structure Management
No ratings yet
Designs and Structure Management
120 pages
Apriso QualityManagement
No ratings yet
Apriso QualityManagement
41 pages
Aerospace and Defense Install Config
No ratings yet
Aerospace and Defense Install Config
26 pages
Project Based Conditions On LOVs PDF
No ratings yet
Project Based Conditions On LOVs PDF
35 pages
Administering Manufacturing Planning
No ratings yet
Administering Manufacturing Planning
178 pages
Getting Start Team Center
No ratings yet
Getting Start Team Center
38 pages
Getting Started With Customization PDF
No ratings yet
Getting Started With Customization PDF
56 pages
Getting Started Teamcenter
No ratings yet
Getting Started Teamcenter
28 pages
Autodesk Fusion 360 PCB Black Book (V 2.0.18719)
From Everand
Autodesk Fusion 360 PCB Black Book (V 2.0.18719)
Gaurav Verma
No ratings yet
Method of Philosophizing
No ratings yet
Method of Philosophizing
26 pages
Commissioning Check List For HP Bypass System
No ratings yet
Commissioning Check List For HP Bypass System
8 pages
OOP QUiz 1
No ratings yet
OOP QUiz 1
2 pages
GROUP 4 Reason and Impartiality May 24 2021
No ratings yet
GROUP 4 Reason and Impartiality May 24 2021
39 pages
2.1.9 Surface Scratch Examination Metal-Clad Foil
No ratings yet
2.1.9 Surface Scratch Examination Metal-Clad Foil
1 page
GNSS Data Processing Laboratory Slides
No ratings yet
GNSS Data Processing Laboratory Slides
458 pages
Congestion Control Using NBP
No ratings yet
Congestion Control Using NBP
12 pages
Hmi - TP177a - tp177b - Op177b Instructions
No ratings yet
Hmi - TP177a - tp177b - Op177b Instructions
2 pages
Project in Math: Fourth Quarter
No ratings yet
Project in Math: Fourth Quarter
2 pages
Art Lesson Plan
No ratings yet
Art Lesson Plan
4 pages
Module1 Remedial Instruction
No ratings yet
Module1 Remedial Instruction
5 pages
Unit 6 Different Cultures Lesson C: Do You Think I Should Take Her Somewhere Special?
No ratings yet
Unit 6 Different Cultures Lesson C: Do You Think I Should Take Her Somewhere Special?
5 pages
Samuel B.T. Tende: Target Job
No ratings yet
Samuel B.T. Tende: Target Job
3 pages
09a1bs01 Mathematics 1
No ratings yet
09a1bs01 Mathematics 1
5 pages
Deep Learning - Cognex
No ratings yet
Deep Learning - Cognex
16 pages
Cross-Cultural Pragmatics
No ratings yet
Cross-Cultural Pragmatics
22 pages
Boeing 737 - b737 Flight Control (Ata 27)
88% (8)
Boeing 737 - b737 Flight Control (Ata 27)
45 pages
TRINA - B - Additional Installation User Manual - DE18M (II) - 2021B - EN - 20210304
No ratings yet
TRINA - B - Additional Installation User Manual - DE18M (II) - 2021B - EN - 20210304
16 pages
Acs 3073 Technology Entrepreneurship: Lecture'S Name: Sir Mahathir Bin Muhamad NO Group Members Matric No
No ratings yet
Acs 3073 Technology Entrepreneurship: Lecture'S Name: Sir Mahathir Bin Muhamad NO Group Members Matric No
4 pages
Boundary Conditions For Option
No ratings yet
Boundary Conditions For Option
6 pages
MonoFlex JSG
No ratings yet
MonoFlex JSG
32 pages
Maharashtra Public Service Commission: MPSC Essay and Language Paper
No ratings yet
Maharashtra Public Service Commission: MPSC Essay and Language Paper
14 pages
Chapter Three Generation of Impulse Voltages: /T (In Sec) Where
No ratings yet
Chapter Three Generation of Impulse Voltages: /T (In Sec) Where
24 pages
Kolmert 2000
No ratings yet
Kolmert 2000
6 pages
EE 8950 - Homework 3
No ratings yet
EE 8950 - Homework 3
4 pages
E211P ELECTRICAL FIRST FLOOR PLAN - POWER - AREA 1 - PHASE 1 Rev.6
No ratings yet
E211P ELECTRICAL FIRST FLOOR PLAN - POWER - AREA 1 - PHASE 1 Rev.6
1 page