The current way of setting up alerts is labour intensive if multiple alert levels are required for individual sensors. Instead of having an alert entry set up for each alert level (low, moderate, high, critical), it would be significantly less work if all alert priority levels could be set-up in one alert entry for single or multiple sensors. Each level would have it's own set of rules although, at least for my use case, actions and sharing could be shared for all alert priorities.

The current system as-is could be improved by decoupling the alert status of multiple sensors from each other. Currently if multiple sensors are selected as part of an alert entry, if one sensor triggers the alert status, all sensors in the group are triggered. An option called something like "Sensors trigger independently" would be helpful. As it stands, if I create a rule that is the same for 20 sensors, if one sensor exceeds the threshold, all sensors are shown with that alert status.

To illustrate why this is labour intensive to work with, take this example from my current project:

I have 24 sensors, with three groups of sensors and each sensor in each group shares the same moderate and high alert levels. Group of 4, group of 16 and group of 4. Under the current system, I need to configure 48 alert entries in order to have all sensors trigger individually. If the sensors could be triggered individually, I would need to create 6 alert entries, 2 alert level x 3 groups.

Another idea to help with alert setup for projects with individual sensors would be to allow for the alerts to be configured via a config file that could be uploaded to the platform. This could be a specifically formatted CSV file that could be created by the user and imported. Vista Data Vision has this functionality and it makes configuring multiple sensors much faster, especially if each discrete sensor has unique trigger levels.