SD-15 Guide For Performance SpecificationsThis document provides guidance information on performance specifications focusing primarily on stating requirements in performance terms and ensuring that sufficient verification means are included in the specification to evaluate conformance. While the focus of this document is on defense specifications developed under DoD 4120.24-M, Defense Standardization Program DSP Policies and Procedures, the principles and techniques can also be applied to program unique performance specifications, performance-based purchase descriptions, commercial item descriptions, or any other type of procurement specification. This guide is intended to supplement the format and content requirements for writing performance specifications found in MIL-STD-961, Defense and Program-Unique Specifications Format and Content.

Pages 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20 - 21 - 22 - 23 - 24 - 25 - 26 - 27 - 28 - 29 - 30 - 31 - 32 - 33 - 34 - 35 - 36 - 37 - 38 - 39 - 40 - 41 - 42 - 43 - 44 - 45 - 46 - 47 - 48 - 49 - 50 - 51 - 52 - 53 - 54 - 55 - 56 - 57 - 58 - 59 - 60 - 61 - 62 - 63 - 64

Performance Specification Guide SD-15

received and feedback from industry and users warrants changes as appropriate to develop a sound acquisition strategy recommendation. Information collected during market research can be analyzed to understand the technologies involved, the available alternatives, and the feasibility of meeting the requirements with a commercial product. A good technique is to send a draft of the performance specification out to users and industry for review and comment to ensure everyone shares the same understanding of the operational requirement and that the specification meets that requirement. Feedback from users and industry on the draft specification can help shorten acquisition cycle time, avoid unnecessary non-value-added costs, eliminate excessively complex or unnecessary requirements, and promote industry responsiveness to the subsequent solicitation package containing the final performance specification.

For more detailed guidance on market research, consult the SD-5, Market Research: Gathering Information about Commercial Products and Services and the Federal Acquisition Regulation, Part 10, Market Research.

DEVELOPING PERFORMANCE REQUIREMENTS

In developing performance requirements, describe only those aspects of the need that are essential for a supplier to provide the user with a viable, practical, and affordable solution. By articulating the needs in terms of output-oriented, measurable, operational, functional, and performance capabilities and characteristics, the needs will remain traceable throughout the systems engineering allocation, design, manufacturing, and verification functions that occur as part of the acquisition process. The following areas represent typical needs from which user requirements generally emanate:

• Command, control, communications, computers and intelligence architecture interface, protocol commonality, and interoperability

• Physical interface or interoperability with other systems, support equipment, or facilities

• Range

• Speed

• Power

• Envelope (size)

• Efficiency

• Accuracy

• Payload

• Safety

• Durability

• Acoustics

• Environmental conditions

• Nuclear, biological, and chemical effects

• Reliability

• Availability

• Maintainability

• Interchangeability