SCADA Software UI Design-1
SCADA Software UI Design-1
COMPONENTS TO MAXIMIZE
PLANT PRODUCTIVITY
How Enhancing Design Can Benefit Operators AND
Increase Profits
In 2013, American international beauty company
Avon Products Inc. halted the global rollout of
a $125 million dollar new order management
system that had been 4 years in the making.
Avon CEO Sheri McCoy later told analysts,
“While the pilot technology platform worked
well, the degree of impact or change in the
daily processes to the representative was
significant. This resulted in a steep drop in the
active representative count.” The difficult-to-use
software interface drove huge numbers of their
sales force to quit. As a result of this and other
factors, Avon ended up selling 80% of its North
American business to refocus on other countries.
This modern-day Aesop’s tale is revealing because it speaks
of the huge impact of user experience (UX) in software. For
industrial control systems, bad UX is the silent killer that steals
your company’s time, money, and overall productivity. That clunky
software you hate but have to use at work every day? Most likely
it’s a problem with poor user interface (UI) design, not functionality.
Something that should happen in three clicks instead takes four
times as long. That extra 30 seconds spent reading confusing
SCADA screens can cause operators to stop regularly checking
daily tasks, potentially letting small problems snowball into huge
problems with delivery dates and tainted products.
Unresolved
errors
Employee
loss
Figure 1. The seemingly minor thirty seconds lost because of a confusing UI can
snowball into a loss of productivity, accurate feedback from the field, and even
knowledgeable employees.
A PICTURE IS WORTH A
THOUSAND WORDS
Improving SCADA HMIs is not a new concept. We’ve come a
long way since the “mimic displays” of the 1970’s that only used
lights, gauges, and push buttons for highly experienced operators
to interpret and run the plant. The addition of computers
allowed access for more data to be displayed as high-density,
monochromatic text or text-based graphics, but a high level of
expertise was still required to accurately utilize that information.
Figure 3. The SCADA GUIs of the 1990’s boasted of new color capabilities, but not
much consideration was given to readability or effectiveness for actually running a
plant. (Source: Automation.com)
Usability
Most engineers create SCADA systems from the machine’s
perspective, not from the user’s. Usually the SCADA screens are
constructed after the PLC code is written, and its functionality has
to bend to support the code. Instead, we believe in designing
the UI with ease of use for the operator first in mind . Usability
combined with sound design principles leads to an intuitive and
valuable tool that benefits all.
1. Color
Color (and specifically contrast) is so powerful because it often
communicates before all other visual factors like text are taken into
account. As designers, we use this innate ability to convey instant
meaning to objects, to draw attention to specific places that may
need focus, and to distinguish items from each other.
Color and their meanings are learned over a lifetime, which when
used properly, provide a lifetime of training to a user. By using an
Figure 6. Intuitive use of color provides contextual clues to the operator for instant
recognition of process states. In another award-winning project by Vertech, we
used a clean color palette with properly contrasting text, where a bright, warm
orange draws attention from the dimensional, cool gray background. Instead of
drop shadows, we went with cleaner lines to emphasize the dimensional gradients
and avoid too much noise.
Figure 7. Taking advantage of human visual behaviors, like the F-shaped pattern
for reading content, speeds up understanding of information and reduces
training. (Source: Nielsen Norman Group)
3. Navigation
Shockingly, information workers spend approximately 2 hours per
day looking for the data they need. Clearly, there is a definite need
for effective software navigation. Take a look at Amazon.com. It
owes much of its success to an excellent navigation system. With an
enormous ecommerce catalog consisting of hundreds of millions of
products, people are still able to find what they want. The website
simply gets you from where you are to where you are trying to go
with minimal delay. In the same way, every SCADA software needs
SCADA software needs well-designed navigation to give users access to critical information
well-designed navigation quickly and intuitively . Basic rules of thumb include:
to give users access to
+ A hierarchy should be consistent
critical information quickly
and intuitively. + The navigation bar should be in the same place on all screens
Figure 8. Clear and obvious icons can immediately convey information, especially
in situations when time may be of the essence. In this craft brewery control
system, Vertech used high-contrast icons on a pop-out navigation menu, similar
to web and mobile UIs. Additionally, space was left for future expansion, such as
packaging, quality control, and shipping.
6. Functional Use
A good SCADA system must of course be functional, not just nice
looking. No point in improving its appearance if the operators
can’t do their job at the end of the day. The key is to design with
user operability in mind while not compromising required system
functionality. Ultimately, the UI of a SCADA system must fulfill
its primary directives of allowing people to monitor and operate
equipment, identify and respond to problems, and meet the
functional control specs. While having good UX is desirable for
the long-term success and efficiency of a SCADA platform, the
immediate parameters that engineers care about most – such
as response time, available actions, and feedback – must be
addressed. The best industrial automation systems are able to
combine functionality and standards with usability.
7. Future Scalability
The best industrial Sometimes companies can unintentionally paint themselves
into a corner. When designing a new SCADA system, the list of
automation systems
requirements is laid out and delivered exactly as specified. But
are able to combine
what happens at the end of the software’s life cycle five to ten
functionality and
years later? What if your organization absorbs another company
standards with usability. and two different systems must be combined? The once perfectly
designed SCADA platform has no room for expansion. Therefore,
most companies choose one of two routes: 1) rework the entire
system from scratch or 2) add on an unexpected subsystem.
What if we told you there was a third option? The key is to make
the software flexible enough to adapt to future changes because,
let’s face it, change is inevitable but also somewhat nebulous. In
1956, development of the U.S. Interstate highway system began,
and architects purposely overdesigned for larger populations and
higher throughputs. More than half a century later, their master
plans live on today and have transformed the economic landscape
and quality of life in America. History shows that scalability can
work, so how can that apply to SCADA systems?
+ What are the next paths for growth for the plant or company
that might increase manufacturing loads, performance
requirements, workflows, and employee headcount?
+ Are there any bottlenecks you can predict or have seen in the
past?
let’s face it, change with and adapting the latest innovations in industrial automation,
we can have foresight into what trends may be added next and
is inevitable but also
can plan accordingly to make room for future developments.
somewhat nebulous.
vertech.comvertech.com