BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW

Transcription

1 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW All rights reserved 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 2008 Airline Tariff Publishing Company. All rights reserved.

2 BAGGAGE ALLOWANCE AND CHARGES OVERVIEW Contents 1.0 OVERVIEW DATA REQUIREMENTS SUB CODE STRUCTURE (BAGGAGE TYPE) Sub Code Attributes Type of Service Commercial Name/Text/Picture BASIC PROCESSING OVERVIEW DEFINITIONS AND ASSUMPTIONS DEFINITIONS ASSUMPTIONS Embargoes No Data and No Match (Service Type E) Baggage Allowance for checked baggage No Data and No Match (Service Type A) Journeys To/From US/CA Journeys NOT To/From US/Canada Carry-on Baggage Allowance No Data and No Match (Service Type B) Pre-Paid Baggage Charges No Data and No Match (Service Type P) Currency Conversion and Rounding Baggage Charges No Data and No Match (Service Type C) Currency Conversion and Rounding Category 35 Baggage Data versus Baggage Data within the Optional Services Product Check-in Processing with Conflicting Data between the ticket and ATPCO data Baggage Specific High-Level Assumptions for what is In Scope for Baggage Processing Prepaid Baggage DETAILED FIELD PROCESSING PROCESSING PRICING BAGGAGE SERVICES Baggage Embargoes Services BT (Baggage Travel) and Carrier Whose Rules Apply Examples Baggage Allowance (Checked Baggage) Page 02 Revised August 2014

3 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW BT (Baggage Travel) and Carrier Whose Rules Apply Examples Carry-on Baggage Allowance BT (Baggage Travel) and Carrier Whose Rules Apply Examples Pre-Paid Baggage Services BT (Baggage Travel) and Carrier Whose Rules Apply Examples Baggage Charges Services Checked Baggage Charges Carry-on Baggage Charges BT (Baggage Travel) and Carrier Whose Rules Apply Pricing Solutions on the Baggage Travel (BT) Examples DISPLAYING SERVICES Examples Baggage Embargoes Baggage Allowance Services Carry-on Baggage Allowance Services Prepaid Baggage Charges Services Baggage Charges Services ATTACHMENT A BAGGAGE SELECTION BAGGAGE ALLOWANCE/PRE-PAID BAGGAGE/BAGGAGE CHARGES FOR CHECKED BAGGAGE BAGGAGE EMBARGOES AND CARRY-ON BAGGAGE (ALLOWANCE AND CHARGES) ATTACHMENT B DISCLOSURE REQUIREMENTS FOR UNITED STATES DEPARTMENT OF TRANSPORTATION (US DOT) CFR (B) REQUIRED DISCLOSURE AT TIME OF PASSENGER FARE QUOTE CFR (C) REQUIRED DISCLOSURE AT TIME OF PASSENGER TICKETING DETERMINING FIRST AND SECOND BAG CHARGE Page 03 Revised August 2014

4 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW 1.0 Overview The Optional Services subscription product defines both Optional Services (such as meals, seat assignments, and in-flight entertainment) and Baggage Allowance and Charges. These are differentiated by a distinct Service Type Code as follows: Optional Services Service Type M = Merchandise (irrelative of whether a ticket exists) Service Type T = Ticket related (must be associated to a passenger s ticket) Service Type F = Flight Related (must be associated to specific flight/s on a passenger s ticket) Service Type R = Rule Buster Service (must be associated to a specific fare component on a passenger s ticket and overrides reissue and/or refund conditions for that fare). Note this is also referred to as the Reissue/Refund Override Service. Service Type Z = Branded Fares (only for use in Branded Fares product) Baggage Allowance and Charges Service Type A = Baggage Allowance (for checked baggage) Service Type B = Carry-on Baggage Allowance Service Type C = Baggage Charges Service Type P = Prepaid Baggage Charges associated to the Baggage Travel (BT) Service Type E = Embargoes Baggage and Optional Services processing share the same data source, formats and structure (i.e. Records S5 and S7). However, they have their own unique processing requirements. This document provides a processing overview for Baggage Allowance and Charges (defined as Service Type A, B, C, P, or E). Refer to the Optional Services Overview Data Application for an overview of processing Optional Services (defined as Service Type M, T, F, Z or R). Page 04 Revised August 2014

