Using the me_populate_plantbop_from_bop migration utility

The command line utility me_populate_plantbop_from_bop is the primary tool for migrating a classic BOP structure to a plant BOP with a predefined plant BOP skeleton. The utility copies operations from the classic BOP and pastes them into an equivalent station in the plant BOP. The copied operations are controlled by a closure rule and are shared with the classic BOP.

The me_populate_plantbop_from_bop utility is a migration tool, not an update tool, meaning it should only be executed once on a classic BOP. After that, the Paste by Rule command in Manufacturing Process Planner should be used for any cleanup or adjustments.

Data input

• A classic BOP, its configuration, scoping, and closure rule to control what is copied.

• Optional mapping of the stations in the classic BOP to the equivalent ones in the plant BOP.

• Plant BOP skeleton - could be automatically created from the BOE twin structure.

• A classic BOP and a plant BOP are inputs to the utility as collaboration context objects.

• Station mapping options.

Main functional behavior

• Properties and attachments are copied from a classic BOP station to the equivalent station in plant BOP (controlled by a cloning rule).

• Operations from the classic BOP are copied and shared with the plant BOP (controlled by a closure rule).

• Properties of operation occurrences are copied (controlled by a preference).

• Simulation datasets on the operation and station are kept consistent (simulation IDs are maintained).

• Operation flows and scope flows are carried over.

• Operation copy is controlled by the cloning rule.

• Depending on use case, process could also be shared between classic BOP and plant BOP.

• Operations can be copied into one plant BOP only and only once per plant BOP.

Excluded

• Product views are not migrated.

• Twin relation between BOE and skeleton plant BOP is not required. The utility only uses the station relation.

• No support to Process Simulate studies.

Station mapping in the me_populate_plantbop_from_bop utility

The command line migration utility must resolve the mapping of what represents the station in the classic BOP to theprocess station in the plant BOP. This is done using one of four methods:

1. Map by itemID In the utility, a file can be provided with a list of pairs of itemIDs or itemUIDs values that identify what represents a station in the classic BOP and its equivalent station in the plant BOP.

2. Map by BOE Station (Default) The equivalence stations are those that are sharing the same BOE station. This is the default behavior.

3. Map by BOE Station assigned to Operation (Default) If there is no clear definition of a station in the classic BOP and the BOE station is assigned to the operation, the operation is copied to the process station in the plant BOP with the same BOE station.

Note In the plant BOP structure, a BOE station should not continue to be referenced directly by the operation; it creates redundancy and overhead when moving an operation from one station to another. When the migration utility has completed, you can revise the operations and remove the references to the station BOE, as shown in the image above.

4. Map by user defined callback A custom callback function can be written to define how to map the classic BOP station to the plant BOP process station. The callback could also explicitly determine which operation in the classic BOP needs to be copied to which process station in the plant BOP.

Key steps in migrating a classic BOP to a plant BOP

1. You must have a classic BOP in a collaboration context as the source.

2. You must have a skeleton plant BOP for the target, which can be created using one of two methods.

Manually create the skeleton plant BOP.

From an existing BOE, use the Synchronize Process and Plant command to create the skeleton plant BOP.

3. Put the skeleton plant BOP in a collaboration context.

4. Run the me_populate_plantbop_from_bop utility first, using the -dryrunfile argument to check if the migration will be as expected.

5. If satisfied, run the me_populate_plantbop_from_bop utility again without the -dryrunfile argument.

6. Run an Accountability Check to make sure all operations are accounted for.

Use the Dynamic Equivalence option using the ItemID.

7. If there are missing operations, use the Paste by Rule command in Manufacturing Process Planner to copy and paste the operations from the classic BOP to the correct locations in the plant BOP.

Note

Typically, you migrate a previously released (and frozen) classic BOP. However, if the classic BOP was not released, you should release (freeze) it after the migration to prevent any modifications.