OPC UA MQTT Modbus Manufacturing Guide for Mixed-OEM Factories
A factory dashboard can show a plausible number while reporting the wrong engineering unit or displaying a stale reading. In Deloitte’s 2025 Smart Manufacturing and Operations Survey, only 45% of respondents reported using an architecture standard, underscoring the need to define how equipment data will be collected and interpreted before scaling an integration [1].
OPC UA MQTT Modbus manufacturing integration is the practice of collecting device data through native interfaces, preserving its meaning at the edge and delivering it to the systems that use it. For APAC manufacturers running mixed-OEM lines, that starts with a design the plant team can validate during a scheduled maintenance window.
Key Takeaways
Use Modbus to read legacy registers, OPC UA to access structured machine data and MQTT to distribute telemetry to multiple applications. Normalize readings at the edge, keep production control local and agree on recovery criteria before rollout. Prove data accuracy and outage behavior on a representative line before expanding across sites.
1. Start from the device and use case
Choose the device interface according to the signal, its consumer and the consequence of a late or incorrect reading. Start with one use case that plant staff can verify independently, such as energy monitoring or machine-state tracking.
Inventory each asset’s OEM, controller, firmware, interface and available documentation. For a legacy power meter, obtain the register map and confirm which readings the device exposes. For an OPC UA-enabled machine, browse the server and verify that the required nodes are accessible to the integration account. Record the expected update rate, maximum acceptable data age and handling of missing values for each signal.
Then agree on an acceptance baseline. An energy dashboard can be checked against the meter’s local display under known loads. A machine-state feed can be compared with operator-observed transitions. Keep interlocks and time-critical control in the controller or safety system, and scope the first integration to read-only access. This gives the plant a clear test boundary and limits the approvals needed for a pilot.
2. Explain each protocol’s role in OPC UA MQTT Modbus manufacturing
Modbus provides access to coils and registers, OPC UA exposes typed data and relationships, and MQTT distributes messages through a broker. Choose according to what the device exposes and what the receiving application needs [2] [3] [4].
| Dimension | Modbus | OPC UA | MQTT |
|---|---|---|---|
| Typical factory role | Read legacy meters, drives and I/O | Access structured controller or machine data | Distribute telemetry to multiple consumers |
| Exchange pattern | Client requests, device responds | Client/server reads and subscriptions, plus PubSub | Brokered publish/subscribe |
| Data representation | Coils and registers | Typed nodes, attributes and references | Application-defined payloads and topics |
| Meaning and units | Device register map supplies context | Information models can expose context | Payload schema carries context |
| Security | Verify whether the device supports Modbus Security | Configure secure endpoints, application trust and user permissions | Use TLS, client identities and broker topic permissions |
| First integration check | Confirm addressing, scaling and word order | Verify node identity, quality and timestamp handling | Verify reconnect, message delivery and duplicate handling |
OPC UA PubSub can also use MQTT as a transport. Confirm that both endpoints support the same message mapping before choosing that arrangement [3] [4].
3. Show an architecture that combines protocols
Use an edge gateway to collect device data and publish a consistent telemetry model. A typical line pairs a Modbus meter with an OPC UA-enabled machine, then uses MQTT to feed a historian and an integration service for the manufacturing execution system (MES).
The gateway converts meter registers into engineering values and carries forward OPC UA status and source timestamps when available. It assigns acquisition timestamps where the device supplies none and identifies their origin. Each telemetry record includes a stable asset and signal identifier, value, unit, timestamp and quality. The broker routes those records to subscribers [2] [3] [4].
Deployment pipeline
- Inventory. Use OEM register maps and an OPC UA browser to produce a verified signal list.
- Normalize. Use a versioned schema and known-value fixtures to validate units, timestamp origin and quality mappings.
- Connect. Use a staging MQTT broker with TLS and topic permissions to verify authorized delivery.
- Pilot. Compare historian readings with operator displays and run an approved outage drill to verify buffering and recovery.
- Roll out. Use version-controlled gateway configurations and a rollback checklist to commission each line against the same acceptance criteria.
4. Check operational and security constraints
Segment the integration by trust boundary and agree on what happens when a device, gateway or broker goes offline. Keep legacy Modbus inside its approved operational technology (OT) segment, and permit only the connections the gateway needs [2] [5].
Use signed and encrypted OPC UA sessions where supported, and document certificate renewal and trust-list ownership. For MQTT, authorize each publisher and subscriber by topic. Size the gateway’s persistent buffer against the approved outage window and message rate. Define how the gateway signals overflow, how subscribers deduplicate replayed events and when applications mark values as stale. Agree with each APAC site on which telemetry can leave the plant and where it may be stored [3] [4] [5].
Use ISO/IEC 27001 as a reference for information security management and CMMI as a reference for engineering process discipline. TMA’s company history records its achievement of ISO/IEC 27001 and CMMI Level 5. For the deployment itself, require evidence of access reviews, change approvals and a tested rollback [6].
5. Build an interoperability test list
Test each signal from the source device to the consuming application, including failures that can leave a plausible value on screen. Record the device firmware, gateway configuration, expected result and observed result so the plant can repeat each test after an upgrade.
- Value fidelity. Compare readings with known loads or operator displays. Check register offsets, signed values, word order, scaling and units.
- Data quality. Disconnect a source and confirm that its last reading becomes stale. Restart the OPC UA server and verify subscription recovery.
- Broker recovery. Interrupt the gateway’s uplink. Verify bounded buffering, replay and deduplication, and confirm that older events cannot overwrite newer state.
- Access and rollback. Verify that unauthorized writes and topic access are denied. Restore the previous configuration and confirm telemetry resumes without disrupting production.
Lessons learned from the field
An anonymized TMA Innovation robotics project faced fragmented data across machines, robots and enterprise systems. TMA integrated those sources on an on-premises platform and enabled live dashboards and alerts [7]. The published case describes the outcome qualitatively. On a protocol pilot, assign a named owner to each mapping and test a disconnected source through to the dashboard. Weak ownership and limited observability can leave stale data looking current.
FAQ
Can OPC UA and MQTT run together?
Yes. A gateway can subscribe to an OPC UA server and publish normalized readings to MQTT. OPC UA PubSub can also use MQTT when both endpoints support the required mapping [3] [4].
Can a legacy Modbus RTU meter feed a modern MES?
Yes. A serial-capable gateway can poll the meter, translate register values into engineering units and expose normalized telemetry through a broker or an MES connector [2].
Does MQTT QoS 1 prevent duplicate readings?
QoS 1 provides at-least-once delivery, so duplicates are possible. Include an event identifier and make consumers idempotent so a replayed event has the same effect as a single delivery [4].
How should a gateway handle a broker outage?
Buffer within a defined storage limit, flag stale data and replay eligible records after reconnection. Preserve original timestamps and verify the behavior when the buffer fills.
How do I evaluate a factory integration vendor?
Ask for a witnessed test on representative firmware, a versioned mapping, observed outage recovery and a rollback demonstration. Confirm who owns certificate renewal, support escalation and post-upgrade regression testing.
Conclusion
Use the first production line to prove that each reading retains its meaning from device to application and that telemetry recovers after an outage. That evidence gives other plants a repeatable basis for commissioning. Share a representative asset list, register map and target use case with TMA Innovation to scope a read-only interoperability pilot [7].
References
[1] Deloitte Insights, 2025 Smart Manufacturing and Operations Survey: Navigating challenges to implementation, 2025. Survey
[2] Modbus Organization, Specifications and Implementation Guides, undated. Specifications
[3] OPC Foundation, OPC Unified Architecture, Part 1: Overview and Concepts, undated. Specification
[4] OASIS, MQTT Version 5.0, 2019. Standard
[5] NIST, Guide to Operational Technology (OT) Security, 2023. Special Publication 800-82 Revision 3
[6] TMA Tech Group, Giới thiệu TMA Tech Group, undated. Company history
[7] TMA Innovation, T-Box, undated. Manufacturing case study and contact form