5 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Baggage Processing applies the following high-level steps: 1. Determine the carrier whose rules apply and the travel (Baggage Travel) on which the baggage data applies. (This is defined in Attachment A - Baggage Selection of this document.) 2. Process Embargoes (Service Type E) Records S5 and S7 data. a. Any item defined as embargoed is not permitted as part of the free or checked baggage. 3. Process free baggage Allowance for checked bags (Service Type A) and carry-on bags (Service Type B) a. Any item not permitted within the free allowance must be processed as a charged item. 4. Process baggage charges for Prepaid (Service Type P) and Charges (Service Type C) a. Assess charges as applicable b. An item that is not permitted within the free allowance and not specified as a charge is assumed to be not permitted. The above steps are further defined below. Baggage processing first identifies the baggage type (allowance, carry-on baggage, embargoes, prepaid, and charges) that is being requested, and then determines the carrier whose rules should be considered. Processing next looks up the applicable service (baggage) type Record S5 and then determines the application for this type of baggage by processing the Record S7 as defined below. 1. Baggage Selection: Baggage processing uses a standard set of rules for baggage selection to determine the carrier whose rules apply and the Baggage Travel (BT) for which the baggage provisions apply. This standard set of rules is defined in Attachment A Baggage Selection. o Baggage selection is determined before gathering the services (S5 processing). o For travel not to/from the US or not to/from Canada, when the marketing carrier s rules apply based on the result of Reso 302 (see Attachment A Baggage Selection), processing must check to see whether the marketing carrier defers their baggage rules to the operating carrier. o For travel to/from the US (see Attachment A Baggage Selection), processing will first check to see whether the first marketing carrier is a US DOT carrier and if they defer their baggage rules to the most significant marketing carrier. o For travel to/from Canada (see Attachment A Baggage Selection), processing will first check to see whether the first marketing carrier is a Canadian Transportation Agency carrier and if they defer their baggage rules to the most significant marketing carrier. NOTE: Optional Services uses a data driven concurrence process using Record S6 data. However, Record S6 processing is not applicable to Baggage Selection processing. Page 05 Revised August 2014

6 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW 2. Processing different Baggage Services: Systems will process Baggage Allowance and Charges services (Service Types A, B, C, E and P) to meet the baggage provisions that apply within or are impacted by a carrier s conditions of carriage. Baggage processed as an Optional Service (Service Types F, T, R and M) may or may not be offered as a separate baggage service. For example, pre-paid excess baggage that is sold as a voucher (not associated to a flight) for a discount prior to check-in is considered an Optional Service whereas pre-paid baggage that is sold associated to a flight is considered a baggage service. The business need will drive whether or not Baggage Allowance and Charges services and/or Optional Services is processed. 3. Baggage Allowance (Checked and Carry-on) and Embargoes Processing: Processing is not only used to help in the calculation of charges, but can be done for other business reasons. For example, Baggage Allowance is processed for business reasons including but not limited to defining the free baggage allowance to put on a passenger ticket; applying at time of passenger check-in to see if the passenger is checking excess baggage; and/or determining carry-on allowance. Baggage Allowance is processed with a standard service type (A and B) and sub code (0DF for check baggage and 0LN for carry-on baggage) that keeps it distinct. Embargo processing results in determining baggage that is not permitted to be checked. NOTE: Refer to Figure 1 on the following page for an explanation of key differences between Optional Services and Baggage processing. Page 06 Revised August 2014

7 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Subscription Records The following primary Optional Services subscription records support the automation of all Baggage Allowance and Charges service types: Record S5 Sub Code Services Record (defines the baggage type and associated Service Type Code) Record S7 Services Provisions Record (defines the qualifying data and applicable allowance, charge, or embargo information) NOTE: Optional Services Concurrence Record S6 is not applicable for Baggage Allowance and Charges. For Baggage Services, a defined set of baggage selection rules based on IATA Resolution 302 are provided for systems to select the applicable carrier(s) and travel for which the baggage allowance and charges provisions specified within Records S5 and S7 apply. Baggage Selection, as a first step, does not require systems to process Record S6. Rather, systems will perform itinerary analysis and then, based on this itinerary analysis, will select a given carrier(s) baggage provisions within Records S5 and S7. Baggage Selection rules are detailed within Attachment A Baggage Selection at the end of this document. A brief description of each of these two records is provided on the following pages along with a processing overview of how they work in conjunction to support the pricing of Baggage Services. This is not a document describing the business display and/or customer interaction. Refer to individual Data Application documentation for each of the records for further information on pricing Baggage Services. Page 07 Revised August 2014

8 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Record S5 Sub Code Services Record Record S5 defines the service (baggage type) associated to a specific Sub Code by identifying the high-level Group Code for the service as well as a specific Sub Group and/or Description(s) that further classify the service. The Group Code, Sub Group, and Description codes (i.e. Attributes) allow systems to pinpoint the type of service applicable to a Sub Code and to compare/identify like services. The Sub Code will be further classified as industry-defined or carrier-defined. Data providers must identify (via Record S5) whether the service applicable for a Sub Code represents baggage allowance (for checked baggage); carry-on baggage allowance baggage charges; pre-paid baggage; or embargoes Baggage Allowance Generic Sub Codes Baggage Allowance for checked baggage (Service Type A) or Carry-on Baggage Allowance (Service Type B) use the following unique generic sub codes designated strictly for use in processing baggage allowance. These codes cannot be used with any other Service Type. 0DF = Baggage Allowance for checked baggage 0LN = Carry-on Baggage Allowance The codes are used to match to applicable Record S7 Provisions records which detail the free baggage allowance (piece, weight, etc.) and qualifying conditions. It is possible the same sub code is specified for multiple Baggage or Optional Services Types. The following Service Types may specify provisions for the same sub code: Baggage Charges (Service Type C), Pre-Paid Baggage (Service Type P), Optional Services baggage (Service Types, F*, T and M), and Embargoes (Service Type E). Page 08 Revised August 2014

