1. DPI Messages Short Overview for AOs and Ground Handlers
January 2013
DFS - Erik Sinz
NMOC/Network Operations Services – Hans Koolen

2. Integration of an Airport into the ATM Network
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

3. Content 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.

4. Introduction & General Overview
Agenda
Introduction & General Overview

5. 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
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

6. 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 or SITA networks.
Are sent between EOBT - 3 Hrs and Take-Off.
Data that is typically not available from IFPS.

7. 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 CDM ARCTYP
The CDM REGistration
Note that TSAT and TOBT are not directly provided but included in the TTOT-field (TTOT = TOBT+VTT or TTOT=TSAT+VTT).
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

8. Who Provides Airport CDM data to the network?
Operational
Expected Operational in
EDDM
EBBR
EDDL
LKPR
LSZH
EDDB
LFPG
LIRF
UKBB
EHAM
EDDF
LOWW
EGLL
LFPG
ENGM
EFHK
LEMD
LSGG
EIDW
LIMC
LIML
LFLL
EDDS
ESSA
LEPA

9. 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)
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

10. 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)

11. 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
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

12. Timing & Sequence of DPI Messages

13. 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,…)

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

15. Last received Target Take Off Time (TTOT): EOBT-TOBT Discrepancy
Where is the CDM Data in CHMI 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):
IFPS Discrepancy
in RED font
De-Icing info:
Blue background & “!“
IFPS Discrepancy:
EOBT-TOBT Discrepancy
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

16. Where is the CDM Data in CHMI Flight Data Display?
Airport Info
IFPS Discrepancy:
REGistration
IFPS
CDM Status
Last received TTOT
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

17. List of all sent and received messages
ETFMS Oplog – message details
List of all sent and received messages
Selected Message
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

18. 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

19. Last received Target Take Off Time (TTOT):
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):
De-Icing info:
Blue background & “!“
IFPS Discrepancy
in RED font
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

20. Where is the CDM Data in NOP Flight Data Display?
Airport Info
IFPS Discrepancy:
ARCTYP
IFPS
CDM Status
Last received TTOT
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

21. 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)

22. 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
More information can be found on:
The NM Flight Progress Messages document
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

23. 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 available TOT before take-off. It is in the ETO-field of the ADEP in the RTEPTS list field.
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.
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

24. 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)

25. 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:
The CFMU Flight Progress Messages document
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

26. 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.
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

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

28. 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

29. 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.

30. 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)
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

31. 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.
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

32. B2B Web Services
AOs can have access on request by filling in the existing online NMOC Service Request Form. Direct link:
section 4.
Customer support (contact):
Central Flow Management Unit Customer Support
More information can be found online:
OST Shared space "B2B - Web Services“ (registration needed).
Direct link (after OSO login)
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
©2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL)

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

34. 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

35. 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

36. Overview 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 Received 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
-TTOT 1434
-SOBT 1415
-SID AMPEG3S
-TAXITIME 0019
-ARCTYP B735
-REG DABII
-ORGN EDDMYDYE
IMDPI DLH6CW EDDMYDYE
@AFTN Received 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
-TTOT 1434
-SID AMPEG3S
-TAXITIME 0019
-ARCTYP B735
-REG DABII
-ORGN EDDMYDYE
IMDPI DLH6CW EDDMYDYE
@AFTN Received 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
-TTOT 1444
-SID AMPEG3S
-TAXITIME 0019
-ARCTYP B735
-REG DABII
-ORGN EDDMYDYE
Target DPI Status
TTOT
TTOT
TTOT

37. Overview 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 Received 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
-ATTOT 1434
-SID AMPEG3S
-TAXITIME 0016
-ARCTYP B735
-REG DABII
-ORGN EDDMYDYE
IMDPI DLH6CW EDDMYDYE
@AFTN Received 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
-TTOT 1439
-SID AMPEG3S
-TAXITIME 0016
-ARCTYP B735
-REG DABII
-ORGN EDDMYDYE
IMDPI DLH6CW EDDMYDYE
@AFTN Received 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
-TTOT 1434
-SID AMPEG3S
-TAXITIME 0016
-ARCTYP B735
-REG DABII
-ORGN EDDMYDYE
Sequenced DPI Status
TTOT
Modified TTOT

38. Overview 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 Received 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
-TTOT 1427
-SID AMPEG2E
-TAXITIME 0014
-ARCTYP B735
-REG DABII
-ORGN EDDMYDYE
IMDPI DLH6CW EDDMYDYE
@AFTN Received 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
-TTOT 1427
-TAXITIME 0014
-ADES LSGG
-SID AMPEG2E
-ORGN EDDMYDYE
IMFSA DLH6CW EDMMZQZX
@AFTN Received 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
-POSITION -TO ADID EDDM
TTOT
TTOT
ATOT

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

