Problem Management

A problem is the cause or potential cause of one or more incidents

Problem Management supports the ITIL process used to find and fix the root cause of issues that result in incidents. You can record problems, associate incidents, and assign them to the appropriate groups. You can document and communicate known errors and initiate actions to resolve the situation.

Problem Management is responsible for managing the life cycle of all problems and preventing problems and resulting incidents from happening. It also aims to eliminate recurring incidents and minimize the impact of incidents that can’t be prevented. Resolving a problem includes the activities required to diagnose the root cause of incidents and determine the resolution for the problem. Problem resolution and elimination of the root cause often calls for applying a change to the configuration item in the existing IT environment.

Problem Management also maintains information about problems and the appropriate workarounds and resolutions, enabling an organization to reduce the number and impact of incidents over time. Problem Management interfaces with Knowledge Management, which is used to document known error articles thoroughly for future reference.

Problem Management workflow

The Problem Management workflow includes the following:

1. Problem Creation: You can create a problem to identify and permanently fix the underlying root cause when:
   • You've resolved a major incident.
   • You have recurring incidents.
2. Assign the problem: You can now assign the problem to be assessed.
3. Assess(Evaluate or Estimate) the problem: You can now assess the problem:
   • Find and relate any additional incidents that the problem represents.
   • If the problem was created from an incident, it has inherited fields from the incident that may not provide a specific description of the issue. In this case, update the Problem Statement and other fields to specifically describe this issue to help the team performing the root cause analysis during the later stages.
   • Do any of the following:
     • Confirm that you plan to work on this problem. This confirmation moves the problem to the Root Cause Analysis state.
     • Mark this problem as a duplicate of an existing problem to close the problem.
     • Cancel this problem if it's not a valid problem. Canceling it closes the problem.
4. Analyze the root cause of the problem:
   • If you're the subject matter expert, analyze the problem to uncover the root cause and identify a fix.
   • If you're not the subject matter expert, create a Root Cause Analysis Problem task to assign to the relevant team. Coordinate with that team as they analyze and uncover the root cause and fix.
   • If there's no permanent fix for the problem, or you don't have the sufficient budget to fix the problem at this time, accept the risk that it can't be fixed at this time. The problem enters the Closed state. It's a good idea to review risk-accepted problems periodically.
5. Communicate the outcome of the problem:
   • After you identify the fix or workaround of the problem, update the workaround or fix for the problem. Communicate updates to the related incidents.
   • If the problem is a known error, create a known error article that is primarily available to help others find information and deflect additional incidents. The known error article can also be referred to by agents who are facing similar problems and incidents.
6. Fix the underlying root cause if possible. If you can fix the root cause, create a change request and assign it to the relevant team. When the change request is completed, resolve the problem. If no new incidents come in, close the problem.
7. Reanalyze the problem if it resurfaces. If you're the problem manager and you're not satisfied with the analysis after resolving or closing the problem, or the problem resurfaces, you can decide to reanalyze the problem. The problem is reopened and the state is changed to Root Cause Analysis.

Problem Management benefits

Benefit	Feature	Users
Create a problem to identify the root cause of the incident.	Create a problem	Agent and Problem write users
Add multiple incidents to a problem to avoid creating multiple problems for incidents that have the same issue.	Add multiple incidents to a problem	Agent
Create a problem task to initiate the root cause analysis.	Create a problem task	Agent, Problem write users, and Problem task analyst
Document and communicate a workaround to restore service failures and lessen the impact of a problem that an actual resolution is not yet available.	Communicate workaround for Problem	Problem Coordinator
Create known error articles as reference material.	Create a known error article	Problem Coordinator
Implement a resolution to a problem by applying a standard change procedure and testing it to confirm service recovery.	Create change request from a problem	Problem Coordinator
Resolve the issue and add detailed notes for the resolution for future reference.	Resolve and complete a problem	Problem Coordinator

• Problem Management process Within the platform, problems are handled using the task record system. Each problem is generated as a task record through various means, and is populated with the pertinent information. These tasks are assigned to Problem Management team members to resolve and then close. • Problem Management models You can use Problem Management models to tailor processes for specific use cases.

• • Problem Management process

  Within the platform, problems are handled using the task record system. Each problem is generated as a task record through various means, and is populated with the pertinent information. These tasks are assigned to Problem Management team members to resolve and then close.

• • Problem Management models

  You can use Problem Management models to tailor processes for specific use cases.