Minnesota Legislature
HF 2557
1st Committee Engrossment - 86th Legislature (2009 - 2010) Posted on 03/19/2013 07:29pm
KEY: stricken = removed, old language.
underscored = added, new language.
1.2relating to state government; establishing a position for a state Webmaster;
1.3requiring the state chief information officer to develop standards for enhanced
1.4public access to state electronic records; amending Minnesota Statutes 2008,
1.5sections 16E.04, subdivision 2; 16E.05, by adding a subdivision; Minnesota
1.6Statutes 2009 Supplement, section 16E.02, subdivision 1.
1.7BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF MINNESOTA:
1.8 Section 1. Minnesota Statutes 2009 Supplement, section 16E.02, subdivision 1, is
1.9amended to read:
1.10 Subdivision 1. Office management and structure. (a) The chief information officer
1.11is appointed by the governor. The chief information officer serves in the unclassified
1.12service at the pleasure of the governor. The chief information officer must have experience
1.13leading enterprise-level information technology organizations. The chief information
1.14officer is the state's chief information officer and information and telecommunications
1.15technology advisor to the governor.
1.16(b) The chief information officer may appoint other employees of the office.
1.17The staff of the office must include individuals knowledgeable in information and
1.18telecommunications technology systems and services and individuals with specialized
1.19training in information security and accessibility.
1.20(c) The chief information officer may appoint a Webmaster responsible for the
1.21supervision and development of state Web sites under the control of the office. The
1.22Webmaster, if appointed, shall ensure that these Web sites are maintained in an easily
1.23accessible format that is consistent throughout state government and are consistent
1.24with the accessibility standards developed under section 16E.03, subdivision 9. The
1.25Webmaster, if appointed, shall provide assistance and guidance consistent with the
2.1requirements of this paragraph to other state agencies for the maintenance of other Web
2.2sites not under the direct control of the office.
2.3 Sec. 2. Minnesota Statutes 2008, section 16E.04, subdivision 2, is amended to read:
2.4 Subd. 2. Responsibilities. (a) In addition to other activities prescribed by law, the
2.5office shall carry out the duties set out in this subdivision.
2.6 (b) The office shall develop and establish a state information architecture to ensure:
2.7(1) that state agency development and purchase of information and communications
2.8systems, equipment, and services is designed to ensure that individual agency information
2.9systems complement and do not needlessly duplicate or conflict with the systems of other
2.10agencies; and
2.11(2) enhanced public access to data can be provided consistent with standards
2.12developed under section 16E.05, subdivision 4.
2.13When state agencies have need for the same or similar public data, the chief information
2.14officer, in coordination with the affected agencies, shall manage the most efficient and
2.15cost-effective method of producing and storing data for or sharing data between those
2.16agencies. The development of this information architecture must include the establishment
2.17of standards and guidelines to be followed by state agencies. The office shall ensure
2.18compliance with the architecture.
2.19 (c) The office shall assist state agencies in the planning and management of
2.20information systems so that an individual information system reflects and supports the
2.21state agency's mission and the state's requirements and functions. The office shall review
2.22and approve agency technology plans to ensure consistency with enterprise information
2.23and telecommunications technology strategy. By January 15 of each year, the chief
2.24information officer must report to the chairs and the ranking minority members of
2.25the legislative committees and divisions with jurisdiction over the office regarding the
2.26assistance provided under this paragraph. The report must include a listing of agencies
2.27that have developed or are developing plans under this paragraph.
2.28 (d) The office shall review and approve agency requests for funding for the
2.29development or purchase of information systems equipment or software before the
2.30requests may be included in the governor's budget.
2.31 (e) The office shall review major purchases of information systems equipment to:
2.32 (1) ensure that the equipment follows the standards and guidelines of the state
2.33information architecture;
2.34 (2) ensure the agency's proposed purchase reflects a cost-effective policy regarding
2.35volume purchasing; and
3.1 (3) ensure that the equipment is consistent with other systems in other state agencies
3.2so that data can be shared among agencies, unless the office determines that the agency
3.3purchasing the equipment has special needs justifying the inconsistency.
3.4 (f) The office shall review the operation of information systems by state agencies
3.5and ensure that these systems are operated efficiently and securely and continually meet
3.6the standards and guidelines established by the office. The standards and guidelines must
3.7emphasize uniformity that is cost-effective for the enterprise, that encourages information
3.8interchange, open systems environments, and portability of information whenever
3.9practicable and consistent with an agency's authority and chapter 13.
3.10 (g) The office shall conduct a comprehensive review at least every three years of
3.11the information systems investments that have been made by state agencies and higher
3.12education institutions. The review must include recommendations on any information
3.13systems applications that could be provided in a more cost-beneficial manner by an outside
3.14source. The office must report the results of its review to the legislature and the governor.
3.15 Sec. 3. Minnesota Statutes 2008, section 16E.05, is amended by adding a subdivision
3.16to read:
3.17 Subd. 4. Standards for transparency. The chief information officer, in consultation
3.18with the Information Policy Analysis Division of the Department of Administration,
3.19shall develop standards to enhance public access to electronic data maintained by state
3.20government, consistent with the requirements of chapter 13. The standards must ensure
3.21that:
3.22(1) the state information architecture facilitates public access to agency data;
3.23(2) publicly available data is managed using an approved state metadata model; and
3.24(3) all geospatial data conform to an approved state geocode model.
3.25 Sec. 4. TRANSPARENCY STANDARDS REPORT.
3.26By January 15, 2011, the chief information officer shall report to the chairs and
3.27ranking minority members of the legislative committees with jurisdiction over the
3.28Office of Enterprise Technology regarding the development of the standards to enhance
3.29public access to data required under Minnesota Statutes, section 16E.05, subdivision 4.
3.30The report must describe the process for development of the standards, including the
3.31opportunity provided for public comment, and specify the components of the standards
3.32that have been implemented, including a description of the level of public use of the new
3.33opportunities for data access under the standards.
1.3requiring the state chief information officer to develop standards for enhanced
1.4public access to state electronic records; amending Minnesota Statutes 2008,
1.5sections 16E.04, subdivision 2; 16E.05, by adding a subdivision; Minnesota
1.6Statutes 2009 Supplement, section 16E.02, subdivision 1.
1.7BE IT ENACTED BY THE LEGISLATURE OF THE STATE OF MINNESOTA:
1.8 Section 1. Minnesota Statutes 2009 Supplement, section 16E.02, subdivision 1, is
1.9amended to read:
1.10 Subdivision 1. Office management and structure. (a) The chief information officer
1.11is appointed by the governor. The chief information officer serves in the unclassified
1.12service at the pleasure of the governor. The chief information officer must have experience
1.13leading enterprise-level information technology organizations. The chief information
1.14officer is the state's chief information officer and information and telecommunications
1.15technology advisor to the governor.
1.16(b) The chief information officer may appoint other employees of the office.
1.17The staff of the office must include individuals knowledgeable in information and
1.18telecommunications technology systems and services and individuals with specialized
1.19training in information security and accessibility.
1.20(c) The chief information officer may appoint a Webmaster responsible for the
1.21supervision and development of state Web sites under the control of the office. The
1.22Webmaster, if appointed, shall ensure that these Web sites are maintained in an easily
1.23accessible format that is consistent throughout state government and are consistent
1.24with the accessibility standards developed under section 16E.03, subdivision 9. The
1.25Webmaster, if appointed, shall provide assistance and guidance consistent with the
2.1requirements of this paragraph to other state agencies for the maintenance of other Web
2.2sites not under the direct control of the office.
2.3 Sec. 2. Minnesota Statutes 2008, section 16E.04, subdivision 2, is amended to read:
2.4 Subd. 2. Responsibilities. (a) In addition to other activities prescribed by law, the
2.5office shall carry out the duties set out in this subdivision.
2.6 (b) The office shall develop and establish a state information architecture to ensure:
2.7(1) that state agency development and purchase of information and communications
2.8systems, equipment, and services is designed to ensure that individual agency information
2.9systems complement and do not needlessly duplicate or conflict with the systems of other
2.10agencies; and
2.11(2) enhanced public access to data can be provided consistent with standards
2.12developed under section 16E.05, subdivision 4.
2.13When state agencies have need for the same or similar public data, the chief information
2.14officer, in coordination with the affected agencies, shall manage the most efficient and
2.15cost-effective method of producing and storing data for or sharing data between those
2.16agencies. The development of this information architecture must include the establishment
2.17of standards and guidelines to be followed by state agencies. The office shall ensure
2.18compliance with the architecture.
2.19 (c) The office shall assist state agencies in the planning and management of
2.20information systems so that an individual information system reflects and supports the
2.21state agency's mission and the state's requirements and functions. The office shall review
2.22and approve agency technology plans to ensure consistency with enterprise information
2.23and telecommunications technology strategy. By January 15 of each year, the chief
2.24information officer must report to the chairs and the ranking minority members of
2.25the legislative committees and divisions with jurisdiction over the office regarding the
2.26assistance provided under this paragraph. The report must include a listing of agencies
2.27that have developed or are developing plans under this paragraph.
2.28 (d) The office shall review and approve agency requests for funding for the
2.29development or purchase of information systems equipment or software before the
2.30requests may be included in the governor's budget.
2.31 (e) The office shall review major purchases of information systems equipment to:
2.32 (1) ensure that the equipment follows the standards and guidelines of the state
2.33information architecture;
2.34 (2) ensure the agency's proposed purchase reflects a cost-effective policy regarding
2.35volume purchasing; and
3.1 (3) ensure that the equipment is consistent with other systems in other state agencies
3.2so that data can be shared among agencies, unless the office determines that the agency
3.3purchasing the equipment has special needs justifying the inconsistency.
3.4 (f) The office shall review the operation of information systems by state agencies
3.5and ensure that these systems are operated efficiently and securely and continually meet
3.6the standards and guidelines established by the office. The standards and guidelines must
3.7emphasize uniformity that is cost-effective for the enterprise, that encourages information
3.8interchange, open systems environments, and portability of information whenever
3.9practicable and consistent with an agency's authority and chapter 13.
3.10 (g) The office shall conduct a comprehensive review at least every three years of
3.11the information systems investments that have been made by state agencies and higher
3.12education institutions. The review must include recommendations on any information
3.13systems applications that could be provided in a more cost-beneficial manner by an outside
3.14source. The office must report the results of its review to the legislature and the governor.
3.15 Sec. 3. Minnesota Statutes 2008, section 16E.05, is amended by adding a subdivision
3.16to read:
3.17 Subd. 4. Standards for transparency. The chief information officer, in consultation
3.18with the Information Policy Analysis Division of the Department of Administration,
3.19shall develop standards to enhance public access to electronic data maintained by state
3.20government, consistent with the requirements of chapter 13. The standards must ensure
3.21that:
3.22(1) the state information architecture facilitates public access to agency data;
3.23(2) publicly available data is managed using an approved state metadata model; and
3.24(3) all geospatial data conform to an approved state geocode model.
3.25 Sec. 4. TRANSPARENCY STANDARDS REPORT.
3.26By January 15, 2011, the chief information officer shall report to the chairs and
3.27ranking minority members of the legislative committees with jurisdiction over the
3.28Office of Enterprise Technology regarding the development of the standards to enhance
3.29public access to data required under Minnesota Statutes, section 16E.05, subdivision 4.
3.30The report must describe the process for development of the standards, including the
3.31opportunity provided for public comment, and specify the components of the standards
3.32that have been implemented, including a description of the level of public use of the new
3.33opportunities for data access under the standards.