ROD Communication

From EGIWiki
Revision as of 13:33, 16 June 2011 by Pslizik (talk | contribs) (Created the page based on the relevant sections of the Draft)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Handover log model

At the end of a shift the current ROD team should prepare the handover for internal ROD matters. Each ROD can decide independently on what the handover should look like and how it should be passed on to the next team. This document just provides suggestions for how it could be:

  1. List of tickets which will continue into the next week: name of the site, ROD ticket ID (if your NGI uses an internal ticket system) and GGUS Ticket number, the current status of the ticket.
  2. Report any problems with operational tools during the shift.
  3. Report encountered problems with core grid services.
  4. Any tickets opened that are not related to a particular alarm
  5. Anything else the new team should know?

Communication lines

ROD should provide an email contact to where all ticket information should be sent and also to make it possible for COD or other bodies to contact them directly. For internal communication ROD can use mailing list(s), instant messengers etc. Each ROD team is free to choose how the internal communication is established.

ROD should communicate with COD through the COD mailing list central-operator-on-duty(AT) For urgent matters, it should be done via a GGUS ticket assigned to COD support unit to make tracking of the case possible.

There is also the handover section in the ROD dashboard which allows for COD and RODs to intercommunicate.

In the case of a non-responsive ROD, COD shall create a GGUS ticket to the appropriate NGI.