Companion specification · Tier 2

IJT Base

Version1.01.0
Published2025-10-06
SectorIndustrial joining technology

The base model for industrial joining technology, refreshed in October 2025 - one of the more actively maintained sector families. It underpins the tightening model and provides the joining-process structure they share.

Where it sits in the stack

Built on the Machinery building blocks and the Device Information Model, and it sits under IJT Tightening.

The types that matter

TypeWhat it carries
(type inventory not confirmed)We have not verified the full type inventory. Browse the released nodeset.

Using it on a real machine

  1. Establish which IJT members are presentBase plus Tightening is the usual pairing. Browse for both.
  2. Treat joining results as quality dataA tightening result is a measured outcome on a specific joint - torque and angle - which is quality evidence rather than a process value.
  3. Map traceability earlyJoining data is frequently required for traceability, so establish the part and joint identification path before designing the collection.

What it gives you for OEE

Quality is the strong suit: a tightening result per joint, with measured values, is unusually good quality evidence. Availability and counts come from the Machinery layer. In safety-critical assembly this data is often a compliance requirement, which changes the retention conversation.

Try it free: No free public server exposes this model as far as we know. To see it you need a machine that implements it or a vendor demo. If you find a public endpoint, tell us and we will add it.

Gotchas

  • Actively maintained - Base and Tightening were both revised in October 2025. Check versions.
  • Result volume can be high: every joint on every part. Plan storage and retention before you start.
  • Traceability requirements may dictate retention periods well beyond normal analytics needs.
Verify before you rely on this: We have not verified the type inventory. The type inventory on this page is deliberately short. We list only type names we are confident of and would rather publish five correct ones than twelve with four wrong. Browse a real server or the released nodeset for the complete list.

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.

Free download
OPC UA Machine Data → OEE Mapping Kit
Which nodes to subscribe to, how they become Availability, Performance and Quality, and which companion specification already gives you the answer, so you stop inventing tags.
Get the free mapping kit →
Free, no course, no login