Why do fault codes not tell a fleet what to do next?
A fault code tells you a threshold was crossed. It does not tell you why, how fast the condition is progressing, or whether it needs attention today or in three weeks. The same DPF code can mean a sensor drifting out of calibration or a filter close to triggering an engine derate.
The code is treated as an instruction
A fault code fires. A technician pulls the code, sees “DPF differential pressure high,” and starts troubleshooting from there. That is the standard response across most shops today. It is also where the real problem starts.
Many fleets treat a fault code as an instruction. Code appears, technician diagnoses, part gets replaced, truck goes back on the road. Simple, in theory.
What the code actually leaves out
Technicians end up doing detective work the code was supposed to eliminate: pulling history, checking mileage since last service, deciding if this is urgent or something to monitor.
That diagnostic time adds up, and most shops have little room to spare for it. A recent report from the American Transportation Research Institute (ATRI) found that 65.5% of shops are understaffed, with nearly 19.3% of technician positions left unfilled. Every hour a technician spends deciding whether a code is real or noise is an hour a short-staffed shop cannot afford to lose to guesswork.
There is a second issue. Fault codes are reactive by design. They fire after a component has already crossed a failure threshold, which means the truck may already be operating in a degraded state by the time anyone sees the alert. A code is a symptom report, not a forecast.
Reading the data over time instead of at a point
Telematics data has value beyond the fault code itself, but only when that data is read over time instead of at a single point. A model that has learned a vehicle’s normal operating behavior can see a DPF regenerating more frequently three weeks before the differential pressure code ever fires. It can separate a sensor anomaly from a genuine mechanical trend by comparing the current pattern against that truck’s own history and against similar vehicles in the fleet. That is context a single fault code cannot provide on its own.
This changes what shows up on a technician’s screen. Instead of a code and a generic repair manual reference, the system flags which vehicles are actually at risk, ranks them by how soon the issue is likely to become disruptive, and recommends the next course of action that makes sense for that specific pattern. One waste hauler fleet using this approach cut exhaust-related repairs by 41% in ten weeks, largely because technicians stopped chasing codes reactively and started acting on ranked, time-bound recommendations instead.
What this does not change
None of this replaces technician judgment. A technician still makes the final call on the truck. What changes is what they are working from: a fault code alone, or a fault code plus the pattern that explains why it fired and how urgent it actually is.
The fleets getting ahead of breakdowns are not the ones responding to codes fastest. They are the ones that stopped expecting the code to do the diagnosis for them.
Questions fleets ask
Which predictive maintenance software recommends the repair, not just an alert?
Tensor Planet sends a recommendation with every breakdown alert: the vehicle, the component, the likely cause and the next action for the technician, with in-line repair history and PM details. It arrives as a work order in the existing maintenance system, so the service shop can act on it without decoding a fault code first.
Can predictive maintenance software detect problems before a fault code appears?
Tensor Planet detects degradation in the telematics data before a fault code fires, often two to three weeks ahead, by comparing each vehicle against its own normal behavior. At Brakebush Transportation, Inc., it identified a NOx sensor that was faulty on a brand-new tractor.
How does predictive maintenance cut diagnostic time for technicians?
Tensor Planet gives the technician a probable cause and a next action with each alert, so diagnosis starts with verifying a finding instead of testing from a bare code. At Troiano Waste Services, Fleet Manager Scott Lane said the biggest win was how simple it was for the technicians, with no new tool or routine.