08.01.2015 Views

Category 35 Ticketing Combinations Across Public & Private

Category 35 Ticketing Combinations Across Public & Private

Category 35 Ticketing Combinations Across Public & Private

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Category</strong> <strong>35</strong> <strong>Ticketing</strong><br />

<strong>Combinations</strong> <strong>Across</strong><br />

<strong>Public</strong> & <strong>Private</strong> Fares<br />

August 2011


Agenda<br />

value<br />

<strong>Ticketing</strong> <strong>Combinations</strong> across <strong>Public</strong> & <strong>Private</strong> fares<br />

• Introduction<br />

• Industry Guidelines Overview<br />

• Examples<br />

• Exception<br />

• Features and Benefits<br />

• Appendix<br />

• Industry Guidelines Detail<br />

2


Introduction<br />

value<br />

Prior to this implementation <strong>Category</strong> 10 was the sole Rule <strong>Category</strong> used<br />

to control the fares combinable for pricing.<br />

However, the increase of Cat <strong>35</strong> Negotiated Fares in markets highlighted a<br />

challenge in ticketing these fares as <strong>Category</strong> <strong>35</strong> stores information<br />

pertinent to ticketing including:<br />

• Net and/or Selling fare levels<br />

• Tour codes<br />

• Commission/mark up values<br />

• Baggage Allowance<br />

As more carriers deployed <strong>Category</strong> <strong>35</strong> it became evident that combining<br />

<strong>Category</strong> <strong>35</strong> fares with other <strong>Category</strong> <strong>35</strong>/15 private fares or standard public<br />

fares created conflicts in the data for ticketing.<br />

Therefore both <strong>Category</strong> 10 and <strong>Category</strong> <strong>35</strong> must be validated so prices are<br />

returned that can be consistently ticketed at the same level without surprise.<br />

3


Enhancement<br />

value<br />

Effective 07 September 2011<br />

Sabre will implement the ATPCO ticketing guidelines for <strong>Category</strong> <strong>35</strong><br />

<strong>Ticketing</strong> <strong>Combinations</strong> agreed to by the carriers.<br />

Sabre Air will return fares in pricing and shopping applicable for autoticketing.<br />

Sabre may bypass previously allowed pricing combinations to return the<br />

next best fare option which can be auto-ticketed.<br />

Sabre will follow the guideline using a series of four steps to address fare<br />

combination and ticketing conflicts.<br />

• The fare combination must pass these additional 4 steps<br />

The combination of fares must pass the <strong>Category</strong> 10 Combination Rules for pricing before<br />

passing into the 4 Step check list for ticketing<br />

4


ATPCo Industry Guidelines Overview<br />

value<br />

The four steps to address allowable combinations for ticketing are:<br />

Step 1 - Validate the allowable combinations between; <strong>Category</strong> 15 private fares,<br />

<strong>Category</strong> <strong>35</strong> Negotiated fares with security, Net Remit ticketing details or Net<br />

(IT/BT) <strong>Ticketing</strong> with other public fares.<br />

Step 2 - Validate the allowable combination of Net Remit Method types with the<br />

same or different carriers<br />

Sabre does not process Net Remit ticketing at this time, however we will<br />

continue to return the price in this case so ticketing can be completed manually<br />

Step 3 - Validate the allowable combination of Tour codes with the same or<br />

different carriers<br />

Step 4 - Validate the allowable combination of IT, BT or standard ticket results with<br />

the same or different carriers and the resulting output in the Fare<br />

Calculation section of the ticket.<br />

The detail of the 4 steps are in the Appendix at the end of this PowerPoint<br />

5


Pricing Changes<br />

This implementation will impact your pricing results in these<br />

possible ways:<br />

value<br />

Before Negative Result After<br />

implementation<br />

A round trip price<br />

returned a message to;<br />

“Issue Separate Tickets”<br />

•If the fare was 2 half round trip fares<br />

that could not be issued separately a<br />

new, possibly higher, fare had to be<br />

used causing an unexpected change in<br />

the final quote<br />

•If the fare was 2 one way fares the<br />

taxes were usually slightly different<br />

when issued separately causing an<br />

unexpected change in the final quote<br />

Sabre will only return<br />

fares in pricing that<br />

passes Cat 10 &<br />

Negotiated Fare<br />

