U.S. flag

An official website of the United States government

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.


Secure .gov websites use HTTPS
A lock () or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Defense Business Systems (DBS)


  1. Home
  2. About AAFDID
  3. Defense Business Systems (DBS)

DoDI 5000.75 Overview. DODI 5000.75, "BUSINESS SYSTEMS REQUIREMENTS AND ACQUISITION", implements the statutory requirements of 10 U.S.C. Section 2222(c) "Issuance of Guidance" and Section 883(e) "Guidance on Acquisition of Business Systems" of Public Law 114-92 (FY16 NDAA). 

Section 2222 provides an opportunity to build a framework in order to resolve discrepancies and other challenges between IT acquisition policy in DoD Instruction (DoDI) 5000.02 and DoD guidance on the business systems requirements and investment review process in accordance with U.S.C., Title 10, Section 2222. Business systems acquisition is the joint responsibility of the functional and the acquisition communities. Both communities are accountable for the successful delivery of business capability, from business process design through business system deployment and capability support.

DoDI 5000.75 Statutory Requirements. Title 10, United States Code (USC), Section 2222 sets forth statutory requirements to govern Defense Business Systems (DBS). See tab 'DBS Statutory Requirements' for further information.

Business Capability Acquisition Cycle (BCAC). The purpose of the Business Capability Acquisition Cycle (BCAC) for DBS, is to rapidly deploy business capabilities that address identified mission and capability needs within approved cost, schedule, and performance parameters. Documentation is not developed merely for compliance purposes or to pass the decision point, but rather to apply commercial best practices and lessons learned to prioritize and more rapidly develop and deploy useable, affordable subsets of capability, such as a release. A release is a manageable subset of functionality, such as minimum viable product, that provides utility in support of the business capability. The utility provided by a release does not have to fulfill the entire business capability. Additional utility may be added through iterative releases based on user feedback to minimize risk and increase adoption.

The procedures used to develop business capability requirements and supporting systems will be tailored to the characteristics of the capability being acquired.

(1) Tailoring should be considered throughout the life cycle from both the functional and acquisition perspective.

(2) The MDA may tailor acquisition content (i.e., acquisition strategy content) for all BCAC phases. Information supporting requirements validation and the annual investment certification process cannot be tailored and must be provided to decision makers as prescribed.

(3) Statutory requirements for business systems are listed on tab 'DBS Statutory Requirements'.