Do it yourself HMI

Technology Update: Should you build or buy a human-machine interface (HMI)? Developing PC-based HMI software may seem a simple task, but there are pitfalls. Configuring a purchased HMI software package is often a better long-term option. A table compares HMI software development versus configuration.

06/08/2015


Figure 1: Some suppliers of PC-based HMI software support services and develop applications from scratch by working closely with OEM partners. Courtesy: Wonderware by Schneider ElectricPC-based human-machine interface (HMI) software has been around since its original introduction by Wonderware in the 1980s. Machine builder original equipment manufacturers (OEMs), system integrators, and end users saw its potential immediately, spawning the success of many additional HMI software companies.

But many users also saw the potential to develop their own PC-based HMI applications, motivated primarily by the desire to avoid up-front costs for HMI development software packages and runtime licenses.

Now that we're decades into these developments, we can look at each approach and evaluate advantages and drawbacks. While buying makes sense for many, making is a viable approach in some instances.

When to develop software internally

While creating an HMI application may seem relatively simple to an experienced programmer, maintaining the software over the long-term inevitably turns into a major effort. For this reason, internal development of HMI software should only be undertaken when the following conditions exist.

First, internal development typically doesn't make sense for an end user as there simply won't be enough deployments over which to spread development costs. It might make sense for a machine builder OEM, but only in certain circumstances.

  • The OEM must produce machines in large volumes to amortize development costs over many units.
  • The HMI application should be relatively simple to keep development and maintenance costs down.
  • There must be at least two capable HMI programmers in-house.

Two or more programmers are needed because reliance on one individual isn't a good idea, as the HMI application is not finished after the first machine is up and running but must be maintained over the life of the machine, which often spans decades. If there's only one programmer, and the person leaves the company, maintenance becomes problematic. With two or more programmers, software maintenance can be handled jointly, a much safer approach. New programmers joining the company must also be fully trained to maintain continuity.

The embedded approach

Figure 2: Embedded HMI platforms provide a lower cost solution than PC-based HMIs and should be considered for many machine builder OEM applications. Courtesy: Wonderware by Schneider ElectricIf all of these conditions are met, internal development of HMI software can be a viable option, but one more factor should be considered. If the HMI application is relatively simple, which is a requirement for internal development, purchasing embedded HMI software can be a better choice than either internal development or a purchased PC-based platform.

With the embedded approach, the OEM buys display hardware with an HMI runtime license already installed (see Figure 2). While an embedded HMI may not have all of the features of a PC-based HMI, most offerings are certainly capable enough for many OEM applications, and they will always be much less expensive than a PC-based HMI, both upfront and long-term. But if the embedded HMI approach just won't work for some reason, and if the OEM is determined to develop the application in-house, these concerns must be addressed.

Updating complications

Internal development of HMI software is much simpler than it was decades ago, primarily due to the emergence of better programming languages such as Visual Basic. Most of these languages can run on Linux- or Microsoft Windows-based platforms.

Linux will be the less expensive option because the software is cheaper than Windows and because the Linux box will be cheaper than a PC. But using Linux adds even more complexity to the equation, so only the PC-based approach is discussed below.

Problems with the PC-based approach often arise after the first application has run through its lifecycle for the initial machine application. At that point, a new or upgraded machine is introduced, and the software must be updated. Other problems may surface due to new versions of operating systems or hardware platforms that no longer support the existing code.

Updating the HMI software for a new or upgraded machine may not be overly difficult if the original programmer is still around. Not only can the software be upgraded, new features can also be added, and bugs can be fixed.

The same is true when the operating system or hardware platform is made obsolete, but in this case the drawbacks of the in-house approach surface as compared to purchased HMI software.

With purchased software, the supplier will typically have new versions of the software ready to go upon introduction of a new operating system. Some suppliers provide import functionality so older HMI applications can be easily upgraded to the new operating system, making this task relatively simple.

When the software is developed internally, the task of ensuring compatibility with the new operating system falls to in-house resources, adding greatly to costs.

