Cfmu Release Notes 10v2

EUROCONTROLC F M U

CFMU 10 - RELEASE NOTESPlanned for Implementation in 2004

Doc. ReferenceCFMU_10RL

6 May 2004 Edited & produced by the CFMU/User Relations Bureau© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

i

EUROCONTROL

PLANNED FOR IMPLEMENTATION in 2004

Revised May 2004

http://www.cfmu.eurocontrol.int

http://www.cfmu.eurocontrol.be/


ii

© 2003 European Organisation for the Safety of Air Navigation(EUROCONTROL). All rights reserved. No part of thispublication may be reproduced, stored in a retrieval system, ortransmitted in any form or by any means, electronic, mechanical,photocopying, recording or otherwise, without the priorpermission of EUROCONTROL.

EUROCONTROLC F M U




iii

TABLE OF CONTENTS

1. INTRODUCTION ............................................................................................1

1.1. General ....................................................................................................................1

2. PLANNING.....................................................................................................3

3. CFMU 10.0 ....................................................................................................5

3.1. FLIGHT PLAN SYSTEMS......................................................................................53.1.1. Integrated Initial Flight Plan Processing System (IFPS) ...........................................53.1.1.1. En-route STAY indicator ..........................................................................................53.1.1.2. Mode S IFP indicator................................................................................................63.1.1.3. Flight trajectory calculation in IFPS ..........................................................................63.1.1.4. EUR RVSM entry/exit conditions checking...............................................................73.1.1.5. En-route DCT checking improvements.....................................................................73.1.1.6. AFP processing........................................................................................................83.2. ENHANCED TACTICAL FLOW MANAGEMENT SYSTEM (ETFMS).......................93.2.1. ETFMS redistribution (to the ATS system) ...............................................................93.2.2. Flight Update Message (FUM) .................................................................................93.2.3. Introduction of the IFPLID in all ATFM Messages to / from ETFMS .......................11Withdrawn Requirement

(ATFM Messages for a flight becoming non-regulated shortly before departure) ...123.2.4. Flight Suspension Message will contain the Identifier of Regulation Causing

Suspension ............................................................................................................133.2.5. Modification of the comment of the FLS message .................................................133.2.6. Process APL/ACH/AFIL messages as updates to the Current flight model route...143.2.7. Departure Planning Information .............................................................................143.3. EXTERNAL INTERFACES....................................................................................153.3.1. New CFMU Interface – Common Human Machine Interface (CHMI) .....................153.3.1.1. Functional changes................................................................................................153.3.1.2. Geographical display of CFMU airspace data ........................................................153.3.1.3. Geographical display of the Traffic Load status (FMP only)....................................163.3.1.4. Geographical display of Regulations and average delays ......................................16

EUROCONTROLC F M U




iv

3.3.1.5. Geographical display of the flight path ...................................................................163.3.1.6. Graphical display of the vertical flight profile ..........................................................163.3.1.7. Attention Getter......................................................................................................163.3.1.8. Miscellaneous improvements ................................................................................173.3.1.9. Flight Plan filing assistance....................................................................................173.3.1.9.1. Supplementary information for standard routes......................................................173.3.1.9.2. Flight planning assistance tools..............................................................................173.3.2. Remote Client Application (RCA) ...........................................................................173.3.3. CFMU Internet Application (CIA) ............................................................................183.3.4. CFMU Interactive Reporting (CIR) .........................................................................183.3.4.1. Gradual deployment of the CIR..............................................................................183.4. DATA SYSTEMS ..................................................................................................193.4.1. Data Warehouse (DWH)......................................................................................193.4.1.1. Extended scope of archived data to prepare the monitoring of newly implemented

features in other CFMU operational systems .........................................................193.4.1.2. Computation of new quality and performance indicators, accessible in future

releases of the CIR ...............................................................................................19

4. DICTIONARY OF ABBREVIATIONS .........................................................21

ANNEXES

PRIMARY FIELD COMPOSITION OF TACTICAL ATFM MESSAGES EXCHANGE

CORRELATION BETWEEN CFMU REASONS FOR REGULATION AND IATA DELAY CODES

BIBLIOGRAPHY OF CFMU DOCUMENTS

AGENCY CONTACTS DATABASE CFMU CLIENTS UPDATE FORMmailto:[email protected]

mailto:[email protected]

EUROCONTROLC F M U



6 May 2004 Edited & produced by the CFMU/User Relations Bureau INTRO© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

1

1. INTRODUCTION1.1. General

This document describes the new or modified functions that will be delivered bythe CFMU as part of the CFMU 10 software release planned in November 2004.This document replaces the document issued in August 2003. The main editorialchanges are due to the removal of the changes related to CFMU 9.3, which wereimplemented last February.The other changes are mainly related to planning and to additional information.

The objective of this document is to provide users of the Central Flow ManagementUnit (CFMU) Systems with advance notice of modifications that will have an impactupon their operational procedures and/or systems.

The CFMU 10 release includes many changes arising from different sources andco-ordinated through the European ATFM Group and its sub-groups.

It should be noted that additional copies of this document could beobtained from the CFMU Website at :

http://www.cfmu.eurocontrol.int


6 May 2004 Edited & produced by the CFMU/User Relations Bureau INTRO© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

2

INTENTIONALLY LEFT BLANK

EUROCONTROLC F M U


PLANNING

6 May 2004 Edited & produced by the CFMU/User Relations Bureau Planning© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

3

2. PLANNING

The CFMU 10.0 software release is planned to be implemented in November 2004.This software release will also include new services that will be deployed afterNovember 2004 and according to a planning that will be discussed with the differentinvolved partners:

a) ETFMS redistribution for ATC Service providers,b) Implementation of the new CFMU external interface replacing RCA,c) Flight planning assistance via IFPUV,d) Provision of the Flight Update Message (FUM),e) Reception of the Departure Planning Information Message (DPI),f) Deployment of the tool for Towers.

6 May 2004 Edited & produced by the CFMU/User Relations Bureau Planning© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

4


EUROCONTROLC F M U

CFMU 10.0 - RELEASE NOTESPlanned for Implementation in 2004

FLIGHT PLANSYSTEMS

IFPS/RPL/RCAT

6 May 2004 Edited & produced by the CFMU/User Relations Bureau Flight Plan Systems© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

5

3. CFMU 10.03.1. FLIGHT PLAN SYSTEMS3.1.1. Integrated Initial Flight Plan Processing System (IFPS)3.1.1.1. En-route STAY indicator

