From Devices to MES: One Single Data Link Makes All the Difference

In the wave of digital transformation in manufacturing, MES (Manufacturing Execution System) has become the core engine driving factories toward intelligence. However, a common and frustrating reality persists: the MES system is deployed, but data cannot feed into it.

Equipment runtime data, production output, yield rates, and progress updates—these essential "raw materials" that MES relies on—remain trapped on the shop floor, unable to be effectively collected and utilized. PLCs, instruments, and servo drives on the production line operate in isolation, speaking different protocols such as Modbus RTU, RS485, and Ethernet. Analog signals (temperature, pressure, humidity) mix with discrete and pulse signals, making it even more complex. Even if data is gathered from the equipment, there is no standardized pathway to deliver it to MES. The link between devices and MES has become the "last mile" bottleneck in factory digitalization.

How do we bridge this gap? The answer lies in a critical enabler: the industrial data acquisition gateway.

1. The Three‑Layer Architecture of Data Acquisition

A complete data acquisition link from field devices to MES typically consists of three layers:

Perception and Acquisition Layer (OT side) – This layer interfaces with all types of on‑site equipment, reading data from PLCs, instruments, and servo drives via protocols such as Modbus RTU, RS485, and Ethernet. The challenge here is to "get the data out"—regardless of whether the device interface is analog, discrete, or digital, the gateway must be able to connect.

Edge Computing Layer – Raw data collected at the previous layer is pre‑processed here: filtering out invalid data, aggregating statistical metrics, and executing local logic decisions. The key value of edge computing is that not all data needs to be uploaded in full. Real‑time processing at the edge allows only valuable results to be forwarded, which reduces network load and also leaves room for reverse control.

Platform Application Layer (IT side) – After edge processing, the data is delivered directly to the MES system via standard industrial communication protocols, enabling real‑time upload of key metrics such as output, yield, equipment status, and production progress. At this point, device connectivity and data visualization are truly realized.

2. Protocol Conversion: The Key to Overcoming "Language Barriers"

Factories are filled with equipment from various vendors—Siemens, Mitsubishi, Fanuc, and others—each with its own proprietary communication protocol. These protocols are mutually incompatible, making it difficult for data acquisition systems to achieve unified access. Protocol fragmentation is the primary challenge in industrial data collection.

One of the core functions of the gateway is protocol conversion: translating proprietary protocols from different devices into a unified standard format. Whether it is converting Modbus RTU to Modbus TCP, or translating PLC data into standard IoT interfaces like MQTT and HTTP—the gateway acts as the interpreter that enables devices speaking different "languages" to understand one another.

3. From Wiring to MES: A Four‑Step Implementation Process

To establish the link from devices to MES, follow these four steps:

Step 1: Inventory of field devices and interfaces. List all PLCs, instruments, servo drives, and other equipment to be connected. Confirm the communication interface type (Modbus RTU, RS485, Ethernet, etc.) and protocol for each device, and differentiate between analog signals and discrete signals.

Step 2: Wiring and parameter configuration. Complete the physical wiring according to the device interfaces, and standardize communication parameters. For example, when using Modbus RTU acquisition, you need to set baud rate, data bits, stop bits, and parity consistently, and assign a unique address to each device to avoid conflicts.

Step 3: Commissioning and data validation. Poll the devices in sequence, enable CRC checking to ensure data integrity, and verify the read values against the device register maps. Proceed to the next step only after confirming the data is accurate.

Step 4: Integration with MES and platforms. Connect the gateway data directly to the MES system through standard industrial communication protocols. Map fields such as output, yield, equipment status, etc., to the corresponding MES data points. Finally, complete device networking and data visualization.

4. The Value of Edge Computing: Beyond Just "Transferring Data"

Traditional data collection simply forwards raw device data as‑is, but edge computing empowers the gateway with stronger data processing capabilities. At the edge, data can be cleaned, filtered, and aggregated, forwarding only meaningful results to MES or the cloud. This not only reduces unnecessary traffic but also lessens the processing load on the cloud and MES systems.

More importantly, edge computing enables reverse control—real‑time processed data at the edge can directly issue control commands to devices, achieving millisecond‑level response times. This capability is critical for industrial scenarios requiring fast reactions.

Conclusion

The gap between devices and MES is never just about hardware—it is the lack of a complete, reliable, and standardized data link. The industrial data acquisition gateway, as the core hub of this link, carries the multiple responsibilities of acquisition, conversion, computation, and upload. Once this link is established, the MES system can truly function, and the factory’s digital transformation takes a substantial step forward.