in house test platform requirements specification - asas tn · 2021. 4. 24. · aircraft model /...

MA-AFAS IN STRICT CONFIDENCE Contract No.G4RD-2000-00228Report No. 560/79696Issue 1.0

IN STRICT CONFIDENCE Page i

CONTRACT N° : G4RD-2000-00228

PROJECT N° : GRD1-1999-10516

ACRONYM : MA-AFAS

TITLE : THE MORE AUTONOMOUS - AIRCRAFT IN THE FUTUREAIR TRAFFIC MANAGEMENT SYSTEM

D30 – In House Test Platform RequirementsSpecification

AUTHOR: BAE SYSTEMS

PROJECT CO-ORDINATOR : BAE SYSTEMS

PRINCIPAL CONTRACTORS :Airtel ATN Ltd (Ireland) QinetiQ (UK)ETG (Germany) EUROCONTROL (France)NLR (Netherlands)

ASSISTANT CONTRACTORS:AMS (Italy) DLR (Germany)ENAV (Italy) FRQ (Austria)Galileo Avionica (Italy) Indra Sistemas (Spain)NATS (UK) SCAA (Sweden)S-TT (Sweden) Skysoft (Portugal)SOFREAVIA (France) Stasys Limited (UK)Thales-ATM (France)

Report Number : 560/79696Project Reference number : MA-AFAS - WP3.0-BAESYSTEMSDate of issue of this report : 29 May 2003Issue No: 1.0PROJECT START DATE : 1/3/2000 DURATION : 36 months

Project funded by the European Communityunder the ‘Competitive and Sustainable Growth’Programme (1998-2002)

This document is proprietary of the MA-AFAS consortium members listed on the frontpage of this document. The document is supplied on the express understanding that it isto be treated as confidential and may not be used or disclosed to others in whole or inpart for any purpose except as expressly authorised under the terms of CEC Contractnumber G4RD-2000-00228


IN STRICT CONFIDENCE Page iii

LIST OF EFFECTIVE PAGES AND CHANGE HISTORY

Insert latest changed pages. Destroy superseded pages

TOTAL NUMBER OF PAGES IN THIS PUBLICATION IS 77CONSISTING OF THE FOLLOWING

Page No. Date Issue DCR Page No. Date Issue DCR

All 1.0 -


IN STRICT CONFIDENCE Page iv

DISTRIBUTION LIST

This Document is distributed as below.

Additional copies held by unnamed recipients will not be updated.

Paper Copies Name Address

MASTER Library BAE SYSTEMS, Rochester

MA-AFAS Library Avionic Systems

ElectronicCopies

Name Address

European Commission EC, Brussels

MA-AFAS Consortium Members [email protected]

MA-AFAS Web Site

mailto:[email protected]


IN STRICT CONFIDENCE Page v

Contents1 SCOPE.............................................................................................................................................1

1.1 Purpose and Scope ..................................................................................................................11.2 System Overview ......................................................................................................................11.3 Document Overview..................................................................................................................4

2 REFERENCED DOCUMENTS ........................................................................................................5

2.1 ARINC Standards .....................................................................................................................52.2 MA-AFAS Documents...............................................................................................................52.3 Other Standards........................................................................................................................5

3 REQUIREMENTS ............................................................................................................................6

3.1 System Architecture..................................................................................................................63.2 Hardware Facilities ...................................................................................................................6

3.2.1 Desktop PC Specification ..................................................................................................63.2.2 General Physical Requirements ........................................................................................73.2.3 Interfaces ...........................................................................................................................7

3.2.3.1 ARINC 429 Outputs .......................................................................................................73.2.3.2 ARINC 429 Inputs ..........................................................................................................83.2.3.3 Discrete Outputs ............................................................................................................83.2.3.4 Discrete Inputs ...............................................................................................................83.2.3.5 Ethernet..........................................................................................................................83.2.3.6 RS422 Ports...................................................................................................................9

3.3 Software....................................................................................................................................93.3.1 Operating System..............................................................................................................93.3.2 IHTP Software ...................................................................................................................93.3.3 Other Software.................................................................................................................10

3.4 Functionality............................................................................................................................103.4.1 Basic PC Functionality.....................................................................................................103.4.2 MA-AFAS Test Platform Functionality .............................................................................10

3.4.2.1 General ........................................................................................................................103.4.2.2 Aircraft Simulation ........................................................................................................103.4.2.3 Display Emulation ........................................................................................................423.4.2.4 Airline Operations Centre Emulation............................................................................463.4.2.5 Air Traffic Control Centre Emulation ............................................................................493.4.2.6 Broadcast Communications Support ...........................................................................523.4.2.7 MCDU Emulation .........................................................................................................543.4.2.8 Traffic Control...............................................................................................................543.4.2.9 Test Control..................................................................................................................56

3.5 Configurations.........................................................................................................................593.5.1 Networked PC..................................................................................................................593.5.2 In House Test Platform....................................................................................................59

3.5.2.1 Remote Configuration ..................................................................................................603.5.2.2 Local Configuration ......................................................................................................60

3.5.3 BAC1-11/RTAVS Support ...............................................................................................613.5.4 ATTAS Support................................................................................................................64

3.6 Sortie Generation and Recording ...........................................................................................663.6.1 File Formats.....................................................................................................................66

4 QUALIFICATION PROVISIONS ...................................................................................................67

5 REQUIREMENTS TRACEABILITY...............................................................................................68

6 NOTES...........................................................................................................................................69

6.1 Abbreviations ..........................................................................................................................69


IN STRICT CONFIDENCE Page vi

FiguresFigure 1 Block Diagram Showing IHTP Support of Other Test Facilities.............................................2Figure 2 IHTP Top Level Breakdown ...................................................................................................3Figure 3 Document Structure for IHTP Requirements .........................................................................4Figure 4 IHTP System Block Diagram..................................................................................................6Figure 5 BAC1-11 DCP Emulation .....................................................................................................44Figure 6 Ethernet Configuration .........................................................................................................60Figure 7 In House Test Platform Configuration ..................................................................................61Figure 8 BAC1-11/RTAVS Configuration ...........................................................................................63Figure 9 ATTAS Configuration ...........................................................................................................65

TablesTable 1 Aircraft Model Data Outputs.................................................................................................12Table 2 IRS Output Data ...................................................................................................................15Table 3 AHRS Output Data ...............................................................................................................17Table 4 ADC Output Data .................................................................................................................18Table 5 GNSS Output Data...............................................................................................................20Table 6 Data Puddle Output..............................................................................................................22Table 7 SBAS Data Output ...............................................................................................................23Table 8 GBAS Data Output ...............................................................................................................24Table 9 BAC1-11 Autopilot Output Data ...........................................................................................26Table 10 Output Status 1 ....................................................................................................................27Table 11 Output Status 2 ....................................................................................................................28Table 12 Discrete Status Word 1 ........................................................................................................29Table 13 Discrete Status Word 2 ........................................................................................................29Table 14 Operational Modes ...............................................................................................................30Table 15 Flight Phase .........................................................................................................................31Table 16 Vertical Modes......................................................................................................................32Table 17 Lateral Modes.......................................................................................................................33Table 18 BAC1-11 Autopilot Input Data ..............................................................................................33Table 19 AFCS Current Profile Mode Word........................................................................................34Table 20 AFCS Approach Mode Prime Command Word ...................................................................34Table 21 ARINC701 AFCS Data.........................................................................................................35Table 22 ARINC 701 AFCS Mode Commands...................................................................................36Table 23 EIU Data...............................................................................................................................37Table 24 ATTAS Aircraft State Vector Data........................................................................................41Table 25 ATTAS Outer Loop Guidance Vector Data ..........................................................................42Table 26 ARINC 725 DCP Data Outputs ............................................................................................43Table 27 Interface Configurations .......................................................................................................58


IN STRICT CONFIDENCE Page 1

1 SCOPE

1.1 Purpose and Scope

This document has been produced by the Avionics Systems Group of BAE SYSTEMS as deliverableitem D30 "Requirements Specification for the In House Test Platform“ for the MA-AFAS programme.

It defines the physical and software requirements of the In House Test Platform (IHTP) that is to beused in testing the MA-AFAS airborne equipment and supporting the aircraft and simulators that willbe used for the validation process.

1.2 System Overview

The BAE SYSTEMS In-house Test Platform (IHTP) will provide simple models for the aircraft and the'real' world to allow the stimulation of the MA-AFAS Avionics rig when connected standalone, or inconjunction with any of the avionic systems or identified Test Rigs. Configuration facilities will beavailable to allow selection of the required equipment configuration.

Figure 1 shows the possible test facilities that the IHTP needs to support.

Primarily, the IHTP software will be written using the Microsoft C++ Development environment. Somesoftware items will, however, be provided by other MA-AFAS consortium members. The software willbe hosted on a standard Personal Computer (PC), either desktop or laptop, running the Windows NT4 operating system.

Figure 2 gives an overview of the top level breakdown of the IHTP. Note that the Test ControlWindow, Test Control File, and Test Results File are effectively connected to all processes but this isnot shown in order to aid clarity.

The IHTP design and construction will allow its use both in the laboratory and the office. Initially, theIHTP will be housed in the office, thus facilitating its continued development whilst also allowing itsuse to stimulate the avionics rack which will always be housed in the laboratory. Interconnectionbetween the two units will be accomplished using the site ethernet network.

When used in the lab, the IHTP will be co-located with the avionics rig thus facilitating the use of theARINC429, RS422 and discrete links for the passage of data between the two units. Configurationfacilities will be provided to allow the selection of data transport mechanism for each link thusfacilitating the migration from 'remote' ethernet configuration to a local connection environment.

Whereas the IHTP will host interface hardware, specifically ARINC429 and Discrete ports, it is adesign goal to be able to use the IHTP software when installed on a laptop PC with all communicationbeing effected by way of an ethernet connection.

Similarly, since the IHTP will have MA-AFAS specific interface hardware, it will be possible for thedata loader, AOC Ground Station Simulator and software support environment to be hosted on thecomputer although it should be noted that it is unlikely that the processor will be unable to run morethan one of these applications at any one time.

MA-AFAS IN STRICT CONFIDENCE Contract No. G4RD-2000-00228Report No. 560/79696Issue 1.0


Flight Deckor

Flight Deck Simulator(Optional)

MA-AFAS AvionicsRack

FMU+CMU

Aircraft Systemsor

Aircraft Simulation(Optional)

BAES In-house Test RigFunction Select

ATN Comms �/�Non-ATN Comms �/�Broadcast �/�Traffic �/�Aircraft Model �/�NAV Display �/�MCDU Display �/�Crew Inputs (MCP etc) �/�Aircraft Systems �/�AOC �/�

Display OutputsCrew Inputs

DataRecorder(Optional)

Discrete/RS422

ARINC 429

Ethernet

DataLoader(Laptop)

Figure 1 Block Diagram Showing IHTP Support of Other Test Facilities



ATNComms

ATCCommsWindow

AOCCommsWindow

TestControlWindow

TestControl

File

TestResults

File

TrafficWindow

AircraftModel

Window

Non-ATNComms

AOCComms

TrafficGenerator

VDL4Simulator

VDL2Simulator

AircraftSystemsWindow

MA-AFASAVIONICS

OnboardAircraft

Simulation

On GroundSimulation

AOCMEDUP,

NUP

FrameMode IP

Non-ATN DataATN over

VDL4

GACS

ATN

ATN overVDL2

BLISVDL2

TrafficTrajectories

AttitudeData

GBASDataNav Data

Aircraft ModelData

AircraftState

SBASSimulator

AircraftSimulator

Airc

raft

Pos

ition

TIS-B/ADS-B

AP Control

Interface Switching

MCPWindow

MCPControl

MCP Interface

MCP Data

ARINC429Ethernet

DiscretesRS422

OtherSystemsSimulator

GBASSimulator

AHRSSimulator

ADCSimulator

AircraftPosition

AircraftPosition

ADCData

SimulatorControl

DiscretesData

AircraftState

AircraftSystems

Data

BroadcastComms

FIS

OwnshipWindow

BroadcastData

MCDUWindow

MCDUControl

MCDU Interface

MCDU Data

AFCSEmulator

APDemands

AP Data

Figure 2 IHTP Top Level Breakdown



1.3 Document Overview

This document is generated as a 6 part specification and is maintained using the DOORSrequirement management tool.

Section 1 provides overviews of the document and its place within the MA-AFAS programme.

Section 2 provides details of other documents and specifications that are referenced within the bodyof this document.

Section 3 gives the requirements that the IHTP must fulfil.

The requirements presented in this document are derived from other MA-AFAS deliverabledocuments as defined by the following documentation structure:

D38CNS/ATM Ground

System Requirements

D30Avionics Test Platform

Specification

D32Test Platform

Scenarios Definition

D31Test Platform Interface

Control Drawing

D18Airborne Systems

Requirement Specification

D24Airborne SystemsInterface Control

Document

D55Communications

Interface Specification

