ASI Emerging Technologies Webinar Series – Breeze Based IoT



with that I'd like to introduce Andrew Pro Comp Andrew is a director of emerging technologies here at ASI and has really been involved in the world of communication since the early 1980s andrew has a number of actually five to be exact US patents around the development in sip technologies more recently Andrews used his knowledge and expertise and has been developing software that integrates into the Internet of Things artificial intelligence natural language processing ITSM vias ServiceNow and as I mentioned we're going to talk about today Abhaya breeze so you know with that I'd like to hand it over to Andrew Andrew go ahead and take it away Thank You Marc and thanks everyone for joining us today I don't know where you are but here in Minnesota it's a beautiful sunny day it's supposed to almost hit 40 and for us that is a heat wave a tropical heat wave so I hope to get out and enjoy it later on this afternoon but until then I really want to talk about IOT so as Mark explained I have a long background I that's a polite way of saying that I'm old in communications technologies my background originally started as a software developer so I worked developing a lot of different products for a lot of different verticals and horizontal in DES strees have a big background in contact center software development and also in sip but none of this has to do with sip today but actually some of it has to do with some context and her stuff we'll talk about that as the presentation goes on so let's just jump right into it and to jump right into IOT and I start with a just a couple of slides that I think are interesting I just sort of poked around the internet and looked at really where the industry is going in including what's where it's going is it's it's it's just going bonkers in terms of IOT as consumers incredibly so more and more of our devices are becoming IOT of Isis we're controlling our houses we're controlling our lights we're controlling our garage doors I have a co-worker who has a IOT device on her dog Elaine you know what I'm talking about her dog runs around her farm and she knows exactly where her dog is and where her dog has been so as consumers we've adopted this technology wholeheartedly and the same thing is happening in industry as well so more and more industries are adopting the technology sensors are just appearing everywhere in the business in the business cycle and then the dollars spent obviously are going astronomical as well and so we see in the consumer world Gartner is predicting something like a tripling of the money from 2016 to 2020 and we're seeing similar trends in in industry as well so this is not a technology that's going away it's a technology that will become pervasive and things that will be part of every one of our lives if it isn't already and it's certainly a part of my life and I would be surprised if if it hasn't touched everybody here on the call today so IOT crystal ball now let's sort of look at where things are going and what's happening so sort of mimicking what I just said before with the slides by 2020 more than half of major new business processes and systems will incorporate some elements of the Internet of Things and this comes from Gartner so by 2020 really I mean everybody that you're dealing with is looking at this and half of the major business processes and systems will use it similar sort of thing discrete manufacturing transportation and logistics and utilities will lead the industries and IOT spending improving customer experience I love this improving the customer experience 70% and then safety 56% are the two areas that enterprises are using the data generated from IOT solutions until I certainly love the the customer experience because I want better customer experiences for myself and a second 70% that that is a huge number of how it enterprises are using the data generating by all these IOT devices and solutions and and all these things these three slides are all happy joyful sites but then we get to this one from Gartner through 2018 75% of IOP IOT projects will take up to twice as long as planned twice as long so clearly people want this technology clearly people are investing this in this technology but unfortunately it's proving to be much more difficult than they realize and and why is that we're really because IOT isn't it's actually not that easy and in some at the etham at the scalable mass solutions level a Gartner again skills and resources to build deploy and run IOT solutions are often scarce training is limited so you have this grand plan for rolling out this huge IOT solution but you don't have people that know how to do it it's so again it's we don't want to put the horse before the cart but we need to think these things through intelligently and this is where all of this presentation comes in is how do we make it easier but before we even get to the working on the solutions we need to look at the the protocols and the devices and this is the this is the key keep stuff that I love I'm a protocol person I love bits and bytes I love to look at you know Wireshark traces of messages and and they're to me they're like mystery novels or puzzles to solve there's not a lot of standardization in the IOT world there are lots of different protocols that are used to move data from one place to the other their different physical layers there a different session layer protocols it's really extremely complicated when you get down to well I have this particular sensor and it produces this kind of data and I want to take this data and I want to get it into my let's say healthcare solution and now I have this sensor that does something very different and I want to get that into my healthcare solution and I have now another sensor or another device so the complexities are are such that it's really difficult to manage if you were to go and say I'm gonna start from scratch and I want to build my own solution and I want to make it open enough so that I can have anybody's devices connect up into my system well again look at all the different things that you need to address are you going to do this on Laura or ule I'm going to talk about some of those later in the presentations or Wi-Fi or Bluetooth or Bluetooth Low Energy or ZigBee or it just becomes very daunting very challenging so what's happening in the industry though are people are saying we need to tame this we need to say if I have all these sensors on the edge and I have all these and all this information that these sensors are producing I want to normalize it information meaning what I want to do is I want to have the information come into some process that allows me to now treat every sensor on the far end is is exactly the same so if I get a temperature reading from sensor a I don't have to worry about that sensor B's temperature reading in a different format our temperature first sensor C in a different format so all the data gets normalized so that I see everything in the same way so we what we do is we have the idea of sensors connecting the gateways now the gateways can support all the different protocols that these sensors might do are that ule or they you know ble bluetooth little energy or they Laura how do they connect up well you as the user as the solution provider you don't care because those go into a gateway we normalize all the information and now we send this up into a data platform and now we can start to build applications on the data platform and as a kind of a geeky guy I like to break things down even further into sort of these boxes so again the edge we have sensors and edge devices and their multi protocols so they all speak their own different language now we have gateways that collect this information now they need to be multi operating system multi vendor different gateways are going to have different requirements because of the sensors how many gateways or how many sensors will connect to a single Gateway what kinds of sensors what's the distance between the gate ways in the censors way you work all that out in your design in your design portion but again we're doing now with the solution so what we want to get to solution so we work that out and then we bring this all into a data platform and the data platform can run in lots of different things it could be a private cloud it could be a public cloud we can use Amazon Web Services we can use IBM we can you know do whatever we want to do in the data platform but now when we start to look at solutions we want to then have all this data that's been with the different protocols and the end of different kinds of data we normalize that we bring the data platform and now we want to expose that to the outside world as the solution developers to create these incredible you know healthcare solutions or transportation solutions or logistic solutions and and do what we did back you know with the slides that are earlier on is to have that improvement in customer service and safety and things like that so now we take these web services and this is where the presentation really begins as we run these into a workflow engine and the workflow engine that we're going to talk about today is breeze of Io breeze so if you've seen breeze well you're actually going to see breeze in just a little bit it makes all the complexities on the left side of this slide very easy because you can get access to lots of complicated information in a visual drag-and-drop manner so you don't worry about the fact that again I have 12 different types of sensors that are giving me information in 12 different ways and now each one of these things is multiplied to crowd across the country across the world so now I have hundreds of thousands of sensors well coming into the data platform and now I bring those again into breeze and it becomes much simpler because I'm dealing with again a a simple drag-and-drop a visual interface and you'll see that just a moment so again so that just a moment is right now so if you haven't seen the breeze engagement designer getting a drag-and-drop tool developed by Aviat so it has all sorts of really cool things in it one of them is telephony communication so you have all sorts of things to manage telephone calls you know good old-fashioned Ma Bell type telephone calls we have voice and we DTMF and we have speech and things like that so we have all these different tools to manage those telephony things we also have some of the more modern ways to communicate sending email sending text messages and things like that so me I I certainly use the phone but I sent far more emails than I call people and I send more text messages on my cell phone then I call somebody on my cell phone so let's take advantage of those things as well and build those into again into the workflows breeze provides those things we go a little bit further now we want to integrate with databases because I have a database with information that I want to bring into these workflows I want to talk to other cloud services and so I have these restful web services interfaces to talk to other cloud services and now I want to do things like well I want to bring this into context Center I told you I was going to talk a little bit about contact center so I can do attribute routing so when I get the right kind of information I want to find the right kind of agent to deal with that information and so we have all the work assignment things to bring that into things like Oceana and and you know and whatnot bring that into your contact center well this is what we've done at ASI is we've added a whole new cabinet with all these really cool tools to bring IOT into these workflows very similar to what Avaya did with bringing telephony and bringing emails and and you know SMS text and database and all those things that they've done and I barely scratched the surface of those things we now have IOT and we have what is this one two three four or five six seven seven different things that we can do with IOT and don't worry I'm gonna go in and explain these things and hopefully in a way that makes sense to non-programmers explain what all these different things mean and how they can be used to build really cool powerful scalable exciting workflows so so again we just take these things we connect them up with the Avaya things that are already there like databases and emails and things like that and in a very very visual way we create these workflows that say when this happens we do this and then we go do this and we do this and then there's the ability to kind of loop and there's ability to have like if-then-else type logic very similar to if you were to sit down and draw a flowchart on a whiteboard is you draw that flowchart you say okay now this occurs in the beginning and then I want to do this and then if this then that and let's take all that and you put that on your whiteboard now you can go and sit down at the breeze engagement designer and almost literally translate your whiteboard into an application and then you know fill in the appropriate data and deploy the application and run the application and voila you you have your solution this application can be this workflow or snapping as if I calls them can be triggered on an incoming phone call it could be triggered on an incoming text message it could be triggered by some outside process telling the workflow to run so something in your database could occur and it can tell the process to run there are a lot of different ways to do this but the whole point is you take this very heat again take the whiteboard come up with the idea and you translate it into a brief snap in our application and there you go so IOT I'm going to talk about all of the different components that we have developed and I'm not going to get too geeky so don't get too worried but I'm gonna give you enough so that do you understand what these things do and then I'm gonna look at them from a couple of different couple of different directions meaning how do we invoke the technology and go out and talk to sensors and then perhaps even more importantly how do we get the sensors to talk to us so that when something happens that we are informed that that thing has happened and now we can take action and that action can come in any number of different forms because again the breeze platform is so flexible and so extendable so I'm gonna take these one by one and I don't believe this actually this might be the order I take them so look at me so I actually did something in a linear fashion so we're gonna start with I think which is one of the more kind of the the most interesting and interesting one of the most useful tasks and that is something called IOT snaps and that what it does is what the name applies is we go out and take a snapshot of the current state of a sensor so and you can have again lots and lots and lots of sensors and we can deal with these sensors in many different ways but I'm gonna keep this very simple for an element sort of deal with one sensor so I want to look at one particular sensor I want to get all the information from the sensor if you've ever looked at breeze you ever you know played with it what you do is when you drag one of these things when these little widgets on to your canvas you have the ability to set properties and there are only two properties that you set for this guy and one of this this thing called the auth token I should go the next slide the same called the auth token and think of that as the user ID of the IOT developer so we built security into the solution from the beginning to the end and so one of these things is you can segment who can control which sensors and get information from the sensors and things and this is all done in a very encrypted way I'm not going to get into the nitty-gritty details over the security and then encryption but we have an encrypted token again think of it almost there's a combination of a user ID / password of the IOT developer or the solution developer if that makes more sense to you so that is the person that's authorized to use this technology now that person authorized to use this technology we'll have a series of gateways and devices assigned to that account so that you can use you know you can get access to the information and you can segment that any which way you want but in this case we need to know which of the devices we want to talk to so again let's keep this really simple I have a sensor in a conference room so me as the solution developer I have my account and then I say well it's the sensor in the conference room and I assign a value to that and then I can just pass that value in and then it can all the authorization so yes you know Andrew this account has a billet II to talk to the sensor now what comes back from the IOT snapshot this is going to look a little not quite there but we have an output schema and two things come back from when we ask the sensor tell me your values one of them is this result of success or failure did the operation work did it work and there's more detail you can drill down into but at a high level its success or failure and then this thing called the values which is a json encoded string that's if you're familiar json is really key value key value key value so you can say you know first name andrew last name prokop city st. paul state minnesota so key value key value key value well this is how the iot work is done as well so you have all this telemetry information and the center's can have all sorts of things one particular multifunctional sensor might have temperature humidity light UV value maybe it has heart rate it's a medical sensor and then as blood pressure it has any number of different things so what it is is you'll get all that information back in this key value you know temperature 38 you know humidity 62 UV level zero point zero light you know how many lumens uh you know 657 something like that so you get all that back and it looks like this it's a little bit if you've never seen this before it might be a little bit scary so this is all the information to notice there are values in here and some of them saying no result because some of the sensors don't support a lot of the values that get delivered but so if I to sort of highlight some of the things so again in this mess it's not really a mess if you're a JSON person but you have all that values like in this case the temperature was 78 point four to the orientation Alpha Beta Gamma that's you know you twist a device around you turn it around you know what's its orientation here's the humidity of 37 point two three the UV level there's a timestamp there's accelerometer if you're familiar with accelerometer basically movements in the XY and z axis and on and on and I pull them out again to make an even easier to look at so key value key value humidity thirty-seven point two three LED status if there's an LED on this device and this one in this case it's turned off so the LED is not with the accelerometer X the temperature so that information can now get fed into a workflow and so the workflow may be you know you're monitoring the temperature of something you want to go out and check the temperature of that thing where you can go out and say hey you know mister or missus to tell me what you know and it comes back with all these different values and now you can easily use those in your workflow there's a very very simple ways and breeze to monitor you know pull the information from the JSON and put it into a Vera of a value or variable that just called temperature and you can say is temperature greater than 80 is temperature less than whatever so so that's snapshot and then one of my favorites because it's kind of the most fun one to work with is this go out and talk to a sensor and get all the data another really fun one is location so you may ask you know that the sensor may tell you okay here's here's my reading but you want to know where the sensor is because sensors can be mobile they don't have to just be you know you know put in a conference room and there they live forever the sensor could be in your pocket the sensor could be on your wrist the sensor could be in a vehicle that's moving around the sensor could be whatever wherever and so we have IOT location which is basically ask the sensor where it is we've already seen the auth token and device ID nothing has changed there but we have a new thing which is the location management family because we can say am I asking for a Gateway where's the location of the Gateway or where's the location of the device so you can say I have a gateway that has a hundred sensors to it but I want to know where that Gateway is physically gateways might not move around as much but they could devices could potentially move around quite a bit so I want to know where the location of the device is so what comes back from this the output is it gives me the results success or failure but are also giving longitude latitude the timestamp which is the last-known time of this device where it was and then some GPS informations degrees minutes seconds or decimal degrees so if we take that and we look at one of the outputs and so this comes back from I'm asking the center where it is and then I actually built this when I was in New Orleans that engaged hopefully something you folks writ engaged but I built this slide out there and what happens is it came back and said the degrees minutes seconds okay if you're a GPS person or a court you know a cartographer you'll know what this means but this is really the location information for this guy so if I take this and it came back to me and I send this information into something like Google Maps and that's the same information I'm just sending over and he said hey you are in the convention center in New Orleans and it actually came up on the map so that information that I asked with breeze where is the sensor I can feed it into another application remember I said that Brees can do Web Services and talk to other cloud service as well I can send it into again into Google and say hey this location show me a map of where it is and voila we're right there we pinpoint you down there next one info you might want to know about the sensor itself it's telling you information it's telling you where it was well tell me more about who you are you know what sensor are you maybe I forgotten or I need to build that in my workflows you can with the platform you can name the sensors and you can give them really geeky names like you know one six five four two or whatever or you can say that it's you know pillar three four to northwest corner whatever but we go out and ask the sensor tell me about yourself again the auth token device ID we've seen that before and it will come back and it will say success or failure and then he'll tell us things about the device in this case it's telling me this one I've asked for it's a silicon lab sensor puck the the name that I gave it was just SI lab sensor puck I probably could have put for two you know you know Andrews silicon lab since or whatever this one happened to be turned off so I had it not enabled so tells me that the sensor is really enabled or not or nail enabled and then we get this UID of that the sensor which is actually what the sensor is telling us it is thinking of itself almost think of as a serial number okay so that is info trending information one of my favorites and that is member snapshot snapshot said hey this is what's happening right now well what if I'm more interested in how did we get here so the snapshot would say and hey it's seventy two point six degrees well I want to know well did we get here because we rose to 72 point six or did we fall to 72 72 point six so I want to look at a a window of time a window time to look at what to look at this value over again and look at the trend so again auth token device ID seen that many times to time and I have a slide just coming up that explains this a little bit better but it's the end time of the trending window by default it's right now so if I say if I leave two time blank it says from right now at this point in time and we go back an offset 1 2 3 4 how many minutes up to 20 minutes we can look at a window of the values and then to amatory family as I'm looking at temperature like humidity at set or any of the different values that the sensors will support so I'm looking at over time what happened with this guy and so what happens is we come back with results in an output from this task again success or failure then we get things like well the name that is what is the name of the value that we're looking at and it's basically mimine mimicking back what you asked for yes for temperature well this is temperature what's the current value now that's exactly like the snapshot what's the current value for this what's pic temperature what's the current temperature but now over this window what was the high what was the low what was the average what was the median and what was the trending so again the trending higher low and I have a slide that explains that in just a moment so again so here's an example of one that I ran so came back and says I was looking at temperature the current value is sixty five point five five the median was sixty five point one two the average 64 though the high in the low of 67 and 61 and my trend is a slight rising so over the time period that I looked in my camera I think this was five minutes I have a slight rising of that temperature so you know if you think of a graph you can see the temperature gradually going up over that five minute time period and of course I don't have highs and lows so that like the stock market you know it could you know go up and down up and down but it's moving in a particular direction and this is my favorite geeky slide where I try and explain this and and you'll get to play back and PDF of all this and you can you can look at this at your leisure but this is how I try and explain trending so if you think about the word change so if the change is less than an equal to 5% then we have a steady the trending is steady so the temperature hasn't changed much because it's less than or equal 5% if we have the temperature rise more than 5% or fall but more than 5% but less than 25% we get a slight rising more than 25% we get a rising and the same thing with falling so if we got that we have a steady we have slight falling and we have falling so there I won't explain all the math of how I've done all this stuff but I look at the large amount of data that's coming across and that's it's something I forgot to point out is not only are these sensors could be complicated in terms of how they talk but how much data they produce they can produce tons of data you know gigabytes terabytes of information if you look at these things long enough and so what we're doing is we're taking all this data aggregating and building you know my will mathematical formulas to determine this information okay so let's go to the next one IOT device IOT device is the ability to talk to gateways though it has to do with how the gateways communicate with the device at this point in time it's really to turn gateways the relationship between a gateway and a sensor on or off so we've seen off token we've seen device ID seen those already Gateway that's a little bit different so here's the the Gateway that we're talking to so it has its own name its own you know hardware ID so we're saying this device on this gateway I want you to start monitoring it or I want you to stop monitoring it and this could be useful if you have a backup situations we have multiple sensors in the same area but you don't want to collect the data for the multiple sensors until there's a reason and maybe because it's fault tolerant you want to have some sort of resiliency failover plant or maybe it's because when I get into certain situations I want to turn on more sensors because I want to zero in on what might be happening so I have a center in a room and it's always reporting data when I start to come to an anomaly can condition simply we set some criteria now I want to say I need to turn on three more sensors in that room because I need to be refine this a little bit more ok so starter stop output really this one's very simple success or failure either I started the Gateway talking to the device or I couldn't IOT state this is they're all cool aren't they but this is an interesting one kind of a strange name but what it allows you to do is set this state of a device and the state think of it as really a command so auth token device ID seeing this state is a command sent down to the device and it's json encoded because I love JSON in this case this this little geekiness and that's all documented in the reference guides and all that tells me to turn this led on or this LED number one on or LED number one off so true or false but I can have also different different kinds of sensors that have other kinds of things like maybe a camera tell it to go into high def mode so again you may be collecting data for a particular room a particular part of a building and then I have some condition occur and I don't want to always be collecting different information high def but now I need to drill myself down so I will go and say hey camera going to high def mode so this is sending a command to the to the device the it's the results back or either success or failure here's a very very simple example so I have a Thunder board react a it's a board that I like to play with it's a really cool developer board because it has the kitchen sink in terms of capabilities in terms of what I want to look at this orientation does a accelerometer it does temperature humidity light and UV value and I can get my positioning information so that sensor see those little LEDs they're right in the middle LED I can't even read it's like 1 or 2 but it's a or b or something like that so there are two LEDs on this board right in the middle I use the state command to this is missus really low-budget to turn those lights on to turn the LEDs on so I can say the LEDs on turn the LED off now you might think well that's kind of silly but imagine that it was more of your writing to a display or you want to alarm set an alarm you can say you know when this red light goes on think of like gas leaks and you have the lights that are sitting there and you have to read the big red the big red light go on so I want to say red light go on red light go off those sorts of things or again camera go into high-def mode go out of high-def mode so this really simple example is I just showed you how I was turning the blue the blue and the green LEDs on and then I can turn them off again so I'm gonna change directions just ever so slightly I'm gonna get back to Brees but I'm gonna talk about actions because this is really important it's a good place to make a little bit of a change here okay in the platform so we go back into the platform is the platform is the thing that really talks to the sensors the platform is the thing that has the gateways that does all the data collection that allows you to mine the data because it puts all these web services on top of it you don't have to worry about it because Andrew worried about it and he did all that work and built it they built that into these drag-and-drop tasks but there are times when you need to get a little closer to the sensor and one of those times is you want to create rules or asynchronous actions and one of those could be again something like if the temperature rises or the light level Falls of the UV level or the pressure or the accelerometer value or this device tips on its side because I'm looking at orientation I want to know about that so what you can do is you can create asynchronous actions on those devices with different criteria so I can say when this thing occurs do something well one of those things is it can actually send web-services messages well Brees is a web service was a web server maybe you didn't know that but it is and it can accept commands from the outside world so what happens is I can have one of my device is tell Brie's to do something to fire off a workflow so again this example I'm saying send a post which is a rest your web services command to something and I haven't filled in all the blanks but to this URL which could be my brain server and I can say when the humidity is greater than 70 I want you to send this command so the brezza server gets it the BRE server with some magic the way that we've built the call says well which workflow should I invoke which data should I pass to that workflow and so then it triggers a workflow and how does this triggering occur because breeze has these things called events that allow you to build events as to why a workflow gets fired in this case I build one which is my IOT event and I'm saying I'm saying when this thing occurs which happens to be like my humidity or my light or whatever I want you to send a value I want you to actually I want you to invoke a workflow on a breeze server in this case that I built this one for temperature and I want to send something about the temperature down so I can say from the platform standpoint send this request down to the breeze server invoke this this workflow I can pass any data that I want to send and that's the beauty of this as any data I'm just sending one value I send this down to my Bri server there's my max temp at this point and what happens is inside of breeze when the workflow starts there's the max temp that was just generated in the other platform so I've passed data from one platform to another platform I now trigger my workflow which is in what's called the start task all workflows begin with the start test now I can do whatever I want to do with that workflow which might be make phone calls send text messages send emails go out and turns other sensors on remember I talked about what's going in and maybe send get more discreet turn more sensors on put a camera in high-def whatever it is that we wanted to send that turn that red light on turn that red light off so I can once I've triggered from the platform now I go into the workflow now I get all the really cool fun stuff that I can do with breeze so this actually brings me to that seventh task I didn't do that one in the previous section because it makes more sense now and that is IOT action and IOT action goes back and it has an interface back into those actions that we just created back here in the platform and specifically what I'm doing is I'm saying which action do I want to enable or disable so for instance I have an action that says when the temperature goes above 70 I want you to fire off this workflow well what you don't want to have happen is while you are managing this problem you don't want the workflow to get invoked again and then maybe a minute later to get invoked again and then a minute later to get invoked again and saying no hey dude I'm dealing with this so you have the ability to say okay I've captured this event I'm processing it I will go back and turn off the action and then I will do whatever is I'm going to do and then when I'm happy that I've done whatever it is I want to do I can go back and turn the action back on again okay if I haven't fixed the problem it's going to be invoked again if I have to fix the problem it won't be invoked so again while you're dealing with something you have the ability to go back and turn actions on and off or put in workflow so an action can trigger a workflow the workflow can maybe one of the first things it can do is basically say got it okay stop talking to me you know don't keep nagging me have you fixed it have you fixed it have you fixed it no I'll deal with it and then when I think I'm done I'll go back and re-enable the the action so that you can do you can tell me again what did I fix it today not fix it so output again just success or failure whew that is the end of kind of the breezy stuff from that level so let's actually kind of take a little look at this in a little more practical man or solutions manner and I love this example because I think this is a great movie and if you were in person I'd ask you what this was but you're not so I'm gonna tell you of course you know this is Forrest Gump and that's Bubba and so what are they talking about they're talking about shrimp and Bubba's telling Forrest all the different ways you can you shrimp and it starts I think in you know they're in their their locker or in their their their whatever you call those the quantity want whatever you call this Hut's and they're talking about shrimp and then the next you know it I think they're on the the gunnery range and then they're in finally and that they're down in the washing the the licked floor of the latrine with toothbrushes and Baba after saying well you can fry shrimp and there's barbecue shrimp and there's lemon shrimp I think he gets the finally says and shrimp sandwich and that's about all you can do with shrimp well if we were talking about IOT and Bubba was talking about all the things you can do with IOT he'd still be talking because you never run out of ideas you go on and on and on and on and on you never run out of solutions for this so I just sort of threw a couple of this sensor it's just a little quick little check some of the some of the more interesting sensors and I actually picked two of the more interesting protocols ule which is Ultra Low Energy and lots and lots of consumer devices are using UL e it has a really a good distance it's better than bluetooth it goes about 70 meters indoors so that's with lots of things in the way outdoors with a clear shot you can go about 500 meters so these things can actually transmit their information pretty far to the gateway so you will ease some of the things that you would use for you Ellie now these next sets of sensors these get more interesting because now we're talking enterprise we're back here now these are currently you certainly you can use these for enterprises like glass break and and temperatures and things like that but now we can start to get into more enterprise or city or municipality sensors like smart parking sensors that's done with a protocol called Laura and this stands for long range really clever I didn't know that at first night is what is Laura stand for it's long range these sensors will Laura's a really low power and you Ellie as well low power consumption protocol so you can build devices potentially that can run for years by ten years on to Triple A batteries so I mean one of the problems with sensors and these different protocols the more distance you get and requires bigger batteries bigger footprint they're more expensive so they're coming up with really low-cost ways of getting information from sensors to gateways and then once we get to the Gateway now the Gateway can be wireless can be you know whatever LTE and get that up into the into the cloud the gateways can be big the gateways can be powered by you know big power sources the sensors you often want small and cheap and low-power and so Laura is a really cool protocol for that so I just sort of snapshot of some of the stuff that's happening with Laura but once you do that now you can start to build all these cool solutions now we get into really solutions building so IOT and healthcare a pill bottle that has a sensor in it if the pills are not dispensed and you know they're not dispensed by really unscrewing the cap and you know shake whatever the sensor has ability to say that the cap has come off so I'm going to assume that the pill has been dispensed think of an EpiPen as well you know the EpiPen has come out of this container I can then generate an event that says it EpiPen has been open if any of your if you have kids that have epi pens you want to know that your kids open an EpiPen you want to know if your kid has used an EpiPen so you want this information to transmit through some system that's fairly long distance but you don't want to put too much money into this thing you know when your kid doesn't want to carry a battery pack so again Laura is really kind of cool for that because again Laura can actually go up to about 10 miles and they're getting better and better with that so you have these gateways and schools in there for kid opens their EpiPen at school you're informed with it so anyway you build these workflows when the conditions occur in healthcare that monitor you that you have different teams that get fired up to do whatever they're going to do a hospitality you check into a room and you have an identity and they're different devices in the room and then and and when Andrew checks into the you know whatever hotel everybody knows that Andrew likes his rooms colder than most people do so it can automatically adjust the temperatures to Andrews settings so I'm not always you know in the middle of night so it's too hot and I'm trying to find the thermostat and adjust the thermostat it's doing it the way that I want the different sensors or the lights and the whatever you know those sorts of things in hospitality food service and food service is absolutely huge and Bo going way back to that slide early on where I talked about safety is one of the primary concerns so safety if I have a those soft-serve yogurt machines and I want to know if there's bacteria forming what bacteria is really difficult to detect you need to have petri dishes and lab environments but it's easy to detect the conditions in which bacteria grow really its temperature and humidity so moisture level so if we can start to track those sorts of things and we can create workflows with you know breeze that raise an event when something has occurred gone out of the norm we can then use that to dispatch a technician shut the Machine down put that red light on it that says out of order any number of different things so there's just a ton of stuff smart beer kegs smart fryer smart refrigerators smart whatever and then running this back into into some workflows because you know in the consumer world you're basically you've got one person with one device in the enterprise world you can have 10,000 devices and so how do we manage that well that's how we manage that with workflows and something like breeze and then smart cities and I love this one here two street lamps that can detect gunshots and gas leaks so you put these all through your cities so if it detects a gas leak then it fires off a workflow that you know does what all the things that it's going to do you know notify people immediately that there's a problem notify those first responders notified the utility company or a gunshot so it hears a gunshot and there are other sensors that are doing the same thing and that triangulates where's that gunshot and then I dispatch emergency crews you know police whatever to the place that it needs to go so that no human being had to call 911 in a sense the Machine made the 911 or security robots that I see these in malls and I believe we're going to see these more in cities that can you know be like the jet and cops you know that are just out there roaming around and when there's a problem they can indicate that there's a problem potentially resolved what they can but most likely just get the right people there again through some sort of workflow to get the right people attribute routing to to take care of this problem again in cities or in malls this slide is a bit of an eye chart you can look at it at your leisure later but smart buildings why you want to invest in smart buildings lots of different advantages of both the monetary advantages and also just your social responsibility profile you know this company is doing the right thing by you know lowering their energy footprint in their buildings so how can we get going on this stuff well we've offered a couple of different ways one of them is if you want to develop this with breeze and there are a lot of good reasons why you'd want to develop this with breeze is you would get the you want us but you're not quite ready to make the investment you'd get our IOT QuickStart the IOT QuickStart gives you access to a full equipped breeze lab in the cloud gives you access to all of the IOT software I actually throw in a few more gimme some other stuff with in terms of artificial intelligence and natural language processing and ServiceNow and some other fun things and then a sensor and you can actually start playing with this technology to understand how to make it work another way is saying I've been talking about breeze this whole time well all this work is now inside of zhuang as well so now you have a hundred percent cloud-based IOT platform develop solution so you can go out and get as go to Zang that IO sign up for a free account get a sorry an account with our back-end system for the the platform and then start building your own workflows a lot of resources so I've if those of you that know me know that I write quite a bit so I have some articles for on Avaya I have some articles on no jitter there's some videos out there as well one of my favorites is one that I a video that I took of what the Avaya team is doing with some of the newest with the IOT IOT work that I'm doing if you're out it engage and this is also gonna be an enterprise connect that they build a Lego smart city which is really cool and I just did a low-budget video of Nathan's Duty doing showing the demos it's gotten a whole lot better actually since the video and I've been working with them on some other enhancements as well so things like train derailments power outages smart parking so and things like that maybe integrate it with a team stuff and text messaging and oh it's sort of a notification system so there's some really interesting resources out there for you and which takes me right to the end except for a few questions and I see some questions here but I want to show you and mark introduces in the beginning is that we have a series of webinar so the last one that was kind of leads into this one so you want to go and find the playback for what is IOT and mark you'll correct me if I'm wrong but I believe we're putting all these on YouTube so if you go to youtube and you search for arrow systems integration find our YouTube channel you will find the play backs for all these and you may be sending them out to the folks as well but I know that they're going onto YouTube and then all the cool ones that are coming up in the future so so let me get to just a couple of questions here and then feel free to ask more questions but I have a couple here and that is and this one just came in to us which is a good one I should have covered is when would I choose Zang over Brees so in terms of the IOT they actually do the very same things so it's the same features that are in Brees are in Zang so why would I choose one over the other and really it's your environment how are you integrating this are you integrating this really tightly with your current vehicle system if the answer is yes then breeze is the way to do is because if you want to integrate with the contact center and attribute routing and all of the phone numbers and things and trunks and all that on your existing phone system breeze is the way to go but if you're building a standalone solution that doesn't need to talk to your phone system doesn't need to really talk to your contact center but you still want to manage you do the telephony stuff and the notification stuff that is provided with Zhang what I would do was a so if I am a farmer and I want to create a solution for my farm with my sensors that are maybe moisture sensors all in the ground I don't own an abaya system so but I could do that by building a Tsang solution and get the same kinds of things both that the bi-directional the sensors are you know going out and telling asking the sensors questions or the sensors asynchronously firing you off another one this is about the platform how much or how long is IOT data stored in the cloud well naturally how you want to set it up so if you want to store lots of data so remember trends can look at patterns over time and what I didn't explain perhaps then was I can pick Windows anywhere in the time of the data it doesn't have to be just now it could be anywhere in the time of the data from the point you started gathering data till now well how much are you gathering well that really depends on how much how much do you want to pay for how much data do you want to store if it's your own private cloud you'll be certainly engineering that if it's a public cloud you'll be paying for that so you want to figure that out so it's really how much do you want to do it here's another one and engage I saw demo that combined IOT with service now is that available as part of this offerings well the answer is yes and no in that it is available it's not the IOT offering but it's it's own offering so if you have development that involves talking with service now and I have a really cool video in fact if we come back here to one of the resources it's this one the third one down the service management one that actually shows you how you can combine service now in breeze and IOT so it's it's not part of this offer it's its own offer but yes we offer a service now integration that can be invoked combined with your breeze workflows it's not part of Zang at this point in time it's part of breeze so if you want the service now integration then you're using the brain that the sir you have to service now integration you're using breeze and you're not using Zang and that was it for questions and my goodness I think we are almost exactly right on time which is good so I'll give you a couple of minutes back so if anyone has any more questions ask them now otherwise you know how to reach me it's at the very first slide a pro cup that's PR o Kop I like to tell people professional police officer prokop a pro cop at Aero si.com you can send me an email if you have a specific question or you can reach out to us through oh my goodness I think it's right here on this slide on the the breeze developer kit there's information you can reach out if you're interested in that there's a phone number and there's a another email address advisory services at Aero si.com to learn more information if not a mark do you have anything to add to this to this webinar before we sign off Andrew just a thank you for your time and in the overview today it was it was great please just be sure to look for the recording passing along dear to your fellow workers and the other sessions are out there as well great thanks everyone and have a wonderful wonderful day all right bye now

Be First to Comment

Leave a Reply

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