Versions Compared

Old Version 8

changes.mady.by.user Alessandro Paolini

Saved on

compared with

New Version 9

changes.mady.by.user Alessandro Paolini

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This Escalation process is a part of Decommissioning of unsupported software procedure

When an alarm appears on the Operations dashboard, ROD should start the procedure below:

Step [#]Dashboard step

Max. Duration [work days]

(time before moving to next step)

Resp. UnitEscalation procedureContent of the message
11st step10ROD

Create a ticket through Operations Portal with the template: ROD_MW_alarm_template 

Mail is send to the site administrator with CC to NGI/ROC operations manager and GGUS.

One ticket can be created for all MW alarms by using alarm masking feature. ROD should make sure that site is aware of all raised alarms.

  • ask to provide information about upgrade plan with 10 working days deadline
  • in case of no response or plan,  ROD will escalate the issue to NGI operations manager
2NGI step5NGI  manager

Escalate ticket to NGI manager through Operations Dashboard.

Mail is send to the site administrator with CC to NGI/ROC operations manager and GGUS.

(optionally: a phone call to site, just to make sure that e-mail communication channel is working);

NGI manager should check why site is unresponsive or what is the reason site cannot migrate to supported software version. Site and NGI manager should decide on upgrade plan or site/endpoint decommission.

  • inform NGI operations managers about unresponsive site 
  • site might be suspended by Operations, CSIRT or NGI operations manager after DEADLINE for the upgrade/decommissioning


3Operations step  (without delay)ROD

In case of issues which cannot be solved on NGI level ROD should escalate ticket to Operations, who should try to help to find the solution.



The communication should be recorded in GGUS ticket.

Escalation for operational problem with ROD

This section introduces a critical part of operations in terms of problem with ROD. The escalation procedure is a procedure that Operations must follow whenever any problem related to ROD work is detected. The main goal of the procedure is to track the problem follow-up process as a whole and keep the process consistent from the time of detection until the time when the ultimate solution is reached.

The procedure applies only in case when ROD is not handling issues on operational dashboard according to operational procedures.

(Max Duration column shows time in working days which you have to wait before you move to next step in the escalation procedure )

Step [#]

Max. Duration [work days]

(time before moving to next step)

Resp. UnitEscalation procedureContent of the message
13OperationsSend mail to the ROD with CC to NGI/ROC, Operations and GGUS (operational ticket is being created).
  • ask for explanation why an issue was not handled according to procedures
  • ask for immediate action
  • in case of no response for 3 working days Operations will contact NGI/ROC manager
23OperationsSend mail to NGI/ROC manager with CC to ROD, Operations and GGUS.
  • Report that ROD is not responsive and not handling operational issues according to procedure
  • In case of no response for 3 working days Operations will contact COO
3(without delay)OperationsSend mail to COO with CC NGI/ROC manager, Operations and GGUS.
  • Report that ROD and NGI/ROC manager is not responsive and not handling operational issues according to procedure

The precondition to stop escalation is that all issues not handled according to procedure disappeared from Operations dashboard.

The communication should be recorded in GGUS ticket.