Integrated Tower Working Position HMI SOLUTION SPECIFICATIONS

Transcription

1 Date: 1 March, 2009 HMI SOLUTION SPECIFICATIONS Reference: HMI solution Edition No: V3.0 Date: 1 March 09 Manager(s) S. Dubuisson / R. Lane Visa : Author EUROCONTROL Endorsement: Director(s) Peter Eriksen Visa : D2 - ITWP HMI Solution Specifications V3 - Page i Draft

2 Table of Contents 1 INTRODUCTION DOCUMENT PURPOSE AND SCOPE METHODOLOGY STRUCTURE OF THE DOCUMENT ACRONYMS REFERENCE DOCUMENTS PRINCIPLES TWR CONFIGURATION TWR FUNCTIONALITY AND PROCEDURES TRAFFIC PLANNING STATES Main states and sub-states Transitions between main states Not concerned to Pending transition Not concerned to Assumed Transition (vehicle and towed aircraft only) Assumed to Not concerned Transition Pending to Assumed Transition Transition between sub-states No value to Pending-in transition No value to Assumed Out transition COLOUR CODING Default colours Not concerned planning state colours Pending planning state colours Assumed planning state colours STRIP BAYS RWY controller bays Taxi Out Bay RWY Bay Transfer Bay GND Controller Bays Outbound Bay Runway Bay CLD Controller Bay Typical flight lifecycle HMI AND TRANSVERSAL FH REQUIREMENTS DESCRIPTION OF HMI OBJECTS DESCRIPTION OF HMI OBJECTS Worktop Window Cursor Switches Buttons Menu System Message Window Logon Window Local Parameters Preferences Setting Window...44 D2 - ITWP HMI Solution Specifications Page 1 Draft

3 General Toolbox Window Composite Situation Display (CSD) Toolbox Window Zoom Back Button Zoom Tool Map Selection Tool Speed Vector Track History Tool Sub-Views Tool Airport setup Tool EFS Configuration Tool EFS Tool Pending Departures Section (GND role) Start-Up Section (GND role) Pushback Section (GND role) Taxi-out Section (GND role) Pending Arrivals Section (GND role) Taxi-in Section (GND role) Transfer to RWY Section (GND role) Pending Departures Section (RWY role) Holding Point Section (RWY role) Pending Arrivals Section (RWY role) Final Section (RWY role) RWY Section (RWY role) RWY Taxi-In Section (RWY role) RWY Airborne Section (RWY role) Pending Departure Section (CLD role) CLD Active Section (CLD role) CLD Start Up Section (CLD role) Clock Window Weather Information Window NAVAIDS Information Window Composite Situation Display (CSD) Window Radar Track Radar Label Vehicle Radar Label Towed Aircraft Radar Label Label Configuration Tool Label Overlap Management Tool Range and bearing tracker link Extended radar label Extended radar label window RWY conflict alert track RWY conflict alert label Alert in the radar label Alert in the e-strip Alert Window Alert displayed on the radar track Runway Conflict Alert Message Runway Incursion Alert Message Conflicting ATC Clearances Alert Messages Non Conformance To ATC Clearance Alert Messages ATCO Input Error w.r.t Airport Layout Alert Messages Runway Alert CROSS / ENTER Runway warning Traffic Filter Tool D2 - ITWP HMI Solution Specifications Page 2 Draft

4 Range and Bearing Tool Callsign Menu Runway Menu Parking / Stand Menu Parking / Stand Symbol Route Accept Menu Stop At Menu Holding Point Menu for a departure flight Holding Point Menu for an arrival flight Stop bar Menu Runway Status Menu Taxiway Status Menu SID Menu Operator Role Menu Transfer Menu (callsign manu only transfer available) Vehicle e-strip Towed aircraft e-strip Arrival e-strip Departure e-strip CLD e-strip DESCRIPTION OF PROCEDURES WIMP GRAPHICAL USER INTERFACE MANAGEMENT Windows Management Open window Close window Move window Come on top window Iconify window De-iconify window Re-size window Re-scale window Page scroll window Slider scroll window Step scroll window Menus Management Open menu Scroll menu Select menu item Close menu Cancel menu ACCESS CWP Access / exit the CWP functions Log on CWP Log out CWP MANAGE THE DISPLAY LAYOUT Set-Up the Display and Access Screen Settings Save configuration set-up Access configuration set-up Set-up input devices Set-Up Screen Parameters Select day/night/sun settings Fine tune brightness settings Fine tune contrast settings Manage Toolbar Functions Access Tool D2 - ITWP HMI Solution Specifications Page 3 Draft

5 Isolate Tool Replace Tool ACCESS AIR, SURFACE AND TIME INFORMATION Zoom, offset and modify the geographical orientation of the display view Perform Zoom Store zoom Retrieve zoom Zoom back Delete zoom Offset centre Zoom in part Modify geographical orientation of situation display Display Airport Information Display composite video map Display / remove display parking names Display parking names (Quick Look) Set Up Runway / Taxiway Status (open / close) Display and track range and bearing between two points Enable Range and Bearing function Cancel Range and Bearing function Create Range and Bearing Track Cancel Range and Bearing Track Express Time to Go to airspace point Access time information Display Time MANAGE THE DISPLAY FEATURES OF TRAFFIC REPRESENTATION Manage the Radar Labels Configure Radar Labels Content Manage the Electronic Flight Strips (EFS, e-strip) Configure the EFS content Move an EFS Manage air tracks and labels Display speed vectors Set speed vectors value Set track history value Manage label position Deconflict labels automatically Deconflict labels manually Set label leader direction Set leader length Set fixed reference Set track as a reference Move radar babel Resume label position Draw attention to a particular aircraft or vehicle Input intra-cwp traffic marking Share marking with next CWP Share marking with all CWPs Unmark traffic ACCESS DATA CONCERNING THE TRAFFIC SITUATION Access aircraft / vehicle representation Display traffic representation Remove traffic representation Select traffic Deselect Traffic Display extended label Display extended label (Quick Look) Display additional CSD sub-view D2 - ITWP HMI Solution Specifications Page 4 Draft

6 Display EFS section Hide EFS Bay Update Traffic Situation Data Input En Route Clearance Input En Route Clearance via data link Input Start Up Input Pushback Input Taxi Input Line up Input Conditional line up Input Hold Input Hold at Input Abort take off Input Cleared to land Input Cleared for take off Input Airborne Input Go around Input Vacate Input Visual Circuit Cancel the last given order Display Estimated Landing Time (ELDT) Display Time To Touchdown (TTT) Input Actual Landing Time (ALDT) Display Estimated In Block Time (EIBT) Display Actual In-Block-Time (AIBT) Display Estimated Off Block Time (EOBT) Display Actual Off-Block Time (AOBT) Display Target Take Off Time (TTOT) Input Actual Take-Off Time (ATOT) Change RWY for landing (single flight) Change RWY for take-off (single flight) Input holding point (single flight) Change holding point (single flight) Change parking stand Input SID Change SID Cancel SID Mark/Unmark SID Transfer and Coordination Assume Traffic Transfer Traffic Transfer Vehicle / Towed aircraft Select Operator Role for Transfer Filter Traffic Filter traffic (height) MANAGEMENT OF VEHICLES Display vehicles on the masked apron area Hide vehicles on the masked apron area Input Tow Input Release MANAGEMENT OF ALERTS AND WARNINGS General alert management Acknowledgement of an alert Red circle for an alarm Management of alerts for conflicting ATC clearances (CLRS) Display conflicting ATC clearance input End display of conflicting ATC clearance input Management of alerts for infringements of restricted / closed areas (AREA) D2 - ITWP HMI Solution Specifications Page 5 Draft

7 Display runway conflict alert End runway conflict alert Display ATCO input error with restect to airport layout End display ATCO input error w.r.t airport layout Management of alerts for non conformance to ATC instructions Display non conformance to ATC instructions (INFORMATION) End display non conformance to ATC instructions (INFORMATION) Display non conformance to ATC instructions (ALARM) End display non conformance to ATC instructions (ALARM) Display excessive aircraft taxi speed End alert for excessive aircraft taxi speed Management of protecting devices and runway lighting Display stop bar status Manually activate / de-activate stop bar Management of navaids serviceability Display navaids serviceability Management of mobiles on the runway Input Enter Input Cross Display of Runway cross/enter End Display of Runway cross/enter Management of warnings Display parking/stand occupied MANAGEMENT OF MOBILE ROUTING Display Planned Route (aircraft and vehicle) Input a new route for a mobile Input Stop At OTHER FUNCTIONS Display timer Count down time ANNEX: ITWP REQUIREMENTS BASIC HMI ELEMENTS AND DISPLAY MANAGEMENT WIMP graphical user management WIMP GRAPHICAL USER MANAGEMENT Access the CWP functions Access / exit the CWP Manage the display layout Set up the display and access screen settings Manage toolbar functions Access air, surface and time information Zoom, offset and modification of geographical orientation Display surface information Display airspace information Display time information Display additional view Display and track range and bearing Manage the display features of traffic representation Manage the radar label position Manage tracks and labels Display speed vectors Display aircraft and vehicle representation Configure the radar labels Filter out groups of tracks Draw attention to a specific aircraft or vehicle ACCESS DATA CONCERNING THE CURRENT TRAFFIC SITUATION Select an aircraft or vehicle D2 - ITWP HMI Solution Specifications Page 6 Draft

8 6.3.2 Display traffic representation Access all traffic entering or planning to enter a controller s area of responsability ACCESS WEATHER / ADVISORY INFORMATION SET UP THE AIRPORT LAYOUT UPDATE SYSTEM DATA CONCERNING THE CURRENT TRAFFIC SITUATION Update system data according to controller clearances Update system data according to traffic data modifications FLIGHT PLAN EDITION Create a flight plan Modify a flight plan SYSTEM SUPPORTED DATA EXCHANGE AND COORDINATION Traffic data distribution between positions Transfer of control responsibility VEHICLE MANAGEMENT Display / hide vehicles Instruction to vehicle MONITORING AND CONTROL FUNCTIONS Surface hazardous situations detection and alerting Introduction to hazardous situations in the surface management Detection of non conformance to ATC instructions / procedures (PROC) Detection of conflicting ATC clearances (CLRS) Detection of infringement of restricted / closed areas (AREA) Runway conflicts detection and alerting Detection of ATC controllers input errors with respect to airport layout Protecting devices and runway lighting NAVAIDS servicability Management of mobiles on the runway (cross & enter) Management of traffic queues sequencing traffic Departure management Arrival management MOBILE ROUTING MANAGEMENT Display planned route Validate assigned route and display cleared route Input Stop At instruction Input route modification AIR-GROUND DATA COMMUNICATION: DATA LINK FUNCTIONS ANNEX: TRANSVERSAL HF REQUIREMENTS PROCESSES OF INTERACTION Behavioural consistency Level of user awareness Explicit Design to support resource management and monitoring Flexibility in the use of the interface: multiple paths and expert use Minimum cognitive effort Feedback on action INPUTS Input Basics The accessibility of selectable objects Response times Temporary versus Permanent Information Display Policy on default selections Input Devices and Input Events Mouse Keyboard Touch screen D2 - ITWP HMI Solution Specifications Page 7 Draft

9 Menus and Pop-Up menus General use Menu options Options organisation Menu bars Scrolling menus Pop-up menus Input Error Management Policy VISUAL PRESENTATION RULES AND CONVENTIONS Display hardware General Glare Principles for the presentation of data General Principles Organisation of information Text properties Fonts and sizes Vocabulary and abbreviations Style and layout Viewing distances Radar Labels Check boxes (i.e. on EFS) Cursors Maps and Tactical Displays Characteristics Graphic display manipulation Dynamic information update Alarms and critical information Visual alerts General Icons, buttons and controls Use of colours principles Brightness / intensity coding Flashing Auditory alerts Differentiation of signals Signals meaning Duration Acknowledging signals Designing windows General Window states Window organisation Window component Title bar System response time D2 - ITWP HMI Solution Specifications Page 8 Draft

10 1 INTRODUCTION 1.1 Document purpose and scope This document is the deliverable D2 of the WP2 of ITWP project in 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, 28 th 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. D2 - ITWP HMI Solution Specifications Page 1 Draft

