OPC UA Protocol: Industrial IoT Data Exchange Explained

The OPC UA protocol industrial IoT standard has become the backbone of Industry 4.0 data exchange globally — and Indian manufacturing is increasingly adopting it for connecting factory floor devices to cloud platforms, ERP systems, and digital twin applications. Unlike legacy protocols such as Modbus (which only moves raw data values), OPC UA provides semantic context — meaning machines can exchange self-describing data that both humans and software can interpret without custom configuration. This guide explains OPC UA fundamentals, security architecture, and how to get started.

What is OPC UA?
OPC UA Architecture
OPC UA Information Model
Security: Encryption and Authentication
Implementing OPC UA: Getting Started
OPC UA Adoption in Indian Industry
Frequently Asked Questions

What is OPC UA?

OPC Unified Architecture (OPC UA) is an IEC 62541 standard for machine-to-machine (M2M) and industrial IoT communication developed by the OPC Foundation. The "UA" part is key — previous OPC standards (Classic OPC: DA, HDA, A&E) were Windows-only, COM/DCOM-based, and not suitable for cross-platform or internet communication. OPC UA rebuilds the concept from the ground up as a platform-independent, internet-scale protocol.

OPC UA transport can use TCP (binary protocol on port 4840), HTTPS (on port 443 for firewall traversal), or MQTT (for pub/sub IoT patterns). The same OPC UA information model and security is preserved regardless of transport. This makes OPC UA equally suitable for:

PLC-to-SCADA communication on a local OT network (TCP binary, low overhead)
Factory-to-cloud data exchange via MQTT over 4G/LTE in India
Cross-company data exchange in supply chain integration (HTTPS through corporate firewalls)

Recommended: 5V Modbus RTU 4-Channel Relay Module — Start with Modbus before OPC UA — understanding the simpler protocol makes OPC UA’s advantages clearer by contrast.

OPC UA Architecture

OPC UA uses a client-server and publish-subscribe (pub/sub) model:

Client-Server (Request-Response)

An OPC UA client (SCADA, MES, cloud gateway) connects to an OPC UA server (embedded in a PLC, machine controller, or standalone gateway). The client can:

Browse the server’s address space to discover available data nodes.
Read node values on demand.
Subscribe to monitored items — the server sends notifications when values change (event-driven, more efficient than polling).
Write values to control outputs.
Call methods — OPC UA supports remote procedure calls (e.g., "StartBatch", "RecalibrateAxis").

Publish-Subscribe (Pub/Sub)

Added in OPC UA 1.04, Pub/Sub uses a message-oriented broker (MQTT, AMQP) as an intermediary. Publishers (PLCs, sensors) send data to topics; multiple subscribers receive simultaneously. This is ideal for IoT cloud integration where the cloud broker buffers data and multiple consumers (dashboard, historian, AI model) can subscribe independently.

OPC UA Information Model

The information model is what makes OPC UA unique among industrial protocols. Instead of raw register values (Modbus: register 40001 = some 16-bit integer), OPC UA provides a structured address space with:

Objects: Representing real-world entities (Motor1, Tank3, Valve_FV101).
Variables: Properties of objects with data type, engineering unit, timestamp, and quality status (MotorSpeed, TankLevel, ValvePosition).
Methods: Functions that can be called (StartMotor, CalibrateLevel, ResetFault).
Types: Object Types define templates — a MotorType can be instantiated for every motor in the plant, ensuring consistent structure.

Companion specifications extend OPC UA for specific industries — OPC UA for Machinery (OPC 40001-1), OPC UA for Robotics (OPC 40010-1), and OPC UA for CNC Systems. A machine implementing the Machinery companion spec exposes a standard MotorDriveType structure — any OPC UA client can understand it without vendor-specific configuration. This is the semantic interoperability that Modbus and PROFIBUS cannot provide.

Security: Encryption and Authentication

OPC UA has built-in security at three layers — absent from all legacy industrial protocols:

Transport Security (TLS)

All OPC UA TCP connections can (and in modern implementations, must) use TLS encryption. Three security modes: None (no security — only for development/testing), Sign (message integrity, no encryption), Sign & Encrypt (full TLS — required for production).

Application Authentication (X.509 Certificates)

Each OPC UA application (client and server) has an X.509 certificate. On connection, both sides exchange and validate certificates — mutual authentication. An OPC UA server can maintain a trust list of known client certificates and reject unknown clients. Self-signed certificates work for private OT networks; PKI-issued certificates are used for internet-facing deployments.

