Conceptual equipment illustration.
OPC UA vs MQTT is not always an either-or choice. OPC UA includes information modelling and communication services, with client-server and PubSub options. MQTT is a publish/subscribe messaging protocol commonly used through a broker. OPC UA PubSub can use MQTT as its transport, so one system can use both.
In machine retrofit and modernization, choose the data contract and operating behaviour before selecting a protocol label.
Compare the Functions You Need
The OPC Foundation’s MQTT mapping explains MQTT messages with application-defined payloads and the OPC UA DataSet encodings that can be carried through that route. The broker can relay the message without understanding its industrial meaning.
| Requirement | Decision to make |
|---|---|
| Discover equipment data and its structure | Which information model and services expose it? |
| Distribute updates to several destinations | Which publishing architecture and broker/transport are used? |
| Interpret values consistently | Where are units, quality, timestamps and schema defined? |
| Recover after disconnect | What is retained, replayed or dropped by this implementation? |
| Permit a control write | Which authenticated service and authorization allows it? |
Client-server subscriptions, direct PubSub and brokered messaging are different arrangements. Do not compare one OPC UA client-server example with every possible MQTT or OPC UA deployment as if they shared the same behaviour.
Agree the Payload, Not Just the Connection
For MQTT data, a topic name and JSON number are not a complete machine record. Define identity, schema version, units, source time and data quality. Establish what happens when the payload changes.
OPC UA information models can supply structured semantics, but the implementation still needs consistent mapping. A connected client does not prove that every machine exposes the required metadata.
The legacy-machine connectivity scope addresses mapping old machine signals to useful data. For downstream dashboards, coordinate the contract with the HMI and SCADA system.
Delivery Features Need an Application Test
MQTT delivery settings, sessions and retained messages affect message behaviour, but they do not by themselves create a complete long-term historian. Test duplicates, missing updates, destination restarts and broker/server unavailability.
For events or counts, decide how the application recognizes a repeated message and distinguishes it from a new event. Preserve source identity and timing through reconnection.
Network access and security need configuration in either architecture. Define certificates or credentials, permitted clients and write permissions for the actual implementation. The MES, ERP and SCADA role comparison helps identify which application owns each record and operating action.
Specify a Working Path
A useful integration drawing names the source, mapping layer, transport, destination and failure response. “Supports OPC UA/MQTT” is only an initial compatibility statement until that path is tested.
Discuss the industrial data route with Motionwell, including who consumes the data and what needs to happen during a connection failure.