When assigning permissions to station users, keep in mind that all alarm ack (acknowledgement) rights in NiagaraAX are determined only by a user’s permissions on AlarmClass components (and not on the source points with alarm extensions, which “generate” alarms). Alarm classes are under a station’s AlarmService. As needed, you link alarm classes to alarm recipients, to define alarm routing in the station.
Specifically, a user requires write permissions on any alarm class in order to acknowledge alarms or events routed by it. Minimum permissions vary depending if AX-3.8 or AX-3.7, as follows:
In AX-3.8, users require operator write (rw) permissions on the alarm class, in order to either acknowledge the alarm, or add “notes” to it. Note this is a change starting in AX-3.8—see below.
In AX-3.7 and earlier releases, users require admin write (RW) permissions on the alarm class, in order to acknowledge the alarm, or add “notes” to it.
This topic is also mentioned because it is a different alarm ack scheme than was used in the older Niagara (R2) systems. Note that in a scenario where many “user-divided” ack rights are needed, you may need to create additional alarm class objects, assigning them to different security categories.
For more details about alarming in general, and also AlarmClass components in particular, see About Alarms, and About alarm class.
Copyright © 2000-2014 Tridium Inc. All rights reserved.