Sec. 4. Enterprise Licensing Positioning at Agencies
559 words·~3 min read·
/bill/118/s/931/rs/section-4A research copy — for the controlling text, always check the official state or federal source. Not legal advice.
The Chief Information Officer of each agency, in consultation with the Chief Financial Officer and the Chief Procurement Officer 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— to consolidate software licenses of the agency; and to the greatest extent practicable, in order to improve the performance of, and reduce unnecessary costs to, the agency, to adopt enterprise license agreements across the agency, by type or category of software.
The plan of an agency shall— include a detailed strategy for— the remediation of any software asset management deficiencies found during the comprehensive assessment of the agency; the ongoing maintenance of software asset management upon the completion of the remediation; and maximizing the effectiveness of software deployed by the agency, including, to the extent practicable, leveraging technologies that— provide in-depth analysis of user behaviors and collect user feedback; measure actual software usage via analytics that can identify inefficiencies to assist in rationalizing software spending; allow for segmentation of the user base; support effective governance and compliance in the use of software; and support interoperable capabilities between software; identify not fewer than 5 categories of software the agency will prioritize for conversion to enterprise licenses as the software entitlements, contracts, and other agreements or arrangements for those categories come up for renewal or renegotiation; provide an estimate of the costs to move to 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; 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 through a cloud service provider; 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; include any estimates for additional resources, services, or support the agency may need to execute the enterprise licensing position plan; provide information on the prevalence of software products in use across multiple software categories; and include any additional information, data, or analysis determined necessary by the Chief Information Officer, or other equivalent official, of the agency.
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. 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.
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.