Root Cause Analysis

Investigations that find the real reason equipment failed or an incident happened: trigger levels, evidence and timelines, five whys, fishbone and fault trees, honest causal statements and corrective actions checked for effect.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Root Cause Analysis, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help you organise your own work. It does not replace your professional judgement, the rules of your regulator or professional body, your firm's policies, or advice from a qualified lawyer, accountant or other adviser. Where a law, code or standard applies, use the current official version for your country, and get qualified sign-off on regulated or safety-critical work.

What it installs.

1

Pillar

1

Area

50

Projects

206

Starter tasks

🔧 Engineering Practice

Root Cause Analysis

Finding why an engineering failure or incident happened: evidence gathering, timelines, five whys, fishbone and fault tree methods, and corrective actions that stick.

  1. Investigation trigger criteria and RCA levels
  2. Investigation procedure and terms of reference
  3. First-hour evidence preservation kit
  4. Trained investigator and facilitator roster
  5. Investigation register and case numbering
  6. Site cause classification scheme
  7. Just culture ground rules for investigations
  8. Quality audit of the last 20 investigation reports
  9. RCA method selection guide
  10. Weekly corrective action status review
  11. Monthly investigation report peer review
  12. Effectiveness checks on closed actions
  13. Quarterly cause trend and repeat event analysis
  14. Weekly near miss and minor event triage
  15. Lessons learned bulletin
  16. Overdue action escalation route
  17. Investigation timeliness and quality metrics
  18. Annual RCA programme review
  19. Evidence store and retention housekeeping
  20. Interviewing witnesses after an incident
  21. Building a sequence of events timeline
  22. Five whys with evidence at every step
  23. Fishbone diagrams beyond brainstorming
  24. Fault tree analysis for a single top event
  25. Change analysis and barrier analysis
  26. Human factors in investigations
  27. Writing causal statements and reports
  28. Physical failure evidence basics
  29. Choosing RCA software or a structured workbook
  30. Corrective actions that change the system
  31. External failure analysis laboratory arrangement
  32. Reopening shallow operator error investigations
  33. Rules for reopening a closed investigation
  34. Feeding RCA actions into work and change systems
  35. Historian and alarm data extraction for investigations
  36. First 72 hours of a major incident investigation
  37. Facilitating a two-day team RCA workshop
  38. Presenting findings to the leadership team
  39. Regulator or insurer review of an investigation
  40. Joint investigation with a vendor or contractor
  41. Your first investigation as a new lead
  42. Sponsoring an investigation as a manager
  43. Investigating when you were involved
  44. Lean RCA for a small site or team
  45. Supporting the affected team after a serious event
  46. Organisational and latent cause analysis
  47. Common cause review across sites
  48. Intermittent and no-fault-found failures
  49. Kepner-Tregoe style problem specification
  50. Systems-theoretic analysis with STAMP and CAST

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Investigation trigger criteria and RCA levels

Without written triggers, investigations happen when someone senior is annoyed and skip the quiet repeat failures that cost the most. A short matrix that maps event severity, potential severity and repetition to three investigation levels (a single-person five whys, a facilitated team RCA, a full independent investigation) tells everyone what gets looked at and how hard.

First tasks

  • List the last twelve months of incidents and failures and the depth each got
  • Draft three investigation levels with method, team and time limit
  • Write severity, potential severity and repeat-event triggers for each level
  • Take the matrix to the leadership meeting for approval
  • Recheck the trigger matrix against the year's events @recurring(yearly)

Investigation procedure and terms of reference

Most weak investigations go wrong in the first hour, when nobody agrees what is in scope, who leads or who the report goes to. A procedure with a one-page terms of reference form fixes the scope, lead investigator, team, sponsor, deadline and the questions to answer before anyone starts asking why.

First tasks

  • Collect the current incident procedure and two recent investigation reports
  • Ask the agent to draft a one-page terms of reference form from the procedure
  • Write the sponsor, lead and action owner roles in plain sentences
  • Trial the form on the coming level two investigation and note the gaps

First-hour evidence preservation kit

Fragile evidence disappears fast: a gasket thrown in the skip, a valve reset, a historian buffer overwritten, a witness who goes home and talks it over. A packed kit and a one-page first-hour checklist let the first responder on shift photograph, tag, quarantine and record before the clean-up starts.

First tasks

  • Write the first-hour checklist in order of how fast each type of evidence decays
  • Buy tags, bags, scale rulers and a camera for the kit
  • Agree with the control systems team how to freeze historian and alarm data
  • Brief each shift supervisor on the kit at their next handover
  • Check the kit is complete and the camera is charged @recurring(monthly:3)

Make it yours.

Install Root Cause Analysis, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.