Bringing IoT to old-school industries without disruption is challenging

Most industries that are moving to modern IoT are faced with integrating the new technology with their older gear, making for a complex transition, but the technical side of the process is getting simpler by the day.

Jon Gold

In the enterprise half of the IoT world, heavy industries like energy, manufacturing, and automotive are the biggest success stories for the new technology, but the prospect of integrating their existing computerized-orchestration and management technology with modern industrial IOT gear can be daunting.

The vast majority of IIoT deployments are attempts to layer modern sensors, edge gateways, and communications modules over the top of existing frameworks like SCADA, which means updating legacy sensors and other hardware where possible.

The good news is that it’s not as big a deal as might be expected from a technical standpoint. There are solutions out there for retrofitting older gear while it’s still operating. New sensor kits or communications modules can sometimes be added to industrial machinery via old RS-232 serial ports, but often that’s not enough. Ethernet connectivity at a minimum is usually what’s required to start metering and then gathering data in meaningful volumes. Hence the need for broader upgrade programs.

Gas pipeline IIoT transition relies on edge networking
Bill Johnson is a vice president and chief transformation officer with DCP Midstream, an energy company mostly devoted to operating natural gas pipelines. It’s got 57,000 miles of pipeline and 61 plants spread across the southern U.S. He said that DCP, like many other companies, is facing the challenge of installing new IIoT equipment without having to take pumps valves and other machinery off-line while they do it. That is such a major concern that the ability to do so has become a selling point for him.

Whether the IIoT add-ons are flow sensors, pressure monitors or digital thermometers, Johnson said that anything that can simply be strapped, bolted or glued onto the outside of the machinery it’s supposed to be monitoring is more attractive than something that has to be mounted within the equipment itself.

For DCP, the value of IIoT is in getting data from its systems in the field into a centralized repository for analysis. Instrumenting those systems and getting them all to communicate with the analysis layer is enough of a challenge, but DCP also has to cope with the issue of many of its facilities being located in remote areas.

“Most of the world believes there’s pervasive 4G/LTE available everywhere, and that’s absolutely not true where we operate,” noted Johnson. “It’s very hard to convince AT&T or Verizon to give you signal at some of these locations, because they don’t have consumer users [out there.]”

So other methods have to be used. One is the use of old-school, point-to-point radio links between sites, as well as satellite communications, but these are expensive and can be unreliable. That prompted a move toward edge computing – installing local devices to receive and process information from sensors, instead of relying on long-range data links back to a data center, or, in DCP’s case, Microsoft’s Azure cloud, for real-time analytics.

Honda's IIoT adoption calls for blending disparate technologies
Those analytics, in fact, are where the real value of IIoT lies for DCP and other companies trying to upgrade their technology. Older industrial automation tech tended not to be designed to share information with a wide range of other machines, particularly those made by different companies.

It’s a cross-industry problem, said Pierce Owen a principal analyst at ABI Research. He gave the example of Honda’s light truck plant in Alabama, which, until modernization, was operating a mix of OMRON, Rockwell, and Mitsubishi industrial-monitoring and orchestration equipment, none of which talked to each other, and all of which used proprietary protocols. Settings couldn’t be changed live, and workers had to go to each individual machine and shut it down to make changes. To manage this, Honda developed a complex, in-house system to synthesize data from these various sources, which required extensive coding knowledge to use properly.

“The reality is that lots of companies are using software they built in-house, and not only is it difficult to reprogram things, but it requires custom coding to even collect the data in a way that makes sense,” Owen said.

What changed things for the Honda plant, he argued, was the adoption of Telit’s DeviceWise system that can be used by line-of-business personnel who might not have backgrounds in programming, letting the company take data from a disparate range of industrial machines and generally simplify the data exchange.

Usually, companies updating old industrial control systems to modern IIoT work closely with an industrial automation vendor like Telit or sometimes a smart manufacturing platform provider like PTC or Siemens to manage remote devices and to gather, process and analyze IIoT data. How complex that is depends on where the company’s starting point is because old infrastructure requires a lot more retrofitting than newer hardware.

IIoT adoption needs clear lines of responsibility
An IoT adoption project of any stripe can be organizationally complicated. Does the line-of-business staff, with its familiarity with the actual equipment involved, take the lead or is the task left to the more technically fluent IT department?

“There just haven’t been enough projects to say, ‘Oh yeah, in this industry, this group should take the lead.’ There’s definitely still a wide variation,” said Mark Hung, an analyst at Gartner.

The example he provided was Microsoft, which undertook a smart buildings initiative a couple years ago at its facilities. Given that Microsoft’s the company in question, it’d be easy to imagine that the IT folks would have been the ones in charge of implementing the new technology, yet the Redmond giant assigned the task to their facilities management people.  Conversely, Toyota set up a separate business unit to implement its connected car programs, instead of letting the operational side handle it.

There’s no clear right answer, according to Gartner analyst Mark Hung, it’s a matter of what makes the most sense for any given organization – whether familiarity with the company’s processes and operational equipment outweighs the need for specialized IT-based skill sets.

