MIL-STD-962C
20 October 1995
________________________
SUPERSEDING
MIL-STD-962B
20 May 1988
DEPARTMENT OF DEFENSE
STANDARD PRACTICE
DEFENSE STANDARDS AND HANDBOOKS
AMSC D7124 AREA SDMP
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
File | MIME type | Size (KB) | Language | Download | |
---|---|---|---|---|---|
MIL_STD_962CDefStds_Hdbks.pdf | application/pdf | 272.12 KB | English | DOWNLOAD! |
Provides definitions
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.
[..]