Support Team Managers and Service T&A Manager. ELS Duration and Stabilisation (Exit) Criteria GUIDANCE NOTE: Update, amend or add to the example text below and in the table as required. The ELS period will last for a period of up to two weeks from go-live provided the following stabilisation criteria are met. Some criteria are measured using specific indicators, others are based on feedback. Measurement Metric Required for Stabilisation Report/Feedback Provided by Category Operational Platform / Operational Requirements Infrastructure Testing Checklist Known issues without Number of known errors / issues Number of user-impacting, known errors or workaround relating to Operating System or issues arising since migration without a application performance. workaround = 0 (zero) Known Issues with Number of known errors / issues Number of known errors or issues arising since workaround relating to Operating System or migration with a workaround < 5 application performance. Significant Incidents P1 or P2 Incidents reported over Significant (P1 or P2) migration-related Incident a set number of consecutive tickets raised by department or school in the business days. previous 2 business days = 0 (zero)
Support Team Managers and Service T&A Manager. ELS Duration and Stabilisation (Exit) Criteria GUIDANCE NOTE: Update, amend or add to the example text below and in the table as required. The ELS period will last for a period of up to two weeks from go-live provided the following stabilisation criteria are met. Some criteria are measured using specific indicators, others are based on feedback. Measurement Category Metric Required for Stabilisation Report/Feedback Provided by Operational Platform / Infrastructure Testing Operational Requirements Checklist Known issues without workaround Number of known errors / issues relating to Operating System or application performance. Number of user-impacting, known errors or issues arising since migration without a workaround = 0 (zero) Known Issues with workaround Number of known errors / issues relating to Operating System or application performance. Number of known errors or issues arising since migration with a workaround < 5 Significant Incidents P1 or P2 Incidents reported over a set number of consecutive business days. Significant (P1 or P2) migration-related Incident tickets raised by department or school in the previous 2 business days = 0 (zero)