Efficiency Metric Sdd

8/8/2019 Efficiency Metric Sdd

http://slidepdf.com/reader/full/efficiency-metric-sdd 1/43

EUROCONTROL

EUROPEAN ORGANISATION FORTHE SAFETY OF AIRNAVIGATION

1.1.1.1.1.1.1.1.1

EUROPEAN AIR TRAFFIC MANAGEMENT PROGRAMME

INTEGRASoftware Development

Documentation of ATM System

Efficiency Metric

INTEGRA

Edition : 1.0Edition Date : 16 February 2001Status : Working Draft

Class : EATMP



DOCUMENT IDENTIFICATION SHEET

DOCUMENT DESCRIPTION

Document TitleINTEGRA

Software Development Documentation of ATM System Efficiency Metric

Author:Laurent BOX

EWP DELIVERABLE REFERENCE NUMBER

PROGRAMME REFERENCE INDEX EDITION : 1.0INTEGRA EDITION DATE : 16 February 2001

Abstract

This document details the ATM Efficiency Software Development

• Software user guide

• Software architecture

• Links between specifications algorithms and metric computing

• Input and output file descriptions

• Example are listed in Annex A

Keywords

INTEGRA ATM System EfficiencyMetricsQuantification

CONTACT PERSON : Andrew Harvey TEL : 7413 DIVISION : ASC

DOCUMENT STATUS AND TYPE

STATUS CATEGORY CLASSIFICATION

Working Draft þ Executive Task o General Public o

Draft o Specialist Task þ EATMP þ

Proposed Issue o Lower Layer Task o Restricted o

Released Issue o

ELECTRONIC BACKUP

INTERNAL REFERENCE NAME :

HOST SYSTEM MEDIA SOFTWARE(S)

Microsoft Windows Type : MS Word 97 or HigherMedia Identification :



INTEGRASoftware Development Documentation of ATM SystemEfficiency Metric

INTEGRA

Edition: 1.0 Working Draft Page iii

DOCUMENT APPROVAL

The following table identifies all management authorities who have successively approvedthe present issue of this document.

AUTHORITY NAME AND SIGNATURE DATE

Contractor Project

Leader

Pascal LATRON

INTEGRA TechnicalManager

Michel Fages

INTEGRA ActionManager



INTEGRA INTEGRASoftware Development Documentation of ATM

System Efficiency Metric

Page iv Working Draft Edition : 1.0

DOCUMENT CHANGE RECORD

The following table records the complete history of the successive editions of the presentdocument.

EDITION DATE REASON FOR CHANGESECTIONS

PAGESAFFECTED

1.0 16 February 2001 Initial Issue All




INTEGRA

Edition: 1.0 Working Draft Page v

TABLE OF CONTENTS

DOCUMENT IDENTIFICATION SHEET ....................................................................................ii

DOCUMENT APPROVAL..........................................................................................................iii

DOCUMENT CHANGE RECORD............................................................................................ iv

TABLE OF CONTENTS............................................................................................................ v

EXECUTIVE SUMMARY............................................................................................................1

1. SOFTWARE OVERVIEW.......................................................................................................9

1.1 Introduction....................................................................................................................9

1.2 Language and Methodology ........................................................................................9

2. DESCRIPTION OF ATM SYSTEM EFFICIENCY ARCHITECTURE.................................10

2.1 Notations ......................................................................................................................10

2.2 Definitions....................................................................................................................10

2.2.1 Efficiency Metric Objects...................................................................................102.2.2 Interface Objects ...............................................................................................102.2.3 Basic Types.......................................................................................................112.2.4 Set-up File..........................................................................................................132.2.5 Efficiency Application action sequence.............................................................13

2.3 AircraftData class........................................................................................................20

2.3.1 Class definition Attributes..................................................................................202.3.2 Attributes Computed by Efficiency Algorithms..................................................202.3.3 AircraftData Computing Methods......................................................................21

2.4 WayPoint class ............................................................................................................22

2.4.1 Class definition Attributes..................................................................................22

2.4.2 Attributes Computed by Efficiency Algorithms..................................................222.5 Trajectory class ...........................................................................................................23

2.5.1 Class definition Attributes..................................................................................232.5.2 Attributes Computed by Efficiency Algorithms..................................................232.5.3 Trajectory Computing Methods .........................................................................23

2.6 AtcVolume class..........................................................................................................25

2.6.1 Class definition Attributes..................................................................................252.6.2 Attributes Computed by Efficiency Algorithms..................................................25

2.7 Economics class..........................................................................................................26

2.7.1 Class definition Attributes..................................................................................26



INTEGRA INTEGRASoftware Development Documentation of ATM

System Efficiency Metric

Page vi Working Draft Edition : 1.0

2.8 Analysis class..............................................................................................................27

2.8.1 Computed Attributes..........................................................................................272.8.2 Analysis Methods ..............................................................................................27

3. GENERATION OF ATM SYSTEM EFFICIENCY ...............................................................28

3.1 Efficiency Metric and costs definition ......................................................................28

3.2 Detailed Algorithms to calculate ATM Output .........................................................29

3.2.1 Ncm(TS) by volume and Trajectory..................................................................293.2.1.1 Ncm(TSi) by volume and Trajectory.............................................................. 293.2.1.2 Ncm(TS) by Volume and Trajectory.............................................................. 30

3.2.2 ATM Output........................................................................................................30

3.3 Detailed Algorithms to calculate ATM Input ............................................................30

3.3.1 Qcharges(TS)....................................................................................................303.3.1.1 Qcharges(TSi)............................................................................................ 303.3.1.2 Qcharges(TS)............................................................................................. 31

3.3.2 Qcrew(TS).........................................................................................................313.3.2.1 Qcrew(TSi) ................................................................................................. 313.3.2.2 Qcrew(TS)..................................................................................................31

3.3.3 Qmaintenance(TS)............................................................................................323.3.3.1 Qmaintenance(TSi) ..................................................................................... 323.3.3.2 Qecc(TSi) ...................................................................................................323.3.3.3 Qecc(TS).................................................................................................... 333.3.3.4 Qmaintenance(TS)...................................................................................... 33

3.3.4 Qfuel(TS)...........................................................................................................333.3.4.1 Fb(TSi) by volume and Trajectory... ........ ......... ......... ........ ......... ........ ......... .. 333.3.4.2 Qfuel(TSi)................................................................................................... 343.3.4.3 Qfuel(TS)....................................................................................................34