These upgrade issues are significantly exacerbated if the original developers are no longer with the OEM, particularly if the code wasn't documented properly. 

Transferring ownership

If none of the original developers of the HMI software have remained, it becomes necessary for one or more new developers to take ownership of the existing and new applications. Significant time is often needed to determine how to fix or change the feature set.

The same is true when creating and incorporating new functionality and then testing the results to ensure no new issues have been introduced. Bug fixes in particular can be problematic, as this task often requires in-depth knowledge of the HMI software.

Transfer of ownership is made easier if the original software and all subsequent changes were made in a structured fashion and meticulously documented, but this is not typical. In most instances, HMI software is developed and maintained somewhat haphazardly, making it difficult or even impossible for the new programmer to maintain the application.

In many, if not most cases, an HMI developed internally often relies on programming tools and methods unfamiliar to a wide group of programmers, and eventually its viability begins to rely on the one person who created the HMI. If that person is no longer around, the new programmer must reverse engineer the code, a time consuming and very difficult task.

To avoid these and other issues, a better choice may be to purchase HMI software from an established supplier, and then configure this software for the particular application. While configuration of purchased HMI software does require some expertise, it's a much simpler proposition than writing code from scratch.

Buy instead of make

While internally developed HMI programs are successful in some applications, software packages such as Wonderware InTouch Machine Edition have a short configuration learning curve compared to VB.NET and C# code development, deployment, and maintenance.

Modern HMI software packages provide intuitive interfaces to develop most necessary functionality (see Figure 3). They also typically contain the connectivity required to interface to most real-world hardware devices in a variety of protocols, simplifying system configuration.

Figure 3: Purchased PC-based HMI software provides a wide range of built-in graphical elements for use in screen design. While internally developed HMI programs are successful in some applications, software packages such as Wonderware InTouch Machine Edit

Purchased HMI development software, with its built-in advanced tools, helps reduce many of the issues encountered by new users. Configuration of functions and communications using fill-in-the-blank panels reduces problems and development time.

Many built-in HMI features would be very difficult or impossible for an OEM to develop from scratch. Purchasing HMI software eliminates the need for the OEM to "reinvent the wheel" when configuring a full-featured HMI application. 

Use an integrator

If in-house resources are insufficient to configure the purchased HMI software, or if the application has a very high degree of complexity, an OEM can use a system integrator. The integrator should be certified by the HMI supplier, as this will ensure a level of competence with the product and a track record developing successful HMI applications.

This may be a prudent choice as the right integrator will have the resources to provide technical support via an engineering staff with years of experience in a variety of applications and industry verticals. This can help an OEM get its equipment to market quickly.

If for some reason it is not possible to use the same integrator for product updates or improvements, the software supplier can provide contacts for other certified integrators to take over project development and maintenance.

This option can be a particularly good choice if the OEM has an on-going partnership with an integrator familiar not only with the HMI software, but also with the OEM's specific applications. When internal resources aren't sufficient, and when a suitable integrator isn't readily available, the HMI software supplier may be able to assist. 

Engage the supplier

A quicker and possibly more cost-effective solution is to engage the services of the HMI software provider (see Figure 1). This option provides direct access to experienced application engineers who can debug an existing application or build a turnkey solution from the ground up.

While all HMI software suppliers offer some level of support, associated costs vary widely, as does the extent of services provided. Some suppliers provide free or low-cost support, while others charge quite a bit more. Some suppliers offer turnkey solutions, while others prefer to refer customers to integrator partners.

But if the HMI software supplier does offer a sufficient array of services at a reasonable cost, this can be an attractive option since no one knows the software as well as the supplier. Very often, the software supplier's staff will have a great deal of experience in creating safe and secure software applications for OEMs and other customers.

Table: Nine criteria can help evaluate if internally developed HMI software is a better option than configuration of purchased software. Courtesy: Wonderware by Schneider Electric