Figure 3 Document Structure for IHTP Requirements

Section 4 identifies the validation process that will be followed to validate the IHTP.

Section 5 provides traceability information that identifies the parentage of the requirements specifiedherein.

Section 6 provides a glossary of terms and abbreviations used within the document.

The requirements contained within this document identify the functionality that is required to fully testa MA-AFAS Avionics Rig. However, it is anticipated that during the development cycle, the AvionicsRig functionality will not require all of the test facilities defined. Where this occurs, the IHTPrequirement will not be modified in this document but the test phase will be set to ‘Post MA-AFAS’.The Test Phase identifier follows each requirement along with the Requirement Identifier and TestMethod.



2 REFERENCED DOCUMENTSThe following documents are referenced within this specification:

2.1 ARINC Standards

ARINC429 ARINC Specification 429P1-15; Mark 33 Digital Information Transfer System(DITS) Part 1, Functional Description, Electrical Interface, Label Assignmentsand Word Formats; September 1, 1995.

ARINC 624 ARINC Specification 624-1; Design Guidance for Onboard MaintenanceSystem, August 1993.

ARINC646 ARINC Specification 646; Ethernet Local Area Network (ELAN); 8 Dec 1995.

ARINC701 ARINC Characteristic 701-1; Flight Control Computer System; April 1, 1983.

ARINC702A ARINC Characteristic 702A-1; Advanced Flight Management ComputerSystem; January 31, 2000.

ARINC704 ARINC Characteristic 704-7; Inertial Reference System; March 19, 1999.

ARINC705 ARINC Characteristic 705-5; Attitude and Heading Reference System; April 30,1985.

ARINC706 ARINC Characteristic 706-4; Subsonic Air Data System; January 11, 1988.

ARINC725 ARINC Characteristic 725-2; Electronic Flight Instruments (EFI); November 5,1984.

ARINC 726 ARINC Characteristic 726-1; Flight Warning Computer System; September 10,1981.

ARINC743A ARINC Specification 743A-3; GNSS Sensor; January 5, 1998.

2.2 MA-AFAS Documents

D11 Ground System Requirements for MA-AFAS; Issue 1.0.

D24 Interface Control Drawing for MA-AFAS; Issue: 1.0.

D31 Interface Control Drawing for the In House Test Platform; 560/79697, Issue:1.0.

D32 Test Platform Scenarios Definition; Issue: Latest.

D34 Simulation and Flight Test Plan for MA-AFAS; Issue: Latest.

D38 CNS/ATM Ground System Requirements Definition; Issue: Latest.

D54 HMI Definition Document, Issue: Latest, Produced by NLR.

D55 Communications Interface Specification; Issue: Latest.

2.3 Other Standards

408-A13985-003 ARINC 739 Data Interface Protocol Specification for the CMA-2014 Mk3MCDU, Parts 1 and 2; Dated 11 April 1998; Issued by Canadian MarconiCompany.

9705/2 ATN Manual of Technical Provisions ICAO 9705/2, Baseline 1 as defined forPetal II.

ODIAC ORD Operational Requirements Document produced by ODIAC; Issue: Latest.



3 REQUIREMENTSThe IHTP provides the following facilities:

• Support for Avionics Hardware and Software development, integration, and test.

• Support for primary test facilities, including simulators and aircraft, providing functions that theprimary test facility does not have.

Basic HMI facilities will provide the ability to perform stored, synchronised test sequences or manualsetting up of simple communications messages, and monitoring of responses. It is not a replacementfor ground test platforms; in this role it is a gap filler only.

3.1 System Architecture

The BAE SYSTEMS In-house Test Platform (IHTP) is hosted in a PC and is summarised in thefollowing block diagram:

TestControlWindow

AOCTerminalWindow

NAVDisplayWindow

MCDUWindow

ATCCommsWindow

MCPWindow

AircraftSimulatorWindow

TrafficControlWindow

ARINC 429 InterfacesARINC 429 Module

RS 422 Module

Discrete Module

Ethernet Module

VDL Mode 2 InterfaceMode Control PanelAutopilot InterfaceAircraft Systems Interfaces

VDL Mode 4 Interface

VDL Mode 2 InterfaceMode Control PanelAutopilot InterfaceAircraft Systems Interfaces

ARINC 702A Discretes

Audio Module

VDL Mode 2 InterfaceMode Control PanelAutopilot InterfaceAircraft Systems InterfacesVDL Mode 4 InterfaceARINC 702A Discretes

ARINC 702A Alerts

MA-AFAS Alerts

Figure 4 IHTP System Block Diagram

3.2 Hardware Facilities

The IHTP will comprise a PC that, optionally, houses dedicated interface cards.

3.2.1 Desktop PC Specification

As a minimum, the PC hardware will include the following:

a) 1GHz Pentium 3, or equivalent

b) 30Gbyte hard drive



c) 128Mbyte RAM

d) CD-RW

e) 21 inch Monitor capable of 1600 x 1200 resolution

f) Sound Card with Joystick(MIDI) port

g) Interface Hardware:

8 ARINC 429 Inputs

16 ARINC 429 Outputs

16 Discrete Inputs

16 Discrete Outputs

Two RS232 Ports

3.2.2 General Physical Requirements

The IHTP shall be self contained and operable without the need to remove covers.

[Demonstration / TBD ] [ IHTP-52 ]

Connectors for the I/O circuitry shall be mounted on the chassis; possibly in a spare 5 1/2inch bay or at the rear of the base unit.

[Inspection / TBD ] [ IHTP-1689 ]

If an external power source is required for any discretes, the connection shall be achievedwithout the need for cover removal.


3.2.3 Interfaces

The IHTP will provide all the interfaces for connection to the MA-AFAS avionics rig. Initially, only asingle link will be provided for a given sub-system interface, i.e. simplex connections only. Later,consideration will be given to incorporating extra interfaces to facilitate the testing of duplex or triplexFMS/AFCS setups.

Further details of the individual interfaces can be found in the IHTP ICD; D31.

3.2.3.1 ARINC 429 Outputs

ARINC429 output ports from the IHTP will be provided to allow the replacement of the followingequipment:

• Inertial Reference System / Attitude and Heading Reference System

• Air Data Computer

• Global Navigation Satellite System

• SBAS

• GBAS

• VDL Mode 2

• Automatic Flight Control System

• Engine Management System

• Weight and Balance System

• MCDU



• Display Control Panel

The IHTP shall provide ARINC 429 output ports to stimulate the ARINC 429 inputs requiredby the MA-AFAS avionics rack.


The IHTP shall provide 16 ARINC 429 output ports.


The physical characteristics of all ARINC 429 output ports from the IHTP shall conform tosection 2 of ARINC429.


3.2.3.2 ARINC 429 Inputs

The IHTP will provide ARINC429 input ports to receive data destined for the following aircraftequipment:

• EFIS (option)

• Automatic Flight Control System (MCP)

• Engine Management System

• Weight and Balance System Interface

• VDL Mode 2

• MCDU

The IHTP shall provide input ports that allow interfacing with the ARINC 429 outputs from theMA-AFAS Avionics Equipment.


The IHTP shall provide 8 ARINC 429 input ports.


The ARINC 429 input ports on the IHTP shall be capable of receiving/decoding signals whosephysical characteristics conform to section 2 of ARINC429.


3.2.3.3 Discrete Outputs

The IHTP shall provide 16 discrete output interfaces with physical characteristics as definedin Section 3.5.1 of D31.


3.2.3.4 Discrete Inputs

The IHTP shall provide 16 discrete input interfaces with physical characteristics as defined inSection 3.5.2 of D31.


3.2.3.5 Ethernet

The IHTP will be able to support Ethernet connections for two functions:

a) The transmission of ARINC429/RS422/Discrete information between the IHTP and theavionics rack when the other interfaces are unavailable, e.g. when the units are physicallyremote.



b) Connection to the BAE SYSTEMS Intranet for the passing of data between the IHTP and theMA-AFAS server

It is anticipated that an ethernet hub will be used to connect the IHTP to each processor card in theAvionics rack, the Data Loader (laptop computer) and any individual equipment that requires ethernetconnection.

The IHTP shall provide a single 10baseT ethernet connection that conforms to the ARINC646characteristic.


3.2.3.6 RS422 Ports

The IHTP shall provide an RS422 port for connection to the avionics rack VHF Mode 4transponder port.


3.3 Software

3.3.1 Operating System

The Operating system for the IHTP shall be Windows NT 4.0, Service pack 5 or later.

[Inspection / DESN ] [ IHTP-95 ]

The operating system shall be set up to allow BAE System users with site usernames to logon, either connected to the Rochester site network or in stand alone mode, using their currentsite username and password.


A single user account, without administrator privileges, shall be provided for non-BAESystems personnel to log on to the computer in stand alone mode.


The username for this account shall be ’ihtpguest’.


A single user account, with administrator privileges, shall be provided for personnel to log onto the computer in stand alone mode.


The username for this account shall be ’ihtpadmin’.


3.3.2 IHTP Software

The IHTP software will provide all the functionality defined within this specification. Because ofworkshare agreements, some parts of the software will be written by other partners who have moreexperience in specific areas. With reference to Figure 2, the following functions will be provided by theidentified partners:

Airtel ATN: VDL2 Simulator, VDL4 Simulator, ATN Comms and Non-ATN CommsSkysoft: AOC CommsGaleleo Avionica: Traffic Generator

Software designed for the IHTP by BAE Systems shall be designed using the Rational Rosedevelopment suite.




Software written by BAE Systems for the IHTP shall be produced using Microsoft Visual C++,Version 6.0.


All software for the IHTP shall have its configuration controlled using the PVCS tool.


3.3.3 Other Software

Since the host will be a standard PC, it is anticipated that other software will be available for use,either in standalone mode or when connected to a site network. It is not expected that the IHTPsoftware will be run concurrently with any other package; in some cases it may be necessary todisable the extra software before invoking the IHTP package (especially anti-virus and toolbars).

Other packages installed on the IHTP PC may include the following:Microsoft Office ProfessionalMicrosoft Visual C++ 6.0Tornado IIMA-AFAS Data Loader/Preparation StationMcafee Anti VirusComms Ground Station simulator

3.4 Functionality

3.4.1 Basic PC Functionality

The IHTP shall provide the Windows NT functionality associated with a full installation.


3.4.2 MA-AFAS Test Platform Functionality

3.4.2.1 General

As depicted in Figure 2, the IHTP will include an Aircraft Simulator that is surrounded by a number ofequipment emulators. The simulator will generate simulated aircraft state and status data at aconstant rate, the data update rate, as defined below. Each of the equipment emulators will use thissimulator data to generate the parameters required for transmission to the avionics rack. To furthersimulate the real world, each state parameter produced by the simulator will be modified by userdefinable offset and ’noise’ factors prior to being transmitted as a equipment parameter.

As an example; Position (Latitude and Longitude) will be generated by the simulator; the GBASemulator will output this data with zero offset, the SBAS emulator will output the data with a smalloffset added and the GNSS emulator will output the data with a larger offset added.

The MA-AFAS IHTP will be totally configurable using software control to allow its use in multiplesituations. All outputs will be able to be isolated to preclude the need to manually configure the I/Ousing separate plugs/sockets. Similarly, an operator will be able to select which inputs need to beused in any given situation. This will be accomplished either by enabling specific I/O’s or by the use ofconfiguration files (to allow standard setup’s to be designed for the different rigs).

As an aid to integration and the use of multiple rigs, the IHTP will allow the isolation of data messagesfrom the physical transmission medium; the prime example being the ability to transfer ARINC429formatted data across either the ARINC 429 interconnections or the ethernet.

3.4.2.2 Aircraft Simulation

The IHTP will provide all the interfaces to aircraft systems that are expected by the MA-AFASavionics.



The simulation will allow both manual and automatic control of aircraft system interfaces. Automaticcontrol will be by means of a pre-defined test file in CSV format.

Manual control of the simulation will be facilitated using a dedicated display on a PC Window withmouse-driven display control and keyboard-driven data entry.

The simulation will comprise an aircraft model, which computes the basic system parameters, andequipment emulators that control the transmission of data to the avionics rig.

3.4.2.2.1 Aircraft Model

The IHTP will incorporate a simple closed loop aircraft model that will facilitate the development of 4Dguidance and ASAS functions.

The model will use a configuration file to define the maximum and minimum parameter values (e.g.maximum speed, climb rate, roll rate etc.) for use thus allowing the emulation of different types ofaircraft.

Initially, the operator will be able to select the following aircraft to model:

• BAC1-11

• ATTAS

Other aircraft types will be added as needed.

3.4.2.2.1.1 Model Inputs

The actions of the aircraft model will be controlled using a number of different sources. The control forthe data source selection will be provided by the MCP which determines the mode of operation of theboth the avionics equipment and the aircraft model.

It is anticipated that the model inputs are isolated from the ’real world’ interfaces in such a way thatthe use of a different autopilot does not require modifications to the model. It may be that the datainputs defined for scenario files is made standard (for the model) and the AFCS interface softwareconverts the available signals to this form.

