Companion specification · Tier 2

FDI5 / FDI7

Version1.1
Published2017-07-14
SectorDevice configuration

The Field Device Integration models, and the notable fact is the date: these nodesets are frozen at 2017 and have not moved since. FDI addresses device configuration and parameterisation rather than runtime data, and it is a different concern from the device information models.

Where it sits in the stack

Related to the Device Information Model and to FDT. The FDI, FDIC and FDT capability codes are all registered, so a server may claim any of them.

The types that matter

TypeWhat it carries
(type inventory not confirmed)We have not verified the type inventory of these frozen nodesets.

Using it on a real machine

  1. Understand the scopeFDI is about configuring and parameterising field devices, not about collecting runtime data. If you want runtime values, DI or PA-DIM is your model.
  2. Check the capability codesFDI, FDIC and FDT are registered capability codes. A server claiming one tells you what tooling it expects.
  3. Note the freezeNodesets unchanged since 2017. Confirm the current state of the wider FDI work with the relevant organisation if it matters to a design.

What it gives you for OEE

Nothing directly. Device configuration is not production data. It matters to OEE only in that a misconfigured device causes downtime, and configuration management is how you avoid that.

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

  • Nodesets frozen at 2017. Treat anything you read about their current state with suspicion, including this page.
  • Configuration, not runtime data. A common misunderstanding.
  • FDI, FDIC and FDT are distinct capability codes covering related but different work.
Verify before you rely on this: These nodesets have not been revised since 2017 and we have not verified the current state of the wider FDI programme or the models' type inventories. Confirm before designing around them.
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