ticketing checks.<br />

Ensuring fares<br />

returned can be<br />

ticketed at the same<br />

price.<br />

6


Best Practice<br />

value<br />

In today’s world there exists an increased presence of low cost carriers,<br />

One Way Branded fares and carriers who understandably require their<br />

lowest fares to be validated on their airline. Therefore, the lowest fare<br />

combination for the journey is not always the one that can be ticketed<br />

together on a single ticket.<br />

For the inventive Travel Agent advantage and best practice:<br />

1. Check Round Trip pricing for the best fare on one ticket.<br />

2. Check One Way fares in separate pricing requests to see if 2 or<br />

more fares/tickets produce the best option for your client.<br />

3. Discuss the impacts on Baggage allowances and reissue<br />

challenges with your client and proceed with the best option<br />

7


Example 1 – Previous pricing response<br />

value<br />

*IA«<br />

1 X1 529B 20NOV 5 MAASIN HK1 2315 0550 21NOV 6 /DCSQ*MYJDH4 /E<br />

2 X1 860B 21NOV 6 SINHKG HK1 0830 1215 /DCSQ*MYJDH4 /E<br />

3 X1 128J 27NOV 5 HKGSYD HK1 2020 0815 28NOV 6 /DCQF*5T7F79 /E<br />

WP«<br />

BASE FARE EQUIV AMT TAXES TOTAL<br />

1- INR153100 EUR2197.00 117.70XT EUR2314.70ADT<br />

XT 3.82WO 10.37HK 14.87WY 88.64YQ<br />

153100 2197.00 117.70 2314.70TTL<br />

ADT-01 BE320C<strong>35</strong> JOW<br />

MAA X1 X/SIN X1 HKG25M519.08X1 SYD Q4.25 2625.67NUC3149.00<br />

END ROE48.618<br />

SABRE TEST FARE/NOT VALID FOR GENERAL SALE<br />

ISSUE SEPARATE TICKETS<br />

PRIVATE FARE APPLIED - CHECK RULES FOR CORRECT TICKETING<br />

VALIDATING CARRIER – X1<br />

In the PNR the first fare<br />

component from<br />

MAA-HKG is a Cat <strong>35</strong><br />

fare with IT Net<br />

ticketing instructions<br />

and the second is a<br />

public fare that is<br />

issued as a standard<br />

ticket.<br />

Prior to this project<br />

Sabre priced the PNR<br />

but returned a trailer<br />

message to issue<br />

separate tickets as<br />

there were conflicts<br />

in the ticketing<br />

instructions<br />

A single ticket could<br />

not be issued.<br />

The example used is a Sabre created Test Filing<br />

8


Example 1- New pricing response<br />

*IA«<br />

1 X1 529B 20NOV 5 MAASIN HK1 2315 0550 21NOV 6 /DCSQ*MYJDH4 /E<br />

2 X1 860B 21NOV 6 SINHKG HK1 0830 1215 /DCSQ*MYJDH4 /E<br />

3 X1 128J 27NOV 5 HKGSYD HK1 2020 0815 28NOV 6 /DCQF*5T7F79 /E<br />

WP«<br />

BASE FARE EQUIV AMT TAXES TOTAL<br />

1- INR153100 EUR2197.00 117.70XT EUR2314.70ADT<br />

XT 3.82WO 10.37HK 14.87WY 88.64YQ<br />

153100 2197.00 117.70 2314.70TTL<br />

ADT-01 BE320C<strong>35</strong> JOW<br />

MAA X1 X/SIN X1 HKG25M519.08X1 SYD Q4.25 2625.67NUC3149.00<br />

END ROE48.618<br />

SABRE TEST FARE/NOT VALID FOR GENERAL SALE<br />

PRIVATE FARE APPLIED - CHECK RULES FOR CORRECT TICKETING<br />

VALIDATING CARRIER – X1<br />

value<br />

With this project the<br />

system now processes<br />

the 4 steps<br />

1. A Cat <strong>35</strong> IT Net<br />

Ticket and a public<br />

fare = pass<br />

2. Same carrier but<br />

neither fares have Net<br />

Remit instructions<br />

=pass<br />

3. Same carrier, one<br />

with a tour code<br />

(TESTTOUR) and one<br />

without =pass<br />

4. Same carrier one<br />

with IT text and one<br />

