DATA APPLICATION CATEGORY 25 FARE BY RULE

Size: px
Start display at page:

Download "DATA APPLICATION CATEGORY 25 FARE BY RULE"

Transcription

1 DATA APPLICATION CATEGORY 25 FARE BY RULE 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.

2 Contents 1.0 OVERVIEW Data Requirements Basic Processing Overview Passenger Itinerary Processing Rule Validation for Categories Other than Category DEFINITIONS AND ASSUMPTIONS Definitions Assumptions DETAILED FIELD PROCESSING Record Base Fare Information Table PROCESSING General Application Passenger Type Code (PTC) Stringing Logic General Rule Processing for a Fare by Rule Routing Validations RBD Validation Footnote Validation Use Of Add-Ons with Fare by Rules Text Table No. 996 and Unavailable Data Tag (Bytes And 348) Match to the Passenger Itinerary Passenger Type Code (PTC) (Bytes 14-16) Passenger Status Fields (Bytes 17-24) ID (Byte 25) Age (Bytes 26-27, 28-29) Passenger Occurrence (Bytes 30-32, 33-35) Travel Wholly Within (Bytes 36-41) Passenger Travel Origin (Bytes 43-50) Number Of Flight Segments (Bytes 57-58) Override Date Table No. 994 (Bytes )... 33

3 No Discount Indicator (Byte 59) Fare Calculation (Bytes ) Mileage Minimum/Maximum (Bytes 60-69) Fare Calculation Indicator (Byte 70) Percent (Bytes 71-77) Fare 1/Fare 2 (Bytes ) Fare Calculation with Constructed Base Fares (Byte 104) Fare Comparison (Bytes ) Fare Range 1/Fare Range 2 (Bytes ) Rules Tariff (Bytes ) Carrier (Bytes ) Fare Class (Bytes ) Fare Type (Bytes ) Multiple Comparison Fares Examples Same Tariff/Rule (Byte 180) Resulting Fare (Bytes ) OW/RT (Byte 191) Global Indicator (Bytes ) Routing Tariff (Bytes ) Routing Number (Bytes ) Fare Class (Bytes ) Fare Type, Season, Day of Week (Bytes ) Display Category (Byte 220) Pricing Category (Byte 221) Prime RBD and RBD Table 999 (Bytes , ) Prime Sector (Byte 246) RBD Validation Base Fare Chart 1 (Byte 247) Ticketing Code and Ticketing Code Modifier (Bytes , 262) Category Override Tags (Bytes ) Restrictions on Category Override Tags Application of Rule Conditions Category 10 Combinability

4 4.7.4 Category 12 Surcharges Per Ticket and Per Direction Category 12 Surcharges Percent Calculation Category 13 Accompanied Travel Category 15 Sales Restrictions Category 17 HIP/Mileage Exceptions Other Category Examples Base Fare Table Sequence Number (Bytes 14-20) Application Indicator (Byte 21) OW/RT (Byte 22) Global Indicator (Bytes 23-24) Carrier Code (Bytes 25-27) Published/Calculated Indicator (Byte 28) Rule Tariff (Bytes 29-31) Rule Number (Bytes 32-35) Fare Class Code (Bytes 36 43) Fare Type Code (Bytes 44-46) Passenger Type Code (Bytes 47-49) Season (Byte 50) Day of Week (Byte 51) Pricing Category (Byte 52) Routing Number (Bytes 53-57) Footnote (Bytes 58-60) Prime RBD (Bytes 61-64) Between And City (Bytes 72-81) Range 1/Range 2 (Bytes ) Highest Indicator (Byte 323) Rule Validation And Fare Selection Process 1 Specified Fares No Base Fare Table Process 2 Calculated Fares Base Fare Table Currency Application TRAVEL SEGMENT INDICATOR (TSI) CODING CONVENTIONS

5 6.1 Match to the Passenger Itinerary Fare Comparison Base Fare Table RBD Processing FARE CONSTRUCTION Maximum Permitted Mileage (MPM) Higher Intermediate Point (HIP) PFC ABSORPTION / FLIGHT SEGMENT TAX ABSORPTION

6 1.0 OVERVIEW Fare by Rule is the creation of fare records using Automated Rules. There are two types of Fare by Rules supported in the Automated Rules Product: Type A and Type B. Type A utilizes data in Discount Categories to create fares, and exists without the use of Category 25. Processing starts with a Base Fare record and follows the existing data application flow for Automated Rules. Discount Categories are used to modify the base fare selected as the starting point for normal processing. Type B utilizes data in Fare by Rule Category 25 to create fares. All references in this document to Fare by Rules are confined to Type B, Category 25 processing. Fare by Rule fares are created using Category 25. Unlike published fare processing, fare records and Record 1s (Fare Class Application) do not exist for Fare by Rule fares. Instead, Record 8 (Fare by Rule Application) serves as the starting point for pricing. Processing uses the passenger s information at the time of pricing to match and retrieve all applicable Record 8s. Once matched, passenger and Record 8 data are used to match the Category 25 Record 2. Category 25 Record 2 points to the applicable Category 25 Record 3 data which contains the information necessary to create the fare. Category 25 supports the creation of the following types of Fare by Rules: Specified Fare amount is a specified amount. Data is self contained within the Category 25 Record 3. Calculated Fare amount is calculated off a base fare. Base Fare Information Table 989 is referenced in Category 25. The Category 25 Record 3 data can be separated into the following subsections based on the purpose of the data: Match Information to the Passenger Itinerary Data Fare Calculation Information Fare Comparison Information Resulting Fare Information Category Override Information Base Fare Table 989 Section 4.0 of this document provides detailed explanation and examples for all fields contained within each of these subsections. Fare by Rule data exists in specific ATPCO Fare by Rule tariffs, separate from all other ATPCO tariffs. The Fare by Rule tariffs exclusively support the Fare by Rule Category 25 processing. These tariffs represent a larger grouping of geographic data than the Page E

7 fare and rule tariffs that exist for published fares. They are not based strictly on geographic global codes but represent the three types of Rules Subscription Products offered by ATPCO: US/CA Domestic, International, and AllFares. Some hold public information, which is separated into DOJ-restricted and non-doj restricted, and some hold private information. The purpose of this document is to describe the pricing of a passenger s itinerary. This document does not address other possible access to the data, such as fare display or database management, unless specifically stated. The following records also support Fare By Rule processing using Category 25. Record 8 Fare by Rule Table 978 User Created Zones Record 2 Fare by Rule Category 25 Refer to data application documentation for each of these records for further explanation of how they apply to Fare by Rule processing. 1.1 Data Requirements In order to validate Category 25, it is essential to know the following: Passenger itinerary information Primary passenger type Any associated secondary passenger types Passenger status Geographic scope of the fare being created Passenger travel origin When the base fares retrieved are constructed fares, the amount and currency of the specified fare and add-on(s), prior to any conversions. Page E

8 1.2 Basic Processing Overview DATA APPLICATION FOR CATEGORY 25 FARE BY RULE Passenger Itinerary Processing Starting with the passenger s itinerary, processing attempts to match a Record 8 for a fare component. Record 8 is then matched to Record 2 for Category 25 which contains the applicable Record 3 data table string. Passenger Itinerary being priced Fare Component Creation - match an applicable Record 8 as described in Data Application for Record 8 Match an applicable Record 2 for Category 25 as described in Category 25 Record 2 Data Application Is there an applicable Category 25 Record 3 based on: Passenger Type Code (PTC) (bytes 14-16) Passenger Status Information (bytes 17-24) Passenger Minimum/Maximum Age (bytes 26-29) Passenger Occurrence (bytes 30-35) Passenger Travel - Wholly Within (bytes 36-41) Passenger Travel - Origin (bytes 43-50) Number of Flight Segments (bytes 57-58) Mileage of the Fare Component (bytes 60-69) Override Date Table No. 994 (bytes ) No Yes Apply the system assumption - fare by rule does not exist for the passenger itinerary being priced Create the Fare by Rule according to the following Category 25 data: Fare Calculation Information Fare Comparison Information Resulting Fare Information Category Override Information Page E

9 1.2.2 Rule Validation for Categories Other than Category 25 Category 25 supports the creation of two different types of Fare by Rules. A different processing path for rule validation is needed for each type. The following are the Fare by Rule types and the associated processing path number. Fare by Rule Type Description Fare Selection and Rule Validation Process Number Specified Fare amount is a specified amount. Data is self Process Type 1 contained within the Category 25 Record 3. Calculated Fare amount is calculated off a base fare. Base Fare Information Table 989 is referenced in Category 25. Process Type 2 To validate other rule categories within the Fare by Rule, the resulting fare information within Category 25 Record 3 must be obtained and used to match to Record 2 s for Fare by Rule Fare Rule and General Rule categories (categories other than 25). NOTE: Refer to Category Override Section in this document for details on processing of Base Fare category data and Fare by Rule category data when a Base Fare (Table 989) is used to create a Fare by Rule. The rule validation flow for both a Specified Type and Calculated Type of Fare by Rule is shown on the following page. Page E

10 Rule Validation for Categories other than Category 25 Record 3 Category 25 Process Type 1 Process Type 2 Specified (Base Fare Table 989 is not present) Specified Is the Fare by Rule Specified or Calculated? Calculated Calculated (Base Fare Table 989 is present) FBR Record 0 For each Category (other than Category 25) determine if FBR, Base Fare, or Both apply based on Category 25 bytes FBR General Rule Record 2 Alt Gen FBR Fare Rule Record 2 (categories other than 25) FBR Record 0 Base Fare Fare Record Record 3 Resulting FBR rule data FBR General Rule Record 2 Alt Gen FBR Fare Rule Record 2 (categories other than 25) Base Fare Record 0 Base Fare Record 1 Record 3 Resulting FBR rule data Base Fare General Rule Record 2 Alt Gen Base Fare Fare Rule Record 2 Base Fare Footnote Record 2 (ALWAYS validated) Record 3 Resulting Base Fare rule/footnote data Page E

11 2.0 DEFINITIONS AND ASSUMPTIONS 2.1 Definitions Base Fare NSSM Primary Sector(s) Resulting Fare Secondary Sector TPM The fare from which a discount will be calculated to determine the resulting discounted fare. Non-stop sector Miles. The significant (primary) portion of travel within a given fare component. This is the portion of travel of a fare component that determines the carrier s fare that will be selected in accordance with standards set forth in IATA Resolutions for the entire fare component (also know as primary portion of travel). Refer to the Glossary of Terms definition of Primary Portion of Travel. The fare that results after a discount is calculated from a base fare or a specified amount is applied. Any flight portion that is not primary within a given fare component. Ticketed point Mileage (TPM) is the distance between pairs of points published in the TPM Manual using non-stop sector mileages. 2.2 Assumptions In the absence of a matched Category 25 Record 2 or Record 3, no Fare by Rule exists for the passenger and/or fare component being priced. All fare amounts created/specified by Category 25 are pre-tax amounts. Page E

