Automated Carrier Plating and E – Ticket Default for Plating Carrier / Fare Requests

1. Automated Carrier Plating and E– Ticket Default for Plating Carrier / Fare Requests Date : 28th Jan 2008

2. Overview • Galileo has implemented Automated Plating Carrier Selection to assist the carrier selection at the time of fare quote, to ensure applicable YQ / YR taxes and PFC charges (if applicable) are quoted for a booking file • Many airlines file plating carrier requirements in fare rules and in extra charges like fees and taxes. • Currently, in Galileo, no default plating carrier logic exists when a fare is stored in a filed fare unless the PCAF field in the agency’s AAT is turned on. • A new AAT field (PLAT) was introduced effective 03 Dec 07 that defines if the default plating carrier logic is applied to the agency. • If the PLAT field is set to Y, then the 360Fares user will have default plating carrier logic. • At the time of Fare Quote, system would automatically apply the Plating Carrier as per IATA Reso 852.

3. Overview • If the user inputs the plating carrier modifier, default plating carrier logic will not be applied. • The user will not be allowed to change the plating carrier once it is stored. • The user will have to cancel the Filed Fare and request a new fare quote with the plating carrier modifier. • Carrier YY is not a valid carrier code for default plating carrier validation. • If the entire itinerary is booked on carrier YY, default plating carrier logic will not be applied. • If part of the itinerary is booked on carrier YY, the non-YY carriers will be candidates for default plating carrier processing. • FQP does not require the input of a carrier code. If the FQP entry does not include a carrier code, default plating carrier logic will not be applied. • Fare guarantee functionality will not change with this enhancement.

4. New AAT Fields / Entries • For the correct plating carrier to be selected, 360Fares will need to know who the ticketing agency will be. • If the ticketing agency is different from the faring agency, the faring agency will have two options of specifying who the ticketing agency is: • A new ticketing agency modifier (TAxxxx) • A new AAT field (TKAG) • Two new messages will be output in the fare quote display. • The ticketing agency used to select the default plating carrier • The selected default plating carrier • The selected default plating carrier and the ticketing agency pseudo city code (PCC) will be appended in the T line of the Filed Fare.

5. AAT fields • In the Agency AAT the PLAT field should be set to Y, to activate Automated Carrier Plating for fare selection • If the Agency is a Faring Agency, the TKAG field should be updated with the Ticketing PCC. • If the Agency is a Faring and Ticketing PCC the TKAG field need not be updated • For the correct plating carrier to be selected, a new ticketing agency modifier will be introduced. The modifier is: • TAxxxx (where xxxx is the PCC of the ticketing agency) • The new ticketing agency modifier (TA) takes precedence over the new ticketing AAT field. • If the ticketing agency modifier (TA) is input with the plating carrier modifier (CCX), the ticketing agency modifier will be ignored, but it will be mirrored back in the fare quote

6. Steps to apply Automated Carrier Plating Logic • Update PLAT field in AAT table to - Y

7. Steps - contd • Update TKAG filed with Ticketing PCC (if Agency is not a ticketing agency)

8. Booking File Validation Process (where carrier is present in AUTH field) • Create a BF in the Agency PCC – 5SH5

9. Booking File Validation Process - contd • Fare using entry FQ

10. Booking File Validation Process - contd • Two new messages will be output in the fare quote display. • The ticketing agency used to select the default plating carrier – in this case 5SH4, as 5SH5 is a faring PCC only. PCC – 5SH4 is added in TKAG field.

11. Booking File Validation Process - contd • The selected default plating carrier – applicable as per IATA ruling

12. Booking File Validation Process - contd Screen Shot of AUTH field in PCC – 5SH4 (PLAT –Y and TKAG –5SH4) AA - is an Authorized carrier zed Carrier

13. Booking File Validation Process (where carrier is NOT present in AUTH field) • PCC – 3I8U

14. Booking File Validation Process - contd • Fare using entry FQ

15. Booking File Validation Process - contd • Two new messages will be output in the fare quote display. • The ticketing agency used to select the default plating carrier – in this case 3I8U, as this PCC is both a Faring and Ticketing PCC. No PCC added in TKAG field

16. Booking File Validation Process - contd • The selected default plating carrier – In case BA is selected as AA (applicable plating carrier as per IATA logic) is NOT present in the AUTH field agency PCC.

