Skip to main content

Alerts App

Alerts and Faults​

This is where alert configurations are created and managed. Alerts can be set to notify who you would like when they have triggered, and how they will affect the color of the asset's map pin.

Alert Dashboard​

The alerts dashboard shows you the amount of alerts that you have active, and lets you action them.

  • The donut charts indicate how many low, medium, and high priority alerts are active.
  • Below the charts will be a table with the active alerts.
  • Clicking the export to CSV button will export what you are seeing on the table to a CSV file.
  • If you click on the asset name, you will be taken to that asset's detail's alerts tab.
  • If an asset enters a faulting state and has an active diagnostic trouble code it will also appear on the alert dashboard with a medium priority automatically assigned to it.
  • Clicking the notes icon opens a modal window where you can view notes that have been added to that alert, and can add your own notes. If there is an exclamation mark ('!') on the notes icon, that indicates that a note has been added.
  • The acknowledge button is intended for you to indicate that you are aware of that alert happening. When you have clicked on acknowledge, the button will change to say clear.
  • When you click the clear button, that alert will be removed from the dashboard.

View Historical Alerts​

This page lists all alerts which have been cleared or have returned to their normal state.

  • When you first land on this page, to see the historical alerts you must first enter in your search criteria. You can search for historical alerts by date range, alert status, alert priority or select specific assets. Clicking the search button will search for alerts based on the options that you chose.
  • The date range allows you to go back up to 13 months, but within a range of 31 days.
  • Clicking on a row in the table will take you to the details of that alert instance.

Historical Alert Details​

This page shows the details of an instance of an alert. It displays a chronology of when the alert became active, who notified it and when.

Alert Configurations​

The Alert Configuration page lists the alert configurations that have been created. Along with the name of the configuration, it also lists how many assets are applied to that configuration, and how many triggers the configuration has. Clicking anywhere in the row of a configuration will take you to the details of that alert configuration.

Alert Configuration Details​

This page displays the details of an alert configuration and allows you to edit it.

  • The top panel lists the name of the alert configuration and the email addresses that are notified (if any were entered) when an asset assigned to the alert configuration triggers any of the conditions. Clicking the edit button allows you to edit the name of the alert configuration, or the notification email addresses.
  • Clicking the delete button will open a modal window to confirm the deletion of the alert configuration.
  • Assets tab
    • This lists the assets that have been assigned to this alert configuration. If any of the trigger conditions are met on any of these assets, they will enter an alerting state.
    • Clicking the add asset button opens a modal window that allows you to select multiple assets.
    • To remove an asset from the alert configuration, click the checkbox beside the name of the asset and then press the remove selected button.
    • An alert configuration must contain at least one asset.
  • Triggers tab
    • The triggers tab lists the triggers that have been added to the alert configuration. These are the conditions that the assets must meet to enter an alerting state.
    • To add a new trigger to the configuration, click the add trigger button.
    • To edit an existing trigger, click the pencil icon.
    • To delete an existing trigger, click the red trash can icon.
    • While you are adding or editing an existing trigger, the add, edit and delete buttons for other triggers are disabled. You must first save or cancel your changes to the trigger you are adding or editing.
    • An alert configuration must contain at least one trigger.

Create Alert Configuration​

This page is a form to create a new alert configuration. Alert configurations can have many triggers assigned to them. When an asset that is assigned to the alert configuration has any of the trigger conditions happen, it will enter an alerting state.

  • The name field is what you would like to call the alert. This name will appear when you receive a notification that one of the triggers occurred for the configuration and it will be shown on the alert dashboard.

  • The notification field allows you to enter up to 10 email addresses that will receive an email when any of the trigger conditions are met for the assets that are assigned to the alert configuration.

  • The pick asset button will open a modal window that lets you select assets that will be assigned to this new alert configuration. An alert configuration must have at least one asset assigned to it.

  • Triggers

    • Triggers can cause the assets assigned to the alert configuration to enter into an alerting state.

    • The data point is what you set the condition on. If the data point of an asset meets the condition of what you set then it will trigger the alert.

    • The conditions are what will cause the assets to trigger into an alert state based on the data point chosen. For example, you may choose to have assets trigger an alert if the Battery voltage falls below a certain value. The amount of time is used to determine when it is an active alert which will add the alert to the dashboard and send a notification email. There are several operators that you can use for the condition:

      • = Equals

      • != Does not equal

      • < Less than

      • "> Greater than

      • ">= Greater than or equal to

    • Priority determines what color the map pin will change to when the trigger occurs on an asset. If it is a low priority, the pin will remain green. If it is a medium priority, the pin will be yellow. If it is a high priority, it will be red. If an asset has multiple alert triggers occur, the map pin will be the highest priority color.

    • Auto clear can be set so that if that asset returns back to its normal state on its own it will automatically be removed from the alert dashboard without having to acknowledge and clear it off the dashboard. You can choose to have it happen immediately after it returns to its normal state, or 24 hours after it returns.

    • You can select to be notified when the asset returns to its normal state.

    • After filling out the trigger information, click on the save icon. You can add more triggers by clicking the add trigger button. This will add a new line where you are able to set the trigger conditions and settings. You can click the red cancel button to cancel adding a new trigger.

    • You can edit a trigger that you have added by clicking the pencil icon.

    • You can delete a trigger by clicking the red trash can icon.

    • An alert configuration must contain at least one trigger.

  • When you have finished creating your alert configuration, clicking the create button will take you to the details page of the configuration you just setup.

