Task Force icaros. Integrated Coordination of Assets for Redispatching and Operational Security. Meeting 5 November 21, Elia

Transcription

1 Task Force icaros Integrated Coordination of Assets for Redispatching and Operational Security Meeting 5 November 21, 2017 Elia Web page:

2 Topics 1. Validation of meeting report of 10/10/ Design notes - Approach 3. Interdependencies between # roles 4. Link with new Federal Grid Code 5. Specific topics Demand facilities (directly ELIA-connected or via CDS): outage planning & scheduling obligations new proposal Coordinability Implementation 6. Planning Disclaimer: The slides are informative. The new market design is under development and still under discussion. 2

3 Validation of meeting report of 10/10/2017 > No comments received: report validated

4 Design notes (Launch public consultation 11/12/2017)

5 General Set of notes: Future roles and responsibilities for the delivery of ancillary service Design note for the coordination of assets: Part I Outage Planning Design note for the coordination of assets: Part II Scheduling and Redispatching Design note for the coordination of assets: Part III Congestion Risk Indicator Will be distributed for a public consultation on 11/12/2017 with deadline to respond by 15/01/2018 Disclaimer: The slides are informative. The new market design is under development and still under discussion. 5

6 Note Future roles and responsibilities for the delivery of ancillary service List of future roles: icaros Grid User Access Holder Outage Planning Agent Scheduling Agent Balance Responsible Party Balance Service Provider Voltage Service Provider Defence Service Provider Restoration Service Provider For each new role: - Description of the role - Evolution from historical to future context - Important milestones (estimation December 2017) - Overview of future interdependencies with other roles - Reference to documentation with more detailed information All topics will be discussed further in 2018: some within icaros, some in other projects/task forces Disclaimer: The slides are informative. The new market design is under development and still under discussion. 6

7 Design note for the coordination of assets: icaros Design note for the coordination of assets: Part I Outage Planning Design note for the coordination of assets: Part II Scheduling and Redispatching In general the following information is described for outage planning, scheduling, and redispatching: Purpose for ELIA: Why does ELIA need the requested information? Responsible Party: Outage Planning Agent / Scheduling Agent Interdependencies with other roles (see next slides) Obligations on Asset Level (PGM, demand, storage) Data exchanges (availability statuses, active power restrictions, schedules, bids for redispatching, ) Time Aspects (Calendars, granularity, deadlines, ) Amendments requested by the Agent or by ELIA (of availability plans / schedules, schedule modification due to activation, ) Remuneration mechanisms Verification & Liabilities Impact on Federal Grid Code (see next slides) Disclaimer: The slides are informative. The new market design is under development and still under discussion. 7

8 Design note for the coordination of assets: icaros Design note for the coordination of assets: Part III Congestion Risk Indicator The following information is described on the CRI: Purpose for ELIA How is the CRI determined? What does the CRI mean? Impact on different procedures and roles Publication of CRI Impact on Federal Grid Code Disclaimer: The slides are informative. The new market design is under development and still under discussion. 8

9 Interdepencies between #roles

10 Note Future roles and responsibilities for the delivery of ancillary service Historical roles & responsibilities Access Grid User Access Holder Balance Responsible Party CIPU signatory Outage plans Scheduling Bidding for redispatching Non-reserved flexibility for balancing AS provision FCR/R1 afrr/r2 mfrr/r3 Mvar Ancillary Service Black Start Service CIPU = Coordination of the Injection of Production Units / AS = Ancillary Services 10

11 Note Future roles and responsibilities for the delivery of ancillary service Current roles & responsibilities Access Grid User Access Holder Responsible party Balance (& BRP source) CIPU signatory AS provision Mvar Black Start Non-CIPU: Balancing Service Provider BRP BSP * BSP AS provision FCR/R1 afrr/r2 mfrr/r3 AS provision FCR/R1 afrr/r2 (pilot) New mfrr/r3 ARP = Access Responsible Party / BRP = Balance Responsible Party / CIPU = Coordination of the Injection of Production Units / AS = Ancillary Services BSP = Balancing Service Provider / Rx = reserved balancing capacity * Only as soon as there is ToE applied 11

12 Note Future roles and responsibilities for the delivery of ancillary service Future roles & responsibilities Balance Responsible Grid User Access Holder Balance Party source Balance Service Provider Balance Responsible Party BSP * Scheduling Agent Outage Planning Agent Restoration Service Provider FCR/R1 afrr/r2 mfrr/r3 Scheduling Bidding for redispatching Outage plans Black Start Service Reserved & nonreserved Focus icaros design notes + Interdependencies with other roles Defence Service Provider * Only as soon as there is ToE applied Voltage Service Provider Mvar Ancillary Service 12

