AFE 003330 Car Del Col and Billing Ref - Functional ...



[pic]

Car Delivery Collection and Billing Reference

AFE #003330

Functional Description

File Name: AFE 003330 Car Del Col and Billing Ref - Functional Description (v6).doc

Author: Kevin Wall, Cheryl Flaherty and Tim Patak

Owner/Sponsor: Ian Rispin

Issue: Version 6

Last Updated: Monday, June 12, 2006

Distribution

|Name |Department |

|Cattani, Carolyn |Product Delivery |

|Chengrian, Marianne |Development |

|Classey, David | |

|Denis, Stephen | |

|Goodrham, Paul | |

|Gordon, Kate |Product Delivery |

|Haight, Sandy |ATL Testing |

|Harrison, Graham | |

|Kidd, Robert |Subscriber Marketing |

|Loesch, Mike |Development |

|Needoff, Barry |Project Manager (EMEA) |

|O’hearn-Brennan, Sue |Product Innovation |

|Patak, Tim |Product Delivery |

|Ries, Sandra |Car Sales |

|Rispin, Ian |Hospitality |

|Rodriguez, Beatrice | |

|Rowland, Cindy |Product Innovation |

|Thomas, Nick |Enterprise Services |

|Townsie, Michael |Links/Middleware |

|Wall, Kevin |Product Delivery |

|Wilkinson, Caroline | |

Table of Contents

Distribution 2

Table of Contents 3

1.0 Car Delivery Collection and Billing Reference: Project Overview 3

1.1 Background 3

1.2 Product Overview 3

1.3 Technical Overview 3

1.4 Assumptions 3

1.5 Constraints and Risks 3

2.0 Requirements Breakdown 3

A. Car Segment Sell Request 3

B. Car Segment Sell Response 3

C. Car Rules Display 3

D. Car Segment Modify 3

E. Car Segment Cancel 3

F. Car Policy Display 3

G. Itinerary 3

H. MIR 3

I. Core System Migrations 3

J. Billing 3

K. Web Services 3

3.0 Glossary 3

4.0 Revisions 3

5.0 References & Related Documentation 3

6.0 Product Impact Checklist 3

7.0 Advisories 3

8.0 Outstanding Items 3

9.0 Screen Display Examples 3

9.1 Viewpoint Car Sell Dialog – “Special” Filetab Supports Delivery Collection 3

9.2 Viewpoint Car Sell Dialog – “Customer” File Tab Supports Billing Reference 3

9.3 Focalpoint IA Rules Response – Containing New Surcharge Labels 3

9.4 Focalpoint Non-IA Rules Display – Containing New Delivery Collection Alert 3

9.5 Focalpoint IA Rules Display – Containing New Delivery Collection Alert 3

9.6 Viewpoint – PNR Display – Current Display 3

9.6 Viewpoint – PNR Display – Current Display 3

9.6 Viewpoint – Itinerary Print – Current Display 3

9.7 Viewtrip – Itinerary Display – Currrent Display 3

9.8 Viewtrip – Electronic Expense Receipt – Current Display 3

9.9 ITIN – Current and Proposed Changes to System Defaults 3

1.0 Car Delivery Collection and Billing Reference: Project Overview

1.1 Background

Car Delivery Collection

Galileo’s existing car rental application, CarMaster, is lacking in a key competitive area: Delivery and Collection. Car Delivery Collection involves delivering the vehicle to a business location or a home address and collecting the vehicle from a corporate or home address.

Delivery Collection rentals primarily affect the UK marketplace as it is frequently part of the standard corporate rate package. Between 30-55 percent of corporate bookings in the UK include a Delivery and/or Collection arrangement.

Galileo markets have supported Delivery Collection via non-standardized work-arounds that vary by vendor. The lack of consistency frustrates subscribers and as a result many Delivery Collection rentals are not booked electronically through CarMaster. Competitor GDS, Amadeus and Sabre, offer standardized functionality to support Delivery Collection, which make the process simpler and less prone to error than current work-arounds.

Without this enhancement, CarMaster’s competitive position will remain weak and risk further loss of car rental bookings and associated air segments to other channels, e.g. the Internet or phone.

Billing Reference

Car suppliers have arrangements with corporations to invoice the corporation for payment of the car rental based upon a billing reference number. Car suppliers create a unique billing reference number for rental agreement contracts between themselves and the corporation. Each car reservation for that corporation must include the unique billing reference number for that car supplier as part of the sell request. The car supplier picks up the billing reference number from the sell request and applies it to the invoice sent to the corporation for payment of the rental.

Car suppliers and corporations in EMEA are accustomed to this type of invoice management/account reconciliation as it is used with other GDSs. To continue the success of these processes in place with other GDSs, car suppliers have asked Galileo to create a new, optional field for the receipt of billing reference information.

1.2 Product Overview

This project will establish a standardized process for supporting CarMaster Delivery Collection and Billing Reference through the use of new agent-input fields, necessary for transmitting related information to car suppliers in the link sell transaction. Additionally, new fields will be added to the car supplier segment-sell response for the return of delivery collection fees if / when available and applicable.

Agent-entered Delivery Collection and Billing Reference detail, and supplier-generated Delivery Collection fees, will be stored in the PNR/BF.

Implementation of these enhancements will:

• Be dependent upon supplier participation in Inside Link Sell; no changes will be made to the CarMaster maintenance database system to support enhancements.

0. Require development effort by car suppliers and Galileo International.

1. Occur on a car supplier basis, similar to Inside Shopper implementations.

As a result of detailed requirement discussion with several of our car suppliers, has been targeted as our initial launch partner.

Implementation of the enhancements noted above support the following corporate strategies: Grow Global Leisure Online Capabilities and Maintain Profit in Core Business.

1.3 Technical Overview

The car segment will accept and store new optional fields within the extended BAS section of the PNR/BF. The new car segment fields are defined as follows:

a) /DEL – 60 characters, non-delimited freeform text, deliver to address.

b) /COL – 60 characters, non-delimited freeform text, collection from address.

c) /DCC – 11 characters, non-delimited freeform text, delivery collection charge.

d) /BR – 25 characters, non-delimited freeform text, billing reference

e) /HP – 25 characters, freeform for customer’s home phone number (optional field)

f) /BP - 25 characters, freeform for customer’s business phone number (optional field)

g) /MP - 25 characters, freeform for customer’s mobile/cell phone number (optional field)

1.4 Assumptions

The following assumptions are being made with respect to this project:

1. Functionality will be implemented on both cores (Apollo and Galileo).

2. Creation of BAS Extension capabilities in both Apollo and Galileo must exist in order to implement this effort.

3. This enhancement will apply to Apollo and Galileo Terminal Emulation and Structured Data desktop applications including: Focalpoint, Viewpoint, and The Browser.

4. As no general release of Viewpoint is currently being prepared, the release of this functionality in Viewpoint is dependent upon an EMEA-sponsored PIR to fund this work in a post 4.0 Viewpoint release, sometime in late 2004/early 2005.

5. We will continue to support old versions of structured data.

6. Car suppliers have confirmed that the base rate shown in a regular availability response will be the same rate confirmed for a delivery collection is requested. A delivery collection request does not change the base rate or type returned in the response. Thus there is no requirement to support Delivery Collection for CAL/CAA Inside Availability; there is no need for new availability search qualifiers.

