| Balancing border capacity limits | |||
|
Regulation Article |
Articles 4.3 & 4.4 of IN IF Articles 4.3 & 4.4 of aFRR IF Articles 4.3 & 4.4 of mFRR IF |
||
|
Regulation text |
|||
|
Detailed description |
The balancing border capacity limits shall be described by a time series that conveys the following information: Adjustment here refers to the difference (also called “delta”) between originally foreseen capacity limit and the updated capacity limit actually being applied. Net position limits impose a cap on the net import and/or export into/from an area, without affecting transit flows. These shall also be published. For imports the Out area corresponds to the region. For exports the In area corresponds to the region. Data is published with ISP resolution. A reason shall be published whenever a temporary limit or adjustment has been applied. The following single reason is foreseen: Operational security constraints. A free-text comment must be included to provide additional explanation and justification. Area may be scheduling area, LFC area or, in case of a technical profile, an aggregation thereof. Time series does not have to be continuous. This is the case when the submitted limit or adjustment applies only during some of the ISPs. Interconnector may be identified by its EIC code when it is necessary to distinguish between the interconnectors on a given border. This may typically be the case when there is more than one HVDC interconnector on the border. For IN and aFRR only temporary adjustments due to operational security constraints will be published. For mFRR all capacity limits, including their updates due to operational security constraints, will be published. When the border does not correspond to a bidding zone border, and the capacity limit therefore equals the technical exchange limit, only the temporary limits due to operational security will be published. |
||
|
Specification of calculation |
If adjustments for the same border or interconnector and the same time interval are received from individual TSOs and from the IN or aFRR platform, the adjustment sent by the platform shall be published. | ||
|
Primary owner of the data |
|||
|
Data provider |
IN, aFRR and mFRR platforms For IN and aFRR individual TSOs may also submit adjustments |
||
|
Aggregation |
|||
|
Publication deadline for ENTSO-E |
Adjustments and their justification shall be published as soon as the need has been identified and as soon as technically feasible but no later than 30 minutes after the end of the first market time unit in which the limit applies. The additional free text comment providing further details will be published as soon as technically and operationally feasible. |
||
|
Updates |
May be submitted in case the time interval, during which adjustments due to operational security constraints are in place, is extended or shortened. An update may also be submitted in case the limit itself has been modified. | ||
|
Comments |
The list of possible reasons may be extended in the future to align with the evolution of capacity calculation methodologies. The publication will be extended with information about TSOs requesting the limits or adjustments at a later stage, once necessary adaptations to European platforms and TSOs’ systems have been put in place. |
||
Comments
0 comments
Article is closed for comments.