Design Review Based on Failure Modes (DRBFM): Proactively Managing Engineering Change Risks

In today’s competitive automotive and industrial environment, preventing quality issues before they reach the customer is paramount. While Failure Mode and Effects Analysis (FMEA) is a cornerstone of risk assessment, it can sometimes be too broad to deeply investigate risks introduced by design changes. The Design Review Based on Failure Modes (DRBFM) methodology, formalized in SAE J2886, offers a powerful, focused approach that complements FMEA by zeroing in on engineering changes and their interfaces. This article explores the core principles, structured process, and best practices for leveraging DRBFM to drive quality improvement.

🛠️ The DRBFM Mindset — Success requires an open, inquisitive, and challenging culture. Adopt a “guilty until proven innocent” stance to surface deeper risks that standard reviews might miss.

What is DRBFM and Why Does It Matter?

DRBFM is a structured, team-based review that concentrates on modifications to a baseline design. It was developed by Toyota (originally part of the GD3 methodology) to proactively prevent problems by thoroughly examining each change point and its potential to disrupt product functions. Unlike FMEA, which systematically analyzes the entire product for single-cause failure modes, DRBFM drills deep into a few high-risk areas—the points where something has been altered. This targeted approach makes it highly efficient for change management, especially in complex systems where even a small modification can have cascading effects.

The purpose of SAE J2886 is to establish a common language and process so that both OEMs and suppliers can apply DRBFM consistently, reducing complexity across the supply chain. It is not a replacement for FMEA but a complementary tool that integrates into existing design and development workflows. By focusing on change points, interfaces, and the surrounding environment, DRBFM uncovers failure modes that might otherwise go undetected.

The Four Key Steps of the DRBFM Process

The DRBFM process is divided into four sequential steps, each building on the previous one to ensure thoroughness and action. A cross-functional team—including design, manufacturing, quality, and testing—participates throughout.

Step Description Key Activities
1. Preparation Define the baseline design, functions, and the scope of changes. Assemble the team and gather necessary documentation (drawings, specs, FMEAs). Identify change points, create awareness sheets (see Appendix A), and plan the review sessions.
2. Change Point FMEA For each change point, identify potential failure modes, effects, causes, and current controls. Use a structured worksheet to assess risk. Analyze functions, interfaces, and novelty; assign severity, occurrence, and detection rankings; prioritize actions.
3. Design Review Hold a facilitated meeting to review and challenge the Change Point FMEA. Encourage devil’s advocate thinking (ask “What else?”). Discuss risks, agree on mitigation actions, record decisions and assumptions, and update designs or plans.
4. Action Results and Feedback Ensure all action items are completed and verified. Document outcomes and feed lessons learned back into the design and FMEA processes. Track effectiveness, close out actions, and update standards or checklists.

Each step incorporates rigorous documentation. The Change Point Awareness Worksheet (Appendix A) is a critical starting tool that helps the team see the full scope of changes, including indirect effects on adjacent systems and manufacturing processes.

🔍 Common Pitfall: Using DRBFM as a substitute for FMEA rather than a complement. Both tools are needed—FMEA for broad coverage, DRBFM for deep exploration of change-related risks.

Best Practices for Effective DRBFM Implementation

To gain the maximum benefit from DRBFM, organizations should embrace the following principles:

  • Focus on changes, not the whole product. The power of DRBFM lies in its narrow scope—avoid the temptation to expand the review to the entire design.
  • Assemble the right cross-functional team. Include representatives from design, manufacturing, quality, service, and suppliers to get multiple perspectives.
  • Foster a culture of curiosity and humility. The best insights come when team members feel safe to challenge assumptions and ask naive questions. The “guilty until proven innocent” mindset is essential for preventing complacency.
  • Document everything. Capture assumptions, decisions, and rationale. This knowledge base becomes invaluable for future changes and audits.
  • Integrate with validation plans. Use the risks identified in DRBFM to influence testing and verification activities (e.g., Design Verification Plan & Report).

Engineering Design Insight: Adopting a “guilty until proven innocent” mentality is not about pessimism but about disciplined curiosity. It drives teams to proactively uncover hidden failure modes by asking “What else could go wrong?” until all reasonable risks are exposed and addressed.

Frequently Asked Questions

  1. How does DRBFM differ from FMEA? FMEA is a broad, systematic review of the entire product or process for potential failure modes with single causes. DRBFM is a targeted, deep dive into specific changes made to a baseline design. They are complementary—FMEA covers the baseline, while DRBFM focuses on the deltas.
  2. When during the product development cycle should DRBFM be performed? Ideally, as soon as a design change is proposed and before detailed design finalization. It can also be used during prototype phases and whenever a late change is introduced. Early application saves cost and rework.
  3. Who should participate in a DRBFM review? A cross-functional team is mandatory—at minimum design engineers, manufacturing engineers, quality engineers, and a facilitator. Depending on the change, include test engineers, service representatives, and suppliers.
  4. Is DRBFM only for the automotive industry? No. While it originated in automotive, SAE J2886 explicitly states it is applicable to non-automotive applications as well. Any industry that manages engineering changes can benefit from this disciplined process.

By implementing DRBFM as part of a comprehensive risk management strategy, engineering teams can dramatically reduce the likelihood of defects arising from design changes. The structured approach, combined with a proactive mindset, turns change—often a source of risk—into a controlled, quality-enhancing process. 🛠️

Leave a Reply

Your email address will not be published. Required fields are marked *