HR6654-119

In Committee

VAMOSA Act of 2025

119th Congress Introduced Dec 11, 2025

Summary

What This Bill Does

The VAMOSA Act adds a new section 534 to title 38 requiring VA-wide software asset management. The VA Secretary must ensure coordination between the Chief Information Officer and other appropriate officials to establish and implement a comprehensive policy for managing software assets. At minimum, the policy must maintain a comprehensive inventory, assess interoperability and license restrictions, identify and eliminate waste, fraud, and abuse by comparing inventory to purchase, subscription, billing, and contract records, coordinate significant software acquisitions, adopt cost-effective licensing strategies such as enterprise agreements, and measure and enforce license-term compliance. The CIO, CFO, and other officials must review and update the policy at least every three years. Employees responsible for acquiring, managing, or implementing software assets must receive annual training on contract restrictions, commercial versus custom software, and cost models. The work must use existing personnel, systems, and funds, with no new program or office. VA must include policy updates and estimated savings in the annual report to Congress, and the authority sunsets five years after enactment.

Who Benefits and How

VA information technology programs benefit from a comprehensive software inventory and better control over subscriptions, licenses, and usage entitlements. VA procurement officials benefit from training on license restrictions, cost models, enterprise agreements, and custom software decisions. Veterans may benefit indirectly if VA reduces waste and redirects resources toward mission needs. Congress benefits from annual reporting on policy updates and estimated cost savings. Taxpayers benefit if over-procurement and underused licenses are reduced.

Who Bears the Burden and How

The VA Secretary, Chief Information Officer, Chief Financial Officer, procurement staff, and software managers must build and maintain the inventory, compare records, review the policy every three years, train employees annually, enforce license terms, and report savings. VA employees responsible for software acquisition must complete annual training. Software vendors may face tougher negotiation over restrictions, deployment, data access, and transferability. VA must implement the requirements without new appropriations, personnel, systems, or a new office.

Key Provisions

  • Requires VA to establish a department-wide software asset management policy.
  • Requires a comprehensive inventory covering licenses, subscriptions, tenants, deployments, entitlements, SaaS, cloud services, platforms, and APIs.
  • Requires VA to identify waste, fraud, abuse, over-procurement, redundant purchases, unauthorized use, and underutilized licenses.
  • Requires annual training for employees who acquire, manage, or implement software assets.
  • Requires annual reporting on policy updates and estimated cost savings.
  • Requires implementation with existing resources and sunsets the authority after five years.

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 VA to establish a department-wide software asset management policy, maintain a comprehensive inventory, identify license waste and restrictions, train acquisition employees annually, report cost savings, and sunset the requirements after five years without new appropriations or a new office.

Key Policy Areas

Veterans, Information Technology, Federal Procurement, Software

Primary Purpose

Requires VA to establish a department-wide software asset management policy, maintain a comprehensive inventory, identify license waste and restrictions, train acquisition employees annually, report cost savings, and sunset the requirements after five years without new appropriations or a new office.

Policy Domains

Veterans Information Technology Federal Procurement Software

Substantive provisions

Identified Gains
  • VA information technology programs
  • VA procurement officials
  • Veterans
  • Congress
  • Taxpayers
Model: codex-gpt-5 | Version: bill_summary_v2 | Source: ih
Congress: ,
Veterans: ,
Taxpayers: ,
VA procurement officials: ,
VA information technology programs: ,
Identified Costs
  • VA Secretary
  • VA Chief Information Officer
  • VA Chief Financial Officer
  • VA software managers
  • VA acquisition employees
  • Software vendors
Model: codex-gpt-5 | Version: bill_summary_v2 | Source: ih
VA Secretary: ,
Software vendors: ,
VA software managers: ,
VA acquisition employees: ,
VA Chief Financial Officer: ,
VA Chief Information Officer: ,

Legislative Progress

In Committee
Introduced Committee Passed
Apr 15, 2026

Forwarded by Subcommittee to Full Committee by Voice Vote.

Apr 15, 2026

Subcommittee Consideration and Mark-up Session Held

Mar 25, 2026

Subcommittee Hearings Held

Jan 21, 2026

Referred to the Subcommittee on Oversight and Investigations.

Dec 11, 2025

Ms. Mace introduced the following bill; which was referred to …

Dec 11, 2025

Introduced in House

Dec 11, 2025

Referred to the House Committee on Veterans' Affairs.

Stakeholder Effects

cui bono?

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

Government
2 mentions across 2 clauses
-2 negative

Department of Veterans Affairs officials implementing department-wide software asset management

2/3
sections analyzed
Full impact breakdown

Bill Structure & Actor Mappings

Who is "The Secretary" in each section?

Domains
Veterans Information Technology Federal Procurement Software
Actor Mappings
"VA"
→ Department of Veterans Affairs
"CFO"
→ Chief Financial Officer
"CIO"
→ Chief Information Officer
"SaaS"
→ Software as a service

Key Definitions

Terms defined in this bill

1 term
"" §software asset

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