UA-.NETStandard/docs

OPC UA .NET Standard stack documentation

These guides lead from a first working application to advanced and experimental capabilities. Follow the numbered stages when you are learning. Choose only the paths that match your application, or use the contents list to find a feature.

• New to the SDK? Start with Getting started, read OPC UA concepts, then build your first information model.
• Upgrading from 1.5.x? Read What's New in 2.0, then follow the Migration Guide.
• Contributing to this repository? See Contributing and maintaining the SDK.

Contents

• How to use this index
• 1. Get started
• 2. Build your application
  • Client path
  • Server path
  • PubSub path
• 3. Add data types and application services
  • Data types and models
  • Application services
• 4. Use companion models
• 5. Prepare for production
• 6. Advanced integration, reliability, and scale
  • Transports and integration
  • Session recovery and performance
  • Security infrastructure and fleet management
  • High availability and deployment
  • Native AOT publishing
• 7. Draft and experimental capabilities
• Reference and upgrade
• Contributing and maintaining the SDK
• UaLens NodeSet2 explorer

How to use this index

Each stage builds on the earlier ones, but you do not need to read every guide. After stage 1, choose the client, server, or PubSub path. Stages 3 to 7 are optional; use the guides your application needs. A stage or group names the knowledge it assumes.

Labels describe the maturity of a package or model:

• Preview package: the package family keeps a -preview version, even when the core packages are stable. See Versioning.
• Draft model: the guide implements a working-group draft specification. Its namespace URIs and NodeIds are provisional.
• Experimental: the guide marks the feature as experimental.

These labels are independent of difficulty. An advanced guide can describe a stable feature, and a released specification can ship in a preview package.

1. Get started

Run a client and server, then learn the terms that the other guides use.

• Getting started — run the minimal samples, or build a client and server from NuGet packages.
• OPC UA concepts — applications, endpoints, sessions, the address space, values, subscriptions, and PubSub.
• Your first information model — add a model to the Getting started server, then read, write, and call it from the client.
• Sample catalogue — minimal, reference, PubSub, and companion-model applications.
• UaLens desktop engineering workspace — connection, exploration, monitoring, administration and saved workspaces, with guided companion workflows, configuration prerequisites and safety limits.
• Packages and supported platforms — choose packages and target frameworks.

2. Build your application

Choose the path for your application. The paths are independent: for example, a PubSub application needs neither a client nor a server.

Client path

Assumes Getting started.

1. Dependency injection: client feature — configure a client in the .NET Generic Host.
2. Managed sessions — connect, recover from connection loss, and close. To compare the managed and classic session APIs, see choosing a session API.
3. Read, write, and call methods — resolve namespace URIs and browse paths, check the status of each operation, and call methods through a client generated from the model.
4. Subscriptions — callback subscriptions for long-lived monitoring and streams for short observations.
5. Generation-bound requests — retain remote file handles, history cursors and target classifications without following a replacement connection.

Server path

Assumes Getting started.

1. Dependency injection: server feature — host a server and configure its endpoints, security, and node managers.
2. Node managers: start with a model — generate a node manager from your model and attach callbacks. Complete method invocation results covers ordered output values and resolved operation/input diagnostics. Your first information model is a complete example.
3. Runtime NodeSets — load NodeSet2 models without generated code when models change independently of your application.
4. Asynchronous server support — implement service and node-manager callbacks asynchronously.

PubSub path

A PubSub application needs neither a client nor a server, so the Getting started exercise and the other two paths are optional here.

1. Concepts: client/server and PubSub — publishers, subscribers, and datasets.
2. Run a first publisher and subscriber — exchange signed and encrypted messages on one computer with the reference PubSub sample.
3. PubSub guide — the fluent builder, hosting, configuration, encodings, and security.
4. Transport selection — UDP, Ethernet, MQTT, and Kafka.

3. Add data types and application services

Assumes the client or server path. Choose the capabilities your application needs.

Data types and models

• Source-generated data types — generate encodeable implementations for your own structures.
• Complex types — decode server-defined structures and enumerations at run time.
• Model dependencies — compose models that depend on other models.
• NodeId assignment — control the identifiers of nodes created at run time.
• Schema generation — produce XSD, BSD, and JSON schemas for data types.

Application services

• State machines — define, drive, and observe state transitions.
• Programs — host and control Part 10 invocations, monitor captured transition results, and manage diagnostics and lifetime.
• Alarms and conditions — raise, acknowledge, and stream alarms. Alarm conditions use state machines, for example for shelving.
• Historical access — store and read value and event history.
• Aggregates — calculate processed history; read historical access first.
• File system client — transfer files through the standard file objects.
• Alias names — find nodes through named aliases.
• Node management — let clients add and delete nodes and references.
• Final-value publication — await terminal Value notifications in real Publish responses before removing dynamic subtrees.
• Model change tracking — keep client caches current when the address space changes.
• NodeSet export — export a server's address space to NodeSet2 XML.

