NAVY MIL-HDBK-2165-1995 TESTABILITY HANDBOOK FOR SYSTEMS AND EQUIPMENT《系统和设备测试手册》.pdf

1、MIL-HDBK-2165 = 9999%70 0207224 bLB NOTE: HIL-STD-216% has been redesignated as a handbook. and is to be used for guidance purposes only. This document is no longer to be cited IS a requirement. For administrative expediency, the only physfcal change from HIL-STD.2165A is this cover page. However. t

2、his docwnt is ?KI langer to be clted as a requirement. If cited as a requirement, contractors my disregard the requirenents of this docunent and interpret its contents only as guidance. l i NOT MEASUREMENT j SENSITIVE I MIL-HDBK-2165 31 Julv 1995 SUPERSEDING MIL-STD-2165A O1 February 1993 DEPARTMENT

3、 OF DEFENSE TESTABILITY HANDBOOK FOR SYSTEMS AND EQUIPMENT AMSC No. N6742 AREA ATTS PISTRIBUTION STATEMENT R. Approved fui public release; distribution is unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-2165A FOREWORD 1. This milit

4、ary standard is approved for use by all Departments and Agemies of the Department of Defense. 2. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to: Commander, Naval Sea Systems Command, ATTN: SEA 0

5、5442, 2531 National Center Bldg. 3, Washington, DC 20362-5160 by using the self-addressed Standardization Document Improvement Proposal (DD Form 1426) appearing at the end of this document or by letter. 3. Testability addresses the extent to which a system or unit supports fault detection and fault

6、isolation in a confident, timely and cost-effective manner. The incorporation of adequate testability, including built-in test (BIT), requires early and systematic management attention to testability requirements, design and meesurement . 4. This standard prescribes a systematic approach to establis

7、hing and conducting a testability program. Included are: (a) Testability program planning (b) Testability reuiews (c) Diagnostic concepts and testability requirements (d) Inherent testability design and assessment (e) Test design and assessment. 5. This standard also prescribes the integration of th

8、ese testability program requirements with design and engineering functions, and with other closely related, interdisciplinary program requirements, such as reliability, maintain- ability and logistic support. 6. Five appendices are included to augment the tasks of this standard: (a) Appendix A provi

9、des guidance in the selection and application of testability program tasks and depicts the interface with other engineering and logistics disciplines. provides a measure of testability early in the design phase. (b) Appendix B describes the inherent testability assessment which (c) Appendix C provid

10、es a glossary of terms used in this standard. (d) Appendix D provides requirements for UUT compatibility with off- (e) Appendix E defines the System Synthesis Model (SSP!) input: date line ATE (applicable to Navy procurements only). sheets as they relate to the Consolidated Automated Support System

11、(CASS). 11 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-CONTENTS WaDh PAGE 1 . SCOPE . 1 1.1 Purpose 1 1.2 Application . 1 1.3 Tailoring of tasks 1 2 . APPLICABU DOCU“B 1 2.1.1 Specifications. standards. and handbooks . 1 2.2 Order of precedence 2

12、 2.1 Government documents . 1 3 . DEFINITIONS . 2 3.1 Definitions 2 3.2 Acronyms and abbr3viation.s . 2 4 . GENERAL REQUIREMENTS 2 4.2 Testability program requirements . 3 4.1 Scope of testability program . 2 4.3 Application of requirements 3 5 . DETAILED REQUIREMENTS . 3 5.1 Task descriptions 3 5.2

13、 Task integration . 3 6 . NOTES . 4 6.1 Intended use . 4 6.2 Issue of DODISS 4 6.3 Data requirements 4 6.4 Subject term (key word) listing 4 6.5 Changes from previous issue 5 TASK SECTIOfj 100 PROGRAM MONITOkING ASD CONTROL Task 101. Testability Program Planning . 7 Task 102, Testability Reviews 9 T

14、ASK SECTION ZOO - DESIGN AND ANALYSIS Task 201. Diagnostic Concepts and Testability Task 202, Inherent TesLability Design and Requirements . 12 Assessment . 14 Task 203, Test Design and Assessment . 16 APPENDIX i ii Provided by IHSNot for ResaleNo reproduction or networking permitted without license

15、 from IHS-,-,-1. SCOPE 1.1 Punose. This standard prescribes a uniform approach to testability program planning, establishment of diagnostic concepts and testability (including BIT) requirements, testability and test design and assessment, and requirements for conducting testability program reviews.