Objective : To enable time delays associated with certain special en-routeactivities such as training flights, air-air refuelling, photographicmissions etc. to be entered in the Route Field of a FPL thusenabling calculation of a more accurate profile.

Description : To indicate the time spent on the route of the flight in an area(STAY area) where special activities are planned a STAY indicatorshall be inserted in Field 15 of the FPL between the point of entryin the STAY area and the point of exit from the STAY area.

Example : … MCT STAY1/0100 POL …

The entry point in the STAY area and the exit point from the STAY area can be thesame.

Example : … MCT STAY1/0030 MCT …

To allow several STAY indicators to be inserted in the route of a flight a numberfrom 1 to 9 shall be attached to a STAY indicator.

Example : … TNT STAY1/0030 TNT UP6 MCT STAY2/0030 MCT…

The time spent in the STAY area shall be indicated in hours and minutes.It shall be possible to indicate speed/flight level changes, flight rules changes(IFR/VFR) and flight type changes (GAT/OAT) on the point of entry in the STAYarea and/or on the point of exit from the STAY area.

Example : ..SHA VFR STAY1/0030 SHA/N0420F330 IFR …

To indicate the reason for STAY, a free text STAYINFO indicator shall be insertedin Field 18 of the FPL.

Example : ..Field 15: ..SHA STAY1/0030 SHA …..Field 18: ..STAYINFO1/CALIBRATION OF SHA VOR

The sequence number attached to the STAYINFO indicator shall be the same asthe one attached to the corresponding STAY indicator.A STAY indicator can only be used for en-route special activities.A STAY indicator can only be used for flights that are completely within the IFPSZone.The STAY indicator is not allowed in Repetitive Flight Plans.

Impact : All STAY information (STAY and STAYINFO) will be output byIFPS to external client systems in either ICAO or ADEXP formataccording to the client requirement. Modifications in the externalclient systems may be required in order to allow processing of theSTAY information.

Procedures for the use of the STAY indicator should be noted and complied with bythe flight plan originators.

EUROCONTROLC F M U


FLIGHT PLANSYSTEMS

IFPS/RPL/RCAT


6

3.1.1.2. Mode S IFP indicator

Objective : To allow ATC to determine to which flights a Mode A conspicuitycode (A1000) can be assigned in order to save Mode A discretecodes and permit them to be allocated to other flights.

Description : For Mode S equipped flights (letter S in Field 10b), the IFPS willinsert the IFP indicator MODESASP in the output flight plan in thefollowing conditions :

- for a flight that takes place entirely within the Mode Sdeclared airspace and

- for a flight that enters the declared Mode S airspace andremains entirely within the airspace for the rest of the flight.

Example : (FPL-ABC443-IS-A319/M-SDEIRWY/S-EDDF1515-N0416F220 KIR G104 RUWER G104 TILGA UG104 DIK UW64BATTY-EBBR0032-EET/EBUR0017 EBBU0018 DOF/030724 IFP/MODESASP)

Note : Although this mechanism will be implemented in IFPS in theCFMU 10.0 release timeframe, the output of the Mode S IFPindicator will be synchronised with the implementation of Mode Soperations by the States concerned.

Impact : ATC centres that implement Mode S operations may process theMode S IFP indicator in order to use the information provided inthe code allocation process.

3.1.1.3. Flight trajectory calculation in IFPS

Objective : To improve calculation of the trajectory of a flight in IFPS.

Description : A new algorithm to calculate the time and level elements of thetrajectory of a flight will be implemented for IFPS.

The following elements are included:

- Use of Profile Tuning Restrictions (currently known as CFLs, ConditionalFlight Levels) to allow a better tuning of the IFPS profile.

- The taxitime will be included in the time profile calculation.

Impact : The IFPS addressing is expected to improve. No impact onexternal client systems.

EUROCONTROLC F M U


FLIGHT PLANSYSTEMS

IFPS/RPL/RCAT


7

3.1.1.4. EUR RVSM entry/exit conditions checking

Objective : To adapt the RVSM Flight Planning requirements and the relatedIFPS checking to an expanded RVSM area.

Description : Since the introduction of the EUR RVSM, there has been arequirement for Aircraft Operators to file, in FPLs, publishedentry/exit points to/from EUR RVSM region. The introduction ofRVSM in the ICAO MID region and the proposed expansion ofEUR RVSM into the Russian Federation have required that theentry/exit criteria be revisited.The current IFPS technology allows the detection of the entry/exitof a flight into/from an RVSM airspace without the explicit mentionin the Flight plan of an RVSM entry/exit point. Therefore, the IFPSsoftware will be adapted to allow disabling of the current checkingof RVSM entry/exit conditions (RVSM entry/exit point and flightlevel). IFPS will continue to accept and process cruising flight levelchanges indicated over points on the boundary of the EUR RVSMairspace as normal flight level changes.In parallel, meetings are taking place with ICAO Paris office toformulate a proposed revision of ICAO Doc 7030 and adapt theprocedure to the new possibilities. A proposed amendment is to becirculated to ICAO member States for approval.Once an agreement is reached, further information will beprovided to all interested parties on the updated RVSM FlightPlanning requirements and the related IFPS checking.

Impact : Simplification of the FPL filing process for RVSM.Possible need to adapt FPL filing systems.

3.1.1.5. En-route DCT checking improvements

Objective : To improve the current en-route DCT checking.

Description : The en-route DCT checking by IFPS was introduced into operationsin 2001, in the CFMU 7.0 release. The following improvements tothe en-route DCT checking will be implemented in the CFMU 10.0release.

It shall be possible to define an en-route DCT limit for a given National Airspace(NAS) in addition to the current possibility to define such a limit for a given FIR/UIR.Note: A National Airspace can include one or several FIR/UIRs.

It shall also be possible to define an en-route DCT limit for a flight level band in agiven FIR/UIR or NAS. For example, in a given FIR, a DCT limit of 20 NM could bedefined above FL70 and a DCT limit of 300NM could be defined below FL70.

When a planned DCT segments crosses the horizontal or vertical boundarybetween two airspaces for which a DCT limit is defined, IFPS shall check that theentire DCT segment is shorter than each one of the two DCT limits. The twoairspaces could be FIRs, UIRs, NASs or a flight level band of such airspaces.

EUROCONTROLC F M U


FLIGHT PLANSYSTEMS

