Accompanied Travel Enhancements. Product Advisory. May 11, 2007

Transcription

1 Accompanied Travel Enhancements Product Advisory May 11, Galileo International. All rights reserved. Information in this document is subject to change without notice. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or any means electronic or mechanical, including photocopying and recording for any purpose without the written permission of Galileo International. All screen examples and other inserts associated with system output are provided for illustration purposes only. They are not meant to represent actual screen responses, rates, etc. Galileo International may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property rights except as expressly provided in any written license agreement from Galileo International.

2 Table of Contents Introduction...3 Enhancement Background...4 Enhancement Details...4 New Accompanied Modifier in Fare Quote...4 Accompaniment Recognition within a PNR/Booking File...4 Accompaniment Validation...4 Apollo FCMI Codes...5 Galileo FCMI and Guarantee Codes...6 Impact to Data Formats...6 Examples...7 Accompaniment Modifier and PTC in Name Remark Field...7 Maximum Number of PTCs Exceeded in PNR/Booking File...8 Implications to Other Products...9 Structured Data/XML Updates...10 Resources...12 Accompanied Travel Enhancements Product Advisory Page 2

3 Introduction Who: All Apollo and Galileo 360 Fares customers What: Accompanied Travel Enhancements Effective: Immediately Why: Greater flexibility in quoting fares for passengers with accompaniment requirements. A new accompaniment modifier in the fare quote entry will indicate an accompanying passenger in a separate PNR/Booking File. This will allow a passenger with accompaniment requirements to be priced separately. The enhancement also allows passengers with accompaniment requirements to be priced separately from the accompanying passengers who are in the same PNR/Booking File. Impacted Platforms: All terminal emulation (TE) and structured data platforms including Focalpoint, Galileo Desktop, Galileo Web Services, and XML Select Not Impacted Platform: Galileo Optimal Shopping users Accompanied Travel Enhancements Product Advisory Page 3

4 Enhancement Background Currently, when a fare requires accompaniment by another passenger, Galileo 360º Fares requires that both passengers be priced at the same time, in the same faring input. In order to override this requirement, the use of a Fare Identification Code (FIC) modifier was necessary which resulted in a fare quote that was not eligible to be guaranteed. Enhancement Details New Accompanied Modifier in Fare Quote This enhancement will allow the user to use a new input modifier, /ACC, to indicate that an accompanying passenger is booked on a separate record. This will enable the user to price and ticket individual passengers on a PNR/Booking File. Accompaniment Recognition within a PNR/Booking File In cases where the accompanied fare quote /ACC modifier is not used, the system will automatically recognize any unselected passenger(s) in the same PNR/Booking File and permit any accompaniment restrictions to pass. This enables the pricing and ticketing of fares that require accompaniment by another passenger to price separately. Accompaniment Validation With the implementation of this enhancement, two types of fare quote entries will result in some differences in accompanied rule validation: The accompanied indicator (/ACC) is used in the fare quote input The /ACC indicator is not used in a fare quote input, but the fare quote request does not include all the passengers in the PNR In these types of entries, the accompanying passengers are those either indicated by the /ACC modifier, or those implicitly recognized as the unselected passengers in the PNR. If the PTC of these accompanying passengers is not also the same PTC as any of the selected passengers, it will be assumed that the user has validated the accompaniment rules and the system should automatically pass certain accompanied travel rules in Category 13 (accompaniment) and Categories (discounts) such as: CPMT Which requires that the passenger be accompanied in the same compartment to qualify for the fare. Rule Which requires that the accompanied passenger be traveling on a fare governed by the same rule. In these types of fare quote entries, Galileo 360º Fares will only validate the PTC, age and number of accompanying passengers. All other non-passenger specific sections of the accompanied travel rule are assumed to have been validated and passed. If the accompanying passenger(s), as indicated by the /ACC modifier or implicit recognition in the PNR, have the same PTC as the passenger(s) selected, then all accompaniment rules will be validated. Accompanied Travel Enhancements Product Advisory Page 4

