From batch ticket to daily log
Two documents, one model. If they live apart, the fracture appears exactly where the shift hands over.
The batch ticket says what should go into the furnace. The daily log says what the day made of it. On paper these are two worlds. In software they must not stay that way.
A continuous model connects recipe, batch, consumption, and close. Not because integration is fashionable, but because otherwise the handover happens again in copies and side calculations.
The interface can stay lean. The connection in the data model cannot. Screens alone ship the fracture with them.
Takeaway: draw a melter’s day first, not the application sitemap.