IFPS/RPL/RCAT


8

It shall be possible to exclude one or several types of flight from a given en-routeDCT limit, be it a general DCT limit for an FIR/NAS or a DCT limit for flight levelband in an FIR/NAS. That shall allow for example military flights to be excludedfrom a general DCT limit of 20 NM in a given FIR. The IFPS shall compare the typeof flight indicated in Field 8b of the ICAO flight plan against the list of types of flightthat are to be excluded from a given en-route DCT limit.

As part of the route processing, IFPS attempts to replace a DCT segment with aknown and available airway segment. If candidate airways are identified but theyare all not available at the time and the requested level the flight plan shall beinvalidated by IFPS.

Impact : No impact on external systems. The new additions to the en-route DCTchecking are expected to provide more flexibility to States in managing the DCTlimits for their national airspace.

3.1.1.6. AFP processing

Objective : To improve the AFP (ATC Flight Plan Proposal) messagesprocessing.

Description : Currently the estimate point included in an AFP message has to beexplicitly mentioned in the Route field (ICAO Field 15) of the AFPmessage. With effect from the CFMU 10.0 release, the estimatepoint need no longer be explicitely specified provided it is a pointalong an ATS route mentioned in the Route Field.

The IFPLID will be included as an optional field in the syntax of AFPmessages in ADEXP format. In the CFMU 10.0 release, IFPS willnot use the IFPLID for correlation. This upgrade will beimplemented in a future software release. The change in CFMU10.0 is meant to allow the AFP originator to start including theIFPLID in AFP messages, in a release that is not synchronised withthe IFPS release.

Note: It should be noted that the IFPLID should always be insertedin an AFP message by a system. Due to the structure of the IFPLID,manual inclusion of IFPLID in a message is prone to error and it ishighly recommended to be avoided.

The ARCTYP will be made an optional field in the syntax of AFPmessages in ADEXP format. This change will allow AFP originatorsto omit the aircraft type in AFP messages in case the aircraft typedoes not change. However, the aircraft type will continue to becompulsory information in AFP messages for missing flight plans.

Impact : AFP messages originators may want to consider these changes inthe process of AFP filing to IFPS.

EUROCONTROLC F M U


ETFMS

6 May 2004 Edited & produced by the CFMU/User Relations Bureau ETFMS© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

9

3.2. ENHANCED TACTICAL FLOW MANAGEMENT SYSTEM (ETFMS)

3.2.1. ETFMS redistribution (to the ATS system)

Objective : To re-distribute the current ETFMS flight data to Air NavigationService Providers (ANSPs).

Description : In the ETFMS implementation plan the second phase is devoted tothe redistribution of information to ANSPs.

ETFMS data redistribution will happen when specific events, which can normallycause an update of the ETFMS flight database, occur. As a result, and afterhaving processed such an event, the system will construct and send an ETFMSFlight Data (EFD) message.

This message consists of a snapshot of selected data regarding the specific flight,at the time of distribution. It is fully described in the CFMU Flight ProgressMessages document. Events that can trigger a data distribution can be due to thereception of incoming messages (flight plan messages or ATFM messages), tosystem operators modifying flight or CFMU environment data, or to system time-outs resulting in the modification of flight data.Each generated EFD message will be transmitted to the CFMU gateway system(enhanced with data distribution functionality). This gateway system will broadcasteach received EFD to all ETFMS entry nodes (enhanced to receive EFD input)included in the distribution. Each entry node system will process the EFDs selectedby the associated ANSP, on the basis of filtering functions applied on selected dataincluded in each EFD message. These filtering functions are specified in thedocument ICD (Interface Control Document) for ETFMS data re-distribution. Thefiltering configuration is part of the customisation of the Entry Node. For a givenEntry Node, the configuration includes the selection of the filtering functions and foreach function, the specification of the applicable values.

Impact : ANSPs willing to receive the ETFMS flight data shall inform theCFMU, adapt their procedures and systems as required.

3.2.2. Flight Update Message (FUM)

Objective : To improve the use of airport resources and ATM capacity throughthe exchange of flight plan data.

Description : An information exchange process has been defined to enablebetter awareness between airports and the CFMU.

Airports are looking for early updates of the landing time of flights based on ETFMSdata. CFMU will provide advanced information on the Estimated Time of Arrival(ETA) of the inbound flights.The FUM is fully described in the CFMU Flight Progress Messages document. Itcontains the following main items :

- the Estimated Landing Time (ELDT)The ELDT will be the CFMU estimation of the aircraft’s landing time, nottaking into account any unplanned changes to the flight such as holding closeto the aerodrome of destination. It is the most accurate value that is known to

EUROCONTROLC F M U


ETFMS


10

ETFMS based upon it’s own flight profile calculation and flight data updatesreceived from ATC.

- the STAR Entry Point or the last point in the flight plan route with thecorresponding Estimated Time Over (ETO or CTO or ATO).

- a flight status field that can be used as an accuracy indicator of the providedestimates.

Example of a FUM message-TITLE FUM-BEGIN ADDR –FAC EBBUZQZX-END ADDR-IFPLID BB52638214-ARCID CTN456-ADEP LDZA-ADES EBBR-EOBD 021003-EOBT 1055-ELDT 0210031240-ARCTYP B462-REG DABXW-ESTDATA –PTID BATTY –ETO 021003122800 –FL F190-FLTSTATE TA

The FUM will be sent via AFTN or SITA. The addressing will be derived from theAerodrome of Destination (ADES) and will follow the standards already used forATS Units for other ATFM messages but on a separated list of addresses.The FUM will be sent at the following occurrences :

- The first FUM will be sent 3 hours before the Time of Arrival by ETFMS. Inmost cases the trigger moment (ELDT – 3 hours) will be based upon flightplan data. However in case the ELDT based upon the latest received airborneinformation (ELDT_airborne) is earlier than ELDT from flight plan data thenthe FUM will be sent at ELDT_airborne – 3 hours.This FUM will take into account the last received DLA messages and thepossible published ATFM delay.

- change of the ELDT of at least X minutesX will be a system parameter in the range 5 – 15 minutes.

- important flight status changes such as : pre-active, airborne, suspended.

Impact : A procedure will be published after the implementation of theCFMU10 software version describing the procedure to follow toget access to the FUM message.

EUROCONTROLC F M U


ETFMS


11

3.2.3. Introduction of the IFPLID in all ATFM Messages to / from ETFMS

