eurocontrol experimental centre · 5.6 efis control panel 15¶ 5.7 mode control panel (mcp) 16¶...

EUROCONTROL EXPERIMENTAL CENTRE

CDTI Evaluation System

Software Specification Document

Division Systèmes Techniques Date : 07/05/2004 Identification : CS-CISI/CDTI/DSL Version : 4.0 Name Date Signature Author(s)

T. BLOND

N. DURAND

L. HUYNH

Approval

P. HAFENEDER

P. REHBINDER

Customer K. ZEGHAL

Deleted: 27/01/00

Deleted: 3.1



CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page ii

Ce document est la propriété de CS-Cisi et ne peut être reproduit sans son autorisation écrite

Distribution List External Distribution

• Karim ZEGHAL Eurocontrol EC.

• Eric HOFFMAN Eurocontrol EC. Internal Distribution

• Pierre HAFENEDER CS-CISI Project Manager

• Thierry BLOND CS-CISI Project Director • Pierre REHBINDER CS-CISI Quality Manager

Document Change Form

Version/Revision Reference No Date Page Paragraph Change Description Author 1.0 01/02/99 Initial Draft T. Blond

N. Durand

L. Huynh 2.0 16/02/99 many Lot of precisions throughout

the document T. Blond N. Durand L. Huynh

2.1 09/03/99 many Modification made according to the Specification Revue held on 19/02/99

T. Blond N. Durand L. Huynh

2.2 26/03/99 many Final Specification Document for “Java Cockpit”

T. Blond N. Durand L. Huynh

3.0 19/01/00 many Addition of evolutions specifications (“Java Cockpit Upgrade”)

N. Durand L. Huynh

3.1 27/01/00 many Final Specification Document

N. Durand

L. Huynh 4.0 07/05/04 many Changes for ADS-B and

TIS-B Asterix message support

M. Vere, T. Cooper

Deleted: 3.1

Formatted: Indent: Left: 0.39",Hanging: 0.2", Numbered + Level: 1+ Numbering Style: Bullet + Start at:1 + Alignment: Left + Aligned at: 0.39" + Tab after: 0" + Indent at: 0.59"

Formatted: Indent: Left: 0.39",Hanging: 0.2", Numbered + Level: 1+ Numbering Style: Bullet + Start at:1 + Alignment: Left + Aligned at: 0.39" + Tab after: 0" + Indent at: 0.59"

Deleted: 3.1

Deleted: 27/01/00

Deleted: Final Specification Document

Deleted: N. Durand¶L. Huynh

Deleted: ssd WP2 v1.1.doc



CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page iii


Table of Content

1 SCOPE .................................................................................................................1 1.1 Identification...............................................................................................1 1.2 Document Description.................................................................................1 1.3 Terminology ...............................................................................................1 1.4 Requirement Traceability ............................................................................1

2 APPLICABLE AND RELATED DOCUMENTS ..............................................3 2.1 Applicable Documents ................................................................................3 2.2 Related Documents .....................................................................................3

3 DEFINITIONS AND ABBREVIATIONS..........................................................4 3.1 Definitions ..................................................................................................4 3.2 Abreviations................................................................................................5

4 GENERAL DESCRIPTION ...............................................................................6 4.1 Context .......................................................................................................6 4.2 Software Objectives ....................................................................................6 4.3 Architecture ................................................................................................7

5 FUNCTIONAL SPECIFICATION.....................................................................9 5.1 Simulation of Aircraft Flights......................................................................9

5.1.1 Initialisation files............................................................................9 5.1.2 ADS-B .........................................................................................11

5.2 Top Level Application ..............................................................................11 5.3 Cockpit Panel............................................................................................12 5.4 Primary Flight Display (PFD) ...................................................................12 5.5 Navigation Display (ND) ..........................................................................13 5.6 EFIS Control Panel ...................................................................................13 5.7 Mode Control Panel (MCP).......................................................................14 5.8 Control Display Unit (CDU) .....................................................................14 5.9 Air Situation Display.................................................................................15 5.10 Aircraft Model module..............................................................................15 5.11 Autopilot Logic module ............................................................................16 5.12 Aircraft Environment module....................................................................17

5.12.1 Navaids related data.....................................................................17 5.12.2 Aircraft related data .....................................................................18

5.13 Automatic guidance ..................................................................................19

6 MAN-MACHINE INTERFACE.......................................................................21

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page iv


6.1 Top Level Application ..............................................................................21 6.2 Cockpit Panel............................................................................................22 6.3 Primary Flight Display ..............................................................................24

6.3.1 PFD Flight Mode Annunciation (FMA)........................................24 6.3.2 PFD Airspeed Indications .............................................................25 6.3.3 PFD Reference Speeds .................................................................26 6.3.4 PFD Attitude Indications ..............................................................27 6.3.5 PFD Steering Indications [S] ........................................................28 6.3.6 PFD Radio Altitude Indications ....................................................28 6.3.7 PFD Instrument Landing System (ILS).........................................29 6.3.8 PFD Altitude Indications ..............................................................30 6.3.9 PFD Landing Altitude/Minimum Indications ................................31 6.3.10 PFD Barometric Indications [S] ...................................................32 6.3.11 PFD Vertical Speed Indications ...................................................33 6.3.12 PFD Heading/Track Indications ...................................................33

6.4 Navigation Display (ND) ..........................................................................35 6.4.1 Data common to Expanded and Centered Map modes...................37 6.4.2 Data Specific to Expanded Map mode ..........................................40 6.4.3 Data Specific to Centered Map mode............................................40

6.5 CDTI Indications ......................................................................................41 6.6 Enhanced CDTI indications.......................................................................42

6.6.1 Lateral Separation Assurance........................................................44 6.6.2 Vertical Separation Assurance ......................................................47 6.6.3 Lateral Passing .............................................................................49 6.6.4 Longitudinal Station Keeping .......................................................50

6.7 EFIS Control Panel ...................................................................................51 6.8 Mode Control Panel (MCP).......................................................................54

6.8.1 Autopilot flight director system controls .......................................54 6.8.2 Autopilot flight director IAS/Mach controls..................................54 6.8.3 Autopilot flight director roll and pitch controls .............................55 6.8.4 Autopilot flight director heading/track controls.............................55 6.8.5 Autopilot flight director vertical speed and flight path angle controls55 6.8.6 Autopilot flight director altitude controls ......................................55

6.9 Control Display Unit .................................................................................56 6.9.1 ASAS Main page..........................................................................57 6.9.2 Target page...................................................................................58 6.9.3 Aircraft page ................................................................................62 6.9.4 Options page ................................................................................63 6.9.5 Increment page .............................................................................64 6.9.6 Reduced and Extended Options page ............................................65 6.9.7 Beacons page................................................................................66 6.9.8 Route legs page ............................................................................67

6.10 Air Situation Display.................................................................................68 6.10.1 Contents and representations........................................................68 6.10.2 Aircraft contextual menu .............................................................70

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page v


6.10.3 Configurations .............................................................................70 6.10.4 Tools ...........................................................................................71

7 SOFTWARE EXTERNAL INTERFACES......................................................72 7.1 Interface with Other Software ...................................................................72 7.2 Interface with Hardware ............................................................................72

8 SOFTWARE CONSTRAINTS .........................................................................73 8.1 Environment .............................................................................................73

8.1.1 Hardware Environment.................................................................73 8.1.2 Software Environment ..................................................................73 8.1.3 Development Libraries .................................................................73

8.2 Performances ............................................................................................73 8.3 Operational Constraints.............................................................................74 8.4 Quality Characteristics ..............................................................................74

9 PROJECT REQUIREMENTS .........................................................................75 9.1 Design Requirements ................................................................................75 9.2 Coding Requirements ................................................................................75 9.3 Test Requirements.....................................................................................75

9.3.1 Product Acceptance ......................................................................75 9.3.2 Documents Acceptance ................................................................75

ANNEX A. LIST OF REQUIREMENTS...............................................................1

ANNEX B. INTERFACING VARIABLES............................................................1

ANNEX C. AIRCRAFT MODEL INTERFACE ...................................................1

ANNEX D. CONFIGURATION PARAMETERS .................................................1

ANNEX E. COORDINATE CONVERSIONS.......................................................1

Deleted: 3.1

Deleted: 1 SCOPE 1¶1.1 Identification 1¶1.2 Document Description 1¶1.3 Terminology 1¶1.4 Requirement Traceability 2¶2 APPLICABLE AND RELATED DOCUMENTS 3¶2.1 Applicable Documents 3¶2.2 Related Documents 3¶3 DEFINITIONS AND ABBREVIATIONS 4¶3.1 Definitions 4¶3.2 Abreviations 5¶4 GENERAL DESCRIPTION 7¶4.1 Context 7¶4.2 Software Objectives 7¶4.3 Architecture 8¶5 FONCTIONAL SPECIFICATION 10¶5.1 Simulation of Aircraft Flights 10¶5.1.1 Initialisation files 10¶5.1.2 ADS-B 12¶5.2 Top Level Application 13¶5.3 Cockpit Panel 14¶5.4 Primary Flight Display (PFD) 14¶5.5 Navigation Display (ND) 14¶5.6 EFIS Control Panel 15¶5.7 Mode Control Panel (MCP) 16¶5.8 Control Display Unit (CDU) 16¶5.9 Air Situation Display 18¶5.10 Aircraft Model module 18¶5.11 Autopilot Logic module 18¶5.12 Aircraft Environment module 20¶5.12.1 Navaids related data 21¶5.12.2 Aircraft related data 21¶5.13 Trajectory Manager module 22¶6 MAN-MACHINE INTERFACE 24¶6.1 Top Level Application 24¶6.2 Cockpit Panel 25¶6.3 Primary Flight Display 27¶6.3.1 PFD Flight Mode Annunciation (FMA) 27¶6.3.2 PFD Airspeed Indications 28¶6.3.3 PFD Reference Speeds 30¶6.3.4 PFD Attitude Indications 31¶6.3.5 PFD Steering Indications [S] 32¶6.3.6 PFD Radio Altitude Indications 32¶6.3.7 PFD Instrument Landing System (ILS) 33¶6.3.8 PFD Altitude Indications 34¶6.3.9 PFD Landing Altitude/Minimum Indications 35¶6.3.10 PFD Barometric Indications [S] 36¶6.3.11 PFD Vertical Speed Indications 37¶6.3.12 PFD Heading/Track Indications 38¶6.4 Navigation Display (ND) 40¶6.4.1 Data common to Expanded and Centered Map modes 42¶6.4.2 Data Specific to Expanded Map mode 45¶6.4.3 Data Specific to Centered Map mode 46¶6.5 CDTI Indications 46¶6.6 Enhanced CDTI indications 48¶

Deleted: ssd WP2 v1.1.doc... [1]



CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page 1


1 SCOPE

1.1 Identification

Project Document Name : CDTI Evaluation System Name : Software Specification Document Reference : 148IRR Identification : CS-CISI/CDTI/DSL Customer : EUROCONTROL

Experimental Centre Version : Date :

4.0 – English 10/05/04

1.2 Document Description

This Software Specification Document is composed of the following chapters : Chapter 1 introduces this document, Chapter 2 lists the applicable and related documents, Chapter 3 gives some definitions, Chapter 4 describes the context and the objectives of the software, Chapter 5 describes the software functional specifications, Chapter 6 describes the Man-Machine Interface, Chapter 7 describes the software External Interfaces, Chapter 8 describes the software environmental constraints, Chapter 9 describes the specifications derived from the project.

1.3 Terminology

In order to ensure clarity and readability, the following notations are applied in this document : « shall » is used whenever a mandatory requirement is expressed.

« should » is used to express a recommendation.

« may » is used to express an option.

« will » is used to express a future expectation.

1.4 Requirement Traceability

The traceability of the requirements is an identified need (cf. req RD.1.2 :DOC(e) ). It is realised throughout the code and the following documents : This Software Specification Document The Software Design Document [DR2] The Software Tests Document [DR3]

Deleted: 3.1

Formatted: Indent: Left: 0",Hanging: 0.25", Bulleted + Level: 1+ Aligned at: 0" + Tab after: 0.25"+ Indent at: 0.25"

Formatted

Deleted:




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The requirement numbers referred to throughout this document as well as any additional information related to requirements traceability are described in the [DR4].

Deleted: 3.1

Deleted: 0




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



2 APPLICABLE AND RELATED DOCUMENTS

2.1 Applicable Documents

The rules, advises, recommendations or requirements contained in the following documents shall apply in the scope on this document.

[DA1] Manuel d'Assurance Qualité CS-Cisi CISI/SYSQUAL/MAQ/01

[DA2] Les Procédures du Système Qualité CISI/SYSQUAL/PSQ/01 à 23

[DA3] CDTI Evaluation System – User Requirement Document CDTI.ES.URD, V 1.4 – 19/10/98 EUROCONTROL Experimental Centre

[DA4] Système d’évaluation CDTI – Proposition CS-CISI Affaire 148IRR, V 1.0 – 02/11/98 CS-CISI

2.2 Related Documents

Related documents are those to which reference is made in this document. They are guiding material helping in the understanding or in the application of this document.

[DR1] Boeing 777 Operation Manual [DR2] Software Design Document

CS-CISI/CDTI/DC/01 [DR3] Software Tests Document

CS-CISI/CDTI/DTS/01 [DR4] Requirements Traceability Matrix

CS-CISI/CDTI/MTE/01 [DR5] eDEP GSDK Detailed Design Document

eDEP_GSDK_DDD.doc

Deleted: 3.1


Formatted: Bullets and Numbering



CS-CISI/CDTI/DSL

Version 4.0 10/05/04



3 DEFINITIONS AND ABBREVIATIONS The following definitions and abbreviations are used in the scope of this document.

3.1 Definitions

Software Quality The set of characteristics and properties of a software product that enables it to fulfil the requirements, either explicit or implicit.

Acceptance Contractual part of the project in which the software is subject to a predefined set of tests. The result of these tests directly influences the acceptance or rejection of the produced software by the customer.

Specification Part of the project whose goal is to describe what is to be realised (and not how it would be). This part leads to the production of the Specification Document.

Design Part of the project whose goal is to describe how the product will be realised. This part leads to the production of the Design Document.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



3.2 Abreviations

ADIRS : Air Data Inertial Reference System AGL : Above Ground Level ASL : Above Sea Level CDTI : Cockpit Display of Traffic Information CDTI++ : Enhanced Cockpit Display of Traffic Information CDU : Control Display Unit CRC : Test Document (Cahier de Recette) DAQ : Quality Assurance Document (Dossier d'Assurance Qualité) DC : Design Document (Dossier de Conception) DME : Distance Measuring Equipment DSL : Software Specification Document (Dossier de Spécification du Logiciel) DTS : Test Reports (Dossier de Tests) EFIS : Electronic Flight information System EFISCP : Electronic Flight information System Control Panel FMA : Flight Mode Annunciation HMI : Human-Machine Interface MAQ : Quality Assurance Manual (Manuel d'Assurance Qualité) MCP : Mode Control Panel MSL : Mean Sea Level MTE : Requirements Traceability Matrix (Matrice de Traçabilité des Exigenges) MUT : User’s Manual (Manuel d'Utilisation et d'Exploitation) ND : Navigation Display NDB : Non-Directional Beacon PAQ : Project Quality Assurance Plan (Plan d'Assurance Qualité) PDL : Project Software Development Plan (Plan de Développement Logiciel) PFD : Primary Flight Display PTV : Validation Tests Plan (Plan de Test de Validation) RA : Radio Altitude Rec : Recommendation Req : Requirement

VHF : Very High Frequency

VOR : VHF Omnidirectional Range

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



4 GENERAL DESCRIPTION

4.1 Context

The CDTI evaluation system is a software dedicated to Man-Machine Interface Prototyping. It is used to evaluate the ergonomy of new functionalities as well as new presentation of data, dedicated to civil pilots in the aircraft cockpit. It takes place in the frame of a study conducted to evaluate the delegation of responsibility, from the controller toward the pilot, concerning the assurance of separation between aircraft. This software will execute through the Internet environment. This environment enables many users (actual pilots) to make their own evaluation alone without the constraint to organize centralised evaluation sessions needing complex and expensive logistics. Parts of this software will then be re-used in the FREER2 environment, in order to continue the ergonomical study further on.

4.2 Software Objectives

The objectives of the CDTI evaluation software are as follows : • Present new features added to the existing CDTI (thus building an Enhanced CDTI also

noted CDTI++) along with their different options.Enable a first evaluation of the above new features, typically through Internet.

• Allow rapid prototyping of future enhancements. • Allow re-use of some modules in a different software environment, typically for the

connection of the cockpit displays to a flight simulator. To fullfil these objectives, and more particulary to conduct the evaluation, this software put the users in a simulated ‘in-flight’ situation. Different scenarios will be used to simulate different types of encounter between aircraft. A scenario simulates only one encounter. During this simulation, the software :

- Updates the position of the different involved aircraft. - Presents to the user (pilot) the information he will have on bord (subject of the

study). - Enables the pilot to interact with the aircraft (like in a real aircraft) and reacts

accordingly. - Automatically guides the aircraft if they are not manually piloted by the user.

Deleted: 3.1


Formatted: Indent: Left: 0",Hanging: 0.25", Numbered + Level:1 + Numbering Style: Bullet + Startat: 1 + Alignment: Left + Aligned at: 0" + Tab after: 0" + Indent at: 0.25"

Formatted: Bulleted + Level: 1 +Aligned at: 0.49" + Tab after: 0.74"+ Indent at: 0.74"

Formatted: Numbered + Level: 1 +Numbering Style: Bullet + Start at: 1+ Alignment: Left + Aligned at: 0" +Tab after: 0" + Indent at: 0.25"

Deleted: ¶Present new features added to the existing CDTI (thus building an Enhanced CDTI also noted CDTI++) along with their different options.




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



4.3 Architecture

The architecture of the application shall comply with the software structire defined in the following figure (req [RH.1.1]):

The user may launch the application from the eCockpit Launcher (providing a standalone demonstration facility) or directly from the standard GSDK launch mechanism. The eCockpit standalone demo launcher enables the user to select the scenario and to set some general parameters and to control the global behaviour of the simulation. The Cockpit Display presents all the information and input means the pilot has to his disposal. It is composed of the following elements [RH.1.2]: The Primary Flight Display (PFD), that displays the basic flight parameters (horizon line,

speed, altitude and rates of climb and turn). The Navigation Display (ND), that presents the navigational environment (beacons,

display of ADS-B and TIS-B tracks). It also comprises the CDTI elements and the CDTI++ elements.

The Electronic Flight Instrument System Control panel (EFISCP) to control the ND display.

The Mode Control Panel (MCP) to pilot the aircraft. The Control Display Unit (CDU) to perform additional tasks such as selections.

Deleted: 3.1

Deleted: break-down

Deleted:

Deleted:

Top-Le

CockpitDisplay

N times x

¶

Deleted: Top-Level Application

Deleted: ,

Deleted:

Deleted: , …

Deleted: other aircraft, …)

Deleted: e

Deleted: ¶




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The Air Situation Display enables the global visualisation of the scenario. It is comparable to a radar controller view of the air situation. The Air Situation display is implemented as a configured CWP component [RH.1.3].

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



5 FUNCTIONAL SPECIFICATION

5.1 Simulation of Aircraft Flights

The simulation of aircraft flights shall be initialised from the scenario file selected in the Top Level Application. This scenario defines the encounter between two or more aircraft [RF.1.1]. The simulation of an aircraft flight shall be possible under two different modes : • The « Automatic Guidance » mode [RF.1.2]. In this mode, the aircraft is moved

automatically using data contained in the initialisation files describing the scenario. In this mode, no manual intervention is needed from the user. This is the default mode in which each aircraft enters at the beginning of the scenario. Initial position, speed and altitude of the aircraft are taken from the first point of the trajectory file (req. RF.1.2 :A/P(b)).

• The « User Guidance » mode [RF.1.3]. If the user intervenes, i.e. if he actions any control on the MCP, the automatic guidance for this aircraft is automatically disengaged. The user can control either only vertical navigation (lateral navigation remains automatic), or lateral and vertical navigations In this mode, the control of the aircraft shall be performed by the Aircraft Model module through the MCP. The target values (values entered on the MCP and activated) shall be interactively entered by the user. Under User Guidance mode, the aircraft shall :

reach the target values in a smooth manner, reproducing the aircraft dynamic (req. RF.1.3 :USER(a)),

stay on the other current flight parameters (req. RF.1.3 :USER(b)). It is possible to re-engage either lateral navigation only, or lateral and vertical navigations. An algorithm to identify next waypoint will be provided by Eurocontrol.

In any mode, it shall be possible to change the time ratio factor of the simulation from 0.1 to 10 (req. RF1 :SIM(a)). However, the update rate of the main control loop shall be set in order to obtain the best compromise between realism of the simulation (i.e. fluidity of the aircraft behaviour, as derived from actual aircraft time constants) and the computational load of the software (req. [RP.2]). The eCockpit component shall generate ADS-B reports that are distributed to other participating eCockpits and to any compatible simulated aircraft [RF.1.4]. The eCockpit component shall receive ADS-B reports from neighbouring traffic and TIS-B reports from local ground stations [RF1.5]. The eCockpit component shall receive the ADS-B and TIS-B reports in the form of logically formatted ASTERIX messages, category 21 for ADS-B and category 62 for TIS-B.

5.1.1 Initialisation files

Three types of initialisation files shall be used : scenario file, trajectory file, and navigation file (req. RF.1.1). Additionally, some parameters will be set into a configuration file. • Scenario file (req. RF.1.1 :FILES(a)) :

Deleted: 3.1

Deleted: O

Deleted: During the simulation, to reproduce ADS-B capabilities, surveillance data shall be transmitted among aircraft




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



A scenario file shall contain a textual description of the scenario, a list of sets {aircraft identifier, filename, delay} where :