17. Booking File Validation Process - contd Screen Shot of AUTH field in PCC – 3I8U (PLAT –Y and TKAG – not updated) AA - is NOT an Authorized carrier

18. Booking File Validation Process - contd • In this case if Agency wants to issue a ticket on an AA document, then the TA entry MUST be used to fare quote BF. • Entry: FQ/TA5SH4

19. Booking File Validation Process - contd • The ticketing agency used to select the default plating carrier - 5SH4 • The selected default plating carrier - AA as applicable

20. APCL Logic for Fare Selection Galileo would apply the Plating Carrier Logic following the steps below: • Analyze the itinerary in accordance with IATA Fare Selection Criteria • Galileo would not apply any local Airline Rules for Fare Selection, if they override IATA Reso 852 • Look at the AUTH field of the TKAG - PCC in the AAT table to see if the Plating Carrier is present and validate the same • If the Plating Carrier is not present in the AUTH field, system would apply the plating of the other carriers present in the Itinerary. • To override the Default Plating Carrier, Agent must use the TA entry to validate the ticketing carrier.

21. Automatic Carrier Plating Logic When determining the plating carrier, the Galileo system will analyse the itinerary and make the required selection of the applicable fare of the airline based on the following rules: A) If the journey is: •  Wholly within a country (or) •  Wholly between Canada and the USA (or) •  Wholly within the area comprising Denmark, Norway and Sweden _ The validating carrier selected will be the carrier supplying the first sector (first coupon) for transportation.

22. Automatic Carrier Plating Logic B) If the journey is not one of the above and: • Involves transportation between Area 1 and Area 3 via Area 2 _ The validating carrier selected will be the carrier performing transatlantic transportation •  Involves transportation between IATA traffic conference (TC) areas _ The validating carrier selected will be the carrier performing the first transportation between TC areas •  Involves transportation wholly within a TC area _ The validating carrier selected will be the carrier that performs the first transportation between IATA sub-areas •  Involves transportation wholly within a single IATA sub-area _ The validating carrier selected will be the carrier that performs the first international transportation

23. Automatic Carrier Plating Logic C) If the sector that determines the plating carrier is a surface sector, the system automatically selects the validating carrier based on IATA ruling. • At time of validation, the Galileo system will also check that the chosen carrier is present in the authorized plating carrier fields of the requesting agency or ticketing agency, if designated. The system will also verify that the chosen carrier has active interline agreements with all other carriers present in the itinerary as booked.

24. Electronic Ticket Default for Fares Request and Plating Carrier Logic Effective 30th Jan / 14th Feb 08

25. Electronic Ticket Default for Fares Request and Plating Carrier Logic • All Fares and Shopping requests for all agency customers and Plating Carrier Logic will now default to Electronic Ticket when no ticketing modifier is input (ET/PT). • Electronic Ticketing is now the default assumption for all fares request, shopping entries and Plating Carrier Logic. • Fare quotes that default to ET will be returned with the “E-TKT REQUIRED” message. • All resulting fare quotes will have the ET or PT modifier appended to the ticketing line. • Plating Carrier Logic users will have Paper Ticket fares returned if any of the ET checks fail. • The user is able to override the ET default with the use of the PT modifier.

26. Electronic Ticket Default for Fares Request and Plating Carrier Logic – Current Functionality • Currently, 360° Fares system does not make any assumptions regarding the ticket type that will be issued, i.e. Electronic Ticket versus Paper Ticket. • The user is required to include the Electronic Ticketing modifier (ET) in the fares request to avoid any Paper Ticket (PT) surcharges the carrier may have filed. • Today, if Plating Carrier Logic (PLAT-Y) is utilized and the fares request includes the ET modifier, then the 360° Fares system returns ET eligible fares only • Ticketing checks fail during plating carrier determination, such as interline electronic ticketing agreements, the fares request fails • Fares and itineraries in shopping (FS) that allow Paper Tickets are not returned, requiring the user to input another fares request with the PT modifier. • Currently the ET modifier displays in the ticketing line only when it is included in the fare request. i.e. FQET

