Responding to voice alarms

Sometimes, there may be issues with specific device interlocks or alarms for certain areas that may go off on the VoiceAlarmClient. If an alarm trips, you will hear a loud voice enunciate what the alarm is. Determine which accelerator the alarm is for, FRIB, ReA, or K500. Acknowledge the alarm and if it is for a specific device, navigate to where it may be on phoebus and see if you can plot its history on data browser. This will be convenient for the next part.

Once you have acknowledged the alarm and found where the PV is, either follow the link below to find the instructions for how to respond, or open up the Voice Alarm Binder in the control room and follow the steps. Usually the response will lead you to investigate what the issue is, then contact the personnel on call that is correlated to the device. The personnel will then either give you more instructions on how to reset the device, diagnose the issue themselves and inform you once they have concluded, or tell you to ignore it. Whatever is the case, be sure to post on the hourlog what the voice alarm was that went off, who you contacted, and what action is being taken to resolve it.

Some specific types of alarms

Ion pumps tripping off due to CCGs going invalid

Links

Voice alarm response guidelines