What is our primary use case?
Our main use case for IoT aaS involves using a Weather Guard AI for our poultry farmers, who utilize this platform for IoT that helps them to have poultry intelligence in terms of rainfall, temperature, and it offers notifications and insights on what they are supposed to do in order for their farming activities not to be affected by daily changing weather patterns, whether it is moisture from rainfall or cold temperature and all that; it has a bearing on especially poultry farming because we also have a solution that we developed for poultry farmers.
The idea to use IoT aaS for poultry farming comes from the fact that IoT is very important in terms of safeguarding the workflows of farmers, especially in safeguarding the dangers associated with weather. Monitoring itself, processing of data, security of that data, platform and infrastructure, when you are using IoT aaS, helps you to actually set up the infrastructure, the data pipeline, and what we can only focus on is enhancing your product so that you deliver more value to the farmers. They specifically focus on activities that improve their technology, and they do not have to worry about designing hard-coded infrastructure, the platform, or the data pipelines; everything is set up for you.
Now from the internship that I am doing, we are actually implementing most of our workflows for our smart crutch that leverages ESP32 devices, which are Bluetooth Low Energy and Wi-Fi enabled, so it collects the telemetric data about the patients, and the whole system, the backend of IoT aaS is on the Supabase. It has been invaluable in terms of how we get our telemetric data and monitor how our clients are recovering, finding ways to improve on the products they have actually acquired from us.
What is most valuable?
IoT aaS offers device management platform and cloud infrastructure, data pipelines, and security as the best features. These are the most important features because this is where most people face challenges in trying to configure the device and planning the best solution for the problems the users face; IoT aaS is a platform that actually helps companies, it helps farmers, it helps anyone, even those who are not technically gifted or savvy, to actually use these devices because the whole infrastructure is abstracted. Our focus now is to improve on things that matter to us to enhance our productivity, increase profitability, among others.
IoT aaS device management platform helps us to fit our requirements for our product on that platform. It actually has suggestions on what is required to achieve our objectives, and the system monitors the devices. It has already set up pipelines for data, built-in security because security is the most fundamental aspect of these IoT devices, and you can see how the organization of workflows is perfectly arranged so that whatever use case you try to incorporate or integrate into your business, it is scalable and designed with security in mind. Sometimes we are also grateful because some of our workflows are offline first, so using IoT aaS offline first, the whole thing, the platform for cloud kicks in whenever connectivity has been restored, and we do not worry about how to wire the connectivity, the security aspects, everything is just in place.
What needs improvement?
IoT aaS is supposed to have smarter devices, especially when remotely operated; in agricultural setups, network challenges arise. Enhancing offline-first capabilities is important, so that telemetric data can be processed on the edge before transmission to the backend for analysis. Edge-first and offline-first should run parallel to cater to areas with intermittent connectivity.
I assigned a rating of eight because there is still some work needed for weather elements protection of components, offline-first architecture, and ease of use in high thermal zones so that it can function in plastic furnaces and high energy zones without interruptions in transmitting telemetric data to the cloud.
I think there is still need for work on AI governance, especially as AI powers our homes and is incorporated into livelihoods with many IoT devices interconnecting; there is a lot of personally identifiable information involved that needs protection. Designers and developers must ensure compliance with data privacy laws in jurisdictions where they operate.
For how long have I used the solution?
I can say it is now about the third year using IoT aaS, and it has been an invaluable experience in actually implementing IoT aaS in our workflows.
What do I think about the scalability of the solution?
When we implemented IoT aaS in our poultry farm management system application, we experienced a significant spike in the number of users trying to use our application. We also checked our reviews where people found it very helpful, especially the use cases of our global application. People in the tropics, who suffer from erratic weather patterns affecting poultry, have a platform which forewarns them; it has intelligence embedded to give notifications, reducing their losses. We have seen a dramatic upsurge in users and monitored how they are using the weather app, which has a positive impact.
From December last year up to mid this year, we have experienced a jump of around 40% in our user base; the pace has accelerated. We did not have that percentage of upsurge before, and we also see from our reviews that people send us messages on how to navigate and use the system properly.
How are customer service and support?
We mainly rely on AI chatbots within the platform for help, which provides assistance quickly without having to wait for anyone.
Which solution did I use previously and why did I switch?
We did not previously use a different solution; we migrated from Supabase because some aspects we needed were not covered there. Moving to AWS has facilitated our workflows effectively.
Before implementing IoT aaS, we hard coded many workflows in our mobile applications; we initially used phone sensors but have migrated to using IoT aaS due to the benefits they bring.
What was our ROI?
We have actually seen about a 60% reduction in outsourcing costs for experts and consultants in our product lineup and service provision; that is a significant reduction in costs.
What's my experience with pricing, setup cost, and licensing?
In terms of pricing, I believe it is currently affordable, not pricey. These IoT devices, which form part of the ecosystem, need more power; while Bluetooth Low Energy and some Wi-Fi enabled modules consume less power, we need more battery power as well as integration with solar for real-time charging. We should incorporate 3D printed casings to protect devices from different weather elements and high thermal zones to prevent component damage.
In terms of pricing, setup cost, and licensing, we did not encounter significant costs compared to alternatives or traditional IoT implementations; we do not worry about hosting aspects or provisioning resources ourselves. Previously, systems required separate authentication providers for identity access management, leading to higher costs. However, with IoT aaS, it is a bundled service that caters for almost everything, managing the hardware on the cloud with proper dashboards for data analysis.
What other advice do I have?
Scaling up production was very easy for us; as mentioned, we experienced a number of people using our platform.
My advice is that IoT aaS is the future as most computing is now in the cloud; implementing IoT devices is invaluable for energy sustainability. Systems offer good connectivity and built-in data pipelines and security stacks, allowing for flexibility in scalability. Pricing is elastic, catering to fluctuating user demands without necessitating significant investments in infrastructure. I assigned an overall review rating of eight to this solution.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?