Objectives:
The objective of this Work Package is to close the following implementation gaps:
- SDP Family 2.2.2 “Extended AOP” for Amsterdam Schiphol (AMS), Barcelona El Prat (BCN), Berlin Brandeburg (BER – only on ANSP’s side), Brussels National (BRU), Copenhagen Kastrup (CPH), Dublin Airport (DUB), Dusseldorf International (DUS – only on ANSP’s side), Frankfurt International (FRA), Adolfo Suarez - Madrid Barajas (MAD), Milan-Malpensa (MXP), Munich Franz Josef Strauss (MUC), Nice Cote D’Azur (NCE), Palma de Mallorca Son Sant Joan (PMI), Paris CDG (CDG), Paris-Orly (ORY), Rome Fiumicino (FCO), Stockholm Arlanda (ARN), and Vienna Schwechat (VIE).
- SDP Family 4.4.1 “AOP/NOP integration” for Amsterdam Schiphol (AMS), Barcelona El Prat (BCN), Berlin Brandeburg (BER – only on ANSP’s side), Brussels National (BRU), Copenhagen Kastrup (CPH), Dublin Airport (DUB), Dusseldorf International (DUS – only on ANSP’s side), Frankfurt International (FRA), Adolfo-Suarez Madrid Barajas (MAD), Milan-Linate (LIN), Milan-Malpensa (MXP), Munich Franz Josef Strauss (MUC), Nice Cote D’Azur (NCE), Palma de Mallorca Son Sant Joan (PMI), Paris CDG (CDG), Paris-Orly (ORY), Stockholm Arlanda (ARN), and Vienna Schwechat (VIE).

The work plan consists of the following sub-work packages (sub-WPs) with their own specific objectives:
- Sub-WP 2.1 – Work Package management & coordination- related to WP management and coordination activities.

- Sub-WP 2.2 – Family 2.2.2 Extended AOP-The ‘extended Airport Operations Plan (eAOP)’ supports landside and airside operations at airports with an increased scope and sharing of data between the airport and the ‘Network Manager (NM)’. The ‘extended Airport Operations Plan (eAOP)’ is the fundamental tool supporting operational services by improving the operational efficiency and increasing resilience of the airport and the network to resist disruptions such as but not limited to: adverse weather conditions, closure of a runway, security alerts, etc.

The ‘extended Airport Operations Plan (eAOP)’ comprises the following four performance services:
o Steer Airport Performance Service
o Monitor Airport Performance Service
o Manager Airport Performance Service
o Post-Operations Analysis Service

This Sub-WP 2.2 builds upon the funded Implementation Project 2017_022_AF2 “Synchronised stakeholder decision on process optimisation at airport level” (Action No 2017-EU-TM-0076-M) and 2022_022_AF2_AF4 “BEACON” ( 22-EU-TG-CLEANATM)
- Sub-WP 2.3 – Family 4.4.1 AOP/NOP integration- The Sub-WP 2.3 aims to focus on the data exchange for efficient cooperation between NM systems and local collaborative structures for improved Network Management. In particular, it will:
o Implement the mature elements of Family 4.4.1 scope for 18 airports in Commission Implementing Regulation (EU) 2021/116;
o Define, validate and integrate AOP-NOP interfaces between the 'Network Manager (NM)' and 19 airports mentioned in Regulation (EU) 2021/116
o Setting up requirements for airport systems to comply with the agreed data exchange between the ‘Airport Operations Plan (AOP)’ and the ‘Network Manager (NM)’.
The activities will require coordination through meetings/workshops particularly with respect to tasks for the definition of integration data and procedures (hence travel costs associated) between the ‘Network Manager (NM)’ and the airports. Depending on the internal organisation of airports (including airport’s stakeholders), the work may also require to incur in travel arrangement costs.

Description:
Considering SESAR performance assessments (PARs) and previous IPs under deployment, the deployment of ‘Family 2.2.2 Extended AOP’ and ‘Family 4.4.1 AOP/NOP integration’ will provide 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 will generate time and fuel savings
- 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 ‘Cost-Benefit Analysis (CBAs)’ and on airport expertise, the following quantified benefits are a first estimation (under the assumption of a full CP1 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%)

The WP 2 builds upon the following funded Implementation Projects:
- 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)
- 2017_052_AF4 ”AOP-NOP integration – extended implementation” (Action 2017 -EU-TM-0076-M)
- 2022_022_AF2_AF4 “BEACON” ( 22-EU-TG-CLEAN ATM)