AggregateConsumptionRecord@1

Node AggregateConsumptionRecord@1 parses an EDA consumption record (DATEN_CRMSG) and aggregates the energy quantities of one meter code to daily values. The days are determined in the time zone Central Europe (Vienna).

The node selects the meter code as follows:

• Consumption: if the message contains quantities for 1-1:2.9.0 G.03, these are aggregated.
• Production: otherwise, if the message contains quantities for 1-1:2.9.0 G.01T, the matching quantities of 1-1:2.9.0 P.01T (same period, same From/To) are subtracted and the result is aggregated. Production blocks without a matching P.01T block are skipped.

Adapter Prerequisites

• EDA Adapter

Node Configuration

For fields path, targetPath, targetValueWriteMode, and targetValueKind, see Overview.

  transformations:
    - type: AggregateConsumptionRecord@1
      path: $.message.RawMessage # raw XML of the consumption record
      meteringPointRtIdPath: $.meteringPoint.RtId # RtId of the metering point entity
      targetPath: $.energyData

Property	Type	Required	Default	Description
path	string	No	$	Path to the raw XML of the consumption record
meteringPointRtIdPath	string	Yes¹	-	Path to the RtId of the metering point the quantities belong to
targetPath	string	No	$	Path where the list of aggregated EnergyData objects is written

¹ Not marked as required in the schema, but enforced at runtime: without meteringPointRtIdPath the node fails with MeteringPointRtIdPath must be set in the configuration.

Behavior

• If the raw XML is empty or missing, or no RtId is found at meteringPointRtIdPath, the node writes nothing and the pipeline continues.
• If the message contains neither consumption nor production quantities, nothing is written.
• Per day, From is the earliest start, To the latest end, Quantity the sum and Quality the highest quality value (L3 before L2 before L1) of the quantities of that day.

Output

A list of EnergyData objects (see ParseConsumptionRecord@1) with one energy quantity per day. CreationTime is the DocumentCreationDateTime of the message; MeterCode and QuantityUnit are not set.

The configuration properties are documented in the API reference.

Complete sample of pipeline configuration

  triggers:
    - type: FromPipelineDataEvent@1
  transformations:
    - type: AggregateConsumptionRecord@1
      path: $.message.RawMessage
      meteringPointRtIdPath: $.meteringPoint.RtId
      targetPath: $.energyData
    - type: FilterEnergyData@1
      path: $.energyData
      targetPath: $.energyData