Previous Topic

Book Contents

Book Index

Next Topic

Major Problem Review

The object of this process is to review the resolution of a Problem in order to prevent recurrence and learn any lessons for the future. Furthermore it is to be verified whether the Problems marked as closed have actually been eliminated.

The following example demonstrates the application of the major Problem review in the context:

  1. When a Problem is detected, create a new Problem in a usual way.

    Help Image

  2. Click the 'Classify' button below to classify the Problem.

    A Ticket Description dialog box asking you for an additional ticket description appears. You can see that the Statement Type is set to 'Information'. Fill in the Shorttext field at least and click 'OK' to proceed.

  3. You can see that the status has changed to 'Classified' in the Problem Editor.

    Help Image

  4. Click the 'Work on' button to confirm that the Problem is being worked on.

    Now you can either assign the Problem to another Support Group or mark the Problem as investigated (i.e. the diagnoses has been done).

    Help Image

  5. In this example, click 'Investigated' to proceed.

    A new ticket description will be required. Note that the Statement Type has changed to 'Analyze'.

  6. Click 'OK' to proceed.

    You can see that the status has changed to 'Investigated' in the Problem Editor. Below you can decide if you want to close the problem (if no solution found) or identify the solution.

    Help Image

  7. Click 'Solution Identified' because you have been able to identify the solution.

    Again, a new ticket description will be required. Note that the Statement Type has changed to 'Proposal'.

  8. Click 'OK' to proceed.

    You can see that the status has changed to 'Solution Identified' in the Problem Editor. Below you can decide if the solution failed or if the Problem can be considered resolved.

    Help Image

    At this stage, you can also create and assign a Superior RFC/Change on the appropriate tab below if necessary.

  9. Click 'Resolved' to proceed.

    A new ticket description will be required. Note that the Statement Type has changed to 'Solution'.

  10. Click 'OK' to proceed.

    In the Problem Editor, click 'Work On'

    Now you can either Close the Problem or do the Major Problem Review.

    Help Image

  11. Click the 'Major Problem Review',

    A new ticket description will be required. Note that the Statement Type has changed to 'Comment'.

    Help Image

    By filling in this ticket description, you are reviewing your experience with this Problem and assign it to the Problem.

  12. Click 'OK' to proceed.

    In the Problem Editor, you can see that the status changed to 'Major Problem Review'.

    Help Image

  13. Close the Problem after the Major Problem Review using the 'Close Problem' button below.

    Note that you had the possibility to close the Problem before if you didn't want to make the Major Problem Review.

See Also

Problem Management Use Cases

Create a Problem Directly

Create a Problem from an Unsolved Incident

Create a Problem According to Incident Analysis

Create a Problem according to a Model Ticket

Assign a Problem

Accept and Edit a Problem (Analysis)

Confirm / Decline a Problem

Problem RCA

Cause + Problem solution found

Cause Found: Create + Assign Error

Accept Error Solution

Request Error Solution

Create and Assign Workaround

Workaround - Editing Process

Workaround - Approval/Rejection

Workaround - Complete

Problem and Error Control

Problem Reporting

Search Solution in KC

KB Proposal

Relate 'N' Systems or Components to an Incident/Problem