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

Mitsubishi MES Interface IT + Ignite Lean

On the roadmap

Mitsubishi MES Interface IT bridges MELSEC PLCs to enterprise systems. Connect at the OPC-UA / SQL bridge layer.

OPC-UA roadmap REST API roadmap

How the Connection Works

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

How It Works

  1. 1MES Interface IT exposes PLC data via OPC-UA + SQL.
  2. 2Ignite Lean ingestion is on the roadmap.
  3. 3Request early access.

Recommended Workflows

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

Want the Mitsubishi MES Interface IT connector?

This one is on the roadmap. Tell us you want it and we'll move it up the list and email you when early access opens.