When.com Web Search

  1. Ad

    related to: who created root cause analysis tools

Search results

  1. Results From The WOW.Com Content Network
  2. Root cause analysis - Wikipedia

    en.wikipedia.org/wiki/Root_cause_analysis

    In science and engineering, root cause analysis (RCA) is a method of problem solving used for identifying the root causes of faults or problems. [1] It is widely used in IT operations, manufacturing, telecommunications, industrial process control, accident analysis (e.g., in aviation, [2] rail transport, or nuclear plants), medical diagnosis, the healthcare industry (e.g., for epidemiology ...

  3. Root Cause Analysis Solver Engine - Wikipedia

    en.wikipedia.org/wiki/Root_Cause_Analysis_Solver...

    Root Cause Analysis Solver Engine (informally RCASE) is a proprietary algorithm developed from research originally at the Warwick Manufacturing Group (WMG) at Warwick University. [ 1 ] [ 2 ] RCASE development commenced in 2003 to provide an automated version of root cause analysis , the method of problem solving that tries to identify the root ...

  4. Dorian Shainin - Wikipedia

    en.wikipedia.org/wiki/Dorian_Shainin

    Dorian Shainin (September 26, 1914 – January 7, 2000) was an American quality consultant, aeronautics engineer, author, and college professor most notable for his contributions in the fields of industrial problem solving, product reliability, and quality engineering, particularly the creation and development of the "Red X" concept.

  5. Five whys - Wikipedia

    en.wikipedia.org/wiki/Five_whys

    The artificial depth of the fifth why is unlikely to correlate with the root cause. The five whys is based on a misguided reuse of a strategy to understand why new features should be added to products, not a root cause analysis. To avoid these issues, Card suggested instead using other root cause analysis tools such as fishbone or lovebug diagrams.

  6. Ishikawa diagram - Wikipedia

    en.wikipedia.org/wiki/Ishikawa_diagram

    Sample Ishikawa diagram shows the causes contributing to problem. The defect, or the problem to be solved, [1] is shown as the fish's head, facing to the right, with the causes extending to the left as fishbones; the ribs branch off the backbone for major causes, with sub-branches for root-causes, to as many levels as required.

  7. Eight disciplines problem solving - Wikipedia

    en.wikipedia.org/wiki/Eight_Disciplines_Problem...

    The design or process controls in a FMEA can be used in verifying the root cause and Permanent Corrective Action in an 8D. The FMEA and 8D should reconcile each failure and cause by cross documenting failure modes, problem statements and possible causes. Each FMEA can be used as a database of possible causes of failure as an 8D is developed.

  8. DMAIC - Wikipedia

    en.wikipedia.org/wiki/DMAIC

    A data collection plan is created and data are collected to establish the relative contribution of each root causes to the project metric (Y). This process is repeated until "valid" root causes can be identified. Within Six Sigma, often complex analysis tools are used. However, it is acceptable to use basic tools if these are appropriate.

  9. Failure reporting, analysis, and corrective action system

    en.wikipedia.org/wiki/Failure_reporting...

    FRACAS records the problems related to a product or process and their associated root causes and failure analyses to assist in identifying and implementing corrective actions. The FRACAS method [ 1 ] was developed by the US Govt. and first introduced for use by the US Navy and all department of defense agencies in 1985.