Fact-checked by Grok 2 weeks ago

Open Platform Communications

Open Platform Communications (OPC) is a series of standards for secure and reliable data exchange in industrial automation, enabling seamless communication between devices, software applications, and systems from multiple vendors without restrictions. Developed to abstract complex protocols such as and , OPC allows human-machine interfaces (HMIs), supervisory control and (SCADA) systems, and other software to access real-time data, alarms, events, and historical information from programmable logic controllers (PLCs) and sensors in a platform-independent manner. Managed by the nonprofit , these standards have become foundational for process industries including , , and , promoting vendor-neutral integration and reducing development costs. The origins of OPC trace back to the mid-1990s, when leading automation vendors recognized the inefficiencies of communication protocols in connecting diverse hardware to Windows-based software. In 1995, a comprising companies like Fisher-Rosemount, , Opto 22, Intellution, and others collaborated with to develop a unified interface based on (OLE) technology. This effort culminated in the release of the first OPC specifications in 1996 under the name OLE for Control (OPC Classic), which quickly gained adoption for its client-server architecture supporting data access, alarms, and events. By the early 2000s, OPC Classic had become the for industrial data connectivity on Windows platforms. To address limitations of its Microsoft-centric design, the OPC Foundation initiated the development of a next-generation standard in the early 2000s, resulting in the release of (OPC UA) in 2008. features a multi-layered, that is fully platform-independent, supporting operating systems like , macOS, and embedded devices, while incorporating advanced security mechanisms including , signing, , and auditing. Key capabilities include an extensible using object-oriented concepts like nodes, references, and namespaces for semantic data representation, as well as support for publish-subscribe messaging, complex data types, and integration with web services. Standardized as IEC 62541 by the , OPC UA ensures compliance and global interoperability. OPC UA has seen widespread adoption as a core enabler of Industry 4.0 and the (IIoT), facilitating the convergence of (OT) and (IT) for applications such as real-time analytics, , and digital twins. It serves as the recommended communication protocol for initiatives like the Reference Architectural Model Industrie 4.0 (RAMI 4.0), supporting secure data flows across edge devices, cloud platforms, and enterprise systems. Major vendors including , , and have integrated OPC UA into their products, with companion specifications tailoring the standard for sectors like automotive, pharmaceuticals, and . As of 2025, OPC UA continues to evolve with enhancements for (TSN), field exchange (FX) including the recent revision of FX specifications (RC V1.00.03), and cloud connectivity, ensuring its relevance in emerging ecosystems.

Introduction

Definition and Purpose

Open Platform Communications (OPC) is an interoperability standard for the secure and reliable exchange of real-time data between devices, systems, and applications from multiple vendors in industrial automation and related industries. This standard ensures platform-independent communication, allowing information to flow seamlessly across diverse hardware and software environments without dependence on specific operating systems or protocols. The primary purpose of OPC is to abstract underlying and operating systems, enabling seamless communication without restrictions. It originated as a solution to issues in process control, standardizing interfaces so that human-machine interfaces (HMIs) and supervisory control and (SCADA) systems could interact with various programmable logic controllers (PLCs) through a unified layer that translates generic requests into device-specific operations. OPC's scope encompasses data access for values, alarms and events for notifications, historical data for querying and , and commands for control operations, applied in sectors such as , (including oil and gas, renewables, and utilities), and (IoT) applications. The standard supports both client-server and server-server interfaces to facilitate these functions across industrial ecosystems. OPC evolved from its original designation as "OLE for Process Control," based on Microsoft's (OLE) technology, to "Open Platform Communications" in 2011 to better reflect its expanded platform independence beyond process control domains. The modern iteration, (UA), further enables cross-platform use by integrating these capabilities into a service-oriented framework.

Key Features

Open Platform Communications (OPC), particularly through its Unified Architecture (UA) standard, emphasizes platform independence, enabling seamless operation across diverse environments including Windows, Linux, embedded systems, and cloud infrastructures without dependency on specific operating system APIs. This design leverages standard internet protocols like TCP/IP, HTTP, and WebSockets, allowing scalability from microcontrollers to (ERP) systems. At its core, OPC UA adopts a (SOA) that facilitates information modeling via abstract constructs such as the , nodes, and references, supporting both client-server interactions and publish-subscribe (PubSub) paradigms for efficient data exchange. This SOA structure ensures that service providers can process requests and deliver results in a standardized manner, promoting in industrial settings. Extensibility is a hallmark of OPC UA, permitting the definition of custom data types, namespaces, and domain-specific models tailored to applications in areas like machinery diagnostics or , while preserving through a multi-layered framework. Vendors can extend base information models via sub-typing and vendor-specific namespaces, enabling innovative adaptations without disrupting existing implementations. Reliability in OPC UA is enhanced by built-in session management for consistent data access across connections, subscription mechanisms for updates with notifications on changes, and fault-tolerant protocols that handle lost messages, scenarios, and heartbeats to maintain robust communication. These features ensure in mission-critical environments, with binary encoding optimizing performance and error recovery. OPC maintains openness through publicly available specifications, accessible via the OPC Foundation's resources, alongside certification programs that validate compliance and of implementations. Free developer tools and open-source starter kits further support widespread adoption and customization. features, such as and signing, integrate with these elements to protect , though detailed models are addressed separately.

History

Origins of OPC Classic

In the , the industrial industry grappled with profound challenges stemming from vendor-specific protocols that fragmented data exchange and created silos in and systems. These proprietary interfaces, often tied to specific PLCs and systems, impeded seamless integration between devices and enterprise IT, driving end-users and vendors to seek a unified standard for access. Microsoft's rising dominance in PC-based , particularly through technologies like (), provided a promising foundation to abstract device-specific protocols into a common interface. To tackle these issues, an industrial automation was formed in 1995 by key vendors including Fisher-Rosemount, Rockwell Software, Opto 22, Intellution, and Intuitive Technology, with Microsoft's technical backing. The group publicly unveiled their initiative at the 1995 ISA Show in New Orleans and incorporated as the on April 22, 1996, with 23 initial members worldwide. This non-profit organization focused on developing open specifications under the banner of OLE for Process Control, later termed OPC Classic, to foster multi-vendor compatibility using /DCOM for client-server communications. The inaugural release, (DA) 1.0, arrived in August 1996, enabling standardized real-time data retrieval from PLCs and sensors via a Windows-centric that relied on DCOM, thereby confining it to PC-based environments. Rapid industry uptake followed, with commercial OPC products emerging by late 1996 and the first convened by Rockwell in that year, validating its role as an emerging standard. By mid-1998, enhanced functionality in OPC DA 2.0 addressed early limitations, coinciding with the debut of Alarms and Events (AE) for event notifications; subsequent core specifications like Historical Data Access (HDA) for data archiving and Data eXchange (DX) for server-to-server transfers rounded out the early OPC Classic suite by the early 2000s. These developments cemented OPC Classic's , though its platform dependencies later spurred the shift to .

Development of OPC UA

