Short overview for AOs and Ground Handlers DPI Messages Short overview for AOs and Ground Handlers Hans Koolen Expert ATFCM and Airport CDM 10/04/2017

Integration of an Airport and the ATM Network

Contents Introduction & General Overview Provision of DPI/CDM data to AOs Use of Local TOBT & TSAT with Provision of DPIs to NMOC DPI Summary and Benefits Overview This presentation has been developed by DFS and has been further extended by Eurocontrol/NMOC. Many thanks to Erik Sinz of DFS for making it available to all Eurocontrol Stakeholders.

Introduction & General Overview Agenda Introduction & General Overview

What does NMOC provide to the Airports? Flight Update Message (FUM) Contains Estimated LanDing Time (ELDT) and ETO over last route point. Sent at: ELDT – 3 hours or earlier if flight is airborne earlier ELDT change >= 5 min Important flight status changes Based upon: Flight plan data such as FPL, DLA, CHG DPI messages from Departure Airport Airborne data updates from ATC

General Overview DEPARTURE PLANNING INFORMATION (DPI) messages: Provide Flight data updates before take-off. Are received from CDM airports or ATC (TWR) systems Are an output of the locally established CDM process or TWR inputs Are sent from system to system (no extra human workload). Received by ETFMS via AFTN, SITA networks or B2B web services. Are sent between EOBT - 3 Hrs and Take-Off. Data that is typically not available from IFPS.

What do CDM Airports provide to the Network? Data that is only locally available at the airport Variable Taxi-Time (VTT) A Target Take Off Time (TTOT) based upon: Target Off-Block Time (TOBT) = handling finished/doors closed Target Start-up Approval Time (TSAT) = start-up approved by ATC Actual Off-Block Event (AOBT) = push-back/taxi start The selected SID The local TOBT The local TSAT The CDM ARCTYP The CDM REGistration

Who Provides Airport CDM data to the network? Operational EDDM EBBR LFPG LSGG EDDF EFHK EDDL LIML EGLL LSZH ENGM LFPO LIRF EDDB LEMD EKCH EDDS LIMC EGKK 22 Airports 31% of departures in NM Area LKPR LEBL LIPZ

Who Provides Airport CDM data to the network? Expected Operational in 2017-2018 ESSA EPWA LEPA LFLL EDDH EHAM EIDW LIRN LTBA LFMN LOWW LPPT ENBR ENZV ENVA LGAV 16 Airports more moving towards 47% of departures in NM Area

Who Provides Airport Adv ATC TWR data to the network? Operational Ukraine: UKBB Germany: EDDG, EDDW, EDDC, EDDE, EDDR UK: EGLC, EGPD, EGCC, EGSS, EGGW, EGPF, EGPH, EGGP Spain: LEAL France: LFMN 17 Airports representing 7% of departures in NM Area

Who Provides Airport Adv ATC TWR data to the network? Expected Operational in 2017 - 2018 UK: EGPE, EGTE, EGSH, EGAE, EGBE Spain: GCTS, LEMG, GCLP Czech Republic: LKTB, LKKV, LKMT 11 Airports more Leading to a total of 9% of departures in NM Area Under investigation UK: 15-20 airports more  target is 95% of UK departures to provide DPI to NMOC Spain: Possibly more airports after the first 4 The Netherlands: EHRD, EHBK, EHGG,… Italy: Olbia, Ciampino, …

How is the CDM data used by NMOC/ETFMS? To obtain more accurate traffic count predictions To display to NMOC users via: CHMI NOP Portal To re-distribute it to external data users via: DDS-to-AOs & DDS-to-ANSPs services Estimated Landing Times (ELDTs) to ADES B2B web services To adjust the CTOT to local available TOT To use de-icing info To adjust Flight Activation Monitoring (FAM) Improve flight plan consistency & planning: Reject DLA, CHG and CNL after AOBT File DLA or CHG on behalf of AO (optional future service) ELDT(FUM)

5 Events at ADEP provided by 5 DPI types At Verification Flight Plan EOBT with Airport Slot provide:  E-DPI (Early-DPI) At Creation & Update of TOBT provide:  T-DPI-t (Target-DPI-target) At TSAT Issue/Publication to NMOC provide:  T-DPI-s (Target-DPI-sequenced) At Actual Off-Block provide:  A-DPI (ATC-DPI) At any interruptions in flights’ progress and new TOT is not yet known provide:  C-DPI (Cancel-DPI)

When do CDM Airports provide Data to the Network? Estimated Landing Time (from NMOC to CDM Airport) F U M TURN-AROUND EOBT Take Off Out-station ELDT AOBT Inblock Start Ground handling Take- Off ATOT Final approach „TMO“ Lan-ding Ground handling Aircraft ready Start Up ASAT FPL - APT Slot (EOBT - 3hrs) EOBT-2h (CTOT issue) TSAT Issue (TOBT-40min to TSAT-10) TSAT TTOT TOBT Automatic calculation TOBT Taxiing AOBT+TT FPL/Schedule-Comparison Provision of TT, SID AO/Handler Readiness Provision of TOBT+TT ATC Readiness Provision of TSAT+TT Early-DPI Target-DPI-target Target-DPI-seq ATC-DPI Four main DPI types

