The short version: the real difference in this round of smart manufacturing is not more robots. It is that AI has entered the decision layer — scheduling, dispatching, inspection standards, the steps that planners and veteran operators used to decide — now generated by systems and confirmed by people. The headlines are about large plants: planning time cut from 6 hours to 90 seconds, 91% automation, supply-chain decision cycles halved. But a mid-size factory only needs to answer one question: which step do I enter at, and where does the first budget go?
The industry context first. Policy and industry conferences have repeatedly set "new-generation smart manufacturing" as the main direction this year. Flagship plants provide the samples: a base taking thousands of orders daily, 80% of them small custom batches, runs an AI scheduling system whose plan goes straight to the line — planning time from 6 hours to 90 seconds. AI visual inspection in real mid-size plants now exceeds 99% defect recall. A cross-region supply-chain agent across dozens of plants and thousands of suppliers cut decision cycles by 50–60%. The common pattern: perception–decision–execution–feedback runs as a loop, AI generates the decision, people confirm and carry responsibility.
1 · Three practical entry points for a mid-size factory
Flagship plants pour mega-castings and staff unmanned shops; a mid-size plant should not copy that. From our line and IoT projects, three entries have the clearest return:
| Entry point | What it fixes | Prerequisite | Time to effect |
|---|---|---|---|
| AI visual inspection | Human-eye misses, standards that vary by shift | Defect sample set + a written grading standard | 3–6 months, recall verifiable |
| Scheduling and dispatch support | Insertion orders, plans that never keep up | Process and capacity data on record first | 6–12 months, assist first then automate |
| Machine connectivity and maintenance | Surprise stoppages, experience-based repairs | Modbus / OPC UA capture + threshold baselines | 3–6 months, fewer unplanned stops |
The shared trait: all three can ship an "assist the human" version first. Inspection flags, a person rules; scheduling proposes, a planner confirms; maintenance reports anomalies, the veteran decides. Once that works, data and trust accumulate — then talk about automation. This fails far less often than starting "unmanned".
2 · Three gates for decision-layer AI
- No records, no decisions. AI scheduling assumes process, capacity and material data live in a system, not in spreadsheets and veterans' heads. Many projects stall at step one: before scheduling, do data governance — that budget cannot be skipped.
- No agreed metrics, no acceptance. What does "on-time delivery" mean — promised date or internal plan date? Without agreed definitions, nobody can say whether the AI's plans are good, and acceptance becomes an argument. Write metric definitions into the contract before go-live; we keep saying this because it keeps being true.
- Design the responsibility chain, do not rely on trust. Who confirms AI-drafted plans, who answers for errors, is confirmation logged — these decide whether the system survives its second year. Keeping a human confirmation point is not conservatism; it closes the chain: when something breaks you can locate whether the data, the plan or the confirmation was wrong.
The test for loosening automation is the same one we use for enterprise AI: tasks that are verifiable, reversible and have confirmation points can open up gradually; the rest should stay in "assist the human" mode first.
3 · A four-step plan
- Connect before you make intelligent. Pick one bottleneck operation and get its data flowing (protocol choice covered in our Modbus vs OPC UA comparison →); produce the first number everyone can see.
- Choose one scenario that pays for itself. Inspection, scheduling or maintenance — pick one, budget against the table above, and keep the word "platform" out of phase one.
- Write the evaluation baseline and metric definitions into the contract before go-live: which data tests it, whose standard decides, what the passing line is.
- Review quarterly; cut and expand bravely. Shrink scenarios whose numbers stagnate; replicate the ones that work to adjacent operations. Ten mediocre pilots lose to one truly closed loop.
Across the line and warehouse projects we deliver, the ones still running years later share one profile: complete records, metric definitions in the contract, humans holding confirmation points. The industry headlines are lighthouses — they show direction. A mid-size factory walks its own path, and the first step is usually the cheap one: get the data flowing.