All integrations Available now
SCADA / MES & Machine Data
Siemens (WinCC / Opcenter) + Ignite Lean
Siemens WinCC and Opcenter run high-end European and automotive plants. Connect at the OPC-UA layer.
OPC-UA roadmap MQTT / Sparkplug B REST API roadmap
How the Connection Works
Machine / PLCcycle, state, faults
Siemens (WinCC / Opcenter)SCADA / edge
OPC-UA
Ignite Leaningest + map tags
Downtime on the floor map
Live OEE + cycle time
Auto work orders
How It Works
- 1WinCC / Opcenter expose data via OPC-UA.
- 2Run the Ignite Lean opcua-bridge against the WinCC OPC-UA server.
- 3Map tags to stations so telemetry, machine status, and quality signals flow live.
Recommended Workflows
How Siemens (WinCC / Opcenter) works best with Ignite Lean. These are recommended patterns: Ignite Lean fires the trigger, and how Siemens (WinCC / Opcenter) 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
- 1Siemens (WinCC / Opcenter) 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
- 1Siemens (WinCC / Opcenter) 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 Siemens (WinCC / Opcenter) 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.