It shall be possible to initialise the model with data prior to starting the simulation.


The operator shall have the ability to input values for windspeed and direction data into themodel.


The aircraft model shall use the AFCS mode data provided by the MCP emulator to control itsactions.


When any other AFCS mode is selected on the MCP, the aircraft model shall be able to utilisecommand parameters output by the Avionics Rig.


The aircraft model shall be able to accept control inputs from scenario files that define thefollowing data items:Scenario timeRequested pitch angleRequested bank angleRequested thrust



AFCS ModeWeight on wheels.


3.4.2.2.1.1.1 Joystick/Keyboard Control of the Model

When the AFCS mode is set to Manual, the aircraft model will be controlled by the operator using thejoystick/keyboard.

The aircraft model will be able to accept control inputs from an analogue joystick and/or the keyboard.

The IHTP joystick y-axis shall equate to rate of change of the aircraft climb rate.

[Analysis / TBD ] [ IHTP-1945 ]

The IHTP joystick x-axis shall equate to roll rate.


The IHTP keyboard ’+’ key (on the keypad) shall be used to increment the requested speed.


The IHTP keyboard ’-’ key (on the keypad) shall be used to decrement the requested speed.


3.4.2.2.1.2 Model Outputs

Data generated by the model shall include the following items:


Parameter Units Range Resolution UpdateRate (mS)

Latitude Radians ±π/2 2.9 E-9 20

Longitude Radians ±π 2.9 E-9 20

Altitude (AGL) Metres -100 to 32,000 0.25 20

Velocity North m/S ±1500 0.04 50

Velocity East m/S ±1500 0.04 50

Vertical Velocity m/S ±200 0.1 20

Longitudinal Acceleration m/S2 ±40 0.0001 10

Lateral Acceleration m/S2 ±40 0.0001 10

Normal Acceleration m/S2 ±40 0.0001 10

Heading Radians ±π 0.00001 10

Roll Angle Radians ±π/2 0.00002 10

Pitch Angle Radians ±π/2 0.00002 10

Yaw Rate Rads/Sec 2 0.0002 10

Roll Rate Rads/Sec 2 0.0002 10

Pitch Rate Rads/Sec 2 0.0002 10

Fuel Quantity Kg 50000 0.05 50

Time Seconds 86400 0.001 10

Table 1 Aircraft Model Data Outputs



3.4.2.2.1.3 Model Functionality

The IHTP shall provide a model of the aircraft that can be used to derive the data fortransmission to the avionics rig.


The Aircraft Model shall be capable of accepting configuration parameters that allows theemulation of the flight profile of different aircraft.


The Aircraft Model shall utilise the given inputs to compute updates to the output parametersat the rates shown in the Model Parameter Table.


It shall be possible to initialise the output parameters to any value within the stated valuerange.


It shall be possible to stop and start the generation of data updates by the Aircraft Model.


It shall be possible to modify the output parameters to any value within the stated range.


The aircraft model shall generate coherent position, attitude and velocity data.


When the AFCS mode is set to Heading Hold, the model shall modify the heading of theaircraft by 3 degrees/S until the current heading equals the operator input value.

[Measurement / TBD ] [ IHTP-1971 ]

3.4.2.2.1.4 Parameter Calculation

This section has been included to identify the calculations to be performed in converting the modeloutput parameters into the data transmitted from the IHTP.

Groundspeed and track shall be calculated as the vector sum of the aircraft velocity and thewind velocity.

[Analysis / DESN ] [ IHTP-1950 ]

3.4.2.2.2 Inertial Reference System

The IHTP will manipulate the aircraft model data to provide an ARINC429 output that simulates anInertial Reference System (IRS).

The IRS emulation shall be controlled using the Aircraft Systems Window.


The IHTP shall allow the operator to simulate the following IRS modes:OFF :- No 429 Outputs will be drivenALIGNMENT :- Generate Outputs as in NAVNAVIGATION :- Generate OutputsATTITUDE REF MODE :- Generate Outputs as in NAVBITE :- Report Status Only




The IHTP shall allow the operator to set IRS state information in the IRS Discretes word(Label 270) on the Aircraft Systems Window.


The IHTP shall provide simulated IRS data as defined in the following table:


Data Item OctalLabel

Tx Interval(mS)

BAC 1-11

NoiseFactor

Units

Present Position - Lat. (BCD) 010 500 N/A °Present Position - Long (BCD) 011 500 N/A °Ground Speed (BCD) 012 500 N/A Kts

Track Angle True (BCD) 013 500 N/A °Magnetic Heading (BCD) 014 500 N/A °Wind Speed (BCD) 015 500 N/A Kts

Wind Direction True (BCD) 016 500 N/A °True Heading (BCD) 044 500 N/A °Body Pitch Acceleration 052 Not Used N/A N/A

Body Roll Acceleration 053 Not Used N/A N/A

Body Yaw Acceleration 054 Not Used N/A N/A

IRS Discretes Word 270 500 N/A N/A

IRS Test 277 Not Used N/A N/A

Present Position - Lat. 310 200 * 0.00035 °Present Position - Long. 311 200 * 0.00035 °Ground Speed 312 50 * 0.25 Kts

Track Angle - True 313 50 * 0.011 °True Heading 314 50 * 0.011 °Wind Speed 315 100 * 2 Kts

Wind Direction 316 100 * 1.5 °Track Angle - Magnetic 317 50 * 0.011 °Magnetic Heading 320 50 * 0.011 °Drift Angle 321 50 * 0.2 °Flight Path Angle 322 50 0.1 °Flight Path Accel. 323 20 0.002 g

Pitch Angle 324 20 * 0.001 °Roll Angle 325 20 * 0.02 °Pitch Rate - Body 326 20 * 0.03 °/s

Roll Rate - Body 327 20 * 0.03 °/s

Yaw Rate - Body 330 20 * 0.03 °/s

Longitudinal Accel. - Body 331 20 * 0.002 g

Lateral Accel. - Body 332 20 * 0.002 g

Normal Accel. - Body 333 20 * 0.002 g

Platform Heading 334 100 N/A N/A

Track Angle Rate 335 20 * 0.03 °/s

Pitch Rate - Inertial 336 20 * 0.03 °/s

Roll Rate - Inertial 337 20 * 0.03 °/s



Track Angle Grid 340 Not Used N/A N/A

Grid Heading 341 Not Used N/A N/A

IRS Maintenance Discretes 350 500 N/A N/A

Potential Vertical Speed 360 20 2 Ft/min

Altitude-Inertial 361 50 3 Ft

Along Track Accel 362 20 0.002 g

Across Track Accel 363 20 0.002 g

Vertical Acceleration 364 20 * 0.002 g

Vertical Speed 365 40 * 2 Ft/s

N/S Velocity 366 100 * 0.25 Kts

E/W Velocity 367 100 * 0.25 Kts

Along Heading Acceleration 375 20 0.002 g

Cross Heading Acceleration 376 20 0.002 g

Equipment Identification (004) 377 1000 N/A N/A

Table 2 IRS Output Data

The IHTP shall base the IRS data on the Aircraft Model data with the addition of aprogrammable pseudo-random error factor.


The format of data output from the IRS emulator via the ARINC429 data link shall be asdefined in ARINC704.


The equipment code associated with the ARINC429 transmissions from the IRS emulatorshall be 004.


The operator shall be able to input a fixed value for Magnetic Variation via the AircraftSystems window.


3.4.2.2.3 Attitude and Heading Reference System

The IHTP will manipulate the aircraft model data to provide an ARINC429 output that simulates anAttitude and Heading Reference System (AHRS).

The IHTP shall provide simulated AHRS data as defined in the following table:

[Inspection / Post MA-AFAS ] [ IHTP-626 ]




TxInterval

(mS)

NoiseFactor

Units

Groundspeed (BCD) 012 500 N/A Kts

Magnetic Heading (BCD) 014 500 N/A °

Wind Speed (BCD) 015 500 N/A Kts

Track Angle Magnetic (BCD) 053 500 N/A °

Wind Direction Magnetic (BCD) 056 500 N/A °

AHRS Discretes Word 270 200 N/A N/A

Groundspeed 312 50 0.25 Kts

Wind Speed 315 100 2 Kts

Track Angle Magnetic 317 50 0.011 °

Magnetic Heading 320 50 0.011 °

Drift Angle 321 50 0.2 °

Flight Path Angle 322 50 0.1 °

Flight Path Accel. 323 20 0.002 g

Pitch Angle 324 20 0.02 °

Roll Angle 325 20 0.02 °

Pitch Rate - Body 326 20 0.03 °/s

Roll Rate - Body 327 20 0.03 °/s

Yaw Rate - Body 330 20 0.03 °/s

Longitudinal Accel. Body 331 20 0.002 g

Lateral Accel. - Body 332 20 0.002 g

Normal Accel. - Body 333 20 0.002 g

Platform Heading 334 40 0.2 °

Track Angle Rate 335 20 0.03 °/s

Pitch Rate - Inertial 336 20 0.03 °/s

Roll Rate - Inertial 337 20 0.03 °/s

Potential Vertical Speed 360 50 2 Ft/min

Altitude-Inertial 361 40 1 Ft

Vertical Accel. 364 20 0.002 g

Vertical Velocity-Inertial 365 40 2 Ft/s

Wind Direction Magnetic 372 100 0.7 °

N-S Velocity-Magnetic 373 200 0.25 Kts

E-W Velocity-Magnetic 374 200 0.25 Kts

Along Heading Accel. 375 20 0.002 g

Across Heading Accel. 376 20 0.002 g

Equipment Identifier (005) 377 1000 N/A N/A



Table 3 AHRS Output Data

The IHTP shall base the AHRS data on the Aircraft Model data with the addition of aprogrammable pseudo-random error factor defined in the data table above.

[Analysis / Post MA-AFAS ] [ IHTP-748 ]

The format of data output from the IRS emulator via the ARINC429 data link shall be asdefined in ARINC705.


The equipment code associated with the ARINC429 transmissions from the AHRS emulatorshall be 005.


3.4.2.2.4 Air Data Computer

The IHTP will manipulate the aircraft model data to provide an ARINC429 output that simulates an AirData Computer (ADC)

The IHTP shall provide simulated ADC data as defined in the following table:





Tx Interval(mS)

BAC 1-11 Units

Altitude (1013.25 mb) 203 62.5 * Ft

Baro Corrected Altitude Output #1 204 62.5 Ft

Mach 205 125 *

Computed Airspeed 206 125 * Kts

Max. Allowable Airspeed 207 125 Kts

True Airspeed 210 125 * Kts

Total Air Temp 211 500 °C

Altitude Rate 212 62.5 * Ft/s

Static Air Temp 213 500 * °C

Impact Pressure 215 125 mb

Static Air Pressure 217 125 * (Not 706) mb

Baro Corrected Altitude Output #2 220 62.5 Ft

Indicated Angle of Attack 221 62.5 °

True Airspeed (BCD) 230 500 Kts

Total Air Temp 231 500 °C

Static Air Temp (BCD) 233 500 °C

Baro Correction mb#1 (BCD) 234 125 mb

Baro Correction ins. Hg #1 (BCD) 235 125 ins Hg

Baro Correction mb#2 (BCD) 236 125 mb

Baro Correction ins. Hg #2 (BCD) 237 125 ins Hg

Corrected Angle of Attack 241 62.5 °

Total Pressure 242 125 mb

Discrete Word #1 270 N/A

Discrete Word #2 271 N/A

Maintenance Word #1 350 N/A

Maintenance Word #2 351 N/A

Equipment Identifier (006) 377 1000 N/A

Table 4 ADC Output Data

The format of data output from the ADC emulator via the ARINC429 data link shall be asdefined in ARINC706


The accuracy of data output from the ADC emulator, with respect to the model data, shall beas defined in section 4.10 of ARINC706.




The equipment code associated with the ARINC429 transmissions from the ADC emulatorshall be 006.


The Aircraft Systems window shall be used to control the mode of the ADC emulator.


3.4.2.2.5 Navigation Data Simulation

The IHTP will be able to emulate multiple navigation sensors. The list will include the following:Global Navigation Satellite System (GNSS) as defined by ARINC 743AQinetiQ defined Data Puddle, to support the flight trials on the BAC1-11,DLR defined navigation data included in the ATTAS EXO data message.

Note: Only one Nav data output will be required at any one time. To this end, the same ARINC429output port will be used for both the data formats.

The IHTP shall provide a configuration facility to allow the operator to select which Nav dataformat is required.


3.4.2.2.5.1 Global Navigation Satellite System Simulation

The IHTP will manipulate the aircraft model data to provide an ARINC429 output that simulates aGlobal Navigation Satellite System (GNSS) as defined by ARINC 743A

The IHTP shall provide simulated GNSS data as defined in the following table:





Tx Interval(mS)

NoiseFactor

Measurement Status 060 Not Used N/A

Pseudo Range 061 Not Used N/A

