Industrial IoT Demands Five Nines, and OPC UA Carries the Semantics

Industrial IoT environments are characterised by requirements that read very differently from consumer deployments: five nines of availability, tens of thousands of localised nodes, and zero tolerance for packet loss or unpredictable latency. The protocol stack reflects that, with OPC UA used for semantic interoperability, MQTT for lightweight publish-subscribe messaging, and conversion layers bridging legacy fieldbus equipment.

The distinction between OPC UA and MQTT is the one worth being clear about, because they are frequently presented as alternatives and are not. MQTT moves bytes between a publisher and subscribers efficiently and says nothing whatever about what those bytes mean. OPC UA carries an information model: a temperature is labelled as a temperature, with units, engineering range and its relationship to the machine it belongs to. A plant can and often does run both, with OPC UA describing the data and MQTT transporting it.

The five nines figure deserves scrutiny in context. It amounts to roughly five minutes of downtime a year, and in a factory it is usually a statement about the control network rather than about analytics or cloud connectivity. Conflating the two produces architectures that try to make a dashboard as reliable as an interlock, which is expensive and misses the point: the control path and the reporting path have genuinely different requirements, and designing them as one system means paying control-network prices for reporting.