Shift handover before the sitemap: what domain knowledge changes in batch management
Knowing the batch book and the shift handover changes the questions. You get different rules, not more fields on the same screen.
Read the note →Notes
Writing for people who own the plant day.
No announcements and no tool lists. The subject is bookings, shift handover, product boundaries, and what remains after go-live.
Batch management and the recipe workbench: why Batch and Studio are two products
The same domain core, two cuts. Force recipe work and plant operations into one application and you carry drafts into stock, or stock onto the desk.
Read the note →From the batch ticket through the batch book to the daily log
Two documents, one model. If they live apart, the fracture appears exactly at shift handover.
Read the note →Batch book and silo deduction: why domain bookings must not simply be deleted
After weighing, a booking has already changed silo and batch book. Correction means a reversing entry, a cancellation or a reconcile, not DELETE.
Read the note →Day close, shift start, backup: operations are part of the product
A day close that only works in the demo will not hold on the floor. The shared clock for shift start, migration and backup belong in the application.
Read the note →30-min analysis · free
Describe the process that's breaking today.
Describe the flow that currently ends in copies, side calculations or quiet corrections. I reply within two working days and will honestly tell you whether I can take the case.
- ✓Reply within 2 working days
- ✓Honest assessment of whether I can take the case
- ✓No slide deck needed, just understanding of the flow