9 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Example A sub code of ABC (heavy bag up to 70 pounds) may be designated as a pre-paid baggage service (P) with one price (USD 15) and a baggage charge (C) with another price (USD 25). In an extreme example, a carrier could use the same sub code to create four Record S5s 1. ABC for pre-paid baggage ( P ), 2. ABC that is sold as merchandise ( M ). 3. ABC that applies as a baggage charge ( C ) and 4. ABC that applies as an embargo ( E ). *Note: The industry has directed that pre-paid baggage charges associated to a flight should be filed as Pre-Paid baggage (Service Type P ). Upon initial pricing/display, processing must interrogate the Record S5 in order to determine what baggage services a carrier offers. Record S5 will specify where (at what point in processing) the service can be displayed. Additional data in the Record S5 is further used to determine the associated SSR code, filter offered services based on Group Code, Sub Group and/or Description, determine the EMD requirements and reason for issuance (RFIC), and/or provide the customer with the commercial name, text, and/or picture explanation of the service. Page 09 Revised August 2014

10 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Record S7 Services Provisions Record For Baggage processing, Record S7 specifies the travel, passenger, geographic, carrier, flight, fare, and sales requirements that apply to baggage allowance (checked and carry-on), baggage charges, embargoes and pre-paid baggage. Baggage Allowance for Checked Baggage For determining the checked baggage allowance, processing must first determine the carrier and BT (baggage travel) (based on Baggage Selection as described in Attachment A Baggage Selection). Once processing finds the applicable record with Service Type A and Sub Code 0DF (based on Record S5 Sub Code Services Record), then processing will interrogate and apply the data in Record S7. Carry-on Baggage Allowance For determining the carry-on baggage allowance, processing must find the operating carrier that applies on each sector (see Attachment A Baggage Selection). Once processing finds the applicable record with Service Type B and Sub Code 0LN (based on Record S5 Sub Code Services Record) for each operating carrier on each sector, then processing will interrogate and apply the data in Record S7. Baggage Charges (including Prepaid) For determining checked baggage charges and prepaid baggage charges, processing must use the same carrier and BT used for checked baggage allowance (Type A) along with the determined excess baggage criteria to look up a charge. Processing must find the applicable charges to look up by using the service (baggage) type identified in Record S5 and interrogating and applying the data in Record S7. Carry-on Baggage Charges For determining carry-on baggage charges, processing must use the same operating carrier and BT (where the BT is defined as a single sector) used for carry-on baggage allowance (Type B) along with the determined excess baggage criteria to look up a charge. Processing must find the applicable charges to look up by using the service (baggage) type identified in Record S5 with Group BG (Baggage) and Sub Group CY (Carry-on) and interrogating and applying the data in Record S7. NOTE 1: Prepaid baggage charges are not applicable for carry-on bags. NOTE 2: The carry-on data is always applied based on the operating carrier on each sector (there are no exceptions to this application.) Embargoes For determining embargoes, processing must find the operating carrier that applies on each sector (see Attachment A Baggage Selection) and interrogate the baggage records by using the service (baggage) type identified in Record S5 with Service Type E along with the applicable baggage criteria to look up the embargoes. Page 010 Revised August 2014

11 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW 1.1 Data Requirements Refer to individual data application documents for Records S5 and S7. Page 011 Revised August 2014

12 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW 1.2 Sub Code Structure (Baggage Type) The Sub Code Services Record S5 identifies the data elements required to automate baggage processing. It provides basic information about the baggage service (baggage type) in terms of who owns it, what it is and how it may be offered. It is validated against conditions defined in the Record S7 Services Provisions Record to determine whether it is permitted as part of the baggage allowance or subject to a charge. Baggage Services processing requires a unique identification of the baggage type within a carrier s data and across all carriers. To this end, every baggage type is uniquely identified by the combination of a Carrier Code (industry standard alphanumeric) and Sub-code (3 byte alphanumeric assigned by ATPCO or by the carrier). NOTE: Record S6 has no application for the purposes of baggage services (Service Type byte 21 values A, B, C, E and P ). All Sub Codes are published via the ATPCO bulletin publication process and posted on the ATPCO website. The Sub Code may be defined by a specific carrier for the carrier s own use or defined by ATPCO for industry use. The purpose of an industry standard structure for naming and qualifying baggage services is to support Consistent display and pricing between carriers Consistent display and pricing across all pricing systems Standard ticketing Standard reporting Sub Codes that are carrier-specific are unique only to that carrier and may not be sold or used for travel which includes any other airline. This section provides an overview of the Sub Code and descriptive Attributes that define the service. Refer to Data Application for Record S5 Sub Code Services Record for a full description of the fields and application of the record Sub Code Sub Codes are aligned to the IATA specifications for OC services which are defined by a 3 byte alphanumeric field. The original IATA design for OC service fees was for validating carrier only and does not meet the current requirements defined by the working group. However, since ticketing standards for the EMD employ the 3 byte alphanumeric field, this standard will apply to the Subcode. The OC designator will not appear on the EMD. Assignation of Sub Codes is at the discretion of ATPCO or the carrier and does not require an industry or standard naming protocol. Carrier-defined Sub Codes cannot duplicate industry-defined Sub Codes. Page 012 Revised August 2014

