03 — Story
The problem.
Downtime is usually written down in several places: shift notes, operator comments, spreadsheets and informal follow-up lists. That makes it hard to see repeat losses, make sure every stop gets a root cause, or hand a clear story to the next shift.
- Built for
- Plant supervisors, line operators, maintenance and process engineers, and operations managers who need one shared record of stops and fixes.
What I built.
I built one working app for all three roles: a tablet screen to log a stop and call maintenance, a Today screen for supervisors, a line status board for screens on the floor, a review queue that asks for the root cause, and an action board where every fix has an owner and a due date. A short weekly report and a shift handover close the loop.
01
Today on the Floor
Key figures, a live card for each line and one queue of stops to review, overdue actions and blocked actions, each one click from the fix.
02
Log a Stop on a Tablet
Large touch targets: pick the machine and the reason and a live timer starts. Call maintenance, then mark the line running again.
03
Root-Cause Review
Supervisors record what caused each stop and close it. A stop cannot be closed without a root cause.
04
Action Board
Every countermeasure has an owner, a due date and a status, with overdue and blocked actions shown first.
05
Weekly Report and Handover
Where time was lost, what to focus on next and which actions are late, plus a printable shift handover.
06
Tested End to End
Browser tests click through every screen and role on SQLite and PostgreSQL, at phone, tablet and desktop widths, in light and dark.
