Day close, shift start, backup: why operations are part of the product

In many projects operations come last. The screens are built first, backup and migration follow at some point, and later still someone notices that shift start differs on every machine. In container-glass production that order soon costs you. The production day needs one clear clock, the stock lives in a file, and the day close has to stay correct even if someone presses the same button again at six.

A shared shift start sounds like a small thing. Without it, one station posts to yesterday, another to today and the log to a third variant. Alarms, batch sheets and handover then refer to different days, although everyone is standing in the same room. That is why shift start is set centrally in the system. The browser's local time or a form field someone once filled in will not do.

The day close works the same way. A CSV export is not yet a close. A close covers which batches apply, what the silo level is and what handover the next shift finds. The result has to be reproducible the next day with the same rules. If it only works when three particular fields happen to be filled, it helps nobody in production.

Migrations go almost unnoticed until something goes wrong. A new recipe version, another posting type or a new field on the silo also touches what was posted yesterday. A migration that rewrites old batches makes the history unreliable. A migration that only works forwards and leaves the past alone takes more effort to write. In return you can still say later which figure belonged to which furnace setting.

Backup belongs here too. An SQLite file holding the stock is the stock. If you do not back it up regularly and verifiably, operations depend on one machine's disk. That is why restores have to be practised. Documenting them is not enough, and emergencies rarely arrive on a quiet Sunday afternoon.

My advice to technical decision-makers: put migration, backup and the shared shift start into the project scope before the first screen is fixed. Whatever is added later tends to get bypassed when it matters.