Timing & Sequence of DPI Messages

Provision of CDM data to Agenda Provision of CDM data to The ATM Network Display in CHMI (for FMP, AO) Display in NOP Portal (for AO, GH, …) The NMOC’s DDS-to_AOs service (EFD message) (for AO) The Flight Update Message (FUM) to Airports of destination B2B web services (for Airports, AOs,…)

Provision of CDM data to AOs and Ground Handlers Agenda Provision of CDM data to AOs and Ground Handlers Display in CHMI

Last received Target Take Off Time (TTOT): EOBT-TOBT Discrepancy Where is the CDM Data in CHMI Flight List? Last received Target Take Off Time (TTOT): CDMSTATUS e = early - flight plan confirmed t = targeted - TOBT defined s = pre-sequence - in ATC pre-dep seq. a = actual off-block - taxiing c = cancel - CDM process interrupted IFPS Discrepancy in RED font REA Status if „R“ Airport Type: S = standard T = Adv ATC TWR C = CDM Airport De-Icing info: Blue background & “!“ IFPS Discrepancy: EOBT-TOBT Discrepancy

Where is the CDM Data in CHMI Flight Data Display? REA Status Airport Info IFPS Discrepancy: REGistration IFPS CDM Status Reason of last C-DPI Last received TTOT Airport Type TOBT TSAT

List of all sent and received messages ETFMS Oplog – message details List of all sent and received messages Selected Message

Provision of Airport CDM data to AOs and Ground Handlers Agenda Provision of Airport CDM data to AOs and Ground Handlers Display in NOP Portal

Last received Target Take Off Time (TTOT): TOBT, TSAT and TT columns Where is the CDM Data in NOP Flight List? CDMSTATUS e = early - flight plan confirmed t = targeted - TOBT defined s = pre-sequence - in ATC pre-dep seq. a = actual off-block - taxiing c = cancel - CDM process interrupted Last received Target Take Off Time (TTOT): TOBT, TSAT and TT columns De-Icing info: Blue background & “!“ IFPS Discrepancy in RED font REA status if „R“ Airport Type: S = standard T = Adv ATC TWR C = CDM Airport

Where is the CDM Data in NOP Flight Data Display? IFPS Discrepancy: ARCTYP IFPS Airport Info REA status Airport Type Last received TTOT TSAT CDM Status TOBT C-DPI reason

Provision of Airport CDM data to AOs and Ground Handlers Agenda Provision of Airport CDM data to AOs and Ground Handlers The NMOC’s DDS-to-AOs service (EFD messages)

DDS-to-AOs service (EFD messages) The NMOC’s DDS-to-AOs service is intended as a datafeed for AOs flight following applications It is based upon the distribution of EFD messages EFD messages contain: Flight identification fields such as ARCID, ADEP, ADES, EOBT, IFPLID,… The flight status The 4D flight profile… CDM data received from the CDM Airport AOs can receive the service up on request

DDS-to-AOs service (EFD messages) EFD messages contain the following Airport CDM data elements: TTOT – Target Take Off Time This is the most accurate TOT before take-off. It is in the ETO-field of the ADEP in the RTEPTS list. TAXITIME This is the Variable Taxi-Time (VTT) as calculated by the CDM Airport system. SID This is the SID provided by the Airport CDM system. It can be found in the RTEPTS list field. DEPAPTYPE The Airport Type specifies if the departure airport is a CDM Airport or an other type. CDMSTATUS The CDMSTATUS is an indicator to identify the progress of the flight in the CDM Turnaround process. DEPREG The DEPREG field contains the REGistration received from the CDM Airport. DEPARCTYP The DEPARCTYP field contains the AIRCRAFT Type received from the CDM Airport. IFPSDISCREPANCY The IFPSDISCREPANCY field contains the type of discrepancy between IFPS data and DPI data. DEPSTATUS The DEPSTATUS field is present if the flight will be de-iced.

Provision of Airport CDM data to AOs and Ground Handlers Agenda Provision of Airport CDM data to AOs and Ground Handlers The Flight Update Message (FUM)

Flight Update Message (FUM) The FUM is mainly used to provide Estimated Landing Times (ELDTs) to Airports of Destination of the flight. The Airports use it to obtain an early estimation of the landing time in order to optimize the turn-around-process of the aircraft. FUM messages contain: Flight identification fields such as ARCID, ADEP, ADES, EOBT, IFPLID,… The flight status CDM data received from the CDM Airport An airport can receive the service up on request More information can be found on: http://www.eurocontrol.int/articles/airport-data-integration-dpi-and-fum The Flight Progress Messages document

