The OPC UA plugin populates asset identity from the server nameplate (BuildInfo plus the DI Model / SerialNumber / HardwareRevision / SoftwareRevision) but never captures the device order code (orderable part number).
Two gaps:
AssetIdentity has no field for it. model holds the product designation (e.g. CPU 1505SP F), which is distinct from the order code. AAS separates ManufacturerProductDesignation (designation) from ManufacturerOrderCode (order code).- The order code is often exposed as a vendor node named
OrderNumber outside the standard DI nameplate namespace (for example some CPUs place it in a vendor namespace rather than the DI namespace), so a DI-namespace-only read misses it. Values may also be fixed-width padded.
Proposal
- Add a typed
order_code identity field (AAS ManufacturerOrderCode), wired through JSON, merge with per-field provenance, and manifest/CSV import.
- Read the
OrderNumber nameplate node by BrowseName across namespaces so vendor-namespace variants are picked up; trim padding on that field.
Acceptance
Connecting an OPC UA device that exposes an order-code nameplate node fills identity.orderCode; the field round-trips through JSON, merges with per-field provenance, and can be set from a manifest/CSV entry.
The OPC UA plugin populates asset identity from the server nameplate (BuildInfo plus the DI Model / SerialNumber / HardwareRevision / SoftwareRevision) but never captures the device order code (orderable part number).
Two gaps:
AssetIdentityhas no field for it.modelholds the product designation (e.g.CPU 1505SP F), which is distinct from the order code. AAS separatesManufacturerProductDesignation(designation) fromManufacturerOrderCode(order code).OrderNumberoutside the standard DI nameplate namespace (for example some CPUs place it in a vendor namespace rather than the DI namespace), so a DI-namespace-only read misses it. Values may also be fixed-width padded.Proposal
order_codeidentity field (AASManufacturerOrderCode), wired through JSON, merge with per-field provenance, and manifest/CSV import.OrderNumbernameplate node by BrowseName across namespaces so vendor-namespace variants are picked up; trim padding on that field.Acceptance
Connecting an OPC UA device that exposes an order-code nameplate node fills
identity.orderCode; the field round-trips through JSON, merges with per-field provenance, and can be set from a manifest/CSV entry.