Updates to our wholesale dispatch gate closures
Gate closures at a glance
| Outside active aFRR participation | Active aFRR participation window | |
|---|---|---|
| Gate closure | None | T-315 seconds |
| Safety buffer | 15 seconds before target execution, recommended | 15 seconds, included in the 315 |
| Changes within a delivery block | Allowed anytime | Allowed, as long as the gate closure is met |
| Setpoint valid until | End of the 15-min delivery block, by default | End of the 15-min delivery block, by default |
Outside active aFRR participation
No gate closure. Dispatch schedules can be submitted or updated anytime, and the schedule is executed immediately by EBX. EBX still recommends 15 seconds of safety buffer before target execution to guarantee execution at exactly the intended target time. Schedules submitted with an execution time in the past at the time of receipt will be rejected. Setpoints can be updated anytime, including within a delivery block. By default, EBX will consider the scheduled dispatch setpoint to be valid until the end of the 15-min delivery block.
For an active aFRR participation window
T-315 seconds. The reasoning behind this is that EBX needs to communicate a per-second anticipated operating point (outside of ancillary services) to the TSOs 5 mins in advance. This anticipated operating point is frozen and must be followed 5 mins later. EBX adds a safety buffer of 15 seconds to guarantee that the calculation and communication of the anticipated operating point (including ramp rates, partial unavailability, power limit adjustments, etc.) does not fail, and to ensure that there are no last-minute races. You are free to change the dispatch setpoint within a delivery block as well (e.g. for imbalance trading), as long as the T-315s gate closure is met. By default, EBX will consider the scheduled dispatch setpoint to be valid until the end of the 15-min delivery block.