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