Fleet Management Software for Construction and Mining Fleets
Most of your fleet does not drive anywhere. It gets delivered on a low-loader, works a pit or a plot for eleven weeks, and burns diesel that arrived in a bowser. KO Fleetz is built around that: hours rather than distance, sites rather than routes, and a register that knows a breaker attachment is an asset too.
Operational reality
What makes construction & mining different
The odometer tells you almost nothing
An excavator slews all day and covers thirty metres. A dozer works a face and reads zero distance. Wear, fuel burn, service intervals and resale value all follow engine hours, and a system built around kilometres cannot see any of it.
Satellites behave badly in a hole
Signal bounces off a quarry highwall, a tower crane mast, a stack of precast. Position jitters, machines appear to teleport across a compound, and a geofence drawn tight enough to be useful fires all night for no reason.
There is no fuel card to reconcile against
Diesel arrives on site in a bowser and goes into machines by hose. No terminal, no receipt, no litres line on a statement. The delivery invoice says two thousand litres and everything after that is somebody's clipboard.
Idling is most of the day
A loader waiting on a truck, a machine left running through a break because restarting is a nuisance: it burns fuel, accrues hours that pull the next service forward, and produces no work. On the sheet it is indistinguishable from production.
Half the yellow iron is hired
Plant comes on hire for a phase and goes off hire when someone remembers. Hire charges run to the day the machine is collected, not the day it stopped being needed, and the gap between those two dates is pure loss.
Attachments walk
Buckets, breakers, quick hitches, compactors, lighting towers, generators. Real capital, no engine, no telematics port, no keys worth mentioning, and a habit of ending a phase on a different site to the one that hired them.
Cost belongs to a plot, not a journey
Commercial reporting runs by contract, phase and cost code. Plant does not make trips, so there is no trip to hang the cost on, and a machine's diesel and downtime end up in a plant department rather than on the job that consumed them.
How plant actually gets used
A machine is mobilised, not dispatched. It goes on a low-loader to a site where it will stay for weeks, and from that moment the interesting questions are all local: is it working, is it idling, is it fuelled, is anyone on this site aware it has a service due at the end of the month. Nobody is driving it home tonight. If it develops a fault, the fitter comes to the machine, and the machine is behind a hoarding on a plot with restricted access.
Fuel arrives by delivery and goes into a bowser, and the bowser goes to the machines. That single fact breaks the reconciliation model every road fleet relies on. There is no transaction to match and no odometer to sanity-check the fill against, so KO Fleetz reads what a machine consumed from its own consumption signal set against its own hours, which is the only reliable evidence a bowser-fed site leaves behind. Where a bowser is worth metering, delivered litres and dispensed litres become two counts that ought to agree, and the interesting month is the one where they do not.
Then the phase ends. The machine is either wanted on the next site, sitting on this one because nobody logged that it finished, or standing at the yard while the hire desk brings a third-party unit in for a job it could have done. That last case is the sector's most expensive routine mistake, and it is not a scheduling failure. It is a visibility failure, and it is fixed by knowing what every asset was doing yesterday without ringing a site manager to ask. KO Fleetz gives the plant desk that answer from the register itself — which site each machine stood on, whether it worked or idled, and whether its hire has run past the day it stopped being needed.
Feature mapping
Which modules matter here, and why
Not every fleet needs every module. This is what actually earns its place in this industry.
Plant servicing runs on the hour meter, and hours accrue at wildly different rates depending on what the machine was asked to do. A hydraulic breaker in a demolition week ages its carrier faster than a month of muck shifting. Undercarriage, hoses, pins and bushes are the wear story here, and none of them appear on a schedule designed around road distance.
Bowser-fed sites are the hardest fuel environment there is, because the control every road fleet leans on simply does not exist. No card, no pump terminal, no transaction. What replaces it is machine-level consumption set against machine-level hours, so a unit that suddenly needs a third more diesel for the same work becomes a question rather than a rounding error inside a site's monthly delivery.
The register has to hold things that are not vehicles. A breaker, a quick hitch, a lighting tower and a generator have serial numbers, examination dates, book values and a strong tendency to disappear, and no engine to report themselves. Owned and hired-in plant also sit side by side, and a machine's on-hire and off-hire dates are the difference between a fair charge and a month of paying for iron in a nettle patch. KO Fleetz keeps the attachment with no telematics port on the same register as the excavator that has one, each carrying the serial number, the examination date and the hire dates that decide what it costs.
Tracking here answers two questions no road fleet asks. Which of my sites is this asset standing on, given it has not moved under its own power in a month. And has it left one, at night, on a trailer, which for plant is what theft looks like. Site boundaries are the geofences that matter, and they need drawing with enough tolerance for a position that wanders when the machine is down in a cutting.
The question a plant director gets asked is never about a vehicle. It is whether the twelve machines allocated to a contract earned their keep on that contract, and whether the hire desk needed to bring in a fourteenth. Answering it needs working hours separated from idle hours, aggregated by site rather than by depot, and available before the phase ends rather than in the post-mortem.
Outcomes
What changes
- Services due on how the machine worked, not how far
- Hour meter
- The two halves of a day split on the same asset
- Working vs idling
- Utilisation aggregated by plot and phase, not by depot
- Per site
- Attachments and towers in the register, engine or not
- Serial numbers
Where a plant fleet connects
Equipment manufacturers publish hours, fuel rate, idle state and fault codes through their own machine telematics, and standardised feeds mean a mixed yard of yellow iron can arrive in one place without a tracker on every unit. Battery-powered asset tags cover the towers, bowsers and attachments that have nothing to publish. Plant hire and rental desk systems own the on-hire and off-hire dates that drive the charges. Project cost and ERP systems take hours and consumption against a cost code. Fuel suppliers provide delivery volumes. Workshop and parts distributors feed the maintenance ledger.
Explore integrationsFrequently asked questions
Usable, yes. Precise, no, and you should plan for that. Signal reflecting off a highwall or a slab arrives late and puts the fix out by metres, sometimes tens of metres. That is fine for the question plant fleets actually ask, which is which site an asset is on and whether it has left. It is not fine for drawing a boundary tight around a compound and expecting silence overnight. Draw site geofences generously, treat brief excursions as noise, and reserve alerting for sustained movement away.
By stopping the search for a transaction. Road fleets reconcile fills against a statement because a statement exists. On a bowser-fed site it does not, so the evidence has to come from the machine: tank level, consumption rate and engine hours, trended per unit. A machine burning materially more diesel per working hour than it did last month is either developing a fault or losing fuel, and both are worth a visit. If the bowser itself is metered, dispensed against delivered closes the loop from the other end.
That is the default for plant, and it is the whole point. Intervals are set against the hour meter, hours are read from the machine's own telematics or the tracker, and the platform forecasts the due point from actual accrual rather than an assumed daily average. A machine on a demolition phase will hit five hundred hours in a third of the time the yard expected, and that is precisely the case a calendar reminder gets wrong. Distance-based intervals remain available for the road-going side of the fleet.
Yes, with a clear-eyed view of the trade-off. They all belong in the register regardless, holding a serial number, an examination date, a value and a current site, because an attachment nobody has listed is an attachment nobody notices leaving. Live position needs a battery-powered tag, and those report on a duty cycle measured in hours rather than seconds so the battery lasts a year or more. You get a daily answer to where it is, not a live one. For an asset with no engine, that is usually the right bargain.
It is designed for it, because a construction register holding only owned assets describes maybe half the yard. Hired-in units are recorded with the supplier, the on-hire date and the expected off-hire, so a machine still accruing a daily charge after the phase closed becomes a flag rather than a discovery on an invoice. Assets you hire out carry the same in reverse. What KO Fleetz does not do is price the hire or raise the invoice: your rental desk system owns the commercials and should keep them.
It feeds job costing rather than performing it. Your ERP or project accounting system owns the cost code structure, the commitments and the valuation, and it should stay that way. What KO Fleetz supplies is the operational half that system has never had: working hours, idle hours, fuel consumed and maintenance spend, attributed to the asset and the site it stood on. Push that across and plant cost lands on the contract that used it. Try to make a fleet platform own your cost ledger and you will end up maintaining two.
Pick one site and one month of bowser deliveries
We will set the delivered litres against machine hours and show you how much of that fuel bought working time.