Edge gateway patterns for brownfield connectivity

Brownfield plants do not get rewired; they get gatewayed. An edge gateway sits between legacy equipment and modern platforms, translating protocols, buffering through outages, and adding the context (asset IDs, units, quality) that raw device data lacks. Four patterns cover most deployments.

The four patterns

1. Protocol converter — speaks the device's language southbound (Modbus, EtherNet/IP, PROFINET, serial, vendor APIs) and OPC UA or MQTT northbound. Stateless, robust, and the right default when all you need is data movement.
2. Store-and-forward buffer — persists data locally through WAN and broker outages, then replays in order. Non-negotiable for cloud historians and remote sites; size the disk for your longest plausible outage, not your average one.
3. Contextualizer — attaches asset models, engineering units, and ISA-95 hierarchy to raw tags before publishing. This is where a tag becomes information. Sparkplug birth certificates carry this metadata natively; otherwise use a DataOps layer.
4. Local actor — runs logic at the edge: alarming, OEE rollups, vision inference, closed-loop control assists. Keeps latency low and keeps working when the uplink dies. Version and monitor edge applications like production software, because they are.

Tooling landscape

Connectivity servers such as Kepware — now part of Velotic — remain the workhorse for multi-protocol device access with OPC UA and MQTT/Sparkplug northbound options. DataOps platforms such as HighByte handle modeling, piping, and governance from edge to cloud. And integration software such as OPC Router covers the awkward middle that pure gateways miss: joining PLC and SCADA data with SQL databases and SAP, with visual project tooling for the mappings that would otherwise become scripts nobody owns.

Whatever the stack, enforce three rules: the gateway never becomes a single point of failure for control (monitor it, fail safe, keep control local), all northbound traffic authenticates (certificates, not anonymous MQTT), and every mapping is versioned and documented — the gateway fleet is infrastructure, not improvisation.

References

• MQTT: the standard for IoT messaging
• Eclipse Sparkplug — specification and resources
• OptoBlog — edge and IIoT architecture