2017_052_AF4

AOP-NOP Integration - Extended Implementation

Timeline

2014
2015
2016
2017
2018
2019
2020
Jan. '20OngoingDec. '21

Implementing Partners

Leader: EUROCONTROL
Contributor: Rome Airport
Contributor: Manchester Airport
Contributor: Dusseldorf Airport
Contributor: Nice Airport
Contributor: Stansted Airport
Contributor: Milan Airport
Contributor: Vienna Airport

Description

This implementing project builds on project 2015_113_AF4 AOP-NOP (Action 2015-EU-TM-0196-M) and 2016_131_AF4 ""AOP-NOP integration - extended implementation"" (Action 2016-EU-TM-0117-M), expanding the scope to other airports part of the Family 4.2.4 implementation area.

The main objective of this Implementing project is to enable the system to system exchanges between a local AOP and the NOP (NM systems) beyond the current A-CDM. This willl be realised through the implementation of the Predicted Departure Planning Information (P-DPI) exchange before the time horizon of the A-CDM process Estimated Off Block Time (EOBT -3hrs) as to improve pre-tactical planning. This exchange shall be possible within the SWIM yellow profile, i.e. exchange via B2B web-services.

Specific objectives:
The project specifically aims to focus on the data exchange for efficient cooperation between NMOC and local collaborative structures for improved Network Management.
In particular, it will:
a) review and refine the intial AOP-NOP integration Concept and related information exchanges as produced in 2015_113_AF4 AOP-NOP and 2016_131_AF4 to ensure harmonisation across all airports;
b) adapt system change requirements for processing the exchanged data in NM and setting up requirements for airport systems of different airport types;
c) develop and deploy the different systems adaptation to allow fully tested AOP-NOP interfaces between NM and the participating airports.

Note that the project will require coordination through common meetings / workshops particularly with respect to tasks 01 and 02 (hence travel costs associated). Internal organisation of airports( work may also require some level of travel for their own tasks related to requirements, implementation and testing)

Expected Results:
AOP-NOP Information sharing as described in the family 4.2.4 documentation is operational between the participating airports and the Network Manager.
The project is within the scope of NSP and NOP and in particular it links to NSP: SO 4/3 SO 06/2; and SO 6/4.

Performance Benefits:
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 of some € 25 million on top of 2015_113_AF4 and 2016_131_AF4 AOP-NOP integration projects.

  • 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%) and air transport non-ATM reactionary cancellations (- 0.5%)."

Additional Information

  • Project Type: Network Manager
  • CEF Call Year: 2017
  • Civil/Military: Civil
  • Multistakeholder: Yes
  • Main AF: AF4 - Network Collaborative Management
  • Sub AF: S-AF 4.2 - Collaborative NOP
  • 0