13 Interdependencies Work in progress Impact on Outage Planning Agent Scheduling Agent BSP BRP source Outage Planning Agent Availability Availability Availability Scheduling Agent Availability of free balancing bids & baselining BRP perimeter correction / schedules vs nominations BSP Schedule modification BRP perimeter correction BRP source Principle: Elia may signal that submitted data is not consistent with previous received/agreed data. If so the concerned market role needs to contact the Grid User for more information in order submit new correct data

14 Outage Planning Agent Work in progress Who and What? - the owner or a third party appointed by the owner Outage Planning Agent Scheduling Agent BRP source - the task of planning the availability status of a relevant po wer generating module, a relevant demand facility or a relevant grid element - The task of delivery active power capacity restrictions, i.e., temporary deviations from the structural Pmax & Pmin BSP Interdependencies: Impact on other roles Outage Planning determines availability of an asset/flexibility for delivering electricity or ancillary services. The availability status (available / unavailable / testing) determines - the schedules (Scheduling Agent) and nominations (BRP) resulting from DA/ID markets Interdependencies: Impact by other roles - Coherent level for data exchange needed across outage plans, schedules (Scheduling Agent), bid for congestion (Scheduling Agent) or for balancing (BSP) - the flexibility bid for congestion (Scheduling Agent) - the flexibility bid for balancing (BSP) - the flexibility available for the portfolio management of the BRP Disclaimer: The slides are informative. The new market design is under development and still under discussion. 14

15 Scheduling Agent Work in progress Who and What? Outage Planning Agent Scheduling Agent BRP source - the owner or a third party BSP/FSP appointed by the owner - the task of providing schedules in Day-ahead and intraday from market participants to ELIA - The task of bidding flexibility for congestion management in Day-ahead and Intraday to the ELIA BSP Interdependencies: Impact on other roles - BSP: MW schedules as baselines for congestion and balancing activations - BSP/BRP: May-Not-Run schedules reduce the marketability of flexibility on an asset on day D - BSP: Activation of redispatching bids affects availability for balancing bids Interdependencies: Impact by other roles - Availability of assets for electricity markets and ancillary services determined in outage planning (Outage Planning Agent) - Coherent level for data exchange needed across outage plans, schedules (Scheduling Agent), bid for congestion (Scheduling Agent) or for balancing (BSP) - BRP perimeter correction when activating flexibility for redispatching (no Transfer of Energy applicable) - Firmness of schedules enforced by ELIA in case of congestion: limitation on use of flexibility by BRP Disclaimer: The slides are informative. The new market design is under development and still under discussion. 15

16 Balance Responsible Party Work in progress Outage Planning Agent Scheduling Agent BRP source Who and What? - Responsible for imbalances BSP Interdependencies: Impact on other roles / Interdependencies: Impact by other roles - Availability of assets for electricity markets and balancing management determined in scheduling & outage planning (Outage Planning Agent & scheduling agent) - Nominations on Day ahead basis: availability of assets (Outage planning agent) - BRP perimeter correction when activating flexibility for redispatching (Scheduling Agent) or for balancing (BSP) Disclaimer: The slides are informative. The new market design is under development and still under discussion. 16

17 Balancing Service Provider Work in progress Who and What? Outage Planning Agent Scheduling Agent BRP source - a market participant with reserve-providing units or reserve-providing groups able to provide balancing services to TSOs; - Balancing services refer to balancing energy ( free bids ) or balancing capacity ( reserves ) BSP Interdependencies: Impact on other roles - BRP perimeter correction when activating flexibility for balancing (Transfer of Energy applicable) - Modification of MW schedules applicable for Scheduling Agent in case of Bid activation Interdependencies: Impact by other roles - Availability of assets for delivery of contracted reserves and ancillary services determined in outage planning (Outage Planning Agent) - Coherent level for data exchange needed across outage plans, schedules (Scheduling Agent), bid for congestion (Scheduling Agent) or for balancing (BSP) - MW schedules from the Scheduling Agent as baselines for balancing activations ELIA has proposed that Scheduling agent role is performed by Grid user or BSP - May-Not-Run schedules (Scheduling Agent) reduce the marketability of flexibility on an asset on day D - Non-reserved flexibility can be used by ELIA for redispatching (Scheduling Agent) Disclaimer: The slides are informative. The new market design is under development and still under discussion. 17

18 Link with new Federal Grid Code

