← Ελλάδα

ΑΠΟΦΑΣΗ ΚΛΑΔΟΥ ΕΝΕΡΓΕΙΑΣ ΤΗΣ ΡΑΑΕΥ ΥΠ’ ΑΡΙΘΜ. Ε-56/2024

Obsah (39)Article 76Article 35Article 37Article 78Article 75Article 74Article 4Article 77Article 72Article 38Article 5Article 22Article 7Article 10Article 11Article 18Article 67Article 33Article 2Article 30Article 70Article 27Article 19Article 28Article 32Article 15Article 21Article 23Article 24Article 25Article 26Article 13Article 6Article 17Article 34Article 79Article 80Article 81Article 8

Τροποποίηση της μεθοδολογίας για το συντονισμό της περιφερειακής επιχειρησιακής ασφάλειας στην περιφέρεια υπολογισμού δυναμικότητας Νοτιοανατολικής Ευρώπης σύμφωνα με το άρθρο 76 παράγραφος 1 του Κανο

Article 76

(1)of Commission Regulation (EU) 2017/1485 of 2 August 2017 establishing a guideline on electricity transmission system operation February 2024 14 Whereas
(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)This document provides an amendment to the Methodology for regional operational security coordination for the capacity calculation region SEE pursuant to Article 76
(1)of the Regulation (EU) 2017/1485 establishing a guideline on electricity transmission system operation (hereafter referred to as the ‘SO Regulation’). This document is hereafter referred to as the ‘ROSC Methodology’. This ROSC Methodology takes into account the general principles and goals set in the 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’). This ROSC Methodology takes into account the possible dependencies with Commission Regulation (EU) 2017/2195 establishing a guideline on electricity balancing, Commission Regulation (EU) 543/2013 on submission and publication of data in electricity markets and amending Annex I to Regulation (EC) 714/2009 (hereafter referred to as the ‘Transparency Regulation’) as well as Commission Regulation (EU) 1227/2011 on wholesale energy market integrity and transparency (hereafter referred to as the ‘REMIT Regulation’). Article 76 of the SO Regulation constitutes the legal basis and defines the requirements for the ROSC Methodology. This ROSC Methodology also includes the appointment of an RSC and rules concerning the governance and operation of the RSC, according to Articles 77
(1), 77
(2)and 77
(3)of the SO Regulation.

Article 35

(2)of Regulation 2019/943 of the European Parliament and of the Council on the internal market for electricity (hereafter referred to as “Electricity Regulation”), since 1 July 2022 the RSCs have been replaced by the Regional Coordination Centers (‘RCCs’). The SEE RCC shall complement the role of TSOs by performing the tasks of regional relevance assigned to it

Article 37of Electricity Regulation. In line with Article 37

(1)(b) of the Electricity Regulation, the RCCs need to carry out the coordinated security analysis

the methodologies developed pursuant to the system operation guideline adopted on the basis of Article 18

(5)of Regulation (EC) No 714/2009. Thereby, as of 1 July 2022, the SEE RCC shall perform this ROSC Methodology for the SEE CCR. Hence, the references to ‘RSCs’ has been accordingly replaced to ‘RCCs’ in this amended ROSC Methodology. This ROSC Methodology defines an adequate frequency of intraday coordination of operational security analysis and updates to the CGM to ensure network security and stability

Article 76(1)(a) of the SO Regulation.

This ROSC Methodology contributes to the objectives stated in Article 76

(1)(b) of the SO Regulation introducing a coordination process with explicit rules for the preparation of cross- border relevant remedial actions in a coordinated way and assigns clear responsibilities for the SEE TSOs and SEE RCC. 15
(10)For the exchange of relevant information and preparation of cross-border relevant remedial actions

Article 76

(1)(b)(i) and Article 76
(1)(b)(iv) of the SO Regulation, this ROSC Methodology determines all input data relevant for regional operational security coordination.
(11)For the activation of cross-border relevant remedial actions

Article 76

(1)(b)(iv) of the SO Regulation, this ROSC Methodology defines two types of coordination processes which aim to resolve operational security violations with crossborder relevant remedial actions. The standard coordination process is called coordinated regional operational security analysis (‘CROSA’)

Article 78

of the SO Regulation that is performed at a regional level by all SEE TSOs and RCC together. In cases where the CROSA cannot be applied, TSO(

  1. s)can apply a fact activation process, which is a limited coordination performed by a TSO(
  2. s)facing operational security violation in coordination with the RCC and other TSOs, which may be affected by application of remedial actions.

(12)This ROSC Methodology defines all relevant types of constraints which are necessary to ensure the operational security

Article 76(1)(b)(ii) of the SO Regulation.

(13)To identify the most effective and economically efficient remedial actions

Article 76

(1)(b)(iii) of the SO Regulation, this ROSC Methodology introduces the remedial action optimisation (‘RAO’). The aim of this optimisation is to minimise the incurred cost as well as to ensure the remedial actions are applied effectivity to address operational security violations.
(14)

Article 76

(1)(b)(v) of the SO Regulation, this ROSC Methodology complements the cost sharing methodology for the SEE CCR established pursuant to Article 74 of the CACM Regulation. While the cost sharing methodology determines the concrete cost sharing solution, this ROSC Methodology determines all the relevant input data and parameters that are required for the application of the cost sharing methodology.
(15)As the SEE CCR is characterised by a highly meshed network, all network elements of voltage equal or higher than 150 kV and all available remedial actions are generally considered as cross- border relevant. This is because in SEE CCR it is generally not possible to identify a network element that would be impacted only by remedial actions that do not have any impact on other cross-border relevant network elements. Still, exceptions to the rule are possible if all SEE TSOs agree that individual network elements can be considered as not cross-border relevant.
(16)As all potential remedial actions are considered as cross-border relevant in SEE CCR, when it comes to coordinated regional operational security analysis, there is no need for qualitative or quantitative assessment of their cross-border relevance

CSAM. Nevertheless, after optimal cross-border remedial actions are determined by RAO, these can be further modified by subsequent coordination and fast activation process and these modifications need to be coordinated only among the TSOs which are directly affected by the concerned remedial action. For this purpose, this ROSC Methodology also 16 defines a methodology for a qualitative and quantitative assessment of TSOs that are significantly affected by cross-border relevant remedial actions.

(17)To achieve the objectives stated in Article 76
(1)of the SO Regulation, the ROSC Methodology considers and, where necessary, complements: (a) the methodology for coordinating operational security analysis

Article 75

of the SO Regulation (hereafter referred to as ‘CSAM’); (b) the common SEE methodology for coordinated redispatching and countertrading

Article 35

of the CACM Regulation; (c) the common SEE methodology for coordinated redispatching and countertrading cost sharing (hereafter referred to as ‘cost sharing methodology’)

Article 74of the CACM Regulation.

(18)In this ROSC Methodology, the CROSA, consists of a preparation step, a coordination step (containing one or more coordination runs) and a validation step. The CROSA describes the coordination between TSOs and the RCC of the SEE CCR as well as coordination of SEE TSOs and the RCC with the TSOs and RCC (s) of other CCRs.
(19)

Recital

(15)of the SO Regulation, synchronous areas do not stop at the European Union's (EU) borders and can include the territory of third countries. The TSOs should aim for secure system operation inside all synchronous areas which include EU countries. This ROSC Methodology is open to participation of third country TSOs subject to a common agreement and equal rights and responsibilities.
(20)To ensure the tools implemented to build CGMs and operated by RCC (s) will be compliant with the respective requirements set up in the relevant legislation in force, including the SO Regulation (notably Article 79
(5)of the SO Regulation), the CGMM and the CSAM, while ensuring reliability of the CGM delivery process and the aligned use of the resulting unique CGM, a consistent and harmonised approach at pan-European level is needed. This should be facilitated by ENTSO-E where all EU TSOs are involved.
(21)This ROSC Methodology contributes to the objectives of the SO Regulation as follows: (a) for the SEE CCR common operational security requirements and principles are followed with the common remedial action optimisation

Article 4

(1)(a) of the SO Regulation as well as introducing common interconnected system operational planning principles for remedial actions

Article 4

(1)(
  1. b)of the SO Regulation; (
  2. b)it ensures the conditions for maintaining the operational security throughout the Union by specifying the provisions and process for the coordination of operational security within the SEE CCR as well as with neighbouring CCR systems

Article 4

(1)(
  1. d)of the SO Regulation; (
  2. c)promoting the coordination of system operation and operational planning by using for the SEE CCR a common remedial action optimisation where the RCC together with TSOs will ensure efficient coordination

Article 4

(1)(
  1. f)of the SO Regulation; (
  2. d)ensuring transparency and reliability of information on transmission system operation, 17 and the efficient operation of the electricity transmission system in the Union by introducing common monitoring obligations and communication formats

Article 4

(1)(
  1. g)of the SO Regulation; (
  2. e)contributing to the efficient operation and development of the electricity transmission system and electricity sector in the Union making sure that the most efficient resources are used in the optimisation for relieving congestions

Article 4

(1)(h) of the SO Regulation;
(22)In conclusion, this ROSC Methodology contributes to the objectives of the SO Regulation and of the Electricity Regulation and to the benefit of all market participants and electricity end-users. TITLE 1 GENERAL PROVISIONS Article 1 Subject matter and scope 1. This ROSC Methodology is developed

Article 76

of the SO Regulation and for organisation of regional operational security coordination

Article 77of the SO Regulation.

2. This ROSC Methodology shall cover the year-ahead, day-ahead and intraday regional operational security coordination within SEE CCR. 3. This ROSC Methodology shall apply to all TSOs and the RCC within the SEE CCR. 4. This ROSC Methodology shall also apply to third country TSO(s), if such TSO(

  1. s)have signed an agreement with all SEE TSOs that they shall comply with this ROSC Methodology, as well as the SEE methodologies pursuant to Article 35 and Article 74 of the CACM Regulation and accept all the rights and obligations stemming from them. In such case the reference to SEE TSO(
  2. s)and SEE CCR in this methodology shall also include such third country TSO(s). Article 2 Definitions and concepts 1. For the purposes of this ROSC Methodology, the terms used 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 Electricity Regulation and Article 2 of the Transparency Regulation. In addition, the following acronyms and definitions shall apply: a. ‘cross-border relevant remedial action’ or ‘XRA’ means a remedial action identified as cross-border relevant and needs to be applied in a coordinated way; b. 'available XRA' means an XRA that is available for the CROSA to relieve operational 18 security violations; c. ‘recommended XRA’ is an XRA determined as optimal by RAO and/or recommended by RCC (
  3. s)to TSOs; d. ‘agreed XRA’ means an XRA which has been agreed during the coordination among SEE TSOs and RCC(s); e. ‘ordered XRA’ is an agreed XRA that is bindingly ordered after the end of CROSA; f. ‘agreed but not ordered XRA’ or ‘ANORA’ is an agreed XRA that has not been ordered after the end of CROSA; g. 'activated XRA' means ordered XRA that has been implemented by the XRA connecting TSO(s), or the request for their activation has been sent to the third party XRA provider; h. ‘CGM’ means the common grid model as defined in Article 2

