Design Review Based on Failure Mode
||The topic of this article may not meet Wikipedia's general notability guideline. (May 2013)|
||It has been suggested that this article be merged into DFMEA. (Discuss) Proposed since May 2013.|
Design Review Based on Failure Mode (DRBFM) is a tool originally developed by the Toyota Motor Corporation. This tool was developed based on the philosophy that design problems occur when changes are made to existing engineering designs that have already been proven successful.
DRBFM Methodology was developed by Tatsuhiko Yoshimura, a Quality Expert and a professor at Japan's Kyushu University. Yoshimura knew that design problems occur when changes are made without the proper level of supporting documentation. Using the philosophy of Preventative Measures (Mizenboushi), he created his own philosophy of DRBFM. Dr. Tatsuhiko Yoshimura supported the development and usage of DRBFM at many companies. He believes companies that implement the usage of DRBFM will be a better company. He believes the implementation of DRBFM requires discipline and engagement of everyone to the one goal of adding value to the customer by meeting engineering functional requirements and customer expectations.
The Philosophy of DRBFM centers on three concepts:
- Good Design
- Good Discussion
- Good Dissection
The DRBFM methodology is now a recognized documented process by SAE (Society of Automotive Engineers)and soon to be by AIAG (Automotive Industry Action Group). SAE J2886 DRBFM Recommended Practice was published in 2013 and the AIAG DRBFM Document will be published in the second quarter of 2014. Bill Haughey is the chair of both the SAE and AIAG committees to ensure a consistent application of the DRBFM process within both documents.
The basis for reliability is not to change a design; therefore, Mr. Yoshimura believes that if a design changes, the change should occur in small increments. Disturbance to a design is caused by the discontinuity of implementing changes affecting the interfaces between parts and interactions between systems. The design should not be changed in two different places simultaneously, because making too many changes too fast has the potential to result in failures faster than our capacity to detect them. One key to successful change is to make changes visible. Dr. Tatsuhiko Yoshimura mentored many people in his methods defined in GD3. Bill Haughey, one of his students, completed an Ebook (published by SAE http://books.sae.org/book-pd251136) "Design Review Based on Failure Modes (DRBFM) and Design Review Based on Test Results (DRBTR) Process Guidebook." The book features process step by step details of the methods along with examples. Haughey (http://reliatrain.com) is currently the chair of an SAE committee developing a DRBFM recommended practice (J2886).
In discussions we should concentrate on the proposed changes to a design. If a proven good design is applied to future products, then the risk of failure is low; however, if changes are made to the existing design, then the probability of failure is increased.
Mr. Yoshimura advises individuals to work to understand the changes as opposed to trivializing them. He also advises that validation testing can help to identify design weaknesses; but, he also states that good discussions held at preliminary design reviews can achieve the same result. The good discussion that Mr. Yoshimura refers to here is also known as DRBFM (Design Review Based on Failure Modes).
The analysis for DRBFM is modeled after a linkage between a good design review and FMEA. A comprehensive, well-done FMEA can be considered one of the prerequisites (plus many other preparations sheets defined in the methodology) for a DRBFM; DRBFM is implemented when change occurs (design, process, supplier, etc.). The intent of the DRBFM http://reliatrain.com/drbfm/ ) is to make these changes visible by discussing them at length, as well as every possible concern for failure that may potentially occur - anything that impacts quality, cost or delivery.
The third part of the GD3 concept. One objective of a good design review is to examine the results of validation testing, making all product weaknesses visible. This examination involves applying another GD3 concept, Design Review Based on Test Results (DRBTR). When applying DRBTR, we must, wherever possible, observe the product test before, during and after completion. DRBTR looks for the validation (test) engineer to lead the review of a DRBTR review to exam the tested part and look for buds of problems that are about to happen (test failures are evident). DRBTR encourages the designer and test engineer to discuss potential problems (observations) or weaknesses from a cross functional multi-perspective approach, and to share this information. DRBTR has the designer observing actual test pieces and discussing test results in open discussions, such as design reviews. Furthermore, when dissecting test results, one must consider manufacturing variation, test profile and expected quality and reliability targets of the product. This process is defined in detail in Bill Haughey's Ebook (published by SAE http://books.sae.org/book-pd251136) "Design Review Based on Failure Modes (DRBFM) and Design Review Based on Test Results (DRBTR) Process Guidebook." The book features process step by step details of the methods along with examples.