Objective : Adding the IFPLID to the ATFM messages will enable thereceivers of these message to improve their automatic correlation.

Description :

a) ETFMS will output the IFPLID in all outgoing messages.The relevant messages are :SAM, SRM, SLC, SIP, FLS, DES, RRP, RRN, ERR, FUM.The IFPLID therefore becomes a mandatory field in these messages (exceptthe ERR message where it will be optional).

Example of an ATFM message output by CFMU-TITLE SAM-IFPLID AA36655760-ARCID ABC101-ADEP EGLL-ADES LMML-EOBD 021010-EOBT 0845-CTOT 0910-REGUL UZZU11-TAXITIME 0020-REGCAUSE CE81

b) ETFMS will accept the IFPLID when provided in an incoming message inADEXP format.The relevant messages are :SMM, SPA, SRJ, FCM, RJT, SWM, RFI, REA, FSA, DPI.The IFPLID therefore becomes an optional filed in these messages.

NOTE : The insertion of the IFPLID is only expected in ADEXP formatmessages that are generated systematically. It is not expected, oreven desired, that the IFPLID should be inserted into messagesthat are manually created, either ADEXP or ICAO format.

Example of an ATFM message received by CFMU-TITLE FCM-IFPLID AA36655760 optional field-ARCID ABC101-ADEP EGLL-ADES LMML-EOBD 021010-EOBT 0845-RVR 2000

Impact : Client systems should be adapted to receive and use the IFPLIDfield in the messages referred to in a) above.

EUROCONTROLC F M U


ETFMS


12

Client systems that systematically generate the messages referredto in b) above should include the IFPLID.For ANSP clients that do not yet receive flight plans in ADEXPformat, the IFPLID could be extracted from the first correlatedCASA message (these messages only exist in ADEXP format e.g.SAM, SRM, etc.).For Aircraft Operators, the IFPLID could be extracted from theACK message or from the first correlated CASA message (thesemessages only exist in ADEXP format e.g. SAM, SRM, etc.).

Withdrawn Requirement3.2.4.ATFM message for a flight that becomes non-regulated shortly before departure

Objective : To publish a realistic departure time to all units concerned.

Description : A flight may become non regulated shortly before its departure(between its EOBT – “TIS” and CTOT – taxitime – TRS) :-either because its latest regulation is cancelled;-or because the last period of its latest regulation has been

deleted or reduced such that the ETO of the flight is outsidethe period.

Since the flight can no longer comply with the Flight plan EOBT due to this lastregulation there is a need to use more realistic information. Instead of issuing anSLC, EAG OSG 14 requested to issue an SRM with a NEWCTOT at current time +taxitime + “TIS” to be respected by the Tower together with its related slot tolerancewindow.The regulation having delayed the flight will be kept in the relevant field :

In case the AO is not able to make the NEWCTOT, it will have to send a DLA toconfirm the EOBT the flight can make. Then, ETFMS will issue a new SRM or anSLC as appropriate.If the flight becomes non regulated very close to its departure (after CTOT –taxitime – TRS), as in CFMU 9, no ATFM message will be sent.

Example of a such SRM message

-TITLE SRM-IFPLID AA36655760-ARCID ABC101-ADEP EGLL-ADES LMML-EOBD 021010-EOBT 0845-NEWCTOT 0930-REGUL UZZU11-COMMENT TAKE OFF TIME ADJUSTED AT 0930 BECAUSE THIS FLIGHT ISNO LONGER AFFECTED BY REGULATION UZZU11-TAXITIME 0020-REGCAUSE CE81

EUROCONTROLC F M U


ETFMS


13

Impact : Adaptation to the procedures.

3.2.4. Flight Suspension Message will contain the Identifier of Regulation CausingSuspension

Objective : To inform the AOs of the location that is giving them problems.

Description : The identifier of the concerned regulations together with thecorresponding regulation cause will be inserted in the FLSmessage to inform the AOs and ANSPs of the location, as is donefor the slot messages. These fields are optional because thesuspension is not always caused by a regulation e.g. FlightActivation Monitoring or the receipt of a Slot Missed Message.

Example of a FLS message-TITLE FLS-IFPLID AA36655760-ARCID ABC101-ADEP EGLL-ADES LMML-EOBD 021010-EOBT 0845-REGUL UZZU11-COMMENT CLOSURE-TAXITIME 0020-REGCAUSE AA83

Impact : It is expected a reduction of the calls to the help desk.Change in message format.

3.2.5. Modification of the comment of the FLS message

Objective : To provide the user with correct information.

Description : When the RVR of the flight is unknown, the comment will be “RVRUNKNOWN”, instead of “RVR CRITERIA NOT MET” (which willremain for other occurrences).:

Example of a FLS message-TITLE FLS-IFPLID AA36655760-ARCID ABC101-ADEP EGLL-ADES LMML-EOBD 021010-EOBT 0845-RVR 350-REGUL UZZU11-RESPBY 0855-COMMENT RVR UNKNOWN-TAXITIME 0020-REGCAUSE CE81

EUROCONTROLC F M U


ETFMS


14

Impact : ATFM users shall adapt their procedures and systems as required.

3.2.6. Process APL/ACH/AFIL messages as updates to the Current flight modelroute

Objective : Better processing of the IAPL/IACH/IAFIL messages to avoidlosing all previously received information from ATC such as FSA,CPR, etc.

Description : To update the Current flight model, ETFMS will use the list ofpoints of the route only from the point in the ESTDATA fieldonwards, in a similar way as the FURTHRTE-field of the FSAmessage.

Impact : No impact on external systems. Past and archived profiles willbetter reflect the profile used in the Tactical phase.

3.2.7. Departure Planning Information

Objective : Initial development of the message process to enable ATFMsystem to receive updates from airports. This action is part of theAirport CDM process.

Description : In collaboration with the Aircraft Operators, an airport may providetaxi time and more accurate take-off time for outbound flights.Various instances of the DPI message are being developed by theCFMU to permit airports to provide more accurate information tothe CFMU for departing traffic. The instances comprise the EarlyDPI (E-DPI) providing information before the slot issue time, the A-DPI providing information when the flight is under local ATCresponsibility and the T-DPI providing information for the inbetween stage.The CFMU release will enable the reception and parsing of suchmessages. The related operational procedures will be developedas part of the evaluation of the impact of these messages andthey will be communicated in due time.