(2)of the CACM Regulation; i. ‘CGMM’ means the common grid model methodology pursuant to Articles 67 and 70 of the SO Regulation; j. 'conditionally available XRA' means an XRA whose availability depends on conditions determined by the XRA Connecting TSO(s); k. ‘CSAM’ means the methodology for coordinating operational security analysis pursuant to Article 75 of the SO Regulation; l. ‘CROSA’ or ‘coordinated regional operational security assessment’ means a process of an operational security analysis performed by RCC (s)

Article 78of the SO Regulation; m.

‘coordinated operational security analysis’ means an operational security analysis performed by a TSO

Article 72(3) and 72(4) of the SO Regulation; n.

‘ID RSA’ means the intraday regional operational security analysis as referred to in Article 72

(1)(d) of the SO Regulation; o. ‘IGM’ means the individual grid model as defined in Article 2
(1)of the CACM Regulation; p. ‘RAO’, means remedial action optimisation that determines optimal set of XRAs within each CROSA; q. ‘RD and CT’ means ‘redispatching and countertrading’ as defined pursuant to Article 2
(26)and Article 2
(13)of the Transparency Regulation; r. ‘ROSC’ means ‘regional operational security coordination’; s. ‘scanned element’ means a network element which is monitored during CROSA such that CROSA does not worsen, or create new operational security violations; t. ‘(X)RA connecting TSO’ means a TSO responsible for the control area where the (X)RA is located or connected. In case of an interconnector, the TSO executing the topological change shall be considered as (X)RA connecting TSO; u. ‘XRA affected TSO’ means the TSO which is significantly impacted by the activation of an XRA; v. ‘XNE’ or ‘cross-border relevant network element’ means a network element 19 identified as cross-border relevant and on which operational security violations need to be managed in a coordinated way; w. ‘XNEC’ or ‘cross-border relevant network element with contingency’ means an XNE associated with a contingency. For the purpose of this methodology, the term XNEC also covers the case where an XNE is used in operational security analysis without a specified contingency; x. ‘XNE connecting TSO’ means the TSO responsible for the control area where the XNE is located or connected. In case of an interconnector, the TSOs on both sides of the interconnector shall be considered as XNE connecting TSOs; y. ‘third party (X)RA provider’ means a party other than the (X)RA connecting TSO who owns and/or operates the assets involved in the activation of the concerned (X)RA; z. ‘network element’ means any component of a transmission system, including interconnectors, or of a distribution system, including a closed distribution system, such as a single line, a single circuit, a single HVDC system, a single transformer, a single phase-shifting transformer, or a voltage compensation installation; (
  1. aa)‘RAIF’ or ‘remedial action influence factor’ means a flow deviation on a XNEC resulting from the application of a remedial action, normalised by the PATL on the associated XNE; (
  2. bb)‘preventive (X)RA’ means a remedial action that is the result of an operational planning process and needs to be activated prior to the investigated timeframe for compliance with the (N-1) criterion; (
  3. cc)‘local preliminary assessment’ means an operational security analysis performed by a TSO to prepare an individual grid model; (
  4. dd)‘overlapping XNE’ means an XNE on which the physical flows are significantly impacted by electricity exchanges in two or more CCRs or by XRAs from two or more CCRs; (
  5. ee)‘overlapping XRA’ means an XRA that is able to address operational security violations on overlapping XNE; (
  6. ff)‘curative (X)RA’ means a remedial action that is the result of an operational planning process and is activated straight subsequent to the occurrence of the respective contingency for compliance with the (N-1) criterion, taking into account TATL and the accepted duration of transitory admissible overload; (
  7. gg)‘virtual positive load margin’ means a positive margin defined by a TSO for a scanned element that will be applied on top of the PATL in order to represent the influence of available remedial action which is not an XRA; 20 (
  8. hh)‘permanent admissible transmission loading’, or ‘PATL’ means the maximum loading in amperes, MW or MVA that can be sustained on a network element for an unlimited duration without risk to the equipment; (
  9. ii)‘temporary admissible transmission loading’, or ‘TATL’ means the maximum loading in amperes, MW or MVA that can be sustained on a network element for a limited duration without risk to the equipment; (
  10. jj)‘thermal limit’ refers to both PATL and TATL; (
  11. kk)‘transitory admissible overload’ means the temporary overload of a network element which is allowed for a limited period and which do not cause physical damage to the network element as long as the defined duration and thresholds are respected. 2. This ROSC Methodology defines the following types of XRAs determined in the following sequence: a. Recommended XRAs are the XRAs determined as optimal by RAO and recommended by the RCC to TSOs; b. Agreed XRAs are the recommended XRAs which are either agreed or modified during the coordination among TSOs and the RCC; c. Ordered XRAs are agreed XRAs for which TSOs and the RCC agree that their activation cannot be postponed until the next CROSA due to specific activation constraints (e.g. required activation time) of such XRAs; d. Activated XRAs are the ordered XRAs which have been implemented by the XRA connecting TSOs, or the request for their activation has been sent to the resource provider. 3. This ROSC Methodology determines the following types of constraints: a. Operational security limits: the acceptable operating boundaries for secure grid operation. This ROSC Methodology shall cover the following operational security limits: (
  12. i)thermal limits of network elements (PATL and TATL); (
  13. ii)voltage limits; (iii) stability limits of the transmission system identified

Article 38

(2)and Article 38
(6)of the SO Regulation; and (
  1. iv)short-circuit current limits of the transmission system. b. Constraints on XRAs: constraints related to all aspects required to be taken into account when using XRAs and classified as followed: (
  2. i)technical constraints are the rules representing technical limitations for activation of XRAs; (
  3. ii)operational constraints are the operational conditions and usage rules taking into account the timings to operate the network and avoid a premature ageing of the assets included in the XRAs; (iii) procedural constraints are all the timing constraints due to local or regional 21 processes; and (
  4. iv)priority constraints are representing national legal requirements regarding the priority of activation of XRAs. c. Additional optimisation constraints called system constraints are additional optimisation constraints, expressed as current limits on a single or a set of XNEs and scanned elements and necessary to respect operational security limits other than PATL and TATL. 4. In this ROSC Methodology, unless the context requires otherwise: a. The acronym ‘(X)RA’ is used where the reference can mean both the remedial action or cross-border relevant remedial action; b. The singular indicates the plural and vice versa; c. Headings are inserted for convenience only and do not affect the interpretation of this ROSC Methodology; d. Any reference to legislation, regulations, directives, orders, instruments, codes or any other enactment shall include any modification, extension or re-enactment of it when in force; e. Any reference to an Article without an indication of the document shall mean a reference to this ROSC Methodology. TITLE 2 REGIONAL OPERATIONAL SECURITY COORDINATION Article 3 General provisions for ROSC 1. SEE TSOs in coordination with the SEE RCC shall perform the ROSC for long term studies for year-ahead regional operational security coordination

CSAM. When SEE TSOs propose a second amendment to this ROSC Methodology, they shall include in this proposal also the detailed process for regional operational security coordination for yearahead timeframe as well as possible other long-term timeframes. 2. SEE TSOs in coordination with the SEE RCC shall execute the ROSC for each timestamp of the target operation day. The ROSC consists of the following activities: (a) Intraday regional operational security analysis (ID RSA) as described in Article 4; (b) One day-ahead and several intraday CROSAs. Day-ahead CROSAs shall be performed

the timings defined in CSAM. Intraday CROSAs shall be performed at least three times in the intraday timeframe

timings defined in CSAM. Each CROSA shall consist of: (

  1. i)Preparation as described in Chapter 1 of Title 4; 22 (
  2. ii)Coordination as described in Chapter 2 of Title 4; (iii) Validation as described in Chapter 3 of Title 4; (
  3. iv)Implementation and activation as described in Chapter 4 of Title 4. A CROSA may consist of two coordination runs. (
  4. c)Fast activation process as described in Title 5. SEE TSOs shall have the right to modify an ordered XRA or may activate a new (X)RA following the fast activation process. Article 4 Intraday regional operational security analysis 1. The goal of the ID RSA is to provide SEE TSOs the latest information for each timestamp of the operation day about the loading of the transmission system and previously undetected operational security violations, which may serve as a trigger for a fast activation process. 2. ID RSA shall be performed at each hour of the day for each timestamp until the end of the operation day. 3. ID RSA shall be performed on the updated IGMs containing the latest available forecast of generation and load, planned outages, forced outages and agreed XRAs. 4. For the purpose of ID RSA, each SEE TSO shall provide IGMs to SEE TSOs and the SEE RCC for all remaining timestamps of the operation day, respecting CGMM provisions and including all agreed XRAs resulting from the latest CROSA or fast activation process. 5. The SEE RCC shall merge updated IGMs into an updated CGM, perform a load flow and contingency analysis and deliver the results to all SEE TSOs. TITLE 3 DEFINITION AND DETERMINATION OF CROSA INPUTS Article 5 Definition of XNEs 1. XNEs shall be: (
  5. a)all critical network elements (‘CNEs’) included in the final list of CNEs in the dayahead and intraday capacity calculation methodology of the SEE CCR

the CACM Regulation; and (b) all other network elements within the control area of SEE TSOs with a voltage level higher than or equal to 150 kV, except for those network elements that are not CNEs and for which SEE TSOs agree that they are not cross-border relevant for the SEE CCR and may therefore be excluded, following the process referred to in Article 7

(3)(b)(iii).
  1. The list of XNEs shall contain all XNEs defined in paragraph
  2. 23 Article 6 Definition of scanned elements
  3. The scanned elements shall be network elements, which are not XNEs and on which CROSA shall not worsen eventually existing operational security violations, or create new operational security violations.
  4. For CROSA purposes only, each SEE TSO shall set on each scanned element an individual virtual positive load margin, on top of the PATL defined in its IGM.
  5. The list of scanned elements shall contain all scanned elements defined pursuant to paragraph
  6. Article 7 The establishment and maintenance of the lists of XNEs and scanned elements
  7. By twelve months before the implementation of the first implementation step of this methodology, all SEE TSOs, with the support of the SEE RCC shall determine the list of XNEs and the list of scanned elements

