Propagating Parts to other PLM Instances

About Propagating Parts to other PLM Instances

During the design process, a designer may request approval for a part not currently approved for his or her project. That request is processed by the parts manager, who can change the approval setting for the part in question.  If the parts manager approves the requested part for the project, the propagation or reconciliation process automatically begins. This process runs in the background to make the part geometry available to the PLM instance that houses the project.

When Propagating Parts to other PLM Instances

  • The propagation of parts is triggered when the status value of a part is changed to APPROVED using the Manage Approval window. For more information, refer to Managing Part Approval.
  • Propagation/reconciliation of parts to other ENOVIA instances requires the V5 Reconciliator. For the Reconciliator V5 to work you must enable the WPE license on both the server and the client. However, if the batch is launched in a separate environment, the licensing configuration of the batch may be different from the licensing configuration of the CATIA Client.
  • Propagating Parts to other PLM Instances requires an SRU license.
  • VPMV4 and VPMV5 PLM systems are supported.
  • The propagation process is only triggered from within Wintop (CATIAClient). It is not triggered within the Webtop (LCAClient).
  • Propagation considers only the CAD modifications.
  • There is no propagation of lifecycle status or P&O modifications.
  • Propagation does not support the C* capability of a VPMV4 implementation.
  • The designated Parts Manager must have an appropriate approval status, as established by the System Administrator. For more information on approval status, refer to CES Enterprise Catalog Administration Guide : User Tasks : CES Administration Desktop User Documentation : Managing Users and User Groups : Approval Settings for Users and User Groups.
  • During the session, prior to actually approving any requests, the Parts Manager must enter his or her credentials in the PLM Standards dialog, including User Name, Password and Role. The Parts Manager must login using the VPMADMIN.ADMIN.CESRECONCILE role.
  • If the PLM system instance that houses the project for which the part is newly approved, does not house another project for which the part is already approved, the approved part will be created in that PLM instance.
  • If the PLM instance already houses a project for which the part is approved, the existing part will be overwritten. Therefore, if the local copy of the part has been modified, this process will overwrite the modifications.
  • The project that introduced the part to CES is, by default, has authority over the part. If the project for which a part is approved also has authority over the part, no propagation is needed.
  • The part number for a part used in multiple PLM projects will be the same in all projects.
  • All PLM instances must use the same user/password combination for the Parts Manager.
  • All the PLM instances associated with a specific CES server should use the same user/password combination for the Part Managers.
  • Before managing part approval and initiating the propagation process, you must set the appropriate options. For more information, refer to Tools Options for Propagating Parts.
  • Additional CAA APIs for external workflow tool plug-in are not supported. Customization must be handled through standard save user exits.