13 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Record S5 (byte 42) will identify the Sub Code as an Industry Defined (within an industry-standard definition so that the code can be used for online or interline travel) or Carrier Defined code (only for use in online travel) Attributes The elements that make up the Sub Code identification are: Carrier Code, Sub Code, and Attributes. Each Sub Code is identified in the Record S5 as carrier or industry defined and uniquely classified based on one or more of the following attributes: Group (required field) Sub Group (optional field) Description (optional fields) For Industry Defined Sub Codes, ATPCO will identify the attributes. All carriers can use the Industry Sub Codes, but edits prohibit any change to the Attributes. For Carrier Defined Sub Codes, carriers will identify the attributes at the time of initial creation of the Sub Code. The Sub Code and its associated Attributes is only applicable to the carrier that creates the Sub Code. Once the Sub Code is created, edits prohibit the carrier from changing the Attributes on the Record S5. For carrier-defined codes, it is important to realize that the Carrier and Sub Code are the unique identifiers for the service. It is possible that the same Sub Code will have different Attributes for different carriers. For example: Sub Code ABC may be a Bicycle for carrier XX but a Box for Carrier ZZ. Industry Defined and Carrier Defined Sub Codes will use the description attributes to define the individual dimensions for a given bag type. For example, an industry defined heavy bag (0FM) is defined as: Group (required field) = BG Sub Group (optional field) = Blank Description (optional fields) = 32 (translated using the Optional Services Attribute appendix to up to 70 lb/32 kg ) Description (optional fields) = 6U (translated using the Optional Services Attribute appendix to up to 62 li/158 lcm ) This description may be processed to define a bag s weight and size for the purposes of determining the free baggage allowance or a baggage charge. For example, at time of passenger check-in, if a passenger is checking a single bag that is 60 pounds, processing will resolve to the Record S5 service that contains the description up to 70 pounds. Then, to determine if the bag is within the free baggage allowance, processing will read the Record S7s with a service type of A and resolve to a record. Here processing will read through the free form text table (containing sub codes) to determine if a 0FM (bag between up to 70 pounds) pounds is permitted free. If so, the result will be returned that the bag is permitted free. If not, the 0FM will be taken to the Record S7 with a service type of Page 013 Revised August 2014

14 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW C to look for the heavy bag charge. The point of this example is that the attributes must be read and used for processing baggage services. Each of these attribute fields is fully described in the Record S5 Sub Code Services Record Data Application. Page 014 Revised August 2014

15 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Type of Service There are five distinct baggage service types in the Optional Services product. Concurrence processing does not apply for baggage services. Each type is distinguished by a common set of rules by its association to the purchase of: 1) Free checked baggage allowance: Service Type A 2) Free carry-on baggage allowance: Service Type B 3) Baggage charges: Service Type C 4) Baggage Embargoes: Service Type E 5) Pre-paid Baggage: Service Type P Each baggage Sub-code must be associated to a Type in the SERVICE TYPE field of Record S5 (byte 21). The same Sub Code (same service) can be offered as more than one type. For example the same baggage type can be defined for Type C (Baggage Charges) and Type P (Prepaid Baggage) Commercial Name/Text/Picture Edits require that each sub-code have a Commercial Name which can be used in the display of baggage services to the passenger. This is a 30-byte text field in the Record S5. Additionally Record S5 includes a Text Table to support descriptive information about of the baggage type. NOTE: A future development phase may include the ability to provide a picture. Page 015 Revised August 2014

16 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW 1.3 Basic Processing Overview After Baggage Selection, processing will attempt to match a Record S5 before attempting to match the Record S7. Which carriers are considered for Record S5 processing is dependent upon whether the service is baggage allowance (checked or carry-on), baggage charges, embargoes or pre-paid baggage as defined by Record S5 Service Type (byte 21). The high-level processing is illustrated on the following page. Page 016 Revised August 2014

