WI03 RC and RP OLA violation report followup
Jump to navigation
Jump to search
Under Construction This page describes steps which should be taken by COD shifter to follow availability/reliability issues.
When GGUS ticket about availability/reliability metrics is assigned to COD: 1. add ticket url to Availability and reliability internal procedure for COD tickets page 2. review Ava/Rel report and prepare following lists:
- CASE 1: sites for suspension (Look at two previous months in AR report and the current one. If all are below 50% then sites qualifies for suspension.)
- CASE 2: sites to be asked for explanation (below 75% for reliability and 70% for availability)
3. Generate child tickets for both lists
- for CASE1: when explanation was provided and is found satisfactory, set child ticket to 'verified' status
4. When the deadline (7 working days) expired:
- suspend sites qualified for suspension in GOC DB
- prepare summary of explanations:
- sites which are not responsive
- sites which provided not satisfactory explanation
- ROCs/NGIs which are not responsive