astos_hmi_1.4

8/8/2019 astos_hmi_1.4

1/83

T

ASTOS / A-SMGCS -

HMI Specification

Edition No. 1.4 Release

Edition Issue Date 16.05.2006

Author K. Krammer, Dr. T. Leitner

Reference ASTOS/HMI-R1.4

Copy No. stamp here

8/8/2019 astos_hmi_1.4

2/83

ASTOS AviBit data processingDocument Title: Document Reference:

ASTOS / A-SMGCS - HMI Specification ASTOS/HMI-R1.4

Edition: Release 1.4 ii

Document Control

Copyright Notice

2002-2005 AviBit data processing GmbH, Austria.All rights reserved.No part of this publication may be reproduced, stored in a retrieval system, ortransmitted in any form or by any means, electronic, mechanical, photocopying,recording or otherwise, without the prior written permission of AviBit.

Approval Table

AviBit Date Signature AustroControl Date Signature

Project Manager

K. Kck 16.05.2006

Quality Manager

T. Leitner 16.05.2006

Document Identification

Full Title: ASTOS / A-SMGCS, HMI Specification

Total Number of Pages: 83

8/8/2019 astos_hmi_1.4

3/83



Edition: Release 1.4 iii

Distribution

COPY No. Role Organisation

1 Customer AustroControl

Edition History

Edition No. Issue Date Author Reason

1.4 16.05.2006 K. Krammer, T.Leitner Changed for ASTOS 2.2.0

1.33 17.11.2005 K.Krammer, T.Leitner Updated for new vehicle display and

alarming display as well as for othersoftware changes

1.32 24.05.2005 T. Leitner Updated for new CTOT display

1.31 14.03.2005 T. Leitner Add error condition details andconfiguration management details

1.3 28.02.2005 T. Leitner Released with minor modifications afterinternal review

Draft 1.3 22.02.2005 T.Leitner, A.Wemmer,K.Krammer

ASTOS 2 features added

1.24 30.03.2004 K.Kck Added Info Hotspots.

1.23 03.11.2003 T. Leitner Changed description of single-line,multi-line info polygons to match thecurrent implementation (6.17.2), addeddescription of STAND dialog (6.19),added a table with possible errormessages (6.10).

1.22 08.10.2003 T. Leitner Change for new login dialog.

1.21 03.10.2003 T. Leitner Minor corrections

1.2 02.10.2003 T. Leitner Modified to match new SW release 1.1

1.1 29.08.2003 T. Leitner Final 1.1 release

Draft 1.1 28.08.2003 T. Leitner, K.Kck Modified for new HMI specs.

1.0 16.05.2003 T. Leitner, K.Kck Initial Release

0.1 15.10.2002 T. Leitner First working draft based on twoASTOS HMI meetings.

8/8/2019 astos_hmi_1.4

4/83



Edition: Release 1.4 iv

Review Table

Edition No. Review type, scope,depth & focus

Reviewers Date Conclusion

Amendment Registration

Location (Old) Add / Del / Mod CR Remark

System Release

System Release: Doc. Edition No.:

ASTOS Client Version 2.2.0 1.4

ASTOS Client Version 2.1.0 1.33

ASTOS Client Version 2.04 1.32

ASTOS Version 2.0 1.3, 1.31

ASTOS Version 1.1x 1.2

ASTOS Version 1.0 as of 29.8.2003 1.1

8/8/2019 astos_hmi_1.4

5/83



Edition: Release 1.4 v

Table of Contents

1. Introduction ...................................................................................................................... 101.1 Intended audience ........................................................................................................ 101.2 Typographical conventions ........................................................................................... 101.3 Definition of notions ...................................................................................................... 111.1 Scope of Document ...................................................................................................... 11

2.

ASTOS Main Display........................................................................................................ 12

3. General HMI Specifications............................................................................................. 143.1 Use of Mouse Buttons .................................................................................................. 143.2 Different mouse cursors................................................................................................ 143.3 General HMI characteristics.......................................................................................... 15

3.3.1 Logging in.............................................................................................................. 153.3.2 General Window/Subwindow behaviour ............................................................... 163.3.3 Range Slider .........................................................................................................173.3.4 Moving contents .................................................................................................... 183.3.5 QNH Display .........................................................................................................183.3.6 User Settings......................................................................................................... 183.3.7 Dialogs, general Behaviour ................................................................................... 193.3.8 Disappearing Toolbar............................................................................................ 193.3.9 Fonts ..................................................................................................................... 193.3.10 Manual Labelling ................................................................................................... 193.3.11 Stand identification ................................................................................................ 213.3.12 Flightplan information............................................................................................ 213.3.13 Approach Estimates .............................................................................................. 223.3.14 VDF beam display................................................................................................. 233.3.15 Info Hotspots ......................................................................................................... 23

4. Configuration management............................................................................................. 255. Label Display .................................................................................................................... 27

5.1 Labels of outbound flights ............................................................................................. 295.2 Labels of inbound flights ............................................................................................... 305.3 Labels of vehicles ......................................................................................................... 315.4 Labels in alarm conditions ............................................................................................ 325.5 Highlighted Label .......................................................................................................... 33

5.5.1 Callsign menu ....................................................................................................... 335.5.2 Stand menu........................................................................................................... 355.5.3 ACTYPE menu...................................................................................................... 365.5.4 SID menu .............................................................................................................. 365.5.5

Holding Point menu............................................................................................... 37

5.5.6 Changed label fields.............................................................................................. 38

5.6 Manually Moving Labels ............................................................................................... 395.7 Automatic Label Anti-overlap ........................................................................................ 39

8/8/2019 astos_hmi_1.4

6/83



Edition: Release 1.4 vi

6. Main display functions..................................................................................................... 406.1 Upper left corner, program status ................................................................................. 406.2 ZOOM ........................................................................................................................... 406.3 APP............................................................................................................................... 416.4 Range slider.................................................................................................................. 426.5 Approach Estimate ....................................................................................................... 436.6 SPV (Speed Vector) ..................................................................................................... 436.7 HIST.............................................................................................................................. 446.8 Time Display / Clock ..................................................................................................... 456.9 SMR/MLAT/SSR/VDF Status ....................................................................................... 456.10 Error/Info Messages ..................................................................................................... 466.11 VDF .............................................................................................................................. 486.12 RESET.......................................................................................................................... 496.13 DEFAULT ..................................................................................................................... 496.14

SETUP.......................................................................................................................... 49

6.15 LAB............................................................................................................................... 516.16 PARK............................................................................................................................ 526.17 SID ............................................................................................................................... 526.18 FULL............................................................................................................................. 526.19 ALL ............................................................................................................................... 526.20 ICE ............................................................................................................................... 526.21 MAP.............................................................................................................................. 52

6.21.1 Entering maps with Quick Draw ............................................................................ 546.21.2 Entering maps with Advanced Draw ..................................................................... 56

6.21.2.1 Choosing the polygon type and text .............................................................. 606.21.2.2 Changing font parameters ............................................................................. 616.21.2.3 Entering a link to a HTML file......................................................................... 616.21.2.4 Choosing a line style...................................................................................... 616.21.2.5 Configuring the filled area.............................................................................. 616.21.2.6 Entering a trigger polygon and text................................................................ 616.21.2.7 Entering an alarm area ..................................................................................616.21.2.8 Moving a polygon........................................................................................... 626.21.2.9 Moving single polygon points......................................................................... 62