12 3.0 DETAILED FIELD PROCESSING 3.1 Record 3 Byte Location Match / Action Definition / Processing RECORD TYPE Key Match Indicates the Record number for which the data is formatted. Byte 1 ACTION Byte 2 Key Match Indicates the type of processing when loading the data either new data (add to the database) or deleted data (purge from the database). CAT NO Byte 3-4 Key Match Indicates rule or category to which the data applies. For Fare by Rule Category, it will always be 25. TABLE NO Byte 5-7 Key Match Indicate a number that links the Category 25 Record 3 to the associated Category Control Records (Record 2). PASSENGER TYPE Byte Match Identifies the passenger type for which the data table is applicable. Matches to the Record 8 Primary PTC. PASSENGER STATUS Byte APPLICATION Byte 17 Action Indicates the positive or negative application of the following fields for the specified passenger type in byte PASSENGER TYPE Byte 18 Match Identifies the passenger status based on nationality, residency, ship registry, or employee. LOC Byte Match Indicates geographic location applicable for the specified passenger type in Bytes PASSENGER ID Action Indicates that identification of status is required at ticketing. Byte 25 MIN PASSENGER AGE Byte Match Indicates the specified age requirments that further define the passenger type in Bytes MAX PASSENGER AGE Byte Match Indicate the specified age requirments that further define the passenger type in Bytes PSGR OCCURRENCE FIRST Byte Match Indicates the first occurrence of the specified passenger type in Bytes (e.g. second through fourth passenger) for which the table applies. Page E

13 Byte Location Match / Action Definition / Processing PSGR OCCURRENCE LAST Byte Match Indicates the last occurrence of the specified passenger type in byte (e.g. second through fourth passenger) for which the table applies. TRAVEL WHOLLY WITHIN Byte Match Indicates all ticketed points on the fare component must be wholly within a specified location. RESERVED Byte 42 PASSENGER TRAVEL ORIGIN Match Indicates the origin of the journey must be at a specified location. Byte NUMBER OF FLIGHT SEGMENTS Byte Match Indicates the maximum number of flight segments (coupons) per fare component allowed by the matched Fare by Rule. NO DISCOUNT Byte 59 FARE CALCULATION MINIMUM MILEAGE Byte MAXIMUM MILEAGE Byte FARE CALCULATION FORMULA INDICATOR Byte 70 PERCENT Bytes SPECIFIED FARE NO. 1 Bytes CURRENCY 1 Bytes DECIMAL Byte 90 SPECIFIED FARE NO. 2 Bytes Action Match Match Action Action Indicates that no discount applies for the specified passenger/itinerary that matches the table. Indicates the minimum mileage of the fare component required to match the Record 3 data. Indicates the maximum mileage of the fare component required to match the Record 3 data. Indicates whether the fare is to be calculated, specified or computed using both calculated and specified amounts. Indicates the percentage to be applied to the base fare. Action Indicates a specified fare amount to be charged or added/subtracted to/from the resulting calculated fare. Action Currency code of the fare amount in bytes Action Action Decimal placement for the currency. Indicates a specified fare amount to be charged or added/subtracted to/from the resulting calculated fare. Used for a secondary currency only. Page E

14 Byte Location Match / Action Definition / Processing CURRENCY 2 Bytes Action Currency code of the fare amount in bytes Used for a secondary currency only. DECIMAL Action Decimal placement for the currency. Used for a secondary currency only. Byte 103 FARE CALCULATION WITH CONSTRUCTED BASE FARES 1 Byte 104 Action Indicates the portion of a constructed base fare that is subject to the percentage calculation. Calculation can be applied to whole constructed base fare or just the specified fare portion of the constructed base fare. RESERVED Bytes FARE COMPARISION FARE RANGE 1 MIN FARE Bytes FARE RANGE 1 MAX FARE Bytes FARE RANGE 2 MIN FARE Bytes FARE RANGE 2 MAX FARE Bytes RULES TARIFF NUMBER Bytes CARRIER CODE Bytes FARE CLASS Bytes Action Action Action Action Action Action Action Indicates the minimum fare amount to be used by itself or in establishing a range of amounts for a fare comparison to the Fare by Rule amount being created. Indicates the maximum fare amount to be used by itself or in establishing a range of amounts for a fare comparison to the Fare by Rule amount being created. Indicates the minimum fare amount to be used by itself or in establishing a range of amounts for a fare comparison to the Fare by Rule amount being created. Used for a secondary currency only. Indicates the maximum fare amount to be used by itself or in establishing a range of amounts for a fare comparison to the Fare by Rule amount being created. Used for a secondary currency only. Indicates the rules tariff used to find the associated fares tariff to be used to match fares used for comparison processing. Indicates the carrier used to match fares used for comparison processing. Indicates the fare class code or fare family used to match fares used for comparison processing. 1 Pending full industry adoption. Page E

15 Byte Location Match / Action Definition / Processing FARE TYPE Bytes Action Indicates the fare type code used to match fares used for comparison processing. SAME TARIFF/RULE Action Indicates fare combination restrictions for the fare by rule. Byte 180 RESERVED Bytes RESULTING FARE INFORMATION OW/RT Byte 191 Action Indicates the one-way/round-trip indicator to be applied to the resulting fare created in the Fare by Rule process. (Tag 1, 2, or 3) GLOBAL Byte Action Indicates the global indicator to be applied to the resulting fare created in the Fare by Rule process. ROUTING TARIFF Bytes Action Indicates the routing tariff to be applied to the resulting fare created in the Fare by Rule process. ROUTING NUMBER Bytes Action Indicates the routing number to be applied to the resulting fare created in the Fare by Rule process. RESERVED Bytes FARE CLASS Bytes Action Indicates the fare class code of the resulting fare created in the Fare by Rule process. FARE TYPE Bytes Action Indicates the fare type code of the resulting fare created in the Fare by Rule process. SEASON TYPE Byte 218 Action Indicates the season type code of the resulting fare created in the Fare by Rule process. DAY CATEGORY Byte219 Action Indicates the day of the week type code of the resulting fare created in the Fare by Rule process. DISPLAY CATEGORY Byte 220 Action Indicates the display category type of the resulting fare created in the Fare by Rule process. PRICING CATEGORY Byte 221 Action Indicates the pricing category type of the resulting fare created in the Fare by Rule Process. Page E

16 Byte Location Match / Action Definition / Processing PRIME RBD Bytes Action Indicates the Prime RBDs of the resulting fare created in the Fare by Rule process. RBD TABLE 999 Bytes Action Indicates the RBD exception data of the resulting fare created in the Fare by Rule process. PRIME SECTOR Action Indicates use of the prime RBD for primary or secondary online sectors. Byte 246 RBD VALIDATION BASE FARE Action Indicates use of the base fare Record 6 Chart 1 for RBD validation. CHART 1 Byte 247 RESERVED Bytes TICKETING CODE Bytes Action Indicates the ticketing code to be used on the ticket instead of the resulting fare class (may or may not be reflected on the fare display). TICKETING CODE MODIFIER Byte 262 Action Indicates the maximum stay, minimum group size, or percentage of discount to be appended to the ticketing code or resulting fare class. TICKET DESIGNATOR Bytes Action Indicates the ticket designator to be appended to the resulting fare class preceded by /. TICKET DESIGNATOR MODIFIER TAG Byte 273 Action Indicate that the maximum stay, minimum group size or percentage of discount to be appended to the end of the ticket designator or resulting fare class preceded by /. CATEGORY OVERRIDE TAGS CATEGORY 1-50 (Except 25) OVERRIDE TAGS Byte HIGHEST TAG Byte 323 OVERRIDE DATE TABLE Byte Action Action Match Indicates whether the Fare by Rule and/or Base Fare categories apply to the Fare by Rule being created. Indicates the order of applying Resulting Fares after all calculations and validation criteria have been met. Refers to a number that defines reservation, ticketing, and/or travel dates to which the discount applies. The Override Date Table data must match the reservation, ticketing, and/or travel dates of the pricing solution for the discount to be applied. Page E

17 Byte Location Match / Action Definition / Processing TEXT TABLE Byte Action Refers to a table containing free-form text regarding Category 25. The information within this table is not autopriced data. BASE FARE TABLE Action Refers to a 989 table containing Base Fare information. Byte UNAVAILABLE DATA TAG Byte 348 Action Indicator that this fare cannot be used for autopricing or that this Record 3 contains only free-form text. Page E

18 3.2 Base Fare Information Table 989 Byte Location Match / Action Definition / Processing RECORD TYPE Key Match Indicates the Record number for which the data is formatted. Byte 1 ACTION Byte 2 Key Match Indicates the type of processing when loading the data either new data (add to the database) or deleted data (purge from the database). TABLE ID Key Match Indicates the table type, always 989 for Base Fare Table. Byte 3-5 TABLE NUMBER Key Match Indicates the table number of the 989 Base Fare Table. Byte 6-13 SEQUENCE NUMBER Byte Action Indicates the processing order to be applied to multiple entries within a single 989 table. BASE FARE INFORMATION APPLICABLE TAG Byte 21 Action Indicates whether to apply the matched data within this sequence as possible base fare(s). OW/RT Byte 22 Action Indicates the one-way/round-trip indicator of the fare class code in the Base Fare retrieval process. GLOBAL Action Indicates the global indicator to use in the Base Fare retrieval process. Byte CARRIER CODE Action Indicates the carrier code to use in the Base Fare retrieval process. Byte PUBLIC CALCULATION TAG Byte 28 Action Indicates that fares already discounted through Category processing should be retrieved and used in the Base Fare retrieval process. RULES TARIFF NUMBER Action Indicates the rule tariff number to use in the Base Fare retrieval process. Byte RULE NUMBER Action Indicates the rule number to use in the Base Fare retrieval process. Byte FARE CLASS Byte Action Indicates the fare class code or fare family to use in the Base Fare retrieval process. FARE TYPE CODE Byte Action Indicates the fare type code to use in the Base Fare retrieval process. Page E

