US Codex
Bill
Notes

H.R. 1695 — what changed

Strengthening Agency Management and Oversight of Software Assets Act

From Introduced in House to Engrossed in House. 5 sections amended between Introduced in House and Engrossed in House.

Sec. 2 Definitions

In this Act:

(1)
Administrator— The term Administrator means the Administrator of General Services.
(2)
changed Agency— The term agency has the meaning given that term in section 3502 of title 44, United States Code.Code, except that such term does not include an element of the intelligence community.
(3)
Cloud computing— The term cloud computing has the meaning given the term in Special Publication 800–145 of the National Institute of Standards and Technology, or any successor document.
(4)
changed Cloud service provider— The term cloud service provider means an entity offering cloud computing products or services to agencies.has the meaning given the term in section 3607(b) of title 44, United States Code.
(5)
Comprehensive assessment— The term comprehensive assessment means a comprehensive assessment conducted pursuant to section 3(a).
(6)
Director— The term Director means the Director of the Office of Management and Budget.
(7)
added Intelligence community— The term intelligence community has the meaning given the term in section 3 of the National Security Act of 1947 (50 U.S.C. 3003).
(8)
renumbered was (9) Plan— The term plan means the plan developed by a Chief Information Officer, or equivalent official, pursuant to section 4(a).
(9)
renumbered was (10) Software entitlement— The term software entitlement means any software that—
(A)
renumbered was (10)(3) has been purchased, leased, or licensed by or billed to an agency under any contract or other business arrangement; and
(B)
renumbered was (10)(4) is subject to use limitations.
(10)
renumbered was (11) Software inventory— The term software inventory means the software inventory of an agency required pursuant to—
(A)
renumbered was (11)(3) section 2(b)(2)(A) of the Making Electronic Government Accountable By Yielding Tangible Efficiencies Act of 2016 (40 U.S.C. 11302 note; Public Law 114–210); or
(B)
renumbered was (11)(4) subsequent guidance issued by the Director pursuant to that Act.

Sec. 3 Software inventory update and expansion

