Cfmu Release Notes 10v2

EUROCONTROL CFMU
CFMU 10 - RELEASE NOTES

Planned for Implementation in 2004
Doc. Reference CFMU_10RL
EUROCONT OL R
PLANNED FOR IMPLEMENTATION in 2004 Revised May 2004
http://www.cfmu.eurocontrol.int
6 May 2004 Edited & produced by the CFMU/User Relations Bureau 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL) i
2003 European Organisation for the Safety of Air Navigation (EUROCONTROL). All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior permission of EUROCONTROL.
6 May 2004
Edited & produced by the CFMU/User Relations Bureau 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)
ii
EUROCONTROL CFMU

TABLE
1.
1.1.
OF
CONTENTS
INTRODUCTION ............................................................................................1
General .................................................................................................................... 1
2. 3.
3.1. 3.1.1. 3.1.1.1. 3.1.1.2. 3.1.1.3. 3.1.1.4. 3.1.1.5. 3.1.1.6. 3.2. 3.2.1. 3.2.2. 3.2.3.
PLANNING .....................................................................................................3 CFMU 10.0 ....................................................................................................5

FLIGHT PLAN SYSTEMS ...................................................................................... 5 Integrated Initial Flight Plan Processing System (IFPS) ........................................... 5 En-route STAY indicator .......................................................................................... 5 Mode S IFP indicator................................................................................................ 6 Flight trajectory calculation in IFPS .......................................................................... 6 EUR RVSM entry/exit conditions checking............................................................... 7 En-route DCT checking improvements..................................................................... 7 AFP processing........................................................................................................ 8 ENHANCED TACTICAL FLOW MANAGEMENT SYSTEM (ETFMS) ....................... 9 ETFMS redistribution (to the ATS system) ............................................................... 9 Flight Update Message (FUM) ................................................................................. 9 Introduction of the IFPLID in all ATFM Messages to / from ETFMS ....................... 11
Withdrawn Requirement (ATFM Messages for a flight becoming non-regulated shortly before departure) ... 12 3.2.4. 3.2.5. 3.2.6. 3.2.7. 3.3. 3.3.1. 3.3.1.1. 3.3.1.2. 3.3.1.3. 3.3.1.4.
6 May 2004
Flight Suspension Message will contain the Identifier of Regulation Causing Suspension ............................................................................................................ 13 Modification of the comment of the FLS message ................................................. 13 Process APL/ACH/AFIL messages as updates to the Current flight model route... 14 Departure Planning Information ............................................................................. 14 EXTERNAL INTERFACES.................................................................................... 15 New CFMU Interface Common Human Machine Interface (CHMI) ..................... 15 Functional changes ................................................................................................ 15 Geographical display of CFMU airspace data ........................................................ 15 Geographical display of the Traffic Load status (FMP only).................................... 16 Geographical display of Regulations and average delays ...................................... 16
Edited & produced by the CFMU/User Relations Bureau 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL) iii
EUROCONTROL CFMU

3.3.1.5. 3.3.1.6. 3.3.1.7. 3.3.1.8. 3.3.1.9. 3.3.1.9.1. 3.3.1.9.2. 3.3.2. 3.3.3. 3.3.4. 3.3.4.1. 3.4. 3.4.1. 3.4.1.1. 3.4.1.2.
Geographical display of the flight path ................................................................... 16 Graphical display of the vertical flight profile .......................................................... 16 Attention Getter...................................................................................................... 16 Miscellaneous improvements ................................................................................ 17 Flight Plan filing assistance.................................................................................... 17 Supplementary information for standard routes...................................................... 17 Flight planning assistance tools.............................................................................. 17 Remote Client Application (RCA) ........................................................................... 17 CFMU Internet Application (CIA) ............................................................................ 18 CFMU Interactive Reporting (CIR) ......................................................................... 18 Gradual deployment of the CIR.............................................................................. 18 DATA SYSTEMS .................................................................................................. 19 Data Warehouse (DWH) ...................................................................................... 19 Extended scope of archived data to prepare the monitoring of newly implemented features in other CFMU operational systems ......................................................... 19 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 FORM mailto:cfmu.opsdoc@eurocontrol.int
6 May 2004
iv
EUROCONTROL CFMU

1.
1.1.
INTRODUCTION
General This document describes the new or modified functions that will be delivered by the CFMU as part of the CFMU 10 software release planned in November 2004. This document replaces the document issued in August 2003. The main editorial changes are due to the removal of the changes related to CFMU 9.3, which were implemented 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 Management Unit (CFMU) Systems with advance notice of modifications that will have an impact upon their operational procedures and/or systems. The CFMU 10 release includes many changes arising from different sources and co-ordinated through the European ATFM Group and its sub-groups.
It should be noted that additional copies of this document could be obtained from the CFMU Website at :
http://www.cfmu.eurocontrol.int
6 May 2004
INTRO
INTENTIONALLY LEFT BLANK
6 May 2004
INTRO
EUROCONTROL CFMU

PLANNING
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 after November 2004 and according to a planning that will be discussed with the different involved partners: a) b) c) d) e) f) ETFMS redistribution for ATC Service providers, Implementation of the new CFMU external interface replacing RCA, Flight planning assistance via IFPUV, Provision of the Flight Update Message (FUM), Reception of the Departure Planning Information Message (DPI), Deployment of the tool for Towers.
6 May 2004
Planning
6 May 2004
Planning
EUROCONTROL CFMU
CFMU 10.0 - RELEASE NOTES

