上传人:tempuser 文档编号:100152373 上传时间:2021-06-03 格式:PDF 页数:74 大小:204.19KB
返回 下载 相关 举报
第1页 / 共74页
第2页 / 共74页
第3页 / 共74页
第4页 / 共74页
第5页 / 共74页
NOT MEASUREMENT SENSITIVE MIL-STD-962C 20 October 1995 _ SUPERSEDING MIL-STD-962B 20 May 1988 DEPARTMENT OF DEFENSE STANDARD PRACTICE DEFENSE STANDARDS AND HANDBOOKS AMSC D7124AREA SDMP MIL-STD-962C ii FOREWORD 1. This standard is approved for use by all Departments and Agencies of the Department of Defense (DoD). 2. The DoD is committed to reducing costs, making greater use of commercial products and practices, and promoting the use of the latest technologies. Every effort must be made to ensure that the standardization documents used by the DoD foster these goals and do not act as barriers. Standardization documents provide a framework by which requirements are defined. They must allow for the various contractual circumstances and environments that exist, and must promote an atmosphere in which appropriate cost, benefit, and risk tradeoffs can be made. 3. This standard covers the content and format requirements for DoD standards and handbooks. Proper preparation and use of standardization documents is a difficult task requiring careful analysis and good judgment. The paragraphs below highlight areas of policy and intent to provide guidelines to assist in document development. 4. There are five types of DoD-prepared standards: interface standards, standard practices, design criteria standards, test method standards, and manufacturing process standards. Before developing or revising a DoD standard, consider using an existing non- Government standard. If a suitable non-Government standard is not available, consider working with industry on a technical committee of a non-Government standards body to develop a new standard or revise an existing one. If it is not practical to use a non- Government standard, consult the DoD Index of Specifications and Standards (DoDISS) to determine if an existing DoD standard could be used. Also, consider whether a standard, which is a requirements-type document, is needed or if a guidance handbook could suffice. If it is determined that a DoD standard is needed, follow the guidelines below: a. Do not develop standards that tell a contractor how to manage a program. It is not the policy of the DoD to create standard management approaches across all programs and all contractors. Contractors must be allowed the flexibility to manage programs in innovative ways that can improve quality, reduce costs, and introduce the latest technological advances. If a common management approach is likely to have applications across industry in meeting both commercial and defense needs, a non-Government standard should be developed. If the DoD has a need to know how a contractor proposes to manage certain program elements, a non-contractual handbook should be used to provide guidance to DoD personnel on how to collect this information during the solicitation. b. DoD interface standards should be developed to specify the physical, functional, or military operational environment interface characteristics of systems, subsystems, equipment, assemblies, components, items, or parts to permit interchangeability, interconnection, interoperability, compatibility, or communications. Non-Government standards should be used to the extent possible to specify interface requirements. DoD interface standards should only be developed to specify military-unique interface requirements. DoD interface standards MIL-STD-962C iii may be cited as solicitation requirements without need for a waiver by the Milestone Decision Authority. c. DoD standard practices should be developed when it is necessary to specify procedures on how to conduct non-manufacturing functions. Standard practices should only be developed for functions that, at least some of the time, are obtained via contract from private sector firms. Procedures for functions performed only by DoD personnel should be covered by such documents as regulations, directives, instructions, technical manuals, or standard operating procedures. DoD standard practices may be cited as solicitation requirements without need for a waiver by the Milestone Decision Authority. d. DoD design criteria standards should be developed to specify military-unique design or functional criteria that must be adhered to in the development of systems, subsystems, equipment, assemblies, components, items, or parts. These design criteria are not primarily related to requirements that affect interchangeability, interoperability, interconnection, compatibility, or communications. Adherence to these design criteria standards, however, will affect the manufacturing of a product. Some examples would include military-unique design selection, nuclear blast protection, safety requirements, and human factors requirements. A DoD design criteria standard requires the Milestone Decision Authoritys waiver to be cited as a solicitation requirement. e. Non-Government standards can usually be used to satisfy DoD requirements for test methods. A DoD test method standard should only be developed if it reflects

当前位置:首页 > 国外标准 > 美国军标MIL