Order not found. Check the code and try again.
Active orders
0 ordersCompleted orders
0 orders| KB ID | Fab name | Part | Part desc | QTY | Total time | Status reason | Start date | End date | Actions |
|---|
Station tags
Print these once and post one at each station. Operators scan the order tag first, then scan Start or Complete at that station to log the time.
Orders are matched by KB ID. Re-importing updates existing orders' details without resetting their progress; new KB IDs are added with every operation "Not started" until someone actually scans in.
One-time data cleanup
Orders imported before this app tracked "Not started" correctly may still show their first operation as active by default, even though nobody has actually scanned them in. This finds any operation marked active with no real scan history and resets it to Not started — it never touches an operation that's genuinely been worked.
Operations efficiency
Based on 0 orders with runtime data
Variance by shop
Top bottlenecks (over scheduled time)
| Order / part | Sch. | Act. | Var. |
|---|
Average time by operation
| Operation | Avg time | Orders |
|---|
WIP by operation
Aging report
Shop utilization
Operator leaderboard
| Operator | Ops completed | Avg time |
|---|
All orders — scheduled vs actual
| Order / part | Sch. | Act. | Var. |
|---|
Needs discussion
Late, stuck, or over budget — worst first
Due this week
On hold
Where the backlog is — WIP by operation
All open orders — full load
Grouped by project. Click to expand. Includes unscheduled backlog that doesn't appear on the Dashboard.