Scheduler: Scheduler information model
| Document number | Part number not confirmed |
|---|---|
| IEC designation | Part number not confirmed |
| Colloquially | Scheduler |
| Group | Utility |
The Scheduler information model is a released OPC UA model at version 1.05.02, published 2022-11-01, in the namespace http://opcfoundation.org/UA/Scheduler/. Its core-style version numbering suggests it is published as a numbered core part rather than as a companion specification, but we have not confirmed which number.
What is confirmed
There is a released, published information model whose namespace URI is http://opcfoundation.org/UA/Scheduler/, at version 1.05.02 with a publication date of 2022-11-01. It ships as a NodeSet2 file alongside every other released model, which means it can be loaded into a modelling tool, checked into a repository and served by any server that supports loading a nodeset. Those facts are solid, and they are the ones worth citing.
Why the number matters and why we do not have it
Companion specifications carry their own version lines, typically starting at 1.00 and moving in small steps. This model instead carries a four-part version in the same shape as a core release family with an errata level, which is the pattern used by the numbered core parts rather than by companion models. That is a strong hint that it is published as a numbered part in the core series. It is a hint, not a citation, and we could not establish which number it holds - so we describe it by namespace URI and version and leave the part number blank rather than filling it with something plausible.
What a scheduler model is for
The subject is representing scheduled activity in an address space: what is planned to happen, when, and in what order, exposed so it can be read and adjusted over OPC UA instead of through a proprietary planning interface. That makes it structurally adjacent to the job and result models in the sector companion specifications, which is also where most production systems currently express planned work. We are not restating this model's object type names on this page, because we have not read a current copy of the specification behind it.
How to check whether a server has it
Read the server's NamespaceArray and look for http://opcfoundation.org/UA/Scheduler/. If it is present, read the corresponding NamespaceMetadata object for the model version and publication date the server actually loaded. That two-step check is worth more than any part number, because it tells you what is on the machine in front of you rather than what a datasheet claims.
What it defines
| Concept | What it is |
|---|---|
| Namespace URI | http://opcfoundation.org/UA/Scheduler/ - the identifier to use in configuration, in a specification and when checking a server, in place of a part number. |
| Version and publication date | Version 1.05.02, published 2022-11-01. Both confirmed, and both stable enough to cite. |
| Core-style version numbering | A four-part version in the shape of a core release family plus errata level, rather than a companion model's own 1.00.x line. This is the evidence that it is a numbered core part. |
| Part number - not confirmed | We could not establish which number in the core series this model is published under, so we do not state one. Neither an OPC 10000-N nor an IEC 62541-N form is asserted here. |
| Delivered as a NodeSet2 file | Like every released model, so it can be loaded into a modelling tool or a server that supports nodeset loading without any special handling. |
| Subject matter | Representing planned and scheduled activity in the address space so it can be read and configured over OPC UA rather than through a proprietary planning tool. |
| Adjacent models | The sector job and result models - ISA-95 job control, the machinery job and result models - are where planned work is expressed in most production systems today. |
| How to detect it | Look for the namespace URI in NamespaceArray, then read the matching NamespaceMetadata for the version the server actually loaded. |
Do you need to read it?
Anyone who has found this namespace on a server and wants to know what it is, and anyone considering it as a target for scheduling data. For a specification, cite the namespace URI and the version - both confirmed - and leave the part number out until it has been checked.
Traps that trace back to this part
- Do not cite a part number for this model. The version numbering makes it look like a core part and we have not confirmed which one, so a number written into a document from here would be a guess wearing a citation's clothes. The namespace URI and version are the safe identifiers.
- Version 1.05.02 is this model's own version, not an alignment with the core release family. Core is at 1.05.07, and the coincidence of shape does not mean the two track each other - do not conclude that a 1.05.07 server implies a current Scheduler model.
- Support has to be detected, not assumed. Read NamespaceArray for the namespace URI and NamespaceMetadata for the loaded version, because a vendor claim about scheduling support may refer to a proprietary interface or to a sector job model rather than to this one.
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.