Legislative Oversight

Official bill text (stored)

Plain-text extraction from Congress.gov text formats. Canonical source remains the official URL above. Full text is prioritized for bills with roll-call votes.

119 HR 3838 IH: Streamlining Procurement for Effective Execution and Delivery Act of 2025 
 U.S. House of Representatives 
 2025-06-09 
 text/xml 
 EN 
 Pursuant to Title 17 Section 105 of the United States Code, this file is not subject to copyright protection and is in the public domain. 
 
 
 
 I 119th CONGRESS 1st Session H. R. 3838 IN THE HOUSE OF REPRESENTATIVES June 9, 2025 Mr. Rogers of Alabama (for himself and Mr. Smith of Washington ) introduced the following bill; which was referred to the Committee on Armed Services A BILL To authorize appropriations for fiscal year 2026 for military activities of the Department of Defense, for military construction, and for defense activities of the Department of Energy, to prescribe military personnel strengths for such fiscal year, and for other purposes. 1. Short title; table of contents (a) Short title This Act may be cited as the Streamlining Procurement for Effective Execution and Delivery Act of 2025 or the SPEED Act . (b) Table of contents The table of contents for this Act is as follows: Sec. 1. Short title; table of contents. Title I—Aligning Acquisition to Warfighter Priorities and Operational Outcomes Sec. 101. Alignment of the defense acquisition system with the needs of members of the Armed Forces. Sec. 102. Program executive officer responsibilities. Sec. 103. Major capability activity areas and pathfinder programs. Sec. 104. Product support manager responsibilities and requirements. Sec. 105. Amendments to life-cycle management and product support. Sec. 106. Navy Senior Technical Authority. Title II—Accelerating the Requirements Process Sec. 201. Joint Requirements Council. Sec. 202. Establishment of the Requirements, Acquisition, and Programming Integration Directorate. Sec. 203. Establishment of the Mission Engineering and Integration Activity. Title III—Striking the Balance Between Regulation and Efficiency Sec. 301. Matters related to Department of Defense use of cost accounting standards. Sec. 302. Review of commercial buying practices. Sec. 303. Adjustments to certain acquisition thresholds. Sec. 304. Alternative capability-based pricing. Sec. 305. Clarification of conditions for payments for commercial products and commercial services. Title IV—Strengthening the Defense Industrial Base and Leveraging Commercial Innovation Sec. 401. Defense Industrial Resilience Consortium. Sec. 402. Amendment to other transaction authority. Sec. 403. Data-as-a-service solutions for weapon system contracts. Sec. 404. Requirements for modular open system approach and modifications to rights in technical data. Sec. 405. Qualification, acceptance, and supply chain management of products manufactured using advanced manufacturing. Sec. 406. Amendments to the procurement technical assistance program. Sec. 407. Report on surge capacity in the defense industrial base. Sec. 408. Bridging Operational Objectives and Support for Transition program. Title V—Developing a Mission-Oriented Defense Acquisition Workforce Sec. 501. Report on strengthening the Defense Acquisition University. Sec. 502. Comptroller General review of the management, training, and development of the acquisition workforce. Sec. 503. Comptroller General review of matters relating to individuals assigned to a critical acquisition position. I Aligning Acquisition to Warfighter Priorities and Operational Outcomes 101. Alignment of the defense acquisition system with the needs of members of the Armed Forces (a) Implementation Not later than 30 days after the date of the enactment of this Act, the Secretary of Defense shall revise Department of Defense Directive 5000.01 and any other relevant instructions, policies, or guidance to carry out the requirements of this section and the amendments made by this section. (b) Objectives of defense acquisition system (1) In general Section 3102 of title 10, United States Code, is amended to read as follows: 3102. Objectives of the defense acquisition system (a) In general The Secretary of Defense shall ensure that the defense acquisition system exists to expeditiously provide the Armed Forces with the capabilities necessary to operate effectively, to address evolving threats, and to maintain the military advantage of the United States in the most cost-effective manner practicable. (b) Guidance The Secretary of Defense shall issue guidance to carry out subsection (a) that requires the following: (1) All activities of the defense acquisition system contribute to the expeditious delivery of capabilities to enhance the operational readiness of the Armed Forces and enable the missions of the Department of Defense. (2) The defense acquisition system maximizes the effective use of resources by delivering capabilities that offer the best value for the investment made in each capability. (3) The defense acquisition system encourages and supports the integration of innovative solutions to enhance military effectiveness and responsiveness to emerging threats. (4) The defense acquisition system encourages an iterative approach to designing and testing technical solutions to enable early identification of solutions that do not deliver desired results. (5) The defense acquisition system supports a leadership and organizational structure that encourages risk-taking, collaboration, and learning through failure. (6) The training and development of members of the acquisition workforce ensures that such members have the skills to effectively manage acquisition activities in accordance with this section. . (2) Conforming amendments (A) Under Secretary of Defense for Acquisition and Sustainment Section 133b(b) of title 10, United States Code, is amended— (i) in paragraph (1), by striking delivering and sustaining timely, cost-effective capabilities for the Armed Forces (and the Department) and inserting expeditiously providing the Armed Forces with the capabilities necessary to operate effectively, to address evolving threats, and to maintain the military advantage of the United States in the most cost-effective manner practicable ; and (ii) in paragraph (9)(A), by striking defense acquisition programs and inserting the defense acquisition system, in accordance with the objectives established pursuant to section 3102 . (B) Director of Operational Test and Evaluation Section 139(b) of title 10, United States Code, is amended— (i) by redesignating paragraphs (1) through (6) as paragraphs (2) through (7), respectively; and (ii) by inserting before paragraph (2), as so redesignated, the following new paragraph: (1) ensure that all operational test and evaluation activities are aligned with, and are conducted in a manner that supports, the objectives of the defense acquisition system established pursuant to section 3102 of this title; . (C) Director of Cost Assessment and Program Evaluation Section 139a(d) of title 10, United States Code, is amended by inserting shall carry out the requirements of this section in accordance with the objectives established pursuant to section 3102 of this title and before shall serve . (c) Civilian management of the defense acquisition system Section 3103 of title 10, United States Code, is amended— (1) in subsection (a), by striking to ensure the successful and efficient operation of the defense acquisition system and inserting in accordance with the objectives of the defense acquisition system established pursuant to section 3102 of this title ; and (2) in subsection (b), by striking to ensure the successful and efficient operation of such elements of the defense acquisition system. and inserting the following: in accordance with the objectives of the defense acquisition system established pursuant to section 3102 of this title. In carrying out this subsection, each service acquisition executive shall perform the following: (1) Implement strategies to effectively and efficiently respond to changes in capability requirements. (2) Use data-driven decisionmaking to manage trade-offs among life-cycle costs, delivery schedules, performance objectives, technical feasibility, and procurement quantity objectives to ensure acquisition and sustainment programs deliver the best value for the investment made in the program. (3) Use iterative development cycles and discontinue or terminate the development of capabilities— (A) that no longer align with approved capability requirements or priorities; or (B) are experiencing significant cost growth, performance deficiencies, or delays in schedule. (4) Ensure the period of assignment of an individual serving in a critical acquisition position (as defined in section 1731 of this title) is of sufficient duration to ensure the development and use of acquired expertise, institutional capacity, accountability in decisionmaking, and stability in the oversight and management of acquisition activities. (5) Ensure that contracting officers are appropriately trained and assigned to support effective contract management. . (d) Acquisition-Related functions of chiefs of the Armed Forces (1) Performance of Certain Acquisition-related Functions Section 3104(a) of title 10, United States Code, is amended— (A) by inserting , in accordance with the objectives established pursuant to section 3102 of this title, after Secretary of the military department concerned ; and (B) by amending paragraphs (1) through (7) to read as follows: (1) The development of capability requirement statements for equipping the armed force concerned that— (A) describe the operational problem to provide necessary context for the capability requirement; and (B) describe the solution sought in a non-prescriptive manner to allow agile and innovative capability development to address the operational problem; (2) The implementation of strategies to effectively and efficiently inform recommendations regarding changes in capability requirements described in paragraph (1). (3) The recommendation of trade-offs among life-cycle costs, delivery schedules, performance objectives, technical feasibility, and procurement quantity objectives to ensure acquisition programs deliver the best value for the investment made. (4) In consultation with the Joint Requirements Council, the establishment and prioritization of requirements to expeditiously provide the Armed Forces with the capabilities needed to operate effectively, to address evolving threats, and to maintain the military advantage of the United States. (5) The use of data-driven decision making to prioritize resource allocation to meet operational readiness requirements (as defined in section 4322 of this title) and the materiel readiness objectives established by the Secretary of the military department concerned under section 118(c) of this title. (6) Support for an environment that enables the adoption and integration of innovative solutions and technologies to enhance military effectiveness and responsiveness. (7) Any recommendation for the termination of the development of capabilities— (A) that no longer align with approved capability requirements or priorities; (B) for which costs have significantly increased; or (C) for which schedule delays have been significant. (8) Support for the development of career paths in acquisition for military personnel (as required by section 1722a of this title) to ensure such personnel have the necessary skills, knowledge, and experience to fulfill the objectives established pursuant to section 3102 of this title. . (2) Adherence to Requirements in Major Defense Acquisition
 Programs Section 3104(b) of title 10, United States Code, is amended— (A) in paragraph (1), by striking program capability document supporting a Milestone B or subsequent decision and inserting requirements documents ; and (B) in paragraph (2)— (i) in subparagraph (A), by striking prior to entry into the Materiel Solution Analysis Phase under Department of Defense Instruction 5000.02 ; and (ii) in subparagraph (B), by striking cost, schedule, technical feasibility, and performance trade-offs and inserting life-cycle cost, delivery schedule, performance objective, technical feasibility, and procurement quantity trade-offs . (3) Definitions Section 3104(d) of title 10, United States Code, is amended to read as follows: (d) Requirements document defined In this section, the term requirements document means a document that establishes the need for a materiel approach to resolve a capability requirement or a joint capability requirement (as such terms are defined in section 181 of this title). . (e) Technical amendments (1) Section 3101 of title 10, United States Code, is amended to read as follows: 3101. Definitions In this chapter: (1) The term best value means, with respect to an acquisition, the optimal combination of cost, quality, technical capability or solution quality, and delivery schedule. (2) The term capability requirement has the meaning provided in section 181 of this title. (3) The term cost-effective means, with respect to an acquisition, the capacity to deliver better results for the same or lower cost compared to alternatives. . (2) Section 3001(c) of title 10, United States Code, is amended by striking this section and inserting this part . 102. Program executive officer responsibilities (a) In general Subchapter III of chapter 87 of title 10, United States Code, is amended by inserting after section 1731 the following new section: 1732. Program executive officer (a) In general A program executive officer is the senior official responsible for the oversight of the plans, budgets, and execution of the programs assigned to the portfolio of such senior official, including life-cycle management. (b) Objectives In carrying out the activities described in subsection (a), the program executive officer shall seek to achieve the following objectives: (1) Expeditiously provide the Armed Forces with the capabilities needed to operate effectively, address evolving threats, and maintain the military advantage of the United States in the most cost-effective manner practicable. (2) Maximize the effective use of resources by delivering capabilities that offer the best value for the investment made in each capability. (3) Enable the integration of innovative solutions and technologies to enhance military effectiveness and responsiveness to emerging threats. (c) Specific responsibilities (1) In general For the programs assigned to the portfolio of a program executive officer, such program executive officer shall be responsible for the following: (A) Provide expeditious delivery of the capabilities necessary to effectively respond to national security challenges by overseeing the procurement, development, and sustainment of defense acquisition programs assigned to the program executive officer. (B) Ensure the cost-effective allocation of resources by delivering operational capabilities. (C) Adjust requirements, other than requirements that are established as key performance parameters, to maximize the agility and speed in program execution in accordance with the objectives described in subsection (b). (D) Use iterative development cycles and discontinue or terminate the development of capabilities— (i) that no longer align with approved capability requirements (as defined in section 181 of this title) or priorities; or (ii) that are experiencing significant cost growth, performance deficiencies, or delays in schedule. (E) Evaluate and implement trade-offs among life-cycle costs, delivery schedules, performance objectives, technical feasibility, and procurement quantity objectives to ensure acquisition and sustainment programs deliver the best value in meeting capability requirements (as defined in section 181 of this title). (F) Use data-driven decisionmaking to prioritize resource allocation to meet operational readiness requirements and materiel readiness objectives established by the Secretary concerned under section 118(c) of this title. (G) Collaborate with the Mission Engineering and Integration Activity established under section 203 of the SPEED Act to conduct cross-service technical and operational activities to integrate emerging technologies, prototypes, and operational concepts, as appropriate. (H) Provide support to the Requirements, Acquisition, and Programming Integration Directorate with respect to the performance of the responsibilities of the Directorate under section 186 of this title and serve as a member of the Directorate in accordance with such section. (2) Milestone decision authority duties A program executive officer shall be the milestone decision authority for a program when directed by the service acquisition executive of the military department that is managing the program or if designated by the Secretary of Defense. (d) Functional Support The Secretary concerned with respect to a program executive officer shall ensure that there is assigned to such program executive officer the personnel and other resources required for such program executive officer to successfully perform the assigned duties and responsibilities of such program executive officer, including— (1) contracting and contract management; (2) estimating costs; (3) financial management; (4) life-cycle management and product support; (5) program management; (6) engineering and technical management; and (7) developmental testing and evaluation. . (b) Amendment to definitions Section 1737(a)(4) of title 10, United Stated Code, is amended to read as follows: (4) The term program executive officer means an individual described in section 1732(a). . 103. Major capability activity areas and pathfinder programs (a) Transition plan required (1) Submission of plan Not later than one year after the date of the enactment of this Act, the Secretary of Defense, in coordination with each Secretary of a military department, shall submit to the congressional defense committees a comprehensive plan for organizing the programs assigned to the portfolio of a program executive officer of the Department of Defense in a manner primarily organized around major capability activity areas ( MCAAs ). (2) Elements of the plan The plan required under paragraph (1) shall be developed to more effectively facilitate the development, fielding, operation, sustainment, and modernization of capabilities of the Department of Defense in accordance with the objectives established pursuant to section 3102 of title 10, United States Code (as added by section 101 of this Act). Such plan shall include the following: (A) A description of each proposed MCAA, including how the specific capability of the Department of Defense that is the subject of each MCAA aligns with and supports joint military capabilities. (B) A proposed schedule, including benchmarks, for phased implementation of the plan to organize the programs of each military department and Defense Agency in a manner primarily organized around MCAAs. (C) Recommendations for statutory or regulatory changes needed to facilitate the reorganization of program executive offices to be primarily organized around MCAAs. (D) A strategy to preserve accountability for the delivery of a capability of the Department of Defense that is the subject of the proposed MCAA and to enable effective oversight of the proposed MCAA by the congressional defense committees. (E) A description of the process for designating a Pathfinder under subsection (b). (3) Organization by MCAAs (A) In general In organizing programs in a manner primarily organized around MCAAs under this subsection, the Secretary shall— (i) organize each proposed MCAA in a capability-oriented structure that reflects the unique and specific aspects of the subject capability of the MCAA; (ii) assign relevant development, procurement, operations, and sustainment activities of the Department to the proposed MCAA as appropriate; and (iii) ensure each proposed MCAA is organized in a manner that— (I) will improve the ability to measure and manage the overall performance in the delivery of the subject capability of the proposed MCAA; and (II) connects amounts authorized for activities assigned to the proposed MCAA to the delivery of subject capability. (B) Flexibility The Secretary of Defense shall ensure each military department and Defense Agency has flexibility, according to their specific mission requirements, in the organization of proposed MCAAs. (b) Designation of pathfinder MCAAs (1) Designation Not later than 90 days after the date of the enactment of this Act, the Secretary of Defense shall— (A) designate at least two program executive offices of the Department of Defense to be known as Pathfinders ; (B) identify the program executive officer with the responsibility of administering each such Pathfinder; (C) ensure each such program executive officer organizes the programs assigned to such offices into a MCAA in accordance with the requirements of subsection (a)(3); and (D) submit to the congressional defense committees a notification of each designation made under subparagraph (A), including the total amount authorized to carry out each Pathfinder for fiscal year 2026 and a description of the MCAA associated with each Pathfinder. (2) Modified transfer authority for Pathfinders (A) Authority The Secretary of Defense, acting through a Secretary of a military department or the head of a Defense Agency, may transfer amounts authorized for programs, projects, or activities that are included in a Pathfinder under the jurisdiction of such Secretary or head among such programs, projects, or activities. (B) Limitations A transfer made under this paragraph— (i) shall directly support delivery of the capability of the Department of Defense that is the subject of the Pathfinder; (ii) may not be used to initiate a new start program (as described in section 3601 of title 10, United States Code); (iii) may not be used to terminate a program or activity of the Department that was in operation on or before the date of the designation of the Pathfinder; and (iv) may not exceed 40 percent of the total amount authorized to carry out a Pathfinder specified under paragraph (1)(D). (3) Additional pathfinders The Secretary of Defense may designate additional MCAAs as Pathfinders under the authority of this subsection if the Secretary notifies the congressional defense committees not later than 15 days prior to each such designation. (c) Report to congress (1) In general Not later than 540 days after the date of the enactment of this Act, and annually thereafter until December 31, 2029, the Secretary of Defense shall submit to the congressional defense committees a report assessing the effectiveness of the use of a capability-oriented structure in subsection (a)(3) and Pathfinders in subsection (b) to— (A) improve the ability to measure and manage the overall performance in the delivery of the subject capability of the proposed MCAA or Pathfinder; (B) inform and improve program management and planning for future activities assigned to the proposed MCAA or Pathfinder for the delivery of subject capability; and (C) achieve the objectives of the defense acquisition system established pursuant to section 3102 of title 10, United States Code (as added by section 101 of this Act). (2) Contents The report required under paragraph (1) shall include the following: (A) The extent to which the use of MCAAs and use of the transfer authority under subsection (b)(2) for Pathfinders affect the speed of addressing emerging threats and adopting new technologies. (B) An analysis of any costs or benefits of using MCAAs. (C) Recommendations, including statutory or regulatory modifications, for— (i) expanding the use of Pathfinders; and (ii) continuing the transition to using MCAAs. (d) Definitions In this section: (1) The term major capability activity area or MCAA means a compilation of activities that relate to the delivery of a capability of the Department of Defense, as determined by the Secretary of Defense. (2) The term joint military capabilities has the meaning given in section 181 of title 10, United States Code, as amended by section 201 of this Act. (3) The term program executive officer has the meaning given in section 1732 of title 10, United States Code, as added by section 102 of this Act. 104. Product support manager responsibilities and requirements (a) In general Subchapter III of chapter 87 of title 10, United States Code, is amended by inserting after section 1732 (as added by section 102 of this Act) the following new section: 1733. Product support manager (a) In general A product support manager is the individual responsible for managing support functions required to field and maintain the readiness and operational capability of a covered system in support of the life-cycle management responsibilities of the program manager for such covered system. (b) Objectives In carrying out the activities described in subsection (a), the product support manager shall seek to achieve the objectives of the defense acquisition system established pursuant to section 3102 of this title. (c) Specific responsibilities A product support manager shall be responsible for the following: (1) Provide product support and subject matter expertise with respect to a covered system to the program manager for the covered system to assist with the development, resourcing, implementation, and execution of the product support strategy developed by the product support manager under section 4322 of this title for the covered system. (2) Collaborate with the chief engineer and systems engineers for the covered system— (A) to develop the life-cycle sustainment plan and any product support plans for the covered system; and (B) to analyze the operating and support costs of the covered system to ensure the cost-effective operation, management, and availability of the covered system. (3) Conduct early risk identification, mitigation, and product support analyses that inform best value solutions in life-cycle planning and management. (4) Provide input on systems engineering requirements, design, budgeting, maintenance planning, and acquisition strategies for covered systems. (5) Support the program manager in evaluating trade-offs among life-cycle costs, delivery schedules, performance objectives, technical feasibility, and procurement quantity objectives to ensure each covered system delivers the greatest value for the investment made in the covered system. (6) Use data-driven decision making, predictive analysis, and appropriate modeling tools related to reliability and maintainability of the covered system to prioritize resource allocation to meet operational readiness requirements and materiel readiness objectives (established under section 118(c) of this title). (7) Support each Secretary of a military department in performance of a core logistics analysis pursuant to section 2464 of this title. (d) Covered system defined In this section, the term covered system has the meaning given in section 4322 of this title. . (b) Education, training, and experience requirements for product support managers Section 1735 title 10, United States Code, is amended— (1) by redesignating subsections (c), (d), and (e) as subsections (d), (e), and (f), respectively; and (2) by inserting after subsection (b) the following new subsection: (c) Product support manager Before being assigned to a position as product support manager, a person— (1) shall have completed all life-cycle logistics certification and training requirements prescribed by the Secretary of Defense; (2) shall have executed a written agreement as required in section 1734(b)(2) of this title; and (3) in the case of— (A) a product support manager of a major defense acquisition program, shall have at least eight years of experience in life-cycle logistics, at least two years of which were performed in a systems program office or similar organization; and (B) a product support manager of a significant nonmajor defense acquisition program, shall have at least six years of experience in life-cycle logistics. . (c) Conforming amendments Section 1731(a)(1)(B) title 10, United States Code, is amended by adding at the end the following new clause: (iv) Product support manager. . 105. Amendments to life-cycle management and product support (a) Reorganization of life-Cycle and sustainment chapter (1) In general Chapter 323 of title 10, United States Code, is amended— (A) by repealing sections 4321, 4323, and 4324; (B) by redesignating section 4328 as section 4321 and transferring such section so as to appear after the table of sections at the beginning of such chapter; (C) by redesignating section 4325 as section 4323 and transferring such section so as to appear after section 4321; (D) in section 4323, as so redesignated, by striking section 4324 of this title and inserting section 4322 of this title ; and (E) by amending the table of sections at the beginning of such chapter to read as follows: 4321. Weapon system design:
 sustainment factors. 4322. Life-cycle management and
 product support. 4323. Major weapon systems:
 assessment, management, and control of operating and support
 costs. . (2) Conforming amendments (A) Section 3041(a) of title 10, United States Code, is amended by striking sections 4292(e) and 4321 and inserting section 4292(e) . (B) Section 3221(b)(2) of title 10, United States Code, is amended by striking 4321, 4323, and 4328 of this title and inserting and 4321 of this title, . (C) Section 4211(c)(2)(D) of title 10, United States Code, is amended by striking section 4324 of this title and inserting section 4322 of this title . (D) Section 4252(b)(14) of title 10, United States Code, is amended by striking section 4324(b) of this title and inserting section 4322 of this title . (b) Life-Cycle management and product support Chapter 323 of title 10, United States Code, as amended by subsection (a), is further amended by inserting after section 4321 the following new section: 4322. Life-cycle management and product support (a) In general The Secretary of Defense shall ensure that each covered system is supported by a life-cycle sustainment plan— (1) that is approved by the senior acquisition executive responsible for such covered system; and (2) that meets applicable operational readiness requirements and materiel readiness objectives (established under section 118(c) of this title) in the most cost-effective manner practicable. (b) Product support manager The Secretary of Defense shall designate a product support manager (as defined in section 1733 of this title) to serve under the supervision of a program manager for each covered system. (c) Life-Cycle sustainment plan (1) A product support manager shall develop, update, and implement a life-cycle sustainment plan for each covered system for which the product support manager is responsible. Such plan shall include the following: (A) A comprehensive product support strategy to best achieve operational readiness requirements and materiel readiness objectives throughout the planned life cycle of such system. (B) A baseline life-cycle cost estimate for the covered system based on the planned product support strategy described in subparagraph (A). (C) Recommended engineering and design considerations that support cost-effective sustainment of the covered system and best value solutions in life-cycle planning and management. (D) An intellectual property management plan for product support developed in accordance with section 3774 of this title. (E) A strategy to maximize use of public and private sector capabilities to establish Government-private partnerships— (i) with appropriate incentives for each partner to contribute to the achievement of operational readiness requirements and materiel readiness objectives in the most cost-effective manner practicable; and (ii) that considers the roles of each partner as the covered system transitions from acquisition, development, production, fielding, sustainment, and disposal. (F) A plan to transition the covered system from production to initial fielding that addresses specific products or services required for successful initial fielding of the covered system, including— (i) a description of the necessary tooling or other unique support equipment, requirements for initial spare parts and components, technical handbooks and maintenance manuals, maintenance training, and facilities; (ii) an identification of the funding required to provide such products and services for any initial fielding location of the covered system; (iii) an identification of any procurement line, program element, or subactivity group in the budget of the Secretary concerned associated with such products or services; (iv) the timeline for delivery of such products and services; and (v) an assessment of any reduction in operational readiness requirements and materiel readiness objectives if such products and services are not provided in accordance with clause (iv). (2) In developing each life-cycle sustainment plan required by this section, the product support manager shall consider the following: (A) Affordability constraints and key cost factors that could affect operating and support costs during the life cycle of the covered system. (B) Sustainment risks or challenges to sustaining the covered system in operational environments, included contested logistics environments (as defined in section 2926 of this title). (C) Compliance with— (i) requirements to maintain a core logistics capability under section 2464 of this title; and (ii) limitations on the performance of depot-level maintenance of materiel under section 2466 of this title. (D) A defense industrial base strategy to maintain a robust, resilient, and innovative defense industrial base to support requirements throughout the life cycle of the covered system. (d) Continuous assessment and active management In carrying out the duties of this section and section 1733 of this title, the product support manager shall— (1) continuously assess and actively manage performance of each covered system for which the product support manager is responsible against the life-cycle sustainment plan for such covered system; and (2) as appropriate, integrate commercial best practices, use commercial standards, and use advanced technologies to enhance the product support of each covered system. (e) Recommendations (1) The product support manager shall recommend changes to the product support strategy required under subsection (c)(1)(A) of a covered system to the program manager responsible for such covered system to meet the requirements of subsection (a). (2) The program manager shall provide to the senior acquisition executive responsible for a covered system any recommendations for such covered system made under paragraph (1) that the program manager did not implement along with the rationale for not implementing such recommendations. (f) Definitions In this section: (1) The term covered system means— (A) a major defense acquisition program as defined in section 4201 of this title; (B) a major subprogram as described in section 4203 of this title; or (C) an acquisition program or project that is carried out using the rapid fielding or rapid prototyping acquisition pathway under section 3602 of this title that is estimated by the Secretary of Defense to require an eventual total expenditure described in section 4201(a)(2) of this title. (2) The term operational readiness means the capability of a unit of the Armed Forces, vessel, weapon system, or equipment to perform the missions or functions for which it is organized or designed. (3) The term product support means the set of support functions, as determined by the product support manager, required to field and maintain the readiness and operational capability of a covered system, or a subsystem or component of a covered system. . (c) Conforming amendments to materiel readiness metrics and objectives for major weapon systems Section 118 of title 10, United States Code, is amended— (1) in the section heading, by inserting materiel readiness before objectives ; (2) in subsection (b), by striking shall address and inserting shall establish procedures and a computation methodology to determine ; (3) in subsection (c)— (A) in paragraph (1), by striking the metrics required and all that follows through the period at the end and inserting materiel readiness objectives for each major weapon system. ; and (B) in paragraph (2), by striking the metrics required by subsection (b) and inserting such readiness objectives ; (4) in subsection (d)(2), by striking readiness goals or objectives and inserting materiel readiness objectives ; (5) in subsection (e), in the matter preceding paragraph (1), by inserting a comma after designated mission ; and (6) in subsection (f)— (A) by redesignating paragraphs (3), (4), and (5) as paragraphs (4), (5), and (6), respectively; and (B) by inserting after paragraph (2) the following new paragraph: (3) The term materiel readiness objective means the minimum required availability of each major weapon system that is necessary to fulfill the requirements of the strategic framework and guidance referred to in subsection (a). . 106. Navy Senior Technical Authority Section 8669b of title 10, United States Code, is amended— (1) in subsection (a)(2), by amending subparagraph (B) to read as follows: (B) reports directly to the program executive officer. ; and (2) in subsection (b)— (A) by inserting (1) before Each Senior ; and (B) by adding at the end the following new paragraph: (2) Each Senior Technical Authority shall also be responsible for the determination that all design requirements for a vessel class are directly related to a key performance parameter or key system attribute established in the capability development document for the vessel class. Any requirements that the Senior Technical Authority determines are unnecessary to meet a key performance parameter or key system attribute shall not be approved. . II Accelerating the Requirements Process 201. Joint Requirements Council (a) Implementation Not later than 30 days after the date of the enactment of this Act, the Chairman of the Joint Chiefs shall revise policies for the Joint Strategic Planning System (established under the Chairman of the Joint Chiefs of Staff Instruction 3100.01F), the Manual for the Operation of the Joint Capabilities Integration and Development System (issued October 30, 2021) and any other relevant instructions, policies, or guidance to carry out the requirements of this section and the amendments made by this section. (b) Amendment to name and mission of Joint Requirements Oversight Council Section 181 of title 10, United States Code, is amended— (1) in the section heading, by striking Oversight ; (2) in subsection (a), by striking Joint Requirements Oversight Council in the Department of Defense. and inserting the following: Joint Requirements Council (in this section referred to as the Council ) in the Department of Defense. The Council shall— (1) assist the Chairman of the Joint Chiefs of Staff in carrying out the functions described in section 153 of this title; and (2) provide recommendations for addressing joint operational problems to the Requirements, Acquisition, and Programming Integration Directorate established under section 186 of this title (in this section referred to as RAPID ). ; and (3) by striking Joint Requirements Oversight Council each place it appears and inserting Joint Requirements Council . (c) Duties Subsection (b) of such section 181 is amended to read as follows: (b) Duties The Council shall support the objectives established pursuant to section 3102 of this title by performing the following duties: (1) Continuously evaluating global trends, adversary capabilities, and emerging threats to inform awareness and understanding of joint operational problems. (2) In coordination with commanders of combatant commands, compiling, refining, and prioritizing joint operational problems. (3) Identifying and prioritizing gaps in joint military capabilities to address joint operational problems. (4) Identifying advances in technology and innovative concepts of operation that could improve the ability of the joint force to address evolving threats and maintain the military advantage of the United States. (5) Developing a joint capability requirement statement that— (A) describes the joint operational problem to provide necessary context for the joint capability requirement; and (B) describes the solution sought in a nonprescriptive manner to allow agile and innovative development of joint capability requirements to address the joint operational problem. (6) Making the following recommendations to RAPID: (A) With respect to a quick action requirement, actions to fulfill such quick action requirement, not later than 30 days after receipt or identification of such quick action requirement. (B) Actions to fulfill each joint capability requirement necessary to address joint operational problems, not later than 60 days after receipt or identification of such a joint operational problem. (C) Modifications to joint force design suitable for addressing joint operational problems or effectively integrating advancements in technology and new concepts of operation. (D) Ways to improve operational effectiveness, increase operational flexibility, or improve interoperability and coordination between and among joint military capabilities and the military capabilities of allies or partners. (7) Providing notification to Deputy Secretary of Defense— (A) upon receipt or identification of a quick action requirement; and (B) upon submission of any recommendation to RAPID. . (d) Composition Subsection (c) of such section 181 is amended— (1) in paragraph (1)(A)— (A) by inserting and RAPID before for making recommendations ; and (B) by striking joint performance requirements and inserting joint capability requirements ; and (2) in paragraph (3), by inserting and RAPID after Chairman of the Joint Chiefs of Staff . (e) Advisors Subsection (d) of such section 181 is amended— (1) in paragraph (2)— (A) by inserting strongly before consider ; and (B) by striking its mission under paragraphs (1) and (2) of subsection (b) and inserting the duties described in subsection (b) ; and (2) in paragraph (3)— (A) by striking seek, and strongly consider, and inserting seek and consider ; (B) by striking , in their roles as customers of the acquisition system, ; and (C) by striking under subsection (b)(2) and joint performance requirements pursuant to subsection (b)(3) . (f) Responsibility for Capability Requirements Subsection (e) of such section 181 is amended to read as follows: (e) Responsibility for Capability Requirements The Chief of Staff of an armed force is responsible for the capability requirements for that armed force. . (g) Analytic and Engineering Support Subsection (f) of such section 181 is amended— (1) in the subsection heading, by inserting and engineering after Analytic ; (2) by inserting and the Mission Engineering and Integration Activity established under section 203 of the SPEED Act after the Office of Cost Assessment and Program Evaluation ; and (3) by striking in operations research, systems analysis, and cost estimation to the Joint Requirements Oversight Council . (h) Availability of Information to Congressional Defense Committees Subsection (g) of such section 181 is amended— (1) in the subsection heading, by striking oversight ; and (2) by striking oversight information and inserting information . (i) Definitions Subsection (h) of such section 181 is amended to read as follows: (h) Definitions In this section: (1) The term capability requirement means a requirement for a capability that is critical or essential to address an operational problem. (2) The term joint capability requirement means a capability requirement, including a capability requirement related to a requirement for joint force interoperability, that is critical or essential to address a specific joint operational problem. (3) The term joint military capabilities means the collective capabilities across the joint force, including both joint and force-specific capabilities, that are available to conduct military operations. (4) The term joint operational problem means a joint challenge faced by a combatant command in achieving an assigned military objective and may include limitations in capabilities, resources, or the ability to effectively and efficiently coordinate across the joint force, with another combatant command, among joint military capabilities, or with the military capabilities of allies or partners. (5) The term operational problem means a challenge or barrier in an operational environment that needs to be overcome to achieve a specific military objective. (6) The term quick action requirement has the meaning given in Department of Defense Directive 5000.71 titled Rapid Fulfillment of Combatant Commander Urgent Operational Needs (August 24, 2012). . (j) Conforming amendments (1) Title 10, United States Code Title 10, United States Code, is amended— (A) in section 139a, by striking Joint Requirements Oversight Council each place it appears and inserting Joint Requirements Council ; (B) in section 153(a)(5)(F), by striking section 181 of this title and inserting sections 181 and 186 of this title ; (C) in section 179(c)(9)— (i) by striking Joint Requirements Oversight Council and inserting Joint Requirements Council ; and (ii) by striking section 181(h) and inserting section 181 ; (D) in section 2926(f)(5)(C), by striking describing and all that follows through details regarding and inserting describing details regarding ; (E) in section 3067(b)(1), by striking Joint Requirements Oversight Council and inserting Joint Requirements Council ; (F) in section 3136(e)(1)(A)(ii), by striking approved by the Joint Requirements Oversight Council and and inserting recommended for approval by the Requirements, Acquisition, and Programming Integration Directorate (established under section 186 of this title) ; (G) in section 4202(a)(2)(A), by striking joint military requirement and all that follows through the period at the end and inserting the following: joint capability requirement, as determined by the Requirements, Acquisition, and Programming Integration Directorate (established under section 186 of this title) ; (H) by amending section 4251(e)(1) to read as follows: (1) The term requirements document has the meaning given in section 3104(d) of this title. ; (I) in section 4252(b)(9), by striking Joint Requirements Oversight Council and inserting Joint Requirements Council ; (J) in section 4376— (i) in subsection (a), by striking , after consultation with the Joint Requirements Oversight Council regarding program requirements, ; (ii) in subsection (b)(2)(B), by striking joint military requirement (as defined in section 181(g)(1) of this title) at less cost and inserting joint capability requirement (as defined in section 181 of this title) at less cost ; and (iii) in subsection (c)(3), by striking joint military requirements and inserting joint capability requirements ; and (K) in section 5514(b)(2)(C)(ii), by striking Joint Requirements Oversight Council and inserting Joint Requirements Council . (2) Other laws (A) Section 902(d) of the National Defense Authorization Act for Fiscal Year 2024 ( 10 U.S.C. 139a note) is amended— (i) by striking , performance requirements, and joint performance requirements and inserting or performance requirements ; and (ii) by striking Joint Requirements Oversight Council to validate such requirements and inserting Joint Requirements Council . (B) Section 1684(d)(4)(A)(i) of the National Defense Authorization Act for Fiscal Year 2024 ( 10 U.S.C. 2271 note) is amended by striking either approved by, or in development for, the Joint Requirements Oversight Council and inserting in development for consideration or under consideration by the Joint Requirements Council . (C) Section 1686(b)(1) of the National Defense Authorization Act for Fiscal Year 2024 ( 10 U.S.C. 2224 note) is amended by striking through the Joint Requirements Oversight Council and inserting in consultation with the Requirements, Acquisition, and Programming Integration Directorate (established under section 186 of title 10, United States Code) . (D) Section 1510(b)(2) of the National Defense Authorization Act for Fiscal Year 2023 ( 10 U.S.C. 113 note) is amended by striking Joint Requirements Oversight Council and inserting Joint Requirements Council . (E) Section 915(a)(1) of the National Defense Authorization Act for Fiscal Year 2023 ( 10 U.S.C. 132 note) is amended by striking Joint Requirements Oversight Council and inserting Joint Requirements Council . (F) Section 938(a)(1) of the National Defense Authorization Act for Fiscal Year 2014 ( 10 U.S.C. 4571 note prec.) is amended by striking Joint Requirements Oversight Council and inserting Joint Requirements Council . (3) Repeals The following provisions of law are repealed: (A) Section 942 of the National Defense Authorization Act for Fiscal Year 2008 ( 10 U.S.C. 181 note). (B) Section 916 of the Floyd D. Spence National Defense Authorization Act for Fiscal Year 2001 ( 10 U.S.C. 181 note). (C) Section 105(b) of the Weapon Systems Acquisition Reform Act of 2009 ( 10 U.S.C. 181 note). (D) Section 201 of the Weapon Systems Acquisition Reform Act of 2009 ( 10 U.S.C. 3102 note). 202. Establishment of the Requirements, Acquisition, and Programming Integration Directorate (a) In general Chapter 7 of title 10, United States Code, is amended by inserting after section 185 the following new section: 186. Requirements, Acquisition, and Programming Integration Directorate (a) Establishment There is within the Department of Defense a Requirements, Acquisition, and Programming Integration Directorate (in this section referred to 

… [truncated for display; full text stored]

Plain-English summary

Confidence: high · Complexity: complex · Model: grok-4.5

Related issues

• Defense & National Security
• Taxes & Government Spending
• Regulation & Agency Oversight

How a vote maps to positions

Impartial mapping: which issue position a Yea vs Nay advances. When a bill has multiple floor votes, each roll can have its own mapping. Bill-level entries (no roll listed) apply as a default when a roll has no specific map. Used for legislator alignment.

Official citations

• Congress.gov

Member votes on this bill