How to Generate DFMEA from KiCad Schematics with EXITON

Why KiCad Users Need DFMEA

You've designed a circuit in KiCad. Schematic is clean. BOM is correct. Layout is done.

Then comes the quality requirement: DFMEA.

If you're an IoT startup, a freelance designer, or even a hardware engineer at a startup, you know the gap: KiCad doesn't talk to FMEA tools. You're left copying components into Excel, hunting datasheets, assigning failure modes by hand, manually formatting a DFMEA sheet that should have been generated automatically.

This tutorial shows you how to close that gap.

Using EXITON FMEA, you'll go from KiCad schematic to structured DFMEA in minutes, not days — with a deterministic database (not AI hallucination), built-in quality lint, and a draft that's ready for engineering review.

By the end of this tutorial, you'll understand how to prepare KiCad files, import them into EXITON FMEA, assign failure modes, validate with quality lint, and export a compliant DFMEA spreadsheet.

What You Need to Get Started

Before you begin, gather these items:

• KiCad .kicad_sch file — Your schematic, exported from KiCad 6.0 or later
• BOM (CSV or XLSX format) — Component list, exported from KiCad. Must include: Reference (R1, C1, U1), Value, Footprint
• EXITON FMEA desktop app — Download from exiton.net. Available for macOS and Windows
• 5 minutes — Time to complete the basic workflow

Optional but recommended:

• Component datasheets (for reference during review)
• Prior FMEA documents (to understand your organization's failure mode patterns)

That's it. You don't need a database subscription, special software licenses, or an internet connection. Everything runs locally.

Step 1: Prepare Your KiCad Files

EXITON parses your KiCad schematic from the .kicad_sch S-expression file. This is a structured text format that KiCad uses internally to store schematic data.

What EXITON Extracts

From your .kicad_sch file, EXITON extracts:

• Component references (R1, R2, C1, U1, etc.)
• Component values (10k, 100µF, STM32L476, etc.)
• Footprints (0603, QFP64, etc.)
• Net connections (which pins connect to which nets)
• Hierarchical structure (if your design uses hierarchical sheets)

Hierarchical Sheet Support

If your schematic is split across multiple sheets (e.g., Power Sheet, Signal Sheet, Protection Sheet), EXITON handles this automatically. It parses all sheets, extracts all instances, and flattens them into a single DFMEA with fully-qualified component references.

Example: If your Power Sheet contains R1, and your Signal Sheet also contains R1, EXITON will track them as Power.R1 and Signal.R1 to avoid collision.

Export BOM from KiCad

In KiCad, generate your BOM from the schematic editor:

1. Open your schematic in KiCad Eeschema
2. Go to Tools → Generate BOM
3. Select the CSV or XLSX export format
4. Ensure these columns are included: Reference, Value, Footprint, Description (optional but recommended)
5. Export the file. Name it something like project_bom.csv

EXITON will read this BOM and cross-reference it with the schematic. If there are discrepancies (e.g., a component in the BOM is missing from the schematic), EXITON will flag these during import.

Clean Up Before Import

Recommended steps to avoid import issues:

• Remove placeholder or DNP (Do Not Populate) components from the BOM, or mark them clearly
• Ensure all component references are unique (no duplicate R1 or C1 across sheets without hierarchy prefix)
• Use consistent naming conventions (e.g., R1, R2, not R_1, R#2)
• Check that all components have a value and footprint assigned

Once your .kicad_sch and BOM files are ready, you're set for the next step.

Step 2: Import into EXITON FMEA

Launch EXITON FMEA on your desktop. You'll see a project creation dialog.

Create a New FMEA Project

Click New Project and fill in:

• Project name (e.g., "IoT Sensor Board v2.1")
• Description (optional, but helps organize later)
• KiCad schematic file (.kicad_sch) — click Browse and select your file
• BOM file (CSV or XLSX) — click Browse and select your BOM

Import & Component Classification

Once you click Import, EXITON will:

1. Parse the .kicad_sch file and extract all components
2. Cross-reference the BOM to validate component list
3. Classify each component into one of 15 standard categories (see below)
4. Display a summary: "Imported 62 components, 15 categories"

The 15 Component Categories

EXITON automatically categorizes components to determine which failure mode database entries apply:

If EXITON misclassifies a component, you can manually override the category before proceeding to failure mode assignment.

Step 3: Review Failure Mode Assignments

Once components are classified, EXITON assigns failure modes. This is the core of the DFMEA generation.

How Failure Modes Are Assigned

EXITON uses a deterministic database lookup, not AI generation. The database is based on the AIAG & VDA FMEA Handbook (1st Edition, 2019), the industry standard for automotive FMEA.

For each component category, the system returns all known failure modes. Example: A ceramic capacitor can fail by opening, shorting, or changing capacitance. Each failure mode has a predefined function, effect, and possible causes.

What a Failure Mode Row Looks Like

Each failure mode row in your DFMEA contains:

Your Job: Assign S/O/D Ratings

EXITON generates the failure mode, function, effect, and causes. You must assign the three critical ratings:

• Severity (S) — How severe is the effect if this failure occurs? (1–10, where 10 is catastrophic)
• Occurrence (O) — How likely is this failure to happen? (1–10, based on design robustness, component quality, your experience)
• Detection (D) — How likely is your current control to catch this failure before reaching the customer? (1–10)

RPN (Risk Priority Number) is calculated automatically: RPN = S × O × D. High RPN items require action plans.

This is where engineering judgment matters. EXITON cannot guess your system requirements or your company's risk tolerance. You decide.

Step 4: Run Quality Lint

Once you've assigned S/O/D ratings, click Validate to run EXITON's built-in quality lint checks.

What Lint Checks

EXITON's lint performs structural validation:

• Missing S/O/D ratings — Flags rows where you haven't assigned values
• Rating consistency — Detects potentially incorrect patterns (e.g., S=10 but O=1 and D=1, which may indicate missing controls)
• AP (Action Priority) validation — Checks if high-RPN items have associated action plans
• RPN calculation — Recalculates and validates all RPN values
• AP rating against AIAG & VDA lookup table — Validates that action priority assignments follow the 1,000-entry AIAG & VDA Handbook standard table
• Completeness checks — Ensures all required fields are filled (Function, Failure Mode, Effect, Cause, Controls, S, O, D)

Quality Score

EXITON assigns a Quality Score (0–100) based on the lint results:

• 90–100 — Excellent. All fields complete, no inconsistencies, action plans assigned
• 70–89 — Good. Minor gaps (e.g., missing action plans on a few high-RPN items)
• 50–69 — Fair. Moderate gaps (incomplete S/O/D ratings, some structural issues)
• Below 50 — Poor. Significant gaps. Review and revise before export

Common Findings

Typical lint warnings you might encounter:

• "Solder Joint FM-007 (open) has S=9, O=3, D=1 — RPN=27. Consider adding electrical continuity testing to reduce D."
• "Component R12 has no failure modes assigned. Check classification."
• "High-RPN row (RPN=240) requires an action plan before export."
• "Electrolytic Capacitor C5: FM-002 (short) has O=8 but current control is 'none'. Consider burn-in testing."

These warnings are suggestions, not blockers. You can override if you have engineering justification. But lint is your safety net — it catches oversights.

Step 5: Export DFMEA Excel

Once validation is complete, click Export to generate a DFMEA spreadsheet.

Output Format

EXITON exports a single Excel file (.xlsx) with multiple sheets:

• DFMEA — Main failure mode table (AIAG & VDA compliant format)
• Summary — Project metadata, quality score, lint results
• BOM — Component list with categories and classification
• Evidence — Traceability log (which rows came from DB, BOM, Schematic, or User input)
• Change History — Timestamp, who made what changes (if collaboration is enabled)

Column Structure in DFMEA Sheet

The main DFMEA sheet includes AIAG & VDA columns:

Evidence Source Tracking

Every row in your DFMEA is tagged with an Evidence Source, showing where that information came from:

• DB — From the EXITON failure mode database (deterministic lookup)
• BOM — From your component BOM (reference, value, footprint)
• Schematic — From KiCad schematic parsing (net connections, hierarchy)
• User — Manually entered or overridden by you during review

This traceability is critical for audit trails and design change management. When someone asks, "Where did this failure mode come from?" you have a verifiable answer.

Download and Share

Once exported, you can:

• Open in Excel or Google Sheets for further refinement
• Share with your cross-functional design review team (QA, Manufacturing, Product)
• Archive in your project management system (Jira, Confluence, DOORS, etc.)
• Use as a baseline for future design iterations

Step 6 (Optional): Validate with Q-gate

After you export your DFMEA, you have an optional next step: Cross-check it against your BOM using EXITON Q-gate.

Why Run Q-gate?

Q-gate is a separate tool that validates DFMEA-BOM alignment using 9 consistency rules:

• All BOM components are in the DFMEA
• No phantom DFMEA rows (components not in BOM)
• Component counts match
• Failure mode coverage is complete
• S/O/D ratings are within acceptable ranges
• Action priority alignment (high-RPN items have priority actions)
• No missing required fields
• Traceability is complete (Evidence Source not blank)
• Change history is logged

Running Q-gate after exporting your DFMEA from EXITON FMEA ensures you haven't missed anything before design review.

See the Q-gate product page for more details.

Tips for Better DFMEA Results

1. Clean Your BOM

Before import, remove or clearly mark DNP (Do Not Populate) components. Messy BOMs lead to import errors or missing components in your DFMEA.

2. Use Consistent Naming

Follow standard conventions: R1, R2 for resistors; C1, C2 for capacitors; U1, U2 for ICs. Avoid special characters or long descriptive names. This makes EXITON's component classification more reliable.

3. Review with Your Team

DFMEA is not a solo activity. Share the exported Excel with your QA engineer, manufacturing partner, and product manager. Their input on S/O/D ratings and action plans is invaluable.

4. Treat Output as a Draft

EXITON accelerates DFMEA creation, but the output is always a draft. You still need to:

• Validate failure modes against component datasheets
• Adjust S/O/D based on your application and risk tolerance
• Define action plans for high-RPN items
• Get cross-functional sign-off

5. Document Your Assumptions

In the DFMEA Summary sheet, capture your key assumptions (operating temperature, humidity, shock/vibration levels, expected field life, etc.). This helps reviewers and future engineers understand the DFMEA context.

6. Iterate

DFMEA is iterative. After design review, update the Excel with feedback, re-import into EXITON if needed, and re-export. Version control is your friend — keep dated copies of each DFMEA iteration.

Frequently Asked Questions