Part 22: Base Network Model
| Document number | OPC 10000-22 - number not confirmed |
|---|---|
| IEC designation | IEC 62541-22 - number not confirmed |
| Colloquially | Part 22 |
| Group | Core |
We have not confirmed this one. Our understanding is that Part 22 is the Base Network Model and that it is grouped with the core parts, but neither the number nor the title has been checked against a current source, so this page describes the position rather than the content.
What we are confident about
The core part numbering continues past the well-established block that ends at Part 21, and there is a base network model in the standard's orbit whose job is to describe a device's network attachment - interfaces, addresses and the connections between them - inside the address space, so that network configuration becomes readable and configurable over OPC UA rather than through a vendor web page. What we have not confirmed is that this document is numbered 22, or that Base Network Model is its exact title.
Why we are not filling this page in
A part number and a title are the two facts a reader is most likely to copy into a specification, a tender document or a purchase order, where a wrong number costs somebody real time. We would rather ship a page that says we do not know than one that reads authoritatively and is wrong. Nothing on this page should be cited, and we have deliberately not listed object type names for a document we have not read.
What to use instead, today
If what you actually need is network configuration exposed over OPC UA, there are confirmed routes. PubSub carries its own transport and connection configuration as an information model, including the datagram connection parameters, quality-of-service category and Ethernet addressing used for time-sensitive networking. The UAFX parts define the network and connection model for field-level exchange. And several sector companion models - notably the PROFINET and IO-Link families - describe network topology and device attachment for their own domains. Those are the documents to cite.
What it defines
| Concept | What it is |
|---|---|
| The number - not confirmed | We believe this document sits at 22 in the core series, which would make it OPC 10000-22 and IEC 62541-22. We have not verified either form. |
| The title - not confirmed | Base Network Model is our best understanding of the title. It may be phrased differently, and we are not treating our version as authoritative. |
| The grouping | Our understanding is that it is classified with the core parts rather than as an access-type or utility part. Also unconfirmed. |
| The subject matter | Describing a device's network attachment in the address space - interfaces, addresses and the links between them - so network state is discoverable over OPC UA. |
| What we are not stating | No object type names, no BrowseNames, no conformance units and no version. We have not read a current copy, and inventing them would be worse than leaving them out. |
| Confirmed alternatives - PubSub | Part 14 carries connection and transport configuration as a browsable model, including datagram parameters and the quality-of-service mapping used for TSN. |
| Confirmed alternatives - UAFX | The 80-series defines the field-exchange network and connection model, which is the relevant place for controller-to-controller network configuration. |
| Confirmed alternatives - sector models | The PROFINET and IO-Link companion model families describe network topology and device attachment within their own domains, and they are in production use. |
Do you need to read it?
Anybody about to write a part number into a document. If you are specifying network modelling over OPC UA, cite Part 14, the UAFX parts or a sector companion model, all of which are confirmed, and treat this page as a marker that there is something in the low twenties we have not pinned down.
Traps that trace back to this part
- Do not cite Part 22 or IEC 62541-22 in a contract, tender or acceptance test on the strength of this page. Confirm the number and the title against the publisher's own current reference documentation first.
- Do not conflate a base network model with the network configuration already defined elsewhere. Part 14 owns PubSub connection and transport configuration, and the UAFX parts own field-exchange networking. A requirement aimed at either of those should name them directly.
- A vendor claiming support for a part number in the low twenties is worth a follow-up question. Ask which namespace URI their model publishes and what version it is at, because a namespace URI and a version can be checked on a running server and a part number cannot.
Last verified 7 September 2026 against OPC UA 1.05.07. The specification parts themselves are published by the OPC Foundation. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.