Downloaded from https://www.everyspec.com AMCP 706-196. The contents and format of reliability required reliability was demonstrated by status reports, which must be issued each hardware element. periodically throughout the program, should be discussed by the Army and the con- The composite reliability status report tractor to arrive at a mutually agreeable in Fig. 5-8 and the reliability status re- document. In many cases, reliability re- port supplement in Fig. 5-9 represent two ports pnerated by the contractor's normal useful formats for summarizing reliability procedures can be used by the Army with- status.
In the first report, failure rates, out modification, reliability indices, a-confldence levels, and mission information are summarized by 54.1 RELIABILITY STATUS REPORTS environmental test category for each hard- ware item tested. The reliability status report presents estimates of the reliability of each compon- ent, equipment, and subsystem; pinpoints 5-4.2 FAILURE SUMMARY REPORTS reliability problem areas; and discusses possible corrective actions. The failure summary report presents a complete record of all failures occurring on The reliability status report should con- a particular program. Making this report tain:
mandatory helps to ensure that failures are Identified and ,eported properly, that 1. A brief description of the subsystem important and repetitive failures are analy- and equipment operation, and mission zed in detail, that causes and modes of against which reliability is reported equipment failures are determined, and that corrective actions are developed. 2. The subsystem block diagram and reliability equation, or an equivalent fault Monthly failure summary reports should tree or cause-consequence chart contain the following information: 3. A summary of the sources of test 1. Hardware Identification - including data nomenclature, diawing number, serial number, vendors, and program code 4.
A table relating the current measured reliability and reliability requirements for 2. Test description - including test each hardware level type, environment, site or reporting activity, and date of test S. Growth curves that tabulate measured reliability versus time 3. Test results - including failure re- port number, failure classification, and 6. A discussion of reliability problem description of failure area, proposed corrective action, and the results of previous corrective action 4. Failure investigation analysis, in- cluding the corrective action recommended 7.
A tabulation of the failure rates and or taken reliability estimates at the component, equipment, and subsystem levels (see Fig. 5. Names of the responsible personnel. 5-7) A sample failure summary report is shown , 8. 1The s-confidence levels at which the in Fig. 5-10.