Timeline

2014
2015
2016
2017
2018
2019
2020
Feb. '17OngoingDec. '20

Implementing Partners

Leader: Dusseldorf Airport
Contributor: DFS

Description

Globally, the Implementation Project aims to set up the Initial Airport Operations Plan (AOP) in Düsseldorf Airport (DUS). Additionally, to the already implemented Initial DMAN, Electronic Flight Strips (EFS) and Basic A-CDM (Airport Collaborative decision Making), Düsseldorf Airport intends to close the gap on Initial AOP by implementing different system modules so that the Airport's Operational Database will be extended in relation to the actual status of the overall capacity and resources at the airport.

The AOP information shall be shared with the local stakeholders (Information Sharing - Common Situational Awareness). It shall be implemented to be ready for the AOP - NOP (Network Operations Plan) Connection (Family 4.2.4.) to ensure the positive impact on the network level (AOP-data sending to NOP implemented). By introducing the Demand Capacity Functionality and On-Time Key Performance Indicator the A-CDM performance assessment and reporting process will be improved/implemented.

After analysing the gaps within Initial AOP compared to the external requirements (SESAR definition) DUS airport will implement demand and capacity balancing functions, What If decision making supporting tools and On time Key Performance Indicators at Düsseldorf Airport.This will improve the common situational awareness and information sharing between the airport stakeholders (also within the DUS Airport Operations Center) and ATC about the operational status of the Airport. It will furthermore optimise the turnaround processes and general throughput to ensure improved ATM stakeholders’ planning processes. Together with the concerned stakeholders it must be defined what is operationally useful and feasible.

The implementation of the system modules includes:

  • Flight trajectory data: Information sharing related to Flight Progress Information Elements of an Inbound/Outbound/airport transit Trajectory to/from/at Airport.

  • Airport Resources data: Airside and landside resources such as runway capacity & configuration, or parking stands.

  • Local weather data: Information sharing related to MET Information Elements of airport.

The initial AOP is the basis for a later integration of the AOP into the NOP (Family 4.2.4.) which provides a rolling picture of the network situation used by stakeholders to prepare their plans and their inputs to the network CDM processes (e.g. negotiation of airspace configurations). Also receiving the NM (Network Manager) Information is planned to make sure to exchange the information with the operational stakeholders by means of defined cooperative network information services. The data exchange between AOP and NOP should be performed by using SWIM components in the future.

Countries involved

Additional Information

  • Project Type: Airport
  • CEF Call Year: 2016
  • Civil/Military: Civil
  • Multistakeholder: Yes
  • Main AF: AF2 - Airport Integration and Throughput
  • Sub AF: S-AF 2.1 Departure Management Synchronised with Pre-departure sequencing
  • Progress Percentage: 68%