Software revisions in manufactured parts

We have software installed in our manufactured products on an end of line testing machine. The software revision is added to the PCB of the manufactured product via testing and stored with the test data on the testing equipment and linked with a serial number of the manufactured product. The software revision can be retrieved and linked backward from the test equipment and various checkpoints can be added.

My question is how to indicate which software revision must be used before the product ends up in testing equipment? Out of my head, a nonstock part number with a revision could be created where the revision is updated at the same time as on the testing equipment. But does anyone have any other working ideas or experience?

Based on my understanding, you are on the right track. Set the software revision to match the product revision. For the software part number, I suggest having only one revision for it and setting Quantity Bearing = FALSE. Also, set the QtyPer = 0 on the method.

I think some have used the Lot feature to store a firmware code. Any update of the machine would consume the old lot and record the new lot. But that is after the fact. To know before, you’d have to do what you and Matt suggested.