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

HighByte Intelligence Hub + Ignite Lean

Available now

HighByte models and contextualizes OT data at the edge. A clean, modeled feed into Ignite Lean.

MQTT / Sparkplug B OPC-UA roadmap REST API roadmap

How the Connection Works

Machine / PLCcycle, state, faults
HighByte Intelligence HubSCADA / edge
MQTT / Sparkplug B
Ignite Leaningest + map tags
Downtime on the floor map
Live OEE + cycle time
Auto work orders

How It Works

  1. 1HighByte builds data models at the edge and publishes them over MQTT / REST.
  2. 2Run the Ignite Lean mqtt-bridge against the HighByte broker output.
  3. 3The bridge forwards every modeled tag for floor-map + OEE + auto-WO routing.

Recommended Workflows

How HighByte Intelligence Hub works best with Ignite Lean. These are recommended patterns: Ignite Lean fires the trigger, and how HighByte Intelligence Hub 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. 1HighByte Intelligence Hub 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. 1HighByte Intelligence Hub 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 HighByte Intelligence Hub 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