7. There is no need to support Delivery and Collection through changes to the CarMaster® database or the Car Index (CAI) display.

8. New fields will be supported in active car segment types only.

9. These fields will not be supported in Global Access and Global MIR.

10. These fields will be made available to United and may appear in a UA bookings/PNR.

11. We will have a qualified car supplier launch partner that will be able to successfully meet the requirements for participation.

12. There is no requirement to support Delivery Collection or Billing Reference within the car vendor CVMCF format.

13. CarMaster, not TPF itin packages, will perform any rules or edits on new fields, where described within this document.

14. The phone fields will be optional and used dependant upon the car companies procedures.

1.5 Constraints and Risks

The following are identified constraints and risks specific to this project:

1. Mid/Back Office systems will need to be advised and make changes to process new fields.

2. I&I system DYO defaults will need to be updated.

3. All Travel Agents DYO layouts will need to be updated.

4. If we do not have a qualified car supplier to participate, the project will not move forward.

5. Initially, participating car suppliers may not be able to identify fees associated with delivery and collection. As a result, CAV may not disclose these charges that could affect the Approximate Total, which customers expect to pay at the conclusion of their rental. Additionally, in order for Galileo to fully implement this project it may be necessary to release functionality that has not been fully tested with a car supplier (i.e. the supplier’s acceptance and return of a DCC field).

Requirements Breakdown

Note: Requirements specific to recommended handling in Viewpoint are broken out within shaded boxes.

Car Segment Sell Request

|Description |Overall Priority (H,M,L) |

|These requirements provide the means for users to submit a request a delivery and collection |H |

|rental. | |

|Ref. |Priority |Description |

|A1. | |Provide for the use of three new optional input fields within active car segment sell requests, to support identification of |

| | |Delivery Collection and Billing Reference detail. These fields are available for terminal emulation and structured data. |

|A1.1. | |For Deliver To address: |

| | |Field identifier: /DEL- |

|A1.2. | |For Collect From address: |

| | |Field identifier: /COL- |

|A1.3 | |For Phone Field related to the Delivery/Collection: These fields will be passed through on the sell, but not to the Itinerary or |

| | |MIR. |

| | |Field identifier: /HP for Home Phone |

| | |Field identifier: /BP for Business Phone |

| | |Field identifier: /MP for Mobile/Cell Phone |

|A1.4. | |For Billing Reference: |

| | |Field identifier: /BR- |

|A1.5. | |No interdependency exists between these fields. A user may opt to include either any combination (i.e. any one, two or all three |

| | |fields) in their request. |

|A1.6. | |Fields will not be supported within passive car segments. Any attempt to include will result in an error response displayed back |

| | |to the user: |

| | |Response for failed Delivery Collection request: |

| | |CHECK FORMAT – DEL/COL NOT SUPPORTED FOR PASSIVE CAR SEGMENTS |

| | |Response for failed Billing Reference request: |

| | |CHECK FORMAT – /BR NOT SUPPORTED FOR PASSIVE CAR SEGMENTS |

|A1.7. | |DEL and COL fields will each support a maximum of 60 input characters, not counting the field identifier. |

|A1.7.1. | |The car company will advise what information will be required in each field. It is a 60 character freeform text area. |

| | | |

|A1.8 | |The BR field will support a maximum of 25 input characters, not counting the field identifier. |

|A1.9. | |The same freeform character set will be supported for DEL, COL, and BR as currently supported for the SI field. |

| | |Notes: |

| | |CarMaster will not perform any edits against field content to ensure either the inclusion or specific placement of any field |

| | |delimiter. |

| | |Car supplier participants have confirmed freeform data is acceptable and desired; they will not require use of specific |

| | |address-field delimiters. |

|A2. | |Delivery Collection and Billing Reference will be supported within Type A (Inside Link) and Type B (Teletype) sell requests / |

| | |responses. |

|A2.1. | |For the Type A message sent to / from CarMaster, input field identifiers will be translated into a two-character CarMaster Inside |

| | |Link message standard: |

| | |DEL- will be translated to DE |

| | |COL- will be translated to CO |

| | |DCC- will be translated to DF |

| | |BR- will be translated to BR |

| | |HP – will be translated to HP |

| | |BP – will be translated to BP |

| | |MP – will be translated to MP |

|A3. | |Galileo will control whether or not Delivery Collection and Billing Reference fields are accepted in the user input and sent to a |

| | |particular car supplier, through use of the existing CarMaster GAC Table. |

|A3.1 | |A new table control will identify acceptance of both DEL and COL fields. |

|A3.2 | |Another new table control will identify acceptance of the BR field. |

|A3.3. | |Attempts to include any Delivery Collection field in the sell request, for a supplier that does not currently support Delivery |

| | |Collection, will result in an new error response issued from CarMaster. The error will prevent execution of the sell request: |

| | | |

| | |RESTRICTED – CAR COMPANY DOES NOT SUPPORT DEL/COL |

|A3.3. | |Similarly, attempts to include a Billing Reference field in the sell request, for a supplier that does not support Billing |

| | |Reference, will result in an new error response issued from CarMaster and prevent execution of the sell request: |

| | | |

| | |RESTRICTED – CAR COMPANY DOES NOT SUPPORT /BR |

|A3.4. | |Delivery Collection fields will be sent only to participants that have confirmed they are prepared to receive these from Galileo, |

| | |as indicated through updates to the GAC Table. |

|A3.5. | |Participants will be required to accept both Delivery Collection fields. The GAC Table control will not allow for selective |

| | |acceptance of only one field or the other. |

|A4. | |Delivery Collection and Billing Reference fields will be supported within Direct Sell and Reference Sell against car availability |

| | |displays. |

|A4.1. | |For Focalpoint, a direct sell containing both DEL and COL and the optional phone fields, might look similar to the following. |