11 Main Functions Sub-Functions { { Procedures (solution) { Requirements Objects (solution) { { 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. D2 - ITWP HMI Solution Specifications Page 2 Draft

12 1.4 Acronyms ACC AIBT APP A-SMGCS ATCO ATM ATS CLD CWP Comb. EFS ELDT EOBT GND HMI ICAO IFR ITWP RGB RWY TWR UTC WIMP Area Control Centre Actual In Block Time APProach Advanced Surface Movement Guidance & Control System Air Traffic COntroller Air Traffic Management Air Traffic Services CLearance Delivery Controller Working Position Combined Electronic Flight Strip (synonym to e-strip) Estimated LanDing Time Estimated Off Block Time GrouND Human Machine Interface International Civil Aviation Organisation Instrument Flight Rules Red Green Blue RunWaY ToWeR Universal Time Coordinates Windows, Icons, Menus and Pointers 1.5 Reference documents [Ref. 1] ITWP HMI Solution specifications V2, Draft V , Dec. 2007, Eurocontrol [Ref. 2] ITWP Functional specifications, V1.0, 12 th Dec 2008, Eurocontrol D2 - ITWP HMI Solution Specifications Page 3 Draft

13 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 D2 - ITWP HMI Solution Specifications Page 4 Draft

14 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 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 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 Not concerned to Pending transition The transition from Not concerned to Pending planning state is governed by the following rules: D2 - ITWP HMI Solution Specifications Page 5 Draft

15 Arrival flight: RWY or Combined operator role: at a time parameter before ELDT (Tpending-arr). This time parameter is defined at local level 1. GND operator role: - The transition from Not concerned to Pending on the first GND control position is triggered on a specific event RWY controller input 2 (i.e. Assume ) or at a time parameter before ELDT. The triggering parameter is defined at local level 3. - 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 level 4. - 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 flight 5, 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 Not concerned to Assumed Transition (vehicle 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. D2 - ITWP HMI Solution Specifications Page 6 Draft

16 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). Departure flight: 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 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. Departure flight: 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 Transition between sub-states 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 Tpendingarr: 20 minutes (see above, section ). Tpending-in-arr: 5 minutes; these are defined and subject to modification at local level. D2 - ITWP HMI Solution Specifications Page 7 Draft

17 Ground operator role: the transition is triggered when the APP controller transfers the flight to the RWY controller 6. Departure flight: 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 position 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 clearance 8. 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 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. D2 - ITWP HMI Solution Specifications Page 8 Draft

18 Warning and information alert colour : yellow 9 Alarm colour : red 10 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; proportions: 122,94,54) Button2Depressed: (RGB 24,31,37 ; proportions: 69,79,94) Cursor, Warning, StoredValue colour: yellow Interaction colour: bright blue (RGB 0,100,100; proportions: 0,255,255) Worktop colour: (RGB 29,32,29; 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 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 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 D2 - ITWP HMI Solution Specifications Page 9 Draft

19 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 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. D2 - ITWP HMI Solution Specifications Page 10 Draft

20 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 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 3 rd 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 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) D2 - ITWP HMI Solution Specifications Page 11 Draft

21 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 ARR 11 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 section 12, 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 section 13, 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. D2 - ITWP HMI Solution Specifications Page 12 Draft

22 Figure 2b: RWY Control Position (RWY Bay) updated Dec 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) 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 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. D2 - ITWP HMI Solution Specifications Page 13 Draft

23 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 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). D2 - ITWP HMI Solution Specifications Page 14 Draft

24 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 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. D2 - ITWP HMI Solution Specifications Page 15 Draft

25 Figure 3c: CLD Control Position (CLD Bay) Updated Dec 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. 1 Assume a/c becomes ASSUMED ClearToLand a/c message moves below Runway divider VACATE Transfer To Ground a/c is PENDING-IN a/c message moves To transfer section a/c becomes ASSUMED OUT GO AROUND Transfer To APP a/c message moves To Airborne section VIS a/c message moves back to Final section a) Evolution of an arrival flight when hold at and stop at clerances are not implemented D2 - ITWP HMI Solution Specifications Page 16 Draft

26 a/c becomes ASSUMED a/c message moves below Runway divider Assume ClearToLand HOLD AT a/c is PENDING-IN CROSS STOPAT VACATE a/c message moves To transfer section Transfer To Ground GO AROUND a/c message moves To Airborne section Transfer To APP VIS a/c becomes ASSUMED OUT a/c message moves back to Final section Note: in case two parallel runways, the arrival flight must cross the parallel runway while taxing to the paring stand b) Evolution of an arrival flight when hold at and stop at implemented are not implemented Figure 4: Evolution of an arrival flight (RWY controller); 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 When GND says STBY Start Push Transfer Taxi StopAt Assume When GND says STBY Push Hold D2 - ITWP HMI Solution Specifications Page 17 Draft Assume StopAt

27 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 (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 Cancel 14 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 Cancel states for the undo order facility (e.g. to cancel LND id [LND] in the callsign menu) D2 - ITWP HMI Solution Specifications Page 18 Draft

28 CLD GND CLR PUSH ASSUME START Transfer ASSUME TAXI HOLD Transfer DCLR STOP AT Figure 5b: Evolution of a departure flight (with CLD control position) updated Dec D2 - ITWP HMI Solution Specifications Page 19 Draft

29 Typical Arrival Flight (1/4) Actions / Events RWY controller GND controller SG.1 1. The aircraft is displayed in the RWY bay / Pending Arr. Section. - ELDT -20 min. 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 ). 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. 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 ) 3. Mark and Cancel is the only available options in the callsign menu; there is no option in the e-strip clearance field. D2 - ITWP HMI Solution Specifications Page 20 Draft

30 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. D2 - ITWP HMI Solution Specifications Page 21 Draft

31 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 CA.6a [OPTIONAL] RWY controller inputs Hold at CA.6b [OPTIONAL] RWY controller inputs Cross or Enter CA.6c [OPTIONAL] RWY controller inputs Stop At 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 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) 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 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 cancel the latest selected taxi clearance limit or to close the menu. 2. Hold at, Stop at, Mark, Cancel, Transfer are available options in the 1. The e-strip is displayed in the Pending arrival section of the RWY bay 1. The e-strip is displayed in the Pending arrival section of the RWY bay 1. The e-strip is displayed in the Pending arrival section of the RWY bay 2. The e-strip background colour changes to orange 1. The e-strip is displayed in the Pending arrival section of the RWY bay D2 - ITWP HMI Solution Specifications Page 22 Draft

32 CA.7 RWY controller inputs Transfer (to GND) 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. 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. D2 - ITWP HMI Solution Specifications Page 23 Draft

33 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 CA.9 The aircraft reaches its arrival stand CA.10 AIBT + 2 min. The planning state changes to Not Concerned. - Aircraft data is removed (label) 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 1. EIBT is updated to AIBT (system-generated). Aircraft data is removed (label and e-strip) D2 - ITWP HMI Solution Specifications Page 24 Draft

34 Typical Departure Flight (1/4) -without CLD Control Position- 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. CA.3 GND controller inputs Assume, Start Up or Pushback 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. 1. The GND Controller can either assume the flight via Assume, Start or Pushback (optional) instructions 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). 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 ). D2 - ITWP HMI Solution Specifications Page 25 Draft

35 Typical Departure Flight (2/4) -without CLD Control Position- Actions / Events GND controller RWY controller CA.3 (see above) 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. CA.4 GND controller inputs Taxi CA.7 GND controller inputs Transfer SG.8 The aircraft reaches the holding point 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). 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. if the GND controller has not yet input a Transfer order, this event has the same consequences as in CA.5. 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. 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. 1. if the GND controller has not yet input a Transfer order, this event has the same consequences as in CA.5. D2 - ITWP HMI Solution Specifications Page 26 Draft

36 Typical Departure Flight (3/4) -without CLD Control Position- Actions / Events GND controller RWY controller CA.9 RWY controller inputs Assume 1. The planning state becomes Not concerned. 1. The e-strip moves to the Holding Point section of the taxi-out bay. 2. The e-strip is removed from Transfer to runway section of the runway 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 CA.11 RWY controller inputs Line up or Conditional Line Up CA.12 RWY controller inputs Take-off CA.13 (optional) RWY controller inputs Abort Take-Off CA.14 (optional) RWY controller inputs Airborne - 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 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 Transfer (to TMA), Abort Take-off and Airborne (optional) are available options in the callsign menu and e-strip clearance fields Vacate (most probable option) and Mark are available options in the callsign menu and e-strip clearance fields if Airborne (optional) is input, Transfer is the available option. 2. The e-strip moves to the Airborne section of the Transferred Bay D2 - ITWP HMI Solution Specifications Page 27 Draft

37 Typical Departure Flight (4/4) -without CLD Control Position- Actions / Events GND controller RWY controller CA 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. RWY controller inputs Transfer (to TMA) 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 D2 - ITWP HMI Solution Specifications Page 28 Draft

38 Departure Flight modifications linked to the implementation 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 CA.3 CLD controller inputs CLR or DCLR CA.4 CLD controller inputs START 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. 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. 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. D2 - ITWP HMI Solution Specifications Page 29 Draft

39 Departure Flight modifications linked to the implementation of a CLD position (1/2) Actions / Events CLD Controller GND controller CA.5 1. The planning state is still Assumed, the sub-state changes to Assumed out. The callsign is displayed in Departure 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 CLD controller inputs TRANSFER the rest of the text, leader line and aircraft symbol are displayed in Not Concerned colour. colour ; the rest of the text, leader line and aircraft symbol are displayed in Text Colour. (by clicking on the next frequency, e.g ) 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. 2. Assume (most probable option), Pushback and Mark are the available options in the callsign menu and e-strip clearance fields. 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) D2 - ITWP HMI Solution Specifications Page 30 Draft

40 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 ITWP 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 D2 - ITWP HMI Solution Specifications - Page 31 Draft

41 .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.trsf To manage the distribution of flight data on control positions. 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.proc.clrs.area..rwy General requirements regarding the alerts. To detect / display non conformance to ATC instructions / procedures (former CNF category and MISC category) To detect / display conflicting ATC clearances (former CLR category) 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). 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 D2 - ITWP HMI Solution Specifications - Page 32 Draft

42 4 Description of HMI objects 4.1 Description of HMI objects Worktop General Description HMI Object WORKTOP 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. 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; 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 Evolution - D2 - ITWP HMI Solution Specifications - Page 33 Draft

43 4.1.2 Window General Description HMI Object WINDOW 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. 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. D2 - ITWP HMI Solution Specifications - Page 34 Draft

44 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. D2 - ITWP HMI Solution Specifications - Page 35 Draft

45 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 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 Evolution - D2 - ITWP HMI Solution Specifications - Page 36 Draft

46 4.1.3 Cursor General Description HMI Object CURSOR To indicate to the user the locus of interaction and possible actions on the interface. 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. D2 - ITWP HMI Solution Specifications - Page 37 Draft

47 Invocation Display Position Illustration Always present. Anywhere on the screen, depending on the user s action on the pointing device. Highest display priority. 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 HMI objects WORKTOP Evolution Not implemented (July 2007) D2 - ITWP HMI Solution Specifications - Page 38 Draft

48 4.1.4 Switches Buttons General Description HMI Object SWITCHES BUTTONS 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. 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 are a few special Switch buttons (g), which are employed to manage and 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. Invocation Display Position 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. Not applicable Anywhere on the screen D2 - ITWP HMI Solution Specifications - Page 39 Draft

49 Illustration Requirement Ref. H.BL.HMI.15 H.BL.HMI.16 H.BL.HMI.17 Associated HMI objects MENU WINDOW Evolution - D2 - ITWP HMI Solution Specifications - Page 40 Draft

50 4.1.5 Menu General Description HMI Object MENU To provide a dialogue object by which the user selects one or more inputs from within a range of possible inputs. 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. Invocation Display Position Outside the scrollable area, toggle or push buttons may be added to the menu, allowing for additional functions. The display of a menu is initiated by designation of fields or objects, called initiating objects. 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). D2 - ITWP HMI Solution Specifications - Page 41 Draft

51 Illustration illustration of a menu with a scrolling mechanism and header. Requirement Ref. H.BL.HMI.18 H.BL.HMI.19 H.BL.HMI.20 H.BL.HMI.21 H.BL.HMI.22 H.BL.HMI.23 H.BL.HMI.24 Initiates Close Menu Select Menu Item Close Menu Scroll Menu Used by Open Menu Associated HMI objects SWITCHES BUTTONS Evolution - D2 - ITWP HMI Solution Specifications - Page 42 Draft

