As part of the evolution of processes and procedures, new data elements will be shared and also negotiated between AOP and NOP. These will have to be integrated in addition to the information that is shared in the iAOP-NOP exchange. The processes, procedures and underlying concepts for the creation and integration will have to be agreed upon and/or adapted.

This will apply to arrival planning information (e.g. TTO/TTA via API), as well as departure information (e.g. P-DPI based on airport capacity information), and also enhanced management of capacities (e.g. diversion capabilities).

System requirements:

The Network Manager shall implement an increased integration of NOP and Airport Operations Plan (AOP) relevant information (for example, TTAs) resulting from a Cooperative Decision-Making Process (ref. Article 2.14 of the EC Regulation of the Network Function).

The AOP shall make available in real time to the NOP data that is appropriate and relevant to inform actions by Network Manager to adjust capacity in the network where appropriate. Such data shall be mutually agreed by the Network Manager and the Airport.

For airports with AOP, the NM shall share with the AOP the arrival demand and establish a collaborative decision-making process at local ATFM level to allow amendments to the TTAs based on the AOP.

AOP system requirements:

• The AOP systems must consume and process the flight updates published by NM via the NM B2B Services;
• The AOP systems must provide to NM the Extended Departure Planning Information via the NM B2B Services;
• The AOP systems must provide to NM the Arrival Planning Information via the NM B2B Services;
• If bilaterally agreed between NM and concerned airports and defined in respective ICD, the AOP systems should be capable of providing additional airport information (runway configurations, airport performance measurement) to NM.

NM system requirements:

• The NM system must be upgraded to process the information provided by the AOP system concerning the Extended DPI and API;
• The NM system must provide the flight updates information necessary to the AOP systems;
• If bilaterally agreed between NM and concerned airports and defined in respective ICD, the NM systems must be capable of integrating additional airport information (runway configurations, airport performance measurement).

NOTE FOR MILITARY AUTHORITIES: It is the responsibility of each military authority to review this Objective IN ITS ENTIRETY and address each of the SLoAs that the military authority considers RELEVANT for itself. This has to be done on top and above of the review of "MIL" SLoAs which identify actions EXCLUSIVE to military authorities.

Edition

2022

Stakeholders

Air Navigation Service Provider / Airport Operator / Network Manager

Type

CP1

Scope

Airport

Status

Active