VAMOSA Act of 2025
- Sponsor
- Rep. Mace, Nancy [R-SC-1]
- Committees
- Veterans' Affairs Committee (primary)
- Last action
- Apr 15, 2026
Bottom line
The bill mandates the VA to create a comprehensive software asset management policy to improve efficiency and reduce waste, without authorizing new funding, and includes a five-year sunset clause.
What it actually does
This bill requires the Department of Veterans Affairs (VA) to establish and implement a comprehensive policy for managing all its software assets, including maintaining an inventory, assessing interoperability, identifying waste, coordinating acquisitions, adopting cost-effective licensing, and enforcing license terms. It also mandates regular reviews of the policy, annual training for relevant employees, and an annual report to Congress on updates and cost savings. The policy must be implemented using existing resources and will sunset after five years.
Proponents argue
Supporters argue that this bill is a critical step towards modernizing the VA's IT infrastructure, ensuring taxpayer dollars are spent efficiently, and preventing costly redundancies or non-compliance with software licenses. They contend that a comprehensive policy, coupled with mandatory training and independent oversight, will lead to significant cost savings and improved operational effectiveness within the Department.
Opponents contend
Critics might argue that while the goals of efficiency and waste reduction are laudable, mandating a comprehensive new policy and training without authorizing additional appropriations could strain existing VA resources. They may contend that this could lead to under-resourced implementation or divert funds and personnel from other critical veteran services, potentially adding administrative burden without guaranteed substantial improvements.
The bill is very short and clearly written, making it highly accessible for any reader to understand its provisions and implications quickly.
Section 2(a), adding new 38 U.S.C. § 534(a) and (b)
Establishment of Comprehensive Software Asset Management Policy
This provision requires the Secretary of Veterans Affairs to work with the Chief Information Officer and other relevant officials to create and implement a department-wide policy for managing all software assets. The policy must include maintaining a complete inventory, assessing software compatibility and license restrictions, identifying and eliminating waste (like redundant purchases or unused licenses), coordinating significant software acquisitions, using cost-effective licensing strategies, and ensuring compliance with license terms.
Supporters argue
Proponents argue that this policy is essential for a large organization like the VA to effectively manage its vast and complex software portfolio, preventing wasteful spending on redundant licenses and ensuring compliance. They believe it will streamline operations and free up resources for direct veteran care.
Critics contend
While the concept of efficiency is generally supported, some critics might argue that the VA already has existing IT management protocols, and this new mandate could create additional bureaucratic layers without a guaranteed return on investment, potentially diverting focus from other critical departmental priorities.
Tradeoffs
The provision balances the need for robust oversight and financial efficiency in software procurement against the administrative burden and potential resource reallocation required to establish and maintain such a comprehensive policy within a large federal agency.
Section 2(a), adding new 38 U.S.C. § 534(c) and (d)
Policy Reviews, Updates, and Employee Training
This section requires the VA's Chief Information Officer (CIO), in consultation with the Chief Financial Officer (CFO), to review and update the software asset management policy at least once every three years. Additionally, it mandates annual training for all VA employees responsible for acquiring, managing, or implementing software assets. This training will cover topics such as negotiating contract terms, understanding different software acquisition models, and evaluating various licensing structures.
Section 2(a), adding new 38 U.S.C. § 534(e) and (f)
Implementation Using Existing Resources and Annual Reporting
This provision explicitly states that the new software asset management policy must be implemented using existing personnel, systems, and funds, meaning no additional appropriations are authorized, nor can a new program or office be established. It also requires the Secretary of Veterans Affairs to include a description of any substantive policy updates and an estimate of cost savings realized from the policy's implementation in the VA's annual report to Congress.
Section 2(a), adding new 38 U.S.C. § 534(h)
Five-Year Sunset Clause
This provision specifies that all requirements and authorities established by the new section 534 (the software asset management policy) will automatically terminate five years after the date the VAMOSA Act is enacted. This means the policy and its mandates will cease to be in effect unless Congress takes further action to extend or reauthorize them.
The definition of 'comprehensive inventory of software assets' explicitly includes the inventory required by the 'Making Electronic Government Accountable By Yielding Tangible Efficiencies Act of 2016' (MEGABYTE Act) and any related OMB directives, in addition to all other software assets. This ensures the new policy builds upon and expands existing federal mandates.
Section 2(a), adding new 38 U.S.C. § 534(g)(1)
Why it matters:This is standard legislative practice for defining terms, but its inclusion here ensures the new policy is not redundant but rather comprehensive by integrating existing requirements.
Case for: Supporters argue that explicitly linking to the MEGABYTE Act ensures continuity and prevents redundant efforts, while expanding the scope to 'all other software assets' makes the VA's inventory truly comprehensive, maximizing efficiency gains.
Case against: No significant case against, as this provision clarifies and expands the scope in a logical manner.
Estimated impact: Ensures a broader and more integrated approach to software inventory management than if the bill only addressed new requirements, potentially leading to greater overall efficiency and cost savings across the VA's entire software footprint.
This subsection explicitly states that the new software asset management policy must be implemented using existing personnel, systems, and funds, and does not authorize additional appropriations or the establishment of a new program, office, or organizational entity.
Section 2(a), adding new 38 U.S.C. § 534(e)
Why it matters:This could be a deliberate choice to ensure fiscal conservatism without making the funding constraint the most prominent feature of the bill, or it could be standard practice for an unfunded mandate.
Case for: Proponents would argue this provision demonstrates fiscal responsibility, ensuring the VA improves efficiency within its existing budget and does not contribute to increased federal spending, aligning with calls for government austerity.
Case against: Critics might argue that mandating a 'comprehensive policy' and annual training without any new funding constitutes an unfunded mandate, potentially straining existing VA resources, diverting funds from other critical services, or leading to a less effective implementation due to lack of dedicated resources.
Estimated impact: This clause significantly impacts the VA's ability to allocate dedicated resources (personnel, tools, budget) specifically for this initiative, forcing internal reallocation and prioritization, which could affect the speed and thoroughness of implementation.