industrial//industrial data layer//edge gateway

An edge gateway is the device that sits on the border between OT and IT, collecting data from the machines of a plant and forwarding it to the systems that use it. It speaks industrial protocols on one side (Modbus, PROFINET, EtherNet/IP, OPC UA toward the PLCs) and IT languages on the other (MQTT, OPC UA server, REST toward applications and cloud): a translator and a concentrator. The shared word misleads: a network Gateway is a first hop that forwards packets it does not understand, while an edge gateway has to understand every byte, because it turns a Modbus register into a named, typed, timestamped value on the other side.


An edge gateway is the device that sits on the border between OT and IT, collecting data from the machines of a plant and forwarding it to the systems that use it. It speaks industrial protocols on one side (Modbus, PROFINET, EtherNet/IP, OPC UA toward the PLCs) and IT languages on the other (MQTT, OPC UA server, REST toward applications and cloud): a translator and a concentrator. The shared word misleads: a network Gateway is a first hop that forwards packets it does not understand, while an edge gateway has to understand every byte, because it turns a Modbus register into a named, typed, timestamped value on the other side.

What it can do: read PLCs, translate protocols, normalize tag names and units, run logic, buffer data locally, filter, aggregate, run analytics or models, publish MQTT, act as an OPC UA server. A common chain is a Siemens PLC read over OPC UA, the gateway, MQTT, the cloud.

It is the practical answer to the legacy problem: a 1998 HART transmitter, a 2003 Modbus meter and a 2006 PROFIBUS DCS all end up as nodes in one OPC UA or MQTT namespace because the gateway did the translation (data contextualization).

Buffer plus local analysis plus cleaning: if the Internet drops, the PLC keeps producing, the gateway keeps storing, and when the link returns it forwards the backlog, each value with the time it was measured rather than the time it was sent (event time) (the same store-and-forward reflex as an RTU, which buffers for a control center operating the process, where the gateway buffers for IT and the cloud exploiting its data). It also removes noise, averages, detects outliers, reduces sampling frequency, converts units and enriches tags, so that not every raw sample has to go up. When it runs models on images and PLC signals it becomes edge AI.

Vibration shows why the reduction is a necessity. One accelerometer channel sampled at 25.6 kHz with 16 bits produces 51 kB/s, about 4.4 GB a day, and a hundred channels make 440 GB a day that nobody wants to pay to transmit or store. So the gateway computes edge features (RMS, peak, crest factor, kurtosis, energy per frequency band, an envelope spectrum), sends some tens of numbers per minute to the historian and keeps a raw capture only when something changes (vibration analysis). With a threshold per machine, that already catches a good share of the faults of a fleet of rotating machines.

Edge is hardware plus software: the box is an industrial PC or a dedicated gateway, but the value is in the drivers, the OPC UA and MQTT stacks, containers, analytics, security and remote management. Infrastructure edge computing asks where compute should run for latency; the plant's edge gateway is also a protocol border and a buffer for when the link dies, and the fast loops stay in the PLC below it.