19 Design note for the coordination of assets: Part I-III (Outage planning, scheduling & redispatching, CRI) 2018 Oct Nov Dec Jan Feb Mar Apr May 11/12 15/01 7/2 17/5 Public consultation of market design note Workshop Federal Grid Code Public consultation on icaros design in preparation of Workshop Federal Grid Code 7/2: Submission Proposal for New Federal Grid Code by May 2018 preceded by a public consultation Design notes will include a list of design principles which ELIA proposes to prescribe in the Federal Grid Code Key principles prescribed in the European Guideline on Electricity Transmission System Operation (GL SO) or Key Organizational Roles, Responsibilities and Requirements (KORRR, draft version) do not require repetition in the Federal Grid Code: a list of these key principles will also be given in the design notes Disclaimer: The slides are informative. The new market design is under development and still under discussion. 19

20 Current Federal Grid Code HOOFDSTUK VII. - Toegang tot het net van een productie-eenheid en opvolging van de injectie Afdeling III. Contract voor de coördinatie van de inschakeling van productie-eenheden Art Een contract voor de coördinatie van de inschakeling van de productie-eenheden wordt tussen de netbeheerder en de toegangsverantwoordelijke belast met de injectie van een productie-eenheid afgesloten. Art Het contract voor de coördinatie van de inschakeling van de productie-eenheden regelt de rechten en plichten van de partijen bedoeld in dit besluit en in het bijzonder : 1 de coördinatie van de inschakeling van de productie-eenheden overeenkomstig Hoofdstuk XIV en de betreffende financiële voorwaarden; 2 de modaliteiten met betrekking tot het dagelijks toegangsprogramma overeenkomstig Afdeling III van Hoofdstuk XI; 3 de modaliteiten met betrekking tot het dagelijks coördinatieprogramma overeenkomstig Hoofdstuk XII. Coordination of injection - Between TSO and ARP - Calendar of (de)commissioning - Revision planning - Availability program of a power unit - Production plan of a power unit - Delivery + adaptation of daily access programs For each procedure : high-level indication of timing, possible change, remuneration, Daily access programs - Between TSO and ARP - TSO can determine specific modalities for RES & CHP - Data exchanges in Day-ahead - Right of TSO to adapt access programs in Intraday Daily coordination programs - Between TSO and ARP - Availability of upward and downward active power flexibility: data exchanges in Day-ahead Disclaimer: The slides are informative. The new market design is under development and still under discussion. 20

21 Principles in New Federal Grid Code (1) - Roles (in addition to definitions) Work in progress - The Grid User must appoint the Outage Planning Agent / Scheduling Agent via the connection contract. - If the Grid User does not act as Scheduling Agent, than the Grid User must appoint one Flexibility Service Provider as Scheduling Agent. - If the asset s flexibility is offered for balancing by a Balancing Service Provider, then the Flexibility Service Provider acting as Scheduling Agent must be the same party as the Balancing Service Provider. - The Scheduling Agent is also responsible for bidding flexibility for redispatching to the TSO. - The Grid User must assure a correct coordination between Outage Planning Agent and Scheduling Agent. Disclaimer: The slides are informative. The new market design is under development and still under discussion. 21

22 Principles in New Federal Grid Code (2) Asset types (in addition to definitions) Work in progress - Level of coordination for production: Power Generating Module or Power Unit when relevant. - Energy Storage devices type B/C/D: - in general same requirements as for Power Generating Modules; - exemptions or alternative modalities described in Terms and Conditions - TSO-connected demand facilities & TSO-connected CDS: - subject to outage planning obligation - subject to DA scheduling obligation - exempted from ID scheduling obligation - The TSO can define the rules for exempting assets from obligations for exchange of outage plans, schedules, and from bidding flexibility for congestion management in the Terms and Conditions, as long as the exemptions are in compliance with the EU guidelines. Disclaimer: The slides are informative. The new market design is under development and still under discussion. 22

23 Principles in New Federal Grid Code (3) (in addition to definitions) Work in progress - Modalities on data exchange will be described in Terms and Conditions, to be submit by the TSO for approval to the regulating authority. - Power Generating Modules & Energy Storage Devices type B, C, D are obliged to offer their full available flexibility for redispatching to the TSO, taking into consideration the level of coordinability of the asset and flexibility that is contracted as a reserve for balancing. - To the extent possible, ELIA will neutralize the effect of activating flexibility for congestion management on the imbalance position of the ELIA control zone. - Description of Transition period from CIPU to icaros Disclaimer: The slides are informative. The new market design is under development and still under discussion. 23

