Child Part revision auto pushed to parent assembly

[hhuang-4]

In Part structure that is built manually. If a child part gets revised, the new revision gets reflected in the part structure of all parent parts and their past revisions automatically. Which does not sound logically right.

Let's say I have a manually built part structure  Parent A.1 which links to Child A.1.   and then Parent A.1 gets revised to Parent B.1 still linking to Child A.1

Then, Child A.1 gets revised to B.1 and checked in.   without touching Parent B.1 object.

In my system,  both Parent A.1 and Parent B.1 are automatically linked to Child B.1 now.  and Parent B.1 stays at B.1 (which is correct).

We are not using change management, just manual editing.

This behavior does not sound logically right,  Parent A.1 should capture the part structure at the time it was created, and should not be updated to Child B.1 without a explicit modification.

However, it does sound like how PTC designed it for as the logic behind is Parent is linked to PartMaster of Child, which means most recent version.

Hope someone might explain why?  and how do I capture the historical part structure?

[kpritchard]

Use baselines to take a snapshot of specific versions of objects (WTParts) in the structure.

You may want to look at your rules/best practices around when to Revise and when to use a new Part Number.  The logic above suits industry best practice (IMO), and works best when "dumb numbers" are used rather than intelligent numbering.

[LoriSood]

Keir is correct. Windchill includes a few OOTB configuration specifications that can be used for dependency collection. By default, it uses the "Latest" config spec when gathering dependent parts of an assembly. Thus, if a child part is revised the latest revision will be collected when the dependents are collected. It is possible to use different config specs that may better suit your needs, such as the suggested baseline, or effectivity, etc.. If your using CAD Docs, you can also use the As Stored configuration when collecting the dependents, which will return the versions of the dependents that were in the workspace when an object was checked in.