The building blocks of qualitative FTA
The Top Event is the outcome being investigated—for example, a customer receives an assembly that does not function. Intermediate Events describe conditions that lead toward that outcome. Basic Events are the lower-level conditions the team can investigate. An Undeveloped Event can record a branch that is relevant but outside the available evidence or scope.
An OR gate means any one input can produce the parent event. An AND gate means all input conditions must occur together. That distinction makes FTA useful when a failure depends on interacting conditions rather than one simple linear sequence.
AND and OR example
A dispatch delay might occur if either an inventory record is wrong OR a required part has been allocated to another order. A technician visit could fail only when the part is unavailable AND no escalation occurs before dispatch. The tree makes these different claims visible so the team can compare them with transaction records, allocation history and communication evidence.
The diagram is still a model. Its Basic Events are investigation targets, not automatically proven causes. A team should test whether the predicted gate relationships fit actual cases and unaffected cases.
Qualitative versus quantitative FTA
Qhubio's Fault Tree Analysis Builder supports qualitative analysis: organizing event logic and investigating plausible paths. It does not calculate event probabilities, failure probabilities, minimal cut sets or reliability metrics. Do not infer quantitative reliability results from a qualitative diagram.
Quantitative FTA requires validated probability data, defined assumptions and an appropriate reliability-analysis method. When those conditions are not present, a qualitative tree can still make complex logic easier to discuss and test.
When FTA is useful
FTA is useful when the top event may result from several alternatives, combinations of events, system interfaces or safety/reliability conditions. It is less efficient than 5 Why for a straightforward causal chain and less natural than Fishbone when the team first needs broad idea generation.
Use Fishbone for broad cause-family exploration. Use FTA when the causal structure needs explicit AND/OR logic. FMEA remains a prospective risk-analysis method; FTA can be used to investigate a specific unwanted event.
FTA in a controlled investigation
FTA can support a complex D4 investigation, but it does not manage containment, corrective action effectiveness, prevention or closure. When the issue requires those controls and cross-functional ownership, use the 8D workspace around the analysis.
Use the method within the right level of control
For a complaint that needs containment, evidence, team ownership, corrective action, effectiveness verification and prevention, run the wider investigation in Qhubio 8D.