Flight Update Message (FUM) FUM messages contain the following Airport CDM data elements: DEPAPTYPE The Airport Type specifies if the departure airport is a CDM Airport or an other type. CDMSTATUS The CDMSTATUS is an indicator to identify the progress of the flight in the CDM Turnaround process. Note that the Estimated LanDing Time (ELDT) for the airport of destination in the FUM is updated with the TTOT that is in the DPI message from the departure airport.

Provision of Airport CDM data to AOs and Ground Handlers Agenda Provision of Airport CDM data to AOs and Ground Handlers B2B web services

B2B Web Services in NMOC What is the B2B web-service? System-to-system interfaces Promotes accurate data sharing and easy access to services Promotes simplification of processes, both for NMOC and its customers Standards-based Web Services (SOAP), REST-like Secure Authentication (PKI), Authorisation, Encryption Multi-version support Preparing for SWIM infrastructure, basis for the SESAR architecture

B2B Web Services Formal service definitions (modelled) Publication: B2B Reference Manuals, WSDL, XSD and examples Provision of a pre-operational platform for customer testing OPS quality, always available, but only office hours support Access request via NMOC web site Usage subject to agreements and terms and conditions => Using the NMOC B2B Web Services external stakeholders can integrate the NMOC services with their business applications.

B2B Web Services The NMOC’s B2B web service dedicated to Flights Data (Flight Management Service) is intended to provide NMOC data to AOs for various purposes This B2B Web Services offer access to the following flight data: Flight identification fields such as ARCID, ADEP, ADES, EOBT, IFPLID,… The flight status The 4D flight profile… CDM data received from the CDM Airport Technical details are available in the dedicated Technical Documentation: B2B Services General Reference Manual B2B Flight Services Reference Manual Samples (SOAP and non SOAP)

B2B Web Services The B2B Web Service providing access to flights details include the following Airport CDM data elements: CDMSTATUS The CDMSTATUS is an indicator to identify the progress of the flight in the CDM Turnaround process. DepartureAirportType The Airport Type specifies if the departure airport is a CDM Airport or an other type. TargetTakeOffTime (TTOT) The TTOT of each DPI-type is available. TaxiTime This is the Variable Taxi-Time (VTT) as calculated by the CDM Airport system. IFPSDiscrepancies The IFPS discrepancy fields contains the type of discrepancy between IFPS data and DPI data. AircraftType The AircraftType field contains the Aircraft Type received from the CDM Airport. RegistrationMark The RegistrationMark field contains the REGistration received from the CDM Airport. DepartureStatus The DepartureStatus field specifies if the flight will be de-iced.

B2B Web Services AOs can have access on request by filling in the existing online NMOC Service Request Form. Direct link: http://www.eurocontrol.int/network-operations/service-request (section 4). Customer support (contact): Network Manager Customer Support E-mail: nm.customersupport@eurocontrol.int More information can be found online: OST Shared space "B2B - Web Services“ (registration needed). Direct link (after OSO login) https://extranet.eurocontrol.int/http://beid.eurocontrol.be:8980/Members/irc/eurocontrol/b2bws/home Technical Documentation B2B Services General Reference Manual B2B Flight Services Reference Manual Samples (SOAP and non SOAP) Newsgroup Allow to share problems/solutions All faced issues during Pilot phase are present Good starting point for newcomer

Non-Regulated Flights Agenda Local TOBT, TSAT and TTOT Calculation with issue of T-DPI-t and T-DPI-s messages Non-Regulated Flights

Local TSAT+TTOT Calculation – Non-Regul Flight FULL Departure Capacity Capacity 60/60min 12:13 12:11 12:09 12:07 12:05 12:17 12:03 12:01 TTOT 12:15 12:19 12:21 12:14 12:12 12:10 12:08 12:06 12:04 12:20 12:16 12:18 12:22 12:02 12:00 TTOT DPI Pre Departure Sequence DLH 1KM TOBT: 12:00 EXOT 15 Min. TSAT: 12:00 DLH 2ES TOBT: 12:02 EXOT 17 Min. TSAT: 12:02 DLH 3KW TOBT: 12:00 EXOT 21 Min. DLH4SH TSAT: 12:00 DLH5SF DLH6HF T-DPI-s TTOT 12:15 NMOC 12:15 DLH1KM DLH7RW T-DPI-s TTOT 12:19 NMOC DPI Status Sequenced 12:19 DLH2ES TSAT Issue = TOBT-40min 12:21 DLH3KW T-DPI-s TTOT 12:21 NMOC

Local TSAT+TTOT Calculation – Non-Regul Flight REDUCED Departure Capacity Capacity 20/60min 12:39 12:33 12:27 12:21 12:15 12:51 12:09 12:03 TTOT 12:45 12:57 13:03 12:42 12:36 12:30 12:24 12:18 12:12 13:00 12:48 12:54 13:06 12:06 12:00 TTOT DPI Pre Departure Sequence DLH 1KM TOBT: 12:30 EXOT 15 Min. TSAT: 12:42 DLH400 LOT378 SAS676 AZA407 DLH5SF Runway Slot already taken 12:45 DLH7RW DLH4SH Next available Runway Slot DLH5SF DLH6HF T-DPI-s TTOT 12:57 NMOC DPI Status Sequenced 12:57 DLH1KM TSAT Issue = TOBT-40min