16、1.2 Application. This standard is applicable to the development of all types of components, equipments, and systems for the Department of Defense. Appropriate tasks of this standard are to be applied during the Conceptual phase, Demonstration and Validation phases, Full-scale Development phase and P

17、roduction phase of the system acquisition process. 1.3 Tailoring$. Tasks described are intended to be tailored to the particular needs of the system or equipment acquisition program. Application guidance and rationale for selecting and tailoring tasks are included in appendix A and the associated Te

18、stability Analysis Handbook. 2. APPLICABLE DOCUMENTS 2.1 Government documents. 2.1.1 Sms. The following specifi- cations, standards, and handbooks form a part of this document to the extent specified herein. Unless otherwise specified, the issues of these documents are those listed in the issue of t

19、he Department of Defense Index of Specifications and Standards (DODISS) and supplement thereto, cited in the solicitation (see 6.2). SPECIFICATION HILITARY MIL-H-46855 - Human Engineering Requirements for.Military Systems, Equipment and Facilities. STANDARDS XILITARY MIL-STD-470 - Maintainability Pr

20、ogram for Systems ment - Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-5.2 Task inteeratioq. The individual task requirements provide for integration with other specified engineering and management tasks to Frecluce duplication and overlap, while e

21、nsuring timely consideration and accomplishment of testability requirements. 6. NOTES (This section contains information of a general or explanatory nature that may be helpful, but is not mandatory.) 6.1 Jntended use. This standard is intended to prescribe a systematic approach to establishing and c

22、onducting a testability program for systems and equipments . 6.2 Jssue of DODISS. When this standarc! is used ir! acquisition, the app1icabl.e issue of the DODISS must be cited in the Solicitation (see 2.1.1). *. 6.3 Pata reauirements. The following Data Item Descriptions (DIDS) must be listed, as a

23、pplicable, on the Contract Data Requirements List (DD Form 1423) when this standard is applied on a contract, in order to obtain the data, except where DOD FAR Supplement 27.475-1 exempts the requirement far a DD Form 1423. Peference ParaeraDh DID Number DIDTit_le Suggested Tailoring Task 101.1 Task

24、 102.1 Task 201.4.1 Task 202.4.2 and 202 ,L. 4 Task 203.4.3, 203.4.4. and 203.4.6 DI-ATTS-81270 Testability program “_ , plan package DI-ATTS-81271 Testability require- “- ments analysis report DI-ATTS-81272 Inherent testability -“ design and assess- ment report assessment report DI - E-5423 Design

25、review data Equivalent DID may be used. Dl-ATTS-81273 Test design and “- Appendix D DI-ATTS-81291 Compatibility 50.2.1 Problem Report Aypendix 3 El - ATTS c 9 12 72 “UT Input/Output “ - JO. 3 Description The above DIDS were those cleared as of the date of this standard. The current issue of DoD 5Q10

26、.12-L, Acquisition Management Systems and Data Requirements Corrtrol List (AMSDL). must be researched to ensure that only current, cleared bIBs are cited on the DD Form 1423. 1. t Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MtL- STD-2165A Dagnost

27、ics Diagnostic requirements Di.agnosric testing Embedded test External test Fault detection Fault isolation Test assessment Test design 6.5 Chaqpw. Marginal notations are not used in this revision to identify changes with respect to the previous issue due to the extensiveness of the changes. Custodi

28、ans: Army - CR Navy - SH Air Force - 17 Preparing activity: Navy - SH (Project ATTS-8904) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-2165 E 9999978 0209232 794 II HIL-STD-2165A TASK SECTION 100 PROGRAM MONITORING AND CONTROL . 6 Provide

29、d by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TESTABXLITY PROGRAM PLANNING 101.1 PURPOSE. To plan for a testability program which will identify and integrate all restability and test design management tasks required to accomplish program requirements. as

30、specified in a testability program pian (see 6.3). 101.2 TASK DESCRIPTION. 101.2.1 Identify a single organizational element within the performing activity which has overall responsibility and authority for implementation of the testability program. Establish analyses and data interfaces among the or

31、ganiza- tional elements responsible for each of the elements of the diagnostic capability. 101.2.2 Establish a procedure by which testability requirements are based on mission needs and system performance requirements and are traceable throughout the design process and are integrated with other desi

