Alerts

Alerts are special messages from the portal to portal users that are tied to specific events and other objects in the ecosystem like Geofences and Assets. These messages will always be delivered by the portal to the user, but the trigger condition and method of delivery may vary.

Delivery

Once the triggering condition has been met, Alerts will notify any portal users it has been set up to notify that the event has occurred. The following are the delivery methods for Alerts:

In-app notification(s): when in Live Mode and History Mode, a list of Assets appears in the List Panel, and each has a set of notification indicators. Assets that have Alerts tied to them will appear with an orange box lit in that notification area.

Text Message (SMS): Alerts can be configured to send text messages to any phone number that has been set up as a Contact in the portal. To send text messages as part of an Alert notification, click the box next to the phone number of the contact under the event type (Alert Triggered, Alert no Longer Triggered, Acknowledge, Alt. Acknowledge) in the Notifications portion of the Add Alert form.

Email: Alerts can be configured to send email messages to any email address that has been set up as a Contact in the portal. To send emails as part of an Alert notification, click the box next to the email address of the contact under the event type (Alert Triggered, Alert no Longer Triggered, Acknowledge, Alt. Acknowledge) in the Notifications portion of the Add Alert form.

Emergency Alert Pop-up: when an Asset triggers an emergency notification to the portal, the Emergency Alert will pop up on the active view, and, if the user has enabled it, a sound will play to notify the user of the hightened need for attention.

Viewing Alerts - In Portal

Each Alert will be tied to an Asset, and will display in the List Panel notification area as well as the Details Panel Alerts tab for that Asset. Users can also view Alerts at the Group level, which will display all Alerts from all Assets in the order in which they were received. Any Asset or Group in the List Panel with an orange notification indicator has new Alerts to be reviewed.

Alert Types and Triggering Conditions

Alert triggering conditions are all events that occur with Assets in the Portal. 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.

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.