Cloud is now the default pitch for new MES deployments. The survey data tells a messier story. In Rockwell Automation’s July 2026 survey of 1,560 manufacturers, 93% already run an MES but only 23% have it fully integrated with ERP, PLM, quality and OT systems. 44% rank integration as their top MES buying requirement, and 43% put security and compliance second. That makes sense once you account for one thing: the shop floor is not the back office.
Where cloud genuinely works
For planning, management reporting, KPI dashboards, and anything the office touches, cloud makes sense: automatic updates, access from anywhere, no server to maintain. That's exactly why major MES vendors (Siemens, Rockwell, SAP) default to cloud, because that's the layer most of their buyers actually care about.
A steel shop floor is a different problem
On the weld line or the cutting station, the network drops, tablets pass between workers wearing gloves, and the moment that needs recording, which welder, which part, which heat number, can't wait for the connection to come back. If the MES is cloud-only, either the worker waits, or the data never gets captured at all, and that missing data is exactly what you need during an inspection or a warranty claim. The same logic applies when the outage is the grid itself; we wrote up how to plan a fabrication week around scheduled power cuts.
Offline-first means designing backwards
The fix is inverting the priority: the app runs fully on the local device, functions completely without a network, and syncs automatically once the connection returns. That's the actual design behind SteelFlow MES, shop-floor tracking, QC logging, part status, all working without depending on the internet moment to moment. The management layer (dashboards, reporting, planning) can still live in the cloud, because offline capability doesn't matter there.
The point isn't that cloud is wrong. It's that treating "cloud-first" as a uniform default across every layer of an MES is exactly what produces the integration and security complaints that keep showing up in these surveys. Design offline where offline is actually required. Don't force the cloud to pretend it's offline.
For the basics of what an MES covers on a steel shop floor, see What Is MES? A Plain-Language Guide for Steel Fabricators.
Inspection apps face the same test, and we broke down the difference between true offline and fake offline in more detail.
Frequently asked questions
How well integrated are MES deployments in 2026?
Not very. In Rockwell Automation's July 2026 survey of 1,560 manufacturers, 93% already run an MES, but only 23% have it fully integrated with ERP, PLM, quality and OT systems. Integration is the top MES buying requirement for 44% of respondents, and 43% rank security and compliance second.
Why is a cloud-only MES risky on a steel shop floor?
On the weld line or cutting station the network drops, and the moment that needs recording, such as which welder, which part and which heat number, cannot wait for the connection to return. With a cloud-only MES the worker waits or the data is never captured, and that missing data is exactly what an inspection or warranty claim needs.
Which MES layers belong in the cloud and which should work offline?
Planning, management reporting and KPI dashboards suit the cloud: automatic updates, access from anywhere and no server to maintain. Shop-floor tracking, QC logging and part status should run fully on the local device, work without a network and sync automatically when the connection returns.
