Worm on the sensor: What happens when IoT data is bad? – PCWorld


December 16, 2016 Facebook Twitter LinkedIn Google+ Uncategorized


Enterprises trying to use the internet of things already face a deluge of data and a dizzying array of ways to analyze it. But what happens if the information is wrong?

Bad data is common in IoT, and though it’s hard to get an estimate of how much information streaming in from connected devices can’t be used, a lot of people are thinking about the problem.

About 40 percent of all data from the edges of IoT networks is “spurious,” says Harel Kodesh, vice president of GE’s Predix software business and CTO of GE Digital. Much of that data isn’t wrong, just useless: duplicate information that employees accidently uploaded twice, or repetitive messages that idle machines send automatically. 

In addition, building a new IoT platform on top of old industrial reporting systems can cause problems because the legacy tools format data in their own way, Kodesh said. “You’re not taking the real, elemental data, you’re taking some translation of that.”

But sometimes devices just generate stuff that’s false or misleading.

Measuring the wrong thing

For example, if a worm crawls over a temperature and humidity sensor in a field, the farmer will get a reading on how warm and moist the worm is, which doesn’t help to run a farm. If a sensor gets covered with dirt or factory grime, or if it’s damaged by vandals, that can tweak the data it produces, too.

The harsher the surrounding conditions and the more isolated the device, the worse the bad-data problem is likely to be. In addition to agriculture, industries like oil and gas and energy distribution face this. But it’s not just far-flung sensors that have problems. Even in a hospital, a blood oxygen sensor clamped on a patient’s finger can start giving bad data if it gets bumped into the wrong position.

On top of that, some IoT devices malfunction on their own and start spewing out bad data, or stop reporting at all. In many other cases, human error is the culprit: The wrong settings mess up what the device generates.

Comments