All messages in CHMI – Non-Regul Flight (1/3) Early DPI Standard transmission EOBT-3h Basic Requirement! 1. Target DPI Status: Target Standard Transmission at EOBT-2h TTOT= „No CTOT Before“ 2. Target DPI Status: Target Reason: Change of TTOT (Parameter 5min or more) TOBT:14:25 IMDPI DLH6CW EDDMYDYE @AFTN 0005334022009010711150500409603870000000264Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/07 11:15:00. Message description: -TITLE DPI -DPISTATUS EARLY -ARCID DLH6CW -ADEP EDDM -ADES LSGG -EOBT 1415 -EOBD 090107 -TTOT 1434 -SOBT 1415 -SID AMPEG3S -TAXITIME 0019 -ARCTYP B735 -REG DABII -ORGN EDDMYDYE IMDPI DLH6CW EDDMYDYE @AFTN 0005334022009010712150400411568040000000267Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/07 12:15:00. Message description: -TITLE DPI -DPISTATUS TARGET -ARCID DLH6CW -ADES LSGG -ADEP EDDM -EOBT 1415 -EOBD 090107 -TTOT 1434 -SID AMPEG3S -TAXITIME 0019 -ARCTYP B735 -REG DABII -ORGN EDDMYDYE IMDPI DLH6CW EDDMYDYE @AFTN 0005334022009010713260400413840410000000267Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/07 13:26:00. Message description: -TITLE DPI -DPISTATUS TARGET -ARCID DLH6CW -ADES LSGG -ADEP EDDM -EOBT 1415 -EOBD 090107 -TTOT 1444 -SID AMPEG3S -TAXITIME 0019 -ARCTYP B735 -REG DABII -ORGN EDDMYDYE Target DPI Status TTOT TTOT TTOT

All messages in CHMI – Non-Regul Flight (2/3) 3. Target DPI Status: Target Reason: change of TTOT (Parameter = 5min or more) TOBT: 14:23 4. Target DPI Status: Target Reason: change of TTOT TOBT: 14:18 (advanced) 5. Target DPI Status: Sequenced Standard transmission at TSAT-issue (TOBT-40min) TOBT: 14:18 TSAT: 14:18 IMDPI DLH6CW EDDMYDYE @AFTN 0005334022009010713393600414276620000000267Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/07 13:39:00. Message description: -TITLE DPI -DPISTATUS SEQ -ARCID DLH6CW -ADES LSGG -ADEP EDDM -EOBT 1415 -EOBD 090107 -ATTOT 1434 -SID AMPEG3S -TAXITIME 0016 -ARCTYP B735 -REG DABII -ORGN EDDMYDYE IMDPI DLH6CW EDDMYDYE @AFTN 0005334022009010713321500414036860000000267Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/07 13:32:00. Message description: -TITLE DPI -DPISTATUS C -ARCID DLH6CW -ADES LSGG -ADEP EDDM -EOBT 1415 -EOBD 090107 -TTOT 1439 -SID AMPEG3S -TAXITIME 0016 -ARCTYP B735 -REG DABII -ORGN EDDMYDYE IMDPI DLH6CW EDDMYDYE @AFTN 0005334022009010713393600414276100000000267Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/07 13:39:00. Message description: -TITLE DPI -DPISTATUS TARGET -ARCID DLH6CW -ADES LSGG -ADEP EDDM -EOBT 1415 -EOBD 090107 -TTOT 1434 -SID AMPEG3S -TAXITIME 0016 -ARCTYP B735 -REG DABII -ORGN EDDMYDYE Sequenced DPI Status TTOT Modified TTOT

All messages in CHMI – Non-Regul Flight (3/3) 6. Target DPI Status: Sequenced Reason: Change of TTOT TOBT: 14:13 TSAT: 14:13 1. ATC DPI Standard transmission: AOBT-Actual Off Block ASAT: 14:12 AOBT: 14:13 1. FSA Standard transmission: Take Off IMDPI DLH6CW EDDMYDYE @AFTN 0005334022009010714084100415155740000000267Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/07 14:08:00. Message description: -TITLE DPI -DPISTATUS SEQ -ARCID DLH6CW -ADES LSGG -ADEP EDDM -EOBT 1415 -EOBD 090107 -TTOT 1427 -SID AMPEG2E -TAXITIME 0014 -ARCTYP B735 -REG DABII -ORGN EDDMYDYE IMDPI DLH6CW EDDMYDYE @AFTN 0005334022009010714135700415315430000000253Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/07 14:13:00. Message description: -TITLE DPI -DPISTATUS ATC -ARCID DLH6CW -ARCTYP B735 -REG DABII -ADEP EDDM -EOBT 1415 -EOBD 090107 -TTOT 1427 -TAXITIME 0014 -ADES LSGG -SID AMPEG2E -ORGN EDDMYDYE IMFSA DLH6CW EDMMZQZX @AFTN 0005334022009010714252500415661520000000211Received from: EDMMZQZX @AFTN. Est. Xmit at: 09/01/07 14:25:00. Message description: -TITLE FSA -ARCID DLH6CW -ADEP EDDM -ADES LSGG -ARCTYP B735 -EOBT 1415 -EOBD 090107 -POSITION -TO 1425 -ADID EDDM TTOT TTOT ATOT

