MQTT (Message Queuing Telemetry Transport)
MQTT (Message Queuing Telemetry Transport) is a lightweight publish-subscribe messaging protocol. Devices and gateways publish topics. Applications subscribe to the topics they need. The broker sits in the middle. That pattern fits intermittent links, many small sensors, and edge devices that prefer to push rather than expose a full address space.
In Industry 4.0 and IIoT stacks, MQTT often carries telemetry that does not need the richer information model of OPC UA. Many plants use both: OPC UA near structured machine data, MQTT for simpler publish paths toward analytics, twins, or cloud consumers.
For a live hall view, MQTT is useful when door contacts, environmental sensors, or edge publishers need to arrive beside location and production context. The protocol does not invent meaning. Topic design, payload conventions, and identifier discipline still decide whether the twin can trust the stream.
Key Components
Broker - The hub that accepts publishes and delivers messages to subscribers.
Topics - Hierarchical names that organize streams (site, line, asset, signal).
Publish and subscribe - Producers push. Consumers opt in. Neither side needs a permanent point-to-point link to every peer.
Quality of service - Delivery guarantees that trade reliability against overhead on constrained links.
Payloads - Often compact JSON or binary. Semantics must still be agreed outside the wire format.
Applications in Manufacturing and Logistics
Plants publish machine health, buffer sensors, and simple status flags over MQTT when a full OPC UA model is unnecessary. Logistics halls use it for edge gateways that already aggregate radio or sensor traffic. Digital twins and analytics platforms subscribe to selected topics and place those values on the same map as movers and material when identifiers line up.
Benefits and Challenges
Benefit: low overhead and a clear fan-out pattern for many small producers. Challenge: wild topic naming, missing units, and no shared asset IDs create a second silo. MQTT alone does not replace structured industrial models where controllers and enterprise systems need typed objects and methods.
Related Terms
OPC UA often sits beside MQTT rather than against it. IoT and edge computing describe where publishers live. Interoperability is the wider Industry 4.0 goal those protocols serve. Digital twins consume the streams once meaning is stable.
Frequently Asked Questions
Is MQTT a replacement for OPC UA? Usually no. MQTT is strong for lightweight publish-subscribe. OPC UA is strong for structured industrial information models. Many architectures use both.
Does MQTT give you a digital twin? No. It moves messages. The twin still needs a hall model, identifiers, and a place to store and show the values.
Why do brownfield plants care? Gateways can publish legacy register values as MQTT topics without rewriting every controller, as long as naming and units stay disciplined.