Slide 1: Technical Guide Presentation
Technical Guide Presentation Introduction to Market Parties 30th June 2025
Slide 2: The (technical) Team
The (technical) Team Fabian Laruelle Jean-Alain Dudel Dimitri De Peutter Benjamin Ramirez Analyst Mvar Outages Analyst Mvar Implementation Application Manager Activations Coordinator Responsible for the backlog & Responsible for the backlog & Responsible for the Responsible for functionalities imple
Slide 3: Agenda
Agenda 1. Introduction (5’) 2. External Communication Layer (10’) 3. Outage Planning – What, Why & How? (10’) 4. Outage Planning – Technical guide details (20’) 5. Activations – Main features (5’) 6. Activations – Technical guide details (20’) Technical Guide Presentation 3
Slide 4: What we have now
What we have now Https://... Technical Guide Presentation 4
Slide 5: What we will build
What we will build ECL Message queing Technical Guide Presentation 5
Slide 6: Why we do this
Why we do this Technology Supporting T&C ‘27-’28 uniformization Modernization Mvar Icaros phase 1 outages/unavailabilities Changes in scope of NIS2 compliancy Non-mandatory units VSP T&C ‘27-’28 Ability to provide future Non active power proof technology related assets Icaros phase 2 Technical Guide
Slide 7: Agenda
Agenda 1. Introduction (5’) 2. External Communication Layer (5’) 3. Outage Planning – What, Why & How? (10’) 4. Outage Planning – Technical guide details (20’) 5. Activations – Main features (5’) 6. Activations – Technical guide details (20’) Technical Guide Presentation 7
Slide 8: External Communication Layer for exchanges between VSP and Elia
External Communication Layer for exchanges between VSP and Elia • The External Communication Layer will be realized by a queue manager located at Elia. No hosting required by the External Stakeholders • International standards are used for communication protocol (ENTSOe CIM) and security protocol (A
Slide 9: External Communication Layer
External Communication Layer General details: • Dedicated queues/exchanges Elia > Market Party : 1 queue for each type of message per Market Party Market Party > Elia: 1 exchange for each type of message • Sending messages Market Party has to write in the corresponding exchange Retry Logic: Sender n
Slide 10: External Communication Layer
External Communication Layer Connection details: • Authentication & Authorization Dedicated User/Password per environment Read rights only in queues Writing rights in exchanges • URLs & ports Production: messaging.elia.be Demo: messaging-demo.elia.be 5671 AMQPS 10
Slide 11: Agenda
Agenda 1. Introduction (5’) 2. External Communication Layer (10’) 3. Outage Planning – What, Why & How? (10’) 4. Outage Planning – Technical guide details (20’) 5. Activations – Main features (5’) 6. Activations – Technical guide details (20’) Technical Guide Presentation 11
Slide 12: Outage planning – What, Why & How? (1/4)
Outage planning – What, Why & How? (1/4) What is outage planning - Communication of events that reduces the services provided by a delivery point (band available, power saving mode, …) - 2 categories of events: - Unavailability events (Forced outage, Planned unavailability, Testing) - Service contro
Slide 13: Slide 12 FL0 Keeping this category to be future proof
Slide 12 FL0 Keeping this category to be future proof Laruelle Fabian; 2025-06-19T08:58:12.740
Slide 14: Outage planning – What, Why & How? (2/4)
FL0 Outage planning – What, Why & How? (2/4) Why outage planning is important - Grid stability with better forecasting - Efficiency improved in communicating unavailability events - Increased security - (Better) Fulfilling of an EU obligation (Commission Regulation (EU) 2017/1485 of 2 August 2017) -
Slide 15: Slide 13 FL0 To be further worked on, just some ideas
Slide 13 FL0 To be further worked on, just some ideas Laruelle Fabian; 2025-06-19T08:54:54.571
Slide 16: Outage planning – What, Why & How? (3/4)
Outage planning – What, Why & How? (3/4) How will it be done? (VSP side) - Using the external communication layer programmatically to submit events - Using the web client to submit events - Retrieval, cancellation of submitted events will also be possible - Visualisation of availability of delivery
Slide 17: Outage planning – Active power example
Outage planning – What, Why & How? Active power example - Using the external communication layer programmatically to submit unavailability events - Using the web client to submit unavailability events - Retrieval, cancellation of submitted events will also be possible - Visualisation of availability
Slide 18: Outage planning – Active power example
Outage planning – What, Why & How? Active power example - Using the external communication layer programmatically to submit unavailability events - Using the web client to submit unavailability events - Retrieval, cancellation of submitted events will also be possible - Visualisation of availability
Slide 19: Outage planning – What, Why & How? (4/4)
Outage planning – What, Why & How? (4/4) How will it be done? (Elia side) - No activations will be sent when an unit is unavailable (or they will be adapted to the new available band) - Settlement will not penalize units not fulfilling their obligations if declared unavailable* (*see terms & conditi
Slide 20: Agenda
Agenda 1. Introduction (5’) 2. External Communication Layer (10’) 3. Outage Planning – What, Why & How? (10’) 4. Outage Planning – Technical guide details (20’) 5. Activations – Main features (5’) 6. Activations – Technical guide details (20’) Technical Guide Presentation 18
Slide 21: Agenda – Outage Planning
Agenda Outage Planning – Technical guide details (20’) - Event submission (15’) - Data retrievals (5’) - Availability plan overview - Availability plan details - Event retrieval Technical Guide Presentation 19
Slide 22: Technical guide details (1/14) Event submission
Outage planning – Technical guide details (1/14) Event submission - Using the External communication layer (ECL) - Using the Web client (that utilizes the ECL in the back-end) - Back-ups: Each method for the other, phone or email. Technical Guide Presentation 20
Slide 23: Technical guide details (2/14) Event submission – Which events?
Outage planning – Technical guide details (2/14) Event submission – Which events ? - Unavailability event : If band deviation from the contractual values. - Submission of new available band with a new Qmin & Qmax - In case of no control available: Qmin=Qmax (can be equal to 0) - Service control even
Slide 24: Technical guide details (3/14) Event submission – ECL queues
Outage planning – Technical guide details (3/14) Event submission – ECL queues Technical Guide Presentation 22
Slide 25: Technical guide details (4/14) Update and withdrawals
Outage planning – Technical guide details (4/14) Event submission – Update and withdrawals - Same message format as for new events - Updates: Same mrid with higher version number - Withdrawals: Same market document without an available period and with a docstatus set to withdrawn (A13). Technical Gu
Slide 26: Technical guide details (5/14) Unavailability event
Outage planning – Technical guide details (5/14) Event submission – Unavailability event Technical Guide Presentation 24
Slide 27: Technical guide details (6/14) Unavailability event
Outage planning – Technical guide details (6/14) Event submission – Unavailability event Technical Guide Presentation 25
Slide 28: Technical guide details (7/14) Unavailability event
Outage planning – Technical guide details (7/14) Event submission – Unavailability event Technical Guide Presentation 26
Slide 29: Technical guide details (8/14) Service control type event
Outage planning – Technical guide details (8/14) Event submission –Service control type event - Power saving mode: - Future proof type of message - End date is not mandatory - Specific message for exiting power saving mode - Every type of event that does not impact the available band - Manual/Automa
Slide 30: Technical guide details (9/14) Service control type event
Outage planning – Technical guide details (9/14) Event submission –Service control type event Technical Guide Presentation 28
Slide 31: Technical guide details (10/14) What data can be retrieved?
Outage planning – Technical guide details (10/14) What data can be retrieved? – Availability plan overview: A global overview of the availabilities of a given delivery point. - Very Similar to the event submission – Availability plan details: All the market documents submitted for a specific day. -
Slide 32: Technical guide details (11/14) Availability plan overview retrieval
Outage planning – Technical guide details (11/14) Availability plan overview retrieval - 1 availability plan message per delivery point but multiple DP can be requested at once - Max 1 year can be requested per message - Requests, answer and plans retrieved have their own queues - Very similar messa
Slide 33: Technical guide details (12/14) Availability plan overview retrieval
Outage planning – Technical guide details (12/14) Availability plan overview retrieval - 1 availability plan message per delivery point but multiple DP - can be requested at once - Max 1 year can be requested per message - Requests, answer and plans retrieved have their own queues - Very similar mes
Slide 34: Technical guide details (13/14) Availability plan details retrieval
Outage planning – Technical guide details (13/14) Availability plan details retrieval - Can be requested 1 day of all events by market parties - Will be answered with acknowledgement and all latest versions of previously submitted events - Specific queues for availability plan details requested, ans
Slide 35: Technical guide details (14/14) Event retrievals
Outage planning – Technical guide details (14/14) Event retrievals – Event submitted can be requested by Market Parties – MRIDs for the document needs to be provided – Latest market document will be returned – As for active power, no “broad” retrieval (availability plans details need to be used for
Slide 36: Agenda
Agenda 1. Introduction (5’) 2. External Communication Layer (10’) 3. Outage Planning – What, Why & How? (10’) 4. Outage Planning – Technical guide details (20’) 5. Activations – Main features (5’) 6. Activations – Technical guide details (20’) Technical Guide Presentation 34
Slide 37: Activation – Main features
Activation – Main features Mvar activation is used to request absorption or production of Mvar in order to solve Voltages issues – Use of the ECL (External communication Layer) – Use of Json format o Concatenation of message per DP / VSP o New Fields (rampingStartTime, business Type, process.process
Slide 38: Activation (1/5) Activation – ECL queues
Activation – Technical guide details (1/5) Activation – ECL queues Technical Guide Presentation 36
Slide 39: Activation (2/5) Granularity and Timeframe
Activation – Technical guide details (2/5) Granularity and Timeframe – Concatenation of message per DP / VSP – Specifique Start time for the ramping of the unit Technical Guide Presentation 37
Slide 40: Activation (3/5) Activation_MarketDocument
Activation – Technical guide details (3/5) Activation – Activation_MarketDocument Technical Guide Presentation 38
Slide 41: Activation (4/5) Activation – Json
Activation – Technical guide details (4/5) Activation – Json rampingStartTime: The start of the ramping of the DP businessType: Identifies the reason why an activation is requested. XX = Normal XX = Start-Up process.processType: Identifies the reason why an activation is requested. Code for type of
Slide 42: Activation (5/5) Activation – Communication Test
Activation – Technical guide details (5/5) Activation – Communication Test The goal of the test is to test the communication between Elia and voltage service provider. Therefore, the communication test will go through the same communication layers as an activation. A communication test has an activa
Slide 43: Thank you.
Gaia group Thank you. < gee ge tthe