Agenda Local TOBT, TSAT and TTOT Calculation with issue of T-DPI-t and T-DPI-s messages Regulated Flights

Local TSAT+TTOT Calculation – Regulated Flight FULL Departure Capacity Capacity 60/60min 12:43 12:41 12:39 12:37 12:33 12:31 TTOT 12:51 12:47 12:49 12:35 12:45 12:44 12:42 12:40 12:38 12:36 12:34 12:50 12:46 12:48 12:52 12:32 12:30 TTOT DPI Pre Departure Sequence DLH 1KM TOBT: 12:20 EXOT 15 Min. TSAT: 12:30 CTOT: 12:45 T-DPI-t No CTOT before Information: 12:35 12:35 DLH1KM NMOC DPI Status target T-DPI-s TTOT 12:45 12:45 12:45 NMOC NMOC CTOT NMOC TSAT Publi to NMOC = TSAT-10min Pilot/Handler receive TSAT based on CTOT

Local TSAT+TTOT Calculation – Regulated Flight REDUCED Departure Capacity Capacity 20/60min 12:39 12:33 12:27 12:21 12:09 12:03 TTOT 12:57 13:03 12:45 12:51 12:15 12:42 12:36 12:24 12:18 12:12 12:48 12:54 13:06 12:06 12:00 TTOT 12:30 13:00 DPI Pre Departure Sequence DLH 4SH TOBT: 12:00 EXOT 15 Min. OptimalTSAT: 12:15 TSAT: 12:45 CTOT: 13:00 12:15 DLH400 Runway Slot already taken LOT378 Next available Runway Slot SAS676 AZA407 DLH7RW T-DPI-s TTOT 12:30 DLH4SH 12:30 NMOC DPI Status Sequenced DLH1KM DLH5SF DLH6HF OptimalTSAT Publi to NMOC = TOBT-40 Pilot/Handler receive TSAT based on CTOT 13:00 NMOC NMOC CTOT

All messages in CHMI – Regulated Flight (1/4) Early DPI - Standard transmission at EOBT-3h - Basic requirement 1. Target DPI - Status: Target - Standard transmission at EOBT-2h Slot Allocation Message (SAM) TTOT of last DPI is used as “No CTOT before“ information OMSAM DLH3354 EDDZYNYS @AFTN AA700647240004978712009010516250000355288440000000459Sent to: EDDZYNYS @AFTN EDMMZQZX @AFTN EDDAYGLZ @AFTN EDDMYQYX @AFTN LDZOZQZX @AFTN EDDFDLHJ @AFTN QLHLCCL @SITA FRAP9LH @SITA QLH5YLH @SITA MUCOGLH @SITA. Message description: -TITLE SAM -ARCID DLH3354 -IFPLID AA70064724 -ADEP EDDM -ADES LTBA -EOBD 090105 -EOBT 1825 -CTOT 1844 -REGUL LOWES05A -TAXITIME 0019 -REGCAUSE CE 81 IMDPI DLH3354 EDDMYDYE @AFTN 0004978712009010515250400353416300000000264Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/05 15:25:00. Message description: -TITLE DPI -DPISTATUS EARLY -ARCID DLH3354 -ADEP EDDM -ADES LTBA -EOBT 1825 -EOBD 090105 -TTOT 1844 -SOBT 1825 -SID CHIEM4S -TAXITIME 0019 -ARCTYP A320 -REG DAIPU -ORGN EDDMYDYE IMDPI DLH3354 EDDMYDYE @AFTN 0004978712009010516250200355289100000000267Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/05 16:25:00. Message description: -TITLE DPI -DPISTATUS TARGET -ARCID DLH3354 -ADES LTBA -ADEP EDDM -EOBT 1825 -EOBD 090105 -TTOT 1844 -SID CHIEM4S -TAXITIME 0019 -ARCTYP A320 -REG DAIPU -ORGN EDDMYDYE TTOT TTOT CTOT