- « aircraft identifier » is the aircraft callsign. - « filename » (absolute or relative) refers to an aircraft trajectory file (see below). - « delay » refers to the time delay for activating the aircraft. (This item is optional.)

• Trajectory file (req. RF.1.1 :FILES(b)) : A trajectory file shall be composed of a list of waypoints with an altitude and a speed associated to each waypoint. A waypoint shall be described either by a couple of latitude and longitude positions, or by an identifier. In the latter case, the identifier shall correspond to a navigation point defined in the navigation file. • Navigation file (req. RF.1.1 :FILES(c)) : The navigation file shall be composed by a sequence of lines, one line for each navigation point. Each line is composed by an identifier, the type of navigation point, latitude and longitude positions. The following formats shall be used :

• Aircraft identifier (or callsign) : 8 characters maximum • Navigation point identifier : 5 characters maximum • Latitude : ±xx.xxxx, where x is a digit (range ±90, North +, South - ) • Longitude : ±xxx.xxxx, where x is a digit (range ±180, East +, West - ) • Type of navigation point : enumerate. The different foreseen types are :

VOR/DME NDB Published waypoint

It shall be possible to define other types of navigation point later in future software releases.

• Sectors file (req. RH.1.3 :ASD(e)) : The sectors file shall be constituted of a sequence of lines, one line for each sector. Each line is composed by an identifier, the lower level of the volume, the upper level of the volume, and a list of navigation points defining the volume geometry. Those descriptions shall respect EUROCONTROL format (IPAS), which is :

• Sector identifier : 5 characters maximum • Lower and upper level: numeric value of 3 characters maximum (range : 000 – 999) • Navigation point identifier : 5 characters maximum

• Airways file (req. RF.1.3 :ASD(e)) : The airways file shall be constituted of a sequence of lines, one line for each airway. Each line is composed by an identifier and a list of navigation points defining the airway. Those descriptions shall respect EUROCONTROL format (IPAS), which is :

• Airway identifier : 5 characters maximum • Navigation point identifier : 5 characters maximum

• Configuration file :

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The configuration file contains the following parts : A general part containing global parameters set for all scenarios (such as

processing behaviour options), A scenario part containing parameters set for the current scenario (such as wind

data), A user part, containing cockpit parameters and options

The interface for modification is foreseen to be developped in future software releases.

5.1.2 ADS-B

To perform CDTI and CDTI++ functions, for each aircraft, the following information on the other aircraft of the simulation must be available : callsign, 3D position, 3D velocity vector, selected MCP values, trajectory points (req. RF.1.4). The availability of these data is of no technical difficulty in a software environment but may not reflect real life situation. The ADS-B technology which is nowadays spreading widely all over the world justify the use of these information in a software and guarantees its theoretical ability to equip “on board” computers in the future.

5.2 Top Level Application

The following functions are provided : 1. Selection of a scenario throught a selection box. The scenario files are organised by

directories and it is possible to navigate in sub-directories (req. RH.1.1 :TOP(a)). 2. Once a scenario is selected, the list of callsigns of aircraft present in the scenario is

displayed in another selection box (req. RH.1.1 :TOP(b)). 3. Selection of an aircraft from the list of callsigns and display of the corresponding cockpit.

(req. RH.1.1 :TOP(c), RH.1.1 :TOP(d)). The maximum number of aircraft that can be selected simultaneously is limited by the MaximumAircraft parameter, as set in the configuration file. The maximum number of cockpits that can be opened simultaneously is limited by the MaximumCockpits parameter, as set in the configuration file.

4. Display of the air situation panel (req. RH.1.1 :TOP(e)). Multiple panels can be displayed (req. RH.1.3 :ASD(a)).

5. Simulation control : • Time ratio control (req. RH.1.1 :TOP(g) ) : a slider is provided allowing to adjust the time ratio factor from 0.1 to 10. The attention is brought on the fact that, at accelerated speeds, no provision is made to reduce the computational load of the application. Consequently, this may lead to an overload of the application which can result in a delay to handle the user actions. • Start : starts the simulation. It is no more possible to change scenario, aircraft or to restart the simulation unless stopping the execution. • Pause : freeze the simulation. It is no more possible to interact with the cockpits until the simulation is resumed.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Resume : the simulation is unfrozen and continues. This function is available only while the simulation is frozen (Pause function). • Stop : stops the simulation. Available only when the simulation is started (req. RH.1.1 :TOP(f)).

Note : Except if otherwise specified, the initial time of the simulation will be the real time at which the start button has been pressed. Consequently, the simulated time and the real time will remain equal as long as the time ratio factor remains “x1”. 6. Display of five lines of text message giving a general description of the scenario (req.

RH.1.1 :TOP(i)). This text is extracted from the scenario file. 7. Application control (req. RH.1.1 :TOP(j)) :

• Quit : exits the application. Available only when no simulation is running. • Help : provides a help on the use of the application.

5.3 Cockpit Panel

The Cockpit Panel provides the following functions : 1. Selection of different options and parameters :

• Display format : Boeing 777 and Airbus 340. Only the Boeing 777 format will be developed (req. RH.1.2.1 :OPT(a)) • CDTI++ options :

Type of representation : absolute, relative. Only the absolute type will be developed (req. RH.1.2.1 :OPT(b))

Level of assistance : baseline, what-if, scale of effect, advisory. Only the baseline and what-if levels will be developed (req. RH.1.2.1 :OPT(c))

2. Display of flight parameters and flight environment through EFIS components : Primary Flight Display and Navigation Display

3. Control of the EFIS through the EFIS panel 4. Control of the flight through the autopilot on the Mode Control Panel 5. Target aircraft designation through the Control Display Unit and/or through the mouse 6. Additional cockpit controls (req. RH.1.2 :ENV(b)) :

• quit : close the cockpit panel (the simulation continues) • help : provides a help on the use of the flightdeck

5.4 Primary Flight Display (PFD)

This PFD shall display a number of aircraft/flight parameters. These parameters essentially reflect the output of the aircraft model and some aspects of the trajectory management. This is detailled in chapter 6. There is no specific functional specification for that display.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



5.5 Navigation Display (ND)

The ND shall display a number of environmental parameters such as navigational beacon, waypoints and other aircraft. This is detailled in chapter 6. The functional specification of navigation display concerns its interactivity :

• Clicking on the ND/CDTI on an aircraft symbol shall copy the SSR code and/or the callsign in the scratchpad (req. RH.1.2.2.5 :INTERACT(a)). This designation function shall be compatible with the CDU designation (req. RH.1.2.2.5 :INTERACT(c)). • Clicking on the ND on an unspecified point shall display the latitude and longitude of the point in the scratchpad (example : N47°15.4 W008°03.4) (req. RH.1.2.2.5 :INTERACT(b)). This designation function shall be compatible with the CDU designation (req. RH.1.2.2.5 :INTERACT(c)). • Clicking on the ND on a navaid shall display its name in the scratchpad (req. RH.1.2.2.5 :INTERACT(b)). • It shall be possible to add route waypoint graphically (req. RH.1.2.2.5 :INTERACT(d)). The procedure shall be :

- Click on the point to be added (specified or not) and select its location in the route (CDU route legs page). The modified trajectory shall then appear (see § 6.4.1.3 for details on graphic representations)

- Press the CDU “EXEC” button. The insertion of the waypoint shall be validated : the modified route shall become active.

Note that pressing on “ERASE” button shall cancel any route edition performed since the last validation by “EXEC”.

• It shall be possible to suppress route waypoint graphically (req. RH.1.2.2.5 :INTERACT(e)). The procedure shall be :

- Click on the “DEL” CDU button and on the route waypoint to be suppressed. The modified trajectory shall then appear.

- Press the CDU “EXEC” button.The suppression of the waypoint shall be validated : the modified route shall become active.

Note that pressing on “ERASE” button shall cancel any route edition performed since the last validation by “EXEC”.

5.6 EFIS Control Panel

The EFISCP shall enable the control of the EFIS components. See the related Human Machine Interface chapter for details.

Deleted: 3.1


Formatted: Indent: Left: 0.98",Hanging: 0.2", Bulleted + Level: 1 +Aligned at: 0.49" + Tab after: 0.74"+ Indent at: 0.74", Tabs: Not at 0.74"

Formatted: Indent: Left: 0.98",Hanging: 0.2", Bulleted + Level: 1 +Aligned at: 0.49" + Tab after: 0.74"+ Indent at: 0.74", Tabs: Not at 0.74"



CS-CISI/CDTI/DSL

Version 4.0 10/05/04



5.7 Mode Control Panel (MCP)

The MCP shall enable control of the autopilot. It is detailled in the Human Machine Interface related chapter. The functional specification related to this HMI panel are described in 5.11.

5.8 Control Display Unit (CDU)

The CDU provides the following functions : 1. Display of all the aircraft visible through ADS-B : callsign, SSR code, current

information, display mode. The aircraft can be sorted by callsign, SSR code or distance. Current information is composed of : relative altitude, vertical speed trend (steady, climbing or descending), ground speed and distance Display mode is one of Extended, Reduced, None and could be changed by the user

2. Selection/deselection of a target aircraft by entering its callsign or SSR code from the keyboard (req. RH.1.2.5 :CDU(a), RH.1.2.5 :CDU(c)) or by clicking it with the mouse on the ND (req. RH.1.2.6 :SELECT(a), RH.1.2.6 :SELECT(b), RH.1.2.6 :SELECT(c)) or by selecting it from the aircraft list.

3. Display of the list of target aircraft : callsign, SSR code, current information, ASAS mode and display mode (req. RH.1.2.5 :CDU(b)). Ten (10) aircraft maximum can be displayed (req. RH.1.2.5 :CDU(d)). ASAS mode is one of LSA, VSA, LP, LSK, None (default) Display mode could be changed by the user

4. Each target aircraft shall be edited individually. The informations displayed are : • callsign, SSR code, current information • ASAS mode, display mode • look-ahead if the ASAS mode is LP or LSK • separation standard • “what-if” separation and if applicable time associated : “what-if” assistance consists in computing hypothetical separation values according to test values associated with the ASAS mode (HDG/TRK for LSA and LP, VS/FPA for VSA, IAS/Mach/GS for LSK). The user enters the test values by incrementing/decrementing according to a specified step • current separation and if applicable time associated • scale of separations assistance : consists in indicating the separation values for the current value +/- an increment • advisory assistance : indicates the manœuvres needed to meet the separation. The algorithm will be provided by Eurocontrol

The ASAS mode, display mode, look-ahead, separation standard could be changed by the user

5. Definition of general display options : • type of sort to be applied to the aircraft list (by callsign, SSR code or distance) • activation/deactivation of the display of the seperation circle around own aircraft in the ND • default display mode for target (extended) and for non target (none) • selection of manœuvre for LSK : IAS/Mach (default) versus GS

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• altitude : no/relative/absolute (default is relative) • selection of the increments used in the “what-if” and scale of separations assistances, for each ASAS mode

6. Definition of reduced and extended display options (unless mentioned, default is off for reduced and on for extended) :

• SSR code on/off • callsign on/off (default is on) • ground speed on/off • vertical speed trend on/off (default is on) • velocity vector (on/off – default is on) along with look-ahead value (0 can be interpreted as off and any positive value as on) • past positions (on/off) along with past positions number (0 can be interpreted as off and any positive value as on) • ASAS related indications (on/off) – extended only • ASAS related conflict indications (on/off) – extended only

7. Modification of the active route : • for each waypoint, display of waypoint name, course, distance to go, speed, flight level • add, delete waypoint. The modifications must be validated to be taken into account. They can be cancelled before validation

8. Selection/deselection of the left or right navigational aid (VOR/DME or NDB) among the list of existing beacons.

See the related Human Machine Interface chapter for details.

5.9 Air Situation Display

The ASD shall display a controller-like representation of the global air situation. It shall be possible to activate multiple ASD (req. RH.1.3 :ASD(a)). When changing the scenario, the ASDs opened shall remain opened (contrary to the cockpits) and shall be updated (scenario files shall be rescanned) (req. RH.1.3 :ASD(a)). See the related Human Machine Interface chapter for details.

5.10 Aircraft Model module

This module computes all the aircraft positional and dynamic parameters. It uses the current parameters (at time t) and the selected values for heading/track, speed, altitude vertical speed and/or flight path angle and computes a new set of parameters at the time t + dt. The exact list of in and out parameters for this module are given in annex. This module is provided by the EUROCONTROL Experimental Centre (req. RF.1.3 :USER(c)) and therefore is not described hereafter.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



5.11 Autopilot Logic module

This module takes into account the user inputs made on the MCP panel and computes the resulting AutoPilot Pitch mode, Roll mode, Autothrottle mode and provides the selected values to the Aircraft Model. The Autopilot Logic module does not handle the Roll and Pitch Armed modes. The ADFS status is always set to A/P. 1. At scenario startup, the aircraft is in Automatic guidance mode : SPD, VNAV PTH,

LNAV (req. RF.1.2 :A/P(c)). 2. The User Guidance mode is entered as soon as any control of the MCP is activated by the

pilot. If the aircraft was manoeuvring when switching to User Guidance, the aircraft stabilises around its current value (speed, track/heading and altitude). If the pilot activates the IAS/Mach, V/S-FPA or altitude buttons of the MCP, VNAV is disengaged. The autopilot modes change to SPD, ALT, LNAV. Vertical navigation is carried out through the V/S-FPA and altitude buttons :

• Altitude 4 Actioning the Altitude rotator modifies the value in the altitude window but do not

alter any Autopilot mode. 4 Pressing the Altitude SEL button changes the pitch mode to FLCH SPD. 4 Pressing the Altitude HOLD button changes the pitch mode to ALT and sets the

current altitude value into the selected altitude value (stops climbing). 4 When the current altitude reaches the selected altitude, the pitch mode changes from

FLCH SPD to ALT • V/S-FPA

4 Pressing the V/S-FPA button changes the pitch mode to V/S or FPA, according to the V/S-FPA switch setting. The value in the V/S-FPA window is copied respectively from the current FPA or current vertical speed.

4 Pressing the V/S-FPA switch will alternately set the pitch mode to FPA or to V/S. 4 Actioning the V/S-FPA rotator modifies the value in the V/S-FPA window

• Speed controls are carried out throught the IAS/Mach buttons : 4 Actioning the IAS/Mach switch has no effect on the autopilots logics. 4 Actioning the speed rotator modifies the value in the speed window but do not alter

any Autopilot mode. 4 Pressing the speed SEL button sets the value of the IAS/Mach window as the target

speed 4 Pressing the Speed HOLD button stabilises the speed around the current speed (i.e.

stops accelerating or decelerating). 3. If the pilot activates the HDG/TRK buttons of the MCP, LNAV and VNAV are both

disengaged. The modes change to SPD, ALT, HDG or TRK HOLD (depending on the HDG/TRK reference switch). Lateral navigation is carried out throught the HDG/TRK buttons :

• Heading/Track

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



4 Actioning the HDG/TRK switch will change the roll mode from HDG HOLD to TRK HOLD (or HDG SEL to TRK SEL) and conversely.

4 Actioning the HDG/TRK rotator modifies the value in the HDG/TRK window but do not alter any Autopilot mode.

4 Pressing the HDG/TRK SEL button changes the HDG/TRK HOLD mode to HDG/TRK SEL mode.

4 Pressing the HDG/TRK HOLD button changes the HDG/TRK SEL mode to HDG/TRK HOLD mode and sets the current heading/track value into the selected heading/track value (stops turning).

4. LNAV can be re-engaged by pressing the LNAV button. The roll mode becomes LNAV.

If the VNAV button is pressed, LNAV and VNAV are both re-engaged. The roll mode becomes LNAV and the pitch mode changes to VNAV PTH.

5.12 Aircraft Environment module

This module computes for an aircraft all the data related to external environment, such as other aircraft related data, navaids related data, etc... Most of the CDTI and CDTI++ information are derived from this module. The values computed by the Aircraft Environment module are described in the following chapters.

5.12.1 Navaids related data

• Navaids X-Y position on ND The X-Y coordinates of the navaids and waypoints are derived from their Latitude-Longitude coordinates, using the GetXYFromLatLon function described in ANNEX E.

• Navaids Bearing and Distance Using the name of the left (resp right) navaid selected on the ND panel, this module computes the bearing angle under which the aircraft sees the navaid and the DME distance between the navaid and the aircraft. This computation uses the GetDistanceBearing function described in ANNEX E.

• Active Waypoint DistanceToGo and ETA Using the name of the active waypoint of the route, this module computes the DistanceToGo and the Estimated Time of Arrival Over the waypoint. For that purpose, it uses the GetDistanceBearing function described in ANNEX E to compute the DistanceToGo and divides this distance by the current True Air Speed (TAS) disregarding the current track or heading. Active Waypoint DistanceToGo and ETA are not computed when in User Guidance Mode.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



5.12.2 Aircraft related data

For each aircraft of the scenario, the following data are computed, relatively to the subject aircraft : • Aircraft GroundSpeed

The GroundSpeed is computed as the modulus of the vectoriel sum of the given True Air Speed and the current winds.

• Aircraft X-Y position on ND The X-Y coordinates of the other aircraft are derived from their Latitude-Longitude coordinates, using the GetXYFromLatLon function described in ANNEX E.

• Closest Point of Approach (CPA). The values : Time before CPA, subject and target 3-D positions at CPA, Lateral and Vertical Distances at CPA, Time of Conflict (TC) for both Lateral and Vertical Separation Assurance modes are computed using the ComputeCPA function described in ANNEX E.This computation is based on the current values of flight parameters to provide baseline assistance. In the case of what-if assistance, the calculation use the same flight parameters whose values are then deduced from target values displayed on the MCP (req. RH.1.2.2.4 :WHAT-IF(a,b)).

• Lateral Passing – OblicDistance (OD) and TrendOblicDistance. The OblicDistance is computed using the GetDistanceBearing function described in ANNEX E. The TrendOblicDistance is deduced from the extrapolated positions at time t + ∆TLP-LSK, where ∆TLP-LSK is set on the CDU page corresponding to the target aircraft (“PRED” value). Those extrapolations are based on current TAS and track of both aircraft to provide baseline assistance. In the case of what-if assistance, the same extrapolations are made, based on : TAS and track of own aircraft, calculated from target values displayed on the MCP. current TAS and track of target aircraft. (req. RH.1.2.2.4 :WHAT-IF(c))

• Lateral Passing – ClosureRate (CR). The ClosureRate is computed as the scalar product between the relative 2-D position of the target aircraft by its relative velocity vector. To provide baseline assistance, the velocity vector calculation is based on the current values of flight parameters. To provide what-if assistance, the calculation use the same flight parameters whose values are then deduced from target values displayed on the MCP (req. RH.1.2.2.4 :WHAT-IF(c)).

• Longitudinal Station Keeping – AlongTrackDistance (ATD), TrendAlongTrackDistance and Along Track Line. The Along Track Line is the trajectory that shall be followed in order to reach and maintain a given distance behind the target aircraft. For simplification purpose, the ATL will be the line connecting the two aircrafts. Dispite this, the graphical API will provide a function to draw a list of segments.

Deleted: 3.1





CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The TrendAlongTrackDistance is deduced from the extrapolated positions at time t + ∆TLP-LSK, where ∆TLP-LSK is set on the CDU page corresponding to the target aircraft (“PRED” value). Those extrapolations are based on current TAS and track of both aircraft to provide baseline assistance. In the case of what-if assistance, the same extrapolations are made, based on : TAS and track of own aircraft, calculated from target values displayed on the MCP. current TAS and track of target aircraft. (req. RH.1.2.2.4 :WHAT-IF(d)) The Along Track Distance is computed as the length of the ATL. For simplification pupose, the ATD will be computed as the oblic distance between the two aircrafts.

• Longitudinal Station Keeping – ClosureRate (CR). The LSK Closure rate is the derivative of the ATD. For simplification purpose, the Closure rate will be computed as follows : (ATDpredicted – ATDcurrent)/∆T. (Where the calculation of ATDpredicted is based on MCP target values for the what-if information (req. RH.1.2.2.4 :WHAT-IF(d)))

5.13 Automatic guidance

When the aircraft is in automatic guidance mode, it perform a step by step progression along the trajectory, using linear interpolation between the waypoints (A & B) defining the current trajectory leg (req. RF.1.2 :A/P(a)). More particulary, the following rules apply : • Speed : the aircraft movement is supposed to follow a uniform acceleration.

Let VA ,VB be the expected speeds respectively at points A and B, and D be the horizontal distance beetween waypoints A and B. In order to joint the next waypoint with exactly the expected speed, the constant acceleration shall be : a = ( VB

2 –VA2 ) / 2D

Therefore, the current speed at time t is given by : Vt = a. ∆t + VA with ∆t = t-TA

• Cartesian coordinates : The horizontal positioning between two waypoints shall be computed in a way so that the aircraft follows the segment joining the waypoints. The distance (dt) from the point A on this segment at time t is given by : dt = ½ . a . (∆t)2 + VA . ∆t The aircraft reaches the point B at time TB, defined by : D = ½ . a . (TB - TA)2 + VA . (TB - TA)

• Altitude : Let ZA, ZB be the expected altitudes respectively over points A and B. The current altitude at time t is computed as :

Deleted: 3.1





CS-CISI/CDTI/DSL

Version 4.0 10/05/04



Zt = ZA + ∆t . (ZB – ZA) / (TB – TA) As soon as t > TB the next point of the trajectory is taken into account and the previous formulas are transposed for points B and C. And so on…

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6 MAN-MACHINE INTERFACE

6.1 Top Level Application

The top-level panel shall look as described below :

