(a) Within one year of the hiring of a chief data officer and every two years thereafter, the managing director, in consultation with the director, other city agencies, agency data coordinators, and the council, shall create a city data plan for submission to the mayor, the council, and all agency directors. The city data plan, at minimum, shall:
(1) Establish governance structures for the implementation of the city data plan;
(2) Address the strategic use of data throughout city operations by, at a minimum:
(A) Establishing data management and analysis standards across all agencies;
(B) Developing specific, short-term goals achievable for each agency within the two years following the submission of the initial city data plan (which plan is to be submitted within one year of the hiring of a chief data officer) and within two years of each plan submitted thereafter, as well as longer-term goals; and
(C) Making recommendations to enhance standardization and integration of data systems and data management practices across all agencies;
(3) Address open data policies and procedures by, at minimum:
(B) Developing specific short- and long-term goals for each agency for the posting of data sets, pursuant to § 2-19.2; and
(C) Establishing guidelines for the selection and prioritization of data sets for posting for each agency;
(4) Establish processes for compliance with the city data plan by each agency in accordance with § 2-19.6; and
(5) Incorporate any technical policies, procedures, or standards developed by the director.
(b) All city data plans submitted after the submission of the initial city data plan (which shall be submitted within one year of the hiring of a chief data officer) shall report project funding and expenditures, cost savings, cost avoidance, efficiency gains, process improvements, and major accomplishments. A description of cost savings and cost avoidance shall include immediate monetary impacts as well as ongoing projections.
(Added by Ord.
22-31
)