ROSC of Baltic CCR
All TSOs’ of Baltic Capacity Calculation Region
common provisions for regional operational
security coordination in accordance with
Articles 76 and 77 of the Commission
Regulation (EU) 2017/1485 of 2 August 2017
19 August 2020
ROSC of Baltic CCR
Table of contents
1. Introduction .................................................................................................................... 3
1.1 Definitions and abbreviations ......................................................................... 4
2. General provisions for regional operational security coordination process .................... 6
3. Definition of input data for coordinated operational security analysis processes ........... 7
3.1 Contingency list .............................................................................................. 7
3.2 Assessed Elements, XNEs and operational security limits ............................ 7
3.3 Remedial actions............................................................................................ 8
3.4 Individual and common grid model provisions................................................ 9
4. Provisions for regional security coordinator ................................................................... 9
4.1 Data consistency evaluation........................................................................... 9
4.2 CROSA within Baltic CCR ............................................................................ 10
4.3 RAs monitoring............................................................................................. 10
5. RAs preparation, coordination and activation provisions ............................................. 11
5.1 Identification of XRAs ................................................................................... 11
5.2 Exchanging the information of the available RAs inside CCR ...................... 11
5.3 Exchanging the information of the available RAs cross-CCR....................... 11
5.4 Identification of the most effective and economically efficient RAs .............. 12
5.5 Coordination of RAs ..................................................................................... 12
5.6 Activation of RAs .......................................................................................... 13
5.7 Sharing of the costs of RAs .......................................................................... 14
6. Day-ahead CROSA ..................................................................................................... 14
7. Intraday CROSA .......................................................................................................... 15
8. Organisation of ROSC ................................................................................................. 16
8.1 Governance and operation of regional security coordinator ......................... 16
8.2 Regional Security coordinator governing area ............................................. 16
9. Appointment of RSC and delegation of tasks to RSC .................................................. 17
9.1 Cooperation and coordination ...................................................................... 17
10. Implementation timescale ...................................................................................... 18
11. Language .............................................................................................................. 18
Annex 1: Day-ahead and Intraday CROSA processes .................................................... 20
2
ROSC of Baltic CCR
1. Introduction
Whereas
(1) This document is a Common Provisions of Baltic Capacity Calculation Region
(hereafter referred to as Baltic CCR) for Regional Operational Security Coordination
(hereafter referred to as Baltic ROSC) in accordance with articles 76 and 77 of
Commission Regulation (EU) 2017/1485 of 2 August 2017 (hereafter referred to as
the “SO Regulation”).
(2) These Common Provisions take into account general principles and goal set in SO
Regulation as well as Commission Regulation (EC) 2015/1222 establishing a
guideline on Capacity Allocation and Congestion Management (hereafter referred to
as the “CACM Regulation”).
(3) It is necessary to standardise operational security analysis at least per synchronous
area according to Article 75(1) of the SO Regulation respectively within CCR
according to Article 76(1) of the SO Regulation. General standardisation principles
defined in a common methodology for coordinated operational security analysis
(hereafter referred to as – CSAM) according to article 75 of the SO Regulation which
shall be considered as legal basis for these Common Provisions.
(4) These Common Provisions consider and where necessary complement the CSAM
and where necessary, the methodologies developed in accordance with article 35 of
the CACM Regulation (hereafter referred to as “CRC Methodology”) and article 74 of
the CACM Regulation (hereafter referred to as “CRCCS Methodology”).
(5) Articles 76 and 77 of the SO Regulation constitute the legal basis for these Common
Provisions and define several requirements that it should include at least:
a) conditions and frequency of intraday coordination of operational security
analysis and updates to the common grid model by the RSC;
b) the methodology for the preparation of Remedial actions (hereafter referred to
as - RAs) managed in a coordinated way, considering their cross-border
relevance as determined in accordance with article 35 of CACM, taking into
account the requirements in articles 20 to 23 of the SO Regulation and
determining at least:
i. the procedure for exchanging the information of the available RAs
between relevant TSOs and the RSC;
ii. the classification of constraints and the RAs in accordance with article
22 of the SO Regulation;
iii. the identification of the most effective and economically efficient RAs in
case of operational security violations referred to in article 22 of the SO
Regulation;
iv. the preparation and activation of RAs in accordance with article 23(2)
of the SO Regulation;
v. the sharing of the costs of RAs referred to in article 22 of the SO
Regulation, complementing, where necessary, the common
methodology developed in accordance with article 74 of the CACM
Regulation.
3
ROSC of Baltic CCR
(6) In conclusion, these Common Provisions document shall contribute to the general
objectives of the SO Regulation to the benefit of all TSOs, regulatory authorities and
market participants.
(7) Common Provisions of Baltic ROSC may be amended and specified in the future
considering the upcoming requirements from Regulation (EU) 2019/943 of the
European Parliament and of the Council of 5 June 2019 on the internal market for
electricity.
1.1 Definitions and abbreviations
For the purposes of the Common Provisions of Baltic ROSC, the terms used in this
document shall have the meaning of the definitions included in article 3 of the SO Regulation,
article 2 of the CACM Regulation, article 2 of the Regulation 543/2013, article 2 of CSAM
and the other items of legislation referenced therein. In addition, the following definitions
shall apply:
Available remedial action - is a remedial action which is available to solve constraints. It
includes the needed technical and cost information.
Baltic TSOs - the transmission system operators for electricity of the Republic of Estonia,
the Republic of Latvia and the Republic of Lithuania.
Baltic RSC – Baltic regional security coordinator, which provides service for three Baltic
TSOs in the following countries: the Republic of Estonia, the Republic of Latvia and the
Republic of Lithuania. Baltic RSC area of operation also includes cross-borders between
EE-FI, EE-LV, LV-LT, LT-SE and LT-PL.
Baltic RSC Agreement – Means Baltic regional security coordinator agreement signed by
Elering, AST and Litgrid on 31 October 2016.
TSOs of Baltic CCR - the transmission system operators for electricity of the Republic of
Estonia, the Republic of Finland, the Republic of Latvia, the Republic of Lithuania, the
Republic of Poland and Sweden.
Baltic CCM – means Capacity calculation methodology within the Baltic Capacity
Calculation region in accordance with article 20(2) of the Commission Regulation (EU)
2015/1222.
CRCCS Methodology - means the “Baltic CCR TSOs common methodology for
redispatching and countertrading cost sharing in accordance with article 74 of the CACM
Regulation.
Baltic CGM - Common grid model consisting of Baltic TSOs’ individual grid models and grid
model data from adjacent third countries’ TSOs operating in the same synchronous area.
Identified Constraint - is a couple of elements composed by one (or more) assessed
elements and the contingency leading to a violation of an operational security limit or a
function of this operational security limit.
4
ROSC of Baltic CCR
Assessed Element - is a network element for which the electrical state is evaluated in the
regional or cross-regional process and which value is expected to fulfil regional rules
function of the operational security limits. Assessed Elements list shall consist of Secured
Elements and Scanned Elements.
Secured Element - is an Assessed Element on which operational security limit violations
shall be identified and relieved in a coordinated way.
Scanned Element - is an Assessed Element on which operational security limit violations
shall be monitored.
Coordinated operational security analysis (COSA) - means an operational security
analysis performed by each TSO on a common grid model, in accordance with Article 72(2)
- 72(4) of the SO Regulation.
Coordinated regional operational security assessment (CROSA) - means an
operational security analysis performed by RSC on a common grid model, in accordance
with Article 78 of the SO Regulation.
Quantitative approach – a mathematical computation method for determining a cross-
border relevance of remedial action, defined in accordance with articles 15(4) and 15(5) of
CSAM.
Qualitative approach - an empirically based method for determining a cross-border
relevance of remedial action.
Abbreviations
CGM – common grid model;
IGM – individual grid model;
ROSC – regional operational security coordination;
RA – remedial action;
XRA – cross-border relevant remedial action;
RSC – regional security coordinator;
NRA – national regulatory authority;
RT – reference time;
DA – day-ahead;
ID – intraday;
CNE – critical network element;
5
ROSC of Baltic CCR
HVDC – high-voltage direct current;
XNE - cross-border relevant network element;
OPDE – operational planning data environment;
2. General provisions for regional operational security coordination
process
1. All TSOs of Baltic CCR and Baltic RSC shall manage operational security limits
violations and RAs that are deemed internal and cross-border relevant within Baltic
CCR, in a coordinated way with the affected TSOs for day-ahead and intraday
CROSA processes.
2. All TSOs of the Baltic CCR and Baltic RSC shall perform regional operational security
coordination in day-ahead and intraday timeframes for Baltic CCR in accordance with
the provisions of this document.
3. Coordinated operational security analysis (hereafter referred to as COSA) process
shall be performed by each TSO for the DA and ID timeframe processes. COSA
requires the TSO to perform contingency analysis on year-ahead, DA and ID CGMs
to ensure that any contingency does not create situation where operational security
limits are exceeded in its control area.
4. Coordinated regional operational security assessment (hereafter referred to as
CROSA) shall be performed by Baltic RSC in coordination with TSOs for the DA and
ID timeframe processes. CROSA requires the Baltic RSC to perform regional
operational security assessment at least to all TSOs of the capacity calculation
region. If a constraint is detected, it shall recommend to the relevant TSO the most
effective and economically efficient remedial action (hereinafter – RA). Baltic RSC
also coordinates the preparation of RAs with and among TSOs to enable coordinated
activation of RAs in real-time by TSOs and cross-border relevant remedial actions
(XRAs) with other RSCs.
5. Prior to the start of the ROSC process for IGM preparation purposes, each TSO shall
have the right to perform a local preliminary assessment in order to detect any
violations of operational security limits on internal grid elements. Each TSO may
choose whether or not to relieve violations of operational security limits on internal
network elements using non-cross-border relevant remedial actions.
6. When preparing IGMs, each TSO shall include any non-cross-border relevant
remedial actions resulting from the local preliminary assessment.
7. Each Baltic TSO shall inform all TSOs of Baltic CCR and Baltic RSC about any RA
inclusion in its IGM.
8. Baltic RSC shall perform CROSA on the basis of the CGM, the contingency list and
the operational security limits provided by TSOs. It shall deliver the results of the
CROSA at least to all TSOs of Baltic CCR. When it detects a constraint, it shall
recommend to the relevant TSOs the most effective and economically efficient RAs
and may also recommend RAs other than those provided by the TSOs.
6
ROSC of Baltic CCR
9. All TSOs shall ensure that the principles of cost-sharing of XRAs determined in
accordance with Baltic CRCCS Methodology are treated in a consistent way. In
addition to this, the additional cost sharing principles are determined in Article 5.7 of
these Common Provisions.
3. Definition of input data for coordinated operational security
analysis processes
3.1 Contingency list
1. Each TSO of Baltic CCR shall establish the list of contingencies to be analysed in DA
and ID security analysis processes in accordance with article 33 of the SO
Regulation.
2. Each TSO of Baltic CCR shall provide contingency list to Baltic RSC which shall be
used for DA and ID security analysis processes.
3. If necessary, each TSO of Baltic CCR shall update its contingency list and provide
updated contingency list to Baltic RSC.
4. Baltic RSC shall create a common contingency list to be used during CROSA
processes based on the latest individual list provided by each TSO of Baltic CCR for
DA and ID security analysis processes.
5. Baltic RSC shall make consistency check of provided Contingency list in accordance
to article 4.1.
6. In case if data is inconsistent and there is sufficient time until further CROSA process
steps, Baltic RSC shall inform relevant TSO. TSO shall send corrected contingency
list. In case if data is inconsistent and there is insufficient time until further CROSA
process steps, Baltic RSC shall use the latest available contingency list.
7. Baltic RSC shall use the latest available common contingency list in DA and ID
CROSA processes in Baltic CCR.
3.2 Assessed Elements, XNEs and operational security limits
1. Each TSO of Baltic CCR shall define the list of Assessed Elements which are relevant
for CROSA in Baltic CCR, considering its observability area and operational security
limits in accordance with article 25 of the SO Regulation. Each TSO shall not include
any reliability margin to operational security limits. Assessed Elements list shall
consist of Secured Elements and Scanned Elements.
2. Secured Elements shall be all critical network elements (hereafter referred to as
CNEs) and all network elements which voltage level is equal or above 330 kV and all
HVDC systems.
3. Each TSO of Baltic CCR, which is a part of more than one CCR, shall have the right
to exclude any element from the Secured Elements list which is subject to CROSA
within other CCR.
4. The cross-border relevant network elements of Baltic CCR (hereafter referred to as
XNEs) are Secured Elements defined in accordance with paragraph 2 of this article.
7
ROSC of Baltic CCR
5. Each TSO of Baltic CCR shall have the right to exclude any element from Secured
Elements list of their own control area, except CNEs, if all TSOs of Baltic CCR agree.
6. Each TSO of Baltic CCR may define Scanned Elements which shall be part of
CROSA process.
7. Scanned Elements can be any element with a voltage level lower than 330 kV which
is modelled in the IGM and any element excluded from the Secured Elements list.
8. Each TSO of Baltic CCR shall provide Assessed Elements list to Baltic RSC which
shall be used for DA and ID security analysis processes.
9. If necessary, each TSO of Baltic CCR shall update its Assessed Elements list and
provide updated Assessed Elements list to Baltic RSC.
10. Baltic RSC shall create a common Assessed Elements list to be used during CROSA
processes based on the latest individual list provided by each TSO of Baltic CCR and
share the common list with TSOs of Baltic CCR.
11. Baltic RSC shall make consistency check of provided Assessed Elements list in
accordance to article 4.1.
12. In case if data is inconsistent and there is sufficient time until further CROSA process
steps, Baltic RSC shall inform relevant TSO. TSO shall send corrected Assessed
Elements list. In case if data is inconsistent and there is insufficient time until further
CROSA process steps, Baltic RSC shall use latest available Assessed Elements list.
13. Baltic RSC shall use the latest available Assessed Elements list in DA and ID CROSA
processes in Baltic CCR.
3.3 Remedial actions
1. Each TSO of Baltic CCR shall design RAs in accordance with article 14 of CSAM.
2. When preparing RAs, each TSO of Baltic CCR shall consider RAs defined in
accordance with article 22 of the SO Regulation.
3. All TSOs of Baltic CCR, in coordination with Baltic RSC, shall identify whether a RAs
prepared in accordance with paragraph 1 of this Article are cross-border relevant
using the rules described in Article 5.1.
4. Provided RA data shall at least contain this information:
a. RA availability timeframe;
b. Expected cost;
c. Activation time;
d. Any additional information which is relevant for RA application.
5. When preparing RAs, each TSO of Baltic CCR shall consider restrictions which may
limit the usage of RAs. At least following types of restrictions shall be considered:
a. Technical limitations such as ramping restrictions, min/max output power,
min/max redispatch or power change through HVDC systems;
b. Operational restrictions and usage rules such as switching limitations,
available range of taps, dependencies between topology measures;
c. Procedural restrictions resulting from timing issues due to local or regional
processes.
8
ROSC of Baltic CCR
6. Baltic CCR TSOs shall provide the information on possible restrictions identified in
accordance with article 3.3.5(a)-(c) to the Baltic RSC together with the list of available
RAs.
3.4 Individual and common grid model provisions
1. All TSOs of Baltic CCR shall prepare Individual Grid Model (hereafter referred to as
IGM) which should be used in security analysis processes. IGMs shall be provided to
the operational data planning environment (hereafter referred to as – OPDE)
according to article 70(2) of the SO Regulation.
2. OPDE shall be used for IGM and CGM data exchange between TSOs and Baltic
RSC.
3. All TSOs of Baltic CCR shall have the right to perform a local preliminary assessment
and choose whether to relieve operational security limit violations in its IGM.
4. All TSOs of Baltic CCR may include in its IGM any non-cross-border relevant
preventive RAs, obtained during local preliminary assessment.
5. All TSOs of Baltic CCR shall include in its IGM preventive RAs, which were agreed
and coordinated during the previous CROSA processes.
6. Baltic TSOs of Baltic CCR shall inform Baltic RSC about any included RAs in their
IGMs.
7. Baltic RSC shall have the right to download those IGMs which are necessary for
Baltic CGM creation.
8. Baltic RSC shall merge IGMs of Baltic TSOs into Baltic CGM including relevant parts
of grid models of same synchronous area if necessary.
9. IGMs and CGM (Baltic CGM) shall be prepared according to common grid model
methodology developed in accordance with article 70(1) of the SO Regulation.
4. Provisions for regional security coordinator
4.1 Data consistency evaluation
1. Baltic RSC shall monitor consistency and correctness of input data provided by each
TSO of Baltic CCR which is defined in article 3 of these Common Provisions
considering at least:
a. Files format correctness;
b. Data consistency within IGM and CGM;
c. Data consistency within previous CROSA processes and timeframes;
2. Baltic RSC shall check the consistency between included RAs in the IGM by each
Baltic TSO and information shared in accordance with articles 2.7 and 3.4.5. In case
of inconsistency Baltic RSC shall inform relevant TSO about this fact and obtain
explanation from the TSO with corrected data.
3. If Baltic RSC identify issues or incorrect information in provided input data, then Baltic
RSC shall inform relevant TSOs and request the data correction and updates.
9
ROSC of Baltic CCR
4.2 CROSA within Baltic CCR
1. CROSA shall be performed for DA timeframe in accordance with article 6 and for ID
timeframe in accordance with article 7.
2. Baltic RSC shall perform CROSA based on Baltic CGM created in accordance with
article 3.4.
3. All TSOs of Baltic CCR shall exchange with relevant TSOs and Baltic RSC the
information on available RAs for DA and ID CROSA processes which can be used in
Baltic CCR.
4. Baltic RSC shall gather all the data needed to perform the CROSA, including:
a. common list of contingencies, in accordance with article 3.1;
b. common list of Assessed Elements, in accordance with article 3.2;
c. list of available RAs in accordance with articles 3.3 and 5.3 with determined
their cross-border relevance in accordance with Article 5.2.
5. Baltic RSC shall assess the completeness and consistency of each input data file
provided by each TSO of Baltic CCR in accordance with article 4.1. In case of any
inconsistency in the delivered files, the Baltic RSC shall report this fact to the relevant
TSO and request their data correction and updating.
6. When performing CROSA, Baltic RSC shall:
a. perform operational security analysis (which covers power flow and
contingency analysis) and identify operational security violations for DA and
ID planning processes in N-situation and in (N-1) situation;
b. provide operational security analysis results to all TSOs of Baltic CCR;
c. recommend to the relevant TSOs RAs which would relieve operational security
violations on Secured elements identified during CROSA in accordance with
article 5.4;
d. coordinate the TSOs acceptance of proposed RAs and share the information
about the agreed RAs between with all TSOs of Baltic CCR.
7. Baltic RSC shall perform the CROSA in accordance with article 30 of CSAM, taking
into account the following conditions:
a. Baltic RSC shall exchange the results of the CROSA process with relevant
RSCs of adjacent CCRs for cross-regional coordination.
b. Baltic RSC shall coordinate with RSCs of adjacent CCRs the operational
security violations on the overlapping XNEs in accordance with article 27 of
CSAM and its amendment.
8. Baltic RSC shall inform all affected TSOs about the results of such cross-regional
coordination.
4.3 RAs monitoring
1. Baltic RSC during CROSA processes shall check the correct inclusion of the agreed
RAs in TSOs IGMs for relevant timeframes.
10
ROSC of Baltic CCR
2. If Baltic RSC identifies that previously agreed RA has not been included in the IGM
by a TSO, Baltic RSC shall contact the relevant TSO. Informed TSO shall fix the
issues and provide updated IGM for further CROSA process steps.
5. RAs preparation, coordination and activation provisions
5.1 Identification of XRAs
1. All TSOs of Baltic CCR shall qualitatively identify the cross-border relevance of each
RA in accordance with articles 14 and 15 of CSAM. In case of a disagreement of the
results, the TSOs and Baltic RSC shall apply a quantitative approach in accordance
with article 15(4) and article 15(5) of CSAM.
2. In case of using quantitative approach, the assessment shall be done at least on the
XNEC elements in accordance with article 15(4) of CSAM.
3. In case of using quantitative approach, all RAs shall be considered as cross-border
relevant which influence factor for at least one element defined in accordance with
paragraph 2 is greater than 5%.
4. TSOs of Baltic CCR may delegate the task of performing calculations of RA influence
factors in case of quantitative approach to Baltic RSC.
5. All RAs that are not identified as cross-border relevant shall be deemed as non-cross-
border relevant.
5.2 Exchanging the information of the available RAs inside CCR
1. All TSOs of Baltic CCR shall provide the list of available RAs to concerned TSOs and
Baltic RSC for the purpose of DA and ID CROSA processes in Baltic CCR. The list
of available RAs shall be updated depending on TSOs’ needs. TSO shall inform other
TSOs and Baltic RSC about any updates of this list.
2. When providing to Baltic RSC the list of RAs, each TSO shall also consider and
provide already agreed RAs from previous coordinated regional operational security
assessments of the same MTU, except if:
a. an unforeseen event has made a RA unavailable, or
b. the RA has become technically unavailable, or
c. a new more effective and efficient RA has become available.
3. If RA from previous CROSA process is no longer available, TSO shall provide reason
to Baltic RSC, why RA is not available for CROSA process.
5.3 Exchanging the information of the available RAs cross-CCR
1. Baltic RSC shall coordinate with RSCs of adjacent CCRs during the CROSA process,
any usage of RA which has the impact across CCR(s) (hereafter referred to as cross-
CCR overlapping XRA).
2. Baltic RSC shall exchange all relevant results of the CROSA process within Baltic
CCR and with RSCs of adjacent CCRs in order to coordinate cross-CCR overlapping
XRAs between Baltic CCR and adjacent CCRs.
3. TSOs in coordination with RSCs shall relieve congestions on overlapping XNEs and
shall coordinate cross-CCR overlapping XRAs impacting these overlapping XNEs in
11
ROSC of Baltic CCR
accordance with the proposal for amendment to be developed in accordance with
article 27(3) of CSAM.
4. Baltic RSC shall inform all TSOs about the results of the coordination with RSCs of
adjacent CCRs on respective cross-CCR overlapping XRAs.
5.4 Identification of the most effective and economically efficient RAs
1. In DA and ID CROSA processes, Baltic RSC shall make the recommendation for the
implementation of the most effective and economically efficient RAs to the concerned
TSOs.
2. If necessary, Baltic RSC shall assess in coordination with the concerned TSOs and
RSCs of adjacent CCRs the effectiveness and economic efficiency of RA prior to the
implementation in a DA and ID CROSA processes.
3. When the Baltic RSC recommends RAs, it shall primarily recommend non-costly RAs.
If there are no non-costly RAs which relieve operational security limit violations or
their efficiency is insufficient, then Baltic RSC shall recommend also costly RAs.
5.5 Coordination of RAs
1. TSOs and Baltic RSC shall relieve congestions on Secured Elements and shall
coordinate XRAs impacting these Secured Elements in accordance with the proposal
for amendment to be developed in accordance with article 27(3) of CSAM.
2. In case of a detected violation of operational security limits, Baltic RSC shall
recommend to the concerned TSO an appropriate RA from the available RAs
provided by the TSOs. Baltic RSC may also recommend RAs other than those
provided by the TSOs. Such kind of recommendation for RA shall be justified by Baltic
RSC and validated by the concerned TSO.
3. When recommending RA in accordance with paragraph 2 of this article, Baltic RSC
shall take into account possible restrictions identified in accordance with article 3.3.6
which may limit its usage.
4. RAs identified for relieving operational security limit violations in accordance with
paragraph 3 of this article:
a. shall not lead to additional violations of operational security limits on Scanned
Elements;
b. should not worsen existing operational security limit violations on Scanned
Elements.
5. Each TSO shall assess whether the recommended RAs meet the following
conditions:
a. the RA is considered available for the specific market time unit in a consistent
manner from the time frame of its decision in the coordination process up to
all the subsequent timeframes of security analyses including the real time;
b. the RA should relieve violations on the Secured Elements;
c. the RA is not setting the affected TSO’s grid in an alert or emergency state
based on the CGM used in the coordination process;
12
ROSC of Baltic CCR
d. the RA is not leading to any violations of operational security limits on
Assessed Elements after the simulation of the corresponding contingency
based on the CGM used in the coordination process;
e. the RA is considered the most effective and economically efficient RA to
relieve the congestion.
6. When the concerned TSO accepts the proposed RA, this RA shall be deemed agreed
and included in the IGM, updated by a TSO according to article 21 of CSAM.
7. When a TSO rejects the recommended RA, the TSO shall provide an explanation for
this decision to the Baltic RSC and the other affected TSOs. The concerned TSO
shall identify with the Baltic RSC and other TSOs alternative RAs to relieve the
operational security limits violations or leave the violation if there is possibility to solve
it during the next CROSA process.
5.6 Activation of RAs
1. Each TSO shall activate the RAs agreed in DA and ID CROSA processes in due time.
2. Where security violations remain unsolved at the end of each coordination process,
the concerned TSOs shall agree on the necessary RAs in real-time operation in order
to coordinate the management of these remaining violations of operational security
limits.
3. If RAs agreed during DA and ID CROSA processes and activated in relevant
timeframe turn out to be insufficient to solve all congestions in real time, affected TSO
shall activate any other available RAs in real time operations in order to maintain
operational security. Involved TSOs shall inform Baltic RSC about activated
additional RAs.
4. The following conditions for the activation of the proposed RA shall be met:
a. this RA is considered available in a consistent manner from the time frame of
its decision to all the subsequent timeframes of security analyses, up to real
time,
b. this RA is considered the most effective and economically efficient to relieve
violations of operational security limits,
c. when this RA is preventive, it shall not set the affected TSO’s grid in an alert
or emergency state based on the CGMs used for its decision,
d. when this RA is curative, it is not leading to a violation of an operational
security limit in the affected TSO’s grid after the simulation of the
corresponding contingency based on the CGMs used for its decision.
5. If an agreed RA becomes unnecessary, the concerned TSO can decline an activation
of a RA or can deactivate an already activated RA. The concerned TSO shall ensure
that declining an activation respectively the deactivation of the RA is not deemed
cross-border impacting and does not affect other TSOs. The concerned TSO shall
provide an explanation for this decision to Baltic RSC and the other TSOs.
13
ROSC of Baltic CCR
5.7 Sharing of the costs of RAs
1. The cost sharing principles for XRA agreed in the DA and ID CROSA processes and
in real-time operations shall apply to the following situations:
a. Cost sharing principles of XRAs implicated by CROSA processes on a XNE
for which the costs attributed to them shall be shared among the involved
TSOs according to “Baltic CCR TSOs common methodology for redispatching
and countertrading cost sharing in accordance with article 74 of the
Commission Regulation (EU) 2015/1222 of 24 July 2015 establishing a
guideline on capacity allocation and congestion management“.
b. In situations where XRAs are activated to relieve violations on XNE that
belongs solely to one TSO control area (i.e. not cross-border
interconnections), the costs attributed to XRAs shall be covered solely by the
XNE connecting TSO.
c. In situations where non-XRAs are activated, the costs of RAs shall be covered
by TSO in that control area where the violations of the network elements were
relieved.
6. Day-ahead CROSA
1. All TSOs of Baltic CCR in coordination with Baltic RSC shall perform DA CROSA
managing violations of operational security limits and XRAs within Baltic CCR.
2. Baltic DA CROSA shall be performed in accordance with articles 23 and 33 of CSAM.
The local aspects including data provision, coordination of results applied in Baltic
region should be followed as described in Annex 1 (Table 1) of these Common
Provisions.
3. CROSA in DA timeframe shall be performed on the basis of a best forecast approach
which shall be established in accordance with the following:
a. Each TSO shall not include any reliability margin to its operational security
limits in accordance with article 3.2.1.
b. IGMs and subsequent CGMs shall include load and intermittent generation
forecasts, market results, schedules and planned topology of the transmission
system in accordance with article 70(3) of the SO Regulation.
c. RAs shall be included in the IGMs and the subsequent CGMs in accordance
to article 3.4.5.
4. DA CROSA process steps shall be performed during T0 to T5 reference time
(hereafter referred to as RT) according to Annex 1 (table 1) and article 33(1) of CSAM.
The default values shall apply: T0=18.00 CET; T1= 19.00 CET; T2=20.00 CET;
T3=20.45 CET; T4=21.30 CET; T5= 22.00 CET. If possible, to implement, all TSOs
of Baltic CCR shall have the right amend timings between T0 to T5 during
implementation phase according to Baltic CCR peculiarities if this does not conflict
with cross-CCR coordination procedures and commonly agreed processes within
other CCRs.
5. Where violations of operational security limits remain at the end of the DA CROSA,
the concerned TSOs and Baltic RSC shall agree on the objectives and the needed
14
ROSC of Baltic CCR
steps to follow in intraday, in order to improve the management of these remaining
violations. The objectives could be such as but not limited to:
a. Third countries influence
b. Time restrictions in order to perform CROSA on time
6. Concerned TSOs of Baltic CCR and Baltic RSC shall organise a teleconference in
order to validate outcomes of DA CROSA process.
7. Intraday CROSA
1. All TSOs of Baltic CCR in coordination with Baltic RSC shall perform ID CROSA and
coordinate XRAs within Baltic CCR.
2. Baltic ID CROSA shall be performed in accordance with the process description
introduced in Annex 1 (Table 2) of these Common Provisions, taking into account
provisions introduced in article 24 of CSAM.
3. ID CROSA process shall be performed at least three times a day. The following
reference timing for ID CROSA shall apply: 00:00, 08:00, and 16:00 CET, which will
cover at least all market time units of following eight hours horizons from the reference
time. Additional timeframes or extended horizons shall be agreed among TSOs upon
their request and technical feasibilities during implementation or operational phases.
4. ID CROSA shall be performed on the basis of a best forecast approach, where the
forecasted situation of each timestamp in the ID timeframe shall be established in
accordance with Article 6.3(a)-(c).
5. When the results of the CROSA have significantly evolved with a regional impact
compared to the previous ones, then the affected TSOs shall coordinate with the
Baltic RSC, in order to:
a. Share information about the significant changes of results, at least flows;
b. Agree on change of previously agreed RA or on new XRA which may become
required due to moving closer to or exceeding the operational security limits.
6. Baltic RSC shall ensure in ID CROSA that:
a. violations of operational security limits on XNE with contingency identified are
relieved using at least the RAs provided by TSOs. If violation is not relieved,
then Baltic RSC shall strive to find and recommend additional available RA
following the rules described in article 5.5.2.
b. each TSO affected by XRA is informed about the violations of operational
security limits to be solved by this RA.
7. When the conditions for implementation of RAs in accordance with article 5.5 are not
met, each affected TSO shall accept or reject the implementation of the proposed
RA. In case of rejection of the RA by one or several TSO(s) of Baltic CCR, the
concerned TSO(s) shall provide an explanation for the decision.
8. All TSOs of Baltic CCR shall consider the results and agreed RAs of the ID CROSA
in real-time operation. Where security violations remain unresolved at the end of each
ID CROSA, the concerned TSOs shall activate necessary actions in real-time
operation in accordance with article 5.6.3 and coordinate the management of these
remaining violations of operational security limits.
15
ROSC of Baltic CCR
8. Organisation of ROSC
8.1 Governance and operation of regional security coordinator
1. Baltic RSC shall be the service provider for the TSOs of Baltic CCR. Baltic RSC
shall perform the tasks delegated by the TSOs of Baltic CCR in accordance with
Article 9 of these Common Provisions.
2. Baltic RSC shall
c. provide to all TSOs of Baltic CCR coordination services for the secure and
efficient operation of the transmission system;
d. build consistent regional data according to Article 3 of these Common
Provisions;
e. facilitate regional operational security coordination and perform the
coordinated regional operational security assessment;
f. make recommendations to TSOs of Baltic CCR in relation to the services they
provide; and
g. support the harmonisation of operational procedures and standards
supporting TSOs of Baltic CCR to maintain security of supply.
3. Parties of the Baltic RSC Agreement shall be responsible for the operation of the
Baltic RSC office(s) and each of these party shall take all necessary measures and
allocate necessary and agreed resources enabling the office(s) to operate and
deliver the agreed coordination services in accordance with Article 9.3.
4. The overall cooperation between the TSOs of Baltic CCR shall be governed by
Baltic CCR steering committee.
5. The security of supply will remain the responsibility of each individual TSO of Baltic
CCR according to national laws and regulations. The responsibility for secure
system operation and any decision taken based on services provided by Baltic RSC
shall remain with the TSOs of Baltic CCR.
8.2 Regional Security coordinator governing area
1. Baltic RSC governing area is equal to area defined according to the decision on
Capacity Calculation Regions (CCRs) in accordance with article 15(1) of the
Commission Regulation (EU) 2015/1222 for Baltic CCR and include following TSOs
responsibility areas:
a. Estonian TSO - “Elering AS”;
b. Latvian TSO - “Augstsprieguma tikls”;
c. Lithuanian TSO - “LITGRID AB”;
2. For coordinated regional operational security processes the following Baltic CCR’s
cross-border interconnections are considered:
a. Estonia - Finland, Estonian TSO and Finnish TSO;
b. Estonia - Latvia, Estonian TSO and Latvian TSO;
c. Latvia - Lithuania, Latvian TSO and Lithuanian TSO;
d. Lithuania – Sweden, Lithuanian TSO and Swedish TSO;
e. Lithuania – Poland, Lithuanian TSO and Polish TSO.
16
ROSC of Baltic CCR
3. The responsibility for secure system operation and any decision taken based on
services from Baltic RSC shall remain with the all TSOs of Baltic CCR.
9. Appointment of RSC and delegation of tasks to RSC
1. All TSOs of Baltic CCR appoint Baltic RSC as a regional security coordinator that will
perform tasks listed in accordance with article 77(3) of the SO Regulation in the Baltic
CCR.
2. Baltic RSC will perform the tasks listed in article 77 (3) of the SO Regulation in the
Baltic CCR for all TSOs of Baltic CCR in a transparent and non-discriminatory
manner.
3. In accordance with article 77(3) of the SO Regulation all TSOs of Baltic CCR delegate
the following tasks to Baltic RSC, which should be carried out accordingly:
a. regional operational security coordination in accordance with article 78 of the
SO Regulation in order to support TSOs of Baltic CCR fulfil their obligations
for the year-ahead, DA and ID timeframes in accordance with articles 34(3),
72 and 74 of the SO Regulation;
b. building a common grid model in accordance with article 79 of the SO
Regulation and article 3.4 of these Common Provisions.
c. regional outage coordination in accordance with article 80 of the SO
Regulation, in order to support TSOs of Baltic CCR to fulfil their obligations in
accordance with articles 98 and 100 of SO Regulation;
d. regional adequacy assessment in accordance with article 81 of the SO
Regulation, in order to support TSOs of Baltic CCR fulfil their obligations in
accordance with article 107 of SO Regulation.
9.1 Cooperation and coordination
1. Baltic RSC will implement the common provision of the tasks in close consultation
and cooperation with All TSOs of Baltic CCR.
2. If Baltic RSC fails to provide service on a daily basis, all TSOs shall have the
possibility to coordinate the process by and among themselves.
3. Until Baltic region is in the same synchronous area with continental Europe, the
cooperation with adjacent RSCs operating in other regions (for example: Nordic RSC
or TSCNET) should be handled through relevant TSOs of Baltic CCR. However, all
TSOs of Baltic CCR have the right to delegate this task to Baltic RSC if the service
could be fully implementable and provided by Baltic RSC.
4. CROSA process requires the interaction among the following TSOs:
a. Estonian TSO - “Elering AS”;
b. Latvian TSO - “AS Augstsprieguma tīkls”;
c. Lithuanian TSO - “Litgrid AB”;
d. Finnish TSO - “Fingrid Oyj”;
e. Swedish TSO - “Affärsverket svenska kraftnät”;
f. Polish TSO - “Polskie Sieci Elektroenergetyczne S.A.”.
5. The process requires the interactions with the following adjacent RSCs:
17
ROSC of Baltic CCR
a. Nordic RSC - RSC responsible for the CROSA processes in Nordic Capacity
Calculation region.
b. TSCNET, CORESO - RSCs responsible for the CROSA processes in Core
Capacity Calculation region.
6. Any dispute between the RSCs and between Baltic RSC and all TSOs of Baltic CCR
arising out of or in connection with this methodology shall be settled amicably
between the TSOs of Baltic CCR. In case the dispute cannot be settled amicably
between these parties within 60 calendar days after having been notified hereof, the
dispute shall be finally settled by an arbitration process.
7. Baltic RSC with adjacent RSC(s) shall agree on a contractual framework defining the
rules for operation of RSCs and the liability between RSCs.
10. Implementation timescale
1. All TSOs of Baltic CCR and Baltic RSC shall implement Common Provisions of Baltic
ROSC without undue delay after all the following provisions are met:
a. regulatory approval and implementation of the amendments of CSAM in
accordance with article 27(3), article 21(6) and article 30 of CSAM;
b. implementation of Common Grid Model Methodology in accordance with
articles 67(1) and 70(1) of SO Regulation;
c. development, testing and implementation of the IT tools, systems and
procedures required to support the Common Provisions of Baltic ROSC;
2. The Common Provisions of Baltic ROSC shall be implemented taking into account
the provisions set out in CRC and CRCCS Methodologies.
3. In accordance with article 46(5) of CSAM, all TSOs of Baltic CCR and Baltic RSC
shall implement the requirements set forth in Common Provisions of Baltic ROSC
concerning cross-regional operational security coordination in six months after the
requirements have been implemented in accordance with paragraph 1 of this Article.
4. Until the CROSA processes will be developed and implemented in Baltic CCR and
adjacent CCRs which will allow consistent and efficient coordination on TSOs level
and on cross-regional level, the security analysis coordination shall be performed
among TSOs of Baltic CCR
5. After the Baltic TSOs control areas synchronization with continental Europe, these
Common provisions of Baltic ROSC shall be revised and amended as necessary.
11. Language
The reference language for the Common Provisions of Baltic ROSC shall be English. For
the avoidance of doubt, where TSOs need to translate the Common Provisions of Baltic
ROSC into their national language(s), in the event of inconsistencies between the English
version and any version in another language, the relevant TSOs shall, in accordance with
18
ROSC of Baltic CCR
national legislation, provide the relevant national regulatory authorities with an updated
translation of the Common Provisions of Baltic ROSC.
19
ROSC of Baltic CCR
Annex 1: Day-ahead and Intraday CROSA processes
Table 1. Day-ahead coordinated regional operational security assessment process
Time Time
Ste
From (Actor) To from until Activity for Actor Output information
p
(CET) (CET)
Assessed element list, network
Relevant 1RSC(SA) Update: security limits for Assessed Elements;
elements security limits list,
TSOs contingency list; RAs list;
contingency list, RAs list
1 T0
2RSC(CGM) Perform local preliminary assessment, provide
Baltic TSOs IGMs
IGMs
Check the consistency of IGMs. If needed,
RSC(SA), Request of correct IGMs
2 RSC (CGM) T0 T1 request for corrected IGMs
Baltic TSOs Baltic CGM
Creation of Baltic CGM
Perform a coordinated regional operational
Report on detected constrains and
3 RSC (SA) TSOs T1 T2 security assessment and share the results
propose RAs
between relevant TSOs.
T2 T3 TSOs evaluate assessment results. TSOs
4 TSOs RSC(SA) shall: Coordinated RAs, updated IGMs
• inform RSCs about acceptance of RAs;
1 RSC(SA) means RSC security analysis service
2 RSC(CGM) means RSC individual and common grid model service
20
Baltic TSOs RSC(CGM) Provide updated IGMs with agreed RAs Updated IGMs with agreed RAs
RSC(SA), Creation of Baltic CGM
5 RSC(CGM) Updated Baltic CGM
Baltic TSOs RSCs provide updated CGM.
RSC perform a coordinated cross-regional Report on detected constrains and
6 RSC(SA) TSOs T3 T4
operational security assessment propose RAs.
TSOs-> Final results coordination and consolidation
TSOs, RSC(SA) session shall be according to Article 33 of SO Report on final results, agreed RAs
7 T4 T5
RSC(SA) RSC(SA)-> Regulation. Final results should be agreed and and possible constraints.
TSOs confirmed between TSOs and RSCs.
21
Table 2. Intraday (ID) coordinated regional operational security assessment process
Time Time
From
Step To from until Activity for Actor Output information
(Actor)
(CET) (CET)
Assessed element list, network
Relevant 3RT-95 ID Update: security limits for Assessed
1 RSC(SA) elements security limits list,
TSOs Elements; contingency list; RAs list;
contingency list, RAs list
Provide: IGMs with updated Net positions
2 Baltic TSOs RSC(CGM) RT-95 ID RT-60 ID
and flows IGMs
Check the consistency of IGMs. If
3 RSC(CGM) Baltic TSOs RT-60 ID RT-55 ID Request of correct IGMs
needed, request for corrected IGMs
Provide CGM files for respective
4 RSC(CGM) RSC(SA) RT-55 ID RT-45 ID Creation of CGM
timeframes
Perform SA. Provide assessment results Report on detected constrains and
5 RSC (SA) TSOs RT-45 ID RT-20 ID
to relevant TSOs. propose RAs
Report, distribute and coordinate the
TSOs/ RSC(SA)/ Report on final results, agreed RAs
6 RT-20 ID RT-10 ID assessment results with TSOs of Baltic
RSC(SA) TSOs and possible constraints.
CCR and RSCs
3 Note: For example, RT-95 means: 95 minutes until reference time
22
Position paper by all Baltic Capacity Calculation Region
National Regulatory Authorities
of
the amended all TSOs’ of Baltic Capacity Calculation
Region common provisions for regional operational
security coordination in accordance with Articles 76 and
77 of the Commission Regulation (EU) 2017/1485
6 October 2020
I. Introduction and legal context
This document elaborates an agreement of all National Regulatory Authorities in the Baltic
capacity calculation region (hereinafter referred to as NRAs), agreed on 6 October 2020, on
all TSOs in the Baltic synchronous area’s (hereinafter referred to as TSOs) amended proposal1
for the methodology for regional operational security coordination in Baltic capacity
calculation region in accordance with Article 76 and Article 77 of the Commission Regulation
(EU) 2017/1485 of 2 August 2017 establishing guideline on electricity transmission system
operation (hereinafter referred to as “Amended ROSC proposal” and “Regulation
2017/1485”).
This agreed position paper of the NRAs shall provide evidence that a decision on the amended
ROSC proposal does not need to be adopted by the Agency for the Cooperation of Energy
Regulators (hereinafter referred to as Agency) pursuant to Article 6(8) of the Regulation
2017/1485 at this stage. This document is intended to constitute the basis on which NRAs will
each subsequently make national decisions pursuant to Regulation 2017/1485 Article 6(1) to
approve the amended ROSC proposal submitted by the TSOs. The TSOs are AS
Augstsprieguma tīkls, Elering AS, Fingrid Oyj, Litgrid AB, Polskie Sieci Elektroenergetyczne
S.A. and Svenska kraftnät.
The legal provisions relevant to the submission and approval of the amended ROSC proposal,
and this NRAs agreed opinion, are Articles 4(1), 5(1), 6(3)(b), 6(6), 6(7), 11, 76, and 77 of
Regulation 2017/1485, listed below.
Article 4(1)
This Regulation aims at:
a) determining common operational security requirements and principles;
b) determining common interconnected system operational planning principles;
c) determining common load-frequency control processes and control structures;
d) ensuring the conditions for maintaining operational security throughout the Union;
e) ensuring the conditions for maintaining a frequency quality level of all synchronous areas
throughout the Union;
f) promoting the coordination of system operation and operational planning;
g) ensuring and enhancing the transparency and reliability of information on transmission
system operation;
h) contributing to the efficient operation and development of the electricity transmission
system and electricity sector in the Union.
Article 5(1)
TSOs shall develop the terms and conditions or methodologies required by this Regulation
and submit them for approval to the competent regulatory authorities in accordance with
Article 6(2) and (3) or for approval to the entity designated by the Member State in
accordance with Article 6(4) within the respective deadlines set out in this Regulation.
Article 6(3)(b)
1
All TSOs’ of Baltic Capacity Calculation Region common provisions for regional operational security
coordination in accordance with Articles 76 and 77 of the Commission Regulation (EU) 2017/1485 of 2 August
2017, 19 August 2020
The proposals for the following terms and conditions or methodologies shall be subject to
approval by all regulatory authorities of the concerned region, on which a Member State may
provide an opinion to the concerned regulatory authority:
common provisions for each capacity calculation region for regional operational security
coordination in accordance with Article 76.
Article 6(6)
The proposal for terms and conditions or methodologies shall include a proposed timescale
for their implementation and a description of their expected impact on the objectives of this
Regulation. Proposals on terms and conditions or methodologies subject to the approval by
several or all regulatory authorities shall be submitted to the Agency at the same time that
they are submitted to regulatory authorities. Upon request by the competent regulatory
authorities, the Agency shall issue an opinion within 3 months on the proposals for terms and
conditions or methodologies.
Article 6(7)
Where the approval of the terms and conditions or methodologies requires a decision by more
than one regulatory authority, the competent regulatory authorities shall consult and closely
cooperate and coordinate with each other in order to reach an agreement. Where the Agency
issues an opinion, the competent regulatory authorities shall take that opinion into account.
Regulatory authorities shall take decisions concerning the submitted terms and conditions or
methodologies in accordance with paragraphs (2) and (3), within 6 months following the
receipt of the terms and conditions or methodologies by the regulatory authority or, where
applicable, by the last regulatory authority concerned.
Article 11
1 TSOs responsible for submitting proposals for terms and conditions or methodologies or
their amendments in accordance with this Regulation shall consult stakeholders, including
the relevant authorities of each Member State, on the draft proposals for terms and
conditions or methodologies listed in Article 6(2) and (3). The consultation shall last for a
period of not less than 1 month.
2 The proposals for terms and conditions or methodologies submitted by the TSOs at Union
level shall be published and submitted to public consultation at Union level. Proposals
submitted by the TSOs at regional level shall be submitted to public consultation at least at
regional level. Parties submitting proposals at bilateral or at multilateral level shall carry
out a public consultation at least in the Member States concerned.
3 The TSOs responsible for developing the proposal for terms and conditions or
methodologies shall duly take into account the views of stakeholders resulting from the
consultations prior to its submission for regulatory approval. In all cases, a sound
justification for including or not including the views resulting from the consultation shall
be provided together with the submission of the proposal and published in a timely manner
before, or simultaneously with the publication of the proposal for terms and conditions or
methodologies.
Article 76
1. By 3 months after the approval of the methodology for coordinating operational security
analysis in Article 75(1), all TSOs of each capacity calculation region shall jointly develop a
proposal for common provisions for regional operational security coordination, to be applied
by the regional security coordinators and the TSOs of the capacity calculation region. The
proposal shall respect the methodologies for coordinating operational security analysis
developed in accordance with Article 75(1) and complement where necessary the
methodologies developed in accordance with Articles 35 and 74 of the Commission
Regulation (EU) 2015/1222 of establishing a guideline on capacity allocation and congestion
management (hereinafter referred to asRegulation (EU) 2015/1222). The proposal shall
determine:
(a) conditions and frequency of intraday coordination of operational security analysis and
updates to the common grid model by the regional security coordinator;
(b) the methodology for the preparation of remedial actions managed in a coordinated way,
considering their cross- border relevance as determined in accordance with Article 35
of Regulation (EU) 2015/1222, taking into account the requirements in Articles 20 to
23 and determining at least:
i. the procedure for exchanging the information of the available remedial actions,
between relevant TSOs and the regional security coordinator;
ii. the classification of constraints and the remedial actions in accordance with
Article 22;
iii. the identification of the most effective and economically efficient remedial
actions in case of operational security violations referred to in Article 22;
iv. the preparation and activation of remedial actions in accordance with Article
23(2);
v. the sharing of the costs of remedial actions referred to in Article 22,
complementing where necessary the common methodology developed in
accordance with Article 74 of Regulation (EU) 2015/1222. As a general
principle, costs of non-cross-border relevant congestions shall be borne by the
TSO responsible for the given control area and costs of relieving cross-border-
relevant congestions shall be covered by TSOs responsible for the control
areas in proportion to the aggravating impact of energy exchange between
given control areas on the congested grid element.
2. In determining whether congestion have cross-border relevance, the TSOs shall take into
account the congestion that would appear in the absence of energy exchanges between control
areas.
Article 77
1. The proposal of all TSOs of a capacity calculation region for common provisions for
regional operational security coordination pursuant to Article 76(1) shall also include
common provisions concerning the organisation of regional operational security coordination,
including at least:
a) the appointment of the regional security coordinator(s) that will perform the tasks in
paragraph 3 for that capacity calculation region;
b) rules concerning the governance and operation of regional security coordinator(s),
ensuring equitable treatment of all member TSOs;
c) where the TSOs propose to appoint more than one regional security coordinator in
accordance with subparagraph (a):
i. a proposal for a coherent allocation of the tasks between the regional security
coordinators who will be active in that capacity calculation region. The
proposal shall take full account of the need to coordinate the different tasks
allocated to the regional security coordinators;
ii. an assessment demonstrating that the proposed setup of regional security
coordinators and allocation of tasks is efficient, effective and consistent with
the regional coordinated capacity calculation established pursuant to Articles
20 and 21 of Regulation (EU) 2015/1222;
iii. an effective coordination and decision making process to resolve conflicting
positions between regional security coordinators within the capacity
calculation region.
2. When developing the proposal for common provisions concerning the organisation of
regional operational security coordination in paragraph 1, the following requirements shall be
met:
a) each TSO shall be covered by at least one regional security coordinator;
b) all TSOs shall ensure that the total number of regional security coordinators across the
Union is not higher than six.
3. The TSOs of each capacity calculation region shall propose the delegation of the following
tasks in accordance with paragraph 1:
a) regional operational security coordination in accordance with Article 78 in order to
support TSOs fulfil their obligations for the year-ahead, day-ahead and intraday time-
frames in Article 34(3) and Articles 72 and 74;
b) building of common grid model in accordance with Article 79;
c) regional outage coordination in accordance with Article 80, in order to support TSOs
fulfil their obligations in Articles 98 and 100;
d) regional adequacy assessment in accordance with Article 81 in order to support TSOs
fulfil their obligations under Article 107.
4. In executing its tasks, a regional security coordinator shall take account of data covering at
least all capacity calculation regions for which it has been allocated tasks, including the
observability areas of all TSOs in those capacity calculation regions.
5. All regional security coordinators shall coordinate the execution of their tasks in order to
facilitate the fulfilment of the objectives of this Regulation. All regional security coordinators
shall ensure the harmonization of processes and, where duplication is not justified by reasons
of efficiency or by the need to ensure continuity of service, the creation of joint tools to
ensure efficient cooperation and coordination between the regional security coordinators.
II. The ROSC proposal
The methodology for regional operational security coordination in Baltic capacity calculation
region proposal was submitted to the NRAs on 20 December 2019. The NRAs sent an RfA on
16 June to the TSOs. The NRAs requested the TSOs to amend the proposal by improving the
description of the regional operational security coordination process, wording, terminology,
assessment of the expected impacts on the objectives of the methodology and the details of
the implementation plan.
The NRAs also note that the public hearing organized by the Baltic CCR TSOs was four days
shorter than the defined minimum time period of one month in line With Article 11(1) of
Regulation 2017/1485. The NRAs note that despite the time period, the deadline has been
clearly defined and communicated to the stakeholders. The NRAs agree that the missing four
days do not pose a significant barrier for the stakeholders to respond to the consultation, and
that the proposal can be processed regardless of this shortcoming related to the time period of
the consultation.
The Amended methodology for regional operational security coordination in Baltic capacity
calculation region proposal was submitted to the NRAs on 2 September 2020 together with a
separate explanatory document. The NRAs note that the amended ROSC proposal was not
submitted within 2 months after receiving the request for amendment from the NRAs, as
defined in Article 7(1) of Regulation 2017/1485. The NRAs however consider that since this
delay does not result in exceeding the maximum handling time of the approval process of 10
months counting from the submission of the first proposal and did not affect the NRAs
possibilities to properly assesses the proposal, the delay doesn´t have such a significant effect
to this process that the NRAs couldn´t take the decision. The NRAs were also informed by the
TSOs in advance of the upcoming delay, and conclude that the amended ROSC proposal can
be processed regardless of the delay in light of the reasoning above. Therefore, the NRAs
consider the delay acceptable.
The NRAs have assessed the amended ROSC proposal and note that the TSOs have amended
the proposal to describe the regional operational security coordination process in sufficient
clarity. The NRAs note that the wording and terminology has improved, and the amended
proposal includes an assessment of the expected impacts on the objectives. The
implementation plan of the amended ROSC proposal has also been clarified in line with the
request for amendment.
III. All National Regulatory Authorities position
The NRAs are of the opinion that the Amended methodology for regional operational security
coordination in Baltic capacity calculation region proposal enables the achievement of the
objectives of Article 4 of Regulation 2017/1485.
As required in Regulation 2017/1485, the NRAs have consulted, closely cooperated, and
coordinated with each other in order to reach agreement. The NRAs have therefore reached an
agreement that the Amended proposal for regional operational security coordination in the
Baltic capacity calculation region meets the requirements of Regulation 2017/1485. The
NRAs agree to make their national decisions by October 20, 2020 in order to remain within
the maximum handling time of the approval process of 10 months counting from the
submission of the first proposal, as defined in Regulation 2017/1485.
IV. Conclusions
All NRAs have assessed, consulted and closely cooperated to reach an agreement that the
Amended proposal for regional operational security coordination in Baltic capacity
calculation region proposal meets the requirements of Regulation 2017/1485 and as such can
be approved by the NRAs.
The NRAs shall, on the basis of this agreed position paper, make their national decisions by
October 20 of 2020. The Amended methodology for regional operational security
coordination in Baltic capacity calculation region proposal will be adopted upon the decision
of the last the NRA in the Baltic capacity calculation region. Following the national decisions
by all NRAs, TSOs are required to publish the Amended methodology for regional
operational security coordination in Baltic capacity calculation region proposal as approved,
according to Article 8(1) of Regulation 2017/1485. All TSOs must respect the implementation
deadlines provided in the Amended methodology for regional operational security
coordination in Baltic capacity calculation region proposal.
OTSUS
14.10.2020 nr 7-26/2020-009
Dokumendi „All TSOs’ of Baltic Capacity Calculation Region common provisions for
regional operational security coordination in accordance with Articles 76 and 77 of the
Commission Regulation (EU) 2017/1485 of 2 August 2017“ kooskõlastamine
1. Haldusmenetluse alustamine
Elektrituruseaduse (ELTS) § 93 lõike 6 punkt 1 kohaselt kontrollib Konkurentsiamet riikliku
järelevalve ülesannete täitmisel Euroopa Parlamendi ja nõukogu määruses (EÜ) nr 714/2009
ning selle alusel kehtestatud komisjoni määrustes sätestatud tingimuste täitmist.
Komisjoni määrus (EL) 2017/1485 on koostatud Euroopa Parlamendi ja nõukogu määruse (EÜ)
nr 714/2009 alusel, milles on ette nähtud mittediskrimineerivad eeskirjad, millega
reguleeritakse võrkudele juurdepääsu piiriüleses elektrikaubanduses, et oleks tagatud elektri
siseturu nõuetekohane toimimine.
Vastavalt Komisjoni määruse (EL) 2017/1485, millega kehtestatakse elektri ülekandesüsteemi
käidueeskiri, artiklitele 76 ja 77 peavad kõik Balti koordineeritud võimsusarvutuse ala (edaspidi
Balti CCR) põhivõrguettevõtjad koos välja töötama ettepaneku regionaalse talitluskindluse
analüüsi kooskõlastamise meetodi kohta, mida peavad regionaalsed talitluskindluse
koordinaatorid ja põhivõrguettevõtjad rakendama.
Vastavalt Komisjoni määruse (EL) 2017/1485 artiklile 6 peavad põhivõrguettevõtjad esitama
määrusega nõutud meetodi heakskiitmiseks riiklikele reguleerivatele asutustele.
Balti CCR hõlmab Eesti, Soome, Läti, Leedu, Poola ja Rootsi elektri ülekandesüsteemihaldurite
poolt teenindatavat ala.
Komisjoni määruse (EL) 2017/1485 artikkel 76 sätestab, et iga võimsusarvutusala kõik
põhivõrguettevõtjad peavad koos välja töötama ettepaneku piirkondliku talitluskindluse
kooskõlastamise ühiste sätete kohta, mida peavad järgima piirkondlikud talitluskindluse
koordinaatorid ja võimsusarvutuse ala põhivõrguettevõtjad. Artikkel 77 täiendab seda nõudega,
et piirkondliku talitluskindluse koordineerimise ühised sätted peavad hõlmama ka piirkondliku
talitluskindluse koordineerimise korraldamist käsitlevaid ühiseid sätteid.
2 (5)
01.09.2020 esitas Elering AS (Eesti süsteemihaldur) Konkurentsiametile taotluse dokumendi
“All TSOs’ of Baltic Capacity Calculation Region common provisions for regional operational
security coordination in accordance with Articles 76 and 77 of the Commission Regulation
(EU)
2017/1485 of 2 August 2017” parandustega versiooni kooskõlastamiseks.
2. Menetlusosalised
Kooskõlastamise taotluse esitajaks on Elering AS; registrikood 11022625; aadress: Kadaka tee
42, 12915 Tallinn; e-post:
[email protected] .
Dokument “All TSOs’ of Baltic Capacity Calculation Region common provisions for regional
operational security coordination in accordance with Articles 76 and 77 of the Commission
Regulation (EU) 2017/1485 of 2 August 2017” on koostatud koostöös Balti CCR elektri
ülekandevõrgu süsteemihalduritega.
3. Asjaolud ja menetluse käik
20.12.2019 kirjaga 1.1-11/2019/1086 esitas Elering AS Konkurentsiametile dokumendi “All
TSOs’ of Baltic Capacity Calculation Region common provisions for regional operational
security coordination in accordance with Articles 76 and 77 of the Commission Regulation
(EU) 2017/1485 of 2 August 2017” (edaspidi Taotlus).
Taotluses toodi Elering AS-i poolt esile, et Taotlus läbis ajavahemikus 08.11.2019 - 04.12.2019
avaliku konsultatsiooni ENTSO-E konsultatsiooni keskkonnas. Avaliku konsultatsiooni käigus
Elering AS poolt esitatud ettepanekule kommentaare ei tehtud.
03.06.2020 esitas Konkurentsiamet Elering AS-ile Balti CCR riikide regulaatorite ühise
seisukoha esitatud Taotlusele (“Request for amendment by all Baltic Capacity Calculation
Region National Regulatory Authorities agreed on all TSOs’ of Baltic Capacity Calculation
Region common provisions for regional operational security coordination in accordance with
Articles 76 and 77 of the Commission Regulation (EU) 2017/1485”).
Ühises seisukohas osutasid riiklikud regulaatorid puudustele Taotluses ning palusid parandada
ja täiendada dokumenti nii, et see vastaks täielikult Komisjoni määruse (EL) 2017/1485
nõuetele.
01.09.2020 kirjaga 1.1-11/2020/759 esitas Elering AS Konkurentsiametile taotluse dokumendi
“All TSOs’ of Baltic Capacity Calculation Region common provisions for regional operational
security coordination in accordance with Articles 76 and 77 of the Commission Regulation
(EU) 2017/1485 of 2 August 2017” parandustega versiooni kooskõlastamiseks. Kirjale oli
lisatud ka süsteemihaldurite ühine selgitav dokument, milles süsteemihaldurid selgitasid ja
põhjendasid kuidas regulaatorite seisukohad on parandatud Taotluses arvesse võetud.
14.09.2020 pöördus Konkurentsiamet Balti CCR regulaatorite poole küsimusega, kas kellelgi
on vastuväiteid või täiendusi esitatud dokumendile.
14.09.2020 Soome regulaator teatas, et esitab täiendused (kui on) hiljemalt 18.09.2020.
3 (5)
18.09.2020 Läti regulaator leidis, et olulisi muutusi pole vaja teha, vaid mõned kirjavead tuleks
ära parandada.
18.09.2020 Rootsi regulaator leidis, et on valmis heaks kiitma dokumendi, kuid tõi välja, et
dokumendis kasutatud arbitraaži protsess ning Komisjoni määruse (EL) 2017/1485 artikkel 6
punkt 6, mis käsitleb meetodite ettepaneku rakendamise esialgset ajakava ning kirjeldust selle
kohta, kuidas need võiksid mõjutada käesoleva määruse eesmärkide saavutamist, vajaksid
lisaselgitust.
21.09.2020 pöördus Konkurentsiamet Elering AS poole lisaselgituste saamiseks Rootsi
regulaatori poolt tõstatatud küsimuste osas.
21.09.2020 Leedu regulaator teatas, et neil ei ole täiendusi esitatud dokumendile.
22.09.2020 esitas Elering AS lisaselgitused arbitraaži protsessi ning metoodika ajakava ning
eesmärkide osas. Konkurentsiamet pidas vastust ammendavaks.
22.09.2020 Soome regulaator esitas oma seisukohad üleskerkinud küsimustele.
25.09.2020 esitas Poola regulaator oma heakskiidu dokumendile koos mõnede
tähelepanekutega.
06.10.2020 leppisid Balti CCR ala riiklikud regulaatorid kokku seisukohadokumendis „Position
paper by all Baltic Capacity Calculation Region National Regulatory Authorities of the
amended all TSOs’ of Baltic Capacity Calculation Region common provisions for regional
operational security coordination in accordance with Articles 76 and 77 of the Commission
Regulation (EU) 2017/1485” (vaata Lisa 2), milles regulaatorid leidsid, et esitatud ettepanek
piirkondliku operatiivturvalisuse kooskõlastamiseks Balti koordineeritud võimsusarvutuse alal
vastab Komisjoni määruse (EL) 2017/1485 nõuetele ja riiklikud reguleerivad asutused kiidavad
selle heaks. Riiklikud reguleerivad asutused teevad selle kokkulepitud seisukoha alusel oma
riiklikud otsused hiljemalt 20. oktoobriks 2020.
4. Konkurentsiameti seisukoht
Kõik Balti CCR-i ja Baltic RSC1 elektri ülekandevõrgu süsteemihaldurid teostavad
piirkondlikku operatiivse turvalisuse koordineerimist päev ette ja päevasisesel ajavahemikel
Balti CCR piirkonnas vastavalt käesoleva Taotluse dokumendi sätetele.
Menetluse käigus Konkurentsiamet võrdles Taotluses toodud süsteemihaldurite poolt ühiselt
kokkulepitud sätteid Komisjoni määruse (EL) 2017/1485 artiklite 76 ja 77 nõuetega ning leidis,
et Taotluses toodud sätted on kooskõlas määruse nõuetega:
1. päevasiseste piirkondlike talitluskindluse analüüside kooskõlastamise tingimused ja
sagedus ning piirkondlike talitluskindluse koordinaatorite poolt tehtava ühiste
1
Baltic RSC - Balti regiooni piirkondliku talituskindluse koordinaator, mis osutab teenust kolmele Balti
põhivõrguettevõtjale järgmistes riikides: Eesti, Läti ja Leedu. Läänemere RSC tegevuspiirkond hõlmab ka
piiriüleseid ühendusi EE-FI, EE-LV, LV-LT, LT-SE ja LT-PL.
4 (5)
võrgumudelite ajakohastamise tingimused ja ajakohastamise sagedus on Taotluses
määratletud;
2. Taotluses on toodud metoodika parandusmeetmete kooskõlastatud ettevalmistamiseks,
võttes arvesse nende piiriülest asjakohasust:
2.1. Taotluses on määratud viis, kuidas vahetada olemasolevate parandusmeetmete
kohta leiduvat teavet asjaomaste põhivõrguettevõtjate ja piirkondliku
talitluskindluse koordinaatori vahel;
2.2. Taotluses on määratud piirangute ja parandusmeetmete liigitamine kooskõlas
Komisjoni määruse (EL) 2017/1485 artikliga 22;
2.3. Taotluses on esitatud tulemusrikka ja majanduslikult tõhusa parandusmeetmete
kindlaksmääramine artiklis 22 osutatud talitluskindluse rikkumiste puhul;
2.4. Taotluses on toodud parandusmeetmete ettevalmistamine ja käivitamine kooskõlas
määruse regulatsiooniga;
2.5. Taotluses on toodud parandusmeetmete kulude jaotamine.
3. Taotluses on ära toodud ka piirkondliku talitluskindluse koordineerimise korraldamist
käsitlevaid ühiseid sätteid:
3.1. piirkondliku talitluskindluse koordinaatori nimetamine;
3.2. eeskirjad, milles käsitletakse piirkondliku talitluskindluse koordinaatori juhtimist
ja tegevust, tagades kõigi osalevate põhivõrguettevõtjate võrdse kohtlemise;
3.3. oma ülesannete täitmisel võtab piirkondliku talitluskindluse koordinaator arvesse
andmeid, mis hõlmavad kõiki selliseid koordineeritud võimsusarvutusalasid,
millega seoses on tema peale pandud ülesandeid, sealhulgas kõikide
põhivõrguettevõtjate jälgimispiirkondi sellistel koordineeritud
võimsusarvutusaladel;
3.4. Taotluse sätetega tagatakse piirkondlike talitluskindluse koordinaatorite vaheline
tõhus koostöö ja koordineerimine.
Lähtudes eeltoodust ja tuginedes Komisjoni määruse (EL) 2017/1485 artiklile 6 ning ELTS §
93 lõike 6 punktile 1 ning Balti koordineeritud võimsusarvutuse ala riiklike regulaatorite
seisukohadokumendile
otsustan:
kooskõlastada dokumendi “All TSOs’ of Baltic Capacity Calculation Region common
provisions for regional operational security coordination in accordance with Articles 76 and 77
of the Commission Regulation (EU) 2017/1485 of 2 August 2017” Lisas 1 toodud sõnastuses.
(allkirjastatud digitaalselt)
Märt Ots
peadirektor
Lisad:
„Lisa 1 – Baltic CCR common provisions for ROSC.pdf“
„Lisa 2 – Position Paper – Baltic SOGL Art 76 and 77 Approval.pdf“
5 (5)