From wiki.opentravel.org

Transport »     Home • OpenTravel On-Demand Meetings

[edit] 2010B

[edit] Vehicle Rental No Show Fees

• Visit the Project Team Page

[edit] Purpose

With the recent down turn in the economy, car rental companies are finding it more difficult to get new vehicles. In the past, vehicle buy back programs, volume pricing, and inexpensive credit made it easy to maintain a large fleet of new vehicles at all times. The net effect on vehicle rental companies is that they are now forced to work with smaller fleets while trying to grow their businesses. In addition, the larger booking channels are beginning to more closely watch the number of confirmed reservations where the customer simply does not show up to pickup the vehicle. Most contracts with booking channels involve paying some commission on vehicle reservations that actually turn into completed rental contracts. Because of this, it’s natural for booking channels to be concerned with reservations that never come to fruition because they don’t get paid when a customer does not show up. For the vehicle rental company, the problem is how to efficiently utilize a smaller fleet while maintaining a high level of customer satisfaction. Reservations that are never picked up tie up inventory without generating any revenue and require the company to maintain a fleet that is larger than the actual rentals require. For booking channels, the problem is how to get a higher percentage of reservations which actually complete and generate revenue. With commission rates as high as possible, the booking channels have no choice but to look for ways to produce higher quality reservations to generate higher sales value. For both types of companies, the current industry practice of not charging cancellation fees when a reservation is not picked up is a continuing source of many of these problems. The core of this proposal is to enhance the existing OpenTravel vehicle messages to disclose the no show fee to the customer and support the collection of the fee. This involves adding content to the existing messages to indicate on which vehicles a fee applies and the rules and conditions that govern the fee. In addition, this requires some additional processing to validate that needed information is provided at booking time.

[edit] Status

On-going

[edit] Structured EMD Functionality in OpenTravel Schema

• Visit the project page

[edit] Purpose

An Electronic Miscellaneous Document (EMD) tracks the sale of charges for additional airline services, like excess baggage or lounge access, in an electronic record. The EMD replaces all paper miscellaneous documents and excess baggage tickets with one standard electronic document type. There is no method in the current OpenTravel booking schema to transport an Electronic Miscellaneous Document to a reservation system. This project will incorporate EMD into the OpenTravel booking schemas in a structured through a new complex element named EMD (Electronic Miscellaneous Document).The major advantage of a new EMD element in OpenTravel booking schema is to exchange an EMD between EMD application and reservation systems in a more structured way that supports the IATA method for EMD web services.

[edit] Status

On-going

[edit] 2010A

[edit] Vehicle Reservation Transfer

• Visit the Project Team Page
• View the Full Proposal

[edit] Status

• Project Completed

[edit] 2009A

[edit] Reservation Status Notification for Car Rental

• Visit the Project Team Page
• View the Proposal

[edit] Purpose

To reserve a vehicle in an asynchronous communication, the requestor sends to the Car Suppliers Systems or to the Central Reservation Systems (CRS) an OTA_VehResRQ message. The latter acknowledges the reception of the message with the OTA_VehResRS. The car rental company can then (e.g. 2 days after) asynchronously confirm or reject the reservation. A pair of messages that contains the functional reply of a car supplier to the trading partner is necessary. This project proposes to define a standardized message set to transport this information.

The proposed messages provide the capability for a car supplier to send Reservation Information to another system for the purpose of confirming, updating or rejecting asynchronously a reservation. The message set acts as a “push” message. The intended partners are the Car Supplier Systems, the CRS, the GDS…

This proposal will be based on the current structure of OTA_VehResRS.

[edit] Status

Published in 2009A (visit the Project Team Page)

[edit] 2008B

[edit] Insurance Replacement Fields For Cars

[edit] Purpose

Add additional elements to accommodate insurance rentals.

[edit] Status

Draft Project Team Proposal developed at Car face-to-face in April 2008.

[edit] Air Rates with Optional Fee Adjustments

[edit] Purpose

To be written.

[edit] Status

Project outlined during 2008 Advisory Forum round table discussion.

[edit] Proposal Summary

Needs the ability to send base rate information with zap-on and zap-off items. So, you would start with a base rate, but then you may be able to deduct $3.00 if you agree not to check bags, but you may agree to pay an additional $25 to have access to the lounge at the airport. So what Air Canada needs is the ability to send the rate with a list of items that you could add on or take off, and their appropriate amounts.

[edit] 2007B

[edit] Fare Families

[edit] Purpose

Airlines are re-branding and packaging fare products into fare families or fare groups. Each fare family has associated with it features, benefits and privileges commonly called attributes. These attributes are priced and marketed as features of the fare group along with the option to up sell to the next fare category or customize the flight by adding or removing features.

To permit attribute selling and flight experience customization options to passengers and offer an XML messaging experience that can incorporate the concepts.

• Project Page

[edit] Status

• PTP completed
• Approval received from IO (31 May 2007)
• Development on indefinite hold

[edit] Rate Details Notification

[edit] Purpose

The collection and distribution of Rates and Rate-related data is a common problematic for the car-rental industry players. These data are exchanged between different systems such as the Car Suppliers Systems, the Central Reservation Systems (CRS) and the Global Distribution Systems (GDS). This document proposes to define a standardized message set to transport this information.

• Project Page

[edit] Status

• PTP completed
• Approval received from IO (31 May 2007)
• Schema finalized by project team (23 July 2007)

[edit] Rule Details Notification

[edit] Purpose

The collection and distribution of Rates and Rate-related data is a common problematic for the car-rental industry players. These data are exchanged between different systems such as the Car Suppliers Systems, the Central Reservation Systems (CRS) and the Global Distribution Systems (GDS). The Rules are Rate-related data and this document proposes to define a standardized message set to transport this information.

• Project Page

[edit] Status

• PTP completed
• Approval received from IO (31 May 2007)
• Schema being developed