edf-1
Coordination of distributed flexibility resources in a marketplace
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 | Distribution Management, Energy Markets, Transmission System, Distribution System, Users, Operational planning, | edf-1 |
1.2. Version Management
| Version No. | Date | Name of author(s) | Changes | Approval status |
|---|---|---|---|---|
| 1 | 2018-03-15T00:00:00 | Nermin Suljanovic, Andrej Souvent (EIMV); Hugo Morais, Belén Goncer, Jérôme Cantenot (EDF), | Final version | Approved by consortium members |
1.3. Scope and Objectives of Use Case
| Scope | - Validation of TSO/DSO coordination mechanism to distributed flexibility resources procurement avoiding double or counter activation of the same flexibility resource by TSO and DSO - Prevent the negative impact of offers activation in the networks - Definition of the data that should exchange between the TSO, the DSO and the market operator. |
| Objective(s) | Improve the system security. Take advantage of increasing amount of flexibility resources connected in the distribution grid for providing services for the benefits of the overall power. Achieve competitiveness of flexibility resources in a common pool and obtain market liquidity. Test different solutions to validate the flexibility offers both by TSO and DSO. Investigate different strategies for TSO-DSO coordination that will maximise usage of flexibility services. |
| Related business case(s) | 01314521-bbb8-496a-b55b-8405057935eb |
1.4. Narrative of Use Case
Short description
This use case defines information exchanges between TSO, DSO, Flexibility Operators and Market Operator necessary for procurement of flexibility provided by distributed energy resources.
Flexibility Operator interacts both with TSO and DSO and it is necessary to validate coordination mechanism that will prevent double activation of the same service at the same time. TSO and DSO should also collaborate in order to avoid negative impact of DFR (Distributed Flexibility Resource) activation on their respective networks.
Three main scenarios should be considered:
- The Flexibility Operator provides services for the TSO (national flexibility market) and the DSO should validate, in day-ahead or intraday timeframes, the activation of these flexibilities (for the resources connected in distribution network)
- The Flexibility Operator provides services for the DSO (local flexibility market). The DSO should provide, in day-ahead, the forecast load/generation for each primary substation including the activation of the procured flexibilities. The TSO should take into account this information for the balancing and congestion detection proposes.
- The Flexibility Operator connected to distribution network provides services for the both for TSO and DSO in a coordinated local and national market mechanism. The offers not accepted in the local market are sent to the national market. At national market the TSO can obtain flexibilities from the Flexibility Operators connected on transmission and distribution networks.
- The Flexibility Operator provides services for the both for TSO and DSO in a single procurement platform (single market). The activation of the offers should be agreed both by TSO and DSO.
Complete description
Flexibility services can be used at the electricity market for the three types of actions:
- portfolio optimisation of market players
- constraints management in transmission and distribution networks (at day-ahead and intraday markets)
- balancing to ensure power system security (balancing market).
Enabling flexibility services must not lead to market fragmentation or competition distortion. However, settlement of constraint management and balancing must be clearly separated. DFR providers must be able to sell their services to both TSOs and DSOs. TSO procures flexibility services, from large industrial consumers or aggregators. DSO procures flexibilities also from aggregators and from several types of DERs (distributed generation, demand response, decentralized storage, electric vehicles) connected to the distribution grid with the purpose to maintain quality of service and the security of supply. DSO can procure flexibility services in long and short timescales. In the present BUC, the timeframes day-ahead and intraday are considered. Coordination between TSO and DSO is needed since the same flexibility resources may be activated for balancing (TSO services) and congestion constraints management (TSO and DSO services) purposes.
Scenario 1: TSO procures the flexibilities and the DSO should validate their activation
DFR are procured by TSO for the purpose of balancing or constraint management in the transmission grid. However, the activation of the flexibilities can jeopardizes the security of supply and reduces quality of services due to, for example, power line congestions, voltage constraints or overload the power transformer at TSO/DSO border. Since the DFR are connected to distribution network, DSO should be asked to validate the DFRs procured by the TSO to avoid constraints in the distribution system.
Scenario 2: DSO procures the flexibilities and provides the forecasted load/generation by primary substation
DSO can organises a local procurement of flexibilities to prevent the operation constraints in the distribution network. The constraints can be technical (HV/MV power transformer overload, lines congestion, voltage constraints) but also contractual (agreements between TSO/DSO in the TSO/DSO borders). Since the procurement of the DFR will impact the global system operation, the DSO should include the activation of the flexibility offers in the forecasts (load/generation by primary substation) sent to the TSO in day-ahead.
Scenario 3: Coordination mechanism between local and national market
The Flexible Operators connected in distribution network should place their offer in a local market and the Flexible Operators connected in the transmission network should place their orders in a national market. The clearing mechanism in local market should provide services for the DSO to solve the distribution network constraints. The offers that are not used in the local market should be technically validated by the DSO and be transferred for the National market. After the clearing process both in local and national markets, the TSO should coordinate the activation of the flexibilities connected in the transmission system and the DSO should coordinate the activation of the flexibilities connected in the distribution network.
Scenario 4: TSO and DSO procure flexibility in a single flexibility market
To ensure the market liquidity, building a level playing field for different service providers in a single marketplace and to joint procurement of services both for TSOs and DSOs a single procurement system is needed [1]. In this single procurement platform (market) the TSO and the DSOs should include their needs to balancing and congestion management (TSO) and for congestion and voltage management (DSO). It is important to mention that some voltage constraints can appear in distribution network even if a good reactive management is implemented.
Flexibility platform enables well-structured and organised exchange of data between TSO, DSO and flexibility service provider. DSO should have visibility of aggregated resources in the distribution grid and information about individual activations. This information should be available (day ahead or intraday time frames) to ensure that market schedules are not in the conflict with network operation.
1.5. Key Performance Indicatiors (KPI)
| ID | Name | Description | Reference to mentioned use case objectives |
|---|---|---|---|
| 1 | Number of expected constraints solved by flexibilities procurement | 95bbcb38-254b-48b6-aa52-027fd4b1b50e, fa8f1c12-924f-4c09-a309-f9b8a124f1da, |
1.6. Use case conditions
| Assumptions |
|---|
| In the presented BUC is considered that the markets are performed in day-ahead or in intraday timeframes. |
| Prerequisites |
|---|
| The Distributed Flexibility Resources (DFR) operated by Flexible Operators should be already pre-qualified |
1.7. Further information to the use case for classification/mapping
| Relation to other use cases |
|---|
| SUC |
| Level of depth |
| Prioritisation |
| High level of priority: business need |
| Generic, regional or national relation |
| Generic use-case with application in different national contexts considering different scenarios |
| Nature of the use cases |
| BUC |
| Further keywords for classification |
| TSO-DSO coordination, data exchange, operational planning, flexibility markets |
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 |
|---|---|---|---|
| Market Operator | Business | The unique power exchange of trades for the actual delivery of energy that receives the bids from the parties that have a contract to bid. The market operator determines the market energy price for the market balance area after applying technical constraints from the system operator. It may also establish the price for the reconciliation within a metering grid area. | |
| Flexibility Operator | Business | Role which links through contractual agreements (flexibility requests, notices etc.) the role customer and its possibility to provide flexibilities to the roles market and grid; generic role that could be taken by many stakeholders. This entity can activate all or part of the flexibility resources during a period and regarding a specific location or geographical area. | |
| Distribution System Operator | Business | A natural or legal person 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 or gas. That definition is provided for by art. 2 n. 6 Dir 2007/72/EC with regards to electricity and by art. 2 (6) Dir 2007/73/EC with regards to gas. In the electricity sector distribution means the transport of electricity on high-voltage, medium-voltage and low-voltage distribution systems with a view to its delivery to customers, but does not include supply according to art. 2 (5) Dir, 2007/72/EC. Accordingly, distribution in the gas sector means the transport of natural gas through regional pipeline networks with a view to its delivery to customers, but not including supply. DSOs have to act according to art. 25, 26, 27 Dir. 2007/72/EC (with regards to electricity) and to art. 25, 26, 27 Dir. 2007/73/EC (with regards to gas). The aforementioned provisions provide the tasks and duties of DSOs. One of the main characteristics of the DSO is that it shall be independent at least in terms of its legal form, organisation and decision making from other activities not relating to distribution within a vertically integrated undertaking. Unlike the transmission system operator, the DSO is not affected by ownership unbundling. | |
| Transmission System Operator | Business | According to the Article 2.4 of the Electricity Directive 2009/72/EC (Directive): "a natural or legal person 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". Moreover, the TSO is responsible for connection of all grid users at the transmission level and connection of the DSOs within the TSO control area. Source : EU Commission Task Force for Smart Grids, EG3 |
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 | Scenario1A: The offers are validated before the market clearing | The Flexibility Operator provides services for the TSO (national flexibility market) and the DSO should validate, in day-ahead or intraday timeframes, the activation of these flexibilities (for the resources connected in distribution network) | ||||
| 2 | Scenario1B: The offers are validated after the market clearing | The Flexibility Operator provides services for the TSO (national flexibility market) and the DSO should validate, in day-ahead or intraday timeframes, the activation of these flexibilities (for the resources connected in distribution network) | ||||
| 3 | Scenario2: Local Market to provide services to the DSO | The Flexibility Operator provides services for the DSO (local flexibility market) and the TSO should validate, in day-ahead or intraday timeframes, the activation of these flexibilities (Consider the impact in the transmission system) | ||||
| 4 | Scenario 3: Coordination between National Market and Local Market | The Flexibility Operators connected in distribution network should place their offer in a local market and the Flexible Operators connected in the transmission network should place their orders in a national market. The clearing mechanism in local market should provide services for the DSO to solve the distribution network constraints. The offers that are not used in the local market should be technically validated by the DSO and be transferred for the National market. After the clearing process both in local and national markets, the TSO should coordinate the activation of the flexibilities connected in the transmission system and the DSO should coordinate the activation of the flexibilities connected in the distribution network | ||||
| 5 | Scenario4: National market to provide services both for TSO and DSO | The Flexibility Operator provides services for the both for TSO and DSO in a single procurement platform (single market). The activation of the offers should be agreed both by TSO and DSO |
Notes
4.2. Steps – Scenarios
| Scenario Name: |
|---|
| Scenario1A: The offers are validated before the market clearing |
| 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 | Send the Flexibility offers | The Flexibility Operator should send the offers to the market Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 1.2 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 1.3 | Gate Closure | Market gate closure Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=All the offers received before the Gate Closure | faeb9fab-a49a-4a68-bac1-ee06950c645d | f508e6d2-a475-4185-917f-c5e7eedcd4fa | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 1.4 | Determine the needs to assure the operation of transmission system (balancing and congestions) | The TSO should identify the flexibility needs to avoid constraints in transmission network Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=Margin to activatE the regulation up offers for Margin to activatE the regulation down offers Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d37347bb-a6bd-4b2e-a2cf-717ccb064b75 | faeb9fab-a49a-4a68-bac1-ee06950c645d | 19841afb-643f-4134-9105-03c4449bde7a 256e57f3-202d-4dec-b9f5-770f1c98782f | |||
| 1.5 | Offers Validation | The DSO should perform the load flows taking into account the forecasted operation conditions and the activation of the offers. If the offers activation can originate some constraints in the distribution network, the DSO can refuse the offers or propose some limits in the use of the offers (depends of the market rules) Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | f508e6d2-a475-4185-917f-c5e7eedcd4fa | faeb9fab-a49a-4a68-bac1-ee06950c645d | c7cf4214-591e-49e8-8995-fb6485f73818 | |||
| 1.6 | Needs and offers validation acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 1.7 | Offers Pre-validation | Based on offers provided by the Flexibility Operator and on the validation did by the DSO, the market operator can propose some changes to the Flexibility Operator. The changes can be of 3 types: - Change the power of the flexibility offers - Change the timeframe of activation of the offers - Change the point of activation of the flexibilities (only if the Flexibility Operator was an aggregator) The price of the offers should remain the same Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | faeb9fab-a49a-4a68-bac1-ee06950c645d | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | c7cf4214-591e-49e8-8995-fb6485f73818 | |||
| 1.8 | Offers redefinition | The Flexibility Operators can change the offer according the market operator demand. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=The price should remain the same of the initial offer | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 1.9 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 1.10 | Market Clearance | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 1.11 | Publication of Market Results | faeb9fab-a49a-4a68-bac1-ee06950c645d |
| Scenario Name: |
|---|
| Scenario1B: The offers are validated after the market clearing |
| 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 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 2.2 | Send the Flexibility offers | The Flexibility Operator should send the offers to the market Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 2.3 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 2.4 | Gate Closure | Market gate closure | faeb9fab-a49a-4a68-bac1-ee06950c645d | |||||
| 2.5 | Determine the needs to assure the operation of transmission system (balancing and congestions) | The TSO should identify the flexibility needs to avoid constraints in transmission network Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d37347bb-a6bd-4b2e-a2cf-717ccb064b75 | faeb9fab-a49a-4a68-bac1-ee06950c645d | 256e57f3-202d-4dec-b9f5-770f1c98782f | |||
| 2.6 | Needs acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 2.7 | Market Clearance | Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=Only the offers accepted in the Market Clearing | faeb9fab-a49a-4a68-bac1-ee06950c645d | f508e6d2-a475-4185-917f-c5e7eedcd4fa | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 2.8 | Offers Validation | The DSO should perform the load flows taking into account the forecasted operation conditions and the activation of the offers. If the offers activation can originate some constraints in the distribution network, the DSO can refuse the offers or propose some limits in the use of the offers (depends of the market rules) Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | f508e6d2-a475-4185-917f-c5e7eedcd4fa | faeb9fab-a49a-4a68-bac1-ee06950c645d | c7cf4214-591e-49e8-8995-fb6485f73818 | |||
| 2.9 | Offers Pre-validation | Based on offers provided by the Flexibility Operators and on the validation did by the DSO, the market operator can propose some changes to the Flexibility Operator. The changes can be of 3 types: - Change the power of the flexibility offers - Change the timeframe of activation of the offers - Change the point of activation of the flexibilities (only if the Flexibility Operator was an aggregator) The price of the offers should remain the same Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | faeb9fab-a49a-4a68-bac1-ee06950c645d | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | c7cf4214-591e-49e8-8995-fb6485f73818 | |||
| 2.10 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 2.11 | Offers redefinition | The Flexibility Operator can change the offer according the market operator demand. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=The price should remain the same of the initial offer | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 2.12 | Publication of Market Results | faeb9fab-a49a-4a68-bac1-ee06950c645d |
| Scenario Name: |
|---|
| Scenario2: Local Market to provide services to the DSO |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|---|---|---|---|---|---|---|---|
| 3.1 | Send the Flexibility offers | The Flexibility Operator should send the offers to the market Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 3.2 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 3.3 | Gate Closure | Market gate closure Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=All the offers received before the Gate Closure | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | ||||
| 3.4 | Determine the needs to assure the operation of distribution system and the limits in the offers activation (margins) | The DSO should identify the flexibility needs to avoid constraints (congestions and voltage profiles) in distribution network Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | f508e6d2-a475-4185-917f-c5e7eedcd4fa | faeb9fab-a49a-4a68-bac1-ee06950c645d | ecb2b9f4-2038-4b12-8a0e-3d5f42575c8f 256e57f3-202d-4dec-b9f5-770f1c98782f | |||
| 3.5 | Offers Validation | The DSO should perform the load flows taking into account the forecasted operation conditions and the activation of the offers. If the offers activation can originate some constraints in the distribution network, the DSO can refuse the offers or propose some limits in the use of the offers (depends of the market rules) Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | faeb9fab-a49a-4a68-bac1-ee06950c645d | c7cf4214-591e-49e8-8995-fb6485f73818 | ||||
| 3.6 | Needs and margins acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 3.7 | Offers Pre-validation | Based on offers provided by the Flexibility Operator and on the validation did by the DSO, the market operator can propose some changes to the Flexibility Operator. The changes can be of 3 types: - Change the power of the flexibility offers - Change the timeframe of activation of the offers - Change the point of activation of the flexibilities (only if the Flexibility Operator was an aggregator) The price of the offers should remain the same Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | faeb9fab-a49a-4a68-bac1-ee06950c645d | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | c7cf4214-591e-49e8-8995-fb6485f73818 | |||
| 3.8 | Offers redefinition | The Flexibility Operators can change the offer according the market operator demand. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=The price should remain the same of the initial offer | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 3.9 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 3.10 | Market Clearance | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 3.11 | Publication of Market Results | Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | faeb9fab-a49a-4a68-bac1-ee06950c645d | f508e6d2-a475-4185-917f-c5e7eedcd4fa | 1552f1d9-c58b-4e4c-b722-e756825e8bc4 | |||
| 3.12 | Definition of the consumption profiles of each primary substation | The DSO should inform the TSO concerning the forecasted consumption and or generation of each primary substation. Beyond the forecasted values the DSO should include the procured flexibility offers. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | f508e6d2-a475-4185-917f-c5e7eedcd4fa | d37347bb-a6bd-4b2e-a2cf-717ccb064b75 | 3d1a82ff-9138-4140-a2ed-1d2ceb3a9f6c | |||
| 3.13 | Forecasted primary substations use profiles acknowledged | d37347bb-a6bd-4b2e-a2cf-717ccb064b75 |
| Scenario Name: |
|---|
| Scenario 3: Coordination between National Market and Local Market |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|---|---|---|---|---|---|---|---|
| 4.1 | Send flexibility offers | The Flexibility Operator connected to transmission network should send the offers to the market Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 4.2 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 4.3 | Local Market Gate Closure | Market Gate closure | faeb9fab-a49a-4a68-bac1-ee06950c645d | |||||
| 4.4 | Determine the needs to assure the operation of distribution system and the limits in the offers activation (margins) | The DSO should identify the flexibility needs to avoid constraints (congestions and voltage profiles) in distribution network Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | f508e6d2-a475-4185-917f-c5e7eedcd4fa | faeb9fab-a49a-4a68-bac1-ee06950c645d | 256e57f3-202d-4dec-b9f5-770f1c98782f ecb2b9f4-2038-4b12-8a0e-3d5f42575c8f | |||
| 4.5 | Local Market | Local market to solve to provide services for the DSO. The information concerning the cleared offers should be transmitted to DSO. The offers not procured and validated (will not have impact in the distribution system) should be sent to the National market Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=Only the validated offers not procured in the local market | faeb9fab-a49a-4a68-bac1-ee06950c645d | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 4.6 | Local Market | Local market to solve to provide services for the DSO. The information concerning the cleared offers should be transmitted to DSO. The offers not procured and validated (will not have impact in the distribution system) should be sent to the National market Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | faeb9fab-a49a-4a68-bac1-ee06950c645d | f508e6d2-a475-4185-917f-c5e7eedcd4fa | 1552f1d9-c58b-4e4c-b722-e756825e8bc4 | |||
| 4.7 | Definition of the consumption profiles of each primary substation | The DSO should inform the TSO concerning the forecasted consumption and or generation of each primary substation. Beyond the forecasted values the DSO should include the procured flexibility offers. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | f508e6d2-a475-4185-917f-c5e7eedcd4fa | d37347bb-a6bd-4b2e-a2cf-717ccb064b75 | 3d1a82ff-9138-4140-a2ed-1d2ceb3a9f6c | |||
| 4.8 | Forecasted primary substations use profiles and flexibilities acknowledged | d37347bb-a6bd-4b2e-a2cf-717ccb064b75 | ||||||
| 4.9 | Send the Flexibility offers | The Flexibility Operator connected to distribution network should send the offers to the market Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 4.10 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 4.11 | National Market Gate Closure | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 4.12 | Determine the needs to assure the operation of transmission system (balancing and congestions) | The TSO should identify the flexibility needs to avoid constraints in transmission network Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d37347bb-a6bd-4b2e-a2cf-717ccb064b75 | faeb9fab-a49a-4a68-bac1-ee06950c645d | 256e57f3-202d-4dec-b9f5-770f1c98782f | |||
| 4.13 | National Market Clearance | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 4.14 | Publication of Market Results | faeb9fab-a49a-4a68-bac1-ee06950c645d |
| Scenario Name: |
|---|
| Scenario4: National market to provide services both for TSO and DSO |
| Step No. | Event. | Name of Process/ Activity | Description of Process/ Activity. | Service | Information Producer (Actor) | Information Receiver (Actor) | Information Exchanged | Requirements, R-ID |
|---|---|---|---|---|---|---|---|---|
| 5.1 | Send the Flexibility offers | The Flexibility Operator should send the offers to the market Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 5.2 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 5.3 | Gate Closure | Market gate closure | faeb9fab-a49a-4a68-bac1-ee06950c645d | |||||
| 5.4 | Determine the needs and the margins by zone (group of nodes HV/MV) | The TSO should identify the margin of activation of flexibility offers taking into account the impact of these offers in transmission network. The margins can be imposed by the operation of some transmission lines near by their limits. The use of margins should avoid the activation of offers to solve the DSO needs but originating congestions in transmission system. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | d37347bb-a6bd-4b2e-a2cf-717ccb064b75 | faeb9fab-a49a-4a68-bac1-ee06950c645d | 256e57f3-202d-4dec-b9f5-770f1c98782f 19841afb-643f-4134-9105-03c4449bde7a | |||
| 5.5 | Determine the needs and the margins in each node HV/MV | The DSO should identify the margin of activation of flexibility offers taking into account the impact of these offers in distribution network. The margins can be imposed by the possible congestion in power transformers in primary substations or some lines or even due to some voltage problems. The use of margins should avoid the activation of offers to solve the TSO needs but originating congestions in distribution system. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | f508e6d2-a475-4185-917f-c5e7eedcd4fa | faeb9fab-a49a-4a68-bac1-ee06950c645d | f47f7cb9-4007-44aa-8266-fd68e9c02fcc ecb2b9f4-2038-4b12-8a0e-3d5f42575c8f | |||
| 5.6 | Needs and margins acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 5.7 | Offers Pre-validation | Based on offers provided by the Flexibility Operators and on the margins provided by the TSO and DSO. The market operator should pre-validate the offers and propose some changes to the Flexibility Operators. The changes can be of 3 types: - Change the power of the flexibility offers - Change the timeframe of activation of the offers - Change the point of activation of the flexibilities (only if the Flexibility Operator was an aggregator) The price of the offers should remain the same Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription= | faeb9fab-a49a-4a68-bac1-ee06950c645d | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | c7cf4214-591e-49e8-8995-fb6485f73818 | |||
| 5.8 | Offers redefinition | The Flexibility Operator can change the offer according the market operator demand. Modsarus Use Case::InstanceName= Modsarus Use Case::InstanceDescription=The price should remain the same of the initial offer | d5aa0368-c4fe-4d82-a3d4-6fb36964b4ae | faeb9fab-a49a-4a68-bac1-ee06950c645d | cf4885b8-d5d1-4873-92c1-d09cb000223a | |||
| 5.9 | Offers acknowledged | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 5.10 | Single Market clearance | faeb9fab-a49a-4a68-bac1-ee06950c645d | ||||||
| 5.11 | Publication of Market Results | faeb9fab-a49a-4a68-bac1-ee06950c645d |
5. Information Exchanged
| Information exchanged ID | Name of Information | Description of Information Exchanged | Requirement |
|---|---|---|---|
| cf4885b8-d5d1-4873-92c1-d09cb000223a | Flexibility Offer | Power (Regulation up) Power (Regulation down) Time (Begin) Time (End) Time (Minimum duration) Time (Maximum duration) Point(s) of activation Price | —- |
| 19841afb-643f-4134-9105-03c4449bde7a | TSO Margins | Margin to activate the regulation up offers for a region (group of nodes HV/MV) and for each period Margin to activate the regulation down offers for a region (group of nodes HV/MV) and for each period | —- |
| 256e57f3-202d-4dec-b9f5-770f1c98782f | SO flexibility needs | Power (Regulation up) Power (Regulation down) Time (Begin) Time (End) Activation points (group of nodes where the offers can be activated to solve the SO problems) | —- |
| c7cf4214-591e-49e8-8995-fb6485f73818 | Flexibility limitations | Redefinition of the flexibilities (or flexibility offers): Power (Regulation up) Power (Regulation down) Time (Begin) Time (End) Time (Minimum duration) Time (Maximum duration) Point(s) of activation (Only for aggregators) | —- |
| ecb2b9f4-2038-4b12-8a0e-3d5f42575c8f | DSO Margins | Margin to activate the regulation up offers for each node HV/MV and for each period Margin to activate the regulation down offers for each node HV/MV and for each period | —- |
| 1552f1d9-c58b-4e4c-b722-e756825e8bc4 | Market Results (Selected Offers) | —- | |
| 3d1a82ff-9138-4140-a2ed-1d2ceb3a9f6c | Primary Substations use profiles | Values of forecasted consumption/generation by period and primary substations for the next day | —- |
| f47f7cb9-4007-44aa-8266-fd68e9c02fcc | DSO flexibility needs | Power (Regulation up) Power (Regulation down) Time (Begin) Time (End) Activation points (group of nodes where the offers can be activated to solve the TSO problems) | —- |
6. Requirements (optional)
7. Common Terms and Definitions
8. Custom Information (optional)
| Key | Value | Refers to Section |
|---|