In 2003, the OPC Foundation initiated the development of (OPC UA), with the first working group meeting held in November, to address the limitations of (DCOM) in OPC Classic, which restricted interoperability to Microsoft Windows environments and complicated cross-platform integration. The primary motivations included achieving platform independence across diverse operating systems such as Windows and , enhancing security through built-in mechanisms like and , and facilitating the convergence of (OT) and (IT) systems to support broader industrial data exchange. This effort aimed to create a that would enable seamless communication from embedded devices to enterprise-level applications, overcoming the proprietary and configuration-heavy nature of earlier OPC standards. The initial release of OPC UA 1.00 occurred in 2008, marking a significant advancement by integrating all core functionalities of OPC Classic—such as , address space browsing, subscriptions, events, and methods—into a unified, extensible . Key innovations included XML-based modeling for defining complex structures and object-oriented representations, TCP encoding for efficient real-time communication, and optional Web Services support using and for broader IT compatibility. These features ensured firewall-friendly protocols and scalability, allowing OPC UA to operate on resource-constrained devices like programmable logic controllers (PLCs) alongside high-end servers. Major milestones followed the 2008 release, including the publication of UA Part 1 (Overview and Modeling) in 2008, which outlined the foundational concepts and multi-layered architecture. The first complete (SDK) was released in July 2009 using C/C++ and .NET frameworks. In 2011, the OPC Foundation launched its certification program to ensure compliance and interoperability. OPC UA was subsequently integrated into the (IEC) standards as IEC 62541, formalizing its role in global industrial communication protocols starting around 2010. Version 1.03, released in 2014, included enhancements such as improved features including better handling and role-based controls. This version addressed demands for distribution in large-scale networks, building on earlier binary and Web Services encodings to support deterministic messaging. Industry collaborations accelerated adoption, with OPC UA aligning with ISA-95 standards through companion specifications for enterprise-control by 2014, enabling standardized modeling of processes and assets. This alignment positioned OPC UA as a cornerstone for Industry 4.0 initiatives, promoting in environments. Subsequent developments included the release of OPC UA Part 14 in 2018, introducing publish-subscribe (PubSub) capabilities for efficient communication in distributed systems as part of version 1.04. Further advancements encompassed support for OPC UA over in 2020, the initiation of Field eXchange (FX) specifications in 2021 for field-level communications, and integrations with (TSN). As of 2025, OPC UA has evolved to version 1.05, incorporating amendments for enhanced cloud connectivity and .

OPC Foundation

Establishment and Role

The OPC Foundation was incorporated on April 22, 1996, in , , and granted non-profit status on January 13, 1998, by a group of leading industrial automation suppliers to develop and maintain open standards for interoperability between control systems and environments. Initially focused on creating the OLE for Process Control (OPC) specifications using COM/DCOM technology, the organization was formed to address the challenges of proprietary systems hindering data exchange in manufacturing and process automation. The core role of the centers on creating, publishing, and updating OPC specifications to ensure secure and reliable data exchange across diverse platforms and devices. It also provides certification testing through authorized labs to verify and of products implementing these standards, with facilities established in locations such as the , , and since the mid-2000s. To support its global operations, the OPC Foundation maintains its headquarters in , , alongside regional offices including the European office in Verl, , and the Japanese office in , facilitating worldwide coordination. It operates specialized working groups that develop specifications, test , and address emerging needs in industrial automation, drawing participation from members across multiple continents. The Foundation advances education and adoption through initiatives like the OPC UAcademic program, launched in 2021, which supplies universities with OPC UA training materials and resources for developers and end-users. It also hosts webinars on technology and market topics, alongside certification training to build expertise in implementing OPC standards. Furthermore, the organization collaborates with international bodies such as the (IEC) to standardize OPC UA under the IEC 62541 series, ensuring global recognition and alignment with broader industrial norms.

Membership and Governance

The OPC Foundation's membership model is structured into several tiers to accommodate diverse participants in the industrial automation ecosystem. Corporate members, who are primarily OPC technology providers offering compliant products, form the core of the voting membership and pay dues scaled by annual sales revenue, ranging from $3,000 for smaller firms to over $18,000 for large enterprises. End-User members, representing consumers of OPC-based solutions, pay a flat fee of $1,800 annually and enjoy full voting rights alongside Corporate members. Non-Voting members, such as universities, research institutions, and government entities, contribute $900 yearly but lack voting privileges. Additionally, the Foundation introduced affiliate partner programs effective January 1, 2025, allowing subsidiaries or related entities of existing members to join at reduced or tied rates, with Startup members (companies under five years old and under $2 million in revenue) qualifying for a $500 entry fee to foster innovation. Governance is overseen by a , comprising up to 15 representatives from member organizations, elected annually by voting members (Corporate and End-User categories) to ensure democratic representation. The Board sets strategic direction, while technical development occurs through specialized working groups and the Technical Control Board (TCB), which supervises specification creation, open-source tools, and compliance processes. These bodies operate under a consensus-based framework, where proposals for new or updated specifications require broad agreement among participants before advancement, promoting collaborative and inclusive progress. Membership benefits emphasize practical support for and , including full access to draft and final OPC specifications, tools, and interoperability testing resources. Members receive up to 50% discounts on lab testing, enabling cost-effective validation of products against standards. Networking opportunities abound through events like the annual OPC Day, where participants engage in workshops, demonstrations, and discussions to advance OPC technologies. The Foundation maintains transparency in decision processes via regular audits of activities and public reporting on specification releases. By November 2025, the had grown to over 1,010 members worldwide, reflecting its expanding influence in industrial automation, IT, and sectors. This includes prominent vendors such as and , alongside recent additions of tech giants like and Google Cloud, which joined as Corporate members in the early 2020s to integrate OPC UA with cloud platforms.

OPC Standards

OPC Classic Specifications

The OPC Classic specifications encompass a set of standards developed for industrial automation data exchange, primarily focusing on and historical process data within Windows environments. These specifications include (DA), which enables clients to read and write tag values, along with associated timestamps and quality indicators; OPC Alarms and Events (AE) for notifying clients of alarm conditions and event states; OPC Historical Data Access (HDA) for querying archived process data; and OPC Data eXchange (DX) for aggregating and redistributing data from multiple sources in scenarios. OPC DA, in its version 3.0 released in 2003, forms the foundational specification for synchronous and asynchronous access to current process data through a client-server interface, supporting operations like browsing server namespaces and subscribing to data changes via groups of items. OPC AE version 1.10, finalized in 2002, extends this by defining mechanisms for servers to monitor process areas and deliver categorized alarms and events to clients, including support for acknowledgments and historical event queries. Complementing these, OPC HDA version 1.20 from 2003 provides standardized methods for retrieving time-series historical data from server databases, incorporating aggregate functions such as averages and minima over specified intervals. OPC DX version 1.0, also released in 2003, targets batch-oriented environments by allowing servers to collect and forward data from disparate OPC DA sources, facilitating recipe management and device coordination without direct client intervention. At its core, the architecture of OPC Classic relies on a client-server model implemented via Microsoft's (DCOM), where clients poll or subscribe to server-provided data items through grouped subscriptions to optimize update rates and reduce network overhead. This setup uses interface definitions in C++ with an wrapper for broader language support, enabling remote procedure calls over DCOM for . The data model in OPC Classic centers on a simple, tag-based approach, where process variables are represented as addressable items with basic attributes like value, , and , lacking advanced semantic modeling or object-oriented hierarchies. Servers expose namespaces of these items for client browsing, but without inherent support for complex relationships or beyond item properties. Despite their widespread adoption, OPC Classic specifications have notable limitations, including exclusive on Microsoft Windows platforms due to DCOM requirements, which restricts deployment in heterogeneous or non-Windows environments. DCOM's reliance on open ports also poses challenges with firewalls and , often necessitating custom configurations for remote access. Security is limited to basic Windows mechanisms, without built-in or fine-grained for data access. Although still prevalent in legacy industrial systems for their proven reliability in Windows-based setups, OPC Classic specifications are considered deprecated in favor of migration to , which addresses these platform and security constraints.

OPC Unified Architecture