3.3.5 Qdelay(TS) ........................................................................................................343.3.5.1 Delay (TSi) by volume.................................................................................. 343.3.5.2 Qdelay(TSi) by volume................................................................................ 353.3.5.3 Qdelay(TS)................................................................................................. 353.3.5.4 Delay(TS) by volume................................................................................... 353.3.5.5 Qdelay(TS) by volume.................................................................................35

3.4 Detailed Algorithms to calculate ATM System Efficiency......................................36

4. CONCLUSION.....................................................................................................................42

5. ANNEX A 43




INTEGRA

Edition: 1.0 Working Draft Page vii

Page left intentionally blank



INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric

Page 8 Working Draft Edition : 1.0

EXECUTIVE SUMMARY

This document presents the detailed development of the INTEGRA Air Traffic ManagementSystem Efficiency Metric software, and the user guide to allow the validation of this metric.

This tool have been created according to the INTEGRA Metrics MethodologiesDetailed Specification of ATM System Efficiency Metric Inputs – Processing – OutputsDocument, version 3.0.

The production of this metric and methodology are based on the recommendations andconclusions of the final report “C.A.R.E. – INTEGRA – ATM EFFICIENCY METRICS”delivered by STERIA, and CENA (15/02/2000).

Aim of the INTEGRA ATM System Efficiency metric is to be a standard metric system for usein any simulation facility in European Civil Aviation Conference (and potentially world wide)for fast time and real time simulations to quantify the efficiency of trajectories flown withindifferent ATM systems.

Efficiency Metric workpackage is closely linked to other INTEGRA Workpackages namelySafety, Capacity, Environmental Impact and Traffic Sample Generator.

Thus the reference values for the Metric will be provided by the Traffic Sample Generator(TSG).

The elements of the ATM system to analyse using the Efficiency Metric, and the output

metrics have been described in the INTEGRA Metrics Methodologies Detailed Specificationof ATM System Efficiency Metric Inputs – Processing – Outputs Document, version 3.0. Thisdocument is the basis of the current software description. The same plan, numbers andnotations are used.

The Efficiency Metric Tool has been built in C++ language, using Microsoft Visual C++development tool. It is a standalone application which does an input data files parsing,computes efficiency metrics and writes outputs to output data files.

The coding methodology is object oriented. It allows a developer to adapt the input filetreatment to another file types or formats than the one used for tests. The current documentgives a detailed view of the different classes.

The input data are read from files (format “csv”) that are produced after Real Timesimulations by Eurocontrol Experimental Center Analysis Team. Those data do not cover allthe input needs for Efficiency Metric computing, and there is description of a model of inputdata files for this module. This document describes only test input files, that can be usedafterwards during the validation phase, nevertheless.

The Efficiency software needs a set-up file to correctly load data. This file is described in thisdocument.



INTEGRASoftware Development Documentation of ATMSystem Efficiency Metric

INTEGRA

Edition : 1.0 Working Draft Page 9

1. SOFTWARE OVERVIEW

1.1 Introduction

This document explains how the Efficiency metrics are computed by the EfficiencyMetric software, and how it must be used in order to get Efficiency output data.

The Efficiency Metric Module is a standalone application that parses input data files inorder to get Efficiency Metric Inputs and write Efficiency Metrics Outputs to a set of outputfiles.

The Efficiency Metric computing (see INTEGRA detailed specifications - §1) isexplained by the following scheme:

The inputs are defined by input file data, and consist in 2 set of data:

-ATM System input, which is a collection of productivity factors. It is given by thecomparison between the requested and actual trajectories of the traffic sample.

-ATM System Outputs, which is the qualified minimum minute of flight in the differentairspace types (ATC Volumes). This information is given by the requested - ideal - flowntrajectory.

The Efficiency Metric outputs are written into output files, and must allow both adiscrete Aircraft analysis and a global overview of the ATM System.

1.2 Language and Methodology

The Efficiency Metric Module is developed in C++, with the Microsoft Visual C++ 6.0tool. This language was chosen in order to allow a later integration of the different Efficiencymodules (Capacity, Safety,…).

The Efficiency Metric application was defined in order to respect as much as possiblean object oriented architecture. Meanwhile a collection of basic types was created to makevariable definition easier. This application can be easily modified in case input/output datafiles format modification. Each class is embedded in a separate module (“.h” and “.cpp”).

Ø ATM SystemInputs

Ø ATM SystemOut uts

INTEGRAEfficiency Metric

Inputs INTEGRAEfficiency MetricAlgorithms and

Process

INTEGRAEfficiency Metric

Outputs





2. DESCRIPTION OF ATM SYSTEM EFFICIENCY ARCHITECTURE

2.1 Notations

This document notation refers to the notations of the Detailed Specifications of ATMEfficiency Metrics document, § 2.1.

2.2 Definitions

2.2.1 Efficiency Metric Objects

The following objects compose the Efficiency Metric application:

AircraftData this object stores the Discrete Aircraft data, and it is one element of theTrafficSample. A requested trajectory and an actual trajectory composean AircraftData. This object can compute and set the costs associatedto a single flight of the TrafficSample.

Analysis this object loads the metric computing algorithms and stores the globaloutput data. It loads the object computing methods to get ATMInput,ATMOutput and efficiency values.

AtcVolume this object is one volume of the ATM System, and compose theAtcSpace. It is defined according to HEIDI convention. Each

AtcVolume contains parameters that qualify metrics.

Economics this object contains all the economic global data.

Trajectory this object stores a flight path, composed by WayPoints. For each flightpath, a set of parameters allows to qualify this path exactly. This objectcan access to the WayPoint, to update their attributes.

WayPoint this is the discrete element of a trajectory. It contains the flightparameters when it is over-flown.

The following two types are not object but they are considered as object containers:

AtcSpace: it is the collection if all AtcVolumes of the ATM System.

TrafficSample: it is the collection of AircraftData of the ATM System.

FlightPlan: it is the collection of WayPoints, which defines the flown path of a trajectory.

2.2.2 Interface Objects

The following objects are not parts of the Efficiency Metric Algorithm. Their aim is either tocreate the Efficiency objects from the input data files or to print out the output results to files




INTEGRA


InputInterface this object reads the set-up file, the data input files and calls thecreation of the TrafficSample (AircraftData, Trajectories, andWayPoints), the AtcSpace and the Economics objects.

OutputInterface this object writes the output data to files

2.2.3 Basic Types

A set of basic types is defined to allow storing elementary data:

TIMETYPE this type allows storing both a time string in hhmmss format and thenumber of seconds since 00h00m00s.