with the fare = pass<br />

In this case the<br />

combination passes<br />

and a single ticket<br />

can be issued<br />

9


Example 1- E-Ticket result<br />

value<br />

An automated ticket is<br />

issued with;<br />

WETR*2«<br />

ELECTRONIC TICKET RECORD<br />

INV: CUST: PNR:HUNVSJ<br />

TKT:6185775366110 ISSUED:12NOV09 PCC:6XXX IATA:96199999<br />

NAME:TEST/E MR<br />

NAME REF:<br />

TOUR ID:TESTTOUR<br />

FOP: CASH<br />

CPN A/L FLT CLS DATE BRDOFF TIME ST F/B STAT<br />

1 X1 0529 B 20NOV MAASIN 2315 OK BE320C<strong>35</strong> OPEN<br />

2 X1 0860 B 21NOV SINHKG 0830 OK BE320C<strong>35</strong> OPEN<br />

3 X1 0128 J 27NOV HKGSYD 2020 OK JOW OPEN<br />

CF00487870586 PI00906551007<br />

SABRE TEST FARE/NOT VALID FOR GENERAL SALE<br />

FARE INRIT TAX 3.82WO TAX 10.37HK TAX 14.87WY<br />

TAX 85.29YQ TAX 3.<strong>35</strong>YQ<br />

TOTAL EURIT EQUIV FARE PD EURIT<br />

•IT in the fare box<br />

• Tour code<br />

=TESTTOUR<br />

Effectively the<br />

combination of the<br />

Negotiated Cat <strong>35</strong> and<br />

the public fare is<br />

accepted and the Cat<br />

<strong>35</strong> ticketing instructions<br />

are applied to the<br />

ticket.<br />

MAA X1 X/SIN X1 HKG25M/IT SYD Q4.25 /IT END VAT EXEMPT<br />

10


Example 1- Ticket database result<br />

value<br />

WETR*2«<br />

ELECTRONIC TICKET RECORD<br />

INV: CUST: PNR:HUNVSJ<br />

TKT:6185775366110 ISSUED:12NOV09 PCC:6XXX IATA:96199999<br />

NAME:TEST/E MR<br />

NAME REF:<br />

TOUR ID:TESTTOUR<br />

FOP: CASH<br />

CPN A/L FLT CLS DATE BRDOFF TIME ST F/B STAT<br />

1 X1 0529 B 20NOV MAASIN 2315 OK BE320C<strong>35</strong> OPEN<br />

2 X1 0860 B 21NOV SINHKG 0830 OK BE320C<strong>35</strong> OPEN<br />

3 X1 0128 J 27NOV HKGSYD 2020 OK JOW OPEN<br />

CF00487870586 PI00906551007<br />

SABRE TEST FARE/NOT VALID FOR GENERAL SALE<br />

FARE INRIT TAX 3.82WO TAX 10.37HK TAX 14.87WY<br />

TAX 85.29YQ TAX 3.<strong>35</strong>YQ<br />

TOTAL EURIT EQUIV FARE PD EURIT<br />

MAA X1 X/SIN X1 HKG25M/IT SYD Q4.25 /IT END VAT EXEMPT<br />

The Sabre Ticket<br />

database shows the<br />

fare level even though<br />

to the airline it is shown<br />

as an IT only<br />

•Tour code<br />

=TESTTOUR<br />

Effectively the<br />

combination of the<br />

Negotiated Cat <strong>35</strong> and<br />

the public fare is<br />

accepted and the Cat<br />

<strong>35</strong> ticketing instructions<br />

are applied to the ticket<br />

to the airline with fare<br />

data shown to the<br />

agent view in the<br />

WTDB*<br />

.<br />

11


Example 2- Previous pricing response<br />

value<br />

*IA«<br />

1 X1 990C 20NOV 5 BOSJFK HK1 1426 1600 /E<br />

2 X1 80C 21NOV 6 JFKICN HK1 0050 0520 22NOV 7 /E<br />

3 X1 600C 22NOV 7 ICNCGK HK1 1520 2030 /E<br />

4 X1 601C 28NOV 6 CGKICN HK1 23<strong>35</strong> 0830 29NOV 7 /E<br />

5 X1 45C 29NOV 7 ICNORD HK1 1140 0905 /E<br />

WP«<br />

