Destination dispatch should be no worse than standard up/down buttons, right (at least in theory)? It provides additional information about the destination, but it should be possible for that information to be interpreted as if it were just an up/down button press, so RSR could still be used. I have a feeling a better algorithm could in fact make destination dispatch slightly better than RSR... or am I missing something?
Of course, user error is also a factor, so this isn't accounting for people not understanding how to use it and making things worse that way.
As the article says, the problem with destination dispatch is that it 'locks in' an elevator. The passenger gets told at call time what elevator to go to, and it can't change that mid flight. RSR has the advantage that the passenger has no idea which elevator will come, and so RSR can change the elevator they will get in real-time as conditions change. This was an insight I had not considered before reading the article.
Seems like the obvious solution is to put a bank of floor numbers above each elevator and when one arrives the floors it has been assigned to go to light up and the people going to them get in that one. So each person only needs to quickly to see if it's going to their floor or not, much like they need to look to see if it's going up or down. Then you can dynamically dispatch elevators right up until 5s or so before it arrives at a floor, with full knowledge of not just up/down but also destination. (And hell make 'em say how many people are in their party too so you also know how many people are traveling and where.)
dperfect · · focus · HN ↗
Of course, user error is also a factor, so this isn't accounting for people not understanding how to use it and making things worse that way.
brd529 · · focus · HN ↗
joshjob42 · · focus · HN ↗