About Managing Collaborated Data

You can manage the actions that you perform on collaborated data.

This page discusses:

Delete Instances

When structures are collaborated, the system maps each EBOM relationship in the Engineering BOM Management app to corresponding instances in the Product Finder app.

This provides a reliable way of determining the instances to be delete when EBOM quantities are reduced, because they are associated with a specific EBOM. When the EBOM quantity is reduced, the instances are deleted in the reverse order of creation. Therefore, the newest instance is deleted first.

Replace Instances

If a child Product Finder  product is replaced in a structure collaborated with the Engineering BOM Management app, then on subsequent collaboration, the children EBOM relationships under the original product are removed and new EBOM relationships are created with the replaced part.

For more information about the behavior when an already collaborated child part in Engineering BOM Management app is replaced in a structure and subsequent collaboration happens, see 3D Modeling User's Guide: Systems Architecture | Product Structure Design | Working with Products | Replacing Products.

Delete Physical Product

When you delete the reference, its corresponding Engineering BOM Management part is deleted.

For more information about how to delete, see Deleting Objects.

Delete Engineering BOM Part

Search a part from the search results. Select the check box next to the name of the part and click Delete.

During the deletion of the part or removal of the part specification relationship, its corresponding Product Finder reference is also deleted.

Note: The Product Finder rules are dependent on the roles provided to the user. The product and the part specification link can be deleted even if the product is in the WAIT-APP state, provided the user has Administrator rights.

Rules followed:

  • The reference gets deleted, under the following circumstances :
    • It is instantiated under other products.
    • It is locked by the owner of the Product Finder reference and the Product Finder reference owner is deleting the part.
    • The user deleting the part has Administrator privileges in the Product Finder app.

  • The reference cannot be deleted if it is locked by a user other than the reference owner.

  • If the specification link is removed and the resulting deletion of the Product Finder reference is violating any Product Finder rules, then the Product Finder reference is not deleted and instead its control is transferred to the Product Finder app.

Clone Objects in Engineering BOM Management

Cloning keeps an internal link between the source objects and the duplicated objects. When you clone an object in the Engineering BOM Management app, there is an option to include the related specification data with the clone object.

Note: The collaboration process leads to inconsistent results if you combine multiple clone and revision operations together because, it tries to reconcile these operations in the other environment. Therefore, it is recommended to collaborate the new cloned objects immediately after they are created.

  • If the related specification data is included: During the collaboration from the clone, the system recognizes the operation and executes the same operation in the Product Finder app.
  • If the related specification data is not included: The object is treated as a new part without any existing part specification.

If you choose to keep the part specifications, select the EBOM Control option. Otherwise, the cloned physical object will have the duplicated child instances, but the EBOM would show no children under the clone.

If you collaborate an Engineering BOM Management app cloned object, the cloned physical object will always be a new branch . For more information see, About Revisions, Branches, and Duplicates.

When a physical controlled part object is cloned in the Engineering BOM Management app, the newly created clone object is treated as a EBOM controlled object.

Note: If an Engineering BOM Management part is cloned, the children under the original product will be automatically instantiated under the cloned object.
For more information, see Engineering BOM ManagementGuide: Part Definition | Cloning a Part

Create Branches or Duplicates of Objects in Collaborative Lifecycle

If a product is duplicated in the Collaborative Lifecycle app including any representations associated with it, all the representation objects under the product are duplicated. The duplicated representation objects are associated with the duplicate of the product in the Collaborative Lifecycle. This ensures that the new duplicated product can have its own geometric modifications without affecting the base product in the Collaborative Lifecycle app.

Duplicating an object in Collaborative Lifecycle that is controlled by Engineering BOM Management, using the Duplicate or New Branch, results in new objects which are controlled by the physical product structure. For more information see, Duplicating Objects and Creating a Branch.

Note: If a Collaborative Lifecycle product is duplicated, the children under the original product will be automatically instantiated under the duplicated Collaborative Lifecycle object.

Create Revision When Major/Minor Version Creation is Enabled in Collaborative Lifecycle

The version on the Collaborative Lifecycle app is mapped with the revision on the Engineering BOM Management app.

Note: New revisions of objects can only be created in the environment that owns the object (a design-owned object can only be versioned in the Collaborative Lifecycle app and an EBOM-owned object can only be revisioned in the Engineering BOM Management app). During collaboration, the system detects that a new revision has been created and the new revision is automatically executed in the other environment. The part specification relationship is also updated.

The Collaborate with EBOM recognizes the minor and major data in both the Collaborative Lifecycle app and the Engineering BOM Management app. One part is created and connected for each major index in the Collaborative Lifecycle. During Collaborate with EBOM, the part connects to the BSF minor of the current major index. Once a minor in the Collaborative Lifecycle app is versioned to create a new minor, it becomes out of sync. During next collaboration operation, the specification link is moved to the new BSF minor.

Notes:
  • Combining multiple clone and version operations together before collaboration results in inconsistent results, because it tries to reconcile these operations in the other environment. Therefore, it is recommended that you perform collaboration on the new version immediately after it is created.
  • In the Collaborative Lifecycle app, if a product is revised, the children under the original product are automatically instantiated under the revised object.
  • When a Collaborative Lifecycle app object is synchronized from a Collaborative Lifecycle app to an Engineering BOM Management app and if it is not a BSF one, the BSF minor object is synchronized irrespective of which minor is selected for collaboration.
  • If a Collaborative Lifecycle app minor object is already synchronized and is connected to a Engineering BOM Management app object, and the user tries to synchronize this object which is non-BSF and upon invocation of synchronisation the BSF minor would be synchronized and the part specification link would be moved from the non-BSF to the BSF minor.

For more information about minor and major versions, see Versioning.

Create Revision When Major/Minor Version Creation is Disabled in Collaborative Lifecycle

The version on the Collaborative Lifecycle app is mapped with the revision on the Engineering BOM Management app.

The collaboration mechanism attempts to maintain the same number of versions and revisions in both environments. This means that if, the first collaboration is being performed from the third revision of a part, the collaboration publishes the initial revision, and use the revision operation to ensure that there are equal number of versions and revisons on the respective side.

As the consequence of this behavior, the customized lifecycle graph states must support versioning in the initial state.

Notes:
  • Combining multiple clone and version operations together before collaborating leads to inconsistent results in the Engineering BOM Management, because it tries to reconcile these operations in the other environment. Therefore, it is recommended to perform a collaboration on the new version immediately after it is created.
  • If a part created in the Engineering BOM Management is revised and then published to Engineering BOM Management with design control, a version of the published part is created in the Product Finder as it is now controlled by Engineering BOM Management.

    However, any attempt to collaborate the revision of published part from the Engineering BOM Management app fails, because the corresponding revision of the part in Engineering BOM Management already exists.

    Similarly, any attempt to collaborate the version of the part in the Engineering BOM Management app will fail, because the corresponding revision of the published part in the Engineering BOM Management app already exists.

  • If a product created in Product Finder is versioned and then published to Engineering BOM Management with EBOM Control option, a revision of the published product is created in Engineering BOM Management as it is now controlled by Engineering BOM Management. The revision of the published product created in Engineering BOM Management is automatically connected to the corresponding version of the product on Engineering BOM Management. As the product version on Engineering BOM Management is EBOM Controlled, the revision created in Engineering BOM Management becomes EBOM Controlled.
  • If multiple revisions of a part or versions of product are created and is collaborated later, all the previous versions and revisions are also collaborated by default. However, note that the previous versions and revisions are collaborated individually. The substructures associated with the previous versions and revisions are not collaborated, irrespective of the Expand Depth selected while invoking collaboration.