| Function | Traffic Volume Entry | |||||||
| Description | This tool permits the user to monitor the actual versus planned differences with respect to flights entering a Traffic Volume, in a given time period (defaulting to [-2h, 1h] ). | |||||||
| Access | Workspace > KPIs > TV Entry | |||||||
| Input | TV | Traffic Volume Identifier to monitor for adherence | ||||||
| Mode | Variability or Delay | |||||||
| Many of the KPI tools offer a mode parameter -
which can take a value of either VARIABILITY or DELAY. The difference between
these 2 values is best explained through an example. Consider, 2 flights – one arriving 5 minutes early and one arriving 5 minutes late. When computing an “arrival KPI” we could either say – • On average, the delay was zero ( (-5 + 5) / 2) • On average, the variability was 5 minutes (i.e. ( |-5| + |5|) / 2) In other words, variability determines the average error in terms of magnitude, ignoring if values are actually –five and +five. Delay on the other hand, does care about the sign of values (-five or +five). |
||||||||
| Past (In min) | With reference to [Go] how may minutes to look in the past | |||||||
| Future (In min) | With reference to [Go] how may minutes to look forward | |||||||
| Auto Refresh | never, every 30s, min, 2 min, 3 min, 4 min, 5 min | |||||||
| Limit Delta Times | The user may specify that “extreme” cases be ignored (for example, in the screen shot below, one flight is arriving 70+ minutes late in the sector. If this is considered totally abnormal, the user may limit the delta times to e.g. [-30, +40 min], causing flights outside of this zone to be filtered out from the graphs, and excluded from the statistics) |
|||||||
| Graph Filter | Select the source of the traffic: • ALL: All flights, regulated or not • REGULATED: flights subject to a CASA or STAM regulation • NON-REGULATED: flights not subject to a CASA or STAM regulation |
|||||||
| Ignore Zero Dely Flts | When chosing for monitoring regulated flights you may want to ignore variability of the zero delay flights | |||||||
| Output | The tool will perform a B2B query, obtaining the flights entering a traffic volume, and comparing the load with the demand, indicate the variation in time of entry and the variation in level so we can see how well the flights adhere to their flight plan. The average deviation is indicated in the gauges for the entry time variation. The graph also is split in two between the flights in the past (entered) and in the future (not yet entered). | |||||||
| The tool displays average (DELAY or
VARIABILITY) data in a set of gauges – • ATO – ETO (Past) For entered non-regulated flights, determine the average entry ‘imprecision’ • ATO – CTO (Past) For entered regulated flights, determine the average entry ‘imprecision’ • ATO – ETO (Future) For later entering non-regulated flights, determine the average entry ‘imprecision’ • ATO – CTO (Future) For later entering regulated flights, determine the average entry ‘imprecision’ The tool also shows, flight by flight, the entry ‘imprecision’, both in terms of FL and time. The colour coding for each flight is – • Blue – non-regulated flights • Magenta - regulated flights with zero delay • Red – regulated flights with delay. Clicking on a ‘dot’ provides summary flight information. The scatter graph may also be zoomed (via the mouse wheel) or panned (via click and drag). |
||||||||
This is the Network Performance Monitoring pzge developed by EUROCONTROL SESAR Network Research and Development to explain the features and possibilities of the NetPerf tool to improve situation awareness for Dynamic Demand Capacity Balancing. This is not an official EUROCONTROL page but provides a reference for all stakeholders in ATFCM Air Traffic Flow and Capacity Management to achieve a better understanding of Network Performance.
TV Entry
Subscribe to:
Posts (Atom)

No comments:
Post a Comment