6.21.3 Modify.................................................................................................................... 636.22 FPL............................................................................................................................... 636.23 PLAB (Predefined Labels) ............................................................................................ 646.24 SPEC (Special)............................................................................................................. 65

6.24.1 Archive Replay ...................................................................................................... 686.25 HELP ............................................................................................................................ 706.26 ADMIN .......................................................................................................................... 706.27 ALARM ......................................................................................................................... 71

7. Mouse Functions.............................................................................................................. 737.1 General ......................................................................................................................... 737.2 Mouseclicks on the label call-sign................................................................................. 737.3 Mouseclicks on other areas in the label........................................................................ 747.4 Mouseclicks on the target ............................................................................................. 747.5 Mouseclicks on the Background ................................................................................... 74

8. Alarming............................................................................................................................ 769. APPENDIX A: Acronyms and Abbreviations ................................................................. 78

8/8/2019 astos_hmi_1.4

7/83



Edition: Release 1.4 vii

10. APPENDIX B: Bibiliography ............................................................................................ 82

8/8/2019 astos_hmi_1.4

8/83



Edition: Release 1.4 viii

List of Figures

Figure 1: ASTOS Main Display. Colours as used for the operational system at Vienna Tower . 12Figure 2: Login Dialog................................................................................................................. 16Figure 3: Individual Close Buttons for all windows ..................................................................... 17Figure 4: Resizing a window....................................................................................................... 17Figure 5: Range Slider. ............................................................................................................... 17Figure 6: Moving window contents ............................................................................................. 18Figure 7: QNH Display................................................................................................................ 18Figure 8: QNH Display, failed input system ................................................................................ 18Figure 9: Track Initiation Probability Indicators: good vs. poor probability................................. 20Figure 10: Manual label entry ..................................................................................................... 20Figure 11: Attaching a manual label ........................................................................................... 21Figure 12: Stand identification .................................................................................................... 21Figure 13: Flightplan information window ................................................................................... 22Figure 14: Approach estimate window........................................................................................ 22Figure 15: VDF-Beam displayed on the ASTOS main screen.................................................... 23Figure 16: Info Hotspot for the Apron Area................................................................................. 24Figure 17: Information assigned to an Info Hotspot.................................................................... 24Figure 19: Label colour example ................................................................................................ 28Figure 20: Outbound flight label.................................................................................................. 29Figure 21: CTOT display rules.................................................................................................... 29Figure 22: Inbound flight label .................................................................................................... 30Figure 23: Label with Hint ........................................................................................................... 32Figure 24: Label with alarm and stop bar alarm ......................................................................... 32Figure 25: Label with hint and runway incursion hint .................................................................. 33Figure 26: Highlighted label ........................................................................................................ 33Figure 27: Callsign menu............................................................................................................ 34Figure 28: Stand menu ............................................................................................................... 35Figure 29: Warning dialog for "Stand already used"................................................................... 36Figure 30: ACTYPE menu .......................................................................................................... 36Figure 31: SID menu................................................................................................................... 37Figure 34: Label with a holding point .......................................................................................... 37Figure 35: Outbound label without point ..................................................................................... 38Figure 36: Holding point menu.................................................................................................... 38Figure 37: Updated field in the label ........................................................................................... 39Figure 38: Display Offline Indicator............................................................................................. 40Figure 39: ASTOS Zoom Window. ............................................................................................. 41Figure 40: Approach Window ..................................................................................................... 42Figure 41: Range Slider. ............................................................................................................. 42Figure 42: Approach Estimate Window ...................................................................................... 43Figure 43: Speed Vector Configuration. ..................................................................................... 44Figure 44: Digital target and speed vector.................................................................................. 44Figure 45: After Glow Selection. ................................................................................................. 45Figure 46: Synthetic (digital) Target and Afterglow..................................................................... 45Figure 47: Current time with QNH on top of it............................................................................. 45Figure 48: ASTOS subsystem status display. ............................................................................ 46Figure 49: ASTOS Error / Info Messages. .................................................................................. 47Figure 50: VHF Direction Finder Mode. ...................................................................................... 48Figure 51: Selection of VDF frequencies. ................................................................................... 49Figure 52: SETUP Dialog ........................................................................................................... 50

8/8/2019 astos_hmi_1.4

9/83



Edition: Release 1.4 ix

Figure 53: LAB Dialog................................................................................................................. 51Figure 54: MAP Dialog................................................................................................................ 53Figure 55: New map name entry dialog...................................................................................... 54Figure 56: Quick Draw Input mode ............................................................................................. 55Figure 57: Newly entered polygon via Quick Draw..................................................................... 56Figure 58: Entering a map polygon............................................................................................. 57Figure 59: Polygon selected after entry ...................................................................................... 57Figure 60: Map Entry Menu ........................................................................................................ 58Figure 61: Map polygon properties dialog ..................................................................................59Figure 62: Trigger-Polygon for an info map ................................................................................ 60Figure 63: Trigger-Polygon for an infomap containing the mouse cursor................................... 60Figure 64: Selected polygon ....................................................................................................... 62Figure 65: Moving polygon points............................................................................................... 62Figure 67: FPL dialog ................................................................................................................. 63Figure 68: Drag & Drop Correlation ............................................................................................ 64

Figure 69: PLAB Toplevel Menu................................................................................................. 65Figure 70: PLAB S Menu ............................................................................................................ 65Figure 72: SPEC Dialog.............................................................................................................. 66Figure 73: Change User Dialog .................................................................................................. 66Figure 74: Change User Dialog, user name selection ................................................................ 67Figure 75: Role selection menu .................................................................................................. 67Figure 76: Password Dialog........................................................................................................ 67Figure 77: ASTOS Version Information dialog............................................................................ 68Figure 78: Replay archive dialog ................................................................................................ 68Figure 79: Select archive dialog ................................................................................................. 69Figure 80: Select archive dialog: Available archives .................................................................. 69Figure 81: Display in archive replay mode.................................................................................. 70Figure 82: ADMIN Dialog............................................................................................................ 70Figure 83: Alarm check mode on toolbar .................................................................................... 71Figure 84: Alarm check mode changed elsewhere..................................................................... 71Figure 85: Alarm Dialog .............................................................................................................. 72

List of Tables

Table 1: Different mouse cursor shapes..................................................................................... 15Table 2: Content of labels of outbound flights. ...........................................................................29Table 3: CTOT countdown example ........................................................................................... 30Table 4: Content of labels of inbound flights............................................................................... 30Table 5: Filter based visibility options ......................................................................................... 31Table 6: Example vehicle group configuration............................................................................ 31Table 7: Callsign Menu Entries................................................................................................... 35Table 8: Error-Indicator, Subsystem Assignment ....................................................................... 46Table 9: Possible error messages .............................................................................................. 48Table 10: VDF Button States ...................................................................................................... 48Table 11: List of possible hints and alarms................................................................................. 76

8/8/2019 astos_hmi_1.4

10/83



Edition: Release 1.4 10

1. Introduction

This document contains a detailed description of the ASTOS Human Machine Interface (HMI).ASTOS stands for:

Airport Surface Movement Tracking, Observation and Control System