All messages in CHMI – Regulated Flight (2/4) 1. Slot Revision Message (SRM) - TTOT of last DPI is the “No CTOT before“ information 2. Slot Revision Message (SRM) - TTOT of last Target DPI-t remains valid 2. Target DPI Status: Target - Standard transmission: 1. TSAT - DPI Status is unchanged TOBT: 18:25 TSAT: 18:39 (Basis=CTOT) OMSRM DLH3354 EDDZYNYS @AFTN AA700647240004978712009010517301200357344590000000462Sent to: EDDZYNYS @AFTN EDMMZQZX @AFTN EDDAYGLZ @AFTN EDDMYQYX @AFTN LDZOZQZX @AFTN EDDFDLHJ @AFTN Message description: -TITLE SRM -ARCID DLH3354 -IFPLID AA70064724 -ADEP EDDM -ADES LTBA -EOBD 090105 -EOBT 1825 -NEWCTOT 1853 -REGUL LOWES05A -TAXITIME 0019 -REGCAUSE CE 81 OMSRM DLH3354 EDDZYNYS @AFTN AA700647240004978712009010517435000357790040000000462Sent to: EDDZYNYS @AFTN EDMMZQZX @AFTN EDDAYGLZ @AFTN EDDMYQYX @AFTN LDZOZQZX @AFTN EDDFDLHJ @AFTN. Message description: -TITLE SRM -ARCID DLH3354 -IFPLID AA70064724 -ADEP EDDM -ADES LTBA -EOBD 090105 -EOBT 1825 -NEWCTOT 1903 -REGUL LOWES05A -TAXITIME 0019 -REGCAUSE CE 81 IMDPI DLH3354 EDDMYDYE @AFTN 0004978712009010517450300357829950000000267Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/05 17:45:00. Message description: -TITLE DPI -DPISTATUS TARGET -ARCID DLH3354 -ADES LTBA -ADEP EDDM -EOBT 1825 -EOBD 090105 -TTOT 1843 -SID CHIEM4S -TAXITIME 0018 -ARCTYP A320 -REG DAIPU -ORGN EDDMYDYE TTOT NEWCTOT NEWCTOT

All messages in CHMI – Regulated Flight (3/4) 3. Slot Revision Message (SRM) TTOT of last Target DPI remains the “No CTOT before“ Information 4. Slot Revision Message (SRM) TTOT of last Target DPI remains valid 1. ATC DPI Standard transmission: AOBT Actual Off Block ASAT: 18:28 AOBT: 18:29 OMSRM DLH3354 EDDZYNYS @AFTN AA700647240004978712009010518075800358535780000000462Sent to: EDDZYNYS @AFTN EDMMZQZX @AFTN EDDAYGLZ @AFTN EDDMYQYX @AFTN LDZOZQZX @AFTN EDDFDLHJ @AFTN QLHLCCL @SITA FRAP9LH @SITA QLH5YLH @SITA MUCOGLH @SITA. Message description: -TITLE SRM -ARCID DLH3354 -IFPLID AA70064724 -ADEP EDDM -ADES LTBA -EOBD 090105 -EOBT 1825 -NEWCTOT 1911 -REGUL LOWES05A -TAXITIME 0018 -REGCAUSE CE 81 OMSRM DLH3354 EDDZYNYS @AFTN AA700647240004978712009010518155900358777640000000462Sent to: EDDZYNYS @AFTN EDMMZQZX @AFTN EDDAYGLZ @AFTN EDDMYQYX @AFTN LDZOZQZX @AFTN EDDFDLHJ @AFTN QLHLCCL @SITA FRAP9LH @SITA QLH5YLH @SITA MUCOGLH @SITA. Message description: -TITLE SRM -ARCID DLH3354 -IFPLID AA70064724 -ADEP EDDM -ADES LTBA -EOBD 090105 -EOBT 1825 -NEWCTOT 1843 -REGUL LOWES05A -TAXITIME 0018 -REGCAUSE CE 81 IMDPI DLH3354 EDDMYDYE @AFTN 0004978712009010518330200359274980000000253Received from: EDDMYDYE @AFTN. Est. Xmit at: 09/01/05 18:33:00. Message description: -TITLE DPI -DPISTATUS ATC -ARCID DLH3354 -ARCTYP A320 -REG DAIPU -ADEP EDDM -EOBT 1825 -EOBD 090105 -TTOT 1843 -TAXITIME 0010 -ADES LTBA -SID CHIEM2E -ORGN EDDMYDYE TTOT NEWCTOT NEWCTOT

All messages in CHMI – Regulated Flight (4/4) 1. FSA Standard transmission: Take Off IMFSA DLH3354 EDMMZQZX @AFTN 0004978712009010518401500359481870000000212Received from: EDMMZQZX @AFTN. Est. Xmit at: 09/01/05 18:40:00. Message description:-TITLE FSA -ARCID DLH3354 -ADEP EDDM -ADES LTBA -ARCTYP A320 -EOBT 1825 -EOBD 090105 -POSITION -TO 1840 -ADID EDDM ATOT

DPI Summary & Benefits Overview Agenda DPI Summary & Benefits Overview

