ESTIMATE ● ● ● ● ● ●
10 U.S.C. 2464 (Ref. (g))
10 U.S.C. 2366a & 2366b (Ref. (g)) SEC. 801, P.L. 112-81 (Ref. (v)) Para. 3d(2) of Enc. 6 of this instruction
MDA/DoD Component STATUTORY. Only the CORE LOGISTICS DETERMINATION is required at Milestone A. Required at Milestone C if there was no Milestone B. Documented in the LCSP. Not required for AIS programs.
Cost Analysis Requirements Description (CARD) ● ● ● ● Sec. 3 of Enc. 10 of this instruction DoD 5000.4-M (Ref. (w)) DoD Component
Regulatory. Due any time an INDEPENDENT COST ESTIMATE (ICE) or an ECONOMIC ANALYSIS is required. Procedures are specifiedin section 3 of Enclosure 10 of this instruction.
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.
ENCLOSURE 1 51
Table 2. Milestone and Phase Information Requirements, continued
INFORMATION REQUIREMENT
PROGRAM TYPE1 LIFE-CYCLE EVENT1,2,3
SOURCE AUTHORITY APPROVAL
MDAP MAIS ACAT MDD MS A CDD Val RFP Dev Rel
MS
B5 MS C FRP/FD Dec OTHER
II ≤ III
CYBERSECURITY STRATEGY ● ● ● ● ● SEC. 811, P.L. 106-398 (Ref. (q)) 40 U.S.C. 11312 (Ref. (p)) DoDI 8500.01E (Ref. (x))
DoD CIO; Component CIO STATUTORY for mission critical or mission essential IT systems. Regulatory for all other programs containing IT, including NSS. See section 6 of Enclosure 11. The CYBERSECURITY STRATEGY is an
appendix to the Program Protection Plan (PPP). A draft4 update is due for the Development RFP Release and is approved at Milestone B. May include the approved DoD Risk Management Framework Security
Plan for urgent needs. The DoD CIO is approval authority for ACAT ID and all ACAT IA programs; the Component CIO is approval authority for all other ACATs.
Development RFP Release Cost Assessment ● ● ● Para. 2a(5) of Enc. 10 of this instruction CAPE
Regulatory. Requirements and procedures for this assessment are specifiedin paragraph 2a(5) in Enclosure 10 of this instruction.
DoD Component Cost Estimate ● ● ● ● ● ● ● Para. 5d(3)(b)2b of this instruction Sec. 2 of Enc. 10 of this instruction DoD Component Regulatory. See the direction in section 2 of Enclosure 10 of this instruction. The DoD Component will determine the cost estimating requirements for ACAT II and III programs.
DoD Component Cost Position ● ● ● ● ● ● ● Para. 2e of Enc. 10 of this instruction DoD Component
Regulatory. Mandatory for MDAPs and MAIS programs; documented DoD Component Cost Position must be signed by the appropriate DoD Component Deputy Assistant Secretary for Cost and Economics.
DoD Component Live Fire Test and Evaluation
(LFT&E) Report ● ● ● ● ● This instruction CAE
Regulatory. Programs on the Director, Operational Test and Evaluation (DOT&E) Oversight List for LFT&E oversight only; due upon completion of LFT&E.
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.
ENCLOSURE 1 52
Table 2. Milestone and Phase Information Requirements, continued
INFORMATION REQUIREMENT
PROGRAM TYPE1 LIFE-CYCLE EVENT1,2,3
SOURCE AUTHORITY APPROVAL
MDAP MAIS ACAT MDD MS A CDD Val RFP Dev Rel
MS
B5 MS C FRP/FD Dec OTHER
II ≤ III
DOT&E REPORT ON INITIAL OPERATIONAL TEST
AND EVALUATION (IOT&E) ● ● ● ● ● 10 U.S.C. 2399 (Ref. (g)) 10 U.S.C. 139 (Ref. (g)) DOT&E
STATUTORY; required for DOT&E Oversight List programs only. The DOT&E publishes an online list of programs under operational test and evaluation (OT&E) and LFT&E oversight at https://extranet.dote.osd.mil/oversight/ (requires login with a Common Access Card).
A final decision to proceed beyond Low-Rate Initial Production (LRIP) or beyond Limited Deployment may not be made until the DOT&E has submitted the IOT&E Report to the Secretary of Defense, and the congressional defense committees have received that report. If DoD decides to proceed to operational use of the program or to make procurement funds available for the program before the MDA’s FRP/FD decision, the DOT&E's report will be submitted as soon as practicable after the DoD decision to proceed.
ECONOMIC ANALYSIS ● ● ● ● ● ● SEC. 811, P.L. 106-398 (Ref. (q)) DoDI 7041.3 (Ref. (y)) DoD Component
STATUTORY for MAIS. May be combined with the AoA at Milestone A. Also required at any review that is the equivalent of Milestone B or the FD Decision.
Exit Criteria ● ● ● ● ● ● ● This instruction MDA
Regulatory. Exit criteria are specific events and accomplishments that must be achieved before a program can proceed to the designated acquisition phase covered by the criteria. Documented in the ADM.