333
edits
Changes
Jump to navigation
Jump to search
Created page with "The '''Global Distribution System''' (GDS) is a specialized computer reservation system (CRS) designed for search, booking and sale of ser..."
The '''Global Distribution System''' (GDS) is a specialized computer reservation system (CRS) designed for [[Search (Air tickets)|search]], [[Booking|booking]] and sale of services. Initially, GDSs were developed by [[Airline|airlines]] for their own needs, but as the market developed, they spread among travel agencies, becoming an important tool for real-time sales of services. Modern GDSs have the ability to sell air and rail [[Ticket|tickets]], provide services for arranging insurance contracts, hotel bookings, car rentals, etc.
== GDS in Websky ==
Websky unifies work with various GDS and other air content providers, automates the majority of template operations, adds customizable management options and logic for working with suppliers like:
* [[Sabre|GDS Sabre]]
* [[Travelport (Galileo)|GDS Travelport (Galileo, Galileo uAPI)]]
* [[Amadeus|GDS Amadeus]]
* [[Mystifly|GDS Mystifly]]
* [[Sirena Travel|GDS Sirena Travel]]
* S7 Siberia Airlines booking system (hosted by [[SITA Gabriel]])
* [[API AviaCenter (Special fares)]]
* [[API Travelfusion]]
* [[Nemo Inventory]]
== How to connect to the GDS ==
For searching, booking and other [[agency]] operations, the agency must contract with one or more GDSs and obtain connection IDs from them.
The agency connects to the GDS through the '''Nemo Connect''' server, which unifies access to content from different airline providers and provides a single set of features for flight searches and bookings. GDS connection requisites are set and stored directly in Nemo Connect. [[User#User types in Websky|Administrator]] in Websky creates an agency account, enters the connection requisites for working with the GDS in Nemo Connect, informs the agency of the '''Login''', '''Password''', '''UserID''' for connecting to the Nemo Connect project and the numbers of [[Nemo Connect requisite packages|requisite packages]] for working with the GDS.
To connect an agency to GDS:
# Establish a contract with GDS for a list of supported services and their settings. GDS generates [[PCC]] and other identifiers and sends them to the agency.
# Pass the PCC identifier and specific GDS interaction settings (region of operation, [[currency]], GDS requests and versions, restrictions, etc.) to the Websky administrator. Based on this data in Nemo Connect, Websky staff will enter [[Nemo Connect GDS connection requisites]] and [[Nemo Connect requisite packages]]. It is assumed that at this point, Websky administrators have created an agency account and given you [[Login]], [[Password]] and [[UserId]] (agency ID number).
# Set up Websky [[GDS connection requisites in Websky#Creating Websky connection requisites|GDS connection requisites]] via the ''Nemo Connect'' connector, using the profile identifiers in Nemo Connect. You can learn about how to properly create connection requisites in [[GDS connection requisites in Websky]]
# Create a [[Websky requisite packages#Creating Websky requisite packages|requisite package in Websky]] where you select the GDS connection requisites for the search, booking and ticketing process you created in step #3.
# Select the requisite packages for searching (for the whole agency or for an individual user) in the section '''Product control → Avia tickets→ Processes→ Search process → Fine tuning'''.
== See also ==
* [[GDS connection requisites in Websky]]
* [[Websky requisite packages]]
* [[GDS connection requisites in Nemo Connect]]
* [[Nemo Connect requisite packages]]
* [[Connection requisites]]
* [[Amadeus]]
* [[Sabre]]
* [[Сирена Трэвел]]
* [[Travelport (Galileo)]]
* [[SITA Gabriel]]
== Useful links ==
* [http://www.amadeus.com Amadeus]
* [http://www.travelport.com/lob/gds/galileo.aspx Travelport (Galileo)]
* [http://www.sabre-holdings.com/ Sabre]
* [http://www.sirena-travel.ru/ Sirena Travel]
* [http://www.sita.aero/ru SITA Gabriel]
== GDS in Websky ==
Websky unifies work with various GDS and other air content providers, automates the majority of template operations, adds customizable management options and logic for working with suppliers like:
* [[Sabre|GDS Sabre]]
* [[Travelport (Galileo)|GDS Travelport (Galileo, Galileo uAPI)]]
* [[Amadeus|GDS Amadeus]]
* [[Mystifly|GDS Mystifly]]
* [[Sirena Travel|GDS Sirena Travel]]
* S7 Siberia Airlines booking system (hosted by [[SITA Gabriel]])
* [[API AviaCenter (Special fares)]]
* [[API Travelfusion]]
* [[Nemo Inventory]]
== How to connect to the GDS ==
For searching, booking and other [[agency]] operations, the agency must contract with one or more GDSs and obtain connection IDs from them.
The agency connects to the GDS through the '''Nemo Connect''' server, which unifies access to content from different airline providers and provides a single set of features for flight searches and bookings. GDS connection requisites are set and stored directly in Nemo Connect. [[User#User types in Websky|Administrator]] in Websky creates an agency account, enters the connection requisites for working with the GDS in Nemo Connect, informs the agency of the '''Login''', '''Password''', '''UserID''' for connecting to the Nemo Connect project and the numbers of [[Nemo Connect requisite packages|requisite packages]] for working with the GDS.
To connect an agency to GDS:
# Establish a contract with GDS for a list of supported services and their settings. GDS generates [[PCC]] and other identifiers and sends them to the agency.
# Pass the PCC identifier and specific GDS interaction settings (region of operation, [[currency]], GDS requests and versions, restrictions, etc.) to the Websky administrator. Based on this data in Nemo Connect, Websky staff will enter [[Nemo Connect GDS connection requisites]] and [[Nemo Connect requisite packages]]. It is assumed that at this point, Websky administrators have created an agency account and given you [[Login]], [[Password]] and [[UserId]] (agency ID number).
# Set up Websky [[GDS connection requisites in Websky#Creating Websky connection requisites|GDS connection requisites]] via the ''Nemo Connect'' connector, using the profile identifiers in Nemo Connect. You can learn about how to properly create connection requisites in [[GDS connection requisites in Websky]]
# Create a [[Websky requisite packages#Creating Websky requisite packages|requisite package in Websky]] where you select the GDS connection requisites for the search, booking and ticketing process you created in step #3.
# Select the requisite packages for searching (for the whole agency or for an individual user) in the section '''Product control → Avia tickets→ Processes→ Search process → Fine tuning'''.
== See also ==
* [[GDS connection requisites in Websky]]
* [[Websky requisite packages]]
* [[GDS connection requisites in Nemo Connect]]
* [[Nemo Connect requisite packages]]
* [[Connection requisites]]
* [[Amadeus]]
* [[Sabre]]
* [[Сирена Трэвел]]
* [[Travelport (Galileo)]]
* [[SITA Gabriel]]
== Useful links ==
* [http://www.amadeus.com Amadeus]
* [http://www.travelport.com/lob/gds/galileo.aspx Travelport (Galileo)]
* [http://www.sabre-holdings.com/ Sabre]
* [http://www.sirena-travel.ru/ Sirena Travel]
* [http://www.sita.aero/ru SITA Gabriel]
