Issue
A customer wants one WorkStation to receive alarms from a specific Automation Server and reject alarms from other Automation Servers.
Product Line
EcoStruxure Building Operation
Environment
- Building Operation Enterprise Server
- Building Operation WorkStation
- Building Operation Automation Servers
Cause
EcoStruxure Building Operation does not provide a native workstation-level configuration that allows a WorkStation to accept alarms from selected Automation Servers while rejecting alarms from others.
Alarm visibility is determined by system configuration, user permissions, and the alarm view being used. Alarm notifications are generated by the system and presented to the logged-in user based on the configured alarm views.
Resolution
Alarm visibility and delivery can be managed using alarm views, user permissions, notification recipients, or enterprise-level segmentation.
Use Separate Alarm Views
Create alarm views that are filtered by Automation Server or server hierarchy.
- Operators can use alarm views that display alarms from specific Automation Servers.
- Different WorkStations can use different alarm views based on operational requirements.
- This controls alarm visibility but does not prevent alarm generation.
Use User Rights and Permissions
Restrict operator access to specific areas of the system database.
- Operators with access limited to specific servers may not see alarms from objects outside their assigned scope.
- This is the closest native method for operator-specific alarm segregation in EcoStruxure Building Operation.
Use Separate Notification Recipients
When alarm delivery is required through email, SMS, or other notification methods:
- Configure separate recipient lists.
- Filter notifications based on alarm source, alarm class, or alarm category.
Use Enterprise-Level Segmentation
For larger systems:
- Assign different operator groups to separate branches of the system hierarchy.
- Use separate Enterprise Servers where complete alarm segregation is required.
Additional Resources
