{"id":1173970,"date":"2026-06-03T09:00:00","date_gmt":"2026-06-03T16:00:00","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/research\/?post_type=msr-story&p=1173970"},"modified":"2026-06-03T06:10:12","modified_gmt":"2026-06-03T13:10:12","slug":"optimind-when-the-system-meets-the-floor","status":"publish","type":"msr-story","link":"https:\/\/www.microsoft.com\/en-us\/research\/story\/optimind-when-the-system-meets-the-floor\/","title":{"rendered":"OptiMind: When the system meets the floor"},"content":{"rendered":"\n
<\/div><\/span>
\n
\n
<\/div>\n\n\n\n

OptiMind: When the system meets the floor<\/h1>\n\n\n\n
<\/div>\n<\/div>\n<\/div><\/div>\n\n\n\n
\n
\n\t\n\t
\n\t\t
\n\t\t\t
<\/div>\t\t<\/div>\n\t<\/div>\n\n\t<\/div>\n\n\n\n
\n
<\/div>\n\n\n\n
\n
<\/div>\n\n\n\n

How a small, domain-specific model moved from research into real operations\u2014and why that matters<\/h2>\n\n\n\n

For years, the production schedule at many factories has lived in an uneasy truce between critical planning and improvisation. An enterprise system spits out a plan, someone exports it to a spreadsheet, and then the inevitable hiccups occur: machines go down, raw materials arrive late, rush orders appear, a line runs slower than expected, and the whole thing starts to wobble.<\/p>\n\n\n\n

The official job title may be scheduler, but on the plant floor, people tend to joke the job is actually \u201crescheduler.\u201d<\/p>\n\n\n\n

That is the chaotic, costly reality behind an interesting challenge in artificial intelligence. Despite all the thunder around general\u2011purpose models, what matters is whether AI can begin operating inside systems where constraints fluctuate and tradeoffs carry real consequences.<\/p>\n\n\n\n

\n\t
\n\t\t
\n\t\t\t\t\t\tMODEL<\/span>\n\t\t\tOptiMind<\/span> <\/span><\/a>\t\t\t\t\t<\/div>\n\t<\/article>\n<\/div>\n\n\n\n

OptiMind<\/a>, a specialized language model from Microsoft researchers, is built to tackle that reality. Released as an experimental model in Foundry (opens in new tab)<\/span><\/a>, it is designed to translate natural-language business problems into solver-ready mathematical formulations. It is, in other words, not built to just sound smart, but to offer domain expertise.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"Laptop
Sight Machine\u2019s scheduling interface visualizes production constraints and machine availability in real time, helping plant operators evaluate how manufacturing decisions ripple across the factory floor.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Three months ago, it was tested in the real world at a Midwestern beverage bottling plant, where shifts in the schedule measured in minutes could translate into significant financial loss.<\/p>\n\n\n\n

\n\n\n\n

How the use case took shape<\/h2>\n\n\n\n

The opportunity to apply OptiMind in a real-world setting first caught the attention of Saumil Shrivastava (opens in new tab)<\/span><\/a>, a principal product manager at Microsoft who leads Foundry Labs. Shrivastava\u2019s job is to look at Microsoft Research projects and ask a question that is sometimes more complicated than the research query: Where, exactly, could this become real?<\/p>\n\n\n\n

\n

“What stood out about OptiMind was that it wasn\u2019t just another generative AI model. It was solving a fundamentally different class of problem around optimization and decision-making under real-world operational constraints.”<\/p>\n\u2013 Saumil Shrivastava (opens in new tab)<\/span><\/a>, Principal Product Manager, Microsoft<\/em> Foundry<\/cite><\/blockquote>\n\n\n\n

Once he saw what it could do, he said, he began thinking \u201cless about it as a standalone research demo, and more about where this could fit inside real operational workflows.\u201d<\/p>\n\n\n\n

The move from demo to workflow is where many promising AI projects stall. Models can look impressive in clean environments and still fall apart in the real world. The people using these systems are rarely researchers. In this case, they are schedulers, plant managers, and engineers who need reliable, practical solutions.<\/p>\n\n\n\n

Shrivastava had seen enough manufacturing environments through prior work with Sight Machine, a company focused on applying AI to industrial operations, to recognize a plausible proving ground. Bottling plants in particular run on a dense tangle of \u201cwhat-ifs,\u201d where even small improvements reverberate through the system in visible ways.<\/p>\n\n\n\n

\n\n\n\n

An idea finds a customer<\/h2>\n\n\n\n

The use case took shape through Kurt DeMaagd (opens in new tab)<\/span><\/a>, chief AI officer and co-founder of Sight Machine. He had a long-running relationship with a major food and beverage company.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"
Kurt DeMaagd, co-founder and chief AI officer at Sight Machine, helped bring Microsoft Research\u2019s OptiMind system into a live beverage manufacturing environment.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

The idea came up on a call, almost in passing, before anything like a pilot had been proposed. A senior leader at the plant didn\u2019t need much convincing. He said he had spent the previous week complaining about how poorly their current scheduling system was working.<\/p>\n\n\n\n

In a fixed-cost business, even flecks of change can ripple outward. \u201cWe\u2019re talking tens of millions of dollars of value for them,\u201d DeMaagd said.<\/p>\n\n\n\n

The problem was already in plain view. And clearly, so was the appetite to try something new.<\/p>\n\n\n\n

\n\n\n\n

Why general AI wasn\u2019t enough<\/h2>\n\n\n\n
<\/div>\n\n\n\n

Scheduling had long been on DeMaagd\u2019s mind. It is one of those persistent industrial problems that many teams avoid precisely because it is so difficult to generalize. Historically, solving it required deep expertise in specialized optimization techniques. That made solutions expensive to build and hard to scale.<\/p>\n\n\n\n

The pilot was structured as a set of recurring scenarios. The team started with a core formulation of how the plant operated, then used it to explore a handful of situations that came up repeatedly: demand shifting, a machine going down, small changes that cascade through the schedule. Each variation traced back to the same underlying model, rather than requiring a new system each time.<\/p>\n\n\n\n

DeMaagd approached the model with skepticism. Many AI systems perform well on familiar prompts but degrade quickly outside them.<\/p>\n\n\n\n

\u201cI was really impressed,\u201d he said. \u201cI was half expecting maybe it would handle a few standard questions, but beyond that it would fall apart.\u201d<\/p>\n\n\n\n

Instead, he saw something different. When he compared outputs to general-purpose models, the contrast was clear.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"Person
An architectural diagram of the OptiMind pilot shows how factory data from Sight Machine flowed into Microsoft\u2019s optimization system to generate updated production schedules.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

\u201cBecause OptiMind is specifically tuned as an optimization tool, I got faster and more reliable responses where it was actually doing the mathematical optimization,\u201d he said. \u201cAbout half the time with general-purpose models, it would go off and I didn\u2019t know what heuristics it was applying.\u201d <\/p>\n\n\n\n

The OptiMind answers came back quickly, usually within 30 to 90 seconds, fast enough to feel usable in the flow of a real scheduling decision.<\/p>\n\n\n\n

\n\n\n\n

From answers to interactions<\/h2>\n\n\n\n

In theory, scheduling is a problem you solve once. In reality, it is something you revisit constantly. Conditions change and decisions have to keep up, functioning as an ongoing conversation.<\/p>\n\n\n\n

That turned out to be one of the most important lessons during this pilot, according to Sirui Li<\/a>, a senior researcher in Microsoft Research\u2019s Machine Learning and Optimization group<\/a>. She said the team quickly realized that \u201coptimization at scale can\u2019t be achieved as a one-shot experience.\u201d<\/p>\n\n\n\n

Instead of rebuilding schedules from scratch, users were asking iterative questions: What changes if demand shifts? What happens if a machine is unavailable?<\/p>\n\n\n\n

To support that, the team built what Li describes as an agentic workflow around OptiMind\u2014one that maintained a core formulation while allowing the system to answer successive questions.<\/p>\n\n\n\n

\u201cWith an agentic workflow around it, we were able to scale OptiMind and optimize a formulation that is flexible enough to accommodate what-if questions,\u201d she said. <\/p>\n\n\n\n

The research itself was led by Ishai Menache<\/a>, a partner research manager at Microsoft Research, whose group focuses on optimization and large-scale decision systems.<\/p>\n\n\n\n

The result is a different way of thinking about AI. It becomes part of an ongoing decision process, adjusting as conditions change.<\/p>\n\n\n\n

\n\n\n\n

The invisible work that made it real<\/h2>\n\n\n\n

\u201cThe biggest challenge we had was doing the plumbing and piping,\u201d said Anson Ho<\/a>, a senior program manager.<\/p>\n\n\n\n

That meant connecting systems, aligning data, and ensuring that everything worked outside controlled environments. This is the part of AI that rarely makes headlines but determines whether anything actually ships.<\/p>\n\n\n\n

Those results mattered because they existed inside a real system, with all its imperfections.<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"Bar
A before-and-after comparison of non-productive time at the bottling plant shows the impact of the OptiMind pilot. Average downtime dropped from 29.7 hours to just a fraction of that level after optimization\u2014an 80 percent reduction in wasted production time.<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

The bottling plant is not an obvious symbol of the AI future, which is why it works as a proving ground. Not glamorous, but complex and expensive to run.<\/p>\n\n\n\n

\n\n\n\n

From general intelligence to useful systems<\/h2>\n\n\n\n

The pilot itself was a success, but Shrivastava sees the project as a broader shift.<\/p>\n\n\n\n

\u201cThe goal was not simply to showcase impressive AI,\u201d he said, \u201cbut to demonstrate how advanced Microsoft Research innovation could evolve toward repeatable enterprise value.\u201d<\/p>\n\n\n\n

That may be the least flashy idea in the story, but the one that carries the most weight.<\/p>\n\n\n\n

Generating the formulation was never the hardest part. The real test came later, once it entered the systems it was meant to serve, where the answer must hold even when the data is partial and the constraints don\u2019t sit still.<\/p>\n\n\n\n

In factories, schedules are never finished. They are revised, negotiated, and revised again.<\/p>\n\n\n\n

AI may be headed in the same direction. Systems are being designed to stay with a problem, working through it as conditions change, rather than attempting to account for everything at once.<\/p>\n<\/div>\n\n\n\n

<\/div>\n<\/div>\n\n\n\n
\n
\n\t\n\t
\n\t\t
\n\t\t\t
\n
\n
\n
\n