Basically ASTOS is an A-SMGCS (Advanced Surface Movement Guidance and ControlSystem) and allows the controller to monitor both aircraft taxiing on the ground as well asairborne flights close to the airport. Airborne flights are monitored by SSR inputs and taxiingaircraft are monitored by an SMR as well as by a multilateration system. In the case where themultilateration system is offline, outbound flights need to be labelled manually. Please refer tothe ASTOS functional specification document (see [2]).

This document focuses on ASTOS HMI which is typically what the end-user (the controller) willsee on the screen. All processing steps in the background are explained in the ASTOS/FSD(see [2]). In addition the configuration of the HMI is covered in the system operation manualASTOS/SOM (see [4]).

Please note that the HMI developed for the ASTOS system is the result of intensive discussionsand tests with Austrian ATC ground controllers. The HMI as described in this document fullycovers their needs and is used operationally at Vienna control tower.

1.1 Intended audience

The primary audience for this manual is the operational staff (controllers), people with in-depthknowledge of airport procedures.

1.2 Typographical conventions

Parameter names are printed in capital letters as shown below:

TTTD

Any restrictions to parameters, or definitions used in the text are printed in courier font like that:

ETA now

8/8/2019 astos_hmi_1.4

11/83




1.3 Definition of notions

This section defines all notions being used throughout the documentation. Refer to chapter 9 forabbreviations which are used in this chapter and throughout the remaining document.

Multilateration System orML System

Surveillance System using multiple sensors to detect the positionof an AC (aircraft) by measuring the transponder signal delay.

Raw Video The output of the SMR (surface movement radar) which isunprocessed and directly displayed in the main or zoom window.

Target A symbol indicating the position of the aircraft on the display.Attached to the target is usually a label (see below) whichcontains information about the target.

Ground Targets Targets which are only tracked by the ground tracker. Thesetargets can be re-assigned to another ground echo or removedfrom the display.

ML Targets Targets which are only detected by the ML system.

Label The annotation of an aircraft on the display. It usually consists ofthe following parts:

- A Text-field consisting of a number of lines showing callsignand other flightplan information.

- A line connecting the label to the target, the so calledconnector line

Connector line The line between the label and the target

Synthetic Afterglow The history point(s) showing the AC position at the last updatecycle

SMR Afterglow The SMR image(s) from the last update cycle dimmed and

combined with the current SMR image to provide a similar pictureas being shown on old CRT Radar displays.

1.1 Scope of Document

This document reflects the current state of the ASTOS HMI specification and implementation. Itdescribes ASTOS Version 2.2.0 as of May 2006.

8/8/2019 astos_hmi_1.4

12/83



Edition: Release 1.4

2. ASTOS Main Display

The ASTOS main display is shown in Figure 1 and will be explained in detail in the nextsections.

Figure 1: ASTOS Main Display. Colours as used for the operational system at Vienna Tower

Generally the ASTOS display is organised in following different layers:

- Layer 1: Airport background map: Is a coloured map in vector format. Due to this vectorformat no reduction in quality occurs when zooming into certain areas. Background Mapscan be divided into static background maps that are prepared offline and dynamicbackground maps which can be drawn by the user during runtime.

- Layer 2: SMR raw video shown in black / gray colour in Figure 1. For user definable areas(e.g. apron or parking positions) static and moving targets can be displayed in differentcolours. This avoids to clutter up the map with unimportant static echoes.

- Layer 3: Stop Bars: These always indicate the present status of the stop-bars and are usedto generate alarms if aircraft pass red stop-bars.

12

8/8/2019 astos_hmi_1.4

13/83




- Layer 4: Digital tracks and labels.

- Layer 5: Menus and dialogs.

Each layer has a priority corresponding to the layer number as described above. This meansthat a higher layer number always overlays a layer with a lower number.

Additionally there can be displayed up to 4 zoom area windows, a flightplan window containinglists of inbound and outbound flights, an approach window (APP) showing the aircrafts from theASR (or Buschberg) radar and an approach estimate window showing the time when the nextaircraft is expected to land on any runway. The time is given as a countdown in seconds assoon as the aircraft is on the final approach.

8/8/2019 astos_hmi_1.4

14/83




3. General HMI Specifications

3.1 Use of Mouse Buttons

The following actions are generally assigned to the various mouse buttons :

Left mouse button (LMB): Action buttonThis button is used to trigger any actions which can beselected from pulldown-menus.

Middle mouse button (MMB): Info buttonThis button can be used to get additional informationabout certain items. For example when clicking on thecallsign with the MMB, the full flightplan information forthis flight is shown.

Right mouse button (RMB): Window buttonThis button can be used to move windows and labelson the screen to different positions.

The abbreviations LMB, MMB and RMB are subsequently used throughout the manual for therespective mouse buttons.

3.2 Different mouse cursors

The HMI uses different shapes of the mouse cursor for different states as follows:

14

State Cursor DescriptionNormal This cursor is used in the normal operating state

Inactive After 10 seconds of inactivity, the mouse cursorautomatically changes to a big and bold + so that it can

be easily seen when looking at the display. Otherwisethe normal cursor is used.

Window resizing When moving the mouse to the bottom right of a dialogwindow, the cursor changes to this shape to that thewindow can be resized

Highlighted label When moving the mouse over an AC label, the AC labelgets highlighted and the mouse cursor changes to thisshape to signal that special actions are possible now.

8/8/2019 astos_hmi_1.4

15/83




State Cursor DescriptionMoving contents When clicking with the MMB on an empty spot of the

main window or a zoom window, the display contentscan be moved and the mouse cursor changes to thisshape.

AttachedCallsign

When manually labelling a ground target (by drag&dropfrom the flightplan list or by the manual label inputfunction) the cursor gets the desired callsign attachednext to it.

Crosshair When re-assigning an existing label to another groundtarget, the cursor changes to a crosshair.

Table 1: D

3.3 General HMI characteristics

This chapter describes the various controls and displays of the ASTOS windows.

t settings. In addition users can have certain

ed users cannly alter a small subset of the settings. So after starting the program, it is necessary to log-in

under a specific user account. For this purpose, the following dialog appears:

ifferent mouse cursor shapes

3.3.1 Logging in

ASTOS supports different users with differen

privileges which allows them to alter many settings in the program. Non-privilego

8/8/2019 astos_hmi_1.4

16/83




Figure 2: Login Dialog

Select the user from the pre-defined user list and enter the necessary password. If no keyboardis available, the password can be entered on the screen-keyboard below. Note that all lettersare converted to lowercase letters as there is no caps lock key on the screen-keyboard. ClickOK to proceed. Please contact the system administrator for the password if you dont haveone. The system administrator can also maintain the list of available users.

Note that this dialog also appears when saving the program settings under a different useraccount.

Note: In order to enter the password via the physical keyboard, the window must be activatedwith an RMB click on the title bar so that the window border gets a light blue colour as shown inthe figure above.

3.3.2 General Window/Subwindow behaviour

All Windows (Zoom, Approach, Flightplan List, Label etc.) can be moved on the screen with theRMB. They can be resized and closed be pressing the appropriate buttons as explained below.

16

8/8/2019 astos_hmi_1.4

17/83




Close Button

Figure 3: Individual Close Buttons for all windows

Close: For closing the window, press the Close Button as shown in Figure 3.

Move: In order to move the window, just click with the RMB on any location within the activatedwindow or within the windows title bar, keep the RMB pressed and move the window to thedesired position.

Resize: To resize a window just move the mouse button to the windows bottom right corner.The shape of the mouse cursor changes to an arrow as shown in the following figure

