The classic warranty dispute has a familiar shape: equipment fails inside its warranty period, the facility files a claim, and the OEM's first response is some version of "this looks like it was operated outside spec." Without a record, that's one word against another — and the party with more leverage usually wins the argument, regardless of what actually happened. The way out of that argument isn't a stronger opinion; it's a record neither side can dispute.
What OEMs Actually Want to See in a Claim
A warranty claim moves faster and more favorably when it comes with evidence that the equipment was operated within its rated parameters — load ranges respected, oil temperature within bounds, protection devices functioning and triggering correctly when conditions called for it. OEMs aren't being unreasonable asking for this; warranty terms genuinely do exclude damage from misuse or neglect, and they need some basis for distinguishing a manufacturing defect from an operating problem. The dispute exists precisely because, without data, that distinction is unprovable either way.
What a Transformer's Operating Envelope Actually Looks Like
For a transformer specifically, the parameters that matter are load % against rated capacity, oil temperature trend over time, power factor, THD, tap changer position history, and Buchholz relay status. Consider what each proves: a load % history shows whether the unit was ever pushed past its rating, and for how long. An oil-temperature trend shows whether cooling was adequate or whether the unit was running hot for an extended period before failure. Buchholz relay status is particularly useful — this relay is designed to trip on internal gas accumulation from developing faults, so a log showing it tripped correctly (or, just as importantly, that no fault condition existed before a sudden failure) directly counters a "you ignored a warning" claim or supports a "this was a sudden defect, not a slow misuse pattern" one.
Why Paper Logs Don't Hold Up
A logbook filled in once a shift, or once a day, has gaps by design — it captures a handful of moments, not the full operating history between them. A transformer's oil temperature can spike overnight and return to normal by the time the morning reading is taken, leaving no trace at all in a manual log. Entries get backfilled from memory, handwriting is sometimes illegible, and there's no way to verify a reading wasn't adjusted after the fact. When an OEM's investigator is looking for a reason to dispute a claim, a thin paper trail gives them plenty of room to argue the gaps favor their position.
What Continuous IoT Data Proves Instead
A continuous, timestamped record shows the equipment's actual operating envelope over its full history — not a handful of spot-checks, but every reading, all the time, including the overnight spike a manual log would have missed entirely. Load percentage over months, oil-temperature trends, Buchholz relay trip timestamps, exactly when maintenance events happened. That level of detail doesn't just support your side of a warranty argument; it often prevents the argument from starting, because the pattern is too complete to plausibly dispute in either direction.
Building a Warranty-Ready Data Trail From Day One
The mistake most facilities make is not thinking about warranty evidence until they're already filing a claim — by which point months or years of unmonitored operation are simply gone, and the transformer's actual load and temperature history during the period that matters was never recorded at all. Continuous monitoring from the day equipment is commissioned means the data trail already exists if you ever need it, instead of being something you wish you'd started collecting three years ago, after the dispute has already started.
Frequently Asked Questions
Acceptance varies by OEM and by the specific terms of the warranty or AMC — a continuous, timestamped operating record covering the parameters the OEM's own warranty terms reference (load %, oil temperature, protection-device trip history) is generally stronger evidence than a verbal account either way, but it's worth confirming what documentation format your specific OEM's claims process expects before you need it.
Yes — the same operating history is useful for a warranty claim, an insurance claim, or simply understanding why a piece of equipment failed when it did, regardless of whether it's still under warranty. A Buchholz relay trip log or an oil-temperature trend is just as informative six months after warranty expiry as it is during the warranty period.
At minimum, for the length of the equipment's warranty or AMC period — many facilities keep it longer, since a multi-year oil-temperature or load trend is also useful for planning replacement timing and for negotiating the next AMC or purchase.
Data can be exported from the dashboard for exactly this purpose — the practical step is confirming with your specific OEM what format or fields their claims process requires before you need it in a dispute, since requirements vary by manufacturer.
Load % against rated capacity, oil temperature trend, power factor, THD, tap changer position history, and Buchholz relay status — together these describe not just whether the unit was overloaded, but whether protection devices functioned correctly and whether internal conditions (rising THD, degrading power factor) were already signaling a developing fault before the failure an OEM might otherwise attribute to misuse.