This video
covers the basics of event
frames in PI Coresight. How to find
events and how to analyze our display
using the event time ranges.
What are event frames? Event frames are
essentially a way to basically bookmark different
sections of our data. Here I'm looking at
some process variables for a blender and I can see that
I've gone through several cycles where my agitation
has gone up and down and up and down.
I'm interested in looking at a specific
blender uptime from when my blender
was turned on til when my blender was turned off.
With event frames, I can put a little
flag here at the start when my RPM is at
zero. And another flag here at the finish
when my RPM has gone back down to zero.
The event frame captures the start and end time of this
particular part of my process as well as the
duration and any information that I'm
interested in capturing for this time-range
that I've specified. Event frames in this
example are looking at distinguishing
different parts of my process. Event frames
are also useful for marking
operator shifts or downtime events.
If I want to look and focus on that specific
blender uptime, in PI
Coresight, I can simply click on a
button and my display updates. Let's take a few
steps back and see how we get there.
I started off
back under the search adding my process
variables like agitation for
my blender. One thing that's important
to keep in mind is event frames are not something that are
setup in PI Coresight. It's setup outside of PI Coresight
and PI Coresight is the visualization tool to look at the
event frames. I've had event frames
setup for this particular blender. And so to find
them, I'll need to navigate down here to the
related assets and
events tab. So let's click on that.
When I click on related assets and events, I can
see that I have several
events showing up in my events
list here. Where are these events coming from? Well PI
Coresight discovers events that are based on
the assets that have data items in my current display.
I was looking at the agitation,
the pH and the pressure. And these were all that you
could see for blender 400. So PI Coresight
is going to discover events that are specific
to blender 400. You can also notice
that for the event list, it has a
time-range of events that it is pulling
from. How is this time-range determined? It's
based on a couple of things on my Coresight display
down here. The first is the start time.
It also depends on the end time and
the duration here. PI Coresight
will discover events from the start time,
9:29, minus the duration,
1:10. So we'll start looking
at around 8:20, and it will finish looking for
events from 10:39, the end time, plus
the duration, 1:10. So around 11:50.
And that's exactly what we saw up
here. Events that partially fit into the
time criteria will be shown in the list as well. To modify
the time frame you are searching for events,
you can basically change the start time, the
end time or the duration. Let's take a
look at that. If I expand the
duration to one week,
my event list is now
pulling from a bigger time period which you can
see here. And I have a lot more events
showing up.
If I want to look at a particular event
such as my blender uptime, I can start looking
at this particular event. If I
drill down, I can find out information like the
time range. If I want to apply this event
to my display, I can do that. In
order to do that, I'm going to click on the clock symbol here.
Before I do that, let me draw your
attention to the current status of the display. I
have a start time of 10:39,
an end time of 10:39 and I'm going
from March 7th to March 14th.
I'm going to go back to the clock and
click on that symbol. You'll notice that
my display updates. My
start time is now 9:29 and my end time is
10:39 matching my event time frame.
Another thing you might have noticed is
this icon has a locked symbol now
and the refresh button is greyed out. When you apply an event frame
to your display,
the event list becomes locked. That way you have your
original list, even as the displayed time frame
changes. You can unlock the list and
revert back to searching based off of these display
settings down here by clicking on the lock icon.
Unlock and refresh.
So I have selected my blender uptime and I've
applied that time period. My blender uptime
has some sub-events as well
to describe the operation charge and the
operation finish stage. If I click on the clock, I
can update my display to those time periods
of that process as well. And operation
finish also has some additional pieces --
an agitation and a drain portion. And I have
an event frame setup to describe these parts of my
process. One thing that I'm particularly
interested in is what was the drain
level at the start of the drain process for my
blender? Rather than seeing if I have that attribute
back under my search, and how can
I apply it, that's something that has been captured
in my event frame and I can add it directly without doing a
search. If I expand drain and look at
data items, I can see
one of the data items I have is actual
level at 10:31:19. This corresponds
to the start of my drain period. To add
this item, I can select it and drag and
drop it to my display until I get the green plus
sign. I could've added it to my trend or I can add it as a value
here. Now you've seen how PI
Coresight can be used in the context of
finding events and also applying
event time ranges to our display
and adding items captured in an event frame
directly to the display as well.
[silence]