Slide 1: iCAROS Taskforce workshop: design and implementation of phase 1
10/7/2020 iCAROS Taskforce workshop : design and implementation of phase 1 Date: 07/10/2020 1 1
Slide 2: Agenda
10/7/2020 AGENDA 1. Introduction – agenda – [9:30 – 9:40] 2. Design fine tuning for phase 1 • ‘real-time’ activation of redispatching energy bids – [9:40 – 9:55] • iCAROS terminology + Level of exchange of information for outage planning, scheduling & redispatching – [9:55 – 10:10] • Schedule update
Slide 3: Real-time activation of Redispatching Energy Bids
10/7/2020 Real-time activation of Redispatching Energy Bids Date: 07/10/2020 3
Slide 4: Context
10/7/2020 Context Remedial actions (among which redispatching actions) can be taken preventively (i.e. before the contingency occurs) or curatively (i.e. after the contingency occurs). In case of preventive actions, the redispatching activations are usually requested well ahead of real-time (e.g. up
Slide 5: Current design
10/7/2020 Current design The current design focuses on redispatching actions that are activated preventively, well ahead of RT: Elia can only activate a Redispatching Energy Bid till the activation deadline, which is at least 15’ before the start of the MTU* for which the bid is activated; This me
Slide 6: Reminder - definitions
10/7/2020 Presented during the last iCAROS Reminder - definitions taskforce on June 16 2020* Redispatching baseline (MW) = the last valid Daily Schedule of the Delivery Point DPSU for quarter hour qh, at the moment of the activation of the Redispatching Energy Bid Redispatching requested (MW) = the
Slide 7: New proposal 1: introduce the concept of 'real-time' activation
10/7/2020 New proposal1 : introduce the concept of ‘real-time’ activation A ‘real-time’ activation is an activation that can be requested at any time by Elia and which implies an immediate reaction of the activated Technical Facility since the Redispatching target should be reached at the latest 1
Slide 8: Impact of this new proposal on rules for settlement, activation control
10/7/2020 Impact of this new proposal on rules for settlement, activation control, correction of BRP perimeter, etc. Introduction of a new notion – ‘pro rata’ approach: Redispatching to be supplied = Redispatching requested * Period of activation during a given MTU / MTU duration Where : • Redispatc
Slide 9: Feedback and follow-up
10/7/2020 Feedback and follow-up Feedback, comments and suggestions on presented design fine tunings are kindly requested by sending it to Caroline.Bosschaerts@elia.be and Raphael.Dufour@elia.be by 21st October 2020. Follow-up via next iCAROS taskforce on February 26th 2021. iCAROS Program Manager V
Slide 10: Back-up slides
10/7/2020 Back-up slides 10 10
Slide 11: Back-up slide – rules for remuneration
10/7/2020 Back-up slide – rules for remuneration Remuneration = time unit x Redispatching to be supplied x Redispatching Energy Bid price 11 11
Slide 12: Back-up slide – rules for control of redispatching activation
10/7/2020 Back-up slide – rules for control of redispatching activation ; ! "# $% & "" & ' #( $ ) * $* # " Where: • Redispatching missing MW = Redispatching to be supplied – Redispatching supplied • Redispatching supplied (MW) = 1 Pmeasured is defined as "The difference between gross offtake and gro
Slide 13: Back-up slide – rules for BRP perimeter correction
10/7/2020 Back-up slide – rules for BRP perimeter correction Elia will correct the perimeter of the BRP with the value of the energy to be supplied (Redispatching to be supplied) as long as the BRP and the SA are the same actor (iCAROS phase 1), instead of directly evolving towards the LT vision for
Slide 14: iCAROS Terminology: Outage planning, Scheduling & Bidding obligation
10/7/2020 iCAROS Terminology Outage planning, Scheduling & Bidding obligation iCAROS Taskforce Date: 07/10/2020 14
Slide 15: Technical Unit
10/7/2020 Technical Unit Device or aggregation of devices connected directly or indirectly to the synchronous electrical network that produces and/or consumes electricity. A Technical Unit can be : • A Power Unit (PU) • A Demand Unit (DU) Examples : A combined heat and A factory on an A gas turbine
Slide 16: Technical Facility
10/7/2020 Technical Facility Complete set of Technical Unit(s) which are operationally linked and which, combined together in one or several operating modes, can consume or generate electricity on its own. A Technical Facility can be : • Synchronous Power Generating Module (SPGM) • Power Park Module
Slide 17: Operating Mode
10/7/2020 Operating Mode Any subset of Technical Units, being part of the same Technical Facility, that can generate or consume electricity on its own. Examples : Technical Technical Technical Facility Only one Unit Unit = operating mode Gas turbine Steam turbine Technical Unit Technical Facility
Slide 18: Outage Planning, Scheduling and Bidding obligation
10/7/2020 Outage Planning, Scheduling and Bidding obligation 18
Slide 19: Current design
10/7/2020 Current design The Outage Planning, Scheduling and Bidding obligations are defined on the level of Technical Facilities (‘Asset’ level in the design note). Examples: • A PGM or an ESD with an installed capacity of more than 25MW should communicate DA and ID MW schedules to Elia • A cross
Slide 20: New proposal
10/7/2020 New proposal The Outage Planning, Scheduling and Bidding obligations remain defined on the level of Technical Facilities. But beware that the definition of Technical Facility slightly defers from the definition of ‘Asset’ mentioned in the design note, since it refers to the notion of PPM
Slide 21: Schedule update in case of storm risk
10/7/2020 Schedule update in case of storm risk Date: 07/10/2020 21
Slide 22: Closer look on the iCAROS design – Amendments to schedules in Intraday
10/7/2020 Closer look on the iCAROS design – Amendments to schedules in Intraday (reminder from the iCAROS design notes) The Scheduling Agent must inform ELIA without delay of any schedule modification of an asset for quarter-hour in the permitted periods. Unless in the cases described below, the sc
Slide 23: Schedule update in case of storm risk – Storm mitigation procedure
10/7/2020 Schedule update in case of storm risk – Storm mitigation procedure • Storm in the North Sea might trigger substantial imbalances in the Belgian control area 1. Cut-out: drop/decrease of the power production of offshore wind parks due to too high wind speed 1 2 2. Cut-in: offshore wind park
Slide 24: Schedule update in case of storm risk – Cut-in phase
10/7/2020 Schedule update in case of storm risk – Cut-in phase • Pursuant to article 252 of the Federal Grid Code, the cut-in phase of an Offshore Power Park Module following a forecasted (or ongoing) storm event must be approved by Elia, and coordinated by the Parties • As described in the T&C SA,
Slide 25: High-level proposal timeline for implementation & testing for Go-Live Phase 1 iCAROS
10/7/2020 High-level proposal timeline for implementation & testing for Go-Live Phase 1 iCAROS Date: 07/10/2020 2 5 25
Slide 26: Business Scope Outage Planning
10/7/2020 iCAROS = Integrated Coordination of Assets for Redispatching and Operational Security FOCUS Phase 1 Icaros for PGM & ESD ≥ 25 MW and no splitting of legal roles (OPA & SA = BRP) Business Scope Exchange of operational data [from LT to realtime] 1 2 3 Outage DA & ID Congestion Planning sched
Slide 27: iCAROS phased implementation
10/7/2020 → Phasing reflects operational prioritization and is cocreated with SGUs & DSOs iCAROS phased implementation → no big bang but safeguarding operational robustness 2020 2021 2022 2023 Window for TSOs to connect to EU mFRR platform (MARI) Today phase 1 phase 2 phase 3 FOCUS Phase 1 for PGM &
Slide 28: iCAROS phase 1: Interaction Scheduling Agent – Elia & Outage Planning Agent
10/7/2020 iCAROS phase 1: Interaction Scheduling Agent – Elia & Interaction Outage Planning Agent DA & ID - Elia ID Scheduling + DA scheduling 1. Outage Planning DA + Outage Planning ID Congestion Risk Indicator 2. Bidding of Redispatching Energy Bids 3. Activation of Redispatching Energy Bids 4. 28
Slide 29: AS IS situation Information flows
10/7/2020 AS IS situation Information flows Y-1 Y W-1 D-1 D LT & DA ID Ready-to- Process ID BRP Listed Revision Stand by Nomination run ‘IDPCR’ BRP status (y) BRP status (y) BRP status (d) BRP status (h) Schedules (qh) Schedules (qh) Technical data Technical data Status (d) Status (d or qh) Prices P
Slide 30: AS IS – TO BE phase 1 DA - ID Information flows
10/7/2020 AS IS – TO BE phase 1 DA - ID Information flows D-1 D D-1 D DA ID Nomination Process ID SA ‘IDPCR’ Schedules (qh) Schedules (qh) RD Energy bids RD Energy bids (qh) Schedules (qh) Schedules (qh) (qh) BRP Status (d) Status (d or qh) Prices Prices Technical data Technical data DA ID OPA Avail
Slide 31: Outage Planning Agent DA & ID
10/7/2020 Outage Planning Agent DA & ID Future process Current process – Availability Status on quarter hour – Availability Status is delivered on unit level in DA on day – level of schedule information exchange will be on Technical Unit level – Availability Status is delivered on Power Plant Future
Slide 32: DA Scheduling
10/7/2020 Under discussion DA Scheduling Future process Current process – DA Schedule – Production Program delivered on unit level in DA – level of schedule information exchange will be on Technical Unit level Current interaction Future interaction – BRP sends Schedule to Elia – Scheduling Agent sen
Slide 33: ID Scheduling
10/7/2020 ID Scheduling Under discussion Current process Future process – IntraDay Production Program Request (IDPCR) – Intraday Schedule amendment – Production Program delivered on Power Plant – Elia can send AD HOC request to return to schedule, in level in intraday (on unit level in DA) case a de
Slide 34: ID Scheduling
10/7/2020 ID Scheduling Future interaction – Message format to be confirmed – Possibly based on ENTSOe CIM: SCHEDULE DOCUMENT 34 34
Slide 35: iCAROS phase 1 timeline
10/7/2020 Mid – End May From September 2021 : Full 2021 on : demo delivery of all platform technical available for iCAROS - Phase 1 Go-Live information market parties to needed for IT test their Explicit mFRR Go-Live developments developments in market parties the framework of for phase 1 phase 1 20
Slide 36: Next steps
10/7/2020 Next steps • 26/02/’21 : iCAROS taskforce fine-tuning workshop : Presentation of final timeline to MP’s & manual ‘bidding properties' • Full delivery of Technical guides mid - end May 2021 • 03/06/’21 : iCAROS taskforce fine-tuning workshop : presentation of Technical guides • September 20
Slide 37: Feedback and follow-up
10/7/2020 Feedback and follow-up Feedback, comments and suggestions on presented initial high-level proposal for implementation & testing timeline for Go-Live Phase 1 iCAROS are kindly requested by sending it to Viviane.Illegems@elia.be by 21st October 2020. Follow-up via next iCAROS taskforce on Fe
Slide 38: Communication Layer - High Level Architecture proposal
10/7/2020 Communication Layer - High Level Architecture proposal Date: 07/10/2020 38 38
Slide 39: Communication Layer - High Level Architecture proposal
10/7/2020 Communication Layer - High Level Architecture proposal Today Tomorrow For historical reason - due to the market and technology We want to propose to our External Stakeholder a new evolution (some communications have been in place over 15 communication layer : years): A central entry poin
Slide 40: Communication Layer - Overview & needs
10/7/2020 Communication Layer - Overview & needs Asynchronous Pipeline Overview: What is still needed : Base on AMQP Protocol A default behavior when message is not respond on time have to be foreseen Queue Manager is located at Elia Side, External Stakeholders do not need to host anything any
Slide 41: Communication Layer - As Is / To Be – A short example
10/7/2020 Communication Layer - As Is / To Be – A short example * Same approach when Elia sends a message 41 41
Slide 42: Communication Layer - Conclusion
10/7/2020 Communication Layer - Conclusion Why do we propose this new communication layer ? To modernize the communication architecture between Elia and its External Stakeholders Reduce the requirements on our External Stakeholders : no need anymore to expose webservers to Elia Reduce the comm
Slide 43: Thank you.
10/7/2020 Thank you. 43