In this guide 6 sections
Give every unit one serial and hang three record types from it, namely the functional test log, the calibration values written to the device and the return findings. When an RMA arrives, scan the serial, attach the teardown result and filter failures by lot, board revision and firmware build, so the pattern shows before the next shipment.
Decide what the serial points to
A serial number is only useful when every record agrees on what it names, whether the finished unit, the main board or the sensing element. A returned sensor often carries a swapped module. Write the rule down first.
Print the serial as a Data Matrix label on unit and carton, then add a second field for the board serial so repairs keep their fixture history.
One rule saves arguments later. A serial is never reused, even after scrap.
Store every test run, not just the final pass
Import each station log, usually a CSV or text dump from the fixture software, against the serial and keep the station ID, fixture number, operator and firmware build.
Keep the failed runs too, because a unit that passed on its third attempt after a retouched solder joint tells you more than a clean pass.
Store measured values, not only pass or fail, since a supply current that sits close to its limit on day one explains a field failure that appears months later. Limits alone hide margin.
- Station ID, fixture number and operator
- Each limit tested, with the measured value
- Firmware build flashed before the run
- Retest count and the reason for each retest
- Date, time and the test program revision
Attach calibration data to the same record
Industrial sensors and meters carry offsets, gain factors and linearisation tables written to flash, so save those values against the serial with the reference instrument and its certificate number.
When a customer says a reading has drifted, compare today’s bench result with the values written at the factory, because that comparison separates a drifting element from damage.
Store the calibration file. Restored units need the exact table.
Record the return the day it lands
Open the RMA when the parcel is scanned in and capture the stated fault, shipment date and installed environment, such as a pump house or a cold room.
Log a failure code from a fixed list after the bench check, since “not working” cannot be counted but open sense line or corroded connector can.
Photograph the board before cleaning it, because water marks, burnt tracks and flux residue vanish once a technician reaches for the brush.
- Customer’s stated fault and site conditions
- Failure code chosen from a fixed list
- Photos of the unit before cleaning
- Part replaced and its lot code
- Verdict: in warranty, out of warranty or misuse
Read the pattern by lot and revision
Once the three links exist, the questions get simple: which board revision returns most often, and do failures cluster in one component lot, one fixture or one firmware build? A filter answers each one.
Link each return to the build record, so that a capacitor lot seen in six returns lets you list the other serials built with it. Then decide who to contact.
Start small this month. Take your last ten returns, key them against their test logs by hand, and note which link was hardest to find, whether label, log or RMA form.
Serial record sheet
Each serial gets one sheet. The top block lists test runs by station, fixture, firmware build and measured values, and the middle block holds calibration offsets, gain and the reference certificate number. The bottom block logs the RMA, with the stated fault, failure code, photos, replaced part and lot, and a verdict of in warranty, out of warranty or misuse.
Open a blank worksheet to printQuestions owners ask
Should the serial sit on the board or the finished unit?
Both, if you can. The board serial survives repairs and module swaps, while the unit serial is what the customer quotes, so link the two and either one will find the full history.
How long should test logs be kept?
Hold them for the warranty term plus any contract retention period, and keep them longer for regulated products such as medical devices. Archive the raw files. Keep the summary row searchable.
Can a spreadsheet do this?
Yes, for a few hundred units a year, provided one person owns the workbook and nobody pastes values over the formulas that link test logs to the RMA sheet. Beyond that, hand merging is the slowest step.
What if returns arrive without a serial?
Log them under a temporary ID, then match by label, date code or calibration values stored in the unit’s memory, which survives a lost sticker. If it keeps happening, fix the label’s durability.