Alerts

Alerts are the portal’s response to events that meet specific user-defined criteria. Alerts are 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.

Viewing Alerts

Alerts take the form of in-app display notifications, in-app pop-ups, and automated messages. 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.

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.

Alerts can also be configured to send messages to any Contact in the portal.

Alert Features

Alert features include control elements, display options, and behavior settings that give Users complete control of their Alert system setup. The system defaults to basic configurations, and allows full customization and detailing for power Users.

Resolution Procedure

As part of the main attributes section of the Alert setup, 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.

Alert Acknowledgement

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.

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.

Alert Rules and Filters

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.

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.

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.