Dev.to WebDev 🛠 Dev 👁 0

OeeBook: OEE without the fragile shift spreadsheet

Planned 480 minutes, seventy-two of them down, twelve-second ideal cycle, nineteen hundred parts with forty-eight scrap — and by the morning meeting someone has to turn that into Availability, Performance, Quality, and o

Planned 480 minutes, seventy-two of them down, twelve-second ideal cycle, nineteen hundred parts with forty-eight scrap — and by the morning meeting someone has to turn that into Availability, Performance, Quality, and one OEE number the plant can trust. The formula is standard; the spreadsheet usually is not.

OeeBook is live: sybilgambleyyu.github.io/OeeBook · Source

What you get

  • Assets with ideal cycle (sec/unit) or units/hour; optional $/hr for lost-time estimate
  • Shift entries: planned minutes, downtime by reason, total / scrap / rework
  • OEE = A × P × Q with world-class / typical / fair / low bands
  • Rollups by asset, shift, and downtime reason
  • Entries CSV and summary — local-only

Honest limits

Not a MES or SCADA. You enter the shift data; confirm planned-time and ideal-cycle definitions with your site standard.

Pair with NcrBook for nonconformances.

📰 Read the original article on Dev.to WebDev

Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.