Data Application for Category 5 - Advance Reservations and Ticketing

DATA APPLICATION CATEGORY 5 – ADVANCE RESERVATIONS AND TICKETING

The information contained in this document is the property of ATPCO. No part of this document may be reproduced, stored in a retrieval system, or transmitted in any form, or by any means; mechanical, photocopying, recording, or otherwise, without the prior written permission of ATPCO. Under the law, copying includes translating into another language or format. Legal action will be taken against any infringement

DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

1.0 OVERVIEW ...... 1 1.1 Data Requirements ...... 1 1.2 Basic Processing Overview ...... 2 2.0 DEFINITIONS AND ASSUMPTIONS ...... 3 2.1 Definitions ...... 3 2.2 Assumptions ...... 8 3.0 DETAILED FIELD PROCESSING ...... 9 4.0 PROCESSING ...... 11 4.1 Application of Data for Advance Reservations and Ticketing Processing ...... 14 4.1.1 Advance Reservation - First - Bytes 14-22 ...... 14 4.1.2 Advance Reservation - Last - Bytes 23-31 ...... 16 4.1.3 Advance Reservations - Travel Segment Indicator (TSI) - Bytes 32-33 ...... 20 4.1.4 Advance Reservations – Not Permitted - Byte 34 ...... 29 4.1.5 Advance Reservation - Ticketed - Byte 35 ...... 35 4.1.6 Advance Reservation - Standby - Byte 36 ...... 39 4.1.7 Confirmed - Sector - Byte 37 ...... 51 4.1.8 Confirmed - Geographic Specification Table No. 995 - Bytes 38-45 ...... 58 4.1.9 Confirmed - Each Sector - Byte 46 ...... 71 4.1.10 Advance Ticketing - Time After Reservations - Bytes - 47-55 ...... 84 4.1.11 Advance Ticketing – Option: Earliest or Required - Byte 56...... 97 4.1.12 Advance Ticketing - Time Before Departure - Bytes 57-60 ...... 99 4.1.13 Advance Ticketing - Travel Segment Indicator (TSI) - Bytes 61-62 ...... 101 4.1.14 Advance Ticketing - Both - Byte 63 ...... 107 4.1.15 Advance Ticketing - Exception Time - Bytes 64-67 ...... 111 4.1.16 Waiver Reservation Date - Bytes 68-74 ...... 115 4.1.17 Waiver Ticketing Date - Bytes 75-81 ...... 121 4.1.18 Override Date Table Number 994 – Bytes 82-89 ...... 124 4.1.19 Text Table No. 996 - Bytes 90-97 and Unavailable Data Tag - Byte 98 ...... 125 4.1.20 Application of Data in Reservation, Ticket after Reservation, Ticket before Departure fields ...... 129 4.2 Reconciliation between Footnote and Rule Levels ...... 136 5.0 TRAVEL SEGMENT INDICATORS (TSIs) ...... 140 6.0 CODING CONVENTIONS ...... 144

DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

1.0 OVERVIEW

The Advance Reservations and Ticketing Category (Category 5) is used to define advance reservations and ticketing requirements applicable to a fare. Reservation restrictions may be specified as a period of time before departure of the originating flight of the pricing unit that indicates either the latest time reservations are required or the earliest time reservations are permitted. Ticketing restrictions are specified as either a period of time before departure of the originating flight of the pricing unit and/or a period of time after reservations are confirmed that indicate the latest time ticketing is required. (Application of reservation and/or ticketing requirements to the originating flight of the pricing unit may be overridden by use of a TSI.) In addition, this category can restrict the type of reservation status code (waitlisting, standby, and/or confirmed) for which the fare can be booked. If this category is not present or there are no provisions applicable to a given fare, then the fare is valid for reservations and/or ticketing at any time before departure; open sectors, standby, and waitlisting are permitted.

1.1 Data Requirements

In order to validate the Advance Reservations and Ticketing Category, it is essential to know the following:

• Departure date and time of all flights within the pricing unit and journey. • Reservation and ticketing date and time of all flights within the pricing unit and journey. • Reservation status code of the itinerary being priced. • All points within the pricing unit and journey.

Page D.03.05.001 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

1.2 Basic Processing Overview

Match to the Category 5 Record 2 - as described in Record 2 Processing (Record 2 Processing includes Directionality, Inbound/Outbound, External ‘If’, etc.)

Is there an applicable Category 5 - Record 3 Based on: - Date Override Table #994 - Exception Time (Bytes 64-67)

NO YES

Apply System Assumption. No Validate the Category 5 information Advance Res/Tkt Restrictions Apply. against the ‘Date and Time of the Departure of the Originating flight of the Pricing unit’ or as specified by the TSI(s).

Page D.03.05.002 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

2.0 DEFINITIONS AND ASSUMPTIONS

2.1 Definitions

Return Travel All sectors of all fare components within the pricing unit that occur after the point of turnaround (after the furthest geographical fare break point).

NOTE: For fares in RTW/CT tariffs, the point of turnaround is defined as the furthest ticketed point on the fare component measured from the origin fare break point. (Refer to the Glossary of Terms).

Standby Non-confirmed status; the handling of standby passengers is a process that generally takes place at the airport.

Status Codes Codes that indicate whether a reservation is confirmed or non-confirmed (e.g. HL = waitlist). Actual status codes are not entered in Category 5; however, waitlist and standby conditions specified within the category may be used to verify status codes applicable to the fare in question.

Waitlist Non-confirmed status; the waitlist process generally takes place when reservations are made.

Counting of Days/Hours/Minutes/ Months

Day Calendar day.

Counting before departure: Counting of days begins the day before departure. The actual date of departure will not be included and the date of booking will be included in counting. Counting after reservations: For example:

Departure Date = 25 December 1 day before departure = 24 December (count back 1 day: Dec 24) 7 days before departure = 18 December (count back 7 days: Dec 24, 23, 22, 21, 20, 19, 18)

Page D.03.05.003 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Counting after reservation: Counting of days begins the day after reservations are made. The actual date of booking will not be included and the date of ticket issue will be included in counting. For example:

Reservation Date = 25 December 1 day after reservation = 26 December (count forward 1 day: Dec 26) 7 days after reservation = 01 January (count forward 7 days: Dec 26, 27, 28, 29, 30, 31, Jan 1)

Hour Counting before departure: Counting of hours begins the hour before departure. The actual hour of departure will not be included and the hour of booking will be included in counting. For example:

Departure Date/Time = 18 December at 10:42 a.m. 1 hour before departure = 18 December at 9:42 a.m. 24 hours before departure = 17 December at 10:42 a.m.

For Daylight Savings (counting remains the same):

Clock is set forward 1 hour the night of April 04: Departure Date/Time = 05 April at 10:42 a.m. 1 hour before departure = 05 April at 9:42 a.m. 24 hours before departure = 04 April at 10:42 a.m.

Clock is set backwards 1 hour the night of 29 October: Departure Date/Time = 30 October at 10:42 a.m. 1 hour before departure = 30 October at 9:42 a.m. 24 hours before departure = 29 October at 10:42 a.m.

Page D.03.05.004 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Counting after reservation: Counting of hours begins the hour after reservations are made. The actual hour of booking will not be included and the hour of ticket issue will be included in counting. For example:

Reservation Date/Time = 18 December at 10:42 a.m. 1 hour after reservation = 18 December at 11:42 a.m. 24 hours after reservation = 19 December at 10:42 a.m.

For Daylight Savings (counting remains the same):

Clock is set forward 1 hour the night of April 04: Reservation Date/Time = 04 April at 10:42 a.m. 1 hour after reservation = 04 April at 11:42 a.m. 24 hours after reservation = 05 April at 10:42 a.m.

Clock is set backwards 1 hour the night of 29 October: Reservation Date/Time = 29 October at 10:42 a.m. 1 hour after reservation = 29 October at 11:42 a.m. 24 hours after reservation = 30 October at 10:42 a.m.

Minute Counting before departure: Counting of minutes begins the minute before departure. The actual minute of departure will not be included and the minute of booking will be included in counting. For example:

Departure Date/Time = 18 December at 10:00 a.m. 1 minute before departure = 18 December at 9:59 a.m. 90 minutes before departure = 18 December at 8:30 a.m.

Counting after reservation: Counting of minutes begins the minute after reservations are made. The actual minute of booking will not be included and the minute of ticket issue will be included in counting. For example:

Reservation Date/Time = 18 December at 10:00 a.m.

Page D.03.05.005 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

1 minute after reservation = 18 December at 10:01 a.m. 90 minutes after reservation = 18 December at 11:30 a.m.

Month Counting before departure: For the purpose of determining advance reservation and ticketing requirements, a month means the period of time from a given date in one month to the corresponding date (same numerically designated date) in an earlier month. For example:

Departure Date = 01 April One month before departure = 01 March Two months before departure = 01 February Three months before departure = 01 January

Exceptions Where the corresponding date does not exist in a shorter, earlier month, then the month(s) shall mean from a given date in one month to the last day of such shorter earlier month. For example: Departure Date = 30 March One month before departure = 28/29 February

When the ‘given date’ is the last day in one month, then the ‘corresponding date’ in an earlier month will be the last day of that month. For example: Departure Date = 31 March One month before departure = 28/29 February

Departure Date = 28/29 February One month before departure = 31 January Departure Date = 30 April Three months before departure = 31 January

Departure Date = 31 July One month before departure = 30 June

Page D.03.05.006 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Counting after reservation: For the purpose of determining ticketing requirements after reservation, a month means the period of time from a given date in one month to the corresponding date (same numerically designated date) in a later month. For example:

Reservation Date = 01 April One month after reservation = 01 May Two months after reservation = 01 June Three months after reservation = 01 July

Exceptions Where the corresponding date does not exist in a shorter, later month, then the month(s) shall mean from a given date in one month to the last day of such shorter later month. For example: Reservation Date = 30 January One month after reservation = 28/29 February

When the ‘given date’ is the last day in one month, then the ‘corresponding date’ in a subsequent month will be the last day in the subsequent month. For example

Reservation Date = 31 January One month after reservation = 28/29 February

Reservation Date = 28/29 February One month after reservation = 31 March

Reservation Date = 30 April Three months after reservation = 31 July

Reservation Date = 31 August One month after reservation = 30 September

Page D.03.05.007 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

2.2 Assumptions

In the absence of Category 5 (Record 2 for Category 5 did not exist or no Record 3 was applicable), the system assumptions for Advance Reservations and Ticketing Category are as follows:

• The fare is valid for reservations and ticketing at any time. • Open segments, including open returns, are permitted. • Standby and waitlisting reservation status codes are permitted.

When the Advance Reservations and Ticketing Category is applicable, the system assumptions for applying the Advance Reservations and Ticketing restrictions are as follows:

• The date and time of the originating flight of the pricing unit identifies the point from which the advance reservation and/or ticketing period is to be measured. The application may be further modified by the presence of a Travel Segment Indicator (TSI) or Confirmed Sector – Each (Byte 46), which identifies the portion of travel from which the advance reservation and/or ticketing is measured (e.g. TSI 31 –transatlantic sectors). • All sectors of all fare components in the pricing unit prior to the point of turnaround (prior to the furthest geographical fare break point) must be confirmed (provided Bytes 37-46 are Blank). RTW/CT fares: For fares in RTW/CT tariffs, the point of turnaround is defined as the furthest ticketed point on the fare component measured from the origin fare break point. (Refer to the Glossary of Terms.) The assumption is that all sectors of the RTW/CT fare component prior to the point of turnaround must be confirmed (provided Bytes 37-46 are Blank). • Standby and waitlisting reservation status codes are permitted for any sector that does not require a confirmed status code (provided Byte 36 is Blank).

Page D.03.05.008 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

3.0 DETAILED FIELD PROCESSING

Byte Location Match / Action Definition / Processing Byte 1 Key Match Indicates the Record number for which the data is formatted. RECORD TYPE Byte 2 Key Match Indicates the type of processing to be taken in connection to the transaction, either ACTION new data or changed data. Bytes 3-5 Key Match Indicates to what rule or footnote category the data applies. For the Advance CAT. NO. Reservations and Ticketing Category, it will always be 05. Bytes 6-13 Key Match Indicates a number that links the Category 5 Record 3 to the associated Category TBL. NO. Control Records (Record 2). Bytes 14-22 Action Indicate the earliest time reservations are permitted, before departure of the ADV RES - FIRST originating flight of the pricing unit or the flight specified in Bytes 32-33. Bytes 23-31 Action Indicate the latest time reservations are required before departure of the originating ADV RES - LAST flight of the pricing unit or the flight specified in Bytes 32-33. Bytes 32-33 Action Specifies a Travel Segment Indicator that further defines from where the advance ADV RES - TSI reservations must be measured. Byte 34 Action Indicates that advance reservations are not permitted. ADV RES - PERM Byte 35 Action Indicates that tickets must be issued at the same time that reservations are made. ADV RES - TKTD Byte 36 Action Indicates the standby/waitlist conditions that are permitted or not permitted. STANDBY Additionally, there are exceptions to when the standby/waitlist conditions are permitted. Byte 37 Action Indicates the fare component/s (sector/s) that must hold a confirmed status code. CONFIRMED-SECTOR Bytes 38-45 Action Identifies what portion of travel within the journey must hold a confirmed status CONFIRMED-GEO TBL #995 code. Byte 46 Action Indicates that the originating flight of each fare component (sector) within the CONFIRMED-EACH pricing unit must satisfy the reservation provisions. Bytes 47-55 Action Indicate a specified unit of time ticketing is required after reservations are made. ADV TICKETING

Page D.03.05.009 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Byte Location Match / Action Definition / Processing Byte 56 Action Identifies that the specified ticketing requirements in Bytes 57-60 are either: (1) ADV TCKT-OPTION the earliest time ticketing is permitted before departure of the originating flight of the pricing unit, or (2) an amount of time before departure of the originating flight of the pricing unit that ticketing is required. Bytes 57-60 Action Indicate a specified time for the ticketing requirements (e.g., Number of days). ADV TCKT-DEPT/UNIT Bytes 61-62 Action Specifies a Travel Segment Indicator that further defines from where the advance ADV TCKT-TSI ticketing must be measured. Byte 63 Action Identifies the earlier or later time of bytes 47-60 ticketing requirements that must ADV TCKT-BOTH be met. (Ticketing after reservations or ticketing before departure.) Bytes 64-67 Match Identify a period of time when reservations are made in order for the ticket issue ADV TCKT-EXC/UNIT requirement to apply. Bytes 68-74 Action Indicates a specific reservation date to override the advance reservation WAIVER - RSVN DATE requirements in bytes 14-34. If reservations are made on/before the date specified, reservation requirements do not apply. If reservations are made after the date specified, the reservation requirements apply. Bytes 75-81 Action Indicates a specific ticket issue date to override the advance ticketing requirements WAIVER - TKTD DATE in bytes 35, 47-63. If tickets are issued on/before the date specified, ticketing requirements do not apply. If tickets are issued after the date specified, the ticketing requirements apply Bytes 82-89 Match Refers to a number that defines reservation, ticketing and/or travel dates to which OVERRIDE DATE TBL #994 the advance reservation and/or ticketing requirements apply. The Override Date Table data must match the reservation, ticketing and/or travel dates of the itinerary being priced in order for the advance reservation and/or ticketing requirements to be applied. Bytes 90-97 Action Refers to a table containing free-form text regarding Category 5. The information TEXT TABLE #996 within this table is not priceable data. Byte 98 Action Identifies that this fare cannot be used for autopricing or that this Record 3 contains UNAVAILABLE DATA TAG only free-form text.

Page D.03.05.010 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.0 PROCESSING

Prior to processing the Advance Reservations and Ticketing Category, a Record 2 must be matched in order to determine the applicable Category 5 provisions and restrictions for the fare component being validated. After a Record 2 has been matched, the next step is to match to a Category 5 Record 3 Table based on the Override Date Table (Bytes 82-89) and Exception Time (Bytes 64-67). Matching and processing Category 5 is dependent upon a “blank” or “coded” value in the Exception Time field. This process is detailed in the explanation and table below.

Exception Time (Bytes 64-67) is BLANK When the fare being validated does match to the Override Date Table and Exception Time (field is blank), and the advance reservation and ticketing restrictions specified within the Category 5 Record 3 apply to the fare being validated, continue processing to an AND table. If no AND tables, then the fare passes processing for Category 5; if an AND table exists, then processing must attempt to match and validate the table. When the fare being validated does match to the Override Date Table and Exception Time (field is blank), and the advance reservation and ticketing restrictions specified within the Category 5 Record 3 do not apply to the fare being validated, continue processing to an OR Table or to the next Set. If no Table or next Set is found, or the provisions do not match based on the match fields, then the fare must fail pricing. When the fare being validated does not match to the Override Date Table and Exception Time (field is blank), then this Category 5 table is considered a no-match, and processing should continue to an OR Table, AND Table or next Set. If another Table or Set is not found, or also did not match based on the Override Date Table or Exception Time (field is blank), then apply the system assumption; i.e., no advance reservation and ticketing restrictions for the fare being validated at this level.

Page D.03.05.011 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Exception Time (Bytes 64-67) is Coded When the fare being validated does match to the Override Date Table and Exception Time (data is entered in the field), and the advance reservation and ticketing restrictions specified within the Category 5 Record 3 apply to the fare being validated, continue processing to an AND table. If no AND tables, then the fare passes processing for Category 5; if an AND table exists, then processing must attempt to match and validate the table. When the fare being validated does match to the Override Date Table and Exception Time (data is entered in the field), and the advance reservation and ticketing restrictions specified within the Category 5 Record 3 do not apply to the fare being validated, the fare must fail pricing. Do not continue processing to an OR Table or to the next Set. Once the coded Exception Time is matched, processing must apply the advanced reservation and ticketing restrictions specified in that table and cannot read on to another subset. When the fare being validated does not match to the Override Date Table or Exception Time (data is entered in the field), then this Category 5 table is considered a no-match, and processing should continue to an OR Table, AND Table, or next Set. If another Table or Set is not found, or also did not match based on the Override Date Table or Exception Time (field is blank), then apply the system assumption; i.e., no advance reservation and ticketing restrictions for the fare being validated at this level.

Matching Override Date Table and Exception Time

Override Date Exception Match/No Match Application – Possible to read on to another subset? Table #994 Time Coded Coded Match both: Apply the data in the table. Cannot read on to another subset. Match 994 and No Match Exception Time: Read on to another table. No Match 994 and Match Exception Time: Read on to another table. Not Coded Coded Match Exception Time: Apply the data in the table. Cannot read on to another subset. (Blank) No Match Exception Time: Read on to another table. NOTE: Blank Table 994 is always a match. Coded Not Coded Match 994: Apply the data in the table. If fail the table, may read on to another subset. (Blank) No Match 994: Read on to the next table. NOTE: Blank Exception Time is always a match. Not Coded Not Coded Apply the data in the table. If fail the table, may read on to another subset. (Blank) (Blank) NOTE: Blank Table 994 and Exception Time are always a match.

Matching the Override Date Table and the Exception Time is further detailed on the chart on the next page.

Page D.03.05.012 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Match Table 994?

No Match Match

Continue processing to the next Is there a Coded OR Table, AND Table, or Set Exception Time?

No Yes

Blank Exception Time is Matched. Apply Category 5 Record 3 data. If fail the Match Exception Time table, then read on to the next subset.

No Match Match

Continue processing to the next Apply Category 5 Record 3 data. OR Table, AND Table, or Set. Processing must pass or fail on this table and cannot read on to another subset.

Page D.03.05.013 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1 Application of Data for Advance Reservations and Ticketing Processing

Measurement of Advance Reservation and Ticketing Dates is based on the CRT location. The date and time recorded by the CRT will be used when validating these restrictions.

4.1.1 Advance Reservation - First - Bytes 14-22

The Advance Reservation – First field (Bytes 14-22) indicates the earliest time reservations are permitted before departure of the originating flight of the pricing unit for the fare component being validated (unless further modified by a TSI in Bytes 32-33). Determination of which sectors need to be confirmed is based on data in the Confirmed Sectors fields (bytes 37-46).

The first reservation time can be expressed as one of the following: • Period of elapsed time (e.g. 3 days). • Day of week (e.g. 1st Monday). • Time of day (e.g. 0900) in conjunction with either a period of elapsed time or day of week.

