Utility Network Topology
Describe an operator-governed utility connectivity model, its revisions, state evidence and qualified derived graph views.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 10 questions
Network elements The nodes and edges that make up the graph.
Nodes and edges
Points and links of the network with their asset references.
Node identity
A connection point with its type and the asset it represents.
- Which asset or connection point does this node represent, and of which type?
- Where is the node located, and in which coordinate reference system?
Edge connectivity
A link between two nodes with its direction and capacity.
- Which two nodes does this edge connect, and is flow directed?
- What rated capacity and length apply to this edge?
Operational state How the network is configured and energised now.
Switching state
Open and closed states of switches and valves at a point in time.
Current configuration
The state of each switching element and its time of validity.
- Is this switch or valve open or closed, and since when?
- Who or what changed the state, under which work order or command?
Connectivity result
Which parts are connected to a source under the current state.
- Which customers or service points are fed from which source under the current state?
- Which parts of the network are isolated or de-energised?
Validity and change Keeping the model true to the field.
Model currency
How up to date the topology is against as-built records.
As-built alignment
Agreement between model and field.
- When was this part of the topology last checked against as-built records?
- Which pending changes from works are not yet reflected in the model?
Classifiers Filled
- Family
- World Models
- Category
- Physical world and living systems
- Entry kind
- entity
- Navigation path
- NAV.PHY.BLT.NET
- Domain
- PHY.BLT.NET
- Industry
- Cross-industry
- Tags
- utilitynetworktopologyphy.blt.net
What it is Filled
A utility network topology is the connectivity model of a utility network: its nodes, the edges that join them and the operational state that decides which parts are connected at a given time. It covers electricity, gas, water, district heat and telecom networks as graphs; the individual assets and their condition are described in their own models.
In scope
- Graph identity, node and terminal incidence, links and network boundaries.
- Utility profiles, state assertions, uncertainty, geometry references and time-qualified revisions.
- Proposed local connectivity analysis, provenance, validation, exchange mappings and governed artifacts.
Out of scope
- Physical asset condition, construction, maintenance work execution and ownership registers.
- Live actuation, switching instructions, excavation clearance and safe-work certification.
- Hydraulic, power-flow or communications performance solvers and guaranteed delivered service.
- Customer/account records, universal sector conformance and production-ready instance schemas.
Why it exists Filled
Describe an operator-governed utility connectivity model, its revisions, state evidence and qualified derived graph views.
Distinguishing features Filled
- Describes connectivity and switching state, not the physical condition of individual assets.
- The same physical network yields different connected graphs as switches and valves change state.
- Narrower than the physical infrastructure network, which also covers assets, ownership and construction.
- Distinct from a service point, which is the delivery end where a customer is connected.
What robots and AI may and may not do Filled
Must not
- Issue switching or valve commands to live networks without an authorised operator.
- Overwrite the recorded switching history instead of appending new states.
- Publish detailed topology of critical infrastructure beyond authorised recipients.
- Treat a modelled isolation as proof that a section is safe to work on.
- Merge unverified field reports into the operational model as fact.
Only with a human decision
- Executing switching or isolation on a live network.
- Accepting model changes from works into the operational topology.
- Releasing detailed topology to external parties.
May
- Read the topology and compute connectivity, feeding paths and affected customers.
- Record switching states reported by control systems with their time of validity.
- Flag differences between the model and as-built or field records.
- Simulate switching plans for review without executing them.
Moral aspects Filled
- Topology errors can lead to work on live equipment and endanger crews and the public.
- Detailed network maps are sensitive because they reveal critical infrastructure weak points.
- Outage planning based on the topology affects vulnerable customers who depend on supply.
Who is affected
- Field crews and network operators
- Customers connected to the network
- Customers who depend on supply for medical equipment
- Emergency services
Owners Filled
Steward
The network operator's network data or GIS manager who answers for the connectivity model.
Roles
- Network data steward
- Maintains graph identity, scope, profiles and candidate edits.
- Configuration reviewer
- Reviews incidence and state interpretation evidence before baseline acceptance.
- Evidence custodian
- Maintains provenance, freshness, retention schedules and record integrity.
- Authorized analyst
- Runs only permitted local analyses and reports uncertainty and use limits.
- Release approver
- Approves scoped disclosure and redaction; operational authority remains separately governed.
Master systems
- Geographic information system for the network
- Distribution or network management system
- Asset register
Links to other meta-models Filled
references
- WM-BLT-003 - Candidate physical-network master binding reconciles registry parent_ids; require deployment-specific identity/version pinning before use.
- WM-BLT-009 - Candidate physical segment binding; no inherited asset lifecycle or mandatory one-to-one mapping.
aligned
- OGC MUDDI Part 1 1.0 - Conceptual underground-network, identity and spatial alignment only; no conformance assertion.
- INSPIRE Utility Networks 3.2.0 - Optional spatial-network exchange mapping with missing topology explicitly represented.
- IEC CIM and selected CGMES profile - Electricity-only semantic mapping with explicit profile/version and reduction rules; not a generic utility implementation.
- PROV-O - Conceptual provenance mapping for revisions, observations and derived artifacts.
neighbor
- WM-BLT-003 Infrastructure Network - The registry parent is reconciled as a physical-network context reference, not mandatory inheritance or asset containment. This model masters one digital connectivity representation.
- WM-BLT-009 Linear Infrastructure Asset - Physical segment identity, condition and ratings remain external; a graph link and a physical segment need not map one-to-one.
- State observation and physical simulation masters - This model stores attributed assertions and bounded graph derivations. Measured or simulated pressure, flow and energization need their own evidence and domain algorithms.
- Service points and operating authority - Optional endpoint references do not import customer data or authorize physical operation. Modeling evidence cannot replace field safety procedures.
parent
- WM-BLT-003
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Nodes and edges are identified by the operator's asset or feature identifiers.
- A topology version is identified by its network, its time of validity and the source system.
Direct properties required Filled
- Edge length in metres, measured along the route.
- Rated capacity of an edge in amperes, cubic metres per hour or bit per second, depending on the utility.
- Nominal voltage in kilovolts or nominal pressure in bar at a node or edge.
- Switching state as open or closed, with the time it was last confirmed.
- Location coordinates with a stated coordinate reference system and positional accuracy in metres.
Recognition required Filled
- In the field, nodes appear as substations, cabinets, valves, hydrants or chambers with operator labels.
- Buried edges are recognised from markers, covers and as-built plans rather than direct sight.
- Easily confused with a network of a different utility sharing the same trench or pole.
Capabilities and actions required Filled
- Trace upstream and downstream from any node under the current switching state.
- Compute customers affected by an outage or planned isolation.
- Compare topology versions over time.
Hazards and failure modes required Filled
- Wrong switching state in the model can lead crews to treat live equipment as dead.
- Stale topology misroutes emergency isolation.
- Leaked topology data can help attackers target critical points.
Standards and interfaces required Filled
- IEC Common Information Model (IEC 61970 and IEC 61968) for electricity networks.
- OGC CityGML Utility Network ADE and OGC GeoPackage for geospatial exchange.
- INSPIRE Utility and Governmental Services data specification in the EU.
Context of use required Filled
- Used in network operation, outage management, planning and excavation enquiries.
- Critical infrastructure protection rules restrict who may receive detailed data.
Sources Filled
- OGC MUDDI Part 1: Conceptual Model - Open Geospatial Consortium
- INSPIRE Utility and Government Services Technical Guidelines - European Commission - INSPIRE Maintenance and Implementation Group
- EPANET 2.2 User Manual - United States Environmental Protection Agency
- CGM Building Process Implementation Guide AC and DC Part - European Network of Transmission System Operators for Electricity
- IEC 61970-301 Common Information Model base - International Electrotechnical Commission
- PROV-O: The PROV Ontology - World Wide Web Consortium
- RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force
- Guide to Operational Technology Security - National Institute of Standards and Technology
- IEC 61970 and IEC 61968 Common Information Model, International Electrotechnical Commission
- INSPIRE Directive 2007/2/EC, European Parliament and Council
Open questions
- Verify source responses, exact source editions, normative access, reuse rights and adopting-jurisdiction applicability without interpreting HTTP success as claim verification.
- Develop specialist utility profiles and fixtures for empty/partial graphs, multi-terminal devices, parallel links, redacted interfaces, stale states, conflicting reports and scenario branching.
- Implement and test nested instance bindings, profile-specific graph processing, identity-preserving mappings and retention/access propagation before operational use.
- Restore independent external review before any canonical or publishable-draft promotion.
- Gas, district heat, sewer and telecommunications operational profiles require specialist evidence and fixtures.
- Nested instance schemas, graph algorithms, adapters and mapping/conformance tests are not implemented.
- Live source/version closure and independent external review remain outstanding.
- Profile-specific rules for phase/circuit propagation, internal devices, capacity and operational safety are delegated, not supplied.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-blt-010-utility-network-topology/spec.yaml, ver-cy/world-models/card-supplements/wm-blt-010-utility-network-topology.json