Resize Cursor

Figure 4: Resizing a window

Now press the RMB mouse button, keep it pressed and change the window size by moving the

mouse.

3.3.3 Range Slider

The range slider in the top menubar works on the currently active zoom window which is eitherthe main display, one of the zoom windows or the approach window. The currently active zoomwindow is marked by a blue window border except for the main display which is not especiallymarked.

Figure 5: Range Slider.

17

8/8/2019 astos_hmi_1.4

18/83




The numeric value above the range slider contains the range in nautical miles from the centerof the window to the window border. If the window is not quadratic, the larger range is shown.

3.3.4 Moving contents

As explained in the previous section, the range slider can be used to change the range/size ofthe displayed image. In order to shift the contents in the window, the MMB can be used asfollows: Click with the MMB on an empty spot in the main window, keep the MMB pressed andmove the mouse. The contents will shift as the mouse is moved. Keep the MMB pressed untilthe contents is on the desired position. This works in the main display, one of the zoomwindows and the approach window. The following figure shows the cursor while the windowcontents is moved:

Figure 6: Moving window contents

3.3.5 QNH Display

The QNH value is displayed on top of the current clock display. The QNH display can betoggled in the SETUP dialog.

Figure 7: QNH Display

In case of a failure of the QNH data input system, the QNH display changes its backgroundcolour to red.

Figure 8: QNH Display, failed input system

3.3.6 User Settings

Generally all users have to log in before they can use the system (see section 3.3.1).

18

8/8/2019 astos_hmi_1.4

19/83




All setting changes (status of SPV, HIST etc.) are saved on a per-user basis when the userclicks on Save settings in the SPEC menu followed by Save for current user in the nextdialog. These settings become the default user settings for this particular user then. Whenusing the change user function, the default user settings are applied. This also affects settingslike screen brightness, day/night setting, overall label display (LAB dialog) etc. Note that globaldisplay settings like label colours, stop-bar colours etc. cannot be changed on a per-user basis.These can only be changed by the administrator. This helps to avoid that all users havedifferent colour settings for important information on the screen.

If the Change user function is used and the user has changed some settings, the programasks if he wants to save his settings prior to switching to the new user.

3.3.7 Dialogs, general Behaviour

All dialogs have a Cancel and an OK button. When settings are changed in a dialog, theyare immediately visible in the display. However when the Cancel button is used, the changedsettings are discarded and the previous settings are used. The changed settings are retainedwhen the OK button is used. Dialogs are opened and closed when pressing the appropriatebutton on the left hand toolbar (see next section). Thus pressing the button twice the dialog canbe turned on and off very quickly.

Note that when the dialog window is closed by toggling the associated button on the left handtoolbar, the effect is the same as clicking on the Cancel button.

3.3.8 Disappearing Toolbar

The vertical toolbar on the left side of the display (see Figure 1) is configurable to automaticallydisappear after a certain time of inactivity of the user, similar to the toolbar available under theMS Windows operating system. When the mouse is moved close to the display border or whenit moves out of the main window on that part of the edge where the toolbar is located, thetoolbar appears again.

The toolbar on the top is always visible because it displays dynamic content such as systemstatus and error messages

3.3.9 Fonts

All fonts of labels etc. can be changed by the administrator.

3.3.10 Manual Labelling

Basically a label can be attached to any SMR echo on the ground. However the SMR echomust have certain properties to allow a reasonable tracking. First, the echo must have a certainminimum size and second there are certain spots on the airport map where reasonable SMRtracking is not possible due to clutter from other Radar targets.

The process of manual labelling consists of two steps:

8/8/2019 astos_hmi_1.4

20/83




- dragging the desired label from either the PLAB menu (see 6.23), the FPL window (seeFehler! Verweisquelle konnte nicht gefunden werden.) or the manual label input dialog(see below) and dropping the label over the desired SMR echo on the display.

- Waiting until the server has received the manual tracking request and displays the label.

Both steps are implemented to give a visual feedback to the user:

a.) When dragging the desired label over the SMR echoes, the a red circle appears. The radiusof the circle indicates the probability that the manual labelling succeeds. When there is nocircle displayed, no manual track can be initiated. The following figures show the difference:

Track initiation

probability indicator.Small circle means lowprobability.

Figure 9: Track Initiation Probability Indicators: good vs. poor probability

b.) In addition as already shown in the figure above the label to be attached (in this caseLDA145) is also moved along with the cursor.

c.) Finally after dropping the label on the desired spot, the cursor still has the label attacheduntil the a response from the server is received indicating that the labelling was successful.

In addition to drag & drop from the FPL list, manual labelling is also possible by clicking with theRMB on any empty spot on the ground map. This causes the following dialog to appear:

Figure 10: Manual label entry

This dialog is used to enter arbitrary labels which can be assigned to any target in the SMRpicture. If the CWP is equipped with a keyboard, the label can be entered via the physical

keyboard (the window needs to be activated with an RMB click on the top toolbar for that).Otherwise the screen-keyboard below the entry field can be used to enter the label with themouse. When Inbound is checked, the label will be shown in the inbound label colour, when

20

8/8/2019 astos_hmi_1.4

21/83




outbound is checked, the label will be shown in the outbound label colour and finally when N/Ais checked, the label will be shown in the vehice label colour.

When clicking OK, keep the LMB pressed. The dialog disappears and the mouse cursorchanges as shown in the following figure:

Figure 11: Attaching a manual label

Move the mouse cursor until it points to the desired SMR target. Then release the mouse buttonto trigger the labelling process. While moving the mouse, the track initiation probability indicator

is shown again as explained above.

3.3.11 Stand identification

When clicking with the MMB on a stand number, either in the flightplan list, in the approachestimate window, the approach window or in the label, the stand position is highlighted in themap. This is shown in the following figure for the case that the stand number is clicked on in thelabel. The highlighted stand position is shown on the right hand side of the following figure.

HighlightedStand

Figure 12: Stand identification

3.3.12 Flightplan information

When clicking with the MMB on a callsign, either in the flightplan list, in the approach estimatewindow, the approach window or in the label, the associated flightplan is displayed in a smallwindow right above the callsign. Note that the window is shown only as long as the MMB is keptpressed. When the MMB is released, the window automatically disappears. The FPL window isshown in the following figure.

Note that the Font and font size of the text in the flightplan window can be changed by theadministrator.

21

8/8/2019 astos_hmi_1.4

22/83




Figure 13: Flightplan information window

Note that the window only shows values which are known to the system.

3.3.13 Approach Estimates

The current approach estimate for all aircraft on the final approach is shown in a dedicatedwindow. It contains AC callsign and the estimated time to touch down shown on a relative time-scale ranging from 0 to 300 seconds. The approach estimate window is shown in the followingfigure:

Figure 14: Approach estimate window

22

8/8/2019 astos_hmi_1.4

23/83




Note that this window can be configured to:

Automatically appear/disappear when an AC is approaching

Never automatically appear

Always stay visible.

This can be configured in the SETUP dialog as explained in section 6.13.

3.3.14 VDF beam display

If enabled by the user the ASTOS main screen, the zoom windows and the approach windowcontain the VDF-beam if the user communicates with an aircraft. All aircraft along the beam areoptionally highlighted in a configurable colour.

Figure 15: VDF-Beam displayed on the ASTOS main screen.

