Department of Defense INSTRUCTION
x9tnk
x9tnk
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DoDI 5000.02, January 7, 2015<br />
standard program categories or types in tabular form. Table 1 in Enclosure 1 provides specific<br />
definitions, funding thresholds, and decision authorities. Some information systems are also<br />
designated as a National Security System or a <strong>Defense</strong> Business System. These designations are<br />
defined in statute and have procedural and policy consequences. Enclosure 11 addresses<br />
Information Technology, and Enclosure 12 DoDI 5000.75 (Reference (cw)) describes <strong>Defense</strong><br />
Business Systems.<br />
(4) Program Decision Reviews and Milestones. The purpose <strong>of</strong> the decision reviews<br />
embedded in the acquisition procedures described in this section is to carefully assess a<br />
program’s readiness to proceed to the next acquisition phase and to make a sound investment<br />
decision committing the <strong>Department</strong>’s financial resources. Consequently, reviews will be issue<br />
and data focused to facilitate an examination <strong>of</strong> relevant questions affecting the decisions under<br />
consideration and to allow the MDA to judge whether the program is ready to proceed. The<br />
following policies will guide decision reviews:<br />
(a) The MDA is the sole and final decision authority. Staff members and staff<br />
organizations support and facilitate the MDA's execution <strong>of</strong> that authority.<br />
(b) The <strong>Defense</strong> Acquisition Board (DAB) will advise the DAE on critical<br />
acquisition decisions when the DAE is the MDA. The DAE or designee will chair the DAB. An<br />
Acquisition Decision Memorandum (ADM) will document decisions resulting from reviews.<br />
Similar procedures will be established at the Component level for use by other MDAs.<br />
(c) Program Managers, under the supervision <strong>of</strong> Program Executive Officers (PEOs)<br />
and CAEs, are expected to design acquisition programs, prepare programs for decisions, and<br />
execute approved program plans.<br />
(d) Overarching Integrated Product Teams (OIPTs) at the DoD OSD level, and<br />
similar organizations within the DoD Components are expected to collectively assist the MDA in<br />
making sound investment decisions for the department, and to ensure programs are structured<br />
and resourced to succeed. These organizations are not decision bodies and they and their leaders<br />
do not supplant the authority <strong>of</strong> the Program Manager, PEO, CAE, or DAE.<br />
(e) Issues should be resolved at the lowest level possible. When an issue cannot be<br />
resolved quickly at a lower level, the issue will be submitted to the MDA with complete and<br />
objective data necessary to support a decision.<br />
(f) The documents prepared in support <strong>of</strong> the decision process (e.g., Acquisition<br />
Strategy, Systems Engineering Plan (SEP), Test and Evaluation Master Plan (TEMP), Life-Cycle<br />
Sustainment Plan (LCSP)) should generally not be prepared solely for staff review and approval,<br />
but be intended primarily for use within the program as planning and management tools that are<br />
highly specific to the program and tailored to meet program needs.<br />
(g) Review preparation will be streamlined and efficient. Staff members will be<br />
provided with the data needed to support the review, but they will also work to minimize the<br />
overhead burden placed on the DoD Components, PEOs, program managers, and their staffs.<br />
Change 2, 02/02/2017 4