FRIB Operators

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 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. There are four different types of alarms: AS(Accelerator Systems), CF(Conventional Facilities), ES(Experimental Systems), and NC(Non-Conventional Facilities). 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.

{{ :task:voicealarmclient_2025-08-20_10-57-05.png?600 |}}
Above is an example picture of the VoiceAlarmClient for FRIB on the FTC network.


==== Some specific types of alarms ====
  * [[ion_pump_trips|Ion pumps tripping off due to CCGs going invalid]]




===== Links =====
  * [[portal>sites/accsystems/preoperation/SitePages/Voice Alarm (Serious Alarm) response guidelines.aspx|Voice alarm response guidelines]]


----
====Notes====
  Shane: Unnecessary to check which system, they'll be on the same network as whatever is causing the alarm
  Shane: Should cover the software, how to acknowledge, could be expanded to cover muting alarms
  Shane: Clean up the portion about "group correlated to device", overly complicated, just follow directions and maybe go over contact lists
  Shane: could expand to cover how to find devices
  Shane: should mention checking ongoing work
  Shane: for response, contacted person should probably stay on the line while directing operators, they may tell us to ignore it, but it should be included that they'll have to come in sometimes, then could link to int. comp forms