Episode Details

UNTANGLING THE PLANT FLOOR: MQTT vs OPC UA & THE TRUTH ABOUT DISCONNECTED MANUFACTURING DATAWhy are modern factories still running on manual exports and guesswork despite having ERP, MES, and Azure systems in place? This episode cuts through the technology hype to address the core problem: a fundamental lack of trust in manufacturing data. People try to frame industrial connectivity as a winner-takes-all battle between MQTT and OPC UA, but that misses the point entirely. If your operators trust the local HMI more than the corporate dashboard, or if every OEE review devolves into an argument about whose numbers are right, you don't have a protocol problem—you have a semantic problem. Technology alone does not create meaning; to build a truly connected factory, you must start with the production problem first and define a shared language for production events before scaling up your technology stack.

In This Episode, We Discuss:

• The Trust Gap on the Plant Floor: Why planners work from spreadsheets and operators rely on local HMIs despite heavy investment in ERP and Azure.
• The Battle of the Numbers: Why morning, afternoon, and night shifts often arrive at three different production counts, and why none of them are necessarily wrong, just descriptive of different points in the process.
• MQTT vs. OPC UA – Two Different Jobs, Not Rivals:
  
  
  • MQTT (Transport): A lightweight, published/subscribe protocol that excels at routing messages efficiently, decoupling publishers from consumers, and handling unstable networks. It doesn't care what is in the payload; it just delivers the envelope.
  • OPC UA (Meaning): Defines what the thing is and what a value represents. It exposes a browsable address space with structured models, variable types, engineering units, and security built into the application layer.
• Why New Dashboards Fail to Solve Disconnected Data: A clean chart doesn't create meaning. A dashboard cannot guess if state code "one" means running, idle, or faulted without context from the machine.
• The Practical Role of the Edge: Why it is critical to normalize data once near the source, rather than mapping it five times in different downstream systems.
• ISA-95 as a Naming Contract: Using the enterprise-to-cell hierarchy as a stable map to locate assets consistently before applying changing business context like work orders and products.
• The Unified Namespace (UNS) Hype: Understanding UNS as a common event space for IT and OT to publish facts, not a new master database or a magic bullet that creates a shared operating model without effort.
• MQTT Topic and Payload Design:
  
  
  • The dangers of stuffing transient context (product codes, order numbers) into static topic paths.
  • Why topic names are case-sensitive and demand strict lowercase conventions.
  • The "cost of casual JSON" and why semantic contracts (types, units, lineage) are essential.
• Sparkplug B: How it adds industrial rules to MQTT (defined topics, birth/death lifecycle state) but still doesn't replace the need to define what your production events actually mean.
• Azure IoT Operations & Microsoft Fabric: Microsoft's edge data plane pattern, running modular services on Arc-enabled Kubernetes, and why a production-ready deployment demands hybrid IT/OT skills.
• The Control vs. Data Plane Boundary: Why local control loops must remain independent of the cloud, and why a broker is never a safety controller.

Key Quote"transport and meaning are different jobs. MQTT roots messages where they need to go, and OPC UA provides machine data with structure and context."

Tags: #ManufacturingData #MQTT #OPCUA #UnifiedNamespace #ISA95 #IndustrialIoT #OEE #AzureIoTOperations #MicrosoftFabric #ITOTconvergence #Sm