Problem Statement ATFCM efficiency is limited by the lack of accurate information about the flight in the period before its departure. Airports, AOs, handlers,… efficiency is limited by the lack of information on the incoming flight. Need to share information between the ATM Network and Partners at the Airport.

Overall Benefits – Integration Airport and the Network A way for airports’ integration with ATFCM process, contribution to common picture, support to network, facilitating understanding and decision making. Allow partners at ADES to have a better knowledge of the traffic into its destination and take it into account in its own processes. Allow NMOC to know constraints locally at airports and take them into account in its own processes. Provide more accurate timing of traffic enabling automatic processes such as slot allocation to be more adjusted to the Airspace Users needs. Improve short term forecast of traffic situation. Enable Aircraft Operators to get a better view on their fleet before departure. Support the management of critical situations at airports and its impact on other actors. First step in data exchange between NMOC and airports, Gate-To-Gate.

Benefits – For AOs in Particular Benefit for AOs, ATC,…: Improved adjustment of CTOT to the TOT of the flight Improved visibility on progress of flight at out station Enabler for improving the flight and fleet planning Assistance to updating flight plans Enabler for improved flight and fleet planning Reduced risk of suspension by Flight Activation Monitoring Allow to delay and advance the TOBT No more DLA required if flight is delayed by ATC (ground) CTOT freezing from Actual Off-block onwards Improved management of adverse conditions Network benefits (including AOs, ATC,…): Information sharing improves predictability More accurate flight profiles in ETFMS provide more accurate data to the network: More accurate Traffic Predictions More efficient use of Available Capacity More Capacity Reduced Delays Improved Adherence to ATFM Slots

Increase of Efficiency by Information Sharing Information required by the ATM Network from Airport Partners: Variable Taxi-Time and SID for all departing flights Estimated Off-Block time as known locally at the airport Time of ATC taking responsibility Estimated Take-Off Time A/C Type & Registration Information required by Airport Partners from the ATM Network: Estimated Landing Time ATFCM Flight status (Airborne, suspended,…)

Integration of the Airport and the Network Via message exchange between NMOC and Airports By NMOC to Airport: FLIGHT UPDATE MESSAGE (FUM) Provide ETFMS’ Landing Times to airports By Airport to NMOC:DEPARTURE PLANNING INFORMATION (DPI) message Provide flight data updates before take-off from CDM airports and ATC (TWR) systems to ETFMS

5 Events at ADEP – 5 DPI types Event: Verification Flight Plan EOBT with Airport Slot  E-DPI (Early-DPI) Event: Creation & Update of TOBT  T-DPI-t (Target-DPI-target) Event: TSAT Issue/Publication to NMOC  T-DPI-s (Target-DPI-sequenced) Event: Actual Off-Block  A-DPI (ATC-DPI) Any interruptions in flights’ progress and new TOT is not yet known:  C-DPI (Cancel-DPI)

Timing & Sequence of DPI Messages Each DPI-type corresponds to the progress of the flight

Benefits – Taxi-Time, SID – All DPI types Used to update flight data and traffic predictions in ETFMS Benefits for AOs, ATC,…: reduced risk of FAM suspension prevent issue of CTOT that cannot be met due e.g. a long taxi-times Network benefits: More accurate taxi-time & SID result in more accurate flight profiles in ETFMS provides more accurate data to the network: More accurate traffic predictions More capacity Reduced delays Prevention of CTOT that cannot be met result in more accurate CTOT adherence

Benefits – Early-DPI The E-DPI confirms the existence of Airport Slot for the flight Benefits for AOs, ATC,…: ETFMS slot allocation improved: first-planned-first-served Network benefits: Confirms the existence of an Airport Slot Increases flight plan completeness, i.e. no flight without an airport slot

Benefits – Target-DPI-target The T-DPI-t provides the Target Take-Off Time estimate from AO and handler, i.e. EOBT updated with TOBT Benefit for AOs, ATC,…: Allows for take-off/CTOT before EOBT Prevent issue of a CTOT that cannot be met by the flight Network benefits: More accurate traffic predictions through the provision of the TOBT (+taxi-time)

Benefits – Target-DPI-sequenced The T-DPI-s provides the Take-Off-Time based upon the ATC pre-departure sequence, i.e. based upon the TSAT Benefit for AOs, ATC,…: Prevent issue of CTOT that cannot be met especially in situations where demand is higher than airport/ATC capacity Enabler to improve mgt during e.g. de-icing situations Network benefits: More accurate traffic predictions through the provision of the TSAT (+taxi-time), especially for non-regulated traffic

Benefits – ATC-DPI The A-DPI provides the actual off-block event and the Take-Off-Time based upon AOBT Benefit for AOs, ATC,…: Freeze CTOT Reduce risk on suspension due to Flight Activation Monitoring (FAM) Network benefits: More accurate traffic predictions through the provision of the AOBT (+taxi-time)

