Working with the Problem Review Board

The goal of the Problem Review BoardA group of people who manage problems. This is done through analyzing incidents as they happen, reviewing historic trend data, and staying current with industry news and vendor updates. The PRB must include representation from relevant individuals to effectively review incident trend data for reactive Problem Management as well as searching for risks from a proactive stance. is to manage problems. This is done through analyzing incidents as they happen, reviewing historic trend data, and staying current with industry news and vendor updates.

The Problem Review Board must include representation from relevant individuals to effectively review incident trend data for reactive Problem Management as well as searching for risks from a proactive stance.

Creating a Problem Review Board

Each Problem can have a unique Problem Review Board, consisting of members. A notification is sent to each member of the Problem Review Board when:

• The root cause of a major problem is identified.
• A majorThis type of change requires a lot of items and/or dependencies and may require other associated change requests. problem is resolved.
• A priority 1 problem is logged.
• A serviceA generally defined framework for actions or items that are provided to an end user. Specific actions, items, response times, and other details are not part of a service definition; those details are defined in service level packages, request offerings, and service level agreements. Instead, a service provides the basis for those detailed definitions. An example of a service is email. After a service is defined, end users do not see or request the service itself. Instead, they use the Service Catalog to view and submit request items, which are features that are based on the service and that you (as a service owner) define and make available to them. Multiple request offerings can be based on the same service. is linked to the problem.

1.

Log in as the Problem ManagerResponsible for managing the lifecycle of all problems. The primary objectives of the role are to prevent incidents from happening and to minimize the impact of unavoidable incidents. The Problem Manager undertakes research for the root causes of incidents, and tries to make sure that interruptions are eliminated., open the Problem workspace, then select the Problem Review Board tab. A list of members appears, if any.

2.

Click Link from the tab toolbar. A list of employees appears.

3.

Select the employee you want to link as a stakeholder and click Select. The employee is linked to the record as a stakeholder and appears in the list

4.

Repeat to add more employees.

5.

Click Save from the toolbar.