Processing must take the following steps when validating the Advance Reservation – First data: 1. Determine which sectors of the pricing unit for the fare component being validated must be confirmed based on data in the Confirmed Sectors fields (bytes 37-46). 2. Reservations for the sectors specified in the Confirmed Sectors fields are not permitted until the time specified by the Advance Reservation – First field (Bytes 14-22), measured from the originating flight of the pricing unit for the fare component being validated (unless further modified by a TSI in Bytes 32-33 and or data in EACH Byte 46). 3. If reservations for all of the sectors specified in the Confirmed Sectors field are made after the time/period indicated in the Advance Reservation – First field, processing will pass validation of the Advance Reservation – First data. 4. If reservations for any of the sectors specified in the Confirmed Sectors field are made prior to the time/period indicated in the Advance Reservation – First field, processing will fail the table.

Page D.03.05.014 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example: Record 3: Bytes 14-17 Bytes 18-20 Bytes 21-22 Bytes 37-46 First Res - Time of Day First Res - Period First Res -Unit Conf Sectors 1200 003 Db Blank The data represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are not permitted until noon 3 days before departure of the originating flight of the pricing unit.

Itinerary – NYC-PAR OW fare component: Origin-Destination Departure Date Reservation Date/Time NYC - LON 04 Jan 99 01 Jan 99 at 9:00am LON - PAR 05 Jan 99 01 Jan 99 at 9:00am

Dept 04Jan 99 Dept 05Jan 99 NYC LON PAR

Reservation window: Dept from pricing unit origin: First Time Reservation Permitted: 04 Jan 99 from NYC 01 Jan 99 at Noon

When pricing the NYC-PAR fare component via LON that resolves to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NYC). • Reservations for all sectors specified in the Confirmed Sector fields are not permitted until to noon on the 3rd day before departure of the originating flight of the pricing unit (NYC). Reservations are being made prior to noon 3 days before departure from NYC; therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.015 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.2 Advance Reservation - Last - Bytes 23-31

The Advance Reservation – Last field (Bytes 23-31) indicates the latest time that reservations are required before departure of the originating flight of the pricing unit for the fare component being validated (unless further modified by a TSI in Bytes 32-33). Determination of which sectors need to be confirmed is based on data in the Confirmed Sectors fields (Bytes 37-46). The last reservation time can be expressed as one of the following: • Period of elapsed time (e.g. 3 days). • Day of week (e.g. 1st Monday). • Time of day (e.g. 0900) in conjunction with either a period of elapsed time or day of week.

Processing must take the following steps when validating the Advance Reservation – Last data: 1. Determine which sectors of the pricing unit for the fare component being validated must be confirmed based on data in the Confirmed Sectors fields (Bytes 37-46). 2. Reservations for the sectors specified in the Confirmed Sectors fields are required by the time specified in the Advance Reservation – Last field (Bytes 23-31), measured from the originating flight of the pricing unit for the fare component being validated (unless further modified by a TSI in Bytes 32-33 and or data in EACH Byte 46). 3. If reservations for all of the sectors specified in the Confirmed Sectors field are made prior to the time/period indicated in the Advance Reservation – Last field, processing will pass validation of the Advance Reservation – Last data. 4. If reservations for any of the sectors specified in the Confirmed Sectors field are made after the time/period indicated in the Advance Reservation – Last field, processing will fail the table.

Page D.03.05.016 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 1 Record 3: Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 37-46 Last Res - Time of Day Last Res - Period Last Res – Unit Conf Sectors 1200 003 Db Blank The data represents that for the fare component being validated, reservations all sectors of all fare components in the pricing unit prior to the point of turnaround are required by noon 3 days before departure of the originating flight of the pricing unit.

Itinerary A – round trip NYC-FRA-NYC: Sector Departure Date Reservation Date NYC-LON 02 Jan 99 30 Dec 98 at 11:00 am LON-FRA 03 Jan 99 30 Dec 98 at 11:00 am FRA-LON Open Open LON-NYC Open Open

Dept 02Jan99 Dept 03Jan99 NYC LON FRA Dept Open Dept Open Reservation window: Dept from pricing unit origin: Reservations Required by: 02 Jan 99 30 Dec 98 at Noon

When pricing the NYC-FRA and FRA-NYC fare components that each resolve to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NYC). • Reservations for all sectors specified in the Confirmed Sector fields are required by noon 3 days before departure of the originating flight of the pricing unit (NYC). Reservations are being made prior to noon 3 days before departure from NYC; therefore, pass the table.

Page D.03.05.017 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – round trip NYC-FRA-NYC: Sector Departure Date Reservation Date NYC-LON 02 Jan 99 30 Dec 98 at 11:00 am LON-FRA 03 Jan 99 01 Jan 99 at Noon FRA-LON Open Open LON-NYC Open Open

Dept 02Jan99 Dept 03Jan99 NYC LON FRA Dept Open Dept Open

Reservation window: Dept from pricing unit origin: Reservations Required by: 02 Jan 99 30 Dec 98 at Noon

When pricing the NYC-FRA and FRA-NYC fare components that each resolve to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NYC). • Reservations for all sectors specified in the Confirmed Sector fields are required by noon 3 days before departure of the originating flight of the pricing unit (NYC). Reservations for the LON-FRA sector are being made one day before departure from NYC; therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.018 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 – First and Last Res Record 3: Bytes 18-20 Bytes 21-22 Bytes 27-29 Bytes 30-31 Bytes 37-46 First Res - Period First Res - Unit Last Res - Period Last Res - Unit Conf Sectors 001 Mb 007 Db Blank The data represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are not permitted until 1 month before departure of the originating flight of the pricing unit and are required by at least 7 days before departure of the originating flight of the pricing unit.

Itinerary – WAS-PAR OW fare component: Origin-Destination Departure Date Reservation Date WAS - PAR 28 Feb 99 31 Jan 99

Dept 28Feb99 WAS PAR

Reservation window: Dept from pricing unit origin: First Time Reservation Permitted: Reservations Required by: 28/29 Feb 99 31 Jan 99 21 Feb 99

When pricing the WAS-PAR fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (WAS). • Reservations for all sectors specified in the Confirmed Sector fields are not permitted until 1 month before departure of the originating flight of the pricing unit (WAS) and are required by 7 days before departure of the originating flight of the pricing unit (WAS). Reservations are being made less than 1 month and prior to 7 days before departure from WAS; therefore, pass the table.

Page D.03.05.019 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.3 Advance Reservations - Travel Segment Indicator (TSI) - Bytes 32-33

Advance reservation requirements in bytes 14-31 are measured from the originating flight of the pricing unit for the fare component being validated unless data is present in the Reservation TSI field (Bytes 32-33) or in the Confirmed Each Sector (Byte 46). (See section 4.1.9 of this document for information pertaining to the Confirmed Each Sector field.) The Reservation TSI field is used to specify a TSI that identifies a portion of travel from which the advance reservation requirements in bytes 14-31 will be measured. The TSI is an action field and identifies a portion of travel that must be on the fare component, pricing unit or journey (depending upon the TSI) for the fare component being validated in order to pass the table.

Geographic restrictions may exist in the Reservation TSI field (Bytes 32-33), and/or the Confirmed Geo Spec Table (Bytes 38-45), and/or the Ticketing TSI field (Bytes 61-62). All of these fields are action fields, specifying a portion of travel that must be validated. If any of the values in these fields does not validate against the fare component, pricing unit or journey (depending upon the TSI) for the fare component being priced, then processing will fail the table and read on to the next subset. When all of the values in these fields validate against the fare component, pricing unit or journey (depending upon the TSI) for the fare component being priced, then processing will measure advance reservations based on the data in the Reservation TSI field (Bytes 32-33) and Confirmed Each Sector field (Byte 46), confirmed sectors based on the data in the Confirmed Geo Spec Table (Bytes 38-45), and advance ticketing based on the data in the Ticketing TSI field (Bytes 61-62).

Once the Category 5 Record 3 table has been matched based on the Override Date Table and Exception Time, if the portion of travel identified by the TSI is on the fare component, pricing unit or journey (depending upon the TSI) for the fare component being validated, then all advance reservation requirements in bytes 14-31 will be measured from the portion of travel identified by the TSI. The TSI only identifies the portion of travel from which advance reservation requirements will be measured. It does not alter the measurement of confirmed sectors or advance ticketing requirements. Measurement of confirmed sectors is based on data in the Confirmed Sectors Fields (Bytes 37-46) and measurement of advance ticketing is based on data in the Ticketing TSI field (Bytes 61- 62).

Once the Category 5 Record 3 table has been matched based on the Override Date Table and Exception Time, if the portion of travel identified by the TSI is not on the fare component, pricing unit or journey (depending upon the TSI) for the fare component being validated, processing will fail the table and read on to the next subset (unless data is present in the Exception Time field Bytes 64-67 in which case processing will fail the category and not read on to the next table).

Page D.03.05.020 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When validating the TSI against the itinerary, if the specified portion of travel is applicable to several points on the itinerary, then measure the advance reservation requirement from the first applicable point. If the same TSI is entered in the Ticketing TSI field (Bytes 61-62), then the advance reservation and ticketing requirements should be applied from the same point.

Example 1 (TSI 06) Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res - TSI Conf Sectors Period Unit Time of Day Period Unit Blank Blank Blank 007 Db 06 Blank The data represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 7 days before departure from the origin gateway (TSI 06).

Itinerary A – MSP-LON OW fare component: Sectors Departure Date Reservation Date MSP - NYC 01 Jan 99 28 Dec 98 NYC - LON 04 Jan 99 28 Dec 98

Dept 01Jan 99 Dept 04Jan99 MSP NYC LON

Reservation window: Dept from Origin gateway: First Time Res Permitted: Res Required by: 04 Jan 99 Not restricted 28 Dec 98

When pricing the MSP-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure from the origin gateway (TSI 06) NYC. • Reservations for all sectors specified in the Confirmed Sectors fields are being made 7 days before departure from origin gateway (NYC depart 04Jan); therefore, pass the table.

Page D.03.05.021 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – MSP-LON OW fare component: Origin-Destination Departure Date Reservation Date MSP-LON 01 Jan 99 28 Dec 98

Dept 01Jan 99 MSP LON

Reservation window: Dept from Origin gateway: Res Required by: 01 Jan 99 25 Dec 98

When pricing the MSP-LON fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure from the origin gateway (TSI 06) MSP. • Reservations for all sectors specified in the Confirmed Sectors fields are being made later than 7 days before departure from origin gateway (MSP depart 01Jan); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.022 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (TSI 03 – each trip) Record 2: for YAP fare Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res - TSI Conf Period Unit Time of Day Period Unit Sectors Blank Blank Blank 001 Mb 03 Blank The data represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 1 month before departure of the first flight of the fare component (TSI 03 – each trip). NOTE: Although the advance reservation period will be validated against the first flight of the fare component being validated based on TSI 03 in Bytes 32-33, the sectors that must be confirmed are all sectors of all fare components in the pricing unit prior to the point of turnaround based on Blank in Bytes 37- 46.

Itinerary A – round trip LON-SYD-LON: Origin-Destination Departure Date Reservation Date LON-SYD for YAP 01 Nov 99 15 Oct 99 SYD-LON for YAP 20 Nov 99 15 Oct 99

50% of YAP fare Dept 01Nov99 LON SYD Dept 20Nov99 50% of YAP fare

Reservation window for YAP: Dept from Fare component origin: Res Required by: 01 Nov 99 from LON 01 Oct 99 20 Nov 99 from SYD 20 Oct 99

Page D.03.05.023 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the YAP LON-SYD fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure from the originating flight of the fare component (TSI 03) LON. • Reservations for all sectors specified in the Confirmed Sectors fields are being made later than 1 month before departure from the originating flight of the fare component (LON depart 01Nov); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

When pricing the YAP SYD-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure from the originating flight of the fare component (TSI 03) SYD. • Reservations for all sectors specified in the Confirmed Sectors fields are being made earlier than 1 month before departure from the originating flight of the fare component (SYD depart 20Nov); therefore, pass the table.

Page D.03.05.024 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – Y fare LON-SYD combined round trip with 50% of YAP fare SYD-LON: Origin-Destination Departure Date Reservation Date LON-SYD for Y 01 Nov 99 21 Oct 99 SYD-LON for YAP 20 Nov 99 21 Oct 99

Y fare Dept 01Nov99 LON SYD Dept 20Nov99 50% of YAP fare

Reservation window for YAP: Dept from Fare component origin: Res Required by: 01 Nov 99 from LON 01 Oct 99 20 Nov 99 from SYD 20 Oct 99

When pricing the Y LON-SYD fare component that does not resolve to any Category 5 data: PASS • Apply system assumption – no advance reservation and ticketing restrictions.

When pricing the YAP SYD-LON fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure from the originating flight of the fare component (TSI 03) SYD. • Reservations for all sectors specified in the Confirmed Sectors fields are being made later than 1 month before departure from the originating flight of the fare component (SYD depart 20Nov); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.025 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (TSI not validated on itinerary) Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res - TSI Conf Period Unit Time of Day Period Unit Sectors Blank Blank Blank 001 Mb 40 Blank The data represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 1 month before departure of the outbound transatlantic sector (TSI 40).

Itinerary – round trip SEA-BKK: Origin-Destination Departure Date Reservation Date SEA-BKK 28 Feb 99 01 Jan 99 BKK-SEA 30 Mar 99 02 Jan 99

Dept 28Feb99 SEA TPE BKK Dept 30Mar99

Reservation window: Dept from Outbound transatlantic sector: Res Required by: N/A N/A

When pricing the SEA-BKK and BKK-SEA fare components that each resolve to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure of the outbound transatlantic sector (TSI 40). • Processing cannot validate an outbound transatlantic sector; therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.026 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 4 (TSI Validates Against Multiple Points) Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res – TSI Conf Sectors Period Unit Time of Day Period Unit 001 Mb Blank 014 Db 07 Blank The data represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are not permitted until 1 month before departure of the overwater segment (TSI 07) and are required at least 14 days before departure of the overwater segment (TSI 07).

Itinerary – three component circle trip FAR-ANC-HNL-FAR: Sectors Departure Date Reservation Date FAR-SEA 31 Jul 99 10 Jul 99 SEA-ANC 31 Jul 99 10 Jul 99 ANC-HNL 15 Aug 99 10 Jul 99 HNL-LAX 01 Sep 99 10 Jul 99 LAX-FAR 11 Sep 99 10 Jul 99

Dept 31Jul99 Dept 31Jul99 FAR SEA ANC Dept 15Aug99

LAX Dept 11Sep99

HNL Dept 01Sep99

Reservation window: Dept from Overwater segment: First Time Res Permitted: Res Required by: 31 Jul 99 30 Jun 99 17 Jul 99

Page D.03.05.027 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the FAR-ANC, ANC-HNL, and HNL-FAR fare components that each resolve to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure of the overwater segment (TSI 07). In this example, an overwater segment exists on the following sectors: SEA-ANC of the FAR-ANC fare component, ANC-HNL of the ANC-HNL fare component, and HNL-LAX of the HNL-FAR fare component. When the Reservation TSI validates against multiple points, the reservation requirement will be applied to the first point: SEA-ANC. • Reservations for all sectors specified in the Confirmed Sectors fields are being made less than 1 month and greater than 14 days before departure from SEA; therefore, pass the table.

Page D.03.05.028 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.4 Advance Reservations – Not Permitted - Byte 34

This field indicates that for the fare component being validated, advance reservations are not permitted for any portion of travel within the fare component. Reservations must be at time of departure of the originating flight of the fare component; however, ticketing may be at any time subject to any advance ticketing requirements in Byte 46 and bytes 47-67. Data in Byte 34 overrides the assumption for value Blank in Confirmed Sector Byte 37 (overrides assumption that blank signifies all sectors of all fare components in the pricing unit prior to point of turnaround must be confirmed). When Byte 34 is blank, apply reservation requirements as indicated within the other fields in the Record 3 table. Note: this field is generally used for standby fares to indicate that no confirmed reservations can be held.

Example 1 Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 34 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res – TSI Res - Perm Conf Sectors Period Unit Time of Day Period Unit Blank Blank Blank Blank Blank Blank X Blank For the fare component being validated, the data above represents that reservations for any portion of travel within the fare component may not be made until time of departure.

Itinerary A – NCE-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date NCE - PAR 28 Nov 98 27 Nov 98 01 Oct 98 PAR - LON 28 Nov 98 27 Nov 98 01 Oct 98

Dept 28 Nov 98 NCE PAR LON

Page D.03.05.029 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: Any day Same Day Same Day

When pricing a NCE-LON fare component that resolves to a single Record 3 as coded above: FAIL • Reservations (res 27 Nov) for all sectors of the fare component are being made prior to time of departure (dept 28 Nov). (Tickets may be issued prior to the date of departure, e.g. standby tickets may be issued prior to departure; however, reservations are not permitted until the day of departure.) Processing will fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Itinerary B – NCE-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date NCE - PAR 01 Aug 99 01 Aug 99 01 Jun 99 PAR - LON 01 Sep 99 01 Aug 99 01 Jun 99

Dept 01Aug99 Dept 01Sep99 NCE PAR LON

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: Any day Same Day Same Day

When pricing a NCE-LON fare component that resolves to a single Record 3 as coded above: PASS • Reservations for all sectors of the fare component are not being made until time of departure of the originating flight of the fare component (dept NCE 01Aug). (Tickets may be issued prior to the date of departure, e.g. standby tickets may be issued prior to departure; however, reservations are not permitted until the day of departure.). Processing will pass the table.

Page D.03.05.030 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 Record 2: For YSTANDBY fare Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 34 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res – TSI Res - Perm Conf Sectors Period Unit Time of Day Period Unit Blank Blank Blank Blank Blank Blank X Blank For the YSTANDBY fare component being validated, the data above represents that reservations for any portion of travel within the fare component may not be made until time of departure.

Record 2: For YAP fare Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 34 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res – TSI Res - Perm Conf Sectors Period Unit Time of Day Period Unit Blank Blank Blank 007 Db Blank Blank Blank For the YAP fare component being validated, the data above represents that reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 7 days before departure.

Itinerary A – 50% of the YSTANDBY fare combined round trip with 50% of the YAP fare Origin-Destination Departure Date Reservation Date Ticketing Date NCE-LON 01 Aug 99 01 Aug 99 01 Jun 99 LON-NCE 01 Sep 99 01 Aug 99 01 Jun 99

YSTANDBY fare Dept 01Aug99 NCE LON Dept 01Sep99 YAP fare

Page D.03.05.031 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Reservation window for YSTANDBY: Dept from pricing unit origin: First Time Res Permitted: Res Required by: Any day Same Day Same Day

Reservation window for YAP: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 01 Aug 99 Not restricted 25 Jul 99

When pricing the YSTANDBY NCE-LON fare component that resolves to a single Record 3 as coded above: PASS • Reservations for all sectors of the fare component are not being made until time of departure of the originating flight of the fare component (dept NCE 01Aug). (Tickets may be issued prior to the date of departure, e.g. standby tickets may be issued prior to departure; however, reservations are not permitted until the day of departure.)

When pricing the YAP LON-NCE fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NCE). • Reservations for all sectors specified in the Confirmed Sectors fields are not being made until time of departure (dept NCE 01Aug); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.032 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – 50% of the YAP fare combined round trip with 50% of the YSTANDBY fare Origin-Destination Departure Date Reservation Date Ticketing Date NCE-LON 01 Aug 99 10 Jul 99 10 Jul 99 LON-NCE 01 Sep 99 01 Sep 99 10 Ju1 99

YAP fare Dept 01Aug99 NCE LON Dept 01Sep99 YSTANDBY fare

Reservation window for YAP: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 01 Aug 99 Not restricted 25 Jul 99

Reservation window for YSTANDBY: Dept from pricing unit origin: First Time Res Permitted: Res Required by: Any day Same Day Same Day

When pricing the YAP NCE-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NCE). • Reservations for all sectors specified in the Confirmed Sectors fields are being made prior to 7 days before departure from the origin of the pricing unit (dept NCE 01Aug); therefore, pass the table.

When pricing the YSTANDBY LON-NCE fare component that resolves to a single Record 3 as coded above: PASS • Reservations for all sectors of the fare component are not being made until time of departure of the originating flight of the fare component (dept LON 01Sep). (Tickets may be issued prior to the date of departure, e.g. standby tickets may be issued prior to departure; however, reservations are not permitted until the day of departure.). Processing will pass the table.

Page D.03.05.033 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (Open Sector) Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 34 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res – TSI Res - Perm Conf Sectors Period Unit Time of Day Period Unit Blank Blank Blank Blank Blank Blank X Blank For the fare component being validated, the data above represents that reservations for any portion of travel within the fare component may not be made until time of departure.

