Every refrigerated trailer in a connected fleet is quietly talking to you. Over a single quarter, the telematics on a Carrier Transicold reefer fleet can log hundreds of alarm codes — failed starts, box-temperature excursions, defrost faults, low-refrigerant warnings, and a long tail of one-off events. Export all of it into a pivot table and the first impression is the same every time: a wall of codes, none obviously more urgent than the next.

Here's the reframe that changes everything: the value of the report isn't the codes. It's turning them into a short list of things worth doing. And when you read one real quarter the right way, the short list gets very short, very fast. We pulled the numbers to show you the shape of it.

A few codes own almost everything

Filtered to urgent severity, the fleet logged 657 events for the quarter. Two codes accounted for the overwhelming majority: shutdowns flagged for a unit-status check, and units failing to run their minimum cycle time. Together, those two fault types were roughly 84% of every urgent alarm.

That's the Pareto principle showing up exactly where you'd expect it. The dozens of other codes — battery voltage, starter solenoid, low suction superheat, box-temp out of range — are real, but chasing them first means polishing the margins while the center of the problem sits untouched. Rank by code first. Then resist the urge to start anywhere but the top.

One asset can distort the entire picture

This is the part that changes how you read the whole dataset. Break the codes down by individual unit and a single trailer dominates — it generated over 500 alarms on its own, and almost all of them were the same two fault types driving the fleet-wide totals.

In fact, nearly every urgent "failed to run min time" event in the entire fleet traced back to that one unit, and it produced the large majority of the urgent shutdown alarms as well. Pull that single trailer out of the analysis and the fleet's alarm profile looks dramatically healthier — not because the other units are perfect, but because one outlier was inflating every fleet-level number it touched.

Every unit has a fingerprint

Once the dominant outlier is set aside, the remaining units don't share one common problem — each has its own signature. A couple of trailers were defined almost entirely by incomplete-defrost faults, with little else wrong. Another clustered around starter and solenoid-circuit codes alongside box-temp excursions. A different unit told a fuel-system story: fuel-sensor faults, low-fuel warnings, and repeated failed auto-mode starts.

These fingerprints are diagnostic gold. A unit that only throws defrost codes points you at a specific subsystem and a specific part — not a full teardown. Reading codes per asset, not just in aggregate, lets you match the right fix to the right machine and stops you applying a fleet-wide remedy to a problem that lives in three trailers.

Severity is the filter that focuses everyone

Raw counts and urgent-only counts tell different stories, and the gap between them is where prioritization happens. Plenty of codes that look loud in total volume fade once you filter to urgent; others stay stubbornly at the top no matter how you slice it. The codes that survive the severity filter — and that concentrate on a few assets — are your real work queue.

Bottom line

The hardest part of fleet telematics was never the data — it's the discipline to read it for the few things that matter and ignore the rest until they earn a place on the list. Hundreds of codes narrow to a few fault types, narrow to a few assets, narrow to one unit that needs eyes on it now. The data does the narrowing for you, but only if you read it for shape and concentration rather than treating every code as equal.

End every review the way this one ended: not with a dashboard, but with one named, physical action. Flag the outlier. Assess it. Then work down the list.

Analysis based on anonymized AVRO field and fleet telematics data. Alarm-code names, severity definitions, and recommended actions vary by unit configuration and software version — confirm current procedures with your authorized dealer before servicing. © 2026 AVRO Parts. All rights reserved.