52 4.1.6 System Message Window HMI Object SYSTEM MESSAGE WINDOW 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 Initiates Move window Used by Open window Evolution not implemented (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 43 Draft

53 4.1.7 Logon Window General Description HMI Object LOGON WINDOW To allow users accessing to and exiting from the CWP functions. 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 Used by Open window Log On CWP Log Out CWP Associated HMI objects CSD TOOLBOX WINDOW Evolution not implemented (Dec. 2008) Local Parameters Associated HMI objects HMI Object LOCAL PARAMETERS To define a number of the parameters used at local level. These parameters are described in the related requirements. Evolution not implemented (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 44 Draft

54 4.1.9 Preferences Setting Window General Description HMI Object PREFERENCES SETTING WINDOW 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. 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 Invocation Display Position Illustration 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). Invoked by Single Click AB on the PREF toggle button in the General Toolbox Window (Ref. the Access Tool procedure). Below the General Toolbox Window. (Then can be moved anywhere on the composite situation display window) 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 Initiates Associated HMI objects 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 LOCAL PARAMETERS COMPOSITE SITUATION DISPLAY WINDOW D2 - ITWP HMI Solution Specifications - Page 45 Draft

55 Evolution not implemented (Dec. 2008), only load and save buttons are displayed (no action). They are set under the SUP button General Toolbox Window General Description HMI Object GENERAL TOOLBOX WINDOW To group together a set of tools that relate to the whole interface. 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 ). Invocation Display Position Illustration The GENERAL TOOLBOX WINDOW cannot be moved or iconified. On system initialisation, the General Toolbox window is displayed on the display. Bottom left edge of the screen. Requirement Ref. H.BL.TOOL.01 H.BL.TOOL.02 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 SUB-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) D2 - ITWP HMI Solution Specifications - Page 46 Draft

56 Composite Situation Display (CSD) Toolbox Window HMI Object CSD TOOLBOX WINDOW 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 antioverlap (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 Display Position Illustration On system initialisation, the CSD Toolbox Window is displayed open within the CSD Window. Top left edge of the CSD Window. Requirement Ref. H.BL.TOOL.01 H.BL.TOOL.02 H.BL.POS.01 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 TOOL MAP SELECTION TOOL ZOOM TOOL LABEL CONFIGURATION TOOL Evolution Updated (May 2007) D2 - ITWP HMI Solution Specifications - Page 47 Draft

57 Zoom Back Button HMI Object ZOOM BACK BUTTON 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 Initiates Zoom Back Used by Zoom in part Associated HMI objects COMPOSITE SITUATION DISPLAY WINDOW ZOOM TOOL Evolution this object is not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 48 Draft

58 Zoom Tool General Description HMI Object ZOOM TOOL To change the radar display range, to store a particular zoom range, and to offset the situation display window centre. 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. Invocation Display Position Illustration 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. Available as an open tool in the CSD Toolbox Window. As part of the Toolbox Window. Can be moved anywhere on the CSD Window. 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 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 D2 - ITWP HMI Solution Specifications - Page 49 Draft

59 Used by Access Tool Zoom Back Zoom in part Associated HMI objects LOCAL PARAMETERS COMPOSITE SITUATION DISPLAY WINDOW CSD TOOLBOX WINDOW Evolution The save/delete functionality is not implemented (Dec 08) Map Selection Tool General Description Invocation Display Position Illustration HMI Object MAP SELECTION TOOL To display or remove maps bearing different kinds of information. 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. Invoked by Single Click AB on the MAP toggle button in the CSD Display Toolbox Window (Ref. the Access Tool procedure). Under the CSD Toolbox Window. (Then can be moved anywhere on the display window). 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 Used by Access Tool D2 - ITWP HMI Solution Specifications - Page 50 Draft

60 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 WINDOW CSD TOOLBOX WINDOW TAXIWAY STATUS MENU Evolution Updated (Dec ) Speed Vector Track History Tool HMI Object SPEED VECTOR and TRACK HISTORY TOOL s 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 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 WINDOW Particularities local parameters : speed vector display values, number of trail dots to be displayed. Evolution not implemented (Dec. 08) D2 - ITWP HMI Solution Specifications - Page 51 Draft

61 Sub-Views Tool s General Description HMI Object CSD SUB-VIEWS TOOL To create additional sub-views in the Composite Situation Display Window 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 Display Position Illustration Invoked by Single Click AB on the VIEW button in the GENERAL TOOLBOX WINDOW. Above the General Toolbox Window; then, can be moved anywhere. Requirement Ref. Used by Initiates F.BL.VIEW.01 F.BL.VIEW.02 H.BL.VIEW.01 Access Tool 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 DISPLAY WINDOW Evolution Updated in Dec 2008 D2 - ITWP HMI Solution Specifications - Page 52 Draft

62 Airport setup Tool HMI Object AIRPORT SETUP TOOL s 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 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 AIRCRAFT RADAR LABEL RUNWAY STATUS MENU TAXIWAY STATUS MENU 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) D2 - ITWP HMI Solution Specifications - Page 53 Draft

63 EFS Configuration Tool General Description HMI Object EFS CONFIGURATION TOOL To select fields to be displayed in the EFS 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 Display Position Illustration Invoked by Single Click AB on the EFS toggle button in the General Toolbox Window (Ref. the Access Tool procedure). Above the General Toolbox Window. (Then can be moved anywhere on the display window). Requirement Ref. F.BL.SIL.04 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-STRIP 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) D2 - ITWP HMI Solution Specifications - Page 54 Draft

64 EFS Tool s General Description HMI Object EFS TOOL To display or remove display EFS (e-strip) Bays on the situation display. 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 Display Position Illustration Invoked by Single Click AB on the BAYS button in the GENERAL TOOLBOX WINDOW. Below the General Toolbox Window; then, can be moved anywhere on the composite situation display window. On the RWY position On the GND position Requirement Ref. Used by Initiates H.BL.SIL.01 Access Tool 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 SECTION GND PUSHBACK SECTION GND START-UP SECTION GND TAXI IN SECTION GND TAXI-OUT SECTION GND TRANSFER TO RWY 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 Evolution Updated (Dec 2008) D2 - ITWP HMI Solution Specifications - Page 55 Draft

65 Pending Departures Section (GND role) s General Description Invocation Display Position Illustration HMI Object GND PENDING DEPARTURES SECTION To display pending departures EFS (GND role) 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. Automatically displayed (system-generated); can be removed from the display via the By default, the section is presented with other GND sections at the bottom of the CSD window; then, can be moved. Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Evolution Updated (Dec. 2008) examples of pending dep section (GND role) D2 - ITWP HMI Solution Specifications - Page 56 Draft

66 Start-Up Section (GND role) s General Description Invocation Display Position Illustration HMI Object GND START-UP SECTION To display start-up flights (GND role) 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. Automatically displayed (system-generated) See GND PENDING DEPARTURES SECTION Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Evolution Updated (July 2007) D2 - ITWP HMI Solution Specifications - Page 57 Draft

67 Pushback Section (GND role) s General Description HMI Object GND PUSHBACK SECTION To display pushback flights (GND role) 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. Invocation Display Position Illustration Automatically displayed (system-generated) See GND PENDING DEPARTURES SECTION Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Hide EFS Bay Associated HMI objects DEP E-STRIP Evolution Updated (Dec. 2008) added clearances D2 - ITWP HMI Solution Specifications - Page 58 Draft

68 Taxi-out Section (GND role) s General Description Invocation Display Position Illustration HMI Object GND TAXI-OUT SECTION To display taxi out flights (GND role) 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. Automatically displayed (system-generated) See GND PENDING DEPARTURES 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 Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP VEHICLE E-STRIP TOWED AIRCRAFT E-STRIP Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 59 Draft

69 Pending Arrivals Section (GND role) s General Description Invocation Display Position Illustration HMI Object GND PENDING ARRIVALS SECTION To display pending arrivals flights (GND role) 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. Automatically displayed (system-generated) See GND PENDING DEPARTURES SECTION Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Evolution Updated (Dec. 2008) Examples of pending arrivals (GND role) D2 - ITWP HMI Solution Specifications - Page 60 Draft

70 Taxi-in Section (GND role) s General Description Invocation Display Position Illustration HMI Object GND TAXI IN SECTION To display assumed arrivals flights (GND role) which taxi from the RWY to the parking stand. 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. Automatically displayed (system-generated) See GND PENDING DEPARTURES SECTION Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Evolution Updated (July 2007) D2 - ITWP HMI Solution Specifications - Page 61 Draft

71 Transfer to RWY Section (GND role) s General Description Invocation Display Position Illustration HMI Object GND TRANSFER TO RWY SECTION To display assumed departure flights (GND role) that have been transferred to the RWY controller 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. Automatically displayed (system-generated) See GND PENDING DEPARTURES SECTION Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Evolution Updated (July 2007) D2 - ITWP HMI Solution Specifications - Page 62 Draft

72 Pending Departures Section (RWY role) HMI Object RWY PENDING DEPARTURES SECTION s 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 Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Evolution Updated (September 2007) D2 - ITWP HMI Solution Specifications - Page 63 Draft

73 Holding Point Section (RWY role) s General Description Invocation Display Position Illustration HMI Object RWY HOLDING POINT SECTION To display departure flights which are assumed by the RWY controller; to display vehicles to assume and assumed ones under the controllers responsibility. 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. Automatically displayed (system-generated) See RWY PENDING DEPARTURES SECTION 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 H.BL.SIL.01 Ref. Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP VEHICLE E-STRIP TOWED AIRCRAFT E-STRIP Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 64 Draft

74 Pending Arrivals Section (RWY role) s General Description Invocation Display Position Illustration HMI Object RWY PENDING ARRIVALS SECTION To display pending arrivals flights (relative to an arrival RWY) 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. Automatically displayed (system-generated) See GND PENDING DEPARTURES SECTION Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Evolution Updated (July 2007); Go-Around order is not implemented (Dec. 08) D2 - ITWP HMI Solution Specifications - Page 65 Draft

75 Final Section (RWY role) s General Description Invocation Display Position Illustration HMI Object RWY FINAL SECTION To display flights which are in final approach phase (RWY controller role) 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. Automatically displayed (system-generated) See RWY PENDING DEPARTURES SECTION Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Evolution Updated (July 2007); Go-Around order is not implemented (Dec. 08) D2 - ITWP HMI Solution Specifications - Page 66 Draft

76 RWY Section (RWY role) s General Description Invocation Display Position Illustration HMI Object RWY SECTION To display flights that use the runway and arrival flights that are about to use the RWY. 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. Automatically displayed (system-generated) See RWY PENDING DEPARTURES SECTION 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 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 Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 67 Draft

77 RWY Taxi-In Section (RWY role) s General Description Invocation Display Position Illustration HMI Object RWY TAXI IN SECTION To display arrival (landed) aircraft which will be transferred to the GND controller 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. Automatically displayed (system-generated) See RWY SECTION Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects ARR E-STRIP Evolution Updated (September 2007) D2 - ITWP HMI Solution Specifications - Page 68 Draft

78 RWY Airborne Section (RWY role) s General Description Invocation Display Position Illustration HMI Object RWY AIRBORNE SECTION To display departure airborne flights 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. Automatically displayed (system-generated) See RWY SECTION Requirement Ref. H.BL.SIL.01 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) D2 - ITWP HMI Solution Specifications - Page 69 Draft

79 Pending Departure Section (CLD role) s General Description Invocation Display Position Illustration HMI Object CLD PENDING DEPARTURE SECTION To display departure flights 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. Automatically displayed (system-generated) By default, the section is presented with other CLD sections at the bottom of the CSD window; then, can be moved. Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Used by Display EFS section Evolution Updated (July 2007) D2 - ITWP HMI Solution Specifications - Page 70 Draft

80 CLD Active Section (CLD role) s General Description Invocation Display Position Illustration HMI Object CLD ACTIVE SECTION To display departure airborne flights 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. Automatically displayed (system-generated) By default, the section is presented with other CLD sections at the bottom of the CSD window; then, can be moved. or Requirement Ref. H.BL.SIL.01 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) D2 - ITWP HMI Solution Specifications - Page 71 Draft

81 CLD Start Up Section (CLD role) s General Description Invocation Display Position Illustration HMI Object CLD START UP SECTION To display departure airborne flights 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. Automatically displayed (system-generated). By default, the section is presented with other CLD sections at the bottom of the CSD window; then, can be moved. Requirement Ref. H.BL.SIL.01 Used by Display EFS section Initiates Move window Associated HMI objects DEP E-STRIP Used by Display EFS section Evolution Updated (July 2007) D2 - ITWP HMI Solution Specifications - Page 72 Draft

82 Clock Window General Description Invocation Display Position Illustration HMI Object CLOCK WINDOW To display time (UTC) The CLOCK WINDOW displays the UTC time System-generated. Top right corner of the CSD Window; then can be moved anywhere on the CSD Window. clock window (unselected) clock window (selected) Requirement Ref. F.BL.TIME.01 H.BL.TIME.01 Initiates Move window Used by Display Universal Time Associated HMI objects - Evolution Updated (November 2007) Weather Information Window s General Description HMI Object MET INFORMATION WINDOW To provide the controller with information about MET information 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 Invocation Display Position Updates of values (e.g. ATIS letter designation, QNH, Temperatures etc.) will be displayed in warning colour (yellow). Invoked by Single Click AB on the MET button in the General Toolbox Window Under the General Toolbox Window (top left corner); then, can be moved anywhere on the composite situation display window. D2 - ITWP HMI Solution Specifications - Page 73 Draft

