|
Three classes of automatic verification systems are built into the pairing subsystem: legality checks, cost checks, and integrity checks. Legality checks operate on three levels: GUI level, solver level, and global level.
The pairing subsystem is based on the creation of scenarios. Pairing scenarios are created and optimized in four principle stages:
- Creation: Creates a new scenario for a given period and fleet, specifying parameters.
- Optimization: Runs solver to obtain an optimized pairing solution.
- Editing: Touches up optimized scenarios using an object-oriented editor.
- Complete Solution: Assembles a complete solution encompassing all fleets.
All of the steps above can be performed in either production mode or test ("what if") mode.
The Pairing subsystem features include:
- Planning period flexibility, up to a month in advance.
- Management of system by intuitive GUI.
- Editing of Gantt chart results with drag and drop features.
- Composing multiple fleet support solutions, based on the single fleet ( i.e., one fleet at a time).
- Management of scenarios and 'what if' scenarios.
- Adding of new fleets and ranks and modifying of existing fleets.
- Balancing of benefit and load for desirable pairings.
- Penalizes for violating crew availability and other constraints.
Solver
The Solver is the heart of EC0.2000. It generates the pairings using the parameters set in the scenario, which legally cover the flights while minimizing global costs. While running, the Solver issues informational messages viewable to the user. The solver executes in two stages. In the first stage, it generates a pairing solution and in the second stage, it generates an optimized pairing solution.
Solution Editor
The solution editor is a powerful, object-oriented editor, based on a Gantt chart object model. The solution editor allows the user to conveniently update and assemble scenario solutions. The editing screen is comprised of three sub-windows: a Pairings sub-window, a Duty Pool sub-window, and a Transfer Flights sub-window.
Updating or modifying pairings is easily performed by dragging and dropping objects between the three sub-windows. The user can check results at each stage of the editing by clicking in the appropriate sub-window with the right mouse button. A new pairing or new duty can be created at each stage.
Assignment Subsystem
The assignment subsystem automatically assigns the cockpit and cabin crews based on the pairing generated by the pairings subsystem. Similar to the pairing subsystem, the assignment subsystem is accessed using an intuitive GUI and includes a graphical editing capability for assignment editing.
The assignment subsystem also offers a mechanism for registering and satisfying crew requests and preferences.
Assignment Features
- Assures complete control to planners with real-time flexibility and preference assignments regarding special crew members and tasks (Rule Specification Language) for the rostering component.
- Allows for graphical or assignment editing (Gantt chart objects).
- Fulfills crew requests and preferences.
- Penalizes for violating crew availability and other constraints.
- Incorporates data from previous planning periods and manual decisions.
Interfleet Features
- Features a flexible setting of weekly violations limit.
- Allows airline crew to transfer via cargo flights.
- Finds the long cockpit duties and permits longer cabin crew duties.
- Considers cross-fleet and cross-rank objectives.
Airline Rule Handling
- Allows for the addition of new rules and the modification of existing rules.
- Supports airline's simulator training duties.
- Supports the airline's splitting rules.
- Reinforces airline's indicated routes.
- Applies base station crew availability constraints.
Airline Cost Structure Handling
- Takes into consideration lost revenues resulting from non-passenger reservations.
- Minimizes overtime, special compensation costs, hotel accommodations, and transportation costs.
- Minimizes use of other airline carriers.
- Accounts for per diem payments for night and time away from base.
| 
