All integrations Available now
SCADA / MES & Machine Data
Kepware (PTC) + Ignite Lean
Kepware KEPServerEX is the universal industrial protocol bridge. The fastest path to almost any PLC.
OPC-UA roadmap MQTT / Sparkplug B REST API roadmap
How the Connection Works
Machine / PLCcycle, state, faults
Kepware (PTC)SCADA / edge
OPC-UA
Ignite Leaningest + map tags
Downtime on the floor map
Live OEE + cycle time
Auto work orders
How It Works
- 1Kepware aggregates 150+ PLC protocols and republishes them over OPC-UA or MQTT.
- 2Run either Ignite Lean bridge against Kepware: opcua-bridge for direct subscription, mqtt-bridge if you use the IoT Gateway.
- 3One bridge instance covers the whole mixed-PLC floor.
Recommended Workflows
How Kepware (PTC) works best with Ignite Lean. These are recommended patterns: Ignite Lean fires the trigger, and how Kepware (PTC) 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
- 1Kepware (PTC) publishes the downtime or fault over MQTT or OPC-UA.
- 2Ignite Lean opens a downtime event on the floor map immediately.
- 3If it runs past your threshold, an auto work order goes to maintenance.
- 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
- 1Kepware (PTC) streams the cycle count to Ignite Lean.
- 2Ignite Lean attributes it to the station and the active order.
- 3OEE, cycle time, and throughput update on their own.
OEE you can trust because it is measured, not hand-entered.
Connect Kepware (PTC) 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.