You have an idea.
riskforge chatbot: a guided LLM interview builds a valid FtaDSL file step by step (raw arch → +OIM/TLE → +IOM/S/O/D). Validator loop against mcsa; no LLM in the analysis substance.
Applied FuSa reduces effort and risk in functional safety — through highly specialised tools and targeted process and team development.
ISO 26262 · IEC 61508 · Automotive SPICE · IEC 62304 · DO-178C
Our tools are uncompromisingly practice-driven: built on decades of automotive FuSa experience, equipped with everything tool qualification and audits demand.
Wherever you start — with an idea, an architecture, or a finished source code base: all three paths converge into the same FtaDSL model file and then run through the same deterministic workflow.
riskforge chatbot: a guided LLM interview builds a valid FtaDSL file step by step (raw arch → +OIM/TLE → +IOM/S/O/D). Validator loop against mcsa; no LLM in the analysis substance.
rca-studio: an interactive browser studio with FtaDSL editor, live architecture canvas, fault tree, and cut-sets — deterministic, runs locally in the browser, no LLM in the analysis.
ai-sw-pl autonomously turns a repository into ASPICE-compliant specs (SYS.1/SYS.2) plus FtaDSL/FmeaDSL model files. A bridge from existing code to functional safety — without touching the code.
A guided chatbot interview builds the FtaDSL file step by step (raw arch → +OIM/TLE → +IOM/S/O/D). The LLM is the notation translator; the deterministic validator loop against mcsa keeps the analysis substance LLM-free.
Fully automated fault-tree analysis and minimal-cut-set computation from a structured architecture description (FtaDSL). Delivers cut-sets, failure rates, and KPIs — in seconds, not weeks.
Model-driven FMEA generation. From an architecture model with failure-mode annotations, fmea mechanically derives the full FMEA table — including effect propagation, RPN calculation, coverage check, and SPOF marking. The FMEA moderator shifts from spreadsheet jockey to model curator.
A structured interview walks through the ISO-26262 requirements and produces a Safety Case as a Markdown document — deterministic, auditable, download-ready. Interview currently in German.
GitHub Action for MISRA-C:2012 pre-audit checks. One workflow file in your repo, and every push runs through the check — findings land as inline annotations in your pull request, as a job summary in the action tab, optionally as SARIF in the security tab. csa26 is a pre-audit tool: it finds rule violations, but does not replace formal compliance assessment. v1 checks a deliberately curated subset of 20 FuSa-relevant MISRA rules.
Authoring and review per ISO 26262, IEC 61508, and IEC 62304. From HARA via FSR to TSR.
Quantitative FTA, common-cause analyses, and cut-set evaluation — supported by MCSA.
Preparation for external assessments. Gap analysis, process design, traceability build-up.
Tool classification, TCL evaluation, and qualification reports per ISO 26262-8 Clause 11.
Independent assessment of existing system architectures from a reliability perspective.
Personal mentoring for engineers entering the field of functional safety.
Compliance is the evidence, not the goal. The goal is functional safety.
Whether MCSA access, a consulting request, or beta access to the Safety Case Generator — write to us directly. We typically respond within one business day.
Wolfgang Freese · Overath (Germany) · Response time typically < 24 h on business days