FLIGHT PLAN SYSTEMS IFPS/RPL/RCAT
3. 3.1.
3.1.1.
3.1.1.1.
CFMU 10.0 FLIGHT PLAN SYSTEMS

Integrated Initial Flight Plan Processing System (IFPS)
En-route STAY indicator Objective : To enable time delays associated with certain special en-route activities such as training flights, air-air refuelling, photographic missions etc. to be entered in the Route Field of a FPL thus enabling 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 indicator shall be inserted in Field 15 of the FPL between the point of entry in 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 the same. Example : MCT STAY1/0030 MCT
To allow several STAY indicators to be inserted in the route of a flight a number from 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 STAY area 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 inserted in 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 as the 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 IFPS Zone. The STAY indicator is not allowed in Repetitive Flight Plans. Impact : All STAY information (STAY and STAYINFO) will be output by IFPS to external client systems in either ICAO or ADEXP format according to the client requirement. Modifications in the external client systems may be required in order to allow processing of the STAY information. Procedures for the use of the STAY indicator should be noted and complied with by the flight plan originators.
6 May 2004
Edited & produced by the CFMU/User Relations Bureau
Flight Plan Systems
2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)
EUROCONTROL CFMU

3.1.1.2.
Mode S IFP indicator Objective : To allow ATC to determine to which flights a Mode A conspicuity code (A1000) can be assigned in order to save Mode A discrete codes and permit them to be allocated to other flights.
Description : For Mode S equipped flights (letter S in Field 10b), the IFPS will insert the IFP indicator MODESASP in the output flight plan in the following conditions :
for a flight that takes place entirely within the Mode S declared airspace and
Example
for a flight that enters the declared Mode S airspace and remains entirely within the airspace for the rest of the flight. : (FPL-ABC443-IS -A319/M-SDEIRWY/S -EDDF1515 -N0416F220 KIR G104 RUWER G104 TILGA UG104 DIK UW64 BATTY -EBBR0032 -EET/EBUR0017 EBBU0018 DOF/030724 IFP/MODESASP) : Although this mechanism will be implemented in IFPS in the CFMU 10.0 release timeframe, the output of the Mode S IFP indicator will be synchronised with the implementation of Mode S operations by the States concerned. : ATC centres that implement Mode S operations may process the Mode S IFP indicator in order to use the information provided in the code allocation process.
Note
Impact
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 the trajectory of a flight will be implemented for IFPS. The following elements are included:
Use of Profile Tuning Restrictions (currently known as CFLs, Conditional Flight Levels) to allow a better tuning of the IFPS profile. The taxitime will be included in the time profile calculation. : The IFPS addressing is expected to improve. No impact on external client systems.
Impact
6 May 2004
Flight Plan Systems
EUROCONTROL CFMU

3.1.1.4.
EUR RVSM entry/exit conditions checking Objective : To adapt the RVSM Flight Planning requirements and the related IFPS checking to an expanded RVSM area.
Description : Since the introduction of the EUR RVSM, there has been a requirement for Aircraft Operators to file, in FPLs, published entry/exit points to/from EUR RVSM region. The introduction of RVSM in the ICAO MID region and the proposed expansion of EUR RVSM into the Russian Federation have required that the entry/exit criteria be revisited. The current IFPS technology allows the detection of the entry/exit of a flight into/from an RVSM airspace without the explicit mention in the Flight plan of an RVSM entry/exit point. Therefore, the IFPS software will be adapted to allow disabling of the current checking of RVSM entry/exit conditions (RVSM entry/exit point and flight level). IFPS will continue to accept and process cruising flight level changes indicated over points on the boundary of the EUR RVSM airspace as normal flight level changes. In parallel, meetings are taking place with ICAO Paris office to formulate a proposed revision of ICAO Doc 7030 and adapt the procedure to the new possibilities. A proposed amendment is to be circulated to ICAO member States for approval. Once an agreement is reached, further information will be provided to all interested parties on the updated RVSM Flight Planning 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 operations in 2001, in the CFMU 7.0 release. The following improvements to the en-route DCT checking will be implemented in the CFMU 10.0 release. 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 a given FIR/UIR or NAS. For example, in a given FIR, a DCT limit of 20 NM could be defined above FL70 and a DCT limit of 300NM could be defined below FL70. When a planned DCT segments crosses the horizontal or vertical boundary between two airspaces for which a DCT limit is defined, IFPS shall check that the entire DCT segment is shorter than each one of the two DCT limits. The two airspaces could be FIRs, UIRs, NASs or a flight level band of such airspaces.
6 May 2004 Edited & produced by the CFMU/User Relations Bureau Flight Plan Systems 7
EUROCONTROL CFMU