See section 6.11 for more information.

3.3.15 Info Hotspots

The Administrator can draw so called Info Hotspots anywhere on the background map as theone shown in Figure 16 below. As soon as the cursor is moved over the Hotspot the respectivearea is highlighted and after pressing the Info Button a window appears showing the associatedinformation (Figure 17). This information can contain any HTML-coded information. As an

example the information in Figure 17 shows the pushback procedure for a certain apron area.

23

8/8/2019 astos_hmi_1.4

24/83




Figure 16: Info Hotspot for the Apron Area.

Figure 17: Information assigned to an Info Hotspot.

Refer also to section 6.21.2.3 for details how to define Info Hotspots.

24

8/8/2019 astos_hmi_1.4

25/83




4. Configuration management

Basically there are two sets of configurations for each user: The global default settings and theuser default settings. The global default settings can be modified only by the administrator,using the Save ADMIN default button in the ADMIN menu (see 6.26). The user default can bedefined for each user individually using the Save settings button in the SPEC menu (see6.24).

When the program starts up the user defaults are used. When the user makes any changes tohis display, he can always use the button RESET (see section 6.12) to switch back to hisdefault settings. If the user is not satisfied with his default settings, he can use the buttonDEFAULT (see 6.24) to switch to the global settings which can only be defined by theadministrator.

All configuration files are stored on both, the client machine and the ASTOS server. When theprogram starts, the local configuration files are compared to the versions stored on the server.Updated config files are copied from the ASTOS server to the ASTOS client when the client isstarted. Config files are stored on a per-user basis on the server. In addition there are globalconfig files which can only be modified by the administrator. When the user saves his currentsettings (for example, using the Save settings entry in the SPEC dialog), the configuration issaved on the local client computer and updated on the ASTOS server as well.

Basically the following configurations and settings are located on the ASTOS server:

global config files

per-user config files

global maps (background maps)

user defined maps

Info-Area HTML files and maps

For a user with administrator rights, the following files are copied from the local client computerto the ASTOS server:

Main display settings and global default config files

Private user config files

Private user maps

Global maps (vienna.xml global background map)

Menu Configuration files (PLAB, ACTYPE and STAND menu)

Dialog Configuration files

Info Map files

VDF Frequency List file

For a user without administrator rights, the following files are copied from the local clientcomputer to the ASTOS server:


Private user maps

8/8/2019 astos_hmi_1.4

26/83




For all users, the following files are copied at client startup (or user change) from the server tothe client:

Main display settings and global config files


Private user maps

Global default config files

Menu Configuration files (PLAB, ACTYPE and STAND menu)

Dialog Configuration files

Info Map files

VDF Frequency List file

The maintenance of the prepared map files at the server is explained in chapter 6.21.

8/8/2019 astos_hmi_1.4

27/83




5. Label Display

ASTOS displays labels for digital targets that are generated by the data fusion and trackingprocess. A label consists of 3 lines maximum and ASTOS distinguishes between labels forinbound and outbound flights and for other targets (e.g. vehicles).

A label basically consists of the following parts:

Figure 18: Anatomy of a label

Target

Connector line

Label

The label contains the text describing the target. While the label can be placed on arbitrarypositions on the screen, the target fixed at the actual position of the target. Finally the connectorline connects the label with the target.

Generally the full label is only shown if there are appropriate flightplan data available. If not, a

unique track identifier is shown.

Basically the label display depends on certain settings and conditions as follows:

If the mouse cursor moves over a label, the label is highlighted and all lines are shown (see5.3).

If the SID, PARK and the FULL button are not pressed, only the first label line is shown.

If the SID button is pressed (see 6.17) the SID is shown in the second line for outboundflights.

If the PARK button is pressed (see 6.16) the stand/parking position is shown for inboundflights in the second line.

If the FULL button is pressed, all lines in the label are shown. If an outbound flight has a CTOT, the delta-CTOT (see 5.1) is shown in any case

The CTOT is only shown in the ground display but not in the APP window

If the flight has been suspended, the CTOT field contains the string SUSP.

If any field of a label changes (e.g. the ACTYPE or the STAND is changed by another useror by a message from the flightplan delivery system) the changed field is displayed ininverse colour.

The following sections show all these different sorts of label displays in detail.

The colour of the label and the target have the following dependencies (default colours arespecified below, colours can be changed by the administrator):

Labels for inbound flights are blue

Labels for outbound flights are orange

27

8/8/2019 astos_hmi_1.4

28/83




Labels for uncorrelated targets are green

Targets which have an emergency squawk (like 7700 etc.) set are displayed in flashingred. The list of emergency squawks can be changed by the administrator.

Labels which are excluded from correlation (and will never be displayed with a callsign)are displayed in inverse colour.

Labels for vehicles are shown in blue

Manually correlated targets are shown in pink

All colours can be changed globally by the administrator.

The following figure shows an example of different label colours. For the demonstration,squawk 7777 was assigned the emergency status at the server causing it to flash in red at thedisplay. Code 7000 was set to DoNotCorrelate status causing it to be displayed with inversecolours. All uncorrelated targets are in green, inbounds in blue and outbounds in orange.

Figure 19: Label colour example

28

8/8/2019 astos_hmi_1.4

29/83




5.1 Labels of outbound flights

The label of an outbound flight is shown in Figure 20

Figure 20: Outbound flight label

The label consists of a maximum of three lines with the following content:

Left Column Right ColumnLine 1 Callsign + WTC HPLine 2 SID CTOT

Countdown

Line 3 ACTYPETable 2: Content of labels of outbound flights.

Where HP is the holding point. Note that the holding point is not displayed when the defaultholding point for the associated runway is being used (as in the example above). Likewise theCTOT is not displayed for non-slotted flights. In the example in Figure 20 the flight has holding

point 2 (A2 in this case), the SID is ABETI2A, the slot starts in 1 minute (+1) and the ACTYPEis DH8D. The WTC is M as neither a + nor a sign are attached to the callsign.

Note that the SID is only displayed when the SID button is pressed in the left toolbar. Alsonote that the SID is displayed in the abbreviated form, e.g. SIT3B rather than SITNI3B.

As already mentioned, the CTOT (only for slotted flights) is implemented as a countdown. Thismeans that controller sees the time in minutes that is left until an aircraft should take off. Thiseases the management of the departure queue. The CTOT countdown is displayed accordingto the following rules:

Zeit

CTOT

-3 -2 -1 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 +1 +2

CTOT - 5 min CTOT + 10 minCTOT + 5 min

Delta CTOTvalues displayed

in the label

CTOT color = red CTOT color = label color CTOT color =yellow

CTOT color =red

Figure 21: CTOT display rules

29

8/8/2019 astos_hmi_1.4

30/83




As soon as a label with a CTOT value is to be displayed, the delta CTOT values are alwaysshown in the label according to the rules shown in the image above. The standard outboundlabel colour is orange. In addition the delta CTOT value can change its colour depending on thevalue. If the delta CTOT is between 3 and 0, the colour is yellow and if it is less than 0 (beforethe slots starts) or after the time CTOT + 10 minutes (when the slot has expired) the colour isred. Note that these colours can be configured by the system administrator.

The next table illustrates the CTOT delta display again for a CTOT of 12:25:

Time Display12:03 -17 red

12:19 -1 red12:20 15 green

12:29 6 green

12:30 5 yellow12:35 0 yellow

