Downloaded from https://www.everyspec.com AMC, • 'W"6 e, Failure classification f. Fault isolation code (identifies hard- reoorttced information that relate to faill ware levels to which eich failure can be at- urea (ie,, failure report number, failure tributed) classification, include-excludecriteria, fault isolation code, and referenced failure re- g, Timer number (identifies the time port numbers), meter from which data were obtained). The failure status reports form the basis 4. Reference Information: of the failure summary, A description of the failure, conclusions based on the analy- a.
Date of entry (date information sea, and the corrective action recommended reaches file) or taken should be added to'the status re- port to form the summary, A sample sheet b. Test report number (references the from a failure status report is shown in test from which the record was generated) Fig. 5-12. h . Failure report number (references "A4.5 HARDWARE SUMMARIES a higher level failure report) d. Project codes (identifies data used The hardware summary report should con. from other programs). tain an entry for each hardware tested, con- slating of the total test time and failures The historic test result file permits a accumulated.
This report can be used in wide variety of reports to be prepared. For logistical planning, example, by using a control on date of test, reports containing data generated over any The hardware summary report can be desired range of dates can be prepared. Use expanded to include failure rates of items of a control on level of test permits re- required for early spares provisioning esti- ports containing only subsystem data or mates, if these items are not incl•ded in any desired combination of subsystem, the reliability measurement plan. equipment, or component data to be pre- pared. Use of a control on test type per.
5-4.6 FAILURE ANALYSIS FOLLOW- mits reports to be generated which elimin- UP REPORTS ate engineering development and acceptance screening tests or which use only field data. A failure analysis follow-up report A properly structured historic test result should be issued periodically for internal file permits reporting and analysis of any action. This report should list every item desired combination of the stored data.
which requires further action and its status, 5-4.4 FAILURE STATUS REPORTS 5-4.7 FAILURE RATE COMPENDIA The purpose of the failure status report Perhaps the most valuable byproduct of Is to maintain an historical record of all the reliability test program Is the failure failures, The report contains an entry for rate compendium which is a compilation anvO each failure. The equipment identification summary of the hardware test results con.
and test description from the historical tained on the historic test result file, The file should be provided in this report along data from all projects should be summarized with those portions of the test results and by hardware groupinp to provide a refer- ". .- . . ..' . ,. .