83 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 Used by Open window Initiates Move window Close window Re-scale window Come on top window Associated HMI objects GENERAL TOOLBOX WINDOW Evolution Updated (July 2007) D2 - ITWP HMI Solution Specifications - Page 74 Draft

84 NAVAIDS Information Window s General Description HMI Object NAVAIDS INFORMATION WINDOW To provide the controller with information about NAVAIDS serviceability. 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 Display Position Illustration 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). Above the General Toolbox Window. (Then can be moved anywhere on the composite situation display window) Requirement Ref. Used by Initiates H.SN.NAV.01 H.SN.NAV.02 Open window Move window Close window Erreur! Source du renvoi introuvable. Come on top window Associated HMI objects GENERAL TOOLBOX WINDOW Evolution Updated (August 2007) D2 - ITWP HMI Solution Specifications - Page 75 Draft

85 Composite Situation Display (CSD) Window General Description HMI Object COMPOSITE SITUATION DISPLAY WINDOW To provide a display of the composite ground / air situation 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 Display Position Illustration On system initialisation the Composite Situation Display is open on the display. Full screen display Requirement Ref. H.BL.ZOOM.01 H.BL.MAP.01 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 D2 - ITWP HMI Solution Specifications - Page 76 Draft

86 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) Radar Track General Description HMI Object RADAR TRACK To provide graphical representation of traffic position. 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 Display Position Displayed when the traffic is present on the situation display. At traffic co-ordinates provided by the Surveillance System. D2 - ITWP HMI Solution Specifications - Page 77 Draft

87 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 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 Evolution Updated (Dec. 2008) 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. D2 - ITWP HMI Solution Specifications - Page 78 Draft

88 Radar Label HMI Object RADAR LABEL 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 General Description To provide the possibility to easily access additional information concerning the aircraft in the air on controller request. 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. D2 - ITWP HMI Solution Specifications - Page 79 Draft

89 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, ); 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; Display Position Note: Data link identifier is displayed around the callsign. Attached to the radar track with the leader line according to the selected label position monitoring options D2 - ITWP HMI Solution Specifications - Page 80 Draft

90 Illustrations (default settings) minimum air label data link equipped aircraft (not concerned state) minimum air label (not concerned state) minimum air label (pending state / no value) (assumed state / no value) minimum air label data link equipped aircraft minimum air label (pending state / pending in) minimum air label (assumed state / no value) minimum air label (assumed state / assumed out) minimum departure label (not concerned state) minimum departure label (pending state / no value) minimum departure label (pending state / pending in) minimum departure label (assumed state / no value) minimum departure label (assumed state / assumed out) D2 - ITWP HMI Solution Specifications - Page 81 Draft

91 Illustrations (default settings) selected air label (not concerned state) selected air label (pending state / no value) selected air label (pending state / pending in) selected air label (assumed state / no value) selected air label (assumed state / assumed out) selected air label (assumed state / no value) selected departure label data link equipped aircraft (pending state / no value) selected departure label (not concerned) selected departure label (pending state / no value) D2 - ITWP HMI Solution Specifications - Page 82 Draft

92 selected departure label (pending state / pending in) selected departure label (assumed state / no value) selected departure label (assumed state / assumed out) selected departure label assumed state / assumed out) Requirement Ref. H.BL.VECT.02 H.BL.TRAF.02 H.BL.TRAF.03 H.BL.TRAF.04 H.BL.TRAF.05 H.BL.SIL.03 H.BL.SEL.03 H.BL.POS.06 H.BL.VECT.02 H.BL.UPD.03 H.FD.TRSF.05 H.BL.UPD.05 F.BL.SIL.04 F.BL.LBL.03 H.DL.IDF.1 Initiates Move Radar Label Select Traffic Deselect Traffic Display Extended Label Display Extended Label (Quick Look) Input Abort Take Off Input Airborne Input Assume Input Actual Time of Arrival Input Actual Take Off Time Input Clear for Take-Off Input Cleared to Land Input Conditional Line Up Input Visual Circuit Input Go Around Input Hold Input Holding Point Input intra- CWP traffic marking Input Line Up Input Pushback Input SID Input Start- Up Input Taxi Input Vacate Mark / Unmark SID Transfer Traffic Unmark Traffic Input CLR Input DCLR Used by Set Leader Direction Set Leader Length Resume Label Position Remove Traffic Representation Display Traffic Representation Deconflict Labels Automatically Deconflict Labels Manually Associated HMI objects RADAR TRACK EXTENDED RADAR LABEL EXTENDED RADAR LABEL WINDOW LABEL CONFIGURATION TOOL LABEL OVERLAP MANAGEMENT TOOL COMPOSITE SITUATION DISPLAY WINDOW CALLSIGN MENU DEP E-STRIP ARR E-STRIP RUNWAY MENU SID MENU PARKING STAND MENU Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 83 Draft

93 Vehicle Radar Label HMI Object VEHICLE RADAR LABEL 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 General Description To provide the possibility to easily access additional information concerning the vehicle on the ground on controller request. 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 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): 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. D2 - ITWP HMI Solution Specifications - Page 84 Draft

94 General Description Display Position Illustrations (default settings) 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). 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. Attached to the radar track with the leader line according to the selected label position monitoring options minimum vehicle label (not concerned state) minimum vehicle label (not concerned state/ no value) minimum vehicle label (pending state / pending in) minimum vehicle label (assumed state / clearance) minimum vehicle label (assumed state / assumed out) minimum vehicle label (assumed state / no value) D2 - ITWP HMI Solution Specifications - Page 85 Draft

95 Illustrations (default settings) selected vehicle label (not concerned state) selected vehicle label (not concerned state / no value) selected vehicle label (pending state / pending in) selected vehicle label (assumed state / no value) selected vehicle label (assumed state / assumed out) selected vehicle label (mark assumed vehicle) Requirement Ref. Initiates Used by Associated HMI objects H.BL.VECT.02 H.BL.TRAF.02 H.BL.TRAF.03 H.BL.TRAF.04 H.BL.TRAF.05 H.BL.SIL.03 H.BL.SEL.03 H.BL.POS.06 H.BL.VECT.02 H.BL.UPD.03 H.FD.TRSF.05 H.BL.UPD.05 F.BL.SIL.04 F.BL.LBL.03 Move Radar Label Select Traffic Deselect Traffic Input Assume Input Hold Input Holding Point Input intra-cwp traffic marking Input Taxi Input Vacate Mark / Unmark SID Transfer Traffic Unmark Traffic Input CLR Set Leader Direction Set Leader Length Resume Label Position Remove Traffic Representation Display Traffic Representation Deconflict Labels Automatically Deconflict Labels Manually RADAR TRACK VEHICLE RADAR LABEL LABEL CONFIGURATION TOOL LABEL OVERLAP MANAGEMENT TOOL COMPOSITE SITUATION DISPLAY WINDOW RWY CONFLICT ALERT LABEL CALLSIGN MENU VEHICLE E- STRIP Evolution Updated (November 2007) D2 - ITWP HMI Solution Specifications - Page 86 Draft

96 Towed Aircraft Radar Label HMI Object TOWED AIRCRAFT RADAR LABEL 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 General Description To provide the possibility to easily access additional information concerning the Towed aircraft on the ground on controller request. 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. 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). The set up of towed aircraft label is enabled as for vehicles. 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): 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. D2 - ITWP HMI Solution Specifications - Page 87 Draft

97 General Description Display Position Illustrations (default settings) 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). 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. Attached to the radar track with the leader line according to the selected label position monitoring options minimum towed a/c label (not concerned state) minimum towed a/c label (not concerned state/ no value) minimum towed a/c label (pending state / pending in) minimum towed a/c label (assumed state / clearance) minimum towed a/c label (assumed state / assumed out) minimum towed a/c label (assumed state / no value) D2 - ITWP HMI Solution Specifications - Page 88 Draft

98 Illustrations (default settings) selected tow a/c label (not concerned state) selected towed a/c label (not concerned state / no value) selected towed a/c label (pending state / pending in) selected towed a/c label (assumed state / no value) selected towed a/c label (assumed state / assumed out) selected towed a/c label (mark assumed) Requirement Ref. Initiates Used by Associated objects Particularities HMI Evolution November 2007 H.BL.VECT.02 H.BL.TRAF.02 H.BL.TRAF.03 H.BL.TRAF.04 H.BL.TRAF.05 H.BL.SIL.03 H.BL.SEL.03 H.BL.POS.06 H.BL.VECT.02 H.BL.UPD.03 H.FD.TRSF.05 H.BL.UPD.05 F.BL.SIL.04 F.BL.LBL.03 Move Radar Label Select Traffic Deselect Traffic Input Assume Input Hold Input Holding Point Input intra-cwp traffic marking Input Taxi Input Vacate Mark / Unmark SID Transfer Traffic Unmark Traffic Input CLR Set Leader Direction Set Leader Length Resume Label Position Remove Traffic Representation Display Traffic Representation Deconflict Labels Automatically Deconflict Labels Manually RADAR TRACK VEHICLE RADAR LABEL LABEL CONFIGURATION TOOL LABEL OVERLAP MANAGEMENT TOOL COMPOSITE SITUATION DISPLAY WINDOW CALLSIGN MENU TOWED AIRCRAFT E-STRIP Towed aircraft is handled as a vehicle. Two types of towed aircraft mouvements are implemented: notified (visible) and not notified (behaviour as vehicle) D2 - ITWP HMI Solution Specifications - Page 89 Draft

99 Label Configuration Tool General Description HMI Object LABEL CONFIGURATION TOOL To display / remove supplementary data in either the minimum or extended format of all radar labels. 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 Display Position Invoked by Single Click AB on the LABEL toggle button in the General Toolbox Window (ref. the Access Tool procedure). Under the CSD TOOLBOX WINDOW; Then can be moved anywhere on Display Window. D2 - ITWP HMI Solution Specifications - Page 90 Draft

100 Illustration Requirement Ref. H.BL.LBL.01 H.BL.LBL.03 H.BL.LBL.04 Initiates Move window Come on top window Iconify window De-iconify window Isolate Tool Configure radar labels content Set Leader Length Set Leader Direction Close window Used by Access Tool Associated HMI objects RADAR LABEL CSD TOOLBOX WINDOW VEHICLE RADAR LABEL TOWED AIRCRAFT RADAR LABEL Evolution Updated (November 2007) (Min+ Sel) not changed yet D2 - ITWP HMI Solution Specifications - Page 91 Draft

