Welcome to Solving with
AWS Solutions, your deep dive
into reference architectures
built by AWS that are ready to
deploy instantly in the cloud.
I'm Johny, joined today by Eric
from the AWS Solutions team.
Hi everyone.
Today we're going to be talking
about Amazon Virtual Andon.
With this solution you can
create a data hierarchy that
models your factory floor and
configures events for common
equipment or process problems.
Members on your factory floor
can then raise issues with one
click and immediately notify an
engineer for resolution.
That sounds good.
Let's begin.
OK, Eric.
Take me through this.
Sure.
So here we've got our
solutions landing page.
Scroll down here.
We've got a link to
our implementation guide.
Here, we've got a link to our
CloudFormation template.
That's how you would deploy the
solution right
into your account.
Here we've got a link to
our source code.
It's all open source
available on GitHub.
And then here's where we've
got our architecture.
Go walk me
through the architecture.
Sure.
So here we've got
our web console.
This is where the users will
interact with the solution.
We're using Amplify to interact
with the back resources.
And we've got a AWS AppSync as
our API layer.
When issues are created in
the solution, they're published
to this IoT topic here,
where they're ultimately are
going to get forwarded
by a rule, IoT rules engine to
this Lambda function.
That's where issues are going
to get created.
Here, we've got this Lambda
function that's creating the
issues in the system.
If you've created an event that
has email addresses or phone
numbers associated with it,
an SMS message will also get
published that will notify you
directly via email or SMS.
And then finally, here up at
the top here you'll see we've
got
automated machine monitoring.
This is where if you're
potentially using a service
like look out for equipment,
which is automatically
monitoring your machine
telemetry data, we can then
send that that data can be sent
to us automatically to then
create issues in and off.
Sounds good.
How about you?
Tell me more about the AWS
AppSync?
So AWS AppSync is a
managed graphical service.
So we're using that because
it's great at keeping data up
to date in real time.
So as you're taking actions on
one screen, another screen is
getting that data sent
to it automatically.
And how about AWS IoT Core at
the middle?
What's the purpose of this
component?
So this is what we're doing,
like our routing for internally
within the solution.
So for example, when you're
publishing a message to the
IoT topic, you're it's getting
sent to this Lambda function.
That's essentially what
IoT Core does.
It's good at getting IoT device
data and routing it to
different
endpoints within AWS.
I see.
Lets go to the console.
Sure.
So here you've got
the console.
I've already gone ahead and
modeled my factories,
I've created my sites, areas,
processes and whatnot.
So if I go here to the
client view, this is where
we're going to start actually
seeing issues get created.
So the client view is think of
it as a tablet that is mounted
on a station where associates
are using the
factory equipment.
This is where they would be
able to raise their hand and
say there's something stopping
me from, from continuing my
work and this is the issue
that I'm having.
And then when those issues
are raised, there's a different
view that a factory engineer
would be seeing these issues
come in as they're raised
in real time.
So if I look at the observer
view here and I'm looking at my
JFK site, we can watch events
automatically get going.
Come in.
So I've got here a
tablet where, you know,
imagine this is mounted
in your factory floor on
on that station.
So I'm going to create some
events here, and these events
are completely customizable.
This can be anything that you
want them to be.
See, as I've created
these events, all I had to do
was tap and they've come up
automatically on
the screen here.
So if I tap again, I can
clear an issue.
If I maybe I tapped
one by accident.
Now, if I go here and I reject
a message, it's automatically
cleared from the from the
client view as well as the
as the observer.
And if I acknowledge it,
that's me as a factory
engineer saying, I see
your issue, I'm on my way
to resolve it.
So now you see here on the
client view,
it's automatically been shown.
Now the client is aware that
the fact that an engineer's on
their way to fix that issue.
So if we go ahead and and go
back to the observer screen
here now I'm
the factory engineer.
I'm working on
resolving this issue.
I see the issue is I'm
out of labels.
I'll go ahead and look at the
machine and see what could
be causing that.
And then I'm going to head and
close that issue.
So if I close that issue and
there's a root cause associated
with it, you know, what are
common problems that lead to
these events happening?
I'll go ahead and select that.
And then if I go ahead and
submit here now, I've closed
that issue and the client
screen is also sees
that issue clear.
I see.
How about the metrics and
history tables here?
So if you take a look at the
metrics page, this is
for factory managers.
So they're going to come in
here and they want to see
what's going on with my
with my factory.
Like, what's what are the
common issues that are occurring
?
What are the resolution times,
things like that.
So you see here we've got two
graphs on the left
hand side here.
We're showing over the past
seven days just the raw number
of issues that have come up on
day over day.
So you can see that trailed out
from left to right there.
And then here for the last
twenty four hours we're seeing
in three hour chunks, what are
the number of issues that have
been created?
So you can imagine as you're
working intraday, you want to
just keep an eye on this line
and you don't want to see too
many issues come up or as you
might want to have to see,
what can I do in my processes
to maybe reduce the number of
issues that come up?
So down at the bottom here,
you'll see we've got just
aggregated at the event level,
aggregated stats on in
each individual event.
So you see here on the out of
boxes event, I've had 10 over
the past seven days for an
average resolution time of just
over three minutes each.
And that's really it.
We've got some user management
at the top here.
This is where you create the
root causes that get associated
with your events.
But but that's that's
pretty much it.
Thanks for walking me
through this, Eric.
Yeah, my pleasure.
Thanks for joining us as we
explored Amazon Virtual Andon
Find the solution and many more
on the AWS Solutions website.
See you soon.