{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-blt-010","code":"wm-blt-010-utility-network-topology","url":"https://ver.cy/models/wm-blt-010-utility-network-topology/","name":"Utility Network Topology","alternateNames":[],"kind":"world-model","status":"todo","version":"unversioned","language":"en","classifiers":{"family":"World Models","category":"Physical world and living systems","entryKind":"standalone-mm","plane":"","domain":["PHY.BLT.NET"],"industry":["Cross-industry"],"navPath":"NAV.PHY.BLT.NET","tags":["utility","network","topology","phy.blt.net"],"facets":{}},"whatItIs":"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.","purpose":"Nodes, edges, connectivity and operational state","scope":{"in":[],"out":[],"boundaries":[]},"distinguishingFeatures":["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."],"structure":{"bundles":[{"id":"BLT010-B1","name":"Network elements","description":"The nodes and edges that make up the graph.","layers":[{"id":"BLT010-B1-L1","name":"Nodes and edges","description":"Points and links of the network with their asset references.","findings":[{"id":"BLT010-F01","name":"Node identity","description":"A connection point with its type and the asset it represents.","questions":[{"text":"Which asset or connection point does this node represent, and of which type?","id":"BLT010-Q01"},{"text":"Where is the node located, and in which coordinate reference system?","id":"BLT010-Q02"}]},{"id":"BLT010-F02","name":"Edge connectivity","description":"A link between two nodes with its direction and capacity.","questions":[{"text":"Which two nodes does this edge connect, and is flow directed?","id":"BLT010-Q03"},{"text":"What rated capacity and length apply to this edge?","id":"BLT010-Q04"}]}]}]},{"id":"BLT010-B2","name":"Operational state","description":"How the network is configured and energised now.","layers":[{"id":"BLT010-B2-L1","name":"Switching state","description":"Open and closed states of switches and valves at a point in time.","findings":[{"id":"BLT010-F03","name":"Current configuration","description":"The state of each switching element and its time of validity.","questions":[{"text":"Is this switch or valve open or closed, and since when?","id":"BLT010-Q05"},{"text":"Who or what changed the state, under which work order or command?","id":"BLT010-Q06"}]},{"id":"BLT010-F04","name":"Connectivity result","description":"Which parts are connected to a source under the current state.","questions":[{"text":"Which customers or service points are fed from which source under the current state?","id":"BLT010-Q07"},{"text":"Which parts of the network are isolated or de-energised?","id":"BLT010-Q08"}]}]}]},{"id":"BLT010-B3","name":"Validity and change","description":"Keeping the model true to the field.","layers":[{"id":"BLT010-B3-L1","name":"Model currency","description":"How up to date the topology is against as-built records.","findings":[{"id":"BLT010-F05","name":"As-built alignment","description":"Agreement between model and field.","questions":[{"text":"When was this part of the topology last checked against as-built records?","id":"BLT010-Q09"},{"text":"Which pending changes from works are not yet reflected in the model?","id":"BLT010-Q10"}]}]}]}]},"agentConduct":{"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."],"mustNot":["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."],"requiresHuman":["Executing switching or isolation on a live network.","Accepting model changes from works into the operational topology.","Releasing detailed topology to external parties."]},"ethics":{"considerations":["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."],"affectedParties":["Field crews and network operators","Customers connected to the network","Customers who depend on supply for medical equipment","Emergency services"]},"owners":{"steward":"The network operator's network data or GIS manager who answers for the connectivity model.","roles":[],"masterSystems":["Geographic information system for the network","Distribution or network management system","Asset register"]},"relations":[{"target":"WM-BLT-003","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["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."]},"properties":{"applicability":"required","items":["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":{"applicability":"required","items":["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":{"applicability":"required","items":["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":{"applicability":"required","items":["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."]},"interfaces":{"applicability":"required","items":["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":{"applicability":"required","items":["Used in network operation, outage management, planning and excavation enquiries.","Critical infrastructure protection rules restrict who may receive detailed data."]}},"sources":[{"title":"IEC 61970 and IEC 61968 Common Information Model, International Electrotechnical Commission"},{"title":"INSPIRE Directive 2007/2/EC, European Parliament and Council"}],"openQuestions":["Planned model: boundary questions, research and every section remain to be written."],"resources":{"spec":"https://ver.cy/models/wm-blt-010-utility-network-topology/spec.yaml","agents":"https://ver.cy/models/wm-blt-010-utility-network-topology/AGENTS.md"},"provenance":{"origin":"planned (registry candidate)","builtFrom":["models/runtime-index.json","ver-cy/world-models/card-supplements/wm-blt-010-utility-network-topology.json"],"providers":[],"researchStatus":"todo","generatedAt":"","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"filled","structure":"filled","agentConduct":"filled","ethics":"filled","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"filled","interaction.recognition":"filled","interaction.capabilities":"filled","interaction.hazards":"filled","interaction.interfaces":"filled","interaction.context":"filled","sources":"filled"},"notes":{"_":"Planned entry, hidden from the catalogue until researched.","_supplement":"Sections authored in card supplement 1.0.0 by Claude (Opus 5.5) (2026-10-06, unreviewed). Written from the card's existing content and established practice in the field; no new sources were read. Unreviewed."},"score":1.0}}