OPC Unified Architecture (OPC UA), standardized as IEC 62541, represents the modern evolution of open industrial communication protocols, providing a platform-independent for secure and reliable data exchange across diverse systems. As the successor to earlier OPC specifications, it enables in industrial automation by modeling complex information structures beyond simple data points. The standard comprises over 15 parts, each addressing specific aspects of the architecture; key foundational elements include Part 1, which outlines core concepts and overview; Part 3, defining the model; Part 4, specifying services; Part 6, detailing mappings for protocol implementation; and Part 14, covering the publish-subscribe (PubSub) mechanism. At the heart of OPC UA lies its object-oriented information model, which organizes data into a hierarchical address space composed of nodes representing variables (for data values), objects (for instances), methods (for executable functions), and types (such as object types, variable types, data types, reference types, and views). Nodes are interconnected via references, which define relationships like hierarchical containment or semantic associations, while namespaces provide unique identifiers and scoping to avoid conflicts across different vendors or applications. This model supports semantic descriptions, allowing for rich metadata and extensible type definitions that facilitate discovery, browsing, and interpretation of industrial data without proprietary formats. OPC UA defines a set of abstract services for client-server interactions, enabling operations such as Read and Write for accessing and modifying values; and for real-time event notifications and data changes; Browse for navigating the ; and Call for invoking methods on objects. These services operate over multiple transport mappings outlined in Part 6, including UA TCP for efficient binary-encoded communication over TCP/IP, UA Secure Conversation leveraging for SOAP-based web services, and emerging PubSub options over for scenarios or for broker-mediated messaging in distributed networks. The specification has evolved through version releases to address growing needs in industrial IoT and . Version 1.04, released in 2017, enhanced modeling capabilities with improved support for complex data types, dictionaries, and finite state machines to better represent advanced . Version 1.05, introduced in 2022 with subsequent updates like 1.05.06, added encoding for lightweight payloads, support for persistent connections, and RESTful interfaces via OpenAPI definitions, broadening accessibility for web and cloud integrations.

Companion Specifications

Companion Specifications extend the core OPC UA framework by defining domain-specific information models, pre-defined node sets, and conformance profiles tailored to particular industries or functions, enabling seamless without requiring custom implementations. These specifications build on the UA address space model to standardize data exchange in vertical sectors such as automotive manufacturing, pharmaceuticals, and , reducing integration efforts and promoting plug-and-play compatibility among devices and systems. They differ from core OPC UA parts (e.g., Parts 1-26 defining foundational elements like services, mappings, and PubSub in Part 14) by providing sector-specific extensions. Developed collaboratively by industry working groups and standards organizations under the , they ensure that specialized requirements—like equipment commands or sector-specific data semantics—are addressed through certified, vendor-neutral extensions. Released primarily after 2015 in alignment with the maturation of , Companion Specifications have proliferated through dedicated working groups, with the facilitating certification to verify compliance and interoperability. By 2025, over 50 such specifications have been developed and released, covering diverse applications from mappings to industry-specific analytics, with ongoing efforts in organizations like VDMA involving more than 600 companies across sectors. This growth reflects the modular nature of , allowing rapid adaptation to emerging needs while maintaining with core standards. Notable examples include the OPC UA for Machinery specification, which defines standardized nodes for machine status monitoring, operational commands, and equipment performance data, serving as a foundational model for subsectors like machine tools and to enable and diagnostics. The OPC UA companion specification for maps IEC 61850 data models—used in substation —to OPC UA constructs, facilitating the exchange of electrical device information such as measurements and signals within broader industrial environments. Similarly, the specification (Part 20) outlines methods for secure, standardized file operations, including upload, download, and directory management, integrated into domain models like subsea production systems for handling configuration files and logs. The PubSub mechanism, detailed in OPC UA Part 14, supports messaging protocols for efficient, distribution to field-level devices, using mechanisms like or to handle high-volume data without session-based overhead. In the realm of analytics and , companion specifications provide sets for data processing pipelines and model integration, allowing standardized access to processed datasets, results, and parameters in industrial applications like . These examples underscore how Companion Specifications certify through OPC Foundation testing, ensuring robust deployment across certified devices and software.

Technical Architecture

Core Components

The core components of Open Platform Communications (OPC) architecture, particularly in (), form the foundational elements that enable secure, platform-independent data exchange between applications. These components include clients and servers for interaction, an for data representation, sessions and subscriptions for managing connections and updates, discovery mechanisms for locating endpoints, and conformance profiles for defining implementation subsets. This structure supports across diverse industrial systems while allowing from devices to servers. In the OPC UA client-server model, clients initiate requests to or invoke operations, while servers expose their data models and provide responses to these requests. Clients and servers can coexist within the same application, enabling flexible system designs where multiple concurrent interactions occur. Servers maintain the state of client connections, ensuring reliable delivery. The serves as a hierarchical of objects and data within a , composed of nodes connected by references to model real-world entities such as variables, methods, and events. Nodes are typed by classes like VariableNode, which holds data values with associated such as data types and access rights, allowing clients to browse and query the dynamically. This model integrates information from various domains, supporting views that subset the for specific client needs. Sessions establish secure, stateful connections between clients and servers, layered atop secure channels for authenticated and encrypted communication, with each session tied to a specific identity. Subscriptions enable event-driven data access by allowing clients to items in the , where servers sample values at configurable rates and publish notifications for changes or events, reducing polling overhead. Monitored items within subscriptions apply filters to optimize updates, supporting efficient . Discovery mechanisms facilitate endpoint location without prior configuration, using services like FindServers to query known servers and GetEndpoints to retrieve connection details such as security policies. Local Discovery Servers (LDS) register and announce servers on a network, while global options extend this to wider scopes, ensuring clients can dynamically connect to available OPC UA applications. Conformance profiles define standardized subsets of OPC UA functionality, aggregating conformance units—testable feature groups like service sets or security modes—to certify application capabilities. For instance, the Micro Embedded Device Server Profile targets resource-constrained devices, building on basic server features with limited support for sessions and subscriptions to enable lightweight implementations. These profiles ensure by specifying mandatory behaviors, such as minimum connection counts or supported transports.

Communication Mechanisms

OPC UA employs a request-response model for synchronous communication, where clients send requests to servers for operations such as reading or writing data, and servers respond accordingly. This model is facilitated through services like Read and Write, transmitted over the UA TCP protocol, ensuring reliable point-to-point interactions with immediate feedback on success or failure. In contrast, the publish-subscribe mechanism supports asynchronous notifications, allowing clients to create subscriptions on servers for monitored items, which trigger data change notifications only when values update based on configurable parameters like sampling intervals or deadbands. This pattern, built on core components like subscriptions, reduces network traffic by avoiding constant polling and enables efficient real-time data delivery in client-server scenarios. OPC UA PubSub extends this further with a one-to-many approach, publishers and subscribers without requiring persistent sessions, ideal for scalable distributed systems. Publishers send messages to a broker, such as , which then distributes them to multiple subscribers, supporting high-throughput scenarios like field-level communications in industrial environments. Data exchange in OPC UA utilizes multiple encodings to balance efficiency and interoperability. The binary encoding prioritizes compactness and speed, using primitive types without redundant metadata for low-latency industrial applications, while XML and encodings provide human-readable formats with explicit type information, facilitating integration with web services and systems. For OPC Classic, tunneling over HTTP addresses DCOM-related challenges in cross-network communications by encapsulating data in HTTP tunnels, enabling secure remote access without extensive configurations or DCOM setup complexities.

Security and Interoperability

Security Model

The Open Platform Communications Unified Architecture (OPC UA) incorporates a comprehensive model designed to protect systems from threats such as unauthorized access, data tampering, and . This model addresses key objectives including , , , , and auditability through a layered approach that secures both applications and users. Application authentication in OPC UA relies on X.509 v3 digital to uniquely identify and verify client and server instances before establishing any communication. Each application maintains a private key paired with its , which is used to authenticate during creation, ensuring that only trusted entities can connect. This certificate-based mechanism supports (PKI) for scalable trust management across distributed systems. Once applications are authenticated, user identity is handled via multiple token types to enable flexible : anonymous for unauthenticated sessions, username/password for basic credential validation, X.509 certificates for strong user-level identity, and issued resembling for federated or delegated . These are presented during session activation, allowing servers to enforce role-based controls based on user privileges. To protect , OPC UA secure channels employ symmetric with AES-128 or AES-256 for message , combined with HMAC-SHA256 or similar algorithms for signing to ensure integrity and prevent replay attacks. These mechanisms are negotiated during channel establishment, with optional support for asymmetric using during the initial . Auditability is integrated through mandatory event logging of security-relevant actions, including attempts, access denials, and session terminations, which can be configured to record timestamps, user identities, and outcomes for and forensic analysis. Servers and clients may subscribe to audit events via the subscription model to monitor and respond to potential incidents in . Endpoint security policies define the supported cryptographic algorithms and modes (e.g., , SignAndEncrypt) available for , categorized into levels like Basic256Sha256 or PubSubSecurityApplication to balance security and performance. Clients select compatible policies during endpoint binding, ensuring mutual agreement on protection levels without compromising . The security model evolved significantly with OPC UA 1.02 in 2012, which formalized PKI support through enhanced certificate handling and introduced stronger encryption options like AES-256 to address emerging threats. Recent developments in OPC UA 1.05 (as of October 2025) include a dedicated section on zero-trust environments, emphasizing continuous verification, PKI scalability for hybrid and cloud deployments, and alignments with modern cybersecurity principles. Ongoing enhancements address vulnerabilities, such as those disclosed in 2024 (e.g., CVE-2024-45526) and 2025 formal analyses, with patches and recommendations from the , including the 2024 OPC UA Security Summit focused on collaborative threat mitigation.

