elering-1
Aggregate energy data
1. Description of the Use Case
1.1. Name of the Use Case
| ID | Area /Domain(s)/Zone(s) | Name of the Use Case |
|---|
| 1 | Access to data, Balance management, Market for flexibilities, Operational planning and forecasting, Services related to end customers, | elering-1 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|
| 1 | 2018-04-12T00:00:00 | Kalle Kukk (Elering), | | |
| 2 | 2018-10-03T00:00:00 | Ricardo Jover (EDF), | UML model | |
| 3 | 2018-10-04T00:00:00 | Eric Suignard (EDF), | Version post WP5&9 physical meeting in Tallinn | |
| 4 | 2018-10-11T00:00:00 | Ricardo Jover (EDF), | Assumptions concerning users of the Application | |
| ²² | 2019-05-07T00:00:00 | Eric Suignard (EDF), | WP6-7-8 demos alignment and miscellaneous changes | |
| 6 | 2020-06-16T00:00:00 | Eric Suignard (EDF), | innogy’s and Elering’s review | |
1.3. Scope and Objectives of Use Case
| |
|---|
| Scope | Aggregation 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
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Assumptions |
|---|
| Same aggregation method could be applied for data sets in different countries to ensure the comparability in case requested by a party. |
| Prerequisites |
|---|
| Aggregation method used shall not enable the identification of the individual behind the personal data or organization behind the commercially sensitive data |
| Relation to other use cases |
|---|
|
| Level of depth |
| Prioritisation |
|
| Generic, regional or national relation |
|
| Nature of the use cases |
| SUC |
| Further keywords for classification |
|
2. Diagrams of Use Case
3. Technical Details
3.1. Actors
| Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
|---|
| Application | System | Any kind of system connected to a Data Exchange Platform and used by a market participant who wishes to receive data. | |
| Data Exchange Platform | System | Data 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 Hub | System | Data 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 Portal | System | Customer Portal for another country.
Can also mean a separate portal in the same country. | |
| Data Hub Operator | Business | Data 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 Operator | Business | Data exchange platform operator owns and operates a communication system which basic functionality is data transfer. | |
3.2. References
| No. | References Type | Reference | Status | Impact on Use Case | Organistaor / Organisation | Link |
|---|
4. Step by Step Analysis of Use Case
4.1. Overview of Scenarios
| No. | Scenario Name | Scenario Description | Primary Actor | Triggering Event | Pre-Condition | Post-Condition |
|---|
| 1 | Request aggregated data | | | | | |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Request aggregated data |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| 1.1 | | Aggregates data | | | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | | | 76bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5 |
| 1.2 | | Forwards aggregated data | | | 5351ac19-9ec2-47b9-9ead-4a28907df045 | | | 76bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5 |
| 1.3 | | Forwards aggregated data | | | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | | | 76bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5 |
| 1.4 | | Forwards aggregated data request |
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
| | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 76bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5 |
| 1.5 | | Forwards aggregated data request |
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
| | 5351ac19-9ec2-47b9-9ead-4a28907df045 | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 76bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5 |
| 1.6 | | Requests aggregated data |
Modsarus Use Case::InstanceName=Any Data
Modsarus Use Case::InstanceDescription=
| | 3b6d4cd1-7cd7-473e-af25-2cd3f990d415 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 5351ac19-9ec2-47b9-9ead-4a28907df045 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 76bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5 |
| 1.7 | | Sends aggregated data | | | 43ac67ff-35a0-48e4-8b2c-d1eaf7537292 | | | 76bc27ee-76af-4412-afe4-b61b8b4cd2d8 35134480-8d1f-47bf-a695-1413f1041c25 2840487e-69cd-468e-838c-d394afec358c b02dea59-d2a9-4284-873d-47efa9adf0e5 |
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|
| 97336539-bfa7-4501-b370-ff9d6d4bf681 | Any Data | | —- |
6. Requirements (optional)
| Category Identifier | Name | Description | mRID |
|---|
| Cat1 | Task 5.3 | Requirements integrated from Task 5.3. | 1880e39c-7084-4785-8c02-297057abe312 |
| Identifier | Name | Description | mRID |
|---|
| Req1 | AGG-ED-REQ-3 | Data source (e.g. meter data hub) ability to aggregate data | 76bc27ee-76af-4412-afe4-b61b8b4cd2d8 |
| Req2 | AGG-ED-REQ-4 | DEP ability to forward aggregated data from a data source to a data user | 35134480-8d1f-47bf-a695-1413f1041c25 |
| Req3 | AGG-ED-REQ-2 | Standard rules to aggregate data in order to ensure the comparability of aggregated data sets | 2840487e-69cd-468e-838c-d394afec358c |
| Req4 | AGG-ED-REQ-1 | Standard rules to aggregate data in order not to enable the identification of persons behind data | b02dea59-d2a9-4284-873d-47efa9adf0e5 |
7. Common Terms and Definitions
| Key | Value | Refers to Section |
|---|