Utility Service Point
Connections for water, heat, power, sewage
Bundle → Layer → Finding → Questions Incomplete
3 bundles · 6 layers · 0 findings · 0 questions
connection Where and how a served place ties into a network
servicePoints
the delivery points where service is handed over
physicalConnections
the pipe or cable from network segment to service point
metering How delivery is measured
meters
measuring devices registered at service points
readings
dated values taken from meters
supply Whether and on what terms supply is active
supplyStatus
active, disconnected and suspended spells
tariffReference
pointers to externally governed tariff schemes
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.UTL
- Domain
- PHY.BLT.UTL
- Industry
- Cross-industry
- Tags
- utilityservicepointphy.blt.utl
- Also called
- U5
What it is Derived, awaiting review
This meta-model describes the points where utility networks meet the places they serve: connections for water, heat, power and sewage, the meters registered at them, readings, supply status and the tariff scheme in force.
Note: First sentence of the legacy card introduction.
Why it exists Filled
Connections for water, heat, power, sewage
Distinguishing features Derived, awaiting review
- It is its own model because service points churn (connect, disconnect, re-meter) on a different cadence than the long-lived network assets (U3) and the premises they serve (U2), and because consumption data carries its own consent regime.
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 Derived, awaiting review
- It is its own model because service points churn (connect, disconnect, re-meter) on a different cadence than the long-lived network assets (U3) and the premises they serve (U2), and because consumption data carries its own consent regime.
Owners Filled
Steward
The owner archetype is the utility operator, which stewards service points, connections and meters for its service kind.
Links to other meta-models Filled
references
- world.premisesSpatialUnit - the served premises; occupancy context lives there
- world.physicalInfrastructureNetwork - the tapped segments and their capacity
- world.buildingStructure - service points serving whole buildings or sites
- world.person - the served party in a supply spell
- world.organization - organizational customers and supplying operators
requires
- vr.wm-blt-002
- vr.wm-blt-003
- vr.wm-blt-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
- connectionEnergized: a new connection was made live and delivery became possible
- meterInstalled: a meter was registered at a service point
- meterExchanged: a meter was replaced and closing/opening readings recorded
- readingTaken: a dated reading was captured from a meter
- supplyDisconnected: supply at a service point was cut off
- supplyReconnected: supply at a service point was restored
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
- consumptionAccessGrant: the served party consents per S2 to share consumption data with a named consumer
- supplierSwitchExchange: the data exchange executed when the supplying party at a service point changes
- aggregateLoadLicense: release of anonymized, aggregated load data to network and settlement planners
- billingProjection: readings and tariff references needed for settlement; omits network topology
- networkLoadProjection: aggregate demand per segment for U3 planning; omits customer identity
- premisePassportProjection: which services a premise is connected to; omits consumption values
Context of use required Filled
- Consumption data is disclosed only with the served party's S2 grant; aggregate releases are anonymized, and all disclosures are 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-u5-utility-service-point/spec.yaml, models/docs/built-environment/U5-utility-service-point.md