Arkansas Legal Resource Navigator

10 U.S.C. § 4171 — Operational test and evaluation of defense acquisition programs

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 4171 — Operational test and evaluation of defense acquisition programs

**(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. A text match is a research starting point; applicability is not established.

Original supplied file — preserved unchanged

Download original Markdown file

File SHA-256: d0d71af088150d0836962591d6ff71185eda4635b7803c29e6988a4cca756901. 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_0e15de06aa2f967fb8a0617e
Source file: Laws/federal/codes/united-states-code/title-10/section-4171-operational-test-and-evaluation-of-defense-acquisition-programs--b8792c5cfd.md
Pages: Not recorded – Not recorded
Passage SHA-256: 0c39b3ad11a6dd75e73bd527e8e22749a17066d2ad83085c16f44f3df8a7e185

Source location: Title 10, Chapter 307, § 4171; chapter-307-test-and-evaluation.md

Stored source content

**(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) additional information on the operational capabilities of the items or components that the Director considers appropriate based on the testing conducted. (3) The Director shall submit each report under paragraph (2) to the Secretary of Defense, the Under Secretary of Defense for Acquisition and Sustainment, the Under Secretary of Defense for Research and Engineering, and the congressional defense committees. Each such report shall be submitted to those committees in precisely the same form and with precisely the same content as the report originally was submitted to the Secretary and Under Secretary and shall be accompanied by such comments as the Secretary may wish to make on the report. (4) A final decision within the Department of Defense to proceed with a major defense acquisition program beyond low-rate initial production may not be made until the Director has submitted to the Secretary of Defense the report with respect to that program under paragraph (2) and the congressional defense committees have received that report. (5) If, before a final decision described in paragraph (4) is made for a major defense acquisition program, a decision is made within the Department of Defense to proceed to operational use of that program or to make procurement funds available for that program, the Director shall submit to the Secretary of Defense and the congressional defense committees the report with respect to that program under paragraph (2) as soon as practicable after the decision described in this paragraph is made. (6) In this subsection, the term “major defense acquisition program” has the meaning given that term in [section 139(a)(2)(B) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section139/a/2/B&num=0&edition=prelim). **(c) Determination of Quantity of Articles Required for Operational Testing.—** The quantity of articles of a new system that are to be procured for operational testing shall be determined by— (1) the Director of Operational Test and Evaluation of the Department of Defense, in the case of a new system that is a major defense acquisition program (as defined in [section 139(a)(2)(B) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section139/a/2/B&num=0&edition=prelim)); or (2) the operational test and evaluation agency of the military department concerned, in the case of a new system that is not a major defense acquisition program. **(d) Impartiality of Contractor Testing Personnel.—** In the case of a major defense acquisition program (as defined in subsection (a)(2)), no person employed by the contractor for the system being tested may be involved in the conduct of the operational test and evaluation required under subsection (a). The limitation in the preceding sentence does not apply to the extent that the Secretary of Defense plans for persons employed by that contractor to be involved in the operation, maintenance, and support of the system being tested when the system is deployed in combat. **(e) Impartial Contracted Advisory and Assistance Services.—** (1) The Director may not contract with any person for advisory and assistance services with regard to the test and evaluation of a system if that person participated in (or is participating in) the development, production, or testing of such system for a military department or Defense Agency (or for another contractor of the Department of Defense). (2) The Director may waive the limitation under paragraph (1) in any case if the Director determines in writing that sufficient steps have been taken to ensure the impartiality of the contractor in providing the services. The Inspector General of the Department of Defense shall review each such waiver and shall include in the Inspector General’s semi-annual report an assessment of those waivers made since the last such report. (3) (A) A contractor that has participated in (or is participating in) the development, production, or testing of a system for a military department or Defense Agency (or for another contractor of the Department of Defense) may not be involved (in any way) in the establishment of criteria for data collection, performance assessment, or evaluation activities for the operational test and evaluation. (B) The limitation in subparagraph (A) does not apply to a contractor that has participated in such development, production, or testing solely in testing for the Federal Government. **(f) Source of Funds for Testing.—** The costs for all tests required under subsection (a) shall be paid from funds available for the system being tested. **(g) Director’s Annual Report.—** As part of the annual report of the Director under [section 139 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section139&num=0&edition=prelim), the Director shall describe for each program covered in the report the status of test and evaluation activities in comparison with the test and evaluation master plan for that program, as approved by the Director. The Director shall include in such annual report a description of each waiver granted under subsection (e)(2) since the last such report. **(h) Operational Test and Evaluation Defined.—** In this section, the term “operational test and evaluation” has the meaning given that term in [section 139(a)(2)(A) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section139/a/2/A&num=0&edition=prelim). For purposes of subsection (a), that term does not include an operational assessment based exclusively on— (1) computer modeling; (2) simulation; or (3) an analysis of system requirements, engineering proposals, design specifications, or any other information contained in program documents.

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

10 U.S.C. § 111 — Executive department

**(a)** The Department of Defense is an executive department of the United States. **(b)** The Department is composed of the following: (1) The Office of the Secretary of Defense. (2) The Joint Chiefs of Staff. (3) The Joint Staff. (4) The Defense Agencies. (5) Department of Defense Field Activities. (6) The Department of the Army. (7) The Department of the Navy. (8) The Department of the Air Force. (9) The unified and specified combatant commands. (10) Such other offices, agencies, activities, and commands as may be established or designated by law or by the President. (11) All offices, agencies, activities, and commands under the control or supervision of any element named in paragraphs (1) through (10). **(c)** If the President establishes or designates an office, agency, activity, or command in the Department of Defense of a kind other than those described in paragraphs (1) through (9) of subsection (b), the President shall notify Congress not later than 60 days thereafter.

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 111

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

10 U.S.C. § 4201 — Major defense acquisition programs: definition; exceptions

**(a) Definition.—** Except as provided under subsection (b), in this part, the term “major defense acquisition program” means a Department of Defense acquisition program that is not a highly sensitive classified program (as determined by the Secretary of Defense) and— (1) that is designated by the Secretary of Defense as a major defense acquisition program; or (2) in the case of a program that is not a program for the acquisition of an automated information system (either a product or a service), that is estimated by the Secretary of Defense to require— (A) an eventual total expenditure for research, development, test, and evaluation of more than $1,000,000,000 (based on fiscal year 2024 constant dollars); or (B) an eventual total expenditure for procurement, including all planned increments or spirals, of more than $4,500,000,000 (based on fiscal year 2024 constant dollars). **(b) Exceptions.—** In this part, the term “major defense acquisition program” does not include the following: (1) An acquisition program or project that is carried out using the rapid fielding or rapid prototyping acquisition pathway under [section 3602 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3602&num=0&edition=prelim). (2) An acquisition program for a defense business system (as defined in [section 2222(i)(1) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2222/i/1&num=0&edition=prelim)) carried out using the acquisition guidance issued pursuant to section 883(e) of the National Defense Authorization Act for Fiscal Year 2016 (Public Law 114–92; [10 U.S.C. 2223a](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2223a&num=0&edition=prelim) note).11 See References in

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 4201

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

10 U.S.C. § 3603 — Software acquisition pathways

**(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

10 U.S.C. § 3041 — Major system

**(a) In General.—** In this part (other than in sections 4292(e) and 4321), the term “major system” means a combination of elements that will function together to produce the capabilities required to fulfill a mission need. The elements may include hardware, equipment, software or any combination thereof, but excludes construction or other improvements to real property. **(b) System Considered to Be a Major System.—** A system shall be considered a major system if— (1) the conditions of subsection (c) or (d), as applicable, are satisfied; or (2) the system is designated a “major system” by the head of the agency responsible for the system. **(c) Department of Defense Systems.—** (1) **In general.—** — For purposes of subsection (b), a system for which the Department of Defense is responsible shall be considered a major system if— (A) the total expenditures for research, development, test, and evaluation for the system are estimated to be more than $275,000,000 (based on fiscal year 2024 constant dollars); or (B) the eventual total expenditure for procurement for the system is estimated to be more than $1,300,000,000 (based on fiscal year 2024 constant dollars). (2) **Adjustment authority.—** — Authority for the Secretary of Defense to adjust amounts and the base fiscal year in effect under this subsection is provided in [section 4202(b) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section4202/b&num=0&edition=prelim). **(d) Civilian Agency Systems.—** For purposes of subsection (b), a system for which a civilian agency is responsible shall be considered a major system if total expenditures for the system are estimated to exceed the greater of— (1) $2,000,000 (based on fiscal year 2024 constant dollars); or (2) the do

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 3041

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

10 U.S.C. § 2399 — Renumbered § 4171]

### Statutory Notes #### Prior Provisions A prior section 2399, added Pub. L. 97–295, § 1(29)(A), Oct. 12, 1982, 96 Stat. 1293, which related to limitation on availability of appropriations to reimburse a contractor for the cost of commercial insurance, was repealed by Pub. L. 100–370, § 1(f)(2)(B), July 19, 1988, 102 Stat. 846, and was restated in [section 2324(e)(1)(L) of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section2324/e/1/L&num=0&edition=prelim) (now [10 U.S.C. 3744(a)(12)](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3744/a/12&num=0&edition=prelim)) by section 1(f)(2)(A) of Pub. L. 100–370.

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 2399

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

10 U.S.C. § 3001 — Defense acquisition system; element of the defense acquisition system

**(a) Defense Acquisition System.—** In this part, the term “defense acquisition system” means— (1) the workforce engaged in carrying out the acquisition of property and services for the Department of Defense; (2) the management structure responsible for directing and overseeing the acquisition of property and services for the Department of Defense; and (3) the statutory, regulatory, and policy framework that guides the acquisition of property and services for the Department of Defense. **(b) Element of the Defense Acquisition System.—** In this part, the term “element of the defense acquisition system” means an organization that— (1) employs members of the acquisition workforce; (2) carries out acquisition functions; and (3) focuses primarily on acquisition. **(c) Acquisition.—** In this part, the term “acquisition” has the meaning provided in [section 131 of title 41](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title41-section131&num=0&edition=prelim).

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 3001

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

10 U.S.C. § 2302 — Repealed. Pub. L. 116–283, div. A, title XVIII, § 1806(d), Jan. 1, 2021, 134 Stat. 4155]