19 3.2 Base Fare Information Table 989 (cont.) Byte Location Match / Action Definition / Processing PASSENGER TYPE CODE Action Indicates the passenger type code to use in the Base Fare retrieval process. Bytes SEASON CODE Action Indicates the season code to use in the Base Fare retrieval process. Byte 50 DAY CODE Action Indicates the day of the week code to use in the Base Fare retrieval process. Byte 51 PRICING CATEGORY CODE Action Indicates the pricing category code to use in the Base Fare retrieval process. Byte 52 ROUTING NUMBER Action Indicates the routing number to use in the Base Fare retrieval process. Bytes FOOTNOTE Action Indicates the footnote(s) to use in the Base Fare retrieval process. Bytes RBD 1 Action Indicates the Prime RBD to use in the Base Fare retrieval process. Bytes RBD 2 Action Indicates the Prime RBD to use in the Base Fare retrieval process. Bytes RESERVED Bytes BETWEEN CITY1 Action Indicates the Origin/Destination fields to be used in the Base Fare retrieval Bytes process if different from the passenger itinerary used to match to Record 8. AND CITY2 Action Indicates the Origin/Destination fields to be used in the Base Fare retrieval Byte process if different from the passenger itinerary used to match to Record 8. FARE RANGE 1 Action Indicates the minimum fare amount to be used in the Base Fare retrieval MIN FARE process (as a stand-alone or in establishing a fare range). Byte FARE RANGE 1 MAX FARE Byte CURRENCY CODE Byte Action Action Indicates the maximum fare amount to be used in the Base Fare retrieval process (as a stand-alone or in establishing a fare range). Indicates the currency code for the Min/Max fare amounts in the previous fields to be used in the Base Fare retrieval process. Page E

20 3.2 Base Fare Information Table 989 (cont.) Byte Location Match / Action Definition / Processing DECIMAL Action Indicates the decimal placement of the currency code for the fare amounts to Byte 103 be used in the Base Fare retrieval process. FARE RANGE 2 Action Indicates the minimum fare amount to be used in the Base Fare retrieval MIN FARE process (as a stand-alone or in establishing a fare range). Used for a Byte secondary currency only. FARE RANGE 2 MAX FARE Byte CURRENCY CODE Byte DECIMAL Byte 125 Action Action Action Indicates the maximum fare amount to be used in the Base Fare retrieval process (as a stand-alone or in establishing a fare range). Used for a secondary currency only. Indicates the currency code for the Min/Max fare amounts in the previous fields to be used in the Base Fare retrieval process. Used for a secondary currency only. Indicates the decimal placement of the currency code for the fare amounts to be used in the Base Fare retrieval process. Used for a secondary currency only. Page E

21 4.0 PROCESSING Prior to processing Category 25, a Record 2 for Category 25 must be matched in order to determine the correct provisions for the fare being created (refer to the data application document for Category 25 Record 2). After a match is made to Record 2, processing attempts to match Category 25 Record 3 based on the following fields: Passenger Type Code (PTC) (Bytes 14-16) Passenger Status Information (bytes 17-25) Passenger Minimum/Maximum Age (bytes 26-29) Passenger Occurrence (bytes 30-35) Travel Wholly Within (Bytes 36-41) Passenger Travel Origin (Bytes 43-50) Number of Flight Segments (bytes 57-58) Mileage of the Fare Component (Bytes 60-69) Override Date Table No. 994 (Bytes ) If processing cannot match all of the above fields, then no match the Record 3 and continue processing to the next table. Once a match is made to a Record 3 based on the above fields, the following steps apply: 1. Process the data according to one of the following paths: a) Stop processing when No Discount (Byte 59) is value X. Do not continue processing to another Record 3 table within the string. b) Create the fare based on the Fare Calculation fields (Bytes ) as follows: i) Create a Specified Fare by Rule (Process Type 1). All data for creating the fare is contained with the Category 25 Record 3. Continue to Step 2. ii) Create a Calculated Fare by Rule (Process Type 2) through the retrieval of base fares. Processing must validate Base Fare Table No. 989 (bytes ) to determine which base fares to retrieve. Table 989 provides selection information such as tariff, carrier, and fare class information. Base Fare processing must include Footnotes and Effective/Discontinue Dates. Continue to Step Perform any Fare Comparison checks (bytes ) against the Resulting Fare created by Step 1. Page E

22 3. Validate rule conditions (for all categories except Category 10). Matching the Base Fare rule category data, for any category, is based on data contained in the Base Fare Records 0, 1, and 2. Matching Fare by Rule category data, for any category, is based on the data in the Category 25 Resulting Fare fields (Bytes ). a) For Specified Fare by Rules, rule validation applies the Fare by Rule Fare Rule and General Rule category data. b) For Calculated Fare by Rules, rule validation may apply Fare Rule and General Rule data from the Base Fare or Fare by Rule, both Base Fare and Fare by Rule, or only some/all categories of the Base Fare and some/all categories of the Fare by Rule, depending on the Category Override Tags (Byte ). 4. Validate Routing data in the Resulting Fare fields (bytes ). 5. Validate RBD data. a) For Specified Fare by Rules, RBD data will be found in the Resulting Fare fields (Bytes , ) and/or in Record 6 Convention 1. b) For Calculated Fare by rules, RBD data will be found in the Resulting Fare fields (Bytes , ), Base Fare Record 1, Base Fare Record 6 Convention 2, and/or Record 6 Convention 1. Refer to later sections in this document or to the RBD Data Application Overview for a detailed explanation of RBD processing for Category If processing passes validation of all of the above criteria, then the fare is a valid Resulting Fare for the Fare by Rule. If processing does not pass validation of all of the above criteria, then the fare is not a valid Resulting Fare for the Fare by Rule. 7. Validate Category 10 data. If the Resulting Fare passes Category 10 validation, then the fare is valid for use in the pricing solution. If the Resulting fare fails Category 10 validation, then fail the pricing solution. Refer to the value in the Highest field Byte 323 (as detailed later in this document) to determine if multiple possible resulting fares can result from a single Category 25 Record 3. NOTE: The above processing steps are for illustrative purposes only and do not reflect how or in what order a subscriber must process the data. The following pages detail the processing for all of the fields in Category 25. Data is organized according to the sections below: 4.1 General Application 4.6 Resulting Fare 4.2 Match to the Passenger Itinerary 4.7 Category Override 4.3 Fare Calculation 4.8 Base Fare Table Fare Comparison 4.9 Highest Indicator 4.5 Same Tariff/Rule 4.10 Rule Validation and Fare Selection Page E

23 4.1 General Application This section describes general processing guidelines. A detailed explanation of each field in Category 25 is found in the following sections Passenger Type Code (PTC) Record 8 provides a Primary PTC (Record 8 bytes 15-17) and a Secondary PTC (Record 8 bytes ). The Record 8 Primary PTC is used to match the Category 25 Record 3 PTC (Bytes 14-16). The Record 8 Secondary PTC specifies a passenger type that may be eligible for a further discount via Categories If the passenger on the itinerary being priced matches the Record 8 Secondary PTC, processing will use the Record 8 Primary PTC as match criteria for Category 25 Record 3. A fare amount and resulting fare information will be determined based on Category 25. To determine if a further discount applies for the Secondary PTC, processing will attempt to match the Secondary PTC to the PTC in Discount Categories 19-22, and the fare amount and resulting fare information determined by the Category 25 processing will be used to validate Categories Refer to Record 8 Data Application for further information Stringing Logic Fare by Rule string processing differs from other categories in the Automated Rules Product as follows: Record 3 for Category 25 can only be used as a main category. This Category can never be used as an IF condition, nor can it be used with AND or OR in the IF portion of a set. Edits prevent AND tables for Category 25. When processing matches a Record 3 with No Discount (Byte 59) value X, a fare by rule cannot be created according to the table. Processing will not continue to another Record 3. When processing matches a Record 3, processing will create the fare(s) according to the table, and processing will continue to another table (including OR tables) attempting to match and create another fare (unless Byte 59 is value X). When processing matches the IF portion of a set, processing will attempt to match and apply the THEN portion. Processing will continue to another set attempting to match and create another fare (unless Byte 59 is value X). Refer to Category 25 Record 2 Data Application for detailed explanation and examples of string processing. Page E

24 4.1.3 General Rule Processing for a Fare by Rule General Rules processing for Fare by Rule tariffs is consistent with other Fare Rules, except that General Rules are not permitted for Category 25. Record 2 for Category 25 (See Record 2 Data Application Document) does not contain fields to reference an alternate general rule (ALT GEN). Record 0 is permitted for Fare by Rule tariffs and can reference any Category other than Categories 10, 25, 31, 33, and 35. For a specified Fare by Rule (Process 1) the general rule information is only contained within the Fare by Rule. For a Calculated Fare by Rule (Process 2), General Rule information may be contained within the Base Fare, the Fare by Rule, or both. The presence or absence of data in the Category 25 Record 3 Category Override Tags (Byte ) will determine the type of rule validation process needed (see Category Override Section below). Example Rule Category Category Override Tag (byte 275) Value Base Fare General Rule Validation? FBR Rule General Rule Validation? Comments 2 Blank Yes Yes Both Base and FBR apply 2 X No Yes Only FBR applies 2 B Yes No Only Base Fare applies Note: Processing must still apply fare rule data and adhere to the combined rule application discussed in the Category Override Section below and in Record 2 Data Application Routing Validations A fare created from a Fare by Rule can have an associated Routing Number, just as a normal Fare Record. The Routing Number may indicate that the applicable routing is a specific Routing Number, Maximum Permitted Mileage (MPM), or any specified routing and/or MPM. The absence of routing data in the Category 25 Resulting Fare section (bytes ) means the Routing Number and Tariff of the Base Fare applies. The Routing (either from the Resulting Fare section or the Base Fare) must be validated against the passenger s itinerary. The Category 25 Routing Number in the Resulting Fare fields (Bytes ) has an associated Routing Tariff (Bytes ). The Routing Tariff may be a Fare by Rule routing tariff or a published fare routing tariff. Fare by Rule routings are only available in the Full Map Routing format. These routings are held in separate Routings Tariffs from those contained in current published fare Page E

