Part 2. Information Technology Planning, Funding, and Reporting.

§ 143B‑1330.  Planning and financing State information technology resources.

(a) The State CIO shall develop policies for agency information technology planning and financing. Agencies shall prepare and submit such plans as required in this section, as follows:

(1) The Department shall analyze the State's legacy information technology systems and develop a plan to document the needs and costs for replacement systems, as well as determining and documenting the time frame during which State agencies can continue to efficiently use legacy information technology systems, resources, security, and data management to support their operations. The plan shall include an inventory of legacy applications and infrastructure, required capabilities not available with the legacy system, the process, time line, and cost to migrate from legacy environments, and any other information necessary for fiscal or technology planning. The State CIO shall have the authority to prioritize the upgrade and replacement of legacy systems. Agencies shall provide all requested documentation to validate reporting on legacy systems and shall make the systems available for inspection by the Department.

(2) The State CIO shall develop a biennial State Information Technology Plan (Plan), including, but not limited to, the use of cloud‑based utility computing for use by State agencies.

(3) The State CIO shall develop one or more strategic plans for information technology. The State CIO shall determine whether strategic plans are needed for any agency and shall consider an agency's operational needs, functions, and capabilities when making such determinations.

(b) Based on requirements identified during the strategic planning process, the Department shall develop and transmit to the General Assembly the biennial State Information Technology Plan in conjunction with the Governor's budget of each regular session. The Plan shall include the following elements:

(1) Anticipated requirements for information technology support over the next five years.

(2) An inventory of current information technology assets and major projects. As used in this subdivision, the term "major project" includes projects costing more than five hundred thousand dollars ($500,000) to implement.

(3) Significant unmet needs for information technology resources over a five‑year time period. The Plan shall rank the unmet needs in priority order according to their urgency.

(4) A statement of the financial requirements, together with a recommended funding schedule and funding sources for major projects and other requirements in progress or anticipated to be required during the upcoming fiscal biennium.

(5) An analysis of opportunities for statewide initiatives that would yield significant efficiencies or improve effectiveness in State programs.

(6) As part of the plan, the State CIO shall develop and periodically update a long‑range State Information Technology Plan that forecasts, at a minimum, the needs of State agencies for the next 10 years.

(c) Each participating agency shall actively participate in preparing, testing, and implementing an information technology plan required under subsection (b) of this section. Separate agencies shall prepare biennial information technology plans, including the requirements listed in subsection (b) of this section, and transmit these plans to the Department by a date determined by the State CIO in each even‑numbered year. Agencies shall provide all financial information to the State CIO necessary to determine full costs and expenditures for information technology assets and resources provided by the agencies or through contracts or grants. The Department shall consult with and assist State agencies in the preparation of these plans; shall provide appropriate personnel or other resources to the participating agencies and to separate agencies upon request. Plans shall be submitted to the Department by a date determined by the State CIO in each even‑numbered year. (2015‑241, s. 7A.2(b); 2015‑268, s. 2.11; 2016‑94, s. 7.4(h).)