If your company has a great idea for a product involving IoT, this will help you understand the issues involved in getting your ideas off the ground and taking a product to market.
Creating an IoT product may be a new thing for your company. You might be a manufacturer who builds physical products and who is yet to take a software and IoT-based product to market.
You probably have some good ideas on how you can add intelligent hardware and software to your existing offering, and a track record of delivering innovative products in your industry. However, IoT product development may require you to employ new skills to get the hardware and software components designed and assembled.
In the early phases of your product development, you’ll probably want to test the market to make sure your concept is well received by potential customers. It will be more cost effective and faster to do this without hiring a whole new department. Instead, you’ll be looking for outside expertise to get you moving.
IoT projects require a certain skill base to get started. Some of these you’ll already have, and other’s you’ll need to hire in.
Note that you might not need all of these at once. Many companies start by prototyping and then work up from there.
Firstly, here are the skills you might already have in-house:
And some skills you’re most likely to need to outsource initially:
Before embarking on you IoT project, it is important to make sure you include the right things in your plan and budget. Every IoT solution is different, but it is likely your project plan will need to include the following elements.
This might be a sensor that detects impacts, or changes in temperature or whatever else you want to detect. Technically it doesn’t have to be a sensor, it might be a button or actuator of some kind. It might be wearable or mounted in a fixed position. Most are battery powered. And, they need to somehow connect to the internet to send their messages. Usually, this happens using a low powered radio such as Zig-Bee to send data to the gateway (see below).
A gateway device typically sits between your swarm of sensors and the internet. For example, you might have 1,000 sensors in a retail department store that collect customer footfall data, and these need to send that data to the cloud so it can be used for something useful. The gateway facilitates that communication. It tends to have GSM, WiFi or wired ethernet connectivity.
You’ll have a cloud solution that receives data from your gateway. This will be secure and capable of handling large amounts of data, especially if you plan to deploy a lot of sensors. You may also be interested in using machine learning to add some intelligence to your product offering.
You have a choice of building your own or selecting an out-of-the-box solution. If you build your own, you will have more control over the visual appearance and the features included in your solution. If you select a ready-made solution, you will get to market faster and perhaps with less cost. That said, many teams can build IoT solutions very quickly using modern tools such as Elixir and the Phoenix framework.
Most IoT solutions add value by turning data collected into useful reports and insights. Often this data is displayed on a control panel. On top of that, you’ll want an online portal where your customers can set up access permissions, configure any settings and export backups of data.
Once you’ve installed hundreds or thousands of your smart hardware devices on premise, you’ll need a way to manage them. For example, you might need to roll out new software to fix a bug. Or you might need to troubleshoot a device when a customer calls you with a problem. This aspect of IoT is called device management. It’s a relatively immature field and there are lots of approaches you can take.
For many IoT products, customers will need to interact with the solution whilst away from their laptop or desktop computer. So, you’ll want to have a mobile offering, be it a native app or progressive mobile site. The mobile app could be designed to receive alerts, or it could be there to assist with setting up the devices. In some cases, you might not have a cloud portal and instead, do everything through the mobile app.
If you want to use your IoT hardware in a commercial or consumer setting in the UK, all your hardware components will need to be certified. For example, say you have a Rasberry Pi and attach a GSM modem to it, you need to make sure both of these components are certified (the Pi is).
Before going to market you’ll need to put your combined components into certification as a whole. This is why it’s so important to ensure all components are certified. If one of them is not certified, then you’re combined solution won’t make it through certification.
When starting a new project, it’s important to pay great attention to this otherwise your project schedule will be at risk as you get bogged down with finding new components or waiting for your component manufacturers to sort things out.
Pulling all these skills and components together is going to be necessary at some point, but there are also options for the short term too.
We’re experts at creating software solutions that underpin IoT projects. Our strengths are in mobile and cloud development, and prototyping IoT solutions. We help companies explore their ideas to take IoT products to market.