25 4.1 General Application (cont) routings. For example, the US/CA Domestic Fares Tariff has two routings tariffs: one governing published fare routings and the other for Fare by Rule routings. Since Fare Records do not exist for Fare by Rules, a Market Routings product for US/CA Domestic Fare by Rules does not exist RBD Validation RBD data is not validated until a Resulting Fare has been identified and all fare and general rule information has been verified. Fare by Rule RBD processing detailed in this document applies to public, private, and third party tariffs. For Specified Fare by Rules, edits require RBD data in the Category 25 Resulting Fare Section (Bytes , ) to provide the RBD data for all Specified Fare by Rules Exception: Resulting Fare RBD data is not applicable for YY Category 25 data. Edits prohibit YY RBD data. For Calculated Fare by Rules, RBD data can be coded in the Category 25 Resulting Fare Section (Bytes , ). Data may be applied from the Resulting Fare Section, from the Base Fare, or from a combination of both. RBD data may be present in the following locations: Category 25 Resulting Fare Table 999 (Bytes ) Category 25 Resulting Fare Prime RBD (Bytes ) Base Fare Record 1 Prime RBD (bytes ) Base Fare Record 1 Table 999 (bytes ) Base Fare Record 6 Convention 2 Table 999 Record 6 Convention 1 Table 999 Refer to Section 4.6 Resulting Fare in this document, RBD Data Application Overview, Record 6 Data Application, Table 999 Data Application, and Record 1 Data Application documents for further explanation of RBD processing Footnote Validation Footnote data does not exist within the Fare by Rule Tariffs; therefore, footnote validation does not apply for Specified Fare by Rules (Process 1). Footnotes are only validated for Calculated Fare by Rules (Process 2). When retrieving a base fare to be used for Fare by Rule validation, all applicable footnotes of the base fare must be validated. This validation must occur regardless of any value in the Page E

26 4.1 General Application (cont) Category Override Tags (Category 25 Byte ). Footnotes, as well as Effective and Discontinue dates of the Base Fare, must be checked prior to any other rule validation. If processing passes the footnote validation of the base fare, then the base fare may be used for Fare by Rule validation (provided all other Table 989 conditions are met and Base Fare categories validate according to Category Override Tags). If processing cannot pass the footnote validation of the base fare, then the fare cannot be used for Fare by Rule creation Use Of Add-Ons with Fare by Rules The use of a Fare by Rule with Add-ons to create constructed fares is not allowed. No Add-on tariffs exist for Fare by Rules. The use of constructed fares in the Base Fare retrieval process through the Table 989 does apply (constructed fares may be used as a base fare). In order to support constructed Base Fare Retrieval, dynamic fare and add-on construction may be needed Text Table No. 996 and Unavailable Data Tag (Bytes And 348) 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. Example 1 (Value X) Record 3 THEN Bytes 14- Byte F Ind PTC Bytes Amount #1 Bytes Currency #1 Byte 191 OW/RT Bytes Text Tbl No. 996 SRC S CAD X Processing will fail the table as a result of the presence of value X in Byte 348. Byte 348 Unavail Data Tag Page E

27 4.1 General Application (cont) Example 2 (Value X) Record 3 THEN Bytes 14- Byte F Ind PTC Bytes Amount #1 Bytes Currency #1 Byte 191 OW/RT Bytes Text Tbl No. 996 SRC S CAD X Record 3 OR Bytes PTC Byte 70 F Ind Bytes Amount #1 Bytes Currency #1 Byte 191 OW/RT Bytes Text Tbl No. 996 Byte 348 Unavail Data Tag Byte 348 Unavail Data Tag SRC S CAD BLANK For the first table, processing will fail the table as a result of the presence of value X in Byte 348; processing will read on to the next table. The data in the second table indicates that the SRC passenger will be charged CAD. Page E

28 4.2 Match to the Passenger Itinerary This section describes the application of the match fields and the No Discount field. Category 25 Record 3 consists of the following match fields: Passenger Type Code (PTC) (Bytes 14-16) Passenger Status Information (bytes 17-24) Passenger Minimum/Maximum Age (bytes 26-27) Passenger Occurrence (bytes 30-35) Travel Wholly Within (Bytes 36-41) Passenger Travel Origin (Bytes 43-50) Number of Flight Segments (Bytes 57-58) Mileage of the Fare Component (Bytes 60-69) * Override Date Table No. 994 (Bytes ) Once a match is made to these fields, processing will interrogate No Discount Byte 59 to determine if a discounted fare is permitted. * Explanation and examples for Mileage of the Fare Component fields (Bytes 60-69) are found in Section 4.3 of this document Passenger Type Code (PTC) (Bytes 14-16) The Passenger Type Code (PTC) identifies the passenger eligible for the fare being created. This is a required field, that may standalone or be coded with any/all fields in bytes Data in PTC Bytes is an exact match to the Primary PTC in Record 8 bytes The PTC Hierarchy does not apply. If the PTC in Category 25 matches the Primary PTC in Record 8, processing will create the fare according to the data in the Category 25 table (provided a match is also made to all other Category 25 match fields). If the PTC in Category 25 does not match the Primary PTC in Record 8, processing will no match the Category 25 table. The PTC specified in Category 25 Bytes is still the resulting PTC applicable to the fare, regardless of the PTC applicable to the Base Fare. ATPCO s Coding Conventions hold that a PTC of ADT should only be used in private tariffs. NOTE: ATPCO is considering an edit restricting the use of ADT to private tariffs only. Currently, this is controlled at the Record 8 level. Example Record 8 Category 25 Result Primary PTC Secondary PTC PTC (Bytes ) 1. SEA CNN SEA Match Page E

29 4.2 Passenger (cont) Record 8 Category 25 Result Primary PTC Secondary PTC PTC (Bytes ) 2. SEA Blank SEA Match 3. SEA CNN CNN No match 4. SEA CNN ADT No match 5. ADT CNN ADT Match 6. ADT Blank ADT Match 7. ADT CNN SEA No match Passenger Status Fields (Bytes 17-24) The Passenger Status fields define the status and any geographic restrictions for the passenger specified in PTC Bytes These fields consist of the following: Application (Byte 17) Passenger Status (Byte 18) Geographic Specification (bytes 19-24) Application (Byte 17) This field defines the positive or negative application of the data specified in the Passenger Status (Byte 18) and/or Geographic Specification (bytes 19-24) fields. Value Blank: When Application is value Blank (positive), the Passenger Status (Byte 18) and/or Geographic Specification (bytes 19-24) has a positive application. The PTC specified in Bytes must meet the Passenger Status and/or Geographic Specification requirements in bytes in order to match the table. When Application is value Blank: If bytes are also Blank, there are no specific Passenger Status or Geographic requirements for the PTC in Bytes If processing matches the PTC in Bytes and matches the Passenger Status and Geographic Specification data in bytes 19-24, then processing will match the table (provided a match is made to all other match fields). Page E

30 4.2 Passenger (cont) If processing no matches the PTC in Bytes 14-16, or if processing matches the PTC in Bytes and does not match the Passenger Status and Geographic Specification data in bytes 19-24, then processing will no match the table. Value N: When Application is value N (negative), the Passenger Status (Byte 18) and Geographic Specification (bytes 19-24) have a negative application. The PTC specified in Bytes must not meet the Passenger Status and Geographic Specification requirements in bytes All Passenger Status and Geographic Specification other than the data specified in bytes are permitted. When Byte 17 is value N: If processing matches the PTC in Bytes and does not match the Passenger Status and Geographic Specification data in bytes 18-24, then processing will match the table (provided a match is made to all other match fields). If processing no matches the PTC in Bytes 14-16, or if processing matches the PTC in Bytes and matches the Passenger Status and Geographic Specification data in bytes 18-24, then processing will no match the table. Edits require that data must be present in Byte 18 (Passenger Status) and bytes (Geo Spec). Refer to the Geographic Specification examples below. Passenger Status (Byte 18) This field further defines the status requirement of the PTC in Bytes as a national (value N), resident (value R), ship registry (value S), or employee (value E) of the location specified in Geographic Specification bytes The value in Application Byte 17 specifies the positive or negative application of the Passenger Status in Byte 18 and the geographic data in bytes Edits require that when data is entered in Byte 18, data must also be entered in Geographic Specification bytes Refer to the Geographic Specification explanation and examples below. Page E

31 4.2 Passenger (cont) Geographic Specification (Bytes 19-24) The Geographic Specification field indicates geographic restrictions for the PTC in Bytes Location data may be specified as an area, zone, country, state, or city. When the Geographic Specification field is blank, there are no geographic restrictions for the PTC in Bytes The value in Passenger Status (Byte 18) specifies whether the PTC in Bytes must be a national, resident, ship registry, or employee of the location specified in bytes Edits require data in Passenger Status (Byte 18) whenever data is present in Geographic Specification (bytes 19-24). The value in Application Byte 17 specifies the positive or negative application of the Passenger Status in Byte 18 and the geographic data in bytes When Application is value Blank, the PTC in Bytes must be a national, resident, ship registry, or employee (depending upon the value in Byte 18) of the location specified in Geographic Specification bytes When Application is value N, the PTC in Bytes must not be a national, resident, ship registry, or employee (depending upon the value in Byte 18) of the location specified in Geographic Specification bytes Any national, resident, ship registry, or employee other than that specified by bytes is permitted. Example PTC * Passenger Status Application Bytes Appl Byte 17 Psgr Status Byte 18 Geo Spec Bytes MIL BLANK R N DE The MIL passenger must be a resident of Germany in order to match the table. 2. MIL N R N DE The MIL passenger must not be a resident of Germany in order to match the table (MIL may be a resident of any other location, or MIL may be a national, employee, ship registry of Germany as long as they are not a resident). 3. GST BLANK E S US FL The GST passenger must be an employee of the state of Florida in order to match the table. Page E

32 4.2 Passenger (cont) PTC * Passenger Status Application Bytes Appl Byte 17 Psgr Status Byte 18 Geo Spec Bytes GST N E S US FL The GST passenger must not be an employee of the state of Florida in order to match the table (GST may be an employee of any other location, or GST may be a national, resident, ship registry of the state of Florida as long as they are not an employee) 5. MIL BLANK BLANK N DE The MIL passenger must be a national, resident, ship registry, or employee of Germany in order to match the table. 6. MIL N BLANK N DE The MIL passenger must not be a national, resident, ship registry, or employee of Germany in order to match the table (MIL may be a national, resident, ship registry, or employee of any other location) 7. MIL BLANK BLANK BLANK The MIL passenger may be a national, resident, ship registry, or employee of any location in order to match the table. (There are no status and geographic restrictions for the MIL passenger.) * For the purpose of these examples, assume processing matches the PTC in Bytes to the Primary PTC on the Record 8 and a match is made to all other match fields ID (Byte 25) This field indicates that proof of status is required at time of ticketing/travel Age (Bytes 26-27, 28-29) These fields indicate the minimum/maximum age requirement of the PTC specified in Bytes that must be met at time and date of departure of the first flight of the fare component in order to match the table. Data in these fields may be entered as solely a minimum age (bytes 26-27) or a maximum age (bytes 28-29) or both a minimum and maximum age. When these fields are blank, there is no minimum or maximum age requirement. Page E

