There are two ways to create an Event:
From checking an Insight (read this article for more information).
Adding it manually on the “Reliability” page.
Create an Event Manually
You can manually create events to log any failure or occurrence throughout your asset’s lifecycle, regardless of whether it was detected by the Smart Trac sensor. This makes events a powerful tool for managing asset failures.
Adding an Event
On the “Reliability” tab, click on “Add”.
First, you must select the Event Type. We will go into detail about completing each type further on.
Then, add files and a description, if desired. We recommend making the Event as detailed and complete as possible, so be sure to fill in the description with as much detail as possible.
Select the Location or Asset of the Event.
Select the failure and component, then choose the action, cause, and effect of the failure. To add more than one failure, click “+Add” in the top right corner of the section.
Event Types when selecting “Problem resolved”
Total Failure, Potential Failure, Functional Failure
Failure Event Period: The period (start and end date and time) when the failure occurred.
Downtime: Define the period during which the asset was offline when it should have been operational.
Effective Repair Time: Enter the time maintenance personnel spent repairing the equipment;
Savings:
Avoided Downtime: how long the asset would’ve been down if the issue hadn’t been anticipated or quickly resolved;
Avoided Repair Time: maintenance time saved through a preventive or more efficient corrective action.
Insights: link any related Insights to this Event, if available;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Unplanned Operation
Unplanned Operation Event Period: The period (start and end date and time) when the Event occurred.
Insights: Link any related Insights to this Event, if they exist;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Event Types when selecting “Unresolved Problem”
Important note: When an Event is classified as “unresolved”, the associated asset will enter a state of Attention.
Total Failure, Potential Failure, Functional Failure
Failure Event Period: Determine the date and time when the Event began. The adjacent field for the end date and time will appear as “Until Now”, since the problem has not been resolved. Under these conditions, this field will be locked for editing.
Insights: Link any related Insights to this Event, if they exist;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Unplanned Operation
Unplanned Operation Event Period: Determine the date and time when the Event began. The adjacent field for the end date and time will appear as “Until Now”, since the problem has not been resolved. Under these conditions, this field will be locked for editing.
Insights: Link any related Insights to this Event, if they exist;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Other Event Types
Planned and Unplanned Downtime
Cause: The reason why the equipment stopped.
Event Stop Period: The period (start and end date and time) when the stop occurred.
Downtime: Define the period the asset was offline when it should have been operational.
Repair Time: Enter the time spent repairing the equipment.
Savings:
Avoided Downtime: how long the asset would’ve been down if the issue hadn’t been anticipated or quickly resolved;
Avoided Repair Time: maintenance time saved through a preventive or more efficient corrective action.
Insights: link any related Insights to this Event, if available;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Process Adjustment
Cause: The reason for the process adjustment or sensor change.
Event Period: The period (start and end date and time) when the Event occurred.
Insights: Link any related Insights to this Event, if they exist;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Energy Event Types
Energy Restoration
Energy Restoration Event Period: The period (start and end date and time) when the restoration occurred.
Downtime: Define the period the asset was offline when it should have been operational.
Repair Time: Enter the time spent repairing the equipment.
Savings:
Avoided Downtime: how long the asset would’ve been down if the issue hadn’t been anticipated or quickly resolved;
Avoided Repair Time: maintenance time saved through a preventive or more efficient corrective action.
Insights: link any related Insights to this Event, if available;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Power Outage when selecting “Problem resolved”
Power Outage Event Period: The period (start and end date and time) when the power outage occurred.
Downtime: Define the period the asset was offline when it should have been operational.
Repair Time: Enter the time spent repairing the equipment.
Savings:
Avoided Downtime: how long the asset would’ve been down if the issue hadn’t been anticipated or quickly resolved;
Avoided Repair Time: maintenance time saved through a preventive or more efficient corrective action.
Insights: link any related Insights to this Event, if available;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Power Outage when selecting “Unresolved Problem”
Power Outage Event Period: Determine the date and time when the Event began. The adjacent field for the end date and time will appear as “Ongoing”, since the problem has not been resolved. Under these conditions, this field will be locked for editing.
Insights: Link any related Insights to this Event, if they exist;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
Power Supply Issue
Cause: The reason for the problem.
Power Supply Issue Event Period: The period (start and end date and time) when the Event occurred.
Insights: Link any related Insights to this Event, if they exist;
Add Work Orders or Requests (for customers using TracOS™): any Work Order or Request related to this failure.
After filling out all the information, save the Event by clicking the “Save” button at the bottom of the screen.
Open Events
Events listed as “Open” are those marked as unresolved.
Completed Events
Events in the “Done” tab are those that have been resolved.
Important note: The information included in Events must also be submitted when resolving an Event that was previously listed as unresolved. As mentioned earlier, the required information varies depending on the nature of the Event.
Event Viewing Modes
There are two ways to view an Event:
Panel Mode
In this mode, you can view each Event individually, both Open and Completed, with all its information.
Table Mode
This type of view provides an objective organization, ideal for quickly viewing key Event details, listing them for a straightforward analysis.
Generate an Event Report
Within the Event itself, you can generate a complete report about it, including all its details, which simplifies audit processes, for example. To do this, simply click on the printer icon at the top of the Event.
Select the information you want to include in the report.
Click “Print”. The report will be automatically generated, and you can print it or save it as a PDF.