Benefits – Cancel-DPI The C-DPI is used to cancel previously sent DPI information. Network benefits: To keep the network up-to-date in case of (last minute) disturbances Remove flight from traffic counts and make the slot available to another flight that is actually ready to go.

Benefits – Flight Progress Display - All DPIs All DPIs provide flight status and flight progress during turn-around process at ADEP to ETFMS and it is: Displayed in CHMI to all CHMI users Sent to Aircraft Operators (and ANSPs) via NMOC Data Redistribution Sent via FUM to all partners at CDM Airports of Destination Benefit for AOs, ATC,…: Improved visibility on progress of flight at out station Enabler for improving the flight and fleet planning Network benefits: Information sharing increases Traffic Predictability

Improved CTOT if local TTOT is provided. EOBT 10:00 ETOT 10:10 CTOT 10:20 exot FPL data only in NMOC/ETFMS Data locally at the airport TOBT/ TSAT 09:48 10:02 CTOT VTT TTOT Flight plan based ETOT (non-CDM), Earliest possible CTOT is the ETOT (10:10) If aircraft is ready for Take-off earlier (10:02) Slot violation If TTOT is provided by A-CDM to NMOC/ETFMS… TTOT will be used as “Earliest possible CTOT”  More suitable CTOT ©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

Summary FUM provides more accurate view on arriving traffic to all partners at the ADES DPI provides local TTOTs and VTTs to ATFCM DPI & FUM are the means to integrate the airport and the network There are mainly Benefits for all partners in ATM

Documentation (1/5) NOP User Guide CHMI ATFCM User Manual (2 parts) Ref: Edition 19.5.1-26, dated 04/02/2016 http://www.eurocontrol.int/publications/nop-portal-user-guide CHMI ATFCM User Manual (2 parts) Ref: Edition 4.0, dated 07/03/2011 http://www.eurocontrol.int/sites/default/files/publication/files/chmi-atfcm-map-reference-guide- current.pdf Ref: Edition 7.0, dated 13/03/2012 http://www.eurocontrol.int/sites/default/files/publication/files/chmi-atfcm-reference-guide-current.pdf

Documentation (2/5) Airport CDM Manual Contains CDM Milestones approach and a general Description of DPI messages Ref: Edition 4.0, March 2012. https://www.eurocontrol.int/sites/default/files/content/documents/official-documents/manuals/2012-airport-cdm-manual-v4.pdf Flight Progress Messages Document Contains DPI and FUM message syntax and semantics, general trigger events Ref: URB/USD/MSG_INTF, version 2.300, dated 25/11/2016 http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/user-guides/flight-progress-msg.pdf DPI Implementation Guide Contains a details of DPI messages, including trigger events and processing by ETFMS Ref: URB/USD/DPI_Impl_Guide, version 2.000, dated 25/11/2016 http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/user-guides/dpi-impl-guide.pdf

Documentation (3/5) FUM Implementation Guide Contains a details of FUM messages, including accuracy info and implementation guidelines Ref: URB/USD/FUM_Impl_Guide, version 1.600, dated 25/11/2016 http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/user-guides/fum-impl-guide-current.pdf DPI & FUM Implementation Road Map Contains description of steps for the DPI & FUM evaluation and Evaluation Criteria Ref: URB/USD/DPI_FUM_Impl_RM, version 1.800, dated 25/11/2016 https://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/user-guides/dpi-fum-impl-road-map.pdf DPI ICD Contains the Airport specific DPI interface with the actual implementation of the DPI contents and trigger events Airport specific, not available via WWW.

Documentation (4/5) Advanced ATC TWR Implementation Guide Contains a details a description and recommendations for ATC TWR Implementation. Ref: URB/USD/AdvAtcTwrImplGuide, version 1.300, dated 25/11/2016  http://www.eurocontrol.int/sites/default/files/content/documents/nm/network-operations/user-guides/advanced-atc-twr-implementation-guide.pdf Adv ATC TWR Benefits Study Available on request. A-CDM web-based training A-CDM web-based training for AO, Handling Agents, ATC/TWR, Pilots,…..  https://trainingzone.eurocontrol.int/clix/data/scorm/decompressed/ACDM_Package_1619660/commonModuleDA/index.htm General web pages www.eurocontrol.int/articles/cdm-airports www.eurocontrol.int/articles/airport-data-integration-dpi-and-fum www.eurocontrol.int/articles/advanced-atc-twr-airports-vs-cdm-airports

Documentation (5/5) EU Rules & Regulations on Airport Slots Article 14 Enforcement 1. An air carrier's flight plan may be rejected by the competent Air Traffic Management authorities if the air carrier intends to land or take off at a coordinated airport, during the periods for which it is coordinated, without having a slot allocated by the coordinator. http://ec.europa.eu/transport/modes/air/airports/slots_en.htm http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CONSLEG:1993R0095:20090630:EN:PDF

Your questions are very welcome

Thank you for your attention Hans Koolen johannes.koolen@eurocontrol.int