Companion specification · Tier 2

Mining (General, TransportDumping, Conveying)

Version1.01.0
Published2025-10
SectorMining equipment

The mining equipment family - general types plus transport, dumping and conveying models. One of the fastest-growing families in 2026, which reflects real demand for standardised equipment data in mining.

Where it sits in the stack

Built on the Machinery building blocks and the Device Information Model. The members are separate namespaces for different equipment classes.

The types that matter

TypeWhat it carries
(type inventory not confirmed)Several distinct namespaces with type inventories we have not verified. Browse the released nodesets.

Using it on a real machine

  1. Identify which family members applyGeneral, transport and dumping, and conveying are separate models. Browse for each.
  2. Map the Machinery layerEquipment identification and state come from the building blocks underneath.
  3. Expect mobile-equipment complicationsMining equipment is often mobile, intermittently connected and geographically dispersed. Design the collection path for that before worrying about the model.

What it gives you for OEE

Conveying and continuous transport measure throughput rather than parts, so performance is a rate. Availability works through the Machinery item state where implemented. The harder problem in this sector is usually connectivity rather than modelling - intermittent links mean store-and-forward, and OPC UA does not buffer for you.

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

  • Several separate namespaces grouped here for convenience. Browse for each.
  • Rapidly evolving through 2025 and 2026, so implementations are early.
  • Mobile and intermittently connected equipment changes the collection architecture more than the model does. Plan store-and-forward.
Verify before you rely on this: Fast-moving family with several members added recently. 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.
Related models

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