← Catalogue
World Models · legacy example

Utility Service Point

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. 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.

AI YAMLAGENTS.mdSource
IDworld.u5-utility-service-point
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainbuilt-environment
Tagsutility, service, point
Data structure

Bundles and layers

Bundle

connection

Where and how a served place ties into a network

Layers

servicePoints`: the delivery points where service is handed over · `physicalConnections`: the pipe or cable from network segment to service point

Bundle

metering

How delivery is measured

Layers

meters`: measuring devices registered at service points · `readings`: dated values taken from meters

Bundle

supply

Whether and on what terms supply is active

Layers

supplyStatus`: active, disconnected and suspended spells · `tariffReference`: pointers to externally governed tariff schemes

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.premisesSpatialUnit` (U2): the served premises; occupancy context lives there
  • REFERENCE `world.physicalInfrastructureNetwork` (U3): the tapped segments and their capacity
  • REFERENCE `world.buildingStructure` (U1): service points serving whole buildings or sites
  • REFERENCE `world.person` (H1): the served party in a supply spell
  • REFERENCE `world.organization` (O1): organizational customers and supplying operators
  • imports: iec-cim (EXTEND: usage point and metering semantics)
  • imports: dlms-cosem (ALIGN: meter reading exchange semantics)

Canon, patches & standards

  • REFERENCE `world.premisesSpatialUnit` (U2): the served premises; occupancy context lives there
  • REFERENCE `world.physicalInfrastructureNetwork` (U3): the tapped segments and their capacity
  • REFERENCE `world.buildingStructure` (U1): service points serving whole buildings or sites
  • REFERENCE `world.person` (H1): the served party in a supply spell
  • REFERENCE `world.organization` (O1): organizational customers and supplying operators
  • imports: iec-cim (EXTEND: usage point and metering semantics)
  • imports: dlms-cosem (ALIGN: meter reading exchange semantics)

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `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

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The owner archetype is the utility operator, which stewards service points, connections and meters for its service kind. Consumption data is disclosed only with the served party's S2 grant; aggregate releases are anonymized, and all disclosures are auditable via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `servicePoint`: the delivery point where a utility service is handed over to a served premise or site; key attributes: serviceKind, status, commissionedAt
  • `physicalConnection`: the pipe or cable tie from a network segment to the service point; key attributes: capacity, length, installedYear
  • `meter`: a measuring device registered at a service point; key attributes: meterKind, accuracyClass, installedAt
  • `meterReading`: a dated value taken from a meter; key attributes: readAt, value, unit, readingMethod
  • `supplySpell`: a continuous period of active supply at a service point; key attributes: startAt, endAt, supplyBasis
  • `tariffReference`: a pointer to an externally governed tariff scheme applying at a service point; key attributes: schemeRef, term, validFrom

Relationships

  • `servicePoint` -> serves -> `premise` (n:1): a service point delivers to a premise, building or site modelled in U2/U1
  • `physicalConnection` -> taps -> `segment` (n:1): the U3 segment the connection draws from
  • `physicalConnection` -> feeds -> `servicePoint` (1:1): each connection terminates in one delivery point
  • `meter` -> installedAt -> `servicePoint` (n:1): meters succeed one another at the same point over time
  • `meterReading` -> takenFrom -> `meter` (n:1): the reading history of a device
  • `supplySpell` -> under -> `tariffReference` (n:1): each active spell runs under one tariff term at a time

Events

  • `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

Projections

  • `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