cvillanua

Tasks check list for maintenance purposes

Blog Post created by cvillanua Employee on Dec 21, 2018

At the current time we are having many customers including event frames in order to be alerted when an asset needs maintenance or even if their data is out of tune.

I have been asked several times in the last month for the possibility of having a tracking of the different tasks needed to perform by a user in order to fulfill a maintenance or a data quality test. The idea of this post is to share a solution that we found that could be suitable for this use cases.

 

USE CASE

The user would like to be notified when an event occurs by email and be able to access to a display to mark different maintenance tasks as checked. In this example the maintenance will be related with a set of pumps of a plant.

 

SOLUTION

When a maintenance is needed for a pump, an Event Frame will be triggered and a PI Notification will be sent. The customer will access to a PI Vision display in order to follow the different needed maintenance tasks and marking them as "Checked" or "Not Checked". BE AWARE THAT THIS SOLUTION INCLUDES AN EXTENSIBILITY SYMBOL THAT WILL NEED TO BE INSTALLED, MAINTAINED AND CONFIGURED BY THE CUSTOMER.

 

  • User receives an email with a task needing to be performed

  • User access to the display and sees the needed tasks to be performed in an event frame table. The template will allow you to create the display for one pump and reuse it for all the pumps from the station
    • Check bearing and lubricant condition
    • Check overall pump vibration
    • Check pump discharge pressure
    • Check shaft seal condition
    • Action Needed ( we will see here if there is a need of maintenance "Needs maintenance")

  • The user will be now performing the tasks and using the drop down list to select if the task was checked or not.

  • Once the maintenance is performed, the user will be marking all the list as checked. Confirm that the that maintenance is performed marking "No maintenance needed".
  • To record all this information the user will click the update button and click the Acknowledged button to record the user that performed the maintenance.

  • To verify that the information was correctly sent the system, the user will receive an email mentioning the closure of the event.

CONFIGURATION

Architecture used

Example with a maintenance Pump checklist when maintenance needed.

Configuration in AF

  • Creation of Enumeration Set to show the different check list options.

  • Creation of the checklist and tags using in PI AF pump template. There is a main attribute that will be the one triggering the events, this is called "Action Needed". In our case this attribute is 0 ("No maintenance needed") or 1 ("Needs Maintenance")

  • The rest of the attributes for the maintenance list are the different tasks needed to be checked.

  • The event frame template will be configure to show the action that is needed to be performed and able to be acknowledge.

  • The event frame trigger will be if action needed is different from zero.

  • There is another analysis to reset the status of the "Checked" values to "Not Checked"

  • A notification will be configure to be sent when there is an action of maintenance needed. This notification will be sent when the previous event frame configured is triggered.

  • After all the configuration a check in will be needed to create the points related with the check attributes that were created.

Configuration PI VISION

  • The custom symbol of manual data entry is needed for this display. There is more information about this symbol in the following link from GitHub from our Engineer Anna Perry

Display creation

  • Select the different attributes to be used in the check list.

  • Drag and drop this list selecting the custom manual data entry symbol and change the colors and configuration as needed.

  • Add the Event frame table to see if there are maintenances requests in queue. This can be done with the "Create Events Table" button.

 

OUTPUT

This set up will allow you to have a tracking of the different maintenances and when those were performed by the operators. Later on will be able to check the duration of the maintenance periods and the time of reaction to make those maintenance.

Please drop a comment if you have any questions or would like any clarification.

Outcomes