Service the machine that did the work
A generator that ran four hundred hours last month is not due at the same time as one that ran forty. QAI counts whatever your equipment counts — hours, kilometres, litres, kilowatt-hours, pressure — and lets those numbers raise the work themselves.
What a number on a dial is worth once it is written down
Five things that change when readings live in the same system as the work.
Service by what the machine did, not what month it is
Set the interval in units instead of days — every 500 hours, every 10 000 kilometres — and the service is raised when the machine gets there. The hard-worked unit comes in early, the one that sat idle stops being serviced for nothing, and both are right for the same reason.
Catch the thing that is drifting before it breaks
A reading that jumps twenty per cent in a week, or climbs faster per hour than it used to, is the machine telling you something ahead of time. QAI can watch for the change rather than the number, so you hear about it while it is still a service and not yet a failure.
The reading does the next bit for you
When a condition is met QAI raises the job — title, priority, type and the person it belongs to already filled in — notifies whoever needs to know, or calls a webhook into another system. Every automation has a cooldown, so a reading hovering on the line cannot fire the same job forty times.
Readings that actually get taken
None of it works if nobody writes the number down. Print a QR code for the meter and stick it on the machine: a technician scans it, types what the dial says, and is done in about fifteen seconds. Readings can also be captured as part of a job, and anything overdue sits on a list rather than in somebody’s memory.
Litres in, hours out
Fuel is recorded against the same hours meter it was burnt by, so you get litres per running hour instead of a fuel bill. A machine whose consumption per hour keeps climbing is a machine going wrong, and that shows up months before it stops.
What a meter can do
Any unit you count
Hours, kilometres, litres, kilowatt-hours, bar, degrees. Name the unit, set the range you expect, and say how often it should be read.
Interval automations
Fire every so many units, or once a running total is reached. Preventive maintenance measured in work rather than in weeks.
Change and rate conditions
Watch for an absolute change, a percentage change, a threshold being crossed, or the rate per hour going above or below a figure.
Limits and stalls
Warn as a reading approaches the minimum or maximum you set, or when a reading has not moved when it should have.
Three kinds of action
Raise a job, notify people, or call a webhook — each with a cooldown so one hovering reading cannot fire the same thing repeatedly.
Printable meter labels
Print a QR code for each meter so a technician scans it at the machine, and see everything overdue on one list.
Meter questions
What teams ask before they put readings into QAI.
Still have questions? Contact our sales team
Servicing equipment on what it has actually done rather than on how long it has been since last time. A generator that ran four hundred hours last month has worn four hundred hours’ worth; one that ran forty has not. Setting the interval in hours, kilometres or cycles keeps both on the right schedule, which is cheaper than servicing everything monthly and safer than servicing nothing until it stops.
Anything your equipment counts, because you name the unit yourself — engine hours, odometer kilometres, kilowatt-hours, litres, cycles, pressure, temperature. A meter belongs to an asset, so the readings and everything they set off stay attached to the machine they came from. You also set the range you expect and how often it should be read.
People record them. A technician opens the meter on their phone at the machine and types the number, usually after scanning a QR code stuck on the equipment so there is no hunting through a list. Readings can also be captured while a job is being done, and if you already keep readings in a spreadsheet you can import them in bulk.
You set a condition on the meter and say what should happen. When a reading meets it, QAI creates the job already filled in — the title you wrote, the priority, the job type, who it goes to, and whether a signature is wanted at the end. The result comes back with the reading, so whoever recorded it sees straight away what it raised.
Yes, several ways. Warn as a reading approaches the minimum or maximum set on the meter, watch for a threshold being crossed, or fire on the change itself — an absolute rise, a percentage rise, or a rate per hour going above what is normal. Meters also show how far the current reading is from the next automation, so you can see it coming.
Yes. Every automation carries a cooldown in hours. Once it fires it will not fire again until that time has passed, which is what stops a reading sitting on the threshold from raising the same job repeatedly.
The meter knows when its next reading is due from the frequency you set, and anything past that is flagged as overdue so it appears on a list instead of being forgotten. The history keeps the previous value and the change between readings, so a gap stays visible rather than being quietly averaged over.
Yes, if litres are captured at the same time as the hours reading. QAI works out litres per running hour over whatever window you choose, alongside total litres, hours run and the number of fills. That per-hour figure is the useful one — a machine burning steadily more fuel for the same work is telling you something long before it fails.
Put a number on when the next service is actually due
Start free, put a meter on one machine, and let the reading do the rest.
From R216 per user per month · 14-day free trial · No credit card