Article 5and Article 6.

2. By twelve months before the implementation of this methodology, all SEE TSOs, with the support of the SEE RCC, shall agree on a process for amendments and regular review of the list of XNEs and the list of scanned elements. 3. When establishing and maintaining the list of XNEs and the list of scanned elements, each SEE TSO shall have the right, for the network elements which are at least partly located in its control area: (

  1. a)to include in the list of XNEs any network element with a voltage level higher than or equal to 150 kV without further agreement with other SEE TSOs, if the network element is modelled in the TSO’s year-ahead IGM or in the IGM otherwise specified in the process pursuant to paragraph 2; (
  2. b)to exclude any network element from the list of XNEs (except for CNEs) as follows: (
  3. i)the following network elements may be subject to exclusion without further agreement with other SEE TSOs: (
  4. i)radial lines, including those connecting power plants, (
  5. ii)distribution network elements and (iii) transformers with the secondary voltage lower than 220 kV; (
  6. ii)SEE TSOs, which are part of more than one CCR, shall have the right to exclude from the list of XNEs any network element that is subject to regional operational security coordination within other CCR(s). In such case, the corresponding SEE TSO shall inform the TSOs and RCC (
  7. s)of the other CCR(s), about the network elements it excluded; (iii) SEE TSOs shall have the right to exclude any elements from the list of XNEs (except for CNEs) if there is a common agreement amongst SEE TSOs that such elements can be excluded; 24 (
  8. c)to include in the list of scanned elements any network element excluded from the list of XNEs; (
  9. d)to include in the list of scanned elements any network element which is modelled in its IGM, with a voltage level lower than 220 kV that is not on the list of XNEs; (
  10. e)to exclude any network element from the list of scanned elements; 4. 5. 6. 7. 8. 9. (
  11. f)to move any network element from its control area fulfilling the criteria for XNEs defined in Article 5 from the list of scanned elements to the list of XNEs. Each SEE TSO shall have the right to include in the list of scanned elements also overlapping XNEs which are declared as XNEs in other CCRs as well as other network elements which are part of its observability area. When applying the process referred to in paragraph 2 and if a new network element with a voltage level higher than or equal to 220 kV is commissioned, the SEE TSO operating this network element shall decide on its inclusion in the list of XNEs pursuant to paragraph 2 while respecting Article 5. When applying the process referred to in paragraph 2 and if a new network element with a voltage level lower than 220 kV is commissioned, the SEE TSO operating this network element shall decide on its inclusion in the list of scanned elements pursuant to paragraph 2 while respecting Article 6. By applying the process referred to in paragraph 2, SEE TSOs shall update the list of XNEs and the list of scanned elements when necessary and inform the SEE RCC about the change. The list of XNEs and the list of scanned elements shall be reassessed by SEE TSOs at least once a year. SEE TSOs shall share the list of XNEs and the list of scanned elements with the SEE RCC for day- ahead and intraday CROSAs. The SEE RCC shall start using the newly shared list of XNEs and the list of scanned elements in the next CROSA. Article 8 Classification of remedial actions 1. Each SEE TSO shall classify the RAs

Article 22of the SO Regulation. 2. RAs classified in categories (d), (h), (i) and (j) of Article 22

(1)of the SO Regulation shall not be used for the ROSC process. Article 9 Cross-border relevance of remedial actions 1. Within one month after the list of XNEs has been defined

Article 7

, SEE TSOs shall share with the SEE RCC all potential RAs, designed

CSAM, which are at least sometimes able to address violations of current limits on XNEs. In doing 25 so, each SEE TSO shall also consider the potential RAs recommended by the SEE RCC

Article 78(2)(a) of the SO Regulation.

Each SEE TSO shall continuously assess the possibility for new potential RAs. All SEE TSOs and the SEE RCC shall commonly assess the possibility for new potential RAs at least on biannual basis.

  1. All potential RAs identified pursuant to paragraph 1 shall be considered as cross-border relevant (XRAs), unless all SEE TSOs unanimously agree that a potential RA is not crossborder relevant.
  2. SEE TSOs, in coordination with the SEE RCC, shall jointly assess the XRA affected TSOs for each XRA determined pursuant to paragraph
  4. SEE TSOs shall aim at agreeing on a qualitative approach

Article 10to determine XRA affected TSOs for each XRA.

5. If the concerned XRA is quantifiable such as RD and CT, change of set point on HVDC systems or change of taps on phase-shifting transformers, the quantity above which this XRA is having a significant effect on the control areas of other TSOs and its control area has to be specified

CSAM. 6. If SEE TSOs cannot agree on XRA affected TSOs based on a qualitative approach

Article 10

, quantitative approach

Article 11shall be used to determine the XRA affected TSOs.

  1. SEE TSOs shall jointly define and share with the SEE RCC the list of XRA affected TSOs and any update to such list.
  2. SEE TSOs with the support of the SEE RCC, shall reassess the XRA affected TSOs at least on an annual basis.
  3. If a new potential RA is designed by a SEE TSO for its control area during real time operation and if the system is in alert state

Article 18

of the SO Regulation and determined as XRA pursuant to paragraph 2, the XRA connecting TSOs shall use quantitative assessment in order to identify the XRA affected TSOs. In doing so, the XRA connecting TSO shall check that the activation of such XRA does not lead to operational security violations on network elements of its observability area using either the latest available CGM or its model from the state estimator. If such analysis shows that the activation of a new XRA may cause operational security violations on network elements of its observability area, its activation has to be coordinated with the TSO(s) where the operational security violations occur.

  1. During real time operation, if the system is in emergency state and only when operational conditions allow it, when preparing restoring remedial actions each TSO shall assess the XRA affected TSOs.
  2. Between two mandatory assessments of XRA affected TSOs pursuant to paragraph 8, each SEE TSO shall have the right to request an additional assessment of XRA affected TSOs providing justification for such a request to the XRA connecting TSO and respective SEE RCC.
  3. During fast activation process, when a SEE TSO proposes an XRA in emergency and alert state pursuant to CSAM and when this TSO is the XRA connecting TSO as well as the only 26 XRA affected TSO, the activation of this XRA shall not be subject to further coordination. SEE TSOs and the SEE RCC shall be informed of the activation of such XRA.
  4. By no later than 1 year after adoption of this ROSC Methodology, all SEE TSOs shall develop a common procedure for identification of all potential RAs and new potential RAs

requirement mentioned in paragraph

(1). This procedure shall describe at least criteria used by SEE TSOs for potential RAs identification. Article 10 Qualitative assessment of XRA affected TSOs 1. For each XRA identified pursuant to Article 9
(2): (
  1. a)Each SEE TSO shall individually assess the effect of each XRA on its control area; (
  2. b)Each XRA connecting TSO shall assess the effect of its XRAs on control areas of other SEE TSOs and also on its control area. 2. SEE TSOs may delegate the tasks described in paragraph 1 to the SEE RCC. 3. When a SEE TSO identifies that an XRA has a significant impact on its control area, it shall inform the XRA connecting TSO and request that it be determined as XRA affected TSO and provide justification for such request. 4. If SEE TSOs reach a common agreement that an XRA has significant impact on a specific control area, then the concerned TSO shall be defined as XRA affected TSO. 5. If an XRA connecting TSO receives no request from any other SEE TSO to be determined as XRA affected TSO, the XRA connecting TSO shall be the only XRA affected TSO. Article 11 Quantitative assessment of XRA affected TSOs 1. The SEE RCC shall use the CGMs established

Article 67of the SO Regulation when quantifying the effect of XRAs on TSOs.

2. Quantitative assessment of XRA affected TSOs shall be done on all XNEs defined

Articles 5 and

  2. If an XRA consists of a combination of actions, the quantitative assessment of XRA affected TSOs shall be done for the combined effect.
  3. A TSO shall be considered as XRA affected TSO if the RAIF calculated

CSAM for this XRA is equal or higher than 5% on any XNE (in N-situation or contingency) for which this TSO is the XNE connecting TSO. This significance threshold may be reduced if agreed by SEE TSOs subject to the governance framework defined in Article

  2. The RAIF referred to in paragraph 4 shall be calculated on the latest available CGM. 27 Article 12 Contingency list
  3. Each SEE TSO shall establish the list of contingencies (hereafter referred to as ‘contingency list’) to be simulated in operational security analysis. The contingency list shall be established

Article 33of the SO Regulation.

2. Each SEE TSO shall provide the respective SEE RCC and SEE TSOs with its contingency list to be used in CROSA and shall inform the SEE RCC about any update of this list

CSAM.

  1. In case a specific operational security violation on XNE or scanned element with specific contingency can be more efficiently addressed outside of the day-ahead and intraday CROSA, the SEE TSOs and SEE RCC may exclude the relevant XNECs and scanned elements associated with a contingency from the concerned day-ahead and intraday CROSA if there is a common agreement amongst SEE TSOs that such XNECs can be excluded.
  2. The SEE RCC shall start using the newly shared contingency lists in the next CROSA. TITLE 4 COORDINATED REGIONAL OPERATIONAL SECURITY ANALYSIS PROCESS CHAPTER 1 PREPARATION Article 13 Provision of CROSA inputs
  3. Each SEE TSO shall provide the following input data to the SEE RCC: (a) IGM according to Article 14, including the operational security limits for each XNE and scanned element according to Articles 5 and 6; (b) XNEs and scanned elements according to Articles 5 and 6; (c) Contingency list according to Article 12; (d) Available XRAs within its control area according to Article 15; (e) Constraints on XRAs

Article 2

(4)and Article 15; and (f) When relevant, system constraints according to Article
  2. The SEE RCC shall provide for each intraday CROSA the list of agreed XRAs from previous CROSAs archived by the SEE RCC

Article 30. 3.

When providing information on XNEs and XRAs pursuant to paragraph 1(

  1. b)and (
  2. d)the connecting TSO shall also provide the information whether the concerned XNE or XRA is overlapping as determined pursuant to Article 28. 4. The input data pursuant to paragraph 1 shall cover all timestamps of the operation day in 28 case of day-ahead CROSA and all applicable timestamps of the operation day in case of intraday CROSA. 5. Each SEE TSO shall update the input data for the second coordination run of the day-ahead CROSA and possible second coordination runs in intraday CROSAs