5 Apollo FCMI Codes For Apollo, a ticket generated with a resulting fare quote from this enhancement will output an FCMI code of 6, which is highlighted in the chart. The FCMI code is only displayed on the ticket and is generated for both the use of the /ACC modifier, or PNR recognition of accompanying passengers within the same PNR. Pricing Code Indicators Definition 0 UA or Subscriber generated. Public fare autopriced. Guaranteed. 1 UA generated. Manual priced using fill-in format. 2 UA generated. FIC or PTC was designated by the agent. 3 Subscriber generated. Public fare autopriced using the Z/ commission override. Guaranteed. 4 UA generated unpriced ticket. Subscriber generated: Airline Private Fares autopriced with or without the Z/ override. Airline Private Fares and Public fare(s) autopriced in the same fare quote with or without the Z/ override. Guaranteed. 5 Subscriber generated. Manually priced using fill-in format and commission auto generated. 6 Subscriber generated. Agency Private Fares Public, Agency Private Fares and/or Airline Private Fares with PTC designated by the agent and commission auto generated. Used with Accompanied Travel Enhancements and /A modifier. 7 Subscriber generated Public, Agency Private Fares and/or Airline Private Fares using FIC pricing with rules violation. Commission not considered. 8 Subscriber generated Manually priced using fill-in format and the Z/ commission override. 9 Subscriber generated Public, Agency Private Fares and/or Airline Private Fares with PTC designated by the agent and Z/ commission modifier used. Accompanied Travel Enhancements Product Advisory Page 5

6 Galileo FCMI and Guarantee Codes For Galileo, any ticket generated with the resulting fare quote from this enhancement will output an FCMI of 0, meaning that the fare is auto-priced. For Galileo, which also uses a Fare Status Indicator, the resulting fare will have an FSI (guarantee code) of G, meaning auto-priced by Galileo, or A, meaning airline private fares are auto-priced. With this enhancement, the Galileo A or G status will apply to fares that have been filed by an airline, as they are applied today for fares that do not require accompaniment, when accompanying/accompanied passengers are NOT priced at the same time. Impact to Data Formats The following are examples of the options associated with using the /ACC modifier in Fare Quote: Galileo Format Apollo Format Description Fare Quote child, accompanied by an FQP2*C05/ACC $BN2*C05/ACC adult passenger on a separate record /ACC input without any PTC following defaults to one Adult (ADT) Fare Quote all passengers in PNR/BF FQ*C05/ACC $B*C05/ACC as child, accompanied by an adult passenger on a separate record. FQP1*CMA/ACCCMP $BN1*CMA/ACCCMP Fare Quote companion, accompanied by a companion on a separate record. Galileo Fare Quote 2 nd passenger as companion, accompanied by a child FQP2*CMA/ACCC10 $BN2-1*CMA/ACCC10 on a separate record. Apollo Fare Quote 2 nd name field, 1 st name as companion, accompanied by a child on a separate record. Fare Quote child, accompanied by 2 FQP1*C10/ACC2 $BN1*C10/ACC2 adult passengers on a separate record. Fare Quote military children, accompanied by 2 military adult FQP1*M10.2*M07/ACC2MIL $BN1*M10+ passengers on a separate record. 2*M07/ACC2MIL Multiple accompanying passengers must be of the same passenger type. FQP1*CMA.2*CMP/ACC0 $BN1*CMA+2*CMP/ACC0 Fare Quote CMA (adult with companion) and CMP (companion), accompanied by no other passenger. Can be used in cases where implicit recognition of unselected passengers (no /ACC modifier used), would fail fare quote due to a restriction on the maximum number of accompanying passengers being exceeded. Accompanied Travel Enhancements Product Advisory Page 6

