Should you build your own IoT solution? The question is not as strange as it sounds. Anyone involved with IoT solutions for the last 10-15 years knows that ‘do it yourself’ is the first thought of most businesses. Companies that have their own R&D labs and IT departments typically task them with ‘implementing’ IoT in the business. After all, how different can it be? Code is code. The cloud is the cloud. It’s just software.

Before we drill down to what it really is I dug up some interesting facts from the IoT implementation battlefield during the last 10 years. I scoured the world wide web and came up with the following.

76% of all internal IoT projects are either over budget, behind schedule or outright failures. 76% gets you fired. Reasons for failure were widely debated between each author but they all had two things in common – IoT has too many moving parts and there is not enough knowledge in most companies.

So with that research done I put together a quick list of what you need to consider for your IoT project.

  • IoT Devices (things)
    • Procurement (don’t forget the new supplier process…)
    • Development
  • Edge Processing
  • Data Models
  • Connectivity
    • Cellular
    • LAN
  • IoT Data Processing Platform
  • Web Applications
  • Mobile Applications
  • Administration
  • Provisioning of New Devices
  • Analytics
  • Machine Learning
  • Security Architecture

And that list will only grow as complexity and changes are incorporated. Ask yourself if you have the knowledge and expertise to develop your own IoT solution in your company?

If you need to use an IoT Highway already built, Triotos provides deployable solutions based on market leading AWS IoT technologies that come with a set of applications that we customize for your needs.

About the Author

Mats Samuelsson

Mats Samuelsson is the CTO & VP Marketing and Business Development for Triotos. In this role, he is responsible for the new business, development, integration, and deployment of Triotos technology initiatives.