OPCFoundation.NetStandard.Opc.Ua.Pumps.Server 2.0.2

Prefix Reserved
dotnet add package OPCFoundation.NetStandard.Opc.Ua.Pumps.Server --version 2.0.2
                    
NuGet\Install-Package OPCFoundation.NetStandard.Opc.Ua.Pumps.Server -Version 2.0.2
                    
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="OPCFoundation.NetStandard.Opc.Ua.Pumps.Server" Version="2.0.2" />
                    
For projects that support PackageReference, copy this XML node into the project file to reference the package.
<PackageVersion Include="OPCFoundation.NetStandard.Opc.Ua.Pumps.Server" Version="2.0.2" />
                    
Directory.Packages.props
<PackageReference Include="OPCFoundation.NetStandard.Opc.Ua.Pumps.Server" />
                    
Project file
For projects that support Central Package Management (CPM), copy this XML node into the solution Directory.Packages.props file to version the package.
paket add OPCFoundation.NetStandard.Opc.Ua.Pumps.Server --version 2.0.2
                    
#r "nuget: OPCFoundation.NetStandard.Opc.Ua.Pumps.Server, 2.0.2"
                    
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
#:package OPCFoundation.NetStandard.Opc.Ua.Pumps.Server@2.0.2
                    
#:package directive can be used in C# file-based apps starting in .NET 10 preview 4. Copy this into a .cs file before any lines of code to reference the package.
#addin nuget:?package=OPCFoundation.NetStandard.Opc.Ua.Pumps.Server&version=2.0.2
                    
Install as a Cake Addin
#tool nuget:?package=OPCFoundation.NetStandard.Opc.Ua.Pumps.Server&version=2.0.2
                    
Install as a Cake Tool

Opc.Ua.Pumps.Server

Server hosting for OPC 40223 — OPC UA for Pumps and Vacuum Pumps.

builder.Services
    .AddOpcUaServer(configuration)
    .AddPumps()
    .ConfigurePumps(async context =>
    {
        IPumpBuilder pump = await context.Manager.CreatePumpAsync(
            new QualifiedName("Pump_1", context.Manager.InstanceNamespaceIndex),
            context.CancellationToken);

        pump.WithNameplate(new PumpNameplate
        {
            NodeId = NodeId.Null,
            Manufacturer = new LocalizedText("Acme Pumps"),
            SerialNumber = "SN-001",
            Model = new LocalizedText("PumpX-2000"),
            CountryOfOrigin = "DE"
        });

        pump.Measurements
            .SetAnalog(BrowseNames.MassFlow, 12.5, EngineeringUnits.KilogramsPerSecond)
            .SetAnalog(BrowseNames.DifferentialPressure, 350_000, EngineeringUnits.Pascal);

        pump.Supervision(BrowseNames.SupervisionProcessFluid)
            .SetDiscrete(BrowseNames.Cavitation, false);

        pump.AddPort(PumpPortKind.InletConnection, "Suction")
            .SetAnalog(BrowseNames.MaximumAllowableInletPressure, 1_600_000);
    });

What it does

