A serialized product with unversioned firmware is only half traceable — and it is always the wrong half when a field problem appears.
Hardware traceability is well understood: serial number, component lots, work order, test record. Firmware traceability is younger, less standardized, and in contract manufacturing it is where records most often break, because the software comes from one organization and the unit is built in another.
The fix is unglamorous. Every unit records which firmware image was loaded, with a version and a checksum, and the record lives with the serial number rather than on the programming station. When a version is superseded, the effectivity is released like any other change: from this serial, or from this date.
Parameter sets deserve the same treatment. Two units with identical firmware and different parameters behave differently in the field, and a support engineer who cannot see which parameters were loaded is debugging blind. Where parameters vary by variant or by customer, they belong in the build record.
The payoff arrives during a field investigation. A serial number that resolves to a hardware revision, a firmware version, a parameter set and a test result turns a fleet-wide worry into a bounded question about a specific batch. Without it, everyone starts guessing, and guessing at fleet scale is expensive.
— GANI Contract Manufacturing engineering team