We have two ways of handling our chassis software here at my company. One business unit puts the software on the bill of material at a level where a change in software causes a revision to the top level assembly. this allows traceability between firmware and hardware.
A second business unit 'kits' the software so that any changes to software do not cause a revision to the top level. There is no traceability to the hardware with this choice. There are +/- to either way.
I am contacting you to see if you can refer me to an individual in your company or your professional circle that may provide me insight into firmware configuration management (firmware on a bill of material that a contract manufacturer) will deal with. We are looking to see how other companies handle this issue. What is the 'best way'.