Pseudo Range Fine 062 Not Used N/A

Range Rate 063 Not Used N/A

Delta Range 064 Not Used N/A

SV Position X 065 Not Used N/A

SV Position X Fine 066 Not Used N/A

SV Position Y 070 Not Used N/A

SV Position Y Fine 071 Not Used N/A

SV Position Z 072 Not Used N/A

SV Position Z Fine 073 Not Used N/A

UTC Measurement Time 074 Not Used N/A

GNSS Altitude 076 1S ± 1Ft

HDOP 101 1S N/A

VDOP 102 1S N/A

Track Angle (True) 103 1S ±1°

Present Position Latitude (Coarse) 110 1S N/A

Present Position Longitude (Coarse) 111 1S N/A

Ground Speed 112 1S ±1kt

Present Position Latitude (Fine) 120 1S ±0.000034°

Present Position Longitude (Fine) 121 1S ±0.000034°

UTC Coarse 125 Not Used N/A

Horizontal Integrity 130 1S N/A

Vertical Integrity 133 1S N/A

Vertical Figure Of Merit 136 1S N/A

UTC Fine 140 1S N/A

UTC Fine Fractions 141 1S N/A

UTC 150 1S N/A

Vertical Velocity 165 1S ±1Ft/Sec

N/S Velocity 166 1S ±1Ft/Sec

E/W Velocity 174 1S ±1Ft/Sec

Horizontal Figure Of Merit 247 1S N/A

Status Word 273 1S N/A

Maintenance Word 355 1S N/A

Table 5 GNSS Output Data



The Aircraft Systems window shall be used to control the mode of the GNSS emulator.


ARINC743A defines a number of modes that a GNSS can operate in. The GNSS emulatorshall provide data outputs that simulate the operation of the GNSS in any of the followingmodes:InitialisationAcquisitionNavigationWAAS excluding precision approach.


Using the Aircraft Systems Window, it shall be possible for the operator to select whichsupported GNSS mode is to be emulated.


The format of data output from the GNSS emulator via the ARINC429 data link shall be asdefined in ARINC743A.


The equipment code associated with the ARINC429 transmissions from the GNSS emulatorshall be TBD.


3.4.2.2.5.1.1 GNSS Time

UTC time shall be derived from the time output by the Aircraft Model by adding an offset.


The offset time shall be read from a configuration file at the start of a test.


Note that the UTC Fine Fractions data (label 141) and the low order 10 bits of UTC Fine (Label 140)will be set to zero. This will provide time with a resolution of approximately 1mS.

3.4.2.2.5.1.2 Position and Attitude Data

The IHTP shall base the Position and Attitude data on the Aircraft Model data with theaddition of programmable offset and pseudo-random error (noise) factors.


3.4.2.2.5.2 BAC1-11 Data Puddle Emulation

The IHTP shall manipulate the aircraft model data to provide an ARINC429 output thatsimulates the output from the BAC1-11 Data Puddle as defined in the following Table:





Tx Interval(mS)

NoiseFactor

Present Position Latitude 310 200

Present Position Longitude 311 200

Ground Speed 312 200 ±1Kt

Track Angle (True) 313 200 ±1°

Heading (True) 314 200 ±1°

Wind Speed 315 200

Wind Direction (True) 316 200 ±1°

Table 6 Data Puddle Output

Parameter formats shall conform to the ARINC702/704 definitions for the data items.


3.4.2.2.5.3 ATTAS Navigation Data

The IHTP will provide an output of navigation data that is compatible with that provided by the ATTASrig. This data is defined in 3.4.2.2.20.2.

3.4.2.2.6 SBAS Interface

The IHTP will be able to output data to the avionics rack in the same format as that provided by theSBAS equipment fitted to the QinetiQ BAC1-11 trials aircraft.

The IHTP shall provide simulated SBAS data as defined in the following table:




Data Item Octal Label Tx Rate

Runway Heading (Magnetic) 105 Not Used

Localiser Deviation 173 Not Used

Glide Slope Deviation 174 Not Used

Altitude 076 200mS

HDOP 101 200mS

VDOP 102 200mS

Track Angle (True) 103 200mS

Present Position Latitude (Coarse) 110 200mS

Present Position Longitude (Coarse) 111 200mS

Ground Speed 112 200mS

Present Position Latitude (Fine) 120 200mS

Present Position Longitude (Fine) 121 200mS

UTC Coarse 125 200mS

Horizontal Integrity 130 200mS

Vertical Integrity 133 200mS

UTC Fine 140 200mS

UTC Fine Fractions 141 200mS

UTC 150 200mS

Vertical Velocity 165 200mS

Date 260 200mS

Status Word 273 200mS

Table 7 SBAS Data Output

The format of data output from the SBAS emulator via the ARINC429 data link shall be asdefined in ARINC743A.


The IHTP shall base the SBAS Position and Attitude data on the Aircraft Model data with theaddition of programmable offset and pseudo-random error (noise) factors.


The equipment code associated with the ARINC429 transmissions from the SBAS emulatorshall be TBD.


3.4.2.2.7 GBAS Interface

The IHTP will be able to output data to the avionics rack in the same format as that provided by theGBAS equipment fitted to the QinetiQ BAC1-11 trials aircraft.

The IHTP shall provide simulated GBAS data as defined in the following table:





Tx Interval(mS)

Runway Heading (Magnetic) 105 200mS

Localiser Deviation 173 200mS

Glide Slope Deviation 174 200mS

Altitude 076 200mS

HDOP 101 200mS

VDOP 102 200mS

Track Angle (True) 103 200mS

Present Position Latitude (Coarse) 110 200mS

Present Position Longitude (Coarse) 111 200mS

Ground Speed 112 200mS

Present Position Latitude (Fine) 120 200mS

Present Position Longitude (Fine) 121 200mS

UTC Coarse 125 200mS

Horizontal Integrity 130 200mS

Vertical Integrity 133 200mS

UTC Fine 140 200mS

UTC Fine Fractions 141 200mS

UTC 150 200mS

Vertical Velocity 165 200mS

Date 260 200mS

Status Word 273 200mS

Table 8 GBAS Data Output

The format of data output from the GBAS emulator via the ARINC429 data link shall be asdefined in ARINC743A.


The IHTP shall base the GBAS data on the Aircraft Model data with the addition ofprogrammable offset and pseudo-random error (noise) factors.


The equipment code associated with the ARINC429 transmissions from the GBAS emulatorshall be TBD.


3.4.2.2.8 GRAS Interface

Provision will be made for data to be output using an RS422 comms port. It is unlikely that thisinterface will be exercised in the MA-AFAS trials.

TBD



3.4.2.2.9 Automatic Flight Control System

The IHTP will provide ARINC429 outputs that simulate the controls output by an Automatic FlightControl System (AFCS) Mode Control Panel (MCP) and the status output by an AFCS.

The IHTP will also provide an ARINC429 input to receive the guidance command messages from theavionics rack.

The IHTP will receive data from the MA-AFAS equipment that is destined for the autopilot. This datawill comprise the steering commands and will be used to drive the aircraft model when the system isunder FMS control. The IHTP will need to be capable of receiving the data in (at least) two differentformats: the QinetiQ BAC1-11 format and that used for the ATTAS. It may also need to cater for astandard ARINC701 format.

Note that the AFCS fitted to the BAC1-11 and ATTAS trials aircraft are not fully compatible with theARINC 701 standard. For this reason, the IHTP will need to be able to be configured to emulate oneof three possible AFCS; BAC1-11, ATTAS and ARINC701.

This will be accomplished by the provision of a number of different emulators and the ability for theoperator to select which one is used.

It is not considered likely that the ARINC 701 configuration will be used for trials.

The IHTP shall provide a window for the Mode Control Panel emulation.


The MCP window shall provide the operator an interface to control the actions of the MCPemulation function.


3.4.2.2.9.1 QinetiQ BAC1-11 Digital Autopilot Emulation

3.4.2.2.9.1.1 Outputs from the BAC1-11 Digital Autopilot Emulation

The BAC1-11 digital autopilot is capable of transmitting a number of status, mode and data wordswhich will be used by the avionics.

The IHTP shall be capable of generating the data defined in the following tables whenemulating the BAC1-11 digital autopilot:




ARINC Label Tx Rate Parameter Description Notes

101 360ms Selected Heading As per ARINC 701

102 360ms Selected Altitude As per ARINC 701

103 360ms Selected Air Speed As per ARINC 701

201 360ms Last Failure Condition 17 bit failure code

202 360ms Last I/O Failure Condition 17 bit failure code

211 360ms Output Status 1 See below for definition

212 360ms Output Status 2 See below for definition

232 360ms Throttle 1 Position Scaling is ±128° using 15 bits

233 360ms Throttle 2 Position Scaling is ±128° using 15 bits

270 360ms Discrete Status Word 1 See below for definition

271 360ms Discrete Status Word 2 See below for definition

272 360ms Operational Modes See below for definition

273 360ms Flight Phase See below for definition

274 360ms Vertical Modes See below for definition

275 360ms Lateral Modes See below for definition

Table 9 BAC1-11 Autopilot Output Data



Bit Data

1-8 ARINC Address (211)

9 Autopilot Engaged

10 Autopilot Engagement Selected

11 Autopilot OK Flag

12 Roll Servo 1 Engaged

13 Roll Servo 2 Engaged

14 Elevator Servo 1 Engaged

15 Elevator Servo 2 Engaged

16 Throttle Servo Engaged

17 Autothrottle Engaged

18 Pitch Control Engaged

19 Roll Control Engaged

20 EFMS Level Flight Mode

21 EFMS Climb Mode

22 EFMS Descent Mode

23 EFMS MLS Level Flight Mode

24 EFMS MLS Descent Mode

25-29 Not Used

30-31 SSM

32 Parity

Table 10 Output Status 1



Bit Data


9 Lateral Control In Attitude Hold Mode

10 Change Alt. Mode / Hold Speed Mode / Autothrottle Engaged

11 Not Used

12 Change Alt. Mode / Change Speed Mode / Autothrottle Engaged

13 Hold Alt. Mode / Hold Speed Mode / Autothrottle Engaged

14 Hold Alt. Mode / Change Speed Mode / Autothrottle Engaged

15 Change Alt. Mode / Hold Speed Mode / Autothrottle Disengaged

16 Change Alt. Mode / Change Speed Mode / Autothrottle Disengaged

17 Not Used

18 Hold Alt. Mode / Autothrottle Disengaged

19 Lateral Control In Attitude Hold Mode

20 Port Heading Control Mode

21 Starboard Heading Control Mode

22 EFMS Lateral Control Mode

23 Port/Stbd. Heading Control Mode

24 ILS Glideslope Acquired / Hold Speed Mode

25 ILS Glideslope Acquired / Change Speed Mode

26 ILS Localiser Acquired Mode

27-29 Not Used

30-31 SSM

32 Parity

Table 11 Output Status 2



Bit Data


9-11 Not Used

12 DAP Id #1

13 DAP Id #2

14 Not Used

15 Autothrottle Armed

16 Hold Speed Mode

17 Change Speed Mode

18-19 Not Used

20-22 Lateral Mode - See note

23-29 Not Used

30-31 SSM

32 Parity

Note: In Attitude Hold, these 3 bits are set to111, in other engaged modes, these are set to011.

Table 12 Discrete Status Word 1

Bit Data


9 Hold Altitude Mode

10 Change Altitude Mode

11-12 Not Used

13 Port/Stbd Heading Mode (non-FMS lateral control)

14-29 Not Used

30-31 SSM

32 Parity

Table 13 Discrete Status Word 2



Bit Data


9 Not Used

10 Speed Control Mode Not Engaged (CLP)

11 Not Used

12 Speed Control Mode Engaged (APR)

13-15 Not Used

16 Vertical Navigation In Climb Mode (N1)

17-20 Not Used

21 Vertical Navigation in Climb Mode (CLB)

22 Not Used

23 Vertical Navigation (VNV)

24 Speed Control Mode Engaged (IAS)

25 Not Used

26 Vertical Guidance Selected to Altitude Hold (ALT)

27-29 Not Used

30-31 SSM

32 Parity

Table 14 Operational Modes



Bit Data


9-12 Not Used

13 Lateral & Vertical Control Modes Engaged (FMC)

14 Lateral Control Mode Engaged (LNAV)

15 Vertical Control Mode Engaged (VNAV)

16 ILS Localiser Mode Primed (LOC)

17-21 Not Used

22 Vertical Navigation in Climb Mode (CLB)

22 ILS Glideslope Mode Primed (GLIDE)

23 Not Used

24 Change Alt. In Climb Mode

25 Change Alt. In Descent Mode

26-29 Not Used

30-31 SSM

32 Parity

Table 15 Flight Phase



Bit Data


9 Change Alt. In Climb Mode (Climb)

10 Change Alt. In Descent Mode (Descent)

11 Speed Control Engaged / Non-Level Flight (IAS)

12 Vertical Control Mode Engaged (VNAV)

