Setpoints, Schedules and Process Recipes

Definitions

A setpoint is the target given to a controller. An operating range describes acceptable controlled variation around or between defined limits. A schedule changes targets or equipment states over time. A process recipe combines the sequence, setpoints, ranges, stage-transition rules, equipment states and product identity for a defined process. A critical limit is different: it is a food-safety boundary established through the HACCP or equivalent control system. These terms should not be used as synonyms.

What a process recipe contains

Depending on the operation, it may specify product and batch size, chamber or machine, stage order, time, air temperature, relative humidity, smoke application, fan and damper state, product-core target, cooling endpoint, pH or water-activity checks and hold conditions. It should also identify the variables that are instructions and those that are release criteria. An equipment programme that contains only time and air temperature may be incomplete for a process controlled by product core, humidity or another critical factor.

Product-specific basis

Schedules must match the validated product and operating conditions. Diameter, shape, casing, formulation, initial temperature, load size, rack arrangement, chamber airflow, smoke system and equipment response can change the result. Copying a programme from a different sausage, whole muscle, chamber or manufacturer can invalidate the assumptions behind it. Regulatory examples for thermal processing explicitly treat product, container, equipment and critical factors as part of the scheduled process; the same discipline is useful when defining other controlled processes.

Version and authorisation

Give each recipe a unique name, revision, effective date and approval status. Record why it changed and which products and equipment the revision covers. Protect authorised recipes from casual editing. At start-up, verify the recipe name and revision loaded into the controller against the batch instruction. A printed master should not disagree with the active machine file. Obsolete versions should remain identifiable but unavailable for unintended use.

Setpoint versus achieved condition

A controller output is an instruction, not proof of the chamber or product condition. Heating, cooling, humidifying or fan commands can be active while the measured environment remains outside range. Record actual sensor values, product measurements, stage changes and alarms. Where the control sensor is located near a coil or air outlet, a separate mapped monitoring sensor may better represent the load. Product-core and endpoint measurements remain necessary when the process depends on them.

Stage transitions and tolerances

Define whether a stage ends by elapsed time, clock time, product measurement, cumulative treatment or another condition. Specify acceptable overshoot, undershoot, delay and minimum hold time where these affect the validated outcome. Automatic transition can be unsafe if a failed or misplaced sensor falsely satisfies the condition. Manual confirmation can add control but also adds dependency on training and timely action. The selected logic should be challenged during commissioning and process validation.

Failure and deviation logic

Define what happens after power loss, sensor failure, alarm, manual override, aborted stage or communication failure. The system should preserve the batch history and not silently restart at an unknown point. If actual conditions do not meet the approved schedule or a critical factor is outside its requirement, treat the event as a deviation. Hold affected product and assess the exposure, cause, corrective action and disposition before resuming or releasing it.

Verification and change control

Compare programmed values with the approved recipe, verify sensor and actuator response, and confirm performance under representative loads. Review recipe files after software updates, controller replacement, maintenance or restoration from backup. A small change in fan logic, humidity control, timing or alarm delay can materially alter drying or heat treatment. Revalidation or focused confirmation is required when the change affects the scientific support or in-plant evidence.

Small-scale use. A small producer can use a written table of stages and settings rather than automated recipe software. Record the planned schedule, actual readings, adjustments, start and finish times and product endpoints. Distinguish a house preference from a validated safety boundary. A schedule taken from a book, forum or equipment preset is a starting hypothesis, not automatically a safe and suitable process for the product, load and jurisdiction.