A high percentage of defense systems fail to meet their reliability requirements. This is a serious problem for the U.S. Department of Defense (DOD), as well as the nation. Those systems are not only less likely to successfully carry out their intended missions, but they also could endanger the lives of the operators. Furthermore, reliability failures discovered after deployment can result in costly and strategic delays and the need for expensive redesign, which often limits the tactical situations in which the system can be used. Finally, systems that fail to meet their reliability requirements are much more likely to need additional scheduled and unscheduled maintenance and to need more spare parts and possibly replacement systems, all of which can substantially increase the life-cycle costs of a system.
Beginning in 2008, DOD undertook a concerted effort to raise the priority of reliability through greater use of design for reliability techniques, reliability growth testing, and formal reliability growth modeling, by both the contractors and DOD units. To this end, handbooks, guidances, and formal memoranda were revised or newly issued to reduce the frequency of reliability deficiencies for defense systems in operational testing and the effects of those deficiencies. Reliability Growth evaluates these recent changes and, more generally, assesses how current DOD principles and practices could be modified to increase the likelihood that defense systems will satisfy their reliability requirements. This report examines changes to the reliability requirements for proposed systems; defines modern design and testing for reliability; discusses the contractor's role in reliability testing; and summarizes the current state of formal reliability growth modeling. The recommendations of Reliability Growth will improve the reliability of defense systems and protect the health of the valuable personnel who operate them.
National Research Council. 2015. Reliability Growth: Enhancing Defense System Reliability. Washington, DC: The National Academies Press. https://doi.org/10.17226/18987.
|2 Defense and Commercial System Development: A Comparison
|3 Reliability Metrics
|4 Reliability Growth Models
|5 System Design for Reliability
|6 Reliability Growth Through Testing
|7 Developmental Test and Evaluation
|8 Operational Test and Evaluation
|9 Software Reliability Growth
|10 Conclusions and Recommendations
|Appendix A: Recommendations of Previous Relevant Reports of the Committee on National Statistics
|Appendix B: Workshop Agenda
|Appendix C: Recent DoD Efforts to Enhance System Reliability in Development
|Appendix D: Critique of MIL-HDBK-217--Anto Peter, Diganta Das, and Michael Pecht
|Appendix E: Biographical Sketches of Panel Members and Staff
|Committee on National Statistics
The Chapter Skim search tool presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter. You may select key terms to highlight them within pages of each chapter.
The National Academies Press (NAP) has partnered with Copyright Clearance Center's Marketplace service to offer you a variety of options for reusing NAP content. Through Marketplace, you may request permission to reprint NAP content in another publication, course pack, secure website, or other media. Marketplace allows you to instantly obtain permission, pay related fees, and print a license directly from the NAP website. The complete terms and conditions of your reuse license can be found in the license agreement that will be made available to you during the online order process. To request permission through Marketplace you are required to create an account by filling out a simple online form. The following list describes license reuses offered by the NAP through Marketplace:
Click here to obtain permission for the above reuses. If you have questions or comments concerning the Marketplace service, please contact:
US Toll Free +1.855.239.3415
To request permission to distribute a PDF, please contact our Customer Service Department at email@example.com.