Itinerary – FNI-FAR OW STANDBY fare component: Sectors Departure Date Reservation Date Ticketing Date FNI - PAR Open Open 02 Nov 98 PAR - FAR 30Nov98 30Nov98 02 Nov 98

Dept Open Dept 30Nov98 FNI PAR FAR

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: Any day Same Day Same Day

When pricing a FNI-FAR fare component that resolves to a single Record 3 as coded above: PASS • Reservations for the PAR-FNI sector of the fare component are being made 30Nov98 and must be at the same time as the departure of the originating flight of the pricing unit (NCE); however, departure from NCE is open. • Processing must validate against the intended departure date from NCE. If the intended departure date is 30Nov98, then processing will optimistically pass the table and revalidate the data once FNI-PAR is booked.

Page D.03.05.034 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.5 Advance Reservation - Ticketed - Byte 35

This field indicates that reservations and ticket issuance must be completed at the same time (instant purchase). When Byte 35 is present, reservations for the sectors specified in the Confirmed Sectors fields (Bytes 37-46) cannot be held without ticket issuance, and advance reservations and/or ticket issue requirements in bytes 14-33 and 47-67 must be met.

Processing must take the following steps when validating the Advance Reservation – Ticketed (Byte 35) data: 1. Determine which sectors of the pricing unit for the fare component being validated must be confirmed based on data in the Confirmed Sectors fields (Bytes 37-46). 2. Reservations for the sectors specified in the Confirmed Sectors fields are required by the time specified in the Advance Reservation First and Last fields (bytes 14-31), measured from the originating flight of the pricing unit for the fare component being validated (unless further modified by a TSI in Bytes 32-33). 3. Ticketing is required by the time specified in the Advance Ticketing fields (bytes 47-67), measured from the originating flight of the pricing unit for the fare component being validated (unless further modified by a TSI in Bytes 61-62). 4. Reservations for the sectors specified in the Confirmed Sectors fields cannot be held without ticket issuance.

Example 1 Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 34 Byte 35 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res – TSI Res - Perm Tktd Conf Period Unit Time of Day Period Unit Sectors Blank Blank Blank Blank Blank Blank Blank X Blank For the fare component being validated, the data above represents that reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround and ticketing must be made at the same time.

Itinerary A – NCE-PAR OW fare component: Origin-Destination Departure Date Reservation Date Ticketing Date NCE - PAR 28 Nov 98 27 Nov 98 at 9am 27 Nov 98 at 5pm

Dept 28 Nov 98 NCE PAR

When pricing a NCE-PAR fare component that resolves to a single Record 3 as coded above: FAIL

Page D.03.05.035 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

• Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Reservations for all sectors specified in the Confirmed Sectors fields and ticketing must be completed simultaneously. Reservations are not being completed at the same time as ticketing (9am booking requires ticket issue at 9am); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Itinerary B – NCE-PAR OW fare component: Origin-Destination Departure Date Reservation Date Ticketing Date NCE - PAR 28 Nov 98 27 Nov 98 at 9am 27 Nov 98 at 9am

Dept 28 Nov 98 NCE PAR

Page D.03.05.036 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 34 Byte 35 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res – TSI Res - Perm Tktd Conf Period Unit Time of Day Period Unit Sectors Blank Blank Blank 007 Db 48 Blank X Blank For the fare component being validated, the data above represents that reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 7 days before departure of the first international sector. Additionally, reservations and ticketing for all sectors of all fare components in the pricing unit prior to the point of turnaround must be made at the same time.

Itinerary A – MEL-LAX-MEL round trip: Sectors Departure Date Reservation Date Ticketing Date MEL-SYD 05 Oct 99 02 Oct 99 at 4 pm 02 Oct 99 at 4 pm SYD-LAX 10 OCT 99 02 Oct 99 at 4 pm 02 Oct 99 at 4 pm LAX-SYD 29 Oct 99 20 Oct 99 at 9 am 02 Oct 99 at 4 pm (attempting to issue with open sectors) SYD-MEL 29 Oct 99 20 Oct 99 at 9 am 02 Oct 99 at 4 pm (attempting to issue with open sectors)

Dept 05Oct99 Dept 10Oct99 MEL SYD LAX Dept 29Oct99 Dept 29Oct99

Reservation/Ticketing window: Dept from First international sector: First Time Res Permitted: Res Required by: Ticketing required by: 10 Oct 99 Not restricted 03 Oct 99 Same time as res

When pricing the MEL-LAX and LAX-MEL fare components that each resolve to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure of the first international sector (TSI 48) SYD-LAX.

Page D.03.05.037 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

• Reservations for all sectors specified in the Confirmed Sectors fields are being made earlier than 7 days before departure of the first international sector (SYD-LAX depart 10 Oct), and reservations for all sectors specified in the Confirmed Sectors fields are being completed simultaneously; therefore, pass the table.

Itinerary B – MEL-LAX-MEL round trip: Sectors Departure Date Reservation Date Ticketing Date MEL-SYD 05 Oct 99 04 Oct 99 at 1 pm 04 Oct 99 at 1 pm SYD-LAX 10 Oct 99 04 Oct 99 at 1 pm 04 Oct 99 at 1 pm LAX-SYD 29 Oct 99 20 Oct 99 at 9 am 04 Oct 99 at 1 pm (attempting to issue with open sectors) SYD-MEL 29 Oct 99 20 Oct 99 at 9 am 04 Oct 99 at 1 pm (attempting to issue with open sectors)

Dept 05Oct99 Dept 10Oct99 MEL SYD LAX Dept 29Oct99 Dept 29Oct99

Reservation/Ticketing window: Dept from First international sector : First Time Res Permitted: Res Required by: Ticketing required by: 10 Oct 99 Not restricted 03 Oct 99 Same time as res

When pricing the MEL-LAX and LAX-MEL fare components that each resolve to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure of the first international sector (TSI 48) SYD-LAX. • Reservations for all sectors specified in the Confirmed Sectors fields are being completed simultaneously; however, reservations for all sectors specified in the Confirmed Sectors fields are not being made earlier than 7 days before departure of the first international sector (SYD-LAX depart 10 Oct); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.038 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.6 Advance Reservation - Standby - Byte 36

This field specifies waitlist and standby restrictions applicable to the fare component being validated. Data pertaining to waitlisting is intended to be validated against the status code on the reservation. For example, if waitlisting is not permitted, then the reservation must hold a confirmed type status code (e.g. HK or KK). Processing must validate data in Byte 36 as well as data in the Confirmed Sector fields (Bytes 37-46); therefore, waitlist codes only apply to flights in the fare component being validated that may be left open as data in the Confirmed Sectors fields will specify sectors that must be confirmed. Data pertaining to standby is applicable as text only and has no intended validation against the fare as standby generally takes place at the airport.

There are 14 values for Byte 36, including ‘Blank’, as follows:

Value Application A Waitlist and Standby not permitted. B Waitlist not permitted. C Waitlist and Standby not permitted on originating flight. D Standby not permitted on originating flight. E Waitlist not permitted on originating flight. F Waitlist not permitted on originating flight / Standby not permitted. G Standby not permitted on originating flight / Waitlist not permitted. H Standby permitted for earlier/later same day flights; otherwise, Waitlist and Standby not permitted. I Standby permitted for earlier/later same day flights; otherwise, Standby not permitted. J Standby permitted for earlier/later same day flights; otherwise, Waitlist and Standby not permitted on originating flight. K Waitlist permitted for earlier/later same day flights; otherwise, Waitlist and Standby not permitted on originating flight. L Standby permitted for same date as originally ticketed provided any flight/time specific provisions are met. X Standby not permitted. BLANK System assumption applies – Waitlist and Standby permitted.

When this field is ‘Blank’, the system assumption is that the passenger may waitlist or standby for any applicable flight that may be open. Any of the other values, A-L and X, must be checked against the applicable status codes to ensure that the passenger conforms. For any value that addresses waitlisting and does not address standby, the system assumption applies to standby – standby permitted (e.g. value B – waitlist not permitted; system assumption is that standby permitted). For any value that addresses standby and does not address waitlisting, the system assumption applies to waitlisting – waitlisting permitted (e.g. value X – standby not permitted; system assumption is that waitlisting permitted).

Page D.03.05.039 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When a value is entered in Byte 36 that pertains to the originating flight, the intention is that the condition applies to the originating flight of the pricing unit. Processing must validate both the standby/waitlist value in Byte 36 and the Confirmed Sector fields (Bytes 37-46). Provided Byte 46 (Confirmed Sector Each) is blank, all values in the Confirmed Sectors fields require confirmed reservations for at least the originating flight of the pricing unit; therefore, when Byte 46 blank, waitlisting will never be permitted for the originating flight of the pricing unit, regardless of the value in Byte 36. When a value in Byte 36 indicates that waitlisting/standby is not permitted for the originating flight, the assumption is that waitlist/standby is permitted for all other flights that may be open (refer to examples 3 and 4 below). Processing must take the following steps when validating the Standby (Byte 36) and Confirmed Sectors (Bytes 37-46) data: 1. Determine which sectors of the pricing unit for the fare component being validated must be confirmed based on data in the Confirmed Sectors fields (Bytes 37-46). 2. Reservations for the sectors specified in the Confirmed Sectors fields are required by the time specified in the Advance Reservation First and Last fields (bytes 14-33), measured from the originating flight of the pricing unit for the fare component being validated (unless further modified by a TSI in Bytes 32-33). 3. Any sector that may be open can hold a waitlist status type code provided Byte 36 indicates that waitlisting is permitted.

Page D.03.05.040 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 1 (Value A) Record 3: Bytes 27-29 Bytes 30-31 Byte 36 Bytes 37-46 Last Res - Period Last Res - Unit Standby Conf Sectors Blank Blank A Blank The data represents that for the fare component being validated, reservations are required for all sectors of all fare components on the pricing unit prior to the point of turnaround. Waitlisting and standby reservation status codes are not permitted on any flight of the fare component that may be open.

Itinerary A – NYC-LON-NYC round trip Sectors Departure Date Reservation Date Reservation Status Code NYC-LON 01 Oct 99 20 Sep 99 Confirmed (HK) LON-NYC 25 Oct 99 20 Sep 99 Waitlisted (HL)

Confirmed Dept 01Oct99 NYC LON Dept 25Oct99 Waitlist

Page D.03.05.041 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – NYC-LON-NYC round trip Sectors Departure Date Reservation Date Reservation Status Code NYC-LON 01 Oct 99 20 Sep 99 Confirmed (HK) LON-NYC Open Open Open

Confirmed Dept 01Oct99 NYC LON Dept 25Oct99 Open

When pricing the LON-NYC fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. Passenger is holding a confirmed reservation for the NYC-LON fare component. • Waitlisting is not permitted on any flight of the fare component that may be open. LON-NYC may be open based on data in the Confirmed Sectors fields; therefore, pass the table. • Note: standbys are not permitted for this fare; standby data is applicable as text only.

Page D.03.05.042 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary C – NYC-LON-NYC round trip Sectors Departure Date Reservation Date Reservation Status Code NYC-LON 01 Oct 99 20 Sep 99 Waitlisted (HL) LON-NYC 25 Oct 99 20 Sep 99 Confirmed (HK)

Waitlist Dept 01Oct99 NYC LON Dept 25Oct99 Confirmed

Page D.03.05.043 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (Value BLANK) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 36 Bytes 37-46 Last Res - Period Last Res - Unit Res - TSI Standby Conf Sectors 007 Db Blank Blank Blank The data represents that for the fare component being validated, confirmed reservations are required for all sectors of all fare components on the pricing unit prior to the point of turnaround at least 7 days before departure of the originating flight of the pricing unit. Waitlisting and standby reservation status codes are permitted on any flight of the fare component that may be open.

Itinerary A – NYC-LON-NYC round trip Sectors Departure Date Reservation Date Reservation Status Code NYC-LON 01 Oct 99 20 Sep 99 Confirmed (HK) LON-NYC 25 Oct 99 20 Sep 99 Waitlisted (HL)

Confirmed Dept 01Oct99 NYC LON Dept 25Oct99 Waitlist

When pricing the NYC-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period is validated against the originating flight of the pricing unit (NYC). • Reservations for all sectors specified in the Confirmed Sectors fields are being made earlier than 7 days before departure of the first flight of the pricing unit. • Waitlisting is permitted on any flight of the fare component that may be open. All sectors of the fare component are confirmed. • Processing will pass the table. • Note: standbys are permitted for this fare; standby data is applicable as text only.

Page D.03.05.044 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the LON-NYC fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period is validated against the originating flight of the pricing unit (NYC). • Reservations for all sectors specified in the Confirmed Sectors fields are being made earlier than 7 days before departure of the first flight of the pricing unit. • Waitlisting is permitted on any flight of the fare component that may be open. LON-NYC may be open and holds a waitlist status • Processing will pass the table. • Note: standbys are permitted for this fare; standby data is applicable as text only.

Itinerary B – NYC-LON-NYC round trip Sectors Departure Date Reservation Date Reservation Status Code NYC-LON 01 Oct 99 20 Sep 99 Waitlisted (HL) LON-NYC 25 Oct 99 20 Sep 99 Waitlisted (HL)

Waitlist Dept 01Oct99 NYC LON Dept 25Oct99 Waitlist

When pricing the NYC-LON fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period is validated against the originating flight of the pricing unit (NYC). • Reservations for all sectors specified in the Confirmed Sectors fields are not being made earlier than 7 days before departure of the first flight of the pricing unit: NYC-LON sector is waitlisted and Confirmed Sector fields indicate it must hold a confirmed status code. (Waitlisting is only permitted on any flight of the fare component that may be open.) • Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.) • Note: standbys are permitted for this fare; standby data is applicable as text only.

Page D.03.05.045 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the LON-NYC fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period is validated against the originating flight of the pricing unit (NYC). • Reservations for all sectors specified in the Confirmed Sectors fields are not being made earlier than 7 days before departure of the first flight of the pricing unit: NYC-LON sector is waitlisted and Confirmed Sector fields indicate it must hold a confirmed status code. (Waitlisting is only permitted on any flight of the fare component that may be open.) • Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.) • Note: standbys are permitted for this fare; standby data is applicable as text only.

Page D.03.05.046 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (Value C) Record 2: Q fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 36 Bytes 37-45 Byte 46 Last Res - Period Last Res - Unit Res - TSI Standby Conf Sectors Conf – Each 007 Db Blank Blank Blank Blank The data represents that for the fare component being validated, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround at least 7 days before departure of the originating flight of the pricing unit. Waitlisting and standby reservation status codes are permitted on any flight of the fare component that may be open.

Record 2: K fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 36 Bytes 37-45 Byte 46 Last Res - Period Last Res - Unit Res - TSI Standby Conf Sectors Conf – Each Blank Blank Blank C Blank Blank The data represents that for the fare component being validated, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. Waitlisting and standby reservation status codes are not permitted on the originating flight of the pricing unit; waitlist and standby are permitted for all other flights that may be open.

Itinerary – 50% of Q fare combined with 50% of K fare on NYC-LON-NYC round trip: Sectors Departure Date Reservation Date Reservation Status Code Q fare: NYC-LON 01 Oct 99 20 Sep 99 Waitlisted (HL) K fare: LON-NYC 25 Oct 99 20 Sep 99 Confirmed (HK)

Q fare (waitlisted) Dept 01Oct99 NYC LON Dept 25Oct99 K fare (confirmed)

Page D.03.05.047 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the NYC-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period is validated against the originating flight of the pricing unit (NYC). • Reservations for all sectors specified in the Confirmed Sectors fields are being made earlier than 7 days before departure of the first flight of the pricing unit. • Waitlisting is only permitted on any flight of the fare component that may be open, and all sectors of the NYC-LON fare component are confirmed. • Processing will pass the table. • Note: standbys are not permitted on the originating flight of the pricing unit; standby data is applicable as text only.

Page D.03.05.048 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 4 (Value C) Record 2: K fare Record 3: Bytes 27-29 Bytes 30-31 Byte 36 Bytes 37-45 Byte 46 Last Res - Period Last Res - Unit Standby Conf Sectors Conf – Each Blank Blank C Blank X The data represents that for the fare component being validated, confirmed reservations are required for each flight of the fare component. Waitlisting and standby reservation status codes are not permitted on the originating flight of the pricing unit; waitlist and standby are permitted for all other flights that may be open.

Itinerary – OW Y fare combined with 50% of K fare on NYC-LON-NYC round trip: Sectors Departure Date Reservation Date Reservation Status Code Q fare: NYC-LON 01 Oct 99 20 Sep 99 Waitlisted (HL) K fare: LON-NYC 25 Oct 99 20 Sep 99 Confirmed (HK)

Y fare (waitlisted) Dept 01Oct99 NYC LON Dept 25Oct99 K fare (confirmed)

When pricing the NYC-LON Y fare component that does not resolve to any Category 5 data: PASS • Apply system assumption – no advance reservation and ticketing requirements.

When pricing the LON-NYC K fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed reservations are required for all flights of the fare component. LON-NYC flights are confirmed. • Waitlisting is not permitted on the originating flight of the pricing unit; waitlisting is permitted on any flight that may be open. The originating flight of the pricing unit (NYC-LON) does not hold a confirmed status code. • Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.) • Note: standbys are not permitted on the originating flight of the pricing unit; standby data is applicable as text only.

Page D.03.05.049 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 5 (Value D) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 36 Bytes 37-46 Last Res - Period Last Res - Unit Res - TSI Standby Conf Sectors Mon 01 Blank D Blank The data above represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required by the first Monday before departure of the originating flight of the pricing unit. In addition, for the fare component being validated, standby reservation status code is not permitted on the originating flight of the pricing unit. As waitlisting is not addressed, system assumption applies for waitlisting - waitlisting reservation status code is permitted for all flights of the fare component being validated that may be open.

Itinerary - 2 reservations for NCE-PAR OW fare component: Sectors Departure Date Reservation Date Reservation Status Code NCE-PAR Wed 03 Dec 97 Sun 30 Nov 97 Confirmed (HK) NCE-PAR Thur 04 Dec 97 Sun 30 Nov 97 Waitlisted (HL)

Dept 03 Dec 97 (HK) Dept 04 Dec 97 (HL) NCE PAR

When pricing a NCE-PAR fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period is validated against the originating flight of the pricing unit (NCE). • Confirmed reservations (dept 03Dec97 is confirmed) for all sectors specified in the Confirmed Sectors fields are being made earlier than the first Monday before departure of the first flight of the pricing unit . • Waitlisting is permitted on any flight that may be open. As processing validated a confirmed 03Dec 97 reservation, processing is not validating the 04Dec97 waitlisted reservation. Processing will pass the table. • Note: standbys are not permitted on the originating flight of the pricing unit; standby data is applicable as text only.

Page D.03.05.050 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.7 Confirmed - Sector - Byte 37

The Confirmed Sector field (Byte 37) is used to indicate which sectors of the pricing unit must have a confirmed reservation status code for the fare component being validated. When data is coded within the Record 3 for Category 5 (other than a free form text only Record 3) values in this field apply as follows:

BLANK = All sectors of all fare components within the pricing unit prior to the point of turnaround must be confirmed.1 X = All sectors of all fare components within the pricing unit must be confirmed. Y = First sector of the first fare component of the pricing unit must be confirmed. N = All sectors of all fare components within the pricing unit must be confirmed.

NOTE: Values X and N have the same application, differing only in text.

When there is no Category 5 data applicable to the fare component being validated (Record 2 for Category 5 does not exist or no Record 3 table is applicable), then the system assumption is that confirmed reservations are not required for any sector of the pricing unit for the fare component being validated (all sectors of the pricing unit may be open). When the applicable Category 5 Record 3 table for the fare component being validated contains free form text only (Byte 98 Unavailable Data Tag is value Y), then the table is ignored for autopricing, and the system assumption applies as if there were no applicable Record 3 table - confirmed reservations are not required for any sector of the pricing unit for the fare component being validated. If the intent were to apply the assumption of blank that confirmed reservations are required for all sectors of all fare components within the pricing unit prior to the point of turnaround, then this confirmed sector requirement would need to be specified by using the Confirmed Sector Geo Spec Table (Bytes 38-45).

When the applicable Category 5 Record 3 table for the fare component being validated does not contain free form text only and Byte 37 is blank, the application of blank is that confirmed reservations are required for all sectors of all fare components within the pricing unit prior to the point of turnaround.

