Who is building your HMI system? If you are a vendor, then who are the designers of your standard HMI screens? If you are an owner-operator, then who are the designers of your operational screens? If the answers to these questions are your programmers, engineers, or web designers that you have hired out of college, then you probably have a low performance HMI (human machine interface). If your graphical displays look like P&IDs (piping and instrumentation diagrams) covered with hundreds of numbers and multiple colors, then you definitely have a low-performance HMI. Operational screens are not like Web pages where flash and glitter are used to draw attention to text and where the user can move a mouse over the screen to discover active links. Operational screens are used by operational staff to monitor and interact with a supervisory control and data acquisition (SCADA) or manufacturing execution system (MES) software. They provide situational awareness of the process.
Poor HMI design, higher risk
HMI screens are used to manage the operation and supervise the process. They are not intended to wow the staff with fancy distracting graphics, or to show the power of the embedded graphics processor by animating near realistic images of the equipment. These HMI designs are not really realistic because they usually reflect the equipment design image. They do not show the holes in the tanks and fluid spilling out, or the broken valves or stopped motors. Unfortunately, poor performance of the HMI system has been cited numerous times as a significant contributing factor to major industrial accidents. The U.S. Chemical Safety Board (CSB) has estimated the total loss due to operator error as $10 billion per year, and poor performing HMIs are a major cause. If your HMI was designed over five years ago, then you may now be running a multimillion-dollar operation from HMIs created when there was little knowledge of proper HMI practices and principles. Newly designed interfaces follow the principle of high-performance HMIs. A high-performance HMI is one that is designed with a consideration of user and functional requirements, with good human factor engineering, and that supports all normal, abnormal, startup, shutdown, and switchover modes of operation.
Usable and safe, not pretty
Designing a high-performance HMI (HP-HMI) is one case where it is important to follow good software engineering practices used in user interface design, and not just copy existing designs. Otherwise, you can end up with screens that resemble badly designed mobile and web designs with hidden hot-spots, small text, inconsistent color use, and too much or little information on each screen. Good software engineering practices involve usability labs and usability studies. In usability studies, users are given a minimal amount of training, usually commensurate with the minimal job skills, and then asked to perform specific tasks using the user interface. All user interactions are recorded, including mistakes and repeats to discover the good and bad aspects of the interface. The studies are often performed in a usability lab where the users can give a running commentary on the mental activity; all conversations, mouse movements, and keystrokes are recorded; and sometimes even eye movements are recorded to see where on the screen users are looking for information. All of the recordings are then analyzed to reduce user confusion, changes are made to the interface, and tests are rerun. This may sound like a lot of work, but it is actually only a small percentage of the total effort required in designing HMIs. Usability studies are often short, involving only a few hours of testing, and typically involve only one or two usability experts.
The closest analogy to high-performance HMI screens are stock market tracker screens. Normally there are only a few items that are watched all the time. In these cases, only the current values are needed to decide if any actions are required. Most items are watched only when they reach limits. These can be actual limit values, or when the trend indicates that an item is approaching a limit. Then the user may drill down to see the trend, maybe look at a longer term trend, or link to related information. The purpose of the interface is not to control the process, but to provide situational awareness and supervision of automated activities.