Bill Overview
Title: Strengthening Agency Management and Oversight of Software Assets Act
Description: This bill requires each federal agency to develop assessments of their software inventories and software licenses and a plan to reduce costs by consolidating licenses and adopting enterprise license agreements to the greatest extent practicable. The bill also requires the Office of Management and Budget and the Government Accountability Office to report on various government-wide issues relating to federal software licenses and inventories.
Sponsors: Sen. Peters, Gary C. [D-MI]
Target Audience
Population: Federal employees and contractors involved in software asset management
Estimated Size: 2700000
- The bill specifically addresses federal agencies and their management practices regarding software assets.
- Federal employees will be involved in implementing and complying with the new requirements set forth in the bill, including assessments, consolidation of software licenses, and transition to enterprise licenses.
- Oversight bodies like OMB, GAO, and Congress will be involved in reviewing the assessments and strategies submitted by agencies.
- Software vendors and contractors who provide services to federal agencies will potentially be impacted by changes in procurement practices and the movement towards open-source software.
- Federal government projects and services that rely heavily on software infrastructure may experience changes in cost efficiency and performance.
Reasoning
- This policy primarily affects federal employees, particularly those in IT, procurement, and management roles related to software asset management.
- Contractors involved with federal projects will also be impacted, especially those providing software solutions or services.
- The general public may not be directly affected since this policy focuses on internal federal agency practices.
- The budget constraints mean the policy will need to be implemented efficiently to maximize impact on agency performance and cost savings.
- The policy would not directly impact individuals outside of the federal employment or contractor ecosystem.
Simulated Interviews
IT Manager at a Federal Agency (Washington, D.C.)
Age: 45 | Gender: male
Wellbeing Before Policy: 6
Duration of Impact: 5.0 years
Commonness: 15/20
Statement of Opinion:
- This policy seems necessary to improve our current software management.
- Enterprise licensing can save our agency money, but it will require effort to implement.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 7 | 6 |
| Year 2 | 7 | 6 |
| Year 3 | 7 | 6 |
| Year 5 | 8 | 6 |
| Year 10 | 8 | 5 |
| Year 20 | 7 | 5 |
Software Vendor Sales Representative (Denver, CO)
Age: 34 | Gender: female
Wellbeing Before Policy: 7
Duration of Impact: 3.0 years
Commonness: 12/20
Statement of Opinion:
- This could impact my sales if the government shifts to more open-source software.
- We might need to adjust our offerings and pricing.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 6 | 7 |
| Year 2 | 6 | 7 |
| Year 3 | 6 | 7 |
| Year 5 | 7 | 7 |
| Year 10 | 7 | 6 |
| Year 20 | 7 | 6 |
Federal Contractor (New York, NY)
Age: 50 | Gender: male
Wellbeing Before Policy: 5
Duration of Impact: 2.0 years
Commonness: 10/20
Statement of Opinion:
- Streamlining software across agencies is overdue; it could improve efficiency and transparency.
- There might be challenges transitioning to enterprise licenses.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 6 | 5 |
| Year 2 | 6 | 5 |
| Year 3 | 6 | 5 |
| Year 5 | 6 | 5 |
| Year 10 | 5 | 5 |
| Year 20 | 5 | 4 |
Federal Employee in Procurement (Seattle, WA)
Age: 28 | Gender: female
Wellbeing Before Policy: 6
Duration of Impact: 5.0 years
Commonness: 8/20
Statement of Opinion:
- This policy provides clear guidance on how we can optimize our software inventory.
- Adopting enterprise licenses should be beneficial, though it might require training.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 7 | 6 |
| Year 2 | 7 | 6 |
| Year 3 | 7 | 6 |
| Year 5 | 8 | 6 |
| Year 10 | 8 | 6 |
| Year 20 | 8 | 6 |
General Services Administration Analyst (Chicago, IL)
Age: 40 | Gender: male
Wellbeing Before Policy: 7
Duration of Impact: 10.0 years
Commonness: 14/20
Statement of Opinion:
- This effort is well aligned with our goals of improving government spending efficiency.
- We will need to monitor changes closely to ensure intended outcomes are met.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 8 | 7 |
| Year 2 | 8 | 7 |
| Year 3 | 8 | 7 |
| Year 5 | 9 | 7 |
| Year 10 | 9 | 7 |
| Year 20 | 9 | 7 |
Retired Federal IT Specialist (Atlanta, GA)
Age: 60 | Gender: female
Wellbeing Before Policy: 8
Duration of Impact: 2.0 years
Commonness: 7/20
Statement of Opinion:
- While I'm retired, I've seen the inefficiencies firsthand; this policy addresses some core issues.
- The success will heavily depend on execution and collaboration across agencies.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 8 | 8 |
| Year 2 | 8 | 8 |
| Year 3 | 8 | 8 |
| Year 5 | 8 | 8 |
| Year 10 | 8 | 8 |
| Year 20 | 8 | 8 |
Open Source Software Advocate (San Francisco, CA)
Age: 38 | Gender: other
Wellbeing Before Policy: 6
Duration of Impact: 5.0 years
Commonness: 9/20
Statement of Opinion:
- This offers a wonderful opportunity to push for broader open-source adoption.
- Concerns remain over whether agencies will truly transition effectively.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 7 | 6 |
| Year 2 | 7 | 6 |
| Year 3 | 8 | 6 |
| Year 5 | 8 | 6 |
| Year 10 | 8 | 6 |
| Year 20 | 9 | 6 |
Federal Project Manager (Los Angeles, CA)
Age: 55 | Gender: male
Wellbeing Before Policy: 5
Duration of Impact: 10.0 years
Commonness: 13/20
Statement of Opinion:
- This mandate will create additional workload in the short term.
- Long-term benefits could include smoother project operations and reduced costs.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 6 | 5 |
| Year 2 | 6 | 5 |
| Year 3 | 7 | 5 |
| Year 5 | 8 | 5 |
| Year 10 | 8 | 5 |
| Year 20 | 8 | 5 |
Government Accountability Office Researcher (Austin, TX)
Age: 46 | Gender: female
Wellbeing Before Policy: 7
Duration of Impact: 7.0 years
Commonness: 11/20
Statement of Opinion:
- Efficient software management is crucial; our findings will guide future policy changes.
- It's essential that agencies accurately report their software use and needs to maximize savings.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 8 | 7 |
| Year 2 | 8 | 7 |
| Year 3 | 8 | 7 |
| Year 5 | 9 | 7 |
| Year 10 | 9 | 7 |
| Year 20 | 8 | 7 |
Federal IT Support Staff (Boston, MA)
Age: 31 | Gender: male
Wellbeing Before Policy: 5
Duration of Impact: 3.0 years
Commonness: 16/20
Statement of Opinion:
- Adapting to new standards could be challenging at first, but I see the potential long-term benefits.
- There may be some apprehension among my colleagues about job impacts.
Wellbeing Over Time (With vs Without Policy)
| Year | With Policy | Without Policy |
|---|---|---|
| Year 1 | 6 | 5 |
| Year 2 | 6 | 5 |
| Year 3 | 7 | 5 |
| Year 5 | 7 | 5 |
| Year 10 | 6 | 5 |
| Year 20 | 6 | 5 |
Cost Estimates
Year 1: $5000000 (Low: $4000000, High: $6000000)
Year 2: $6000000 (Low: $5000000, High: $7000000)
Year 3: $7000000 (Low: $6000000, High: $8000000)
Year 5: $8000000 (Low: $7000000, High: $9000000)
Year 10: $0 (Low: $0, High: $0)
Year 100: $0 (Low: $0, High: $0)
Key Considerations
- The initial cost outlay for assessments and strategy development is necessary but could provide long-term savings.
- Agencies may face challenges in coordinating software inventory audits and standardizing procurement practices.
- Competence in handling open-source software solutions will be crucial in realizing projected cost savings.
- Training and transitioning costs for new software systems may emerge as the policy is implemented.