33 4.2 Passenger (cont) Example: Minimum (bytes 26-27) age requirement is 18. Passenger is 17 at time of ticketing but will be 18 at time/date of departure of the first flight of the fare component. Result: Processing will match the table (provided a match is made to all other match fields) Passenger Occurrence (Bytes 30-32, 33-35) The First field (bytes 30-32) specifies the first occurrence within the same PNR of the PTC in Bytes who may qualify for the fare. The Last field (bytes 33-35) specifies the last occurrence within the same PNR of the PTC in Bytes who may qualify for the fare. These fields are used when the data applies to the XXXth through the YYYth passenger of specified type. Value 000 in these fields indicates there are no occurrence restrictions. Example THEN Category 25 Record 3 PTC Bytes First Occur Bytes Last Occur Bytes Fare Calculation Data Bytes XYZ % of Y fare OR Category 25 Record 3 PTC Bytes First Occur Bytes Last Occur Bytes Fare Calculation Data Bytes XYZ % of Y fare The data in the first table indicates that the 1 st through 10 th XYZ passenger in the PNR will be charged 50% of the Y fare. The data in the second table indicates the 11 th through 20 th XYZ passenger in the PNR will be charged 75% of the Y fare. When pricing a PNR with 15 XYZ passengers: The 1 st through 10 th passengers will match the first table (provided a match is made to all other match fields) and be charged 50% of the Y fare. (Processing will continue to another table and no match the second table.) The 11 th through 15 th passengers will no match the first table and match the second table (provided a match is made to all other match fields). Charge 75% of the Y fare. Page E

DATA APPLICATION BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES PROVISIONS RECORD S7

DATA APPLICATION BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES PROVISIONS RECORD S7 DATA APPLICATION BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES PROVISIONS RECORD S7 The information contained in this document is the property of ATPCO. No part of this document may be reproduced,

More information

BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW

BAGGAGE ALLOWANCE AND CHARGES IN OPTIONAL SERVICES OVERVIEW 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

More information

Debit Memo Reasons Airlines Reporting Corporation. All rights reserved. Updated March 14,

Debit Memo Reasons Airlines Reporting Corporation. All rights reserved. Updated March 14, Debit Memo Reasons Categories Booking... 2 Chargeback... 3 Commission... 4 Exchange... 6 Fare... 15 Fee... 20 Miscellaneous... 21 Refund... 22 Tax... 23 FAQ s... 24 2017 Airlines Reporting Corporation.

More information

Accompanied Travel Enhancements. Product Advisory. May 11, 2007

Accompanied Travel Enhancements. Product Advisory. May 11, 2007 Accompanied Travel Enhancements Product Advisory May 11, 2007 2006 Galileo International. All rights reserved. Information in this document is subject to change without notice. No part of this publication

More information

INTERNATIONAL FARE RECORD

INTERNATIONAL FARE RECORD DATA APPLICATION INTERNATIONAL FARE RECORD 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

More information

Be fast with fares. Be first with customers

Be fast with fares. Be first with customers Be fast with fares. Be first with customers Agenda The challenges of fare management Get on the fast track The elements of success 2 Facing the challenges of fare management Keeping tariffs and rules up

More information

Reservation Booking Designators (RBDs)

Reservation Booking Designators (RBDs) Reservation Booking Designators (RBDs) How to Instruct and Code RBDs for Chart 1 and Chart 2 Updated 5 July 2016 2016 Airline Tariff Publishing Company. All rights reserved. Reservation Booking Designators

More information

ATPCO Category 25 SABRE FILING INSTRUCTIONS MANUAL. Effective November 26, 2007 Version 1.11

ATPCO Category 25 SABRE FILING INSTRUCTIONS MANUAL. Effective November 26, 2007 Version 1.11 ATPCO Category 25 SABRE FILING INSTRUCTIONS MANUAL Effective November 26, 2007 Version 1.11 2003, Sabre Holdings. All rights reserved. This documentation is the confidential and proprietary intellectual

More information

RULE APPLICATION AND OTHER CONDITIONS

RULE APPLICATION AND OTHER CONDITIONS Routing Details V FARE BASIS BK FARE TRAVEL-TICKET AP MINMAX RTG 1 ACNP2BE A R 1642.00 E01JL T29JN - 3/12M EH01 D15JA PASSENGER TYPE-ADT AUTO PRICE-YES FROM-BRU TO-BJS CXR-LX TVL-12JUL17 RULE-BE19 IPREUAS/4

More information

Air Travel: An Introduction (Higher) Selling Scheduled Air Travel (Higher)

Air Travel: An Introduction (Higher) Selling Scheduled Air Travel (Higher) National Unit Specification: general information NUMBER DF6M 12 COURSE Selling Scheduled Air Travel (Higher) SUMMARY This unit is designed to prepare candidates for employment in the retail travel industry.

More information

Ticketing and Carrier-Imposed Fees Reference Manual. Version 7

Ticketing and Carrier-Imposed Fees Reference Manual. Version 7 Ticketing and Reference Manual Version 7 Ticketing and Reference Manual Version 7 August 2017 2005 Airline Tariff Publishing Company. All rights reserved. Table of Contents Table of Contents Ticketing

More information

BLUE PANORAMA AIRLINES POLICY ON AGENT DEBIT MEMO (ADM)

BLUE PANORAMA AIRLINES POLICY ON AGENT DEBIT MEMO (ADM) BLUE PANORAMA AIRLINES POLICY ON AGENT DEBIT MEMO (ADM) ADM Policy Background Blue Panorama Airlines considers you as our key partners in business. We seek your support and cooperation to effectively implement

More information

Filing ZED/MIBA Fares Reference Manual

Filing ZED/MIBA Fares Reference Manual Filing ZED/MIBA Fares Reference Manual Version 9.3 10 June 2016 2006 Airline Tariff Publishing Company. All rights reserved. Filing ZED/MIBA Fares Reference Manual 1. Introduction... 2 2. Disclaimer...

More information

PMP PART 3 PRORATE AGREEMENTS SECTION B: MULTILATERAL PRORATION AGREEMENT (EFFECTIVE: 01 SEPTEMBER 2008)

PMP PART 3 PRORATE AGREEMENTS SECTION B: MULTILATERAL PRORATION AGREEMENT (EFFECTIVE: 01 SEPTEMBER 2008) PMP PART 3 PRORATE AGREEMENTS SECTION B: MULTILATERAL PRORATION AGREEMENT (EFFECTIVE: 01 SEPTEMBER 2008) CONTENTS ARTICLE Page A Scope of Agreement 3 B Amount to be Prorated (ATBP) 3-5 B1 Effective Date

More information

Sabre: Refund and Exchange Customer Questions

Sabre: Refund and Exchange Customer Questions Sabre: Refund and Exchange Customer Questions The following questions were raised by the audience during the Refund and Exchange Overview presented by Sabre 01 November 2017. Questions have been consolidated

More information

EASTERN MILES MEMBERSHIP TERMS AND CONDITIONS

EASTERN MILES MEMBERSHIP TERMS AND CONDITIONS EASTERN MILES MEMBERSHIP TERMS AND CONDITIONS TERMS AND CONDITIONS To protect the rights of the members and frequent flyers program of Eastern Miles, China Eastern Airlines Ltd. constitutes these terms

More information

Routing Details. Rules RULE APPLICATION AND OTHER CONDITIONS ELIGIBILITY DAY/TIME SEASONALITY FLIGHT APPLICATION ADVANCE RESERVATIONS/ TICKETING

Routing Details. Rules RULE APPLICATION AND OTHER CONDITIONS ELIGIBILITY DAY/TIME SEASONALITY FLIGHT APPLICATION ADVANCE RESERVATIONS/ TICKETING Routing Details V FARE BASIS BK FARE TRAVELTICKET AP MINMAX RTG 1 JN3BX J R 1161.00 T16JN / / 6M EH01 PASSENGER TYPEADT AUTO PRICEYES FROMLON TOSGN CXRTK TVL03JUL17 RULEBR01 IPREUAS/4 FARE BASISJN3BX SPECIAL

More information

ADM Policy Ticketing Audit Scope Including But Not Limited To

ADM Policy Ticketing Audit Scope Including But Not Limited To GOL Airline s Debit Memo Policy From July 2016, GOL Linhas Aéreas Inteligentes follows below guidelines for ADMs issuance. The ADM serves to notify an Agent that unless there is some justification to the

More information

myldtravel USER GUIDE

myldtravel USER GUIDE myldtravel USER GUIDE Rev #2 Page 2 of 37 Table of Contents 1. First-Time Login... 4 2. Introduction to the myldtravel Application... 7 3. Creating a Listing... 8 3.1 Traveller Selection... 9 3.2 Flight

More information

Contents. FT/SH/FTSH14.VP ES 2007 iii

Contents. FT/SH/FTSH14.VP ES 2007 iii Contents Chapter 1 - Fares Overview.............................. 1 Fare References................................... 2 Terms......................................... 4 Tariff/Fare Quote Display...............................

More information

Concur Travel: Post Ticket Change Using Sabre Automated Exchanges

Concur Travel: Post Ticket Change Using Sabre Automated Exchanges Concur Travel: Post Ticket Change Using Sabre Automated Exchanges Travel Service Guide Applies to Concur Travel: Professional/Premium edition TMC Partners Direct Customers Standard edition TMC Partners

More information

Introduction Package. June 2015

Introduction Package. June 2015 Introduction Package June 2015 Contents Welcome... 3 Customer Marketing Directors... 4 Products and Services... 5 Initial Process... 6 Components of an Instruction... 8 Fares Record Layout... 9 Add-on

More information

Fare rules & restrictions Qatar Airways (QR) RJFIP1ZE HEL to BKK

Fare rules & restrictions Qatar Airways (QR) RJFIP1ZE HEL to BKK Fare rules & restrictions Qatar Airways (QR) RJFIP1ZE HEL to BKK HEL-BKK FRI-01SEP17 QR TAXES/FEES NOT INCLUDED ADULT FARES CX FARE FARE C AP MIN/ SEASONS... MR GI D USD BASIS MAX 9 QR 1163.00R RJFIP1ZE

More information

EL AL Agent Debit Memo (ADM) Policy for Russian Travel Agents

EL AL Agent Debit Memo (ADM) Policy for Russian Travel Agents EL AL Agent Debit Memo (ADM) Policy for Russian Travel Agents In an effort to eliminate unnecessary cost and effort for you as an agent and to offer our customers the best possible service, EL AL carefully