User Authentication

Beyond application certificates, OPC UA supports user-level authentication: anonymous, username/password, or user certificates. User roles can restrict which nodes each user can read or write — a maintenance engineer might have read-only access while the automation engineer has write access for configuration.

Implementing OPC UA: Getting Started

Open Source Implementations

open62541: C library for OPC UA client and server. Runs on Linux, Windows, and embedded systems (Arduino, STM32, ESP32 with enough RAM). Easiest entry point for embedded systems.
Node-OPCUA: JavaScript/Node.js OPC UA implementation. Ideal for running on Raspberry Pi as an OPC UA gateway collecting Modbus data from PLCs.
python-opcua / asyncua: Python OPC UA client/server. Excellent for quick prototyping and cloud integration scripts.

#!/usr/bin/env python3
# Simple OPC UA client reading temperature from a Siemens S7-1200
# Requires: pip install asyncua

import asyncio
from asyncua import Client

async def main():
    url = "opc.tcp://192.168.1.100:4840"  # PLC IP address
    async with Client(url=url) as client:
        # Browse to find the temperature node
        # NodeId comes from TIA Portal OPC UA configuration
        temp_node = client.get_node("ns=3;s="DB_Process"."Temperature"")
        temp_value = await temp_node.get_value()
        print(f"Current temperature: {temp_value:.1f} °C")

asyncio.run(main())

Recommended: 4-20mA to 5V Converter for Arduino Industrial Sensor Interface Board — Build OPC UA gateway nodes that read 4-20mA sensors and publish them as OPC UA variables.

OPC UA Adoption in Indian Industry

OPC UA adoption in India is growing rapidly, driven by:

Government initiatives: DPIIT’s National Industrial Corridor Programme mandates digital manufacturing standards. Smart City Mission connects industrial parks with digital infrastructure.
Multinational mandates: Global automotive, pharmaceutical, and electronics manufacturers require OPC UA from their Indian suppliers for supply chain integration.
PLC support: Siemens S7-1200/1500 (v4+), Beckhoff TwinCAT 3, Mitsubishi iQ-R, and Fanuc CNCs all have native OPC UA servers. With the dominant PLCs already supporting OPC UA, implementation cost is low.
Cloud platforms: AWS IoT SiteWise, Azure IoT Hub, and GE Predix natively consume OPC UA data. This simplifies cloud integration for Indian manufacturers using these platforms.

Current challenge: Indian automation engineers trained on Modbus/PROFIBUS need re-skilling. TÜV, Siemens, and Rockwell offer OPC UA training in India; online courses on Udemy and the OPC Foundation eLearning portal are also available.

Recommended: 12V Modbus RTU 4-Channel Relay Module RS485 — While migrating to OPC UA, use Modbus-to-OPC UA gateways to connect legacy Modbus devices to the modern architecture.

Frequently Asked Questions

Is OPC UA replacing Modbus and PROFIBUS?

OPC UA is becoming the preferred northbound protocol for enterprise integration and cloud connectivity. At the field level, PROFINET and EtherNet/IP remain dominant for device-to-controller communication. Many PLCs expose both PROFINET (for device I/O) and OPC UA (for vertical integration to MES/cloud). The trend is convergence at the enterprise layer while fieldbuses persist at the device layer — for now.

Does OPC UA require an internet connection?

No. OPC UA works entirely on local OT networks without internet. The security features (encryption, certificates) function identically on a private network. Internet connectivity is only required when you want to exchange data with cloud platforms or remote systems.

How does OPC UA compare to MQTT for IoT?

MQTT is a lightweight pub/sub protocol with no data model or semantic context. OPC UA provides structured, self-describing data. For cloud IoT connectivity, both are used: OPC UA Pub/Sub over MQTT combines OPC UA’s semantic richness with MQTT’s scalable broker infrastructure. This is the recommended approach for Industry 4.0 architectures (IEC 62541-14 defines OPC UA over MQTT).

Can I use OPC UA on an Arduino or ESP32?

Arduino (limited RAM) has a basic OPC UA server implementation via open62541 on high-RAM variants (Arduino Due, Portenta H7). ESP32 (520KB SRAM) can run a minimal OPC UA server using open62541 with reduced feature set. For a full-featured OPC UA server on an embedded gateway, use a Raspberry Pi (Linux) running the complete open62541 stack — this is the most practical approach for Indian DIY industrial IoT projects.

Shop Industrial Automation at Zbotic →