Skip to main content

Aggregations and Calculations

What it does​

Grid operators and energy communities need totals that no single meter measures: the load on a transformer or a feeder, the consumption and production of a community, and how much of a community's solar production each household actually used. Aggregations and Calculations produces these figures from the validated VEE data on a schedule, stores them as datasources of their own and keeps them current as members join or leave. It comes as two packages, one for energy communities and one for network areas.

Energy communities​

  1. Assign members. Households and shared production installations, for example a solar roof, are assigned to a community with a dated tag through a ready-made CSV import. Membership has a validity period, so a household can join or leave on a given date or switch to another community.
  2. Aggregate. A daily and a monthly schedule sum the consumption and the production of all members over the period, for exactly the time each one was a member, and store the totals on the community datasource.
  3. Calculate. A second daily and monthly schedule calculates how much of the production was used within the community and allocates it to the members, splitting each household's consumption into self-delivered and grid-delivered energy.
  4. Formulas on virtual metering points. Calculations that combine channels of several datasources are expressed as formulas in a tag on the result datasource: arithmetic, comparisons, minimum, maximum, mean, sum, count, rounding and if-then-else conditions. The standard calculation flow evaluates them for the ingested period.

Network areas​

  1. Know the topology. Each metering point carries its network area, such as a transformer, a feeder or a substation, in its network contract tag.
  2. Aggregate. A daily and a monthly schedule sum the delivery and the redelivery of all metering points per network area and keep an aggregated quality status, so that a total that rests on estimates is recognisable as such.
  3. Store. The results are ingested onto the network-area datasources, where they can be charted, exported and used in further calculations like any other datasource.

What you see​

  • Community and network-area datasources with their aggregated channels in the datasource view, next to the member meters.
  • Per household, the split between self-consumption and grid consumption as channels of its own.

What you can configure​

  • The schedules (daily, monthly) and their time zone.
  • The community membership of each household and installation, with validity dates.
  • The formulas and the destination channel of each calculation.
  • Which channels are aggregated per network area.

Verified behaviour​

The package ships with automated acceptance scenarios that run against a live environment. Among others, they cover:

  • a community set-up of 30 households, 3 solar installations and 2 communities, with the daily aggregation and calculation checked datapoint by datapoint;
  • households that joined the community at different times, and households that switch communities;
  • a household that leaves one community and joins another;
  • the daily and the monthly network-area aggregation, including the aggregated quality status.

Standard rules in this module​

RuleWhat it does
Standard Formulae CalculationEvaluates the formulas configured on the calculation tags of a datasource over the ingested period.

The aggregations themselves run as scheduled queries (trigger schedules) whose results are ingested back onto the community and network-area datasources.

Extending the module​

  • Add aggregation levels such as building, street or substation by adding a tag and a schedule.
  • Use virtual datasources for ad-hoc aggregations over any tag-based selection.
  • Replace the proportional allocation of community production with your own allocation key as a formula.

Installation and updates: standard-packages.