17 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Perform pre-processing analysis (i.e. determine the furthest checked point, what baggage is being checked and where it is being checked to, all marketing and operating carriers on the Determine the carrier(s) and the resulting travel which will drive the resulting embargoes and/or free baggage allowance* (* See Attachment A - Baggage Selection at the end of this document) For Embargo Proecessing For Carry-on Allowances For Checked Baggage Allowances and Pre-paid/Charges For each sector in the itinerary, process the S5 for the operating carrier against Embargo data (Service Type E) For each sector in the itinerary process the S5 for the operating carrier against Carry-on allowance data (Service Type B and Sub Code 0LN) For each identified BT process the S5 for the carrier whose rules apply for checked baggage allowance( Service Type A and Sub Code 0DF) and prepaid/charges Process S7 for carrier whose rules apply for baggage allowance (Service Type A and Sub Code 0DF) to determine what is permitted within the free allowance. Process the S7 for any matched Embargo Record S5s. Is there a match? YES The baggage service is embargoed for this sector NO The baggage service is not embargoed for this sector and processing can validate for allowance and charges. Process the S7 for the matched Carry-on Allowance Record S5. Is there a match? YES Apply the specified Carry-on Allowance NO There is no free carry-on allowance. All carry-on bags are subject to a charge Process Record S7 for the carrier whose rules apply for carry-on baggage charges. Is there a match? NO Apply the free allowance for the applicable business purposes (e.g. put on the ticket, quote to the passenger, apply at check-in) YES Permitted within Allowance Not permitted within Allowance The service is subject to a charge. Process Record S7 Prepaid (Type P) and Charges (Type C) for the carrier(s) whose rules apply. Is there a match? YES NO The baggage service is not allowed as carry-on for this sector. Use the resulting baggage charges for the applicable business purpose (e.g. quote baggage charges OR apply baggage charges at check-in The bag is not permitted. Page 017 Revised August 2014

18 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Examples Charge for an Excess Bag (sub code ABC) Process Record S7 with the following: o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection) o Service Type C o Sub code ABC and o Occurrence = 1 Charge for 5 kilos excess Process Record S7 with the following: o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection) o Service Type C o 5 kilos excess and o Sub Code 0DG Charge for an Excess Bag (sub code ABC) and 5 kilos Excess Weight Process Record S7 with the following: o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection), Service Type C, Sub Code ABC and Occurrence 1, and o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection), Service Type C, 5 excess kilos and sub code 0DG. Charge for a Heavy Bag (sub code BCD) Process the S7 with the following: o All Data Requirements for processing the S7 (including the carrier and travel resulting from Baggage Selection) o Service Type C and o Sub Code BCD (Note: A Heavy Bag that does not resolve to a Baggage Allowance Record is not assigned an occurrence) Page 018 Revised August 2014

19 2.0 Definitions and Assumptions 2.1 Definitions Term BT (Baggage Travel) Canadian Transportation Agency (CTA) Carriers Checked Point/Throughchecked point Definition Travel resulting from Baggage Selection processing (see Attachment A Baggage Selection). Data within the BT is used to match against the match criteria contained within Record S7. Carriers who file general rules to/from Canada. ATPCO maintains a list of these carriers that subscribers use to determine the carrier whose rules apply on a journey to/from Canada. Refer to Appendix A of this document. A point where the bags are checked. Processing will determine all checked points during itinerary analysis prior to baggage processing. The system assumption is for systems to use the definition of a stopover as defined in IATA Resolution 012. Any exceptions specified within IATA Resolution 012 apply. Journeys wholly within the US/CA (or between the US and CA) are subject to the 4 hour rule. The journey destination is always a checked point. This definition applies to the system assumption of a checked point for this product; systems may bilaterally and/or manually override this assumption. A surface sector is always considered a checked point. Exception: A surface sector that occurs between airports within the same city (multi-airport city) is only considered a checked point when the surface sector meets the definition of a stopover as defined above. Page 019 Revised August 2014

20 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Term Checked Portion of Travel Destination DOT Carriers EMD Fare Owner Furthest Checked Point Definition The point where the bags are checked to a point at where they are picked up. The following high-level steps apply for determining the checked portions of travel for a journey: 1. Gather the full itinerary (including all ticketed points and the time between arrival and departure at each point) 2. Determine all checked points (see section 2.1 Definitions Checked Point). 3. The journey origin to the next checked point is a checked portion of travel. If applicable, identify any further checked portions from the next checked point to any future checked points, etc. A checked portion of travel may consist of one or multiple sectors on one or more operating/marketing carriers and can be covered by one or more fare components. There may be an occasion where a passenger is required to collect baggage in order to clear customs - even though the bag may be considered through checked to a further destination. In this situation, the ending point of the checked portion of travel would still be considered the destination point where the bags were considered to be through checked. I t is assumed that a passenger s bags cannot transit a point more than once on the same checked portion of travel. So, for example, FRA-LHR-MAN-LHR-JFK would be an invalid checked portion of travel (LHR is transited twice). Ultimate stopping place of the journey as shown on the ticket Carriers who file general rules to/from the US. ATPCO maintains a list of these carriers that subscribers use to determine the carrier whose rules apply on a journey to/from the US. Refer to Appendix A of this document. Electronic Miscellaneous Document. A one or many coupon electronic document that may be associated to a flight coupon, referenced to a ticket, or may be issued standalone, in order to document the sale and track usage of optional services and other miscellaneous fees. The carrier code on the Automated Rules Record 1 or Category 25 Record 2 associated to a fare component on the passenger s ticket. EXCEPTION: Unless otherwise specified, YY is not a valid fare owner for Baggage Services processing. Processing will use the resulting journey (during itinerary analysis prior to baggage processing) to determine the furthest checked point. The furthest checked point is the furthest point by mileage from the journey origin that meets the definition of a checked point. Processing should measure using the following steps: Page 020 Revised August 2014

