elering-7
Exchange data between DERs and System Operators
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 | Market for flexibilities, Operational planning and forecasting, | elering-7 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|---|---|---|---|
| 1 | 2018-04-05T00:00:00 | Wojciech Lubczynski (PSE), | ||
| 2 | 2018-07-19T00:00:00 | Ricardo Jover (EDF), Eric Suignard (EDF), | ||
| 3 | 2018-08-02T00:00:00 | Eric Suignard (EDF), | ||
| 4 | 2018-09-21T00:00:00 | Ricardo Jover (EDF), | Remarks from Elering (Narrative) and EirGrid. | |
| 5 | 2018-10-04T00:00:00 | Eric Suignard (EDF), | Version post WP5&9 physical meeting in Tallinn | |
| 6 | 2018-10-17T00:00:00 | Eric Suignard (EDF), | Version reviewed by WP5&9 partners | |
| 7 | 2019-05-07T00:00:00 | Eric Suignard (EDF), | WP6-7-8 demos alignment and miscellaneous changes | |
| 8 | 2020-06-16T00:00:00 | Eric Suignard (EDF), | innogy’s and Elering’s review |
1.3. Scope and Objectives of Use Case
| Scope | Data exchange between DER (Distributed Energy Resources) and SCADA systems of TSO and DSOs, using the Data Exchange Platform as an intermediary. |
| Objective(s) | Ensuring the observability and controllability of DER units providing electrical energy and flexibility services to the power system. |
| Related business case(s) |
1.4. Narrative of Use Case
Short description
The use case includes data exchange between distributed generators, demand response (DR) resources and energy storage devices, and a Data Exchange Platform (DEP) that communicates with TSO and DSO SCADA systems. DEP is not appropriate for time-critical data exchange (like activation of very fast products) thus being out of scope of this use case. It is assumed that the SCADA systems may require both schedule data for planning purpose and structural data (including connection diagrams) each time they are changed.
Complete description
1.5. Key Performance Indicatiors (KPI)
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Assumptions |
|---|
| It is assumed that systems of authentication and access permission are implemented that allow data exchange with all individual DER units, even those that are part of the aggregator pool. |
| Prerequisites |
|---|
| Communication standards must be established |
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 |
|---|---|---|---|
| DER Operator | Business | Operates a single DER unit. Distributed Energy Resources can consist of generation sources, energy storage facilities and facilities participating in Demand Response. Are mainly connected to distribution power grids but can also be connected to transmission power grids (e.g. Portugal). Can be an Asset Operator, a Generator or a Generation Asset Operator (cf. definitions in T3.3 deliverable). | |
| System Operator SCADA | System | SCADA operated by a System Operator. | |
| 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. | |
| Aggregator SCADA | System | SCADA operated by an Aggregator. | |
| Flexibility Platform | System | Flexibility Platform (FP) for System Operators and Flexibility Service Providers that enables the trading of different flexibility products and services. A FP is operated by a Market Operator. Available to System Operators and Flexibility Services Providers. It is used to support the prequalification, the bidding, the activation and the verification processes, ensuring coordination between activities undertaken by several operators using the same flexible resources. Several national and regional FPs may exist. | |
| 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 | Exchange data from DERs to System Operators | |||||
| 2 | Exchange data from System Operators to DERs | Cf. "Manage flexibility activations" data exchange System Use Case. |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Exchange data from DERs to System Operators |
| 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 | Provide DER changes in schedule data and DER structural data | Occasional provision of non-real-time data. Modsarus Use Case::InstanceName=DER Structural Data Modsarus Use Case::InstanceDescription=In case of changes in portfolio or changes in topology. | 9d306918-8a80-41e1-9545-c4173c3976b8 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | d233fbe2-d6f8-4623-89c0-c50eea811e98 | 2b41cee9-30ef-41dc-93e2-291685c63dec 63b15f5e-3edf-46e1-b142-af2d67d1a436 5ef4999a-2781-4010-8e80-749933b35149 5e73c5d8-1027-40b6-8ced-7640662d12d2 b5656698-619e-4c9e-9a4b-699003b8c341 f7ecbcd4-cbd7-420d-8c1f-b66ad79e0305 dd1ce7c9-4f60-4b53-9271-27638175f59f 99bbfdb2-f7ee-4289-953e-338013a1e262 3c811d2b-1a8d-4b89-8cef-e92165421fbd f774b2e9-dbb0-49dd-a04c-ff6b47e24fa9 | ||
| 1.2 | Provide changes in aggregated DER schedule data and aggregated DER structural data | Occasional provision of non-real-time data. Modsarus Use Case::InstanceName=DER Structural Data Modsarus Use Case::InstanceDescription=In case of changes in portfolio or changes in topology. | c307526e-765c-4f70-83b7-6893c5118e3e | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | d233fbe2-d6f8-4623-89c0-c50eea811e98 | 2b41cee9-30ef-41dc-93e2-291685c63dec 63b15f5e-3edf-46e1-b142-af2d67d1a436 5ef4999a-2781-4010-8e80-749933b35149 5e73c5d8-1027-40b6-8ced-7640662d12d2 b5656698-619e-4c9e-9a4b-699003b8c341 f7ecbcd4-cbd7-420d-8c1f-b66ad79e0305 dd1ce7c9-4f60-4b53-9271-27638175f59f 99bbfdb2-f7ee-4289-953e-338013a1e262 3c811d2b-1a8d-4b89-8cef-e92165421fbd f774b2e9-dbb0-49dd-a04c-ff6b47e24fa9 | ||
| 1.3 | Forward DER schedule and structural data | Transmission of schedule and structural data when they are changed (push method). Data are sent to the SCADA systems of the TSOs and the DSOs which need such data. Modsarus Use Case::InstanceName=DER Structural Data Modsarus Use Case::InstanceDescription=In case of changes in portfolio or changes in topology. | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 328ba15c-42bf-42b1-945d-127aab24c7bd | d233fbe2-d6f8-4623-89c0-c50eea811e98 | 2b41cee9-30ef-41dc-93e2-291685c63dec 63b15f5e-3edf-46e1-b142-af2d67d1a436 5ef4999a-2781-4010-8e80-749933b35149 5e73c5d8-1027-40b6-8ced-7640662d12d2 b5656698-619e-4c9e-9a4b-699003b8c341 f7ecbcd4-cbd7-420d-8c1f-b66ad79e0305 dd1ce7c9-4f60-4b53-9271-27638175f59f 99bbfdb2-f7ee-4289-953e-338013a1e262 3c811d2b-1a8d-4b89-8cef-e92165421fbd f774b2e9-dbb0-49dd-a04c-ff6b47e24fa9 | ||
| 1.4 | Forward DER real-time setpoint data | Real-time data transfer for all DERs to SCADA systems (push method). Data are sent to the SCADA systems of the TSOs and the DSOs which need such data. Modsarus Use Case::InstanceName=DER Real Time Data Modsarus Use Case::InstanceDescription=At least P,Q,V. | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 328ba15c-42bf-42b1-945d-127aab24c7bd | 8fd4a450-4a75-4d4f-ad42-9f5661d35651 | 2b41cee9-30ef-41dc-93e2-291685c63dec 63b15f5e-3edf-46e1-b142-af2d67d1a436 5ef4999a-2781-4010-8e80-749933b35149 5e73c5d8-1027-40b6-8ced-7640662d12d2 b5656698-619e-4c9e-9a4b-699003b8c341 f7ecbcd4-cbd7-420d-8c1f-b66ad79e0305 dd1ce7c9-4f60-4b53-9271-27638175f59f 99bbfdb2-f7ee-4289-953e-338013a1e262 3c811d2b-1a8d-4b89-8cef-e92165421fbd f774b2e9-dbb0-49dd-a04c-ff6b47e24fa9 | ||
| 1.5 | Provide aggregated DER real-time setpoint data | In the case of an aggregator that manages multiple DERs. Modsarus Use Case::InstanceName=DER Real Time Data Modsarus Use Case::InstanceDescription=At least P,Q,V. | c307526e-765c-4f70-83b7-6893c5118e3e | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 8fd4a450-4a75-4d4f-ad42-9f5661d35651 | 2b41cee9-30ef-41dc-93e2-291685c63dec 63b15f5e-3edf-46e1-b142-af2d67d1a436 5ef4999a-2781-4010-8e80-749933b35149 5e73c5d8-1027-40b6-8ced-7640662d12d2 b5656698-619e-4c9e-9a4b-699003b8c341 f7ecbcd4-cbd7-420d-8c1f-b66ad79e0305 dd1ce7c9-4f60-4b53-9271-27638175f59f 99bbfdb2-f7ee-4289-953e-338013a1e262 3c811d2b-1a8d-4b89-8cef-e92165421fbd f774b2e9-dbb0-49dd-a04c-ff6b47e24fa9 | ||
| 1.6 | Provide DER real-time setpoint data | In case of the single DER unit. Modsarus Use Case::InstanceName=DER Real Time Data Modsarus Use Case::InstanceDescription=At least P,Q,V. | 9d306918-8a80-41e1-9545-c4173c3976b8 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 8fd4a450-4a75-4d4f-ad42-9f5661d35651 | 2b41cee9-30ef-41dc-93e2-291685c63dec 63b15f5e-3edf-46e1-b142-af2d67d1a436 5ef4999a-2781-4010-8e80-749933b35149 5e73c5d8-1027-40b6-8ced-7640662d12d2 b5656698-619e-4c9e-9a4b-699003b8c341 f7ecbcd4-cbd7-420d-8c1f-b66ad79e0305 dd1ce7c9-4f60-4b53-9271-27638175f59f 99bbfdb2-f7ee-4289-953e-338013a1e262 3c811d2b-1a8d-4b89-8cef-e92165421fbd f774b2e9-dbb0-49dd-a04c-ff6b47e24fa9 | ||
| 1.7 | Take into account DER data | 328ba15c-42bf-42b1-945d-127aab24c7bd | 2b41cee9-30ef-41dc-93e2-291685c63dec 63b15f5e-3edf-46e1-b142-af2d67d1a436 5ef4999a-2781-4010-8e80-749933b35149 5e73c5d8-1027-40b6-8ced-7640662d12d2 b5656698-619e-4c9e-9a4b-699003b8c341 f7ecbcd4-cbd7-420d-8c1f-b66ad79e0305 dd1ce7c9-4f60-4b53-9271-27638175f59f 99bbfdb2-f7ee-4289-953e-338013a1e262 3c811d2b-1a8d-4b89-8cef-e92165421fbd f774b2e9-dbb0-49dd-a04c-ff6b47e24fa9 |
| Scenario Name: |
|---|
| Exchange data from System Operators to DERs |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
5. Information Exchanged
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|---|---|---|
| d233fbe2-d6f8-4623-89c0-c50eea811e98 | DER Structural Data | —- | |
| 8fd4a450-4a75-4d4f-ad42-9f5661d35651 | DER Real Time Data | —- |
6. Requirements (optional)
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat1 | Functional | Functional requirements | 59e7899c-d9ee-4534-81a6-81b37dce5e81 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req1 | Transmissions between DEP and SCADA should be based on standards | Applicable standards, in particular:<br/><ul><li>ICCP: Inter-Control Center Communications Protocol (IEC 60870-6/TASE.2),</li><li>Communication networks and systems for power utility automation (IEC 61850-8-2),</li><li>RESTful services.</li></ul> | 2b41cee9-30ef-41dc-93e2-291685c63dec |
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat2 | Security | Security requirements | c44d91be-533b-4762-9b73-aca8371243d3 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req2 | IT infrastructure of DER and/or aggregator meets safety standards | Applicable standards, in particular IEC 62351. | 63b15f5e-3edf-46e1-b142-af2d67d1a436 |
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat3 | Performance | b50a27e2-b8b9-4aaa-947a-a459914dbda5 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req3 | Real-time data sent from the DER unit reach SCADA systems in no more than 1 minute | According to KORRR art. 10, the refresh rate for the real-time data exchanges shall not be longer than 1 minute. It should be defined by each TSO in its control area. | 5ef4999a-2781-4010-8e80-749933b35149 |
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat4 | Task 5.3 | Requirements integrated from Task 5.3. | 1880e39c-7084-4785-8c02-297057abe312 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req4 | DER-SCADA-REQ1 | Encrypted data exchange | 5e73c5d8-1027-40b6-8ced-7640662d12d2 |
| Req5 | DER-SCADA-REQ7 | Ability of DEP to forward activation requests from System Operators to DER | b5656698-619e-4c9e-9a4b-699003b8c341 |
| Req6 | DER-SCADA-REQ6 | Ability of DEP to forward near-real-time (up to 1 hour) data from DER’s to System Operators | f7ecbcd4-cbd7-420d-8c1f-b66ad79e0305 |
| Req7 | DER-SCADA-REQ4 | Ability of DEP to forward real-time data from DER’s to System Operators | dd1ce7c9-4f60-4b53-9271-27638175f59f |
| Req8 | DER-SCADA-REQ5 | Ability of DEP to forward very-near-real-time (up to 1 minute) data from DER’s to System Operators | 99bbfdb2-f7ee-4289-953e-338013a1e262 |
| Req9 | DER-SCADA-REQ2 | Communication link between DEP and SO’s SCADA | 3c811d2b-1a8d-4b89-8cef-e92165421fbd |
| Req10 | DER-SCADA-REQ3 | Safety of DER’s IT infrastructure | f774b2e9-dbb0-49dd-a04c-ff6b47e24fa9 |
7. Common Terms and Definitions
8. Custom Information (optional)
| Key | Value | Refers to Section |
|---|