Questionaire for Interactive Sell final.doc



PRELIMINARY QUESTIONNAIRE FOR INTERACTIVE SELL

Listed below is a set of initial questions concerning %vendor%’s requirements for the Interactive Sell product.

Test System

1. What is your Test System Date?

     

2. How often is this date changed?

     

1. How often is your test system refreshed?

     

2. To which SITA address in your Test System should Type B messages from 1G Copy be sent?

Note: 1G Test System address is SWITT1G

     

Message Processing

EDIFACT Versions

Please advise EDIFACT versions for:

ITAREQ/RES (earliest version for Electronic Ticketing indicator 96:2)

     

HWPREQ/RES

     

CLTREQ/RES

     

Token (CARF)

It is essential for the Interactive Sell process that a Token is returned to 1G even if %vendor% does not normally use a Token in its own process. The Token format may be %vendor%’s own choice. Generally a token is up to a maximum of 9 characters however, if required, Galileo can handle a maximum of 28 characters by special arrangement.

Each token must be unique to each transaction & must be carried through the ITA exchange to be included in the HWP generation even if this means a Type B fallback of the HWPREQ. There are three options for token creation: GI creates all, YY creates all or a split CARF where each party adds part to create the whole unique token.

Please indicate which option you require

GI Generates Entire Token (CARF)

YY Generates Entire Token (CARF)

Split Token (CARF)

Flight Facts

YY are able to return up to five flight facts in the ITARES response. An example of a flight fact message within an ITA response is as follows:

IFT@@ DPTS LAX T3@OPERATED BY YY 527@CHECK IN WITH SERVICE AIR

How many lines of flight facts might be sent for each segment?

     

Rebook/Cancel

Can %vendor% handle interactive cancel?

     

Can %vendor% handle rebook before cancel?

     

Fallback

Select the type of sell to which you wish to default if the Interactive Sell Link is down. Request (NN) recommended so subscriber is aware seat is not confirmed.

NN Status

Super Guaranteed (NK status returning RLOC)

Guaranteed – LK Status

Standard Teletype Booking (SS – sold from status assuming positive availability status)

Point Of Sale Information

The following Point of Sale information is available and, if required, can be transmitted in the EDIFACT ORG..

Example: ORG@1G:SWI@14123454:XI2@SWI@@T@GB@35'

Please indicate which items are required to be sent with Booking Entries:

Agents IATA/ ARC number (8 numeric)

PCC (Maximum 4 alpha/numeric. Booking Pseudo City Code

Agency City Code (maximum 5 alpha city code of the National Distribution Company)

Originator Type (Alpha “A” or “t” indicates Airline or Travel Agent)

ISO Country Code ( 2 Alpha Country Code of Selling Agent)

Agent sign-on

Point of Sale in End Transact Name Message (HWPREQ)

The above “enhanced” point of sale items may also be sent with the ET Name Message (HWPREQ).

Suggested Example:

LTS@ ? QK LONRMYY? .SWIRM1G 161147/DKGALILEO1G AE97/AE97     ?

SWI1G V3B3MW/XI2/14123454/SWI/1G/T/HK? 1GALILEO/TEST? YY1234Y25SE

P LHRPAR DK1/06551240? ?'        

Is “enhanced” Point of Sale information required with End Transact name Message? (HWPREQ)

Yes No

Status Codes

Please advise status codes YY will return in their ITARES messages. (e.g. HK OK HS SS etc)

     

ERC Codes

Please advise ERC codes YY will return in their ITARES

     

Transaction Timer

Specify in seconds the time-out value for this session.

(Recommend 5 seconds for Interactive Sell) (Note - %vendor% response time should be lower then GI value)

     

Abort Timer

Abort (or Inactivity Timer) in Minutes

(Recommend 35 minutes for Interactive Sell) (Note - %vendor% inactivity timer must be greater than GI value)

     

Dialogue Management

 

Galileo International will use conversational host to host, with the series control in Layer 5. Galileo will initiate the dialogue with a first in series ITAREQ, (Layer 5: QRI5 value HEX 56 or CHARACTER V) a subsequent request would be sent as an intermediate in series (Layer 5: QRI5 value HEX 54 or CHARACTER T) with an ignore (CLTREQ) or wrap-up (HWPREQ) sent as a last in series (Layer 5: QRI5 value HEX 55 or CHARACTER U)

Reconfirm Query Request (RQR / RLR)

When the booking has been completed in the Galileo system an End Transaction Name Message (contained in the HWPREQ) will be sent by Galileo to %vendor% in order to complete the booking.

This End Transaction Name Message contains a DK action code to identify that the inventory has already been confirmed by an interactive sell. (GI can generate LK status if preferred) We would expect a HWPRES reply with MSG3 and the return of the airline RLOC to signify the vendor had accepted all information in our HWPREQ, the data was correct and they where able to complete the booking.

Where a reply to the End Transaction Name Message is not received, the Un-Answered File (UAF) Function in the Galileo core system will send either an RQR or RLR via Type B message within 3 hours, and once only.

The time can be variable and we also have the option to suppress RQR/RLR generation if YY does not wish to receive this.

 

Does %vendor% require this function?

Yes No

If yes, which message type do you prefer?

RQR (Reconfirm Query Request) RLR (Record Locator Request)

Message will be sent via Type B within 3 hours. If a time other than 3 hours is required please specify.

     

Message will be sent once only. If you require the message more than once please specify.

     

Possible Dupe Message (PDM)

When the booking has been completed in the Galileo system an End Transaction Name Message (contained in the HWPREQ) will be sent by Galileo to %vendor% in order to complete the booking.

This End Transaction Name Message contains a DK action code to identify that the inventory has already been confirmed by an interactive sell. We would expect a HWPRES reply with MSG3 and the return of the airline RLOC to signify the vendor had accepted all information in our HWPREQ and was able to complete the booking.

If the vendor has been unable to complete the booking we would expect the HWPRES to be returned with a MSG7 or MSG8 to denote an error handling the GI HWPREQ.

Please advise whether %vendor% will generate MSG7 or MSG8 in the End Transact Name Message (HWPRES). Both these messages are accepted by GI & denote YY could not fully complete the transaction on their system. Upon receipt of either of these errors GI will re-transmit the name message but send Type B with a PDM tag.

     

TPR’s

Please specify number of TPR’s and ordinal range allocated for the Interactive Sell session

Production Copy

Number of TPR’s            

Ordinal Range            

Handshake (APSINQ/APSRES)

The Handshake enquiry allows Galileo to request the status of an application should the link be operating at under specified performance levels.

Does %vendor% support handshake?

     

Would %vendor% like to implement handshake as part of Interactive Sell?

     

At what intervals would a handshake message be required?

     

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

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

Google Online Preview   Download