It's no surprise that Cisco -- late to the game on this one -- is trying to gain as much as it can by selling its existing 'hardened' devices for IoT apps.
But there is no innovation here (yet). IP can already transport BACnet, MODbus, and many other SCADA, BMS, and other protocols.
The real innovation work that needs to be done is systems, not network integration. Most if not all of the SCADA, BMS, and other PLC gear already have IP functionality or at least gateways. What's really missing is systems/application level integration, not transport (over IP).
It is interesting to learn that CISCO is working towards bringing SCADA on the internet. GE has coined the term "Industrial Internet" and plans to work with AT&T, CISCO, Intel for building and expanding the industrial Internet, or machine-to-machine (M2M), does this relate to the same?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.