101 Label Overlap Management Tool General Description Invocation Display Position Illustration HMI Object LABEL OVERLAP MANAGEMENT TOOL 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. 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 antioverlap 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. Invoked by Single Click AB on the OVERLAP toggle button in the General Toolbox Window. Under the General Toolbox Window. (then can be moved anywhere) 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 Initiates Move window Come on top window Iconify window De-iconify window Isolate Tool Replace Tool Set Leader Length Set 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 Evolution Object is partially implemented (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 92 Draft

102 Range and bearing tracker link General Description HMI Object RANGE and BEARING TRACKER LINK 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. 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 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 SITUATION DISPLAY WINDOW CSD TOOLBOX WINDOW RANGE AND BEARING TOOL Particularities The Range and Bearing information should be included in the global information antioverlap policy. Evolution Not implemented (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 93 Draft

103 Extended radar label General Description HMI Object EXTENDED RADAR LABEL 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. 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 CLEARANCE RWY SeQ N M Time2 Airline SSR ADES QNH RMKS Invocation Display Position Illustration b) Arrival aircraft Time1 C/S TYPE/VW Stand (-Hold) I or V CLEARANCE RWY SeQ N M Time2 Airline SSR ADES QNH RMKS 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. 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. 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 Used by Display Extended Label Display Extended Label (Quick Look) Associated HMI objects EXTENDED RADAR LABEL WINDOW Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 94 Draft

104 Extended radar label window General Description Invocation Display Position Illustration HMI Object EXTENDED RADAR LABEL WINDOW To display the EXTENDED RADAR LABEL content of an aircraft or vehicle 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. Invoked by Single Click IB on the callsign field within the radar label or anywhere else that this field is displayed. At the radar label position. 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 Initiates Close window Come on top window Move window Used by Open window Display Extended Label Associated HMI objects Evolution This window is not any more in the ITWP. Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 95 Draft

105 RWY conflict alert track General Description HMI Object RWY CONFLICT ALERT TRACK To indicate to the controller a potential runway conflict alert (step 1 or step 2 alert) is likely to occur. 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 Used by Display Runway Conflict (step 1 alert) Display Runway Conflict (step 2 alert) End Runway Conflict Alert Associated HMI objects RADAR TRACK Evolution not implemented (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 96 Draft

106 RWY conflict alert label HMI Object RWY CONFLICT ALERT LABEL 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 Display Position Illustration System generated; displayed automatically by the system when a runway conflict alert is detected. Callsigns of the involved traffic radar label - information alert radar label - infromation alert runway conflict alert / step 1 runway conflict alert / step 1 (selected label) (minimum label) Requirement Ref. Used by radar label - Alarm radar label - Alarm runway conflict alert / step 2 runway conflict alert / step 2 (selected label) (minimum label) H.SN.AREA.1 H.SN.AREA.2 H.SN.AREA.3 H.SN.AREA.4 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 Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 97 Draft

107 Alert in the radar label General Description HMI Object ALERT IN LABEL 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) 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 Display Position Illustration System generated; displayed automatically by the system when an alert is detected. Callsigns of the involved traffic 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 D2 - ITWP HMI Solution Specifications - Page 98 Draft

108 Used by Display Runway Conflict (step 1 alert) Display Runway Conflict (step 2 alert) End Runway Conflict Alert Acknowledge alert Display Excessive Taxi Speed End Display Conflicting ATC clearance Input Display Non Conformance to ATC Instructions Display ATCO Input Error w.r.t. Airport Layout Associated HMI objects RADAR LABEL EXTENDED RADAR LABEL VEHICLE RADAR LABEL TOWED AIRCRAFT RADAR LABEL Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 99 Draft

109 Alert in the e-strip HMI Object ALERT IN E-STRIP 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 Invocation Display Position Illustration 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. System generated; displayed automatically by the system when an alert is detected. Callsigns of the involved traffic in the e-strip. 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 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 Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 100 Draft

110 Alert Window General Description HMI Object ALERT WINDOW To display alert messages produced by the safety support functions. The ALERT WINDOW displays a list of alert messages, each line correspond to an alert message. Invocation Display Position Illustration 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). Top of the CSD Window; can not be moved anywhere on the CSD Window. 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 H.SN.AREA.1 H.SN.AREA.2 H.SN.AREA.3 H.SN.AREA.4 H.SN.CLRS.1 H.SN.CLRS.2 Ref. 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 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 MESSAGE ATCO INPUT ERROR w.r.t. AIRPORT LAYOUT ALERT MESSAGE RUNWAY INCURSION MESSAGE D2 - ITWP HMI Solution Specifications - Page 101 Draft

111 Evolution Updated (Dec. 2008) Alert displayed on the radar track HMI Object ALERT RADAR TRACK 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 Invocation Display Position Illustration 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: System generated; displayed automatically by the system when an alert step 2 is detected. Radar track of the involved traffic Requirement Ref. Used by Example of ALARM (step 2 alert) displayed round the radar track 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 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 Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 102 Draft

112 Runway Conflict Alert Message General Description Invocation Display Position Illustration HMI Object RUNWAY CONFLICT ALERT MESSAGE To provide to the controller information on the potential runway conflict alert. 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. System generated when a runway conflict alert is detected In the ALERT WINDOW example of runway conflict alert message (alarm) * example of runway conflict alert message (information) Requiremen H.SN.AREA.1 H.SN.AREA.2 H.SN.AREA.3 H.SN.AREA.4 t Ref. 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 Particulariti - es Evolution Updated (Dec 2008) D2 - ITWP HMI Solution Specifications - Page 103 Draft

113 Runway Incursion Alert Message General Description Invocation Display Position Illustration HMI Object RUNWAY INCURSION MESSAGE To provide to the controller information of the entrence of mobile in the runway protected area. 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. System generated when a runway incursion is detected In the ALERT WINDOW Requirement Ref. H.SN.AREA.1 H.SN.AREA.2 H.SN.AREA.3 H.SN.AREA.4 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 Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 104 Draft

114 Conflicting ATC Clearances Alert Messages General Description Invocation Display Position Illustration HMI Object CONFLICTING ATC CLEARANCES ALERT MESSAGE To provide to the controller information when the alert function detects manually input of inconsistent clearances. 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. System generated when a manual inconsistent clearances input is detected In the ALERT WINDOW 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 Requiremen H.SN.CLRS.2 H.SN.CLRS.1 t Ref. 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 Particulariti - es Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 105 Draft

115 Non Conformance To ATC Clearance Alert Messages General Description Invocation Display Position Illustration HMI Object NON CONFORMANCE TO ATC CLEARANCE ALERT MESSAGE To provide to the controller information when the alert function detects non conformance to the given instruction. 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. System generated when a non conformance to the given instruction is detected In the ALERT WINDOW 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) Requiremen H.SN.PROC.2 H.SN.PROC.1 t Ref. 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 Particulariti - es Evolution Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 106 Draft

116 ATCO Input Error w.r.t Airport Layout Alert Messages General Description Invocation Display Position Illustration HMI Object ATCO INPUT ERROR w.r.t. AIRPORT LAYOUT ALERT MESSAGE To provide to the controller information when the alert function detects that in the manual input w.r.t airport layout is an error. 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. System generated when ATCO input error w.r.t airport layout is detected In the ALERT WINDOW 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) Requiremen H.SN.AREA.5 H.SN.AREA.6 t Ref. Initiates Come on top window Move window Used by example of alert message when RWY type is not appropriate for an a/c Display ATCO Input Error w.r.t. Airport Layout 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 Particulariti - es Evolution Updated (Decembre 2008) D2 - ITWP HMI Solution Specifications - Page 107 Draft

117 Runway Alert General Description HMI Object RUNWAY ALERT To provide clear and visible runway indication whenever a runway conflict alert (step 1 or step 2) is detected. 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 Used by Display Runway Conflict (step 1 alert) Display Runway Conflict (step 2 alert) End Runway Conflict Alert Associated HMI objects Evolution not implemented (Dec 2008) CROSS / ENTER Runway warning General Description Invocation Display Position Illustration HMI Object DISPLAY CROSS/ENTER RUNWAY To provide clear and visible runway indication whenever a runway CROSS or ENTER instruction is given to an aircraft, vehicle or towed aircraft. 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. 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). On the shape of the concerned runway 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 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) D2 - ITWP HMI Solution Specifications - Page 108 Draft

118 Traffic Filter Tool General Description HMI Object TRAFFIC FILTER TOOL To provide the means to the controllers to filter categories of traffic to be displayed. 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 Display Position Illustration Invoked by Single Click AB on the HEIGHT toggle button in the CSD Display Toolbox Window (Ref. the Access Tool procedure). Under the CSD Toolbox Window; then can be moved anywhere on the display window. Requirement Ref. Initiates Used by Associated HMI objects Evolution possible height filter tool H.BL.FILT.01 Replace Tool Isolate Tool Move window Come on top window Filter traffic (height) Close window De-iconify window Iconify window Access Tool RADAR TRACK RADAR LABEL CSD TOOLBOX WINDOW COMPOSITE SITUATION DISPLAY WINDOW Updated (Dec. 2008); Height button is implemented (May 2007) but not the functionality. D2 - ITWP HMI Solution Specifications - Page 109 Draft

119 Range and Bearing Tool General Description HMI Object RANGE AND BEARING TOOL To provide Range and Bearing functionality 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 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 WINDOW Evolution Not implemented (Dec 2008) D2 - ITWP HMI Solution Specifications - Page 110 Draft

120 Callsign Menu General Description HMI Object CALLSIGN MENU 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. 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 Display Position 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. When invoked, the Callsign Menu pops-up so that the default item is under the cursor. D2 - ITWP HMI Solution Specifications - Page 111 Draft

121 Illustration examples of aircraft callsign menu examples of vehicle callsign menu examples of tow aircraft callsign menu Requirement Ref. H.BL.ORD.02 H.BL.ORD.03 H.BL.ORD.04 H.BL.ORD.05 H.BL.ORD.06 H.BL.ORD.07 H.BL.ORD.08 H.BL.ORD.09 H.BL.ORD.10 H.BL.ORD.11 H.BL.ORD.12 H.BL.ORD.13 H.BL.WAR.01 H.BL.ORD.14 F.SN.RWY.1 F.ROUTE.ORD.1 H.ROUTE.ORD.1 Initiates Input Clear for Take-Off Input Cleared to Land Input Conditional Line Up Input Visual Circuit Input Go Around Input Hold Input Line Up Input Pushback Input intra-cwp traffic marking Input Vacate Select Menu Item Close Menu Cancel order / instruction Input Stop At Used by Open Menu Associated HMI objects RADAR LABEL EXTENDED RADAR LABEL VEHICLE E-STRIP DEP E- STRIP ARR E-STRIP VEHICLE RADAR LABEL TOWED AIRCRAFT RADAR LABEL TOWED AIRCRAFT E-STRIP Evolution Updated (Dec 2008) D2 - ITWP HMI Solution Specifications - Page 112 Draft

122 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. D2 - ITWP HMI Solution Specifications - Page 113 Draft

123 1. Callsign menu for a GND controller Main state Not concerned CALLSIGN Menu for a GND controller - Departure Flight Pending Pending Assumed Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value No Value Assumed out CALLSIGN Menu option ASSUME When Push-back clearance has been given TAXI * PUSH BACK * When Taxi clearance has been given TRANSFER * HOLD STOP AT When the taxi clearance has been given MARK * * * CANCEL Note: updated in Dec 2008 D2 - ITWP HMI Solution Specifications - Page 114 Draft

124 CALLSIGN Menu for a GND controller - Arrival Flight Main state Not concerned Pending Pending Assumed Sub-State No Value No Value Pending-in No Value CALLSIGN Menu option TAXI * HOLD * STOP AT * MARK * * CANCEL Note: updated in Dec 2008 D2 - ITWP HMI Solution Specifications - Page 115 Draft

125 2. Callsign menu for a RWY controller Main state Not concerned Pending Pending Callsign menu for a RWY controller - Departure Flight Assumed Assumed Assumed Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value No Value No Value No Value Assumed out Clearance field option ASSUME * When Hold instruction has been given HOLD LINE-UP * * CONDITIONAL LINE-UP TAKE-OFF * When Conditional line-up or line-up clearance has been given TRANSFER * ABORT TAKE- OFF When Take-Off clearance has been given VACATE * When Abort Takeoff clearance has been given 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 D2 - ITWP HMI Solution Specifications - Page 116 Draft

126 Main state Not concerned Pending CALLSIGN Menu for a RWY controller - Arrival Flight Pending Assumed Assumed Assumed Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value No Value No Value No Value Assumed out CALLSIGN Menu option When Assume has been input by the controller When Continue Approach clearance has been given When Cleared to land clearance has been given When Go-Around clearance has been given When Vacate clearance has been given ROF * ASSUME * CLEARED * * TO LAND GO AROUND VACATE * FINAL * TRANSFER to GND to APP * to GND MARK * * CANCEL Note: updated in May 2007 D2 - ITWP HMI Solution Specifications - Page 117 Draft

127 Main state Not concerned Pending CALLSIGN Menu for a COMBINED Role - Departure Flight Pending Assumed Assumed Assumed Assumed Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value No Value No Value No Value No Value Assumed out CALLSIGN Menu option When pushback clearance has been given When Taxi clearance has been given When the cond.line-up or line-up clearance has been given When Take-Off clearance has been given When Abort Take-off clearance has been given START-UP * ASSUME TAXI * PUSH BACK * HOLD STOP AT LINE-UP * COND. LINE UP TAKE-OFF * ABORT TAKE-OFF VACATE * TRANSFER * MARK * * * CANCEL D2 - ITWP HMI Solution Specifications - Page 118 Draft

128 Note: updated in Dec 2008 Main state Not concerned Pending CALLSIGN Menu for a COMBINED role - Arrival Flight Pending Assumed Assumed Assumed Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value No Value No Value No Value Assumed out CALLSIGN Menu option When Assume has been input by the controller When Continue Approach clearance has been given When Cleared to land clearance has been given When Go-Around clearance has been given When Vacate clearance has been given ROF * ASSUME * CLEARED * * TO LAND GO AROUND VACATE * FINAL * TRANSFER to APP TAXI * STOP AT HOLD MARK * * CANCEL Note: updated in Dec HOLD AT is not included as it is specific to the CDG airport. D2 - ITWP HMI Solution Specifications - Page 119 Draft

