Reliability Growth Enhancing Defense System Reliability (2015) / Chapter Skim
Currently Skimming:
Appendix C: Recent DoD Efforts to Enhance System Reliability in Development
Appendix C: Recent DoD Efforts to Enhance System Reliability in Development
Pages 185-202
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 185... ...
failed to include many newer methods, the Military Handbook: Reliability Prediction of Electronic Equipment (MIL-HDBK-217) became increasingly outdated, and in 1998 DoD cancelled Reliability Program for Systems and Equipment Development and Production (MIL-STD-785B)
|
From page 186... ...
i) : Contributors to reliability problems include: poor definition of reliability requirements, a lack of understanding by the developer on how the user will operate and maintain the system when fielded, lack of reliability incentives in contracting, and poor tracking of reliability growth during system development.
|
From page 187... ...
The report found that the use of reliability growth in development had been discontinued by DoD more than 15 years previously. It made several recommendations to the department regarding the defense acquisition process (p.
|
From page 188... ...
5 that declared materiel availability, a component of suitability that is a function of reliability, a "key performance parameter." RELIABILITY IMPROVEMENT WORKING GROUP Also in 2008, DOT&E established a Reliability Improvement Working Group, with three goals: ensuring that each DoD acquisition program incorporates a viable systems engineering strategy, including a RAM growth program; promoting the reconstitution of cadres of experienced test and evaluation and RAM personnel across government organizations; and implementing mandated integrated developmental and operational testing, including the sharing of and access to all appropriate contractor and 3 The TEMP is the high-level "basic planning document for all life cycle Test and Evaluation (T&E) that are related to a particular system acquisition and is used by all decision bodies in planning, reviewing, and approving T&E activity" (U.S.
|
From page 189... ...
identify reliability-critical items and areas where additional design or testing activities are required in order to achieve the reliability require ments. The system reliability model shall be updated whenever new fail ure modes are identified, failure definitions are updated, operational and environmental load estimates are revised, or design and manufacturing changes occur throughout the life cycle.
|
From page 190... ...
The contractor shall allocate the reliability requirements down to lower indenture levels and flow them and needed inputs down to its subcontractors/uppliers. The s contractor shall assess the reliability of the system periodically throughout the life cycle using the System Reliability Model, the lifecycle operational and environmental load estimates generated herein, and the failure defini tion and scoring criteria.
|
From page 191... ...
First, all major defense acquisition programs were to establish target goals for the metrics of materiel reliability and ownership costs. This was to be done through effective collaboration between the requirements and acquisition communities that balanced funding and schedule while ensuring
|
From page 192... ...
vi) For this policy guidance to be effective, the Services must incorporate formal requirements for early RAM planning into their regulations, and assure development programs for individual systems include reliability growth and reliability testing; ultimately, the systems have to prove them selves in operational testing.
|
From page 193... ...
The TechAmerica Engineering Bulletin Reliability Program Handbook, TA-HB-0009 was released and published in May 2013. On June 30, 2010, DOT&E issued a memorandum, "State of Reliability," which strongly argued that sustainment costs are often much more
|
From page 194... ...
The memo also stressed that reliability constraints must be "pushed as far to the left as possible," meaning that the earlier that design-related reliability problems are discovered, the less expensive it is to correct such problems, and the less impact there is on the completion of the system. Finally, the memo stated that all DoD acquisition contracts will require, at a minimum, the system engineering practices of ANSI/GEIA STD-0009 (Information Technology Association of America, 2008)
|
From page 195... ...
• Manage potential reliability risks due, for example, to new tech nologies or testing approaches. • Ensure that reliability allocations, monitoring provisions, and inputs that impact reliability (e.g., user and environmental loads)
|
From page 196... ...
The goal is to ensure the use of welldefined reliability engineering processes to develop, design, manufacture, and sustain the system/product so that it meets the user's reliability requirements and needs. This includes the initial conceptual reliability model of the system, quantitative reliability requirements for the system, initial reliability assessment, user and environmental life-cycle loads, failure definitions and scoring criteria, the reliability program plan, and the reliability requirements verification strategy.
|
From page 197... ...
For Objective 4, to monitor and assess user reliability, the ANSI/GEIASTD-0009 directs that RFPs mandate that proposals includes methods for which field performance can be used as feedback loops for system reliability improvement. DTM 11-003: Improving Reliability Analysis, Planning, Tracking, and Reporting As mentioned above, the deficiency in the reliability of fielded systems may at least be partially due to proposals that gave insufficient attention to plans for achieving reliability requirements, both initially and through testing.
|
From page 198... ...
A decision. This report provides a quantitative basis for reliability requirements and improves cost estimates and program planning.
|
From page 199... ...
PMs shall report the status of reliability objec tives and/or thresholds as part of the formal design review process, during Program Support Reviews, and during systems engineering technical reviews. RGC shall be employed to report reliability growth status at Defense Acquisition Executive System reviews.
|
From page 200... ...
How does one know when a prototype for a system is ready for operational testing? Although the TechAmerica Engineering Bulletin Reliability Program Handbook, TA-HB-0009,8 has been produced with the goal at least in part to answer these questions, a primary goal of this report is to assist in the provision of additional specificity as to how some of these steps should be carried out.
|
From page 201... ...
. Instruction, Operation of the Defense Acquisition Sys tem.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.