21 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Term Definition Measure using the non-stop TPM (Ticketed Point Mileage) between the origin of the journey and the furthest checked point. o When a single TPM exists between the points being measured, use the TPM regardless of the global. o When multiple TPMs exist between the points being measured, apply Global direction in determining the correct TPM to use. o When more than one global direction applies to the points being measured, use the highest TPM that applies for one of the global directions. If there are no TPMs, calculate TPMs as MPM (Maximum Permitted Mileage) divided by 1.2 (MPM/1.2). o When a single MPM exists between the points being measured, use the MPM regardless of the global. o When multiple MPMs exist between the points being measured, apply Global direction in determining the correct MPM to use. o When more than one global direction applies to the points being measured, use the highest MPM that applies for one of the global directions. If MPMs do not exist, use GCM (Great Circle Mileage). If the furthest point occurs more than once on the journey, then processing will identify the first occurrence of the point as the furthest checked point. (see Example below) Example 1: Round the world circle trip: TYO-NYC-LON-TYO* *Mileage in examples used for illustrative purposes only and may not reflect real mileage Mileage required to determine furthest point: TYO-NYC and TYO-LON TYO-NYC(PA global direction) TYO-NYC = 6737 (only one TPM found) Page 021 Revised August 2014

22 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Term Definition Possible mileage results TYO-NYC: TPM: 6737(AT) - use this TPM regardless of global MPM/GCM: Do Not Check (found at least one TPM) TYO-LON(EH global direction) TYO-LON (multiple TPM s found) (AP) (EH) use this TPM as it matched the global Comparing Mileage Results The mileage should be measured looking for all possible TPMs (or MPM/1.2 or GCM), and use the highest mileage resulting from all calculations, in which case, the itinerary above would be resolved as follows: TYO-NYC 6737 (TPM) TYO-LON 6220 (TPM) NYC is the furthest checked point. Example 2 : Round the world circle trip: TYO-NYC-LON-TYO Mileage required to determine furthest point: TYO-NYC and TYO-LON TYO-NYC(PA global direction) TYO-NYC = 6737 (only one TPM found) Possible mileage results TYO-NYC: TPM: global MPM/GCM: TYO-LON (EH global direction) TYO-LON (no TPM s found; check MPM) Possible mileage results TYO-LON: TPM: 6737(AT) use this TPM regardless of Do Not Check (found at least one TPM) None found Page 022 Revised August 2014

23 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Term Definition MPM/1.2: MPM/1.2: global 9393 (AP) 7213 (EH) use this TPM as it matched the Comparing Mileage Results The mileage should be measured looking for all possible TPMs (or MPM/1.2 or GCM), and use the highest mileage resulting from all calculations, in which case, the itinerary above would be resolved as follows: TYO-NYC 6737 (TPM) TYO-LON 7213 (MPM/1.2) LON is the furthest checked point. Example 3 : Travel: IAD-FRA-CDG-FRA-IAD Stopovers in FRA (out), CDG, and FRA (in). Mileage required to determine furthest point: IAD-FRA and IAD-CDG FRA is the furthest point. Since FRA occurs twice as a checked point, processing selects the first occurrence of FRA as the furthest. Therefore, the two directions of travel are: IAD-FRA (outbound) FRA-CDG-FRA-IAD (inbound) When No Furthest Checked Point Exists: For international journeys in which the origin and destination are in the same country processing should define two checked portions. In the absence of a furthest stopover to identify the furthest checked point (meets the definition of a stopover), processing should apply the furthest ticketed point to create two checked portions. For example ZRH LHR ZRH. The time between arrival and departure in LHR is less than 24 hours. LHR will be defined as the furthest checked point. ZRH-LHR is outbound baggage travel, LHR-ZRH is inbound. For a journey in which the travel is wholly within one country and the origin and destination are the Page 023 Revised August 2014

24 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Term Definition same city, processing should define two checked portions. In the absence of a furthest stopover to identify the furthest checked point, systems should use the furthest ticketed point to create two checked portions. When the furthest checked point is a surface sector: Processing must verify both end points of the surface sector to determine the furthest distance. Example 1 JFK-DUS//TXL-GVA//ZRH-JFK Processing will check: JFK-DUS, JFK-TXL, JFK-GVA, JFK-ZRH and determine the furthest point. TPM JFK-DUS: 3743 JFK-TXL: 3969 JFK-GVA: 3859 JFK-ZRH: 3926 Result: TXL is the furthest point. Example 2 JFK-FRA//BOM-JFK Processing will check JFK-FRA, JFK-BOM and determine the furthest point. Result: BOM is the furthest point. Ground Transportation Ground transportation where there is a valid carrier code on the ticket (and other than the equipment code, it appears to be a flown sector) is treated as if it were a flown sector. Otherwise, ground transportation must be processed outside of ATPCO automation. Page 024 Revised August 2014

