Protocol Stacking Done Right: A Field Guide for the Plant Floor

Here's a misconception that keeps costing us downtime: the belief that your industrial protocol choice is a single pick—you're either a Modbus shop or a PROFINET shop, and you stick with it until the next forklift drives through the control cabinet. That's wrong. The protocols we reach for on the plant floor aren't competitors; they're layers of a stack, each doing a job the others can't. If you're still thinking one-protocol-to-rule-them-all, you're leaving reliability and security on the table. Let's walk through a real scenario to show how layering actually works.

Picture This: The Retrofit That Made Us Rethink Everything

Imagine you're a controls engineer at a mid-sized food and beverage plant in the Midwest. The line has been running on Modbus RTU over serial for years—rock solid, but a pain to scale. Management wants real-time visibility to the cloud, and they want it yesterday. You've got legacy field devices, a mix of PLCs, and a mandate to keep production running. The instinct is to rip out the old and go all-in on one new protocol. Resist that. The smart move is to layer: keep Modbus for the field, add EtherNet/IP or PROFINET for the control network, and bridge it all to the cloud with OPC UA and MQTT. This isn't a pipe dream; it's how the industry is actually evolving. The OPC Foundation notes that Modbus, PROFINET, and EtherNet/IP connect field devices and PLCs, while OPC UA and MQTT carry data securely to SCADA, MES, and cloud systems (OPC Foundation). That's the layering principle in one sentence.

Step One: Don't Fix What Isn't Broken—Keep Modbus in the Field

Your field devices—sensors, actuators, maybe an old flow meter—are already talking Modbus. Developed in the late 1970s, Modbus uses a master-slave register-based model and supports both serial (RTU) and Ethernet (TCP) transport (OPC Foundation). It's simple, proven, and your techs can troubleshoot it with a screwdriver and a multimeter. Replacing every field device to get a “modern” protocol would cost a fortune and add zero value. The hardware segment—sensors, PLCs, HMI panels—accounts for 50% to 60% of the industrial automation market (Maximize Market Research), so you're not alone in having a lot of iron to manage. Keep Modbus where it belongs: at the edge, talking to individual devices. Just make sure to use Modbus TCP if you can—it runs over the same Ethernet you'll use for the rest of the stack, saving you serial-to-Ethernet converters down the road.

Step Two: The Control Layer Isn't a Religion—Pick What Your PLCs Speak

Now, between the field and your controllers, you need a real-time protocol that your PLCs natively support. This is where the “which protocol is best” debate gets silly. If you're on Rockwell/Allen-Bradley, you're likely using EtherNet/IP, which runs the Common Industrial Protocol (CIP) over standard Ethernet and TCP/UDP (OPC Foundation). If you're in a Siemens-heavy plant, PROFINET is your go-to—an Ethernet-based, real-time protocol supporting real-time (RT) and isochronous real-time (IRT) for motion control (OPC Foundation). Neither is “better” in the abstract; they're both designed to move control data with deterministic timing. The choice is dictated by your installed base, not by a benchmark. In our scenario, the plant has a mix of old and new PLCs, so we standardize on EtherNet/IP for the new controllers and use a gateway to translate Modbus TCP to EtherNet/IP for the legacy ones. This gives us a unified control backbone without ripping out the old gear.

Step Three: The Cloud Connection—OPC UA and MQTT Are the Bridge

Here's where the layering pays off. Control protocols like EtherNet/IP and PROFINET are not designed to push data to the cloud. They're real-time, connection-oriented, and often too chatty for wide-area networks. That's where OPC UA and MQTT come in. OPC UA is vendor-neutral, platform-independent, with built-in encryption and authentication, and it's the backbone for IIoT and IT/OT integration (OPC Foundation). MQTT, standardized as ISO/IEC 20922, is a lightweight publish/subscribe messaging transport designed for constrained M2M and IoT environments (ISO/IEC 20922 MQTT Standard). In our plant, we install an OPC UA server on the control network that reads from the EtherNet/IP PLCs and publishes to an MQTT broker, which then streams to the cloud. The beauty of MQTT is its publish/subscribe pattern—it provides one-to-many distribution and decouples the data producers from consumers (ISO/IEC 20922 MQTT Standard). That means you can have multiple dashboards, historians, or analytics tools subscribing to the same data without messing with the control network.

Step Four: Security Isn't a Protocol Feature—It's a Discipline

Now, the security folks get nervous when you mention cloud connectivity. And they should. But the answer isn't to avoid layering; it's to follow standards that are designed for this. The ISA/IEC 62443 series defines requirements and processes for implementing and maintaining electronically secure industrial automation and control systems (IACS), bridging the gap between OT and IT (ISA/IEC 62443). It's not just a checklist; it's a framework that covers asset owners, integrators, and suppliers. NIST SP 800-82 Rev. 3 provides guidance on securing OT, including industrial control systems, SCADA, DCS, and PLC systems (NIST SP 800-82 Rev. 3). In our retrofit, we segment the network: the control network is isolated behind a firewall, and the OPC UA/MQTT traffic passes through a demilitarized zone with TLS encryption and strong authentication. MQTT supports TLS and OAuth, and clients are small enough to run on microcontrollers, so we can secure even the edge devices (MQTT.org). CISA's Secure by Demand guidance warns that threat actors exploit weak authentication and outdated protocols, so we make sure every layer uses current, secured versions (CISA Industrial Control Systems).

Step Five: Scale It—Because the Market Is Moving Fast

Once the stack is in place, the plant starts seeing the benefits. The IIoT market is growing at a double-digit clip—the global Industrial IoT automation market was about $134.64 billion in 2025 and is expected to reach $301.38 billion by 2032 (Maximize Market Research). Your retrofit is part of that wave. The digital twin market is exploding too, projected to grow from $21.14 billion in 2025 to $149.81 billion by 2030 at a CAGR of 47.9% (MarketsandMarkets Digital Twin Report). With OPC UA feeding real-time data into a digital twin, you can simulate changes before touching the line. And you're not alone in this: the global industrial automation market is valued at about $184.43 billion in 2025, projected to reach $326.48 billion by 2032 (Maximize Market Research). The vendors you're dealing with—Siemens, Rockwell, Schneider—are all pushing this layered approach because it works.

Takeaway

Stop thinking of protocols as a single choice. In the real world, you layer them: Modbus in the field for legacy, EtherNet/IP or PROFINET for real-time control, OPC UA and MQTT for IT/OT integration and the cloud. Each layer does what it's best at, and together they give you reliability, scalability, and security—if you apply the standards like ISA/IEC 62443 and NIST SP 800-82. The next time someone asks you “Modbus or OPC UA?”, tell them: it's not either/or. It's both, in the right layers.

Sources

• OPC Foundation - https://opcfoundation.org/
• ISO/IEC 20922 MQTT Standard - https://www.iso.org/standard/69466.html
• MQTT.org - https://mqtt.org/
• ISA/IEC 62443 - https://www.isa.org/standards-and-publications/isa-standards/isa-iec-62443-series-of-standards
• NIST SP 800-82 Rev. 3 - https://csrc.nist.gov/pubs/sp/800/82/r3/final
• CISA Industrial Control Systems - https://www.cisa.gov/topics/industrial-control-systems