Professional Documents
Culture Documents
Main page
Contents
Crew scheduling
Featured content From Wikipedia, the free encyclopedia
Current events
Random article This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced
Donate to Wikipedia
material may be challenged and removed. (February 2011) (Learn how and when to remove this template message)
Wikipedia store
Crew scheduling is the process of assigning crews to operate transportation systems, such as rail lines or aircraft.
Interaction
4 Parts [ edit ]
Although not a "rule", We can describe at least 4 parts of the equation that are ingested by the computational process:
In crew scheduling the rules and constraints are typically a combination of:
government regulations concerning flight time, duty time and required rest, designed to promote aviation safety and limit crew fatigue,
crew bid requests, vacations,
labor agreements
aircraft maintenance schedules
crew member qualification and licensing
other constraints related to training
pairing experienced crew members with more junior crew members
returning crew to their base at the end of their trip (called deadheading)
The first phase in crew planning is building the crew pairings (also known as trips, rotations, among other popular descriptions). This process pairs a generic crew member with a flight so that at the
end of this process all aircraft flights are covered and all trips (combination of flights starting at a crew base and returning to that crew base or co-terminal are crew legal. The next step is the
allocation of those trips to the individual crewmember. For the US, Canada and Australia, seniority generally rules. The two processes (which are completely different) are referred to as bid lines and
preferential bidding. In seniority order, pilots bid for either a line of time (bidline) or trips and days off (preferential bidding. these are awarded based on seniority and modified only when their
selections have already been taken by a more senior crew member (bidlines) or their trip and day off selections (preferential bidding) do not make up a complete line (hours, days off, etc. parameters
agreed to by the company and the union). The senior folks have more time off, better choice of time off and fly better trips than the junior crew members, generally speaking. In the US, this is
considered fair. For European airlines and other airlines in the rest of the world, the allocation process is completely different. The company builds the pilot schedules directly to meet their needs, not
the pilot's needs. Before assigning a single trip, the schedulers put all planned absences (vacation, training, etc.) onto the crew members' schedule. Only then are trips assigned to the individual
crew members. As such, fairness means that the most senior captain and the most junior captain have the same amount of duty time, block hours, night time, time away from base, layovers, expense
pay, etc. in a given schedule period. Seniority is out and all work is completely homogenized. For them, anything else is unfair, undemocratic. Slowly over the last thirty years, foreign airlines using the
"no seniority" rostering system have allowed some measure of seniority to creep into the allocation process from pilots who may now ask for a specific day off or trip once a quarter or make multiple
requests within a schedule period. Although this may sound very much like preferential bidding, it is not. The disparity between junior and senior crew members is still very limited and thus
achievement of your choices is limited.
Disruptions [ edit ]
Additional unplanned disruptions in schedules due to weather and air traffic control delays can disrupt schedules, so crew scheduling software remains an area for ongoing research.[1]
Linear programming
Column generation
Tabu search
Fatigue Avoidance Scheduling Tool
References [ edit ]
Categories: Aviation safety Optimization algorithms and methods Transportation planning Transport safety Scheduling (transportation)
Privacy policy About Wikipedia Disclaimers Contact Wikipedia Developers Cookie statement Mobile view