Impact : No impact on external systems. Format of the messages will becommunicated to the participants of the evaluation.

EUROCONTROLC F M U


EXTERNALINTERFACES

6 May 2004 Edited & produced by the CFMU/User Relations Bureau External Interfaces© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

15

3.3. EXTERNAL INTERFACES3.3.1. New CFMU Interface – Common Human Machine Interface (CHMI)

Objective : Improve services through technological evolution.

Description : CFMU 10.0 will be the start point of the deployment of the newinterface for external users. This implies a change oftechnology (move from C++ to Java based applications).

This first version of CHMI for external users will include the current RCA/CIAfunctions and in addition will give access to the ENV information and to the Mapfunctionality.The main benefit of this new interface will be the possibility to get graphicalrepresentations of the airspace structure and of the flight plans.Three types of CFMU Interfaces will be defined depending on the customers :

- FMPs, Aircraft Operators and Towers.

They will first be available as a prototype for evaluation and customisation.The deployment of the new interface will take place after the migration to the CFMU10.0. A planning for migration site per site will be defined in due time. To allow aphased rollout, the CFMU 9.0 RCA/CIA will be upgraded to remain compatible withCFMU version 10.0. It is however intended that in due time RCA/CIA interfaces willbe migrated to CHMI.

Impact : Important modifications to the layout, to the set-up andultimately to the services.The deployment will begin with the FMPs, starting after thesoftware release implementation, and later for the AircraftOperators (expected by mid 2005)A Deployment Plan will be provided in due time.

3.3.1.1. Functional changes

Objective : Benefiting from the new interface.

Description : The existing RCA/CIA functions will be migrated with only minorchanges. They will continue to be accessible by users accordingto their profile.

Impact : Better service.

3.3.1.2. Geographical display of CFMU airspace data

Objective : Give the possibility to display CFMU Environment data on a map.

Description : The Users will be in a position to display most of the geographicalelements available in the CFMU database (routes, points,aerodromes, airspace and sectors). Several controls will bepossible as for example, time, Flight Levels, zooming methods,customisation, etc...

EUROCONTROLC F M U


EXTERNALINTERFACES


16

Impact : Better information to Users.

3.3.1.3. Geographical display of the Traffic Load status (FMP only)

Objective : Geographical display of the Monitor query through the display ofthe load status on locations.

Description : 2-D projection of the locations (per layers). The colour status willbe similar (4 colours).

Impact : Better awareness of the traffic and capacity situation.

3.3.1.4. Geographical display of Regulations and average delays

Objective : Display of the Regulations and the average delay status.

Description : 2-D projection of the regulated areas. This geographical displaycorresponds to the delay status of the Monitoring query. Thecolour status will be similar (4 colours).

Impact : Better awareness of the regulated areas and of the impact ontraffic.

3.3.1.5. Geographical display of the flight path

Objective : Display of the flight route on a map.

Description : 2-D projection of the flight route.

Impact : Better representation of the flight path.

3.3.1.6. Graphical display of the vertical flight profile

Objective : Display of the flight profile.

Description : Vertical projection of the flight profile.

Impact : Better understanding of the CFMU flight profile.

3.3.1.7. Attention Getter

Objective : Display a warning when the CHMI is about to logout.

Description : A few seconds before the time out for de-connection, a window willbe opened indicating the de-connection time.

Impact : Avoid de-connection.

EUROCONTROLC F M U


EXTERNALINTERFACES


17

3.3.1.8. Miscellaneous improvements

Objective : Improve the readability of the data displayed by improving thelabels and the ergonomics.

Description : Improve the Print, Export and Sort, improve the graphical displayof counts, improve the display labels.

Impact : None.

3.3.1.9. Flight Plan filing assistance

Two new functions will be developed to improve the quality of filed flight plans.

3.3.1.9.1. Supplementary information for standard routes

Objective : To provide supplementary information for standard routes.

Description : Where available, supplementary information for a standard routewill be displayed.

Example : Off-load Maastricht via point SASKI.

Impact : It will facilitate selection by Aircraft Operators of standard routes.

3.3.1.9.2. Flight planning assistance tools

Objective : Provide assistance in flight plan route finding via Internet.

Description : Based on a limited amount of Flight Plan information (aerodromeof departure, aerodrome of destination, aircraft type, requestedspeed, requested flight level, estimated off-block time), the tool willprovide a list of possible valid routings for the flight.

Note : This is a first version of the Routing Assistance service calledDaedalus. This initial version will be delivered in the CFMU 10.0release on an evaluation basis. Enhanced versions are foreseenfor future CFMU releases. They will take into account thefeedback received from users.

Impact : It is expected that flight plan originators, using the tool, will be ableto file valid routes to IFPS and therefore increase the automatedprocessing rate.

3.3.2. Remote Client Application (RCA)

Objective : Allow a phased deployment of new interface.

Description : Upgrade for compatibility with CFMU10.0 . No functional changewill be implemented.

Impact : None.

EUROCONTROLC F M U


EXTERNALINTERFACES


18

3.3.3. CFMU Internet Application (CIA)

Objective : Allow a phased deployment of new interface.

Description : Upgrade for compatibility with CFMU10.0. No functional changewill be implemented.

Impact : None.

3.3.4. CFMU Interactive Reporting (CIR)

3.3.4.1. Gradual deployment of the CIR

Objective : To give access, via internet, to interactive reports on performanceindicators and archived data, which are stored in the CFMUDataWarehouse (DWH).This new system is called CIR.

Description : In addition with static reports, which are currently accessible inPDF format on the CFMU Web site (Statistics), the CIR will giveaccess to a set of pre-defined reports with different userinteractions:

- interactive selection of multiple criteria: time, areas, level ofdetail;

- zoom possibilities: navigation between global counts untilindividual flight data is reached;

- comparison facilities over several years, between locations(countries, airspaces, sectors, aerodromes), between operators(ANSPs, FMPs, AOs);

- swap possibilities between tabular and graphical display of theretrieved data;]

- export facilities of reported data into spreadsheets to allowfurther analysis.

The first set of reports will give information on Traffic and ATFM Delay counts,history of applied ATFM regulations and individual flights using archived data storedin the CFMU DataWarehouse (DWH).

The deployment will start in October 2004.

Impact : Access to CIR, for Customers included in the deployment targetaudience.

EUROCONTROLC F M U


DATA SYSTEMSDWH/ENV

6 May 2004 Edited & produced by the CFMU/User Relations Bureau Data Systems© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