The availability of the different commands is context-dependent and follows the rules described herebelow (req RH.1.1 :TOP(k)) : Initially, only the « Quit » and « Help » buttons and the « Scenario » selection box are sensitive. When a scenario is chosen, the « Air situation display », « Start » buttons and the « Time ratio control » slider become sensitive. The aircraft of the scenario are displayed in the « Callsigns » box. The « Show cockpit » button becomes sensitive when an aircraft is selected. The « Air situation display » button opens the air situation panel. Only one air situation panel is displayed. When one clicks the « Start » button, it remains depressed and the « Pause » and « Stop » buttons become sensitive. Clicking one more time on the « Start » button has no effect if a simulation is running. The « Quit » and « Show Cockpit » buttons become insensitive. The « Pause » button remains depressed when it is clicked. Clicking one more time the button raises it and unfreezes the application.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



When the « Stop » button is pressed, it becomes insensitive, like the « Pause » button. The « Start » and eventually « Pause » buttons are raised. The « Quit » and « Show Cockpit » buttons become sensitive. The « Help » button opens a window, which displays the help in HTML format

6.2 Cockpit Panel

Only the left side of the cockpit is reproduced (req. RH.1.2 :ENV(a)). The background of the flightdeck is brown (R=150, G=126, B=96) The title of the cockpit window is the aircraft callsign. The cockpit window has zoom and scroll features.

The menu bar at the top of the cockpit window allows to close the cockpit view, to set options and to get help

The « Quit » button closes only the current Cockpit window, leaving the simulation running (req. RH.1.2 :ENV(b)). It is always available (req. RH.1.2 :ENV(c)).

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



Display format : The cockpit display shall be able to propose two options for the display format. These options shall be : “Boeing 777” and “Airbus 340” (req RH.1.2.1 :OPT(a)). The selection is made through a menu listing both formats. However, only the “Boeing 777” format shall be developed. Representation type : The cockpit display shall be able to propose two options for the representation type. These options shall be : “Absolute” and “Relative” (req. RH.1.2.1 :OPT(b)). The selection is made through a menu listing both types. However, only the “Absolute” type shall be developed. Assistance Level : The cockpit display shall be able to propose four options for the assistance level. These options shall be : “Baseline”, “What-if”, “Scale of Effect” and “Advisory” (req. RH.1.2.1 :OPT(c)). The selection is made through a menu listing both types. However, only the “Baseline” level shall be developed. The « Help » button opens a window, which displays the same help as from the Top Level Application, but directly opened on the “Cockpit Display” chapter (req. RH.1.2 :ENV(b)). It is always available (req. RH.1.2 :ENV(c)). The status of the aircraft shall be indicated on each cockpit (req. RH.1.2 :ENV(c))

- “ stopped “ when the simulation is not started yet or has been stopped. - “ not started ” when the simulation is started, before the activation delay of the

aircraft, - “ frozen ” when the simulation is in pause,

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.3 Primary Flight Display

The PFD shall represent its data as depicted in [DA3] and [DR1] (req RH.1.2.2.1 :Figure1). Some precisions are given below. The PFD background is dark blue (R=31, G=71, B=95).

For each item, [S] indicates that the item can be automatically or manually switched on/off.

6.3.1 PFD Flight Mode Annunciation (FMA)

The FMA part of the PFD displays the current states of the autopilot (in terms of pitch mode, roll mode and autothrottle). The FMA layout shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure2). Its background is grey (R=G=B=127). The following convention is applied : engaged in green, armed in white, NO AUTOLAND in amber. (req. RH.1.2.2.1 :PFD.FM(g)). All these data are given by the Autopilot Logic module.

6.3.1.1 Autothrottle Modes (engaged)

Engaged autothrottle mode is displayed in the upper left part of the FMA (req. RH.1.2.2.1 :PFD.FM(a)). The PFD shall be able to display the following values : THR, THR REF, HOLD, IDLE, SPD. If only one autothrottle is armed, the autothrottle mode display is preceded by L or R ([DR1] 4.20.9).

6.3.1.2 AFDS Roll Modes (armed)

Armed roll mode is displayed in the lower central part of the FMA (req. RH.1.2.2.1 :PFD.FM(c)). The PFD shall be able to display the following values : LOC, ROLLOUT, LNAV.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.3.1.3 AFDS Roll Modes (engaged)

Engaged roll mode is displayed in the upper central part of the FMA (req. RH.1.2.2.1 :PFD.FM(b)). The PFD shall be able to display the following values : LOC, ROLLOUT, LNAV, HDG HOLD, TRK HOLD, HDG SEL, TRK SEL, TO/GA, ATT.

6.3.1.4 AFDS Pitch Modes (armed)

Armed pitch mode is displayed in the lower right part of the FMA (req. RH.1.2.2.1 :PFD.FM(e)). The PFD shall be able to display the following values : G/S, FLARE, VNAV.

6.3.1.5 AFDS Pitch Modes (engaged)

Engaged pitch mode is displayed in the upper right part of the FMA (req. RH.1.2.2.1 :PFD.FM(d)). The PFD shall be able to display the following values : TO/GA, ALT, V/S, FPA, VNAV PTH, VNAV SPD, VNAV ALT, G/S, FLARE, FLCH SPD.

6.3.1.6 AFDS Status (engaged)

The AFDS status is displayed between the previous modes and the attitude information (req. RH.1.2.2.1 :PFD.FM(f)). The PFD shall be able to display the following values : FLT DIR, A/P, LAND3, LAND2, NO AUTOLAND.

6.3.2 PFD Airspeed Indications

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure3). See also [DR1] 10.10.3 and 10.10.4. The airspeed tape background is grey (R=V=B=127). The numbers and scale marks are white and can scroll up and down. • Selected Speed [S] (req. RH.1.2.2.1 :PFD.SPD(a)) :

When in User Interactive Control, displays the value as set in the MCP IAS/MACH window. When in Automatic Guidance, nothing is displayed. The number displayed has 3 digits, in magenta when SelectedSpeedIsToDisplay = AsSelValue, or in white when SelectedSpeedIsToDisplay = AsHoldValue. This item is selectable [S] : the selection is done through the API (variable SelectedSpeedIsToDisplay).

• Speed Trend Vector (req. RH.1.2.2.1 :PFD.SPD(b)) : indicates predicted airspeed in ten seconds based on current acceleration or deceleration. The vector is represented by a black arrow from the Current Airspeed value to the predicted value. When in User Interactive Control, the PredictedAirspeed is provided by the aircraft model. When in Automatic Guidance, the PredictedAirspeed equals the CurrentAirspeed.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Current Airspeed (req. RH.1.2.2.1 :PFD.SPD(c)) : indicates current Air Data Inertial Reference System (ADIRS) airspeed. The number displayed has 3 digits max, in white on black. The box around the current airspeed indication turns amber when airspeed is below minimum manoeuvring speed. Both CurrentAirspeed and MinimumManoeuvringSpeed are provided by the aircraft model.

• Current Mach (req. RH.1.2.2.1 :PFD.SPD(d)) : displays current ADIRS Mach when greater than 0.40 Mach. The number displayed has 3 digits with a leading decimal point, in green.

• Maximum Speed (req. RH.1.2.2.1 :PFD.SPD(e)) : indicates maximum permissible airspeed. Along the right edge of the airspeed indication, the area from the top of the airspeed scale to the maximum speed value is covered by small red squares ([DR1] 10.10.3) The MaximumSpeed is provided by the aircraft model and is computed as the minimum between 340 and the value in knots of 0.9 Mach

• Maximum Manoeuvring Speed [S] (req. RH.1.2.2.1 :PFD.SPD(f)) : when displayed, indicates manoeuvre margin to buffet. This value is computed as Maximum Speed - 10 This item is selectable [S] : it is displayed when in scale (according to the up-down scale movement).

• Speed Bug [S] (req. RH.1.2.2.1 :PFD.SPD(g)) : Points to the SelectedSpeed as described above. The bug is five knots in height. When the selected speed is off scale, the bug is parked at the top or bottom of the airspeed indication, with only half the bug visible. The bug is transparent. Its border has the same colour as the SelectedSpeed described above. It can move along the airspeed tape. This item is selectable [S] : the selection is done through the API (variable SelectedSpeedIsToDisplay).

6.3.3 PFD Reference Speeds

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure4). All the PFD reference speeds described below are provided by the aircraft model. • Takeoff Reference Speeds [S] (req. RH.1.2.2.1 :PFD.SPD(h)) : displays the takeoff

reference speeds V1, VR and V2, as provided by the aircraft model : V1 = 135, V2 = 145, VR = 140. These items are selectable [S] : they are displayed only when the pitch mode is set to TO/GA.

• Flap Manoeuvring Speed [S] (req. RH.1.2.2.1 :PFD.SPD(i)) : indicates to the pilot the manoeuvring speed at which he should command the next flap retraction or extension. Displays the flaps opening angle (1, 5, 15, 20, 25 or 30) in front of the related speed (resp. 240, 220, 200, 190, 180, 170). This item is selectable [S] : it is not displayed above 20000 ft altitude.

Deleted: 3.1

Deleted: ¶¶

Deleted: ¶

Deleted: ¶

Deleted: ¶




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Landing Reference Speed [S] (req. RH.1.2.2.1 :PFD.SPD(j)) : displays the VREF speed provided by the aircraft model : VREF = 130. This item is selectable [S] : it is displayed in landing mode, i.e. only when the pitch mode is set to G/S or FLARE.

• Minimum Manoeuvring Speed [S] (req. RH.1.2.2.1 :PFD.SPD(k)) : indicates manoeuvre speed margin to stick shaker or low speed buffet. MinimumManoeuvringSpeed = MinimumSpeed + 5 This item is selectable [S] : it is displayed when in scale (according to the up-down scale movement).

• Minimum speed (req. RH.1.2.2.1 :PFD.SPD(l)) : indicates the airspeed where stick shaker activates. The minimum speed is computed according to the flap angle and is equal to 5 + resp. 150, 145, 140, 132, 117, 112, 110 when flap angle is resp. 1, 5, 15, 20, 25, 30 Along the right edge of the airspeed indication, the area from the bottom of the airspeed scale to the minimum speed value is covered by small red squares.

• Selected Landing Flaps and VREF Speed [S] (req. RH.1.2.2.1 :PFD.SPD(m)) : Displays digitally the current landing flaps setting and the landing reference speed at the bottom of the airspeed indication. Selected Landing Flap = 30 This item is selectable [S] :. it is displayed in landing mode, i.e. only when the pitch mode is set to G/S or FLARE.

6.3.4 PFD Attitude Indications

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure5). The upper part of the PFD representing the sky is light blue (R=75, G=143, B=171). The lower part representing the ground is amber (R=176, G=135, B=48). When in User Interactive Control, all the PFD Attitude Indications described below are provided by the aircraft model. • Bank Pointer (req. RH.1.2.2.1 :PFD.ATT(a)) : indicates ADIRS bank angle in reference

to the Bank Scale. Turns solid amber at bank angles of 35° or more. When in Automatic Guidance, the BankPointer always indicates 0°.

• Slip/Skip Indication (req. RH.1.2.2.1 :PFD.ATT(b)) : displaces beneath the Bank Pointer to indicate slip or skid. Turns solid white at full scale deflection and solid amber at bank angles of 35° or more. Slip/skid angle is represented by a right (resp. left) translation for positive (resp. negative) angles, in which the center of the rectangle remains on a radius making the slip/skid angle with the CurrentBank angle. When in Automatic Guidance, the Slip/Skid angle is always set to 0°.

• Pitch Limit Indication [S] (req. RH.1.2.2.1 :PFD.ATT(c)) : Indicates pitch limit provided by the aircraft model (stick shaker activation point for the existing flight conditions). Pitch limit = 20. This item is selectable [S] : it is displayed when flaps are not up or at slow speeds with flaps up.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



A configuration file will define the slow speed threshold. • Horizon Line and Pitch Scale (req. RH.1.2.2.1 :PFD.ATT(d)) : Indicates the ADIRS

horizon relative to the Airplane Symbol. Pitch scale is in 2.5° increments. If the pitch is greater than 45°, chevrons are displayed.

• Bank Scale (req. RH.1.2.2.1 :PFD.ATT(e)) : Scale marks are at 0, 10, 20, 30, 45 and 60 degrees.

• Airplane Symbol (req. RH.1.2.2.1 :PFD.ATT(f)) : Indicates airplane attitude with reference to the ADIRS Horizon Line. This symbol is fixed on the screen.

6.3.5 PFD Steering Indications [S]

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure6). See also [DR1] 10.10.9. When in User Interactive Control, all the PFD Steering Indications described below are provided by the aircraft model, even for the Selected Flight Path Angle which may be initially isued by user interaction on the MCP. When in Automatic Guidance, only the Flight Director Pitch and Roll Bars are displayed. • Flight Director Pitch and Roll Bars (req. RH.1.2.2.1 :PFD.ATT(g)) : indicate flight

director pitch and roll commands, as set by the autopilot. These bars never rotate. The Pitch Bar represents that angle and is displayed on the same scale as the pitch angle. The Roll Bar takes values from –1 to +1 which are linearly displayed from the left edge of the PFD central panel (-1) to the right edge (+1).

• Flight Path Vector (req. RH.1.2.2.1 :PFD.ATT(h)) : displays current Flight Path Angle and current drift angle when FPA is selected on the MCP. FPA is displayed relative to the horizon line . Drift angle is represented by the perpendicular distance from the centreline of the pitch scale to the Flight Path Vector symbol. The drift angle is displayed on the same scale as the pitch angle (i.e. using such a factor that 40° are displayed on the totality of the PFD central panel, either horizontally or vertically).

• Selected Flight Path Angle (req. RH.1.2.2.1 :PFD.ATT(i)) : indicates the selected FPA when FPA is selected on the MCP.

All the items above are displayed when the MCP Flight Director switch is ON (Default) ([DR1] 4.10.2).

6.3.6 PFD Radio Altitude Indications

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure7). • Radio Altitude [S] (req. RH.1.2.2.1 :PFD.STAT(a)) : displays radio altitude below 2500

ft AGL (Above Ground Level). When in User Interactive Control, the RadioAltitude is provided by the aircraft model. When in Automatic Guidance, the RadioAltitude is equal to the current altitude for simplification purpose. This item is selectable [S] : nothing is displayed above 2500 ft AGL.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



Turns amber when below radio altitude minimum.

6.3.7 PFD Instrument Landing System (ILS)

6.3.7.1 PFD Instrument Landing System Indications [S]

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure8). See also [DR1] 10.10.11. All the information directly depending on an ILS equipment in the real life should normally be displayed only if the ILS signal is actually received. However the reception of this signal is not modelised. Consequently all these ILS dependant information will be displayed only if a boolean value is set through the graphical API. Additional display conditions may be described below for each individual item. In the current software version, the ILS dependant information will not be displayed, neither in Automatic Guidance nor in User Interactive Control. • Approach Reference (req. RH.1.2.2.1 :PFD.STAT(b)) : displays the selected ILS

identifier, approach front course and ILS DME distance. These data are given by the aircraft model. This item is selectable [S] : it is displayed only when the ILS Identifier is known (through the graphical API).

• Localizer Pointer and Scale (req. RH.1.2.2.1 :PFD.STAT(c)) : The localizer pointer indicates localizer position relative to the airplane : A circle equals 2 dots deviation. The localizer pointer fills in solid when within 2½ dots from the centre. If the deviation become within ¾ dot, the scale turns to expanded scale (see 6.3.7.2). At low radio altitudes, the scale turns amber and the pointer flashes to indicate excessive localizer deviation (the autopilot is supposed to be always engaged). In a real aircraft, at low altitudes, with LNAV engaged and LOC armed, the localizer scale turns amber and the pointer flashes if the localizer is not captured. This functionality will not be implemented as we assume the ILS localizer is always captured. A configuration file will define :

• low radio altitude threshold • localizer deviation threshold

This item is selectable [S] : it is displayed when the Localiser deviation is known.

• Marker Beacon Indication (req. RH.1.2.2.1 :PFD.STAT(d)) : The Marker Beacon Indication appears and flashes when over one of the marker beacon transmitters :

• IM - Airway or inner marker. • MM - Middle marker. • OM - Outer marker.

The indication flashes in cadence with the ILS identifier on the PFD panel. This item is selectable [S] : it is displayed and flashes for a 10s duration when the related message is received .

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Glideslope Pointer and Scale (req. RH.1.2.2.1 :PFD.STAT(e)) : The glideslope pointer indicates glideslope position relative to the airplane. At low radio altitudes, the scale turns amber and the pointer flashes to indicate excessive glideslope deviation. The GlideSlope pointer fills in solid when within 2½ dots from the centre. A configuration will define the glideslope deviation threshold. This item is selectable [S] : it is displayed when the GlideSlope deviation is known.

6.3.7.2 PFD Expanded Localizer Indications [S]

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure9). Expanded Localizer Scale (req. RH.1.2.2.1 :PFD.STAT(f)) : this item is a zoomed view of the above described Localizer Pointer and scale. A rectangle equals 1/2 dot deviation. This item is selectable [S] : it is automatically displayed when the LocalizerPosition is lower than ¾ dot.

6.3.7.3 PFD Rising Runway Indications [S]

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure10). Rising Runway (req. RH.1.2.2.1 :PFD.STAT(g)) : displayed below 2500 ft Radio Altitude when the LOC mode is engaged. Initially displayed at the bottom of the display, it moves toward the airplane symbol below 200 ft Radio Altitude to reach it at 0 ft Radio Altitude in a linear way. Additionnally, it moves horizontally to remain centered on the Localiser Pointer. The stem of the rising runway symbol flashes in cadence when at least one of the localizer or glideslope pointer flashes ([DR1] 10.10.13). This item is selectable [S] : it is displayed according to the above rule.

6.3.8 PFD Altitude Indications

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure11). See also [DR1] 10.10.14. The altitude indication presented on the Altitude Tape on the right of the PFD are always barometric altitudes. • Selected Altitude [S] (req. RH.1.2.2.1 :PFD.ALT(c)) : displays the altitude value as set in

the MCP altitude window. When in User Interactive Control, displays the altitude value as set in the MCP altitude window. When in Automatic Guidance, nothing is displayed. The value is boxed in white when the Selected Altitude value is between 200 and 900 m. The value is displayed in magenta when SelectedAltitudeIsToDisplay = AsSelValue, or in white when SelectedAltitudeIsToDisplay = AsHoldValue. This item is selectable [S] : the selection is done through the API (variable SelectedAltitudeIsToDisplay).

• Selected Altitude Bug [S] (req. RH.1.2.2.1 :PFD.ALT(a)) : Points to the Selected Altitude as described above.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



When the selected altitude is off scale, the bug is parked at the top or bottom of the tape with only half the bug visible. This item is selectable [S] : the same rule is applied ads for the above Selected Altitude.

• Selected Altitude – Meters [S] (req. RH.1.2.2.1 :PFD.ALT(b)) : indicates the above Selected Altitude in meters (selected in feet in the MCP altitude window). This item is selectable [S] : it is displayed if both the Selected Altitude (above) is displayed and the DisplayAltitudeInMeters boolean is set to True in a configuration file. Display is in 10 meter increments. The used conversion factor is 1 ft = 0.3048 m.

• Current Altitude (req. RH.1.2.2.1 :PFD.ALT(e)) : indicates current ADIRS altitude in feet. If the Barometer Setting is QNH, the CurrentAltitude received from the Aircraft Model is corrected before display, using the folllowing conversion : CurrentAltitudeCorrected = CurrentAltitudeReceived + 0.27.(QNH – 1013) If the Barometer Setting is QFE, the CurrentAltitude received from the Aircraft Model is corrected before display, using the folllowing conversion : CurrentAltitudeCorrected = CurrentAltitudeReceived + 0.27.(QFE – 1013)

• Current Altitude – Meters [S] (req. RH.1.2.2.1 :PFD.ALT(d)) : indicates the (corrected) current altitude in meters. This item is selectable [S] : it is displayed if the DisplayAltitudeInMeters boolean is set to True in a configuration file.

6.3.9 PFD Landing Altitude/Minimum Indications

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure12). These informations are found in a configuration file. BARO Minimum Pointer (req. RH.1.2.2.1 :PFD.ALT(f)) : displays a pointer and line representing the Approach Minimum Altitude.

Turns steady amber when the airplane descends below BARO minimum.

• Landing Altitude Indication (req. RH.1.2.2.1 :PFD.ALT(g)) : the crosshatched area indicates the airport landing altitude for the destination runway or airport as found in a configuration file.

• Minimum Reference (req. RH.1.2.2.1 :PFD.ALT(h)) : displays the string “BARO” or “RADIO” depending on the value of the BARO/RADIO switch. This BARO/RADIO switch is set in a configuration file. Turns amber and flashes for 3 seconds when the airplane descends below selected minimum altitude.

• Minimum (req. RH.1.2.2.1 :PFD.ALT(i)) : indicates the Approach Minimum Altitude numeric value, as found in a configuration file. Turns amber and flashes for 3 seconds when the airplane descends below selected minimum altitude.

• Landing Altitude Reference Bar (req. RH.1.2.2.1 :PFD.ALT(j)) : indicates the height above touchdown.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The bar is amber from 0 to 500 ft above the landing altitude and white from 500 to 1000 ft. The bar stops at 1000 ft.

6.3.10 PFD Barometric Indications [S]

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure13). All these items are selectable [S] depending on the selections made on the EFIS panel. • Barometric setting (req. RH.1.2.2.1 :PFD.ALT(k)) : indicates the current barometric

setting (STD, QNH or QFE). When STD is selected, just the string “STD” is displayed. When QNH is selected, the display shows the QNH value and its unit (“in” or “hPa”). When QFE is selected, the display shows the QFE value, its unit (“in” or “hPa”) and the string “QFE”. Additionnaly, the altitude scale background turns to green (req. RH.1.2.2.1 :PFD.ALT(m)). The display is boxed and changes to amber if the barometric setting is set to QNH or QFE and current altitude is above transition altitude, or if the barometric setting is set to STD and current altitude is below the transition flight level. A configuration file will define :

