DRBTR, Design Review Based on Test Results. It allows to document the tests, to take into account the effects for the customers and to determine if corrective actions are necessary.
Introduction
The DRBTR is used during the so-called “Good Dissection;” phases of the Mizenboushi principle. Its goal is to improve the interpretation of test results through documented collaborative work on the various causes of product failure..
Prepare validation reviews
From each cause of failure identified in Phase 2 “creative FMEA” DRBFM, we build a table of this form :
|
Cause of failure |
Priority |
Parts / Location) |
1. Test |
2. Test results |
3. Comparison with previous results |
|
| A, B, C | Engineer’s point of view | After exchange with the team | ||||
| … | ||||||
| … | ||||||
| … | ||||||
- For each cause of failure, we identify what we will test on our prototype. The method, means and evaluation criteria are defined.
- Once the tests are done, the interpretation will be done in two stages. First, the engineer in charge of the tests indicates his result at the end of the test. Then the results will be discussed in a group for a final interpretation.
- As a group, results will be compared to previous results to measure improvement.
Prepare design review
If our tests have been conclusive, we immediately move to DRBFM 4. If not, a new design review loop is performed (DRBFM 2/ DRBFM 3) using the support below which is following the previous table.
Thus, for each inconclusive test, new actions and associated tests are defined. We loop as many times as necessary until the results of our tests are conclusive.
|
Complementary action |
Responsible |
Date |
Test |
The whole point of the DRBTR is that the causes of failure identified during the « creative FMEA » du DRBFM e traced throughout the design / validation process and before production launch.
