- 4 min readproduct
The machine that left at 2am
Presence and last-seen won't paint a live dot on a map — and shouldn't pretend to. But the moment a tag stops being heard, and the last hub that heard it, is a record worth having. Here's what that boundary honestly catches, and what it doesn't.
Read → - 5 min readproduct
You don't have a 40-machine fleet
The asset list says forty machines. The run-hours say twenty-eight are earning and twelve are insurance you're paying to store. Utilization doesn't just tune your maintenance — it decides what you buy next.
Read → - 5 min readmobile
Building Fleet for the field
The office runs Fleet in a browser tab. The field runs on a phone — in the sun, in gloves, in a dead zone — and that's a different app. Notes from building the mobile half of the platform, and the Bluetooth trick that turns every phone into a roaming hub.
Read → - 4 min readproduct
Location isn't utilization
A map full of dots tells you where your equipment is. It tells you nothing about whether any of it is working. Those are two different questions, and most fleets only own hardware that answers the first.
Read → - 5 min readtechnical
Getting your data out
Somewhere in every buying cycle a careful customer asks the question that separates a tool from a trap — "can I get my data out?" A dashboard is where data goes to be looked at. The fleet data that matters has to live in the systems you already run. Here's how we think about the way out.
Read → - 5 min readproduct
Idling isn't working
At month-end the 50-ton excavator shows 190 hours — the busiest number on the yard. Then you find out 70 of them were the engine running while nobody touched a lever. Hours tell you the machine was on. Utilization tells you whether it earned its keep, and those are not the same number.
Read → - 5 min readfield
Tagging the whole yard
The PO is signed and a box of forty tags shows up. Between that box and a dashboard that means anything sits the least glamorous step of the whole deployment — giving every machine an identity the system can trust. Do it wrong once and you'll chase phantom assets for months. Here's how to do it right, and why it isn't the six-month project everyone fears.
Read → - 3 min readproduct
The 490-hour service
We wrote a while back that continuous CMH lets you schedule the 500-hour service at 490 instead of "when someone notices." That was half the story. Here's the other half — turning the number into a job that someone actually does.
Read → - 5 min readfield
The first 30 days of a deployment
Signing the PO is the start, not the finish. The first month decides whether a deployment becomes infrastructure the site forgets it has, or a support ticket that never closes. Here's the arc — a composite of the ones that went well.
Read → - 5 min readproduct
A day in Fleet
The new Fleet App ships soon. Instead of a feature list, here's what a Tuesday looks like for an ops lead with it open — from the 7am inbox paragraph to the 5pm audit log.
Read → - 4 min readproduct
CMH and the warranty conversation
When a $40,000 engine fails at 1,840 hours and the warranty runs to 2,000, what counts as proof? The boring bookkeeping that decides whether the claim gets paid.
Read → - 3 min readproduct
CMH from telemetry vs CMH from the clipboard
The dashboard says 4,820 hours. The operator's logbook says 5,180. The gap is real, it's persistent, and it's costing someone money. Here's how to think about it.
Read → - 3 min readproduct
What "running" actually means
Every yard tracks "machine hours" and every yard means something slightly different by it. The definition you pick changes the number by 20% or more, and decides whether your service intervals work.
Read → - 3 min readproduct
When predictive maintenance isn't magic
The industry loves to talk about AI + IoT for equipment management. Most of what actually ships in production is thresholds, trendlines, and someone willing to look at the dashboard.
Read →