Alerts

Introduction to Alerts

Alerts are the portal’s response to triggers that meet specific user-defined criteria. Once a User sets them up, Alerts will be generated automatically whenever an Asset’s reported data satisfies the triggering criteria for the Alert. There are hundreds of events that can trigger Alerts in the portal, and the list of available Alert triggering criteria varies according to the user’s device ecosystem, and the type of data its Assets can report.

Alert Fields

Name: optional field to provide a name for the Alert to differentiate it from others of the same type, will display in all Alert notifications Description: optional field to provide a description of the Alert, will display in the portal notifications Resolution Procedure: Users have the option to include a text field with a resolution procedure that will display with the Alert. The text field is static and will be the same every time that particular Alert triggers. Photo: optional field, allows the user to attach a photo that will display in the portal notifications

Alert Triggers (Type field)

Alert Triggers tell the portal which conditions must be met in order to generate the Alert. Users will select the Triggering condition for each Alert as part of the setup process from the drop-down menu in the Type field.

There is an extensive list of hundreds of potential Alert Triggers, which will change dynamically for each user based on the types of devices in their ecosystem. Many of them are triggered manually by the Asset operator (by pressing a button, sending a message, or performing some other action), and others are triggered by the portal recognizing certain parameters about a regular position reporting event. The latter type of events occur regularly, and are typically tied to other features and objects like Places, Geofences, Chats, and Messages.

Some of the most common Alert Events are listed below. Each ecosystem will have a different list of Alert triggering conditions, as the list will be based on the type of data that can be sent by devices in the ecosystem.

• Alarm/emergency
  This Alert triggers whenever an Asset reports an emergency event, and is typically triggered manually by the Asset operator directly from the device. Emergency Alerts also trigger special notification popovers in the portal interface.

• Check in/OK
  Many devices come with a manual check in button that allows operators to send manual Check-ins to the portal. Alerts can be configured to notify users whenever an Asset reports one of these Check-in events.

• Distance Traveled
  For Assets that support Odometer reporting, a Distance Traveled Alert can be configured whenever the Asset’s Odometer meets or exceeds the threshold. These Alerts are often used to manage maintenance needs, but can also be used to warn managers and drivers of over-use.

• Enter Fence
  Tied to Geofences, the Enter Fence Alert will be triggered whenever its Asset(s) enter the bounds of a specified Geofence.

• Exit Fence
  Tied to Geofences, the Exit Fence Alert will be triggered whenever its Asset(s) leave the bounds of a specified Geofence.

• Far from Asset
  Tied to other Asset(s), the Far from Asset Alert will be triggered whenever the Asset(s) selected in the Rules section are a specified distance or greater from the reference Asset.

• Geofence Dwell
  Tied to Geofences, the Geofence Dwell Alert will be triggered whenever its Asset(s) remain within the bounds of a specified Geofence for an indicated period of time.

• Harsh Acceleration
  For Assets that support detection and reporting of operating conditions, Alerts can be set to trigger when those Assets report harsh behavior like Acceleration, Braking, and Turning.

• Harsh Braking
  For Assets that support detection and reporting of operating conditions, Alerts can be set to trigger when those Assets report harsh behavior like Acceleration, Braking, and Turning.

• Harsh Turning
  For Assets that support detection and reporting of operating conditions, Alerts can be set to trigger when those Assets report harsh behavior like Acceleration, Braking, and Turning.

• Heartbeat
  While the Heartbeat Alert can be tied to a biometric sensor that reports the operator’s heartbeat, the Alert can be triggered for any Asset that fails to report to the portal for a specified amount of time.

• Help
  Some Assets send status messages and have a button or protocol for messages to request help. This type of Alert will monitor for those assets that can send help messages.

• Help Cancel
  Some Assets send status messages and have a button or protocol for messages to request help. This type of Alert will monitor for those assets that cancel previously sent help messages.