It shall be possible to exclude one or several types of flight from a given en-route DCT limit, be it a general DCT limit for an FIR/NAS or a DCT limit for flight level band in an FIR/NAS. That shall allow for example military flights to be excluded from a general DCT limit of 20 NM in a given FIR. The IFPS shall compare the type of flight indicated in Field 8b of the ICAO flight plan against the list of types of flight that 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 a known and available airway segment. If candidate airways are identified but they are all not available at the time and the requested level the flight plan shall be invalidated by IFPS. Impact : No impact on external systems. The new additions to the en-route DCT checking are expected to provide more flexibility to States in managing the DCT limits for their national airspace. 3.1.1.6. AFP processing Objective : To improve the AFP (ATC Flight Plan Proposal) messages processing.
Description : Currently the estimate point included in an AFP message has to be explicitly mentioned in the Route field (ICAO Field 15) of the AFP message. With effect from the CFMU 10.0 release, the estimate point need no longer be explicitely specified provided it is a point along an ATS route mentioned in the Route Field. The IFPLID will be included as an optional field in the syntax of AFP messages in ADEXP format. In the CFMU 10.0 release, IFPS will not use the IFPLID for correlation. This upgrade will be implemented in a future software release. The change in CFMU 10.0 is meant to allow the AFP originator to start including the IFPLID in AFP messages, in a release that is not synchronised with the IFPS release. Note: It should be noted that the IFPLID should always be inserted in 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 is highly recommended to be avoided. The ARCTYP will be made an optional field in the syntax of AFP messages in ADEXP format. This change will allow AFP originators to omit the aircraft type in AFP messages in case the aircraft type does not change. However, the aircraft type will continue to be compulsory information in AFP messages for missing flight plans. Impact : AFP messages originators may want to consider these changes in the process of AFP filing to IFPS.
6 May 2004
Flight Plan Systems
EUROCONTROL CFMU

ETFMS
3.2.
3.2.1.
ENHANCED TACTICAL FLOW MANAGEMENT SYSTEM (ETFMS)

ETFMS redistribution (to the ATS system) Objective : To re-distribute the current ETFMS flight data to Air Navigation Service Providers (ANSPs).
Description : In the ETFMS implementation plan the second phase is devoted to the redistribution of information to ANSPs. ETFMS data redistribution will happen when specific events, which can normally cause an update of the ETFMS flight database, occur. As a result, and after having processed such an event, the system will construct and send an ETFMS Flight 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 Progress Messages document. Events that can trigger a data distribution can be due to the reception of incoming messages (flight plan messages or ATFM messages), to system operators modifying flight or CFMU environment data, or to system timeouts 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 broadcast each received EFD to all ETFMS entry nodes (enhanced to receive EFD input) included in the distribution. Each entry node system will process the EFDs selected by the associated ANSP, on the basis of filtering functions applied on selected data included in each EFD message. These filtering functions are specified in the document ICD (Interface Control Document) for ETFMS data re-distribution. The filtering configuration is part of the customisation of the Entry Node. For a given Entry Node, the configuration includes the selection of the filtering functions and for each function, the specification of the applicable values. Impact : ANSPs willing to receive the ETFMS flight data shall inform the CFMU, 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 through the exchange of flight plan data.
Description : An information exchange process has been defined to enable better awareness between airports and the CFMU. Airports are looking for early updates of the landing time of flights based on ETFMS data. 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. It contains the following main items :
the Estimated Landing Time (ELDT) The ELDT will be the CFMU estimation of the aircrafts landing time, not taking into account any unplanned changes to the flight such as holding close to the aerodrome of destination. It is the most accurate value that is known to
Edited & produced by the CFMU/User Relations Bureau ETFMS 9
6 May 2004
EUROCONTROL CFMU

ETFMS
ETFMS based upon its own flight profile calculation and flight data updates received from ATC. the STAR Entry Point or the last point in the flight plan route with the corresponding Estimated Time Over (ETO or CTO or ATO). a flight status field that can be used as an accuracy indicator of the provided estimates.
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 the Aerodrome of Destination (ADES) and will follow the standards already used for ATS 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. In most cases the trigger moment (ELDT 3 hours) will be based upon flight plan data. However in case the ELDT based upon the latest received airborne information (ELDT_airborne) is earlier than ELDT from flight plan data then the FUM will be sent at ELDT_airborne 3 hours. This FUM will take into account the last received DLA messages and the possible published ATFM delay. change of the ELDT of at least X minutes X will be a system parameter in the range 5 15 minutes. important flight status changes such as : pre-active, airborne, suspended. : A procedure will be published after the implementation of the CFMU10 software version describing the procedure to follow to get access to the FUM message.
Impact
6 May 2004
ETFMS
10
EUROCONTROL CFMU

ETFMS
3.2.3.
Introduction of the IFPLID in all ATFM Messages to / from ETFMS Objective : Adding the IFPLID to the ATFM messages will enable the receivers 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 (except the 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 ETFMS will accept the IFPLID when provided in an incoming message in ADEXP 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. : The insertion of the IFPLID is only expected in ADEXP format messages that are generated systematically. It is not expected, or even desired, that the IFPLID should be inserted into messages that are manually created, either ADEXP or ICAO format.
b)
NOTE
Example of an ATFM message received by CFMU -TITLE FCM -IFPLID AA36655760 -ARCID ABC101 -ADEP EGLL -ADES LMML -EOBD 021010 -EOBT 0845 -RVR 2000 Impact optional field
: Client systems should be adapted to receive and use the IFPLID field in the messages referred to in a) above.
Edited & produced by the CFMU/User Relations Bureau ETFMS 11
6 May 2004
EUROCONTROL CFMU

ETFMS
Client systems that systematically generate the messages referred to in b) above should include the IFPLID. For ANSP clients that do not yet receive flight plans in ADEXP format, the IFPLID could be extracted from the first correlated CASA message (these messages only exist in ADEXP format e.g. SAM, SRM, etc.). For Aircraft Operators, the IFPLID could be extracted from the ACK message or from the first correlated CASA message (these messages only exist in ADEXP format e.g. SAM, SRM, etc.). Withdrawn Requirement 3.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 outside the period. Since the flight can no longer comply with the Flight plan EOBT due to this last regulation there is a need to use more realistic information. Instead of issuing an SLC, 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 tolerance window. 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 to confirm the EOBT the flight can make. Then, ETFMS will issue a new SRM or an SLC 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 IS NO LONGER AFFECTED BY REGULATION UZZU11 -TAXITIME 0020 -REGCAUSE CE81
6 May 2004 Edited & produced by the CFMU/User Relations Bureau ETFMS 12
EUROCONTROL CFMU

