Calibrationoverdue gauges can't write to the batch record. Full stop.
Calibration is not a spreadsheet exercise. V5 keeps a register of every gauge, scale, probe and instrument; tracks calibration intervals; stores the vendor calibration cert with as-found / as-left readings; and enforces the rule that matters — an out-of-cal device is blocked from writing to any regulated record. Not warned. Blocked.
Calibration is a live signal, not a binder.
Follow SC-12 — a floor scale on Suite 2 — through a full year. Drift is plotted, not discovered. The moment it leaves tolerance, the eBMR refuses the value.
SC-12 · range 0-60 kg · ± 5 g · NIST class F
A scale that's overdue doesn't exist.
When an instrument's calibration expires, V5 doesn't email the metrology lead and hope. It removes the instrument from the kiosk's drop-down. The operator literally cannot select it. No bypass, no override, no "we'll do it next batch."
Every instrument is on a visible countdown.
The operator can't accidentally pick a dead scale.
The instrument list at the kiosk filters itself. Overdue and under-investigation instruments fall off the list. If a fixed recipe step is pinned to a now-dead instrument, the batch auto-pauses with a clear "blocked by metrology" reason.
"Was this scale in cal when batch B-44871 was made?" One query.
When an instrument fails its periodic cal, V5 walks back through every batch that used it since its last successful cal — and surfaces them as a triage list. No spreadsheet archaeology, no "let me get back to you."
Metrology is a gate, not a memo.
Curious how V5 actually keeps instruments honest?
Where AI actually earns its place.
AI reads the calibration register the same way a metrology lead would — watching drift trends across devices and getting ahead of the due date instead of reacting to a blocked kiosk.
- 01
Drift trend flagged before it's overdue
By comparing as-found and as-left readings across a device's calibration history, AI flags a gauge or scale that's drifting faster than its peers, so the asset owner can shorten the interval before the device gets blocked mid-run.
- 02
Vendor cert data extraction
When a vendor calibration cert PDF is uploaded, AI reads the as-found/as-left values, tolerance and next-due date straight off the document and pre-fills the register entry for the technician to confirm.
Removes the manual transcription step from every cert intake.
- 03
Due-soon prioritisation on the daily brief
AI ranks the due-within-7 list by which devices sit on the busiest lines or the tightest-tolerance formulas, so the maintenance tech tackles the calibration that would cause the most disruption first.
AI never marks a device calibrated, never lifts the block on an out-of-cal instrument, and never edits a vendor cert — only a completed calibration event recorded by the technician clears the gate.
The instrument record decides what can write to a batch.
MES, eBMR, maintenance, QMS, audit and analytics all read the same cal status — so an overdue instrument can't quietly slip a value into a release.
Wondering how V5 calibration plugs into the rest of your stack?
Just ask V5 — it knows the product cold.
Pick a question or type your own. V5 answers grounded in how calibration management — gauges, scales & instruments, with hard-gates on overdue | v5 ultimate actually behaves on the floor.
The rest of the platform this plugs into.
V5 isn't a bolt-on. Every module shares the same data, the same audit trail, the same operator. Pick where to look next.
MES
Operator-led execution: scan-gated dispense, step-by-step kiosk, equipment + scale integration, live yield. Built for regulated process & discrete manufacturing.
WMS
Receiving, putaway, transfers, cycle counts, picks, pack & ship — all lot-aware, bin-accurate, FEFO/FIFO-enforced and barcode-driven.
QMS
Built-in QMS: deviations, CAPA, supplier scorecards, in-process AQL, release-by-exception. Aligned with 21 CFR 211/820, ISO 13485 and 111.
Got questions, or want to see it on your shop floor?
Ask V5 — our code-aware assistant — or spin up a workspace. Both are free.