Department of Defense INSTRUCTION

DoDI 5000.02, January 7, 2015
1. General. EMD completes all needed hardware and software detailed design;
systemically retires any open risks; builds and tests prototypes or first articles to verify
compliance with capability requirements; and prepares for production or deployment. It includes
the establishment of the initial product baseline for all configuration items.
a. Design. The system design effort usually includes a standard series of
design reviews prior to test article fabrication and/or software build or increment coding.
Multiple design iterations may be necessary to converge on a final design for production. The
SEP, described in section 2 in Enclosure 3 of this instruction, provides the basis for design
activities.
b. Post-Milestone B PDR. If a PDR prior to Milestone B has been waived,
the Program Manager will plan for a PDR as soon as feasible after program initiation.
2. Developmental Test and Evaluation (DT&E). Developmental testing and
evaluation provides feedback to the Program Manager on the progress of the design process and
on the product’s compliance with contractual requirements. DT&E activities also evaluate the
ability of the system to provide effective combat capability, including its ability to meet its
validated and derived capability requirements, including the verification of the ability of the
system to achieve KPPs and KSAs, and that initial system production and deployment and
OT&E can be supported. The effort requires completion of DT&E activities consistent with the
TEMP. Successful completion of adequate testing with production or deployment representative
prototype test articles will normally be the primary basis for entering LRIP or Limited
Deployment. Enclosure 4 includes more detailed discussions of DT&E requirements.
3. Early OT&E Events. Independent operational assessments, conducted by the
Component operational test organization, will normally also occur during EMD. These events
may take the form of independent evaluation of developmental test results or of separate
dedicated test events such as Limited User Tests. Developmental and operational test activities
should, to the extent feasible, be planned in conjunction with one another to provide as efficient
an overall test program as possible. Enclosures 4 and 5 provide more detailed discussions of
DT&E and OT&E.
(c) Preparation for Production, Deployment, and Sustainment. During EMD, the
Program Manager will finalize designs for product support elements and integrate them into a
comprehensive product support package. Early in the EMD Phase, the Program Manager’s
initial product support performance requirements allocations will be refined based on the results
of engineering reviews. Later in this phase, programs will demonstrate product support
performance through test, to ensure the system design and product support package meet the
sustainment requirements within the affordability caps established at Milestone B.
(d) EMD Phase Completion. The EMD Phase will end when: (1) the design is
stable; (2) the system meets validated capability requirements demonstrated by developmental
and initial operational testing as required in the TEMP; (3a) manufacturing processes have been
effectively demonstrated and are under control; (3b) software sustainment processes are in place
and functioning; (4) industrial production capabilities are reasonably available; and (5) the
Change 2, 02/02/2017 28