19

3.4. DATA SYSTEMS3.4.1. Data Warehouse (DWH)

The CFMU DataWarehouse contains archived data produced by other CFMUoperational systems and derived Quality and Performance indicators.

3.4.1.1. Extended scope of archived data to prepare the monitoring ofnewly implemented features in other CFMU operational systems

Objective : To allow the post-operational analysis of newly implementedfeatures within other CFMU operational systems (ENV, IFPS, andETFMS), the scope of archived data, loaded in the DWH, will beextended.

Description : Extended scope of archived data in DWH relates to :

- partial logging of ETFMS data redistribution;

- logging of FUM, DPI, FLS messages;

- archive IFPL-ID in all exchanged messages.

Impact : No external impact.

3.4.1.2. Computation of new quality and performance indicators, accessible in futurereleases of the CIR

Objective : Systematic daily computation from archived data of newperformance indicators.

Description : New Quality and Performance indicators relate to :

- monitoring of Slot adherence per AO and ADEP;

- monitoring of Delays (AO Delay, ATFM Delay and ATCDelay);

- monitoring of Exempted flights;

- monitoring of Suspended flights (FAM);

- monitoring of efficiency of applied regulations.

Impact : New reports available in CIR and static reports accessible from theCFMU Web site, from late 2004.

6 May 2004 Edited & produced by the CFMU/User Relations Bureau Data Systems© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

20


EUROCONTROLC F M U


DICTIONARY

6 May 2004 Edited & produced by the CFMU/User Relations Bureau Abbreviations© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

21

4. DICTIONARY OF ABBREVIATIONS

ACRONYM DEFINITION

AATOT Anticipated Actual Take-Off TimeACA AUP/UUP Composition ApplicationACC Area Control CentreACH ATC Flight Plan ChangeADEP Aerodrome of DepartureADES Aerodrome of DestinationADEXP ATS Data Exchange PresentationAFIL Airborne Filed Flight PlanAFP ATC Flight Plan ProposalAFTN Aeronautical Fixed Telecommunication NetworkAIP Aeronautical Information PublicationAMC Airspace Management CellAME ATM Msg ExchangeANM ATFM Notification MessageAO Aircraft OperatorAOWIR Aircraft Operator WHAT-IF RerouteAPR Aircraft Operator Position ReportARCID Aircraft IdentificationARU Archive to UNIXATC Air Traffic ControlATCU Air Traffic Control UnitATFM Air Traffic Flow ManagementATM Air Traffic ManagementATS Air Traffic ServicesATTOT Aircraft Operator Target Take-Off TimeAUP Airspace Use PlanCASA Computer Assisted Slot AllocationCFL Conditional Flight LevelCFMU Central Flow Management Unit (Directorate)CHG Modification MessageCHMI Common Human Machine InterfaceCIA CFMU Internet ApplicationCIR CFMU Interactive ReportingCPM Correlated Position MessageCPR Correlated Position Report

EUROCONTROLC F M U


DICTIONARY


22

ACRONYM DEFINITION

CRAM Conditional Route Availability MessageCSO CFMU System OperationsCTFM ETFMS Current ModelCTO Calculated Time OverCTOT Calculated Take-Off TimeDCT DirectDLA Delay MessageDOF Date Of FlightDOM DomesticDPI Departure Planning InformationDWH DataWarehouseEAD European AIS DatabaseEAG European ATFM GroupEATMP The European Air Traffic Management ProgrammeELDT Estimated Landing TimeEOBD Estimated Off-Block DateEOBT Estimated Off-Block TimeERR Error MessageETFMS Enhanced Tactical Flow Management SystemETO Estimated Time OverETOT Estimated Take-Off TimeEUROCONTROL European Organisation for the Safety of Air NavigationFAM Flight Activation MonitoringFIR Flight Information RegionFLS Flight Suspension MessageFMD CFMU - Flow Management DivisionFMP Flow Management PositionFNM Flight Notification MessageFPD Flight Plan DataFPL Flight Plan Message (ICAO format)FSA First System Activation MessageFSH Flight Shift MessageFUM Flight Update MessageGAT General Air TrafficHMI Human Machine InterfaceIACH Individual ATC Flight Plan ChangesIAFP Individual ATC Flight Plan ProposalIACA International Air Carrier Association

EUROCONTROLC F M U


DICTIONARY


23

ACRONYM DEFINITION

IATA International Air Transport AssociationICAO International Civil Aviation OrganisationICD Interface Control DocumentIFPS Integrated Initial Flight Plan Processing SystemIFR Instrument Flight RulesINTL InternationalIOBD Initial Off-Block DateIOBT Initial Off-Block TimeMIL MilitaryMTOW Maximum Take-Off WeightNAT North Atlantic Region (ICAO)NEWCTOT New Calculated Take-Off TimeNEWETOT New Estimated Take-Off TimeNEWPTOT New Provisional Take-Off TimeNEWRTE New RouteOAT Operational Air TrafficOBT Off-Block TimeOPIF Operator InterfaceOPR OperatorORGMSG Original MassageORGN OriginalORGRTE Original RouteORM Operational Reply MessageOTS Organised Track SystemPC Personnel ComputerPFD Planned Flight DataPTOT Provisional Take-Off TimeRAD Route Availability DocumentRCA CFMU - Remote Client ApplicationRCAT Route CatalogueREA Ready MessageREGUL RegulationRFI Ready For Improvement MessageRJT Rerouteing Rejection MessageRPL Repetitive Flight PlanRQP Request Flight Plan MessageRRN Rerouteing Notification MessageRRP Rerouteing Proposal Message

EUROCONTROLC F M U


DICTIONARY


24

ACRONYM DEFINITION

RVR Runway Visual RangeRVSM Reduced Vertical Separation MinimumSAM Slot Allocation MessageSEP STAR Entry PointSID Standard Instrument DepartureSIP Slot Improvement Proposal MessageSIT Slot Issue TimeSITA Société Internationale de Télécommunications AéronautiquesSLC Slot Cancellation MessageSMM Slot Missed MessageSPA Slot Proposal Acceptance MessageSRJ Slot Improvement Proposal Rejection MessageSRM Slot Revision MessageSRS Standard Routeing SchemeSSR Secondary Surveillance RadarSTAR Standard Terminal Arrival RouteSWM SIP Wanted MessageTFV Traffic VolumeTIS Time to Insert the SequenceTITLE Message NameTRS Time to Remove from the SequenceTWR TowerUIR Upper Flight Information RegionURB CFMU - User Relations BureauUUP Updated Airspace Use PlanVFR Visual Flight RulesWTC Wake Turbulence Category