• I/O
  I/O Alerts trigger when an Asset reports an Input value as part of its I/O map. To configure this type of Alert, use the I/O Mapping Template and filters in the Rules section of the Add Alert form.

• Low Battery
  As the name implies, Low Battery Alerts can be configured to notify portal users when the Asset reports having low charge remaining in its internal battery.

• Movement
  Whether reported as moving or reporting a speed greater than 2.24 m/s, Movement Alerts will trigger whenever an Asset’s position report meets one of the aforementioned conditions. Movement Alerts are unique, in that they will also notify users when the Asset is no longer moving.

• Near Asset
  Tied to other Asset(s), the Near Asset Alert will be triggered whenever the Asset(s) selected in the Rules section are a specified distance or less from the reference Asset.

• On Backup Power
  For devices with multiple power sources, Alerts can be triggered to notify portal users when the Backup Power source is in use.

• On Main Power
  For devices with multiple power sources, Alerts can be triggered to notify portal users when the Backup Power source is in use.

• Position
  The Position Alert triggers whenever the Asset tied to it reports a position.

• Powered Off
  As the name implies, this Alert triggers whenever an Asset has reported that it has powered off.

• Powered On
  As the name implies, this Alert triggers whenever an Asset has reported that it has powered on.

• Raw Data
  The Raw Data Alert is triggered whenever the Asset reports a non-standard message with Raw Data or otherwise unparsed information.

• Speed
  Speed Alerts are triggered whenever an Asset reports a speed in excess of a defined limit.

• Started
  The Started Alert can be configured to trigger whenever an Asset has reported a startup, whether of itself or of a defined action, like a trip log,operating cycle, or movement.

• Stationary Dwell
  The Stationary Dwell Alert will be triggered when the Asset reports stationary positions for a specified Dwell Time in the same location.

• Stopped
  The Stop Alert can be configured to trigger whenever an Asset has reported a stop, whether of itself or of a defined action, like a trip log or operating cycle.

• Text Message
  Assets can send text messages to the portal (they appear in the Chats tab for the Asset) and this Alert will allow the portal to notify the user with more than just an in-app notification.

• Text Message Status Update
  Assets that can send and receive text messages also update the status of those messages (for example: sent, delivered, read) and those updates can trigger alerts in the portal to keep users updated with regard to message status.

Alert Rules

When creating an Alert, users have the ability to control the way that Alert gets triggered in a number of ways. Once a type/triggering condition has been selected, users can navigate to the Rules section of the Add Alert form to specify additional Rules and filters to reduce redundant or insignificant notifications.

Rules: Alert applies to gives users the ability to say that only Events from specific Assets or Asset Groups can trigger the Alert. The default is to apply the Alert to all Assets, but if users limit by selection, any Asset(s) or Group(s) with a green check mark next to them will be able to trigger the Alert.

Rules: Exclude from Alert gives users the ability to further refine an “Applies to” Rule, or to create “all except” style rules to reduce the number of Assets and Groups that can trigger the Alert.

Alert Filters

Each filter is defined in the portal itself, and will apply after the limiting conditions and other rules have applied. These filters include date/time related qualifiers, reported value qualifiers, and proximity qualifiers that typically leverage other features like Geofences.

For details about Alert Filters, see the Filters article.

Alert Acknowledgement

Requires Acknowledgement yes or no options, if no, users will have no further options. If yes, users will see the following fields become available.

Priority When creating an Alert, the section for Acknowledgement gives users control of the Alert’s priority level, which will change the display order of Alert popups in the interface, according to their importance as designated by priority level setting.

Color set the color for the Alert’s display notifications in the list panel. This helps differentiate different types of Alerts configured for the same device.

Pop up Alert in Portal if the User wants the portal to produce a pop-over box notification that will display on the map interface, select yes.

