Three Classification Levels and Why Asset Registries Fail Without Them

Power utility asset management collapses at scale when assets are logged without a consistent classification hierarchy. "Transformer, 500 kVA" is a description. "MSB / MVPT / MV Power transformer, 500 kVA, Facility 0037, GPS captured" is a retrievable, comparable, auditable asset record. The MV Substation template in Memento Database builds that hierarchy across three levels: Level 5 (MSB—MV Substation), Level 6 (twenty-one component codes covering everything from AUXE through VOLT), and Level 7 (the granular variant codes that identify specific equipment types within each Level 6 category).

Level 6 alone covers the full MV substation component taxonomy: AUXE (Auxiliary equipment), BATC (Battery charger), BATT (Batteries), CBRP (Circuit breaker panel), CONP (Control panel), CURT (Current transformer), EMET (Electricity meter), LCST (Load control set), LOCT (Local transformer), MSUB (Mini-Sub), MVPT (MV Power transformer), MVSC (MV Switchgear—Circuit breaker), MVSL (MV Switchgear—Isolating link), PFEQ (Power factor equipment), REAC (Reactor), RMU (Ring main unit), SURG (Surge arrestor), TNEC (Transformer NEC), TNER (Transformer NER), VOLT (Voltage transformer).

That vocabulary is not arbitrary. It maps to IEC and national utility classification standards. When an asset database uses it consistently across hundreds of substations, the query "all MVSC assets installed before 2005 across Region 3" returns a meaningful, actionable list. Without the hierarchy, the same query requires manual interpretation of free-text descriptions that vary by whoever logged the record.

Capacity, Dimensions, and the Physical Record That Supports Planning

Power rating (kVA/kW), tank capacity, and weight are the capacity fields. Width, length, height, area, and volume are the dimensional fields. Together they support infrastructure planning decisions that cannot be made from nameplate data alone: whether a replacement transformer will physically fit in the existing bay, whether the civil foundation will support the rated weight, whether the switchgear room has clearance for the proposed busbar extension.

An asset database without dimensional records requires a site visit to answer every physical planning question. One with dimensional records answers most of them from the office—a difference that matters when the substation is at the end of a four-hour access road in wet season.

Age, Criticality, and the Replacement Budget That Isn't a Guess

Age and Last Renewal are lifecycle fields. Operational costs and criticality are the business case fields. A 28-year-old MV power transformer at a substation feeding a hospital complex is a different replacement priority than the same-age transformer at a low-demand agricultural feeder. Criticality captures that distinction explicitly, enabling a risk-weighted replacement prioritization that budget cycles can actually act on.

Without criticality classification, asset replacement decisions default to age-based queuing. Age-based queuing replaces assets in installation-date order without regard to failure consequence. Criticality-weighted queuing replaces the assets where failure is most expensive first—which is almost never the same list.

GPS coordinates and the five component photo fields round out the record as a physical documentation package. GPS coordinates enable GIS integration and field navigation. Five photos—enough for the transformer itself, the nameplate, the switchgear, the control panel, and a general bay view—create the visual asset record that commissioning reports, insurance documentation, and condition assessments all require. The sketch field carries the dimensional drawing or cable routing diagram that doesn't compress into a photograph.

Link to Facility ties each component record to the parent facility record in the broader asset management system. This is the field that makes the database relational rather than standalone—a component without a facility link is an orphan record that cannot be queried in the context of the site it belongs to.