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

Beckhoff TwinCAT + Ignite Lean

Available now

Beckhoff TwinCAT powers high-speed motion + control. Bridge its PLC data via OPC-UA.

OPC-UA roadmap MQTT / Sparkplug B REST API roadmap

How the Connection Works

Machine / PLCcycle, state, faults
Beckhoff TwinCATSCADA / edge
OPC-UA
Ignite Leaningest + map tags
Downtime on the floor map
Live OEE + cycle time
Auto work orders

How It Works

  1. 1TwinCAT exposes tags via OPC-UA (TF6100) or an MQTT publisher.
  2. 2Run the Ignite Lean opcua-bridge or mqtt-bridge against the published endpoint.
  3. 3Map each tag to a station so axis, state, and fault data drive OEE.

Recommended Workflows

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