Marc Schier
0374e19121
# Description _Describe the changes here to communicate to the maintainers why they should accept this pull request. By default - this will become the Commit message after merging and thus define history._ Add provider-backed MachineTool, bundled WMTP, GMS and CranesHoists companions using the existing Machinery/MachineVision fluent, DI and typed-client approach. **The PR is open/non-draft by user choice. Current head `ecc4a7d6ca3e8004cf28ab54da605da302d026bf` is mergeable and has 108 successful checks, six intentionally skipped checks, zero failures and zero pending checks. All five primary workflows completed successfully at that exact head.** | Family | Released specification/model | Packaging | | --- | --- | --- | | MachineTool | OPC 40501-1, 1.02.0 | Model, Server, Client and MCP; normal root versions | | WMTP | OPC 40505, 1.0.0 | Bundled in MachineTool; distinct CLR/wire namespace and independent WMTP-only hosting | | GMS | OPC 40210 reference 1.0.1, normative model 1.0.0 | Model, Server, Client and MCP; normal root versions | | CranesHoists | OPC 40020-1, 1.00 | Model, Server, Client and MCP; all four plus Debug variants forced preview | There are **12 new packable projects**. No separate WMTP package/profile/guide, root version bump, tag, release or package publication is included. Mandatory instance structure is the default; selected optional features require explicit providers. The implementation reuses Machinery results/jobs/files/ProcessValues and Robotics topology, including retained MachineTool Production, defined GMS jobs/parts, modern ISA95/Machinery jobs, shared-owner hosting and isolated instances alongside MachineVision. Runtime and integration fixes preserve raw quality/timestamps, coherent acquisition, namespace ownership, accepted-configuration state, borrowed-resource lifetime, session/node/file cleanup, terminal-value publication, event propagation and endpoint-aware capability publication. Firmware/licence transfer means provider acceptance, not installation/activation. Cancellation does not silently abort another caller's operation. The later upstream MCP expansion is integrated without losing either family set or its default-off privileged/live execution policy. ### Conformance and scope Canonical model inputs are pinned to UA-Nodeset revision `96a08945425d0295edb3607d2a38f6841ef44046`. **GMS upstream exception:** [Annex A.1](https://reference.opcfoundation.org/specs/OPC-40210/annex-a) makes the released NodeSet normative, but §12.3.2.7 requires undefined `GMS_ProductionStatisticsType`. Inherited statistics and defined jobs/parts are implemented without inventing a standard type/NodeId; the complete GMS Production facet is withheld. The requirement ledger records **102 positively evidenced CU rows, 96 directly negative-tested rows and six explicit negative-evidence limitations**. All 648 test-class/name/TRX links were independently resolved to passing cases. The six limitations concern Stacklight, retained legacy PowerOnDuration, Machinery PowerOnDuration, WorkingUnit, Obligation and MaintenanceMode. They are not claims that every invalid-input or hardware-control behavior was tested. The undefined GMS requirement is outside the 102 defined CUs. No external certification claim is made. Retained baseline complete-assembly line coverage, with generated code retained and no source exclusions: | Family | Model | Server | Client | | --- | ---: | ---: | ---: | | MachineTool/WMTP | 83.80% | 91.98% | 84.74% | | GMS | 95.51% | 90.63% | 88.38% | | CranesHoists | 92.76% | 94.45% | 92.24% | These nine measurements predate the later focused review fixes and merges; they are not relabelled as new `ecc4a7d6c` percentages. The current head's separate CI code-coverage check succeeded. No new exclusions or threshold relaxations were introduced. ## Related Issues - Fixes [#4764](https://github.com/OPCFoundation/UA-.NETStandard/issues/4764), the implementation/design and acceptance tracker. ## Checklist _Put an `x` in the boxes that apply. You can complete these step by step after opening the PR._ - [ ] I have signed the [CLA](https://opcfoundation.org/license/cla/ContributorLicenseAgreementv1.0.pdf) and read the [CONTRIBUTING](https://github.com/OPCFoundation/UA-.NETStandard/blob/master/CONTRIBUTING.md) doc. - [x] I have added tests that prove my fix is effective or that my feature works and increased code coverage. - [x] I have added all necessary documentation. - [ ] I have verified that my changes do not introduce (new) build or analyzer warnings. - [ ] I ran **all** tests locally using the **UA.slnx** solution against at least .net **framework** and .net **10**, and all passed. - [ ] I fixed **all** failing and flaky tests in the CI pipelines and **all** CodeQL warnings. - [x] I have addressed **all** PR feedback received.
GMS sample pair
GmsServer and GmsClient use the public fluent/DI hosting, generated proxies
and bounded GMS clients. These are simulations, not physical measuring
equipment. There are no measurement-start, job-execution, calibration or
machine-correction commands.
The released model is 1.0.0; its reference document is 1.0.1. The upstream
undefined GMS_ProductionStatisticsType remains an explicit conformance
exception: Annex A.1 makes the released NodeSet normative. Neither sample
claims the complete Production facet.
Run
From the repository root, use separate terminals:
dotnet run --project samples\GMS\GmsServer\GmsServer.csproj -f net10.0 -- `
--advanced --instances 2 --seconds 60 --demo-trust
dotnet run --project samples\GMS\GmsClient\GmsClient.csproj -f net10.0 -- `
--events --characteristic Bore --download --demo-trust
Omit --advanced for mandatory structure and inline results. Optional
equipment, corrections and file-transfer absence are reported explicitly.
The server prints READY only after OPC UA initialization; --port 0 selects
a free port and prints its actual URL. Pass that URL with the client's
--endpoint option.
Certificate trust is required by default. The separate server/client stores
under artifacts\gms-pki are retained for administration; trust each peer's
application certificate in the other application's trusted peer store.
--demo-trust is an explicit acceptance-only exception: the server actually
binds the numeric IPv4 loopback address, the client rejects remote endpoints,
and both retain encryption. The client requires Basic256Sha256
SignAndEncrypt and certificate-domain checks. No credentials are embedded.
The default client is passive. To acknowledge one result only, specify its exact system and result and confirm the state change:
dotnet run --project samples\GMS\GmsClient\GmsClient.csproj -f net10.0 -- `
--system Gms1 --acknowledge Gms1-F-0000 --confirm-acknowledgement --seconds 0 --demo-trust
Acknowledgement does not run a job or change a correction. Sensor warnings are observed, never implicitly acknowledged. Their inputs are actual additional environmental measurements, not primary-probe qualification.
Bounds and cleanup
--help lists every bound. The server runs for at most 120 seconds and owns
one or two independent providers/stores, each limited to 256 results and
8 MiB. Each instance permits one metadata handle and one file transfer.
The client queries at most 16 IDs per instance, preserves raw DataValue
quality/timestamps, bounds every observation by time/count/bytes and releases
its subscriptions. Use --count 32 to capture changing advanced measurements
beyond the initial inventory (the notification cap is 64). Downloads return
bounded ByteString values in memory; no result file is written to disk.
With an advanced local server, add
--system Gms1 --download --verify-cleanup --demo-trust to demonstrate a
missing-result error, file-byte-limit refusal, cancellation after a remote
file read and cancellation after monitored-item creation. A subsequent
download and metadata read verify reuse of the single-handle capacity
without waiting for expiration. Other failures return a nonzero exit code;
the client does not silently retry acknowledgement. Ctrl+C awaits cleanup.
Both projects use AppTargetFrameworks and are nonpackable. NativeAOT is
selected inside each application project only, conditionally for net10:
dotnet publish samples\GMS\GmsServer\GmsServer.csproj -c Release -f net10.0 -r win-x64
dotnet publish samples\GMS\GmsClient\GmsClient.csproj -c Release -f net10.0 -r win-x64
Do not pass a graph-wide PublishAot property. Execute the published
applications with the same options to exercise the real transport.
On Windows, the PowerShell 7 GmsClient\Test-GmsSamplePair.ps1 acceptance harness takes
-ServerExecutable, -ClientExecutable and -EvidenceDirectory.
Use -Advanced -AllChecks for positive, refusal and cancellation checks;
add -AssertNative for published NativeAOT binaries. It verifies the actual
loopback listener, natural exits, subscription/handle reuse and owned PKI
cleanup, and records exact commands, output logs and summary.json.