MINOS/MINOS+ Remote Operation Centers (ROC's)¶
Remote Operation Centers provides the flexibility for the collaborators to take shifts remotely. To be a certified ROC one must fulfill the prerequisites documented in the DocDB-xxxx-Vn (will be updated soon). This documentations provides a full explanation of the hardware and software requirements, a step-by-step installation procedure and how the certification process works.
This wiki is intended to help the remote shifters to complete their daily tasks during shifts.
Communication protocol during shift transitions¶
Since remote shifts are different from shift performed at the Control Room, a different procedures must be done. A more detailed explanation about these steps can be found in DocDB 9842-v1.
- The oncoming remote shifter calls the current local (or remote) shifter before the end of the current shift to discuss the status of the experiment. It is strongly recommended that the oncoming shifter also checks the Logbook and the Memopad. (Ignore this step if there was no previous shift, but checking the Logbook and MemoPad before the start of the shift is strongly recommended and could avoid some problems.)
- The oncoming remote shifter calls the MCR to inform that a remote shift is starting.
- The oncoming remote shifter must add a note in the Logbook with the shifters name and the ROC informations (location and phone number).
- The oncoming remote shifter must ensure that the remote shift contact information is prominently displayed in the MINOS+ Control Room.
- Oncoming local (or remote) shifter will call the current shifter (local or remote) before the end of the shift.
- The current shifter must state in the logbook that the current remote shift has ended.
- The current remote shift announce display must be removed from the MINOS+ Control Room display.
List of certified ROC's¶
|DATE||STATION||INSTITUTION'S NAME||PHONE||CURRENT RESPONSIBLE|
|2013-05-27||ROC @ Goias||Federal University of Goias||+55 62 3521 1122 ext. 217||Stefano Tognini (firstname.lastname@example.org)|