Ransford's NotesCourses
Workspace

Asset and Network Data Architecture

Model the data layers of a utility asset register, from GIS through SCADA to the planning layer, so data gaps between operational and planning systems are visible.

Phase C, Information Systems ArchitectureDerived from TOGAF

Asset and network data: each domain mapped from store of record to model to consumer

Four data domains each trace the same path: the system of record that holds them, the model or standard they must conform to, and the operational consumers that read them back.

Asset and network data has to land in a model the network operator already uses, such as the IEC CIM and GIS topology. Naming the model per domain gives every consumer a contract it can trust.

Asset and network data: each domain mapped from store of record to model to consumer Four horizontal lanes, one per network-asset data domain, under three headers: store of record, model or standard, and operational consumer. Topology and geography runs GIS, conforms to IEC CIM plus GIS schema, read by ADMS and planning. Asset register runs EAM, conforms to IEC 61968, read by planning and finance. Live network state runs ADMS, conforms to IEC CIM, read by reliability reporting. Headroom and capacity runs a capacity tool, conforms to IEC CIM SystemCapacity, read by Ofgem reporting. In every lane the conforms-to arrow into the emphasised middle model panel is red, and a red note marks the model column as the contract. Store of recordModel or standardOperational consumer Topologyand geographyGISNetwork topology, geographyconforms toIEC CIM + GIS schemaTopology and geographyread byADMS, planningSwitching, capacity studies Asset registerEAMAsset register, conditionconforms toIEC 61968Asset class hierarchyread byPlanning, financeReinforcement, capex Live network stateADMSLive network stateconforms toIEC CIMLive state modelread byReliability reportingCML, CI counts Headroomand capacityCapacity toolHeadroom, declarationsconforms toIEC CIM SystemCapacityHeadroom profileread byOfgem reportingRIIO-ED declarations The model column is the contract.Land each domain in a model the operator already runs, and every consumer reads from a known shape rather thana bespoke export.