### Statutory Notes Section, act Aug. 10, 1956, ch. 1041, 70A Stat. 127; Pub. L. 85–568, title III, § 301(b), July 29, 1958, 72 Stat. 432; Pub. L. 85–861, § 1(43A), Sept. 2, 1958, 72 Stat. 1457; Pub. L. 96–513, title V, § 511(74), Dec. 12, 1980, 94 Stat. 2926; Pub. L. 98–369, div. B, title VII, § 2722(a), July 18, 1984, 98 Stat. 1186; Pub. L. 98–525, title XII, § 1211, Oct. 19, 1984, 98 Stat. 2589; Pub. L. 98–577, title V, § 504(b)(3), Oct. 30, 1984, 98 Stat. 3087; Pub. L. 99–661, div. A, title XIII, § 1343(a)(13), Nov. 14, 1986, 100 Stat. 3993; Pub. L. 100–26, § 7(k)(2), Apr. 21, 1987, 101 Stat. 284; Pub. L. 101–189, div. A, title VIII, § 853(b)(1), Nov. 29, 1989, 103 Stat. 1518; Pub. L. 102–25, title VII, § 701(d)(1), Apr. 6, 1991, 105 Stat. 113; Pub. L. 102–190, div. A, title VIII, § 805, Dec. 5, 1991, 105 Stat. 1417; Pub. L. 103–355, title I, § 1502, Oct. 13, 1994, 108 Stat. 3296; Pub. L. 104–106, div. D, title XLIII, § 4321(b)(3), Feb. 10, 1996, 110 Stat. 672; Pub. L. 104–201, div. A, title VIII, §§ 805(a)(1), 807(a), Sept. 23, 1996, 110 Stat. 2605, 2606; Pub. L. 105–85, div. A, title VIII, § 803(b), Nov. 18, 1997, 111 Stat. 1832; Pub. L. 107–217, § 3(b)(2), Aug. 21, 2002, 116 Stat. 1295; Pub. L. 107–296, title XVII, § 1704(b)(1), Nov. 25, 2002, 116 Stat. 2314; Pub. L. 111–350, § 5(b)(8), Jan. 4, 2011, 124 Stat. 3842; Pub. L. 111–383, div. A, title VIII, § 866(g)(1), Jan. 7, 2011, 124 Stat. 4298; Pub. L. 113–291, div. A, title X, § 1071(a)(2), Dec. 19, 2014, 128 Stat. 3504; Pub. L. 114–92, div. A, title VIII, § 815(b), Nov. 25, 2015, 129 Stat. 896; Pub. L. 115–91, div. A, title II, § 221, Dec. 12, 2017, 131 Stat. 1333; Pub. L. 115–232, div. A, title VIII, § 836(c)(1), Aug. 13, 2018, 132 Stat. 1864; Pub. L. 116–283, div. A, title XVIII, § 1806(a)(5), (6), (b)(2)–(6

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 2302

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

