site map Root Cause Methodology and Tools for Improved Operations
Home
About TapRooT®
Course Info
Summit Info
Software
Equipment Troubleshooting
Weblog
Store
Support
Contact Us

Archive for November 21st, 2007

Fault with Fault Trees

Wednesday, November 21st, 2007

Many of us have had experience working with fault trrees.  We have worked throught the painstaking process of determining how a particular material failure will get us to a specific observed failure.  It is an excellent tool to structure your thinking when you need to see exactly what could possibley have caused the failure we are investigating.

Too often, we seem to focus only on the material failures.  The fault tree will have items such as “Relief Valve Fails”, Vessel Wall Fatigue Failure”, “Overpressure”, “Power Supply Fails.”  This is very comfortable, because it is only a piece of “stuff” that failed, and I can easily lay the blame for the failure on an inanimate object.  The fault tree will use the basic event (or equivalent) symbol, signifying that we need look no deeper than this event.

The more realistic investigator may add in a set of events that include “Human Error” into the mix.  More often than not, however, these events are catagorized as Incomplete Events, or those that we just don’t have enough information to further develop.  It is easier to just leave these events on our fault trees as incomplete, and we just accept that the human error is just going to occur.  After all, I can’t replace the human like I can a part.  And parts don’t get their feelings hurt or complain about the result!

Yet, deep down we know (and studies have proven over and over again) that these “human errors” are at the root of over 90% of equipment failures.  Therefore, although our fault trees may eventually get you to the point of discovering what part or condition contributed to the final failure, we still never seem to get to the bottom of 90% of our failures.

It is important that, when conducting a fault tree analysis, we include and run down the human errors that lead to the failure conditions.  The failure conditions that we discover should be considered Causal Factors (“Relief Valve did not lift”), and then a proper root cause analysis can be conducted on the reasons why the relief valve did not lift.  Use Equifactor® to help populate your fault trees.  Then take the results of your fault tree, plug them into your SnapCharT®, and finish your investigation.  Using the rest of the TapRooT® system to assist in your equipment troubleshooting process, you will get much further beyond where the fault tree drops you.

90 Die in Ukraine Mine Accident

Wednesday, November 21st, 2007

AFP reports on a mining disaster in the Ukraine. 90 have been confirmed dead and 10 are still missing. For the complete story see:
http://afp.google.com/article/ALeqM5jnxMxWdxKy4XLFaGpSw6Z9LKOYZQ

Picture 5

The UK RAIB Releases Two Accident Investigation Reports

Wednesday, November 21st, 2007

Click on the links below to download the investigation reports:

Derailment of Freight Train at Washwood Heath

Incident at Wellesley Roaf on Croydon Tramlink

Plaintiff Lawyer Objects to BP Texas City Criminal Settlement - Asks Court to Raise Fine to $1 Billion

Wednesday, November 21st, 2007

Don Perry, who represents 12 people injured in the Texas City Refinery explosion, has filed a motion in federal court objecting to the proposed settlement between the government and BP.

The hearing on the plea and settlement is set for the Tuesday after Thanksgiving.

For more info see:

http://www.chron.com/disp/story.mpl/business/5319044.html

Job Opening - Aberdeenshire, UK - Aerospace Continuous Improvement Engineer - Root Cause Analysis Skills Needed

Wednesday, November 21st, 2007

Woking within a team in an aircraft assembly environment, the candidate will be accountable and responsible for the timely delivery of projects that directly contribute to 2007 cost reduction targets through the elimination of non conformance. The applicant will be focussed on the resolution of assembly problems, often of a complex nature. The candidate will be responsible for data gathering, analysis, and identification of root cause and embodiment of the corrective actions. The individual will be expected to lead/facilitate cross-functional problem solving teams. The candidate will also be responsible for supporting Continuous Improvement activities. The candidate will ensure the manufacturing cell compliance with Company procedures and work instructions, also to JAR 21G, JAR 145, and environmental compliance through ISO 14001 AND 18001.

Key Skills / Knowledge Required (MUST HAVE) · Problem resolution, Complex problem solving skills, Project management, Lean manufacturing fundamentals. Working within a 19001 quality environment Display a pro - active approach and demonstrate the ability to work unsupported. · Microsoft Office, effective communication, team working

For more info see:

http://www.thecareerengineer.com/cand-viewjob.php?jid=260161