Build
Track B is for people writing code. It covers events, alarms and historical access, authoring your own information model, certificates and PKI properly rather than by disabling security, and building a working client and server in four languages.
| Courses | 4 |
|---|---|
| Lessons | 44 |
| Prerequisites | Track A, and enough of one of Python, JavaScript, C# or C to run an example. |
| Who it is for | Software developers and integrator engineers who are implementing an OPC UA client or server, or who own the code that talks to one. |
What you will be able to do
- You can subscribe to alarms and conditions with a filter that returns only what you need.
- You can pull server-side aggregates instead of streaming raw history and computing it yourself.
- You can author, compile and load a NodeSet2 information model of your own.
- You can set up a working PKI, including the SAN entries that make certificates actually validate.
- You can write a client that survives a server restart without losing its subscriptions.
- You can read an unfamiliar OPC UA SDK's API and map it onto the twelve tasks you already know.
Courses in this track
Events, alarms and history
Values tell you what is happening now; events and history tell you what happened and why. This course covers the Part 9 alarm hierarchy, event filters that return only what you need, condition classes as machine-readable reason codes, and server-side aggregates.
10 lessons · about 72 minutes
Information modelling
Anyone can expose tags. Modelling is what makes a server understandable to a client that has never seen it. This course covers modelling rules, interfaces, custom structures, authoring NodeSet2 XML, compiling it, and publishing it.
12 lessons · about 96 minutes
Security and PKI
Most OPC UA security problems are certificate problems, and most are solved by disabling security, which is why so many plants run None. This course sets up a working PKI properly: policies and modes, certificate anatomy, the four stores, roles and audit.
12 lessons · about 96 minutes
Write a client and a server
The same twelve tasks, implemented four times: Python with asyncua, Node with node-opcua, C# with the OPC Foundation reference stack, and C with open62541. Learning the shape once means you can read any OPC UA SDK afterwards.
10 lessons · about 80 minutes
Last verified 7 September 2026 against OPC UA 1.05.07. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.