Pending Data Application For Category 7 – Maximum Stay App... · DATA APPLICATION FOR CATEGORY 7...

45
. DATA APPLICATION CATEGORY 7 – MAXIMUM STAY 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. Copyright © 2002 by Airline Tariff Publishing Company All rights reserved

Transcript of Pending Data Application For Category 7 – Maximum Stay App... · DATA APPLICATION FOR CATEGORY 7...

.

DATA APPLICATION

CATEGORY 7 – MAXIMUM STAY

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.

Copyright © 2002 by Airline Tariff Publishing Company All rights reserved

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

.

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 ................................................................................................................................................................................. 4

3.0 DETAILED FIELD PROCESSING ............................................................................................................................................. 5

4.0 OVERVIEW .................................................................................................................................................................................... 7

4.1 APPLICATION OF DATA FOR MAXIMUM STAY .............................................................................................................................. 11 4.1.1 Appl (Byte 14) ...................................................................................................................................................................... 11 4.1.2 Time of Day (Bytes 15-18) .................................................................................................................................................. 14 Maximum Stay (Bytes 19-21) ............................................................................................................................................... 14 Unit of Time (Bytes 22-23)................................................................................................................................................... 14 4.1.3 Ticket Issuance Indicator (Byte 24) ...................................................................................................................................... 15 4.1.4 From / To Geographic Specification Tables (Bytes 25-32) (Bytes 33-40) ......................................................................... 16 4.1.5 Waiver (Byte 41) & Waiver Conditions (Bytes 66-76) ........................................................................................................ 29 4.1.6 Override Date Table (Bytes 42-49)....................................................................................................................................... 31 4.1.7 Text Table (Bytes 50-57) and Unavailable Data Tag (Byte 58) ........................................................................................... 31 4.1.8 Maximum Stay Date (Bytes 59-64) ...................................................................................................................................... 35 4.1.9 Earlier/Later (Byte 65) .......................................................................................................................................................... 36

4.2 RECONCILIATION BETWEEN FOOTNOTE AND RULE LEVELS .......................................................................................................... 39

5.0 TRAVEL SEGMENT INDICATORS (TSI) .............................................................................................................................. 40

6.0 CODING CONVENTIONS ......................................................................................................................................................... 43

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.01 Revised November 2015

1.0 OVERVIEW The Maximum Stay Category (Category 7) provides the capability to indicate the last time at which travel must commence or must be completed from the point specified by the To Geographic Specification Table (bytes 33-40). Calculation of this date may be based on travel commencement or ticket issuance, and the maximum stay may be stated as either a day of week or elapsed time. Maximum stay provisions are not processed on one way pricing units. If data exists in Category 7 applicable for a one way fare that is being used on a one way pricing unit, then processing will not validate the maximum stay; however, if a one way fare is used in a round trip, open jaw, or circle trip pricing solution, then the maximum stay provisions will apply. If this category is not present there are no maximum stay requirements, outside of the ticket validity applicable to the fare.

1.1 Data Requirements In order to validate the Maximum Stay Category, it is essential to know the following: • Days and Times of all flights for all fare components on the pricing unit and journey. • Date of Ticket Issuance.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.02 Revised November 2015

1.2 Basic Processing Overview

Apply system assumption; no maximum stay

requirements apply.

Validate Maximum Stay provisions against the pricing unit or journey

of the fare being priced.

Match to the Category 7, Record 2 as described in Record 2 Data Application.

(Record 2 Data Application includes Directionality, Outbound/Inbound, External If, etc.)

Is there an applicable Category 7 – Record 3 Based on: • Geographic Specifications • Date Overrides

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.03 Revised November 2015

2.0 DEFINITIONS AND ASSUMPTIONS

2.1 Definitions DAY Calendar day. Counting of days begins the day after departure. For example:

Departure Date = 01 January 0 days after departure (same day) = 01 January 1 day after departure = 02 January 7 days after departure = 08 January

MONTH(S) For the purpose of determining maximum stay requirements, a month means the period of time from a given date in

one month to the corresponding date in a subsequent month. For example: One month validity - 01 January – 01February Two Months validity - 15 January - 15 March Three months validity - 30 January – 30 April Exceptions Where the corresponding date does not exist in a shorter subsequent month, then the month(s) shall mean from a given date in one month to the last day of such shorter subsequent month. For example: One month validity - 30 January - 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 such subsequent month. For example One month validity - 31 January – 28/29 February Two month validity - 28/29 February – 30 April Three month validity - 30 April – 31 July

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.04 Revised November 2015

2.2 Assumptions The Assumptions when there is no data present for Category 7: When there is no Category 7 information (No Category 7 Record 2 that resolves to the fare, Inbound/Outbound, Directional Indicators, Geographic Specifications, and Date Overrides) the assumption is there are no maximum stay requirements outside of ticket validity of the fare. When there is data present for Category 7 that resolves to a fare then the following assumption applies: Maximum Stay is calculated from point specified in the From Geographic Specification Table to travel commencement or travel completion from the point specified in the To Geographic Specification Table. Maximum stay will be counted from the day after departure from the point specified in the From Geo Spec Table, unless the provision is specified in months. If the provision is specified in months, then minimum stay will be counted from the day of departure from the point specified in the From Geo Spec Table.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.05 Revised November 2015

3.0 DETAILED FIELD PROCESSING Byte Location Match / Action Definition / Processing Byte 1 RECORD TYPE

Key Match This field indicates the Record Number for which the data is formatted.

Byte 2 ACTION

Key Match This field indicates the type of processing to be taken in connection with the transaction - either new data or changed data.

Bytes 3-5 CATEGORY NUMBER

Key Match These fields indicate what rule or footnote category to which the data applies. For the Maximum Stay Category, it will always be 07.

Bytes 6-13 TABLE NUMBER

Key Match These fields indicate a number that links the Category 7 Record 3 to the associated Category Control Record 2.

Byte 14 APPL

Action This field indicates whether the travel Must Commence or Must be Completed by the restriction stated in the table from the point specified in the To Geo Spec Table (bytes 33-40).

Bytes 15-18 TIME OF DAY

Action This field indicates Time of Day when travel Must Commence or Must be Completed from the point specified in the To Geo Spec Table (bytes 33-40).

Bytes 19-21 MAXIMUM STAY

Action This field indicates if the maximum stay is calculated in an amount of elapsed time or a specified day of week.

Bytes 22-23 UNIT OF TIME

Action This field further defines MAXIMUM STAY field (bytes 19-21) as follows: If MAXIMUM STAY field is amount of elapsed time, this field indicates if the elapsed time is in Minutes, Hours, Days, or Months. If MAXIMUM STAY field is day of week, this field indicates the occurrence of the day of week.

Byte 24 TICKET ISSUANCE INDICATOR

Action This field indicates the measurement of maximum stay is from the day of ticket issuance.

Bytes 25-32 FROM GEOGRAPHIC SPECIFICATION TABLE

Match This field refers to a table number containing geographic information specifying the point from which maximum stay is calculated .

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.06 Revised November 2015