LEVELTYPE this type allows storing the level value: either a level in 100’s of feet ifthe level type is Altitude, or the Flight Level Number if the type is FlightLevel. This type also stores the level type.

SPEEDTYPE this type allows storing the speed value: either a TAS in Kt. if the speedtype is TAS, or the Mach Number if the type is Mach. This type alsostores the speed type.

POINTTYPE this type allows storing a geographic point, with an ident, longitude andlatitude co-ordinates.

FLOATVECTORTYPE this type is a float value container.

XXPERCENTAGECOSTTYPE this type store a acceleration percentage band and itscorresponding cost in $/min.

XXECCTYPE vector that store percentage bands for one engine type

For each of these types, a pointer type is defined: PLEVELTYPE, PSPEEDTYPE,PPOINTYPE and PTIMETYPE.

The names are stored in string types. This type allows an easy string management. Theinput specified string data are all stored in string. It allows to get out of the format restrictionsof the specifications (see paragraph 2.3 and next).

2.2.4 Input Interface

The Efficiency Metric Module gets its data from csv files (separator “;”), in order to createATM System objects that are analysed by the Efficiency algorithms.

2.2.4.1 InputInterface class

This class contains the methods that read input files and create ATM System objects. Itsdesign depends on the Input file format. It also initialises the Atc Space of the ATM System.





As no definitive format was described to fill the Efficiency Metric module, it is based on theoutput data of Real Time Simulations that were done at the Eurocontrol Experimental Center,

Bretigny.

The Object Oriented methodology that was chosen to create this application allowsdevelopers to easily modify the Input Interface in order to adapt the Efficiency Module toother types of files.

• Definition Attributes

fSetupFile - fstream - file descriptor for the set-up file

fAircraft - fstream - file descriptor for the aircraft file

fRequestedTraj - fstream - file descriptor for the requested trajectory

WayPointsfActualTraj – fstream - file descriptor for the actual trajectory WayPoints

fielBuff - string - current read line storage

• Methods

initAtcSpace(AtcSpace &);

This method creates the different AtcVolume objects according to the HEIDI documentation:

TAXI, TWR, APP, FIR, UIR.

setUpEfficiencyBasic(AtcSpace &, Economics &);

This method reads the Set-up file (see 2.2.4.2) in order to store the name of the differentinput files that give the ATM system data, the global cost values that describe the economicenvironment, and the quality coefficients that are linked to each AtcVolume of the AtcSpace.

setUpTrafficSampleAircraftData(TrafficSample &, AtcSpace);

This method reads line by line, the Discrete Aircraft Data input files, and generate theAircraftData objects and the traffic sample. Only general flight information are stored, but thetrajectories are not.

setUpTrafficSampleRequestedTrajectory(TrafficSample&);

This method reads the requested trajectory data input file, generates the WayPoints of therequested Trajectory of an existing AircraftData.

setUpTrafficSampleActualTrajectory(TrafficSample&);




INTEGRA


This method reads the actual trajectory data input file, generates the WayPoints of the actualTrajectory of an existing AircraftData.

Once those three methods are called, the TrafficSample is fully generated, and the EfficiencyMetric algorithms can be applied.

2.2.4.2 Set-up File

EFFICIENCY SETUP FILE: EfficiencySetup.csv

The InputInterface reads this file. Its aim is to set up the name of the other input files to read,to initialise the economical cost (Economics) and AtcSpace quality parameters. It must belocated in the same directory than the Efficiency Metric Application.

Description :

The first line is a simulation or data description line.

For each line, a description field is set in the first column, and the corresponding value is setcolumn 2.

LINE FIELD DESCRIPTION VALUE FORMAT

2 TITLE OF THE SIMULATION (NOT USED) STRING

3 AIRCRAFT DATA FILE (LOCATION) STRING

4 REQUESTED TRAJECTORY (LOCATION) STRING

5 ACTUAL TRAJECTORY (LOCATION) STRING

6 SPEED DOMAIN STRING

7 LEVEL DOMAIN STRING

8 QLABOUR FLOAT

9 QCAPITAL FLOAT

10….30

FOR EACH ATCVOLUME OF ATCSPACE,

KCOST

KDELAY

KENVT

KX

FLOAT

FLOAT

FLOAT

FLOAT





2.2.4.3 Discrete Aircraft Data Input File

This file is not the definitive version of an Integra input file. Here is a description of thedifferent columns of this file. Its common name is “Aircraft file”.

The first line is the column description line

COLUMN DESCRIPTION

1 CALLSIGN

2 ADEP : DEPARTURE AIRPORT

3 ADES : ARRIVAL AIRPORT

4 ACTYPE : AIRCRAFT TYPE5 FLIGHT TYPE : (S = CIVIL / M = MILITARY)

6 FPL : FLIGHT PLAN

7 SECTORS : SECTORS LIST

8 SID

9 STAR

10 PISTE_A : ARRIVAL RUNWAY

11 PISTE_D : EDPARTURE RUNWAY

12 IFR_VFR : (I=IFR / V=VFR)

13 NAV START : NAVAID START TIME

14 NAV END : NAV END TIME

15 ENGINE TYPE

16 AIRLINE CREW COST ($)

17 MAINTENANCE COST ($)

18 ECC COST ($)

19 AIRLINE

20 ALTN

21 FUEL (TONS)

22 ETA (TIME)

23 ETD (TIME)

24 MIN RPM ACCELERATION PERCENTAGE

25




INTEGRA


26 50%ECC COST

27 60%ECC COST

28 70%ECC COST

29 80%ECC COST

30 90%ECC COST

31 100%ECC COST





2.2.4.4 Trajectory data Input File

This file is not the definitive version of an Integra input file. Here is a description of thedifferent columns of this file. Its common name is “Navigator File”.

The first line is the column description line

COLUMN DESCRIPTION

1 REPTIME : SIMULATION TIME

2 CALLSIGN : A/C CALLSIGN

3 LAT : LATITUDE (1/10000)

4 LON : LONGITUDE (1/10000)

5 HEAD : HEADING (1/10)

6 TAS : THRU AIR SPEED (1/10)

7

ROCD : RATE OF CLIMB / DESCENT

IF VALUE IS >=65000 ==> NOT CLIMB./DESCEND

(FEET/MINUTES)

8 ROT : RATE OF TURN (DEGREES/MINUTES)

9 SSRCODE

10 AFL : ACTUAL FLIGHT LEVEL

11 RFL : REQUESTED FLIGHT LEVEL

12 CFL : CLEAR FLIGHT LEVEL