Data in the Confirmed Sector field Byte 37 specifies the applicable sectors/segments of the pricing unit that must be confirmed unless further qualified by data in the Confirmed Geo Spec Table (Bytes 38-45). For example, value Y indicates that the first sector of the first fare component of the pricing unit must be confirmed. If the Confirmed Geo Spec Table contains geographic locale France and

1 Refer to the Glossary of Terms for a definition of “point of turnaround”

Page D.03.05.051 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

confirmed sector is value Y, then the first sector departing in France must be confirmed, rather than the first sector of the first fare component of the pricing unit.

Example 1 (value BLANK) Record 2: YAP fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 007 Db Blank Blank Blank The data above represents that for the YAP fare component being validated, confirmed reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 7 days before departure from the origin of the pricing unit. (Open returns are permitted.)

Itinerary A – YAP fare NYC-LON-NYC round trip: Sectors Departure Date Reservation Date Reservation Status NYC-LON 01 Oct 99 20 Sep 99 Confirmed (HK) LON-NYC Open Open Open

YAP Dept 01Oct99 NYC LON Dept Open YAP

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 01 Oct 99 Not restricted 24 Sep 99

When pricing the NYC-LON and LON-NYC YAP fare components that each resolve the single Record 3 coded above: PASS • Confirmed Sector (Byte 37) and Confirmed Sector Geo Spec Table (Bytes 38-45) are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround.

Page D.03.05.052 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

• Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NYC). • Reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are being made earlier than 7 days before departure of the originating flight of the pricing unit (NYC depart 01Oct); therefore, pass the table.

Itinerary B – OW Y fare combined RT with 50% of YAP fare to form a NYC-LON-NYC round trip: Sectors Departure Date Reservation Date Reservation Status NYC-CHI 01 Oct 99 20 Sep 99 Waitlist (HL) CHI-LON 04 Oct 99 20 Sep 99 Waitlist (HL) LON-CHI 20 Oct 99 20 Sep 99 Confirmed (HK) CHI-NYC 20 Oct 99 20 Sep 99 Confirmed (HK)

Y fare Dept 01Oct99 (Waitlist) Dept 04Oct99 (Waitlist) NYC CHI LON Dept 20Oct99 Dept 20Oct99 YAP fare Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 01 Oct 99 Not restricted 24 Sep 99

When pricing the NYC-LON Y fare component that does not resolve to any Category 5 data: PASS • Apply system assumption – no advance reservation and ticketing requirements.

When pricing the LON-NYC YAP fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sector (Byte 37) and Confirmed Sector Geo Spec Table (Bytes 38-45) are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NYC). • NYC-CHI and CHI-LON sectors do not hold a confirmed status; therefore reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are not being made earlier than 7 days before departure of the originating flight of the pricing unit (NYC depart 01Oct); therefore, fail the table.

Page D.03.05.053 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

• Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.) Example 2 (value X) Record 2: YAP fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 007 Db Blank X Blank The data above represents that for the YAP fare component being validated, confirmed reservations for all sectors of the pricing unit are required at least 7 days before departure from the origin of the pricing unit (open returns are not permitted).

Itinerary – OW Y fare combined round trip with 50% of YAP fare to form a NYC-FRA-NYC round trip: Sectors Departure Date Reservation Date Reservation Status NYC-LON 01 Oct 99 20 Sep 99 Confirmed (HK) LON-FRA 04 Oct 99 20 Sep 99 Waitlist (HL) FRA-LON 20 Oct 99 20 Sep 99 Confirmed (HK) LON-NYC 20 Oct 99 20 Sep 99 Confirmed (HK)

Y fare Dept 01Oct99 Dept 04Oct99 (Waitlist) NYC LON FRA Dept 20Oct99 Dept 20Oct99 YAP fare

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 01 Oct 99 Not restricted 24 Sep 99

When pricing the NYC-FRA Y fare component that does not resolve to any Category 5 data: PASS • Apply system assumption – no advance reservation and ticketing requirements.

Page D.03.05.054 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the FRA-NYC YAP fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sector (Byte 37) is value X and Confirmed Sector Geo Spec Table (Bytes 38-45) is blank; therefore, confirmed reservations are required for all sectors of all fare components in the priceable. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NYC). • Reservations are required for all sectors of the pricing unit prior to 7 days before departure from the origin of the pricing unit, and the LON-FRA sector does not hold a confirmed reservation status; therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.055 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (value Y) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 007 Db Blank Y Blank The data above represents that for the fare component being validated, confirmed reservations for the first sector of the first fare component of the pricing unit are required at least 7 days before departure from the origin of the pricing unit. Itinerary – NYC-FRA-MIA-NYC three component circle trip: Sectors Departure Date Reservation Date Reservation Status NYC-LON 01 Oct 99 23 Sep 99 Confirmed (HK) LON-FRA 04 Oct 99 23 Sep 99 Waitlist (HL) FRA-MIA Open Open Open MIA-NYC Open Open Open

Dept 01Oct99 Dept 04Oct99 (waitlist) NYC LON FRA Dept Open

MIA Dept Open

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 01 Oct 99 Not restricted 24 Sep 99

Page D.03.05.056 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the NYC-FRA and FRA-NYC fare components that each resolve to a single Record 3 as coded above: PASS • Confirmed Sector (Byte 37) is value Y and Confirmed Sector Geo Spec Table (Bytes 38-45) is blank; therefore, confirmed reservations are required for the first sector of the first fare component in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NYC). • Reservations for the first sector of the first fare component of the pricing unit (NYC-LON) are being made prior to 7 days before departure from the origin of the pricing unit (NYC dept 01Oct); therefore, pass the table.

Example 4 (value N) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 007 Db Blank N Blank The data above represents that for the fare component being validated, confirmed reservations for all sectors of the pricing unit are required at least 7 days before departure from the origin of the pricing unit.

Itinerary – NYC-FRA-NYC round trip: Sectors Departure Date Reservation Date Reservation Status NYC-LON 01 Oct 99 23 Sep 99 Confirmed (HK) LON-FRA 04 Oct 99 23 Sep 99 Confirmed (HK) FRA-LON 20 Oct 99 23 Sep 99 Confirmed (HK) LON-NYC 20 Oct 99 23 Sep 99 Confirmed (HK)

Dept 01Oct99 Dept 04Oct99 NYC LON FRA Dept 20Oct99 Dept 20Oct99

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 01 Oct 99 Not restricted 24 Sep 99

Page D.03.05.057 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the NYC-FRA and FRA-NYC fare components that each resolve to a single Record 3 as coded above: PASS • Confirmed Sector (Byte 37) is value N and Confirmed Sector Geo Spec Table (Bytes 38-45) is blank; therefore, confirmed reservations are required for all sectors of all fare components in the priceable. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (NYC). • Reservations for all sectors of the pricing unit are being made prior to 7 days before departure from the origin of the pricing unit (NYC dept 01Oct); therefore, pass the table.

4.1.8 Confirmed - Geographic Specification Table No. 995 - Bytes 38-45

The confirmed sector requirement in Byte 37 applies to the pricing unit unless data is present in the Confirmed Geo Spec Table (Bytes 38-45). The Confirmed Geo Spec Table is used to specify the portions of travel to which the confirmed sector (confirmed booking status) requirement in Byte 37 applies. The Confirmed Geo Spec Table is an action field and identifies a portion of travel that must be on the fare component, pricing unit or journey (depending upon the TSI) for the fare component being validated in order to pass the table. Data in the Confirmed Geo Spec Table may consist of up to two locations and/or a TSI specifying the portion of travel to which the confirmed sector requirement applies. The application of each of the locations is “within” and the relationship between the locations is “or” (e.g. locations FR/DE signify travel within France or within Germany). Note: ATPCO’s Coding Convention holds that cities should not be entered without a TSI.

Geographic restrictions may exist in the Reservation TSI field (Bytes 32-33), and/or the Confirmed Geo Spec Table (Bytes 38-45), and/or the Ticketing TSI field (Bytes 61-62). All of these fields are action fields, specifying a portion of travel that must be validated. If any of the values in these fields does not validate against the fare component, pricing unit or journey (depending upon the TSI) for the fare component being priced, then processing will fail the table and read on to the next subset. When all of the values in these fields validate against the fare component, pricing unit or journey (depending upon the TSI) for the fare component being priced, then processing will measure advance reservations based on the data in the Reservation TSI field (Bytes 32-33), confirmed sectors based on the data in the Confirmed Geo Spec Table (Bytes 38-45), and advance ticketing based on the data in the Ticketing TSI field (Bytes 61-62).

Once the Category 5 Record 3 table has been matched based on the Override Date Table and Exception Time, if the portion of travel identified by the Confirmed Geo Spec Table is on the fare component, pricing unit or journey (depending upon the TSI) for the fare component being validated, then the confirmed sector requirement in Byte 37 will apply to the portion of travel identified by the Geo Spec Table. The Geo Spec Table only identifies the portion of travel on which the confirmed sectors will be applied. It does not alter

Page D.03.05.058 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

the measurement of advance reservation requirements or advance ticketing requirements. Measurement of advance reservation requirements is based on data in the Reservation TSI field (Bytes 32-33) and measurement of advance ticketing is based on data in the Ticketing TSI field (Bytes 61-62).

Once the Category 5 Record 3 table has been matched based on the Override Date Table and Exception Time, if the portion of travel identified by the Confirmed Geo Spec Table is not on the fare component, pricing unit or journey (depending upon the TSI) being validated, processing will fail the table and read on to the next subset (unless data is present in the Exception Time field Bytes 64-67 in which case processing will fail the category and not read on to the next table).

When validating the data in the Confirmed Geo Spec Table against the itinerary, if the specified portion of travel is applicable to several points on the itinerary, then the confirmed sector value (Byte 37) will indicate to which portion of travel the confirmed sector requirement applies.

The Confirmed Sector field (Byte 37) should be populated when a Confirmed Geo Spec Table is present in order to further define the sectors applicable for the location(s) and/or TSI indicated. When data is present in the Confirmed Geo Spec Table and the Confirmed Sector field (Byte 37) is blank, then the portion of travel identified by the Geo Spec Table must be validated on fare components prior to the point of turnaround, and the confirmed sector requirement will apply to the portion of travel on fare components prior to the point of turnaround as specified by the Geo Spec Table (open returns will still be permitted).

Page D.03.05.059 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 1 (Confirmed Geo Spec Table with Confirmed Sector Value X): Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table Blank Blank Blank X FR The data above represents that for the fare component being validated, reservations for all sectors of the pricing unit within France must be confirmed.

Itinerary MRS-LON OW fare component: Sectors Departure Date Reservation Date Reservation Status MRS-RNS 03 Dec 97 30 Nov 97 Waitlist RNS-PAR 03 Dec 97 30 Nov 97 Confirmed PAR-LON 05 Dec 97 30 Nov 97 Confirmed LON-PAR 02 Jan 98 02 Nov 97 Confirmed PAR-RNS 02 Jan 98 02 Nov 97 Confirmed RNS-MRS 02 Jan 98 02 Nov 97 Confirmed

Dept 03Dec97 (waitlist) Dept 03Dec97 (confirm) Dept 05Dec97 (confirm) MRS RNS PAR LON Dept 02Jan98 (confirm) Dept 02Jan98 (confirm) Dept 02Jan98 (confirm)

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 03Dec97 Not restricted Not restricted

Page D.03.05.060 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing a MRS-LON fare component that resolves to a single Record 3 as coded above: FAIL • Processing must first validate a portion of travel within France. • Multiple portions of travel within France validate: MRS-RNS, RNS-PAR, PAR-RNS, RNS-MRS. The confirmed sector requirement applies to all sectors within France. • All flights within France must be confirmed and the status code of MRS-RNS sector is waitlist; therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.061 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (Confirmed Geo Spec Table with Confirmed Sector Value Y): Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 001 Mb Blank Y FR The data above represents that for the fare component being validated, confirmed reservations for the first sector within France on the pricing unit are required at least one month before departure from the origin of the pricing unit.

Itinerary MRS-LON-MRS round trip: Sectors Departure Date Reservation Date Reservation Status MRS-RNS 03 Dec 97 02 Nov 97 Confirmed RNS-PAR 03 Dec 97 02 Nov 97 Waitlist PAR-LON 05 Dec 97 02 Nov 97 Waitlist LON-PAR 02 Jan 98 02 Nov 97 Waitlist PAR-RNS 02 Jan 98 02 Nov 97 Waitlist RNS-MRS 02 Jan 98 02 Nov 97 Waitlist

Dept 03Dec97 (confirm) Dept 03Dec97 (waitlist) Dept 05Dec97 (waitlist) MRS RNS PAR LON Dept 02Jan98 (waitlist) Dept 02Jan98 (waitlist) Dept 02Jan98 (waitlist)

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 03 Dec 97 Not restricted 03 Nov 97

Page D.03.05.062 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the MRS-LON and LON-MRS fare components that each resolve to a single Record 3 as coded above: PASS • Processing must first validate a portion of travel within France. • Multiple portions of travel within France validate: MRS-RNS, RNS-PAR, PAR-RNS, RNS-MRS. The confirmed sector requirement applies to the first sector within France (MRS-RNS). • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (MRS). • Reservations for the first sector within France are being confirmed earlier than one month before departure from the origin of the pricing unit; therefore, pass the table. NOTE: ATPCO’s coding convention holds that when location data is present in the Geo Spec Table, Sector field (Byte 37) must be filled with value X.

Example 3 (Confirmed Geo Spec Table with Confirmed Sector Value N):

Page D.03.05.063 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 007 Db Blank N Z 210 The data above represents that for the fare component being validated, confirmed reservations for all sectors of the pricing unit within Europe are required at least 7 days before departure from the origin of the pricing unit.

Itinerary BKK-LON round trip: Sectors Departure Date Reservation Date Reservation Status BKK-ATH 03 Dec 97 02 Nov 97 Waitlisted (HL) ATH-PAR 03 Dec 97 02 Nov 97 Confirmed (HK) PAR-LON 05 Dec 97 02 Nov 97 Confirmed (HK) LON-PAR 02 Jan 98 02 Nov 97 Confirmed (HK) PAR-ATH 02 Jan 98 02 Nov 97 Confirmed (HK) ATH-BKK 02 Jan 98 02 Nov 97 Waitlisted (HL)

Dept 03Dec97 (waitlist) Dept 03Dec97 (confirm) Dept 05Dec97 (confirm) BKK ATH PAR LON Dept 02Jan98 (waitlist) Dept 02Jan98 (confirm) Dept 02Jan98 (confirm)

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 03 Dec 97 Not restricted 26 Nov 97

Page D.03.05.064 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the BKK-LON and LON-BKK fare components that each resolve to a single Record 3 as coded above: PASS • Processing must first validate a portion of travel within Europe. • Multiple portions of travel within Europe validate: ATH-PAR, PAR-LON, LON-PAR, PAR-ATH. The confirmed sector requirement applies to all sectors within Europe . • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (BKK). • Reservations for the all sectors within Europe are being confirmed earlier than 7 days before departure from the origin of the pricing unit. NOTE: ATPCO’s coding convention holds that when location data is present in the Geo Spec Table, Sector field (Byte 37) must be filled with value X.

Page D.03.05.065 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 4 (Confirmed Geo Spec Table with Confirmed Sector Value BLANK): Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 014 Db Blank Blank TSI 42 The data above represents that for the fare component being validated, confirmed reservations on each transatlantic sector (TSI 42) for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 14 days before departure from the origin of the pricing unit.

Itinerary CHI-STO round trip: Sectors Departure Date Reservation Date Reservation Status CHI-NYC 01 Aug 99 10 Jul 99 Confirmed NYC-FRA 01 Aug 99 10 Jul 99 Confirmed FRA-STO 02 Aug 99 10 Jul 99 Waitlist STO-FRA Open Open Open FRA-NYC Open Open Open NYC-CHI Open Open Open

Dept 01Aug99 (confirm) Dept 01Aug99 (confirm) Dept 02Aug99 (waitlist) CHI NYC FRA STO Dept Open Dept Open Dept Open

Reservation window: Dept from pricing unit origin: First Time Res Permitted: Res Required by: 01 Aug 99 Not restricted 18 Jul 99

Page D.03.05.066 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the CHI-STO and STO-CHI fare components that each resolve to a single Record 3 as coded above: PASS • Processing must first validate a transatlantic portion of travel on fare components in the pricing unit prior to the point of turnaround. NYC-FRA validates, and the confirmed sector requirement applies to that sector. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (CHI). • Reservations for the NYC-FRA transatlantic sector are being confirmed earlier than 14 days before departure from the origin of the pricing unit. NOTE: ATPCO’s coding convention holds that when location data is present in the Geo Spec Table, Sector field (Byte 37) must be filled with value X.

Page D.03.05.067 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 5 (Confirmed Geo Spec Table with Reservation TSI): Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 014 Db 37 X US The data above represents that for the fare component being validated, confirmed reservations for all sectors of the pricing unit within the United States are required at least 14 days before departure of the transoceanic sector.

Itinerary – DEN-LON-DEN round trip: Sectors Departure Date Reservation Date Reservation Status DEN-NYC 20 May 98 07 May 98 Waitlist NYC-LON 21 May 98 07 May 98 Confirmed LON-NYC 30 Jul 98 07 May 98 Confirmed NYC-DEN 30 Jul 98 07 May 98 Confirmed

Dept 20May98 (waitlist) Dept 21May98 (confirm) DEN NYC LON Dept 30Jul98 (confirm) Dept 30Jul98 (confirm)

Reservation window: Dept from Transoceanic sector: First Time Res Permitted: Res Required by: 21 May 98 Not restricted 07 May 98

Page D.03.05.068 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the DEN-LON and LON-DEN fare components that each resolve to a single Record 3 as coded above: FAIL • Processing must validate a portion of travel on a transoceanic sector (Res TSI) and a portion of travel within the United States (Confirmed Geo Spec Table). • Multiple portions of travel on a transoceanic sector validate: NYC-LON and LON-NYC. The advance reservation requirement will be measured from the departure of the first transoceanic sector, NYC-LON. • Multiple portions of travel within the United States validate: DEN-NYC and NYC-DEN. The confirmed sector requirement applies to all sectors of the pricing unit within the United States. • The DEN-NYC sector does not hold a confirmed status; therefore, confirmed reservations for all sectors within the United States are not being made earlier than 14 days before departure of the transoceanic sector (NYC-LON depart 21May). • Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.069 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 6 (Confirmed Geo Spec Table with Reservation TSI – Geos do not Validate): Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Last Res - Last Res - Res – TSI Conf Conf Period Unit Sector Geo Spec Table 014 Db 40 X US The data above represents that for the fare component being validated, confirmed reservations for all sectors of the pricing unit within the United States are required at least 14 days before departure of the outbound transatlantic sector (TSI 40).

Itinerary – DEN-LON-DEN round trip: Sectors Departure Date Reservation Date Reservation Status DEN-LON 20 May 98 07 May 98 Confirmed LON-DEN 30 Jul 98 07 May 98 Confirmed

Dept 20May98 (confirm) DEN LON Dept 30Jul98 (confirm)

Reservation window: Dept from Outbound transatlantic sector: First Time Res Permitted: Res Required by: 20 May 98 Not restricted 06 May 98

When pricing the DEN-LON and LON-DEN fare components that each resolve to a single Record 3 as coded above: FAIL • Processing must validate a portion of travel on the outbound transatlantic sector (Res TSI) and a portion of travel within the United States (Confirmed Geo Spec Table). • Processing validates a portion of travel on the outbound transatlantic sector: DEN-LON. The advance reservation requirement will be measured from the departure from DEN. • Processing is not able to validate a portion of travel within the United States. • Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.070 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.9 Confirmed - Each Sector - Byte 46

The Each Sector field (Byte 46) indicates that the advance reservation restrictions will be measured from the originating flight of the fare component being validated and confirmed reservations are required for each sector within the fare component being validated. Data in this field overrides the application of measuring advance reservation requirements in bytes 14-31 from the originating flight of the pricing unit (unless data is present in the Reservation TSI field Bytes 32-33) and overrides the Blank application in Confirmed Sectors Byte 37 that confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. For example, if reservations are not permitted until 3 days before departure and Byte 46 is populated, then reservations for each sector on the fare component being validated are not permitted until 3 days before departure of the fare component. When Byte 46 is populated and a Reservation TSI (Bytes 32-33) is also entered, the TSI will be validated against the fare component being priced; therefore, the only applicable TSIs that may be entered are fare component or fare component/pricing unit TSIs.