Rename Acknowledge Buttons Alerts can be configured to have two different Acknowledgement buttons with customizable text, which users will click to dismiss the Alert. Each Acknowledgement button can be configured as a triggering event for sending communications to stakeholders outside the portal.

When dismissing Acknowledgements in the interface, Users will have the option to include notes in a text field that will be stored with the Acknowledgement.

Notifications - Recipients

The Notifications - Recipients component of Alerts lets users determine which Contacts will receive the Alert if it is sent outside the portal, and under which conditions those Contacts receive Alerts.

Contacts

This section displays checkboxes next to the names of Contacts in the portal, and allows users to select the ones that will receive the notifications for each event that occurs.

Alert Triggered Contacts with a green check next to them will receive a notification when the Alert is triggered

Acknowledgement notification options will display if Acknowledgement is turned on for the Alert.

Ack 1 This header will change when you rename the Acknowledge buttons in the Acknowledgement section. Contacts with a green check next to them will receive a notification when the Alert is Acknowledged using the first of the two options.

Ack 2 This header will change when you rename the Acknowledge buttons in the Acknowledgement section. Contacts with a green check next to them will receive a notification when the Alert is Acknowledged using the second of the two options.

Send Notifications until Alert is acknowledged This yes/no toggle gives the portal the ability to send repeat notifications to the contacts that will receive them until the Alert has been Acknowledged.

Notification interval If the above yes/no is set to yes, Users will need to specify the frequency of re-messaging that will occur. Users can set any number of minutes, hours, or days as the interval.

Hide Alert Notices on map This yes/no toggle determines whether Alerts will be visible on the map.

Viewing Alerts

Alerts take the form of in-app display notifications, in-app pop-ups, and automated messages. They can be viewed as visual notifications in the portal or as text.

Finding Alerts

Alerts will display in one of the two formats listed below (In-app or Text) when they are triggered. Navigating to Alerts in the application is as easy as opening any map interface. Alternatively, users can navigate to the Manage Module and open the Alerts option in the List Panel to view and manage all of the Alert confgurations in the portal.

Managing Alerts

Users can view all of the Alerts they have set up as a list in the Manage Module. In the Manage Module display, users will see a list of Alerts and their configurations, along with a few buttons that allow them to quickly manage them from the interface. There are Edit, Delete, and Add buttons throughout the list and on the top of the interface.

In-app viewing

List Panel and Details Panel Users can find a list of Alerts by clicking the cog icon next to the name of any Asset, then selecting the Alerts tab. Alternatively, users can click the multicog icon next to any Group name to view all Alerts for the selected Group in the Alerts Tab. Any Asset or Group in the List Panel with an orange notification indicator has new Alerts to be reviewed.

Pop-ups Some Alerts can be set up to display a pop-up message over the Map interface when they are triggered. These Alerts will still display in the List Panel if the user chooses to view them there, but will also generate a notification box on the right of the Map interface until the User closes it.

Text delivery

_SMS and Email Messages__ Alerts can also be configured to send messages to any Contact in the portal. The options to send Alerts to Contacts will deliver the Alert message in text form to the Contact chosen by the User, according to the settings selected (Alert triggered, Alert no longer triggered, Acknowledged, Alt. Acknowledged).

Using Alerts

Alerts help managers prioritize Asset data events in large ecosystems, and serve to notify portal users of potential emergencies or problems with Assets in the field. The Alert system was built to make sure that no relevant asset data event goes unnoticed, especially those that need immediate attention. Because so many satellite applications involve safety assurance and emergency support, systems that provide automated, programmable Alerts to watch for those events become invaluable to asset managers.

Using the Acknowledgement feature, for example, is one way an organization can manage their emergency protocols with automated messages and rapid response. The Acknowledgement buttons are completely customizable, and typically are configured to be some kind of bimodal options like “needs further attention” and “resolved” in order to help stakeholders keep track of the responses. A user clicking a “needs further attention” Acknowledgement button can be configured to trigger an email to be sent to the user’s supervisor.