Entry/Occupancy Comparison

	Function		Occupancy / Entry Load Comparison
	Description		This tool permits the user to see, for a given airspace traffic volume, • Entry counts (by default Hourly counts every 20 minutes) • Min/Max/Average occupancy counts for each entry count bar.
	Access		Workspace > KPIs > Occ. Load Comparison
	Input		TV		Identifier of an active Traffic Volume of which the reference location is an Airspace = mostly a sector (elementary or collapsed)
			WEF		Start of the trending period (hh:mm or hhmm)
			UNT		End of the trending period (hh:mm or hhmm)
			Occ. Duration		The Occupancy Duration being the period during which the flight is considered to be in the airspace starting at the time of the count bar and ending duration later. So the counts at the end of the trending period include also flights until (UNT+Duration). Durations for which an OTMV is defined are indicated with *n* (n being a number from 1 to 20). When an OTMV is defined the sustain or peak values can be indicated to alert the observer.
			Entry Interval		The interval at which the counts have to be made.
			Entry Duration		The period over which the counts have to be accumulated.
			Proposals		The Occupancy Counts can be based on the 'normal' traffic which is the traffic as it was filed or it can be based on the 'proposal' traffic which includes the flights that are being considered for a STAM measure. If a flight is in a proposed STAM measure, then the counts will reflect its absence or presence in the sector due to a STAM. This allows what-if analysis of the effect of a STAM.
			Algorithm		[ DEFAULT | NM | INTERNAL_PSEUDO_NM | INTERNAL_PROBABILITIC ]
					This tool includes some experimentation on different traffic counting mechanisms. Therefore, numerous HMIs (and for example this Occupancy Variability) offer the possibility to choose an algorithm : • DEFAULT – allow the prototype to choose the best algorithm (normally NM) • NM – use the “real” NM traffic counts • INTERNAL_PSEUDO_NM – a local count engine used pre-R19   • INTERNAL_PROBABILISTIC – a local count engine that performs probabilistic counts. The probabilistic counts engine takes into account an estimation of the flight ETO imprecision. For flights still on the ground, the imprecision is relatively high. For airborne flights, the imprecision decreases as the flight approaches the TV in question.  These imprecisions are then taken into account when computing the counts.
			Auto Refresh Mode		never, every 30s, min, 2 min, 3 min, 4 min, 5 min
	Output		The tool will perform a B2B query to retrieve the entry counts and a similar query to retrieve the occupancy counts. For each interval period and count duration, the min, max, and average occupancy values are calculated and presented in a graph. One would assume that when entry counts peak and the variability between min and max occupancy is narrow, there is little or no opportunity to perform STAM by delay measure. More analysis is needed to understand the correspondence between entry and occupancy count evolution and variability.
					The user may click right on the traffic count bars, which brings up a CHMI-like contextual menu