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.
Find out more about the evolution of the SO Regulation.
The SO Regulation applies to significant grid users that are further characterised as (new or existing):
The network code provides a minimum degree of harmonisation and leaves certain details to further implementation procedures 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.
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:
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 table 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.
The CSAM is expected to be implemented in several steps. Find more details on these steps within the approved methodology.
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.
The RAOCM is expected to be implemented within three months after ACER's decision.
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.
Related documents:
CORE TSOs' proposal
Explanatory document
RAs letter for referral
