U.S. Code · Título 10
Defense business systems: business process reengineering; enterprise architecture; management
10 U.S.C. § 2222
Office of the Law Revision Counsel · release 119-142
Se muestra el texto operativo de la sección. Las notas estatutarias y el historial de enmiendas están en la fuente oficial.
Defense Business Processes Generally.—
The Secretary of Defense shall ensure that defense business processes are reviewed, and as appropriate revised, through business process reengineering to match best commercial practices, to the maximum extent practicable, so as to minimize customization of commercial business systems.Defense Business Systems Generally.—
The Secretary of Defense shall ensure that each covered defense business system developed, deployed, and operated by the Department of Defense—
Issuance of Guidance.—
Secretary of defense guidance.—
The Secretary shall issue guidance to provide for the coordination of, and decision making for, the planning, programming, and control of investments in covered defense business systems.Supporting guidance.—
The Secretary shall direct the Chief Information Officer of the Department of Defense, the Under Secretary of Defense for Acquisition and Sustainment, and the Chief Information Officer of each of the military departments to issue and maintain supporting guidance, as appropriate and within their respective areas of responsibility, for the guidance of the Secretary issued under paragraph (1).Guidance Elements.—
The guidance issued under subsection (c) shall include the following elements:
Policy to ensure that the business processes of the Department of Defense are continuously reviewed and revised—
Defense Business Enterprise Architecture.—
Blueprint.—
The Secretary, working through the Chief Information Officer of the Department of Defense, shall develop and maintain a blueprint to guide the development of integrated business processes within the Department of Defense. Such blueprint shall be known as the “defense business enterprise architecture”.Purpose.—
The defense business enterprise architecture shall be sufficiently defined to effectively guide implementation of interoperable defense business system solutions and shall be consistent with the policies and procedures established by the Director of the Office of Management and Budget.Elements.—
The defense business enterprise architecture shall—
enable the Department of Defense to—
Integration into information technology architecture.—
Common enterprise data.—
The defense business enterprise shall include enterprise data that may be automatically extracted from the relevant systems to facilitate Department of Defense-wide analysis and management of its business operations.Roles and responsibilities.—
The Chief Information Officer of the Department of Defense, in coordination with the Chief Data and Artificial Intelligence Officer, shall have primary decision-making authority with respect to the development of common enterprise data. In consultation with the Defense Business Council, the Chief Information Officer shall—
The Chief Information Officer and the Under Secretary of Defense (Comptroller) shall—
Defense Business Council.—
Requirement for council.—
The Secretary shall establish a Defense Business Council to provide advice to the Secretary on developing the defense business enterprise architecture, reengineering the Department’s business processes, developing and deploying defense business systems, and developing requirements for defense business systems. The Council shall be co-chaired by the Chief Information Officer and the Performance Improvement Officer of the Department of Defense.Membership.—
The membership of the Council shall include the following:
The following officials of the Department of Defense, or their designees:
Approvals Required for Development.—
Initial approval required.—
The Secretary shall ensure that a covered defense business system program cannot proceed into development (or, if no development is required, into production or fielding) unless the appropriate approval official (as specified in paragraph (2)) determines that—
Appropriate official.—
For purposes of paragraph (1), the appropriate approval official with respect to a covered defense business system is the following:
Except as may be provided in subparagraph (C), for any defense business system other than a priority defense business system—
Annual certification.—
For any fiscal year in which funds are expended for development or sustainment pursuant to a covered defense business system program, the appropriate approval official shall review the system and certify, certify with conditions, or decline to certify, as the case may be, that it continues to satisfy the requirements of paragraph (1). If the approval official determines that certification cannot be granted, the approval official shall notify the milestone decision authority for the program and provide a recommendation for corrective action.Obligation of funds in violation of requirements.—
The obligation of Department of Defense funds for a covered defense business system program that has not been certified in accordance with paragraph (3) is a violation of section 1341(a)(1)(A) of title 31.Responsibility of Milestone Decision Authority.—
The milestone decision authority for a covered defense business system program shall be responsible for the acquisition of such system and shall ensure that acquisition process approvals are not considered for such system until the relevant certifications and approvals have been made under this section.Definitions.—
In this section:
Defense business system.—
The term “defense business system” means an information system that is operated by, for, or on behalf of the Department of Defense, including any of the following:
The term does not include—
Covered defense business system.—
The term “covered defense business system” means a defense business system that is expected to have a total amount of budget authority, over the period of the current future-years defense program submitted to Congress under section 221 of this title, in excess of $50,000,000.Business system portfolio.—
The term “business system portfolio” means all business systems performing functions closely related to the functions performed or to be performed by a covered defense business system.Covered defense business system program.—
The term “covered defense business system program” means a defense acquisition program to develop and field a covered defense business system or an increment of a covered defense business system.Priority defense business system.—
The term “priority defense business system” means a defense business system that is—
Enterprise architecture.—
The term “enterprise architecture” has the meaning given that term in section 3601(4) of title 44.Information system.—
The term “information system” has the meaning given that term in section 11101 of title 40, United States Code.National security system.—
The term “national security system” has the meaning given that term in section 3552(b)(6)(A) of title 44.Business process mapping.—
The term “business process mapping” means a procedure in which the steps in a business process are clarified and documented in both written form and in a flow chart.Common enterprise data.—
The term “common enterprise data” means business operations or management-related data, generally from defense business systems, in a usable format that is automatically accessible by authorized personnel and organizations.Data governance process.—
The term “data governance process” means a system to manage the timely Department of Defense-wide sharing of data described under subsection (e)(6)(A).(Added Pub. L. 108–375, div. A, title III, § 332(a)(1), Oct. 28, 2004, 118 Stat. 1851; amended Pub. L. 109–364, div. A, title IX, § 906(a), Oct. 17, 2006, 120 Stat. 2354; Pub. L. 110–417, [div. A], title III, § 351, Oct. 14, 2008, 122 Stat. 4425; Pub. L. 111–84, div. A, title X, § 1072(a), Oct. 28, 2009, 123 Stat. 2470; Pub. L. 111–383, div. A, title X, § 1075(b)(29), Jan. 7, 2011, 124 Stat. 4370; Pub. L. 112–81, div. A, title IX, § 901, Dec. 31, 2011, 125 Stat. 1527; Pub. L. 112–239, div. A, title IX, § 906, Jan. 2, 2013, 126 Stat. 1869; Pub. L. 113–66, div. A, title IX, § 901, Dec. 26, 2013, 127 Stat. 815; Pub. L. 113–283, § 2(e)(5)(A), Dec. 18, 2014, 128 Stat. 3087; Pub. L. 113–291, div. A, title VIII, § 803, title IX, § 901(d), (k)(3), title X, § 1071(f)(16), Dec. 19, 2014, 128 Stat. 3427, 3463, 3468, 3511; Pub. L. 114–92, div. A, title VIII, § 883(a)(1), (f), title X, § 1081(a)(7), Nov. 25, 2015, 129 Stat. 942, 1001; Pub. L. 114–328, div. A, title X, § 1081(a)(6), (c)(5), Dec. 23, 2016, 130 Stat. 2417, 2419; Pub. L. 115–91, div. A, title IX, § 912(a), title X, § 1081(b)(2), Dec. 12, 2017, 131 Stat. 1519, 1597; Pub. L. 115–232, div. A, title X, § 1081(f)(1)(A)(ii), Aug. 13, 2018, 132 Stat. 1986; Pub. L. 116–92, div. A, title VIII, § 839(a), title IX, § 902(25), title XVII, § 1731(a)(31), Dec. 20, 2019, 133 Stat. 1498, 1545, 1814; Pub. L. 117–263, div. A, title IX, § 902, Dec. 23, 2022, 136 Stat. 2748; Pub. L. 118–159, div. A, title IX, § 902(b), Dec. 23, 2024, 138 Stat. 2026; Pub. L. 119–60, div. A, title VIII, § 812(a)(2), Dec. 18, 2025, 139 Stat. 951.)