7 Galileo system passenger names in fare quote are numbered in ascending order starting with first name in the Booking File. There is not a reference to a name field number as there is in Apollo system. Entering two or more different PTCs in conjunction with the /ACC modifier will not be a supported format. Although any type of PTC modifiers are permitted with the /ACC modifier, resident modifiers ( E modifier for Spanish Residents) and personal geography modifiers ( L modifier) cannot be validated for the passenger in a separate PNR. Examples Apollo Input Galileo Input: $BN1/ACCADRLTCI $BN1/ACCADR30 $BN1*CHRLTCI/ACCADR FQP1/ACCADRLTCI FQP1/ACCADR30 FQP1*ADRLTCI/ACCADR Incorrect, since the location cannot be validated for passenger in the separate PNR Correct, since PTC and age can be validated Correct, since location modifier can be used with passenger selected from the primary PNR Incorrect, location cannot be validated for passenger in a separate Booking File Correct, since PTC and age can be validated Correct, location modifier can be used with passenger selected from the primary Booking File Accompaniment Modifier and PTC in Name Remark Field With the implementation of the PTC in Fare Quote enhancement, a PTC that exists in a passenger name remarks field will be used by fare quote, unless it is overridden by another PTC in the fare quote entry. Example: The name remarks has a PTC of M05 for military child, age 5: 1.1FRANKLIN/BMISS*P-M05 1 AA 101H 05NOV LHRJFK SS1 955A 1245P SU 2 AA 142H 20NOV JFKLHR SS1 830A 825P MO To price this passenger using the accompaniment modifier: Apollo Input: $B/ACCMIL Fare Quote Military Child, accompanied by Military Adult Galileo Input: FQ/ACCMIL Fare Quote Military Child, accompanied by Military Adult 1.1FRANKLIN/BMISS*P-M05 1 AA 101H 05NOV LHRJFK SS1 955A 1245P SU 2 AA 142H 20NOV JFKLHR SS1 830A 825P MO Accompanied Travel Enhancements Product Advisory Page 7

8 If the PTC in name remarks is overridden by a PTC in the fare quote entry: Apollo Input: $B*C05/A Price child with accompanying adult on separate PNR Galileo Input: FQP1*C05/ACC Price child with accompanying adult on separate Booking File Maximum Number of PTCs Exceeded in PNR/Booking File If not all of the passengers in a booking are being selected for fare quote, and if the number of different types of PTCs of the unselected passengers in the name field remarks in a PNR or Booking File exceeds 4 in Galileo, or 6 in Apollo, a fare quote request without the /ACC modifier will result in a new error message: TOO MANY PTCS IN BOOKING. USE /ACC MODIFIER TO QUOTE Accompaniment recognition of any un-selected passengers as accompanying passengers in the same PNR/Booking File must adhere to the existing maximum number of different PTCs that can be processed for a fare quote. Using the /ACC modifier will process only the selected passenger(s) from the PNR, based on the accompanying passenger(s) indicated by the /ACC modifier. Apollo Example: The following PNR contains 8 different PTCs: ADT (default), MIL, M05, C05, SRC, YTH, GVT, SEA 1.1TEST/AMR 2.1SOLDIER/BMR*P-MIL 3.1MILKID/JMISS*P-M05 4.1CHILD/KMISS*P-C05 5.1SENIOR/LMS*P-SRC66 6.1YOUTH/NMR*P-YTH 7.1GOVERN/MMR*P-GVT 8.SEAMAN/WMR*P-SEA 1 BA2037Y 15MAY LGWMCO GK8 1105A 320P TU Current Processing: Current Processing: New Processing: New Processing: $B results in error: TOO MANY PSGR IDENTIFICATION CODES $BN3 results in best fare for passenger, ADT, since military child must be accompanied $B results in error: TOO MANY PSGR IDENTIFICATION CODES $BN3 results in error: TOO MANY PTCS IN BOOKING. USE /ACC MODIFIER TO QUOTE Correct entry: $BN3/ACCMIL This is because of accompaniment recognition of the unselected passengers types of PTCs in the same PNR, which exceed the maximum of 6. In this case there are 7 PTCs remaining from the one selected. Accompanied Travel Enhancements Product Advisory Page 8

