EACL-PL-03
Event-driven Active Power Management for Congestion Management and voltage control by the DSO
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 | Poland, | EACL-PL-03 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|
| 0.9 | 2021-09-10T00:00:00 | Wojciech Lubczyński and Dominik Falkowski (PSE), | None | None |
1.3. Scope and Objectives of Use Case
| |
|---|
| Scope | The scope of BUC covers the use by the distribution system operator (DSO) of the service providers' active power capabilities to eliminate congestion and voltage violations in the distribution network. The services would be purchased using an IT Flexibility platform on market condition |
| Objective(s) | • Elimination of congestion in the distribution network using active power |
| • Elimination of voltage violations in the distribution MV and LV network, using active power | |
| • Coordination of TSO and DSO activities in the field of congestion management and voltage control | |
| Related business case(s) | EACL-PL-01 Prequalification, |
| EACL-PL-02 Balancing | |
1.4. Narrative of Use Case
Short description
Scenario 1
This scenario describes actions that need to be performed as a first for acquiring services from the market. It focuses on the bidding process for the congestion management and voltage control for DSOs needs in the cases of day ahead auctions and medium term auctions. In both cases procedure is the same. The difference is in the timeline of each step. In the case of the medium term auction, DSO in the first step pays for the capacity from FSP for the selected period of time and in case of activation, DSO pays for the energy. In the case of the bids selected in the Day ahead auctions, DSO pays for the energy,
• Selection/Bidding
Description: The process of selecting offers from the market to solve the DSO problem related to network congestion or voltage violations with the use of active power management.
The DSO opens an auction with detailed information about the location affected by the problem and providing all the required parameters to receive offers. Offers are submitted by FSPs who have successfully passed the prequalification process. Before selecting an offer, network analyses are performed, which eliminates offers that have a negative impact on the operation of the DSO network reporting the need or others DSOs. In detail, it includes:
o DSO calls the auction on the Flexibility Platform for an action related to active power change for a strictly defined network area for the congestion or voltage violations as a result of the event in the network. The triggering event will be different for the day ahead auctions and the medium term auctions.
o Flexibility Platform informs FSPs about the new need for service from the DSO side and the appearance of the auction. Flexibility platform collects all bids submitted within the specified by DSO time frame
o The MOL stack is created
o Collected offers are analysed in terms of the possibility of solving a network problem, taking into account the impact on networks of others DSOs (in the case under consideration and in the specific network operation state)
o Choosing the optimal offers
o Based on analysis an offer / offers that allow to remove congestion or solve voltage problems from the network are selected.
o The selected offer or offers are stored by the flexibility platform, then dispatched the day before delivery and added to the group of offers sourced in the day-ahead process.
Complete description
The process carried out on the Flexibility Platform in day-ahead time frame consists of the following steps:
Scenario 1 – Determination of TSO needs in terms of capacity
• Every morning TSO also announces information on the constraints in the network.
• The Flexibility Platform Operator (FPO) takes the above-mentioned information from TSO and makes it available as soon as possible on the Flexibility Platform to interested parties.
• Every morning the Flexibility Platform may also make available information on the constraints in the distribution network that may affect the technical feasibility of potential offers for balancing capacity products and balancing energy.
| ID | Name | Description | Reference to mentioned use case objectives |
|---|
1.6. Use case conditions
| Relation to other use cases |
|---|
|
| Level of depth |
| Prioritisation |
|
| Generic, regional or national relation |
| National Polish Flexibility Market |
| Nature of the use cases |
| Business Use Case |
| Further keywords for classification |
| Medium term, day ahead, planed work DSO, Operational, Congestion management, Voltage control, voltage violation |
2. Diagrams of Use Case
3. Technical Details
3.1. Actors
| Actor Name | Actor Type | Actor Description | Further information specific to this Use Case |
|---|
| Transmission System Operator (TSO) | Business | A natural or legal person who is responsible for operating, ensuring the maintenance of and, if necessary, developing the transmission system in a given area and, where applicable, its interconnections with other systems, and for ensuring the long-term ability of the system to meet reasonable demands for the transmission of electricity | |
| Distribution System Operator (DSO) | Business | A natural or legal person who is responsible for operating, ensuring the maintenance of and, if necessary, developing the distribution system in a given area and, where applicable, its interconnections with other systems, and for ensuring the long-term ability of the system to meet reasonable demands for the distribution of electricity | |
| Flexibility Service Provider (FSP) | Business | A natural or legal person who is a market participant providing flexibility services to any electricity market that represents and aggregates the capacity of the entities that own a distributed energy resources (DER). | |
| Market Operator (MO) or Flexibility Platform Operator (FPO) | Business | A natural or legal person who organizes auctions (continuous auction, discrete auctions, call for tenders) between buyers and sellers of electricity-related products in the markets. Manage/operate the platform for trading (where bids and offers are collected). Clear the market and communicate results. | |
| Flexibility Service Provider being Aggregator (FSPA) | Business | A party who is a market participant providing flexibility services to any electricity market that represents and aggregates the capacity of the entities that own a distributed energy resources | |
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 | Selection/Bidding for mid-term and day-ahead | Based on the results of network analyzes the DSO identifies the problem with congestion or voltage violation in the distribution network as a result of the specific event. In the case of scheduled works, it can be . specific network configuration, preventing the execution of the planned work. For the day ahead operational the cause of the network problem may be related to deviation in the forecast or some network failure that has an impact on the grid configuration. The DSO decides to launch an auction in order to take advantage of the available sources of flexibility in the market to guarantee that the correct grid operation during normal operational and planned work is under consideration. The auction is launched a day ahead or several weeks in advance for planned works and concerns active power control activity by customers connected to specific locations in the distribution network for which problems have been identified. In case of medium term auctions launched for planned works, DSO contracts capacity and energy from FSP. One of the key elements is coordination between DSO and TSO in the field of contracting bids for CM and balancing. Coordination is needed so that the actions of one party do not cause problems for the other party. Thanks to the coordination of activities, it is also possible to obtain an optimal solution in economic terms (solving balancing and CM problems using the same offers). | | Selection/Bidding for mid-term and day-ahead | | |
| 2 | Delivery for DSO | Activation and delivery of the offer by a strictly defined FSPs resource under the previously contracted offer for the DSO. After contracting the offer under scenario 1, the DSO performs the final assessment of the feasibility of planned work and the legitimacy of using the offer. After the final confirmation of the necessity to activate the offer for medium term auctions, the DSO sends information to the platform operator about the commencement of activation of the contracted offer. Based on the information received from the platform operator, the FSP activates his resource and provides the service following the contracted offer. The DSO supervises the execution of the offer by the client in real-time. | | Delivery for DSO | | |
| 3 | Settlement | Market platform operator collects all data that are necessary to create an invoice for the provided services. Base on the contracted bid, baselines and meter data MPO verifies which offers have been made correctly, which have been partially made and those that have not been performed. Performs financial calculations and prepares invoices. | | Settlement | | |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Selection/Bidding for mid-term and day-ahead |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| Scenario Name: |
|---|
| Delivery for DSO |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|
6. Requirements (optional)
| Category Identifier | Name | Description | mRID |
|---|
| Req_ID | Req_Name | ‘Event-driven Active Power Management for Congestion Management and voltage control by the DSO’ | |
| Identifier | Name | Description | mRID |
|---|
7. Common Terms and Definitions
| Key | Value | Refers to Section |
|---|