• Current Barometric Setting • QNH Value • Transition Altitude ASL

The following values are deduced : • Transition Flight Level = TransitionAltitude + 0.27(QNH – 1013), rounded up to the nearest available flight level (by steps of 1000 ft if lower than 29000 ft, by steps of 2000 ft above). • QFE Value = QNH Value + AirportAltitudeASL/0.27.

• Barometric Reference i.e. Pressure Unit (req. RH.1.2.2.1 :PFD.ALT(l)) : Indicates the used pressure units :

• IN : inches of mercury (1 inch Hg = 1013/29.92 hPa) • HPA : hectopascals

The pressure units will be defined in a configuration file. • Autopilot/Flight Director Barometric Source (req. RH.1.2.2.1 :PFD.ALT(n)) : L or R

indicates that the left or right EFIS panel is the barometric setting reference for the autopilot or flight director. Since we have only one EFIS panel (left one), so this items is always set to “L”.

• Preselected Barometric Setting (req. RH.1.2.2.1 :PFD.ALT(o)) : barometric setting can be preselected when STD is displayed. This item can be displayed through the graphical API.

• QFE (req. RH.1.2.2.1 :PFD.ALT(p)) : when STD is selected, a small QFE appears when QFE is selected. This item can be displayed through the graphical API.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.3.11 PFD Vertical Speed Indications

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure14). The vertical scale is not linear. It will be approximated by the following law : linear from 0 to 2 ft/mn and linear (different scale) from 2 to 6 ft/mn. A symetrical law apply to the negative numbers. Scale marks show –6, -2, -1, 0, 1, 2 and 6 ft/mn with one unmarked graduation between each. • Vertical Speed Pointer (req. RH.1.2.2.1 :PFD.VSPD(a)) : indicates current vertical speed.

The display simulates an analogic needle as could be found in former galvanometers. The rotation axis is somewhere at the same height as the scale center (0 value), but outside the display (to the right). However, the needle end will not follow a circle (as in actual galvanometers) but will follow a vertical line, next to the graduations. This facilitates the readability of the display. The Vertical Speed is provided by the Aircraft Model.

• Selected Vertical Speed Bug [S] (req. RH.1.2.2.1 :PFD.VSPD(b)) : indicates the speed selected in the MCP vertical speed window. When in User Interactive Control, the Bug is displayed, according to the value provided by the MCP. When in Automatic Guidance, the Bug is not displayed. This item is selectable [S] : nothing is displayed if the vertical speed window is empty.

• Vertical Speed (req. RH.1.2.2.1 :PFD.VSPD(c)) : displays numerically the vertical speed when greater than 400 ft/mn. The display is located above the vertical speed indication when climbing and below when descending. This item is selectable [S] : displayed when vertical speed greater than 400 ft/mn.

6.3.12 PFD Heading/Track Indications

The layout of this item shall comply to the URD [DA3] (req RH.1.2.2.1 :Figure15). Heading is the direction of the aircraft’s nose, i.e. the direction of the aircraft Airspeed. Track is the direction of the aircraft’s trajectory, i.e. the direction of the aircraft Groundspeed. The track can be deduced from the heading since Airspeed + Windspeed = GroundspeedBeware that this relation is not true for the corresponding selected values. • Selected Heading/Track [S] (req. RH.1.2.2.1 :PFD.HDG(d)) : digital display of the

selected heading or track When in User Interactive Control, displays the selected heading or track as set in the MCP Heading/Track window. When in Automatic Guidance, nothing is displayed. The value is displayed in magenta when SelectedHdgTrkIsToDisplay = AsSelValue, or in white when SelectedHdgTrkIsToDisplay = AsHoldValue. This item is selectable [S] : the selection is done through the API (variable SelectedHdgTrkIsToDisplay).

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Selected Track Bug (MCP selection) [S] (req. RH.1.2.2.1 :PFD.HDG(b)) : is displayed on the inside of the compass rose in the same colour as the Selected Heading/Track value. If the selected track exceeds display range, the bug parks on the side of the compass rose in the direction of the shorter turn to the track. This item is selectable [S] : nothing is displayed if SelectedHdgTrkIsToDisplay = False or if Heading/Track Reference is set to Heading.

• Selected Heading Bug (MCP selection) [S] (req. RH.1.2.2.1 :PFD.HDG(f)) : is displayed on the outside of the compass rose in the same colour as the Selected Heading/Track value. If the selected heading exceeds display range, the bug parks on the side of the compass rose in the direction of the shorter turn to the heading. This item is selectable [S] : nothing is displayed if SelectedHdgTrkIsToDisplay = False or if Heading/Track Reference is set to Track.

• Selected Heading/Track Reference (MCP selection) [S] (req. RH.1.2.2.1 :PFD.HDG(e)) : displays an H when HDG is selected, and a T when TRK is selected.

• Current Heading Pointer (req. RH.1.2.2.1 :PFD.HDG(a)) : indicates current heading. The Current Heading is provided by the Aircraft Model.

• Track Line (req. RH.1.2.2.1 :PFD.HDG(c)) : indicates the current track. The Current Track is provided by the Aircraft Model.

• Heading/Track Reference (req. RH.1.2.2.1 :PFD.HDG(g)) : displays the selected heading/track reference : MAG or TRU. The MAG/TRU reference and the value of the magnetic deviation are defined in a configuration file.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.4 Navigation Display (ND)

The Navigation Display shall represent the aircraft 2D position relative to the environment and to the flight. The ND shall provide two modes of display : Expanded and Centered, as described below. The graphical representation of each mode shall comply to the figures mentioned in the URD [DA3] (req RH.1.2.2.2 :Figure16 and RH.1.2.2.2 :Figure17). These figures are included hereafter to ease the understanding.

Figure 1 - ND Expanded Map Mode

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



Figure 2 - ND Centered Map Mode

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.4.1 Data common to Expanded and Centered Map modes

6.4.1.1 Aircraft State

Except where explicitely mentionned, all the Aircraft State information described below are provided by the aircraft model. • Compass Rose :

The Compass Rose is rotated to show the current Heading (respectively the current Track) at the top of its vertical radius, according to the Heading/Track Reference setting.

• Current Heading Pointer (req. RH.1.2.2.2 :ND.MAP(a)) : The Current Heading Pointer shall point to the aircraft heading on the Compass Rose (Figure 1).

• Current Heading / Track (req. RH.1.2.2.2 :ND.MAP(c)) : The Current Heading / Track indicator shall display the current Track (TRK) or Heading (HDG) in degrees in a numerical way (Figure 1).

• Heading / Track Reference (req. RH.1.2.2.2 :ND.MAP(b)) : The Heading / Track Reference indicator shall display TRK (Track) or HDG (Heading), according to the selection made on the MCP (Figure 1).

• Selected Track Bug (req. RH.1.2.2.2 :ND.MAP(d)) : The Selected Track Bug shall point to the MCP selected track. The selected track bug shall be displayed on the internal side of the compass rose (Figure 1). If selected track exceeds display range, the bug shall park on the side of the compass rose, in the direction of the shorter turn to the track. This bug is not displayed when Heading Reference is set.

• Selected Heading Bug (req. RH.1.2.2.2 :ND.MAP(e)) : The Selected Heading Bug shall indicate the MCP selected heading. The selected heading bug shall be displayed on the outside of the compass rose (Figure 2). If selected heading exceeds display range, the bug shall park on the side of the compass rose, in the direction of the shorter turn to the heading. This bug is not displayed when Track Reference is set.

• Selected Track Line (req. RH.1.2.2.2 :ND.MAP(f)) : A dashed line shall extend from the track bug to the airplane symbol except in the following case : if LNAV, LOC, or ROLLOUT is engaged, the dashed line shall be removed 10 seconds after the selected track bug is moved (Figure 1). This line is not displayed when Heading Reference is set.

• Selected Heading Line (req. RH.1.2.2.2 :ND.MAP(g)) : A dashed line shall extend from the heading bug to the airplane symbol except in the following case : if LNAV, LOC, or ROLLOUT is engaged, the dashed line shall be removed 10 seconds after the selected heading bug is moved (Figure 2). The line is not displayed when Track Reference is set.

• Magnetic / True Reference (req. RH.1.2.2.2 :ND.MAP(h)) :

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The Magnetic / True Reference shall indicate if heading / track is referenced to magnetic north (MAG) or true north (TRU) (Figure 1). By default, the value shall be “magnetic”. This default value shall be adjustable in a configuration file. It shall automatically change to “true” for latitudes greater than 82° (north or south).

• Groundspeed (req. RH.1.2.2.2 :ND.MAP(i)) : The current ground speed (GS) shall be displayed in knots (Figure 2). The current GroundSpeed is provided by the Aircraft Environment module.

• True Airspeed (req. RH.1.2.2.2 :ND.MAP(j)) : The current True Airspeed (TAS) shall be displayed (in knots) above 100 knots (Figure 2).

• Position Trend Vector (req. RH.1.2.2.2 :ND.MAP(k)) : A dashed line shall indicate the predicted position at the end of 30, 60, and 90 seconds intervals. Those predictions shall be based on ground speed and turning rate (in degrees per second) (Figure 1). Each segment shall represent 30 seconds. Selected ND range (as selected on the EFIS Control Panel) shall determine the number of segments displayed according to the following :

• range greater than 20 NM => 3 segments. • range equal to 20 NM => 2 segments. • range equal to 10 NM => 1 segment.

Each 30s segment is split into a non displayed 5s segment and a displayed 25s segment. This enable to visually separate the segments. The displayed segment is a chord of an arc. The angle of the arc is Θ = TurningRate * 25s. The radius of the arc is R = GroundSpeed / TurningRate.

6.4.1.2 Wind

• Wind Direction / Speed (req. RH.1.2.2.2 :ND.MAP(l)) : An indicator shall display wind bearing in degrees (corresponding to the direction the wind comes from) and wind speed in knots (Figure 2). These values shall be read in a configuration file.

• Wind Arrow (req. RH.1.2.2.2 :ND.MAP(m)) : A constant length arrow shall display wind direction with respect to display orientation and Heading/Track reference (Figure 2).

6.4.1.3 Navigation and route

• Navigation Point (req. RH.1.2.2.2 :ND.MAP(n)) : If the « NAV » switch of the EFIS control panel is selected on, all the navigation points defined in the Navigation file shall be indicated, except the published waypoints. Each of such points shall be represented by a symbol, representing the point type (the concentric circles represent NDB, the hexagons with three rectangles represent VOR/DME). This symbol is annotated by the name of the point (Figure 1 & Figure 2).

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



If both « NAV » and « RTE » switches are activated and if a navigation point is also a waypoint of the route, only the following Route-waypoint symbol shall be used (instead of the navigation point symbol) :

VOR/DMENDB orPublished waypoint :

On the aircraft route :

• If the “DATA” switch is also activated, the altitude and estimated time of arrival over the

waypoint shall be indicated near the star symbol.Left & right VOR/ADF Selection (req. RH.1.2.2.2 :ND.MAP(o) & RH.1.2.2.2 :ND.MAP(r)) : When the left (resp. right) reference point selected on a CDU specific page or on the ND screen is a VOR/DME, the string “VOR L” (resp. “VOR R”) is displayed. When this reference point is a NDB, the string “ADF L” (resp. “ADF R”) is displayed (Figure 2).

• Left & right VOR/ADF Ident (req. RH.1.2.2.2 :ND.MAP(p) & RH.1.2.2.2 :ND.MAP(s)) : The left and right Reference Points selected on a CDU specific page or on the ND screen shall be indicated by their identifier (and never by their frequency because the decoding of identifiers shall not be simulated) (Figure 2).

• Left & right VOR DME (req. RH.1.2.2.2 :ND.MAP(q) & RH.1.2.2.2 :ND.MAP(t)) : When the left (resp right) navaid has a DME equipment, the distance to that navaid shall be indicated in Nm (Figure 2).

• Active route (req. RH.1.2.2.2 :ND.MAP(u)) : If the « RTE » switch of the EFIS control panel is selected on, the legs of the active route shall be displayed (Figure 1). Moreover, the waypoints defining the active route are displayed with a star symbology (see above). If “DATA” EFISCP switch is also activated, altitude and estimated time of arrival for each waypoint of the trajectory shall be displayed near the route-waypoint symbol.

• Modified route (req. RH.1.2.2.2 :ND.MAP(v)) : If the « RTE » switch of the EFIS control panel is selected on, the legs of the modified route (if any) shall be displayed with short dashes (Figure 1). The symbology for the representation of the modified route waypoints is the same as for active route.

• Active Waypoint (req. RH.1.2.2.2 :ND.MAP(w)) : If the « RTE » switch of the EFIS control panel is selected on, the active waypoint identifier -representing the waypoint the airplane is currently navigating to- shall be displayed at a fixed location (Figure 2). Active Waypoints are not displayed in User Guidance Mode

• Active Waypoint ETA (Estimated Time of Arrival) (req. RH.1.2.2.2 :ND.MAP(x)) : If the « RTE » switch of the EFIS control panel is selected on, the ETA at the active waypoint, whose calculation shall be based on ground speed and distance only, shall be indicated in Coordinated Universal Time (e.g. 0838.4z = O8h 38min 40s) (Figure 2). ETA = CurrentSimulationTime + ActiveWaypointDistanceToGo / GroundSpeed. The Active Waypoint ETA is not displayed in User Guidance Mode

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Active Waypoint Distance-To-Go (req. RH.1.2.2.2 :ND.MAP(y)) : If the « RTE » switch of the EFIS control panel is selected on, the horizontal distance to the active waypoint shall be indicated in Nm (Figure 2). The Active Waypoint Distance-To-Go is not displayed in User Guidance Mode

6.4.2 Data Specific to Expanded Map mode


• VNAV Path Pointer (req. RH.1.2.2.2 :ND.ExMAP(a)) : The VNAV (Vertical Navigation) Path Pointer shall display vertical deviation from selected VNAV PATH. Scale shall indicate +/- 400 feet deviation (Figure 1). Digital display shall be provided when the pointer indicates more than +/- 400 feet. This item is displayed only when both the engaged pitch mode is VNAV PTH and the aircraft is descending. The aircraft is considered in descent when its vertical speed is lower than a (negative) threshold.. This threshold is defined in a configuration file.

6.4.3 Data Specific to Centered Map mode


• Left & right VOR/ADF pointer (req. RH.1.2.2.2 :ND.CenMAP(a) & RH.1.2.2.2 :ND.CenMAP(b)) : The bearings to (Head) or from (Tail) the left and right reference navigation points shall be indicated. (Figure 2).

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.5 CDTI Indications

The CDTI specifications are derived from RTCA MOPS.

Figure 3 – CDTI Indications

Aircraft information (req. RH.1.2.2.3 : [DA3] Annex CDTI) : In CDTI mode, the ND/CDTI shall display the indications on aircraft as specified in the ASAS Options page (listed between parenthesis). Those informations are described below (the description lists all the possible informations) The graphical representation shall comply to the Figure 3 (req. RH.1.2.2.3 :Figure18). • Aircraft Symbol and position.

Each aircraft position is deduced from its current Latitude and Longitude position in an Earth centered spherical coordinates system. The algorithm used to convert Latitude and Longitude position to X, Y coordinates is given in Annex E.

• Callsign (on/off), SSR code (on/off), altitude (no/relative/absolute), trend of vertical speed : climbing, descending or steady (on/off), and groundspeed in knots/10 (on/off). The SSR code shall be a data tag of four digits. The relative altitude shall be indicated by a data tag of three digits, preceded by a « - » sign if the target aircraft is below own aircraft. The trend of vertical speed shall be indicated by an arrow (climbing vertically, descending vertically or horizontal). Ground speed shall be indicated by a data tag of two digits.

• Velocity vector. It shall extend from the current position of the aircraft up to its extrapolated position at x min, x being chosen in CDU option page. This extrapolation shall be based on current ground speed and track.

Deleted: 3.1

Deleted: (a)

Deleted: Figure 3

Inserted: Figure 3

Deleted: Figure 3




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Past tracks

White points represent the fixed past positions of the aircraft, separated by 30 seconds (The quantity of points is chosen in CDU option page)

Selected aircraft (req. RH.1.2.2.3 : [DA3] Annex CDTI ) : In order to enable the operator to distinguish the symbols of target aircraft from others, those symbols shall be highlighted as specified in the graphical representation . Moreover, the callsign of the first target aircraft that is in extended display mode shall be displayed in text in a fixed location (in the « target aircraft information box »). In this document, we will call this aircraft “main target”. CDTI Display Priority (req. RH.1.2.2.3 : [DA3] Annex CDTI ) : CDTI information shall be brought to the front of ND. The priority display of CDTI information shall follow the list order of selected aircraft (e.g. CDTI information of the aircraft in first position in the list shall be brought to the front). Range Tools (req. RH.1.2.2.3 : [DA3] Annex CDTI) : In order to provide an indication of range with respect to surrounding aircraft, two range tools shall be shown in on the ND. Range Rings shall be drawn centered on the controlled aircraft, with markers placed in a clockface configuration around the ring. Placement and representation of the Range Rings shall be configurable. A Range Ruler with configurable range intervals shall be drawn extending in the direction of flight of the controlled aircraft. ADS-B and TIS-B Representations (req. RH.1.2.2.3 : [DA3] Annex CDTI) : Aircraft representations shall be dependent on the type of message from which the track is derived, ADS-B or TIS-B. ADS-B message information is used as the primary source if both messages are received for a single aircraft. Data Display (req. RH.1.2.2.3 : [DA3] Annex CDTI) : A fixed position data block shall be displayed on the Navigation Display showing information on the selected aircraft. Information in the track data tags and the fixed data block shall be configurable depending on the type of simulation being run and the messages available for the aircraft, ADS-B or TIS-B.

6.6 Enhanced CDTI indications

The CDTI++ concepts mainly result from investigations carried out at EEC. The information to be displayed is described below (Graphical representation shall follow the figures mentioned). This information can be displayed in the ND only if both following conditions are satisfied:

Deleted: 3.1

Formatted

Formatted

Formatted

Formatted

Formatted

Formatted

Deleted: CDTI(b)

Deleted: CDTI(c)




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



A target aircraft is in extended display mode “ON” is chosen for “ASAS IND” in the extended options page of the CDU

It should be noted that the computation of the information to be displayed on CDTI++ is not part of the contract. However, for testing purposes, this information shall be replaced by simulated data. For the calculations concerning CPA and conflict, it shall be assumed that aircraft have uniform movement. • CDTI++ representation :

The types of representation shall be denoted by : absolute, relative (req. RH.1.2.1 :OPT(b)). A menu listing both types of representation shall allow the selection (req. RH1.2.1). However, the type of representation considered shall be « absolute » only (req. RH.1.2.2.4 :CDTI++(a)).

• CDTI++ level of assistance : The levels of assistance are denoted by : baseline, what-if, scale of effect, advisory (req. RH.1.2.1 :OPT(c)) . A menu listing all the levels mentioned shall allow the selection (req. RH1.2.1). However, the levels of assistance considered shall be « baseline » and “what-if” only (req. RH.1.2.2.4 :CDTI++(b)). The ASAS related indications shall be based upon current flight parameters. The ASAS numerical indications shall be located in a “target aircraft information box”, located on the right of the left beacon information box. To provide a “what-if” assistance on the MCP, same indications shall be displayed based on target values of the MCP. This shall be done in an information box located on the right of the target aircraft information box. Format shall be the same (The MCP “what-if” is not correlated to the CDU “what-if” but shall use the same algorithms) (req. RH.1.2.2.4 :WHAT-IF). ASAS/what-if indications shall concern the first aircraft that is in extended mode in the list of target (if any). To distinguish this target from others, we will call it “main target” in this document.

• CDTI++ Display Priority (req. RH.1.2.2.4 :CDTI++(c)) : For CDTI++, the information to display depends on the selected mode of the CDTI++ (none, LSA, VSA, LP or LSK). CDTI++ information shall be brought to the front of CDTI (and therefore ND). The priority display of CDTI++ information shall follow the list order of selected aircraft (e.g. CDTI++ information of the aircraft in first position in the list shall be brought to the front).

• CDTI++ Colours (req. RH.1.2.2.4 :CDTI++(d)) : The following convention for colour shall be applied (and appears in graphics representations) :

• white for extrapolated trajectories • green for current conditions on selected aircraft (e.g. CR, current OD) • yellow for predicted conditions (e.g. CPA) • red for conflict conditions (e.g. TC)

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• CDTI++ Units (req. RH.1.2.2.4 :CDTI++(e)) : The following units shall be used :

• Nm for horizontal distances • Flight level (100*feet) for altitude • Minute for time value

6.6.1 Lateral Separation Assurance

Figure 4 – Lateral Separation Assurance

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



Figure 5 – Lateral Separation Assurance (with conflict) The general layout of the LSA mode shall comply to Figure 4 and Figure 5 (req. RH.1.2.2.3 :Figure19-20) • Closest point of approach (CPA) (req. RH.1.2.2.4 :L-SEP(a)) :

If “Baseline” is selected in the “Assistance Level” menu, the lateral positions at closest point of approach (CPA) of subject and target aircraft shall be indicated graphically.

• Lateral CPA distance (LCPA) (req. RH.1.2.2.4 :L-SEP(b)) : - If “Baseline” is selected in the “Assistance Level” menu, a data tag in the target aircraft information box shall indicate the lateral distance between subject and target aircraft at CPA. - If “What-if” is selected in the “Assistance Level” menu, the same information shall be provided, based on target values of the MCP.

• Time before CPA (TCPA) (req. RH.1.2.2.4 :L-SEP(c)) : - If “Baseline” is selected in the “Assistance Level” menu, and if at least one of the following condition is satisfied :

the extrapolation up to CPA does not show any conflict between subject and target aircraft

“OFF” is chosen for “CONFLICT IND” in the extended options page of the CDU