Byte Location Match / Action Definition / Processing Bytes 33-40 TO GEOGRAPHIC SPECIFICATION TABLE

Match This field refers to a table number containing geographic information specifying the point to which maximum stay is calculated.

Byte 41 WAIVER

Action This field indicates if the maximum stay can be extended until the next day or a specified date or time that service is provided.

Bytes 42-49 OVERRIDE DATE TABLE

Match This table further defines reservation, ticketing, and/or travel dates that the Maximum Stay applies to. The Override Date Table data must match the reservation, ticketing, and/or travel dates of the itinerary being priced, in order for the Maximum Stay to be applied.

Bytes 50-57 TEXT TABLE

Action This table refers to a table containing free form text regarding Category 7. The information within this table is not priceable data.

Byte 58 UNAVAILABLE DATA TAG

Action This field identifies that this fare can not be used for auto pricing or that this Record 3 contains only free-form text.

Bytes 59-64 MAXIMUM STAY DATE

Action This field indicates a specified maximum stay date.

Byte 65 EARLIER/LATER

Action This field indicates to apply the earlier or later of the calculated maximum stay versus the specified maximum stay date.

Bytes 66-71 WAIVER – DATE

Action This field indicates a specified date to which the maximum stay may be waived.

Byte 72 WAIVER – EARLIER/LATER

Action This field indicates to apply the earlier or later of the calculated waiver and the specified waiver date.

Bytes 73-75 WAIVER – PERIOD

Action This field indicates the elapsed time for the waiver conditions.

Byte 76 WAIVER – UNIT

Action This field defines the elapsed time in the PERIOD field (Bytes 73-75) as Days or Months.

Bytes 77-86 FILLER

Filler – Reserved for future use.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.07 Revised November 2015

4.0 OVERVIEW Prior to processing the Maximum Stay provisions in Category 7, an applicable Record 2 for Category 7 must be matched in order to determine the correct provisions and restrictions for the applicable fare being validated. After a Record 2 has been matched, the next step is to match a Category 7 Record 3 Table based on the Override Date Table and From and To Geographic Specification Tables. When the fare being validated does match to the Override Date Table and the From and To Geo Spec Tables, and the maximum stay restrictions specified within the Category 7 apply to the dates of travel on the portion of travel identified by the Geo Spec Tables, continue processing to an AND table. If no AND tables, then the fare passes processing for Category 7. When the fare being validated does match to the Override Date Table and the From and To Geo Spec Tables, and the maximum stay restrictions specified within the Category 7 do not apply to the dates of travel on the portion of travel identified by the Geo Spec Tables, 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 or the From or To Geo Spec Tables, this Category 7 is considered a no-match, and processing should continue to an OR table, AND table, or the next set. If another table or Set is not found, or also does not match, then apply the system assumption of no Maximum Stay restrictions outside of ticket validity of the fare. One Way Fares Maximum stay provisions are not processed on one way pricing units. If data exists in Category 7 applicable for a one way fare that is being used on a one way pricing unit, then processing will not validate the maximum stay. If a one way fare is used in a round trip, open jaw, or circle trip pricing solution, then the maximum stay provisions will apply. This application of Category 7 for one way fares applies when Category 7 is used as a main or qualifying category.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.08 Revised November 2015

Example – Category 7 used as an IF Condition for OW fare THEN Category 12 Record 3 Sur Type Byte 41

Sur Appl Byte 45

Amt Bytes 72-78

Curr Bytes 79-81

P BLANK + 0.00 USD IF Category 7 Record 3 Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 030 Db TSI 01 TSI 05 ELSE Category 12 Record 3 Sur Type Byte 41

Sur Appl Byte 45

Amt Bytes 72-78

Curr Bytes 79-81

P BLANK + 100.00 USD The data indicates that if travel from last stopover commences no later than 30 days after departure from fare origin, then there is no surcharge. Otherwise, a surcharge of USD 100.00 will apply to the pricing unit for waiving the maximum stay requirements. Itinerary A: NYC-LON one way Y fare Dept 01Jul 99 NYC LON When validating the NYC-LON fare component that resolves to the above Record 3s: Surcharge of USD 100 applies Maximum stay provisions are not processed on one way pricing units. Processing will no match the IF table and apply surcharge requirements in the ELSE table.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.09 Revised November 2015

Itinerary B: NYC-LON OW Y fare and 50% of LON-NYC Y2 fare priced round trip. Y fare Dept 01Jul 99 NYC LON Dept 20Jul 99 50% of Y2 fare When validating the NYC-LON Y fare component that resolves to the above Record 3s: No Surcharge Maximum stay provisions are processed for a one way fare used in a round trip pricing solution. Travel from last stopover (LON) commences less than 30 days after departure from fare origin (NYC); therefore, processing will match the IF table and apply surcharge requirements in the THEN table. Open/Surface Sectors When open sectors or surface sectors are permitted, the validation of any open or surface sectors is optimistic, but not unrealistic. Validation will be against the booked sectors, passing the open or surface sectors until such time that they are booked. Processing will validate all known information pertaining to the fare and may fail processing if there is enough information to ascertain that the open or surface sectors would fail when booked. (The allowance of open sectors is addressed in Category 5.) Example Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 001 Mb TSI 01 TSI 58 The data represents that travel from the last international sector must commence no later than 1 month after the day of departure from fare origin.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.10 Revised November 2015

Itinerary A: FAR-FNI and FNI-FAR fare components, priced round trip: Dept 01Jul 99 Dept 02Jul 99 FAR PAR FNI Open Dept 20Jul 99 When validating the FAR-FNI and FNI-FAR fare components that each resolve to the above Record 3: PASS The latest date travel on the last international sector (PAR-FAR) is permitted is 1 month after the departure from fare origin (FAR). As the PAR-FAR sector is open, processing will be optimistic and PASS both fare components until PAR-FAR is booked. Once booked, processing will revalidate to determine if the maximum stay restrictions are met. Itinerary B: FAR-FNI and FNI-FAR fare components, priced round trip: Dept 01Jul 99 Dept 02Jul 99 FAR PAR FNI Open Dept 10Aug 99 When validating the FAR-FNI and FNI-FAR fare components that each resolve to the above Record 3: FAIL The latest date travel on the last international sector (PAR-FAR) is permitted is 1 month after the departure from fare origin (FAR). Although the PAR-FAR sector is open, travel from FNI-PAR departs later than 1 month after departure from fare origin (FAR); therefore; booking the PAR-FAR sector within the maximum stay requirements will not be possible. Processing will fail the table and read on to the next subset. As no further subsets exist, fail the fare.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.11 Revised November 2015

4.1 Application of Data for Maximum Stay NOTE: The To Geo Spec Table (Bytes 33-40) is a required field and will be used in all coding examples. Unless the Ticket Issuance Indicator (Byte

24) is set to ‘X”, the From Geo Spec Table (Bytes 25-32) is also a required field and will be used in all coding examples. Required fields may not be present if the Unavailable Data Tag (Byte 58) is set to ‘Y’.

Bytes 14-40 represent a unit of thought describing the Maximum Stay provisions and the geographic points where the provision must be met in order to validate the fare.

