System Operation

System Operation

The SO Regulation

The SO Regulation provides the rules and standards to ensure the required level of operational security, frequency, quality and efficient use of the interconnected system and resources. The SO Regulation entered into force on 14 September 2017. ​

Click here for information on the incident on the power system separation of Iberia from Continental Europe on 24 July 2021.

Click here for in​​​​​formation on the continental Europe electricity system separation (​8th January 2021) incident.​​

Click here for information on the incident in the Polish power system on 17 May 2021.

System Operation

The core elements

Image
Electricity small

The SO Regulation applies to significant grid users that are further characterised as (new or existing):

  • power generating modules classified as type B, C and D

  • transmission connected demand facilities

  • transmission connected closed distribution systems     

  • demand facilities, closed distribution systems and third parties in case they provide demand response directly to the TSO

  • high-voltage direct current (HVDC) systems, as well as,

  • providers of redispatching of power generating modules or demand facilities by means of aggregation and providers of active power reserve.

The network code provides a minimum degree of harmonisation and leaves certain details to further implementation p​rocedures at regional level. This also applies to terms and conditions, as well as to methodologies, in connection to:

  • key organisational requirements, roles and responsibilities related to data exchange and operational security

  • methodology for building the common grid models

  • methodology for coordinating operational security analysis.​​

System Operation

Terms and conditions and methodologies

The SO Regulation defines obligations for TSOs, regulatory authorities and ACER on the development and approval of terms and conditions and methodologies, as well as describing their adoption process. These rules contribute to ensuring security, facilitating the establishment and functioning of the Union's internal electricity market and the integration of renewable energy sources, as well as allowing a more efficient usage of the network and increasing competition for the benefit of consumers.

Terms and conditions and methodologies can be subject to the approval of:

  • All regulatory authorities

  • Regulatory authorities of a specific region

  • Individually at the Member states' level

The TSOs' proposal should be consulted upon and submitted to the relevant regulatory authorities for approval. The proposal should contain a timescale for implementation and expected impact on the Regulation's objectives.

The NRAs involved should take decisions within six months after receiving the proposal. In case of disagreement, the regulatory authorities can request an amendment, allowing TSOs two more months for adjustments and additional two months for the regulatory authorities to approve the revised proposal. If the NRAs do not reach a unanimous agreement, or if they jointly request so, ACER can adopt a decision within six months from the referral.

Once the terms and conditions or methodologies are adopted, they can be amended after the request of the relevant TSO or NRA. In this case, the proposals for adjustments should be submitted for consultation and undergo a new approval procedure.

The implementation tabl​e​ provides more details on the latest updates.

Methodology for coordinated operational security analysis

​All TSOs must develop a proposal for a methodology for coordinating operational security analysis (CSAM) and submit it to all regulatory authorities for approval. The CSAM shall aim at the standardisation of operational security analysis, at least per synchronous area.

Action 1: In September 2018, all TSOs submitted the proposal for the CSAM to the regulatory authorities.

Action 2: In December 2018, all regulatory authorities requested ACER to adopt a decision on the proposal.

Action 3: From 25 January to 18 February 2019, ACER conducted a formal public consultation in order to obtain a wider view from stakeholders.

Action 4: In Spring 2019, ACER engaged with TSOs and NRAs and informed them about the decision.

Action 5: In June 2019, ACER adopted a decision on the CSAM proposal.

The CSAM is expected to be implemented in several steps. Find more details on these steps within the approved methodology.

Related documents

Approved CSAM

Amendments to the methodology for coordinated operational security analysis

Following the 18 months deadline after the CSAM approval (18 December 2020), all TSOs must submit amendments regarding the:

  • Remedial actions inclusion in individual grid models (Article 21)
  • Coordination of cross-border relevant network elements (XNEs) and cross-border relevant remedial actions (XRAs) in overlapping zones (Inter-CCR) (Article 27)
  • Cost Sharing for XNEs and XRAs in overlapping zones (Inter-CCR) (Article 27)

Action 1: In December 2020, ENTSO-E, on behalf of all TSOs, submitted the CSAM amendments proposals to ACER.

Action 2: In March 2021, ACER ran a public consultation to obtain a wider overview from stakeholders.

Action 3: In Spring 2021, ACER engaged with TSOs and NRAs and informed them about the decision.

Action 4: In June 2021, ACER adopted a Decision on the CSAM amendments proposal.

Action 5: In November 2023, ENTSO-E, on behalf of all TSOs, submitted the CSAM amendment proposals to ACER. ACER will decide on TSOs’ proposals by May 2024.

Methodology for assessing the relevance of assets for outage coordination​

All TSOs must develop a proposal for a methodology at least per synchronous area, evaluating the relevance of outage coordination's assets (RAOCM) and submit it to all the regulatory authorities for approval and to ACER for information.

Action 1: In September 2018, all TSOs submitted the proposal for RAOCM to all the regulatory authorities and to ACER.

Action 2: In December 2018, all regulatory authorities requested ACER to adopt a decision on the Proposal.

Action 3: From 25 January to 18 February 2019 ACER conducted a formal public consultation in order to obtain a wider view from stakeholders.

Action 4: In Spring 2019, ACER engaged with TSOs and NRAs and informed them about the decision.

Action 5: In June 2019, ACER adopted a decision on the proposal for RAOCM.

The RAOCM is expected to be implemented within three months after ACER's decision.

Related documents

Approved proposal for coordinating operational security analysis

Methodology for regional operational security coordination - CORE Region​

All CORE TSOs must develop a proposal for a methodology for regional operational security coordination (ROSC) and submit it to all CORE regulatory authorities for approval. The methodology should aim at the regional standardisation of operational security analysis for Austria, Belgium, Croatia, Czech Republic, France, Germany, Hungary, Luxembourg, Netherlands, Poland, Romania, Slovakia and Slovenia (the CORE region).

Action 1: In December 2019, all CORE TSOs submitted the proposal for the ROSC to all regulatory authorities.

Action 2: In June 2020, all CORE regulatory authorities requested ACER to adopt a decision on the proposal.

Action 3: In September 2020, ACER conducted a formal public consultation in order to obtain a wider view from stakeholders.

Action 4: From July to October 2020, ACER engaged with TSOs and NRAs and informed them about the decision.

Action 5: In December 2020, ACER adopted a decision on the Methodology for Regional Operational Security Coordination for the Core Capacity Calculation Region.

The ROSC is expected to be implemented in two steps. Find more details on these steps within the approved methodology.

Related documents

Approved Core ROSC

CORE TSOs' proposal

Explanatory document

RAs letter for referral ​​

Core ROSC​ Non-Paper​​

Methodology for regional operational security coordination - SEE Region

All SEE TSOs must develop a proposal for a methodology for regional operational security coordination (ROSC) and submit it to all SEE regulatory authorities for approval. The methodology should aim at the regional standardisation of operational security analysis for Bulgaria, Greece and Romania (the SEE region).

Action 1: In December 2019, all SEE TSOs submitted the proposal for the ROSC to all regulatory authorities.

Action 2: In October 2020, all SEE regulatory authorities requested ACER to adopt a decision on the proposal.

Action 3: In October 2020, ACER engaged with TSOs and NRAs and informed them about the decision.

Action 4: In December 2020, ACER adopted a decision on the Methodology for Regional Operational Security Coordination for the SEE Capacity Calculation Region.

The ROSC is expected to be implemented in two steps. Find more details on these steps within the approved methodology.

Related documents 

Approved SEE ROSC

SEE TSOs' proposal

RAs letter for referral

RAs Non​- Paper