For example, let's say that part number 12345 Rev A is the PCBA with firmware version 1.0. We order our PCBAs from our vendor with firmware already loaded onto it. I'm referring to the PCBA into which the firmware is loaded. To be clear, I'm not asking about the version of the firmware itself - that is easily handled. Strictly applying the rule would imply that any firmware version change requires a new part number, but this seems that it can rapidly become excessive as bugfixes and minor features are rolled out. However, some things can change fairly often, such as firmware versions. If they must be kept separated because there is a change in Fit, Form, or Function (the F3 rule) that affects the next assembly, then the old and new parts must be kept separate and a new part number is required. If the change is such that old and new parts can be co-mingled in the same parts bin, then only a drawing revision is required. In researching this question, I've come across multiple sources that state the principle of "interchangeability" as being the arbiter of this decision. when to create a new part number must be answered. When developing an ECR/ECN process, the question of when to roll a rev vs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
June 2023
Categories |