Edits prevent entering data in both Confirmed Sectors (Byte 37) and Each Sector (Byte 46); however, data may be entered in both the Confirmed Geo Spec Table (Bytes 38-45) and Each Sector (Byte 46). The confirmed sectors will be validated against the portion of travel identified in the Confirmed Geo Spec Table and the reservation restrictions will be validated against the departure from the origin of the fare component. When Byte 46 is populated, the advance reservation restrictions are applied to the fare component being validated; therefore the Geo Spec Table will also be validated against the fare component. The only applicable TSIs that should be entered in the Geo Spec Table in conjunction with data in Byte 46 are fare component or fare component/pricing unit TSIs.

Page D.03.05.071 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 1 (Geo Spec Blank) Record 3: Bytes 18-20 Bytes 21-22 Bytes 32-33 Bytes 38-45 Byte 46 First Res - First Res - Res-TSI Conf Conf Period Unit Geo Spec Table Each 007 Db Blank Blank X The data above represents that for the fare component being validated confirmed reservations for each flight of the fare component are not permitted until 7 days before departure of the originating flight of the fare component.

Itinerary – PAR-LON-PAR round trip: Sectors Departure Date Reservation Date PAR-LON 12 Dec 97 06 Dec 97 LON-PAR 26 Dec 97 06 Dec 97

Dept 12Dec97 PAR LON Dept 26Dec97

Reservation window: Dept from Fare component origin: First Time Res Permitted: 12 Dec 97 from PAR 05 Dec 97 26 Dec 97 from LON 19 Dec 97

Page D.03.05.072 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the PAR-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sector Geo Spec is blank and Byte 46 is coded; therefore, confirmed reservations are required for all sectors of the fare component being validated. • Res TSI field is blank and Byte 46 is coded; therefore, advance reservation period will be validated against the departure of the originating flight of the fare component (PAR). • Reservations for all sectors of the fare component are being made less than 7 days before departure of the fare component (PAR depart 12Dec); therefore, pass the table.

When pricing the LON-PAR fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sector Geo Spec is blank and Byte 46 is coded; therefore, confirmed reservations are required for all sectors of the fare component being validated. • Res TSI field is blank and Byte 46 is coded; therefore, advance reservation period will be validated against the departure of the originating flight of the fare component (LON). • Reservations for all sectors of the fare component are being made earlier than 7 days before departure of the fare component (LON depart 26Dec); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.073 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (Geo Spec Coded - Loc) Record 3: Bytes 18-20 Bytes 21-22 Bytes 32-33 Bytes 38-45 Byte 46 First Res - First Res - Res – TSI Conf Conf Period Unit Geo Spec Table Each 003 Db Blank Z 210 X The data above represents that for the fare component being validated confirmed reservations for each flight of the fare component within Europe are not permitted until 3 days before departure of the originating flight of the fare component. Itinerary – CPT-LON-CPT round trip: Sectors Departure Date Reservation Date CPT-AMS 08 Jun 99 15 May 99 AMS-LON 10 Jun 99 06 Jun 99 LON-AMS 07 Aug 99 05 Aug 99 AMS-CPT 12 Aug 99 05 Aug 99

Dept 08Jun99 Dept 10Jun99 CPT AMS LON Dept 12Aug99 Dept 07Aug99 Reservation window: Dept from Fare component origin: First Time Res Permitted: 08 Jun 99 from CPT 05 Jun 99 07 Aug 99 from LON 04 Aug 99

When pricing the CPT-LON fare component that resolves to a single Record 3 as coded above: PASS • Processing must validate a portion of travel within Europe on the fare component being validated (Confirmed Geo Spec Table), and processing validates the AMS-LON sector. Confirmed reservations are required on the AMS-LON sector. • Res TSI field is blank and Byte 46 is coded; therefore, advance reservation period will be validated against the departure of the originating flight of the fare component (CPT). • Reservations are not permitted for the AMS-LON sector until 3 days before departure from CPT. Reservations for the AMS- LON sector (res 06 Jun) are being made less than 3 days before departure of the fare component (CPT depart 08Jun); therefore, pass the table.

Page D.03.05.074 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the LON-CPT fare component that resolves to a single Record 3 as coded above: PASS • Processing must validate a portion of travel within Europe on the fare component being validated (Confirmed Geo Spec Table), and processing validates the LON-AMS sector. Confirmed reservations are required on the LON-AMS sector. • Res TSI field is blank and Byte 46 is coded; therefore, advance reservation period will be validated against the departure of the originating flight of the fare component (LON). • Reservations are not permitted for the LON-AMS sector until 3 days before departure from LON. Reservations for the LON- AMS sector (res 05Aug) are being made less than 3 days before departure of the fare component (LON depart 07Aug); therefore, pass the table.

Page D.03.05.075 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (Geo Spec Coded – FC/PU TSI) Record 3: Bytes 18-20 Bytes 21-22 Bytes 32-33 Bytes 38-45 Byte 46 First Res - First Res - Res – TSI Conf Conf Period Unit Geo Spec Table Each 003 Db Blank TSI 41 X The data above represents that for the fare component being validated reservations for each flight of the fare component on the outbound transpacific sector are not permitted until 3 days before departure of the originating flight of the fare component.

Itinerary – SIN-MEX round trip (via the Pacific): Sectors Departure Date Reservation Date SIN-MEX 10 Jun 99 09 Jun 99 MEX-SIN 01 Aug 99 30 Jul 99

Dept 10Jun99 SIN MEX Dept 01Aug99 Reservation window: Dept from Fare component origin: First Time Res Permitted: 10 Jun 99 from SIN 07 Jun 99 01 Aug 99 from MEX 29 Jul 99

Page D.03.05.076 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the SIN-MEX fare component that resolves to a single Record 3 as coded above: PASS • Processing must validate an outbound transpacific portion of travel on the fare component being validated (Confirmed Geo Spec Table), and processing validates the SIN-MEX portion. Confirmed reservations are required SIN-MEX. • Res TSI field is blank and Byte 46 is coded; therefore, advance reservation period will be validated against the departure of the originating flight of the fare component (SIN). • Reservations are not permitted for the SIN-MEX portion of travel until 3 days before departure from SIN. Reservations for the SIN-MEX sector (res 09Jun) are being made less than 3 days before departure of the fare component (SIN depart 10Jun); therefore, pass the table.

When pricing the MEX-SIN fare component that resolves to a single Record 3 as coded above: FAIL • Processing must validate an outbound transpacific portion of travel on the fare component being validated (Confirmed Geo Spec Table). Processing cannot validate outbound transpacific travel on the MEX-SIN fare component as MEX-SIN is not an outbound fare component. • Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.077 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 4 (Last Res) Record 2: HAP fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 38-45 Byte 46 Last Res - Last Res - Res – TSI Conf Conf Period Unit Geo Spec Table Each 007 Db Blank Blank Blank The data above represents that for the HAP fare component being validated confirmed reservations all sectors of all fare components in the pricing unit prior to the point of turnaround are required 7 days before departure of the originating flight of the pricing unit.

Record 2: QAP fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 38-45 Byte 46 Last Res - Last Res - Res – TSI Conf Conf Period Unit Geo Spec Table Each 014 Db Blank Blank X The data above represents that for the QAP fare component being validated confirmed reservations for each flight of the fare component are required 14 days before departure of the originating flight of the fare component.

Itinerary – round trip: 50% of HAP fare PAR-LON and 50% of QAP fare LON-PAR

Sectors Departure Date Reservation Date HAP fare PAR-LON for HAP 12 Dec 97 05 Dec 97 Dept 12Dec97 LON-PAR for QAP 26 Dec 97 05 Dec 97 PAR LON Dept 26Dec97 QAP fare

Reservation window for HAP: Dept from Pricing unit origin: Res Required By: 12 Dec 97 05 Dec 97

Page D.03.05.078 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Reservation window for QAP: Dept from Fare component origin: Res Required By: 26 Dec 97 12 Dec 97

When pricing the HAP PAR-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Res TSI field is blank; therefore, advance reservation period will be validated against the departure of the originating flight of the pricing unit (PAR). • Reservations for all sectors specified in the Confirmed Sectors fields are being made earlier than 7 days before departure of from the origin of the pricing unit (PAR depart 12Dec); therefore, pass the table.

When pricing the QAP LON-PAR fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sector Geo Spec is blank and Byte 46 is coded; therefore, confirmed reservations are required for all sectors of the fare component being validated. • Res TSI field is blank and Byte 46 is coded; therefore, advance reservation period will be validated against the departure of the originating flight of the fare component (LON). • Reservations for all sectors of the fare component are being made earlier than 14 days before departure from the origin of the fare component (LON depart 26Dec); therefore, pass the table.

Page D.03.05.079 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 5 (Res TSI) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 38-45 Byte 46 Last Res - Last Res - Res – TSI Conf Conf Period Unit Geo Spec Table Each 007 Db TSI 42 Blank X The data above represents that for the fare component being validated confirmed reservations for each flight of the fare component are required 07 days before departure of each transatlantic sector (TSI 42) of the fare component.

Itinerary – CHI-LON-CHI round trip: Sectors Departure Date Reservation Date CHI-NYC 01 Dec 99 24 Nov 99 NYC-LON 03 Dec 99 24 Nov 99 LON-NYC 10 Dec 99 04 Dec 99 NYC-CHI 10 Dec 99 04 Dec 99

Dept 01Dec99 Dept 03Dec99 CHI NYC LON Dept 10Dec99 Dept 10Dec99

Reservation window: Dept from Each transatlantic sector Res Required by: 03 Dec 99 from NYC 26 Nov 99 10 Dec 99 from LON 03 Dec 99

When pricing the CHI-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sector Geo Spec is blank and Byte 46 is coded; therefore, confirmed reservations are required for all sectors of the fare component being validated. • Advance reservation period will be validated against the departure of each transatlantic sector (TSI 42) of the fare component (dept from NYC). • Reservations for all sectors of the CHI-LON fare component are being made more than 7 days before departure from NYC (dept 03Dec); therefore, pass the table.

Page D.03.05.080 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the LON-CHI fare component that resolves to a single Record 3 as coded above: FAIL • Confirmed Sector Geo Spec is blank and Byte 46 is coded; therefore, confirmed reservations are required for all sectors of the fare component being validated. • Advance reservation period will be validated against the departure of each transatlantic sector (TSI 42) of the fare component (dept from LON). • Reservations for LON-NYC are being made less than 7 days before departure from LON (dept 10Dec); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.081 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 6 (Res TSI and Conf Geo Spec Table coded) Record 3: Bytes 18-20 Bytes 21-22 Bytes 32-33 Bytes 38-45 Byte 46 First Res - First Res - Res-TSI Conf Conf Period Unit Geo Spec Table Each 007 Db TSI 42 TSI 42 X The data above represents that for the fare component being validated confirmed reservations for each transatlantic sector (Conf Geo Spec TSI 42) are not permitted until 7 days before departure of each transatlantic sector (Res TSI 42) of the fare component.

Itinerary – CHI-LON-CHI round trip: Sectors Departure Date Reservation Date CHI-NYC 01 Dec 99 24 Nov 99 NYC-LON 03 Dec 99 24 Nov 99 LON-NYC 10 Dec 99 04 Dec 99 NYC-CHI 10 Dec 99 04 Dec 99

Dept 01Dec99 Dept 03Dec99 CHI NYC LON Dept 10Dec99 Dept 10Dec99

Page D.03.05.082 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Reservation window: Dept from each transatlantic sector First Time Res Permitted: 03 Dec 99 from NYC 26 Nov 99 10 Dec 99 from LON 03 Dec 99

When pricing the CHI-LON fare component that resolves to a single Record 3 as coded above: FAIL • Processing must validate each transatlantic sector (TSI 42) on the fare component being validated (Confirmed Geo Spec Table), and processing validates the NYC-LON portion. Confirmed reservations are required NYC-LON. • Advance reservation period will be validated against the departure of each transatlantic sector (TSI 42) of the fare component (dept from NYC) • Reservations for NYC-LON are being made more than 7 days before departure from NYC (dept 03Dec); therefore, fail the table. • Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

When pricing the LON-CHI fare component that resolves to a single Record 3 as coded above: PASS • Processing must validate each transatlantic sector (TSI 42) on the fare component being validated (Confirmed Geo Spec Table), and processing validates the LON-NYC portion. Confirmed reservations are required LON-NYC. • Advance reservation period will be validated against the departure of each transatlantic sector (TSI 42) of the fare component (dept from LON) • Reservations for LON-NYC are being made less than 7 days before departure from LON (dept 10Dec); therefore, pass the table.

Page D.03.05.083 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.10 Advance Ticketing - Time After Reservations - Bytes - 47-55

These fields are used to indicate the amount of time after reservations are made that ticket issuance is required. If ticket issuance for the pricing unit for the fare component being validated is not made by the time indicated, processing will fail the table. Time can be expressed as one of the following: • Period of elapsed time (e.g. 24 hours). • Day of week (e.g. 1st Monday). • Time of day (e.g. 0900) in conjunction with either a period of elapsed time or day of week.

The Ticket After Reservation restriction is measured against the reservation dates and times on the sectors that must be confirmed. Determination of which sectors need to be confirmed is based on data in the Confirmed Sectors fields (Bytes 37-46). When multiple reservation dates and/or times apply on the sectors that must be confirmed, validation will be against all reservation dates and times. When different reservation dates and/or times apply for the same sector (and the sector is identified by Bytes 37-46 Confirmed Sector fields), processing will validate the Ticket After Reservation restriction against all reservation dates and times. When different reservation dates and/or times apply for different sectors within the pricing unit (and the sectors are identified by Bytes 37-46 Confirmed Sector), processing will validate all reservation dates and times on the pricing unit for each sector as it is booked. If processing fails the Ticket After Reservation restriction, then the original reservation may need to be canceled and rebooked with the current reservation date.

Page D.03.05.084 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 1 (No advance reservation restriction) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Bytes 47-50 Bytes 51-53 Bytes 54-55 Last Res - Last Res - Res – TSI Conf Conf Tkt – Tkt - Tkt - Unit Period Unit Sector Geo Spec Tbl Time of Day Period Blank Blank Blank Blank Blank Blank 024 Hb The data above represents that for the fare component being validated, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround and ticket issuance is required within 24 hours of reservations.

Itinerary – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 12 Dec 97 05 Dec 97 at 9am 06 Dec 97 at 3pm LON-PAR Open Open 06 Dec 97 at 3pm

Dept 12Dec97 PAR LON Dept Open

Reservation window: Dept from pricing unit origin: Res Required by: 12 Dec 97 Not restricted

Ticketing window: For Reservation on: Ticketing required by: 05 Dec 97 at 9am 06 Dec 97 at 9 am

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: FAIL Reservations are made for all sectors of all fare components in the pricing unit prior to the point of turnaround; however, ticket issuance is not being made within 24 hours of reservations. Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.085 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (Advance reservation restriction) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Bytes 47-50 Bytes 51-53 Bytes 54-55 Last Res - Last Res - Res – TSI Conf Conf Tkt – Tkt - Tkt – Unit Period Unit Sector Geo Spec Tbl Time of Day Period 014 Db Blank X Blank Blank 007 Db The data above represents that for the fare component being validated, reservations for all sectors of the pricing unit are required at least 14 days before departure of the originating flight of the pricing unit, and ticket issuance is required within 7 days of reservations.

Itinerary – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 15 Sep 99 28 Aug 99 03 Sep 99 LON-PAR 02 Oct 99 28 Aug 99 03 Sep 99

Dept 15Sep99 PAR LON Dept 02Oct99 Reservation window: Dept from pricing unit origin: Res Required by: 15 Sep 99 01 Sep 99

Ticketing window: For Reservation on: Ticketing required by: 28 Aug 99 04 Sep 99

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: PASS Reservations for all sectors of the pricing unit are being made earlier than 14 days before departure, and ticket issuance is being made less than 7 days after reservations for these sectors.

Page D.03.05.086 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (Advance reservation restriction – Different Reservation Dates Outbound and Inbound) Record 2: YAP fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Bytes 47-50 Bytes 51-53 Bytes 54-55 Last Res - Last Res - Res – TSI Conf Conf Tkt – Tkt - Tkt – Unit Period Unit Sector Geo Spec Tbl Time of Day Period 014 Db Blank X Blank Blank 007 Db The data above represents that for the YAP fare component being validated, reservations for all sectors of the pricing unit are required at least 14 days before departure of the originating flight of the pricing unit, and ticket issuance is required within 7 days of reservations.

Record 2: HAP fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Bytes 47-50 Bytes 51-53 Bytes 54-55 Last Res - Last Res - Res – TSI Conf Conf Tkt – Tkt - Tkt – Unit Period Unit Sector Geo Spec Tbl Time of Day Period Blank Blank Blank Blank Blank Blank 024 Hb The data above represents that for the HAP fare component being validated, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround, and ticket issuance is required within 24 hours of reservations.

28 AUG 99 – PASSENGER BOOKS OUTBOUND AS FOLLOWS:

Itinerary – PAR-LON round trip: 50% of the YAP fare PAR-LON; LON-PAR Open Sectors Departure Date Reservation Date Ticketing Date YAP fare PAR-LON 15 Sep 99 28 Aug 99 Not ticketed LON-PAR Open Open Not ticketed

Dept 15Sep99 PAR LON Dept Open

Page D.03.05.087 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Reservation window for YAP: Dept from pricing unit origin: Res Required by: 15 Sep 99 01 Sep 99

Ticketing window for YAP: For Reservation on: Ticketing required by: PAR-LON 28 Aug 99 04 Sep 99

When pricing the YAP PAR-LON fare component that resolves to a single Record 3 as coded above: PASS Reservations for all sectors of the pricing unit are being made earlier than 14 days before departure. Processing will pass the fare and will revalidate at time of ticket issuance to ensure that tickets are issued less than 7 days after reservations.

31 AUG 99 – PASSENGER BOOKS RETURN AND INTENDS TO TICKET:

Itinerary – PAR-LON round trip: 50% of the YAP fare PAR-LON; 50% of the HAP fare LON-PAR Sectors Departure Date Reservation Date Ticketing Date YAP fare PAR-LON 15 Sep 99 28 Aug 99 31 Aug 99 HAP fare LON-PAR 10 Oct 99 31 Aug 99 31 Aug 99

Res 28Aug99 Dept 15Sep99 PAR LON Dept 10Oct99 Res 31Aug99

Reservation window for YAP: Dept from pricing unit origin: Res Required by: 15 Sep 99 01 Sep 99 Ticketing window for YAP: For Reservation on *: Ticketing required by: PAR-LON 28 Aug 99 04 Sep 99 LON-PAR 31 Aug 99 07 Sep 99

Page D.03.05.088 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

* Sectors specified by the Confirmed Sector fields (Bytes 37-46).

Reservation window for HAP: Dept from pricing unit origin: Res Required by: 15 Sep 99 Not restricted Ticketing window for HAP: For Reservation on *: Ticketing required by: PAR-LON 28 Aug 99 29 Aug 99 at same time of day * Sectors specified by the Confirmed Sector fields (Bytes 37-46).

When pricing the YAP PAR-LON fare component that resolves to a single Record 3 as coded above: PASS • Reservations for all sectors of the pricing unit are being made earlier than 14 days before departure (dept PAR 15Sep). • The Ticketing After Reservation restriction will be measured against all reservation dates on the sectors identified by the confirmed sector fields: PAR-LON reservation 28Aug; LON-PAR reservation 31Aug. • Tickets are being issued less than 7 days after reservations on all sectors of the pricing unit (ticket issue 31Aug). Processing will pass the table.

When pricing the HAP LON-PAR fare component that resolves to a single Record 3 as coded above: FAIL • Reservations are being made for all sectors of all fare components in the pricing unit prior to the point of turnaround. • The Ticketing After Reservation restriction will be measured against all reservation dates on the sectors identified by the confirmed sector fields: PAR-LON reservation 28Aug. • Tickets are being issued more than 24 hours after the reservation date on the PAR-LON sector (ticket 31Aug). Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.) NOTE: The original reservation may need to be canceled and rebooked with the current reservation date in order to possibly pass the fare.

Page D.03.05.089 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 4 (Advance reservation restriction – Different Reservation Dates) Record 2: HAP fare Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Bytes 47-50 Bytes 51-53 Bytes 54-55 Last Res - Last Res - Res – TSI Conf Conf Tkt – Tkt - Tkt – Unit Period Unit Sector Geo Spec Tbl Time of Day Period 014 Db Blank Blank Blank Blank 024 Hb The data above represents that for the HAP fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 14 days before departure of the originating flight of the pricing unit, and ticket issuance is required within 24 hours of reservations.

18Jan00 – PASSENGER BOOKS AS FOLLOWS:

