GDS stands for Global Distribution System, which is any of several computerized reservation systems for booking travel. The GDS emulation process described in this topic allows Deem and ETSI the necessary access to your GDS to process reservations and synchronize profiles for your agency. Follow the steps in this topic for your agency’s GDS.

Need to Know

Deem supports the following GDSs:

• Amadeus

• Apollo

• Galileo / Travelport+

• Sabre

• Worldspan

Amadeus Emulation

Amadeus Web Service credentials connect Deem with your Office ID for booking and profile synchronization.

To emulate the Amadeus GDS:

1. From the Deem Form & Checklist Library. download the following forms as necessary:

   1. the form “Amadeus Web Services - DEEM”

   2. If you’re using ETSI for profile synchronization, also download the “Amadeus Web Services - ETSI” form and see the attached document in this topic.

2. Submit the completed form/s to Amadeus.

3. Once complete, Amadeus returns the following.

   • WASP

   • WBS User ID

   • Clear Password

   • Base64 PWD

   • List of offices

   • Duty Code

4. Provide these credentials to your Deem Configuration Manager.

Apollo Emulation

To request Apollo emulation, follow this process:

1. Contact your Travelport Account Executive (AE) to request emulation.

2. When emulation is complete on Travelport’s end, the Travelport AE notifies the agency and provides a document for the agency to sign. (This process applies to all Travelport API Products.)

3. The agency opens a Deem Support Case that reports to Deem that emulation request is complete.

Notes:

• Deem and ETSI (for GDS profiles) uses Service Bureau access from PCC 1H1H to the agency's PCC.

• Deem uses agent sine RC.

• Full emulation access is required from this host PCC (1H1H) to the customer’s booking PCC.

• In addition to opening access to the booking PCC, also open access to any alternate pseudo city doc Deem should access, such as queue drop.

Galileo/Travelport+ Emulation

To request Galileo/Travelport+ emulation, follow this process:

1. Contact your Travelport Account Executive (AE) to request emulation.

2. When emulation is complete on Travelport’s end, the Travelport AE notifies the agency and provides a document for the agency to sign. (This process applies to all Travelport API Products.)

3. The agency opens a Deem Support Case that reports to Deem that emulation request is complete.

Notes:

• Travelport Auto Segment Logic (ASL) is not compatible with Deem Travel and/or Car Service applications. Verify with your Travelport Account Executive that this feature is turned off in your AAT Table for the booking PCC.  If this feature is currently on, verify that changing it to off will not affect other agency processes and/or technology.

Instructions:

1. Bridge Deem PCC 590M.

2. Deem and ETSI (for GDS profiles) uses Service Bureau access from PCC 590M to the agency's PCC.

3. Deem uses agent sine RC.

4. Full provisioning access is required from this host PCC (590M) to the customer’s booking PCC.

5. In addition to opening access to the booking PCC, also open access between any alternate pseudo city doc you're asking Deem to access (i.e., queue drop, etc.).

Sabre Emulation

Prior to Sabre emulation, establish branch access so Deem can make bookings in the correct pseudo city, and open access between the booking pseudo and alternate pseudo city code.

Process:

1. The agency provides the implementation team with the booking pseudo city code.

2. Deem initiates the emulation process.

3. Open a Deem Support Case for Deem to complete its process. Provide the following information, in which XXXX is the agency pseudo city code: W/TAA8CXA‡BXXXX and W/TAASO1A‡BXXXX

4. Deem will initiate B access.

Instructions in Sabre:

1. The agent with Sabre duty code 9 must login to perform the following entries; when complete, advise your implementation team this is complete and update the Deem Support Case that these steps are complete. In all steps XXXX is the agency pseudo city code:

2. Sign into Sabre with duty code 9 using SI9.

   1. AAA into the pseudo city used for Deem online bookings, as in AAAXXXX.

   2. Open B, C access from your pseudo city to Deem's Primary pseudo city (8CXA) and Support pseudo city (SO1A) with the following: W/TAAXXXX‡B8CXA, W/TAAXXXX‡C8CXA, W/TAAXXXX‡BSO1A, W/TAAXXXX‡CSO1A

   3. Open S access from your pseudo city to Deem's Primary pseudo city (8CXA) and Support pseudo city (SO1A) with the following: W/TAAXXXX‡S8CXA, W/TAAXXXX‡SSO1A

3. After these steps are complete, Deem returns S access to your pseudo city from Deem's Primary pseudo city (8CXA) and Support pseudo city (SO1A) as follows: W/TAA8CXA‡SXXXX, W/TAASO1A‡SXXXX

4. Deem also creates an agent sine of RC (or R1 if Deem is already in use by agency) to be used for online Sabre transactions.

5. Provide the Sabre Web Service credentials, as provided by Sabre. You can find these in the Deem Partner Dashboard in Configuration > Supplier Web Service Credentials; they include the pseudo city code, user name (EPR), and password. (Click for more about Sabre Webservices CSL.)

Worldspan Emulation

You must set up Worldspan emulation at the agency level to grant access to Deem and ETSI. Set up the booking PCC first and then the profile PCC per the following instructions.

Set up the booking PCC:

1. A manager at the agency location must enter KYA7KF the following to access the Access Screen (Deem’s pseudo city is 7KF). The screen then looks like the example below:

Open

2. Tab through the entire table and change the N in each area to a Y. When you reach the end, press Enter to open emulation. The screen looks like the following example:

Open

Set up the profile PCC:

1. A manager at the agency location must enter KYAYFI to access the Access Screen (ETSI's pseudo city is YFI). The screen then looks like the first example in the preceding instructions.

2. Tab through the entire table and change the N in each area to a Y. When you reach the end, press Enter to open emulation. The screen then looks like the second example in the preceding instructions.