|
|
The solution is closely connected to ACROSS - Crew Pairing And Rostering application that enables control and managing of all crew activities using mainly manual procedures.
The process begins with transfer of schedules and other data that is crucial for generation into a separate local work database. Only a segment that is relevant for the selected date period of the plan is transferred.
The user then has to define fleet objects, target crew groups, methods to be used, and several other parameters that will guide the system when executing the selected operations. The system takes data of crew members’ personal history and all limitations stipulated by civil transportation flight regulations or any additional corporate or union regulations from the common production database.
The user can then choose to run several single operations or load a scenario that joins more pre-selected operations and executes them together as a group of consecutive tasks.
After the plan is generated, the user can check its successful completion as well as monitor new data and reports in several views that can be quickly reached using the bottom tabs of the main Results window.
After the generated plan is confirmed, its data can be transferred back from the local to the production database and become available to all users.
Monitoring the Results
After the operation has been completed, the results can be monitored immediately in a way that is already familiar from other Caspis Airline Suite applications: several graphical windows display various aspects of the completed operation.
In this way the user can monitor crew pairing results in the Flight Orders window, all planned crew members' activities in the Crew Members window and all planned standby reserve crew rosters in the Reserve Crew window.
All objects represented within these views are displayed and behave in the manner already known from ACROSS application. Even their colors and other properties are taken from the same user-specified configuration.
Flight Plan
The Flight Plan view displays the final results of automatic crew pairing and rostering in the form of a text table. The table is sorted by dates, aircraft types and flight orders, and equipped with corresponding flight and cabin crew members together with their reporting, block and duty times.
Limitations
All limitations applied to selected members can be monitored in the Limits window as graphic bars displaying block and duty time limits.
Check Report
The Check Report collects all critical information about generated flight orders and crew members’ limitations, and presents it sorted by the days. This enables the user to quickly discover the critical issues, correct adequate parameters if necessary and repeat the process of generation.
Statistics
Another valuable report that is available after the generation has been completed is the Statistics report. This report displays several tables with statistical values that help discover the success or eventual problems of separate operations, for instance, the share of flight legs successfully paired into flight orders, the number of crew members allocated on flight duties, etc. All this data is displayed by days as well as by totals, averages and minimum / maximum values.
All information on legs that could not be paired or flight duties that could not be fulfilled with adequate crew members is displayed in separate tables using different colors. This ensures that only a fully verified plan will be released into production.
Running Operations or Scenario
The main operations that can be executed independently for a selected fleet or deck crew are Pairing generation, Rosters generation, Standby generation and Off days generation. Various combinations of these tasks can be grouped together using a special Scenario setup dialog and saved under meaningful names to be called and executed as a batch job.
Carefully designed scenario enables a fully automated process and replaces once tiresome and error-prone routines with few mouse clicks, reducing days of manual work into minutes...
During the execution the system keeps track of all events and informs the user of the results of separate tasks. All this information is documented in the Log file report window.

|
|