129 Runway Menu General Description Invocation HMI Object RUNWAY MENU To allow the controller to change the runway for landing or the runway for take off for a single flight. The runway menu is used to change the RWY for take off (if departure flight) or RWY for landing (arriving flight). 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 Illustration When invoked, the runway menu pops-up so that the possible RWY options are displayed under the cursor. example of runway menu Requirement Ref. F.BL.UPD.02 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 Evolution Updated (September 2007) D2 - ITWP HMI Solution Specifications - Page 120 Draft

130 Parking / Stand Menu General Description Invocation Display Position Illustration HMI Object PARKING STAND MENU To allow the controller to change the parking stand for an arrival flight. The parking / stand menu is used to change the parking stand for an arrival aircraft. It displays the possible parking options to the controller. 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 ). When invoked, the runway menu pops-up so that the possible parking stand options are displayed under the cursor. Requirement Ref. Initiates Used by Associated HMI objects Particularities example of parking/stand menu F.BL.UPD.02 Evolution Updated (July 2007) Open Menu Close Menu Select Menu Item Scroll Menu Change Parking Stand When the controller scrolls over the parking position, then the parking symbol is highlighted on the airport map (not implemented) D2 - ITWP HMI Solution Specifications - Page 121 Draft

131 Parking / Stand Symbol General Description Invocation Display Position Illustration HMI Object PARKING STAND SYMBOL To allow the controller to display / remove display parking names on the airport map. The display / remove display of parking names (fixed) interaction is enabled via the parking stand symbol The invocation of display / remove display of parking stand is performed by single click AB on the parking stand symbol 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). display parking names (example) remove display parking names Requirement Ref. F.BL.UPD.02 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) D2 - ITWP HMI Solution Specifications - Page 122 Draft

132 Route Accept Menu General Description Invocation Display Position Illustration HMI Object ROUTE ACCEPT MENU To allow the controller to accept a modification of the initally planned route. The route accept menu is used to accept a route modification or to confirm the choice of the system proposed route modification. 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. When invoked, the route accept menu is displayed on the right of the last selected point of the route. Requirement Ref. H.ROUTE.CHG.1 H.ROUTE.CLR.1 Initiates Open Menu Used by Cancel Menu Close Menu Select Menu Item Evolution Updated (Dec. 2008) Stop At Menu General Description Invocation Display Position Illustration HMI Object STOP AT MENU To allow the controller to clear an aircraft to taxi until a certain point on the initially planned route. 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. 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. When invoked, the stop at menu is displayed on the right of the planned route. Requirement Ref. F.ROUTE.ORD.1 H.ROUTE.ORD.1 Initiates Open Menu Used by Cancel Menu Close Menu Select Menu Item Input Stop At Evolution Updated (Dec to be further developed) D2 - ITWP HMI Solution Specifications - Page 123 Draft

133 Holding Point Menu for a departure flight General Description Invocation HMI Object HOLDING POINT MENU To indicate that a departure flight has been instructed to taxi to a specific holding point. The runway menu is used to change the holding point. 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 Initiates Open Menu Used by Cancel Menu Close Menu Select Menu Item Evolution not implemented (May 2007) Holding Point Menu for an arrival flight General Description Invocation HMI Object HOLDING POINT MENU ARR To indicate that an arrival flight has been instructed to taxi to a specific holding point. 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). 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 Requirement Ref. Initiates Example of holding point menu (for the flight CLH41, it is possible to select K1, K2 or K3 point) H.BL.ORD.09 Open Menu D2 - ITWP HMI Solution Specifications - Page 124 Draft

134 Used by Cancel Menu Close Menu Select Menu Item Input HoldAt Evolution Updated (Dec 2008) Stop bar Menu General Description Invocation Display Position Illustration HMI Object STOP BAR MENU To activate / deactivate the stop bar. The stop bar menu is used to change the status of the stop bar. 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). When invoked, the stop bar menu is displayed near the selected stop bar. 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 Initiates Open Menu Close Menu Used by Particularities Evolution Updated (Dec 2008) Select Menu Item Display Stop Bar Status Manually Set Up Stop Bar Status 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. D2 - ITWP HMI Solution Specifications - Page 125 Draft

135 Runway Status Menu General Description Invocation Display Position Illustration HMI Object RUNWAY STATUS MENU To input open / closed runway status by GND or RWY controller. The runway status menu is used to change the status of each runway threshold. 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. When invoked, the runway status menu is displayed near the selected runway. Runway status set up Requirement Ref. F.BL.APT.01 H.BL.APT.01 Initiates Open Menu Close Menu Associated HMI objects MAP SELECTION TOOL AIRPORT 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) D2 - ITWP HMI Solution Specifications - Page 126 Draft

136 Taxiway Status Menu General Description Invocation Display Position Illustration HMI Object TAXIWAY STATUS MENU To input open / closed taxiway status by GND or RWY controller. The taxiway status menu is used to change the status of a taxiway. 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. When invoked, the taxiway status menu is displayed near the selected taxiway. Taxiway status set up Taxiway closed Taxiway open (i.g. K4E) Requirement Ref. F.BL.APT.01 H.BL.APT.01 Initiates Open Menu Close Menu Set Up Runway/ Taxiway Status Associated HMI objects MAP SELECTION TOOL AIRPORT 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) D2 - ITWP HMI Solution Specifications - Page 127 Draft

137 SID Menu General Description Invocation HMI Object SID MENU To allow the controller to access to SID options for a departure flight. The SID menu is used to modify a SID for a departure flight. 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 Illustration When invoked, the holding point menu pops-up so that the possible holding point options are displayed under the cursor. Requirement Ref. F.BL.UPD.02 Initiates Open Menu Used by Change SID Evolution Updated (Septembre 2007) - the SID menu is displayed with the RWY menu - the SID default value is highlighted D2 - ITWP HMI Solution Specifications - Page 128 Draft

138 Operator Role Menu General Description Invocation HMI Object OPERATOR ROLE MENU To change the Operator role to which a transfer is due to be performed. 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 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 Illustration When invoked, the operator role menu pops-up so that the possible operator roles are displayed under the cursor. example of e-strip (single click on GND should open the operator role menu (not implemented)) Requirement H.FD.TRSF.03 Ref. Used by Select Operator Role for Transfer Associated HMI objects Particularitie - s Evolution not implemented (Dec 2008) D2 - ITWP HMI Solution Specifications - Page 129 Draft

139 Transfer Menu (callsign manu only transfer available) General Description Invocation HMI Object TRANSFER MENU To allow the controller to access the Operator role to transfer a vehicle / towed aircraft. The Transfer menu is used to transfer a vehicle or a towed aircraft. 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 Illustration When invoked, the transfer menu opens so that the possible Operator role may be selected (currently only GND and RWY controllers). 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 Initiates Open Menu Used by Transfer Vehicle/Towed aircraft Evolution Updated (November 2007) D2 - ITWP HMI Solution Specifications - Page 130 Draft

140 Vehicle e-strip HMI Object VEHICLE E-STRIP 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 Display Position System generated 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. D2 - ITWP HMI Solution Specifications - Page 131 Draft

141 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 Used by - Associated HMI objects RWY SECTION RWY HOLDING POINT 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 D2 - ITWP HMI Solution Specifications - Page 132 Draft

142 Towed aircraft e-strip HMI Object TOWED AIRCRAFT E-STRIP 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, ): 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. Invocation Display Position M (interactive field): gives the possibility to the controller to mark (M) / unmark (UM) vehicle System generated 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. D2 - ITWP HMI Solution Specifications - Page 133 Draft

143 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 Used by - Associated HMI objects RWY SECTION RWY HOLDING POINT 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 Towed aircraft strip format: Time 1 C/S TYPE/ STAND CLEARANCE RWY M D2 - ITWP HMI Solution Specifications - Page 134 Draft

144 Arrival e-strip HMI Object ARR E-STRIP 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, ): H (Heavy): all aircraft types of kg or more; M (Medium): aircraft types less than kg but more than kg; L (Light): aircraft types of 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. D2 - ITWP HMI Solution Specifications - Page 135 Draft

145 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. Invocation Display Position Illustration System generated Displayed in bays and sections according to the progress of the flight and controller clearances. 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 Used by - Associated HMI objects Evolution Data link identifier is displayed. Updated (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 136 Draft

146 Extended arrival strip format: Time1 C/S (DL) TYPE/VW STAND(-HOLD) I or V CLEARANCE 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 CLEARANCE RWY SEQ N M D2 - ITWP HMI Solution Specifications - Page 137 Draft

147 Departure e-strip General Description HMI Object DEP E-STRIP To replace the use of paper strips and support the TWR controller in reducing mental workload and in saving time for operations. 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, ): H (Heavy): all aircraft types of kg or more; M (Medium): aircraft types less than kg but more than kg; L (Light): aircraft types of 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. D2 - ITWP HMI Solution Specifications - Page 138 Draft

148 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). 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). 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. Invocation Display Position System generated e-strips are displayed in appopriate bays and sections according to rules (e.g. time rules) or clearances / transfers input by the controller. D2 - ITWP HMI Solution Specifications - Page 139 Draft

149 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) Particularities: example of minimum dep. e-strip (assumed state / assumed out) 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 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 D2 - ITWP HMI Solution Specifications - Page 140 Draft

150 CLD e-strip General Description HMI Object CLD E-STRIP To replace the use of paper strips and support the CLD controller in reducing mental workload and in saving time for operations. 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, ): H (Heavy): all aircraft types of kg or more; M (Medium): aircraft types less than kg but more than kg; L (Light): aircraft types of 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). RWY field (interactive field): runway identification, e.g. 26, 08, 19R, 01L etc. The RWY modification is obtained via the RWY Menu. M (interactive field): gives the possibility to the CLD controller to mark/unmark a specific flight. D2 - ITWP HMI Solution Specifications - Page 141 Draft

151 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. Invocation Display Position Illustration System generated e-strips are displayed in appopriate bays and sections according to rules (e.g. time rules) or clearances / transfers input by the controller. 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) Req. ref H.BL.SIL.01 H.BL.SIL.02 H.BL.SIL.03 Used by - Associated HMI objects Evolution Updated (July 2007) Extended CLD strip format: exemple of CLD extended e-strip 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 D2 - ITWP HMI Solution Specifications - Page 142 Draft

152 1. e-strip clearance field for a GND controller Main state Not concerned e-strip clearance field for a GND controller - Departure Flight Pending Pending Assumed Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value No Value Assumed out CALLSIGN Menu option START-UP * ASSUME When Push-back clearance has been given TAXI * PUSH BACK * When Taxi clearance has been given TRANSFER * HOLD STOP AT * * When the taxi clearance has been given Updated Dec 2008: Start up is available on the GND position only if CLD is not available. D2 - ITWP HMI Solution Specifications - Page 143 Draft

153 e-strip clearance field for a GND controller - Arrival Flight Main state Not concerned Pending Pending Assumed Sub-State No Value No Value Pending-in No Value Clearance field option 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. D2 - ITWP HMI Solution Specifications - Page 144 Draft

154 2. e-strip clearance field for a RWY controller Main state Not concerned Pending Pending e-strip clearance field for a RWY controller - Departure Flight Assumed Assumed Assumed Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value No Value No Value No Value Assumed out Clearance field option ASSUME * When Hold instruction has been given HOLD STOP AT LINE-UP * * CONDITIONAL LINE-UP TAKE-OFF * When Conditional line-up or line-up clearance has been given TRANSFER * ABORT TAKE- OFF When Take-Off clearance has been given VACATE * When Abort Takeoff clearance has been given Updated Dec D2 - ITWP HMI Solution Specifications - Page 145 Draft

155 Main state Not concerned Pending Pending e-strip clearance field for a RWY controller - Arrival Flight Assumed Assumed Assumed Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value No Value No Value No Value Assumed out Clearance field option Or when Final has been input by the controller When Continue Approach clearance has been given When Cleared to land clearance has been given When Go-Around clearance has been given When Vacate clearance has been given 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) D2 - ITWP HMI Solution Specifications - Page 146 Draft

156 3- e-strip clearance field for a CLD controller e-strip clearance field for a CLD controller Main state Not concerned Pending Pending Assumed Assumed Assumed Sub-State No Value No Value Pending-in No Value No Value Assumed out CALLSIGNMenu option ASSUME CLR/DCLR (*) When CLR has been given START When the start-up clearance has been given TRANSFER (*): DCLR (En-route clearance via data link) is not implemented (July 2007) D2 - ITWP HMI Solution Specifications - Page 147 Draft