ETFMS
Impact 3.2.4.
: Adaptation to the procedures.
Flight Suspension Message will contain the Identifier of Regulation Causing Suspension Objective : To inform the AOs of the location that is giving them problems.
Description : The identifier of the concerned regulations together with the corresponding regulation cause will be inserted in the FLS message to inform the AOs and ANSPs of the location, as is done for the slot messages. These fields are optional because the suspension is not always caused by a regulation e.g. Flight Activation 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 3.2.5. : It is expected a reduction of the calls to the help desk. Change in message format.
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 RVR UNKNOWN, instead of RVR CRITERIA NOT MET (which will remain 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
6 May 2004
ETFMS
13
EUROCONTROL CFMU

ETFMS
Impact 3.2.6.
: ATFM users shall adapt their procedures and systems as required.
Process APL/ACH/AFIL messages as updates to the Current flight model route Objective : Better processing of the IAPL/IACH/IAFIL messages to avoid losing all previously received information from ATC such as FSA, CPR, etc.
Description : To update the Current flight model, ETFMS will use the list of points of the route only from the point in the ESTDATA field onwards, in a similar way as the FURTHRTE-field of the FSA message. Impact : No impact on external systems. Past and archived profiles will better reflect the profile used in the Tactical phase.
3.2.7.
Departure Planning Information Objective : Initial development of the message process to enable ATFM system to receive updates from airports. This action is part of the Airport CDM process.
Description : In collaboration with the Aircraft Operators, an airport may provide taxi time and more accurate take-off time for outbound flights. Various instances of the DPI message are being developed by the CFMU to permit airports to provide more accurate information to the CFMU for departing traffic. The instances comprise the Early DPI (E-DPI) providing information before the slot issue time, the ADPI providing information when the flight is under local ATC responsibility and the T-DPI providing information for the in between stage. The CFMU release will enable the reception and parsing of such messages. The related operational procedures will be developed as part of the evaluation of the impact of these messages and they will be communicated in due time.
Impact
: No impact on external systems. Format of the messages will be communicated to the participants of the evaluation.
6 May 2004
ETFMS
14
EUROCONTROL CFMU

EXTERNAL INTERFACES
3.3.
3.3.1.
EXTERNAL INTERFACES
New CFMU Interface Common Human Machine Interface (CHMI) Objective : Improve services through technological evolution. CFMU 10.0 will be the start point of the deployment of the new interface for external users. This implies a change of technology (move from C++ to Java based applications).
Description :
This first version of CHMI for external users will include the current RCA/CIA functions and in addition will give access to the ENV information and to the Map functionality. The main benefit of this new interface will be the possibility to get graphical representations 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 CFMU 10.0. A planning for migration site per site will be defined in due time. To allow a phased rollout, the CFMU 9.0 RCA/CIA will be upgraded to remain compatible with CFMU version 10.0. It is however intended that in due time RCA/CIA interfaces will be migrated to CHMI. Impact : Important modifications to the layout, to the set-up and ultimately to the services. The deployment will begin with the FMPs, starting after the software release implementation, and later for the Aircraft Operators (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 minor changes. They will continue to be accessible by users according to their profile. Impact 3.3.1.2. : Better service.
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 geographical elements available in the CFMU database (routes, points, aerodromes, airspace and sectors). Several controls will be possible as for example, time, Flight Levels, zooming methods, customisation, etc...
6 May 2004 Edited & produced by the CFMU/User Relations Bureau External Interfaces 15 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)
EUROCONTROL CFMU

EXTERNAL INTERFACES
Impact 3.3.1.3.
: Better information to Users.
Geographical display of the Traffic Load status (FMP only) Objective : Geographical display of the Monitor query through the display of the load status on locations.
Description : 2-D projection of the locations (per layers). The colour status will be similar (4 colours). Impact 3.3.1.4. : Better awareness of the traffic and capacity situation.
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 display corresponds to the delay status of the Monitoring query. The colour status will be similar (4 colours). Impact : Better awareness of the regulated areas and of the impact on traffic.
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 3.3.1.6. : Better representation of the flight path.
Graphical display of the vertical flight profile Objective : Display of the flight profile.
Description : Vertical projection of the flight profile. Impact 3.3.1.7. : Better understanding of the CFMU flight profile.
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 will be opened indicating the de-connection time. Impact : Avoid de-connection.
6 May 2004
External Interfaces
16
EUROCONTROL CFMU

EXTERNAL INTERFACES
3.3.1.8.
Miscellaneous improvements Objective : Improve the readability of the data displayed by improving the labels and the ergonomics.
Description : Improve the Print, Export and Sort, improve the graphical display of counts, improve the display labels. Impact 3.3.1.9. : None.
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 route will be displayed. Example Impact 3.3.1.9.2. : Off-load Maastricht via point SASKI. : It will facilitate selection by Aircraft Operators of standard routes.
Flight planning assistance tools Objective : Provide assistance in flight plan route finding via Internet.
Description : Based on a limited amount of Flight Plan information (aerodrome of departure, aerodrome of destination, aircraft type, requested speed, requested flight level, estimated off-block time), the tool will provide a list of possible valid routings for the flight. Note : This is a first version of the Routing Assistance service called Daedalus. This initial version will be delivered in the CFMU 10.0 release on an evaluation basis. Enhanced versions are foreseen for future CFMU releases. They will take into account the feedback received from users. : It is expected that flight plan originators, using the tool, will be able to file valid routes to IFPS and therefore increase the automated processing rate.
Impact
3.3.2.
Remote Client Application (RCA)

Objective : Allow a phased deployment of new interface.
Description : Upgrade for compatibility with CFMU10.0 . No functional change will be implemented. Impact
6 May 2004
: None.
Edited & produced by the CFMU/User Relations Bureau External Interfaces 17
EUROCONTROL CFMU

EXTERNAL INTERFACES
3.3.3.
CFMU Internet Application (CIA)

Objective : Allow a phased deployment of new interface.
Description : Upgrade for compatibility with CFMU10.0. No functional change will be implemented. Impact : None.
3.3.4.
3.3.4.1.
CFMU Interactive Reporting (CIR)

Gradual deployment of the CIR Objective : To give access, via internet, to interactive reports on performance indicators and archived data, which are stored in the CFMU DataWarehouse (DWH). This new system is called CIR.
Description : In addition with static reports, which are currently accessible in PDF format on the CFMU Web site (Statistics), the CIR will give access to a set of pre-defined reports with different user interactions:
interactive selection of multiple criteria: time, areas, level of detail; zoom possibilities: navigation between global counts until individual 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 the retrieved data;] export facilities of reported data into spreadsheets to allow further 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 stored in the CFMU DataWarehouse (DWH). The deployment will start in October 2004. Impact : Access to CIR, for Customers included in the deployment target audience.
6 May 2004
External Interfaces
18
EUROCONTROL CFMU