13 Hold Altitude Mode (ALT)

14-18 Not Used

19 ILS Glideslope Control Mode (GLIDE)

20-21 Not Used

22 Speed Control Engaged / Non-Level Flight

or Level Flight Mode

or Hold Alt. Control Mode (TRACK)

23-25 Not Used

26 Speed Control Mode

or Hold Alt. Control Mode (HOLD)

27 Not Used

28 Vertical Guidance Not In Hold Alt. Mode (PITCH)

29 Not Used

30-31 SSM

32 Parity

Table 16 Vertical Modes



Bit Data


9-10 Not Used

11 Lateral Control Mode Engaged (LNAV)

12 Lateral Attitude Hold (HDG HOLD)

13 Port/Stbd. Heading Control Mode (HDG SEL)

14 Not Used

15 Localiser Control Mode (LOC)

16-20 Not Used

21 Lateral Control Mode in non-Attitude Hold (CAPTURE)

22 Not Used

23 Lateral Control Mode in non-Attitude Hold (TRACK)

24-29 Not Used

30-31 SSM

32 Parity

Table 17 Lateral Modes

3.4.2.2.9.1.2 Inputs to the BAC1-11 Digital Autopilot Emulation

If the avionics rack is configured to use the QinetiQ BAC1-11 autopilot, the data received by the IHTPwill be as defined in the following tables:

Parameter Description ARINC Label Notes

Bank Demand 121 As per ARINC702

Glide Slope Deviation 174 As per ARINC710

Current Profile Mode 301 See below for definition

Approach Mode Prime Command 360 See below for definition

Height Demand 361 As per ARINC702, label 102

Computed Air Speed (CAS) Demand 362 As per ARINC702, label 103

N1 Demand (%RPM) 363 As per ARINC702, label 341

Next Level Height 364 As per ARINC702, label 102

Vertical Profile Gradient Change 365 Scaled to ±128Rad using 19significant bits

Throttle Demand 366 Scaled to ±180° using 15significant bits

CAS Rate Demand 370 Scaled to 4kts/sec using 15significant bits

Table 18 BAC1-11 Autopilot Input Data



Bits Data

1-8 ARINC Label (301)

9-10 Not Used

11 Level Flight Mode

12 Climb Mode

13 Descent Mode

14 Within STAR Region (used to allow the pilot toselect speed while FMS control height)

15-20 Not Used

21 Continuous Profile Guidance Mode

22-29 Not Used

30-31 SSM

32 Parity

Table 19 AFCS Current Profile Mode Word

Bits Data

1-8 ARINC Label (360)

9-13 Not Used

14 Prime Glide Slope Capture Mode

15 Prime Localiser Capture Mode

16-17 Not Used

18-29 Selected Runway Heading

Table 20 AFCS Approach Mode Prime Command Word

3.4.2.2.9.1.3 Mode Control Panel Emulation

The IHTP will provide an emulation of the BAC1-11 Autopilot Mode Control Panel. This will roughlyaccord with the actual panel fitted to the aircraft in as far as the provision of mode control buttons andheight/speed/heading setting controls.

The IHTP shall provide for the emulation of the following BAC1-11 autopilot modes:LNAVProfile


The IHTP Mode Control Panel emulator shall be capable of inputting a numerical failure codeassociated with autopilot disengagement.


3.4.2.2.9.2 ATTAS Autopilot Emulation

3.4.2.2.9.2.1 ATTAS Autopilot Interfaces

Section 3.4.2.2.20.2 defines the data transmitted between the IHTP and Avionics rig when in ATTASemulation mode.



3.4.2.2.9.2.2 ATTAS MCP Emulation

The IHTP shall provide an emulation of the ATTAS Mode Control Panel. This shall roughlyaccord with the actual unit fitted to the ATTAS in as far as the provision of controls forenabling/disengaging the autopilot and autothrottle, and the selection of height, speed andheading demands.


Demand data input by the operator using the MCP Emulation shall be transmitted to theATTAS in the Outer Loop Guidance Vector datablock as defined in 3.4.2.2.20.


3.4.2.2.9.3 ARINC 701 Autopilot Emulation

3.4.2.2.9.3.1 AFCS Command Reception

The IHTP shall provide an input port to receive ARINC429 data destined for an Autopilot.


If the avionics rack is configured to use a standard ARINC 701 autopilot, the data received by theIHTP will be as defined in the following table:

Data Item Octal Label Tx Rate

Lateral Steering Command 121

Vertical Steering Command 122

Table 21 ARINC701 AFCS Data

3.4.2.2.9.3.2 Mode Control Panel Emulation

The MCP emulation will provide control for the simulated autopilot and mode data to Avionics rack.

The MCP emulation will be able to simulate the following modes of autopilot operation.

• Manual flying (Pilot control)

• FMS

• LNAV

• VNAV

• Autothrust

• Altitude Hold

• Heading Hold

Note: The MCP emulation will not support TURB, FD, or LAND functions

Generated data will conform to characteristic ARINC 701 and will be transmitted to the Avionics Rackvia an ARINC 429 interface or the Ethernet connection.

Data entry and control of the MCP actions will be either manual, using the MCP display window, or viaautomatic test files.



The IHTP shall provide an MCP emulator that is capable of emulating the outputs from aMode Control Panel as defined in ARINC 701.

[Demonstration / Post MA-AFAS ] [ IHTP-1867 ]

The MCP emulation function shall be capable of providing mode data to the avionics rack thatdefines operation of the aircraft in any of the following modes:ManualFMSLNAVVNAVAutothrustAltitude HoldHeading Hold.


The IHTP shall provide an ARINC429 interface to the avionics rack for the transfer of AFCSmode commands.


The IHTP shall provide the following mode data (defined in Section 5 of ARINC701) to theavionics rack:



Tx Interval(mS)

Discrete Word #1 270 200


Table 22 ARINC 701 AFCS Mode Commands

3.4.2.2.10 Communication System Interfaces

The IHTP will provide interfaces for two VHF Data Link facilities; VDL Mode 2 and VDL Mode 4.

3.4.2.2.10.1 VDL Mode 2 Interface

The IHTP shall provide a bi-directional ARINC 429 interface to the avionics rack for thetransmission of VDL mode 2 data.


Data format requirements for the VDL mode 2 interface shall conform to document TBD.

[TBD / Post MA-AFAS ] [ IHTP-1916 ]

3.4.2.2.10.2 VDL Mode 4 Interface

The IHTP shall provide a bi-directional RS422 interface to the avionics rack for thetransmission of VDL mode 4 data.


Data format requirements for the VDL mode 4 interface shall conform to document BLIS Rev1E.




3.4.2.2.11 Engine Management System

The Engine Management System (EMS) can be considered as comprising an Engine InstrumentationUnit (EIU) that reports the status of the engine(s) and the engine Autothrottle components. For theBAC1-11 fit, this latter functionality is included in the Digital Autopilot.

3.4.2.2.11.1 BAC1-11 Engine Instrumentation Unit

The IHTP shall be capable of emulating an EIU as fitted to the BAC1-11.


The EIU emulation shall provide engine data as defined in the following table:



Range Tx Interval(Sec)

N1, Starboard Engine % HP RPM 245 0-256% 1

N1, Port Engine % HP RPM 246 0-256% 1

Table 23 EIU Data

3.4.2.2.12 Weight and Balance System

TBD (ARINC737)

3.4.2.2.13 Aircrew Warning System

Throughout the MA-AFAS trials, there will not be an Aircrew Warning System (AWS) fitted. Instead,the IHTP will contain a sound generator that can generate simple tones in support of an aural alertingfacility.

Note: it is assumed that the IHTP sound generator includes speakers that may need to be connectedexternally.

The standard AWS (as defined by ARINC726) is not considered comprehensive enough to supportthe aural signals identified in D54. Thus for MA-AFAS, the interface to the IHTP sound generator willnot be the standard 28V discrete. Instead, the ethernet link will be used to transfer the alert data fromthe avionics rig to the IHTP sound generator.

The IHTP sound card shall be used to generate aural alerts when alert data is received fromthe Avionics Rack.


The sound generator shall be capable of replaying wave sound files (.wav) to generate theaudio alerts. For the MA-AFAS trials, these are defined in section 7 of D54.


The sound generator shall be capable of decoding an 8 bit data word from the avionics rackto define which of 8 sound files should be replayed.


The IHTP shall include an Audio Out socket as defined in D31 for connection to an aircraftintercom system during flight/rig trials.




3.4.2.2.14 Weather Radar

This interface will not be supported by the IHTP.

3.4.2.2.15 ACMS Emulation

Using the Aircraft Systems window, the operator will be able to define sufficient aircraft condition datato allow the compilation of a simple ACMS message for transmission via the avionics to the AOCemulation.

Note: For MA-AFAS purposes, the emulation of ACMS data will only be associated with thegeneration of OOOI messages by the Avionics Rig. Data for this will be generated by the IHTP and betransmitted to the rig via ethernet rather than ARINC429.

The IHTP shall allow the operator to generate simulated aircraft condition information usingthe Aircraft Systems Window. (The detailed information types available are based on ARINC624.)


The IHTP shall be capable of receiving a ’request for data’ from the avionics Rig via theethernet interface.

[TBD / TBD ] [ IHTP-2200 ]

The IHTP shall be capable of transmitting ACMS data to the Avionics Rig via the ethernet.

[TBD / TBD ] [ IHTP-2199 ]

3.4.2.2.16 Fuel Quantity Emulation

The BAC1-11 does not provide any facilities for the generation of fuel information so in thisconfiguration the Avionics Rig will compute its own data.

For other configurations, the IHTP will allow the entry of initial data (aircraft mass, fuel mass etc.) andthe aircraft model shall compute the remaining fuel value. This data will then be used to compute therequired fuel data for transmission to the Avionics Rig.

The IHTP shall allow the operator to manually input the initial fuel quantity information.


The IHTP shall allow the setting of fuel quantity information using a configuration file..


When in the ATTAS configuration, the IHTP will output the data defined in section 3.4.2.2.20.2.

When emulating ARINC standard equipment, the IHTP shall output the fuel data in TBDformat.


3.4.2.2.17 Nowcast Emulation

The IHTP shall allow the operator to set weather information for transmission to the AOC (asnowcast data) via the Aircraft Model Window. (The detailed Nowcast information typesavailable are TBD.)




3.4.2.2.18 Aircraft Discretes

Commercial aircraft use discrete signals to determine the status of components that comprise thesystem. The IHTP will include functionality that allows the generation and reception of aircraft discretesignals.

The physical and electrical characteristics of the discrete signals are defined in D31.

Note: It is not anticipated that discrete signals will be used for the MA-AFAS trials. Instead, the datawill be transferred between the IHTP and the Avionics Rig via the ethernet.

The IHTP shall be able to generate 16 discrete output signals.


The IHTP shall provide the operator with an interface to manually control the discretesdefined in this section.


The IHTP shall allow the setting of discretes defined in this section by use of a configurationfile.


The IHTP shall provide for the reception of 16 discrete inputs.


The operator shall be able to examine the current state of any of the discrete signals usingthe Aircraft Systems Window.


The IHTP shall be capable of providing and receiving discrete signals in 0V/+28V or OpenCircuit/Short Circuit format using software control.


3.4.2.2.19 Joystick Interface

An interface for an analogue joystick will be provided, possibly via a MIDI/Joystick socket on a soundcard, to allow the manual control of the aircraft model.

The IHTP shall provide an interface for an analogue joystick.


3.4.2.2.20 Configuration of the Aircraft Interfaces

The IHTP will be capable of emulating a number of different types of aircraft not only as regards theaircraft capabilities, as defined above, but also with regard to the equipment fit and interfacesavailable. Currently identified for the MA-AFAS trials is the BAC1-11 and the ATTAS. Also included isthe basic ARINC equipment fit.

The IHTP shall provide the operator with the means to define what interfaces are to be used.




3.4.2.2.20.1 BAC1-11 Configuration

When configured to exercise the BAC1-11/RTAVS configuration, the IHTP shall only outputthe data identified as BAC1-11 in the above tables. Where no such indication occurs (e.g.GBAS), all of the identified data will be output.


3.4.2.2.20.2 ATTAS Configuration

The IHTP is required to be capable of emulating the data formats/timing of messages received fromand transmitted to the ATTAS flight simulator. This will allow testing of the interfaces prior toconnecting the MA-AFAS avionics to the ATTAS.

In this configuration, all data will be transferred using the ethernet connection. Four data blocks havebeen defined in the ATTAS Interface Description document for this purpose.

The ethernet protocols to be used for data transmissions whilst in the ATTAS emulation modeare TCP/IP using ports 5003 and 5005 (Time & Position Data only).


3.4.2.2.20.2.1 Aircraft State Vector Data Block

When emulating the ATTAS configuration, the IHTP shall output state data to the Avionics Rigusing a single ethernet transmission known as the Aircraft State Vector as defined in thefollowing Table:




Parameter Units Type #Bytes

