RPR Problem Diagnosis

RPR Problem Diagnosis

RPR is a problem diagnosis method specifically designed to determine the Root Cause of IT problems.

Overview

RPR deals with failures, incorrect output and performance issues, and its particular strengths are in the diagnosis of ongoing recurring problems. The method comprises:

* Core Process
* Supporting Techniques

The Core Process defines a step-by-step approach to problem diagnosis and has three phases:

* Discover
** Gather & review existing information
** Reach an agreed understanding
* Investigate
** Create & execute a diagnostic data capture plan
** Analyse the results & iterate if necessary
** Identify Root Cause
* Fix
** Translate diagnostic data
** Determine & implement fix
** Confirm Root Cause addressed

The Supporting Techniques detail how the objectives of the Core Process steps are achieved, and cite examples using tools and techniques that are available in every business.

Standards alignment

RPR has been fully aligned with ITIL v3 since RPR 2.01 was released in April 2008. RPR fits directly into the ITIL v3 Problem Management Process as a sub-process. Some organisations handle ongoing recurring problems within Incident Management, and RPR also fits into the ITIL v3 Incident Management Process as a sub-process.

COBIT also defines a Problem Management Process (DS10) with key activity of "Perform root cause analysis". RPR is a superset of this step in that it defines a process that covers all of the activities needed to perform Problem investigation & diagnosis, including Root Cause identification.

Limitations

RPR has some limitations and considerations, including:

* RPR deals with a single symptom at one time
* RPR is not a forensic technique and so historical data alone is rarely sufficient
* The Investigate phase requires the user to experience the problem one more time

History

The method was originally developed by advance7 in 1990 as the Rapid Problem Resolution Method, with the first fully documented version produced in 1995. Early versions included problem management guidance but this was removed over time as the method became more closely aligned to ITIL. RPR is now focused on Problem Diagnosis based on Root Cause Identification. Due to the highly practical nature of the Supporting Techniques and the ever changing IT landscape, advance7 continues to develop RPR to keep it relevant to current IT environments.

Until November 2007 advance7 made the RPR material available to its employees only, although a limited number of other IT professionals have been trained in the use of the method. In late 2007 the company announced its intention to make RPR training and material more widely available.

ee also

* ITIL v3 Problem Management
* ITIL v3 Incident Management
* COBIT

Further reading

* [http://coventry.bcs.org/past_events.php RPR presentation to the British Computer Society]


Wikimedia Foundation. 2010.

Игры ⚽ Нужна курсовая?

Look at other dictionaries:

  • Problem solving — forms part of thinking. Considered the most complex of all intellectual functions, problem solving has been defined as higher order cognitive process that requires the modulation and control of more routine or fundamental skills (Goldstein Levin …   Wikipedia

  • RPR — is a three letter abbreviation that can refer to: * Raipur Airport, the IATA code for the airport in India * Rally for the Republic, a defunct French political party ( Rassemblement pour la République ) * Rapid Plasma Reagin, a modern screening… …   Wikipedia

  • Grey Area Diagnosis — is an activity performed during Incident Management. It is the activity via which the cause(s) of an Incident are determined in order to escalate the Incident to the appropriate team(s) for further investigation and resolution. Advantages:… …   Wikipedia

  • Information Technology Infrastructure Library — The Information Technology Infrastructure Library (I), is a set of good practices for IT service management (ITSM) that focuses on aligning IT services with the needs of business. In its current form (known as ITILv3 and ITIL 2011 edition), ITIL… …   Wikipedia

  • Decision making — For Decision making in groups, see Group decision making. Sample flowchart representing the decision process to add a new article to Wikipedia. Decision making can be regarded as the mental processes (cognitive process) resulting in the selection …   Wikipedia

  • Troubleshooting — is a form of problem solving. It is the systematic search for the source of a problem so that it can be solved. Troubleshooting is often a process of elimination eliminating potential causes of a problem. Troubleshooting is used in many fields… …   Wikipedia

  • Root cause analysis — (RCA) is a class of problem solving methods aimed at identifying the root causes of problems or events. Root Cause Analysis is any structured approach to identifying the factors that resulted in the nature, the magnitude, the location, and the… …   Wikipedia

  • Cause Mapping — is a problem solving method that draws out, visually, the multiple chains of interconnecting causes that lead to an incident. The method, which breaks problems down specific cause and effect relationships, can be applied to a variety of problems… …   Wikipedia

  • Root cause — A root cause is an initiating cause of a causal chain which leads to an outcome or effect of interest. Commonly, root cause is used to describe the depth in the causal chain where an intervention could reasonably be implemented to change… …   Wikipedia

  • test — 1. To prove; to try a substance; to determine the chemical nature of a substance by means of reagents. 2. A method of examination, as to determine the presence or absence of a definite disease or of some substance in any of the fluids, tissues,… …   Medical dictionary

Share the article and excerpts

Direct link
… Do a right-click on the link above
and select “Copy Link”