DATA SYSTEMS DWH/ENV
3.4.
3.4.1.
DATA SYSTEMS
Data Warehouse (DWH)
The CFMU DataWarehouse contains archived data produced by other CFMU operational systems and derived Quality and Performance indicators.
3.4.1.1.
Extended scope of archived data to prepare the monitoring newly implemented features in other CFMU operational systems Objective
of
: To allow the post-operational analysis of newly implemented features within other CFMU operational systems (ENV, IFPS, and ETFMS), the scope of archived data, loaded in the DWH, will be extended.
Description : Extended scope of archived data in DWH relates to :
Impact 3.4.1.2.
partial logging of ETFMS data redistribution; logging of FUM, DPI, FLS messages; archive IFPL-ID in all exchanged messages.
: No external impact.
Computation of new quality and performance indicators, accessible in future releases of the CIR Objective : Systematic daily computation from archived data of new performance indicators.
Description : New Quality and Performance indicators relate to :
Impact
monitoring of Slot adherence per AO and ADEP; monitoring of Delays (AO Delay, ATFM Delay and ATC Delay); monitoring of Exempted flights; monitoring of Suspended flights (FAM); monitoring of efficiency of applied regulations.
: New reports available in CIR and static reports accessible from the CFMU Web site, from late 2004.
6 May 2004
Data Systems
19
6 May 2004
Data Systems
20
EUROCONTROL CFMU

DICTIONARY
4.
DICTIONARY OF ABBREVIATIONS
ACRONYM DEFINITION
Anticipated Actual Take-Off Time AUP/UUP Composition Application Area Control Centre ATC Flight Plan Change Aerodrome of Departure Aerodrome of Destination ATS Data Exchange Presentation Airborne Filed Flight Plan ATC Flight Plan Proposal Aeronautical Fixed Telecommunication Network Aeronautical Information Publication Airspace Management Cell ATM Msg Exchange ATFM Notification Message Aircraft Operator Aircraft Operator WHAT-IF Reroute Aircraft Operator Position Report Aircraft Identification Archive to UNIX Air Traffic Control Air Traffic Control Unit Air Traffic Flow Management Air Traffic Management Air Traffic Services Aircraft Operator Target Take-Off Time Airspace Use Plan Computer Assisted Slot Allocation Conditional Flight Level Central Flow Management Unit (Directorate) Modification Message Common Human Machine Interface CFMU Internet Application CFMU Interactive Reporting Correlated Position Message Correlated Position Report
Edited & produced by the CFMU/User Relations Bureau 2003 European Organisation for the Safety of Air Navigation (EUROCONTROL) Abbreviations 21
AATOT ACA ACC ACH ADEP ADES ADEXP AFIL AFP AFTN AIP AMC AME ANM AO AOWIR APR ARCID ARU ATC ATCU ATFM ATM ATS ATTOT AUP CASA CFL CFMU CHG CHMI CIA CIR CPM CPR
6 May 2004
EUROCONTROL CFMU

DICTIONARY
ACRONYM
CRAM CSO CTFM CTO CTOT DCT DLA DOF DOM DPI DWH EAD EAG EATMP ELDT EOBD EOBT ERR ETFMS ETO ETOT EUROCONTROL FAM FIR FLS FMD FMP FNM FPD FPL FSA FSH FUM GAT HMI IACH IAFP IACA
6 May 2004
DEFINITION
Conditional Route Availability Message CFMU System Operations ETFMS Current Model Calculated Time Over Calculated Take-Off Time Direct Delay Message Date Of Flight Domestic Departure Planning Information DataWarehouse European AIS Database European ATFM Group The European Air Traffic Management Programme Estimated Landing Time Estimated Off-Block Date Estimated Off-Block Time Error Message Enhanced Tactical Flow Management System Estimated Time Over Estimated Take-Off Time European Organisation for the Safety of Air Navigation Flight Activation Monitoring Flight Information Region Flight Suspension Message CFMU - Flow Management Division Flow Management Position Flight Notification Message Flight Plan Data Flight Plan Message (ICAO format) First System Activation Message Flight Shift Message Flight Update Message General Air Traffic Human Machine Interface Individual ATC Flight Plan Changes Individual ATC Flight Plan Proposal International Air Carrier Association
EUROCONTROL CFMU

