elering-10
Manage flexibility activations
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, Services related to end customers, | elering-10 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|---|---|---|---|
| 1 | 2018-04-17T00:00:00 | Olivia Alonso Garcia (REE), | ||
| 2 | 2018-06-22T00:00:00 | Ricardo Jover (EDF), Eric Suignard (EDF), | ||
| 3 | 2018-07-30T00:00:00 | Eric Suignard (EDF), | ||
| 4 | 2018-08-02T00:00:00 | Eric Suignard (EDF), | ||
| 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 | 2018-10-30T00:00:00 | Eric Suignard (EDF), | Description of Grid data | |
| 9 | 2019-05-07T00:00:00 | Eric Suignard (EDF), | WP6-7-8 demos alignment and miscellaneous changes | |
| 10 | 2019-06-05T00:00:00 | Ricardo Jover (EDF), Eric Suignard (EDF), | Changes following WP5&9 workshop in Chatou | |
| 11 | 2019-06-13T00:00:00 | Eric Suignard (EDF), | Elering review | |
| 12 | 2019-08-22T00:00:00 | Eric Suignard (EDF), Wiebke Albers (innogy), | Partial convergence on Grid Validation System usage | |
| 13 | 2020-06-16T00:00:00 | Eric Suignard (EDF), | innogy’s and Elering’s review |
1.3. Scope and Objectives of Use Case
| Scope | Developing generic case describing the data exchange for the process of flexibility activation. |
| Objective(s) | Make data exchange for activation of flexibilities effective and reliable. |
| Related business case(s) |
1.4. Narrative of Use Case
Short description
Description of the needed data exchange for the selection (taking into account any grid limitations) and initiation of activation of flexibilities bids that previously have been sent to the Flexibility Platform. Delivery of notification of activation requests to the Flexibility Service Providers (FSPs), in a reliable and timely manner according to the relevant terms and conditions applicable to FSPs.
According to EU-SysFlex WP3 suggestion, the function of grid impact assessment and hosting of Grid Validation System could be taken over by Optimisation Operator role from the Primary and Secondary System Operator roles.
Complete description
1.5. Key Performance Indicatiors (KPI)
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Assumptions |
|---|
| Data exchange occurs as a result of business processes. The method of implementing business processes depends on the architecture of the flexibility services markets |
| Prerequisites |
|---|
| FSPs have been prequalified and have submitted bids. |
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 |
|---|---|---|---|
| Secondary System Operator | Business | Operates the power grid on which a flexibility service unit is connected or this unit may otherwise impact its grid. Assesses the impact on its network of the flexibility to be procured because the activation of such flexibility may potentially cause congestion in its grid. | |
| Flexibility Service Provider | Business | Can be a Distribution Network Flexibility Provider or a Transmission Network Flexibility Provider (cf. definitions in T3.3 deliverable). Similar to Flexibility Aggregator. Can be both aggregator and individual consumer/generator. Type of Energy Service Provider. | |
| Primary System Operator | Business | Initiates the call for tenders and initiates the activation of a flexibility. It also can operate the power grid on which a flexibility service unit is connected or this unit may otherwise impact its grid. In this case, it assesses the impact on its network of the flexibility to be procured because the activation of such flexibility may potentially cause congestion in its grid. | |
| 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. | |
| 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. | |
| Grid Validation System | System | System hosted by Optimisation Operators and used for the power grid congestion assessment, including grid validation if activation will cause congestion. | |
| Optimisation Operator | Business | Optimise and select the bids, where relevant in combination with switching measures; clear the market for auctions or select individual bids in the order book organised by the MO taking into account the grid data (constraints and sensitivities/topology if needed) provided by DS_O and TS_O ; communicate results (rewarded offers and prices) to the MO. The OO role can be carried out by a system operator, market operator or a third party. (cf. definition in T3.2 deliverable) | |
| 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 | Manage flexibility activation |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Manage flexibility activation |
| 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 flexibility activation | Primary System Operator initiates flexibility activation on Flexibility Platform which selects bids considering the amounts of energy/capacity needed, maximum price and grid impact analysis results from SO - limitation and sensitivities where applicable (e.g. congestion management call for tender) Modsarus Use Case::InstanceName=Flexibility Activation Request Modsarus Use Case::InstanceDescription= | eb116f35-39eb-4ce4-8136-5fa3c744b655 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 2e7a4bcd-e349-48b9-9cb0-c0e68567a37f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.2 | Request flexibility activation | Primary System Operator initiates flexibility activation on Flexibility Platform which selects bids considering the amounts of energy/capacity needed, maximum price and grid impact analysis results from SO - limitation and sensitivities where applicable (e.g. congestion management call for tender) Modsarus Use Case::InstanceName=Flexibility potential Modsarus Use Case::InstanceDescription= | eb116f35-39eb-4ce4-8136-5fa3c744b655 | ec556f1b-8608-4de1-ab7c-a7e614f2bc37 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | |||
| 1.3 | Forward request for flexibility activation | DEP forwards request to FP. Modsarus Use Case::InstanceName=Flexibility Activation Request Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 908bfa7a-c616-4b2b-a712-04aac115429b | 2e7a4bcd-e349-48b9-9cb0-c0e68567a37f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.4 | Register request for flexibility activation | FP registers the request. Modsarus Use Case::InstanceName=Flexibility Activation Request Modsarus Use Case::InstanceDescription= | 908bfa7a-c616-4b2b-a712-04aac115429b | 908bfa7a-c616-4b2b-a712-04aac115429b | 2e7a4bcd-e349-48b9-9cb0-c0e68567a37f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.5 | Send necessary information for grid impact assessment | Flexibility Platform sends required level of information necessary for grid impact assessment to Secondary System Operators concerned via DEP. This concerns bids to be activated. Modsarus Use Case::InstanceName=Flexibility Activation Request Modsarus Use Case::InstanceDescription= | 908bfa7a-c616-4b2b-a712-04aac115429b | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 2e7a4bcd-e349-48b9-9cb0-c0e68567a37f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.6 | Forward necessary information for grid impact assessment | DEP forwards information to Secondary System Operator Modsarus Use Case::InstanceName=Flexibility Activation Request Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 6a6d00e5-7ffc-4832-9b93-a346392c62cb | 2e7a4bcd-e349-48b9-9cb0-c0e68567a37f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.7 | Assess secondary grid impact | Secondary System Operator assesses the impact of flexibility activations in its grid in order to avoid congestions due to these activations. Secondary System Operator provides the results of grid impact assessment to the Flexibility Platform setting restrictions – if necessary - on the activation of flexibilities which would cause congestion in other grids. Modsarus Use Case::InstanceName=Results of grid validation Modsarus Use Case::InstanceDescription= | 6a6d00e5-7ffc-4832-9b93-a346392c62cb | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 1d84924c-81aa-4e8a-b1b4-0a5be6a8b488 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.8 | Forward results of secondary grid impact assessment | DEP forwards results to Flexibility Platform Modsarus Use Case::InstanceName=Results of grid validation Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 908bfa7a-c616-4b2b-a712-04aac115429b | 1d84924c-81aa-4e8a-b1b4-0a5be6a8b488 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.9 | Collect the result of the grid impact assessment of SSO | Flexibility Platform collects the results of grid impact assessment to see if activations would cause further imbalance or congestions and therefore counter actions would be needed. Counter actions are an inherent part of this step (frequency products do not need counteractions, redispatch is per definition an energy balance neutral measure - the increased and decreased energy of a measure is always equal). | 908bfa7a-c616-4b2b-a712-04aac115429b | c834d26a-4514-4c9b-86f6-b12cd9ec9e7c | ||||
| 1.10 | Select next set of bids based on the merit order principle | Modsarus Use Case::InstanceName=Flexibility Bid Modsarus Use Case::InstanceDescription= | 908bfa7a-c616-4b2b-a712-04aac115429b | 908bfa7a-c616-4b2b-a712-04aac115429b | bb2896bc-89a8-400e-99c4-c560a72ebe7f | c834d26a-4514-4c9b-86f6-b12cd9ec9e7c ce682e61-249f-4c7b-bd9b-d14efdbb7bd0 | ||
| 1.11 | Forward request for counter action | Modsarus Use Case::InstanceName=Counter Action Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | eb116f35-39eb-4ce4-8136-5fa3c744b655 | aa909516-40bc-4852-94aa-753657714401 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.12 | Take a counter action | The flexibility service in the opposite direction should be activated to balance the system. As TSO is responsible for balancing, we can assume it is TSO’s responsibility to initiate the counteraction (it is assumed that TSO is the Primary System Operator in this use case). In case a counter action is not possible (e.g. due to lack of time if it is happening close to real-time), emergency plan (not defined yet) is activated. Alternatively, this activity could be automatic action in the Flexibility Platform without direct involvement of System Operator, but only after the check of the technical limits of the network involved. Modsarus Use Case::InstanceName=Counter Action Modsarus Use Case::InstanceDescription= | eb116f35-39eb-4ce4-8136-5fa3c744b655 | eb116f35-39eb-4ce4-8136-5fa3c744b655 | aa909516-40bc-4852-94aa-753657714401 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.13 | Forward request for activation | Modsarus Use Case::InstanceName=Flexibility Activation Request Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 908bfa7a-c616-4b2b-a712-04aac115429b 2b8f28a5-4b5a-49fb-92fa-1728b089ce00 | 2e7a4bcd-e349-48b9-9cb0-c0e68567a37f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.14 | Register request for activation | 908bfa7a-c616-4b2b-a712-04aac115429b | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | |||||
| 1.15 | Activate bids (Operational) | Modsarus Use Case::InstanceName=Activated Flexibility Modsarus Use Case::InstanceDescription= | 2b8f28a5-4b5a-49fb-92fa-1728b089ce00 | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 6bc23364-c3c2-4760-8065-7fba38f1d821 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.16 | Activate bids (Operational) | Modsarus Use Case::InstanceName=Flexibility Bid Modsarus Use Case::InstanceDescription= | 2b8f28a5-4b5a-49fb-92fa-1728b089ce00 | 908bfa7a-c616-4b2b-a712-04aac115429b | bb2896bc-89a8-400e-99c4-c560a72ebe7f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.17 | Forward activation confirmation | Modsarus Use Case::InstanceName=Activated Flexibility Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 908bfa7a-c616-4b2b-a712-04aac115429b | 6bc23364-c3c2-4760-8065-7fba38f1d821 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.18 | Register activation confirmation | Flexibility Platform receives and registers confirmations from Flexibility Service Providers in order to make sure that they actually received the requests for activation. This step does not include the verifications aspects of activations (see "Verify and settle activated flexibilities" SUC for activation verification). Modsarus Use Case::InstanceName=Activated Flexibility Modsarus Use Case::InstanceDescription= | 908bfa7a-c616-4b2b-a712-04aac115429b | 908bfa7a-c616-4b2b-a712-04aac115429b | 6bc23364-c3c2-4760-8065-7fba38f1d821 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b |
5. Information Exchanged
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|---|---|---|
| 2e7a4bcd-e349-48b9-9cb0-c0e68567a37f | Flexibility Activation Request | —- | |
| ec556f1b-8608-4de1-ab7c-a7e614f2bc37 | Flexibility Potential | —- | |
| 1d84924c-81aa-4e8a-b1b4-0a5be6a8b488 | Congestion Matrix | Congestion matrices are provided by System Operators and stored in Flexibility Platforms. It consists in a matrix based on grid models. Flexibility bids are inserted into the matrix, in order to check whether congestions would occur. | —- |
| bb2896bc-89a8-400e-99c4-c560a72ebe7f | Flexibility Bid | —- | |
| aa909516-40bc-4852-94aa-753657714401 | Counter Action | —- | |
| 6bc23364-c3c2-4760-8065-7fba38f1d821 | Activated Flexibility | —- |
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 | FA-REQ2 | Exchange of activation requests through DEP and flexibility platform | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 |
| Req2 | FA-REQ1 | Automated activation of devices is possible | d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b |
| Category Identifier | Name | Description | mRID |
|---|---|---|---|
| Cat2 | Functional | Functional requirements | 59e7899c-d9ee-4534-81a6-81b37dce5e81 |
| Identifier | Name | Description | mRID |
|---|---|---|---|
| Req3 | PSOs can take over the selection of bids and select the bids themselves in emergency situations | Flexibility bids are selected by Flexibility Platforms on a merit order basis and with several criteria. Different criteria should be considered (e.g. price, social economic value, location).<br/>However, in some cases, this may not be feasible. This situation can occur for congestion management or frequency control, when flexibility needs are too close to real time (emergency situations). | c834d26a-4514-4c9b-86f6-b12cd9ec9e7c |
| Req4 | TSO-DSO coordination in flexibility optimisation | Flexibilities must be studied and validated by TSOs and DSOs in a coordinated manner before activation requests can be submitted to Flexibility Service Providers. | ce682e61-249f-4c7b-bd9b-d14efdbb7bd0 |
7. Common Terms and Definitions
8. Custom Information (optional)
| Key | Value | Refers to Section |
|---|