then, a data tag shall indicate the time before reaching CPA. This tag shall be displayed in the target aircraft information box.

Deleted: 3.1

Deleted: Figure 4

Inserted: Figure 4

Deleted: Figure 4

Deleted: Figure 5

Deleted: Figure 5

Inserted: Figure 5

Deleted: ¶




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



- If “What-if” is selected in the “Assistance Level” menu, the same information shall be provided based on target values of the MCP (the same conditions of display must be satisfied).

• Time before conflict (TC) (req. RH.1.2.2.4 :L-SEP(d)) : - If “Baseline” is selected in the “Assistance Level” menu, and if both following conditions are satisfied :

the extrapolation up to CPA shows a conflict between subject and target aircraft

“ON” is chosen for “CONFLICT IND” in the extended options page of the CDU

then, a data tag shall indicate the time before the conflict. This tag shall be displayed in the target aircraft information box. Moreover, the subject aircraft lateral position at conflict shall be indicated graphically. The rule of definition of a lateral conflict is : lateral distance between aircraft < 5 NM (this threshold value shall be adjustable in a configuration file). - If “What-if” is selected in the “Assistance Level” menu, the same information shall be provided, based on target values of the MCP (the same conditions of display must be satisfied).

• Extrapolated lateral trajectory of target aircraft (req. RH.1.2.2.4 :L-SEP(e)) : If “Baseline” is selected in the “Assistance Level” menu, the lateral trajectory of target aircraft shall extrapolated up to the CPA. This extrapolation shall be represented by a dotted line between the current position of target aircraft and its position at CPA. This trajectory shall be defined as a brokenline, with a configurable number of intermediate points. This definition ensures possible evolution of the extrapolation (for instance, considering a non-uniform motion). For the time being, since the extrapolation supposes uniform motion, only two points are used thus defining a simple line.

Deleted: 3.1

Deleted: ¶

Deleted: ¶




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.6.2 Vertical Separation Assurance

Figure 6 – Vertical Separation Assurance

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



Figure 7 –Vertical Separation Assurance (with conflict) The general layout of the VSA mode shall comply to Figure 6 and Figure 7 (req. RH.1.2.2.3 :Figure21-22). • Altitudes at CPA (req. RH.1.2.2.4 :V-SEP(a)) :

If “Baseline” is selected in the “Assistance Level” menu, the current and CPA altitudes of subject and target aircraft shall be positioned on a scale indicating +/- 50 FL (1 FL = 100 feet) deviation from the subject aircraft current altitude. This scale shall replace the VNAV deviation scale. In a future version, a manual command may allow the user to switch between both displays. To avoid confusion between different scales, the representation of the « CDTI++ Vertical Separation Scale » shall be much longer than the representation of VNAV deviation scale. If an altitude exceeds display range, its pointer shall park on the corresponding end of the scale. To avoid confusion, the pointer shall in this case be only the half of the usual representation :

• the lower half if it is parked on the upper end of the scale, • the upper half if it is parked on the lower end of the scale.

• Relative altitude at CPA (VCPA) (req. RH.1.2.2.4 :V-SEP(b)) : - If “Baseline” is selected in the “Assistance Level” menu, a data tag in the target information box shall indicate the relative altitude at CPA of the target aircraft. A « - » sign shall be displayed if the target aircraft isbelow own aircraft at CPA time. - If “What-if” is selected in the “Assistance Level” menu, the same information shall be provided, based on target values of the MCP.

Deleted: 3.1

Deleted: Figure 6

Inserted: Figure 6

Deleted: Figure 6

Deleted: Figure 7

Deleted: Figure 7

Inserted: Figure 7




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Time before CPA (TCPA) (req. RH.1.2.2.4 :V-SEP(c)) :

Idem req. RH.1.2.2.4 :L-SEP(c).

• Time before conflict (TC) (req. RH.1.2.2.4 :V-SEP(d)) : Idem req. RH.1.2.2.4 :L-SEP(d) with the following rule of definition of a vertical conflict : vertical distance between aircraft < 1000 ft (this threshold value shall be adjustable in a configuration file).

6.6.3 Lateral Passing

Figure 8 – Lateral Passing The general layout of the LP mode shall comply to Figure 8 (req. RH.1.2.2.3 :Figure23) • Oblic distance (OD) (req. RH.1.2.2.4 :L-PASS(a)) :

- If “Baseline” is selected in the “Assistance Level” menu, a data tag shall indicate the current and trend value of the (lateral) oblic distance (OD). The trend value of the oblic distance represents the predicted oblic distance in x minutes (where x has been previously selected on the main target CDU page (“PRED” value)). - If “What-if” is selected in the “Assistance Level” menu, the same information shall be provided, based on target values of the MCP.

• Closure rate (CR) (req. RH.1.2.2.4 :L-PASS(b)) :

Deleted: 3.1

Deleted: Figure 8

Inserted: Figure 8

Deleted: Figure 8

Deleted: ¶




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



- If “Baseline” is selected in the “Assistance Level” menu, a data tag shall indicate the relative closure rate, in knots, for the selected target aircraft. The data tag shall consist of three numeric digits, and a sign character. The closure rate information shall also be represented graphically by a vector emanating from the target aircraft. This vector shall be the projection - on the oblic line - of the instantaneous relative speed of target aircraft. For target aircraft getting closer to own aircraft, the sign character shall be « - » and the corresponding line shall follow the oblic line. For target aircraft moving further away from own aircraft, the sign character shall be « + » and the corresponding line shall be in the oblic line opposite direction. - If “What-if” is selected in the “Assistance Level” menu, the same numerical information shall be provided, based on target values of the MCP.

• Oblic line (req. RH.1.2.2.4 :L-PASS(c)) : - If “Baseline” is selected in the “Assistance Level” menu, a dotted straight line shall bind the target aircraft and own aircraft.

6.6.4 Longitudinal Station Keeping

Figure 9 – Longitudinal Station Keeping

Deleted: 3.1

Deleted: ¶

Deleted: ¶

Deleted: ¶




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The general layout of the LSK mode shall comply to Figure 9 (req. RH.1.2.2.3 :Figure24) • Along track distance (ATD) (req. RH.1.2.2.4 :LS-KEEP(a)) :

- If “Baseline” is selected in the “Assistance Level” menu, a data tag shall indicate the current and trend value of the along track distance (ATD). The trend value of the along track distance represents the predicted along track distance in x minutes (where x has been previously selected on the main target CDU page (“PRED” value)). - If “What-if” is selected in the “Assistance Level” menu, the same information shall be provided, based on target values of the MCP.

• Closure rate (CR) (req. RH.1.2.2.4 :LS-KEEP(b)) : - If “Baseline” is selected in the “Assistance Level” menu, a data tag shall indicate the relative closure rate, in knots, for the selected target aircraft. The data tag shall consist of three numeric digits, and a sign character. The closure rate information shall also be represented graphically by a continuous line emanating from the target aircraft. For target aircraft getting closer to subject aircraft, the sign character shall be « - » and the corresponding line shall follow the along track line (from target aircraft toward subject aircraft). For target aircraft moving away from subject aircraft, the sign character shall be « + » and the corresponding line shall be straight and drawn in the opposite direction. - If “What-if” is selected in the “Assistance Level” menu, the same numerical information shall be provided, based on target values of the MCP.

• Along track line (req. RH.1.2.2.4 :LS-KEEP(c)) : - If “Baseline” is selected in the “Assistance Level” menu, a dotted line shall bind the target aircraft and own aircraft, representing the track the subject aircraft has to follow. It shall be tangent to both velocity vectors.

6.7 EFIS Control Panel

The EFIS Control Panel enables the control of the EFIS components. It shall provide the control functions described below. Graphical representation shall follow the Figure 10. The different HMI controls shall be handled in an intuitive way, using either the direct click method or the press – drag/rotate – release method.

Figure 10 - EFIS Control Panel

Deleted: 3.1

Deleted: Figure 9

Inserted: Figure 9

Deleted: Figure 9

Deleted: ¶

Deleted: ¶¶

Deleted: ¶

Deleted: .

Deleted: Figure 10

Inserted: Figure 10

Deleted: Figure 10




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



1. PFD (req. RH.1.2.3 :EFISCP(a)) - No control functions. 2. ND (req. RH.1.2.3 :EFISCP(b)) • Selection of the range (i.e. zooming and unzooming) :

A ND range selector shall allow to select one of the following ND range scale : 10, 20, 40, 80, 160, or 320 nautical miles (from subject aircraft to compass rose, along the track line).

• Selection of the mode : A ND Center (CTR) switch shall allow to alternate between centered map (i.e. entire compass rose) and expanded map (i.e. quart of compass rose) displays. Initially (before pushing the switch for the first time), the expanded map is displayed.

• Activation / deactivation of display of flight plan : - A switch (RTE) shall allow to select the display of flight plan, including :

• The active route • All the (visible) waypoints located on the active route with the symbology described in 6.4.1.3. • The active waypoint and relating information (ETA and Distance-To-Go)

A second push shall remove the information. - Another switch (DATA) shall allow the display, on the ND, of altitude and estimated time of arrival for each way-point of the trajectory.

• Activation / deactivation of display of navaids : A switch (NAV) shall allow to select the display of all the navigation aids with the symbology described in 6.4.1.3. A second push shall remove the information (except those located on the active route if the RTE switch is on). This switch indifferently applies on both high and low altitude navigation aids (whatever the selected range is). The labels of the RTE, DATA and NAV switch are yellow when the mode is active and white otherwise

• Unused buttons shall be set as “spare” (i.e. no label and no interaction).

3. CDTI/CDTI++ (req. RH.1.2.3 :EFISCP(d)) • Selection of the mode :

A CDTI/CDTI++ mode selector shall allow to select a mode for the main target (if any), according to the type of problem to be delegated. The modes are : OFF (i.e. CDTI/CDTI++ not activated), CDTI (only CDTI information are displayed), LSA (Lateral Separation Assurance), VSA (Vertical Separation Assurance), LP (Lateral Passing), LSK (Longitudinal Station Keeping).

• Selection of the trend value : When the main target is in LP or LSK mode, predicted conditions shall be displayed depending on the desired trend value (i.e. the predicted value in the future). A CDTI++

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



prediction selector (PREDICT.) shall allow to select one of the following prediction times : 30 seconds, 1 minute, 2 minutes, 5 minutes.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.8 Mode Control Panel (MCP)

The following controls are available : speed, heading, vertical speed, altitude (req. RH.1.2.4 :MCP(d)). The selectors are used to enter target values without guiding the aircraft (HOLD mode) (req. RH.1.2.4 :MCP(b)) or when the aircraft is manoeuvring to reach a target value (SEL mode, req. RH.1.2.4 :MCP(c)) (req. RH.1.2.4 :MCP(h)). The two mode SEL and HOLD are exclusive (req. RH.1.2.4 :MCP(e)) and it is possible to switch to one mode whatever the current mode (req RH.1.2.4 :MCP(f)). When switching from SEL mode to HOLD mode, the aircraft is stabilised along the current value or along the value predicted in 10 seconds (req. RH.1.2.4 :MCP(i)).

6.8.1 Autopilot flight director system controls

• A/P lights : illuminated when the ADFS Status is set to A/P. • Left flight director switch : activates the flight director steering indications on the PFD.

6.8.2 Autopilot flight director IAS/Mach controls

• IAS/Mach Window : displays the speed selected by the IAS/MACH selector. The display range is 100-399 KIAS, 0.40-0.95 Mach. The selected speed is displayed as the PFD selected speed. During climb, automatically changes from IAS to MACH at 0.84 mach. During descent, automatically changes from MACH to IAS at 310 KIAS.

• IAS/MACH Reference Switch : Push : alternately changes the IAS/MACH window between IAS and Mach displays (Mach must be 0.4 or greater to switch from IAS to Mach).

• IAS/MACH Selector : sets the speed in the IAS/MACH window and on the PFD as the selected speed : to increase (resp. decrease) the speed, click the right (resp. left) border of the selector.

• Speed HOLD switch : Push : the aircraft maintains the present speed. The light is illuminated

• Speed SEL switch : Push : the airplane accelerates or decelerates to reach the target speed

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.8.3 Autopilot flight director roll and pitch controls

• LNAV button : is illuminated when LNAV is engaged. (req. RH.1.2.4 :MCP(a)). Press : re-engage LNAV

• VNAV button : is illuminated when VNAV is. (req. RH.1.2.4 :MCP(a)). Press : re-engage both LNAV and VNAV

6.8.4 Autopilot flight director heading/track controls

• HDG/TRK reference switch : Push – alternately changes the HDG/TRK window, PFD and ND selected heading/track references between heading and track. Also changes the PFD roll mode, if the HDG or TRK mode is engaged. The HDG/TRK reference acts simultaneously on all the cockpits related to the same aircraft.

• Heading/Track window : displays the selected heading or track. The selected heading/track is displayed on the PFD and ND.

• Heading/Track hold switch : Push : selects HDG or TRK HOLD as the roll mode. The light is illuminated. The airplane holds the present heading or track.

• Heading/Track select switch : Push : selects HDG or TRK SEL as the roll mode. The airplane turns to the heading or track selected in the heading/track window. Click the right (resp. left) border of the selector to increase (resp. decrease) heading or track

6.8.5 Autopilot flight director vertical speed and flight path angle controls

• Vertical Speed/Flight path angle Window : displays the selected vertical speed in 100 fpm increments or the selected flight path angle in 0.1 degrees increments. The display range is V/S : –8000 to +6000 fpm, FPA : -9.9 to +9.9°. The selected vertical speed or flight path angle is displayed on the PFD.

• V/S-FPA reference switch : Push – alternately changes the Vertical Speed window, PFD and ND displays between vertical Speed (V/S) and Flight Path Angle (FPA). The V/S-FPA reference switch acts simultaneously on all the cockpits related to the same aircraft.

• V/S switch : Push : engages V/S or FPA as the pitch mode. Display the current vertical speed or flight path angle in the V/S-FPA window

• V/S-FPA Selector : sets the vertical speed or flight path angle in the V/S-FPA window and on the PFD.

6.8.6 Autopilot flight director altitude controls

• Altitude Window : displays the selected altitude. The range is 0-50000 ft.

• Altitude Selector : sets the altitude in the altitude window and on the PFD. Click the left (resp. right) border of the selector to decrease (resp. increase) the selected altitude

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



Push : the airplane begins a climb or descent toward the altitude window altitude. Once the actual value reaches the target value, the mode is switched automatically to HOLD (req RH.1.2.4 :MCP(g)).

• Altitude hold switch : Push : engages ALT as the pitch mode. The light is illuminated. The airplane holds the altitude when the switch was pushed.

6.9 Control Display Unit

Figure 11 - CDU panel

The general layout of fthe CDU shall look like Figure 11. The buttons drawn on this panel are inoperative except those with a label. For using this panel, the actual keyboard of the computer shall be used. (req. RH.1.2.5 :Figure35). The MENU button displays the root menu of the CDU. From this page, one can access to the ASAS main page, the beacons page and the route legs page. The NEXT PAGE and PREV PAGE buttons allow scrolling through CDU pages. The DEL button writes CLR in the scratchpad when pressed. The EXEC button is used to validate route modifications.

Deleted: 3.1

Deleted: 11

Inserted: 11

Deleted: 11

Deleted: Figure 11

Deleted: Figure 11

Inserted: Figure 11




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The CDU screen can display 14 lines x 24 columns. Two buttons are associated to each of the 6 principal lines (one to the left and one to the right). The last line is called “scratchline”. It is linked to the keyboard. The scratchline is used as input buffer and displays any printable character hit on the keyboard. The entered string is validated by a click on any left CDU button. This validation send the string for processing and clears the scratchline. The scratchline is also used as output buffer and displays the eventual errors messages generated by the processing. Such messages may be stacked. Only the most recent message is displayed. The user have to acknowledge each message with the “Del” key. This action clears the currently displayed message and display the next one, if any (i.e. the message that has been generated just before). The stack size is theoretically unlimited (limited only by the memory available on the machine on which the application runs). If a message has not been acknolewdged, any input entry hides it until the input is validated. For simplification pupose, all the CDUs opened on the same aircraft will be synchronized in term of :

• User inputs

• Information displayed. However, the display options, ASAS mode, display mode, look-ahead, separation standard and “what-if” inputs are specific to each cockpit and are not synchronized.

6.9.1 ASAS Main page

The CDU is able to select a list of up to 10 aircraft among those available. This list is scrollable through PgUp/PgDown keys or PREV PAGE/NEXT PAGE buttons.

A L L T A R G E T S 1 / p

C A L L S G N S S R A S A S C D T I

- A F R 4 3 2 1 / 1 2 3 4 - - - - - - -

F L + 1 1 0 ↓ 3 2 N M G S 3 4 0 k T

- A F R 4 3 2 2 / 1 2 3 5 - - - - - - -

F L + 1 2 0 ↑ 3 7 N M G S 4 4 8 k T

- -

- -

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



- -

- < A L L T R A F F I C O P T I O N S > -

For each target, the left button is used to edit the target in a separated page and the right button is used to set the display mode. The display mode changes in a circular way from none, to reduced then to extended and so on. The 6th button on the left allows access to the aircraft page and the one on the right opens the options page. The following procedure enable to select an aircraft : 1. Input the aircraft callsign and/or SSR code with the keyboard

or click an aircraft on the ND with the mouse (in this case, the callsign and/or SSR code is automatically entered in the scratchline). The item (callsign or SSR) which is not manually entered will be displayed in small font.

2. Press one of the six CDU buttons, corresponding to an empty line (possibly use PgUp or PgDn before).

3. If the corresponding line is free the callsign is displayed and the aircraft is added to the target aircraft list. If there is already a target aircraft at this line, a message « <callsign> is selected » is displayed in the scratchline, indicating that the previously selected aircraft must be deselected before entering the new one. No other processing is performed. If the callsign is unknown a message « Unknown aircraft : <callsign> » is displayed in the scratchline. No other processing is performed.

The following procedure enable to deselect an aircraft : 1. Input of the keyword “CLR “ with the keyboard or press the DEL button. 2. Press the left CDU button corresponding to the callsign to deselect. 3. A confirmation message is displayed on the CDU right column with two options

« confirm » and « cancel ». These options are accessible via two right line select buttons. 4. Press the CDU right button for “ confirm “ : the callsign is removed from the list

or Press the CDU right button for “ cancel “ : the action is aborted and the aircraft remains in the list.

In any case, the confirmation message is cleared. Any other sequence will result in error message.

6.9.2 Target page

This page is displayed when the left button associated with an aircraft is pressed in the ASAS main page or the the Aircraft page

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.9.2.1 LSA mode

A F R 4 3 2 1 / 1 2 3 4 1 / t

R / A L T V D I S T G S C D T I

- F L + 1 1 0 ↓ 3 2 N M 3 4 0 k T E X T -

A S A S

- N O N E ↔ L S A ↔ V S A ↔ L P ↔ L S K L F T -

L / S E P T T G H D G

- 1 0 . 0 N M 5 . 1 M I N 1 1 4 ° R G T -

1 0 . 5 5 . 5 1 3 1

- 8 . 1 5 . 5 1 1 1 -

4 . 5 5 . 5 0 9 1

- 8 . 0 5 . 8 0 5 0 -

5 . 8 1 0 9

- < A L L T A R G E T S O P T I O N S > -

The rank of the target and the number of targets are displayed in the upper right corner of the CDU screen The 1st button on the right adjacent to the string EXT allows modification of the display mode. The 2nd button on the left adjacent to the string LSA allows modification of the ASAS mode. The ASAS mode changes in a circular way from none to LSA, VSA, LP then to LSK and so on. When the mode is none, the separation values are not shown The L/SEP column displays the LCPA values. The TTG column displays the TCPA values. The HDG column displays the heading associated with the separation values. When the MCP HDG/TRK switch is set to TRK, the track is displayed instead The two buttons adjacent to the strings LFT and RGT are used to increment/decrement the heading or track test value of the “what-if” assistance. “What-if” separation values are displayed in cyan on the level of the 3rd button Current separation values are displayed in white on the level of the 4h button. Scale of separations values are displayed in green above and below this line Seperation standard is displayed in magenta beside the 5th button on the left. It can be modified by typing a numerical value with the keyboard then by clicking the button

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



The 6th button on the left allows access to the ASAS main page and the one on the right allows access to the options page

6.9.2.2 VSA mode

A F R 4 3 2 1 / 1 2 3 4 1 / t


- F L + 1 1 0 ↓ 3 2 N M 3 4 0 k T E X T -

A S A S

- N O N E ↔ L S A ↔ V S A ↔ L P ↔ L S K U P -

V / S E P T T G V / S

- F L + 1 0 5 . 1 M I N + 1 4 D O -

+ 2 0 5 . 5 + 1 1

- + 0 9 5 . 5 + 1 3 -

+ 0 1 5 . 5 + 1 9

- + 1 0 5 . 8 + 1 5 -

5 . 8 + 0 9


The V/SEP column displays the VCPA values. The TTG column displays the TCPA values The two buttons adjacent to the strings UP and DO are used to increment/decrement the V/S or FPA test values (depending on the MCP V/S-FPA switch) of the “what-if” assistance. The seperation standard is entered in feet

6.9.2.3 LSK mode

A F R 4 3 2 1 / 1 2 3 4 1 / t


- F L + 1 1 0 ↓ 3 2 N M 3 4 0 k T E X T -

A S A S

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



- N O N E ↔ L S A ↔ V S A ↔ L P ↔ L S K A C C -

A T D / S E P G S / I A S

- 1 0 . 4 N M 3 1 4 / 2 1 4 D E C -

9 . 0 3 1 1 / 2 1 1 P R E D

- 9 . 1 3 1 3 / 2 1 3 2 . 0 -

9 . 0 3 1 1 / 2 1 1

- 1 0 . 0 3 1 5 / 2 1 5 -

