About Configured BOM - VPM Synchronization

VPM and Configured BOM can synchronize part and VPM product information, including both BOM and item information. Both development configured part structure (WIP BOM), and production configured structure (only the current applicability), can be synchronized.

For additional details, see Collaborative Lifecycle User's Guide:Collaboration Between Physical Product and Engineering BOM Management.

This page discusses:

Item Synchronization Rules (Part without A structure)

  • Configured parts in any state can be synchronized to VPM. The VPM product can be synchronized to Configured BOM only if the part is in WIP mode. Once the part is released, sync from VPM to Configured BOM is not allowed.
  • If no VPM product exists during the sync, the VPM product is created in the In Work state regardless of the state of the part. Similarly, if the VPM product is synchronized, the part is created in the Preliminary state regardless of the state of the VPM product.
  • During sync from Configured BOM, if the VPM product already exists, it is connected by the Part Specification relationship. If not, the VPM product is created and connected.
  • The configured part can be released only if the corresponding VPM product is in the Shared state.

Configured BOM - VPM BOM Synchronization Rules

  • Only WIP configured BOMs can have bidirectional synchronization, that is, from Configured BOM to VPM and from VPM to Configured BOM. Only the current applicability information is synchronized.
  • Once the WIP BOM is released, the synchronization from VPM to Configured BOM is no longer possible. The synchronization from Configured BOM to VPM is however enabled since any changes to the configured structure are governed by the enterprise app.
  • If the configured structure has both configured and unconfigured parts, the applicability information of the WIP configured BOM is synchronized. The unconfigured part's BOM is synchronized using the existing ENG-VPM sync mechanism.

    Example: In the following case, when CF-010 is published to VPM, only the level 1 BOM and its applicability information will be synchronized. Configured part CF-022 will not be considered for synchronization because this structure is already released.

    Unconfigured part CF023 will be created in VPM and its BOM will be synchronized.

  • During the sync process, VPM products are created (if they do not exist) for all the child parts and are connected to the part with the Part Specification relationship.
  • New instances are created between the parent and child product part based on the quantity defined in the EBOM relationship. If there are any changes in the applicability values, you must manually execute the synchronization.
  • Only the current applicability is synchronized. Pending changes (proposed applicability) are not synchronized.
  • If a configured product has multiple types of applicability, the synchronization is blocked.
  • The Transfer Control option works similarly to the unconfigured part sync.
  • The release of the WIP BOM is a bottom up approach, that is, all child parts must be released before releasing the parent part.
  • The synchronization is blocked from the VPM side once the corresponding configured part is released.
  • When the PUE ECO is released, the VPM product is not revised, however the configured part is revised. In order to maintain the part and VPM product association, the same VPM product is connected to two revisions of the configured part.

Production BOM Synchronization Rules

  • The production release structure allows these operations: ADD, CUT, Replace. These operations can be directly done on the released structure using a PUE ECO.
  • The synchronization for a production released BOM is enabled only from the Configured BOM side.
  • The synchronization from Configured BOM has the Transfer Control switched off.