The cycle as a state sequence
A recipe defines target quantities for individual ingredients. Execution coordinates weighing, transfer, mixing and discharge with equipment state. Each stage needs explicit entry, completion and stop conditions. For example, admitting new material while the discharge gate is open is a sequencing problem that a screen warning alone cannot resolve. The relevant permissive belongs in the control logic.
Example: target versus actual quantity
In an illustrative recipe, a water target of 180 kg and a measured result of 182 kg should remain separate fields. Record the recipe version, target, actual quantity, any moisture adjustment and operator intervention. Link the adjustment to its measurement and method. These numbers explain record structure; they are neither a suitable concrete recipe nor a recommended acceptance tolerance.
Interruption, validation and scope
After a power or communication interruption, the application should not blindly start another cycle. Reconcile material already present, scale condition and the last completed step; do not report a partial cycle as completed production. Commissioning tests should cover sensor loss, gate feedback and operator cancellation alongside normal operation. An automation record does not replace concrete quality testing.