About Functionality Process

Dear user,
Welcome to the Gas Network Codes Functionality Platform. This Platform is a focal point for issues related to Network Codes (NCs) and Guidelines (GLs).
This page provides general and practical information about access to and the treatment of issues notified via the Gas Network Codes Functionality Platform.
For fully detailed information on the purpose and scope of the Functionality Process and access conditions to the Gas Network Codes Functionality Platform, see the Terms of Use .

1. FUNCTIONALITY PROCESS

The purpose of "The Functionality Process for Gas Network Codes" is to handle issues which are related to the way of working of the various NCs and GLs on gas transmission by involving stakeholders, National Regulatory Authorities and Transmission System Operators. The process is aimed at reaching proposal(s) for issue solution(s) from ACER and ENTSOG on the cross-border, regional and European issues.

Within the Functionality Process, Stakeholders are provided a possibility to raise and discuss issues related to the NCs and GLs as well as being involved in elaborating on the proposal(s) for issue solution.

2. SCOPE OF FUNCTIONALITY PROCESS

The scope of the Functionality Process is limited to the issues related to or derived from the NCs, GLs and the Transparency Annex of the Regulation (EC) No. 715/2009. The assessment whether the issue falls under the scope of the Functionality Process is done during the validation step between ACER and ENTSOG. The criteria for validation are included in Terms of Use .

This voluntary Functionality Process is not a substitute for a formal network code amendment procedure, as described in Article 7 of Regulation (EC) No. 715/2009.

3. ACCESS TO THE GAS NETWORK CODES FUNCTIONALITY PLATFORM

In order to report or support an issue, you must first register on the Gas Network Codes Functionality Platform.
As a principle, issues can be raised by any relevant entity, as defined in Terms of Use . Therefore, while everyone can access the Gas Network Codes Functionality Platform, only eligible users may register and report an issue (within the defined scope of the Platform). Eligibility criteria are detailed in Terms of Use .

4. PROCESSING OF REPORTED ISSUES

The Functionality Process consists of coordinated joint collection, validation, categorization, and prioritization of issues as well as coordinated joint (ACER-ENTSOG) elaboration of solutions.

  1. Collection involves on-going reviewing of the posted issues on the Gas Network Codes Functionality Platform.
  2. Validation is an assessment whether the issues fall under the scope of the Functionality Process (for validation criteria see Terms of Use ).
  3. Categorization includes grouping of the issues into one of the following categories:
    • National issues, affecting only one Member State;
    • Cross-border issues, affecting two Member States without further European relevance;
    • Cross-border issues with further European relevance;
    • Regional issues;
    • European issues.

    As a main principle, issues which can be solved locally will be handled at that level. National issues, affecting only one Member State, or cross-border issues, affecting two Member States without further European relevance, are sent to the relevant National Regulatory Authority(s) and/or Transmission System Operator(s).

    If identified by ACER and ENTSOG that an issue posted as national might potentially become a regional, cross-border or European issue, this issue should be progressed in the Functionality process.

    Cross-border issues with further European relevance, regional and European issues are further prioritised.

  4. Prioritization includes ranking of issues in their order of importance and urgency (e.g. low, medium, high).

Decisions on the validation, categorization and prioritisation are made on a monthly basis. The prioritised/selected cross-border, regional and European issues are sent to the relevant ENTSOG Working Group and ACER Task Force for development of the solutions. Stakeholders may be contacted to provide clarity if an issue is not clear or fully understood. If the Stakeholder is not responding to the communication, ACER and ENTSOG may take measures to proceed with the issue.

At the end of the Functionality Process, when ACER and ENTSOG agree on a solution, it is commonly recommended and approved by the relevant decision-making bodies of ENTSOG and ACER, and then published.