Production monitoring and OEE
The problem in the plant
Pieces, downtime and scrap are written on paper or in separate files, so the shift lead works with yesterday's numbers.
What happens in IRIS
- 01IoT
Sensors send readings to IoT. An alarm rule (threshold, rate of change or anomaly) raises an alarm when a reading leaves its range.
- 02MES Production
Operators report pieces, defects and breaks at the kiosk next to the machine. A critical IoT alarm appears as an Andon alert on the board.
- 03MES Production
MES calculates OEE from the downtime, scrap and pieces it recorded. Every screen uses the same OEE definition.
- 04KPI / Analytics
Every hour MES sends OEE, availability, performance and quality to KPI / Analytics, where you set targets and alert rules.
What you can see and do
- OEE per station and for the plant, built from recorded downtime, scrap and pieces.
- Open Andon alerts that you acknowledge, resolve or escalate.
- OEE against its target, with an alert when it crosses the rule's threshold.
What IRIS does not do here
- MES does not connect to machine controllers. Machine data arrives as events from IoT and Data Bridge.
- IoT does not read OPC UA or Modbus itself. An external gateway forwards that data over MQTT.
- MES does not calculate order delay. APS does.