A typical plant has PLCs, industrial Ethernet switches, HMIs, SCADA systems, edge computers, MES platforms, and maybe a few cloud applications. Sooner or later, someone asks: “Should we use Industrial Ethernet or OPC UA?”
The question is misleading, because the two technologies address different parts of the communication architecture. Industrial Ethernet is network connectivity. OPC UA is a standardised industrial information exchange protocol. This article explains what each one does and how they work together.
What Is Industrial Ethernet?
Industrial Ethernet uses Ethernet networking technology in industrial environments. The infrastructure includes industrial Ethernet switches, copper cabling with RJ45 connectors, fibre links with SFP interfaces, PLC Ethernet ports, industrial PCs, HMIs, and remote I/O.
Managed switches add functions such as VLANs, QoS, ring redundancy, traffic monitoring, and managed configuration.
Industrial Ethernet is primarily concerned with moving network traffic between connected devices. It is not one protocol, and not every Industrial Ethernet network runs the same industrial protocol on top.
What Is OPC UA?
OPC UA (Open Platform Communications Unified Architecture) is a platform-independent framework for exchanging information between industrial systems and applications. It supports client/server communication, structured data, data models, security mechanisms, and interoperability between different systems.
Its key strength is information modelling. A raw value might arrive as Temperature = 72. With OPC UA, the same value can sit in a structure like this:
Machine → Motor → Temperature → Current Value → Unit → Status
Now a SCADA or MES application knows this is a motor temperature, in what unit, and whether the reading is good. Nobody has to decode an anonymous register address.
Industrial Ethernet vs OPC UA: The Basic Difference
| Feature | Industrial Ethernet | OPC UA |
|---|---|---|
| Primary role | Network connectivity | Industrial information exchange |
| Main focus | Moving data across an Ethernet network | Communicating structured industrial information |
| Typical components | Switches, cables, NICs, PLC ports | OPC UA clients, servers, applications |
| Physical infrastructure | Ethernet copper/fiber | Uses underlying network transports |
| Typical use | Device/network connectivity | PLC/SCADA/MES/IT/IIoT data exchange |
| Information modeling | Not its primary purpose | Core capability |
| Can they work together? | Yes | Yes |
This is a functional comparison, not a contest between equivalent technologies.
Where Does OPC UA Sit, and How Do They Work Together?
Think of it as a simple stack, not a strict OSI mapping:
Physical network → Industrial Ethernet → IP/TCP or other supported transport → OPC UA communication → Industrial application
Industrial Ethernet provides the network path. OPC UA provides application-level communication and information modeling on top of it.
A practical flow looks like this:
PLC → Industrial Ethernet Switch → Industrial PC / Edge Gateway → SCADA / MES
- The PLC generates machine or process data.
- Industrial Ethernet connects the devices.
- An OPC UA server exposes selected data.
- An OPC UA client accesses it.
- SCADA, MES, or edge software uses the information.
The Ethernet network carries the traffic. OPC UA standardises how applications exchange and understand the data. Not every PLC speaks OPC UA directly, so some architectures use a gateway or software server.
Industrial Ethernet Is Not a Single Protocol
“Industrial Ethernet” is an umbrella term. PROFINET, EtherNet/IP, EtherCAT, and Modbus TCP are all Ethernet-based, but they have different communication models, characteristics, and use cases.
People often search for “OPC UA vs PROFINET” or “OPC UA vs EtherNet/IP,” but those comparisons need context. Automation protocols are often deeply involved in device-level and control communication. OPC UA is commonly used to exchange structured information between applications, systems, and devices, including systems built on different automation technologies. OPC UA does not universally replace any of these protocols, and modern plants often run several technologies at once.
OPC UA for PLC, SCADA, MES, and IIoT
- PLC: Provides process and control data.
- SCADA: Consumes and visualises operational data.
- MES: Uses production-related information.
- Edge computer: Processes or aggregates data locally.
- IT/cloud systems: Consume selected industrial information.
OPC UA can help connect these layers without every application needing to understand every underlying device protocol. The actual design depends on PLC support, software, gateways, and application requirements.
Control Communication vs Information Exchange
Control-oriented communication may need deterministic behaviour, low latency, cyclic exchange, device-level coordination, and time-sensitive performance.
Information-oriented communication involves machine data, production information, diagnostics, asset information, historical values, and IT/OT integration.
Your actual requirements decide which technology, or combination, fits. OPC UA isn’t inherently unsuitable for time-sensitive work. It offers different communication mechanisms and extensions for different use cases, such as publish/subscribe models, so the right choice depends on the implementation and the application.
OPC UA and Industrial Edge Networking
Machine → PLC → Industrial Ethernet Switch → Edge Gateway → OPC UA → MES / Cloud
An edge device can collect data from equipment, process it locally, and expose or forward selected information over OPC UA. In practice, this helps with data normalisation, system integration, machine-to-IT communication, IIoT applications, and edge analytics.
Security: Two Layers, Not One
Network infrastructure security covers segmentation, VLANs, access control, firewalling, port security, and network monitoring. OPC UA adds its own mechanisms: authentication, encryption, signing, and certificates.
OPC UA security does not replace network security, and network segmentation does not replace application-level security. A secure architecture generally needs both.
Does OPC UA Replace Industrial Ethernet?
No. Industrial Ethernet provides network connectivity. OPC UA provides a framework for exchanging structured industrial information. A system can use both:
PLC → Industrial Ethernet → OPC UA Server → SCADA / MES / Edge
Practical Example: A Factory Network
Sensors / Machines → PLC → Industrial Ethernet Switch → Industrial PC / Edge Gateway → OPC UA → SCADA / MES
Sensors and machines produce signals, and the PLC handles control logic. The switch connects the devices. The industrial PC or gateway runs the OPC UA server or client software, and SCADA or MES consumes the data.
Note that the switch does not become an OPC UA server just because OPC UA traffic passes through it. It provides connectivity. OPC UA functions live in compatible devices or software.
When to Think About Which
Think about Industrial Ethernet when designing device connectivity, switch infrastructure, cable and fibre links, topology, redundancy, VLANs, QoS, and network performance.
Think about OPC UA when designing application-to-application communication, structured machine data, PLC-to-SCADA integration, MES integration, IIoT data exchange, information modelling, and IT/OT interoperability.
Many projects need both.
Common Misunderstandings
- “OPC UA is an Ethernet replacement.” It isn’t. It typically relies on underlying network transports.
- “They’re competing protocols.” They operate at different functional levels.
- “Every PLC needs OPC UA.” That depends on the device and architecture.
- “An Ethernet switch provides OPC UA.” A standard switch forwards traffic. OPC UA needs compatible endpoint software or hardware.
- “OPC UA eliminates network design.” It doesn’t. Topology, redundancy, and segmentation still matter.
Conclusion
Industrial Ethernet and OPC UA are complementary, not interchangeable. Industrial Ethernet connects devices, and OPC UA lets applications exchange meaningful, structured information. A modern architecture may combine Industrial Ethernet for connectivity, industrial protocols for device and control communication, and OPC UA for information exchange and IT/OT integration.
When you plan the network side, choose industrial Ethernet infrastructure around your topology, device requirements, reliability needs, and overall communication architecture, which is the approach Comxus encourages.
Read Also: How to Troubleshoot Packet Loss in Industrial Ethernet
Read Also: IEEE 802.1AS Explained: Time Synchronisation in TSN
