How to provision a preconfigured IoT solution?
Azure IoT suite does have some preconfigured IoT solutions that you can use to get started.
You can create these preconfigured solutions by navigating to http://azureiotsuite.com
When created, it will setup all necessary resources on your azure subscription and then you can take preconfigured solution you choose and customize it based on your needs. These can be extremely helpful on building app solutions that are similar to the preconfigured solutions without having to build it all yourself from scratch. Especially with the best practices that be implemented in these preconfigured solutions without you having to learn those necessary before getting started.
These preconfigured solutions that are also made available to us open source and they are all hosted on Github.
azureiotsuite.com web site is basically a landing page for you to discover Azure IoT. And what we call the provisioned solutions are things that already deployed on my account but what I can do is to create a new solution.
Let me actually drive you through the process. On the web page what I do is just ask for a new solution to be created.
There are several options here for these new solutions:
The first one is remote monitoring. There is also a new version of remote monitoring which is in previous right now and this is the one I am going to go through. I can eventually deploy a connected factory solution. So these are some of the examples of preconfigured solutions that will help me get started and discover what azure IoT has to offer.
On the next page, I will be able to select a few things about what kind of solution.
Basic or standard, allowing me to whether having something that actually is a single instance of that service which is better for evaluation and so forth or standard which is the production version of that solution.
My backend is developed with .NET or Java so I can pick one of these two options.
Next I would enter the name of the solution. Then I can pick one of azure subscriptions and I need to have a subscription to be able to work with that and then I can pick the region I want to deploy my solution on to.
From Here I can just go ahead and create the solution.
It is going to take something like 5 minutes to deploy a full blown solution for IoT with many services which I will show in the azure portal later.
So this is the solution after successful deployment. I have a full blown dashboard that monitors devices across the world and these devices basically are sending telemetry data to azure and that data is analyzed by various type of services and I gathered all that data and processed that data and I display that data in the dashboard.
The dashboard shows me the location of the devices because device is sending metadata when connecting. It shows various alerts that have been set up and it allows me to dive into KPIs that I can track to make sure that I have all my devices in good health and eventually I've been dealing with these alerts in a timely manner.
On the devices page, I can see all these devices.
Here we have some numbers but because they can be way more I can also filter them. I can create filters and then pick only the chillers and filter the view here.
There is a maintenance tab as well that is where basically I have my maintenance operator do his maintenance. I can see that we have an alert here so I can visualize that alert by clicking on that particular row.
I can then dive into the history for that alert. I can also try understanding what that rule that has been triggering that alert is. I realized that the trigger basically is been that pressure went over certain value.
In terms of the telemetry of data actually I can also dive into each of these devices by clicking on devices menu and clicking on the device. Back to that device view I can actually visualize real time data temperature, humidity and pressure and I can also see the various methods are available on how to control and configure these devices.
And at the end I put some links and resources:
Source of remote monitoring on github dotnet source:
Number of Views:1133