MTConnect data collection
MTConnect is the machine-tool industry's open, read-only data standard — one common format for machine state, counts, and alarms regardless of who built the machine. Where your machines speak it, ThingConnect listens.
How MTConnect works
MTConnect has two moving parts. An adapter sits close to the control and translates its native signals; an agent collects those signals and publishes them over the network in a standard, self-describing format. On many newer machines both parts ship built in — the machine simply answers requests on a network port.
The standard is read-only end to end: it defines how machines publish data, and deliberately includes no way to command them. For monitoring, that is exactly the right shape.
Strengths — and the honest limits
| Strength | Limit |
|---|---|
| One format across brands — a mixed fleet reads consistently. | The builder decides what the agent publishes; some expose dozens of data items, some expose four. |
| Open and royalty-free — no per-machine protocol licence. | On some machines the agent itself is a paid option, or absent on older vintages. |
| Read-only by design — an easy yes from IT and maintenance. | Depth still varies: part counts and override positions are published on some implementations, missing on others. |
Our approach: MTConnect is one connection method among several, not a religion. Machines with rich agents connect through it; machines with deeper native interfaces — like FANUC over FOCAS — connect natively; legacy machines join over digital I/O. One dashboard, each machine on its best available connection.
What an MTConnect machine reports
A well-implemented agent typically publishes machine state (active/stopped/interrupted), program identity, part counts, feed and spindle data, and alarm conditions — enough to drive OEE, downtime tracking, and live floor views with no operator transcription. During the fleet survey we read each agent's actual device model, so you know per machine what will be measured rather than discovering gaps after go-live.
Frequently asked questions
What is MTConnect?
MTConnect is an open, royalty-free standard for reading manufacturing equipment data. A machine (or a small adapter beside it) runs an 'agent' that publishes its data — states, part counts, positions, alarms — in one common, read-only format that any monitoring system can consume.
Which machines have MTConnect?
It depends on the builder and the vintage. Some machine builders ship an MTConnect agent enabled on newer machines; on others it is a paid option, and on many older machines it is absent entirely. The practical answer comes from checking each machine's documentation or control screens — which is part of our fleet survey.
Is MTConnect better than a native controller connection?
Neither universally. MTConnect's strength is standardization across brands; its limit is that the builder decides what the agent publishes, and implementations range from rich to minimal. A native connection reads whatever the control exposes. In practice we use the deepest connection each machine supports, which keeps the whole fleet honest on one dashboard.
Does MTConnect allow anything to write to my machines?
No. MTConnect is read-only by design — the standard has no mechanism to send commands, change programs, or alter parameters. It is one reason monitoring over MTConnect is an easy conversation with IT and maintenance teams.