9 Galileo Example: With the implementation of PTC in Fare Quote, P- PTC items in name remarks will be used in a fare quote entry, unless overridden by appending a PTC in the fare quote entry. The following Booking File contains 6 different PTCs: ADT (default), MIL, M05, C05, SRC, SEA 1.1TEST/AMR 2.1SOLDIER/BMR*P-MIL 3.1MILKID/JMISS*P-M05 4.1CHILD/KMISS*P-C05 5.1SENIOR/LMR*P-SRC66 6.1SEAMAN/WMR*P-SEA 1. BA 2037 Y 15MAY LGWMCO AK TU Current Processing: Current Processing: New Processing: New Processing: New Processing: FQ - results in error response Too many passenger descriptions. FQP3 - results in best fare for passenger, ADT, since military child must be accompanied. FQ - results in error response: Too many passenger descriptions. FQP3 - results in error response: TOO MANY PTCS IN BOOKING. USE /ACC MODIFIER TO QUOTE This is because of accompaniment recognition of all the unselected passengers types of PTCs in the same Booking File exceeds 4. This example has 5 remaining passenger types from the one selected. FQP3/ACCMIL - results in a military child fare quote when applicable Implications to Other Products This enhancement is applicable to all Apollo platforms including Focalpoint, Viewpoint, Galileo Desktop, XML Select and Galileo Web Services. Exceptions to products supporting the new accompaniment modifier and enhancements are: Galileo Optimal Shopping will issue an existing error response when the /ACC accompaniment modifier is in the input request. Best Buy Quote ($BBQ) entries that are processed by Galileo Optimal Shopping entries, rather than processed by Galileo 360º Fares. The /ACC modifier will be permitted as an input, but will be ignored for the purposes of the transaction. This is the case for certain agents in Canada and the US and only for wholly North American itineraries, where the BBQ request is automatically translated to a Galileo Optimal Shopping response. Calendar Shop (Viewpoint) for both Galileo and Apollo will not support the /ACC modifier and already bypasses certain accompaniment rules. Fare Quote Planner (FQP) will support the new /ACC modifier, and already bypasses certain accompaniment rules, similar to the processing in this enhancement when the /ACC is not used. Galileo Desktop will support implicit recognition of unselected passengers in this release. However the new /ACC accompaniment modifier will require updates to Galileo Desktop, scheduled to be loaded with a future update release of Galileo Desktop 2.0. Accompanied Travel Enhancements Product Advisory Page 9

10 Structured Data/XML Updates Structured Data/XML will require updates to activate accompanied travel enhancements. If the structured data user wishes to include information about passengers to be used only for the purpose of validating accompanied travel restrictions, this can be added as additional array items to the GQPA KLR. The 'Last Name Element Number', 'Passenger Element Number' and 'Absolute Name Element ID' data within the GQPA KLR should be set to '00' for these accompanying passengers to prevent them from being priced and included in the fares returned. Field Name Data Type Length Description Length Numeric 4 Total KLR Length Record Identifier AlphaNumeric 4 'GQPA' Number of Array Items Numeric 3 Number of Array Items Delimiter Character Alpha 1 Not Used - Always 'F' Level Indicator Numeric 2 Not Used - Always '00' Version Number Numeric 2 Version of this KLR - 4 Field Name XML Tag Data Type Length Description Passenger Array <PsgrAry> Array Passenger Array Element <Psgr> FieldSet Last Name Element Number: Sequential number identifying Last Name Range Of Possible Values: Last Name Element number <LNameNum> Numeric 2 Example: If the first 3 passengers are all Smith, and the next two passenger are Jones, then the fourth and fifth passenger's Last Name Number would be '02' because they have the second last name in the group. What does null data indicate? Zero indicates passenger data not part of pricing request to be used for accompanied travel restriction validation only. If zero is input, it must be input in all three data elements: Last Name Element Number, Passenger Element Number, Absolute Name Element ID Accompanied Travel Enhancements Product Advisory Page 10

11 Passenger element number Absolute Name Element ID <PsgrNum> Numeric 2 <AbsNameNum> Numeric 2 Passenger element number: Unique Sequential number identifying a passenger within a Last Name group Range Of Possible Values: Example: If the first 3 passengers are all Smith, and the next two passenger are Jones, then the fourth passenger would have a 2 in the previous field, and a 1 in this field, since he is the first Jones in the group. What does null data indicate? Zero indicates passenger data not part of pricing request to be used for accompanied travel restriction validation only. If zero is input, it must be input in all three data elements: Last Name Element Number, Passenger Element Number, Absolute Name Element ID Absolute Name Element ID: Unique Sequential number identifying a passenger by an Absolute number, or a number that is not relative to last name groups. Range of Possible Values: Example: If the first 3 passengers are all Smith, and the next two passenger are Jones, then the fourth passenger would have a 4 in this field, since he is the fourth passenger in the group regardless of last name. What does null data indicate? Zero indicates passenger data not part of pricing request to be used for accompanied travel restriction validation only. If zero is input, it must be input in all three data elements: Last Name Element Number, Passenger Element Number, Absolute Name Element ID Accompanied Travel Enhancements Product Advisory Page 11

12 Resources HELP ENHANCE-ACCOMPANIED TRAVEL S*GEM/ACCOMPANIED TRAVEL S*AME/ VOYAGE ACCOMPAGNE (US) (CA - English) (CA - French) Accompanied Travel Enhancements Product Advisory Page 12