More information

Routing Details. Rules RULE APPLICATION AND OTHER CONDITIONS ELIGIBILITY

Routing Details. Rules RULE APPLICATION AND OTHER CONDITIONS ELIGIBILITY Routing Details V FARE BASIS BK FARE TRAVEL-TICKET AP MINMAX RTG 1 ZPWWEU Z R 786.00 ---- - / 3M AT01 PASSENGER TYPE-ADT AUTO PRICE-YES FROM-ZRH TO-SFO CXR-AF TVL-20MAY17 RULE-EUPR IPRA/1 FARE BASIS-ZPWWEU

More information

e-ticketing and QREX Course (Revision 01)

e-ticketing and QREX Course (Revision 01) e-ticketing and QREX Course (Revision 01) Address: 24 Alkeou St, Engomi P.O.Box 25326, 1308 Nicosia Cyprus Tel: 357-22664515, Fax: 357-22664502, SITA:NICXZCY e-mail:zenon@cyprusair.com.cy Copyright 2006

More information

Air Travel: Reservations, Fares and Ticketing

Air Travel: Reservations, Fares and Ticketing Higher National Unit Specification General information for centres Unit title: Air Travel: Reservations, Fares and Ticketing Unit code: DK0G 34 Unit purpose: This Unit is designed to enable the candidate

More information

JAPAN AIRLINES AGENCY DEBIT MEMO POLICY AND PROCEDURE FOR TRAVEL AGENTS IN BSP MALAYSIA

JAPAN AIRLINES AGENCY DEBIT MEMO POLICY AND PROCEDURE FOR TRAVEL AGENTS IN BSP MALAYSIA JAPAN AIRLINES AGENCY DEBIT MEMO POLICY AND PROCEDURE FOR TRAVEL AGENTS IN BSP MALAYSIA In accordance to IATA Resolution 850m, Japan Airlines (JAL) hereby provides its Agency Debit Memo (ADM) Policy to

More information

Fare rules & restrictions Kenya Airways (KQ) ULUP5D LON to JNB

Fare rules & restrictions Kenya Airways (KQ) ULUP5D LON to JNB Fare rules & restrictions Kenya Airways (KQ) ULUP5D LON to JNB V FARE BASIS BK FARE TRAVEL-TICKET AP MINMAX RTG 1 ULUP5D UR 916.00 ---- 5 5/12M EH01 PASSENGER TYPE-ADT AUTO PRICE-YES FROM-LON TO-JNB CXR-KQ

More information

Fare rules & restrictions United (UA) KLNNZWWW BRU to NYC

Fare rules & restrictions United (UA) KLNNZWWW BRU to NYC Fare rules & restrictions United (UA) KLNNZWWW BRU to NYC General notes INSTANT PURCHASE NONREFUNDABLE FARES K Between AREA 2 and AREA 1 APPLIES FOR ROUND TRIP FARES Category 3: Seasonal restrictions PERMITTED

More information

NEW AND IMPROVED. ROYAL CARIBBEAN Scope & Changes DEPOSITS AND FINAL PAYMENTS DEFINITIONS, SIZE REQUIREMENTS AND LIMITS

