; and (2) all software and other key technical components, including documentation, data models, schemas, metadata, and architecture designs, are owned by the agency. (b) Software Reuse Rights in Procurement Contracts (1) In general The head of an agency that enters into a contract for the custom development of software shall acquire and enforce rights sufficient to enable the governmentwide access, execution, and modification of the custom-developed code relating to the software. (2) Best practices (A) Contract administration With respect to a contract described in paragraph (1), the head of an agency shall ensure appropriate contract administration and use of best practices to secure the full scope of licenses and rights for the Federal Government of the custom-developed code developed under the contract, to allow for access, execution, and modification by other agencies. (B) Development process With respect to a contract described in paragraph (1), the head of an agency shall ensure the use of best practices to require and obtain the delivery of the custom-developed code, documentation of the custom-developed code, configuration and artifacts required to develop, build, test, and deploy the custom-developed code, and other associated materials from the developer throughout the development process. (c) Discovery Not later than 210 days after the date of enactment of this Act, the head of each agency shall make metadata 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 Federal Chief Information Officer, shall develop an agency-wide policy that— (A) addresses the requirements of this Act, including— (i) ensuring that agency custom-developed code follows best practices for operating repositories and version control systems to keep track of changes and