Beverage Automation in Australia: Recipe Control, Work Orders and a Single Source of Truth

It is easy to think of a control system as the part that runs the pumps and valves. That is the smallest part of what it does. The real value is that the automation sets each product up once, makes it the same way every time, and keeps a clear record of how every batch was made. Get that right and variability comes down, and variability is what steadily erodes both consistency and margin.

Metromotion Controls is a control systems integrator in Mount Waverley. We build this layer for soft drink, juice, water, ready-to-drink, beer, cider and spirits producers across Melbourne, Victoria and Australia.

The principle is simple. Give the whole business one live source of truth. Schedulers, operators, quality and management all see the same plan. The line runs it the same way every shift. And how each product was made is saved as data you can return to, measure, and improve.

From paper to one live source of truth

Many beverage plants still run on paper. A scheduler updates the plan, prints it, and sends it down to the floor, and the line runs whatever sheet is in hand. Each change has to be reprinted and redistributed, while an older version is often still pinned up nearby. The floor stays a step behind the office.

When the run is finished, the record of how it was made is thin: a few lines in a logbook rather than the full picture.

Automation removes the paper. The recipe and the work order live in the control system. When a scheduler makes a change, the line has it the moment they save, and so does everyone else. No printing, no delay, and no question about which copy is current. The plan changes, and the floor is already working to it.

Recipe control: define each product once, and keep its history

A recipe is the definition of a product: the blend and brix targets, the carbonation level, the fermentation time and temperature, the cut points on a still, the pasteurisation temperature curve, and the fill settings. Recipe control keeps all of it in one place, separate from the code that drives the equipment. Because it is built on the ISA-88 model, a recipe is a set of parameters over a tested library of reusable phases, so setting up a new product, or adjusting an existing one, is a parameter change rather than a programming job.

That gives you two things. The product is defined once and made the same way on every line and every shift. And every change to a recipe is saved with a version, a timestamp and the name of whoever made it, so you can return to any day and see exactly what the recipe was, who changed it, and what they changed.

That history matters most when a product starts to drift. The first question is usually whether something changed, and with versioned recipes you can answer it. You can see that the fermentation time was shortened, or the pasteurisation curve adjusted, and then look at what happened to the product afterwards.

Batch control: make it the same way, every time

Batch control runs that recipe as a batch against a work order. The line follows the defined sequence, with holds, aborts and restarts handled in the logic, so the product comes out the same on every shift, whoever is operating.

This is where variability comes down. A fermentation that always holds the same time and temperature. A distillation that always cuts at the same point. A pasteuriser that always follows the same curve. That consistency comes from the system, not from an operator's memory or a note left on the panel. The result is less drift between batches, and far less off-spec product at the start of a run or after a changeover.

Work orders: one schedule everyone shares

A work order is straightforward: make this quantity of this product, at this time. Held in the control and MES layer, it becomes the single schedule the whole business works from. Schedulers set it and change it in one place. Operators see what is next, with the right recipe already loaded. Quality knows what is being made and to what specification. Management can see the plan and how it is tracking.

Because there is one work order rather than a stack of printouts, changing the plan is instant and unambiguous. Bring a run forward or swap a product, and the floor is on the new plan as soon as it is saved. The paper, the reprints, the lag and the version confusion all go, and so do the wrong runs and lost time they cause.

Historian: the full record of every batch

As a work order runs, the historian records all of it: when it started, when it finished, how much came off the line, and the process data behind it. On a beverage line that is the fermentation curve, the still temperatures, the pasteurisation hold and any divert events, the blend and carbonation readings, and the fill volumes, all tied to that batch, that work order, and the recipe version that made it.

That link is what makes it valuable. Because the batch is tied to the recipe version it ran on, you can return to any run and know not only what was produced, but exactly how it was specified at the time. For quality and recall it is genealogy: which product was made under which conditions, isolated quickly and defensibly when a complaint or recall arises, in line with the traceability expected under the FSANZ Food Standards Code. The control and data layer underneath it is covered in our Ignition SCADA guide and our MES and SCADA integration work.

Measure and improve with real numbers

Once every run is recorded as data, improving the line stops being a matter of opinion. OEE, read from validated machine states rather than estimates, shows where the time actually goes: short stops, changeovers, CIP windows, and the small losses that never reach a shift report. The process data shows where ingredient is given away, where a run drifts, and which products or shifts hold tightest to specification.

It also lets you compare like with like. Change a fermentation profile, a distillation cut or a changeover routine, then judge it against the recorded data from before and after. With versioned recipes and a full historian, that is a controlled comparison rather than guesswork. That is how variability comes down over time, not in a single change, but by testing each one and keeping what works. It is the same approach behind our Remedy Drinks MEX and Ignition integration, where the system raises maintenance work orders automatically from real plant events.

What it adds up to

Put together, you have a beverage operation running from one live source of truth rather than a stack of paper. Schedulers change the plan and the floor follows. Every product is made to one definition, every time. Every batch leaves a full record of how it was made and which recipe version made it. And every change can be measured, so variability comes down with evidence behind it.

The process loops underneath still need tuning and the interlocks still have to hold, and we cover that engineering elsewhere. But the value that reaches the whole business sits in the layer above: recipe, batch, work order and data.

If you can share your product range, how you schedule production, and where variability or the gap between the plan and the floor is costing you, we can work through where this returns first.

References

• FSANZ Food Standards Code: food safety and traceability requirements in Australia, Food Standards Australia New Zealand.
• ISA: ISA-88 batch control, recipe and procedural models for batch processes.