3 0 9 / 2 0 9


The ATD/SEP displays the predicted ATD for the assistance lines and the current ADT for the current values line The buttons adjacent to the strings ACC and DEC are used to increment/decrement the aircraft speed (GS, IAS or Mach depending on the LSK manœuvre option and the status of the MCP IAS/Mach switch) The look-ahead is displayed below the string PRED and can be changed by typing a numerical value and by clicking the corresponding button

6.9.2.4 LP mode

A F R 4 3 2 1 / 1 2 3 4 1 / t


- F L + 1 1 0 ↓ 3 2 N M 3 4 0 k T E X T -

A S A S

- N O N E ↔ L S A ↔ V S A ↔ L P ↔ L S K L F T -

O D / S E P H D G

- 1 0 . 4 N M 1 1 4 ° R G T -

9 . 0 1 3 1 P R E D

- 9 . 1 1 1 1 2 . 0 -

9 . 0 0 9 1

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



- 1 0 . 0 0 5 0 -

1 0 9


The OD/SEP column displays the predicted OD for the assistance lines and the current OD for the current values line The buttons adjacent to the strings LFT and RGT are used to increment/decrement the heading or track test values (depending on the MCP HDG/TRK switch) of the “what-if” assistance. The look-ahead is displayed below the string PRED and can be modified like in the LSK mode

6.9.3 Aircraft page

A L L T R A F F I C 1 / p

C A L L S G N S S R A S A S C D T I

- A F R 4 3 2 1 / 1 2 3 4 - - - - - - -

F L + 1 1 0 ↓ 3 2 N M G S 3 4 0 k T

- A F R 4 3 2 2 / 1 2 3 5 - - - - - - -

F L + 1 2 0 ↑ 3 7 N M G S 4 4 8 k T

- -

- -

- -


Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



This page shows all the aircraft visible through ADS-B. The list is sorted by callsign, SSR code or distance according to an option set in the Options page. The display mode can be changed in a circular way (none → reduced → extended) by clicking the right key associated with an aircraft By clicking the left key, the aircraft is set as a target (it appears at the first position of the targets list) and is edited in the Target page The last button on the left allows access to the ASAS main page and the one on the right allows access to the Options page

6.9.4 Options page

O P T I O N S

A C S O R T

- S S R ↔ C L L S G N ↔ D I S T -

S E P C I R C L E A L T I T U D E

- O N ↔ O F F N O ↔ R E L ↔ A B S -

T R G T D S P L

- N O N E ↔ R E D ↔ E X T -

N O N T R G T D S P L

- N O N E ↔ R E D I N C R E M E N T > -

L S K M A N E U V

- I A S / M A C H ↔ G S R E D U C E D > -

- < A L L T A R G E T S E X T E N D E D > -

This page allows : • Selection of the type of sort to be applied to the Aircraft page : by pressing the 1st button

on the left, the type of sort changes in a circular way from SSR → Callsign → Distance • Activation/deactivation of the display of the separation circle around own aircraft

(applicable to the ND/CDTI) by pressing the 2nd button on the left • Selection of the default display mode applicable to the ND/CDTI for target. By pressing

the 3rd button on the left the display mode changes in a circular way from None → Reduced → Extended (default is Extended)

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• Selection of the default display mode applicable to the ND/CDTI for non target traffic. By pressing the 4th button on the left the display mode changes in a circular way from None → Reduced (default is None)

• Selection of manœuvre for LSK (IAS/Mach versus G/S – default is IAS/Mach) by pressing the 5th button on the left

• Selection of the display of altitude applicable to the ND/CDTI. By pressing the 2nd button on the right the altitude display mode changes from No display → Relative → Absolute (default is Relative)

The ASAS main page, Increment page, Reduced options page, Extended options page are accessible from this page

6.9.5 Increment page

I N C R E M E N T

W H A T - I F S C A L E S E P

- -

L S A : H D G

- 2 0 1 5 -

V S A : V S

- 1 0 0 2 0 0 -

L P : H D G

- 1 0 2 0 -

L S K : M A C H

- . 1 . 2 -


This page allows the definition of the increments used in the “what-if” assistance and scale of separations assistance schemes. The increment is set by entering a numerical value with the keyboard and by pressing the appropriate button. The choice of the increment unit (HDG/TRK for LSA and LP, VS/FPA for VSA, IAS/Mach/GS for LSK) is performed on the MCP (except for the IAS/Mach versus GS choice which is defined on the Options page)

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.9.6 Reduced and Extended Options page

R E D U C E D O P T I O N S

S S R V E L V E C T

- O N ↔ O F F 6 0 0 S E C -

C A L L S G N P A S T P O S

- O N ↔ O F F 5 -

G S

- O N ↔ O F F -

V / S T R E N D

- O N ↔ O F F -

- -


E X T E N D E D O P T I O N S

S S R V E L V E C T

- O N ↔ O F F 3 0 S E C -

C A L L S G N P A S T P O S

- O N ↔ O F F 5 -

G S A S A S I N D

- O N ↔ O F F O N ↔ O F F -

V / S T R E N D C O N F L I C T I N D

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



- O N ↔ O F F O N ↔ O F F -

- -


These pages allow activation/deactivation of the items to be displayed on the ND/CDTI (see p15 §6 Definition of reduced and extended display options (unless mentioned, default is off for reduced and on for extended) :)

6.9.7 Beacons page

The CDU enables to select the right or (inclusive) left VOR/NDB beacon displayed in the ND. The following procedure enable to select beacon : 1. Select the Beacons Page from the Menu page if the current page is not the Beacons Page. 2. Input the beacon identfier with the keyboard

or click an beacon on the ND with the mouse (in this case, the identifier is automatically entered in the scratchline).

3. Press either the first top left or top right CDU button, corresponding to left beacon resp. right beacon selection for the ND.

4. If the corresponding column is free the identifier is displayed. If there is already a beacon at this column, a message « <beacon> is selected » is displayed in the scratchline, indicating that the previously selected beacon must be deselected before entering the new one. No other processing is performed. If the beacon is unknown a message « Unknown beacon : <Identifier> » is displayed in the scratchline. No other processing is performed.

The following procedure enable to deselect a beacon : 5. Input of the keyword “CLR “ with the keyboard. 6. Press the left CDU button corresponding to the beacon to deselect. 7. A confirmation message is displayed on the CDU bottom right column with two options

« confirm » and « cancel ». These options are accessible via two right line select buttons. 8. Press the CDU right button for “ confirm “ : the callsign is removed from the list

or Press the CDU right button for “ cancel “ : the action is aborted and the aircraft remains in the list.

In any case, the confirmation message is cleared. Any other sequence will result in error message.

Deleted: 3.1

Deleted: 15

Inserted: 15

Deleted: 17




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.9.8 Route legs page

A C T R T E L E G S 1 / p

1 6 5 ° 3 8 N M

- B T G . 8 1 0 / F L 3 5 0 -

1 6 3 ° 1 9 7 N M

- O E D . 8 1 0 / F L 3 5 0 -

0 9 0 ° 2 4 0 N M

- O A K . 8 1 0 / F L 3 5 0 -

- -

- -

- < E R A S E -

This page shows the active route (i.e all the waypoints starting at the active waypoint). For each waypoint, the waypoint name, course, distance to go, speed and flight level are displayed. For the active waypoint, the course and distance are computed compared to the aircraft position, whereas for the other waypoints they are computed compared to the previous waypoint. All is displayed in white except the active waypoint identifier, speed, fligth level which are in magenta To add a waypoint, type its name or click on the ND (the co-ordinates of the point will be copied to the scratchpad with the format defined page 11.31.15 of the “777 Operations Manual”) and press a left key. The new waypoint will be inserted before the selected button. Waypoint speed and altitude constraints are modified by entering xxx/xxxxx (speed and altitude simultaneously) or /xxxxx (altitude only) in the scratchpad then by pressing a right key To delete a waypoint, type “CLR” or press the DEL button, then press a left key Waypoints temporary added or deleted are displayed in shaded white. When the route is under modification, the title of the page changes to “MOD RTE”, the EXEC light is illuminated and “<ERASE” is displayed on left/bottom

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



Pressing the button corresponding to “<ERASE” cancels all the modifications. Pressing the EXEC button validates them, switch title to “ACT RTE” and extinguishes EXEC light.

6.10 Air Situation Display

The window of the air situation display shall appear when activated through the top-level application ( « Air situation display » button). This window shall comprise a button allowing to close itself. It shall be possible to activate multiple ASD (req. RH.1.3 :ASD(a)).

6.10.1 Contents and representations

The air situation display shall provide a graphical representation of the aircraft flights before and during the execution of the scenario. (req. RH.1.3) When changing the scenario, all ASDs opened shall remain opened (contrary to the cockpits) and shall be updated (scenario files shall be rescanned) (req. RH.1.3 :ASD(a)). The graphical aspect shall approximately follow the figure below.

6.10.1.1 Aircraft representation

(req. RH.1.3 :ASD(i)) The following items shall be displayed for each aircraft : aircraft position, callsign, SSR code, flight level, trend of vertical speed (represented by an arrow), past tracks (fixed past positions of the aircraft separated by 30 seconds), groundspeed (in knots/10), velocity vector, and flight plan. The aircraft labels shall be joined to the corresponding aircraft thanks to a white leading line. The ASAS equipped aircraft shall be notified by a black label border. ASAS equipment (on/off) shall be specified in the scenario file (just like callsign and SSR code). The aircraft status (to be assumed, assumed, transferred, not concerned) shall be indicated by the colour of the label :

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• assumed : white callsign and white label • to be assumed : white callsign and pink label • transferred : mustard color callsign and white label • not concerned : black callsign and black label It shall be possible to put the labels anywhere in the ASD with the mouse (thanks to drag and drop). After a label has been moved, it shall stay at the same position relative to the aircraft symbol.

6.10.1.2 Background and Space reference marks

The Navigation points and navaids contained in the navigation file shall be displayed according to the following representation :

VOR/DME :

NDB :

Published Waypoint:

The airways and sector boundaries shall be displayed as described in “AirwaysFile.txt” and “SectorsFile.txt” (req. RH.1.3 :ASD(e)). When clicking on the ASD, the latitude and longitude position shall be indicated in the status bar (format : N47°15.4 w008°03.4) (req. RH.1.3 :ASD(d)). A moving scale, located in the status bar, shall indicate distances (req. RH.1.3 :ASD(d)).

6.10.1.3 Zoom

(req. RH.1.3 :ASD(b)) Differents types of zoom shall be provided : • Zoom in : shall apply a zoom factor > 1 • Zoom out : shall apply a zoom factor < 1 • Fit to size : shall adapt the zoom so that all objects are visible • Rectangular zoom in : shall let the user drag a rectangle, and zoom in on the view on the

selected rectangle. • Rectangular zoom in : shall let the user drag a rectangle, and zoom out so that the previous

view takes the size of the selected rectangle. ASD zoom shall be a logical zoom : all items (symbols, lines, fonts, …) shall keep the same size when zooming or unzooming.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.10.2 Aircraft contextual menu

A contextual menu shall allow the access to various functionalities by right clicking on a given aircraft in the ASD (note that when clicking on an aircraft symbol, it shall be highlighted). Those functionalities shall be : 1. Opening of a new cockpit window corresponding to the chosen aircraft (req. RH.1.3

:ASD(c)). 2. Display/erasure of the selected aircraft trajectory (req. RH.1.3 :ASD(j)). Trajectories

representation shall follow the following rules : • Routes legs shall be represented as segments linking the different waypoints. • The altitude and the estimated time of arrival over each waypoint shall be indicated under the waypoint name. • When the mouse pointer is on a trajectory, the corresponding waypoints information shall be highlighted

It shall be possible to display multiple trajectories. Initially, no trajectory shall be represented. 3. Marking/unmarking of the chosen aircraft (req. RH.1.3 :ASD(g)). Marking an aircraft

shall display a yellow circle around the symbol. It shall be possible to mark one or more aircraft.

4. Aircraft status change (req. RH.1.3 :ASD(i)).

6.10.3 Configurations

(req. RH.1.3 :ASD(k)) A menu called “Display Options” shall allow access to each of the following configuration windows : 1. Configuration of the display (on/off) for each aircraft status (to be assumed, assumed,

transferred and not concerned). 2. Configuration of the display (on/off) for each type of navaid (published waypoint, VOR,

NDB). 3. Configuration of the length of the velocity vectors (look-ahead : 30s, 1, 3, 5 and 10min). 4. Configuration of the numbers of past positions (from 0 to 10). 5. Configuration of the following items :

- Symbol width - Aircraft labels font size - Waypoints labels font size - Trajectories width and color - Airways width and color - Sector boundaries width and color - Sectors fill color - Velocity vectors width

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



6.10.4 Tools

(req. RH.1.3 :ASD(h)) A tracking tool shall be provided :

– A switch in a menu called “Tools” shall allow to activate/deactivate tracker – If Tracker is on, it shall be possible to attach a line joining :

– (1) one point and the mouse pointer (by dragging from the point) – (2) two points (thanks to drag and drop)

This line shall be red. The corresponding distance and bearing shall be displayed in a status bar.

– In case one of the points is an aircraft (resp. the mouse pointer), it shall be updated to follow the aircraft position (resp. the mouse); line, distance and bearing shall be updated accordingly.

– These items shall remain displayed until Tracker is switched off.

Deleted: 3.1


Formatted: Indent: Left: 0.25",Bulleted + Level: 1 + Aligned at: 0"+ Tab after: 0.25" + Indent at: 0.25"





CS-CISI/CDTI/DSL

Version 4.0 10/05/04



7 SOFTWARE EXTERNAL INTERFACES

7.1 Interface with Other Software

This application software has no specific interface with other software. However, since it is composed of two sub-parts, one which being provided by the EUROCONTROL Experimental Centre, a list of interfacing variable have been given in ANNEX B. This list will be transferred toward the Software Design Document as soon as this document is available.

7.2 Interface with Hardware

There is no specific interface with hardware, except those described in following chapter 8.1.1.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



8 SOFTWARE CONSTRAINTS

8.1 Environment

8.1.1 Hardware Environment

This software shall run on a Personal Computer (PC). It shall be downloadable through Internet.

8.1.2 Software Environment

This software shall be compatible with the following Web Browsers : Netscape 4.05 (req RS.1 :SYSTEM(b) ) Microsoft Explorer 4.0 (req RS.1 :SYSTEM(c) )

This software shall run under the following operating systems : Window 95 (req RS.1 :SYSTEM(d) ) Unix Solaris 2.51 (req RS.1 :SYSTEM(e) ) Unix Solaris 2.6 (req RS.1 :SYSTEM(f) )

This software should also run under Windows NT and HP UX 10.20 (req RS.1 :SYSTEM(g) ).

8.1.3 Development Libraries

This software shall be built on top of the GSDK software library with the graphical display built on top of the ILog JViews library [RS.2]. It is the long-term intention to replace the ILog JViews library with the GSDK AWS library.

8.2 Performances

The Human-Machine Interface shall provide a real-time look and feel on all the HMI components. (req RP.1 :PERFO(a) ). Participating to that goal, it is recommended that the graphical animation on the displays should be smooth and free of flicker. (rec RP.1 :PERFO(b) ). In addition, a visual feedback should be given to the user inputs within 0.1 second (rec RP.1 :PERFO(c) ). In order to simulate the aircraft behaviour in real time (req RP.2), the update rate of the aircraft model’s control loop shall not be greater then 1s. However, these performance requirement and recommendations will be appreciated on a local area network (LAN), since the data transmission rate on Internet is not predictable. Similarly, the performance checks will be done on a PC, with sufficient hardware resources (memory, CPU speed), that doesn’t run any other CPU consuming program.

Deleted: 3.1



Deleted: ¶




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



8.3 Operational Constraints

Not Applicable.

8.4 Quality Characteristics

The quality characteristics of the software concern mainly the design.

Deleted: 3.1




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



9 PROJECT REQUIREMENTS

9.1 Design Requirements

This software shall be written following the design methodology and patterns laid out in the GSDK software library and eDEP projects. The software shall be object-oriented and follow a modular structure that provides flexibility within the software for the purposes of future development and mainainance. The software shall make use of file resources to allow configuration of the application without changing the software. The eDEP GSDK Detailed Design Document contains more information on the resources, patterns and methodologies [DR5].

9.2 Coding Requirements

This software shall be written in Java and HTML (req RS.1 :SYSTEM(a) ).

9.3 Test Requirements

9.3.1 Product Acceptance

Refer to the Software Tests Document [DR3].

9.3.2 Documents Acceptance

The delivered documents are subject to an official acceptance from the customer. This acceptance shall be reflected by the customer’s signature on the front cover page of each accepted document.

Deleted: 3.1


Deleted: There is no specific design requirement.¶However, it is recommended that the software should be designed in such a way to confer to the software the capabilities of evolution & extension.¶This is normally brought by a modular design.¶Anyway, this recommendation will be taken into account in the Software Design Document, [DR2].¶




CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page A-1


ANNEX A. LIST OF REQUIREMENTS Here follows the list of all the requirements mentioned in this document. This list is to be compared with the check-list contained in the 0. Additional explanation is also to be found in that document. Requirements present in this document RD.1.2

DOC(e).......................................................................1, 2 RF.1.1

FILES(a) ..................................................................9, 10 FILES(b) ......................................................................10 FILES(c).......................................................................10

RF.1.2 A/P(a) ...........................................................................19 A/P(b) ............................................................................. 9 A/P(c) ...........................................................................16

RF.1.3 USER(a) ......................................................................... 9 USER(b) ......................................................................... 9 USER(c) .......................................................................15

RF.1.4 ...............................................................9, 11 RH.1.1

TOP(a) .........................................................................11 TOP(b) .........................................................................11 TOP(c)..........................................................................11 TOP(d) .........................................................................11 TOP(e)..........................................................................11 TOP(f) ..........................................................................12 TOP(g) .........................................................................11 TOP(i) ..........................................................................12 TOP(j) ..........................................................................12 TOP(k)..........................................................................21

RH.1.2 ENV(a) .........................................................................22 ENV(b) ....................................12, 13, 15, 18, 19, 22, 23 ENV(c)....................................................................22, 23

RH.1.2.1 OPT(a) ...................................................................12, 23 OPT(b) .............................................................12, 23, 43 OPT(c)..............................................................12, 23, 43

RH.1.2.2.1 Figure1.........................................................................24 Figure10.......................................................................30 Figure11.......................................................................30 Figure12.......................................................................31 Figure13.......................................................................32 Figure14.......................................................................33 Figure15.......................................................................33 Figure2.........................................................................24 Figure3.........................................................................25 Figure4.........................................................................26 Figure5.........................................................................27 Figure6.........................................................................28 Figure7.........................................................................28 Figure8.........................................................................29 Figure9.........................................................................30 PFD.ALT(a) .................................................................30 PFD.ALT(b) .................................................................31 PFD.ALT(c) .................................................................30 PFD.ALT(d) .................................................................31

PFD.ALT(e)................................................................. 31 PFD.ALT(f).................................................................. 31 PFD.ALT(g)................................................................. 31 PFD.ALT(h)................................................................. 31 PFD.ALT(i).................................................................. 31 PFD.ALT(j).................................................................. 31 PFD.ALT(k)................................................................. 32 PFD.ALT(l).................................................................. 32 PFD.ALT(m)................................................................ 32 PFD.ALT(n)................................................................. 32 PFD.ALT(o)................................................................. 32 PFD.ALT(p)................................................................. 32 PFD.ATT(a)................................................................. 27 PFD.ATT(b)................................................................. 27 PFD.ATT(c)................................................................. 27 PFD.ATT(d)................................................................. 28 PFD.ATT(e)................................................................. 28 PFD.ATT(f).................................................................. 28 PFD.ATT(g)................................................................. 28 PFD.ATT(h)................................................................. 28 PFD.ATT(i).................................................................. 28 PFD.FM(a).................................................................. 24 PFD.FM(b).................................................................. 25 PFD.FM(c) .................................................................. 24 PFD.FM(d).................................................................. 25 PFD.FM(e) .................................................................. 25 PFD.FM(f)................................................................... 25 PFD.FM(g).................................................................. 24 PFD.HDG(a)............................................................... 34 PFD.HDG(b)............................................................... 34 PFD.HDG(c) ............................................................... 34 PFD.HDG(d)............................................................... 33 PFD.HDG(e) ............................................................... 34 PFD.HDG(f)................................................................ 34 PFD.HDG(g)............................................................... 34 PFD.SPD(a) ................................................................ 25 PFD.SPD(b) ................................................................ 25 PFD.SPD(c) ................................................................ 26 PFD.SPD(d) ................................................................ 26 PFD.SPD(e) ................................................................ 26 PFD.SPD(f) ................................................................. 26 PFD.SPD(g) ................................................................ 26 PFD.SPD(h) ................................................................ 26 PFD.SPD(i) ................................................................. 26 PFD.SPD(j) ................................................................. 27 PFD.SPD(k) ................................................................ 27 PFD.SPD(l) ................................................................. 27 PFD.SPD(m) ............................................................... 27 PFD.STAT(a)............................................................... 28 PFD.STAT(b)............................................................... 29 PFD.STAT(c)............................................................... 29 PFD.STAT(d)............................................................... 29 PFD.STAT(e)............................................................... 30 PFD.STAT(f)................................................................ 30 PFD.STAT(g)............................................................... 30

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page A-2


PFD.VSPD(a) ..............................................................33 PFD.VSPD(b) ..............................................................33 PFD.VSPD(c) ..............................................................33

