Managing Parts Across Multiple PLM Instances

One CES database may service several different PLM instances, which in turn house numerous projects.

 

Parts within the CES database may be approved for use in some projects and not others. During the design process you may discover a part in CES that would be useful for your project, but is not approved for your project. You can request that the part be approved for your project so that you can use it, instead of having to recreate the part yourself. A Parts Manager will approve or reject the part in question for the project in question. If the part is approved, the part's geometry gets propagated to each PLM instance on which projects utilizing that part reside.

For example, Project A uses Part1, which is stored in the CES database. Project A introduced Part 1 to the CES database, so it owns or has authority over Part 1. The designer for Project D requests approval for Part 1 in Project D. The Parts Manager approves Part 1 for Project D. Upon approval, Part 1 is propagated to PLM 2, which houses Project D. No other project on PLM 2 uses Part 1, so a new entry for Part 1 is created on PLM2.

Next, the designer of Project B requests approval for Part 1 in Project B. The Parts Manager approves Part 1 for Project B. Since Project A already uses Part 1 and Project B only resides in PLM1, no propagation occurs. The part, project name and approval status are added to the PLM link to PLM Project class.

Since Project A owns Part 1, only Project A can be used to update or synchronize Part 1. Any attempt to update or synchronize Part 1, while logged in to any project other than Project A, will fail.

For more information, refer to:

Requesting Part Approval
Managing Part Approval
Propagating Parts to other PLM Instances