(a)
changed In general— As soon as practicable, and not later than 1 year 18 months after the date of enactment of this Act, the Chief Information Officer of each agency, in consultation with the Chief Financial Officer, the Chief Procurement Acquisition Officer, the Chief Data Officer, and General Counsel of the agency, or the equivalent officials of the agency, shall complete a comprehensive assessment of the software entitlements and software inventories of paid for by, in use at, or deployed throughout the agency, which shall include—
(1)
changed the current software inventory of the agency, including software entitlements, contracts and other agreements or arrangements of the agency, and a list of the largest software entitlements of the agency separated by vendor provider and category of software;
(2)
a comprehensive, detailed accounting of—
(A)
changed any software used by or deployed for within the agency, including software developed or built by the agency, or by another agency for use by the agency, including shared services, as of the date of the comprehensive assessment, including, to the extent identifiable, the contracts and other agreements or arrangements that used by the agency uses to acquire, build, deploy, or use such software;
(B)
changed information and data on software entitlements, which shall include information on any additional fees or costs, including fees or costs for the use of cloud services services, that is are not included in the initial costs of the contract, agreement, or arrangement—
(i)
for which the agency pays;
(ii)
that are not deployed or in use by the agency; and
(iii)
changed that are billed to the agency under any contract or business arrangement that creates redundancy duplication, or are otherwise determined to be unnecessary by the Chief Information Officer of the agency, or the equivalent official, in the deployment or use by the agency; and
(C)
the extent—
(i)
to which any software paid for, in use, or deployed throughout the agency is interoperable; and
(ii)
of the efforts of the agency to improve interoperability of software assets throughout the agency enterprise;
(3)
changed a categorization of software licenses entitlements of the agency by cost, volume, and type of software;
(4)
changed a list of any provisions in the software licenses entitlements of the agency that may restrict how the software can be deployed, accessed, or used, including any such restrictions on desktop or server hardware or hardware, through a cloud service provider; provider, or on data ownership or access; and
(5)
an analysis addressing—
(A)
changed the accuracy and completeness of the software inventory and software entitlements of the agency before and after the comprehensive assessment;
(B)
changed management by the agency management of and compliance by the agency with all contracts or other agreements or arrangements that include or implicate reference software licensing entitlements or software management within the agency;
(C)
changed the extent to which the agency accurately captures the total cost of enterprise licenses agreements software entitlements and related costs, including the total cost of upgrades over the life of a contract, cloud usage cost per user, costs, and any other cost associated with the maintenance or servicing of contracts; and
(D)
compliance with software license management policies of the agency.
(b)
Contract support—
(1)
Authority— The head of an agency may enter into 1 or more contracts to support the requirements of subsection (a).
(2)
changed No conflict of interest— Contracts under paragraph (1) shall not include contractors with organization organizational conflicts of interest.interest, within the meaning given that term under subpart 9.5 of the Federal Acquisition Regulation.
(3)
Operational independence— Over the course of a comprehensive assessment, contractors hired pursuant to paragraph (1) shall maintain operational independence from the integration, management, and operations of the software inventory and software entitlements of the agency.
(c)
changed Submission— On the date on which the Chief Information Officer, Chief Financial Officer, Chief Procurement Acquisition Officer, the Chief Data Officer, and General Counsel of an agency, or the equivalent officials of the agency, complete the comprehensive assessment, and not later than 1 year after the date of enactment of this Act, the Chief Information Officer shall submit the comprehensive assessment to—to the head of the agency.
(d)
added Subsequent submission— Not later than 30 days after the date on which the head of an agency receives the comprehensive assessment under subsection (c), the head of the agency shall submit the comprehensive assessment to—
(1)
removed the head of the agency;
(1)
renumbered was (4)(4) the Director;
(2)
renumbered was (4)(5) the Administrator;
(3)
renumbered was (4)(6) the Comptroller General of the United States;
(4)
renumbered was (4)(7) the Committee on Homeland Security and Governmental Affairs of the Senate; and
(5)
renumbered was (4)(8) the Committee on Oversight and Accountability of the House of Representatives.
(e)
added Consultation— In order to ensure the utility and standardization of the comprehensive assessment of each agency, including to support the development of each plan and the report required under section 4(e)(2), the Director, in consultation with the Administrator, shall share information, best practices, and recommendations relating to the activities performed in the course of a comprehensive assessment of an agency.
(f)
added Intelligence community— For each element of the intelligence community, a comprehensive assessment described under subsection (a) shall be—
(1)
added conducted separately;
(2)
added performed only by an entity designated by the head of the element of the intelligence community, in accordance with appropriate applicable laws;
(3)
added performed in such a manner as to ensure appropriate protection of information which, if disclosed, may adversely affect national security; and
(4)
added submitted in summary form, not later than 30 days after the date on which the head of the element of the intelligence community receives the assessment, by the head of the element of the intelligence community to—
(A)
added the Director;
(B)
added the Select Committee on Intelligence of the Senate; and
(C)
added the Permanent Select Committee on Intelligence of the House of Representatives.
(d)
removed Consultation— In order to ensure the utility and standardization of the comprehensive assessment of each agency, including to support the development of each plan and the Government-wide strategy described in section 5, the Director, in consultation with the Administrator, may share information, best practices, and recommendations relating to the activities performed in the course of a comprehensive assessment of an agency.

Sec. 4 Software modernization planning at agencies

