Strengthening Agency Management and Oversight of Software Assets Act

Bill Number: S. 1956
Origin Chamber: Senate
Congress: 119th Congress, Session 1
Policy Area: Government Operations and Politics
Status: Introduced
Latest Action: 2025-06-04: Read twice and referred to the Committee on Homeland Security and Governmental Affairs.
Last Updated: 2026-02-24T15:33:52Z

AI-Generated Summary

Purpose

The Strengthening Agency Management and Oversight of Software Assets Act aims to enhance federal agencies' tracking, management, and efficiency of software assets. It focuses on reducing waste, improving cost-effectiveness, and increasing accountability in how agencies acquire, use, and maintain software, including licenses and cloud-based services.

Key Provisions

Comprehensive Software Assessments (Section 3): Within 18 months of enactment, each agency's Chief Information Officer (CIO), in consultation with the Chief Financial Officer, Chief Acquisition Officer, Chief Data Officer, and General Counsel (or equivalents), must conduct a detailed review of all agency software. This includes:
Updating the existing software inventory (a list of all software in use, including purchased, leased, or licensed items with usage limits, known as "software entitlements").
Accounting for all software usage, contracts, hidden costs (e.g., cloud fees or upgrades), interoperability (how well software works together), and any unused or duplicate licenses.
Categorizing software by cost, volume, and type; identifying restrictions on use (e.g., limits on hardware, cloud deployment, or data access); and analyzing compliance with contracts and total costs.
Agencies may hire external contractors for support, but these must avoid conflicts of interest (e.g., no involvement in the agency's ongoing software operations) and maintain independence.
Assessments are submitted internally, then to the Director of the Office of Management and Budget (OMB), Administrator of General Services (GSA), Comptroller General (head of the Government Accountability Office, or GAO), and relevant congressional committees within 30 days.
The OMB Director, with GSA, shares best practices across agencies to standardize assessments.

Software Modernization Plans (Section 4): Using assessment results, each agency's CIO must develop a plan within one year of submitting the assessment. The plan must:
Consolidate licenses to eliminate duplicates and restrict new acquisitions without CIO and Chief Acquisition Officer approval.
Outline strategies for fixing deficiencies, automating license tracking (e.g., using tools to monitor usage), training staff on negotiations and cost options, and maximizing software efficiency (e.g., through analytics for usage data and promoting interoperability).
Identify opportunities to switch to cost-effective options like enterprise-wide licenses or open-source software, estimate costs and savings, and mitigate usage restrictions.
Ensure purchases use fair, public criteria without favoring specific vendors (unless legally required).
Plans are submitted to OMB Director and congressional committees; agencies can request OMB/GSA support.
OMB Director coordinates with government councils (e.g., CIO Council) and industry to standardize terms and processes, and submits a government-wide report within two years recommending ways to improve interoperability, consolidation, costs, performance, and oversight.

GAO Oversight Report (Section 5): Within three years, the GAO must report to congressional committees on:
Government-wide trends and agency comparisons in software management.
OMB's standardization efforts, contractor compliance, and analysis of agency plans.

Funding (Section 6): No new funds are authorized; implementation uses existing agency resources.

Significant Changes to Existing Law

Builds on the 2016 Making Electronic Government Accountable By Yielding Tangible Efficiencies Act (often called the MEGABYTE Act), which requires basic software inventories, by expanding them to include detailed cost accounting, interoperability checks, usage restrictions, and hidden fees.
Introduces mandatory modernization plans and centralized approval for software acquisitions, which were not previously required at this level of detail.
Adds government-wide coordination through OMB and councils, plus GAO reporting, to enforce standardization and oversight beyond individual agency efforts.
Prohibits conflicts in contractor support for assessments, drawing from Federal Acquisition Regulation rules on organizational conflicts (situations where a contractor's interests could bias results).

Potential Impacts

On Government Agencies: Could lead to significant cost savings by eliminating unused licenses and duplicates, estimated through plans' projections; improves efficiency via better training, automation, and interoperability, potentially reducing long-term maintenance expenses. Agencies must reallocate existing budgets for assessments and plans, with possible short-term administrative burdens.
On Citizens: Indirect benefits through more efficient use of taxpayer dollars on software, potentially freeing resources for public services; no direct impact on individual rights or services.
On International Relations: Minimal to none, as the bill focuses on domestic federal operations; it may indirectly affect U.S. government interactions with foreign software vendors through fair procurement criteria.

Main Stakeholders Affected

Federal Agencies: All executive branch agencies (as defined under records management laws) must comply, with CIOs and other chiefs bearing primary responsibility.
Oversight Bodies: OMB (leads coordination), GSA (supports assessments and plans), and GAO (provides independent audits).
Congress: Committees on Homeland Security and Governmental Affairs (Senate) and Oversight and Government Reform (House) receive reports and ensure accountability.
Software Industry: Vendors and cloud providers face increased scrutiny on licensing terms, restrictions, and fair competition; agencies may negotiate harder for flexible, cost-effective deals.
Contractors: Third-party firms assisting assessments must adhere to strict independence rules.

Notable Legal, Constitutional, or Political Implications

Legal: Strengthens contract compliance and acquisition rules under existing federal laws (e.g., Federal Acquisition Regulation), promoting transparency in spending without creating new enforcement penalties; emphasizes fair procurement to avoid vendor favoritism, aligning with antitrust principles.
Constitutional: Supports Article I's congressional spending power by enhancing oversight of executive branch expenditures; no direct challenges to separation of powers, as it mandates internal agency processes and reporting to Congress.
Political: Bipartisan sponsorship (introduced by Senators Peters, Cassidy, Ernst, Tillis, Lankford, and Wyden) signals broad support for government efficiency; no new funding requirement pressures agencies to prioritize within budgets, potentially sparking debates on resource allocation. Could set precedents for similar reforms in other IT areas, like cybersecurity or data management.

This summary was generated by AI and may contain inaccuracies. Refer to the official source document for the authoritative text.

Sponsor

Sen. Peters, Gary C. [D-MI]

Cosponsors (5)

Sen. Cassidy, Bill [R-LA], Sen. Ernst, Joni [R-IA], Sen. Tillis, Thomas [R-NC], Sen. Lankford, James [R-OK], Sen. Wyden, Ron [D-OR]

Recent Actions

2025-06-04: Read twice and referred to the Committee on Homeland Security and Governmental Affairs.
2025-06-04: Introduced in Senate

Bill Versions

Strengthening Agency Management and Oversight of Software Assets Act — issued 2025-06-04 — PDF (15 pages)