157 5 Description of Procedures 5.1 WIMP GRAPHICAL USER INTERFACE MANAGEMENT Windows Management The following table provides a summary of procedures associated to windows which are described in the following sections. Procedures Open window Close window Move window Come on top window Iconify window De-iconify window Page scroll window Re-scale window Re-size window Slider scroll window Step scroll window To display a window. To close a displayed window. To move a window To transfer a window from its current position to the top of its stack. To modify the displayed aspect of a window from a full display to a small pictorial representation (icon). To restore the original full display of the iconified window. To scroll a window in pages. 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 resized window, i.e. the image gets bigger or smaller as the window is rescaled. 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. To manually scroll a window. To scroll a window in incremental steps Open window Procedure D2 - ITWP HMI Solution Specifications - Page 148 Draft

158 Actors Trigger Open window To display a window. RWY Controller GND Controller 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 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 Evolution - WINDOW LOGON WINDOW MET INFORMATION WINDOW NAVAIDS INFORMATION WINDOW EXTENDED RADAR LABEL WINDOW SYSTEM MESSAGE WINDOW PREFERENCES SETTING WINDOW D2 - ITWP HMI Solution Specifications - Page 149 Draft

159 Close window Procedure Close window 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 1a or 1b. The window is closed. event OR 1b. Single Click AB on the Close button of the window Requirement Ref. H.BL.HMI.04 Previous Open window Associated HMI Objects Initiated by Evolution - 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 D2 - ITWP HMI Solution Specifications - Page 150 Draft

160 Move window Procedure Move window 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 Previous Associated HMI Objects Initiated by Open window 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 Evolution - D2 - ITWP HMI Solution Specifications - Page 151 Draft

161 Come on top window Procedure Come on top window 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. Previous Associated HMI Objects Initiated by Particularities H.BL.HMI.04 Open window 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 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 - D2 - ITWP HMI Solution Specifications - Page 152 Draft

162 Iconify window Procedure Iconify window 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 lefthand 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 Following De-iconify window Previous Associated HMI Objects Initiated by Open window 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 De-iconify window Procedure De-iconify window 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 Previous Associated HMI Objects Initiated by Evolution - Iconify window 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 D2 - ITWP HMI Solution Specifications - Page 153 Draft

163 Re-size window Procedure 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. 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 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 - D2 - ITWP HMI Solution Specifications - Page 154 Draft

164 Re-scale window Procedure 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. 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 Rescale 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 resized window. Requirement Ref. H.BL.HMI.05 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 - D2 - ITWP HMI Solution Specifications - Page 155 Draft

165 Page scroll window Procedure Page scroll window 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 3. Page Scroll Left body between the slider bar and left arrow button 4. Single Click AB on the scroll bar 4. Page Scroll Right body between the slider bar and right arrow button Requirement Ref. H.BL.HMI.05 Previous Open window Associated HMI Objects Initiated by WINDOW Evolution - D2 - ITWP HMI Solution Specifications - Page 156 Draft

166 Slider scroll window Procedure Slider scroll window 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 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 - D2 - ITWP HMI Solution Specifications - Page 157 Draft

167 Step scroll window Procedure Step scroll window 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 1.image scroll down of an incremental step button 2. Single Click AB on the down arrow 2.image scroll up of an incremental step button 3. Single Click AB on the left arrow 3.image scroll right of an incremental step button 4. Single Click AB on the right arrow 4.image scroll left of an incremental step button 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 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 - D2 - ITWP HMI Solution Specifications - Page 158 Draft

168 5.1.2 Menus Management The following table provides a summary of procedures associated to menus which are described in the following sections. Procedures Open Menu Scroll Menu Select Menu Item Close Menu Cancel Menu To display a menu To scroll a menu To select an option item in the menu To close (remove) a displayed menu dialogue after having made a selection To cancel an initiated menu dialogue without having made a selection Open menu Procedure Open Menu 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 Requirement Ref. H.BL.HMI.18 Previous Select Traffic Following Cancel Menu Close Menu Scroll Menu Select Menu Item Associated HMI Objects Uses Evolution Updated (October 2007) 1. The menu is displayed at its default position. MENU RUNWAY MENU CALLSIGN MENU HOLDING POINT MENU OPERATOR ROLE MENU PARKING STAND MENU STOP BAR MENU RUNWAY STATUS MENU D2 - ITWP HMI Solution Specifications - Page 159 Draft

169 Scroll menu Procedure Scroll Menu 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 Previous Open Menu Following Cancel Menu Select Menu Item Associated HMI Objects Initiated by MENU PARKING STAND MENU Evolution Select menu item Procedure Select Menu Item 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 Previous Open Menu Scroll Menu Following Close Menu Associated HMI Objects Initiated by Evolution - MENU RUNWAY MENU CALLSIGN MENU HOLDING POINT MENU OPERATOR ROLE MENU PARKING STAND MENU RUNWAY STATUS MENU ROUTE ACCEPT MENU RUNWAY MENU D2 - ITWP HMI Solution Specifications - Page 160 Draft

170 Close menu Procedure Close Menu 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 Previous Open Menu Scroll Menu Associated HMI Objects Initiated by Evolution Updated (Octobre 2007) MENU RUNWAY MENU CALLSIGN MENU HOLDING POINT MENU OPERATOR ROLE MENU PARKING STAND MENU STOP BAR MENU RUNWAY STATUS MENU Cancel menu Procedure Cancel Menu 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 1a or 1b. The dialogue is discarded. The menu is removed 1b - Single Click AB or IB outside the menu region Requirement Ref. H.BL.HMI.24 Previous Associated HMI Objects Initiated by Evolution - Open Menu Scroll Menu MENU RUNWAY MENU CALLSIGN MENU HOLDING POINT MENU OPERATOR ROLE MENU PARKING STAND MENU D2 - ITWP HMI Solution Specifications - Page 161 Draft

171 5.2 ACCESS CWP The following table provides a summary of procedures associated to windows which are described in the following sections. Procedures Log On CWP Log Out CWP To access the CWP functions as an identified user. To exit the CWP functions Access / exit the CWP functions Log on CWP Procedure Log On CWP 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 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 Following Access Tool Associated HMI Objects Initiated by - Uses LOGON WINDOW Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 162 Draft

172 Log out CWP Procedure Log Out CWP 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' 1. The 'LOG' button is shown as toggle button depressed ; the Log On Window is displayed ; The access to the CWP functions is not allowed any more. Requirement Ref. F.BL.LOG.03 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) D2 - ITWP HMI Solution Specifications - Page 163 Draft

173 5.3 MANAGE THE DISPLAY LAYOUT Set-Up the Display and Access Screen Settings Save configuration set-up Procedure Save Configuration Set-Up 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 1. The radio button is redrawn as radio button in region 1. 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 Previous Access Tool Following Access Configuration Set-Up Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 164 Draft

174 Access configuration set-up Procedure Access Configuration Set-Up 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 Previous Save Configuration Set-Up Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution not implemented (may 2007) D2 - ITWP HMI Solution Specifications - Page 165 Draft

175 Set-up input devices Procedure Set Mouse Hand 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' 1. The button is redrawn as depressed. radio button in region 2 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 Previous Access Tool Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Evolution Not implemented (May2007) Set-Up Screen Parameters Select day/night/sun settings Procedure Select day/night/sun settings 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 Previous Access Tool Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 166 Draft

176 Fine tune brightness settings Procedure Fine Tune Brightness Settings 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 Requirement Ref. F.BL.SET.08 Previous Access Tool Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Evolution not implemented (May 2007) Fine tune contrast settings Procedure Fine Tune Contrast Settings 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 Requirement Ref. F.BL.SET.08 Previous Access Tool Associated HMI Objects Initiated by PREFERENCES SETTING WINDOW Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 167 Draft

177 5.3.3 Manage Toolbar Functions Access Tool Procedure Access Tool 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 Following Isolate Tool Previous Associated HMI Objects Initiated by CSD TOOLBOX WINDOW GENERAL TOOLBOX WINDOW Uses Evolution - 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 D2 - ITWP HMI Solution Specifications - Page 168 Draft

178 Isolate Tool Procedure Isolate Tool 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 Previous Access Tool Following Replace Tool Associated HMI Objects Initiated by 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 Uses CSD TOOLBOX WINDOW GENERAL TOOLBOX WINDOW Evolution - D2 - ITWP HMI Solution Specifications - Page 169 Draft

179 Replace Tool Procedure Replace Tool 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 1a or 1b - The tool is replaced back to its button of the tool parent Toolbox or is closed. The OR 1b - Single Click AB on the toggle toggle button representing the tool in the Toolbox is shown as undepressed. button representing the tool in the Toolbox Requirement Ref. H.BL.TOOL.02 Following Access Tool Previous Associated HMI Objects Initiated by Uses Evolution - Isolate Tool 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 CSD TOOLBOX WINDOW GENERAL TOOLBOX WINDOW D2 - ITWP HMI Solution Specifications - Page 170 Draft

180 5.4 ACCESS AIR, SURFACE AND TIME INFORMATION Zoom, offset and modify the geographical orientation of the display view Perform Zoom Procedure Perform Zoom.1 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 Previous Access Tool Following Store Zoom Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution - Procedure Perform Zoom.2 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 Following Store Zoom Associated HMI Objects Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution - D2 - ITWP HMI Solution Specifications - Page 171 Draft

181 Store zoom Procedure Store Zoom 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 Previous Perform Zoom.1 Perform Zoom.2 Following Delete Zoom Retrieve Zoom Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 172 Draft

182 Retrieve zoom Procedure Retrieve Zoom 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 Previous Store Zoom Following Delete Zoom Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution not implemented (May 2007) Zoom back Procedure Zoom Back 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 Previous Perform Zoom.1 Perform Zoom.2 Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 173 Draft

183 Delete zoom Actors Trigger Procedure Delete Zoom To delete a stored zoom setting. RWY Controller GND Controller 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 Previous Retrieve Zoom Store Zoom Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution not implemented (May 2007) Offset centre Procedure Offset Centre.1 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 1. The button is shown as depressed. The button cursor changes to the recentring 2. Single Click AB on any point of the radar window Requirement Ref. F.BL.ZOOM.07 Previous Access Tool Associated HMI Objects Initiated by ZOOM TOOL Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution - cursor form. 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. D2 - ITWP HMI Solution Specifications - Page 174 Draft

184 Procedure Offset Centre.2 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 HMI Objects Uses COMPOSITE SITUATION DISPLAY WINDOW Evolution - D2 - ITWP HMI Solution Specifications - Page 175 Draft

185 Zoom in part Procedure Zoom in part 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 1. A rectangular wire-frame outline in COMPOSITE SITUATION DISPLAY Warning colour is displayed; fixed at WINDOW 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 Following Zoom Back Previous - Associated HMI Objects Initiated by COMPOSITE SITUATION DISPLAY WINDOW Uses ZOOM TOOL Evolution - D2 - ITWP HMI Solution Specifications - Page 176 Draft

186 Modify geographical orientation of situation display Procedure Modify Geographical Orientation 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 1. The geographical orientation of situation COMPOSITE SITUATION DISPLAY display is modified (turns on the left or on WINDOW the right, depending on dragging SB). Requirement Ref. Previous Access Tool Associated HMI Objects Initiated by Uses Evolution Updated (May 2007) 2. Release SB. 2. The map is fully redrawn with the selected modification of geographical orientation. F.BL.MAP.07 MAP SELECTION TOOL COMPOSITE SITUATION DISPLAY WINDOW Display Airport Information Display composite video map Procedure Display Composite Video Map 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 Requirement Ref. F.BL.MAP.01 Previous Access Tool Associated HMI Objects Initiated by MAP SELECTION TOOL Uses Evolution - D2 - ITWP HMI Solution Specifications - Page 177 Draft

187 Display / remove display parking names Procedure Display / Remove Display Parking Names 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. Requirement Ref. Following - Previous - Associated HMI Objects Initiated by Evolution - 2. Single click AB on the parking stand symbol (filled triangle) on the CSD window F.BL.MAP.03 PARKING STAND SYMBOL 2. The name of the parking stand is removed, the parking stand symbol is displayed as an unfilled triangle Display parking names (Quick Look) Procedure Display Parking Names (Quick Look) 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 2. Move the cursor outside of the parking stand symbol. Requirement Ref. F.BL.MAP.03 Following - Previous - Associated HMI Objects Initiated by PARKING STAND SYMBOL Evolution - the parking stand is displayed. 1. The parking stand symbol is returns to an unfilled triangle (blank) and the name of the parking stand is removed D2 - ITWP HMI Solution Specifications - Page 178 Draft