the provisions defined in Articles 14 to

  2. Within the timelines established pursuant to Article 18

(4), all SEE TSOs and the SEE RCC shall define for each CROSA the common gate closure time by which the inputs pursuant to in paragraph 1 can be delivered and updated by SEE TSOs. Article 14 Preparation and updates of IGMs by SEE TSOs
  1. Each SEE TSO shall prepare and deliver day-ahead and intraday IGMs for day-ahead and intraday CROSAs as defined in CSAM and the CGMM.
  2. Each SEE TSO shall have the right to perform a local preliminary assessment pursuant to CSAM. Each SEE TSO shall have the right to include in its IGM the (X)RAs resulting from the local preliminary assessment performed before the day-ahead CROSA

the rules specified in CSAM. 3.

CSAM, each SEE TSO shall have the right to include in its IGM, the (X)RAs for which this TSO is the only XRA affected TSO and that are resulting from the local preliminary assessment performed by such SEE TSO at any time. 4.

CSAM, if a SEE TSO includes in its IGMs the (X)RA(

  1. s)resulting from the local preliminary assessments pursuant to paragraph 2 and 3, the information on these (X)RA(
  2. s)shall be shared among SEE TSOs and be clearly distinguishable in the IGM from the initial state variables without these (X)RAs applied

Article 70(4) of the SO Regulation. 5. The costs of (X)

RAs included in IGM resulting from the local preliminary assessment shall not be included in the final costs to be shared

the cost sharing methodology.

  1. In case paragraphs 2 and 3 are contradicting the provisions of CSAM, the relevant provisions from CSAM shall prevail.
  2. If the RAO results in agreed XRAs for the respective control area, each SEE TSO shall provide to the SEE RCC an updated IGM with agreed XRAs between two coordination runs within one CROSA

CSAM and CGMM. The XRAs resulting from the first coordination run shall not be binding and shall be possible to be changed by the RAO during the following coordination run within the same CROSA if deemed necessary. Article 15 Information on available XRAs 1. Each SEE TSO shall make available all XRAs as identified in Article 9

(2)to the SEE RCC 29 for each day-ahead and intraday CROSA as defined in CSAM unless an XRA is not available pursuant to this article. 2. When identifying whether the XRAs identified pursuant to Article 9
(2)shall be made available for the day-ahead and intraday CROSAs, each SEE TSO shall respect the following principles: (a) Each XRA connecting TSO shall assess the availability of all its XRAs identified in Article 9
(2); (
  1. b)Each XRA connecting TSO may declare the XRA as not available in case it cannot be activated due to: i. an unforeseen event, or ii. planned or unplanned outage, or iii. a declaration of unavailability status done by a third party XRA provider, or iv. any other cause outside of the responsibility of the SEE TSOs; (
  2. c)In case XRA is conditionally available, the XRA connecting TSO shall provide to the SEE RCC and other SEE TSOs the conditions for its availability and the underlying justification. 3. Each SEE TSO shall provide any relevant information for each available or conditionally available XRA for the purpose of day-ahead and intraday CROSA process that will reflect the technical, operational or procedural constraints of the XRA as defined

Article 2. 4.

Each SEE TSO shall also provide, for the purpose of day-ahead and intraday CROSA, the information on the available volume of XRAs considering the constraints of XRAs as defined

Article 2. 5.

SEE TSOs and the SEE RCC shall agree and define a detailed specification of information requirements for XRAs needed for each CROSA. This shall include a predefined set of conditions for conditionally available XRAs. 6. In case of a second coordination run of the coordination stage of day-ahead or intraday CROSA, each SEE TSO shall provide to the SEE RCC an updated information on available XRAs, considering: (a) The agreed outcome of the latest coordination run for the XRAs

Article 27

and 28; (

  1. b)Any update of XRA availability related to unplanned or forced outages or changes of outage schedules of relevant assets; (
  2. c)Any update of available XRA volumes related to the latest schedules of load and generation. 7. In case XRAs are owned or provided by a third party, such third party XRA providers shall provide to the XRA connecting TSOs best up-to-date information on the availability of their XRAs, including all the necessary information that is required for CROSAs. This information shall be provided by the deadline determined by the XRA connecting TSO, which shall be shortly before the gate closure time referred to in Article 13

(6). The provided 30 information shall include at least the following: (
  1. a)Available volume of XRAs; (
  2. b)Technical characteristics and constraints of XRAs; (
  3. c)Information on prices or costs of XRAs, which shall enable the XRA connecting TSOs and the SEE RCC the estimation of total costs of XRAs subject to their optimal and/or ordered volume. Article 16 System constraints 1. SEE TSOs may apply system constraints

Article 2

for the purpose of respecting operational security limits other than thermal limits. Such system constraints shall be expressed as a current limit on a single XNE or a set of XNEs and scanned elements. 2. The system constraints introduced for the purpose of dynamic stability shall be defined based on the criteria for dynamic system stability

Articles 38 and 39 of the SO Regulation. 3. Before applying such system constraints, the concerned SEE TSO shall provide to other SEE TSOs and the SEE RCC in a transparent manner all the details and possible underlying studies on how the value of each specific system constraint was determined and calculated. 4. When SEE TSOs propose a second amendment to this ROSC Methodology, they shall include in this proposal also the information on: (

  1. a)which TSOs need to apply system constraints; (
  2. b)which system constraints need to be applied and which operational security limits are represented in such system constraints; (
  3. c)justification on why these system constraints need to be applied in CROSAs and why other measures are not sufficient or appropriate; and (
  4. d)information about possible long-term measures to mitigate the need for system constraints. Article 17 Consistency and quality check of the input data 1. The SEE RCC shall assess and monitor the consistency and quality of each input data file provided by each SEE TSO

CGMM and CSAM.

  1. The SEE RCC shall monitor if the agreed XRAs are included in the IGMs provided by each SEE TSO.
  2. The SEE RCC shall inform the concerned SEE TSOs on the identified issues pursuant to paragraphs 1 and 2 in an appropriate timeframe before starting the RAO, to give SEE TSOs the opportunity to correct these errors or inconsistencies and provide updated input files. 31 CHAPTER 2 COORDINATION Article 18 General provisions of coordination process
  3. The SEE RCC in coordination with SEE TSOs shall perform the day-ahead and intraday CROSAs

CSAM. 2. The day-ahead CROSA shall include two coordination runs and each intraday CROSA will include at least one coordination run. Each coordination run shall consist of the following steps: (a) Building of the CGMs by the RCC

CGMM; (b) Performing the load flow and contingency analysis

Article 19

; (c) RAO

Articles 20 to 26; (d) Coordination of XRAs

Article 27

; (e) Inter-CCR coordination

Article 28. 3.

The RAO of each CROSA shall use all available XRAs as identified

Articles 9 to 11 and Article

  1. All recommended XRAs that are the result of the RAO shall be considered for the purpose of subsequent processes, i.e. coordination of XRAs, validation, inter-CCR coordination and determination of costs for cost sharing.
  2. All SEE TSOs with the support of the SEE RCC shall jointly define the timeline of each step of the day-ahead and intraday CROSA,

CSAM and CGMM. The timings shall be published on the ENTSO-E website. 5.

Article 32

, during the intraday CROSA, the SEE TSOs and SEE RCC shall reassess the ANORAs that were agreed in the day-ahead CROSA or previous intraday CROSA as well as other available XRAs (except ordered XRAs), for the period relevant for the actual intraday CROSA.

  1. Information about ordered XRAs and ANORAs during day-ahead and intraday CROSA shall be archived by the SEE RCC. Article 19 Operational security analysis
  2. The SEE RCC shall perform the operational security analysis by using the CGM built

CGMM. The security analysis will be performed considering the latest contingency list as well as the latest list of XNEs and scanned elements provided by SEE TSOs. 2. Operational security analysis shall be performed by applying the AC load flow calculation. For the eventual cases of AC load flow divergence (at the particular contingencies), DC load flow can be used as the fall-back solution. 32 3. The SEE RCC shall provide to all SEE TSOs the operational security analysis results. These results shall contain, at least: (

  1. a)applied current limits for XNEs and scanned elements; (
  2. b)current loading of the XNECs and scanned elements with contingencies; (
  3. c)applied voltage limits; (
  4. d)voltages calculated on the CGM; (
  5. e)cases of AC load flow divergence and possible fall-back DC load flow results. 4. SEE TSOs shall have the opportunity to validate the power flow and operational security analysis results. This validation aims at identifying errors in input data, which would make the outcome of the operational security analysis non-realistic and to give SEE TSOs the opportunity to correct these errors. In case of the detection of errors in input data, the concerned SEE TSOs shall update their input data. Article 20 Remedial action optimisation 1. SEE TSOs and the SEE RCC shall optimise XRAs in order to identify in a coordinated way the most effective and economically efficient XRAs, based on the following principles: (
  6. a)The remedial action optimisation (RAO) of XRAs shall be performed with consideration of all available XRAs

Article 15

; (b) The RAO shall consider all constraints on XRAs

Article 21

; (c) The RAO shall aim at relieving operational security violations on XNEs

Article 22

; (d) The RAO shall not create additional operational security violations on XNEs and scanned elements

Article 23

; (e) The RAO shall aim at ensuring economic efficiency by minimising the incurred costs of XRAs as well as the effectiveness of the XRAs to address operational security violations

Article 24

; (f) The RAO shall ensure energy balance of XRAs

Article 25

; (g) The RAO shall take into account the impact of variations in forecasts and market activities

Article 26. Article 21 Constraints on XRAs 1.

The RAO shall take into account all constraints of XRAs as determined in Article 2 and provided by SEE TSOs

Article 13

, including intertemporal constraints, when identifying the most effective and economically efficient XRAs for all timestamps that are being optimised. 33

  1. The RAO for day-ahead CROSA shall optimise all timestamps of the operation day.
  2. The RAO for intraday CROSA shall optimise all remaining timestamps until the end of the operation day.
  3. In the RAO for both day-ahead and intraday CROSA, any constraints

Article 2(4) on ordered XRAs from previous timestamps shall be taken into account.

