Systems and records
Utility asset record inconsistency: when two systems disagree
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
Reconcile conflicting utility asset records in two passes. First settle identity: decide whether the records describe the same physical asset, using persistent identifiers and work order history rather than names. Then settle each attribute separately, taking it from the evidence authoritative for that attribute, such as the closed work order for install date or GIS for location. Record every decision with its evidence and leave unresolved conflicts labeled.
System export
Utility asset record
Key takeaways
- Settle whether two records describe the same physical asset before comparing any attribute.
- Match on persistent identifiers and work orders, never on names, and separate network positions from the units installed in them.
- Take each attribute from the evidence created by the event that set it, and date every value.
- Send corrections to system owners instead of editing operational or regulated records.
- Keep unresolved conflicts as labeled data, and leave safety-relevant conflicts to engineers.
How do you reconcile conflicting utility asset records across systems?
Do not crown one system as the truth. Utility asset records disagree because each system was built for a different job: GIS for where things are and how they connect, work and asset management for what was done to them, the plant accounting records for what they cost and when they were retired, and meter data systems for what they measured. Each is usually right about its own job and often stale about the others.
The reliable method has two passes. The identity pass decides whether two records describe the same physical asset, the same location with a replaced asset, or two different assets. The attribute pass then takes each attribute from the evidence that has authority over it and records which evidence was used, with dates.
The output is a reconciliation record kept beside the source systems, not an edit to them. Changing operational or regulated records is the utility's own controlled process. For a dataset, what matters is that every value has a traceable source and every unresolved conflict is visible rather than smoothed over.
Is it the same asset? Settle identity before comparing attributes
Match on persistent identifiers and work history, never on names. Names and descriptions are labels people type, and two records with the same name can describe different assets while one asset can carry several names across systems.
The Common Information Model used across the power industry makes this explicit. In the CGMES classes published in the cimpy library, the mRID is a master resource identifier issued by a model authority and globally unique within an exchange context, with a UUID strongly recommended, while the name is free text that may be non-unique. Tooling can still break identity: the CIMHub project's documentation warns that converting a circuit for the first time creates random UUIDs, and that later conversions should reuse the saved UUID file so the same objects keep the same identifiers.
Separate the place from the thing in that place. CIM describes a power system resource as an item of equipment, a container such as a substation, or an organizational entity, linked to a location. When a transformer is replaced, the position on the network continues but the physical unit changes, so a reconciliation that merges the two loses the replacement, and one that treats them as unrelated loses the history of the position.
- Strong match: a shared persistent identifier, or a cross-reference stored by an integration.
- Supported match: the same location and asset class plus a work order that names both records.
- Weak match: the same location and class only. Treat as a candidate until evidence links them.
- Not a match: different serial or manufacturer numbers at the same location, unless a work order shows a correction.
Which system should win for each attribute?
Each attribute has its own authoritative evidence, and the matrix below is a starting point that a utility adjusts to how its own processes run. The rule is to prefer the record created by the event that set the attribute, closest in time to that event.
| Attribute | Usually authoritative evidence | Common conflicting source | Tie-break rule |
|---|---|---|---|
| Location and connectivity | GIS after as-built posting | Work order address or staking sheet | Prefer GIS if the as-built is posted; otherwise flag the posting lag |
| Installed or in-service date | Closed installation work order | GIS feature creation date | Feature creation dates record data entry, not installation |
| Manufacturer, serial and nameplate | Installation record or nameplate photo | Asset register defaults | Physical evidence beats a default value |
| Material and specification | Purchase, mill or test records | Design standard assumed for the era | Assumed values stay labeled as assumed |
| Operating status | Operations or outage system | GIS status field | Use the dated operational record; GIS often lags |
| Retirement and cost unit | Continuing property records | Asset register status | Accounting records govern accounting attributes only |
| Meter readings and usage | Meter data system with quality flags | Billing extract | Use the latest revision and keep earlier ones |
| Maintenance and inspection history | Work management system | Spreadsheets and paper forms | Keep both, linked by work order where possible |
What do regulated records already require an asset file to prove?
Some attributes already carry a regulatory standard of evidence, and a reconciliation has to respect it rather than replace it. These rules also show what a well-evidenced asset file looks like.
For onshore steel gas transmission pipelines, 49 CFR 192.607 requires that records of material properties, such as diameter, wall thickness, seam type and grade, be traceable, verifiable and complete, and sets out testing procedures where they are not. For gas distribution, the integrity management rule in 49 CFR 192.1007 asks operators to demonstrate knowledge of the system from reasonably available information, to identify the additional information needed with a plan to gain it over time through normal activities, and to capture at least the location and material of new pipe.
Accounting rules define a parallel record. The Uniform System of Accounts in 18 CFR Part 101 describes continuing plant inventory records that give, for each retirement unit, its name or description and its location, and the Rural Utilities Service rule in 7 CFR 1770.14 asks borrowers to keep continuing property records with the date of placement, location, description and original cost. When the accounting record and GIS disagree on location, the reconciliation notes the conflict; it does not decide that one regulated record is wrong.
How do effective dates, corrected readings and safety limits shape the next step?
Dates decide most conflicts, so every value in the reconciliation carries the date it became true and the date it was recorded. A value that was right in 2015 and wrong today is not an error; it is history, and treating it as an error destroys exactly the sequence a model would learn from.
Corrected readings are the clearest case. The Green Button reference implementation of the ESPI data standard describes reading quality as assumed good unless a quality code says otherwise, and more than one quality can apply to a reading. When a reading is estimated and later replaced, keep both values with their quality codes and revision times, and mark which one billing used. Tariff and contract terms work the same way: link usage to the terms in force on the service date, not the current ones.
Safety and confidentiality set hard boundaries on the next step. A reconciliation never changes switching state, protection settings or operating records, and resolving a conflict by looking at the asset is field work for qualified staff under the utility's own procedures. Some asset detail is also sensitive: FERC's rules on critical energy and electric infrastructure information cover specific engineering, vulnerability or detailed design information that goes beyond the general location of critical infrastructure.
The asset identity and evidence authority reconciliation plan
The plan is a sequence of steps, each with an output a reviewer can check. It is written for a data or records team working alongside engineering and compliance, not instead of them.
| Step | Action | Output | Stop or escalate when |
|---|---|---|---|
| 1. Scope | Pick asset classes, territory and date range | Scope note with excluded classes | Scope includes protection settings or detailed design |
| 2. Inventory sources | List each system, its owner, extract date and identifier fields | Source register | A source has no stable identifier at all |
| 3. Build the crosswalk | Link records by identifier, then by work order, then by location and class | Identity crosswalk with match strength | Weak matches exceed what reviewers can check |
| 4. Split place from unit | Separate network positions from physical units and link replacements | Position and unit tables with replacement links | Replacement history is missing for a class |
| 5. Apply the authority matrix | Take each attribute from its authoritative evidence | Attribute values with evidence references | Two authoritative records disagree |
| 6. Date every value | Record valid-from, recorded-on and revision for each value | Time-stamped attribute history | Dates cannot be recovered for a regulated attribute |
| 7. Label conflicts | Mark each value resolved by rule, by evidence, or unresolved | Conflict register | Unresolved share is too high to use the class |
| 8. Review boundaries | Check safety, confidentiality and customer data | Exclusion list and redaction notes | Content may be critical infrastructure information |
| 9. Hand back findings | Send source corrections to system owners | Correction list; no direct edits | Never; corrections follow the utility's own process |
Illustrative worked example: one pole, two transformers, three records
This example is illustrative. GIS shows a pole-mounted distribution transformer at a pole with one serial number and a 2009 feature date. The work management system shows a 2021 work order that replaced a failed unit at the same pole with a new serial number. The continuing property records show one retirement and one addition in 2021.
Identity pass: the pole is one network position. The 2021 work order names both serial numbers, so there are two physical units, the 2009 unit retired and the 2021 unit installed. GIS was never updated with the new serial, which explains the conflict without either system being wrong about its own job.
Attribute pass: location from GIS, because the position did not move. Installed date and serial for the current unit from the closed 2021 work order. Retirement of the old unit from the accounting record and the same work order, which agree. The 2009 GIS feature date is kept as the record creation date for the position, not as an installation date.
The exception: the current unit's rating differs between the work order and the asset register, and no nameplate photo exists. The value stays unresolved, both candidates are kept, and the item goes on the list for confirmation during the next routine visit by qualified crews.
How should unresolved conflicts appear in the reconciled data?
Keep conflicts as data rather than resolving them by guesswork. Each attribute value carries a resolution label, the competing values, and the evidence for each, so a downstream user can include, exclude or weight uncertain values deliberately.
At a glance
How should unresolved conflicts appear in the reconciled data
- Resolved by rule: the authority matrix picked the value; cite the rule and the evidence.
- Resolved by evidence: a document or photo settled it; cite the document.
- Unresolved: keep every candidate value with its source and date.
- Assumed: a default or era-based value with no direct evidence, never presented as observed.
- Superseded: a value that was correct for a period and has a valid-to date.
Which conflicts belong to engineers rather than the data team?
Any conflict whose resolution would change how the network is operated, maintained or protected belongs to engineering, not to a records project. The data team's job is to surface it with evidence and stop there.
Escalate when two authoritative records disagree on a regulated attribute, when a material property lacks the evidence a rule requires, when a conflict touches ratings or protection, or when the reconciled file would combine location with detailed design in a way that could be sensitive. Customer-linked records, such as service addresses and usage tied to an account, also need a privacy review before they leave the utility. This article is general information; the utility's engineers, compliance staff and counsel decide.
Offering reconciled asset histories for licensing
A reconciled asset history, with identity crosswalks, dated attribute values and labeled conflicts, is far more useful to an AI developer than raw extracts from each system. Utilities and contractors that hold such histories can take them to SourceX, which handles rights review, preparation and delivery on the way to a licensed AI dataset; the opening step is a brief assessment of the company, made before any GIS or work order extract is shared.
Large GIS and asset archives never need a new host, because SourceX leaves deliveries of that size in the company's own storage or moves them on encrypted drives. Safety-sensitive and confidential design detail is scoped out before any agreement.
Frequently asked questions
Why do GIS and asset management systems disagree about the same asset?
Each system records a different event at a different time. GIS is updated when as-builts are posted, work management when the job closes, and accounting when units are added or retired, so lags and missed updates create conflicts that are often history rather than errors.
What should the asset identity and evidence authority reconciliation plan include?
A scope, a source register, an identity crosswalk with match strength, separate tables for network positions and physical units, an attribute authority matrix, dated values, a conflict register, a boundary review and a correction list for system owners. Each step produces an output a reviewer can check.
Should a reconciliation project fix the source systems?
No. It should send a correction list to each system owner and let the utility's own change process update operational and regulated records. Editing those records directly bypasses controls that exist for safety and compliance.
How should corrected meter readings be handled?
Keep the original and the corrected reading with their quality codes and revision times, and mark which one billing used. Replacing the original destroys the record of what was estimated and when it was fixed.
Can utility asset records be licensed for AI?
Some can, after scoping. Records that reveal specific engineering, vulnerability or detailed design information about critical infrastructure, and customer-linked data, need careful review or exclusion, and the utility's counsel and compliance staff decide what leaves.
Sources
- In the CGMES classes, the mRID is a master resource identifier issued by a model authority and globally unique within an exchange context, with UUIDs strongly recommended, while the name may be non-unique. Source
- CIM describes a power system resource as an item of equipment, an equipment container such as a substation, or an organizational entity, associated with a location. Source
- CIMHub's documentation says a first conversion creates random UUIDs and later conversions should reuse the saved UUID values so objects keep their identifiers. Source
- The Green Button ESPI reference implementation treats reading quality as good unless a quality code states otherwise, and allows more than one quality per reading. Source
- 49 CFR 192.607 requires traceable, verifiable and complete records of material properties for onshore steel transmission pipelines. Source
- 49 CFR 192.1007 requires distribution operators to demonstrate knowledge of their system, identify additional information needed with a plan to gain it over time, and capture location and material of new pipe. Source
- The Uniform System of Accounts in 18 CFR Part 101 describes continuing plant inventory records listing each retirement unit's name or description and location. Source
- 7 CFR 1770.14 requires RUS borrowers to keep continuing property records with the date of placement, location, description and original cost of property units. Source
- 18 CFR 388.113 defines critical energy and electric infrastructure information as specific engineering, vulnerability or detailed design information that goes beyond the general location of critical infrastructure. Source
See if your company qualifies
A short company assessment. No data uploads are needed.