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

procedures for such programs will be consistent with applicable statute, regulation, and this<br />

instruction.<br />

4. DBS PROBLEM STATEMENT. DBS generally do not employ Joint Capabilities Integration<br />

and Development System procedures for the development and validation <strong>of</strong> capability<br />

requirements documents. Instead functional sponsors will analyze a perceived business problem,<br />

capability gap, or opportunity and document the results in a Problem Statement. The Problem<br />

statement will include measurable business outcomes, a rough order <strong>of</strong> magnitude cost estimate<br />

and projected/anticipated financial return measures such as net present value, payback or return<br />

on investment.<br />

a. The DBS Problem Statement must be reviewed by the IRB and approved by the IRB<br />

chair. Analysis supporting the Problem Statement will be forwarded to the IRB and the Joint<br />

Staff for review.<br />

b. The Problem Statement will be refined over time to inform post-MDD decision making.<br />

The final Problem Statement will be reviewed by the IRB and approved by the IRB chair prior to<br />

the Development RFP Release Decision Point.<br />

c. Approved Problem Statements will be submitted to the MDA 30 days prior to the MDD<br />

and any subsequent decision point where they are required.<br />

d. The Joint Requirements Oversight Council (JROC), on advice <strong>of</strong> the J-8 and the<br />

Functional Capabilities Board, will have authority to review Problem Statements to determine if<br />

JROC interest exists.<br />

1. PURPOSE. This enclosure provides additional policy and procedure applicable to the<br />

acquisition <strong>of</strong> defense business systems (DBS).<br />

2. DBS<br />

a. A DBS is defined in 10 U.S C. 2222 and is a Doctrine, Organization, Training, Materiel,<br />

Leadership and Education, Personnel, Facilities, and Policy (DOTMLPF-P) solution. The DoD<br />

Component makes the determination that a program is a DBS.<br />

(1) A covered DBS is expected to have a total amount <strong>of</strong> budget authority over the period<br />

<strong>of</strong> the current FYDP in excess <strong>of</strong> $50 million.<br />

(2) A priority DBS is expected to have a total amount <strong>of</strong> budget authority over the period<br />

<strong>of</strong> the current FYDP in excess <strong>of</strong> $250 million, or is designated as such by the DCMO.<br />

(3) The requirements in Table 2 in Enclosure 1 will apply to a DBS that is a Major<br />

Automated Information System (MAIS). A DBS can be both a MAIS and a priority DBS.<br />

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

ENCLOSURE 12

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

Saved successfully!

Ooh no, something went wrong!