Re:Southwest cancels 5,400 flights in less than 48 hours
by bombcar on Tuesday December 27, 2022 @12:20PM
(#34150944)
The easiest way to solve the tension is probably to add additional money into the mix - the hard to fill shifts get paid a bonus, etc. someone would figure out how to game it of course but you already have this somewhat when overnights pay more.
Re:Southwest cancels 5,400 flights in less than 48 hours
by linuxftw on Tuesday December 27, 2022 @12:30PM
(#34151094)
I was thinking similarly. Have people bid on shifts.
Re:Southwest cancels 5,400 flights in less than 48 hours
by thenewwazoo on Tuesday December 27, 2022 @01:51PM
(#34152207)
Pilots do precisely this already.
Re:Southwest cancels 5,400 flights in less than 48 hours
by pc86 on Tuesday December 27, 2022 @03:07PM
(#34153142)
Sort of. They bid based on seniority. So if you've been there forever you get the cushy flight that pays a ton. If you just joined to get the worst shift nobody wants (because it's the last one left).
Re:Southwest cancels 5,400 flights in less than 48 hours
by bombcar on Tuesday December 27, 2022 @07:42PM
(#34155993)
What you add is bonuses that grow the longer a shift hasn’t been assigned (somehow).
Of course this all works best when you have more employee time than you need - it’ll never solve a true shortage.
The two classes of solutions that I considered where optimization solvers (see Gurobi Optimization for example), and meta-heuristics (see the book Metahueristics: From Design to Implementation). If I remember correctly, the people at Gurobi started at a previous company which was spun out of an airline, but I might be confused. All the algorithms in both classes of solutions are so nuanced that it can take years to begin to grasp how their strengths and weaknesses interact with your particular scheduling challenge, and how the way you formulate the problem interacts with the ability of the algorithm to solve it.
All that said, the real problem for me was a human one: If you produce a viable schedule X, the organization involved will always want to alter the rules to stretch the available resources to cover more, and simultaneously all the schedule staff will want more flexibility and nuance in expressing their preferences. You, as the author of scheduling software, are caught between them. Neither side is ever happy with the result.
I occasionally daydream about revisiting resident scheduling (I don't recommend it, the people who use your software leave every year, are not business oriented, and don't understand the complexity of the task until they've tried it on their own their first and only attempt). If I did, I would focus less on algorithms, and more on incentives to reconcile the tension between the organization, which wants to cover the most shifts with the fewest people at the cost of flexibility and preferences, and the staff, who want more flexibility and more preferences satisfied. I think that is the core problem at a business level.