10 U.S.C. § 2430 — Repealed. Pub. L. 116–283, div. A, title XVIII, § 1846(f)(8), Jan. 1, 2021, 134 Stat. 4251]

### Statutory Notes Section, added Pub. L. 100–26, § 7(b)(2)(A), Apr. 21, 1987, 101 Stat. 279; amended Pub. L. 102–484, div. A, title VIII, § 817(b), Oct. 23, 1992, 106 Stat. 2455; Pub. L. 104–106, div. A, title XV, § 1502(a)(1), Feb. 10, 1996, 110 Stat. 502; Pub. L. 106–65, div. A, title X, § 1067(1), Oct. 5, 1999, 113 Stat. 774; Pub. L. 111–23, title II, § 206(b), May 22, 2009, 123 Stat. 1728; Pub. L. 113–291, div. A, title X, § 1071(f)(18), Dec. 19, 2014, 128 Stat. 3511; Pub. L. 114–92, div. A, title VIII, § 825(a), Nov. 25, 2015, 129 Stat. 907; Pub. L. 114–328, div. A, title VIII, §§ 807(b), 847(a), Dec. 23, 2016, 130 Stat. 2261, 2292; Pub. L. 115–91, div. A, title VIII, § 831, title X, § 1081(a)(38), Dec. 12, 2017, 131 Stat. 1467, 1596; Pub. L. 116–283, div. A, title XVIII, § 1846(c)(1), (d)(1), (f)(1), Jan. 1, 2021, 134 Stat. 4248–4250, defined major defense acquisition program. See sections 4201, 4202(a), and 4204 of this title. #### Effective Date of Repeal Repeal effective Jan. 1, 2022, with additional provisions for delayed implementation and applicability of existing law, see section 1801(d) of Pub. L. 116–283, set out as a note preceding [section 3001 of this title](https://uscode.house.gov/view.xhtml?req=granuleid:USC-prelim-title10-section3001&num=0&edition=prelim).

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 2430

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

