IJT Tightening
| Version | 2.00.1 |
|---|---|
| Published | 2025-10-06 |
| Sector | Tightening systems |
The tightening systems model, at version 2.00.1 as of October 2025 - a second-generation model in an actively maintained family. It describes tightening tools and, more usefully, their results.
Where it sits in the stack
Built on IJT Base, which in turn builds on the Machinery building blocks.
The types that matter
| Type | What it carries |
|---|---|
(type inventory not confirmed) | We have not verified the full type inventory. Browse the released nodeset. |
Using it on a real machine
- Confirm you are on the 2.x lineThis is a second-generation model. Read the version from the server.
- Design result collection deliberatelyEvery joint on every part produces a result. On an assembly line that is a lot of data, and it needs a retention decision before it starts.
- Link results to part identityA torque result is only useful for traceability if you know which part and which joint it belongs to. Establish that path first.
What it gives you for OEE
Excellent quality data - measured torque and angle per joint, with a pass or fail. Availability and cycle counts come from the Machinery layer or the line controller. In regulated assembly this is often the primary reason for the integration, with OEE a secondary benefit.
Gotchas
- Second-generation model at 2.00.1. Do not assume a 1.x client works.
- Result volume is high by design. Retention and storage need deciding up front.
- Traceability requirements often drive retention well beyond analytics needs.
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.