PlasticsRubber Extrusion v2
| Version | 2.00 |
|---|---|
| Published | 2022-2023 |
| Namespace | http://opcfoundation.org/UA/PlasticsRubber/Extrusion_v2/ |
| Sector | Extrusion lines |
The second-generation extrusion model for the plastics and rubber family, published as its own namespace rather than as a revision of v1. An extrusion line is a set of cooperating units, and the model reflects that structure rather than treating the line as one machine.
Where it sits in the stack
Built on PlasticsRubber GeneralTypes and the core information model. The v2 namespace is separate from v1, so a client written against one does not silently work against the other.
The types that matter
| Type | What it carries |
|---|---|
ExtrusionLineType | The line as a whole, aggregating the units that make it up. |
ExtruderType | The extruder unit itself. |
Using it on a real machine
- Confirm v2 and not v1Read the ModelUri from the server. The v2 namespace is distinct, and a client bound to v1 node ids will not find v2 nodes.
- Map the line structure before individual valuesAn extrusion line is a set of units. Understanding the aggregation first makes the values meaningful and makes the integration portable to the next line.
- Establish where production counts liveContinuous processes count differently from discrete ones - length or mass rather than parts. Settle the unit of production before designing an OEE calculation.
What it gives you for OEE
Continuous production makes OEE genuinely different here. Performance is throughput against a rate rather than parts against a cycle time, and quality is often a length or mass of off-spec product rather than a reject count. Take state from the line and unit state where exposed, and expect to agree the definitions with production before the numbers mean anything.
Gotchas
- The v2 namespace is separate from v1. This is the single most important thing to check.
- Continuous production breaks part-count OEE assumptions. Decide on your unit of production first.
- Line-level and unit-level state can disagree - a line can be down while a unit runs. Model the hierarchy rather than picking one node.
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.