Browse Arkansas Code titles and sections
10 U.S.C. § 4571 — Repealed. Pub. L. 119–60, div. A, title VIII, § 811(a)(1), Dec. 18, 2025, 139 Stat. 948]
Federal law — U.S. Code and appendices · legal_authorities
### Statutory Notes
Section, added Pub. L. 111–383, div. A, title VIII, § 805(a)(1), Jan. 7, 2011, 124 Stat. 4259, § 2223a; renumbered § 4571 and amended Pub. L. 116–283, div. A, title XVIII, § 1857(b), Jan. 1, 2021, 134 Stat. 4276, related to information technology acquisition: planning and oversight processes.
#### Electromagnetic Spectrum Demonstration Program
Pub. L. 118–159, div. A, title II, § 234, Dec. 23, 2024, 138 Stat. 1839, which authorized a demonstration program to assess the viability of using wideband adaptive signal processing technology to support simultaneous transmit and receive signals on the same electromagnetic spectrum frequency band, was transferred and is set out as a note under [section 4001 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4001&num=0&edition=prelim).
#### Policies for Management and Certification of Link 16 Military Tactical Data Link Network
Pub. L. 118–31, div. A, title II, § 228, Dec. 22, 2023, 137 Stat. 199, as amended by Pub. L. 119–60, div. A, title II, § 216, Dec. 18, 2025, 139 Stat. 775, which directed the Secretary of Defense shall develop and implement policies to adapt Link 16 system management and certification to align with agile development practices, was transferred and is set out as a note under [section 4001 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4001&num=0&edition=prelim).
#### Requirements for Deployment of Fifth Generation Information and Communications Capabilities to Military Installations and Other Department Facilities
Pub. L. 118–31, div. A, title XV, § 1526, Dec. 22, 2023, 137 Stat. 557, which required the Secretary of Defense shall develop and implement a strategy for deploying to military installations a
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 4571
Stored review status: release_metadata_unconfirmed. A text match is a research starting point; applicability is not established.
Original supplied file — preserved unchanged
Download original Markdown file
File SHA-256: 827ce274d21325d810470237b1f0a44c9c1e157330ab3ff41b1e402714eba566. The original may include catalog metadata, neighboring provisions, or embedded records outside this collection's scope. Search shows only the selected federal record. Historical editions and unverified snapshots are not a statement of current law.
Authority boundary: historical or unconfirmed source not current law verified.
Open the recorded source website ↗
Record provenance
Stable record: federal_law:legal_authorities:record_usc_a244adcde8da19f4391c1c8a
Source file: Laws/federal/codes/united-states-code/title-10/section-4571-repealed-pub-l-11960-div-a-title-viii-811-a-1-dec-18-2025-139-stat-948--1ac7a5dc33.md
Pages: Not recorded – Not recorded
Passage SHA-256: 2f71b1bf16a2e1c5db7d0b721cb8bee501fd11fb0b43636962eb5096ffab3799
Source location: Title 10, Chapter [CHAPTER 345, § 4571; chapter-chapter-345-chapter-chapter-345.md
Stored source content
### Statutory Notes
Section, added Pub. L. 111–383, div. A, title VIII, § 805(a)(1), Jan. 7, 2011, 124 Stat. 4259, § 2223a; renumbered § 4571 and amended Pub. L. 116–283, div. A, title XVIII, § 1857(b), Jan. 1, 2021, 134 Stat. 4276, related to information technology acquisition: planning and oversight processes.
#### Electromagnetic Spectrum Demonstration Program
Pub. L. 118–159, div. A, title II, § 234, Dec. 23, 2024, 138 Stat. 1839, which authorized a demonstration program to assess the viability of using wideband adaptive signal processing technology to support simultaneous transmit and receive signals on the same electromagnetic spectrum frequency band, was transferred and is set out as a note under [section 4001 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4001&num=0&edition=prelim).
#### Policies for Management and Certification of Link 16 Military Tactical Data Link Network
Pub. L. 118–31, div. A, title II, § 228, Dec. 22, 2023, 137 Stat. 199, as amended by Pub. L. 119–60, div. A, title II, § 216, Dec. 18, 2025, 139 Stat. 775, which directed the Secretary of Defense shall develop and implement policies to adapt Link 16 system management and certification to align with agile development practices, was transferred and is set out as a note under [section 4001 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4001&num=0&edition=prelim).
#### Requirements for Deployment of Fifth Generation Information and Communications Capabilities to Military Installations and Other Department Facilities
Pub. L. 118–31, div. A, title XV, § 1526, Dec. 22, 2023, 137 Stat. 557, which required the Secretary of Defense shall develop and implement a strategy for deploying to military installations and other facilities of the Department of Defense private wireless networks, was transferred and is set out as a note under [section 2661 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2661&num=0&edition=prelim).
#### Target Date for Deployment of 5G Wireless Broadband Infrastructure at All Military Installations
Pub. L. 117–263, div. A, title II, § 221, Dec. 23, 2022, 136 Stat. 2478, which required the Secretary of Defense to establish a target date by which the Secretary plans to deploy 5G wireless broadband infrastructure at all military installations and establish metrics, was transferred and is set out as a note under [section 2661 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2661&num=0&edition=prelim).
#### Pilot Programs for Deployment of Telecommunications Infrastructure To Facilitate 5G Deployment on Military Installations
Pub. L. 117–81, div. A, title II, § 233, Dec. 27, 2021, 135 Stat. 1614, which required each Secretary of a military department to submit a plan for a pilot program for the deployment of telecommunications infrastructure to facilitate the availability of fifth-generation wireless telecommunications services on military installations and to establish a pilot program in accordance with the plan, was transferred and is set out as a note under [section 2661 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2661&num=0&edition=prelim).
#### Legacy Information Technologies and Systems Accountability
Pub. L. 117–81, div. A, title XV, § 1522, Dec. 27, 2021, 135 Stat. 2041, which required the Secretaries of the Army, Navy, and Air Force to initiate efforts to identify legacy applications, software, and information technology within their respective Departments and eliminate any such application, software, or information technology that was no longer required, was transferred and is set out as a note under [section 2223 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2223&num=0&edition=prelim).
#### Governance of Fifth-Generation Wireless Networking in the Department of Defense
Pub. L. 116–283, div. A, title II, § 224, Jan. 1, 2021, 134 Stat. 3472, which required development of a plan to transition fifth-generation (“5G”) wireless technology to operational use within the Department of Defense, designation of the Chief Information Officer as the senior official within Department of Defense with primary responsibility for 5G wireless networking, and the establishment of a cross-functional team for 5G wireless networking, was transferred and is set out as a note under [section 2223 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2223&num=0&edition=prelim).
#### Demonstration Project on Use of Certain Technologies for Fifth-Generation Wireless Networking Services
Pub. L. 116–283, div. A, title II, § 225, Jan. 1, 2021, 134 Stat. 3475, which authorized the Secretary of Defense to carry out a demonstration project to evaluate the maturity, performance, and cost of covered technologies to provide additional options for providers of fifth-generation wireless network services, was transferred and is set out as a note under [section 2223 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2223&num=0&edition=prelim).
#### Pilot Program on the Use of Consumption-Based Solutions To Address Software-Intensive Warfighting Capability
Pub. L. 116–283, div. A, title VIII, § 834, Jan. 1, 2021, 134 Stat. 3754, which authorized the Secretary of Defense to establish a pilot program to explore the use of consumption-based solutions to address software-intensive warfighting capability, was transferred and is set out as a note under [section 3605 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3605&num=0&edition=prelim).
#### Balancing Security and Innovation in Software Development and Acquisition
Pub. L. 116–283, div. A, title VIII, § 835, Jan. 1, 2021, 134 Stat. 3755, which provided for the development of requirements for appropriate software security criteria to be included in solicitations for commercial and developmental solutions and the evaluation of bids submitted in response to such solicitations, was transferred and is set out as a note under [section 3206 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3206&num=0&edition=prelim).
#### Establishment of Secure Next-Generation Wireless Network (5G) Infrastructure for the Nevada Test and Training Range and Base Infrastructure
Pub. L. 116–92, div. A, title II, § 226, Dec. 20, 2019, 133 Stat. 1269, which required the Secretary of Defense to establish secure fifth-generation wireless network components and capabilities at no fewer than two Department of Defense installations, specifically including the Nevada Test and Training Range, was transferred and is set out as a note under [section 2661 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2661&num=0&edition=prelim).
#### Digital Engineering Capability To Automate Testing and Evaluation
Pub. L. 116–92, div. A, title II, § 231, Dec. 20, 2019, 133 Stat. 1274, which required the Secretary of Defense to establish a digital engineering capability to be used for the development and deployment of digital engineering models for use in the defense acquisition process and to provide testing infrastructure and software to support automated approaches for testing, evaluation, and deployment throughout the defense acquisition process, was transferred and is set out as a note under [section 4171 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4171&num=0&edition=prelim).
#### Strategy and Implementation Plan for Fifth Generation Information and Communications Technologies
Pub. L. 116–92, div. A, title II, § 254, Dec. 20, 2019, 133 Stat. 1287, as amended by Pub. L. 117–263, div. A, title II, § 232, Dec. 23, 2022, 136 Stat. 2486, which required the Secretary of Defense to develop a strategy for harnessing fifth generation (“5G”) information and communications technologies to enhance military capabilities, maintain a technological advantage on the battlefield, and accelerate the deployment of new commercial products and services enabled by 5G networks throughout the Department of Defense and a plan to implement such strategy, was transferred and is set out as a note under [section 2223 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2223&num=0&edition=prelim).
#### Department-Wide Software Science and Technology Strategy
Pub. L. 116–92, div. A, title II, § 255, Dec. 20, 2019, 133 Stat. 1288, as amended by Pub. L. 117–81, div. A, title II, §§ 212(c)(1), 215(d)(10), Dec. 27, 2021, 135 Stat. 1588, 1594, which required the designation of a single official or existing entity within the Department of Defense as the official or entity with principal responsibility for guiding the development of science and technology activities related to next generation software and software reliant systems for the Department, was transferred and is set out as a note under [section 4001 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4001&num=0&edition=prelim).
#### Authority for Continuous Integration and Delivery of Software Applications and Upgrades to Embedded Systems
Pub. L. 116–92, div. A, title VIII, § 800, Dec. 20, 2019, 133 Stat. 1478, which authorized establishment of pathways to provide for the efficient and effective acquisition, development, integration, and timely delivery of secure software, was repealed by Pub. L. 118–159, div. A, title VIII, § 805(c)(1), Dec. 23, 2024, 138 Stat. 1972. See [section 3603 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3603&num=0&edition=prelim).
#### Reorientation of Big Data Platform Program
Pub. L. 116–92, div. A, title XVI, § 1651, Dec. 20, 2019, 133 Stat. 1759, as amended by Pub. L. 116–283, div. A, title XVII, § 1709(a), Jan. 1, 2021, 134 Stat. 4086, which directed the Secretary of Defense to reorient the Big Data Platform program and align the reorientation effort under an existing line of effort of the Cyber Strategy of the Department of Defense, was repealed by Pub. L. 119–60, div. A, title VIII, § 811(b)(4)(C), Dec. 18, 2025, 139 Stat. 948.
#### Policy Regarding the Transition of Data and Applications to the Cloud
Pub. L. 116–92, div. A, title XVII, § 1755, Dec. 20, 2019, 133 Stat. 1854, which required the development and issuance of enterprise-wide policy and implementing instructions regarding the transition of data and applications to the cloud under the Department of Defense cloud strategy, was transferred and is set out as a note under [section 2223 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2223&num=0&edition=prelim).
#### Implementation of Recommendations of the Final Report of the Defense Science Board Task Force on the Design and Acquisition of Software for Defense Systems
Pub. L. 115–232, div. A, title VIII, § 868, Aug. 13, 2018, 132 Stat. 1902, which required the Secretary of Defense, with certain exceptions, to commence implementation of each recommendation submitted as part of the final report of the Defense Science Board Task Force on the Design and Acquisition of Software for Defense Systems, was transferred and is set out as a note under [section 3603 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3603&num=0&edition=prelim).
#### Activities and Reporting Relating to Department of Defense’s Cloud Initiative
Pub. L. 115–232, div. A, title X, § 1064, Aug. 13, 2018, 132 Stat. 1971, which required the Chief Information Officer of the Department of Defense to conduct certain key enabling activities relating to the Department of Defense’s cloud initiative and submit to the congressional defense committees a report on the initiative, was transferred and is set out as a note under [section 2223 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2223&num=0&edition=prelim).
Pub. L. 115–232, div. A, title VIII, § 869(a)–(d), Aug. 13, 2018, 132 Stat. 1902, 1903, provided that the Secretary of Defense was to include certain systems in the pilot program to use agile or iterative development methods pursuant to section 873 of Pub. L. 115–91, formerly set out below.
Pub. L. 115–91, div. A, title VIII, § 873, Dec. 12, 2017, 131 Stat. 1498, as amended by Pub. L. 115–232, div. A, title VIII, § 869(e), Aug. 13, 2018, 132 Stat. 1903, provided that the Secretary of Defense was to establish a pilot program to tailor and simplify software development requirements and methods for major software-intensive warfighting systems and defense business systems, and that such pilot program would terminate on Sept. 30, 2023.
#### Global Theater Security Cooperation Management Information System
Pub. L. 115–91, div. A, title XII, § 1272, Dec. 12, 2017, 131 Stat. 1695, which directed the Secretary of Defense, not later than 180 days after Dec. 12, 2017, to update relevant security cooperation guidance for the Global Theater Security Cooperation Management Information System and submit a report to the congressional defense committees, was repealed by Pub. L. 119–60, div. A, title VIII, § 811(b)(6)(D), Dec. 18, 2025, 139 Stat. 948.
#### Operational Metrics for Joint Information Environment and Supporting Activities
Pub. L. 113–291, div. A, title VIII, § 854, Dec. 19, 2014, 128 Stat. 3459, which directed the Secretary of Defense, acting through the Chief Information Officer of the Department of Defense, not later than 180 days after Dec. 19, 2014, to issue guidance for measuring the operational effectiveness and efficiency of the Joint Information Environment within the military departments, Defense Agencies, and combatant commands, was repealed by Pub. L. 119–60, div. A, title VIII, § 811(b)(9), Dec. 18, 2025, 139 Stat. 949.
#### Data Servers and Centers
Pub. L. 112–81, div. B, title XXVIII, § 2867, Dec. 31, 2011, 125 Stat. 1704, as amended by Pub. L. 112–239, div. B, title XXVIII, § 2853, Jan. 2, 2013, 126 Stat. 2161; Pub. L. 115–91, div. A, title X, § 1051(q)(3), Dec. 12, 2017, 131 Stat. 1565, which prohibited a department, agency, or component of the Department of Defense from obligating funds for a data server farm or data center from Dec. 31, 2011, to May 1, 2012, unless approved by the Chief Information Officer of the Department of Defense or the Chief Information Officer of a component of the Department to whom the Chief Information Officer had delegated such approval authority, was repealed by Pub. L. 119–60, div. A, title VIII, § 811(b)(11), Dec. 18, 2025, 139 Stat. 949.
#### Demonstration and Pilot Projects on Cybersecurity
Pub. L. 111–383, div. A, title II, § 215, Jan. 7, 2011, 124 Stat. 4165, which directed the Secretary of Defense and Secretaries of the military departments to jointly carry out demonstration projects on processes for application of commercial technologies to cybersecurity requirements and for the Secretary of Defense to support or conduct pilot programs on cybersecurity, was repealed Pub. L. 119–60, div. A, title VIII, § 811(b)(12)(A), Dec. 18, 2025, 139 Stat. 949.
#### Implementation of New Acquisition Process for Information Technology Systems
Pub. L. 111–84, div. A, title VIII, § 804, Oct. 28, 2009, 123 Stat. 2402, which provided for development and implementation of a new acquisition process for information technology systems, was repealed by Pub. L. 115–232, div. A, title VIII, § 812(b)(2), Aug. 13, 2018, 132 Stat. 1848, and Pub. L. 119–60, div. A, title VIII, § 811(b)(13)(A), Dec. 18, 2025, 139 Stat. 949.
#### Clearinghouse for Rapid Identification and Dissemination of Commercial Information Technologies
Pub. L. 110–181, div. A, title VIII, § 881, Jan. 28, 2008, 122 Stat. 262, which directed the Secretary of Defense, acting through the Assistant Secretary of Defense for Networks and Information Integration, not later than 180 days after Jan. 28, 2008, to establish a clearinghouse for rapidly identifying, assessing, and disseminating knowledge about readily available information technologies, was repealed by Pub. L. 119–60, div. A, title VIII, § 811(b)(15)(D), Dec. 18, 2025, 139 Stat. 949.
#### Improvement of Software Acquisition Processes
Pub. L. 107–314, div. A, title VIII, § 804, Dec. 2, 2002, 116 Stat. 2604, which directed the Secretary of each military department to establish a program to improve the software acquisition processes of that military department, was repealed by Pub. L. 119–60, div. A, title VIII, § 811(b)(19)(B), Dec. 18, 2025, 139 Stat. 949.
Cross-references
Connections may be documented source relationships, shared citations or nearby passages. Each explains its basis; a connection alone does not establish applicability to your situation.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Additional Responsibilities of Chief Information Officer of Department of Defense.—** In addition to the responsibilities provided for in chapter 35 of title 44 and in [section 11315 of title 40](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title40-section11315&num=0&edition=prelim), the Chief Information Officer of the Department of Defense shall—
(1) review and provide recommendations to the Secretary of Defense on Department of Defense budget requests for information technology and national security systems;
(2) ensure the interoperability of information technology and national security systems throughout the Department of Defense;
(3) ensure that information technology and national security systems standards that will apply throughout the Department of Defense are prescribed;
(4) provide for the elimination of duplicate information technology and national security systems within and between the military departments and Defense Agencies; and
(5) maintain a consolidated inventory of Department of Defense mission critical and mission essential information systems, identify interfaces between those systems and other information systems, and develop and maintain contingency plans for responding to a disruption in the operation of any of those information systems.
**(b) Additional Responsibilities of Chief Information Officer of Military Departments.—** In addition to the responsibilities provided for in chapter 35 of title 44 and in [section 11315 of title 40](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title40-section11315&num=0&edition=prelim), the Chief Information Officer of a military department, with respect to the military department concerned, shall—
(1) review budget requests for all information technology and nation
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 2223
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Condition for Proceeding Beyond Low-rate Initial Production.—**
(1) The Secretary of Defense shall provide that a covered major defense acquisition program, a covered designated major subprogram, or an element of the ballistic missile defense system may not proceed beyond low-rate initial production until initial operational test and evaluation of the program, subprogram, or element is completed.
(2) In this subsection:
(A) The term “covered major defense acquisition program” means a major defense acquisition program that involves the acquisition of a weapon system that is a major system.
(B) The term “covered designated major subprogram” means a major subprogram designated under [section 4203(a)(1) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4203/a/1&num=0&edition=prelim) that is a major subprogram of a covered major defense acquisition program.
**(b) Operational Test and Evaluation.—**
(1) Operational testing of a major defense acquisition program may not be conducted until the Director of Operational Test and Evaluation of the Department of Defense approves (in writing) the adequacy of the plans (including the projected level of funding) for operational test and evaluation to be conducted in connection with that program.
(2) The Director shall analyze the results of the operational test and evaluation conducted for each major defense acquisition program. At the conclusion of such testing, the Director shall prepare a report stating—
(A) the opinion of the Director as to—
(i) whether the test and evaluation performed were adequate; and
(ii) whether the results of such test and evaluation confirm that the items or components actually tested are effective and suitable for combat; and
(B) add
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 4171
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Software Acquisition and Development Pathways.—** The Secretary of Defense shall establish pathways as described under subsection (b) to provide for the efficient and effective acquisition, development, integration, and timely delivery of software and covered hardware.
**(b) Pathways.—** The Secretary of Defense may establish as many pathways under this section as the Secretary determines appropriate and shall establish the following pathways:
(1) **Applications.—** — The applications pathway shall provide for the use of rapid development and implementation of applications and other software or software improvements operated by the Department of Defense, which may include applications and associated procurement of covered hardware (including modifications of a type not customarily available in the commercial marketplace to meet Department requirements), commercially available cloud computing platforms, and other nondevelopmental items.
(2) **Embedded systems.—** — The embedded systems pathway shall provide for the rapid development and insertion of upgrades and improvements for software and covered hardware embedded in weapon systems and other hardware systems unique to the Department of Defense.
**(c) Requirements for Pathways.—** A pathway established under this section shall provide for the use of proven technologies and solutions to continuously engineer and deliver capabilities for software and covered hardware.
**(d) Considerations for Use of Authority.—** In using the authority under this section, the Secretary shall consider how such use will—
(1) initiate the engineering of new software capabilities quickly and, if applicable, the integration of such capabilities into covered hardware;
(2) demonstrate the viability and effectiveness of such capabil
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 3603
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Availability of Operation and Maintenance Funds.—** Appropriations for operation and maintenance of the active forces shall be available for the following:
(1) The repair of facilities.
(2) The installation of equipment in public and private plants.
**(b) Leasing and Road Maintenance Authority.—** The Secretary of Defense and the Secretary of each military department may provide for the following:
(1) The leasing of buildings and facilities (including the payment of rentals for special purpose space at the seat of Government). Rental for such leases may be paid in advance in connection with—
(A) the conduct of field exercises and maneuvers; and
(B) the administration of the Act of July 9, 1942 ([43 U.S.C. 315q](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title43-section315q&num=0&edition=prelim)).
(2) The maintenance of defense access roads which are certified to the Secretary of Transportation as important to the national defense under the provisions of [section 210 of title 23](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title23-section210&num=0&edition=prelim).
**(c) Prohibition on Naming Department of Defense Real Property After Member of Congress.—**
(1) Real property under the jurisdiction of the Secretary of Defense or the Secretary of a military department may not be named after, or otherwise officially identified by the name of, any individual who is a Member of Congress at the time the property is so named or identified.
(2) In this subsection:
(A) The term “Member of Congress” includes a Delegate or Resident Commissioner to the Congress.
(B) The term “real property” includes structures, buildings, or other infrastructure of a military installation, roadways and defense access roads, and any other are
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 2661
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Authority.—** The Secretary of Defense and the Secretaries of the military departments may acquire services through consumption-based solutions.
**(b) Guidance Required.—** The Secretary of Defense shall amend the Department of Defense Supplement to the Federal Acquisition Regulation to implement the authority under subsection (a), including creating a new subcategory of services under part 237 of the Department of Defense Supplement to the Federal Acquisition Regulation, entitled “Consumption-based solutions”, that—
(1) is any combination of hardware, equipment, software, labor, or services that together provides a seamless capability;
(2) has the ability to be metered and billed based on actual usage;
(3) has predetermined pricing at fixed-price units;
(4) requires the awardee to notify the Department of Defense contracting officer when consumption under the contract reaches 75 percent and 90 percent of the funded amount, respectively, of the contract; and
(5) treats modifications to a contract entered into under the authority established in subsection (a) to add new features or capabilities in an amount less than or equal to 25 percent of the total value of such contract, as originally awarded, as procurements made using competitive procedures for the purposes of chapter 221 of this title.
**(c) Funding.—** Amounts authorized to be appropriated for acquisitions using the authority under subsection (a)—
(1) may be used for expenses for—
(A) research, development, test and evaluation;
(B) procurement;
(C) production;
(D) modification; and
(E) operation and maintenance; and
(2) may be used to enter into incrementally funded contracts or other agreements, including advanced payments.
**(d) Consumption-based Solution Defined.—** In this sect
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 3605
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Authority.—** The Secretary of Defense or the Secretary of a military department may engage in basic research, applied research, advanced research, and development projects that—
(1) are necessary to the responsibilities of such Secretary’s department in the field of research and development; and
(2) either—
(A) relate to weapon systems and other military needs; or
(B) are of potential interest to the Department of Defense.
**(b) Authorized Means.—** The Secretary of Defense or the Secretary of a military department may perform research and development projects—
(1) by contract, cooperative agreement, or grant, in accordance with chapter 63 of title 31;
(2) through one or more military departments;
(3) by using employees and consultants of the Department of Defense;
(4) by mutual agreement with the head of any other department or agency of the Federal Government;
(5) by transactions (other than contracts, cooperative agreements, and grants) entered into pursuant to section 4021 or 4022 of this title; or
(6) by purchases through procurement for experimental purposes pursuant to [section 4023 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4023&num=0&edition=prelim).
**(c) Requirement of Potential Department of Defense Interest.—** Funds appropriated to the Department of Defense or to a military department may not be used to finance any research project or study unless the project or study is, in the opinion of the Secretary of Defense or the Secretary of that military department, respectively, of potential interest to the Department of Defense or to such military department, respectively.
**(d) Additional Provisions Applicable to Cooperative Agreements.—** Additional authorities, conditions, and requiremen
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 4001
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Planning and Specifications.—**
(1) **Preparing for procurement.—** — In preparing for the procurement of property or services, the head of an agency shall—
(A) specify the agency’s needs and solicit bids or proposals in a manner designed to achieve full and open competition for the procurement;
(B) use advance procurement planning and market research; and
(C) develop specifications in such manner as is necessary to obtain full and open competition with due regard to the nature of the property or services to be acquired.
(2) **Requirements of specifications.—** — Each solicitation under chapter 137 legacy provisions shall include specifications which—
(A) consistent with the provisions of chapter 137 legacy provisions, permit full and open competition; and
(B) include restrictive provisions or conditions only to the extent necessary to satisfy the needs of the agency or as authorized by law.
(3) **Types of specifications.—** — For the purposes of paragraphs (1) and (2), the type of specification included in a solicitation shall depend on the nature of the needs of the agency and the market available to satisfy such needs. Subject to such needs, specifications may be stated in terms of—
(A) function, so that a variety of products or services may qualify;
(B) performance, including specifications of the range of acceptable characteristics or of the minimum acceptable standards; or
(C) design requirements.
**(b) Contents of solicitation.—** In addition to the specifications described in subsection (a), a solicitation for sealed bids or competitive proposals (other than for a procurement for commercial products or commercial services using special simplified procedures or a purchase for an amount not greater than the simplified acquisition
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 3206
Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Establishment.—**
(1) With the advice and assistance of the Chairman of the Joint Chiefs of Staff, the President, through the Secretary of Defense, shall establish under [section 161 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section161&num=0&edition=prelim) a unified combatant command for cyber operations forces (hereinafter in this section referred to as the “United States Cyber Command”).
(2) The principal mission of the United States Cyber Command is to direct, synchronize, and coordinate military cyberspace planning and operations to defend and advance national interests in collaboration with domestic and international partners.
**(b) Assignment of Forces.—**
(1) Active and reserve cyber forces of the armed forces shall be assigned to the United States Cyber Command through the Global Force Management Process, as approved by the Secretary of Defense.
(2) Cyber forces not assigned to United States Cyber Command remain assigned to combatant commands or service-retained.
**(c) Grade of Commander.—** The Commander of the United States Cyber Command shall hold the grade of general or, in the case of an officer of the Navy, admiral while serving in that position, without vacating that officer’s permanent grade. The Commander of such Command shall be appointed to that grade by the President, by and with the advice and consent of the Senate, for service in that position.
**(d) Authority of Combatant Commander.—**
(1) In addition to the authority prescribed in [section 164(c) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section164/c&num=0&edition=prelim), the Commander of the United States Cyber Command shall be responsible for, and shall have the authority to conduct, all affairs
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 167b
Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Defense Acquisition University Structure.—** The Secretary of Defense, acting through the Under Secretary of Defense for Acquisition and Sustainment, shall establish and maintain a defense acquisition university structure to provide for—
(1) the professional educational development and training of the acquisition workforce; and
(2) research and analysis of defense acquisition policy issues from an academic perspective.
**(b) Civilian Faculty Members.—**
(1) The Secretary of Defense may employ as many civilians as professors, instructors, and lecturers in the defense acquisition university structure as the Secretary considers necessary.
(2) The Secretary of Defense shall ensure the defense acquisition university structure includes relevant expert lecturers from extramural institutions (as defined in [section 1746a(g) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section1746a/g&num=0&edition=prelim)), industry, or federally funded research and development centers to advance acquisition workforce competence regarding commercial business interests, acquisition process-related innovations, and other relevant leading practices of the private sector.
(3) The compensation of persons employed under this subsection shall be as prescribed by the Secretary.
(4) In this subsection, the term “defense acquisition university” includes the Defense Systems Management College.
**(c) Curriculum Development.—** The President of the Defense Acquisition University shall work with the relevant professional schools and degree-granting institutions of the Department of Defense and military departments, and with extramural institutions (as defined in [section 1746a(g) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-ti
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 1746
Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.
Federal law — U.S. Code and appendices · legal_authorities
**(a) Training Program.—** Not later than 180 days after the date of the enactment of this section, the Under Secretary for Acquisition and Sustainment shall establish a training program that supports cross-functional personnel and contractors of the Department of Defense involved in any phase of the acquisition and sustainment lifecycle in making important decisions with respect to acquisition or sustainment, including requirements validation, the development of an acquisition strategy, awarding contracts, and ongoing management of performance and governance.
**(b) Elements.—** The training program established under subsection (a) shall—
(1) create deployable training teams to coach the cross-functional personnel and contractors described in subsection (a) and facilitate such personnel and contractors successfully completing a phase of an acquisition or sustainment effort with the same training team to the maximum extent possible;
(2) to the extent practicable, ensure that the same training team under paragraph (1) provides the support described under such paragraph with respect to a phase of an acquisition or sustainment effort until such phase is completed or otherwise ends;
(3) provide to the cross-functional personnel and contractors described in subsection (a) short, intermittent lessons on innovative acquisition and fielding procedures, flexible contracting frameworks, and business negotiation skills that are timed to align the topics of the lessons to relevant activities under a phase of an acquisition or sustainment effort;
(4) emphasize—
(A) the acquisition of commercial products, commercial services, and commercially available off-the-shelf items (as such terms are defined in sections 103, 103a, and 104, respectively, of title 41);
(B) technology p
Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 1749
Stored review status: release_metadata_unconfirmed. Incoming connection: Explicit cross-reference supplied in source Markdown; currentness and applicability require review.