elering-17
Transfer 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-17 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|---|---|---|---|
| 1 | 2018-04-12T00:00:00 | Richárd Balog (Mavir), Kalle Kukk (Elering), | ||
| 2 | 2018-07-13T00:00:00 | Ricardo Jover (EDF), Eric Suignard (EDF), | ||
| 3 | 2018-07-19T00:00:00 | Ricardo Jover (EDF), Eric Suignard (EDF), | ||
| 4 | 2018-08-02T00:00:00 | Eric Suignard (EDF), | Scenario names changed. First scenario restructured. | |
| 5 | 2018-09-21T00:00:00 | Eric Suignard (EDF), Ricardo Jover (EDF), | Remarks from Innogy and EirGrid. | |
| 6 | 2018-10-04T00:00:00 | Eric Suignard (EDF), | Version post WP5&9 physical meeting in Tallinn | |
| 7 | 2018-10-17T00:00:00 | Eric Suignard (EDF), | Version reviewed by WP5&9 partners | |
| 8 | 2019-05-07T00:00:00 | Eric Suignard (EDF), | WP6-7-8 demos alignment and miscellaneous changes | |
| 9 | 2020-06-16T00:00:00 | Eric Suignard (EDF), | innogy’s and Elering’s review |
1.3. Scope and Objectives of Use Case
| Scope | Transfer of different types of energy related data. The system use case describes the data flow through data exchange platform from the data provider (data hub or any other data source) to data user (data owner) or to a third party application (supplier, aggregator, ESCO), who has consent or legal mandate to use the data. Data transfer does not necessarily need a central storage. |
| Objective(s) | To support business use cases and to ensure access to needed data for the relevant processes. |
| Related business case(s) |
1.4. Narrative of Use Case
Short description
The granularity of data and frequency of data transfer could be different depending on the business use case, but the purpose is the same: ensuring the needed data in order to support business processes. Some other system use cases (data collection, authentication of data users, authorization, anonymization of data, aggregation of data) are strongly connected to this use case, which are considered as preconditions.
Complete description
1.5. Key Performance Indicatiors (KPI)
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Assumptions |
|---|
| Some sort of data validation is applied |
| Prerequisites |
|---|
| The user has the proper authentication to download data |
1.7. Further information to the use case for classification/mapping
| Relation to other use cases |
|---|
| Level of depth |
| Prioritisation |
| Generic, regional or national relation |
| Nature of the use cases |
| SUC |
| Further keywords for classification |
1.8. General remarks
| General remarks |
|---|
2. Diagrams of Use Case
3. Technical Details
3.1. Actors
| Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
|---|---|---|---|
| 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 Source | System | Any kind of system used to store data (including Data Hub and Flexibility Platform). | |
| Application | System | Any kind of system connected to a Data Exchange Platform and used by a market participant who wishes to receive data. | |
| Data User | Business | Any person who uses data. Can be a Data Owner or a Data Delegated Third party. | |
| Foreign Customer Portal | System | Customer Portal for another country. Can also mean a separate portal in the same country. | |
| Customer Portal | System | Customer Portal manages data users' authentication, access permissions and data logs. Customer Portals store data related to its services (e.g. authentication information, representation rights, access permissions, data logs). | |
| 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 data through DEP API and publish data to subscribed applications | Data can be sent to an application if the application has requested for the data through DEP API or if it has subscribed to publications of this data. | ||||
| 2 | Download data through DEP customer portal | An authenticated user can check and download the data through DEP from any Data Hub, depending on the type of data (to be defined). |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Request data through DEP API and publish data to subscribed applications |
| 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 | Request data | An application requests for data from a Data Source. | 3b6d4cd1-7cd7-473e-af25-2cd3f990d415 | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||||
| 1.2 | Check authorization from data owner to request specific data | According to "Manage access permissions" SUC, an application can receive authorization from a Data Owner to request data from a Data Source. Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | 3b6d4cd1-7cd7-473e-af25-2cd3f990d415 | baa61f8b-bde4-4008-820b-bfad5a7150f6 5351ac19-9ec2-47b9-9ead-4a28907df045 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 1.3 | Authorization check | Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | baa61f8b-bde4-4008-820b-bfad5a7150f6 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 1.4 | Authorization check | Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | 5351ac19-9ec2-47b9-9ead-4a28907df045 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 1.5 | Forward request for data | The Data Exchange Platform forwards to the Data Source the request for data. Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 0dd151df-ddcc-48b7-9236-208eb2f4a16c | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 1.6 | Check the request for data | The Data Source checks whether there is valid authorization for the requesting application. | 0dd151df-ddcc-48b7-9236-208eb2f4a16c | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||||
| 1.7 | Process the request for data | The Data Source makes data available to the requesting application, in a "publish-stream" mode. | 0dd151df-ddcc-48b7-9236-208eb2f4a16c | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||||
| 1.8 | Publish data to authorized applications | The Data Source publishes data to all applications with valid authorization. Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | 0dd151df-ddcc-48b7-9236-208eb2f4a16c | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 1.9 | Forward data | The Data Exchange Platform forwards the published data to authorized applications. Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 3b6d4cd1-7cd7-473e-af25-2cd3f990d415 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 21ea2803-acf7-41f1-84c8-c72d43aeda29 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 |
| Scenario Name: |
|---|
| Download data through DEP customer portal |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|---|---|---|---|---|---|---|---|
| 2.1 | Process the request for data | Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | 5351ac19-9ec2-47b9-9ead-4a28907df045 | 0dd151df-ddcc-48b7-9236-208eb2f4a16c | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 21ea2803-acf7-41f1-84c8-c72d43aeda29 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 2.2 | Authenticate to DEP | Data users authenticates to Data Exchange Platform via a web-based customer portal or through 3rd party application. Modsarus Use Case::InstanceName=Authenticate Information Modsarus Use Case::InstanceDescription= | f3850003-cd20-463b-891f-a2ab28c75bb1 | baa61f8b-bde4-4008-820b-bfad5a7150f6 | 79077332-56bd-437e-8295-63b9a9dab5bd | 21ea2803-acf7-41f1-84c8-c72d43aeda29 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 2.3 | Verify authentication information | The Data Exchange Platform verifies the authentication information and the representation rights. Modsarus Use Case::InstanceName=Authenticate Information Modsarus Use Case::InstanceDescription= | baa61f8b-bde4-4008-820b-bfad5a7150f6 | f3850003-cd20-463b-891f-a2ab28c75bb1 | 79077332-56bd-437e-8295-63b9a9dab5bd | 21ea2803-acf7-41f1-84c8-c72d43aeda29 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 2.4 | Request data | Data users request for data via a DEP web-based portal or through 3rd party applications. Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | f3850003-cd20-463b-891f-a2ab28c75bb1 | baa61f8b-bde4-4008-820b-bfad5a7150f6 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 21ea2803-acf7-41f1-84c8-c72d43aeda29 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 2.5 | Process request | If the Data User and the Data Source are not in the same country, the Data Exchange Platform forwards the request to the Foreign Data Exchange Platform. Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | baa61f8b-bde4-4008-820b-bfad5a7150f6 | 0dd151df-ddcc-48b7-9236-208eb2f4a16c 5351ac19-9ec2-47b9-9ead-4a28907df045 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 21ea2803-acf7-41f1-84c8-c72d43aeda29 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 | ||
| 2.6 | Process the request for data | The Data Source can create different kinds of file (e.g. Excel, PDF, XML). Modsarus Use Case::InstanceName=Any Data Modsarus Use Case::InstanceDescription= | 0dd151df-ddcc-48b7-9236-208eb2f4a16c | f3850003-cd20-463b-891f-a2ab28c75bb1 | 97336539-bfa7-4501-b370-ff9d6d4bf681 | 21ea2803-acf7-41f1-84c8-c72d43aeda29 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 f2decf5c-0584-4b7f-b3cd-3f965c05eaac 3c2a1a64-8572-4c9e-a14f-fd230623d471 96f13794-5aad-4213-a61a-8a20c2f5089e ccb8fafe-70eb-44eb-aba5-b221fe6704e8 |
5. Information Exchanged
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|---|---|---|
| 97336539-bfa7-4501-b370-ff9d6d4bf681 | Any Data | —- | |
| 79077332-56bd-437e-8295-63b9a9dab5bd | Authenticate Information | —- |
6. Requirements (optional)
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat1 | Personal data | bd1580a2-20b8-41fa-a8df-2ae6041bf604 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req1 | Access Citizen Right | Right to secure direct access of own personal data and to any processing, storage or sharing details | 2af6ad64-c90f-4bc9-aebd-7c01060f85c4 |
| Req2 | Portable Citizen Right | A copy of the data held may be requested by the individual in a portable format | 21ea2803-acf7-41f1-84c8-c72d43aeda29 |
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat2 | Task 5.3 | Requirements integrated from Task 5.3. | 1880e39c-7084-4785-8c02-297057abe312 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req3 | DT-REQ1 | Transfer of data must be secured, by means of encryption or communication protocol | f2decf5c-0584-4b7f-b3cd-3f965c05eaac |
| Req4 | DT-REQ3 | Data owner’s access to data through DEP (and foreign DEP) | 3c2a1a64-8572-4c9e-a14f-fd230623d471 |
| Req5 | DT-REQ4 | Application’s access to data through DEP (and foreign DEP) | 96f13794-5aad-4213-a61a-8a20c2f5089e |
| Req6 | DT-REQ2 | Data portability (applies to personal data - Article 20 of the GDPR) | ccb8fafe-70eb-44eb-aba5-b221fe6704e8 |
7. Common Terms and Definitions
8. Custom Information (optional)
| Key | Value | Refers to Section |
|---|