Operations and Evidence

Reconcile the operational evidence

The operations workspace brings together instrument use, supplier submissions and configured integration events. It helps the Calibration Coordinator see whether expected evidence arrived and whether external handoffs were acknowledged. A local record changing state cannot prove that another system accepted the same information, so receipt, application and acknowledgement remain distinct facts.

InstrumentUseRecords connects the instrument to an external inspection, test, lot or job. The actual use time remains separate from the import time. A delayed upload therefore preserves when the measurement happened instead of making the event appear to occur after a new calibration or release decision.

Make imports repeatable without erasing exceptions

A configured connector supplies a source-system identifier, stable event key and payload digest. Repeating the same event returns its prior outcome. Reusing the key for changed data is a conflict that requires investigation, not an instruction to silently replace an earlier use or certificate.

• Reconcile imported events to stable instrument identities.
• Quarantine unknown instruments, incompatible ranges and conflicting payloads.
• Keep failed events visible with a reason and a safe retry path.
• Preserve historical invalid use for assessment rather than dropping it.
• Limit connector authority to the configured tenant and operating scope.

Integration Exceptions exposes failed and quarantined events. The operations team can distinguish a transport problem from a business-data problem. Retrying a delivery should not duplicate instrument use, create another approval, or generate a second quality case with no link to the first.

Use reports that retain their meaning

Calibration Due Exposure counts current approved plans and their unresolved obligations. Certificate Review Backlog concerns review work, while Hold and Release History concerns service restrictions. Combining these into a single completion percentage would hide the difference between evidence received, evidence accepted and an instrument authorized for use.

As-Found Drift History compares like measurement points and units with their method context. A changed procedure or operating range can affect whether observations are comparable. The report preserves that context instead of presenting every numeric difference as instrument drift. Interval Decision History records the evidence behind schedule changes and retains rejected proposals.

Prepare an evidence package with controlled access

An authorized evidence export should include the relevant instrument identity, plan revision, calibration order, certificate version and decision history. Investigations may also require use records and external acknowledgement references. Scope the package to the request and retain the source identifiers so a reviewer can follow each item back to its controlled record.

Auditor access is read-only and tenant scoped. File download and export permissions require the same server-side checks as ordinary record access. The app must not leak an external customer’s or another site’s documents merely because the caller knows an attachment address. Configure evidence retention, export access and legal preservation rules around your organisation’s record policies.