Industrial Data Capture
Get the machine data out of your equipment, the foundation every other outcome builds on. Connect any PLC, sensor, or device and stream clean, structured data into MAJiK Visual Factory, or to your own cloud, historian, or analytics tools, all from a single binary. From install to your first PLC tags in minutes.
30%
of industrial IoT pilots stalled before production.
Traditional IIoT stacks stall before they ship. MAJiK IoT Connect goes live in days, not quarters.
Source: Microsoft, IoT Signals, 2019
How It Works
From raw equipment signals to actionable intelligence.
Capabilities
What Visual Factory delivers for industrial data capture.
PLCs and machine control
Point it at the network and it finds what is there: Allen-Bradley, Siemens, Beckhoff, Mitsubishi, and anything speaking Modbus or OPC UA. Browse live tags without touching the PLC program, over read-only connections.
Protocols
CNC and machine tools
Cycle status, part counts, programs, and alarms straight from the control: FANUC over FOCAS, Heidenhain over LSV2, and anything publishing MTConnect, each tied to the right machine in the equipment model.
Protocols
Process equipment and instruments
Per-cycle process values from injection molders, torque results from fastening tools, stable weights from scales, and IO-Link sensor readings. 24 edge transforms turn raw values into meaningful metrics before they leave your network.
Protocols
Buildings, utilities, and existing systems
BACnet brings building automation and HVAC alongside production, useful for climate-sensitive and refrigerated processes, while SQL, files, HTTP, and MQTT pull in the data your existing systems already produce. Everything lands in the same ISA-95 Unified Namespace.
Protocols
Delivered to Visual Factory, reliably
One binary streams everything as Sparkplug B into MAJiK Visual Factory, or any broker you choose. Store-and-forward buffers through outages and replays in order, connections stay read-only and outbound-only, and configuration and updates are cloud-managed.
Built in
Sparkplug B at the edge, a Unified Namespace for the enterprise
The modern industrial data architecture, built in. Capture at the edge, then publish it both ways: as Sparkplug B for the systems that already speak it, and as a contextualized Unified Namespace the whole organization can subscribe to.
01Sparkplug B at the edge
Sparkplug B is the open standard that makes plain MQTT ready for the plant floor. It defines how each value is named, typed, and kept in sync, so machine data lands on the network clean and trustworthy.
Every device announces itself with a birth certificate listing each metric and its value, and an automatic death certificate marks that data stale the moment it drops offline.
From there it reports by exception, publishing only what changes, so the network stays light and the live state is always known.
02Modeled as a Unified Namespace
A Unified Namespace organizes all of that into a single, structured model of the whole organization, from a sensor on a line up to the business, and becomes the one source of truth every system reads from.
The same data is published as an ISA-95 hierarchy (enterprise, site, area, line, cell, equipment) with full context, so any tool finds what it needs by where it lives.
Producers and consumers are decoupled, so your historians, analytics, dashboards, and AI all subscribe to the same real-time data instead of wiring point-to-point up the pyramid.
03One capture, published both ways
On its own, Sparkplug’s fixed topic structure cannot express a full ISA-95 namespace, so MAJiK IoT Connect does not make you choose.
From a single capture it publishes both in parallel: Sparkplug B for the systems that already speak it, and a contextualized Unified Namespace for everything that wants ISA-95 context.
Both are driven from the same data, not transcoded one from the other, the architecture UNS practitioners recommend.
Replacing something?
How MAJiK IoT Connect compares to the tools teams reach for today.