CTI products are designed for specific applications within the TTL sector but are also flexible enough to adapt to different business processes.

TPAC Pairing


TPAC Pairing is a module of the TPAC suite that automatically creates sets of optimised crew pairings for vehicle schedules. TPAC is a suite designed to provide planning and operations control capabilities for crew and equipment in transport applications.

What is Crew Pairing?

Crew pairing is the process of pairing operating crews with legs of a vehicle schedule such that:

  • All legs in the schedule are crewed.

  • The crew start and end each pairing at their base.

  • All legislative and industrial work rules are obeyed for each pairing.

Challenges in Crew Pairing

Crewing of a transport schedule would be a simple problem if crew could work non-stop like vehicles - it would simply be a matter of the crew staying with the vehicle all day. Vehicles like aircraft and trains are expensive assets whose utilisation must be maximised, however, so they cannot stand idle while their crew takes a break. For such equipment, it is necessary for crew to be paired with different vehicles over the course of a duty period.

Furthermore, when it is not practical for a vehicle to return to a central point whenever there is a crew change, then it is necessary to produce crew pairings that change vehicles at intermediate ports or stations. The resulting pairing creation process thus becomes much more complicated than a simple rostering problem, as it is necessary to have a crew waiting at these points ready to take over from the crew whose duty is finishing.

For long haul schedules, a pairing might also incorporate one or more "layovers" - that is one or more nights of rest in a hotel between duties. Pairings may also include transfers via other modes of transport or legs operated by different operators, and other may also include duties such as training, shunting, standby duty etc.

A good set of crew pairings has the following characteristics:

  • Every leg of a schedule is paired with only one crew, i.e. within a pairing there should be few or no "paxing" or "deadheading" legs where a crew are travelling in order to be in position for operating another leg. Such legs are unproductive, and may also incur an additional cost.

  • Each crew works for close to their maximum permitted work time each day, thus minimising the number of crew required to crew the schedule when rostering is performed.

  • There are as few vehicle changes as possible, as these mean that disruptions to one vehicle can cause disruptions to other vehicles. This increases the robustness of the crew pairing solution.

  • Vehicle changes have some slack time built in to minimise the flow on effect of disruptions, but not too much as then the crew is being paid to wait around.

  • All legislative and company rules regarding maximum work times, required meal breaks etc. are obeyed.

About TPAC Pairing

TPAC Pairing automatically creates a set of optimised crew pairings for schedules that are too large for manual pairing creation. It ensures that the crew pairings have a minimum cost subject to the constraints given by the crew work rules and the desire for a solution that is robust to disruptions.

How TPAC Pairing is Used

It can be used in several ways:

  • Pairing generation for planning.

  • Pairing generation, repair and assignment for just in time crew assignment.

  • Repair of disrupted pairings.

Manual pairing generation may be performed at any stage to cater for special requirements such as training or charters.

Technology

TPAC Pairing uses advanced optimisation technologies to minimise the total cost of crewing the given legs given the required constraints. Cost is defined as the actual cost (crew pay, hotels, allowances, transfers etc.) plus penalties.

The penalties are set by the user, enabling them to choose the trade off between the various rules. There are several classes of penalties:

  • Penalties for pairings that are not robust.

  • Penalties for solutions that are inequitable between bases.

  • Penalties for pairings that are legal but undesirable from the perspective of the crew.

Features

  • Production of robust patterns through:

  • Minimisation of vehicle changes.

  • Penalties for tight connections.

  • Penalties for duty or operating close to legal maximums.

  • Minimisation of number of pairings if variable crewing required on each leg.

  • Flexibility:

  • Optimisers can generate an entire solution, improve existing solutions or repair solutions after schedule changes.

  • Extraction and optimisation of weekly and daily schedules available to improve solution regularity.

  • Users can direct the optimisers using additional constraints if desired.

  • Supports ground travel from base to alternate ports/stations or between nearby ports/stations.

  • Supports international time zones and currencies.

  • Rules can be changed for each run to enable "what if" scenario testing:

  • Adherence to legislative and industrial rules.

  • User configurable costs.

  • Penalties may be added to allow soft rules and to indicate desirable properties of solutions.

  • Selectable equity of pay and hours between crew bases.

  • Selectable limits on crew from each base for each leg.

  • Different rules may be used for different bases crewing the same legs.

  • Different rules may be used for different crew sizes.

  • Choice of user configurable rules or more than 200 standard rules to choose from.

