AOP-NOP Integration Airports CDM Information Exchange 2016 Dr. Alexandra von Eckartsberg ACI Liaison Officer 21/10/2016
Integrating Airports with the Network Enables sharing of collected data Improves situational awareness Enables enhanced planning Improves predictability for better demand-capacity balancing Allows optimizing for airport performance at given capacity Allows optimizing for Network performance 2
Airport Operations Plan (AOP) Enhanced Airport Operational Database (AODB) Implementation of airport operations management decisions are reflected in the AOP data Single source of information for airport operational partners Contains most up to date status information on all Airport Transit View elements Contains single-flight and flow based planning information AOP Airport Slots A-CDM milestones Stands&Gates Capacity Plan Runway Configuration Plan TTA proposals etc. 3
AOP-NOP Integration AOP NOP AU APT GH Tower APOC Airport Slots A-CDM Milestones Stands&Gates Capacity& Event Plan Runway Configuration Plan TTA proposals etc. Flight Plans Flight Updates DPIs from Outstations Capacity& Event Plan (other airports) CTOTs Coordinated TTAs etc. AU ACC AOP needs input from its counterpart, the Network Operations Plan (NOP) and vice versa to give complete picture Strategic, pre-tactical and tactical data exchange Air traffic demand identification and consolidation (FLP) Airport capacity and event plan information Runway configuration plan Arrival and departure planning Information APOC & AOP/NOP Exchange 4
Data Exchange Technical Level Decision Making Communication Level Decision Making and Data Exchange Future Pretactical tactical AIRPORT Local Collaboration Airport Operator Airlines AIRPORT Local Collaboration Airport Operator Airlines Local ATC Ground Handlers Local ATC Ground Handlers AIRPORT AIRPORT AOP AOP NOP NOP 5
Data Exchange Technical Level Decision Making Communication Level Decision Making and Data Exchange Today, CDM as Basis Pretactical tactical AIRPORT Airport Operator Airlines AIRPORT Airport Operator Airlines Local Collaboration Local ATC Local ATC Ground Handlers AIRPORT AIRPORT Airlines Airport Operator Ground Handlers Airlines Airport Operator Local ATC 7
AOT APOC Task Force It was acknowledged that airport local collaboration is a necessary prerequisite for the integration of airport and Network operations APOC and other forms of ground coordination are the key Collaborative decisions are translated into coherent, consistent and reliable data contained in eth AOP that is exchanged with external partners 9
Task Force Goals Process layer Guidance for internal (Ground Coordinator, APOC, etc.) and external (, ) Collaboration Process Data layer Identify data elements that will benefit your operations Create three data packages for short-term, medium-term and long-term implementation AOP-NOP Exchange 10
Existing and New Data Use Cases Demand Information as DCB Input From NOP to AOP Provide ADES with Arrival Demand before Flight Plan Filing Provide ADES with Flight Plans Informing ADES on Arriving Flight Progress Informing ADES on Holdings Informing ADEP on ATFM slot 11
Existing and New Data Use Cases Demand Information as DCB Input From AOP to NOP Provide NM with Airport Slots Informing NM on Shifted Departure Times before Flight Plan Filing Informing NM on Departing Flight Progress Provide NM with Information on Arriving Flights Provide NM with Runway Configuration Plan Provide NM with Standard SID assignment per runway configuration 12
Existing and New Data Use Cases Capacity Information as DCB Input From AOP to NOP Provide NM with Runway Configurations Standard Capacities Provide NM with Runway Capacity Plan Report Diversion Capabilities to NM 13
Existing and New Data Use Cases DCB process From NOP to AOP Informing ADES on Original Arrival Demand (the wish prior to arrival regulation) Provide Airport with Response to TTA Request Provide ADEP with List of Adjacent ATFM Regulations for SID balancing From AOP to NOP Send TTA Request to NM Informing NM about Demand Reduction Request made to Airlines 14
Existing and New Data Use Cases Situational Awareness Info From NOP to AOP Provide Airports with Capacity Updates from Other Airports Provide Airports with List of En-Route and Destination Arrival Regulations From AOP to NOP Report Airport Events to NM Inform NM on Expected Average Departure Delay Inform NM about Adverse Weather Inform NM about De-Icing 15
Priorities Data Use Case Priorities (Package 1) Informing NM on Departing Flight Progress (DPIs) A-CDM Informing ADEP on Flight Departure Constraints Send TTA Request to NM Provide NM with Information on Arriving Flights (APIs) TTA Inform NM about De-Icing Report Airport Events to NM Informing ADES on Arriving Flight Progress Informing NM on Shifted Departure Times and not Operating Flights before Flight Plan Filing Extended Planning Horizon Provide NM with Runway Configuration Plan Provide Airport with Response to TTA Request 16
AOP-NOP Pilot Implementation INEA CEF call 2015 project three major airports (CDG, FRA, LHR) in cooperation with NM B2B SWIM implementation Definition of services an interfaces Baseline proposal for harmonization of AOP-NOP interface Operational AOP-NOP Integration by end of 2019 (min. Package 1) placing proposal in CEF call 2016 to expand implementation to additional airports!
Thank you! 18