Utility Fleet Costing: When Idle Hours Beat Miles

Utility trucks cost money while parked. If your bucket trucks, digger derricks, or service vans are running PTO equipment, compressors, or hydraulics at a job site, they’re accumulating wear — and cost — with zero miles on the odometer. Cost-per-mile is the wrong denominator for these assets.

Most fleet management software defaults to miles. Your telematics provider generates mileage-based reports. Your fuel cards track gallons per trip. But if a truck idles four hours a day powering a lift or a generator, none of that wear shows up in your cost-per-mile figure — it just vanishes into a number that looks artificially cheap. You end up over-extending service intervals, missing failure patterns, and making replace-vs-repair decisions based on bad math.

Here’s how to fix that — and what a duty-cycle costing model actually looks like in practice.

Why Miles Mislead on Utility Fleets

A linehaul truck and a utility service truck can both clock 60,000 miles in a year. But one of them might run 3,000 engine hours doing it. The other might log 6,000 hours — half of those stationary, driving PTO loads.

The FHWA’s Vehicle Inventory and Use Survey has consistently shown that utility and construction trucks average significantly lower annual mileage than over-the-road assets, often under 15,000 miles per year. But their engine hours can rival or exceed long-haul trucks when you account for stationary operation. That gap is where your maintenance budget bleeds out invisibly.

The practical consequence:

• Oil and filter life is driven by engine hours and heat cycles, not miles. A truck idling under load heats oil just as thoroughly as one cruising at highway speed.
• Hydraulic systems, PTOs, and auxiliary equipment accumulate wear on a duty-cycle clock, not a mileage clock.
• Transmission and drivetrain wear on a digger derrick is largely independent of miles traveled.
• Fuel consumption per mile looks terrible on a utility truck — because it should. The metric is meaningless when the engine runs for hours without the wheels turning.

The result: your cost-per-mile figures on these assets are often 2x to 4x your line-haul trucks, which makes them look like fleet liabilities. They’re not. They’re just being measured wrong.

Building a Duty-Cycle Cost Model

Switching from cost-per-mile to cost-per-engine-hour — or a blended metric — changes what you see and what you decide.

Step 1: Pull Engine Hours, Not Odometer Readings

Most Geotab, Samsara, and Motive devices report engine hours alongside mileage. The data exists — it just rarely gets surfaced in standard dashboards. Your telematics provider’s default cost reporting almost always anchors to miles. Pulling engine hours requires either a custom report build or a system sitting on top of the raw data.

Step 2: Separate Drive Hours from Idle-Under-Load Hours

Not all idle is equal. A truck sitting in traffic with the engine running is different from a truck powering a 50-foot aerial platform for four hours. If your telematics supports PTO status or auxiliary power monitoring, tag those hours separately. That’s your “working idle” — it belongs in your duty-cycle cost model.

A reasonable rule of thumb from OEM service manuals: 1 hour of PTO-loaded operation ≈ 25–33 miles of equivalent drivetrain and engine wear, depending on load factor. That benchmark varies by equipment type, but it gives you a starting conversion rate until you build your own from failure data.

Step 3: Restate Your Cost Denominators

Once you have engine hours, you can run two parallel calculations:

Running all three exposes where each asset actually sits. A bucket truck at $38/engine hour and 9,000 annual engine hours has a clearer total cost story than one sitting at “$1.42/mile” on 14,000 miles.

Step 4: Adjust PM Intervals Accordingly

Most OEMs publish dual service intervals — miles or engine hours, whichever comes first. Utility fleets frequently hit the hour threshold before the mileage threshold. If your PM schedule is mileage-gated, you may be running oil changes and inspections 30–60% later than the OEM recommends. That’s where accelerated wear and unplanned failures come from.

Reactive repairs cost 3–9x more than planned maintenance. On a $180,000 aerial platform, catching an overdue service interval that leads to a hydraulic failure isn’t just a maintenance win — it’s the difference between a $400 filter and a $25,000 cylinder replacement.

What Samsara, Geotab, and Motive Don’t Do Here

To be fair: all three platforms capture engine hours at the device level. Geotab in particular surfaces engine hours in its raw data exports and has some reporting around PTO activity. Samsara and Motive have expanded their maintenance modules significantly.

What they don’t do by default is normalize costs across mixed denominators at the fleet level — pulling fuel card data, repair invoices, and telematics hours into a single per-asset cost model that runs both mile-based and hour-based costing in parallel, flags when a PM trigger is hour-gated vs. mileage-gated, and surfaces replace-vs-repair decisions against actual depreciated value. That requires a layer of integration and analytics logic that standard telematics dashboards aren’t built to deliver.

How Link-X Handles Duty-Cycle Costing

Link-X connects to your existing Geotab, Samsara, or Motive telematics feed, your fuel cards, and your maintenance and repair history — and normalizes all of it into a unified cost model per asset. You don’t swap out your telematics hardware. You get the intelligence layer on top of it.

For utility fleets specifically, that means:

• Engine-hour-based PM scheduling alongside mileage triggers, so you don’t miss the interval that hits first
• Work orders and DVIRs tied to actual asset condition, not calendar dates
• Cost-per-hour and cost-per-mile reporting in parallel, so you’re making replace-vs-repair decisions with the right denominator for each asset class
• Invoice processing and warranty tracking that flags whether a repair should come back on a warranty claim before you pay it
• Fleet-health dashboards that separate your line-haul assets from your utility assets so the averages don’t hide what’s actually happening

Sunrun, one of the largest residential solar installers in the U.S., used Link-X to surface 376 underutilized vehicles across their fleet — a finding worth $16.9M in avoided cost. That kind of analysis only works when your cost model reflects how assets actually operate, not just how far they travel.

The Denominator Is a Decision

If you’re running utility, construction, or field-service trucks and measuring them in miles, you’re not managing cost — you’re managing a proxy for cost. The trucks that idle more than they drive need a different ruler.

Recalibrate your PM intervals to engine hours. Build a parallel cost model that includes working idle. Run your replace-vs-repair decisions against total cost of ownership, not odometer readings.

If you want to see what your fleet’s actual duty-cycle costs look like — broken down by asset class, with the right denominators — reach out to the Link-X team and we’ll show you what your data is already telling you.