BASE FARE EQUIV AMT TAXES TOTAL<br />

1- USD2<strong>35</strong>9.00 EUR1579.00 43.03XT EUR1622.03ADT<br />

XT 21.56US 3.68YC 4.69XY 3.68XA<br />

3.<strong>35</strong>AY 3.05YQ 3.02XF<br />

2<strong>35</strong>9.00 1579.00 43.03 1622.03TTL<br />

ADT-01 C1SRT/CAT<strong>35</strong> C1SOW/JPS1<br />

BOS X1 X/NYC X1 X/SEL X1 JKT M1150.05 X1 X/SEL X1 CHI M1134.24<br />

3S75.00NUC2<strong>35</strong>9.29END ROE1.00 XFJFK4.5<br />

SABRE TEST FARE/NOT VALID FOR GENERAL SALE<br />

UNABLE TO AUTO TICKET – MULTIPLE TOUR CODES.<br />

VALIDATING CARRIER – X1<br />

Previous to this project<br />

Sabre would return the<br />

lowest applicable price<br />

using the rules in<br />

<strong>Category</strong> 10 that<br />

allowed these<br />

combinations.<br />

With this project Sabre<br />

processes the Industry<br />

guidelines for <strong>Ticketing</strong><br />

and reporting of these<br />

Cat <strong>35</strong> Negotiated fare<br />

combinations<br />

In this example –<br />

underneath are 2<br />

different <strong>Category</strong> <strong>35</strong><br />

fares with 2 different<br />

tour codes in the<br />

ticketing instructions<br />

that are in conflict.<br />

12


Example 2- New pricing response<br />

*IA«<br />

1 X1 990C 20NOV 5 BOSJFK HK1 1426 1600 /E<br />

2 X1 80C 21NOV 6 JFKICN HK1 0050 0520 22NOV 7 /E<br />

3 X1 600C 22NOV 7 ICNCGK HK1 1520 2030 /E<br />

4 X1 601C 28NOV 6 CGKICN HK1 23<strong>35</strong> 0830 29NOV 7 /E<br />

5 X1 45C 29NOV 7 ICNORD HK1 1140 0905 /E<br />

WP«<br />

BASE FARE EQUIV AMT TAXES TOTAL<br />

1- USD11087.00 EUR16495.00 94.81XT EUR16589.81ADT<br />

XT 47.92US 8.19YC 10.42XY 7.44XA<br />

7.44AY 6.70YQ 6.70XF<br />

11087.00 16495.00 94.81 16589.81TTL<br />

ADT-01 CWRT C CXRT<br />

BOS X1 X/NYC X1 SEL Q70.00M4655.50 X1 JKT Q10.00 1013.67 X1 SEL<br />

Q10.00 1013.67 X1 CHI Q70.00 4244.00NUC11086.84END ROE1.00 XF<br />

JFK4.5<br />

VALIDATING CARRIER - X1<br />

value<br />

The previous Cat <strong>35</strong><br />

combination is no<br />

longer applicable to<br />

pricing and ticketing<br />

and therefore Sabre<br />

bypasses that invalid<br />

combination and<br />

returns the next best<br />

fare option which can<br />

be auto-ticketed.<br />

As in this case the<br />

Round trip fare is<br />

considerably higher<br />

than was previously<br />

returned prior to the<br />

implementation.<br />

Best Practice –<br />

check one way fares<br />

for lower fares –<br />

perhaps 2 tickets are<br />

best for your<br />

customer<br />

13


Command Pricing responses<br />

If you are expecting a combination that Sabre did not return,<br />

the command price trailer message will describe why the<br />

combination is invalid.<br />

value<br />

UNABLE TO AUTO TICKET - COMMISSIONS NOT COMBINABLE<br />

OR<br />

UNABLE TO AUTO TICKET – MULTIPLE TOUR CODES<br />

Or<br />

UNABLE TO AUTO-TICKET - INVALID NET REMIT FARE<br />

OR<br />

‡NO COMBINABLE FARES FOR CLASS USED‡53.<br />

14


Re-Filing Options<br />

With this implementation fares that previously combined under<br />

the Cat 10 check may not be returned at all when ticketing<br />

conflicts are found.<br />

value<br />

If the carriers agree that the fares can be on the same ticket,<br />