27. Electronic Ticket Default for Fares Request and Plating Carrier Logic – New Functionality • Electronic Ticketing is now the default assumption for all fares request, shopping entries and Plating Carrier Logic. • When no ticketing modifier is included in the fares request, Electronic Ticketing will be assumed. • Plating Carrier Logic will also default to Electronic Ticketing. • If any of the Electronic Ticketing checks fail, then Paper Ticket will be assumed for fares processing and output in the resulting fare quote. • Plating Carrier Logic users will have Paper Ticket fares returned if any of the ET checks fail. • The user is able to override the ET default with the use of the PT modifier. • The ticketing modifier, either ET or PT, will always be appended to the ticketing line in the Galileo Filed Fare.

28. Plating Carrier Logic Default to Electronic Ticketing. • When an itinerary is being processed for the determination of plating carrier, Galileo 360º Fares will assume that an electronic ticket will be issued and process Plating Carrier Logic accordingly. • With this enhancement if the Plating Carrier is not ET eligible, then the system would default to the ET Eligible Carrier on the itinerary. • This is the same selection that would occur if the user had specifically used the ET modifier – with this enhancement this becomes the assumption, unless overridden. • When a fare quote is requested without a ticketing modifier, the new default assumption will be ET. The ‘E-TKT REQUIRED’ message will be output with the fare quote. • The ticketing modifier, either ET or PT, will always be appended to the ticketing line in the Galileo Filed Fare.

29. Plating Carrier Logic Default to Electronic Ticketing. • When a fare quote is requested without a ticketing modifier, the new default assumption will be ET. The ‘E-TKT REQUIRED’ message will be output with the fare quote. • Entry: FQCQR or FQ >FQCQR PSGR FARE TAXES TOTAL PSG DES FQG 1 EUR 800.00 115.09 915.09 ADT GUARANTEED AT TIME OF TICKETING GRAND TOTAL INCLUDING TAXES **** EUR 915.09 ADT LAST DATE TO PURCHASE TICKET: 16JAN08 ADT E-TKT REQUIRED ADT FARE HAS A PLATING CARRIER RESTRICTION

30. Plating Carrier Logic Default to Electronic Ticketing.. • The ticketing modifier, either ET or PT, will always be appended to the ticketing line in the Galileo Filed Fare. FQ1 - S1-4 AP 27JUL07 13/AG P1 TEST/PNR ADT G * EUR 915.09 ROM QR X/DOH QR MNL 538.47QLE3MIT QR X/DOH QR ROM 538.47QLE3MI T NUC1076.94END ROE0.742833 FARE EUR800.00 TAX 2.05EX TAX 2.50HB TAX 7.41IT TAX 1.81VT TAX 101.32YQ TOT EUR915.09 S1 FB-QLE3MIT B-20K NA-16APR S2 FB-QLE3MIT B-20K NA-16APR S3 FB-QLE3MIT B-20K NB-19JAN NA-16APR S4 FB-QLE3MIT B-20K NB-19JAN NA-16APR NONEND/NONRER VALID ON QR ONLY NONREF T S1-4/CQR/ET

31. Paper Ticket Override • Users are able to override the Electronic Ticketing default by including the Paper Ticket modifier (PT) in the fares request entry. • When the PT modifier is added to the fares request, the Electronic Ticketing default is overridden. • The Paper Ticket fare is returned and the quote includes the Paper Ticket Surcharge. • The quote also includes the Paper Ticket Required message. >FQCQR/PT PSGR FARE TAXES TOTAL PSG DES FQG 1 EUR 819.00 115.09 934.09 ADT GUARANTEED AT TIME OF TICKETING GRAND TOTAL INCLUDING TAXES **** EUR 934.09 ADT LAST DATE TO PURCHASE TICKET: 16JAN08 ADT PAPER TICKET REQUIRED ADT FARE HAS A PLATING CARRIER RESTRICTION

32. Plating Carrier Logic - Electronic Ticketing Checks • When an itinerary is being processed for the determination of plating carrier, Galileo 360º Fares will assume that an ET will be issued and process Plating Carrier Logic accordingly. • The system performs the following checks: • The ET checks ensure that the itinerary is valid for ET, • Also that the interline ET agreements are in place. • If any of the above checks fail, Galileo 360º Fares will then assume PT for the itinerary and proceed with fares processing. • If a carrier does not have an electronic ticketing agreement with interline the ET check fails and a PT fare is returned including the PT surcharge. • The fare quote includes the Paper Ticket Required message and the PT modifier is added to the ticketing line.

33. Questions?