computer science

OPC Unified Architecture

OPC Unified Architecture is a computer science topic covered in the lgStudy science library. This page brings together a partial reference excerpt, illustrations, worked examples, real-world applications and a short study plan, so you can understand OPC Unified Architecture rather than just read about it. In short: OPC Unified Architecture (OPC UA) is a cross-platform, open-source, IEC62541 standard for data exchange from sensors to cloud applications developed by the OPC Foundation. Distinguishing characteristics are: Standardized data models freely available for over 60 types of industrial equipment, published by the OPC Foundation via Companion Specifications Extensible security profiles, including authentication, authoriza…

Key takeaways

OPC Unified Architecture belongs to computer science; place it in that map before memorising details.
Learn the definition first, then one example that makes the definition concrete.
Connect OPC Unified Architecture to a quantity you can measure, compute or draw — that is where exam questions come from.
Reproduce the core statement of OPC Unified Architecture from memory before moving on to harder problems.

Reference excerpt

Standardized data models freely available for over 60 types of industrial equipment, published by the OPC Foundation via Companion Specifications Extensible security profiles, including authentication, authorization, encryption and checksums Extensible security key management, including X.509, token and password Support for both client-server and publish-subscribe communication patterns Communication protocol independent. Mappings to several communication protocols like TCP/IP, UDP/IP, WebSockets, AMQP and MQTT are specified Initially successful in standardized data exchange with industrial equipment (discrete manufacturing, process manufacturing, energy) and systems for data collection and control, but now also leveraged in building automation, weighing and kitchen equipment and cloud applications Open – open-source reference implementations freely available to OPC Foundation members, non members under GPL 2.0 license Cross-platform – not tied to one operating system or programming language Service-oriented architecture (SOA) The specification is freely available on the OPC Foundation website and is split into several parts to ease implementation, but only OPC UA stack vendors need to read them, end users simply leverage existing commercial and/or open-source stacks available in all popular programming languages

History Although developed by the same organization, OPC UA differs significantly from its predecessor, Open Platform Communications (OPC). The Foundation's goal for OPC UA was to provide a path forward from the original OPC communications model (namely the Microsoft Windows-only process exchange COM/DCOM) that would better meet the emerging needs of industrial automation. After more than three years of specification work and another year for a prototype implementation, the first version of the Unified Architecture was released in 2006. The current version of the specification is on 1.04 (22 November 2017). The new version of OPC UA now has added publish/subscribe in addition to the client/server communications infrastructure. Although the original binding to COM/DCOM helped OPC to distribute well, it had several drawbacks:

Frequent configuration issues with DCOM; No configurable time-outs; Microsoft Windows only; Lower security; No control over DCOM (COM/DCOM is kind of a black box, developers have no access to sources and therefore have to deal with bugs or insufficient implementations). These drawbacks along with a number of other considerations pushed the decision to develop a new and independent stack for OPC UA, which replaces COM/DCOM. The main characteristics of this communication stack were:

Multi-platform implementation, including portable ANSI C, Java and .NET implementations; Scalability: from smart sensors and smart actuators to mainframes; Multi-threaded, as well as single-threaded/single-task operation—necessary for porting the stack to embedded devices; Security, based on new standards; Configurable time-outs for each service; Chunking of big datagrams. This communication stack reflects the beginning of various innovations. The OPC UA architecture is a service-oriented architecture (SOA) and is based on different logical levels. OPC Base Services are abstract method descriptions, which are protocol independent and provide the basis for OPC UA functionality. The transport layer puts these methods into a protocol, which means it serializes/deserializes the data and transmits it over the network. Two protocols are specified for this purpose. One is a binary TCP protocol, optimized for high performance and the second is Web service-oriented. The OPC information model is a Mesh Network based on nodes. These nodes can include any kind of meta information, and are similar to the objects of object-oriented programming (OOP). A node can have attributes for read access such as DataAccess (DA), HistoricDataAccess (HDA), methods that can be called (Commands), and triggered events that can be transmitted (such as AlarmEvent (AE), DataAccess, and DataChange). Nodes hold process data as well as other types of metadata. The OPC namespace contains the type-model. The namespace is a URI that identifies the naming authority responsible for assigning the identifier element of the NodeId. Naming authorities include the local Server, the underlying system, standards bodies and consortia. It is expected that most Nodes will use the URI of the Server or of the underlying system. OPC UA defines a common infrastructure model to facilitate this information exchange, and specifies the following:

The information model to represent structure, behaviour and semantics; The message model to interact between applications; The communication model to transfer the data between end-points; The conformance model to guarantee interoperability between systems. Client software can verify what profiles a server supports. This is necessary to obtain information, if a server only supports DA functionality or additionally AE, HDA, etc. Additionally, information can be obtained about whether a server supports a given profile. New and important features of OPC UA are:

Redundancy support Heartbeat for connections in both directions (to indicate whether the other end is "alive"). This means that both server and client recognize interrupts. Buffering of data and acknowledgements of transmitted data. Lost connections don't lead to lost data anymore. Lost datagrams can be refetched. At the OPC UA DevCon in October 2006, in Munich the first prototypes were presented live. Various UA Servers have been shown on a Beckhoff programmable logic controller and an embedded test board from Euros. The Beckhoff PLC is based on Windows XP Embedded and the embedded controller is based on the real-time operating system Euros. The company Embedded Labs Ltd demonstrated an OPC UA Server based on their own C++ UA Stack executing on a single chip ARM microcontroller with 64kB RAM. In October 2012 the German Fraunhofer-Application Center IOSB-INA and the Institute for industrial Information Technologies (inIT) showed that an OPC UA server is scalable down to 15 kB RAM and 10 kB ROM and therefore usable at chip level. The current version of the specification is 1.05.06, and was released on 22 October, 2025.

… excerpt ends here. Continue reading the full article.

Worked examples

Example 1 — a first encounter with OPC Unified Architecture

Start with the simplest possible case. Write down what OPC Unified Architecture claims or describes in one sentence, then invent the smallest concrete situation in which that sentence is true. In computer science, the smallest case is usually a single object, a single equation or a single measurement. Check that every symbol or term in your sentence has a meaning in that case.

Example 2 — changing one variable

Take the situation from Example 1 and change exactly one quantity: double it, halve it, or set it to zero. Predict what should happen to OPC Unified Architecture before you calculate. Comparing your prediction with the result is the fastest way to find out whether you understand the idea or only the words.

Example 3 — an exam-style question

Typical questions about OPC Unified Architecture ask you to (a) state it precisely, (b) apply it to given data, and (c) explain a limitation. Practise writing all three answers in under five minutes; the third part is what separates a full-mark answer from an average one.

Applications of OPC Unified Architecture

In research: OPC Unified Architecture appears in computer science research whenever the underlying quantities have to be modelled precisely. Papers usually cite it as a starting assumption and then explore where it breaks down.
In technology and industry: Engineering practice reuses OPC Unified Architecture in design rules, simulations and safety margins. Knowing the idea lets you read a specification sheet and understand why the numbers look the way they do.
In the classroom: OPC Unified Architecture is common in secondary-school and first-year university syllabi. It links to neighbouring topics Application programming interfaces, Computer standards, Industrial automation, so understanding it makes those chapters shorter.
In everyday life: Look for OPC Unified Architecture outside the textbook — in sport, cooking, traffic, electronics or the sky above you. An example you found yourself is remembered far longer than one you were given.

Affiliate

Preply — study more efficiently by working with a personal tutor. 50% off.

How to study OPC Unified Architecture in 20 minutes

Read the reference excerpt below once, without taking notes.
Close the page and write down what OPC Unified Architecture means in your own words.
Compare your version with the excerpt and mark what you missed.
Work through the three examples above with pen and paper.
Explain OPC Unified Architecture out loud to somebody else — or to Teacher Smith in the lgStudy chat.

Frequently asked questions

What is OPC Unified Architecture in simple terms?

OPC Unified Architecture (OPC UA) is a cross-platform, open-source, IEC62541 standard for data exchange from sensors to cloud applications developed by the OPC Foundation. Distinguishing characteristics are: Standardized data models freely available for over 60 types of industrial equipment, publis…

Why does OPC Unified Architecture matter?

Because it connects several computer science ideas at once: it gives you a definition you can apply, a quantity you can calculate, and a way to check whether a result is plausible.

How should I study OPC Unified Architecture?

Read the excerpt, restate it from memory, then work through the examples and applications listed on this page. The five-step study plan above takes about twenty minutes.

What does this page cover?

It gives you a compact reference excerpt plus original lgStudy explanations, examples, applications and study material on OPC Unified Architecture.