The Event Tracker logs all repair recommendations made in ExpertALERT-Cloud by your analyst(s). The Event Tracker can be accessed from the Reports section in Program View, Plant View, or Area View, and when you are viewing the Machine Details page for a particular piece of equipment.
How you access the Event Tracker determines the scope of the recommendations that appear:
From Program View, click Event Tracker in Database to see recommendations for all machines across all plants in the database.
From Plant View, click Event Tracker in Plant to see recommendations for machines in the currently selected plant.
From Area View, click Event Tracker in Area to see recommendations for machines in the currently selected area.
From the Machine Details page, the Event Tracker for that machine is located at the bottom of the page on the Event Tracker tab. You can also click Event Tracker for Machine in the Reports section to open the Event Tracker for this machine without all of the other Machine Details information, essentially filling the entire right side of the screen.
The following image shows the Event Tracker for a particular plant:
When an analyst recommends a particular action (for example, bearing replacement, additional monitoring, etc.), a row is added to the Event Tracker table. This enables those viewing the WATCHMAN Reliability Portal to see the recommendations without having to access ExpertALERT.
The Event Tracker provides a two-way communication channel between analysts and the plant's maintenance personnel, closing the information loop in a manner that enhances program effectiveness. Incipient failure events can be tracked from cradle to resolution. Root causes of these failures can be compiled and used to prevent future failures, not just detect them as they develop. This significantly increases the financial return of your reliability program.
Feedback from the plant maintenance team to the analysts impacts the behavior and subsequent recommendations sent to the plant, making the reliability team more precise when making decisions about events that impact plant operation. Bi-directional communication always results in information being transferred more accurately and helps to close the gap created the geographical separation of members of the reliability team.
For some examples showing how the Event Tracker can benefit a PdM program, see Event Tracker Use Cases.
The following table explains each column in the table.
Latest Priority |
The importance of the current recommended action. The priority is identified by color. This color may differ from the Insert Priority color if after the initial report, more information deems the repair more or less important. |
Latest Date |
The date of the data used to make the recommendation. This is the date the data was collected. |
Insert Priority |
The importance of the recommended action when the recommendation was first made. This priority is identified by color. |
Insert Date |
The date the recommended action was first made. |
Machine Name |
The name of the machine for which the recommendation was made. Click the name to see details about this machine (Machine Details page). |
Plant |
The plant in which the machine resides. |
Area |
The area in which the machine resides. |
Recommended Actions |
The action(s) recommended by the analyst. This is taken directly from ExpertALERT. (When the analyst reviews data, recommended actions are entered via the Report Editor in ExpertALERT.) |
Event Description |
A description of the problem that prompted the recommendation (for example, motor bearing wear). |
Work Order Number |
The number of the work order that is associated with the recommendation. Typically, this is the same work order number you would use in your Computerized Maintenance Management System (CMMS). A value appears only if a number was entered in ExpertALERT or if the event is edited via the Portal and a number is entered. |
Work Order Status |
The status of the work order. When a recommendation is first made, it has a status of Open. Edit the event to change the status. The available status options are: Open, Work Order Assigned, Work Order Deferred, Work Order Completed, Closed, Analyst Closed, Work Order Rejected. Each status is described here. |
Status Date |
The date the current work order status was specified. |
Date WO Assigned |
The date a work order number was entered for this recommendation. |
Date WO Completed |
The date a work order is set to the status of Work Order Completed. This is generally done when the recommended action has been performed per the work order. |
Days WO Open |
The number of days a work order has been open. The counter starts when the recommendation is inserted (and automatically set to Open) until it is either Analyst Closed or Closed, regardless of any statuses set in between. |
Findings Confirmed |
Whether the findings of the analyst have been confirmed. Available options are Yes, No, or Partial. |
Root Cause Performed |
The date root cause analysis was performed to confirm the analyst's findings. |
Root Cause Finding |
The root cause of the problem (for example, a lubrication problem). |
Additional Finding |
Any additional information entered about the machine. This could be more information about a root cause, details about the work to be done, etc. The information you enter here will be displayed with this machine when it is included on Machines By Severity reports generated at the database, plant, and area levels. |
Financial Impact |
The net gain resulting from the recommendation. This value is the money saved by catching the problem and repairing it (for example, the daily cost of downtime had the machine failed, minus the cost to repair the problem). |
Attachments |
Access to documents/photos that are attached to this event. |
Tip! By default, only a subset of these fields appear in the table. Right-click the table heading (blue area) to display a list of all available column heads. Select the ones you want to see in the table; clear the ones you don't.
Use the two Filter by drop-down lists at the top of the page to filter the recommendations in the Event Tracker table by repair priority and work order status. Both filters can be used simultaneously.
The Filter by drop-down list on the left lets you filter by the priority of the repair. The following options are available:
All. Does not filter the table. All recommended actions are shown regardless of whether your analyst assigned them a priority of Desirable, Important, or Mandatory.
Mandatory. Filters the table to show only those recommended actions marked Mandatory by your analyst.
>=Important. Filters the table to show recommended action marked Important or Mandatory by your analyst.
The Filter by drop-down on the right lets you filter the table by Work Order Status. In addition to filtering by Work Order Status, there are two "special" options that group work orders based on whether the work order is awaiting action (Pending) or not (Resolved).
The table below describes each Work Order Status as well as shows which ones appear when you filter to Pending or Resolved.
By default, the Event Tracker table filters to Pending.
Groups of |
Individual |
Description |
Pending This shows all events with work orders that are pending an action. |
Open |
When a recommendation is inserted as an event in the Event Tracker it is automatically assigned a status of Open. |
Work Order Assigned |
When a work order number is entered, the work order status automatically updates to Work Order Assigned. |
|
Work Order Deferred |
If a work order number is assigned, but there is no plan to perform the work in the short term, you can change the work order status to Work Order Deferred. For example, if you plan to overhaul a motor, but are going to wait until next outage you can defer the work order. When you get close to the outage, filter the list to Work Order Deferred to see the work you need to complete. |
|
Work Order Completed |
Select this status when the repairs outlined on the work order have been completed. This status is a trigger for someone to review the work and, once the repair is confirmed, mark the event as Closed. |
|
Resolved This shows all events with work orders that do not require further action. |
Closed |
If no further action is needed, set the work order status to Closed. Setting a work order status to Closed means the work has been completed and someone has confirmed it. This is different from Work Order Completed, which means the work has been done, but no one has confirmed it. If your maintenance department does not require confirmation, you may never use the Work Order Completed status and instead mark events Closed as soon as you finish the work. |
Analyst Closed |
If new data is collected for a machine that previously had a recommendation, but the problem no longer exists, the Event Tracker automatically sets the status to Analyst Closed. Important! If the status of an event is set to anything other than Open (for example, you entered a work order which changed the status to Work Order Assigned), the event will NOT automatically be set to Analyst Closed if the recommendation is no longer present in new data. |
|
Work Order Rejected |
This status is used when the recommendation does not require any work or you choose to intentionally ignore it. Even though this status means no work will be done, it is different from marking it Closed, which implies that work has been completed and confirmed. |
Related Topics
Editing an Event in the Event Tracker