Ensuring Interoperability

The OPC Foundation's certification program ensures by subjecting OPC-based products to rigorous stack and in dedicated labs, verifying conformance to specified profiles for , robustness, and seamless operation across diverse implementations. This process involves automated and manual evaluations to identify and resolve potential incompatibilities before products reach the market, thereby minimizing integration risks in multi-vendor environments. Testing covers core functionalities such as data access, alarms, events, and historical data, with a focus on OPC UA specifications to guarantee platform-independent communication. Compliance with the OPC UA Information Model is mandated through the required adoption of standard node sets, which define the structure, semantics, and relationships of data in the using XML-based files for precise exchange between clients and servers. These node sets include predefined types, instances, and namespaces that form the for domain-specific models, ensuring that all certified implementations share a common semantic framework without proprietary deviations. Reference implementations provided by the further support developers in aligning their products with these standards, promoting consistent behavior across devices and systems. Key tools for validating interoperability include the OPC UA Compliance Testing Tool (CTT), an automated suite that tests client and server products against the full spectrum of OPC UA specification requirements, generating detailed reports on conformance and highlighting areas for correction. Complementing this, the OPC Foundation organizes regular Interoperability Workshops, where member vendors collaboratively test products from multiple suppliers in real-time scenarios to debug issues and confirm cross-vendor compatibility. These workshops facilitate direct interaction and knowledge sharing, accelerating the resolution of interoperability challenges. OPC UA specifications incorporate strict rules to maintain across versions, prohibiting changes that would break existing clients or servers while allowing controlled extensions through mechanisms like optional properties and notices for obsolete features. For instance, updates to information models must preserve mandatory components and reference existing nodes without altering their semantics, ensuring that newer implementations can interact with legacy ones seamlessly. These rules are detailed in official modeling guidelines, emphasizing semantic stability to support long-term deployments in industrial settings. The efficacy of these measures is evidenced by global adoption metrics, with more than 52 million applications in use worldwide as of 2025, a figure verified through the certification program's tracking of compliant products from more than 5,200 suppliers. This widespread deployment underscores the program's role in fostering reliable, scalable interoperability across industrial automation ecosystems.

Adoption and Applications

Industry Sectors

Open Platform Communications (OPC) has found extensive application across various industry sectors, enabling standardized data exchange and interoperability between diverse systems and devices. In manufacturing, OPC is integrated into programmable logic controllers (PLCs) and supervisory control and data acquisition (SCADA) systems to facilitate real-time monitoring and control of production lines, particularly in high-precision environments like automotive assembly where it supports seamless communication between robotic systems and enterprise software. In process industries such as oil and gas, and chemicals, OPC Historical Data Access (HDA) plays a key role in monitoring and archiving operational data for process optimization and compliance, exemplified by its use in control systems to track variables like and over time. This adaptation allows for efficient historical analysis without disrupting ongoing operations. The energy sector leverages (UA) for power generation and applications, where it maps to the standard to enable secure, platform-independent data exchange between substations, sources, and grid management systems. This integration supports real-time visibility into grid stability and energy distribution. Building automation employs OPC UA companion specifications, such as the mapping to BACnet, to integrate heating, ventilation, and air conditioning (HVAC) systems with access control mechanisms, allowing centralized management of environmental controls and security in commercial facilities. Emerging sectors are increasingly adopting OPC UA for specialized applications, including healthcare devices where it ensures secure data transmission from medical equipment like cryostorage systems to patient monitoring platforms. In agriculture, OPC UA facilitates IoT-enabled precision farming by connecting sensors, irrigation controllers, and machinery for data-driven crop management. Additionally, the semiconductor industry is experiencing growth in OPC UA deployment as of 2025, with ongoing development of domain-specific companion specifications to standardize equipment interfaces in fabrication processes. These adaptations highlight OPC's role in reducing integration costs across sectors by promoting vendor-neutral connectivity.

Case Studies and Benefits

One notable implementation of OPC UA involves ' platform, which leverages the standard for seamless cloud-edge data exchange in settings. At the Electronics Works plant, operational data such as , , and from PLCs is transmitted via OPC UA to a -hosted , enabling real-time monitoring, , and process optimization. This approach has streamlined , reducing the time required for connecting systems to by facilitating plug-and-play across devices. Another key example is 's adoption of OPC UA within its Open Process Automation (OPA) framework for operations. Following the selection of OPC UA as the core communication standard by the Open Process Automation Forum in 2018, ExxonMobil prototyped an OPA system in a hydrocarbon , marking a migration from legacy control systems to enhance data reliability and system . By 2025, this evolved into a full-scale deployment with over 100 controllers and 1,000 I/O points at the ExxonMobil Resins Finishing Plant—a facility akin to environments—resulting in improved operational reliability and reduced downtime through standardized, secure data flows. OPC UA delivers tangible benefits, including cost savings in middleware by minimizing the need for custom integration layers and enabling reuse of existing components, which can reduce engineering expenses. Its scalability supports Industrial Internet of Things (IIoT) deployments by handling large-scale data volumes across distributed systems without performance degradation. Additionally, the standard's semantic data modeling enhances analytics capabilities, allowing contextual interpretation of industrial data for advanced insights like predictive maintenance. By 2025, OPC UA has achieved significant adoption, with the related OPC server software market expanding to $15.87 billion, reflecting its integration into a majority of new projects for standardized communication. The protocol's vendor-neutral ecosystems further drive (ROI) by promoting multi-vendor , lowering long-term ownership costs through reduced and simplified maintenance. Legacy system challenges are effectively addressed via OPC UA gateways, which bridge older protocols like OPC Classic to modern UA environments without full replacements, ensuring gradual migrations while maintaining .

Future Developments

Ongoing Enhancements

In 2022, the (OPC UA) 1.05 specification was released, introducing encoding support to facilitate efficient data serialization and APIs through OpenAPI definitions, enabling seamless integration with web and cloud environments. This enhancement expanded OPC UA's applicability beyond traditional industrial networks, allowing developers to leverage modern web technologies for accessing industrial data without requiring full OPC UA protocol stacks. Building on these foundations, the 2023 updates to OPC UA PubSub introduced support for and transports, optimizing for low-latency, broker-based messaging suitable for scenarios. These features enable scalable, one-to-many data distribution in distributed systems, such as those involving devices and analytics at the network edge, while maintaining OPC UA's semantic . In 2025, the expanded its Board of Directors to include (AWS), Google Cloud, and , underscoring the protocol's role in bridging (OT) with (IT) convergence. This strategic inclusion of cloud providers aims to accelerate OPC UA adoption in hybrid cloud-edge architectures, fostering standardized data exchange across IT/OT boundaries. In late 2024, the OPC Foundation established a working group for OPC UA for Battery Systems to develop standardized data models for interoperability in battery production and management processes, including cell manufacturing and lifecycle tracking. This initiative addresses key challenges in the electric vehicle and renewable energy sectors by enabling secure, real-time data sharing among heterogeneous equipment, with a proof-of-concept demonstrated in April 2024. Ongoing efforts continue to enhance OPC UA support for s, leveraging its extensible information modeling to provide unified frameworks for virtual representations of physical assets with rich semantic information. This supports advanced simulations and by integrating OPC UA's object-oriented concepts with digital twin platforms, enhancing cross-vendor compatibility in Industry 4.0 applications. In November 2025, the released the OPC UA Companion Specification for Identification and Locating (OPC 30091), creating a unified for technologies such as RFID, UWB, RTLS, and . This specification enables interoperable location tracking and supports physical applications in industrial environments, facilitating precise and automation. At Hannover Messe 2025, the showcased demonstrations of OPC UA integrated with networks, highlighting real-time, low-latency communications for industrial applications such as and . These live exhibits, including OPC UA PubSub over and cloud reference architectures, illustrated practical implementations of the protocol's enhancements in high-speed, deterministic environments.

