Certifiable test records are a project after the test,not a by-product of it.

Engine and component test cells run qualification and acceptance campaigns for flight hardware. Every fire is commanded against a written test card — a stepped sequence of valve states, throttle points and hold durations — under AS9100 quality governance, with software-in-the-loop elements under DO 178C.

A single hot-fire produces dense telemetry: chamber pressure at kilohertz rates, propellant tank pressures and temperatures, valve position feedback, structural strain, thrust. All of it has to be reconciled against the card, the SOPs, and the calibration state of every sensor on the stand.

After the fire, the work starts. Engineers pull DAQ exports into spreadsheets and scripts, line up channels against the test card by hand, and chase anomalies through raw plots: was the main valve 40 milliseconds late against the commanded step? Was the pressure-rise rate inside the predicted band? Every conclusion has to trace back to a raw channel — and to the calibration certificate of the sensor behind it.

Certification needs two things at once: a tamper-proof record of what was commanded, measured and concluded, by whom and when; and fast turnaround, because the analysis backlog is what gates the next fire. Existing tools deliver one or the other. The audit pack gets assembled weeks later, by hand, from the DAQ archive, the test card, the engineer's notebook and a folder of calibration PDFs.