12:36 +1 red

Table 3: CTOT countdown example

As illustrated in this example, the time window for take-off is from 12:20:00 to 12:35:59, which isa duration of 16 minutes. This is indeed correct and intentional.

In addition the following rules apply:

Delta CTOT values less than 99 are displayed as ---

Delta CTOT values greater than +99 are displayed as +++

When the slot is suspended by the CFMU, the CTOT delta value is replaced by the textSUSP.

The WTC is shown in the label as a small letter in the upper right corner of the callsign (notshow in Figure 20). For heavy AC, the letter + is used and for light AC the letter is used. ForAC with a medium WTC, no indication is given.

5.2 Labels of inbound flights

The label of an inbound flight is shown in Figure 22.

Figure 22: Inbound flight label

The label has three lines with the following content:

Line 1 Callsign + WTC

Line 2 STANDLine 3 ACTYPE

Table 4: Content of labels of inbound flights.

30

8/8/2019 astos_hmi_1.4

31/83




WTC (Wake turbulence category) is given in Heavy (+), Light (-) or Medium (no indication). Theexample in Figure 22 shows a aircraft with medium WTC as there is no + or letter attached tothe callsign.

Note: The STAND is only displayed if the PARK button is pressed in the left toolbar.

5.3 Labels of vehicles

Labels of vehicles can be drawn differently depending on which region of the airport they are inand to which group of vehicles they belong.The general appearance can be one of the following four classes: filtered, reduced, reducedwith history and normal.

Class Description ExampleFiltered A filtered label is not shown at allReduced For reduced labels only the

target symbol is drawn, but nohistory dots are shown.

Reduced withhistory

Drawing of the label as forreduced labels, but additionallywith history dots

Normal Unmodified appearance,including history dots.

Normal withwarning

The label is drawn normallyincluding history dots butadditionally shows a warning textin its second line

Table 5: Filter based visibility options

Note: The display of the history dots also depends on the setting of the HIST button (see

chapter 6.7)

The default configuration has the following groups and associated properties

Group Apron Safety stripincl. runway

Airport area but not on Apronor on Safety strip

Outside airport area

FBL Normal Normal Normal FilteredOTHER Filtered Normal with

warningNormal with warning Filtered

SPECIAL Reduced Normal withwarningl

Normal Filtered

Table 6: Example vehicle group configuration

The group called SPECIAL contains auxiliary vehicles like the following:

31

8/8/2019 astos_hmi_1.4

32/83




WAG

EW EINWINK

FLUSI

TEC

HAND

SAN

FLORIAN

GAC

S

WIESE

CTL

WINTER

The group OTHER contains all vehicles which are not explicitly specified in any group.

5.4 Labels in alarm conditions

When an alarm (runway incursion, stopbar crossing and the like) occurs, the associated aircraftor vehicle labels change to one of the following, depending on the type of the hint or alarm:

Hint: the labels target will be enclosed in a circle drawn in the configured hint colour.See Figure 23

Alarm: the labels target will be enclosed in a circle and the label itself will have a border,

both drawn in the configured alarm colour. See Figure 24 Stopbar Alarm: the label will be displayed like in other alarm situations as described

above and the stop bar will get one vertical line on each side, also drawn in theconfigured alarm colour. See Figure 24

Runway hint or incursion: the label will be displayed in either hint or alarm markerdepending on the alarm severity while the associated area (Runway) will be highlightedin either the configured hint or alarm colour for alarm areas. See Figure 25

Figure 23: Label with Hint

Figure 24: Label with alarm and stop bar alarm

32

8/8/2019 astos_hmi_1.4

33/83




Figure 25: Label with hint and runway incursion hint

Alarms can be acknowledged by LMB clicking the labels call sign. The label will then return toits normal visualization until it triggers another alarm.Alarms will vanish without interaction once they no longer apply, e.g. the alarm situation isresolved. Stop bar alarms last for 10 seconds if not acknowledged manually.

5.5 Highlighted Label

According to the actual needs the user can configure the HMI to show all three lines of a labelor just 1 or 2 lines of it (see 6.15, 6.16 and 6.18). If just one or two lines are visible the user canexpand a single label to all three lines simply by moving the cursor on the label. This state iscalled highlighted label. When a label is highlighted, its position remains constant and it doesnot move with the target anymore. The following figure shows a highlighted label:

Figure 26: Highlighted label

When the label is highlighted the cursor can be moved across the different fields in the label.Different fields in the label can have different action menus attached. If there is an action menuattached to a certain field, the field is surrounded by a blue border as shown in Figure 26 for thecallsign.

The different possible action menus for the different label fields are explained in detail in thefollowing sections. All menus have the following properties in common:

The first title line of the menu contains the callsign for which the menu is valid.

The second title line of the menu contains the field or item for which the menu is valid.

The menu stays visible when the LMB is released.

As soon as the mouse is moved outside the menu (plus a certain border around the menurectangle) the menu automatically disappears.

For certain menus, a default entry is available and the mouse cursor is automatically placedabove the default entry when the menu is opened.

5.5.1 Callsign menu

The callsign menu appears when clicking with the LMB on the callsign in the highlighted labelas shown in the following figure:

33

8/8/2019 astos_hmi_1.4

34/83




Figure 27: Callsign menu

The callsign menu has the following entries:

Mark1: Switches the label colour to the Mark1 colour which is purple.

Mark2: Switches the label colour to the Mark2 colour which is green.

Mark3: Displays the label in inverse colour (black or white text on coloured background).

Modify: Allows to change the callsign: This entry only exists for manually labelled targets

Hide: Hides the label and only displays the target. This can be used to hide certain(possibly unimportant) labels to avoid cluttering up the display when many AC are on to bedisplayed. When a label is hidden, it is shown automatically when the cursor is moved over

the target. Click on the target to make the label permanently visible again. Remove: This menu entry only exists for manually labelled targets. It deletes the label from

the ground track..

Reassign: This menu entry only exists for manually labelled targets. When the function isused a crosshair cursor appears which can be used to assign the selected label to anotherground target.

Corr: This menu entry allows to manually assign a callsign to an uncorrelated track.Clicking the entry will bring up a dialog to enter the callsign, similar to the dialog for manuallabelling triggered by RMB clicks on empty regions of the background map. The menu entryonly exists for uncorrelated targets. Note that correlation can also be performed via drag &drop from the FPL dialog (see Fehler! Verweisquelle konnte nicht gefunden werden.).

Decorr: This menu entry allows to break the correlation between a callsign and atransponder code. The menu entry exists only for correlated and non-manually labelledtargets.

Auto: This menu entry allows to revert from a manual Hide or Unhide switch back toautomatic (filter) based visibility. This menu entry only exists for vehicles.

Again, Modify, Remove and Reassign are only available for ground targets (targets whichare tracked by the ground tracker only). For ML targets (targets which are detected by the MLsystem), the menu entries Modify, Remove and Reassign are not available.

Note that Mark1 to Mark2 menu entries always reflect the colour which will be used for the labelwhen the respective menu entry would be triggered.

The following table summarises the conditions under which the single menu entries are visible.

34

8/8/2019 astos_hmi_1.4

35/83




Menu Entry Ground Track Correlated UncorrelatedMark1 X X X

Mark2 X X X

Mark3 X X XModify X - -

Remove X - -

Reassign X - -Corr. - - X

Decorr. - X -