DICTIONARY
ACRONYM
IATA ICAO ICD IFPS IFR INTL IOBD IOBT MIL MTOW NAT NEWCTOT NEWETOT NEWPTOT NEWRTE OAT OBT OPIF OPR ORGMSG ORGN ORGRTE ORM OTS PC PFD PTOT RAD RCA RCAT REA REGUL RFI RJT RPL RQP RRN RRP
6 May 2004
DEFINITION
International Air Transport Association International Civil Aviation Organisation Interface Control Document Integrated Initial Flight Plan Processing System Instrument Flight Rules International Initial Off-Block Date Initial Off-Block Time Military Maximum Take-Off Weight North Atlantic Region (ICAO) New Calculated Take-Off Time New Estimated Take-Off Time New Provisional Take-Off Time New Route Operational Air Traffic Off-Block Time Operator Interface Operator Original Massage Original Original Route Operational Reply Message Organised Track System Personnel Computer Planned Flight Data Provisional Take-Off Time Route Availability Document CFMU - Remote Client Application Route Catalogue Ready Message Regulation Ready For Improvement Message Rerouteing Rejection Message Repetitive Flight Plan Request Flight Plan Message Rerouteing Notification Message Rerouteing Proposal Message
EUROCONTROL CFMU

DICTIONARY
ACRONYM
RVR RVSM SAM SEP SID SIP SIT SITA SLC SMM SPA SRJ SRM SRS SSR STAR SWM TFV TIS TITLE TRS TWR UIR URB UUP VFR WTC Runway Visual Range
DEFINITION
Reduced Vertical Separation Minimum Slot Allocation Message STAR Entry Point Standard Instrument Departure Slot Improvement Proposal Message Slot Issue Time Socit Internationale de Tlcommunications Aronautiques Slot Cancellation Message Slot Missed Message Slot Proposal Acceptance Message Slot Improvement Proposal Rejection Message Slot Revision Message Standard Routeing Scheme Secondary Surveillance Radar Standard Terminal Arrival Route SIP Wanted Message Traffic Volume Time to Insert the Sequence Message Name Time to Remove from the Sequence Tower Upper Flight Information Region CFMU - User Relations Bureau Updated Airspace Use Plan Visual Flight Rules Wake Turbulence Category
6 May 2004
Abbreviations
24
EUROCONTROL CFMU

ANNEXES
6 May 2004
Annexes
25
6 May 2004
Annexes
26
PRIMARY FIELD COMPOSITION OF TACTICAL ATFM MESSAGES EXCHANGE (1) Message Field
-TITLE -IFPLID -ADDR -ARCID -ADEP -EOBD -EOBT -IOBD -IOBT -CTOT -NEWCTOT -NEWPTOT -REJCTOT -REASON -ADES -REGUL -ORGRTE -PTOT -NEWRTE -RRTEREF -RVR -RESPBY -ORGMSG -FILTIM -ERRFIELD -MINLINEUP -COMMENT -TAXITIME -REGCAUSE "1" "(1)" 0< 1 1 0< 1 1 0< 1 0< 1 0< 1 0< a "blank cell" means : "n<" means : this field is not in a message n or more occurrences of this field can appear in a message 0< 1 0< 1 0< 1 0< (1) (1) 1 (1) (1) 1 1 (1) 1 0< (1) 1 1< (1) 1 1< (1) 1 (1) 1 1< (1) 1 0< 1 (1) 1 (1) 1 (1) 1 1 (1) (1) (1) 1 (1) 1 (1) 1 (1) (1) 1 1 1 1 1
SAM
1 1 (1) 1 1 1 1 (1) (1) 1
SRM
1 1 (1) 1 1 1 1 (1) (1) 1
SLC
1 1 (1) 1 1 1 1 (1) (1)
SIP
1 1 (1) 1 1 1 1 (1) (1) 1 1
FLS
1 1 (1) 1 1 1 1 (1) (1)
DES
1 1 (1) 1 1 1 1 (1) (1)
RRP
1 1 1 1 1 1 (1) (1) (1) (1) (1)
RRN
1 1 1 1 1 1 (1) (1) (1) (1) (1)
ERR
1 (1) (1) (1) (1) (1) (1) (1)
SMM
1 (1) 1 1 (1) 1 (1) (1) 1
SPA
1 (1) 1 1 (1) 1 (1) (1) 1
SRJ
1 (1) 1 1 (1) 1 (1) (1)
FCM
1 (1) 1 1 (1) 1 (1) (1)
RJT
1 (1) 1 1 (1) 1 (1) (1)
means : exactly one field of the specified type is required means : a single optional field of the specified type is allowed
6 May 2004
Annex
27
PRIMARY FIELD COMPOSITION OF TACTICAL ATFM MESSAGES EXCHANGE (2)

Message Field
-TITLE -ADDR -ADEP -ADES -ARCID -COMMENT -CTOT -EOBD -EOBT -ERRFIELD -FILTIM -IFPLID -IOBD -IOBT -MINLINEUP -NEWCTOT -NEWPTOT -NEWRTE -ORGMSG -ORGRTE -PTOT -REASON -REGCAUSE -REGUL -REJCTOT -RESPBY -RRTEREF -RVR (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) (1) 1 (1) 1 (1) 1 1 1 1 1 1 1 1 1 1
ATC/AIRPORT APPLICATION MESSAGES

