Defining interlocks for the non-programmer

[mylespetro]

If we do an HMI - we always post an interlocks screen. I also always have all of the I/O on screens - with descriptions - so you can quickly see if an I/O point is on or off.

This is the easiest way to go that I know of, and most skids/HMIs developed by large SIs that I come across have something along these lines. An example from a recent project (I didn't create this HMI runtime):

Nice to be able to pull up the interlocks if something won't start/turn on and see what's holding you out. The red obviously would be green if the interlock is satisfied, which even people who aren't super well-versed would be likely to understand.

 

[Phrog30]

+1 on posting on an HMI. If your HMI is developed "correctly" this is an easy step. Look at PlantPax for inspiration.