elering-11
Manage flexibility activations - Alternative 2
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 | Services related to end customers, Operational planning and forecasting, Market for flexibilities, | elering-11 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|---|---|---|---|
| 2 | 2020-06-16T00:00:00 | Eric Suignard (EDF), | innogy’s and Elering’s review | |
| 1 | 2019-08-30T00:00:00 | Wiebke Albers (innogy SE), | alternative SUC for "Manage Flexibility Activation" |
1.3. Scope and Objectives of Use Case
| Scope | Developing generic case describing the data exchange for the process of flexibility activation where the capacity has already been reserved during earlier time frames and a new grid assessment is necessary to select the best flexibility. |
| 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 and where previously the bids were not activated but their capacity was reserved in the bidding process. 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 |
|---|
| 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 |
|---|---|---|---|
| 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. | |
| 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 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. | |
| 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. | |
| 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. | |
| 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. | |
| 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 by selecting bids on the Flexibility Platform considering the amounts of energy/capacity needed as well as the maximum price based on the grid impact analysis results from SO - limitation and sensitivities where applicable (e.g. congestion management call for tender) | eb116f35-39eb-4ce4-8136-5fa3c744b655 | 6a6d00e5-7ffc-4832-9b93-a346392c62cb | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | |||
| 1.2 | Request flexibility activation | Primary System Operator initiates flexibility activation on Flexibility Platform by selecting bids on the Flexibility Platform considering the amounts of energy/capacity needed as well as the maximum price based on the grid impact analysis results from SO - limitation and sensitivities where applicable (e.g. congestion management call for tender) Modsarus Use Case::InstanceName=Flexibility Bid Modsarus Use Case::InstanceDescription= Modsarus Use Case::InstanceName=Flexibility potential Modsarus Use Case::InstanceDescription= | eb116f35-39eb-4ce4-8136-5fa3c744b655 | bb2896bc-89a8-400e-99c4-c560a72ebe7f ec556f1b-8608-4de1-ab7c-a7e614f2bc37 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | |||
| 1.3 | 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 PSO setting restrictions – if necessary - on the activation of flexibilities which would cause congestion in its grids and provide sensitivities in case of a congestion management tender. | 6a6d00e5-7ffc-4832-9b93-a346392c62cb | 6a6d00e5-7ffc-4832-9b93-a346392c62cb eb116f35-39eb-4ce4-8136-5fa3c744b655 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | |||
| 1.4 | Decluster flexibility bids | Secondary System Operator declusters flexibility bid cluster and selects best flexibilities, so carries out the final individual bid selection based on its new grid information. SSO informs FP, PSO and FSP Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | 6a6d00e5-7ffc-4832-9b93-a346392c62cb | 908bfa7a-c616-4b2b-a712-04aac115429b | bb2896bc-89a8-400e-99c4-c560a72ebe7f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.5 | Collect the resulting requests of the SO and send request for activation | Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | 908bfa7a-c616-4b2b-a712-04aac115429b | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | bb2896bc-89a8-400e-99c4-c560a72ebe7f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.6 | Collect the resulting requests of the SO and send request for activation | Modsarus Use Case::InstanceName=Flexibility Bid Modsarus Use Case::InstanceDescription= | 908bfa7a-c616-4b2b-a712-04aac115429b | bb2896bc-89a8-400e-99c4-c560a72ebe7f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | |||
| 1.7 | Forward resulting flexibility request | Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | 2b8f28a5-4b5a-49fb-92fa-1728b089ce00 | bb2896bc-89a8-400e-99c4-c560a72ebe7f | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.8 | 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.9 | 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.10 | Forward activation confirmation | Modsarus Use Case::InstanceName=Activated Flexibility Modsarus Use Case::InstanceDescription= | 4e694b8b-e0eb-4b2a-ae7a-1bcb6f656385 | eb116f35-39eb-4ce4-8136-5fa3c744b655 6a6d00e5-7ffc-4832-9b93-a346392c62cb 908bfa7a-c616-4b2b-a712-04aac115429b | 6bc23364-c3c2-4760-8065-7fba38f1d821 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.11 | Register flexibility activation confirmation | Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | eb116f35-39eb-4ce4-8136-5fa3c744b655 | eb116f35-39eb-4ce4-8136-5fa3c744b655 | 6bc23364-c3c2-4760-8065-7fba38f1d821 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.12 | Register flexibility activation confirmation | Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | 6a6d00e5-7ffc-4832-9b93-a346392c62cb | 6a6d00e5-7ffc-4832-9b93-a346392c62cb | 6bc23364-c3c2-4760-8065-7fba38f1d821 | 4c275fe9-7bd5-4a43-bccb-e8541ffa25a3 d1ef6b9b-72a4-49e7-be5d-62693dd1cb2b | ||
| 1.13 | 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= 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 |
|---|---|---|---|
| bb2896bc-89a8-400e-99c4-c560a72ebe7f | Flexibility Bid | —- | |
| ec556f1b-8608-4de1-ab7c-a7e614f2bc37 | Flexibility Potential | —- | |
| 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 |
7. Common Terms and Definitions
8. Custom Information (optional)
| Key | Value | Refers to Section |
|---|