13 FLIGHTID : A UNIQUE NUMBER FOR EACH AIRCRAFT (SAME ASCALLSIGN)

14 SECTOR : SECTOR (BASED ON FREQUENCY)

15

PHASE:

1 :TAKEOFF

2 : SID




INTEGRA


3 : EN-ROUTE

4 : STAR

5 :LANDING

6 :HOLDING

7 :UNKNOWN

16

ATTITUDE:

1 : CLIMB

2 :LEVEL

3 :DESCENDING

17

ACTIVE :

0 : ACTIVE,

1 :ENDED

18

RULE :

0 : VFR

1 : IFR

19 FUEL : FUEL CONSUMPTION (IN G)

20 CHARGES COST ($)

21 RPM





2.2.5 Remarks about input data set

It is obvious that not all the values are loaded into Efficiency Metric. Meanwhile, some values

are missing. As the current phase needs testing, and that it is not realistic to invent somedata without any basis, modifications were added to the specifications (Detailed Specificationof ATM System Efficiency Metric Inputs – Processing – Outputs Document, version 3.0).

• Fuel :

The on-board fuel at the beginning of the simulation is not available. The amount of fuel burnto evaluate qFuel has been chosen, instead of the remaining fuel.

• ETD and ETA

ETD and ETA are not defined in simulation outputs.

v Elapsed Time

Simulations do not take the ADEP and ADES in account during the flight except if it is anAirport or TMA simulation. The ETD and ETA are not defined as input data. It has beenchosen to take the first WayPoint as the reference of the elapsed time computing.

v Flown Distance

For the same reasons, it has been chosen to take the first WayPoint as the reference of theelapsed time computing. And Efficiency Metric application computes the flown distance.

• ALTN

ALTN is not filled by Aircraft Data files. An imaginary AIRPORT has to be invented. But thisdata is not used during Efficiency metric computing.

• AIRLINE

AIRLINE is not filled by Aircraft Data files. An imaginary name has to be invented. But thisdata is not used during Efficiency Metric computing.

• ENGINE CHARASTERISTICS

The following fields are not filled by simulations.

v Engine Type

v Rpm

v Percentages of accelerations

v Minimum acceleration percentage




INTEGRA


2.3 Efficiency Application : action sequence

The following scheme shows the Efficiency Main module architecture.Set-up file reading by InputInterface

AtcVolume initialisationEconomics initialisation

Discrete Aircraft data input file reading by InputInterface

AircraftData loadingEach element of the traffic sam le is defined and added to TrafficSam le.

Requested Trajectory data input file reading by InputInterfaceRequested Trajectory loading

Each requested Trajectory WayPoint is defined and added to the requested AircraftDataTra ector

Actual Trajectory data input file reading by InputInterface

Actual Trajectory loadingEach actual Trajectory WayPoint is defined and added to the actual AircraftData

Trajectory

Analysis: computing and set up:The following values are computed

In each Trajectory of each AircraftData, and each AtcVolume:Ncm(TSi)volume, Fb(Tsi)volume

In each AtcVolume of AtcSpace :actual and requested Ncm(TS), delay(TS), Qdelay(TS)

In each AircraftData of TrafficSample:

Qcrew(TSi), Qecc(TSi), Qcharges(TSi), Qdelay (TSi), Qmaintenance(TSi)

In Analysis :Qcrew(TS), Qecc(TS), Qcharges(TS), Qdelay (TS), Qmaintenance(TS),

ATMInput, ATMOutput, Efficiency

OutputInterface write the output data to 4 files:

Discrete Aircraft OutputFuel Burn by Aircraft, Trajectory and AtcVolume Output

Delay and Qdelay by Aircraft and Volume OutputGlobal Traffic Sample Output





2.4 AircraftData class

An AircraftData class contains one element of the TrafficSample. It also storesATMInput costs (Qmaintenance, Qcrew, Qfuel, and Qcharges).

2.4.1 Class definition Attributes

callsign - string : flight callsign.

adep - string : flight departure aerodrome (ICAO location indicator).

ades - string : flight destination aerodrome (ICAO location indicator).

altn - string : alternate aerodrome (ICAO location indicator).

airline - string : flight airline name.

acType - string : aircraft type (according to ICAO Doc 8643)

engineType - string :engine type name (with manufacturer name)

etd - PTIMETYPE : estimated time of departure at ADEP.

eta - PTIMETYPE : estimated time of arrival at ADES.

requestedTraj - Trajectory * : requested Trajectory

actualTraj -Trajectory * : actual Trajectory

fuel - float : fuel burn at the beginning of the flight path (default = 0)

maintenanceCost - float : Cost of the maintenance for this flight.

AirlineCrewCost - float : Cost of the Commercial and technical crew for

this flight

eccCost - float : Cost of engine maintenance

percentageMinEcc – float - engine rpm acceleration percentage critical for

enginemaintenance.

XXEcc – vXXPERCENTAGECOSTTYPE - bands of %ECC with corresponding costvalues.

2.4.2 Attributes Computed by Efficiency Algorithms

The AircraftData object contains methods that compare the requested with actualTrajectories, in order to define additional costs and delays.

delay - FLOATVECTORTYPE : additional time between the actual and requested

trajectory, for each AtcVolume.

qDelay - FLOATVECTORTYPE: additional cost between the actual and requested

trajectory, for each AtcVolume.qfuel- FLOATVECTORTYPE: additional cost of fuel between the actual and

requested trajectory, for each AtcVolume.

qEccTsi - float: Cost of critical use of engine

qCrew- float: Additional Crew cost between actual and requested

trajectories.

qCharges - float: Additional Charges costs between actual and requested

trajectories.

qMaintenance - float :Additional Maintenance cost between actual andrequested trajectories.

qFuelTSiAllVolume - float : Sum of all the qFuel[i] (i = size of AtcSpace)




INTEGRA


2.4.3 AircraftData Computing Methods

The AircraftData object contains methods to compute and set its computed attributes, and toset up its trajectory attributes.

• QCharges

For the current AircraftData qCharges is set by:

setQCharges()

• QCrew

For the current AircraftData qCrew is set by:

setQCrew()

• Delays

Each delay attribute of AtcVolume of AtcSpace is set by :

setDelay(AtcSpace)

Each qDelay attribute of AtcVolume of AtcSpace is set by :

setQDelay(AtcSpace)

• QEccTSi

For the current AircraftData qEccTsi is set by

setQEccTSi()

• FuelBurn

Each qFuel and qFuelAllVolume attributes of AtcVolume of AtcSpace are computed and setby :

