Asset utilisation rate
Asset utilisation rate explained: the formula, and the four ways it misleads
Asset utilisation rate is the share of an asset's available time or capacity that was actually spent doing productive work, calculated by dividing hours or units of real output by the hours or units available in the same period. It answers one question only: is this equipment earning, and how much of the time.
For field service
Know what the job needs before the van rolls
Venta Capture, a product of VentaVid, lets the customer show you the fault first, so the engineer arrives with the right part or does not need to arrive at all.
Spelled utilisation across the UK, Europe and Australia, utilization in the US. Also called equipment utilisation, plant utilisation, or fleet utilisation depending on what is being counted. It is an equipment metric, and confusing it with the people equivalent is the first trap.
How is asset utilisation rate calculated?
Three forms are in common use, and they answer different questions.
- Time-based. Productive hours divided by available hours, times 100. The default on mobile plant and vehicles.
- Capacity-based. Actual output divided by rated output. Standard on production lines, where a machine can be running and still under-loaded.
- Financial. Revenue or billable hours generated per asset against what the asset could theoretically generate. The version a hire company reports to its board.
The denominator is where every argument starts. Available hours can mean the calendar, the shift pattern, the hire period, or the shift pattern minus planned maintenance. Each choice moves the answer by a wide margin, so a utilisation figure quoted without its denominator is a number nobody can use.
A worked example: one excavator, two defensible answers
A 20-tonne excavator is on site for 22 working days at 10 hours a day, giving 220 available hours. The engine-hour meter reads 141 hours, so utilisation is 64 percent. Then the telematics splits those 141 hours: 96 hours of working time and 45 hours of engine idle. Productive utilisation is 44 percent. Both numbers are correct, and they support opposite decisions about hiring a second machine.
Asset utilisation and availability are not the same number
Availability asks whether the asset could run. Utilisation asks whether it did. A machine sitting serviced, certified and ready in a compound scores perfectly on availability and zero on utilisation, and reporting only the first one is how fleets end up larger than the work requires.
The distinction is formalised in Overall Equipment Effectiveness, where availability, performance and quality are multiplied rather than averaged. Seiichi Nakajima set the original world-class OEE target at 85 percent, made up of 90 percent availability, 95 percent performance and 99.9 percent quality. Three strong-looking numbers that multiply out to a considerably less comfortable one.
How asset utilisation rate gets misread
- Availability counted as use. Engine hours, ignition-on time and "allocated to a job" are all proxies, and all three inflate the figure. An excavator with its engine running while the operator waits for a delivery is utilised on paper and idle in reality.
- Seasonal fleets judged on annual averages. Gritters, harvesters, holiday-peak vans and flood-response pumps are supposed to sit still for most of the year. Their annual utilisation is meaningless and their in-season utilisation is the only figure worth reviewing. Averaging across the year makes the case for disposing of exactly the asset you cannot do without in February.
- Idle confused with standby. These look identical in the data and mean opposite things. Idle is waste: a machine burning fuel and hours while nothing is achieved. Standby is deliberate capacity held for a purpose, whether that is a breakdown cover unit, a contractual response time, or a spare. US Department of Energy figures put typical long-haul truck idling at around 1,800 hours a year, consuming roughly 1,500 gallons of diesel (Alternative Fuels Data Center). Those hours often sit inside a reported utilisation figure as though they were work.
- Fleet averages hiding the tails. A 70 percent fleet average can be six machines at 95 percent and four at 32 percent. The average tells you nothing. The distribution tells you which four to move or sell.
- Chasing the number for its own sake. Push utilisation high enough and you remove all slack, so the first breakdown or urgent job cascades. High utilisation on ageing equipment also accelerates the failures that will take it out of service entirely.
How it differs from technician utilisation
The two get used interchangeably in operations meetings, and they measure different things entirely.
- Asset utilisation counts the machine. Hours or capacity the equipment spent producing, against what was available.
- Technician utilisation counts the person. Paid hours booked to customer work, against total available hours.
They can move in opposite directions on the same site. A workshop can run 90 percent technician utilisation while its machines sit at 40 percent, because the technicians are busy repairing the machines. Reading one as a proxy for the other produces confident decisions in the wrong direction.
Reading the number properly
Utilisation is a fleet-sizing and allocation metric, not a productivity score. It answers whether you own the right amount of equipment and whether it is pointed at the right work. It says nothing about whether the work was done well, and nothing about the condition of the asset doing it.
Read it against three things: the maintenance record, so you know whether low utilisation is demand or downtime; the fleet management cost per hour, because a poorly utilised asset carries its full fixed cost regardless; and the compliance file on the plant and machinery itself, since a machine that cannot lawfully work is not an availability problem you can schedule around. Most of the recoverable hours are found in the gap between engine hours and working hours, and the only reliable way to see that gap is to instrument it through fleet telematics rather than infer it from a timesheet.
