---
title: "OPC UA explained: secure industrial data exchange | Quantlix"
description: "OPC UA (IEC 62541) is the open standard for secure, vendor-neutral industrial data exchange. Learn how its information model, services and PubSub work."
canonical: "https://quantlix.com/en/standards/opc-ua/"
last-updated: 2026-11-16
---

Source: https://quantlix.com/en/standards/opc-ua/
Language: en
Description: OPC UA (IEC 62541) is the open standard for secure, vendor-neutral industrial data exchange. Learn how its information model, services and PubSub work.

**OPC UA** [Industrial and technical data](https://quantlix.com/en/standards/#industrial)

# OPC UA: secure data exchange for industrial automation

OPC UA is the OPC Foundation's platform-independent architecture for exchanging industrial data securely, combining an information model with client-server and publish-subscribe communication. It is also IEC 62541.

[Discuss your project](https://quantlix.com/en/contact/) [Read the key points](https://quantlix.com/en/standards/opc-ua/#standard-overview)

## At a glance

**Full name**

OPC Unified Architecture (OPC 10000 series), published internationally as IEC 62541

**Published by**

OPC Foundation; IEC Technical Committee 65 (SC 65E) for the IEC 62541 series

**Type**

Open specification and international standard series

**Current version**

Release 1.05, with parts at 1.05.06 (October 2025) or 1.05.07 (April 2026); new IEC 62541 editions from December 2025 and January 2026

**Applies to**

Device, controller, SCADA, MES and cloud software vendors, and the manufacturers, utilities and process plants that connect them

**Last reviewed**

November 16, 2026 (2026-11-16)

## In plain terms

### Key points

- OPC UA pairs a data model with services to browse, read, write, subscribe and call methods, so meaning travels with the data.
- Security is built in: applications identify themselves with X.509 certificates, and messages can be signed and encrypted.
- PubSub, defined in Part 14, adds publish-subscribe messaging over UDP, Ethernet or MQTT brokers.
- Companion specifications reuse the core model to describe specific device types and industries.
- The OPC Foundation certifies products through accredited test labs, testing against OPC UA profiles.

### What is OPC UA?

OPC UA (OPC Unified Architecture) is **a platform-independent, service-oriented architecture for exchanging industrial data securely**. The OPC Foundation released it in 2008 and publishes it as the OPC 10000 series, and the IEC publishes the same content as the IEC 62541 series.

Before OPC UA, industrial software often relied on OPC Classic interfaces tied to Windows, or on vendor protocols that needed a separate driver for each connection. OPC UA gives machines, controllers, SCADA, manufacturing execution systems (MES) and cloud applications one way to describe and exchange data, on any operating system and with security designed in from the start.

### What OPC UA covers

The core specification has more than twenty parts. These are the ones most projects meet first:

- **Address space and information model.** Parts 3 and 5 define how a server exposes objects, variables, methods and the references between them, so data arrives with its type, units and context.
- **Services.** Part 4 defines the services clients use to browse, read, write, subscribe to changes and call methods.
- **Security model.** Part 2 describes how applications authenticate with X.509 certificates, how messages are signed and encrypted, and how users are authorized and audited.
- **Mappings and profiles.** Part 6 maps the abstract services to concrete encodings and transports, and Part 7 groups features into profiles that products declare and are tested against.
- **Specialized models.** Further parts cover data access, alarms and conditions, historical access, aggregates and role-based security, among others.
- **PubSub.** Part 14 adds publish-subscribe communication beside client-server.

### Client-server and PubSub

In client-server mode, a client opens a secure session with a server, sends requests and receives results. Subscriptions let the client receive data changes and events without polling, each delivered to that one client.

**PubSub suits many-to-many distribution.** Publishers send messages without knowing who receives them, and subscribers choose the data they need without knowing its source. Part 14 defines binary (UADP) and JSON message formats and transports over UDP, Ethernet and MQTT brokers, which is why OPC UA and [MQTT](https://quantlix.com/en/standards/mqtt/) often appear in the same architecture.

### Releases and companion specifications

OPC UA is at release 1.05, updated in batches of parts. In November 2026 the OPC Foundation online reference showed several core parts at 1.05.06 (October 2025) and others, including Services, Mappings and Data Access, at 1.05.07 (April 2026). New IEC 62541 editions of the core parts, among them Part 1 as a full International Standard for the first time, were published in December 2025 and January 2026.

Companion specifications build on the core model to describe particular kinds of equipment and industries in the factory, process and energy domains. A server that implements one gives every client the same structure for, say, a machine or an instrument, which saves mapping work on each project.

### How it shows up in software projects

- **Information modeling.** Teams agree which companion specification or custom model each server exposes, including namespace URIs and node identifiers, before writing integration code.
- **Security configuration.** Certificates are issued, trusted and renewed for every client and server, and connections use signing and encryption rather than the unsecured mode.
- **Read-only integration.** Analytics and cloud connectors can browse, read and subscribe only, with an account on the server that cannot write values or call methods.
- **Data quality.** Each value keeps its source timestamp, server timestamp and status code, so downstream systems can tell good data from stale or uncertain data.
- **Version records.** Integrations record the release and profiles each server declares, since behavior can differ between releases.

### How we work with OPC UA

We design and build OPC UA integrations: edge gateways that collect plant data, information models mapped to MES and ERP systems, and read-only connectors that feed analytics without touching control. See our [IoT and edge computing](https://quantlix.com/en/services/iot-edge-computing/) service and our work in [manufacturing](https://quantlix.com/en/industries/manufacturing/).

We describe interoperability carefully. A client or server earns the OPC Foundation certification logo only through an accredited test lab, so we state which profiles our integrations were tested against and with which systems. For the business and operations models above the device level, see [ISA-95](https://quantlix.com/en/standards/isa-95/).

## Where it applies

Industries where this standard often shapes the work.

- ### [Manufacturing](https://quantlix.com/en/industries/manufacturing/)

  Connected factories, quality inspection and production planning
- ### [Oil & Gas](https://quantlix.com/en/industries/oil-and-gas/)

  Asset monitoring, field data and maintenance planning

## Related standards

[All standards](https://quantlix.com/en/standards/)

- MQTT

  ### [Lightweight messaging for IoT](https://quantlix.com/en/standards/mqtt/)

  MQTT is the OASIS standard publish-subscribe messaging protocol for devices and telemetry, in which clients exchange messages through a broker. Versions 3.1.1 (also ISO/IEC 20922) and 5.0 are in use.
- ISA-95

  ### [Enterprise and manufacturing integration](https://quantlix.com/en/standards/isa-95/)

  ISA-95 is the international standard, also published as IEC 62264, that defines how business systems such as ERP exchange information with manufacturing operations and control, using shared models and terms.
- IEC 62443

  ### [Industrial control system security](https://quantlix.com/en/standards/iec-62443/)

  IEC 62443 is the international series of standards for securing industrial automation and control systems, with requirements for asset owners, service providers, system integrators and product suppliers.

## Services that support this work

The services we usually bring to projects that involve this standard.

[View all services](https://quantlix.com/en/services/)

### [IoT and edge computing](https://quantlix.com/en/services/iot-edge-computing/)

Connect machines, sensors and business software with assessed IoT and edge integrations. Define data meaning, connectivity, permitted actions and recovery.

### [Data analytics](https://quantlix.com/en/services/data-analytics/)

Quantlix builds analytics pipelines and business intelligence tools that turn operational data into defined metrics, useful reports and decision support.

### [Enterprise applications](https://quantlix.com/en/services/enterprise-applications/)

Quantlix designs and builds enterprise applications for internal workflows, business rules and system integration, with clear access controls and maintainable architecture.

## Questions, answered

What teams usually ask us about this standard.

**Is OPC UA the same as IEC 62541?**

Yes, in content. The OPC Foundation publishes the specification as the OPC 10000 series, and the IEC publishes it as IEC 62541. New IEC editions of several core parts appeared in December 2025 and January 2026.

**What is the latest version of OPC UA?**

Release 1.05. The OPC Foundation updates parts in batches, so in November 2026 its online reference showed some parts at 1.05.06 (October 2025) and others, such as Services and Data Access, at 1.05.07 (April 2026). The official specification takes precedence over that reference site.

**What is the difference between OPC UA and MQTT?**

MQTT is a lightweight transport that moves messages through a broker but does not define what the data means. OPC UA defines the information model and services, and its PubSub part can use an MQTT broker as one of its transports.

**How does OPC UA differ from OPC Classic?**

OPC Classic specifications such as OPC DA were tied to Microsoft Windows technology. OPC UA, released in 2008, is platform independent and merges the Classic functions into one extensible framework with security built in.

**Can an OPC UA product be certified?**

Yes. The OPC Foundation certifies clients, servers, publishers and subscribers through accredited certification test labs. Software development kits cannot be certified directly, but products built with them can.

## Official sources

Read the official text before relying on any detail. What applies to you depends on your role, your location and the version in force.

- [OPC Unified Architecture (OPC Foundation)](https://opcfoundation.org/about/opc-technologies/opc-ua/)
- [OPC UA online reference (OPC 10000 parts)](https://reference.opcfoundation.org/)
- [IEC 62541-1:2025 on the IEC webstore](https://webstore.iec.ch/en/publication/81513)
- [OPC Foundation certification program](https://opcfoundation.org/certification/overview-benefits/)

These guides explain each standard in plain terms. They are not legal advice, and they do not state that any product or organization conforms to a standard.

## Planning software around this standard?

Tell us which systems are involved and what you need to show. We will help you build the requirements in from the start.

[Discuss your project](https://quantlix.com/en/contact/)
