Integration of the Airport and the Network DPI/FUM Messages Management Overview

Transcription

1 Integration of the Airport and the Network DPI/FUM Messages Management Overview Hans Koolen NMOC/CFMU Network Operations Services Edition March 2013

2 Introduction Purpose The purpose of this presentation is to provide an overview of the various DPI and FUM messages and their benefits for all the relevant stakeholders. Target Audience Management All others who would like to have a global overview 2

3 AGENDA 1) Introduction 2) Flight Update Message - FUM 3) Departure Planning Information message - DPI 4) Information Sharing by NMOC/CFMU 5) Summary 6) Documentation & Contacts 4

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

5 Integration of an Airport and the ATM Network 2011 The European Organisation for the Safety of Air Navigation (EUROCONTROL) 6

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

7 Integration of the Airport and the Network FLIGHT UPDATE MESSAGE (FUM) Provide ETFMS Landing Times to airports DEPARTURE PLANNING INFORMATION (DPI) Provide flight data updates before take-off from CDM airports and ATC (TWR) systems to ETFMS 11

8 AGENDA 1) Introduction 2) Flight Update Message - FUM 3) Departure Planning Information message - DPI 4) Information Sharing by NMOC/CFMU 5) Summary 6) Documentation & Contacts 12

9 Flight Update Message (FUM) Purpose: Supply partners at airports of destination with landing time. Contains Estimated LanDing Time (ELDT) and ETO over last route point. Sent via AFTN by ETFMS. Sent at: ELDT 3 hours ELDT change > 5 min Important flight status changes Not required when ANSP receives ETFMS data redistribution (EFD message). 13

10 Flight Update Message (FUM) EXAMPLE - TITLE FUM - BEGIN ADDR - FAC LEMDDZZP - END ADDR - IFPLID AA ARCID SWR581 - ARCTYP MD80 - REG HBIXG - ADEP EKCH - EOBT EOBD ELDT ESTDATA - PTID BAN ETO FL F230 - ADES LEMD - STAR XXXXX - FLTSTATE AA 14

11 AGENDA 1) Introduction 2) Flight Update Message - FUM 3) Departure Planning Information message - DPI 4) Information Sharing by NMOC/CFMU 5) Summary 6) Documentation & Contacts 15

12 General Overview DEPARTURE PLANNING INFORMATION (DPI) Flight data updates before take-off. From CDM airports and ATC (TWR) Output of the locally established CDM process From system to system. Received by ETFMS via AFTN or SITA networks. Between EOBT - 3 Hrs and Take-Off. DPI contains: Accurate estimation of Take-Off Times (TTOTs). Updates of TaxiTime, SID, ARCTYP, REG Data that is typically not available from IFPS. 16

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

14 Timing & Sequence of DPI Messages When shall which DPI be sent? E-DPI T-DPI-t T-DPI-s A-DPI EOBT - 3hrs EOBT - 2hrs TOBT 40 min AOBT Take-off Fig: DPI

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

16 Benefits Taxi-Time, SID All DPI types To update flight profiles and traffic predictions Benefit 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 more accurate CTOT adherence 21

17 Benefits ARCTYP & REGistration - All DPI types Raise warnings about inconsistencies between data at airport and in flight plan Benefit for AOs, ATC, : Receive an automatic reminder that flight plan data is inconsistent with data at the airport AO is requested to solve the inconsistency by e.g. updating the flight plan More accurate flight plans (for en-route ATC, ADES, ) Network benefits: More accurate flight profiles in ETFMS provides more accurate data to the network. 22

18 Improved CTOT if local TTOT is provided 10:00 10:10 10:20 exot EOBT ETOT CTOT In NMOC/CFMU 09:48 10:02 Locally at the airport VTT TOBT/ TTOT TSAT CTOT Flight plan based ETOT (non-cdm) Slot violation If TTOT is provided by A-CDM to NMOC/CFMU/ETFMS TTOT = Earliest possible CTOT More suitable CTOT 28

19 AGENDA 1) Introduction 2) Flight Update Message - FUM 3) Departure Planning Information message - DPI 4) Information Sharing by NMOC/CFMU 5) Summary 6) Documentation & Contacts 29

20 Benefits Sharing DPI information - All DPIs Provide flight status and flight progress during turn-around process at ADEP via: FUM to all partners at the Airport of Destination CHMI to all CHMI users NMOC/CFMU Data Redistribution to Aircraft Operators and ANSPs 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 30

21 AGENDA 1) Introduction 2) Flight Update Message - FUM 3) Departure Planning Information message - DPI 4) Information Sharing by NMOC/CFMU 5) Summary 6) Documentation & Contacts 31

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

23 AGENDA 1) Introduction 2) Flight Update Message - FUM 3) Departure Planning Information message - DPI 4) Information Sharing by NMOC/CFMU 5) Summary 6) Documentation & Contacts 33

24 Documentation (1/2) Airport CDM Manual Contains CDM Milestones approach and a general Description of DPI messages Ref: Edition 4.0, March airport-cdm-manual-v4.pdf NM/CFMU Flight Progress Messages Document Contains DPI and FUM message syntax and semantics, general trigger events Ref: URB/USD/MSG_INTF, version 1.900, dated 01/02/ DPI Implementation Guide Contains a details of DPI messages, including trigger events and processing by ETFMS Ref: URB/USD/DPI_Impl_Guide, version 1.600, dated 01/02/

25 Documentation (2/2) FUM Implementation Guide Contains a details of FUM messages, including accuracy info and implementation guidelines Ref: URB/USD/FUM_Impl_Guide, version 1.200, dated 01/02/ DPI & FUM Implementation Road Map DPI ICD Contains description of steps for the DPI & FUM evaluation and Evaluation Criteria Ref: URB/USD/DPI_FUM_Impl_RM, version 1.400, dated 01/02/ Contains the Airport specific DPI interface with the actual implementation of the DPI contents and trigger events Airport specific, not available via WWW. 35

26 Contacts Contacts: Hans Koolen, tel johannes.koolen@eurocontrol.int Ms/Ms NMOC/CFMU Operations, tel: xxxx firstname.lastname@eurocontrol.int Ioana Coliban, tel ioana-angelica.coliban-porosnicu@eurocontrol.int 36

27 Your questions are very welcome 37

28 Thank you for your attention Hans Koolen