Alerts
Alert Triggers
Feature Summary
The Alert Triggers feature in GSatTrack empowers users to define and customize conditions that, when met, trigger alerts. This proactive monitoring system ensures that operators are promptly notified of critical events or deviations from expected conditions. By allowing users to set up personalized alert triggers, GSatTrack enhances real-time awareness, enabling users to take immediate action to address issues or optimize operational efficiency.
How to Use
Note!
Alert triggers are chosen when adding a new alert. See the “Add Alert” page for more information.
Additional Information
Alert Triggers
Below is a list of the different types of Alert Triggers users can choose from:
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 overuse.
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 a 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.