Integrated Tower W orking Position HMI SOLUTION ......Version: V3.0 Status: Draft D2 - ITWP HMI...

ITWP

Integrated Tower Working Position

Date: 1 March, 2009

Version: V3.0

Status: Draft

D2 - ITWP HMI Solution Specifications V3 - Page i Draft


HMI SOLUTION SPECIFICATIONS

Reference: HMI solution Status: Draft Edition No: V3.0 Date: 1 March 09

Manager(s) S. Dubuisson / R. Lane

Visa :

Author EUROCONTROL

Endorsement:

Director(s) Peter Eriksen

Visa :

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft

D2 - ITWP HMI Solution Specifications Page 1 Draft

Table of Contents

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

1.1 DOCUMENT PURPOSE AND SCOPE........................................................................................................ 1 1.2 METHODOLOGY................................................................................................................................... 1 1.3 STRUCTURE OF THE DOCUMENT........................................................................................................... 2 1.4 ACRONYMS.......................................................................................................................................... 3 1.5 REFERENCE DOCUMENTS..................................................................................................................... 3

2 PRINCIPLES............................................................................................................................................. 4

2.1 TWR CONFIGURATION........................................................................................................................ 4 2.2 TWR FUNCTIONALITY AND PROCEDURES........................................................................................... 4 2.3 TRAFFIC PLANNING STATES................................................................................................................. 5

2.3.1 Main states and sub-states.............................................................................................................. 5 2.3.2 Transitions between main states..................................................................................................... 5

2.3.2.1 ‘Not concerned’ to ‘Pending’ transition ................................................................................................ 5 2.3.2.2 ‘Not concerned’ to ‘Assumed’ Transition (vehicle and towed aircraft only) ........................................ 6 2.3.2.3 ‘Assumed’ to ‘Not concerned’ Transition ............................................................................................. 6 2.3.2.4 ‘Pending’ to ‘Assumed’ Transition ....................................................................................................... 7

2.3.3 Transition between sub-states ........................................................................................................ 7 2.3.3.1 ‘No value’ to ‘Pending-in’ transition..................................................................................................... 7 2.3.3.2 ‘No value’ to ‘Assumed Out’ transition ................................................................................................ 8

2.4 COLOUR CODING................................................................................................................................. 8 2.4.1 Default colours ............................................................................................................................... 8 2.4.2 ‘Not concerned’ planning state colours ......................................................................................... 9 2.4.3 ‘Pending’ planning state colours ................................................................................................... 9 2.4.4 ‘Assumed’ planning state colours .................................................................................................10

2.5 STRIP BAYS.........................................................................................................................................11 2.5.1 RWY controller bays......................................................................................................................11

2.5.1.1 Taxi Out Bay....................................................................................................................................... 11 2.5.1.2 RWY Bay............................................................................................................................................ 12 2.5.1.3 Transfer Bay........................................................................................................................................ 13

2.5.2 GND Controller Bays....................................................................................................................13 2.5.2.1 Outbound Bay ..................................................................................................................................... 13 2.5.2.2 Runway Bay ........................................................................................................................................ 14

2.5.3 CLD Controller Bay ......................................................................................................................15 2.5.4 Typical flight lifecycle ...................................................................................................................16

3 HMI AND TRANSVERSAL FH REQUIREMENTS ................ ...........................................................30

4 DESCRIPTION OF HMI OBJECTS .....................................................................................................32

4.1 DESCRIPTION OF HMI OBJECTS..........................................................................................................32 4.1.1 Worktop .........................................................................................................................................32 4.1.2 Window..........................................................................................................................................33 4.1.3 Cursor............................................................................................................................................36 4.1.4 Switches Buttons............................................................................................................................38 4.1.5 Menu..............................................................................................................................................40 4.1.6 System Message Window...............................................................................................................42 4.1.7 Logon Window...............................................................................................................................43 4.1.8 Local Parameters ..........................................................................................................................43 4.1.9 Preferences Setting Window..........................................................................................................44

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.10 General Toolbox Window .........................................................................................................45 4.1.11 Composite Situation Display (CSD) Toolbox Window..............................................................46 4.1.12 Zoom Back Button.....................................................................................................................47 4.1.13 Zoom Tool .................................................................................................................................48 4.1.14 Map Selection Tool ...................................................................................................................49 4.1.15 Speed Vector Track History Tool ..............................................................................................50 4.1.16 Sub-Views Tool .........................................................................................................................51 4.1.17 Airport setup Tool .....................................................................................................................52 4.1.18 EFS Configuration Tool............................................................................................................53 4.1.19 EFS Tool ...................................................................................................................................54 4.1.20 Pending Departures Section (GND role) ..................................................................................55 4.1.21 Start-Up Section (GND role) ....................................................................................................56 4.1.22 Pushback Section (GND role) ...................................................................................................57 4.1.23 Taxi-out Section (GND role) .....................................................................................................58 4.1.24 Pending Arrivals Section (GND role) .......................................................................................59 4.1.25 Taxi-in Section (GND role).......................................................................................................60 4.1.26 Transfer to RWY Section (GND role)........................................................................................61 4.1.27 Pending Departures Section (RWY role) ..................................................................................62 4.1.28 Holding Point Section (RWY role) ............................................................................................63 4.1.29 Pending Arrivals Section (RWY role)........................................................................................64 4.1.30 Final Section (RWY role) ..........................................................................................................65 4.1.31 RWY Section (RWY role)...........................................................................................................66 4.1.32 RWY Taxi-In Section (RWY role) ..............................................................................................67 4.1.33 RWY Airborne Section (RWY role) ...........................................................................................68 4.1.34 Pending Departure Section (CLD role) ....................................................................................69 4.1.35 CLD Active Section (CLD role) ................................................................................................70 4.1.36 CLD Start Up Section (CLD role).............................................................................................71 4.1.37 Clock Window ...........................................................................................................................72 4.1.38 Weather Information Window...................................................................................................72 4.1.39 NAVAIDS Information Window ................................................................................................74 4.1.40 Composite Situation Display (CSD) Window............................................................................75 4.1.41 Radar Track ..............................................................................................................................76 4.1.42 Radar Label ..............................................................................................................................78 4.1.43 Vehicle Radar Label..................................................................................................................83 4.1.44 Towed Aircraft Radar Label .....................................................................................................86 4.1.45 Label Configuration Tool..........................................................................................................89 4.1.46 Label Overlap Management Tool .............................................................................................91 4.1.47 Range and bearing tracker link.................................................................................................92 4.1.48 Extended radar label.................................................................................................................93 4.1.49 Extended radar label window ...................................................................................................94 4.1.50 RWY conflict alert track............................................................................................................95 4.1.51 RWY conflict alert label ............................................................................................................96 4.1.52 Alert in the radar label..............................................................................................................97 4.1.53 Alert in the e-strip .....................................................................................................................99 4.1.54 Alert Window ..........................................................................................................................100 4.1.55 Alert displayed on the radar track ..........................................................................................101 4.1.56 Runway Conflict Alert Message..............................................................................................102 4.1.57 Runway Incursion Alert Message............................................................................................103 4.1.58 Conflicting ATC Clearances Alert Messages..........................................................................104 4.1.59 Non Conformance To ATC Clearance Alert Messages...........................................................105 4.1.60 ATCO Input Error w.r.t Airport Layout Alert Messages........................................................106 4.1.61 Runway Alert...........................................................................................................................107 4.1.62 CROSS / ENTER Runway warning .........................................................................................107 4.1.63 Traffic Filter Tool ...................................................................................................................108

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.64 Range and Bearing Tool .........................................................................................................109 4.1.65 Callsign Menu.........................................................................................................................110 4.1.66 Runway Menu..........................................................................................................................119 4.1.67 Parking / Stand Menu .............................................................................................................120 4.1.68 Parking / Stand Symbol...........................................................................................................121 4.1.69 Route Accept Menu .................................................................................................................122 4.1.70 Stop At Menu...........................................................................................................................122 4.1.71 Holding Point Menu for a departure flight .............................................................................123 4.1.72 Holding Point Menu for an arrival flight................................................................................123 4.1.73 Stop bar Menu.........................................................................................................................124 4.1.74 Runway Status Menu...............................................................................................................125 4.1.75 Taxiway Status Menu ..............................................................................................................126 4.1.76 SID Menu ................................................................................................................................127 4.1.77 Operator Role Menu ...............................................................................................................128 4.1.78 Transfer Menu (callsign manu – only transfer available).......................................................129 4.1.79 Vehicle e-strip .........................................................................................................................130 4.1.80 Towed aircraft e-strip .............................................................................................................132 4.1.81 Arrival e-strip..........................................................................................................................134 4.1.82 Departure e-strip ....................................................................................................................137 4.1.83 CLD e-strip .............................................................................................................................140

5 DESCRIPTION OF PROCEDURES ...................................................................................................147

5.1 WIMP GRAPHICAL USER INTERFACE MANAGEMENT........................................................147 5.1.1 Windows Management ................................................................................................................147

5.1.1.1 Open window .................................................................................................................................... 147 5.1.1.2 Close window.................................................................................................................................... 149 5.1.1.3 Move window.................................................................................................................................... 150 5.1.1.4 Come on top window ........................................................................................................................ 151 5.1.1.5 Iconify window ................................................................................................................................. 152 5.1.1.6 De-iconify window........................................................................................................................... 152 5.1.1.7 Re-size window................................................................................................................................. 153 5.1.1.8 Re-scale window ............................................................................................................................... 154 5.1.1.9 Page scroll window .......................................................................................................................... 155 5.1.1.10 Slider scroll window.......................................................................................................................... 156 5.1.1.11 Step scroll window ............................................................................................................................ 157

5.1.2 Menus Management ....................................................................................................................158 5.1.2.1 Open menu ........................................................................................................................................ 158 5.1.2.2 Scroll menu ....................................................................................................................................... 159 5.1.2.3 Select menu item ............................................................................................................................... 159 5.1.2.4 Close menu........................................................................................................................................ 160 5.1.2.5 Cancel menu...................................................................................................................................... 160

5.2 ACCESS CWP.................................................................................................................................161 5.2.1 Access / exit the CWP functions ..................................................................................................161

5.2.1.1 Log on CWP...................................................................................................................................... 161 5.2.1.2 Log out CWP..................................................................................................................................... 162

5.3 MANAGE THE DISPLAY LAYOUT ............................................................................................163 5.3.1 Set-Up the Display and Access Screen Settings ..........................................................................163

5.3.1.1 Save configuration set-up.................................................................................................................. 163 5.3.1.2 Access configuration set-up .............................................................................................................. 164 5.3.1.3 Set-up input devices .......................................................................................................................... 165

5.3.2 Set-Up Screen Parameters ..........................................................................................................165 5.3.2.1 Select day/night/sun settings ............................................................................................................. 165 5.3.2.2 Fine tune brightness settings ............................................................................................................. 166 5.3.2.3 Fine tune contrast settings ................................................................................................................. 166

5.3.3 Manage Toolbar Functions .........................................................................................................167 5.3.3.1 Access Tool ....................................................................................................................................... 167

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.3.3.2 Isolate Tool........................................................................................................................................ 168 5.3.3.3 Replace Tool ..................................................................................................................................... 169

5.4 ACCESS AIR, SURFACE AND TIME INFORMATION ..............................................................170 5.4.1 Zoom, offset and modify the geographical orientation of the display view .................................170

5.4.1.1 Perform Zoom ................................................................................................................................... 170 5.4.1.2 Store zoom ........................................................................................................................................ 171 5.4.1.3 Retrieve zoom ................................................................................................................................... 172 5.4.1.4 Zoom back......................................................................................................................................... 172 5.4.1.5 Delete zoom ...................................................................................................................................... 173 5.4.1.6 Offset centre ...................................................................................................................................... 173 5.4.1.7 Zoom in part...................................................................................................................................... 175 5.4.1.8 Modify geographical orientation of situation display........................................................................ 176

5.4.2 Display Airport Information........................................................................................................176 5.4.2.1 Display composite video map ........................................................................................................... 176 5.4.2.2 Display / remove display parking names........................................................................................... 177 5.4.2.3 Display parking names (Quick Look)................................................................................................ 177 5.4.2.4 Set Up Runway / Taxiway Status (open / close)................................................................................ 178

5.4.3 Display and track range and bearing between two points ..........................................................179 5.4.3.1 Enable Range and Bearing function .................................................................................................. 179 5.4.3.2 Cancel Range and Bearing function .................................................................................................. 180 5.4.3.3 Create Range and Bearing Track....................................................................................................... 181 5.4.3.4 Cancel Range and Bearing Track ...................................................................................................... 182 5.4.3.5 Express Time to Go to airspace point................................................................................................ 182

5.4.4 Access time information ..............................................................................................................183 5.4.4.1 Display Time..................................................................................................................................... 183

5.5 MANAGE THE DISPLAY FEATURES OF TRAFFIC REPRESENTATION ..............................184 5.5.1 Manage the Radar Labels ...........................................................................................................184

5.5.1.1 Configure Radar Labels Content ....................................................................................................... 184 5.5.2 Manage the Electronic Flight Strips (EFS, e-strip).....................................................................185

5.5.2.1 Configure the EFS content ................................................................................................................ 185 5.5.2.2 Move an EFS..................................................................................................................................... 186

5.5.3 Manage air tracks and labels ......................................................................................................186 5.5.3.1 Display speed vectors........................................................................................................................ 186 5.5.3.2 Set speed vectors value...................................................................................................................... 187 5.5.3.3 Set track history value ...................................................................................................................... 187

5.5.4 Manage label position .................................................................................................................188 5.5.4.1 Deconflict labels automatically ......................................................................................................... 188 5.5.4.2 Deconflict labels manually ................................................................................................................ 189 5.5.4.3 Set label leader direction ................................................................................................................... 190 5.5.4.4 Set leader length ................................................................................................................................ 190 5.5.4.5 Set fixed reference............................................................................................................................. 191 5.5.4.6 Set track as a reference...................................................................................................................... 191 5.5.4.7 Move radar babel............................................................................................................................... 192 5.5.4.8 Resume label position ....................................................................................................................... 193

5.5.5 Draw attention to a particular aircraft or vehicle.......................................................................194 5.5.5.1 Input intra-CWP traffic marking ....................................................................................................... 194 5.5.5.2 Share marking with next CWP .......................................................................................................... 195 5.5.5.3 Share marking with all CWPs ........................................................................................................... 195 5.5.5.4 Unmark traffic................................................................................................................................... 196

5.6 ACCESS DATA CONCERNING THE TRAFFIC SITUATION....................................................197 5.6.1 Access aircraft / vehicle representation ......................................................................................197

5.6.1.1 Display traffic representation ............................................................................................................ 197 5.6.1.2 Remove traffic representation ........................................................................................................... 198 5.6.1.3 Select traffic ...................................................................................................................................... 199 5.6.1.4 Deselect Traffic ................................................................................................................................. 200 5.6.1.5 Display extended label ...................................................................................................................... 201 5.6.1.6 Display extended label (Quick Look)............................................................................................... 202 5.6.1.7 Display additional CSD sub-view ..................................................................................................... 203

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.1.8 Display EFS section .......................................................................................................................... 204 5.6.1.9 Hide EFS Bay.................................................................................................................................... 205

5.6.2 Update Traffic Situation Data .....................................................................................................206 5.6.2.1 Input “En Route Clearance” .............................................................................................................. 206 5.6.2.2 Input “En Route Clearance via data link”.......................................................................................... 207 5.6.2.3 Input “Start Up” ................................................................................................................................ 208 5.6.2.4 Input “Pushback”............................................................................................................................... 209 5.6.2.5 Input “Taxi” ...................................................................................................................................... 210 5.6.2.6 Input “Line up”.................................................................................................................................. 211 5.6.2.7 Input “Conditional line up” ............................................................................................................... 212 5.6.2.8 Input “Hold”...................................................................................................................................... 213 5.6.2.9 Input “Hold at” .................................................................................................................................. 214 5.6.2.10 Input “Abort take off” ....................................................................................................................... 215 5.6.2.11 Input “Cleared to land”...................................................................................................................... 215 5.6.2.12 Input “Cleared for take off”............................................................................................................... 216 5.6.2.13 Input “Airborne” ............................................................................................................................... 216 5.6.2.14 Input “Go around” ............................................................................................................................. 217 5.6.2.15 Input “Vacate”................................................................................................................................... 218 5.6.2.16 Input “Visual Circuit” ....................................................................................................................... 219 5.6.2.17 Cancel the last given order ................................................................................................................ 220 5.6.2.18 Display Estimated Landing Time (ELDT) ........................................................................................ 220 5.6.2.19 Display Time To Touchdown (TTT)................................................................................................. 221 5.6.2.20 Input Actual Landing Time (ALDT) ................................................................................................. 222 5.6.2.21 Display Estimated In Block Time (EIBT) ......................................................................................... 223 5.6.2.22 Display Actual In-Block-Time (AIBT) ............................................................................................. 223 5.6.2.23 Display Estimated Off Block Time (EOBT) ..................................................................................... 224 5.6.2.24 Display Actual Off-Block Time (AOBT).......................................................................................... 224 5.6.2.25 Display Target Take Off Time (TTOT)............................................................................................. 225 5.6.2.26 Input Actual Take-Off Time (ATOT)................................................................................................ 226 5.6.2.27 Change RWY for landing (single flight) ........................................................................................... 226 5.6.2.28 Change RWY for take-off (single flight)........................................................................................... 227 5.6.2.29 Input holding point (single flight) ..................................................................................................... 227 5.6.2.30 Change holding point (single flight).................................................................................................. 228 5.6.2.31 Change parking stand ........................................................................................................................ 228 5.6.2.32 Input SID........................................................................................................................................... 229 5.6.2.33 Change SID ....................................................................................................................................... 229 5.6.2.34 Cancel SID ........................................................................................................................................ 230 5.6.2.35 Mark/Unmark SID............................................................................................................................. 230

5.6.3 Transfer and Coordination..........................................................................................................231 5.6.3.1 Assume Traffic.................................................................................................................................. 231 5.6.3.2 Transfer Traffic ................................................................................................................................. 232 5.6.3.3 Transfer Vehicle / Towed aircraft ..................................................................................................... 233 5.6.3.4 Select Operator Role for Transfer ..................................................................................................... 234

5.6.4 Filter Traffic ................................................................................................................................234 5.6.4.1 Filter traffic (height).......................................................................................................................... 234

5.7 MANAGEMENT OF VEHICLES...................................................................................................235 5.7.1 Display vehicles on the masked apron area ................................................................................235 5.7.2 Hide vehicles on the masked apron area.....................................................................................235 5.7.3 Input “Tow” ................................................................................................................................236 5.7.4 Input “Release”...........................................................................................................................237

5.8 MANAGEMENT OF ALERTS AND WARNINGS .......................................................................238 5.8.1 General alert management ..........................................................................................................238

5.8.1.1 Acknowledgement of an alert............................................................................................................ 238 5.8.1.2 Red circle for an alarm ...................................................................................................................... 239

5.8.2 Management of alerts for conflicting ATC clearances (CLRS) ...................................................239 5.8.2.1 Display conflicting ATC clearance input .......................................................................................... 239 5.8.2.2 End display of conflicting ATC clearance input................................................................................ 240

5.8.3 Management of alerts for infringements of restricted / closed areas (AREA).............................241

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.3.1 Display runway conflict alert ............................................................................................................ 241 5.8.3.2 End runway conflict alert .................................................................................................................. 243 5.8.3.3 Display ATCO input error with restect to airport layout ................................................................... 244 5.8.3.4 End display ATCO input error w.r.t airport layout............................................................................ 245

5.8.4 Management of alerts for non conformance to ATC instructions................................................246 5.8.4.1 Display non conformance to ATC instructions (INFORMATION) .................................................. 246 5.8.4.2 End display non conformance to ATC instructions (INFORMATION)............................................ 247 5.8.4.3 Display non conformance to ATC instructions (ALARM)................................................................ 248 5.8.4.4 End display non conformance to ATC instructions (ALARM) ......................................................... 249 5.8.4.5 Display excessive aircraft taxi speed................................................................................................. 249 5.8.4.6 End alert for excessive aircraft taxi speed ......................................................................................... 250

5.8.5 Management of protecting devices and runway lighting.............................................................250 5.8.5.1 Display stop bar status....................................................................................................................... 250 5.8.5.2 Manually activate / de-activate stop bar ............................................................................................ 251

5.8.6 Management of navaids serviceability ........................................................................................251 5.8.6.1 Display navaids serviceability........................................................................................................... 251

5.8.7 Management of mobiles on the runway.......................................................................................252 5.8.7.1 Input “Enter” ..................................................................................................................................... 252 5.8.7.2 Input “Cross”..................................................................................................................................... 253 5.8.7.3 Display of Runway cross/enter.......................................................................................................... 254 5.8.7.4 End Display of Runway cross/enter .................................................................................................. 254

5.8.8 Management of warnings ............................................................................................................255 5.8.8.1 Display parking/stand occupied......................................................................................................... 255

5.9 MANAGEMENT OF MOBILE ROUTING.................................................................................................256 5.9.1 Display Planned Route (aircraft and vehicle) .............................................................................256 5.9.2 Input a new route for a mobile ....................................................................................................257 5.9.3 Input “Stop At” ...........................................................................................................................257

5.10 OTHER FUNCTIONS...........................................................................................................................258 5.10.1 Display timer...........................................................................................................................258 5.10.2 Count down time .....................................................................................................................258

6 ANNEX: ITWP REQUIREMENTS .....................................................................................................259

6.1 BASIC HMI ELEMENTS AND DISPLAY MANAGEMENT........................................................................259 6.1.1 WIMP graphical user management .............................................................................................259

6.2 WIMP GRAPHICAL USER MANAGEMENT...........................................................................................260 6.2.1 Access the CWP functions ...........................................................................................................260

6.2.1.1 Access / exit the CWP....................................................................................................................... 260 6.2.2 Manage the display layout...........................................................................................................260

6.2.2.1 Set up the display and access screen settings .................................................................................... 260 6.2.2.2 Manage toolbar functions .................................................................................................................. 261

6.2.3 Access air, surface and time information ....................................................................................261 6.2.3.1 Zoom, offset and modification of geographical orientation............................................................... 261 6.2.3.2 Display surface information .............................................................................................................. 262 6.2.3.3 Display airspace information............................................................................................................. 263 6.2.3.4 Display time information................................................................................................................... 263 6.2.3.5 Display additional view..................................................................................................................... 263 6.2.3.6 Display and track range and bearing ................................................................................................. 264

6.2.4 Manage the display features of traffic representation.................................................................264 6.2.4.1 Manage the radar label position......................................................................................................... 264 6.2.4.2 Manage tracks and labels................................................................................................................... 266

6.2.4.2.1 Display speed vectors ................................................................................................................... 266 6.2.4.2.2 Display aircraft and vehicle representation................................................................................... 266 6.2.4.2.3 Configure the radar labels............................................................................................................. 266 6.2.4.2.4 Filter out groups of tracks............................................................................................................. 267 6.2.4.2.5 Draw attention to a specific aircraft or vehicle ............................................................................. 267

6.3 ACCESS DATA CONCERNING THE CURRENT TRAFFIC SITUATION.......................................................268 6.3.1 Select an aircraft or vehicle ........................................................................................................268

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


6.3.2 Display traffic representation......................................................................................................268 6.3.2.1 Access all traffic entering or planning to enter a controller’s area of responsability......................... 269

6.4 ACCESS WEATHER / ADVISORY INFORMATION ..................................................................................272 6.5 SET UP THE AIRPORT LAYOUT...........................................................................................................272 6.6 UPDATE SYSTEM DATA CONCERNING THE CURRENT TRAFFIC SITUATION .........................................272

6.6.1 Update system data according to controller clearances .............................................................272 6.6.2 Update system data according to traffic data modifications .......................................................274

6.7 FLIGHT PLAN EDITION.......................................................................................................................274 6.7.1 Create a flight plan......................................................................................................................274 6.7.2 Modify a flight plan .....................................................................................................................275

6.8 SYSTEM SUPPORTED DATA EXCHANGE AND COORDINATION.............................................................275 6.8.1 Traffic data distribution between positions .................................................................................275 6.8.2 Transfer of control responsibility ................................................................................................275

6.9 VEHICLE MANAGEMENT ...................................................................................................................276 6.9.1 Display / hide vehicles.................................................................................................................276 6.9.2 Instruction to vehicle ...................................................................................................................276

6.10 MONITORING AND CONTROL FUNCTIONS.........................................................................................276 6.10.1 Surface hazardous situations detection and alerting..............................................................276

6.10.1.1 Introduction to hazardous situations in the surface management ...................................................... 276 6.10.1.2 Detection of non conformance to ATC instructions / procedures (PROC)........................................ 277 6.10.1.3 Detection of conflicting ATC clearances (CLRS) ............................................................................. 279 6.10.1.4 Detection of infringement of restricted / closed areas (AREA) ......................................................... 281

6.10.1.4.1 Runway conflicts detection and alerting ..................................................................................... 281 6.10.1.4.2 Detection of ATC controllers input errors with respect to airport layout.................................... 282

6.10.2 Protecting devices and runway lighting..................................................................................283 6.10.3 NAVAIDS servicability............................................................................................................283 6.10.4 Management of mobiles on the runway (cross & enter).........................................................284 6.10.5 Management of traffic queues – sequencing traffic ................................................................284

6.10.5.1 Departure management...................................................................................................................... 284 6.10.5.2 Arrival management .......................................................................................................................... 284

6.11 MOBILE ROUTING MANAGEMENT ....................................................................................................284 6.11.1 Display planned route.............................................................................................................284 6.11.2 Validate assigned route and display cleared route .................................................................285 6.11.3 Input ‘Stop At’ instruction.......................................................................................................285 6.11.4 Input route modification..........................................................................................................285

6.12 AIR-GROUND DATA COMMUNICATION : DATA LINK FUNCTIONS......................................................286

7 ANNEX: TRANSVERSAL HF REQUIREMENTS............................................................................287

7.1 PROCESSES OF INTERACTION............................................................................................................287 7.1.1 Behavioural consistency..............................................................................................................287 7.1.2 Level of user awareness...............................................................................................................287 7.1.3 Explicit Design to support resource management and monitoring .............................................288 7.1.4 Flexibility in the use of the interface: multiple paths and expert use .........................................288 7.1.5 Minimum cognitive effort ............................................................................................................288 7.1.6 Feedback on action .....................................................................................................................288

7.2 INPUTS..............................................................................................................................................288 7.2.1 Input Basics .................................................................................................................................289 7.2.2 The accessibility of selectable objects .........................................................................................289 7.2.3 Response times ............................................................................................................................290 7.2.4 Temporary versus Permanent Information Display ....................................................................290 7.2.5 Policy on default selections .........................................................................................................291 7.2.6 Input Devices and Input Events...................................................................................................292

7.2.6.1 Mouse................................................................................................................................................ 292 7.2.6.2 Keyboard........................................................................................................................................... 292 7.2.6.3 Touch screen ..................................................................................................................................... 293

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.2.6.4 Menus and Pop-Up menus................................................................................................................. 293 7.2.6.4.1 General use................................................................................................................................... 293 7.2.6.4.2 Menu options ................................................................................................................................ 294 7.2.6.4.3 Options organisation..................................................................................................................... 294 7.2.6.4.4 Menu bars..................................................................................................................................... 295 7.2.6.4.5 Scrolling menus ............................................................................................................................ 295 7.2.6.4.6 Pop-up menus ............................................................................................................................... 296

7.2.7 Input Error Management Policy..................................................................................................297 7.3 VISUAL PRESENTATION RULES AND CONVENTIONS...........................................................................297

7.3.1 Display hardware ........................................................................................................................297 7.3.1.1 General .............................................................................................................................................. 297 7.3.1.2 Glare.................................................................................................................................................. 297

7.3.2 Principles for the presentation of data ........................................................................................298 7.3.2.1 General Principles ............................................................................................................................. 298 7.3.2.2 Organisation of information .............................................................................................................. 298 7.3.2.3 Text properties................................................................................................................................... 299

7.3.2.3.1 Fonts and sizes.............................................................................................................................. 299 7.3.2.3.2 Vocabulary and abbreviations ...................................................................................................... 299 7.3.2.3.3 Style and layout ............................................................................................................................ 300

7.3.2.4 Viewing distances ............................................................................................................................. 300 7.3.2.5 Radar Labels...................................................................................................................................... 300 7.3.2.6 Check boxes (i.e. on EFS) ................................................................................................................. 301 7.3.2.7 Cursors .............................................................................................................................................. 302 7.3.2.8 Maps and Tactical Displays............................................................................................................... 302

7.3.2.8.1 Characteristics .............................................................................................................................. 302 7.3.2.8.2 Graphic display manipulation....................................................................................................... 304 7.3.2.8.3 Dynamic information update ........................................................................................................ 304

7.3.3 Alarms and critical information ..................................................................................................305 7.3.4 Visual alerts.................................................................................................................................305

7.3.4.1 General .............................................................................................................................................. 305 7.3.4.2 Icons, buttons and controls ................................................................................................................ 306 7.3.4.3 Use of colours principles................................................................................................................... 306 7.3.4.4 Brightness / intensity coding ............................................................................................................. 308 7.3.4.5 Flashing............................................................................................................................................. 309

7.3.5 Auditory alerts.............................................................................................................................309 7.3.5.1 Differentiation of signals................................................................................................................... 309 7.3.5.2 Signals meaning ................................................................................................................................ 310 7.3.5.3 Duration ............................................................................................................................................ 310 7.3.5.4 Acknowledging signals ..................................................................................................................... 310

7.3.6 Designing windows......................................................................................................................311 7.3.6.1 General .............................................................................................................................................. 311 7.3.6.2 Window states ................................................................................................................................... 311 7.3.6.3 Window organisation ........................................................................................................................ 312 7.3.6.4 Window component – Title bar ......................................................................................................... 312

7.3.7 System response time...................................................................................................................312

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


1 INTRODUCTION

1.1 Document purpose and scope This document is the deliverable D2 of the WP2 of ITWP project in 2008. It is the update of the delivrable HMI solution design V2 (see [Ref. 1] ). The objectives of this document is to describe the EUROCONTROL ITWP solution (release: TWR based on the eDEP, 28th Nov. 2008). It must be emphasized that the EUROCONTROL design supports a specific solution (i.e. other solutions are possible). Particular attention has been put to facilitate the update and traceability of modifications throughout the ITWP development lifecycle and ease the integration of new functionality that will be developed in 2008 and covered in future releases ITWP documentation.

1.2 Methodology Emphasis has been put to distinguish between requirements (functional and HMI requirements) - independently of any HMI solution - from an HMI solution i.e. procedures, detailed HMI objects and interactions which The methodology adopted in this document is to describe: • A set of working procedures (equivalent to use cases) that describes the different action possibilities provided by the function and suggesting the ways in which the controller would use it. A procedure is described by its objectives, the actors involved, the triggering conditions, the necessary pre-conditions and the dialog, i.e. by the sequence of actions/consequences.

• A set of HMI objects the controller needs to carry out the procedures. An object is described in terms of its objectives, when and where it is available, and how it is presented, and

• To link them with the set of requirements, i.e. functional and associated HMI requirements.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Figure 1: Overall model structure example

1.3 Structure of the document The content of this document is organised as follows:

• Section 2 addresses the main principles that underlie the proposed design;

• Section 3 describes the requirements related to the interface and fonctunalities of the ssytem

• Section 4 provides the description of HMI objects used;

• Section 5 addresses the associated procedures;

• Section 6 lists the requirements referenced in the design of objects and procedures;

• Section 7 presents the transversal human factor requirements.

Main Functions

{{{{{{{{

{{{{

{{{{{{{{

Procedures(solution)

Sub-Functions

Requirements

Objects(solution)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


1.4 Acronyms ACC Area Control Centre AIBT Actual In Block Time APP APProach A-SMGCS Advanced Surface Movement Guidance & Control System ATCO Air Traffic COntroller ATM Air Traffic Management ATS Air Traffic Services CLD CLearance Delivery CWP Controller Working Position Comb. Combined EFS Electronic Flight Strip (synonym to e-strip) ELDT Estimated LanDing Time EOBT Estimated Off Block Time GND GrouND HMI Human Machine Interface ICAO International Civil Aviation Organisation IFR Instrument Flight Rules ITWP Integrated Tower Working Position RGB Red Green Blue RWY RunWaY TWR ToWeR UTC Universal Time Coordinates WIMP Windows, Icons, Menus and Pointers

1.5 Reference documents [Ref. 1] ITWP – HMI Solution specifications V2, Draft V03122007, Dec. 2007, Eurocontrol [Ref. 2] ITWP – Functional specifications, V1.0, 12th Dec 2008, Eurocontrol

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


2 PRINCIPLES

2.1 TWR Configuration It is important to note that the TWR forms an integrated part of the system. It is to be regarded as a sector just as an APP or ACC sector. The main difference being that the geographical extension of the sector both lateral and vertical is limited compared to ACC and APP sectors.

The Air Traffic Services (ATS) provided by the TWR sector may be delegated to several different controller working positions (CWP’s) also referred to as Operator Roles (an operator role is a defined set of working responsibilities to be performed by an operator).

Three different controller positions will be considered: Ground Control position, Runway Control position and Clearance Delivery position.

For ITWP TWR prototype, Operator Roles are:

• GND controller (GND) – the controller handling the traffic on the apron and taxiways

• RWY controller (RWY) – the controller handling the traffic on the runway.

• Clearance Delivery (CLD)

notes:

a) GND, RWY and CLD control positions are addressed in this document release. Pilots’ positions and TMA position are not part of this document.

b) These Operator Roles might be configured in a variety of combinations e.g. RWY arrival controller, RWY departure controller, each controller role separate, two roles merged, or even all roles merged.

2.2 TWR Functionality and Procedures The TWR sector transfers and assumes flights to/from APP/ACC sectors in exactly the same manner and follow the same rules as are used between other sectors (e.g. APP and ACC sectors).

Inside the TWR sector it is also intended to use system assisted co-ordination between Operator Roles in the same manner as between sectors. It is not foreseen that the full range of messages/or similar data exchange known from the APP/ACC environment should be used, but only specific messages/data exchange such as notification of flights and transfer of communication.

The HMI should however be the same or as close as possible to the HMI used between sectors.

The fixed sequence for arriving flights will be either:

• [APP] � RWY-A � GND-A, or • [APP] � Comb-A.

The fixed sequence for departing flights will be either:

• [CLD] �GND-D � RWY-D � [APP], or • Comb-D. � [APP]

note: in ITWP prototype, APP controller actions will be ensured by the System (i.e. is a system dummy function used to simulate transfer of flights to/from APP). It is also assumend that controller has a possibility

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


to have a vehicle driver or a pilot of towed aircraft on frequency so as the controller can give routing / guidance instructions.

2.3 Traffic planning states

2.3.1 Main states and sub-states Some definitions:

• Main state: is a state in which a traffic can be seen from an individual ATM system point of view. Each main state can have more sub-states.

• Sub-state: is a state in which a traffic can be seen from an individual control area of responsibility. Sub-states can affect the behaviour of the display and the possible control instructions/inputs authorised by the system to the controller.

The main traffic planning states considered in ITWP are:

• Not concerned: traffic for which the current operator role is not responsible.

• Pending: traffic planned to be under control responsibility of the current operator role, but not yet assumed.

• Assumed: traffic for which the current operator role is responsible.

Possible sub-states are:

• No value (default sub-state);

• Pending in (pending sub-state);

• Assumed out (assumed sub-state);

note: at system initialisation, all traffic is in ‘Not concerned’ planning state.

2.3.2 Transitions between main states The diagram of state transitions is as follows: 1. Not concerned to Pending: possible 2. Not concerned to Assumed: not possible (state possible for a vehicle and towed aircraft) 3. Pending to Not concerned: not possible 4. Assumed to Not concerned: possible 5. Pending to Assumed: possible 6. Assumed to Pending: not possible

2.3.2.1 ‘Not concerned’ to ‘Pending’ transition The transition from Not concerned to Pending planning state is governed by the following rules:

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


• Arrival flight:

� RWY or Combined operator role: at a time parameter before ELDT (Tpending-arr). This time parameter is defined at local level1. � GND operator role: - The transition from Not concerned to Pending on the first GND control position is triggered on a

specific event RWY controller input2 (i.e. ‘Assume’) or at a time parameter before ELDT. The triggering parameter is defined at local level3.

- The transition from Not concerned to Pending on all GND control concerned positions is triggered at ‘Transfer’ between RWY controller and first GND position.

• Departure flight:

� GND or Combined operator role: - The transition from Not concerned to Pending on the first GND control position is triggered at a time

parameter before EOBT (Tpending-dep). The triggering parameter is defined at local level4. - The transition from Not concerned to Pending on all GND control concerned positions will be

triggered at transfer between clearance delivery position and the first GND position.

� RWY operator role: the transition is triggered either on ‘Pushback’ (if aircraft pushback is required), ‘Taxi’ clearance input by the first GND control position concerned by the flight5, or - in absence of ATCO clearance - when the system detects that the aircraft is moving.

• Vehicle :

� RWY or Combined operator role: the transition from Not concerned to Pending on the RWY position is triggered when the GND controller inputs a ‘Transfer RWY’ in the vehicle radar label. � GND operator role: the transition from Not concerned to Pending on the GND position is triggered when the RWY controller inputs a ‘Transfer GND’ in the vehicle radar label.

2.3.2.2 ‘Not concerned’ to ‘Assumed’ Transition (v ehicle and towed aircraft only)

• Vehicle / towed aircraft: � RWY operator role: when a vehicle/towed aircraft is assumed by the RWY controller. � GND operator role: when a vehicle/towed aircraft is assumed by the GND controller.

1 Tpending-arr is set to 20 minutes 2 Non nominal case: if the RWY controller does not issue the triggering event (‘cleared to land’ or ‘continue approach’), the system will automatically trigger the transition from ‘Not concerned‘ to ‘Pending’ when landing event is detected. 3 Set to 1 minute. 4 Set to 5 minutes 5 Non nominal case: if the GND controller does not issue the triggering event (‘pushback’ or ‘taxi’), the system will automatically trigger the transition from ‘Not concerned’ to ‘Pending’ when aircraft starting to roll is detected.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


2.3.2.3 ‘Assumed’ to ‘Not concerned’ Transition The transition from Assumed to Not concerned planning state is governed by the following rules: • Arrival flight:

� RWY operator role: when the aircraft is assumed by the next operator role, i.e. the GND operator role. � GND or Combined operator role: when the AIBT (Actual In Block Time) of the aircraft is logged (system-generated event).


� RWY or Combined operator role: when the aircraft is transferred to approach/TMA sector. � GND operator role: when the aircraft is assumed by the next operator role, i.e. the GND operator role.

2.3.2.4 ‘Pending’ to ‘Assumed’ Transition The transition from ‘Pending’ to ‘Assumed’ planning can be triggered only when the flight is in ‘Pending-in’ sub-state. • Arrival flight:

� RWY or combined operator role: the controller will assume the aircraft via ‘Assume’ order. � GND operator role: the controller will assume the aircraft via ‘Taxi’ input instruction.


� GND or combined operator role: the controller will assume the aircraft via ‘Assume’,‘ Start Up’ or ‘Pushback’ instructions. � RWY or combined operator role: the controller will assume the aircraft via ‘Assume’, ‘ Hold’, ‘ Line Up’, ‘ Conditional Line Up’ or ‘Take off’ instruction.

Note: The transition from ‘Pending’ to ‘Assumed’ is specific for a vehicle transfer between controllers. The controller will assume a vehicle via ‘Assume’ order in the radar lable or on EFS.

2.3.3 Transition between sub-states

2.3.3.1 ‘No value’ to ‘Pending-in’ transition The ‘Pending’ sub-state has initially ‘No Value’. The transition to ‘Pending in’ sub-state will be triggered when the flight is in pending state, and has been transferred from previous sector but is not yet assumed by the controller. • Arrival flight:

� RWY or combined operator role: the transition will be triggered when the APP controller transfers the flight to the RWY controller. note: as there is no APP controller role in ITWP simulation, the transition is system-generated at a time parameter (Tpending-in-arr) before ELDT, with Tpending-arr ≥ Tpending-in-arr. Typical values are Tpending-arr: 20 minutes (see above, section 2.3.2.1). Tpending-in-arr: 5 minutes; these are defined and subject to modification at local level.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


� Ground operator role: the transition is triggered when the APP controller transfers the flight to the RWY controller6.


� GND or combined operator role: the transition will be triggered at a time parameter (Tpending-in-dep) before EOBT, with Tpending-dep ≥ Tpending-in-dep. Typical values are Tpending-dep: 5 min. Tpending-in-dep: 2 min. These values shall be defined at local level. � RWY operator role: the transition will be triggered at transfer from GND control position7.

2.3.3.2 ‘No value’ to ‘Assumed Out’ transition The ‘Assumed Out’ sub-state has initially ‘No Value’. The transition to ‘Assumed Out’ sub-state will be triggered when the flight is in ‘Assumed’ state, and has been transferred to the next control position but is not yet assumed. • Arrival flight:

� RWY role: the transition will be triggered when the controller has input a ‘Transfer’ or ‘Vacate’ clearance. � GND or combined role: no need if there is only one GND or combined role concerned. In case of several GND or combined roles positions concerned by the flight, the transition will be triggered when the controller has input the ‘Transfer’ clearance.

• Departure flight: � GND role: the transition will be triggered when the controller has input a ‘Transfer’ clearance8. � RWY or combined role: the transition will be triggered when the RWY controller has input a ‘Transfer’ clearance to TMA controller; note: when the aircraft is transferred to APP/TMA controller, the transition to ‘Not Concerned’ will automatically be triggered by the system at a time parameter (local level).

2.4 Colour Coding

2.4.1 Default colours A set of default colours are used in ITWP. These default colours are off-line parameters that can be tuned at local level. a) Traffic: • ‘Arrival colour’: set to dark brown; • ‘Departure colour’: set to dark blue; • ‘Other Traffic Colour’ (i.e. vehicles, towed aircraft, non-identified traffic): dark green. b) Warning, information alert and alarm:

6 Non nominal case: if the RWY controller does not issue the flight transfer, the system will automatically trigger the transition to pending-in when it has detected that the aircraft has vacated the runway. 7 Non nominal case: if the GND controller does not issue the flight transfer, the system will automatically trigger the transition to pending-in when it has detected that the aircraft has reached the holding point.

8 Non nominal case: in case of no controller input when the aircraft has reached the holding point, the system will automatically trigger the transition to assumed out sub-state.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


• ‘Warning and information alert colour’: yellow9 • ‘Alarm colour’: red10 c) traffic planning sub-states: • ‘Pending-in colour’: white • ‘Not concerned colour’: dark grey • ‘Assumed out colour’: dark grey d) text colour: • ‘Text Colour’: black d) Mark background colour: • ‘Mark Colour’ (background): green e) Other logical colours used in this document: • TextUnselected, TrackSelected, Speedvector colour: black • TrackUnselected: white

• Button1Depressed: (RGB 48,37,21; 0..255 proportions: 122,94,54)

• Button2Depressed: (RGB 24,31,37 ; 0..255 proportions: 69,79,94)

• Cursor, Warning, StoredValue colour: yellow

• Interaction colour: bright blue (RGB 0,100,100; 0..255 proportions: 0,255,255)

• Worktop colour: (RGB 29,32,29; 0..255 proportions: 74,82,74)

notes:

a) In the following, ‘callsign’ refers to the callsign field wherever presented; ‘text’ refers to text in label and e-strip.

b) Alarm and information alert colours have priority over any callsign background colour.

2.4.2 ‘Not concerned’ planning state colours Traffic in ‘Not Concerned’ planning state has its labels and symbols and data list (if any) in ‘Not-Concerned Colour’.

2.4.3 ‘Pending’ planning state colours There are different cases depending on the traffic planning sub-state. a) sub-state ‘No value’: • Arrival flight: callsign is displayed in ‘Arrival Colour’ (see §2.4.1), rest of the text, leader line and aircraft

symbol are displayed in ‘Text Colour’. • Departure flight: callsign is displayed in ‘Departure Colour’, rest of the text, leader line and aircraft

symbol are displayed in ‘Text Colour’. • Other traffic: callsign is displayed in ‘Other Traffic Colour’, rest of the text, leader line and traffic symbol

are displayed in ‘Text Colour’.

9 A warning is an information to the controller (e.g. parking stand is occupied).

10 An alarm is an alert of higher severity than an information alert

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


b) sub-state ‘Pending in’: • Arrival flight: callsign is displayed in ‘Arrival Colour, callsign background is in ‘Pending in colour’; the

rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’. • Departure flight: callsign is displayed in ‘Departure Colour, callsign background is in ‘Pending in

colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’. • Other traffic: callsign is displayed in ‘Other Traffic Colour, callsign background is in ‘Pending in colour’;

the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’.

2.4.4 ‘Assumed’ planning state colours a) sub-state ‘No value’: • Arrival flight: callsign, leader line, aircraft symbol and text are displayed in ‘Arrival Colour’. • Departure flight: callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. • Other traffic: callsign, leader line, traffic symbol and text are displayed in ‘Other Traffic Colour’. b) sub-state ‘Assumed out’: • Arrival flight: callsign is displayed in ‘Arrival Colour’; the rest of the text, leader line and aircraft symbol

are displayed in ‘Not Concerned’ colour. • Departure flight: callsign is displayed in ‘Departure Colour’; the rest of the text, leader line and aircraft

symbol are displayed in ‘Not Concerned’ colour. • Other traffic: callsign is displayed in ‘Other Traffic Colour’; the rest of the text, leader line and aircraft

symbol are displayed in ‘Not Concerned’ colour.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


2.5 Strip bays As a principle, strip bays at each working position should display: • Traffic that will become controlled in the near future (pending traffic), • Traffic under control (active traffic), • Traffic for which transfer to another controller role has been initiated (transfered traffic). Depending on controller role and local considerations, traffic may be presented to the controller in different bays. Each bay can then be composed of different sections for planning and control purpose.

2.5.1 RWY controller bays Note: The organisation of bays require further investigations; the different bays described below reflect the design presented to controllers during the third ITWP evaluation session (Nov.08)). However as flexibility is required by controllers to organise sections (resulting from the 3rd ITWP evaluation session), grouping sections in bays need to be assessed again in the future. Thus, objects and procedures described in this document only address sections (and not bays); possible bays (and associated names) are only intended to help the reader for better understanding. In the following is described the solution adopted for ITWP for the RWY, GND and CLD controllers. Other configurations may be defined depending on local considerations and should be defined off-line.

2.5.1.1 Taxi Out Bay The taxi out bay is organised in two sections: • PENDING DEP section

� should be opened (system-generated) when a departure flight is given ‘Pushback’ (if any) or initial ‘Taxi’ instruction (when aircraft pushback is not required). � remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default to the left of the RWY section and above the Holding Point section (see below).

• HOLDING POINT section

� should be opened (system-generated) when a departure flight is assumed by the RWY controller or the GND controller transfer a vehicle to the RWY controller. � remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default to the left of the RWY bay (below the PENDING DEP section if it is opened).

Figure 2a: RWY Control Position (Taxi Out Bay)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


2.5.1.2 RWY Bay The RWY bay includes pending arrival traffic and active (departure and arrivals) traffic. This bay includes active vehicle/towed aircraft having clearances to cross/enter the runway. The RWY bay is organised into the following sections: • PENDING ARR11 section

� should be opened (system-generated) when at least one flight is less than 20 minutes before ELDT or if a go-around instruction has been issued by the controller. � remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default above FINAL and RWY sections.

• FINAL section

� should be opened (system-generated) when - at least one e-strip is displayed in the PENDING ARR section, or - at least one e-strip is displayed in the FINAL section12, or - if a go-around instruction has been issued by the controller. � remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default between PENDING ARR and RWY sections.

• RWY section � should be opened (system-generated) when - at least one arrival e-strip is displayed in the FINAL section, or - at least one arrival or departure e-strip is displayed in the RWY section13, or - a go-around instruction has been issued by the controller, or - at least one departure e-strip is displayed in the HOLDING POINT section or - one vehicle/towed aircraft is cleared to cross / enter the RWY � remains open as long as there is at least one e-strip strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default below the FINAL section. � The RWY section indicates the RWY in use and surface wind at touchdown (TD) and stop end (SE); � A flight is placed under the RWY divider when: - when an arrival flight is given a ‘Cleared to land’, or - When a departure flight is given a ‘Line up’ or ‘Conditional Line Up’; � A vehicle is placed under the RWY divider when: - A vehicle / towed aircraft is given a “Cross” or “Enter” clearance

11 Arrival 12 Triggered by ‘Assume’ RWY controller instruction. 13 Triggered by ‘Continue Approach’ controller instruction.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Figure 2b: RWY Control Position (RWY Bay) – updated Dec. 2008

2.5.1.3 Transfer Bay • TAXI-IN section

� should be opened (system-generated) when - at least one arrival flight or vehicle e-strip is displayed in the RWY section (either above or below the

runway divider strip). � remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default to the right and in line with the bottom of the RWY section.

• AIRBORNE section

� should be opened (system-generated) when - at least one departure e-strip is displayed in the RWY section (either above or below the runway

divider strip) or - if there is a go-around flight. � remains open as long as there is at least one e-strip strip in this section. � is closed (system generated) when conditions above no longer exist. � is displayed by default to the right and in line with the bottom of the RWY section and above the TAXI-

IN section if present.

Figure 2c: RWY Control Position (Transfer Bay)

2.5.2 GND Controller Bays The traffic is organised in two bays; for readability purpose of this document, these bays have been named ‘outbound bay’ and ‘RWY bay’.

2.5.2.1 Outbound Bay The ‘outbound bay’ is organised in the following sections: • PENDING DEP section

� should be opened (system-generated) when at least one flight is 5 minutes from its EOBT; � remains open as long as there is at least one e-strip in this section.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


� is closed (system-generated) when conditionsabove no longer exist. � is displayed by default above the PUSHBACK and TAXI-OUT sections.

• START section (only available if CLD position is not available; in the current version of ITWP, the

START section is available on the CLD position only)

� should be opened (system-generated) when at least one flight is displayed in the PENDING DEP section. � remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditionsabove no longer exist. � is displayed by default above PUSHBACK and TAXI-OUT sections.

• PUSHBACK section

� should be opened (system-generated) when at least one flight is displayed in the PENDING DEP section .

� remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default above the TAXI-OUT section.

• TAXI-OUT section

� should be opened (system-generated) when at least one flight is displayed in the PUSHBACK section or when a vehicle is transferred from the RWY controller to the GND controller.

� remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default at the bottom of the bay.

Figure 3a: GND Control Position (Outbound Bay) – Updated Dec. 2008

2.5.2.2 Runway Bay In ITWP, the Runway Bay (GND controller) groups arrival sections (PENDING ARR and TAXI IN sections) as well as transfer to RWY section. • PENDING ARR section

� should be opened (system-generated) when at least one arrival flight is assumed by the RWY controller.

� remains open as long as there is at least one e-strip in this section. � closes when above conditions no longer exist. � is displayed by default above the TAXI-IN and TRANSFER to RWY sections (if present).

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


• TAXI IN section

� should be opened (system-generated) when at least one arrival flight is displayed in PENDING ARR section.

� remains open as long as there is at least one e-strip in this section. � closes when above conditions no longer exist. � is displayed by default above the TRANSFER to RWY section (if present).

• TRANSFER to RWY section

� should be opened (system-generated) when at least one departure flight is displayed in the TAXI-OUT section

� remains open as long as there is at least one e-strip in this section. � closes when above conditions no longer exist.

Figure 3b: GND Control Position (RWY Bay) – Updated Dec. 2008

2.5.3 CLD Controller Bay Only one bay is required to organise the CLD traffic is organised; for readability purpose of this document, this bay has been named ‘outbound bay’. The ‘outbound bay’ is organised in the following sections: • PENDING DEP section

� should be opened (system-generated) when at least one flight is 5 minutes from its EOBT; � remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditions above no longer exist. � is displayed by default above CLD ACTIVE and START sections.

• CLD ACTIVE section

� should be opened (system-generated) when at least one arrival flight is displayed in PENDING DEP section.

� remains open as long as there is at least one e-strip in this section. � closes when above conditions no longer exist. � is displayed by default above the START section

• START section

� should be opened (system-generated) when at least one flight is displayed in the CLD ACTIVE section.

� remains open as long as there is at least one e-strip in this section. � is closed (system-generated) when conditionsabove no longer exist. � is displayed by default at the bottom of the CLD bay.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Figure 3c: CLD Control Position (CLD Bay) – Updated Dec. 2008

2.5.4 Typical flight lifecycle In the following pages are described typical arrival and departure flights lifecycle. It is important to note that: • Clearance Delivery position (CLD) has not been considered in this section. • A single Ground Position is considered. • In the numbering, ‘SG.n’ refers to a System-Generated event; ‘CA.n’ refers to a Controller action event. Arrival flight The figure below summarises the evolution of an arrival flight for a RWY controller and the possible transitions between clearance orders.

Assume

GO AROUND Transfer To APP

VIS

ClearToLand VACATE Transfer To GroundClearToLand VACATEVACATE Transfer To GroundTransfer To Ground

a/c becomes ASSUMED

a/c is PENDING-IN

a/c message moves back to Final section

a/c message moves below Runway divider

a/c message moves To transfer section

a/c message moves To Airborne section

a/c becomes ASSUMED OUT

1

a) Evolution of an arrival flight when ‘hold at’ and ‘stop at’ clerances are not implemented

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


b) Evolution of an arrival flight when ‘hold at’ and ‘stop at’ implemented are not implemented

Figure 4: Evolution of an arrival flight (RWY contr oller); a) – no parallel runways, b) parallel runways

Figure 5a below summarises the evolution of an departure flight for a GND controller (in that case, clearance delivery is ensured by GND control) and the possible transitions between clearance orders.

Note: without a ‘stop at’ order

Assume


VIS

ClearToLand HOLD AT

Transfer To Ground

a/c becomes ASSUMED

a/c is PENDING-IN






CROSS

STOPATVACATE

Note: in case two parallel runways, the arrival flight must cross the parallel runway while taxing to the paring stand

Assume


VIS

ClearToLand HOLD AT

Transfer To Ground

a/c becomes ASSUMED

a/c is PENDING-IN






CROSS

STOPATVACATE

Assume


VIS

ClearToLand HOLD AT

Transfer To Ground

a/c becomes ASSUMED

a/c is PENDING-IN






CROSS

STOPATVACATE

Note: in case two parallel runways, the arrival flight must cross the parallel runway while taxing to the paring stand

Assume

Assume Push

StopAt

Transfer

Start Push

When GNDsays STBY

When GNDsays STBY

Taxi

Assume StopAt

Hold

Assume

Assume Push

StopAt

Transfer

Start Push

When GNDsays STBY

When GNDsays STBY

Taxi

Assume StopAt

Hold

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Note: with a ‘stop at’ order

Figure 5a: Evolution of a departure flight (GND controller, without CLD control position)

The following tables are intended to explain the different HMI consequences of transitions for a typical arrival flight and a typical departure flight. Note: In the following tables, the full text of options and clearances has been provided for readability purpose (e.g. ‘Assume’, ‘ Go Around’ etc.). The following abbreviations will be used on the e-strip and callsign menus: ASSUME (‘Assume’), LND (‘Cleared to Land’), GO (‘Go Around’), ROF (‘Request On Frequency’), VAC (‘Vacate’), VIS (‘Visual Circuit’), TAXI (‘ Taxi’) , HOLD (‘Hold’), HOLD AT (‘Hold At’), STOPAT (‘Stop At’), CLU (‘ Conditional Line Up’), LUP (‘Line Up’), TOF (‘Clear for Take Off’), ABT (‘ Abort Take Off’), AIR (‘ Airborne’), START (‘Start-Up’), PUSH (‘PushBack’), TOW (‘Tow’), REL (‘Release’). ‘Transfer’option will be displayed as <Control Position> <Frequency>, e.g. GND 121.950 (frequency is the interactive field). The abbreviations will be identical on the e-strip and in the callsign menu with the following exceptions: ‘Mark’, ‘ Unmark’ and ‘Cancel14’ will use full words in the callsign menu; ‘M’ and ‘UM’ will be the abbreviations used for ‘Mark’, ‘ Unmark’ on the e-strip; ‘Mark’, ‘ Unmark’ on the e-strip will be accessed via a specific field (and not via e-strip clearance field). There is no ‘Cancel’ on the e-strip. Note: in case where a CLD control position is implemented, co-ordination is required between CLD and GND control positions. Figure 5b below summarises the evolution of a departure flight.

July 2007.

14 Cancel states for the undo order facility (e.g. to cancel LND id –[LND] in the callsign menu)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Figure 5b: Evolution of a departure flight (with CL D control position) – updated Dec. 2008

ASSUME

CLR

DCLR

START Transfer ASSUME TAXI

PUSH

STOP AT

HOLD Transfer

CLD GND

ASSUME

CLR

DCLR

START Transfer ASSUME TAXI

PUSH

STOP AT

HOLD Transfer

CLD GND

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Typical Arrival Flight (1/4) Actions / Events RWY controller GND controller

SG.1

ELDT -20 min .

1. The aircraft is displayed in the RWY bay / Pending Arr. Section. 2. The planning state is set to ‘Pending’, the sub-state has ‘No Value’. Callsign is displayed in ‘Arrival Colour’, rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’ (ref. §2.3.3.3). 3. ‘Request on Frequency’, ‘Mark’, and ‘Cancel’ options are available in the callsign menu, ‘Request on Frequency’ in the e-strip clearance field (see note above, previous page).

-

SG.2

ELDT–5 min .

1. The planning state is ‘Pending’, the sub-state changes to ‘Pending-in’. Callsign is displayed in ‘Arrival Colour, callsign background is in ‘Pending in colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’ (ref. §2.3.3.3). 2. ‘Assume’ (most probable option), ‘Mark’ and ‘Cancel’ options are available in the callsign menu, ‘Assume’ in the e-strip clearance field.

-

CA.3

RWY controller inputs ‘Assume ’

1. The aircraft is displayed in the ‘RWY’ bay / ‘Final’ section. 2. The planning state changes to ‘Assumed’, the sub-state is ‘No value’. Callsign, leader line, aircraft symbol and text are displayed in ‘Arrival Colour’. 3. ‘Cleared to land’ (most probable option), ‘Go Around’, ‘ Mark’ and ‘Cancel’ options are available in the callsign menu; ‘Cleared to land’ (most probable option), ‘Go Around’ in the e-strip clearance fields.

1. The e-strip is displayed in the ‘Pending arrival’ section of the ‘RWY’ bay 2. The planning state is set to ‘Pending’, the sub-state is ‘No value’. Callsign is displayed in ‘Arrival Colour’, rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’ (ref. §2.3.3.3) 3. ‘Mark’ and ‘Cancel’ is the only available options in the callsign menu; there is no option in the e-strip clearance field.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Typical Arrival Flight (2/4)

Actions / Events RWY controller GND controller

CA.4 RWY controller inputs

‘Cleared to land ’

1. The aircraft is displayed in the RWY bay / RWY section below the RWY divider. Two cases shall be envisaged: a) if the aircraft is airborne, i.e. the landing event is not triggered (either input by the controller or system generated), then ‘Go around’ (most probable option), ‘Mark’ and ‘Cancel’ are available options in the callsign menu; ‘Go around’ in the e-strip clearance field. a) if the landing event has been triggered (see above, a)), then ‘Vacate’ (most probable option) and ‘Transfer’ (to GND), ‘Mark’ and ‘Cancel’ are available options in the callsign menu; ‘Vacate’ (most probable option) and ‘Transfer’ in the e-strip clearance field. Note: in the case of two parallel runways, the following options are available in the callsign menu: ‘HOLD AT’ , ‘CROSS XX RWY’, ‘ENTER’ and ‘STOP AT’’ in the e-strip clearance field.

-

CA.5 [OPTIONAL]

RWY controller inputs

‘Go around ’

1. The aircraft moves to the ‘airborne’ section of the ‘transfer’ bay. 2. ‘Visual Circuit’ (most probable option), ‘Transfer’ (to APP), ‘Mark’, ‘Cancel’ are available options in the callsign menu; ‘Visual Circuit’ (most probable option), ‘Transfer’ (to APP) in the e-strip clearance field.

1. The e-strip is removed from the ‘Pending arrival’ section of the ‘RWY’ bay

CA.5a [OPTIONAL]

RWY controller inputs ‘Visual Circuit ’

1. The aircraft moves to the final section of the RWY bay. 2. ‘Cleared to land’ (most probable option), ‘Go Around’, ‘ Mark’ and ‘Cancel’ options are available in the callsign menu; ‘Cleared to land’ (most probable option), ‘Go Around’ in the e-strip clearance fields.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Typical Arrival Flight (3/4) Actions / Events RWY controller GND controller

CA.5b [OPTIONAL]

RWY controller inputs ‘Transfer’ (to APP)

note: for an arrval flight, follows a ‘Go around’ RWY controller instruction 1. The planning state is still ‘Assumed’, the sub-state changes to ‘Assumed out’. Callsign, leader line, aircraft symbol are displayed in ‘Arrival Colour’, the text is diplayed in ‘Assumed Out’ colour. 2. the e-strip is removed a time parameter (i.e. 1 minute) after ‘Transfer’ request (no TMA position).

-

CA.6 [OPTIONAL]

RWY controller inputs ‘Vacate’

1. The aircraft moves to the ‘taxi in’ section of the ‘RWY’ bay. 2. ‘Transfer’ (to GND), ‘Stop At’, ‘Mark’, ‘Cancel’ are available options in the callsign menu; ‘Transfer’ (to GND) in the e-strip clearance field.

1. The e-strip is displayed in the ‘Pending arrival’ section of the ‘RWY’ bay

CA.6a [OPTIONAL ] RWY controller inputs

‘Hold at’

1. The aircraft moves to the ‘taxi in’ section of the ‘RWY’ bay. 2. ‘Cross’, ‘Enter’, ‘Mark’ and ‘Cancel’ are available options in the callsign

menu The symbol for ‘hold at’ is displayed in the label (and in the e-strip)


CA.6b [OPTIONAL ] RWY controller inputs

‘Cross ’or ’Enter’

1. The aircraft moves to the ‘taxi in’ section of the ‘RWY’ bay. 2. ‘Vacate’, ‘Enter’, ‘Mark’, ‘Cancel’ and ‘Transfer’ are available options in the callsign menu 3. The borders of the runway that the aircraft crosses are highlighted in orange 4. The e-strip background is orange.

1. The e-strip is displayed in the ‘Pending arrival’ section of the ‘RWY’ bay 2. The e-strip background colour changes to orange

CA.6c [OPTIONAL ] RWY controller inputs

‘Stop At ’

1. The routing function displays the initally assigned and cleared route to the aircraft (e.g. solid green line); the ‘stop at’ menu pops-up with options to cancelthe latest selected taxi clearance limit or to close the menu. 2. ‘Hold at’, ‘Stop at’, ‘Mark’, ‘Cancel’ , ‘Transfer’ are available options in the


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


callsign menu 3. The holding point of the arrival flight (e.g. K1, K2, K3) is available in the callsign menu. 4. The holding point of the arrival flight is available in the e-strip.

CA.7

RWY controller inputs ‘Transfer’ (to GND)

1. The planning state is still ‘Assumed’, the sub-state changes to ‘Assumed out’. Callsign, leader line, aircraft symbol are displayed in ‘Arrival Colour’, the text is diplayed in ‘Assumed Out’ colour. 2. the e-strip is removed once the flight is assumed by the GND controller.

1. The planning state is still ‘Pending’, the sub-state changes to ‘Pending-in’. Callsign is displayed in ‘Arrival Colour, callsign background is in ‘Pending in colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’ / 2. ‘Taxi’ (most probable option), ‘Hold’ and ‘Mark’ are available options in the callsign menu and e-strip clearance fields.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Typical Arrival Flight (4/4)

Actions / Events RWY controller GND controller CA.8

GND controller inputs ‘Taxi’ or ‘Hold’

1. The e-strip is removed from the ‘Taxi in‘ section of the ‘RWY’ bay 2. The planning state changes to ‘Not Concerned’.

1. The planning state changes to ‘Assumed’, the sub-state is ‘No value’. Callsign, leader line, aircraft symbol and text are displayed in ‘Arrival Colour’. 2. The e-strip is displayed in the ‘Pending arrival’ section of the ‘RWY’ bay. 3. If ‘Hold’ has been input, then ‘Taxi’ (most probable option) and ‘Mark’ are available options in the callsign menu (‘Taxi’ in the e-strip clearance field). If ‘Taxi’ has been input, then ‘Hold’ and ‘Mark’ are possible options in the callsign menu (‘Hold’ in the e-strip clearance field).

CA.8 a GND controller inputs

‘Stop at’’

The planning state changes to ‘Not Concerned’.

1. The routing function displays the initally assigned and cleared route to the aircraft (e.g. solid green line); the ‘stop at’ menu pops-up with options to clear (cancel the latest given taxi clearance limit) or to close the menu. 2. ‘Hold’, ‘Stop at’, ‘Mark’, ‘Cancel’ and ‘Transfer’ are available options in the callsign menu

CA.9 The aircraft reaches its

arrival stand

-

1. EIBT is updated to AIBT (system-generated).

CA.10 AIBT + 2 min.

Aircraft data is removed (label) Aircraft data is removed (label and e-strip)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Typical Departure Flight (1/4) -without CLD Control P osition-

Actions / Events GND controller RWY controller SG.1

EOBT – 5 min.

1. The planning state is set to ‘Pending’, the sub-state is ‘No Value’. The callsign is displayed in ‘Departure Colour’, rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’. 2. The e-strip is displayed in the Pending Dep section of the Outbound bay 3. ‘Mark’ is the only available option in the callsign menu and e-strip clearance fields.

-

SG.2

EOBT – 2 min.

1. The planning state is still ‘Pending’, the sub-state changes to ‘Pending in’. The callsign is displayed in ‘Departure Colour, callsign background is in ‘Pending in colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’. 2. ‘Start up’ (most probable option), ‘Assume’, ‘Pushback’ and ‘Mark’ are available options in the callsign menu and e-strip clearance fields.

-

CA.3

GND controller inputs

‘Assume’, ‘Start Up’ or

Pushback’

1. The GND Controller can either assume the flight via ‘Assume’, ‘Start’ or ‘Pushback’ (optional) instructions.

2. The planning state is ‘Assumed’, the sub-state is ‘No Value’. The callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. 3. The e-strip is displayed in the corresponding section of the Outbound bay, i.e. Pending Dep section (if ‘Assume’), Start (if ‘Start up’), Pushback (if ‘Pushback’).

1. In case of ‘Assume’ or ‘Start’ instruction: nothing. 2. In case of ‘Pushback’ instruction (optional), the planning state turns to ‘Pending’, sub-state is ‘No Value’. The callsign is displayed in ‘Departure Colour’, the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’. The e-strip is displayed in the Taxi Out bay (pending dep. Section).

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Typical Departure Flight (2/4) -without CLD Control Po sition-

Actions / Events GND controller RWY controller CA.3

(see above)

GND controller inputs ‘Assume’, ‘Start’ or

‘Pushback’

4. The availability of options in the callsign menu and e-strip clearance fields depend on the order input by the controller. - in case of ‘Assume’ order, ‘Start ’ (most probable option), ‘Pushback’ and ‘Mark‘options are available. - in case of ‘Start Up’ order, ‘Pushback’ (most probable option), ‘Taxi’ and ‘Mark’ options are available. - in case of ‘Pushback’ option, ‘Taxi’ (most probable option), ‘Start up’ and ‘Mark’ options are available in the callsign menu and e-strip clearance fields.

See above.

CA.4

GND controller inputs ‘Taxi’

1. ‘Transfer’ (most probable option), ‘Hold’ and ‘Mark’ are available options in the callsign menu and e-strip clearance fields. The e-strip moves to the taxi out section of the outbound bay. ‘Transfer’, ‘Hold’ and ‘Mark’ are possible options (callsign menu, e-strip).

If ‘Pushback’ (optional) has not been previously input by the GND controller: a) then the ‘Taxi’ order triggers the e-strip display in the Pending Dep. Section of the taxi-out (RWY controller). b) the planning state turns to ‘Pending’, the sub-state is ‘No Value’. The callsign is displayed in ‘Departure Colour’, the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’.

CA.7

GND controller inputs ‘Transfer’

1. The planning state is still ‘Assumed’, the sub-state changes to ‘Assumed out’. The callsign is displayed in ‘Departure Colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Not Concerned’ colour. 2. The e-strip moves from the ‘taxi out’ section of the outbound bay to the ‘transfer to runway’ section of the runway bay. ‘Hold’ and ‘Mark’ are possible options.

1. The planning state is still ‘Pending’, the sub-state changes to ‘Pending in’. The callsign is displayed in ‘Departure Colour, callsign background is in ‘Pending in colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’. 2. ‘Assume’ (most probable option), ‘Hold’, ‘Line up’, ‘Conditional line up’, ‘Take-Off’ and ‘Mark’ are the available options in the callsign menu and e-strip clearance fields.

SG.8

The aircraft reaches the holding point

1. if the GND controller has not yet input a ‘Transfer’ order, this event has the same consequences as in CA.5.

1. if the GND controller has not yet input a ‘Transfer’ order, this event has the same consequences as in CA.5.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Typical Departure Flight (3/4) -without CLD Control Po sition-

Actions / Events GND controller RWY controller CA.9

RWY controller inputs ‘Assume’

1. The planning state becomes ‘Not concerned’. 2. The e-strip is removed from ‘Transfer to runway’ section of the runway bay.

1. The e-strip moves to the Holding Point section of the taxi-out bay. 2. The planning state is set to ‘Assumed’, the sub-state is ‘No value’. callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. 3. ‘Line up’ (most probable option), ‘Conditional line up’, ‘Hold’, ‘ Stop At’, ‘Take-Off’, ‘Transfer’, ‘ Mark’ are available options in the callsign menu and e-strip clearance fields.

CA.10

RWY controller inputs ‘Hold’

- 1. ‘Line up’ (most probable option), ‘Conditional line up’, ‘Taxi’, ‘Transfer’, ‘ Take-Off’, ‘Mark’ are available options in the callsign menu and e-strip clearance fields.

CA.11

RWY controller inputs ‘Line up’ or

‘Conditional Line Up’

- 1. ‘Line up’ or ‘Conditional line up’ could be skipped depending on operational conditions, i.e. in absence of ‘Line up’ or ‘Conditional line up’ order, ‘Take off’ would be equivalent to “Line Up and Take Off”. 2. ‘Take-Off’ (most probable option), ‘Transfer’, ‘Hold’, ‘ Mark’ are available options in the callsign menu and e-strip clearance fields.

CA.12

RWY controller inputs ‘Take-off’

- 1. ‘Transfer’ (to TMA), ‘ Abort Take-off’ and ‘Airborne’ (optional) are available options in the callsign menu and e-strip clearance fields.

CA.13 (optional)

RWY controller inputs ‘Abort Take-Off’

- 1. ‘Vacate’ (most probable option) and ‘Mark’ are available options in the callsign menu and e-strip clearance fields.

CA.14 (optional)

RWY controller inputs ‘Airborne’

- 1. if ‘Airborne’ (optional) is input, ‘Transfer’ is the available option. 2. The e-strip moves to the Airborne section of the Transferred Bay

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Typical Departure Flight (4/4) -without CLD Control Po sition- Actions / Events GND controller RWY controller

CA.15

RWY controller inputs ‘Transfer’ (to TMA)

-

1. The planning state is to ‘Assumed’, the sub-state changes to ‘Assumed out’. The callsign is displayed in ‘Departure Colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Not Concerned’ colour. 2. The e-strip moves to the Airborne section of the Transferred Bay (if CA.12 has not been performed) or stays in this bay (if already performed). No option is available in the callsign menu and e-strip clearance field.

SG.16

The aircraft reaches a pre-defined altitude or a time parameter after

take off (local parameter)

1. The planning state changes to ‘Not concerned’. 2. The e-strip is removed from the ‘Transferred Bay’.

Note: in the case where a CLD control position is implemented, coordination is required between CLD and GND ATCOs. Associated modifications are as follows (next two pages). Updated Dec. 2008.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Departure Flight – modifications linked to the imple mentation of a CLD position (1/2)

Actions / Events CLD Controller GND controller SG.1

EOBT– 5 min.

1. The planning state is set to ‘Pending’, the sub-state is ‘Pending in’. The callsign is displayed in ‘Departure Colour, callsign background is in ‘Pending in colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’. 2. The e-strip is displayed in the Pending Dep section of the Outbound bay (CLD role). 3. ‘Assume’ and ‘Mark’ are available options in the callsign menu and e-strip clearance fields.

CA.2

CLD controller inputs ‘Assume’

1. The callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. The planning state is ‘Assumed’, the sub-state is ‘no value’ 2. The e-strip is displayed in the CLD Active section of the Outbound bay (CLD role). 3. ‘CLR’ (most probable option), ‘DCLR’ (Data Link Clearance) and ‘Mark’ are available options in the callsign menu and e-strip clearance fields.

CA.3

CLD controller inputs ‘CLR’ or ‘DCLR’

1. The callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. 2. The e-strip is still displayed in the CLD Active section of the Outbound bay (CLD role). 3. ‘Start’ (most probable option – Start up) is the only available option in the callsign menu and e-strip clearance fields.

CA.4

CLD controller inputs ‘START’

1. The callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. 2. The e-strip is still displayed in the Start section of the Outbound bay (CLD role). 3. ‘Start’ (most probable option, i.e. start up) is the only available option in the callsign menu and e-strip clearance fields.

1. The e-strip is displayed in the Taxi Out bay (pending dep. Section). The planning state turns to ‘Pending’, the sub-state is ‘No Value’. The callsign is displayed in ‘Departure Colour’, the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Departure Flight – modifications linked to the imple mentation of a CLD position (1/2)

Actions / Events CLD Controller GND controller CA.5

CLD controller inputs

‘TRANSFER’

(by clicking on the next frequency, e.g. 121.95)

1. The planning state is still ‘Assumed’, the sub-state changes to ‘Assumed out’. The callsign is displayed in ‘Departure Colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Not Concerned’ colour.

1. The planning state is still ‘Pending’, the sub-state changes to ‘Pending in’. The callsign is displayed in ‘Departure Colour, callsign background is in ‘Pending in colour’; the rest of the text, leader line and aircraft symbol are displayed in ‘Text Colour’. 2. ‘Assume’ (most probable option), ‘Pushback’ and ‘Mark’ are the available options in the callsign menu and e-strip clearance fields.

CA.6

GND controller inputs ‘ASSUME’, ‘TAXI’ or

‘PUSHBACK’

1. The planning state becomes ‘Not concerned’. 2. The e-strip is removed from ‘Start section of the CLD outbound bay.

1. The planning state is set to ‘Assumed’, the sub-state is ‘No value’. callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. 2a. If the GND Controller inputs ‘Assume’, ‘ Taxi’ and/or ‘Pushback’ (available option if contact stand), ‘Stop at’ and ‘Mark’ are the available options in the callsign menu and e-strip clearance fields. 2b. If the GND Controller inputs ‘Pushback’ (available option if contact stand), The e-strip is displayed in the Taxi Out bay (pushback Section) . ‘Taxi’, ‘ Stop at’ and ‘Mark’ are the available options in the callsign menu and e-strip clearance fields. 2c. If the GND Controller inputs ‘Taxi’, The e-strip is displayed in the Taxi Out bay (taxi Section) . ‘Taxi’ , ‘Stop At’ and ‘Mark’ are the available options in the callsign menu and e-strip clearance fields.

CA.7 etc. Same as typical departure flight –without CLD control position- ( see above)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft

D2 - ITWP HMI Solution Specifications - Page 31 Draft

3 HMI and transversal FH requirements The system having an human-machine interface uses the human factor (HF) and HMI requirements for the system interface development (in our case ITWP prototype). Requirements have been split into:

• Transversal FH requirements or guidelines / General ITW P HMI requirements which are independent of function and should apply to all aspects of the ITWP interface, placed under the responsibility of human factors experts.

• Functional and associated HMI requirements. HMI requirements are specific to the individual function generating them.

General HMI requirements and transversal Human Factors requirements (XHF) are requirements or guidelines that potentially apply to all aspects of the ITWP interface. They relate to the general approach that the interface will adopt to interaction and are thus potentially applicable to any new function that would be added. General ITWP HMI requirements are ones adressing the basic graphical user interface management linked to windows and menus: .BL Basic HMI elements display and management .HMI To manage WIMP graphical user interface .LOG To access to CWP .SET To set up the display and access screen setting .TOOL To manage toolbars functions .ZOOM To zoom, offset and modify the geographical information .MAP To manage the display of surface and air information on the display In addition to the basic HMI requirements, the transversal FH requirements given in Ref. 2 adresses:

- Processes of interaction (behavioural consistency, level of user awareness, congnitive effort, etc.) - Inputs (basic inputs, accessibility of selected objects, reponse time, default sections, input devices

and input events, menues, input error management policy …) - Visual presentation rules and conventions (principals for the data presentation, check boxes, radar

labels, text propreties, maps and tactical displays, visual alerts, auditory alerts etc.) Transversal requirements are often integrated and expressed in terms of policies or conventions which are considered in the ITWP prototype development. Distinction has been made between requirements (X.HF.Rx) and guidelines (X.HF.Gx) to categorise between mandatory and desirable aspects. They are not individualy referenced in HMI objects and procedures. The HMI requirements associated to the functional specifications are available in the document “ITWP Functional Requirements” [ Ref. 2]. The ITWP is a possible HMI solution for the integration of systems and informations in the controller working position in the tower environement. The HMI prototype solution design is given via HMI objects and procedures. The HMI objects and procedures are linked to the previously defined requirements that are associated to the functional specifications. .BL requirements that are enabling the support functions like: .TIME To access time information .POS To manage the position of radar label .TRCK To manage the display of radar tracks

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


.VECT To manage the display of speed vectors .LBL To manage the content of radar labels .WAR To draw controller’s attention to a specific a/c or vehicle .SEL To select an individual aircraft or vehicle .TRAF To provide controllers with available data on any individual aircraft or vehicle .SIL To access data on all aircraft/vehicles entering or planning to enter a TWR sector .ORD To provide support to the controller for the input of clearances given to an aircraft .WEA To access to weather information .APT To set up airport elements status .FD To provide system support for data exchange and coordination between ATC units. .RUL To manage the distribution of flight data on control positions. .TRSF To provide system assistance for flight transfer control. .SN To provide the controllers with alerts to potentially hazardous situations in an effective manner and with sufficient warning time for appropriate instruction to be issued by ATC to resolve the situation, allowing for appropriate avoiding action to be taken by the pilot. .GEN General requirements regarding the alerts. .PROC To detect / display non conformance to ATC instructions / procedures (former CNF category

and MISC category) .CLRS To detect / display conflicting ATC clearances (former CLR category) .AREA To detect / display infringement of restricted / closed areas (merge of the former RCA

category – runway conflicts detection and alerting and LAY category – controllers input errors versus airport layout).

…..RWY To manage mobiles on the runway (crossing / entering). .PTD To manage protecting devices. .NAV To be informed about navaids serviceability. .ROUTE To provide support to the controllers regarding routing functions (i.e. effective modifications of routes initialy assigned to a mobile).

.DIS To provide support to the controller to display an assigned / cleared route to a mobile .CLR To provide support to the controller to validate / clear the initially assigned route .CHG To provide support to the controller to manage the modification of a route given to a mobile .VEH To provide support to the controllers to manage vehicles and towed aircraft .DIS To display vehicle traffic .ORD To manage vehicles by controlling their behaviour .SEQ To manage arriving and departuring traffic .DEP To manage departing traffic .ARR To manage arriving traffic. .DL To provide system support for air-ground communication between pilots and ATC unit controllers. .IDF To provide the controllers with information about data link equipped aircraft

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4 Description of HMI objects

4.1 Description of HMI objects

4.1.1 Worktop HMI Object WORKTOP

Objective To define the limits of the space of interaction with the system. It is the background surface on which all other display elements are presented, and defines the lower limit of the range of screen priorities.

General Description The worktop covers the entire addressable surface of the primary display. On the display, all the pixels of the worktop have the same RGB dynamic range. The visual presentation of the worktop is subdued in relation to other major display elements. The colour used is the ‘worktop’ colour (RGB 29,32,29; 0-255 proportions:

74,82,74: ).

Invocation Always present. Display Position Screen background (lowest interaction priority). Illustration - Requirement Ref. H.BL.HMI.01 | H.BL.HMI.02 Associated HMI objects CURSOR | WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.2 Window HMI Object WINDOW

Objective To encapsulate different processes for the purposes of easy reorganisation of information within the display, and to provide access as needed to an organised display surface, presenting information of a particular type: tabular lists, textual data, graphic images (e.g. maps), HMI tools, functional tools, system messages. etc.

General Description A window is defined by display attributes and its behavioural attributes. The visual appearance and behaviour of a window provide the user with cues as to its available properties. The following details all the possible features of a window (many windows will employ only a subset of these elements).

a) The frame of a window is defined by the line style, the colour of the border enclosing the window and the type of corners (square or round) related to the type of the window. A window frame can include: • A Header (or name bar) is at least 6.0 mm thick, located along the top edge of

each window frame. The number of lines of text contained in the header is specified as a parameter. The text font parameters and colour, and the background colour of the header part can be defined. The header portion of the window is not scrollable.

• Scroll bars (vertical and/or horizontal): if a window is defined to be scrollable, a

scroll bar is displayed automatically along the bottom edge or the right hand edge of the window frame when the content of the window exceeds horizontally or vertically the displayed page. A scroll bar consists of 3 parts :

� The scroll bar body. � The panning sliders: they are fixed size if the range of the possible

display is not limited (e.g. radar window), and variable size if there is a fixed range of display possible, the length of the slider displaying the proportion of the range currently visible.

� Left / Right and Down / Up scrolling arrow buttons: they are drawn in full colour if scrolling is possible in the direction indicated. If not (no further items available for example), the colour of the arrow is modified so that to effectively reduce the contrast of the arrow area.

The display features of the scroll bar elements are identical for all the windows.

• Function buttons : a window frame can include the following buttons: � Iconify button: an iconified window (Iconify window procedure) is

represented by a small icon, bearing a graphical representation or text identifying its content.

� Close button (Close window procedure) � Re-size button (Re-size window procedure) � Re-scale button (Re-scale window procedure)

Different visual forms and positions in the window frame should be employed for the function buttons.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


General Description b) the background colour The background colour of a window is a single colour displayed as the background for the entire window. Transparency should be an option for the background colour when the cursor is placed outside the window. Transparent background would allow the information placed underneath the window to be visible (although not necessarily legible), without affecting the legibility of the window content itself. c) the size (default, minimum, maximum) The window sizes are defined in terms of X and Y axes, and are expressed in pixels or characters. Default size relates to the window size at simulation initiation and may vary according to data posting during the course of a simulation, and preferences stored in the user preferences set. note : all the window sizes given in this document are the internal window area sizes. d) associated toolbox To each window, it should be possible to associate a toolbox with contents (tools) matched to the specific requirements of that window. This toolbox shall be movable only within its parent window. Where similar tools are required in different windows, they should be identical in form and operation. e) status (parent, child, independent) Each window possesses one of these statuses. Child windows are employed within the context of interaction with their ‘parent’ window, and have the following characteristics:

� a child window changes its priority with its parent window, � a child window cannot be moved outside its parent window, � a child window can never be positioned behind its parent window, � a child window can be moved in front of another family windows

stack. Independent windows do not have child windows. f) window priority Windows may overlap i.e. the general principle of window organisation is stacking. Windows screen stacking priority is defined, to determine the overlapping of their display representations. Windows are initially displayed in accordance with their priorities. On display, a window of a given priority is displayed in front of objects or windows of the same or of a less high priority. The proposed priorities are as follows:

• Cursor : priority 1 (highest priority), • System Message Window : priority 2, • Alert Window : priority 3, • General Toolbox Window (and Clock): priority 4, • Airport View Display Window: priority 6 (so that interacting with the radar

display will not cause it to be redrawn in front of the other displayed windows),

• All the other windows: priority 5.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Invocation The display of a window is initiated either automatically by the system, or manually by the controller by designation of objects or invoking fields. When invoked, windows are displayed in accordance with their display priorities.

Display Position The window display position is defined in terms of X/Y of top left-hand corner, and is expressed in pixels or characters. Default window position relates to the position of the window at simulation initiation, and may vary according to data posting during the course of a simulation, and preferences stored in the user preferences set.

Illustration Requirement Ref. H.BL.HMI.03 | H.BL.HMI.04 | H.BL.HMI.05 | H.BL.HMI.06 | H.BL.HMI.07 |

H.BL.HMI.08 Associated Procedures Initiates Close window | Come on top window | Iconify window | De-iconify window |

Move window | Re-size window | Re-scale window | Page scroll window | Slider scroll window | Step scroll window

Used by Open window Associated HMI objects WORKTOP | SWITCHES BUTTONS Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.3 Cursor HMI Object CURSOR

Objective To indicate to the user the locus of interaction and possible actions on the interface.

General Description The cursors shall have sufficient contrast in relation to all backgrounds against which they can appear. Since the pointing cursor can be moved against varying backgrounds and crossing lines of different colours, the proposed options are:

• a double black and white contour (demonstrated solution) • the outline of the cursor changes colour as a function of the current

background colour. The following cursors should be provided, reflecting a number of aspects of system activity (see illustrations of possibilities below):

• The Pointing cursor of a cursor is the pixel point within the cursor, which is returned as the value of the cursor location).

• The Busy cursor is used to indicate that the system is processing as a result of input. It reverts to the appropriate cursor when processing is complete. No other inputs are possible in the area while this is active. For the Clock (and the Hourglass) the hot spot is at the centre of the visible disk. The busy cursor should be dynamic (for example a spinning Hourglass). The speed of spin could effectively act as a secondary cue to the current loading on the system (on the assumption that it will slow as the system loading increases).

Note: in cases where the input action requires a particularly lengthy computation, it may be appropriate to provide a specific system message, by means of a suitable mechanism, to indicate the progress of this activity. It may even be necessary to release the cursor to permit the controller to undertake other activities while awaiting the outcome of this process. Possible examples could include the running of an induced conflict probe, or other calls to tools, or the use of a Datalink communications mechanism. However, this type of mechanism should be undertaken only with extreme caution.

• The Sighting cursors are used when the interaction has entered a mode. The shape is crosshairs of 10 mm in Cursor colour (yellow). The hot spot of this cursor is the centre of the cross.

• The Recentring cursor is used during the offset of the display centre of the situation display. It is a 5 mm square in Cursor colour (yellow). The hot spot of this cursor is the centre of the square.

• The Caution cursor is used to show that no input is currently possible in this region of the display, usually because some prior input requirement must be completed first. With a three button mouse, some inputs could be legal while others are not. Under these circumstances, the caution cursor shall only appear when the illegal button input is attempted or all button inputs would be illegal. The cursor reverts to previous cursor form when the pointer is moved from the illegal region or an attempt at an illegal input is terminated. The colour used for this cursor is the Alarm (red) colour. The hot spot is the centre of the disk.

• In addition, other “function specific” cursors may be employed within editing modes to indicate the nature of the functions available, or to communicate other information to the operator (e.g. a change of cursor form to direct the controller’s attention to some urgent or outstanding action elsewhere on the interface). Such cursors will be defined in the specification of the associated function.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Invocation Always present. Display Position Anywhere on the screen, depending on the user’s action on the pointing device.

Highest display priority. Illustration

Requirement Ref. H.BL.HMI.09 | H.BL.HMI.10 | H.BL.HMI.11 | H.BL.HMI.12 | H.BL.HMI.13 |

H.BL.HMI.14 Associated Procedures Associated HMI objects WORKTOP Particularities - Evolution Not implemented (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.4 Switches Buttons HMI Object

SWITCHES BUTTONS Objective To provide access to tools or to a set of options amongst which the controller can

make a selection in order to access information or to perform an action. General Description The buttons have different formats and colours providing the controller with

information on their functions and characteristics (see illustration of the different options below):

• Large buttons : give access to main elements of the HMI (windows, tools, menus…).

• Button1 colour (a) : give access to main windows or tools. • Button2 colour (b): give access to windows or menus in which additional

choices should be made.

The ON or selected state of both buttons is shown by Button1Depressed colour ( ) or Button2Depressed colour ( ).

• Medium buttons : give access to child windows or menus • Button2 colour (c): give access to child windows or menus in which

additional choices should be made, and initiate processing. The ON or selected state of these buttons is shown by Button2Depressed colour.

• small buttons : (minimum 5mm x 5mm):

• Button1 colour (d): Radio buttons for choosing between a range of options . The ON or selected state of Radio buttons is shown by Button1Depressed colour and the button surface label in TextSelected colour (white).

• Button2 colour (e): Toggle and push buttons for operating and

monitoring functions . The ON or selected state of these buttons is shown by Button2Depressed colour with text in TextSelected colour.

• Switch buttons (f) are used for selecting values on parameters . The

OFF or unselected form of Switch buttons is always in Button2Highlight colour. The ON or selected state is shown by Button2Depressed colour with a tick mark in TextSelected colour inside. Clicking AB on any Switch button toggles its state.

• In addition to the standard switch buttons, there a re a few special

Switch buttons (g), which are employed to manage an d provide feedback for functions with a series of states . These buttons are in the same colour as the conventional Switch buttons, but are distinguished by their form and size in that they are rectangular, 5mm in height and up to 30mm in length, allowing the presentation of single word feedback on the state of processes. The word is presented in TextUnselected colour (black) in OFF (unselected) state, and in TextSelected colour in ON (selected) state.

Switch buttons are distinguished from radio buttons in that they can all be set independently. Only one radio button can be selected at a time.

Invocation Not applicable Display Position Anywhere on the screen

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Illustration

Requirement Ref. H.BL.HMI.15 | H.BL.HMI.16 | H.BL.HMI.17 Associated Procedures Associated HMI objects MENU | WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.5 Menu HMI Object

MENU Objective To provide a dialogue object by which the user selects one or more inputs from

within a range of possible inputs. General Description A menu appears as an area on the display surface, presenting a set of selectable

items. The physical appearance of a menu shall be characterised by a set of display attributes:

• A menu frame , that can include • A header (or name bar) located along the top edge of each menu frame.

The number of lines of text contained in the header is specified as a parameter. The text font parameters and colour, and the background colour of the header part can be defined. The header portion of the menu is not scrollable. The header of a menu related to a particular aircraft always displays the identity (callsign) of that aircraft, and eventually the identification of the menu on a second line.

• A scrolling mechanism : if a menu is defined to be scrollable, it contains scrolling features which can be of different types:

� a scroll bar of the same type as that used for windows, situated to the right of the menu items

� arrow buttons situated above and below the menu items � or any other scrolling mechanism.

• A background colour The background colour of a menu is a single colour displayed as the background for the entire menu. • Number of menu items The number of displayed items is defined for each menu. These determine the size of the menu. • Default value A default value is defined for each menu. Several default values can be defined, depending on the current context when opening the menu. The text font parameters of the menu items, and colour of the available and unavailable options can be defined. Outside the scrollable area, toggle or push buttons may be added to the menu, allowing for additional functions.

Invocation The display of a menu is initiated by designation of fields or objects, called “initiating objects”.

Display Position The display position of the menu is defined relative to the invoking field or to the cursor position. Unless otherwise specified, when invoked, a menu is displayed so that the default value is under the cursor (to avoid cursor movement).

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.6 System Message Window HMI Object

SYSTEM MESSAGE WINDOW Objective To provide special information, or warnings, concerning the status of the system. General Description System Message Windows display messages that fall into two broad categories:

• System Information Messages: they are used to communicate temporary system conditions to users. For example, if system action in response to user input will take a significant time, a system information message could appear to explain that fact and to provide dynamic feedback as to the status of the activity. System information messages are removed with no specific user input when they are no longer relevant. They can also be closed by means of a conventional close box.

• Equipment Status Messages: they are used when a transition equipment status is detected (available � failure or failure � available). A specific input, e.g. user acknowledgement of a warning information is required. It is closed when the user completes the necessary actions.

Invocation System-generated Display Position At the current location of the cursor. Illustration - Requirement Ref. H.BL.HMI.25 Associated Procedures Initiates Move window Used by Open window Particularities - Evolution not implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.7 Logon Window HMI Object

LOGON WINDOW Objective To allow users accessing to and exiting from the CWP functions. General Description The Log On Window allows any user to enter a login and a password. Correct

login/password leads to display a window allowing to choose between different roles and profiles.

Invocation On system initialisation, the Log On Window is displayed open on the display. Display Position middle of the screen. Illustration - Requirement Ref. H.BL.LOG.01 | H.BL.LOG.02 | H.BL.LOG.03 Associated Procedures Used by Open window | Log On CWP | Log Out CWP Associated HMI objects CSD TOOLBOX WINDOW Particularities - Evolution not implemented (Dec. 2008)

4.1.8 Local Parameters HMI Object

LOCAL PARAMETERS Objective To define a number of the parameters used at local level. These parameters are

described in the related requirements. Associated HMI objects Particularities - Evolution not implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.9 Preferences Setting Window HMI Object

PREFERENCES SETTING WINDOW Objective To save and restore a preferred screen set-up. To adapt input logic, screen

settings and data display formats to the user's needs and preferences. General Description The Preferences Setting Window is divided into four regions with the following

contents: • Region 1 : 2 push buttons, labelled 'LOAD' and 'SAVE', and four radio

buttons labelled '1' to '3' and 'DEF'. (Ref. description in SWITCHES BUTTONS). If a screen configuration is stored under a numbered button, the text of the button number is displayed in StoredValue (yellow) colour.

The 'DEF' button label is in SelectUnavailable (grey75) colour to indicate that the default setting cannot be overwritten.

While depressed, the labels of the buttons invert from TextUnselected to TextSelected .

• Region 2 : an identifying label (‘Mouse’) in TextUnselected colour and two

radio buttons labelled ‘L’ and ‘R’, intended for setting the mouse for left or right handed users.

• Region 3 : an identifying label (‘Day Settings’) in TextUnselected colour

and three radio buttons labelled ‘Day’, ‘Night’, ‘Sun’, intended for setting the lighting ambiance.

• Region 4 : two identifying labels: ‘Brightness’ and ‘Contrast’ in

TextUnselected colour and two associated slider cursors (i.e. for brightness tuning and contrast tuning); each of these two slider cursors is associated with default selected value indicated inTextUnselected colour below the slider

General Description On initial start up, the screen set up is set to the default (‘DEF’ button selected)

defined at local level, and mouse hand is set to ‘R’ (right). Invocation Invoked by Single Click AB on the ‘PREF’ toggle button in the General Toolbox

Window (Ref. the Access Tool procedure). Display Position Below the General Toolbox Window. (Then can be moved anywhere on the

composite situation display window) Illustration

Requirement Ref. F.BL.SET.02 | H.BL.SET.01 | H.BL.SET.02 | H.BL.SET.03 | H.BL.SET.04 | H.BL.SET.05 | H.BL.SET.06 | H.BL.SET.07 | H.BL.SET.08 | H.BL.SET.09 | H.BL.SET.10

Associated Procedures Initiates Access Configuration Set-Up | Iconify window | De-iconify window | Come on

top window | Move window | Save Configuration Set-Up | Select day/night/sun settings | Fine Tune Brightness Settings | Fine Tune Contrast Settings

Associated HMI objects LOCAL PARAMETERS | COMPOSITE SITUATION DISPLAY WINDOW

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Particularities - Evolution not implemented (Dec. 2008), only load and save buttons are displayed (no

action). They are set under the “SUP” button.

4.1.10 General Toolbox Window

HMI Object GENERAL TOOLBOX WINDOW

Objective To group together a set of tools that relate to the whole interface. General Description

The General Toolbox contains a row of menus that are used to launch a variety of windows or functions:

• Toggle buttons corresponding to each of the primary windows potentially available within the interface. This addresses the access to:

a) Supervision Tool (‘SUP’ button) containing :

1)Preferences Setting Window (‘PREF’ button) 2) Credos setup configuration tool (‘CREDOS’ button) 3) Alerts setup tool (‘ALERTS’ button)

b) EFS Tool (‘BAYS ’ button) c) View Tool (‘VIEW’ button) d) MET window (‘MET’ button) e) NAVAIDS window (‘EQUIP’ button) f) EFS configuration tool (‘EFS’ button) g) Airport setup configuration tool (‘APT SETUP’ button) f) Timer window (‘TIMER’ button) It should be possible to add other tools to this toolbox as needs and capabilities emerge (note: ‘speed and track history tool’ is not implemented; corresponding HMI object is described in section 3.1.15). The GENERAL TOOLBOX WINDOW cannot be moved or iconified.

Invocation On system initialisation, the General Toolbox window is displayed on the display. Display Position Bottom left edge of the screen. Illustration

Requirement Ref. H.BL.TOOL.01 | H.BL.TOOL.02 Associated Procedures Initiates Access Tool | Isolate Tool | Move window | Iconify window | De-iconify window |

Come on top window Used by Display Universal Time | Isolate Tool Associated HMI objects PREFERENCES SETTING WINDOW | EFS CONFIGURATION TOOL | NAVAIDS

INFORMATION WINDOW | MET INFORMATION WINDOW | CSD S UB-VIEWS TOOL | EFS TOOL | AIRPORT SETUP TOOL | timer

Particularities The ALERT button has been implemented for the purpose of the third evaluation session only. The objective was to set up an alert or no alert simulation environment.

Evolution Updated ( Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.11 Composite Situation Display (CSD) Toolbox Wi ndow HMI Object

CSD TOOLBOX WINDOW Objective To provide a logical grouping of a set of tools (toolset) designed to monitor the display

features of the composite situation display window. General Description The toolset within the Composite Toolbox Window consists of :

a) Map Selection Tool (‘MAP’ button) b) Zoom Tool (‘ZOOM’ button) c) Label Overlap Management Tool (‘OVERLAP ’ button) d) Filtering Tool (‘HEIGHT’ button) e) Range and Bearing Tool (‘R&B’ button) f) Labels Configuration Tool (‘LABEL ’ button)

Some of the tools are represented by medium (25 x 5 mm) toggle buttons (see SWITCHES BUTTONS ) providing access to the corresponding tool. Each tool is described individually in the following text.

The toggle button giving access to the Label Overlap Management Tool bears another button labelled ‘AUTO’, allowing direct activation of the automatic Radar Label anti-overlap (see Deconflict Labels Automatically procedure). Each of these tools can be displayed, moved and used independently of the Toolbox. (see Access Tool and Isolate Tool procedures). Thus a tool, which will be frequently employed over a period of time, can be accessed via the Toolbox, moved to a convenient location on the Composite Situation Display and left open whilst the Toolbox itself is iconified leaving only the required tool available for use. When moved out of the toolbox, the empty location of the tool shows the label of the displaced tool, and is displayed in Button2Depressed colour as a standard toggle button. The display features of the tools elements are given in the description of each tool. On initial start up, the filtering function is not active (the corresponding toggle buttons are undepressed).

Invocation On system initialisation, the CSD Toolbox Window is displayed open within the CSD Window.

Display Position Top left edge of the CSD Window. Illustration

Requirement Ref. H.BL.TOOL.01 | H.BL.TOOL.02 | H.BL.POS.01 Associated Procedures Initiates Access Tool | Replace Tool | Move window | Iconify window | De-iconify window Used by Isolate Tool Associated HMI objects LABEL OVERLAP MANAGEMENT TOOL | TRAFFIC FILTER TOO L | MAP

SELECTION TOOL | ZOOM TOOL | LABEL CONFIGURATION TO OL Particularities - Evolution Updated (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.12 Zoom Back Button HMI Object

ZOOM BACK BUTTON Objective To zoom (out) back the COMPOSITE SITUATION DISPLAY WINDOW , after

having zoomed in a part of the situation display.

General Description The Zoom Back Button is a push button. Invocation Invoked on activation of the Zoom in part procedure. Display Position Under the ZOOM TOOL, or under its icon if iconified, or under the icon of the CSD

TOOLBOX WINDOW if iconified. Illustration - Requirement Ref. H.BL.ZOOM.05 Associated Procedures Initiates Zoom Back Used by Zoom in part Associated HMI objects COMPOSITE SITUATION DISPLAY WINDOW | ZOOM TOOL Particularities - Evolution this object is not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.13 Zoom Tool HMI Object

ZOOM TOOL Objective To change the radar display range, to store a particular zoom range, and to offset

the situation display window centre. General Description The Zoom Tool consists of a conventional slider bar, with the currently selected

zoom value in nautical miles, corresponding to the x aperture of the display, indicated in TextUnselected colour below the slider. Value increases from the left to the right. The minimum range is 50 NM, the maximum range is 600 NM (minimum and maximum range are defined at local level). Additional features provide access to previously stored zoom: an indicator of a stored zoom value (vertical line across the slider bar), and the stored zoom value in TextSelected colour indicated below. The number of stored zoom settings is limited by default to a maximum of three (loca parameter). The tool contains 4 push buttons (ref. description in SWITCHES BUTTONS):

• CENTRE: permits to offset the situation display centre (the recentring cursor is as described in CURSOR ).

• RESET: permits to return to the default zoom and offset values. • RINGS: permits to display / remove display rings (1nm) • SCALE: permits to display a scale that is proportional to the zoom. A fifth button might be foreseen in the future: • SAVE/DELETE (not implemented in may 2007): permits to store/delete a

particular zoom range. The legend on this push button reads ‘DELETE’ in TextSelected colour if the slider cursor is positioned on a stored zoom value. Otherwise, the legend reads ‘SAVE’ in TextUnselected colour. If the maximum number of stored settings is reached, the ‘SAVE’ legend turns to StoredValue colour.

The default setting of the tool is such that the view is centred on the sector manned on the position, and the zoom is adapted to show its limits.

Invocation Available as an open tool in the CSD Toolbox Window. Display Position As part of the Toolbox Window. Can be moved anywhere on the CSD Window. Illustration

Requirement Ref. F.BL.ZOOM.02 | F.BL.ZOOM.04 | H.BL.ZOOM.01 | H.BL.ZOOM.02 | H.BL.ZOOM.03 | H.BL.ZOOM.04 | H.BL.ZOOM.05 | H.BL.ZOOM.06 | H.BL.ZOOM.07

Associated Procedures Initiates Isolate Tool | Replace Tool | Move window | Come on top window | Iconify

window | De-iconify window | Perform Zoom.2 | Store Zoom | Retrieve Zoom | Offset Centre.1 | Offset Centre.2 | Close window

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Used by Access Tool | Zoom Back | Zoom in part Associated HMI objects LOCAL PARAMETERS | COMPOSITE SITUATION DISPLAY WIN DOW | CSD

TOOLBOX WINDOW Particularities - Evolution The save/delete functionality is not implemented (Dec 08)

4.1.14 Map Selection Tool HMI Object

MAP SELECTION TOOL Objective To display or remove maps bearing different kinds of information. General Description The Map Selection Tool consists of a list area with text labels and switch buttons

(ref. description in SWITCHES BUTTONS) for: traffic labels, traffic symbols, airport area, taxiway, taxiway clines, runway, holding points, runway entry exit, protected areas, airspace, ILS, buidings, stands, stop bars , vehicle mask area (apron) and taxiway sectors (taxiway segments). To each text label is associated an acquisition area. When the cursor is moved over the text acquisition area, the background of the text field is shown in Button2Highlight colour (lightblue). Note: by default, the traffic label, traffic symbols, airport area, taxiways, taxiway clines, runway, buildings, stands and stop bars options are selected.

Invocation Invoked by Single Click AB on the ‘MAP’ toggle button in the CSD Display Toolbox Window (Ref. the Access Tool procedure).

Display Position Under the CSD Toolbox Window. (Then can be moved anywhere on the display window).

Illustration

Requirement Ref. F.BL.MAP.02 | H.BL.MAP.01 | H.BL.MAP.02 | H.BL.MAP.03 | F.BL.MAP.04 | H.BL.MAP.04 | H.BL.MAP.05 | H.BL.MAP.07 | F.VEH.DIS.1| H.VEH.DIS.1

Associated Procedures Used by Access Tool

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Initiates Come on top window | De-iconify window | Iconify window | Isolate Tool | Move window | Replace Tool | Close window | Set Up Runway/ Taxiway Status

Associated HMI objects LOCAL PARAMETERS | COMPOSITE SITUATION DISPLAY WIN DOW | CSD

TOOLBOX WINDOW | TAXIWAY STATUS MENU Particularities - Evolution Updated (Dec. 2008 )

4.1.15 Speed Vector Track History Tool HMI Object

SPEED VECTOR and TRACK HISTORY TOOL Objectives To select :

a) the number of radar updates (track past positions) to display for all tracks. b) a heading speed vector corresponding to n minutes of flight time on all aircraft tracks in the air.

General Description The Track History Tool contains a row of radio buttons (ref. description in SWITCHES BUTTONS) for track history function: 6 buttons labelled 0 to 5 radar updates. A value of ‘0’ corresponds to the function being ‘switched-off’. A label in TextUnselected colour identifies the function. The default setting is the ‘5’ value selected.

Invocation Should be available as a tool in the CSD Toolbox Window. Display Position As part of the CSD Toolbox Window. Can be moved out of the anywhere on the

display window. Illustration

Requirement Ref. F.BL.TRCK.05 | F.BL.VECT.02 | H.BL.TRCK.04 | H.BL.VECT.01 Associated Procedures Used by Access Tool Initiates Come on top window | De-iconify window | Iconify window | Isolate Tool | Move

window | Replace Tool | Set Speed Vectors Value | Set Track History Value | Close window

Associated HMI objects RADAR TRACK | LOCAL PARAMETERS | CSD TOOLBOX WINDO W Particularities local parameters : speed vector display values, number of trail dots to be

displayed. Evolution not implemented (Dec. 08)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.16 Sub-Views Tool HMI Object

CSD SUB-VIEWS TOOL Objectives To create additional sub-views in the Composite Situation Display Window General Description The Sub-Views Tool consists of 2 buttons (‘VIEW_1’ and ‘VIEW_2’) which allow to

create up to two additional free CSD sub-views in the composite situation display window.

Invocation Invoked by Single Click AB on the ‘VIEW’ button in the GENERAL TOOLBOX WINDOW.

Display Position Above the General Toolbox Window; then, can be moved anywhere. Illustration

Requirement Ref. F.BL.VIEW.01 | F.BL.VIEW.02 | H.BL.VIEW.01 Associated Procedures Used by Access Tool Initiates Isolate Tool | Move window | Replace Tool | Close window | Display additional

CSD sub-view | Come on top window | De-iconify window | Iconify window Associated HMI objects GENERAL TOOLBOX WINDOW | COMPOSITE SITUATION DISPL AY WINDOW Particularities - Evolution Updated in Dec 2008

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.17 Airport setup Tool HMI Object

AIRPORT SETUP TOOL Objectives To input of statuses for the taxiways and runways (open or closed) and to hide /

display the vehicles on the apron (similar to the VEHICLE MASK AREA in the MAP SELECTION TOOL ).

General Description The airport setup tool allows the controller to input the status of the taxiways and runways and mask the vehicles on the apron. For each runway end and taxiway sectors, two statuses are displayed (‘Open’ and ‘Close’). The button (‘Hide vehicles’) allows the controller to hide vehicles on the apron. Note: by default, taxiway sectors are closed, runway thersholds are open and the vehicles are hidden.

Invocation Invoked by Single Click AB on the ‘APT SETUP’ button in the GENERAL TOOLBOX WINDOW .

Display Position Above the General Toolbox Window; then, can be moved anywhere. Illustration

Requirement Ref. F.VEH.DIS.2| H.VEH.DIS.2| F.BL.APT.01 | H.BL.APT.01 Associated Procedures Used by Access Tool Initiates Isolate Tool | Open window | Move window | Close window | De-iconify

window | Iconify window | Set Up Runway/ Taxiway Status | Display vehicles | Hide vehicles

Associated HMI objects MAP SELECTION TOOL| VEHICLE RADAR LABEL | TOWED AI RCRAFT

RADAR LABEL | RUNWAY STATUS MENU | TAXIWAY STATUS M ENU Particularities Notified and selected not-notified towed aircraft are visible on the apron even when

the hide vehicles option is selected. Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.18 EFS Configuration Tool HMI Object

EFS CONFIGURATION TOOL Objective To select fields to be displayed in the EFS General Description The EFS Configuration Tool consists of a list area with text labels and switch

buttons (ref. description in SWITCHES BUTTONS) for time, aircraft type, parking stand, rules (IFR or VFR), CTOT, ATC clearances, runway, sequence number. To each text label is associated an acquisition area. When the cursor is moved over the text acquisition area, the background of the text field is shown in Button2Highlight colour (lightblue). note: traffic labels, traffic symbols, airport area, taxiways, taxiway clines, runway, buildings, stands and stop bars are default options; it should not be possible to deselect callsign field.

Invocation Invoked by Single Click AB on the ‘EFS’ toggle button in the General Toolbox Window (Ref. the Access Tool procedure).

Display Position Above the General Toolbox Window. (Then can be moved anywhere on the display window).

Illustration

Requirement Ref. F.BL.SIL.04 Associated Procedures Used by Access Tool Initiates Isolate Tool | Move window | Replace Tool | Close window | Come on top

window | De-iconify window | Iconify window Associated HMI objects GENERAL TOOLBOX WINDOW | DEP E-STRIP | ARR E-STRI P | VEHICLE E-

STRIP | TOWED AIRCRAFT E-STRIP Particularities CTOT is selected in es-strip for the CLD Controller (by default CTOT option will

not be selected for RWY and GND controllers) ; at current CTOT is set as default for RWY / GND and CLD controller

Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.19 EFS Tool HMI Object EFS TOOL

Objectives To display or remove display EFS (e-strip) Bays on the situation display. General Description The EFS Configuration Tool consists of a list area with text labels and switch

buttons (ref. description in SWITCHES BUTTONS) for each possible runway which allow a) to display / remove display possible EFS bays (‘Visible ’). b) to group / ungroup sections for each bay (‘Group ’). To each text label is associated an acquisition area. When the cursor is moved over the text acquisition area, the background of the text field is shown in Button2Highlight colour (lightblue). note: traffic labels, traffic symbols, airport area, taxiways, taxiway clines, runway, buildings, stands and stop bars are default options; it should not be possible to deselect callsign field. note: at current (May 2007), RWY26 and RWY19R are available for the RWY controller, and ‘GND’ to the GND controller.

Invocation Invoked by Single Click AB on the ‘BAYS’ button in the GENERAL TOOLBOX WINDOW.

Display Position Below the General Toolbox Window; then, can be moved anywhere on the composite situation display window.

Illustration

On the RWY position On the GND position

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Access Tool Initiates Isolate Tool | Move window | Replace Tool | Close window | Display EFS

section | Come on top window | De-iconify window | Iconify window Associated HMI objects GENERAL TOOLBOX WINDOW | DEP E-STRIP | ARR E-STRIP | GND

PENDING ARRIVALS SECTION| GND PENDING DEPARTURES SE CTION| GND PUSHBACK SECTION| GND START-UP SECTION| GND TAX I IN SECTION | GND TAXI-OUT SECTION| GND TRANSFER TO RWY SECTION| RWY FINAL SECTION| RWY HOLDING POINT SECTION| RWY P ENDING ARRIVALS SECTION| RWY PENDING DEPARTURES SECTION| R WY SECTION| RWY TAXI IN SECTION | RWY AIRBORNE SECTION

Particularities - Evolution Updated (Dec 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.20 Pending Departures Section (GND role) HMI Object

GND PENDING DEPARTURES SECTION Objectives To display pending departures EFS (GND role) General Description The GND pending departures section is opened when at least one flight is ‘n’ minutes

before its EOBT (local parameter, set to 5 minutes in ITWP prototype). The section remains opened as long as there is one EFS in this section; It is closed automatically when the conditions above no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of EFS in this section.

Invocation Automatically displayed (system-generated); can be removed from the display via the Display Position By default, the section is presented with other GND sections at the bottom of the CSD

window; then, can be moved. Illustration

examples of pending dep section (GND role)

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.21 Start-Up Section (GND role) HMI Object

GND START-UP SECTION Objectives To display start-up flights (GND role) General Description The GND start-up section is opened (empty) when at least one flight is displayed in the

GND pending departures section. The displayed flights are assumed by the GND controller. The section remains opened as long as there is one EFS in this section (start-up order) or if at least one flight is displayed in the GND pending departures section. It is closed automatically when the conditions above no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of EFS in this section.

Invocation Automatically displayed (system-generated) Display Position See GND PENDING DEPARTURES SECTION Illustration

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Particularities - Evolution Updated (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.22 Pushback Section (GND role) HMI Object

GND PUSHBACK SECTION Objectives To display pushback flights (GND role) General Description The GND pushback section is opened when at least one flight is displayed in the

GND pending departures or start-up section and if the stand is a contact stand (i.e. the aircraft will need pushback). The displayed flights are assumed by the GND controller. The section remains opened as long as there is one EFS in this section (pushback order) or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of EFS in this section.


Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window | Hide EFS Bay Associated HMI objects DEP E-STRIP Particularities - Evolution Updated (Dec. 2008) – added clearances

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.23 Taxi-out Section (GND role) HMI Object

GND TAXI-OUT SECTION Objectives To display taxi out flights (GND role) General Description

The GND taxi out section is opened when at least one flight is displayed in the Start-Up or Pushback section. The section , remains opened as long as there is one EFS in this section (aircraft taxiing out to the RWY or vehicle taxi on the apron) or if the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of EFS in this section.


example of e-strip of a departing aircraft and tow aricraft

examples of e-strip for a vehicle/tow aircraft (list of clerances depends on the initial vehicle routing)

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP | VEHICLE E-STRIP | TOWED AIRCRAFT E-STRIP Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.24 Pending Arrivals Section (GND role) HMI Object

GND PENDING ARRIVALS SECTION Objectives To display pending arrivals flights (GND role) General Description The pending arrivals section (GND controller role) is opened when at least one flight is

assumed by the RWY controller for which the GND controller is the first GND operator role concerned by the flight. The section remains opened as long as there is one EFS in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of EFS in this section.


Examples of pending arrivals (GND role)

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.25 Taxi-in Section (GND role) HMI Object

GND TAXI IN SECTION Objectives To display assumed arrivals flights (GND role) which taxi from the RWY to the parking stand. General Description

The taxi in section (GND controller role) is opened when at least one arrival flight is displayed in the pending arrivals section (GND role). The section remains opened as long as there is one EFS in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of EFS in this section.


Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Particularities - Evolution Updated (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.26 Transfer to RWY Section (GND role) HMI Object

GND TRANSFER TO RWY SECTION Objectives To display assumed departure flights (GND role) that have been transferred to the RWY

controller General Description The Transfer to RWY section (GND controller role) is opened when at least one arrival

flight is displayed in the taxi-out section (GND role). The section remains opened as long as there is one EFS in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of EFS in this section.


Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Particularities - Evolution Updated (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.27 Pending Departures Section (RWY role) HMI Object

RWY PENDING DEPARTURES SECTION Objectives To display pending departure flights (RWY role) General Description The pending departures section (RWY controller role) is opened when a departure flight –

planed to take-off from managed RWY - is given ‘pushback’ or (first) ‘taxi’ clearance. The section remains opened as long as there is one e-strip in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section.

Invocation Automatically displayed (system-generated) Display Position By default, the section is presented with other RWY sections (dec 06) at the bottom of the

CSD window; then, can be moved.

Illustration

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Particularities - Evolution Updated (September 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.28 Holding Point Section (RWY role) HMI Object

RWY HOLDING POINT SECTION Objectives To display departure flights which are assumed by the RWY controller; to display vehicles to

assume and assumed ones under the controllers responsibility. General Description

The Holding Point section (RWY controller role) is opened when a departure flight is assumed by the RWY controller. The section remains opened as long as there is one e-strip in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strips in this section.

Invocation Automatically displayed (system-generated) Display Position

See RWY PENDING DEPARTURES SECTION

Illustration

Example of holding point section for departing flights

Example of holding point section for a vehicle going to the fire station (FS) and crossing

RWY 19R

Example of holding point section for a towed aircraft

Example of holding point section for a vehicle going to the EN20, ‘stop at’ functionality is available

Requirement Ref.

H.BL.SIL.01

Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP | VEHICLE E-STRIP | TOWED AIRCRAFT E-STRIP Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.29 Pending Arrivals Section (RWY role) HMI Object

RWY PENDING ARRIVALS SECTION Objectives To display pending arrivals flights (relative to an arrival RWY) General Description The Pending Arrivals section (RWY controller role) is opened when at least one flight

is less than ‘n’ minutes before ELDT or if a Go-Around order has been issued by the RWY controller. ‘n’ is a local parameter; by default it is set to 20 minutes. The section remains opened as long as there is one e-strip in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section.


Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Particularities - Evolution Updated (July 2007); Go-Around order is not implemented (Dec. 08)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.30 Final Section (RWY role) HMI Object

RWY FINAL SECTION Objectives To display flights which are in final approach phase (RWY controller role) General Description

The Final section (RWY controller role) is opened when at least one flight is displayed in the RWY Pending Arrivals section or in the RWY Final section, or if a go-around controller has been issued by the controller. The section remains opened as long as there is one e-strip in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section.

Invocation Automatically displayed (system-generated) Display Position See RWY PENDING DEPARTURES SECTION Illustration

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Particularities - Evolution Updated (July 2007); Go-Around order is not implemented (Dec. 08)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.31 RWY Section (RWY role) HMI Object

RWY SECTION Objectives To display flights that use the runway and arrival flights that are about to use the RWY. General Description

The RWY section (RWY controller role) is opened when at least one flight is displayed in the RWY final section or if a go-around instruction has been issued by the RWY controller (arrival flights); or if at least one aircraft is displayed in the pending departures section. The section remains opened as long as there is one e-strip in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section. The RWY section has a runway divider that indicates the RWY in use and the surface wind at touchdown and stop end. Flights that are on final are placed above the divider. Flights which have received a ‘cleared to land’ instruction, ‘line up’ or ‘conditional line up’ are placed under the RWY divider.

Invocation Automatically displayed (system-generated) Display Position See RWY PENDING DEPARTURES SECTION Illustration

examples for an arriving aircraft

examples for a departuring aircraft

examples for a vehicle cleared to cross the RWY

examples for a ghost e-strip when the CROSS instruction is given by GND controller

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section | Input Cross RWY | Input Enter | Input HoldAt Initiates Move window | Hide EFS Bay Associated HMI objects ARR E-STRIP | DEP E-STRIP | VEHICLE E-STRIP | TOWED AIRCRAFT E-STRIP Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.32 RWY Taxi-In Section (RWY role) HMI Object

RWY TAXI IN SECTION Objectives To display arrival (landed) aircraft which will be transferred to the GND controller General Description

The RWY Taxi-In section (RWY controller role) is opened when at least one arrival flight is displayed in the RWY section (RWY controller role), either above or below the RWY divider. The section remains opened as long as there is one e-strip in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section.

Invocation Automatically displayed (system-generated) Display Position See RWY SECTION

Illustration

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Particularities - Evolution Updated (September 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.33 RWY Airborne Section (RWY role) HMI Object

RWY AIRBORNE SECTION Objectives To display departure airborne flights General Description

The RWY section (RWY controller role) is opened when at least one flight is displayed in the RWY section or if there is a go-around flight. The section remains opened as long as there is one e-strip in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section.

Invocation Automatically displayed (system-generated) Display Position See RWY SECTION Illustration

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP | DEP E-STRIP Used by Display EFS section Evolution Updated (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.34 Pending Departure Section (CLD role)

HMI Object CLD PENDING DEPARTURE SECTION

Objectives To display departure flights General Description

The CLD Pending Dep section is opened when at least one flight is 5minutes from its EOBT. The section remains opened as long as there is one e-strip in this section or the conditions above are fulfilled. It is closed automatically when these conditions no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section.

Invocation Automatically displayed (system-generated) Display Position By default, the section is presented with other CLD sections at the bottom of the CSD


Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Used by Display EFS section Evolution Updated (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.35 CLD Active Section (CLD role)

HMI Object CLD ACTIVE SECTION

Objectives To display departure airborne flights General Description

The CLD pending departures section is opened when at least one flight is displayed in the CLD Pending departure section. The section remains opened as long as there is one e-strip in this section; It is closed automatically when the conditions above no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section.

Invocation Automatically displayed (system-generated) Display Position By default, the section is presented with other CLD sections at the bottom of the CSD


or

Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window | Hide EFS Bay Associated HMI objects DEP E-STRIP Used by Display EFS section Evolution Updated (July 07)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.36 CLD Start Up Section (CLD role)

HMI Object CLD START UP SECTION

Objectives To display departure airborne flights General Description

The GND start-up section is opened (empty) when at least one flight is displayed in the CLD Active section. The displayed flights are assumed by the GND controller. The section remains opened as long as there is one e-strip in this section (start order) or if at least one flight is displayed in the CLD pending departures section. It is closed automatically when the conditions above no longer exist. It can be moved but neither iconified nor closed by the controller. The vertical size of the section is automatically adapted to the number of e-strip in this section.

Invocation Automatically displayed (system-generated). Display Position By default, the section is presented with other CLD sections at the bottom of the CSD


Requirement Ref. H.BL.SIL.01 Associated Procedures Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Used by Display EFS section Evolution Updated (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.37 Clock Window HMI Object

CLOCK WINDOW Objective To display time (UTC) General Description The CLOCK WINDOW displays the UTC time Invocation System-generated. Display Position Top right corner of the CSD Window; then can be moved anywhere on the CSD

Window. Illustration

clock window (unselected) clock window (selected)

Requirement Ref. F.BL.TIME.01 | H.BL.TIME.01 Associated Procedures Initiates Move window Used by Display Universal Time Associated HMI objects - Particularities - Evolution Updated (November 2007)

4.1.38 Weather Information Window HMI Object

MET INFORMATION WINDOW Objectives To provide the controller with information about MET information General Description

The MET window contains weather information and can be displayed either in normal or extended format depending on controller needs. In normal format, the MET information window displays: a) surface wind direction (Touch Down) and strength in graphical (compass) and text, b) QNH (in hectopascals or millibars (same value)), c) ATIS code (letter designation) and issued time d) Temperature and dew point in degrees celsius e) Cross winds (X-wind) and tail winds in knots. The access to extended MET information window is obtained via re-scale function. The additional MET information includes: a) surface wind (Touch Down and Stop End) , b) visiblity, c) cloud ceiling, d) QNH and QFE (hectopascals and inches), e) RVR conditions and f) specific MET report Updates of values (e.g. ATIS letter designation, QNH, Temperatures etc.) will be displayed in ‘warning’ colour (yellow).

Invocation Invoked by Single Click AB on the ‘MET’ button in the General Toolbox Window Display Position Under the General Toolbox Window (top left corner); then, can be moved anywhere on

the composite situation display window.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Illustration

normal (i.e. reduced) MET Information window

extended MET Information window note: the circle represents a compass so there should be the normal markings The blue and pink line shall be curved inside the circle and represents the wind over the last 10 minutes (blue) and 2 minutes (pink)

Requirement Ref. H.BL.WEA.01 | H.BL.WEA.02 Associated Procedures Used by Open window Initiates Move window | Close window | Re-scale window | Come on top window Associated HMI objects GENERAL TOOLBOX WINDOW Particularities - Evolution Updated (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.39 NAVAIDS Information Window HMI Object

NAVAIDS INFORMATION WINDOW Objectives To provide the controller with information about NAVAIDS serviceability. General Description The Navaids window contains serviceability information about radio navigation

aids systems for aircraft: a) VHF Omni-directional Radio range (VOR) b) Distance Measuring Equipment (DME) c) Non Directional Beacon (NDB), and for each runway (local parameter) d) Glide Path (GP) e) Localizer (LLZ), and f) Precision Approach Path Indicator (PAPI)

Invocation Invoked by Single Click AB on the ‘EQUIP’ button in the General Toolbox Window (Ref. the Access Tool procedure), or is displayed automatically when a transition (when failure, or when recovery from failure) is detected by the system (note: this functionality (on/off) might be accessed in the future via the preferences setting window).

Display Position Above the General Toolbox Window. (Then can be moved anywhere on the composite situation display window)

Illustration

Requirement Ref. H.SN.NAV.01 | H.SN.NAV.02 Associated Procedures Used by Open window Initiates Move window | Close window | Erreur ! Source du renvoi introuvable. | Come

on top window Associated HMI objects GENERAL TOOLBOX WINDOW Particularities - Evolution Updated (August 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.40 Composite Situation Display (CSD) Window HMI Object

COMPOSITE SITUATION DISPLAY WINDOW Objective To provide a display of the composite ground / air situation General Description The Composite Situation Display contains the background ATC map containing:

a) representation of the airspace, sectors and restricted spaces, waypoints/beacons, airfields, representation of air routes b) representation of the airport: taxiways, runways, terminals and other airport buildings, aprons and gates, stop bars, holding points, protected areas. The display of these elements is toggled by using the appropriate options of the MAP SELECTION TOOL. Other objects are displayed on this background ATC map in relation with the Composite Situation Display: a) the toolset provided within the CSD TOOLBOX WINDOW and any of its element tools which the controller chooses to leave available independently of the toolbox:

• The symbology representing the traffic (radar tracks),

• Radar labels (aircraft and vehicles) providing flight data information for each individual traffic

• Secondary windows and information displays which appear within the confines of the Composite Situation Display (e.g. e-strips, menus, Met window, etc.).

Invocation On system initialisation the Composite Situation Display is open on the display. Display Position Full screen display Illustration

Requirement Ref. H.BL.ZOOM.01 | H.BL.MAP.01 Associated Procedures Initiates Move window | Offset Centre.1 | Offset Centre.2 | Re-scale window | Zoom in part |

Slider scroll window | Perform Zoom.1 | Re-size window | Re-scale window Used by Access Configuration Set-Up | Save Configuration Set-Up | Perform Zoom.2 | Store

Zoom | Zoom Back | Delete Zoom | Retrieve Zoom Associated HMI objects

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


RADAR LABEL | LOCAL PARAMETERS | RADAR TRACK | DEP E-STRIP | ARR E-STRIP | ZOOM BACK BUTTON | ZOOM TOOL | PREFERENCES SETTING WINDOW | MAP SELECTION TOOL

Particularities The Composite Situation Display Window cannot be closed. Evolution Updated (Dec. 2008)

4.1.41 Radar Track HMI Object

RADAR TRACK Objective To provide graphical representation of traffic position. General Description The radar track consists of:

� A position symbol � The size of aircraft position is 6 pixels of diameter for light aircraft category, b) 8 pixels of diameter for medium aircraft category, 10 pixels of diameter for heavy aircraft category. � track history dots (trail dots): 0 to 6 dots of equal size of 2 pixels of diameter, each dot representing a position from a previous radar update, � a speed vector (aircraft in the air): a 1 pixel thick solid line of length corresponding to 0 to 6 minutes of flight time. � Planned route The speed vector length and the number of displayed track history dots are selectable from within the SPEED VECTOR and TRACK HISTORY TOOL

Other graphical attributes can be added to the radar track: � · intra-sector warning: a 1 pixel thick ring of 1 cm diameter, in Warning colour, drawn around the aircraft position symbol, � · measure of distance: a 1 pixel thick circle of 5 NM radius, in Warning colour, drawn around the aircraft position symbol, � · interaction warning: the position symbol is displayed in Interaction colour (bright blue).

The radar track display shall never be obscured by other information.

The colours of the track are the following:

position symbol and history dots: � unselected: TrackUnselected colour (black) � selected: TrackSelected colour (white)

speed vector: � global display: SpeedVector colour (black)

Invocation Displayed when the traffic is present on the situation display. Display Position At traffic co-ordinates provided by the Surveillance System.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Illustration

arrival track (unselected) arrival track (selected)

departure track (unselected) departure track (selected)

example for displaying planned route

Requirement Ref. H.BL.TRCK.01 | H.BL.TRCK.02 | H.BL.TRCK.03 | H.BL.TRCK.04 |

H.ROUTE.DIS.1 Associated Procedures Initiates Select Traffic | Deselect Traffic Used by Display Traffic Representation | Set Leader Direction | Set Leader Length |

Deconflict Labels Manually | Deconflict Labels Automatically | Remove Traffic Representation | Resume Label Position | Set Fixed Reference | Set Track as a Reference | Set Speed Vectors Value | Set Track History Value | Display Planned Route

Associated HMI objects Particularities The planned route of a vehicle can only be displayed if it has been assumed.

The initally planned route of an aircraft can only be displayed if it is known by the system.


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.42 Radar Label HMI Object

RADAR LABEL Objective To provide the minimum updated flight information needed by the controller,

directly attached to the air track of any traffic present on the situation display. These are: • Traffic information, • Planning state, • Indication of the necessity of controller action To provide the possibility to easily access additional information concerning the aircraft in the air on controller request.

General Description The radar label is composed of a leader line and a block of aircraft data (label)

a) Leader line The Leader line is a 1 pixel thick solid line connecting the centre of the Position symbol of the aircraft track to the centre of the label. The maximum length of the Leader line depends on the selected label position monitoring options (Ref. the section 'Manage the radar Label position'). In any case, the minimum length of the Leader line is 5 mm, ensuring that the Position symbol and the label do not overlap. The part of the Leader line passing through the label is hidden, and a gap of approximately ½ of a character space is left between the leader line and the label text to avoid impairment of label legibility. When the aircraft is selected, the leader line thickness is increased to 3 pixels

The label is displayed in different formats depending on the planning state of the traffic and on the controller’s intention to interact with it.

b) Label format and content

1) The Minimum format is the normal display form of the label (unselected).

Data presented between brackets { } is optional and is displayed in the Minimum label only if selected from the LABEL CONFIGURATION TOOL section (Configure radar labels content ):

arrival aircraft line 0: CALLSIGN {Stand} departure aircraft line 0: CALLSIGN {Stand} or {Clearance limit}

note 1: by default , a) Callsign and Stand are displayed in the minimum arrival label. b) Callsign and Stand (or Clearance limit) are displayed in the minimum departure label.

note 2: for a departure aircraft, the stand is shown on the radar label until the first ‘taxi’ clearance is input by the controller. Then, the ‘clearance limit’ replaces the stand in the radar label.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


General Description

2) The Selected format is displayed when the controller selects the label by moving the cursor pointer on any of the representations of the traffic. · Data presented between brackets { } is optional and is displayed in the Selected

label only if selected from the LABEL CONFIGURATION TOOL section (Configure radar labels content ).

arrival aircraft line 1 : CALLSIGN {Stand} line 2: {Altitude} {True Air Speed} line 3: {Aircraft type} {/} {Wake vortex category} {RWY} {sequence number}

departure aircraft line 1 : CALLSIGN {Stand} or {Clearance limit} (see note 2 above) line 2: {Altitude} {True Air Speed} {CTOT} line 3: {Aircraft type} {/} {Wake vortex category} {RWY}{-}{sequence number} {SID} note: radar labels are displayed if traffic is present on the situation display. Common fields to departures and arrivals: a) Callsign: up to 7 characters (ref. doc. ICAO 4444), e.g. BAW429; interactive field, the callsign menu displays possible controller clearances. b) Stand: stand identification, e.g. 67, F32L, G142; interactive field which allows the controller to change stand (menu). c) Altitude: altitude format is ‘Annn’ (‘A’ for altitude, nnn in feet/100); e.g. A070 stands for an altitude of 7000 (070x100) feet. d) True Air Speed (TAS): format is ‘Tnnn’ (‘T’ for True Air Speed, nnn in knots), e.g. T123 e) Aircraft type: 2 up to 4 characters (ref. doc. ICAO 8643). f) Wake vortex category: one of the following letters (ref. doc. ICAO 4444, §4.9.1.1); ‘H’ (Heavy): all aircraft types of 136,000 kg or more; ‘M’: aircraft types less than 136,000 kg but more than 7,000 kg; ‘L’: aircraft types of 7,000 kg or less. g) RWY: runway field, e.g. 01L, 19R, 26, 08 etc. h) Sequence number: runway sequence number (from 1 to n), combining arrivals and departures that may use the runway. Specific fields for departures: a) CTOT: format is ‘Cnnii’; ‘C’ stands for CTOT, nn for hours (00 to 23), ii for minutes (00 to 59). CTOT is only displayed for regulated flights. b) SID: Standard Instrument Departure;

Note: Data link identifier is displayed around the callsign. Display Position Attached to the radar track with the leader line according to the selected label

position monitoring options

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Illustrations (default settings)

minimum air label – data link equipped aircraft (not concerned state)

minimum air label minimum air label (not concerned state) (pending state / no value)

minimum air label – data link equipped aircraft

(assumed state / no value)

minimum air label minimum air label (pending state / pending in) (assumed state / no value)

minimum air label (assumed state / assumed out)

minimum departure label minimum departure label (not concerned state) (pending state / no value)

minimum departure label minimum departure label (pending state / pending in) (assumed state / no value)

minimum departure label (assumed state / assumed out)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft



selected air label selected air label (not concerned state) (pending state / no value)

selected air label selected air label (pending state / pending in) (assumed state / no value)

selected air label selected air label (assumed state / assumed out) (assumed state / no value)

selected departure label – data link equipped aircraft (pending state / no value)

selected departure label selected departure label (not concerned) (pending state / no value)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.43 Vehicle Radar Label HMI Object

VEHICLE RADAR LABEL Objective To provide the minimum updated vehicle information needed by the controller,

directly attached to the traffic on the manoeuvring area present on the situation display. These are: • Traffic information, • Planning state, • Indication of the necessity of controller’s action To provide the possibility to easily access additional information concerning the vehicle on the ground on controller request.

General Description The radar label is composed of a leader line and a block of vehicle data (label)

a) Leader line The Leader line is a 1 pixel thick solid line connecting the centre of the Position symbol of the vehicle track to the centre of the label. The maximum length of the Leader line depends on the selected label position monitoring options (Ref. the section 'Manage the radar Label position'). In any case, the minimum length of the Leader line is 5 mm, ensuring that the Position symbol and the label do not overlap. The part of the Leader line passing through the label is hidden, and a gap of approximately half of a character space is left between the leader line and the label text to avoid impairment of label legibility. When the vehicle is selected, the leader line thickness is increased to 3 pixels



1) The Minimum format is the normal display form of the label (unselected).


vehicle line 0: CALLSIGN {}

note 1: by default a vehicle Callsign is displayed in the minimum vehicle radar label. If vehicle is assumed by a controller, the operational role is displayed (RWY or GND) line 0: CALLSIGN Operational role

note 2: If “Cross” or “Enter” clearance is given, the line 1 contains the sign for given clearance.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


General Description



Vehicle line 1 : CALLSIGN Operational role line 2: {Type} {Destination} line 3: Clearance note: vehicle radar labels are displayed if traffic is present on the situation display.

Display Position Attached to the radar track with the leader line according to the selected label position monitoring options


minimum vehicle label minimum vehicle label (not concerned state) (not concerned state/ no value)

minimum vehicle label minimum vehicle label (pending state / pending in) (assumed state / clearance)

minimum vehicle label minimum vehicle label (assumed state / assumed out) (assumed state / no value)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.44 Towed Aircraft Radar Label HMI Object

TOWED AIRCRAFT RADAR LABEL Objective To provide the minimum updated towed aircraft information needed by the

controller, directly attached to the traffic on the manoeuvring area present on the situation display. These are: • Traffic information, • Planning state, • Indication of the necessity of controller’s action To provide the possibility to easily access additional information concerning the Towed aircraft on the ground on controller request.

General Description The radar label is composed of a leader line and a block of towed aircraft data (label)

a) Leader line The Leader line is a 1 pixel thick solid line connecting the centre of the Position symbol of the towed aircraft track to the centre of the label. The maximum length of the Leader line depends on the selected label position monitoring options (Ref. the section 'Manage the radar Label position'). In any case, the minimum length of the Leader line is 5 mm, ensuring that the Position symbol and the label do not overlap. The part of the Leader line passing through the label is hidden, and a gap of approximately ½ of a character space is left between the leader line and the label text to avoid impairment of label legibility. When the TUG (towed aircraft) is selected, the leader line thickness is increased to 3 pixels .



1) The Minimum format is the normal display form of the label (unselected). The set up of towed aircraft label is enabled as for vehicles.


Vehicle (towed aircraft) line 0: CALLSIGN {}

note 1: by default a towed aircraft Callsign is displayed in the minimum towed aircraft radar label. If a/c is assumed by a controller, the operational role is displayed (RWY or GND) line 0: CALLSIGN Operational role

note 2: If “Cross” or “Enter” clearance is given, the line 1 contains the sign for given clearance.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


General Description



Towed aircraft line 1 : CALLSIGN Operational role line 2: {Type} {Destination} line 3: Clearance (HOLD, CROSS, ENTER) note 3: towed aircraft radar labels are displayed if traffic is present on the situation display. Two type of towed aircraft are implemented: notified and not notified movements. Radar label for notified towed aircraft is visible on the apron. Not notified aircraft is hiden by the vehicle mask area.

Display Position Attached to the radar track with the leader line according to the selected label position monitoring options


minimum towed a/c label minimum towed a/c label (not concerned state) (not concerned state/ no value)

minimum towed a/c label minimum towed a/c label (pending state / pending in) (assumed state / clearance)

minimum towed a/c label minimum towed a/c label (assumed state / assumed out) (assumed state / no value)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.45 Label Configuration Tool HMI Object

LABEL CONFIGURATION TOOL Objective To display / remove supplementary data in either the minimum or extended format

of all radar labels. General Description The Label Configuration Tool consists of a list area with text labels and switch

buttons. The switch buttons are displayed in two columns labelled ‘Min+Sel’ and ‘Sel’. Each of the switch buttons in the ‘Min+Sel’ column displays or removes the corresponding data from both the Minimum and Selected formats of all the labels: this means that checking (unchecking) a switch button in the ‘Min+Sel’ column also checks (unchecks) the corresponding switch button in the 'Sel' column. Each of the switch buttons in the ‘Sel’ column displays the corresponding data in the Selected format of all the labels, or removes them from both the Minimum and Selected formats of all the labels (data cannot in the same time be displayed in the Minimum format and not be displayed in the Extended format). To each text label is associated a square acquisition area. When the cursor is moved over the text acquisition area, the background of the text field is shown in Button2Highlight colour. The default setting of the tool is – Callsign is a mandatory field in the radar label (i.e. cannot be unchecked): a) minimum label: all options unchecked, except ‘stand’ (arrival aircraft) and stand / clerance limit and CTOT for departure aircraft. For vehicle, vehicle type and ground route may be selected / deselected. b) extended label: all options checked for departure and arrival aircraft, i.e.:

• Arrival aircraft: stand, altitude, true air speed, aircraft type / wake vortex category, runway and sequence number.

• Departure aircraft: stand or clearance limit, altitude, true air speed, CTOT, aircraft type / wake vortex category, runway, sequence number, SID.

• Vehicle: type and ground route

Invocation Invoked by Single Click AB on the ‘LABEL’ toggle button in the General Toolbox Window (ref. the Access Tool procedure).

Display Position Under the CSD TOOLBOX WINDOW ; Then can be moved anywhere on Display Window.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.46 Label Overlap Management Tool HMI Object

LABEL OVERLAP MANAGEMENT TOOL Objective To manage the radar labels' positions by:

• Activating the radar label automatic anti-overlap function, • Providing manual control of the position of the radar labels, with the ability to

set the orientation and Leader line length of all labels relative to a frame of reference.

General Description The window content is redrawn to different forms depending on the selected options. · Region 1 consists of the ‘AUTO’ toggle button for controlling the shift between

the Automatic and the Manual modes (not implemented, may 2007) · Region 2 consists of a button “RESET ALL” . Region 3 consists of 3 radio buttons for selecting the length of the Leader line

between an aircraft symbol and its label: S, M and L, organised from left to right, indicate short, medium and long Leader lines respectively (the values of S, M, L are parameters, with default of 1, 2, 3 cm respectively).

. Region 4 consists of 4 radio buttons for selecting the label direction relative to the aircraft track: abeam left, abeam right, 135 degrees from the route, 225 degrees from the route.

When the tool is accessed for the first time, the default options are: auto anti-overlap function switched OFF (AUTO toggle button un-depressed), 'the leader length is set to ‘L’, and the label position is set to 45 degrees from the aircraft track. At each subsequent use of the tool, the last selected options are presented.

Invocation Invoked by Single Click AB on the ‘OVERLAP’ toggle button in the General Toolbox Window.

Display Position Under the General Toolbox Window. (then can be moved anywhere) Illustration

Label Overlap Management Tool (July 2007)

Requirement Ref. H.BL.POS.01 | H.BL.POS.02 | H.BL.POS.03 | H.BL.POS.04 | H.BL.POS.05 | H.BL.POS.06 | H.BL.POS.07 | H.BL.POS.08

Associated Procedures Initiates Move window | Come on top window | Iconif y window | De-iconify window |

Isolate Tool | Replace Tool| Set Leader Length | Se t Leader Direction | Resume Label Position | Set Track as a Reference | Set Fixed Reference | Deconflict Labels Automatically | Deconflict Labels Manually | Close window

Used by Access Tool Associated HMI objects Particularities - Evolution Object is partially implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.47 Range and bearing tracker link

HMI Object RANGE and BEARING TRACKER LINK

Objective To provide readout of bearing, distance and time as measured from one point to another. To link two points, one or both of which can be dynamic (an aircraft and a fixed point, or two aircraft), and to monitor the change in relative heading, distance and time over time.

General Description The sighting cursor is a 'X' in RangeBearing colour. The point of origin is a 'x' of 5 mm in RangeBearing colour. The elastic vector obtained by activation of the Range_Bearing or the Tracker link, is a 1 pixel thick dashed line in RangeBearing colour. The readout of bearing and distance is displayed in RangeBearing colour: yyy/xx. · yyy: absolute heading in degrees (3 digits, to the nearest degree). · xxx.x: distance in nautical miles (precision of one decimal).

The ETO for the range and bearing or the tracker link created between an aircraft and the cursor or a fixed point is displayed in RangeBearing colour: HH:MM. The ‘time to go format is ‘MM mn’.

Invocation Invoked by Single Click AB in the CSD Window Display Position On the Composite Situation Display Window (airspace). Illustration - Requirement Ref. F.BL.RB.02 | F.BL.RB.03 | H.BL.RB.01 | H.BL.RB.03 | H.BL.RB.04 | H.BL.RB.05 |

H.BL.RB.06 | H.BL.RB.07 | H.BL.RB.09 Associated Procedures Initiates Cancel Range and Bearing Track Used by Create Range and Bearing Track | Express time to go to airspace point |

Obtain range and bearing information | Cancel Range and Bearing function Associated HMI objects RADAR TRACK | LOCAL PARAMETERS | COMPOSITE SITUATI ON DISPLAY

WINDOW | CSD TOOLBOX WINDOW | RANGE AND BEARING TOO L Particularities The Range and Bearing information should be included in the global information anti-

overlap policy. Evolution Not implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.48 Extended radar label

HMI Object EXTENDED RADAR LABEL

Objective To provide, in a fixed format, available additional data concerning an aircraft. The Extended Radar Label can be displayed: � in a quick-look mode at the location of the radar label, and/or � in a fixed mode in the extended radar label window.

General Description

The information presented in the extended radar label form is the information presented in the DEP E-STRIPand ARR E-STRIP), i.e. a) Departure aircraft

Time1 C/S TYPE/VW Stand / Clr.Lmt SID or V CTOT CLE ARANCE RWY SeQ N° M Time2 Airline SSR ADES QNH RMKS

b) Arrival aircraft Time1 C/S TYPE/VW Stand (-Hold) I or V CLEARANCE R WY SeQ N° M Time2 Airline SSR ADES QNH RMKS

Invocation Invoked by Single Click or Press and Hold IB on the ‘callsign” field within the radar label or anywhere else that this field is displayed.

Display Position

� in a ‘Fixed’ mode: in the Extended Radar Label Window. � in a ‘Quick look’ mode: at the location of the radar Label, so that the callsign is maintained at the same position.

Illustration

Example of extended label for an arrival flight eqquiped for data link com

Example of extended radar arrival label (aircraft involved in an alarm)

Example of extended radar departure label

Example of extended radar departure label for an aircraft involved in an information alert)

Example of extended label for a departure flight eqquiped for data link com

Req. Ref. H.BL.TRAF.04 | F.BL.LBL.03 | F.BL.TRAF.02 | F.BL.SIL.03 | H.BL.SEL.03 F.BL.APT.01 |

H.BL.SEL.04 | H.BL.WAR.01 | H.DL.IDF.1 Associated Procedures Used by Display Extended Label | Display Extended Label (Quick Look) Associated HMI objects EXTENDED RADAR LABEL WINDOW Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.49 Extended radar label window HMI Object

EXTENDED RADAR LABEL WINDOW Objective To display the EXTENDED RADAR LABEL content of an aircraft or vehicle General Description The Extended Radar Label Window displays the Extended Radar Label content of

an aircraft or vehicle. The window size is adapted to the Extended Radar Label content.

Invocation Invoked by Single Click IB on the ‘callsign’ field within the radar label or anywhere else that this field is displayed.

Display Position At the radar label position. Illustration

example of extended radar arrival label window

example of extended radar departure label window

Requirement Ref. H.BL.TRAF.04 | F.BL.LBL.03 | F.BL.TRAF.02 | F.BL.SIL.03 | H.BL.SEL.03 F.BL.APT.01 | H.BL.SEL.04

Associated Procedures Initiates Close window | Come on top window | Move window Used by Open window | Display Extended Label Associated HMI objects Particularities - Evolution This window is not any more in the ITWP. Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.50 RWY conflict alert track HMI Object

RWY CONFLICT ALERT TRACK Objective To indicate to the controller a potential runway conflict alert (step 1 or step 2 alert)

is likely to occur. General Description The trail dots and the position symbol of traffic involved in the runway conflict are

presented in:

� Information alert colour in case of Runway Conflict Alert (Step 1) � Alarm colour in case of Runway Conflict Alert (Step 2) The Runway Conflict Alert information remains until the conflict is ended.

Invocation System generated. Display Position At the position of involved traffic Illustration - Requirement Ref. H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4 Associated Procedures Used by Display Runway Conflict (step 1 alert) | Display Runway Conflict (step 2 alert)

| End Runway Conflict Alert Associated HMI objects RADAR TRACK Particularities - Evolution not implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.51 RWY conflict alert label HMI Object

RWY CONFLICT ALERT LABEL Objective To indicate to the controller that a potential runway conflict alert (step 1 or step 2

alert) is likely to occur. General Description The callsign of the traffic involved in the runway conflict is highlighted with the

following colours: � Information alert colour in case of Runway Conflict Alert (Step 1) � Alarm colour in case of Runway Conflict Alert (Step 2)

The text of the callsign is coloured in text colour (i.e. black) This presentation is applicable to all the occurrences of the callsign, anywhere on the display. The Runway Conflict alert information remains until the conflict on the runway has been resolved.

Invocation System generated; displayed automatically by the system when a runway conflict alert is detected.

Display Position Callsigns of the involved traffic Illustration

radar label - information alert radar label - infromation alert runway conflict alert / step 1 runway conflict alert / step 1 (selected label) (minimum label)

radar label - Alarm radar label - Alarm runway conflict alert / step 2 runway conflict alert / step 2 (selected label) (minimum label)

Requirement Ref. H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4 Associated Procedures Used by Display Runway Conflict (step 1 alert) | Display Runway Conflict (step 2 alert)

| End Runway Conflict Alert | Acknowledge alert Associated HMI objects RADAR LABEL | EXTENDED RADAR LABEL | VEHICLE RADAR LABEL |

TOWED AIRCRAFT RADAR LABEL for the ALARM the alert is displayed in the object ALERT RADAR TRACK


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.52 Alert in the radar label HMI Object

ALERT IN LABEL Objective To indicate to the controller the detection of:

- inconsistent clerances different from runway conflict detection (conflicting ATC instructions / procedures)

- non conformance to ATC clearances

- Controller input errors with respect to airport layout (restricted and closed areas)

General Description The callsign of the traffic involved in the detected situation is highlighted with the following colours: � Information alert colour (yellow) when detected (Step 1). � Alarm colour (red) when detected (Step 2).

The text of the callsign is coloured in text colour (i.e. black for information alert and white for alarm) This presentation is applicable to all the occurrences of the callsign, anywhere on the display (radar label and e-strip). The information alert remains until the situation has been resolved or the controller has acknowledged the alert; the alarm remains until the situation has been resolved.

Invocation System generated; displayed automatically by the system when an alert is detected. Display Position Callsigns of the involved traffic Illustration

radar label - information radar label - information no taxi clearance / step 1 route deviation alert / step 1 (selected label) (minimum label)

radar label (arr ) - Alarm radar label (arr) – Alarm LND/LND alert / step 2 stationary aircraft in RPA alert / step 2 (selected label) (minimum label)

Requirement Ref. H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4 | F.SN.CLRS.1| H.SN.CLRS.1| H.SN.CLRS.2| F.SN.PROC.2| H.SN.PROC.4| H.SN.PROC.5 | H.SN.PROC.6 | H.SN.PROC.8 | H.SN.PROC.9 | F.SN.PROC.8| H.SN.PROC.11| H.SN.PROC.2 | H.SN.PROC.1| H.SN.PROC.3 | F.SN.PROC.1| H.SN.AREA.5 | H.SN.AREA.6 | F.SN.AREA.8

Associated Procedures

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.53 Alert in the e-strip HMI Object

ALERT IN E-STRIP Objective To indicate to the controller the detection of the following categories of alerts:

- PROC Alert: conflicting ATC instructions / procedures

- CLRS Alert: non conformance to ATC clerances

- AREA Alert: infringement of restricted / closed aeas

General Description The callsign of the traffic involved in the detected situation is highlighted with the following colours: � Information alert colour (yellow) when detected (Step 1): � Alarm colour (red) when detected (Step 2):

The text of the callsign in the e-strip is coloured in text colour (i.e. black for information alert and white for alarm) The information alert in the e-strip remains until the potential hazardous situation has been resolved or until the controller has acknowledged the alert in the alert window. The display of an alarm remains until the potential hazardous situation has been resolved.

Invocation System generated; displayed automatically by the system when an alert is detected. Display Position Callsigns of the involved traffic in the e-strip. Illustration

Example of ALARM (step 2 alert) displayed in the e-strip

Example of ALARM (step 2 alert) displayed in the e-strip

Example of INFORMATION (step 1 alert) displayed in the e-strip

Requirement Ref. H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4 | F.SN.CLRS.1|

H.SN.CLRS.2 | H.SN.CLRS.3| F.SN.PROC.2| H.SN.PROC.4| H.SN.PROC.5 | H.SN.PROC.6 | H.SN.PROC.8 | H.SN.PROC.9 | F.SN.PROC.8 | H.SN.PROC.11 | F.SN.PROC.1 | H.SN.AREA.5 | H.SN.AREA.6 | F.SN.AREA .8

Associated Procedures Used by Display Runway Conflict (step 1 alert) | Display Runway Conflict (step 2 alert) |

End Runway Conflict Alert | Display Excessive Taxi Speed | Display Non Conformance to ATC Instructions | Display ATCO Input Error w.r.t. Airport Layout | Display Conflicting ATC Clearances Input

Associated HMI objects CLD E-STRIP | DEP E-STRIP | TOWED AIRCRAFT E-STRIP | VEHICLE E-STRIP|

ARR E-STRIP Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.54 Alert Window HMI Object

ALERT WINDOW Objective To display alert messages produced by the safety support functions. General Description

The ALERT WINDOW displays a list of alert messages, each line correspond to an alert message.

Invocation System-generated Every new message is added on the top of the list in the Alert Window. The priority of the alerts in the alert window is defined as follows: - alarms (CONFLICT; RWY INCURSION; NO TOF CLR; NO LND CLR; NO CROSS CLR; LUP/LND; TOF/LUP; TOF/LUP; CROSS/LND; CROSS/TOF; ENTER/LND; ENTER/TOF; LND/LND; TOF/TOF; STATIONARY IN RPA; etc.) and information (CONFLICT; ROUTE DEV; RWY TYPE; HIGH SPEED; NO PUSH CLR; NO TAXI CLR; RWY CLOSED; TWY CLOSED…) The Alert Window size is automatically adapted to its content; it is dynamically resized in length (number of lines) in accordance with the number of incoming messages. An empty Alert Window is automatically reduced to its minimum size (header).

Display Position

Top of the CSD Window; can not be moved anywhere on the CSD Window.

Illustration

Example of alert window with the message of an a/c on runway protection area without clearance and an a/c is cleared to land on the same runway while an a/c is cleared to take-off

Example of an alarm message for an a/c which lines up without clearance / alert Step 2

Example for aircraft taking-off without take-off clearance , alert step 1 (Information)

Example for a route deviation , alert step 1 (Information)

Requirement Ref.

H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4 | H.SN.CLRS.1 | H.SN.CLRS.2| F.SN.PROC.2| H.SN.PROC.4 |H.SN.PROC.5 |H.SN.PROC.6 | H.SN.PROC.8 | H.SN.PROC.9 | F.SN.PROC.8| H.SN.PROC.11| H.SN.PROC.2 | H.SN.PROC.1 | F.SN.PROC.1 | H.SN.AREA.5 | H.SN.AREA.6 | F.SN.AREA.8

Associated Procedures Initiates Come on top window | Move window Used by Display Runway Conflict (step 1 alert) | Display Runway Conflict (step 2 alert) | End

Runway Conflict Alert |Display ATCO Input Error w.r.t. Airport Layout | Display Excessive Taxi Speed | Display Non Conformance to ATC Instructions | Acknowledge alert

Associated HMI objects RUNWAY CONFLICT ALERT MESSAGE | NON CONFORMANCE TO ATC CLEARANCE

ALERT MESSAGE | CONFLICTING ATC CLEARANCES ALERT ME SSAGE | ATCO INPUT ERROR w.r.t. AIRPORT LAYOUT ALERT MESSAGE | RUNWAY INCURSION MESSAGE |

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft



4.1.55 Alert displayed on the radar track HMI Object

ALERT RADAR TRACK Objective To indicate to the controller the detection of the following categories of alerts:

- PROC Alert: conflicting ATC instructions / procedures

- CLRS Alert: non conformance to ATC clerances

- AREA Alert: infringement of restricted / closed aeas

General Description

The red circle around the radar track of the traffic involved in the detected situation is highlighted with the Alarm colour (red) when detected alert Step 2:

Invocation System generated; displayed automatically by the system when an alert step 2 is detected. Display Position

Radar track of the involved traffic

Illustration

Example of ALARM (step 2 alert) displayed round the radar track

Requirement Ref.

H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4 | F.SN.CLRS.1| H.SN.CLRS.1 | H.SN.CLRS.2| F.SN.PROC.2| H.SN.PROC.4| H.SN.PROC.5 | H.SN.PROC.6 | H.SN.PROC.8 | H.SN.PROC.9 | F.SN.PROC.8 | H.SN.PROC.11 | F.SN.PROC.1 | H.SN.AREA.5 | H.SN.AREA.6 | F.SN.AREA.8

Associated Procedures Used by Display Runway Conflict (step 1 alert) | Display Runway Conflict (step 2 alert) | End

Runway Conflict Alert | Display Excessive Taxi Speed | Display Non Conformance to ATC Instructions | Display ATCO Input Error w.r.t. Airport Layout | Display Conflicting ATC Clearances Input

Associated HMI objects RADAR TRACK Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.56 Runway Conflict Alert Message HMI Object

RUNWAY CONFLICT ALERT MESSAGE Objective To provide to the controller information on the potential runway conflict alert. General Description

The Runway Conflict Alert is displayed in the ALERT WINDOW ; the alert description is composed of a RWY number in black on the grey background and the traffic involved (callsigns) highlighted as follows: � Information alert (runway conflict alert step 1 message) or � Alarm (runway conflict alert step 2 message)

The runway conflict alert description line remains in the ALERT WINDOW until the alert ends. Invocation System generated when a runway conflict alert is detected Display Position

In the ALERT WINDOW

Illustration

example of runway conflict alert message (alarm) *

example of runway conflict alert message (information)

Requirement Ref.

H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4

Associated Procedures Initiates Come on top window | Move window Used by Display Runway Conflict (step 1 alert) | Display Runway Conflict (step 2 alert) | End

Runway Conflict Alert Associated HMI objects ALERT WINDOW Particularities

-

Evolution Updated (Dec 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.57 Runway Incursion Alert Message HMI Object

RUNWAY INCURSION MESSAGE Objective To provide to the controller information of the entrence of mobile in the runway

protected area. General Description The Runway Incursion Alert is displayed in the ALERT WINDOW , presenting a line of

the alert description composed of RWY number with traffic callsign presented on red background. The runway incursion alert information line remains in the ALERT WINDOW until the alert is ended.

Invocation System generated when a runway incursion is detected Display Position In the ALERT WINDOW Illustration

Requirement Ref. H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4 Associated Procedures Initiates Come on top window | Move window Used by Display Runway Conflict (step 2 alert) | End Runway Conflict Alert |

Acknowledge alert Associated HMI objects ALERT WINDOW Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.58 Conflicting ATC Clearances Alert Messages HMI Object

CONFLICTING ATC CLEARANCES ALERT MESSAGE Objective To provide to the controller information when the alert function detects manually input of

inconsistent clearances. General Description

The inconsistent clearances Alert is displayed in the ALERT WINDOW , presenting a line of the alert description composed of RWY number in white with traffic callsign presented on red background. The inconsistent clearances alert description line remains in the ALERT WINDOW until the alert is ended.

Invocation System generated when a manual inconsistent clearances input is detected Display Position

In the ALERT WINDOW

Illustration

Alert message for the inconsistant clearance (landing vs. landing)

Alert message for the inconsistent clearance e.g. line-up vs. line-up on the same holding point

Alert message for CROSS vs. TOF

Requirement Ref.

H.SN.CLRS.2 | H.SN.CLRS.1

Associated Procedures Initiates Come on top window | Move window Used by Display Conflicting ATC Clearances Input | End Display Conflicting ATC clearance Input

|Acknowledge alert Associated HMI objects ALERT WINDOW Particularities

-


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.59 Non Conformance To ATC Clearance Alert Messa ges HMI Object

NON CONFORMANCE TO ATC CLEARANCE ALERT MESSAGE Objective To provide to the controller information when the alert function detects non conformance to the

given instruction. General Description

The non conformance to the given instruction Alert is displayed in the ALERT WINDOW , presenting a line of the alert description composed of RWY number in white with traffic callsign presented on red background. The inconsistent clearances alert description line remains in the ALERT WINDOW until the alert is ended.

Invocation System generated when a non conformance to the given instruction is detected Display Position

In the ALERT WINDOW

Illustration

example of alert window with message of non conformance to ATC clearances: i.e a flight which is cleared to linu-up Takes-off- Alarm/ alert Step 2

example of alert message for an aircraft taking of without take off clearance (Information alert / alert Step 1)

Requirement Ref.

H.SN.PROC.2 | H.SN.PROC.1

Associated Procedures Initiates Come on top window | Move window Used by Display Non Conformance to ATC Instructions | End Display Non Conformance to ATC

Instructions Associated HMI objects ALERT WINDOW Particularities

-


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.60 ATCO Input Error w.r.t Airport Layout Alert Messages HMI Object

ATCO INPUT ERROR w.r.t. AIRPORT LAYOUT ALERT MESSAG E Objective To provide to the controller information when the alert function detects that in the manual input

w.r.t airport layout is an error. General Description

The ATCO input error w.r.t airport layout is displayed in the ALERT WINDOW , presenting a line of the alert description composed of RWY number in white with traffic callsign presented on red background. The ATCO input error w.r.t airport layout alert description line remains in the ALERT WINDOW until the alert is ended.

Invocation System generated when ATCO input error w.r.t airport layout is detected Display Position

In the ALERT WINDOW

Illustration

example of alert message when planned taxi route contains a closed TWY

example of alert message when RWY for an a/c is closed (an Information – planned route include the closed taxiway; an alarm – system detects the aircraft on the closed runway)

example of alert message when RWY type is not appropriate for an a/c

Requirement Ref.

H.SN.AREA.5 | H.SN.AREA.6

Associated Procedures Initiates Come on top window | Move window Used by Display ATCO Input Error w.r.t. Airport Lay out | End Display ATCO Input Error w.r.t.

Airport Layout | Set Up Runway/ Taxiway Status Associated HMI objects ALERT WINDOW | TOWED AIRCRAFT E-STRIP | RADAR LABEL | ARR E-STRIP | DEP E-

STRIP | TOWED AIRCRAFT RADAR LABEL Particularities

-

Evolution Updated (Decembre 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.61 Runway Alert HMI Object

RUNWAY ALERT Objective To provide clear and visible runway indication whenever a runway conflict alert

(step 1 or step 2) is detected. General Description The runway shape and background are presented in:

� Information alert colour in case of runway conflict alert step 1 or � Alarm colour in case of runway conflict alert step 2.

Invocation System generated; when a runway conflict alert is detected and displayed as long as the conflict exists.

Display Position On the shape of the concerned runway Illustration - Requirement Ref. H.SN.AREA.1 | H.SN.AREA.2 | H.SN.AREA.3 | H.SN.AREA.4 Associated Procedures Used by Display Runway Conflict (step 1 alert) | Display Runway Conflict (step 2 alert)

| End Runway Conflict Alert Associated HMI objects Particularities - Evolution not implemented (Dec 2008)

4.1.62 CROSS / ENTER Runway warning HMI Object

DISPLAY CROSS/ENTER RUNWAY Objective To provide clear and visible runway indication whenever a runway CROSS or

ENTER instruction is given to an aircraft, vehicle or towed aircraft. General Description The runway shape is presented in Orange and the symbol for the given clearance

(cross, enter) is displayed in the radar label and in the e-strip in orange. Invocation System generated; when a runway CROSS/ENTER is given and displayed as long

as a mobile has this clearance (i.e. input VAC or REL ends runway cross/enter warning display).

Display Position On the shape of the concerned runway Illustration

example for runway enter warning (FIRE1 vehicle is cleared to ENTER runway )

Requirement Ref. H.SN.RWY.1| H.SN.RWY.2| H.SN.RWY.2 | H.SN.RWY.3 | H.SN.RWY.4 Associated Procedures Used by Display EFS section | Input Cross RWY | Input Enter Associated HMI objects VEHICLE E-STRIP | TOWED AIRCRAFT E-STRIP | RWY SECTION Particularities For ENTER and CROSS instructions only Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.63 Traffic Filter Tool HMI Object

TRAFFIC FILTER TOOL Objective To provide the means to the controllers to filter categories of traffic to be displayed. General Description The Traffic Filter Tool is intended to provide possibility for the controller to filter out

traffic (depending on future criteria need to be defined); it will consist of different tools; Height filter is the only current possiblity that is presented in the initial release of the document. Other filters wiil be defined in future release of this document. a) Height Filter: The altitude filtering consists of a conventional slider bar, with the currently selected altitude value in feet. Value increases from the left to the right. The minimum range and the maximum range are defined at local level: current lowest level parameter is FL000, current upper level is FL600, The modification step is 10 FL). Positioning the slider enable to filter out traffic above the altitude value. By default, the maximum range is selected.

Invocation Invoked by Single Click AB on the ‘HEIGHT’ toggle button in the CSD Display Toolbox Window (Ref. the Access Tool procedure).

Display Position Under the CSD Toolbox Window; then can be moved anywhere on the display window.

Illustration

possible height filter tool

Requirement Ref. H.BL.FILT.01 Associated Procedures Initiates Replace Tool | Isolate Tool | Move window | Come on top window | Filter

traffic (height) | Close window | De-iconify window | Iconify window Used by Access Tool Associated HMI objects RADAR TRACK | RADAR LABEL | CSD TOOLBOX WINDOW | C OMPOSITE

SITUATION DISPLAY WINDOW Particularities - Evolution Updated (Dec. 2008); ‘Height’ button is implemented (May 2007) but not the

functionality.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.64 Range and Bearing Tool HMI Object

RANGE AND BEARING TOOL Objective To provide Range and Bearing functionality General Description The Range and Bearing Tool is intended to provide possibility for the controller to

obtain range and bearing information as measured from one point of the airspace to another, and the estimated time of flight of an aircraft to a fixed point of the airspace. Two formats for the estimated time of flight on the tracker link are possible: ‘ETO’ and ‘Time to go’.

Invocation Invoked by Single Click AB on the ‘R&B ’ toggle button in the CSD Display Toolbox Window (Ref. the Access Tool procedure).

Display Position Under the CSD Toolbox Window; then can be moved anywhere on the display window.

Illustration No illustration (to be designed, second 6 month period) Requirement Ref. F.BL.RB.01 Associated Procedures Initiates Replace Tool | Isolate Tool | Move window | Close window | De-iconify

window | Iconify window Used by Access Tool Associated HMI objects COMPOSITE SITUATION DISPLAY WINDOW | CSD TOOLBOX W INDOW Particularities - Evolution Not implemented (Dec 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.65 Callsign Menu HMI Object

CALLSIGN MENU Objective To allow the controller to modify the control responsibility for an aircraft / vehicle,

advise other sectors or Operator roles. It is also used to input ATC clearances. General Description a) The Callsign Menu is a ‘pop-up’ menu

b) The callsign menu is used by the controller to input various clearances and flight / vehicle planning state control function such as ‘Assume’ and ‘Transfer’. (note: clearances can be also input in ITWP via the e-strip clearance field). c) The following principles apply in ITWP: P1. The callsign menu only contains the options that are authorised for a particular light with regards to its flight / vehicle planning state, plus the ‘mark’ option that is authorised all the time. P2. The callsign menu size is reduced to its minimum (no empty lines). P3. The mouse cursor should always default to the most probable next input to issue for a flight on a CWP/Operator role. P4. Previously given clerance could be cancelled (e.g. –[LND]) d) Availability and default items are provided in the tables below (in the next following pages)

Invocation Invoked by Single Click AB on the callsign field within the radar label or anywhere else that this field is displayed (e.g. e-strip). The availability of the Callsign Menu and options associated depend on traffic planning state / sub-state.

Display Position When invoked, the Callsign Menu ‘pops-up’ so that the default item is under the cursor.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Note: in the following tables, a) The ‘√’ shows the options that should be presented in the callsign menu. These options depend on the current flight planning state and sub-state (if relevant), but also on the history of previous clerances for the flight. b) The ‘*’ shows the most probable option meaning where the mouse cursor should be positionned in the callsign menu.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


1. Callsign menu for a GND controller

CALLSIGN Menu for a GND controller - Departure Fli ght Main state Sub-State CALLSIGNMenu option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

‘Assumed’

No Value

‘Assumed’

No Value

When Push-back clearance has been

given

‘Assumed’

No Value

When Taxi

clearance has been given

‘Assumed’

‘Assumed out’

When the taxi clearance has been given

ASSUME √

TAXI √ √*

PUSH BACK √ √*

TRANSFER √*

HOLD √ √

STOP AT √ √ √

MARK √* √* √ √ √ √ √*

CANCEL √ √ √ √ √ √ √

Note: updated in Dec 2008

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


CALLSIGN Menu for a GND controller - Arrival Fligh t Main state

Sub-State CALLSIGNMenu option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

‘Assumed’

No Value

TAXI √* √

HOLD √ √*

STOP AT √*

MARK √* √* √ √

CANCEL √ √ √ √


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


2. Callsign menu for a RWY controller

Callsign menu for a RWY controller - Departure Flight Main state Sub-State Clearance field option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

‘Assumed’

No Value

‘Assumed’

No Value

When ‘Hold’ instruction

has been given

‘Assumed’

No Value

When ‘Conditional line-up’ or ‘ line-up’ clearance has

been given

‘Assumed’

No Value

When ‘Take-Off’ clearance has been

given

‘Assumed’

No Value

When ‘Abort Take-off’ clearance has

been given

‘Assumed’

Assumed out

ASSUME √*

HOLD √ √ √

LINE-UP √* √*

CONDITIONAL LINE-UP

√ √

TAKE-OFF √ √ √*

TRANSFER √*

ABORT TAKE-OFF

√ √

VACATE √ √*

MARK √* √* √ √ √ √ √ √ √*

CANCEL √ √ √ √ √ √ √ √ √

Note: updated in Dec 2008 note: after ‘Abort Take Off’ clearance input on the RWY role, the planning state should be triggered to ‘Pending in’ on the GND controller role. This suggests that the flight should be considered as an arrival flight (GND controller role). Note: For the airport CDG, ‘HOLD AT’ instruction have been implemented in ITWP to enable the controller to input taxi clearance until a certain point (i.e. exit point K1, K2 or K3) to an arriving aircraft

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


CALLSIGN Menu for a RWY controller - Arrival Fligh t Main state Sub-State CALLSIGNMenu option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

Assumed’

No Value

When ‘Assume’ has been input

by the controller

‘Assumed’

No Value

When ‘Continue Approach’


‘Assumed’

No Value

When ‘Cleared to

land’ clearance has been given

‘Assumed’

No Value

When ‘Go-Around’ clearance has been given

Assumed’

No Value

When ‘Vacate’ clearance

has been given

‘Assumed’

Assumed out

ROF √*

ASSUME √*

CLEARED TO LAND

√*

√*

GO AROUND √

√

√

VACATE

√*

FINAL √*

TRANSFER √ to GND √ to APP √* to GND

MARK √* √ √ √ √ √ √ √ √*

CANCEL √ √ √ √ √ √ √ √ √

Note: updated in May 2007

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


CALLSIGN Menu for a COMBINED Role - Departure Fligh t Main state Sub-State CALLSIGNMenu option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

‘Assumed’

No Value

Assumed’

No Value

When pushback clearance has been

given

Assumed’

No Value

When Taxi clearance has been

given

Assumed’

No Value

When the cond.line-up or

line-up clearance has been given

Assumed’

No Value

When Take-Off clearance has been

given

Assumed’

No Value

When Abort

Take-off clearance has been

given

‘Assumed

Assumed out

START-UP √*

ASSUME √

TAXI √ √*

PUSH BACK √ √*

HOLD √ √ √

STOP AT √ √ √

LINE-UP √*

COND. LINE UP

√

TAKE-OFF √*

ABORT TAKE-OFF

√ √

VACATE √ √*

TRANSFER √*

MARK √* √* √ √ √ √ √ √ √ √*

CANCEL √ √ √ √ √ √ √ √ √ √

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft



CALLSIGN Menu for a COMBINED role - Arrival Flight Main state Sub-State CALLSIGNMenu option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

Assumed’

No Value

When ‘Assume’ has been input

by the controller

‘Assumed’

No Value

When ‘Continue Approach’


‘Assumed’

No Value

When ‘Cleared to

land’ clearance has been given

‘Assumed’

No Value

When ‘Go-Around’ clearance has been given

Assumed’

No Value


has been given

‘Assumed’

Assumed out

ROF √*

ASSUME √*

CLEARED TO LAND

√*

√*

GO AROUND √

√

√

VACATE

√*

FINAL √*

TRANSFER √ to APP

TAXI √*

STOP AT

HOLD √

MARK √* √ √ √ √ √ √ √ √*

CANCEL √ √ √ √ √ √ √ √ √

Note: updated in Dec. 2008. HOLD AT is not included as it is specific to the CDG airport.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.66 Runway Menu HMI Object

RUNWAY MENU Objective To allow the controller to change the runway for landing or the runway for take off

for a single flight. General Description The runway menu is used to change the RWY for take off (if departure flight) or

RWY for landing (arriving flight). Invocation The availability of the runway menu depends on the availability to interaction of the

RWY field (when the flight is assumed).

The RWY menu is invoked by single click AB on the RWY field in flight e-strips or radar label. The RWY menu consists of possible runway options (local parameter, depends on airport and possible RWY configurations).

Display Position When invoked, the runway menu ‘pops-up’ so that the possible RWY options are

displayed under the cursor. Illustration

example of runway menu

Requirement Ref. F.BL.UPD.02 Associated Procedures Initiates Open Menu Used by Close Menu | Select Menu Item | Change RWY for Landing (single flight) |

Change RWY for take-off (single flight) Associated HMI objects Particularities - Evolution Updated (September 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.67 Parking / Stand Menu

HMI Object PARKING STAND MENU

Objective To allow the controller to change the parking stand for an arrival flight. General Description The parking / stand menu is used to change the parking stand for an arrival

aircraft. It displays the possible parking options to the controller. Invocation The availability of the parking stand menu depends on the availability to interaction

of the parking stand field (the flight must be assumed).

The parking stand menu is invoked by single click AB on the parking stand field field in flight e-strips or radar label . it consists of possible parking stand options (local parameter, depends on airport ).

Display Position When invoked, the runway menu ‘pops-up’ so that the possible parking stand options are displayed under the cursor.

Illustration

example of parking/stand menu

Requirement Ref. F.BL.UPD.02 Associated Procedures Initiates Open Menu Used by Close Menu | Select Menu Item | Scroll Menu | Change Parking Stand Associated HMI objects Particularities When the controller scrolls over the parking position, then the parking symbol is

highlighted on the airport map (not implemented) Evolution Updated (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.68 Parking / Stand Symbol

HMI Object PARKING STAND SYMBOL

Objective To allow the controller to display / remove display parking names on the airport map.

General Description The display / remove display of parking names (fixed) interaction is enabled via the parking stand symbol

Invocation The invocation of display / remove display of parking stand is performed by single click AB on the parking stand symbol

Display Position When invoked, the stand symbol (filled) and stand name is displayed (see example below). The same invocation also allows removing the display of a parking name (see Display / Remove Display Parking Names procedure).

Illustration

display parking names (example) remove display parking names

Requirement Ref. F.BL.UPD.02 Associated Procedures Used by Display / Remove Display Parking Names Associated HMI objects Particularities when scroll in the parking menu the parking stand symbol and name is highlighted Evolution Updated (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.69 Route Accept Menu HMI Object

ROUTE ACCEPT MENU Objective To allow the controller to accept a modification of the initally planned route. General Description The route accept menu is used to accept a route modification or to confirm the

choice of the system proposed route modification. Invocation The route accept menu is invoked by single click AB on the radar track of the

aircraft or vehicle whenever a route is presented (planned or modified). The menu consists of an ‘accept’ button.

Display Position When invoked, the route accept menu is displayed on the right of the last selected point of the route.

Illustration

Requirement Ref. H.ROUTE.CHG.1 | H.ROUTE.CLR.1 Associated Procedures Initiates Open Menu Used by Cancel Menu | Close Menu | Select Menu Item | Particularities - Evolution Updated (Dec. 2008)

4.1.70 Stop At Menu HMI Object

STOP AT MENU Objective To allow the controller to clear an aircraft to taxi until a certain point on the initially

planned route. General Description The stop at menu is used to clear an aircraft to taxi until a given point of the

planned route. A white moving point along the planned route follows the mouvement of the cursor. It allows the controller to chose a point where the aircraft has to ask for further taxi instructions. the Clear option in the menu aims at validating the controller’s choice and the Close option aims at closing the menu.

Invocation The ‘stop at’ menu is invoked by single click AB on the option ‘Stop At’ in the callsign menu or in the e-strip. The menu consists of a ‘Clear’ button and a ‘Close’ button.

Display Position When invoked, the stop at menu is displayed on the right of the planned route. Illustration

Requirement Ref. F.ROUTE.ORD.1 | H.ROUTE.ORD.1 Associated Procedures Initiates Open Menu Used by Cancel Menu | Close Menu | Select Menu Item | Input Stop At Particularities - Evolution Updated (Dec. 2008 to be further developed)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.71 Holding Point Menu for a departure flight HMI Object

HOLDING POINT MENU Objective To indicate that a departure flight has been instructed to taxi to a specific holding

point. General Description The runway menu is used to change the holding point. Invocation The availability of the runway menu depends on the availability to interaction of the

holding point field.

The RWY menu is invoked by single click AB on the holding point field in flight e-strips or radar label whenever presented. The holding point menu consists of possible holding points options (local parameter, depends on airport and possible RWY configurations).

Display Position When invoked, the holding point menu ‘pops-up’ so that the possible holding point options are displayed under the cursor.

Illustration - Requirement Ref. F.BL.UPD.02 Associated Procedures Initiates Open Menu Used by Cancel Menu | Close Menu | Select Menu Item | Particularities - Evolution not implemented (May 2007)

4.1.72 Holding Point Menu for an arrival flight HMI Object

HOLDING POINT MENU ARR Objective To indicate that an arrival flight has been instructed to taxi to a specific holding

point. General Description The holding point menu is used to change the holding point (e.g. K1, K2 and K3 for

CDG airport. They represent the holding points of runway 27R/ 09L, where the aircraft have to stop before crossing the departure runway towards the terminal).

Invocation The availability of the holding point menu depends on the availability of the holding points at the airport (i.e. if there is only one runway exit point available, then there is no need for this menu).

The holding point menu is invoked by single click AB on the holding point field in flight e-strips or radar labels whenever presented. The holding point menu consists of options related to the holding points available for a given flight (local parameter, depends on the airport layout and the possible RWY configurations).

Display Position When invoked, the holding point menu ‘pops-up’ so that the options for the available holding points are displayed under the cursor.

Illustration

Example of holding point menu (for the flight CLH41, it is possible to select K1, K2 or K3 point)

Requirement Ref. H.BL.ORD.09 Associated Procedures Initiates Open Menu

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Used by Cancel Menu | Close Menu | Select Menu Item | Input HoldAt


4.1.73 Stop bar Menu HMI Object

STOP BAR MENU Objective To activate / deactivate the stop bar. General Description The stop bar menu is used to change the status of the stop bar. Invocation The Stop bar menu is available for the RWY controller. The stop bar menu is

invoked by single click AB on the stop bar.

The menu includes the name of the holding point on the taxiway (i.e. YK).

Two status of the stop bar are available:

- On (stop bar activated – red)

- Off (stop bar de-activated – grey)

The menu closes after selecting an option (On / Off).

Display Position When invoked, the stop bar menu is displayed near the selected stop bar. Illustration

Stop bar On Stop bar Off

Requirement Ref. F.SN.PTD.01 | F.SN.PTD.02 | F.SN.PTD.03 | F.SN.PTD.04 | H.SN.PTD.01 | H.SN.PTD.02 | H.SN.PTD.05

Associated Procedures Initiates Open Menu | Close Menu Used by Select Menu Item | Display Stop Bar Status | Manually Set Up Stop Bar Status Particularities Only for RWY controller action. Currently the stop bar switches off when TOF, LUP

or CLUP clearance is given to an aircraft and switches on after 45 s. The stop bar switches on after an aircraft crosses the stop bar.

Evolution Updated (Dec 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.74 Runway Status Menu HMI Object

RUNWAY STATUS MENU Objective To input open / closed runway status by GND or RWY controller. General Description The runway status menu is used to change the status of each runway threshold. Invocation The Runway status menu is available for RWY and GND controller. The runway

status menu is invoked by single right mouse click on the runway.

The menu includes the name of the threshold on the runway (i.e. 08 and 26).

Two status of the runway are available:

- Open (runway is open for operations)

- Closed (runway is closed for operations)

The menu closes when cursor is not in the menu.

Display Position When invoked, the runway status menu is displayed near the selected runway. Illustration

Runway status set up

Requirement Ref. F.BL.APT.01 | H.BL.APT.01 Associated Procedures Initiates Open Menu | Close Menu Associated HMI objects MAP SELECTION TOOL | AIRP ORT SETUP TOOL Used by Select Menu Item | Set Up Runway/ Taxiway Status Particularities The RWY status may be changed in the AIRPORT SETUP TOOL Evolution Updated (Sep. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.75 Taxiway Status Menu HMI Object

TAXIWAY STATUS MENU Objective To input open / closed taxiway status by GND or RWY controller. General Description The taxiway status menu is used to change the status of a taxiway. Invocation The taxiway status menu is available for RWY and GND controller.

In the MAP SELECTION TOOL , the option ‘taxiway sectors’ should be selected first; the name of taxiway is displayed on the screen. The runway status menu is invoked by single right mouse click on the taxiway name.

The menu includes the name of the taxiway (i.e. PA).

Two status of the runway are available:

- Open (taxiway is open for operations)

- Closed (runway is closed for operations)

The menu closes when cursor is not in the menu.

Display Position When invoked, the taxiway status menu is displayed near the selected taxiway. Illustration

Taxiway status set up Taxiway closed Taxiway open (i.g. K4E)

Requirement Ref. F.BL.APT.01 | H.BL.APT.01 | Associated Procedures Initiates Open Menu | Close Menu | Set Up Runway/ Taxiway Status Associated HMI objects MAP SELECTION TOOL | AIRP ORT SETUP TOOL Used by Select Menu Item Particularities The controller is able to input taxiway status only for a selected taxiway sector. Evolution Updated (Sep 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.76 SID Menu HMI Object SID MENU

Objective To allow the controller to access to SID options for a departure flight. General Description The SID menu is used to modify a SID for a departure flight. Invocation The SID menu is available for departure flights.

The SID menu is only available (accessible) by the RWY menu. The SID menu consists of its possible options.

Display Position When invoked, the holding point menu ‘pops-up’ so that the possible holding point options are displayed under the cursor.

Illustration

- the SID menu is displayed with the RWY menu - the SID default value is highlighted

Requirement Ref. F.BL.UPD.02 Associated Procedures Initiates Open Menu Used by Change SID Particularities - Evolution Updated (Septembre 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.77 Operator Role Menu HMI Object

OPERATOR ROLE MENU Objective To change the Operator role to which a transfer is due to be performed. General Description

The menu is only used in connection with the Direct Transfer option of the callsign menu or e-strip (when available) and is invoked when this option is selected

Invocation The availability of the operator menu depends on the availability to transfer traffic interaction.

The Operator Role Menu is invoked by single click AB on the ‘D-TRANSF’ field in the callsign menu or operator role in the corresponding e-strip clearance field. The possible operator roles and available menu options depend on local airport (local parameters). Possible options are composed of Operator Roles and its associated frequency (e.g. GND 121,95).

Display Position

When invoked, the operator role menu ‘pops-up’ so that the possible operator roles are displayed under the cursor.

Illustration

example of e-strip (single click on ‘GND’ should open the operator role menu (not implemented))

Requirement Ref.

H.FD.TRSF.03

Associated Procedures Used by Select Operator Role for Transfer Associated HMI objects Particularities

-

Evolution not implemented (Dec 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.78 Transfer Menu (callsign manu – only transfer available) HMI Object

TRANSFER MENU Objective To allow the controller to access the Operator role to transfer a vehicle / towed

aircraft. General Description The Transfer menu is used to transfer a vehicle or a towed aircraft. Invocation The Transfer menu is available for assumed vehicles and towed aircraft.

The Transfer menu is only available (accessible) via Operator role in a vehicle / towed aircraft radar labele. The Transfer menu consists of its possible options.

Display Position When invoked, the transfer menu opens so that the possible Operator role may be selected (currently only GND and RWY controllers).

Illustration

example the vehicle is assumed by the RWY controller; possible transfer to GND

example the vehicle is assumed by the RWY controller; possible transfer to GND

Requirement Ref. H.FD.TRSF.03 Associated Procedures Initiates Open Menu Used by Transfer Vehicle/Towed aircraft Particularities - Evolution Updated (November 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.79 Vehicle e-strip HMI Object

VEHICLE E-STRIP Objective To replace the use of paper strips and support the TWR controller in reducing mental

workload and in saving time for operations.

General Description

e-strip fields (see representation below)

• Time : For vehicles, the time field in the flight strip is only required for planned vehicle movements (an estimated time changing to actual when the clearance is given).

• C/S field (interactive field) : callsign; displayed on up to 7 characters; allows the access

to the callsign menu.

• TYPE: Vehicle type.

• CLEARANCE field (interactive field): composed of possible clearance options (i.e. only possible clearances are shown); HOLD, TAXI, CROSS, ENTER, VAC, REL

• RWY field (interactive field) : runway identification, e.g. 26, 08, 19R, 01L etc. • M (interactive field) : gives the possibility to the controller to mark (M) / unmark (UM)

vehicle

Invocation System generated Display Position

Displayed in ‘TAXI OUT’ section on GND role when a vehicle is assumed; displayed in HOLDING POINT section on RWY role when a vehicle is assumed by RWY controller. When GND controller approves CROSS/ENTER runway a vehicle, e-strip is displayed in orange and a ghost e-strip is displayed in the RWY section of the RWY controller. When RWY controller approves CROSS/ENTER runway to vehicle, the e-strip is displayed in the RWY section in orange.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Illustration

examples of vehicle e-strip (transfered)

examples of vehicle e-strip (pending state)

example of vehicle e-strip (assumed)

example of vehicle e-strip (cleared to cross) it is displayed in the RWY to cross bay section

Particularities:

Req. Ref. H.BL.SIL.01 | H.BL.SIL.02 | H.BL.SIL.03 | F.VEH.ORD.3| H.VEH.ORD.1| F.BL.ORD.04 | F.BL.ORD.05 | F.BL.ORD.06 | F.BL.ORD.09

Associated Procedures Used by - Associated HMI objects RWY SECTION | RWY HOLDING P OINT SECTION | GND TAXI-OUT SECTION Particularities Ghost e-strip is system generated in the RWY controller position when GND controller issues CROSS/ENTER instructions to a vehicle Evolution Updated (Dec. 2008) Vehicle strip format: TIME C/S TYPE STAND CLEARANCE RWY M

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.80 Towed aircraft e-strip HMI Object

TOWED AIRCRAFT E-STRIP Objective To replace the use of paper strips for a planned (Pre notified) towed aircraft or assumed not

notified towed aircraft.

General Description

The e-strip for a towed aircraft is displayed for a pre notified flight or a not notified flight assumed by a controller. e-strip fields (see representation below) • Time1 field : Time1 displays specific time information whose content depends on flight

progress. The format may be ‘Ehhmm’, ‘for Estimated time to start towing. • C/S field (interactive field) : callsign; displayed on up to 7 characters; allows the access

to the callsign menu.

• TYPE: Type of aircraft. displayed on up to 6 characters: � Type of aircraft: 2 to 4 characters (ref. ICAO 8643) � An oblique stroke (one character) � One of the following letters to indicate the wake vortex category (ref. ICAO 4444, §4.9.1.1):

• STAND: Destination for a towed aircraft

• CLEARANCE field (interactive field): composed of possible clearance options (i.e. only possible clearances are shown); possible clearance are TOW, HOLD, CROSS, ENTER, REL.

• RWY field (interactive field): runway identification, e.g. 26, 08, 19R, 01L etc. • M (interactive field) : gives the possibility to the controller to mark (M) / unmark (UM)

vehicle Invocation System generated

Display Position

Displayed in TAXI OUT section on GND role when a vehicle is assumed; displayed in HOLDING POINT section on RWY role when a vehicle is assumed by RWY controller. When GND controller approves CROSS/ENTER runway a vehicle, e-strip is displayed in orange and a ghost e-strip is displayed in the RWY section of the RWY controller. When RWY controller approves CROSS/ENTER runway to vehicle, the e-strip is displayed in the RWY section in orange.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Illustration

example of minimum towed aircraft e-strip (assumed)

example of minimum towed aircraft e-strip (pending state / pending in)

example of minimum towed aircraft e-strip (assumed)

example of towed aircraft e-strip (assumed by controller and approved to CROSS and

involved in runway conflict situation)

Particularities:

example of ghost towed aircraft e-strip (assumed and approved to CROSS by GND)

Req. Ref. H.BL.SIL.01 | H.BL.SIL.02 | H.BL.SIL.03 | H.VEH.ORD.1 | H.VEH.ORD.1 Associated Procedures Used by - Associated HMI objects RWY SECTION | RWY HOLDING P OINT SECTION | GND TAXI-OUT SECTION Particularities Ghost e-strip is system generated on the RWY controller position when GND controller

issues CROSS/ENTER instructions to a tow aircraft Evolution Updated Dec. 2008 Towed aircraft strip format: Time 1 C/S TYPE/ STAND CLEARANCE RWY M

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.81 Arrival e-strip HMI Object

ARR E-STRIP Objective To replace the use of paper strips and support the TWR controller in reducing

mental workload and in saving time for operations.

General Description e-strips are available in 2 different sizes: normal and extended. The possible interactions on an arrival e-strip depend on the context format and the operator role. arrival e-strip fields (see representation below) a) normal e-strip format: the following fields are displayed in line 1: • Time1 field : Time1 displays specific time information whose content depends

on flight progress. The format may be ‘Ehhmm’, ‘Thhmm’ or ‘Ahhmm’ for Estimated, Target and Actual times. ELDT is displayed in Time1 field from [ELDT-20 min.]; when the RWY controller assumes the flight, TTT (Time to Touchdown) is displayed in Time1 field. At landing event (input by the RWY controller or system-detected), ALDT (Actual Landing Time) replaces TTT. When the GND controller assumes the flight, EIBT (Estimated In Block Time) is displayed in Time1 field. When the aircraft reaches its stand (system detected), AIBT is displayed in Time1 field. In case of ‘Go Around’ input by the RWY controller before landing, ELDT computed as current_time+20 minutes is displayed in Time1 field. Then incase of Visual Circuit instruction by the controller, TTT is displayed in Time1 field.

• C/S field (interactive field) : callsign; displayed on up to 7 characters; allows

the access to the callsign menu. Data link idenitification is displayed around the aircraft callsign (two vertical bars)

• TYPE/VW (interactive field): Type of aircraft / Wake Vortex category. displayed on up to 6 characters: � Type of aircraft: 2 to 4 characters (ref. ICAO 8643) � An oblique stroke (one character) � One of the following letters to indicate the wake vortex category (ref. ICAO 4444, §4.9.1.1): H (Heavy): all aircraft types of 136 000 kg or more; M (Medium): aircraft types less than 136 000 kg but more than 7 000 kg; L (Light): aircraft types of 7 000 kg or less.

• STAND(-HOLD) (interactive field): Parking stand and -if it is occupied- an indication (letter H, 1 character) and the estimated holding time (number of minutes, 2 characters). example: 313-H10 stands for ‘stand 313, estimated holding time 10 min’.

• to indicate that the flight is landing; when the aircraft touches down the arrows are removed.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


General Description

• I or V field (interactive field): IFR or VFR (1 character, I or V).

• CLEARANCE field (interactive field): composed of possible clearance options (i.e. only possible clearances are shown); possible clearance fields versus flight planning states / sub-states are provided in the tables below (GND and RWY controllers).

• RWY field (interactive field): runway identification, e.g. 26, 08, 19R, 01L etc. The RWY modification is obtained via the RWY Menu.

• SEQ N° field : runway sequence number (from 1 to n); the format is ‘-{runway sequence number}’, e.g. ‘-2’ (if sequence number is 2).

b) extended e-strip format: the following fields are displayed in line 2: Time2 field : Time2 displays specific time information whose content depends on flight progress. The format may be ‘Ehhmm’, ‘Thhmm’ or ‘Ahhmm’ for Estimated, Target and Actual times. a) EIBT is displayed in Time2 field Airline field : airline identification (e.g. LUFTHANSA, IBERIA, etc.)

SSR: SSR code, 2 or 4 digits (normally 4-digit Mode A code).

ADEP : ICAO departure airport code (4 letters)

QNH : Q code (displayed as ‘Qnnnn’ where nnnn is set in millibars)

REMARKS (interactive field) : allows the controller to input specific remarks via an electronic keyboard.


Displayed in bays and sections according to the progress of the flight and controller clearances.

Illustration

example of minimum arr. e-strip (pending state / no value)

example of minimum arr. e-strip (pending state / pending in)

example of minimum arr. e-strip (data link idetifier)

example of minimum arr. e-strip (assumed / no value)

example of minimum arr. e-strip (assumed / assumed out)

example of minimum arr. e-strip (not concerned)

Req. Ref. H.BL.SIL.01 | H.BL.SIL.02 | H.BL.SIL.03 Associated Procedures Used by - Associated HMI objects Particularities - Evolution Data link identifier is displayed. Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Extended arrival strip format:

Time1 C/S (DL) TYPE/VW STAND(-HOLD) I or V CLEARAN CE RWY SEQ N° M Time2 Airline SSR ADEP QNH REMARKS

Normal arrival strip format:

Time1 C/S(DL) TYPE/VW STAND(-HOLD) I or V CLEARANC E RWY SEQ N° M

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.82 Departure e-strip

HMI Object DEP E-STRIP

Objective To replace the use of paper strips and support the TWR controller in reducing mental workload and in saving time for operations.

General Description e-strips are available in 2 different sizes: normal and extended. The possible interactions on a departure e-strip depend on the context format and the operator role. a) normal e-strip format: the following fields are displayed in line 1 (see figure below): • Time1 field : Time1 displays specific time information whose content depends

on flight progress. The format may be ‘Ehhmm’, ‘Thhmm’ or ‘Ahhmm’ for Estimated, Target and Actual times. GND Controller: EOBT is displayed in the Time1 field. When ‘Pushback’ or first ‘Taxi’ clearance (if pushback is not required) is issued by the GND controller, TTOT (Target Take-Off Time) replaces EOBT. When the RWY controller inputs ‘Airborne’, the TTOT becomes ATOT. In case of ‘Abort Take Off’, EIBT is displayed in the Time1 field (the flight is then considered as an arriving flight).

• C/S field (interactive field): callsign; displayed on up to 7 characters; allows to

access possible clearance options (via callsign menu). Data link idenitification is displayed around the aircraft callsign (two vertical bars)

• TYPE/VW (interactive field): Type of aircraft / Wake Vortex category. displayed on up to 6 characters: � Type of aircraft: 2 to 4 characters (ref. ICAO 8643) � An oblique stroke (one character) � One of the following letters to indicate the wake vortex category (ref. ICAO 4444, §4.9.1.1): H (Heavy): all aircraft types of 136 000 kg or more; M (Medium): aircraft types less than 136 000 kg but more than 7 000 kg; L (Light): aircraft types of 7 000 kg or less. The modification of aircraft type is obtained via a menu (aircraft type menu).

• STAND / CLEARANCE LIMIT (interactive field). Displays either the parking stand or the holding point clearance, i.e. parking stand until the first taxi clearance is input by the controller (then clearance limit).

� STAND: Parking Stand (e.g. S76, G142, F39L) � CLEARANCE LIMIT: Holding point / Clearance limit (e.g. YK, YJ, YD, etc.).

The modification of stand or clearance limit is obtained via a menu (parking stand menu or clearance limit menu).

• to indicate that the flight is taking-off; when the aircraft is airborne the arrows are removed.

• SID or V field (interactive field): SID (Standard Instrumernt Departure) or VFR (1 character, V). The SID modification is obtained via the SID Menu.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


General Description

• CTOT (interactive field) : Calculated Take-Off Time; displayed under ‘HH:MM’ format.

This field is interactive, which allows the CLD or GND controller to input a Ready Message (to be sent to the CFMU), via a Ready Message menu.

• CLEARANCE field (interactive field): composed of possible clearance options (i.e.

only possible clearances are shown); possible clearance fields versus flight planning states / sub-states are provided in the tables below (GND and RWY controllers).


• SEQ N° field : runway sequence number (from 1 to n); the format is ‘-{runway sequence

number}’, e.g. ‘-2’ (if sequence number is 2). a) extended e-strip format: the following fields are displayed in line 2 (see figure below): • Time2 field : Time2 displays specific time information whose content depends on flight

progress. The format may be ‘Ehhmm’, ‘Thhmm’ or ‘Ahhmm’ for Estimated, Target and Actual times.

• Airline field : airline identification (e.g. LUFTHANSA, IBERIA, etc.)

• SSR: SSR code, 2 or 4 digits (normally 4-digit Mode A code).

• ADES : ICAO destination airport code (4 letters)

• QNH : Q code (displayed as ‘Qnnnn’ where nnnn is set in millibars)

• REMARKS (interactive field) : allows the controller to input specific remarks, via an electronic keyboard.


e-strips are displayed in appopriate bays and sections according to rules (e.g. time rules) or clearances / transfers input by the controller.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Illustration

example of minimum dep. e-strip (pending state / no value); selected format

example of minimum dep. e-strip (pending state / pending in)

example of minimum dep. e-strip (assumed state / no value)

example of minimum dep. e-strip (assumed state / assumed out)

Particularities:

example of minimum arrival e-strip when ‘hold’ order has been input.

example of marked departure traffic (runway and ‘UM’ (i.e. UnMark) are displayed in marked

colour)

example of departure traffic when take-off clearance has been given (green arrows)

Req. ref H.BL.SIL.01 | H.BL.SIL.02 | H.BL.SIL.03 Associated Procedures Used by - Associated HMI objects Particularities Evolution Updated (May 2007) Extended departure strip format:

Time 1 C/S (DL) TYPE/VW STAND/CLR LMT SID or V CTOT CLEARANCE RWY SEQ N° M Time 2 Airline SSR ADES QNH REMARKS

Normal departure strip format:

Time 1 C/S (DL) TYPE/VW STAND/CLR LMT SID or V CTOT / REA CLEARANCE RWY SEQ N° M

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


4.1.83 CLD e-strip

HMI Object CLD E-STRIP

Objective To replace the use of paper strips and support the CLD controller in reducing mental workload and in saving time for operations.

General Description e-strips are available in 2 different sizes: normal and extended. a) normal e-strip format: the following fields are displayed in line 1 (see figure below):

• Time1 field : EOBT is displayed in the Time1 field. • C/S field (interactive field): callsign; displayed on up to 7 characters; allows to

access possible clearance options (via callsign menu). Data link idenitification is displayed around the aircraft callsign (two vertical bars)

• TYPE/VW (interactive field): Type of aircraft / Wake Vortex category. displayed on up to 6 characters: � Type of aircraft: 2 to 4 characters (ref. ICAO 8643) � An oblique stroke (one character) � One of the following letters to indicate the wake vortex category (ref. ICAO 4444, §4.9.1.1): H (Heavy): all aircraft types of 136 000 kg or more; M (Medium): aircraft types less than 136 000 kg but more than 7 000 kg; L (Light): aircraft types of 7 000 kg or less. The modification of aircraft type is obtained via a menu (aircraft type menu).

• STAND (interactive field). Displays the parking stand. � STAND: Parking Stand (e.g. S76, G142, F39L)

• SID or V field (interactive field): SID (Standard Instrumernt Departure) or VFR (1 character, V). The SID modification is obtained via the SID Menu.

• CTOT (interactive field) : Calculated Take-Off Time; displayed under ‘HH:MM’ format. This field is interactive, which allows the CLD or GND controller to input a Ready Message (to be sent to the CFMU), via a Ready Message menu.

• CLEARANCE field (interactive field): composed of possible clearance options (i.e. only possible clearances are shown), i.e. ASSUME, CLR/DCLR, START, [Shhmm] GND [frequency] after start-up clearance for transfer to the GND controller, where Shhmm is the time at which start-up has been given (e.g. S1025); frequency is the GND frequency (e.g. 121,95).


• M (interactive field): gives the possibility to the CLD controller to mark/unmark a specific flight.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


General Description

a) extended e-strip format: the following fields are displayed in line 2 (see figure below): • Time1 field : Time1 displays the ETOT (Estimated Take Off Time) • Time2 field : Time2 displays the EOBT (Estimated Off Block Time)

• Airline field : airline identification (e.g. LUFTHANSA, IBERIA, etc.)

• SSR: SSR code, 2 or 4 digits (normally 4-digit Mode A code).

• ADES : ICAO destination airport code (4 letters)

• QNH : Q code (displayed as ‘Qnnnn’ where nnnn is set in millibars)

• REMARKS (interactive field) : allows the controller to input specific remarks, via an electronic keyboard.


e-strips are displayed in appopriate bays and sections according to rules (e.g. time rules) or clearances / transfers input by the controller.

Illustration

exemple of CLD e-strip in the Pending DEP section

exemple of CLD e-strip in the CLD Active Section

exemple of CLD e-strip in the START section (S0607 is the time at which start up clearance

has been given by the CLD controller)

exemple of CLD extended e-strip

Req. ref H.BL.SIL.01 | H.BL.SIL.02 | H.BL.SIL.03 Associated Procedures Used by - Associated HMI objects Particularities - Evolution Updated (July 2007) Extended CLD strip format:

Time 1 C/S - DL TYPE/VW STAND SID or V CTOT RWY SEQ N° M Time 2 Airline SSR ADES QNH REMARKS

Normal CLD strip format: Time 1 C/S - DL TYPE/VW STAND SID or V CTOT / REA CLEARANCE RWY M

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


1. e-strip clearance field for a GND controller

e-strip clearance field for a GND controller - Departure Flight Main state Sub-State CALLSIGNMenu option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

‘Assumed’

No Value

‘Assumed’

No Value

When Push-back clearance has been

given

‘Assumed’

No Value

When Taxi


‘Assumed’

‘Assumed out’

When the taxi clearance has been given

START-UP √* √

ASSUME √

TAXI √ √*

PUSH BACK √ √*

TRANSFER √*

HOLD √

STOP AT √ √* √*

Updated Dec 2008: Start up is available on the GND position only if CLD is not available.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


e-strip clearance field for a GND controller - Arrival Flight Main state

Sub-State Clearance field option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

‘Assumed’

No Value

TAXI √* √

HOLD √ √*

HOLD AT* √ √*

* it is available in case the RWY controller have transferred the flight to the GND just after the aircraft has been landed.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


2. e-strip clearance field for a RWY controller

e-strip clearance field for a RWY controller - Departure Flight Main state Sub-State Clearance field option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

‘Assumed’

No Value

‘Assumed’

No Value

When ‘Hold’ instruction

has been given

‘Assumed’

No Value

When ‘Conditional line-up’ or ‘ line-up’ clearance has

been given

‘Assumed’

No Value

When ‘Take-Off’ clearance has been

given

‘Assumed’

No Value

When ‘Abort Take-off’ clearance has

been given

‘Assumed’

Assumed out

ASSUME √*

HOLD √ √ √

STOP AT √ √

LINE-UP √* √*

CONDITIONAL LINE-UP

√ √

TAKE-OFF √ √ √*

TRANSFER √*

ABORT TAKE-OFF

√ √

VACATE √ √*

Updated Dec. 2008

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


e-strip clearance field for a RWY controller - Arrival Flight Main state Sub-State Clearance field option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

Assumed’

No Value

Or when ‘Final’ has been input

by the controller

‘Assumed’

No Value

When ‘Continue Approach’ clearance

has been given

‘Assumed’

No Value

When ‘Cleared to land’ clearance has been

given

‘Assumed’

No Value

When ‘Go-Around’ clearance

has been given

Assumed’

No Value


has been given

‘Assumed’

Assumed out

ROF √*

ASSUME √*

CLEARED TO LAND

√ √*

GO AROUND √ √ √

HOLD AT √

VACATE √*

FINAL √*

TRANSFER √ to GND √ to APP √* to GND

• Cleared to land: When the RWY controller gives the ‘Cleared to land’ clearance, 3 green arrows pointing down (��) are displayed on the e-strip on the left of the clearance field

until the RWY controller transfers the flight. • Go around: When the RWY controller inputs ‘Go around’, the aircraft is moved in the ‘AIRBORNE’ section. The RWY controller has the following options: either to keep the flight

(via ‘FINAL’ clearance, most probable option) or to transfer the flight to APP (via ‘TRANSFER’ clearance). The consequence of ‘FINAL’ instruction is to move the e-strip in the FINAL section with the corresponding clearance field options. Tranferring back the flight to APP controller (via ‘TRANSFER’ instruction) leads to move the e-strip to the ‘PENDING ARR’ section with an updated ELDT, i.e. ELDT NEW = ELDT OLD + 20 min.

note: updated (Dec 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


3- e-strip clearance field for a CLD controller

e-strip clearance field for a CLD controller

Main state Sub-State CALLSIGNMenu option

‘Not concerned’

No Value

‘Pending’

No Value

‘Pending’

Pending-in

‘Assumed’

No Value

‘Assumed’

No Value

When CLR has

been given

‘Assumed’

‘Assumed out’

When the start-up clearance has been

given

ASSUME √

CLR/DCLR (*) √

START √

TRANSFER √

(*): DCLR (En-route clearance via data link) is not implemented (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5 Description of Procedures

5.1 WIMP GRAPHICAL USER INTERFACE MANAGEMENT

5.1.1 Windows Management The following table provides a summary of procedures associated to windows which are described in the following sections. Procedures Objective Open window To display a window. Close window To close a displayed window. Move window To move a window Come on top window To transfer a window from its current position to the top of its stack. Iconify window To modify the displayed aspect of a window from a full display to a small

pictorial representation (icon). De-iconify window To restore the original full display of the iconified window. Page scroll window To scroll a window in pages. Re-scale window To change the scale of the content of a window. The aperture of the

image window remains constant and the image is re-scaled to fill the re-sized window, i.e. the image gets bigger or smaller as the window is re-scaled.

Re-size window To change the size of a window. The scale of the window contents is not changed but the aperture of the window is changed to show an increased or decreased field of view.

Slider scroll window To manually scroll a window. Step scroll window To scroll a window in incremental steps.

5.1.1.1 Open window Procedure

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Open window Objective To display a window. Actors RWY Controller | GND Controller Trigger A window can be opened

a) either on an internal system event after the system start-up (e.g. system message display…). In this case a window is opened automatically. b) or on controller decision. In this case a window is opened manually by the controller from an invoking field (or button). Note: When a window/tool is opened and moved to a different position and then closed, it reopens at the last position not the original default position

Pre-condition The window is not displayed. Dialogue Action Result 1a. occurrence of an internal System

event 1a or 1b - The window is opened at its default position, or, if it is opened and moved to a different position and then closed, it reopens at the last position.

OR 1b. Single Click AB on the window

invoking field (button)

Requirement Ref. H.BL.HMI.04 Associated Procedures Following Close window | Come on top window | De-iconify window | Close window |

Move window | Come on top window | Iconify window | De-iconify window Associated HMI Objects Uses WINDOW | LOGON WINDOW | MET INFORMATION WINDOW | NAVAIDS

INFORMATION WINDOW | EXTENDED RADAR LABEL WINDOW | SYSTEM MESSAGE WINDOW | PREFERENCES SETTING WINDOW

Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.2 Close window Procedure

Close window Objective To close a displayed window. Actors RWY Controller | GND Controller Trigger A window can be closed:

a) either on an internal System event. In this case a window is closed automatically. b) Or on controller decision.

Pre-condition The window is displayed. The Close button of the window is available.

Dialogue Action Result 1a. Occurrence of an internal System

event 1a or 1b. The window is closed.

OR 1b. Single Click AB on the Close

button of the window

Requirement Ref. H.BL.HMI.04 Associated Procedures Previous Open window Associated HMI Objects Initiated by WINDOW | MET INFORMATION WINDOW | NAVAIDS INFORMATION WINDOW

| EXTENDED RADAR LABEL WINDOW | SYSTEM MESSAGE WINDOW | PREFERENCES SETTING WINDOW | CSD SUB-VIEWS TOOL | EFS TOOL| EFS CONFIGURATION TOOL | LABEL CONFIGURATION TOOL | LABEL OVERLAP MANAGEMENT TOOL | MAP SELECTION TOOL | SPEED VECTOR and TRACK HISTORY TOOL| TRAFFIC FILTER TOOL | ZOOM TOOL


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.3 Move window Procedure

Move window Objective To move a window Actors RWY Controller | GND Controller Trigger Controller action. Pre-condition The window is displayed. Some part of the name bar of the window is available on

the display surface. Dialogue Action Result 1. Press and Drag AB in the name

bar part of the window 1. The window moves in a fixed relation to the cursor to a new position on the screen (the window should be re-drawn with a speed that allows it to track the cursor position moving at the same speed as is required in normal cursor movement).

2. Release AB 2. The window stays at its last display position.

Requirement Ref. H.BL.HMI.04 Associated Procedures Previous Open window Associated HMI Objects Initiated by

WINDOW | MET INFORMATION WINDOW | NAVAIDS INFORMATION WINDOW | EXTENDED RADAR LABEL WINDOW | SYSTEM MESSAGE WINDOW | PREFERENCES SETTING WINDOW | CSD SUB-VIEWS TOOL | EFS TOOL| EFS CONFIGURATION TOOL | LABEL CONFIGURATION TOOL | LABEL OVERLAP MANAGEMENT TOOL | MAP SELECTION TOOL | SPEED VECTOR and TRACK HISTORY TOOL| TRAFFIC FILTER TOOL | ZOOM TOOL


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.4 Come on top window Procedure

Come on top window Objective To transfer a window from its current position to the top of its stack. Actors RWY Controller | GND Controller Trigger Controller action. Pre-condition Part of the window frame is available Dialogue Action Result 1. Single Click AB on the frame of

the partially covered window

1. The window moves to the top of its stack.

Requirement Ref. H.BL.HMI.04 Associated Procedures Previous Open window Associated HMI Objects Initiated by WINDOW | MET INFORMATION WINDOW | NAVAIDS INFORMATION WINDOW

| EXTENDED RADAR LABEL WINDOW | PREFERENCES SETTING WINDOW | CSD SUB-VIEWS TOOL | EFS TOOL| EFS CONFIGURATION TOOL | LABEL CONFIGURATION TOOL | LABEL OVERLAP MANAGEMENT TOOL | MAP SELECTION TOOL | SPEED VECTOR and TRACK HISTORY TOOL | TRAFFIC FILTER TOOL | ZOOM TOOL

Particularities The priority assigned to a window determines the ability to move it in front of other windows/objects: a window can only be moved in front of windows/objects of the same or of a lower priority.

Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.5 Iconify window Procedure

Iconify window Objective To modify the displayed aspect of a window from a full display to a small pictorial

representation (icon). Actors RWY Controller | GND Controller Trigger Controller action. Pre-condition The Iconify button of the window is available. Dialogue Action Result 1. Single Click AB on the Iconify

button of the window

1. The window is iconified. The icon is placed at its previous position or, if the window is being iconified for the first time, so that the position of the top left-hand corner of the icon coincides with the top left-hand corner of the window at the time it was iconified.

Requirement Ref. H.BL.HMI.04 Associated Procedures Following De-iconify window Previous Open window Associated HMI Objects Initiated by WINDOW|PREFERENCES SETTING WINDOW|GENERAL TOOLBOX WINDOW |

CSD TOOLBOX WINDOW | CSD SUB-VIEWS TOOL | EFS TOOL| EFS CONFIGURATION TOOL | LABEL CONFIGURATION TOOL | LABEL OVERLAP MANAGEMENT TOOL | MAP SELECTION TOOL | SPEED VECTOR and TRACK HISTORY TOOL| TRAFFIC FILTER TOOL | ZOOM TOOL

Particularities The icon of a window retains the same screen priority as the window that it represents.

Evolution -

5.1.1.6 De-iconify window Procedure

De-iconify window Objective To restore the original full display of the iconified window. Actors RWY Controller | GND Controller Trigger Controller action. Pre-condition The icon of the window is available Dialogue Action Result 1. Single Click AB on the icon of the

window

1. The window is displayed with the same attributes (size, position…) as when it was iconified.

Requirement Ref. H.BL.HMI.04 Associated Procedures Previous Iconify window Associated HMI Objects Initiated by WINDOW|PREFERENCES SETTING WINDOW|GENERAL TOOLBOX WINDOW |

CSD TOOLBOX WINDOW | CSD SUB-VIEWS TOOL | EFS TOOL| EFS CONFIGURATION TOOL | LABEL CONFIGURATION TOOL | LABEL OVERLAP MANAGEMENT TOOL | MAP SELECTION TOOL | SPEED VECTOR and TRACK HISTORY TOOL| TRAFFIC FILTER TOOL | ZOOM TOOL


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.7 Re-size window Procedure

Re-size window Objective To change the size of a window. The scale of the window contents is not changed

but the aperture of the window is changed to show an increased or decreased field of view.

Actors RWY Controller | GND Controller Trigger The re-sizing of a window can be:

a) either automatic (by the system): the system dynamically re-sizes the window to allow just adequate display of varying amounts of information. b) or on controller decision. In this case the window is re-sized manually by the controller.

Pre-condition Manual re-sizing: the window re-size feature (button) is available. Dialogue Action Result 1. Press and Hold AB on the Re-size

button 1. The window is fixed at its top left-hand

corner. 2. Press and Drag AB

2. Dragging the window from the corner

in the X and Y directions permits two axes re-size. (Dragging the window in the X or the Y directions permits a single axis re-size).

3. Release AB

3. The current location of the Varying Aperture button becomes the new button position of the window.

Requirement Ref. H.BL.HMI.05 Associated Procedures Previous Open window Associated HMI Objects Initiated by WINDOW | COMPOSITE SITUATION DISPLAY WINDOW Particularities Font sizes do not change when windows are re-sized. Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.8 Re-scale window Procedure

Re-scale window Objective To change the scale of the content of a window. The aperture of the image window

remains constant and the image is re-scaled to fill the re-sized window, i.e. the image gets bigger or smaller as the window is re-scaled.

Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The window re-scale feature (button) is available. Dialogue Action Result 1. Press and Hold AB on the Re-

scale button 1. The window is fixed at its top left-hand

corner. 2. Press and Drag AB

2. Dragging the window from the corner

expands/contracts it in the X/Y directions.

3. Release AB

3. The current location of the re-scale button becomes the new button position of the window. The aperture of the image window remains constant and the image is re-scaled to fill the re-sized window.

Requirement Ref. H.BL.HMI.05 Associated Procedures Previous Open window Associated HMI Objects Initiated by WINDOW | COMPOSITE SITUATION DISPLAY WINDOW Particularities When a window is re-scaled to a different extent in the X and Y directions changing

the aspect ratio of the window, the aspect ratio of the contents does not change. The displayed image retains the same centring and is re-scaled to maintain the X axis extent as constant.

Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.9 Page scroll window Procedure

Page scroll window Objective To scroll a window in pages. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The scroll bar window is available Dialogue Action Result 1. Single Click AB on the scroll bar

body between the slider bar and upper arrow button

1. Page Scroll Up

2. Single Click AB on the scroll bar body between the slider bar and lower arrow button

2. Page Scroll Down

3. Single Click AB on the scroll bar body between the slider bar and left arrow button

3. Page Scroll Left

4. Single Click AB on the scroll bar body between the slider bar and right arrow button

4. Page Scroll Right

Requirement Ref. H.BL.HMI.05 Associated Procedures Previous Open window Associated HMI Objects Initiated by WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.10 Slider scroll window Procedure

Slider scroll window Objective To manually scroll a window. Actors RWY Controller | GND Controller Trigger Controller action. Pre-condition The scroll bar of the window is available. Dialogue Action Result 1. Press and Drag AB on the slider 1. The slider moves accordingly. 2. Release AB

2. The screen image is redrawn on the

same scale but with the centre of the display displaced in the same sense as the slider has been dragged, and in proportion to the displacement of the slider relative to the scale.

Requirement Ref. H.BL.HMI.05 Associated Procedures Previous Open window Associated HMI Objects Initiated by WINDOW | COMPOSITE SITUATION DISPLAY WINDOW Particularities In cases where the potential field of view is limited, the slider shall reach the end

of the slider bars to correspond with the limit of possible movement of the display. If the cursor is moved off the slider with AB still held down, the slider will continue to track the appropriate axis of cursor movement until AB is released, as if the cursor were still positioned on the slider (retention area without limit).

Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.1.11 Step scroll window Procedure

Step scroll window Objective To scroll a window in incremental steps. Actors RWY Controller | GND Controller Trigger Controller action. Pre-condition The sroll bar of the window is available Dialogue Action Result 1. Single Click AB on the up arrow

button 1.image scroll down of an incremental step

2. Single Click AB on the down arrow button

2.image scroll up of an incremental step

3. Single Click AB on the left arrow button

3.image scroll right of an incremental step

4 . Single Click AB on the right arrow button

4.image scroll left of an incremental step

5. Press and Hold AB on any arrow button

5.the displayed image is continuously displaced in the appropriate direction.

Requirement Ref. H.BL.HMI.05 Associated Procedures Previous Open window Associated HMI Objects Initiated by WINDOW Particularities Each click results in a displacement of the displayed image in the opposite

direction to the incremental pointer i.e. the pointer indicates the direction in which the window frame moves relative to the image. The dimension of a scroll step is dependent on the content type of the window: a) The scroll step of a window displaying graphical images (such as the radar image) is a parameter (with default setting of 1/10 th of the display). b) The scroll step of a window displaying textual information is 1 line of text.

Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.2 Menus Management The following table provides a summary of procedures associated to menus which are described in the following sections. Procedures Objective Open Menu To display a menu Scroll Menu To scroll a menu Select Menu Item To select an option item in the menu Close Menu To close (remove) a displayed menu dialogue after having made a

selection Cancel Menu To cancel an initiated menu dialogue without having made a selection

5.1.2.1 Open menu Procedure Open Menu

Objective To display a menu. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The menu is not displayed Dialogue Action Result 1. Single Click AB on the menu

invoking field 1. The menu is displayed at its default

position. Requirement Ref. H.BL.HMI.18 Associated Procedures Previous Select Traffic Following Cancel Menu | Close Menu | Scroll Menu | Select Menu Item Associated HMI Objects Uses MENU | RUNWAY MENU | CALLSIGN MENU | HOLDING POINT MENU|

OPERATOR ROLE MENU | PARKING STAND MENU | STOP BAR MENU | RUNWAY STATUS MENU

Particularities - Evolution Updated (October 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.2.2 Scroll menu

Procedure Scroll Menu

Objective To scroll a menu. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition A scrollable menu is displayed Dialogue Action Result Depending on the implemented

scroll mechanism and the defined scrolling parameters, either only the Step scroll window procedure (with arrow buttons) or also the Page scroll window procedure and the Slider scroll window procedure (with a scroll bar) will be possible to scroll a menu.

Requirement Ref. H.BL.HMI.18 Associated Procedures Previous Open Menu Following Cancel Menu | Select Menu Item Associated HMI Objects Initiated by MENU | PARKING STAND MENU Particularities - Evolution -

5.1.2.3 Select menu item Procedure

Select Menu Item Objective To select an option item of a menu. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition A menu is displayed Dialogue Action Result 1. Single Click AB on an available

option of the menu 1. The action related to the selected item

is launched. Requirement Ref. H.BL.HMI.18 Associated Procedures Previous Open Menu | Scroll Menu Following Close Menu Associated HMI Objects Initiated by MENU | RUNWAY MENU | CALLSIGN MENU | HOLDING POINT MENU|

OPERATOR ROLE MENU | PARKING STAND MENU | RUNWAY STATUS MENU | ROUTE ACCEPT MENU | RUNWAY MENU


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.1.2.4 Close menu Procedure

Close Menu Objective To close (remove) a displayed menu dialogue after having made a selection. Actors RWY Controller | GND Controller Trigger An available option of the menu has been selected. The action related to the

selected menu item is launched. Controller action Pre-condition A menu is displayed Dialogue Action Result 1. Select Menu Item 1. The menu is removed Requirement Ref. H.BL.HMI.23 Associated Procedures Previous Open Menu | Scroll Menu Associated HMI Objects Initiated by MENU | RUNWAY MENU | CALLSIGN MENU | HOLDING POINT MENU|

OPERATOR ROLE MENU | PARKING STAND MENU | STOP BAR MENU |RUNWAY STATUS MENU

Particularities - Evolution Updated (Octobre 2007)

5.1.2.5 Cancel menu Procedure

Cancel Menu Objective To cancel an initiated menu dialogue without having made a selection. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition A menu is displayed Dialogue Action Result 1a - Single Click IB inside the menu

region or 1b - Single Click AB or IB outside the

menu region

1a or 1b. The dialogue is discarded. The menu is removed

Requirement Ref. H.BL.HMI.24 Associated Procedures Previous Open Menu | Scroll Menu Associated HMI Objects Initiated by MENU | RUNWAY MENU | CALLSIGN MENU | HOLDING POINT MENU|

OPERATOR ROLE MENU | PARKING STAND MENU Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.2 ACCESS CWP The following table provides a summary of procedures associated to windows which are described in the following sections. Procedures Objective Log On CWP To access the CWP functions as an identified user. Log Out CWP To exit the CWP functions

5.2.1 Access / exit the CWP functions

5.2.1.1 Log on CWP

Procedure Log On CWP

Objective To access the CWP functions as an identified user. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The LOGON WINDOW is available Dialogue Action Result 1. Input the login A '*' is displayed in the feedback zone for

each inputted character 2. Single Click enter and input the

password A '*' is displayed in the feedback zone for each inputted character

3. Single Click enter 3a. The password is correct The Log On Window is removed. OR 3b. The password is not correct

3b. Login and password are cleared. Then proceed from step 1.

4. Single click on ‘Launch TWR’ icon Possible scenarios/user roles are displayed

5. Choose a user role 1. The screen and window configuration set-up of the user are restored.

2. The access to the CWP functions is allowed.

3. The control toolbox window (Edep console) is displayed

Requirement Ref. F.BL.LOG.01 | F.BL.LOG.02 Associated Procedures Following Access Tool Associated HMI Objects Initiated by - Uses LOGON WINDOW Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.2.1.2 Log out CWP Procedure

Log Out CWP Objective To exit the CWP functions. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition - Dialogue Action Result 1. Single Click AB on the 'LOG'

toggle button 1. The 'LOG' button is shown as

depressed ; the Log On Window is displayed ; The access to the CWP functions is not allowed any more.

Requirement Ref. F.BL.LOG.03 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by - Uses LOGON WINDOW Particularities As the log out does not remove the current configuration, but simply removes the

possibility to interact with the CWP, this procedure can also be used as a temporary 'locking' function of the 'CWP'. The Log On CWP procedure can then be used again to de-lock the CWP.

Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.3 MANAGE THE DISPLAY LAYOUT

5.3.1 Set-Up the Display and Access Screen Settings

5.3.1.1 Save configuration set-up Procedure

Save Configuration Set-Up Objective To store the current screen set-up. To delete a previously stored screen set-up by

overwriting it with another screen set-up. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The PREFERENCES SETTING WINDOW is available Dialogue Action Result 1. Single Click AB on a numbered

radio button in region 1. 1. The radio button is redrawn as

depressed; any other depressed button in that region is released.

2. Single Click AB on the SAVE

button

2. The current screen configuration is saved under that radio button. The text of the button number is displayed in StoredValue colour to show that a configuration has been stored with this button. If a new configuration is saved on a previously saved configuration, the former overwrites the latter.

Requirement Ref. F.BL.SET.01 | F.BL.SET.06 Associated Procedures Previous Access Tool Following Access Configuration Set-Up Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.3.1.2 Access configuration set-up Procedure

Access Configuration Set-Up Objective To access and display a previously stored or the default screen configuration. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The PREFERENCES SETTING WINDOW is available Dialogue Action Result 1. Single Click AB on a numbered

radio button or on the 'DEF' radio button in region 1

1. The button is redrawn as depressed; any other depressed button in that region is released.

2. Single Click AB on the LOAD button

2. - If a stored screen set-up is associated

with the button (i.e. the radio button number is in StoredValue colour), the screen is redrawn accordingly.

- If not, the screen is not re-drawn (the cursor changes to the ‘Caution’ cursor when moved over the LOAD button.

Requirement Ref. F.BL.SET.03 | F.BL.SET.05 Associated Procedures Previous Save Configuration Set-Up Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution not implemented (may 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.3.1.3 Set-up input devices

Procedure Set Mouse Hand

Objective To set the mouse buttons for right or left-handed users. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The PREFERENCES SETTING WINDOW is available Dialogue Action Result 1. Single Click AB on the 'L' or 'R'

radio button in region 2

1. The button is redrawn as depressed. The other depressed button is released. The mouse buttons use is modified accordingly, i.e.: - Right hand use: the left button is the Action Button (AB), the right button is the Information Button (IB). - Left hand use: the right button is the Action Button (AB), the left button is the Information Button (IB).

Requirement Ref. F.BL.SET.07 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Particularities - Evolution Not implemented (May2007)

5.3.2 Set-Up Screen Parameters

5.3.2.1 Select day/night/sun settings Procedure

Select day/night/sun settings Objective To select between day / night / sun screen settings Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The PREFERENCES SETTING WINDOW is available Dialogue Action Result 1 - Single Click AB on the 'Day',

‘Night' or ‘Sun’ radio buttons in region 3

1. The selected button is redrawn as depressed. If any, the other depressed button is released. The bright and contrast settings are applied accordingly.

Requirement Ref. F.BL.SET.07 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.3.2.2 Fine tune brightness settings Procedure

Fine Tune Brightness Settings Objective To fine tune brightness settings Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The PREFERENCES SETTING WINDOW is available Dialogue Action Result 1. Press and Drag AB on the

brightness slider cursor along the slider

1. As the slider cursor moves, the brightness value is shown below the slider, and increases from the left to the right.

2. Release AB 2. The brightness changes as quickly as possible to reflect changes


5.3.2.3 Fine tune contrast settings Procedure

Fine Tune Contrast Settings Objective To fine tune contrast settings. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The PREFERENCES SETTING WINDOW is available Dialogue Action Result 1. Press and Drag AB on the contrast

slider cursor along the slider 1. As the slider cursor moves, the contrast

value is shown below the slider, and increases from the left to the right.

2. Release AB 2. The contrast changes as quickly as possible to reflect changes


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.3.3 Manage Toolbar Functions

5.3.3.1 Access Tool Procedure

Access Tool Objective To make available and access a window (tool) represented by a toggle button in a

"parking rank" area of a Toolbox Window. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The ‘tool’ toggle button is available and is in undepressed state. Dialogue Action Result 1. Single Click AB on the toggle

button in a Toolbox 1a. The tool is opened at its default

position, or at a location defined by the currently stored preferences list. A tool having been displaced during the session opens at its last position.

1b. The toggle button in the Toolbox is shown as depressed.

Requirement Ref. F.BL.TOOL.01 Associated Procedures Following Isolate Tool Previous Associated HMI Objects Initiated by CSD TOOLBOX WINDOW | GENERAL TOOLBOX WINDOW Uses CSD SUB-VIEWS TOOL | EFS TOOL| EFS CONFIGURATION TOOL | LABEL

CONFIGURATION TOOL | LABEL OVERLAP MANAGEMENT TOOL | MAP SELECTION TOOL | SPEED VECTOR and TRACK HISTORY TOOL | TRAFFIC FILTER TOOL | ZOOM TOOL


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.3.3.2 Isolate Tool Procedure

Isolate Tool Objective To isolate a tool in order to make it available for use independently of its parent

Toolbox. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The tool is available. (Ref the Access Tool procedure). Dialogue Action Result 1. Press and Drag AB in the name

bar part of the tool 1. The tool moves in a fixed relation to the

cursor to a new position on the screen. 2. Release AB 2a. The tool stays at its last display

position. 2b. The tool is presented open in the

Toolbox: the empty location of the tool shows the label of the displaced tool, and is displayed in Button2Depressed colour as a standard toggle button.

Requirement Ref. H.BL.TOOL.02 Associated Procedures Previous Access Tool Following Replace Tool Associated HMI Objects Initiated by CSD SUB-VIEWS TOOL | EFS TOOL| EFS CONFIGURATION TOOL | LABEL


Uses CSD TOOLBOX WINDOW | GENERAL TOOLBOX WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.3.3.3 Replace Tool Procedure

Replace Tool Objective To replace back into its parent Toolbox a window (tool) that has been accessed

and/or isolated (Ref. the Access Tool and the Isolate Tool procedures). Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The tool has been isolated from its parent Toolbox. The Close button of the tool is

available, or the toggle button representing the tool in the Toolbox is available. The toggle button representing the tool in the Toolbox is shown as depressed.

Dialogue Action Result 1a - Single Click AB on the Close

button of the tool OR 1b - Single Click AB on the toggle

button representing the tool in the Toolbox

1a or 1b - The tool is replaced back to its parent Toolbox or is closed. The toggle button representing the tool in the Toolbox is shown as undepressed.

Requirement Ref. H.BL.TOOL.02 Associated Procedures Following Access Tool Previous Isolate Tool Associated HMI Objects Initiated by CSD SUB-VIEWS TOOL | EFS TOOL| EFS CONFIGURATION TOOL | LABEL


Uses CSD TOOLBOX WINDOW | GENERAL TOOLBOX WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4 ACCESS AIR, SURFACE AND TIME INFORMATION

5.4.1 Zoom, offset and modify the geographical orie ntation of the display view

5.4.1.1 Perform Zoom Procedure

Perform Zoom.1 Objective To change the selected situation display range via a zoom in and zoom out

mechanism. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The ZOOM TOOL is available Dialogue Action Result 1. Press and Drag AB on slider

cursor along the slider on the Zoom tool

1. As the cursor moves, the range in meters or nautical miles is shown below the slider. The radar display is redrawn to keep track of the slider

Requirement Ref. F.BL.ZOOM.01 Associated Procedures Previous Access Tool Following Store Zoom Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution -

Procedure Perform Zoom.2

Objective To change the selected situation display range via a zoom in and zoom out mechanism.

Actors RWY Controller | GND Controller Trigger Controller action Pre-condition - Dialogue Action Result 1. Use mouse wheel to zoom in or

zoom out.

1. The radar display is redrawn.

Requirement Ref. F.BL.ZOOM.01 Associated Procedures Following Store Zoom Associated HMI Objects Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.1.2 Store zoom Procedure

Store Zoom Objective To store the current zoom range and map centre for future access. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The ZOOM TOOL is available. A zoom range has been selected. The

SAVE/DELETE button legend reads ‘SAVE’ in TextUnselected colour (the maximum number of zooms is not reached).

Dialogue Action Result 1. Single Click AB on the SAVE

button. 1. The current zoom setting and map

centre-point is stored. The ‘SAVE’ legend on the button changes to ‘DELETE’.

2. Press and drag AB on slider

cursor to move it away from the location of the stored value .

2. The ‘DELETE’ legend on the button changes to ‘SAVE’. The stored value indicator is drawn to correspond to the centre of the stored cursor position. The zoom range value of the saved position is displayed at its original location. If the maximum number of stored zooms is reached (local parameter), the ‘SAVE’ legend turns to StoredValue colour.

Requirement Ref. H.BL.ZOOM.03 Associated Procedures Previous Perform Zoom.1 | Perform Zoom.2 Following Delete Zoom | Retrieve Zoom Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.1.3 Retrieve zoom Procedure

Retrieve Zoom Objective To access a stored zoom setting. Actors RWY Controller | GND Controller Trigger Controller action. Pre-condition The ZOOM TOOLis available. A zoom setting has already been stored. Dialogue Action Result 1. Single Click AB on the stored

zoom value.

1. The slider cursor jumps to the pointed value. The radar display is redrawn accordingly to the saved zoom setting. The SAVE/DELETE button reads ‘DELETE’.

Requirement Ref. F.BL.ZOOM.05 Associated Procedures Previous Store Zoom Following Delete Zoom Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution not implemented (May 2007)

5.4.1.4 Zoom back Procedure Zoom Back

Objective To zoom (out) back (or reset) Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The Zoom Back (Reset) Button is available. Dialogue Action Result 1. Single Click AB on the ZOOM

BACK BUTTON

1. In the ZOOM TOOL, the slider cursor jumps to the zoom value stored under the ZOOM BACK BUTTON . The composite situation display window is redrawn accordingly. The ZOOM BACK BUTTON is removed.

Requirement Ref. F.BL.ZOOM.05 Associated Procedures Previous Perform Zoom.1 | Perform Zoom.2 Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.1.5 Delete zoom Procedure

Delete Zoom Objective To delete a stored zoom setting. Actors RWY Controller | GND Controller Trigger Controller action. Pre-condition The ZOOM TOOL is available. A zoom setting has been stored and accessed (the

SAVE/DELETE button reads ‘DELETE’). Dialogue Action Result 1. Single Click AB on the button

‘SAVE/DELETE’.

1. The selected value is removed from the stored save set (but remains currently selected). The ‘DELETE’ legend on the button changes to ‘SAVE’.

Requirement Ref. F.BL.ZOOM.06 Associated Procedures Previous Retrieve Zoom | Store Zoom Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution not implemented (May 2007)

5.4.1.6 Offset centre Procedure

Offset Centre.1 Objective To offset the situation display centre Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The ZOOM TOOL is available Dialogue Action Result 1. Single Click AB on the CENTRE

button

1. The button is shown as depressed. The cursor changes to the recentring cursor form.

2. Single Click AB on any point of the radar window

2. The composite situation display is redrawn centred on the designed point. The CENTRE button returns to the undepressed state. The cursor reverts to the normal pointing form.

Requirement Ref. F.BL.ZOOM.07 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Procedure

Offset Centre.2 Objective To offset the situation Display centre Actors RWY Controller | GND Controller Trigger Controller Decision Pre-condition - Dialogue Action Result 1. Single click IB

1. The cursor changes to the re-centring

cursor form.

2. Press and Drag IB on any point of the radar window

2. On Press the composite situation display is captured at the designed point. On Drag the captured point follows the re-centring cursor. The map is redrawn following the cursor displacement.

3. Release IB 3. The map is fully redrawn with the

selected point in the new location. The CENTRE button returns to the undepressed state. The cursor reverts to the normal pointing form.

Requirement Ref. F.BL.ZOOM.07 Associated Procedures Associated HMI Objects Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.1.7 Zoom in part Procedure

Zoom in part Objective To zoom in part of the Composite Situation Display Window. Actors RWY Controller | GND Controller Trigger Controller Decision Pre-condition The COMPOSITE SITUATION DISPLAY WINDOW is available Dialogue Action Result 1. Press and Drag IB on the

COMPOSITE SITUATION DISPLAY WINDOW

1. A rectangular wire-frame outline in Warning colour is displayed; fixed at the first clicked point. Dragging the wire-frame from this fixed point in the X and Y directions permits a two-axe delimitation of a part of the CSD window

2. Release IB 2 .

- The delimited part of the CSD image is displayed within the limits of the CSD Window, replacing the initial image.

- In the ZOOM TOOL, the slider cursor jumps to the current scale value.

- The ZOOM BACK BUTTON is displayed under the ZOOM TOOL(or under its icon). The initial image scale value is stored under the button.

- If the ZOOM BACK BUTTON is already displayed, the new image scale value is stored, replacing the previously stored one.

Requirement Ref. F.BL.ZOOM.01 Associated Procedures Following Zoom Back Previous - Associated HMI Objects Initiated by COMPOSITE SITUATION DISPLAY WINDOW Uses ZOOM TOOL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.1.8 Modify geographical orientation of situatio n display Procedure

Modify Geographical Orientation Objective To orientate the situation display according to ATC controller needs Actors RWY Controller | GND Controller Trigger Controller action Pre-condition - Dialogue Action Result 1. Press <Ctrl> and Drag SB on the

COMPOSITE SITUATION DISPLAY WINDOW

1. The geographical orientation of situation display is modified (turns on the left or on the right, depending on dragging SB).

2. Release SB.

2. The map is fully redrawn with the selected modification of geographical orientation.

Requirement Ref. F.BL.MAP.07 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by MAP SELECTION TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution Updated (May 2007)

5.4.2 Display Airport Information

5.4.2.1 Display composite video map Procedure

Display Composite Video Map Objective To display a composite (air/airport) video map on the Situation Display. To remove

a displayed airport video map. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The map selection tool is available Dialogue Action Result 1. 1. 2. 2. 3. 3. Requirement Ref. F.BL.MAP.01 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by MAP SELECTION TOOL Uses Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.2.2 Display / remove display parking names Procedure

Display / Remove Display Parking Names Objective To display (or remove display) parking names on the Composite situation display. Actors GND controller | RWY controller Trigger Controller action Pre-condition - Dialogue Action Result 1. Single click AB on the parking

stand symbol (unfilled triangle) on the CSD window, or

1. The parking stand symbol is displayed as a filled triangle (blank) and the name of the parking stand is displayed.

2. Single click AB on the parking stand symbol (filled triangle) on the CSD window

2. The name of the parking stand is removed, the parking stand symbol is displayed as an unfilled triangle.

Requirement Ref. F.BL.MAP.03 Associated Procedures Following - Previous - Associated HMI Objects Initiated by PARKING STAND SYMBOL Particularities - Evolution -

5.4.2.3 Display parking names (Quick Look) Procedure

Display Parking Names (Quick Look) Objective To have a quick and temporary look at parking names on the Composite situation

display. Actors GND controller | RWY controller Trigger Controller action Pre-condition - Dialogue Action Result 1. Move the cursor on the parking

stand symbol. 1. The parking stand symbol is displayed as a filled triangle (blank) and the name of the parking stand is displayed.

2. Move the cursor outside of the parking stand symbol.

1. The parking stand symbol is returns to an unfilled triangle (blank) and the name of the parking stand is removed

Requirement Ref. F.BL.MAP.03 Associated Procedures Following - Previous - Associated HMI Objects Initiated by PARKING STAND SYMBOL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.2.4 Set Up Runway / Taxiway Status (open / clos e) Procedure

Set Up Runway/ Taxiway Status Objective To modify the status of the runway threshold and taxiway Actors GND controller | RWY controller Trigger Controller action Pre-condition Open runway / taxiway configuration menu. Dialogue Action Result 1. Single IB on the runway surface

2. Single IB on the name of taxiway

1a. The runway status menu is displayed under the cursor with current runway status setting (for each threshold). 1b. the taxiway status menu is displayed under the cursor with current taxiway status setting.

2a. The selected RWY theshold status is highlighted and replaces the previous one. 2b. The selected TWY status is highlighted and replaces the previous one. The taxiway sector is displayed in different coulour (orange/red).

Requirement Ref. F.BL.APT.01 Associated Procedures Following Close Menu Previous Open Menu Associated HMI Objects Initiated by RUNWAY STATUS MENU | TAXIWAY STATUS MENU | MAP SELECTION

TOOL | AIRPORT SETUP TOOL | ALERT IN LABEL | ALERT WINDOW | DEP E-STRIP | ARR E-STRIP | TOWED AIRCRAFT RADAR LABEL | TOWED AIRCRAFT E-STRIP | VEHICLE RADAR LABEL | VEHICLE E-STRIP

Particularities When a change of runway/taxiway status triggers alert messages, the associated alert is displayed in the alert window, radar label and on the e-strip of the concerned aircraft or vehicle on the GND and RWY controllers’ positions..

Evolution Updated (Septembre 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.3 Display and track range and bearing between t wo points

The objective is to provide the controllers with information on range and bearing as measured from one point to another, and with estimated time of flight of an aircraft to a fixed point of the airspace. To allow the linking of several couples of points, one or both of which can be dynamic (an aircraft and a fixed point, or two aircraft), in order to permit monitoring of the change in relative range and bearing over time.

5.4.3.1 Enable Range and Bearing function Procedure

Obtain range and bearing information Objective To obtain range and bearing information as measured from one point of the

airspace to another, and the estimated time of flight of an aircraft to a fixed point of the airspace.

Actors GND controller | RWY controller Trigger Controller action Pre-condition The range and bearing function is not active Dialogue Action Result 1. Single click AB on the CSD

window, outside of a selectable object.

1. The cursor changes to the sighting cursor form.

2. Move the cursor 2. A continuous readout of distance and bearing from the fixed point is displayed immediately below the sighting cursor.

3. Single Click AB on the CSD Window, outside of a selectable object

3. A new point of origin is drawn at the pointed location, the readout is updated according to the new point of origin.

Requirement Ref. F.BL.RB.01 | F.BL.RB.05 Associated Procedures Following Create Range and Bearing Track | Cancel Range and B earing Track Previous Express time to go to airspace point Associated HMI Objects Uses RANGE and BEARING TRACKER LINK Initiated by COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution Not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.3.2 Cancel Range and Bearing function

Procedure Cancel Range and Bearing function

Objective To cancel the Range and Bearing function Actors GND controller | RWY controller Trigger Controller decision Pre-condition The Range and Bearing function is active Dialogue Action Result 1. Single click IB on the CSD

window, outside of a selectable object.

1 - The cursor reverts to the normal pointing form. The point of origin, the elastic vector, the range and bearing readout, if any, are removed.

Requirement Ref. H.BL.RB.02 Associated Procedures Previous Obtain range and bearing information Associated HMI Objects Uses RANGE and BEARING TRACKER LINK Initiated by COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution Not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.3.3 Create Range and Bearing Track

Procedure Create Range and Bearing Track

Objective To obtain continuous readout over time of the relative range and bearing between two points, one or both of which are dynamic (an aircraft and a fixed point, or two aircraft). To obtain continuous readout over time of the estimated time of flight of an aircraft to a fixed point of the airspace.

Actors GND controller | RWY controller Trigger Controller decision Pre-condition The tracker function is not active Dialogue Action Result 1. Single click AB on a selectable

object (i.e. aircraft or waypoint symbol)

1. The cursor changes to the sighting cursor form. A point of origin is drawn at the pointed location and an elastic vector is created between this cross and any subsequent position of the cursor.

2. Move the cursor 2. A continuous readout of distance and bearing from the fixed point is displayed immediately below the sighting cursor.

3. Single Click AB on another selectable object (aircraft or waypoint symbol).

3. The cursor reverts to the normal pointing form. The selected objects are redrawn in RangeBearing colour. The elastic vector connects the two points and continues to do so as the radar updates. The range and bearing of the second object from the first is displayed at the second object.

Requirement Ref. F.BL.RB.02 | F.BL.RB.05 Associated Procedures Previous Obtain range and bearing information | Express time to go to airspace point Following Cancel Range and Bearing Track Associated HMI Objects Initiated by RADAR TRACK | COMPOSITE SITUATION DISPLAY WINDOW Uses RANGE and BEARING TRACKER LINK Particularities - Evolution Not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.3.4 Cancel Range and Bearing Track

Procedure Cancel Range and Bearing Track

Objective To cancel the display of a particular range and bearing readout between two points. Actors GND controller | RWY controller Trigger Controller action Pre-condition A tracker link has been previously created and is displayed. Dialogue Action Result 1. Single Click IB on the range and

bearing readout 1. The elastic vector and the range and bearing

readout (and ETO if displayed) are removed. The selected objects revert to their normal colour coding.

Requirement Ref. H.BL.RB.05 | F.BL.RB.04 Associated Procedures Previous Create Range and Bearing Track Associated HMI Objects Initiated by RANGE and BEARING TRACKER LINK Particularities - Evolution Not implemented (May 2007)

5.4.3.5 Express Time to Go to airspace point Procedure

Express time to go to airspace point Objective To express the estimated time of flight of an aircraft to a fixed point of the airspace either

as an estimate or as 'time to go' to that point. Actors GND controller | RWY controller Trigger Controller action Pre-condition - Dialogue Action Result 1. Single Click AB on the 'ETO'

or 'Time to go' toggle button. 1 - The button is redrawn as depressed. - The other depressed button is released. - On subsequent display of the range and bearing /

tracker link, the time of flight is displayed in the chosen format.

Requirement Ref. H.BL.RB.10 Associated Procedures Previous Access Tool Following Obtain range and bearing information | Create Range and Bearing Track Associated HMI Objects Uses RANGE and BEARING TRACKER LINK Initiated by RANGE AND BEARING TOOL Particularities - Evolution Not implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.4.4 Access time information

5.4.4.1 Display Time Procedure

Display Universal Time Objective To display the current UTC time on the controller HMI. Actors RWY Controller | GND Controller Trigger Time update Pre-condition - Dialogue Action Result 1. The clock time is updated 1. The time displayed on the Clock button

is updated with the precision of 1 second.

Requirement Ref. F.BL.TIME.01 | H.BL.TIME.01 Associated Procedures Associated HMI Objects Uses CSD TOOLBOX WINDOW | CLOCK WINDOW Particularities - Evolution Updated (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5 MANAGE THE DISPLAY FEATURES OF TRAFFIC REPRESEN TATION

5.5.1 Manage the Radar Labels

5.5.1.1 Configure Radar Labels Content Procedure

Configure radar labels content Objective To configure the content of all radar labels, i.e. to display supplementary data in

either the minimum and selected, or only the selected format of all radar labels, or to remove displayed supplementary data from all radar labels.

Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The LABEL CONFIGURATION TOOL is available Dialogue Action Result 1a. Single Click AB on a text

acquisition area or on the associated switch button in the ‘Min’ column

Or

� If the option is not selected, the state of the switch buttons in ‘Min’ column is set to ON. � The selected supplementary data is displayed (if available) at the relevant location in Minimum label. � If the option is already selected, the state of the switch button is set to OFF (the tick mark is removed) in the ‘Min’ column.

1b. Single Click AB on a switch button in the ‘Sel’ column

� If the option is not selected, the state of the switch button in the ‘Sel’ column is set to ON. � The selected supplementary data is displayed (if available) at the relevant location in the Selected format of all the labels. � If the option is already selected in the ‘Sel’ column the state of the switch button is set to OFF. � The data corresponding to the de-selected option is removed from selected formats of all the labels. � If the option is already selected in the ‘Sel’ column only, the state of the switch button is set to OFF in that column. �

Requirement Ref. F.BL.LBL.01 | F.BL.LBL.03 | F.BL.LBL.02 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by LABEL CONFIGURATION TOOL Uses RADAR LABEL | VEHICLE RADAR LABEL | TOWED AIRCRAFT RADAR

LABEL Particularities - Evolution Updated (Nov 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.2 Manage the Electronic Flight Strips (EFS, e-s trip)

5.5.2.1 Configure the EFS content Procedure

Configure EFS content Objective To configure the content of EFS, i.e. to display supplementary data in either the

minimum and selected, or only the selected format of all EFS, or to remove displayed supplementary data from all EFS.

Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The EFS CONFIGURATION TOOL is available Dialogue Action Result 1a. Single Click AB on a text

acquisition area or on the associated switch button.

� If the option is not selected, the state of the switch buttons is set to ‘ON’. � The selected supplementary data is displayed (if available) at the relevant location in Minimum label. � If the option is already selected, the state of the switch button is set to ‘OFF’ (the tick mark is removed) in the column.

Requirement Ref. F.BL.SIL.03 | F.BL.SIL.04 | F.BL.SIL.05 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by EFS CONFIGURATION TOOL Uses DEP E-STRIP| ARR E-STRIP | VEHICLE E-STRIP | TOWED AIRCRAFT E-STRIP Particularities - Evolution Updated (November 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.2.2 Move an EFS Procedure

Move an EFS Objective To move an EFS Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The EFS CONFIGURATION TOOL is available Dialogue Action Result 1a. Single Click AB on the square

box on the left of the EFS.

� If the option is not already selected - filled square - , the state is set to ‘selected’ (the square is unfilled) indicating the controller that the EFS has been moved. � A blank shape representing the EFS is drawn.

2a. Move the EFS (drag an drop) within a bay.

� The EFS is moved

Requirement Ref. F.BL.LBL.01 | F.BL.LBL.03 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by EFS CONFIGURATION TOOL Uses DEP E-STRIP| ARR E-STRIP | VEHICLE E-STRIP | TOWED AIRCRAFT E-STRIP Particularities - Evolution Updated (Dec. 2008)

5.5.3 Manage air tracks and labels

5.5.3.1 Display speed vectors Procedure

Display Speed Vectors Objective To display (or remove display) speed vectors for all air radar tracks Actors RWY Controller Trigger Controller action Pre-condition The SPEED VECTOR and TRACK HISTORY TOOL is available. Dialogue Action Result 1. Single Click AB on the

corresponding radio button of the speed vector function

1. The radio button is redrawn as depressed;

Requirement Ref. F.BL.VECT.01 | F.BL.VECT.02 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by SPEED VECTOR and TRACK HISTORY TOOL Uses RADAR TRACK Particularities Selecting the ‘0’ value removes the speed vectors. Evolution not implementented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.3.2 Set speed vectors value Procedure

Set Speed Vectors Value Objective To select a speed vector value for all the displayed air radar tracks. Actors RWY Controller Trigger Controller action Pre-condition The SPEED VECTOR and TRACK HISTORY TOOL is available. Dialogue Action Result 1 - Single Click AB on a radio button

of the speed vector function 1. The radio button is redrawn as

depressed; any other possible depressed button in that function is released. A speed vector corresponding to the selected value is displayed for all the displayed air radar tracks.

Requirement Ref. F.BL.VECT.01 | H.BL.VECT.02 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by SPEED VECTOR and TRACK HISTORY TOOL Uses RADAR TRACK Particularities Selecting the ‘0’ value removes the speed vectors. Evolution not implemented (May 2007)

5.5.3.3 Set track history value Procedure

Set Track History Value Objective To set a track history value for all the displayed radar tracks. Actors RWY Controller Trigger Controller action Pre-condition The SPEED VECTOR and TRACK HISTORY TOOL is available. Dialogue Action Result 1. Single Click AB on a radio button

of the Track history function

1. The button is redrawn as depressed; any other depressed button in that function is released. The number of track positions corresponding to the selected value is displayed for all the displayed aircraft tracks.

Requirement Ref. F.BL.TRCK.04 Associated Procedures Previous Access Tool Associated HMI Objects Initiated by SPEED VECTOR and TRACK HISTORY TOOL Uses RADAR TRACK Particularities Selecting the ‘0’ value removes all the history dots. Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.4 Manage label position

5.5.4.1 Deconflict labels automatically Procedure

Deconflict Labels Automatically Objective To activate the automatic radar label anti-overlap algorithm. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The Label Overlap Management Tool (or its icon) is available. The automatic radar

label de-confliction algorithm is de-activated (the ‘AUTO’ toggle button is in the OFF state).

Dialogue Action Result 1 - Single Click AB on the ‘AUTO’

toggle button 1 - The state of the toggle button is set to

ON. The previously stored label position values in the automatic mode are restored. The Radar Label anti-overlap algorithm is activated: the Radar Labels (excepting the individually moved labels) are immediately taken into account by the algorithm, and progressively move to their 'rest positions' (the 'rest position' is the label position defined in the tool while in the automatic mode, to which the algorithm tends to move the label and maintains it at that location as long as it does not generate any overlap conflict.).

Requirement Ref. F.BL.POS.01 | H.BL.POS.01 Associated Procedures Previous Deconflict Labels Manually Following Resume Label Position Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.4.2 Deconflict labels manually Procedure

Deconflict Labels Manually Objective To de-activate the automatic radar label de-confliction algorithm, and to take

manual control of the position of all the labels. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The Label Overlap Management Tool is available. The automatic Radar Label de-

confliction algorithm is activated (the ‘AUTO’ toggle button is in the ON state). Dialogue Action Result 1 - Single Click AB on the ‘AUTO’

toggle button 1 - The state of the toggle button is set to

OFF. The previously stored label position values in the manual mode are restored. The radar Labels (excepting the individually moved labels) are redrawn in conformance with the stored label position values for the manual mode. The radar Label anti-overlap algorithm is deactivated.

Requirement Ref. F.BL.POS.01 Associated Procedures Previous Access Tool Following Deconflict Labels Automatically | Resume Label Position Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL | CSD TOOLBOX WINDOW Uses RADAR LABEL | RADAR TRACK Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.4.3 Set label leader direction Procedure

Set Leader Direction Objective To change the label direction relative to the aircraft or vehicle track symbol. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The Label Overlap Management Tool is available. Dialogue Action Result 1 - Single Click AB on a radio button

setting the Radar Label direction within the currently selected frame of reference

1. The button is redrawn as depressed; in the manual mode, the selected subset of radar labels is redrawn in the appropriate position. In the automatic mode, the selected position is used by the algorithm as ‘rest position’ of the labels (the rest position of the label is the position to which the algorithm tends to move the label and maintains it at that location as long as it does not generate any overlap conflict).

Requirement Ref. F.BL.POS.02 | F.BL.POS.04 Associated Procedures Previous Set Fixed Reference | Set Track as a Reference Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL | RADAR TRACK Particularities - Evolution Updated (May 2007)

5.5.4.4 Set leader length Procedure

Set Leader Length Objective To change the length of the leader line of all the radar labels (vehicles and aircraft). Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The Label Overlap Management Tool is available. Dialogue Action Result 1. Single Click AB on a radio button

setting the Leader line length within the currently selected frame of reference

1. The button is redrawn as depressed; any other depressed button in that region is released. The selected subset of Radar Labels is redrawn with the leader line of the selected length value.

Requirement Ref. F.BL.POS.02 | F.BL.POS.05 Associated Procedures Previous Set Fixed Reference | Set Track as a Reference Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL | RADAR TRACK Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.4.5 Set fixed reference Procedure

Set Fixed Reference Objective To set the top of the screen as reference for the orientation of the radar labels. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The Label Overlap Management Tool is available. Dialogue Action Result 1. Single Click AB on the ‘top of

screen’ option 1. The ‘top of screen’ option is selected.

The LABEL OVERLAP MANAGEMENT TOOL is redrawn accordingly to the 'Screen' option selection. The previously stored label position values for the ‘Screen’ option are restored. The selected subset of radar Labels is redrawn in conformance with the stored label position values for that option.

Requirement Ref. F.BL.POS.02 | F.BL.POS.03 Associated Procedures Following Set Leader Length | Set Leader Direction Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL Particularities - Evolution not implemented (May 2007)

5.5.4.6 Set track as a reference Procedure

Set Track as a Reference Objective To set an aircraft track as the reference for the orientation of the radar labels. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The Label Overlap Management Tool is available. Dialogue Action Result 1. Single Click AB on the ‘Track’

option

1. The ‘Track’ option is selected. The Label Overlap Management Tool is redrawn accordingly to the ‘Track’ option selection. The previously stored label position values for the ‘Track’ option are restored. The selected subset of radar Labels is redrawn in conformance with the stored label position values for that option.

Requirement Ref. F.BL.POS.02 | F.BL.POS.03 Associated Procedures Following Set Leader Length | Set Leader Direction Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.4.7 Move radar babel Procedure

Move Radar Label Objective To allow a manual positioning of a radar label so that make it free of overlap with

other objects displayed on the composite situation display window. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The cursor is positioned over the radar label (i.e. the radar label is in the selected

format). Dialogue Action Result 1. Press and Hold AB on a radar

label, then move the mouse pointer cursor anywhere on the CSD window.

1. The radar label follows the cursor motion. The leader line automatically adapts its length and position to maintain the link between the label and the traffic position symbol.

2. Release AB 2. The radar label stays in the last reached position, and remains in the same position relative to the radar track, until the label is individually moved again, or the ‘resume’ option (ref. Resume Label Position procedure) is selected.

Requirement Ref. F.BL.POS.06 Associated Procedures Previous Select Traffic Following Resume Label Position Associated HMI Objects Initiated by RADAR LABEL Uses RADAR TRACK Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.4.8 Resume label position Procedure

Resume Label Position Objective • To provide the possibility to easily access additional information concerning

vehicles on controller request. To put the individually moved labels in conformance with the global label position setting defined within the Label Overlap Management Tool. • To take individually moved labels off the global label position setting defined in the Label Overlap Management Tool, so that they stay in the controller-defined position.

Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The Label Overlap Management Tool is available. Dialogue Action Result 1. Single Click AB on the ‘resume’

radio button in region 2. 1. The button is redrawn as depressed;

any other depressed button in that region is released. In the manual mode, any previously manually moved label moves back to the position defined in the Label Overlap Management Tool. In the automatic mode, any previously manually moved label is immediately taken into account by the algorithm, and progressively moves to its 'rest position'.

Requirement Ref. F.BL.POS.08 Associated Procedures Previous Deconflict Labels Automatically | Deconflict Labels Manually | Move Radar

Label Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL | RADAR TRACK Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.5 Draw attention to a particular aircraft or ve hicle

5.5.5.1 Input intra-CWP traffic marking Procedure

Input intra-CWP traffic marking Objective To input a marking (local to CWP) on an aircraft or vehicle. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The traffic radar label or the corresponding e-strip is available. No intra-sector

warning is currently input on the aircraft or vehicle. Dialogue Action Result 1a. Single Click AB on ‘MARK’ option

in the callsign menu wherever presented, or

1b. Single Click AB on the marking

field of the corresponding e-strip (‘M’)

1a or 1b a) A square in ‘marked’ colour is drawn in

the radar label on the right side of the C/S.

b) The ‘UNMARK’ option replaces the ‘MARK’ option in the callsign menu.

c) ‘UM’ replaces ‘M’ in the e-strip. The Runway and ‘UM’ are displayed in ‘marked’ colour.

Requirement Ref. H.BL.WAR.01 Associated Procedures Previous Select Traffic Following Unmark Traffic | Share marking with next CWP | Share marking with all CWPs Associated HMI Objects Initiated by RADAR TRACK | EXTENDED RADAR LABEL | DEP E-STRIP| ARR E-STRIP |

VEHICLE E-STRIP | TOWED AIRCRAFT E-STRIP Particularities - Evolution Updated (November 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.5.2 Share marking with next CWP Procedure

Share marking with next CWP Objective To share an intra-sector warning (internal to a sector) marking on an aircraft or

vehicle with the next sector controller unit. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The track position symbol of the traffic is available, or the e-strip or the extended

radar label is available. An intra-sector marking has been input on the aircraft or vehicle.

Dialogue Action Result 1. Single Click AB on ‘MARK NEXT’

in the lower toolbar.

1. A ring in Warning colour is drawn around the position symbol of the aircraft or vehicle, shared with the next sector control unit (if any).

Requirement Ref. F.BL.WAR.02 Associated Procedures Previous Select Traffic | Input intra-CWP traffic marking Following Unmark Traffic | Share marking with all CWPs Associated HMI Objects Initiated by RADAR TRACK | EXTENDED RADAR LABEL | DEP E-STRIP| ARR E-STRIP Particularities - Evolution not implemented (May 2007)

5.5.5.3 Share marking with all CWPs Procedure

Share marking with all CWPs Objective To share an intra-sector warning (internal to a sector) marking on an aircraft or

vehicle with the next sector controller unit. Actors RWY Controller | GND Controller Trigger Controller action Pre-condition The track position symbol of the traffic is available, or the e-strip or the extended

radar label is available. A traffic marking (local to CWP) has been input on the aircraft or vehicle.

Dialogue Action Result 1. Single Click AB on ‘MARK ALL’ in

the lower toolbar.

1. A double ring in Warning colour is drawn around the position symbol of the aircraft or vehicle, shared with all CWPs.

Requirement Ref. F.BL.WAR.02 Associated Procedures Previous Select Traffic | Input intra-CWP traffic marking Following Unmark Traffic Associated HMI Objects Initiated by RADAR TRACK | EXTENDED RADAR LABEL | DEP E-STRIP| ARR E-STRIP Particularities - Evolution not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.5.5.4 Unmark traffic Procedure

Unmark Traffic Objective To remove manually an traffic marking displayed on an aircraft or vehicle. Actors Trigger Controller action (manual) or System generated (after traffic transfer completed) Pre-condition A marking (shared or not shared) has been input on a traffic (aircraft or vehicle) Dialogue Action Result 1a. Single Click AB on ‘UNMARK’

option in the callsign menu wherever presented, or

1b. Single click ‘UM’ in the corresponding e-strip, or 1.c Single click on the green square in the label

1d. The planning state has changed to ‘not concerned’.

1a, 1b, and 1c. The marking is removed

Requirement Ref. F.BL.WAR.03 Associated Procedures Previous Input intra-CWP traffic marking | Associated HMI Objects Initiated by RADAR TRACK | EXTENDED RADAR LABEL | DEP E-STRIP| ARR E-STRIP |

VEHICLE RADAR LABEL | RADAR LABEL | VEHICLE E-STRIP Particularities - Evolution Updated (November 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6 ACCESS DATA CONCERNING THE TRAFFIC SITUATION

5.6.1 Access aircraft / vehicle representation

5.6.1.1 Display traffic representation Procedure

Display Traffic Representation Objective To provide the controllers with a clear representation of the traffic and provide

updates of this representation. Actors Surveillance System Trigger System generated Pre-condition The radar track is detected by the Surveillance System Dialogue Action Result 1. The traffic enters the CSD window

display boundary 1. The traffic representation is displayed

on the situation display(s) with the radar label in the Minimum format

2. The traffic (aircraft or vehicle) position in the horizontal plane is modified

2. The representation of the traffic position in the horizontal plane is updated accordingly on the Composite Situation Display window(s) of the controller position.

3. The aircraft position in the vertical plane is modified (altitude)

3. The representation of the aircraft position in the vertical plane is updated accordingly (i.e. the altitude field of the radar label is updated) on the controller position.

4. Any system or controller initiates update of traffic data

4. The traffic representation is updated.

Requirement Ref. F.BL.TRAF.01 | F.BL.TRAF.02 | F.BL.TRAF.03 Associated Procedures Following Select Traffic | Remove Traffic Representation Associated HMI Objects Uses RADAR TRACK | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.1.2 Remove traffic representation Procedure

Remove Traffic Representation Objective To inform the controller that a traffic has left the CSD window display boundary. Actors Surveillance System Trigger System Generated; The traffic leaves the CSD window display boundary Pre-condition The traffic representation exists and is displayed. Dialogue Action Result 1. The aircraft leaves the CSD

window display boundary 1. The representation of the traffic is

removed from the CSD window(s) of the controller position.

Requirement Ref. F.BL.TRAF.01 | F.BL.TRAF.02 | F.BL.TRAF.03 Associated Procedures Previous Display Traffic Representation Associated HMI Objects Uses RADAR TRACK | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.1.3 Select traffic Procedure

Select Traffic Objective To highlight an aircraft or vehicle representation via selection, to localise it, to

examine or to modify data. Actors RWY Controller | GND controller Trigger The controller moves the cursor onto any traffic representation. Pre-condition The traffic representation exists and is displayed on the composite situation

display. The Radar Label is displayed in the Minimum format. Dialogue Action Result 1. Move the cursor pointer on a

representation of an aircraft or vehicle.

1. All the traffic representations are highlighted:

aircraft : � The radar label is displayed in the minimum+selected (min+sel) format with additional fields � The radar track components (position symbol, trail dots, speed vector) are highlighted � All other traffic representations are highlighted � The content of the Extended Radar Label Window is highlighted vehicle : � The radar label is displayed in the minimum+selected (min+sel) format with additional fields � All other traffic representations are highlighted � The content of the Extended Radar Label Window is highlighted

2. Move the cursor pointer on one of the interactive fields of the selected object

2. The selected field is highlighted

Requirement Ref. F.BL.LBL.01 | H.BL.TRAF.04 Associated Procedures Previous Display Traffic Representation Following Associated HMI Objects Initiated by RADAR TRACK | RADAR LABEL | EXTENDED RADAR LABEL | RUNWAY

CONFLICT ALERT MESSAGE | ARR E-STRIP | DEP E-STRIP Particularities � The label is selected only if the cursor remains within the label acquisition area

longer than a parameter time. � During the selection, the selected object remains stationary. � Where two radar labels overlap, the label that is selected/highlighted is the label whose acquisition area the mouse pointer first entered, or the label with the highest priority. To select another label the cursor must exit the initially selected label. � Moving the cursor pointer on a non-interactive field has no highlighting effect on that field. � Ideally, the label should only be selected by active cursor movement, i.e. should not be selected if the moving track and label are moved under the cursor.

Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.1.4 Deselect Traffic Procedure

Deselect Traffic Objective To unhighlight a traffic representation by deselecting the aircraft or vehicle Actors RWY controller | GND controller Trigger The controller moves the cursor out of the selected traffic representation (i.e.

Radar Track, Radar Label, Extended Radar Label, or any other existing representation).

Pre-condition The traffic is selected (all the traffic representations are highlighted). Dialogue Action Result 1. Move the cursor pointer out of the

selected representation of the traffic.

1. � All the representations of the traffic are unhighlighted: � The radar label reverts to its Minimum format. � The radar track components revert to their normal colour. � Other representations related to the selected traffic revert to their normal unhighlighted presentation. � The content of the Extended Radar Label Window reverts to its normal unhighlighted presentation.

2. Move the cursor pointer out of the interactive field of the object

2. The selected field is unhighlighted

Requirement Ref. F.BL.SEL.01 Associated Procedures Previous Select Traffic Following - Associated HMI Objects Initiated by RADAR LABEL | RADAR TRACK | EXTENDED RADAR LABEL | DEP E-

STRIPARR E-STRIP Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.1.5 Display extended label Procedure

Display Extended Label Objective To display extended label information concerning an aircraft or vehicle in a fixed

format. Actors RWY controller | GND controller Trigger Controller action Pre-condition The aircraft or vehicle is selected. Dialogue Action Result 1. Single Click IB on the ‘callsign’

field of an aircraft or vehicle wherever presented (e.g. radar label, electronic strip etc.)

1. � If the Extended radar label window is not displayed, it opens at its default position, or at its last display position. The Extended Radar Label data is displayed in the window. � If the Extended Radar Label Window is already displayed, the Extended Radar Label data of the selected traffic overwrites the previous content of the window. note : during the Extended Radar Label display in the Extended Radar Label Window, the displayed data is updated following data modifications and surveillance system updates.

Requirement Ref. F.BL.LBL.01 Associated Procedures Previous Select Traffic Following - Associated HMI Objects Initiated by RADAR LABEL | DEP E-STRIP | ARR E-STRIP Uses EXTENDED RADAR LABEL | EXTENDED RADAR LABEL WINDOW Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.1.6 Display extended label (Quick Look) Procedure

Display Extended Label (Quick Look) Objective To display extended label information concerning an aircraft or vehicle in a quick

look format. Actors RWY controller | GND controller Trigger Controller action Pre-condition The aircraft or vehicle is selected. Dialogue Action Result 1. Press and Hold IB on the ‘callsign’

field of an aircraft or vehicle wherever presented (e.g. radar label, electronic flight strip, etc. )

1. The Extended Radar Label data is displayed at the location of the callsign, so that the callsign is maintained at the same position.

note : During the display, the data is updated following data modifications and Surveillance System updates

2. Release IB 2. The Extended Radar Label data is removed.

Requirement Ref. H.BL.TRAF.04 Associated Procedures Previous Select Traffic Following - Associated HMI Objects Initiated by RADAR LABEL | DEP E-STRIP | ARR E-STRIP Uses EXTENDED RADAR LABEL Particularities � The Extended Radar Label can be displayed simultaneously for two different

traffic, one in the ‘quick look’ mode, and the second in the ‘fixed’ mode. � Interaction with the temporarily displayed Extended Radar Label data is not possible.

Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.1.7 Display additional CSD sub-view Procedure

Display additional CSD sub-view Objective To display an additional sub-view in the CSD window Actors RWY controller | GND controller Trigger Controller action Pre-condition The CSD SUB-VIEWS TOOL is open and less than 2 additional views have already

been created by the controller. Dialogue Action Result 1. Single click AB in one of the two

acquisition areas linked to ‘view_1’ or ‘view_2’.

1. an additional CSD window subview is created within the CSD window (picture in picture)

Requirement Ref. F.BL.VIEW.01 | F.BL.VIEW.02 Associated Procedures Previous - Following Close window | Come on top window | Move window | Re-size window Associated HMI Objects Initiated by CSD SUB-VIEWS TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution Updated (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.1.8 Display EFS section Procedure

Display EFS section Objective To display an EFS section Actors RWY controller | GND controller Trigger System generated ; triggering conditions are as follows :

a) GND Controller 1) Pending departures section: at least one flight is ‘n’ minutes before its EOBT (local parameter, set to 2 minutes in ITWP prototype). 2) Start up section: at least one flight is displayed in the GND pending departures section. 3) Pushback section: at least one flight is displayed in the GND pending departures or start-up section and if the stand is a contact stand (i.e. the aircraft will need pushback). 4) Taxi-out section: at least one flight is displayed in the start-up or pushback section. 5) Pending arrivals section: at least one flight is assumed by the RWY controller for which the GND controller is the next operator role concerned by the flight. 6) Taxi in section: at least one arrival flight is displayed in the pending arrivals section (GND role). 7) Transfer to RWY section: at least one arrival flight is displayed in the taxi-out section (GND role).

b) RWY Controller 1) Pending Departures Section: at least one departure flight – planed to take-off from managed RWY - is given ‘pushback’ or (first) ‘taxi’ clearance. 2) Holding Point Section: at least one departure flight is assumed by the RWY controller. 3) Pending Arrivals Section: at least one flight is less than ‘n’ minutes (local parameter, set to 20 in ITWP prototype) before ELDT or a Go-Around order has been issued by the RWY controller. 4) Final Section: at least one flight is displayed in the (RWY) Pending Arrivals section or in the RWY Final section or a go-around controller has been issued by the RWY controller. 5) RWY Section: at least one flight is displayed in the (RWY) Final Section or if a go-around instruction has been issued by the RWY controller (arrivals flights); or if at least one aircraft is displayed in the pending departures section. 6) Taxi-in Section: at least one arrival flight is displayed in the RWY section. 7) Airborne Section: at least one flight is displayed in the RWY section (either above or below the RWY divider) or if there is a go-around flight. Sections remain open as soon as above conditions are fulfilled or there is at least one displayed flight in the corresponding section. By default , groups of sections are presented to the controller, depending of the operator role, control responsibility and RWY configuration. - By default, are presented to the GND Controller: Pending departures section, start up, pushback, taxi-out, pending arrivals, taxi in, transfer to runway sections - By default, are presented to the RWY controller (for each runway for which the RWY controler is responsible): pending departures, holding point, pending arrivals, final, RWY, taxi in and airborne sections.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Pre-condition - Dialogue Action Result 1. The system detects that the pre-

conditions above are fulfilled. 1. The corresponding section is displayed open on the CSD window.

Requirement Ref. F.BL.SIL.01 | F.BL.SIL.02 Associated Procedures Previous - Following - Associated HMI Objects Uses GND PENDING ARRIVALS SECTION | GND PUSHBACK SECTION | GND TAXI

IN SECTION | GND TRANSFER TO RWY SECTION | GND PENDING DEPARTURES SECTION | GND START-UP SECTION | GND TAXI-OUT SECTION | RWY FINAL SECTION | RWY HOLDING POINT SECTION | RWY PENDING ARRIVALS SECTION | RWY PENDING DEPARTURES SECTION | RWY SECTION | RWY TAXI IN SECTION | RWY AIRBORNE SECTION


5.6.1.9 Hide EFS Bay Procedure

Hide EFS Bay Objective To end display and EFS section Actors RWY controller | GND controller | CLD controller Trigger Controller action Pre-condition EFS bays are already displayed on the CSD window Dialogue Action Result 1. Single Click AB on the white cross

in the RWY header (RWY role) or GND Pushback section (GND role) or CLD active section (CLD role)

1. The corresponding bay is no more displayed on the CSD window.

Requirement Ref. F.BL.SIL.01 | F.BL.SIL.02 Associated Procedures Previous Display EFS section Following - Associated HMI Objects Uses GND PENDING ARRIVALS SECTION | GND PUSHBACK SECTION | GND TAXI

IN SECTION | GND TRANSFER TO RWY SECTION | GND PENDING DEPARTURES SECTION | GND START-UP SECTION | GND TAXI-OUT SECTION | RWY FINAL SECTION | RWY HOLDING POINT SECTION | RWY PENDING ARRIVALS SECTION | RWY PENDING DEPARTURES SECTION | RWY SECTION | RWY TAXI IN SECTION | RWY AIRBORNE SECTION

Particularities It is possible to hide all the e-strips via EFS TOOL by selecting not visible Evolution Not implemented (November 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2 Update Traffic Situation Data

5.6.2.1 Input “En Route Clearance”

Procedure Input CLR

Objective To provide the controller with the possibility to input an En-Route Clearance a flight Actors CLD controller Trigger Controller action Pre-condition The ‘CLR’ clearance option for a departure is available in the callsign menu / e-

strip. This option is only available to the CLD controller, when the flight is in pending planning state (sub-state: pending in).

Dialogue Action Result 1a. Single click AB on the ‘CLR’

option in the callsign menu, or

1b. Single click AB on the ‘CLR’ option on the e-strip

1. The callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. 2. The e-strip is still displayed in the CLD Active section of the Outbound bay (CLD role). 3. ‘Start’ (most probable option – Start up) is the only available option in the callsign menu and e-strip clearance fields.

Requirement Ref. F.BL.ORD.14 Associated Procedures Following Input Start-Up Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution Updated (June 07)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.2 Input “En Route Clearance via data link” Procedure Input DCLR

Objective To provide the controller with the possibility to input an En-Route Clearance a flight Actors CLD controller Trigger Controller action Pre-condition The ‘CLR’ clearance option for a departure is available in the callsign menu / e-

strip. This option is only available to the CLD controller, when the flight is in pending planning state (sub-state: pending in).

Dialogue Action Result 1a. Single click AB on the ‘DCLR’


1b. Single click AB on the ‘DCLR’ option on the e-strip

1. The callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. 2. The e-strip is still displayed in the CLD Active section of the Outbound bay (CLD role). 3. ‘Start’ (most probable option – Start up) is the only available option in the callsign menu and e-strip clearance fields

Requirement Ref. F.BL.ORD.14 Associated Procedures Following Input Start-Up Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution Updated (June 07)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.3 Input “Start Up” Note: This procedure is applicable if GND controller gives ‘start –up’ clearance.

Procedure Input Start-Up

Objective To provide the controller with the possibility to input a ‘start-up’ engines for a flight Actors GND controller | CLD Controller Trigger Controller action Pre-condition The ‘start-up’ clearance option for a departure is available in the callsign menu / e-

strip. This option is only available to the GND controller, when the flight is in pending planning state (sub-state: pending in).

Dialogue Action Result 1a. Single click AB on the ‘start-up’


1b. Single click AB on the ‘start-up’ option on the e-strip

1a or 1b. - The flight is assumed (i.e. transition from Pending to Assumed planning state). - The flight is moved to the Start-Up section of the Departure bay - Available clearance options are ‘Pushback’, ‘Taxi’ or Hold’.

Requirement Ref. F.BL.ORD.07 Associated Procedures Following Input Pushback | Input Hold | Input Taxi Previous - Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.4 Input “Pushback” Procedure

Input Pushback Objective To provide the controller with the possibility to input a push back order Actors GND controller Trigger Controller action Pre-condition The ‘pushback’ clearance option for an arrival flight is available in the callsign

menu / e-strip. This option is only available to the GND controller, when the flight is either in pending state (sub-state: pending in) or is assumed (sub-state: no value).

Dialogue Action Result 1a. Single click AB on the ‘Pushback’


1b. Single click AB on the ‘Pushback’ option on the e-strip

1a or 1b. - The flight is assumed by the GND controller if not assumed yet (via previous ‘Assume’ input clearances). - The flight moves within the Departure bay from Pending Dep section to the Pushback section. - Available clearances are ‘Taxi’, ‘Stop at’ and ‘Hold’.

Requirement Ref. F.BL.ORD.08 Associated Procedures Following Input Taxi | Input Hold | add stop at Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities Note: the ‘Start up’ clearance is not available on the current GND position. Evolution Updated (Dec.2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.5 Input “Taxi” Procedure Input Taxi

Objective To provide the controller with the possibility to input a taxi order Actors GND controller Trigger Controller action Pre-condition The ‘taxi’ clearance option for is available in the callsign menu / e-strip. This option

is only available to the GND controller, a) when a departure flight is assumed, either via previous ‘start-up’ (i.e. displayed in the start-up section of the Departure bay) or ‘pushback’ (i.e. displayed in the pushback section of the Departure bay) clearance; b) when an arrival flight is in pending planning state (sub-state: pending in). c) when a‘hold’ order has been input by the GND controller on a taxiing traffic (aircraft / vehicle).

Dialogue Action Result 1a. Single click AB on the ‘Taxi’

option in the callsign menu, or 1b. Single click AB on the ‘Taxi’

option on the e-strip

1a. or 1b. � departure traffic: if the departure traffic was displayed in the start up or pushback section of the departure bay: -- it is moved to the taxi-out section. -- the stand field changes to the clearance limit (normally the holding point) -- the transfer (to RWY controller) option is only available. -- The runway bay is displayed (if not already displayed). � arrival traffic: if the arrival traffic was displayed in the RWY bay of the GND controller (pending arr section) -- it is moved to the taxi-in section -- ALDT changes to EIBT in the departure e-strip field. -- the Hold option is only available. � taxiing traffic (aircraft / vehicle): if a ‘Hold’ order has been input by the GND controller when a traffic was either in the taxi-out section (Departure bay) or taxi-in section (RWY bay), then the Taxi option is available.

Requirement Ref. F.BL.ORD.06 Associated Procedures Following Input Hold | Transfer Traffic Previous Input Pushback | Input Start-Up | Input Hold Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL | VEHICLE E-

STRIP | VEHICLE RADAR LABEL | ARR E-STRIP Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.6 Input “Line up” Procedure

Input Line Up Objective To provide the controller with the possibility to input a line up order Actors RWY controller Trigger Controller action Pre-condition The line-up clearance for a departure flight is available in the callsign menu / e-

strip. This option is only available to the RWY controller, when the flight is assumed.

Dialogue Action Result 1a. Single click AB on the ‘Line up’

option in the callsign menu, or 1b. Single click AB on the ‘Line up’


1a or 1b. - The flight is moved to the RWY bay (RWY section, under the RWY divider) - The available clearance option is ‘Take-off’. - an orange dotted line is displayed in the radar label under the flight callsign (see below) and in the electronic flight strip.

Requirement Ref. F.BL.ORD.10 Associated Procedures Following Input Clear for Take-Off | Cancel order / instruction Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.7 Input “Conditional line up” Procedure

Input Conditional Line Up Objective To provide the controller with the possibility to input a conditional line up order Actors RWY controller Trigger Controller action Pre-condition The conditional line-up clearance for a departure flight is available in the callsign menu / e-

strip. This option is only available to the RWY controller, when the flight is assumed.

Dialogue Action Result 1a. Single

click AB on the ‘Conditional line up’ option in the callsign menu, or

1b. Single click AB on the ‘Conditional line up’ option on the e-strip

1a or 1b. - The flight is moved to the RWY bay (RWY section, under the RWY divider) - The available clearance option is ‘Take-off’. - an orange dotted line with a ‘C’ (Conditional line up) is displayed in the radar label under the flight callsign (see below) and in the electronic flight strip.

Requirement Ref.

F.BL.ORD.11

Associated Procedures Following Input Clear for Take-Off Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU | DEP E-STRIP Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.8 Input “Hold” Procedure Input Hold

Objective To provide the controller with the possibility to input a hold instruction to an aircraft / vehicle

Actors GND controller Trigger Controller action Pre-condition The Hold instruction is available in the callsign menu / e-strip.

Dialogue Action Result 1a. Single click AB on the ‘Hold’

option in the callsign menu, or 1b. Single click AB on the ‘Hold’


1a. or 1b. - ‘Taxi’ becomes an an available option;

- an orange crossed circle is displayed a) on the left of ‘Taxi’ option (e-strip) and b) on the left of the last row (radar label).

Requirement Ref. F.BL.ORD.09 Associated Procedures Following Input Taxi | Cancel order / instruction Previous Input Taxi Associated HMI Objects Initiated by CALLSIGN MENU | DEP E-STRIP | ARR E-STRIP | VEHICLE E-STRIP |

VEHICLE RADAR LABEL Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL |VEHICLE

RADAR LABEL | VEHICLE E-STRIP | TOWED AIRCRAFT RADAR LABEL | TOWED AIRCRAFT E-STRIP


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.9 Input “Hold at” Procedure

Input HoldAt Objective To provide the controller with the possibility to input a hold at instruction for an

arrival aircraft (e.g. for CDG airport, instruct the aircraft to hold at a holding point) . Actors RWY controller Trigger Controller action Pre-condition The ‘Hold at’ instruction is available in the callsign menu / e-strip. Dialogue Action Result 1a. Single click AB on the ‘Hold at’

instruction in the callsign menu 1b. Single click AB on the ‘Hold at’


1a. or 1b. - ‘Cross’ and ‘Enter’ become available options; - an orange crossed circle and the holding point is displayed a) on the left of ‘Cross or Enter’ option (e-strip) and b) on the left of the last row (radar label).

Requirement Ref. F.BL.ORD.09 Associated Procedures Following Input Cross RWY | Cancel order / instruction Previous Input Cleared to Land Associated HMI Objects Initiated by CALLSIGN MENU | ARR E-STRIP Uses RADAR LABEL | ARR E-STRIP Particularities - Evolution Implemented (Nov. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.10 Input “Abort take off” Procedure

Input Abort Take Off Objective To provide the controller with the possibility to input an abort take off for a flight. Actors RWY controller Trigger Controller action Pre-condition The Take-off clearance instruction has already been issued

Dialogue Action Result 1a. Single click AB on the ‘abort take

off’ option in the callsign menu, or 1b. Single click AB on the ‘abort take

off’ option on the e-strip

1a. or 1b. - The 3 green arrows pointing up (��) are no more displayed on the e-strip. - The available clearance option is ‘vacate’.

Requirement Ref. F.BL.ORD.13 Associated Procedures Following Input Vacate Previous Input Clear for Take-Off Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution Not implemented (Dec 2008)

5.6.2.11 Input “Cleared to land” Procedure

Input Cleared to Land Objective To provide the controller with the possibility to clear a flight to land. Actors RWY controller Trigger Controller action Pre-condition The ‘Cleared to land’ instruction is available in the callsign menu / e-strip.

Dialogue Action Result 1a. Single click AB on the ‘cleared to

land’ option in the callsign menu, or 1b. Single click AB on the ‘cleared to

land’ option on the e-strip

1a. or 1b. - 3 green arrows pointing up (��) are displayed on the e-strip on the left of the clearance field. - The available clearance options are ‘go around’ and ‘vacate’.

Requirement Ref. F.BL.ORD.02 Associated Procedures Following Input Actual Time of Arrival | Input Vacate | Cancel order / instruction | Input

HoldAtInput HoldAtInput HoldAtInput HoldAtInput Hol dAtInput HoldAtInput HoldAtInput HoldAt

Previous Transfer Traffic | Input Visual Circuit Associated HMI Objects Initiated by CALLSIGN MENU Uses ARR E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.12 Input “Cleared for take off” Procedure

Input Clear for Take-Off Objective To provide the controller with the possibility to clear a flight for take-off Actors RWY controller Trigger Controller action Pre-condition The Take-Off instruction is available in the callsign menu / e-strip. The flight is

displayed in the RWY section under the RWY divider.

Dialogue Action Result 1a. Single click AB on the ‘take off’

option in the callsign menu, or 1b. Single click AB on the ‘take off’


1a. or 1b. - 3 green arrows pointing up (��) are displayed on the e-strip on the left of the clearance field. - The available clearance options are ‘airborne’ and ‘abort take off’)

Requirement Ref. F.BL.ORD.12 Associated Procedures Following Input Actual Take Off Time | Input Airborne | Input Abort Take Off | Cancel

order / instruction Previous Input Line Up | Input Conditional Line Up Associated HMI Objects Initiated by CALLSIGN MENU | DEP E-STRIP Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution -

5.6.2.13 Input “Airborne” Procedure

Input Airborne Objective To provide the controller with the possibility to indicate that a departure flight is

airborne. Actors RWY controller Trigger Controller action Pre-condition The ‘Airborne’ instruction is available in the callsign menu / e-strip, i.e. a ‘Cleared

for take-off’ instruction has already been issued by the controller.

Dialogue Action Result 1a. Single click AB on the ‘airborne’

option in the callsign menu, or 1b. Single click AB on the ‘airborne’


1a. or 1b. - The departure flight moves from the runway to the airborne section. - The available options is ‘Transfer’ (to TMA)

Requirement Ref. - Associated Procedures Following - Previous Input Clear for Take-Off Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.14 Input “Go around” Procedure

Input Go Around Objective To provide the controller with the possibility to input a “go around” for a flight Actors RWY controller Trigger Controller action Pre-condition The go-around instruction for an arrival flight is available in the callsign menu / e-

strip. This option is only available to the RWY controller, when the flight is assumed and when ‘final’ or ‘continue approach’ or ‘cleared to land’ instructions has been previously issued.

Dialogue Action Result 1a. Single click AB on the ‘go around’


1b. Single click AB on the ‘go around’ option on the e-strip

1a or 1b. - The flight is moved to the ‘Airborne’ section of the transfer bay - Available clearance options are ‘Final’ (if the RWY controller chooses to keep the flight (virtual circuit)) and ‘Transfer’ (if the RWY controller chooses to hand back the flight to APP).

Requirement Ref. F.BL.ORD.03 Associated Procedures Following Input Visual Circuit | Transfer Traffic Previous Input Cleared to Land | Transfer Traffic Associated HMI Objects Initiated by CALLSIGN MENU Uses ARR E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution Not implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.15 Input “Vacate” Procedure

Input Vacate Objective To provide the controller with the possibility to input a “vacate” instruction for a

flight / vehicle cleared to cross the RWY Actors RWY controller Trigger Controller action Pre-condition The ‘Vacate’ instruction is available in the callsign menu / e-strip. This option is

only available to the RWY controller, when the flight (vehicle) is assumed: - in case of a departure flight, after ‘conditional line up’, ‘line up’ or ‘abort take off’ instruction has been given by the RWY controller. - in case of an arrival flight, after ‘cleared to land’ clearance has been issued by the controller. - in case of a vehicle, after ‘Cross’ clearance has been issued by the controller.

Dialogue Action Result 1a. Single click AB on the ‘vacate’


1b. Single click AB on the ‘vacate’ option on the e-strip

1a or 1b. the flight / vehicle moves to transfer bay / taxi in section (it has the same consequences as ‘transfer’ to the GND controller).

Requirement Ref. F.BL.ORD.04 Associated Procedures Following Input Taxi | Cancel order / instruction Previous Input Cleared to Land | Input Actual Time of Arrival | Input Cross RWY | Input

Enter Associated HMI Objects Initiated by CALLSIGN MENU Uses ARR E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL | VEHICLE E-

STRIP | VEHICLE RADAR LABEL | TOWED AIRCRAFT RADAR LABEL | TOWED AIRCRAFT E-STRIP

Particularities The GND controller can give a vacate instruction, in particular to a vehicle, when he manages the crossing / entering of the runway.


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.16 Input “Visual Circuit” Procedure

Input Visual Circuit Objective To provide the controller with the possibility to input a “visual circuit” instruction for

an arrival flight Actors RWY controller Trigger Controller action Pre-condition The ‘visual circuit’ instruction is available in the callsign menu / e-strip. This option

is only available to the RWY controller, when the flight is assumed and a go-around has been issued (the flight is then in the ‘airborne’ section).

Dialogue Action Result 1a. Single click AB on the ‘visual

circuit’ option (VIS) in the callsign menu, or

1b. Single click AB on the ‘visual circuit’ option on the e-strip

1a or 1b. the flight moves from the ‘airborne’ section to the ‘final’ section.

Requirement Ref. - Associated Procedures Following Transfer Traffic | Input Cleared to Land | Input Go Around Previous Input Go Around Associated HMI Objects Initiated by CALLSIGN MENU Uses ARR E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution Not implemented (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.17 Cancel the last given order Procedure

Cancel order / instruction Objective To provide the controller with the possibility to cancel the last given instruction to

an aircraft, vehicle or towed aircraft Actors RWY / GND controller Trigger Controller action Pre-condition The ‘-[order]’ clearance option is available in the callsign menu .

Dialogue Action Result 1a.Single click -B on the ‘-[order]’

option in the callsign menu. 2b.Sigle click IB in the square on the left of the callsign in the e-strip

1a or 1b: The last given order is cancelled. The e-strip will move back to the bay where it was before the latest clearance

Requirement Ref. F.BL.ORD.15 Associated Procedures Following Input Hold | Input Cross RWY | Input Enter Previous Input Hold | Input Cross RWY | Input Enter | Input Line Up | Input Taxi | Input

tow | Input Vacate | Input Cleared to Land | Input Clear for Take-Off Associated HMI Objects Initiated by CALLSIGN MENU Uses TOWED AIRCRAFT RADAR LABEL | RADAR LABEL | VEHICLE RADAR

LABEL Particularities Only available in the callsign menu as an option Evolution Updated (Dec. 2008)

5.6.2.18 Display Estimated Landing Time (ELDT) Procedure

Display Estimated Landing Time Objective To display the Estimated Landing Time (ELDT) Trigger System Generated Pre-condition ELDT flight data is known by the system Dialogue Action Result 1. The system detects that a

departure flight is 5 minutes from its ELDT.

1. The flight is displayed in the RWY Bay / Pending Arr section of the RWY controller with its ELDT in the Time1 arrival e-strip field. Note: ELDT is displayed in the Time1 arrival e-strip field until ‘assume’ clearance is input by the RWY controller (see ‘display time to touchdown’ procedure).

Requirement Ref. F.BL.SIL.04 Associated Procedures Following Input Assume Associated HMI Objects Initiated by - Uses ARR E-STRIP | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.19 Display Time To Touchdown (TTT) Procedure

Display Time To Touchdown Objective To display the Time To Touchdown (arrival flight) Trigger System Generated Pre-condition The arrival flight has been transferred by TMA/APP to the RWY controller and is

displayed in the RWY bay/Pending Arr section; the ‘Assume’ clearance option is available.

Dialogue Action Result 1. The system detects that an

‘Assume’ clearance has been issued by the RWY controller.

1. The ELDT (Estimated Landing Time) displayed in the Time1 arrival e-strip field (RWY controller) is replaced by a system-generated countdown (Time To touchdown). The format is ‘mm:ss’ (i.e. minutes:seconds). note: TTT is displayed until an ALDT (Actual Landing Time) has been input by the controller (see ‘input actual time of arrival’’ procedure) or detected by the system.

Requirement Ref. F.BL.SIL.04 Associated Procedures Following Input Actual Time of Arrival Previous Input Assume Associated HMI Objects Initiated by - Uses ARR E-STRIP | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.20 Input Actual Landing Time (ALDT) Procedure

Input Actual Time of Arrival Objective To provide the controller with the possibility to input an ALDT (Actual Landing

Time) Actors RWY controller Trigger Controller action Pre-condition The flight must have been given a ‘Cleared to land’ instruction, i.e. 3 green arrows

pointing up (��) are displayed on the e-strip on the left of the clearance field.

Dialogue Action Result 1a. Single click AB on the ‘ALDT’

field in the callsign menu, or

1b. Single click AB on the Time1 arrival e-strip field.

1b. - RWY controller: The displayed TTT (Time To Touchdown) is replaced by ALDT in the Time1 arrival e-strip field; the format is ‘Ahhmm’ (‘A’ for actual, hhmm hours and minutes, universal time). - GND controller: As a consequence of the RWY controller action, the displayed ELDT is replaced by ALDT in the Time1 field of the corresponding GND controller e-strip; the format is ‘Ahhmm’ (‘A’ for actual, hhmm hours and minutes, universal time).

Requirement Ref. F.BL.SIL.04 Associated Procedures Following - Previous Input Cleared to Land Associated HMI Objects Initiated by - Uses ARR E-STRIP | EXTENDED RADAR LABEL Particularities In case of the RWY controller does not input the actual time of arrival, transferring

the flight to the GND controller will have the same effect (i.e. displaying ALDT in the arrival e-strip field).

Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.21 Display Estimated In Block Time (EIBT)

Procedure Display Estimated In Block Time

Objective To display the Estimated In Block Time (EIBT) Trigger System generated Pre-condition The arrival flight is displayed in the RWY bay / Pending Arr section (GND

controller). The Taxi clearance option is available to the GND controller (to assume the flight)

Dialogue Action Result 1. The GND controller assumes the

arriving flight (see input taxi procedure). 2. The system detects that the aircraft is arrived at its stand.

1. The EIBT (estimated in block time) is displayed in the Time1 e-strip field (GND controller). 2. The EIBT moves from the Time1 to the Time2 field of the arrival e-strip. note: AIBT is displayed in Time1 (see ‘display arrival in block time’ procedure).

Requirement Ref. F.BL.SIL.04 Associated Procedures Previous Input Assume Associated HMI Objects Initiated by - Uses ARR E-STRIP | EXTENDED RADAR LABEL Particularities - Evolution -

5.6.2.22 Display Actual In-Block-Time (AIBT) Procedure

Display Actual In-Block Time Objective To display the Actual In Block Time (AIBT) Trigger System generated Pre-condition The arrival flight is displayed in the RWY bay / Taxi in section of the GND

controller. Dialogue Action Result 1. The system detects that the

aircraft has reached its stand. 1. The AIBT (actual in block time) is displayed and replaces the EIBT in the Time1 arrival e-strip field (GND controller). note: the e-strip is archived and removed from the GND display ‘n’ minutes after in-block event detection (system-generated). By default ‘n’ is equal to 2 minutes (local parameter)

Requirement Ref. F.BL.SIL.04 Associated Procedures Following Archive strip (to be defined) Associated HMI Objects Initiated by - Uses ARR E-STRIP | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.23 Display Estimated Off Block Time (EOBT) Procedure

Display Estimated Off Block Time Objective To display the EOBT for a departure flight Trigger System Generated Pre-condition EOBT flight data is known by the system Dialogue Action Result 1. The system detects that a

departure flight is 5 minutes from its EOBT.

1. The flight is displayed in the Departure Bay / Pending Dep section of the GND controller with its EOBT in the Time1 departure e-strip field. Note: EOBT is displayed in the Time1 departure e-strip field until ‘pushback’ clearance or first ‘taxi’ clearance is input by the GND controller (see ‘display target take off time’ procedure).

Requirement Ref. F.BL.SIL.04 Associated Procedures Following Input Start-Up | Input Taxi | Input Pushback Associated HMI Objects Initiated by - Uses DEP E-STRIP | EXTENDED RADAR LABEL Particularities In this initial version, the Clearance Delivery controller is not an actor. The

procedure will be updated accordingly in future issues of the document. Evolution -

5.6.2.24 Display Actual Off-Block Time (AOBT) Procedure

Display Actual Off Block Time Objective To display the actual off block time (AOBT) for a departure flight Trigger System generated Pre-condition The flight is displayed in the Departure Bay. Dialogue Action Result 1. The system detects that the

aircraft is moving, after pushback clearance (when any) or first taxi clearance issued by the GND controller.

1. GND controller: AOBT (actual off block time) is displayed in the Time2 departure e-strip field (extended e-strip).

Requirement Ref. F.BL.SIL.04 Associated Procedures Previous Input Taxi | Input Pushback Associated HMI Objects Initiated by - Uses DEP E-STRIP | EXTENDED RADAR LABEL Particularities - Evolution -

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.25 Display Target Take Off Time (TTOT) Procedure

Display Target Take-Off Time Objective To display the target take off time (TTOT) for a departure flight Trigger System Generated Pre-condition The ‘Pushback ’ or first ‘Taxi’ clearance (if pushback is not required) has been

issued by the controller. Dialogue Action Result 1. The system detects that pushback

or first taxi clearance has been issued by the GND controller. 2. The system detects that the departure aircraft starts moving after pushback clearance (if any) or taxi clearance issued by the GND controller.

1. GND controller: Time1 departure e-strip field is updated: EOBT is replaced by TTOT (Target Take-Off Time). 2. RWY controller: The e-strip is displayed in the Pending Departure Bay/ Pending Dep section (RWY controller). The TTOT is displayed in the corrresponding Time1 departure e-strip field. note: - The TTOT is displayed in the Time1 departure e-strip field (RWY controller) until ‘clearance for take off’ is issued by the RWY controller. - The TTOT is displayed in the Time1 departure e-strip field (GND controller) until the flight is assumed by the RWY controller.

Requirement Ref. F.BL.SIL.04 | F.SEQ.DEP.2 Associated Procedures Previous Input Start-Up | Input Pushback | Input Taxi Associated HMI Objects Initiated by - Uses DEP E-STRIP | EXTENDED RADAR LABEL Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.26 Input Actual Take-Off Time (ATOT) Procedure

Input Actual Take Off Time Objective To provide the controller with the possibility to input an ATOT. Actors RWY controller Trigger Controller action Pre-condition The flight must have been given a ‘Cleared for take-off’ instruction, i.e. 3 green arrows

pointing up (��) are displayed on the e-strip on the left of the clearance field. The ‘Airborne’ clearance option is available.

Dialogue Action Result 1a. Single click AB on the ‘airborne‘


1b. Single click AB on the ‘airborne’ option on the e-strip.

1a. or 1b. The e-strip moves from the RWY bay/RWY section to the Transfer Bay/Airborne Dep section. The ATOT is displayed in the Time1field of the DEP E-STRIP.

Requirement Ref. F.BL.SIL.04 Associated Procedures Following - Previous Input Clear for Take-Off Associated HMI Objects Initiated by - Uses DEP E-STRIP | CALLSIGN MENU Particularities - Evolution -

5.6.2.27 Change RWY for landing (single flight) Procedure

Change RWY for Landing (single flight) Objective To modify the RWY for landing for an individual arrival flight Actors RWY controller Trigger Controller action Pre-condition The arrival flight must be airborne and assumed, before issueing a ‘cleared to land’

clearance. Dialogue Action Result 1. Single click AB on a RWY menu

option in the extended e-strip or in the callsign

1. The selected RWY option replaces the previous RWY value

Requirement Ref. F.BL.UPD.02 Associated Procedures Previous Select Traffic Associated HMI Objects Initiated by RUNWAY MENU Particularities At current, the modification of landing RWY does not trigger dynamic aspects

(including ELDT recalculation and modification of path to the new assigned RWY). Evolution Updated (May 2007) not possible Dec. 2008

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.28 Change RWY for take-off (single flight) Procedure

Change RWY for take-off (single flight) Objective To modify the RWY for take-off for an individual arrival flight Actors GND Controller Trigger Controller action. Pre-condition The departure flight must be on the ground, assumed by the controller; the option

is no more available after clear for take off clearance issued by the RWY controller. The option is available on both the departure radar label and e-strip.

Dialogue Action Result 1. Single click AB on a RWY menu

option. 1. The selected RWY option replaces the previous RWY value wherever presented for this flightt

2. The SID is removed from SID field (the controller has to input a new SID (see ‘input SID’ procedure). If displayed, the clearance limit is removed from holding point field.

Requirement Ref. F.BL.UPD.02 Associated Procedures Following Input SID Previous Select Traffic Associated HMI Objects Initiated by RUNWAY MENU Particularities - Evolution Updated (May 2007)

5.6.2.29 Input holding point (single flight) Procedure

Input Holding Point Objective To input a holding point (clearance limit) for a departure flight. Actors GND controller | RWY controller Trigger Controller action Pre-condition The clearance limit has been previously removed after RWY change for take off

(single flight). Dialogue Action Result 1. Single click AB on the clearance

limit field. 1. The holding point menu is displayed under the cursor

2. Single click AB on an holding point menu option

2. The selected holding point option is displayed for this flight wherever this field is presented

Requirement Ref. F.BL.UPD.02 Associated Procedures Following - Previous Select Traffic Associated HMI Objects Initiated by HOLDING POINT MENU Particularities In the courrent version of the ITWP, the routing function allows the controller to

input a taxi clearance limit using the ‘Stop At’ order and ‘Stop at’ menu. Evolution not implemented (Dec 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.30 Change holding point (single flight) Procedure

Change Holding Point Objective To modify the holding point for a departure flight. Actors GND controller | RWY controller Trigger Controller action Pre-condition The flight is assumed by the controller; the clearance limit is displayed and line up,

conditional line up or take off clearance has not been issued by the RWY controller.

Dialogue Action Result 1. Single click AB on the clearance

limit field. 1. The holding point menu is displayed under the cursor

2. Single click AB on an holding point menu option

2. The selected RWY option is displayed and replaces the previous one.

Requirement Ref. F.BL.UPD.02 Associated Procedures Following - Previous Select Traffic Associated HMI Objects Initiated by HOLDING POINT MENU Particularities - Evolution not implemented (Dec. 2008)

5.6.2.31 Change parking stand Procedure

Change Parking Stand Objective To modify the parking stand for an arrival flight. Actors GND controller | RWY controller Trigger Controller action Pre-condition The arrival flight is assumed by the controller; Dialogue Action Result 1. Single click AB on the parking

stand field (arrival e-strip or radar label)

1. The parking stand menu is displayed under the cursor with current parking stand as default.

2. Single click AB on a parking stand option

2. The selected RWY option is displayed and replaces the previous one.

Requirement Ref. F.BL.UPD.02 Associated Procedures Following - Previous Select Traffic Associated HMI Objects Initiated by PARKING STAND MENU Particularities - Evolution Updated (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.32 Input SID Procedure Input SID

Objective To input a SID for a departure flight Actors RWY controller | GND controller Trigger Controller action Pre-condition The SID menu is available for the corresponding departure flight. Dialogue Action Result 1. Sincle click AB on the SID field in

the departure e-strip or radar label 1. The SID menu is displayed

2. Single click AB on a SID option 2a. The selected SID is assigned to the subject flight.

2b. The SID menu is closed and the SID field displays the selected SID for this flight, wherever presented.

Requirement Ref. F.BL.UPD.02 Associated Procedures Following - Previous Select Traffic Associated HMI Objects Initiated by SID MENU Particularities - Evolution not implemented (Dec. 2008)

5.6.2.33 Change SID Procedure

Change SID Objective To modify the current SID for a departure flight Actors RWY controller | GND controller Trigger Controller action Pre-condition The SID menu is available for the corresponding departure flight. Dialogue Action Result 1. Sincle click AB on the RWY field

in the departure e-strip or radar label 1. The SID menu is displayed with current SID as default.

2. Single click AB on a SID option 2a. The selected SID replaces the current SID wherever it is presented. 2b. The SID menu is closed and the SID field displays the new selected SID

Requirement Ref. F.BL.UPD.02 Associated Procedures Following - Previous Select Traffic | Input SID Associated HMI Objects Initiated by SID MENU Particularities - Evolution Updated (Septembre 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.2.34 Cancel SID Procedure Cancel SID

Objective To cancel the current SID for a departure flight Actors RWY controller | GND controller Trigger Controller action Pre-condition The SID menu is available for the corresponding departure flight. Dialogue Action Result 1. Sincle click SB on the SID field 1. The SID is removed from the SID field. Requirement Ref. F.BL.UPD.02 Associated Procedures Following - Previous Select Traffic | Input SID Associated HMI Objects Initiated by SID MENU Particularities - Evolution not implemented (Dec. 2008)

5.6.2.35 Mark/Unmark SID Procedure

Mark / Unmark SID Objective To mark the current SID field for a departure flight Actors RWY controller | GND controller Trigger Controller action Pre-condition The SID menu is available for the corresponding departure flight. A SID is

displayed in the SID field. Dialogue Action Result 1. Sincle click AB on the SID field in

the departure e-strip or radar label 1. The SID menu is displayed.

2a. Single click AB on the ‘MARK’ option (if available), or

2a. The SID field is displayed on ‘Marked’ colour background. The ‘UNMARK’ option replaces the ‘MARK’ option in the SID menu in the departure e-strip and radar label.

2b. Single click AB on the ‘MARK’ option (if available, i.e. if the SID has already been marked).

2b. The Mark colour background is removed from the SID field. The ‘MARK’ option replaces the ‘UNMARK’ option in the SID menu in the departure e-strip and radar label.

Requirement Ref. F.BL.UPD.02 Associated Procedures Following - Previous Select Traffic | Input SID Associated HMI Objects Initiated by SID MENU Particularities - Evolution not implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.3 Transfer and Coordination

5.6.3.1 Assume Traffic Procedure

Input Assume Objective To provide the controller with the possibility to assume a flight Actors GND Controller | RWY controller | CLD Controller Trigger Controller action Pre-condition The flight is in ‘Pending in’ sub-state. It is displayed in the Pending Departure bay

(Pending Dep section) or RWY bay (Pending Arr section); Dialogue Action Result 1a. Single click AB on the

‘Assume’ option in the callsign menu, or

1b. Single click AB on the ‘Assume’ option on the e-strip

1a or 1b. - Arrival traffic : RWY controller: the flight moves from RWY bay (Pending Arr) to the Final section. Available clearances are ‘Continue Approach’, ‘Cleared to land’ and ‘Go Around’. On the corresponding e-strip (RWY controller), ELDT is replaced by TTT (System Generated event) in the Time1 e-strip field. First GND controller: when assumed by the RWY controller, the flight is displayed in the ‘RWY bay/Pending Arr section’ of the first GND controller concerned by the flight. The ELDT (system-generated) is displayed in the Time1 e-strip field. - Departure traffic : GND controller: the e-strip stays in the pending departure bay; text in label and e-strips is displayed in ‘departure colour’. Possible instructions are ‘start up’ (if not already issued), ‘taxi’, ‘pushback’ (‘mark’ and ‘cancel’ are also available in the callsign menu). RWY controller: the flight moves from the Pending Departure bay / Pending Dep section to the Holding point section. Available clearances are ‘Hold’, ‘Line-up’ and ‘Conditional line-up’. CLD controller: the flight is dispyaed in the pending dep. Section of the outbound bay. The callsign, leader line, aircraft symbol and text are displayed in ‘Departure Colour’. - Vehicle : GND controller: the e-strip is displayed in the GND bay / taxi-out section. Possible instructions are dependant on the initial route of the vehicle (e.g if vehicle would cross the RWY then ‘Cross’ will be available as clearance). RWY controller: the e-strip is dispalyed in the ‘Holding point’ section. When ‘Cross’ clearance is approved, the e-strip moves to the RWY section (RWY bay).

Requirement Ref. F.FD.TRSF.02 | F.FD.TRSF.04 Associated Proc edures

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Following Input Cleared to Land | Input Go Around | Input Line Up | Input Conditional Line Up | Input Hold | Input CLR | Input DCLR

Previous - Associated HMI Objects Initiated by CALLSIGN MENU | DEP E-STRIP | ARR E-STRIP | VEHICLE RADAR LABEL Uses - Particularities - Evolution Updated (Octobre 2007)

5.6.3.2 Transfer Traffic Procedure

Transfer Traffic Objective To transfer a traffic to the next default Operator Role. Actors GND Controller | RWY controller | CLD Controller Trigger Controller action Pre-condition The traffic is assumed by the controller; the transfer option is available to the

controller. Dialogue Action Result 1a. Single click AB on the default

next controller frequency (e.g. 121.950) in the callsign menu, or

1b. Single click AB on the the default next controller frequency on the e-strip.

1a. or 1b. a) RWY�GND controller: the e-strip moves from the RWY bay / RWYsection to the Transfer Bay / Taxi in section b) GND�RWY controller: the e-strip moves from departure bay / taxi out section to the RWY bay / transfer to RWY section. c) RWY�TMA/APP: the flight is still displayed in the transfer bay / airborne dep section. d) TMA/APP� RWY: the flight is displayed in the RWY bay / Pending Arr. section at a time parameter before ELDT (Tpending-arr) (see §2.3.2.1). E) CLD� GND: the flight is still displayed in the outbound bay / start section. - transition from ‘assumed’ to ‘not concerned’ main state The text is displayed in ‘not concerned’ colour (see §2.4.2).

Requirement Ref. F.FD.TRSF.01 | F.FD.TRSF.02 | F.FD.TRSF.04 Associated Procedures Following - Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU | DEP E-STRIP | ARR E-STRIP | RADAR LABEL |

EXTENDED RADAR LABEL Particularities - Evolution Updated (May 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.3.3 Transfer Vehicle / Towed aircraft Procedure

Transfer Vehicle/Towed aircraft Objective To transfer a vehicle / towed aircraft to the RWY or GND controller. Actors GND Controller | RWY controller Trigger Controller action Pre-condition The traffic is assumed by the controller; the transfer option is available to the

controller. Dialogue Action Result 1a. Single click AB on Operator role

in a vehicle radar lable (e.g.GND) open transfer menu with available operator role 1b. Single click AB on Operator role in a aircraft (towed) radar lable (e.g.GND) open transfer menu with available operator role

1a. a) RWY�GND controller: the e-strip moves from the RWY bay / RWY section to the Transfer Bay / Taxi in section b) GND�RWY controller: the e-strip moves from outbound bay / taxi out section to the RWY bay / transfer to RWY section.

Requirement Ref. F.FD.TRSF.01 | F.FD.TRSF.02 | F.FD.TRSF.04 Associated Procedures Following Input Taxi | Input tow |Input Hold | Input Cross RWY | Input Enter | Input

Release Previous Input Assume Associated HMI Objects Initiated by VEHICLE RADAR LABEL | TOWED AIRCRAFT RADAR LABEL Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.6.3.4 Select Operator Role for Transfer Procedure

Select Operator Role for Transfer Objective To select an Operator Role for transfer different from the default one. Actors GND Controller | RWY controller Trigger Controller action Pre-condition The traffic is assumed by the controller. Dialogue Action Result 1a. single click AB on ‘D-TRANSF’ in

the callsign menu, or 1b. single click AB on the operator

role in the e-strip clearance field when available.

1a or 1b. The operator role-menu opens with operator role default

2. single click AB on an operator role option and its associated frequencyt in the operator role menu.

2. The selected operator role option and associated frequency) replaces the previous role and the menu is closed.

Requirement Ref. F.FD.TRSF.03 Associated Procedures Following Transfer Traffic Previous Select Traffic Associated HMI Objects Initiated by OPERATOR ROLE MENU Particularities - Evolution not implemented (Dec. 2008)

5.6.4 Filter Traffic

5.6.4.1 Filter traffic (height) Procedure

Filter traffic (height) Objective To provide the ATC controller with the ability to remove display airborne aircraft on

altitude criterion. Actors RWY Controller Trigger Controller action Pre-condition - Dialogue Action Result 1. Press and Drag AB on slider

cursor along the slider on the Traffic Filter Tool (altitude)

1. As the cursor moves, the altitude value is shown below the slider. The traffic above the altitude value is filtered out .

Requirement Ref. F.BL.FILT.01 | F.BL.FILT.02 Associated Procedures Previous Access Tool Following - Associated HMI Objects Initiated by TRAFFIC FILTER TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Particularities - Evolution Not implemented (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.7 MANAGEMENT OF VEHICLES

5.7.1 Display vehicles on the masked apron area Procedure

Display vehicles Objective To provide the controller with the possibility to display vehicles on the masked

apron area Actors RWY / GND controller Trigger Controller action Pre-condition By default, The vehicles are hidden on the apron. Dialogue Action Result 1. De-selection of ‘hide vehicles’ in

the AIRPORT SETUP TOOL All the vehicles are visible on the composite radar display.

Requirement Ref. F.VEH.DIS.2 Associated Procedures Following Previous Hide vehicles Associated HMI Objects Initiated by AIRPORT SETUP TOOL Particularities - Evolution Updated (Dec. 2008)

5.7.2 Hide vehicles on the masked apron area Procedure

Hide vehicles Objective To provide the controller with the possibility to hide vehicles on the masked apron

area Actors RWY / GND controller Trigger Controller action Pre-condition By default, the vehicles are displayed on the apron (limit of the masked apron

area). Dialogue Action Result 1. Select the ‘hide vehicles’ option in

the AIRPORT SETUP TOOL All the vehicles are hidden on the composite radar display.

Requirement Ref. F.VEH.DIS.2 Associated Procedures Following Previous Display vehicles Associated HMI Objects Initiated by AIRPORT SETUP TOOL Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.7.3 Input “Tow”

Procedure Input tow

Objective To provide the controller with the possibility to give a tow instruction to a towed aircraft

Actors RWY / GND controller Trigger Controller action Pre-condition The ‘Tow’ clearance option is available in the callsign menu / e-strip of the towed

aircraft when a towed aircraft is assumed, either via radar label or via e-strip

Dialogue Action Result 1a. Single click AB on the ‘TOW’

option in the callsign menu, or 1b. Single click AB on the ‘TOW’


1a. or 1b. if a ‘TOW’ instruction has been input by the GND controller, the e-strip is in the taxi-out section of the Departure bay. If the order has been input by the RWY controller, the e-strip is in the holding point section of the Taxi-out bay.

Requirement Ref. F.VEH.ORD.2 Associated Procedures Following Input Hold | Input Cross RWY | Input Enter | Cancel order / instruction | Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU Uses TOWED AIRCRAFT RADAR LABEL | TOWED AIRCRAFT E-STRIP Particularities - Evolution Updated Dec. 2008

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.7.4 Input “Release” Procedure

Input Release Objective To provide the controller with the possibility to release the vehicle / towed aircraft Actors RWY / GND controller Trigger Controller action Pre-condition The ‘REL’ clearance option is available in the callsign menu / e-strip of the vehicle /

towed aircraft a) when a vehicle / towed aircraft is assumed, either via radar label or via e-strip

Dialogue Action Result 1a. Single click AB on the ‘REL’

option in the callsign menu, or 1b. Single click AB on the ‘REL’


1a. or 1b. The status of the vehicle / towed aircraft is changed. It is not assumed any more by the controller (non concerned status). The released traffic is displayed in the colour defined for non concerned traffic (grey).

Requirement Ref. F.VEH.ORD.1 | F.VEH.ORD.3 Associated Procedures Following Previous Input Assume | Input Taxi | Input Vacate | Input tow Associated HMI Objects Initiated by CALLSIGN MENU Uses VEHICLE E-STRIP | VEHICLE RADAR LABEL | TOWED AIRCRAFT RADAR

LABEL | TOWED AIRCRAFT E-STRIP | Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8 MANAGEMENT OF ALERTS AND WARNINGS

5.8.1 General alert management

5.8.1.1 Acknowledgement of an alert Procedure

Acknowledge alert Objective To enable the controller to acknowledge the alert. Actors RWY controller | GND controller Trigger Automatically displayed in case of alert. Pre-condition A potential hazardous situation has been predicted or detected. The alert has been

displayed on the composite situation display (in the alert window, in the e-strip and in the radar label – callsing and alert description and around the radar track symbol).

Dialogue Action Result 1. Single AB click on the

acknowledement button acknowledges the alert and removes the display of the information alert in the radar label and in the e-strip on both positions (GND and RWY).

1. For the information alert (step 1), the ‘ACK’ removes the display alert in the radar label, in the e-strip and in the alert window on both ATC control positions. 2. For an alarm, the button ‘ACK’ stops the audio signal that comes with the alarm display.

Requirement Ref. F.SN.GEN.5 Associated Procedures Previous Display Excessive Taxi Speed | Display ATCO Input Error w.r.t. Airport

Layout | Display Conflicting ATC Clearances Input Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | | ALERT IN E-STRIP | ALERT RADAR

TRACK Particularities If you click ACK again it returns the alert to the label Evolution Implemented (Nov. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.1.2 Red circle for an alarm Procedure Red circle

Objective To informe the controller about an alarm. Actors RWY controller | GND controller Trigger Automatically displayed in case of alert step 2 (ALARM). Pre-condition A potential hazardous situation, an ALARM, has been detected. The alert has been

displayed on the composite situation display (in the alert window, in the e-strip and in the radar label – callsing and alert description) and around the radar track of the involved traffic.

Dialogue Action Result - - Requirement Ref. F.SN.GEN.2 | F.SN.GEN.3 | F.SN.GEN.4 Associated Procedures Previous Display Excessive Taxi Speed | Display ATCO Input Error w.r.t. Airport

Layout | Display Conflicting ATC Clearances Input | Display Non Conformance to ATC Instructions

Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP | ALERT RADAR

TRACK Particularities If you click ACK again it returns the alert to the label Evolution Implemented (Nov. 2008)

5.8.2 Management of alerts for conflicting ATC clea rances (CLRS)

5.8.2.1 Display conflicting ATC clearance input Procedure

Display Conflicting ATC Clearances Input Objective To indicate to the controller that the clearance input is inconsistent (confliciting with

any other given clearance). Actors RWY controller | GND controller Trigger Automatically displayed in case of inconsitent clerances. Pre-condition An inconsistent clearance has already been detected and displayed on the

composite situation display. Dialogue Action Result 1. The alerting function detects an

inconsistent clearance when controller input it and sends an ALERT / alert step 2 to the ATC control positions (both GND and RWY).

1. The ALERT / alert step 2 is displayed for the involved traffic on concerned ATC control positions. The alert is displayed on all traffic representations on the composite radar situation display and on the Alert window.

Requirement Ref. F.SN.CLRS.1 Associated Procedures Following Acknowledge alert | End Display Conflicting ATC clearance Input Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP | ALERT IN E-STRIP

| ALERT RADAR TRACK | ALERT RADAR TRACK Particularities - Evolution This alert belongs to the Category 2 (CLRS) of the Airport Safety Nets. The former

references of the requirements have been replaced (see § 6). Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.2.2 End display of conflicting ATC clearance in put Procedure

End Display Conflicting ATC clearance Input Objective To indicate to the controller that the inconsistent clearance is canceled. Actors RWY controller | GND controller Trigger The alert is automatically removed when clerances are consistent. Pre-condition The alert Step 2 for inconsistent clearance is displayed. Dialogue Action Result 1. The alerting function detects that

clearances are consistent, and sends an end of alert for inconsistent clearance input to the concerned control positions.

1. The inconsistent clearance input (step 2 alert) is removed for the involved traffic on both RWY and GND control positions; the alert is removed from all the traffic representations on the composite situation display and from the Alert Window.

Requirement Ref. F.SN.GEN.5 | F.SN.GEN.6 Associated Procedures Previous Display Conflicting ATC Clearances Input | Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP | ALERT RADAR

TRACK | ALERT RADAR TRACK Particularities Evolution This alert belongs to the Category 2 (CLRS) of the Airport Safety Nets. The former

references of the requirements have been replaced ( see § 6). Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.3 Management of alerts for infringements of res tricted / closed areas (AREA)

5.8.3.1 Display runway conflict alert Procedure

Display Runway Conflict (step 1 alert) Objective To provide the controller with an alert when the surface potential hazardous

situations detection and Alerting function predicts a runway conflict alert (information, alert – step 1)

Actors RWY controller | GND controller Trigger Automatically displayed within the look-ahead time, raised in case of runway conflict

alert step 1 event. Pre-condition - Dialogue Action Result 1. The surface conflict detection

and alerting function detects a runway incursion within the corresponding look ahead time (T1, local parameter) and sends a RCA step 1 alert to concerned ATC control positions.

1. The runway conflict step 1 alert is displayed for the involved traffic on concerned ATC control positions. The alert is displayed on all traffic representations. The callsigns of involved traffic are displayed in Information alert background colour wherever presented (radar labels, e-strips, alert window).

Requirement Ref. F.SN.AREA.1 | F.SN.AREA.2 | F.SN.AREA.3 | F.SN.AREA 4 | F.SN.AREA.5| F.SN.AREA.6 | F.SN.AREA.7 | F.SN.GEN.1 | F.SN.GEN.2 | F.SN.GEN.4 | F.SN.GEN.5

Associated Procedures Following End Runway Conflict Alert | Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN E-STRIP | ALERT IN LABEL | RWY CONFLICT

ALERT LABEL | RUNWAY CONFLICT ALERT MESSAGE | RWY CONFLICT ALERT TRACK | RUNWAY ALERT |ALERT IN E-STRIP | ALERT RADAR TRACK

Particularities - Evolution This alert belongs to the Category 3 (AREA) of the Airport Safety Nets. The former

references of the requirements have been replaced ( see § 6). Update (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Procedure

Display Runway Conflict (step 2 alert) Objective To provide the controller with an alert when the surface potential hazardous

situations detection and alerting function predicts a runway conflict alert (Alarm alert step 2).

Actors RWY controller | GND controller Trigger Automatically displayed within the look-ahead time, raised in case of runway

conflict alert step 1 event. Pre-condition A runway conflict alert has already been detected and displayed on the composite

situation display. Dialogue Action Result 1. The surface conflict detection and

alerting function detects a runway incursion within the corresponding look ahead time (T2, local parameter) and sends an alert step 1 alert to concerned ATC control positions (CLD, GND and RWY).

1. The runway conflict step 2 alert is displayed for the involved traffic on concerned ATC control positions. The alert is displayed on all traffic representations on the composite radar situation display and on the Alert window.

Requirement Ref. F.SN.AREA.1 | F.SN.AREA.2 | F.SN.AREA.3 | F.SN.AREA 4 | F.SN.AREA.6 | F.SN.AREA.7 | F.SN.GEN.1 | F.SN.GEN.2 | F.SN.GEN.4 | F.SN.GEN.5 | F.SN.GEN.3

Associated Procedures Following End Runway Conflict Alert | Acknowledge alert Associated HMI Objects Initiated by ALERT WINDOW | RWY CONFLICT ALERT LABEL | RUNWAY CONFLICT

ALERT MESSAGE | RWY CONFLICT ALERT TRACK | RUNWAY ALERT | ALERT IN E-STRIP | ALERT IN LABEL | ALERT RADAR TRACK | ALERT RADAR TRACK

Uses - Particularities This group of alerts includes the following alerts: conflict and runway incursion Evolution Update (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.3.2 End runway conflict alert Procedure

End Runway Conflict Alert Objective To indicate to the controller that the runway conflict alert is over. Actors RWY controller | GND controller Trigger Within the look-ahead time, the traffic is predicted to be above the RWY conflict

alert triggering parameters. The alert is automatically removed when runway conflict alert is over.

Pre-condition The Runway Conflict Alert is displayed. Dialogue Action Result 1. The surface conflict detection and

alerting function detects that runway conflict alert triggering parameters are no more fulfilled, and sends an end of runway conflict alert to the concerned control positions.

1. The runway conflict alert (step 1 or step 2 alert) is removed for the involved traffic on both RWY and GND control positions; the alert is removed from all the traffic representations on the composite situation display and from the Alert Window.

Requirement Ref. F.SN.GEN.6 | F.SN.GEN.5 | F.SN.AREA.5 Associated Procedures Previous Display Runway Conflict (step 1 alert) | Display Runway Conflict (step 2 alert)

| Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | RWY CONFLICT ALERT LABEL | RUNWAY CONFLICT

ALERT MESSAGE | RWY CONFLICT ALERT TRACK | RUNWAY ALERT | ALERT RADAR TRACK | ALERT IN E-STRIP | ALERT IN LABEL | ALERT RADAR TRACK | ALERT RADAR TRACK


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.3.3 Display ATCO input error with restect to ai rport layout Procedure

Display ATCO Input Error w.r.t. Airport Layout Objective To indicate to the controller that in the manual input w.r.t airport layout is an error. Actors RWY controller | GND controller Trigger Automatically displayed in case of error in ATCO’s input w.r.t airport layout. Pre-condition Taxiway sector status or runway status is set “closed”. An input error w.r.t airport

layout has already been detected and displayed on the composite situation display. Dialogue Action Result 1. The alerting function detects an

error in ATCO input related to the airport layout and sends an alert step 1 to the ATC control positions (GND, RWY and CLD) (e.g. aircraft cleared to taxi via a closed taxiway).

2. The alerting function detects if a mobile is on the restriced / closed area and sends an alert step 2 to the ATC control positions (GND, RWY and CLD) (e.g. aircraft is on the closed taxiway).

1. The alert step 1 is displayed for the involved traffic on concerned ATC control positions. The alert is displayed on all traffic representations on the composite radar situation display and on the Alert window. 2. The alert step 2 is displayed for the involved traffic on concerned ATC control positions if the mobile is detected on the restricted / closed area. The alert is displayed on all traffic representations on the composite radar situation display and on the Alert window.

Requirement Ref. F.SN.GEN.1 | F.SN.GEN.2 | F.SN.GEN.4 | F.SN.GEN.5 | F.SN.GEN.3 | F.SN.AREA.8 Associated Procedures Previous Set Up Runway/ Taxiway Status Following End Display ATCO Input Error w.r.t. Airport Layout | Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ATCO INPUT ERROR w.r.t. AIRPORT

LAYOUT ALERT MESSAGE | ALERT IN E-STRIP | Particularities If the alert step 2 (ALARM) then ALERT RADAR TRACK is applicable Evolution This alert belongs to the Category 3 (AREA) of the Airport Safety Nets. The former

references of the requirements have been replaced (see § 6). Update (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.3.4 End display ATCO input error w.r.t airport layout Procedure

End Display ATCO Input Error w.r.t. Airport Layout Objective To indicate to the controller that the error in manual input w.r.t airport layout is

corrected. Actors RWY controller | GND controller Trigger The alert is automatically removed when input error w.r.t airport layout is corrected. Pre-condition The alert Step 1 for ATCO input error w.r.t airport layout is displayed.

The alert Step 2 is displayed if the input error is not resolved and the system detects a mobile entering the unauthorised area.

Dialogue Action Result 1. The alerting function detects that

input error w.r.t airport layout is corrected, and sends an end of alert for input error w.r.t airport layout to the concerned control positions.

1. The input error w.r.t airport layout (step 1 alert) is removed for the involved traffic on both RWY and GND control positions; the alert is removed from all the traffic representations on the composite situation display and from the Alert Window.

2. The display of information alert is removed for the involved traffic on both RWY and GND control positions

Requirement Ref. F.SN.GEN.6 | F.SN.GEN.5 Associated Procedures Previous Display ATCO Input Error w.r.t. Airport Layout | Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP | ALERT RADAR

TRACK Particularities - Evolution Updated (Dec.2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.4 Management of alerts for non conformance to A TC instructions

5.8.4.1 Display non conformance to ATC instructions (INFORMATION) Procedure

Display Non Conformance to ATC Instructions Objective To indicate to the controller non conformance to the given ATC instruction. Actors RWY controller | GND controller Trigger Automatically displayed in case of non conformance to the given ATC instruction. Pre-condition A non conformance to the given ATC instruction has already been detected and

displayed on the composite situation display. Dialogue Action Result 1. The alerting function detects a non

conformance to the given ATC instruction, no interation with the surrounding traffic, and sends an alert step 1 to the ATC control positions (GND, RWY and CLD).

1. The alert step 1 is displayed for the involved traffic on concerned ATC control positions. The alert is displayed on all traffic representations on the composite radar situation display and on the Alert window.

Requirement Ref. F.SN.GEN.1 | F.SN.GEN.2 | F.SN.GEN.4 | F.SN.GEN.5 | F.SN.PROC.1 | F.SN.PROC.2 | F.SN.PROC.3 | F.SN.PROC.7

Associated Procedures Following End Display Non Conformance to ATC Instructions | Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP Particularities This procedure adresses the display of alert if:

-an aircraft taxis with excessive speed, -an aircraft is stationary in the RWY protection area, -an aircraft takes off without clearance.


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.4.2 End display non conformance to ATC instruct ions (INFORMATION) Procedure

End Display Non Conformance to ATC Instructions Objective To indicate to the controller that the non conformance to the given instruction is

resolved. Actors RWY controller | GND controller Trigger The alert is automatically removed when non conformance to the given instruction

is resolved. Pre-condition The alert Step 1 for non conformance to the given instruction is displayed. Dialogue Action Result 1. The alerting function detects that

non conformance to the given instruction is resolved and sends an end of alert for non conformance to the concerned control positions.

1. The non conformance to the given instruction (step 1 alert) is removed for the involved traffic on both RWY and GND control positions; the alert is removed from all the traffic representations on the composite situation display and from the Alert Window.

Requirement Ref. F.SN.GEN.6 | F.SN.GEN.5 Associated Procedures Previous Display Non Conformance to ATC Instructions Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.4.3 Display non conformance to ATC instructions (ALARM) Procedure

Display Non Conformance to ATC Instructions - ALARM Objective To indicate to the controller non conformance to the given ATC instruction. Actors RWY controller | GND controller Trigger Automatically displayed in case of non conformance to the given ATC instruction. Pre-condition A non conformance to the given ATC instruction has already been detected and

displayed on the composite situation display. Dialogue Action Result 1. The alerting function detects a non

conformance to the given ATC instruction and sends an alert step 2 to the ATC control positions (GND, RWY and CLD).

1. The alert step 2 is displayed for the involved traffic on concerned ATC control positions. The alert is displayed on all traffic representations on the composite radar situation display and on the Alert window. An audio signal comes with the alarm display.

Requirement Ref. F.SN.GEN.1 | F.SN.GEN.2 | F.SN.GEN.4 | F.SN.GEN.5 | F.SN.GEN.3 | F.SN.GEN.6 | F.SN.PROC.1 | F.SN.PROC.2 | F.SN.PROC.3 | F.SN.PROC.4 | F.SN.PROC.5 | F.SN.PROC.6 | F.SN.PROC.8 | F.SN.PROC.7

Associated Procedures Following End Display Non Conformance to ATC Instructions - A LARM | Acknowledge

alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP | ALERT RADAR

TRACK Particularities This procedure adresses the display of alert if:

- an aircraft taxis with excessive speed, - an aircraft is stationary in the RWY protection area, - a mobile is entering a runway without clearances, - an aircraft is on short final and is not cleared to land, - an aircraft crosses the red stop bar, - an aircraft takes off without clearance, - an aircraft is not aligned on final on the assigned landing runway..


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.4.4 End display non conformance to ATC instruct ions (ALARM) Procedure

End Display Non Conformance to ATC Instructions - A LARM Objective To indicate to the controller that the non conformance to the given instruction has

been resolved. Actors RWY controller | GND controller Trigger The alert is automatically removed when non conformance to the given instruction

has been resolved. Pre-condition The alert Step 1 for non conformance to the given instruction is displayed. Dialogue Action Result 1. The alerting function detects that

non conformance to the given instruction has been resolved and sends an end of alert for non conformance to the concerned control positions.

1. The non conformance to the given instruction (step 1 alert) is removed for the involved traffic on both RWY and GND control positions; the alert is removed from all the traffic representations on the composite situation display and from the Alert Window.

Requirement Ref. F.SN.GEN.5 | F.SN.GEN.6 Associated Procedures Previous Display Non Conformance to ATC Instructions - ALARM | Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP | ALERT RADAR

TRACK Particularities - Evolution Updated (Dec. 2008)

5.8.4.5 Display excessive aircraft taxi speed Procedure

Display Excessive Taxi Speed Objective To indicate to the controller that an aircraft taxies with a speed that exceeds given

speed limit. Actors RWY controller | GND controller Trigger Automatically displayed in case of taxi speed exceeding. Pre-condition An aircraft excessive taxi speed has already been detected and displayed on the

composite situation display. Dialogue Action Result 1. The alerting function detects a

speed excessing speed limit and sends an alert step 1 / step 2 to the ATC control positions (GND, RWY and CLD).

1. The alert step 1 is displayed if an aircraft taxi speed exceeds 36 knots. The alert is displayed on all traffic representations on the composite radar situation display and in the alert window. 2. The alert step 2 is displayed if an aircraft taxi speed exceeds 50 knots.

Requirement Ref. F.SN.GEN.1 | F.SN.GEN.2 | F.SN.GEN.3 | F.SN.GEN.4 | F.SN.GEN.5 | F.SN.GEN.6 | F.SN.PROC.2

Associated Procedures Following End Display Excessive Taxi Speed | Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP | and if ALARM then

ALERT RADAR TRACK in addition

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft



5.8.4.6 End alert for excessive aircraft taxi speed Procedure

End Display Excessive Taxi Speed Objective To indicate to the controller that the aircraft have reduced taxies speed and is

inferior to the given speed limit Actors RWY controller | GND controller Trigger The alert is automatically removed when aircraft taxi speed is inferior than given

speed limit. Pre-condition The alert Step 1 / Step 2 for taxi speed excess is displayed. Dialogue Action Result 1. The alerting function detects that

the aircraft taxi speed is inferior to the given speed limit and sends an end of taxi speed excess alert to the concerned control positions.

1. The taxi speed excess (step 1 alert / step 2) is removed for the involved traffic on both RWY and GND control positions; the alert is removed from all the traffic representations on the composite situation display and from the Alert Window.

Requirement Ref. F.SN.GEN.5 | F.SN.GEN.6 Associated Procedures Previous Display Excessive Taxi Speed | Acknowledge alert Associated HMI Objects Uses ALERT WINDOW | ALERT IN LABEL | ALERT IN E-STRIP for the alert step 2

ALERT RADAR TRACK is associated object Particularities - Evolution Updated (Dec. 2008)

5.8.5 Management of protecting devices and runway l ighting

5.8.5.1 Display stop bar status Procedure

Display Stop Bar Status Objective To display the status of the stop bar.

Actors RWY Controller | GND controller Trigger System Generated Pre-condition - Dialogue Action Result - The stop bar is displayed on the

composite radar screen. Requirement Ref. F.SN.PTD.01 | F.SN.PTD.02 | F.SN.PTD.05 Associated Procedures Following Move window | Close window | Manually Set Up Stop Bar Status Associated HMI Objects Uses NAVAIDS INFORMATION WINDOW Particularities It is valid for both automatic and manual stop bar management. The status of the

stop bars is changed automatically according to ATC clearances. Evolution Updated (reorganisation of sections, Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.5.2 Manually activate / de-activate stop bar

Procedure Manually Set Up Stop Bar Status

Objective To enable the controller to manually activate / de-activate a stop bar (change a stop bar status)

Actors RWY Controller | GND controller Trigger Controllers action Pre-condition The stop bars are working correctly and are displayed on the composite radar

screen (‘stopbars’ selected in the MAP SELECTION TOOL ). Dialogue Action Result 1. Single Click AB on the stop bar

open menu and enable the controller to change the status of the stop bar.

After 1. the stop bar menu is open; OFF and ON options are available: - if ON then the stop bars is activated and displayed in red - if OFF then the stop bar is de-activated.

Requirement Ref. F.SN.PTD.01 | F.SN.PTD.02 Associated Procedures Following Previous

Move window | Close window Display Stop Bar Status

Associated HMI Objects Uses STOP BAR MENU Particularities Evolution Updated (Dec. 2008)

5.8.6 Management of navaids serviceability

5.8.6.1 Display navaids serviceability Procedure

Display Navaids Serviceability Objective To display minimum information about navaids serviceability to the controller

Actors RWY Controller | GND controller Trigger System Generated (when failure or recovery from failure) or Controller Action Pre-condition - Dialogue Action Result 1a. Single Click AB on the ‘EQUIP’

button in the General Toolbox Window, or

1b. The system detects the transition from serviceable to failure or recovery from failure (note: if the

1. The NAVAIDS window is displayed.

Requirement Ref. F.SN.NAV.01 Associated Procedures Following Move window | Close window Associated HMI Objects Uses NAVAIDS INFORMATION WINDOW Particularities - Evolution Updated (reorganisation of sections, Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.7 Management of mobiles on the runway

5.8.7.1 Input “Enter” Procedure Input Enter

Objective To provide the controller with the possibility to instruct an aircraft or a vehicle / towed aircraft to enter a protected area.

Actors RWY / GND controller Trigger Controller action Pre-condition The ‘Enter’ clearance option is available in the mobile callsign menu / e-strip.

a) when a vehicle / towed aircraft is assumed, either via vehicle / towed aircraft radar label (i.e. displayed in the taxi-out section of the Departure bay) and its planned route is crossing the runway or entering protected area b) for an aircraft , either via radar label or via the e-strip.

Dialogue Action Result 1a. Single click AB on the ‘Enter’

option in the callsign menu, or 1b. Single click AB on the ‘Enter’


1a. or 1b. � vehicle / towed aircraft: if a ‘Enter’ order has been input by the GND controller when a vehicle was in the taxi-out section (Departure bay): -- it stays in taxi - out section , a ghost e-strip is open in the RWY bay of the RWY controller -- the VAC / HOLD / REL options are availabe -- runway border is highlighted orange � vehicle/ towed aircraft: if the vehicle was displayed in the RWY bay of the RWY controller (holding point section) : -- it is moved to the RWY bay in the RWY section -- the VAC / HOLD / REL options are availabe � arrival aircraft: if an arrival aircraft was displayed in the RWY bay of the RWY controller (RWY bay): -- it is moved to the RWY bay of the parallel active runway to cross. -- the VAC / CROSS / Transfer options are availabe.

Requirement Ref. F.SN.RWY.1 Associated Procedures Following Input Vacate | Transfer Traffic | Cancel order / instruction Previous Input Assume | Input Taxi | Input Hold Associated HMI Objects Initiated by CALLSIGN MENU Uses VEHICLE E-STRIP | VEHICLE RADAR LABEL | TOWED AIRCRAFT E-STRIP |

TOWED AIRCRAFT RADAR LABEL | ARR E-STRIP | RADAR LABEL Particularities - Evolution Updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.7.2 Input “Cross” Procedure

Input Cross RWY Objective To provide the controller with the possibility to input a cross runway order to an

aircraft or vehicle Actors RWY controller | GND controller Trigger Controller action Pre-condition The ‘CROSS’ clearance option is available in the vehicle / towed aircraft callsign

menu / e-strip. This option is available to the RWY / GND controller a) when a vehicle/towed aircraft is assumed, either via vehicle / towed aircraft radar label (i.e. displayed in the taxi-out section of the Departure bay or in the holding point section of the RWY bay) and his planned route is crossing the runway b) when an arrival aircraft has to cross a parallel active runway while taxiing to the assigned stand.

Dialogue Action Result 1a. Single click AB on the ‘Cross’

option in the callsign menu, or 1b. Single click AB on the ‘Cross’


1a. or 1b. � vehicle / towed aircraft: if a ‘Cross’ order has been input by the GND controller when a vehicle was in the taxi-out section (Departure bay): -- it stays in taxi - out section , a ghost e-strip is open in the RWY bay of the RWY controller -- the VAC / HOLD / REL options are availabe -- runway border is highlighted orange � vehicle/ towed aircraft: if the vehicle was displayed in the RWY bay of the RWY controller (holding point section) : -- it is moved to the RWY bay in the RWY section -- the VAC / HOLD / REL options are availabe � arrival aircraft: if an arrival aircraft was displayed in the RWY bay of the RWY controller (RWY bay): -- it is moved to the RWY bay of the parallel active runway to cross. -- the VAC / ENTER / Transfer options are availabe.

Requirement Ref. F.SN.RWY.2 Associated Procedures Following Input Vacate | Transfer Traffic | Cancel order / instruction | Input Enter Previous Input Assume | Input Taxi | Input Hold | Input HoldAt Associated HMI Objects Initiated by CALLSIGN MENU Uses ARR E-STRIP | RADAR LABEL | VEHICLE E-STRIP | VEHICLE RADAR LABEL

| TOWED AIRCRAFT E-STRIP | TOWED AIRCRAFT RADAR LABEL Particularities - Evolution Updated Dec. 2008

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.7.3 Display of Runway cross/enter

Procedure Display Runway Occupied

Objective To indicate that a mobile is authorised to ‘cross’ or ‘enter’ the active runway. Actors GND controller | RWY controller Trigger Controller action Pre-condition The controller gives the cross or enter clearance to an aircraft or a vehicle. Dialogue Action Result 1.a Single click AB on the ‘Cross’ or

‘Enter’ option in the callsign menu; 1b. Single click AB on the ‘Cross’ or ‘Enter’ option on the e-strip

1a or 1b The runway border is higlighted in orange.

Requirement Ref. H.SN.RWY.2 Associated Procedures Following End Display Runway Occupied Previous - Associated HMI Objects Uses Particularities - Evolution Updated (Dec 2008)

5.8.7.4 End Display of Runway cross/enter Procedure

End Display Runway Occupied Objective To indicate that a mobile has been cleared to vacate the active runway . Actors GND controller | RWY controller Trigger Controller action Pre-condition The controller inputs the ‘Vacate’ clearance to an aircraft or a vehicle. Dialogue Action Result 1.a Single click AB on the ‘Vac’, or

‘Enter’ option in the callsign menu; 1b. Single click AB on the ‘Vac’, ‘Enter’ or ‘Transfer’ option on the e-strip

1a or 1b The runway border returns to it original colour (grey).

Requirement Ref. F.SN.RWY.4 | H.SN.RWY.2 Associated Procedures Following Previous Display Runway Occupied Associated HMI Objects Uses Particularities - Evolution Updated (Dec 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.8.8 Management of warnings

5.8.8.1 Display parking/stand occupied Procedure

Display Parking/Stand Occupied Objective To indicate to the controller that the parking/stand allocated to an arrival a/c is still

occupied. Actors GND controller | RWY controller Trigger System Generated Pre-condition The arrival aircraft landing event has been detected by the system or input by the

RWY controller.Should be automatically displayed when an arrival aircraft has its planned parking stand occupied.

Dialogue Action Result 1. At landing, the system checks if

the parking stand allocated to the arrival flight is occupied by another aircraft. The system compares the EIBT for the arrival aircraft with the TSAT of the departure aircraft.

1. if EIBT arrival aircraft < TSAT departure

aircraft, a. arrival aircraft: the ‘parking stand’ information (arrival flight) is replaced by ‘parking stand information – Hnn ’ (e.g. ‘S75-H07’), where nn represents the difference in minutes between EIBT and TSAT. The information is displayed in ‘warning’ colour wherever presented. b. departure aircraft: the stand (conflicting departure aircraft) is displayed in ‘warning’ colour

Requirement Ref. F.BL.SIL.04 Associated Procedures Following Change Parking Stand Previous - Associated HMI Objects Uses DEP E-STRIP| ARR E-STRIP | RADAR LABEL | EXTENDED RADAR LABEL Particularities - Evolution Implemented (July 2007)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.9 Management of mobile routing

5.9.1 Display Planned Route (aircraft and vehicle) Procedure

Display Planned Route Objective To display the planned route of an aircraft (dep, arr, towed) and assumed vehicle Trigger Controller action Pre-condition The mobile is known to the system Dialogue Action Result 1. By hovering the mouse over the

traffic symbol (i.e. radar track of a mobile)

For an aircraft: 1. The planned route of a non-assumed aircraft or an aircraft assumed but not cleared to taxi or an aircrfat cleared to land is displayed in white on the screen. 2. The planned route of an aircraft cleared to taxi is displayed in solid green on the screen. 3. The portion of cleared planned route is displayed in solid green and the part of the route that has not yet been cleared is displayed in dached green (e.g. when aircraft is cleared to pushbach, the portion of the initally planned route is displayed in solid green and the rest of the routeis displayed in dashed green). For a towed aircraft: 1. If it is a planned tow (assumed of not), then its planned route is displayed in solid green

Requirement Ref. F.ROUTE.DIS.1 Associated Procedures Previous Input Assume | Input new route Following Input Stop At Associated HMI Objects Initiated by - Uses RADAR TRACK Particularities - Evolution Updated (Dec. 08)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


5.9.2 Input a new route for a mobile Procedure

Input new route Objective To provide the controller with the possibility to modify the initial route of a mobile Actors RWY / GND controller Trigger Controller action Pre-condition The input new route is available when a mobile is assumed using the radar track

and mouse. Dialogue Action Result Single click AB on the radar track

and on the points of the airport where a mobile should taxi. IB click on the destination to finish the input

The new route replaces the initial one. It could be displayed by placing the cursor on the radar track of a mobile.

Requirement Ref. F.ROUTE.CHG.1 Associated Procedures Following Previous Input Assume | Display Planned Route Associated HMI Objects Initiated by Uses RADAR TRACK Particularities - Evolution Updated (Dec. 2007)

5.9.3 Input “Stop At” Procedure

Input Stop At Objective To provide the controller with the possibility to input a ‘stop at’ instruction to a

mobile (to clear an aircraft to taxi until a given point). Actors RWY / GND controller Trigger Controller action Pre-condition An initial planned route is assigned to a mobile. Dialogue Action Result 1a. Single click AB on the ‘Stop At’

option in the callsign menu. Then the controller selects the end point of the taxi clearance with the mouse. The system is informed of the clearance end point by a single AB click on the planned route; or

1b. Single click AB on the ‘Stop At’ option on the e-strip. Then the controller selects the end point of the taxi clearance with the mouse. The system is informed of the clearance end point by a single AB click on the planned route.

1a. or 1b. the ‘stop at’ menu opens and a white point on the planned route follows the movement of the cursor. The controller defines the taxi clearance limit by a single click AB on the planned route. The Stop at menu options are ‘Clear’ or ‘Close’. - ‘Close’ closes the ‘stop at’ menu - ‘Clear’ clears the taxi route until the selected end point (i.e. the white point is deblocked and it is possile to select a new taxi clearance limit)

Requirement Ref. F.ROUTE.ORD.1 Associated Procedures Following Previous Input Assume | Input Taxi | Input Vacate | Input tow | Input Hold Associated HMI Objects Initiated by CALLSIGN MENU

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Uses ARR E-STRIP | DEP E-STRIP | EXTENDED RADAR LABEL | RADAR LABEL | VEHICLE E-STRIP | VEHICLE RADAR LABEL | TOWED AIRCRAFT RADAR LABEL | TOWED AIRCRAFT E-STRIP |

Particularities - Evolution Implemented (Nov. 2008) and updated in Dec. 2008

5.10 Other functions

5.10.1 Display timer

Procedure Display Timer

Objective To enable the controller to count down a 1, 2 or 3 minutes time period. This is a manual count down timer.

Actors GND controller | RWY controller Trigger Controller Action Pre-condition - Dialogue Action Result 1. Single click AB on the ‘TIMER’

button in the GENERAL TOOL 1. The Time window opens at its default position.

Requirement Ref. Associated Procedures Following Move window | Close window Previous - Associated HMI Objects Uses Particularities - Evolution Updated (Dec. 2008)

5.10.2 Count down time Procedure

Countdown time Objective To count down a 1, 2 or 3 minutes period. This is a manual count down timer. Actors GND controller | RWY controller Trigger Controller Action Pre-condition Display timer window Dialogue Action Result 1. Single click AB on ‘1 MIN’, ‘2 MIN’

or ‘3MIN’ triggers the countdown 1. The Time starts to countdown. Time stops at 0:00.

Requirement Ref. Associated Procedures Following Move window | Close window Previous Display Timer Associated HMI Objects Uses Particularities - Evolution updated (Dec. 2008)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


6 Annex: ITWP Requirements This section reproduces ITWP functional and HMI requirements that lays the ground for ITWP design. References to these requirements are provided in designed procedures and objects.

6.1 Basic HMI elements and display management

6.1.1 WIMP graphical user management H.BL.HMI.01 The limits of the space of interaction with the system shall be clearly defined H.BL.HMI.02 The background colour and luminance of the worktop should be such as to: Provide good,

homogenous, contrast for all task related information, minimise flicker effects at the available screen refresh rate.

H.BL.HMI.03 There is a need to access more information than can instantaneously be presented on the surface of the display area, which can be made 'available' to a single controller.

H.BL.HMI.04 The general set of information than can potentially be presented, mixes graphical and textual sources and does not conform to a unique hierarchy, hence: The user shall be able to navigate freely amongst the available information sources, which implies that the user shall be able to: -Visualise the sources of information available (overview requirement) - Select/deselect and prioritise the information sources which are available - Flexibly and easily re-organise information within the display, including the possibility of a temporary undisplay.

H.BL.HMI.05 A window size need not be identical to the field of information, which can be viewed through it. This generates the need to change the viewpoint to access all the information in the field.

H.BL.HMI.06 The visual appearance of a window's structure should provide the controller with cues as to its behaviour and available properties.

H.BL.HMI.07 The nature of the window content should always be clearly indicated. H.BL.HMI.08 The background colour of the window interior should be such as to provide good contrast

for the displayed information. H.BL.HMI.09 At any moment, the locus of potential user actions shall be clearly indicated. H.BL.HMI.10 The type of system activity and the entry into a mode shall be clearly indicated. H.BL.HMI.11 At any moment, possible actions on the interface shall be clearly indicated. H.BL.HMI.12 The occurrence of events, which may lie outside of the user's current focus of attention,

shall be clearly indicated. H.BL.HMI.13 The cursor shall always be visible and easily located. H.BL.HMI.14 The cursor movement should be smooth and track input device (e.g. mouse) movements

without lags. No system activity should take priority over the cursor tracking relationship. H.BL.HMI.15 An easy and immediate access shall be provided at the HMI level to all the functions

available to the controller, allowing him to perform actions and to access tools and objects containing information.

H.BL.HMI.16 Buttons shall provide feedback specific to the action taken. H.BL.HMI.17 The physical appearance of the buttons shall provide the controller with information on

their functions and characteristics.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.BL.HMI.18 On request, the controller shall be provided with a set of selectable items amongst which he can make a selection to perform an action. Any one of the selectable items shall be easily and quickly accessed.

H.BL.HMI.19 The availability to selection, and the operational status of the presented menu items shall be clearly indicated.

H.BL.HMI.20 The currently selected menu item shall always be clearly indicated. H.BL.HMI.21 The menu item that is the most probable to be selected, depending on the context, shall be

very easily and quickly accessed. H.BL.HMI.22 The identity of the object that initiated the display of a menu shall be clearly indicated.

Depending on the context, it could be the aircraft, the particular field indication, etc. H.BL.HMI.23 The process of making a selection shall be completed by the selection action (i.e. no

supplementary action shall be necessary to close a menu). H.BL.HMI.24 It shall be possible to easily and quickly abandon any initiated menu dialogue without

having made a selection. H.BL.HMI.25 The system status shall always be clearly stated and indicated to the controller.

6.2 WIMP graphical user management

6.2.1 Access the CWP functions

6.2.1.1 Access / exit the CWP F.BL.LOG.01 It shall be possible to an authorised user to access any time the CWP functions. A

mechanism to ensure that only authorised users can access the CWP functions shall be provided. This mechanism shall be mandatory for access to the CWP functions.

F.BL.LOG.02 Only one access to the CWP functions at a time shall be allowed for each identified user. H.BL.LOG.01 The authorised user should be provided with an unambiguous and personalised access to the

CWP functions. H.BL.LOG.02 When accessing the CWP functions, the user should have access to the identity of all the

other users currently working on a CWP. F.BL.LOG.03 It shall be possible to a user to exit the CWP functions. H.BL.LOG.03 The user should be provided with the possibility to exit the CWP functions.

6.2.2 Manage the display layout

6.2.2.1 Set up the display and access screen settin gs F.BL.SET.01 It shall be possible to store the current CWP screen set-up.

The information stored shall be:

• the location, size and current priority of all open windows, including hidden windows,

• whether a window is (temporarily) iconified or not,

• the panning and zoom values of all windows equipped with this capability,

• the presence and position of any toolboxes and tools and of all settings selectable within tools.

• screen and global window settings.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.BL.SET.02 The maximum number of screen set-ups that can be stored at any one time shall be defined at the local level. The proposed default number is 3.

F.BL.SET.03 It shall be possible to access a stored screen set-up. F.BL.SET.04 A default screen set-up shall be defined for each control position at the local level. At

initialisation, the default settings should be presented, and the controller can then choose a previously stored configuration, or create a new one.

F.BL.SET.05 It shall be possible to delete a stored screen set-up, except for the default screen set-up. F.BL.SET.06 The interaction means with the system shall be adapted to both left and right handed users. H.BL.SET.01 At each control position, the controller should be provided with the possibility to store a

pre-defined number of screen and window configuration set-ups. H.BL.SET.02 The controller should be provided with an easy access to a previously stored screen and

window configuration set-up. H.BL.SET.03 The controller should be provided with an easy access to the default screen and window

configuration set-up. H.BL.SET.04 The controller should be provided with the possibility to delete a previously stored screen

set-up, by overwriting it with a newly defined screen set-up. H.BL.SET.05 It should not be possible to delete the default screen set-up. This impossibility should be

clearly indicated. H.BL.SET.06 The controller should have the choice of which previously stored screen set-up to

delete/overwrite when the maximum number of stored screen set-ups is attained. H.BL.SET.07 The fact that the maximum number of screen set-ups has been stored should be clearly

indicated. H.BL.SET.08 The controller should be allowed to easily and rapidly adapt the interaction means operation

to his own left-handed or right-handed use. F.BL.SET.07 It shall be possible to select amongst different lighting ambiance settings F.BL.SET.08 It shall be possible to fine tune brightness and contrast settings. H.BL.SET.09 The controller should be provided with a rapid and easy access to configure lighting

ambiance settings.

H.BL.SET.10 The controller should be provided with a rapid and easy means to fine tune brightness and contrast settings.

6.2.2.2 Manage toolbar functions F.BL.TOOL.01 The HMI shall provide individual access to each of the situation display monitoring

functions. H.BL.TOOL.01 A rapid and easy access should be provided to each of the TWR situation monitoring

functions. H.BL.TOOL.02 It should be possible to access individually each of the TWR view display monitoring

functions. The eventual grouping of the TWR view display monitoring functions should not hinder the access to each individual function.

6.2.3 Access air, surface and time information

6.2.3.1 Zoom, offset and modification of geographic al orientation F.BL.ZOOM.01 It shall be possible to change the situation display range (APP or Ground Situation Display),

without changing the size of the situation display

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.BL.ZOOM.02 The minimum and maximum zoom ranges shall be defined at the local level. H.BL.ZOOM.01 The controller should be provided with a composite picture which can zoom in to airport

scale and out to APP/en-route scale. H.BL.ZOOM.02 The controller should be provided with the possibility to change the situation display range

(APP or Ground situation display). The minimum and maximum zoom values, if any, should be clearly indicated.

F.BL.ZOOM.03 It shall be possible to store a particular zoom range associated with a particular map centre-point (zoom setting).

F.BL.ZOOM.04 The maximum number of zoom settings that can be stored at any one time shall be defined at local level. The proposed default number is 3.

H.BL.ZOOM.03 The controller should be provided with the possibility to store a pre-defined number of zoom settings.

H.BL.ZOOM.04 The fact that the maximum number of zoom settings has been stored should be clearly indicated.

F.BL.ZOOM.05 It shall be possible to access a stored zoom setting.

H.BL.ZOOM.05 The controller should be provided with the possibility to quickly and easily access a previously stored zoom setting.

F.BL.ZOOM.06 It shall be possible to delete a stored zoom setting.

H.BL.ZOOM.06 The controller should be provided with the possibility to delete a previously stored zoom setting.

H.BL.ZOOM.07 The controller should have the choice of which setting to delete when the maximum number of stored zoom settings is attained.

F.BL.ZOOM.07 It shall be possible to centre the situation display on any point chosen by the controller.

H.BL.ZOOM.08 The controller should be provided with the possibility to easily and rapidly re-centre the situation display on a chosen point.

6.2.3.2 Display surface information F.BL.MAP.01 It shall be possible to display and remove different types of surface information on the

ground situation display. F.BL.MAP.02 The number of airport 2D maps and the content of each map shall be defined at local level.

The proposed default display is the following:

• The taxiways,

• The runways,

• The terminals and other airport buildings,

• Aprons and gates,

• Stop bars H.BL.MAP.01 The controller should be provided with a rapid and easy access to the surface information

display or removal on the ground situation display. F.BL.MAP.03 It shall be possible to display / remove display parking names and associated location on the

ground situation display. H.BL.MAP.02 The controller should be provided with a rapid and easy means to display / remove display

parking names and associated location on the ground situation display, either permanently or temporarily.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.BL.MAP.04 It shall be possible to display / remove display taxiway names on the ground situation display, either permanently or temporarily.

H.BL.MAP.03 The controller should be provided with a rapid and easy means to display / remove display taxiway names on the ground situation window, either permanently or temporarily.

F.BL.MAP.05 If any, working areas should be automatically displayed on the ground situation window. H.BL.MAP.04 The controller should be provided with a rapid and easy means to remove display or re-

display working areas on the ground situation window. F.BL.MAP.06 It shall be possible to display / remove display the limits of RWY restricted areas (RWY

strips boundaries) according to LVP / non-LVP conditions. H.BL.MAP.05 The controller should be provided with a rapid and easy means to display / remove display

RWY strip boundaries according to LVP or non-LVP conditions. F.BL.MAP.07 It shall be possible to modify the geographical orientation of airport maps. H.BL.MAP.06 The controller should be provided with a rapid and easy means to modify the geographical

orientation of airport maps.

6.2.3.3 Display airspace information F.BL.MAP.08 It shall be possible to display and remove different types of airspace information on the

APP radar image. F.BL.MAP.09 The number of airspace maps and the content of each air map shall be defined at local

level. The proposed default display is the following: • The area of the sector(s) controlled on the position

• The waypoints and waypoint identifications

• The airways / airway centre-lines

• The military areas

• The coastlines

• The scale markers

• The range-rings. H.BL.MAP.07 The controller should be provided with a rapid and easy access to the airspace information

display or removal on the APP radar image.

6.2.3.4 Display time information F.BL.TIME.01 The UTC time shall be continuously provided to the controller with the precision of 1

second. H.BL.TIME.01 The display of the UTC time should be always available.

6.2.3.5 Display additional view F.BL.VIEW.01 It shall be possible to display additional composite situation view (picture in picture) on the

situation display. F.BL.VIEW.02 The maximum number of additional sub-views that can be displayed shall be defined at the

local level. The proposed default number is 2. H.BL.VIEW.01 The controller should be provided with a rapid and easy means to display / remove display

additional sub-views on the situation display.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


6.2.3.6 Display and track range and bearing F.BL.RB.01 It shall be possible to obtain range and bearing information as measured from one point of

the airspace to another.

H.BL.RB.01 The controller should be provided with a rapid and easy access to the Range and Bearing function allowing obtaining precise range and bearing information as measured from one point of the airspace to another.

H.BL.RB.02 The controller should be provided with a rapid and easy way of leaving the Range and Bearing function.

H.BL.RB.03 The controller should be provided with feedback when the Range and Bearing function is active or not.

F.BL.RB.02 It shall be possible to monitor over time the change in relative range and bearing over time of two points, one or both of which are dynamic (an aircraft and a fixed point, or two aircraft).

F.BL.RB.03 The maximum number of trackers linking two points that can be displayed at the same time on the Composite Situation Display shall be defined at the Centre level. The proposed default number is 5.

H.BL.RB.04 The controller should be provided with a rapid and easy access to the Tracker link function allowing to monitor over time the change in relative range and bearing over time of two points, one or both of which are dynamic (an aircraft and a fixed point, or two aircraft).

H.BL.RB.05 The controller should be provided with a rapid and easy way of leaving the Tracker Link function.

H.BL.RB.06 The controller should be provided with feedback when the Tracker link function is active or not.

H.BL.RB.07 The fact that the maximum number of Tracker links has been displayed should be clearly indicated.

F.BL.RB.04 It shall be possible to remove the displayed range and bearing information. H.BL.RB.08 The controller should be provided with a rapid and easy way of removing the displayed

range and bearing information. F.BL.RB.05 It shall be possible to display and to monitor over time the estimated time of flight of an

aircraft between its current position and a fixed point of the airspace. H.BL.RB.09 The controller should be provided with a rapid and easy access to the estimated time of

flight of an aircraft to a fixed point of the airspace. H.BL.RB.10 The controller should be provided with the possibility to express the estimated time of flight

of an aircraft to a fixed point of the airspace in a format best suited to his need.

6.2.4 Manage the display features of traffic repres entation

6.2.4.1 Manage the radar label position F.BL.POS.01 An 'on-off' automatic radar label anti-overlap function shall be provided to the controller.

The automatic function shall find for each radar label (aircraft or vehicle) the optimum display position free of overlap with other radar labels or with other displayed information, taking into account a set of constraints and parameters defined at the anti-overlap algorithm configuration level.

H.BL.POS.01 The controller should have the possibility to choose whether to use the automatic radar label anti-overlap function: the function should be activated and de-activated only on controller's request. The access to the activation/deactivation should be immediate, and the controller should be provided with feedback whether the automatic anti-overlap is active or not.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.BL.POS.02 It shall be possible to modify some of the algorithm configuration parameters to adapt them to the local needs. At the minimum, it should be possible: • To change the radar label position relative to the aircraft track symbol. • To change the length of the leader line of all the radar labels. • To set the top of the screen as reference for the orientation of the radar labels. • To set the aircraft track as reference for the orientation of the radar labels.

H.BL.POS.02 The controller should have the possibility to adapt easily and quickly some of the algorithm configuration parameters to his own needs.

F.BL.POS.03 In the manual label positioning mode, it shall be possible to choose a frame of reference for the display of all radar labels in a given orientation with respect to this reference. Proposed references are:

• Variable reference: aircraft heading • Fixed reference: the top of the screen, providing the possibility to display the radar

label with different angles relative to this fixed reference. H.BL.POS.03 At any moment, the controller should have the possibility to choose between the proposed

frames of reference for the manual monitoring of all the radar labels' position. F.BL.POS.04 In the manual label positioning mode, it shall be possible to set the position of the displayed

radar labels to a given orientation with respect to a specified reference. H.BL.POS.04 At any moment, the controller should have the possibility to manually set the orientation of

all the displayed radar labels, within a given frame of reference. F.BL.POS.05 In the manual label positioning mode, it shall be possible to change the length of the

displayed radar labels' leader lines. H.BL.POS.05 At any moment, the controller should have the possibility to manually set the leader line

length of all the displayed radar labels. Several lengths of the leader line should be available, allowing changing the position of the labels without modifying their direction with respect to the aircraft track.

F.BL.POS.06 It shall be possible to manually move any individual label, independently of either the automatic anti-overlap algorithm operation, or the global manual setting of label position.

H.BL.POS.06 At any moment, it should be possible to move a particular radar label anywhere on the radar image. The leader line should automatically extend and reposition to maintain the link between the label and the aircraft or vehicle position symbol. The minimum length of the leader line should be long enough to avoid overlapping of the label with the position symbol. There should be no limitation of the leader line orientation or maximum length, allowing the controller to find an adequate position for the label.

F.BL.POS.07 A label, manually put in a certain position, should be avoided by the labels which are monitored by the automatic radar label anti-overlap function.

F.BL.POS.08 It shall be possible to put the individually moved labels in conformance with the rules defined within the global setting of label position, or to take them off the global setting so that they stay in the controller-defined position.

H.BL.POS.07 At any moment, the controller should have the choice of including or not the individually moved labels into the global label position setting.

H.BL.POS.08 Any manual global or individual positioning of labels should be easy and rapid to perform.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


6.2.4.2 Manage tracks and labels

6.2.4.2.1 Display speed vectors F.BL.VECT.01 It shall be possible to display (remove display) a speed vector, corresponding to a given

number of minutes of flight time for all the aircraft. H.BL.VECT.01 The controller should be provided with an easy and rapid way to configure the speed vector

length for all the aircraft tracks. F.BL.VECT.02 The possible display values of the overall and individual speed vector shall be defined at

local level. The proposed default values are 0, 1, 2, 3, 4, 5 minutes. H.BL.VECT.02 The speed vector should not be 'confusable' with the leader line of the air aircraft radar

label.

6.2.4.2.2 Display aircraft and vehicle representation F.BL.TRCK.01 It shall be possible to distinguish between aircraft and vehicles symbols. H.BL.TRCK.01 Aircraft and vehicles track symbols should be different so that the controller should clearly

distinguish between them. F.BL.TRCK.02 It shall be possible to distinguish between light, medium and heavy aircraft categories on

the situation display. H.BL.TRCK.02 Three sizes of dots should be displayed to the controller to represent light, medium and

heavy aircraft categories F.BL.TRCK.03 It shall be possible to display the aircraft shape in a quick look mode. H.BL.TRCK.03 The controller should be provided with the ability to enable/disable the display of aircraft

shape in a quick look mode. F.BL.TRCK.04 It shall be possible to display a given number of trail dots for all the aircraft. F.BL.TRCK.05 The number of trail dots that can be displayed shall be defined at local level. The proposed

default number is 0, 1, 2, 3, 4, 5. H.BL.TRCK.04 The controller should be provided with an easy and rapid way to configure the number of

trail dots for all the aircraft tracks.

6.2.4.2.3 Configure the radar labels F.BL.LBL.01 It shall be possible to configure the content of radar labels by displaying and removing

additional data. F.BL.LBL.02 It shall be possible to configure independently the selected format of radar labels (aircraft

and vehicles) from the minimum format, by displaying and removing additional data.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.BL.LBL.03 The minimum and selected data to be displayed in the radar labels shall be defined at local level.

The proposed default set for the minimum label is the following:

a) for a departure aircraft: callsign, departure parking/stand, clearance limit

b) for an arrival aircraft: callsign, arrival parking/stand.

c) for a towed aircraft: callsign

d) for a vehicle: callsign

The proposed default set for the selected label is the following: a) for a departure aircraft callsign, departure parking/stand, clearance limit, altitude

(when airborne), true air speed (when airborne), type of aircraft, RWY, SID, CTOT, weight vortex category, departure sequence number.

b) for an arrival aircraft: callsign, aircraft type, arrival parking/stand, altitude (when airborne), true air speed (when airborne), RWY, type of aircraft, weight vortex category, arrival sequence number.

c) for a towed aircraft: callsign, aircraft type, departure stand, arrival stand.

d) for a vehicle: callsign, operational role and ground route

F.BL.LBL.04 It shall be possible to configure the content and position of fields in the radar label. H.BL.LBL.01 The controller should be provided with a rapid and easy way to configure the content of

minimum and selected radar labels by adding or removing data fields.. H.BL.LBL.02 The content of radar labels should be configurable according to operator role. H.BL.LBL.03 The colours associated to arriving and departing traffic should be different. At least the

callsign, symbol and the leader line should have the same colour. H.BL.LBL.04 The colours associated to vehicles should be different from the associated to the arriving

and departing traffic.

6.2.4.2.4 Filter out groups of tracks F.BL.FILT.01 It shall be possible to select category(ies) of aircraft tracks to be displayed. F.BL.FILT.02 The default categories of aircraft tracks to be displayed shall be defined at local level. H.BL.FILT.01 The controller should be provided with the possibility to set/select groups of aircraft tracks

to be displayed.

6.2.4.2.5 Draw attention to a specific aircraft or vehicle F.BL.WAR.01 It shall be possible to input an intra-sector warning marking on an aircraft or vehicle. H.BL.WAR.01 The controller should be provided with an easy and rapid way to mark an aircraft or vehicle

for herself/himself as an 'aide memoire'. F.BL.WAR.02 It shall be possible to share an aircraft or vehicle marking with the next sector controller

unit. H.BL.WAR.02 The controller should be provided with an easy and rapid way to share an aircraft or vehicle

marking with the next controller unit. If input, this warning should be provided even if the aircraft or vehicle is not yet visible on the controller's ground situation display.

F.BL.WAR.03 It shall be possible to remove an intra-sector warning marking on an aircraft or vehicle.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.BL.WAR.03 The controller should be provided with an easy and rapid way of removing the displayed intra-sector warning.

6.3 Access data concerning the current traffic situ ation

6.3.1 Select an aircraft or vehicle F.BL.SEL.01 It shall be possible to select or deselect an individual aircraft or vehicle. H.BL.SEL.01 The controller should be able to select an aircraft or vehicle by placing the cursor on its

representation. It is proposed that aircraft or vehicle representation would be accessed a) either through its label or on its track. b) or traffic data representation.

H.BL.SEL.02 Only one aircraft or vehicle should be possible to select at any instant within the interface of

a single controller. H.BL.SEL.03 Selecting an aircraft or vehicle should:

a) Highlight all the available representations of that traffic wherever such information appears, allowing for an easy location of the traffic information.

b) Show the radar label in the appropriate selected format.

H.BL.SEL.04 De-selecting an aircraft or vehicle should: a) Deselect the previously highlighted traffic representation. b) Revert the radar label to its minimum form

H.BL.SEL.05 Selection is a necessary pre-condition for interaction with an aircraft or a vehicle or its data.

Only interactive fields should be highlighted when accessed with the input/output device.

6.3.2 Display traffic representation F.BL.TRAF.01 The controller shall be provided with a clear representation of the traffic (i.e. aircraft and

vehicles) helping the controller to easily locate and identify aircraft and vehicles and to have a direct access to essential information.

F.BL.TRAF.02 The traffic representation shall be updated following: a) Updates of the surveillance system

b) Controller or system initiated update of data.

H.BL.TRAF.01 Aircraft and vehicle representation should be provided in a format helping the controller to

easily locate and identify the traffic and to have direct access to essential information. The relation between traffic representation and information concerning that traffic should be unambiguous.

H.BL.TRAF.02 To avoid screen congestion and minimise overlap of displayed information, the permanently displayed traffic data should be only the minimum information needed by the controller. Minimum traffic information data shall be defined at local level.

F.BL.TRAF.03 The controller shall be provided with a clear indication that a traffic is: a) Entering her/his area of responsibility; b) Being under her/his responsibility; c) Leaving her/his area of responsibility

H.BL.TRAF.03 The planning state of the aircraft/ vehicle should be clearly indicated.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.BL.TRAF.04 Temporary ('quick look') presentation of any of the additional traffic data should be allowed.

H.BL.TRAF.05 The traffic representation should be updated on the controller's display following: a) updates of the surveillance system b) controller or system initiated update of traffic data.

F.BL.TRAF.04 The cooperative status of traffic should be indicated on the traffic representation. H.BL.TRAF.06 The controller should be provided with a clear and visible indication of traffic cooperative

status.

6.3.2.1 Access all traffic entering or planning to enter a controller’s area of responsability

F.BL.SIL.01 Traffic data related to aircraft and tow aircraft entering or planned to enter controller’s area of responsibility shall be presented to the controller.

F.BL.SIL.02 Traffic Data Items shall be grouped in one or several Traffic Data Lists. Displayed Traffic Data Items displayed at each working position shall include:

a) Traffic that will become under control responsibility in the near future, and b) Traffic under responsibility control for that position.

H.BL.SIL.01 All Traffic Data Items pertinent to a controller should be presented in a clear and pre-

defined format(s) that help her/him to prioritise planning and control actions. Depending on operational needs, traffic data shall be highly configurable with regard to layout, size, shape, fonts, colours and interaction capability.

H.BL.SIL.02 Traffic under the control area responsibility of a controller at a particular working position should be clearly distinguished from traffic which is not under her/his control responsibility.

F.BL.SIL.03 Traffic Data Items shall be represented in minimum format or extended format based on controllers’ choice. It shall be possible to configure independently the extended format of Traffic Data Items from the minimum format, by displaying and removing additional data.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.BL.SIL.04 Traffic Data Items fields to be displayed in minimum format shall be defined at local level.

The proposed default sub-set is the following: a) for an arrival flight: - ELDT (i.e. Estimated LanDing Time, when estimated) or ALDT (Actual Landing Time) - Aircraft callsign - Aircraft type - Wake Vortex category - Stand identification + Waiting time indication (if the stand is occupied) - IFR or VFR flight indicator - Time to touchdown - Indication of last clearance / instruction - Runway - Runway sequence number b) for a departure flight: - TTOT (Target Take-Off Time) or ATOT (Actual Take Off Time) - Aircraft callsign - Aircraft type - Wake vortex category - Stand - SID or VFR indicator - CTOT (Calculated Take Off Time) and Ready Message indicator - Indication of last clearance / instruction - Runway - Runway sequence number c) for a towed aircraft: - Aircraft callsign - Aircraft type - Stand - Runway - Estimated Start Taxi Time

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.BL.SIL.05 Traffic Data Items fields to be displayed in extended format shall be defined at local level.

The proposed default sub-set is the following: a) for an arrival flight: - EIBT (Estimated In-Block Time) or AIBT (Actual In-Block Time) - Airline name - SSR code - Aerodrome of departure - QNH - Remarks b) for a departure flight: - EOBT or TOBT or AOBT (Estimated or Target or Actual Off Block Time) - Airline name - SSR code - Aerodrome of destination - QNH - Remarks c) for a towed aircraft: - Aircraft callsign - Aircraft type - Stand - Runway - Estimated Start Taxi Time

F.BL.SIL.06 The controller shall be able to expand the format of a displayed Traffic Data Item to access additional data. By default, Traffic Data Items should be presented under normal (minimum) format.

H.BL.SIL.03 Extended Traffic Data Item information should be available on controller request. The presentation format should be fixed, allowing the controller to easily find an information. Access to additional information should be simple and rapid.

F.BL.SIL.07 It shall be possible for the controller to sort displayed Traffic Data Items either manually or in a semi-automatic mode acording to criteria. The proposed criteria are chronological and alphabetic (callsign).

H.BL.SIL.04 The controller should be provided with an easy means to sort out Traffic Data Items displayed in a Traffic Data List, either manually or according to configurable criteria. By default, Traffic Data Items should be sorted chronologically.

F.BL.SIL.08 The movement of traffic data items from one position to another one in the same Traffic List or to a different traffic list on the same control position shall be exclusively triggered on a controller action.

F.BL.SIL.09 It should be possible to create a new traffic data item. H.BL.SIL.05 The controller should be assisted to create a new traffic data item

a) either by selecting a pre-defined model (departure, arrival, towed, vehicle model), or

b) by copying an existing one and modify subsequent data F.BL.SIL.10 It shall be possible to archive Traffic Data Items, either

a) on controller decision, or b) automatically after AIBT (for arrivals) or after ATOT (for departures);

F.BL.SIL.11 It shall be possible to display all archived traffic data items either in a fixed or quick look mode.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


6.4 Access weather / advisory information F.BL.WEA.01 It shall be possible to access to weather information, minimum and additional.

a) The proposed minimum information includes surface wind direction (touch down) and strength (graphical and text), QNH (mb), ATIS code, temperature and dew point

b) Additional information should be defined at local level and can include information such as surface wind (Touch Down and Stop End) , visiblity, current weather, cloud ceiling, QNH and QFE (mb and inches), weather forecast information, RVR conditions and a remarks section.

H.BL.WEA.01 Minimum weather information should always be displayed and available to the controller

and includes (per runway): surface wind direction (touch down) and strength (graphical and text), QNH (mb), ATIS code, temperature and dew point

H.BL.WEA.02 The controller should be provided with an easy means to access to additional weather information that should include surface wind (Touch Down and Stop End) , visiblity, current weather, cloud ceiling, QNH and QFE (mb and inches), weather forecast information, RVR conditions and a remarks section. The display should be provided either on controller request or automatically triggered on specific events defined at local level.

6.5 Set up the airport layout F.BL.APT.01 It shall be possible to input the status of the runways and taxiways. H.BL.APT.01 The controller should be provided with an easy means to access / modify the status of the

RWY and taxiways (active / closed).

6.6 Update system data concerning the current traff ic situation

6.6.1 Update system data according to controller cl earances F.BL.ORD.01 Deleted (June 07) H.BL.ORD.01 Deleted (June 07) F.BL.ORD.02 It shall be possible to input a “cleared to land” instruction. H.BL.ORD.02 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a cleared to land instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.03 It shall be possible to input a “go-around” instruction for an aircraft. H.BL.ORD.03 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a go-around instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.04 It shall be possible to input a “vacate” instruction H.BL.ORD.04 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a vacate instruction for an aircraft or vehicle. The aircraft/vehicle representation should account for this instruction.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.BL.ORD.05 Requirement moved to chapter “ Management of mobiles on runway” see F.SN.RWY.2 (Dec. 2008)

H.BL.ORD.05 Requirement moved to chapter “ Management of mobiles on runway” see H.SN.RWY.2 (Dec. 2008)

F.BL.ORD.06 It shall be possible to input a “taxi” instruction. H.BL.ORD.06 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a taxi instruction for an aircraft or vehicle. The aircraft/ vehicle representation should account for this instruction.

F.BL.ORD.07 It shall be possible to input a “start up” engines instruction H.BL.ORD.07 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a start-up instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.08 It shall be possible to input a “pushback” instruction H.BL.ORD.08 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a pushback instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.09 It shall be possible to input a “hold” instruction H.BL.ORD.09 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a hold instruction for a mobile. The mobile representation should account for this instruction.

F.BL.ORD.10 It shall be possible to input a “line-up” instruction. H.BL.ORD.10 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a line-up instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.11 It shall be possible to input a “conditional line up” instruction H.BL.ORD.11 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a conditional line up instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.12 It shall be possible to input a “cleared for take off” instruction H.BL.ORD.12 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a cleared for take-off instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.13 It shall be possible to input an “abort take-off “ instruction. H.BL.ORD.13 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input an abort take-off instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.14 It shall be possible to input a “En-route clearance” instruction H.BL.ORD.14 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input an en-route clearance instruction for an aircraft. The aircraft representation should account for this instruction.

F.BL.ORD.15 It shall be possible to cancel the latest given order / instruction to an aircraft. H.BL.ORD.15 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to cancel the last given instruction to an aircraft. F.BL.ORD.16 It shall be possible to input a “hold at” instruction.

Note: The objective is to implement a function that enables the controller to clear an arrival aircraft, after landing, to taxi until a certain point. For the CDG airport layout, the instruction “hold at” is used. For other airports, another instruction could be associated to this function.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.BL.ORD.16 Depending on the controller role and flight control responsibility, the controller should be provided with an easy means to input a “hold at” instruction for an aircraft. The aircraft representation should account for this instruction.

6.6.2 Update system data according to traffic data modifications F.BL.UPD.01 It shall be possible to modify traffic data items fields. Only the controller role having a

traffic under control responsibility shall be able to access to modifiable fields. H.BL.UPD.01 Traffic data item fields that can be subject to interaction by the controller should be clearly

indicated. H.BL.UPD.02 Only available options for interaction should be displayed. Such options depend on the

flight planning state and previously issued clearances for the flight H.BL.UPD.03 The controller shall be provided with a visible indication when modifications are made to a

displayed traffic data item. H.BL.UPD.04 A visible indication shall be provided on a traffic data item when a flight has been cancelled

or delayed. H.BL.UPD.05 Modification of traffic data on one control position shall lead to update this information

wherever it is available. F.BL.UPD.02 Depending on traffic responsibility, it shall be possible to modify traffic data item fields:

a) Departure RWY, Departure parking /stand, SID and aircraft type (departure flight) b) Arrival Runway, Arrival parking/stand and aircraft type (arrival flight) c) Arrival and departure parking / stands (towed aircraft)

F.BL.UPD.03 It shall be possible to log the actual times of arrival or departure for each aircraft under responsibility.

H.BL.UPD.06 The controller should be provided with an easy means to log departure and arrival times of traffic under responsibility either manually (controller action) or automatically (detection of take-off or landing event).

F.BL.UPD.04 It shall be possible for the controller to input or modify a free remark (‘remarks’ field) on a traffic data item when a traffic is under her/his responsibility.

H.BL.UPD.07 The controller should be provided with visual indication that a remark has been input for a traffic by the preceding control position.

H.BL.UPD.08 The controller should be provided with an easy way to input free text. F.BL.UPD.05 It shall be possible for the controller to display a remark on a traffic data item.

6.7 Flight plan edition

6.7.1 Create a flight plan F.BL.FPL.01 It shall be possible to manually create a new flight plan H.BL.FPL.01 The controller should be provided with an easy and simple means to manually create a new

flight plan H.BL.FPL.02 At any Step of a new flight plan creation the controller should be assisted by the system by

indication of data to be input, data available for input, erroneous data, possible actions, forbiden actions.

F.BL.FPL.02 The controller should have the possibility to create a flight plan from a copy of an existing flight plan and subsequent modification of the data.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.BL.FPL.03 The controller should be provided with an easy and simple means to copy an existing traffic data item

F.BL.FPL.03 The controller should have the possibility to correct or delete a previously saved flight plan H.BL.FPL.04 Flight plans that have been saved by the controller and can be deleted or corrected should be

clearly identified. H.BL.FPL.05 The deletion of a saved flight plan should be confirmed by the controller.

6.7.2 Modify a flight plan F.BL.FPL.04 The controller shall have the possibility to display the flight plan data of any existing flight

plan H.BL.FPL.06 The controller should be provided with an easy and simple access to the display a flight

plan. F.BL.FPL.05 The controller shall have the possibility to manually modify flight plan elements H.BL.FPL.07 Flight plan elements that can be modified by the controller should be clearly indicated

6.8 System supported data exchange and coordination

6.8.1 Traffic data distribution between positions F.FD.RUL.01 Arrival traffic data shall be displayed on the RWY arrival control position at a time

parameter before expected landing time (ELDT). The proposed time parameter should be defined at local level.

F.FD.RUL.02 Based on local decision, Arrival traffic data shall be displayed on concerned GND control position(s) either at a time parameter before expected landing time or based on an identified RWY controller action/clearance for that flight. The proposed time parameter should be defined at local level.

F.FD.RUL.03 Based on local decision, Departure traffic data item shall be displayed on concerned GND position(s) either at a time parameter before expected off block time (EOBT) time or based on an identified controller action/clearance for that flight. The proposed time parameter should be defined at local level.

6.8.2 Transfer of control responsibility F.FD.TRSF.01 It shall be possible to modify the control responsibility for an aircraft or vehicle, and

transfer control responsibility to other operator roles in the system H.FD.TRSF.01 The controller should be provided with easy means to modify or transfer the control

responsibility for an aircraft to other operator roles. Transfer of control responsibility should be possible trough any representation of the aircraft / vehicle.

F.FD.TRSF.02 Transfer of control responsibility shall consist of two actions: transfer (to transfer traffic to default next operator role) and assume (to assume traffic).

H.FD.TRSF.02 The controller should be provided with an easy and visible way to indicate that transfer of control responsibility has been initiated on both giving and receiving control positions.

F.FD.TRSF.03 It shall be possible to transfer a flight to another controller role than planned in the pre-defined sequence.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.FD.TRSF.03 The controller should be provided with an easy means to transfer control responsibility of any traffic to a control position different from the pre-defined one

F.FD.TRSF.04 After successful transfer of a flight or vehicle to another controller role, it shall remain under control of the former controller until the latter assumes it, that completes the transfer.

H.FD.TRSF.04 When transferred by another operator role, the controller should be provided with an easy way to assume an aircraft or vehicle.

H.FD.TRSF.05 Visible indication of completion of a flight or vehicle transfer/assume control responsibility shall be provided on both assuming and transferring operator roles.

6.9 Vehicle management

6.9.1 Display / hide vehicles F.VEH.DIS.1 It shall be possible to display / remove the apron mask area limit. H.VEH.DIS.1 The controller should be provided with a rapid and easy means to display / remove the

apron mask area limit. F.VEH.DIS.2 It shall be possible to hide / show all the vehicles on the apron. H.VEH.DIS.2 The controller should be able to easily hide or show all the vehicles on the apron. Only

previously selected vehicles should be highlighted. By default, all the vehicles shall be hidden.

6.9.2 Instruction to vehicle F.VEH.ORD.1 It shall be possible for the controller to assume a vehicle and to have it on the frequency. F.VEH.ORD.2 It shall be possible to input a “Tow “ instruction for a towed aircraft. H.VEH.ORD.1 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a tow clearance instruction for a towed aircraft. The aircraft representation should account for this instruction.

F.VEH.ORD.3 It shall be possible to input a “REL “ instruction for a vehicle / towed aircraft. H.VEH.ORD.2 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a release clearance instruction for a vehicle / towed aircraft.

6.10 Monitoring and Control Functions

6.10.1 Surface hazardous situations detection and a lerting

6.10.1.1 Introduction to hazardous situations in th e surface management

F.SN.GEN.1 An alert associated with a detected conflict should be provided with an adequate time and brought to the attention of the controller (ALARM coding). An alert associated with a predicted conflict (INFORMATION coding) should also be provided.

F.SN.GEN.2 A visual display of an alert associated with a detected or predicted hasardous situation should be provided to the controller .

H.SN.GEN.1 Alerting and warning systems shall be unambiguous, with a clear indication of the cause of the alert.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.SN.GEN.2 The controller should be provided with a consistent visual display of alerts on the interface. The display of alert should be given in the radar label, on the e-strip, on the A-SMGCS display and around the track symbol.

F.SN.GEN.3 Auditory signals in conjunction with alerts should only be used when immediate action is required, with auditory alerts only competing when it is absolutely necessary.

H.SN.GEN.3 The controller should be provided with an audio signal to support identification of alarms. F.SN.GEN.4 The controller on the GND and RWY position shall be provided with all alert messages and

auditory signal when they are triggered. H.SN.GEN.4 The controller should be provided with the same visual and audio coding of the alerts on the

GND and RWY position. F.SN.GEN.5 Only the controller responsible for handling the potential hazardous situation should be able

to acknowledge the alert on his position. H.SN.GEN.5 The controller shall be provided with means to easily acknowledge perception of visual and

sound alert messages. The acknowledgment of alerts should not impact the safety situation. H.SN.GEN.6 The controller shall not be allowed to cancel an alarm (i.e. remove the display of the alarm

on the screen before it has been resolved). F.SN.GEN.6 The end of an alert shall be automatically triggered when the corresponding triggering

conditions are no more fulfilled. H.SN.GEN.7 The controller shall be provided with clear and visible information about the end of the alert

as soon as the alert ends. H.SN.GEN.8 An alert associated with a detected conflict should be provided with an adequate time and

brought to the attention of the controller (alarm coding). An alert associated with a predicted conflict (information coding) should also be provided.

6.10.1.2 Detection of non conformance to ATC instru ctions / procedures (PROC15)

F.SN.PROC.1 F.SN.CNF.1

It shall be possible to detect and display non conformance to ATC instructions. H.SN.PROC.1 H.SN.CNF.1

The controller shall be provided with clear and visible indication of non conformance to ATC instructions as soon as they exist.

H.SN.PROC.2 H.SN.CNF.2 An alert shall be automatically triggered in case a non conformance to ATC instructions is detected, when: a) An aircraft deviates from a cleared route on a taxiway (INFORMATION alert) b) An aircraft does not stop at clearance limit; if the clearance limit is the runway holding point, an ALARM alert shall be triggered; in other clearance limit cases, an INFORMATION alert shall be triggered. c) An aircraft stays stationary a time parameter after take-off, line up or cross given clearances (INFORMATION / ALARM alert). The proposed time parameter should be defined at local level.

H.SN.PROC.3 H.SN.CNF.3

An alert shall be automatically triggered in case non conformance to ATC instructions is detected, when:

15 Airport Safety Nets, Alerts Category 1: Non-conformance to ATC instructions/procedures

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


a) An assumed vehicle deviates from cleared route on a taxiway (INFORMATION) b) An assumed vehicle does not stop at clearance limit. ; c) An assumed vehicle stays stationary in the runway protected area

F.SN.PROC.2 F.SN.CNF.2 It shall be possible to detect and display if an aircraft taxiies with excessive speed16

H.SN.PROC.4 H.SN.CNF.4 The controller shall be provided with clear and visible indication when an aircraft is taxiing at speed > X knots.


An INFORMATION alert shall be automatically triggered when an excessive aircraft taxi speed is detected (speed > X knots).


An ALARM alert shall be automatically triggered when an excessive aircraft taxi speed is detected (speed > Y knots, X>Y).


It shall be possible to detect and display if an aircraft is stationary in the RWY protection area.

H.SN.PROC.7 H.SN.CNF.7 The controller shall be provided with clear and visible indication when an arrival aircraft is stationary (i.e. stops for more than a time parameter) in the RWY protection area. The proposed time parameter should be defined at a local level.


An alert ALARM shall be automatically triggered when an arrival stationary aircraft is detected in the runway protection area.


An alert INFORMATION shall be automatically triggered when a stationary mobile is detected in the runway protection area without interaction with a surrounding traffic.

F.SN.PROC.4 F.SN.CNF.4 It shall be possible to detect and display if an aircraft or a vehicle is entering a runway without clearance.


The controller shall be provided with clear and visible indication when an aircraft or vehicle is entering a runway without clearance.


An alert ALARM shall be automatically triggered when an aircraft or vehicle is entering a runway without clearance.


It shall be possible to detect and display if an aircraft on short final has not been cleared to land after it passes a certain point.


The controller shall be provided with clear and visible indication when an arrival aircraft on short final has not been cleared to land after it passes a certain point (distance/altitude from runway threshold).


An alert ALARM shall be automatically triggered when an arrival aircraft on short final has not been cleared to land after it passes a certain point (distance/altitude from runway threshold).

16 an excessive speed is a parametre to be defined at a local level

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft



It shall be possible to detect when an aircraft crosses the red stop bar. H.SN.PROC.14 H.SN.CNF.14

The controller shall be provided with clear and visible indication when an aircraft crosses a red stop bar.


An alert ALARM shall be automatically triggered when an aircraft crosses a red stop bar. F.SN.PROC.7 F.SN.CNF.7

It shall be possible to detect and display if an aircraft takes-off without clearance. H.SN.PROC.16 H.SN.CNF.16

The controller shall be provided with clear and visible indication when an aircraft is taking- off without clearance.


An alert INFORMATION shall be automatically triggered when an aircraft is taking off without clearance and there is no implication with the surrounding traffic.


An alert ALARM shall be automatically triggered when an aircraft is taking off without clearance and a mobile is on the RPA (crossing or entering the same runway).


It shall be possible to detect and display if an arrival aircraft is not lined up on final on assigned landing runway.


The controller shall be provided with clear and visible indication when an arrival aircraft is not lined up on final on the assigned landing runway.


An alert ALARM shall be automatically triggered when an arrival aircraft is not lined up on final on the assigned landing runway.

6.10.1.3 Detection of conflicting ATC clearances (C LRS17) Note: the former requirements referenced F.SN.CLR.YY and H.SN.CLR.YY have been replaced respectively with F.SN.CLRS.YY and H.SN.CLRS.YY. F.SN.CLRS.1 F.SN.CLR.1

It shall be possible to detect and display manual inputs of inconsistent clearances. H.SN.CLRS.1 H.SN.CLR.1

The controller shall be provided with clear and visible indication of inconsistency between manually input clearances as soon as they exist.

17 Airport Safety Nets, Alerts Category 2: Conflicting ATC clearances

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.SN.CLRS.2 H.SN.CLR.2 An ALARM shall be automatically triggered when inconsistent clearances input occur. Triggering conditions are as follows:

a/c 1 a/c 2

Line-up Cross/Enter Take-Off Landing

Line-up Yes if a/c are LUP from the same or adjacent holding points on the same runway (if the multiple line-up is forbiden). In case of authorised multiple line-up, if the sequence order displayed on the EFPS is different from the actual sequence of aircraft with LUP CLR (already lined-up or not) then INFORMATION (5) , (8)

Yes if ac2* is in front of ac1

Yes (6)

Cross/Enter Aircraft with CROSS/LUP but another aircraft on final within T1+15”

(8) Yes if a/c2(*) is in

front of a/c1

Yes(*)

(6)

Take-off Yes if a/c1 is in front of a/c2

Yes if a/c1(*) is in front of a/c2

Yes (1), (2), (5)

Yes (6)

Landing Yes Yes(*) Yes (4), (5)

Yes (3)

(*) applies to aircraft and vehicle (1) if converging runways and converging trajectories then TOF vs. TOF => ALARM (2) if intersecting runways and converging trajectories then TOF vs. TOF => ALARM (3) if intersecting runways and converging trajectories then LND vs. LND => ALARM (4) if intersecting runways and converging trajectories then TOF vs. LND => ALARM (5 ) LUP/LUP, TOF/TOF and LND/LND shall triger an ALARM if two aircraft are cleared on two opposite runway directions (on the same runway but on the opposite threshold) => ALARM. (6) if an aircraft is cleared to CROSS/LUP/TOF and the other aircrfat is cleared to LND on the opposite direction on the same runway => ALARM (7) if an aircraft is cleared to TOF and another aircarft is cleared to TOF/CROSS/ENTER/LUP on the same runway => ALARM (8) CROSS/LUP vs. CROSS/LUP: if on taxiways in opposite direction => ALARM

H.SN.CLRS.3 H.SN.CLR.3

The controller shall be provided with clear and visible indication when the manually input inconsistent clearances have been corrected. A visual display of an alert shall be removed when the triggering conditions are not fullfieled.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


6.10.1.4 Detection of infringement of restricted / closed areas (AREA 18)

6.10.1.4.1 Runway conflicts detection and alerting Note: the former requirements referenced F.SN.RCA.YY and H.SN.RCA.YY have been replaced with F.SN.AREA.YY and H.SN.AREA.YY respectively. F.SN.AREA.1 F.SN.RCA.01

It shall be possible to detect and display: a) Conflicts / infringements on runway caused by aircraft or vehicles; b) Restricted areas incursions caused by aircraft (i.e incursions on a closed taxiway or runway).

F.SN.AREA.2 F.SN.RCA.02 The controller shall be provided with clear and visible indication of a runway conflict alert as soon as the alert exists. Different levels of severity for alert situations should be distinguished. To each level of severity may correspond a different alert step: • Step 1 alert is used to inform the controller that a situation which is potentially

dangerous may occur, and he/she needs to be made aware of. According to the situation, the controller receiving a stage 1 alert may take a specific action to resolve the alert if needed. This is called the ‘INFORMATION’ step.

• Step 2 alert is used to inform the controller that a critical situation is developing which needs immediate action. This is called ‘ALARM’ step.

F.SN.AREA.3 F.SN.RCA.03 A runway conflict monitoring alert shall be automatically triggered when an arriving or departing aircraft proceeds with moving traffic to/on converging or intersecting runways. The following cases shall be considered:

Ref. aircraft Conflicting aircraft Step 1 alert Step 2 alert

Unidentified vehicle on the runway protection area

No Yes

Aircraft proceeding to a closed runway

Aircraft on runway protection area surface

Departing aircraft lining up or taking off, or arriving aircraft (<T1 from treshold).

No reference aircraft

Aircraft departing on the runway in the wrong direction

No Yes

Arriving aircraft An aircraft or vehicle is on the runway protection area surface

Arriving aircraft is <T1 from treshold

The arriving aircraft < T2 from treshold, until the arriving aircraft has passed the a/c or vehicle (a/c or vehicle behind the arriving aircraft)

A slower preceeding departing aircraft which has not crossed the end of the runway in use or has not started a turn



A preceeding aircraft which has not cleared the protection area



Departing aircraft A mobile (aircraft or Departing aircraft is not Departing aircraft is

18 Airport Safety Nets, Alerts Category 3: Infringement of restricted / closed areas

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


vehicle) is on the runway protection area surface and not behind the departing aircraft

yet taking-off (speed < 50 knots)

taking off (speed > 50 knots)

Note: the ir boundary is defined as a flight time to threshold; non LVP conditions: T1=30’’, T2 = 15’’; LVP conditions: T1 = 45’’, T2 = 30’’. Note: LUP/LUP, TOF/TOF and LND/LND shall triger an ALARM if two aircraft are cleared on the same runway but on the opposite thresholds.

H.SN.AREA.1 H.SN.RCA.01 Conflict information should be unambiguously presented to the controller using visual and sound processes: a) Visual process consists in the provision of alert situation information: the provided information should include the type and location of alert situation, and identification of the conflicting traffic.

b) Sound process consists in a sound alert issued when the alert situation necessitates an immediate action. A sound process shall always be associated with a visual process in order to provide the controller with the information he needs to understand the situation.

This information should be always available to the controller. H.SN.AREA.2 H.SN.RCA.02

An alert associated with a detected conflict should be provided with an adequate time and brought to the attention of the controller (alarm coding). An alert associated with a predicted conflict (information coding) should also be provided.

F.SN.AREA 4 F.SN.RCA.04 Conflict information should be displayed continuously while the conflict is present. It should not be possible to manually de-activate a runway conflict alert.

H.SN.AREA.3 H.SN.RCA.03 The controller shall not be allowed to cancel a runway conflict alert.

F.SN.AREA.5 F.SN.RCA.05 The end of a runway conflict alert shall be automatically triggered when the corresponding triggering conditions are no more fulfilled.

H.SN.AREA.4 H.SN.RCA.04 The controller shall be provided with clear and visible information about the end of the runway conflict alert as soon as the alert ends.

F.SN.AREA.6 F.SN.RCA.06 A runway incursion alert should always be clearly distinguished and shall never be hidden by any other alert or information display.

F.SN.AREA.7 F.SN.RCA.07 The indication of a runway incursion alert shall have higher priority than any other alert or information display.

6.10.1.4.2 Detection of ATC controllers input errors with respect to airport layout Note: the former requirements referenced F.SN.LAY.YY and H.SN.LAY.YY have been replaced with F.SN.AREA.YY and H.SN.AREA.YY respectively. F.SN.AREA.8 F.SN.LAY.1

It shall be possible to detect and display ATCO input error with respect to airport layout (i.e. a/c arriving to or departing on a closed runway; aircraft cleared to taxi via closed taxiway)

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.SN.AREA.5 H.SN.LAY.1 The controller shall be provided with clear and visible indication of an input error with respect to the airport layout.

H.SN.AREA.6 H.SN.LAY.2 An INFORMATION alert shall be automatically triggered when ATCO input error with respect to the airport layout occur:

a) For a flight, when a selected runway is either closed or inactive.

b) For a flight, when a selected runway is inappropriate/unsuitable w.r.t the aircraft type, i.e. runway is too short.

c) For a flight, when the input taxi route is inappropriate/unsuitable, i.e. at least one taxiway in the planned route is closed, or at least one taxiway in the planned route is not compatible with the aircraft type.

H.SN.AREA.7 H.SN.LAY.3 An ALARM alert shall be automatically triggered when the situation, input error with respect to airport layout, is not resolved and the system detects mobile entering the unauthorised area: a) For a flight, when an aircraft is entering either closed or inactive runway. b) For a flight, when an aircraft is taxiing on the closed taxiway.

6.10.2 Protecting devices and runway lighting F.SN.PTD.01 It shall be possible to display the stop bars status F.SN.PTD.02 It shall be possible to manually switch (i.e. activate or de-activate) protection devices such

as stop bars or anti-intrusion system. H.SN.PTD.01 The controller should be provided with an easy means to manually activate or de-activate

stop bars. H.SN.PTD.02 The status of stop bars (i.e. activated, de-activated, failure) should be clearly and visually

indicated to the controller. F.SN.PTD.03 It shall be possible to display the APP and runway lighting status F.SN.PTD.04 It shall be possible to manually switch APP and runway lighting H.SN.PTD.03 The controller should be provided with an easy means to manually switch-on or switch off

APP and runway lighting H.SN.PTD.04 The status of runway lighting should be clearly and visually indicated to the controller. F.SN.PTD.05 The switching (i.e. activated or de-activated) status of stop bars should be changed

automatically according to ATC clearances and a/c position. H.SN.PTD.05 Red stop bars should switch off when a line up or take-off clearance is given to an aircraft.

They should return to red (activated) when the aircraft has crossed the stop bar. The parameter to switch the stop bars on could be time or distance based. This parameter should be defined at a local level. Note: in the future, the activation of the stop bar will be refined. The change of the red stop bar status might be linked to the conflicting ATC clearances detections.

6.10.3 NAVAIDS servicability F.SN.NAV.01 It shall be possible to display the status of any airport NAVAIDS equipment.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


H.SN.NAV.01 The controller should be provided with an easy means to display on request the status of airport NAVAIDS equipment.

H.SN.NAV.02 The controller should be warned automatically in case of modification of airport NAVAIDS equipment serviceability.

6.10.4 Management of mobiles on the runway (cross & enter) F.SN.RWY.1 It shall be possible for the controller to input an “enter runway protected area” instruction F.SN.RWY.2 It shall be possible to input a “cross runway” instruction H.SN.RWY.1 The controller should be provided with an easy means to input a “cross” clearance

instruction H.SN.RWY.2 When the controller gives a ‘cross’ or ‘enter’ instruction to a mobile, the controller should

have visual indication of the runway occupancy until the ‘vacate’ or ‘release’ order is given (e.g. runway e-strip).

F.SN.RWY.3 It shall be possible to display when a runway is occuped by an aircarft or a vehicle which is on the frequency with the controller.

H.SN.RWY.3 The controller should be provided with a clear identification of runway occupancy. F.SN.RWY.4 It shall be possible to display when the end of a runway is not occupied anymore. H.SN.RWY.4 The controller should be provided with a clear visual identification when the runway is not

occupied any more.

6.10.5 Management of traffic queues – sequencing tr affic

6.10.5.1 Departure management F.SEQ.DEP.1 It shall be possible to display the Target Start Up Time of a departing aircraft. H.SEQ.DEP.1 The controller should be provided with a clear display of the Target Start Up Time for a

departing aircraft. The time should be displayed on the EFS and in the radar label. F.SEQ.DEP.2 It shall be possible to display the Target Take Off Time of a departing aircraft. H.SEQ.DEP.2 The controller should be provided with a clear display of the Target Take Off Time for a

departing aircraft. The time should be displayed on the EFS and on the radar label. F.SEQ.DEP.3 It shall be possible to display the flight position number in the runway sequence at the

runway. H.SEQ.DEP.3 The controller should be provided with clear display of the flight position number in the

departure sequence at the runway. The number should be available on the EFS and on the radar label (extended radar label and selected field in the EFS).

6.10.5.2 Arrival management F.SEQ.ARR.1 It shall be possible to display the Estimated LanDing Time of an arriving aircraft. H.SEQ.ARR.1 The controller should be provided with a clear display of the Estimated LanDing Time for

an arriving aircraft. F.SEQ.ARR.2 It shall be possible to display flight position number in the arrival sequence at the runway. H.SEQ.ARR.2 The controller should be provided with clear display of the flight position number in the

arrival sequence at the runway. The number should be available on the EFS and on the radar label (extended radar label and selected field in the EFS).

6.11 Mobile Routing Management

6.11.1 Display planned route

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


F.ROUTE.DIS.1 It shall be possible to provide routing information (i.e. visualise the trajectory) for an aircraft and an assumed vehicle.

H.ROUTE.DIS.1 The controller should be able to easily visualise the planned trajectory of a mobile. Only the trajectories of the assumed mobiles should be highlighted.

6.11.2 Validate assigned route and display cleared route F.ROUTE.CLR.1 It shall be possible to validate a part or the totality of the route assigned to an assumed

mobile. H.ROUTE.CLR.1 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to validate the route assigned to a mobile. The mobile representation should account for this validation.

F.ROUTE.DIS.2 It shall be possible to visualise a cleared / not cleared portion of the trajectory of an assumed mobile.

H.ROUTE.DIS.2 The controller should be able to easily visualise portions of the cleared route for a mobile

6.11.3 Input ‘Stop At’ instruction F.ROUTE.ORD.1 It shall be possible to input a “stop at” instruction H.ROUTE.ORD.1 Depending on the controller role and flight control responsibility, the controller should be

provided with an easy means to input a “stop at” instruction for an aircraft. The aircraft representation should account for this instruction.

6.11.4 Input route modification F.ROUTE.CHG.1 It shall be possible for the controller to change the inital trajectory of an assumed mobile. F.ROUTE.CHG.2

By human-initiated means, it should be possible to immediately cancel or change an existing and used route.

F.ROUTE.CHG.3 When the existing and used route of a mobile has been cancelled, the controller should be able to input a new route.

F.ROUTE.CHG.4 When the existing and used route is modified, the system should propose a new route to reach the inital destination.

H.ROUTE.CHG.1 The controller should be provided with an easy means to change a planned trajectory or to input a new route for a mobile. Only the trajectories of the assumed mobiles should be modifiable.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


6.12 Air-Ground Data Communication: Data link Funct ions F.DL.IDF.1 It shall be possible to identify an aircraft equipped with data link. H.DL.IDF.1 The controller should be provided with visual representation for aircraft equipped for data

link communications in the radar label, on the EFS and everywhere else the callsign of the aircraft is displayed.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7 Annex: Transversal HF Requirements 7.1 Processes of interaction

7.1.1 Behavioural consistency

Rationale: the system behaviour therefore has to be predictable, which in turn implies that its behaviour should be consistent, i.e. the same event, applied to the same object in the same context, provokes the same response.

X.HF.G1 Minimize Train ing Description: Systems and equipment should be capable of being maintained, operated, and repaired

in the planned operational and maintenance environment with minimal training. Source: MIL-STD-1472F, 1999

X.HF.G2 Predictable resu lts Description: Systems and equipment should be designed so that basic system functions are obvious

to the user. Source: Martin & Dong, 1999

X.HF.G3 Standardize hardware and software Description: Hardware and software designs should be standardized to the degree practical and

compatible with system functions and purposes. Source: MIL-STD-1472F, 1999

X.HF.G4 Maintain identical interfaces for identical functions Description: Equipment with identical functions should employ identical or similar interfaces Source: MIL-STD-1472F, 1999

X.HF.G5 Make controls, displays, marking, coding, labelling, and arrangem ent uniform Description: Controls, displays, marking, coding, labelling, and arrangement schemes should be

uniform for common functions of all equipment Source: MIL-STD-1472F, 1999

7.1.2 Level of user awareness

Rationale: the user should only be ‘thinking’ in terms of the task activities and never in terms of the mechanics of the interface. The user should be thinking in terms of operational actions and consequences. This is critically dependent on the intuitiveness and ease of use of the interface.

X.HF.G6 Use familiar terms and images Description: Systems and equipment should use terms and images familiar to the user Source: Martin & Dong, 1999

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.1.3 Explicit Design to support resource managemen t and monitoring

Rationale: the rules and limitations should be built into the procedures rather than being ‘hard-wired’ into the interface code. There should be some separation of operational procedures and the mechanisms of the interface

X.HF.G7 Design for simplici ty Description: The system or equipment design should be as simple as possible, consistent with the

desired human-machine system functions, and compatible with the expected maintenance and operational concepts

Source: MIL-STD-1472F, 1999

7.1.4 Flexibility in the use of the interface: mul tiple paths and expert use

Rationale: the design must be flexible and tolerant because, at the detailed level, we do not know all the ways in which the expert may make use of it.

X.HF.G8 Provide enough flexibilit y for different user skill levels Description: Systems and equipment should be flexible enough to accommodate the interaction

styles of users with differing skill and experience levels Source: Ameritech, 1998

7.1.5 Minimum cognitive effort

X.HF.G9 Be consistent with user mental model Description: To decrease learning or training times, systems should be designed to be consistent

with the mental model of the users Source: CTA, 1996

7.1.6 Feedback on action

X.HF.G10 Routine feedback

Description: The system should provide users with consistent, routine feedback regarding such activities as control entries, computer processing, and print requests

Source: MIL-STD-1801, 1987

X.HF.G11 Timely and informative feedback

Description: Systems and equipment should provide timely and informative feedback to user actions to keep the users informed about what is happening

Source: Apple Computer Incorporated, 1995

X.HF.G12 Predictable results Description: For the feedback to be effective an appropriate response time should be defined for

each selectable object. In absence of definition ≤125 milliseconds is assumed. Source: Eurocontrol Echoes, 2003

X.HF.G13 Predictable results Description: User actions should cause predictable results. Source: Martin & Dong, 1999

7.2 Inputs

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.2.1 Input Basics

X.HF.R1 Highlighting principle Description: By default any field or object that is selectable shall provide a feedback (highlight) to

show selection acquisition and an ‘inverse’ feedback to show de-selection. Source: Eurocontrol Echoes, 2003

X.HF.R2 Highlighting activatio n Description: An object shall become selected only when the acquisition boundary of (an instance19

of) the object has been crossed by the cursor. (The area within the acquisition boundary is called the acquisition area).

Source: Eurocontrol Echoes, 2003

X.HF.R3 Highlighting de-activation Description: The object shall cease to be highlighted only when the cursor crosses the retention

boundary, or when the presentation of the object changes as the result of an input action. (The area within the retention boundary can be called the retention area).


X.HF.G14 Highlighting latency Description: There should be a latency parameter associated with highlighting such that the object

highlights only when the cursor lies within the two boundaries for more than a certain time, i.e. the value of the latency parameter.


X.HF.R4 Boun dary definition

Description: Acquisition and retention boundaries shall be defined as attributes, for each selectable object. (The boundaries are defined in millimetres20 relative to the visible boundaries of the object).


X.HF.R5 Boundary defa ult Description: If unspecified, the default assumption shall be that all boundaries correspond to the

visible boundary. Source: Eurocontrol Echoes, 2003

7.2.2 The accessibility of selectable objects

X.HF.R6 Target a ccess Description: To be selectable a screen object shall be visible to the user (i.e. not completely

overlapped by other screen objects). Source: Eurocontrol Echoes, 2003

19 There are cases in the HMI where selection of one instance of an object results in the cross highlighting of all other instances (e.g. selecting an aircraft in a list highlights the label).

20 Of course it is the visual angle presented which is important.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.R7 Target availab ility Description: If a screen object is visible, its availability for input shall be clearly indicated to the

user either through a convention or a specific encoding. Source: Eurocontrol Echoes, 2003

X.HF.R8 Target size Description: Selectable objects shall be at least 4.00mm across the shortest axis along which they

will be acquired. Applies to both text and non-text selectable objects. Source: Eurocontrol Echoes, 2003

7.2.3 Response times

X.HF.G15 Priority response

Description: An initial response to user input - indicating recognition that an input has been made - should take priority over any other activity at the interface.


X.HF.G16 Feedback response time

Description: For good interface engagement a minimum feedback response to an explicit user input should be provided in ≤ 125 milliseconds (perception of immediate response).


X.HF.R9 Feedback response consistency Description: Consistency of response time shall be more important than the absolute time of

response. Source: Eurocontrol Echoes, 2003

7.2.4 Temporary versus Permanent Information Displa y

X.HF.R10 Access quick look

Description: The interface shall provide the capability to display objects or information temporarily, removing it after the controller has obtained the desired information, with no further intentional action on the controller’s part.


X.HF.R11 Access sustained Description: The interface shall provide the capability to display objects or information which

remains displayed on screen for successive use by the controller, and is removed only as a consequence of a subsequent, specific controller action.


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.2.5 Policy on default selections

X.HF.G17 Menu defaults Description: Where defaults are deemed necessary, care should be taken to:

(a) limit their tendency to impede non-standard inputs (they should never block them) and (b) ensure that consistency of interaction is maintained.


X.HF.R12 Menu defaults Description: The use of menu defaults shall not lead to inconsistency in menu presentation or in the

rules for user interaction with menus. Source: Eurocontrol Echoes, 2003

X.HF.R13 Menu defaults Description: The order of menu items21 shall not be modified in menus for the input of operational

parameters or actions. If the menu should open on a specific selection, the opening menu shall be displaced vertically to put the appropriate value under the cursor which shall not move from the point of last user action.

Source: Eurocontrol Echoes, 2003 (modified)

X.HF.G18 Menu defaults Description: In cases where a parameter selection menu defaults to a value, there should be a

method or coding which allows recognition of the currently assigned parameter value. Source: Eurocontrol Echoes, 2003

X.HF.R14 Pop-up menu Description: When displayed, a pop-up menu shall appear in a location that is coordinated with the

location of the pointer. Source: Eurocontrol Echoes, 2003

X.HF.R15 Menu options Description: A menu shall display explicitly and completely all options available to a user at the

current step in a transaction sequence. Source: Eurocontrol Echoes, 2003

X.HF.G19 Menu activation Description: A menu should be activated by a click and shall require another click or action

(moving of the object) to be deactivated. Source: Eurocontrol Echoes, 2003 (modified)

X.HF.R16 Groups of options Description: Groups of options in a menu shall be ordered according to user’s logic. Source: Eurocontrol Echoes, 2003

21 Generally the contents of menus are fixed. Items not available in a certain context will be present but ‘greyed-out’.

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G20 Number of options Description: The number of options in a menu should not be more than ten or less than three. Source: Eurocontrol Echoes, 2003

X.HF.R17 Number of options Description: A menu shall display explicitly and completely all options available to a user at the

current step in a transaction sequence. Source: Eurocontrol Echoes, 2003

7.2.6 Input Devices and Input Events

7.2.6.1 Mouse

X.HF.R18 Mouse buttons hand Description: Definition of mouse buttons, assignement of actions and results should be consistent

throughtout the overall interface. Source: ITWP, 2007

X.HF.R19 Mouse buttons hand Description: The buttons mouse functions shall be interchangeable as an option for left-handed

subjects. Source: Eurocontrol Echoes, 2003 (modified)

7.2.6.2 Keyboard

X.HF.G21 When to use Description: If applicable, keyboards should be provided for the entry of alphabetic, numeric, and

other special characters into the system. Source: Department of Defence, (MIL-STD-1472D), 1989

X.HF.G22 Include a numer ic keypad for entering

numeric data Description: If an application requires substantial and repetitive input of numeric data, the keyboard

should include a numeric keypad Source: MIL-STD-1472D, 1989; Department of Defence (MIL-STD-1801), 1987

X.HF.R20 Frequently used commands Description: Function keys shall be provided for frequently used commands, and shall be clearly

labelled to indicate their function Source: ATC (FAA) HF Checklist, 7.4.3

X.HF.R21 Keyboard location Description: The main keyboard shall be located directly in front of and below the associated visual

display, at a comfortable distance from the seated controller’s position Source: ATC (FAA) HF Checklist, 7.4.3

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G23 Accidental activation Description: Guards should be in place for any key that would present a problem if inadvertently

activated Source: ATC (FAA) HF Checklist, 7.4.3

7.2.6.3 Touch screen

X.HF.G24 Use Description: A touch panel or screen should be used to provide an overlaying control function to a

display device (e.g., a CRT, an electro luminescent display, or a programmable indicator) if direct visual reference access and optimum direct control access are desired

Source: MIL-STD-1472D, 1989; DOE-HFAC1, 1992

X.HF.G25 Luminance transmission Description: Touch panels should have sufficient luminance transmission to allow the display to be

clearly readable in the intended environment Source: MIL-STD-1472D, 1989; DOE-HFAC1, 1992

X.HF.G26 Minimal parallax Description: Touch-interactive devices should be selected and mounted to minimize parallax

problems Source: Avery & Bowser (DOE HFDG ATCCS V2.0), 1992

X.HF.G27 Minimal specular glare Description: Touch-interactive devices should be selected and mounted to minimize specular glare Source: DOE HFDG ATCCS V2.0, 1992

7.2.6.4 Menus and Pop-Up menus

7.2.6.4.1 General use

X.HF.G28 Use Description: Menus should be used for selecting values and choosing from a set of related options. Source: DON UISNCCS, 1992

X.HF.G29 Selecting a mutually exclusive option Description: When users need to choose one option from a number of mutually exclusive options,

a) radio buttons should be used for up to 6 options, b) a menu should be used for up to 10 options, and c) a scrolling menu should be used for more than 10 options.

Source: DON UISNCCS, 1992

X.HF.G30 Menus distinct from other dis played information Description: Menus should be distinct from the other objects or information on the screen Source: MIL-HDBK-761A, 1989; DOE HFDG ATCCS V2.0, 1992; MIL-STD-1801, 1987;

DOD HCISG V2.0, 1992

X.HF.G31 Consistent style Description: Menus throughout an application should conform to a single style of interface Source: DOE HFDG ATCCS V2.0, 1992

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G32 Consistent menus and options Description: When the same menu or option appears in different displays within an application, it

should be consistent in wording, grammatical structure and organization. Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992 (modified)

X.HF.G33 Menu titles Description: Menu titles and menu options should be easily distinguishable Source: Ameritech Services Inc., 1996

X.HF.G34 Distinguishing menu titles Description: Menu titles should be easily distinguished from the options Source: Ameritech Services Inc., 1996

X.HF.G35 Numbering menu titles Description: Menu titles should not be numbered Source: MIL-HDBK-761A, 1989; Defence Information Systems Agency, 1995

X.HF.G36 Menu titles as options Description: The menu title should not appear as an option in the menu Source: MIL-HDBK-761A, 1989

7.2.6.4.2 Menu options

X.HF.G37 Highlighting menu options Description: A menu option should be highlighted when the pointer is on the menu option Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992

X.HF.G38 Number of options Description: The number of options in a menu should not be more than 10 Source: MIL-HDBK-761A, 1989 (modified)

X.HF.G39 Disting uishing unavailable options Description: When a menu contains options that are temporarily unavailable, the unavailable

options should be displayed but clearly distinguishable from available options Source: MIL-HDBK-761A, 1989

X.HF.G40 Menus with no available options Description: When all the options on a menu are unavailable, then the menu title and all the options

should be disabled (greyed out) Source: Ameritech Services Inc., 1996

7.2.6.4.3 Options organisation

X.HF.G41 Alignment of options Description: With the exception of a menu bar, the options in a menu should be presented in a

single vertical column, aligned and left justified Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992; MIL-HDBK-761A, 1989;

MIL-STD-1801,1987

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G42 Ordering a number of options Description: When a group of options or a menu contains a number of options, the options should

be ordered logically according to the requirement of the user. Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992 (modified)

X.HF.G43 Default option Description: The most likely selection in a menu list should be made the default option Source: CTA, 1996

7.2.6.4.4 Menu bars

X.HF.G44 Number of options Description: Menu bars should contain no more than 10 options plus Help Source: DON UISNCCS, 1992] HFDS 2003 Chapter 8 Computer human interface, 8-77

X.HF.G45 Placement of options Description: The options should begin at the left margin and extend to the right with Help located

consistently, with enough space between them so that they can be read easily and accommodate the longest options in the pull-down menus


X.HF.G46 Names of menu bar options Description: Each menu that appears as an option in a menu bar should have a title that is unique in

the application Source: DON UISNCCS, 1992

X.HF.G47 Same menu bar in different windows Description: When the same menu occurs in different windows, it should have the same title in

each Source: DON UISNCCS, 1992

X.HF.G48 Menu bar activation Description: A menu bar should be activated b a single click and shall require another click or

action (moving of the object) to be deactivated) Source: ITWP, 2007

7.2.6.4.5 Scrolling menus

X.HF.G49 When to use Description: Scrolling capability should be provided for menus used in data entry that are too long

to display in their entirety (for example, lists of retrievable files or acceptable entries for a filed)

Source: Apple Computer Inc., 1992 X.HF.G50 Scroll-bar Description: The scroll-bar should be placed at the right of the displayed options Source: DON UISNCCS, 1992

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G51 Option display Description: The displayed options in a scrolling menu should be arranged vertically with one

option per line Source: DON UISNCCS, 1992

X.HF.G52 Order of options Description: The options in a scrolling menus should be ordered in a way that minimizes user

navigation Source: DON UISNCCS, 1992

X.HF.G53 Alphabetical arrangement Description: When ordering by expected frequency of use or in chronological or other sequential

order is not appropriate, options should be ordered alphabetically Source: DON UISNCCS, 1992

X.HF.G54 Display of all opti ons in a scrolling menu Description: All the options in a scrolling menu should be available for explicit and complete

display through scrolling. Source: Apple Computer Inc.,1992

7.2.6.4.6 Pop-up menus

Pop-up menus are menus that only appear on user demand. They are often associated with a particular object on a display, (for example, a pop-up menu listing acceptable command options close to the immediate work area). Because they are not displayed all of the time, they do not take up valuable screen space. They provide an efficient way to access commands because they eliminate the need for the user to navigate to a menu bar or control bar. A pop-up menu typically contains 5 to 10 options presented in a vertical listing. Pop-up menus can be very useful in data entry. They can present to a user the permissible entries for a field, thus eliminating the need for the user to remember the entries, preventing invalid entries, and eliminating potential typing errors. A pop-up menu resembles a pull-down menu, but it is not associated with the top level menus listed in the menu bar. [source: CTA, 1996].

X.HF.G55 Pop-up menus Description: Pop-up menus should follow the rules for standard pull-down menus and should be

titled when required Source: Microsoft Corp., 1992 (modified)

X.HF.G56 Distinguishing the pop-up menu Description: The pop-up menu should be made distinct from the screen background by giving it a

contrasting yet complementary background or by giving it a solid-line border Source: CTA, 1996

X.HF.G57 Pop-up menu location Description: A pop-up menu should be placed directly below the pointer used to select it and near

the object or higher-level menu that is being manipulated Source: CTA, 1996

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G58 Indication of pop-up menu Description: An indication or cue should be provided to the existence of a pop-up menu Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992

X.HF.G59 Selecting an option usi ng a pointing device Description: A user should be able to select an option on a pop-up menu by moving the pointer

onto the desired option and clicking the appropriate button Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992

X.HF.G60 Selection highlighting Description: When an option in a pop-up menu remains on display after it has been selected, it

should remain highlighted Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992

X.HF.G61 Pop-up menus leading to cascading menus Description: When an option in a pop-up menu leads to a cascading menu, a right pointing triangle

(►) should be placed after the option label. Source: CTA, 1996

X.HF.G62 Options l eading to cascading menus Description: Selected options that lead to a cascading menu should remain highlighted and serve as

the title for the cascading menu. Source: CTA, 1996

7.2.7 Input Error Management Policy

X.HF.G63 Flexible "go ba ck" for error correction Description: A system or application should allow a user to go back easily to previous steps in a

transaction sequence in order to correct an error or make any other desired change. Source: DOE HFDG ATCCS V2.0, 1992

7.3 Visual presentation rules and conventions

7.3.1 Display hardware

7.3.1.1 General X.HF.G64 Make displays legible und er all conditions Description: Visual displays should be legible under all anticipated viewing conditions, and should

maintain good image quality even at the dimmest possible setting Source: MIL-STD-1472F, 1999

7.3.1.2 Glare

X.HF.G65 Glare Control Description: Glare should be eliminated or minimized Source: ANSI, 1988; MIL-STD-1472F, 1999

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.3.2 Principles for the presentation of data

7.3.2.1 General Principles X.HF.G66 Simplicity Description: Information should be presented simply and in a well-organized manner. Ways to

achieve simplicity include the following: a. The screen should appear to be orderly and clutter-free. b. Information should be presented in consistent, predictable locations. c. The language used should be plain and simple. d. The means for moving around the screen and to related screens should be

simple. e. Interrelationships should be indicated clearly.

Source: Avery & Bowser (DOE HFDG ATCCS V2.0), 1992; Avery & Bowser (DOD HCISG

V2.0), 1992

X.HF.G67 Minimizing the user's short-t erm memory load Description: A single window should contain all relevant information and should allow a user to

complete the task without having to refer to additional information Source: Department of the Navy (DON UISNCCS, 1992), 1992

7.3.2.2 Organisation of information

X.HF.G68 Priority of displayed information Description: Information should be prioritized so that the most important or critical information is

displayed all the time and less important or critical information can be displayed upon a user's request

Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992

X.HF.G69 Grouped information Description: Groups of data items should be separated by a blank space, lines, colour-coding, or

other visually distinctive means Source: MIL-HDBK-761A, 1989

X.HF.G70 Primary viewing area Description: Information that is particularly important or that requires immediate user response

should be displayed in the user's primary viewing area Source: DOD HCISG V2.0, 1992

X.HF.G71 Task-critical information Description: When a window contains task-critical information, that information should be

displayed in a way that users can identify easily, (for example, separating it from other information by a blank space)


X.HF.G72 Ordering of information Description: When displayed information is to be used in some spatial or chronological order, its

arrangement on the screen should preserve that order. When ordering displayed information by sequence, function, frequency, or importance is not appropriate, some other method such as alphabetical or chronological should be followed.

Source: DOD HCISG V2.0, 1992

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G73 Minimal visual competition Description: Information on a display screen should be organized so that visual competition among

distinct items of information is minimized. Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992

X.HF.G74 Matching layout to task Description: Application designers should design the screen layout so that users can move quickly

and easily among items and can manipulate objects in ways that support task performance


X.HF.G75 Removal of Inf ormation from the screen Description: Information that the controller needs should not disappear from the screen without

being deleted or suppressed by the controller Source: ATC (FAA) HF Checklist

X.HF.G76 Highlighting Description: When a user is performing an operation on a selected object in a display, that object

should be highlighted Source: DOE HFDG ATCCS V2.0, 1992; MIL-HDBK-761A, 1989

X.HF.G77 Display Consistency Description: There should be a high level of consistency between screen structures, screen

elements, display formats, and location of instructions and prompts Source: MIL-HDBK-761A, 1989

7.3.2.3 Text properties

7.3.2.3.1 Fonts and sizes

X.HF.G78 Number of different fonts Description: There should be a limit of two different fonts displayed on any one screen Source: National Air Traffic Services, 1999]

X.HF.G79 Text size and style Description: Variations in the size and style within a font should be used to categorize the

information into different levels Source: National Air Traffic Services, 1999

7.3.2.3.2 Vocabulary and abbreviations

X.HF.G80 Vocabulary Description: The words used in all non-editable text should be task-oriented and familiar to users Source: DON UISNCCS, 1992

X.HF.G81 Consist ent wording and structure Description: The wording and grammatical structure of displayed data and labels should be

consistent throughout an application and related applications Source: MIL-HDBK-761A, 1989

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G82 Use of abbreviations Description: When a system or application uses abbreviations in its user-computer interface, the

abbreviations should be unique, distinct, and unambiguous so as not confuse users Source: MIL-HDBK-761A, 1989; Department of Defence (MILSTD-12D), 1981

X.HF.G83 Acronyms Description: Acronyms should be used only if they will be seen more than once, are significantly

shorter than the term they represent, and the users will commonly understand them Source: DON UISNCCS, 1992

X.HF.G84 Acronym format Description: Acronyms should be displayed in all upper-case letters Source: DON UISNCCS, 1992

X.HF.G85 Consistent abbreviation use Description: When used, abbreviations should be used consistently throughout an application or set

of related applications Source: DOE HFDG ATCCS V2.0, 1992; DOD HCISG V2.0, 1992

7.3.2.3.3 Style and layout

X.HF.G86 Contrast Description: Text should be displayed as black characters on a white or light background. The

contrast between text and its background should be sufficiently high to ensure readability of the text


X.HF.G87 Suitability/approp riateness of bold coding Description: Bold coding should be used for strong emphasis. No more than three levels of bold

coding should be used Source: National Air Traffic Services, 1999

7.3.2.4 Viewing distances

X.HF.G88 Range for viewing distance Description: Minimum and maximum viewing distances for displays should be determined by the

legibility of the displayed information Source: MIL-STD-1472F, 1999 (modified)

7.3.2.5 Radar Labels

X.HF.G89 Aircraft information Description: The presented aircraft information should clearly indicate if the aircraft status or evolution

requires a controller action. Source: Eurocontrol Echoes, 2007

X.HF.G90 Aircraft parametre Description: Information concerning the aircraft's current flight parameters should be available on controller

request, in an easy and rapid way. Source: Eurocontrol Echoes, 2007

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G91 Aircraft flight data avialbility Description: The controller receiving the aircraft should be informed of the availability of the aircraft flight

data on reception of the flight notification. Source: Eurocontrol Echoes, 2007 (modified)

X.HF.G92 Aircraft flight data update Description: The controller in the sending Unit should be informed that flight activation has been performed

on the aircraft. The controller in the receiving Unit should be informed of the availability of the updated aircraft flight data on reception of the flight activation.


X.HF.G93 Inactive label Description: After having successfully sent the transfer of communication or the release of an aircraft, the

transferring controller should no more have the capability to input any order (clearance) on that aircraft.


X.HF.G94 Notification of an aircraft Description: The controller in the receiving Unit should be informed of the availability of the aircraft flight

data on reception of the flight notification. The controller in the receiving Unit should be provided with adequate (ease of use, consistency, predictability - see the Style Guide) means to access the aircraft flight data.


X.HF.G95 Transfer of an aircraft Description: The reception of the transfer of communication or of the release of an aircraft by the accepting

Unit should enable the controller to assume the control of that aircraft. Source: Eurocontrol Echoes, 2007

7.3.2.6 Check boxes (i.e. on EFS)

Check boxes (also known as nonexclusive buttons) are single, two-state choices. For example, a check box can be on, (checked) or off (not checked). A check box group is a collection of two-state choices, all of which apply to the same selected object. Check boxes can be grouped.

X.HF.G96 Selecting check boxes Description: Users should be able to toggle selected and unselected states on a check box using

either a pointing device or the keyboard Source: DON UISNCCS, 1992

X.HF.G97 Check box states Description: Check boxes should have two states, selected and unselected. Source: DON UISNCCS, 1992

X.HF.G98 Labelling check boxes Description: Labels should be provided for each set of check boxes Source: CTA, 1996

X.HF.G99 Check box height and width Description: When grouping check boxes, the boxes should be equal in height and width Source: CTA, 1996

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.3.2.7 Cursors

X.HF.G100 Cursor movement Description: When entering and editing text, users should be able to move the cursor freely within a

displayed page to specify items for change and to make changes directly in the text Source: MIL-HDBK-761A, 1989

X.HF.G101 Size Description: Position or pointing cursors should maintain their size across all screen locations

during movement Source: Ameritech Services Inc., 1996

X.HF.G102 Rate of movement Description: Position or pointing cursors should move rapidly in response to the pointing device

(less than 100msec). Source: Ameritech Services Inc., 1996

X.HF.G103 Pointer location Description: The pointer should be easy to locate on the screen of the user. Source: ITWP, 2007

X.HF.G104 Cursor active point Description: A pointer should have an active point to indicate the precise location where an

operation will occur. These points are specified for a variety of pointer shapes Source: DOE HFDG ATCCS V2.0, 1992 (modified)

7.3.2.8 Maps and Tactical Displays

7.3.2.8.1 Characteristics

X.HF.G105 Intensity Description: The intensity of the map should be controllable to allow the map to be dimmed

without losing all the map features Source: DOE HFDG ATCCS V2.0, 1992

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G106 Map as background Description: When an application uses one map intensively, it is recommended that the map be

used as the background or base screen, which should be the maximum display size possible to promote readability

Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G107 Map size Description: Map displays should be large enough to permit the simultaneous presentation and

visual integration required by users Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G108 Coverage Description: Maps should cover the areas and display all the essential features and details users

need to perform their tasks Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G109 Situation displays as overlays Description: Situation displays (additional view windows) should be provided to their related maps Source: DOE HFDG ATCCS V2.0, 1992 (modified)

X.HF.G110 Map orientation Description: Users should have a possibility to orient the map in order to perform their task Source: ITWP, 2007

X.HF.G111 Areas of special interest Description: Map areas of special interest should differentiated by colour or shading Source: DOE HFDG ATCCS V2.0, 1992 (modified)

X.HF.G112 Reading a map Description: Users should be provided with a means or easily determining distance and bearing

between any two points on a map Source: DON UISNCCS, 1992

X.HF.G113 Labelling features Description: To the extent possible without cluttering the display, all significant features should be

labelled Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G114 Consistent label position Description: Map labels should be positioned consistently with respect to the feature they identify,

for example, to the left of or below the feature, but without obscuring important information


X.HF.G115 Label legibility Description: Labels should remain legible at all display resolutions Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G116 Association of symbols with map features

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Description: A symbol should be placed accurately with respect to the map feature with which it is associated, or connected to the feature with an arrow, line, or other pointing device so that the association between feature and symbol is clear

Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G117 Reducing clutter Description: Users should be provided with a means for reducing clutter without losing essential

information, such as the use of filters Source: DOE HFDG ATCCS V2.0, 1992

7.3.2.8.2 Graphic display manipulation

X.HF.G118 User control of map appearance Description: Users should be able to customize a map to conform to the task being performed.

Methods include: pan and zoom, return to initial appearance, define a home position and return to this position easily, move a map window, define the map appearance (for example, assign colours to areas), and select the objects that appear on the map and change the appearance of critical information


X.HF.G119 Map manipulation Description: The system should provide users with all appropriate tools for moving easily around a

map, including zooming and panning as well as insets, registration, and keys for scale Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G120 Return to start Description: When panning is provided, users should have the ability to return to the starting

configuration quickly and easily Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G121 Zooming and legibility Description: Zooming in and out should not interfere with the ability of users to read symbols,

labels, and other map features Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G122 Discrete vs. continuous zooming Description: The method of zooming provided, discrete or continuous, should be acceptable to the

users Source: DOE HFDG ATCCS V2.0, 1992

7.3.2.8.3 Dynamic information update

X.HF.G123 Alphanumeric data Description: Alphanumeric data that users are required to read reliably and accurately should not be

updated more often than once a second Source: MIL-HDBK-761A, 1989

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.3.3 Alarms and critical information

X.HF.G124 Display of alarms Description:

Alarms or critical information that a controller must read quickly should never blink or flash.


X.HF.R22 Alerts causes Description: Alerting and warning systems shall be unambiguous, with a clear indication of the

cause for the alert. Source:

Eurocontrol Echoes, 2003

X.HF.G125 Use of alarms Description: Alarms should

a. alert the user to the fact that a problem exists, b. inform the user of the priority and nature of the problem, c. guide the user’s initial responses, and d. confirm in a timely manner whether the user’s response corrected the problem.


X.HF.R23 Visual and Auditory Alarm Description: When used in conjunction with a visual display, an audio signal shall be

supplementary or supportive, alerting and directing the user’s attention to the appropriate visual display.


X.HF.R24 Priority between alerts Description:

When two or more incidents or malfunctions occur simultaneously, the one generating a message of higher priority shall be presented first. After presentation of the highest priority message, remaining messages shall be presented in descending order of priority.


7.3.4 Visual alerts

7.3.4.1 General X.HF.R25 Alert Location Description: High-priority and other critical information shall be located within the central display

areas (the central 15 degrees of the area where the controller normally looks, given the normal viewing position). If alert is displayed should not be hidden by other windows and objects.

Source: ATC (FAA) HF Checklist, 9.3.4, 7.2.11 (modified)

X.HF.G126 Reduc ing False Alarms

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Description: Alerts should have a low incidence of false alarms Source: ATC (FAA) HF Checklist, 7.2.11

X.HF.G127 Coding Description: Coding should be used to differentiate items of information, call a user's attention to

important information; unusual situations, or potential problems that require user action; or indicate changes in the state of a system

Source: MIL-HDBK-761A, 1989

X.HF.G128 Attention Description: A user's attention should be drawn to critical or abnormal information by highlighting,

inverse video, colour-coding, or other means. Coding techniques that have strong attention-getting qualities (for example, colour and flashing) should be used sparingly and judiciously

Source: National Air Traffic Services, 1999

X.HF.G129 Misuse of Visual Coding Description: Visual coding should be used for functional, not decorative, purposes Source: National Air Traffic Services, 1999

X.HF.G130 Consistency Description: Coding should be consistent throughout an application and related applications Source: MIL-HDBK-761A, 1989

7.3.4.2 Icons, buttons and controls

X.HF.G131 Design of symbols Description: To the extent possible, a symbol should be an analogy of the object it represents in

general use and well known to the users or based on established standards or conventional meanings


X.HF.G132 Minimum selectable area Description: The selectable area or hotspot outside of the area of the icon should be at least 4

millimetres Source: Ameritech Services Inc., 1996

X.HF.G133 Creating icons Description: When existing icons are not satisfactory, the user should create drawings that are

meaningful representations to users, easily recognizable, and visually distinct from each other

Source: CTA, 1996 7.3.4.3 Use of colours principles

X.HF.G134 Use of Colour

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Description: Colour should be used: a. to augment a user's understanding of the information being presented, b. to attach specific meaning to a portion of text or a symbol, c. to direct a user's attention to something (highlighting critical elements), d. to reduce clutter, e. to identify and classify information, f. to indicate changes in status, g. As a formatting aid, and to enhance legibility.

Source: DOD HCISG V2.0, 1992; National Air Traffic Services, 1999

X.HF.G135 Reserved meanings Description: Cultural colour conventions should not be violated. Colour-coding should conform to

the following reserved meanings consistent with conventional associations for particular colours:

a) Red should indicate conditions such as no-go, error, failure, or malfunction. b) Flashing red should be used only to indicate emergency conditions requiring immediate user action to avert personnel injury or equipment damage. c) Yellow should indicate marginal conditions, alert users to situations where caution or rechecking is necessary, or notify users of an unexpected delay.

Source: MILHDBK- 761A, 1989 (modified)

X.HF.G136 Colour coding strategy Description: The same colour coding strategy should be applied to every display used by the same

controller, and colours should be used consistently within a screen, within an application, and across a set of applications


X.HF.G137 Data categories Description: When colour is used to identify data categories, its use should not conflict with other

colour-coding conventions Source: MIL-HDBK-761A, 1989

X.HF.G138 Redundant use Description: The use of colour should not reduce screen readability Source: DOD HCISG V2.0, 1992

X.HF.G139 Small areas Description: Users should not have to discriminate among colours in small areas Source: DOD HCISG V2.0, 1992

X.HF.G140 Drawing attention Description: Brighter or more saturated colours should be used to draw a user's attention to critical

data Source: MIL-HDBK-761A, 1989

X.HF.G141 Colou rs for action and status

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Description: Longer wavelength colours (for example, red and orange) should be used to suggest action or a demand for a response


X.HF.G142 Relative colour Description: The colour of other figures and the background relative to a particular item should be

considered in order to provide the appropriate colour contrast and emphasis to the colour-coding of a particular item.


X.HF.G143 Colour pairs Description: The following colour pairs should be avoided: saturated red and blue, saturated red

and green, saturated blue and green, saturated yellow and green, yellow on purple, green on white, yellow on green, blue on black, magenta on green, red on black, magenta on black, yellow on white.

Source: CTA, 1996

X.HF.G144 Test colours Description: Selected colours should be tested with users to verify that the colours can be easily

discriminated from each other Source: CTA, 1996

X.HF.G145 Varying lightness Description: Colour combinations that are similar in lightness should be avoided (for example,

navy blue on black, yellow on white). Source: CTA, 1996

X.HF.G146 Foreground and background contrast Description: The foreground colour should contrast highly with the background Source: DOD HCISG V2.0, 1992

7.3.4.4 Brightness / intensity coding

X.HF.G147 High brightness Description: High brightness should be used to call attention to errors in data-entry fields and to

highlight answer fields on question and answer screens Source: CTA, 1996

X.HF.G148 Highlighting during operations Description: When a user is performing an operation on a selected object in a display, that object

should be highlighted Source: DOE HFDG ATCCS V2.0, 1992; MILHDBK-761A, 1989

X.HF.G149 Highl ighting on dark backgrounds Description: When the background is dark, white highlighting should be used with dark letters to

draw attention to particular data or portions of the screen Source: DOD HCISG V2.0, 1992 X.HF.G150 Highlighting o n light backgrounds

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


Description: When the background is light, dark highlighting should be used with white letters to draw attention to particular data or portions of the screen


X.HF.G151 Size and number of areas highlighted Description: The size and number of areas highlighted should be minimized Source: DOD HCISG V2.0, 1992

7.3.4.5 Flashing

X.HF.G152 Flash rate for Error Messages Description: Information that the controller must read and understand quickly, such as alarms or

critical error messages, should never blink or flash rapidly (greater than 3Hz). Source: ATC (FAA) HF Checklist

7.3.5 Auditory alerts

X.HF.G153 Use Description: Auditory alerts should be used only as necessary, to alert the controller of any

impending danger or critical change in the system or equipment status and to alert him of any actions that need to be taken. They can also be used to supplement visual signals, present information in situations in which visual presentation is not feasible and provide feedback for control actuation, data entry or the completion of timing cycles and sequences.


X.HF.G154 Application Description: An audio signal should be provided when the information to be processed is short,

simple, and transitory and requires immediate or time-based response. The criticality of a response to a visual signal makes supplementary or redundant alerting desirable. It is desirable to warn, alert, or cue the user for subsequent or additional responses and when voice communication is necessary or desirable


X.HF.G155 Annoyance factors Description: Alerts should not annoy or antagonize the controller Source: ATC (FAA) HF Checklist 7.3.5, 7.3.6

X.HF.G156 Alarms for normal conditions Description: Auditory alarms should not be used to indicate normal conditions Source: Wiener, 1988

7.3.5.1 Differentiation of signals

X.HF.G157 Differentiating signals Description: Auditory signals that require different user responses should be easily distinguishable

from one another Source: MIL-STD-1472F, 1999

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


X.HF.G158 Multiple audio signals Description: When several different audio signals will be used to alert a user to different conditions,

the signals should be distinctive in intensity, pitch, or use of beats and harmonics Source: MIL-STD-1472F, 1999

7.3.5.2 Signals meaning

X.HF.G159 Consistent signals and meanings Description: The meaning of audio warning signals selected for a particular function in a system

should be consistent with warning signal meanings already established for that function

Source: MIL-STD-1472F, 1999 7.3.5.3 Duration

X.HF.G160 Signal termination Description: Completion of a corrective action by the user or by other means should automatically

terminate the signal Source: MIL-STD-1472F, 1999

Intensity (loudness)

X.HF.G161 Environmental compatibility Description: The intensity, duration, and source location of an auditory signal should be compatible

with the acoustic environment of the intended receiver as well as with the requirements of other personnel within acoustic range of the signal


X.HF.G162 Volume limits Description: Volume control movement should be restricted to prevent reducing the volume to an

inaudible level or increasing it to an unacceptably high level Source: MIL-STD-1472F, 1999

7.3.5.4 Acknowledging signals

X.HF.G163 Acknowledging and terminating alarms Description: A system or application should provide users with a means of acknowledging alarms

and of turning off alarm signals once the alarms have been acknowledged or the condition generating the alarm has been corrected

Source: MIL-STD-1801, 1987

X.HF.G164 Automatic reset Description: An automatic reset function for audio signals should be provided, whether the signals

are designed to terminate automatically, manually, or both. The automatic reset function should be controlled by a sensing mechanism that recycles the signal system to a specified condition as a function of time or the state of the signalling system so that the warning device can sound again if the condition reappears


ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.3.6 Designing windows

7.3.6.1 General

Windows can be either modal or modeless. A modal window is a window with which a user must interact before being able to interact with any other windows. That is, a user cannot interact with other windows as long as the modal window is displayed. When a window is modeless, a user can interact with other windows.

X.HF.G165 User-specified windows Description: When there is a need to view several different types of data simultaneously, the user

should be able to display and select separate windows on a single CRT screen Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G166 Number of allowable open windows Description: The number of allowable open windows should not compromise system response time Source: DOE HFDG ATCCS V2.0, 1992

X.HF.G167 Window size Description: Windows should be large enough to: present all relevant information for the task, not

obscure important information, not cause crowding or visual confusion, and minimize the need for scrolling. The default size of the window should be less than the full size of the entire screen. When possible, the initial size of a window should permit the display of all its contents

Source: National Air Traffic Services, 1999

X.HF.G168 Window Resizing Description: Where applicable, the application should provide a resize operation that enables a user

to change the size of a window Source: DON UISNCCS, 1992

X.HF.G169 Moved or resized windows Description: When a window has been moved or resized or both and is then closed and reopened

during an application session, it should reappear in the size and location it had when it was closed


X.HF.G170 Default location for move d or resized windows Description: When a window has been moved or resized in the current session, it should appear in

its default location at the next application session Source: DON UISNCCS, 1992

7.3.6.2 Window states

X.HF.G171 Window movement limits Description: The user should never be able to move a window off the display so that it cannot be

seen, although it may be completely hidden by one or more other windows Source: Ameritech Services Inc., 1996

ITWP


Date: 1 March 2009

Version: V3.0

Status: Draft


7.3.6.3 Window organisation

X.HF.G172 Window default location

Description: Each window should have a default location at which the window appears when it is first opened. The initial placement of a window should be based on the importance of the information (critical information should be placed in the centre of the user's field of view), information already displayed that should not be obscured, the distance from the current pointer location (pointer movement should be minimized), and when applicable, information already displayed that is relevant to the window

Source: DON UISNCCS, 1992 7.3.6.4 Window component – Title bar

X.HF.G173 Use Description: A title bar should appear as a rectangular area at the top of a window inside the

window border and with the title of the window in the centre Source: DON UISNCCS, 1992

X.HF.G174 Capitalization in window titles Description: Significant words in the title (except user-defined words) should be capitalized Source: Ameritech Services Inc., 1996

7.3.7 System response time

X.HF.G175 Appr opriate system response time Description: The response time of a system to a user action should be appropriate to the type of

transaction, the time constraints of the task, and any specific data processing requirements

Source: DOE HFDG ATCCS V2.0, 1992; MILHDBK-761A, 1989 ************************** END OF THE DOCUMENT ******************

Integrated Tower W orking Position HMI SOLUTION ......Version: V3.0 Status: Draft D2 - ITWP HMI...

Documents

Transcript of Integrated Tower W orking Position HMI SOLUTION ......Version: V3.0 Status: Draft D2 - ITWP HMI...