14.02.2017 Views

Department of Defense INSTRUCTION

x9tnk

x9tnk

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

DoDI 5000.02, January 7, 2015<br />

(3) The DAE may reclassify an acquisition program at any time. The reclassification<br />

decision will be documented in an ADM.<br />

3. ACQUISITION PROGRAM INFORMATION REQUIREMENTS AT MILESTONES<br />

AND OTHER DECISION POINTS<br />

a. Table 2 lists the statutory and regulatory requirements at each <strong>of</strong> the milestones and other<br />

decision points during the acquisition process. In consultation with the appropriate stakeholders,<br />

program managers may propose for MDA approval, tailoring <strong>of</strong> Regulatory program<br />

information. MDAs will document all information tailoring decisions.<br />

b. Each row identifies an information requirement and the source <strong>of</strong> the requirement.<br />

(Sources may refer to United States Code (U.S.C.), Public Law (P.L.), an Executive Order<br />

(E.O.), DoD Instructions (DoDIs), Directives (DoDDs), or other types <strong>of</strong> documentation. When<br />

available, the source will include paragraph (Para.), section (Sec.), or enclosure (Enc.) numbers<br />

and the reference (Ref.) identifier from the list <strong>of</strong> references in this instruction. STATUTORY<br />

items and sources appear in ALL CAPS; Regulatory items and sources appear in normal text.<br />

Requirements are in alphabetical order.<br />

(1) A dot (●) in a cell indicates the specific applicability <strong>of</strong> the requirement to program<br />

type and life-cycle event, and represents the initial submission <strong>of</strong> information. Moving right<br />

across a row, a checkmark () indicates the requirement for updated information, and another<br />

dot indicates submission <strong>of</strong> new information.<br />

(2) Notes accompany each row to explain the requirement, limit or extend the<br />

requirement’s applicability to program type and/or life-cycle event, or refer the reader to more<br />

detailed direction.<br />

c. Labels for the “Life-Cycle Event” columns represent the following events:<br />

(1) “MDD”—Materiel Development Decision.<br />

(2) “MS A”—Milestone A Decision Review.<br />

(3) “CDD Val”—Capability Development Document Validation.<br />

(4) “Dev RFP Rel”—The Development Request for Proposals (RFP) Release Decision<br />

Point conducted before Milestone B to authorize release <strong>of</strong> the RFP for the next phase.<br />

(5) “MS B”—Milestone B Decision Review.<br />

(6) “MS C”—Milestone C Decision Review.<br />

(7) “FRP/FD Dec”—The Full-Rate Production (FRP) Decision or the Full Deployment<br />

(FD) Decision.<br />

Change 2, 02/02/2017 50<br />

ENCLOSURE 1

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!