Project Delay

  • Upload
    kit2584

  • View
    218

  • Download
    0

Embed Size (px)

Citation preview

  • 8/11/2019 Project Delay

    1/22

    1Determining Root Cause 1

    Determining the RootCause of a Problem

    Approved for Public Release

  • 8/11/2019 Project Delay

    2/22

    2Determining Root Cause 2

    Why Determine Root Cause?

    Prevent problems from recurring

    Reduce possible injury to personnel

    Reduce rework and scrap

    Increase competitiveness

    Promote happy customers and stockholders

    Ultimately, reduce cost and save money

    Approved for Public Release

  • 8/11/2019 Project Delay

    3/22

  • 8/11/2019 Project Delay

    4/22

    4Determining Root Cause 4

    Often the Stated Root Cause

    is the Quick, but Incorrect Answer

    For example, a normal response is:

    Equipment Failure

    Human Error

    Initial response is usually the symptom, notthe root cause of the problem. This is whyRoot Cause Analysis is a very useful andproductive tool.

    Approved for Public Release

  • 8/11/2019 Project Delay

    5/22

  • 8/11/2019 Project Delay

    6/22

    6Determining Root Cause 6

    What is Root Cause Analysis?

    Root Cause Analysis is an in-depth

    process or technique for identifying the

    most basicfactor(s) underlying avariation in performance (problem).

    Focus is on systems and processes Focus is not on individuals

    Approved for Public Release

  • 8/11/2019 Project Delay

    7/22

    7Determining Root Cause 7

    When Should Root Cause

    Analysis be Performed? Significant or consequential events

    Repetitive human errors are occurringduring a specific process

    Repetitive equipment failures associatedwith a specific process

    Performance is generally below desired

    standard May be SCAR or CPAR (NGNN) driven

    Repetitive VIRs

    Approved for Public Release

  • 8/11/2019 Project Delay

    8/22

    8Determining Root Cause 8

    How to Determine the Real

    Root Cause? Assign the task to a person (team if necessary)

    knowledgeable of the systems and processes involved

    Define the problem

    Collect and analyze facts and data

    Develop theories and possible causes - there may bemultiple causes that are interrelated

    Systematically reduce the possible theories and possiblecauses using the facts

    Approved for Public Release

  • 8/11/2019 Project Delay

    9/22

    9Determining Root Cause 9

    How to Determine the Real

    Root Cause? (continued) Develop possible solutions

    Define and implement an action plan (e.g., improvecommunication, revise processes or procedures or work

    instructions, perform additional training, etc.)

    Monitor and assess results of the action plan forappropriateness and effectiveness

    Repeat analysis if problem persists- if it persists, did weget to the root cause?

    Approved for Public Release

  • 8/11/2019 Project Delay

    10/22

    10Determining Root Cause 10

    Useful Tools For

    Determining Root Cause are: The 5 Whys

    Pareto Analysis (Vital Few, Trivial Many)

    Brainstorming

    Flow Charts / Process Mapping Cause and Effect Diagram

    Tree Diagram

    Benchmarking (after Root Cause is found)

    Some tools are more complex than others

    Approved for Public Release

  • 8/11/2019 Project Delay

    11/22

    11Determining Root Cause 11

    Example of Five Whys for Root

    Cause Analysis

    Problem - Flat Tire

    Why? Nails on garage floor Why? Box of nails on shelf split open

    Why? Box got wet

    Why? Rain thru hole in garage roof Why? Roof shingles are missing

    Approved for Public Release

  • 8/11/2019 Project Delay

    12/22

    12Determining Root Cause 12

    Pareto Analysis

    Count 14 14 11 9 7 7 3 3 3 3162 2 2 1 513934 20 19 19 15 15

    Percent 3 3 2 2 1 1 1 1 1 132 0 0 0 127 7 4 4 4 3 3

    Cum % 86 89 91 93 94 96 96 97 97 9832 98 99 991005966 70 74 78 80 83

    Count

    Defect

    Othe

    r

    EBDam

    aged

    Su

    pplie

    rClea

    nline

    ss

    EBMark

    ing

    Supp

    lierRu

    sted,

    Corr

    oded

    EBIn

    corre

    ctMat

    erial

    EB

    Docu

    ment

    ation

    EBDim

    ensio

    n

    Suppli

    erMiss

    ingPart

    s

    ESD

    Pack

    aging

    Supplie

    rLab

    Tes

    tFailu

    re

    Supp

    lierShelf

    Life

    Exc

    eede

    d

    Supp

    lierWro

    ngCon

    figur

    ation

    Supp

    lierO

    ther

    Workm

    anship

    Supp

    lierIn

    corre

    ctMat

    erial

    S

    uppli

    erDam

    aged

    Pack

    aging

    Supp

    lierD

    imen

    sions

    EBOth

    er

    Supplie

    rDoc

    umen

    tatio

    n

    Supp

    lierM

    arking

    180

    160

    140

    120

    100

    80

    60

    40

    20

    0

    Supplier Material Rejections May 06 to May 07

    Vital Few

    Trivial Many

    60 % of

    Material

    Rejections

    Approved for Public Release

  • 8/11/2019 Project Delay

    13/22

    13Determining Root Cause 13

    Cause and Effect Diagram(Fishbone/Ishikawa Diagrams)

    EFFECT

    CAUSES (METHODS) EFFECT (RESULTS)

    Four Ms Model

    MAN/WOMAN METHODS

    MATERIALS MACHINERY

    OTHER

    Approved for Public Release

  • 8/11/2019 Project Delay

    14/22

    14Determining Root Cause 14

    Cause and Effect DiagramLoading My Computer

    MAN/WOMAN METHODS

    MATERIALS MACHINERY

    OTHERCannot

    Load

    Softwar

    e on PC

    Inserted CD Wrong

    Instructions are Wrong

    Not Enough

    Free Memory

    Inadequate System

    Graphics Card Incompatible

    Hard Disk Crashed

    Not Following

    Instructions

    Cannot Answer Prompt

    Question

    Brain Fade

    CD Missing

    Wrong Type CDBad CD

    Power Interruption

    Approved for Public Release

  • 8/11/2019 Project Delay

    15/22

    15Determining Root Cause 15

    Tree Diagram

    Result Cause/Result Cause/Result Cause

    Result Primary

    Causes

    Secondary

    CausesTertiary

    Causes

    Approved for Public Release

  • 8/11/2019 Project Delay

    16/22

    16Determining Root Cause 16

    Tree Diagram

    Poor SafetyPerformance

    Stale/TiredApproaches

    InappropriateBehaviors

    Lack ofEmployeeAttention

    Lack of Models/Benchmarks

    No Outside Input

    Research Not

    Funded

    No Money for ReferenceMaterials

    No Funds forClasses

    No Consequences

    InfrequentInspections

    InadequateTraining

    No Publicity

    Lack of Sr.Management Attention

    No PerformanceReviews

    No Special SubjectClasses

    Lack of RegularSafety Meetings

    Zero Written SafetyMessages

    No Injury CostTracking

    Result Cause/Result Cause/Result Cause

    Approved for Public Release

  • 8/11/2019 Project Delay

    17/22

    17Determining Root Cause 17

    Bench Marking

    Benchmarking: What is it?

    "... benchmarking ...[is] ...'the process of identifying, understanding, andadapting outstanding practices and processes from organizationsanywhere in the world to help your organization improve itsperformance.'"American Productivity & Quality Center

    "... benchmarking ...[is]... an on-going outreach activity; the goal of theoutreach is identification of best operating practices that, whenimplemented, produce superior performance."Bogan and English, Benchmarking for Best Practices

    Benchmark refers to a measure of best practice performance.Benchmarkingrefers to the search for the best practices that yields thebenchmark performance, with emphasis on how you can apply theprocessto achieve super ior resul ts.

    Approved for Public Release

  • 8/11/2019 Project Delay

    18/22

    18Determining Root Cause 18

    Bench Marking

    All process improvement efforts require a soundmethodology and implementation, and benchmarkingis no different. You need to:

    Identify benchmarking partners Select a benchmarking approach

    Gather information (research, surveys, benchmarkingvisits)

    Distill the learning Select ideas to implement

    Pilot

    Implement

    Approved for Public Release

  • 8/11/2019 Project Delay

    19/22

    19Determining Root Cause 19

    Common Errors of Root Cause

    Looking for a single cause- often 2 or 3

    which contribute and may be interacting

    Ending analysis at a symptomatic cause Assigning as the cause of the problem the

    why event that preceded the real cause

    Approved for Public Release

  • 8/11/2019 Project Delay

    20/22

    20Determining Root Cause 20

    Successful application of the

    analysis and determination of

    the Root Cause should result

    in elimination of the problem

    and create Happy Campers!

    Approved for Public Release

  • 8/11/2019 Project Delay

    21/22

    21Determining Root Cause 21

    Summary:

    Why determine Root Cause? What Is Root Cause Analysis?

    When Should Root Cause Analysis beperformed?

    How to determine Root Cause Useful Tools to Determine Root Cause1. Five Whys

    2. Pareto Analysis

    3. Cause and Effect Diagram

    4. Tree Diagram5. Brainstorming

    Common Errors of Root Cause

    Where can I learn more?

    Approved for Public Release

  • 8/11/2019 Project Delay

    22/22

    22Determining Root Cause 22

    Where Can I Learn More?

    Solving a Problem & Getting Along: Toward the Effective Root CauseAnalysis, Khaimovich,1998.

    The Quality Freeway, Goodman, 1990

    Potential Failure Modes & Effects Analysis: A Business Perspective, Hatty

    & Owens, 1994

    In Search of Root Cause, Dew, 1991

    Solving Chronic Quality Problems, Meyer, 1990

    The Tools of Quality, Part II: Cause and Effect Diagrams, Sarazen, 1990

    Root Cause Analysis: A Tool for Total Quality Management, Wilson, Dell &Anderson, 1993

    Approved for Public Release