Elia Group Sa/nv · EURONEXT:ELI
Elia Group Sa/nv — Investor Presentation (June 2018)
21 slides from Elia Group Sa/nv's investor presentation, Jun 27, 2018
Slide 1: iCAROS – 1st implementation Workshop
12/20/2018 iCAROS – 1st implementation Workshop 27 June 2018 Agenda 1. Introduction 2. High level planning 3. Future Roles & Responsibilities 4. Design Outage Planning 5. Implementation Proposal Outage Planning 6. Next Steps 1
Slide 2: Introduction
12/20/2018 Introduction iCAROS design project Integrated Coordination of Assets for Redispatching and Operational Security Objective: Creation of a new Task Force iCAROS: • To develop a new EU Network Code compliant approach for the • Common platform for design discussions with a coordination of
Slide 3: Design Notes iCAROS
12/20/2018 Design Notes iCaros Design notes part I Outage Planning – II Scheduling & Redispatching proposal for assets connected to the ELIA grid (transmission and local grids) & ELIA-connected CDS Design notes part III – CRI: general link between congestion management & balancing applicable to
Slide 4: Transition planning
12/20/2018 European Guideline on electricity transmission system operation Transition planning 7 Transition planning 14/03/19 SO GL compliance Terms & Conditions iCAROS implementation 17/5 Expected Entry ~2021 ? 2018 2019 into force new ~2020 Submission Federal Grid Code FGC to FOD Current Federal G
Slide 5: Future Roles & Responsibilities
12/20/2018 2018 Goal : to have a general overview of impacted processes & tools and implementation planning at stakeholders’ & Elia side by end of November 2018 Continue with implementation meetings in 2019 for follow-up & finetuning 9 Future Roles & Responsibilities 5
Slide 6: Historical and current roles & responsibilities
12/20/2018 Historical roles & responsibilities Access Grid User Access Holder Balance Responsible Party CIPU signatory AS provision Outage plans FCR/R1 Scheduling aFRR/R2 Bidding for mFRR/R3 redispatching Non-reserved Mvar Ancillary Service flexibility for balancing Black Start Service 11 Current ro
Slide 7: Future roles & responsibilities; Changing perspective
12/20/2018 Future roles & responsibilities Balance Responsible Grid User Access Holder Balance Partysource Balance Service Balance Responsible Provider PartyBSP * FCR/R1 Reserved aFRR/R2 & non- reserved mFRR/R3 Scheduling Agent Scheduling Focus iCAROS design notes Bidding for redispatching ** + Outa
Slide 8: Design Outage Planning
12/20/2018 Design Outage Planning Purpose of outage planning Adequacy check Local Congestion Check The goal is to reduce The goal is to reduce the risk that insufficient flexibility the risks for scarcity would be available in case of congestions. throughout the year. Avoid simultaneous unavailabi
Slide 9: Outage Planning Agent Statuses
12/20/2018 Outage Planning Agent Who? the owner or a third party appointed by the owner Which assets? – Mandatory OP - Grid User (or signatory of the connection contract) is by default the OP-Agent - PGM B/C/D - The Grid User may delegate the task, but this is an operational delegation; the delegati
Slide 10: Implementation proposal Outage Planning
12/20/2018 Timeline for PGM/storage type ≥ 25MW & all cross-border relevant assets Y-1 Y 07 08 09 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 December 1st (GL SO deadline) Final availability plans * November 1st (GL SO deadline) Lighter approach for: Preliminary availability plans * - PGM/storage < 25MW Sta
Slide 11: Transfer of CIPU content to new framework
12/20/2018 Transfer of CIPU content to new framework Content transfer Contract CIPU procedures New contractual framework signatory Outage Planning Outage Planning Agent Listed Exchange of statuses & active power capability restriction (YA => RT) (Guideline System Operation art. 89) Revision Standby
Slide 12: Data exchange during new Outage Planning procedure
12/20/2018 Data exchange during new Outage Planning procedure Y-1 Y 07 08 09 10 11 12 1 2 3 4 5 6 7 8 9 10 11 12 December 1st (GL SO deadline) Final availability plans * November 1st (GL SO deadline) Lighter approach for: Preliminary availability plans * - PGM/storage < 25MW Starting from October -
Slide 13: Exchange of new statuses
12/20/2018 Exchange of new statuses Time granularity: CIPU Revision procedure Outage Planning procedure Year-Ahead => W-1 : daily W-1 => RT : quarter-hourly The asset is capable of and In service In service ready for providing service regardless Revision Available of whether it is or it is not in op
Slide 14: Platform interfaces
12/20/2018 Platform interfaces 1. Web portal that can be used by Outage Planning agent to manage his outage plans, request and receive amendment requests. And inform Elia of a fully forced unavailability or a restriction in active power capability. 2. Web services that can be used by the Outage Plan
Slide 15: Data exchanges
12/20/2018 Outage Planning Agent provides Y-1 Availability plans Motivation: Extract from DN Outage Planning pg 7 In compliance with articles 3 and 89 of the European Guideline on Transmission System Operation ELIA enters into an agreement with the Outage Planning Agent as the party responsible for
Slide 16: Ambition to base on the standard ENTSOe file format
12/20/2018 Outage Planning module Check for Provide outage planning Y-1 Availability plans incompatibilities Receive and respond <<include>> Request for amendment on request for amendment Inform Elia ASAP in case Communicate final of fully forced unavailability availability plans to OPA's Inform Eli
Slide 17: Elia can request an amendment of the availability plan
12/20/2018 Outage Planning module Check for Provide outage planning Y-1 Availability plans incompatibilities Receive and respond <<include>> Request for amendment on request for amendment Inform Elia ASAP in case Communicate final of fully forced unavailability availability plans to OPA's Inform Eli
Slide 18: Request for amendment by Elia
12/20/2018 Request for amendment by Elia Request for amendment by Elia Planning Propose alternative period for Outage Agent planned unavailability and Update the availability plan deliver a possible associated cost. Request to provide an alternative period for Elia unavailability. Refuse Accept And
Slide 19: Request for amendment by Outage Planning Agent
12/20/2018 Request for amendment by Outage Planning Agent Outage Planning Agent Propose alternative Request for amendment by Outage Planning Agent period for planned Update the availability plan unavailability. Agree Disagree Inform about the reason for refusal. And suggest to provide an alternative
Slide 20: Platform interfaces
12/20/2018 Outage Planning Agent must inform Elia ASAP in case of fully forced unavailability or a restriction in active power capability Motivation: Extract from DN Outage Planning pg. 25 The Outage Planning Agent is obliged to inform ELIA without delay of the forced full unavailability of the asse
Slide 21: Next Steps
12/20/2018 Questions • Which other functionalities, that were not presented, you believe would have an added value? • Which functionalities are preferably supported via the web service interface? • How do you assess the process flows that are proposed for amendment requests? Please provide your feed