This Implementation Project aims at closing the gaps at 7 airports newly included in CP1 (Common Project 1), as Implementing Airports, in 2 SESAR Deployment Programme (SDP) families, with target date for implementation 31.12.2027: SDP Family 2.2.2 “Extended AOP” (Airport Operating Plan) and SDP Family 4.4.1 “AOP/NOP Integration”(Airport Operations Plan/ Network Operations Plan)

Implementation of SDP Family 2.2.2 “Extended AOP” (including, as a pre-requisite, Initial AOP) and SDP Family 4.4.1 “AOP/NOP integration” (including the Initial AOP/NOP Information Sharing) will be done in close cooperation with Network Manager as Implementation Project Partner. By now, Implementing Airports have crossed initial level of SESAR solutions deployment, as six of them are Airport Collaborative Decision-Making (A-CDM) airports and one is becoming A-CDM (Airport Collaborative Decision-Making) in 2023. Being A-CDM airport is a pre-requisite for SDP Families 4.2.2 and 4.4.1. The IP aims to implement full scope of ATM (Air Traffic Management) Functionalities for SP Families 2.2.2 and 4.4.1 as requested by CP1 and in detail elaborated within SDP.

The WP is subdivided into 3 Sub-WPs:

• WP2.1 – Family 2.2.2 “Extended AOP” – the Airport Operations Plan (AOP) is a rolling plan that interacts with services, systems and stakeholders gathering information from several systems. The AOP must provide all the information that is relevant for the network to the network operations plan (NOP) in real time. The AOP supports landside and airside operations at airports with an increased scope of data sharing between the airport and Network Manager building on the available A-CDM supporting systems. The AOP must support the steering, monitoring, managing and post-post operations services by improving the overall operational efficiency and increasing resilience of the airport and of the network to disruptions such as adverse weather conditions, closure of a runway and security alerts. In order to implement an AOP, one of the fundamental prerequisites is a functional A-CDM. Therefore, all involved airports in this proposal have completed its implementation (with Athens putting it into operations in 2023).
As the Implementing Airports under the scope of this proposal are not, according to CP1, obliged to implement iAOP (initial AOP) in a separate intermediate step by the end of 2023, their objective is to implement full scope of this family (iAOP and extended AOP) by the implementation target date of 31.12.2027. Therefore, the activities to be performed by each one of the airports are similar in terms of data integration, operational elements and airport performance services to reach the extended AOP. Task 2 to 8 - ''Specific Airport'' – SDP Family 2.2.2: the specific task for every Implementing Airport related to SDP Family 2.2.2 implementation. This will include the full scope of activities as defined in SDP regarding implementation of particular Deployment Milestones (DMs).

• WP2.2 – Family 4.4.1 “AOP/NOP Integration” –As part of the evolution of processes and procedures, new data elements (subject to maturity and agreement of content) will be shared and also negotiated between AOP and NOP. These might be integrated in addition to the information that is shared in the iAOP-NOP information exchange, which is a prerequisite of AOP/NOP integration. The processes, procedures and underlying concepts for the creation and integration will have to be agreed upon and/or adapted. The deployment of SDP Family 4.4.1 at the 6 airports (Milan Linate Airport is addressing the issue of AOP-NOP integration within another ongoing project focused on Milano Malpensa Airport) builds on project 2015_113_AF4 “AOP-NOP” (Action 2015-EU-TM-0196-M), 2016_131_AF4 "AOP-NOP integration
- extended implementation" (Action 2016-EU-TM-0117-M) and 2017_052_AF4 “AOP-NOP integration – extended implementation" (Action 2017 -EU-TM-0076-M)
The first objective of SDP Family 4.4.1 is to enable the system-to-system exchanges between a local AOP and the NOP (NM systems) beyond the current A-CDM time horizon as part of the initial AOP/NOP information sharing. The systemto- system exchanges are realized through the implementation of additional DPI (Departure Planning Information) on top of A-CDM ones, the Predicted Departure Planning Information (P-DPI) exchange before the time horizon of the A-CDM process (Estimated Off Block Time (EOBT) - 3 hours) and implementation of General Arrival Planning Information (G-API) as to improve pre-tactical and tactical planning. The DPI exchanges currently done via Aeronautical FixedTelecommunication Network (AFTN) need to be moved to Network Manager business-to-business (NM B2B) services.
The second objective of SDP Family 4.4.1 is to define the new data elements that might be shared, negotiated between AOP and NOP and to integrate them for the exchange. For this scope, detailed milestones and deliverables are set up in the proposal. The system-to-system exchanges shall be possible within the System-Wide Information Management (SWIM) yellow profile, i.e. exchange via NM B2B services.

• WP2.3 – Project Management – This task, allocated to Letiste Praha A.S. (PRG), will consist in coordinating the participating partners ensuring sound and efficient dialogue is taking place to meet project deadlines and objectives.
This task, which lasts for the entirety of the project, focuses on the project management tasks including project definition, organization, resources and effort assignment, risk management, project control and monitoring. The project manager will establish a reporting mechanism to have direct visibility on the project progress through the achievement of previously defined milestones. Standardized and regular weekly/monthly reporting will be established, including: identification of deviations and countermeasures, monitoring of implementation progress, detailed planning, strategic management and action plans to solve open issues.

Taking into account SESAR performance assessments (PARs) and previous AOP/NOP projects under deployment, AOP/ NOP integration provides for the following performance benefits:
• Increased traffic predictability, which enhances capacity available in the planning phase.
• Increased ATCO productivity (indirect benefit).
• Cost-efficiency: no Aeronautical Fixed Telecommunication Network (AFTN) or Société Internationale de
Télécommunications Aéronautiques (SITA) connections required any more. Significant operating cost reduction through better predictability of arrival runway capacity, which reduces airborne and taxi-out holdings. This generates time savings and fuel saving.
• Reduction of reactionary delays and reactionary flight cancellations at the destination airport.
• AOP/NOP integration will provide benefits to airports through an improved information flow concerning arrival flights,
and to en-route and TMA units through a more accurate traffic picture in advance of real operations.
Based on previous CBAs and on airport expertise, the following quantified benefits are the first estimation (under the assumption of a full PCP implementation):
• An improved en-route capacity utilisation (1%)
• An improved runway capacity utilisation which results in a reduction of arrival airport ATFM delays (5%)
• A reduction of air transport non-ATM reactionary delays (-5%)