Message Field
-TITLE -ACTYPE -ADDR -ADEP -ADES -ARCID -ELDT -EOBD -EOBT -ESTDATA -FLTSTATE -FURTHRTE -IFPLID -POSITION -REG -STAR (1) (1) 1 (1) (1) 1 (1) (1) 1 1 1
SWM
1
RFI
1
REA
1
FSA
1 (1)
FUM
1 (1) 1 1 1 1 1 1 1 1
"1" "(1)"
means : exactly one field of the specified type is required means : a single optional field of the specified type is allowed
a "blank cell" means : "n<" means :

this field is not in a message n or more occurrences of this field can appear in a message
Annex 28
6 May 2004
CORRELATION BETWEEN THE CFMU REASONS FOR REGULATION AND IATA DELAY CODES CFMU REASON FOR REGULATION ATC Capacity CODE REGULATION LOCATION D C E A D ATC Ind Action ATC Routeings I R S E A E D ATC Staffing E A D ATC Equipment T E A Accident/Incident Aerodrome Capacity De-Icing Equipment non-ATC Ind Action non-ATC A G D E N D A D A D D A D A D Military Activity M E A Special Event P D A D Weather W E A Environmental Issues V D A D Other O E A 6 May 2004 Security alert Noise Thunderstorm; low visibility; X winds European football cup; Heads of Government meetings Brilliant Invader; ODAX RWY23 closed due accident Lack of parking; taxiway closure; areas closed for maintenance; demand exceeds the declared airport capacity De-Icing Runway or taxiway lighting failure Firemens strike Radar failure; RTF failure Illness; traffic delays on the highway Phasing in of new procedures Controllers strike Demand exceeds the capacity EXAMPLE CODE 89 81 83 89 82 83 81 89 82 83 89 82 83 89 83 87 87 89 87 87 98 98 89 82 83 89 83 89 73 84 89 83 89 81 83 IATA DELAY CAUSE RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to ATC ENROUTE DEMAND/CAPACITY ATFM due to RESTRICTION AT DESTINATION AIRPORT RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to ATC STAFF/EQUIPMENT ENROUTE ATFM due to RESTRICTION AT DESTINATION AIRPORT ATFM due to ATC ENROUTE DEMAND/CAPACITY RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to ATC STAFF/EQUIPMENT ENROUTE ATFM due to RESTRICTION AT DESTINATION AIRPORT RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to ATC STAFF/EQUIPMENT ENROUTE ATFM due to RESTRICTION AT DESTINATION AIRPORT RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to RESTRICTION AT DESTINATION AIRPORT AIRPORT FACILITIES AIRPORT FACILITIES RESTRICTIONS AT AIRPORT OF DEPARTURE AIRPORT FACILITIES AIRPORT FACILITIES INDUSTRIAL ACTION OUTSIDE OWN AIRLINE INDUSTRIAL ACTION OUTSIDE OWN AIRLINE RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to ATC STAFF/EQUIPMENT ENROUTE ATFM due to RESTRICTION AT DESTINATION AIRPORT RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to RESTRICTION AT DESTINATION AIRPORT RESTRICTIONS AT AIRPORT OF DEPARTURE WEATHER EN ROUTE OR ALTERNATE ATFM due to WEATHER AT DESTINATION RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to RESTRICTION AT DESTINATION AIRPORT RESTRICTIONS AT AIRPORT OF DEPARTURE ATFM due to ATC ENROUTE DEMAND/CAPACITY ATFM due to RESTRICTION AT DESTINATION AIRPORT Annex 29
6 May 2004
Annex
30
EUROCONTROL CFMU

ANNEXES
BIBLIOGRAPHY OF CFMU DOCUMENTS
Document Title
Latest Edition No.
Date
Standard Distribution
CFMU HANDBOOK BASIC PARTS

r / GENERAL & CFMU SYSTEMS r / IFPS USERS MANUAL r / ATFM USERS MANUAL r / ADDRESSES
8.0 8.0 9.0 18/02/02 18/02/02 14/04/03
amendments to all CFMU Users amendments to all CFMU Users amendments to all CFMU Users amendments to all CFMU Users
UNDER REVIEW
CFMU HANDBOOK SUPPLEMENTS

u / PROVISION OF ENVIRONMENT DATA u
RCA - Remote Client Application Reference Guide CFMU INTERNET APPLICATION (CIA) FLIGHT HANDLING USERS GUIDE 4.0 1.0 23/08/01 27/08/03
amendments ONLY to FMP, ATS amendments ONLY to FMP/AO with a CFMU Terminal connection with the RCA installed on their PCs amendments ONLY to CLIENTS with CIA SecurID Access amendments ONLY to FMD, FMP
1.0
18/06/01
u / FMP MANUAL for FMPs
3.0
27/03/00
OTHER CFMU DOCUMENTS
CFMU RELEASE NOTES CFMU 9/10 11/08/03 6.2 3.0 6.0 31/01/02 22/10/01 18/04/01
amendments to all CFMU Users amendments to all CFMU Users on request, to AOs amendments ONLY to AMC
r / CFMU NETWORK CONNECTION GUIDE
K K
RPL INPUT APPLICATION USERS GUIDE ACA USERS GUIDE FOR AMC
ADDITIONAL COPIES MAY BE REQUESTED :
H
u
from the EUROCONTROL LIBRARY Phone : ++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:cfmu.opsdoc@eurocontrol.int
6 May 2004
Annexes
31
6 May 2004
Annexes
32
EUROCONTROL CFMU