25 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Term Marketing Carrier Open Sectors Operating Carrier Portion of Travel Sector Service Type Code Surface Sector Validate Validating Carrier Definition The carrier code that will appear on the flight coupon of the ticket (different from operating carrier for code share). The Marketing Carrier may be a primary and/or secondary carrier. A sector where the flight and carrier information is not known. Processing will ignore any sectors where the carrier and flight information is not known (e.g. for a ticket NCE-PAR-MOW with an open return, in NCE processing would process the baggage allowance and charges for NCE-PAR-MOW and not for any assumed return to NCE). The carrier who owns the schedule record (SSIM file) unless that record contains a value in the DEI050 field which identifies the operating carrier of the segment. DEI050 is a data element found in a SSIM file (Standard Schedules and Information Manual). In order to use this product, carriers should file the operating carrier (and operating carrier flight number) in the DEI050 of the schedules record (as opposed to the DEI027). ATPCO will add this recommended practice to the reference manual for this product. If carriers do not file a value in DEI050, systems will assume the marketing carrier and flight number is the same as the operating carrier and flight number. Any travel consisting of a single sector or multiple sectors on any carrier. A portion of a journey covered by a single flight coupon. A code identifying the service for which a fee will be assessed. This code is made up of a generic ATPCO service code and a more specific sub-code to further define the service. A surface sector is a sector between two ticketed points where travel is via other than air transportation. A surface sector is always a checked point for the purposes of baggage processing. Exception: Surface sectors that meet both of the following criteria are not considered checked points: The surface sector occurs between airports in the same city (multi-airport cities); AND The surface sector is a connection (based on elapsed time per definition). Compare. When used in this document to describe how to process the data, the term validate means to compare. For example, validate the data against the sector being processed means to compare the data against the sector being processed The carrier whose ticket stock was used to issue the ticket (plating carrier). This carrier is commonly the holder of the money for the ticket Page 025 Revised August 2014

26 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) 2.2 Assumptions Processing must resolve to a Record S5 Sub Code Services Record for the Baggage Service being processed in order for the baggage to be automated via ATPCO data Embargoes No Data and No Match (Service Type E) If there is no Record S5 and/or S7 data for the resulting S5/S7 carrier or processing does not match a Record S5 and/or S7 applicable to the baggage being interrogated, then the assumption is that there is no embargo in effect for that carrier (embargoes are not applicable for the criteria being priced). Any bag that does not match applicable embargo data can be processed against baggage allowance and charges data. Example For the purposes of this example, assume the following Record S5 data exists: Carrier = XX Sub Code = 0GO Service Type = E (embargo) Group Code = BG (Baggage) Sub Group = Blank When attempting to match embargo data for carrier XX, assume processing matches the Record S5 above: If Record S7 data exists for carrier XX Sub Code 0GO with Service Type value E, but processing is unable to match a Record S7, then the assumption is that XX s 0GO embargo data is not applicable (no embargo applies for 0GO). This bag can be interrogated for baggage allowance and charges. Page 026 Revised August 2014

27 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Baggage Allowance for checked baggage No Data and No Match (Service Type A) The application is dependent upon whether the journey is to/from the US/Canada (subject to the US DOT reservation and/or the Canadian Transportation Agency Interpretation Note) or not (refer to Attachment A Baggage Selection) Journeys To/From US/CA Record S5 (Sub Code Services Record) The carrier whose rules apply must be a DOT carrier (must file tariffs to/from the US) for joureys to/from US and/or must be a Canadian Transportation Agency (CTA) carrier (must file tariffs to/from Canada) for journeys to/from Canada For journeys between the US and Canada, the carrier must be both a DOT carrier and and a CTA carrier. Processing first attempts to match Record S5 for sub code 0DF for the carrier whose rules apply (either the first marketing carrier or the MSC) as defined in Attachment A Baggage Selection. If the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the journey defers to the MSC (who is a valid DOT/CTA carrier for the journey ) (refer to Attachment A Baggage Selection): If there is no Record S5 data for the MSC or processing does not match a Record S5 for generic sub code 0DF for the MSC: Process Record S5 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey)) on the ticket If there is no Record S5 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey)) or processing does not match a Record S5 for generic sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey), then: At time of passenger ticketing, systems must put Blank on the ticket, At time of passenger fare quote, systems must indicate the baggage allowance is unknown, and At time of passenger check-in, processing will determine the baggage allowance and charges to apply outside of ATPCO automation. If the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the journey defers to the MSC, but the MSC is not a valid DOT/CTA carrier for the journey (refer to Attachment A Baggage Selection): Process Record S5 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the ticket Page 027 Revised August 2014

28 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) If there is no Record S5 0DF for the first marketing carrier (who is a DOT carrier) or processing does not match a Record S5 for generic sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey), then: At time of passenger ticketing, systems must put Blank on the ticket, At time of passenger fare quote, systems must indicate the baggage allowance is unknown, and At time of passenger check-in, processing will determine the baggage allowance and charges to apply outside of ATPCO automation. If the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the journey does not defer to the MSC (refer to Attachment A Baggage Selection): If there is no Record S5 data for the first marketing carrier (who is a valid DOT/CTA carrier for the journey) or processing does not match a Record S5 for generic sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey)at time of passenger ticketing, systems must put Blank on the ticket, At time of passenger fare quote, systems must indicate the baggage allowance is unknown, and At time of passenger check-in, processing will determine the baggage allowance and charges to apply outside of ATPCO automation. Page 028 Revised August 2014

