Welcome to this video in: "See the light: Easy wins to improve your asset framework
experience". So we've done four out of the six issues that the engineer found for us.
The first one being that FFS 0-5 wasn't available in PI Vision, we fixed that by applying a template
to the unit. The second issue was that the sugar grain size was duplicated for units three,
four and six. This is a common symptom when people use "allow extensions". So what we did
is we disallowed extensions and then we used what is called a derived template to take care
of the difference between the salt and the sugar units. The third issue we fixed was
that the sealer temperature was way out of bounds on the form fill and seal machines.
That is because the units had been purchased in Europe and we're measuring in degree Celsius,
we are displaying in Fahrenheit and so we just needed to make sure that we double specified our
units of measure in asset framework and so that I knew that it needed to do the conversion. And
then the fourth issue is a biggie it saved a lot of time for a lot of people because
we stopped referencing a three hundred thousand row table and moved it down to only return the
data for these specific units that we queried, that was done through parameterised queries.
Now the fifth issue the engineer pointed out to us was that in PI Vision when he was looking at
the detailed display for the form fill and seal machines he noticed that on form fill and seal
unit number four there was a problem where the nominal max throughput wasn't being displayed.
This is likely only an issue on unit number four and it works for the others. So what we gonna do,
again configuration changes don't work in PI Vision, will switch across to PI System
Explorer and I've got form fill and seal machine four loaded up here. To see how the nominal max
throughput value gets its data, we can click on it and have a look at the settings field
on the right hand side. Now in our case this is a table lookup and our settings
are we want to select the max throughput from the table called model specifications where
the model value in the table is matching the value of the model in our attributes.
So we want the model in the table to match our model which in our case is MF Tecno. This seems
like there should be no problems it's working for unit number 6, so what we'll go ahead and
do is open up our library and just inspect the table for model specifications. You can
see we've got the three entries the ADCO, MF Tecno and the BibBox entry that I made in our
previous exercise. What I've put up in front of you is a comparison between units FFS 0-4 and
the table and if we have a look and the error is pretty clear to see what the problem is,
we've got ADCO is 75 and MF Tecno 70 however, FFS 0-4 is spelled MF space
T E C H N O and there is no H in our model table. Now there are two ways to fix this.
The first way would be for me to go to my elements and because model has got a data reference of none
I can simply come in here and delete the H. If I hit refresh, fantastic problem solved we can
go back to working. You are relying on a human to spell correctly, and if I've learned anything it's
that the more you can take the possibility of a human making a mistake away from your system,
the less likely it is that there will be mistakes in the system. So what we want to do instead of
having the the person type in the name of the model, we want to make it so that they can
select from a drop-down. That is possible in asset framework using what are called enumeration sets.
Enumeration sets are found in our library and if you are familiar with the PI Data Archive,
if you've worked with PI Data Archive for a while this can be sort of analogous to what is called a
digital set in PI AF. What we're doing here is every time the system sends a value of 0 or 1,
we will convert it into MF Tecno or ADCO. What we can also do is in
our element templates for sandbox FFS I can go up to my attributes,
select nominal max selecting model sorry and instead of using a value type of string
we're gonna say I only want values that come from the model list enumeration set.
If I select that and check in my change, when I go through to my elements you'll see that model
is blank for FFS 0-4 and one and two. That's the problem with applying a digital set after the fact
it will wipe the results that have been written in there. So what we're gonna do is go and fill out
this form according to the table that is on screen at the bottom. So unit 1 is ADCO, two is ADCO,
three is ADCO, four is MF Tecno, five's ADCO. Now if this is taking a long time, and six is MF Tecno
if you worried that this takes a long time it is possible to do all of this through PI Builder in
Microsoft Excel. For six units that's not worth opening up Excel and going through the process but
if you had 100 units you definitely gonna wan to do that. What we will do is check in our change.
Now when I go back to my PI Vision display I can see that for FFS 0-4 we've got the correct
model now MF Tecno is spelled correctly which gives us the nominal max throughput
and also go to FFS 0-1 and FFS 0-3 and they seem to be working. Now the best practice
we've applied here is that it's always a good idea to remove the potential for human error;
so by applying an enumeration set and letting the engineer choose the asset rather than type
it in, we've saved ourselves some potential headaches in the future.
The next is going to be the last of our six issues and that's just fixing a title
in PI Vision and making sure that it changes according to the asset that we have selected.