Revision Freeze Function ?
We have the following BOM Example
PCA0001 -1 Rev 01 having PCB0001 Rev 01 as component
PCA0001-2 Rev 01 having PCB0001 Rev 01 as component
PCB0001 Rev 01 has SCH0001 Rev 01 (schematic) as component.
Since we are building multiple boards at the same time, we are creating 2 version of the PCA
PCA0001-1 is the Prototype version of PCA0001 , and PCA0001-2 is the qual version although it’s build by the same PCB.
Currently Engineer is revising SCH001 Rev 01 to Rev 02 , and it automatically updates PCB0001 BOM Components to SCH0001 Rev 02.
However Engineer still wants to keep PCA0001-1 components to still refer to SCH0001 Rev 01 due to this is more for prototype purposes and they would like to freeze the components under it. The only way I could think of is to use a different PCB, eg : PCB0001-1 and SCH0001-1, however it will be maintenance nightmare if the number of parts increases. What is the best way to handle this in Agile ?
Thanks,
Donny
What you are suggesting is not possible in PLM the way you have set it up.
First we need to take a step back to understand what PLM is. It represents an Eng playground to develop product and DOES NOT represent purchased inventory. ERP is where we track what is purchased and how it looked at time of purchase. In order to do as you are suggesting I suggest using the differentiation in ERP by using effectivity dates.
Hi Patrick,
Thank you for the answer. We have not gone into ERP yet at this point, we have CM managing the builds with them having access to our Agile.
The issue here is that the engineer believed that in Agile unless we increase the rev of the PCA0001 from Rev1 to Rev2, the component revision below it should stay frozen/as-is. I have proven that it’s not correct and Agile (and any other PLM systems) will always refer to the latest revision of the components, regardless whether we up-rev the parent BOM or not.
They accepted that and still looking for ways to freeze the component revision. They have had a few builds that they were not aware are using the latest component revision instead the original ones. They were able to fix by it using deviations, but it’s hard to check on this one by one. What is the typical way to handle this issue ?
Thanks,