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

• Day/Time of each flight within the fare component.
• Departure/Arrival day/time for all flights within the pricing unit or journey because 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 system assumption.

Assumptions

The assumptions for Day/Time application are:

• When there is no Category 2 information (no Category 2, Record 2 that resolves to the fare, including Record 2 match, inbound/outbound directional indicators, Geographic Specifications and date overrides), then the fare is valid for all days of the week and/or times of day within the confines of the other category provisions.
• Once there is data present for Category 2 that resolves to the fare, the assumption is that the data applies to the departure day and time of the origin flight of the fare component.

The ability to override this assumption and state that the data applies to departure from the origin of the pricing unit is provided within the category (Byte 58, Application Tag). The presence of a TSI and/or Geo Locs within Category 2 can further modify where the application of day/time restrictions are to be applied within the fare component. Additionally, there is the ability to further modify the category application with Byte 58 (Application Tag), to indicate where the restrictions of day/time should be applied within the pricing unit; i.e., a TSI alone does not modify the application of Category 2. It is important to note that the TSI or Geo Specification does not modify the Category Application from fare component to pricing unit; it only further identifies where the application of the time/days are to be measured from. Additionally, use of an arrival TSI can override the departure application of the category, causing the data to apply to the arrival at the point specified by the TSI.