4.1.1 Appl (Byte 14) The Appl field indicates whether the maximum stay specified in bytes Maximum Stay (bytes 15-23) or Maximum Stay Date (Bytes 59-64) applies for departure or arrival of the sector specified in the To Geographic Specification Table (bytes 33-40). When Appl value is C (Commence), processing will validate the point specified in the To Geo Spec Table. Departure of the sector from the specified point must commence no later than the designated maximum stay, calculated from the point specified in the From Geo Spec Table (bytes 25-32). When the Appl value is P (Complete), processing will validate the point specified in the To Geo Spec Table. Arrival of the sector from the specified point must be completed no later than the designated maximum stay, calculated form the point specified in the From Geo Spec Table. Example 1 (Commence) Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 030 Db Blank TSI 01 TSI 05 The data represents that travel from the last point of stopover must commence no later than 30 days after departure from fare origin.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.12 Revised November 2015

Itinerary: CHI-LON round trip. Dept 15Jan 99 CHI LON Dept 01Feb 99 Maximum Stay Window: when departing CHI on 15 Jan 99, departure from LON must begin no later than 14 Feb 99. When validating the CHI-LON and LON-CHI fare components that each resolve to the above Record 3: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from CHI and the departure from the last point of stopover on the pricing unit is departure from LON.

• The maximum stay is 30 days calculated from the departure from CHI (depart 15Jan), to the departure of the sector from LON (depart 16Feb). Travel from LON commences less than 30 days after departure from CHI. Processing will pass the table and pass the category.

Example 2 (Complete) Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

P 001 Mb Blank TSI 01 TSI 05 The data represents that travel from the last point of stopover must be completed no later than 1 month after departure from fare origin. Itinerary A: CHI-LON round trip. Dept 15Jan 99 Arrive 16Jan 99 CHI LON Arrive 01Feb 99 Dept 01Feb 99 Maximum Stay Window: when departing CHI on 15 Jan 99, arrival of the sector from LON (arrival in CHI) must be completed no

later than 15 Feb 99.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.13 Revised November 2015

When validating the CHI-LON and LON-CHI fare components that each resolve to the above Record 3: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from CHI and the departure from the last point of stopover on the pricing unit is departure from LON.

• The maximum stay is 1 month calculated from the departure from CHI (depart 15Jan), to the arrival of the sector from LON (arrival in CHI 01Feb). Arrival in CHI is completed in less than 1 month after departure from CHI. Processing will pass the table and pass the category.

Itinerary B: CHI-LON round trip (via NYC) Dept 15Jan 99 Arrive 15Jan 99 Dept 15Jan 99 Arrive 16Jan 99 CHI NYC LON Arrive 20Feb 99 Dept 20Feb 99 Arrive 10Feb 99 Dept 10Feb 99 Maximum Stay Window: when departing CHI on 15 Jan 99, arrival of the sector from LON (arrival in NYC) must be completed

no later than 15 Feb 99. When validating the CHI-LON and LON-CHI fare components that each resolve to the above Record 3: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from CHI and the departure from the last point of stopover on the pricing unit is departure from LON.

• The maximum stay is 1 month calculated from the departure from CHI (depart 15Jan), to the arrival of the sector from LON (arrival in NYC 10Feb). Arrival in NYC is completed in less than 1 month after departure from CHI. Processing will pass the table and pass the category.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.14 Revised November 2015

4.1.2 Time of Day (Bytes 15-18) Maximum Stay (Bytes 19-21) Unit of Time (Bytes 22-23)

The Time of Day field (Bytes 15-18) further restricts the maximum stay requirements to a specific time of day based upon the 24 hour clock (0000-2400). Travel from the point specified in the To Geo Spec Table field cannot commence/complete (depending upon the value in Byte 14) later than the time specified in Bytes 15-18. This field will always be received in conjunction with Maximum Stay (Bytes 19-21) and Unit of Time (Bytes 22-23) or with Maximum Stay Date (Bytes 59-64). The Maximum Stay (Bytes 19-21) and Unit of Time (Bytes 22-23) fields have a cross field edit, and a subscriber will never receive the Maximum Stay field without the Unit of Time present in Category 7 and vice versa. The Maximum Stay field may be populated with a 3 digit numerical value (000-999) or a 3 character alpha representation for the applicable Day of Week (Sun/Mon/Tue/Wed/Thu/Fri/Sat). The Unit of Time field further defines the maximum stay elapsed period of time in Minutes (Nb), Hours (Hb), Days (Db), Months (Mb), or occurrence of day of week (01-52). When the maximum stay field is populated with one of the following 3 alpha characters: Mon., Tue. Wed, Thu, Fri, Sat or Sun, the Unit of Time field will be used to define the value as an occurrence of the given Day of Week (01-52).

For example: SUN 01 = First Sunday TUE 05 = Fifth Tuesday

When the Maximum Stay field is populated with a 3 digit numeric entry, the Unit of Time field will be used to define the value as an elapsed period of time in Minutes (Nb), Hours (Hb), Days (Db), or Months (Mb).

For example: 007 Db = 7 Days 024 Hb = 24 Hours

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.15 Revised November 2015

4.1.3 Ticket Issuance Indicator (Byte 24) This field is used to override the assumption that Maximum Stay is calculated from departure from the point specified in the From Geo Spec Table (bytes 25-32) and should be calculated from the date of ticket issuance. When the Ticket Issuance Indicator is Blank, both the From and To Geo Spec Tables (bytes 25-32, 33-40) are required fields, and maximum stay will be calculated from departure from the point specified in the From Geo Spec Table to the earliest date travel can commence/complete from the point specified in the To Geo Spec Table. When the Ticket Issuance Indicator is value X, edits require that the From Geo Spec Table must be blank, and maximum stay will be calculated from the ticket issuance date to the earliest date travel can commence/complete from the point specified in the To Geo Spec Table. Example Record 3: Appl Byte 14

Time of Day Bytes 15-18

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 1400 001 Mb X Blank TSI 05 The data represents that travel from the last point of stopover must commence no later than 1400 hours 1 month after the date of ticket issuance. Itinerary: CHI-LON round trip. Ticket Issue Date = 01Jan 99 at 1000 h Dept 15Jan 99 at 1800 h CHI LON Dept 01Feb 99 at 1600 h Maximum Stay Window: for Ticket Issuance on 01 Jan 99, travel from LON must begin no later than 01 Feb 99 at 1400h.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.16 Revised November 2015

When validating the CHI-LON and LON-CHI fare components that each resolve to the above Record 3: FAIL • The actual maximum stay is calculated using the Ticket Issue Date and the To measurement points identified in the To Geo Spec

Tables. The ticket issue date on the pricing unit is 01Jan and the departure from the last point of stopover on the pricing unit is departure from LON.

• The maximum stay is 1 month 1400 hours, calculated from 01Jan (ticket issue date), to the departure from LON (01Feb). Departure from LON commences later than 1400 hours 1 month after the ticket issuance date.