Article 22 Relieving operational security violations 1. When performing day-ahead and intraday CROSAs, SEE TSOs and the SEE RCC shall detect operational security violations. These violations can be addressed with RAO or during the coordination of XRAs pursuant to Article 27. The RAO shall aim to reduce the currents on XNEs in N-situation or after occurrence of a contingency down to the applicable current limits. The current limits shall represent the thermal limits (PATL and TATL) of an XNE, unless otherwise defined in this methodology. 2. The thermal limits of XNEs shall be defined as follows: (

  1. a)Seasonal limit, which means a fixed limit for all hours of each of the four seasons; (
  2. b)Dynamic limit, which means a value per hour reflecting the varying ambient conditions; (
  3. c)Fixed limits for all hours, in case of specific situations where the physical limit reflects the capability of overhead lines, cables or substation equipment installed in the primary power circuit (such as circuit-breaker, or disconnector) with limits not sensitive to ambient conditions. 3. SEE TSOs shall aim at gradually phasing out the use of seasonal limits pursuant to paragraph 2(
  4. a)and replace them with dynamic limits pursuant to paragraph 2(b), when the benefits are greater than the costs. After the end of each calendar year, each TSO shall analyse for all its XNEs for which seasonal limits are applied and have been congested at least in 0.1% of timestamps in the previous calendar year, the expected reduction of remedial action costs and increase in economic surplus from single day-ahead and intraday coupling in the next 10 years resulting from the implementation of dynamic limits, and compare it with the cost of implementing dynamic limits. Each TSO shall provide this analysis to the SEE RCC and all SEE TSOs shall report these analyses to SEE regulatory authorities. If the cost benefit analysis, taking into account other planned investments, is positive, the concerned TSO shall implement the dynamic limits within three years after the end of the analysed calendar year. In case of interconnectors, the concerned TSOs shall cooperate in performing this analysis and implementation when applicable. 4. For addressing violations of other operational security limits, such as voltage violations, violations of short-circuit current limits or violations of stability limits, each SEE TSO should perform local assessment and long-term operational security analysis

Articles 31, 38 and 73 of the SO Regulation. These violations may be addressed in CROSA during the coordination of XRAs pursuant to Article

  1. When addressing these 34 violations by applying additional constraints on XRAs, the concerned SEE TSO shall provide to other SEE TSOs and the SEE RCC the reasoning for these constraints in a transparent manner.
  2. SEE TSOs may also apply system constraints that reflect other operational security limits referred to in paragraph 4 for the purpose that RAO does not create new or worsen the existing underlying operational security violations. However, RAO shall not resolve these underlying violations as these shall be resolved

paragraph

  2. In intraday CROSA, the detection of current limit violations pursuant to paragraph 1 shall be performed on CGMs, which do not include ANORAs.
  3. The RAO shall aim at identifying the optimal XRAs from the list of available XRAs

Article 15

to relieve violations of applicable current limits on XNEs in NSituation and all contingencies, detected pursuant to paragraph

  2. Curative XRAs shall be used for relieving operational security violations in contingency case on an XNE as long as the TATL of a network element is not exceeded. Under consideration of all recommended preventive and curative XRAs, the PATL of XNEs shall be respected. Article 23 Avoiding additional operational security violations on XNEs and scanned elements
  3. The activation of XRAs determined by the RAO for relieving operational security violations on XNEs: (a) shall not lead to additional operational security violations of operational security limits on XNEs and scanned elements; and (b) shall not worsen eventually existing operational security violations on scanned elements

Article 6. 2.

On request of SEE TSOs and in case a scanned element constrains the RAO in a significant frequency, the SEE TSO who has defined this scanned element shall do everything in its power to reduce its constraining character, e.g. by increasing its virtual positive load margin. Article 24 Economic efficiency and effectiveness 1. The RAO shall determine the optimal set of XRAs and their volumes by respecting the following objectives (in order of priority): (a) aim to relieve operational security violations

Article 22

and 23; (

  1. b)aim to minimise total sum of costs and revenues of XRAs; and (
  2. c)aim to minimise the amount and volume of XRAs. 2. In case RAO is not able to find a solution given the three objectives defined in paragraph 1 it may relax these three objectives to the minimum extent required and in reverse order of priority in order to find a solution. 35 3. The RAO shall take into account the impact of XRAs on operational security violations with remedial action influence factor (RAIF), which determine the impact of each RA on the power flow or current on XNEs and scanned elements as a function of their nominal power flow or current. 4. If RAO is not able to relieve all operational security violations, it shall provide all relevant information on the remaining operational security violations. Article 25 Energy balance of XRAs 1. In order to guarantee the energy balance of the electricity system after activation of XRAs, the RAO shall ensure that the optimised XRAs do not create energy imbalances and can be activated in a way that does not create energy imbalances in each timeframe. Article 26 Robustness 1. Taking into account all the principles introduced in Articles 21 to 25, the RAO shall ensure that the identified XRAs for relieving operational security violations on the XNEs are robust to variations of forecasts in consumption, RES production, and market activities and allow SEE TSOs to operate their control area without operational security violations. 2. In case of exceptional situations, such as, but not limited to, unpredictable arrival of a wind front or snowfall on PV modules, where the accuracy of one or more of the forecasts variables included in the IGMs is insufficient to allow the correct identification of operational security violations, SEE TSOs shall have the right to change the current limit of their XNEs referred to in Article 22 in regional day-ahead or intraday processes

CSAM. 3. Concerned TSOs shall inform without undue delay SEE TSOs and the SEE RCC in case of application of paragraph 2, providing at least the following information: (

  1. a)XNEs and timestamps which are affected by the application of paragraph 2; (
  2. b)Estimate of the time for which application of paragraph 2 is needed. 4. In case of application of paragraph 2, the concerned SEE TSOs shall provide ex-post on request of any SEE TSO its justification about its decision to other SEE TSOs and the SEE RCC. 5. The SEE RCC shall monitor the need, the effectiveness and the impact of the reduction of current limits applied pursuant to paragraph 2 and report to all SEE TSO(s). Subject to this report, all SEE TSOs may agree,

governance rules pursuant to Article 36, to exclude additional costs of XRAs resulting from reduced current limits from cost sharing. 36 Article 27 Coordination of XRAs 1. The SEE RCC shall recommend the implementation of the most effective and economically efficient XRAs identified by the RAO to the XRA connecting TSOs and inform at least all XRA affected TSOs about this recommendation. 2.

CSAM, Article 78

(4)of the SO Regulation and Article 42
(2)of the Electricity Regulation, during each CROSA, the recommended XRAs shall be considered as agreed, except where it is rejected by: (
  1. a)any XRA affected TSO (including XRA connecting TSOs) on the grounds that the implementation of a specific XRA would result in operational security violations; (
  2. b)the XRA connecting TSO on the grounds that the recommended XRA is no longer available. 3. If a SEE TSO rejects a recommended XRA, it shall provide to the SEE RCC and other SEE TSOs clear reasons for rejection, including the evidence for the claimed grounds of rejection. 4. If a SEE TSO rejects a recommended XRA, except in the case of an unavailability of the proposed XRA, the SEE RCC in coordination with the respective SEE TSO shall perform an ex-post assessment, at the request of any SEE TSO or the SEE RCC, to determine the additional costs and impact resulting from the rejected XRA on the congestion. These costs and impact shall be compared with the costs (and impact on congestion) of possible (X)RAs not recommended by the SEE RCC which would avoid the rejection of a recommended XRA. If a recommended XRA is frequently rejected by a SEE TSO due to a specific reason, the SEE RCC in coordination with the rejecting SEE TSO shall perform an ex-post assessment as described above. The rejecting SEE TSO shall also propose and apply mitigating measures to avoid similar rejections in future. 5. In case of rejection of a recommended XRA, the concerned SEE TSOs shall coordinate with the SEE RCC and other SEE TSOs to identify and plan alternative XRAs taking into account cost and efficiency to relieve the operational security violations in a coordinated way

this methodology and CSAM.

Article 78

(2)(a) of SO Regulation, the SEE RCC may recommend alternative XRAs other than those identified by the concerned SEE TSO(s). Article 28 Inter-CCR coordination 1.

the CSAM, the SEE RCC and relevant other RCC (s) in coordination with SEE TSOs shall relieve operational security violations on overlapping XNEs and shall coordinate overlapping XRAs impacting these overlapping XNEs. 2.

CSAM, the SEE RCC shall perform the coordinated cross-regional operational security assessment with relevant other RCC(s). In doing so, the SEE RCC shall consider and coordinate with relevant other RCC(s) the use of XRAs available in the 37 concerned CCRs.

  1. The SEE RCC in coordination with XRA connecting TSOs and XNE connecting TSOs shall assess whether the concerned XRAs and XNEs are overlapping according to CSAM; CHAPTER 3 VALIDATION Article 29 Validation session
  2. In the end of the day-ahead CROSA

CSAM, the SEE RCC and SEE TSOs shall consolidate results of the day-ahead CROSA and validate XRAs that have been agreed during the day-ahead CROSA. Article 30 Outcome of validation

  1. The SEE RCC shall archive all ordered XRAs and ANORAs after the validation session.
  2. The SEE RCC shall report any remaining operational security violations. Based on this input, SEE TSOs shall specify next steps which may include, but not limited to, an intraday CROSA or fast activation process.
  3. The SEE RCC shall ensure the availability of results and decisions to all SEE TSOs.
  4. The SEE RCC shall archive all necessary data for the yearly report

Article 17of the SO Regulation.

CHAPTER 4 IMPLEMENTATION OF REMEDIAL ACTIONS Article 31 Activation of XRAs 1. Each XRA connecting TSO shall activate XRAs at the latest time compatible with technical, operational and procedural constraints of the resources

CSAM. 2. In fast activation process, each SEE TSO shall have the right to request a reassessment of ordered XRAs or already activated XRAs in case the XRAs are not required anymore and considering technical, operational and procedural constraints. XRA affected TSOs shall reassess the ordered XRAs via fast activation process

Article 33. 3.

In order to prevent the effect of activated XRAs on operational security to be diminished by additional cross-zonal trade SEE TSOs may: (

  1. a)prevent the netting of cross-border schedules, which result from activated XRAs, with cross-zonal capacities and prevent that these schedules increase cross-zonal capacities 38 in the directions in which additional trade could worsen operational security; (
  2. b)as a last resort measure, modify cross-zonal capacities outside the coordinated capacity calculation process pursuant to the day-ahead and intraday capacity calculation methodology of the SEE CCR, if: i. waiting for the next coordinated capacity calculation would endanger operational security; and ii. additional cross-zonal trade would create operational security violations which would not be possible to be addressed with available XRAs. Article 32 Consideration of remedial actions in next IGM 1. All agreed XRAs shall be classified based on a possibility of their reassessment in later CROSAs: (
  3. a)If activation time of an agreed XRA prevents waiting for the next CROSA for possible reassessment, then such XRA shall be classified as ordered XRA. Only fast activation process can change the status of such ordered XRA; (
  4. b)If a reassessment of an agreed XRA in the next CROSA is possible, then such XRA shall be classified as ANORA. 2. Each SEE TSO shall include all agreed XRAs determined during the latest CROSA in the intraday IGMs as provided in CSAM. Information about all agreed XRAs determined during day-ahead and intraday CROSA shall be archived by the SEE RCC. 3. The SEE RCC shall monitor the inclusion of agreed XRAs into IGMs

