Woodworking
| Version | 1.02.0 |
|---|---|
| Published | 2025-06-01 |
| Namespace | http://opcfoundation.org/UA/Woodworking/ |
| Sector | Woodworking machinery |
The VDMA woodworking machinery model, and one of the more mature sector models - actively maintained and, unusually, testable for free on a public server. If you integrate panel saws, CNC routers or edgebanders, this is the model to ask your builder for.
Where it sits in the stack
Built on the Machinery building blocks and the Device Information Model, like the rest of the VDMA machinery family. Machine state and identification come from Machinery; the woodworking-specific structure sits on top.
The types that matter
| Type | What it carries |
|---|---|
WwMachineType | The woodworking machine, aggregating its state, identification and subunits. |
WwStateType | Woodworking machine state information. |
WwSubUnitType | A subunit of the machine, which is how multi-station equipment is described. |
Using it on a real machine
- Browse the umati sample server firstWoodworking is one of the models the umati sample server implements, so you can explore the real structure before you have a machine.
- Check the Machinery layer underneathIdentification, item state and operation mode come from the Machinery building blocks. Map those first; they are what makes the integration portable to a non-woodworking machine later.
- Model subunits separatelyMulti-station machines expose subunits. Collapsing them into one machine loses the ability to attribute a stoppage to a station.
- Ask for it at procurementEumabois and VDMA have pushed this model, so asking a builder to implement it is a reasonable and increasingly common request.
What it gives you for OEE
Among the better sector models for OEE. State comes from the woodworking state model plus the Machinery item state and operation mode underneath, which gives you planned-versus-unplanned separation. Counts depend on the builder's implementation - check for the Machinery operation counters. Subunit structure lets you attribute downtime to a station rather than a machine, which is where the useful improvement conversations start.
Gotchas
- Vendor implementations vary in how much of the optional structure they populate. Browse before promising a data point.
- Eumabois, the related model, is still pre-1.0 at 0.14 - do not confuse the two.
- Subunit modelling is where the value is and also where implementations differ most.
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.