Table 7: Callsign Menu Entries

5.5.2 Stand menu

The stand menu which appears when clicking with the LMB on the stand number in thehighlighted label is shown in the following figure:

Figure 28: Stand menu

The menu can be used to select the two letter stand number as follows: The first letter isselected in the toplevel menu while the second letter is selected from one of the sub-menus. So

for example (as shown in Figure 28) in order to select stand number 57, click with the LMB onentry 5 and in the sub-menu click with the LMB on entry 7.

35

8/8/2019 astos_hmi_1.4

36/83




Note that the menu is configured to show only available stand numbers. In the above example,no stand number 50 exists.

If a stand is chosen which is already assigned to another flight in the flightplan, a warningmessage appears as shown below:

Figure 29: Warning dialog for "Stand already used"

If Cancel is selected (the default selection), the stand menu as shown in Figure 28 stays openand another stand can be selected. However if CONFIRM is selected, the newly chosen standis used for this particular flight and two flights will have the same stand assignment.

5.5.3 ACTYPE menu

The ACTYPE menu which appears when clicking with the LMB on the ACTYPE in thehighlighted label is shown in the following figure:

Figure 30: ACTYPE menu

The ACTYPE menu simply shows the most common AC types. The list of AC types can bechanged by the system administrator. In order to select a different AC type, just move thecursor over the desired menu entry and click it with the LMB.

Note that when the ACTYPE is changed, the WTC might get changed accordingly. The list ofACTYPEs and associated WTCs is maintained by the administrator at the ASTOS server.

5.5.4 SID menu

This menu is only available for outbound flights when clicking with the LMB on the SID field inthe highlighted label. An example of the SID menu is shown in the following figure:

36

8/8/2019 astos_hmi_1.4

37/83




Figure 31: SID menu

Each RWY has an associated list of possible SIDs. Figure 31 shows the menu for the case whenthere is no current SID assigned to the respective flights. Note that the menu shows the abbreviatedSIDs.

5.5.5 Holding Point menu

The holding point is shown in the label at the right hand side of the callsign separated with aunderline character. If there is no holding point being used, no holding point is shown in thelabel. However in this case, in the highlighted label mode, the text _HP is attached to thecallsign which can be used to open the holding point menu.

When an outbound label already has a holding point configured, it is displayed as follows:

Holding Point2

Figure 32: Label with a holding point

37

8/8/2019 astos_hmi_1.4

38/83




Again, when there is no holding point in use the label looks as shown in Figure 20.

Outbound labels with the default holding point are shown in highlighted mode as follows:

Figure 33: Outbound label without point

When clicking on _HP the holding point menu appears as follows:

Figure 34: Holding point menu

This allows you to select a different holding point. In addition the cursor is placed on the holdingpoint 2 when the menu is opened. In order to reset to the default holding point, use the Clearmenu entry.

5.5.6 Changed label fields

As already mentioned in section 5, if an entry in the label is changed in the internal flightplan

(possibly caused by a manual input or due to updated flightplans being received) the respectiveentry in the label is displayed unconditionally (regardless of the settings of the SID, PARK and

38

8/8/2019 astos_hmi_1.4

39/83




FULL buttons). In addition the changed entry is displayed in inverse colour. The followingfigure shows an example for that:

Figure 35: Updated field in the label

In this case, the stand was changed to 31 to signal to the user that there is a new stand for

this flight. Now the user can acknowledge this change by clicking with the LMB on the changedfield. This causes the stand to be displayed normally again or it might even disappear when thesecond line is not turned on. The same can happen for all fields in the label.

In addition this function is also used to signal to the user when a desired setting is not beingaccepted by the system (regardless of the reason). When, for example, the ACTYPE is to bechanged in the above case from A306 to A320 and the system would not accept the change,the field A306 would be displayed in inverse colour. Clicking on the field would acknowledge it.

5.6 Manually Moving Labels

In order to avoid labels to overlap when they are moved with their targets the user can move

the labels by placing the cursor on the selected label, pressing and holding down the RMB andmoving the label to the desired new position.

5.7 Automatic Label Anti-overlap

ASTOS provides an automatic label anti-overlap feature. This feature assures as far aspossible that labels to not overlap when they are moved with the targets on the screen. Labelanti-overlapping can be turned on / off as described in section 6.15.

39

8/8/2019 astos_hmi_1.4

40/83




6. Main display functions

This chapter explains all functions and elements which are located on the upper horizontalfunction bar as well as on the left hand vertical tool bar as shown in Figure 1.

6.1 Upper left corner, program status

Under normal operating conditions, this corner is empty (as shown in Figure 1). There are twoprogram modes where the upper left corner is displayed differently.

1. In case the program has no connection to the server, the corner automatically changes toa big white X (cross) with red background. This signals the program is off-line and thedisplayed data do not reflect the current situation.

Figure 36: Display Offline Indicator.

2. In archive replay mode, the upper left corner contains the green text: ARCHIVE REPLAY.(See section 6.24.1 figure Figure 77)

6.2 ZOOM

This is a push-button which can be used to open a new zoom window showing an arbitrary partof the main display. ASTOS allows a maximum of 4 zoom windows to be opened and maintainsposition, size and zoom area of these windows. When clicking the ZOOM button for the firsttime, the first zoom window will appear using the position, size and zoom-area which was savedfor this window. When clicking the ZOOM button for the second time, the second zoom windowwill appear using the associated parameters (position, size and zoom-area). Again, a maximumof four zoom windows can be opened. When any parameters of a zoom window are changed(window is moved, resized or the zoom-area is changed) and the window is closed, the window

will appear at exactly the same position and size, showing the same zoom-area where it waslast closed. If there are no zoom-window definitions yet (when the software is run for the firsttime) default settings for the zoom windows are used.

40

8/8/2019 astos_hmi_1.4

41/83




Figure 37: ASTOS Zoom Window.

6.3 APP

The APP button is a toggle button which allows to toggle the display of the approach window.There can only be one approach window active at a time. If the approach window is turned on,it will appear at the same position, with the same size and zoom-area where it was closed last.When the APP button is turned off (button is out), the approach window is closed. Theapproach window is shown in Figure 38.

Note: The APP window might not be available on all installations.

41

8/8/2019 astos_hmi_1.4

42/83




Figure 38: Approach Window

6.4 Range slider

The slider right to the APP button reflects the display range of the currently active window. Thenumeric value above the range slider contains the range in nautical miles from the center of thewindow to the window border. If the window is not rectangular, the larger range is shown.

Figure 39: Range Slider.

The currently active window can be changed by clicking into the titlebar of the respectivewindow (zoom window, approach window or main display). Unless the currently active windowis the main display, it is marked by a blue window border. When switching between activewindows, the range slider will change accordingly. The range can be changed with the slider inthree ways:

1. Clicking on the slider button and dragging the slider to a new position. While dragging, thenew display range in NM is shown on top of the slider.

42

8/8/2019 astos_hmi_1.4

43/83




2. Clicking on the slider bar left or right of the slider button will change the range in big stepsand immediately update the display.

3. Clicking on the slider up/down buttons (the triangles at the left and right end of the slider)will change the range in small steps and immediately update the display.

For the ground display (and ground zoom windows) the big step size is 0.5 Nm and the smallstep size is 0.01 Nm. For the APP window the big step size is 10 Nm while the small step sizeis 1 Nm.

6.5 Approach Estimate

