How Should You Control Machine Recipe Changes?
Control machine recipe changes by treating each recipe as a versioned set of validated operating parameters. Separate editing, approval, transfer and activation, with clear permissions and checks at each step. Practical PLC recipe management best practices should also define what happens when a download fails or a change is requested during an active cycle.
What should a machine recipe contain?
Define a recipe as the operating values needed to make a particular product on a specified machine. Depending on the process, these might include temperature targets, feed speeds, dwell times, pressure settings and sequence options.
Give every parameter a clear name, unit, permitted range and purpose. Avoid labels such as “Setting A” that require someone to remember what they mean.
Alongside the values, record:
- A unique recipe identifier and version.
- The intended product and compatible machine configuration.
- Who prepared and approved the version.
- The reason for the change.
- Its status: draft, approved or retired.
Keep approved versions unchanged. Make an adjustment by creating a new version, preserving the previous values and approval record.
Distinguish recipe parameters from maintenance settings and protective limits. Review any safety-related boundary or proposed adjustment with a qualified assessor.
Who should be allowed to edit and approve recipes?
Set permissions around responsibilities. An operator may need to select an approved recipe without having permission to change its values.
Use the following as a starting point, then adapt it to the plant's staffing and process risks.
| Responsibility | Suggested permission | Required boundary |
|---|---|---|
| Operator | Select and request approved recipes | Cannot alter approved values |
| Process specialist | Create and edit drafts | Cannot silently replace an approved version |
| Authorised approver | Review and release versions | Sees values, changes and validation results |
| Maintenance engineer | Maintain machine configuration | Configuration changes trigger a recipe compatibility review |
| System administrator | Manage accounts and access | Administrative access alone does not grant process approval |
Use individual accounts for changes and approvals. Record the person's identity and the values before and after the change.
For higher-consequence changes, require a different person to approve the draft. If staffing makes that impractical, document the review arrangement and restrictions before enabling recipe editing.
Define temporary access with the same care: who grants it, what it permits and when it ends.
How should allowed ranges be validated?
Check values while the draft is edited, then check them again in the controller before accepting the requested recipe.
Specify limits by parameter, product and machine configuration where necessary. A value being within a machine's overall range should not, by itself, make it acceptable for every product.
Include checks for:
- Required values, units and permitted decimal precision.
- Minimum and maximum values.
- Relationships between parameters.
- Compatibility with the installed equipment and operating mode.
- Missing, unknown or unsupported parameters.
For example, specify that a lower temperature target must remain below its upper target. Treat this relationship as a validation rule, rather than relying on separate range checks.
Reject invalid requests with a useful explanation. Identify the parameter, submitted value and required correction. Do not silently replace an invalid value with a limit and then report success.
Document these rules in the functional design specification, including who owns each limit and how limit changes are approved.
What should a download acknowledgement confirm?
Make the distinction between “sent,” “accepted” and “active” visible to the operator.
Define a download as a request with a unique transaction identifier, recipe identifier, version and intended machine. Transfer the values into a staging area, validate the complete set, then issue a controller acknowledgement tied to that request.
The acknowledgement should state whether the request was rejected, accepted for later activation or activated. Include a reason when it is rejected.
Require confirmation of the accepted recipe identity and version, together with a readback or agreed integrity check of the parameter set. Also define how values are represented so that harmless formatting differences do not create ambiguous comparisons.
Avoid writing directly into individual live parameters as they arrive. Specify that the complete validated set becomes active together.
If communication stops before acknowledgement, show the outcome as unknown until it is reconciled with the controller. Before retrying, check the transaction status. Define repeat requests so that they cannot accidentally activate the same change twice.
What should happen during an active cycle?
Choose an activation policy for each machine and process. For a discrete cycle, a useful default is to keep the active recipe fixed until the cycle finishes and the machine reaches its defined changeover state.
Keep three identities visible:
- Selected: the recipe the operator has chosen.
- Pending: the validated version waiting for an activation condition.
- Active: the version governing the current cycle.
Changing the selection should not change the active values.
Define exactly what permits activation. “Machine stopped” is too vague: specify the relevant sequence state, material condition and required checks. Agree these conditions with the people responsible for the process, and review safety-related conditions with a qualified assessor.
If an urgent adjustment is necessary, use a documented procedure covering the current product, equipment state, authorisation and restart checks. Do not make an ordinary recipe download an informal route around that procedure.
Record the active version against the cycle or batch. Where controlled live adjustments are permitted, record their values and effective point as well.
What would a controlled change look like?
The following example is illustrative. Its values are not operating recommendations.
An approved recipe uses a temperature target of 160 degrees Celsius and a dwell time of 20 seconds. A proposed version changes them to 165 degrees Celsius and 22 seconds.
- The process specialist creates a draft from the approved version and records the reason.
- Validation checks the proposed values, their relationship and machine compatibility.
- The approver reviews the differences and releases the new version.
- The operator requests it while a cycle is running.
- The controller validates the complete request and acknowledges it as pending.
- The current cycle finishes using the existing version.
- At the agreed changeover state, the controller activates the new version and confirms its identity.
- The next cycle records that version as its operating recipe.
If acknowledgement is missing, the display shows an unresolved request. It does not assume that the new version is active.
Before commissioning this behaviour, test the interruption points as well as the successful sequence. For a retrofit, include those checks in the shutdown and commissioning plan.
What common mistakes should you avoid?
Allowing edits to approved recipes. Create a new version so the previous production record retains a stable meaning.
Trusting only the screen's validation. Require the controller to check every incoming recipe request.
Displaying the selected recipe as active. Show selection, pending acceptance and confirmed activation separately.
Ignoring adjustments made outside recipe screens. Include maintenance screens and remote interfaces in the same permission and recording rules.
Automatically restoring an old version after a fault. Define recovery explicitly. Recheck approval, machine compatibility and activation conditions before restoring it.
Leaving restart behaviour unspecified. Decide how pending requests and active values are recovered after power loss, and require reconciliation before production resumes.
How can you check the design before handover?
Ask for a witnessed demonstration of these acceptance checks:
- An unauthorised user cannot edit or approve a recipe.
- Invalid values and incompatible versions are rejected with clear reasons.
- An interrupted transfer leaves the previous active parameter set intact.
- A request during a cycle follows the agreed activation policy.
- Repeated requests and missing acknowledgements produce clear, recoverable states.
- Restart recovery identifies the actual active version.
- The production record identifies the parameters used.
Keep the observed results with the handover record. These checks should demonstrate behaviour on the machine, including failure handling.
What questions come up about PLC recipe management?
Should every recipe change stop the machine?
Define this by process. A discrete machine might activate between cycles. A continuous process needs an agreed transition procedure, potentially including controlled adjustments and treatment of material produced during the change.
Can operators make small adjustments?
Yes, if the design defines the adjustable parameters, permitted limits and required authority. Record the actual adjustment against production. Decide whether it is temporary or must become a newly approved recipe version.
Is restoring an older recipe a rollback?
Treat it as a new activation request. Confirm that the older version remains approved and compatible, then apply the same validation and acknowledgement rules.
Where should recipe ownership be agreed?
Name the owners of recipe content, approval, machine validation and production records in the specification. For help defining those responsibilities, see our control systems services and frequently asked questions.