PumpsNodeManager derives from DiNodeManager — a pump is a Device Integration device — and loads DI, OPC 10000-200 IA, OPC 40001-1 Machinery and OPC 40223 Pumps into one address space, in that order (Machinery's Stacklight is typed by an IA type, so IA has to be loaded first). CreatePumpAsync materialises a PumpType instance below DeviceSet and organizes it into the Machinery Machines folder as well, so both a DI client and a Machinery client find it.

Building a pump

Nothing is materialised until it is asked for. The full PumpType surface is about 3000 nodes; a pump that publishes a flow rate and a cavitation flag should publish those, not 3000 mostly empty variables.

IPumpBuilder exposes the seven groups and their sub-groups as properties, and IPumpGroupBuilder addresses everything below them by browse name — Add, Set, SetAnalog, SetDiscrete, With, Nested. Children are created through the model's own CreateChild, so each one gets the type, data type, access level and default value the specification declares. Names the group does not declare are rejected. Pass the generated Opc.Ua.Pumps.BrowseNames constants and a rename in the model breaks the build.

SetDiscrete handles both shapes OPC 40223 uses for a boolean: the TwoStateDiscreteType variables of the supervision groups, and the DiscreteInput/DiscreteOutputObjectType objects of the signal and actuation groups whose value sits one level down.

Retained identity, conditions and history

PumpsRuntime.WithRetainedIdentificationAsync binds AssetId, ComponentName and Location to a persistent IAssetConfigurationStore with explicit role permissions and a stable ProductInstanceUri. Storage commits precede accepted writes; the shared AMB binding restores the values on restart, including the component-name locale.

AddDiagnosticAlarmAsync maps a supervision input to an explicit DI NE107 category. AddMeasurementAlarmAsync creates an exclusive limit condition. Publish readings, then await each binding's EvaluateAsync; acknowledgment and retained refresh use the standard condition implementation.

HistorizeAsync and HistorizeEventsAsync select an already configured shared Part 11 provider. No fallback archive or physical pump controller is created. BindDocumentationFile and BindMarkingFile reuse the session-owned IFileTypeBinder. These extensions accept direct services or services resolved inside either hosting configurator. The address-space owner releases capture and file bindings; the application or DI container owns storage providers.

Neither Pumps profile URI is advertised automatically. The Advanced profile's published Base dependency has conflicting Pumps/CAS URIs; see the guide for the unresolved reference and mandatory inherited facets.

The standalone and composed runtime contributes the Table 152 native units from live registered nodes, bound conditions and historian routes. Titles use the Pumps model namespace to avoid collisions with other companions' generic unit names. Removing required nodes, conditions or routes withdraws their units; disposal withdraws the runtime's contribution.

Typed fluent accessors

This package also supplies the typed Opc.Ua.Server.Fluent accessors for the whole Pumps model, so builder.Node<PumpState>(id).Components().Events() and friends are available to servers that wire per-node callbacks directly.

Ownership

AddPumps claims the Device Integration address space, so it cannot be combined with AddOpcUaDi or another DI-owning registration. A server that uses the stock Machinery owner composes Pumps additively:

services.AddOpcUa().AddServer<StandardServer>(ConfigureServer)
    .AddMachinery(options => options.Parts = MachineryParts.BuildingBlocks)
    .AddPumpsToMachinery()
    .ConfigurePumpsFor<MachineryNodeManager>(async (context, ct) =>
    {
        var pump = await context.Runtime.CreatePumpAsync(
            new QualifiedName("FeedPump", context.Runtime.InstanceNamespaceIndex), ct);
        pump.Measurements.SetAnalog(Opc.Ua.Pumps.BrowseNames.MassFlow, 12.5);
    });

The shared PumpsRuntime preserves lazy groups and live updates, with all instances in the Machinery owner's application namespace. It can coexist with AddScalesToMachinery() and the AMB sidecar. For direct construction, supply PumpsMachineryModelProvider to MachineryNodeManager and call owner.CreatePumpsRuntime() after its address space is ready. The owner disposes the runtime on shutdown. Existing standalone APIs remain unchanged.

See the Pumps guide for model ordering, service injection, asset registration and custom-owner lifetime.

For the client side use Opc.Ua.Pumps.Client; the model and the shared snapshot contracts live in Opc.Ua.Pumps.

Product Compatible and additional computed target framework versions.
.NET net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed.  net9.0 is compatible.  net9.0-android was computed.  net9.0-browser was computed.  net9.0-ios was computed.  net9.0-maccatalyst was computed.  net9.0-macos was computed.  net9.0-tvos was computed.  net9.0-windows was computed.  net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
.NET Framework net48 is compatible.  net481 was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last Updated
2.0.2 140 11/11/2026
2.0.1 284 10/12/2026
2.0.0 277 10/7/2026