Amadeus

Amadeus – TelMe Set Up Requirements
Step 1 - How to apply
Each supplier will need to arrange for API (Application Programme Interface)
access. This requires a Client Application User (CAU) form to be completed
by the agency and returned to their Amadeus account manager. There are 2
versions at the end of this document, a UK and a North America version for
guidance, but please ask your local Amadeus representative for the correct
version for your region.
You must arrange with your Amadeus Account Manager for a NEW Office ID
and a minimum of 20 AAA’s The required number of AAAs will depend upon
likely traffic levels in the TelMe booking engine.
Office ID settings and configuration required for the TelMe booking engine will
differ from those in current use within the agency, this is why we require a
new Office ID.
Once the new Office ID has been created, the CAU form can be submitted to
Amadeus. Amadeus will then incorporate the API.
The new Office ID will be for TelMe use only and where all TelMe bookings
are made. It is possible for TelMe to place these bookings on a different Office
ID as part of the booking process. However to do this, Extended Ownership
agreements (EOS) must be in place between the 2 office Id’s. The PNR’s will
be queued with a PNR Release command to the other Office ID. This avoids
the agency having to work an additional Office Id on a full time basis.
The new Office ID will need the following activated (these are also
indicated on the CAU form)
•
•
•
•
•
•
Validating Carrier (PBC) flag - ON
DIPSUM (D65) flag
- ON
24 hour clock
Name order set to be Chronological as the default is alphabetical
CIP Airline Plates enables so ticketing entries can be added for (File
Fare Ladder and Bureau products)
EOS agreements between the TelMe Office ID and where bookings are
to be queued to
Charges
Amadeus may make a charge for this access and may have a minimum term.
All commercials are strictly between the GDS and their customers. All GDS
charges are billed directly by the GDS.
Step 2 - Processing and confirmation
On receipt of the agent’s CAU form, Amadeus will take a minimum of 3 weeks
to process the application as Nice and German offices are both involved in the
process. Allow extra time for the new Office ID to be set up before
submitting this form.
Confirmation that the API is in place will be sent via Email or a CAU
confirmation form which may including support processes etc. Each Amadeus
region has a different format.
On receipt of either of the above, these details must be passed to
TECHSUPPORT@TELME.COM.
Confirmation will include
•
•
•
•
•
Corporate ID reference i.e. TelMe-TKTWindow
Password
Office ID where the API has been activated
Amadeus Environment i.e. Production / Practice Training
Encrypted – i.e. Yes/No
Without the above information TelMe cannot set up your Office ID for use
within our systems.
Step 3 - Set Up & Receiving Bookings
TelMe will need to know
•
•
Office ID where TelMe bookings are to be sent
Queue number (and Category code if used)
Please do not use queue numbers pre-assigned Amadeus airline/system
message queue numbers as these can cause issues.
Agents will need to
•
Continually work their bookings queues to take ownership of bookings
promptly after they have been made.
As the PCC is owned by the Travel Agent, it has to their responsibility to make the
necessary arrangements directly with GDS. TelMe do not have any authority to make
requests for changes on this Office Id on behalf of agents.
Amadeus
Amadeus API
CAU Questionnaire
Author:
Reviewed by:
Published by:
Steven LAWRENCE
Stuart BROOM
Amadeus Marketing (UK) Ltd
The Web House
106 High Street
Crawley
West Sussex
RH10 1BF
Copyright © 2007 Amadeus Marketing (UK) Ltd
All Rights Reserved. This document is the property of Amadeus Marketing (UK) Ltd. It
is an Amadeus confidential document. As such, it is the proprietary information of the
Amadeus Company and should not be duplicated, in whole or in part, distributed outside
of this company without the written consent of Amadeus.
Version Details
1.0
Original
Date
02/01/2007
Index ................................................................................................................5
1 Introduction ................................................................................................6
2 Company Information.................................................................................7
2.1
2.2
2.3
2.4
Commercial Contact in your Company ....................................................................... 7
Details of your Software Provider (CAP)..................................................................... 7
Network/Connectivity Contact in your Company......................................................... 7
Your Account Manager at Amadeus ........................................................................... 7
3
Application Information ..............................................................................8
4
Production Access ...................................................................................12
3.1
3.2
3.3
3.4
4.1
4.2
4.3
4.4
4.5
Application Usage ....................................................................................................... 8
Resource Management............................................................................................... 9
Amadeus API Functional Interfaces............................................................................ 9
Traffic Estimation ...................................................................................................... 10
Production System Connectivity ............................................................................... 12
Amadeus Office ID .................................................................................................... 12
Amadeus API Access Codes .................................................................................... 12
Production Network Connectivity .............................................................................. 13
Production Support ................................................................................................... 13
Appendix I - New Amadeus Office ID Request form ......................................14
Appendix II - EOS Request form....................................................................15
Appendix III - Additional Sign-In Request form ..............................................17
We differentiate between the different entities as follows:
CAP:
CAU:
CAP/CAU:
Client Application Provider (Application Owner/Developer)
Client Application User (Implementation and Use of Client Application)
Both (Developer and User of Client Application)
The Amadeus API CAU Questionnaire enables Amadeus to plan the resources needed
to plan your migration to the Amadeus Production environment as well as giving
important information about connectivity and capacity.
Please ensure this Questionnaire is completed as fully and as accurately as possible as it is used as
the primary source of project information (although we realise you may not be able to provide all
information in great detail).
Thanks and best regards,
The DAP & Development Team
Amadeus Marketing (UK) Ltd
Telephone:
+44 (0)870 895 7829 / 7822
E-mail:
dap@uk.amadeus.com
Company Name:
Mailing Address:
Correspondence Contact:
Business Title:
Telephone Number:
Mobile Number:
Fax Number:
E-Mail:
Hours of Availability:
Time Zone:
Company Name: Telme Online Ltd
Mailing Address: Suite 2 The Technology Centre, Rossmore Business Park,
Inward Way, Ellesmere Port, Cheshire, CH65 3EN
Correspondence Contact:
Business Title:
Telephone Number:
Mobile Number:
Fax Number:
E-Mail:
Hours of Availability:
Time Zone:
!
"
Craig Palfrey
Technical Support Manager
0151 348 8099
07734 758279
0151 348 8097
craigp@telme.com
9-5.30 Mon-Fri
GMT
#$
Company Name:
Mailing Address:
Correspondence Contact:
Business Title:
Telephone Number:
Mobile Number:
Fax Number:
E-Mail:
Hours of Availability:
Time Zone:
%
Name
E-Mail
&
'
(
!
!
) (
Application Name
Application Version
Application Type
Ticket Window
Application Environment
Application Description
(Please provide a brief
description of how you will
utilise the application and
provide a summary of the
different functional
modules)
Proposed Application
Users
General Public (Open User Group)
Travel Professionals (Closed User Group)
Corporate Users (Closed User Group)
$
#
1
2
3
4
5
6
×
Robotic (e.g. Ticketing, QC, Queuing)
Internet Booking Engine
×
Front Office Booking Tool
Web Based (Internet)
×
Client Server (Intranet / Extranet)
Use by Travel Professionals or direct consumers to make
bookings online.
!
"
%&
"
%'
Office ID (User ID)
#
Installations
Normally 1 Office ID
/×
/×
/×
7
8
9
!
*
'
(
When your application goes live into production, will you manage AAA resources1 centrally
or will they be allocated independently to the end-user Office IDs?
CAP managed resources
x
CAU managed resources
!!
+
Interface
PoweredAir
PoweredCar
PoweredDoc
PoweredFare
PoweredFare (VP2)
PoweredHotel
PoweredInfo
PoweredInsurance
PoweredLowestFare (MP3)
PoweredLowestFareTPF
X
X
X
X
Interface
PoweredPNR
PoweredPOR
PoweredProfile
PoweredQueue
PoweredTicket
PoweredTLAccess
Air
DocPrt
Fare
X
FarePlus
X
X
X
X
X
X
X
X
X
X
X
X
Interface
Hotel
Information
PNR
Queue
Ticket
Control
Cryptic (Command)
All checked with Steve
Lawrence 4/1/2007
Provide an exhaustive list of Cryptic entries (Command_GetScreen) that will be sent to Amadeus
by your application.
E.g. See certification report )SL 4/1/2007
(
/
6
)
0
5
+
&
0
&
5
,
1 23 1 +
*
-.
'
4
5
3
1 2+
'
4
5
X
X
X
X
X
X
!%
,
-
It is very important to fill out this section as accurately as possible as we will create your
Amadeus API environment based on these figures, which will affect the overall running costs of
the application: Please inform us if any of the information is likely to change.
!% . / 0
-
Please give your best estimation of the maximum number of concurrent accesses that you will
need. i.e. The maximum number of simultaneous conversations that will exist during your peak
period.
No of AAA
required
7
8
20 or 50
+
/
4
/
#
5
1
(
(
2
#
1-3% normally
general public
– front office
could higher
/ #3
(
/ # (
(
/
(
3
"*6
How many Amadeus API function calls will you be sending per day?
(If not known at this time, please estimate)
!% 7
"*
-.
Function
&
9
Number of Calls
Low Fare Search (VP or MP)
Availability
Pricing
PNR Creation / Modification
TST Creation
Ticketing
Others (please specify)
! % !+
Not non at this
time as new
system
N/A
30
20
??
??
??
??
&
'
4
-.
'
How many bookings do you plan to make through this application and what is the
forecasted growth over the next 3 years?
Year 1
Year 2
Year 3
%
$
%
%
Do you currently have Production Amadeus API access for another
application?
If YES please specify:
Corporate ID
User ID
Will you be using Encryption?4
%
/×
8
5
8
8
9
6
6:
If you have already requested a new Office ID, please
give details.
,
#
(
6
&-
<
&- 4
9
Normally this is only 1.Only the
new one created. All booked
PNR’s will then be queued to the
normal office id and PNR
ownership released to the normal
office id.
8
;
<
/
/
/
,
#
*
(
<
No, but ticket entries will need to be
added into bookings. No tickets
physically issued off this Office ID
See above
/ 6
Central System Sign In to be used when accessing the
system7 (e.g. 0001AA/SU)
JI0001AA/SU
%!
:
;
,
!
%
;
If you require new Amadeus Office ID(s) please complete the New Amadeus Office ID Request form: Appendix I
In addition to existing access rights, you may require specific access rights to the data of this and other Office IDs.
Please complete the Extended Ownership Security Request form: Appendix II
=
If you require additional sign-in(s) please complete the Additional Sign-in Request form: Appendix III
<
6
5
<
9
6
"84
(
6
And what is the existing User ID(s)?
<
&- 4
,
%%
"
(6
×
#
!
">
Connection Speed
!
, '
Please also ensure that the URL apiv2.amadeus.net (or apiv2-1a.amadeus.net if you are
using a leased line) and Port 20002 are opened on any firewall that you use.
%:
When your application runs in Production Software Providers are asked to act as first
level support for their Application Users to resolve any potential customer Front End
problems. Application Providers should then report Amadeus System problems to the
Amadeus UK Help Desk: helpdesk@uk.amadeus.com
!
<"
8
*9
The following is needed if you are requesting new Amadeus Office ID(s). If more than one Office
ID is needed please copy the table below as many times as required. You must provide the
information below for each Office ID you are requesting.
This information is only required if, in the Connectivity section of this Questionnaire, you
specified ‘YES’ to ‘New Amadeus Office ID required’
Company/Agency Full Name Mandatory
Address
Mandatory
City
County
Post Code
Country
Telephone Number
Fax Number
Ticketing
Back Office Accounting
Default Currency
Language
Default Sign
Additional Sign-In Required
Duty Code Required
IATA or ARC Number9
;.+--
Does this Office ID require
access to the data of other
offices (e.g. bookings, queue
messages, customer profiles
etc.)
Specific Office ID settings
(e.g. Ticketing Option, Value
Pricer, Accounting Office
AMID etc.)
If possible, please indicate en
existing Amadeus Office ID
whose settings may be used
as a model for your new
Office ID
Does your company have a
unique 2 character Amadeus
Corporate Code?
8
Mandatory
Mandatory
Mandatory
Mandatory
Mandatory
Mandatory
Default Value: EN
Mandatory
Default Value: 0001AA
YES – to add ticketing entries
only so full list of CIP plates to
be on this new Office ID please.
YES/NO
YES8/NO
Default Value: SU
5
9 ,
$
YES10/NO
PBC – Validating Carrier
DIPSUM(D65) – set to Y
FXC Value Pricer – ON
Name order – Chronological
24 Hour clock
TelMe existing Clients GCIU123WF
YES/NO
If you require additional sign-in(s) please complete the Additional Sign-in Request form, Appendix III
Mandatory for Ticketing Offices
(@
In addition to existing access rights, you may require specific access rights to the data of these and other Office IDs.
Please complete the Extended Ownership Security Request form, Appendix II
?
If YES, please indicate it
here
If NO, how many Office IDs
belonging to your
organisation are (or will be)
accessed through the
Amadeus API application?11
%
< -8 * 9
Extended Ownership Security (EOS) is Amadeus System functionality that protects the
integrity and confidentiality of data belonging to and indexed under individual Office
IDs.
Depending on the functionality of your Amadeus API application, you may need to
retrieve and/or update data belonging to other Amadeus offices. You may also require
that other offices have access to your own office data: for example you may need to
update bookings of your partner agencies through Amadeus API.
EOS functionality is most commonly used for data such as PNRs, Queues, and Customer
Profiles in addition to the ability to remotely sign-in to another Office ID.
Please complete the form below if you wish to grant access to your office’s data to other
Office IDs.
However if you require access to the data of other office(s), we kindly ask you to contact
the Local Security Administrator for each of these offices. Due to legal security rules
governing customer data in the Amadeus Central System we ask that you solicit these
access rights form the owner(s) of the data.
Please open access from my (new) Office ID: __________________ to the following
Office ID(s) and/or Corporation(s) for the type of data indicated below:
Office ID(s) to which the access should be opened: __________________
__________________
__________________
Corporation(s) to which the access should be opened:
__________________
__________________
__________________
Data type
Individual Bookings (PNRs) retrieved
by Record Locator only
Individual Bookings (PNRs) retrieved
by ANY method
Group Bookings (PNRs) retrieved by
Record Locator only
Group Bookings (PNRs) retrieved by
ANY method
PNR Responsibility Office
Customer Profiles
11
Read
&-
Access Mode
Write/Update
No access
YES
NO
NO
YES
In future
maybe
For identity and security reasons it is advisable that organisations with a minimum of 10 Amadeus Office IDs request a
unique Amadeus Corporate ID. A Corporate ID is made of a Corporate Code (2 characters) and a Corporate Qualifier
(assigned by Amadeus)
Queues
YES
Allow updates to PNR responsible Office ID (i.e. take over the ownership of the PNR):
YES/NO
Allow remote sign-in to my Office ID:
YES/NO
Other Requirements: ___________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
___________________________________________________
:
<
(<
*9
When the Amadeus Central System is accessed through an Amadeus API application, the default
sign-in 0001AA is used. The default duty code is ‘SU’.
Depending on the functionality of your Amadeus API application, you may require your
application to use other sign-ins.
A
!
+
Sign-In12
User Name
(5-10
characters)
Password
Protected?
Ability to use this
sign by remote
location to sign-in
,
Allow update of responsible Office ID for PNRs (i.e. take over ownership of the PNR):
YES/NO
Allow remote sign-in to my Office ID:
YES/NO
Other Requirements: ___________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
___
12
Sign-in code is made of 4 digits and 2 letters, e.g. 1234AB. The 4-digit code must be unique per office, i.e. no other
sign-in code may exist for a given office with the same 4-digit code. It is advisable that the 2-letter code is also unique.