RH.1.2.2.2 Figure16.......................................................................35 Figure17.......................................................................35 ND.CenMAP(a) ...........................................................40 ND.CenMAP(b) ...........................................................40 ND.ExMAP(a) .............................................................40 ND.MAP(a)..................................................................37 ND.MAP(b)..................................................................37 ND.MAP(c) ..................................................................37 ND.MAP(d)..................................................................37 ND.MAP(e) ..................................................................37 ND.MAP(f)...................................................................37 ND.MAP(g)..................................................................37 ND.MAP(h)..................................................................37 ND.MAP(i)...................................................................38 ND.MAP(j)...................................................................38 ND.MAP(k) ..................................................................38 ND.MAP(l)...................................................................38 ND.MAP(m) .................................................................38 ND.MAP(n)..................................................................38 ND.MAP(o)..................................................................39 ND.MAP(p)..................................................................39 ND.MAP(q)..................................................................39 ND.MAP(r) ..................................................................39 ND.MAP(s) ..................................................................39 ND.MAP(t)...................................................................39 ND.MAP(u)..................................................................39 ND.MAP(v) ..................................................................39 ND.MAP(w) .................................................................39 ND.MAP(x) ..................................................................40

RH.1.2.2.3 CDTI(a)........................................................................41 CDTI(b)........................................................................42 CDTI(c) ........................................................................42 Figure18.......................................................................41

RH.1.2.2.4 CDTI++(a) ..................................................................43 CDTI++(b) ............................................................43, 68 CDTI++(c) ..................................................................43 CDTI++(d) ..................................................................43 CDTI++(e) ..................................................................44 Figure19-20 .................................................................45 Figure21-22 .................................................................48 Figure23.......................................................................49 Figure24.......................................................................51 L-PASS(a) ....................................................................49 L-PASS(b) ....................................................................49 L-PASS(c).....................................................................50

L-SEP(a) ...................................................................... 45 L-SEP(b) ...................................................................... 45 L-SEP(c) ................................................................45, 49 L-SEP(d) ................................................................46, 49 L-SEP(e) ...................................................................... 46 LS-KEEP(a)................................................................. 51 LS-KEEP(b)................................................................. 51 LS-KEEP(c) ................................................................. 51 V-SEP(a)...................................................................... 48 V-SEP(b)...................................................................... 48 V-SEP(c) ...................................................................... 49 V-SEP(d)...................................................................... 49

RH.1.2.3 EFISCP(a) ................................................................... 52 EFISCP(b) ................................................................... 52 EFISCP(d) ................................................................... 52

RH.1.2.4 MCP(a) ........................................................................ 55 MCP(b) ........................................................................ 54 MCP(c) ........................................................................ 54 MCP(d) ........................................................................ 54 MCP(e) ........................................................................ 54 MCP(f) ......................................................................... 54 MCP(g) ........................................................................ 56 MCP(h) ........................................................................ 54 MCP(i) ......................................................................... 54

RH.1.2.5 CDU(a) ........................................................................ 14 CDU(b) ........................................................................ 14 CDU(c) ........................................................................ 14 CDU(d) ........................................................................ 14 Figure35 ...................................................................... 56

RH.1.2.6 SELECT(a) .................................................................. 14 SELECT(b) .................................................................. 14 SELECT(c)................................................................... 14

RH.1.3...................................................................68 RP.1

PERFO(a).................................................................... 73 PERFO(b).................................................................... 73 PERFO(c) .................................................................... 73

RP.2 ........................................................................9 RS.1

SYSTEM(a) .................................................................. 75 SYSTEM(b) .................................................................. 73 SYSTEM(c) .................................................................. 73 SYSTEM(d) .................................................................. 73 SYSTEM(e) .................................................................. 73 SYSTEM(f) ................................................................... 73 SYSTEM(g) .................................................................. 73

Deleted: 3.1

Deleted: Section Break (Continuous)RD.1.2¶DOC(e) 2¶RF.1.1¶FILES(a) 8¶FILES(b) 9¶FILES(c) 9¶RF.1.2¶A/P(a) 15¶A/P(b) 8¶A/P(c) 13¶RF.1.3¶USER(a) 8¶USER(b) 8¶USER(c) 13¶RF.1.4 8, 9¶RH.1.1¶TOP(a) 10¶TOP(b) 10¶TOP(c) 10¶TOP(d) 10¶TOP(e) 10¶TOP(f) 10¶TOP(g) 10¶TOP(i) 10¶TOP(j) 10¶TOP(k) 17¶RH.1.2¶ENV(a) 18¶ENV(b) 11, 19¶ENV(c) 19¶RH.1.2.1¶OPT(a) 11, 19¶OPT(b) 11, 19, 37¶OPT(c) 11, 19, 38¶RH.1.2.2.1¶Figure1 20¶Figure10 26¶Figure11 26¶Figure12 27¶Figure13 28¶Figure14 29¶Figure15 29¶Figure2 20¶Figure3 21¶Figure4 22¶Figure5 23¶Figure6 24¶Figure7 25¶Figure8 25¶Figure9 26¶PFD.ALT(a) 27¶PFD.ALT(b) 27¶PFD.ALT(c) 27¶PFD.ALT(d) 27¶PFD.ALT(e) 27¶PFD.ALT(f) 27¶PFD.ALT(g) 28¶PFD.ALT(h) 28¶PFD.ALT(i) 28¶


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E

... [2]



CS-CISI/CDT

Version 410/05/04

eCockpit_SSD.doc Software Specification Document Pag


ANNEX B. INTERFACING VARIABLES This annex is to be transferred to the Software Design Document [DR2], when this one will be available. This annex describes the HMI API to be used to control the Cockpit Panel. At this stage of the specification, the interface will be described only by a set of variables given by one sub-part described in the two following tables. The Cockpit Panel displays the following values :

Values needed by the Cockpit HMI (exact variable name)

Type Values Range (unit) Com

EngagedAutothrottleMode Enum {NONE, THR REF, THR, IDLE, HOLD, SPD}

AFDSArmedRollMode Enum {NONE, LOC, ROLLOUT, LNAV}

AFDSEngagedRollMode Enum {NONE, HDG HOLD, HDG SEL, TRK HOLD, TRK SEL, LNAV, LOC, ROLLOUT, TO/GA, ATT}

AFDSArmedPitchMode Enum {NONE, G/S, FLARE, VNAV}

AFDSEngagedPitchMode Enum { NONE, TO/GA, ALT, V/S, FPA, VNAV PTH, VNAV SPD, VNAV ALT, G/S, FLARE, FLCH SPD }

AFDSStatus Enum {NONE, FLT DIR, A/P, LAND2, LAND3, NO AUTOLAND}

SoundSpeed Int [0; +399] (knots) Speed of sound for the invconversion between knots

SelectedSpeed Int [0; +399] (knots) Value of the MCP IAS/M

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04





SelectedSpeedIsToDisplay Enum {False, AsSelValue, AsHoldValue} Respectively indicates thanot be displayed, or shall bother colour.

PredictedAirspeed Int [0; +399] (knots) Predicted Indicated airspe

CurrentAirspeed Int [0; +399] (knots) Current Indicated Airspee

MaximumSpeed Int [0; +399] (knots) Maximum speed

MaximumManeuveringSpeed Int [0 ; + 399] (knots) Maximum manoeuvering

DisplayMaximumManeuveringSpeed

Bool {YES, NO} Maximum maneuvering sp

V1

V2

VR

Int

[0 ; + 399] (knots)

Takeoff reference speeds

DisplayReferenceSpeeds Bool {YES, NO} Display toggle for V1, V2

TrueAirspeed Int [+100; +999] (knots) Current True Airspeed (TA

GroundSpeed Int [0; +999] (knots) Current Ground Speed (G

FlapManeuveringSpeeds (Int; Int)

([0;399] knots ; {0, 1, 5, 15, 20, 25, 30}) Flap maneuvering speed : at whichs the pilot should the next (given) value.

LandingReferenceSpeed Int [0 ; + 399] (knots) VREF

MinimumManeuveringSpeed Int [0 ; + 399] (knots)

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04





MinimumSpeed Int [0 ; + 399] (knots)

SelectedLandingFlap Int {0, 1, 5, 15, 20, 25, 30} Current Landing Flap

BankAngle Float [-180 ; + 180] (degrees)

TurningRate Int [-180 ; + 180] (degrees per second)

CurrentSlipSkidAngle Float (degrees)

PitchLimit Float [-180 ; +180] (degrees)

SlowSpeedThreshold Int [0 ; + 399] (knots) Pitch limit display conditi

PitchAngle Float [-180 ; +180] (degrees)

FDPitchCommand Float [-180 ; +180] (degrees)

FDRollCommand Float [-180 ; +180] (degrees)

FlightPathAngle Float [-9.9 ; +9.9] (degrees)

DriftAngle Float (degrees)

SelectedFlightPathAngle Float [-9.9 ; +9.9] (degrees) Initially issued by Automa

RadioAltitude Int ≤ 2500 (feet)

ILSIsToDisplay Bool {True, False} Indicates if the ILS relateddisplayed.

ILSIdentifier String 5 car. Initially got from trajector

ILSApproachFrontCourse Float (degrees)

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04





ILSDMEDistance Float (NM)

LocalizerPosition Float [-6 ; +6] (dot)

MarkerBeacon Enum {NONE, IM, MM, OM} The transmission of this vthe aircraft above the corr

GlideslopePosition Float [-6 ; +6] (dot)

SelectedAltitude Int [ 0 ; +50000] (feet MSL) Initially issued by Automa

SelectedAltitudeIsToDisplay Enum {False, AsSelValue, AsHoldValue} Respectively indicates thashall not be displayed, or or the other colour.

CurrentAltitude Int [-10000; +50000] (feet MSL)

DisplayAltitudeInMeters Bool {YES, NO} Display toggle

EFISMinimumsReference Enum {RADIO, BARO} Display toggle

AFDSBarometricSource Enum {NONE, L, R}

BarometricSetting Enum {STD, QNH, QFE}

BarometricPreSetting Enum {STD, QNH, QFE}

PressureUnit Enum {IN, HPA}

VerticalSpeed Int [- 8000 ; + 6000] (ft/mn)

SelectedVerticalSpeed Int [- 8000 ; + 6000] (ft/mn) Initially issued by Automaeventually expressed as a

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04





CurrentHeading Float [0 ; 360] (degrees)

CurrentTrack Float [0 ; 360] (degrees)

SelectedTrackHeading Float [0 ; 360] (degrees) Initially issued by AutomaInterpretation as Heading SelectedHeadingTrackRef

SelectedHdgTrkIsToDisplay Enum {False, AsSelValue, AsHoldValue} Respectively indicates thaSelectedTrackHeading shashall be displayed in one o

SelectedHeadingTrackReference Enum {HDG, TRK}

NorthReference Enum {MAG, TRU} The value of this toggle isgreater than 82° (Norh or value TRU is compulsory

LeftBeaconName String 5 char

LeftBeaconType Enum {VOR/DME, NDB}

LeftBeaconBearing Float [0 ; 360] (degrees)

LeftBeaconDistance Float (NM)

RightBeaconName String 5 char

RightBeaconType Enum {VOR/DME, NDB}

RightBeaconBearing Float [0 ; 360] (degrees)

RightBeaconDistance Float (NM)

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04





ActiveWaypointDistanceToGo Float (NM)

CurrentComputedAltitude Int [-10000; +50000] (feet MSL) Current Theoretical AltituVNAV PTH mode of the deviation to be displayed

CurrentLatitude Float [-90 ; 90] (degrees)

CurrentLongitude Float [0 ; 360] (degrees)

TargetAircraftLatitude Float [-90 ; 90] (degrees) For each target aircraft

TargetAircraftLongitude Float [0 ; 360] (degrees) For each target aircraft

TargetAircraftCallsign String 10 char For each target aircraft

TargetAircraftCurrentAltitude Float [-10000; +50000] (feet MSL) For each target aircraft

TargetAircraftTrendVS Enum {STEADY, CLIMB, DESCENT} For each target aircraft

TargetAircraftCurrentGroundSpeed

Int [0; +999] (knots) For each target aircraft

TargetAircraftCurrentHeading Float [0 ; 360] (degrees) For each target aircraft

LSATimeCPA Int (seconds) Time before Closest Point

LSATargetCPALatitude Float [-90 ; 90] (degrees) Extrapolated Target positi

LSATargetCPALongitude Float [0 ; 360] (degrees) Extrapolated Target positi

LSASubjectCPALatitude Float [-90 ; 90] (degrees) Extrapolated Subject posit

LSASubjectCPALongitude Float [0 ; 360] (degrees) Extrapolated Subject posit

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04





LSACPADistance Float (NM) Extrapolated distance at T

LSATimeConflict Int (seconds) Time of Conflict

LSASubjectTCLatitude Float [-90 ; 90] (degrees) Extrapolated Subject posit

LSASubjectTCLongitude Float [0 ; 360] (degrees) Extrapolated Subject posit

VSATimeCPA Int (seconds) Time before Vertical Clos

VSATargetCPAAltitude Int [ -10000 ; +10000] (feet) Extrapolated Target altitud

VSASubjectCPAAltitude Int [ -10000 ; +10000] (feet) Extrapolated Subject altitu

VSACPAVerticalDistance Int [ -10000 ; +10000] (feet) Extrapolated vertical dista

VSATimeVerticalConflict Int (seconds) Time of vertical Conflict

VSASubjectTCLatitude Float [-90 ; 90] (degrees) Extrapolated Subject posit

VSASubjectTCLongitude Float [0 ; 360] (degrees) Extrapolated Subject posit

LPOblicDistance Float (NM) Current Oblic Distance

LPTrendOblicDistance Float (NM) Trend Oblic Distance at L

LPClosureRate Int [-399 ; +399] (knots) Lateral Passing ClosureRa

LSKAlongTrackDistance Float (NM) Current Along Track Dist

LSKTrendAlongTrackDistance Float (NM) Trend Along Track DistanLSKExtrapolationTime

LSKClosureRate Int [-399 ; +399] (knots) Longitudinal Station Keep

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04



The Cockpit Panel provides the following values : Values provided by the Cockpit

HMI (exact variable name) Type Values Range (unit) Comm

AltitudeSelectSwitch Enum {ON, OFF} Reflects the state of the “SEL

SelectedAltitude Int [0 ; +50000] (feet MSL) Value of the MCP altitude w

SelectedIASMACHReference Enum {IAS, MACH}

SelectedSpeed Float [100 ; 399] (knots)

HeadingTrackSelectSwitch Enum {ON, OFF} Reflects the state of the “SEL

SpeedSelectSwitch Enum {ON, OFF} Reflects the state of the “SEL

VSFPASelector Enum {VS, FPA}

SelectedFlightPathAngle Float [-9.9 ; +9.9] (degrees)

SelectedVerticalSpeed Int [- 8000 ; + 6000] (ft/mn) Value of the MCP V/S windo

SelectedTrackHeading Float [0 ; 360] (degrees) Value of the MCP HDG/TRKHeading or Track according tSelectedHeadingTrackRefere

SelectedHeadingTrackReference Enum {HDG, TRK}

NDRangeSelector Int {10, 20, 40, 80, 160, 320, 640} (NM) Default = 80

NDNavSwitch Enum {ON, OFF}

CDTIModeSelector Enum {OFF, CDTI, LSA, VSA, LP, LSK} Default = OFF

LP-LSKExtrapolationTime Enum Int

{30, 60, 120, 300} (seconds)

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04



Values provided by the Cockpit HMI (exact variable name)

Type Values Range (unit) Comm

RightBeaconName String 5 char To allow beacon behaviour s

RightBeaconName String 5 char To allow beacon behaviour s

SelectedAircraftCallsigns List of Strings

10 char each Ordered list of the selected ai

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page C-1


ANNEX C. AIRCRAFT MODEL INTERFACE This annex is to be transferred to the Software Design Document [DR2], when this one will be available. This annex describes the interface between the Aircraft Model (as provided by EEC) and the Main application. The aircraft model starts when the user enters a command on the MCP for the first time. It is initialized by the current parameters of the aircraft taken at the end of the automatic guidance mode : • aircraft position : latitude, longitude and altitude (feet MSL)

• the direction of the trajectory : track and flight path angle

• aircraft speed (IAS)

The software periodically queries the aircraft model for the following parameters : • sound speed (knots)

• predicted airspeed in 10 seconds (knots)

• current indicated airspeed (knots)

• maximum speed (knots)

• maximum maneuvering speed if available (knots)

• takeoff reference speeds V1, V2 and VR if available (knots)

• flap maneuvering speed if available : flap angle (1, 5, 15, 20, 25 or 30) and the corresponding speed limit (knots)

• landing reference speed VREF if available (knots)

• minimum maneuvering speed if available (knots)

• minimum speed (knots)

• selected landing flap if available (1, 5, 15, 20, 25 or 30)

• bank angle (degrees)

• turning rate (degrees per second)

• slip/skid angle (degrees)

• pitch limit if available (degrees)

• pitch angle (degrees)

• flight director pitch command (degrees)

• flight director roll command ([-1 ; +1])

• flight path angle (degrees)

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E





CS-CISI/CDTI/DSL

Version 4.0 10/05/04



• drift angle (degrees)

• radio altitude (feet)

• current altitude (feet MSL)

• vertical speed (ft/mn)

• current heading (degrees)

• current track (degrees)

• current computed altitude (feet MSL)

• current latitude (degrees)

• current longitude (degrees) The aircraft model takes as input : • target speed (knots)

• target heading or track

• target vertical speed or flight path angle or altitude

• wind data

The API must provide the following functions, in Java : public class AircraftModel { // The functions returning an int return 1 on success, 0 on error public int init( float currentLatitude, float currentLongitude, int currentAltitude, float currentTrack, float currentFlightPathAngle, int currentIndicatedAirSpeed, float windBearing, float windSpeed ) ;

// Returns aircraft parameters at dt milliseconds since the last call of the // function, or, if called for the first time, since the call of init() // Returns null on error public AircraftModelOutput getAircraftParameters( int dt ) ; // The aircraft maintains its current speed public int holdSpeed() ; // The aircraft must reach the target speed public int setTargetSpeed( int ias ) ;

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E




CS-CISI/CDTI/DSL

Version 4.0 10/05/04



// The aircraft maintains its current track public int holdTrack() ; // The aircraft must reach the target track public int setTargetTrack( float track ) ; // The aircraft maintains its current heading public int holdHeading() ; // The aircraft must reach the target heading public int setTargetHeading( float heading ) ; // The aircraft maintains its current altitude public int holdAltitude() ; // The aircraft must reach the target altitude public int setTargetAltitude( int altitude ) ; // The aircraft must reach the target vertical speed public int setTargetVerticalSpeed( float vs ) ; // The aircraft must reach the target flight path angle public int setTargetFlightPathAngle( float fpa ) ; // To modify wind data public int setWindBearing( float bearing ); // degrees public int setWindSpeed( float speed ) ; // knots

} Output data of the aircraft model : the class AircraftModelOutput must be defined as a sub-class of the abstract class ComputedAircraftParameters and must implement all its functions public abstract class ComputedAircraftParameters {

// All the functions returning an object (Integer, Float, …) return null if the // corresponding data is not available

public abstract int getSoundSpeed() ; public abstract int getPredictedAirspeed() ; public abstract int getIndicatedAirspeed() ; public abstract int getMaximumSpeed() ; public abstract Integer getMaximumManeuveringSpeed() ; public abstract Integer getV1() ; public abstract Integer getV2() ; public abstract Integer getVR() public abstract FlapManeuveringSpeed getFlapManeuveringSpeed() ; public abstract Integer getLandingReferenceSpeed() ; public abstract Integer getMinimumManeuveringSpeed() ; public abstract int getMinimumSpeed() ; public abstract Integer getSelectedLandingFlap() ; public abstract float getBankAngle() ; public abstract float getTurningRate() ; public abstract float getSlipSkidAngle() ; public abstract Float getPitchLimit() ; public abstract float getPitchAngle() ; public abstract float getFDPitchCommand() ; public abstract float getFDRollCommand() ; public abstract float getFlightPathAngle() ;

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04



public abstract float getDriftAngle() ; public abstract Integer getRadioAltitude() ; public abstract int getCurrentAltitude() ; public abstract int getVerticalSpeed() ; public abstract float getCurrentHeading() ; public abstract float getCurrentTrack() ; public abstract int getCurrentComputedAltitude() ; public abstract float getCurrentLatitude() ; public abstract float getCurrentLongitude() ;

} public class AircraftModelOutput extends ComputedAircraftParameters {

// All the functions returning an object (Integer, Float, …) return null if the // corresponding data is not available

public int getSoundSpeed() ; public int getPredictedAirspeed() ; public int getIndicatedAirspeed() ; public int getMaximumSpeed() ; public Integer getMaximumManeuveringSpeed() ; public Integer getV1() ; public Integer getV2() ; public Integer getVR() public FlapManeuveringSpeed getFlapManeuveringSpeed() ; public Integer getLandingReferenceSpeed() ; public Integer getMinimumManeuveringSpeed() ; public int getMinimumSpeed() ; public Integer getSelectedLandingFlap() ; public float getBankAngle() ; public float getTurningRate() ; public float getSlipSkidAngle() ; public Float getPitchLimit() ; public float getPitchAngle() ; public float getDriftAngle() ; public abstract float getFDPitchCommand() ; public abstract float getFDRollCommand() ; public abstract float getFlightPathAngle() ; public Integer getRadioAltitude() ; public int getCurrentAltitude() ; public int getVerticalSpeed() ; public float getCurrentHeading() ; public float getCurrentTrack() ; public int getCurrentComputedAltitude() ; public float getCurrentLatitude() ; public float getCurrentLongitude() ;

} public class FlapManeuveringSpeed { public int flap_angle ;

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04



public int speed ; }

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04



ANNEX D. CONFIGURATION PARAMETERS This annex lists and describes the configuration parameters use by the Main application.

Configuration Parameters Type Values Range (unit) Comm

General Parameters

MaximumAircraft Int > 0 Indicates the maximum numbcan select on the Top Level P

MaximumCockpits Int > 0 Indicates the maximum numbcan open simultaneously (gloaircraft)

LowRadioAltitudeThreshold Int ≤ 2500 (feet) For localizer & glideslope fla

LocalizerDeviationThreshold Float [-6 ; +6] (dot) For localizer flashing display

GlideslopeDeviationThreshold Float [-6 ; +6] (dot) For glideslope flashing displa

ClimbDescentThreshold Int [0 ; 5000] (feet) Threshold used to detect climadjusted in conjunction with steps.

EarthRadius Int (NM) Earth Radius in a spherical eaconvert Lat-Long into x-y

VelocityVectorExtrapolationTime Int [0 ; 5] (minutes) Extrapolation extent for the daircraft velocity vectors

LSAConflictThreshold Int [0 ; 20] (NM) Lateral conflict threshold val

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04




between aircraft)

VSAConflictThreshold Int [0 ; 5000] (ft) Vertical conflict threshold vabetween aircraft)

Scenario Parameters

MinimumRadioAltitude Int [0 ; 5000] (feet AGL) Same for all airports of the sc

ApproachMinimumAltitude Int [-10000;+50000] (feet MSL) Same for all airports of the sc

AirportAltitude Int [0 ; 5000] (feet ASL) To convert between QFE and

QNHValue Int [0 ; 2000] (hPa) To convert between STD and

TransitionAltitude Int [0; +50000] (feet ASL) Barometric setting display co

MagneticDeviation Float [-10 ; +10] (degrees) positive east

WindBearing Float [0 ; 360] (degrees) Constant for the duration of t

WindSpeed Int [0 ; + 399] (knots) Constant for the duration of t

Cockpit Parameters

DisplayMaximumManeuveringSpeed

Bool {YES, NO} Maximum maneuvering spee

DisplayReferenceSpeeds Bool {YES, NO} Display toggle for V1, V2, V

DisplayAltitudeInMeters Bool {YES, NO} Display toggle

EFISMinimumsReference Enum {RADIO, BARO} Display toggle

BarometricSetting Enum {STD, QNH, QFE}

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDT

Version 410/05/04




PressureUnit Enum {IN, HPA}

NorthReference Enum {MAG, TRU} The value of this toggle is igngreater than 82° (Norh or Souvalue TRU is compulsory.

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04

eCockpit_SSD.doc Software Specification Document Page E-1


ANNEX E. COORDINATE CONVERSIONS /************************************************************************* * * routines to calculate spherical lat/lon values * thanks Steve * ************************************************************************/ #include <math.h> #include "LatLon.H" #include "GlobalDefs.h" // function to calculate distance and bearing of one point from another // on the earth (thanks Steve) //------------------------------------------------------------------------- static void ValidateArcDomain(double & val) { if ( val < -1.0 ) val = -1.0; if ( val > 1.0 ) val = 1.0; } //------------------------------------------------------------------------- void GetDistanceBearing(double FromLat, double FromLon, double ToLat, double ToLon, float * Distance, float * Bearing) { // calculate values relevant to spherical triangle formulae double DeltaLong = (ToLon - FromLon)/Radians; double CosCob = sin((double) ToLat/Radians); double SinCob = cos((double) ToLat/Radians); double CosCoa = sin((double) FromLat/Radians); double SinCoa = cos((double) FromLat/Radians); double CosAcb = cos(DeltaLong); double SinAcb = sin(DeltaLong); // apply spherical cosine rule to get angle subtended at centre of earth double CosAob = CosCoa*CosCob + SinCoa*SinCob*CosAcb; ValidateArcDomain (CosAob); double Aob = acos(CosAob); double SinAob = sin(Aob); if(SinAob == 0.0) // i.e. points coincide { *Distance = 0.0; *Bearing = 0.0; } else { *Distance = EarthRadius*Aob; // in nautical miles // use sine rule to find sine of departure bearing double SinCab = SinCob*SinAcb/SinAob; ValidateArcDomain(SinCab); // check for bearing > 90 using cosine rule if(CosCob - CosCoa*CosAob < 0.0) { *Bearing = 180.0 - Radians*asin( SinCab ); } else

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04



{ *Bearing = Radians*asin( SinCab ); } } } //------------------------------------------------------------------------- void GetLatLon( double FromLat, double FromLon, float Distance, float Bearing, double* ToLat, double* ToLon ) { double SinCoa = cos( (double) FromLat/Radians ); double CosCoa = sin( (double) FromLat/Radians ); double Aob = Distance/EarthRadius; double CosAob = cos( Aob ); double SinAob = sin( Aob ); double CosCab = cos( (double) Bearing/Radians ); double SinCab = sin( (double) Bearing/Radians ); // Applying the spherical cosine rule to find the new latitude double CosCob = CosCoa*CosAob + SinCoa*SinAob*CosCab; ValidateArcDomain (CosCob); double Cob = acos ( CosCob ); double SinCob = sin (Cob); if ( SinCob == 0.0 ) { // ie. the latitude is at the north or south pole if( CosCob > 0.0 ) { // North pole *ToLat = 90.0; *ToLon = FromLon; } else { // South pole *ToLat = -90.0; *ToLon = FromLon; } } else { // applying the spherical sine rule to find the change of longitude double SinAcb = SinAob*SinCab/SinCob; ValidateArcDomain ( SinAcb ); // check to see if the angle magnitude is greater than 90.0 degrees // derived from cosine rule if ( CosAob - CosCob*CosCoa < 0.0 ) { *ToLon = FromLon + 180.0 - Radians*asin(SinAcb); } else { *ToLon = FromLon + Radians*asin (SinAcb); } // The latitude of the point = 90.0 - COB // the change of longitude is ACB *ToLat = 90.0 - Radians*Cob; } }

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04



