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 />

Table 6. Exceptions, Waivers, and Alternative Management and Reporting Requirements, Continued<br />

INFORMATION<br />

REQUIREMENT FOR WAIVER<br />

OR EXCEPTION<br />

PROGRAM TYPE<br />

ACAT<br />

MDAP MAIS<br />

II ≤ III<br />

WHEN REQUIRED<br />

SOURCE<br />

REPORTING<br />

PROCEDURE<br />

DT&E EXCEPTION<br />

REPORTING<br />

LEAD SYSTEM INTEGRATOR<br />

EXCEPTION CERTIFICATION<br />

LFT&E WAIVER FROM<br />

FULL-UP, SYSTEM-LEVEL<br />

TESTING<br />

MAIS CRITICAL CHANGE<br />

REPORT AND<br />

CERTIFICATION<br />

MAIS SIGNIFICANT CHANGE<br />

NOTIFICATION<br />

●<br />

Case 1: When an MDAP proceeds with implementing a TEMP that includes a<br />

developmental test plan disapproved by DASD(DT&E).<br />

Case 2: When an MDAP proceeds to IOT&E following an assessment by<br />

DASD(DT&E) that the program is not ready for operational testing.<br />

SEC. 904, P.L. 112-239 (Ref. (l))<br />

Program Manager<br />

to USD(AT&L) to<br />

Congress<br />

STATUTORY<br />

• The report due for Case 1 must include a description <strong>of</strong> the specific aspects <strong>of</strong> the DT&E plan determined to be inadequate; an explanation <strong>of</strong> why the program<br />

disregarded the DASD(DT&E)’s recommendations; and identification <strong>of</strong> the steps taken to address the concerns <strong>of</strong> the DASD(DT&E).<br />

• The report due for Case 2 must include an explanation <strong>of</strong> why the program proceeded to IOT&E despite the DASD(DT&E) findings; a description <strong>of</strong> the aspects <strong>of</strong> the<br />

TEMP that had to be set aside to enable the program to proceed to IOT&E; a description <strong>of</strong> how the program addressed the specific areas <strong>of</strong> concern raised in the<br />

assessment <strong>of</strong> operational test readiness; and a statement <strong>of</strong> whether IOT&E identified any significant shortcomings in the program.<br />

• The USD(AT&L) will compile all such exception reports and annually, not later than 60 days after the end <strong>of</strong> each fiscal year through 2018, submit a report on each<br />

case to the congressional defense committees.<br />

● ● ● Due if the MDA grants an exception. 10 U.S.C. 2410p (Ref. (g)(h)) DAE to Congress<br />

STATUTORY. Satisfies the statutory restrictions applicable to exceptional use <strong>of</strong> a lead systems integrator (see paragraph 5d(9)(g)1 <strong>of</strong> this instruction for additional<br />

discussion).<br />

● ● ● Due at Milestone B or as soon as practicable after program initiation. 10 U.S.C. 2366 (Ref. (g)(h)) DAE to Congress<br />

STATUTORY. Only required for programs on the DOT&E Oversight List for LFT&E that are requesting a waiver from full-up, system-level testing.<br />

●<br />

Not later than 60 calendar days after a MAIS Quarterly Report indicating a<br />

critical change is due to the Senior Official.<br />

10 U.S.C. 2445c (Ref. (g)(h))<br />

Senior Official<br />

through OSD to<br />

Congress<br />

STATUTORY. When the Senior Official is not an individual within OSD, the Critical Change Report will be signed by the Senior Official and provided to the cognizant<br />

OSD <strong>of</strong>ficial for transmittal to Congress. The signed Critical Change Report should be provided to the appropriate OSD <strong>of</strong>ficial with draft transmittal letters addressed to<br />

the congressional defense committees no later than 5 working days before expiration <strong>of</strong> the 60-day period.<br />

●<br />

Not later than 45 calendar days after a MAIS Quarterly Report indicating a<br />

significant change is due to the Senior Official.<br />

10 U.S.C. 2445c (Ref. (g)(h))<br />

Senior Official to<br />

Congress<br />

STATUTORY. The notification must be coordinated with the USD(AT&L), the Deputy Chief Management Officer, or the DoD CIO, as appropriate, before sending to<br />

Congress.<br />

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

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

ENCLOSURE 1

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

Saved successfully!

Ooh no, something went wrong!