NEW AND IMPROVED. ROYAL CARIBBEAN Scope & Changes DEPOSITS AND FINAL PAYMENTS DEFINITIONS, SIZE REQUIREMENTS AND LIMITS NEW AND IMPROVED G R O U P S Y O U R WAY ROYAL CARIBBEAN Scope & Changes The policies contained in these Groups Your Way Group Policies (the Group Policies ) of Royal Caribbean International ( Royal Caribbean

More information

CX/KA Document. Electronic Ticket (ET) - Policy and Best Practice for Travel Agents. < Effective since 28 th August 2012 > 1 of 5

CX/KA Document. Electronic Ticket (ET) - Policy and Best Practice for Travel Agents. < Effective since 28 th August 2012 > 1 of 5 CX/KA Document Electronic Ticket (ET) - Policy and Best Practice for Travel Agents < Effective since 28 th August 2012 > 1 of 5 Electronic Ticket (ET) A. Ticketing Policy for All Authorized Ticketing Agents

More information

This policy is applicable to Qatar Airways staff and agents selling QR inventory.

This policy is applicable to Qatar Airways staff and agents selling QR inventory. Background Qatar Airways considers you as our key partners in business. We seek your support and cooperation to effectively implement our policy on Agent Debit Memos (ADMs). Therefore, Qatar Airways would

More information

Improved Seat Reservation Functionality in Worldspan

Improved Seat Reservation Functionality in Worldspan Improved Seat Reservation Functionality in Worldspan Product Advisory Number: 575 High Level Description Impact Summary Reason For Issue Customer Impact Version: 4 Effective Date of Advisory: 27October

More information

GOL Airline s Debit Memo Policy

GOL Airline s Debit Memo Policy GOL Airline s Debit Memo Policy From July 2016, GOL Linhas Aéreas Inteligentes follows below guidelines for ADMs issuance. The ADM serves to notify an Agent that unless there is some justification to the

More information

Fare rules & restrictions TAP Portugal (TP) OLCAEUTP YTO to PAR

Fare rules & restrictions TAP Portugal (TP) OLCAEUTP YTO to PAR Fare rules & restrictions TAP Portugal (TP) OLCAEUTP YTO to PAR General notes BASIC SEASON ECONOMY ONE WAY SPECIAL O EXCURSION FARES Between CANADA and AREA 2 APPLIES FOR ONE WAY FARES Category 3: Seasonal

More information

Virgin Atlantic Airways Limited Global BSP Agency Debit Memo Policy

Virgin Atlantic Airways Limited Global BSP Agency Debit Memo Policy Virgin Atlantic Airways Limited Global BSP Agency Debit Memo Policy Introduction In accordance with IATA Resolution 850m, the Virgin Atlantic Airways Ltd Global BSP Agency Debit Memo Policy clarifies the

More information

Dynamic Fare Adjustments and Dynamic Fare Generation. Presented by Tom Gregorson

Dynamic Fare Adjustments and Dynamic Fare Generation. Presented by Tom Gregorson Dynamic Fare Adjustments and Dynamic Fare Generation Presented by Tom Gregorson Method 4: Dynamic Fare Adjustments or Fare Generation $ Price Value D QTY 2 Method 4: Dynamic Fare Adjustments or Fare Generation

More information

Agency Debit Memo Policy

Agency Debit Memo Policy Agency Debit Memo Policy In accordance with IATA Resolution 850m/830a, Nepal Airlines Corporation reserves the right to issue Agency Debit Memos to recover excessive GDS cost wastage. purpose of this document

More information

When the credit card company will not pay American Airlines, additional fees may apply to the debit memo(s) issued.

When the credit card company will not pay American Airlines, additional fees may apply to the debit memo(s) issued. Debit Memos Credit Card Charge Backs Debit Memo Tips Non-Refundable Ticket Refund Non-Refundable Ticket Endorsement Period Of Ticket Validity Incorrect Use Of A Ticket Designator Special Contracts GDS

More information

Fare rules & restrictions Aeromexico (AM) RRKSUNNY LON to UIO General notes

Fare rules & restrictions Aeromexico (AM) RRKSUNNY LON to UIO General notes Fare rules & restrictions Aeromexico (AM) RRKSUNNY LON to UIO General notes SHOULDER SEASON INSTANT PURCHASE NONREFUNDABLE FARES APPLIES FOR ROUND TRIP FARES FOR ADULT FOR NEG R R Category 3: Seasonal

More information

JAPAN AIRLINES AGENCY DEBIT MEMO POLICY AND PROCEDURE FOR TRAVEL AGENTS IN ARC USA

JAPAN AIRLINES AGENCY DEBIT MEMO POLICY AND PROCEDURE FOR TRAVEL AGENTS IN ARC USA JAPAN AIRLINES AGENCY DEBIT MEMO POLICY AND PROCEDURE FOR TRAVEL AGENTS IN ARC USA In accordance with IATA Resolution 850m, Japan Airlines (JAL) hereby revises its Agency Debit Memo (ADM) Policy to be

More information

FQDWAWTLV/ALY/31AUG/IL ROE UP TO 1.00 PLN 31AUG17**31AUG17/LY WAWTLV/NSP;EH/TPM 1555/MPM 2668

FQDWAWTLV/ALY/31AUG/IL ROE UP TO 1.00 PLN 31AUG17**31AUG17/LY WAWTLV/NSP;EH/TPM 1555/MPM 2668 FQDWAWTLV/ALY/31AUG/IL ROE 4.075730 UP TO 1.00 PLN 31AUG17**31AUG17/LY WAWTLV/NSP;EH/TPM 1555/MPM 2668 LN FARE BASIS OW PLN RT B PEN DATES/DAYS AP MIN MAX R 01 CPLOW 4079 C + - - + + - - M 02 CPLRT 6799

More information

Fare rules & restrictions Qatar Airways (QR) WLMYP1ZX KUL to WAS

Fare rules & restrictions Qatar Airways (QR) WLMYP1ZX KUL to WAS Fare rules & restrictions Qatar Airways (QR) WLMYP1ZX KUL to WAS General notes LOW/OFF-PEAK SEASON MIDWEEK REGULAR W EXCURSION FARES Between AREA 1 and AREA 3 FOR ROUND TRIP FARES Category 2: Day/Time

More information

Amadeus Selling Platform Timatic User Guide

Amadeus Selling Platform Timatic User Guide Amadeus Selling Platform Timatic User Guide amadeus.com YOUR USE OF THIS DOCUMENTATION IS SUBJECT TO THESE TERMS Use of this documentation You are authorised to view, copy, or print the documentation for

More information

Automated Baggage Rules (ABR): Effect on Revenue Accounting. 46 th IATA Revenue Accounting Meeting Breakout Session 9/13/2012

Automated Baggage Rules (ABR): Effect on Revenue Accounting. 46 th IATA Revenue Accounting Meeting Breakout Session 9/13/2012 IS Week 10-14 September 2012 46 th IATA Revenue Accounting Meeting Breakout Session Dave McEwen Manager, Airline Distribution Standards 11 October 2010 1 1 1 Automated Baggage Rules (ABR): Effect on Revenue

More information

Volunteer Travel & Expense Policy For Traveling on Behalf of ARMA International

Volunteer Travel & Expense Policy For Traveling on Behalf of ARMA International Volunteer Travel & Expense Policy For Traveling on Behalf of ARMA International Travel Policy Purpose & Enforcement Purpose The purpose of this document is to: Scope Ensure all designated ARMA travelers

More information

Cathay Pacific Airways. BSP Electronic Miscellaneous Document (EMD) for Travel Agents

Cathay Pacific Airways. BSP Electronic Miscellaneous Document (EMD) for Travel Agents Cathay Pacific Airways BSP Electronic Miscellaneous Document (EMD) for Travel Agents Prepared by: Sales & Distribution Last updated: Apr 2013 Version: 1.0 1 P a g e Table of Contents 1 Introduction...

More information

Lesson: Total Time: Content: Question/answer:

Lesson: Total Time: Content: Question/answer: Go! Lesson: Total Time: Content: Question/answer: Worldspan 60 minutes 45 minutes 15 minutes Lesson Description: This lesson is designed to review the booking using cruise options, search, fare codes and

More information

BIG DEAL SPECIALS TO AMERICAS BUSINESS 'Z' CLASS RT FARES TO THE AMERICAS

BIG DEAL SPECIALS TO AMERICAS BUSINESS 'Z' CLASS RT FARES TO THE AMERICAS New Issue: 20 JUL 18 Replaces: BIG DEAL SPECIALS TO AMERICAS BUSINESS 'Z' CLASS RT FARES TO THE AMERICAS 01, APPLICATION: RT, SOJ, DOJ - BUSINESS CLASS TRAVEL 02, ELIGIBILITY: FOR SALE IN AUSTRALIA TICKETS

More information

GDS/CRS Booking Policy for Air India Ltd

GDS/CRS Booking Policy for Air India Ltd RM/GDS/H9 Dated: 15 May, 2017 v jmmrr fmrmwfj* GDS/CRS Booking Policy for Air India Ltd 1. Introduction As part of our continued efforts to reduce distribution costs Air India is updating GDS/ CRS booking

More information

BEFORE THE DEPARTMENT OF TRANSPORTATION WASHINGTON, D.C. NOTICE OF TIER 1 AGREEMENTS FILING BY THE INTERNATIONAL AIR TRANSPORT ASSOCIATION

BEFORE THE DEPARTMENT OF TRANSPORTATION WASHINGTON, D.C. NOTICE OF TIER 1 AGREEMENTS FILING BY THE INTERNATIONAL AIR TRANSPORT ASSOCIATION BEFORE THE DEPARTMENT OF TRANSPORTATION WASHINGTON, D.C. Notice of IATA Traffic Conference Actions Tentatively Exempted From Filing for Approval Docket OST-2012-0058 NOTICE OF TIER 1 AGREEMENTS FILING

More information

DCC Distribution Cost Charge Operative Guideline for Travel Agents

DCC Distribution Cost Charge Operative Guideline for Travel Agents DCC Distribution Cost Charge Principle, Handling Rules & Refund Procedures SWISS International Air Lines Ltd. Malzgasse15, 4052 Basel, Switzerland 1 DCC Distribution Cost Charge Principle, Handling Rules

More information

Passenger Services Update ACH Revenue Accounting Committee By: Patty Edwards, Managing Director, Passenger Services

Passenger Services Update ACH Revenue Accounting Committee By: Patty Edwards, Managing Director, Passenger Services Passenger Services Update ACH Revenue Accounting Committee By: Patty Edwards, Managing Director, Passenger Services Adopted Effective Date: June 1, 2018 (unless otherwise noted) Resolution 30.97: Profiles

More information

Orientation Booklet The New Airline Chart Series

Orientation Booklet The New Airline Chart Series Orientation Booklet The New Airline Chart Series Copyright 2007 Jeppesen. All rights reserved. Table of Contents Introduction...1 Approach Chart...2 Heading...2 Plan View...2 Profile View... Minimums...

More information

Air France KLM ADM Policy In compliance with IATA resolution 850m

Air France KLM ADM Policy In compliance with IATA resolution 850m Applicable as per January 2015 issuances Air France KLM ADM Policy - Letter for external communication to Travel Agents In accordance with IATA resolution 850m 1. General Scope policies ensure fare rules

More information

Condor Flugdienst GmbH Thomas Cook Group Airlines Agency Debit Memo (ADM) Last updated: 2018 November 25

Condor Flugdienst GmbH Thomas Cook Group Airlines Agency Debit Memo (ADM) Last updated: 2018 November 25 Condor Flugdienst GmbH Thomas Cook Group Airlines Agency Debit Memo (ADM) Last updated: 2018 November 25 Table of Content 1. General Information 2 2. Reasons for ADMs 3 2.1. Bookings 3 2.2. Ticketing 5

More information

APPENDIX D MSP Airfield Simulation Analysis

APPENDIX D MSP Airfield Simulation Analysis APPENDIX D MSP Airfield Simulation Analysis This page is left intentionally blank. MSP Airfield Simulation Analysis Technical Report Prepared by: HNTB November 2011 2020 Improvements Environmental Assessment/

More information

November Delta, Northwest To Align Fees, Policies. November Issue

November Delta, Northwest To Align Fees, Policies. November Issue November 2008 Delta, Northwest To Align Fees, Policies NOVEMBER 05, 2008 -- Delta Air Lines plans to initiate a $15 fee for coach passengers to check their first bag, while adopting Northwest Airlines'

More information

FAQs Optional Payment Charge (OPC)

FAQs Optional Payment Charge (OPC) FAQs Optional Payment Charge (OPC) Version: 2.0 Author: Lufthansa Group Updated: Lufthansa, 20 th March 2012 1 Background & Basic Information... 1 1.1 What is the meaning of Optional Payment Charge (OPC)?...

More information

DISCOUNTED PUBLISHED FARES...

DISCOUNTED PUBLISHED FARES... Table of Contents DISCOUNTED PUBLISHED FARES... 1 FARE SELECTION - DISCOUNTED PUBLISHED... 2 FARE SELECTION - SCALED DISCOUNT BY FARE AMOUNT... 10 FINALIZE/EXIT AGREEMENT... 13 DISCOUNTED PUBLISHED EXAMPLE...

More information

Issue Date: 24 th June Agent Debit Memo QATAR AIRWAYS. Qatar Airways Policy on Agent Debit Memo (ADM) Version 2.

Issue Date: 24 th June Agent Debit Memo QATAR AIRWAYS. Qatar Airways Policy on Agent Debit Memo (ADM) Version 2. QATAR AIRWAYS Qatar Airways Policy on (ADM) Version 2.2 Page 1 of 11 TABLE OF CONTENTS 1. Background...3 2. Scope...3 3. Distribution...3 4. Legal position...3 5. Scope of ADM issuance/policy...4 6. ADM

More information

Fare Guarantee Policy

Fare Guarantee Policy Sabre Travel Network is committed to providing accurate and high-quality fare information to its customers via the Sabre system. Sabre Travel Network therefore guarantees the payment of debit memos resulting

More information

Reservations Handbook. Effective 1 June th Edition

Reservations Handbook. Effective 1 June th Edition Reservations Handbook Effective 1 June 2018 29th Edition NOTICE DISCLAIMER. The information contained in this publication is subject to constant review in the light of changing government requirements

More information

What if I just want to obtain flight schedules without making a reservation?

What if I just want to obtain flight schedules without making a reservation? http://www.omanair.com/en/faqs/booking Booking Home > Printer-friendly PDF > Booking If you have any unanswered questions about Oman Air and our services and need help, please select the appropriate category

More information

Concur Travel User Guide

Concur Travel User Guide Concur Travel User Guide Table of Contents Updating Your Travel Profile... 3 Travel Arranger... 3 Access... 3 Book a Flight... 5 Step 1: Start the Search... 5 Step 2: Select a flight... 7 Step 3: Select

More information

Passenger Agency Conference Resolutions Manual

Passenger Agency Conference Resolutions Manual Passenger Agency Conference Resolutions Manual RESOLUTION 880 REDUCED FARES FOR ACCREDITED PASSENGER SALES AGENTS PAC1(52)880(except USA) Expiry: Indefinite PAC2(52)880 Type: B PAC3(52)880 RESOLVED that,

More information

myldtravel USER GUIDE

myldtravel USER GUIDE myldtravel USER GUIDE Page 2 of 32 Welcome to myidtravel a self service tool that allows you to book travel on other airlines at a discount rate based on standby travel. And by end of Summer 2017 you will

More information

Preliminary 2018 Price Change. Initial 2017 Price

Preliminary 2018 Price Change. Initial 2017 Price ATPCO 2018 Prices Database Occupancy and Activity, and Data Collection/Input Systems Database Occupancy Charge Database Occupancy charges are determined by the percentage of ATPCO's database each customer

More information

Fare rules & restrictions LATAM (JJ) ZEEEVH0Y LON to RIO General notes

Fare rules & restrictions LATAM (JJ) ZEEEVH0Y LON to RIO General notes Fare rules & restrictions LATAM (JJ) ZEEEVH0Y LON to RIO General notes BUSINESS RESTRICTED FARES Z APPLIES FOR ROUND TRIP FARES FOR ADULT Category 4: Flight restrictions THE FARE COMPONENT MUST NOT INCLUDE

More information

Condor Flugdienst GmbH Thomas Cook Group Airlines Agency Debit Memo (ADM) Last updated: 2016 August, 23

Condor Flugdienst GmbH Thomas Cook Group Airlines Agency Debit Memo (ADM) Last updated: 2016 August, 23 Condor Flugdienst GmbH Thomas Cook Group Airlines Agency Debit Memo (ADM) Last updated: 2016 August, 23 Table of Content 1. General Information 2 2. Reasons for ADMs 3 2.1. Bookings 3 2.2.Ticketing 5 3.

More information

For additional information about this benefit, call Platinum Travel Service.

For additional information about this benefit, call Platinum Travel Service. PLATINUM BENEFITS TERMS & CONDITIONS Annual Travel Voucher: Platinum Cardmembers are eligible for one Travel Voucher of US$ 300 per year on annual Card fee renewal date. The Travel Voucher can be redeemed

More information

Cathay Pacific Airways Dragonair. BSP Electronic Miscellaneous Document (EMD) for Travel Agents

Cathay Pacific Airways Dragonair. BSP Electronic Miscellaneous Document (EMD) for Travel Agents Cathay Pacific Airways BSP Electronic Miscellaneous Document (EMD) for Travel Agents Prepared by: Sales & Distribution Last updated: Mar 2014 Version: 1.5 1 P a g e Table of Contents 1 Introduction...

More information

SERVICE AGREEMENT. The Parties agree as follows: 1. SERVICE AGREEMENT:

SERVICE AGREEMENT. The Parties agree as follows: 1. SERVICE AGREEMENT: SERVICE AGREEMENT This Service Agreement (the Service Agreement ) is effective as of the date of purchase of the baggage tracking service product offered by Blue Ribbon Bags, LLC ( Provider ) by, or on

More information

Valid for 22NOV2016. Rebooking, Reissue & Refund Procedures. SWISS International Air Lines Ltd. Malzgasse15, 4052 Basel, Switzerland

Valid for 22NOV2016. Rebooking, Reissue & Refund Procedures. SWISS International Air Lines Ltd. Malzgasse15, 4052 Basel, Switzerland SWISS Policy Irregularity Handling Procedure of 724/LX ETKT for flight cancellations due to EW cabin crew strike action - Applicable for all Travel Agents Valid for 22NOV2016 Rebooking, Reissue & Refund

More information

AIR MADAGASCAR ADM POLICY

AIR MADAGASCAR ADM POLICY Page 1 sur 5 AIR MADAGASCAR ADM POLICY Agency Debit Memos ADM Air Madagascar Policy Update : 18 June 2014 Effective date: 01st July 2014 Background AIR MADAGASCAR publishes this document in order to provide

More information

Frequently asked questions (FAQ)

Frequently asked questions (FAQ) Frequently asked questions (FAQ) Content 1. Subscription 2. Connectivity 3. Data (General) 4. Air carrier traffic 5. Traffic by Flight Stage (TFS) 6. Air carrier finances 7. Airport traffic 8. On-Flight

More information

BILATERAL TEMPLATE AIR SERVICES AGREEMENT

BILATERAL TEMPLATE AIR SERVICES AGREEMENT BILATERAL TEMPLATE AIR SERVICES AGREEMENT Throughout this document: 1) an asterisk is used to indicate that a specific provision within an article is common to each of the traditional, transitional and

