FTA and FMEA — deterministic and standard-compliant.
From your architecture and failure model: fault tree (IEC 61025), FMEA, prioritized cut-sets, common-cause and report. Four ways to the model — editor, chat, source code or Simulink.
Deterministic engines — they compute, they don’t guess.
The problem
FTA and FMEA by hand are slow and error-prone.
Safety analyses live in spreadsheets and drawing tools today — hand-maintained, hard to keep current, barely reproducible.
01Every architecture change breaks the fault tree — maintenance eats weeks.
02Cut-sets, common-cause and prioritization are curated by hand and go stale.
03Reviews stumble over inconsistent tables instead of real safety questions.
The core
Four ways to the model, one deterministic analysis.
How you reach the model is your choice. What comes out the other end is always the same: a fault tree per IEC 61025 and an FMEA — computed, not guessed.
Write in the Studio Live
Author the model directly on the Studio canvas as FtaDSL/FmeaDSL — structured, versionable, instantly checkable.
Generate from prose Live
rfChat produces the DSLs from your description. You state the case in words, the model takes structured shape.
Recover from code Pilot
rfRecover reconstructs the model from your source code. In pilot today — the entry point for existing codebases.
From the Simulink model Live
Upload an .slx, pick the malfunction in chat — the architecture is read and turned into an FTA. Try it below.
all lead into FtaDSL / FmeaDSL → FTA + FMEA
Click a tile to start · „?“ for details
The target is the core: a fault tree (mcsa + fta-render) and an FMEA. The four ways are just how you get there.
What you get
Honestly staged: what ships today — and what’s coming.
Delivered — the FTA/FMEA core
Live
Real and live today.
→Fault tree per IEC 61025Symbology strictly per IEC 61025, as SVG and PDF — cleanly typeset, audit-ready.
→Prioritized cut-set listMinimal cut-sets, ordered by relevance.