How information ascends to the cloud for greater utilization

Modern instrumentation delivers data, but too often it serves no purpose.

By Ryan Williams October 29, 2019

Smart instruments have been available since the mid-1980s when first 4-20mA HART devices entered the market, quickly followed by fieldbus-based devices. These digital communication technologies made it possible for instruments to provide more than just a process signal. Using digital interfaces, these devices were now able to send device status, diagnostics and other information.

Endress+Hauser estimates that of the 40 million of its process instruments installed worldwide, 90% are digital, smart devices. These smart instruments provide an incredible amount of information at “the Edge” that is of immense benefit a wide range of host systems and IIoT applications, such as maintenance management, asset management, inventory control, manufacturing execution systems (MES), enterprise resources planning (ERP), and so forth. But one major problem facing industrial plants is: How do we manage all this data?

If a single smart instrument, such as a Coriolis meter, delivers a few dozen items of status and diagnostic information, and a plant has several thousand similar instruments (Figure 1), it’s a given that the host systems must deal with huge amounts of data derived in real time.

Because of the immense amount of data, and problems in managing it, Endress+Hauser estimates that 97% of the data is not being used. Instead, automation systems use the flow, pressure, temperature, level and other data needed to control the process, and ignore or discard status, diagnostic and other data.

Major instrument manufacturers are well aware of the problem, and several are now delivering solutions to acquire data from the Edge and making it available tot to specialized IIoT software — all without affecting or involving the automation system. Let’s take a quick look at the concepts behind these solutions.

Handling massive data

As noted above, a smart instrument generates a great deal of status, diagnostic and other information. An Endress+Hauser Proline flowmeter, for example, can detect entrained air, vibration (which could be caused by pump cavitation), coating, corrosion and inhomogeneous or unsuitable media. In fact, the flowmeter can detect 125 different problems. When process conditions warrant a notification (Figure 2), the flowmeter generates an event message.

While the automation system is mostly interested in flow values and alarms, IIoT software wants to know about the warnings shown in Figure 2, as well as diagnostics and other data.

Many smart instruments can provide diagnostics to indicate problems with electronics or subcomponents. For example, Proline Coriolis flowmeters can monitor oscillation damping and frequency, temperature, signal asymmetry, exciter current, carrier pipe temperature, frequency fluctuation and other parameters. Changes in these parameters indicate potential problems.

While every instrument manufacturer’s diagnostics differ, each typically monitors internal parameters, observes changes and diagnoses problems. Any further analysis must be done by IIoT maintenance software, which means status and diagnostic data needs to be transmitted to this software.

In many cases, this is accomplished by the automation system, which periodically asks each instrument for the data, then stores it in an online database, such as a process historian. Maintenance management software accesses what it needs from the historian and performs its analysis.

This type of solution presents problems. Networks can be unduly burdened with data transmissions, historians can become bloated, and there can be lags between data collection and recognition by the IIoT software.

Data is collected only periodically because the automation system can’t deal with the massive amount of status and diagnostic data from hundreds or thousands of instruments. The data is stored in a database, which must be accessed from the maintenance software, adding even more delays.

A better solution — now being offered by several major instrument manufacturers — is to provide all the data available at the edge to IIoT software via the cloud, thus bypassing the automation system completely.

Connecting at the edge

The 30+ million digital instruments currently installed worldwide communicate with their automation systems via different interfaces, including Profibus, 4-20mA HART, WirelessHART, EtherNet/IP, and several others. However, many eventually connect to an Ethernet-based network (Figure 3), where the data can be acquired by a specialized “edge device.”

The edge device is programmed to extract instrument data from the network and transmit it to IIoT software in the cloud.

An edge device can also be installed on a smaller system, such as a pumping station, that may or may not be connected to a plant’s Ethernet network, or to instruments that are connected to an older, non-Ethernet system. In that case, each instrument is wired to a nearby “edge gateway” device which collects data from devices and transmits it to the cloud.