Latitude Radians Double 8

Longitude Radians Double 8

Radar Altitude metres Long 4

Altitude Rate m/S Long 4

CAS m/S Long 4

Groundspeed m/S Long 4

TAS m/S Long 4

Mach Long 4

Bank Angle Radians Long 4

Heading Radians Long 4

Track Radians Long 4

Thrust Newtons Long 4

Fuel Used Newtons Long 4

Fuel Flow Kg/S Long 4

Wind Speed m/S Long 4

Wind Direction Radians Long 4

Outside Air Temperature Kelvin Long 4

Outside Air Pressure N/m2 Long 4

QNH N/m2 Long 4

Baro Altitude Metres Long 4

UTC Time Seconds Long 4

Airborne (WOW) Discrete(0..1) Boolean 4

EFCU Altitude Pushed Discrete(0..1) Boolean 4

Spoiler Discrete(0..1) Boolean 4

Lateral Guidance Active Discrete(0..1) Boolean 4

Profile Guidance Active Discrete(0..1) Boolean 4

Table 24 ATTAS Aircraft State Vector Data

3.4.2.2.20.2.2 Outer Loop Guidance Vector Data Block

The following table identifies the autopilot data, termed the Outer Loop Guidance Vector, tobe transmitted to the IHTP from the Avionics Rig when configured as an ATTAS:




Parameter Units Type #Bytes

Bank Angle Demand Radians Float 4

Abeam Altitude Metres Float 4

Next Level Altitude Metres Float 4

CAS Demand Metres/sec Float 4

Thrust Demand Newtons Float 4

Profile Mode Demand Discrete (0..4) Long 4

Regenerated Flag Discrete (0..1) Long 4

Activated Flag Discrete (0..1) Long 4

Toggle Bit Discrete (0..1) Long 4

Table 25 ATTAS Outer Loop Guidance Vector Data

3.4.2.2.20.2.3 EXO Data Block

The following table identifies the EXternal Output data block of the ATTAS. Note that theIHTP shall only output those data items identified. The other data parameters shall be set tozero.

[TBD / TBD ] [ IHTP-2218 ]

3.4.2.2.20.2.4 Time and Position Data Block

3.4.2.2.20.3 Standard ARINC Configuration

When configured as standard ARINC equipment, the IHTP shall output all the data identifiedshown in the above tables.


3.4.2.3 Display Emulation

This section defines the role the IHTP will play in supporting the display of data from the Avionicsrack. Initially, it was assumed that the Avionics would drive an EFIS as per ARINC725 and that theIHTP would be able to provide a ’repeater’ function to generate a display. Currently, the avionicsdesign incorporates a video output for the Navigation Display only so emulation of the displays is notrequired.

3.4.2.3.1 Primary Flight Display


3.4.2.3.2 Navigation Display.


3.4.2.3.3 Head-Up Display




3.4.2.3.4 Display Control Panel

The IHTP will provide a mechanism by which the operator can control the image presented on theNavigation Display.

The IHTP shall provide an emulation for the Display Control Panel (DCP).


The Aircraft Systems window shall be used to control the DCP emulation.


3.4.2.3.4.1 DCP Output Formats

The DCP emulator will be capable of providing the DCP data in one of the following formats:ARINC725 format using an ARINC429 linkBAC1-11 format using an RS232 serial data linkATTAS EXO format using the ethernet.

3.4.2.3.4.1.1 ARINC725 Display Control Panel

The DCP emulation shall be capable of commanding the ND display mode to Map, VOR, ILSor PLAN.


The DCP emulation shall be capable of commanding the avionics rack to display anycombination of Nav Aid, Waypoint, Route, Flight Path and/or airport symbology on the ND.


The DCP emulation shall be capable of commanding the scale of the map data displayed onthe ND from the options of 5, 10, 20, 40, 80 or 160 nm.


The DCP emulator shall output the following data to the avionics rack:



Tx Interval(mS)




Table 26 ARINC 725 DCP Data Outputs

Data formats of the discrete words output by the DCP emulator via the ARINC429 link shallbe as defined in section 5.6 of ARINC 725.


3.4.2.3.4.1.2 BAC1-11 Display Control Panel

The IHTP will be able to generate and output signals that emulate the functionality of the XKD EFIScontrol panel that is fitted to the RTAVS/BAC1-11. The emulation will use COM2 port of the IHTP.



The IHTP shall generate a graphical representation of the BAC1-11 DCP. The following figureshows a possible implementation that is representative of the real equipment:


10

32016080

4020

RANGE nm

LAT TAXIVERT

SECRTE

MAPMODE

NAVPOSN

WPTS APTSNAVAIDS

AHMIOFF

SPARE3RACAL/EFMS

ROUTE

PLAN

HOME

FWD

BACK

Figure 5 BAC1-11 DCP Emulation

The IHTP COM2 port shall be set up as follows:Baud Rate: 9600Number of Data Bits: 7Stop Bits: 1Parity: EvenHandshaking: None

[TBD / TBD ] [ IHTP-2051 ]

The transmission from the IHTP to the Avionics rig shall comprise 8 characters.

[TBD / TBD ] [ IHTP-2050 ]

Character 1 shall identify the status of the 6 range buttons. Data shall be in the range "1" to"6" (Hex 31 to 36) where "1" indicates that the 10nm range has been selected, and "6"represents the selection of the 320nm range.


Character 2 shall identify the status of the mutually exclusive "LAT", "VERT" and "TAXI"switches according to the following table:Switch Character HexOff(default) "0" 30LAT "1" 31VERT "2" 32TAXI "4" 34

[TBD / TBD ] [ IHTP-2055 ]

It shall not be possible to select any other combination of the "LAT", "VERT" and "TAXI"switches.

[TBD / TBD ] [ IHTP-2056 ]



Character 3 shall identify the setting of the "PLAN" switch as follows:Button Character HexOut (default) "1" 31In "2" 32

[TBD / TBD ] [ IHTP-2057 ]

Character 4 shall identify the status of the "FWD", "HOME" and "BACK" switches as follows:FWD BACK HOME Character HexOut Out Out (default) "0" 30Out Out In "1" 31Out In Out "2" 32Out In In "3" 33In Out Out "4" 34In Out In "5" 35In In Out "6" 36In In In "7" 37

[TBD / TBD ] [ IHTP-2058 ]

Character 5 shall identify the status of the "SEC RTE", "NAV POSN" and "MAP MODE"switches as follows:SEC RTE NAV POSN MAP MODE Character HexOut Out Out (default) "0" 30Out Out In "1" 31Out In Out "2" 32Out In In "3" 33In Out Out "4" 34In Out In "5" 35In In Out "6" 36In In In "7" 37

[TBD / TBD ] [ IHTP-2059 ]

Character 6 shall identify the status of the "WPTS", "NAVAIDS" and "APTS" switches asfollows:WPTS NAVAIDS APTS Character HexOut Out Out (default) "0" 30Out Out In "1" 31Out In Out "2" 32Out In In "3" 33In Out Out "4" 34In Out In "5" 35In In Out "6" 36In In In "7" 37

[TBD / TBD ] [ IHTP-2060 ]

Character 7shall identify the status of the "AHMI", "RACAL/EFMS" and "SPARE3" switchesas follows:AHMI RACAL/EFMS SPARE3 Character HexOut Out Out (default) "0" 30Out Out In "1" 31Out In Out "2" 32Out In In "3" 33In Out Out "4" 34In Out In "5" 35In In Out "6" 36In In In "7" 37

[TBD / TBD ] [ IHTP-2061 ]



The eighth character shall be the newline character, control-J (Hex 0A).

[TBD / TBD ] [ IHTP-2062 ]

3.4.2.3.4.1.3 ATTAS EXO Display Control Panel

The IHTP will output controls for the ATTAS Nav display using the EXO message defined in section3.4.2.2.20.

3.4.2.4 Airline Operations Centre Emulation

The IHTP will incorporate an Airline Operation Centre (AOC) emulation that allows an operator tocompile, send, receive and display messages that flow between the MA-AFAS Avionics and AOCground station(s).

Each AOC emulation will be presented in its own sub-window and the operator will have the samefacilities available for each AOC emulation.

It will be possible to emulate a number of AOC stations simultaneously; it is envisaged that the IHTPwill emulate the current AOC, the next AOC and, possibly, one other.

Note that the AOC emulation only provides AOC-Aircraft functions, it does not simulate AOCinteraction with any other actors.

The AOC emulation process encompasses the following facilities listed in D11:

• ATN GACS

• AOC Flight Plan

• AOC Maintenance

• Aircraft/AOC CDM

• AOC Asset Management

• AOC Operator HMI

The IHTP shall provide for the simultaneous emulation of at least 3 AOC’s.


The IHTP shall provide an AOC Comms Window for each AOC emulated to allow theoperator to control the actions of the AOC.


The operator shall also be able to control the actions of the AOC emulation by means of aconfiguration file.


The IHTP shall allow the operator to enter free-text messages for transmission to the aircraftvia the AOC Window.


The IHTP shall allow the operator to display free-text messages received from the aircraft viathe AOC Window.


The IHTP shall allow the operator to enter structured SIGMET information as defined in ICAOTBD for transmission to the aircraft via the AOC Window.




The IHTP shall allow the operator to enter structured METAR information as defined in ICAOTBD for transmission to the aircraft via the AOC Window.


The IHTP shall allow the operator to enter structured TAF information as defined in ICAOTBD for transmission to the aircraft via the AOC Window.


The IHTP shall allow the operator to enter structured Flight Plan information as defined inICAO TBD for transmission to the aircraft via the AOC Window.


The IHTP shall allow the operator to enter Collaborative Decision Making information (e.g.Re-route proposal, Re-route response, etc) as defined in TBD for transmission to the aircraftvia the AOC Window.


The IHTP shall allow the operator to display 4D Trajectory information received from theaircraft via the AOC Window.


The IHTP shall allow the operator to enter structured Loadsheet information as defined inICAO TBD for transmission to the aircraft via the AOC Window.


The IHTP shall allow the operator to display the returned Loadsheet Acknowledgmentmessage on the AOC window.


The IHTP shall allow the operator to enter Take Off Settings information as defined in TBD fortransmission to the aircraft via the AOC Window.


The IHTP shall allow the operator to enter Slot Allocation information as defined in TBD fortransmission to the aircraft via the AOC Window.


The IHTP shall allow the operator to enter NOTAM information as defined in TBD fortransmission to the aircraft via the AOC Window.


The IHTP shall allow the operator to enter aircraft systems failure information via the AircraftSystems Window.


The IHTP shall allow the operator to display aircraft systems failures information receivedfrom the aircraft via the AOC Window.


The IHTP shall allow the operator to enter simulated ACMS information via the AircraftSystems Window.


The IHTP shall allow the operator to display ACMS information received from the aircraft viathe AOC Window.




The IHTP shall allow the operator to enter aircraft fuel quantity information via the AircraftSystems Window.


The IHTP shall allow the operator to display fuel quantity information received from theaircraft via the AOC Window.


The IHTP shall allow the operator to enter Meteorological data as defined in TBD fortransmission to the aircraft via the AOC window.


The IHTP shall allow the operator to display Nowcast information received from the aircraftvia the AOC Window.


The IHTP shall allow the operator to display OOOI information received from the aircraft viathe AOC Window.


3.4.2.4.1 AOC Data Link Control

This section defines two aspects of the AOC Data Link functionality, that of the transport mechanismby which data is transferred between the air and ground systems, and the access mechanism bywhich the aircraft systems can initiate the use of the data link (Dynamic Link Logon - DLL).

The AOC Data Link Control process is not listed in D11 but is required in order to establish data linksspecifically for AOC communications, as opposed to ATC communications.

The system will support 3 transport mechanisms; Frame Mode IP, ATN over VDL4 or ATN over VDL2.The operator will be able to select which mechanism to use via an AOC Window.

Whenever an AOC data transfer is initiated, if the system is not logged on then it shall automaticallyinitiate a DLL sequence. The operator will also be able to manually initiate this sequence.

Note that the IHTP does not simulate the appearance and disappearance of ground stations (VDL2and VDL4) as this is beyond the scope of this simple test facility.

Also note that the IHTP does not provide for the injection of many failure types into the simulatednetwork. However, gross failures can be simulated by stopping the simulated end system fromcommunicating with the avionics.

Using the AOC window, the operator shall be able to define the connection type andsubnetwork for each instance of AOC.


The IHTP shall allow the operator to enter commands to perform DLL operations as defined inODIAC ORD via an AOC Window


The operator shall be able to view pilot responses related to DLL via an AOC Window


The operator shall be able to view pilot requests related to DLL via an AOC Window




3.4.2.5 Air Traffic Control Centre Emulation

The IHTP will incorporate an Air Traffic Control (ATC) emulation that allows an operator to compile,send, receive and display messages that flow between the MA-AFAS Avionics and ATC groundstation(s).

