Aggregate energy data

1. Description of the Use Case

1.1. Name of the Use Case

IDArea /Domain(s)/Zone(s)Name of the Use Case
1Access to data, Balance management, Market for flexibilities, Operational planning and forecasting, Services related to end customers,elering-1

1.2. Version Management

Version No.DateName of author(s)ChangesApproval status
12018-04-12T00:00:00Kalle Kukk (Elering),
22018-10-03T00:00:00Ricardo Jover (EDF),UML model
32018-10-04T00:00:00Eric Suignard (EDF),Version post WP5&9 physical meeting in Tallinn
42018-10-11T00:00:00Ricardo Jover (EDF),Assumptions concerning users of the Application
²²2019-05-07T00:00:00Eric Suignard (EDF),WP6-7-8 demos alignment and miscellaneous changes
62020-06-16T00:00:00Eric Suignard (EDF),innogy’s and Elering’s review

1.3. Scope and Objectives of Use Case

ScopeAggregation of different types of data made available through data exchange platform
Objective(s)Making private data available to other parties without authorization (permission) requirement.
Related business case(s)

1.4. Narrative of Use Case

Short description

Data Exchange Platforms can support data aggregation by transporting aggregated data from a data source to an application. Aggregation itself takes place at data source. Aggregated data may be useful for different applications (services) – e.g. related to benchmarking, national statistics, imbalance reporting. Also, aggregated data would not require consent (permission rights) for personal data or commercially sensitive data.

Complete description

1.5. Key Performance Indicatiors (KPI)

IDNameDescriptionReference to mentioned use case objectives

1.6. Use case conditions

Same aggregation method could be applied for data sets in different countries to ensure the comparability in case requested by a party.
Aggregation method used shall not enable the identification of the individual behind the personal data or organization behind the commercially sensitive data

1.7. Further information to the use case for classification/mapping

Relation to other use cases
Level of depth
Generic, regional or national relation
Nature of the use cases
Further keywords for classification

1.8. General remarks

General remarks

2. Diagrams of Use Case

Aggregate energy data - overview Aggregate energy data - scenarios flowchart

3. Technical Details

3.1. Actors

Actor NameActor TypeActor DescriptionFurther information specific to this Use Case
ApplicationSystemAny kind of system connected to a Data Exchange Platform and used by a market participant who wishes to receive data.
Data Exchange PlatformSystemData exchange platform (DEP) is a communication platform the basic functionality of which is to secure data transfer (routing) from data providers (e.g. data hubs, flexibility service providers, TSOs, DSOs) to the data users (e.g. TSOs, DSOs, consumers, suppliers, energy service providers). DEP stores data related to its services (e.g. cryptographic hash of the data requested). The DEP does not store core energy data (e.g. meter data, grid data, market data) while these data can be stored by data hubs. Several DEPs may exist in different countries and inside one country.
Data HubSystemData Hub is an information system which main functionality is to store and make available measurements (e.g. meter data, operational data) and associated master data. Data Hubs are not necessarily centralized in a country or in a region.
Foreign Customer PortalSystemCustomer Portal for another country.
Can also mean a separate portal in the same country.
Data Hub OperatorBusinessData hub operator owns and operates an information system which main functionality is to store and make available electricity (also gas, heat) metering data and associated master data. Can be :
  • Grid Data Hub Operator in the sphere of a System Operator
  • Market Data Hub Operator in the sphere of a Market Operator
  • Meter Data Hub Operator in the sphere of a Metered Data Operator
  • Sub-meter Data Hub Operator in the sphere of an Energy Service Provider
DEP OperatorBusinessData exchange platform operator owns and operates a communication system which basic functionality is data transfer.

3.2. References

No.References TypeReferenceStatusImpact on Use CaseOrganistaor / OrganisationLink

4. Step by Step Analysis of Use Case

4.1. Overview of Scenarios

No.Scenario NameScenario DescriptionPrimary ActorTriggering EventPre-ConditionPost-Condition
1Request aggregated data


4.2. Steps – Scenarios

Scenario Name:
Request aggregated data
Step No.Event.Name of Process/ ActivityDescription of Process/ Activity.ServiceInformation Producer (Actor)Information Receiver (Actor)Information ExchangedRequirements, R-ID
1.1Aggregates data43ac67ff-35a0-48e4-8b2c-d1eaf753729276bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5
1.2Forwards aggregated data5351ac19-9ec2-47b9-9ead-4a28907df04576bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5
1.3Forwards aggregated data4e694b8b-e0eb-4b2a-ae7a-1bcb6f65638576bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5
1.4Forwards aggregated data request
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
4e694b8b-e0eb-4b2a-ae7a-1bcb6f65638543ac67ff-35a0-48e4-8b2c-d1eaf753729297336539-bfa7-4501-b370-ff9d6d4bf68176bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5
1.5Forwards aggregated data request
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
5351ac19-9ec2-47b9-9ead-4a28907df04543ac67ff-35a0-48e4-8b2c-d1eaf753729297336539-bfa7-4501-b370-ff9d6d4bf68176bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5
1.6Requests aggregated data
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
3b6d4cd1-7cd7-473e-af25-2cd3f990d4154e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 5351ac19-9ec2-47b9-9ead-4a28907df04597336539-bfa7-4501-b370-ff9d6d4bf68176bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5
1.7Sends aggregated data43ac67ff-35a0-48e4-8b2c-d1eaf753729276bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5

5. Information Exchanged

Information exchanged IDName of InformationDescription of Information ExchangedRequirement
97336539-bfa7-4501-b370-ff9d6d4bf681Any Data—-

6. Requirements (optional)

Category IdentifierNameDescriptionmRID
Cat1Task 5.3Requirements integrated from Task 5.3.1880e39c-7084-4785-8c02-297057abe312
Req1AGG-ED-REQ-3Data source (e.g. meter data hub) ability to aggregate data76bc27ee-76af-4412-afe4-b61b8b4cd2d8
Req2AGG-ED-REQ-4DEP ability to forward aggregated data from a data source to a data user35134480-8d1f-47bf-a695-1413f1041c25
Req3AGG-ED-REQ-2Standard rules to aggregate data in order to ensure the comparability of aggregated data sets2840487e-69cd-468e-838c-d394afec358c
Req4AGG-ED-REQ-1Standard rules to aggregate data in order not to enable the identification of persons behind datab02dea59-d2a9-4284-873d-47efa9adf0e5

7. Common Terms and Definitions

8. Custom Information (optional)

KeyValueRefers to Section