188 Set Up Runway / Taxiway Status (open / close) Procedure Set Up Runway/ Taxiway Status 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 1a. The runway status menu is displayed under the cursor with current runway status setting (for each threshold). 2. Single IB on the name of taxiway 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. Requirement Ref. Following Previous Associated HMI Objects Initiated by F.BL.APT.01 Close Menu Open Menu 2b. The selected TWY status is highlighted and replaces the previous one. The taxiway sector is displayed in different coulour (orange/red). 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) D2 - ITWP HMI Solution Specifications - Page 179 Draft

189 5.4.3 Display and track range and bearing between two 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 Enable Range and Bearing function Procedure Obtain range and bearing information 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 1. The cursor changes to the sighting cursor form. object. 2. Move the cursor 2. A continuous readout of distance and bearing from the fixed point is displayed 3. Single Click AB on the CSD Window, outside of a selectable object immediately below the sighting cursor. 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 Following Create Range and Bearing Track Cancel Range and Bearing Track Previous Express time to go to airspace point Associated HMI Objects Uses RANGE and BEARING TRACKER LINK Initiated by COMPOSITE SITUATION DISPLAY WINDOW Evolution Not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 180 Draft

190 Cancel Range and Bearing function Procedure Cancel Range and Bearing function 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 Previous Obtain range and bearing information Associated HMI Objects Uses RANGE and BEARING TRACKER LINK Initiated by COMPOSITE SITUATION DISPLAY WINDOW Evolution Not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 181 Draft

191 Create Range and Bearing Track Procedure Create Range and Bearing Track 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 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 Evolution Not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 182 Draft

192 Cancel Range and Bearing Track Procedure Cancel Range and Bearing Track 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 Previous Create Range and Bearing Track Associated HMI Objects Initiated by RANGE and BEARING TRACKER LINK Evolution Not implemented (May 2007) Express Time to Go to airspace point Procedure Express time to go to airspace point 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 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 Evolution Not implemented (Dec. 2008) D2 - ITWP HMI Solution Specifications - Page 183 Draft

193 5.4.4 Access time information Display Time Procedure Display Universal Time 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 HMI Objects Uses CSD TOOLBOX WINDOW CLOCK WINDOW Evolution Updated (May 2007) D2 - ITWP HMI Solution Specifications - Page 184 Draft

194 5.5 MANAGE THE DISPLAY FEATURES OF TRAFFIC REPRESENTATION Manage the Radar Labels Configure Radar Labels Content Procedure Configure radar labels content 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 TOOLis available Dialogue Action Result 1a. Single Click AB on a text If the option is not selected, the state acquisition area or on the of the switch buttons in Min column is set associated switch button in the Min column 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. Requirement Ref. Previous Associated HMI Objects Initiated by Uses Or 1b. Single Click AB on a switch button in the Sel column F.BL.LBL.01 F.BL.LBL.03 F.BL.LBL.02 Access Tool Evolution Updated (Nov 2007) 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 deselected 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. LABEL CONFIGURATION TOOL RADAR LABEL VEHICLE RADAR LABEL TOWED AIRCRAFT RADAR LABEL D2 - ITWP HMI Solution Specifications - Page 185 Draft

195 5.5.2 Manage the Electronic Flight Strips (EFS, e-strip) Configure the EFS content Procedure Configure EFS content 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 If the option is not selected, the state acquisition area or on the of the switch buttons is set to ON. associated switch button. 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 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 Evolution Updated (November 2007) D2 - ITWP HMI Solution Specifications - Page 186 Draft

196 Move an EFS Procedure Move an EFS 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 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 Evolution Updated (Dec. 2008) Manage air tracks and labels Display speed vectors Procedure Display Speed Vectors 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 1. The radio button is redrawn as corresponding radio button of the depressed; speed vector function Requirement Ref. F.BL.VECT.01 F.BL.VECT.02 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) D2 - ITWP HMI Solution Specifications - Page 187 Draft

197 Set speed vectors value Procedure Set Speed Vectors Value 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 1. The radio button is redrawn as of the speed vector function 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 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) Set track history value Procedure Set Track History Value 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 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) D2 - ITWP HMI Solution Specifications - Page 188 Draft

198 5.5.4 Manage label position Deconflict labels automatically Procedure Deconflict Labels Automatically 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 1 - The state of the toggle button is set to toggle button ON. The previously stored label position values in the automatic mode are restored. The Radar Label antioverlap 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 Previous Deconflict Labels Manually Following Resume Label Position Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 189 Draft

199 Deconflict labels manually Procedure Deconflict Labels Manually 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 deconfliction 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 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 Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 190 Draft

200 Set label leader direction Procedure Set Leader Direction 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 1. The button is redrawn as depressed; in the manual mode, the selected subset within the currently selected of radar labels is redrawn in the frame of reference 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 Previous Set Fixed Reference Set Track as a Reference Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL RADAR TRACK Evolution Updated (May 2007) Set leader length Procedure Set Leader Length 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 1. The button is redrawn as depressed; any other depressed button in that within the currently selected region is released. The selected frame of reference 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 Previous Set Fixed Reference Set Track as a Reference Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL RADAR TRACK Evolution - D2 - ITWP HMI Solution Specifications - Page 191 Draft

201 Set fixed reference Procedure Set Fixed Reference 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 Following Set Leader Length Set Leader Direction Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL Evolution not implemented (May 2007) Set track as a reference Procedure Set Track as a Reference 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 Following Set Leader Length Set Leader Direction Associated HMI Objects Initiated by LABEL OVERLAP MANAGEMENT TOOL Uses RADAR LABEL Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 192 Draft

202 Move radar babel Procedure Move Radar Label 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 Previous Select Traffic Following Resume Label Position Associated HMI Objects Initiated by RADAR LABEL Uses RADAR TRACK Evolution - D2 - ITWP HMI Solution Specifications - Page 193 Draft

203 Resume label position Procedure Resume Label Position 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 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. Previous F.BL.POS.08 Deconflict Labels Automatically Deconflict Labels Manually Move Radar Label Associated HMI Objects Initiated by Uses Evolution not implemented (May 2007) LABEL OVERLAP MANAGEMENT TOOL RADAR LABEL RADAR TRACK D2 - ITWP HMI Solution Specifications - Page 194 Draft

204 5.5.5 Draw attention to a particular aircraft or vehicle Input intra-cwp traffic marking Procedure Input intra-cwp traffic marking 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 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 Evolution Updated (November 2007) D2 - ITWP HMI Solution Specifications - Page 195 Draft

205 Share marking with next CWP Procedure Share marking with next CWP 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 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 Evolution not implemented (May 2007) Share marking with all CWPs Procedure Share marking with all CWPs 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 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 Evolution not implemented (May 2007) D2 - ITWP HMI Solution Specifications - Page 196 Draft

206 Unmark traffic Procedure Unmark Traffic 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 1a, 1b, and 1c. The marking is removed 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. Requirement Ref. F.BL.WAR.03 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 Evolution Updated (November 2007) D2 - ITWP HMI Solution Specifications - Page 197 Draft

207 5.6 ACCESS DATA CONCERNING THE TRAFFIC SITUATION Access aircraft / vehicle representation Display traffic representation Procedure Display Traffic Representation 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 Requirement Ref. Following Associated HMI Objects Uses Evolution - 2. The traffic (aircraft or vehicle) position in the horizontal plane is modified 3. The aircraft position in the vertical plane is modified (altitude) radar label in the Minimum format 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 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 4. The traffic representation is updated. update of traffic data F.BL.TRAF.01 F.BL.TRAF.02 F.BL.TRAF.03 Select Traffic Remove Traffic Representation RADAR TRACK RADAR LABEL EXTENDED RADAR LABEL D2 - ITWP HMI Solution Specifications - Page 198 Draft

208 Remove traffic representation Procedure Remove Traffic Representation 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 Previous Display Traffic Representation Associated HMI Objects Uses RADAR TRACK RADAR LABEL EXTENDED RADAR LABEL Evolution - D2 - ITWP HMI Solution Specifications - Page 199 Draft

209 Select traffic Procedure Select Traffic 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 Requirement Ref. Previous Following Associated HMI Objects Initiated by Particularities 2. Move the cursor pointer on one of the interactive fields of the selected object F.BL.LBL.01 H.BL.TRAF.04 Display Traffic Representation 2. The selected field is highlighted RADAR TRACK RADAR LABEL EXTENDED RADAR LABEL RUNWAY CONFLICT ALERT MESSAGE ARR E-STRIP DEP E-STRIP 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 - D2 - ITWP HMI Solution Specifications - Page 200 Draft

210 Deselect Traffic Procedure Deselect Traffic 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 2. The selected field is unhighlighted interactive field of the object Requirement Ref. F.BL.SEL.01 Previous Select Traffic Following - Associated HMI Objects Initiated by RADAR LABEL RADAR TRACK EXTENDED RADAR LABEL DEP E- STRIPARR E-STRIP Evolution - D2 - ITWP HMI Solution Specifications - Page 201 Draft

211 Display extended label Procedure Display Extended Label 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 1. field of an aircraft or vehicle If the Extended radar label window is wherever presented (e.g. radar label, electronic strip etc.) 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 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 Evolution - D2 - ITWP HMI Solution Specifications - Page 202 Draft

212 Display extended label (Quick Look) Procedure Display Extended Label (Quick Look) 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 1. The Extended Radar Label data is field of an aircraft or vehicle displayed at the location of the wherever presented (e.g. radar label, callsign, so that the callsign is electronic flight strip, etc. ) 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 Previous Select Traffic Following - Associated HMI Objects Initiated by RADAR LABEL DEP E-STRIP ARR E-STRIP Uses Particularities Evolution - EXTENDED RADAR LABEL 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. D2 - ITWP HMI Solution Specifications - Page 203 Draft

213 Display additional CSD sub-view Procedure Display additional CSD sub-view 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 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 Evolution Updated (May 2007) D2 - ITWP HMI Solution Specifications - Page 204 Draft

214 Display EFS section Procedure Display EFS section 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. D2 - ITWP HMI Solution Specifications - Page 205 Draft

215 Pre-condition - Dialogue Action Result 1. The system detects that the preconditions above are fulfilled. 1. The corresponding section is displayed open on the CSD window. Requirement Ref. F.BL.SIL.01 F.BL.SIL.02 Previous - Following - Associated HMI Objects Uses Evolution - 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 Hide EFS Bay Procedure Hide EFS Bay 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 1. The corresponding bay is no more displayed on the CSD window. GND Pushback section (GND role) or CLD active section (CLD role) Requirement Ref. F.BL.SIL.01 F.BL.SIL.02 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) D2 - ITWP HMI Solution Specifications - Page 206 Draft

216 5.6.2 Update Traffic Situation Data Input En Route Clearance Procedure Input CLR 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 Following Input Start-Up Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP RADAR LABEL EXTENDED RADAR LABEL Evolution Updated (June 07) D2 - ITWP HMI Solution Specifications - Page 207 Draft

217 Input En Route Clearance via data link Procedure Input DCLR 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 option in the callsign menu, or 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 Following Input Start-Up Previous Input Assume Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP RADAR LABEL EXTENDED RADAR LABEL Evolution Updated (June 07) D2 - ITWP HMI Solution Specifications - Page 208 Draft

218 Input Start Up Note: This procedure is applicable if GND controller gives start up clearance. Procedure Input Start-Up 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 option in the callsign menu, or 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 Following Input Pushback Input Hold Input Taxi Previous - Associated HMI Objects Initiated by CALLSIGN MENU Uses DEP E-STRIP RADAR LABEL EXTENDED RADAR LABEL Evolution - D2 - ITWP HMI Solution Specifications - Page 209 Draft

219 Input Pushback Actors Trigger Pre-condition Procedure Input Pushback To provide the controller with the possibility to input a push back order GND controller Controller action 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 option in the callsign menu, or 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. Requirement Ref. Following Previous Associated HMI Objects Initiated by Uses Particularities Evolution F.BL.ORD.08 Input Taxi Input Hold add stop at Input Assume - Available clearances are Taxi, Stop at and Hold. CALLSIGN MENU DEP E-STRIP RADAR LABEL EXTENDED RADAR LABEL Note: the Start up clearance is not available on the current GND position. Updated (Dec.2008) D2 - ITWP HMI Solution Specifications - Page 210 Draft

220 Input Taxi Actors Trigger Pre-condition Procedure Input Taxi To provide the controller with the possibility to input a taxi order GND controller Controller action 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 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 Evolution - D2 - ITWP HMI Solution Specifications - Page 211 Draft

221 Input Line up Procedure Input Line Up 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 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 Takeoff. - 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 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 Evolution - D2 - ITWP HMI Solution Specifications - Page 212 Draft

222 Input Conditional line up Procedure Input Conditional Line Up 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 F.BL.ORD.11 Ref. 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 Evolution - D2 - ITWP HMI Solution Specifications - Page 213 Draft