How Are Reference Devices and Uncertainty Managed in Calibration Software?

Short answer: how should the record chain be established?

Link each calibration job to the specific certificate revision of the reference instrument used and to the versioned uncertainty budget for that job; do not silently change this link after technical approval.

A digital system must not store only the certificate PDF and the final uncertainty value. It must be able to trace backwards why the reference was suitable for the job, which revision of the measurement model was used, the source of the inputs, who reviewed the calculation, and which record revision the published result is based on.

Why are the reference instrument, certificate and measurement result separate records?

The physical instrument represents its life cycle, the certificate documents a calibration event, and the measurement result represents the technical output produced in a specific job.

According to BIPM/JCGM VIM3, metrological traceability is the ability of a measurement result to be linked to a reference through an unbroken documented chain of calibrations, each contributing to the uncertainty. Therefore a single “reference instrument has a certificate” field in the database is not sufficient. The system must show which result is linked, through which calibration event of which reference, to which chain.

Which fields should a reference instrument card contain?

Beyond identifying the instrument, the card must carry the technical scope and status history that make a conformity assessment possible for a specific measurement job.

• Unique inventory identifier, manufacturer, model, serial number and physical location,
• measured quantity, measurement range, resolution and required auxiliary equipment,
• calibration, intermediate verification, maintenance, adjustment, repair and transport events,
• the calibration event and the accepted certificate revision,
• the result, uncertainty, correction and scope information on the certificate,
• time-stamped statuses such as available, reserved, quarantined or out of service,
• the person who made the technical acceptance, date, justification and any usage restriction.

When a new certificate arrives, do not overwrite the old file. Even if the document number stays the same, open a new revision if the result, uncertainty or scope has changed. The certificate link used in past jobs must remain on the old revision; the new revision should only become selectable for future jobs after an authorized acceptance decision.

For the broader instrument life cycle measuring instrument inventory guide; for the field result link calibration certificate and field report traceability is complementary.

Which gates must operate when a reference instrument is assigned to a job?

A due-date check alone is not sufficient; the measurand, range, target uncertainty, environmental conditions, instrument status and certificate acceptance must be verified together.

1. Planning: the reference class, measurand and range required by the method are filtered.
2. Assignment: the instrument's availability on the job date and the accepted certificate revision are checked server-side.
3. Job start: after the reservation, it is re-verified whether any maintenance, impact, failed intermediate check or quarantine event has occurred.
4. Measurement record: the reference actually used is linked to the raw record by its unique identifier, not by free text.
5. Technical review: range, corrections, the relevant uncertainty and environmental conditions are shown together.

If a gate fails, the system should not automatically declare the result “invalid”. It should stop further use, show the reason and route the affected records to an authorized technical review. The technical decision itself must also be recorded with date, person and basis.

How should a measurement uncertainty budget be versioned?

Before the final expanded uncertainty value, store the measurand, the model, the input sources and the calculation steps in a reproducible manner.

JCGM 100:2008 GUM gives the general rules for the evaluation and expression of measurement uncertainty. The official JCGM publication inventory also lists complementary documents such as JCGM GUM-6:2020 on measurement models and the introductory JCGM GUM-1:2023. The digital counterpart is not a single calculation cell but a versioned technical record.

• An explicit definition and unit of the measurand,
• the measurement model or equation revision,
• the value, unit and data source of each input quantity,
• the Type A or Type B evaluation record and the technical justification for the choice,
• standard uncertainty, probability distribution and degrees of freedom if applicable,
• sensitivity coefficients and significant correlations,
• combined standard uncertainty, coverage factor and expanded uncertainty,
• calculation engine/template revision, creator and technical reviewer.

When the formula or template changes, past records must not be silently recalculated. A new revision is opened with the reason for the change and its effective date. The previous result is preserved together with the model it used, the input snapshot and the calculation output. If recalculation is required, a new result revision is created and it is stated which record it replaces.

How is the uncertainty on the reference certificate linked to the budget?

Take the relevant result and uncertainty on the certificate into the budget from the selected calibration point and certificate revision, not from a general PDF link on the instrument card.

ILAC P10:07/2020 sets out the policy on metrological traceability; ILAC P14:09/2020 explains the estimation and statement of measurement uncertainty in calibration. In a digital system their counterpart is more detailed than the reference instrument appearing “valid”. The certificate result relating to the range or point used in the job is selected; the uncertainty value, its unit, coverage factor and, if needed, probability information are linked to the budget input with their source.

This link must not be a copy-paste field. If the source certificate revision changes, the input in the past budget does not change. If a corrected certificate introduces a significant technical difference, the system lists which calibration results the relevant reference has been used in since its acceptance date and opens an impact review. Instead of automatic cancellation of results, an authorized technical assessment, the justification and, if required, a report revision are recorded.

How should authorization, audit trail and technical approval be separated?

The roles entering the data, building the budget, performing the technical review and publishing the result must be distinct; critical changes must be written to an audit trail that preserves the old value.

ISO/IEC 17025:2017 is the current international framework for the competent, impartial and consistent operation of laboratories and was reaffirmed by ISO in 2023. ISO also notes that the 2017 revision places stronger focus on information technologies, electronic records and the electronic production of results. Software does not replace the standard; it makes the controls defined by the organization implementable and auditable.

• Separate reference instrument master data from the authority for technical acceptance.
• Manage the uncertainty budget with draft, under review, approved and out-of-use statuses.
• Record changes to formulas, inputs, units, certificate revisions and coverage factors with old/new values.
• Open a new revision instead of modifying an approved budget.
• At the publication gate, re-verify the links between job, reference, budget, raw data and report revisions.

What should the technical review package show?

The reviewer must be able to go in a single chain from the published result to the raw record, the uncertainty budget and the accepted certificate revision of the reference used.

• Job and result identity, measurement time, method and environmental conditions,
• unique identifiers of the references and auxiliary equipment used,
• calibration event, certificate revision, relevant result and uncertainty input,
• measurement model, budget revision, input sources and calculation output,
• exception, quarantine, correction or impact review records,
• audit trail of the creator, reviewer, approver and publisher.

Vizyon Muayene during the assessment, pilot-test this back-tracing on an anonymized sample job: upload a new certificate and check that the old job link has not changed; quarantine the reference and verify that new assignment is blocked; update the budget template and show that the past result remains the same.