ALLcrimesfood&drugstaxestelecomcommercehealthconservationtransportationagricultureveteransbrowse all titles »
0

44 U.S.C. § 3520 — Chief Data Officers

submitted 24 years ago by Pub. L. 107-198 to r/title-44-PUBLIC-PRINTING-AND-DOCUMENTS · 646 words · no verdicts yet

in plain englishAI-generated · not legal advice

Each agency must designate a nonpolitical appointee employee as its Chief Data Officer. The officer manages agency data, coordinates data-related work, supports agency performance and evaluation, and reports annually on compliance.

(a) Establishment. The head of each agency must designate a nonpolitical appointee employee in the agency as Chief Data Officer.

(b) Qualifications. The designation must be based on demonstrated training and experience in data management and governance, including creating, applying, and maintaining data standards; collecting, analyzing, protecting, using, and sharing data; and statistical and related methods for protecting and removing identifying information from confidential data.

(c) Functions. The Chief Data Officer must—
(1) manage data throughout its lifecycle;
(2) coordinate with agency officials who use, protect, share, or generate data so the agency’s data needs are met;
(3) manage agency data assets, including standardizing formats, sharing assets, and publishing them as law allows;
(4) while carrying out paragraphs (3) and (5), consult the agency’s statistical official designated under 5 U.S.C. § 314;
(5) carry out the agency’s duties under 44 U.S.C. § 3506(b)–(d), (f), and (i), § 3507, and § 3511;
(6) ensure, as far as practicable, that agency data follows data-management best practices;
(7) involve employees, the public, and contractors in using public data assets and encourage collaborative ways to improve data use;
(8) support the Performance Improvement Officer in identifying and using data for 31 U.S.C. § 1124(a)(2);
(9) support the Evaluation Officer in obtaining data for 5 U.S.C. § 313(d);
(10) review how agency infrastructure affects access to data assets and coordinate with the Chief Information Officer to improve that infrastructure and reduce access barriers;
(11) ensure, as far as practicable, that the agency makes maximum use of data, including to produce evidence (a term defined in 44 U.S.C. § 3561), protect cybersecurity, and improve operations;
(12) identify points of contact for open-data roles and responsibilities as the Director requires;
(13) act as the agency’s liaison with other agencies and the Office of Management and Budget about using existing agency data for statistical purposes (a term defined in § 3561); and
(14) follow regulations and guidance under subchapter III, including obtaining and maintaining required certifications and training.

(d) Delegation of responsibilities. (1) As needed to comply with statistical laws, the Chief Data Officer must delegate a subsection (c) responsibility to the head of an agency statistical agency or unit (a term defined in § 3561). (2) To the extent law permits, the person receiving the delegation must consult the Chief Data Officer while carrying it out. (3) The Chief Data Officer must defer to that person about the necessary delegation concerning data the agency acquires, keeps, or shares under applicable statistical law.

(e) Reports. Each year, the Chief Data Officer must report to the Senate Homeland Security and Governmental Affairs Committee and the House Oversight and Government Reform Committee on the agency’s compliance with this subchapter. The report must identify each requirement the agency could not carry out and, if applicable, what the agency needs to carry it out.

the actual law source: uscode.house.gov ↗public domain
(a)Establishment.—

The head of each agency shall designate a nonpolitical appointee employee in the agency as the Chief Data Officer of the agency.

(b)Qualifications.—

The Chief Data Officer of an agency shall be designated on the basis of demonstrated training and experience in data management, governance (including creation, application, and maintenance of data standards), collection, analysis, protection, use, and dissemination, including with respect to any statistical and related techniques to protect and de-identify confidential data.

(c)Functions.—

The Chief Data Officer of an agency shall—

(1)

be responsible for lifecycle data management;

(2)

coordinate with any official in the agency responsible for using, protecting, disseminating, and generating data to ensure that the data needs of the agency are met;

(3)

manage data assets of the agency, including the standardization of data format, sharing of data assets, and publication of data assets in accordance with applicable law;

(4)

in carrying out the requirements under paragraphs (3) and (5), consult with any statistical official of the agency (as designated under section 314 of title 5);

(5)

carry out the requirements of the agency under subsections (b) through (d), (f), and (i) of section 3506, section 3507, and section 3511;

(6)

ensure that, to the extent practicable, agency data conforms with data management best practices;

(7)

engage agency employees, the public, and contractors in using public data assets and encourage collaborative approaches on improving data use;

(8)

support the Performance Improvement Officer of the agency in identifying and using data to carry out the functions described in section 1124(a)(2) of title 31;

(9)

support the Evaluation Officer of the agency in obtaining data to carry out the functions described in section 313(d) of title 5;

(10)

review the impact of the infrastructure of the agency on data asset accessibility and coordinate with the Chief Information Officer of the agency to improve such infrastructure to reduce barriers that inhibit data asset accessibility;

(11)

ensure that, to the extent practicable, the agency maximizes the use of data in the agency, including for the production of evidence (as defined in section 3561), cybersecurity, and the improvement of agency operations;

(12)

identify points of contact for roles and responsibilities related to open data use and implementation (as required by the Director);

(13)

serve as the agency liaison to other agencies and the Office of Management and Budget on the best way to use existing agency data for statistical purposes (as defined in section 3561); and

(14)

comply with any regulation and guidance issued under subchapter III, including the acquisition and maintenance of any required certification and training.

(d)Delegation of Responsibilities.—
(1)In general.—

To the extent necessary to comply with statistical laws, the Chief Data Officer of an agency shall delegate any responsibility under subsection (c) to the head of a statistical agency or unit (as defined in section 3561) within the agency.

(2)Consultation.—

To the extent permissible under law, the individual to whom a responsibility has been delegated under paragraph (1) shall consult with the Chief Data Officer of the agency in carrying out such responsibility.

(3)Deference.—

The Chief Data Officer of the agency shall defer to the individual to whom a responsibility has been delegated under paragraph (1) regarding the necessary delegation of such responsibility with respect to any data acquired, maintained, or disseminated by the agency under applicable statistical law.

(e)Reports.—

The Chief Data Officer of an agency shall submit to the Committee on Homeland Security and Governmental Affairs of the Senate and the Committee on Oversight and Government Reform of the House of Representatives an annual report on the compliance of the agency with the requirements of this subchapter, including information on each requirement that the agency could not carry out and, if applicable, what the agency needs to carry out such requirement.

Source credit: (Added Pub. L. 107–198, § 3(a)(2), June 28, 2002, 116 Stat. 730; amended Pub. L. 115–435, title II, § 202(e)(1), Jan. 14, 2019, 132 Stat. 5541.)

history & why it existsrecord from the source credit
  • 2002Enacted · Pub. L. 107-198 · 116 Stat. 730
  • 2019Amended · Pub. L. 115-435 · 132 Stat. 5541

A history note hasn’t been published yet. The record shows enactment by Pub. L. 107-198 on 2002-06-28.

all 0 arguments · sorted by: best

0/280

no arguments yet — make the first case