Itinerary – CHI-LON round trip: 50% of the HAP fare CHI-LON; LON-CHI Open Sectors Departure Date Reservation Date Ticketing Date CHI-NYC 10Feb00 at 7:00 pm 18Jan00 at 9:00 am Not ticketed NYC-LON 10Feb00 at 10:00 pm 18Jan00 at 9:00 am Not ticketed LON-NYC Open Open Not ticketed NYC-CHI Open Open Not ticketed

Res 18Jan00 Res 18Jan00 Dept 10Feb00 7pm Dept 10Feb00 10pm CHI NYC LON Dept Open Reservation window Dept from pricing unit origin: Res Required by: 10Feb00 27Jan00

Ticketing window For Reservation on *: Ticketing required by: CHI-NYC 18Jan00 at 9:00 am 19Jan00 at 9:00 am NYC-LON 18Jan00 at 9:00 am 19Jan00 at 9:00 am * Sectors specified by the Confirmed Sector fields (Bytes 37-46).

Page D.03.05.090 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the HAP CHI-LON fare component that resolves to a single Record 3 as coded above: PASS Reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are being made earlier than 14 days before departure. Processing will pass the fare and will revalidate at time of ticket issuance to ensure that tickets are issued less than 24 hours after reservations.

20Jan00 – PASSENGER BOOKS ENTIRE PRICING UNIT + CHANGES CHI-NYC SECTOR INTENDS TO TICKET:

Itinerary – CHI-LON round trip: 50% of the HAP fare CHI-LON; 50% of the HAP fare LON-CHI Sectors Departure Date Reservation Date Ticketing Date CHI-NYC 10Feb00 at 7:00 pm 18Jan00 at 9:00 am Not ticketed CHI-NYC 10Feb00 at 6:00 pm 20Jan00 at 2:00 pm 20Jan00 NYC-LON 10Feb00 at 10:00 pm 18Jan00 at 9:00 am 20Jan00 LON-NYC 20Feb00 at 8:00 am 20Jan00 at 2:00 pm 20Jan00 NYC-CHI 20Feb00 at 4:00 pm 20Jan00 at 2:00 pm 20Jan00

Res 20Jan00 2pm Dept 10Feb00 6pm Res 18Jan00 Res 18Jan00 9am Dept 10Feb00 7pm Dept 10Feb00 10pm CHI NYC LON Dept 20Feb00 4pm Dept 20Feb00 8am Res 20Jan00 2pm Res 20Jan00 2pm

Reservation window Dept from pricing unit origin: Res Required by: 10Feb00 27Jan00

Page D.03.05.091 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Ticketing window For Reservation on *: Ticketing required by: CHI-NYC 18Jan00 at 9:00 am 19Jan00 at 9:00 am CHI-NYC 20Jan00 at 2:00 pm 21Jan00 at 2:00 pm NYC-LON 18Jan00 at 9:00 am 19Jan00 at 9:00 am * Sectors specified by the Confirmed Sector fields (Bytes 37-46).

When pricing the HAP CHI-LON fare component that resolves to a single Record 3 as coded above: FAIL • Reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are being made earlier than 14 days before departure (dept CHI 10Feb). • The Ticketing After Reservation restriction will be measured against all reservation dates on the sectors identified by the confirmed sector fields: CHI-NYC reservation dates 18Jan and 20Jan; NYC-CHI reservation date 18Jan. • Tickets are being issued more than 24 hours after the earlier reservation date on the CHI-NYC sector (res 18Jan and ticket 20Jan). Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.) NOTE: The original reservation may need to be canceled and rebooked with the current reservation date in order to possibly pass the fare.

Page D.03.05.092 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 5 (No advance reservation restriction – Same Day Ticketing – Value Db) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Bytes 47-50 Bytes 51-53 Bytes 54-55 Last Res - Last Res - Res – TSI Conf Conf Tkt – Tkt - Tkt - Unit Period Unit Sector Geo Spec Tbl Time of Day Period Blank Blank Blank Blank Blank Blank 000 Db The data above represents that for the fare component being validated, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround and ticket issuance is required within the same day of reservations.

Itinerary A – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 12 Dec 03 05 Dec 03 at 9am 05 Dec 03 at 5pm LON-PAR Open Open 05 Dec 03 at 5pm

Dept 12Dec03 PAR LON Dept Open

Reservation window: Dept from pricing unit origin: Res Required by: 12 Dec 03 Not restricted

Ticketing window: For Reservation on: Ticketing required by: 05 Dec 03 at 9am 05 Dec 03 by 11.59pm

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: PASS Reservations are made for all sectors of all fare components in the pricing unit prior to the point of turnaround; ticket issuance is being completed at 5.00pm which is prior to 11.59pm on the same day as reservations.

Page D.03.05.093 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 12 Dec 03 05 Dec 03 at 9am 06 Dec 03 at 9.00am LON-PAR Open Open 06 Dec 03 at 9.00am

Dept 12Dec03 PAR LON Dept Open

Reservation window: Dept from pricing unit origin: Res Required by: 12 Dec 03 Not restricted

Ticketing window: For Reservation on: Ticketing required by: 05 Dec 03 at 9am 05 Dec 03 by 11.59pm

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: FAIL Reservations are made for all sectors of all fare components in the pricing unit prior to the point of turnaround; however, ticket issuance is not being made by 11.59pm on the same day as reservations. Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.094 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 6 (Advance reservation restriction – Same Hour Ticketing – Value Hb) Record 3: Bytes 27-29 Bytes 30-31 Bytes 32-33 Byte 37 Bytes 38-45 Bytes 47-50 Bytes 51-53 Bytes 54-55 Last Res - Last Res - Res – TSI Conf Conf Tkt – Tkt - Tkt – Unit Period Unit Sector Geo Spec Tbl Time of Day Period 014 Db Blank X Blank Blank 000 Hb The data above represents that for the fare component being validated, reservations for all sectors of the pricing unit are required at least 14 days before departure of the originating flight of the pricing unit, and ticket issuance is required within the same hour of reservations.

Itinerary A – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 15 Sep 04 28 Aug 04 at 3.05pm 28 Aug at 3:57pm LON-PAR 02 Oct 04 28 Aug 04 at 3.05pm 28 Aug at 3:57pm

Dept 15Sep04 PAR LON Dept 02Oct04 Reservation window: Dept from pricing unit origin: Res Required by: 15 Sep 04 01 Sep 04

Ticketing window: For Reservation on: Ticketing required by: 28 Aug 04 at 3.05pm 28 Aug 04 at 3:59pm

Page D.03.05.095 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 15 Sep 04 28 Aug 04 at 3.05pm 28 Aug at 4.05pm LON-PAR 02 Oct 04 28 Aug 04 at 3.05pm 28 Aug at 4.05pm

Dept 15Sep04 PAR LON Dept 02Oct04 Reservation window: Dept from pricing unit origin: Res Required by: 15 Sep 04 01 Sep 04

Ticketing window: For Reservation on: Ticketing required by: 28 Aug 04 at 3.05pm 28 Aug 04 at 3:59pm

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: FAIL Reservations for all sectors of the pricing unit are being made earlier than 14 days before departure, and ticket issuance is not within the same hour for these sectors. Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.096 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.11 Advance Ticketing – Option: Earliest or Required - Byte 56

For the fare component being validated, this field is used to indicate that the advance ticketing requirement in Bytes 57-60 applies as one of the following:

P = First time before departure of the originating flight of the pricing unit for the fare component being validated (unless, further modified by a TSI in Bytes 61-62) that ticket issuance is permitted

R = Latest time before departure of the originating flight of the pricing unit for the fare component being validated (unless, further modified by a TSI in Bytes 61-62) that ticket issuance is required.

Example 1 (Value P) Record 3: Byte 56 Bytes 57-59 Byte 60 Bytes 61-62 Tkt – Tkt – Tkt – Tkt – Option Dept Dept Unit TSI P 007 D Blank The data above represents that for the fare component being validated, ticket issuance is not permitted until 7 days before departure of the originating flight of the pricing unit.

Itinerary – BUE-MIA round trip: Sectors Departure Date Reservation Date Ticketing Date BUE-MIA 10 Aug 99 01 Aug 99 01 Aug 99 MIA-BUE 20 Aug 99 01 Aug 99 01 Aug 99

Dept 10 Aug 99 BUE MIA Dept 20 Aug 99

Reservation/Ticketing window: Dept from pricing unit origin: Res Required by: Ticketing not permitted until: 10 Aug 99 Not restricted 03 Aug 99

Page D.03.05.097 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the BUE-MIA and MIA-BUE fare components that each resolve to a single Record 3 as coded above: FAIL – Ticket is being issued more than 7 days before departure of the originating flight of the pricing unit (BUE depart 10Aug). Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Example 2 (Value R) Record 3: Byte 56 Bytes 57-59 Byte 60 Bytes 61-62 Tkt – Tkt – Tkt – Tkt – Option Dept Dept Unit TSI R 007 D Blank The data above represents that for the fare component being validated, ticket issuance is required 7 days before departure of the originating flight of the pricing unit.

Itinerary – BUE-MIA round trip: Sectors Departure Date Reservation Date Ticketing Date BUE-MIA 10 Aug 99 01 Aug 99 01 Aug 99 MIA-BUE 20 Aug 99 01 Aug 99 01 Aug 99

Dept 10 Aug 99 BUE MIA Dept 20 Aug 99

Reservation/Ticketing window: Dept from pricing unit origin: Res Required by: Ticketing required by: 10 Aug 99 Not restricted 03 Aug 99

When pricing the BUE-MIA and MIA-BUE fare components that each resolve to a single Record 3 as coded above: PASS – Ticket is being issued more than 7 days before departure of the originating flight of the pricing unit (BUE depart 10Aug).

Page D.03.05.098 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.12 Advance Ticketing - Time Before Departure - Bytes 57-60

This field specifies the earliest or latest time (based on the value in Option Byte 56) that tickets must be issued before departure of the originating flight of the pricing unit for the fare component being validated (unless further modified by a TSI in Bytes 61-62). The time can only be expressed as a period of elapsed time (e.g. 3 days).

Example Record 3: Bytes Bytes Bytes Byte Bytes Bytes Byte Bytes Byte Bytes 27-29 30-31 32-33 37 51-53 54-55 56 57-59 60 61-62 Last Res - Last Res - Res – Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Period Unit TSI Sector Period Unit Opt Dept Dept Unit TSI 021 Db Blank X Blank Blank R 007 D Blank The data above represents that for the fare component being validated, reservations for all sectors of the pricing unit are required at least 21 days before departure of the originating flight of the pricing unit, and ticket issuance is required at least 7 days before departure of the originating flight of the pricing unit.

Itinerary A – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 10 Aug 99 10 Jul 99 01 Aug 99 LON-PAR 20 Aug 99 10 Jul 99 01 Aug 99

Dept 10 Aug 99 PAR LON Dept 20 Aug 99

Reservation/Ticketing window: Dept from pricing unit origin: Res Required by: Ticketing required by: 10 Aug 99 20 Jul 99 03 Aug 99

Page D.03.05.099 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: PASS – Reservations for all sectors of the pricing unit are being made more than 21 days before departure of the originating flight of the pricing unit (PAR depart 10Aug). Ticket is being issued more than 7 days before departure of the originating flight of the pricing unit (PAR depart 10Aug).

Itinerary B – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 10 Aug 99 19 Jul 99 08 Aug 99 LON-PAR 20 Aug 99 19 Jul 99 08 Aug 99

Dept 10 Aug 99 PAR LON Dept 20 Aug 99

Reservation/Ticketing window: Dept from pricing unit origin: Res Required by: Ticketing required by: 10 Aug 99 20 Jul 99 03 Aug 99

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: FAIL – Reservations for all sectors of the pricing unit are being made more than 21 days before departure of the originating flight of the pricing unit (PAR depart 10Aug); however ticket is being issued less than 7 days before departure of the originating flight of the pricing unit (PAR depart 10Aug). Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.100 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.13 Advance Ticketing - Travel Segment Indicator (TSI) - Bytes 61-62

Advance ticketing requirements in bytes 56-60 are measured from the originating flight of the pricing unit for the fare component being validated unless data is present in the Ticketing TSI field (Bytes 61-62). The Ticketing TSI field is used to specify a TSI that identifies a portion of travel from which the advance reservation requirements in bytes 56-60 will be measured. The TSI is an action field and identifies a portion of travel that must be on the fare component, pricing unit or journey (depending upon the TSI) for the fare component being validated in order to pass the table.

Geographic restrictions may exist in the Reservation TSI field (Bytes 32-33), and/or the Confirmed Geo Spec Table (Bytes 38-45), and/or the Ticketing TSI field (Bytes 61-62). All of these fields are action fields, specifying a portion of travel that must be validated. If any of the values in these fields does not validate against the fare component, pricing unit or journey (depending upon the TSI) for the fare component being priced, then processing will fail the table and read on to the next subset. When all of the values in these fields validate against the fare component, pricing unit or journey (depending upon the TSI) for the fare component being priced, then processing will measure advance reservations based on the data in the Reservation TSI field (Bytes 32-33), confirmed sectors based on the data in the Confirmed Geo Spec Table (Bytes 38-45), and advance ticketing based on the data in the Ticketing TSI field (Bytes 61-62).

Once the Category 5 Record 3 table has been matched based on the Override Date Table and Exception Time, if the portion of travel identified by the TSI is on the fare component, pricing unit or journey (depending upon the TSI) for the fare component being validated, then all advance ticketing requirements in bytes 56-60 will be measured from the portion of travel identified by the TSI. The TSI only identifies the portion of travel from which advance ticketing requirements will be measured. It does not alter the measurement of confirmed sectors or advance reservation requirements. Measurement of confirmed sectors is based on data in the Confirmed Sectors Fields (Bytes 37-46) and measurement of advance reservations is based on data in the Reservation TSI field (Bytes 32-33).

Page D.03.05.101 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When validating the TSI against the itinerary, if the specified portion of travel is applicable to several points on the itinerary, then measure the advance ticketing requirement from the first applicable point. If the same TSI is entered in the Reservation TSI field (Bytes 64-67), then the advance reservation and ticketing requirements should be applied from the same point.

Example 1 Record 3: Byte 56 Bytes 57-59 Byte 60 Bytes 61-62 Tkt – Tkt – Tkt – Tkt – Option Dept Dept Unit TSI R 007 D 06 The data above represents that for the fare component being validated, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround; ticket issuance is required 7 days before departure from the origin gateway (TSI 06).

Itinerary – ATL-LON OW fare component: Sectors Departure Date Ticketing Date ATL-NYC 01 Jan 99 28 Dec 98 NYC-LON 04 Jan 99 28 Dec 98

Dept 01Jan 99 Dept 04Jan99 ATL NYC LON

Ticketing window: Dept from Origin gateway: Ticketing required by: 04 Jan 99 28 Dec 98

When pricing the ATL-LON fare component that resolves to a single Record 3 as coded above: PASS – Ticket is being issued 7 days before departure from origin gateway (NYC depart 04Jan).

Itinerary – ATL-LON OW fare component: Sectors Departure Date Ticketing Date ATL-LON 01 Jan 99 28 Dec 98

Page D.03.05.102 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Dept 01Jan 99 ATL LON

Reservation window: Dept from Origin gateway: Ticketing required by: 01 Jan 99 25 Dec 98

When pricing the ATL-LON fare component that resolves to a single Record 3 as coded above: FAIL – Ticket is being issued less than 7 days before departure from origin gateway (ATL depart 01Jan); therefore, fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.103 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (TSI 03 – each trip) Record 3: Byte 56 Bytes 57-59 Byte 60 Bytes 61-62 Tkt – Tkt – Tkt – Tkt – Option Dept Dept Unit TSI R 001 M 03 The data above represents that for the fare component being validated, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround; ticket issuance is required 1 month before departure of the first flight of the fare component (TSI 03 – each trip).

Itinerary – LON-SYD round trip: Sectors Departure Date Ticketing Date LON-SYD 01 Nov 99 15 Oct 99 SYD-LON 20 Nov 99 15 Oct 99

Dept 01Nov99 LON SYD Dept 20Nov99 Ticketing window: Dept from Fare component origin: Ticketing required by: 01 Nov 99 from LON 01 Oct 99 20 Nov 99 from SYD 20 Oct 99

When pricing the LON-SYD fare component that resolves to a single Record 3 as coded above: FAIL – Ticket is being issued less than one month before departure of the originating flight of the fare component (LON depart 01Nov); therefore, fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

When pricing the SYD-LON fare component that resolves to a single Record 3 as coded above: PASS – Ticket is being issued earlier than 1 month before departure of the originating flight of the fare component (SYD depart 20Nov).

Page D.03.05.104 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (TSI not validated on itinerary) Record 3: Byte 56 Bytes 57-59 Byte 60 Bytes 61-62 Tkt – Tkt – Tkt – Tkt – Option Dept Dept Unit TSI R 001 M 40 The data above represents that for the fare component being validated, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround; ticket issuance is required 1 month before departure of the outbound transatlantic sector (TSI 40).

Itinerary – SEA-BKK round trip: Sectors Departure Date Ticketing Date SEA-BKK 28 Feb 99 01 Jan 99 BKK-SEA 30 Mar 99 01 Jan 99

Dept 28Feb99 SEA TPE BKK Dept 30Mar99

Ticketing window: Dept from Outbound transatlantic sector: Ticketing required by: N/A N/A

When pricing the SEA-BKK and BKK-SEA fare components that each resolve to a single Record 3 as coded above: FAIL – Processing cannot validate an outbound transatlantic sector. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.105 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 4 (TSI Validates Against Multiple Points) Record 3: Byte 56 Bytes 57-59 Byte 60 Bytes 61-62 Tkt – Tkt – Tkt – Tkt – Option Dept Dept Unit TSI R 014 D 07 The data above represents that for the fare component being validated, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround; ticket issuance is required 14 days before departure of the overwater segment.

Itinerary – three component circle trip BOS-ANC-HNL-BOS: Sectors Departure Date Ticketing Date BOS-SEA 31 Jul 99 10 Jul 99 SEA-ANC 31 Jul 99 10 Jul 99 ANC-HNL 15 Aug 99 10 Jul 99 HNL-LAX 01 Sep 99 10 Jul 99 LAX-BOS 11 Sep 99 10 Jul 99

Dept 31Jul99 Dept 31Jul99 BOS SEA ANC Dept 15Aug99

LAX Dept 11Sep99

HNL Dept 01Sep99

Ticketing window: Dept from Overwater segment: Ticketing required by: 31 Jul 99 17 Jul 99

Page D.03.05.106 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the BOS-ANC, ANC-HNL, and HNL-BOS fare components that each resolve to a single Record 3 as coded above: PASS – Ticketing is measured from the departure of the overwater segment. In this example, an overwater segment exists on the following sectors: SEA-ANC of the BOS-ANC fare component, ANC-HNL of the ANC-HNL fare component, and HNL- LAX of the HNL-BOS fare component. When the Ticketing TSI validates against multiple points, the ticketing requirement will be applied to the first point: SEA-ANC. Tickets are being issued more than 14 days before departure from SEA.

4.1.14 Advance Ticketing - Both - Byte 63

When advance ticket requirements are specified as both a time before departure and time after reservations, this field is used to indicate that either the earlier or the latter of the two ticket issuance requirements apply. When ‘earlier’ is indicated, the first date of the two advance ticketing requirements applies. When ‘later’ is indicated, the last date of the two advance ticketing requirements applies.

Page D.03.05.107 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 1 (Earlier) Record 3: Bytes 51-53 Bytes 54-55 Byte 56 Bytes 57-59 Byte 60 Byte 63 Tkt - Period Tkt - Unit Tkt Opt Tkt Dept Tkt Dept - Unit Tkt Both 007 Db R 007 D E For the fare component being validated, the data above represents that ticket issuance is required 7 days after reservations are made or at least 7 days before departure, which ever comes first.

Itinerary A – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 31 Dec 97 01 Dec 97 09 Dec 97

Depart 31Dec97 PAR LON

Ticketing window: Dept from pricing unit origin: For Reservation: Ticketing Required after Res by: Ticketing Required before Dept by: 31 Dec 97 01 Dec 97 08 Dec 97 24 Dec 97

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: FAIL – Ticketing is required the earlier of 7 days after reservations or 7 days before departure. The earliest date is 08 Dec 97, and the ticket is issued 09 Dec 97; therefore, fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.108 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 31 Dec 97 01 Dec 97 07 Dec 97

Depart 31Dec97 PAR LON

