Skip to main content
11-Garnet
November 8, 2021
Solved

Use of non-latest version in a product structure

  • November 8, 2021
  • 1 reply
  • 5219 views

We have a situation where a subcontractor has delivered Rev A of a part which we have tested and are now ready to incorporate into the system we will deliver to our customer. 

In the meantime the subcontractor has continued work on the product and has delivered the part with added functionality, but have delivered it as Rev B with the same part number, ready for us to test.

However when we go to add the part into our overall product structure there is no way to select a specific version of the subcontractor part; that is, because Rev B is now in our PLM system there doesn't seem to be any way for us to add Rev A into the product structure.

Does anybody have any way around this, or thoughts on what we can do?

Best answer by GrahamV

This is fundamental to how BOMs work in Windchill, a BOM structure only controls the number of the child part, not the version, e.g. WTPart A10001 V1.2 may contain child WTPart B20001, no version is recorded for the child. If you wish to control the version of children, you have to use a filter method like baselines (a snapshot of part versions) or effectivity (typically a date or serial number from which a version comes into effect). The default filter is 'latest', which is why you always see the new version when revising.

 

Note, CAD documents usually have an 'As Stored' configuration that others have mentioned, this does record the child version, however it's not much use in the context of a BOM.

1 reply

23-Emerald III
November 9, 2021

Open the Rev A parts in Creo first, then open the assembly. This will create the assembly links to the Rev A components.

The caveat is that you will need to open the assemblies with the As Saved option in the future until you have upgraded the assembly structures to utilize the Rev B components.

 

Dana111-GarnetAuthor
11-Garnet
November 9, 2021

Thanks Ben, unfortunately these are not modelled in Creo.

23-Emerald III
November 9, 2021

Should not matter, as long as you have the rev A and Rev B in your PLM system as the same number but different revisions, it should still work. If they are in PLM as unique objects, you will need to create 2 upper level assemblies for each component revision.