The Field That Breaks the Insurance Claim
INSTALLDATE is a text field in this template, not a date picker — and that's an intentional accommodation for the reality that transformer installation records arrive in inconsistent formats from different contractors, handover documents, and legacy systems. But that field, whatever its format, is the one that determines whether a claim for premature failure gets paid or disputed. A unit that failed 14 months after installation and was supposed to carry a 5-year warranty is a vendor problem if the install date is documented. Without it, the failure is just a maintenance cost.
What the Asset Record Actually Contains
KAPASITAS — capacity — is the technical heartbeat of the record. For power distribution transformers, this is the kVA rating that determines which loads the unit can legally carry and what the protection scheme is calibrated to. A unit running above its rated capacity isn't a scheduling problem; it's a safety and compliance issue. The asset record that captures capacity alongside the actual location and load circuit makes overloading events visible in retrospect when a unit fails thermal testing or shows hotspot damage on thermographic inspection.
SERIALNUM and MANUFACTURER together are the chain-of-custody trail. When a fault occurs in the field, the first call is to the manufacturer's technical support line — and that conversation goes nowhere without the serial number. Manufacturers track production batches, and a documented quality deviation in a production run of 2021 units from a specific facility is only actionable if you can cross-reference your asset register against the affected serial range. Utilities that don't maintain serial-level records discover this the hard way after a batch failure event.
CLASSIFICATION defines where in the grid hierarchy this unit sits: distribution, sub-transmission, step-down, isolation. This isn't a descriptor for taxonomy's sake — it drives maintenance scheduling, inspection frequency requirements, and the priority tier assigned when an outage is reported. A Class 1 asset that's showing oil pressure anomalies gets a same-day response. A misclassified asset gets scheduled maintenance and the wrong urgency level until something fails.
TGLUPDATE (date of last update) and USERUPDATE (who updated the record) are the audit fields that tell you whether the record is current. An asset register with no update timestamps is a static document masquerading as live data. In a utility context, a record that was last touched three years ago may reflect a unit that has since been relocated, rewound, or decommissioned — and none of those events made it back to the database.
Finding the Right Unit at 02:00 During a Grid Fault
LOCATION is what gets called first. Not the description, not the classification — the location. A grid event at 02:00 means the dispatcher is pulling location data while simultaneously routing the field crew and briefing the SCADA operator. The asset record needs to return a usable location — substation name, bay identifier, geographic coordinates — without requiring cross-referencing another system.
The STATUS field (operating, maintenance, decommissioned, reserve) is what tells the dispatcher whether the hot spare in Bay 7 is actually available to switch in or whether it was pulled for rewind last month and hasn't come back yet. That single field, kept current, is the difference between a 40-minute restoration time and a four-hour dig through maintenance records to confirm whether the backup unit is serviceable.
Full equipment photos and specific SR (substation record) photos — captured in the template's image fields — mean the field crew arriving at an unfamiliar installation has a visual reference for what they're walking into. The photo record taken at commissioning is the baseline the thermographic survey is compared against two years later, when the oil cooling fins on the left side of the tank are running 8°C hotter than they were at install.