Department of Defense INSTRUCTION

DoDI 5000.02, January 7, 2015
risk reduction prototypes will be included if they will materially reduce engineering and
manufacturing development risk at an acceptable cost. If competitive prototyping is not
considered feasible, single prototypes at the system or subsystem level will be considered.
a. Risk reduction prototypes will be included if they will materially reduce
engineering and manufacturing development risk at an acceptable cost. Risk reduction
prototypes can be at the system level or can focus on sub-systems or components.
b. A competitive prototype, or if this is not feasible, a single prototype or
prototyping of critical subsystems prior to Milestone B is statutorily required to be part of the
Acquisition Strategy for MDAPs and is a regulatory requirement for all other programs. The
MDA may waive the competitive prototyping requirement at or prior to Milestone A if:
I. The cost of producing competitive prototypes exceeds the expected lifecycle
benefits (in constant dollars) of producing the prototypes, including the benefits of
improved performance and increased technological and design maturity that may be achieved
through competitive prototyping; or
II. The department would be unable to meet critical national security
objectives without such a waiver.
3. There are a number of ways to structure this phase which should be tailored to
reduce the specific risks associated with the product being acquired. Technology Readiness
Levels, described in the Technology Readiness Assessment (TRA) Guidance (Reference (e) (f)),
should be used to benchmark technology risk during this phase; however, these indices are rough
benchmarks, and not conclusive about the degree of risk mitigation needed prior to development.
Deeper analysis of the actual risks associated with the preferred design and any recommended
risk mitigation must be conducted and provided to the MDA.
(c) The Acquisition Strategy will guide this phase. Multiple technology development
demonstrations, defined in the acquisition strategy, may be necessary before the operational user
and material materiel developer can substantiate that a preferred solution is feasible, affordable,
and supportable; satisfies validated capability requirements; and has acceptable technical risk.
Critical program information will be identified during this phase and program protection
measures to prevent disclosure of critical information will be implemented consistent with
section 13 in Enclosure 3. Planning for EMD, production, developmental and operational test,
and life-cycle sustainment of proposed products will occur during this phase. The government
will update the program IP Strategy (see paragraph 6a(4) of Enclosure 2) to ensure the ability to
compete future sustainment efforts consistent with the Acquisition Strategy to include
competition for spares and depot repair.
(d) During this phase, and timed to support CDD validation (or its equivalent), the
Program Manager will conduct a systems engineering trade-off analysis showing how cost and
capability vary as a function of the major design parameters. The analysis will support the
assessment of refined KPPs/KSAs in the CDD. Capability requirements proposed in the CDD
(or equivalent requirements document) should be consistent with program affordability goals.
Change 2, 02/02/2017 22