Glossary
Term |
Definition |
---|---|
ARC |
Airline settlement in USA by the Airline Reporting Corporation.
|
BSP |
Airline settlement in each other country by the IATA Billing Settlement Plan.
|
APO |
Abbreviation used to refer to the Travelport Apollo System.
|
Travelport+ |
Used to refer to Galileo or GCS.
|
Central Reservation System (CRS)
|
Airline and Auxiliary (Car Hotel and Tour/Cruise) Segment booking and Ticketing system. |
GDS |
Global Distribution System. A later version of a CRS. |
Agency Management Systems
|
Business Systems marketed by CRSs and other software companies to travel agencies. |
Point of Sale
|
Access by travel agent to the CRS and other databases. |
Front Office |
Functionality for booking records, passenger details, services booked, client documents and payments.
|
Middle Office |
Information on clients, suppliers and the analysis of costs and service information, sales returns and daily reports, MIS reports.
|
Back Office |
Accounting records, MIS reports, reconciliation, cash flow management and regulatory accounting. Term used mainly in North America.
|
Agency Management Systems |
As above but includes point of sale, and middle office in addition. Term used mainly in Europe.
|
Third Party Agency Management Systems
|
Third Party Agency Management Systems is the CRS term for Agency Management Systems supplied by non-CRS companies.
|
Data Hand-off/Interfaces |
The term applies to CRS derived hand-offs for accounting and MIS data used by travel agent’s systems.
|
MIR Products |
The term applies to Galileo data hand-offs for accounting and MIS data used by travel agent’s systems which access Apollo and Galileo.
|
MIR |
The data hand-off product from the Apollo and Galileo CRSs.
|
GMIR |
The data hand-off product from the Galileo CRS which MIR replaces.
|
Global MIR |
The application and mechanism which gives the ability to transmit MIRs between the Federation CRSs: Apollo and Galileo. |
XML MIR |
A handoff similar to MIR using the XML (Extended Mark-up Language) has been implemented in the Galileo rail environment for SBB/DB/SNCF only. |
TAT/E-TAT Ticketing |
Most ticketing supported by Galileo results in tickets being reported to a BSP for settlement. However, it is possible to configure agencies to issue tickets of an airline in such a way that reporting and billing occurs between the agency and airline with no BSP in between. In the old paper environment the ticket type used is a TAT (Transitional Automated Ticket – a form of the red carbon multi part ticket). Where an electronic version of this process is used Galileo refer to it as E-TAT. Where TAT or E-TAT is in use only one airline may be included in each AAT. |
Void/Spoiled MIR |
The term applies to the data hand-off of void data when a ticket has been issued (plated or un-plated) which is cancelled within a period of time specified by BSP. The ticket may or may not have been reported to BSP depending on the BSP RET hand-off cycle. To undo the void transaction, the term “un-void” is used. When an unused ticket or stock number has caused a void due to printer jam or electronic ticket failure, the term “spoiled” is used. |
Electronic ticket |
The term applies to the passenger purchase business process by which a ticket is issued electronically by an airline. |
Paper ticket |
The term applies to the passenger purchase business process by which a ticket is issued and printed by an airline or GDS on an actual piece of paper |
Virtual ticketing |
The commercial name for the Galileo electronic ticketing process made available to participating carriers. |
Section |
A set of data elements beginning with a Section ID, ending in two carriage returns. |
Item |
A set of data elements beginning with a Section ID, ending in a single carriage return. An item may repeat with different values. |
Line |
A set of data elements between carriage returns. A line can be of indeterminate length. |