Ticketing window: Dept from pricing unit origin: For Reservation: Ticketing Required after Res by: Ticketing Required before Dept by: 31 Dec 97 01 Dec 97 08 Dec 97 24 Dec 97

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: PASS – Ticketing is required the earlier of 7 days after reservations or 7 days before departure. The earliest date is 08 Dec 97, and the ticket is issued 07 Dec 97; therefore, pass the table.

Page D.03.05.109 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (Later) Record 3: Bytes 51-53 Bytes 54-55 Byte 56 Bytes 57-59 Byte 60 Byte 63 Tkt - Period Tkt - Unit Tkt Opt. Tkt Dept. Tkt Dept. - Unit Tkt Both 007 Db R 007 D L For the fare component being validated, the data above represents that ticket issuance is required 7 days after reservations are made or at least 7 days before departure, which ever comes later.

Itinerary A – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 31 Dec 97 01 Dec 97 09 Dec 97

Depart 31Dec97 PAR LON

Ticketing window: Dept from pricing unit origin: For Reservation: Ticketing Required after Res by: Ticketing Required before Dept by: 31 Dec 97 01 Dec 97 08 Dec 97 24 Dec 97

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: PASS - Ticketing is required the later of 7 days after reservations or 7 days before departure. The latest date is 24 Dec 97, and the ticket is issued 09 Dec 97.

Page D.03.05.110 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 31 Dec 97 01 Dec 97 07 Dec 97

Depart 31Dec97 PAR LON

Ticketing window: Dept from pricing unit origin: For Reservation: Ticketing Required after Res by: Ticketing Required before Dept by: 31 Dec 97 01 Dec 97 08 Dec 97 24 Dec 97

4.1.15 Advance Ticketing - Exception Time - Bytes 64-67

This field is used to indicate that the ticketing requirements are only applicable if reservations are made by the time specified. The Exception Time is a match field, and the data specified within the Record 3 table will only apply if the reservation time matches the Exception Time.

Application of the Exception Time is an exception to Record 2 string processing. When the Exception Time is coded and matched (and the Override Date Table is also matched), processing must pass or fail on that table. Processing cannot read on to any other tables.

Page D.03.05.111 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example THEN Record 3: Bytes 51-53 Bytes 54-55 Byte 56 Bytes 57-59 Byte 60 Byte 63 Bytes 64-66 Byte 67 Bytes 82-89 Tkt Period Tkt Unit Tkt Opt Tkt Dept Tkt Dept Unit Tkt Both Tkt Excpt Tkt Excpt Unit Table 994 014 Db Blank Blank Blank Blank 060 D Blank OR Record 3: Bytes 51-53 Bytes 54-55 Byte 56 Bytes 57-59 Byte 60 Byte 63 Bytes 64-66 Byte 67 Bytes 82-89 Tkt Period Tkt Unit Tkt Opt Tkt Dept Tkt Dept Unit Tkt Both Tkt Excpt Tkt Excpt Unit Table 994 Blank Blank R 007 D Blank 030 D Blank

For the fare component being validated, the data above represents that confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. When reservations are made at least 60 days before departure of the originating flight of the pricing unit, ticket issue must be within 14 days after reservations are made. When reservations are made at least 30 days before departure of the originating flight of the pricing unit, tickets must be issued 7 days before departure of the originating flight of the pricing unit.

Itinerary A – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 01 Sep 99 01 Jan 99 20 Jan 99

Depart 01Sep99 PAR LON

Ticketing window (reservations more than 60 days before departure): Dept from pricing unit origin: For Reservation: Ticketing Required after Res by: Ticketing Required before Dept by: 01 Sep 99 01 Jan 99 15 Jan 99 Not restricted

Page D.03.05.112 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: FAIL • Reservations are being made more than 60 days before departure, and processing will match the first table and apply the ticketing restrictions in the first table. • Tickets are being issued later than 14 days after reservations are made. • Processing will fail the table and fail the fare. Processing will not read on to the next table because once the Exception Time is matched, the fare must pass or fail on that table.

Itinerary B – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 01 Sep 99 20 Jul 99 09 Aug 99

Depart 01Sep99 PAR LON

Ticketing window (reservations more than 30 days before departure): Dept from pricing unit origin: For Reservation: Ticketing Required after Res by: Ticketing Required before Dept by: 01 Sep 99 20 Jul 99 Not restricted 25 Aug 99

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: PASS • Reservations are being made less than 60 and more than 30 days before departure. Processing will no match the first table and read the second table. Processing will match the second table and apply the ticketing restrictions in the second table. • Tickets are being issued more than 7 days before departure of the originating flight of the pricing unit. • Processing will pass the table and pass the category.

Page D.03.05.113 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary C – PAR-LON round trip: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 01 Sep 99 20 Aug 99 01 Sep 99

Depart 01Sep99 PAR LON

Ticketing window (reservations less than 30 days before departure): Dept from pricing unit origin: For Reservation: Ticketing Required after Res by: Ticketing Required before Dept by: 01 Sep 99 20 Aug 99 Not restricted Not restricted

When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 as coded above: PASS • Reservations are being made less than 30 days before departure. Processing will no match the first table and read the second table. Processing will no match the second table. • As no further tables exist, apply the system assumption for this level.

Page D.03.05.114 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.16 Waiver Reservation Date - Bytes 68-74

This field is used to indicate a specific date that overrides the advance reservation requirements within the Record 3 table. When reservations are made on/before the Waiver Date, the specified reservation requirements in bytes 14-34 will not apply; however, the Confirmed Sector restrictions (Bytes 37-46) and Advance Ticketing restrictions (bytes 35, 47-67) within the table must still be processed. When reservations are made after the Waiver Date, apply the specified reservation requirements in bytes 14-34 along with the Confirmed Sector restrictions and Advance Ticketing restrictions. For example, this data may be used for carriers opening new service and where passengers would be unable to meet the standard advance reservation requirements.

When multiple reservation dates exist, validation of the Waiver Reservation Date will be against the latest reservation on the fare component being processed.

Page D.03.05.115 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 1: Record 3: Bytes 27-29 Bytes 30-31 Bytes 51-53 Bytes 54-55 Bytes 68-74 Last Res - Period Last Res - Unit Tkt - Period Tkt - Unit Wavier - Rsvn Date 014 Db 024 Hb 980101 For the fare component being validated, the data above represents that when reservations are made after 01Jan 98, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 14 days before departure of the origin flight of the pricing unit and ticketing is required 24 hours after reservations. When reservations are made on/before 01 Jan 98, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround and ticketing is required 24 hours after reservations.

Itinerary A – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 01 Feb 98 19 Jan 98 at 9am 19 Jan 98 at 4 pm

Depart 01Feb98 PAR LON

Reservation window (after 01 Jan 98) Dept from pricing unit origin: For Reservation: Res Required by: Ticketing Required after Res by: 01 Feb 98 19 Jan 98 at 9am 18 Jan 98 20 Jan 98 at 9 am

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: FAIL • Reservations are being made after 01 Jan 98; therefore, apply advance reservation requirements (bytes 14-34) in this table. • Reservations are being made later than 14 days before departure, and processing will fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.116 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 01 Feb 98 14 Dec 97 at 1pm 14 Dec 97 at 4 pm

Depart 01Feb98 PAR LON

Reservation window (on/before 01 Jan 98) Dept from pricing unit origin: For Reservation: Res Required by: Ticketing Required after Res by: 01 Feb 98 14 Dec 97 at 1pm Not restricted 15 Dec 97 at 1 pm

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: PASS • Reservations are being made on/before 01 Jan 98; therefore, do not apply advance reservation requirements (bytes 14-34) in this table. Advance ticketing requirements apply. • Tickets are being issued less than 24 hours after reservations, and processing will pass the table and pass the category.

Itinerary C – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 01 Feb 98 31 Dec 97 at 9am 02 Jan 98 at 10am

Depart 01Feb98 PAR LON

Reservation window (on/before 01 Jan 98) Dept from pricing unit origin: For Reservation: Res Required by: Ticketing Required after Res by: 01 Feb 98 31 Dec 97 at 9am Not restricted 01 Jan 98 at 9 am

Page D.03.05.117 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: FAIL • Reservations are being made on/before 01 Jan 98; therefore, do not apply advance reservation requirements (bytes 14-34) in this table. Advance ticketing requirements apply. • Tickets are being issued more than 24 hours after reservations, and processing fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.118 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (Multiple Reservation Dates): Record 3: Bytes 27-29 Bytes 30-31 Bytes 51-53 Bytes 54-55 Bytes 68-74 Last Res - Period Last Res - Unit Tkt - Period Tkt - Unit Wavier - Rsvn Date 014 Db 003 Db 000119 For the fare component being validated, the data above represents that when reservations are made after 19 Jan 00, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 14 days before departure of the origin flight of the pricing unit and ticketing is required 3 days after reservations. When reservations are made on/before 19 Jan 00, reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround and ticketing is required 3 days after reservations.

Itinerary – CHI-LON Round Trip: Sectors Departure Date Reservation Date Ticketing Date CHI-NYC 31Jan00 19Jan00 20Jan00 NYC-LON 31Jan00 18Jan00 20Jan00 LON-NYC 20Feb00 19Jan00 20Jan00 NYC-CHI 20Feb00 20Jan00 20Jan00

Res 19Jan00 Res 18Jan00 Dept 31Jan00 Dept 31Jan00 CHI NYC LON Dept 20Feb00 Dept 20Feb00 Res 20Jan00 Res 19Jan00

Reservation window (for Reservation on/before 19Jan00) Dept from pricing unit origin: Res Required by: Ticketing Required after Res by: 31Jan00 Not restricted 3 days after res

Reservation window (for Reservation after 19Jan00) Dept from pricing unit origin: Res Required by: Ticketing Required after Res by: 31Jan00 17Jan00 3 days after res

Page D.03.05.119 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing a CHI-LON fare component that resolves to a single Record 3 as coded above: PASS • Multiple reservations dates exist on the fare component: CHI-NYC reservation 19Jan00; NYC-LON reservation 18Jan00. Waiver Reservation date validates against the latest reservation date on the fare component: validate CHI-NYC reservation 19Jan00. • Reservations on this fare component are being made on/before 19Jan00; therefore, do not apply advance reservation requirements (bytes 14-34) in this table. Advance ticketing requirements apply. • Tickets are being issued less than 3 days after reservations, and processing pass the table (ticket 20Jan00 is less than 3 days after all reservation dates).

When pricing a LON-CHI fare component that resolves to a single Record 3 as coded above: FAIL • Multiple reservations dates exist on the fare component: LON-NYC reservation 19Jan00; NYC-CHI reservation 20Jan00. Waiver Reservation date validates against the latest reservation date on the fare component: validate NYC-CHI reservation 20Jan00. • Reservations on this fare component are being made after 19Jan00; therefore, apply advance reservation requirements (bytes 14- 34) in this table and advance ticketing requirements. • Reservations for all sectors prior to the point of turnaround are being made later than 14 days before departure, and processing will fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.120 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.17 Waiver Ticketing Date - Bytes 75-81

This field is used to indicate a specific date that overrides the advance ticketing requirements within the Record 3 table. When tickets are issued on/before the Waiver Date, the advance ticketing requirements specified in bytes 56-67 will not apply; however, the Advance Reservation restrictions (bytes 14-34), Advance Reservation – Ticketed (Byte 46 Res and Ticket at the same time), Confirmed Sector restrictions (Bytes 37-46), and Advance Ticketing After Reservation (Bytes 47-55) within the table must still be processed. When tickets are issued after the Waiver Date, apply the specified ticketing requirements in bytes 56-67 along with the Advance Reservation, Reservation and Ticket at the same time, Confirmed Sector, and Ticket after Reservation restrictions.

Example Record 3: Bytes 27-29 Bytes 30-31 Bytes 51-53 Bytes 54-55 Byte 56 Bytes 57-59 Byte 60 Byte 63 Bytes 68-74 Bytes 75-81 Last Res - Last Res - Tkt - Tkt – Tkt Tkt Tkt Tkt Wavier - Waiver - Period Unit Period Unit Opt Dept Dept – Both Rsvn Date Tkt Date Unit 003 Db 024 Hb R 007 D E Blank 971225 For the fare component being validated, the data above represents that when ticket issuance is after 25 Dec 97, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 3 days before departure of the origin flight of the pricing unit. Ticketing is required 24 hours after reservations or 7 days before departure of the origin flight of the pricing unit, whichever is earlier. When ticket issuance is on/before 25 Dec 97, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 3 days before departure of the origin flight of the pricing unit and ticketing is required 24 hours after reservations.

Page D.03.05.121 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary A – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 28 Dec 97 22 Dec 97 at 3pm 26 Dec 97 at 5pm

Depart 28Dec97 PAR LON

Reservation/Ticketing window (after 25 Dec 97) Dept from pricing unit origin: For Reservation: Res Required by: Ticketing Required after Res by: Ticketing Required before dept by: 28 Dec 97 22 Dec 97 at 3pm 25 Dec 97 23 Dec 97 at 3pm 21 Dec 97

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: FAIL • Tickets are issued after 25 Dec 97; therefore, apply advance ticketing requirements in bytes 56-67 in this table. • Reservations are being made earlier than 3 days before departure; however, tickets are being issued later than the earlier of 24 hours after reservations or 7 days before departure (later than 21 Dec 97). Processing will fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.122 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary B – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 28 Dec 97 22 Dec 97 at 3pm 25 Dec 97 at 9am

Depart 28Dec97 PAR LON

Reservation/Ticketing window (on/before 25 Dec 97) Dept from pricing unit origin: For Reservation: Res Required by: Ticketing Required after Res by: Ticketing Required before dept by: 28 Dec 97 22 Dec 97 at 3pm 25 Dec 97 23 Dec 97 at 3pm Not restricted

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: FAIL • Tickets are issued on/before 25 Dec 97; therefore, do not apply advance ticketing requirements in bytes 56-67 in this table. Advance reservation requirements and Ticketing after Reservation requirements will still apply • Reservations are being made earlier than 3 days before departure; however, tickets are being issued later than 24 hours after reservations (later than 23 Dec 97 at 3pm). Processing will fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.123 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Itinerary C – PAR-LON OW fare component: Sectors Departure Date Reservation Date Ticketing Date PAR-LON 25 Dec 97 22 Dec 97 at 3pm 22 Dec 97 at 9pm

Depart 25Dec97 PAR LON

Reservation/Ticketing window (on/before 25 Dec 97) Dept from pricing unit origin: For Reservation: Res Required by: Ticketing Required after Res by: Ticketing Required before dept by: 25 Dec 97 22 Dec 97 at 3pm 22 Dec 97 23 Dec 97 at 3pm Not restricted

When pricing a PAR-LON fare component that resolves to a single Record 3 as coded above: PASS • Tickets are issued on/before 25 Dec 97; therefore, do not apply advance ticketing requirements in bytes 56-67 in this table. Advance reservation requirements will still apply. • Reservations are being made earlier than 3 days before departure and tickets are issued within 24 hours after reservations are made. Processing will pass the table.

4.1.18 Override Date Table Number 994 – Bytes 82-89

A number referring to a table containing dates on which travel, ticketing and/or reservations are valid for the data in this category. When present, it further defines the specific date range within Effective/Discontinue dates of the Record 2. If the reservation, ticketing and/or travel dates of the fare being processed are not within the dates specified in the Override Date Table, no-match and continue processing. If no further tables/sets or all other tables contain 994 tables that do not match, apply the system assumption for this category. Refer to 994 Data Application for further details.

Page D.03.05.124 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.1.19 Text Table No. 996 - Bytes 90-97 and Unavailable Data Tag - Byte 98

When the Unavailable Data Tag is set to value ‘X’ (unavailable data), the fare being validated will fail the table; processing will read on to the next subset. When the Unavailable Data Tag is set to value ‘Y’ (text data only), retrieve the referenced 996 Text Table for text display. The 996 table has no impact on itinerary pricing; therefore, treat the table as not applicable and continue processing. If a single table is coded with an Unavailable Data Tag set to ‘Y’, the table would not be applicable and processing would apply the system assumption for this category. If a ‘Then, And’ set is coded and the ‘Then’ table has an Unavailable Data Tag set to ‘Y’, only the ‘And’ table would need to be satisfied.

Example 1 (Value X) Record 3 “THEN” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 007 Db Blank X Processing will fail the table due to the presence of value “X” in Byte 98.

Example 2 (Value X) Record 3 “THEN” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 007 Db Blank X Record 3 “OR” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 001 Mb Blank Blank For the first table, processing will fail the table as a result of the presence of value “X” in Byte 98; processing will read on to the next table. The data in the second table indicates that reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required 14 days before departure from the origin of the pricing unit.

Page D.03.05.125 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (Value X) Record 3 “THEN” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 007 Db Blank X Record 3 “AND” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 001 Mb Blank Blank For the first table, processing will fail the table as a result of the presence of value “X” in Byte 98; processing will not read on to the next table and will fail the set.

Example 4 (Value Y) Record 3 “THEN” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag Blank Blank 123 Y 996 Table Number 123 = text regarding advance res and ticketing. Record 3 “AND” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 001 Mb Blank Blank The data in the first table indicates that the table contains text data only and is not applicable for autopricing. The data in the second table indicates that reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required 14 days before departure from the origin of the pricing unit. Processing will not apply data in the first table and will read the second table. Conditions in the AND table must be satisfied in order to pass category validation.

Page D.03.05.126 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 5 (Value Y) Record 3 “THEN” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag Blank Blank 123 Y 996 Table Number 123 = text regarding advance res and ticketing. Record 3 “OR” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 001 Mb Blank Blank The data in the first table indicates that the table contains text data only and is not applicable for autopricing. The data in the second table indicates that reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required 14 days before departure from the origin of the pricing unit. Processing will not apply data in the first table and will read the second table. Conditions in the OR table must be satisfied in order to pass the category validation.

Page D.03.05.127 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 6 (Value Y in IF Condition) Record 3 “THEN” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 007 Db Blank Blank Record 3 Category 3 “IF” Bytes 44-51 Byte 52 Text Table No. 996 Unavailable Data Tag 123 Y Table Number 123 = Seasonal restrictions apply. Record 3 “ELSE” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 001 Mb Blank Blank The IF table contains text data only and is not applicable for autopricing; therefore, the data in the THEN table is also not applicable for autopricing. The data in the ELSE table indicates that reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required 14 days before departure from the origin of the pricing unit. Processing will apply data in the ELSE table, and conditions in this table must be satisfied in order to pass the category validation.

NOTE: This example is considered invalid coding. ATPCO coding convention holds that unavailable data tag Y (free form text only) should not be present in an IF condition.

Page D.03.05.128 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 7 (Value Y in THEN Condition of THEN/IF Set) Record 3 Category 5 “THEN” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag Blank Blank 123 Y 996 Table Number 123 = passenger must show passport as proof of identity. Record 3 Category 3 “IF” Byte 14 Bytes 15-20 Bytes 21-26 Byte 27 Seasonal Tag Start Stop Assumption Override Tag X 991202 991215 BLANK Record 3 Category 5 “ELSE” Bytes 27-29 Bytes 30-31 Byte 90-97 Byte 98 Last Res - Period Last Res - Unit Text Table # 996 Unavailable Data Tag 001 Mb Blank Blank The data indicates that when the first flight from the origin of the pricing unit is 01Dec 99 through 15Dec 99, then the data in the THEN table applies. The THEN table contains text data only and is not applicable for autopricing; therefore, when conditions in the IF table are met, processing will not apply the data in the THEN table, and the system assumption will apply. When conditions of the IF table are not met, processing will apply the data in the ELSE table.

4.1.20 Application of Data in Reservation, Ticket after Reservation, Ticket before Departure fields

Advance Reservation requirements are in the Advance Reservation fields (bytes 14-34) and the Waiver Reservation Date Field (Bytes 68-74). The relationship between the Advance Reservation fields and the Wavier Reservation Date is OR; processing must satisfy one of the two in order to pass the table.

Advance Ticketing requirements are in the Ticketing fields (Ticket After Reservation and Ticket Before Departure field’s bytes 35, 47- 67) and the Waiver Ticketing Date Field (Bytes 75-81). When data is present in both ticketing after reservation (Bytes 47-55) and ticketing before departure (bytes 56-62), the value in Both (Byte 63) will indicate whether the earlier or later of the two must be satisfied. The relationship between the Ticketing fields and the Wavier Ticketing Date is OR; processing must satisfy one of the two in order to pass the table.

Page D.03.05.129 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

