DRBFM vs FMEA: When Change-Point Analysis Beats a Full Re-Rate
You swapped one connector supplier on a wiring harness that has run clean for three years. Now the fork: do you re-open the 200-line DFMEA and re-rate the whole thing, or run a focused analysis on just the change? Re-rating everything is theater — the team rubber-stamps 195 lines that did not move to get to the five that did. But missing the interaction the new connector introduced is the field failure. Design Review Based on Failure Mode (DRBFM) was built for exactly this decision. Knowing when it beats a full re-rate keeps your analysis effort pointed at real risk.
What DRBFM is, briefly
DRBFM was developed by Tatsuhiko Yoshimura with Toyota as part of the GD3 philosophy — Good Design, Good Discussion, Good Dissection. Its premise is that failures cluster around changes to an otherwise proven design, so the analysis should concentrate on the change points and the concerns they raise rather than re-examining the whole design. The worksheet is derived from the FMEA form but reorganized around what changed and what worries the engineers about it, and the method weights the structured engineering discussion (the design review) as heavily as the worksheet itself. It is a change-focused complement to FMEA, not a replacement for it.
The factors that decide the fork
Five questions settle almost every case. Is there a genuinely proven predecessor design with a sound baseline FMEA? How large is the change — one component, or a re-architecture? Does the change touch interfaces and interactions, or is it self-contained? Do you have the subject-matter experts available for a real review discussion? And does a customer or standard require the FMEA itself as a deliverable?
Path A — reach for DRBFM
Use DRBFM when the change is incremental and sits on top of a design with a solid baseline analysis. The method shines when you need to surface the concerns a change introduces — especially interactions with neighboring components that a line-by-line FMEA re-rate tends to gloss over — and when you have the cross-functional experts in the room to dissect those concerns. The connector swap above is the textbook case: proven baseline, contained change, real interaction risk at the mating interface.
Path B — run a full FMEA instead
Reach for a full FMEA — a new analysis or a complete re-rate — when there is no proven baseline to anchor against, when the change is too broad for the old baseline, or when the FMEA document itself is the required deliverable. A new platform, a first-of-kind process, or a redesign touching most of the bill of materials all fail the “proven predecessor” test. DRBFM then has nothing stable to compare the change against. And under IATF 16949, the customer expects the FMEA as the artifact — the AIAG-VDA FMEA handbook is the format auditors and OEMs look for; a DRBFM worksheet does not substitute for it in a PPAP package.
Path C — the answer is usually both
In a mature program the two are not exclusive. DRBFM works best as the front-end discussion that feeds the FMEA: you dissect the change points, surface new concerns, and then push those concerns back into the FMEA and the control plan as updated failure modes, causes, and controls. The DRBFM finds the risk the change introduced; the FMEA remains the living, auditable record. That hand-off is the same one you run on any engineering change — see updating your FMEA after a design change through the ECN workflow for the re-rating triggers and version-control side of it.
Summary
| Situation | Reach for |
|---|---|
| Incremental change on a proven design | DRBFM (then update the FMEA) |
| Interaction / interface risk from a change | DRBFM discussion |
| New design, no proven baseline | Full FMEA |
| Change so broad the baseline no longer applies | Full FMEA re-rate |
| Customer / IATF requires the FMEA deliverable | FMEA (DRBFM optional front-end) |
DRBFM also leans on a strong baseline to compare against, which is one more reason to keep foundation FMEAs and failure-mode libraries current — the better your proven baseline, the sharper the change-point dissection. The same discipline applies to how you write the new failure modes a DRBFM uncovers: keep them in the function-based verb-noun structure the rest of the DFMEA uses.
Close the loop in the FMEA
Whichever path you take, the risk numbers end up back in the FMEA. When a DRBFM surfaces a concern that warrants a new or re-rated failure chain, the RPN and Action Priority calculator turns the revised Severity, Occurrence, and Detection into the priority that decides whether the change ships. Run the focused analysis where the change is, then make sure the living document reflects what you found.