The Machine With No Hour Meter
A generator is serviced every 250 running hours. A vehicle at 10,000 kilometres. A compressor on its duty cycle. Every one of those is a number the machine keeps and the asset register does not, so the only schedule the register can offer you is a calendar.
Ask a plant manager when a generator is next due and they will not tell you a date. They will tell you a number — hours on the clock, and how far off it is.
Ask an asset register the same question and it can only answer in dates, because a date is the only thing it holds. That mismatch is small on paper and it is the whole of preventive maintenance.
Two ways a machine becomes due
By time: it has been six months, so it is due. By use: it has run 250 hours, so it is due. Most manufacturers specify both and mean whichever arrives first, and for anything that works hard the usage figure is nearly always the one that arrives.
A register that holds only dates can express the first and not the second. It can tell you a machine was last serviced in March. It cannot tell you it has done 900 hours since.
A calendar knows how long you have owned a machine. It has no opinion at all about how hard you have worked it.
Which produces the two characteristic errors, and they are expensive in opposite directions. The machine that sat idle all quarter gets serviced on schedule for no reason, at full cost. The machine that ran double shifts through the same quarter goes to its service date having done twice the work the interval assumed, and the interval existed precisely to stop that.
What the register does hold, which is more than you might expect
It is worth being fair about this, because the absence is specific rather than general. An asset here has a custodian by name, a movement history with a time, a location and a signature, and a record of when it was last physically verified. It knows whether you own it, lease it or are holding it for somebody else, and that distinction is enforced rather than decorative.
Maintenance is present too — as a movement. You can record that a machine was sent for maintenance and that it came back, with who sent it, when, and where it went. That is a genuine maintenance history, and for a compliance file or an insurance claim it is most of what you need.
What none of it does is tell you that something is due. A history answers "what happened to this machine". A schedule answers "what should happen next", and that is a different question with a different input.
What happened, and to which machine
Movements with an actor, a time, a place, a signature and a GPS position. Sent for maintenance and returned from maintenance are recorded events with a full trail behind them.
Who is holding it right now
Named custody, transfer history, and a last-verified date, so the question "where is it and who has it" has an answer that does not depend on anybody's memory.
What is due next, and on what basis
A service interval expressed in hours, kilometres or cycles, a reading captured against the machine, and a due list computed from the two.
Why the Gulf makes this obvious faster
Because so much of the plant here is rated by use rather than by age. Standby and prime generators on sites where the grid is a convenience rather than a guarantee. Chillers and compressors running against ambient temperatures that make duty cycle the governing figure. Vehicle fleets covering distances that make a six-month interval meaningless in either direction.
On that kind of plant, a calendar schedule is not a rough approximation of the right answer. It is a different answer that happens to be expressed in the same units as a date.
Running it on a calendar without pretending otherwise
Four things that work today
- Set the calendar interval from your actual duty, not from the manual. If a machine reaches 250 hours in seven weeks on your sites, the useful interval is seven weeks, and it is a decision you make once rather than a reading you take weekly.
- Keep the meter reading where the machine is — a log sheet on the unit, filled in by whoever runs it. It is the reading that matters and the register is not where it has to live.
- Record every service as a maintenance movement, so the history is complete even though the trigger was manual. The history is the half you will be asked for.
- Review the interval quarterly against the log sheets. A machine that keeps arriving at its service date well past its hours is telling you the interval is wrong, and that is a fifteen-minute conversation with a real answer.
The fourth is the one that actually closes the loop. A calendar interval chosen from observed duty and revisited quarterly gets you most of the way to a usage schedule, using paper for the part the system does not hold.
Four questions for anybody selling you an asset register
Can I store a meter or odometer reading against an asset?
What you will hear
A quick yes, then a pause.
How to read it
Ask where it goes and what reads it. A number in a free-text note is storage, not a reading — the difference is whether anything can compute a due date from it.
Can a service interval be set in hours or kilometres rather than months?
What you will hear
Varies enormously.
How to read it
This is the question. A register that can hold both bases and take whichever arrives first is built for plant. One that offers only months was built for furniture and office equipment, which is most of them.
What is on the "due this week" list, and what put it there?
What you will hear
A description of a report.
How to read it
Ask to see it with a machine on it. A due list that a person maintains by hand is a spreadsheet with a login, and you should price it as one.
If a machine is idle for a quarter, does its next service move?
What you will hear
Usually no.
How to read it
The cleanest single test of whether a schedule is usage-based. If nothing moves, the schedule is a calendar wearing maintenance vocabulary, and you will pay for services you did not need.
The short version
If your plant is rated in hours, kilometres or cycles, the question to ask an asset register is not whether it does maintenance. It will say yes and it will be telling the truth about history. Ask what it can put on a due list and what number it computed that from. Ours computes from dates, holds no readings, and keeps a complete record of every service once it has happened — which is a good history and a calendar schedule, and on hard-worked plant those are not the same product.
What AWRA OpsHub does today
- Maintenance as a recorded movement — sent and returned — with the actor, the time, the destination, a signature and a GPS position on the movement.
- Named custody with full transfer history, so who holds a machine and who held it before is answerable without asking anybody.
- An ownership basis on every asset — owned, leased or held for a third party — validated everywhere an asset is created or edited.
- A last-verified date per asset, so the physical existence of a machine has a freshness figure rather than an assumption.
- Asset creation from stock, so a spare that becomes a machine carries its cost across rather than being keyed again.
More we can add to your workspace
- A meter, odometer or cycle reading stored against an asset, captured on a schedule and kept as a series.
- Service intervals expressed in hours, kilometres or cycles, taking whichever basis falls due first.
- A due-and-overdue list computed by the system, rather than assembled by a person from records and log sheets.
- Work orders, turning a due item into assigned work with parts, labour and a completion record against it.
- Warranty and service-contract cover keyed to usage, so a machine approaching its covered limit is visible before it passes it.
Where we point you to a specialist
- Reading a meter is a physical act on a site and we would not model it as anything else. A reading typed by the person standing at the machine is the honest input; inferring hours from anything else would produce a number that looks authoritative and is estimated.
- What interval a given machine should run on is the manufacturer's specification and your engineer's judgement about your duty. We would build the schedule you specify and would decline to publish intervals of our own.
- Connecting to telematics or a machine controller to take readings automatically is a project on your equipment and your network. We would scope the register side; the hardware and its data rights stay yours.
Usage readings, usage-based intervals, a computed due list and work orders are one coherent piece of work we can scope and quote on.
Three, and they arrive in this order for a reason
The reading has to exist before an interval can consume it, and an interval has to exist before a due list means anything.
Readings against an asset
A meter, odometer or cycle count captured with a date and the person who took it, kept as a series rather than overwritten — so the rate of use is visible as well as the current figure.
Intervals in hours as well as months
Both bases on the same asset, falling due on whichever arrives first, which is how manufacturers actually specify them and how nearly no register expresses them.
A computed due list, and work orders behind it
What is due this week and what is overdue, produced by the system rather than by a person with a folder — then turned into assigned work with parts, labour and a completion record.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. If any of your plant is rated in hours rather than months, the first item is where this starts.
Talk to us about plant and equipmentCheck one machine against its own clock
Take the hardest-worked machine you own, read its meter, and compare it to what it had done at its last service. If that number surprises you, your maintenance is running on a calendar and the machine is not.
Talk to us about asset management