A-CDM Implementation

...for the airport
  • Efficient utilisation of capacity and operational resources
  • Safety, punctuality and quality of service
  • Information sharing and common situational awareness
  • Link to the European ATM network
  • European programs (SESAR)The airport’s competitiveness
...for the network
  • Improvement and harmonization of data exchange between airports and Network Manager (NMOC)
  • Improvement of European airspace capacity and utilisation
  • Reduction of flight times and emissions
project-structure.png

 

Project philosophy
  • Small projectteam
  • Constant participation of all project partners
  • No Crewchanges
  • No-Blame-Culture
  • Open discussions during development of processes
  • Procedures define the system requirements  (NOT: Systems define procedures!)
  • From pilots point of view the Airport CDM@FRA procedure has to work the same way as e.g. the procedures of Munich, Paris, Brussels or Barcelona.

The main challenges of the A-CDM@FRA Implementation Project were:

  • The project structure involving different parties with differing goals
  • Necessity to change the fundamental understanding of the departure planning process (pre departure sequence versus first come first serve)
  • A very tight time schedule due to other predetermined airport projects in connection with only limited resources available
  • Substantial adaptation of the system‘s architecture with only a small time frame for the implementation in addition to the requirement of having no adverse effects on operations

The objective of the three months trial operations phase was to introduce all local partners involved to the A-CDM procedure and to test the supporting systems. The data exchange to the Network Management Unit in Brussels via DPI was initially tested by the CFMU test system. Because of the strong procedure adherence by all stakeholders and high quality of Target Takeoff Times (TTOT) transmitted to the CFMU, the permanent connection to the CFMU live system could be realized on first of February 2011, 9 days earlier than scheduled.


Objectives of trial operation phase

  • Local implementation of A-CDM procedure at FRA: A-CDM process will be standard procedure
  • Connection to European ATFM network: Several testing phases with CFMU (network management unit)
1. Preparations
trail_operations_1.png

 

Preceding activities:

  • Fraport and DFS OPS staff training and introduction of new IT-system applications completed
  • Communication with customers and users, publications and documentation are ensured:
    • Brief Description, AIC, customer guidelines, information, homepage
    • Support office will be established for trial operation phase
  • Customers and users prepare for trial operation phase
2. Local trial OPS/ CFMU test
trail_operations_1.png

 

Trial requirements and implementation:

  • Fraport and DFS OPS staff training successfully completed
  • Necessary IT-systems have been tested and are available
  • Support office is available for customers and users
  • Quality control and reliability based on KPI concept
  • Involvement of customer and user  e.g.:
    • TOBT responsibility
    • A-CDM alerts
3. Local trial OPS/ CFMU live test
trail_operations_1.png

 

Main focus:

  • Compliance with procedure
  • Observance of quality standards as required by CFMU
  • Connection to CFMU live system
4. Transition phase / CFMU live
trail_operations_1.png

 

From trial OPS to regular OPS:

  • Local A-CDM procedure + permanent CFMU live connection
  • Smooth transition from trial OPS to regular OPS is ensured
  • AIP publication
5. Full operations
trail_operations_1.png

 

Regular operation and basic expectations:

  • A safe, stable and efficient traffic flow will be ensured
  • Implementation of A-CDM as a standard procedure at FRA
  • Connection of  A-CDM@FRA to European ATFM  network
  • Quality of process and results: no deterioration of performance compared to previous operation (before A-CDM)
  • Permanent quality control and reliability checks by reporting system
  • Positive trend in procedural compliance and IT system performance