LoRaWAN: A Clipboard Killer for Condition Monitoring


Manufacturers of all sorts have long sought a balance between tasks best done by automation and those best done by human beings. In recent years, this has shifted in favor of automation due to more capable technologies coupled with a decline in the availability of qualified people. One area where this has been particularly visible is the traditional practice of sending out humans on manual inspection and data collection rounds. In these activities, an operator with a clipboard or a more sophisticated recording device follows a route through a facility with stops along the way to read a gauge, examine a sight glass, or perform a similar check related to a process directly, or to verify equipment condition. This may be simply a mechanistic recording of a reading, but could also include a more subjective component. After reading and noting the gauge, another step may call for an evaluation. Does the compressor sound normal? Is the centrifugal pump vibrating more today than yesterday? Is the seal leaking? Is there a faint aroma of burning lubricating oil? Some operators may be highly qualified to make such judgements based on extensive experience, but how many of those people are around today? A generation of skilled workers is quickly fading into retirement. In many industrial plants and facilities, the reality is changing, because these rounds tend to be tedious and time consuming. Also, they may not add much value to the operation, as the result is usually simply confirmation of any obvious signs of abnormality. Insightful observations are waning, leaving little potential for detecting a slowly developing problem. These characteristics make routine rounds prime candidates for automation, especially for far flung equipment (Figure 1).


Fortunately, there is no shortage of appropriate instruments capable of measuring relevant variables. The larger problem is gathering data efficiently and bringing it to a central host system. Often the equipment that needs to be monitored is spread over a large area, potentially in places that are difficult to access or are hazardous. Distance calls for a wireless solution, and there are many choices. For the balance of this article, we will examine one practical way to solve the overall challenge.

Wireless deployments

Although there are few hard statistics, it is safe to say that the majority of process manufacturing facilities have deployed wireless networks in some capacity. Wi-Fi networks, first set to cover offices, now extend into production areas to facilitate mobile workers and a wide variety of other purposes, but few support instrumentation or field devices of any kind. Many progressive companies have deployed other types of wireless networks specifically for device-level support, such as ISA-100.11a and WirelessHART. These networks are well suited for process instruments and actuators involved in process control, supervised by a distributed control system (DCS), and serving similar functions as wired counterparts. Although these two protocols are incompatible, they share many functional similarities:

  • Similar communication distances, for example up to 500-m line-of-sight for ISA-100.11a.
  • Extremely high signal reliability.
  • Ideal for high-density installations.

So, what is the answer for an engineering team that wants to deploy temperature and pressure sensors in condition-monitoring rather than process-control applications? Either of these device-level networks is better than Wi-Fi, but there are still drawbacks:

  • Condition-monitoring instruments do not need frequent updates.
  • Data from a condition-monitoring instrument will have to be separated from the process instruments on the same network so it can be sent to other people.
  • Equipment needing condition-monitoring instruments will likely be more spread out, so longer communication distance coverage is desirable.
  • Battery life is often insufficient.
  • Most installations require repeaters.

The answer is choosing a wireless protocol suited for the specific requirements of condition monitoring, rather than trying to make it fit in a less optimal solution. What does that look like?

Alternative wireless protocol

The requirements for a wireless protocol supporting condition-monitoring instruments are different from those for a network supporting process devices:

  • Longer distances may need to be covered.
  • Lower update rate is typical, often hourly as opposed to every few seconds for a process device network.
  • Lower signal reliability is tolerable.
  • Long battery life may be needed.

This can be satisfied by a different wireless protocol, originally designed for smart city and other industrial purposes: LoRaWAN. This low-power, wide-area networking protocol (figure 2) is supported by the LoRa Alliance and used by 500 IoT-related companies globally.


Combining sensor and LoRaWAN transmitter

Since the introduction of WirelessHART and ISA-100.11a about 13 years ago, the range of native process instruments has grown enormously, but sensor selections have been largely limited to devices with low power consumption. Offerings designed for equipment condition monitoring tend to focus on tell-tale variables, including temperature, pressure, and vibration. Let’s look at how the first two can be applied. Temperature sensors are designed to work with various types of thermocouples, including B, E, J, K, N, R, S, T and C. The transmitter can support the full measuring range of each type, so low as well as high temperature measurements are possible. The actual temperature sensor can take any typical form and be mounted separately from the transmitter, or it can be attached directly. This allows monitoring anything from gases and liquids flowing through a pipe to electric motor bearings. Pressure sensors for condition monitoring tend to be basic in-line gauge pressure measuring devices, which can be mounted directly like a mechanical gauge or connected to the process via impulse lines. Frequently, the new wireless transmitter can be mounted in the same location as a mechanical gauge it is replacing. Typical applications might include monitoring the output pressure of a pump or compressor, back pressure of a reverse-osmosis membrane to detect clogging, or pipeline pressure. When installed in a plant environment, it is often possible to install a single LoRaWAN gateway in a central location capable of covering the whole facility, thanks to its 1 km radius range. Naturally geographically large facilities, such as a tank farm or well head site, may need more than one gateway. Because this network only serves the condition-monitoring sensors, data can be routed to the appropriate users, such as maintenance or reliability teams.

Examples of automated condition monitoring

Returning to the earlier discussion about manual rounds, let’s look at how condition-monitoring sensors improve on traditional practices, including:

  • Inconsistent timing: Manual rounds are effective only when operators perform them consistently. If an emergency or other assignment causes a skipped visit, a problem has that much more time to escalate.
  • Inconsistent data retention: If data has to be collected and transferred to a host system manually, there is high potential for errors and missing data.
  • Inability to spot trends: With gaps in data, it is difficult to recognize trends and steadily escalating problems.

Automated data collection ensures consistency on all sides. There are no gaps in performance and no errors. If there are trends, they are easy to spot. Because all the data comes in through a single gateway, or at least a single network, all data can be directed to the right individuals for evaluation and appropriate action. Here are some brief examples of how companies have put this capability to work.