TL;DR
OPC UA and MQTT do different jobs. OPC UA reads and describes data from industrial equipment, while MQTT moves messages between many systems through a broker, and many plants use both. Whichever carries the data, it needs production context before anyone can act on it, and that's the MES's job. See how TrakSYS connects your plant.
Key takeaways:
- OPC UA is built for talking to equipment. It gives other systems a standard way to read machine data, with its structure and meaning attached.
- MQTT is built for sharing data widely. Devices and systems publish messages to a broker, and every system that subscribes receives them.
- Many plants don't have to choose. OPC UA often sits close to the equipment, and MQTT shares data across systems and sites.
- Context turns either one into something useful. A value from a machine rarely arrives knowing which order, product, or line it belongs to. The MES adds that.
What is OPC UA?
OPC UA is an industrial standard that enables software to read data from machines and controllers consistently. Along with each value, it describes what the value is and where it comes from.
That makes it a common choice for collecting data straight from equipment such as PLCs, machines, and SCADA systems.
What is MQTT?
MQTT is a lightweight publish/subscribe messaging protocol. A device or system publishes a message to a broker, and any system that has subscribed to that topic receives it. The sender doesn't need to know who's listening.
That design suits plants with many data sources and many consumers, from edge devices on the line to systems at other sites. Our post on how MQTT and TrakSYS work together goes further.
What's the difference between MQTT and OPC UA?
| OPC UA | MQTT | |
|---|---|---|
| What it's for | Reading and describing equipment data in a standard way | Moving messages between many devices and systems |
| How data moves | A system connects to an OPC UA server on or near the equipment and asks for the values it needs | Senders publish to a broker, and subscribers receive what they signed up for |
| What it carries | Values plus their structure and meaning | Whatever the sender puts in the message, so its meaning depends on how the message is structured |
| Where it usually sits | Close to the equipment: PLCs, machines, and SCADA | Between systems and sites: edge devices, the MES, and business systems |
| Typical uses | Reading machine states, counts, and process values | Sharing data from many sources with many systems at once |
Do you have to choose?
Usually not. Plants commonly use OPC UA close to the equipment and MQTT to share data across systems and sites.
The harder part is often agreeing on how systems even talk. In our 2026 State of the Manufacturing Industry report, 41% of OT and IT leaders named a lack of standard protocols or interfaces as a challenge when integrating new systems. Picking protocols on purpose, rather than one project at a time, is part of bringing IT and OT together.
Where does the MES fit?
Whichever protocol carries it, raw data needs production context before it's useful: the order, the product, and the line it came from. That's the job of the MES: turning readings into information your teams can act on.
TrakSYS Connect natively supports OPC UA, MQTT, REST, and SQL, and also supports Sparkplug B over MQTT. Additionally, the platform enables structured, two-way messaging with business systems over your own broker, meaning you can:
- Write a process order acknowledgment back to a business system.
- Publish a quality result for other systems to use.
- Receive inbound order data.
What should you ask before choosing a protocol?
- What data do you need, and from which equipment?
- Which systems need that data: the MES, ERP, quality, or something else?
- How many sites will share it?
- Who owns and runs the broker?
- What context does the data need before anyone can use it?
If you're working out how your plant's equipment and business systems should share data, an advisor can talk it through with you. Speak with an advisor.
FAQs
For parts of the job, sometimes, but many plants use the two together. MQTT is strong at sharing messages across many systems, while OPC UA is built to read and describe equipment data. The better question is what each part of your data path needs.
That depends as much on the whole system around it as on the protocol. Ask how the broker is run and secured, what happens when a connection drops, and how the data lands in the records your quality team relies on.
Not always. Many devices and systems already speak MQTT, and smart devices can bring data from other machines and sensors into TrakSYS.
Related Blog Posts


Let’s Build Your Plan
We’ll help you create the right configuration—today and for the future.







.avif)
.avif)





