Order
Customer requirement, approved specification, destination and requested documents.
Quality & safety / Traceability
A traceability record connects what was ordered, what was used, what was checked, what was released and where it was shipped.
Record architecture
The framework starts with identifiers and relationships: each retained record must point back to a product, batch, unit, process step or shipment.
Traceability depth is defined by product risk, regulation, contract and practical record needs. A batch-level product may require a different identifier strategy from an individually serialized cylinder.
Traceability chain
Identifiers move with the work so the final record does not rely on memory or manual reconstruction.
Customer requirement, approved specification, destination and requested documents.
Cylinder, valve, gas, label and packaging identifiers or controlled batch references.
Filling or assembly record, equipment status, operator and critical parameters.
Inspection and test results, disposition, reviewer and document revision.
Quantity, package identifiers, logistics documents and destination connection.
Three traceability layers
Connect component or batch identifiers to the configuration that was actually produced and released.
Link a measurement result to the method, equipment, calibration chain and stated uncertainty where required.
Keep approvals, changes, deviations, rework and release decisions in chronological context.
Official references
NIST distinguishes metrological traceability from general chain-of-custody or product-history records. Both ideas may be needed, but they answer different questions.