4.1.4 From / To Geographic Specification Tables (Bytes 25-32) (Bytes 33-40) The From /Geographic Specification Table (Bytes 25-32) and the To Geographic Specification Table (33-40) in Category 7 are match fields. If the specified geographic points are not present on the pricing unit/journey, then processing will no match the table and read on to the next OR Table, AND Table, or Set. If the pricing unit/journey for the fare being processed does contain the specified geographic restrictions, then the maximum stay restrictions must be applied to the points indicated by the Geo Spec Tables. When there is a maximum stay period for a given fare, the From Geo Spec Table is a required field (unless Ticket Issuance Indicator Byte 24 is value X) and the To Geo Spec Tables is a required field, and they specify the points from which the maximum stay provision should be calculated. (Note: If a value of ‘X’ is received in the Ticket Issuance Indicator field the maximum stay must be calculated from the date of ticket issuance. In this scenario, edits prevent entering data in the From Geographic Specification Table since the Maximum Stay will be calculated from the date of ticket issuance.) Within each Geo Spec Table, there is the ability to enter a Travel Segment Indicator (TSI) and Geographic Locales. A TSI entry is required in both the From and To Geo Spec Tables for every Category 7 (unless Byte 24 is value X) and indicates the two points to be used in calculating the maximum stay. Processing will validate the TSIs specified in the Geo Spec Tables against the pricing unit/journey and calculate the maximum stay between those points. When validating any TSI that refers to a stopover, the TSI Data Application documentation states that a stopover 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 that this stopover application applies for TSI validation only.) For additional information on processing stopover TSIs, refer to Data Application for TSIs.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.17 Revised November 2015

In addition to TSIs, two Geographic Locales may be entered in each Geo Spec Table to further modify the maximum stay application. The relationship between the two locales in each table is OR, and the application of each locale is from/to. For example, maximum stay application could be calculated from the departure from gateway in Area 1 (TSI 82, Geo Loc Area 1). TSIs can be used with or without location data; however, some TSIs require locations to be present and some TSIs require locations to be blank. (Refer to Section C, Appendix G for a list of valid TSIs.) When validating the From Geo Spec Table (bytes 25-32) and identifying the point from which maximum stay will be calculated, if the specified geographic data is applicable to several points on the itinerary, then calculate maximum stay from the last applicable point. When validating the To Geo Spec Table (bytes 33-40) and identifying the point from which travel may commence/complete, if the specified geographic data is applicable to several points on the itinerary, then calculate maximum stay from the first applicable point. Round the World/Circle Trip Validation Round the World (RTW) and Circle Trip (CT) fares are priced as single fare components on a single pricing unit where the origin and destination of the fare component are the same point. For validating Maximum Stay, the point of turnaround is the furthest ticketed point on the fare component measured from fare component origin. The measurement is based on Great Circle Miles (GCM). Any TSI that validates against an outbound or inbound fare component is automatically a no match (since these fares are priced as a single fare component) and will not be applied. Refer to the TSI data application for more information on TSIs that require the establishment of outbound and inbound fare components. Please see Examples 9, 10, and 11 below for additional information. Example 1 (Day of Week) Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C SUN 01 BLANK TSI 01 TSI 05 The data represents that travel from the departure from last point of stopover (TSI 05) must commence no later than the first Sunday after departure from fare origin (TSI 01)

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.18 Revised November 2015

Itinerary: SEA-SAN round trip. Dept Tue 10Feb SEA SAN Dept Mon 16Feb Maximum Stay Window: when departing SEA on Tue 10 Feb, travel from SAN must begin no later than Sun 15 Feb. When validating the SEA-SAN and SAN-SEA fare components that each resolve to the above Record 3: FAIL • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from SEA and the departure from the last point of stopover on the pricing unit is departure from SAN.

• The maximum stay is the first Sunday calculated from the departure from SEA (depart 10Feb), to the departure from SAN (depart 16Feb). Travel from SAN commences after the first Sunday, and processing will fail the table and read on to the next table. As no further tables exist, fail the fare.

Example 2 (Same Day Return) NOTE: If the value of 000 Db is received this will be used to in conjunction with the value in Appl (Byte 14) to indicate that travel for departure/arrival at the

point specified in the To Geo Spec Table must commence or must be completed the SAME DAY as departure. Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 000 Db BLANK TSI 01 TSI 05 The data represents that travel from the departure from last stopover (TSI 05) must commence no later than the same day as departure from fare origin (TSI 01) Itinerary: DFW-HOU round trip. Dept 10Feb DFW HOU Dept 10Feb

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.19 Revised November 2015

Maximum Stay Window: when departing DFW on 10 Feb, travel from HOU must begin no later than 10 Feb. When validating the DFW-HOU and HOU-DFW fare components that each resolve to the above Record 3: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from DFW and the departure from the last point of stopover on the pricing unit is departure from HOU. (HOU is the point of turnaround, and the point of turnaround is always considered a stopover for TSI validation.)

• The maximum stay is 0 days (same day) calculated from the departure from DFW (depart 10Feb), to the departure from HOU (depart 10Feb). Travel from HOU commences the same day as departure from DFW, and processing will pass the table and pass the category.

Example 3 (One Day) Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 001 Db BLANK TSI 01 TSI 05 The data represents that travel from the departure from last stopover (TSI 05) must commence no later than 1 day after departure from fare origin (TSI 01) Itinerary: DFW-HOU round trip. Dept 10Feb DFW HOU Dept 11Feb Maximum Stay Window: when departing DFW on 10 Feb, travel from HOU must begin no later than 11 Feb. When validating the DFW-HOU and HOU-DFW fare components that each resolve to the above Record 3: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from DFW and the departure from the last point of stopover on the pricing unit is departure from HOU.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.20 Revised November 2015

• The maximum stay is 1 day calculated from the departure from DFW (depart 10Feb), to the departure from HOU (depart 11Feb). Travel from HOU commences within 1 day of departure from DFW, and processing will pass the table and pass the category.

Example 4 (Time of Day) Record 3: Appl Byte 14

Time of Day Bytes 15-18

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 1500 002 Mb BLANK TSI 48 TSI 36 The data represents that travel from the departure from last international stopover (TSI 36) must commence no later than 1500 hours, 2 months after the day of departure of the first international sector (TSI 48) Itinerary: NYC-LON, LON-PAR, PAR-NYC fare components priced on a three-component circle trip: Dept. 30Jun99 (0300h) Dept. 15Jul99 (1400h) NYC LON PAR

Dept. 31 Aug99 (1400h) Maximum Stay Window: when departing NYC on 30 Jun, travel from PAR must begin no later than 1500h on 31Aug. When pricing the NYC-LON, LON-PAR and PAR-NYC fare components that each resolve to a single Record 3 above: PASS

• The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec Tables. The departure from the first international sector on the pricing unit is departure from NYC and the departure from the last international stopover on the pricing unit is departure from PAR.