40. 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

41. 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

42. Overview 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 AA Sent to: EDDAYGLZ @AFTN EDDFDLHJ @AFTN QLHLCCL @SITA MUCOGLH @SITA. Message description:
-TITLE SAM
-ARCID DLH3354
-IFPLID AA
-ADEP EDDM
-ADES LTBA
-EOBD
-EOBT 1825
-CTOT 1844
-REGUL LOWES05A
-TAXITIME 0019
-REGCAUSE CE 81
IMDPI DLH3354 EDDMYDYE @AFTN Received 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
-TTOT 1844
-SOBT 1825
-SID CHIEM4S
-TAXITIME 0019
-ARCTYP A320
-REG DAIPU
-ORGN EDDMYDYE
IMDPI DLH3354 EDDMYDYE @AFTN Received 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
-TTOT 1844
-SID CHIEM4S
-TAXITIME 0019
-ARCTYP A320
-REG DAIPU
-ORGN EDDMYDYE
TTOT
TTOT
CTOT

43. Overview 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: TSAT - DPI Status is unchanged TOBT: 18:25 TSAT: 18:39 (Basis=CTOT)
OMSRM DLH3354 EDDZYNYS @AFTN AA Sent to: EDMMZQZX @AFTN EDDMYQYX @AFTN Message description:
-TITLE SRM
-ARCID DLH3354
-IFPLID AA
-ADEP EDDM
-ADES LTBA
-EOBD
-EOBT 1825
-NEWCTOT 1853
-REGUL LOWES05A
-TAXITIME 0019
-REGCAUSE CE 81
OMSRM DLH3354 EDDZYNYS @AFTN AA Sent to: EDDZYNYS @AFTN EDDAYGLZ @AFTN Message description:
-TITLE SRM
-ARCID DLH3354
-IFPLID AA
-ADEP EDDM
-ADES LTBA
-EOBD
-EOBT 1825
-NEWCTOT 1903
-REGUL LOWES05A
-TAXITIME 0019
-REGCAUSE CE 81
IMDPI DLH3354 EDDMYDYE @AFTN Received 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
-TTOT 1843
-SID CHIEM4S
-TAXITIME 0018
-ARCTYP A320
-REG DAIPU
-ORGN EDDMYDYE
TTOT
NEWCTOT
NEWCTOT

44. Overview 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 AA Sent to: EDMMZQZX @AFTN EDDAYGLZ @AFTN LDZOZQZX @AFTN FRAP9LH @SITA MUCOGLH @SITA. Message description:
-TITLE SRM
-ARCID DLH3354
-IFPLID AA
-ADEP EDDM
-ADES LTBA
-EOBD
-EOBT 1825
-NEWCTOT 1911
-REGUL LOWES05A
-TAXITIME 0018
-REGCAUSE CE 81
OMSRM DLH3354 EDDZYNYS @AFTN AA Sent to: EDMMZQZX @AFTN LDZOZQZX @AFTN Message description:
-TITLE SRM
-ARCID DLH3354
-IFPLID AA
-ADEP EDDM
-ADES LTBA
-EOBD
-EOBT 1825
-NEWCTOT 1843
-REGUL LOWES05A
-TAXITIME 0018
-REGCAUSE CE 81
IMDPI DLH3354 EDDMYDYE @AFTN Received 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
-TTOT 1843
-TAXITIME 0010
-ADES LTBA
-SID CHIEM2E
-ORGN EDDMYDYE
TTOT
NEWCTOT
NEWCTOT

45. Overview all messages in CHMI – Regulated Flight (4/4)
1. FSA Standard transmission: Take Off
IMFSA DLH EDMMZQZX @AFTN Received 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
-POSITION -TO ADID EDDM
ATOT

46. DPI Summary & Benefits Overview
Agenda
DPI Summary & Benefits Overview

47. 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.

48. Overall Benefits – Integration Airport into the Network
A way for airports’ integration into 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.

49. 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

50. 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,…)

51. Integration of the Airport in 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

52. 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)

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

54. 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

55. The E-DPI confirms the existence of Airport Slot for the flight
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

56. 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)

57. 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

58. 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)

59. 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

60. 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

61. 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)

62. 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 into the network
There are mainly Benefits for all partners in ATM

63. Thank you for your attention
Erik Sinz - DFS
Hans Koolen