(a)
changed In general— The Chief Information Officer of each agency, in consultation with the Chief Financial Officer and Officer, the Chief Procurement Officer Acquisition Officer, the Chief Data Officer, and the General Counsel of the agency, or the equivalent officials of the agency, shall use the information developed pursuant to the comprehensive assessment of the agency to develop a plan for the agency—
(1)
changed to consolidate software licenses entitlements of the agency; andagency;
(2)
changed to the greatest extent practicable, ensure that, in order to improve the performance of, and reduce unnecessary costs to, the agency, to the Chief Information Officer, Chief Data Officer, and Chief Acquisition Officer of the agency, or the equivalent officers, develop criteria and procedures for how the agency will adopt cost-effective acquisition strategies, including enterprise license agreements licensing, across the agency, by type or category of software.agency that reduce costs, eliminate excess licenses, and improve performance; and
(3)
added to restrict the ability of a bureau, program, component, or operational entity within the agency to acquire, use, develop, or otherwise leverage any software entitlement (or portion thereof) without the approval of the Chief Information Officer of the agency, in consultation with the Chief Acquisition Officer of the agency, or the equivalent officers of the agency.
(b)
Plan requirements— The plan of an agency shall—
(1)
include a detailed strategy for—
(A)
the remediation of any software asset management deficiencies found during the comprehensive assessment of the agency;
(B)
changed the ongoing maintenance of software asset management upon the completion of the remediation; andremediation;
(C)
added automation of software license management processes and incorporation of discovery tools across the agency;
(D)
added ensuring that officers and employees of the agency are adequately trained in the policies, procedures, rules, regulations, and guidance relating to the software acquisition and development of the agency before entering into any agreement relating to any software entitlement (or portion thereof) for the agency, including training on—
(i)
added negotiating options within contracts to address and minimize provisions that restrict how the agency may deploy, access, or use the software, including restrictions on deployment, access, or use on desktop or server hardware and restrictions on data ownership or access;
(ii)
added the differences between acquiring commercial software products and services and acquiring or building custom software; and
(iii)
added determining the costs of different types of licenses and options for adjusting licenses to meet increasing or decreasing demand; and
(E)
renumbered was (3)(3)(4) maximizing the effectiveness of software deployed by the agency, including, to the extent practicable, leveraging technologies that—
(i)
removed provide in-depth analysis of user behaviors and collect user feedback;
(i)
renumbered was (3)(3)(4)(3) measure actual software usage via analytics that can identify inefficiencies to assist in rationalizing software spending;
(ii)
renumbered was (3)(3)(4)(4) allow for segmentation of the user base;
(iii)
renumbered was (3)(3)(4)(5) support effective governance and compliance in the use of software; and
(iv)
renumbered was (3)(3)(4)(6) support interoperable capabilities between software;
(2)
changed identify not fewer than 5 categories of software the agency will could prioritize for conversion to more cost-effective software licenses, including enterprise licenses licenses, as the software entitlements, contracts, and other agreements or arrangements for those categories come up for renewal or renegotiation;
(3)
changed provide an estimate of the costs to move to toward more enterprise, open-source, or other licenses that do not restrict the use of software by the agency, and the projected cost savings, efficiency measures, and improvements to agency performance throughout the total software lifecycle;
(4)
changed identify potential mitigations to minimize software license restrictions on how such software can be deployed, accessed, or used, including any mitigations that would minimize any such restrictions on desktop or server hardware or hardware, through a cloud service provider;provider, or on data ownership or access;
(5)
changed ensure that the purchase by the agency of any enterprise license or other software is based on publicly available criteria that are not unduly structured to favor any specific vendor;vendor, unless prohibited by law (including regulation);
(6)
changed include any estimates for additional resources, services, or support the agency may need to execute implement the enterprise licensing position plan;
(7)
provide information on the prevalence of software products in use across multiple software categories; and
(8)
include any additional information, data, or analysis determined necessary by the Chief Information Officer, or other equivalent official, of the agency.
(c)
removed Consultation and coordination— The Director, in coordination with the Chief Information Officers Council, the Chief Acquisition Officers Council, the Administrator, and other government and industry representatives identified by the Director, may establish processes to identify, define, and harmonize common definitions, terms and conditions, and other information and criteria to support agency heads in developing and implementing the plans required by this section.
(c)
renumbered was (5) Support— The Chief Information Officer, or other equivalent official, of an agency may request support from the Director and the Administrator for any analysis or developmental needs to create the plan of the agency.
(d)
added Agency submission—
(1)
added In general— Not later than 1 year after the date on which the head of an agency submits the comprehensive assessment pursuant to section 3(d), the head of the agency shall submit to the Director, the Committee on Homeland Security and Governmental Affairs of the Senate, and the Committee on Oversight and Accountability of the House of Representatives the plan of the agency.
(2)
added Intelligence community— Not later than 1 year after the date on which the head of an element of the intelligence community submits the summary assessment pursuant to section 3(f)(4), the head of the element shall separately submit the plan of the element to the Director, the Select Committee on Intelligence of the Senate, and the Permanent Select Committee on Intelligence of the House of Representatives.
(e)
changed Submission—Consultation and coordination— Not later than 120 days after the date on which the Chief Information Officer, or other equivalent official, of an agency submits the comprehensive assessment pursuant to section 3(c), the head of the agency shall submit to the Director, the Committee on Homeland Security and Governmental Affairs of the Senate, and the Committee on Oversight and Accountability of the House of Representatives the plan of the agency.The Director—
(1)
added in coordination with the Administrator, the Chief Information Officers Council, the Chief Acquisition Officers Council, the Chief Data Officers Council, the Chief Financial Officers Council, and other government and industry representatives identified by the Director, shall establish processes, using existing reporting functions, as appropriate, to identify, define, and harmonize common definitions, terms and conditions, standardized requirements, and other information and criteria to support agency heads in developing and implementing the plans required by this section; and
(2)
added in coordination with the Administrator, and not later than 2 years after the date of enactment of this Act, submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Oversight and Accountability of the House of Representatives a report detailing recommendations to leverage Government procurement policies and practices with respect to software acquired by, developed by, deployed within, or in use at 1 or more agencies to—
(A)
added increase the interoperability of software licenses, including software entitlements and software built by Government agencies;
(B)
added consolidate licenses, as appropriate;
(C)
added reduce costs;
(D)
added improve performance; and
(E)
added modernize the management and oversight of software entitlements and software built by Government agencies, as identified through an analysis of agency plans.