• The maximum stay is 2 months calculated from the day of departure from NYC (dept 30 Jun at 0300h) to the departure from PAR (dept 31 Aug 99 at 1400). In this provision, a specific time is also given, indicating that travel from PAR must commence no later than 1500h, two months from the day of departure from NYC. Departure from PAR cannot be any later that 1500 on 31 Aug99. Departure from PAR commences prior to the maximum stay requirement, and processing will pass the table and pass the category.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.21 Revised November 2015

Example 5 (Geo Spec Table Validates Against Multiple Points) Record 3: Appl Byte 14

Time of Day Bytes 15-18

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C Blank 030 Db BLANK TSI 01 TSI 07 The data represents that travel from the departure of the overwater segment (TSI 07) must commence no later than 30 days after departure from fare origin (TSI 01).

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.22 Revised November 2015

DAY-FAI, FAI-HNL, HNL-DAY fare components priced on a three-component circle trip: Dept 01Jun99 Dept 10Jun99 DAY SFO FAI Dept 15Jun99 LAX Dept 31Jul99 HNL

Dept 31Jul99 Maximum Stay Window: when departing DAY on 01 Jun, travel from SFO must begin no later than 01Jul. When pricing the DAY-FAI, FAI-HNL and HNL-DAY fare components that each resolve to a single Record 3 above: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from DAY. The departure on the overwater segment on the pricing unit is located, and an overwater segment exists on the following sectors: SFO-FAI sector of the DAY-FAI fare component; FAI-HNL sector of the FAI-HNL fare component; and HNL-LAX sector of the HNL-DAY fare component. When the To Geo Spec Table validates against multiple points on the itinerary, maximum stay calculation will be against the first point. In this example, overwater segment for the purpose of maximum stay calculation is SFO-FAI.

• The maximum stay is 30 days calculated from the day after departure from fare origin (TSI 01) DAY depart 01Jun, to the departure of the overwater segment (TSI 07) SFO-FAI depart 10Jun. The maximum stay requirement is met (travel from SFO is less than 30 days after departure from DAY). Processing will pass the table and pass the category.

Example 6 (From/To Geo Spec Tables Validate against Same Point) Record 3: Appl Byte 14

Time of Day Bytes 15-18

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C Blank 001 Mb BLANK TSI 50 c FRA TSI 05 The data represents that travel from the departure from last stopover (TSI 05) must commence no later than 1 month after the day of departure from FRA.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.23 Revised November 2015

LON-ATH, ATH-LON fare components priced round trip with a FRA-MUC-FRA side trip: MUC Dept 15Jun99 Dept 01Jun99 Dept 10Jun99 Dept 16Jun99 LON FRA ATH Dept 12Jul99 Dept 05Jul9

Maximum Stay Window: when departing FRA-LON on 12 Jul, travel from FRA-LON must begin no later than 12 Aug. When pricing the LON-ATH fare component that resolves to a single Record 3 above: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from FRA on the pricing unit is located, and departure from FRA exists on the following sectors: FRA-MUC sector of the LON-ATH fare component; FRA-ATH sector of the LON-ATH fare component; and FRA-LON sector of the ATH-LON fare component. When the From Geo Spec Table validates against multiple points on the itinerary, maximum stay calculation will be against the last point. In this example, for the purposes of maximum stay calculation, the departure from FRA will be on the FRA-LON sector of the ATH-LON fare component. The departure from the last point of stopover on the pricing unit is departure from FRA on the ATH-LON fare component. (The From and To points of calculation are the same point in this example.)

• The maximum stay is 1 month calculated from the day of departure from FRA (TSI 50 c FRA) on the FRA-LON sector, to the departure from last stopover (TSI 05) FRA also on the FRA-LON sector. The maximum stay requirement is met, and processing will pass the table and pass the category.

Example 7 (Fares used in Combination) Record 2: BE7NR fare Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 007 Db BLANK TSI 01 TSI 05 The data represents that for the BE7NR fare component being validated, travel from the departure from last stopover (TSI 05) must commence no later than 7 days after departure from fare origin (TSI 01)

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.24 Revised November 2015

Record 2: M2SUN fare Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C SUN 02 BLANK TSI 01 TSI 05 The data represents that for the M2SUN fare component being validated, travel from the departure from last stopover (TSI 05) must commence no later than the second Sunday after departure from fare origin (TSI 01) Itinerary: BOS-SAN round trip BE7NR fare Dept Sat 27 Nov 99 BOS SAN Dept Fri 04 Dec 99 M2SUN fare Maximum Stay Window for BE7NR: when departing BOS on 28Nov, travel from SAN must begin no later than 04Dec. Maximum Stay Window for M2SUN: when departing BOS on 28Nov, travel from SAN must begin no later than 05Dec. When validating the BE7NR BOS-SAN fare component that resolves to the above Record 3: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from BOS and the departure from the last point of stopover on the pricing unit is departure from SAN.

• The maximum stay is 7 days calculated from the departure from BOS (depart 27Nov), to the departure from San (depart 04Dec). Travel from SAN commences within the maximum stay requirement, and processing will pass the table and pass the category.

When validating the M2SUN SAN-BOS fare component that resolves to the above Record 3: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from BOS and the departure from the last point of stopover on the pricing unit is departure from SAN.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.25 Revised November 2015

• The maximum stay is the second Sunday calculated from the departure from BOS (depart 27Nov), to the departure from San (depart 04Dec). Travel from SAN commences within the maximum stay requirement, and processing will pass the table and pass the category.

Example 8 (Fares Used in Combination) Record 2: YHE21NR fare Record 3: Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C 021 Db BLANK TSI 48 TSI 36 The data represents that for the YHE21NR fare component being validated travel from the departure from last international stopover (TSI 36) must commence no later than 21 days after departure of the first international sector (TSI 48) Itinerary: LAX-SYD, SYD-AKL, AKL-LAX fare components priced on a three-component circle trip: Y Fare Dept. 10 Feb 99 Dept. 15 Feb 99 LAX SYD Y2 fare YHE21NR fare AKL

Dept. 27 Feb 99 Maximum Stay Window: when departing LAX 10Feb 99, departure from AKL must commence prior to 03Mar 99.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.26 Revised November 2015

When pricing the YHE21NR SYD-AKL fare components that each resolve to a single Record 3 above: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from the first international sector on the pricing unit is departure from LAX and the departure from the last international stopover on the pricing unit is departure from AKL.

• The maximum stay is 21 days calculated from the day of departure from LAX (dept 10Feb) to the departure from AKL (dept 27Feb). Departure from AKL is commences prior to the maximum stay requirement, and processing will pass the table and pass the category.

Example 9 (Round the World) Record 3: Appl Byte 14

Time of Day Bytes 15-18

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C Blank 030 Db BLANK TSI 01 TSI 35 The data represents that travel from the departure of point of turnaround (TSI 35) must commence no later than 30 days after departure from fare origin (TSI 01). LON-LON Round the World fare component: Dept 01Jun99 Dept 04Jun99 Dept 15Jun99 LON DXB TYO NYC SYD Dept 21Jul99 Dept 10Jul99 LAX HNL

Dept 20Jul99 Dept 16Jul99 Maximum Stay Window: when departing LON 01Jun 99, departure from SYD must commence prior to 01Jul 99. When pricing the LON-LON fare component that resolves to a single Record 3 above: FAIL • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from LON (01Jun99).

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.27 Revised November 2015