Integration with Emerging Technologies

Open Platform Communications Unified Architecture (OPC UA) is increasingly integrated with Industrial Internet of Things (IIoT) frameworks to support Industry 4.0 initiatives, particularly through its Publish-Subscribe (PubSub) mechanism, which facilitates efficient communication among large-scale device swarms in smart factories. OPC UA PubSub enables exchange in distributed environments, allowing thousands of sensors and actuators to operate seamlessly without traditional client-server bottlenecks, thereby enhancing and in automated lines. This approach supports massive in IIoT ecosystems by leveraging broker-based messaging for decoupled publisher-subscriber interactions, reducing latency and bandwidth usage in high-density factory settings. Furthermore, OPC UA's semantic information modeling ensures that data from diverse devices remains interoperable, enabling and orchestration in environments. In and paradigms, OPC UA operates over (TSN) to deliver deterministic, real-time performance essential for mission-critical applications. TSN extensions to Ethernet provide guaranteed and , allowing OPC UA to transmit control data with microsecond precision across hybrid cloud-edge infrastructures, which is vital for coordinating distributed automation systems. This integration bridges (OT) with (IT), enabling edge devices to process OPC UA data locally while syncing with resources for , thus minimizing delays in time-sensitive scenarios like robotic assembly. By combining OPC UA's secure tunneling with TSN's , systems achieve sub-millisecond determinism, supporting scalable deployments in edge-cloud architectures without proprietary hardware. OPC UA's semantic models are pivotal in enabling (AI) and (ML) applications, particularly on continuous data streams from . These models provide structured, context-rich representations of data, allowing AI algorithms to interpret and federate learning across decentralized nodes without centralizing sensitive information, which preserves in multi-vendor environments. For instance, OPC UA companion specifications define ontologies that map process variables to ML inputs, facilitating distributed on streams for and optimization in production lines. This capability extends to cognitive production systems, where from OPC UA enables cross-domain federated models to improve accuracy in while complying with regulations. To address sustainability goals, OPC UA specifications incorporate standardized models for , promoting efficient resource use in green manufacturing. The OPC UA for Energy Management companion specification defines an that captures power consumption, efficiency metrics, and optimization signals across devices, enabling dynamic load balancing to reduce waste in industrial operations. This framework supports real-time monitoring and control of energy flows, allowing factories to integrate renewable sources and adapt to demand fluctuations for lower carbon footprints. In energy-flexible systems, OPC UA interfaces facilitate predictive algorithms that adjust machine operations based on electricity pricing and environmental data, advancing sustainable practices without disrupting production. Looking ahead, the OPC Foundation is advancing its to incorporate and -compatible simulations, ensuring long-term resilience and innovation through 2030. Hybrid OPC UA protocols are being developed to integrate post-quantum algorithms, such as lattice-based signatures, into existing security handshakes, protecting against quantum threats in IIoT communications. Concurrently, OPC UA extensions enable immersive simulations by streaming semantic data to virtual environments, supporting visualizations for training and in virtual factories. These evolutions align with the Foundation's vision for secure, interoperable ecosystems, as outlined in ongoing enhancements to the OPC UA standard.

