: Public <<Narrative>> Narrative
Created: 19/09/2018 10:36:23
Modified: 19/09/2018 10:36:23
Project:
Advanced:
Attribute
Public string
  completeDescription
Details:
Notes: The Use Case defines information exchange between TSO and DSO necessary for exploitation of DSO-connected resources for balancing purposes in the market environment. Two scenarios are identified. <br/>In the first scenario the BSP provides services directly for the TSO even if the resources were connected to distribution system. DSO will participate in the pre-qualification process to technical validate the services. It is also considered that the DSO can participate in the offering process, validating the merit order list defined by the TSO taking into account the impact in the distribution system. In the second scenario, the TSO will use the demand response operated by the DSO. It is important to mention that this scenario does not reflect the way how systems work today in most of the power systems. Nowadays, the balancing services are assured mainly by BSPs in competition operating large generators, and in the future it is expected that DER will also be operated in a competition framework. Therefore, within this scenario, it is important to test different solutions (local DR operated by multiple BSPs or by a single one – namely the DSO) identifying the advantages and inconvenient of each one. The scenario subject to demonstration can be seen as a transitory solution while the single TSO/DSO services market is not a reality.<br/>The use case is divided into two scenarios with the following actions:<br/><b>SCENARIO 1:</b> BSP provides balancing capacity using asset connected to the distribution grid. <br/><ul>
<li>Prequalification: TSO collects data from each balancing service provider intending to provide balancing energy or balancing capacity. BSP asset is connected to the distribution grid and this is done in close cooperation with DSO. This is to ensure during pre-qualification that the party connected to the grid is appropriately included in the process. In this process, BSP must guarantee adequate unit features (e.g. preparation period, ramping period, full activation time, minimum and maximum quantity, deactivation period, min and max duration of activation period), measurement and communication capabilities. BSP should pre-qualify the Distributed Flexibility Resources (DFR) activation even if the service was provided by an aggregator managing several individual resources. The DSO should be involved in the pre-qualification process for the resources connected in the distribution system. </li><li>Bidding: TSO procures both aFRR and mFRR capacity through tendering procedure. Before real-time operation, TSO collects individual offers from Balancing Service Providers (BSPs) in its control area in order to create merit order list (MOL). In the bidding, two possibilities should be considered. In the first one, is considered that the DSO only participate in the pre-qualification but not in the bidding process. In this case the DSO should pre-qualify the BSP considering that all BSP in the same distribution network will be activated. In the second case, the DSO also participates in the bidding process. This means that in the pre-qualification the TSO will pre-qualify the BSP base in their individual impact in the distribution network and afterwards the DSO can limit the use of BSP services in the bidding process. </li><li>Activation of balancing capacity: Activation is based on the merit order list. BSP sends real-time information to TSO. BSP archives data for ex-post monitoring. Also, DSO may limit the activation of offers that could push the distribution grid to the limits (e.g. cause congestions). </li><li>Imbalance settlement: Settlement between TSO and BSPs is done on pay-as-bid principle. Delivered energy is settled in accordance with metered response for aFRR and requested response for mFRR. </li></ul>
<br/><b>SCENARIO 2:</b> TSO use the DSO demand response mechanism for balancing purposes.<ul>
<li>Prequalification: TSO carries out the tests, prior real-time operation, to examine DSO technical capability for mFRR/aFRR product. </li><li>Bidding: TSO procures balancing capacity through tendering procedure. Before real-time operation, TSO collects individual offers from Balancing Service Providers (BSPs) in its control area in order to create merit order list (MOL). TSO (and also DSO) must inform possible limitations due to TSO/DSO network constraints (e.g. overload of a transformer at TSO/DSO border). DSO sends bids for the balancing services. </li><li>Baseline forecast: DSO provides balancing capacity using demand response mechanism (e.g. Conservation Voltage Reduction) as mFRR balancing service. DSO provides short-term (hours scale) consumption forecast to TSO in advanced (reference for the provided balancing service). The consumption forecast may be either calculated available flexibility at a given consumer connection point or baseline forecast. As a part of the same process, DSOs must aggregate, whenever needed, the corresponding information from all TSO/DSO connection points or balancing zones. DSO provides this information to TSO. Limitations must be informed by all the actors. </li><li>Activation of balancing capacity: Activation is based on the merit order list. Real time activity during which DSO reduced consumptions and sends real-time information to TSO. DSO sends information about power realisation to TSO. TSO monitors quality of service parameters and takes adequate actions if these parameters are violated. In case of aFRR real-time data exchange is required (control signal, base line, realisation). For mFRR achieved data can be provided for ex-post analyses. </li><li>Imbalance settlement: After the activation, the TSO, or any other responsible entity (i.e. market operator), performs the imbalance settlement and financially compensate the procured power for the balancing service. </li></ul>
In aFRR case, data is exchanged in real-time utilizing published/subscribe model.<br/><br/>In mFRR case real-time exchange is not necessarily needed. This case includes data exchange which can occur after service delivery (ex-post analysis). Software platforms are already available for this end (ex.: ECP platform by ENTSO-E).<br/><br/>Frequency and voltage stability must be also ensured locally, and it is a DSO task to be done. In this context, TSOs might need to make use of flexibility in the distribution grid to reduce cross-border imbalances or between balancing zones, thereby encouraging information and data exchange. The DSOs should be enabled by the TSO-DSO interface to fulfil their task. High automation of the process close to SCADA systems could support the security of supply throughout the process.<br/><br/>Both operators should define the data they need from each other. Both operators should define the data they need from each other. <br/>
Public string
  scope
Details:
Notes: Demonstrate the best practices on how ancillary services provided by flexibility resources connected to a distribution grid be can efficiently exploited in a balancing market. The use is applied mostly for tertiary (mFRR) and in some cases also for secondary (aFRR) and primary frequency regulation (FCR). Use case will validate data modelling and data exchange mechanisms between DSO and TSO at preoperational, operational and post operational time scales. The cooperation and information exchange between TSO-DSO must ensure overall safe grid operation.<br/>Local constraints including voltage or operational reasons may use smart grid approaches for resolution. <br/>
Object Type Connection Direction Notes
«BUC» Activation of DSO-connected resources for balancing purposes in market environment BusinessUseCase Dependency From