View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Engineering Fault Isolation |  Operations Fault Tree Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 30 min Setup, dann laufend | 30-180 min | 2-6 h | 2-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-6 | 3-8 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | RiskTrackingStakeholdersGovernance | TroubleshootingDiagnosisEngineering | RiskRoot causeSafety | Root causeSafetyIncident |