Skip to main content
All integrations
SCADA / MES & Machine Data

Ignition (Inductive Automation) + Ignite Lean

Available now

Ignition is the most popular SCADA/MES platform in SMB-to-mid manufacturing. The single highest-value machine-data source.

MQTT / Sparkplug B OPC-UA roadmap REST API roadmap

How the Connection Works

Machine / PLCcycle, state, faults
Ignition (Inductive Automation)SCADA / edge
MQTT / Sparkplug B
Ignite Leaningest + map tags
Downtime on the floor map
Live OEE + cycle time
Auto work orders

How It Works

  1. 1Ignition publishes tag data over MQTT (Sparkplug B) or OPC-UA.
  2. 2Run the Ignite Lean mqtt-bridge against the Ignition MQTT Transmission output, or the opcua-bridge against the Ignition OPC-UA Server.
  3. 3Map each tag to a station in Settings -> Connectors and cycle / downtime / OEE are sensed automatically. Order context can flow back to the HMI.

Recommended Workflows

How Ignition (Inductive Automation) works best with Ignite Lean. These are recommended patterns: Ignite Lean fires the trigger, and how Ignition (Inductive Automation) routes it (which work group, which device, which rule) is configured to your IT setup.

Machine down to work order
Trigger A machine reports a stop or fault
  1. 1Ignition (Inductive Automation) publishes the downtime or fault over MQTT or OPC-UA.
  2. 2Ignite Lean opens a downtime event on the floor map immediately.
  3. 3If it runs past your threshold, an auto work order goes to maintenance.
  4. 4The OEE clock reflects the loss live.
Downtime is caught and dispatched the second it happens, not at shift change.
Sensed OEE, not typed
Trigger Each machine cycle completes
  1. 1Ignition (Inductive Automation) streams the cycle count to Ignite Lean.
  2. 2Ignite Lean attributes it to the station and the active order.
  3. 3OEE, cycle time, and throughput update on their own.
OEE you can trust because it is measured, not hand-entered.

Connect Ignition (Inductive Automation) today

This works now through our REST API, outbound webhooks, and Excel/CSV. Start with the API reference, or talk to us about a guided setup.

API ReferenceTalk to Us