Since the ATN Manual requires at least 4 ground systems to be handled simultaneously by theavionics and MA-AFAS is intended to operate with 4, the IHTP will allow 5 simultaneous groundsystems of each transport mechanism (ATN and IP) to allow for the operator to prepare hand overactivities.

Each ATC emulation will be presented in its own sub-window and the operator will have the samefacilities available for each ATC emulation.

For each end system, the operator will be able to define whether it is a C-ATSU, N-ATSU, D-ATSU,or X-ATSU using the ATC Comms Window or an equivalent command in a Test Control File.

The progression of these definitions is normally:

• C-ATSU becomes X-ATSU

• N-ATSU becomes C-ATSU

• D-ATSU(1) becomes N-ATSU

• D-ATSU(2) becomes D-ATSU(1)

and this sequence will be provided automatically as a series of prompts for the operator.

Note that X-ATSU is normally removed from the defined list, but it can also be redefined as N-ATSUor a D-ATSU, using the ATC Comms Window an equivalent command in a Test Control File.

3.4.2.5.1 ATC Communications Messages

The IHTP will provide facilities for the generation of the following ATC message types:

• Delegated Manoeuvres: COSEP

• 4D Trajectory Negotiation: COTRAC and DYNAV

• Clearance Delivery: ACL, DSC, DCL and Taxi Management

• ADS-C

• CPDLC

• URCO (potentially)

3.4.2.5.1.1 Delegated Manoeuvres

Co-operative Separation Assurance is implemented by the generation of a request by the operatorusing ATC Comms Window or by an equivalent command in a Test Control File, based on a target (ortargets) controlled from the Traffic Window or from an equivalent command in a Test Control File.

The operator shall be able to enter commands for level flight Spacing manoeuvres via theATC Comms Window


The operator shall be able to enter commands for in-descent Spacing manoeuvres via theATC Comms Window




The operator shall be able to enter commands for lateral crossing and passing manoeuvresvia the ATC Comms Window


The operator shall be able to enter commands for vertical crossing and passing manoeuvresvia the ATC Comms Window


The operator shall be able to select a target for delegated manoeuvres using the ATC CommsWindow in conjunction with the Traffic Window.


The operator shall be able to view pilot responses to delegated manoeuvre requests on theATC Comms Window


3.4.2.5.1.2 4D Trajectory Negotiation

The operator shall be able to enter commands to perform COTRAC via the ATC CommsWindow


The operator shall be able to enter commands to perform DYNAV via the ATC CommsWindow


The operator shall be able to view pilot requests related to 4D trajectory negotiation via theATC Comms Window


The operator shall be able to view pilot responses related to 4D trajectory negotiation via theATC Comms Window


The IHTP shall be able to support C-ATSU and D-ATSU negotiation as allowed by ODIACORD


3.4.2.5.1.3 Clearance Delivery

The operator shall be able to enter commands to perform ACL clearances as defined inODIAC ORD via the ATC Comms Window


The operator shall be able to enter commands to perform DCL clearances as defined inODIAC ORD via the ATC Comms Window


The operator shall be able to enter commands to perform DSC clearances as defined inODIAC ORD via the ATC Comms Window


The operator shall be able to view pilot responses related to clearance delivery via the ATCComms Window




The operator shall be able to view pilot requests related to clearance delivery via the ATCComms Window


The IHTP shall be able to support C-ATSU and D-ATSU clearance delivery as allowed byODIAC ORD


3.4.2.5.1.4 ATN ADS-C

The avionics support Event, Periodic, and Demand contracts but not the Emergency contract, so theIHTP supports the same 3 types.

The IHTP shall allow the operator to generate ADS contracts of type Demand in accordancewith the ATN Manual of Technical Provisions ICAO 9705/2.


The IHTP shall allow the operator to generate ADS contracts of type Event in accordance withthe ATN Manual of Technical Provisions ICAO 9705/2.


The IHTP shall allow the operator to generate ADS contracts of type Periodic in accordancewith the ATN Manual of Technical Provisions ICAO 9705/2.


The IHTP shall allow the operator to view the responses from the avionics on the same sub-window of the ATC Comms Window as the contract was generated on.


3.4.2.5.1.5 CPDLC

Since the avionics support Baseline 1 CPDLC, so the IHTP will, as a minimum, support this standard.

The CPDLC process will also address the MA-AFAS extensions to the D11 facilities as detailed inTechnical Note TBD.

The IHTP shall allow the operator to generate CPDLC messages in accordance with the ATNManual of Technical Provisions ICAO 9705/2, Baseline 1 as defined for Petal II.


The IHTP shall allow the operator to generate CPDLC messages in accordance with the TBDMEDUP standard.


The IHTP shall allow the operator to generate CPDLC messages in accordance with the TBDNUP standard.


The IHTP shall allow the operator to view the CPDLC responses from the pilot on the samesub-window of the ATC Comms Window as the original message was generated on.


The IHTP shall allow the operator to view messages from the pilot on the sub-window of theATC Comms Window associated with the CPDLC end user address.




3.4.2.5.1.6 URCO

URgent COmmunications may not be implemented in the MA-AFAS trials.

Note that the URCO function is not supported by ATN, which can only send data after a Point-To-Point connection has been established.

The IHTP shall allow the operator to generate URCO messages in accordance with TBD.


3.4.2.5.2 ATC Data Link Control

As with the AOC communications, this section defines the control of the transport mechanism for ATCcommunications, and the access mechanism by which the aircraft systems enter a dialogue with ATC.

The ATC Data Link Control process encompasses the following facilities listed in D11:

• Dynamic Link Logon (DLL)

• Context Management (CM)

Note that the IHTP does not simulate the appearance and disappearance of ground stations (VDL2and VDL4) as this is beyond the scope of this simple test facility. However, it does simulate severalground end systems that can be logged into and out of, to represent acquiring and leaving C-ATSUs,N-ATSUs, and D-ATSUs.

Also note that the IHTP does not provide for the injection of many failure types into the simulatednetwork. However, gross failures can be simulated by stopping the simulated end system fromcommunicating with the avionics.

The ATC emulation will provide for the transmission of data using ATN or Non-ATN protocols via theVDL Mode 2 or VDL mode 4 interfaces. The operator will be able to select, on a message bymessage basis, which combination the message will utilise. The configuration will be set up using theATC Comms Window or a Test Control File.

DLL operations defined in Section 13 of the ODIAC ORD can be initiated independently on eachground system by the operator via the ATC Comms Window or an equivalent command in a TestControl File.

The status of each ground system data link logon will be displayed to the operator for monitoring, andchanges in status are recorded in the Test Results File.

The IHTP shall allow the operator to enter commands to perform DLL operations as defined inODIAC ORD via the ATC Comms Window


The operator shall be able to view pilot responses related to DLL via the ATC CommsWindow


The operator shall be able to view pilot requests related to DLL via the ATC Comms Window


3.4.2.6 Broadcast Communications Support

The IHTP will include the ability to generate traffic broadcast information and Flight InformationServices data for transfer to the Avionics rack.



3.4.2.6.1 Traffic Broadcasts

The Traffic Broadcasts process encompasses the following facilities listed in D11:

• ADS-B

• ATS-TIS

• TIS-B

Note that AOC use of ADS-B information is not shown here, as it is assumed to be provided by aground-ground link between ATC and AOC systems and therefore does not fall into the IHTP systemof interest.

The IHTP will allow for the transmission of traffic object data, held in the Traffic Database, to theavionics rack by way of the ADS-B and/or TIS-B Traffic Broadcast mechanism.

The operator will be able to globally enable/disable each transmission type, as well as individuallyidentify traffic objects for inclusion in a transmission.

All eligible traffic objects will be continually transmitted on a cyclic basis.

The ownship can be included as a TIS-B target to check that it is rejected as a separate target by theavionics.

The IHTP shall allow the operator to enable TIS-B transmissions for the ownship via theTraffic Window.


The IHTP shall allow the operator to monitor the ownship ADS-B transmissions via theOwnship Window.


Using the Traffic Control Window, the operator shall be able to include ownship data in theTIS-B transmissions.


Using the traffic control window, the operator shall be able to define the transmission rate foreach traffic object.


The IHTP shall include a pseudo-random drop out effect capability for both TIS-B and ADS-Btransmissions.


3.4.2.6.2 Flight Information Services

The Flight Information Service process encompasses the following facilities listed in D11:

• FIS-B

• DFIS

Note that FIS-C is not considered by MA-AFAS as it is thought to be a very inefficient use of availableVHF spectrum. Also note that NUP is not initially intending to provide SIGMET information or Option3, but it has defined SIGMET and Option 3 formats and the avionics and IHTP will be designed tosupport these.

For the IHTP, the FIS services supported are:



• D-RVR

• D-OTIS: ATIS; METAR; OFIS

• D-SIGMET

The IHTP shall allow the operator to generate FIS-B messages in accordance with NUP FIS-B Service Description via the ATC Window.


The IHTP shall allow the operator to view requests for FIS-B information from the pilot via theATC Window.


3.4.2.7 MCDU Emulation

The IHTP will provide a simple MCDU emulation that primarily facilitates the remote control of theavionics rack over an ethernet connection

A secondary use will be in the provision of an MCDU repeater display which can be used in parallelwith an ARINC standard MCDU. This facility will be used in the BAC1-11 to allow the display ofMCDU operation to personnel in the rear cabin area and will be used in conjunction with a NavigationDisplay repeater.

The IHTP will be able to emulate the functionality of a CMA-2014 MCDU (as defined by 408-A13985-003) using ARINC 429 or Ethernet.

Data entry and control is either manual or via automatic test files.

Display is on a dedicated PC Window with mouse-driven display control and keyboard-driven dataentry.

Note that this display only shows FMS outputs – it does not accept other ARINC 739A sources.

The IHTP shall provide a simple MCDU emulator that allows control of the avionics rackfunctions.


An MCDU window shall be provided for operator interaction with the MCDU emulator.


The Subsystem Address Label (SAL) output on address 172 of the ARINC429 message tothe avionics rack shall be set to 300 (Octal).


3.4.2.8 Traffic Control

The IHTP will include a Traffic Database that holds information about other traffic objects. The systemwill update the data for each traffic object dynamically to simulate a real world air traffic scenario. Theoperator can create new traffic objects using the Traffic Window or by an equivalent command in aTest Control File.

Each traffic object can be airborne or on the ground.

The traffic generator will output the data to the avionics rack as ADS-B and TIS-B targets for thedevelopment of CDTI and ASAS. This may also be used in conjunction with simulators that do nothave this capability.



Each traffic object is defined as an identity, satisfying ADS-B and TIS-B encoding requirements, andas a 4D trajectory.

The number of traffic objects that can be simultaneously generated is 1022 per the NUP TIS-BService Description and as adopted for the avionics definition (this assumes the figure of 1022 is theabsolute number of objects and could be 1022 duplicated ADS-B/TIS-B ones).

The operator can inject discrepancies between ADS-B values and TIS-B values to simulate the effectsof different data sources.

Similarly, the operator can set different Figures Of Merit (FOM) to cause selection of specific datasources by the avionics.

Traffic can also be generated from configuration files.

The IHTP shall allow the operator to specify up to at least 1022 traffic objects for inclusion inthe traffic database.


The IHTP shall allow the operator to generate traffic objects with qualifiers as defined in theManual on Detailed Technical Specifications for the VDL Mode 4 Data Link (ADS-B) and inthe NUP TIS-B Service Description (TIS-B) via the Traffic Window.


The IHTP shall allow the operator to specify 4D trajectories for each defined traffic object viathe Traffic Window.


The IHTP shall allow the operator to specify dynamically each defined traffic object as eitheran ADS-B object a TIS-B object, or a mixed ADS-B and TIS-B object via the Traffic Window.


The IHTP shall automatically remove the ADS-B transmit flag if the traffic object is more than250 nautical miles from the ownship.


The IHTP shall allow the operator to specify dynamically the ADS-B error value for anydefined traffic object via the Traffic Window.


The IHTP shall allow the operator to specify dynamically the TIS-B error value for any definedtraffic object via the Traffic Window.


The IHTP shall allow the operator to specify dynamically the ADS-B Figure Of Merit for anydefined traffic object via the Traffic Window.


The IHTP shall allow the operator to specify dynamically the TIS-B Figure Of Merit for anydefined traffic object via the Traffic Window.


The IHTP shall allow the operator to specify dynamically a pseudo-random lost messagedistribution for any defined traffic object via the Traffic Window.




The IHTP shall allow the operator to disable transmissions dynamically for any defined trafficobject via the Traffic Window.


The IHTP shall allow the operator to enable transmissions dynamically for any defined trafficobject via the Traffic Window.


The state data for each Traffic Object in the database shall be updated at a 1Hz rate


3.4.2.9 Test Control

The IHTP allows manual or semi-automatic test sequences to be performed from stored files andallows simultaneous results capture to file.

Depending on what functions are already available in the connected test equipment, the Test ControlWindow is used to enable or disable individual IHTP substitute functions.

