Learn Automation with MINATA #66: Recipes and Machine Parameters — Changing Values Without Changing the Logic

Recipes and Machine Parameters: Changing Values Without Changing the Logic

A good recipe lets the product change under control, without anyone editing the PLC logic. What it must not do is turn the HMI into a screen where anybody can adjust any number on the machine.

Classify the values first

Before building a recipe, classify the machine's values, because each group is managed differently:

Group	Example	Who edits it, and how it is stored
Product setpoints	Temperature, speed, time	The recipe, by permission
Engineering limits	Safe minimum and maximum for the mechanism	Engineering; locked down
Calibration constants	Scaling, sensor offset	Maintenance, with an audit trail
Safety parameters	Safety thresholds	Never in a recipe
Service parameters	First-time configuration	High permission, rarely changed

Mixing these groups onto one "settings" screen is where mistakes and incidents come from.

A recipe needs identity and a version

A recipe needs an ID, a version, who changed it, when, and its approval state — plus a snapshot used for each batch where traceability is required. If only the current values are stored, then after one edit nobody can say what parameters the previous product ran on. That becomes a serious problem the day a quality complaint arrives.

Separate values from logic

A recipe changes data, not behaviour. The PLC logic reads the recipe and then applies its own limits. A recipe value beyond the engineering threshold must be rejected — changing product must never become a way of changing the safety of the machine.

A worked engineering situation

A machine holds recipes by product code, each with a version and an approval state. At changeover, the operator selects an approved recipe; the PLC loads the setpoints but still clamps them inside fixed engineering limits. Each batch stores a snapshot of the recipe, so that later somebody can answer "which parameters did this lot run on".

The parameter list, the editing rights and the storage method all follow the product requirements and the quality procedure.

Common mistakes

Putting every value, safety parameters included, on one shared settings screen.
Recipes without versions, so old batch parameters cannot be traced.
Letting a recipe override an engineering or safety limit.
No access control, so anyone can edit a product setpoint.
Storing only current values, losing the history of changes.

Recipe and parameter checklist

[ ] Values are classified into groups, each with its own editing rights.
[ ] Recipes carry an ID, a version, an author, a time and an approval state.
[ ] The PLC clamps recipe values inside fixed engineering limits.
[ ] Safety parameters are never part of a recipe.
[ ] Each batch keeps a snapshot for traceability.

Separating the values from the logic is what makes a changeover routine instead of risky. #67 goes into batch control and the ideas behind ISA-88.

Read more automation knowledge at MINATA: https://minatavn.com/en/blog/industrial-automation

Previous — #65: Manual, automatic and bumpless transfer: https://minatavn.com/en/blog/automation-65-manual-auto-bumpless-transfer

Next — #67: Batch control and ISA-88: https://minatavn.com/en/blog/automation-67-batch-control-isa-88

View all MINATA technical articles