32、gn requirements, and how these requirements are disseminated to design personnel and subcontractors. Establish controls for ensuring that each subcontractors testability practices are consistent with overall system or equipment requirements. 101.2.3 Identify testability design guides and analysis mo

33、dels and procedures to be imposed upon the design process. Flan for the review, verifica- tion, and utilization of testability data submissions. 101.2.4 Describe the approach to be used for establishing vertical test traceability to ensure compatibility of testing among all levels of testing, includ

34、ing factory testing. The approach must address both the compatibility of testing tolerances among levels and the compatibility of testing environments. 101.2.4.1 Describe the approach to be used to identify high-risk diagnostic technology applications and to provide procedures CO lower these risks.

35、101.2.A.2 Describe tne approach to be used io ensure integration and compatibility between testabilitv and other diagnostic elernenrs (that is, technical information, personnel, and training) and among all levels of main- tenance. 101.2.4.3 Define the means for demonstrating and validating that the

36、diagnostic capab11 ity meers specified requirement:, using maintainability demonstrations, rest progran verification, and other demonstration methods. Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NIL-HDBK-2LbS 9999970 0209234 5b7 MIL-STD-216SA 101

37、.2.4.5 Define an approach for the analysis of production and acceptance test and evaluation results to determine how BIT hardware and software, ATE hardware and software, and maintenance documentation performed as a means for satisfying production testing, as well as meeting testability requirements

38、. 101.2.4.6 Establish procedures to analyze maintenance actions for fielded systems to determine if the diagnostic capability is performing within specified requirements and take corrective measures. Define data collection requirements to conduct these analyses. Data collection shall be integrated w

39、ith similar data collection procedures, such as those for reliability and maintainability and logistic support analysis and shall be compatible with specified data systems in use by the military user organizations. 101.2.5 Develop a testability program plan which describes how the tes- tability prog

40、ram will be conducted. The plan must also include the time phasing of each task and relationships to other tasks. Diagnostic issues which relate to reliability, maintainability, logistics, human engineering, safety, and training shall also be addressed in those individuil plans. 101.3 TASK INPUT. 10

41、1.3.1 Identifications of each task which is required to be performed as part of the program.* 101.3.2 Identification of the time period over which each task is to be conducted. * 101.3.3 Identification of approval procedures for plan updates.* 101.3.4 Identification of deliverable data items.* 101.3

42、.5 Identification of items to be demonstrated.* 101.3.5.1 Identification of existing maintenance data collection systems in use by the using command. * 101.4 TASK. 101.4.1 Testability program plan if specified as a stand-alone plan. When required to he a part of another engineering or management pla

43、n, such as the Systems Engineering Management Plan (SEMP), use rhe appropriate, specified DID. * To be specified by the requiring authority 8 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MlL-STD-2165A TASK 102 TESTABILITY REVIEWS 102.1 PURPOSE. To

44、 establish a requirement for the performing activity to (1) provide for all official review of testability design information in a timely and controlled manner, and (2) conduct in-process testability design reviews at specified dates to ensure that the program is proceeding in accordance with the co

45、ntract requirements and program plans (see 6.3). 102.2 TASK DESCRIPTION. 102.2.1 Include the formal review and assessment of the testability program as an integral part of each system program review (such as system design review, preliminary design review, critical design review, etc.) specified by

46、the contract. Reviews shall cover all pertinent aspects of the testability program such as: (a) Status and results of testability-related tasks. (b) Documentation of task results. (c) Testability-related requirements in specifications. (d) Testability design, cost, or schedule problems. 102.2.2 Cond

47、uct and document testability design reviews with performing activity personnel, subcontractors, and suppliers. Coordinate and conduct these reviews in conjunction with reliability, maintainability, and logistic support reviews whenever possible. Inform the requiring authority in advance of each revi

48、ew. Utilize MIL-STD-1521 and program review criteria contained in MIL-STD-470, MIL-STD-785, and MIL-Sm-1388-1. Design reviews shall cover all pertinent aspects of the design, such as the following: (a) Review the impact of the selected diagnostic concept on readiness, (b) Review performance monitori

49、ng, built-in test, off-line test t:ic CSUI-S, required at t!dCil 1t2Vc.l i 31JlrltetlhlCi (1) A dct.ermination of the sensitivity of life cycle costs to varia- 12 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MlL-STD-2165A (d) An estimetion of risk associated with each concept. 201.2.4 Recommend system-level fault detectio