Use Case
In large-scale sites with frequent activity, relying on a single MVS/MASS client configured with the pan on alarm feature can become inefficient. While this setting is designed to automatically zoom in on the location of an alarm event, it may result in excessive map movement when multiple alarms occur in rapid succession across different remote areas. This constant panning can be disorienting and make it difficult for operators to focus on critical events.
Conversely, disabling the pan on alarm feature results in a static, wide-area view. While this prevents erratic movement, it significantly reduces the level of detail available—making it challenging to accurately assess individual tracks or alarms.
An optimal solution would balance situational awareness with contextual detail, minimizing unnecessary map motion while still providing sufficient zoom for event verification.
Recommendation
Use “Boundary lock” in combination with pan on alarm as described below:
- Divide your site into several separate “boundaries”. In this figure I used the blue, orange and yellow rectangles to show the boundaries:
2. Define a sperate user per boundary. Eg. recorder1, recorder2, recorder3, etc…
3. Login with each user. Move the map so that the view matches the boundary you want:
4. Open the user section in the settings menu and click on the boundary lock:
5. Make sure Pan on alarm is enabled in the configuration screen:
6. Repeat these steps for all the boundaries.
Now each user will only Pan the view to alarms inside the boundary defined to him – thus reducing the number of simultaneous event handled by a single view.