OptimalTipsTricks v2.doc



General Optimal Shopping Tips & Tricks

Maximum itinerary Option Recommendations 

Even though Galileo Optimal Shopping enables a user to request up to 150 different itinerary solutions for a given itinerary, due to the complexity of the request, the system may time-out if too many itinerary solutions are requested. There are three factors that affect the complexity of a Galileo Optimal Shopping request:

• Passenger Origin and Destination (actual O&D, not considering connecting cities)

• Passenger Type Codes

• Airline Preferences

The following table is provided to give the user guidelines that will maximize their success in launching Galileo Optimal Shopping requests. As the request becomes more complex, the system considers less and less schedule data when creating itineraries for pricing solutions. For example, a simple round trip request with no PTC’s might consider 250 itinerary options per direction, whereas an itinerary containing 5 O&D’s and a PTC might only consider 25 per leg. As a result, the system is unable to create as many itinerary options for complex requests as simple ones, and creates those options from a small subset of data. It is important to be aware of the trade-off between the complexity of a request and its resulting response.

|Request |Recommendation |

|1-2 O&D’s (basic round trip or one way) |10 – 150 Itinerary Solutions |

|and | |

|0-1 PTC’s | |

|3-4 O&D’s |10 – 50 Itinerary Solutions |

|and | |

|2 PTC’s | |

|> 4 O&D’s |10 – 20 Itinerary Solutions |

|or | |

|>2 PTC’s | |

|or | |

|Any Airline Preference | |

Also, keep in mind that the following factors will influence the product’s performance:

← Requesting a large number of itinerary options in some cases may result in finding more acceptable fares, but in other cases may degrade the quality of the answer returned.

← The stricter the constraint (such as narrowing the departure/arrival times), the more likelihood no options, or undesirable ones, will be returned.

← Too many origins/destinations, and too broad a time range can result in lower quality solutions.

Search logic Recommendations

The customer has the ability to define the search logic they want to use, as a default, or on transaction basis, depending on the traveler’s needs. It is important to keep in mind that these search logics help to guide the search, but are by no means absolute answers to finding a suitable itinerary. The user will need to experiment with them to understand how to maximize their value. Also, the Cheapest search logic is not always useful, since it does not take convenience into consideration at all.

Best Practice to incorporate Optimal Shopping into fare shopping process

← Evaluate the agency current shopping process and primary customer type.

← Decide on the default search logic and number of Itinerary Options for each location.

← Sign-up or register via the Galileo 360 Portal.

← Establish / update agency shopping best practice.

← Access or download the Quick Reference Document from the Galileo 360 Portal.

← Train front line agents on Optimal Shopping.

Searching the Internet Fares

If the agency is searching the Internet for sites that have content that is in Galileo, there is a solid opportunity for them to discontinue those searches. Optimal Shopping and Preferred Fares Select ensure that the content considered is the same and removes the need to shop those sites. If the agency is searching sites for content that is not in the GDS, like Southwest or JetBlue, then those searches may need to continue.

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download