Bidirectional MQTT integration for modern industrial data architectures
Factry Historian natively supports MQTT as both a data source and a data destination, making it an ideal component in Unified Namespace (UNS) architectures. Whether you're ingesting real-time sensor data from edge devices or publishing processed values back to the broker, the integration is built for low-latency, flexible communication. Data can be ingested using standard JSON payloads or the Sparkplug B protocol. When using Sparkplug B, the system supports autodiscovery and automatic import of metrics, enabling fast, low-touch onboarding of new devices. On the output side, processed or contextualized data can be published back to your MQTT broker to feed dashboards, trigger workflows, or make structured Historian data available to other systems.
Why we love
MQTT
Medium length section heading goes here
Medium length section heading goes here
Medium length section heading goes here
Medium length section heading goes here
Medium length section heading goes here
Medium length section heading goes here
Ingest and publish over MQTT
Subscribe to live data streams and publish back processed metrics and events. This makes Factry Historian a flexible participant in edge-to-cloud data flows.
Sparkplug B autodiscovery
Automatically discover new new edge nodes and devices using Sparkplug B. With auto-onboarding, metrics can be imported into Historian with correct naming conventions. No manual configuration needed.
Built for Unified Namespace (UNS)
By supporting bi-directional MQTT communication and structured data output, the integration fits cleanly into modern UNS setups, bridging OT data with cloud apps, MES, or analytics platforms.
New Sparkplug B MQTT collector for Factry Historian: all you need to know
Put your industrial data to work
Ready to get started with Factry? Awesome! Let’s schedule a call so you can discover how our platform empowers your operations.