jkramer
09-25-2003, 11:07 PM
Hi,
We are thinking about the best way to deal with what we call "Barbapappa parts".
One example is timing belts: one part that has different shapes in different assemblies.
Another is rivets: we model the rivet "before riveting" in order to make a good drawing of the rivet, but often we want the rivet to be "after riveting" in the assembly. And one type of rivet can be riveted into a plate of 1.5 mm AND also in another plate of 2 mm.
So there you have parts with one code number and revision, but with 2 or 3 (or more) shapes.
We need a standard procedure to store these parts in Workmanager so that we don't mess up BOM activities, and at the same time we keep track of what part is what.
One idea is to add a kind of postfix to the "Model No" in Workmanager, for example:
123456 (the normal part)
123456_riveted (the riveted part)
123456_riveted2 (another riveted part)
But the risk is that if the part changes, someone forgets to change all variants...
Any suggestions???
Thanks!
Jaap
We are thinking about the best way to deal with what we call "Barbapappa parts".
One example is timing belts: one part that has different shapes in different assemblies.
Another is rivets: we model the rivet "before riveting" in order to make a good drawing of the rivet, but often we want the rivet to be "after riveting" in the assembly. And one type of rivet can be riveted into a plate of 1.5 mm AND also in another plate of 2 mm.
So there you have parts with one code number and revision, but with 2 or 3 (or more) shapes.
We need a standard procedure to store these parts in Workmanager so that we don't mess up BOM activities, and at the same time we keep track of what part is what.
One idea is to add a kind of postfix to the "Model No" in Workmanager, for example:
123456 (the normal part)
123456_riveted (the riveted part)
123456_riveted2 (another riveted part)
But the risk is that if the part changes, someone forgets to change all variants...
Any suggestions???
Thanks!
Jaap