← Catalogue
World Models · legacy example

Energy

This meta-model describes energy as it flows through the world: the carriers energy takes (electricity, gas, heat, fuels), the sources that generate or transform it, the points that consume it, and the continuous reconciliation of supply and demand across balance areas. It is its own model because energy obeys network physics and balance identities: quantities must reconcile per carrier, per area and per settlement period, a discipline that generic goods or financial models do not carry.

AI YAMLAGENTS.mdSource
IDworld.f1-energy
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainflows-resources
Tagsenergy
Data structure

Bundles and layers

Bundle

carrier

What energy is and how it is measured

Layers

carrierTypes`: catalogue of carriers (electricity, gas, heat, hydrogen, liquid fuels) and their physical qualities · `unitsAndConversion`: energy content units and conversion rules between carriers

Bundle

production

Where energy enters or changes form

Layers

generationAssets`: generating units, their technology and capacity · `transformation`: conversion processes between carriers (refining, gas to power, power to heat)

Bundle

consumption

Where energy is drawn

Layers

demandAndLoad`: consumption points, sectors and load profiles · `metering`: quantified readings at delivery points

Bundle

balance

Reconciling supply and demand

Layers

gridBalance`: balance areas and settlement periods · `storageAndReserves`: buffering of carriers over time · `interchange`: scheduled and measured flows between areas

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.landParcel` (P2): generation, storage and network assets are sited on identified parcels.
  • REFERENCE `world.organization` (O1): operators of assets and balance areas are organizations governed elsewhere.
  • REFERENCE `world.emission` (F6): fuel combustion and process activity recorded here serves as activity data for emission quantification.
  • COMPOSE `world.money` (F2): imbalance settlement amounts embed the money value object rather than local amount fields.
  • imports: IEC CIM (ALIGN): field equivalences for grid assets, measurement and network semantics.
  • imports: IEA energy balances (ALIGN): definitions of aggregate balance categories and carrier accounting.

Canon, patches & standards

  • REFERENCE `world.landParcel` (P2): generation, storage and network assets are sited on identified parcels.
  • REFERENCE `world.organization` (O1): operators of assets and balance areas are organizations governed elsewhere.
  • REFERENCE `world.emission` (F6): fuel combustion and process activity recorded here serves as activity data for emission quantification.
  • COMPOSE `world.money` (F2): imbalance settlement amounts embed the money value object rather than local amount fields.
  • imports: IEC CIM (ALIGN): field equivalences for grid assets, measurement and network semantics.
  • imports: IEA energy balances (ALIGN): definitions of aggregate balance categories and carrier accounting.

Artifact formats & serial data

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

Policies & accepted processes

  • `meteringDataAccess`: a consumption point owner or their delegate reads interval meter data for that point.
  • `aggregateBalanceFeed`: a consumer receives per-area, per-period balance aggregates without per-meter detail.
  • `assetRegisterLookup`: resolution of a generation or storage asset's descriptive record by identifier.

Read / add / edit / delete

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

Ownership, roles & access

Grid and asset operators steward the records of their own assets, meters and balance areas, and a statistics office archetype stewards the published aggregates. Access to any record is granted by its steward through the catalogue's S1/S2 ownership and access models, with usage auditable via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `energyCarrier`: a form in which energy is held or moved; key attributes: carrierType, physicalState, energyContentUnit.
  • `generationSource`: a unit that produces a carrier (plant, turbine, panel array); key attributes: technology, capacity, commissioningDate, siteRef.
  • `transformationProcess`: a conversion between carriers; key attributes: inputCarrier, outputCarrier, conversionEfficiency.
  • `consumptionPoint`: a delivery point where energy is drawn; key attributes: sector, connectionCapacity, profileClass.
  • `meterReading`: a quantified measurement at a point over an interval; key attributes: quantity, unit, interval, qualityFlag.
  • `storageFacility`: a buffer that shifts a carrier over time; key attributes: storageCapacity, roundTripEfficiency, stateOfCharge.
  • `balanceArea`: a grid zone or territory over which supply and demand are reconciled; key attributes: areaCode, carrier, settlementPeriod.
  • `interchangeFlow`: a scheduled or measured flow between two balance areas; key attributes: direction, quantity, period.

Relationships

  • `generationSource` -> produces -> `energyCarrier` (n:m): which carriers a unit can deliver.
  • `transformationProcess` -> converts -> `energyCarrier` (n:m): input and output carriers of a conversion.
  • `consumptionPoint` -> draws -> `energyCarrier` (n:1): the carrier delivered at a point.
  • `balanceArea` -> aggregates -> `generationSource` (1:n): units settled within an area.
  • `balanceArea` -> aggregates -> `consumptionPoint` (1:n): delivery points settled within an area.
  • `storageFacility` -> buffers -> `energyCarrier` (n:1): the carrier a facility stores.
  • `interchangeFlow` -> links -> `balanceArea` (n:2): the exporting and importing areas of a flow.

Events

  • `generationRecorded`: a generating unit delivered a quantified amount of a carrier in a period.
  • `consumptionMetered`: a meter reading was taken at a consumption point.
  • `outageOccurred`: a generation, storage or network asset became unavailable.
  • `storageCharged`: a storage facility absorbed energy from the system.
  • `storageDischarged`: a storage facility returned energy to the system.
  • `interchangeExecuted`: a flow between balance areas was delivered and measured.
  • `balancePeriodClosed`: supply, demand, storage and interchange were reconciled for an area and period.

Projections

  • `publicEnergyBalance`: national and area-level supply and demand aggregates by carrier; omits all per-asset and per-meter data.
  • `gridOperationsView`: near-real-time state of areas, assets and interchange for operations; omits commercial and personal attributes.
  • `consumerUsageView`: a single holder's own consumption points and readings; omits everything else.