So besides the HVAC Manufacturing entity,
Contoso also have a smaller one
which is about vending machines.
Because that entity doesn't have the skills and
the resources to build their own IoT solution end to end,
leveraging the past services from Azure IoT,
they can leverage the IoT,
the Microsoft IoT Central solution.
I want to show you the various parts of
IoT Central by wearing different hats once again.
The first hat I'm going to wear is the Operator hat.
What you're seeing right now on
my screen is the Operator View
of this Contoso Vending Management IoT Central Solution.
And from here, I can do several things.
I have a high level landing page.
The main thing as an Operator that I'm interested
into is visualizing different device types.
And within these device types,
like let me pick for example,
refrigerated vending machines.
And in there, I can see the various,
in our case, simulated vending machines.
But I can actually monitor each of them.
I can visualize what
the actual measurements from all the sensors on
these very particular refrigerator machine and
actually get a good graph of their actual health.
There is a dashboard that has been created for
this device type that I can also dive into.
I can see some KPIs
here that are monitored for this device type.
I can visualize some of its settings like the fan speed.
I can see the data real time
actually about these various sensors.
So, it's a very useful dashboard that as an Operator,
I can take advantage of,
to have a very nice and fast snapshot
of the health of my machine.
So, if I look at the rules for that device,
what I can do is actually edit some of these rules.
I can visualize them first.
I can see the criterias, the name,
and I can actually edit and modify them.
Here in our case,
we have rule that will
monitor for temperature that is too
high and what it's going to do is actually
send an email when that happens.
For the device, I can also
visualize what we call the properties.
This is the metadata that is shared by
the device with the Microsoft IoT Central Solution.
It tells me what kind of model,
when it's been manufactured, the serial number,
all that information allows me to have
a fine understanding of
which device it is and what's running on this guy.
The "Setting" section allows
me to actually interact with that device.
I can change the fan speed for example here real quick.
So, let me switch that to
different RPM value from five to three and I can see
that the Microsoft IoT
Central Solution is actually sending
that configuration to the device
and is waiting for that device to be in sync.
So, I can see that has been synced and I
have this regular updates from
device to IoT Central
in terms of measuring what's going on.
So, you see like I have
this nice view of my refrigerator here.
So it's as an Operator, I can already do a lot of things,
monitor my devices, but what I
think will be more interesting right
now is actually switch hat.
How did all that arrive in my IoT Central Solution?
So, what I will do is actually create a new device type.
Now, I'm wearing the Solution Builder hat
and the first thing I'm doing actually is switching to
that builder mode and I can create
a new device template and
that device template will actually be a custom one.
And I will call it something like, I don't know,
Pizza Vending Machine and
when I create this new device type,
what happens is IoT Central will create
that infrastructure but also
will create a first stimulated device.
This is going to be my reference device.
The first thing I want to do in there is
actually create some, what we call "Measurements".
I want to add some "Telemetry".
The first one will be "Temperature"
and the field will be called "Temp".
It will be in Celsius.
It will go from zero to a hundred for example,
and only on decimals, and I like the color.
I was like, just save from here.
I can create another "Measurement"
which will be "Telemetry" again.
And I will have this one being "Humidity",
pretty typical in a vending machine
and it will be a
"Percentage" and it will go from zero to 100.
And for this one,
I'm going to pick a different color.
So, now I have my two "Measurement"
for that device that've been created.
I can also define "Settings".
So one of the "Settings" I want to define,
once again as a Builder,
is for example, the "Fan Speed".
So, I can define "Fan Speed" and that's going to
be "Fan Speed" as the name
underneath and I can actually add
some interesting values to
our or parameters to that text field here,
not much that I want to customize.
So, what I will do actually
is set initial value which I need.
I will say 20 percent by
default and then I can do "Save".
Right? So, this defines
actually what the Operator will see.
So, you see I can also move that,
so that when he's going to switch
the "Settings" queue for that vending,
so the type of device,
it's going to have this particular item at that position.
In "Properties", what I can do now is do something else.
I can actually add a date for example
and put a date like "Manufacturing
Date" and this one will be
"Manufacturing Date" as the actual field name.
I don't need an actual time.
I have an initial value which is
today and it is a required field, right?
So, let's define that as is.
This is one of my properties that
the Operator once again will be able to see.
And then what I want to do is to find a dashboard.
What is it that the user will see in that nice dashboard.
So, the first one I can add,
you remember, I added "Temperature".
I can show a legend.
I want to have the past week and is going to be
"Temperature" here and I saved this one.
So, this chart actually will show
the real time temperature and
the will show that one week of data.
I can add another one which is for example,
the bar chart that will say "Humidity" and
track in that way,
past week is going to be "Humidity". You get the idea.
But eventually you can say,
we'll see I want some "KPI" here.
"KPI" would be "Health",
let's say and we'll say "Temperature" in
average and look at that for the past months for example.
And I will have a monthly tracking of that
"KPI" here which is "Health" and I can move it up there.
Right? So, you can see as well that I can
start moving around my charts.
I can really do that graphical editing of this dashboard.
So, now I have this dashboard all ready and prepared.
What I can do is make it available for my operators.
And so, if I go back to my device view,
I remove the edit one.
I can see now there's
a Pizza Vending Machine dashboard
and you can see the exact dashboard that
just created a minute ago.
Now, what I want to do is actually switch gear.
We've seen what the Operator visualizes.
We've seen how the Builder
interacts with Microsoft IoT Central to
create these device types and
the dashboards that the Operator will be using.
But now, how about connecting a real device.
So, if I want to do that,
what I will do is actually switch into
that other device type which
is called "Drive-Up Vending Machine".
Right? And here I can see I only have a simulated device.
What I need to do is create a real device.
And when I do that, basically it creates an entity into
my IoT Central Solution which
happens to be leveraging
the Azure IoT [inaudible] Services to back end,
so it's an Azure IT Hub which is behind,
so it created a device identity for that real device.
And I want to connect a real piece of code and for that,
I need to have this connection string which is unique to
the device and I will be using
in a node application in our case.
So I have a piece of code ready here
which is very simple node application using
the Azure IoT SDK for node
and it's basically sending telemetry data,
the temperature and humidity expected and will be able to
respond to some commands like
the fan speed for example or others.
I want to paste that connection string
here to allow my device to connect to that
"Instance" of IoT Hub and hence
connect into my IoT Central Solution.
And what I will do is run that "Drive-Up" and to save
the file and I will start the file here.
So, the device is starting.
It will connect to the IT Hub
"Instance" and will start sending telemetry data.
And when I go back to my dashboard for that very device,
what I will see is actually
the measurements that will start flowing as
the telemetry data is received into IoT Central and boom,
we have the real time data that is coming
in and we we're seeing the outdoor temperature,
in our case, here that is shown on this graph.
So, you've seen how our Contoso Vending team is able to
create a full blown UI Dashboard
and a solution into IoT Central.
Last but not least,
I want to show you how they are able now
also to create stats
interface for their customers for them
to have access to the data in IoT Central.
They have an "Administration" page where they
can actually define "Settings" for the application,
a name, a nice UI, a nice icon.
They can also then define "Users" so they can assign
roles to the various "Users" that they
want to give access to the solution.
So, they can have one customer which is, for example,
a building where they have several vending machines.
They can create a couple of
accounts for them that will be
just like "Read Only" on that telemetry.
We'll be able to see the dashboards and see how
the vending machines are doing and that's
how I can actually offer that as
a dashboard for my customers.
So, you've just seen how
easy and just in a matter of minutes,
we're able to create a full,
end to end IoT Solution using IoT Central from defining
device types to defining
dashboards with all the data
we need our customers to watch and see,
to defining what the "Administration" settings
are such as the roles the "Users" and so on.
All of that from a web page without touching
any code into IoT Central.
Thanks for watching this video about
Azure IoT and if you want to learn more,
you can visit Internet of your Things
dot com and try it out.