setQFuelTSi(AtcSpace, Economics)

• QMaintenance

For the current AircraftData qMaintenance is set by:

setQMaintenance()

NB : The XX%ECC are inserted to XXEcc attribute once the AircraftData is created andinitialised, using the method :

addEngineXXCost(int, float);





2.5 WayPoint class

This class defines a flown point of a trajectory.


coord (PPOINTTYPE) : the WayPoint Id.

level (PLEVELTYPE) : the flight level above the WayPoint.

speed (PSPEEDTYPE) :the flight speed above the WayPoint.

overflightTime - PTIMETYPE defines the flight overflight when the flight

overflies the WayPoint.

atcVolumeName - string : Type of airspace when the flight the WayPoint

rpm -int : engine rpm value when the flight overflies the WayPoint.


elapsedTime -int : the elapsed time (sec) from first trajectory WayPoint to

the WayPoint.

flownDistance - float : the flown distance (Nm) from the first trajectory

WayPoint to the WayPoint.

fuel - float : aircraft mass of burn fuel since the first WayPoint to the

WayPoint.

The WayPoint object set up is done when it is added to a Trajectory. At this time, computedattributes are filled.




INTEGRA


2.6 Trajectory class

This class defines the actual and requested flown flight plans of an AircraftData object.


td - PTIMETYPE - Time over the first WayPoint of the trajectory.

ta - PTIMETYPE - Time over the last point of the trajectory.

chargesCost - float - route charges and Aerodrome taxes for the trajectory

nbWpt -int - number of WayPoints (WPT) stored in the trajectory

wpt - FLIGHTPLANTYPE - WayPoints vector that makes the flown flight path.

qEccTraj - float - Cost of the number of seconds the engine is used over

its Rpm acceleration percentage limit considering the wholetrajectory.


ncmTsi - FLOATVECTORTYPE - vector of elapsed time between the entry and

exit of each AtcVolume, qualified by the AtcVolume coefficient kX.

fbTsi - FLOATVECTORTYPE - FuelBurn between the entry and exit of each

AtcVolume.

flightTime -int - number of seconds between the start and the end of the

flown flight path.

nmRpmlim - float - number of seconds the engine is used over its Rpm Limit

considering the whole trajectory.

2.6.3 Trajectory Computing Methods

The following method allows to set up WayPoint when they are added to the wpt attribute(flight path).

• NcmTSi

For a given volume of AtcSpace the ncmTsi attribute is set by :

setNcmTSi(AtcSpace, int)

• FbTsi

For each volume of AtcSpace the fbTsi attribute is set by:

setFbTSi(AtcSpace)

• Flight Time

The Flight Time between the first point and the last point of the trajectory is set by:

setFlightTime()

• qEccTraj

For a given Rpm acceleration percentage limit, and %ECC engine reference bands, qEccTrajattribute is computed and set by:





setNmRpmLim(int)

• Building the Flight Path

The flight path creation is done by adding WayPoints at the end of a container (vector).

Each time a new WayPoint is added, the fuel, elapsedTime, flownDistance of the newWayPoint are set up, and Trajectory too.

- Elapsed time

The elapsed time value between two WayPoint is given by :

computeElapsedTime(WayPoint, WayPoint)

Arg1 is the first Wpt, Arg 2 is the second one

- Flown distance

The flown distance value between two points is given by :

computeFlownDistance(WayPoint, WayPoint)

Arg 1 is the first Point, Arg2 is the second one.




INTEGRA


2.7 AtcVolume class

An AtcVolume object only store data associated to the AtcSpace definition.

The different AtcVolume are initialised via InputInterface initAtcSpace() method


phase - string - AtcVolume Name (according HEIDI norm)

kEnvt - float - Quality coefficient for Fuel Burn.

kX - float - Quality coefficient for number of controlled minutes.

kDelay - float - Quality coefficient for number of minutes of delay.

KCost - float - Quality coefficient to determine : 1 by default.

2.7.2 Attributes Computed by Efficiency AlgorithmsThe following attributes are computed using Analysis methods.

requestedNcmTS - float - Qualified elapsed time between the entry and the

exit of the volume for all traffic sample req trajectory

actualNcmTS - float - Qualified elapsed time between the entry and the exit

of the volume for all traffic sample act trajectory

DelayTS - float - delay (in sec) between requested and actual trajectory

for the traffic sample.





2.8 Economics class

An Economics object only store data associated to the Economics definition.


qLabour - float- Cost ($) of the total work force for the studied ATM

System.

qCapital - float - Cost ($) of valuation of all the equipment and ground

property for the studied ATM system.

fuelCost - float - Cost ($/ton) of aviation fuel on the period of time of

the simulation.




INTEGRA


2.9 Analysis class

This class is defined to apply efficiency metric algorithm, using the different objects of theapplication. It stores global output data and metrics, before they are printed out to file.

2.9.1 Computed Attributes

requestedATMOutput - float - Valuation for all the outputs of the ATM

System (requested Trajectory)

actualATMOutput - float - Valuation for all the outputs of the ATM System

(actual Trajectory)

qEccTS - float - additional cost of engine cycling between actual and

requested trajectory for the whole traffic sample.

qChargesTS - float - additional cost of charges between act and req

trajectory for the whole traffic sample.

qMaintenanceTS - float - additional cost of maintenance between act andreq trajectory for the whole traffic sample.

qCrewTS - float - additional airline crew cost between act and req

trajectory for the whole traffic sample.

qDelayTS - float - cost of delay for the whole traffic sample.

qFuelTS - float - additional cost of fuel between act and req trajectory

for the whole traffic sample

ATMInput - float - Valuation for all the inputs of the Atm System.

Efficiency - float - given ATM System efficiency (equals ATMInput /

ATMOutput).

2.9.2 Analysis Methods

When an Analysis object is created, it automatically computes the Efficiency Metric values,according to the TrafficSample, the AtcSpace and the Economics.

Analysis(TrafficSample, AtcSpace, Economics)





3. GENERATION OF ATM SYSTEM EFFICIENCY

This section describes how the specified algorithms required to generate the ATM SystemEfficiency Metric are applied.

3.1 Efficiency Metric and costs definition

The Efficiency Metric e is given by the following formulae (see Detailed Specifications of ATMSystem Efficiency Metric §3.1) :

Input ATM Output ATM __=ε

DelayFuelenance MaCrewesChCapital Labour

N

i

FIRUIR APPTWRTAXI VolumeVolume X req

Volumecm

QQQQQQQ

K TSi N TS

++++++

×

=∑=

∈

intarg

