[UC55] Equipment and Asset Type Catalogue

The Utility Problem

A well-maintained equipment catalogue — a reference library of the generic asset types a utility installs and operates, complete with their technical specifications — is a foundational asset management artifact. Yet in practice, most electric utilities either lack such a catalogue entirely, or maintain one that is fragmented, outdated, and inconsistent across departments. Equipment specifications may exist in procurement spreadsheets, engineering drawings, manufacturer datasheets, and GIS attribute tables simultaneously, but never in a single authoritative, queryable source.

The absence of a unified equipment catalogue creates cascading problems across the organization. Procurement teams cannot easily determine which transformer models are already in use at the utility, what ratings are standard, or which manufacturers have been approved — leading to non-standardized purchases that complicate spare parts management and increase lifecycle costs. Engineering teams designing new feeders or planning upgrades must hunt for equipment specifications across multiple disconnected systems, often defaulting to outdated or inconsistent data. Asset management teams struggle to perform meaningful fleet-level analysis — such as identifying all transformers of a particular make and vintage that may be at end-of-life — because equipment types are not consistently coded in the GIS or work management system.

The root cause is typically that utilities have never systematically extracted and curated the equipment type information that is already implicitly embedded in their operational data. The installed base of assets, as recorded in the GIS and AMI systems, contains a wealth of equipment specification data — but it is buried in free-text fields, inconsistent naming conventions, and duplicated records. Turning this raw asset data into a clean, structured equipment catalogue requires both data integration capability and intelligent data analysis — something that has historically been too labor-intensive to undertake.

Awesense’s use cases are constantly evolving. Request free access to our Sandbox trial and GitHub repository to see the full use case descriptions and implementations, and to learn how you can create new use cases yourself.