Managing the enterprise BOP
Remove origin links between BOP structures
At some point in the planning process, a processor operation (for example, in the plant BOP) is optimized to a level where further updates to it (in this case, from the product BOP) is counter-effective. It is assumed that your business process defines when such an action needs to be performed. You can use the Disconnect menu command to remove the origin link on a selected process or operation.
After disconnecting a process or operation, the object has the same behavior as a structure-specific node (for example, a plant-specific process or operation).
Caution
Because there is no longer an origin link between the source and target after disconnecting, the following applies:
The accountability check now considers the source and target nodes as different.
The Find in ... menu commands no longer find the equivalent node in the other structure.
To perform this procedure, you must have write access to the product or plant BOP.
Procedure
- Right-click one of the following:
An allocated process, operation, or process area in a plant BOP.
A partition, process, or operation in a product BOP that is cloned from a generic BOP.
Choose Disconnect from Origin from the shortcut menu.
In the Disconnect from Origin dialog box, select Disconnect Children to break the origin link of all the children of the selected line.
Click OK.
Results
Teamcenter traverses the structure from the selected point down and removes all the origin links with the product BOP or generic BOP. The selected line (and its children, if that option is selected) is now product or plant-specific. You can no longer propagate from generic to product BOP or from product to plant BOP. This procedure does not remove any lines from the structures.
If you do not have write access to certain processes or operations, these are not disconnected.
Source: https://docs.sw.siemens.com/en-US/doc/282219420/PL20251212545240207.mse/xid480572 · retrieved 2026-07-11