- ITIL Basics
- ITIL - Home
- ITIL - Overview
- ITIL - Terminologies
- ITIL - Service Basics
- ITIL - Service Lifecycle
- Service Strategy
- ITIL - Service Strategy Overview
- ITIL - Service Strategy Roles
- ITIL - Strategy Generation
- ITIL - Service Portfolio Management
- Business Relationship Management
- ITIL - Demand Management
- ITIL - Financial Management
- Service Design
- ITIL - Service Design Overview
- ITIL - Service Catalogue Management
- ITIL - Service Level Management
- ITIL - Capacity Management
- ITIL - Availability Management
- ITIL - Service Continuity Management
- Information Security Management
- ITIL - Supplier Management
- Service Transition
- ITIL - Service Transition Overview
- ITIL - Project Management
- ITIL - Change Management
- Service Assets and Configuration Management
- Release and Deployment Management
- ITIL - Service and Validation Testing
- Service Operation
- ITIL - Service Operation Overview
- ITIL - Event Management
- ITIL - Incident and Request
- ITIL - Problem Management
- ITIL - Access Management
- Continual Service Improvement
- CSI Overview
- Service Reporting
- ITIL Useful Resources
- ITIL - Quick Guide
- ITIL - Useful Resources
- ITIL - Discussion
ITIL - Problem Management
In ITIL, Problem is defined as unknown cause of one or more incident.
Problem Management ensures the identification of problems and performs Root Cause Analysis. It also ensures that recurring incidents are minimized and problems can be prevented.
Problem Manager is the process owner of this process.
Key Points
Problem Management comprises of activities required to diagnose the root cause of the incident and to determine the resolution to those problems.
When a problem is resolved after root cause analysis, it becomes known error.
Problem Management also records information regarding problems in a system called Known Error Database (KED).
Problem Management consists of following two processes −
Reactive Problem Management is executed as part of service operation.
Proactive Problem Management initiated in service operation but generally driven as part of Continual Service Improvement
Problem Management Process
The following diagram describes activities involved in Problem Management −
Problem detection
Problem can be detected in following ways −
Analysis of incident by technical support group.
Automated detection of an infrastructure or application fault, using alert tools automatically to raise an incident which may reveal the need for problem management.
A notification from supplier that a problem exists that has to be resolved.
Problem logging
Problem should be fully logged and contains the following details −
User details
Service details
Equipment details
Priority and categorization details
Date/time initially logged
Problem categorization
In order to trace true nature of Problem, It is must to categorize the Problems in same way as Incidents.
Problem Prioritization
Problems must be categorized in the same way as incidents to identify how serious the Problem is from an infrastructure perspective.
Workarounds
It is temporary way to overcome the difficulties. Details of workaround should always be documented within Problem record.
Raising a Known Error Record
Known error must be raised and placed in Known Error Database for future reference.
Problem Resolution
Once resolution is found, it must be applied and documented with the problem details.
Problem closure
At time of closure, a check should be performed to ensure that record contains full historical descriptions of all events.
Major Problem Review
A review of following things should be made −
Those things that were done correctly
Those things that were done wrong
What could be done better in future
How to prevent recurrence