How do you track the calibrations of your measuring instruments?
The right workflow follows a simple logic: instrument → planning → internal or external calibration → results → validation → certificate → return to service → next due date. The software must make this chain readable for metrology teams and for the other actors in the information system.
Each event should keep its date, the operator or laboratory, the result, the certificate, the cost, the duration of immobilization, and the status. That is what keeps tracking from being reduced to a simple date table.
How do you define the calibration interval and next due date?
An annual interval is not universal. It depends on criticality, usage frequency, usage conditions, maintenance, observed drift, and result history.
The recommendations ILAC-G24:2022 / OIML D 10:2022 specifically address determining and reviewing calibration intervals. Useful software must therefore turn history into an actionable decision, not just store yet another date.
The right model is simple: history → drift trend → interval reassessment → next due date. That is what avoids intervals frozen by habit.
How do you automate calibration due dates?
Automation must stay concrete: D-90 to anticipate, D-30 to plan, D-7 to alert, then an adapted status when the due date is overdue. The workflow must also manage the responsible people and the laboratories involved.
The system can then plan immobilization, return-to-service actions, and replacement instruments when equipment must leave the base during the intervention.
How do you manage calibration certificates and results?
Each intervention links to the instrument its calibration certificate, results, uncertainty, observed errors, any adjustment, the laboratory, the date, the decision, and the next due date.
The software does more than archive PDFs. It structures successive results to visualize how an instrument evolves and detect drift: for example 2024: +0.02 → 2025: +0.05 → 2026: +0.11.
This logic is consistent with ISO/IEC 17025, which frames laboratory competence and the reliability of the associated results.
What should you do when calibration reveals an instrument out of tolerance?
An out-of-tolerance result should trigger a block on status, followed by an impact analysis. The system identifies potentially affected measurements before letting the team decide the next step.
The next logical steps go from adjustment or repair to a new calibration, then return to service. When relevant, a connection to the MES or QMS makes it possible to trace batches or checks performed since the last valid result.
What does ISO 10012:2026 change for metrology tracking?
Published in February 2026, ISO 10012:2026 replaces the 2003 edition and reinforces the idea of a measurement management system capable of supporting the reliability of results.
The software can support that organization by structuring equipment, responsibilities, evidence, history, and actions, without pretending that using software alone is enough to ensure ISO compliance.
How do you connect calibration tracking to your MES, CMMS, or QMS?
The MES provides the view of batches and instrument usage. The CMMS connects equipment and maintenance. The QMS keeps track of non-conformities and CAPA.
You can also connect the ERP for providers, purchasing, and costs, the DMS for certificates, and the lab API to retrieve results without duplicate entry.
This is where custom development becomes relevant: it moves the useful data around without creating a new software island.
Excel, calibration software, or a custom solution: which should you choose?
Excel remains enough for a small, very simple base. Standard software becomes relevant when processes are already structured and close to common market usage.
Custom development takes over when you need to manage multiple sites, special rules, deep system integrations, or workflows specific to your company.
At Koragence, the method follows a clear sequence: audit → Excel/PDF takeover → prototype → development → integrations → migration → tests → deployment.
