General Problem Management. Service Provider’s responsibilities include: 1. Implement a robust and auditable process for Problem Management, which is approved by DIR. 2. Use the approved Problem Management process to reduce the recurrence of Incidents. 3. Communicate the Problem Management process within Service Provider and to each Third Party Vendor(s) with which an OLA or underpinning contract exists. 4. Manage the effective entry of data into Problem Management systems and escalate to DIR and DIR Customer for prioritization and approval. 5. Manage and Resolve any deviation from the effective management of Problems. 6. Perform regular review of Incidents to identify recurring Incidents and associated Problems. 7. Engage with Financial Management processes to provide effective business cases / return on investment analysis to quantify the cost and benefit of implementing Problem / Known Error Resolutions. 8. Implement the corrective actions as identified in an expedited fashion. 9. Submit Request for Changes (RFC) through the Change Management Process to request the Resolution of Problems / Known Errors. 10. Validate that Problem Resolution and corrective actions taken through Change Management are sufficient to confirm that root causes identified do not recur in same or similar environments. This includes update of manuals, procedures, and other documentation, and the submission of RFCs through the Change Management process to facilitate changes to other services, systems or components which have been impacted by the same or similar Problems / Known Errors. 11. Verify and track that the identified corrective actions are being implemented. 12. Escalate to appropriate management within DIR, DIR Customers, Service Provider and all Third Party Vendor(s) if corrective actions are not being closed. 13. Document workarounds for Incidents that can be used to support the handling of future Problems and Incidents, and which will: 13.1. Be stored in the Known Error Database / Knowledge Database. 13.2. Have a unique identifier or reference number. 13.3. Be categorized in a manner like the categorization of Incidents and Problems in order to facilitate effective identification and use. 13.4. Provide a detailed description of the steps to be executed to implement the workaround. 13.5. Provide a detailed description of any required inputs, capabilities, resources, etc. that are required for proper execution of the workaround. 13.6. Describe the appropriate context under which the workaround is to be used and/or conditions under which it is not to be used. 13.7. Provide a reference to previous Incidents, Problems and Known Errors to which the workaround is related. 13.8. Provide a reference to the service, system or configuration item / component to which the workaround is related. 14. Update Known Error Database / Knowledge Database with all relevant information, including documented workarounds for Problems / Known Errors as they identified and addressed. 15. Routinely perform trend analyses on the volume and nature of Problems in order to identify areas for improvement. 16. Provide additional treatment of Major Problems as required. 17. Develop tools/scripts and enhance processes to proactively perform Problem Management, with the objectives of automating the Problem Management process and predicting Problems before they occur. 18. Implement measures to avoid unnecessary reoccurrence of Problems. 19. Manage all Problems in accordance with consistent and agreed classification and prioritization criteria.
Appears in 3 contracts
Sources: Master Services Agreement, Master Services Agreement, Master Services Agreement
General Problem Management. Service Provider’s Provider responsibilities include:
1. Implement a robust and auditable process for Problem Management, which is approved by DIR.
2. Use the approved Problem Management process to reduce the recurrence of Incidents.
3. Communicate the Problem Management process within the Service Provider and to each Third Party Vendor(s) DCS Service Provider with which an OLA or underpinning contract existsexists to provide the Services.
4. Manage the effective entry of data into Problem Management systems systems, and escalate to DIR and DIR Customer MSI for prioritization and approval.
5. Manage and Resolve any deviation from the effective management of Problems.
6. Perform regular review of Incidents to identify recurring Incidents and associated Problems.
7. Engage with Financial Management processes to provide effective business cases / return on investment analysis to quantify the cost and benefit of implementing Problem / Known Error Resolutions.
8. Implement the corrective actions as identified in an expedited fashion.
9. Submit Request for Changes (RFC) RFC through the Change Management Process to request the Resolution resolution of Problems / Known Errors.
10. Validate that Problem Resolution and corrective actions taken through Change Management are sufficient to confirm that root causes identified do not recur in same or similar environments. This includes update of manuals, procedures, and other documentation, and the submission of RFCs through the Change Management process to facilitate changes to other services, systems or components which have been impacted by the same or similar Problems / Known Errors.
11. Verify and track that the identified corrective actions are being implemented.
12. Escalate to appropriate management within DIR, DIR Customers, the other DCS Service Provider Providers and all Third Party Vendor(s) if corrective actions are not being closed.
13. Document workarounds work-around for Incidents that can be used to support the handling of future Problems and Incidents, and which will:
13.1. Be stored in the Known Error Database / Knowledge Database.
13.2. Have a unique identifier or reference number.
13.3. Be categorized in a manner like the categorization of Incidents and Problems in order to facilitate effective identification and use.
13.4. Provide a detailed description of the steps to be executed to implement the workaround.
13.5. Provide a detailed description of any required inputs, capabilities, resources, etc. that are required for proper execution of the workaround.
13.6. Describe the appropriate context under which the workaround is to be used and/or conditions under which it is not to be used.
13.7. Provide a reference to previous Incidents, Problems and Known Errors to which the workaround is related.
13.8. Provide a reference to the service, system or configuration item / component to which the workaround is related.
14. Update Known Error Database / Knowledge Database with all relevant information, including documented workarounds for Problems / Known Errors as they are identified and addressed.
15. Routinely perform trend analyses on the volume and nature of Problems in order to identify areas for improvement.
16. Provide additional treatment of Major Problems as required.
17. Develop tools/scripts and enhance processes to proactively perform Problem Management, with the objectives of automating the Problem Management process and predicting Problems before they occur.
18. Implement measures to avoid unnecessary reoccurrence of Problems.
19. Manage all Problems in accordance with consistent and agreed classification and prioritization criteria.
Appears in 2 contracts
Sources: Data Center Services Service Component Provider Master Services Agreement, Master Services Agreement