Operations Research

Ports are already full of automation. Cranes move containers, AGVs follow routes, software coordinates flows, dashboards blink reassuringly at managers who are paid to pretend that blinking equals control. Then one terminal changes its layout, closes a road, adds a vehicle restriction, or introduces a new safety corridor. Suddenly the “automated” dispatching system needs engineers, operations researchers, domain experts, test scripts, model reformulation, solver debugging, and several meetings where everyone discovers that “just adjust the rule” was not, in fact, just. ...

Warehouse. That is a useful place to begin, because combinatorial optimization only sounds abstract until someone has to decide which trucks leave first, which jobs enter which machines, which items fit into which containers, or which solver should be trusted before the deadline starts laughing. In those systems, the hardest question is often not “What is the answer?” It is “Which method should we use for this particular instance?” One algorithm works beautifully on one family of cases and then quietly embarrasses itself on another. This is not a personality flaw. It is the normal condition of optimization. ...

Trucks do not care whether your routing algorithm is elegant. They care whether the vehicle arrives, whether the route violates capacity, whether the dispatch plan survives a late order, and whether the whole thing can be recomputed before someone in operations starts calling the system “that AI toy.” Optimization has always lived in this unglamorous place: close enough to mathematics to look pure, close enough to reality to be messy. ...

TL;DR for operators The paper is useful because it gets the hierarchy right: the optimizer decides; the LLM explains, configures, contextualizes, and packages the decision for humans.1 That is not a small distinction. It is the difference between a supply chain system that can be audited and a chatbot confidently waving at a warehouse. ...

TL;DR for operators When an AI system has to execute a multi-step operational plan, the tempting move is to ask the LLM for the plan. This paper argues for a less glamorous and more useful pattern: let the LLM help shrink the search problem, then let a classical planner verify and compose the actual action sequence.1 ...

TL;DR for operators Many business optimisation problems do not ask for “the best answer.” They ask for a menu of acceptable compromises: cheaper but slower, faster but riskier, smaller but slightly less accurate, feasible but less elegant. This paper matters because it adapts an old Monte Carlo workhorse, Nested Rollout Policy Adaptation, to that messy multi-objective setting. ...

TL;DR for operators SMARTAPS is not another chatbot sprinkled over enterprise software like parsley on a mediocre buffet. It is a tool-augmented interface for advanced planning systems: planners ask natural-language questions, the system detects the planning intent, retrieves the right expert-built API, extracts the necessary parameters, runs the tool, and turns the raw result into a readable answer.1 ...

TL;DR for operators Optimization work usually looks technical from the outside: equations, solvers, constraints, tolerances, and someone quietly muttering about convergence. Inside the business, the real bottleneck is often less glamorous. Someone has to decide what the problem actually is, how to formulate it, which algorithm to try, which hyperparameters to tune, and whether the resulting answer is useful or merely mathematically decorative. ...