Bringing IoT to old-school industries without disruption is challenging

Most industries that are moving to modern IoT are faced with integrating the new technology with their older gear, making for a complex transition, but the technical side of the process is getting simpler by the day.

Jon Gold Mar 12th 2019

In the enterprise half of the IoT world, heavy industries like energy, manufacturing, and automotive are the biggest success stories for the new technology, but the prospect of integrating their existing computerized-orchestration and management technology with modern industrial IOT gear can be daunting.

The vast majority of IIoT deployments are attempts to layer modern sensors, edge gateways, and communications modules over the top of existing frameworks like SCADA, which means updating legacy sensors and other hardware where possible.

The good news is that it’s not as big a deal as might be expected from a technical standpoint. There are solutions out there for retrofitting older gear while it’s still operating. New sensor kits or communications modules can sometimes be added to industrial machinery via old RS-232 serial ports, but often that’s not enough. Ethernet connectivity at a minimum is usually what’s required to start metering and then gathering data in meaningful volumes. Hence the need for broader upgrade programs.

Gas pipeline IIoT transition relies on edge networking
Bill Johnson is a vice president and chief transformation officer with DCP Midstream, an energy company mostly devoted to operating natural gas pipelines. It’s got 57,000 miles of pipeline and 61 plants spread across the southern U.S. He said that DCP, like many other companies, is facing the challenge of installing new IIoT equipment without having to take pumps valves and other machinery off-line while they do it. That is such a major concern that the ability to do so has become a selling point for him.

Whether the IIoT add-ons are flow sensors, pressure monitors or digital thermometers, Johnson said that anything that can simply be strapped, bolted or glued onto the outside of the machinery it’s supposed to be monitoring is more attractive than something that has to be mounted within the equipment itself.

For DCP, the value of IIoT is in getting data from its systems in the field into a centralized repository for analysis. Instrumenting those systems and getting them all to communicate with the analysis layer is enough of a challenge, but DCP also has to cope with the issue of many of its facilities being located in remote areas.

“Most of the world believes there’s pervasive 4G/LTE available everywhere, and that’s absolutely not true where we operate,” noted Johnson. “It’s very hard to convince AT&T or Verizon to give you signal at some of these locations, because they don’t have consumer users [out there.]”

So other methods have to be used. One is the use of old-school, point-to-point radio links between sites, as well as satellite communications, but these are expensive and can be unreliable. That prompted a move toward edge computing – installing local devices to receive and process information from sensors, instead of relying on long-range data links back to a data center, or, in DCP’s case, Microsoft’s Azure cloud, for real-time analytics.

Honda's IIoT adoption calls for blending disparate technologies
Those analytics, in fact, are where the real value of IIoT lies for DCP and other companies trying to upgrade their technology. Older industrial automation tech tended not to be designed to share information with a wide range of other machines, particularly those made by different companies.

It’s a cross-industry problem, said Pierce Owen a principal analyst at ABI Research. He gave the example of Honda’s light truck plant in Alabama, which, until modernization, was operating a mix of OMRON, Rockwell, and Mitsubishi industrial-monitoring and orchestration equipment, none of which talked to each other, and all of which used proprietary protocols. Settings couldn’t be changed live, and workers had to go to each individual machine and shut it down to make changes. To manage this, Honda developed a complex, in-house system to synthesize data from these various sources, which required extensive coding knowledge to use properly.

“The reality is that lots of companies are using software they built in-house, and not only is it difficult to reprogram things, but it requires custom coding to even collect the data in a way that makes sense,” Owen said.

What changed things for the Honda plant, he argued, was the adoption of Telit’s DeviceWise system that can be used by line-of-business personnel who might not have backgrounds in programming, letting the company take data from a disparate range of industrial machines and generally simplify the data exchange.

Usually, companies updating old industrial control systems to modern IIoT work closely with an industrial automation vendor like Telit or sometimes a smart manufacturing platform provider like PTC or Siemens to manage remote devices and to gather, process and analyze IIoT data. How complex that is depends on where the company’s starting point is because old infrastructure requires a lot more retrofitting than newer hardware.

IIoT adoption needs clear lines of responsibility
An IoT adoption project of any stripe can be organizationally complicated. Does the line-of-business staff, with its familiarity with the actual equipment involved, take the lead or is the task left to the more technically fluent IT department?

“There just haven’t been enough projects to say, ‘Oh yeah, in this industry, this group should take the lead.’ There’s definitely still a wide variation,” said Mark Hung, an analyst at Gartner.

The example he provided was Microsoft, which undertook a smart buildings initiative a couple years ago at its facilities. Given that Microsoft’s the company in question, it’d be easy to imagine that the IT folks would have been the ones in charge of implementing the new technology, yet the Redmond giant assigned the task to their facilities management people.  Conversely, Toyota set up a separate business unit to implement its connected car programs, instead of letting the operational side handle it.

There’s no clear right answer, according to Gartner analyst Mark Hung, it’s a matter of what makes the most sense for any given organization – whether familiarity with the company’s processes and operational equipment outweighs the need for specialized IT-based skill sets.