Can Open IoT Solve the Main IoT Challenges

Chris Murphy from InformationWeek has published a fascinating article about some of the challenges organizations face when trying to implement IoT solutions. The article focuses on Industrial IoT solutions and is based on interviews with GE, Union Pacific and others. I certainly recommend reading the article.

I thought it might be interesting to look at each of the challenges presented in the article to see how the Open IoT community might help solve the problems.
 
 
 
 

  1. The data isn’t good enough.
  2. Getting smarter about how to collect and use the data is still a work in progress. The last quote ‘linkage is one of the next big areas to look at’ is particularly relevant. This is why open standards like MQTT, CoAP and others will be so important for IoT. We need to break-down the existing proprietary protocols so it is easy to flow the data from a Nest thermostat or smart-meter into the demand generation of a power generation plant.

  3. Networks aren’t ubiquitous.
  4. “The future Internet of Things model often will combine on-machine processing for urgent needs and batch-data uploads for less timely analysis. Bill Ruh, VP of GE Software, describes this as “real-time, big data processing at the machine. We don’t have anything like that today.”

    A lot of the current web and enterprise development architecture assume the existence of a reliable network, in IoT that is not the case. Pushing application logic on-machine or to a gateway will become essential. Cisco has certainly observed this challenge and that is why they talk about ‘fog computing’. It is also why the Eclipse Krikkit project is so important.  IoT gateway solutions will also help with this challenge. Eclipse Kura and Mihini provide open source solutions for people wanting to build IoT gateways.

  5. Integration is tougher than analysis.
  6. Companies spend 90% of their IoT budgets on those kinds of integrations, leaving insufficient money to drive the operational changes that actually produce the returns, says Ton Steenman, Intel’s IoT business leader.

    Building IoT solutions is hard work. It requires the skills of hardware architects, embedded software developers, network engineers, enterprise software developers and data analytic experts. Each solution is often custom crafting of a specific solution. This is where the open IoT community can deliver a huge benefit. We need to collaborate on building a common set of building blocks that people use to build these solutions. We need to use software in help with the complexity of integration. Communities like Alljoyn and Eclipse IoT are building these foundations to help with integration.

  7. More sensor innovation needed.
  8. It would seem the open hardware community is well positioned to take up this challenge. We are seeing tremendous innovation in hardware for the maker and IoT community. My guess is that we will see more and more innovation in this community.

    It is interesting to see mention the concept of a software-defined sensor. I need to do some more research in this area but like software defined network or software defined radio, my guess is that open source software would be a great way to provide software-defined sensors.

  9. Status quo security doesn’t cut it.
  10. “The biggest fallacy is that traditional IT security solves operational technology problems,”

    Everyone sees security as an issue for IoT but I don’t see anyone stepping up to solve it. Someone needs to start working on this or maybe someone can point me to a community working on this, please.

I really like this list of challenges since it is based on companies trying to implement real IoT solutions. There is still a lot of work needed to create technology to solve these solutions but in confirms my belief that the vision we have for Eclipse IoT is focused on the correct customer requirements.

 

Related Whitepaper:

Software Architecture

This guide will introduce you to the world of Software Architecture!

This 162 page guide will cover topics within the field of software architecture including: software architecture as a solution balancing the concerns of different stakeholders, quality assurance, methods to describe and evaluate architectures, the influence of architecture on reuse, and the life cycle of a system and its architecture. This guide concludes with a comparison between the professions of software architect and software engineer.

Get it Now!  

Leave a Reply


1 × five =



Java Code Geeks and all content copyright © 2010-2014, Exelixis Media Ltd | Terms of Use | Privacy Policy
All trademarks and registered trademarks appearing on Java Code Geeks are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries.
Java Code Geeks is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.

Sign up for our Newsletter

20,709 insiders are already enjoying weekly updates and complimentary whitepapers! Join them now to gain exclusive access to the latest news in the Java world, as well as insights about Android, Scala, Groovy and other related technologies.

As an extra bonus, by joining you will get our brand new e-books, published by Java Code Geeks and their JCG partners for your reading pleasure! Enter your info and stay on top of things,

  • Fresh trends
  • Cases and examples
  • Research and insights
  • Two complimentary e-books