ANNEXES
More information is given overleaf concerning the completion of this form.
CFMU URB
AGENCY CONTACTS DATABASE CFMU CLIENTS UPDATE FORM mailto:cfmu.opsdoc@eurocontrol.int

EUROCONTROL
Submitted by ORGANISATION English name Usual name Acronym Type GENERAL ADDRESS Street line 1 Street line 2 Street line 3 P.O. Box Postcode Country Phone e-mail AFTN PERSON Last name (English) Last name (Original) First name Title Function Unit Office Phone e-mail_1 Mobile GROUP Name Status CFMU DOC required? CFMU WPs required? Member Yes Yes Labels Mailing e-mail Fax Yes Yes Yes Observer Participant No No No No No Document RESERVED FOR EUROCONTROL CFMU URB/RQP Fax e-mail_2 Mr Ms Other Type SITA Fax Web IATA ICAO Postcode P.O. Box City ICAO Area Code
27-05-04
6 May 2004
Annexes
33
EUROCONTROL CFMU

ANNEXES
ORGANISATION English Name Usual name Acronym Type Government Body Regulatory Authority / C.A.A. Examples: Ministry of Transport, Ministry of Defence, Embassy, Permanent Representation to E.U., ... Examples: C.A.A., Military regulatory Authority, Accident and Incident Investigation Offices/Bureaus, ... Examples: Headquarters, Director Of Operations, Head of Operations, FMP, FMP Adjacent, ARO, AIS, Tower, AMC, Meterological services, Training, ... Examples: EC, ECAC, EUROCAE, ESA, BEI, EBRD, ISO, ICAO, United Nations, NATO, EUROCONTROL, Examples: ACI, IATA, CANSO, ETF, ATC EUC, IFATCA, AECMA, AEA, IFALPA, IACA, FATSEA, ERAA, All airspace users: Passenger and Cargo airlines, Business/Corporate Aviation, General Aviation, Air work Companies, Flying Clubs, Military Aviation, Organisations which are not AOs themselves but provide flight planning or ATFM messages exchange services to other AOs. Examples: Fraport, BIAC, Aroports de Paris, Examples: ATM System manufacturers, Communication system manufacturers, Aircraft and Aircraft Engine manufacturers, Avionics, ... Examples: Microsoft, Oracle, consultancy companies Name of the organisation transcribed in English. Name of the organisation, as it is generally used to address the organisation. Mostly in the original language of the organisation, sometimes in English or another language, in which the organisation is usually addressed. Short name
Air Navigation Service Provider
International Organisation Association / Federation
Aircraft Operator
Handling Agent Airports & Airport Services Industry Consultant GENERAL ADDRESS & PERSON Phone Fax Mobile Web AFTN SITA IATA ICAO ICAO Area
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 URL of the organisations website. AFTN code of the Organisation (capital letters). SITA code of the Organisation (capital letters). IATA code of the Organisation (capital letters). 3- or 4-letter ICAO code specific to the client (capital letters). 2-letter code for the ICAO location of the organisation (capital letters). This field is required, because some countries e.g. China - are divided in several regions with a different ICAO area code.
6 May 2004
Annexes
34

Cfmu Release Notes 10v2

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Cfmu Release Notes 10v2

Загружено:

Авторское право:

Доступные форматы

EUROCONTROL CFMU

CFMU 10 - RELEASE NOTES

Doc. Reference CFMU_10RL

CFMU 10 - RELEASE NOTES

Doc. Reference CFMU_10RL

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

CFMU 10 - RELEASE NOTES

Doc. Reference CFMU_10RL

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

CFMU 10 - RELEASE NOTES

Doc. Reference CFMU_10RL

INTENTIONALLY LEFT BLANK

CFMU 10 - RELEASE NOTES

INTENTIONALLY LEFT BLANK

CFMU 10.0 - RELEASE NOTES

FLIGHT PLAN SYSTEMS IFPS/RPL/RCAT

CFMU 10.0 FLIGHT PLAN SYSTEMS

Edited & produced by the CFMU/User Relations Bureau

Flight Plan Systems

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

FLIGHT PLAN SYSTEMS IFPS/RPL/RCAT

Edited & produced by the CFMU/User Relations Bureau

Flight Plan Systems

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

FLIGHT PLAN SYSTEMS IFPS/RPL/RCAT

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

FLIGHT PLAN SYSTEMS IFPS/RPL/RCAT

Edited & produced by the CFMU/User Relations Bureau

Flight Plan Systems

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

ENHANCED TACTICAL FLOW MANAGEMENT SYSTEM (ETFMS)

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

Edited & produced by the CFMU/User Relations Bureau

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

: Adaptation to the procedures.

Edited & produced by the CFMU/User Relations Bureau

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

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

Edited & produced by the CFMU/User Relations Bureau

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

FMPs, Aircraft Operators and Towers.

Functional changes Objective : Benefiting from the new interface.

CFMU 10.0 - RELEASE NOTES

: Better information to Users.

Edited & produced by the CFMU/User Relations Bureau

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

Remote Client Application (RCA)

2003 European Organisation for the Safety of Air Navigation (EUROCONTROL)

CFMU 10.0 - RELEASE NOTES

CFMU Internet Application (CIA)

CFMU Interactive Reporting (CIR)