The approach estimate window shows the time estimate until the next aircraft will touch down

on the respective runway. This window contains a vertical time scale where the aircraftexpected to land are shown on a vertical position corresponding to their estimated touch downtime. Normally the aircraft signs are moved down constantly until they touch down. The left andright side of the vertical time scale represent the different runways. The MMB (info button) canbe used on the callsign and on the stand (below the callsign) for displaying the flight-plan andthe stand-position, respectively. In addition all label menus are available in the approachestimate window. Note however, that it is not possible to move the label in this window.

Note that only aircraft are shown which are already on the final approach (ILS aligned).

Figure 40: Approach Estimate Window

6.6 SPV (Speed Vector)

This is a toggle button which can be used to toggle the display of the speed vector. If turned on,all targets are drawn with a speed vector. In this case, the speed vector for individual targetscan be toggled by clicking with the RMB on the target. When the SPV button is turned off, thespeed vector for individual targets can be turned on by clicking with the RMB on the target.

43

8/8/2019 astos_hmi_1.4

44/83




The value (option menu) below the speed vector contains the numbers: 15, 30, 60, 90, 120 anddefines the length of the speed vector in seconds or in other words: If the value 30 is chosen,the end of the speed vector points to the position where the aircraft will be located in 30seconds if it keeps the current speed and heading.

Figure 41: Speed Vector Configuration.

The SPV function affects all zoom windows, meaning that targets located in both the maindisplay and the zoom window will get a speed vector. When a speed vector for a single target istoggled with the RMB this affects only the currently active window or in other words: If, forexample, a speed vector is turned off for via the RMB in zoom window 1 for a particular target,this does not affect the main display where the speed vector will be retained.

Speedvector

Figure 42: Digital target and speed vector.

6.7 HIST

This is a toggle button which toggles the afterglow display. This affects both afterglow ofsynthetic (digital) targets and SMR afterglow (delayed radar echoes). The history range can be

changed in the option menu below between the values 1 and 10.

44

8/8/2019 astos_hmi_1.4

45/83




Figure 43: After Glow Selection.

This function affects all zoom windows including the approach window. Of course in the lattercase, there is no SMR afterglow but only a synthetic afterglow available.

Figure 44: Synthetic (digital) Target and Afterglow

6.8 Time Display / Clock

Displays the current ASTOS server system time in UTC HH:MM:SS where the minutes (MM)are displayed in black bold letters while the hours and seconds are displayed in smaller greyletters. The ASTOS server time is synchronised with the company wide system clock via NTP.

Figure 45: Current time with QNH on top of it.

6.9 SMR/MLAT/SSR/VDF Status

These boxes signal the state of the various ASTOS subsystems

45

8/8/2019 astos_hmi_1.4

46/83




Figure 46: ASTOS subsystem status display.

The indicators represent the following subsystem operational status :

Indicator SubsystemALRM Alarm CheckerASR Airport Surveillance Radar

BUB Buschberg Radar

COR Target correlatorDFUSE Ground display, data fusionFP Flightplan Interface

MACH MACH interfaceML Multilateration System

QNH QNH interface

SB Stopbar InterfaceSDPS APP window tracker

SMRF Surface Movement RadarFusion

SMRT SMR TrackerSMRN SMR North

SMRS SMR SouthSMRW SMR West

VDF Direction finder.

Table 8: Error-Indicator, Subsystem Assignment

Under normal operating conditions (all systems ok), these boxes are not displayed and thetoolbar space is empty. As soon as one of the subsystems is not available, the respective box(containing one of the 2-4 letter abbreviations as shown above) is displayed in red colour (justas shown in Figure 46). So for instance if there is a problem with the ASR, there will be a redASR box shown. When the problem is fixed and the subsystem works again, the respective boxbecomes green. After 10 minutes the green box disappears. So the indicators are:

RED showing that the associated subsystem is currently out of order.

GREEN box showing that the associated subsystem is currently OK but has been out oforder in the last 10 minutes.

Invisible showing that the associated system is OK since more than 10 minutes.

In addition the display can be configured to beep constantly when any status box goes red. Inorder to acknowledge the error condition and turn off the beep, please click with the LMB on anerror or info message box (see next chapter).

6.10 Error/Info Messages

There are two message fields, the upper one for error messages and one the lower one for infomessages.

46

8/8/2019 astos_hmi_1.4

47/83




Figure 47: ASTOS Error / Info Messages.

The behaviour of these two fields is as follows:

1. The error message field contains messages which describe the error causing to a redstatus box (as described in section 6.9). As long as the status box is red, the error messagefield contains the associated error message. If there are multiple red status boxes, the firsterror message is displayed in the error message field but it is possible by clicking on thetext field with the info button (MMB), to get all error messages listed. Errors dealing with lost

data-sources popup an appropriate window indicating the error. As soon as any status boxbecomes green, the associated error message in the error box is cleared. If all status boxesare green again, the error message field is cleared again.

2. The info message field may contain arbitrary multi-line messages which can be enteredby the system administrator. The info message is displayed until it is manually cleared bythe system administrator.

The following error messages can appear here:

Message Effect on the displayALARM Checker off The ALARM checker is not currently running, no alarms will be

displayed.Archiver off ASTOS does not currently write the data into the archive.

ASR off ASTOS does not get data from the ASR. In this case the systemswitches to the secondary radar (Buschberg) and Buschberg datawill be displayed. In the unlikely case that both ASR and BUB areoff, no approach radar data will be displayed at all.

BUB off The Buschberg radar does not deliver data. Under normal operatingconditions, ASR data is used anyway so when BUB is off, it has noinfluence on the display. However it indicates that no backup radar isavailable for the case that ASR would go off as well. So when BUBis red but ASR is not red, a normal operation is possible.

Correlator off The display (both, ground and air) will only show uncorrelated

targets (targets with Mode-A or Mode-S codes only).Data fusion (GNDtracker) off.

The ground display will not get updated data.

Flightplan Interface off ASTOS does not get new flightplans. It might occur that uncorrelatedtargets (e.g. targets identified only by their SSR code) are visible atthe HMI.

MACH Interface off The interface to the FWAG MACH system is off and no updatedstand data will be displayed.

Multilateration systemoff

ASTOS does not get data from the multilateration (MDS) system.The ground display will only contain the SMR video with groundtargets.

QNH/RVR Interface off The QNH value will not get updatedSDPS (air tracker) off The approach display will not get updated data.

SMR Fusion off SMR data is not available. The current SMR image will be deleted at

47

8/8/2019 astos_hmi_1.4

48/83




Message Effect on the displaythe client and only multilateration targets will be displayed.

SMR Tracker off SMR data is not available. The current SMR image will be deleted atthe client and only multilateration targets will be displayed.

SMR North off SMR data from areas covered by SMR North is not available.Depending on the state of the other SMR inputs and the SMR fusionconfiguration the SMR image as well as SMR-only targets might stillbe available on some parts of that coverage area.

SMR South off SMR data from areas covered by SMR South is not available.Depending on the state of the other SMR inputs and the SMR fusionconfiguration the SMR image as well as SMR-only targets might stillbe available on some parts of that coverage area.

SMR West off SMR data from areas covered by SMR West is not available.Depending on the state of the other SMR inputs and the SMR fusion

configuration the SMR image as well as SMR-only targets might stillbe a

Documents

astos_hmi_1.4