Part 200: Industrial Automation (IA)
| Document number | OPC 10000-200 - also cited as OPC 40001-1 |
|---|---|
| IEC designation | IEC 62541-200 - publication not confirmed |
| Colloquially | Part 200 |
| Group | Domain |
Industrial Automation is a base-layer information model that sector companion specifications build on, in the namespace http://opcfoundation.org/UA/IA/. Its document identity is genuinely ambiguous: it is cited both as OPC 10000-200 and as OPC 40001-1, and there are two version numbers in circulation. We present that as an open question.
The dual identity, laid out
The same model is cited two ways. In some material it appears as OPC 10000-200 - a core-series part number - with the online reference for it published at version 4.00. In other material the same model is called OPC 40001-1, Industrial Automation, which is a companion-specification series number. Meanwhile the released nodeset for the namespace http://opcfoundation.org/UA/IA/ carries version 1.01.4 with a publication date of 2025-05-23. So there are two document numbers in two different series and two version numbers that do not correspond.
The possible readings, none of them confirmed
One reading is that the model was originally published as the companion specification OPC 40001-1 and has since been renumbered into the core series as Part 200, with older citations lingering. A second is that the two numbers refer to related but distinct documents - a base companion specification and a core part that incorporates it. A third is that the version 4.00 on the reference site is a document or site-level version that has never been aligned with the nodeset's own model version. We have not established which of these is correct, and we are not going to pick one to make the page tidier.
What the model is for
Whatever it is called, its role in the stack is clear enough: it is a base layer, sitting above the device information model and below the sector-specific machinery models, supplying types those models reuse rather than each redefining. That makes it a dependency rather than a destination. Implementing it by itself gives a server very little that an integrator can use; its value is that a machine-tool, robotics or metal-forming model can assume it and stay smaller. We are not restating its type names on this page, because we have not read a current copy of the document that defines them.
What it defines
| Concept | What it is |
|---|---|
| Namespace URI | http://opcfoundation.org/UA/IA/ - the unambiguous identifier for this model, and the one to use in configuration and in a specification. |
| Nodeset version | The released nodeset for the IA namespace is at version 1.01.4, published 2025-05-23. This is the version a server reports through NamespaceMetadata. |
| Reference version 4.00 | The online reference documentation for this model is published at version 4.00, which does not correspond to the nodeset's 1.01.4. We cannot reconcile the two. |
| Cited as OPC 10000-200 | A core-series part number, which would make it Part 200 and put it alongside the device information model in the elevated range. |
| Cited as OPC 40001-1 | A companion-specification series number for the same model, under the title Industrial Automation. Both citations appear in current material. |
| Role as a base layer | Supplies common types that sector machinery models reuse. A dependency of those models rather than something an integrator targets directly. |
| What we are not stating | No object type names, no conformance units and no claim about which document number is correct. We have not read a current copy of the defining document. |
| How to detect it | Look for the namespace URI in NamespaceArray and read the version and publication date from NamespaceMetadata. Two checkable values beat any part number. |
Do you need to read it?
Modellers building on the machinery stack, who need to know what their model can assume, and anyone reconciling two datasheets that appear to cite different standards. If a specification names one of the two document numbers, rewrite the requirement around the namespace URI and version before it becomes an argument at acceptance.
Traps that trace back to this part
- There are two document numbers and two version numbers in circulation for one model. Writing either part number into a contract invites a dispute about whether a device complies. Specify the namespace URI http://opcfoundation.org/UA/IA/ and a minimum model version instead, both of which can be read off a running server.
- Do not assume two vendors citing the two different numbers mean different things - and do not assume they mean the same thing either. Ask each of them which namespace URI they publish and at what version, and compare those answers rather than the citations.
- This is a base layer, so support for it is close to meaningless on its own. What matters is which sector model on top of it a device implements and which of that model's optional parts are populated. A server loading the IA namespace and nothing above it gives an integrator almost nothing to read.
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.