RCM++ DFR: Difference between revisions
Jump to navigation
Jump to search
Created page with '{{Template:NoSkin}} {| class="FCK__ShowTableBorders" border="0" cellspacing="0" cellpadding="0" align="center"; style="width:100%;" |- | valign="middle" align="left" bgcolor=EEEE…' |
No edit summary |
||
| Line 2: | Line 2: | ||
{| class="FCK__ShowTableBorders" border="0" cellspacing="0" cellpadding="0" align="center"; style="width:100%;" | {| class="FCK__ShowTableBorders" border="0" cellspacing="0" cellpadding="0" align="center"; style="width:100%;" | ||
|- | |- | ||
| valign="middle" align="left" bgcolor=EEEEEE|[[Image:Webnotesbanner- | | valign="middle" align="left" bgcolor=EEEEEE|[[Image:Webnotesbanner-RCM.png|center|195px]] | ||
|} | |} | ||
{| class="FCK__ShowTableBorders" border="0" cellspacing="1" cellpadding="1" | {| class="FCK__ShowTableBorders" border="0" cellspacing="1" cellpadding="1" | ||
Revision as of 05:23, 18 July 2012
 |
| Design for Reliability (DFR) |
|
Design for Reliability (DFR) is a process in which a series of reliability engineering practices are utilized early in a product's design and integrated into the entire product development cycle. It is widely understood that the cost of addressing reliability issues increases significantly as a product progresses through the development cycle (e.g., it is much more expensive to provide support for an unreliable product than it is to improve a product's design). Thus, the effective use of DFR can minimize the costs and maximize the benefits of producing a reliable product. |
Learn more from...
|
the help files... |
|
the theory textbook... |
|
related article(s)... |
|
use example(s)... |
