Hi Mark,
What you will find, many companies are focusing on just making IoT/IoE devices function. Data collection is immature and a low priority objective. There are no direct tools, data is often gathered as a man-in-the-middle.
Consider giving an IP address to a simple coffee maker. It really isn't an IoT/IoE device yet, but you can remotely start brewing the coffee. After it's prepared to make the coffee.
Without going into the kitchen, there are dozens of methods that could be used to start the coffee maker on the local network. API, port, CLI, VPN, tunnel, etc... Depends on the complexity and access you have to the coffee maker.
Remotely connecting to your home network, you could also find a way to start the coffee brewing. But it's still not an IoT/IoE device.
When the device contacts a central hub, somewhere on the internet, now it's an IoT/IoE device. And it doesn't do anything until you install an app of visit the central hub's website. Which provides a button to start brewing the coffee in your home coffee maker.
In most cases, the app and website would make a call that cascades an instruction to your coffee maker. When viewing all the calls, to every other coffee maker, this would be the big data.
The manufacturer could also notify the hub when you manually start the coffee making process. Providing more data, showing preference over the app, website, or directly using the button.
While the coffee maker may even use NTP to keep the clock accurate. In many cases, IoT/IoE does not change the basic functionality of a device.
------------------------------
Brian LaVallee
INVITE Communications Co. Ltd
------------------------------
Original Message:
Sent: 09-11-2017 16:26
From: Mark Desar
Subject: Collecting data in IoT networks
I am interested to learn what companies with IoE and IoT use to monitor the IoT network and make sense of the (big) data that is collected in the IoT networks?
------------------------------
Mark Desar
ESRI
------------------------------