Why Asset Data Is the Foundation of Grid Reliability 

GIS and the functional location: two systems of record for the same pole 

Ask a utility where the authoritative asset record lives and you will usually get two answers depending on who’s in the room. GIS says the network model. SAP says the functional location hierarchy. Both are partly right, and the gap between them is where work orders go to die. 

The specific failure is that the two models were built for different purposes. GIS is spatial and network-topological features, connectivity, upstream/downstream traces. The SAP functional location hierarchy is structural and financial where work is planned, costed, and capitalized. They were rarely designed against each other, so the crosswalk between GIS feature ID and functional location is often incomplete, one-directional, or maintained by hand in a spreadsheet somewhere. 

When that crosswalk is weak, four things break: 

• Work doesn’t find the asset. Field crews get notifications that reference a location that doesn’t resolve to a physical thing. 
• Cost doesn’t roll up. Spend lands at a level too coarse to support asset-level decisions or a defensible rate case. 
• Reliability metrics get soft. SAIDI/SAIFI attribution requires knowing which asset served which customers. 
• Compliance evidence is hard to assemble. Regulators are increasingly asking utilities to show the asset-level record behind the mitigation work. 

The right answer isn’t to pick a winner between GIS and EAM. It’s to define the crosswalk deliberately which system masters which attribute, what the matching key is, how conflicts resolve, and how the sync is monitored  and then instrument it so drift surfaces as an exception rather than as a surprise three years later. 

Linear assets don’t fit in a box, and that’s the whole problem 

Most EAM data models were designed for point assets. A pump is a pump. It has a nameplate, a location, a BoM, a maintenance plan. 

A utility’s fleet is substantially linear: conductor, cable, pipe, right-of-way, and the spans between structures. A 14-mile feeder is not one asset and it is not 14 assets. Condition varies along it. Work happens on segments of it. Failure happens at a point on it. 

Handling that properly requires linear referencing  start point, end point, offsets, dynamic segmentation  so that an inspection finding, a work order, and a vegetation cycle can all attach to the same 400 feet without forcing the utility to shred the asset into artificial pieces. SAP supports this through Linear Asset Management, but the capability only pays off if the underlying reference data is consistent: measurement points defined against the same reference system, offsets in the same units, segment boundaries that agree with the GIS model. 

Vegetation management is where this stops being an abstraction. Post-wildfire, utility vegetation management has shifted from a cyclical trim program to a risk-based, evidence-backed program  LiDAR and imagery flown across the territory, findings scored by span, work prioritized by ignition risk. That entire chain depends on being able to bind a finding to a linear location and carry it through to a completed work record. If the span-level reference data is inconsistent, the utility has spent real money on inspection data it can’t operationalize or defend. 

Sensors have nowhere to land without an asset spine 

The IoT conversation in utilities usually starts with the sensor and works forward. It should start with the asset record and work backward. 

Line sensors, transformer monitors, substation IEDs, and AMI-derived voltage all produce time series that are only useful when they’re bound to a specific piece of equipment with known criticality, known maintenance history, and a known position in the network. That binding historian tag or device ID to equipment number and measurement point is almost always the weakest link in a predictive maintenance program. 

Models don’t usually fail because the algorithm was wrong. They fail on the join. A model trained on a population where 20% of the assets are mislabeled learns the mislabeling. 

Before investing further in analytics, the questions worth answering are simple: What percentage of monitored assets have a valid equipment record? Do measurement points exist and are they consistently defined by asset class? Is the equipment hierarchy stable enough that a model trained today still resolves in eighteen months? 

The MRO storeroom is where the money already is 

While AMI 2.0 and wildfire dominate the strategy deck, there is immediate, unglamorous value sitting in the materials and spares data and it’s the fastest thing on this list to prove. 

The recurring patterns are consistent across every heavy-asset industry we work in: 

• Duplicate materials. The same part described four ways, stocked four times, ordered four times. 
• Missing criticality. Spares for critical assets carrying no criticality indicator, which means they carry no safety stock policy either. 
• Broken BoM coverage. Critical equipment with no bill of materials at all  so a storm response depends on someone’s memory. 
• Excess and obsolete stock. High stock value with near-zero movement, usually because the equipment it supported was retired and the association was never cleaned up. 
• Price and unit-of-measure keying errors. A “$4M gasket” is a decimal error, not a costly part but it distorts valuation and planning until someone catches it. 

Each of these is measurable today against the existing data, quantifiable in dollars, and fixable without waiting for a transformation program. For a lot of utilities, this is the right first proof it funds credibility for the bigger work. 

The truck roll that shouldn’t have happened twice 

Ask a maintenance planner where their time goes and you’ll rarely hear “planning.” You’ll hear “chasing information.” 

The repeat truck roll is the most visible symptom of bad asset data, and it’s almost never a scheduling failure. It’s a data failure that surfaced in the field: 

• The equipment record was incomplete, so the crew arrived without knowing the make, model, or rating of what they were there to work on. 
• There was no bill of materials, so the part they needed wasn’t on the truck and nobody could have known it would be.
• The qualification was wrong. The work required a certification the dispatched crew didn’t hold, because the job wasn’t scoped against an accurate picture of the asset.  
• The scope was wrong. The notification described a different asset, an older configuration, or a condition that had already been corrected. 
• The access or safety requirement wasn’t in the record  permits, clearances, switching, landowner notification so the crew got there and couldn’t start. 

Every one of those is a second trip. In a utility running tens of thousands of work orders a year, across a service territory measured in hours of drive time, the cumulative cost is significant and it’s cost that never appears in a data quality business case, because it gets booked as field labor. 

The upstream damage is worse. Planning quality is capped by data quality. A planner working from an incomplete equipment record can’t build an accurate job package, can’t reserve the right materials, can’t estimate duration credibly, and can’t sequence work efficiently. So they pad. They over-scope. They schedule conservatively. The whole planning function quietly degrades into a buffer against uncertainty, and schedule compliance metrics stop meaning anything. 

Fixing this doesn’t require a new work management system. It requires the equipment record, the BoM, the classification, and the task-list-to-qualification mapping to be complete and correct on the assets that generate the work which is a bounded, measurable, achievable target. 

New sites and new build: get it right at construction 

Utilities are building substations, storage, interconnection facilities, service centers. Every new site is a chance to either extend a clean standard or import a new dialect. 

Setting a site up well means the functional location hierarchy follows an enterprise standard rather than the EPC’s convention; equipment is classified against a defined taxonomy with real characteristic values rather than free text; maintenance plans and strategies are assigned at handover, not months later; spares are linked to equipment BoMs before the first failure; and the as-built handover from the contractor is validated against the standard before it’s accepted. 

The economics are stark. Structuring the data at handover costs a fraction of remediating it later, and it never generates the compliance and reliability gaps that a year of unmanaged records does. 

The challenge is that utilities often know these issues exist. What’s harder is determining where to invest limited resources for the greatest operational impact. 

The Asset Record Underneath It All 

The common thread across all of these challenges isn’t GIS, sensors, inventory, vegetation management, or work planning. It’s the asset data underneath them. 

Utilities often encounter these issues as separate operational problems owned by different teams. In practice, they’re usually different symptoms of the same condition: infrastructure data that has become disconnected from the assets it describes. 

That’s why the highest-return asset investments aren’t always new technologies. Sometimes they’re the less visible work of establishing reliable relationships between assets, locations, materials, work history, and network information. 

When those relationships are trustworthy, utilities get more value out of every system they’re already running. When they aren’t, each new initiative inherits the same underlying problem.