Additional options for Grouping Alarms/Events

The current restriction to grouping events by Area or Alarm Point does not provide the flexibility a PSIM could offer in handling larger volumes of alarms at a single location.

With the current implementation, Operators watching the Processing queue need to either deal with many potentially associated alarms individually when grouping by Alarm Point (for example from a cleaning crew moving through a floor after hours), or risk missing new alarms associated with the Area but not in the vicinity of the original alarm when grouping by Area (for example, construction work is causing a lot of alarms on one floor, causing a forced door appearing on another floor in the same building to blend in and be missed).

Several suggestions to provide more flexibility in this area:

• Allow grouping by Floor for those who are utilizing the mapping component of SureView Ops
• Allow Grouping by proximity for those who are utilizing the mapping function
• In coordination with the two above, allow grouping by time (for example, it was within x feet and occurred within y seconds or minutes from the initial alarm)
• Allow manual grouping by the operators. For example if an Operator is working an incident and sees another alarm go off (or if another operator opens the new alarm and confirms with their colleague it's related), they should be able to associate the two alarms into one event. This functionality would also support the collaborative nature of the platform.

On top of the above and perhaps related to a previous feature request, let events be run individually, but associated with one another from a reporting perspective. In the current state, if alarms are grouped by Alarm Point, and someone forces a door open, moves onto the floor, forces another, breaks a window, then leaves the stairwell propped on their way out, these would all be separate events. When reviewing the incident, each SitRep would need to be exported, likely recompiled manually, and shared to investigators/leadership, etc. as a single compiled view outside the products produced natively in SureView. If incidents cannot be, or by their nature should not be integrated into one event, the multiple activities should be able to be tagged somehow to create a single report of the entire incident.