the fare rules can be refiled to achieve this alignment.<br />

Otherwise the Best Practice to check one way pricing options<br />

should be followed.<br />

15


Exception<br />

Cat <strong>35</strong> Net Remit ticketing continues to be processed manually<br />

in Sabre either by Phase IV or command price to the public<br />

fare.<br />

Each country has their own method and you can find these in<br />

Format Finder :<br />

• (netov003) General Net Remit Information<br />

• (nettp001) by country<br />

If the Cat <strong>35</strong> fare is filed with a BSP Method Type of 1,2,3 or 5<br />

for Net Remit ticketing, as Sabre cannot process this data<br />

automatically at this time we will continue to return this trailer<br />

message:<br />

NET REMIT FARE - PHASE 4 AND USE NET/ FOR TKT ISSUANCE<br />

value<br />

16


New Flexible Content<br />

Prior to this implementation Sabre’s processing of <strong>Category</strong> <strong>35</strong><br />

was very controlled. We are pleased to relax many of our<br />

current edits and requirements to provide flexible solutions.<br />

value<br />

Sabre will allow all <strong>Category</strong> <strong>35</strong> fare type content to result in<br />

an IT or BT type ticket, with or without the Tour Code if filed by<br />

the carrier.<br />

This will increase the fare content<br />

applicable for auto-ticketing<br />

17


Other IT/BT Manual <strong>Ticketing</strong> Options<br />

value<br />

Golden Rule:<br />

• If the priced fare has a filed Tour Code in Cat 27 or Cat <strong>35</strong> this cannot be<br />

overridden on ticketing. Sabre will always return the filed data to protect your<br />

Fare Guarantee.<br />

Tour code<br />

manual<br />

<strong>Ticketing</strong> Input<br />

Formats<br />

W¥UABC123<br />

W¥UI*ABC12<br />

not applicable<br />

in the USA<br />

W¥UB*ABC123<br />

W¥UN*ABC123<br />

Displayed in the Ticket Fare Box;<br />

•fare amount or<br />

•IT or BT text only<br />

This manual qualifier prints a standard ticket with the fare showing<br />

and the tour code prefixed with IT in the tour box<br />

This manual qualifier masks the fare amount and places “IT” in the<br />

Fare Box.<br />

The code in the tour code box is preceded with “IT”<br />

This manual qualifier masks the fare amounts and places “BT” in<br />

the Fare Box.<br />

The code in the tour code box is preceded with “BT”<br />

This manual qualifier prints a standard ticket with the fare showing.<br />

The code in the tour code box is not preceded with “IT<br />

Effectively this will print the same as a standard driven ticket<br />

without this code if a Cat 27 or Cat <strong>35</strong> tour code is filed<br />

Tour Code Box output if<br />

the Cat 27 or Cat <strong>35</strong> of<br />

the ticketed fare is filed<br />

with Tour code XYZ123<br />

ITXYZ123<br />

ITXYZ123<br />

BTXYZ123<br />

XYZ123<br />

18


Features fully implemented by 7 September 2011<br />

value<br />

Feature<br />

Following Industry<br />

Guidelines<br />

for Negotiated fare<br />

combinations<br />

Following Industry<br />

Guidelines<br />

Following Industry<br />

Guidelines<br />

Following Industry<br />

Guidelines<br />

Benefit<br />

Returned shopping and pricing<br />

results will carry through to autoticketing<br />

<strong>Combinations</strong> that are invalid for<br />

ticketing will not be returned in<br />

pricing<br />

Returns consistent results for<br />

agents to meet carrier<br />

expectations<br />

More price-able and auto-ticketable<br />

content without inbuilt<br />

restrictions for IT or BT ticketing.<br />

19


Appendix


Step 1 - Fares in Combination<br />

1 st Fare is a; 2 nd Fare is a;<br />

AUTO TICKET<br />

If YES then go<br />

to Chart 2<br />

Cat15 (<strong>Private</strong>) <strong>Public</strong> Yes<br />

Cat15 (<strong>Private</strong>) Cat15 (<strong>Private</strong>) Yes<br />

Cat15 (<strong>Private</strong>) Cat<strong>35</strong> (Security) Yes<br />

Cat15 (<strong>Private</strong>) Cat<strong>35</strong> (Net Remit) No<br />