Reporting

A range of standard reports give key metrics to enable evaluation of the quality of solutions.

screen capture

Performance

  • Suitable for large problems (tens of thousands of legs).

  • Scalable for solution of sub-problems on multiple CPUs and/or machines.

Architecture

  • UNIX (e.g. Linux or SUN/Solaris) server with standard XML interface.

  • User interfaces: single or dual screen, Spider (train) graphs and/or Gantt charts.

Architecture

Planning

The overall planning process starts with downloading the schedules from the scheduling system's database. The number and categories of crew required for each leg can be specified in the downloaded schedule, or specified separately according to equipment type and configuration.

Information for ports/stations can be downloaded or maintained locally:

  • Port/station codes, names and time zones.

  • Currencies.

  • Exchange rates.

  • Meal allowances.

  • Available hotels, rates for various room types and transport costs.

  • Co-terminals.

Crew requirements from carry-in pairings starting in the previous bid period are subtracted from the required crew. Manual pairings are then optionally generated to cater for any special requirements (e.g. training, special charters), and the crew for these is also subtracted from the required crew.

The schedule is then prepared for optimisation. This may involve extracting a weekly schedule containing those legs that are repeated every week for the schedule period, and a daily schedule containing those legs that are repeated for most days of the schedule period. Separate problems are prepared for each crew type - e.g. a separate problem for each fleet that requires different skills to operate it.

Extra legs may be added to the schedule for travel using the services of other companies for paxing/deadheading purposes.

If maximum schedule regularity is desired, the global optimiser is used to produce a solution for the daily problem, which is then improved using the local optimiser. Pairings from the daily solution that match well with the weekly schedule are fixed in the weekly solution, and the remaining legs in the weekly solution are then used as the weekly problem to be solved. The weekly problem is then optimised using the global optimiser, and this solution is improved using the local optimiser.

A similar process to the above generates a solution for the entire bid period using the weekly solution as a starting point. For schedules with insufficient daily regularity, optimisation can start by solving the weekly problem.

If regularity is not important, the schedule for the entire bid period may be generated in one step, omitting the daily and weekly steps.

The resulting optimised solutions then have pairing numbers assigned to each pairing, after which reports are printed and the result is exported to the pairing assignment system.

The optimisation process can be started or restarted from any point. The optimiser can be directed by changing the amounts of penalties applied to undesirable pairings, or by adding in required, prohibited or suggested connections.

Just In Time Crew Assignment

Just in time crew assignment is a way of coping with a situation where significant changes to schedules often occur after work days have been assigned to crew members. The crew members are assigned blocks of working days according to the planned pairings, but the actual legs operated by each crew member are only finalised a few days in advance of the start of the block. This process is repeated each day.

In this case, information about each crew member's preferences, work history and assigned work days is also provided to the system. The optimisers then assign pairings to individual crew members at the same time as pairings are generated. This allows the preferences of the crew members to be taken into consideration when generating the pairings.

To increase the speed of the optimisation process, only a small number of days in the future are considered in these problems. Also, the previously planned pairings are used as suggestions to the optimiser.

Repair of Disrupted Pairings

On the day of operations, planned pairings may be disrupted by delays and cancellations. TPAC Pairing automatically detects which pairings are now illegal, and modifies existing pairings or generates new pairings to enable crewing of the disrupted schedule.

User Interface

The user interface enables initiation and monitoring of optimisation runs, review of solutions and interactive pairing creation or modification.

screen capture

Interactive pairing creation and modification is performed using a graphical editor. Many options are available for selection of displayed ports, legs and pairings to reduce screen clutter. Pairings are colour coded from a selectable palette. Clutter is also significantly reduced by the optional dynamic display of legs suitable for adding to the pairing as the pairing is built.

screen capture

Further Information

You may also wish to read the brochure ( PDF).