Welcome to this lesson and "See the light: Easy wins to improve your asset framework
experience". In our previous video we just finished a meeting with the
engineer on site and we'd asked the engineer to find a couple of faults with the system
we're working with that we are building for them in both asset framework and PI Vision.
We did that by opening up PI Vision going through a couple of screens that had been built and then
the engineer just drew our attention to a couple of things that he wasn't really happy with,
we noted them down and what we're gonna start doing now is apply some PI System
based practices to go through and fix those issues that the engineer came up with. Just
to start off our first issue was that when we opened up PI Vision and we looked at the
detailed report the monitoring of our form fill and seal machines the first issue the engineer
came across was that they knew they were having issues with form fill and seal number five the
moisture sensor was having a couple of errors and we weren't able to show him the asset.
So for some reason we can switch to all six assets except for FFS 0-5,
so that's what we're gonna want to fix now. In order to fix that we can't make
any configuration changes through PI Vision so we're gonna have to go ahead and open up PI
System Explorer and what we can see here is that we do have a fform fill and seal machine number
five. If at this point you are not in sweet and savory Corp what I'd like you to do is go file,
database and just make sure that you are connected to the sweet and savory Corp
database. Sweet and savory Corp data is a second database that we have built in the
background and that is what is generating all of the the values for our tags. So we're going to
ignore that for this lab just so that you know why it's there and we're gonna go ahead open
up sweet-and-savory Corp and expand through our sandbox, into packaging and we'll look at FFS 0-1.
FFS 0-1 should be identical to two, three, four and six however there's a problem with if FFS 0-5.
I'm gonna go ahead and select FFS 0-5 and at this point we can see there's some discrepancies. What
I've put on the screen for you now is a side by side view of the FFS 0-1 and FFS 0-5. What you'll
notice is that there looks slightly different, the layout is slightly different they've
categories FFS 0-1 has got identification, overall equipment effectiveness and process data. Whereas
FFS 0-5 has got a big category for none and then categories for identification and the OEE section.
Another big difference between FFS 0-1 and FFS 0-5 is that on one next to all of the
attributes you can see there's a green box with a black T in there. What that tells me
is those attributes that have that T are based off of an element template whereas
FFS 0-5 there is nothing. This asset is not based off of a template. We can confirm that
by going to the general tab and where we see template on FFS 0-5 it is empty,
however when we select FFS 0-1 we can see that FFS 0-1 is based on the sandbox FFS template.
Now the reason for this is back when we first started building out the assets what had happened
was we notice that on FFS 0-5 the moisture content sensor was faulty. So we didn't want
to have an empty attribute for moisture content in our asset so what the PI System team decided
to do was to remove the template from FFS 0-5 and build it up from scratch on its own. Now
while that might work in the short term, in the long term it's created a couple of issues for
us in that we've started changing the way the categories are built and some of the
naming conventions have changed and we've built displays based off of the templates and because
we're not using the template for number five and none of that functionality is available to us.
Luckily this is a relatively simple fix we want to make sure we use templates wherever possible,
so what we're going to do is we're going to convert FFS 0-5 and may could use that the FFS
template. I can do that by right-clicking on FFS 0-5 choosing convert and then change template. At
this point I'm going to be shown all of the element templates that are available to me,
the one that FFS 0-5 is based of is the sugar sandbox sugar FFS. By selecting that and saying
okay, what it's going to do is it's going to apply that template to FFS 0-5 and the
problem with this is we've made some changes. So for example moisture content doesn't exist
so that's something we're gonna have to take care of. Our last service dates and nominal
max throughput are referencing an attribute called asset name that no longer exists.
What we can do to fix this relatively quickly is just force everything that has been configured
to conform to the template settings. To do that we can select any one of these,
hit CTRL-A to select everything, then we can right click and say reset to templates. That
forces the template configuration to be applied to FFS 0-1 and another thing we have to do is,
because the default model is a blank string we need to specify what the model of this asset is,
in our case it's ADCO. Okay now when I hit refresh and apply those changes
you'll see that based off of the model I'm getting the nominal max throughput now.
Okay and because I've got that I can get how far behind target I am,
what my packaging target per minute is, a whole lot of extra data. The reason in the first place
that FFS 0-5 wasn't based off of the template is because it was a faulty moisture sensor.
Now what we can do is at the moment this is not going to cause any major problems,
every couple of minutes the system is going to look for the moisture content tag if it doesn't
find anything there's no problem. But we don't want the engineers in the field to be able to
see that there's a problem with moisture content for FFS 0-5 so we can exclude this attribute. And
excluding an attribute basically just means that that specific attribute doesn't apply
to this asset. It won't appear in searches, it can't be used in any calculations and it's
a much safer fix to exclude an attribute than to not have the asset based off of a template.
In order to exclude moisture content I can just select it and in the properties I can
select excluded. It says if checked this attribute does not return in
searches and it won't return a value, it won't be shown in most applications.
With that done FFS 0-5 now conforms to our standard and we've taken care of the
excluded moisture contents sensor and I can go ahead and check in my changes.
Now this change won't be reflected immediately in PI Vision so you may have to wait a couple
of minutes. We will switch across to PI Vision and reloading the sandbox FFS monitoring page
will give us the opportunity to see if we can select that asset. In our case we have shortened
the caching interval for PI Vision, this is done through the PI Web API we've shortened
it to one minute by default on your system it will probably be three minutes and this
can be set up to a day. So depending on your configuration it may take more time
for changes in that you make in PI AF in the asset framework to be reflected in PI Vision.
However, I can go ahead switch to FFS 0-5 now and things look like they're working I've got my last
service date, I can see my sealant temperature, packaging right FFS 0-5 now behaves exactly the
same way that every other asset does. The only difference between FFS 0-5 and the other form
fill and seal machines now is that whenever we are displaying moisture content we will see a
N/A for not applicable it doesn't apply to this asset highlighting FFS 0-1 it is available there.
Now before you carry on to the next video in which we're gonna solve issue number
two that the engineer picked up on, there is a little bit of reading to take you through the
the attribute properties that we looked at. We looked at the excluded property,
there's a couple more and then we're gonna introduce you turn to some
of the replacement character syntax that you will often work with in AF.