Siemens SINUMERIK machine monitoring, over its own OPC UA server
Siemens didn't wait for a third party to build connectivity into SINUMERIK — Access MyMachine / OPC UA ships from Siemens itself, on the control, for SINUMERIK ONE, 840D sl, and 828D. ThingConnect reads it the same read-only way it reads every OPC UA source.
Access MyMachine / OPC UA: Siemens' own server
Access MyMachine / OPC UA is Siemens' own OPC UA server software for the SINUMERIK line — not a bolt-on gateway box, and not a third-party translation layer. It runs on the control (or alongside SINUMERIK Operate) and exposes the control's data as a standard OPC UA address space that any compliant client, including ThingConnect's gateway, can browse and subscribe to.
It's licensed per control and needs a minimum software version to activate: SINUMERIK Operate 6.13 or later on SINUMERIK ONE (with AMM version 4.8+), Operate 2.6 or later on 840D sl, and Operate 4.5 or later on 828D. Where a fleet runs older Operate builds, that's exactly the kind of thing the fleet survey catches before a rollout is quoted.
How a SINUMERIK control gets connected
The physical connection point differs by control family, which is why "does it have OPC UA" isn't quite the same question as "is it reachable right now":
| Control | Where OPC UA is reachable |
|---|---|
| SINUMERIK 828D | Over the X130 Ethernet interface, once the server is licensed and activated. |
| SINUMERIK 840D sl | Runs alongside SINUMERIK Operate itself; with a Thin Client setup, reachable over the NCU's X120 and X130 interfaces. |
| SINUMERIK ONE | Same Access MyMachine / OPC UA server, current-generation licensing and activation flow. |
No OPC UA licence active? A SINUMERIK control without Access MyMachine activated doesn't stop it from joining the dashboard — it connects the same way any control without a modern data interface does, through a digital I/O connection, with honest labeling on the difference in depth.
Siemens and umati — standardizing what gets published
Siemens is one of the lead contributors behind umati ("universal machine technology interface"), the OPC Foundation-backed initiative that standardizes what a machine tool should publish over OPC UA — machine state, program identity, overrides, counts — in a predictable shape regardless of who built the control. That involvement is part of why SINUMERIK's OPC UA implementation is substantive rather than a minimal checkbox server: Siemens helped write the specification it's implementing.
The honest caveat runs the other way: MTConnect, the machine-tool industry's other open standard (see how MTConnect works), has no Siemens-built path onto a SINUMERIK control. Getting MTConnect data out of a Siemens machine means installing a third-party adapter between the control and an MTConnect agent — workable, but not the zero-extra-software path OPC UA already is here.
Questions
Frequently asked questions
If it's a SINUMERIK ONE, 840D sl, or 828D, yes — Siemens ships its own Access MyMachine / OPC UA server for all three. It needs a specific minimum software version (SINUMERIK Operate 6.13+ on SINUMERIK ONE, 2.6+ on 840D sl, 4.5+ on 828D) and a licence to activate, both of which we confirm per machine during the fleet survey rather than assuming.
It varies by control. On an 828D, the server is reachable over the X130 Ethernet interface once licensed and activated. On an 840D sl, it runs alongside SINUMERIK Operate itself, and — where a Thin Client is used — is reachable over the NCU's X120 and X130 interfaces.
Not as a Siemens-built option. SINUMERIK's own connectivity investment has gone into OPC UA — MTConnect access on a SINUMERIK control requires a third-party adapter sitting between the control and an MTConnect agent, not a Siemens-shipped agent the way OPC UA is.
Yes. OPC UA connections for monitoring are read-only subscriptions to the address space the control publishes — the protocol itself has no channel for a client to write back program or parameter changes through this kind of session. Sessions are encrypted and certificate-trusted, and machines only ever talk outbound to a gateway inside your firewall.