Safety analysis, delivered

Hundreds of hours of safety analysis. Done in ten.

sev10 delivers DFMEAs, FMEDAs and HARAs for automotive hardware. Our AI engine drafts every failure chain from your design data, and a hardware engineer reviews every line. You get a finished, review-ready package at a fixed price, in days.

783DFMEA failure chains
484FMEDA rows across 6 safety goals
56open questions logged, none hidden
~10 hof engineer time, start to finish

The same package. A tenth of the time.

A hardware safety package like the one below takes a traditional team hundreds of engineer-hours: building the structure tree, working through every part, rating every chain, then computing the metrics by hand. sev10's engine does the drafting. Our engineers put their hours into judgment.

What the AI does

  • Reads the schematic, BOM, layout and datasheets
  • Builds the structure and function trees
  • Drafts every failure mode, effect and cause, part by part
  • Rates S, O and D with a written rationale
  • Computes SPFM, LFM and PMHF, live in Excel

What the engineer does

  • Scopes the item and the safety goals with you
  • Reviews every row before it reaches you
  • Challenges the coverage claims and the failure-rate splits
  • Marks every assumption and logs every open question
  • Walks your team through the findings

Case study · Example package Rev A

Brake-by-wire corner ECU. 27 single-point faults, mapped to the part.

A full ISO 26262 hardware safety analysis of Texas Instruments’ TIDA-020106 electro-mechanical brake reference design (design guide), run as if for a client: HARA, DFMEA, FMEDA and a findings report for Quillon Motors, a fictional OEM. Every number on this page is computed from the delivered workbooks.

27 → 11single-point faults, as published → with sev10’s recommended actions
7hardware changes, ranked by what they buy on the metrics
765 → 23DFMEA chains at High action priority, before → after the actions (a reference design ships with no verification evidence, so nearly every chain starts High)

49 parts carry a single-point fault

Board map of the corner ECU, top and bottom, with every part coloured by its worst fault class across the safety goals as published.
  • Single-point fault: no safety mechanism
  • Residual: mechanism below 100 % coverage
  • Latent multiple-point fault only
  • No violating fault

What the analysis found

Single-point fault metric by safety goal

Scale 50–100 %. Outline: as published. Bar: with the actions. Red tick: ISO 26262-5 target for the goal’s ASIL. Results are provisional: TI’s IC-level FMEDA data is pending, so the metrics will move. TIDA-020106 is a lab reference design, not a safety-qualified product. The findings are gaps against assumed goals, not defects in TI’s intent.

Safety-mechanism rows from the FMEDA workbook: diagnostic-coverage cells shaded orange, tagged ASSUMED with a reason code and an open-question reference.
From the FMEDA workbook: diagnostic coverage per safety mechanism. Orange means assumed; the same row records why, and which open question closes it.

Every assumption marked. Every gap logged.

AI output you can’t check is worthless in a safety case. Every value we assumed rather than sourced is shaded orange in the workbook, tagged ASSUMED with a reason code, and traced to an open question. Nothing is buried in a footnote.

  • 56open questions, each tied to the rows it affects and who closes it
  • 51safety mechanisms, each with its ISO 26262-5 Annex D basis
  • 2scenarios in every metric: as published and with the actions
  • LiveExcel formulas. Change a failure rate, and every metric follows.

What lands in your inbox.

Editable source files in the formats your process expects, plus a report your program manager can read in ten minutes. This is exactly what the example package contains.

A page of the HARA: hazardous events rated for severity, exposure and controllability.

ISO 26262-3

HARA

Item definition, hazardous events rated S, E and C, and safety goals with ASILs, safe states and FTTIs.

16 pages · PDF and Word

DFMEA heat map: failure chains by circuit block and by the safety goal their effect violates.

AIAG-VDA

DFMEA

Every failure chain from structure to action, with S, O and D rationale, action priority, pivots and a dashboard.

783 chains · 23 tabs · Excel

FMEDA results chart: SPFM, LFM and PMHF per safety goal, as built and with the actions, against the targets.

ISO 26262-5

FMEDA

SPFM, LFM and PMHF per safety goal, live in Excel, with sensitivity cases and an assumptions register.

484 rows · 16 tabs · Excel and PDF

The cover of the hardware safety analysis report.

Findings report

Report

Findings ranked by effect, board fault maps for every goal, and the actions that close the gaps.

59 pages · PDF

Four steps. Fixed price.

  1. 01

    Scope

    Send the schematic, BOM, layout and whatever item definition you have. We come back with the scope, the assumed safety goals and a fixed price.

  2. 02

    Analyze

    The engine drafts the HARA, DFMEA and FMEDA from your data. An engineer reviews every row, challenges every coverage claim and marks every assumption.

  3. 03

    Review

    We walk your engineers through the findings, then revise the package against their answers to the open questions.

  4. 04

    Handover

    You own editable workbooks in your templates, ready for your safety manager, your customer and your assessor.

Straight answers.

What do you need from us?

A schematic, a BOM and ideally the layout. Datasheets we fetch ourselves. Item definition, safety goals and a mission profile help, but they aren’t required: where you have gaps, we assume, mark it and log the question.

Is the output certified or approved?

No, and nobody honest will tell you theirs is. We deliver a reviewed engineering analysis. Your safety manager approves it and your assessor confirms it. We make both of those steps fast.

Where does our design data go?

Your data is used only for your analysis, under NDA. If it can’t leave your building, we can deploy the engine inside your environment instead.

Can it match our templates?

Yes. AIAG-VDA and ISO 26262 structures by default. Your own templates, IDs and rating tables on request.

How long does it take?

The example package took about 10 hours of engineer time over 3 days. Scope decides the rest. You get a firm date with the fixed price.

Take the whole package.

The complete example: a one-page summary, the 59-page findings report, the HARA, and the DFMEA and FMEDA workbooks with live formulas. Open it, poke at it, send it to your safety manager.

Download the package (zip, 9 MB)
  • 00 One-page summary
  • 01 Hardware safety analysis report
  • 02 HARA
  • 03 DFMEA workbook
  • 04 FMEDA workbook and PDF
The one-page summary that opens the package: the board fault map, headline numbers, findings and SPFM by goal.

Your subsystem is next.

Tell us what it is, which analysis you need and when your review is. We’ll come back with a scope and a fixed price.

Start a project

walshf@oregonstate.edu