1、 MIL-STD-961E w/CHANGE 1 2 April 2008 SUPERSEDING NOT MEASUREMENT SENSITIVE MIL-STD-961E 1 August 2003 DEPARTMENT OF DEFENSE STANDARD PRACTICE DEFENSE AND PROGRAM-UNIQUE SPECIFICATIONS FORMAT AND CONTENT AMSC D7500 AREA SDMP Provided by IHSNot for ResaleNo reproduction or networking permitted withou
2、t license from IHS-,-,-MIL-STD-961E w/CHANGE 1 F O R E W O R D 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 developing defense specifications, which are used on multiple progra
3、ms or applications, and program-unique specifications, which are used for a single program or system with little or no potential for use with other programs or systems. The policies governing such procedural matters as authorization for document development, coordination, comment resolution, indexin
4、g and distribution, application, and document maintenance can be found in DoD 4120.24-M, “Defense Standardization Program Policies and Procedures.” 3. This revision has resulted in many changes to specification format, but the most significant ones are: a. Replacement of “pen-and-ink” type amendment
5、s by amendments integrated into the full specification. b. Limiting the number of amendments 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 quickly and without the need for coord
6、ination. d. Additional requirement to provide Internet addresses to contact organizations and obtain referenced documents. e. Expansion of the maximum number of characters in a Part or Identifying Number (PIN) from 15 to 32 characters. f. Elimination of the distinction between associated specificati
7、ons and specification sheets. g. Allowance of a cover page for specifications under certain conditions. h. Allowance of a table of contents if a cover page is used. i. Elimination of the DD Form 1426. j. Replacement of the DoD Index of Specifications and Standards (DoDISS) with the Acquisition Strea
8、mlining and Standardization Information System (ASSIST) database. k. Integration of program-unique specification requirements previously covered by MIL-STD-490, which is canceled. iiProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-961E w/CHANG
9、E 1 4. The overall purpose of a specification is to provide a basis for obtaining a product or service that will satisfy a particular need at an economical cost and to invite maximum reasonable competition. To this end, specifications may not be unduly restrictive. By definition, a specification set
10、s limits and thereby eliminates, or potentially eliminates, items that are outside the boundaries drawn. However, a specification should be written to encourage, not discourage, competition consistent with seeking overall economy for the purpose intended. A good specification should do four things:
11、(1) identify minimum requirements, (2) list reproducible test methods to be used in testing for compliance with specifications, (3) allow for a competitive bid, and (4) provide for an equitable award at the lowest possible cost. Proper preparation and use of defense specifications is a difficult tas
12、k requiring careful analysis and good judgment. The following points are some helpful reminders for consideration when developing a specification: a. For commercial products, first consider using or developing a non-Government standard or including DoD requirements in an existing non-Government stan
13、dard. If that will not meet the need, consider developing or revising a commercial item description. b. The specification preparing activity should maintain a carefully documented, permanent record of the source and reason behind particular requirements and changes to requirements. Issues and contro
14、versial areas during the coordination process should be noted, and it may be desirable to summarize these issues and areas in the “Notes” section of the document and solicit feedback as experience develops. This record should provide a basis for related application guidance and a history useful in f
15、uture document revisions. c. Wherever possible, state requirements in terms of performance or form, fit, and function, as opposed to providing details on “how to” achieve the desired result. d. Avoid unnecessary reference to other documents, which can lead to excessive “tiering” of requirements. If
16、only a small portion of another document is needed, it may be better to extract that portion and include it in the specification rather than reference the document. When referencing another document, try to limit the extent of its application by citing specific grades, types, or classes, or citing s
17、pecific requirements or tests. Do not cite paragraph numbers in referenced documents since these are likely to change in future updates. e. Try to make use of commercial products, processes, or practices when setting requirements or tests. f. Make a distinction between requirements portions and guid
18、ance portions of documents. Careful attention to use of the words “should” (guidance language) and “shall” (re-quirement language) is important. g. Use Section 6 “Notes” to provide users with guidance information that should be considered for inclusion in the contract, how to apply the document to d
19、ifferent contract types and different program phases, lessons learned, relationship to other documents, tailoring guidance, and any other information that is not suitable for inclusion as a requirement or test. iiiProvided by IHSNot for ResaleNo reproduction or networking permitted without license f
20、rom IHS-,-,-MIL-STD-961E w/CHANGE 1 h. If a specification is the source document for data item descriptions, develop, coordinate, and issue the specification and the data item descriptions together. 5. The figures appearing at the back of this standard are fictitious and are used only as examples to
21、 illustrate format. If there is any conflict between the text of the document and the figures at the end of this document, the text applies. 6. Comments, suggestions, or questions on this document should be addressed to the Defense Standardization Program Office (DSPO), ATTN: J-307, 8725 John J. Kin
22、gman Road, Stop 6233, Fort Belvoir, VA 22060-6233 or emailed to DSPOdla.mil. Since contact information 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 networki
23、ng permitted without license from IHS-,-,-MIL-STD-961E w/CHANGE 1 SUMMARY OF CHANGE 1 MODIFICATIONS 1. Changed the Uniform Resource Locator (URL) for the Acquisition Streamlining and Standardization Information System (ASSIST) database throughout the document. 2. Changed the order of precedence stat
24、ement in section 2 to include the words “unless otherwise noted herein or in the contract” in the first sentence. Generally, a specification takes precedence over the documents referenced, but there can be occasions, such as a drawing, where the referenced document can take precedence over the speci
25、fication as long as it is noted within the specification. 3. Added a definition for “supersede” in section 3. 4. Deleted the statement in 4.3 that only the contract can require the delivery of data. There are public laws that also require data independent of a contract. 5. Added a requirement to 5.4
26、.1 for the preparing activity to obtain new document numbers using the Automated Document Number module in ASSIST. 6. Added a requirement in 5.4.2 to include the phrase “DRAFT DATED (DATE OF DRAFT) under the header of each page of a draft specification. 7. Added new 5.4.7.3 to authorize inclusion of
27、 reinstatement note on cancelled specifications that are reinstated and updated simultaneously. 8. Added a requirement in 5.7.2.1.5 to cite the specific color 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
28、 since it is not a requirement document. 9. Added an additional sentence to the qualification paragraph in section 6 of specifications to inform users that listings of qualified products can be obtained online through ASSIST. 10. Added shelf-life guidance in 5.11.14, which will be included in the se
29、ction 6 notes of specifications covering items where shelf-life is a consideration. 11. Added a requirement for the amendment number to appear below the document identifier on every page of a specification being amended. 12. Incorporated Defense Standardization Program Policy Memorandum 08-1 as 5.19
30、.3 and figures 15A and 15B to allow cancellation notices to cite either direct replacements or suggested replacements. 13. Incorporated Defense Standardization Program Policy Memorandum 08-3 in 4.5 and 5.19.6 and figure 20 to require unclassified administrative notices for classified specifications.
31、 vProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-961E w/CHANGE 1 14. Added a requirement in 5.19.7.6 that project numbers are not required for administrative notices. 15. Added advisory note to figures 10, 11, and 13 through 18. 16. The foll
32、owing modifications were made to this standard: PARAGRAPH MODIFICATIONForeword Changed 2.2.1 Changed 2.2.2 Changed 2.4 Changed 3.2 Changed 3.24 Changed 3.45.1 Aded 4.3 Changed 4.5 Changed 4.12 Changed 5.4.1 Changed 5.4.2 Changed 5.4.7 Changed 5.4.7.3 Aded 5.4.9 Changed 5.7.2.1.4 Changed 5.7.2.1.5 Ad
33、ed 5.7.4 Changed 5.8.3 Changed 5.11 Changed 5.11.4 Changed 5.11.6 Changed 5.11.12 Changed 5.11.14 Aded 5.12.8 Changed 5.18.3 Changed 5.19.3 Changed 5.19.6 Changed 5.19.7.6 Aded 6.3 Changed 6.6 Changed Figure 3 Changed Figure 5 Changed Figure 10 Changed Figure 11 Changed Figure 12 Changed Figure 13 C
34、hanged Figure 14 Changed viProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-961E w/CHANGE 1 PARAGRAPH MODIFICATION Figure 15 Deleted Figure 15A Aded Figure 15B Aded Figure 16 Changed Figure 17 Changed Figure 18 Changed Figure 19 Aded Figure 20
35、 Aded Concluding material Changed viiProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-961E 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
36、Government documents 1 2.2.1 Specifications, standards, and handbooks 1 2.2.2 Other Government documents, 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
37、 and Standardization InformationSystem (ASSIST). 3 3.3 Analysis 3 3.4 Class. 3 3.5 Composition. 3 3.6 Coordinated specification. 3 3.7 Data. 3 3.8 Data Item Description (DID) 3 3.9 Data product specification. 3 3.10 Defense specification. 4 3.11 Demonstration 4 3.12 Design activity. 4 3.13 Detail sp
38、ecification 4 3.14 DoD Single Stock Point 4 3.15 Entity. 4 3.16 Examination 4 3.17 General specification 4 3.18 Grade. 4 3.19 Inch-pound specification. 4 3.20 Inspection 5 3.21 Interchangeable item. 5 3.22 Interim amendment. 5 3.23 Interim revision. 5 3.24 International standardization agreement. 5
39、viiiProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-961E w/CHANGE 1 CONTENTS PARAGRAPH PAGE 3.25 Item specification 5 3.26 Limited-coordination specification. 5 3.27 Material specification 5 3.28 Metric specification. 5 3.29 Metric units 6 3.
40、30 MS Sheet. 6 3.31 Non-Government standard 6 3.32 Not measurement sensitive specification 6 3.33 Packaging 6 3.34 Part or Identifying Number (PIN). 6 3.35 Performance specification. 6 3.36 Process specification. 6 3.37 Program-unique specification. 6 3.38 Qualification 7 3.39 Recovered material 7 3
41、.40 Recycled material 7 3.41 Soft conversion 7 3.42 Software specification. 7 3.43 Specification 7 3.44 Specification sheet 7 3.45 Style 7 3.45.1 Supersedes 7 3.46 Supplement. 7 3.47 System specification. 7 3.48 Tailoring 8 3.49 Technical manual specification. 8 3.50 Test 8 3.51 Type. 8 3.52 Verific
42、ation 8 4. GENERAL REQUIREMENTS 8 4.1 General 8 4.2 Coverage. 8 4.2.1 Tailoring of requirements. 8 4.3 Data requirements. 8 4.3.1 Data product specifications. 9 4.3.2 Technical manual specifications. 9 4.3.3 Qualification data 9 4.3.4 Use of copyright or patent material 9 4.4 Contractual and adminis
43、trative requirements. 9 4.5 Classified material 9 4.6 Text. 10 ixProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-961E w/CHANGE 1 CONTENTS PARAGRAPH PAGE 4.6.1 Grammar and style. 10 4.6.2 Abbreviations 10 4.6.3 Acronyms 10 4.6.4 Symbols. 10 4.
44、6.5 Proprietary names 10 4.6.6 Commonly used words and phrases 10 4.7 Measurements. 12 4.8 Metric practices. 12 4.8.1 Metric units. 12 4.8.2 Dual dimensions. 12 4.9 Paragraph numbering 12 4.10 Paragraph identification 12 4.11 Specification identifier 12 4.12 Page number 13 4.13 Tables 13 4.13.1 Tabl
45、e numbering. 13 4.13.2 Table title 13 4.13.3 Table format 13 4.13.4 Continuation of tables. 13 4.14 Figures. 13 4.14.1 Figure numbering 14 4.14.2 Figure title. 14 4.14.3 Continuation of figures. 14 4.15 Footnotes and notes. 14 4.15.1 Footnotes to text 14 4.15.2 Footnotes to tables. 14 4.15.3 Notes t
46、o figures. 14 4.16 Foldouts 14 4.17 Definitions 15 4.18 Cross-reference. 15 4.19 References to other documents. 15 4.20 Approved document format 16 5. DETAILED REQUIREMENTS 16 5.1 General 16 5.2 Draft note 16 5.3 Cover page 16 5.3.1 Program-unique specifications 16 5.3.1.1 Program-unique specification identifier 16 5.3.1.2 Commercial and Government Entity (CAGE) code. 17 5.3.1.3 Date of specification. 17 5.3.1.4 Heading. 17 xProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-STD-961E w/CHANGE 1 CONTENTS PARAGRAPH PAGE 5.3.1.5 Type of program
