 |
       |
||
|
|
|
 |
|
|
|
||||||||||||||||||||||||||
|
Synchronization |
||||||||||||||||||||||||||
|
The synchronization of the booking data performed by offices, agencies or individuals around the globe and based on the remote CRS host system is solved by automated tasks and numerous service applications that control the terminal emulation.
The data that comes back from the CRS as a response to generated inquiries is constantly parsed to be processed internally. This processing is oriented in two directions: updating data of planned schedules in the central information system and building the archive of booking dynamics. The first process is based on the transformation of a number of booked places in various booking classes into expected number of passengers in the corresponding passenger compartments. This data is then updated in the central information system which is thus constantly synchronized with real time booking dynamics. Since all applications access this refreshed data, all users and services are always well informed of the current state of booking. This reduces the need for dedicated CRS systems and connections. Booking Dynamics The second process transfers the data into several history files thus keeping track of booking dynamics that was taking place for every flight registered in CRS. This data can later be accessed by various analytical methods and tools in order to forecast the estimated number of passengers on certain flights in certain time periods or under other special conditions. If the data on booking dynamics by classes is evaluated using corresponding fares and tariffs several important information can be carried out, information that can have a significant influence on decisions about planned operations. Various service applications engaged in this process report their success into several log files that can later be accessed from the application. Classes view The Classes view displays booking curves for the 30 days preceding a selected flight’s actual departure. The horizontal axis represents the time dimension displaying dates on the top of the chart and corresponding days-till-operation at the bottom of the chart. The vertical axes represent the quantity of booking displaying a scale of numeric values that correspond to the number of seats/bookings. Each booking class is represented by its own color line. Different line styles can also be attached. The meaning of each line can be understood from the Legend window that can be opened separately and positioned anywhere on the screen. When the user hovers with the mouse over a line a tool tip window appears with information about corresponding class, days-till-operation and number of seats reserved. The user can easily turn the display of particular classes on or off for clearer picture and comparison, using the corresponding buttons on the toolbar. Nesting view The Nesting view is another view on the same flight that can be opened in the same or a new window. It is a combination of line and area chart. The line chart reflects the dynamics of booking for a certain nesting level, which means that now it represents a sum of all booked reservations in all classes that form the same nesting level on a certain day prior to operation. The area chart acts as a background which is composed of columns that represent areas of individual nesting levels valid on a particular day. The meaning of individual colors of these areas can also be understood from the Legend window. When the user hovers the mouse pointer briefly in the area that shows days remaining till the date of departure, in the lower part of the chart a small window is opened containing a detailed numerical report in text format. It contains a detailed specification of available and booked seats by classes and their nestings. This window simulates the classical output of the CRS terminal to make it easier for the user to combine digital and analogue presentation of information into integral view of observed operation. All views can also be used to analyze dynamics and trends that can be reconstructed from the archived data.  |
|
|||||||||||||||||||||||||
ClassX
