I have 8 control modules (Bursting discs) that belong to an area called "Ammonia" we are having problems where the operator is acknowledging them and not doing anything about them, what I want to happen is that the alarm still indicates on the graphic and the sounder starts but they are not able to acknowledge them, I want the shift managers to do the acknowledging.
My initial thought was to move the 8 signals to an area called "shift managers" which works fine the shift managers can hear the sounder and can acknowledge the alarm, but my only issue is that the operators get the visible indication on the graphic but they don't get the sounder alarm is there another way I can do this of fix the sounder.
In reply to GaryL:
In reply to JackC:
I've never tried using the userlock01 as a visibility on the alarm banner. I think it will cause too much of a headache, especially if any other script controls the banner. In your situation, if you don't want Operators to have access to the alarms, I would create maybe something like a Operator Jr versus Operator Sr. where the Alarm key will be removed from the Operate Jr. Or just remove it from Operate entirely if only Shift Managers are managing the alarms.
The bigger issue is what are the operators acknowledging alarms without taking any actions? Or could those actually be nuisance alarms which can be prevented by having conditionals programmed into the logic to disable the alarm?
If you go that route, I recommend also propagating it onto the faceplates so that the Operators/Shift managers know which condition is preventing the alarm from coming on. See an example I attached below.
JackC
Thanks for this, I have had a change of mind I have created a new faceplate by copying the original and then using this DVSYS.THISUSER/USER_CAN.F_CV[AREA_A][USERLOCK01] to hide (VIA) visibility the alarmack button on the faceplate this seams to work depending on the user who is logged in, the only issue I am unable to understand is that the value I receive from the DVSYS.THISUSER/USER_CAN.F_CV[AREA_A][USERLOCK01] is a -1 not a positive value which is what I would expect.
This is the faceplate logged in as admin (supervisor) that shows the button visible and a value of -1 on the main graphic.
This is the faceplate logged in as an operator showing the button invisible with the value showing 0.
I am happy I think its working but the bug is the -1.
That is how some/most of those checks work and are documented in Help on DeltaV Display Parameters (see below) that way as well.
So you should check = 0 or <> 0 in your animations