1

},,,,{,][])([

This formulae gives the ATM Output definition:

∑=∈×=

TS N

iFIRUIR APPTWRTAXI VolumeVolume X reqVolumecm K TSi N Output ATM

1},,,,{,][ ])([_

And the ATM Input definition:

DelayFuelenance MaCrewesChCapital Labour QQQQQQQ Input ATM ++++++= intarg

_

As QLabour and QCapital are given as input global values, ATM Input is given once thefollowing costs are computed according to the Efficiency Metric formulae.

( )i N

i

esCh TSQQTS

esCh∑=

=1

arg arg

( )i N

i

Crew TSQQTS

Crew∑=

=1

( ) ( )i N

i

i

N

i

TSQTSQQTSTS

∑∑==

+=11

eMaintenanc EcceMaintenanc

( )Volume

i

N

i

Fuel Volume Envt

TS

Fuel K TSQQ

×= ∑

=,

1

( )Volume

i

N

i

Delay Volume Delay

TS

Delay K TSQQ

×= ∑

=,

1




INTEGRA


3.2 ATM Output

3.2.1 Ncm(TS) by volume and Trajectory

3.2.1.1 Ncm(TSi) by volume and Trajectory

ATM Output is given by :

∑=

∈×=TS N

i

FIRUIR APPTWRTAXI VolumeVolume X reqVolumecm K TSi N Output ATM 1

},,,,{,][ ])([_

N cm(TSi)volumereq equals the elapsed time in a given ATC Volume, for a single aircraftrequested trajectory.

In the Efficiency Metric Output Data definition, Ncm(TSi)volumereq equals the previous valuequalified by the coefficient kXvolume.

First entry and exit of the AtcVolume must be determined. It is done by :

Trajectory::determineCPI(AtcVolume, int&, int&)

Arg 2 (Arg 3) is the Volume entry (exit) WayPoint indice on the trajectory.

The previous function is called within the Ncm(TSi) computing procedure :

Trajectory::computeNcmTsi(AtcVolume atcVE)

{

int cpni, cpxi;if (determineCPI(atcVE, cpni, cpxi) == 1) {

if (cpni !=cpxi){

return (atcVE.getKX()* (wpt[cpxi].getOverflightTime()->timesec

- wpt[cpni].getOverflightTime()->timesec));

}

else return 0;

}

else return 0;

}

Then the value is stored in Trajectory::ncmTSi[volumeId]

via : Trajectory::setNcmTSi(AtcSpace, int)

The Ncm(TSi) computing is done for each AircraftData by AtcVolume, by :

Analysis::setRequestedNcmTSi(TrafficSample, AtcSpace, int).

NB : In the Efficiency Metric application, both actual and requested Ncm(TSi) values arecomputed, in order to have the actualATMOutput and requestedATMOutput (which is thespecified ATM Output)





3.2.1.2 Ncm(TS) by Volume and Trajectory

The set up of each Ncm(TSi) by AtcVolume and their sum for the whole AtcSpace is doneby:

Analysis::setUpNcmTs(TrafficSample&, AtcSpace&);

(That function computes Ncm(TSi) for Actual and requested Trajectories both.)

The computing and storing of each Ncm(Ts) by AtcVolume, in each volume of AtcSpace isdone by :

Analysis::setRequestedNcmTSi(TrafficSample, AtcSpace, int).

3.2.2 ATM Output

ATM Output is set up by the following function :

Analysis::setRequestedATMOutput(AtcSpace);

This function computes the sum of each Ncm(TS) by ATC Volume for the whole AtcSpace.

The result is stored in Analysis::requestedATMOutput()

3.3 ATM Input

As ATM Output is given by :

DelayFuelenance MaCrewesChCapital Labour QQQQQQQ Input ATM ++++++= intarg

_

According to the previous formulae, each member of the sum must be computed before.Q Labour andQCapital are given by the Economics definition, but the other members have to bedefined.

3.3.1 Qcharges(TS)

Qcharges(TS) is defined by the following formulae:

( )i N

i

esCh TSQQTS

esCh∑=

=1

arg arg

Each AircraftData Qcharges is named Qcharges(TSi).

3.3.1.1 Qcharges(TSi)

The following function computes Qcharges(TSi) as the difference between actual andrequested charge cost :

AircraftData::setQCharges()

{

qCharges = actualTraj->chargesCost - requestedTraj->chargesCost;

}

That value is stored in AircraftData::qCharges




INTEGRA


The set up of each Qcharges of the traffic sample is done by:

Analysis::setQChargesI(TrafficSample &)

3.3.1.2 Qcharges(TS)Qcharges(TS) is the sum of all the Qcharges(TSi). It is computed by :

Analysis::setQCharges(TrafficSample)

The result is Qcharges(TS) that is stored in : Analysis::qChargesTS

The whole process is done by :

Analysis::SetUpCharges(TrafficSample)

3.3.2 Qcrew(TS)

Qcrew(TS) is given by the following formulae :

( )i N

i

Crew TSQQTS

Crew∑=

=1

Each AircraftData Qcrew is named qCrew(TSi)

3.3.2.1 Qcrew(TSi)

It is defined as the difference of flight time between the actual and requested Trajectory

qualified by the airline crew cost.

The following function allows to compute this value: AircraftData::setQCrew()

It calls AircraftData::computeQCost(float) that qualify the difference of flight time bythe Argument 1.

float AircraftData::computeQCosts(float coeffE){

return((actualTraj->computeFlightTime()

-requestedTraj->computeFlightTime())*coeffE);

}

The final value is stored in: AircraftData::qCharges

All the Qcharges(TSi) are set by : Analysis::setQChargesI(TrafficSample &)

3.3.2.2 Qcrew(TS)

Qcrew(TS) is the sum of all the Qcrew(TSi). It is computed by :

Analysis::setQCrew(TrafficSample)

The result is Qcrew(TS) that is stored in : Analysis::qCrewTS

The whole process is done by :

Analysis::setUpQCrew(TrafficSample &)





3.3.3 Qmaintenance(TS)

Qmaintenance(TS) is given by the following formulae :

( ) ( )i N

i

i

N

i

TSQTSQQTSTS

∑∑==

+=11

eMaintenanc EcceMaintenanc

It is the sum of the AircraftData maintenance, called Qmaintenance(TSi), and of theAircraftData Qecc(TSi).

AircraftData Qecc(TSi) is the cost produced by a use of engine over the Rpm accelerationpercentage limit, during a time which is bigger than 1 minute. The percentage is comparedto percentage reference costs associated to percentage bands (50%..100%). This excess

engine use is called Excess Usage.

3.3.3.1 Qmaintenance(TSi)

It is defined as the difference of flight time between the actual and requested Trajectoryqualified by the maintenance cost.

The following function allows to compute this value: AircraftData::setQMaintenance()

It calls AircraftData::computeQCost(float) that is described in §3.3.2.

The final value is stored in: AircraftData::qMaintenance

The set up of each AircraftData qMaintenance is done by

Analysis::setQMaintenanceI (TrafficSample &tsE)

Their sum is computed by : Analysis::computeQMaintenanceTS(TrafficSample)

3.3.3.2 Qecc(TSi)

Qecc(TSi) is computed for each Trajectory.

The cost of duration in minutes, at Excess Usage is computed using the following function:

Trajectory::setQEccTraj(int RpmLimit)

It calls a recursive procedure that seek for each ExcessUsage period and returns the overallvalue:

Trajectory::computeIntermediateXXCost(POINTTYPE &,float &,int &, float,

vXXPercentageCostType, string, string)

Then, for each Trajectory, the Qecc(TSi) is given by the following formulae:

QEcc(TSi) traj = Sum of all Engine Usage costs(Trajectory)

It is applied for one Trajectory by : AircraftData::setQEccTrajTSi(Trajectory &)




INTEGRA


The result is stored in Trajectory::qEccTraj

Qecc (TSi) is the difference between QEcc(TSi) actual and QEcc(TSi) requested.

It is computed by : AircraftData::setQEccTSi()

3.3.3.3 Qecc(TS)

The set up of all the Qecc(TSi) of the traffic sample and their sum is done by:

Analysis::setUpQecc(TrafficSample &)

The result is Qecc(TS) that is stored in : Analysis::qEccTS

3.3.3.4 Qmaintenance(TS)

Qmaintenance(TS) is given by the sum of Qecc(TS) and the sum of eachQmaintenance(TSi). It is done by the following function:

Analysis:: setQMaintenance(TrafficSample)

The whole process to compute Qmaintenance(TS) is done by :

Analysis::SetUpQMaintenance(TrafficSample &, AtcSpace)

Qmaintenance(TS) is stored in Analysis::qMaintenanceTS

3.3.4 Qfuel(TS)

Qfuel(TS) is defined by the following formulae :

( )Volume

i

N

i

Fuel Volume Envt

TS

Fuel K TSQQ

×= ∑

=,

1

Each AircraftData Qfuel value is named Qfuel(TSi). It is defined as the difference of fuel burnby Trajectory, inside a given AtcVolume. First fuelburn by Trajectory and AtcVolume must bedefined.

3.3.4.1 Fb(TSi) by volume and Trajectory

The Fb(TSi) is defined by the difference of AircraftData Trajectory fuel between the entry andthe exit of the given AtcVolume. It is computed by :

Trajectory::setFbTSi(AtcSpace);

For each AtcVolume, the result is stored in Trajectory::fbTSi





3.3.4.2 Qfuel(TSi)

Qfuel(TSi) is given by the difference of Fb(TSi) between actual and requested Trajectory,qualified by the AtcVolume kEnvt coefficient, and multiplied by the fuel cost.

For each AircraftData, the following method allows to compute Qfuel(TSi) by AtcVolume, andto sum all these values to give QFuelAllVolume(TSi) value.

AircraftData::setQFuelTSi(AtcSpace, Economics)

The result is stored in Aircraftdata::qFuel and in AircraftData::qFuelAllVolume

The set-up of each QFuelAllVolume(TSi) and Qfuel(TSi) is done by :

Analyse::setQFuelI(TrafficSample &, AtcSpace, Economics)

3.3.4.3 Qfuel(TS)

Qfuel(TS) is the sum of all the QFuelAllVolume(TSi). It is computed by :

Analyse::setQFuel(TrafficSample &tsE)

The result is stored in : Analysis::qFuelTS

The whole process is done using the following function:

Analyse::setUpQFuel(TrafficSample, AtcSpace, Economics)

3.3.5 Qdelay(TS)

Qdelay(TS) is given by the following formulae:

( )Volume

i

N

i

Delay Volume Delay

TS

Delay K TSQQ

×= ∑

=,

1

For each AircraftData, delay and delay cost is counted on each AtcVolume.

3.3.5.1 Delay(TSi) by volume

For each AircraftData, and for a given AtcVolume, the Delay(TSi) is given by the difference ofNcm(TSi) actual and Ncm(TSi) requested, qualified by the AtcVolume coefficient Kdelay:

AircraftData::setDelay(AtcSpace atsE){

for (int i = 0; i < atsE.size(); i++){

delay[i] = (actualTraj->getNcmTSi(i)

- requestedTraj->getNcmTSi(i))

atsE[i].getKDelay();

}

}




INTEGRA


Delay(TSi) is set for each AircraftData with :

Analysis::setDelayI(TrafficSample&, AtcSpace)

It is stored in: AircraftData::delay

3.3.5.2 Qdelay(TSi) by volume

For each volume, Qdelay(TSi) is the cost of delay for a single flight : it equals to the productof the delay by the coefficient Kcomplexity and Kcost.

Qdelay(TSi) by volume is given by : AircraftData::setQDelay(AtcSpace atsE)

Qdelay(TSi) is set for each AircraftData in :

Analysis::setQdelay(TrafficSample &, AtcSpace)

It is stored in : AircraftData::qDelay

3.3.5.3 Qdelay(TS)

Qdelay(TS) is the sum of each Qdelay(TSi) in the traffic sample. It is computed by :

Analysis::setQDelayTS(TrafficSample)

It is stored in Analysis::qDelayTS

3.3.5.4 Delay(TS) by volume

Delay(TS) by volume is the sum of all the delay(TSi) for a given volume. It represents thenumber of seconds of delay recorded in a AtcVolume.

It is computed by :

Analysis::setDelayVolumeTS(TrafficSample, AtcVolume)

It is stored in AtcVolume::delayTS

This result does not take part to the ATM Output computing.

3.3.5.5 Qdelay(TS) by volume

Qdelay(TS) by volume is the sum of all the Qdelay(TSi) for a given volume. It represents thecost of delay recorded in a AtcVolume.

It is computed by :

Analysis::setQDelayVolumeTS(TrafficSample, AtcVolume)

It is stored in AtcVolume::qDelayTS

This result does not take part to the ATM Output computing.

3.3.6 ATM Input

ATM Input is given by the sum of Qcharges, Qcrew(TS), Qdelay(TS), Qmaintenance(TS),Qfuel(TS), QLabour, QCapital, in the following method :





Analysis::setATMInput(Economics)

ATM Input value is stored in Analysis::ATMInput

3.4 ATM System Efficiency

The ATM System Efficiency is given by the following formulae:

Input ATM

Output ATM

_

_=ε

The Efficiency is computed by :

Analyse::setEfficiency(){

Efficiency = requestedATMOutput / ATMInput;

}

It is stored in Analysis::Efficiency




INTEGRA


4. EFFICIENCY METRICS OUPTUTS

4.1 OutputInterface class

This class collects the Efficiency data and write them to four output files.


fDiscreteAircraft - fstream – file descriptor that store output data for

OUTPUTFILE_AIRCRAFT file printing.fDelayI - fstream - file descriptor that store output data for

OUTPUTFILE_DELAYBYFLIGHT file printing.

fFuelI – fstream – that store output data for OUTPUTFILE_FUELBURN file

printing.

fGlobal - fstream - file descriptor that store output data forOUTPUTFILE_GLOBAL_DATA file printing.

4.1.2 Output Description

The four out put files are described below, with the corresponding method of OutputInterface,that allows to create them





4.1.2.1 Discrete Aircraft Data Output

File Name : EFFICIENCY_AIRCRAFT.csv

This file contains the cost that are defined by AircraftData, for the whole AtcSpace.

COLUMN DESCRIPTION

1 CALLSIGN

2 QCHARGES (US $)

3 QFUEL (US $)

4 QCREW (US $)

5 QMAINTENANCE (US $)

6 FLIGHT TIME – REQUESTED TRAJECTORY (SEC)

7 FLIGHT TIME – ACTUAL TRAJECTORY (SEC)

8 QECC – REQUESTED TRAJECTORY (US $)

9 QECC – ACTUAL TRAJECTORY (US $)

The OuputInterface method that is used to create the EFFICIENCY_AIRCRAFT file is :printDiscreteAircraftData(TrafficSample);




INTEGRA


4.1.2.2 Fuel Burn by Aircraft, Trajectory and AtcVolume Output

File Name : EFFICIENCY_FUELBURN.csv

This file contains fuel burn indication by AircraftData, Trajectory, and AtcVolume

COLUMN DESCRIPTION

1 CALLSIGN

2 TAXI - FUEL BURN - REQUESTED TRAJECTORY (KG)

3 TAXI - FUEL BURN - ACTUAL TRAJECTORY (KG)

4 TWR - FUEL BURN - REQUESTED TRAJECTORY (KG)

5 TWR - FUEL BURN - ACTUAL TRAJECTORY (KG)

6 FIR - FUEL BURN - REQUESTED TRAJECTORY (KG)

7 FIR - FUEL BURN - ACTUAL TRAJECTORY (KG)

8 UIR - FUEL BURN - REQUESTED TRAJECTORY (KG)

9 UIR - FUEL BURN - ACTUAL TRAJECTORY (KG)

10 APP - FUEL BURN - REQUESTED TRAJECTORY (KG)

11 APP - FUEL BURN - ACTUAL TRAJECTORY (KG)

The OuputInterface method that is used to create the EFFICIENCY_AIRCRAFT file is

printFuelByFlightAtcTraj(TrafficSample, AtcSpace);





4.1.2.3 Delay and Qdelay by Aircraft and Volume Output

File Name : EFFICIENCY_DELAY.csv

This file contains AircraftData delays and delay costs by flight and AtcVolume.

COLUMN DESCRIPTION

1 CALLSIGN

2 DELAY IN TAXI ATC VOLUME (SEC)

3 QDELAY IN TAXI ATC VOLUME (US $)

4 DELAY IN TWR ATC VOLUME (SEC)

5 QDELAY IN TWR ATC VOLUME (US $)

6 DELAY IN FIR ATC VOLUME (SEC)

7 QDELAY IN FIR ATC VOLUME (US $)

8 DELAY IN UIR ATC VOLUME (SEC)

9 QDELAY IN UIR ATC VOLUME (US $)

10 DELAY IN APP ATC VOLUME (SEC)

11 QDELAY IN APP ATC VOLUME (US $)

The OuputInterface method that is used to create the EFFICIENCY_AIRCRAFT file isprintDelayByFlightAtc(TrafficSample, AtcSpace);




INTEGRA


4.1.2.4 Global Traffic Sample Output

File Name : EFFICIENCY_METRICS.csv

This file contains all the Efficiency Metrics global output data for the whole ATM System.Moreover for each AtcVolume, global output data (for the whole traffic sample) are printed.

COLUMN DESCRIPTION

1 ATM EFFICIENCY (MINUTE/US$)

2 ATM INPUT (MINUTE)

3 ATM OUTPUT (US $)

4 QCHARGES (US $)

5 QCREW (US $)

6 QDELAY (US $)

7 QECC (US $)

8 QFUEL (US $)

9 QMAINTENANCE (US $)

10..25

FOR EACH ATC VOLUME OF ATC SPACE

- TOTAL DELAY (SEC)

- NCM(TS) FOR REQUESTED TRAJECTORY (MINUTE)

- NCM(TS) FOR ACTUAL TRAJECTORY (MINUTE)

The OuputInterface method that is used to create the EFFICIENCY_AIRCRAFT file is

GlobalDataOutput(AtcSpace, Analyse);





5. CONCLUSION

As specified within the document “Detailed Specification of ATM System Efficiency MetricInputs – Processing – Outputs Document, version 3.0”, the ATM System Efficiency Metricapplication allows to compute the Integra Efficiency Metrics as a function of economical data,requested trajectory, actual trajectory, Complexity, Environment and Capacity.

This standalone application provides the Efficiency global output, by aircraft, and for fuel burnand delay analysis by AtcVolume.

The format of the input and output file allows the user easy manipulations, via spread sheetapplications.

Although some data are not provided for the time being by simulation analysis teams, thisapplication allow further testing with the whole set of data.

That will be the case in the next step of the Integra project which concerns the Validation ofthe ATM system Efficiency Metric




INTEGRA

6. ANNEX A

• User guide

The set-up file can be created and defined using a spread sheet application (Microsoft Excelby example).

The set-up file must be located in the same directory than the Efficieny Metric application.

Then run Efficiency Metric Application. This phase can take a few minutes according to thenumber of flights in the traffic sample, and the trajectory sizes.

The output file are located in the same directory the Efficiency application. They can be used

with a spread sheet application.

Documents

Efficiency Metric Sdd