EUROCONTROL EUROPEAN ORGANISATION FOR THE SAFETY OF AIR NAVIGATION 1.1.1.1.1.1.1.1.1EUROPEAN AIR TRAFFIC MANAGEMENT PROGRAMME INTEGRA Software Development Documentation of ATM System Efficiency Metric INTEGRA Edition : 1.0 Edition Date : 16 February 2001 Status : Working Draft Class : EATMP
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
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.1 Class definition Attributes..................................................................................252.6.2 Attributes Computed by Efficiency Algorithms..................................................25
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
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”).
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 10 Working Draft Edition : 1.0
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
INTEGRASoftware Development Documentation of ATMSystem Efficiency Metric
INTEGRA
Edition : 1.0 Working Draft Page 11
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.
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 12 Working Draft Edition : 1.0
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.
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.
INTEGRASoftware Development Documentation of ATMSystem Efficiency Metric
INTEGRA
Edition : 1.0 Working Draft Page 13
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.
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 14 Working Draft Edition : 1.0
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)
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 16 Working Draft Edition : 1.0
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)
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 18 Working Draft Edition : 1.0
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.
INTEGRASoftware Development Documentation of ATMSystem Efficiency Metric
INTEGRA
Edition : 1.0 Working Draft Page 27
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.
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 28 Working Draft Edition : 1.0
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.
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)
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 :
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 32 Working Draft Edition : 1.0
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:
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
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 34 Working Draft Edition : 1.0
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 :
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:
INTEGRASoftware Development Documentation of ATMSystem Efficiency Metric
INTEGRA
Edition : 1.0 Working Draft Page 41
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
INTEGRA INTEGRASoftware Development Documentation of ATM System Efficiency Metric
Page 42 Working Draft Edition : 1.0
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
INTEGRASoftware Development Documentation of ATMSystem 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