//------------------------------------------------------------------------- void GetXYFromLatLon( double Lat, double Lon, double CentreLat, double CentreLon, double* X, double* Y ) { // this is a gnomic mapping which has the property of mapping // great circle arcs to straight lines. double Z; double TempZ; double lX, lY ; // first calculate sines and cosines for point double SinLat = sin(Lat/Radians); double CosLat = cos(Lat/Radians); double SinLon = sin(Lon/Radians); double CosLon = cos(Lon/Radians); // then form unit vector to point from earths centre lY = SinLat; lX = CosLat*SinLon; Z = CosLat*CosLon; // now set Sines and Cosines for reference; double SinRefLat = sin(CentreLat/Radians); double CosRefLat = cos(CentreLat/Radians); double SinRefLon = sin(CentreLon/Radians); double CosRefLon = cos(CentreLon/Radians); // Rotate vector around North/South axis TempZ = lX *SinRefLon + Z*CosRefLon; lX = lX *CosRefLon - Z*SinRefLon; // Rotate vector about West/East axis Z = lY *SinRefLat + TempZ*CosRefLat; lY = lY *CosRefLat - TempZ*SinRefLat; // finally project the point onto tangent plane lX *= EarthRadius/Z; lY *= EarthRadius/Z; *X = lX; *Y = lY; } //------------------------------------------------------------------------- void GetLatLonFromXY( double X, double Y, double CentreLat, double CentreLon, double* Lat, double* Lon) { // inverse of the gnomic mapping above double norm; double Z; double TempZ, SaveX, SaveY; SaveX = X; SaveY = Y; // first project point back onto a unit sphere

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04



//printf( " %f %f \n",X,Y); X /= EarthRadius; Y /= EarthRadius; Z = 1.0; norm = sqrt(X*X + Y*Y + Z*Z); X /= norm; Y /= norm; Z /= norm; // now set Sines and Cosines for reference; double SinRefLat = sin(CentreLat/Radians); double CosRefLat = cos(CentreLat/Radians); double SinRefLon = sin(CentreLon/Radians); double CosRefLon = cos(CentreLon/Radians); // Rotate vector about West/East axis TempZ = Z*CosRefLat - Y*SinRefLat; Y = Z*SinRefLat + Y*CosRefLat; // Rotate vector around North/South axis Z = TempZ*CosRefLon - X*SinRefLon; X = TempZ*SinRefLon + X*CosRefLon; // map unit vector back to spherical coordinates *Lat = Radians*asin(Y); *Lon = Radians*atan2(X,Z); X = SaveX; Y = SaveY; } ComputeCPA() { // Attention : les unités sont supposées homogènes // On utilise une distance "elliptique" en ramenant // les séparations verticale et horizontale const double Rho = LateralSeparation / VerticalSeparation; // Les opérations sur Vector3D = (X, Y, Z) sont des opérations // classiques (le "*" correspondant au produit scalaire) Vector3D relativePositionE = ownPosition - intruderPosition; Vector3D relativeVelocityE = ownVelocity - intruderVelocity; relativePositionE.Z *= Rho; relativeVelocityE.Z *= Rho; if (norm(relativeVelocityE) < Epsilon) { timeCPA = 0; ownPositionCPA = ownPosition; intruderPositionCPA = intruderPosition; } else { timeCPA = - (relativePositionE * relativeVelocityE) / (relativeVelocityE * relativeVelocityE) ownPositionCPA = ownPosition + (ownVelocity * timeCPA); intruderPositionCPA = intruderPosition + (intruderVelocity * timeCPA);

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E



CS-CISI/CDTI/DSL

Version 4.0 10/05/04



} // Valeur de separation verticale au CPA vertCPA = ownPositionCPA.Z - intruderPositionCPA.Z; // Valeur de separation laterale au CPA latCPA = norm(ownPositionCPA.X - intruderPositionCPA.X, ownPositionCPA.Y - intruderPositionCPA.Y); // un exemple simple de calcul du point de conflit à partir du CPA if (latCPA < LateralSeparation) and (vertCPA < VerticalSeparation) { for (timeCP = timeCPA ; timeCP = 0 ; time -= timeStep) { ownPositionCP = ownPosition + (ownVelocity * timeCP); intruderPositionCP = intruderPosition + (intruderVelocity * timeCP) vertCP = ownPositionCP.Z - intruderPositionCP.Z; latCP = norm(ownPositionCP.X - intruderPositionCP.X, ownPositionCP.Y - intruderPositionCP.Y); if not ((latCP < LateralSeparation) and (vertCP < VerticalSeparation)) break; } } }

Deleted: 3.1


Deleted: E

Inserted: E

Deleted: E

Inserted: E

Deleted: E

Page v: [1] Deleted Tim Cooper 5/10/2004 11:01 AM

1 Scope 1 1.1 Identification 1 1.2 Document Description 1 1.3 Terminology 1 1.4 Requirement Traceability 2 2 Applicable and Related Documents 3 2.1 Applicable Documents 3 2.2 Related Documents 3 3 Definitions and Abbreviations 4 3.1 Definitions 4 3.2 Abreviations 5 4 General Description 7 4.1 Context 7 4.2 Software Objectives 7 4.3 Architecture 8 5 Fonctional Specification 10 5.1 Simulation of Aircraft Flights 10 5.1.1 Initialisation files 10 5.1.2 ADS-B 12 5.2 Top Level Application 13 5.3 Cockpit Panel 14 5.4 Primary Flight Display (PFD) 14 5.5 Navigation Display (ND) 14 5.6 EFIS Control Panel 15 5.7 Mode Control Panel (MCP) 16 5.8 Control Display Unit (CDU) 16 5.9 Air Situation Display 18 5.10 Aircraft Model module 18 5.11 Autopilot Logic module 18 5.12 Aircraft Environment module 20 5.12.1 Navaids related data 21 5.12.2 Aircraft related data 21 5.13 Trajectory Manager module 22 6 Man-Machine Interface 24 6.1 Top Level Application 24 6.2 Cockpit Panel 25 6.3 Primary Flight Display 27 6.3.1 PFD Flight Mode Annunciation (FMA) 27 6.3.2 PFD Airspeed Indications 28 6.3.3 PFD Reference Speeds 30 6.3.4 PFD Attitude Indications 31 6.3.5 PFD Steering Indications [S] 32 6.3.6 PFD Radio Altitude Indications 32 6.3.7 PFD Instrument Landing System (ILS) 33 6.3.8 PFD Altitude Indications 34 6.3.9 PFD Landing Altitude/Minimum Indications 35 6.3.10 PFD Barometric Indications [S] 36 6.3.11 PFD Vertical Speed Indications 37 6.3.12 PFD Heading/Track Indications 38

6.4 Navigation Display (ND) 40 6.4.1 Data common to Expanded and Centered Map modes 42 6.4.2 Data Specific to Expanded Map mode 45 6.4.3 Data Specific to Centered Map mode 46 6.5 CDTI Indications 46 6.6 Enhanced CDTI indications 48 6.6.1 Lateral Separation Assurance 49 6.6.2 Vertical Separation Assurance 53 6.6.3 Lateral Passing 56 6.6.4 Longitudinal Station Keeping 58 6.7 EFIS Control Panel 59 6.8 Mode Control Panel (MCP) 63 6.8.1 Autopilot flight director system controls 63 6.8.2 Autopilot flight director IAS/Mach controls 63 6.8.3 Autopilot flight director roll and pitch controls 64 6.8.4 Autopilot flight director heading/track controls 64 6.8.5 Autopilot flight director vertical speed and flight path angle controls 64 6.8.6 Autopilot flight director altitude controls 65 6.9 Control Display Unit 66 ASAS Main page 68 6.9.2 Target page 70 6.9.3 Aircraft page 74 6.9.4 Options page 75 6.9.5 Increment page 77 6.9.6 Reduced and Extended Options page 78 6.9.7 Beacons page 79 6.9.8 Route legs page 80 6.10 Air Situation Display 82 6.10.1 Contents and representations 82 6.10.2 Aircraft contextual menu 85 6.10.3 Configurations 85 6.10.4 Tools 86 7 Software External Interfaces 87 7.1 Interface with Other Software 87 7.2 Interface with Hardware 87 8 Software Constraints 88 8.1 Environment 88 8.1.1 Hardware Environment 88 8.1.2 Software Environment 88 8.2 Performances 88 8.3 Operational Constraints 89 8.4 Quality Characteristics 89 9 Project Requirements 90 9.1 Design Requirements 90 9.2 Coding Requirements 90 9.3 Test Requirements 90 9.3.1 Product Acceptance 90 9.3.2 Documents Acceptance 90 ANNEX A. List of Requirements 1 ANNEX B. Interfacing Variables 1

ANNEX C. Aircraft Model Interface 1 ANNEX D. Configuration parameters 1 ANNEX E. Coordinate Conversions 1

Page 2: [2] Deleted Tim Cooper 5/11/2004 10:27 AM

Section Break (Continuous)RD.1.2 DOC(e) ................................................... 2 RF.1.1 FILES(a) ................................................. 8 FILES(b) ................................................. 9 FILES(c) ................................................. 9 RF.1.2 A/P(a) ................................................... 15 A/P(b) ..................................................... 8 A/P(c) ................................................... 13 RF.1.3 USER(a).................................................. 8 USER(b) ................................................. 8 USER(c)................................................ 13 RF.1.4 ................................................. 8, 9 RH.1.1 TOP(a) .................................................. 10 TOP(b).................................................. 10 TOP(c) .................................................. 10 TOP(d).................................................. 10 TOP(e) .................................................. 10 TOP(f)................................................... 10 TOP(g).................................................. 10 TOP(i)................................................... 10 TOP(j)................................................... 10 TOP(k).................................................. 17 RH.1.2 ENV(a) ................................................. 18 ENV(b) ........................................... 11, 19 ENV(c) ................................................. 19 RH.1.2.1 OPT(a) ............................................ 11, 19 OPT(b).......................................11, 19, 37 OPT(c) .......................................11, 19, 38 RH.1.2.2.1 Figure1.................................................. 20 Figure10................................................ 26 Figure11................................................ 26 Figure12................................................ 27 Figure13................................................ 28 Figure14................................................ 29 Figure15................................................ 29 Figure2.................................................. 20 Figure3.................................................. 21 Figure4.................................................. 22 Figure5.................................................. 23

Figure6 ..................................................24 Figure7 ..................................................25 Figure8 ..................................................25 Figure9 ..................................................26 PFD.ALT(a) ..........................................27 PFD.ALT(b) ..........................................27 PFD.ALT(c) ..........................................27 PFD.ALT(d) ..........................................27 PFD.ALT(e) ..........................................27 PFD.ALT(f) ...........................................27 PFD.ALT(g) ..........................................28 PFD.ALT(h) ..........................................28 PFD.ALT(i) ...........................................28 PFD.ALT(j) ...........................................28 PFD.ALT(k) ..........................................28 PFD.ALT(l) ...........................................28 PFD.ALT(m) .........................................28 PFD.ALT(n) ..........................................29 PFD.ALT(o) ..........................................29 PFD.ALT(p) ..........................................29 PFD.ATT(a) ..........................................23 PFD.ATT(b) ..........................................23 PFD.ATT(c) ..........................................24 PFD.ATT(d) ..........................................24 PFD.ATT(e) ..........................................24 PFD.ATT(f) ...........................................24 PFD.ATT(g) ..........................................24 PFD.ATT(h) ..........................................24 PFD.ATT(i) ...........................................24 PFD.FM(a) ............................................20 PFD.FM(b) ............................................21 PFD.FM(c) ............................................20 PFD.FM(d) ............................................21 PFD.FM(e) ............................................21 PFD.FM(f).............................................21 PFD.FM(g) ............................................20 PFD.HDG(a)..........................................30 PFD.HDG(b) .........................................30 PFD.HDG(c)..........................................30 PFD.HDG(d) .........................................30 PFD.HDG(e)..........................................30 PFD.HDG(f) ..........................................30 PFD.HDG(g) .........................................30 PFD.SPD(a)...........................................21 PFD.SPD(b)...........................................21 PFD.SPD(c)...........................................22

PFD.SPD(d) .......................................... 22 PFD.SPD(e) .......................................... 22 PFD.SPD(f)........................................... 22 PFD.SPD(g) .......................................... 22 PFD.SPD(h) .......................................... 23 PFD.SPD(i) ........................................... 23 PFD.SPD(j) ........................................... 23 PFD.SPD(k) .......................................... 23 PFD.SPD(l) ........................................... 23 PFD.SPD(m) ......................................... 23 PFD.STAT(a)........................................ 25 PFD.STAT(b)........................................ 25 PFD.STAT(c)........................................ 25 PFD.STAT(d)........................................ 26 PFD.STAT(e)........................................ 26 PFD.STAT(f) ........................................ 26 PFD.STAT(g)........................................ 26 PFD.VSPD(a)........................................ 29 PFD.VSPD(b) ....................................... 29 PFD.VSPD(c)........................................ 29 RH.1.2.2.2 Figure16................................................ 31 Figure17................................................ 31 ND.CenMAP(a) .................................... 36 ND.CenMAP(b) .................................... 36 ND.ExMAP(a) ...................................... 36 ND.MAP(a)........................................... 33 ND.MAP(b) .......................................... 33 ND.MAP(c)........................................... 33 ND.MAP(d) .......................................... 33 ND.MAP(e)........................................... 33 ND.MAP(f) ........................................... 33 ND.MAP(g) .......................................... 33 ND.MAP(h) .......................................... 34 ND.MAP(i) ........................................... 34 ND.MAP(j) ........................................... 34 ND.MAP(k) .......................................... 34 ND.MAP(l) ........................................... 34 ND.MAP(m) ......................................... 34 ND.MAP(n) .......................................... 34 ND.MAP(o) .......................................... 35 ND.MAP(p) .......................................... 35 ND.MAP(q) .......................................... 35 ND.MAP(r) ........................................... 35 ND.MAP(s)........................................... 35 ND.MAP(t) ........................................... 35 ND.MAP(u) .......................................... 35 ND.MAP(v) .......................................... 35 ND.MAP(w) ......................................... 35 ND.MAP(x) .......................................... 35

RH.1.2.2.3 CDTI(a) .................................................37 CDTI(b).................................................37 CDTI(c) .................................................37 Figure18 ................................................37 RH.1.2.2.4 CDTI++(a).............................................37 CDTI++(b) ............................................38 CDTI++(c).............................................38 CDTI++(d) ............................................38 CDTI++(e).............................................38 Figure19-20 ...........................................39 Figure21-22 ...........................................40 Figure23 ................................................41 Figure24 ................................................42 L-PASS(a) .............................................41 L-PASS(b).............................................41 L-PASS(c) .............................................42 L-SEP(a)................................................39 L-SEP(b) ...............................................39 L-SEP(c)..........................................39, 41 L-SEP(d) .........................................39, 41 L-SEP(e)................................................39 LS-KEEP(a)...........................................42 LS-KEEP(b) ..........................................42 LS-KEEP(c)...........................................43 V-SEP(a) ...............................................40 V-SEP(b) ...............................................41 V-SEP(c) ...............................................41 V-SEP(d) ...............................................41 RH.1.2.3 EFISCP(a) .............................................43 EFISCP(b) .............................................43 EFISCP(c) .............................................44 EFISCP(d) .............................................44 RH.1.2.4 MCP(a)..................................................46 MCP(b)..................................................45 MCP(c)..................................................45 MCP(d)............................................45, 46 MCP(e)..................................................45 MCP(f) ..................................................45 MCP(g)..................................................47 MCP(h)..................................................45 MCP(i) ..................................................45 RH.1.2.5 CDU(a)..................................................12 CDU(b)..................................................12 CDU(c)..................................................12 CDU(d)..................................................12

Figure35................................................ 47 RH.1.2.6 SELECT(a) ........................................... 12 SELECT(b) ........................................... 12 SELECT(c) ........................................... 12 RH.1.3................................................... 50 RP.1 PERFO(a) ............................................. 52 PERFO(b) ............................................. 52 PERFO(c) ............................................. 52 RP.2 ........................................................ 8 RS.1 SYSTEM(a) .......................................... 54 SYSTEM(b) .......................................... 52 SYSTEM(c) .......................................... 52 SYSTEM(d) .......................................... 52 SYSTEM(e) .......................................... 52 SYSTEM(f)........................................... 52 SYSTEM(g) .......................................... 52

Section Break (Next Page)