Measurement and traceability14 / 39

Track defect class, technical approval, repair method and return-to-service decision in the work order.

On a certificate you read the instrument identity, the calibrated points, the deviation and the measurement uncertainty; the uncertainty narrows your alarm limit.

When comparing two recorders, record matched times, clock settings and sensor positions together.

Find the last valid and first returning readings; do not estimate the temperature between them.

Record how a route, unit, plate or process change affects validated conditions before implementation; assign test and rollback owners.

Compare raw values, known events and file completeness; a flat curve alone proves neither stability nor device failure.

Before excluding an unusual monthly reading, match the raw file with run events and the relevant clock records.

Track model and serial scope, current document versions, gaps and ownership in one technical file.

Review raw data, adjacent readings, device status and event evidence before excluding an outlier.

Define scope, request channel, authorised roles and file format for controlled access to event records.

Control the comparison to separate device, clock and calibration differences from location effects.

Duration bands make events easier to compare. Define boundaries and include logging intervals and gaps in the report.

Product requirements and evidence duties do not disappear when the main carrier outsources work.

Assessing every trip alone hides gradual performance change.

Identify the event by container, lot, time and measurement point; track decision owner and notification acknowledgement.

The same average can hide different record completeness and route mix. Match runs first, then review the distribution.