← Solution examplesUtilities & Energy example · GIS ↔ EAM ↔ SCADA

Asset Identity & Outage Context

GIS knows where the asset is. SCADA knows what it is doing. Asset management knows what happened to it. We make those facts exist in one place.

solution / asset-identity-outage-context

Engineering blueprint

LAYER 01Existing systemsIntegrated, not replaced

GISEAMSCADAOMSCIS

LAYER 02Governed asset dataCanonical, with lineage

AssetsTopologyTelemetry pointsWork history

LAYER 03KBSIntel asset context layerIdentity & enrichment

Identity resolutionTopology reconciliationEvent enrichment

LAYER 04Decisions & intelligenceBuilt on governed data

Outage contextCritical customersAsset risk

Problem

One transformer can carry a GIS ID, an EAM ID, a SCADA point, an OMS node, and customer links, all created separately. When it fails, operators rebuild the context by hand.

Example

SCADA reports a fault. The operator needs the asset, its location, downstream customers, recent maintenance, and open work orders, across five systems.

Governed object · Physical Asset Identity

GIS ID
EAM ID
SCADA point
OMS node
CIS link
Location
Topology
Maintenance history

Where the systems disagree

Unmapped identifiers
Topology drift
Orphaned telemetry
Hidden maintenance
Unknown critical customers
Stale field records

What we build

An asset identity and context layer across GIS, EAM, SCADA, OMS, and CIS.

Asset identity resolution across systems
Topology reconciliation between GIS and OMS
Fault enrichment with location and customers
Mismatch queues for data stewards
Context services for operators and crews

Controls

Flag identifiers that do not resolve
Reconcile GIS and OMS topology
Enrich every fault with full context
Route field changes to the system of record

Intelligence

Outage context for operators
Critical-customer impact
Asset risk from history
GIS and EAM data-quality scores

What we'd measure

Assets with a resolved identity
Open identifier and topology mismatches
Time to assemble outage context
Critical facilities linked to the network

Start with one problem. Engineer the right solution.

Manual work, systems that don't talk, data nobody trusts. We trace it to the source and ship the fix into production.