EUROCONTROLC F M U


ANNEXES

6 May 2004 Edited & produced by the CFMU/User Relations Bureau Annexes© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

25


26


6 May 2004 Edited & produced by the CFMU/User Relations Bureau Annex© 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

27

PRIMARY FIELD COMPOSITION OF TACTICAL ATFM MESSAGES EXCHANGE (1)

Message Field SAM SRM SLC SIP FLS DES RRP RRN ERR SMM SPA SRJ FCM RJT-TITLE 1 1 1 1 1 1 1 1 1 1 1 1 1 1-IFPLID 1 1 1 1 1 1 1 1 (1) (1) (1) (1) (1) (1)-ADDR (1) (1) (1) (1) (1) (1)-ARCID 1 1 1 1 1 1 1 1 (1) 1 1 1 1 1-ADEP 1 1 1 1 1 1 1 1 (1) 1 1 1 1 1-EOBD 1 1 1 1 1 1 1 1 (1) (1) (1) (1) (1) (1)-EOBT 1 1 1 1 1 1 1 1 (1) 1 1 1 1 1-IOBD (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1)-IOBT (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1)-CTOT 1 1 (1) (1) 1-NEWCTOT 1 1 (1) (1) 1-NEWPTOT (1) (1)-REJCTOT 1-REASON (1) (1) (1) (1) (1) (1) (1) (1) (1)-ADES 1 1 1 1 1 1 1 1 (1) 1 1 1 1 1-REGUL 1< 1< 1< 0<-ORGRTE 1 1-PTOT (1) (1)-NEWRTE 1 1-RRTEREF (1) 1 (1)-RVR (1) (1) (1) (1)-RESPBY 1 (1) 1 1-ORGMSG (1)-FILTIM 1-ERRFIELD 0<-MINLINEUP-COMMENT 0< 0< 0< 0< 0< 0< 0< 0< 0<-TAXITIME 1 1 1 1 1 1 1 1-REGCAUSE 1 1 0<

"1" means : exactly one field of the specified type is required a "blank cell" means : this field is not in a message"(1)" means : a single optional field of the specified type is allowed "n<" means : n or more occurrences of this field can appear in a message


28

PRIMARY FIELD COMPOSITION OF TACTICAL ATFM MESSAGES EXCHANGE (2) ATC/AIRPORT APPLICATION MESSAGES

Message Field SWM RFI REA Message Field FSA FUM-TITLE 1 1 1 -TITLE 1 1-ADDR -ACTYPE (1)-ADEP 1 1 1 -ADDR (1)-ADES 1 1 1 -ADEP 1 1-ARCID 1 1 1 -ADES 1 1-COMMENT -ARCID 1 1-CTOT -ELDT 1-EOBD (1) (1) (1) -EOBD (1) 1-EOBT 1 1 1 -EOBT (1) 1-ERRFIELD -ESTDATA 1-FILTIM -FLTSTATE 1-IFPLID (1) (1) (1) -FURTHRTE (1)-IOBD (1) (1) (1) -IFPLID (1) 1-IOBT (1) (1) (1) -POSITION 1-MINLINEUP (1) -REG (1)-NEWCTOT -STAR (1)-NEWPTOT-NEWRTE-ORGMSG-ORGRTE-PTOT-REASON-REGCAUSE-REGUL-REJCTOT-RESPBY-RRTEREF-RVR

"1" means : exactly one field of the specified type is required a "blank cell" means : this field is not in a message"(1)" means : a single optional field of the specified type is allowed "n<" means : n or more occurrences of this field can appear in a message


29

CORRELATION BETWEEN THE CFMU REASONS FOR REGULATION AND IATA DELAY CODESCFMU IATA

REASON FORREGULATION CODE REGULATION

LOCATION EXAMPLE CODE DELAY CAUSE

D 89 RESTRICTIONS AT AIRPORT OF DEPARTUREE 81 ATFM due to ATC ENROUTE DEMAND/CAPACITYATC Capacity CA

Demand exceeds the capacity83 ATFM due to RESTRICTION AT DESTINATION AIRPORT

D 89 RESTRICTIONS AT AIRPORT OF DEPARTUREE 82 ATFM due to ATC STAFF/EQUIPMENT ENROUTEATC Ind Action IA

Controllers’ strike83 ATFM due to RESTRICTION AT DESTINATION AIRPORT

ATC Routeings R E Phasing in of new procedures 81 ATFM due to ATC ENROUTE DEMAND/CAPACITY D 89 RESTRICTIONS AT AIRPORT OF DEPARTURE E 82 ATFM due to ATC STAFF/EQUIPMENT ENROUTE ATC Staffing S A

Illness; traffic delays on the highway 83 ATFM due to RESTRICTION AT DESTINATION AIRPORT

D 89 RESTRICTIONS AT AIRPORT OF DEPARTURE E 82 ATFM due to ATC STAFF/EQUIPMENT ENROUTE ATC Equipment T A

Radar failure; RTF failure 83 ATFM due to RESTRICTION AT DESTINATION AIRPORT

D 89 RESTRICTIONS AT AIRPORT OF DEPARTUREAccident/Incident A

ARWY23 closed due accident

83 ATFM due to RESTRICTION AT DESTINATION AIRPORT D 87 AIRPORT FACILITIES Aerodrome Capacity G A

Lack of parking; taxiway closure; areas closed formaintenance; demand exceeds the declared airport capacity 87 AIRPORT FACILITIES

De-Icing D D De-Icing 89 RESTRICTIONS AT AIRPORT OF DEPARTURE D 87 AIRPORT FACILITIES Equipment non-ATC E A Runway or taxiway lighting failure 87 AIRPORT FACILITIES D 98 INDUSTRIAL ACTION OUTSIDE OWN AIRLINE Ind Action non-ATC N A Firemen’s strike 98 INDUSTRIAL ACTION OUTSIDE OWN AIRLINE D 89 RESTRICTIONS AT AIRPORT OF DEPARTURE E 82 ATFM due to ATC STAFF/EQUIPMENT ENROUTE Military Activity M A

Brilliant Invader; ODAX 83 ATFM due to RESTRICTION AT DESTINATION AIRPORT

