Department of Defense INSTRUCTION

DoDI 5000.02, January 7, 2015
Table 2. Milestone and Phase Information Requirements, Continued
INFORMATION REQUIREMENT
MDAP
PROGRAM TYPE 1 LIFE-CYCLE EVENT 1,2,3
MAIS
ACAT
II
≤ III
MDD
MS
A
CDD
Val
Dev
RFP
Rel
MS
B 5
MS
C
FRP/FD
Dec
OTHER
SOURCE
APPROVAL
AUTHORITY
ANALYSIS OF ALTERNATIVES (AoA) ● ● ● ● ●
40 U.S.C. 11312 (Ref. (p))
SEC. 811, P.L. 106-398 (Ref. (q))
10 U.S.C. 2366a (Ref. (g)(h))
MDA (DCAPE
assesses AoAs for
ACAT ID/IAM only)
STATUTORY for MDAPs, MAIS programs, and all AIS programs, including National Security Systems (NSSs), at Milestone A. STATUTORY updates required through Milestone C (or Milestone B if there is no
Milestone C) for MAIS programs, and all AIS programs. Regulatory for all other specified Program Type/Event combinations. A DoD Component is responsible for conduct and approval of the AoA. The distinct
assessment and approval roles of the Director of Cost Assessment and Program Evaluation (DCAPE) and the MDA associated with the AoA and the selection of the materiel solution(s) are detailed in section 2
of Enclosure 9 of this instruction.
AoA Study Guidance and AoA Study Plan ● ● ● ● ● Para. 5d(1)(b) of this instruction
DCAPE or DoD
Component Equivalent
Regulatory requirements to guide the AoA. AoA Study Guidance informs the preparation of the AoA Study Plan. The AoA Study Guidance must be provided to DoD Component(s) for development of the AoA
Study Plan prior to the MDD. Consistent with the AoA Study Guidance, the lead DoD Component will prepare the AoA Study Plan and present it at the MDD.
BANDWIDTH REQUIREMENTS REVIEW ● ● ● ● ●
SEC. 1047, P.L. 110-417 (Ref.
(f)(g))
This Instruction
STATUTORY for MDAPs and major weapon systems; Regulatory for all other programs. Bandwidth requirements data will be documented in the Information Support Plan (ISP). If the ISP is waived for a
program, conformance with bandwidth review will be based on data provided in the Capability Development Document (CDD), consistent with Net-Ready Key Performance Parameter (NR-KPP) guidance in
Appendix E to Enclosure D of the Manual for the Operation of the Joint Capabilities Integration and Development System (JCIDS) (Reference (r)) and Chairman of the Joint Chiefs of Staff Instruction (CJCSI)
6212.01F 5123.01G (Reference (s)).
Capability Development Document (CDD) ● ● ● ● ●
CJCSI 3170.01 (Ref.(d))
JCIDS Manual (Ref. (r))
DoD CIO
JROC, JCB, or
Component Validation
Regulatory. A draft CDD is required at Milestone A; a validated CDD is required at the Development RFP Release Decision Point and informs Milestone B. If there are no changes, a revalidated CDD may be
submitted for the Capability Production Document (CPD) required at Milestone C. An equivalent DoD Component-validated requirements document will satisfy this requirement for certain information systems.
For approval authorities, JROC is Joint Requirements Oversight Council; JCB is Joint Capabilities Board.
Table Notes:
1. A dot (●) in a cell indicates the specific applicability of the requirement to program type and life-cycle
event, and represents the initial submission requirement. Moving right across a row, a checkmark ()
indicates the requirement for updated information.
2. All of the “Life-Cycle Events” will not necessarily apply to all “Program Types.”
3. Unless otherwise specified when discussed in this instruction, documentation for identified events will
be submitted no later than 45 calendar days before the planned review.
4. Requires a Program Manager-, PEO-, and CAE-approved draft.
5. Information requirements that have been finalized and approved by the responsible authority in support of the Development
RFP Release Decision Point do not have to be re-submitted prior to Milestone B unless changes have occurred. In that
case, updated documents will be provided.
6. Incrementally Deployed Software Intensive Programs (Model #3) do not have a Milestone C and consequently are not
required to satisfy the Table 2 requirements associated with that milestone.
Change 2, 02/02/2017 55
ENCLOSURE 1