24 No repetition in New Federal Grid Code of Work in progress Key principles prescribed in SO GL: - TSO-connected and CDSO-connected Power Generating Modules type B, C, and D are obliged to deliver - Availability plans - Schedules in Day-ahead and Intraday. - TSO-connected Demand Facilities are obliged to deliver schedules in Day-ahead. - Each grid user obliged to deliver schedules, must take on the role of Outage Planning Agent / Scheduling Agent or appoint a third party. Key principles prescribed in KORRR (draft version): - The Grid User shall remain responsible for ensuring compliance with the obligations from the European Guidelines on Transmission System Operation, even if the Grid User delegates the task of Scheduling Agent to a third party - The Grid User remains responsible for the quality of the delivered schedules, even if the Grid User delegates the task of Scheduling Agent to a third party. - The requirements to exchange schedules are defined by the TSO. - The Grid User is responsible for the real-time execution of availability plans. Disclaimer: The slides are informative. The new market design is under development and still under discussion. 24

25 Specific topics

26 Overview Demand facilities (directly ELIA-connected or via CDS): outage planning & scheduling obligations new proposal Coordinability Implementation Disclaimer: The slides are informative. The new market design is under development and still under discussion. 26

27 Demand facilities OUTAGE PLANNING Interpretation: indication of substantial deviations from normal business and therefore from normal offtake pattern (e.g. due to incidents, bankruptcy, renovations, annual holiday, ) Previous design proposal: focus on cross-border relevant assets New design proposal: Outage planning on demand broader than only cross-border relevant, yet pragmatic solution with limited workload on both sides Merge with other existing process: yearly survey of ELIA-connected demand facilities & CDS on short-, mid-, long-term forecasts, including periods of low activity or inactivity SCHEDULING Previous design proposal: DA scheduling obligation for all ELIA-connected demand facilities (direct or via CDS); no ID scheduling obligation New design proposal: DA scheduling obligation for large ELIA-connected demand facilities (direct or via CDS); no ID scheduling obligation Threshold to define whether a demand facilities is considered as large : Contractual Offtake Power or Power Put At Disposal 25MVA Disclaimer: The slides are informative. The new market design is under development and still under discussion. 27

28 Coordinability To take into account different types of flexibility To register which assets are exempted from bidding flexibility for redispatching To allow case-by-case agreement on coordinability levels for process-driven generators Fully coordinable - the asset can respond quickly to activations by ELIA (within the quarter-hour) - flexibility typically also offered in standardized balancing products. Limited coordinable - the asset can respond to activations by ELIA during Intraday but only under specific conditions, such as: activation requested sufficiently ahead in time (longer start-up or ramp-up) depending on business process of linked demand facility: a start-up may one day take 5 hours while on other days this may be reduced to 2 hours The coordinability level on an asset can be different: per direction: e.g., RES: decremental coordinability but not incremental between operating and non-operating mode: e.g., slow to start-up (limited coordinable) but quickly responding once in operating mode (fully coordinable) Not coordinable - the asset does not have flexibility that can be activated by ELIA for redispatching or balancing purposes Disclaimer: The slides are informative. The new market design is under development and still under discussion. 28

29 Implementation ELIA view: room for pragmatic temporary solution Transition period CIPU PGM: largely compliant to GL SO obligations regarding delivery of operational information Transition period: BRP as Outage Planning Agent & Scheduling Agent [Transition from implicit => explicit bidding: GL EB, linked to creation of European platforms] Non-CIPU units with outage planning & scheduling obligation: => PGM type B Transition period: default status at available and default schedule at ON Create pragmatic communication to inform ELIA of unavailability or OFF schedules Demand: scheduling obligation during transition tackles together with transition of BRP nominations with CIPU to BRP nominations without CIPU Storage: no GL SO obligations Disclaimer: The slides are informative. The new market design is under development and still under discussion. 29

30 Planning

31 Project Timeline 2017 Working Group Balancing 2018 Oct Nov Dec Jan Feb Mar Apr May 21/11 11/12 15/01 7/2 17/5 Today Public consultation of market design note Workshop Federal Grid Code Submission Proposal for New Federal Grid Code by May 2018 preceded by a public consultation Planning 2018 will be presented during Working Group Balancing end 2017 / beginning 2018 Disclaimer: The slides are informative. The new market design is under development and still under discussion. 31

32 Many thanks for your attention! Sofie Van den waeyenberg ELIA SYSTEM OPERATOR Boulevard de l'empereur Brussels info@ elia.be An Elia Group company