HR5457-119

Passed House

Strengthening Agency Management and Oversight of Software Assets Act

119th Congress Introduced Sep 18, 2025

Summary

What This Bill Does

The Strengthening Agency Management and Oversight of Software Assets Act requires each covered agency Chief Information Officer, in consultation with the Chief Financial Officer, Chief Acquisition Officer, Chief Data Officer, and General Counsel, to complete a comprehensive software assessment within 18 months. The assessment must cover the agency's software inventory, software entitlements, contracts, largest entitlements by provider and category, software built or used by the agency, shared services, cloud fees and other extra costs, unused or duplicative software, interoperability, cost-volume-type categories, restrictive entitlement provisions, total lifecycle costs, and compliance with license-management policies. Agency heads may hire support contractors, but not contractors with organizational conflicts of interest.

Using that assessment, each agency CIO must create a modernization plan to consolidate software entitlements, reduce unnecessary cost, eliminate excess licenses, improve performance, automate license management, use discovery tools, train employees on software acquisition and development, negotiate restrictive contract terms, and restrict bureaus or components from acquiring or using software without CIO approval. OMB and GSA must coordinate common definitions, terms, and conditions for software asset management. GAO must report within three years on government-wide trends, interagency comparisons, OMB harmonization work, compliance with support-contractor restrictions, and agency plans. The bill authorizes no additional funds.

Who Benefits and How

Federal taxpayers, agency CIO offices, software asset management tool vendors, IT asset management consultants, enterprise software vendors, open-source software providers, OMB digital-management staff, GSA procurement officials, and GAO oversight teams benefit because agencies must identify unused licenses, duplicative entitlements, hidden cloud costs, restrictive terms, and consolidation opportunities before buying or renewing software.

Who Bears the Burden and How

Federal agency CIOs, agency IT departments, Chief Financial Officers, Chief Acquisition Officers, Chief Data Officers, agency General Counsel offices, bureau program offices, software procurement staff, support contractors, and small software vendors with agency-specific deals face inventory, reporting, training, contract-review, approval, consolidation, and budget constraints. Agencies must do the work with existing funds, and bureaus lose autonomy to buy or build software outside CIO-controlled procedures.

Key Provisions

  • Requires each covered agency CIO to complete a comprehensive software assessment within 18 months.
  • Requires assessment of entitlements, contracts, cloud fees, unused software, duplicative software, interoperability, restrictive terms, lifecycle costs, and license-policy compliance.
  • Authorizes support contracts but bars contractors with organizational conflicts of interest.
  • Requires agency modernization plans to consolidate entitlements, automate license management, train staff, reduce costs, and restrict component-level acquisitions without CIO approval.
  • Directs OMB and GSA to harmonize common software-management definitions, terms, and conditions.
  • Requires GAO to report within three years on agency software asset management trends and compliance.
  • Bars additional appropriations for implementation.

Evidence Chain:

This summary is generated from the full bill text using AI analysis. Expand "Detailed Analysis" below for identified beneficiaries/burden bearers with clause-level evidence links.

At a Glance

What This Bill Does

Requires agency CIOs to inventory and assess software entitlements within 18 months, build modernization plans to consolidate licenses and control software acquisition, directs OMB and GSA to harmonize software-management terms, requires GAO review, and authorizes no new funds.

Key Policy Areas

Federal IT, Government Procurement, Software, Government Oversight

Primary Purpose

Requires agency CIOs to inventory and assess software entitlements within 18 months, build modernization plans to consolidate licenses and control software acquisition, directs OMB and GSA to harmonize software-management terms, requires GAO review, and authorizes no new funds.

Policy Domains

Federal IT Government Procurement Software Government Oversight

Substantive provisions

Identified Gains
  • Federal taxpayers
  • Agency CIO offices
  • Software asset management tool vendors
  • IT asset management consultants
  • Enterprise software vendors
  • Open-source software providers
  • OMB digital-management staff
  • GSA procurement officials
  • GAO oversight teams
Model: codex-gpt-5 | Version: bill_summary_v2 | Source: rfs
Federal taxpayers: , , , , , , , , ,
Agency CIO offices: , , , , , , , , ,
GAO oversight teams: , , , , , , , , ,
GSA procurement officials: , , , , , , , , ,
Enterprise software vendors: , , , , , , , , ,
OMB digital-management staff: , , , , , , , , ,
Open-source software providers: , , , , , , , , ,
IT asset management consultants: , , , , , , , , ,
Software asset management tool vendors: , , , , , , , , ,
Identified Costs
  • Federal agency CIOs
  • Agency IT departments
  • Chief Financial Officers
  • Chief Acquisition Officers
  • Chief Data Officers
  • Agency General Counsel offices
  • Bureau program offices
  • Software procurement staff
  • Support contractors
  • Small software vendors
Model: codex-gpt-5 | Version: bill_summary_v2 | Source: rfs
Chief Data Officers: , , , , , , , , ,
Federal agency CIOs: , , , , , , , , ,
Support contractors: , , , , , , , , ,
Agency IT departments: , , , , , , , , ,
Bureau program offices: , , , , , , , , ,
Small software vendors: , , , , , , , , ,
Chief Financial Officers: , , , , , , , , ,
Chief Acquisition Officers: , , , , , , , , ,
Software procurement staff: , , , , , , , , ,
Agency General Counsel offices: , , , , , , , , ,

Legislative Progress

Passed House
Introduced Committee Passed
Dec 16, 2025

Received; read twice and referred to the Committee on Homeland …

Dec 16, 2025

Received in the Senate and Read twice and referred to …

Dec 16, 2025 (inferred)

Passed House (inferred from eh version)

Dec 15, 2025

Passed/agreed to in House: On motion to suspend the rules …

Dec 15, 2025

DEBATE - The House proceeded with forty minutes of debate …

Dec 15, 2025

Mr. Timmons moved to suspend the rules and pass the …

Dec 15, 2025

Considered under suspension of the rules. (consideration: CR H5862-5864)

Dec 15, 2025

Motion to reconsider laid on the table Agreed to without …

Dec 15, 2025

On motion to suspend the rules and pass the bill, …

Dec 2, 2025

Ordered to be Reported (Amended) by the Yeas and Nays: …

Stakeholder Effects

cui bono?

How this legislation distributes effects. Mention counts reflect frequency, not effect magnitude.

Government
26 mentions across 15 clauses
-23 negative ?3 uncertain

Agency bureaus and program offices (software acquisition authority), Federal agencies (budget constraint), Federal agencies (definition scope)

Technology
11 mentions across 6 clauses
+8 positive -3 negative

Enterprise software vendors offering consolidated licensing, Open-source software providers, Smaller software vendors with agency-specific deals

Positive-direction: Enterprise software vendors offering consolidated licensing, Open-source software providers, Software asset management tool vendors

Negative-direction: Smaller software vendors with agency-specific deals, Software vendors with restrictive licensing terms

Professional Services
3 mentions across 3 clauses
+3 positive

IT asset management consultants and contractors

6/6
sections analyzed
Full impact breakdown

Bill Structure & Actor Mappings

Who is "The Secretary" in each section?

Domains
Federal IT Government Procurement Software Government Oversight
Actor Mappings
"cio"
→ Chief Information Officer
"gao"
→ Government Accountability Office
"gsa"
→ General Services Administration
"omb"
→ Office of Management and Budget

We use a combination of our own taxonomy and classification in addition to large language models to assess meaning and potential beneficiaries. High confidence means strong textual evidence. Always verify with the original bill text.

Learn more about our methodology