Production monitoring prototypes
Three small, working concepts that explore what useful shop-floor software could look like for a CNC or auto-component plant. They exist to start conversations, not to sell a product.
Experimental concept — sample data only. Not a live factory deployment. Every figure on this page is invented for demonstration. Nothing you enter is sent anywhere or saved after you leave the page.
Production monitoring dashboard
A single-screen shift view for a supervisor or production manager: planned vs actual output, downtime and rejections, by hour and by machine. Switch between shifts to see how the same layout highlights different problems.
- Planned production
- 500
- parts this shift
- Actual production
- 420
- 80 parts below plan
- Achievement
- 84%
- Behind plan
- Downtime
- 65 min
- all machines
- Rejections
- 12
- 408 good parts
Hourly output: planned vs actual
Use the left and right arrow keys to move between hours.
View hourly figures as a table
| Hour | Planned | Actual |
|---|---|---|
| H1 | 60 | 58 |
| H2 | 65 | 48 |
| H3 | 65 | 60 |
| H4 | 60 | 56 |
| H5 | 65 | 30 |
| H6 | 60 | 56 |
| H7 | 65 | 58 |
| H8 | 60 | 54 |
| Machine | Plan | Actual | Ach. | Down (min) | Rej. | Status |
|---|---|---|---|---|---|---|
| CNC-01 | 180 | 162 | 90% | 15 | 4 | Watch |
| CNC-02 | 160 | 118 | 74% | 38 | 3 | Behind plan |
| CNC-03 | 160 | 140 | 88% | 12 | 5 | Watch |
Status thresholds used in this concept: On plan ≥ 95%, Watch 85–94%, Behind plan < 85%. In a real plant these would be agreed with the production team.
Research question: does seeing H2 and H5 fall behind during the shift give a supervisor enough time to act? Background reading: why production visibility matters.
Machine downtime reporting
A stoppage log designed to take seconds: pick the machine, pick a reason from a short fixed list, enter the start time and duration. The summary ranks reasons by lost minutes so the largest loss is always at the top.
Downtime by reason
65 min · 7 stoppages
Material not available accounts for 38% of recorded downtime.
| Start | Machine | Reason | Minutes |
|---|---|---|---|
| 06:20 | CNC-01 | Setup / changeover | 15 |
| 07:35 | CNC-02 | Tool change | 6 |
| 08:10 | CNC-03 | Tool change | 8 |
| 09:05 | CNC-02 | Quality hold | 3 |
| 10:15 | CNC-02 | Material not available | 25 |
| 11:40 | CNC-03 | Quality hold | 4 |
| 12:50 | CNC-02 | Tool change | 4 |
Entries are kept only in this browser tab and disappear when you leave the page.
Research question: will operators record a reason for every stoppage longer than five minutes if it takes three taps? Background reading: understanding machine downtime tracking.
Production performance insights
Enter one shift's figures to see achievement against plan alongside availability, performance and quality — the three factors of OEE — plus plain-language observations about where the loss is concentrated.
Results
- Achievement vs plan
- 84%
- Behind plan
- Good parts
- 408
- Availability
- 85.6%
- Performance
- 98.2%
- Quality
- 97.1%
- OEE (A × P × Q)
- 81.6%
Observations
- Output is 80 parts below plan (84% achievement).
- At the ideal cycle time, 65 minutes of downtime equals roughly 72 parts of lost capacity.
- The weakest factor is availability (stoppages) at 85.6% — the first place to investigate.
Research question: do plant heads find OEE factors useful, or is achievement against plan with downtime reasons enough?
Would this work on your shop floor?
Honest feedback from plant heads and supervisors is the most valuable input for these prototypes — including "this would never work here, because…".