Difference between revisions of "WI05 Unresponsive NGI escalation"
| Line 1: | Line 1: | ||
In case of not responding NGI, COD should:<br> | In case of not responding NGI, COD should:<br> | ||
| − | #Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC DB - NGIs List]) | + | #Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from [http://tinyurl.com/724emw5 GOC DB - NGIs List] or in Dashboard) |
| − | #Make a phone call to NGI manager (phone number can be found in GOC DB - look at given NGI's detailes - do not forgot about time zones ;) ) | + | #Make a phone call to NGI manager (phone number can be found in GOC DB - look at given NGI's detailes - do not forgot about time zones ;) ) |
| + | #Mail to COO with full report about the situation. | ||
<br> | <br> | ||
Revision as of 09:52, 28 May 2012
In case of not responding NGI, COD should:
- Send an email to NGI managers mailing list and to each of NGI managers and ask for action (email can be taken from GOC DB - NGIs List or in Dashboard)
- Make a phone call to NGI manager (phone number can be found in GOC DB - look at given NGI's detailes - do not forgot about time zones ;) )
- Mail to COO with full report about the situation.