Cat15 (<strong>Private</strong>) Cat<strong>35</strong> (Net <strong>Ticketing</strong>) Yes<br />

Cat<strong>35</strong> (Security) <strong>Public</strong> Yes<br />

Cat<strong>35</strong> (Security) Cat<strong>35</strong> (Security) Yes<br />

Cat<strong>35</strong> (Security) Cat<strong>35</strong> (Net Remit) No<br />

Cat<strong>35</strong> (Security) Cat<strong>35</strong> (Net <strong>Ticketing</strong>) Yes<br />

Cat<strong>35</strong> (Net Remit) <strong>Public</strong> No<br />

Cat<strong>35</strong> (Net Remit) Cat<strong>35</strong> (Net Remit) Yes<br />

Cat<strong>35</strong> (Net Remit) Cat<strong>35</strong> (Net <strong>Ticketing</strong>) No<br />

Cat<strong>35</strong> (Net <strong>Ticketing</strong>) <strong>Public</strong> Yes<br />

Cat<strong>35</strong> (Net <strong>Ticketing</strong>) Cat<strong>35</strong> (Net <strong>Ticketing</strong>) Yes<br />

•This step displays all<br />

possible combinations of<br />

private fares (<strong>Category</strong><br />

15 or <strong>35</strong> fares) with other<br />

private fares or public<br />

fares. For each<br />

combination, a decision<br />

is made on whether the<br />

transaction must autoticket.<br />

•If a step is No, then<br />

processing stops and<br />

Sabre will check the next<br />

combination until the<br />

lowest fare combination<br />

is found that can be<br />

ticketed.<br />

21


Step 2 - Net Remit Method Types<br />

This step displays a grid of net remit method types and carriers in<br />

combination being the same or different. For each fares combination, a<br />

decision is made on whether the transaction must auto-ticket.<br />

If there are no Net Remit instructions we pass to Step 3<br />

Are the 2 fares<br />

owned by the same<br />

or Different<br />

Carriers<br />

Net Remit<br />

Method Type<br />

AUTO TICKET<br />

If YES then go to<br />

table 3<br />

Same carrier Same Yes<br />

Different carrier Same Yes<br />

Same carrier Different Yes<br />

Different carrier Different No<br />

22


Step 3 - Tour Code, Value Code, Contract Code<br />

This step displays a grid of tour codes and carriers in combination as being<br />

the same or different. For each combination, a decision is made on whether<br />

the transaction must auto-ticket.<br />

Are the 2 fares<br />

owned by the<br />

same or Different<br />

Carriers<br />

1 st Fare 2 nd FARE<br />

AUTO TICKET<br />

If YES then go to<br />

table 4<br />

Same carrier Same Tour Code Same Tour Code Yes<br />

Different carrier Same Tour Code Same Tour Code Yes<br />

Same carrier Tour Code No Tour Code Yes<br />

Different carrier Tour Code No Tour Code Yes<br />

Same carrier Tour Code = ABC Tour Code = XYZ No<br />

Different carrier Tour Code = ABC Tour Code = XYZ No<br />

23


24<br />

Step 4 - Fare Calculation<br />

This step assesses the data used for the Fare Calculation section of the<br />

ticket.<br />

The chart shows carriers being the same or different, information in the fare<br />

box being text or fare amounts, and the results in the fare box<br />

Are the 2 fares<br />

owned by the<br />

same or Different<br />

Carriers<br />

1 st Fare 2 nd FARE<br />

AUTO<br />

TICKET<br />

Fare Box<br />

Results<br />

Same Same Text Same Text Yes Text Text<br />

* Note- Sabre has made the decision to return the first text in the fare calc<br />

line of the ticket, rather than applying a mixture of both fare amounts and<br />

text ( “IT” or “BT”).<br />

Fare<br />

Calculation<br />

on the<br />

ticket<br />

Same Text = IT Text = BT Yes First First *<br />

Same Text Fare Yes Text First *<br />

Same Fare Fare Yes Total Fare FC<br />

Different Same Text Same Text Yes Text Text<br />

Different Text = IT Text = BT Yes First First*<br />

Different Text Fare Yes Text First *<br />

Different Same Fare Same Fare Yes Total Fare FC


Thank you<br />

Sabre Red -- your total travel solution to drive customer<br />

loyalty and power business performance<br />

25

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!