How it works
This Coreflux LoT template computes OEE for every machine on a line, on the broker, every 5 seconds. Machine state, a parts counter and a scrap counter come in under raw/factory/hall-a/line-1/<machine>/.... A line clock ticks each machine, and one Action adds the tick to a run, idle or fault bucket, counts parts made and scrapped since the shift started, and publishes Availability, Performance, Quality and OEE to factory/hall-a/line-1/<machine>/oee. It runs on the free Community licence.
Key features
- The whole OEE definition sits in one Action,
OeeMachineCalc, in four lines you can read and change. - The ideal cycle time is a retained config topic per machine. Change it and Performance moves on the next record.
- Shifts start at 06:00 on weekdays or when you publish to
factory/hall-a/line-1/shift/cmd/start. - Counter baselines survive a PLC restart: if a counter goes backwards the count does not go negative.
- A
POSTGRESQLroute stores every record, and the compose file brings up PostgreSQL and a Grafana dashboard with a gauge per machine. - It uses 8 of the 24 LoT artifacts and 2 of the 3 routes the Community licence allows.