| | |(Fields are underscored and bolded for clarification purposes only. |

| | | |

| | |>0CARZELHR11AUG-14AUGECMN/ARR-9A/DT-4P/CD-12345/SQ-PHN/DEL-NORTHERN PERIMETER ROAD WEST HOUNSLOW UK TW62QD/COL-THE ROYAL DOCKS |

| | |LONDON UK E162PX/HP-847-888-9090/BP-312-555-1234/MP-708-999-0055 |

|A4.2. | |For Focalpoint, a reference sell containing BR, DEL, and the optional phone fields, only might look similar to the following |

| | |example. |

| | |(Content shown underscored and bolded for clarification purposes only.) |

| | | |

| | |>01A1/DEL-17 AVE DE ROUEN VERNON 27200 FR/G-AX378200000000000EXP |

| | |1205/BR-987654321/HP-847-888-9090/BP-312-555-1234/MP-708-999-0055 |

|vp. | |For the Viewpoint Car Direct Sell and the normal Car Sell request dialog screens, three new Delivery Collection input fields will |

|A1 | |be accessible from the SPECIAL file tab. |

| | |Delivery Address – 60 characters max |

| | |Collection Address – 60 characters max |

| | |Billing Reference Code – 25 characters |

| | |(optional) Phone fields – 25 characters each (home, business and mobile/cell) |

| | | |

| | |Note: |

| | |The Car Direct Sell request dialog is accessed from the Car menu bar and the Car toolbar (‘direct sell’ and ‘modify’) and from |

| | |context-sensitive menus (‘new car segment’ / ‘direct sell’ / ‘modify’). |

| | | |

| | |Refer to: Screen Display Examples |

| | |9.1 Viewpoint Car Sell Dialog – “Special” Filetab Supports Delivery Collection |

| | |The new fields will appear immediately below “Special Service” and above “Special Equipment”. |

|vp. | |Fields will be positioned under a new “Car Delivery and Collection” heading, similar to the “Special Equipment” heading seen |

|A1.2. | |today. |

|vp. | |Viewpoint will edit to ensure that a combined total of no more than 60 characters have been entered into “Deliver Car To” fields, |

|A1.3. | |i.e the combined maximum number of characters allowed for the first, second and third input fields described under vp.A1.4 below. |

| | |A similar edit will be applied to “Collect Car From” field, i.e. the fourth, fifth, and sixth input fields described under |

| | |vp.A1.5. The 60-character maximums enforced here will allow for inclusion of the postal coded delimiter, described under |

| | |vp.A1.4.1 and vp.A1.5.1. |

|vp. | |The first input field will be labeled “Deliver Car To: Address:”. |

|A1.4. | |Whenever the user positions their cursor within this input field, help text (appearing in at the bottom of the Viewpoint window) |

| | |will change to read as follows: |

| | |”Enter customer address where car is to be delivered.” |

|vp. | |The input field labeled “Collect Car From: Address:”. |

|A1.5. | |Whenever the user positions their cursor within this input field, help text (appearing in at the bottom of the Viewpoint window) |

| | |will change to read as follows: |

| | |Enter customer address where car is to be collected. |

|vp.A1.6 | |The input field labeled “Phone Contacts” this input field, help text (appearing in at the bottom of the Viewpoint window) will |

| | |change to read as follows: |

| | |Enter customer phone contacts. |

| | | |

| | |Whenever the user positions their cursor within this |

|vp. | |A new “hint”, referring the user to the Car Delivery and collection policy keyword, will be included here, again similar to |

|A1.7. | |current handling for "Special Equipment". Hint will also alert user to the maximum field length limitation for both the Delivery |

| | |and Collection fields, as described under vp.A1.3 above. |

|vpA1.8 | |A new online Help for Delivery and Collection addresses. |

|vp. | |For the Viewpoint Car Direct Sell and the normal Car Sell request dialog screens, a new Billing Reference input field will be |

|A2. | |accessible from the CUSTOMER file tab. |

| | | |

| | |Note: |

| | |The Car Direct Sell request dialog is accessed from the Car menu bar and the Car toolbar (‘direct sell’ and ‘modify’) and from |

| | |context-sensitive menus (‘new car segment’ / ‘direct sell’ / ‘modify’). |

| | | |

| | |Refer to: Screen Display Examples |

| | |9.2 Viewpoint Car Sell Dialog – “Customer” File Tab Supports Billing Reference |

|vp.A2.1. | |The new field will appear immediately below the current credit card “Guarantee” field. |

|vp.A2.2. | |The field will be labeled “Billing Reference #:”. |

| | |Whenever the user positions their cursor within the input field, help text (appearing in at the bottom of the Viewpoint window) |

| | |will change to read as follows: |

| | |”Enter car billing reference number.” |

| | |Data entered into this field will be reflected in the Viewpoint “List of Selected Sell Options”, where it will be preceded by the |

| | |label “Billing Ref No:”, and mapped to the car segment /BR- field. |

|vA2.3. | |A new “hint” will be included for Billing Reference, positioned below existing hint text. |

|vpA2.4 | |Online help for Billing Reference freeform text. |

|A5. | |A reference sell made against an Inside Availability rate, and appended with COL, DEL, and/or BR field data, will continue to be |

| | |marked as an “absolute sell” request, based upon rules in place today. If other qualifiers are included with the reference sell, |

| | |or if the sell is made against a stale IA display, the request could then lose the “absolute sell” designation. |

Car Segment Sell Response

|Description |Overall Priority (H,M,L) |

|These requirements provide the means for car suppliers to confirm a delivery and collection |H |

|request. | |

|Ref. |Priority |Description |

|B1. | |Within the car segment sell response, the car supplier will be able to echo back user-entered DEL, COL and/or BR field content, as |

| | |they do with other optional fields today. |

|B2. | |Car suppliers should be allowed to modify user-supplied DEL/COL field content. |

|B3. | |Car suppliers should not be allowed to modify user-supplied BR field content. |

|B4. | |The car supplier may opt to include a Delivery Collection Charge in their response. Although participating suppliers may not be |

| | |prepared to identify any specific charge initially, a new Deliver Collection Charge field will be enabled for use in the car segment|

| | |sell response: |

|B4.1. | |For Delivery Collection Charge: |

| | |Field identifier: /DCC- |

|B4.2. | |Field will support a maximum of 11 characters of freeform alpha-numeric text data, not counting field identifiers. |

|B4.3. | |There is no interdependency between the DCC field and the DEL or COL fields. A supplier may opt to include the DCC field in any |

| | |response. Although we would not expect suppliers to return a DCC field for request that does not involve Delivery Collection, |

| | |CarMaster will not prevent this. |

|B4.4. | |Suppliers have confirmed that the currency of Delivery Collection Charge may differ from the rate currency. Where this is the case,|

| | |the supplier will be allowed to identify the currency in their freeform response, e.g. /DCC-GBP0.00. |

|B4.5. | |Where the supplier is able to return Delivery Collection Charges, and there is no charge for a specific Delivery Collection sell |

| | |request, a /DCC- field containing a “0.00” amount will be expected in the sell response; however, CarMaster will not complete any |

| | |type of validation to ensure the supplier has returned a /DCC field. |

|B5. | |DEL, COL, DCC and BR fields will be supported in both the Type A (Inside Link) and Type B (Teletype) response. |

|B5.1. | |For Focalpoint, an Inside Link sell response containing both DEL and COL fields, but no fee field, might look similar to the |

| | |following: |

| | | |

| | |Note: There is no CarMaster requirement to programmatically append an alert, such as the text “A DELIVERY AND COLLECTION CHARGE MAY|

| | |APPLY” shown in the response below. This notification will remain up to the supplier. |

| | | |

| | |Figure B1 – Car Supplier Response to Delivery and Collection Request |

| | |(Content shown underscored and bolded for clarification purposes only.) |

| | |1 CCR EP SS1 CDG 13NOV – 14NOV EBMN/BS-14537482/PUP-CDGT01/ARR |

| | |-9A/RC-EUPR-DS /DT-12N/DEL-9C BLD DES COQUIBUS EVRY 91000/COL-9C |

| | |BLD DES COQUIBUS EVRY 91000/HP-847-888-9090/BP-312-555-1234/MP-708-999-0055 |

| | | |

| | |/NM-TEST MESSAGE |

| | |/RQ-EUR63.61-UNL DY |

| | |/CF-123700938 |

| | |A DELIVERY AND COLLECTION CHARGE MAY APPLY |

| | |TOTAL RENTAL CHARGE EUR 156.56 FOR 2 DY |

| | |INCL-AIRPORT/PREM. STAT. SURCHARGE MAND-TAXES, |

| | |LAF 1.84 OPTL-ADD-DRV 9.62,CDW 6.32,PAI 5.02, |

| | |SCDW 3.34,SLDW 4.18,SPAI 2.51,THW 3.16 * |

| | |OFFER HOTEL >HOA· |

| | |> |

|B5.2. | |For Focalpoint, an Inside Link sell response containing DEL and COL fields, and DCC fields might look similar to the following: |

| | | |

| | |Figure B2 – Car Supplier Response to Delivery and Collection Request |

| | |(Content shown underscored and bolded for clarification purposes only.) |

| | |1 CCR EP SS1 CDG 13NOV – 14NOV EBMN/BS-14537482/PUP-CDGT01/ARR |

| | |-9A/RC-EUPR-DS /DT-12N/DEL-9C BLD DES COQUIBUS EVRY 91000/COL-9C |

| | |BLD DES COQUIBUS EVRY 91000/DCC-USD50.00/HP-847-888-9090/BP-312-555-1234/MP-708-999-0055 |

| | | |

| | |/NM-TEST MESSAGE |

| | |/RQ-EUR63.61-UNL DY |

| | |/CF-123700938 |

| | |TOTAL RENTAL CHARGE EUR 156.56 FOR 2 DY |

| | |INCL-AIRPORT/PREM. STAT. SURCHARGE MAND-TAXES, |

| | |LAF 1.84 OPTL-ADD-DRV 9.62,CDW 6.32,PAI 5.02, |

| | |SCDW 3.34,SLDW 4.18,SPAI 2.51,THW 3.16 * |

| | |OFFER HOTEL >HOA· |

| | |> |

|vp.B1 | |For Viewpoint, Delivery Collection and/or Billing Reference information should appear in Viewpoint’s Car Direct Sell and normal |

| | |Sell response screens, similar to how car segment optional field data and vendor freeform text are both handled today. |

|B6. | |The DCC field identifier will be translated to a two-character CarMaster standard with the Inside Link Sell message sent to/from |

| | |suppliers: |

| | |DCC will be translated to DF |

|B7. | |Car suppliers will be required to complete validation of all DEL, COL and BR field content, together with all other parameters of |

| | |the booking request. In some cases, a car supplier may require a Corporate Discount number in the Delivery Collection or Billing |

| | |Reference sell request. |

|B7.1. | |Where this is the case, the supplier will be expected to validate the sell request and return an appropriate links warning message, |

| | |rejecting the sell request. CarMaster will be prepared to accept and display this message to the user. |

|B7.2. | |For Focalpoint, a failed Inside Link sell response might look similar to the following – error number definitions should be set-up |

| | |to support each of these conditions: |

| | |Sample Response for Delivery Collection: |

| | |DELIVERY POINT NOT SUPPORTED * |

| | |COLLECTION POINT NOT SUPPORTED * |

| | |DELIVERY COLLECTION POINTS NOT SUPPORTED * |

| | |DELIVERY COLLECTION REQUIRES CD NUMBER * |

| | |Sample Response for Billing Reference: |

| | |BILLING REFERENCE REQUIRES CD NUMBER * |

|vp.B2. | |For Viewpoint, sell warning messages should be handled same as today. Any message the car supplier returns related to Delivery |

| | |Collection, through use of error code or freeform text, must be displayed back to the user. |

|B7.3. | |A successful sell response returned by the car supplier will serve as confirmation that the Delivery Collection and/or Billing |

| | |Reference request was accepted. |

|B7.4. | |In some instances, further sell validation may be required by the car supplier before they can confirm the request. In this case, |

| | |the supplier may provide an “On Request” segment response to the Type A sell request, and then return a Type B follow-up message |

| | |after ET to either confirm or reject the booking. This is consistent with current Type A sell processing options in place today. |

|B8. | |If the Type A (Inside Link) is down, the sell transaction will be processed via Type B (Teletype). |

|B9. | |Upon receipt of a successful sell response DEL, COL, DCC, HP, BP, MP, and/or BR field content will be saved in the PNR/BF using BAS |

| | |Extension. |

|B9.1. | |A PNR/BF redisplayed after receiving a successful sell response, might look similar to the following: |

| | | |

| | |Figure B3 – Focalpoint Booking File (Galileo) Display Using BAS Extension |

| | |M258K2/77 XDBKR C981772 AG 99999992 06MAY |

| | |1.1TEST/MESSAGE |

| | |1. BA 312 M 14JUN LHRCDG HK1 1205 1420 O SA |

| | |2. CCR ZE SS1 CDG 14JUN-20JUN IDMR/RG-EUR275.08WY-UNL KM XD 39 |

| | |.30 UNL/BS-99999992/ARR-1230P/RC-AEXWMC/DT-10A/NM-TEST MESSA |

| | |GE/CF-C17910959E5* |

| | |3. HHL CX HK1 PAR 14JUN-20JUN 6NT 50851 COUNTRY INN PARIS |

| | |1IA00054-1/RG-EUR174.00/AGT99999992/G-AX378200000000000EXP |

| | |1205/NM-TEST MESSAGE/CF-19B80D7* |

| | |4. BA 309 M 20JUN CDGLHR HK1 1225 1235 O FR |

| | |FONE-PARN |

| | |TKTG-T* |

| | |***ADDITIONAL ITINERARY DATA EXISTS***>*I |

| | |> |

|vp.B3. | |Figure B4 – Viewpoint PNR Display Using BAS Extension |

| | |BAS Extension for Cars will be indicated in Viewpoint similar to handling for Hotels. Assumption here is that the user would be |

| | |required to expand the Car Options Fields line to view BAS Extension items. |

| | | |

|B9.2. | |BAS Extension items for Delivery Collection and Billing Reference will be moved and stored into the PNR in the same order as they |

| | |exist in the AAA. The user will enter *I to view the additional itinerary items in the BAS Extension. |

|B9.3. | |BAS Extension items will immediately follow their associated prime BAS item on a separate indented line. |

| | | |

| | |Figure B5a– Focalpoint BAS Extension Booking File Display (Galileo) |

| | |(Content shown underscored and bolded for clarification purposes only.) |

| | | 1. BA 312 M 14JUN LHRCDG HK1 1205 1420 O SA |

| | |2. CCR ZE HK1 CDG 14JUN-20JUN IDMR/RG-EUR275.08WY-UNL KM XD 39 |

| | |.30 UNL/BS-99999992/ARR-1230P/RC-AEXWMC/DT-10A/NM-TEST MESSA |

| | |GE/CF-C17910959E5* |

| | |/DEL-EVRY DOWNTOWN ACTI CLUB 9C BLD DES COQUIBUS EVRY |

| | |91000 FR |

| | |/COL-GARE DU NORD 10 VOIE NUMERO 3 75010 FR |

| | |/BR-987654321 |

| | |/DCC-EUR25.00 |

| | |/HP-847-888-9090 |

| | |/BP-312-555-1234 |

| | |/MP-708-999-0055 |

| | | |

| | |3. HHL CX HK1 PAR 14JUN-20JUN 6NT 50851 COUNTRY INN PARIS |

| | |1IA00054-1/RG-EUR174.00/AGT99999992/G-AX378200000000000EXP |

| | |1205/NM-TEST MESSAGE/CF-19B80D7* |

| | |4. BA 309 M 20JUN CDGLHR HK1 1225 1235 O FR |

| | |> |

| | |Figure B5b– Focalpoint BAS Extension PNR Display (Apollo) |

| | |(Content shown underscored and bolded for clarification purposes only.) |

| | | 1 UA 241Y 12MAY ORDDEN SS1 935A 1201P * WE E |

| | |2 CCR AC SS1 DEN 12MAY-13MAY ECAR/RG-USD132.99DY-UNL FM XD 92.9 |

| | |9 UNL FM XH 10.00/BS-UA/PUP-DENO01/ARR-1P/RC-FLYDRV-DP /DT-1P/HP-847-888-9090/BP-312-555-1234/MP-708-999-0055/CF-1234567888US |

| | | |

| | |/DEL-123 MAIN ST DENVER CO PC-US12345 |

| | |/COL-432 SECONDARY STREET DENVER CO PC-US12343 |

| | |/BR-123456787 |

| | |/DCC-USD0.00 |

| | |/HP-847-888-9090 |

| | |/BP-312-555-1234 |

| | |/MP-708-999-0055 |

| | |> |

|vp.B4. | | |

| | |Figure B6 – Viewpoint BAS Extension Booking File Display |

| | |BAS Extension detail will appear when the user clicks on the “+” appearing next to Car Optional Fields. Extension items and |

| | |associated user-entered detail will be listed similar to “Rate Guarantee”, “Booking Source” and other items shown here. |

| | | |

|B9.4 | |BAS Extension items for Delivery Collection and Billing Reference will be moved and stored into the PNR/BF in the same order as they|

| | |exist in the AAA. The user will enter *I to view the additional itinerary items in the BAS Extension. |

|B9.5 | |BAS Extension items for Delivery Collection and Billing Reference will be reflected within PNR/BF history. The user will enter *H |

| | |to view historical itinerary items in the BAS Extension. |

| | | |

| | |Figure B7 – Focalpoint BAS Extension History Display |

| | |(Content shown underscored and bolded for clarification purposes only.) |

| | | ***** HISTORY LPQTQM ***** |

| | |** ONLY ACTIVE PRODUCTS EXIST ** |

| | |** ORIGINAL CREATOR ** |

| | |RCVD-P/0028394 |

| | |CRDT- XDB AG 39 2137Z/26MAR |

| | |** HISTORY ** |

| | |AS CCR NF 23AUG SS/SS1 LAS -24AUG ECAR/RG-USD15.30DY-UNL FM XD |

| | |22.95 .15MI 4000FM/BS-99999992/PUP-LASO01/RC-STD-DS /DT-7P/C |

| | |F- |

| | |ASE /DEL-EVRY DOWNTOWN ACTI CLUB 9C BLD DES COQUIBUS EVRY |

| | |91000 FR/EXT 1 |

| | |ASE /COL-GARE DU NORD 10 VOIE NUMERO 3 75010 FR/EXT 1 |

| | |ASE /BR-987654321 |

| | |ASE/HP-847-888-9090 |

| | |ASE/BP-312-555-1234 |

| | |ASE/MP-708-999-0055 |

| | | |

| | | |

| | | |

| | |> |

|B10 | |The Galileo International Inside Link Functional Spec will be updated to include these new optional sell request and response |

| | |fields, and re-distributed to all Inside Link car suppliers. |

Car Rules Display

|Description |Overall Priority (H,M,L) |

|Provide a means for suppliers to include disclosure of delivery and collection fees within the |M |

|car rules display. | |

|Ref. |Priority |Description |

|C1. | |Delivery Collection and Billing Reference data will not be passed in the Inside Availability Rules request; however, suppliers |

| | |will be allowed to include a breakdown of Delivery Collection Charges within their IA response to a Car Rules response made |

| | |against a sold segment. |

| | | |

| | |Assumption: |

| | |Car suppliers are able to use the car segment confirmation number, included in the CAV request, to cross-reference the Delivery |

| | |Collection booking and return associated charges. |

|C2. | |For IA participants enable use of three new surcharge label codes within any Inside Availability Rules response: |

| | |DELIVERY FEE |

| | |COLLECTION FEE |

| | |DELIVERY/COL FEE |

| | |Suppliers may return one or more labels in their response. Each label returned will include an associated cost, whether the fee |

| | |is included in the base rate –or– approximate total amount, how the charge is applied (e.g. per day v. per rental), and whether or|

| | |not the charge is taxable. All this is consistent with current IA functionality. |

| | |The IA participants can return a freeform surcharge label to specify delivery and collection fees. |

| | |Refer to: Screen Display Examples |

| | |9.3 Focalpoint IA Rules Response – Containing New Surcharge Labels |

Car Segment Modify

|Description |Overall Priority (H,M,L) |

|Modifications will be supported as they are today. |H |

|Ref. |Priority |Description |

|D1. | |CarMaster will support modification of any booking containing DEL, COL, DCC, HP, BP, MP, and/or BR field data, consistent with |

| | |car modify functional in place today. |

|D1.1. | |Users may add new or modify existing DEL, COL, HP, BP. MP, and/or BR field content using the optional field modify request. |

| | |Focalpoint Input Examples*: |

| | |>CAM2O/BR-987654321 |

| | |>CAM2O/DEL-ABCDEFGHIJKLMNOP |

| | |>CAM2O/COL-PONMLKJIHGFEDCBA |

| | |>CAM2O/COL-PONMLKJIHGFEDCBA/BR-987654321/DEL-ABCDEFGHIJKLMNOP |

| | |>CAM2O/HP-847-909-6060 |

| | |>CAM2O/BP-312-787-2345 |

| | |>CAM2O/MP-708-687-6543 |

| | |* Where “2” = PNR/BF segment number for the car segment to be modified. |

|D1.2. | |Users may cancel or remove DEL, COL, and/or BR field content using the optional field cancel request. |

| | |Focalpoint Input Examples*: |

| | |>CAM2X/BR |

| | |>CAM2X/DEL |

| | |>CAM2X/COL |

| | |>CAM2X/COL/BR/DEL |

| | |* Where “2” = PNR/BF segment number for the car segment to be modified. |

|D1.3 | |Users may not add, modify or remove DCC field content. |

|D2. | |Unless the specific field is being updated within the optional field modify / cancel request, existing DEL, COL, HP, BP, MP and/or|

| | |BR field content should remain associated to the booking. Existing DCC field content should always be replaced by that returned |

| | |in the supplier link response. |

|D3. | |A successful sell response will confirm acceptance of the car optional field modify or cancel request. |

Car Segment Cancel

|Description |Overall Priority (H,M,L) |

|Cancellations will be supported as they are today. |H |

|Ref. |Priority |Description |

|E1. | |Support the cancellation of a Delivery and Collection booking same as car segment cancellation is supported today. |

Car Policy Display

|Description |Overall Priority (H,M,L) |

|Suppliers will be able to provide freeform text policy detail for Delivery Collection rentals |M |

|and Billing Reference. | |

|Ref. |Priority |Description |

|F1. | |A new Delivery Collection policy keyword will be added to the CarMaster system for use by car vendors. |

Itinerary

|Description |Overall Priority (H,M,L) |

|Requirements provide for limited Itinerary support. |H |

|Ref. |Priority |Description |

|G1. | |For Billing Reference: The three TPF based itinerary packages will not be enhanced to support the new BR data field. The BR is |

| | |not intended to be printed on the Itinerary and Invoice document. |

|G1.1. | |The BR data will not appear on any document that is based on the TPF Itinerary package – Apollo fax, Relay. |

|G2. | |For Delivery Collection: The three TPF based Itinerary and Invoice packages will require modification to handle and output the 3 |

| | |new optional data fields. |

|G2.1 | |The new DYO labels will be added to the CAR section. |

|G2.2 | |The new DYO labels will be built as conditional constant labels. |

|G2.3 | |The DEL-, COL-, and DCC- will have one output choice. |

|G2.4 | |The DEL-, COL-, and DCC- are free text labels. The Itinerary packages will not perform any edits on these labels for content or |

| | |characters. |

|G2.5 | |The Itinerary packages will not perform any edits or hierarchy on the co-extent of labels at time of output. All labels will |

| | |print if data fields exist. Example – PUP and DEL. |

|G2.6 | |The new DYO labels are as follows: |

| | |DEL- = CARDEL, 60 bytes |

| | |COL- = CARCOL, 60 bytes |

| | |DCC- = CDELCOLCHG, 11 bytes |

|G2.7 | |The DYO labels should be added to the system defaults (DEF) with the following English conditional constant verbiage: |

| | |CARDEL = @#DEL ADDR – |

| | |CARCOL = @#COL ADDR – |

| | |DCC = @#D/C CHG – |

|G2.8 | |Local Language labels are not required for these 3 new fields. |

|G2.9. | |Translation of the conditional constant verbiage for the 3 new labels will be provided by the Business Units “sponsor” for the |

| | |foreign language system defaults. |

|G2.10 | |The DCC field should follow the current print logic used for the DO (drop charge) field. |

|G2.11 | |Section 9 contains example(s) of current and proposed changes to the system defaults. |

| | |The Business Units are still deciding on what layout version they wish to proceed with. Open item |

| | | |

| | |Refer to: Screen Display Examples |

| | |9.9 ITIN – Current and Proposed Changes to System Defaults |

|G2.12 | |The new labels should follow current Itinerary print logic. Only the text prints, excludes the CarMaster ID. |

MIR

|Description |Overall Priority (H,M,L) |

|Requirements provide for limited MIR support. |H |

|Ref. |Priority |Description |

|H1. | |For Billing Reference: The two MIR packages (MIR on 1G and MIR 92 on 1V) will output this data field when present in the car |

| | |segment. |

|H1.1. | |The BR- will be output in the Car data section – A16. |

|H1.2. | |The BR- data will appear in MIR label A160DD (Optional Data). The field currently outputs a max of 220 bytes out of a possible |

| | |407. No expansion required under Billing Reference. |

|H1.3. | |The BR- data will appear after the /SI- for data output order. |

|H2. | |For Delivery Collection: The two MIR packages (MIR on 1G and MIR 92 on 1V) will be enhanced to output these additional car |

| | |delivery and collection data fields when present in the car segment. |

|H2.1. | |The new data will be output in the current Car data section – A16. |

|H2.2. | |The new data will be output in MIR label A16ODD (Optional Data). |

|H2.3. | |The A16ODD label will need to be expanded by 280 bytes; from 220 to 500. This label is used by all the A16 groups (hotel and car |

| | |both active and passive). |

|H2.4. | |The new data will appear after the /SI- field, in the following sequence: |

| | |/SI, /BR-, /DCC-, /DEL, /COL. |

|H2.5. | |The output in the MIR should follow the current logic for these new data fields. The text information, plus the field delimiter |

| | |and the CarMaster field ID. |

Core System Migrations

|Description |Overall Priority (H,M,L) |

|Car Delivery Collection and Billing Reference should be supported for customer system |L |

|migrations. | |

|Ref. |Priority |Description |

|I1. | |Car Delivery Collection and Billing Reference field data should be retained and included in the car segment that is migrated from |

| | |one Galileo system to another. |

Billing

|Description |Overall Priority (H,M,L) |

|There are no billing-system changes required to support this effort. |N/A |

Web Services

|Description |Overall Priority (H,M,L) |

|XML services will need to enhance their product to allow for participation in this project. |H |

|Ref. |Priority |Description |

|K1. | |Galileo International Structured Data structures, XML APIs and Web Services code will be modified to allow users with the most |

| | |current product release to utilize this functionality. |

Glossary

|Term |Definition |

| | |

Revisions

|Date |Draft # |Revisions |By |

|3/31/04 |V1 |Original Document – Draft Version – Distributed to Project Team |Kevin Wall |

|4/21/04 |V2 |Draft Update –Billing Reference requirements and results from car supplier feedback |Kevin Wall |

| | |sessions | |

|4/22/04 |V2.1 |Draft Update – Combined Itin/MIR requirements for Billing Reference |Kevin Wall |

|4/23/04 |V2.2 |Draft Update – Added Viewpoint Car Sell Dialog Examples and Combined Itin/MIR |Kevin Wall |

| | |requirements for Delivery Collection | |

|5/07/04 |V2.3 |Final – Update includes additional clarification resulting from walkthrough |Kevin Wall |

| | |discussions and the introduction of a new postal code delimiter for DEL and COL | |

| | |fields. | |

|6/24/04 |V2.3 |C2-added freeform Deliver and Collection text |Cheryl Flaherty |

| |(pg 17) |C3-new surcharge label updated | |

|6/24/04 |V2.3 |Removed the “Additional delivery collection charge may apply” from the Summary |Cheryl Flaherty |

| |(pg 30-31) |Information section. | |

|6/29/04 |V2.3 |Added the Interface Document Details |Cheryl Flaherty |

| |(pg 37) | | |

|7/27/04 |V3.0 |Final – removed wording about fixed fields for the Collection and Delivery addresses. |Cheryl Flaherty |

| | |These fields are freeform. | |

|11/2/04 |V5.0 |Updated the VP wording for the three fields, delivery and collection addresses and the|Cheryl Flaherty |

| | |billing reference point | |

|11/18/04 |V6.0 |Adding three new phone fields (/HP, /BP, /MP) to the sell, PNR display, extended BAS, |Cheryl Flaherty |

| | |cancel, modify, history | |

| | |Page Section modified | |

| | |Assumption 1.4 and Technical oveview 1.3 | |

| | |A13 | |

| | |A2.1 | |

| | |A4.1 and A4.2 and vp.A.1 | |

| | |vp.A1.3 and vp.A1.6 | |

| | |11 B5.1 and B5.2 | |

| | |13 B9 | |

| | |14 B9.3 | |

| | |15 B9.5 | |

| | |17 D1.1 | |

| | | | |

| | |This new optional field will load separately on 2/10/05 | |

References & Related Documentation

|Author |Name/Reference of Document |

|Cindy Rowland |Car Enhancements: Delivery and Collection High Level Requirements, February 27, 2004 |

|Cindy Rowland |Car Enhancements: Billing Reference High Level Requirements, February 27, 2004 |

|Tim Patak |Car Billing Reference Functional Requirement Document, version 2.0, final, April 21, 2004 |

| | |

Product Impact Checklist

|Product Name |Impact |

| |Yes |No |Unknown |

|ACCESS PRODUCTS | | | |

|Edifact Select | | | |

|Relay | | | |

|Viewpoint | | | |

|AIR | | | |

|Airline Servicing Terminals/Co-Host | | | |

|Availability | | | |

|Links | | | |

|Seats/Seat Maps | | | |

|Sell | | | |

|Teletype | | | |

|Travel Restriction Table | | | |

|BILLING | | | |

|CAR | | | |

|Availability | | | |

|Links | | | |

|Sell | | | |

|Teletype | | | |

|Other –       | | | |

|DOCUMENT PRODUCTION | | | |

|CGNR (1G only 0 impacts what prints in net remit area of ticket) | | | |

|MIR | | | |

|RET (1G and 1V – BSP/ARC reporting tape) | | | |

|GLOBALFARES | | | |

|ITA | | | |

|HOTEL | | | |

|Availability | | | |

|Links | | | |

|Sell | | | |

|Teletype | | | |

|LEGAL | | | |

|Product Name |Impact |

| |Yes |No |Unknown |

|LEISURE | | | |

|Availability | | | |

|Links | | | |

|Sell | | | |

|Teletype | | | |

|PNR/Booking File | | | |

|AAT | | | |

|Claim PNR | | | |

|Client File/Travel Screen | | | |

|Custom Check | | | |

|Enhanced Booking File Servicing | | | |

|Fixed Format Display | | | |

|Galileo Integrated Data Source (GIDS) | | | |

|Global Access | | | |

|Queues | | | |

|SSRs | | | |

|Terminal Security | | | |

|TDS | | | |

|Cendant Travel | | | |

|CheapTickets | | | |

|Travelport | | | |

|United Airlines | | | |

7.0 Advisories

|Advanced Notification Requirement |60 Days |90 Days |120 Days |

| | | |Planned May 12, 2004 |

8.0 Outstanding Items

|Requirement Reference |Description |Tracking |

|F1. |Policy Keyword text to support Delivery Collection |Open. Required from the supplier group. |

|G. |Foreign language translations for the new labels contain data text |Open. Required from the Business Units. |

| | |A total of 8 languages on 1g and 10 on |

| | |1v. |

|G2.11. |Agreement on ITIN Layout |Open. Business Units are still deciding |

| | |on what layout version they wish to |

| | |proceed with. |

|G. |Recommended layouts for Viewpoint and Viewtrip ITIN |Open. |

|A4.3.5. |Viewpoint “Hint” text for Billing Reference and Delivery Collection |Open. Text must be defined. |

|A4.4.3 | | |

|C. |Need to validate Galileo’s definition of Approximate Total and how |Open. |

| |this might affect the disclosure of Delivery Collection fees on the | |

| |rules display as well as any expectation that car companies include | |

| |these fees in their Approximate Total calculation. | |

9.0 Screen Display Examples

9.1 Viewpoint Car Sell Dialog – “Special” Filetab Supports Delivery Collection

(Content shown highlighted or in red text for clarification purposes only.)

The Delivery and/or Collection address area will be 60 freeform characters and not structured into sections.

[pic]

9.2 Viewpoint Car Sell Dialog – “Customer” File Tab Supports Billing Reference

(Content shown highlighted or in red text for clarification purposes only.)

[pic]

9.3 Focalpoint IA Rules Response – Containing New Surcharge Labels

(Content shown underscored and bolded for clarification purposes only.)

** AVIS INSIDE AVAILABILITY RULES DISPLAY **

AVIS - A DYNAMIC GLOBAL ORGANIZATION COMMITTED

TO DELIVERING THE HIGHEST LEVEL OF SERVICE

*SUMMARY INFORMATION*

ARRIVAL 12:00P WE 23JUN LHRT01 / RETURN 5:00P TH 24JUN

ECMN DESCRIPTION: REFER TO POLICY PAGE

ESTIMATED BASE RATE: 74.53 GBP

APPROX TOTAL COST OF RENTAL: 96.97 GBP

*RATE DETAIL*

BASE RATE INCLUDES: DAY/HOUR CHARGES

CDW TP

STATE TAX

APPROX TOTAL INCLUDES: BASE RATE PLUS TAXES AND SURCHARGES

DAILY: (* 2DY) 37.26 GBP UNL FM- .00MI

EXTRA DAY: (* XD) 35.77 GBP UNL FM- .00MI

EXTRA HOUR: (* XH) 43.77 GBP UNL FM- .00MI

RATE GUARANTEE PERIOD: 22APR04-22APR05

RATE CODE: VII - EASY EUROPE

RATE TYPE/CATEGORY: DAILY / STD/PROM

*TAXES*

STATE TAX

17.50 PERCENT - INCLUDED IN BASE RATE

*SURCHARGES / FEES AND OTHER REQUIRED CHARGES*

LOCATION SURCHARGE

17.00*GBP PER RENTAL - INCLUDED IN APROX TTL

REGISTRATION FEE

1.05*GBP PER DAY - INCLUDED IN APROX TTL

DELIVERY FEE

10.00*GBP PER RENTAL - INCLUDED IN APROX TTL

COLLECTION FEE

10.00*GBP PER RENTAL - INCLUDED IN APROX TTL

DELIVERY/COL FEE

15.00*GBP PER RENTAL - INCLUDED IN APROX TTL

* TAXES APPLY TO ALL CHARGES MARKED BY AN ASTERISK

*COVERAGE*

... (Truncated display example)

9.4 Focalpoint Non-IA Rules Display – Containing New Delivery Collection Alert

(Content shown underscored and bolded for clarification purposes only.)

** THRIFTY CARMASTER RULES DISPLAY **

*SUMMARY INFORMATION*

ARRIVAL 12:00P WE 23JUN ORDT01 / RETURN 5:00P TH 24JUN MKET01

ECAR5 DESCRIPTION: DAEWOO LANOS

ESTIMATED BASE RATE: 50.70 USD**ADDITIONAL DROP

**CHARGE MAY APPLY

*RATE DETAIL*

BASE RATE INCLUDES: DAY/HOUR CHARGES

DAILY: (* 2DY) 25.35 USD UNL FM- .00MI

EXTRA DAY: (* 0XD) 31.99 USD UNL FM- .00MI

EXTRA HOUR: (* 0XH) 10.66 USD UNL FM- .00MI

DROP CHARGE: AMOUNT NOT AVAILABLE- ADDL CHARGE MAY APPLY

RATE GUARANTEE PERIOD: 09APR04-09APR05

RATE CODE: 6510 - AUTOMATICALLY BOOKED WITH THIS RATE CODE

RATE TYPE/CATEGORY: DAILY / STANDARD

*TAXES*

TAXES ARE NOT INCLUDED IN BASE RATE AMOUNT

REFER TO LOCATION TAX POLICY >CADA12/TAX

*SURCHARGES / FEES AND OTHER REQUIRED CHARGES*

ADDITIONAL DELIVERY COLLECTION CHARGE MAY APPLY

*COVERAGE*

... (Truncated display example)

9.5 Focalpoint IA Rules Display – Containing New Delivery Collection Alert

(Content shown underscored and bolded for clarification purposes only.)

** VROOM INSIDE AVAILABILITY RULES DISPLAY **

** FOR ALL YOUR CAR RENTAL NEEDS...CALL ON VRRROOOOOM **

*SUMMARY INFORMATION*

ARRIVAL 12:00P WE 23JUN ORDT01 / RETURN 5:00P TH 24JUN MKET01

ECAR5 DESCRIPTION: DAEWOO LANOS

ESTIMATED BASE RATE: 50.70 USD

APPROX TOTAL COST OF RENTAL: 96.97 USD

*RATE DETAIL*

BASE RATE INCLUDES: DAY/HOUR CHARGES

DAILY: (* 2DY) 25.35 USD UNL FM- .00MI

EXTRA DAY: (* 0XD) 31.99 USD UNL FM- .00MI

EXTRA HOUR: (* 0XH) 10.66 USD UNL FM- .00MI

DROP CHARGE: AMOUNT NOT AVAILABLE- ADDL CHARGE MAY APPLY

RATE GUARANTEE PERIOD: 09APR04-09APR05

RATE CODE: 6510 - AUTOMATICALLY BOOKED WITH THIS RATE CODE

RATE TYPE/CATEGORY: DAILY / STANDARD

*TAXES*

TAXES ARE NOT INCLUDED IN BASE RATE AMOUNT

REFER TO LOCATION TAX POLICY >CADA12/TAX

*SURCHARGES / FEES AND OTHER REQUIRED CHARGES*

ADDITIONAL DELIVERY COLLECTION CHARGE MAY APPLY

LOCATION SURCHARGE

17.00*GBP PER RENTAL - INCLUDED IN APROX TTL

REGISTRATION FEE

1.05*GBP PER DAY - INCLUDED IN APROX TTL

*COVERAGE*

... (Truncated display example)

9.6 Viewpoint – PNR Display – Current Display

[pic]

9.6 Viewpoint – Itinerary Print – Current Display

[pic]

9.7 Viewtrip – Itinerary Display – Currrent Display

[pic]

9.8 Viewtrip – Electronic Expense Receipt – Current Display

[pic]

9.9 ITIN – Current and Proposed Changes to System Defaults

A. Current output with pick up and drop off at same location (airport)

15 MAY 04 - SATURDAY

HERTZ 1 INTERMED 2/4 DR DROP-17MAY CONFIRMED

PICKUP-CHICAGO/OHARE OHARE AIRPORT

RATE- 51.99 DAILY GUARANTEED EXTRA HR 26.00

MILEAGE-UNL/MI CODE-MCLS EXTRA DAY 76.99

CONFIRMATION-C51601420F1

B. Current output with off airport pick up (PUP-) and off airport drop off (DO) with a Drop off charge

18 MAY 04 - TUESDAY

ALAMO 1 INTERMED 2/4 DR DROP-19MAY CONFIRMED

PICKUP-CHICAGO/OHARE 203 N. LASALLE

DROP OFF- 1705 W JEFFERSON ST CHG-USD 10.00

RATE- 117.98 BASERTE GUARANTEED EXTRA HR 19.66-UN

MILEAGE-UNL/FM

PHONE-312-236-2581

CONFIRMATION-45276330

C. New layout option 1

18 MAY 04 - TUESDAY

ALAMO 1 INTERMED 2/4 DR DROP-19MAY CONFIRMED

PICKUP-CHICAGO/OHARE 203 N. LASALLE D/C CHG-USD 20.00 (74)

DEL ADDR-GALILEO HOUSE 123 MAIN ST

DROP OFF- 1705 W JEFFERSON ST CHG-USD 10.00

COL ADDR-TRAVEL 2 13 LAKE ST

RATE- 117.98 BASERTE GUARANTEED EXTRA HR 19.66-UN

MILEAGE-UNL/FM

PHONE-312-236-2581

CONFIRMATION-45276330

D. New layout option 2

18 MAY 04 - TUESDAY

ALAMO 1 INTERMED 2/4 DR DROP-19MAY CONFIRMED

PICKUP-CHICAGO/OHARE 203 N. LASALLE D/C CHG-USD 20.00 (74)

DROP OFF- 1705 W JEFFERSON ST CHG-USD 10.00

RATE- 117.98 BASERTE GUARANTEED EXTRA HR 19.66-UN

MILEAGE-UNL/FM

PHONE-312-236-2581

CONFIRMATION-45276330

DEL ADDR-GALILEO HOUSE 123 MAIN ST

COL ADDR-TRAVEL 2 13 LAKE ST

(Continue on next page)

E. New layout option 3

18 MAY 04 - TUESDAY

ALAMO 1 INTERMED 2/4 DR DROP-19MAY CONFIRMED

PICKUP-CHICAGO/OHARE 203 N. LASALLE D/C CHG-USD 20.00 (74)

DROP OFF- 1705 W JEFFERSON ST CHG-USD 10.00

DEL ADDR-GALILEO HOUSE 123 MAIN ST

COL ADDR-TRAVEL 2 13 LAKE ST

RATE- 117.98 BASERTE GUARANTEED EXTRA HR 19.66-UN

MILEAGE-UNL/FM

PHONE-312-236-2581

CONFIRMATION-45276330

F. New layout option 4

18 MAY 04 - TUESDAY

ALAMO 1 INTERMED 2/4 DR DROP-19MAY CONFIRMED

DEL ADDR-GALILEO HOUSE 123 MAIN ST

COL ADDR-TRAVEL 2 13 LAKE ST

PICKUP-CHICAGO/OHARE 203 N. LASALLE D/C CHG-USD 20.00 (74)

DROP OFF- 1705 W JEFFERSON ST CHG-USD 10.00

RATE- 117.98 BASERTE GUARANTEED EXTRA HR 19.66-UN

MILEAGE-UNL/FM

PHONE-312-236-2581

CONFIRMATION-45276330

Interface Document Details:

Four new fields will be enabled for CarMaster sell/modify processing.

/DEL-max 60 characters freeform text representing a delivery address.

/COL-max 60 characters freeform text representing a collection address.

/DCC-max 11 characters freeform text representing a delivery/collection charge.

/BR-max 25 characters freeform text representing a billing reference number.

Ex. 0CARXXNN1DEN12AUG-14AUGECAR/ARR-1P/DT-1P/DEL-DELIVER IT HERE/COL-COLLECT IT HERE/BR-12345678

For the Type A message sent to / from CarMaster, input field identifiers will be translated into a two-character CarMaster Inside Link message standard:

DEL- will be translated to DE

COL- will be translated to CO

BR- will be translated to BR

DCC- will be translated to DF

There will be 2 new switches in the Universal Access processing which enable the agent to use these fields for a given car supplier. The first switch will control if the supplier can accept /DEL, /COL and /DCC. The second switch will control if the supplier can accept /BR. If the appropriate switch is not on for the car company being sold, the agent will receive an error message stating that the qualifier is not valid with the car company being sold.

The Car supplier will have the option of returning a DE, CO and/or DF field that will replace the /DEL, /COL and/or /DCC (respectively) previously stored in the car segment.

Only the Car supplier can update the /DCC field in the booking. The agent will be restricted from attempting a sell or modify which includes this qualifier.[pic]

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

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

Google Online Preview   Download