While internal development of HMI software is easier now than in years past, configuring purchased HMI software is simpler. And internally developed software has other pitfalls, particularly with respect to long-term maintenance of deployed applications (see Table 1). As many OEM machines have life spans measured in decades, software maintenance will be required, and it's simpler to maintain applications configured using purchased HMI software.

- Richard Clark, an InduSoft Web Studio application developer at Wonderware by Schneider Electric; edited by Mark T. Hoske, content manager, CFE Media, Control Engineering, mhoske@cfemedia.com.

Key concepts

  • Various tools make do-it-yourself HMIs a tempting choice.
  • Costs of creating an HMI extend far beyond initial investment; wait for the upgrades.
  • Maintenance of deployed applications can be considerably easier with purchased software.

Consider this

Lower initial cost of do-it-yourself software may not make sense after considering lifecycle costs.

ONLINE extra

Richard Clark, as an InduSoft Web Studio application developer, oversees marketing, engineering, support, and security of third-party products for Wonderware by Schneider Electric.

- See additional stories about information systems and HMIs below.



The Top Plant program honors outstanding manufacturing facilities in North America. View the 2015 Top Plant.
The Product of the Year program recognizes products newly released in the manufacturing industries.
Each year, a panel of Control Engineering and Plant Engineering editors and industry expert judges select the System Integrator of the Year Award winners in three categories.
Pipe fabrication and IIoT; 2017 Product of the Year finalists
The future of electrical safety; Four keys to RPM success; Picking the right weld fume option
A new approach to the Skills Gap; Community colleges may hold the key for manufacturing; 2017 Engineering Leaders Under 40
Control room technology innovation; Practical approaches to corrosion protection; Pipeline regulator revises quality programs
The cloud, mobility, and remote operations; SCADA and contextual mobility; Custom UPS empowering a secure pipeline
Infrastructure for natural gas expansion; Artificial lift methods; Disruptive technology and fugitive gas emissions
Power system design for high-performance buildings; mitigating arc flash hazards
VFDs improving motion control applications; Powering automation and IIoT wirelessly; Connecting the dots
Natural gas engines; New applications for fuel cells; Large engines become more efficient; Extending boiler life

Annual Salary Survey

Before the calendar turned, 2016 already had the makings of a pivotal year for manufacturing, and for the world.

There were the big events for the year, including the United States as Partner Country at Hannover Messe in April and the 2016 International Manufacturing Technology Show in Chicago in September. There's also the matter of the U.S. presidential elections in November, which promise to shape policy in manufacturing for years to come.

But the year started with global economic turmoil, as a slowdown in Chinese manufacturing triggered a worldwide stock hiccup that sent values plummeting. The continued plunge in world oil prices has resulted in a slowdown in exploration and, by extension, the manufacture of exploration equipment.

Read more: 2015 Salary Survey

Maintenance and reliability tips and best practices from the maintenance and reliability coaches at Allied Reliability Group.
The One Voice for Manufacturing blog reports on federal public policy issues impacting the manufacturing sector. One Voice is a joint effort by the National Tooling and Machining...
The Society for Maintenance and Reliability Professionals an organization devoted...
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.
Maintenance is not optional in manufacturing. It’s a profit center, driving productivity and uptime while reducing overall repair costs.
The Lachance on CMMS blog is about current maintenance topics. Blogger Paul Lachance is president and chief technology officer for Smartware Group.
The maintenance journey has been a long, slow trek for most manufacturers and has gone from preventive maintenance to predictive maintenance.
This digital report explains how plant engineers and subject matter experts (SME) need support for time series data and its many challenges.
This digital report will explore several aspects of how IIoT will transform manufacturing in the coming years.
Maintenance Manager; California Oils Corp.
Associate, Electrical Engineering; Wood Harbinger
Control Systems Engineer; Robert Bosch Corp.
This course focuses on climate analysis, appropriateness of cooling system selection, and combining cooling systems.
This course will help identify and reveal electrical hazards and identify the solutions to implementing and maintaining a safe work environment.
This course explains how maintaining power and communication systems through emergency power-generation systems is critical.
click me