1 year ago

Department of Defense INSTRUCTION


DoDI 5000.02, January 7,

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

DoDI 5000.02, January 7, 2015 system has met or exceeds all directed EMD Phase exit criteria and Milestone C entrance criteria. EMD will often continue past the initial production or fielding decision until all EMD activities have been completed and all requirements have been tested and verified. (e) Concurrency Between EMD and Production. In most programs for hardware intensive products, there will be some degree of concurrency between initial production and the completion of developmental testing; and perhaps some design and development work, particularly completion of software, that will be scheduled to occur after the initial production decision. Concurrency between development and production can reduce the lead time to field a system, but it also can increase the risk of design changes and costly retrofits after production has started. Program planners and decision authorities should determine the acceptable or desirable degree of concurrency based on a range of factors. In general, however, there should be a reasonable expectation, based on developmental testing of full-scale EMD prototypes, that the design is stable and will not be subject to significant changes following the decision to enter production. At Milestone B, the specific technical event-based criteria for initiating production or fielding at Milestone C will be determined and included in the Milestone B ADM. (f) Release of the P&D RFP. If the strategy and associated business arrangements planned and approved at Milestone B have been changed as a result of EMD phase activity, or if the validated capability requirements have changed, an updated Acquisition Strategy will be submitted for MDA review and approval prior to the release of the RFP for competitive source selection or the initiation of sole source negotiations. In any event, an updated Acquisition Strategy will be submitted prior to Milestone C and contract award, consistent with the procedures specified in this document. Paragraph 6a in Enclosure 2 provides additional detail about the Acquisition Strategy. (g) Additional EMD Phase Requirements 1. Inherently Government Functions and Lead System Integrators (LSI). Program managers will emphasize the importance of appropriate checks and balances when contractors perform acquisition-related activities and ensure that the government is singularly responsible for the performance of inherently governmental functions. If the Acquisition Strategy for a major system calls for the use of a LSI, a contract will not be awarded to an offeror that either has or is expected to acquire a direct financial interest in the development or construction of an individual system or an element of a system of systems within the major system under the LSI. Exceptions may be granted by the MDA, as provided in 10 U.S.C. 2410p (Reference (g) (h)), that require certification to the Committees on Armed Services of the Senate and House of Representatives. Table 6 in Enclosure 1 of this instruction provides details about the exception reporting. 2. Advanced Procurement of Long Lead Production Items. The MDA may authorize long lead at any point during EMD or at the Development RFP Release Decision or Milestone B, subject to the availability of appropriations. These items are procured in advance of a Milestone C production decision in order to provide for a more efficient transition to production. The amount of long lead appropriate for a given program depends on the type of product being acquired. The product’s content dictates the need for early purchase of selected Change 2, 02/02/2017 29

Joint Pub 6-02 - United States Department of Defense
joint program management handbook - Defense Acquisition University
OVERVIEW W - Office of the Under Secretary of Defense (Comptroller)
Department of Defense Nonlethal Weapons and Equipment Review
Quadrennial Defense Review (QDR) - United States Department of ...
Department of Defense (DoD) Information Enterprise Strategic Plan
Developing Operational Requirements - U.S. Department of ...
Space Acquisition - Air Force Space Command
department of defense more disciplined use of resources
Department of Defense Nonlethal Weapons and Equipment Review
Joint Service Chemical & Biological Defense Program Overview ...
Unmanned Aerial Vehicle - Defense Technical Information Center
USAF ILA Handbook - ACC Practice Center - Defense Acquisition ...
Download PDF - Department of Navy Chief Information Officer - U.S. ...
Joint Service Chemical and Biological Defense Program FY00-02 ...
Navy Cyber Power 2020 - Defense Innovation Marketplace