{"check":null,"uid":"dcc3f0f2542b552c","title":"To amend title 10, United States Code, to require the Secretary of Defense to annually review the amount of financial assistance for child care and youth program services providers provided by the Secretary.","title_generated":false,"country":"США","organ":"Конгресс США","kind":"law","kind_name":"Законодательство","lang":"en","date":"2026-05-15","summary":"Закон утверждает ассигнования на 2026 финансовый год для деятельности Министерства обороны, военного строительства и оборонных программ Минэнерго США, а также устанавливает численность военнослужащих. Документ содержит правила закупки вооружений по видам войск (сухопутные войска, ВМС, ВВС), финансирования НИОКР и ограничений на отдельные программы. Вводится запрет для Федеральной резервной системы на создание или использование цифровой валюты центрального банка либо схожих цифровых активов при проведении денежно-кредитной политики.","snippet":"","topics":["Криптоактивы и блокчейн","Электронная коммерция и платежи"],"status":"ok","error":"ReadTimeout: The read operation timed out","text_len":124372,"versions":2,"url":"https://www.congress.gov/bill/119-congress/hr/3838","first_seen":"2026-09-08","last_checked":"2026-11-16 05:24","relevance":"hit","score":5,"query":"","source_key":"congress_us","verdict":{"relevance":"hit","score":5,"topics":["Криптоактивы и блокчейн","Электронная коммерция и платежи"],"need_body":8,"authorities":[],"evidence":[{"topic":"Электронная коммерция и платежи","term":"цифров валют","weak":true,"pos":639,"ctx":"рограммы. вводится запрет для федеральной резервной системы на создание или использование цифровой валюты центрального банка либо схожих цифровых активов при проведении денежно-кредитной политики","zone":"название","weight":1},{"topic":"Криптоактивы и блокчейн","term":"цифров валют центральн","weak":false,"pos":639,"ctx":"рограммы. вводится запрет для федеральной резервной системы на создание или использование цифровой валюты центрального банка либо схожих цифровых активов при проведении денежно-кредитной политики.","zone":"название","weight":3},{"topic":"Криптоактивы и блокчейн","term":"цифров актив","weak":true,"pos":686,"ctx":"вной системы на создание или использование цифровой валюты центрального банка либо схожих цифровых активов при проведении денежно-кредитной политики.","zone":"название","weight":1}],"dropped":[{"topic":"Кибербезопасность","term":"cybersecurity","weak":false,"pos":1327,"ctx":"policy for various matters related to dod cyber activities, cyber workforce and training, cybersecurity, and artificial intelligence matters; and authorizes the activities of the national nucle","why":"одиночное упоминание (нужно 8)"},{"topic":"Искусственный интеллект","term":"artificial intelligence","weak":false,"pos":1346,"ctx":"matters related to dod cyber activities, cyber workforce and training, cybersecurity, and artificial intelligence matters; and authorizes the activities of the national nuclear security administration, d","why":"одиночное упоминание (нужно 8)"},{"topic":"Искусственный интеллект","term":"artificial intelligence","weak":false,"pos":83430,"ctx":"ommercial approaches to information technology, software, the cloud, data management, and artificial intelligence to support and enable modern manufacturing capabilities; and (ii) identifying financial i","why":"одиночное упоминание (нужно 8)"},{"topic":"Интеллектуальная собственность в цифровой среде","term":"intellectual property","weak":true,"pos":34127,"ctx":"e 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 tit","why":"одиночное упоминание (нужно 8)"},{"topic":"Интеллектуальная собственность в цифровой среде","term":"copyright","weak":false,"pos":101000,"ctx":"tes code, is amended-- (a) in subsection (a)-- (i) in paragraph (2)(a), by striking `` or copyrights'' and inserting ``, copyrights, trade secrets,''; and (ii) by adding at the end the follo","why":"одиночное упоминание (нужно 8)"},{"topic":"Интеллектуальная собственность в цифровой среде","term":"copyright","weak":false,"pos":101031,"ctx":"ubsection (a)-- (i) in paragraph (2)(a), by striking `` or copyrights'' and inserting ``, copyrights, trade secrets,''; and (ii) by adding at the end the following new paragraph: ``(3) enfor","why":"одиночное упоминание (нужно 8)"},{"topic":"Телеком и инфраструктура","term":"spectrum","weak":true,"pos":82757,"ctx":"anced manufacturing and other production capabilities to enable rapid response across the spectrum of operational environments; (iv) enabling and enhancing public-private partnerships betw","why":"одиночное упоминание (нужно 8)"}]},"last_changed":"2026-10-16","meta":{"congress":"119","billType":"HR","number":"3838","policyArea":"Armed Forces and National Security","subjects":["Accounting and auditing","Advanced technology and technological innovations","Advisory bodies","Alabama","Alaska","Alliances","Animal protection and human-animal relationships","Appropriations","Arab-Israeli relations","Architecture","Arizona","Arkansas","Armed Forces Retirement Home","Art, artists, authorship","Asia","Assault and harassment offenses","Atmospheric science and weather","Australia","Aviation and airports","Belarus","Belgium","Border security and unlawful immigration","Broadcasting, cable, digital technologies","Building construction","California","Canada","Cancer","Caribbean area","Chemical and biological weapons","Child care and development","Child health","Child safety and welfare","China","Collective security","Competition and antitrust","Computer security and identity theft","Computers and information technology","Conflicts and wars","Congressional officers and employees","Congressional oversight"],"latestAction":"2025-09-16 Referred to the House Committee on Armed Services.","textVersion":"ih"},"source_url":"https://www.congress.gov/bill/119-congress/hr/3838","text":"SUMMARY\nStreamlining Procurement for Effective Execution and Delivery and National Defense Authorization Act for Fiscal Year 2026\nThis bill sets forth policies and authorities for FY2026 for Department of Defense (DOD) programs and activities, military construction, and the national security programs of the Department of Energy and the Maritime Administration. It also authorizes appropriations for the Defense Nuclear Facilities Safety Board and the Naval Petroleum Reserves, and modifies the defense acquisition system to expedite delivery of capabilities to the Armed Forces.\nAmong other elements, the bill\nauthorizes the acquisition or modification of various military items (e.g., aircraft) and sets policy for certain procurement programs;\nauthorizes research, development, test, and evaluation and sets policy for such activities;\nsets active component and reserve component end-strength levels;\nsets policy regarding various aspects of military health care and military compensation;\nsets policy regarding acquisitions and acquisition management, including contracting authorities and small businesses;\nsets policy for various matters related to DOD interactions with foreign nations, including matters concerning Israel;\nsets policy for various matters related to DOD cyber activities, cyber workforce and training, cybersecurity, and artificial intelligence matters; and\nauthorizes the activities of the National Nuclear Security Administration, defense environmental cleanup, nuclear energy, and other defense activities.\nFor additional information on the National Defense Authorization Act (NDAA) see\nCRS In Focus IF10516, Defense Primer: Navigating the NDAA , and\nCRS In Focus IF10515, Defense Primer: The NDAA Process .\n\nFULL TEXT\n[Congressional Bills 119th Congress]\n[From the U.S. Government Publishing Office]\n[H.R. 3838 Introduced in House (IH)]\n\n<DOC>\n\n119th CONGRESS\n1st Session\nH. R. 3838\n\nTo authorize appropriations for fiscal year 2026 for military\nactivities of the Department of Defense, for military construction, and\nfor defense activities of the Department of Energy, to prescribe\nmilitary personnel strengths for such fiscal year, and for other\npurposes.\n\n_______________________________________________________________________\n\nIN THE HOUSE OF REPRESENTATIVES\n\nJune 9, 2025\n\nMr. Rogers of Alabama (for himself and Mr. Smith of Washington)\nintroduced the following bill; which was referred to the Committee on\nArmed Services\n\n_______________________________________________________________________\n\nA BILL\n\nTo authorize appropriations for fiscal year 2026 for military\nactivities of the Department of Defense, for military construction, and\nfor defense activities of the Department of Energy, to prescribe\nmilitary personnel strengths for such fiscal year, and for other\npurposes.\n\nBe it enacted by the Senate and House of Representatives of the\nUnited States of America in Congress assembled,\n\nSECTION 1. SHORT TITLE; TABLE OF CONTENTS.\n\n(a) Short Title.--This Act may be cited as the ``Streamlining\nProcurement for Effective Execution and Delivery Act of 2025'' or the\n``SPEED Act''.\n(b) Table of Contents.--The table of contents for this Act is as\nfollows:\n\nSec. 1. Short title; table of contents.\nTITLE I--ALIGNING ACQUISITION TO WARFIGHTER PRIORITIES AND OPERATIONAL\nOUTCOMES\n\nSec. 101. Alignment of the defense acquisition system with the needs of\nmembers of the Armed Forces.\nSec. 102. Program executive officer responsibilities.\nSec. 103. Major capability activity areas and pathfinder programs.\nSec. 104. Product support manager responsibilities and requirements.\nSec. 105. Amendments to life-cycle management and product support.\nSec. 106. Navy Senior Technical Authority.\nTITLE II--ACCELERATING THE REQUIREMENTS PROCESS\n\nSec. 201. Joint Requirements Council.\nSec. 202. Establishment of the Requirements, Acquisition, and\nProgramming Integration Directorate.\nSec. 203. Establishment of the Mission Engineering and Integration\nActivity.\nTITLE III--STRIKING THE BALANCE BETWEEN REGULATION AND EFFICIENCY\n\nSec. 301. Matters related to Department of Defense use of cost\naccounting standards.\nSec. 302. Review of commercial buying practices.\nSec. 303. Adjustments to certain acquisition thresholds.\nSec. 304. Alternative capability-based pricing.\nSec. 305. Clarification of conditions for payments for commercial\nproducts and commercial services.\nTITLE IV--STRENGTHENING THE DEFENSE INDUSTRIAL BASE AND LEVERAGING\nCOMMERCIAL INNOVATION\n\nSec. 401. Defense Industrial Resilience Consortium.\nSec. 402. Amendment to other transaction authority.\nSec. 403. Data-as-a-service solutions for weapon system contracts.\nSec. 404. Requirements for modular open system approach and\nmodifications to rights in technical data.\nSec. 405. Qualification, acceptance, and supply chain management of\nproducts manufactured using advanced\nmanufacturing.\nSec. 406. Amendments to the procurement technical assistance program.\nSec. 407. Report on surge capacity in the defense industrial base.\nSec. 408. Bridging Operational Objectives and Support for Transition\nprogram.\nTITLE V--DEVELOPING A MISSION-ORIENTED DEFENSE ACQUISITION WORKFORCE\n\nSec. 501. Report on strengthening the Defense Acquisition University.\nSec. 502. Comptroller General review of the management, training, and\ndevelopment of the acquisition workforce.\nSec. 503. Comptroller General review of matters relating to individuals\nassigned to a critical acquisition\nposition.\n\nTITLE I--ALIGNING ACQUISITION TO WARFIGHTER PRIORITIES AND OPERATIONAL\nOUTCOMES\n\nSEC. 101. ALIGNMENT OF THE DEFENSE ACQUISITION SYSTEM WITH THE NEEDS OF\nMEMBERS OF THE ARMED FORCES.\n\n(a) Implementation.--Not later than 30 days after the date of the\nenactment of this Act, the Secretary of Defense shall revise Department\nof Defense Directive 5000.01 and any other relevant instructions,\npolicies, or guidance to carry out the requirements of this section and\nthe amendments made by this section.\n(b) Objectives of Defense Acquisition System.--\n(1) In general.--Section 3102 of title 10, United States\nCode, is amended to read as follows:\n``Sec. 3102. Objectives of the defense acquisition system\n``(a) In General.--The Secretary of Defense shall ensure that the\ndefense acquisition system exists to expeditiously provide the Armed\nForces with the capabilities necessary to operate effectively, to\naddress evolving threats, and to maintain the military advantage of the\nUnited States in the most cost-effective manner practicable.\n``(b) Guidance.--The Secretary of Defense shall issue guidance to\ncarry out subsection (a) that requires the following:\n``(1) All activities of the defense acquisition system\ncontribute to the expeditious delivery of capabilities to\nenhance the operational readiness of the Armed Forces and\nenable the missions of the Department of Defense.\n``(2) The defense acquisition system maximizes the\neffective use of resources by delivering capabilities that\noffer the best value for the investment made in each\ncapability.\n``(3) The defense acquisition system encourages and\nsupports the integration of innovative solutions to enhance\nmilitary effectiveness and responsiveness to emerging threats.\n``(4) The defense acquisition system encourages an\niterative approach to designing and testing technical solutions\nto enable early identification of solutions that do not deliver\ndesired results.\n``(5) The defense acquisition system supports a leadership\nand organizational structure that encourages risk-taking,\ncollaboration, and learning through failure.\n``(6) The training and development of members of the\nacquisition workforce ensures that such members have the skills\nto effectively manage acquisition activities in accordance with\nthis section.''.\n(2) Conforming amendments.--\n(A) Under secretary of defense for acquisition and\nsustainment.--Section 133b(b) of title 10, United\nStates Code, is amended--\n(i) in paragraph (1), by striking\n``delivering and sustaining timely, cost-\neffective capabilities for the Armed Forces\n(and the Department)'' and inserting\n``expeditiously providing the Armed Forces with\nthe capabilities necessary to operate\neffectively, to address evolving threats, and\nto maintain the military advantage of the\nUnited States in the most cost-effective manner\npracticable''; and\n(ii) in paragraph (9)(A), by striking\n``defense acquisition programs'' and inserting\n``the defense acquisition system, in accordance\nwith the objectives established pursuant to\nsection 3102''.\n(B) Director of operational test and evaluation.--\nSection 139(b) of title 10, United States Code, is\namended--\n(i) by redesignating paragraphs (1) through\n(6) as paragraphs (2) through (7),\nrespectively; and\n(ii) by inserting before paragraph (2), as\nso redesignated, the following new paragraph:\n``(1) ensure that all operational test and evaluation\nactivities are aligned with, and are conducted in a manner that\nsupports, the objectives of the defense acquisition system\nestablished pursuant to section 3102 of this title;''.\n(C) Director of cost assessment and program\nevaluation.--Section 139a(d) of title 10, United States\nCode, is amended by inserting ``shall carry out the\nrequirements of this section in accordance with the\nobjectives established pursuant to section 3102 of this\ntitle and'' before ``shall serve''.\n(c) Civilian Management of the Defense Acquisition System.--Section\n3103 of title 10, United States Code, is amended--\n(1) in subsection (a), by striking ``to ensure the\nsuccessful and efficient operation of the defense acquisition\nsystem'' and inserting ``in accordance with the objectives of\nthe defense acquisition system established pursuant to section\n3102 of this title''; and\n(2) in subsection (b), by striking ``to ensure the\nsuccessful and efficient operation of such elements of the\ndefense acquisition system.'' and inserting the following: ``in\naccordance with the objectives of the defense acquisition\nsystem established pursuant to section 3102 of this title. In\ncarrying out this subsection, each service acquisition\nexecutive shall perform the following:\n``(1) Implement strategies to effectively and efficiently\nrespond to changes in capability requirements.\n``(2) Use data-driven decisionmaking to manage trade-offs\namong life-cycle costs, delivery schedules, performance\nobjectives, technical feasibility, and procurement quantity\nobjectives to ensure acquisition and sustainment programs\ndeliver the best value for the investment made in the program.\n``(3) Use iterative development cycles and discontinue or\nterminate the development of capabilities--\n``(A) that no longer align with approved capability\nrequirements or priorities; or\n``(B) are experiencing significant cost growth,\nperformance deficiencies, or delays in schedule.\n``(4) Ensure the period of assignment of an individual\nserving in a critical acquisition position (as defined in\nsection 1731 of this title) is of sufficient duration to ensure\nthe development and use of acquired expertise, institutional\ncapacity, accountability in decisionmaking, and stability in\nthe oversight and management of acquisition activities.\n``(5) Ensure that contracting officers are appropriately\ntrained and assigned to support effective contract\nmanagement.''.\n(d) Acquisition-Related Functions of Chiefs of the Armed Forces.--\n(1) Performance of certain acquisition-related functions.--\nSection 3104(a) of title 10, United States Code, is amended--\n(A) by inserting ``, in accordance with the\nobjectives established pursuant to section 3102 of this\ntitle,'' after ``Secretary of the military department\nconcerned''; and\n(B) by amending paragraphs (1) through (7) to read\nas follows:\n``(1) The development of capability requirement statements\nfor equipping the armed force concerned that--\n``(A) describe the operational problem to provide\nnecessary context for the capability requirement; and\n``(B) describe the solution sought in a non-\nprescriptive manner to allow agile and innovative\ncapability development to address the operational\nproblem;\n``(2) The implementation of strategies to effectively and\nefficiently inform recommendations regarding changes in\ncapability requirements described in paragraph (1).\n``(3) The recommendation of trade-offs among life-cycle\ncosts, delivery schedules, performance objectives, technical\nfeasibility, and procurement quantity objectives to ensure\nacquisition programs deliver the best value for the investment\nmade.\n``(4) In consultation with the Joint Requirements Council,\nthe establishment and prioritization of requirements to\nexpeditiously provide the Armed Forces with the capabilities\nneeded to operate effectively, to address evolving threats, and\nto maintain the military advantage of the United States.\n``(5) The use of data-driven decision making to prioritize\nresource allocation to meet operational readiness requirements\n(as defined in section 4322 of this title) and the materiel\nreadiness objectives established by the Secretary of the\nmilitary department concerned under section 118(c) of this\ntitle.\n``(6) Support for an environment that enables the adoption\nand integration of innovative solutions and technologies to\nenhance military effectiveness and responsiveness.\n``(7) Any recommendation for the termination of the\ndevelopment of capabilities--\n``(A) that no longer align with approved capability\nrequirements or priorities;\n``(B) for which costs have significantly increased;\nor\n``(C) for which schedule delays have been\nsignificant.\n``(8) Support for the development of career paths in\nacquisition for military personnel (as required by section\n1722a of this title) to ensure such personnel have the\nnecessary skills, knowledge, and experience to fulfill the\nobjectives established pursuant to section 3102 of this\ntitle.''.\n(2) Adherence to requirements in major defense acquisition\nprograms.--Section 3104(b) of title 10, United States Code, is\namended--\n(A) in paragraph (1), by striking ``program\ncapability document supporting a Milestone B or\nsubsequent decision'' and inserting ``requirements\ndocuments''; and\n(B) in paragraph (2)--\n(i) in subparagraph (A), by striking\n``prior to entry into the Materiel Solution\nAnalysis Phase under Department of Defense\nInstruction 5000.02''; and\n(ii) in subparagraph (B), by striking\n``cost, schedule, technical feasibility, and\nperformance trade-offs'' and inserting ``life-\ncycle cost, delivery schedule, performance\nobjective, technical feasibility, and\nprocurement quantity trade-offs''.\n(3) Definitions.--Section 3104(d) of title 10, United\nStates Code, is amended to read as follows:\n``(d) Requirements Document Defined.--In this section, the term\n`requirements document' means a document that establishes the need for\na materiel approach to resolve a capability requirement or a joint\ncapability requirement (as such terms are defined in section 181 of\nthis title).''.\n(e) Technical Amendments.--\n(1) Section 3101 of title 10, United States Code, is\namended to read as follows:\n``Sec. 3101. Definitions\n``In this chapter:\n``(1) The term `best value' means, with respect to an\nacquisition, the optimal combination of cost, quality,\ntechnical capability or solution quality, and delivery\nschedule.\n``(2) The term `capability requirement' has the meaning\nprovided in section 181 of this title.\n``(3) The term `cost-effective' means, with respect to an\nacquisition, the capacity to deliver better results for the\nsame or lower cost compared to alternatives.''.\n(2) Section 3001(c) of title 10, United States Code, is\namended by striking ``this section'' and inserting ``this\npart''.\n\nSEC. 102. PROGRAM EXECUTIVE OFFICER RESPONSIBILITIES.\n\n(a) In General.--Subchapter III of chapter 87 of title 10, United\nStates Code, is amended by inserting after section 1731 the following\nnew section:\n``Sec. 1732. Program executive officer\n``(a) In General.--A program executive officer is the senior\nofficial responsible for the oversight of the plans, budgets, and\nexecution of the programs assigned to the portfolio of such senior\nofficial, including life-cycle management.\n``(b) Objectives.--In carrying out the activities described in\nsubsection (a), the program executive officer shall seek to achieve the\nfollowing objectives:\n``(1) Expeditiously provide the Armed Forces with the\ncapabilities needed to operate effectively, address evolving\nthreats, and maintain the military advantage of the United\nStates in the most cost-effective manner practicable.\n``(2) Maximize the effective use of resources by delivering\ncapabilities that offer the best value for the investment made\nin each capability.\n``(3) Enable the integration of innovative solutions and\ntechnologies to enhance military effectiveness and\nresponsiveness to emerging threats.\n``(c) Specific Responsibilities.--\n``(1) In general.--For the programs assigned to the\nportfolio of a program executive officer, such program\nexecutive officer shall be responsible for the following:\n``(A) Provide expeditious delivery of the\ncapabilities necessary to effectively respond to\nnational security challenges by overseeing the\nprocurement, development, and sustainment of defense\nacquisition programs assigned to the program executive\nofficer.\n``(B) Ensure the cost-effective allocation of\nresources by delivering operational capabilities.\n``(C) Adjust requirements, other than requirements\nthat are established as key performance parameters, to\nmaximize the agility and speed in program execution in\naccordance with the objectives described in subsection\n(b).\n``(D) Use iterative development cycles and\ndiscontinue or terminate the development of\ncapabilities--\n``(i) that no longer align with approved\ncapability requirements (as defined in section\n181 of this title) or priorities; or\n``(ii) that are experiencing significant\ncost growth, performance deficiencies, or\ndelays in schedule.\n``(E) Evaluate and implement trade-offs among life-\ncycle costs, delivery schedules, performance\nobjectives, technical feasibility, and procurement\nquantity objectives to ensure acquisition and\nsustainment programs deliver the best value in meeting\ncapability requirements (as defined in section 181 of\nthis title).\n``(F) Use data-driven decisionmaking to prioritize\nresource allocation to meet operational readiness\nrequirements and materiel readiness objectives\nestablished by the Secretary concerned under section\n118(c) of this title.\n``(G) Collaborate with the Mission Engineering and\nIntegration Activity established under section 203 of\nthe SPEED Act to conduct cross-service technical and\noperational activities to integrate emerging\ntechnologies, prototypes, and operational concepts, as\nappropriate.\n``(H) Provide support to the Requirements,\nAcquisition, and Programming Integration Directorate\nwith respect to the performance of the responsibilities\nof the Directorate under section 186 of this title and\nserve as a member of the Directorate in accordance with\nsuch section.\n``(2) Milestone decision authority duties.--A program\nexecutive officer shall be the milestone decision authority for\na program when directed by the service acquisition executive of\nthe military department that is managing the program or if\ndesignated by the Secretary of Defense.\n``(d) Functional Support.--The Secretary concerned with respect to\na program executive officer shall ensure that there is assigned to such\nprogram executive officer the personnel and other resources required\nfor such program executive officer to successfully perform the assigned\nduties and responsibilities of such program executive officer,\nincluding--\n``(1) contracting and contract management;\n``(2) estimating costs;\n``(3) financial management;\n``(4) life-cycle management and product support;\n``(5) program management;\n``(6) engineering and technical management; and\n``(7) developmental testing and evaluation.''.\n(b) Amendment to Definitions.--Section 1737(a)(4) of title 10,\nUnited Stated Code, is amended to read as follows:\n``(4) The term `program executive officer' means an\nindividual described in section 1732(a).''.\n\nSEC. 103. MAJOR CAPABILITY ACTIVITY AREAS AND PATHFINDER PROGRAMS.\n\n(a) Transition Plan Required.--\n(1) Submission of plan.--Not later than one year after the\ndate of the enactment of this Act, the Secretary of Defense, in\ncoordination with each Secretary of a military department,\nshall submit to the congressional defense committees a\ncomprehensive plan for organizing the programs assigned to the\nportfolio of a program executive officer of the Department of\nDefense in a manner primarily organized around major capability\nactivity areas (``MCAAs'').\n(2) Elements of the plan.--The plan required under\nparagraph (1) shall be developed to more effectively facilitate\nthe development, fielding, operation, sustainment, and\nmodernization of capabilities of the Department of Defense in\naccordance with the objectives established pursuant to section\n3102 of title 10, United States Code (as added by section 101\nof this Act). Such plan shall include the following:\n(A) A description of each proposed MCAA, including\nhow the specific capability of the Department of\nDefense that is the subject of each MCAA aligns with\nand supports joint military capabilities.\n(B) A proposed schedule, including benchmarks, for\nphased implementation of the plan to organize the\nprograms of each military department and Defense Agency\nin a manner primarily organized around MCAAs.\n(C) Recommendations for statutory or regulatory\nchanges needed to facilitate the reorganization of\nprogram executive offices to be primarily organized\naround MCAAs.\n(D) A strategy to preserve accountability for the\ndelivery of a capability of the Department of Defense\nthat is the subject of the proposed MCAA and to enable\neffective oversight of the proposed MCAA by the\ncongressional defense committees.\n(E) A description of the process for designating a\nPathfinder under subsection (b).\n(3) Organization by mcaas.--\n(A) In general.--In organizing programs in a manner\nprimarily organized around MCAAs under this subsection,\nthe Secretary shall--\n(i) organize each proposed MCAA in a\ncapability-oriented structure that reflects the\nunique and specific aspects of the subject\ncapability of the MCAA;\n(ii) assign relevant development,\nprocurement, operations, and sustainment\nactivities of the Department to the proposed\nMCAA as appropriate; and\n(iii) ensure each proposed MCAA is\norganized in a manner that--\n(I) will improve the ability to\nmeasure and manage the overall\nperformance in the delivery of the\nsubject capability of the proposed\nMCAA; and\n(II) connects amounts authorized\nfor activities assigned to the proposed\nMCAA to the delivery of subject\ncapability.\n(B) Flexibility.--The Secretary of Defense shall\nensure each military department and Defense Agency has\nflexibility, according to their specific mission\nrequirements, in the organization of proposed MCAAs.\n(b) Designation of Pathfinder MCAAs.--\n(1) Designation.--Not later than 90 days after the date of\nthe enactment of this Act, the Secretary of Defense shall--\n(A) designate at least two program executive\noffices of the Department of Defense to be known as\n``Pathfinders'';\n(B) identify the program executive officer with the\nresponsibility of administering each such Pathfinder;\n(C) ensure each such program executive officer\norganizes the programs assigned to such offices into a\nMCAA in accordance with the requirements of subsection\n(a)(3); and\n(D) submit to the congressional defense committees\na notification of each designation made under\nsubparagraph (A), including the total amount authorized\nto carry out each Pathfinder for fiscal year 2026 and a\ndescription of the MCAA associated with each\nPathfinder.\n(2) Modified transfer authority for pathfinders.--\n(A) Authority.--The Secretary of Defense, acting\nthrough a Secretary of a military department or the\nhead of a Defense Agency, may transfer amounts\nauthorized for programs, projects, or activities that\nare included in a Pathfinder under the jurisdiction of\nsuch Secretary or head among such programs, projects,\nor activities.\n(B) Limitations.--A transfer made under this\nparagraph--\n(i) shall directly support delivery of the\ncapability of the Department of Defense that is\nthe subject of the Pathfinder;\n(ii) may not be used to initiate a new\nstart program (as described in section 3601 of\ntitle 10, United States Code);\n(iii) may not be used to terminate a\nprogram or activity of the Department that was\nin operation on or before the date of the\ndesignation of the Pathfinder; and\n(iv) may not exceed 40 percent of the total\namount authorized to carry out a Pathfinder\nspecified under paragraph (1)(D).\n(3) Additional pathfinders.--The Secretary of Defense may\ndesignate additional MCAAs as Pathfinders under the authority\nof this subsection if the Secretary notifies the congressional\ndefense committees not later than 15 days prior to each such\ndesignation.\n(c) Report to Congress.--\n(1) In general.--Not later than 540 days after the date of\nthe enactment of this Act, and annually thereafter until\nDecember 31, 2029, the Secretary of Defense shall submit to the\ncongressional defense committees a report assessing the\neffectiveness of the use of a capability-oriented structure in\nsubsection (a)(3) and Pathfinders in subsection (b) to--\n(A) improve the ability to measure and manage the\noverall performance in the delivery of the subject\ncapability of the proposed MCAA or Pathfinder;\n(B) inform and improve program management and\nplanning for future activities assigned to the proposed\nMCAA or Pathfinder for the delivery of subject\ncapability; and\n(C) achieve the objectives of the defense\nacquisition system established pursuant to section 3102\nof title 10, United States Code (as added by section\n101 of this Act).\n(2) Contents.--The report required under paragraph (1)\nshall include the following:\n(A) The extent to which the use of MCAAs and use of\nthe transfer authority under subsection (b)(2) for\nPathfinders affect the speed of addressing emerging\nthreats and adopting new technologies.\n(B) An analysis of any costs or benefits of using\nMCAAs.\n(C) Recommendations, including statutory or\nregulatory modifications, for--\n(i) expanding the use of Pathfinders; and\n(ii) continuing the transition to using\nMCAAs.\n(d) Definitions.--In this section:\n(1) The term ``major capability activity area'' or ``MCAA''\nmeans a compilation of activities that relate to the delivery\nof a capability of the Department of Defense, as determined by\nthe Secretary of Defense.\n(2) The term ``joint military capabilities'' has the\nmeaning given in section 181 of title 10, United States Code,\nas amended by section 201 of this Act.\n(3) The term ``program executive officer'' has the meaning\ngiven in section 1732 of title 10, United States Code, as added\nby section 102 of this Act.\n\nSEC. 104. PRODUCT SUPPORT MANAGER RESPONSIBILITIES AND REQUIREMENTS.\n\n(a) In General.--Subchapter III of chapter 87 of title 10, United\nStates Code, is amended by inserting after section 1732 (as added by\nsection 102 of this Act) the following new section:\n``Sec. 1733. Product support manager\n``(a) In General.--A product support manager is the individual\nresponsible for managing support functions required to field and\nmaintain the readiness and operational capability of a covered system\nin support of the life-cycle management responsibilities of the program\nmanager for such covered system.\n``(b) Objectives.--In carrying out the activities described in\nsubsection (a), the product support manager shall seek to achieve the\nobjectives of the defense acquisition system established pursuant to\nsection 3102 of this title.\n``(c) Specific Responsibilities.--A product support manager shall\nbe responsible for the following:\n``(1) Provide product support and subject matter expertise\nwith respect to a covered system to the program manager for the\ncovered system to assist with the development, resourcing,\nimplementation, and execution of the product support strategy\ndeveloped by the product support manager under section 4322 of\nthis title for the covered system.\n``(2) Collaborate with the chief engineer and systems\nengineers for the covered system--\n``(A) to develop the life-cycle sustainment plan\nand any product support plans for the covered system;\nand\n``(B) to analyze the operating and support costs of\nthe covered system to ensure the cost-effective\noperation, management, and availability of the covered\nsystem.\n``(3) Conduct early risk identification, mitigation, and\nproduct support analyses that inform best value solutions in\nlife-cycle planning and management.\n``(4) Provide input on systems engineering requirements,\ndesign, budgeting, maintenance planning, and acquisition\nstrategies for covered systems.\n``(5) Support the program manager in evaluating trade-offs\namong life-cycle costs, delivery schedules, performance\nobjectives, technical feasibility, and procurement quantity\nobjectives to ensure each covered system delivers the greatest\nvalue for the investment made in the covered system.\n``(6) Use data-driven decision making, predictive analysis,\nand appropriate modeling tools related to reliability and\nmaintainability of the covered system to prioritize resource\nallocation to meet operational readiness requirements and\nmateriel readiness objectives (established under section 118(c)\nof this title).\n``(7) Support each Secretary of a military department in\nperformance of a core logistics analysis pursuant to section\n2464 of this title.\n``(d) Covered System Defined.--In this section, the term `covered\nsystem' has the meaning given in section 4322 of this title.''.\n(b) Education, Training, and Experience Requirements for Product\nSupport Managers.--Section 1735 title 10, United States Code, is\namended--\n(1) by redesignating subsections (c), (d), and (e) as\nsubsections (d), (e), and (f), respectively; and\n(2) by inserting after subsection (b) the following new\nsubsection:\n``(c) Product Support Manager.--Before being assigned to a position\nas product support manager, a person--\n``(1) shall have completed all life-cycle logistics\ncertification and training requirements prescribed by the\nSecretary of Defense;\n``(2) shall have executed a written agreement as required\nin section 1734(b)(2) of this title; and\n``(3) in the case of--\n``(A) a product support manager of a major defense\nacquisition program, shall have at least eight years of\nexperience in life-cycle logistics, at least two years\nof which were performed in a systems program office or\nsimilar organization; and\n``(B) a product support manager of a significant\nnonmajor defense acquisition program, shall have at\nleast six years of experience in life-cycle\nlogistics.''.\n(c) Conforming Amendments.--Section 1731(a)(1)(B) title 10, United\nStates Code, is amended by adding at the end the following new clause:\n``(iv) Product support manager.''.\n\nSEC. 105. AMENDMENTS TO LIFE-CYCLE MANAGEMENT AND PRODUCT SUPPORT.\n\n(a) Reorganization of Life-Cycle and Sustainment Chapter.--\n(1) In general.--Chapter 323 of title 10, United States\nCode, is amended--\n(A) by repealing sections 4321, 4323, and 4324;\n(B) by redesignating section 4328 as section 4321\nand transferring such section so as to appear after the\ntable of sections at the beginning of such chapter;\n(C) by redesignating section 4325 as section 4323\nand transferring such section so as to appear after\nsection 4321;\n(D) in section 4323, as so redesignated, by\nstriking ``section 4324 of this title'' and inserting\n``section 4322 of this title''; and\n(E) by amending the table of sections at the\nbeginning of such chapter to read as follows:\n\n``4321. Weapon system design: sustainment factors.\n``4322. Life-cycle management and product support.\n``4323. Major weapon systems: assessment, management, and control of\noperating and support costs.''.\n(2) Conforming amendments.--\n(A) Section 3041(a) of title 10, United States\nCode, is amended by striking ``sections 4292(e) and\n4321'' and inserting ``section 4292(e)''.\n(B) Section 3221(b)(2) of title 10, United States\nCode, is amended by striking ``4321, 4323, and 4328 of\nthis title'' and inserting ``and 4321 of this title,''.\n(C) Section 4211(c)(2)(D) of title 10, United\nStates Code, is amended by striking ``section 4324 of\nthis title'' and inserting ``section 4322 of this\ntitle''.\n(D) Section 4252(b)(14) of title 10, United States\nCode, is amended by striking ``section 4324(b) of this\ntitle'' and inserting ``section 4322 of this title''.\n(b) Life-Cycle Management and Product Support.--Chapter 323 of\ntitle 10, United States Code, as amended by subsection (a), is further\namended by inserting after section 4321 the following new section:\n``Sec. 4322. Life-cycle management and product support\n``(a) In General.--The Secretary of Defense shall ensure that each\ncovered system is supported by a life-cycle sustainment plan--\n``(1) that is approved by the senior acquisition executive\nresponsible for such covered system; and\n``(2) that meets applicable operational readiness\nrequirements and materiel readiness objectives (established\nunder section 118(c) of this title) in the most cost-effective\nmanner practicable.\n``(b) Product Support Manager.--The Secretary of Defense shall\ndesignate a product support manager (as defined in section 1733 of this\ntitle) to serve under the supervision of a program manager for each\ncovered system.\n``(c) Life-Cycle Sustainment Plan.--(1) A product support manager\nshall develop, update, and implement a life-cycle sustainment plan for\neach covered system for which the product support manager is\nresponsible. Such plan shall include the following:\n``(A) A comprehensive product support strategy to best\nachieve operational readiness requirements and materiel\nreadiness objectives throughout the planned life cycle of such\nsystem.\n``(B) A baseline life-cycle cost estimate for the covered\nsystem based on the planned product support strategy described\nin subparagraph (A).\n``(C) Recommended engineering and design considerations\nthat support cost-effective sustainment of the covered system\nand best value solutions in life-cycle planning and management.\n``(D) An intellectual property management plan for product\nsupport developed in accordance with section 3774 of this\ntitle.\n``(E) A strategy to maximize use of public and private\nsector capabilities to establish Government-private\npartnerships--\n``(i) with appropriate incentives for each partner\nto contribute to the achievement of operational\nreadiness requirements and materiel readiness\nobjectives in the most cost-effective manner\npracticable; and\n``(ii) that considers the roles of each partner as\nthe covered system transitions from acquisition,\ndevelopment, production, fielding, sustainment, and\ndisposal.\n``(F) A plan to transition the covered system from\nproduction to initial fielding that addresses specific products\nor services required for successful initial fielding of the\ncovered system, including--\n``(i) a description of the necessary tooling or\nother unique support equipment, requirements for\ninitial spare parts and components, technical handbooks\nand maintenance manuals, maintenance training, and\nfacilities;\n``(ii) an identification of the funding required to\nprovide such products and services for any initial\nfielding location of the covered system;\n``(iii) an identification of any procurement line,\nprogram element, or subactivity group in the budget of\nthe Secretary concerned associated with such products\nor services;\n``(iv) the timeline for delivery of such products\nand services; and\n``(v) an assessment of any reduction in operational\nreadiness requirements and materiel readiness\nobjectives if such products and services are not\nprovided in accordance with clause (iv).\n``(2) In developing each life-cycle sustainment plan required by\nthis section, the product support manager shall consider the following:\n``(A) Affordability constraints and key cost factors that\ncould affect operating and support costs during the life cycle\nof the covered system.\n``(B) Sustainment risks or challenges to sustaining the\ncovered system in operational environments, included contested\nlogistics environments (as defined in section 2926 of this\ntitle).\n``(C) Compliance with--\n``(i) requirements to maintain a core logistics\ncapability under section 2464 of this title; and\n``(ii) limitations on the performance of depot-\nlevel maintenance of materiel under section 2466 of\nthis title.\n``(D) A defense industrial base strategy to maintain a\nrobust, resilient, and innovative defense industrial base to\nsupport requirements throughout the life cycle of the covered\nsystem.\n``(d) Continuous Assessment and Active Management.--In carrying out\nthe duties of this section and section 1733 of this title, the product\nsupport manager shall--\n``(1) continuously assess and actively manage performance\nof each covered system for which the product support manager is\nresponsible against the life-cycle sustainment plan for such\ncovered system; and\n``(2) as appropriate, integrate commercial best practices,\nuse commercial standards, and use advanced technologies to\nenhance the product support of each covered system.\n``(e) Recommendations.--(1) The product support manager shall\nrecommend changes to the product support strategy required under\nsubsection (c)(1)(A) of a covered system to the program manager\nresponsible for such covered system to meet the requirements of\nsubsection (a).\n``(2) The program manager shall provide to the senior acquisition\nexecutive responsible for a covered system any recommendations for such\ncovered system made under paragraph (1) that the program manager did\nnot implement along with the rationale for not implementing such\nrecommendations.\n``(f) Definitions.--In this section:\n``(1) The term `covered system' means--\n``(A) a major defense acquisition program as\ndefined in section 4201 of this title;\n``(B) a major subprogram as described in section\n4203 of this title; or\n``(C) an acquisition program or project that is\ncarried out using the rapid fielding or rapid\nprototyping acquisition pathway under section 3602 of\nthis title that is estimated by the Secretary of\nDefense to require an eventual total expenditure\ndescribed in section 4201(a)(2) of this title.\n``(2) The term `operational readiness' means the capability\nof a unit of the Armed Forces, vessel, weapon system, or\nequipment to perform the missions or functions for which it is\norganized or designed.\n``(3) The term `product support' means the set of support\nfunctions, as determined by the product support manager,\nrequired to field and maintain the readiness and operational\ncapability of a covered system, or a subsystem or component of\na covered system.''.\n(c) Conforming Amendments to Materiel Readiness Metrics and\nObjectives for Major Weapon Systems.--Section 118 of title 10, United\nStates Code, is amended--\n(1) in the section heading, by inserting ``materiel\nreadiness'' before ``objectives'';\n(2) in subsection (b), by striking ``shall address'' and\ninserting ``shall establish procedures and a computation\nmethodology to determine'';\n(3) in subsection (c)--\n(A) in paragraph (1), by striking ``the metrics\nrequired'' and all that follows through the period at\nthe end and inserting ``materiel readiness objectives\nfor each major weapon system.''; and\n(B) in paragraph (2), by striking ``the metrics\nrequired by subsection (b)'' and inserting ``such\nreadiness objectives'';\n(4) in subsection (d)(2), by striking ``readiness goals or\nobjectives'' and inserting ``materiel readiness objectives'';\n(5) in subsection (e), in the matter preceding paragraph\n(1), by inserting a comma after ``designated mission''; and\n(6) in subsection (f)--\n(A) by redesignating paragraphs (3), (4), and (5)\nas paragraphs (4), (5), and (6), respectively; and\n(B) by inserting after paragraph (2) the following\nnew paragraph:\n``(3) The term `materiel readiness objective' means the\nminimum required availability of each major weapon system that\nis necessary to fulfill the requirements of the strategic\nframework and guidance referred to in subsection (a).''.\n\nSEC. 106. NAVY SENIOR TECHNICAL AUTHORITY.\n\nSection 8669b of title 10, United States Code, is amended--\n(1) in subsection (a)(2), by amending subparagraph (B) to\nread as follows:\n``(B) reports directly to the program executive\nofficer.''; and\n(2) in subsection (b)--\n(A) by inserting ``(1)'' before ``Each Senior'';\nand\n(B) by adding at the end the following new\nparagraph:\n``(2) Each Senior Technical Authority shall also be responsible for\nthe determination that all design requirements for a vessel class are\ndirectly related to a key performance parameter or key system attribute\nestablished in the capability development document for the vessel\nclass. Any requirements that the Senior Technical Authority determines\nare unnecessary to meet a key performance parameter or key system\nattribute shall not be approved.''.\n\nTITLE II--ACCELERATING THE REQUIREMENTS PROCESS\n\nSEC. 201. JOINT REQUIREMENTS COUNCIL.\n\n(a) Implementation.--Not later than 30 days after the date of the\nenactment of this Act, the Chairman of the Joint Chiefs shall revise\npolicies for the Joint Strategic Planning System (established under the\nChairman of the Joint Chiefs of Staff Instruction 3100.01F), the Manual\nfor the Operation of the Joint Capabilities Integration and Development\nSystem (issued October 30, 2021) and any other relevant instructions,\npolicies, or guidance to carry out the requirements of this section and\nthe amendments made by this section.\n(b) Amendment to Name and Mission of Joint Requirements Oversight\nCouncil.--Section 181 of title 10, United States Code, is amended--\n(1) in the section heading, by striking ``Oversight'';\n(2) in subsection (a), by striking ``Joint Requirements\nOversight Council in the Department of Defense.'' and inserting\nthe following: ``Joint Requirements Council (in this section\nreferred to as the `Council') in the Department of Defense. The\nCouncil shall--\n``(1) assist the Chairman of the Joint Chiefs of Staff in\ncarrying out the functions described in section 153 of this\ntitle; and\n``(2) provide recommendations for addressing joint\noperational problems to the Requirements, Acquisition, and\nProgramming Integration Directorate established under section\n186 of this title (in this section referred to as `RAPID').'';\nand\n(3) by striking ``Joint Requirements Oversight Council''\neach place it appears and inserting ``Joint Requirements\nCouncil''.\n(c) Duties.--Subsection (b) of such section 181 is amended to read\nas follows:\n``(b) Duties.--The Council shall support the objectives established\npursuant to section 3102 of this title by performing the following\nduties:\n``(1) Continuously evaluating global trends, adversary\ncapabilities, and emerging threats to inform awareness and\nunderstanding of joint operational problems.\n``(2) In coordination with commanders of combatant\ncommands, compiling, refining, and prioritizing joint\noperational problems.\n``(3) Identifying and prioritizing gaps in joint military\ncapabilities to address joint operational problems.\n``(4) Identifying advances in technology and innovative\nconcepts of operation that could improve the ability of the\njoint force to address evolving threats and maintain the\nmilitary advantage of the United States.\n``(5) Developing a joint capability requirement statement\nthat--\n``(A) describes the joint operational problem to\nprovide necessary context for the joint capability\nrequirement; and\n``(B) describes the solution sought in a\nnonprescriptive manner to allow agile and innovative\ndevelopment of joint capability requirements to address\nthe joint operational problem.\n``(6) Making the following recommendations to RAPID:\n``(A) With respect to a quick action requirement,\nactions to fulfill such quick action requirement, not\nlater than 30 days after receipt or identification of\nsuch quick action requirement.\n``(B) Actions to fulfill each joint capability\nrequirement necessary to address joint operational\nproblems, not later than 60 days after receipt or\nidentification of such a joint operational problem.\n``(C) Modifications to joint force design suitable\nfor addressing joint operational problems or\neffectively integrating advancements in technology and\nnew concepts of operation.\n``(D) Ways to improve operational effectiveness,\nincrease operational flexibility, or improve\ninteroperability and coordination between and among\njoint military capabilities and the military\ncapabilities of allies or partners.\n``(7) Providing notification to Deputy Secretary of\nDefense--\n``(A) upon receipt or identification of a quick\naction requirement; and\n``(B) upon submission of any recommendation to\nRAPID.''.\n(d) Composition.--Subsection (c) of such section 181 is amended--\n(1) in paragraph (1)(A)--\n(A) by inserting ``and RAPID'' before ``for making\nrecommendations''; and\n(B) by striking ``joint performance requirements''\nand inserting ``joint capability requirements''; and\n(2) in paragraph (3), by inserting ``and RAPID'' after\n``Chairman of the Joint Chiefs of Staff''.\n(e) Advisors.--Subsection (d) of such section 181 is amended--\n(1) in paragraph (2)--\n(A) by inserting ``strongly'' before ``consider'';\nand\n(B) by striking ``its mission under paragraphs (1)\nand (2) of subsection (b)'' and inserting ``the duties\ndescribed in subsection (b)''; and\n(2) in paragraph (3)--\n(A) by striking ``seek, and strongly consider,''\nand inserting ``seek and consider'';\n(B) by striking ``, in their roles as customers of\nthe acquisition system,''; and\n(C) by striking ``under subsection (b)(2) and joint\nperformance requirements pursuant to subsection\n(b)(3)''.\n(f) Responsibility for Capability Requirements.--Subsection (e) of\nsuch section 181 is amended to read as follows:\n``(e) Responsibility for Capability Requirements.--The Chief of\nStaff of an armed force is responsible for the capability requirements\nfor that armed force.''.\n(g) Analytic and Engineering Support.--Subsection (f) of such\nsection 181 is amended--\n(1) in the subsection heading, by inserting ``and\nEngineering'' after ``Analytic'';\n(2) by inserting ``and the Mission Engineering and\nIntegration Activity established under section 203 of the SPEED\nAct'' after ``the Office of Cost Assessment and Program\nEvaluation''; and\n(3) by striking ``in operations research, systems analysis,\nand cost estimation to the Joint Requirements Oversight\nCouncil''.\n(h) Availability of Information to Congressional Defense\nCommittees.--Subsection (g) of such section 181 is amended--\n(1) in the subsection heading, by striking ``Oversight'';\nand\n(2) by striking ``oversight information'' and inserting\n``information''.\n(i) Definitions.--Subsection (h) of such section 181 is amended to\nread as follows:\n``(h) Definitions.--In this section:\n``(1) The term `capability requirement' means a requirement\nfor a capability that is critical or essential to address an\noperational problem.\n``(2) The term `joint capability requirement' means a\ncapability requirement, including a capability requirement\nrelated to a requirement for joint force interoperability, that\nis critical or essential to address a specific joint\noperational problem.\n``(3) The term `joint military capabilities' means the\ncollective capabilities across the joint force, including both\njoint and force-specific capabilities, that are available to\nconduct military operations.\n``(4) The term `joint operational problem' means a joint\nchallenge faced by a combatant command in achieving an assigned\nmilitary objective and may include limitations in capabilities,\nresources, or the ability to effectively and efficiently\ncoordinate across the joint force, with another combatant\ncommand, among joint military capabilities, or with the\nmilitary capabilities of allies or partners.\n``(5) The term `operational problem' means a challenge or\nbarrier in an operational environment that needs to be overcome\nto achieve a specific military objective.\n``(6) The term `quick action requirement' has the meaning\ngiven in Department of Defense Directive 5000.71 titled `Rapid\nFulfillment of Combatant Commander Urgent Operational Needs'\n(August 24, 2012).''.\n(j) Conforming Amendments.--\n(1) Title 10, united states code.--Title 10, United States\nCode, is amended--\n(A) in section 139a, by striking ``Joint\nRequirements Oversight Council'' each place it appears\nand inserting ``Joint Requirements Council'';\n(B) in section 153(a)(5)(F), by striking ``section\n181 of this title'' and inserting ``sections 181 and\n186 of this title'';\n(C) in section 179(c)(9)--\n(i) by striking ``Joint Requirements\nOversight Council'' and inserting ``Joint\nRequirements Council''; and\n(ii) by striking ``section 181(h)'' and\ninserting ``section 181'';\n(D) in section 2926(f)(5)(C), by striking\n``describing'' and all that follows through ``details\nregarding'' and inserting ``describing details\nregarding'';\n(E) in section 3067(b)(1), by striking ``Joint\nRequirements Oversight Council'' and inserting ``Joint\nRequirements Council'';\n(F) in section 3136(e)(1)(A)(ii), by striking\n``approved by the Joint Requirements Oversight Council\nand'' and inserting ``recommended for approval by the\nRequirements, Acquisition, and Programming Integration\nDirectorate (established under section 186 of this\ntitle)'';\n(G) in section 4202(a)(2)(A), by striking ``joint\nmilitary requirement'' and all that follows through the\nperiod at the end and inserting the following: ``joint\ncapability requirement, as determined by the\nRequirements, Acquisition, and Programming Integration\nDirectorate (established under section 186 of this\ntitle)'';\n(H) by amending section 4251(e)(1) to read as\nfollows:\n``(1) The term `requirements document' has the meaning\ngiven in section 3104(d) of this title.'';\n(I) in section 4252(b)(9), by striking ``Joint\nRequirements Oversight Council'' and inserting ``Joint\nRequirements Council'';\n(J) in section 4376--\n(i) in subsection (a), by striking ``,\nafter consultation with the Joint Requirements\nOversight Council regarding program\nrequirements,'';\n(ii) in subsection (b)(2)(B), by striking\n``joint military requirement (as defined in\nsection 181(g)(1) of this title) at less cost''\nand inserting ``joint capability requirement\n(as defined in section 181 of this title) at\nless cost''; and\n(iii) in subsection (c)(3), by striking\n``joint military requirements'' and inserting\n``joint capability requirements''; and\n(K) in section 5514(b)(2)(C)(ii), by striking\n``Joint Requirements Oversight Council'' and inserting\n``Joint Requirements Council''.\n(2) Other laws.--\n(A) Section 902(d) of the National Defense\nAuthorization Act for Fiscal Year 2024 (10 U.S.C. 139a\nnote) is amended--\n(i) by striking ``, performance\nrequirements, and joint performance\nrequirements'' and inserting ``or performance\nrequirements''; and\n(ii) by striking ``Joint Requirements\nOversight Council to validate such\nrequirements'' and inserting ``Joint\nRequirements Council''.\n(B) Section 1684(d)(4)(A)(i) of the National\nDefense Authorization Act for Fiscal Year 2024 (10\nU.S.C. 2271 note) is amended by striking ``either\napproved by, or in development for, the Joint\nRequirements Oversight Council'' and inserting ``in\ndevelopment for consideration or under consideration by\nthe Joint Requirements Council''.\n(C) Section 1686(b)(1) of the National Defense\nAuthorization Act for Fiscal Year 2024 (10 U.S.C. 2224\nnote) is amended by striking ``through the Joint\nRequirements Oversight Council'' and inserting ``in\nconsultation with the Requirements, Acquisition, and\nProgramming Integration Directorate (established under\nsection 186 of title 10, United States Code)''.\n(D) Section 1510(b)(2) of the National Defense\nAuthorization Act for Fiscal Year 2023 (10 U.S.C. 113\nnote) is amended by striking ``Joint Requirements\nOversight Council'' and inserting ``Joint Requirements\nCouncil''.\n(E) Section 915(a)(1) of the National Defense\nAuthorization Act for Fiscal Year 2023 (10 U.S.C. 132\nnote) is amended by striking ``Joint Requirements\nOversight Council'' and inserting ``Joint Requirements\nCouncil''.\n(F) Section 938(a)(1) of the National Defense\nAuthorization Act for Fiscal Year 2014 (10 U.S.C. 4571\nnote prec.) is amended by striking ``Joint Requirements\nOversight Council'' and inserting ``Joint Requirements\nCouncil''.\n(3) Repeals.--The following provisions of law are repealed:\n(A) Section 942 of the National Defense\nAuthorization Act for Fiscal Year 2008 (10 U.S.C. 181\nnote).\n(B) Section 916 of the Floyd D. Spence National\nDefense Authorization Act for Fiscal Year 2001 (10\nU.S.C. 181 note).\n(C) Section 105(b) of the Weapon Systems\nAcquisition Reform Act of 2009 (10 U.S.C. 181 note).\n(D) Section 201 of the Weapon Systems Acquisition\nReform Act of 2009 (10 U.S.C. 3102 note).\n\nSEC. 202. ESTABLISHMENT OF THE REQUIREMENTS, ACQUISITION, AND\nPROGRAMMING INTEGRATION DIRECTORATE.\n\n(a) In General.--Chapter 7 of title 10, United States Code, is\namended by inserting after section 185 the following new section:\n``Sec. 186. Requirements, Acquisition, and Programming Integration\nDirectorate\n``(a) Establishment.--There is within the Department of Defense a\nRequirements, Acquisition, and Programming Integration Directorate (in\nthis section referred to as `RAPID').\n``(b) Purposes.--RAPID shall--\n``(1) serve as the principal forum within the Department of\nDefense to inform, coordinate, and evaluate solutions to joint\noperational problems;\n``(2) provide senior oversight, coordination, and budget\nand capability harmonization with respect to such matters; and\n``(3) act as an advisory body to the Secretary of Defense\nand the Deputy Secretary of Defense with respect to such\nmatters.\n``(c) Organization and Membership.--RAPID shall consist of the\nfollowing members:\n``(1) The Chairman of the Joint Requirements Council and\nthe Director of Cost Assessment and Program Evaluation, who\nshall serve as co-directors of RAPID.\n``(2) One member designated by each commander of a\ncombatant command.\n``(3) One member designated by the Chairman of the Joint\nRequirements Council.\n``(4) One member designated by the Director of Cost\nAssessment and Program Evaluation.\n``(5) One member designated by each service acquisition\nexecutive of a military department.\n``(6) One member designated by the principal staff\nassistant for the Mission Engineering and Integration Activity\n(established under section 203 of the SPEED Act).\n``(7) One member designated by the executive director of\nthe Joint Rapid Acquisition Cell (as described in the\nDepartment of Defense Directive 5000.71 titled `Rapid\nFulfillment of Combatant Commander Urgent Operational Needs'\n(August 24, 2012)).\n``(8) One member designated by each portfolio executive\nofficer or a similar member of the acquisition workforce\nresponsible for the execution of a recommendation under\nconsideration by RAPID.\n``(d) Responsibilities.--(1) RAPID shall--\n``(A) promptly convene relevant members to assess a\nproposed joint capability requirement to address a joint\noperational problem by considering, with respect to such\nproposed joint capability requirement--\n``(i) associated resource requirements;\n``(ii) mission engineering and interoperability\nconsiderations for integration into joint\narchitectures; and\n``(iii) factors related to acquisition and\nsustainment; and\n``(B) provide prioritized recommendations for solutions to\nsuch joint operational problem to the Secretary of Defense and\nDeputy Secretary of Defense.\n``(2) In carrying out paragraph (1), RAPID shall--\n``(A) use data-driven decisionmaking to prioritize resource\nallocation;\n``(B) maximize the effective use of resources by enabling\ntimely delivery of solutions to address a joint operational\nproblem in a manner that provides the greatest value for the\ninvestment made;\n``(C) enable the adoption and integration of solutions to\nenhance military effectiveness and responsiveness to emerging\nthreats; and\n``(D) in addition to any other considerations required\nunder this subsection, consider--\n``(i) joint capability requirement statements or\nother relevant justification materials provided by the\nJoint Requirements Council;\n``(ii) any analysis and recommendations provided by\nthe Mission Engineering and Integration Activity or the\nDirector of Cost Assessment and Program Evaluation\nrelating to resource requirements described in\nparagraph (1)(A)(i);\n``(iii) recommendations from relevant service\nacquisition executives or program executive officers\nrelated to planning and execution of the proposed joint\ncapability requirement, including budget planning and\nmanagement, acquisition approach, program management,\nand life-cycle management for a proposed joint\ncapability requirement; and\n``(iv) the need to incorporate measure for\ntechnology protection in certain covered systems to\nenable the use or sale of proposed technology solutions\nto joint operational problems with allies and partner\ncountries in a manner that protects national security\ninterest while promoting international collaboration.\n``(e) Recommendation.--(1) Not later than 30 days after the date of\nreceipt of a recommendation with respect to a joint capability\nrequirement for a joint operational problem, from the Joint\nRequirements Council in accordance with section 181 of this title,\nRAPID shall submit to the Deputy Secretary of Defense a recommendation\nfor a solution to the joint operational problem that includes the\nfollowing:\n``(A) A description of the resources needed to implement\nthe solution and, as appropriate, resources needed to support\nthe acquisition and sustainment of such solution of over the\nanticipated life cycle of the solution.\n``(B) Any recommended actions necessary to enable\nintegration of the solution into the joint force or to revise\njoint concepts of operation to best resolve the joint\noperational problem.\n``(C) With respect to a solution for which access may be\nshared with an ally or partner country, recommended\nconsiderations--\n``(i) to be incorporated during the design and\ndevelopment phase of the solution; and\n``(ii) to facilitate future production and\nlogistics support for the solution to the ally or\npartner country.\n``(D) Any necessary changes to policy or guidance to enable\neffective acquisition, fielding, and employment of a solution\nthat is a joint military capability.\n``(E) Any other recommended actions to expeditiously\nprovide the Armed Forces with the capabilities necessary to\noperate effectively, to address evolving threats, and to\nmaintain the military advantage of the United States in the\nmost cost-effective manner practicable.\n``(2) The co-chairs of RAPID may request an additional amount of\ntime, not to exceed 30 days, to provide a recommendation related to a\njoint capability requirement that is not a quick action requirement to\nthe Deputy Secretary of Defense under this subsection.\n``(f) Determination.--(1) Not later than 30 days after receipt of a\nrecommendation under subsection (e), the Deputy Secretary of Defense\nshall issue a memorandum that approves, approves with modification, or\nrejects such a recommendation.\n``(2) The Deputy Secretary of Defense shall include along with a\nmemorandum that approves or approves with modification a recommendation\ndescribed in paragraph (1) specific direction and guidance to the\napplicable element of the Department of Defense to which such\nrecommendation applies.\n``(3) The Deputy Secretary of Defense shall include along with a\nmemorandum that rejects a recommendation described in paragraph (1) a\nspecific direction--\n``(A) for alternative action to be taken by the applicable\nelement of the Department of Defense to which such\nrecommendation applies to address the relevant joint\noperational problem; or\n``(B) to RAPID for further action to address the relevant\njoint operational problem.\n``(g) Notification.--If the Deputy Secretary of Defense fails to\nissue a memorandum as required by subsection (f) within 90 days after\nthe date on which the Joint Requirements Council provides a\nrecommendation to address a joint operational problem to the RAPID, the\nSecretary of Defense shall submit to the congressional defense\ncommittees a notification of such failure.\n``(h) Definitions.--In this section:\n``(1) The terms `joint capability requirement', `joint\nmilitary capability', `joint operational problem', and `quick\naction requirement' have the meanings given, respectively, in\nsection 181 of this title.\n``(2) The term `relevant member' means a member of RAPID\n(or a designee) that has a primary interest in, or\nresponsibility for, a proposed joint capability requirement or\nquick action requirement under assessment by RAPID.''.\n(b) Conforming Amendments to Director of Cost Assessment and\nProgram Evaluation.--Section 139a(d) of title 10, United States Code,\nis amended--\n(1) by redesignating paragraphs (4) through (9) as\nparagraphs (5) through (10), respectively; and\n(2) by inserting after paragraph (3) the following new\nparagraph:\n``(4) Analysis and advice for resource discussions relating\nto joint capability requirements under consideration by the\nRequirements, Acquisition, and Programming Integration\nDirectorate pursuant to section 186 of this title.''.\n\nSEC. 203. ESTABLISHMENT OF THE MISSION ENGINEERING AND INTEGRATION\nACTIVITY.\n\n(a) Establishment.--Not later than 120 days after the date of the\nenactment of this Act, the Secretary of Defense shall establish within\nthe Department of Defense a Mission Engineering and Integration\nActivity (in this section referred to as ``MEIA'').\n(b) Designation.--The Secretary of Defense shall designate a\nprincipal staff assistant from within the Office of the Secretary of\nDefense whose office shall serve as the office of primary\nresponsibility for MEIA.\n(c) Duties.--The principal staff assistant designated under\nsubsection (b) shall have the following duties:\n(1) Lead cross-service activities to develop, identify,\nanalyze, and validate integrated technology solutions to\naddress joint operational problems.\n(2) Coordinate with the appropriate program executive\nofficers to align and implement such activities.\n(3) Proactively seek and consider feedback of the primary\nusers and operators of proposed technology solutions to address\njoint operational problems throughout the implementation of\nsuch activities.\n(4) Upon request, perform analysis for, experiment with,\nand prototype technology to integrate such technology into\njoint architectures, to use such technology, to inform\noperational concepts, and to provide analysis or\nrecommendations regarding the use of such technology to the\nRequirements, Acquisition, and Programming Integration\nDirectorate, established by section 186 of title 10, United\nStated Code (in this section referred to as ``RAPID'').\n(5) Coordinate with commanders of the combatant commands to\nunderstand the priorities of commanders and support the\nfielding of integrated technology solutions to address joint\noperational problems.\n(6) Upon request, assist a program executive officer in\ncarrying out the responsibilities established under section\n1732 of title 10, United States Code (as added by section 102\nof this Act), by providing analysis, recommendations, and\nengineering assistance in the integration of technology\nsolutions related to the capabilities for which the program\nexecutive officer is responsible.\n(7) Use existing authorities (including authorities\nprovided in section 4022 of title 10, United States Code) to\ncarry out this section.\n(d) Implementation Plan.--\n(1) Plan.--Not later than 90 days after the date of the\nenactment of this Act, the Secretary of Defense shall submit to\nthe congressional defense committees an implementation plan for\nMEIA.\n(2) Elements.--The plan required by paragraph (1) shall\ninclude a description of the following:\n(A) The organizational structure and resource\nrequirements associated with the establishment and\noperation of MEIA.\n(B) How MEIA will support and inform the RAPID in\ncarrying out the requirements of section 186 of title\n10, United States Code.\n(C) Each budget line item or program element that\nwill be associated with the activities of MEIA.\n(D) Coordination between MEIA and relevant elements\nof the Department of Defense that are established to\nidentify and support the development of,\nexperimentation with, and integration of technology\nsolutions to address joint operational problems for the\nDepartment, including--\n(i) the Defense Innovation Unit established\nunder section 4217 of the title 10, United\nStates Code;\n(ii) the Defense Research and Development\nRapid Innovation Program established under\nsection 4061 of such title;\n(iii) a entity of the Department of Defense\nthat is a member of the Defense Innovation\nCommunity of Entities established by the\nDirector of the Defense Innovation Unit;\n(iv) the Strategic Capabilities Office; and\n(v) recipients of awards under the Small\nBusiness Innovation Research Program or the\nSmall Business Technology Transfer Program (as\ndefined in section 9 of the Small Business Act\n(15 U.S.C. 638)).\n(E) How MEIA will coordinate with and assist--\n(i) the commanders of combatant commands in\nfielding integrated technology solutions to\naddress joint operational problems under\nsubsection (c)(5); and\n(ii) the program executive officers and\neach Secretary of a military department in the\nintegration of technology to enhance military\neffectiveness and responsiveness.\n(F) Any recommendations for changes to statute or\npolicy for successful implementation of this section.\n(e) Assessment.--Not later than five years after the date of the\nestablishment of MEIA, the Secretary of Defense shall submit to the\ncongressional defense committees an assessment of whether MEIA should\nbe modified, made permanent, or terminated based on its effectiveness\nin carrying out the requirements of this section.\n(f) Joint Operational Problem Defined.--In this section, the term\n``joint operational problem'' has the meaning given in section 181 of\ntitle 10, United States Code.\n\nTITLE III--STRIKING THE BALANCE BETWEEN REGULATION AND EFFICIENCY\n\nSEC. 301. MATTERS RELATED TO DEPARTMENT OF DEFENSE USE OF COST\nACCOUNTING STANDARDS.\n\n(a) Reduction or Elimination of CAS.--\n(1) In general.--Not later than 90 days after the date of\nthe enactment of this Act, the Secretary of Defense shall--\n(A) identify actions necessary to streamline\nrequirements for compliance with the cost accounting\nstandards established under section 1502 of title 41,\nUnited States Code (in this section referred to as\n``CAS''), in the performance of a contract with the\nDepartment of Defense; and\n(B) reduce or eliminate such requirements under the\ncircumstances described in paragraph (2).\n(2) Circumstances described.--The circumstances described\nin this paragraph are as follows:\n(A) With respect to an action to eliminate\ncompliance with CAS, if reliance on a similar\nrequirement under generally accepted accounting\nprinciples (in this section referred to as ``GAAP'')\nwould materially achieve uniformity and consistency in\ncost accounting with respect to such elimination\nwithout bias or prejudice to parties to a contract.\n(B) If other existing requirements in guidance or\nregulation will sufficiently protect the interests of\nthe Secretary of Defense in the oversight of cost\ncontracts.\n(C) If such requirement is no longer necessary or\nappropriate.\n(b) Assessment of GAAP To Meet Department of Defense Needs.--\n(1) In general.--The Secretary of Defense shall conduct an\nassessment of the steps necessary to enable the use of GAAP\ninstead of CAS as the baseline for standards of financial\naccounting and reporting for the contracts of the Department of\nDefense. Such assessment shall include--\n(A) an identification of needed changes to law,\nregulation, or policy to enable the Secretary to\neliminate the use of CAS and implement the use of GAAP\nas such baseline; and\n(B) an identification any Department-specific\nstandards that would be required in addition to GAAP to\nsupport the unique requirements of defense contracts.\n(2) Report.--Not later than 180 days after the date of the\nenactment of this Act, the Secretary shall submit to the\ncongressional defense committees a report on the findings of\nthe assessment required by paragraph (1), along with any\nrecommended actions for Congress to reduce or eliminate\nrequirements for compliance with CAS.\n\nSEC. 302. REVIEW OF COMMERCIAL BUYING PRACTICES.\n\n(a) Review Required.--\n(1) In general.--Not later than 120 days after the\nenactment of this Act, the Secretary of Defense shall carry out\na comprehensive review of the approach of the Department of\nDefense to acquiring commercial products and commercial\nservices and the implementation of the requirements of the\nFederal Acquisition Streamlining Act of 1994 (Public Law 103-\n355) by the Department.\n(2) Review requirements.--The review required by paragraph\n(1) shall include an assessment of each of the following as\nthey relate to the approach of the Department of Defense to\nacquiring commercial products and commercial services:\n(A) The policies, procedures, guidance, and\ninstructions of the Department of Defense.\n(B) The extent to which contracts entered into by\nthe Department of Defense for the acquisition of\ncommercial products or commercial services include\nrequirements or other provisions that should not apply\nto the acquisition of a commercial product or\ncommercial service and the extent to which such\nrequirements or other provisions are included in\nsubcontracts under such contracts.\n(C) Training curricula, educational materials, and\nassociated activities of the Department of Defense\nrelated to acquiring commercial products and commercial\nservices, including such curricula, materials, and\nactivities that pertain to the determination of a\nproduct or service as a commercial product or\ncommercial service and the congressional intent that\nthe definitions of the terms ``commercial product'' and\n``commercial service'' should be applied broadly.\n(D) Audit and oversight policies and practices of\nthe Department of Defense.\n(E) Incentives that discourage the acquisition\nworkforce from acquiring commercial products or\ncommercial services.\n(F) The process by which the Department of Defense\ndevelops and issues regulations related to the\nacquisition of commercial products or commercial\nservices, including delays in rulemaking and the\nresulting delays in the implementation of policies\nintended to improve or streamline the acquisition of\ncommercial products or commercial services.\n(G) Requirements in solicitations or contracts of\nthe Department of Defense requiring the use of military\nspecifications or standards when applicable commercial\nspecifications or standards were available that could\nhave meet the needs of the Department served by such\nmilitary specifications or standards.\n(H) The process by which the Department of Defense\nevaluates past performance, including performance under\nFederal, State, and local government and private\ncontracts (as described in section 15.305(a)(2)(ii) of\nthe Federal Acquisition Regulation), in the acquisition\nof commercial products or commercial services.\n(b) Report.--Not later than 180 days after the enactment of this\nAct, the Secretary of Defense shall submit to the congressional defense\ncommittees a report that--\n(1) describes the findings of the review required by\nsubsection (a)(1);\n(2) describes the corrective actions taken by the Secretary\nto address the issues identified pursuant to such review,\nincluding any findings of noncompliance by the Department of\nDefense with the requirements of the Federal Acquisition\nStreamlining Act of 1994 (Public Law 103-355) or any other\nstatutory or regulatory requirements related to advancing and\nenabling the procurement of commercial products and commercial\nservices; and\n(3) includes any recommendations of the Secretary on\nactions that Congress may take to better enable the Department\nof Defense to take advantage of the benefits of acquiring\ncommercial products and commercial services.\n\nSEC. 303. ADJUSTMENTS TO CERTAIN ACQUISITION THRESHOLDS.\n\n(a) Major Program.--Section 3041 of title 10, United States Code,\nis amended--\n(1) in subsection (c)(1)--\n(A) in subparagraph (A), by striking ``$115,000,000\n(based on fiscal year 1990 constant dollars)'' and\ninserting ``$275,000,000 (based on fiscal year 2024\nconstant dollars)''; and\n(B) in subparagraph (B), by striking ``$540,000,000\n(based on fiscal year 1990 constant dollars)'' and\ninserting ``$1,300,000,000 (based on fiscal year 2024\nconstant dollars)''; and\n(2) in subsection (d)(1), by striking ``$750,000 (based on\nfiscal year 1980 constant dollars)'' and inserting ``$5,000,000\n(based on fiscal year 2024 constant dollars)''.\n(b) Use of Procedures Other Than Competitive Procedures.--Section\n3204(e)(1) of title 10, United States Code, is amended--\n(1) by striking ``$10,000,000'' each place it appears and\ninserting ``$100,000,000'';\n(2) by striking ``$75,000,000'' each place it appears and\ninserting ``$500,000,000''; and\n(3) in subparagraph (B)(i), by striking ``$500,000'' and\ninserting ``$5,000,000''.\n(c) Simplified Procedures for Small Purchases.--Section 3205(a) of\ntitle 10, United States Code, is amended--\n(1) in paragraph (1), by striking ``simplified acquisition\nthreshold'' and inserting ``threshold specified in section\n3571(a) of this title''; and\n(2) in paragraph (2), by striking ``$5,000,000'' and\ninserting ``$50,000,000''.\n(d) Multiyear Contracts.--Section 3501 of title 10, United States\nCode, is amended--\n(1) by striking ``$500,000,000'' each place it appears and\ninserting ``$1,000,000,000'';\n(2) by striking ``$100,000,000'' each place it appears and\ninserting ``$150,000,000''; and\n(3) by striking ``$20,000,000'' each place it appears and\ninserting ``$50,000,000''.\n(e) Simplified Acquisition Threshold.--Section 3571(a) of title 10,\nUnited States Code, is amended--\n(1) by inserting ``(1)'' before ``For purposes of\nacquisitions'';\n(2) by striking ``as specified in section 134 of title 41''\nand inserting ``$10,000,000''; and\n(3) by adding at the end the following new paragraph:\n``(2) In the case of any contract to be awarded and performed, or\npurchase to be made, in support of a contingency operation or a\nhumanitarian or peacekeeping operation, the simplified acquisition\nthreshold means an amount equal to two times the amount specified in\nparagraph (1).''.\n(f) Micro-Purchase Threshold.--Section 3573 of title 10, United\nStates Code, is amended by striking ``$10,000'' and inserting\n``$100,000''.\n(g) Modifications to Submissions of Cost or Pricing Data.--Section\n3702(a) of title 10, United States Code, is amended--\n(1) in paragraph (1)--\n(A) by striking ``June 30, 2018'' each place it\nappears and inserting ``June 30, 2026'';\n(B) in subparagraph (A), by striking ``$2,000,000''\nand inserting ``$10,000,000''; and\n(C) in subparagraph (B), by striking ``$750,000''\nand inserting ``$2,000,000'';\n(2) in paragraph (2), by striking ``$2,000,000'' and\ninserting ``$10,000,000''; and\n(3) in subparagraph (3)(A), by striking ``$2,000,000'' and\ninserting ``$10,000,000''.\n(h) Major Defense Acquisition Programs; Definitions; Exceptions.--\nSection 4201(a)(2) of title 10, United States Code, is amended--\n(1) in subparagraph (A), by striking ``$300,000,000 (based\non fiscal year 1990 constant dollars)'' and inserting\n``$1,000,000,000 (based on fiscal year 2024 constant\ndollars)''; and\n(2) in subparagraph (B), by striking ``$1,800,000,000\n(based on fiscal year 1990 constant dollars)'' and inserting\n``$5,500,000,000 (based on fiscal year 2024 constant\ndollars)''.\n\nSEC. 304. ALTERNATIVE CAPABILITY-BASED PRICING.\n\nChapter 287 of title 10, United States Code, is amended by adding\nat the end the following new section:\n``Sec. 3906. Alternative capability-based pricing\n``(a) In General.--Except as provided by subsection (b), the head\nof an agency may use alternative capability-based analysis for the\nacquisition of a commercial solution to determine whether the price for\na commercial solution is fair and reasonable based on the value to the\nGovernment as determined under such analysis.\n``(b) Exception.--Subsection (a) does not apply with respect to the\nacquisition of a commercial solution under a subcontract.\n``(c) Definitions.--In this section:\n``(1) The term `alternative capability-based analysis'\nmeans an analysis of the value to the Government of a\ncommercial solution that determines such value based on one or\nmore of the following criteria:\n``(A) The suitability of the commercial solution\nfor the particular purpose for which the Government\nwould acquire such commercial solution.\n``(B) The benefits obtained by the Government as a\nresult of improvements in capability, effectiveness,\nefficiency, process, or speed to delivery provided by\nsuch commercial solution.\n``(C) The estimated total cost avoidance resulting\nfrom the acquisition and use of such commercial\nsolution, including the cost avoidance resulting from\nreductions to operations, sustainment, or risks to\nmission by replacing fielded capabilities with such\ncommercial solution.\n``(D) Input from the intended end users of such\ncommercial solution on the potential value of the\nimprovements to capabilities or processes provided by\nsuch commercial solution.\n``(2) The term `commercial solution' means a product or\nservice, including an integrated combination of products,\nservices, or products and services--\n``(A) that is sold, leased, or licensed in the\ncommercial marketplace, or offered for sale, lease, or\nlicense in the commercial marketplace; and\n``(B) the provider of which contemporaneously\noffers such solution or a solution that is similar to\nsuch solution to the general public or public entities,\nincluding State and local governments and foreign\ngovernments, under terms and conditions that are\nsimilar to the terms and conditions under which such\nsolution is offered to the Federal Government.''.\n\nSEC. 305. CLARIFICATION OF CONDITIONS FOR PAYMENTS FOR COMMERCIAL\nPRODUCTS AND COMMERCIAL SERVICES.\n\nSection 3805 of title 10, United States Code, is amended--\n(1) in subsection (d)--\n(A) by striking ``The conditions'' and inserting\n``(1) The conditions''; and\n(B) by adding at the end the following new\nparagraph:\n``(2) For the purposes of section 3803 of this title, a payment for\ncovered services acquired through a commercially utilized acquisition\nstrategy shall not be considered an advance payment made under section\n3801 of this title.''; and\n(2) by adding at the end the following new subsection:\n``(e) Definitions.--In this section:\n``(1) The term `commercially utilized acquisition strategy'\nmeans an acquisition of a service by the Government under terms\nand conditions that--\n``(A) are similar to the terms and conditions under\nwhich such service is available to the public; and\n``(B) provide such service as a consumption-based\nsolution or under a technology subscription model or\nother model based on predetermined pricing for access\nto such service.\n``(2) The term `covered service' means a commercial service\nthat includes access to or use of any combination of hardware,\nequipment, software, labor, or services, including access to\ncommercial satellite data and associated services, that is\nintegrated to provide a capability.''.\n\nTITLE IV--STRENGTHENING THE DEFENSE INDUSTRIAL BASE AND LEVERAGING\nCOMMERCIAL INNOVATION\n\nSEC. 401. DEFENSE INDUSTRIAL RESILIENCE CONSORTIUM.\n\n(a) Establishment.--Not later than 90 days after the date of the\nenactment of this Act, the Secretary of Defense shall establish a\nconsortium (to be known as the ``Defense Industrial Resilience\nConsortium'') to address challenges to and limitations of the\nindustrial base to ensure that the Armed Forces are equipped with the\ncapabilities necessary to effectively respond to national security\nchallenges.\n(b) Membership.--Membership in the consortium established under\nsubsection (a) shall be open to relevant entities and individuals from\nthe Government, industry, and academia with an interest in advanced\nmanufacturing or production technologies, fostering domestic industrial\ninnovation, or enabling rapid, scalable solutions to sustain and\nenhance the availability of essential defense components.\n(c) Purpose.--\n(1) In general.--The consortium established under\nsubsection (a) shall provide a forum for the Government,\nindustry, and academia to collaborate on identifying and\naddressing challenges to and limitations of the industrial base\nin meeting the needs of the Department of Defense.\n(2) Areas of focus.--In identifying and addressing\nchallenges to and limitations of the industrial base, the\nconsortium established under subsection (a) shall focus on--\n(A) eliminating impediments to a resilient and\nrobust industrial base, including--\n(i) policies and procedures that are\nimpeding businesses of all types and sizes from\nworking with the Department of Defense;\n(ii) areas where the Department could\nimprove implementation of the Federal\nAcquisition Streamlining Act of 1994 (Public\nLaw 103-355), including limiting the\napplication of requirements specific to the\nGovernment in the procurement of commercial\nproducts and commercial services, and\nmaximizing the use of commercial standards\nrather than military specifications and\nstandards; and\n(iii) impediments to transitioning\nresearch, development, testing, and evaluation\nprograms funded by military departments and the\nDepartment to relevant acquisition programs of\nrecord;\n(B) identifying and addressing supply chain\nfragility, including--\n(i) preventing or mitigating parts\nobsolescence, and addressing the\nvulnerabilities from reliance on single sources\nfor any material, product, or service while\nreducing the dependencies on nonallied nations;\n(ii) developing long-term industrial base\nstrategies and solutions to ensure the\navailability of mission-critical parts for\nsystems of the Department throughout the life\ncycle of such systems; and\n(iii) bolstering supply chain diversity and\ndeveloping shared awareness of supply chain\nchallenges, risks, and opportunities between\nGovernment and industry;\n(C) expanding domestic manufacturing and industrial\ncapacity, including--\n(i) enabling rapid engagement between\ngovernment, academia, and industry to develop,\ntest, and scale solutions that can revitalize\ndomestic manufacturing capabilities, reduce\nreliance on single sources of supply, and\nstrengthen the defense industrial base;\n(ii) identifying financial incentives and\nbusiness models to enable and support a civil\nreserve manufacturing network that could be\nactivated to meet the needs of the Department\nof Defense;\n(iii) supporting and informing efforts to\nenhance government-owned, government-operated\narsenals and depots with advanced manufacturing\nand other production capabilities to enable\nrapid response across the spectrum of\noperational environments;\n(iv) enabling and enhancing public-private\npartnerships between the organic industrial\nbase, commercial manufacturing, and other\nindustrial entities; and\n(v) anticipate and close gaps in\nmanufacturing capabilities for defense systems\nby fostering the adoption of additive\nmanufacturing, automation, AI-driven\nproduction, and other emerging capabilities to\nmodernize the industrial base and associated\nsupply chains;\n(D) accessing and implementing commercial\napproaches to enabling modern manufacturing\ncapabilities, including--\n(i) adoption of commercial approaches to\ninformation technology, software, the cloud,\ndata management, and artificial intelligence to\nsupport and enable modern manufacturing\ncapabilities; and\n(ii) identifying financial incentives and\nbusiness models to encourage private-sector\ninvestment and expand access to advanced, high-\nquality advanced manufacturing, that uses\nsoftware to digitize manufacturing to the\ngreatest extent possible; and\n(E) development and training of the workforce,\nincluding--\n(i) leveraging industry best practices\ntraining and development of critical skills in\nadvanced manufacturing, including skills\nrequired to manufacture unique components and\nproducts for systems of the Department of\nDefense and to enable capabilities of the\nDepartment;\n(ii) identifying or developing\nopportunities for public-private talent\nexchanges and skills development in areas such\nas advanced manufacturing, supply chain\nmanagement, and supply chain risk management;\nand\n(iii) identify or develop curriculum and\nexperiential learning to support and enable\nadvanced manufacturing, production\ntechnologies, or industrial innovation.\n(d) Consortium Work Products and Recommendations.--Relevant work\nproducts and recommendations developed through consortium activities\nshall be considered by the Secretary of Defense in developing policy\nand allocating resources to ensure that the Armed Forces are equipped\nwith the capabilities necessary to effectively respond to national\nsecurity challenges.\n(e) Use of Other Transaction Authorities.--The consortium\nestablished under subsection (a) shall support the use of other\ntransaction authorities under sections 4021 and 4022 of title 10,\nUnited States Code, and other appropriate acquisition authorities, to\nrapidly prototype and field advanced manufacturing solutions and to\naddress the other challenges to and limitations of the industrial base.\n\nSEC. 402. AMENDMENT TO OTHER TRANSACTION AUTHORITY.\n\n(a) In General.--Section 4022 of title 10, United States Code, is\namended--\n(1) in subsection (a)(2)--\n(A) in subparagraph (A), by striking ``agency\nthat'' and all that follows through ``the use'' and\ninserting ``agency that the use'';\n(B) in subparagraph (B)(i), by striking ``writing\nthat'' and all that follows through ``the use'' and\ninserting ``writing that the use''; and\n(C) in subparagraph (C)--\n(i) by striking ``subsection (f)'' each\nplace it appears and inserting ``subsection\n(e)''; and\n(ii) in clause (i)(I), by striking ``the\nrequirements of subsection (d)'' and all that\nfollows through ``and the'' and inserting\n``the'';\n(2) by striking subsection (d);\n(3) by redesignating subsections (e) through (i) as\nsubsections (d) through (h), respectively; and\n(4) in subsection (f), as so redesignated, by striking\n``subsection (f)'' and inserting ``subsection (e)''.\n(b) Conforming Amendments.--\n(1) National security act of 1947.--Section 102A(n)(6)(C)\nof the National Security Act of 1947 (50 U.S.C. 3024(n)(6)(C))\nis amended--\n(A) by repealing clauses (v) and (vi); and\n(B) in clause (vii)--\n(i) in the matter preceding subclause (I),\nby striking ``4022(f)(2)'' and inserting\n``4022(e)(2)''; and\n(ii) in subclause (V)(cc), by striking\n``4022(f)(5)'' and inserting ``4022(e)(5)''.\n(2) Homeland security act of 2002.--Section 831(d) of the\nHomeland Security Act of 2002 (6 U.S.C. 391(d)) is amended by\nstriking ``4022(e)'' and inserting ``4022(d)''.\n(3) John s. mccain national defense authorization act for\nfiscal year 2019.--Section 873(c)(1) of the John S. McCain\nNational Defense Authorization Act for Fiscal Year 2019 (Public\nLaw 115-232; 10 U.S.C. 4021 note) is amended--\n(A) in subparagraph (A), by striking ``subsection\n(f)'' and inserting ``subsection (e)''; and\n(B) in subparagraph (E), by striking ``or (f)'' and\ninserting ``or (e)''.\n(4) James m. inhofe national defense authorization act for\nfiscal year 2023.--Section 322(h)(2) of the James M. Inhofe\nNational Defense Authorization Act for Fiscal Year 2023 (Public\nLaw 117-263; 10 U.S.C. 2911 note) is amended by striking\n``subsection (f)'' and inserting ``subsection (e)''.\n\nSEC. 403. DATA-AS-A-SERVICE SOLUTIONS FOR WEAPON SYSTEM CONTRACTS.\n\n(a) In General.--Chapter 323 of title 10, United States Code, as\namended by section 105 of this Act, is amended by adding at the end the\nfollowing new section:\n``Sec. 4324. Data-as-a-service solutions for weapon system contracts\n``(a) Negotiations for Data-as-a-Service.--Before entering into a\ncontract for the procurement of a weapon system (or component thereof),\nthe Secretary of Defense shall ensure, to the maximum extent\npracticable, that the negotiations for such contract include\nnegotiations for data-as-a-service solutions to facilitate access to\nthe information described in subsection (b) as necessary for--\n``(1) the performance of depot-level maintenance and repair\nworkload by employees of the Department of Defense in\naccordance with section 2466 of this title; or\n``(2) the maintenance of a core logistics capability in\naccordance with section 2464 of this title.\n``(b) Covered Information.--The information described in subsection\n(a) is technical data or computer software that relates to the weapon\nsystem (or component thereof) to be procured that is--\n``(1) detailed manufacturing or process data relating to\nhow contractors or subcontractors design, develop, produce,\ntest, certify, diagnose, maintain, repair, or otherwise support\nsuch weapon system (or component thereof);\n``(2) digital networks or digital models that contain data\ndescribed in paragraph (1), or virtual replicas of such data;\n``(3) design details, algorithms, processes, flow charts,\nformulas, and related information that describe the design,\norganization, or structure of computer software; or\n``(4) necessary for operation, maintenance, installation,\nor training with respect to such weapon system (or component\nthereof).\n``(c) Methods and Schedule for Access.--(1) With respect to a data-\nas-a-service solution described in subsection (a), access to the\ninformation described in subsection (b) may be made available through\none or more methods, including electronically, in-person, or machine-\nto-machine encryption, as appropriate based on the type, sensitivity,\nor authorized use of such information.\n``(2) The Secretary of Defense shall ensure that the terms of a\ncontract for a data-as-a-service solution described in subsection (a)\nclearly state the requirements, conditions, and schedule for providing\naccess to the information described in subsection (b).\n``(d) Applicability to Commercial Products.--(1) With respect to a\ncontract for a commercial product that is a data-as-a-service solution\ndescribed in subsection (a), the offeror for such commercial product\nshall ensure that the pricing and terms and conditions of access to\ninformation described in subsection (b) for such commercial product is\ncommensurate with commercial practices for similar access.\n``(2) The Secretary of Defense may not require an offeror for a\ncommercial product that is a data-as-a-service solution described in\nsubsection (a) to provide access to information described in subsection\n(b) in a manner that is different from what such offeror customarily\nprovides to a buyer of such commercial product, unless the offeror has\nagreed to provide such access pursuant to a specifically negotiated\nagreement with the Secretary.\n``(e) Rule of Construction.--Nothing in this section shall be\nconstrued as modifying any rights, obligations, or limitations of the\nGovernment, contractor, or subcontractor with respect to rights in\ntechnical data under subchapter I of chapter 275 of this title.\n``(f) Definitions.--In this section:\n``(1) The term `access', with respect to information\ndescribed in subsection (b), means the availability of such\ninformation as a service rather than as specifically delivered\nin the performance of a contract for the procurement of a\nweapon system (or component thereof).\n``(2) The term `data-as-a-service' means a model under\nwhich the Secretary is provided access to the most up-to-date\ninformation described in subsection (b) that relates to a\nweapon system (or component thereof) to be procured by the\nSecretary, including any associated license agreements for such\ninformation.\n``(3) The term `technical data' has the meaning given in\nsection 3013 of this title.''.\n(b) Guidance Required.--Not later than 180 days after the date of\nthe enactment of this Act, the Secretary of Defense shall issue\nguidance to carry out the requirements of section 4324 of title 10,\nUnited States Code, as added by this section.\n(c) Applicability.--Section 4324 of title 10, United States Code,\nas added by this section, shall apply with respect to a contract for\nthe procurement of a weapon system (or component thereof) entered into\non or after the date of the enactment of this Act.\n\nSEC. 404. REQUIREMENTS FOR MODULAR OPEN SYSTEM APPROACH AND\nMODIFICATIONS TO RIGHTS IN TECHNICAL DATA.\n\n(a) Requirements for Modular Open System Approach.--Section 4401 of\ntitle 10, United States Code, is amended to read as follows:\n``Sec. 4401. Requirement for modular open system approach\n``(a) Requirement.--The Secretary of Defense shall ensure that a\ncovered system to be procured is designed and developed, to the maximum\nextent practicable, with a modular open system approach.\n``(b) Assessment To Inform Strategy.--Before designing or\ndeveloping a covered system, the Secretary of Defense shall conduct an\nassessment to identify the open systems objectives to be achieved by\nthe design and development of the covered system. Such assessment shall\nidentify and document how such approach would--\n``(1) support the objectives of the defense acquisition\nsystem established pursuant to section 3102 of this title;\n``(2) align with the preference for the acquisition of\ncommercial products in section 3453 of this title to retain, to\nthe maximum extent practicable, the commercial viability of\nsubsystems and components of the covered system;\n``(3) reduce the complexity and increase the speed by which\nnew technology can be integrated into a covered system to\nenhance miliary effectiveness and responsiveness to emerging\nthreats;\n``(4) enable the use of iterative development cycles and\ndiscontinue or terminate the development of capabilities--\n``(A) that no longer align with approved capability\nrequirements (as defined in section 181 of this title)\nor priorities; or\n``(B) that are experiencing significant cost\ngrowth, performance deficiencies, or delays in\nschedule;\n``(5) promote a robust and responsive defense industrial\nbase, and foster competition amongst offerors of subsystems and\ncomponents of the covered system through the life cycle of the\ncovered system, especially at the module level;\n``(6) reduce schedule delays and development timelines;\n``(7) increase and enable interoperability of a covered\nsystem with the joint force as changes to force design evolve;\nand\n``(8) enable effective life-cycle management and product\nsupport of a covered system--\n``(A) in accordance with the requirements of\nsection 4322 of this title; and\n``(B) to ensure that the covered system will meet\napplicable operational readiness requirements (as\ndefined in such section 4322) and materiel readiness\nobjectives (established under section 118(c) of this\ntitle) in the most cost-effective manner practicable.\n``(c) Architecture Requirements.--(1) In developing an architecture\nfor the procurement of a covered system using a modular open system\napproach, the Secretary shall ensure that the architecture--\n``(A) adequately designates and defines modules, module\ninterfaces, key interfaces, and openness characteristics of the\ncovered system necessary to achieve the open systems objectives\ndescribed in subsection (b);\n``(B) to the extent practicable, is based on--\n``(i) widely accepted, consensus-based standards\nthat are available at no cost or under fair and\nreasonable license terms; or\n``(ii) if such standards are not available or\nsuitable, incremental standards that define\nrelationships between module interfaces and key\ninterfaces; and\n``(C) is designed and developed to accelerate the\nprocurement and integration of commercial products as modules,\nmodule interfaces, and key interfaces.\n``(2) The Secretary shall consider input from private entities as\nearly as possible to inform decisions regarding the level in the\narchitecture at which a modular open system approach will be\nimplemented for a covered system.\n``(3) The architecture described in this subsection shall be\nincluded in any draft and final solicitations for procurement of a\ncovered system.\n``(d) Openness Characteristics.--Consistent with the requirements\nof subchapter I of chapter 275 of this title, the Secretary shall\ninclude in the solicitation for the covered system a description of the\ndesired openness characteristics of the covered system necessary to\nachieve the open systems objectives described in subsection (b),\nincluding the following:\n``(1) The open systems objectives identified as result of\nthe assessment required by subsection (b).\n``(2) A description of the application of specifications or\nstandards for module interfaces to achieve such objectives.\n``(3) A description of the minimum technical data package\nelements necessary to achieve such objectives.\n``(4) The desired license rights in module interfaces or\nkey interfaces based on such objectives, including desired\nlicense rights to enable the replacement of a module or module\ninterface with an alternative or new module or module\ninterface.\n``(e) Applicability to Commercial Products.--In applying the\nrequirements of this section to a covered system that includes a\ncommercial product, the Secretary of Defense shall--\n``(1) implement modular open system approaches in\naccordance with such approaches used in the ordinary course of\nbusiness for such commercial product on the commercial\nmarketplace;\n``(2) for a commercial product that is commercial technical\ndata or commercial software, procure such commercial product\nunder license terms similar to such terms that are customarily\nprovided to the public, unless the Secretary has specifically\nnegotiated different license terms;\n``(3) when applicable, obtain the delivery of commercial\nsoftware development kits with license rights necessary to\nsupport the desired openness characteristics for the covered\nsystem; and\n``(4) to the maximum extent practical, conduct negotiations\nfor desired license rights in accordance with the preference\nfor specially negotiated licenses in section 3774(c) of this\ntitle.\n``(f) Definitions.--In this section:\n``(1) The term `covered system' means a system acquired or\ndeveloped under--\n``(A) an acquisition program of the Department of\nDefense; or\n``(B) a research and development program of the\nDepartment to address a capability requirement or joint\ncapability requirement (as defined in section 181 of\nthis title).\n``(2) The term `incremental standard' means a specification\nfor a module interface or key interface that includes--\n``(A) software-defined syntax and properties that\nspecifically govern how values are validly passed and\nreceived between subsystems and components in machine-\nreadable format;\n``(B) a machine-readable definition of the\nrelationship between the module interface or key\ninterface and existing common standards or interfaces\navailable in Department databases; and\n``(C) documentation with functional descriptions of\nsoftware-defined interfaces, conveying semantic meaning\nof elements of the module interface or key interface.\n``(3) The term `key interface' means a shared boundary\nbetween any system, subsystem of a covered system, or set of\nmodules, defined by various physical, logical, functional\ncharacteristics, such as electrical, mechanical, fluidic,\noptical, radio frequency, data, networking, or software.\n``(4) The term `modular open system approach' means the\napplication of a strategy that leverages an architecture that\nenables modules to be incrementally added, removed, or replaced\nthroughout the life cycle of the covered system to achieve a\nset of objectives.\n``(5) The term `module' means a self-contained functional\nhardware or software unit--\n``(A) that can be developed, tested, and deployed\nindependently of a module interface or key interface;\nand\n``(B) that can simultaneously interact with another\nself-contained functional hardware or software unit\ndescribed in subparagraph (A) through a module\ninterface or key interface.\n``(6) The term `module interface' means a shared boundary\nbetween modules, defined by physical, logical, and functional\ncharacteristics, such as electrical, mechanical, fluidic,\noptical, radio frequency, data, networking, or software.\n``(7) The term `software development kit' means a\ncollection of software tools and programs such as libraries,\napplication programming interfaces, integrated development\nenvironments, testing tools, or documentation used to create\napplications that are appropriate for a specific software\nplatform.''.\n(b) Guidance.--Not later than 180 days after the date of the\nenactment of this Act, the Secretary of Defense shall issue guidance to\ncarry out the requirements of section 4401 of title 10, United States\nCode, as amended by this section.\n(c) Applicability.--The requirements of section 4401 of title 10,\nUnited States Code, as amended by this section, shall apply with\nrespect to a contract entered into on or after the date of the\nenactment of this Act.\n(d) Modification to Rights in Technical Data.--\n(1) Rights in technical data.--Section 3771 of title 10,\nUnited States Code, is amended--\n(A) in subsection (a)--\n(i) in paragraph (2)(A), by striking `` or\ncopyrights'' and inserting ``, copyrights,\ntrade secrets,''; and\n(ii) by adding at the end the following new\nparagraph:\n``(3) Enforcement of certain rights.--Regulations\nprescribed under paragraph (1) may not affect or limit any\nright described in paragraph (2)(A) or the ability of a\ncontractor or subcontractor to enforce such a right against a\nthird party that has not otherwise obtained a license for such\na right from the United States or from the contractor or\nsubcontractor.''; and\n(B) in subsection (b)--\n(i) in paragraph (2), by striking\n``paragraphs (3), (4), and (7),'' and inserting\n``paragraphs (3) and (4),'';\n(ii) by amending paragraph (3) to read as\nfollows:\n``(3) Inapplicability of paragraph (2).--Unless otherwise\nnegotiated, paragraph (2) does not apply to technical data\nthat--\n``(A) constitutes a correction or change to data\nfurnished by the United States; or\n``(B) is otherwise publicly available or has been\nreleased or disclosed by the contractor or\nsubcontractor without restriction on further release or\ndisclosure.'';\n(iii) by amending paragraph (4) to read as\nfollows:\n``(4) Exceptions to paragraph (2).--(A) Notwithstanding\nparagraph (2), unless otherwise negotiated, the United States\nshall have government purpose rights, in perpetuity, in\ntechnical data that--\n``(i) relates to form, fit, or function of an item\nor process; or\n``(ii) is necessary for operation, maintenance,\ninstallation, or training (other than detailed\nmanufacturing or process data) of an item or process.\n``(B) Notwithstanding paragraph (2), the United States may\nrelease or disclose technical data to persons outside the\nGovernment, or permit the use of technical data by such\npersons, if such release, disclosure, or use--\n``(i) is necessary for emergency repair and\noverhaul;\n``(ii) is a release or disclosure of technical data\n(other than detailed manufacturing or process data) to,\nor use of such data by, a foreign government, where\nsuch release or disclosure is in the interest of the\nUnited States and is required for evaluation or\ninformational purposes;\n``(iii) is made subject to a prohibition that the\nperson to whom the data are released or disclosed may\nnot further release, disclose, or use such data; and\n``(iv) the contractor or subcontractor asserting\nthe restriction is notified of such release,\ndisclosure, or use.'';\n(iv) in paragraph (6)--\n(I) in the paragraph heading, by\nstriking ``Interfaces'' and inserting\n``Module interfaces of an item'';\n(II) by inserting ``, in\nperpetuity,'' after ``government\npurpose rights''; and\n(III) by striking ``an interface\nbetween an item or process and other\nitems or processes'' and inserting ``a\nmodule interface of an item''; and\n(v) in paragraph (7)--\n(I) in the paragraph heading, by\nstriking ``Modular system interfaces''\nand inserting ``Key interfaces of an\nitem'';\n(II) in subparagraph (A)--\n(aa) by striking\n``paragraphs (2) and (5)'' and\ninserting ``paragraph (5) and\nexcept as otherwise provided by\nsubsection (e) of section 4401\nof this title,'';\n(bb) by inserting ``, in\nperpetuity,'' after\n``government purpose rights'';\nand\n(cc) by striking ``modular\nsystem interface'' and\ninserting ``key interface of an\nitem'';\n(III) in subparagraph (B), by\nstriking ``modular system interface''\nand inserting ``a key interface''; and\n(IV) in subparagraph (C), by\nstriking ``modular system interface''\nand inserting ``key interface of an\nitem''.\n(2) Definitions.--Section 3775(b) of title 10, United\nStates Code, is amended to read as follows:\n``(b) Additional Definitions.--In this subchapter, the terms `key\ninterface', `modular open system approach', and `module interface' have\nthe meanings given, respectively, in section 4401 of this title.''.\n(e) Conforming Amendments.--\n(1) Section 3791(c)(1) of title 10, United States Code, is\namended--\n(A) in subparagraph (A), by striking ``section\n4401(b) of this title'' and inserting ``section 4401 of\nthis title''; and\n(B) in subparagraph (D)(iv), by striking ``modular\nsystem interfaces (as defined in section 4401(b) of\nthis title)'' and inserting ``module interfaces (as\ndefined in section 4401(f) of this title)''.\n(2) Section 4402 of title 10, United States Code, is\nrepealed.\n(3) Section 4403 of title 10, United States Code, is\nrepealed.\n(4) Section 4425 of title 10, United States Code, is\namended to read as follows:\n``Sec. 4425. Definitions\n``In this subchapter:\n``(1) The term `major system platform' means the highest\nlevel structure of a major weapon system that is not physically\nmounted or installed onto a higher level structure and on which\na major system component can be physically mounted or\ninstalled.\n``(2) The term `weapon system component'--\n``(A) means a high level subsystem or assembly,\nincluding hardware, software, or an integrated assembly\nof both, that can be mounted or installed on a major\nsystem platform through a key system interface (as\ndefined in section 4401(f) of this title); and\n``(B) includes a subsystem or assembly that is\nlikely to have additional capability requirements, is\nlikely to change because of evolving technology or\nthreat, is needed for interoperability, facilitates\nincremental deployment of capabilities, or is expected\nto be replaced by another subsystem or assembly\ndescribed in subparagraph (A).''.\n(5) Section 804 of the National Defense Authorization Act\nfor Fiscal Year 2021 (10 U.S.C. 4401 note) is repealed.\n\nSEC. 405. QUALIFICATION, ACCEPTANCE, AND SUPPLY CHAIN MANAGEMENT OF\nPRODUCTS MANUFACTURED USING ADVANCED MANUFACTURING.\n\n(a) In General.--Not later than 180 days after the date of the\nenactment of this Act, the Secretary of Defense shall establish in the\nDefense Industrial Resilience Consortium established under section 401\nof this Act a working group to develop recommendations for improving\nthe policies and procedures of the Department of Defense for the\nqualification, acceptance, and management of the supply chains of\nproducts manufactured using advanced manufacturing.\n(b) Membership.--The membership of the working group shall include\nrepresentatives from government, industry, and academia with expertise\nin advanced manufacturing, engineering, the procedures of the\nDepartment of Defense for qualifying and accepting products, supply\nchain management, or commercial best practices and business models for\nadvanced manufacturing.\n(c) Responsibilities.--The working group shall--\n(1) review the policies and procedures of the Department of\nDefense to identity policies and procedures for the\nqualification, acceptance, and management of the supply chains\nof products that are insufficient for or not applicable to\nproducts manufactured using advanced manufacturing;\n(2) identify any changes to the policies and procedures of\nthe Department required for the Department to benefit fully\nfrom access to and use of products manufactured using advanced\nmanufacturing; and\n(3) develop recommendations for--\n(A) technical guidance with respect to the\nqualification, acceptance, and management of the supply\nchains of products manufactured using advanced\nmanufacturing;\n(B) policies and procedures for the qualification,\nacceptance, and management of the supply chains of such\nproducts;\n(C) changes to any other policies and procedures of\nthe Department identified under paragraph (2); and\n(D) training to enhance the knowledge and\nexperience of the workforce of the Department of\nDefense with advanced manufacturing, including the\nbenefits, limitations, and commercial best practices\nand business models for designing, developing, and\nusing products manufactured using advanced\nmanufacturing.\n(d) Report.--Not later than 1 year after the date of enactment, the\nSecretary of Defense shall submit to Congress--\n(1) a report on the recommendations developed by the\nworking group under subsection (c)(3) and the actions taken by\nthe Secretary to better enable to the Department of Defense to\naccess and use products manufactured using advanced\nmanufacturing; and\n(2) a recommendation whether to continue or terminate the\nworking group.\n(e) Working Group Defined.--In this section, the term ``working\ngroup'' means the working group established under subsection (a).\n\nSEC. 406. AMENDMENTS TO THE PROCUREMENT TECHNICAL ASSISTANCE PROGRAM.\n\nChapter 388 of title 10, United States Code, is amended--\n(1) in section 4952--\n(A) by redesignating paragraphs (1) and (2) as\nparagraphs (2) and (3);\n(B) by inserting before paragraph (2), as so\nredesignated, the following new paragraph:\n``(1) to support the growth and resiliency of the\nindustrial base by accelerating innovation, fostering ingenuity\nof business entities, and establishing resilient supply\nchains;'';\n(C) in paragraph (2), as so redesignated, by\nstriking ``and'' at the end;\n(D) in paragraph (3), as so redesignated, by\nstriking the period at the end and inserting ``; and'';\nand\n(E) by inserting after paragraph (3) the following\nnew paragraph:\n``(4) to mitigate costs of entry for business entities that\nimprove the technology capabilities of the Department of\nDefense.''; and\n(2) in section 4961--\n(A) in paragraph (1), by striking ``and'' at the\nend;\n(B) in paragraph (2)(B), by striking the period at\nthe end and inserting ``; and''; and\n(C) by adding at the end the following new\nparagraph:\n``(3) an amount determined appropriate by the Secretary to\nestablish one or more centers of excellence to provide to\nindividuals or eligible entities that provide procurement\ntechnical assistance pursuant to this chapter training\nnecessary to fulfill the purpose of the program under section\n4952 of this title.''.\n\nSEC. 407. REPORT ON SURGE CAPACITY IN THE DEFENSE INDUSTRIAL BASE.\n\n(a) Report Required.--Not later than March 1, 2026, the Assistant\nSecretary of Defense for Industrial Base Policy and the Director of\nDefense Pricing, Contracting, and Acquisition Policy shall jointly\nsubmit to the congressional defense committees a report on efforts to\nidentify and address regulations or policies that discourage or prevent\ncontractors of the Department of Defense from maintaining or investing\nin surge capacity.\n(b) Elements.--The report required subsection (a) shall include the\nfollowing:\n(1) A discussion of any efforts by United States DOGE\nService (commonly referred to as the ``Department of Government\nEfficiency'' or ``DOGE''), acting in coordination with the\nOffice of the Secretary of Defense, to review and address the\nbarriers described in subsection (a)(1).\n(2) An identification of policies that incentivize\ncontractors to reduce or eliminate surge capacity, including\nsection 31.205-17 of the Federal Acquisition Regulation\n(relating to idle facilities and idle capacity costs).\n(3) Any steps taken by the Secretary of Defense to address\nregulatory barriers disincentivizing surge capacity within the\ndefense industrial base as part of the implementation of\nExecutive Order 14265 titled ``Modernizing Defense Acquisitions\nand Spurring Innovation in the Defense Industrial Base'' (90\nFed. Reg. 15621; April 15, 2025).\n(c) Surge Capacity Defined.--In this section, the term ``surge\ncapacity'' means the ability of contractors in the defense industrial\nbase to rapidly increase production capacity to meet increased demand\nfor defense articles and defense services (as such terms are defined,\nrespectively, in section 301 of title 10, United States Code).\n\nSEC. 408. BRIDGING OPERATIONAL OBJECTIVES AND SUPPORT FOR TRANSITION\nPROGRAM.\n\n(a) Bridging Operational Objectives and Support for Transition\nProgram.--\n(1) Establishment.--In meeting the responsibilities of the\nDefense Innovation Unit under section 4127(d) of title 10,\nUnited States Code, the Director of the Defense Innovation Unit\nshall establish a program (to be known as the ``Bridging\nOperational Objectives and Support for Transition program'') to\naccelerate the adoption or integration of commercial\ntechnologies into programs of record of the Department of\nDefense.\n(2) Program execution.--Not later than 90 days after the\ndate of the enactment of this subsection, the Director shall\nissue guidance on the BOOST program, including guidance to do\nthe following:\n(A) Enable a customer seeking a technology solution\nfor a challenge or requirement in a program of record\nof the Department of Defense to request assistance\nunder the BOOST program with identifying and adopting\nor integrating such a solution into such program.\n(B) Establish requirements for the Defense\nInnovation Unit to--\n(i) conduct a review of commercial\ntechnologies pursuant to a request described in\nsubparagraph (A) with respect to a challenge or\nrequirement of a program of record of the\nDepartment to identify commercial technology\nthat may address such challenge or requirement;\n(ii) provide to the customer that made such\nrequest the findings of such review, including\nany commercial technologies so identified; and\n(iii) at the request of such customer after\nproviding such findings to such customer,\nconduct development, experimentation, or\nintegration activities in coordination with\nsuch customer to support or enable the adoption\nor integration of any commercial technology so\nidentified into such program of record.\n(C) Establish criteria for terminating assistance\nunder the BOOST program for a customer or with respect\nto a commercial technology.\n(3) Support to other programs.--The Director shall ensure\nthe BOOST program works with and in support of--\n(A) the program established under section 4061(a)\nof title 10, United States Code;\n(B) other organizations of the Department of\nDefense responsible for accelerating the adoption and\nintegration of technology in systems or programs of the\nDepartment;\n(C) the Small Business Innovation Research Program;\n(D) the Small Business Technology Transfer Program;\nand\n(E) the Joint Rapid Acquisition Cell (as described\nin the Department of Defense Directive 5000.71 titled\n``Rapid Fulfillment of Combatant Commander Urgent\nOperational Needs'' (August 24, 2012)).\n(4) Funding.--Subject to the availability of\nappropriations, amounts authorized to be appropriated the\nDefense Innovation Unit for research, development, test, and\nevaluation for a fiscal year may be used for such fiscal year\nto carry out the BOOST program.\n(5) Sunset.--The authorities and requirements under this\nsubsection shall expire on December 31, 2030.\n(b) Reporting.--Not later than two years after the date of the\nenactment of this Act, the Secretary of Defense, in coordination with\nthe Under Secretary of Defense for Acquisition and Sustainment and the\nDirector, shall submit to the congressional defense committees a report\non the effectiveness of the BOOST program in accelerating the adoption\nor integration of commercial technologies into programs of record of\nthe Department of Defense, including--\n(1) a summary description of customers and technologies\nadopted or integrated into such programs of record based on\nassistance provided under the BOOST program;\n(2) recommendations of the Secretary to improve the BOOST\nprogram; and\n(3) a recommendation whether to continue or terminate the\nBOOST program.\n(c) Definitions.--In this section:\n(1) The term ``BOOST program'' means the program\nestablished under subsection (a)(1).\n(2) The term ``customer'' means a program manager or\nprogram executive officer of the Department of Defense that has\nprimary responsibility for fielding the system or systems\nacquired.\n(3) The term ``Director'' means the Director of the Defense\nInnovation Unit.\n(4) The term ``program executive officer'' has the meaning\ngiven such term in section 1737(a) of title 10, United States\nCode.\n(5) The terms ``Small Business Innovation Research\nProgram'' and ``Small Business Technology Transfer Program''\nhave the meanings given such terms, respectively, in section\n9(e) of the Small Business Act (15 U.S.C. 638(e)).\n\nTITLE V--DEVELOPING A MISSION-ORIENTED DEFENSE ACQUISITION WORKFORCE\n\nSEC. 501. REPORT ON STRENGTHENING THE DEFENSE ACQUISITION UNIVERSITY.\n\n(a) Assessment Required.--The Secretary of Defense, acting through\nthe Director of the Acquisition Innovation Research Center, shall\nconduct a comprehensive assessment of the Defense Acquisition\nUniversity (in this section referred to as ``DAU'') to strengthen the\nability of the DAU to train and develop members of the acquisition\nworkforce to meet future needs of the Department of Defense. The\nassessment shall include the following:\n(1) An evaluation of the mission of the DAU and the\nalignment of such mission with the objectives of the defense\nacquisition system established pursuant to section 3102 of\ntitle 10, United States Code (as added by section 101 of this\nAct).\n(2) An evaluation of the effectiveness of training and\ndevelopment provided by DAU to members of the acquisition\nworkforce to enable such members to effectively implement the\nobjectives of the defense acquisition system.\n(b) Elements.--The assessment in paragraph (1) shall evaluate the\nfollowing:\n(1) The organization and structure of DAU.\n(2) The curriculum and educational offerings of DAU.\n(3) The composition of the staff and faculty of DAU,\nincluding an assessment of the diversity of skills, abilities,\nand professional backgrounds of such staff and faculty.\n(4) The sufficiency of resource and funding mechanisms\nsupporting DAU operations.\n(5) The extent to which DAU uses external experts and\nacademic institutions to inform and enhance its programs.\n(c) Recommendations.--The Director of the Acquisition Innovation\nResearch Center shall use the assessment required under this section\nand the objectives of the defense acquisition system to provide to the\nSecretary of Defense recommendations to strengthen the ability of the\nDAU to train and develop members of the acquisition workforce to meet\nfuture needs of the Department of Defense.\n(d) Report to Congress.--Not later than one year after the date of\nthe enactment of this Act, the Secretary of Defense shall submit to the\ncongressional defense committees a report containing--\n(1) the findings of the assessment conducted under\nsubsection (a) and the recommendations provided under\nsubsection (c); and\n(2) any actions necessary to ensure that DAU fulfills its\nmission and provides training and development to members of the\nacquisition workforce that aligns with the objectives of the\ndefense acquisition system.\n(e) Definitions.--In this section:\n(1) The term ``Acquisition Innovation Research Center''\nmeans the acquisition research organization within a civilian\ncollege or university that is described under section 4142(a)\nof title 10, United States Code.\n(2) The term ``acquisition workforce'' has the meaning\ngiven in section 101 of title 10, United States Code.\n\nSEC. 502. COMPTROLLER GENERAL REVIEW OF THE MANAGEMENT, TRAINING, AND\nDEVELOPMENT OF THE ACQUISITION WORKFORCE.\n\n(a) In General.--The Comptroller General of the United States shall\nconduct a review of the management, training, and development of the\nacquisition workforce to enable the acquisition workforce to\nexpeditiously provide the Armed Forces with the capabilities necessary\nto operate effectively, to address evolving threats, and to maintain\nthe military advantage of the United States in the most cost-effective\nmanner practicable.\n(b) Review Contents.--In conducting the review required by\nsubsection (a), the Comptroller General shall evaluate the following:\n(1) The current organization and staffing of the\nacquisition workforce, including the total number of positions\nin the acquisition workforce, a list of such positions\ndisaggregated by the skills and experience required, and the\nnumber of such positions that are vacant or are filled by an\nindividual whose skills and experience do not meet the required\nskills and experience for such position.\n(2) The sufficiency of the processes and authorities of the\nDepartment of Defense for recruiting and retaining the\nacquisition workforce, and the use of such authorities to\nmaintain an acquisition workforce that is optimized to meet\nmission requirements.\n(3) Trends in acquisition workforce hiring and retention\nover the preceding five years.\n(4) The impediments to members of the acquisition workforce\nreceiving training and education, including any lack of\nfunding, unavailability of required or desired training, and\nexcessive workload demands that preclude such members from\nbeing able to attend such training.\n(c) Report.--Not later than April 1, 2026, the Comptroller General\nshall submit to the congressional defense committees a report on the\nfindings of the review required by subsection (a), including any\nrecommendations to improve the management, training, and development of\nthe acquisition workforce.\n(d) Acquisition Workforce Defined.--In this section, the term\n``acquisition workforce'' has the meaning given such term in section\n101(a) of title 10, United States Code.\n\nSEC. 503. COMPTROLLER GENERAL REVIEW OF MATTERS RELATING TO INDIVIDUALS\nASSIGNED TO A CRITICAL ACQUISITION POSITION.\n\n(a) Review Required.--The Comptroller General of the United States\nshall--\n(1) conduct a review of the education, training, and career\ndevelopment programs offered by the Secretary of Defense for\nmembers of the acquisition workforce; and\n(2) conduct an assessment of the efficacy of the career\ndevelopment policies established by section 1734 of title 10,\nUnited States Code.\n(b) Matters for Review.--In conducting the review required by this\nsection, the Comptroller General shall--\n(1) review the compliance of the Secretary with the\nrequirements of section 1734 of title 10, United States Code;\n(2) conduct an assessment of the efficacy of the career\ndevelopment policies and minimum periods of assignment\nestablished by such section 1734 in--\n(A) improving the ability of the acquisition\nworkforce to expeditiously provide the Armed Forces\nwith the capabilities necessary to operate effectively,\nto address evolving threats, and to maintain the\nmilitary advantage of the United States in the most\ncost-effective manner practicable;\n(B) enhancing the knowledge and experience of the\nacquisition workforce;\n(C) enabling competitive career progression of\nmembers of the acquisition workforce compared to other\nmembers of the civilian and military workforce of the\nDepartment of Defense that are not subject to the\nminimum periods of assignment established by such\nsection 1734; and\n(D) the retention rates of members of the\nacquisition workforce assigned to a critical\nacquisition position, particularly key leadership\npositions (as defined by the Under Secretary of Defense\nfor Acquisition and Sustainment), compared with the\nretention rates for other members of the civilian and\nmilitary workforce of the Department of Defense that\nare not subject to the minimum periods of assignment\nestablished by such section 1734; and\n(3) conduct an assessment of any benefits, including\nenhanced accountability in leadership and decisionmaking by\nindividuals in key leadership positions, of a minimum period of\nassignment of at least four years to a critical acquisition\nposition.\n(c) Report Required.--Not later than July 1, 2026, the Comptroller\nGeneral shall submit to the congressional defense committees\nrecommendations on--\n(1) improvements to education, training, and career\ndevelopment programs offered by the Secretary of Defense for\nmembers of the acquisition workforce; and\n(2) minimum periods of assignment for an individual\nassigned as a program executive officer.\n<all>","changes":[{"id":1217,"doc_id":11291,"v_from":13650,"v_to":17070,"detected_at":"2026-10-16 03:16:45","added":980,"removed":43032,"summary":"--- \n+++ \n+SUMMARY\n+Streamlining Procurement for Effective Execution and Delivery and National Defense Authorization Act for Fiscal Year 2026\n+This bill sets forth policies and authorities for FY2026 for Department of Defense (DOD) programs and activities, military construction, and the national security programs of the Department of Energy and the Maritime Administration. It also authorizes appropriations for the Defense Nuclear Facilities Safety Board and the Naval Petroleum Reserves, and modifies the defense acquisition system to expedite delivery of capabilities to the Armed Forces.\n+Among other elements, the bill\n+authorizes the acquisition or modification of various military items (e.g., aircraft) and sets policy for certain procurement programs;\n+authorizes research, development, test, and evaluation and sets policy for such activities;\n+sets active component and reserve component end-strength levels;\n+sets policy regarding various aspects of military health care and military compensation;\n+sets policy regarding acquisitions and acquisition management, including contracting authorities and small businesses;\n+sets policy for various matters related to DOD interactions with foreign nations, including matters concerning Israel;\n+sets policy for various matters related to DOD cyber activities, cyber workforce and training, cybersecurity, and artificial intelligence matters; and\n+authorizes the activities of the National Nuclear Security Administration, defense environmental cleanup, nuclear energy, and other defense activities.\n+For additional information on the National Defense Authorization Act (NDAA) see\n+CRS In Focus IF10516, Defense Primer: Navigating the NDAA , and\n+CRS In Focus IF10515, Defense Primer: The NDAA Process .\n+\n-[H.R. 3838 Engrossed in House (EH)]\n+[H.R. 3838 Introduced in House (IH)]\n-\n-_______________________________________________________________________\n-\n-AN ACT\n+_______________________________________________________________________\n+\n+IN THE HOUSE OF REPRESENTATIVES\n+\n+June 9, 2025\n+\n+Mr. Rogers of Alabama (for himself and Mr. Smith of Washington)\n+introduced the following bill; which was referred to the Committee on\n+Armed Services\n+\n+_______________________________________________________________________\n+\n+A BILL\n+\n+To authorize appropriations for fiscal year 2026 for military\n+activities of the Department of Defense, for military construction, and\n+for defense activities of the Department of Energy, to prescribe\n+military personnel strengths for such fiscal year, and for other\n+purposes.\n+\n-SECTION 1. SHORT TITLE.\n-\n-(a) In General.--This Act may be cited as the ``Streamlining\n-Procurement for Effective Execution and Delivery and National Defense\n-Authorization Act for Fiscal Year 2026''.\n-(b) Reference.--Any reference in this or any other Act to the\n-``National Defense Authorization Act for Fiscal Year 2026'' shall be\n-deemed to be a reference to the ``Streamlining Procurement for\n-Effective Execution and Delivery and National Defense Authorization Act\n-for Fiscal Year 2026''.\n-"}],"passport":{"data":{"act":{"jurisdiction":"США","title_official":"Streamlining Procurement for Effective Execution and Delivery Act of 2025","title_short":"SPEED Act","level":"закон","date_adopted":"июнь 9, 2025 года","date_in_force":"","date_version":"","phased":"","status":"действует","sunset":"","regulator":"Министерство обороны США","related":""},"goal":{"problem":"повышение эффективности и оперативности приобретения вооружений и военной техники для обеспечения военных операций.","goal":"оптимизация процесса закупок вооружений и военной техники, обеспечение своевременной поставки необходимых средств и поддержание военного превосходства США.","targets":"отсутствуют","scope":"военные ведомства США","exclusions":"отсутствуют"},"subjects_note":{"protected":"отсутствуют"},"subjects":[{"role":"поставщик, платформа, оператор, потребитель, госорган","who":"– программа управления закупками (Program Executive Officer)\n– продуктовый менеджер поддержки (Product Support Manager)\n– госорганы (Министерство обороны, Комитет по делам вооруженных сил)","criteria":"наличие полномочий и обязанностей в рамках реализации закона","count":""}],"norms":[{"address":"ст. 201 ч. 1; ст. 202 ч. 1; ст. 203 ч. 1; ст. 204 ч. 1; ст. 205 ч. 1; ст. 206 ч. 1","addressee":"госорган","essence":"1. Совместный комитет по требованиям должен регулярно оценивать глобальные тенденции, угрозы и проблемы.\n2. Совместный комитет по требованиям и интеграции должен предоставлять рекомендации по решению проблем и угроз.\nТип предписание: обязанность","type":"обязанность","mechanism":"организационный контроль","cost_channel":"административный","cost_kind":"регулярные","trigger":"постоянно","sanction":"отсутствует","refs":"","form":"цифровая","in_force":"","ru_analog":"требует проверки"}]},"made_by":"GigaChat-2","made_at":"2026-10-16 06:04:56","edited_at":null,"edited_by":null}}