View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations MORT Analysis |  Operations Barrier Analysis |  Knowledge Modeling Ontology Design Patterns |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Mehrere Tage bis Wochen | 2-4 h | 1-3 h pro Pattern | 15-30 min |
Participantsdifferent | 2-6 | 2-6 | 1-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Root cause notes, Countermeasures |
Tagsno overlap | Root causeSafetySystemicIncident | Root causeSafetyIncident | OntologyPatternsReuseSemanticModeling | Root causeIncidentLeanProblem solving |