Implementing Regulation (EU) No 409/2013 is amended as follows:
Article 2 is amended as follows:
points (1), (2) and (3) are replaced by the following:
‘(1) ”SESAR Joint Undertaking” means the body established under Council Regulation (EC) No 219/2007 [Council Regulation (EC) No 219/2007 of 27 February 2007 on the establishment of a Joint Undertaking to develop the new generation European air traffic management system (SESAR) (OJ L 64, 2.3.2007, p. 1).], or its successor, entrusted with the task of managing and coordinating the development phase of the SESAR project;
“charging scheme” means the scheme established by Commission Implementing Regulation (EU) 2019/317 [Commission Implementing Regulation (EU) 2019/317 of 11 February 2019 laying down a performance and charging scheme in the single European sky and repealing Implementing Regulations (EU) No 390/2013 and (EU) No 391/2013 (OJ L 56, 25.2.2019, p. 1).’;];
“ATM functionality” means a group of ATM interoperable operational functions or services related to trajectory, airspace and surface management or to information sharing within the en-route, terminal, airport or network operating environments;
the following points (3a) and (3b) are inserted:
‘(3a) ”ATM sub-functionality” means an integral part of an ATM functionality consisting of an operational function or service, contributing to the overall scope of the functionality;
“SESAR solution” means an output of the SESAR development phase, introducing new or improved standardised and interoperable technologies and harmonised operational procedures supporting the implementation of the European ATM Master plan;’;
the following point (4a) is inserted:
‘(4a) “synchronised implementation” means an implementation of ATM functionalities in a synchronised way over a defined geographical area, which includes at least two Member States within the EATMN, or between air and ground operational stakeholders based on a common planning that includes implementation target dates and the relevant transitional measures for progressive deployment and involving multiple operational stakeholders;’;
point (6) is replaced by the following:
‘(6) “implementation” means, in reference to ATM functionalities, the procurement, installation, testing, training and putting into service of equipment and systems, including associated operational procedures, carried out by operational stakeholders;’;
the following points (6a) and (6b) are inserted:
‘(6a) “implementation target date” means a date by when the implementation of the ATM functionality or sub-functionality is to be completed;
“industrialisation target date” means a date by when the standards and specifications are to be available for the ATM functionality or sub-functionality to enable its implementation;’;
points (8), (9) and (10) are replaced by the following:
‘(8) “performance scheme” means a scheme established by Implementing Regulation (EU) 2019/317;
“European Union-wide performance targets” means the targets referred to in Article 9 of Implementing Regulation (EU) 2019/317;
“operational stakeholders” means the Network Manager and civil and military: airspace users, air navigation service providers, airport operators;’;
the following point (11) is added:
‘(11) “SESAR project” means an innovation cycle providing the Union with a high performing, standardised and interoperable air traffic management system, which comprises the SESAR definition, development and deployment phases.’;
Article 4 is replaced by the following:
Common projects shall identify the ATM functionalities and their sub-functionalities. Those functionalities and sub-functionalities shall be based on SESAR solutions addressing the essential operational changes defined in the European ATM Master Plan, shall be ready for implementation and shall require synchronised implementation.
Readiness for implementation shall be assessed, inter alia, based on the results of validation carried out during the development phase, the status of industrialisation and an assessment of interoperability, as well as in relation to the International Civil Aviation Organization (‘ICAO’) Global Air Navigation Plan and relevant ICAO material.
Common projects shall set out for each ATM functionality and sub-functionality the following characteristics:
essential operational changes they contribute to;
the operational and technical scope;
the geographical scope;
the operation stakeholders that are required to implement them;
the synchronisation requirements;
the implementation target dates;
the interdependencies with other functionalities or sub-functionalities.
By way of derogation from paragraph 1, common projects may also include ATM functionalities or sub-functionalities that are not ready for implementation but that constitute an essential component of the common project concerned and provided that their industrialisation is deemed to be finalised within three years from the adoption of the concerned common project. For that purpose, an industrialisation target date for those ATM functionalities or sub-functionalities shall also be defined in the common project.
At the expiry of the industrialisation target date, the Commission, with the support of the European Union Aviation Safety Agency, shall verify that the ATM functionalities or sub-functionalities referred to in paragraph 3 have been standardised and that they are ready for implementation. Where they are found not to be ready for implementation, they shall be withdrawn from the common project regulation.
The deployment manager, the SESAR Joint Undertaking, the European standardisation organisations, Eurocae and the relevant manufacturing industry shall cooperate under the coordination of the European Union Aviation Safety Agency to ensure that the industrialisation target date is met.
Common projects shall also:
be consistent with and contribute to the European Union-wide performance targets;
demonstrate a positive business case for the EATMN, based on cost-benefit analysis, and identify any potential local or regional negative impact for any specific category of operational stakeholders;
take account of the relevant deployment elements specified in the Network Strategy Plan and the Network Operations Plan of the Network Manager;
demonstrate an improved environmental performance.’;
Article 5 is amended as follows:
paragraph 2 is replaced by the following:
‘2. The Commission shall be assisted by the Network Manager, the European Union Aviation Safety Agency, the Performance Review Body within their respective roles and competencies, and by the SESAR Joint undertaking, Eurocontrol, the European standardisation organisations, Eurocae and the deployment manager. Those bodies shall involve the operational stakeholders and manufacturing industry.’;
the following paragraph 2a is inserted:
‘2a. The European Union Aviation Safety Agency, upon the request by the Commission shall provide an opinion on the technical readiness for deployment of the ATM functionalities, and their sub-functionalities, proposed for a common project.’;
paragraph 3 is replaced by the following:
‘3. The Commission shall consult the stakeholders in accordance with Articles 6 and 10 of Regulation (EC) No 549/2004 including through the European Defence Agency, within its remit to facilitate the coordination of military views, and the consultative group of experts on the social dimension of the single European sky on its proposals for common projects.
The Commission shall verify that proposals for common projects are endorsed by the airspace users and the ground operational stakeholders that are required to implement a specific common project.’;
paragraph 4 is deleted;
the following paragraph 7 is added:
‘7. Member States and the Network Manager shall include the investments related to the implementation of common projects in the performance plans and the Network performance plan.’;
Article 8 is amended as follows:
in paragraph 2, point (g) is replaced by the following:
‘(g) establishing coordination with the European Union Aviation Safety Agency and with the European standardisation organisations to facilitate industrialisation and promote interoperability of ATM functionalities and sub-functionalities;’;
Paragraph 4 is amended as follows:
point (c) is replaced by the following:
‘(c) the European Union Aviation Safety Agency, to ensure that safety, interoperability and environmental requirements and standards of the common projects are established in accordance with Regulation (EU) 2018/1139 of the European Parliament and of the Council [Regulation (EU) 2018/1139 of the European Parliament and of the Council of 4 July 2018 on common rules in the field of civil aviation and establishing a European Union Aviation Safety Agency, and amending Regulations (EC) No 2111/2005, (EC) No 1008/2008, (EU) No 996/2010, (EU) No 376/2014 and Directives 2014/30/EU and 2014/53/EU of the European Parliament and of the Council, and repealing Regulations (EC) No 552/2004 and (EC) No 216/2008 of the European Parliament and of the Council and Council Regulation (EEC) No 3922/91 (OJ L 212, 22.8.2018, p. 1).’;] and its implementing rules, and with the European Plan for Aviation Safety established in accordance with Article 6 thereof;
point (e) is replaced by the following:
‘(e) the European standardisation organisations and Eurocae, to facilitate and monitor industrial standardisation processes and the use of the resulting standards.’;
Article 9(2) is amended as follows:
point (j) is replaced by the following:
‘(j) ensuring appropriate coordination with National Supervisory Authorities;’;
the following point (k) is added:
‘(k) ensuring appropriate coordination with the European Union Aviation Safety Agency.’;
Article 11 is replaced by the following:
The deployment programme shall provide a comprehensive and structured work plan of all activities necessary to implement technologies, procedures and best practices required to implement common projects. The deployment programme shall specify the technological enablers for implementing the common projects.
The deployment programme shall define how the implementation of common projects shall be synchronised within the EATMN, taking into account local operational requirements and constraints.
The deployment programme shall constitute the references for all operational stakeholders required to implement common projects and for the management and implementation levels. The operational stakeholders shall provide the deployment manager with relevant information concerning the implementation of deployment programme. The deployment programme shall be part of the framework partnership agreement and, as such, all the beneficiaries shall commit to implement it.’.