← All notes

Batch management and the recipe workbench: why Batch and Recipe are two products

Both use the same domain core, but they serve different working days. In one application, drafts end up in stock or stock ends up at the desk.

W-Make Batch and W-Make Recipe share the core for recipes, raw materials and glass chemistry. Their scope differs. Batch covers silos, shifts, postings and the day close. Recipe covers versions, recipe checks and the print-ready batch sheet. The split follows from the different days at the two workplaces.

In production the day starts with shift start, a stock position and batches that are fixed after weighing. At the desk it starts with a recipe version that may still change, an oxide calculation you want to check, and a sheet that has not been posted. Put that in one product and either production rules apply to drafts or draft rules apply to stock. Both lead to mistakes.

An example: in Recipe a recipe version may fail its check, and that is a visible step there. In Batch, once batches are running on that version, it must not be replaced unnoticed by a new one. Costing depends on the version that was weighed and not on the one currently open on screen. Mix the products and exactly that unnoticed replacement can happen in production.

It goes wrong the other way too. Put silos and shifts into Recipe and recipe work has to go through an operating mode nobody at the desk needs. You open a shift to print a sheet and maintain stock that is not really stock there. The tool becomes cumbersome.

Technically the boundary means its own server, file and interface. The calculation of oxide, redox and batch size can be related, and posting stays separate. A batch sheet from Recipe is a draft and a print template. It is posted in Batch only when the scale and silo come into play.

My advice to technical decision-makers: ask which working day is meant to take place in the application before you merge modules just because the core looks similar. A similar calculation is no reason for the same operating model.

First call · 30 minutes · free

Tell me where your process gets stuck.

This article came out of the work on W-Make Batch.

A few sentences about the process are enough: what runs in lists or side calculations today, and who works with it. Within two working days you get a reply and a clear view of whether I am the right person for it.

  • ✓Reply within two working days
  • ✓A clear view, even if I am not the right fit
  • ✓No presentation needed
Arrange a call