Elia Group Sa/nv · EURONEXT:ELI

Elia Group Sa/nv — Technical Presentation (April 2019)

27 slides from Elia Group Sa/nv's technical presentation, Apr 2, 2019

  1. Slide 1: iCaros: Integrated Coordination of Assets for Redispatching and Operational Security

    iCaros : Integrated Coordination of Assets for Redispatching and Operational Security First fine-tuning workshop 2 April 2019

  2. Slide 2: Introduction to the ICAROS project

    Introduction to the ICAROS project

  3. Slide 3: Coordination of assets & Drivers for a redesign

    Coordination of assets & Drivers for a redesign The coordination of assets serves to provide Elia with the data and means necessary to:  avoid congestions on the grid  ensure the availability of ancillary services  monitor the availability of production to satisfy demand with the aim of providing

  4. Slide 4: Pragmatic approach towards implementation of iCaros design

    Pragmatic approach towards implementation of iCaros design iCAROS GO iCAROS organization & preparation iCAROS development and testing LIVE 17/5 Expected Entry ~end Q1 ~2021/20 2018 2019 into force new 22 Submission 2020 Federal Grid Code FGC to FOD 14/03/19 SO GL entry into force Current Federal Gri

  5. Slide 5: Project Timeline – High Level Delivery Plan until Go-Live

    Project Timeline – High Level Delivery Plan until Go-Live Dec Dec 2021/ 2017 2019 2022 Planning and Development iCaros platform(s) Testing of iCaros platform(s) (UAT) Go- organization : Go-Live iCaros Live translation of design Prepa- Window Design Development@ Testing of into business ration requir

  6. Slide 6: Dates fine-tuning sessions

    Dates 8 fine-tuning sessions (2hours)  First 4 sessions pure brainstorming regarding fine-tuning topics • 2/4 • 23/4 • 22/5 • 24/6  Following 4 sessions mock-ups & brainstorming regarding fine-tuning topics • 25/9 • 23/10 • 27/11 • 17/12 6

  7. Slide 7: Fine-tuning session 1

    Fine-tuning session 1 : • Scheduled data exchange DA/ID for Energy storage • Bidding of flexibility for redispatching: bid properties 7

  8. Slide 8: Summary Asset Obligations

    Summary Asset Obligations - Expansion of assets included in coordination and congestion management. Rules on operational information exchange in SO GL: LEGEND: Mandatory Mandatory connection/access contract Voluntary - Yearly contracts replaced by contracts of longer duration (lifetime or ad hoc dep

  9. Slide 9: Scheduled data exchange DA/ID for Energy storage

    Topic 1 Fine-Tuning workshop : Scheduled data exchange DA/ID for Energy storage

  10. Slide 10: DA/ID Scheduling: MW or ON/OFF schedules

    DA/ID Scheduling: MW or ON/OFF schedules  A MW schedule provides MW output per quarter-hour of day D. … 18:15 18:30 18:45 19:00 19:15 19:30 19:45 20:00 20:15 20:30 20:45 21:00 21:15 … PGM & … 49,00 49,50 50,00 51,00 51,00 51,00 51,30 51,70 51,70 51,70 51,70 50,70 50,00 … storage C/D  DA and ID sch

  11. Slide 11: Scheduled data exchange DA/ID for Energy storage

    Scheduled data exchange DA/ID for Energy storage Feedback during public consultation: why not one schedule including both the loading and discharge of the energy storage device? > Question to stakeholders: preferences? Reasons for one option (two separate schedules) or the other (one schedule)? 11

  12. Slide 12: Bidding of flexibility for redispatching: bid properties

    Topic 2 Fine-Tuning workshop : Bidding of flexibility for redispatching: bid properties

  13. Slide 13: Redispatching bidding: AS IS => TO BE

    Redispatching bidding: AS IS => TO BE AS IS TO BE Implicit bidding Explicit bidding: block bids or scheduling limits Same bid for redispatching & balancing Different bid possible for redispatching & balancing Cost-based pricing in DA Free pricing in ID Cost-based/cost-reflective pricing in ID Paid-a

  14. Slide 14: Summary – Bidding for redispatching

    Summary – Bidding for redispatching Grid User = Scheduling Agent OR Grid User FSP/BSP = Scheduling Agent Signatory of contract Scheduling & Signatory of contract Scheduling & Redispatching Bidding Redispatching Bidding with Elia with Elia Mandatory bidding of available Bidding level Remuneration fle

  15. Slide 15: Bidding level

    Bidding level National portfolios (with delivery points spread across entire Belgium) are only useful for international redispatching purposes, 1 specifically countertrading. Portfolios for national redispatching purposes can only include delivery points located in the same geographic area: all deli

  16. Slide 16: Bidding of flexibility on PGM & storage C & D (≥ 25MW)

    Bidding of flexibility on PGM & storage C & D (≥ 25MW) - Hypothesis: Continuation of current bidding obligations (Federal Grid Code, CIPU) for redispatching (taking into account whether an asset is fully coordinable, limited coordinable, or not coordinable). - Bidding on unit-level - Bidding format:

  17. Slide 17: Explicit form of bidding: Alternative 1 = Block bids

    Explicit form of bidding: Alternative 1 = Block bids Bid indicating the MW delta available for incremental and decremental redispatching actions SCHEDULING AGENT ELIA MW 1. Incremental block bid offered Bid 2. Elia matches the schedule and A redispatching activation the bids. = a new schedule comman

  18. Slide 18: Bidding of flexibility on PGM & storage B (< 25MW)

    Bidding of flexibility on PGM & storage B (< 25MW) - Bidding obligation for redispatching (taking into account whether an asset is fully coordinable, limited coordinable, or not coordinable. Remark: possible automatisation on bidding process, e.g., set default bid to avoid daily operations - Bidding

  19. Slide 19: Explicit form of bidding: Alternative 2 = Scheduling Limit bids

    Explicit form of bidding : Alternative 2 = Scheduling Limit bids Bid indicating an incremental and decremental limit for redispatching actions SCHEDULING AGENT ELIA MW 1. Scheduling limit (maximum) offered (could vary per quarter- minimum hour) Bid A redispatching activation = a new schedule command

  20. Slide 20: Bidding of flexibility on demand

    Bidding of flexibility on demand - No bidding obligation for redispatching - In case of bidding for redispatching: Bidding on the level of the demand facility (1st implementation phase: no portfolio bids) - Bidding format: • If same bid as for balancing: explicit block bids (in compliance with artic

  21. Slide 21: Price setting for congestion bid & Remuneration

    Price setting for congestion bid & Remuneration Grasping ID market opportunities + Cost-based redispatching The proposed design reduces the impact of congestions on the ID markets compared to CIPU: - No more block on schedules depending on CRI level. - When possible Elia will wait to activate flexib

  22. Slide 22: Bid properties - Possibilities

    Use properties to differentiate between - Start-up bid - Fast versus slow flexibility Bid properties - Possibilities - - Shut-down bid Incremental bid - - Energy limited bids … - Decremental bid Bid property Unit Explanation Delay 15 Min the deadline for an activation request before the start of the

  23. Slide 23: Explicit bids & full availability bidding: example start up/incremental

    Explicit bids & full availability bidding: example start up/incremental Pmax 200 150 AS reserved – UP Non-reserved incremental flexibility: to offer for redispatching Pmin 50 0 QH1 QH2 QH3 QH4 Bid Unit QH1 QH1 QH2 QH2 QH3 QH4 property start up bid incremental bid start up bid incremental bid increme

  24. Slide 24: Explicit bids & full availability bidding: example shut down/decremental

    Explicit bids & full availability bidding: example shut down/decremental Pmax 200 150 Pmin 50 Non-reserved decremental flexibility: to offer for redispatching 0 QH1 QH2 QH3 QH4 Bid Unit QH1 QH1 QH2 QH2 QH3 QH4 property decremental bid shut down bid decremental bid shut down bid shut down bid shut do

  25. Slide 25: Annex

    Annex

  26. Slide 26: For information: Thresholds for PGM A/B/C/D as specified in FTR

    For information: Thresholds for PGM A/B/C/D as specified in FTR Thresholds for PGM A/B/C/D & required derogations on NC RfG (towards implementation of RfG art. 5(3))  Derogations (categories Type D (requir.=A) and Type D (requir.=B)) only apply for connection requirements.” The same classification

  27. Slide 27: Definition Coordinable – Limited Coordinable

    Definition Coordinable – Limited Coordinable • Coordinable or “C” : Characteristic of a CIPU Technical Unit which is technically capable of modifying its power injection on the Elia Grid upon request by ELIA, within 15 minutes; • Limited Coordinable or “LC”‘ : Characteristic of a CIPU Technical Unit

Elia Group — Technical Presentation (April 2019) on 6ix