Sec. 5 GAO report

added Not later than 3 years after the date of enactment of this Act, the Comptroller General of the United States shall submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Oversight and Accountability of the House of Representatives a report on—

(1)
added Government-wide trends in agency software asset management practices;
(2)
added comparisons of software asset management practices among agencies;
(3)
added the establishment by the Director of processes to identify, define, and harmonize common definitions, terms, and conditions under section 4(e);
(4)
added agency compliance with the restrictions on contract support under section 3(b); and
(5)
added other analyses of and findings regarding the plans of agencies, as determined by the Comptroller General of the United States.
(a)
removed In general— Not later than 2 years after the date of enactment of this Act, the Director, in consultation with the Administrator and the Federal Chief Information Officers Council, shall submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Oversight and Accountability of the House of Representatives a strategy that includes—
(1)
removed proposals to support the adoption of Government-wide enterprise licenses for software entitlements identified through the comprehensive assessments and plans, including, where appropriate, a cost-benefit analysis;
(2)
removed opportunities to leverage Government procurement policies and practices to increase interoperability of software entitlements acquired and deployed to reduce costs and improve performance;
(3)
removed the incorporation of data on spending by agencies on, the performance of, and management by agencies of software entitlements as part of the information required under section 11302(c)(3)(B) of title 40, United States Code;
(4)
removed where applicable, directions to agencies to examine options and relevant criteria for transitioning to open-source software; and
(5)
removed any other information or data collected or analyzed by the Director.
(b)
removed Budget Submission—
(1)
removed First budget— With respect to the first budget of the President submitted under section 1105(a) of title 31, United States Code, on or after the date that is 2 years after the date of enactment of this Act, the Director shall ensure that the strategy required under subsection (a) of this section and the plan of each agency are included in the budget justification materials of each agency submitted in conjunction with that budget.
(2)
removed Subsequent 5 budgets— With respect to the first 5 budgets of the President submitted under section 1105(a) of title 31, United States Code, after the budget described in paragraph (1), the Director shall—
(A)
removed designate performance metrics for agencies for common software licensing, management, and cost criteria; and
(B)
removed ensure that the progress of each agency toward the performance metrics is included in the budget justification materials of the agency submitted in conjunction with that budget.

Sec. 6 No additional funds

changed Not later than 3 years after the date of enactment of this Act, the Comptroller General of the United States shall submit No additional funds are authorized to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Oversight and Accountability of the House of Representatives a report on Government-wide trends, comparisons among agencies, and other analyses of plans and the strategy required under section 5(a) by be appropriated for the Comptroller General purpose of the United States.carrying out this Act.