See which of your machines are working and which are parked.
Asset Utilisation Monitor compares two passes over your yards and sites and marks each unit idle or active, for the part of the fleet that has no telematics reporting. It is an early-access pilot.
The job today
The Monday utilisation call
Take the units with no working telematics box. Older machines, small plant, kit that came in with an acquisition, anything whose box has died. Their utilisation number comes from contracts and off-rent paperwork, and the paperwork says what should be true. A branch manager tells the call how many excavators are in the yard. Someone drives round at the end of the week and counts what is actually sitting there. The two lists do not always match, and nobody has time to reconcile them unit by unit.
So the decision about what to redeploy, what to sell and what to leave alone gets made on a mix of hours from the machines that report and a feeling about the ones that do not. A unit can be off-rent on paper and parked at the wrong end of a yard for weeks. Another can be on rent in the system and idle on a customer's site. Both look fine in the report. Dead iron stays on the books until the annual fleet plan, when somebody finally asks why the branch has so many of them.
What this changes
A weekly picture of the yards and sites you name, with each unit it can read marked idle or active from the imagery, so the call starts from what is on the ground.
What you get
What comes back each week
During the pilot it covers the yards and sites you choose, not the whole fleet.
2.1Map layer
Idle and active map layer
One layer per location, each readable unit marked idle or active for the latest pass. It is meant for GIS or a map viewer.
2.2Change log
Weekly change log
Per unit location: what moved, what stayed put, and what changed since last week's pass.
2.3CSV
Flagged coordinates
The idle units as a CSV of coordinates, so they can be matched against your asset list by whoever owns that list.
2.4Per-yard summary
Yard-level utilisation rate
The share of units read as active at each yard or site, worked out from the same calls. It is a proxy from two pictures and not a utilisation figure from the machine.
How it works
Draw your yards and sites
You send the boundaries of the yards and sites to cover. Polygons, a KML, or a list of addresses we outline with you.
We pull a pass every week
The pilot area is imaged by VHR satellite or aerial pass each week, when the sky allows.
Position and disturbance are compared
Each unit's position and the ground disturbance around it are compared from one pass to the next. A unit that has not moved and has no fresh disturbance is read as idle.
The layer and CSV arrive
The idle and active layer and the flagged CSV come to you after each pass.
Where it fits in your workflow
Before the Monday call, not after
Use it next to telematics. Units that report keep reporting, and the imagery covers the gap around them. The list of idle units is a prompt for the regional fleet manager to ask the branch about specific machines, to move something to a yard where it would rent, or to put it on the sale list. It does not tell you the model, the operator or why a unit is idle.
Limits
Weekly, not live
This is a comparison of passes a week apart or more, so it is never live tracking. A machine that leaves and comes back between two passes will not show.
Cloud and night
Cloud delays a pass. Night and heavy overcast give no read. A yard with no clear image that week comes back without a call, not with a guess.
Machine footprints, not model badges
At 0.5 m a pixel is large. A big unit shows as a footprint; a small one, such as a light tower or a compressor, may not be seen well enough to call. Nothing here tells one make or model from another.
A moved machine can look idle
A machine shifted just before capture, or left running in place, can be misread. Idle and active are a proxy, not a meter reading.
Not a replacement for GPS
Units with working telematics should keep using it. This covers units that do not report.
No accuracy figure
Nothing on this page states how often the read is right. Check it against your own yard counts during the pilot.
Who it's for
For
- Fleet ops and regional fleet managers at rental companies with units that have no telematics.
- Teams deciding which units to redeploy, put off-rent or sell.
Not for
- Live tracking or theft recovery.
- Identifying make, model or operator.
- Fleets where every unit already reports reliable hours.
- A per-machine utilisation figure to bill against.
Questions before joining the pilot list
Does this replace our telematics?
No. Units that report should keep reporting. This covers the ones that do not, or whose data you do not trust.
Is this real time?
No. It compares passes, so you see a weekly picture at best. Cloud can push a pass later.
Can it tell me what a machine is?
No. It tells you whether a unit looks idle or active, not its model or who is operating it.
How do we check it against our own records?
Choose a yard where you already know what is parked, and compare our idle and active calls with your own count. Judge for yourself whether it is good enough to plan with.
What resolution does it need?
VHR imagery at 0.5 m or finer. That shows larger machines as footprints. Small units may not be readable.
What do we have to send?
The outlines of the yards and sites you want covered. You do not need to send your asset list, though matching against it is the next step on your side.
Will it load into our systems?
The output is a map layer and a CSV of coordinates. We do not write into your rental or telematics system.
Who owns the results and the imagery?
Ownership and licence terms for the deliverables and the imagery are set out before a pilot starts. If your legal team needs them early, ask.
How is a pilot priced?
We scope it for your pilot area, and there is no number on this page.
See your own yards.
Tell us which yards and sites you would put in a pilot. We will say whether weekly passes over them are realistic.
Join the pilot list