industrial//industrial data layer//edge gateway

The device that sits on the border between OT and 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 device that sits on the border between OT and 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.

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. 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.

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 (edge computing).