Why Your OT Network Needs Modbus More Than OPC UA

Question: Should You Replace Modbus with OPC UA?

Every vendor webinar, every standards body, every self-proclaimed IIoT expert tells you the same thing: modernize your industrial protocols. Ditch Modbus. Adopt OPC UA. They claim it's the only way to secure your plant and connect to the cloud. I call that lazy thinking. The real question isn't which protocol is newer or shinier—it's which one actually solves your problem. And for most of us, that problem is not protocol obsolescence. It's configuration and integration. I'm going to make a case that will get me uninvited from some keynote panels: keep Modbus on the plant floor, and use OPC UA as the integration layer on top. Don't rip out what works.

The Modbus Reality Check

Modbus has been around since the late 1970s (OPC Foundation). It's a master-slave, register-based protocol that runs over both serial RTU and Ethernet TCP. That's ancient history in tech terms, but plant floors are not tech startups. They're built on decades of installed equipment, and that equipment speaks Modbus. The protocol is simple, deterministic, and understood by every electrician and control engineer in the world. When I walk into a facility, I see Modbus RTU on legacy sensors and Modbus TCP on modern PLCs. It's everywhere. And here's the kicker: the global industrial automation market is valued at $184.43 billion in 2025, projected to hit $326.48 billion by 2032 (Maximize Market Research). That's not a shrinking industry. That's a massive installed base that isn't going to rip out its Modbus infrastructure because a standards body says so.

OPC UA's Real Role

Now, don't get me wrong—OPC UA is a fantastic standard. It's vendor-neutral, platform-independent, and has built-in encryption and authentication (OPC Foundation). That makes it the right backbone for IIoT and IT/OT integration. But notice what I just said: integration, not field-level communication. OPC UA is heavy. It runs on powerful hardware, requires complex certificates, and needs careful configuration. That's overkill for a simple temperature read from a pressure transmitter. The fact base confirms the layering: 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). So why are we trying to replace the field-level protocol with the integration protocol? That's like replacing your car's engine with a satellite dish.

The Security Argument Is Overblown

The most common reason I hear for abandoning Modbus is security. Yes, Modbus lacks native encryption and authentication. But so do PROFINET and EtherNet/IP—they're all field-level protocols, not security frameworks. The real security risks in OT are weak authentication, insecure settings, and outdated protocols, as CISA's Secure by Demand guidance warns (CISA Industrial Control Systems). Note that list: weak authentication, insecure settings, outdated protocols. The first two are configuration issues, not protocol issues. You can put Modbus behind a firewall, use a VPN for remote access, and enforce strong authentication at the OT boundary. That's what the ISA/IEC 62443 standards are all about—they define requirements for securing industrial automation and control systems, bridging OT and IT (ISA/IEC 62443). The standard doesn't say 'use OPC UA.' It says implement secure configurations and strong authentication. So stop blaming Modbus for your firewall holes.

How to Layer Both (My Recommendation)

Here's my concrete advice: keep Modbus for the field devices, and add OPC UA as the northbound integration layer. That's how I've seen successful plants operate. For example, in a chemical plant I consulted for, the PLCs talked Modbus TCP to the sensors and actuators. Then we installed an OPC UA server on a gateway that polled the PLCs and exposed the data to the MES and cloud dashboards. This gave us the security and interoperability of OPC UA without touching a single field device. The cost? A few hours of configuration. The result? A secure, modern architecture that didn't require a forklift upgrade.

Now, you might ask about MQTT. It's lightweight and great for telemetry, but it's not a field protocol. It's a messaging transport that's agnostic to payload content (ISO/IEC 20922 MQTT Standard). Use it if you're sending data to the cloud and need publish/subscribe scalability. But for real-time control loops, you still need Modbus or PROFINET. And for IT/OT integration, OPC UA is still the best choice because of its built-in security features.

Quick tip: Before you rip out Modbus, check your OT security configuration. You'll likely find more value in fixing that than in swapping protocols.

The Single Most Important Thing

The most important thing to remember is this: your protocol choice is not a security strategy. The real risk is how you configure your systems. Stop chasing the new protocol and start securing what you have. Layer OPC UA on top for integration, but don't abandon Modbus on the plant floor. It's not the protocol that's the problem—it's your configuration.

Sources

• OPC Foundation - https://opcfoundation.org/
• Maximize Market Research - https://www.maximizemarketresearch.com/
• ISA/IEC 62443 - https://www.isa.org/standards-and-publications/isa-standards/isa-iec-62443-series-of-standards
• CISA Industrial Control Systems - https://www.cisa.gov/topics/industrial-control-systems
• ISO/IEC 20922 MQTT Standard - https://www.iso.org/standard/69466.html