More information

ESOP-A: ESOP Administration

ESOP-A: ESOP Administration ESOP-A: ESOP Administration Course The administration of employee stock ownership plans (ESOPs) requires knowledge of unique allocation and compliance testing requirements. The ESOP Administration certificate

More information

Salk Institute for Biological Studies

Salk Institute for Biological Studies Salk Institute for Biological Studies Supplier Travel Policy Purpose and Compliance Purpose This travel policy provides guidelines and established procedures for Suppliers incurring business travel and

More information

BEST PRACTICES GUIDE v1.0

BEST PRACTICES GUIDE v1.0 BEST PRACTICES GUIDE v.0 INTRODUCTION The ADM User Group (formerly known as the ADM Working Group) was established in 06 in accordance with the requirements set by the Passenger Agency Conference Steering

More information

Product information & MORE. Product Solutions

Product information & MORE. Product Solutions Product information & MORE Product Solutions Amadeus India s Ticket Capping Solution For Airlines Document control Company Amadeus India Department Product Management Table of Contents 1. Introduction...4

More information

Fare rules & restrictions Iberia (IB) INN4SO BRU to RIO

Fare rules & restrictions Iberia (IB) INN4SO BRU to RIO Fare rules & restrictions Iberia (IB) INN4SO BRU to RIO V FARE BASIS BK FARE TRAVEL-TICKET AP MINMAX RTG 1 INN4SO IR 1318.00 D31DE T21AU 14/3 SU/12M AT01 PASSENGER TYPE-ADT AUTO PRICE-YES FROM-BRU TO-RIO

More information

Fare rules & restrictions Qatar Airways (QR) RJHQP8ZX MOW to SGN

Fare rules & restrictions Qatar Airways (QR) RJHQP8ZX MOW to SGN Fare rules & restrictions Qatar Airways (QR) RJHQP8ZX MOW to SGN MOW-SGN WED-09AUG17 QR TAXES/FEES NOT INCLUDED ADULT FARES CX FARE FARE C AP MIN/ SEASONS... MR GI D USD BASIS MAX 7 QR 729.00R RJHQP8ZX

More information

Verizon Select Services Inc. Massachusetts D.P.U. Tariff No. 2 Original Page 105 SECTION 7 - GOVERNMENT AGENCY SERVICE

Verizon Select Services Inc. Massachusetts D.P.U. Tariff No. 2 Original Page 105 SECTION 7 - GOVERNMENT AGENCY SERVICE Massachusetts D.P.U. Tariff No. 2 Original Page 105 (M) 7.1 Government Agency Service 7.1.1 General Government Agency Service is a switched telecommunications service furnished only to state and local

More information

This Section 1 contains the requirements for the approval of Master Minimum Equipment Lists and Minimum Equipment Lists.

This Section 1 contains the requirements for the approval of Master Minimum Equipment Lists and Minimum Equipment Lists. SECTION 1 JAR-MMEL/MEL SECTION 1 - REQUIREMENTS 1 GENERAL This Section 1 contains the requirements for the approval of Master Minimum Equipment Lists and Minimum Equipment Lists. 2 PRESENTATION 2.1 The

More information

Supports full integration with Apollo, Galileo and Worldspan GDS.

Supports full integration with Apollo, Galileo and Worldspan GDS. FEATURES GENERAL Web-based Solution ALL TRAVELPORT GDS Supports full integration with Apollo, Galileo and Worldspan GDS. GRAPHICAL INTUITIVE WEB EXPERIENCE Intuitive web experience for both GDS expert

More information

Shuttle Membership Agreement

Shuttle Membership Agreement Shuttle Membership Agreement Trend Aviation, LLC. FlyTrendAviation.com Membership with Trend Aviation, LLC. ("Trend Aviation") is subject to the terms and conditions contained in this Membership Agreement,

More information

HOTEL PROGRAM REQUIREMENTS.

HOTEL PROGRAM REQUIREMENTS. HOTEL PROGRAM REQUIREMENTS www.owners.org/freenights freenights@ihgowners.org TABLE OF CONTENTS LIST OF DEFINED TERMS... 3 OVERVIEW OF HOTEL PROTECTIONS...4 HOTEL PROGRAM REQUIREMENTS...5-12 1. INIOA Rate

More information

PASSENGER FARE TARIFF AND SALES MANUAL

PASSENGER FARE TARIFF AND SALES MANUAL TABLE OF CONTENTS PAGE Discounted Fares Children s Fares... 4.2 Unaccompanied Children... 4.2 Unaccompanied Children Form Sample... 4.3 Senior Citizen s Fares... 4.4 Compassionate Discounts... 4.4 Traveller

More information

Fare rules & restrictions EVA Air (BR) PLX3R USA to AREA 3

Fare rules & restrictions EVA Air (BR) PLX3R USA to AREA 3 Fare rules & restrictions EVA Air (BR) PLX3R USA to AREA 3 General notes BASIC SEASON MIDWEEK ADVANCE PURCHASE P 2ND LEVEL FARES Between AREA 1 and AREA 3 FOR ROUND TRIP FARES Category 1: Eligibility restrictions

More information

Air France KLM ADM Policy In compliance with IATA resolution 850m

Air France KLM ADM Policy In compliance with IATA resolution 850m Applicable as per January 2017 issuances - In accordance with IATA resolution 850m Country - Ukraine 1. General Scope policies ensure fare rules and other agreements between the Travel Agent and AFKL are

More information

SWISS Policy Irregularity Handling Procedure for flight cancellations due to LH/4U pilot strike - for Travel Agents

SWISS Policy Irregularity Handling Procedure for flight cancellations due to LH/4U pilot strike - for Travel Agents SWISS Policy Irregularity Handling Procedure for flight cancellations due to LH/4U valid for the period 08-09SEP15 Re-booking, Re-issue & Refund Procedures SWISS International Air Lines Ltd. Malzgasse15,

More information

TRAVEL POLICY FOR THE U.S. SCIENCE SUPPORT PROGRAM OFFICE (USSSP)

TRAVEL POLICY FOR THE U.S. SCIENCE SUPPORT PROGRAM OFFICE (USSSP) TRAVEL POLICY FOR THE U.S. SCIENCE SUPPORT PROGRAM OFFICE (USSSP) Table of Contents IMPORTANT INFORMATION 2 TRAVEL AUTHORIZATION 2 AIR TRANSPORTATION GENERAL 2 EXPEDITION-RELATED TRAVEL 3 AIR CARRIER SELECTION

More information

TRIP INFORMATION: Please confirm that the travel arrangements including travel dates and times, cities, hotel(s) and passenger name(s) are correct.

TRIP INFORMATION: Please confirm that the travel arrangements including travel dates and times, cities, hotel(s) and passenger name(s) are correct. Thank you for choosing CAA Travel to help plan your travel arrangements. The purchase of the travel arrangements included in this document constitutes a contractual agreement and implies your acceptance

More information

Fare rules & restrictions LATAM (LA) ZLEEVH6P MEX to IPC

Fare rules & restrictions LATAM (LA) ZLEEVH6P MEX to IPC Fare rules & restrictions LATAM (LA) ZLEEVH6P MEX to IPC V FARE BASIS BK FARE TRAVEL-TICKET AP MINMAX RTG 1 ZLEEVH6P ZR 440.00 C31DE T30JL -/ SU/12M WH01 PASSENGER TYPE-ADT AUTO PRICE-YES FROM-MEX TO-IPC

More information

Concur Travel FAQs. 5. How do I log in to Concur Travel? Visit or the link is available on the Travel page of the Compass.

Concur Travel FAQs. 5. How do I log in to Concur Travel? Visit   or the link is available on the Travel page of the Compass. General 1. What is Concur Travel? Concur Travel is a hosted, web-based system that allows users to book travel using a web browser or mobile device instead of booking travel through a travel agent. Concur

More information

Secure Flight Passenger Data (SFPD) FAQs

Secure Flight Passenger Data (SFPD) FAQs Secure Flight Passenger Data (SFPD) FAQs Overview Formats SFPD and Passport (APIS) Frequently Asked Questions Secure Flight Domestic and International Travel Travel Redress Program (TRIP) TSA PreCheck

More information

NIAGARA MOHAWK POWER CORPORATION. Procedural Requirements

NIAGARA MOHAWK POWER CORPORATION. Procedural Requirements NIAGARA MOHAWK POWER CORPORATION Procedural Requirements Initial Effective Date: November 9, 2015 Table of Contents 1. Introduction 2. Program Definitions 3. CDG Host Eligibility Provisions 4. CDG Host

More information

kulula.com Ticket Audit and Agent Debit Memo Policy

kulula.com Ticket Audit and Agent Debit Memo Policy kulula.com Ticket Audit and Agent Debit Memo Policy Policy Title Policy Reference Number 5/01/2014 Version 8 kulula.com Ticket Audit and Agent Debit Memo Policy Author Sunel Oelofse Original Create Date

More information