Everyspec (implied, based on the URL) AMC PAMPHLET 31a, AMCP 706.198 — Everyspec AMC PAMPHLET 31a: US Army Reliability Development Guide for Military Equipment (PDF)

Downloaded from https://www.everyspec.com AMCP 70-1 sign decisions, Later, when the system be- Once a suitable organizationa] structure for comes, operational, the data system can be data has been determined, a corresponding used by the Army to collect field reliability address structure must also be devised so data (if so desired) which will provide the that an address is available to designate uni- basis for system modifications and changes quely any category in the organizational in maintenance and supply concepts, The hierarchy, DA operates several data banks; see Part Two, App. B for a listing of' somc of the The data elements to be stored in the sys- data bank/retrieval systems.

The policy tern must be carefully defined and structured in regard to data banks changes occasionally. prior to establishing the files, A typival data Check the latest directives in this regard, element structure is given in Table 5-I (Ref, 3), This is suitable only for testing up to, 5r2 STRUCTURE OF A RELIABILITY hut not inc!udlng, ordinary field use, Stan- DATA SYSTEM dard DA procedures are to be used for field failure reporting (Refs. 1, 2). A reliability data system consists of a data bank, a set of computer programs, and Ts computer hardware. The data bank is a sys.

reliability data to be organized by system, tematic sct of data describing the reliability subsystem, assembly, subassembly, and low- characteristics of selected component parts est replaceable unit. A numerical coding and subsystems as well as the system as a scheme should be developed which permits whole, The information in the data bank the system hierarchical structure to be des- can be made available in printed form in a cubed. variety of formats, tusing report generator programs, The information in the data bank The coding system also must permit fail.

ure modes and test environments to be des- also can be manipulated to produce reports crmbede All environmental factors to be required by systems management and en. ce nuering perbontin, flit use of a single uni- applied during the reliability and environ- fled data base simplifies the problems of file mental tests, as well as those factors expect- ed to be encounterLd in the field, must be searching, report generation, and adding new data. included in the system, Fig. 5-1 (Rol'. 4) shows a typical computer printout sum- In this paragraph, the following areas will marizing a typical set of environmental be discussed: (I) organizing and addressing factors.

As the project progresqes, thin list data, and data format, (2) programs for data can be expanded% bank establishment and updating, (3) ex- The data formats most suitable for com- traction routines, and (4) data bank oper- ation, puter manipulation may not coincide with formats that are easy for the test engineers to use: therefore, tile formats for data entry 5-2.1 ORGANIZING AND ADDRESSING may bc somewhat different than those used DATA by test engineers. The way in which data reformatting is accomplished depends on the The information in the data bank must be system.

For example, one approach is to organized in a systematic manner, so that it reorganize the data when entering it onto is uniquely addressable and readily accessible. data-entry coding forms. Or, the data can Th,, information retrieval programs should be entered directly from test forms (after permit standard reports to be generated and error checking) to be reformatted by the "specific questions to be answered on query. computer. ", 0,., I Mil I 0 ..