Calibration management is the program that keeps every measuring instrument in a plant, gauges, scales, thermometers, pressure transmitters, torque tools, verified against traceable standards on a defined schedule, with records that survive an audit. It is the quiet infrastructure under quality: every acceptance decision, process setting, and compliance claim is only as good as the instrument that measured it.
When an instrument comes back out of tolerance, the finding is retroactive: every measurement it made since its last good calibration is now suspect. The program must answer: what did this instrument accept, adjust, or release during that window, and does any of it matter? This is reverse traceability, from instrument to decisions, and it only works if usage was recorded as it happened.
A pressure transmitter on a sterilizer is found reading 0.4 bar low at its annual calibration. Its last good calibration was 12 months ago; the process specification allows 0.2 bar of error. The register shows it served one autoclave; batch records show 214 sterilization cycles in the window. Because cycle records captured the transmitter ID, quality can pull the redundant temperature data for those 214 cycles within hours and demonstrate lethality was achieved on all but 3, which used a marginal recipe; those 3 batches are quarantined for review. Total exposure: 3 batches, resolved in two days. Without instrument-to-batch linkage, the honest scope would have been all 214, and in regulated industries that word is recall. Calibration comparisons like calibration versus adjustment and measurement studies such as gauge R&R versus calibration cover the finer distinctions; the OOT chain is where they all cash out.
Calendar intervals are simplest; usage-based intervals (cycles, hours) fit instruments whose wear tracks activity; and drift-history adjustment tunes both over time. In GMP and similar regimes (see IQ/OQ/PQ), interval changes need documented rationale, evidence in, decision out.
Fabrico is not a metrology laboratory and does not perform calibrations. It runs the management layer: the instrument register inside the asset structure, calibration due dates as preventive schedules with certificates attached to history, out-of-service status visible at the point of work, and instrument usage captured on work orders so the OOT investigation starts from records instead of memory. EU-built, with EU data residency, which matters when those records are the audit trail.
Any instrument whose reading feeds a product acceptance, process control, safety, or compliance decision. Indication-only devices can be designated reference-only and excluded, but that designation must be explicit and labeled, silence creates shadow instruments.
Yes, with evidence: consecutive as-found-in-tolerance results support extension, and regulated environments expect a documented rationale. The symmetrical rule is less popular: repeat OOT findings must shorten the interval or retire the instrument.
Calibration compares the instrument to a standard and documents the errors, with adjustment if needed. Verification is a pass/fail check that the instrument still meets its specification. Many programs verify frequently and calibrate at longer intervals; both need records.
Want calibration schedules, certificates, and instrument usage on one asset timeline? Book a Fabrico demo to see a field-ready CMMS carry your measurement traceability.
Login
Blog