Displays are provided to allow stand-alone operation of the Avionics Rack without being connected toa flight deck or simulated flight deck. These include Autopilot Mode Control Panel, MCDU, ATCcomms control, and AOC comms control.

Depending on the configuration for the test, messages are sent via ATN or Non-ATN path, throughVDL2 or VDL4 simulations. The configuration is set up using the Test Control Window or a TestControl File.

The test control window will provide facilities for the operator to individually configure the transmissionchannel of each emulation function (i.e. Ethernet or ARINC429/RS422/Discrete).

The IHTP shall provide facilities for the operator to individually or globally enable/disable theemulation functions.


3.4.2.9.1 AOC Control Window

Each ground system can be accessed via the AOC Comms Window, so up to 4 sub-windows areprovided to accomplish this.

The IHTP shall allow the operator to define up to two end systems with specified ATNaddresses


The IHTP shall allow the operator to define up to two end systems with specified IPaddresses


The IHTP shall allow the operator to start any defined end system communicating with theavionics


The IHTP shall allow the operator to stop any defined end system from communicating withthe avionics




The IHTP shall allow the operator to restart any defined end system communicating with theavionics


The IHTP shall allow the operator to control simultaneously all defined end systems’communications individually via the AOC Comms Window


3.4.2.9.2 ATC Control Window

Since the ATN Manual requires at least 4 ground systems to be handled simultaneously by theavionics and MA-AFAS is intended to operate with 4, the IHTP will allow 5 simultaneous groundsystems of each type (ATN and IP) to allow for the operator to prepare hand over activities.

Each ground system can be accessed via the ATC Comms Window, so up to 10 sub-windows areprovided to accomplish this.

The IHTP shall allow the operator to define up to five end systems with specified ATNaddresses


The IHTP shall allow the operator to define up to five end systems with specified IPaddresses


The IHTP shall allow the operator to start any defined end system communicating with theavionics


The IHTP shall allow the operator to stop any defined end system from communicating withthe avionics


The IHTP shall allow the operator to restart any defined end system communicating with theavionics


The IHTP shall allow the operator to define end systems as C-ATSU, N-ATSU, D-ATSU, X-ATSU types


The IHTP shall allow the operator to control simultaneously all defined end systems’communications individually via the ATC Comms Window


3.4.2.9.3 Interface Configuration Control

A window will be provided that allows the configuration of the IHTP to use the Ethernet interface inplace of any, or all, of the other ARINC429/RS422/Discrete interfaces.

The IHTP shall provide a window to allow the operator to select the transmission mechanismfor each data link to the avionics rack.


The IHTP links to the avionics rack shall be configurable using a pre-defined set up file.




The allowable combinations of equipment and communications link shall be as defined in thefollowing Interface Configurations Table.:


Interface Normalconnection

Ethernet Port #

Inertial Reference System ARINC429 TX1 50003

Attitude and Heading Reference System ARINC429 TX2 50004

Air Data Computer ARINC429 TX3 50005

Global Navigation Satellite System ARINC429 TX4 50006

SBAS ARINC429 TX5 50007

GBAS ARINC429 TX6 50008

VDL Mode 2 ARINC429 RX4 TBD

VDL Mode 2 ARINC429 TX7 TBD

VDL Mode 4 RS422 Port 1 RX TBD

VDL Mode 4 RS422 Port 1 TX TBD

Automatic Flight Control System ARINC429 TX8 50011

Automatic Flight Control System ARINC429 RX1 50012

Mode Control Panel ARINC429 TX9 50013

Engine Management System ARINC429 TX10 50014

Weight and Balance System ARINC429 TX11 TBD

MCDU Rx (Ethernet Server) ARINC429 RX3 50000

MCDU Tx (Ethernet Client) ARINC429 TX12 50001

MCDU Control Tx N/A 50002

Display Control Panel ARINC429 TX13 50015

Aircraft Conditioning Monitoring System Tx N/A 50016

Aircraft Conditioning Monitoring System Rx N/A 50017

Aircrew Warning System TBD 50018

ATTAS N/A 5003

ATTAS Time and Position N/A 5005

IHTP Time Sync N/A 50019

WOW Post MA-AFAS Post MA-AFAS

Self Test Post MA-AFAS Post MA-AFAS

MagHdg True Post MA-AFAS Post MA-AFAS

Doors Closed Post MA-AFAS Post MA-AFAS

Alert Post MA-AFAS TBD

Table 27 Interface Configurations



3.5 Configurations

3.5.1 Networked PC

The simplest configuration for the IHTP is as a networked PC. In this configuration, the system will beconnected to a standard network (such as the Rochester domain) and users will be able to log on withtheir Windows NT username and password. The normal PC facilities (e.g. Microsoft Office) will beavailable in this configuration.

3.5.2 In House Test Platform

The IHTP will be used for in house testing in one of 2 configurations. Initially, a Remote configurationwill be used whereby all data communications will be accomplished using the Ethernet connections.This will allow testing where the rig is housed in the rig room and the IHTP in the office.



3.5.2.1 Remote Configuration

ARINC429

FMU

PowerPC

CMU

PowerPC

10 BaseT Ethernet Hub

IHTP

Site Network

Tornado2 Server

VME Backplane

VDL Mode 4

HDDSCSI

DisplaySVGA

Figure 6 Ethernet Configuration

In this configuration, software will be downloaded to the target from the project Tornado2 server PCon the site network. The server will be on the site network and IHTP will be connected to the rig eitherdirectly to the ethernet hub, or via the site network. MCDU functionality will be provided by theemulator resident in the IHTP.

Data transmitted to the Avionics Rig will be transferred either as BAC1-11 data or ATTAS data usingthe ethernet ports defined above.

3.5.2.2 Local Configuration

When configured in the Local Configuration, the IHTP will connect to the avionics rig via theARINC429, RS422, discrete and Ethernet (for the Mode 2 VHF receiver) connections. It is notanticipated that the system will be connected to a site LAN whilst in this configuration although this



option will be available for the downloading of software to the target. The Avionics Rig, MCDU andIHTP will be co-located in this configuration.

ARINC429

FMU

PowerPC

CMU

PowerPC

10 BaseT Ethernet Hub

IHTP

Site Network

Tornado2 Server

VME Backplane

HDDSCSI

DisplaySVGA

MCDU

Figure 7 In House Test Platform Configuration

The MCDU will be used to control the actions of the Avionics Rig in this configuration.

3.5.3 BAC1-11/RTAVS Support

When configured to support the BAC1-11 trials aircraft and the QinetiQ Real Time, All VehicleSimulator (RTAVS), the system will be hosted on a laptop computer and will provide an AOCsimulation and the generation of audio alerts. Optionally, a repeater MCDU function will be providedon a second laptop computer. It is not anticipated that the IHTP will be connected to a site LAN whilstin this configuration. Local PC functionality will be available.



When used as a test and simulation harness, the IHTP will provide the above defined functionality toexercise the Avionics Rig via the ARINC 429 and/or ethernet interfaces.



MVME5100Power PC

(FMU)

IPMC761

MVME5100Power PC

(CMU)

IPMC761 MVME761-001

VMEBus

Avionics Rig

Aurora3 Monitor

A429-VARINC 429Interface 1

s3

c1

10 BaseTHub1

Ethernet

RGB+S

Ethernet

MVME761P2-001

P2 Adaptor

HDD SCSI

P2Adapter

VDL4

DADC

IRS

SBAS

DataPuddle

Printer

VDL2

EIU

GBAS

DigitalAutopilot

MCDU

Laptop PC

PMC408

Ethernet

IntercomSystem

BAC1-11/RTAVSConfiguration

(RS422)


J1

D5

D1

Trackball

DCP

D2

D4

D3

c2

D7 to D10

1

D6

J1

Figure 8 BAC1-11/RTAVS Configuration



Section 2 of D32 provides further information about the use of the IHTP with the RTAVS.

3.5.4 ATTAS Support

During the ATTAS flight trials, the IHTP software, hosted on a laptop PC, will provide support for thealert generation function by providing the interface between the Avionics Rig and the aircraft intercomsystem.



MVME5100Power PC

(FMU)

IPMC761

VMEBus

Avionics Rig

Aurora3Nav Display

(Monitor)


RGB

MVME761P2-001

P2 Adaptor

HDD SCSI

ATTASConfiguration

FMU:CMU

LAN (32)

MVME5100Power PC

(CMU)

IPMC761 MVME761-001

C1

1

P2Adapter

PMC408

CCD

Not Used

Ethernet for DataLoader (Laptop)

S3

VDL4(RS422)

C2

Aquarius5000

(RS232/422)

2 Ethernet

2 Ethernet

Ethernet1

Laptop PC

IntercomSystem

Hub

Ethernet

MCDU

VT220, IHTP orLaptop

(RS232)

Ethernet

Figure 9 ATTAS Configuration



3.6 Sortie Generation and Recording

The IHTP will be able to record data from any of the processes identified in Figure 2. This data cansubsequently be used to replace the functionality of the process by ’replaying’ the recorded datainstead of running the process.

Note. Repeatability of actions of the IHTP is only possible if the data recorded/replayed is the outputdata to the avionics rack.

3.6.1 File Formats

In order to aid the manual generation and reading of the recorded data, each file will be held in astandard format that can be read into a spreadsheet application. Each column of the datafile will havea text title followed by a Data label in brackets. E.g. “Pitch Angle (324)”. The exception to this is thefirst column which will have the Title Elapsed time and will store the elapsed time from the start of thesortie.

Input and output files shall be held in CSV (Comma Separated Variable) format.


The size of individual CSV Data files shall be limited to a maximum of 64000 records of up to255 elements (columns).


It shall be possible to incorporate sub-events into the CSV control file.




4 QUALIFICATION PROVISIONSNot Applicable



5 REQUIREMENTS TRACEABILITYTraceability information between the requirements in this specification and the prime equipmentrequirements specification are contained within the MA-AFAS project folder of the DOORSrequirements management tool. The information is available on-line or on request in printed form fromthe DOORS Project Specialist for the MA-AFAS programme, and is thus not included in thisdocument.



6 NOTES

6.1 Abbreviations

ACL ATC Clearance and Information Services

ACM ATC Communications Management Services

ADS-B Automatic Dependent Surveillance – Broadcast

AFCS Automatic Flight Control System

AFD Architecture Flow Diagram

AG Aircraft Guidance Process

AIC Airborne, Inhabited, Cargo

AID Architecture Interconnection Diagram

AOC Airline Operations Centre

ASA Airborne Separation Assurance

ATC Air Traffic Control

ATM Air Traffic Management

ATN Aeronautical Telecommunications Network

ATTAS Advanced Technologies Testing Aircraft System

ATSAW Air Traffic Situation Awareness

ATSU Air Traffic Services Unit

C-ATSU Current Air Traffic Services Unit

CCD Cursor Control Device

CDTI Cockpit Display of Traffic Information

CFMU Central Flow Management Unit

CMU Communications Management Unit

COSEP Co-operative Separation

COTRAC Common Trajectory Co-ordination Service

CPDLC Controller Pilot Data Link Communications

D-ATIS Data-link Automatic Terminal Information Services

D-ATSU Downstream Air Traffic Services Unit

DCL Departure Clearance Service

DFD Data Flow Diagram

DLL Data Link Logon

DSC Downstream Clearance

DYNAV Dynamic Route Availability Service

EFD Enhanced Data Flow Diagram

EMS Engine Management System

EOBT Estimated Off Block Time

FDPS Flight Data Processing System

FFAS Free Flight Air Space



FIS Flight Information System

FLIPCY Flight Plan Consistency

FMS Flight Management System

FMU Flight Management Unit

GACS Generic ATN Communications Service

GBAS Ground Based Augmentation System

GM Guide to Manoeuvre Process

GNSS Global Navigation Satellite System

GRAS Ground Based Regional Augmentation System

GT Guide to Trajectory Process

HDOP Horizontal Dilution of Precision

HIL Horizontal Integrity Limit

HMI Human Machine Interface

HUD Head Up Display

ICAO International Civil Aviation Organisation

ILS Instrument Landing System

MAS Managed Air Space

MCDU Multi-Function Control and Display Unit

MLS Microwave Landing System

ND Navigation Display

ODIAC Operational Development of an Integrated Surveillance and Air/GroundCommunications

OOOI Off, On, Out and In

PC Personal Computer

PFD Primary Flight Display

PM Performance Model

RFL Required Flight Level

RTAVS Real Time All Vehicle Simulator

RVR Runway Visual Range

SID Standard Instrumented Departure

SBAS Satellite Based Augmentation System

STAR Standard Arrival Route

SUA Special Use Airspace

TBD To Be Defined

TG Trajectory Generator Process

TIS-B Traffic Information Service – Broadcast

TMA Terminal Manoeuvring Area

UMAS Unmanaged Air Space

URCO Urgent Communication

VDL VHF Data Link



VDOP Vertical Dilution of Precision

VHF Very High Frequency

VIL Vertical Integrity Limit

WBS Weight and Balance System