The AOP is a single, common and collaboratively agreed rolling plan available to all airport stakeholders whose purpose is to provide common situational awareness and to form the basis upon which stakeholder decisions relating to process optimization can be made. The AOP can be implemented in two steps: Initial AOP (iAOP) and Extended AOP, as described in objectives AOP11.1 and AOP11.2.

The collaborative NOP is the continuous data exchanges between the Network Manager and operational stakeholder systems in order to cover the entire flight trajectory lifecycle and to reflect priorities as required.

In order to improve the European ATM network performance, notably capacity and flight efficiency through exchange, modification and management of trajectory information there is a clear need for information sharing between the AOP and the NOP. The initial AOP/NOP integration is the technical data layer for the collaborative NOP information sharing.

The integration of AOP and NOP provides a rolling picture of the network and airport situation used by stakeholders to prepare and update their plans and their inputs to the network CDM processes, with a focus on the availability of shared operational planning and real-time data.

The iAOP/NOP integration focuses on exchanging between Airports/Airports Operational stakeholders’ systems and NM systems the Arrival Planning Information (API) and Departure Planning Information (DPI) messages; those messages are an add-on to DPI messages currently provided by CDM Airports. The procedures to generate those messages and their detailed contents have to be defined in collaboration between the NM and the implementing stakeholders. NM has an implementation work plan with Airports in CEF projects for deployment of the Family.

Stakeholders also impacted are all the other involved airports stakeholders such as but not limited to:

• Aircraft operators
• Ground handlers
• De-icing handlers
• ANSPs
• MET services providers

System requirements:

• Network Manager systems shall handle arrival planning information and departure planning information from the iAOP via NM B2B services;
• In Airports, iAOP shall provide arrival and departure planning information to the NOP via NM B2B services. DPI messages might still be provided in ADEXP format until 2025, while P-DPI and API interfaces are available only via NM B2B services.
• Operational stakeholders’ ground systems shall be adapted to directly interface with Network Manager systems via NM B2B services.
• Arrival and departure planning information for iAOP/NOP integration consists of the following mandatory messages:
o P-DPI;
o DPI used in CDM process;
o General-API;
o The other API messages (e.g. TTO, TTA) are considered for optional deployment in the iAOP/NOP integration.

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