Powertrain
| Version | 1.0.0 |
|---|---|
| Published | 2024-11 |
| Sector | Powertrain manufacturing |
The powertrain model, published in 2024, notable for shipping its own IRDI dictionary alongside the information model - the same semantic-identifier approach PA-DIM uses, which points at where cross-industry semantics are heading.
Where it sits in the stack
Built on the Machinery building blocks, and it ships a dictionary namespace using IRDI identifiers to tie model elements to external semantic definitions.
The types that matter
| Type | What it carries |
|---|---|
(type inventory not confirmed) | We have not verified the type inventory. The model ships an accompanying IRDI dictionary namespace. |
Using it on a real machine
- Note the dictionaryThe IRDI dictionary is the interesting part: it links model elements to external semantic definitions rather than relying on names alone.
- Map the Machinery layerIdentification and state come from the building blocks underneath.
- Consider the semantic layer for cross-plant workIRDI-tagged elements are easier to reconcile across plants and vendors than name-matched ones.
What it gives you for OEE
Standard Machinery-layer OEE applies. The dictionary's real contribution is reconciliation: comparing the same measure across plants and vendors is much less painful when both sides carry a semantic identifier rather than a hopeful name match.
Gotchas
- Ships its own dictionary namespace using IRDI identifiers - unusual and worth understanding.
- Published 2024, implementation early.
- The semantic-identifier approach here mirrors PA-DIM's, which is the better-documented example.
Once the machine speaks a companion spec, the OEE mapping is portable across vendors, which is the point at which analytics stops being a per-machine project.
See Jemba →Last verified 7 September 2026 against OPC UA 1.05.07. Version and publication date read from the released nodeset. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.