Это видео недоступно.
Сожалеем об этом.

Basics of Root Cause Analysis

Поделиться
HTML-код
  • Опубликовано: 15 авг 2024
  • With James Rooney
    Simply stated, root cause analysis is a tool designed to help identify not only what and how an event occurred, but also why it happened. Only when investigators are able to determine why an event or failure occurred will they be able to specify workable corrective and preventive measures that prevent future events of the type observed. Understanding why an event occurred is the key to developing effective recommendations.

Комментарии • 10

  • @sonandpets1215
    @sonandpets1215 Год назад

    Mr. James and ASQ Division, I been watching and learning from RUclips videos on and off for 2 years whatever I can find on RCA. This is BY FAR the best applicable, practical, clear and concise video on RCA I've ever watched!!! Thanks you for your time, effort and for sharing!!! Clear voice, no noisy background music, no weird sounds coming from you in regard to lack of knowledge such as, erm, ummm, VERY KNOWLEDGEABLE GUEST YOU ARE!

  • @henriquepaula9086
    @henriquepaula9086 Год назад

    This is an absolute best presentation for almost anyone in any industry! Well done, Jim.

  • @chidubemiloeje5375
    @chidubemiloeje5375 Месяц назад

    Splendid video. Please how can i get the US department of energy management oversight MORT technique?

  • @isoamauditor3965
    @isoamauditor3965 Год назад +1

    Anyone who is looking to identify a process failure using "root cause" will be as successful as someone look for the Eiffel tower in Innsbruck Austria.
    Process failures are almost never attributed to a "Root Cause"
    Processes are a compilation of many events coming into play at a single point in time. Therefore looking for a root cause to that compilation of events in order to resolve the issue from ever reoccurring, is an impossible task at best.
    -------
    Failure causation should be first defined as to the frequency of its occurrence and the severity of its result
    I have discovered in my nearly 3 decades as a troubleshooter of problems, that process problems are usually resolved when the process is mapped with the relative players, using a cross functional process map (also called a swim lane map). All too often I find the organization and the relative players within a process are making assumptions as to how the process functions, without actually being familiar with what is actually occurring. Mapping the process helps lower the water level and identify the big rocks (so to speak), identifying the cause(s) which can create variation and therefore failure.

  • @irfanmahdee
    @irfanmahdee 3 года назад +1

    Please upload the PDF of the ppt.

  • @irfanmahdee
    @irfanmahdee 3 года назад

    This is a very informative video. Is it possible to improve the sound/voice and repost this video?

    • @hassannimah732
      @hassannimah732 2 года назад

      facilities.uw.edu/partner-resources/files/media/abs-root-cause-map-readable.pdf

  • @nicoleangelic430
    @nicoleangelic430 3 года назад

    Where do we get the map?

    • @hassannimah732
      @hassannimah732 2 года назад

      facilities.uw.edu/partner-resources/files/media/abs-root-cause-map-readable.pdf

  • @arbeitslos4247
    @arbeitslos4247 11 месяцев назад

    Sounds like Orson Welles