Curriculum
- 2 Sections
- 37 Lessons
- 26 Weeks
- ISO/IEC 20000-112
- 1.1Introduction to IT Service Management and ISO/IEC 20000-1
- 1.2ISO/IEC 20000-1 Structure and Core Clauses
- 1.3Service Management System (SMS) Requirements and Integration
- 1.4Service Portfolio, Service Catalogue, and Service Level Management
- 1.5Relationship Management and Supplier Management
- 1.6Service Design, Transition, and Change Management
- 1.7Incident Management and Service Request Management
- 1.8Problem Management and Configuration Management
- 1.9Availability Management and Capacity Management
- 1.10Information Security Management and IT Service Continuity
- 1.11Performance Evaluation and Continual Improvement
- 1.12Documentation, Records Management, and Compliance
- ISO 19011: Guidelines for auditing management systems26
- 2.1Introduction to ISO19011
- 2.2Principles of Auditing
- 2.3Managing an Audit Program
- 2.4Establishing Audit Program Objectives
- 2.5Determining Audit Program Risks and Opportunities
- 2.6Establishing the Audit Program
- 2.7Implementing the Audit Program
- 2.8Monitoring the Audit Program
- 2.9Reviewing and Improving the Audit Program
- 2.10Initiating the Audit
- 2.11Determining Audit Feasibility
- 2.12Preparing Audit Activities
- 2.13Reviewing Documented Information
- 2.14Preparing the Audit Planx
- 2.15Assigning Work to the Audit Team
- 2.16Preparing Working Documents
- 2.17Opening Meeting
- 2.18Communication During the Audit
- 2.19Collecting and Verifying Information
- 2.20Generating Audit Findings
- 2.21Preparing Audit Conclusions
- 2.22Closing Meeting
- 2.23Preparing the Audit Report
- 2.24Completing the Audit
- 2.25Follow-Up Activities
- 2.26ISO 20000-1 EXAM120 Minutes40 Questions
Incident Management and Service Request Management
Incident Management and Service Request Management
Incident management focuses on restoring normal service operation as quickly as possible following an unplanned interruption or reduction in service quality. The primary objective is to minimize the impact on business operations and ensure continuity of service.
An incident is defined as any event that disrupts or has the potential to disrupt a service. This can include system failures, application errors, network outages, or any other issue affecting service performance.
The incident management process begins with the identification and logging of incidents. All incidents must be recorded to ensure traceability and enable effective tracking. Accurate logging includes capturing relevant details such as the nature of the issue, time of occurrence, affected services, and user information.
Incident Classification and Prioritization
Once an incident is logged, it must be classified and prioritized. Classification involves categorizing the incident based on its type, such as hardware, software, or network-related issues. This helps in assigning the incident to the appropriate support team.
Prioritization is based on the impact and urgency of the incident. High-impact incidents that affect critical services or multiple users are given higher priority and require immediate attention. Lower-priority incidents may be scheduled for resolution within defined timeframes.
A consistent approach to classification and prioritization ensures that resources are allocated effectively and that critical issues are addressed promptly.
Incident Resolution and Escalation
The resolution process involves diagnosing the root cause of the incident and implementing a solution to restore normal service. This may include troubleshooting, applying fixes, or coordinating with other teams or suppliers.
If an incident cannot be resolved within the initial support level, it must be escalated to higher levels of expertise. Escalation ensures that more complex issues receive the necessary attention and resources.
There are typically two types of escalation: functional escalation, where the incident is transferred to a more specialized team, and hierarchical escalation, where management is involved due to the severity or impact of the issue.
Effective escalation procedures ensure that incidents are resolved efficiently and within agreed timeframes.
Communication During Incidents
Clear and timely communication is a critical aspect of incident management. Users and stakeholders must be kept informed about the status of incidents, expected resolution times, and any actions being taken.
Communication helps manage expectations and reduces uncertainty during service disruptions. It also enhances transparency and builds trust between the service provider and users.
Organizations should establish communication protocols to ensure that information is shared consistently and accurately throughout the incident lifecycle.
Once an incident is resolved, it must be formally closed. Closure involves verifying that the service has been fully restored and that the user is satisfied with the resolution.
Incident records should be updated with details of the resolution, actions taken, and any lessons learned. This information supports future analysis and helps improve the incident management process.
In some cases, incidents may require further review to identify underlying issues or trends. This can lead to improvements in processes, systems, or preventive measures.
Service request management focuses on handling user requests that are not related to service disruptions. These requests typically involve standard services such as access requests, information inquiries, or routine service actions.
Unlike incidents, service requests are usually planned and predictable. They follow predefined procedures and are often fulfilled through standardized workflows.
The objective of service request management is to provide a consistent and efficient approach to handling requests, ensuring that users receive timely and accurate responses.
Request Fulfilment Process
The request fulfilment process begins with the submission and logging of a service request. Requests must be recorded and tracked to ensure visibility and accountability.
Each request is then reviewed and categorized to determine the appropriate handling procedure. Standard requests may be automatically routed and fulfilled based on predefined criteria, while more complex requests may require additional approval or processing.
Clear procedures and defined workflows ensure that requests are handled consistently and efficiently.
Approval and Authorization
Some service requests require approval before they can be fulfilled. This is particularly important for requests that involve access to systems, changes to configurations, or allocation of resources.
Approval processes must be clearly defined, including who is authorized to approve different types of requests. This ensures that requests are handled in accordance with organizational policies and security requirements.
Proper authorization helps prevent unauthorized access and ensures that services are delivered in a controlled manner.
Monitoring and Performance Management
Organizations must monitor the performance of both incident management and service request management processes. This includes tracking metrics such as response times, resolution times, and request fulfilment rates.
Performance data provides insights into the efficiency and effectiveness of these processes. It helps identify bottlenecks, areas for improvement, and opportunities to enhance service delivery.
Regular analysis of performance metrics supports continuous improvement and ensures that processes remain aligned with organizational objectives.