Directionality User Guide

Introduction

We're enhancing all TIV modules methodology to compute and report searches and redirects in term of PAX volume based on directionality (Non-Directional & Directional), which will further impact the accurate computation of Average Fare Per Passenger.

We are making changes to how we calculate metrics in TI Vision modules.  The intention of this document is to explain at a high level what changes the Partners will experience and when this will likely happen.

Non-Directional and Directional definition

A market's non-directional air traffic is when we calculate traveller demand into two streams of traffic that flow in opposite directions. For example: if a traveller searches for a return flight from Valencia to Edinburgh, they are counted once from Valencia to Edinburgh and once from Edinburgh to Valencia, therefore a passenger count based on "departure" and "arrival".

Some of the other industry terms used for this methodology are bidirectional, PDEW (per day each way).

A market's directional air traffic is when we calculate traveller demand that flows in one direction. For example: if a traveller searches for a return flight from Valencia to Edinburgh, they are counted once from Valencia to Edinburgh.

Interface change

In the front end interface of TIV, the change will appear in the Routes filter. In addition to the Origin and Destination selection, there is an additional Directionality tab that will allow you to analyse data between Directionality and Non-Directionality. By Default Non-Directionality is selected. 

Methodology explanation (old and new change)

In the user interface, the Routes filter will allow users to choose the directionality.

Searches and redirects volume
Current		New change (if Non-Directional is applied to the routes filter)
We currently count the number of unique searches/redirects.  E.g. if a traveller booked a RETURN flight from EDI>BCN for 5 passengers, then the total is   1 search/redirect.		We’ll count the number of searches/redirects and include the passenger count.  E.g. if there are 5 passengers on a ONE WAY flight, the count is 5. If it’s a RETURN trip, then the count is 10.

Average fare per passenger (AFPP)

Current

New change
(if Non-Directional is applied to the routes filter)

When calculating AFPP for RETURN and ONE WAY flights combined, we currently consider the total booking cost of the RETURN (2 flights) and the ONE WAY (1 flight) ticket.

Examples
Trip Kind	AFPP
Return	$160
One Way	$90
Overall	$125

The AFPP will be computed per direction. The return flight is divided by 2 to compute per direction price. 

Examples
Trip Kind	One Way + Return	Return	One Way
Return	$160/2=$80	$160	-
One Way	$90	-	$90
Overall	$85	$160	$90