CSAM. TITLE 5 FAST ACTIVATION PROCESS Article 33 Fast activation process 1. The fast activation process shall be considered as a fall-back solution for situations where coordination through the CROSA is no longer possible due to insufficient time and the regular process described in Article 18 could not be properly applied. 2. In case of new circumstances (determined in paragraph 3) which lead to detection of operational security violations on XNEs (in N-situation or after occurrence of a contingency): (

  1. a)between two CROSAs, when a fast activation of XRAs is required because it cannot wait for the next CROSA; or (
  2. b)after the latest CROSA, 39 the XNE connecting TSO shall trigger the fast activation process to relieve operational security violations on such XNEs. 3. The fast activation process can be triggered for the following circumstances: (
  3. a)The ordered XRA is no longer available due to unexpected technical unavailability of the underlying assets and alternative XRAs need to be activated; and (
  4. b)New operational security violations have been detected and they cannot be resolved with the next CROSA. 4. During the fast activation process, the XRA connecting TSOs and XRA affected TSOs shall coordinate among each other to identify, plan and activate alternative or additional XRAs to relieve the operational security violations in a coordinated way while respecting the relevant provisions of CSAM. New operational security violations as a result of those XRAs should be avoided. 5. In the fast activation process, the activation of preventive as well as curative XRAs may be applied. 6. In the fast activation process, each SEE TSO may activate XRAs in direct coordination with XRA affected TSOs

the principles for coordination of XRAs described in CSAM.

  1. A SEE TSO activating XRAs through fast activation process shall provide the SEE RCC the relevant information on which the decision to activate XRAs was based.
  2. The fast activation process shall end once XRAs to relieve the operational security violation are identified, coordinated and agreed. These XRAs will be considered as agreed XRAs.
  3. SEE TSOs shall include the changes regarding activated XRAs resulting from fast activation process in the next relevant IGMs. TITLE 6 DETERMINATION OF INPUTS FOR COSTS SHARING Article 34 Inputs for cost sharing of XRAs
  4. Cost sharing pursuant to the cost sharing methodology shall be applied for ordered XRAs resulting from each CROSA. Cost sharing shall also be applied to XRAs which have been ordered in fast activation process in a circumstance determined pursuant to Article 33

(3)(a). Cost sharing pursuant to the cost sharing methodology shall not be applied to XRAs which have been ordered in fast activation process pursuant to Article 33
(3)(b). The costs of these XRAs shall be borne by the XNE connecting TSO(s) triggering the fact activation process.
  1. The cost sharing methodology shall be executed, independently, for each CROSA. The inputs for the cost sharing of XRAs from a given CROSA, such as CGM, ANORAs and ordered XRAs, shall be determined exclusively from the data used and resulting from this CROSA. The costs and/or revenues for each CROSA shall be determined only for ordered 40 XRAs resulting from that CROSA.
  2. SEE TSOs and the SEE RCC shall determine for each CROSA and for each XRA the total costs and/or revenues that shall be shared between SEE TSOs

the cost sharing methodology. 4. The costs and/or revenues of ordered XRAs shall be determined based on the prices and costs provided by TSOs and used in RAO and the volumes of ordered XRAs determined by RAO or subsequent coordination

Article 27. 5.

Any deviations in costs and/or revenues resulting from the difference between: (

  1. a)the prices and costs per volume, provided by TSOs for the execution of the RAO; and (
  2. b)the final incurred costs per volume or settled costs per volume with third party XRA provider, shall also be subject to cost sharing pursuant to the cost sharing methodology. 6. The deviations of costs and/or revenues resulting from deviations between ordered and delivered volume of XRAs shall not be subject to cost sharing. 7. All SEE TSOs and the SEE RCC shall monitor the deviations in costs and/or revenues of ordered XRAs as defined in paragraph 5 and identify systematic deviations or other potential abuse resulting from these deviations. In case of identified abuse, SEE TSOs shall have the right to reject a specific deviation to be included in cost sharing

the governance principles pursuant to Article

  2. All SEE TSOs and the SEE RCC shall monitor the impact of deviations in costs and/or revenues of ordered XRAs as defined in paragraph 5 on the efficiency and effectiveness of RAO. This monitoring shall focus on the loss of economic efficiency as well as possible effectiveness of RAO arising from these deviations.
  3. For XRAs which have significant deviations pursuant to paragraph 5, all SEE TSOs and the SEE RCC shall identify mitigating measures to minimise the impact of these deviations on RAO and cost sharing.
  4. All SEE TSOs shall establish, share and settle the provisional costs and/or revenues of ordered XRAs for cost sharing and settlement by no later than 30 days after the end of the calendar month. Any corrections to the provisional costs and/or revenues of ordered XRAs shall be established, shared and settled by no later than 90 days after the end of a given quarter. Any deviations in costs and revenues beyond this deadline shall not be subject to cost sharing pursuant to the cost sharing methodology.
  5. All SEE TSOs shall determine and calculate all the parameters and data resulting from each CROSA that are required as inputs to cost sharing and as determined in cost sharing methodology, including particular versions of CGMs from each CROSA. 41 TITLE 7 MONITORING AND IMPLEMENTATION Article 35 Reporting and monitoring
  6. The SEE RCC shall record and share all necessary data to enable SEE TSOs and RCC(s) to fulfil the obligations regarding this methodology, the cost sharing methodology and Articles 14 and 17 of the SO Regulation. This data shall be stored for at least 3 years and shall be made available to SEE regulatory authorities at request.
  7. SEE TSOs and the SEE RCC shall perform regular monitoring of the efficiency, effectiveness and robustness of ROSC process after its implementation. This shall in particular include the following: (a) Monitoring of the input data and inclusion of agreed XRAs in IGMs

Articles 17 and 33; (

  1. b)Monitoring of deviations between indicative and realised prices and/or costs of XRAs and their impact on efficiency and effectiveness of RAO pursuant to Article 34; (
  2. c)Monitoring the need, the effectiveness and the impact of the reduction of current limits due to variations of forecasts in consumption, RES production, and market activities

Article 26

; (

  1. d)Monitoring the occurrence and the reasons for the use of the fast activation process pursuant to Article 33; and (
  2. e)Monitoring the need, the effectiveness and the impact of the operational security violations on scanned elements

Article 23. 3.

SEE TSOs and the SEE RCC shall prepare and submit to SEE regulatory authorities on biannual basis a report on efficiency and effectiveness of ROSC process. This shall in particular include: (a) Reporting on the occurrence and impact of rejected XRAs

Article 27

; (b) Reporting on the deviations between indicative and realised prices and/or costs of XRAs, their impact on efficiency and effectiveness of RAO as well as possible abuses and rejections to include those deviations in cost sharing

Article 34and Article 35

(2)(b); (c) Reporting on input data and inclusion of agreed XRAs in IGMs

Article 35

(2)(a); (d) Reporting on the robustness of XRAs

Article 35

(2)(c); (e) Reporting on the occurrence and the reasons to use the fast activation process

Article 35(2)(e).

4. SEE TSOs and the SEE RCC shall make available to SEE regulatory authorities at their request the following data regarding the ROSC process: (

  1. a)For each timestamp, each CROSA and each XNEC relieved by RAO: The list of 42 XNECs relieved by RAO, their loading before and after RAO, applicable current and flow limits; (
  2. b)For each timestamp, each CROSA and each XRA recommended by RAO and ordered XRA: The prices and/or costs used in RAO, the volumes determined by RAO, the type of XRAs, the ordered volume of XRAs, the final settled cost of XRAs; (
  3. c)The loading of XNEC defined in point (
  4. a)in real-time (based on e.g. real time snapshots). 5. SEE TSOs and the SEE RCC shall consult and coordinate with SEE regulatory authorities regarding detailed specification of the above reporting and data delivery requirements. SEE regulatory authorities shall have the right to request additional reporting and data delivery in coordination with SEE TSOs and the RCC, or to withdraw the requirement for specific reporting or data delivery, if they consider it no longer valid. SEE TSOs, the SEE RCC and regulatory authorities shall cooperate to avoid duplication of reporting and data delivery requirements. 6. By no later than 6 months after adoption of this ROSC Methodology, each SEE TSO shall develop a description of national rules and procedures for activation of remedial actions, with specific focus on redispatching actions. This description shall entail all relevant information that is required for understanding of these rules and procedures. For cost-based compensation of redispatching actions, the description shall clearly list the different cost categories, and identifies which cost categories are to be considered as incurred costs in the cost sharing methodology. It shall also include the planning on future evolution of these rules and assessment of potential incompatibilities with this ROSC Methodology. This assessment shall be updated on an annual basis and provided to SEE RCC, SEE TSOs and SEE regulatory authorities. Article 36 Rules concerning governance and decision making among SEE TSOs 1. All SEE TSOs shall cooperate for the implementation and operation of this ROSC Methodology. This cooperation shall be carried out through common bodies where each TSO shall have at least one representative. The members of the common bodies shall aim to make unanimous decisions. Where unanimity cannot be reached, qualified majority voting based on the voting principles established

Article 5(5) of the SO Regulation shall apply.