• The point of turnaround is determined to be SYD since it has the greatest GCM from the point of fare origin (LON) compared to other points on the pricing unit. The departure from the point of turnaround on the pricing unit is 10Jul99 (departure from SYD).

• The maximum stay is 30 days calculated from the day after departure from fare origin (TSI 01) LON, to the departure from the point of turnaround (TSI 35) SYD. The minimum stay requirement is not met (travel from SYD is more than 30 days after departure from LON), and processing will fail the table and read on to the next table. If no further tables exist, fail the fare.

Example 10 (Round the World) Record 3: Appl Byte 14

Time of Day Bytes 15-18

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C Blank 045 Db BLANK TSI 01 TSI 56 The data represents that travel from the departure of the inbound Transatlantic Sector (TSI 56) must commence no later than 45 days after departure from the fare origin (TSI 01). LON-LON Round the World fare component: Dept 01Jun99 Dept 04Jun99 Dept 15Jun99 LON DXB TYO NYC SYD Dept 21Jul99 Dept 10Jul99 LAX HNL

Dept 20Jul99 Dept 16Jul99 When pricing the LON-LON fare component that resolves to a single Record 3 above: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from LON (01Jun99). • Processing cannot match the departure of the inbound Transatlantic Sector since round the world fares are neither outbound or

inbound. • Continue processing to the next subset. If no further subsets, then apply the system assumption (no minimum stay restrictions).

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.28 Revised November 2015

Example 11 (Round the World) Record 3: Appl Byte 14

Time of Day Bytes 15-18

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C Blank 060 Db BLANK TSI 01 TSI 66 The data represents that travel from the departure of the last international sector of the journey (TSI 66) must commence no later than 60 days after departure from fare origin (TSI 01). LON-LON Round the World fare component: Dept 01Jun99 Dept 04Jun99 Dept 15Jun99 LON DXB TYO NYC SYD Dept 21Jul99 Dept 10Jul99 LAX HNL

Dept 20Jul99 Dept 16Jul99 When pricing the LON-LON fare component that resolves to a single Record 3 above: PASS • The actual maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec

Tables. The departure from fare origin on the pricing unit is departure from LON (01Jun99). The departure from the last international sector of the journey is located: NYC (21Jul99).

• The maximum stay is 60 days calculated from the day after departure from fare origin (TSI 01) LON, to the departure from the last international sector of the journey (TSI 66) NYC. The maximum stay requirement is met (travel from NYC is less than 60 days after departure from LON). Processing will pass the table and pass the category.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.29 Revised November 2015

4.1.5 Waiver (Byte 41) & Waiver Conditions (Bytes 66-76) The Waiver field (Byte 41) and the Waiver Conditions fields (Bytes 66-76) indicate whether the maximum stay may be waived and any conditions for such waiver. The Waiver field (Byte 41) has two values: Value ‘1’ Indicates that if service (scheduled flights) is not provided on the last day of the maximum stay, the maximum stay may

be extended to the next day that service (scheduled flights) is provided, and travel is valid on any flight on the next day.

Value ‘2’ Indicates that if service (scheduled flights) is not provided on the last day of the maximum stay, the maximum stay may be extended to the specified date in bytes 66-71 or the specified amount of calculated time in bytes 73-76.

If the waiver field is blank, then there is no waiver, and the maximum stay requirements must be applied in order for the fare to pass processing. The Waiver Conditions (Bytes 66-76) indicate that the maximum stay may be extended to a specific date or amount of time provided that scheduled flights are not provided on the last day of the maximum stay. When Waiver Conditions are present, the value in the Waiver field (Byte 41) will be ‘2’.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.30 Revised November 2015

Waiver Conditions may be specified as follows:

Waiver Date (bytes 66-71) Indicates that the maximum stay may be extended to a specific date when service (scheduled flights) is not provided on the last day of the maximum stay, specified in YYMMDD format.

Earlier/Later (byte 72) When both the Waiver Date (bytes 66-71) and the Period/Unit (bytes 73-76) are entered, byte 72 must

also be entered to indicate that the earlier (E) or later (L) of the two should be chosen. For example, if Waiver Date is 01Jun99 and the Period/Unit is 002 days, then byte 76 will specify that either the earlier or later of the two must be used.

Period/Unit (bytes 73-76) Indicates a calculated amount of elapsed time period in units of either days or months to which the

maximum stay may be extended. The unit identifies the preceding time period specified in day’s (D), or month’s (M).

If the Waiver field and Waiver Conditions are blank, then there is no waiver, and the maximum stay requirements must be applied in order for the fare to pass processing. Example Record 3: Appl Byte 14

Max. Stay Bytes 19-21

Unit of time Bytes 22-23

From Geo Spec Bytes 25-32

To Geo Spec Bytes 33-40

Waiver Byte 41

Waiver date Bytes 66-71

E/L Byte 72

Period Bytes 73-75

Unit Byte 76

C 001 Db TSI 01 TSI 05 2 990113 E 001 D The data represents that travel from the departure from last stopover (TSI 05) must commence no later than 1 day after departure from fare origin (TSI 01). Maximum stay may be extended to 1 day or until 13Jan 99, whichever is earlier, when service is not provided on the last day of the Maximum Stay. Itinerary: PAR-LON round trip Dept 09 Jan 99 PAR LON Dept 11 Jan 99

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.31 Revised November 2015

Maximum Stay Window: when departing PAR on 09Jan, travel from LON-PAR must begin no later than 10Jan. Waiver for May Stay Date of 10 Jan: earlier of 11 Jan or 13Jan. When pricing the PAR-LON and LON-PAR fare components that each resolve to a single Record 3 above: PASS Assuming there is no service (scheduled flights) offered on the last day of the maximum stay (one day after departure from PAR), the maximum stay requirements have been met as departure from last stopover (LON) on the LON-PAR fare component is 11Jan 99, which is the earlier of the two waiver options for travel from last stopover when no service is offered on the last day of the maximum stay.

4.1.6 Override Date Table (Bytes 42-49) 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 by 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.

4.1.7 Text Table (Bytes 50-57) and Unavailable Data Tag (Byte 58) When the Unavailable Data Tag is set to value ‘X’ (unavailable data), the fare being created 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 Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 001 Mb TSI 01 TSI 05 Blank X Processing will fail the table as a result of the presence of value ‘X’ in Byte 58.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.32 Revised November 2015

Example 2 (Value X) Record 3 THEN Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 001 Mb TSI 01 TSI 05 Blank X Record 3 THEN Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 002 Db TSI 01 TSI 05 Blank Blank For the first table, processing will fail the table as a result of the presence of value “X” in Byte 58; processing will read on to the next table. The data in the second table indicates that travel from the departure from last stopover must commence no later than 2 days after departure from fare origin. Example 3 (Value X) Record 3 THEN Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 001 Mb TSI 01 TSI 05 Blank X Record 3 AND Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 002 Db TSI 01 TSI 05 Blank Blank For the first table, processing will fail the table as a result of the presence of value “X” in Byte 58; processing will not read on to the next table and will fail the set. Example 4 (Value Y) Record 3 THEN Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

