Companion specification · Tier 2

MTConnect

Version-
Published-
SectorMachine tool data

MTConnect is a separate machine-tool data standard with its own agent architecture, and a nodeset exists mapping it into OPC UA. The honest position: that nodeset carries no Model element and looks unmaintained, and new European machine-tool projects target MachineTool plus Machinery instead.

Where it sits in the stack

Nominally a bridge between the two standards. MTC is a registered capability code, so servers may claim it, but MachineTool has become the mainstream path.

The types that matter

TypeWhat it carries
(no Model element in the released nodeset)The nodeset we examined carries no Model element, which is the old pre-Models-element style and a maintenance signal in itself. We have not verified a type inventory.

Using it on a real machine

  1. Prefer MachineTool for new workMachineTool at 1.02.0 plus the Machinery building blocks is what new machine-tool projects target, and gives you a much richer OEE surface.
  2. Check the capability code if you meet itMTC is registered, so a server may claim it. Browse to see what is actually there.
  3. Treat MTConnect and OPC UA as complementaryThey are different standards with different architectures - MTConnect is agent-based, read-oriented and XML over HTTP. In a mixed shop you may well run both.

What it gives you for OEE

For machine-tool OEE, use MachineTool. Its ProductionStatisticsType, production state machines and condition classes are a far better foundation than anything you would get from this mapping, and they are actively maintained.

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

  • The released nodeset has no Model element and appears unmaintained. That is a strong signal.
  • MachineTool plus Machinery has largely displaced this mapping in new European projects.
  • MTConnect itself is a live standard - it is the OPC UA mapping whose state is questionable, not MTConnect.
Verify before you rely on this: The maintenance state of this mapping is genuinely unclear to us. The nodeset we examined lacked a Model element. Confirm the current status of the OPC UA to MTConnect companion arrangement with the relevant organisations before designing around it.

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