SD-5 Market ResearchThe purpose of this document is to provide DoD and other Federal personnel involved in the acquisition process with practical guidance on using market research to ensure the acquisition of products and services that will best serve the government??s needs. Specifically, this document is designed for personnel involved with establishing requirements for products or services, such as engineers, technical specialists, project officers, and customers; personnel involved with purchasing products or services, such as contracting officers, contract specialists, and cost analysts; and personnel who support the acquisition process, such as logisticians, testing and quality assurance specialists, and legal counsel.

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

I f; •I r , • ~·

' .• I ( ..A#'

•

To get the most useful information from potential sources, you should first provide them with information about the requirement.Table 1 is an example of the type of information you might want to provide about a requirement for an IT system. Again, you should provide only the minimum information necessary to obtain the answers you need.

Table 1. Example of the Type of Information to Provide to Sources

About a Requirement for an IT System

Category	Type of information
General information	Operating characteristics for hardware or software Environmental conditions for use Anticipated use (fixed, airborne, tactically deployable)
Services information	Description of services desired Period of performance Expected deliverables Expected labor categories
System interface or integration requirements	Computer language, speed, throughput, ports, memory, and expansion potential Radio transmission frequency requirements and allocation status Rules for government use of frequency spectrum Human factor considerations
Maintainability	Self-test requirements Limitations, if any, on organizational-level support equipment
Communications/computer system interfaces	Software portability to other communications/computer systems Operating duty cycle (full time, intermittent) Input power quality (drops, surges, spikes, noise) Essential safety characteristics Reliability, maintainability, and survivability Nuclear hardening requirements Chemical, biological, and radiological survivability Electromagnetic compatibility
Logistics support	Planned maintenance echelons Maintainer proficiency levels Software maintenance plans Limitations on evacuation of reparable items (battlefield, underground, rough handling) Maintenance environment (high winds, mud) Supply support, support equipment needs, and limitations Training needs Technical data needs Transportability