References

  1. [1]
    What is OPC? - OPC Foundation
    OPC is an interoperability standard for secure data exchange, now known as Open Platform Communications, and is platform independent.
  2. [2]
    What is OPC? | Open Platform Communications - PTC
    OPC is an industrial communication standard that enables data exchange between multi-vendor devices and control applications without proprietary restrictions.
  3. [3]
    What is Open Platform Communications (OPC)? - TechTarget
    Aug 21, 2024 · Open Platform Communications (OPC) is an interoperability standard for secure data exchange in industrial automation and other areas.
  4. [4]
    Classic - OPC Foundation
    In 2008, the OPC Foundation released OPC Unified Architecture (OPC UA), a platform independent service-oriented architecture that integrates all the ...<|separator|>
  5. [5]
    Unified Architecture - Landingpage - OPC Foundation
    The multi-layered architecture of OPC UA provides a “future proof” framework. Innovative technologies and methodologies such as new transport protocols, ...OPC UA Roadmap · UA Companion Specifications · Resources
  6. [6]
    What is OPC Unified Architecture (OPC UA)? - PTC
    Just like OPC Classic, OPC UA offers helpful features to speed integrations like OPC server discovery, address space browsing, and data change subscriptions.
  7. [7]
    What is OPC UA? - S2OPC
    Key features of OPC UA. International standard (IEC 62541); Open and vendor-neutral: independent of manufacturers, programming languages, and operating ...<|control11|><|separator|>
  8. [8]
    Connecting Industry 4.0 with OPC UA - NXP Semiconductors
    Apr 30, 2024 · OPC UA is an information architecture built to be extensible, open and secure for Industry 4.0 applications. It enables engineers to design ...
  9. [9]
    There Is No Industrie 4.0 without OPC UA
    OPC UA is the recommended communication layer for Industrie 4.0, providing industrial interoperability and is the de facto standard for the automation market.
  10. [10]
    OPC UA – an overview over the central Industry 4.0 standard - KEBA
    Feb 20, 2023 · OPC UA is a platform-independent, service-oriented architecture for data exchange, enabling networking of devices and services, and is a ...
  11. [11]
    Industry experts offer OPC UA solutions update
    Jan 23, 2025 · OPC UA includes features like authentication, authorization, encryption, and data integrity checks.”Opc Ua Security Enhancements · Opc Ua And Mqtt Sparkplug · Impact Of Opc Ua Fx And Tsn
  12. [12]
    Tightening Systems - 4.3 Introduction to OPC Unified Architecture
    OPC UA provides a robust and reliable communication infrastructure having mechanisms for handling lost messages, failover, heartbeat, etc. With its binary ...Missing: features | Show results with:features
  13. [13]
    [PDF] OPC UA for Analyzer Devices (ADI) is released as a companion ...
    The OPC Foundation begins converting its existing specification to web services. 1999. Classic OPC Alarms & Events (OPC AE) specification is released. 2001.
  14. [14]
    History of OPC | OPCconnect.com
    The need for OPC is probably best traced back to the introduction of Windows 3.0 in 1990. With Windows 3 it became possible, on an inexpensive, mainstream ...
  15. [15]
    OPC UA | OPCconnect.com
    The first parts of the specification were released August 2006, with a full phase I release in February 2009. OPC Foundation has developed UA in recognition of ...
  16. [16]
    [PDF] OPC Unified Architecture
    OPC Unified Architecture (OPC UA) is the informa- tion exchange standard for secure, reliable, manu- facturer- and platform-independent industrial com-.
  17. [17]
    OPC Foundation Announces OPC Test and Certification Program
    Jan 11, 2011 · January 11, 2011 ‚Äì The OPC Foundation introduced the OPC Unified Architecture (OPC UA) Test and Certification Program for products from ...
  18. [18]
    https://www.opcconnect.com/ua.php
  19. [19]
    [PDF] News on OPC UA platform, PubSub and MQTT
    2015. 1.03. 2018. 1.04. 2021. 1.05.0. Errata. Errata. Errata. Amendements. ▻. OPC UA (OPC 10000) Specification Release Cycle was three years. ▻. Errata handled ...<|separator|>
  20. [20]
    OPC UA is Enhanced for Publish-Subscribe (Pub/Sub)
    OPC UA is Enhanced for Publish-Subscribe (Pub/Sub). 11/20/2015 Press Releases. The enhanced communication mechanism in OPC UA is the foundation for planned ...Missing: 1.03 | Show results with:1.03
  21. [21]
    [PDF] Current Standards Landscape for Smart Manufacturing Systems
    Some of these customizations are contained in companion standards for different application areas—for example OPC UA for ISA 95, OPC UA for Field Device ...<|control11|><|separator|>
  22. [22]
    [PDF] OPC Unified Architecture
    OPC Unified Architecture (OPC UA) is the data ex- change standard for safe, reliable, manufacturer- and platform-independent industrial communication.
  23. [23]
    Imprint - OPC Foundation
    The OPC Foundation is an Arizona Not-for-Profit Corporation incorporated in April 1996 and granted non-profit status by the US Internal Revenue Service IRS 501 ...
  24. [24]
    Contact Us - OPC Foundation
    OPC Foundation Headquarters and Administrative Office, OPC Foundation, 16101 N. 82nd Street, Suite 3B, Scottsdale, AZ 85260-1868 USA, Phone: 480 483-6644.
  25. [25]
    OPC-F Working Groups
    The OPC Foundation working groups (OPC-F WGs) are essential for the development of industry-leading specifications, technologies, certification and processes.
  26. [26]
    OPC UAcademic
    The aim of the OPC Foundation's “OPC UAcademics” program is to support Universities around the world by providing Information about OPC UA and related ...
  27. [27]
    The OPC Foundation launches its OPC UAcademics program to ...
    Jun 8, 2021 · The OPC Foundation launches its OPC UAcademics program to supplement OPC UA training in post-secondary institutes. 06/08/2021. New OPC UA ...
  28. [28]
    Webinars - OPC Foundation
    The OPC Foundation is hosting a series of webinars to share information about different topics including technology, markets or collaboration.Missing: training programs
  29. [29]
    IEC 62541-5:2020
    Jul 10, 2020 · IEC 62541-5:2020 defines the Information Model of the OPC Unified Architecture. The Information Model describes standardized Nodes of a Server's AddressSpace.
  30. [30]
    Benefits - Membership - OPC Foundation
    Membership provides access to all the specifications and tools required to develop your product, it provides the tools for certification of your product.
  31. [31]
    Organization - OPC Foundation
    The OPC Foundation Organization includes: Board of Directors, Christoph Berlin, Microsoft, Dr. Jan Bezdicek – Rockwell Automation, Steve Blackwell – Amazon Web ...
  32. [32]
    Overview & Benefits - OPC Foundation
    Corporate Members: US$950 per day; Logo-members: US$1900 per day. Testing typically varies between 5 to 10 days for an OPC UA Client or between 3 to 7 days ...
  33. [33]
    OPC Day (virtual) International 2025 - OPC Foundation
    The OPC Foundation will host the digital event from May 19-23, 2025 with 3 hours per day starting at 1:00pm – 4:00pm CEST.Missing: access discounts
  34. [34]
    OPC UA connects assets to International Data Spaces
    Mar 26, 2025 · The Foundation supports over 1010 members from around the world in industrial automation, IT, IoT, IIoT, M2M, Industry 4.0, building ...
  35. [35]
    Classic - OPC Foundation
    The original OPC Specification and its evolution from versions 1, 2.x, and 3.0, covering: The concepts of OPC Client/Server technology and data definition ...
  36. [36]
    Classic - OPC Foundation
    ### Summary of OPC AE Specification
  37. [37]
    Classic - OPC Foundation
    ### OPC HDA Specification Summary
  38. [38]
    Classic - OPC Foundation
    ### Summary of OPC Batch Specification
  39. [39]
    [PDF] OPC Data Access Custom Interface Specification 3.0 - Advosol
    Mar 4, 2003 · A revised automation interface may be provided with release 3.0 of the OPC specification. This is shown below. C++ Application. VB ...
  40. [40]
    Opc Data Exchange Specification Version 1.0 [PDF] - VDOC.PUB
    E-Book Content. OPC Data eXchange Specification Version 1.0 Release March 5, 2003 ... DX server: Page 81 of 122. OPC Data eXchange Specification Version: 1.0
  41. [41]
    Unified Architecture - OPC Foundation
    OPC UA is a platform-independent, service-oriented architecture specification that integrates all functionality from the existing OPC Classic specifications.
  42. [42]
    OPC UA Online Reference - Released Specifications
    OPC 10000-1: UA Part 1: Overview and Concepts · OPC 10000-2: UA Part 2: Security · OPC 10000-3: UA Part 3: Address Space Model · OPC 10000-4: UA Part 4: Services.OPC 10000-3 UA Part 3 · OPC 10000-4 UA Part 4 · UA Part 23 · 1.05.06Missing: publicly | Show results with:publicly
  43. [43]
    IEC 62541-14:2020
    Jul 8, 2020 · IEC 62541-14:2020 defines the OPC Unified Architecture (OPC UA) PubSub communication model. It defines an OPC UA publish subscribe pattern.
  44. [44]
    https://vdoc.pub/documents/opc-data-exchange-specification-version-10-15tufthm2rc0
  45. [45]
    OPC UA and OpenAPI
    The 1.05.04 version of the specification introduced the OpenAPI definitions for OPC UA. OpenAPI is a specification for defining and documenting RESTful APIs.
  46. [46]
    UA Companion Specifications - OPC Foundation
    OPC UA specifies a number of base information models (DataAccess – DA, Alarms&Conditions – AC, and more) that define commonly used objects.Missing: publicly | Show results with:publicly
  47. [47]
    OPC UA Companion Specifications (OPC UA CS) | OPCconnect.com
    Companion Specifications provide a common method for standards bodies and specialized industry groups to collaborate on specific information models.
  48. [48]
    Working Group Machinery Building Blocks - OPC UA Profiles
    Currently, around 40 working groups in the VDMA are working on OPC UA Companion Specifications, and more than 600 companies in the industry are involved in the ...
  49. [49]
    OPC UA Companion Spec Generation with EMF
    More than 40 Companion Specifications are currently in development or already released. In this paper the current approaches to generate an OPC UA information ...
  50. [50]
    OPC UA for Machinery
    Currently, around 40 working groups in the VDMA are working on OPC UA Companion Specifications, and more than 600 companies in the industry are involved in the ...
  51. [51]
    OPC 40501 UA for Machine Tools - Umati
    The Machine Tool companion specification provides the harmonized uses cases and information defined by OPC UA for Machinery, especially the Machine States.
  52. [52]
    IEC61850 companion specification for electrical substation ...
    This companion specification document describes how IEC 61850 data can exchanged using OPC UA data modelling and services.
  53. [53]
    OPC Foundation Announces IEC 61850 Companion Spec Release
    The OPC UA for IEC61850 Companion Specification was created to support the integration of electrical aspects into an industrial plant. It defines an OPC UA ...
  54. [54]
    MDIS OPC UA Companion Specification - D.3 Signature File Transfer
    A Server that supports transferring the valve signature via OPC UA shall expose a FileObject as part of the Valve Object Instance via the HasSignature ...
  55. [55]
    UA Part 14: PubSub - OPC UA Online Reference
    OPC 10000-14: UA Part 14: PubSub. Released 1.05.06. 2025-10-31. This document is subject to the license terms described here. The general OPC Foundation ...
  56. [56]
    OPC UA PubSub - OPC Labs
    OPC UA PubSub. QuickOPC gives you access to OPC UA functionality described in Part 14 of the OPC Unified Architecture Specification, also known as PubSub.
  57. [57]
    [PDF] Use Cases for a CIP Companion Specification for OPC UA | ODVA
    Mar 4, 2020 · Data Scientists harvest large datasets from plant floor operations and use statistical analysis and artificial intelligence tools to identify.
  58. [58]
    UA Part 1: Overview and Concepts - 5 Systems concepts
    The OPC UA systems architecture models Clients and Servers as interacting partners. Each system may contain multiple Clients and Servers.Missing: sessions | Show results with:sessions
  59. [59]
    https://reference.opcfoundation.org/Core/Part20/v105/
  60. [60]
    https://reference.opcfoundation.org/MDIS/v130/docs/D.3
  61. [61]
    UA Part 1: Overview and Concepts - 4 Overview
    ### Summary of OPC UA Concepts Related to Address Space, Nodes, and Object Models
  62. [62]
    UA Part 1: Overview and Concepts - 6 Client/Server Service Sets
    Well known dedicated Discovery Servers provide a way for Clients to discover all registered Servers. OPC 10000-12 describes how to use the Discovery Services ...
  63. [63]
    UA Part 6: Mappings - 6 Message SecurityProtocols
    ### Summary of Conformance Profiles in OPC UA
  64. [64]
    UA Part 4: Services - 5 Service Sets
    Summary of each segment:
  65. [65]
    UA Part 7: Profiles - 4 Profile Model
    ### Summary of OPC UA Conformance Profiles
  66. [66]
    Profile Micro Embedded Device 2017 Server Profile
    This Profile is a FullFeatured Profile intended for small devices with limited resources. This Profile builds upon the Nano Embedded Device Server Profile.
  67. [67]
    UA Part 4: Services - 4.2 Request/response Service procedures
    Request/response procedures involve a client sending a request, the server decoding it, performing the operation, and returning a response with success/failure ...
  68. [68]
    UA Part 1: Overview and Concepts - 5.5 Publish-Subscribe
    The Publish-Subscribe (PubSub) communication model in OPC UA offers an alternative to the ClientServer model, enabling efficient and/or decoupled communication.
  69. [69]
    UA Part 6: Mappings - 5 Data encoding
    This standard defines three data encodings: OPC UA Binary, OPC UA XML and OPC UA JSON. It describes how to construct Messages using each of these encodings.
  70. [70]
    [PDF] The OPC UA Security Model For Administrators Whitepaper Version ...
    Jul 7, 2010 · When working with certificates it is important to understand the formats associated with a certificate and where the certificates are stored.
  71. [71]
    [PDF] OPC UA Security Analysis - BSI
    Mar 2, 2017 · The subject under examination of the "OPC UA security analysis" project is the OPC UA protocol in the ver- sion 1.02 (1.02.47 for Part 12) ...
  72. [72]
    Security - OPC Foundation
    Many of the concepts behind what's known today as "zero trust" already exist in OPC, such as advanced authentication schemes, including the use of PKI, ...Missing: enhancements | Show results with:enhancements
  73. [73]
    How to Certify - OPC Foundation
    The OPC Foundation Certification Program requires OPC-based products to pass an extensive level of testing to assure compliance, interoperability, robustness, ...Missing: discounts | Show results with:discounts
  74. [74]
    Unified Architecture - OPC Foundation
    This repository contains the OPC Unified Architecture (UA) .NET Standard Library. It provides a .NET Standard implementation of the OPC UA specifications, ...
  75. [75]
    Using Nodeset Files to Exchange Information - OPC Connect
    The usage of NodesetFiles greatly simplifies the exchange of information models and the configuration of clients and servers.
  76. [76]
    Test Tools - OPC Foundation
    The CTT can be used to test OPC UA Client and Server products for compliance to the OPC UA specification. Multiple versions of the CTT are maintained in order ...
  77. [77]
    Interoperability Workshops - OPC Foundation
    The purpose of such workshops is the validation of interoperability between products provided by different vendors.Background · Required Experience And... · Basic Sequence Of StepsMissing: program | Show results with:program
  78. [78]
    3 Rules for backward compatibility of Information Models
    An Information Model defines a contract between OPC UA Applications. OPC UA Clients can rely on the mandatory parts defined in such an Information Model.
  79. [79]
    OPC Foundation: Home Page
    OPC technologies were created to allow information to be easily and securely exchanged between diverse platforms from multiple vendors and to allow seamless ...What is OPC? · Unified Architecture · OPC Offices / OPC Hubs · OPC UAcademic
  80. [80]
    OPC-UA Application - Automotive Industry - RealPars
    Aug 5, 2025 · OPC Unified Architecture, or OPC-UA, allows data to be shared in real time between devices, systems, and applications in many different industries.
  81. [81]
    OPC UA Tutorial: Connect and Exchange Data with Industrial ...
    Jul 16, 2025 · OPC UA is an industry-standard protocol providing a universal language for secure communication between PLCs, SCADA systems, HMIs, and ...
  82. [82]
    What is the OPC HDA?
    OPC Historical Data Access (OPC HDA) is a protocol used in industrial automation systems to retrieve, manage, and analyze historical data.
  83. [83]
    Integration of DCS and ESD through an OPC application for ...
    Owing to the generic and flexible information modelling method, OPC UA has also been implemented in various types of process monitoring and control systems in ...<|separator|>
  84. [84]
    Historical Data Manager (Exaquantum/HDM) - Yokogawa
    Exaquantum Historical Data Manager allows Exaquantum to continually collect process data from an OPC HDA Server(s) into an Exaquantum Real-Time database.
  85. [85]
    [PDF] Standardized Smart Grid Semantics using OPC UA for Communication
    The mapping shows that it is possible to expose the IEC 61850 model in OPC UA. By providing the LN Class and the LNodeTypes in the UA Address Space, it is ...
  86. [86]
    IEC 61850 based OPC UA communication - The future of smart grid ...
    The IEC 61850 provides both an abstract data model and an abstract communication interface. Different technology mappings to implement the model exist. With the ...
  87. [87]
    OPC UA: An Automation Standard for Future Smart Grids
    OPC UA is the successor of the established Classic OPC specifications and state of the art regarding information exchange in the industrial automation branch.
  88. [88]
    4 General information to BACnet and OPC UA
    OPC DA provides functionality to browse through a hierarchical namespaces containing data items and to read, write and to monitor these items for data changes.
  89. [89]
    Mapping BACnet to OPC UA
    A mapping of building automation data from BACnet devices and represent them through a mapping device in OPC UA.
  90. [90]
    OPC UA Security for Mobile Healthcare Services
    The high level of security provided by CodeMeter ensures software and data protection at the endpoints, where data is transmitted and computed.
  91. [91]
    CryoMed™ with OPC UA, Medical Device 48 L | Request for Quote
    CryoMed™ with OPC UA, Medical Device. CryoMed with OPC UA provides precise, repeatable freezing results that protect samples from intracellular freezing.<|separator|>
  92. [92]
    Next Generation Task Controller for agricultural Machinery using ...
    In this article, an OPC UA information model was designed for data exchange between the task controller and implements, and its suitability for use in the high ...
  93. [93]
    https://opcfoundation.org/wp-content/uploads/2021/03/Standardized_Smart_Grid_Semantics_using_OPC_UA_for_Communication.pdf
  94. [94]
    Towards building OPC-UA companions for semi-conductor domain
    Mar 5, 2020 · Instead, the SEMI (SECS/GEM) set of standards is widely used in the industry for interfacing between the shop-floor ''equipment'', such as wafer ...
  95. [95]
    OPC UA for Process Automation
    OPC UA is much more than just a protocol – it's a framework to define and exchange standardized data with included (built-in by design) end-to-end security.Missing: chemicals refinery HDA
  96. [96]
    https://reference.opcfoundation.org/BACnet/v200/docs/4
  97. [97]
    Pioneering a new automation technology - ExxonMobil
    Feb 10, 2025 · This new technology is called Open Process Automation (OPA) and we're proud to be the first company in the world to deploy it at scale at a commercial ...
  98. [98]
    Open Process Automation for Distributed Control Systems - AIChE
    Case Study: Developing and testing an open architecture. ExxonMobil is a founding member of the OPAF. To complement the activities being progressed by the OPAF, ...
  99. [99]
    [PDF] OPC UA Users and Experts – Conveying Knowledge and Experience
    Oct 29, 2020 · The OPC Foundation publishes a series of interviews with experts, market leaders and think tanks in communication, automation and industrial IT ...
  100. [100]
    [PDF] Expertise - Softing Industrial
    ▫ Cost savings by using existing OPC Classic components. ▫ Gateway functionality for connecting controllers and components with integrated OPC UA Server to.
  101. [101]
    Exploring OPC UA's use cases and benefits in industrial environments
    Jul 11, 2023 · OPC UA brings numerous benefits to industrial companies, ensuring interoperability, real-time monitoring, secure data exchange, scalability, ...Missing: chemicals refinery HDA
  102. [102]
    OPC Server Software Market 2025 - Industry Share And Forecast
    In stockIt will grow from $14.93 billion in 2024 to $15.87 billion in 2025 at a compound annual growth rate (CAGR) of 6.3%. The growth in the historic period can be ...
  103. [103]
    OPC Foundation's Cloud Reference Architecture Unlocks the Future ...
    Sep 16, 2025 · The OPC Foundation is a global organization with over 1,000 members, committed to delivering secure, vendor-neutral interoperability across ...
  104. [104]
    https://www.bright-amber.com/case-studies/process-automation-in-manufacturing
  105. [105]
    What is the OPC UA Web API? - manubes
    May 27, 2025 · The OPC UA Web API is a new, REST-compatible interface available since OPC UA version 1.05.04. It is provided as a complete OpenAPI specification.Integration Via Rest · Simple Functions, Readable... · ConclusionMissing: 2022 | Show results with:2022
  106. [106]
    Releases · OPCFoundation/UA-.NETStandard - GitHub
    Sep 18, 2025 · The focus in this release was on perf improvements and bug fixes. This is also the last official release without ECC support... Server ...Missing: timeline | Show results with:timeline
  107. [107]
    OPC UA over MQTT: The Future of IT and OT Convergence - EMQX
    Aug 29, 2023 · In this article, we will dive into OPC UA over MQTT and explore its potential to empower the convergence of IT and OT.
  108. [108]
    OPC UA + MQTT = A Popular Combination for IoT Expansion
    OPC UA is a robust, secure and scalable expansion of the highly successful basic COM/DCOM-based OPC standard communication protocol. It enables the ...
  109. [109]
    OPC Foundation Welcomes Three New Board Members and ...
    The OPC Foundation is excited to announce the addition of three new members to its Board of Directors: Amazon Web Services (AWS), Google Cloud, and Huawei.
  110. [110]
    Press Releases Archives - OPC Foundation
    The latest announcements and developments from the OPC Foundation. For press related inquiries, please contact the Marketing department at the OPC Foundation.
  111. [111]
    Battery Passport Proof of Concept based on OPC UA
    Apr 21, 2024 · OPC UA has proven to be the right technology to standardize the management, operation, and optimization of renewables assets. It is, therefore, ...
  112. [112]
    OPC UA in Battery Cell Manufacturing: Progress of the Working Group
    ... battery production. In December 2024, the new working group "OPC UA for Battery Production" was established, and Uwe Volmer, from the Production, Logistics ...
  113. [113]
    A Gap Analysis of OPC UA Companion Specifications - ScienceDirect
    2024, Pages 853-858. Procedia CIRP. Leveraging Industry 4.0 Solutions for Lithium-Ion Battery Manufacturing: A Gap Analysis of OPC UA Companion Specifications.
  114. [114]
    AAS Meets OPC UA: A Unified Approach to Digital Twins - IEEE Xplore
    AAS Meets OPC UA: A Unified Approach to Digital Twins ; Article #: ; Date of Conference: 12-15 May 2025 ; Date Added to IEEE Xplore: 30 July 2025.
  115. [115]
    Leveraging OPC UA for Digital Twin Realization
    This case study focuses on the use of OPC UA to achieve Digital Twin realization, a core technology of Industry 4.0. The Merits of Utilizing Simulation Software.
  116. [116]
    Hannover Messe 2025 - 5G-ACIA.org
    Industrial 5G | Integration of OPC UA with 5G Networks Talk. Thursday, April 25 | 10:05 – 10:25 a.m.. Speaker: Dr. Xueli An, Huawei. Industrial 5G | How to ...
  117. [117]
    Hannover Messe - OPC Foundation
    In 2025 we showed these demos: Learn about the new OPC Foundation Cloud Reference Architecture including leading cloud suppliers like AWS, Google Cloud but also ...
  118. [118]
    OPC Foundation at Hannover Messe - OPC Connect
    Visitors to the interactive booth, staffed with experts from industry and officials of the OPC Foundation, were able to explore various live demonstrations:.
  119. [119]
    Approaching OPC UA Publish–Subscribe in the Context of UDP ...
    The Open Platform Communication Unified Architecture (OPC UA) protocol is a key enabler of Industry 4.0 and Industrial Internet of Things (IIoT).
  120. [120]
    How does OPC UA PubSub data support connector digital twins?
    Mar 15, 2024 · OPC UA Pub/Sub data can be sent from a connector with an embedded AAS to support the implementation of the connector's digital twin in an Industry 4.0 factory.
  121. [121]
    OPC UA over TSN: A New Frontier in Ethernet Communications
    Recently, the concept of Time-Sensitive Networking (TSN) in conjunction with OPC UA is being discussed more and more in the automation industry. For those ...
  122. [122]
    OPC UA over TSN: A Realistic Future for a Unified Industrial Control ...
    Numerous product demonstrations, announcements, and discussions promoted the combination of Time Sensitive Networking (TSN IEEE 802.1) with OPC UA messaging and ...
  123. [123]
    Edge Computing OPC UA over Testbed - Huawei Enterprise
    OPC UA over TSN as a critical edge computing connectivity and communication technology stack can provide a real-time, deterministic and truly open ...
  124. [124]
    (PDF) Enabling Federated Learning Services Using OPC UA ...
    May 30, 2024 · Administration Shell (AAS) and OPC UA are used for collecting and referencing operational and engineering data.Missing: streams | Show results with:streams
  125. [125]
    Enabling Federated Learning Services Using OPC UA, Linked Data ...
    An exemplary pipeline for federated services in cross-domain and cross-company value creation networks for cognitive production is presented, which enables ...
  126. [126]
    [PDF] Flexible Data Architecture for Enabling AI Applications in Production ...
    Abstract. We present a flexible data architecture that combines RDF knowledge graphs for semantic descriptions with tailored data formats and APIs for time.
  127. [127]
    OPC UA for Energy Management Companion Specification
    This document specifies the OPC UA Information Model to represent the Objects and services that comprise Energy Management.Missing: sustainability green manufacturing
  128. [128]
    Optimized energy savings thanks to innovative standards
    Mar 30, 2025 · This specification defines a standardized information model based on OPC UA that enables comprehensive energy management in industrial automation.
  129. [129]
    (PDF) OPC UA Information Model for Energy-Flexible Aqueous Parts ...
    Jun 29, 2025 · This paper introduces an energy synchronization platform and an OPC UA interface for operating machines in an energy-flexible manner.
  130. [130]
    Hybrid OPC UA: Enabling Post-Quantum Security for the Industrial ...
    These schemes offer the potential to enhance data transfers and layered cryptographic solutions for different applications, utilising quantum-safe technologies, ...
  131. [131]
    OPC UA connects the industry to the Metaverse
    Nov 13, 2023 · Metaverse concept and real world examples for Digital Twins in industrial automation have been published.
  132. [132]
    OPC UA Roadmap
    In our road maps, you can learn about OPC UA innovations along three different timelines: Recent innovations lists features that have been added to the ...