10 U.S.C. § 4571 — Repealed. Pub. L. 119–60, div. A, title VIII, § 811(a)(1), Dec. 18, 2025, 139 Stat. 948]

### 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. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.

Federal law — U.S. Code and appendices · legal_authorities

10 U.S.C. § 4401 — Requirement for modular open system approach in major defense acquisition programs; definitions

**(a) Modular Open System Approach Requirement.—** A major defense acquisition program that receives Milestone A or Milestone B approval after January 1, 2019, shall be designed and developed, to the maximum extent practicable, with a modular open system approach to enable incremental development and enhance competition, innovation, and interoperability. Other defense acquisition programs shall also be designed and developed, to the maximum extent practicable, with a modular open system approach to enable incremental development and enhance competition, innovation, and interoperability. **(b) Disclosure Required.—** Not later than one year after the date of the enactment of this subsection, the Secretary of Defense shall make publicly available any standards for implementation of the modular open system approaches for contracts, unless the service acquisition executive with respect to a specific contract submits to the Secretary a request to not disclose such standards and the Secretary approves such request. **(c) Definitions.—** In this chapter: (1) The term “modular open system approach” means, with respect to a major defense acquisition program, an integrated business and technical strategy that— (A) employs a modular design that uses modular system interfaces between major systems, major system components and modular systems; (B) is subjected to verification to ensure that relevant modular system interfaces— (i) comply with, if available and suitable, widely supported and consensus-based standards; or (ii) are delivered pursuant to the requirements established in subsection (a)(2)(B) of section 804 of the William M. (Mac) Thornberry National Defense Authorization Act for Fiscal Year 2021, including the delivery of— (I) software-defined int

Source: Supplied U.S. Code snapshot — release unconfirmed · 10 U.S.C. § 4401

Stored review status: release_metadata_unconfirmed. Explicit cross-reference supplied in source Markdown; currentness and applicability require review.