‹ Insights · Part 2 of 3
From data to dollars: utilisation, servicing and billing from real machine hours
Every fleet manager I know has sat in a meeting where someone asks, "So what is all this data actually worth?" It is a fair question. Telematics has been sold for years on dashboards and maps. The honest answer is that the value is not in the dashboard. It is in three decisions the business makes every week, and how much better those decisions get when they run on real machine hours.
1. Utilisation: know what earns
Utilisation is the number that decides whether a fleet makes money. When I ran national fleet strategy at Energy Power Systems, across power generation, temperature control and compressed air solutions, the hardest part was never buying the right assets. It was knowing, week to week, which ones were working and which were costing us money to own.
Without live data, utilisation is usually measured by what is on hire, not by what is actually running. A machine can be on hire and barely used, or sitting in a yard when another branch is short. Real hours close that gap. They show which categories deserve more capital, which assets should move, and which should be sold before they lose more value.
A simple example: once we could see recorded hours across the fleet, it became clear that some categories looked busy on paper but ran very few hours on hire, while others were regularly turning customers away. That changed where the next round of capital went. Instead of buying more of what we already had, we put the money into the assets customers were actually asking for, and moved idle units to the branches that could keep them working.
The value is not in the dashboard. It is in the decisions.
2. Servicing: on hours, not the calendar
Most service schedules are built on time or on estimates. That means some machines are serviced too early, which wastes labour and parts, and others too late, which risks a breakdown on a customer's site. Breakdowns on hire cost far more than the repair: there is the swap-out, the lost hire days and the damage to the relationship.
When servicing runs on the hours a machine actually recorded, and fault codes arrive before the operator rings, the workshop plans its week instead of reacting to it. I saw this first-hand when we brought early connected-asset technology into the fleet. The machines did not change. The timing of the work did.
3. Billing: charge for what was used
This is the one that surprises people. In many rental businesses, billing still relies on dockets, estimates and the customer's memory of how long a machine ran. That creates disputes, write-offs and slow payment.
When billing draws on recorded hours, the conversation changes. The invoice matches what the machine reported. Disputes get shorter. Usage-based pricing becomes possible, which many customers now prefer. And cash arrives sooner because there is less to argue about.
Putting a number on it
You do not need a large business case to test this. Pick one category of assets and track three figures for a quarter:
- Average utilisation, measured on recorded hours rather than hire days.
- Unplanned breakdowns on hire, and what each one cost.
- Billing disputes or adjustments, and their total value.
Then compare them with the same quarter before you had joined-up data. In my experience, the gains in at least one of these three are usually enough to fund the rest of the rollout.
The bigger point
Connected data is not an IT project. It is a commercial one. The businesses that get the most from it are the ones where the fleet manager, the workshop and the finance team all look at the same hours and make decisions from them. That is where the dollars are.

Wade Bailey is General Manager, OEM & Rental at Inauro, with 30+ years of leadership across construction, mining, technology and power generation. More about Wade ›
Want to put a number on your fleet data? Let's talk it through.
Start a conversation