MIL-STD-962D
w/CHANGE 2
b. Whenever possible, DoD standards should be written in terms of performance requirements, stating what is required rather than how to achieve the requirement.
c. 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.
d. DoD standard practices should be developed when it is necessary to define consistent procedures on how to conduct technical or technical management functions. Standard practices should only be developed for functions that, at least some of the time, are obtained via contract from commercial firms. Procedures for functions performed only by DoD personnel should be covered by non-directive military handbooks or directive documents as regulations, directives, instructions, technical manuals, or standard operating procedures.
e. 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.
f. 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 a military-unique requirement.
g. The DoD discourages the development of manufacturing process standards. The concept of DoD manufacturing process standards is inconsistent with both Department's emphasis on using commercial processes and reliance on performance specifications that state desired outcomes rather than "how-to's." The role for DoD process standards is limited to situations where the DoD alone has the technological expertise to specify a military-unique process. If there is an advantage to establishing requirements for an industry-wide commercial process, a non-Government standard should be developed.
h. Standards should include application guidance to help users know when and how to use a document. Such guidance might include: (1) how to apply a document to different contract types and different program phases; (2) how to make use of any flexibility allowed by the standard; (3) lessons learned; (4) the extent of Government review and approval; and (5) the relationship between the standard and other related documents.
i. Standards should be structured to facilitate tailoring of requirements -- either to remove requirements that are not always needed or include requirements that may be needed under certain conditions.
iii
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business