MQTT for Industry 4.0: Sparkplug B, Unified Namespace and ISA-95 topic design for factories and industrial data.
Most IIoT business cases fail because the benefits are vague and the costs are incomplete. This framework turns downtime, energy and quality gains into numbers you can defend, and shows where messaging and broker costs fit.
A clear IIoT architecture separates devices, edge gateways, the messaging broker and applications so each layer can change without breaking the others. This reference explains each layer's role, the design rules that keep it scalable and a runnable end-to-end example.
The primary host application is the Sparkplug consumer edge nodes depend on. This guide explains STATE messages in Sparkplug 3.0, how edge nodes react when the host goes offline, and how to test the flow with Python and mosquitto.
MTConnect agents expose CNC data over HTTP and XML. Build a bridge that follows the agent's sequence numbers, picks the data items that matter and publishes machine state over MQTT for dashboards and analytics.
Why MQTT became the backbone of Industrial IoT, how edge gateways, Sparkplug B and ISA-95 namespaces fit together, and how to build a working machine-to-cloud data flow with runnable code.
A practical Industry 4.0 guide for engineers and plant leaders: what the core technologies are, how connectivity, data platforms and analytics fit together, and how to launch a first pilot on a managed MQTT broker.
Ready-to-use UNS topic structure examples for discrete manufacturing and process plants, with the naming rules, payload conventions and validation that keep a unified namespace usable as it grows.
Use TwinCAT 3 IoT functions to publish structured PLC data as JSON, verify it on a public broker and then connect to a private broker with TLS, credentials and a Last Will.
Testing a Sparkplug host or dashboard should not require a PLC. This tutorial builds a Python Sparkplug B edge node simulator with births, data, deaths and rebirth handling, running against a real MQTT broker.
Configure Ignition's MQTT Transmission and MQTT Engine modules against an external broker, publish tags as Sparkplug B, consume them back as Ignition tags, and verify the decoded payloads in a broker portal.
A complete Python tutorial for decoding Sparkplug B payloads: generate classes from sparkplug_b.proto, subscribe with paho-mqtt 2.x, resolve metric aliases from birth messages and handle signed integers correctly.
A practical reference to every Sparkplug B data type, the Protobuf field each one travels in, metric properties such as Quality, metric flags and DataSets, with decoded examples and common conversion mistakes.
Network links fail, but industrial data should not disappear. Learn how store and forward works for MQTT edge devices, how to size the buffer, keep replay ordered and throttled, and build it with Python and SQLite.
Report by exception publishes a value only when it changes meaningfully. Learn how deadbands, rate limits and heartbeats work together, and run a Python gateway that applies RBE before publishing to MQTT.
An MQTT DMZ lets plant data reach the cloud without opening a single inbound port to the OT network. This guide covers outbound-only patterns, DMZ bridge brokers, firewall rules and the mistakes that weaken the design.
A practical guide to IIoT data modeling: how to move from flat PLC tags to structured, reusable information models using ISA-95, Sparkplug B templates and OPC UA, published over MQTT.
Every Sparkplug B message travels on a strictly defined topic. This guide breaks down spBv1.0, group ID, message type, edge node ID and device ID, with naming rules, wildcard patterns and common mistakes.
Connect RS-485 Modbus RTU energy meters and sensors to a gateway that publishes their readings over MQTT. Covers wiring, termination, serial settings, register maps and a complete Python poller.
An MQTT historian subscribes to your plant topics and stores every value as time series. This guide compares InfluxDB, TimescaleDB and commercial historians and shows working Telegraf and Python setups.
Sparkplug B gives industrial MQTT a strict session and payload model, while a Unified Namespace gives your plant data a single, readable home. Here is how they fit together, with topic design tips and live examples.
How to sample, compress, timestamp and store industrial time series data flowing over MQTT, with deadband code, a Telegraf config and a storage decision table.
Sparkplug metric aliases replace long metric names with small integers in DATA messages. This guide explains how the mapping works, when to use it, and how to debug alias mismatches.
IT OT convergence is less about merging networks and more about giving two very different teams the same trustworthy data. This explainer covers the cultural gap, the technical building blocks and a practical shared-namespace pattern built on MQTT.
The nine pillars of Industry 4.0 are often presented as separate technologies. This explainer walks through each one in plain terms and shows how a shared MQTT messaging layer is what actually connects them on a real plant floor.
PROFINET IO is cyclic, real-time and controller-centric, so you cannot simply poll it like Modbus. Compare the practical ways to get PROFINET data into MQTT, with a working example that reads a Siemens PLC and publishes to a broker.
Build a small, open-source OPC UA to MQTT gateway that subscribes to PLC tags, maps them to ISA-95 style topics and publishes them to a cloud MQTT broker over TLS.
Most IIoT pilots fail from too much scope, not too little technology. This 30-day IIoT proof of concept plan covers scope, success metrics, a lightweight stack and a week-by-week schedule you can follow on your own plant floor.
A practical IIoT connectivity checklist for plant engineers, covering network access, protocols, data modeling, security and broker selection, with real commands to verify each step before the first machine goes live.
How water and wastewater utilities use MQTT to bring pump stations, reservoirs and lift stations into one telemetry layer, with topic design, report by exception, threshold alerts and a runnable station simulator.
Use open-source CIP libraries on an edge gateway to read ControlLogix and CompactLogix tags and generic EtherNet/IP device attributes, then publish them as clean MQTT messages.
Create an account, get your broker credentials and connect your first device — no servers to install, patch or scale.
