Companion specification · Tier 2

IO-Link

Version-
Published-
SectorFieldbus and sensor integration

The IO-Link model, which brings sensor and actuator level data up into OPC UA. IO-Link is enormously widely deployed at the sensor level, and IODD device descriptions carry the semantics - which makes this a bridge between two description worlds rather than a machine model.

Where it sits in the stack

Built on the Device Information Model. IODD files are the IO-Link world's own device description format, and reconciling them with OPC UA information models is the substance of this integration.

The types that matter

TypeWhat it carries
(type inventory not confirmed)We have not verified the type inventory. The IOLINK capability code is registered.

Using it on a real machine

  1. Check the capability codeA server claiming IOLINK is exposing IO-Link masters or devices. Read the ServerCapabilities first.
  2. Understand where the semantics liveIODD files describe IO-Link devices. Whether and how that semantic content surfaces in the OPC UA address space is the key question for your integration.
  3. Expect a lot of nodesSensor-level data multiplies fast. An IO-Link master with many ports, each with a device with many parameters, produces a large address space - filter before you subscribe.

What it gives you for OEE

Sensor-level data rather than production data. It contributes to condition monitoring and to diagnosing a cause: a sensor reporting a fault explains a stop that would otherwise be unattributed. Not a source of counts or state.

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

  • Node count explodes at sensor level. Filter your browse and be selective about subscriptions.
  • IODD is a separate description format. How its semantics surface in OPC UA is the real question.
  • Sensor diagnostics explain downtime; they do not measure production.
Verify before you rely on this: We have not verified the type inventory or how IODD semantics are currently surfaced. 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