Constraint Relaxation Order: Where Replans Actually Lose Time
It's 6:42 on a Tuesday. A route that looked rock solid at 5 a.m. just lost a driver to a breakdown, and the dispatcher's screen is spinning while the system tries to rebuild the day's outline. You've seen this prior—the replan that takes forever, the one that makes everyone reach for a whiteboard and a phone. Most groups blame the optimizer. But in my experience, the real culprit is often the queue in which constraints get relaxed when the original roadmap falls apart. Get that group off, and you're not just slow—you're also getting worse solutions than you need. Get it right, and you can shave minutes off every replan loop, sometimes without touching the solver's internals.