Alert Configuration Examples​

Alerts are powerful tools to help you maintain operational fleet awareness. Understanding how to set up them up correctly is an important part of fleet management. The alerts depend on the type of data you receive as part of your specific solution:

  • Periodic data -- this is the operational data snapshot that's sent on a specific schedule while the equipment is operating. Typically, this is every 15 minutes when using cellular communication, however this frequency could be unique based on your specific solution. Engine Run Hours, RPM and Coolant Temperature are examples of periodic data.
  • Change-of-state data -- these are status changes that are captured and transmitted to Industrility® immediately upon occurrence.

Examples of change-of-state data could include engine status (on/off), a low fuel alarm becoming active based on a digital switch, J1939 engine faults, etc.

Industrility's alert configuration delay workflows behave differently depending on whether the incoming data is periodic data or change-of-state data. The delay workflow defines the period of time after the alert has become active, before any alert notification is dispatched to email and/or text message.

Implementing a delay on the notification can prevent issues related to excessive volumes of notification emails/texts in cases where the alert condition is quickly toggling between active and inactive conditions. These toggling events can be caused by things like loose input wiring, analog values hovering around defined thresholds or J1939 fault toggling, as examples. In addition, an incoming periodic data value may want to be evaluated a second time before dispatching notifications, to ensure the condition continues to be true. Consider the behavior of the events you select for alert configurations.

Here are some examples of appropriate configurations:

Low-fuel alert based on a Fuel Level value that's dispatched as periodic data
The alert would advise personnel to fill the fuel tank.

  • If Fuel level 20% for 0 minutes, create a high priority alert that auto clears after 24 hours.
  • The remote monitoring hardware has dispatched a periodic data value for a fuel level of 19%. This is below the 20% threshold defined in the alert configuration.
  • The alert will then appear on the alerts screen.
  • An alert notification is dispatched immediately based on the configuration indicating a zero- minute delay on the notification. In this example, there's no need to wait for any additional data since the fuel level is at the threshold that indicates a need for a fuel fill.

Low-temperature alert based on a Fluid Temp value that's dispatched as periodic data
The alert could signify the need to dispatch a technician to troubleshoot equipment when parameters fall out of line.

  • If Fluid Temp < 10° C (50° F) for 20 minutes, create a medium priority alert that auto clears after 24 hours.
  • A Fluid Temp value of 9° C (49° F) has been dispatched as periodic data, which is below the 10° C (50° F) threshold for an alert.
  • There may be a desire to confirm that this issue is persisting before displaying the alert and dispatching the technician.
  • Because this is a periodic data value, an updated value will not arrive for another 15 minutes (standard Periodic Data frequency), therefore a delay of at least 15 minutes is required to ensure a subsequent Fluid Temp value is received and evaluated against the alert configuration to determine if the alert is still valid.
  • If the Fluid Temp value increased above 10° C (50° F) in the next report of periodic data, no alert is displayed on the alerts screen, and no notification would be dispatched, reducing needless disruption to the tech's workload.
  • If the subsequent periodic data report indicated a Fluid Temp of 8° C (47° F), the original alert is still valid, therefore the alert will then be displayed on the alerts screen and notifications would be dispatched five minutes after the second round of periodic data (15 minute periodic data interval + 5 minutes = 20 minutes).

A High Pressure alert, based on a pressure switch with a pre-defined threshold
In this case, the condition is either active (alarm) or inactive (clear) depending on switch status. This implies a change of state. A message that would be dispatched immediately upon the switch's status change.

  • If High Pressure Alarm = active for 5 minutes, create a high priority alert that auto clears after 24 hours.
  • There's a risk of receiving multiple alert notifications if the pressure value is hovering around the switch's pre-defined threshold, because as the switch toggles the active and inactive status, each of those changes is sent to the ONE i3 platform.
  • If no delay is configured, all toggled alerts would display on the alerts screen, with each change also resulting in a notification email. Therefore, it's important that you implement a short delay duration to validate that the condition is true before displaying the alert and dispatching notifications.
  • When the active condition is received in the ONE i3 platform, the delay timer initiates. If a subsequent inactive change-of-state message is received during the delay interval, the alert display and the related notification stop.
  • If the condition continues to be true after the delay interval, the alert displays and notifications will dispatch.

Please engage your support channels for any additional support required to establish alert configurations effectively.