mk2000
Mechanical
- Nov 5, 2001
- 92
I have seen this topic a few times in deferent companies and people always argue about this every time it comes up. Even here it is being discussed see this thread .
I would like to gather everyone’s experience and find out what is the best strategy to address the relationship between Part numbers (PN), BOM numbers (BN), Assembly number (AS), model number (MN) and linking their revision. To help me describe the situation I will use a scenario.
MN321A (computer mouse)
|_AN678A (computer mouse assembly)
|_BN456A (computer mouse BOM)
|_AN612A
|_BN613A
| |_PN123A
| |_PN124A
| |_PN125A
|_AN614A
|_BN615A
|_PN126A
|_PN127A
|_PN128A
|_AN616A
|_BN617A
|_PN129A
|_PN210A
|_PN211A
|_PN212A
I will use the following convention; XXNNNR where
XX is the identifying prefix (not necessary but help to clarify the number)
NNN is the actual number
R is the revision
The questions I have are as follows:
[ol]
[li]When should one use a separate MN to the AN? For example if we are building a computer mouse, then what is the advantage in having separate AN and MN.[/li]
[li]In what situations one would link the Revision of the model number and Assembly number (given that they are two separate numbers)[/li]
[li]To what level should you propagate the Rev changes? In the example above if revision of PN212A is changed to B should both corresponding BN and AN change only? Or do you propagate all the way up to AN678A and BN456A?[/li]
[li]Has anyone any experience in regulated industries and what is the best way to handle this? Every time a part number or even the revision of the product is changed then the company is up for resubmission costs.[/li]
[li]To make mater more interesting, what is the best practice in handling the software revision? For example if the software for USA version is deferent to Chines version and each of them is tracked and revised independently.[/li]
[/ol]
Please don’t hesitate to describe how you or the company you work for handles this issue (with out violating confidentiality). It is a common issue and everyone as an engineer had to struggle with it at one point or another. I plan to summarise the outcome of this thread and post a white paper on this forum. Everyone involved will be given the appropriate credit on the white paper.
Thank you
I would like to gather everyone’s experience and find out what is the best strategy to address the relationship between Part numbers (PN), BOM numbers (BN), Assembly number (AS), model number (MN) and linking their revision. To help me describe the situation I will use a scenario.
MN321A (computer mouse)
|_AN678A (computer mouse assembly)
|_BN456A (computer mouse BOM)
|_AN612A
|_BN613A
| |_PN123A
| |_PN124A
| |_PN125A
|_AN614A
|_BN615A
|_PN126A
|_PN127A
|_PN128A
|_AN616A
|_BN617A
|_PN129A
|_PN210A
|_PN211A
|_PN212A
I will use the following convention; XXNNNR where
XX is the identifying prefix (not necessary but help to clarify the number)
NNN is the actual number
R is the revision
The questions I have are as follows:
[ol]
[li]When should one use a separate MN to the AN? For example if we are building a computer mouse, then what is the advantage in having separate AN and MN.[/li]
[li]In what situations one would link the Revision of the model number and Assembly number (given that they are two separate numbers)[/li]
[li]To what level should you propagate the Rev changes? In the example above if revision of PN212A is changed to B should both corresponding BN and AN change only? Or do you propagate all the way up to AN678A and BN456A?[/li]
[li]Has anyone any experience in regulated industries and what is the best way to handle this? Every time a part number or even the revision of the product is changed then the company is up for resubmission costs.[/li]
[li]To make mater more interesting, what is the best practice in handling the software revision? For example if the software for USA version is deferent to Chines version and each of them is tracked and revised independently.[/li]
[/ol]
Please don’t hesitate to describe how you or the company you work for handles this issue (with out violating confidentiality). It is a common issue and everyone as an engineer had to struggle with it at one point or another. I plan to summarise the outcome of this thread and post a white paper on this forum. Everyone involved will be given the appropriate credit on the white paper.
Thank you