GEN AFTN Terminal User Manual
GEN AFTN Terminal User Manual
GEN AFTN Terminal User Manual
Revision History
Change History
Checked by
Approved by
Quality Stamp
Document Authorisation
Date Date
Document Authorisation
No. of Hardcopy /
Name Company
Copies Softcopy
Referenced Documents
Table of Contents
1 Document Overview .................................................................................................................... 6
1.1 Identification ......................................................................................................................... 6
1.2 Purpose .................................................................................................................................. 6
1.3 Scope ..................................................................................................................................... 6
1.4 Conventions ........................................................................................................................... 6
2 System Overview ......................................................................................................................... 7
2.1.1 Message Processing ....................................................................................................... 7
2.1.2 System Architecture Overview ...................................................................................... 9
3 Application Basics ..................................................................................................................... 10
3.1 On-Line Help ....................................................................................................................... 11
3.2 Limitations........................................................................................................................... 11
4 Using the Application ................................................................................................................ 12
4.1 Main Window ...................................................................................................................... 12
4.1.1 Status Bar ..................................................................................................................... 14
4.1.2 Main Window Print Options ........................................................................................ 15
4.1.3 Main Window Tree Folder Manipulation .................................................................... 15
4.1.4 Message Templates ...................................................................................................... 16
4.1.5 Main Window Message Correction ............................................................................. 16
4.1.6 Main Window Message Deletion ................................................................................. 16
4.1.7 Main Window Message Display .................................................................................. 17
4.1.8 Main Window Message Composition .......................................................................... 17
4.1.9 Main Window Message Transmission ......................................................................... 18
4.1.10 Acknowledging Received Message ............................................................................. 18
4.2 Message Editors .................................................................................................................. 18
4.2.1 Text Editor ................................................................................................................... 20
4.2.2 Form Editor .................................................................................................................. 25
4.3 Network Connectivity Window........................................................................................... 37
5 Appendix A Command Availability Matrix ........................................................................... 39
6 Appendix B Acronyms............................................................................................................ 40
List of Figures
Figure 1 - Simplified Architectural Overview ................................................................................ 9
Figure 2 - Client Primary GUI Window ....................................................................................... 10
Figure 3 - Main Application Window Appearance after cold Start .............................................. 12
Figure 4 - Main Application Window Appearance after warm Start ........................................... 13
Figure 5 - Main Application Window with Error Selected .......................................................... 14
Figure 6 - Text Editor Appearance (new Message) ...................................................................... 20
Figure 7 - Text Editor Appearance (Reply To)............................................................................. 21
Figure 8 - Form Editor (FPL) ....................................................................................................... 25
Figure 9 - Network Connectivity Window ................................................................................... 37
List of Tables
Table 1 - Status Bar Icons ............................................................................................................... 15
Table 2 - Command Availability Matrix ......................................................................................... 39
1 Document Overview
1.1 Identification
Program: <Program Name>
Revision: A0.01
1.2 Purpose
This is the user manual for the Flight ATM Systems Ltd. AFTN Terminal application.
1.3 Scope
This document provides end users with sufficient information to use the AFTN Terminal Application
in an operational environment.
This document can be used as training material if required.
This document cannot be used for system monitoring and control; this includes system
configuration, fallback operation and general functionality of a system nature typically reserved for
SMC and/or technicians maintaining the operational systems for the ANSP.
1.4 Conventions
Menu and submenu item selection are shown in fixed pitch font as follows:
File Print Summary List
This means select Print Summary List File menu item.
2 System Overview
The Flight ATM Systems Ltd. AFTN Terminal Application is designed to receive from and transmit
to the AFTN a number of different message types including:
ATS Messages in both ICAO and ADEXP formats;
METARs for meteorological data;
NOTAMs;
Other plain text messages as required;
The application is implemented using state of the art technological solutions:
Messages are stored in a COTS XML database;
The application is implemented in Java which provides scalability for future enhancements
as well as a reduction in initial production and subsequent maintenance costs due to the
high levels of support for the language.
The application paradigm is based on commercial email applications; this paradigm is immediately
recognisable from the main application window. The application provides the following functionality:
Support for processing all ICAO ATS messages defined in [1], (receive and transmit);
Support for processing ADEXP messages, message processing conforms to the rules
defined by EUROCONTROL in [4] (receive and transmit). The ADEXP message titles
supported are defined in configuration data at a programming level. Currently changes to
the ADEXP configuration data must be made through Flight ATM Systems. Ltd.
Support for reception and transmission of METAR and NOTAM messages;
Support for reception and transmission of other free text message carried by the AFTN;
Archiving of all received and transmitted messages to meet legal retention obligations;
Field 18 and 19 are also checked but many fields are not parsed due to the free text nature of
many fields. However, fields such as field 18 EET are checked for correct syntax and semantics.
The overall concept is to provide syntax and semantic checking wherever ICAO specifies very
specific rules (EET and DOF are examples where such rules are clearly defined).
ADEXP messages are parsed for the following:
That the correct primary fields are present for a given message title;
That auxiliary terms are syntactically and semantically correct;
That a primary field contains the correct auxiliary term;
All parsing rules are implemented as defined in the ADEXP standard given in [4].
Only messages with a priority indicator FF are parsed for ATS message compliance, (this
includes ADEXP and ICAO formats); other priority indicators are used for specific message types
which, as already stated are not parsed.
The messages parsed are:
ICAO messages - ACH, ACP, AFP, APL, ARR, CDN, CHG, CNL, CPL, DEP, DLA, EST, FPL,
FNM, MFS, RQP, RQS and SPL;
ADEXP ETFMS messages DES, SAM, SRM, SLC and SMM;
ADEXP ATS messages FLS, IACH, IAFP, IAPL, IARR, ICHG, ICNL, IDEP, IDLA, IFPL, IRQP,
and IRQS;
TCP/IP LAN
3 Application Basics
This section provides a brief overview of the AFTN Terminal Application functionality without going
into detail; later sections elaborate on the use of the application in greater detail.
The application provides functionality to:
Enter all ICAO ATS Message types in either ICAO or ADEXP format;
Ensure entered messages are syntactically correct;
Ensure entered messages are semantically correct as far as is possible without
environmental data checking against AIP data;
Receive all ICAO ATS Message types in either ICAO or ADEXP format;
Transmit all ICAO ATS Message types;
Message creation is supported using two mechanisms:
Plain text editors these editors are free format text editors allowing complete freedom as to
the data entered. These editors are difficult to use as a user must have extensive knowledge
of both syntax and semantics for a message being entered.
Form editors these editors provide a form where many fields are initialised by default and
context sensitive help is provided for all fields in a given form providing users with as much
support as possible during message composition. The online help is configured in off-line
configuration data and can be modified for user preferences.
Default ICAO AFTN originator and addresses are provided in both the form and text editors. This
data is obtained from configuration data; for details on how to configure such data refer to [3]
As stated previously, the paradigm used for the application is analogous to many commercial email
applications. The following drawing provides a high level description of the applications primary
client window at application start up. This window is never closed; closing this window closes the
client and disconnects the client application from the server.
Window Title Bar
Menu
Tool Bar
Error reports
Status Bar
Title bar standard windows title bar containing the name of the application with a minimise,
maximise and close button.
Menu standard window menu with a number of menu items (described later) from which
inputs can be made.
Tool bar standard window toolbar that contains a number of buttons that replicate many
options available in the menus, these buttons provide a shortcut to the menu functions.
Tree view displays a hierarchical view of the messages held in the XML database. The
user is able to create, modify and delete folders as required. There are a number of folders
that cannot be deleted, (e.g. the Inbox which is used to display all received messages).
Summary list this displays messages stored in a folder selected by a user from the tree
view. The summary list contains a number of columns that provide a synopsis of the data for
a given message.
Text Editor displays the message as received on the AFTN. This editor is normally
disabled but if the message contains an error it is enabled to allow the message to be
corrected and saved to the database. Once saved the editor is again disabled.
Error reports this area displays the errors (if any) in received messages. Selecting an error
causes the erroneous part of the message to be highlighted in the Text Editor.
Status bar provides status information about various parts of the application, including
network connection status and the number of messages in a selected folder etc.
Once a message is received it can be moved around to a folder of choice (just as files in a file
explorer). Stored messages can be copied or a Reply to initiated.
When a Reply to is initiated using a form editor the form is filled out using data from the message
being copied. Hence if a Reply to is initiated on an FPL to reply with a DEP then the DEP form
editor is opened with all fields initialised from the original message; the user need only provide the
ATD, check the message for correct syntax and transmit it.
Users have the ability to Save a message to a Draft folder and then send it immediately or defer
the transmission for a later time.
All the buttons, menu items and fields are supported with tool tips that can be used as a reminder
as to their function or data input requirements of a GUI component.
There is also a help button ( ) on the toolbar which causes the help to be displayed at the
Introduction page of the help documentation.
3.2 Limitations
The application provides numerous dialogues for creating and correcting messages along with a
number of windows that provide functions other than message editing. Many of the windows can
be opened more than once; this functionality is provided in order to be able to copy data from one
message to another or compare data between messages. In order to ensure that system resources
cannot be exhausted by opening too many windows a limit is placed on the maximum number of
windows that can be opened. The limit can be configured using configuration data.
The maximum number of windows that can be opened excludes the main application window, the
About dialogue, the Network Connectivity window and the Help window. Message boxes
reporting warnings, information and errors are also excluded. Once the limit is reached the user is
prompted to close one or more windows in order to continue opening additional windows.
Icon Meaning
EXEC server is available and this client is connected to it; the availability of the STBY is not
indicated. For further information the Network Connectivity window must be opened.
Icon Meaning
This client is not connected to an EXEC server; The connection to a standby server is not
indicated. For further information the Network Connectivity window must be opened.
This and client is connected to an EXEC server; The connection to a standby server is not
indicated. For further information the Network Connectivity window must be opened.
This and client and at least one other client are connected to the EXEC server; The connection
to a standby server is not indicated. For further information the Network Connectivity window
must be opened.
The EXEC server is connected to the AFTN; the connection status of the STBY is not indicated.
For further information the Network Connectivity window must be opened.
A number of the folders displayed in the tree view cannot be altered and/or deleted. These are
automatically created and reserved for special purposes, these include:
All the Inbox folders;
The Draft folder;
The Outbox folder;
The Sent folder;
The popup and file menu items associated with the renaming and/or folder deletion will be disabled
or not present in the folder menus when invoked on a protected folder.
Once something has been typed into the text area the Check button ( ) displayed on the main
window toolbar is enabled to validate any changes made. A message must be error free before it
can be saved.
Once the message passes input validation, the Save button ( ) is enabled on the toolbar and
the message can be saved by selecting the Save button. The original message is updated with
any changes made and secured to the database when the Save button is pressed.
The Save and Check options are also available from the popup menu displayed when the right
mouse button is clicked and the cursor is in the text editor.
Messages can also be corrected using a text editor that can be invoked from:
The popup menu displayed when right clicking a summary list entry and selecting the Edit
Message option ( );
Selecting the Text Editor button ( ) from the main window toolbar.
The text editor is discussed later in this document. The text editor functions in an identical manner
to the text editor displayed in the main application window.
Pressing the Delete menu item ( ) displayed in the popup menu invoked with a right
click on a selected message displayed in the summary list;
Pressing the Delete menu item ( ) displayed in the popup menu invoked with a right
click in the message editor area;
Selecting the main window edit menu item Edit Delete ATS Message;
The various Delete menu items are only enabled when a message is selected in the summary
list. When a message is deleted from a folder other than the Deleted folder, the message is
removed from the list in which it was selected and moved to the Deleted folder. If a message is
deleted from the Deleted folder it is permanently deleted and removed from the database;
messages deleted from the Deleted folder cannot be recovered.
Select the Display Message menu item ( ) displayed in the popup menu invoked with
a right click on a selected message displayed in the summary list;
The window displays a read only copy of the message that can be printed if required.
A message copy always copies the message field for field; (if an ARR message is copied the
ARR editor is opened, if FPL then an FPL editor is opened etc.). A message box is displayed
when an attempt is made to open a form editor on a message that has no form editor support. The
message box advises that the plain text editor should be used instead.
For an unread message - Select the Read menu item ( ) displayed in the popup menu
invoked with a right click on a selected message displayed in the summary list;
For a read message - Select the Unread menu item ( ) displayed in the popup menu
invoked with a right click on a selected message displayed in the summary list;
Form editors invoked using Reply to or Copy Message are initialised with as much data from the
message used to invoke the editor as possible, thus minimising the amount of additional data to
input before they are ready for transmission.
Form editors are available for the following message titles:
ACP, ARR, CDN, CHG, CNL, CPL, DEP, DLA, EST, FPL, RQP, RQS and SPL;
Form editors are not available for ADEXP messages and other types of non-ATS message such as
NOTAM and METAR messages.
This section describes how to use the various editors supported by the application.
When the text editor is invoked with a Reply to both the message header and body are initialised
with data obtained from the message used to invoke the message. This results in a complete copy
of the message being placed into the editor, which can then be modified before validating and
ultimate transmission onto the AFTN. When a text editor is invoked from an ATS message the
callsign of the message is displayed in the window title bar.
4.2.1.1.1 ACH
(ACH-FIELD_7-FIELD_13-FIELD_16A(FIELD_16B)
-FIELD_18_DOF-FIELD_22)
4.2.1.1.2 ACP
(ACP-FIELD_7-FIELD_13-FIELD_16)
4.2.1.1.3 AFP
(AFP-FIELD_7(-FIELD_8)
-FIELD_9-FIELD_10
-FIELD_13A(FIELD_13B)
-FIELD_14
(-FIELD_15)
-FIELD_16A(FIELD_16B) 0{FIELD_16C}2
-FIELD_18
-FIELD_19)
4.2.1.1.4 APL
(APL-FIELD_7-FIELD_8
-FIELD_9-FIELD_10
-FIELD_13
-FIELD_14
-FIELD_15
-FIELD_16A(FIELD_16B) 1{FIELD_16C}2
-FIELD_18
-FIELD_19)
4.2.1.1.5 ARR
(ARR-FIELD_7-FIELD_13-FIELD_16A-FIELD_17(-FIELD_18_DOF))
4.2.1.1.6 CDN
(CDN-FIELD_7-FIELD_13-FIELD_16)
4.2.1.1.7 CHG
(CHG-FIELD_7-FIELD_13A(FIELD_13B)-FIELD_16A(FIELD_16B)(-FIELD_18_DOF)
1{-FIELD_22})
4.2.1.1.8 CNL
(CNL-FIELD_7-FIELD_13A(FIELD_13B)-FIELD_16A(-FIELD_18_DOF))
4.2.1.1.9 CPL
(CPL-FIELD_7-FIELD_8
-FIELD_9-FIELD_10
-FIELD_13-FIELD_14
-FIELD_15
-FIELD_16 1{FIELD_16C}2
-FIELD_18)
4.2.1.1.10 DEP
(DEP-FIELD_7-FIELD_13-FIELD_16A(-FIELD_18_DOF))
4.2.1.1.11 DLA
(DLA-FIELD_7-FIELD_13-FIELD_16A(-FIELD_18_DOF))
4.2.1.1.12 EST
(EST-FIELD_7-FIELD_13-FIELD_14-FIELD_16)
4.2.1.1.13 FNM
(FNM-FIELD_7-FIELD_9-FIELD_13A
-FIELD_15
-FIELD_16A
-FIELD_18
-FIELD_19)
4.2.1.1.14 FPL
(FPL-FIELD_7-FIELD_8
-FIELD_9-FIELD_10
-FIELD_13
-FIELD_15
-FIELD_16 1{FIELD_16C}2
-FIELD_18
-FIELD_19)
4.2.1.1.15 MFS
(MFS-FIELD_7-FIELD_9
-FIELD_13A
-FIELD_14
-FIELD_16A-SIGNIFICANT_POINT_ID)
4.2.1.1.16 RQP
(RQP-FIELD_7-FIELD_13-FIELD_16A(-FIELD_18_DOF))
4.2.1.1.17 RQS
(RQS-1{Any text so long as its a minimum of 1 character})
4.2.1.1.18 SPL
(FPL-FIELD_7-FIELD_13
-FIELD_16 1{FIELD_16C}2
-FIELD_18
-FIELD_19)
To input a message using a form editor, data must be entered into the various fields. If a Reply To
was selected then most of the fields are filled out upon displaying a form editor. Once data is
entered into any field the Validate button is enabled.
Pressing the Validate button causes entered data to be parsed. If errors are detected they are
displayed in the Error Messages area. A message cannot be saved or sent while errors are
present. In order to expedite message correction, selecting an error causes the cursor to be placed
at the text in error and the field with the erroneous text to gain the focus.
When no errors are present the Save button is enabled; selecting this button causes the message
to be saved to the Draft folder.
Once saved the Send button is enabled; selecting this button sends the message to the Outbox
folder. If a connection with the AFTN switch is available the message is sent and moved to the
Sent folder.
Selecting the Close button closes the form editor.
T - TACAN
U - UHF RTF
V - VHF RTF
W - RVSM Capable
X - When prescribed by ATS
Y - 8.33KhZ channel separation supported
Z - Other equipment carried (see Note 2)
Note 1. Standard equipment is considered to be VHF RTF, ADF, VOR and ILS, unless another
combination is prescribed by the appropriate ATS authority.
Note 2. If the letter Z is used, the equipment carried is to be specified in Item 18, preceded by
COM/ and/or NAV/ as appropriate.
Note 3. If the letter J is used, specify in Item 18 the equipment carried, preceded by DAT/ followed
by one or more letters as appropriate.
Note 4. Information on navigation capability is provided to ATC for clearance and routing purposes.
Note 5. Inclusion of letter R indicates that an aircraft meets the RNP type prescribed for the route
segment(s), route(s) and/or area concerned.
N followed by 4 NUMERICS giving the True Airspeed in knots when so prescribed by the
appropriate ATS authority;
M followed by 3 NUMERICS giving the Mach Number to the nearest hundredth of unit Mach;
The AFTN details pertain to a single server; if two servers are running the status for each servers
AFTN switch connection would be shown. As only one server is up and running in the screen shot
shown above, there is only one AFTN switch connection shown.
Network Connectivity
Summary list popup
Accelerator Keys
Editor popup
Form Editor
Text Editor
Help Menu
Edit menu
File menu
Toolbar
About -
Check -
Copy CTRL C
Create copy (FPL only) CTRL Shift C
Cut CTRL X
Delete message CTRL D
Display original message (read only) CTRL Shift
M
Edit original message, (form editor) CTRL Shift F
Edit original message, (text editor) CTRL Shift E
Exit -
Folder manipulation -
Help Contents F1
Open selected form editor (creates new message) -
Paste CTRL V
Print individual message CTRL Shift P
Print summary list CTRL P
Read toggle -
Redo CTRL Y
Reply to message (select message title for -
response)
Save -
Select all CTRL A
Send - D
Undo CTRL U
Status bar icons (double click) -
6 Appendix B Acronyms
Acronym Description
A
ACH ATC Change Message (ICAO format, CFMU special)
ACP Acceptance message (OLDI)
ADEXP ATS Data Exchange Presentation
AFP ATC Flight Plan proposal Message (ICAO)
AFTN Aeronautical Fixed Telecommunications Network
AIP Aeronautical Information Publication
APL ATC Flight Plan Message (ICAO)
ARR ICAO ATS Arrival Message
ATA Actual Time of Arrival
ATD Actual Time of Departure
ATM Air Traffic Management
ATS Air Traffic Service
C
CDN Coordination Message (OLDI)
CDP Configuration Data Preparation
CFMU Central Flow Management Unit
CHG ICAO ATS Change Message
CNL ICAO ATS Cancel Message
COTS Common Off The Shelf
CPL ICAO ATS Current Flight Plan Message
CWP Controller Working Position
D
DEP ICAO ATS Departure Message
DLA ICAO ATS Delay Message
DOF ICAO Field 18 subfield, Date of Flight
DPS Data Playback System
E
EET Estimated Elapsed Time
EST ICAO ATS Estimate Message
EUROCONTROL European Organisation for the Safety of Air Navigation
F
FNM ICAO ATS Message (Oceanic)
FPL Flight Plan Message (ICAO)
G
GUI Graphical User Interface
I
ICAO International Civil Aviation Organisation
IP Internet Protocol
M
METAR Meteorological Aviation Routine Report
MFS ICAO ATS Message (Oceanic)
N
NOTAM Notice To Airmen
P
PANS Procedures for Air Navigation Services
R
RQP Request Flight Plan (ICAO)
RQS Request Supplementary Information (ICAO)
Acronym Description
S
SC Soft Copy
SMC System Monitoring and Control
SPL ICAO ATS Supplementary Flight Plan Message
T
TBD To Be Decided
TBP To Be Provided
TCP Transmission Control Protocol
U
X
XML Extensible Mark up Language