Dashboard for manufacturing
It brings orders, workstation load, scrap and dates into one report. While the shift is still on, it shows where the queue stopped and which orders are losing their date.
- Buildfrom $1,700
- Timeline2–4 weeks
- Supportfrom $420/mo
Who this suits: Plants where the plan lives in a spreadsheet, the real state of things comes over the phone from a foreman, and a missed date surfaces on the day of shipping.
What is in the first version
- orders by stage
- station queues
- scrap by cause
- dates per order
The figures above are the package this sits on: Dashboard and analytics. Anything past its edges the calculator adds before the work starts, not after.
How the path goes
- 01
The order breaks into stages
Every stage carries a station, a norm and a queue place, so the date comes from the queue, not optimism.
- 02
The shift logs what happened
A few taps at the station terminal: made, scrapped, stopped, why, since the form suits the shift, not the report.
- 03
The date recomputes itself
Scrap returns a batch to the queue, downtime shifts everything behind it, and today’s late orders land in a list.
What decides whether this works or annoys people
The log is written from memory
Then scrap has no stage and downtime no cause, so entry lives at the machine and the reason list stays short.
Scrap logging reads as blame
Once the screen punishes, scrap stops being logged, so it counts by stage and cause with the per-person cut closed by default.
The plan rests on old norms
An optimistic norm makes every order late, so actual time corrects it, the change carries a date and old orders keep theirs.
What to measure once it is live
- share of orders delivered on the first date
- scrap by stage and by cause
- station downtime per shift
- share of shifts with the log filled in
Why this comes out faster
The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.
A likely stack for this
Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.
- The screen and the shift terminalTypeScriptReactNext.js
- Server and dataNode.jsPostgreSQLPrismaRedisDocker
- Exchange and watchingPythonn8nTemporalTelegram Bot APIGrafana
Price it yourself, right here
Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.
These bills do not come from us
- tablets or terminals at the stations
- network coverage in the shop
- a licence on the system holding orders
- the server the report runs on
Asked before the first call
- The network in the shop is poor, will this work?
- The station terminal works offline: entries queue on the device and go to the server when the link returns. Order is preserved, a repeated send makes no duplicates, and a silent station shows on screen.
- Do we have to replace the system we keep our orders in?
- No. Orders and the item list are read from the system you already run, and shop-floor fact and dates are added on top; writing back happens only if you ask, as a separate line.
- Who does the logging, when a foreman has no time for it?
- The foreman or operator, in as many taps as fit between two operations, after we watch a shift. If there is nobody to log it, we say so: an empty report is worse than none.