Sec. 3. SOFTWARE REUSE

694 words·~3 min read·/statute-compilations/comps-17951/sec-3

A research copy — for the controlling text, always check the official state or federal source. Not legal advice.

## SEC. 3 SOFTWARE REUSE ###

(a)Sharing Not later than 210 days after the date of enactment of this Act, the head of each agency shall ensure that the custom-developed code of the agency and other key technical components of the code (including documentation, data models, schemas, metadata, architecture designs, configuration scripts, and artifacts required to develop, build, test, and deploy the code) of the code are— ####

(1)stored at not less than 1 public repository or private repository; ####

(2)accessible to Federal employees via procedures developed under subsection (d)(1)(A)(ii)(III); and ####

(3)owned by the agency. ###

(b)Software Reuse Rights in Procurement Contracts The head of an agency that enters into a contract for the custom development of software shall acquire and exercise rights sufficient to enable the governmentwide access to, sharing of, use of, and modification of any custom-developed code created in the development of such software. ###

(c)Discovery Not later than 210 days after the date of enactment of this Act, the head of each agency shall make metadata created on or after such date for the custom-developed code of the agency publicly accessible. ###

(d)Accountability Mechanisms ####

(1)Agency cios Not later than 180 days after the date of enactment of this Act, the Chief Information Officer of each agency, in consultation with the Chief Acquisition Officer, or similar official, of the agency and the Administrator of the Office of Electronic Government, shall develop an agency-wide policy that— #####

(A)implements the requirements of this Act, including— ######

(i)ensuring that custom-developed code follows the best practices established by the Director of the Office and Management and Budget under paragraph

(3)for operating repositories and version control systems to keep track of changes and to facilitate collaboration among multiple developers; and ######

(ii)managing the sharing of custom-developed code under subsection (b), and the public accessibility of metadata under subsection (c), including developing— ######

(I)procedures to determine whether any custom-developed code meets the conditions under section 4(b) for an exemption under this Act; ######

(II)procedures for making metadata for custom-developed code publicly accessible pursuant to subsection (c); ######

(III)procedures for Federal employees to gain access to public repositories and private repositories that contain custom developed source code; and ######

(IV)standardized reporting practices across the agency to capture key information relating to a contract under which custom-developed source code was produced for reporting statistics about the contract; and #####

(B)corrects or amends any policies of the agency that are inconsistent with the requirements of this Act. ####

(2)Administrator of the office of electronic government #####

(A)Minimum standard reporting requirements Not later than 120 days after the date of enactment of this Act, the Administrator of the Office of Electronic Government shall establish minimum standard reporting requirements for the Chief Information Officers of agencies, which shall include information relating to— ######

(i)measuring the frequency of reuse of code, including access and modification under subsection (b); ######

(ii)whether the shared code is maintained; ######

(iii)whether there is a feedback mechanism for improvements to or community development of the shared code; and ######

(iv)the number and circumstances of all exemptions granted under section 4(a)(2). #####

(B)Reporting requirement ######

(i)Requirement Not later than 1 year after the date of the enactment of this Act, and annually thereafter, the Administrator of the Office of Electronic Government shall publish on a centralized website a report on the implementation of this Act that includes— ######

(I)a complete list of all exemptions granted under section 4(a)(2); and ######

(II)information showing whether each agency has updated the acquisition and other policies of the agency to be compliant with this Act. ######

(ii)Open government data asset The report under clause

(i)shall be maintained as an open Government data asset (as defined in section 3502 of title 44, United States Code). ####

(3)Guidance The Director of the Office of Management and Budget shall issue guidance, consistent with the purpose of this Act, that establishes best practices and uniform procedures across agencies for the purposes of implementing this subsection.