← Back to catalogue
Previous version

Physical Infrastructure Network

vr.wm-blt-003 · world-u3-physical-infrastructure-network

Roads, rail, pipes, grids as physical networks

World Models Physical world and living systems PHY.BLT.NET

Bundle → Layer → Finding → Questions Incomplete

3 bundles · 8 layers · 0 findings · 0 questions

topology The physical shape and connectivity of the network

segments

linear stretches between nodes

nodes

junctions, switches, substations, terminals

connectivity

how segments and networks join

linearReferencing

positions along segments from a datum

capacity What the network can carry and how loaded it is

ratedCapacity

engineering statements of carrying capability

utilization

observed load against rating

assetCondition The physical state and upkeep of assets

condition

dated condition surveys and grades

maintenance

planned regimes and completed upkeep

Note: Legacy card: layers named, findings and questions never written.

Classifiers Filled

Family
World Models
Category
Physical world and living systems
Entry kind
standalone-mm
Navigation path
NAV.PHY.BLT.NET
Domain
PHY.BLT.NET
Industry
Cross-industry
Tags
infrastructurenetworkphy.blt.net
Also called
U3

What it is Derived, awaiting review

This meta-model describes roads, rail, pipes, grids and cables as physical networks: the topology of segments and nodes, their rated capacity and utilization, and their asset condition and maintenance.

Note: First sentence of the legacy card introduction.

Why it exists Filled

Roads, rail, pipes, grids as physical networks

Distinguishing features Derived, awaiting review

  • It is its own model because the physical asset base persists across operators and service arrangements, and its topology is the shared substrate that service points (U5), settlements (U4) and incidents (X3) all reference.

What robots and AI may and may not do Missing, in the backlog

Not described yet. This gap is in the card backlog.

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Filled

Steward

The owner archetype is the operator organization: the operator of each network stewards its asset records, and several operators can steward different networks over the same territory.

Links to other meta-models Filled

references

  • world.buildingStructure - carrying structures such as bridges and tunnels are modelled there
  • world.utilityServicePoint - where end users tap the network; supply semantics live in U5
  • world.settlementUrbanForm - segments traverse settlements and districts modelled there
  • world.landParcelCadastre - rights of way and easements over parcels are resolved in the cadastre
  • world.incidentEmergency - incidents affecting network assets are recorded there and mirrored as closure events here

requires

  • vr.wm-act-019
  • vr.wm-blt-004
  • vr.wm-blt-005
  • vr.wm-plc-005

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Missing, in the backlog

Not described yet. This gap is in the card backlog.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Derived, awaiting review

  • segmentCommissioned: a new segment entered service
  • segmentDecommissioned: a segment was permanently withdrawn from service
  • capacityRerated: a segment or node received a new capacity rating
  • conditionSurveyed: a condition survey was completed and graded
  • maintenanceCompleted: planned or corrective upkeep was finished on an asset
  • closureOccurred: a segment was temporarily closed or out of service

Legacy events listed as state transitions.

Hazards and failure modes optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Derived, awaiting review

  • openNetworkMapLicense: public release of simplified topology for mapping and routing
  • interOperatorExchange: exchange of connectivity and capacity data at interconnection points between operators
  • conditionDataAccess: operator-granted access to condition surveys for engineers, insurers or works planners
  • routingGraphProjection: topology and capacity as a graph for pathfinding; omits condition and maintenance detail
  • assetRegisterProjection: assets with age, condition grade and maintenance state; omits utilization
  • publicMapProjection: simplified geometry and classification for general maps; omits operationally sensitive attributes

Context of use required Filled

  • Access to condition and capacity detail is granted by the operator through S2, with disclosures auditable via S4.

Sources Missing, in the backlog

Not described yet. This gap is in the card backlog.

Open questions

  • Superseded by a researched world model? Map this legacy card to its successor or retire it.

Machine files

Provenance

legacy MMAS card (world-models v0.2) · legacy

Built from: models/world-u3-physical-infrastructure-network/spec.yaml, models/docs/built-environment/U3-physical-infrastructure-network.md