MARS is the Mercator Airline Reservations System hosted in Dubai, providing the best customer service, functionality and ease of use whilst maintaining the highest levels of cost efficiency. Emirates Airline, and other major carriers such as Sri Lankan, Air Algerie, Yemenia and Kuwait Airways are currently using the system.
|
| |
| | | Key Business Benefits | | Advanced functionality, unmatched by similar systems available in the market. | | Fully integrated Departure Control (MACS) with IATCI available to provide maximum support to airlines. | | Full integration with frequent flyer, revenue accounting, revenue management, operational systems ensures a seamless flow of information driving better customer service. | | High level access to all GDSs such as Abacus, Sabre, Galileo, and Amadeus. | | Comprehensive online help function. | | Dedicated and experienced implementation teams ensure quick on-site support to reduce post implementation teething problems. | | Integrated modules such as Super Agent and E-ticketing, advanced reporting mechanism for operation and management information needs. |
| | | Key System Features | Selling and distribution. | | Direct access for availability, seat maps, FLIFO. | | Interactive access for selling, seat maps and seat reservation. | | Reverse host access capability. | | CLAIM PNR facility. |
| | | Revenue Management / Class Nesting Functions | Priority waitlist assignment - airline specific set of rules can be set. | | Automatic waitlist confirmation in line with the inventory management system. | | Full system snapshot, downloaded daily to a revenue management system. | | Automatic upload of flight optimisation data from the revenue management system. | | Revenue oriented post departure processing for no shows/go shows/offloads/upgrades/downgrades by revenue class; accurate booking figures for down line stations. | | Selling of space supported through various AVS agreements, FCA/SANDR/NAVS/MAS. | | AVS agreement allows redemption classes' AVS to be exchanged with FFP partners |
| | | Nesting | Several different types of class nesting support available, such as parallel and serial. | | ROOTY (complex or mixed nesting structure). | | Hierarchy allowed for any sequence of classes / leg. | | Planning and controlling parameters per leg. | | Option to control the inventory system with any RMS or manually. | | Automated download / upload of sales to / from any RMS. | | Class types for groups / individuals / blocked space. | | Leg allotment per class. | | Leg overbooking profiles per class. | | Leg / segment no-show profiles per class. | | Leg maximal / minimal sales limits per class. | | Sophisticated thresholds for booking / cancellation trends. |
| | | Code Sharing and Flight Complexes | The three major AIRIMP options for code sharing, using free sell, are supported. | | Allows participating hosted carriers a specialised code share - flight complexing - to maximise revenues and get better operational level control. | | Any number of marketing flights is permitted for the operating flight. | | Duplicate flights table maintains relationship between the operating / marketing flights. | | At the time of complexing, all leg figures are synchronised, whilst all segment seats sold are kept separately. |
| | | IPassenger Lists / PNR Functions | Numbered passenger lists with short programmable entries for PNR retrieval as well as with numerous selection options. | | Guided booking process where customer preferences are extracted from the customer information database and imported directly into the PNR being created. | | Frequent flyer tracking function at booking time as well as departure feed to the FFP system.
Automatic transfer of bookings to the DCS. | | Dupe suspect handling using XPS. | | Automatic policing of pending confirmations in PNRS. | | Easy to read PNR handouts in five languages. | | Special fields in PNR as well as a central table to allow tracking of split PNRS. | | PNR fields maintain 'expected show up rate' as well as 'net revenue' for groups. | | Support for "claim PNR" function. | | Short entries to allow availability / passenger name list / seat mask displays from the PNR segments. |
| | | Various Queue Functions | No duplication of PNRS on queue. | | Possibility of sorting PNRS on queue using various criteria. | | Removing all PNRS / messages from a city queue. | | Moving all PNRS / messages from one city queue to another. | | Ability to select for display, any of the last 10 messages from the supervisory / message queues. |
| | | Flight Schedules and Availability | System supports circular flights. | | User friendly schedule information displays. | | Availability displays allow header information in addition to marketing facts. | | The marketing facts file allows:
- | Support for user groups. | - | Attachment of facts per country, city pair or flight number. | - | Every host airline to have its own file. | - | Unlimited number of display facts. | - | STAR3 package, which allows automatic generation and loading of your own 'Transfer Connection Files' in an offline mode. |
| | The availability package allows:
- | Direct flights out of / into a city. | - | Own neutral availability database if so desired. | - | Support of last seat availability. | - | Easy switching facilities between biased and neutral products. | - | Buffering of seats in the interactive selling environment. |
|
| | | Participating Vs Non-Participating Hosted Carriers
The MARS multi-hosted environment permits the possibility of hosted customers to have either a participating level agreement among themselves or to be completely independent of each others operation. In the former case, two or more participating carriers can enjoy the flexibility of operating from different logical system partitions but still have limited access to each others data such as flights, PNRS, passenger lists and inventory lists.
If there is no participation among two or more hosted carriers, MARS allows their logical partitions to act as a physical demarcation across which absolutely no access is permitted. This is similar to the non-participating carriers being hosted on different hardware / physical locations.
| | |
|
|
|