Once the instruments are connected to an Ethernet-based network that is ready for IIoT connection, the appropriate edge device is selected. Various edge devices are available from instrument manufacturers to handle expected data rates.

For example, Endress+Hauser has multiple approaches to select the right edge device for the right quantity of instruments transmitting information to the cloud. At a site where there are hundreds of instruments, the edge device has high-speed data acquisition to push the information to the cloud. Conversely, instrument-based edge devices are offered that run at basic speed, transmitting small amounts of information to the cloud.

All data transmission is one way from the device to the cloud. Cybersecurity is deployed within data transmission, edge devices, and cloud services connectivity.

Living in a cloud

Major instrument manufacturers provide software that uses data from the edge to diagnose problems, schedule maintenance activities, analyze processes, predict problems and so on.

For example, cloud software consists of several components:

Instrument diagnostics: Software built into modern instruments monitors device status and process conditions, and provides data needed for further analysis. Endress+Hauser embeds “Heartbeat Technology” into its instruments to provide status and diagnostic information, and to perform vital functions such as condition monitoring and in-situ verification.

During verification, the current conditions of various parameters are compared with their reference values, thereby determining the device status. The technology produces a “pass” or a “fail” statement based on the tests, which is performed by traceable and redundant internal references. The individual tests and results are automatically recorded and used to print a verification report.

Cloud connection: Software and hardware are needed to extract data from the plant’s Ethernet network or from individual devices and transmit it to the cloud-based software. At Endress+Hauser, this is accomplished with Netilion Connect, which consists of edge devices which acquire the data, a cloud platform that hosts the IIoT software and an application programmable interface (API).

The API provides a way to connect cloud-to-cloud or cloud-to-apps in a simplified way. It enables customers to use IIoT in a simple and efficient way without the complexity of IT-based computer science.

The ecosystem is based on an open source technology platform that is common in our industry and — like other vendor’s ecosystems — offers these functions:

Analytical software: Analytics processes data generated by the technology to assess instrument health, analyze and predict problems, schedule maintenance, etc.

Process health: Health software analyzes instrumentation at the edge to determine if the process is getting more difficult to control, if external influences are having a detrimental effect on performance, or if changes need to be made. For example, water treatment plants can monitor incoming surface water. The system monitors conductivity, pH, dissolved oxygen and other parameters, and issues warnings to operators.

Equipment documentation: Maintenance technicians need access to equipment manuals, troubleshooting instructions and other materials describing each instrument. Library software logs in all pertinent information and makes it available to technicians on request.

Getting started

Implementing such a system might appear challenging, but several factors help simplify the effort.

First, few plants are exclusive to a single instrument vendor. All this instrumentation must be identified and entered into the system, along with their manuals, error codes, diagnostic information and other pertinent data. This is normally done during an installed base analysis.

Fortunately, modern instruments typically are identified with bar codes or labels that can be scanned to identify the vendor and product. Then, the necessary data can easily be downloaded from the vendor’s web site.

Second, there’s no need to implement a plant-wide system right away. Most vendors provide a “start-up kit” that allows a plant to try out the concept. For example, Endress+Hauser offers a free trial version for up to 15 assets with a typical plant introductory IIoT package that can connect as many as 500 instruments to its cloud software.

Final words

Modern instruments provide a wealth of information about their health and the process they’re monitoring, but few plants use all that data. Today, major instrument manufacturers are providing hardware and software solutions that bring all the data available at the edge to IIoT software for analysis and corrective actions.

This article appears in the IIoT for Engineers supplement for Control Engineering and Plant Engineering.

Author Bio: Ryan Williams is the national product manager for Solutions and Service at Endress+Hauser USA. He graduated from Purdue University in 2005 with a degree in electrical and computer engineering technology. He came to Endress+Hauser with more than 14 years of experience at Rockwell Automation and has been with the company since 2018.