Department of Defense INSTRUCTION
x9tnk
x9tnk
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
DoDI 5000.02, January 7, 2015<br />
ENCLOSURE 12<br />
ACQUISITION OF DEFENSE BUSINESS SYSTEMS (DBS)<br />
1. PURPOSE. This enclosure provides additional policy applicable to the acquisition <strong>of</strong> defense<br />
business systems that are expected to have a life-cycle cost in excess <strong>of</strong> $1 million over the<br />
current Future Years <strong>Defense</strong> Program. It is intended to be used in conjunction with the<br />
procedures in the core instruction, with statutorily specified governance, distinctive<br />
documentation as noted in Enclosure 1 <strong>of</strong> this instruction, and augmented review requirements.<br />
2. DBS<br />
a. A DBS is an information system, other than a National Security System, operated by, for,<br />
or on behalf <strong>of</strong> the DoD, including financial systems, management information systems,<br />
financial data feeder systems, and the information technology and cybersecurity infrastructure<br />
used to support business activities, such as contracting, pay and personnel management systems,<br />
some logistics systems, financial planning and budgeting, installations management, and human<br />
resource management. The Component Chief Management Officer makes the determination that<br />
a program is a DBS.<br />
b. DBS will enter the acquisition process at the Materiel Development Decision (MDD) and<br />
follow the procedures described in paragraph 5d <strong>of</strong> this instruction. By statute, prior to<br />
approving Milestone A or initiating development <strong>of</strong> any increment <strong>of</strong> a DBS, the Milestone<br />
Decision Authority (MDA) must determine that the program will achieve Initial Operational<br />
Capability within 5 years (section 811 <strong>of</strong> P.L. 109-364 (Reference (k))). For a DBS that is a<br />
Major Automated Information System (MAIS) program, the requirements in Table 4 will apply.<br />
c. The policies in this enclosure apply to the development <strong>of</strong> all DBS.<br />
3. DBS GOVERNANCE<br />
a. <strong>Defense</strong> Business Systems Management Committee (DBSMC)<br />
(1) The DBSMC, chaired by the Deputy Secretary <strong>of</strong> <strong>Defense</strong>, recommends policy and<br />
procedure to improve the acquisition <strong>of</strong> DBS.<br />
(2) The DBSMC is the approval authority for all statutorily required DBS certifications<br />
and will document such decisions.<br />
(3) A DBSMC certification approval is required prior to any obligation <strong>of</strong> funds for<br />
acquisition. Programs must be reviewed at least annually.<br />
(4) The MDA (when at the OSD or Military <strong>Department</strong> level) will serve as a member <strong>of</strong><br />
the DBSMC.