(a)
(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 that is a major subprogram of a covered major defense acquisition program.
(b)
(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.
(c)
(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); 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)
(e)
(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)
(g)
(h)
(1) computer modeling;
(2) simulation; or
(3) an analysis of system requirements, engineering proposals, design specifications, or any other information contained in program documents.
Editorial Notes
Amendments
2021—Pub. L. 116–283, §1845(b), as amended by Pub. L. 117–81, §1701(u)(6)(B), renumbered section 2399 of this title as this section.
Subsec. (a)(2)(A). Pub. L. 117–81, §1701(d)(10)(A), struck out "within the meaning of that term in section 3041 of this title" before period at end.
Pub. L. 116–283, §1883(b)(2), substituted "section 3041" for "section 2302(5)".
Subsec. (a)(2)(B). Pub. L. 117–81, §1701(d)(10)(B), which directed the substitution of "under section 4203(a)(1) of this title" for "under" and all that followed through "this title", was not executed in light of the prior amendment by section 1883(b)(2) of Pub. L. 116—283, to reflect the probable intent of Congress. See note below.
Pub. L. 116–283, §1883(b)(2), substituted "section 4203(a)(1)" for "section 2430a(a)(1)".
2019—Subsec. (b)(3). Pub. L. 116–92 substituted "Under Secretary of Defense for Acquisition and Sustainment, the Under Secretary of Defense for Research and Engineering," for "Under Secretary of Defense for Acquisition, Technology, and Logistics,".
2017—Subsec. (a)(1). Pub. L. 115–91 substituted ", a covered designated major subprogram, or an element of the ballistic missile defense system" for "or a covered designated major subprogram" and "program, subprogram, or element" for "program or subprogram".
2011—Subsec. (a). Pub. L. 111–383 amended subsec. (a) generally. Prior to amendment, text read as follows:
"(1) The Secretary of Defense shall provide that a major defense acquisition program may not proceed beyond low-rate initial production until initial operational test and evaluation of the program is completed.
"(2) In this subsection, the term 'major defense acquisition program' means a conventional weapons system that—
"(A) is a major system within the meaning of that term in section 2302(5) of this title; and
"(B) is designed for use in combat."
2006—Subsec. (b)(2). Pub. L. 109–364, §231(a)(1), amended par. (2) generally. Prior to amendment, par. (2) read as follows: "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 the opinion of the Director as to—
"(A) whether the test and evaluation performed were adequate; and
"(B) whether the results of such test and evaluation confirm that the items or components actually tested are effective and suitable for combat."
Subsec. (b)(5), (6). Pub. L. 109–364, §231(a)(2), (3), added par. (5) and redesignated former par. (5) as (6).
2003—Subsec. (h). Pub. L. 108–136 substituted "Operational Test and Evaluation Defined" for "Definitions" in heading, struck out introductory provisions which read "In this section:", substituted "In this section, the term" for "(1) The term", redesignated subpars. (A) to (C) of former par. (1) as pars. (1) to (3), respectively, realigned margins, and struck out former par. (2) which defined "congressional defense committees" to mean the Committees on Armed Services and Appropriations of the Senate and the House of Representatives.
2002—Subsec. (a)(2). Pub. L. 107–314 substituted "means a conventional weapons system that" for "means" in introductory provisions and struck out "a conventional weapons system that" before "is a major system" in subpar. (A).
2001—Subsec. (b)(3). Pub. L. 107–107 substituted "Under Secretary of Defense for Acquisition, Technology, and Logistics" for "Under Secretary of Defense for Acquisition and Technology".
1999—Subsec. (h)(2)(B). Pub. L. 106–65 substituted "Committee on Armed Services" for "Committee on National Security".
1996—Subsec. (h)(2). Pub. L. 104–106 substituted "means—" and subpars. (A) and (B) for "means the Committees on Armed Services and the Committees on Appropriations of the Senate and House of Representatives."
1994—Subsecs. (b)(5), (c)(1). Pub. L. 103–337, §1070(a)(11)(A), substituted "139(a)(2)(B)" for "138(a)(2)(B)".
Subsec. (e)(3)(B). Pub. L. 103–337, §1070(f), substituted "solely in testing for" for "solely as a representative of".
Subsec. (g). Pub. L. 103–337, §1070(a)(11)(B), substituted "139" for "138".
Subsec. (h)(1). Pub. L. 103–337, §1070(a)(11)(C), substituted "139(a)(2)(A)" for "138(a)(2)(A)".
1993—Subsec. (b)(3). Pub. L. 103–160 substituted "Under Secretary of Defense for Acquisition and Technology" for "Under Secretary of Defense for Acquisition".
1992—Subsec. (e)(3). Pub. L. 102–484 designated existing provisions as subpar. (A) and added subpar. (B).
Statutory Notes and Related Subsidiaries
Effective Date of 2021 Amendment
Amendment by section 1701(d)(10) of Pub. L. 117–81 to take effect immediately after the amendments made by title XVIII of Pub. L. 116–283 have taken effect, see section 1701(a)(3) of Pub. L. 117–81, set out in a note preceding section 3001 of this title and note below.
Amendment by section 1701(u)(6)(B) of Pub. L. 117–81 applicable as if included in the enactment of title XVIII of Pub. L. 116–283 as enacted, see section 1701(a)(2) of Pub. L. 117–81, set out in a note preceding section 3001 of this title and note below.
Amendment by Pub. L. 116–283 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.
Termination of Reporting Requirements
For termination, effective Dec. 31, 2021, of provisions in subsec. (g) of this section requiring submittal of annual report to Congress, see section 1061 of Pub. L. 114–328, set out as a note under section 111 of this title.
Alternative Test and Evaluation Pathway for Designated Defense Acquisition Programs
Pub. L. 119–60, div. A, title II, §218, Dec. 18, 2025, 139 Stat. 776, provided that:
"(a)
"(b)
"(1) For each covered program, the Secretary of the military department concerned, through its service test activities, shall—
"(A) develop and implement a unified test and evaluation strategy that aligns developmental testing and operational testing to a single set of test objectives that build system understanding throughout the test program to more effectively support capability delivery within rapid prototyping and iterative updates with early and continuous operational feedback;
"(B) develop and implement a test data strategy that includes—
"(i) collection of raw data from system components during test events and operational activities, including submission of industry-derived data from their development and testing evolutions;
"(ii) evaluation criteria to assess the mission effects and suitability of the system based on the data to be collected, including from live-fire test events, if applicable;
"(iii) a process for independently validating industry-derived data, if needed;
"(iv) provision of resources for automated data collection, storage, and access; and
"(v) automated analytics tools to assess performance trends, reliability, and maintenance needs;
"(C) incorporate, to the maximum extent practicable, best practices such as—
"(i) hardware-in-the-loop testing to validate system integration;
"(ii) continuous data collection from prototypes and fielded systems to refine designs and update lifecycle costs;
"(iii) testing subsystem prototypes throughout system development to assess their contribution to the mission effect of the fielded system; and
"(iv) integration of supporting or complementary data from digital twins or other model-based systems engineering tools;
"(D) define general test and evaluation objectives and data needs while allowing detailed execution plans to evolve based on test results and emerging requirements, avoiding rigid milestone-driven schedules; and
"(E) ensure all raw test data and associated analytics are owned by the Federal Government, stored in accessible repositories, and available to authorized Department entities, including the Director of Operational Test and Evaluation, throughout the program lifecycle.
"(2) Each such covered program shall be exempt from—
"(A) any requirement in law, regulation, or policy, including Department of Defense Instruction 5000.02 or other policies, to develop and submit a test and evaluation master plan, as long as a unified test and evaluation strategy and test data strategy are implemented, as required by subparagraphs (A) and (B) of paragraph (1);
"(B) any requirement in law, regulation, or policy to conduct any milestone-specific operational test event, such as the requirement in section 4171 of title 10, United States Code, to conduct initial operational test and evaluation; and
"(C) any other test and evaluation documentation or approval process that the Secretary determines is inconsistent with the agile and iterative nature of this pathway.
"(c)
"(1) provide independent evaluation of test data across all phases of the program lifecycle, including—
"(A) assessing the sufficiency of the program's test and evaluation strategy and data strategy to demonstrate military effectiveness;
"(B) evaluating whether the program collects and analyzes sufficient raw data, learns from test results at a pace relevant to operational needs, and converges on military effectiveness based on data trends;
"(C) identifying deficiencies in test and evaluation strategies that risk system performance, suitability, or survivability; and
"(D) providing continuous oversight through ongoing analysis of test data;
"(2) have unrestricted access to all raw test data, data repositories, and analytics maintained by the military departments for the covered program;
"(3) not require of the covered program—
"(A) any specific test plan, execution method, or documentation format, or any pre-approval of test and evaluation activities, as a condition of testing, data collection, or evaluation; or
"(B) any Director of Operational Test and Evaluation-approved test and evaluation master plan or other pre-execution documentation under existing policies; and
"(4) include in the annual report required under section 139(h) of title 10, United States Code, a summary of the adequacy of data strategies, rates of learning, and risks that aligns with the evaluation processes established in this section.
"(d)
"(e)
"(f)
"(1) A defense acquisition program that the Secretary of Defense designates, on or after the date on which guidance is issued under subsection (d), for use of the alternative test and evaluation pathway under this section.
"(2) A defense acquisition program relating to software and covered hardware initiated on or after the date of the enactment of this Act."
Application of Software Innovation To Modernize Test and Evaluation Infrastructure
Pub. L. 119–60, div. A, title II, §220, Dec. 18, 2025, 139 Stat. 778, provided that:
"(a)
"(1)
"(2)
"(A) incorporate commercially-derived data management, analysis, and operations software tools to enable rapid test and evaluation;
"(B) enable real-time and iterative data collection, management, analysis, and feedback loops across the life cycle of tested systems;
"(C) provide secure environments for testing systems with operational security sensitivities; and
"(D) use a modular open system approach (as defined in section 4401 of title 10, United States Code) to ensure the environment can be accessed by multiple vendors and is interoperable with multiple data sources, data formats, and digital tools.
"(3)
"(4)
"(A) the Director of the Defense Innovation Unit;
"(B) the Director of Operational Test and Evaluation; and
"(C) each chief of a covered Armed Force.
"(b)
"(1)
"(A) to accelerate continuous integration and continuous testing of warfighting capabilities by applying industry best practices and tooling for scalability, advanced analysis, and data sharing; and
"(B) to enable continuous and iterative testing throughout capability design, development, engineering, and fielding.
"(2)
"(A) not later than 120 days after the date of the enactment of this Act [Dec. 18, 2025], submit to the congressional defense committees [Committees on Armed Services and Appropriations of the Senate and the House of Representatives] an interim report that includes an implementation plan for the pilot program under paragraph (1); and
"(B) following submittal of the report under subparagraph (A), but not later than 270 days after the date of the enactment of this Act, submit to the committees a report on the progress of the pilot program, which shall include a description of—
"(i) the metrics used to measure the performance of commercial software under the program;
"(ii) the initial findings of the program; and
"(iii) based on such findings, any identified roadblocks or limitations to using commercial software and digital tools for accelerated testing.
"(3)
"(c)
Digital Engineering Capability To Automate Testing and Evaluation
Pub. L. 116–92, div. A, title II, §231, Dec. 20, 2019, 133 Stat. 1274, provided that:
"(a)
"(1)
"(A) for the development and deployment of digital engineering models for use in the defense acquisition process; and
"(B) to provide testing infrastructure and software to support automated approaches for testing, evaluation, and deployment throughout the defense acquisition process.
"(2)
"(A) The capability will be accessible to, and useable by, individuals throughout the Department of Defense who have responsibilities relating to capability design, development, testing, evaluation, and operation.
"(B) The capability will provide for the development, validation, use, curation, and maintenance of technically accurate digital systems, models of systems, subsystems, and their components, at the appropriate level of fidelity to ensure that test activities adequately simulate the environment in which a system will be deployed.
"(C) The capability will include software to automate testing throughout the program life cycle, including to satisfy developmental test requirements and operational test requirements. Such software may be developed in accordance with the authorities provided under section 800 [of Pub. L. 116–92, formerly set out as a note under section 4571 of this title], and shall support—
"(i) security testing that includes vulnerability scanning and penetration testing performed by individuals, including threat-based red team exploitations and assessments with zero-trust assumptions; and
"(ii) high-confidence distribution of software to the field on a time-bound, repeatable, frequent, and iterative basis.
"(b)
"(1)
"(A) enable continuous software development and delivery;
"(B) satisfy developmental test requirements for the software-intensive programs of the Department of Defense; and
"(C) satisfy operational test and evaluation requirements for such programs.
"(2)
"(A) at least one program participating in the pilot program authorized under section 873 of the National Defense Authorization Act for Fiscal Year 2018 (Public Law 115–91; 10 U.S.C. 2223a note [now former 10 U.S.C. 4571 note]);
"(B) at least one program participating in the pilot program authorized under section 874 of such Act (Public Law 115–91; 10 U.S.C. 2302 note);
"(C) at least one major defense acquisition program (as defined in section 2430 of title 10, United States Code [now 10 U.S.C. 4201]);
"(D) at least one command and control program;
"(E) at least one defense business system (as defined in section 2222(i) of title 10, United States Code); and
"(F) at least one program from each military service.
"(3)
"(A) conduct a comparative analysis that assesses the risks and benefits of the digital engineering supported automated testing approaches of the programs participating in the demonstration activities relative to traditional testing approaches that are not supported by digital engineering;
"(B) ensure that the intellectual property strategy for each of the programs participating in the demonstration activities is best aligned to meet the goals of the program; and
"(C) develop a workforce and infrastructure plan to support any new policies and guidance implemented in connection with the demonstration activities, including any policies and guidance implemented after the completion of such activities.
"(c)
"(1) promote the use of digital engineering capabilities for development and for automated testing; and
"(2) address roles, responsibilities, and procedures relating to such capabilities.
"(d)
"(1)
"(2)
"(A) The Under Secretary of Defense for Research and Engineering.
"(B) The Under Secretary of Defense for Acquisition and Sustainment.
"(C) The Chief Information Officer.
"(D) The Director of Operational Test and Evaluation.
"(E) The Director of Cost Assessment and Program Evaluation.
"(F) The Service Acquisition Executives.
"(G) The Service testing commands.
"(H) The Director of the Defense Digital Service.
"(e)
"(1)
"(2)
"(f)
"(1)
"(2)
"(A) a report summarizing the assessment; and
"(B) a briefing on the findings of the assessment."
Enhancements to Transparency in Test and Evaluation Processes and Data
Pub. L. 115–91, div. A, title VIII, §839, Dec. 12, 2017, 131 Stat. 1475, provided that:
"(a)
"(1)
"(2)
"(b)
"(1)
"(2)
"(A) obtain the concurrence of the Director for Cost Assessment and Program Evaluation; and
"(B) coordinate with the Secretaries of the military departments.
"(3)
"(A)
"(B)
"(c)
