Stop Chasing Protocols: Pick the Right Tool for the Job

Imagine you're a controls engineer at a mid-sized plant. The boss just told you to 'modernize' the network because the IIoT market is exploding—$134.64 billion in 2025, heading to $301.38 billion by 2032 (Maximize Market Research). You've got legacy Modbus RTU devices on the floor, a new PROFINET line being installed, and IT is pushing MQTT for cloud analytics. The vendor reps are all claiming their protocol is the future. What do you do?

Here's my thesis: the protocol wars are a distraction. The real decision isn't about which protocol is 'best'—it's about fitting the right protocol to the right layer of your network, and being honest about your legacy constraints. Stop chasing the shiny new thing; start thinking in layers.

Don't Fall for the Hype Cycle

Every few years, a new protocol gets crowned as the savior of industrial networking. Right now, it's OPC UA and MQTT, fueled by the IIoT narrative. But the market data tells a different story: hardware still dominates the industrial automation market, holding 50% to 60% of the share (Maximize Market Research). That means the physical layer—PLCs, sensors, robots—is where the money and the real decisions live. And those devices don't speak OPC UA natively; they speak fieldbus protocols like Modbus, PROFINET, and EtherNet/IP.

The hype around OPC UA is real, but it's not a replacement for field-level protocols. It's an integration layer. As the OPC Foundation notes, OPC UA is a vendor-neutral, platform-independent standard with built-in security—perfect for IT/OT integration. But it doesn't talk to a sensor directly; it talks to the PLC that talks to the sensor. So, if you're ripping out your PROFINET infrastructure to 'go OPC UA', you're making a mistake.

The Layering Principle: Know Your Place

The key insight is layering. The OPC Foundation describes it clearly: Modbus, PROFINET, and EtherNet/IP connect field devices and PLCs, while OPC UA and MQTT carry data securely to SCADA, MES, and cloud systems. These are not competitors; they're complementary.

Think of it like the OSI model—each layer has a job. At the device level, you need deterministic, real-time communication. PROFINET supports real-time (RT) and isochronous real-time (IRT) classes for motion control—you can't do that with MQTT. EtherNet/IP runs the Common Industrial Protocol (CIP) over standard Ethernet and TCP/UDP, and it's deeply embedded in North American Rockwell/Allen-Bradley shops. Modbus, despite being from the late 1970s, is still everywhere because it's simple and works over serial and Ethernet.

When MQTT and OPC UA Make Sense

Now, for the IT side—the level where you're aggregating data from multiple lines or sending it to the cloud—MQTT and OPC UA shine. MQTT is standardized (ISO/IEC 20922:2016) as a lightweight publish/subscribe messaging transport, designed for constrained M2M/IoT environments. It's payload-agnostic, supports three QoS levels (0, 1, 2), and can run on small microcontrollers and scale to millions of devices (MQTT.org). That's a huge advantage when you're dealing with hundreds of sensors.

OPC UA, on the other hand, is the backbone for IIoT and IT/OT integration because it's vendor-neutral and has built-in encryption and authentication (OPC Foundation). If you're building a digital twin—the market is projected to hit $149.81 billion by 2030 (MarketsandMarkets)—you'll need OPC UA to feed that twin with structured, secure data.

So, the decision isn't either/or. It's about where you are in the architecture. Use PROFINET or EtherNet/IP on the floor, and use MQTT or OPC UA to get that data up to the cloud.

But What About the Legacy?

Here's where the counter-argument comes in: 'Sure, layering is nice, but we've got Modbus RTU devices from 1985 that we can't replace. How do we modernize?' That's a fair point. You can't just rip out working hardware—the hardware segment is still the biggest chunk of the market for a reason.

My answer: don't replace, bridge. Use protocol converters or gateways to connect legacy Modbus to your new OPC UA backbone. That's a standard practice. The OPC Foundation's own materials show that Modbus supports both serial (RTU) and Ethernet (TCP) transport, so it's not going away. The key is to create a clean architecture where the legacy devices talk to a gateway, and the gateway talks to the modern systems. You get the best of both worlds: your old gear keeps running, and you get the data you need for IIoT.

Yes, it's a bit messy, but it's practical. And practical is what we do in industrial networking.

What I'd Actually Do

If I were in your shoes, here's my concrete plan:

• Audit your current protocol inventory. List every device and its protocol. You'll probably find a mix of Modbus, PROFINET, and EtherNet/IP.
• Keep field-level protocols as-is. Don't replace a working PROFINET line just to standardize. That's a waste of money and risk.
• Deploy OPC UA as your integration layer. It's the industry standard for secure, vendor-neutral data exchange, and it's ready for your future digital twin projects.
• Use MQTT for cloud and mobile applications. Its lightweight publish/subscribe model is perfect for sending data to the cloud or to mobile dashboards.
• For legacy devices, add gateways. Don't fight the old stuff; bridge it. You'll get the data you need without a forklift upgrade.

And here's the kicker: stop listening to vendors who want to lock you into their protocol ecosystem. The market is full of players like ABB, Siemens, Schneider Electric, and Rockwell Automation (Maximize Market Research), and they all have their preferences. But your job is to make the network work for your plant, not for their quarterly earnings.

Remember, the industrial automation market is growing at 8.5% CAGR (Maximize Market Research), and IIoT is growing even faster. You need a network that can scale. Layering with the right protocols at the right levels is the only way to do that without painting yourself into a corner.

Sources

• OPC Foundation - https://opcfoundation.org/
• Maximize Market Research - https://www.maximizemarketresearch.com/
• MQTT.org - https://mqtt.org/
• MarketsandMarkets Digital Twin Report - https://www.marketsandmarkets.com/Market-Reports/digital-twin-market-225269522.html