2. All SEE TSOs shall establish a steering committee consisting of one representative from each SEE TSO. The steering committee shall make binding decisions on any matter or question related to the implementation and operation of this ROSC Methodology. The steering committee shall adopt rules governing its operation. 3. The steering committee shall also act as a body for settlement of disputes among SEE TSOs regarding the implementation and operation of this ROSC Methodology. The steering committee shall solve the problems and disputes regarding, but not limited to, the following 43 issues: (

  1. a)Resolution of disputes on the interpretation of aspects of this methodology, which may not be clear; (
  2. b)Resolution of disputes on design choices required for implementation and operation of this methodology, which are not defined in this methodology; and (
  3. c)Resolution of possible disputes in the application and operation of this methodology, including the disputes related to the provisions ruling the day-to-day operation, but excluding the day-to-day operation itself. Article 37 Implementation 1. This ROSC Methodology shall be implemented in two steps. In the first step, all SEE TSOs and the SEE RCC shall implement the first implementation step of the ROSC Methodology as described in paragraphs 2, 3 and 5. In the second step all SEE TSOs and the SEE RCC shall implement the second implementation step of the ROSC Methodology as described in paragraphs 4 and 5. 2. All SEE TSOs and the SEE RCC shall implement the first implementation step of the ROSC Methodology no later than 31.12.2025. The first implementation step of the ROSC Methodology shall fulfil at least the following requirements: (
  4. a)Implementation of day ahead CROSA; (
  5. b)Implementation of cost sharing for day-ahead CROSA pursuant to cost sharing methodology; (
  6. c)RAO for day-ahead CROSA must include at least optimisation of redispatching resources and phase shifting transformers. 3. The first implementation step of the ROSC Methodology may include some other simplification of the ROSC Methodology which do not significantly infringe the requirements pursuant to paragraph 2. These simplifications shall be consulted with SEE regulatory authorities. 4. All SEE TSOs and the SEE RCC shall implement the second implementation step of the ROSC Methodology no later than 30.06.2027. The second implementation step of the ROSC Methodology shall fulfil all the requirements of this ROSC Methodology and shall be complemented by the implementation of the cost sharing methodology. 5. The implementation process for both steps of the ROSC Methodology shall consist of the development, testing and implementation of the IT tools as well as systems and procedures required to support the ROSC Methodology. 6. All SEE TSOs and the SEE RCC shall closely follow the implementation of the ROSC Methodology in the Core CCR and strive to adopt the same tools, systems and processes in the ROSC Methodology for the SEE CCR, when duly justified. 7. By no later than four months after the adoption of this ROSC Methodology, all SEE TSOs and the SEE RCC shall develop a detailed implementation plan for this ROSC Methodology and update it regularly. The implementation plan shall define: 44 (
  7. a)clear implementation tasks, milestones and deliverables for which each SEE TSO and the SEE RCC is responsible individually; and (
  8. b)clear implementation tasks, milestones and deliverables for which SEE TSOs and the RCC are responsible jointly. 8. All SEE TSOs with the support of the SEE RCC shall regularly provide to SEE regulatory authorities the following information regarding the implementation of this ROSC Methodology: (
  9. a)the implementation plan as well as its regular updates; (
  10. b)the information on the implementation progress with regard to individual and joint implementation steps, milestones and deliverables; (
  11. c)without undue delay, the possible risks of implementation delay and possible mitigation options; (
  12. d)the individual entities responsible for delays in implementation tasks, milestones and deliverables with individual responsibilities; and (
  13. e)the contribution of individual entities to the failure to meet the implementation tasks, milestones and deliverables with joint responsibilities. 9. After adoption of this ROSC Methodology and during its implementation, all SEE TSOs and the SEE RCC shall endeavour to continue to improve the existing SEE CSA and the existing day-ahead and ID RSA processes. TITLE 8 ALLOCATION OF TASKS Article 38 Appointment of RSC and delegation of tasks to RSC 1. SEE TSOs appoint SEleNe CC as RSC that shall perform the tasks listed in Article 77

(3)of the SO Regulation in the SEE CCR. 2. SEleNe CC shall perform the tasks listed in Article 77
(3)of the SO Regulation in the SEE CCR for all SEE TSOs in a transparent and non-discriminatory manner. 3.

Article 77(3) of the SO Regulation all SEE TSOs delegate the following tasks to SEle

Ne CC: (a) ROSC

Article 78

of the SO Regulation in order to support SEE TSOs to fulfil their obligations for the year-ahead, day-ahead and intraday timeframes

Articles 34

(3), 72 and 74 of the SO Regulation; (b) Building of CGM

Article 79

of the SO Regulation; (c) Regional outage coordination

Article 80

of the SO Regulation, in order to support SEE TSOs to fulfil their obligations in Articles 98 and 100 of the SO Regulation; and 45 (d) Regional adequacy assessment

Article 81of the SO Regulation in order to support SEE TSOs to fulfil their obligations under Article 107 of the SO Regulation. 4. In line with Article 35

(2)of the Electricity Regulation SEleNe CC, as of 1 July 2022, has been appointed as the SEE RCC. 5. SEleNe CC shall perform the tasks listed in Article 37
(1)of the Electricity Regulation for all SEE TSOs in a transparent and non-discriminatory way. Article 39 Coordination and decision-making process
  1. The SEE RCC shall cooperate in good faith and shall seek to adopt a fair and loyal treatment of the other Parties concerned.
  2. The SEE RCC shall implement the provision of the tasks in close consultation and cooperation with the SEE TSOs.
  3. The SEE RCC and SEE TSOs shall establish a contractual framework for the implementation of this methodology. Article 40 Rules concerning governance and operation of RSCs
  4. The security of supply shall be the responsibility of each of the SEE TSOs according to national laws and regulations. The responsibility for secure system operation and for any decision taken based on tasks performed by SEleNe CC shall remain with the SEE TSOs.
  5. For the avoidance of doubt, these rules shall not replace any provision of national or European law that may apply to any of the SEE TSOs. The provisions of these rules shall be complementary and interpreted

the applicable regulations. In case of contradictions between these rules and the applicable laws and regulations, the provisions of these rules shall be amended accordingly.

  1. Any dispute between the RCC and SEE TSOs arising out of or in connection with this methodology shall be settled amicably between the Parties. In case the dispute cannot be settled amicably between the Parties within 60 calendar days after having been notified hereof, the dispute shall be finally settled by a decision of SEE TSOs pursuant to governance rules determined in Article
  2. 46 TITLE 9 FINAL PROVISIONS Article 41 Publication of this proposal
  3. Upon approval by the SEE National Regulatory Authorities, each SEE TSO shall publish this ROSC Methodology on their respective websites

Article 8(1) of the SO Regulation.

Article 42 Language 1. The reference language for this ROSC Methodology shall be English. For the avoidance of doubt, when SEE TSOs need to translate this ROSC Methodology into their national language(s), in the event of inconsistencies between the English version published by SEE TSOs

Article 8

(1)of SO Regulation and any version in another language, the relevant SEE TSOs shall,

national legislation be obliged to dispel any inconsistencies by providing a revised translation of this ROSC Methodology to their relevant national regulatory authorities. 47 Πρώτη τροποποίηση της Μεθοδολογίας για τον συντονισμό της περιφερειακής επιχειρησιακής ασφάλειας για την ΠΥΔ Νοτιοανατολικής Ευρώπης σύμφωνα με το άρθρο 76 παράγραφος 1 του Κανονισμού (ΕΕ) 2017/1485 της Επιτροπής της 2ας Αυγούστου 2017 σχετικά με τον καθορισμό κατευθυντήριας γραμμής για τη λειτουργία του συστήματος μεταφοράς ηλεκτρικής ενέργειας Φεβρουάριος 2024 48 Αιτιολογικές σκέψεις

(1)
(2)
(3)
(4)
(5)
(6)
(7)
(8)Στο παρόν έγγραφο προβλέπεται η τροποποίηση της Μεθοδολογίας για τον συντονισμό περιφερειακής επιχειρησιακής ασφάλειας για την Περιφέρεια Υπολογισμού Δυναμικότητας Νοτιοανατολικής Ευρώπης σύμφωνα με το άρθρο 76 παράγραφος 1 του Κανονισμού (ΕΕ) 2017/1485 σχετικά με τον καθορισμό κατευθυντήριας γραμμής για τη λειτουργία του συστήματος μεταφοράς ηλεκτρικής ενέργειας (στο εξής αναφερόμενου ως «Κανονισμός ΛΣ»). Το παρόν έγγραφο θα αναφέρεται στο εξής ως «Μεθοδολογία ΣΠΕΑ». Η παρούσα Μεθοδολογία ΣΠΕΑ λαμβάνει υπόψη τις γενικές αρχές και τους στόχους που καθορίζονται στον Κανονισμό ΛΣ καθώς και στον Κανονισμό (ΕΚ) 2015/1222 της Επιτροπής σχετικά με τον καθορισμό κατευθυντήριων γραμμών για την κατανομή της δυναμικότητας και τη διαχείριση της συμφόρησης (εφεξής «Κανονισμός ΚΔΔΣ»). Η παρούσα Μεθοδολογία ΣΠΕΑ λαμβάνει υπόψη τις πιθανές εξαρτήσεις από τον Κανονισμό (ΕΕ) 2017/2195 της Επιτροπής σχετικά με τον καθορισμό κατευθυντήριας γραμμής για την εξισορρόπηση ηλεκτρικής ενέργειας, τον Κανονισμό (ΕΕ) 543/2013 της Επιτροπής σχετικά με την υποβολή και δημοσίευση δεδομένων στις αγορές ηλεκτρικής ενέργειας και την τροποποίηση του παραρτήματος I του Κανονισμού (ΕΚ) 714/2009 (εφεξής «Κανονισμός για τη διαφάνεια»), καθώς και τον Κανονισμό (ΕΕ) 1227/2011 της Επιτροπής για την ακεραιότητα και τη διαφάνεια στη χονδρική αγορά ενέργειας (εφεξής «Κανονισμός REMIT»). Το άρθρο 76 του Κανονισμού ΛΣ αποτελεί τη νομική βάση και καθορίζει τις απαιτήσεις για τη μεθοδολογία ΣΠΕΑ. Η παρούσα Μεθοδολογία ΣΠΕΑ περιλαμβάνει επίσης τον διορισμό ενός ΠΣΑ και τον ορισμό κανόνων όσον αφορά τη διακυβέρνηση και τη λειτουργία του ΠΣΑ, σύμφωνα με τα άρθρα 77 παράγραφος 1, 77 παράγραφος 2 και 77 παράγραφος 3 του Κανονισμού ΛΣ. Σύμφωνα με το άρθρο 35 παράγραφος 2 του Κανονισμού 2019/943 του Ευρωπαϊκού Κοινοβουλίου και του Συμβουλίου για την εσωτερική αγορά ηλεκτρικής ενέργειας (εφεξής «Κανονισμός για την ηλεκτρική ενέργεια»), από την 1η Ιουλίου 2022 οι ΠΣΑ έχουν αντικατασταθεί από τα περιφερειακά συντονιστικά κέντρα («ΠΣΚ») Κανονισμό το ΠΣΚ ΝΑΕ συμπληρώνει το ρόλο των ΔΣΜ εκτελώντας τα περιφερειακά καθήκοντα που του έχουν ανατεθεί σύμφωνα με το άρθρο 37 του Κανονισμού για την ηλεκτρική ενέργεια. Σύμφωνα με το άρθρο 37 παράγραφος 1 στοιχείο β) του Κανονισμού για την ηλεκτρική ενέργεια, τα ΠΣΚ διενεργούν τη συντονισμένη ανάλυση ασφαλείας σύμφωνα με τις μεθοδολογίες που αναπτύσσονται δυνάμει των κατευθυντήριων γραμμών λειτουργίας του συστήματος που εκδίδονται βάσει του άρθρου 18 παράγραφος 5 του Κανονισμού (ΕΚ) αριθ. 714/2009. Ως εκ τούτου από την 1η Ιουλίου 2022 το ΠΣΚ ΝΑΕ θα διενεργεί τη Μεθοδολογία ΣΠΕΑ για την ΠΥΔ ΝΑΕ. Επομένως όλες οι αναφορές σε «ΠΣΑ» έχουν αναλόγως αντικατασταθεί σε «ΠΣΚ» σε αυτή την τροποποίηση της Μεθοδολογίας ΣΠΕΑ. Η παρούσα Μεθοδολογία ΣΠΕΑ προσδιορίζει μια επαρκή συχνότητα ενδοημερησίου συντονισμού της ανάλυσης επιχειρησιακής ασφάλειας και των επικαιροποιήσεων του 49 ΚΜΔ για την εγγύηση της ασφάλειας και της σταθερότητας του δικτύου σύμφωνα με το άρθρο 76 παράγραφος 1 στοιχείο α) του Κανονισμού ΛΣ.
(9)Η παρούσα μεθοδολογία ΣΠΕΑ συμβάλλει στους στόχους που αναφέρονται στο άρθρο 76 παράγραφος 1 στοιχείο β) του Κανονισμού ΛΣ, εισάγοντας μια διαδικασία συντονισμού με σαφείς κανόνες για την προετοιμασία διορθωτικών μέτρων διασυνοριακής σημασίας με συντονισμένο τρόπο και αναθέτει σαφείς αρμοδιότητες προς τους ΔΣΜ ΝΑΕ και το ΠΣΚ ΝΑΕ.
(10)Για την ανταλλαγή σχετικών πληροφοριών και για την προετοιμασία διορθωτικών μέτρων διασυνοριακής σημασίας σύμφωνα με το άρθρο 76 παράγραφος 1 στοιχείο β) σημείο
  1. i)και το άρθρο 76 παράγραφος 1 στοιχείο β) σημείο
  2. iv)του Κανονισμού ΛΣ, η παρούσα Μεθοδολογία ΣΠΕΑ καθορίζει όλα τα δεδομένα εισόδου που αφορούν τον συντονισμό περιφερειακής επιχειρησιακής ασφάλειας.
