; and (3) 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) the ongoing maintenance of software asset management upon the completion of the remediation; (C) automation of software license management processes and incorporation of discovery tools across the agency; (D) 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) 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) the differences between acquiring commercial software products and services and acquiring or building custom software; and (iii) determining the costs of different types of licenses and options for adjusting licenses to meet increasing or decreasing demand; and (E) maximizing the effectiveness of software deployed by the agency, including, to the extent practicable, leveraging technologies that— (i) measure actual software usage via analytics that can identify inefficiencies to assist in rationalizing software spending; (ii) allow for segmentation of the user base