29 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Record S7 (Provisions Record) Once a match is made to Record S5 for sub code 0DF (for the carrier whose rules apply and who is a valid DOT/CTA carrier for the journey), processing attempts to match Record S7. If the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the journey defers to the MSC (who is a valid DOT/CTA carrier for the journey) (refer to Attachment A Baggage Selection): If there is no Record S7 data for the MSC or processing does not match a Record S7 for generic sub code 0DF for the MSC: Re-start Baggage Allowance processing, but attempt to match data for the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the ticket Process Record S5 for generic sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey). If there is no Record S5 data or processing does not match a Record S5 for sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey), then refer to the Record S5 No Data No Match assumptions above. If processing matches Record S5, but there is no Record S7 data or processing does not match a Record S7 for sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey), then o The assumption is that there is no free checked baggage allowance. All checked baggage is subject to a charge. o Systems must put NO, NIL or XX: on the passenger ticket Note: These values are per IATA Resolution 722F. If the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the journey defers to the MSC, but the MSC is not a valid DOT/CTA carrier for the journey (refer to Attachment A Baggage Selection): Processing will have re-started Baggage Allowance processing, but attempted to match data for the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the ticket Process Record S5 for generic sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey)if there is no Record S5 data or processing does not match a Record S5 for sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey) then refer to the Record S5 No Data No Match assumptions above. If processing matches Record S5, but there is no Record S7 data or processing does not match a Record S7 for sub code 0DF for the first marketing carrier (who is a valid DOT/CTA carrier for the journey), then o The assumption is that there is no free checked baggage allowance. All checked baggage is subject to a charge. o Systems must put NO, NIL or XX: on the passenger ticket Page 029 Revised August 2014

30 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) Note: These values are per IATA Resolution 722F. If the first marketing carrier (who is a valid DOT/CTA carrier for the journey) on the journey does not defer to the MSC (refer to Attachment A Baggage Selection): If there is no Record S7 data for the first marketing carrier (who is a valid DOT/CTA carrier for the journey) or processing does not match a Record S7 for generic sub code 0DF for the first marketing carrier, then The assumption is that there is no free checked baggage allowance. All checked baggage is subject to a charge. Systems must put NO, NIL or XX: on the passenger ticket NOTE: These values are per IATA Resolution 722F. Example 1 Ticket: MOW-ZZ-CDG-BB-LHR-XX-YYZ-CC-SEA Scenario A: Scenario B: ZZ, BB, XX, and CC are DOT Carriers. Process the rules of the first marketing carrier who is a DOT carrier: ZZ. ZZ defers to the MSC (carrier XX). Process XX rules. When attempting to determine the baggage allowance for carrier XX, assume processing matches a Record S5 XX sub code 0DF: If Record S7 data exists for carrier XX Sub Code 0DF with Service type value A, but processing is unable to match a Record S7, then processing attempts to match Record S5 and S7 data for carrier ZZ If Record S7 data exists for other carrier XX Sub Codes within Group BG but does not exist for Sub Code 0DF with Service Type value A, then processing attempts to match Record S5 and S7 data for carrier ZZ. BB, XX, and CC are DOT Carriers. ZZ is not a DOT carrier. Process the rules of the first marketing carrier who is a DOT carrier: BB BB defers to the MSC (carrier XX). Process XX rules When attempting to determine the baggage allowance for carrier XX, assume processing matches a Record S5 XX sub code 0DF: If Record S7 data exists for carrier XX Sub Code 0DF with Service type value A, but processing is unable to match a Record S7, then processing attempts to match Record S5 and S7 data for carrier BB. Page 030 Revised August 2014

31 BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW Definitions and Assumptions (cont) If Record S7 data exists for other carrier XX Sub Codes within Group BG but does not exist for Sub Code 0DF with Service Type value A, then processing attempts to match Record S5 and S7 data for carrier BB. Scenario C: BB and CC are DOT Carriers. ZZ and XX are not DOT carriers. Process the rules of the first marketing carrier who is a DOT carrier: BB BB defers to the MSC (carrier XX). However, since XX is not a DOT carrier, processing must revert to BB s rules as the first marketing carrier who is a DOT carrier. Process BB s rules When attempting to determine the baggage allowance for carrier BB, assume processing matches the Record S5 for BB sub code 0DF: If Record S7 data exists for carrier BB Sub Code 0DF with Service type value A, but processing is unable to match a Record S7, then there is no free checked baggage allowance. If Record S7 data exists for other carrier BB Sub Codes within Group BG but does not exist for Sub Code 0DF with Service Type value A, then there is no free checked baggage allowance. Scenario D: ZZ, BB, XX, and CC are DOT Carriers. Process the rules of the first marketing carrier who is a DOT carrier: ZZ. ZZ does not defer to the MSC (carrier XX). Process ZZ rules. When attempting to determine the baggage allowance for carrier ZZ, assume processing matches a Record S5 ZZ sub code 0DF: If Record S7 data exists for carrier ZZ Sub Code 0DF with Service type value A, but processing is unable to match a Record S7, then there is no free checked baggage allowance. If Record S7 data exists for other carrier ZZ Sub Codes within Group BG but does not exist for Sub Code 0DF with Service Type value A, then there is no free checked baggage allowance. Page 031 Revised August 2014