The problem
Calibration lives in a spreadsheet with red cells and a binder in a filing cabinet. When the auditor arrives, you go hunting.
What it does
- Gauge register with calibration intervals and due-date alerts
- Full calibration history with attached cert PDFs
- Per-user access levels (basic, advanced, admin)
- Daily dashboard of what is overdue
- Optional vending stations that enforce access at the hardware
Who it's for
QA managers, metrology leads, and anyone responsible for passing an audit.
In the demo: Scan a gauge for its cal status, due date and history. Show the daily due-date dashboard, then a vending station refusing a basic-tier user.
Works with
Works on its own - no other module required.
Common questions
What does it replace?
At worst nothing: calibration sits in manual filing, or in a third-party system that does not talk to anything else. Gauges replaces all of it with one register that tracks calibration and history.
Who is it for, and do I actually need it?
Everyone who uses or manages gauges and measuring equipment. If you would ever have to go hunting for a gauge's calibration status or its last cert, you need it.
Does it need another module?
To simply manage gauges, the base module is enough. Add a Terminal or the Mobile add-on and users can also vend: take and return gauges with access enforced.
How does it make the rest of TRS better?
Users stop looking for gauges, and the equipment starts to connect with the rest. The same take and return habit, the same floor screens and the same assistant that run tools now run gauges too.
We're not ISO certified, why bother?
Audits are only one reason. Even without ISO, an out-of-tolerance gauge scraps parts and a missing one stops a job. The register earns its place the first time it flags an overdue gauge or finds one you would have spent ten minutes hunting for.
We can do without it.
Until the cert nobody can find holds up an order, or the gauge everyone assumed was fine turns out overdue. The register makes that a non-event.