I did many of these systems for the brewing industry over the years. Could write a book about the subject, but I'll try not do it here.
I always built the system to automatically step thru the process from beginning to end, but gave the operator the option to pause and resume the process at any time. Also provided the operator the ability to step forward or backwards in the program.
Sometimes, the program had a built-in pause in it, to permit the operator to install a gasket, or replace a manway cover. He then hit the "Resume" button to continue.
In later years, I found more and more users requiring some form of printed record of the cleaning cycle, which recorded flows, pressures, temperatures, and solution concentrations. This became part of the HMI project design.
Most users required multiple programs, depending on the type of cleaning they wished to do: ie
1. PreRinse
2. Caustic Wash
3. PostRinse
4. Acid Wash
5. PostRinse
6. Sanitizer
7. PostRinse
other programs would omit certain steps. eg. Rinse/Caustic/Rinse only, or Acid only etc.
The program would also vary, depending on the equipment being washed. A pipe-only route would require that each solution be chased or pushed out with the following solution, whereas tanks would require a pause after each solution to allow the sides of the tank to drain and return the solution before going on to the next. Also, with tanks, it was usually necessary to start and stop the supply pumps to prevent solution accumulation in the tanks, leading to a "bathtub ring"in the tank.
I could go on for a few more pages. If there's any topic you'd like to discuss, just pm me.
Walter