(11)Για την ενεργοποίηση των διορθωτικών μέτρων διασυνοριακής σημασίας, σύμφωνα με το άρθρο 76 παράγραφος 1 στοιχείο β) σημείο iv), η παρούσα μεθοδολογία ΣΠΕΑ ορίζει δύο τύπους διαδικασιών συντονισμού που στοχεύουν στην επίλυση των παραβιάσεων επιχειρησιακής ασφάλειας με διορθωτικά μέτρα διασυνοριακής σημασίας. Η τυπική διαδικασία συντονισμού ονομάζεται συντονισμένη αξιολόγηση περιφερειακής επιχειρησιακής ασφάλειας («ΑΣΠΕΑ») σύμφωνα με το άρθρο 78 του Κανονισμού ΛΣ, η οποία εκτελείται σε περιφερειακό επίπεδο από όλους τους ΔΣΜ και το ΠΣΚ ΝΑΕ μαζί. Σε περιπτώσεις όπου η ΑΣΠΕΑ δεν μπορεί να εφαρμοστεί, οι ΔΣΜ μπορούν να εφαρμόσουν μια διαδικασία ενεργοποίησης γεγονότων, η οποία είναι ένας περιορισμένος συντονισμός που εκτελείται από ΔΣΜ οι οποίοι υφίστανται παραβίαση της επιχειρησιακής ασφάλειας σε συντονισμό με τα ΠΣΚ και άλλους ΔΣΜ και η οποία μπορεί να επηρεαστεί από την εφαρμογή διορθωτικών μέτρων.
(12)Η παρούσα Μεθοδολογία ΣΠΕΑ καθορίζει όλους τους σχετικούς τύπους περιορισμών που είναι απαραίτητοι για τη διασφάλιση της επιχειρησιακής ασφάλειας σύμφωνα με το άρθρο 76 παράγραφος 1 στοιχείο β) σημείο ii) του Κανονισμού ΛΣ.
(13)Για τον προσδιορισμό των πλέον αποτελεσματικών και οικονομικά αποδοτικών διορθωτικών μέτρων σύμφωνα με το άρθρο 76 παράγραφος 1 εδάφιο β σημείο iii) του Κανονισμού ΛΣ, η παρούσα Μεθοδολογία ΣΠΕΑ εισάγει τη διαδικασία της βελτιστοποίησης διορθωτικών μέτρων («ΒΔΜ») Στόχος της βελτιστοποίησης αυτής είναι να ελαχιστοποιήσει το κόστος που προκύπτει, καθώς και να διασφαλίσει ότι τα διορθωτικά μέτρα εφαρμόζονται αποτελεσματικά για την αντιμετώπιση παραβιάσεων της επιχειρησιακής ασφάλειας.
(14)Σύμφωνα με το άρθρο 76 παράγραφος 1 στοιχείο β) σημείο v) του Κανονισμού ΛΣ, η παρούσα Μεθοδολογία ΣΠΕΑ συμπληρώνει τη μεθοδολογία επιμερισμού του κόστους για την ΠΥΔ Νοτιοανατολικής Ευρώπης που θεσπίστηκε σύμφωνα με το άρθρο 74 του Κανονισμού ΚΔΔΣ. Ενώ η μεθοδολογία επιμερισμού του κόστους καθορίζει τη συγκεκριμένη λύση επιμερισμού του κόστους, η παρούσα Μεθοδολογία ΣΠΕΑ προσδιορίζει όλα τα σχετικά δεδομένα εισόδου και τις παραμέτρους που απαιτούνται για την εφαρμογή της μεθοδολογίας επιμερισμού του κόστους. 50
(15)Δεδομένου ότι η ΠΥΔ ΝΑΕ χαρακτηρίζεται από ένα δίκτυο με υψηλό βαθμό διασύνδεσης, όλα τα στοιχεία δικτύου τάσης ίσης ή μεγαλύτερης των 150 kV και όλα τα διαθέσιμα διορθωτικά μέτρα θεωρούνται γενικά ως διασυνοριακής σημασίας. Αυτό οφείλεται στο γεγονός ότι στην ΠΥΔ ΝΑΕ δεν είναι γενικά δυνατό να προσδιοριστεί ένα στοιχείο δικτύου που θα επηρεαζόταν μόνο από διορθωτικά μέτρα τα οποία δεν έχουν αντίκτυπο σε άλλα διασυνοριακής σημασίας στοιχεία του δικτύου. Ωστόσο, είναι δυνατόν να υπάρξουν εξαιρέσεις στον κανόνα εάν όλοι οι ΔΣΜ της ΝΑΕ συμφωνούν ότι μεμονωμένα στοιχεία του δικτύου μπορούν να θεωρηθούν ως μη διασυνοριακής σημασίας.
(16)Καθώς όλα τα πιθανά διορθωτικά μέτρα θεωρούνται ως διασυνοριακής σημασίας στην ΠΥΔ ΝΑΕ, όταν πρόκειται για τη συντονισμένη ανάλυση της περιφερειακής επιχειρησιακής ασφάλειας, δεν υπάρχει ανάγκη για ποιοτική ή ποσοτική αξιολόγηση της διασυνοριακής τους σημασίας σύμφωνα με την ΜΣΑΑ. Ωστόσο, αφού καθοριστούν τα βέλτιστα διασυνοριακά διορθωτικά μέτρα από τη ΒΔΜ, αυτά μπορούν να τροποποιηθούν περαιτέρω με επακόλουθο συντονισμό και με τη διαδικασία της ταχείας ενεργοποίησης, και οι τροποποιήσεις αυτές πρέπει να συντονίζονται μόνο μεταξύ των ΔΣΜ που επηρεάζονται άμεσα από τα σχετικά διορθωτικά μέτρα. Για τον σκοπό αυτόν, η παρούσα Μεθοδολογία ΣΠΕΑ καθορίζει επίσης μια μεθοδολογία για την ποιοτική και ποσοτική αξιολόγηση των ΔΣΜ που επηρεάζονται σημαντικά από διασυνοριακής σημασίας διορθωτικά μέτρα.
(17)Για την επίτευξη των στόχων που αναφέρονται στο άρθρο 76 παράγραφος 1 του Κανονισμού ΛΣ, η Μεθοδολογία ΣΠΕΑ εξετάζει και, όπου είναι αναγκαίο, συμπληρώνει: α. τη μεθοδολογία για το συντονισμό της ανάλυσης επιχειρησιακής ασφάλειας σύμφωνα με το άρθρο 75 του Κανονισμού ΛΣ (εφεξής «ΜΣΑΑ»)· β. την κοινή μεθοδολογία ΝΑΕ για τη συντονισμένη αναδιανομή και αντίρροπη συναλλαγή σύμφωνα με το άρθρο 35 του Κανονισμού ΚΔΔΣ· γ. την κοινή μεθοδολογία ΝΑΕ για τον συντονισμένο επιμερισμό του κόστους αναδιανομής και αντίρροπης συναλλαγής (εφεξής «μεθοδολογία επιμερισμού του κόστους») σύμφωνα με το άρθρο 74 του Κανονισμού ΚΔΔΣ.
(18)Σε αυτή τη μεθοδολογία ΣΠΕΑ, η ΑΣΠΕΑ αποτελείται από ένα βήμα προετοιμασίας, ένα βήμα συντονισμού (που περιέχει έναν ή περισσότερους κύκλους συντονισμού) και ένα βήμα επικύρωσης. Η ΑΣΠΕΑ περιγράφει τον συντονισμό μεταξύ των ΔΣΜ και του ΠΣΚ της ΠΥΔ Νοτιοανατολικής Ευρώπης, καθώς και τον συντονισ

🔗 Στην επίσημη πηγή

Επεξήγηση AI βάσει του επίσημου κειμένου του νόμου. Ενδεικτική, δεν υποκαθιστά νομική συμβουλή.