14) Azure IoT & Microsoft Power Apps, Dynamics 365, Flow, Cosmos DB – Intelligent Service Demo



good afternoon everybody on today's business applications Lunch and Learn we're gonna be diving into the Internet of Things and we're gonna have my colleague Jack bender showcase how you can take the Internet of Things and marry it with all of Microsoft's business applications ecosystems including Azure Dynamics 365 cosmos DB Microsoft flow and the power platform through a power app that can be replicated and stay tuned to the end of the episode where we show you how to replicate that in Jack's github repositories if you're new to the Microsoft business applications YouTube series we release new content every Monday so hit the subscribe button below and be sure to LIKE so that we can continue to provide these videos for you on today's team's call I've got my colleague Jack bender Jack how are you today I'm doing fantastic how you doing Nick I'm doing well we appreciate your time we know you're busy and traveling and we've been trying to schedule this for a while so thank you for making the time and we look forward to your session today so thank you thanks for having me Nick today what we're gonna jump into is really talking about the way that you can use a variety of platforms within Microsoft and marry them into a power app so the power apps can read off those platforms and to the end-user they don't realize that they're looking at data coming from separate systems they're just going into one single pane of glass to see the information that they need so with connected devices once that information starts to come into the cloud there is more than just dynamics to that and in fact there's three different areas that we talk about so there's what's considered cold path warm path and hot path and hot path is what you typically see for a dynamic scenario so hot path is I have a device that's failing and I need to roll a technician to show up on site to correct that device so in the past we've worked with one of our customers is a battery and UPS manufacturer so let's say that device is starting to send an alarm it's beeping or so forth that's a hot path scenario we know we need to take care of that immediately up top here we have what is considered our cold path scenario in a cold past scenario itself allows you to gather all the raw telemetry coming off that device so you could have 40 or 50 data points and today you only care about ten but those other thirty could be very important to you two years down the road when you come out with product v2 or v3 also being able to take that information and put it into your data Lake so now that you can hydrate your lake with the data over time so now you can start to do predictive maintenance so instead of waiting for the alarm to beep on that UPS battery backup we know that the temperature of the jars or cells of the battery are starting to deviate and once we've seen a certain deviation point we can now predict that this thing will fail maybe not in the next hour but probably in the next two to three weeks so we want to send out a technician next week to take a look at that what's that reject and all of this is really the aspect of warm paths scenarios so today we're gonna focus more on power apps but also another great idea of a warm path scenario is power bi and so here's an example of a power bi dashboard that's showing the real-time telemetry that is coming off of an MX chip that I have so I hopefully you can see this here here is the MX chip on the screen is that pretty visible Nick yeah it looks good and an MX chip is really a Internet of Things device that's exude a telemetry but this could be on a elevator or it could be on a myriad of devices and it's kind of like a cell phone accelerometer with a tremendous amount of sensors exactly exactly so best way I think about an MX chip is it's a Raspberry Pi with embedded sensors it's actually an Arduino based device but it gives you the ability to showcase something very easily without having a breadboard and a cobbler what I think looks more like a this looks less like a sixth-grade science fair project so within the power bi report here or the dashboard I can see the various data that's coming in and this is my warm path scenario I'm not necess taking action upon this but I want to observe data trends and any anomalies that are going on with that so this is a great example of showcasing that data but here we're looking at it via a desktop and that's not always ideal for people within the field so really what we want to be able to do is give them a power app to see this data so now we're actually looking at my mobile device here with a powerup and this power app is showing me data live telemetry data coming off that chip and what's important about this is this data is actually being written to a no sequel store of cosmos TV and I'll get into that in a minute but so all this telemetry data that I see here with temperature humidity accelerometer I can see this one highlighted in red down here this here is telling me I've got an anomaly I can drill into that data and now I could see the various data within a year so this gives me my detail within and again here's my list view now but as I mentioned all of this telemetry data is coming from cosmos dB and we updated every 15 seconds so I can see data is coming in but my listing of actual devices comes from dynamics so this is my IOT devices list so let's actually dig in a little bit here to see how I created this power app so here's a good representation of our warm path data so as this data comes into the Microsoft cloud it goes through the IOT hub and it streams out to cosmos dB so for those of you that are very used to sequel databases you're used to a uniform structure you use the meta data tables cosmos allows you to store no sequel data and that's very important with the Internet of Things because you could have different devices sending different values different fields and as you light up a brand new device you see this more in a connected manufacturing as opposed to a connected product scenario but you get ten new fields and you don't want that this pipeline to necessarily here you still want to capture those new fields so let's take a look at what that looks like Here I am and as your storage explores so these are fields that are coming into cosmos as JSON documents and I could see that I've got my various values within here that are being pulled in from the device telemetry right here as I click through and I could have six new values show up if I lit up another device that gives me additional readings besides accelerometer you know in Fahrenheit humidity latin lon and this is key because as you are starting to bring in IOT data you really need to understand that a lot of times this is this could go into a no sequel store and we want power apps to be able to read from that so back on the diagram here is we start to create our power app a power app could expect the specific fields and that's easy we can we can link dynamics 365 directly to it but for a no sequel dynamic type of database I have to put flow in the middle of it because I got to tell power apps I'm always getting these eight fields and I don't care about the other 30 field bills coming in so if this here was a sequel database I wouldn't need flow here but now I have that ability to use flow with power apps so that I have that screen I was looking at before I can see the data that I want yeah Jack that's critical because the Microsoft Power Platform and the ability to take those analytics with power bi the ability to act in power apps and then the ability to automate using Microsoft flow that's where Microsoft is helping all of Microsoft's customers take advantage of those IOT devices and the data and a variety of data stores and to be able to drive business outcomes at the heart of what the power platform is that's where we can start to help business analysts and the customers that have invested in technologies outside of Microsoft but also take advantage of the easy and elegant experience within the Microsoft power platform it's very powerful yeah agreed and that's what I like about this is that I'm not a developer by trade but I'm now able to use through configuration through power apps and flow to build out what I need to I always make the joke you know I'm not a developer but I stayed at a Holiday Inn Express last night so voila use my power app here's my flow and what I'm able to do with this so within here is I look at my power app designer I can see my data sources I'm pulling to different flow pieces and then also I'm pulling in my IOT devices from dynamics so again when I look at my power app I can see that here is my data that's coming from dynamics when I select a device and then my telemetry data I had two different flows I had one that was my ListView and then another one that is my detail view that I can see within here yeah Jack you used the power apps designer to create those elegant experiences so you're taking the data from cosmos DB and dynamics 365 or another data source of which the power platform has over 200 connectors into various data repositories and you're bringing that into the power apps designer to create simple and purpose-built experiences in that power app capability for fields technicians or maintenance technicians to be able to consume in that power platform on their mobile device and that's what we're seeing here yeah exactly so I could get an alert from a customer that they're seeing some funky behavior with one of their devices but it's not necessarily a situation that I need to create a work order I need to roll a technician out to the site and this is what the power app allows me to do is pull it up on my phone to see that information so I can pull up that raw telemetry and now with a power app the only detail here is for this I have to use flow to standardize the data and it's actually pretty simple to do the hardest thing here is just writing this select statement and the good thing about this is I put all this into a github repository so that you have access to all this information so as I look at here if I go into files when I was showing you example of the select statements here it is so here's a great example of what a cosmos DB query could look like coming off of an MX chip and the reason for this github repository is to make it easy for everybody to understand okay now I just seen what Jack shows me how do I build this and with here I actually walked through step by step with screenshots to show everyone how easy it is or that they can start to build this out so you can see all the various components within here so at the end of the day even pulling the data from dynamics and having that drop down and being able to see that information come in yeah Jack it's great right we're combining the capability is a Microsoft flow the power platform dynamics as well as Azure and Cosmo Stevie and marrying that with the ability to harness telemetry coming off of an Internet of Things device and this is really the business applications ecosystem coming in together and all of them Microsoft's assets that have been engineered to help create that digital transformation for customers and it's really taking advantage of our Asscher infrastructure our business applications infrastructure in Dynamics 365 and the power platform and then the analytics capabilities and the automation capabilities of Microsoft flow and power bi it's really an excellent showcase of how our customers are empowered to take advantage of Microsoft's cloud and to be able to drive business outcomes to deliver proactive service leveraging data rather than being reactive and helped create those experiences for their customers it's excellent yeah and again what I love about this is Dynamics data does not always have you shouldn't always have to be in Dynamics 365 to see that data it should be surfaced and married with other systems and be at your fingertips whether you're on a laptop a tablet or a mobile device hey thanks Jack this has been an excellent showcase of taking all of the assets that Microsoft gives to our customers with regards to creating transformational experiences all the way from an Internet of Things all the way to taking that telemetry ingesting it into asher and leveraging that capability through the dynamics database the power platform database and looking at how you can analyze that with power bi leveraging Microsoft well such an excellent showcase will link to where you can replicate and find Jack's github repository in the description but if this is helpful feel free to give it a thumbs up and and on behalf of Jack and myself we appreciate your time thanks jack we really appreciate it in my pleasure thank you

One Comment

  1. Mehul Pandya said:

    This is excellent demo showing end-to-end capability of different cloud services, business components, analytics. Showing how to leverage and take advantage of different components of MS to build real business useful application with very less time (i.e. less time to market). – Great work! – appreciated.

    June 29, 2019
    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *