ࡱ> q bjbjt+t+ ;AA]""""8ZT"nA|^ " 4V V V q ?( K,8888W8"<"A$BDAA-S.C.qS.S.AA1V V ^ 111S.V V 8""S.81,17%8S8V r@(3^w""0x8 Functional Specification Inside Link Cars Distribution NameDepartmentSYMBOL 227 \f "Symbol" Copyright Galileo International Partnership savedate \@ "yyyy"1998 Filename: filename Inside Link Cars Styleguide: FNSPEC-1 Author: author Corporate Network Services Owner: fillin "Enter name of owning department" Issue: fillin "Enter issue status and version number"Draft 0 Number of Pages: numpages 34 Table of Contents  TOC \o "1-2" Approval  PAGEREF _Toc424442184 \h 3 1.0 Introduction  PAGEREF _Toc424442185 \h 4 1.1 Inside Link Objectives  PAGEREF _Toc424442186 \h 4 1.2 Application Functions  PAGEREF _Toc424442187 \h 4 1.3 Inside Link Car Special Requirements/Restrictions  PAGEREF _Toc424442188 \h 4 2.0 Functional Detail  PAGEREF _Toc424442189 \h 5 2.1 Segment Sell  PAGEREF _Toc424442190 \h 5 2.2 Segment Sell Requirements/Restrictions  PAGEREF _Toc424442191 \h 5 2.3 Agent Sell Inputs  PAGEREF _Toc424442192 \h 6 2.4 Direct Sell  PAGEREF _Toc424442193 \h 6 2.5 Reference Sell  PAGEREF _Toc424442194 \h 7 2.6 Combination Sells  PAGEREF _Toc424442195 \h 8 2.7 Segment Sell Process  PAGEREF _Toc424442196 \h 8 2.8 Universal Access Validation Table  PAGEREF _Toc424442197 \h 9 2.9 The Car Vendors Computer System  PAGEREF _Toc424442198 \h 10 2.10 Segment Sell Apollo Output  PAGEREF _Toc424442199 \h 11 3.0 Cancel Segment or Itinerary Containing a Car Segment  PAGEREF _Toc424442200 \h 12 3.1 Segment Cancel Requirements/Restrictions  PAGEREF _Toc424442201 \h 12 3.2 Agent Cancel Segments  PAGEREF _Toc424442202 \h 12 3.3 Segment Cancel Process  PAGEREF _Toc424442203 \h 12 3.4 The Car Vendors System  PAGEREF _Toc424442204 \h 13 3.5 Segment Cancel Apollo Output  PAGEREF _Toc424442205 \h 13 4.0 Ignore Apollo Session Containing a Car Segment  PAGEREF _Toc424442206 \h 14 4.1 PNR Ignore Requirements/Restrictions  PAGEREF _Toc424442207 \h 14 4.2 Agent Ignore Inputs  PAGEREF _Toc424442208 \h 14 4.3 Inside Link Session Ignore Progress  PAGEREF _Toc424442209 \h 14 4.4 The Car Vendors System  PAGEREF _Toc424442210 \h 15 4.5 PNR Apollo Ignore Output  PAGEREF _Toc424442211 \h 15 5.0 Modify a Car Segment  PAGEREF _Toc424442212 \h 16 5.1 Segment Modification Requirements/Restrictions  PAGEREF _Toc424442213 \h 16 5.2 Apollo Agent Modify Inputs  PAGEREF _Toc424442214 \h 16 5.3 Segment Modify Process  PAGEREF _Toc424442215 \h 17 5.4 The Car Vendors System  PAGEREF _Toc424442216 \h 18 5.5 Segment Modify Apollo Output  PAGEREF _Toc424442217 \h 18 6.0 End Transact Apollo Session Containing a Car Segment  PAGEREF _Toc424442218 \h 19 6.1 End Transact Requirements/Restrictions  PAGEREF _Toc424442219 \h 19 6.2 Agent End Transact Inputs  PAGEREF _Toc424442220 \h 19 6.3 Inside Link End Transact Process  PAGEREF _Toc424442221 \h 19 6.4 The Car Vendors Sytem  PAGEREF _Toc424442222 \h 20 6.5 PNR End Transact Apollo Output  PAGEREF _Toc424442223 \h 20 7.0 Application Environment  PAGEREF _Toc424442224 \h 21 Appendix I  PAGEREF _Toc424442225 \h 22 Appendix II Technical Summary  PAGEREF _Toc424442226 \h 25  Approval NameTitleDate 1.0 Introduction The purpose of Car Vendor Direct Access is to provide last car availability by processing the sell segments within the car vendor's computer system. The confirmation number is displayed to the agent as part of the sell response prior to End transact. As a result, an agent is able to sell all car types at all locations and receive confirmation of car reservations instantly. 1.1 Inside Link Objectives Establish a direct access computer link between Apollo and a car vendor's computer system in order to improve accuracy and timeliness when booking a car. 1.2 Application Functions SYMBOL 183 \f "Symbol" \s 10 \h Provide the ability to access last car availability when booking a car segment. SYMBOL 183 \f "Symbol" \s 10 \h Provide a confirmation number at the time of booking as part of the sell response. SYMBOL 183 \f "Symbol" \s 10 \h Provide the ability to sell all car types at both on and off airport locations. SYMBOL 183 \f "Symbol" \s 10 \h Provide these functions using standard Apollo formats and procedures. 1.3 Inside Link Car Special Requirements/Restrictions Data transmitted from a car vendor's computer system to Apollo via direct access is limited to a maximum of 960 characters. When the direct access link is down, processing continues as it does today with data being transmitted between systems via teletype. Car booking messages entered by UA agents are transmitted via the direct access link. 2.0 Functional Detail 2.1 Segment Sell Provide travel agents the ability to reference or direct sell car segments via the direct access link utilizing the Computer-to-Computer Link Last Car Availability functionality. This sell results in an instant confirmation number response from the car vendor which is displayed to the agent as an addition to the existing sell response. 2.2 Segment Sell Requirements/Restrictions Booking entries input by travel agents and United agents are processed via the direct access link. Standard Apollo car segment sell procedures and inputs are utilized. Apollo edits the car type for four alpha characters. Availability for that car type is determined in the car vendor's computer system. Link processing can be restricted if a vendor specific critical validation item fails during MVS validation processing (Universal Access). Availability for the car types contained within Apollo is determined within the car vendor's computer system even when Apollo shows the car type unavailable. A sell request for multiple cars is not sent via the direct access link, but is sold within Apollo and sent via teletype at End transact. The message 'MULTIPLE CARS NOT SOLD VIA LINK' is returned to the CRT. Individual sell messages should be entered if instant confirmation numbers are required. Arrival data is required to enable a car vendor to generate an instant confirmation number. This data can be retrieved from the preceding air segment or from the optional /ARR field input by the agent. The error message 'NEED ARRIVAL TIME' is sent to the CRT if arrival information is not available. The /ARR field stored in the PNR should be entered as follows: /ARR-time-flight information. Either twelve or twenty-four hour clock format is accepted. Apollo sends the time to the vendor in twenty-four hour format. Flight data contained in the arrival field can be up to seven characters and is not be edited. Flight data is optional. The error message 'CHECK ARRIVAL DATA' is displayed if a format error exists in this field. Arrival information obtained from the previous air segment is not stored in the /ARR field of the PNR. Only the arrival information stored in the PNR is displayed to the agent. Name data is required to generate an instant confirmation number. Entry of the PNR name is required prior to entering the car segment sell. The error message 'NEED PNR NAME (LINK MESSAGE)' is displayed if this data is not available at the time of the sell entry. If a customer identification number is input, it is sent to the car vendor along with the name field. Bookings containing a customer ID number are always sold in the car vendor's computer system for the name contained in their customer ID file. If no match is found for the customer ID number, an error message is returned to the agent. If a United agent books a car segment, the referral source field (RS) contains the two characters 'UA' followed by the three character pseudo city code. The 'TC' field also contains 'UA'. If a travel agent sells a car segment, the referral field contains the 'UA' followed by the pseudo city code. The 'TC' field contains the travel agency eight digit ARC number and a vendor assigned ID number if the travel agent inputs one. The format is: '/BS-.18SA838281' up to a maximum of ten alpha-numeric characters. If a '/PUP' field is entered by the agent to reflect a location other than the airport, it is sent to the car vendor's computer system in place of the airport city. The travel agency phone number is sent to the car vendor's computer system as part of the sell message. A United phone number is not included if a United agent makes the booking. To request express service if not automatically setup in the customer's ID profile, the agent must input the customer ID number followed by '-EXP'. If a format error exists in this field, the error message 'INVALID EXPRESS SERVICE FORMAT' is sent to the CRT. 'EXP' is returned from the car vendor's computer system attached to the confirmation number, i.e.: ID12345678901EXP and displayed to the agent as CF-12345678901EXP. In order to bypass express service reflected in the customer ID profile, -'NOEXP' is entered following the customer id number. If the car vendor's system returns a response indicating that the car is on request, the segment is sold within Apollo with an 'NN' status code and a message 'CAR ON REQUEST *'. At the vendor's request, the transaction can be sent to the vendor's system via teletype at End transact (ET). Sell requests with an 'HK' or 'BK' action code do not go across the direct access link as these action codes indicate that a car has already been confirmed with the car vendor's computer system. Sell requests with a 'MO' action code (manual override) go across the direct access link. Change segment status (.2HK) is not allowed for link confirmed segments. An error message is returned from Apollo if attempted. Teletype out messages to the car vendor's system do not contain any reference to segments sold via the direct access link during the current conversation. 2.3 Agent Sell Inputs There are several procedures an agent may use for selling a car segment: direct sell, reference sell and selling in combination with a cancel/rebook or with inserting after an existing segment. 2.4 Direct Sell The direct segment sell entry allows the agent to book a car reservation by including all the required and optional data fields in one entry. ENTRY: 0:CARXXNN1DEN13OCT-15OCTICAR/ARR-8A  Segment Sell Identifier Arrival Time Apollo Car Segment ARR Field ID Car Vendor Optional Fields Delimiter Current Status Code Car Type Number of Cars Drop-off Date Airport/City of Service Pick-up Date Current status code is optional. It defaults to NN1. Drop-off date is optional. Default is 1 day after input. Airport city and pick-up date fields are optional if a previous air segment exists. If a previous air segment does not exist, 'NO ITIN' is the error response sent to the CRT. Following are examples depicting various options if a previous air segment exists. ENTRY: Sell an ICAR car type. Airport city and pick-up date is retrieved from previous air segment. 0:CARXXICAR ENTRY: Sell the same as above with the additional optional drop-off date field. 0:CARXX-1DECICAR If a previous air segment does not exist, 'NO ITIN' is the error response displayed to the CRT. 2.5 Reference Sell The reference sell entry allows an agent to quickly convert car availability information into an itinerary segment. A car availability entry must first be input. The line number of the desired car type and the column letter of the desired car vendor from the availability display, plus any additional optional information, are entered as part of the reference sell message. The number of cars to be sold defaults to one if that field is omitted. Reference the following examples: ENTRY: Sell one car from column A and line 2 01A2  Line Number of Car Type Column Letter of Vendor Number of Cars Segment Sell Identifier ENTRY: Sell one car from column B, line 3, returning car on Dec 24. 0B3-24DEC Pick-up date and airport code is retrieved from the availability display previously requested as depicted in the examples above. For both of the segment sell formats there are optional fields which can be entered as part of the sell request. These fields can be included in any combination: RT - Rate Field BS - Booking Source W - Address for written confirmation ID - Customer identification number PUP - Pick-up if other than airport DO - Drop-off point if other than pick-up location ARR - Arrival time and date IT- - Tour number CD - Corporate ID Code SI - Special information RC - Rate Identification Code FT - Frequent Traveler SQ - Special Equipment Code NM - Name field CF - Confirmation number DL - Driver's License number EXP - Express Service indicator G - Credit Card number R - Pre-payment data DT - Drop Time SI-PC - Promotional Code (Hertz only) SI-AUTH - Authorization (Hertz only) 2.6 Combination Sells The direct and reference sells can be used in conjunction with a cancel/rebook entry or an insert after input message. Optional fields may be included. Reference the following examples: ENTRY: Cancel segment 3 and rebook with new data. X3/0CARXX17OCT-19OCTICAR/SI--DESIRES RED CAR ENTRY: Insert car sell after segment 2 in AAA. /2+01B3-23MAR/ID-22222/SI-DESIRES COUGAR 2.7 Segment Sell Process Apollo The existing car package is used for input message editing and validation. All existing error responses are used in this editing process. Prior to sending a car sell across the link the following checks are performed: Is vendor eligible for direct access? Is the link available? Is requested transaction supported via the direct access link? Is agency allowed to utilize the Last Car Availability function? Universal Access uses the routing indicator sent from the car package to route the request to MVS Database, Links or Both (M, L or B). When the 'Both' routing indicator is requested, the sell first processes in MVS and then the TPF validation utility compares the MVS validation response to the vendor specific critical validation data (GA12N). Then if no critical validation data is flagged, processing continues across the Link to the vendor else, the MVS response is displayed to the agent. Universal Access also merges MVS response data to the Link vendor response block. Both the rate code (/RC) and rate (/RQ or /RG) is merged to the link vendor response if not receive from the link vendor. If one of these checks is not met processing continues within Apollo. If the sell was for a car type not available within Apollo the sell is completed with a 'NN' status code. If all checks were met, the arrival time, carrier code and flight number are retrieved from the previous air segment in the PNR if one exists. If there is no air segment and no 'ARR' field has been entered by the agent, the error response 'NEED ARRIVAL DATA' is issued to the agent requesting arrival information. A check is made for the PNR name. If not found, the message 'NEED PNR NAME (LINK MESSAGE)' is displayed to the agent. A check is made for the ID field. A car vendor uses this number to access their customer ID file for the car rental reservation. If not input, the name is retrieved from the PNR name field so it can be sent to the car vendor. 2.8 Universal Access Validation Table The following is a list of items included in the CarMaster Validation Table and information pertaining to what these items are validated against in MVS. An item is considered to be critical for a specific Link vendor if its bit in the GA12N record is set on or to 'Yes'. List of fields to be validated (GA12N): advance booking requirement minimum rental requirement maximum rental requirement hours of operation early pick-up time failed late pick-up time failed car type invalid rate not available (closed) rate code invalid pick-up location invalid The Advance Booking Requirement is validated against the advance booking field in the rate record. If the time from booking to pick-up time is less than allowed for the particular rate this flag is set. The Minimum and Maximum Rental Requirements are validated against the pick-up/return rule (if no rule found it is validated against the pick-up/return policy). The edit verifies if the total number of days for the rental attempt falls within the boundaries set in the pick-up/return rule. The Hours of Operation Failed Indicator is checked against the hours policy of the pick-up location. If the location is not open at pickup time this indicator is be set. The Early and Late Pick-Up times are validated against the pick-up/return rule or policy. If the arrival time is earlier than the earliest pick-up or later than the latest pick-up time one of these indicators is set. Car Type Invalid validates if the requested car type exists for the location. If it does not, this indicator is set. Rate Code Invalid for the requested car type: if no rate is found with the specified rate code, this indicator is set. Invalid Pick-up Location: If the requested pickup location is not found this indicator is set. Once the necessary data fields have been obtained, they are formatted into a message and sent to the vendor system. Reference following examples: Apollo: 0A4 (Sell 1 intermediate car) to VENDOR: V/NMHOPE BOB/DA25MAY/TA1530/CYDEN/VTICAR/FLUA1125 Apollo: 0B5-30MAY/ID-2573689/SI-CONVERTIBLE to VENDOR: V/DA25MAY/RD30MAY/TA0945/CYLAX/VTSCAR/FLUA0725 /F1CONVERTIBLE/NO2573689 If the direct access link is not available, the message is returned to Apollo to be processed within Apollo as it is today, if possible. In some situations, an error response of 'XX ACCESS NOT AVAILABLE' may be displayed. 2.9 The Car Vendors Computer System The car vendor's system verifies that the format of the input message is correct and that all required data is present. If all required checks are met and the car type is available, the car vendor's system returns a confirmation number to indicate that the booking has been made. If any error conditions are encountered by the car vendor's system while attempting to build the reservation record, an error code or message is returned to Apollo. Upon completion of processing, the car vendor's system returns a response indicating that either the reservation was processed successfully or unsuccessfully. The response from the car vendor's system is analyzed by Apollo to be displayed to the agent's CRT. VER/ID12341234567EXP/NFHOPE BOB Apollo If the sell request was successfully processed by the car vendor's system, the car sell response is displayed on the agent's screen. The confirmation number and asterisk appears on the last line of the display to indicate that the segment was sold over the direct access link and has been confirmed. If the optional field /RC is input followed by a rate code and the car vendor's system has the capability of returning rates, a rate display preceded with a /RQ is displayed as shown below. If an error is encountered during processing within the car vendor's system, an error response is displayed on the screen followed by an asterisk to indicate that the error was identified by the car vendor's system. Apollo displays multiple error responses if returned from the car vendor's system. 2.10 Segment Sell Apollo Output RESPONSE: 1 CCR XX SS1 DEN 7MAR - 10MAR SCAR/BS-UA/ID-123456 /NM-HOPE BOB /RQ-USD149.00WK-UNL MI XD35.00DY-UNL MI (up to 50 characters) /CF-45678123456 * Sell response with the confirmation number and asterisk reflecting the car segment was sold over the direct access link. RESPONSE: INCORRECT RENTAL CITY CODE * Error response with an asterisk showing that the error was identified in the car vendor's system. For multiple error responses, each appear on a separate line with an asterisk appended only on the last line. 3.0 Cancel Segment or Itinerary Containing a Car Segment Provide Apollo travel agents the ability to cancel car segments sold via the Computer-to-Computer Link function. Only segments that have been confirmed by the vendor can be canceled via the link. All other cancels go via teletype as Type B traffic. 3.1 Segment Cancel Requirements/Restrictions Standard Apollo cancel segment/itinerary procedures and inputs apply to direct access cancellations. The confirmation number is passed as part of the cancellation message for each car segment sold via the direct access link. A cancellation message for multiple car segments (XI or X2-4) generates multiple cancellation messages to the car vendor's system. Each message contains the confirmation number for that segment. When the car vendor's system receives the cancellation request, the booking record is not canceled until Apollo sends the End transact message. A segment sold via the link and then canceled from the PNR is sent via the link due to the existence of the confirmation number. This is true whether the cancel is for a segment sold during the current PNR session or for a segment from a retrieved PNR. Cancellations for segments sold via teletype are sent via the link if a confirmation number exists. 3.2 Agent Cancel Segments ENTRY: X2 Cancel segment 2 ENTRY: XI Cancel itinerary 3.3 Segment Cancel Process Apollo The current cancel segment package is utilized to perform message editing and validation. All existing error responses are used in this editing process. Several checks are made to verify validity of transmitting this message across the direct access link: Is the cancel request for a vendor with a direct access session in progress? Is the vendor eligible for direct access? Is the requested transaction supported via the direct access link? Is the agency allowed to utilize the Last Car Availability function? Once the necessary checks have been made, a message is formatted and passed to the Vendor system Apollo: X2 X/ID12345678901 If the link is unavailable the cancel request is sent teletype to the Vendor system. The segment number is not sent to the car vendor's system as the confirmation number is sufficient for identification of the car segment. Cancellation of multiple car segments in Apollo results in multiple cancel messages being sent to the car vendor's system. 3.4 The Car Vendors System The following message is transmitted to the vendor system to indicate the booking has been canceled. CAN/ID12341234123/NFCLIENT NAME If any errors are encountered by the car vendor's system, the appropriate error message is returned. The response from the car vendor's system is returned to Apollo where it is determined whether the response was successful. If an error response is received, Apollo sends the message via Type B teletype. There is no response to the agent as a result of the error. Apollo The CRT does not wait for a response from the car vendor's computer system. Apollo displays a response that the segment has been canceled and the CRT is available for other entries. 3.5 Segment Cancel Apollo Output Apollo always displays the following message: RESPONSE: NEXT REPLACES X Where X = the number of the canceled segment 4.0 Ignore Apollo Session Containing a Car Segment If car segments have been sold/modified/canceled across the direct access link during a current PNR session in Apollo and that session is ignored, a message is sent to ignore the updates to the corresponding records in the car vendor's system. 4.1 PNR Ignore Requirements/Restrictions Standard Apollo PNR ignore procedures and inputs apply to Direct Access PNR ignores. An ignore message must be sent for each car segment which has been sold/canceled/modified during the current session versus a single ignore message for all segments. Thus, if an existing car segment is canceled and a new segment is sold, an ignore entry generates an ignore transaction for the new car segment and one for the canceled segment. Once an ignore has been entered and no further bookings or modifications have been input for that PNR, no End transact message is required. 4.2 Agent Ignore Inputs ENTRY: I or IGN (programmed function key) 4.3 Inside Link Session Ignore Progress Apollo The existing ignore package is entered to perform message editing and validation. All existing error responses are used in this editing process. Several checks are made to verify validity of transmitting this message across the direct access link: Is the ignore request for a vendor with a direct access session in progress? Is the vendor eligible for direct access? Is the requested transaction supported via the direct access link? Is the agency allowed to utilize the Last Car Availability function? A determination is made as to which car segments are affected during the session and therefore how many ignore messages need to be sent. Once the necessary checks have been made, the message is formatted and passed to the vendor system (one for each car segment). Apollo: I (ignore Apollo PNR session) to VENDOR: I/ID12341234567 An ignore message is a must go transaction. If the link to the car vendor's system is not available, the message is queued until communication is restored. An ignore message is created for each car segment affected during the current session. Therefore, one ignore entry in Apollo may result in multiple ignore messages being sent to the car vendor's system. 4.4 The Car Vendors System A booking record resides for each of the car segments that were sold/modified/canceled during the current session. A match is found on the confirmation number and the booking record. The following message is sent back to Apollo to indicate this action has taken place: IGN/ID12341234567/NFCLIENT NAME If an error is encountered by the car vendor's system, the appropriate error message is returned. Apollo The response from the car vendor's system is returned to Apollo where it is determined if an error condition was identified. Four additional attempts will be made to send the message. If all five tries receive an error response no further action is taken. No response is sent to Apollo as a result of an error. Since ignore is considered a 'must go' type of message, the CRT does not wait for a response from the car vendor's system. Apollo displays an ignore response and the CRT is available for other entries. 4.5 PNR Apollo Ignore Output Apollo always displays the following message: RESPONSE: 'IGND' 5.0 Modify a Car Segment Frequently, there is a need to alter an existing car segment. Various fields within the car segment can be added, modified or deleted. These include dates, car type and all the optional fields to an existing car segment or a car segment in a retrieved PNR. Modifications made to car segments sold either across the direct access link or with a programmatically appended confirmation number, are sent across the direct access link. 5.1 Segment Modification Requirements/Restrictions Standard Apollo procedures and inputs apply to all car modifications which are sent across the direct access link. Deletion of the confirmation number of a link sold segment is not allowed. Link processing can be restricted if a vendor specific critical validation item fails during MVS validation processing (Universal Access). Modifications to a car segment sold via the direct access link or the teletype link are sent via the direct access link if a confirmation number is present. If the modification is successful, the segment is marked as a segment sold via the link. If the confirmation number is invalid, the travel agent may need to call the car vendor. An agent may modify the /NM field. A delete entry for the pick-up field (CAM1X/PUP) generates a modification for the rental city to change to the arriving airport code. If the drop-off field is deleted, the car vendor's system automatically changes the drop-off point to the pick-up location. A modification to an air segment does not change the 'ARR' field which was entered by the agent. If a modification entry is input and the link is down, Apollo modifies the car segment in the PNR and sends it via teletype to the car vendor's system at End transact. If the link is brought up prior to End transact and additional modifications are made to the same car segment, they do not go across the direct access link. These modifications are also reflected in the PNR and are sent to the car vendor's system via teletype at ET. The car vendor's system assumes the teletype is complete and correct and finalizes the booking accordingly. Once a modification has successfully been entered, an End transact message confirms this action with the car vendor's system. An ignore message returns the status in both Apollo and the car vendor's system to that prior to the creation of the car segment if in current session or to that of the original PNR when it was first retrieved. If the '/ID' field is deleted, the '/NM' field is deleted programmatically. The PNR name needs to be sent to the car vendor at that point. 5.2 Apollo Agent Modify Inputs The following examples depict date and car type changes. ENTRY: CAM2D/25MAY-29MAY Modify dates for segment 2 ENTRY: CAM4T/ICAR Modify car type for segment 4 The optional fields for a segment can be added, modified or deleted. Any combination of the fourteen fields can be modified in a single entry or they can all be modified at once. Only the optional data of the car segment can be deleted, with the exception of the booking source. This field can be modified but not deleted. The format is as follows: ENTRY: CAM3X/G Delete the ID information for segment 3 ENTRY: CAM2X/W/SI Delete address and special information The above examples would generate a message of '/GDXXX' and '/ADXXX/F1XXX' respectively. 5.3 Segment Modify Process Apollo The existing segment modification package is entered to perform message editing and validation. All existing error responses are used in this editing process. Universal Access then uses the routing indicator sent from the car package to route the request to the MVS Database, Links or Both (M, L or B). When the 'Both' routing indicator is requested, the sell first processes in MVS and then the TPF validation utility compares the MVS validation response to the vendor specific critical validation data (GA12N). Then if no critical validation data is flagged, processing continues across the Link to the vendor else, the MVS response is displayed to the agent. Universal Access also merges MVS response data to the Link vendor response block. Both the rate code ('/RC') and rate ('/RQ' or '/RG') is merged to the link vendor response if not receive from the link vendor. Several checks are made to verify validity of transmitting this message across the direct access l ink: Is the change request for a vendor with a direct access session in progress? Is the vendor eligible for direct access? Is the link available? Is the requested transaction supported via the direct access link? Is the agency allowed to utilize the Last Car Availability function? Once the necessary checks are made, the message is formatted and passed to the Vendor system. Apollo: CAM3T/ECAR to VENDOR: C/ID12345678901/VTECAR If the link to the car vendor's system is not available, the message is returned to Apollo to be processed within Apollo. The segment number is not sent to the car vendor's system as the confirmation number is sufficient for identification of the car segment. If the modification is to a retrieved PNR, the message sent to the car vendor is preceded by a 'P/' instead of a 'C/'. Apollo: CAM2T/ICAR to VENDOR: P/ID12345678901/VTICAR If the modification is to the SI field, a maximum length of 90 characters is allowed in Apollo. Apollo: CAM20/SI-DESIRES A FLASHY............(90 chars.) 5.4 The Car Vendors System If any errors are encountered by the car vendor's system, the appropriate error message is returned. Apollo If the change request is successfully processed by the car vendor's system, the modify response is displayed on the agent's screen. If the modification results in a new booking, the new confirmation number and asterisk appears on the last line of the modify display to indicate that the segment has been sold over the direct access link and is confirmed. If an error is encountered during processing within the car vendor's system, an error response is displayed on the screen followed by an asterisk to indicate that the error was identified by the car vendor. Apollo displays multiple error responses if returned from the car vendor's system. 5.5 Segment Modify Apollo Output RESPONSE: SEGMENT 2 NOW /SI-DESIRES CONVERTIBLE /NM-JONES T /CF-12345678901 * Modification response for which the original booking was updated. RESPONSE: SEGMENT 2 NOW /ARR-3A-UA222 /NM-JONES T CF-98765432109 * Modification response for which a new booking was generated. The display reflects the new confirmation number assigned by the car vendor's system. 6.0 End Transact Apollo Session Containing a Car Segment Since all of the required data has been sent to the car vendor's system at the time of the sell, a teletype message containing the PNR is not sent at End transact either via direct access or teletype. An End transact message containing the confirmation number and the PNR record locator is sent to the car vendor's system via direct access when the session is complete. 6.1 End Transact Requirements/Restrictions Standard Apollo End transact procedures and inputs apply to Direct Access End transacts. The car vendor's confirmation number is passed as part of the End transact message for each car segment sold via the direct access link during the current conversation. An End transact message for multiple car segments generates multiple ET messages to the car vendor's system. Each message contains the confirmation number for that segment and the Apollo record locator for the PNR. End transact messages are sent across the direct access link for car segments sold/modified via the direct access link which have not been ETd previously. Car segments not sold/modified across the direct access link are formatted into a teletype message and sent via Type B teletype. Modifications to associated air segments are transmitted via teletype as it is today. 6.2 Agent End Transact Inputs ENTRY: E or ET or ER 6.3 Inside Link End Transact Process Apollo The current End transact package is utilized to perform message editing and validation. All existing error responses are used in this editing process. Several checks are made to verify validity of transmitting this message across the direct access link: Is the End transact request for a vendor with a direct access session in progress? Is the vendor eligible for direct access? Is the requested transaction supported via the direct access link? Is the agency allowed to utilize the Last Car Availability function? Once the necessary checks have been made, the message is formatted and passed to the Vendor system. Apollo: E to VENDOR: E/ID12345678901/VN3A18NO Since End transact is a must go transaction, it is queued if the link is unavailable. Once communication is restored, the ET message is sent to the car vendor's system. An ET involving multiple car segments in an Apollo PNR results in multiple ET messages being sent to the car vendor's system. 6.4 The Car Vendors Sytem The End transact is processed and the reservation is placed in sold or canceled status as requested. The following message is sent back to Apollo to indicate this action has taken place: CON/ID12341234567/NFCLIENT NAME If any errors are encountered by the car vendor's system, the appropriate error message is returned. Apollo The response from the car vendor's system is returned to Apollo where it is determined whether the response was successful. If an error response is received, two more attempts is made to transmit the message. If all three tries receive an error response, Apollo needs to determine how to end the session. There is no response to the agent as a result of the error. Since End transact is considered a 'must go' type of message, the CRT does not wait for a response from the car vendor's system. Apollo displays a response that the PNR has been finalized and the CRT is available for other entries. 6.5 PNR End Transact Apollo Output RESPONSE: EOK-3A18NO Where 3A18NO = the PNR Record Locator 7.0 Application Environment System Availability This application must be available during all Apollo up-times, 24 hours a day, 7 days a week. Standard Apollo up-time requirements for Computer-to-Computer Link applications must be met. Standard Apollo reliability requirements must be met. Response Time/Throughput Standard Apollo response time for Computer-to-Computer Link applications of 3 to 5 seconds must be met. Hardware To be determined on a per car vendor basis. Acceptance Criteria The following functional areas are included in the testing: All sell, cancel, modify, ignore and End transact entries involving car segments utilize standard Apollo inputs. Arrival information, when manually entered in the '/ARR' field, must contain the arrival time and method of transportation in that order. Arrival time is accepted in either 12 or 24 hour clock. A rental location code in the '/PUP' field overrides the airport code in the car segment and is generated out as the rental city. Selling a car segment via direct access builds a reservation record in the car vendor's system. The car vendor responds with a confirmation number and asterisk appended to the sell response in Apollo. If a customer ID number is used in the car segment sell, the car vendor returns the name associated with that number as part of the response. The name is stored in the '/NM' field as part of the car segment. It may differ from the PNR name. Multiple car requests in a single car segment are not sent via direct access but default to normal teletype processing. The standard Apollo response time of 3 to 5 seconds is required. The application is not to be implemented until the testing criteria have been satisfied. Appendix I Special Equipment Codes 2DR - 2 DOOR CAR 4DR - 4 DOOR CAR AIR - AIR CONDITIONING AUT - AUTOMATIC TRANSMISSION CBR - CITIZEN BAND RADIO CNV - CONVERTIBLE CSS - CHILD SAFETY SEAT CSI - INFANT SAFETY SEAT EXP - EXPRESS SERVICE HCL - HAND CONTROL ON LEFT HCR - HAND CONTROL ON RIGHT LUG - LUGGAGE RACK MAN - MANUAL TRANSMISSION PHN - CAR PHONE SCH - SNOW CHAINS SKI - SKI RACK TRH - TRAILER HITCH ROD - ROOF RACK Car Types EMAN - ECONOMY MANUAL E0CAN - ECONOMY AUTOMATIC CCAR - COMPACT CAR ICAN - INTERMEDIATE CAR FCAR - FOUR DOOR CAR PCAR - PREMIUM CAR SCAR - STANDARD CAR LCAR - LUXURY CAR CWGN - COMPACT WAGON EWGN - ECONOMY WAGON IWGN - INTERMEDIATE WAGON SWGN - STANDARD WAGON 0XFWD - 4 WHEEL DRIVE XCNV - CONVERTIBLE XVAN - VAN XJEP - JEEP XMIN - MINI VAN Error Messages An error message begins with 'ERR/ 'or 'OFF/' and may or may not contain a name field. Error messages may be returned as pre-assigned error numbers or as vendor formatted text. ERR/ID12341234567/NFCLIENT NAME/ERR023037078 OFF/ID12341234567/NFCLIENT NAME/xxxxxxxxxxxxx Following are examples of error responses that may be displayed to the Agent. See Appendix for exact list. SYSTEM UNAVAILABLE ** IATA/ARC NUMBER INVALID CLIENT NAME MISSING RENTAL CITY MISSING MUST CANCEL AND SELL NEW RESERVATION CAR TYPE MISSING PICKUP DATE MISSING ** Message not sent to Agent; Apollo marks session as timed out. Warning Messages A warning message begins with 'WAR/' and must contain the confirmation number and name field. Warning messages may be returned as pre-assigned error numbers or as vendor formatted text. Return of a warning message is interpreted as a good sell (the car is booked) with either warning or informational messages to be appended on the original display only. These messages are not stored by Apollo following the display. This return can also be utilized for marketing messages. In order for the Apollo system to identify the text message, the characters '/MSG/' must follow the client name and precede the text which Apollo is to display. WAR/ID12341234567/NFCLIENT NAME/ERR023037078 WAR/ID12341234567/NFCLIENT NAME/MSG/xxxxxxxxx Message Queuing No change from current environment. Car Segment Display on Itinerary/Invoice No change from current environment. Billing Car Vendor for Apollo Bookings No change from current environment. Teletype-Out Overview The teletype system as it is used for Apollo Cars functionality will continue to be utilized as a backup method when the direct access link is not available. There are also be other specific instances already identified in this document when data will need to be transmitted via teletype. Teletype-In Overview No change from current environment. Type B Teletype is utilized as backup when the link is down. Session Control and Termination Summary The number of transaction control records (TCRs) to be allocated in Apollo to control the direct access sessions is determined on a per vendor basis. Appendix II Technical Summary Handshake Apollo sends the characters UA, a blank and a question mark. Ab? Action Codes Apollo to Vendor TRANSACTION CODE Sell SV Modify new PNR SC Modify retrieved PNR SP Cancel SX Ignore SI End transact SE Action Codes Vendor to Apollo TRANSACTION CODE Sell completed SVER Sell completed with warning msg SWAR Modify completed SCHG Cancel completed SCAN Ignore completed SIGN End transact completed SCON Error condition - number follows SERR Error condition - text follows SOFF Code Definition and Length AGENT ENTRY LNK CODE MAX LENGTH FIELD CF- ID 25 Confirmation number CY 10 Rental city PUP- CY 10 Rental city DA 5 Pickup date RD 5 Return date VT 5 Vehicle type RS 6 Referral source BS- TC 20 Booking source PH 20 Agency phone number ARR- TA 5 Pickup time ARR- FL 7 Inbound Flight information FO 7 Outbound Flight information RC 10 Return city DO- RC 25 Return city NM- NM 30 Customer name W- AD 80 Customer address ID- NO 25 Customer ID # EXP EX 1 Express service indicator CD- CD 10 Corporate discount # RC- RQ 10 Rate code information FT- FT 20 Frequent traveler data SQ- SQ 20 Special equipment data DT- RT 5 Drop time DL- DL 30 Driver's license G- GD 19 Credit card number PR- PR 25 Prepayment information SI- F1 30 Special information SI- F2 30 Special information SI- F3 30 Special information IT- TR 30 Tour number RF 9 Agent/user ID VN 6 Apollo record locator AA 106 Agency Address C 15 Drop Charge PG 55 Pricing Guaranteed OS 100 OSI Message Text GR 55 Pricing Guaranteed(ZE) PQ 55 Pricing Quoted QR 55 Pricing Quoted(ZE) SI-PC TK 8 Promotional Code SI-AUTH TK 20 Authorization IP 8 Point of Sale (Intuitive Framework only) NOTE: Maximum number of characters allowed for optional data sent from Apollo is 141, including the field identifiers. Following is an estimate of the average number of characters which can be expected. This does not include the header and can vary depending on the length of the confirmation number. Sell: 100 characters Modify: 60 characters Cancel: 16 characters Ignore: 16 characters ET: 28 characters Keywords Apollo to Vendor FIELD CODE Customer name /NM Pick up date /DA Pick up time /TA Rental city /CY Return date /RD Return city /RC (if different from rental city) Vehicle type /VT Rate code /RQ Customer address /AD Confirmation number /ID Corporate identification number /CD Special equipment /SQ Tour number /TR Express service /EX Frequent traveler number /FT Booking source - ARC # /TC Referral source /RS Inbound flight number /FL Car club number /NO Travel agency phone number /PH Drop time /RT Driver's license /DL Prepayment information /PR Credit card number /GD Remarks field- broken up in /F1 3 - 30 byte /F2 fields /F3 Apollo record locator /VN Agent/user ID /RF Promotional Code or Authorization /TK Agency Address /AA Drop Charge /DC Pricing Guaranteed /PG Pricing Guaranteed(ZE) /GR Pricing Quoted /PQ Pricing Quoted(ZE) /QR Keywords Vendor to Apollo FIELD CODE Customer name /NF Confirmation number /ID Rate field /RQ /RG /GR /QR Drop Charge /DC OSI Message Text /OS Rate Code /RC Format Examples 1. Apollo sends sell, modify, cancel, ignore, and End transact in keyword format: SV/CYDEN/DA25OCT/RD27OCT/VTICAR/RSUADEN/ TCUA/TA1600/NMSMITH JANE SC/ID12345678901/DA26OCT/RD27OCT SP/ID12345678901/VTLCAR SP/ID12345678901/NOXXX SX/ID12345678901 SI/ID12345678901 SE/ID12345678901/VN3AA4LX 2. Every message sent by Apollo begin with the characters 'UA' (Apollo) or '1G' (Galileo), depending on the requester, a blank, the LNIATA of the agent set, five blanks, and 'Sx/'. (Where x = type of transaction.): ........ E4C140F2 C2C3F1F1 F2404040 4040E2E7 61...... ........ ........ 3. The vendor returns a code to indicate completion of transaction, a confirmation number, and the name (optional): SVER/ID12345678901/NFSMITH JANE or SVER/ID12345678901 SCHG/ID12345678901/NFSMITH JANE SCAN/ID12345678901/NFSMITH JANE SIGN/ID12345678901/NFSMITH JANE SCON/ID12345678901/NFSMITH JANE SWAR/ID12345678901/NFSMITH JANE/ERR043045 or SWAR/ID12345678901/NFSMITH JANE/MSG/xxxxxxxxx SWAR/ID12345678901/NFDOE J/OS free form text Note: If message text is returned (signified by MSG) it must be the last item in the message. 4. If for any reason the sell cannot be completed (error condition) by the vendor, an error number or response is returned to Apollo. SERR/ERR043045 or SOFF/xxxxxxxxxxxxx 5. Existing type B teletype is used as a backup in case the link is down. Rate Field The entered rate should be in the following format: /RQ-USD70.00WK-.10 MI -RC  Rate Code (Optional) - 5 character maximum Dash Blank Miles or Kilometers ` Blank Mileage or Kilometer Charge - Max 4 digits or UNL Dash Rental Period (sell table for codes) Basic Rental Charge - maximum 7 characters. including decimal, if valid Currency RQ - Rate Quoted or RG - Rate Guaranteed NOTE: A second rate can be appended which is only edited for length: /RQ-USD70.00WK-.10MI 130.00MO-UNL MI-RC (Total Rate Field - including /RG- cannot exceed 50 characters.) CODES - RENTAL PERIODS: DY (Daily) WY (Weekly) WK (Weekly) WD (Weekend) MO (Monthly) PK (Package) WE (Weekend) SP (Special) BR (Base Rate) HR (Hourly) NOTE: When returning a rate via Type A, there is no dash following the first /RG identifier. Error Numbers/Definitions CAR SYSTEM ERROR CODE APOLLO RESPONSE TO AGENT 001 002 ***SYSTEM UNAVAILABLE 003 INVALID IATA/ARC NUMBER 004 CLIENT NAME MISSING 005 RENTAL CITY MISSING 006 MUST CANCEL AND SELL NEW RESERVATION 007 CAR TYPE MISSING 008 PICKUP DATE MISSING 009 RETURN DATE MISSING 010 PICKUP TIME MISSING 011 INVALID NUMBER ONE CLUB NUMBER 012 INVALID CUSTOMER ID NUMBER 013 PHONE FIELD REQUIRED 014 INVALID PICKUP DATE 015 INVALID PICKUP TIME 016 INVALID RENTAL CITY /PUP- CODE 017 INVALID /DO- CITY CODE 018 INVALID RETURN DATE 019 INVALID CAR TYPE CODE 020 INVALID /CD- NUMBER 021 INVALID EXPRESS SERVICE FORMAT 022 ***SYSTEM PROBLEM - RETRY 023 INCORRECT INBOUND FLIGHT 024 HOST/REFERRAL SOURCE MISMATCH 025 INVALID /RC- CODE 026 INVALID /SQ- CODE 027 RESERVATION NOT ON FILE 028 INVALID /FT- AIRLINE CODE 029 WAR EXPRESS SERVICE NO LONGER OFFERED 030 WAR NOT WITHIN GOLD SERVICE HOURS 031 PICKUP NOT ALLOWED THIS LOCATION 032 DROP-OFF NOT ALLOWED THIS LOCATION 033 WAR GOLD SVC NOT AVAIL THIS TERMINAL 034 NO CARS AVAILABLE THIS DATE/TIME 035 RATE CODE INVALID-CK MIN RENTAL 036 RATE CODE INVALID-CK ADV BOOKING 037 THIS CAR TYPE NOT AVAILABLE 038 LOCATION CLOSED AT TIME SPECIFIED 039 ONE WAY RENTALS NOT ALLOWED 040 RETURN LOC NOT 24HRS - CHECK TIMES 041 CAR ON REQUEST 042 SIMULT CHANGE TO PNR 043 ADV BOOKING TIME NOT MET-ON STANDBY 044 7 DAY MIN REQ FOR ONE WAY THIS RATE 045 EUROPEAN LOCATIONS PROCESS VIA TTY 046 RESERVATION IN REQUEST STATUS 048 INVALID /FT- AIRLINE CODE 049 UNABLE TO LOCATE RECORD 052 *** SYSTEM BUSY - RETRY 053 HAND CTRLS NOT AVAIL THIS DATE/TIME 054 SKIERIZED NOT AVAIL THIS DATE/TIME 055 BABY SEATS NOT AVAIL THIS DATE/TIME 056 UNABLE - RESERVATION CANCELLED 057 LENGTH OF RENTAL EXCEEDS MAX DAYS 058 RC- CODE NOT AVAILABLE 059 RATE NOT GUARANTEED BEYOND 30 DAYS 060 PC CODE INVALID OR NOT AVAIL 061 INVALID NAME 062 NEED MAILING ADDRESS 064 INVALID /PUP- LOCATION NUMBER 065 FT- NBR EXCEEDS FIELD LENGTH 066 INVALID /DO- LOCATION NBR 067 CAR TYPE REQUIRES SPECIAL HANDLING 068 INVALID CONVENTION NBR/ITCV 069 EXPRESS SVC REQUIRES NBR 1 CLUB NBR 070 ARR- TIME HAS LAPSED 071 VERIFY /DO- LOCATION 072 RETURN LOCATION TEMPORARILY CLOSED 073 ONE WAY OR /DO- NOT AVAIL THIS VEH TYP 074 ***FRONT END PROCESSOR ERROR 075 OWNERSHIP ASSIGNED OTHER CARRIER 076 W- EXCEEDS FIELD LENGTH 077 ` MUST CANCEL AND SELL NEW RESERVATION 078 FLIGHT REQUIRED FOR GOLD SERVICE 079 ARR- TIME HAS LAPSED 080 MOBILE PHONE NOT AVAIL FOR DATE/TIME 081 MUST BE GUARANTEED - CALL VENDOR 082 CANNOT MODIFY/CANCEL - CALL HERTZ 084 PRICING DISPLAY UNAVAILABLE 087 LOCATION CLOSED ON DAY SPECIFIED 088 *** Do not use this number.*** 089 /SQ NOT OFFERED ON THIS CAR TYPE 090 /SQ NOT OFFERED THIS CITY / LOCATION 091 ADVANCE BOOKING FOR /SQ NOT MET 092 MAXIMUM /SQ REQUESTS REACHED 093 RATE QUOTE NOT AVAIL THIS LOCATION 094 FOR HAND CTRLS CALL NATIONAL DIRECT 095 ALL ONE-WAY CARS ARE UNAVAILABLE 096 /SQ HAS BEEN REQUESTED 097 CONTRACTED RATE EXTENDED AT COUNTER 098 DISCOUNT RATE EXTENDED AT COUNTER 099 ***Do not use this number.*** 100 PRICING SYSTEM BUSY - RETRY 101 REQUESTED RATE DID NOT QUALIFY 102 /CD FIELD REQUIRED TO AUTOPRICE 103 /RC DOES NOT QUALIFY 104 PRICING NOT AVAILABLE THIS RATE CODE 105 UNABLE TO PRICE NO /RC QUALIFIES 106 /CD REQUIRED THIS RATE CODE 107 INVALID - RES BEYOND 365 DAYS 108 GOLD SERVICE NOT OFFERED WITH /SQ 109 GOLD SERVICE NOT OFFERED WITH PC- 110 NO GOLD SERVICE ON THIS VEHICLE 111 GOLD SERVICE NOT OFFERED WITH /IT- 112 WAR GOLD SVC ADVANCE BOOKING NOT MET 113 ` GOLD SERVICE NOT OFFERED THIS CITY 114 CLIENT NOT USA/EUR GOLD MEMBER 115 NOTE /FT-WAS NOT INCLUDED 116 CREDIT CARD NOT ON FILE - CALL VENDOR 117 CREDIT CARD ON FILE EXP - CALL VENDOR 118 DROP OFF NOT ALLOWED AFTER HOURS 119 MUST INCLUDE /G-FIELD 120 CUSTOMER DOES NOT MEET RESTRICTIONS 121 CUSTOMER NOT ENTITLED TO THIS RC 122 FLIGHT INFO REQUIRED FOR THIS /RC 123 NEED SPECIFIC FLIGHT NUMBER 124 SQ NOT AVAILABLE THIS DATE/TIME 125 INVALID RETURN TIME 126 - 127 ***Reserved for Hertz.*** 128 SQ NOT AVAILABLE ONE WAY 129 RC REQUESTED REQUIRES/IT FIELD 130 ONE WAY DISTANCE NOT AVAILABLE 131 DROP FEE CANNOT BE CALCULATED 132 RC - SELECTED APPLIES TO ONE WAY ONLY 133 EXTRA DAY CHARGES NOT AVAILABLE 134 DROP OFF NOT ALLOWED AFTER HOURS 135 LOCAL CONTRACT RATE WILL APPLY 136 PREPAYMENT REQUIRED - CALL HERTZ 137 RC - SELECTED EXCEEDS MAXIMUM DAYS 138 RC - NOT AVAILABLE FOR CITY /CAR 139 RC - SELECTED MUST RETURN DOWNTOWN 140 RC - SELECTED MUST RETURN TO AIRPORT 141 RC - SELECTED MUST RETURN TO A HOTEL 142 RC - MUST RETURN SAME LOCATION 143 RC - NOT AVAILABLE FOR ONE WAY 144 RC - MUST RETURN WITHIN SAME STATE 145 RC - CANNOT BE USED WITH PROMOTION 146 CONTRACT BENEFITS WILL NOT APPLY 147 CSTMRS AGRMNT REQUIRES CR WHEN AVLBL 148 RC-NOT AVAIL-CORP RATE ASSIGNED 149 RC-NOT AVAIL-BEST RATE ASSIGNED 150 RC- REQ DENIED - COR RATE ASSIGNED 151 /IT REQUESTED REQUIRES /RC- FIELD 154 INVALID RETURN TIME 155 CC TYPE INVALID FOR PREPAYMENT 157 RATE SUBJECT TO CHANGE/CHECK RULES 164 LOCATION REQUIRES SPECIFIC CD 165 INVALID NBR OF COUPONS SPECIFIED 166 PC -NOT AVAIL FOR VEHICLE/DATE 167 PC -NOT AVAIL THIS CITY/LOCATION 168 INVALID FORM OF PAYMENT 169 ADV BOOKING REQUIRED FOR PC- 170 PC-HAS MIN/MAX DAY REQUIREMENTS 171 PC-NOT AVAIL FOR ONE WAY RENTAL 172 PC- REQUIRES SPECIFIC CD NUMBER 173 PC- DOES NOT HAVE OPTIONAL BENEFIT 174 RC- NOT VALIDATED - CHECK AT COUNTER 175 /RC-REQUIRES SPECIFIC FOP 177 DUPLICATE TOUR RES ID 178 MUST INCLUDE /VI 179 INVALID /VI 180 MUST INCLUDE /TI 181 SQ ON REQUEST ONLY 182 INVALID TOUR DATE/TOUR NUMBER 184 SQ ON REQUEST ONLY 185 TOUR BOOKING DOES NOT QUALIFY 186 MINIMUM RENTAL REQUIRED FOR THIS CAR TYPE 183 INVALID TOUR DATE / TOUR NUMBER 187 GOOD DRIVING REC REQ-SEE VALID 188 WAR RATE ASSIGNED REQ A/L TICKET 189 WAR THEFT PROTECTION MANDATORY 190 GOLD CANOPY SERVICE CONFIRMED 191 PREPAID CONFIRMED - INVOICE PENDING 193 INVALID CC EXP DATE 196 FAX REQUIRES VALID COUNTRY CODE 197 INVALID FAX NUMBER 198 FAX NUMBER REQUIRED 199 FAX NOT AVAILABLE THIS RATE PLAN 200 MUST INCLUDE VOUCHER NUMBER 201 FOR RENTERS UNDER 25 SEE KEYWORD AGE 202 EXTRA DAY CHARGES APPLY AFTER 203 VOUCHER AUTHORIZATION DENIED 204 VOUCHER VALUE NOT AUTHORIZED 205 SECURITY FILEL NOT FOUND 206 MUST INCLUDE VOUCHER VALUE 207 MUST INCLUDE BILLING NUMBER 208 MUST INCLUDE OFFICE ID 209 INVALID FORM OF PAYMENT 210 /FT-REQUIRES SPECIFIC /CD- 211 IMPORTANT-DIRECT RNTR TO HERTZ BUX 212 TOUR RATE NOT AVAILABLE 213 NO DRP LOC.-RTRN TO SERV. LOCATION 214 CD-REQUIRES CORP RATE TO BE ASSIGNED 215 FP ONLY VALID AT CHECK-IN 216 ISSUE VOUCHER FOR RNTL OR RMOVE /ID- 217 ADDITIONAL INFO. REQUIRED-CALL HERTZ 219 GOLD PROFILE REQRS UPDATE-CALL HERTZ 220 INVALID FREQUENT TRAVELLER NUMBER 221 CT RES. PAYING CASH SEE KEYWRD PYMNT 222 ADVISE CUSTOMER $5.00 VALET FEE 223 3RD ID REQUIRED SEE KEYWORD VALID 224 ADVISE CUST. TOP PROCEED TO MONORAIL 225 FOP INVLD FOR DESTINATION - USE ALT 226 GOLD SVC NOT CFMD-FOP INVLD FOR DEST 227 FOP INVLD FOR DEST. - USE ALT 228 PICKUP LOC. FOR HOTEL GUEST ONLY 229 INVALID CREDIT CARD NUMBER 230 PC CODE EXPIRED FOR SPECIFIED DATE 231 PC CODE IN BLACKOUT FOR CITY/DATE 233 IATA REQUIRED FOR CD NUMBER *** Message not sent to agent; Apollo marks session as timed-out. PAGE  GALILEO INTERNATIONAL INSIDE LINK CAR - FUNCTIONAL SPECIFICATION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Page PAGE 6 Functional Specification %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Galileo International Confidential Page page10 Galileo International Proprietary and Confidential 18 June, 1998 Galileo International Proprietary and Confidential 18 June, 1998 ,9Jef|} +,45]_gh)*DEFGHdejUmHj}UmHjUmH jUmH5CJOJQJ;mH jU5CJ CJOJQJJ+,9>IJKLMNOPQRS H$ $$4TH$$$40Txx$&#$/  &#$/  d+,9>IJKLMNOPQRSTUVWXYZ[\]^_`abcdeIJ{,_ Z E ;  [  d _D Gs ^STUVWXYZ[\]^_`abcde d &.+Dp&+D$$40T $$4TH$IJ{,_ Z d*+EFGHI[\vwxyz  '()*+?@Z[\]^uvj_UmHjUmHjeUmHjUmHjkUmHjUmHjqUmHjUmH jUmHjwUmHmH=     9 : T U V X Y | } $ % ? @ A C D _ ` z { | ~  j UmHjG UmHjUmHjMUmHjUmHjSUmHjUmHjYUmHjUmH jUmHmH= E ;  [  d _D Gs   5 6 7 9 : n o    : ; U V W Y Z w x   C D ^ j UmHj/ UmHj UmHj5 UmHj UmHj; UmHj UmHjA UmH jUmHmH=^ _ ` b c >?YZ[]^#$>?@BCijjUmHjUmHjUmHjUmHjUmHjUmHj#UmHjUmHmH jUmHj)UmH= &'ABCEFRSmnoqry1KLMlmjOJQJU >*OJQJOJQJ>*CJOJQJ5OJQJ CJOJQJ jUjUmHjUmHjUmHj UmHjUmHmH jUmH:xy/0Ľ}ztqnkJ st                        ($H$H$*$$4F"$xx$xx$dxyd!dd*$$4F"$H$H$ $$4 "y/01KL9LMOP%d@&8ddd01KL9LMOP%&'RT  opy ľ͠|yvsHI23p  LM n I,9:YZL'R**++b,n,q0022!7778888::::::;;x@@J,JMM7P9P[PoRRSSrWWWWWW[[[]]^^>_q_f`h``bbc=cEcghiikk%l>lm 5OJQJjOJQJUmH >*OJQJjOJQJUOJQJV%&'RT  opy z !d@&ddy z !!""##w$x$,%-%1&2&&&X'Y'}(~(A)B)))*******++++6,7,>,b,o,p,,,,|yva & #$w:;_`@A,->?-!!""##w$x$,%-%1&2&&&X'Y'}(~(A)B)))******dd@&d**++++6,7,>,b,o,p,,,,, -V-X--------@ dd@&d $$dd,, -V-X----------1.2...6/7////////00p0q000i2j2222222233/36373|3334 4ܻܝܚܗܔܑ܈t ;<89EFxy^`3---1.2...6/7////////00p0q000i2j22d@&pdddd@&222222233/36373|3334 444445A5u555pdpd@&d@&dd@& 444445A5u5555 6*6;6U6s666666 7!7778777(8U8V888888888^9_9999,:m:n:|yv^lm wxy,- [\ 'ARo;`s-55 6*6;6U6s666666 7!7778777(8U8V888888dd@&ddpd8888^9_9999,:m:n:_<`<-=.===????w@x@@0dddd@&dn:_<`<-=.===????w@x@@@AAAAB0BEBaB|BBBBBBCCDDyEzETFUFFFDGEGGGHH9H~{xu]^34#$3He ST78kl]-@@AAAAB0BEBaB|BBBBBBCCDDyEzETFUFFFDGddd d ` DGEGGGHH9H:H`HaHmHHHHHH&I'IJJ,J-JJJFKGKd@&d@&ddd9H:H`HaHmHHHHHH&I'IJJ,J-JJJFKGKKKLLLLMMMMMMMMMKNLN O OOO7P8P9P[P\PfPPP񲯬񦣠񋈂 3  rsz{ab yz>?0GKKKLLLLMMMMMMMMMKNLN O OOO7P8P9P[Pd@&d@&d@&dd[P\PfPPPPPPrQsQ}Q~QQQQQmRoRRRSSSS9T:Tddd@&d@&dPPPPrQsQ}Q~QQQQQmRoRRRSSSS9T:TTT VV W WqWrWWWWWWWWWWWXXX>YhYYYYRZ֠|<]^  5l mn0:TTT VV W WqWrWWWWWWWWWWWXXX>YhYYYYdd@&ddYRZSZ^ZoZpZZZP[Q[[[[[[Q\R\r\s\\\]]]]^d@&pd@&d@&ddRZSZ^ZoZpZZZP[Q[[[[[[Q\R\r\s\\\]]]]^^^^^^^_<_>_q_r_f`g`h```AbBbbbbbbbcв n&'  ?@Aoyz~  1^^^^^^^_<_>_q_r_f`g`h```AbBbbbbbbbd@&pd@& d@&ddbccc=c>cEcFcccAdddd@eAeeeJfKfufvfffpdd & Fddd@&dd@&ccc=c>cEcFcccAdddd@eAeeeJfKfufvfff/g0ggghhhh(iMiNiiiiijjkkkkk|ys wop OPstC        de ,f/g0ggghhhh(iMiNiiiiijjkkkkkll#l%ld@&d@&ddkll#l%l>l?lmm&n'nnnnnrosoppppqqrqqqQrRrvtwtuuXvYvxvyvvvvvvvwwww|x}xxxxxxxHy,- noPQuvUV()Y 235%l>l?lmm&n'nnnnnrosoppppqqrqqqQrRrvtwtuud@&ddm&nYvxvJyeymyzzzzzzzzTVrځm4؇-.LtopӐڐ:]ϓȔLUitu#- &OPvģڣy;[\f˦ئhͨ5>*CJOJQJ 5OJQJ >*OJQJOJQJZuXvYvxvyvvvvvvvwwww|x}xxxxxxxHy d@&@ d@&pd@&d@&d@&ddHyIyJyeyfymynyzz | |||H}}}}~_~`~~~~~~~uvyzTUVrs؁فƾ{xu dFIJL          [\WX }~,HyIyJyeyfymynyzz | |||H}}}}~_~`~~~~~d@& & Fdd0ddd@&d~~~uvyzTUVrs؁فځgd@&d@&dddفځghHIlm˄݄ބ !+GSde45؇ه23܈݈ST,-.LMrstĸ  #$ NOP12 mnrs}2ghHIlm˄݄ބ !+GSde45dd@&d@&dd؇ه23܈݈ST,-.LMrst:;d@&dd@&d:; eDEopJKklѐҐӐڐېLM89:]^t¿}zw yz&  5  z      _`-; eDEopJKklѐҐӐdd@&d & FddӐڐېLM89:]^tϓГƔǔȔ d@& !@ d@&ddd@&ϓГƔǔȔJKLUVՕ֕GHҖӖ ]^RS̙͙ituʚ.H唑G`s uvBC<=}~,3JKLUVՕ֕GHҖӖ ]^RS̙d@& d@& !dd̙͙ituʚ.H_{Ǜ؛!dd@&dH_{Ǜ؛!"#-.D^qŜל1GZeqLMzЀ}zN )CXm FSTez-/!"#-.D^qŜל1GZeqd@&ddLMz-EYmdd@&dd@&d !-EYm lm$%&OPtuv£ãģڣۣwxy   l 123uve4 lm$%&OPtuvd@&d@&dd£ãģڣۣwxy9;[\fgpd@&pdddd@&y9;[\fg˦̦5DSfgh:cʨ˨ͨ6Qp¿Ȫȃ}z]| .Qi =DEXgv  @ %/˦̦5DSfgh:cʨ˨ͨdddͨ6Qpũ*Jyê#Cp/RdͨưǰհUqr!"'|}ĺ ۾ "$&(*\^5CJOJQJ0J5CJOJQJmHj0J5CJOJQJU0J5CJOJQJ CJOJQJCJ0J j0JU H*OJQJjOJQJUmH 5OJQJ >*OJQJOJQJ5>*CJOJQJ7ũ*Jyê#Cp/RvŬ/Mrխ#@ah!"8[~~|yve#Fl4[.W{ 6] &T%A.RvŬ/Mrխ#@ah!"8[dd@&d$dd[~ưǰհְ&9Mmñ*Hedddd~ưǰհְ&9Mmñ*He|β߲-N`nȳݳ &<U~{xun  <J\}.Eb)=]q xyz-e|β߲-N`nȳݳ &<UqrdpddUqrǴϴ״!"uv޵ /IJ#$lm9YyøƸ!"# 볰똕֒%Sqr EFVl~ 1Ǵϴ״!"uv޵ /IJ#$lmdd@&dd9YyøƸ!"# /0{|}dddd@& /0{|}!"58JKhi~˻̻lmnoݽ F| )STb89cd 0!"58JKhi~˻̻lmnod@&ddoݽ F۾ܾ#>Yӿ6Rddd@&۾ܾ#>Yӿ6RmEk"OxEm8c~{xuHdz;b1^;a|.Jl'B]}.RmEk"OxEmd8c@k-W{?bdc@k-W{?bFn*S}Fm,~{xur:f-V:cAk)Sq@c.Fn*S}Fm,W0\d,W0\,S}Hu 6Y-RFn<~{xuj:d.Sy'Js 8e-T}$Pl)T.\,S}Hu 6Y-RddFn<f 2\=cd<f 2\=cFqEl$Kq*Rl~{xu.Vq5\;j:bCk$NuD.FqEl$Kq*Rld%Im1[zIuHs8a~{xuHr 8def 7c%Oq7[.%Im1[zIuHsd8ad$dd $&*\?j 1 d !d. *\^'(jkno d ! $d  !$h !$ $d  !$`d&d d$d$hd&`#$"#%&'(=?[\ijknoOJQJ5CJOJQJ CJOJQJ 5OJQJCJmHCJ jCJU9 000@&PP/ =!"#$%@}DyK _Toc424442184}DyK _Toc424442185}DyK _Toc424442186}DyK _Toc424442187}DyK _Toc424442188}DyK _Toc424442189}DyK _Toc424442190}DyK _Toc424442191}DyK _Toc424442192}DyK _Toc424442193}DyK _Toc424442194}DyK _Toc424442195}DyK _Toc424442196}DyK _Toc424442197}DyK _Toc424442198}DyK _Toc424442199}DyK _Toc424442200}DyK _Toc424442201}DyK _Toc424442202}DyK _Toc424442203}DyK _Toc424442204}DyK _Toc424442205}DyK _Toc424442206}DyK _Toc424442207}DyK _Toc424442208}DyK _Toc424442209}DyK _Toc424442210}DyK _Toc424442211}DyK _Toc424442212}DyK _Toc424442213}DyK _Toc424442214}DyK _Toc424442215}DyK _Toc424442216}DyK _Toc424442217}DyK _Toc424442218}DyK _Toc424442219}DyK _Toc424442220}DyK _Toc424442221}DyK _Toc424442222}DyK _Toc424442223}DyK _Toc424442224}DyK _Toc424442225}DyK _Toc424442226! [$@$NormalmH <@< Heading 1$@&5CJOJQJ8@8 Heading 2$@& 5OJQJF@F Heading 3 $<>*CJOJQJkHFF Heading 4 $<>*CJOJQJkHBB Heading 5$d@& >*OJQJB@B Heading 6$d@& 5OJQJ<A@<Default Paragraph Font, @,Footer  !,@,Header  !&)@& Page Number>@>TOC 1  u  5OJQJ:@:TOC 2  u OJQJ::TOC 3  u OJQJ2@2TOC 4 (# OJQJ22TOC 5X (# OJQJ22TOC 6  (# OJQJ22TOC 7 (# OJQJ22TOC 8 (# OJQJ22TOC 9x (# OJQJ8Y8 Document Map-D OJQJZOZMainhead#$& #$/  @5CJOJQJmH BOBVersion Control $5CJ,O, ProprietryCJ4O4Table 10H OJQJmH DD Table Text $:: .5CJ0sw ^ mͨx}~S y%!*-258@DGGK[P:TY^bf%luHy~g;Ӑ̙!ͨR[eoR\y{|0y , 4n:9HPRZckHyفHy~U c,<ze|+4]^g)EGd*FH[wy (*?[]u9UX|$@C_{~69n :VYw  C _ b   > Z ]  # ? B i   & B E R n q Ll9Y9'' %T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T%T9999%*-!!!8@ B ( }0 NB  S ?NB  S ?NB  S ? NB  S ? NB  S ?NB  S ?NB  S ?NB   S ?NB   S ?NB   S ?NB   S ?NB   S ?NB  S ?NB  S ?NB  S ?NB  S ? NB  S ? NB  S ? NB  S ?NB  S ?NB  S ?NB  S ?NB  S ?NB  S ?NB  S ?NB  S ?NB  S ?B S  ?b(c(d(e(f(g(h(i(j(k(l(m(....¶öH0It0t0! tx0yt0t0t0 t01 tX0YAt 0 t 0 tX0Y1 t1 tx1yrt1tX1YbtPQtt5t t  % t ` a t01t @ A %t1rt (1)t h 1i ttitlecodefilenameauthorissuecontents _Toc422819508 _Toc422880100 _Toc424442184 _Toc422818939 _Toc422880101 _Toc424442185 _Toc424442186 _Toc404499715 _Toc422818940 _Toc422880102 _Toc404499716 _Toc422818941 _Toc422880103 _Toc424442187 _Toc422818942 _Toc422880104 _Toc424442188 _Toc404499718 _Toc422880105 _Toc424442189 _Toc404499719 _Toc422818943 _Toc422880106 _Toc424442190 _Toc422880107 _Toc424442191 _Toc422880108 _Toc424442192 _Toc422880109 _Toc424442193 _Toc422880110 _Toc424442194 _Toc422880111 _Toc424442195 _Toc422880112 _Toc424442196 _Toc404499726 _Toc422880113 _Toc424442197 _Toc422880114 _Toc424442198 _Toc422880115 _Toc424442199 _Toc404499728 _Toc422818944 _Toc422880116 _Toc424442200 _Toc422880117 _Toc424442201 _Toc422880118 _Toc424442202 _Toc422880119 _Toc424442203 _Toc422880120 _Toc424442204 _Toc422880121 _Toc424442205 _Toc404499733 _Toc422818945 _Toc422880122 _Toc424442206 _Toc422880123 _Toc424442207 _Toc422880124 _Toc424442208 _Toc422880125 _Toc424442209 _Toc422880126 _Toc424442210 _Toc422880127 _Toc424442211 _Toc422880128 _Toc424442212 _Toc422880129 _Toc424442213 _Toc422880130 _Toc424442214 _Toc422880131 _Toc424442215 _Toc422880132 _Toc424442216 _Toc422880133 _Toc424442217 _Toc422880134 _Toc424442218 _Toc422880135 _Toc424442219 _Toc422880136 _Toc424442220 _Toc422880137 _Toc424442221 _Toc422880138 _Toc424442222 _Toc422880139 _Toc424442223 _Toc422818948 _Toc422880140 _Toc424442224 _Toc422818949 _Toc422880141 _Toc424442225 _Toc422880142 _Toc422880143 _Toc422880145 _Toc422880146 _Toc422880147 _Toc422880148 _Toc422880149 _Toc422880150 _Toc422880151 _Toc404499759 _Toc422818950 _Toc422880152 _Toc424442226 _Toc422880153 _Toc422880154 _Toc422880155 _Toc422880156 _Toc422880157 _Toc422880158 _Toc422880159 _Toc422880160 _Toc422880161+` y}}}1111''&&''q,q,!3!344x<x<x<FF9L9LoNoNoNoNOOrSrSSSWWZZ>[>[>[>[h\h\^^__ccgg%h%hiiYrYrJuJuV}V}mm..ttpp::iiiu#&vğy;;;;\hͤU}  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ +` ~6JJJKKKQQ&&'',,636344<<<+F+FZLZLtNtNNNOOSSSSWWZZC[C[p[p[\\^^<_<_ddgg=h=h%j%jwrwrduduq}q}33׃׃KK\\sss, Nٟ<ZZZeʢŬp 9Y|$D_:n:Zw C c  > ^  # C i & F R r &?[9Y|$D_:n:Zw C c  > ^  # C i & F R r '4&?[Corporate Network Services>C:\My Documents\Word\Functional Specs\Inside Link Cars cjw.docCorporate Network Services>C:\My Documents\Word\Functional Specs\Inside Link Cars cjw.docCorporate Network Services>C:\My Documents\Word\Functional Specs\Inside Link Cars cjw.docY2K Project Office;C:\My Documents\Word\Functional Specs\Inside Link Cars .doc Corporate Network Services - LANX\\DENPFS02\edi\Document Templates\Documents - 1998\Functional Specs\Inside Link Cars.doc Corporate Network Services - LANC:\Inside Link Cars.doc Corporate Network Services - LAN!C:\Documents\Inside Link Cars.doc Sandra Ries)C:\My Documents\Word\Inside Link Cars.docCorporate LAN Services)D:\My Documents\Word\Inside Link Cars.docCorporate LAN Services1C:\TEMP\AutoRecovery save of Inside Link Cars.asd*@h 8OJQJo(@HP LaserJet 4050 Series PCL 6\\Chiptr01\hp45_03HPBFDB1HP LaserJet 4050 Series PCL 6HP LaserJet 4050 Series PCL 6?XX",HP LaserJet 4050 Series PCL 6.\ ƣQp1 Pj5QXX*aca>"7Hhg 2- yL"V9RIm*RL3)d~_MtE/ϡUJ ^Y 2oOe+,i+r5"Ucq̂5SZ(C1ŰsOlh9F(\9B!rǨ&_F#rgSs=fl NV'`b-v5WFf0rw ?*9!yM 4ĭޜ,iRsZr\t4O^m>}EEx U!_h5~׆ ]P]6Y|e ܇}[V \g%_4~i$ hiI04^|6}(0tt~XHǵ =mee E0w` QY!Ovi&+ea9s 4J "- >oS1wi_ ]a.Ia`gi ƈ֠z Zd~k( lqI:p)ʎBv}K֠[>2ŧ#^ 8Z81 Y) )d e1pc.U ^g` Bt<2w. 2xU#$UR63A.JE&W?6sf"7Hhg 2- yL"V9RIm*RL3)d~_MtE/ϡUJ ^Y 2oOe+,i+r5"Ucq̂5SZ(C1ŰsOlh9F(\9B!rǨ&_F#rgSs=fl NV'`b-v5WFf0rw ?*9!yM 4ĭޜ,iRsZr\t4O^m>}EEx U!_h5~׆ ]P]6Y|e ܇}[V \g%_4~i$ hiI04^|6}(0tt~XHǵ =mee E0w` QY!Ovi&+ea9s 4J "- >oS1wi_ ]a.Ia`gi ƈ֠z Zd~k( lqI:p)ʎBv}K֠[>2ŧ#^ 8Z81 Y) )d e1pc.U ^g` Bt<2w. 2xU#$UR63A.JE&W?6sfas.microsoft.com/office/2006/metadata/longProperties"/> This value indicates the number of saves or revisions. The application is responsible for updating this value after each revision. ?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~="xs:string"> tomXml"/>repoint/v3/contenttype/forms">DocumentLibraryFDocumentLibraryFormDocumentLibraryFormDocumentLibraryForm5F8-5377-4223-BF7F-86C5A9BC2D6C}" xml