Setpoints, Schedules and Process Recipes

A setpoint is a target; an operating range recognises controlled variation; a schedule changes targets over time; a process recipe combines these with equipment states and sequence logic.

Fermentation, cooking, cooling, smoking and drying schedules must fit product size, casing, load and required endpoint. Copying a programme between products can invalidate its assumptions.

Recipe name, revision, authorisation and change history should be controlled. Unrecorded edits to time, temperature, humidity, fan or damper logic undermine traceability.

A controller may command one condition while the chamber or product experiences another. Recorded sensor values, product measurements and alarm history show performance.

Power loss, sensor failure, manual override and aborted stages require defined response. The system should preserve data and prevent silent continuation after a critical failure.

Lock authorised recipes, verify loaded version at start-up and retain actual records with the batch. Review trends and deviations before release, not only after complaints.