4. Use companion models

Companion specifications define models for particular industries and device types; Concepts explains how they relate to the base model. These libraries assume the server path and, for typed client access, the client path. The packages load the models that each model depends on.

• Device Integration (OPC 10000-100) — devices, topology, and locking.
• Asset Management Basics (OPC 10000-110) — make devices, machines, pumps or scales manageable assets: discovery, identification, health alarms, maintenance, documentation links and locations. Read Device Integration first.
• Software update (OPC 10000-100) — software package storage, installation, and confirmation. Read Device Integration first.
• ISA-95 (OPC 10030 and OPC 10031-4) — the common model and job control.
• Positioning (OPC 10000-210 and OPC 10000-211; preview package) — relative frames and geographic positions.
• Machinery (OPC 40001-1, -2, -3, -4 and -101) — machines with identification, server-driven state machines, process values, job management, energy and result transfer, based on the Industrial Automation, Device Integration, PA-DIM, ECM and ISA-95 models.
• Pumps (OPC 40223) — pumps and vacuum pumps, published both as Device Integration devices and as Machinery machines.
• AutoID Devices (OPC 30010) — RFID, OCR, optical, optical verifier and RTLS readers: model, server hosting with a provider contract for the reader hardware, typed client, MCP tools and a simulated RFID reader sample, based on the Device Integration model.
• Machine Vision (OPC 40100-1 and OPC 40100-2) — released control, recipes, configurations, results, assets, and condition monitoring, with Vision/Perception composition and Machinery hosting.
• MachineTool and wireless peripherals (OPC 40501-1 and OPC 40505) — machine monitoring, tools, production/jobs/files and independently hosted wireless measurements, configuration and records in one package family.
• Geometric Measurement Systems (OPC 40210) — native measurement equipment, qualification/calibration, production observations and results. The guide documents the upstream undefined Production-statistics CU exception.
• Cranes and Hoists (OPC 40020-1; preview packages) — Robotics-derived crane systems, equipment observations and explicitly authorized speed-limit requests.
• Scales (OPC 40200 and OPC 30050) — weighing technology with every scale kind, scale systems, recipes and PackML state machines, based on the Machinery model.
• Plastics and rubber capabilities (OPC 40083 and OPC 40082-6) — shared machine configuration, control and monitoring, with production dataset transfer and granulate drying.
• Extrusion (OPC 40084-1 through -12) — the extrusion line and its device families, optional capabilities, typed clients and composition.
• Robotics (OPC 40010-1; preview package) — motion-device systems, based on the Industrial Automation and Device Integration models. The guide's draft Robot Intent model is listed in stage 7.
• WoT connectivity (OPC 10100-1; preview package) — connect Web of Things assets. Its registry extension is listed in stage 7.

For more examples, including the Pumps and Machinery models, see the companion-model samples. The generic recycling simulation combines a causal production model with separately hosted process views; its guide identifies the remaining companion integration limits. The optional recycling operator console adds a local ASP.NET Core 10 browser schematic, strict UA trust and role-limited commands; its guide covers standalone and Compose setup, image publication and the synthetic sample's operational/security limits.

To expose these typed client interfaces to an agent, use the industrial companion MCP tools. Select one family or compose several profiles without enabling the entire tool catalog. The WoT and xRegistry profiles cover asset/registry management and document conversion; the document profile does not require a UA connection.

5. Prepare for production

Builds on the certificate trust you used in Getting started. Before you deploy a client or server, work through the production readiness checklist. It links to these guides for the details:

1. Certificates — certificate stores, trust, and chain validation.
2. Identity providers — authenticate users on clients and servers.
3. Role-based user management — map identities to roles and permissions.
4. Certificate manager — certificate lifecycle, rotation, and remote updates.
5. Diagnostics — logging, metrics, tracing, auditing, and packet capture.
6. Rate limiting — admission limits and busy signals during connection storms.
7. Server resource isolation — per-caller limits and reserved capacity for startup and recovery.
8. Profiles and facets — implemented profiles and platform boundaries.
9. Container reference server — run the reference server in a container.

6. Advanced integration, reliability, and scale

Each group names the stages it assumes.

Transports and integration

Assumes the client or server path.

