OPC UA data collection
OPC UA is industrial automation's common language — a secure, browsable data interface that newer CNC controls, PLCs, and ancillary equipment increasingly ship with. ThingConnect reads it as a client, the same way it reads everything else: through one gateway, into one dashboard.
How OPC UA works
Equipment with OPC UA runs a server: a structured, browsable tree of everything the builder chose to expose — machine state, program identity, counts, overrides, temperatures. A client connects, browses that tree, and subscribes to the items it needs; the server then pushes changes as they happen rather than being polled blind.
Unlike older industrial protocols, security is part of the design: sessions are encrypted, trust is certificate-based, and access can be restricted per user. For a monitoring connection, the client subscribes read-only — nothing writes to the machine.
OPC UA on CNC machines
On the machine-tool side, OPC UA matters for two reasons. Newer controls from several major makers ship or offer an OPC UA server directly on the control. And the industry's umati initiative ("universal machine technology interface") builds on OPC UA to standardize what a machine tool publishes — so a conformant machine reports state, program, overrides, and counts in a predictable shape regardless of brand.
| Where OPC UA fits | What to expect |
|---|---|
| Newer CNC controls | A server on the control itself; depth depends on the builder's implementation — from minimal to umati-conformant. |
| PLCs and ancillary equipment | Washers, gauges, compressors, and cells often expose OPC UA — the same gateway brings them onto the plant dashboard. |
| Older CNCs | Generally absent. Those machines connect natively — like FANUC over FOCAS — or through digital I/O instead. |
The pattern across the fleet: FOCAS where controls speak it natively, MTConnect or OPC UA where builders ship them, digital I/O for the veterans. Each machine on its deepest available connection — one dashboard over all of it.
Frequently asked questions
What is OPC UA?
OPC UA (Open Platform Communications Unified Architecture) is the general-purpose industrial data standard: equipment runs an OPC UA server exposing its data as a browsable address space, and clients — like a monitoring gateway — read from it. It spans CNCs, PLCs, robots, and sensors, with security (encryption, authentication) built into the protocol itself.
Do CNC machines support OPC UA?
Increasingly, on newer controls — several major control makers now ship or offer an OPC UA server, and the machine-tool industry's umati initiative standardizes what a machine tool should publish over it. Older controls generally do not have it, which is why a realistic fleet uses OPC UA for some machines and other methods for the rest.
What data does a CNC expose over OPC UA?
Whatever the builder put in the server's address space — that is both the power and the caveat. A umati-conformant machine publishes a defined set: state, program, overrides, counts, tool data. A minimal implementation may publish only a handful of items. We browse each server during the fleet survey so the coverage per machine is known up front.
Is OPC UA secure enough for a production network?
OPC UA is one of the few industrial protocols with security designed in: encrypted sessions, certificate-based trust, and per-user authentication. Combined with our outbound-only gateway architecture — machines never touch the internet — it is typically the easiest connection method to take through an IT review.