Blank Blank Blank Blank Blank 123 Y 996 Table Number 123 = text regarding maximum stay.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.33 Revised November 2015

Record 3 AND Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 002 Db TSI 01 TSI 05 Blank Blank The data in the first table indicates that the table contains text data only and is not applicable. The data in the second table indicates that travel from the departure from last stopover must commence no later than 2 days after departure from fare origin. 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. Example 5 (Value Y) Record 3 THEN Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

Blank Blank Blank Blank Blank 123 Y 996 Table Number 123 = text regarding maximum stay. Record 3 OR Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 002 Db TSI 01 TSI 05 Blank Blank The data in the first table indicates that the table contains text data only and is not applicable. The data in the second table indicates that travel from the departure from last stopover must commence no later than 2 days after departure from fare origin. 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 category validation. Example 6 (Value Y in IF Condition) Record 3 Category 7 THEN Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 001 Mb TSI 01 TSI 05 Blank Blank Record 3 Category 3 IF Bytes 44-51 Byte 52

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.34 Revised November 2015

Text Table No. 996 Unavailable Data Tag 123 Y

Table Number 123 = Seasonal restrictions apply. Record 3 Category 7 ELSE Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 002 Db TSI 01 TSI 05 Blank X The IF table contains text data only and is not applicable; therefore, the data in the THEN table is also not applicable. The data in the ELSE table indicates that travel from the departure from last stopover must commence no later than 2 days after departure from fare origin. Processing will only read 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. Example 7 (Value Y in THEN Condition of THEN/IF Set) Record 3 Category 7 THEN Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

Blank Blank Blank Blank Blank 123 Y 996 Table Number 123 = text regarding maximum stay. Record 3 Category 3 “IF” Byte 14 Seasonal Tag

Bytes 15-20 Start

Bytes 21-26 Stop

Byte 27 Assumption Override Tag

X 991202 991215 BLANK Record 3 Category 7 ELSE Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Text Table # 996 Bytes 50-57

Unavailable Data Tag Byte 58

C 002 Db TSI 01 TSI 05 Blank X The data indicates that when the first flight from the origin of the pricing unit is 02Dec 99 through 15Dec 99, then the data in the THEN table applies. The THEN table contains text data only and is not applicable; therefore, when conditions in the IF table are met,

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.35 Revised November 2015

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.8 Maximum Stay Date (Bytes 59-64) The Maximum Stay Date is the latest date that travel may depart/arrive at the point defined in the To Geo Spec Table (bytes 33-40). When Maximum Stay Date is entered, edits require a TSI entry in both the From and To Geo Spec Tables; however, the measurement point defined in the From Geo Spec Table (bytes 25-32) has no impact on the application of the Maximum Stay Date. Example Record 3 Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Max Stay Date Bytes 59-64

C Blank Blank TSI 01 TSI 05 981231 The data represents that travel for departure from last point of stopover (TSI 05) must be commence no later than 31 Dec 98 (From Geo Spec TSI 01 has no impact on the application of the Maximum Stay Date). Itinerary: LAX-TYO round trip Dept 21Dec 98 LAX TYO Dept 11 Jan 99 Maximum Stay Window: travel from TYO must begin no later than 31Dec 98. When pricing the LAX-TYO and TYO-LAX fare components that each resolve to a single Record 3 above: FAIL • The departure from last stopover is determined by looking at the TYO-LAX fare component. In this example, the last point of

stopover is TYO. • The latest date travel is permitted from the last point of stopover is 31Dec98. Travel from TYO is after the date specified;

therefore, processing will fail the table and read on to the next subset. If no further subsets, then fail the fare.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.36 Revised November 2015

4.1.9 Earlier/Later (Byte 65) When a maximum stay restriction is expressed as both a Maximum Stay Period (bytes 15-23) and a Maximum Stay Date (Bytes 59-64), Earlier/Later (Byte 65) is used to determine whether the earlier or later of the two applies. If this field is populated with “E”, the earlier of the two applies,; if this field is populated with “L”, the later of the two applies. Example 1 (Earlier) Record 3 Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Max Stay Date Bytes 59-64

Earlier/Later Byte 65

C 001 Mb TSI 01 TSI 05 981127 E The data indicates that travel for departure from last point of stopover (TSI 05) must commence no later than 1 month or 27 Nov 98, whichever is earlier, after departure from the fare origin (TSI 01). Itinerary A – Earlier Date: WAS-FRA round trip Dept 10 Nov 98 WAS FRA Dept 28 Nov 98 Maximum Stay is Earlier of the following: Maximum Stay Date = 27Nov 98 1 month after departure from fare origin (WAS) = 10Dec 98 When pricing the WAS-FRA and FRA-WAS fare components that each resolve to a single Record 3 above: FAIL

• The maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec Tables. The departure from the fare origin on the pricing unit is departure from WAS and the departure from the last point of stopover on the pricing unit is departure from FRA.

• In this example, travel from last stopover (FRA) must commence by the earlier of one month after departure from fare origin (dept WAS 10Nov98), or 27Nov 98. The earlier is 27Nov 98, and the passenger is departing from FRA on 28Nov 98, which does not meet the maximum stay requirements. Processing will fail the table and read on to the next subset. If no further subsets, then fail the fare.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.37 Revised November 2015

Itinerary B – Earlier Time: WAS-FRA round trip Dept 10 Oct 98 WAS FRA Dept 10 Nov 98 Maximum Stay is Earlier of the following: Maximum Stay Date = 27Nov 98 1 month after departure from fare origin (WAS) = 10Nov 98 When pricing the WAS-FRA and FRA-WAS fare components that each resolve to a single Record 3 above: PASS

• The maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec Tables. The departure from the fare origin on the pricing unit is departure from WAS and the departure from the last point of stopover on the pricing unit is departure from FRA.

• In this example, travel from last stopover (FRA) must commence by the earlier of one month after departure from fare origin (dept WAS 10Oct98), or 27Nov 98. The earlier is 10Nov 98, and the passenger is departing from FRA on 10Nov 98, which meets the maximum stay requirements. Processing will pass the table and pass the category.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.38 Revised November 2015

Example 2 (Later) Record 3 Appl Byte 14

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

From Geo Spec Tbl Bytes 25-32

To Geo Spec Tbl Bytes 33-40

Max Stay Date Bytes 59-64

Earlier/Later Byte 65

C 001 Mb TSI 01 TSI 05 981127 L The data indicates that travel for departure from last point of stopover (TSI 05) must commence no later than 1 month or 27 Nov 98, whichever is later, after departure from the fare origin (TSI 01). Itinerary A – Later Time: WAS-FRA round trip Dept 10 Nov 98 WAS FRA Dept 28 Nov 98 Maximum Stay is Later of the following: Maximum Stay Date = 27Nov 98 1 month after departure from fare origin (WAS) = 10Dec 98 When pricing the WAS-FRA and FRA-WAS fare components that each resolve to a single Record 3 above: PASS

