{"data":{"slug":"opc-ua-protocol-overview","title":"OPC UA Protocol Overview","summary":"OPC Unified Architecture (OPC UA) , defined by IEC 62541, is the platform-independent, service-oriented architecture for secure, reliable data exchange in…","category":{"slug":"opc-solutions","name":"OPC Solutions"},"url":"https://wiki.aspotomasyon.com/article/opc-ua-protocol-overview","markdown_url":"https://wiki.aspotomasyon.com/article/opc-ua-protocol-overview.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/opc-ua-protocol-overview","published":"2026-05-12T12:47:31+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":873,"image":"https://wiki.aspotomasyon.com/assets/social/opc-ua-protocol-overview-eae98061a685.png","html":"

OPC Unified Architecture (OPC UA), defined by IEC 62541, is the platform-independent, service-oriented architecture for secure, reliable data exchange in industrial automation. It is the successor to OPC Classic (OPC DA, OPC HDA, OPC A&E) and has become the foundational communication standard for Industry 4.0 and IIoT initiatives worldwide.

\"A
A conceptual OPC UA client/server path. Application certificates establish application trust; user authorization controls what a connected user may do. View full size
\n\n

Architecture Overview

\n\n

OPC UA follows a layered architecture that separates transport, security, and application concerns:

\n\n\n\n

Layered Architecture

\n\n
  +-------------------------------------------+\n  |        OPC UA Client Application          |\n  |  (HMI, MES, Historian, Analytics)         |\n  +-------------------------------------------+\n  |        OPC UA Client SDK                  |\n  +-------------------------------------------+\n  |  Security (X.509 Certs + Encryption)      |\n  +-------------------------------------------+\n  |  Transport (TCP / HTTPS / WebSocket)      |\n  +===========================================+\n  |  Transport (TCP / HTTPS / WebSocket)      |\n  +-------------------------------------------+\n  |  Security (X.509 Certs + Encryption)      |\n  +-------------------------------------------+\n  |        OPC UA Server SDK                  |\n  +-------------------------------------------+\n  |        OPC UA Server Application          |\n  |  (PLC, DCS, Gateway, Kepware)             |\n  +-------------------------------------------+
\n\n

Information Model

\n\n

The OPC UA Information Model is a graph-based structure of Nodes connected by References. This is a fundamental departure from the tag-based flat namespace of OPC Classic:

\n\n\n\n

Security Model

\n\n

OPC UA provides comprehensive, application-level security independent of the transport protocol:

\n\n
    \n
  1. Authentication — X.509 certificate-based or username/password authentication. Servers validate client identity before granting access.
    2. \n
  2. Authorization — Role-based access control (RBAC) per node. Administrators can restrict read, write, or browse permissions.
    3. \n
  3. Encryption — AES-128 or AES-256 with RSA-OAEP key exchange protects all communication.
    4. \n
  4. Integrity — Messages are signed to detect tampering. Every message includes a signature verified by the recipient.
    5. \n
  5. Auditing — Security-relevant events are logged for compliance and forensic analysis.
    6. \n
\n\n

OPC UA vs. OPC Classic

\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n
FeatureOPC UA (IEC 62541)OPC Classic (DA/HDA)
PlatformCross-platform (Windows, Linux, embedded)Windows only (DCOM-dependent)
SecurityBuilt-in (X.509, encryption, RBAC)DCOM security (complex, fragile)
Data ModelRich object-oriented information modelFlat tag namespace
Firewall FriendlySingle port, no DCOMRequires DCOM port range (135 + dynamic)
ScalabilityThousands of sessions and subscriptionsLimited by DCOM overhead
DiscoveryLDS (Local Discovery Server)Manual configuration or OPCEnum
SubscriptionsNative pub/sub with configurable intervalsGroup-based polling
Cloud ReadyYes (MQTT, AMQP, HTTPS transports)No
\n\n

Benefits for Industry 4.0

\n\n

OPC UA is a key enabler of Industry 4.0 because it solves the interoperability challenge that has plagued industrial automation for decades:

\n\n\n\n
\n

ASP OTOMASYON A.Ş. and its subsidiaries OPCTurkey and ASP Dijital provide end-to-end industrial engineering solutions for process automation, data operations and AI.

\n

References & Further Reading

\n
    \n
  1. OPC Foundation — OPC UA Specification (IEC 62541) — Official specification for OPC Unified Architecture, including address space model, services, security, and Pub/Sub.
    2. \n
  2. OPC UA Security Architecture — Official OPC Foundation documentation on security policies, X.509 certificate management, encryption, and authentication for OPC UA.
    3. \n
  3. OPC UA Part 14: PubSub — IEC 62541-14 — Official specification for OPC UA publish-subscribe communication pattern with MQTT and AMQP transport mappings.
    4. \n
  4. IEC 62541: OPC Unified Architecture — Multi-Part Standard — International standard for OPC UA, covering all parts from data access through alarms, history, and Pub/Sub.
    5. \n
  5. OPC Foundation Companion Specifications — Official directory of industry-specific OPC UA information models for Euromap, ISA-95, PackML, MDIS, and more.
    6. \n

What a successful connection does not prove

Browsing the address space confirms only part of an integration. Verify user permissions, engineering units, data types, StatusCodes, timestamps, and subscription behavior at the final consumer. Disconnect the source during a controlled test and observe whether the client clearly distinguishes last-known data from current observations. OPC UA supplies mechanisms for interoperability and security; the configured applications still need acceptance testing.

Continue with the related practical guide.

Apply this to your project

Follow an ASP project guide to connect the fundamentals with implementation and acceptance.

\"Engineering
Engineering review sequence: Discover → Authenticate → Subscribe → Recover. Keep the recorded evidence with the accepted configuration. View full size

Primary references and further reading

Use the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.

","markdown":"# OPC UA Protocol Overview\n\n> OPC Unified Architecture (OPC UA) , defined by IEC 62541, is the platform-independent, service-oriented architecture for secure, reliable data exchange in…\n\n- Canonical URL: https://wiki.aspotomasyon.com/article/opc-ua-protocol-overview\n- Publisher: ASP OTOMASYON A.Ş. (ASP OTOMASYON Wiki)\n- Category: OPC Solutions\n- Published: 2026-05-12 · Updated: 2026-09-13\n- Reading time: 4 min · Language: English\n\n**OPC Unified Architecture (OPC UA)**, defined by IEC 62541, is the platform-independent, service-oriented architecture for secure, reliable data exchange in industrial automation. It is the successor to OPC Classic (OPC DA, OPC HDA, OPC A&E) and has become the foundational communication standard for Industry 4.0 and IIoT initiatives worldwide.\n\n![A conceptual OPC UA client/server path. Application certificates establish application trust; user authorization controls what a connected user may do.](https://wiki.aspotomasyon.com/assets/diagrams/opc-solutions-context.svg)\n\n*A conceptual OPC UA client/server path. Application certificates establish application trust; user authorization controls what a connected user may do.*\n\n## Architecture Overview\n\nOPC UA follows a layered architecture that separates transport, security, and application concerns:\n\n- **Transport Layer** — Supports multiple transport mappings including OPC TCP (opc.tcp://), HTTPS, and WebSocket. The native binary protocol provides efficient real-time data exchange with minimal overhead.\n- **Security Layer** — Implements authentication, authorization, encryption, and integrity signing using X.509 certificates and configurable security policies (None, Basic128Rsa15, Basic256, Basic256Sha256).\n- **Application Layer** — Defines the OPC UA Services (Read, Write, Subscribe, Browse, Method Call) and the Information Model that structures process data.\n\n### Layered Architecture\n\n```\n +-------------------------------------------+\n | OPC UA Client Application |\n | (HMI, MES, Historian, Analytics) |\n +-------------------------------------------+\n | OPC UA Client SDK |\n +-------------------------------------------+\n | Security (X.509 Certs + Encryption) |\n +-------------------------------------------+\n | Transport (TCP / HTTPS / WebSocket) |\n +===========================================+\n | Transport (TCP / HTTPS / WebSocket) |\n +-------------------------------------------+\n | Security (X.509 Certs + Encryption) |\n +-------------------------------------------+\n | OPC UA Server SDK |\n +-------------------------------------------+\n | OPC UA Server Application |\n | (PLC, DCS, Gateway, Kepware) |\n +-------------------------------------------+\n```\n\n## Information Model\n\nThe OPC UA Information Model is a graph-based structure of **Nodes** connected by **References**. This is a fundamental departure from the tag-based flat namespace of OPC Classic:\n\n- **Object Nodes** — Represent physical or logical entities (e.g., a pump, a production line, a tank).\n- **Variable Nodes** — Hold data values with timestamps and quality codes. Two types: *Properties* (metadata) and *DataVariables* (process data).\n- **Method Nodes** — Callable functions exposed by the server (e.g., `StartMotor()` , `CalibrateSensor()` ).\n- **Reference Types** — Define relationships: `HasComponent` , `HasProperty` , `Organizes` , `HasTypeDefinition` .\n\n## Security Model\n\nOPC UA provides comprehensive, application-level security independent of the transport protocol:\n\n1. **Authentication** — X.509 certificate-based or username/password authentication. Servers validate client identity before granting access.\n2. **Authorization** — Role-based access control (RBAC) per node. Administrators can restrict read, write, or browse permissions.\n3. **Encryption** — AES-128 or AES-256 with RSA-OAEP key exchange protects all communication.\n4. **Integrity** — Messages are signed to detect tampering. Every message includes a signature verified by the recipient.\n5. **Auditing** — Security-relevant events are logged for compliance and forensic analysis.\n\n## OPC UA vs. OPC Classic\n\n| Feature | OPC UA (IEC 62541) | OPC Classic (DA/HDA) |\n| --- | --- | --- |\n| Platform | Cross-platform (Windows, Linux, embedded) | Windows only (DCOM-dependent) |\n| Security | Built-in (X.509, encryption, RBAC) | DCOM security (complex, fragile) |\n| Data Model | Rich object-oriented information model | Flat tag namespace |\n| Firewall Friendly | Single port, no DCOM | Requires DCOM port range (135 + dynamic) |\n| Scalability | Thousands of sessions and subscriptions | Limited by DCOM overhead |\n| Discovery | LDS (Local Discovery Server) | Manual configuration or OPCEnum |\n| Subscriptions | Native pub/sub with configurable intervals | Group-based polling |\n| Cloud Ready | Yes (MQTT, AMQP, HTTPS transports) | No |\n\n## Benefits for Industry 4.0\n\nOPC UA is a key enabler of Industry 4.0 because it solves the interoperability challenge that has plagued industrial automation for decades:\n\n- **Vendor-Neutral** — Equipment from different manufacturers can expose a standardized information model, enabling plug-and-produce scenarios.\n- **Edge-to-Cloud** — OPC UA runs on resource-constrained edge devices and scales up to cloud platforms. The OPC UA over TSN extension (IEC/IEEE 60802) is an emerging standard that brings deterministic communication to Ethernet networks. While still in early deployment, it is gaining traction for time-sensitive applications.\n- **Semantic Interoperability** — Companion specifications (EUROMAP for plastics, ISA-95 for MES, PackML for packaging) define standardized models for specific industries.\n- **IT/OT Convergence** — OPC UA bridges operations technology and information technology with a common, secure protocol both domains understand.\n\n> ASP OTOMASYON A.Ş. and its subsidiaries OPCTurkey and ASP Dijital provide end-to-end industrial engineering solutions for process automation, data operations and AI.\n\n---\n\n## References & Further Reading\n\n1. [OPC Foundation — OPC UA Specification (IEC 62541)](https://reference.opcfoundation.org/specs/OPC-10000-1) — Official specification for OPC Unified Architecture, including address space model, services, security, and Pub/Sub.\n2. [OPC UA Security Architecture](https://reference.opcfoundation.org/) — Official OPC Foundation documentation on security policies, X.509 certificate management, encryption, and authentication for OPC UA.\n3. [OPC UA Part 14: PubSub — IEC 62541-14](https://reference.opcfoundation.org/Core/Part14/v105/docs/) — Official specification for OPC UA publish-subscribe communication pattern with MQTT and AMQP transport mappings.\n4. [IEC 62541: OPC Unified Architecture — Multi-Part Standard](https://www.iec.ch) — International standard for OPC UA, covering all parts from data access through alarms, history, and Pub/Sub.\n5. [OPC Foundation Companion Specifications](https://reference.opcfoundation.org/) — Official directory of industry-specific OPC UA information models for Euromap, ISA-95, PackML, MDIS, and more.\n\n## What a successful connection does not prove\n\nBrowsing the address space confirms only part of an integration. Verify user permissions, engineering units, data types, StatusCodes, timestamps, and subscription behavior at the final consumer. Disconnect the source during a controlled test and observe whether the client clearly distinguishes last-known data from current observations. OPC UA supplies mechanisms for interoperability and security; the configured applications still need acceptance testing.\n\nContinue with [the related practical guide](https://wiki.aspotomasyon.com/article/opc-ua-data-quality-timestamps).\n\n## Apply this to your project\n\n- Record the endpoint, supported security policies, application identity, certificate expiry, and user permissions.\n- Verify the value, engineering unit, StatusCode, and source timestamp together at the receiving application.\n- Test disconnection and recovery with representative subscriptions; preserve evidence of any data gaps or repeated values.\n\n[Follow an ASP project guide](https://wiki.aspotomasyon.com/guides) to connect the fundamentals with implementation and acceptance.\n\n![Engineering review sequence: Discover → Authenticate → Subscribe → Recover. Keep the recorded evidence with the accepted configuration.](https://wiki.aspotomasyon.com/assets/diagrams/opc-solutions-review.svg)\n\n*Engineering review sequence: Discover → Authenticate → Subscribe → Recover. Keep the recorded evidence with the accepted configuration.*\n\n## Primary references and further reading\n\nUse the original specifications and product documentation for implementation details. The examples in this guide are illustrative engineering scenarios, not published project results.\n\n- [OPC Foundation — OPC UA Part 4: Services](https://reference.opcfoundation.org/specs/OPC-10000-4/)\n- [OPC Foundation — OPC UA Part 2: Security Model](https://reference.opcfoundation.org/specs/OPC-10000-2/)\n\n---\n\nCite the canonical article: https://wiki.aspotomasyon.com/article/opc-ua-protocol-overview (OPC UA Protocol Overview, ASP OTOMASYON, updated 2026-09-13).\n","headings":[{"id":"architecture-overview","title":"Architecture Overview"},{"id":"information-model","title":"Information Model"},{"id":"security-model","title":"Security Model"},{"id":"opc-ua-vs-opc-classic","title":"OPC UA vs. OPC Classic"},{"id":"benefits-for-industry-40","title":"Benefits for Industry 4.0"},{"id":"references-further-reading","title":"References & Further Reading"},{"id":"what-a-successful-connection-does-not-prove","title":"What a successful connection does not prove"},{"id":"apply-this-to-your-project","title":"Apply this to your project"},{"id":"primary-references-and-further-reading","title":"Primary references and further reading"}],"faq":[],"references":[{"name":"OPC Foundation — OPC UA Specification (IEC 62541)","url":"https://reference.opcfoundation.org/specs/OPC-10000-1"},{"name":"OPC UA Security Architecture","url":"https://reference.opcfoundation.org/"},{"name":"OPC UA Part 14: PubSub — IEC 62541-14","url":"https://reference.opcfoundation.org/Core/Part14/v105/docs/"},{"name":"IEC 62541: OPC Unified Architecture — Multi-Part Standard","url":"https://www.iec.ch"},{"name":"OPC Foundation — OPC UA Part 4: Services","url":"https://reference.opcfoundation.org/specs/OPC-10000-4/"},{"name":"OPC Foundation — OPC UA Part 2: Security Model","url":"https://reference.opcfoundation.org/specs/OPC-10000-2/"}],"related":[{"slug":"industrial-communication-protocol-selection-guide","title":"Choosing an Industrial Communication Protocol: A Decision Guide","summary":"Pick an industrial protocol by the job it must do (cyclic control, device access, plant data, or telemetry), then match timing, data model, and security to…","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/industrial-communication-protocol-selection-guide","markdown_url":"https://wiki.aspotomasyon.com/article/industrial-communication-protocol-selection-guide.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/industrial-communication-protocol-selection-guide","published":"2026-10-11T11:46:21+00:00","modified":"2026-10-11T11:46:21+00:00","reading_minutes":9,"word_count":1767,"image":"https://wiki.aspotomasyon.com/assets/social/industrial-communication-protocol-selection-guide-bbf4fa97587d.png"},{"slug":"ethercat-fundamentals-distributed-clocks","title":"EtherCAT Fundamentals: Frames, Topology, and Distributed Clocks","summary":"EtherCAT sends frames that each device reads and writes as they pass, so cycle time, topology, and clock synchronization become engineering decisions you can…","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/ethercat-fundamentals-distributed-clocks","markdown_url":"https://wiki.aspotomasyon.com/article/ethercat-fundamentals-distributed-clocks.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/ethercat-fundamentals-distributed-clocks","published":"2026-10-11T11:46:21+00:00","modified":"2026-10-11T11:46:21+00:00","reading_minutes":9,"word_count":1796,"image":"https://wiki.aspotomasyon.com/assets/social/ethercat-fundamentals-distributed-clocks-a86776332437.png"},{"slug":"protocol-gateway-patterns","title":"Protocol Gateway and Translation Patterns","summary":"No plant runs one protocol: Modbus coexists with PROFINET, EtherNet/IP with OPC UA, HART with MQTT — and the systems that need the data (SCADA, MES, cloud)…","category":{"slug":"modern-connectivity","name":"Modern Connectivity"},"url":"https://wiki.aspotomasyon.com/article/protocol-gateway-patterns","markdown_url":"https://wiki.aspotomasyon.com/article/protocol-gateway-patterns.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/protocol-gateway-patterns","published":"2026-08-11T13:05:24+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":4,"word_count":871,"image":"https://wiki.aspotomasyon.com/assets/social/protocol-gateway-patterns-48062598cdfb.png"},{"slug":"opc-ua-pub-sub-configuration","title":"OPC UA Pub/Sub Configuration and Deployment Guide","summary":"OPC UA Pub/Sub extends the traditional client-server OPC UA model with a publish-subscribe communication pattern.","category":{"slug":"opc-solutions","name":"OPC Solutions"},"url":"https://wiki.aspotomasyon.com/article/opc-ua-pub-sub-configuration","markdown_url":"https://wiki.aspotomasyon.com/article/opc-ua-pub-sub-configuration.md","api_url":"https://wiki.aspotomasyon.com/api/v1/articles/opc-ua-pub-sub-configuration","published":"2026-05-13T11:58:29+00:00","modified":"2026-09-13T11:07:23+00:00","reading_minutes":6,"word_count":1147,"image":"https://wiki.aspotomasyon.com/assets/social/opc-ua-pub-sub-configuration-33cfd0c96572.png"}],"citation":"ASP OTOMASYON. OPC UA Protocol Overview. Updated 2026-09-13. https://wiki.aspotomasyon.com/article/opc-ua-protocol-overview"}}