Using the Diagram
Now that you’ve downloaded the fault tree diagram, let’s use an example to see how a project team might use it.
For our purposes, let’s say our project is the development of a new alarm monitoring system; however, time and time again the alarm system turns off without warning.
Prompting Event – The event should be specific and clear. In our example we would simply write “alarm shuts off without warning.”
Faults – Through brainstorming, the Six Sigma team can offer up possible faults such as “power outages” or “wiring problems.” The fault tree diagram can have many faults and should be expanded beyond our two faults where needed and include as many possible faults as possible.
Root Cause – From brainstorming sessions, evaluation, testing and analysis, the project team assigns the root cause. Here, let’s say our root cause is “wiring problems.”
Countermeasures – In a fault tree diagram, a countermeasure is something the team reveals that can be done immediately to alleviate the problem prior to a total fix. Here, the team might come up with using the “alarm override system” as a countermeasure.
Solutions – Once the root cause of the alarm problem has been identified and a quick fix has been implemented as a countermeasure, the project team can then seek out solutions to fix the problem from happening again. The final solution fix may involve stakeholders such as the initial wiring schematics vendor, meaning contact, reevaluating and retesting of the wiring schematics could bring a swift fix. In our example, once the wiring schematics were reanalyzed and changed to work properly, the end of our fault tree diagram would list, “wiring schematics re-worked with vendor.”