• Transports — UA-TCP, HTTPS, and WebSocket transports.
• REST binding — OpenAPI mapping, encoding negotiation, and HTTP authentication.
• OPC UA over OpenAPI — serve the OpenAPI document the stack generates from its REST routes and call the server from generated REST clients.
• Reverse Connect — server-initiated connections.
• Session-less invocation — let clients call Read, Browse, Call and the other §6.3 Services without a Session.
• PubSub external-server adapter — bind PubSub to an OPC UA server through a managed client session. Assumes the client and PubSub paths.
• PubSub transcoding — convert encodings, values, and metadata between PubSub messages.
• MCP server — let AI agents browse, read, write, and diagnose OPC UA servers. Stack workflow profiles add GDS/credential issuance, roles/users, files, alarms, history, schemas, policy-controlled PubSub and live WoT execution.
• WoT / NodeSet conversion and WoT protocol bindings — convert Thing Descriptions and add protocol bindings. The conversion guide also covers resolver ownership and DataType declaration inputs. Read WoT connectivity first.

Session recovery and performance

The subscription guides assume the client path; the sizing guides assume Diagnostics.

• TransferSubscriptions — move server subscriptions to a new session.
• Durable subscriptions — keep subscriptions and queued notifications while clients are disconnected.
• Generation-bound session clients — capture dispatch, session identity and mapping snapshots without reconnecting to a replacement peer.
• Server scalability — sizing limits, bottlenecks, and runtime settings for servers under load (Server GC, hybrid CPUs, warm-up).
• Benchmarks — measured performance and methodology.

Security infrastructure and fleet management

Assumes stage 5.

• ECC profiles — elliptic-curve security policies and their platform requirements.
• Crypto providers — replace the platform cryptography and keep private keys in hardware.
• Provisioning mode — configure a new server securely before exposing application data.
• Global Discovery Server — application registration and central certificate management.
• GDS sample — a runnable onboarding workflow.
• AuthorizationService — issue access tokens.
• KeyCredentialService — manage credentials for services that are not OPC UA. Its issued-token bridge is listed in stage 7.

High availability and deployment

Assumes a working single server and stage 5.

• High availability (preview package) — redundancy, failover, and distributed state.
• Replica-consistent NodeIds (preview package) — keep node identifiers identical across replicas; required before replicating an address space.
• Kubernetes (preview package) — cluster deployment, discovery, readiness, and secrets. Read high availability first.
• PubSub high availability (preview package) — redundant publishers and subscribers. Assumes the PubSub path.

Native AOT publishing

Publish an application as a native executable without a JIT compiler; start with Native AOT: publish an application. Feature-specific guidance:

• Servers with generated node managers
• Applications hosted with dependency injection
• PubSub applications

7. Draft and experimental capabilities

These guides implement working-group drafts or experimental extensions. Namespace URIs, NodeIds, and APIs can change before the specifications are published, so evaluate them before you depend on them in production. Each guide describes its current limitations.

• xRegistry (draft model; preview package) — the generic registry base model, resource storage, and federation.
• AI model management (draft model; preview package) — model catalogues, deployments, inference, and learning jobs. Builds on xRegistry.
• Perception model (draft model; optional OpenUSD renderer is preview-only) — capture, media, feedback, and client workflows.
• Robot Intent (draft model; preview package) — task-level motion commands. Does not require the Robotics model.
• OpenUSD (draft models; preview package) — bind values to OpenUSD scenes and materialize scenes in the address space.
• WoT Connectivity registry (draft model; preview package) — hosting, document provisioning, and refresh.
• WoT-Con 1.02 compatibility — existing-type bindings, declarations, and original document preservation.
• WoT runtime provider contracts — exact-Version dependencies and leases, prepared storage/publication, and recovery.
• KeyCredential issued-token bridge (experimental).

These samples combine several draft or preview capabilities. Read the guides for their models first:

• Bin picking cell — Robot Intent, Vision, and an OpenUSD scene.
• Visual inspection cell — Vision, AI model management, and ISA-95 job control.
• WoT aggregation sample — load Device Integration, Machinery, and Pumps models from WoT documents through the WoT Connectivity 1.1 registry, and bind them to two OPC UA source servers.
• Generator sample model (draft model) — generating-set simulation and scene composition.

Reference and upgrade

• What's New in 2.0 — a summary of new capabilities.
• Migration Guide — upgrade from 1.5.378, with topic-specific 2.0 guides and PubSub migration.
• Reference client — command-line configuration and transport profiles.
• Reference server — hosting and compliance-test setup.
• Reference PubSub client — publisher, subscriber, and external-adapter modes.

The Windows Forms reference applications are maintained in the Samples repository.

Contributing and maintaining the SDK

These documents describe building and maintaining this repository, not using the SDK in an application:

• Developer Guide — prerequisites, build, tests, and coding conventions.
• Continuous integration — pipelines and coverage gates.
• Native AOT test harness — build, run, and extend the Native AOT compatibility tests.
• Release process — release branches, versioning, backports, and recovery.
• Redundancy sample tests — process-level failover and soak validation.
• Fuzz testing — encoder, certificate, and network campaigns.