The relationship between the Advance Reservation and Advance Ticketing requirements is AND. Both must be satisfied in order to validate the table.

Example 1 (Res/Tkt after Res) Record 3: Bytes Bytes Bytes Byte Bytes Bytes Bytes Byte Bytes Byte Bytes Byte 27-29 30-31 32-33 37 38-45 51-53 54-55 56 57-59 60 61-62 63 Last Res - Last Res - Res – Conf Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Tkt- Period Unit TSI Sector Geo Spec Period Unit Opt Dept Dept Unit TSI Both 014 Db Blank X Blank 024 Hb Blank Blank Blank Blank Blank The data represents that for the fare component being validated, reservations for all sectors of the pricing unit are required 14 days before departure from the origin of the pricing unit and ticketing is required 24 hours after reservation.

Itinerary – SYD-LAX round trip: Sectors Departure Date Reservation Date Ticketing Date SYD-LAX 20 Sep 99 06 Sep 99 at 2pm 07 Sep 99 at 9am LAX-SYD 03 Oct 99 06 Sep 99 at 2pm 07 Sep 99 at 9am

Depart 20Sep99 SYD LAX Depart 03Oct99

Reservation/Ticketing window Dept from pricing unit origin: For Reservation: Res Required by: Ticketing Required after Res by: 20 Sep 99 06 Sep 99 at 2pm 06 Sep 99 07 Sep 99 at 2pm

When pricing the SYD-LAX and LAX-SYD fare components that each resolve to a single Record 3 as coded above: PASS • Reservations are being made 14 days before departure. • Ticket is issued within 24 hours of reservations. (Ticket is issued less than 14 days before departure; however, there is no restriction on ticket issuance prior to departure. Processing will pass the advance ticket requirement of 24 hours after reservation.) • Processing will pass table and pass the category.

Page D.03.05.130 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 (Res/Tkt after Res/Tkt before Dept) Record 3: Bytes Bytes Bytes Byte Bytes Bytes Bytes Byte Bytes Byte Bytes Byte 27-29 30-31 32-33 37 38-45 51-53 54-55 56 57-59 60 61-62 63 Last Res - Last Res - Res – Conf Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Tkt- Period Unit TSI Sector Geo Spec Period Unit Opt Dept Dept Unit TSI Both 014 Db Blank X Blank 024 Hb R 014 D Blank E The data represents that for the fare component being validated, reservations for all sectors of the pricing unit are required 14 days before departure from the origin of the pricing unit and ticketing is required 24 hours after reservation or 14 days before departure from the origin of the pricing unit, whichever is first.

Itinerary – SYD-LAX round trip: Sectors Departure Date Reservation Date Ticketing Date SYD-LAX 20 Sep 99 06 Sep 99 at 2pm 07 Sep 99 at 9am LAX-SYD 03 Oct 99 06 Sep 99 at 2pm 07 Sep 99 at 9am

Depart 20Sep99 SYD LAX Depart 03Oct99

Reservation/Ticketing window: Dept from pricing unit origin: For Reservation: Res Required by: Tkt Req after Res by: Tkt Req before Dept by: 20 Sep 99 06 Sep 99 at 2pm 06 Sep 99 07 Sep 99 at 2pm 06 Sep 99

When pricing the SYD-LAX and LAX-SYD fare components that each resolve to a single Record 3 as coded above: FAIL • Reservations are being made 14 days before departure. • Ticket issuance is required the earlier of 24 hours after reservations or 14 days before departure of the origin flight of the pricing unit. The earlier is 14 days before departure (required 06Sep), and ticket is being issued after this date. • Processing will fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.131 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 (Res/Tkt after Res/Tkt before Dept - TSIs) Record 3: Bytes Bytes Bytes Byte Bytes Bytes Bytes Byte Bytes Byte Bytes Byte 27-29 30-31 32-33 37 38-45 51-53 54-55 56 57-59 60 61-62 63 Last Res - Last Res - Res – Conf Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Tkt- Period Unit TSI Sector Geo Spec Period Unit Opt Dept Dept Unit TSI Both 014 Db TSI 48 X TSI 43 024 Hb R 014 D TSI 48 E The data represents that for the fare component being validated, reservations for all transpacific sectors (TSI 43) of the pricing unit are required 14 days before departure of the first international sector (TSI 48). Ticketing is required 24 hours after reservation or 14 days before departure of the first international sector (TSI 48), whichever is first.

Itinerary – MEL-LAX round trip: Sectors Departure Date Reservation Date Ticketing Date MEL-SYD 20 Sep 99 06 Sep 99 at 2pm 07 Sep 99 at 9am SYD-LAX 22 Sep 99 06 Sep 99 at 2pm 07 Sep 99 at 9am LAX-SYD 03 Oct 99 06 Sep 99 at 2pm 07 Sep 99 at 9am SYD-MEL Open Open 07 Sep 99 at 9am

Depart 20Sep99 Depart 22Sep99 MEL SYD LAX Depart Open Depart 03Oct99

Reservation/Ticketing window: Dept from First international sector: For Reservation: Res Required by: Tkt Req after Res by: Tkt Req before Dept by: 22 Sep 99 06 Sep 99 at 2pm 08 Sep 99 07 Sep 99 at 2pm 08 Sep 99

Page D.03.05.132 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the SYD-LAX and LAX-SYD fare components that each resolve to a single Record 3 as coded above: PASS • Processing must validate a first international sector (TSI 48) and transpacific sector (TSI 43) portions of travel. • The first international sector is SYD-LAX. Advance reservations and ticketing will be measured from the departure from SYD. • Multiple transpacific sectors validate: SYD-LAX, LAX-SYD. Confirmed sector requirement applies for all transpacific sectors. • Reservations for all transpacific sectors are being made 14 days before departure of the first international sector (SYD-LAX depart 22Sep). • Ticket issuance is required the earlier of 24 hours after reservations (07Sep99 at 2pm) or 14 days before departure of the first international sector (08Sep99). The earlier is 24 hours after reservation (07Sep99 at 2pm) and ticket is being issued before this time. • Processing will pass table and pass the category.

Page D.03.05.133 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 4 (Res/Tkt after Res/Tkt before Dept - TSIs) Record 3: Bytes Bytes Bytes Byte Bytes Bytes Bytes Byte Bytes Byte Bytes Byte 27-29 30-31 32-33 37 38-45 51-53 54-55 56 57-59 60 61-62 63 Last Res - Last Res - Res – Conf Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Tkt- Period Unit TSI Sector Geo Spec Period Unit Opt Dept Dept Unit TSI Both 014 Db TSI 48 X TSI 43 024 Hb R 014 D TSI 40 E The data represents that for the fare component being validated, reservations for all transpacific sectors (TSI 43) of the pricing unit are required 14 days before departure of the first international sector (TSI 48). Ticketing is required 24 hours after reservation or 14 days before departure of the outbound transatlantic sector (TSI 40), whichever is first.

Depart 20Sep99 Depart 22Sep99 MEL SYD LAX Depart Open Depart 03Oct99 Reservation Window: Dept from First international sector: Res Required by: 22 Sep 99 08 Sep 99

Ticketing Window: Dept from Outbound Transatlantic sector: For Reservation: Tkt Req after Res by: Tkt Req before Dept by: N/A N/A N/A N/A

Page D.03.05.134 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the SYD-LAX and LAX-SYD fare components that each resolve to a single Record 3 as coded above: FAIL • Processing must validate a first international sector (TSI 48), transpacific sector (TSI 43), and outbound transatlantic sector (TSI 40) portions of travel. • The first international sector is SYD-LAX. Advance reservations will be measured from the departure from SYD. • Multiple transpacific sectors validate: SYD-LAX, LAX-SYD. Confirmed sector requirement applies for all transpacific sectors. • Processing cannot validate an outbound transatlantic sector. • Processing will fail the table. Processing will read on to the next subset. If no further subsets, then fail the fare. (Note: if the Exception Time Bytes 64-67 is coded and matched, processing cannot read on and will fail Category 5 validation.)

Page D.03.05.135 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

4.2 Reconciliation between Footnote and Rule Levels

When Category 5 data is present in a fare rule and general rule, the data from both the fare rule and general rule will apply (unless Fare Rule Record 2 byte 102 General Rule Application is coded ‘X’). If a footnote exists for Category 5, the advance reservation and ticketing information in the footnote will override all advance reservation and ticketing information in the fare rule and general rule.

Example 1 – Fare Rule/General Rule

FARE RULE Record 2: Byte 102 blank Record 3: Bytes Bytes Bytes Byte Bytes Bytes Byte Bytes Byte Bytes 27-29 30-31 32-33 37 51-53 54-55 56 57-59 60 61-62 Last Res - Last Res - Res – Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Period Unit TSI Sector Period Unit Opt Dept Dept Unit TSI 021 Db Blank Blank Blank Blank Blank Blank Blank Blank

GENERAL RULE Record 3: Bytes Bytes Bytes Byte Bytes Bytes Byte Bytes Byte Bytes 27-29 30-31 32-33 37 51-53 54-55 56 57-59 60 61-62 Last Res - Last Res - Res – Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Period Unit TSI Sector Period Unit Opt Dept Dept Unit TSI Blank Blank Blank Blank 024 Hb Blank Blank Blank Blank

APPLICATION: Both Fare Rule and General Rule Apply The data above represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 21 days before departure of the originating flight of the pricing unit (fare rule), and ticket issuance is required 24 hours after reservations (general rule). Processing must validate conditions of both the fare rule and general rule in order to pass Category 5 validation.

Page D.03.05.136 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 2 – Fare Rule/General Rule

APPLICATION: Both Fare Rule and General Rule Apply The data above represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 21 days before departure of the originating flight of the pricing unit (fare rule), and reservations for all sectors of the pricing unit are required at least 14 days before departure of the originating flight of the pricing unit (general rule). Processing must validate conditions of both the fare rule and general rule in order to pass Category 5 validation.

Page D.03.05.137 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 3 – Fare Rule/General Rule Not Applicable FARE RULE Record 2: Byte 102 value “N” Record 3: Bytes Bytes Bytes Byte Bytes Bytes Byte Bytes Byte Bytes 27-29 30-31 32-33 37 51-53 54-55 56 57-59 60 61-62 Last Res - Last Res - Res – Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Period Unit TSI Sector Period Unit Opt Dept Dept Unit TSI 021 Db Blank Blank Blank Blank Blank Blank Blank Blank

APPLICATION: Only Fare Rule applies The data above represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 21 days before departure of the originating flight of the pricing unit (fare rule). Processing will only validate conditions in the fare rule in order to pass Category 5 validation.

Page D.03.05.138 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example 4 – Fare Rule/General Rule/Footnote

FOOTNOTE Record 3: Bytes Bytes Bytes Byte Bytes Bytes Byte Bytes Byte Bytes 27-29 30-31 32-33 37 51-53 54-55 56 57-59 60 61-62 Last Res - Last Res - Res – Conf Tkt - Tkt – Tkt – Tkt – Tkt – Tkt – Period Unit TSI Sector Period Unit Opt Dept Dept Unit TSI Blank Blank Blank X Blank Blank Blank Blank Blank Blank

APPLICATION: Only Footnote applies The data above represents that for the fare component being validated, reservations are required for all sectors of the pricing unit. Processing will only validate conditions in the footnote in order to pass Category 5 validation.

Page D.03.05.139 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

5.0 TRAVEL SEGMENT INDICATORS (TSIs)

Category 5 - Advance Reservation and Ticketing contains three Travel Segment Indicator fields as follow:

1. Reservation TSI field (Bytes 32-33) – defines the portion of travel from which the reservation restrictions must be measured. 2. Ticketing TSI field (byte 61-62) – defines the portion of travel from which the ticketing restrictions must be measured. 3. Confirmed Geographic Specification Table #995 (Bytes 38-45) – defines what portion of travel on the fare component, pricing unit, or journey must hold a confirmed status.

The TSI fields and the Geo Spec Table are action fields, specifying a portion of travel that must be validated. If any of the values in these fields does not validate against the pricing unit for the fare component being priced, then processing will fail the table and read on to the next subset. When all values in these fields validate against the pricing unit for the fare component being priced, each TSI will only apply to the group of fields that are modified by that specific TSI. The TSI will not apply to all of the fields in the Record 3. Processing will measure advance reservations based on the data in the Reservation TSI field (Bytes 32-33), confirmed sectors based on the data in the Confirmed Geo Spec Table (Bytes 38-45), and advance ticketing based on the data in the Ticketing TSI field (Bytes 61-62).

When data is entered in the Each Sector field (Byte 46), the measurement of advance reservations and the application of confirmed sectors is against the fare component being validated. The only applicable TSIs that may be entered in the Res TSI field (Bytes 32-33) and the Confirmed Geo Spec Table (Bytes 38-45) in conjunction with data in the Each Sector field are fare component or fare component/pricing unit TSIs.

Stopover TSIs

The TSI Data Application documentation defines a stopover for TSI processing as follows:

Occurs when a passenger breaks the journey at an intermediate point or fare break point and is not scheduled to depart in the time defined within the carrier’s tariff (usually 24 hours for international and 4 hours for domestic). The point of turnaround is always considered a stopover point. NOTE: This definition does not apply when validating Category 8 or Category 10.

For additional information on processing stopover TSIs, refer to Data Application for TSIs.

Page D.03.05.140 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

Example (TSI 05) Record 3: Bytes 18-20 Bytes 21-22 Bytes 23-26 Bytes 27-29 Bytes 30-31 Bytes 32-33 Bytes 37-46 First Res - First Res - Last Res - Last Res - Last Res - Res - TSI Conf Sectors Period Unit Time of Day Period Unit Blank Blank Blank 007 Db 05 Blank The data represents that for the fare component being validated, reservations for all sectors of all fare components in the pricing unit prior to the point of turnaround are required at least 7 days before departure from last point of stopover (TSI 05).

Itinerary – MSP-LON-MSP RT pricing unit: Sectors Departure Date Reservation Date MSP - NYC 04 Jan 99 28 Dec 98 NYC - LON 07 Jan 99 28 Dec 98 LON-NYC 22 Jan 99 28 Dec 98 NYC-MSP 22 Jan 99 28 Dec 98

Dept 04Jan 99 Dept 07Jan99(Stopover) NYC MSP LON Dept 22Jan99(Transfer) Dept 22Jan99 (Stopover) NYC

Reservation window: Dept from Last Point of Stopover: First Time Res Permitted: Res Required by: LON 22 Jan 99 Not restricted 15 Jan 99

Page D.03.05.141 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

When pricing the MSP-LON fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure from last point of stopover (TSI 05) LON. • Reservations for all sectors specified in the Confirmed Sectors fields are being made greater than 7 days before departure from last point of stopover (LON depart 22Jan, reservations required by 15Jan); therefore; pass the table.

When pricing the LON-MSP fare component that resolves to a single Record 3 as coded above: PASS • Confirmed Sectors fields are blank; therefore, confirmed reservations are required for all sectors of all fare components in the pricing unit prior to the point of turnaround. • Advance reservation period will be validated against the departure from last point of stopover (TSI 05) LON. • Reservations for all sectors specified in the Confirmed Sectors fields are being made greater than 7 days before departure from last point of stopover (LON depart 22Jan, reservations required by 15Jan); therefore; pass the table.

The following is a list TSIs used within Record 3 Category 5 (beginning with most common, listing in descending order. Statistics were compiled in April 2003)

TSI Definition Application Usage 01 Departure from Fare Origin PU 3274 26 Outside Geographic Type of Fare Origin PU 2400 27 Outside Geographic Type of Turnaround Point PU 1517 48 Departure of First International Sector FC/PU 750 11 Arrival at First Point of Stopover FC/PU 402 41 Departure of Outbound Transpacific Sector FC/PU 265 06 Departure From Origin Gateway FC/PU 126 40 Departure of Outbound Transatlantic Sector FC/PU 113 18 All International Sectors FC/PU 109

Page D.03.05.142 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

TSI Definition Application Usage 34 All International Sectors PU 52 42 Departure of Each Transatlantic Sector FC 40 33 Outside the Following Geographic Locale FC/PU/J 37 84 Arrival at First International Stopover Point FC/PU 32 82 Departure from Gateway FC/PU 25 50 Departure From the Following Geographic Locale FC/PU 22 63 Departure of First International Sector of the Journey J 14 31 Transatlantic Sector(s) FC/PU 10 59 Departure of Journey Origin J 10 25 All Segments FC/PU 7 75 All International Sectors of the Journey J 7 35 Departure From Point of Turnaround PU 4 56 Departure of Inbound Transatlantic Sector FC/PU 4 03 Departure of Each Trip FC 3 10 Arrival at Fare Destination PU 3 19 All Domestic Sectors FC/PU 3 86 Arrival at First Break Outside Country of Journey Origin PU 3 05 Departure From Last Point of Stopover FC/PU 2 24 Arrival at First Point of Stopover Outside the Geographic Locale FC/PU 2 32 Transpacific Sector(s) FC/PU 2 43 Departure of Each Transpacific Sector FC 2 49 Arrival at the Following Geographic Locale FC/PU 2 51 Departure of Each Fare Component FC 2 87 Departure of First Outbound Intercontinental PU 2 07 Departure of Overwater Segment FC/PU 1 17 Departure From Point of Stopover Farthest From the Fare Origin Geographically PU 1 21 Departure From Stopover FC/PU 1 83 Arrival at Gateway FC/PU 1

Page D.03.05.143 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

6.0 CODING CONVENTIONS

• 24 Hours versus One Day - 24 hours is clock hours; therefore, when a reservation is booked at 9am and the Category 5 states ‘tickets must be issued within 24 hours after reservations’, this means tickets must be issued before 9am the following day. Using the same example, when a reservation is booked at 9am, and Category 5 states ‘ticket within 1 day after reservations.’, the ticket would need to be issued before the end of the following day (midnight).

• Standby Value ‘L’ - Standbys are permitted for the same date as originally ticketed provided the new flight(s) and flight time(s) were originally allowed by the fare.

Example: A passenger was ticketed to travel on Friday November 29, 1997 on flight 100 MSP-FAR at 8am on a KSPCL fare. The passenger requests to standby for flight 200 at 5pm.

This provision indicates that standby is allowed on the same date (Friday, November 29, 1997) as originally ticketed provided the KSPCL Day/Time (Category 2), Flight Application (Category 4), and Routing provisions allow travel on the new flight number and flight time (Flight 200 at 5pm).

• Geographic Specification Table #995 (Bytes 38-45) - When geography is indicated as a portion of travel that must be booked in a confirmed status, Sector field (Byte 37) must be filled with value X. - When a city is entered in the Geo Spec Table, a TSI should also be entered in the Geo Spec Table because the application of the geo locs is within.

• TSIs and Geo Spec Table – When a TSI is entered in the Reservation TSI (Bytes 32-33), Confirmed Geo Spec Table (Bytes 38- 45), and Ticketing TSI (Bytes 61-62), the same TSI should be used in each of these fields.

• Confirmed Sector Values coded in conjunction with Standby/Waitlist values – When Confirmed Sectors Byte 37 is value X or N (confirmed reservations required for all sectors of the pricing unit) any Standby/Waitlist value in Byte 36 that permits waitlisting is not logical as waitlisting is only permitted on sectors that may be open.

Page D.03.05.144 Revised July 2014 DATA APPLICATION FOR CATEGORY 5 - ADVANCE RESERVATIONS AND TICKETING

• Advanced Ticketing: Ticket After Res and First Time Ticketing Permitted before Departure – Do not specify a Ticket After Reservation requirement (Bytes 47-55) in the same Record 3 table with a First Time Ticketing Permitted requirement (Byte 56 Value P and Bytes 57-60). (Byte 63 should be blank when Byte 56 is value P.)

Example Record 3: Bytes 51-53 Bytes 54-55 Byte 56 Bytes 57-59 Byte 60 Byte 63 Tkt - Period Tkt - Unit Tkt Opt. Tkt Dept. Tkt Dept. - Unit Tkt Both 024 Hb P 003 D E For the fare component being validated, the data above represents that ticket issuance is required 24 hours after reservations are made, or the earliest time ticketing is permitted is 3 days before departure, which ever comes earlier.

This coding cause’s comparison of a latest time required and earliest time permitted.

Itinerary: CHI-LON OW fare component: Res 10Jan00 Dept 01Feb00 CHI LON

For Reservations on 10Jan00, ticketing is required by 11Jan00. For Departure 01Feb00, reservations are not permitted until 29Jan00.

Comparison is against the latest time required – 11Jan00 and the earliest time permitted – 29Jan00.

Page D.03.05.145 Revised July 2014