Create, update, or remove a DIPA

You can generate DIPA for a single selected object, as well as recursively for all stations under a selected process. Using the same command, you can create, update, or remove existing DIPA.

​​When you generate a dynamic in-process assembly (DIPA) recursively, DIPA is generated for all stations and processes under the selected process line or process area.

Prerequisites

Your work package must contain a plant bill of process (BOP). Teamcenter Easy Plan does not support DIPA with classic BOP data.

You must create a sequence flow between the process stations that you use in a DIPA node. Another way to think of it is that every process station except the last one in a DIPA node must have a predecessor.

Note

Teamcenter Easy Plan supports external sequence flows for DIPA.

You must set the following preferences to use this feature:

• MEDynamicIPADisplayName—Determines the property of the predecessor in the given process structure to be considered when generating the name of the In-Process Assembly (IPA). A valid value is one of the following plant BOP line properties: bl_item_object_name or bl_rev_object_name.

• MEDynamicIPAOccurrenceTypes—Determines which part occurrence types are collected into a DIPA node. The default value is MEConsumed. If you use other occurrence types, such as custom occurrence types, your administrator must add these occurrence types to the preference. Otherwise the DIPA does not contain parts assigned to the process structure with those occurrence types.

• MEDynamicIPARemoveOccTypes—Determines which occurrence types to consider for removal from aggregated parts of the predecessors in the given process structure to generate the DIPA. Set the value to valid Teamcenter occurrence type in your structure.

• ​MEDynamicIPARecursiveCreateProcessTypes determines which bill of process (BOP) object types are considered to recursively generate DIPA. The default values are Mfg0MEProcStatnRevision and MEProcessRevision.

• MEDynamicIPARootItemTypes—Determines the types of root item allowed by the product or manufacturing bill of material (MBOM) structures that are part of a DIPA. The default value is Item. Note If you create a custom item type that is subclassed instead of subtyped, or vice versa, you must edit the value of MEDynamicIPARootItemTypes and add your custom type.

• MEDynamicIPATraversalClosureRule—Determines the closure rule to be used for traversal of the process structure to calculate the DIPA. The default value is DynamicIPAProcessOnlyWithPA. Note If you customize your process and add your own closure rule type derived from the item type, you must edit the transfer mode value of MEDynamicIPATraversalClosureRule.

• MEDynamicIPADisableRepopulateForPS—Determines the closure rule to use to traverse the process structure to calculate the DIPA. The default value is DynamicIPAProcessOnlyWithPA.

In addition, you must add these preferences to the AWC_StartupPreferences in the Teamcenter rich client.

See the Preferences section in the Active Workspace Administration documentation for a description of preferences and how to set them.

Procedure

1. If you have not done so already, search for and open an existing work package that contains processes and operations, and navigate to the Work Instructions Authoring or Process Planning page.

2. In the Process panel, expand the process and select a station or process.

3. Do one of the following.

To create a new DIPA, from the process toolbar, click Generate DIPA .Teamcenter Easy Plan creates a DIPA node that includes all the parts that were consumed in the process before the station you selected.To assign DIPA to an operation, copy and paste the object to that operation or drag it to the operation. In the Process panel, select an operation and then drag the DIPA node to the Parts tab.

To update an existing DIPA, select it in the DIPA tab and click Generate DIPA . Teamcenter Easy Plan updates all consumed parts within the DIPA node and all predecessor relationships. If you assigned the DIPA node to an operation, Easy Plan updates the same information that is assigned to the operation. You do not need to manually refresh it there. Tip After you apply a different configuration to a structure, update the DIPA node. You might have configured out part of the DIPA node.

To remove a DIPA node, remove any predecessor relationships within the node. If you assigned a DIPA node to an operation, you must also manually remove any assignments to operations.