• The maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec Tables. The departure from the fare origin on the pricing unit is departure from WAS and the departure from the last point of stopover on the pricing unit is departure from FRA.

• In this example, travel from last stopover (FRA) must commence by the later of one month after departure from fare origin (dept WAS 10Nov98), or 27Nov 98. The later is 1 month after departure from WAS (10Dec98), and the passenger is departing from FRA before 10Dec98 which meets the maximum stay requirements. Processing will pass the table and pass the category.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.39 Revised November 2015

Itinerary B – Later Date: WAS-FRA round trip Dept 10Oct 98 WAS FRA Dept 26Nov 98 Maximum Stay is Later of the following: Maximum Stay Date = 27Nov 98 1 month after departure from fare origin (WAS) = 10Nov 98 When pricing the WAS-FRA and FRA-WAS fare components that each resolve to a single Record 3 above: PASS

• The maximum stay is calculated using the From and To measurement points identified in the From and To Geo Spec Tables. The departure from the fare origin on the pricing unit is departure from WAS and the departure from the last point of stopover on the pricing unit is departure from FRA.

• In this example, travel from last stopover (FRA) must commence by the later of one month after departure from fare origin (dept WAS 10Oct 98), or 27Nov 98. The later is maximum stay date 27Nov 98 (1 month after departure from WAS is 10Nov 98), and the passenger is departing from FRA before 27Nov 98 which meets the maximum stay requirements. Processing will pass the table and pass the category.

4.2 Reconciliation between Footnote and Rule Levels For the application of merged footnote, fare rule and general rule levels, see Section 4.3 – Reconciling between the Levels of the Rule Process in Data Application for Record 2.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.40 Revised November 2015

5.0 TRAVEL SEGMENT INDICATORS (TSI) Travel Segment Indicators in Category 7 are part of the Geographic Specification Tables #995 and are match fields. If the specified TSIs are validated against the pricing unit/journey for the fare component being validated, then the maximum stay provisions within the Record 3 table will apply. As data within Category 7 is validated against the pricing unit/journey, valid TSIs are fare component/pricing unit, pricing unit, or journey based. TSIs in Category 7 are required fields as they provide a point of measurement from which the Maximum Stay conditions will be calculated 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. Example – TSI 05 Record 3 Appl Byte 14

Time of Day Bytes 15-18

Max Stay Bytes 19-21

Unit of Time Bytes 22-23

Tkt Issue Ind Byte 24

From Geo Spec Table Bytes 25-32

To Geo Spec Table Bytes 33-40

C Blank 030 Db BLANK TSI 01 TSI 05 The data represents that the departure from last stopover on the pricing unit (TSI 05) must commence no later than 30 days after departure of the first flight of the pricing unit (TSI 01).

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.41 Revised November 2015

Itinerary – AMS-MIL round trip (stopover in PAR outbound, transfer in PAR inbound and transfer at fare break in MIL): Dept 30Jun

Dept 01Jun PAR (stopover) AMS MIL (fare break transfer) PAR (transfer) Dept 30Jun

Dept 30Jun When pricing the AMS-MIL and MIL-AMS fare components that each resolve to the Record 3 above: For TSI 05 validation: • Establish all stopovers on the pricing unit: PAR (outbound), MIL (turnaround point). • Establish the termination point of the pricing unit: AMS. • Working backwards from AMS, mark the point and departure time from the first stopover encountered: MIL depart 30Jun. NOTE: Continue processing TSI 01 and the remainder of the data in Category 7. Following is a list of TSIs currently used in Category 7 and the amount of usage as of April 2003. The table is arranged by usage in descending order beginning with the most commonly used TSI. Usage is based on the number of Record 2 sequences with a Category 7 Record 3 table containing the specified TSI. TSI Definition Application Usage 01 Departure from Fare Origin PU 173308 05 Departure from Fare Origin FC/PU 159772 52 Departure of Last Sector FC/PU 10450 36 Departure From Last International Stopover Point FC/PU 2745 08 Departure from Fare Origin FC/PU 2392 48 Departure of First International Sector FC/PU 1927 56 Departure of Inbound Transatlantic Sector PU * 1109 35 Departure From Point of Turnaround PU 958 82 Departure from Gateway FC/PU 943 40 Departure of Outbound Transatlantic Sector PU * 923 58 Departure of Last International Sector FC/PU 357 06 Departure from Fare Origin FC/PU 142 34 Arrival at Point of Turnaround PU 94

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.42 Revised November 2015

TSI Definition Application Usage 41 Departure of Outbound Transpacific Sector PU * 72 55 Departure of Inbound Transpacific Sector PU * 56 10 Arrival at Fare Destination PU 50 17 Departure From Point of Stopover Farthest From the Fare Origin Geographically PU 49 11 Arrival at First Point of Stopover FC/PU 35 84 Arrival at First International Stopover Point FC/PU 33 07 Departure from Fare Origin FC/PU 20 63 Departure of First International Sector of the Journey J 14 85 From Last Fare Break Outside Country of Journey Origin PU * 13 86 Arrival at First Break Outside Country of Journey Origin PU * 10 18 All International Sectors FC/PU 7 46 Departure from Last Stopover Outside Geographic Type of Fare Origin PU 5 50 Departure From the Following Geographic Locale FC/PU 4 66 Departure of Last International Sector of the Journey J 4 19 All Domestic Sectors FC/PU 2 49 Arrival at the Following Geographic Locale FC/PU 2 12 Arrival at Destination Gateway FC/PU 1 25 All Segments FC/PU 1 31 Transatlantic Sector(s) FC/PU 1 39 Within Any One Country FC/PU 1 * The Data Application Working Group proposes that the application of these TSIs be changed to Pricing Unit in order to accurately

reflect intent and processing. ** Fare Component TSIs are not valid for use in Category 7. As of April 2003 statistics, there were none in use.

DATA APPLICATION FOR CATEGORY 7 – MAXIMUM STAY

Pending - Page D.03.07.43 Revised November 2015

6.0 CODING CONVENTIONS From and To Geo Spec Tables: When the point from which the maximum stay count begins is not defined in the rule, the ‘From’ portion of travel will be entered as ‘Departure from Fare Origin' (TSI 01). If the point from which travel may commence is not defined in the rule the ‘To’ portion will be entered as the ‘Last point of stopover' (TSI 05). Likewise, if outward destination is not defined it will be assumed that outward destination, point of turnaround, is the last point of stopover. Directionality: Calculation of maximum stay is done by going outside the fare component being validated and looking at the entire pricing unit. Processing will mark the points specified in the From and To Geo Spec Tables, on the pricing unit. The maximum stay is then counted from the departure from the point specified in the From Geo Spec Table to travel commencement from the point specified in the To Geo Spec table. As the provision is calculated by looking at the entire pricing unit/journey, any maximum stay restrictions based on directionality require the use of value 3 (Origin Loc 1) or value 4 (Origin Loc 2). Use of directionality value (From Loc 1), value 2 (To Loc 1), Inbound or Outbound is illogical.