Client Portal

Cat 3 – Seasonality

In order to validate the Seasonality Category, it is essential to know the following:

Departure/arrival date for all flights within the fare component, pricing unit and journey. (The inclusion of a Travel Segment Indicator (TSI) and the setting of the Assumption Override Tag in this category can modify the application of the assumption from departure of the originating flight of the pricing unit to the departure of the originating flight of the fare component or journey).

It is important to know whether each portion is Outbound or Inbound, this is especially important when selecting a TSI

Review all fare break points within the pricing unit and measure each of those points from the point of origin of the pricing unit to determine the furthest geographical fare break point (point of turnaround).

Outbound = All fare components within the pricing unit prior to the furthest geographical fare break point.

Inbound = All fare components within the pricing unit after the furthest geographical fare break point are considered Inbound.

All fare components within the pricing unit that are selected in the opposite direction of the passenger’s travel is INBOUND travel”

Assumptions

In the absence of Category 3 (Record 2 for Category 3 did not exist or no Record 3 was applicable), the system assumption for Category 3 – Seasonality is that there are no seasonal date(s) restrictions that apply for the fare.

When the Seasonality Category is applicable, the assumption for applying the Seasonality restrictions is: ‘The date of departure of the originating flight of the pricing unit’ determines the seasonality of the fare component being validated. The application of travel may be further modified by the presence of the Assumption Override Tag in Byte 27, which indicates that ‘The date of the Originating Flight of the Fare Component’ determines the seasonality. The Assumption Override Tag in Byte 27 may be used alone or in combination with Geographic Specification Table #995. When a TSI is used in the Geographic Specification Table #995, the TSI should be within the confines of the Assumption Override Tag. For example, when the Assumption Override Tag is set and is used with a TSI in the Geographic Specification Table #995, the TSI must be FC (fare component) or FC/PU (fare component/pricing unit – but will be processed as a fare component) based TSI. When the Assumption Override Tag is not set and a TSI is used in the Geographic Specification Table #995, then the TSI must be FC/PU, PU or Journey based. (Refer to Section C Appendix G for a list of valid TSIs and their fare component, pricing unit or journey application). A TSI alone may expand the application of the seasonality to the journey, but will not override the assumption to make it fare component based. A TSI is generally present to redefine the segment within the pricing unit. See Section 4.1.3 Travel Application – Assumption Override Tag in this document for examples of utilizing fare component, pricing unit, journey TSIs with or without the Assumption Override Tag.

Enable Notifications