1、 MIL-STD-962D w/CHANGE 1 2 April 2008 SUPERSEDING NOT MEASUREMENT SENSITIVE MIL-STD-962D 1 August 2003 DEPARTMENT OF DEFENSE STANDARD PRACTICE DEFENSE STANDARDS FORMAT AND CONTENT AMSC D7504 AREA SDMPProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MI
2、L-STD-962D w/CHANGE 1 FOREWORD 1. This standard is approved for use by all Departments and Agencies of the Department of Defense (DoD). 2. This standard covers the format and content requirements for DoD standards, which include interface standards, standard practices, design criteria standards, tes
3、t method standards, and manufacturing process standards. The previous revision to MIL-STD-962 also covered the requirements for DoD handbooks. These have been removed from this standard and are now covered by MIL-STD-967. 3. The policies governing such procedural matters as authorization for documen
4、t development, coordination, comment resolution, indexing and distribution, application, and document maintenance can be found in DoD 4120.24-M, “Defense Standardization Program Policies and Procedures.” 4. This revision has resulted in many changes to standard format, but the most significant ones
5、are: a. Replacement of stand-alone change notices with changes integrated into the full standard. b. Limiting the number of changes for a specific issuance to a maximum of five before the document must be revised. c. Introduction of administrative notices to allow for nontechnical changes to be made
6、 quickly and without the need for coordination. d. Additional requirement to provide Internet addresses to contact organizations and obtain referenced documents. e. Elimination of the DD Form 1426. f. Replacement of the DoD Index of Specifications and Standards (DoDISS) with the Acquisition Streamli
7、ning and Standardization Information System (ASSIST) database. 5. Proper preparation and use of defense standards is a difficult task requiring careful analysis and good judgment. The following points are some helpful reminders to be considered when developing a standard: a. Before developing or rev
8、ising 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. iiProvided by IHSNot for R
9、esaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-962D w/CHANGE 1 b. 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
10、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 commercial and defense needs, a non-Government stan
11、dard 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. c. DoD interface standards should be develo
12、ped 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 standard
13、s 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 specify procedures on how to conduct non-manufacturing
14、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 such documents as regulations, directives, instructions, technical manu
15、als, 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 pr
16、imarily 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, nuclea
17、r 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 developm
18、ent of manufacturing process standards. The concept of DoD manufacturing process standards is inconsistent with both Departments emphasis on using commercial processes and reliance on performance specifications that state desired outcomes rather than “how-tos.” The role for DoD process standards is
19、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 guidan
20、ce to help users know when and how to use a document. Such guidance might include: (1) how to apply a document to different contract iiiProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-962D w/CHANGE 1 types and different program phases; (2) ho
21、w 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 req
22、uirements that are not always needed or include requirements that may be needed under certain conditions. 6. The figures appearing at the back of this standard are fictitious and are used only as examples to illustrate format. If there is any conflict between the text of the document and the figures
23、 at the end of this document, the text applies. 7. Comments, suggestions, or questions on this document should be addressed to the Defense Standardization Program Office (DSPO), ATTN: J-307, 8725 John J. Kingman Road, Stop 6233, Fort Belvoir, VA 22060-6233 or emailed to DSPOdla.mil. Since contact in
24、formation can change, you may want to verify the currency of this address information using the ASSIST Online database at http:/assist.daps.dla.mil. ivProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-962D w/CHANGE 1 SUMMARY OF CHANGE 1 MODIFIC
25、ATIONS 1. Changed the Uniform Resource Locator (URL) for the Acquisition Streamlining and Standardization Information System (ASSIST) database throughout the document. 2. Deleted from the foreword the requirement to obtain a waiver to cite defense standards in solicitations and contracts. 3. Changed
26、 the order of precedence statement in section 2 to include the words “unless otherwise noted herein or in the contract” in the first sentence. Generally, a standard takes precedence over the documents referenced, but there can be occasions, such as a drawing, where the referenced document can take p
27、recedence over the standard as long as it is noted within the standard. 4. Added a definition for “supersede” in section 3. 5. Added a requirement to 5.4.3 for the preparing activity to obtain new document numbers using the Automated Document Number module in ASSIST. 6. Added a requirement in 5.4.4
28、to include the phrase “DRAFT DATED (DATE OF DRAFT) under the header of each page of a draft standard. 7. Added new 5.4.7.3 to authorize inclusion of reinstatement note on cancelled standards that are reinstated and updated simultaneously. 8. Added a requirement in 5.8.2.1.3 to cite the specific colo
29、r chip(s) number in section 2 when referencing FED-STD-595. Note that FED-STD-595 was not included as a reference in section 2 of this standard since it is not a requirement document. 9. Added a requirement for the change number to appear below the document identifier on every page of a standard bei
30、ng changed. 10. Added advisory note to figures 10, 11, and 13 through 16. 11. Incorporated Defense Standardization Program Policy Memorandum 08-1 as 5.19.3 and figures 12A and 12B to allow cancellation notices to cite either direct replacements or suggested replacements. 12. Incorporated Defense Sta
31、ndardization Program Policy Memorandum 08-3 in 4.6 and 5.19.6 and figure 17 to require unclassified administrative notices for classified standards. 13. Added a requirement in 5.19.7.6 that project numbers are not required for administrative notices. 14. The following modifications to MIL-STD-962D h
32、ave been made: vProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-962D w/CHANGE 1 PARAGRAPH MODIFICATION Foreword Changed 2.2.1 Changed 2.2.2 Changed 2.4 Changed 3.2 Changed 3.14 Changed 3.26.1 Aded 4.6 Changed 5.4.3 Changed 5.4.4 Changed 5.4.7
33、 Changed 5.4.7.1 Changed 5.4.7.3 Aded 5.4.7.2 Changed 5.5.2 Changed 5.8.2.1.2 Changed 5.8.2.1.3 Aded 5.8.4 Changed 5.12.4 Changed 5.12.10 Changed 5.13.8 Changed 5.18.3 Changed 5.18.4.2 Changed 5.19.3 Changed 5.19.6 Changed 5.19.7.6 Aded 6.3 Changed 6.6 Changed Figure 2 Changed Figure 5 Changed Figur
34、e 7 Changed Figure 9 Changed Figure 10 Changed Figure 11 Changed Figure 12 Deleted Figure 12A Aded Figure 12B Aded Figure 13 Changed Figure 14 Changed Figure 15 Changed Figure 16 Changed Figure 17 Aded Concluding material Changed viProvided by IHSNot for ResaleNo reproduction or networking permitted
35、 without license from IHS-,-,-MIL-STD-962D w/CHANGE 1 CONTENTS PARAGRAPH PAGE FOREWORD. ii SUMMARY OF CHANGE 1 MODIFICATIONS v 1. SCOPE 1 1.1 Scope. 1 2. APPLICABLE DOCUMENTS 1 2.1 General 1 2.2 Government documents 1 2.2.1 Specifications, standards, and handbooks 1 2.2.2 Other Government documents,
36、 drawings, andpublications 1 2.3 Non-Government publications. 2 2.4 Order of precedence. 3 3. DEFINITIONS 3 3.1 Acquisition Management Systems Control (AMSC) number 3 3.2 Acquisition Streamlining and Standardization InformationSystem (ASSIST). 3 3.3 Class. 3 3.4 Composition. 3 3.5 Coordinated standa
37、rd. 3 3.6 Data 3 3.7 Data Item Description (DID) 3 3.8 Department of Defense (DoD) standard 3 3.9 Design criteria standard 3 3.10 DoD Single Stock Point 4 3.11 Grade. 4 3.12 Inch-pound document. 4 3.13 Interface standard 4 3.14 International standardization agreement. 4 3.15 Limited-coordination sta
38、ndard 4 3.16 Manufacturing process standard. 4 3.17 Metric documents 4 3.18 Metric units. 5 3.19 Non-Government standard 5 3.20 Not measurement sensitive standard 5 3.21 Recovered material. 5 3.22 Recycled material 5 3.23 Soft conversion 5 3.24 Standard 5 viiProvided by IHSNot for ResaleNo reproduct
39、ion or networking permitted without license from IHS-,-,-MIL-STD-962D w/CHANGE 1 CONTENTS PARAGRAPH PAGE 3.25 Standard practice. 5 3.26.1 Supersedes. 5 3.26 Style 5 3.27 Tailoring. 5 3.28 Test method standard 6 3.29 Type 6 4. GENERAL REQUIREMENTS 6 4.1 General 6 4.2 Coverage. 6 4.2.1 Tailoring of re
40、quirements. 6 4.3 Data requirements. 6 4.4 Use of copyright or patent material 7 4.5 Contractual and administrative requirements. 7 4.6 Classified material 7 4.7 Text. 7 4.7.1 Grammar and style 7 4.7.2 Abbreviations 7 4.7.3 Acronyms 8 4.7.4 Symbols. 8 4.7.5 Proprietary names. 8 4.7.6 Commonly used w
41、ords and phrases. 8 4.8 Measurements. 9 4.9 Metric practices. 9 4.9.1 Metric units. 9 4.9.2 Dual dimensions 9 4.10 Paragraph numbering 10 4.11 Paragraph identification 10 4.12 Standard identifier. 10 4.13 Page number 10 4.14 Tables. 10 4.14.1 Table numbering 10 4.14.2 Table title. 10 4.14.3 Table fo
42、rmat. 11 4.14.4 Continuation of tables. 11 4.15 Figures. 11 4.15.1 Figure numbering 11 4.15.2 Figure title. 11 4.15.3 Continuation of figures. 11 4.16 Footnotes and notes 11 4.16.1 Footnotes to text. 11 viiiProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS
43、-,-,-MIL-STD-962D w/CHANGE 1 CONTENTS PARAGRAPH PAGE 4.16.2 Footnotes to tables 11 4.16.3 Notes to figures. 12 4.17 Foldouts. 12 4.18 Cross-reference. 12 4.19 References to other documents. 12 4.20 Approved document format 13 5. DETAILED REQUIREMENTS 13 5.1 General 13 5.2 Types of standards 13 5.2.1
44、 Interface standards 13 5.2.2 Design criteria standards. 13 5.2.3 Test method standards. 14 5.2.4 Standard practices 14 5.2.5 Manufacturing process standards 14 5.3 Organization of standards. 14 5.4 Self-cover 15 5.4.1 Heading. 15 5.4.2 Titling 15 5.4.3 Document identifiers. 15 5.4.3.1 Identificatio
45、n of coordinated standards. 15 5.4.3.2 Identification of limited-coordination standards. 16 5.4.4 Date of document 16 5.4.5 Measurement system identification 16 5.4.6 Superseding document indicator. 16 5.4.6.1 Superseding revisions 16 5.4.6.2 Superseding other documents 17 5.4.7 Inactivation and rea
46、ctivation note 18 5.4.7.1 Inactive for new design note 18 5.4.7.2 Reactivation note. 18 5.4.7.3 Reinstatement note 18 5.4.8 Designation of federal supply class (FSC), group (FSG), or area assignment. 18 5.4.9 AMSC number 18 5.4.10 Restriction statements. 19 5.5 Foreword. 19 5.5.1 Preambles 19 5.5.2 Contact information. 19 5.6 Contents page 19 5.7 Section 1 Scope 20 5.7.1 Scope. 20 ixProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-962D w/CHANGE 1 CONTENTS PARAGRAPH PAGE 5.7.2 Classification. 20 5.8 Section 2 Applicable Documents.