D 89 RESTRICTIONS AT AIRPORT OF DEPARTURESpecial Event P

AEuropean football cup; Heads of Government meetings

83 ATFM due to RESTRICTION AT DESTINATION AIRPORTD 89 RESTRICTIONS AT AIRPORT OF DEPARTUREE 73 WEATHER EN ROUTE OR ALTERNATEWeather WA

Thunderstorm; low visibility; X winds84 ATFM due to WEATHER AT DESTINATION

D 89 RESTRICTIONS AT AIRPORT OF DEPARTUREEnvironmental Issues V

ANoise

83 ATFM due to RESTRICTION AT DESTINATION AIRPORT D 89 RESTRICTIONS AT AIRPORT OF DEPARTURE E 81 ATFM due to ATC ENROUTE DEMAND/CAPACITY Other O A

Security alert 83 ATFM due to RESTRICTION AT DESTINATION AIRPORT


30


EUROCONTROLC F M U


ANNEXES


31

BIBLIOGRAPHY OF CFMU DOCUMENTS

Document Title LatestEdition No. Date Standard

Distribution

CFMU HANDBOOK BASIC PARTS

�� / �� GENERAL & CFMU SYSTEMS 8.0 18/02/02 amendments to all CFMU Users

�� / �� IFPS USERS MANUAL 8.0 18/02/02 amendments to all CFMU Users

�� / �� ATFM USERS MANUAL 9.0 14/04/03 amendments to all CFMU Users

�� / �� ADDRESSES UNDER REVIEW amendments to all CFMU Users

CFMU HANDBOOK SUPPLEMENTS

�� / �� PROVISION OF ENVIRONMENT DATA 4.0 23/08/01 amendments ONLY to FMP, ATS

�� RCA - Remote Client ApplicationReference Guide

1.0 27/08/03 amendments ONLY to FMP/AOwith a CFMU Terminal connection

with the RCA installed on their PCs

�� CFMU INTERNET APPLICATION (CIA)FLIGHT HANDLING USERS GUIDE

1.0 18/06/01 amendments ONLY to CLIENTSwith CIA SecurID Access

�� / �� FMP MANUAL for FMPs 3.0 27/03/00 amendments ONLY to FMD, FMP

OTHER CFMU DOCUMENTS

�� CFMU RELEASE NOTES CFMU 9/10 11/08/03 amendments to all CFMU Users

�� / �� CFMU NETWORK CONNECTION GUIDE 6.2 31/01/02 amendments to all CFMU Users

�� RPL INPUT APPLICATION USERS GUIDE 3.0 22/10/01 on request, to AOs

�� ACA USERS GUIDE FOR AMC 6.0 18/04/01 amendments ONLY to AMC

ADDITIONAL COPIES MAY BE REQUESTED :

� from the EUROCONTROL LIBRARYPhone : ++32 2 729 3639 / 3023 - FAX : ++32 2 729 9109

�� on the CFMU web site at http://www.cfmu.eurocontrol.int

�� on request by mailto:[email protected]




32


EUROCONTROLC F M U


ANNEXES


33

More information is given overleaf concerning the completion of this form.

CFMUURB

AGENCY CONTACTS DATABASECFMU CLIENTS UPDATE FORM


Submitted by 27-05-04

ORGANISATION

English name

Usual name

Acronym

Type

GENERAL ADDRESS

Street line 1

Street line 2

Street line 3

P.O. Box Postcode P.O. Box

Postcode City

Country ICAO Area Code Phone Fax

e-mail Web

AFTN SITA IATA ICAO

PERSON

Last name (English)

Last name (Original)

First name Type

Title Mr Ms Other

Function

Unit

Office

Phone Fax

e-mail_1 e-mail_2

Mobile

GROUP RESERVED FOR EUROCONTROL CFMU URB/RQP

Name

Status Member Observer Participant Document

CFMU DOC required? Yes No

CFMU WPs required? Yes No

Labels Yes No

e-mail Yes NoMailingFax Yes No


EUROCONTROLC F M U


ANNEXES


34

ORGANISATION

English Name Name of the organisation transcribed in English.

Usual nameName of the organisation, as it is generally used to addressthe organisation. Mostly in the original language of theorganisation, sometimes in English or another language, inwhich the organisation is usually addressed.

Acronym Short name

Type

Government Body Examples: Ministry of Transport, Ministry of Defence, Embassy,Permanent Representation to E.U., ...

Regulatory Authority / C.A.A. Examples: C.A.A., Military regulatory Authority, Accident andIncident Investigation Offices/Bureaus, ...

Air Navigation Service ProviderExamples: Headquarters, Director Of Operations, Head ofOperations, FMP, FMP Adjacent, ARO, AIS, Tower, AMC,Meterological services, Training, ...

International Organisation Examples: EC, ECAC, EUROCAE, ESA, BEI, EBRD, ISO,ICAO, United Nations, NATO, EUROCONTROL, …

Association / Federation Examples: ACI, IATA, CANSO, ETF, ATC EUC, IFATCA,AECMA, AEA, IFALPA, IACA, FATSEA, ERAA, …

Aircraft OperatorAll airspace users: Passenger and Cargo airlines,Business/Corporate Aviation, General Aviation, Air workCompanies, Flying Clubs, Military Aviation, …

Handling Agent Organisations which are not AOs themselves but provide flightplanning or ATFM messages exchange services to other AOs.

Airports & Airport Services Examples: Fraport, BIAC, Aéroports de Paris, …

IndustryExamples: ATM System manufacturers, Communicationsystem manufacturers, Aircraft and Aircraft Enginemanufacturers, Avionics, ...

Consultant Examples: Microsoft, Oracle, consultancy companies

GENERAL ADDRESS & PERSON

PhoneFaxMobile

Area code separated by a space from local local.Local code formatting = 3 digits, space, 4 digits.For example : 2 729 4717 (in Belgium)Area Code = 2 - Local Code = 729 4717

Web URL of the organisation’s website.AFTN AFTN code of the Organisation (capital letters).SITA SITA code of the Organisation (capital letters).IATA IATA code of the Organisation (capital letters).ICAO 3- or 4-letter ICAO code specific to the client (capital letters).

ICAO Area2-letter code for the ICAO location of the organisation (capitalletters). This field is required, because some countries – e.g.China - are divided in several regions with a different ICAOarea code.

Cfmu Release Notes 10v2

Documents

Transcript of Cfmu Release Notes 10v2