Why AI Can't Optimize a Factory It Doesn't Understand

A machine stops in the middle of production. ERP knows the customer orders and due dates, MES knows which operation stopped, maintenance knows the repair status, and the machine layer knows the fault code and exact timestamp. Then someone asks the obvious question: what should we do now?

AI can summarize the alarm, find patterns in historical downtime, and explain what probably happened. But unless it also understands which product was running, which orders depend on that operation, which machines are approved alternatives, which tools are available, which operators are qualified, and which quality or process rules apply, it cannot safely optimize the response.

That is not primarily an AI problem. It is a factory-context problem.

DATA IS NOT THE SAME AS CONTEXT

Factories already produce huge amounts of data. ERP, MES, maintenance, quality, historians, PLCs, IoT platforms, and spreadsheets all hold useful facts.

The problem is that those facts often remain disconnected.A machine stop code by itself does not tell you whether the event happened during production, changeover, maintenance, or a batch with a strict processing window. A machine can appear idle while still being unusable because the required fixture is unavailable or the qualified operator is not on shift.

Context connects the event to the operating situation around it.

That includes:

• Asset and resource identity

• Active operation and work order

• Product and revision

• Route and alternate routes