Before operating production with a MES platform, data has to be captured. This step, often underestimated in industrial projects, conditions everything that follows. Without reliable collection, OEE indicators are wrong, downtime is incomplete, production batches get disconnected from the manufacturing reality. An industrial gateway plays this critical role: it queries PLCs and sensors close to the shop floor, absorbs industrial network turbulence and delivers clean data to the platform. Its robustness makes the difference between a useful MES and a theoretical one.
Definition and role of an industrial gateway
An industrial gateway is a hardware or software device, typically installed on an industrial mini PC, deployed close to the production machines, inside an electrical cabinet, a technical room or directly in the production environment. Its role is to connect the PLC layer (PLCs, sensors, SCADA) to the MES platform. In concrete terms, it queries PLCs continuously using available industrial protocols (OPC UA, Modbus TCP), formats raw signals (typing, timestamping, normalisation), keeps a local buffer in case of network outage, then synchronizes data to the platform over an authenticated channel. It absorbs equipment heterogeneity and delivers homogeneous data, ready to be structured by the platform.
Why not connect machines directly to the cloud
A legitimate question: why not connect machines directly to the cloud, with no intermediary? Several operational reasons make this impractical. First, an industrial network is not designed for permanent outbound connections to the internet. Outages, restarts and segmentation are frequent. Without a local buffer, each incident loses data. Second, IT security usually requires flows to be outbound from the site, authenticated and limited to a single endpoint. A gateway centralises this responsibility and simplifies firewall rules. Third, PLCs are not sized to query a remote cloud continuously. They expose their data locally. The gateway acts as a buffer between the real-time field and the platform.
OPC UA and Modbus TCP
OPC UA (Open Platform Communications Unified Architecture) is a modern industrial protocol, structured and object-oriented. It exposes values (states, measurements) together with their semantics (type, unit, security). It fits modern equipment: Siemens, Beckhoff, Schneider PLCs, robots, CNC controllers. It supports native encryption and authentication. Modbus TCP is an older protocol, simple and widely deployed across the existing industrial base. It works by register reads (binary states, analog values) following addressing maps specific to each device. Its main strength is ubiquity: sensors, drives, old and new PLCs. Covering both protocols lets plant teams connect a large fleet quickly without imposing heavy machine-side upgrades.
Local buffer and secure data synchronization
The local buffer is the mechanism that makes collection resilient. The gateway stores captured data locally in an embedded database (typically SQLite). During a network outage, a platform restart, a maintenance window or an unstable link, collection continues normally. No data is lost on the shop floor side. Once connectivity is restored, secure synchronization takes over. The gateway pushes buffered data to the platform via an authenticated, encrypted channel. Flows are outbound from the industrial site, which simplifies integration with IT security and existing firewalls. This dual mechanism ensures the MES platform always ends up with a complete, consistent history.
Portable architecture: SaaS, dedicated instance, on-prem
The same gateway can feed several targets depending on the IT context and the maturity of the site. It can push data to a shared SaaS instance (fast deployment, externally supervised), to a dedicated instance (data isolation, guaranteed performance), or in the future to an on-prem instance fully hosted on site (full sovereignty, regulatory constraints). The target can evolve over time without changing the field collection layer. The gateway stays the same, the captured data stays the same, only the synchronization endpoint changes. This portability protects the initial investment.
Common mistakes
- Trying to connect machines directly to the cloud with no local buffer in between.
- Underestimating the operational cost of a network outage with no buffering.
- Picking a single protocol while the fleet is heterogeneous (OPC UA and Modbus TCP often coexist).
- Not authenticating nor encrypting the synchronization channel.
- Locking the architecture on a single target (SaaS only or on-prem only) with no upgrade path.
Key takeaways
- The gateway captures data close to the machines and absorbs equipment heterogeneity.
- OPC UA and Modbus TCP together cover a very large industrial fleet.
- Local buffering keeps data collection resilient during network outages.
- A portable architecture leaves the choice between SaaS, dedicated and on-prem.