Turn owned hours into earning hours — cut idle, lift utilisation and close availability gaps across trucks, dumpers and machines. A machine that is powered and paid for is not the same as a machine that is earning.
By converting powered, paid-for hours into earning hours — separating idle from working, lifting utilisation of available assets, closing availability lost to parts-wait, and benchmarking each unit against its identical twin. Utilisation is not a location question; GPS shows where an asset is, not whether it earned.
A dot on a map shows where a machine is. It cannot tell you whether the engine was earning or idling, whether an available asset sat unbooked while a sister site hired one in the same week, or whether a rig is running four minutes slow on every cycle. Utilisation is an engine-hours, availability and cycle question. Improving asset productivity is a question that needs a stack to answer.
Only one of the six is visible on a tracking map. That is why fleets that buy a GPS tracker and stop there recover a fraction of what is actually idle. Scroll the six — the ledger keeps score.
A 100-tonne rigid dumper — one of forty — idles 2 h 40 m a shift in the crusher queue, engine on, wheels still. Invisible unless idle burn is separated from working consumption, which needs engine state, not a tracking pin. · mining
Idle burn separated from the hours the dumper actually earned.
An excavator works 3 of 10 shift-hours on Site 6 while Site 9 hires one in on spot the same week. Availability is there; nobody could see it across sites to redeploy it. · construction
One machine's shift — 30% earning, the rest sat idle while a sister site paid spot rates.
A haulage truck runs the return leg empty — a leg that was bookable. The asset is moving and burning diesel while producing nothing. GPS is already in the OBD device, so it needs no separate tracking product. · transportation
Laden out, empty back — a return leg run for free.
North-bench haul cycles run 4 minutes over the best rig on the same bench. Four minutes × 38 cycles a shift × 40 rigs is a shift's worth of production lost — and no one sees it without benchmarking each unit against its identical twin. · mining
A face shovel is down 72 hours — 50 of them the part arriving, not the repair. And the eleven trucks it feeds queue idle behind it. At fleet scale a stalled feeder asset stops the units downstream too. · mining
A bank of site DG sets runs with no per-set, per-site baseline to manage to. Without a benchmark there is nothing to fall from — so drift never registers as a loss. · infrastructure
Per-set utilisation scatters with no line to manage against — the loss is real but unnamed.
One of these six is visible on a tracking map — the empty return leg, about ₹42 lakh. The other ₹92 lakh (idle-vs-earning, unbooked availability, cycle drift and parts-wait) lives in engine-hours, utilisation and availability data. At eight machines a supervisor sees this by walking the yard; across 300 assets and 9 sites, no human can. That is the entire argument for running utilisation as a programme, not a pin on a map.
The recovery is split by the product that earns it — so you can decide what to deploy first.
Each one answers a different part of "did this asset earn its hour?". Deploy them in the order your utilisation profile demands — the calculator above tells you which. GPS is built into the OBD device, so there is no separate tracking product to buy.
Utilisation, availability and redeploy signals per asset, per model, per site — the identical-twin benchmark that makes drift visible and moves an idle machine to where it earns.
Engine-hours that separate idle from earning, plus built-in GPS for route and dead-running context. The signal that turns 'switched on' into 'producing'.
Puts a litre — and a rupee — on idle time, so idle stops being a soft metric and becomes a cost line with an owner.
Keeps cycle discipline — the operator habits behind a rig that runs slow on every cycle or lets a machine sit warm between loads.
Each product you add does not just close its own leak. It makes the ones below it more accurate — because it removes an explanation for a missing earning hour.
Utilisation and availability per asset, per site. You can finally see the machine that sat unbooked while a sister site hired one in.
Engine-hours split powered time into working and idling, and GPS rules the empty return leg in or out. 'Available' becomes 'actually earning'.
Idle burn in litres puts a rupee on every stationary hour, cycle drift benchmarks each rig against its twin, and the signal becomes a redeploy decision.
Utilisation is not a switch. It is a programme with a sequence — and the sequence matters, because each phase makes the next one measurable.
OBD and sensors across trucks, dumpers and machines. Engine-hours and idle-vs-working surface immediately — a machine switched on but stationary is not ambiguous.
Per-model, per-site utilisation and availability baselines — the identical-twin benchmark that lets cycle drift register as a loss for the first time.
Unbooked availability and cycle drift become redeploy and coaching actions across sites — the leak becomes a decision, not a report.
Asset utilisation is the share of an asset's powered, available hours actually spent earning — moving freight, cutting a face, lifting a load. A truck or machine can be switched on, fuelled and visible on a map yet earn nothing. Utilisation measures earning hours against owned hours, not location.
By converting powered, paid-for hours into earning hours: separate idle from working, lift utilisation of available assets, close availability lost to parts-wait, and benchmark each unit against its identical twin. This needs engine-hours, utilisation and availability data working together — not a tracking pin.
Only partly. A tracking dot shows where an asset is, not whether it earned. It can't separate idle burn from working, flag a machine sitting unbooked while a sister site hires one in, or catch a rig running slow on every cycle. Utilisation is an engine-hours and availability question, so tracking alone leaves most of the leakage invisible. GPS ships built into the OBD device rather than as a separate product.
Asset Intelligence surfaces utilisation, availability and redeploy signals. Vehicle Intelligence (OBD) separates idle from earning through engine-hours, with GPS built in. Fuel Monitoring quantifies idle burn in litres. Driver Behaviour keeps cycle discipline. Together they turn owned hours into earning hours.
