Batchmaker family · Vanilla operations
W-Make Batch · Vanilla
The complete operations version for container glass: from batch ticket through silo and batch book to the daily log.
- Responsibility
- Domain model, full-stack development, and technical quality.
- Technology
- Node.js · Express · SQLite · Web Components · native tests · Playwright
- Status
- Live · reference implementation
- Positioning
- The domain reference. Bookings, stock and shift handover stay in one model.
Situation
Situation
In container-glass production the day is a chain. A recipe version holds, a batch ticket goes to the scale, consumption leaves the silo, oxide and redox have to match the furnace, the shift hands over, the day closes. If one link breaks, three figures that do not agree are waiting the next morning.
Built as a loose set of screens, someone copies values from one sheet to the next. The ticket says one thing, the silo another, the log a third. The fastest correction in software is then to delete or overwrite a row. After weighing, that is already a lie to stock and to the shift.
Shift handover adds pressure. What is passed on verbally is written nowhere. Whoever takes over in the morning inherits a hall and a table that contradict each other.
Decisions
Decisions
- 01
Domain bookings are states. A correction after silo deduction is a reversing entry, a cancellation or a reconcile, not a DELETE on the row.
- 02
Batch ticket, batch book and daily log belong in one model. Two tools at that seam recreate the paper fracture the software was meant to replace.
- 03
Oxide, redox, batch size and cost stay bound to the recipe version and live in their own modules. The interface shows the figure. It does not invent it.
- 04
Shift start is a shared clock, not a default in a form field. Without that clock the day drifts between stations.
- 05
Migrations, backup and a close you can repeat belong to the product. A system that closes only in the demo will not hold on the floor.
- 06
The public demo shows the model. Client data, volumes and internal metrics stay off the site.
What you can inspect
A look at the application.
What you can inspect
The flow as a model.
01
Recipe
Composition, version, temperature and cost stay tied to later consumption.
02
Ticket
The ticket is the order to the scale, not a printout of a table.
03
Silo
Consumption leaves the stock. After that the booking is part of the hall.
04
Batch book
What was weighed stays bound to the batch and the recipe version.
05
Log
The day closes as a state the next shift will find, not as an exported list.
What remains
What remains
A production system improves when domain irreversibility lives in the data model. A form validation comes too late once silo and log have already been written.
batchmaker-vanilla.w-make.com →30-min analysis · free