For a final project, I've spoken with some engineers at the plant where I work and have come up with a use case for trying out event frames. In one part of the plant, we have three large compressors that contain multiple sub-sections, with each section having a pair of vibration sensors at both ends of the section. I'd like to model all of this in AF with templates since each vibration probe would have similar properties, as would the compressors themselves. I'd then like to have event frames to capture vibration alerts, including roll ups to confirm that multiple probes are sensing anomalies, and not just one. I'd also like to have event frames to capture compressor run time statistics and downtime root causes.
In total, I expect to have 3 compressor elements, each having 3 or more sections, with each section having 4 vibration sensors. I would then have the event frames mentioned above, with critical criteria triggering notifications.
Is this enough for the final project?
This sounds like an excellent project idea loaded with analytics content. I look forward to seeing how it progresses.
It sounds like you are still working on the AF hierarchy; have you had much experience in this area? It would be great if you could share your structure here or if it would not be allowed by your employer, I can review it privately and perhaps we could come up with a cleansed version we could post here.
For run times, it depends what you are after. If you want a live number to show on a dashboard, input to something like an OEE calculation, or trigger a Notification or maintenance alert, then a calculated value that outputs to an attribute is useful. On the other hand, if you are doing some sort of BI type of analysis where you want to sum runtimes or production numbers associated with runtime or you want to categorize these summaries (think slicers, like by equipment type, shift on duty, day of week, etc.), then EFs can be a great way to track runtime events and serve as input to the BI tool. You may want to look into some of our CBM related materials here.
Downtimes are a great case for EF; I believe we have some AF Example Kits that deal with downtime tracking that maybe helpful.
I'll see what I find on the above two and post back.
Please post back with any questions or comments you may have.
I've made some decent progress and was wondering how to best submit the project itself. Do we do a WebEx/GoToMeeting or do I submit some screenshots or something?
Edit: Scratch that, I see the instructions about creating a Word doc in the course outline. I was wondering if you could help with something else that's causing me grief. I followed the video when creating my Event Frames and included a "Duration" attribute. What's odd is that it's returning the seconds value, no matter what UOM I select. So I have a 40 hour outage, and the Duration in the Event Frame is returning as "145380 h", which is clearly wrong. 145380 seconds is right around 40 hours. Any ideas?
That is odd. Can you post some screenshots of the configuration of the EF attribute and the results you are getting. What are the versions of AF you are using (in PSE, select Help-> About PSE to get a window with the Explorer, AF SDK, and AF Server versions)?
Please let me know.
PS- If we can't get the standard PI Point data reference Duration attribute working, there are workarounds. For example: Duration attribute on an Event Frame - Part 1
I somehow fixed the issue. I had changed it to just display seconds so I could move on. This morning, I added a few more attributes to get decent information during the EF and everything was working nicely. I then swapped it to minutes to try and get some screenshots for you and now the time is converting properly.
I literally did nothing to the Duration attribute itself, aside from change the UOM from seconds to minutes. I did this countless times yesterday but today it worked. I'm happy for now lol.
Great! Glad to hear it is working!
Please try to get that project to me today if you can.
I have done couple of things for the final project.
- PI Analyses - expression and PI Notifications for Time monitoring.
PI expression to find the difference between the current time vs the source system time. I have used this expression - String((parsetime(string('*'))) - (prevevent('IIT Time',(prevevent('IIT Time','*'))))). Below is the PI notification I generated.
- PI Analyses for fridge temperature monitoring on site.
There are multiple fridge units on site and I have created AF template and analyses to monitor the average temperature and how long the high temperature was out of control. I have backfilled the data.
Temperature average expression - Convert(TagAvg('Temperature','*','*-24h'),"°C")
High temperature time monitoring - Convert(Timegt('Temperature','*-1d','*','Temp_High 8 DegC') /60/60,"h")
I'll be working on setting up rollup and PI visualisation using process book.
will this suffice for the final project?
This looks good; thanks for sharing!
You should be able to avoid all of the string and parse time functions in your date math. Please see the reference doc on analysis I posted on this class thread below and also this thread on date differences:
You can use the convert function to convert the difference to seconds or if needed, cast the difference to an integer or float using the int or float function respectively.
Also, can you provide some more info on the attribute IIT Time? With the expression, String((parsetime(string('*'))) - (prevevent('IIT Time',(prevevent('IIT Time','*'))))), you are going back to the event previous to the previous event (two events before current time) so my initial thought is that this event time would always be older than the current time of now (*).
For the refrigerator calculations, nice use of the convert function! Are planning to do any type of alerting on fridge high temperature events? Is there any type of interesting summary data around these events you would want to capture with event frames? Number of times the door is opened, shift on duty, etc.; anything that would help identify reasons for or impacts of the high temperature events.
Please let me know and keep up the good work!
We are into the final week now and I'm happy to see a couple of students posting ideas for their final projects! Please keep it up!
As a reminder, I'll need some time to evaluate projects so please try to have them in by Friday morning and start posting ideas here if you need feedback before finishing them up.
Also, to help guide your work with asset analytics, please take a look a this document from one of our resident AF gurus, Ales Soudek:
Alright, that is all; have a good day!