Approval of acquisitions of information technology.
Checkout our iOS App for a better way to browser and research.
(1)
(a) In accordance with Subsection (2), the chief information officer shall approve the acquisition by an executive branch agency of:
(i) information technology equipment;
(ii) telecommunications equipment;
(iii) software;
(iv) services related to the items listed in Subsections (1)(a)(i) through (iii); and
(v) data acquisition.
(b) The chief information officer may negotiate the purchase, lease, or rental of private or public information technology or telecommunication services or facilities in accordance with this section.
(c) Where practical, efficient, and economically beneficial, the chief information officer shall use existing private and public information technology or telecommunication resources.
(d) Notwithstanding another provision of this section, an acquisition authorized by this section shall comply with rules made by the applicable rulemaking authority under Title 63G, Chapter 6a, Utah Procurement Code.
(2) Before negotiating a purchase, lease, or rental under Subsection (1) for an amount that exceeds the value established by the chief information officer by rule in accordance with Section 63A-16-205, the chief information officer shall:
(a) conduct an analysis of the needs of executive branch agencies and subscribers of services and the ability of the proposed information technology or telecommunications services or supplies to meet those needs; and
(b) for purchases, leases, or rentals not covered by an existing statewide contract, certify in writing to the chief procurement officer in the Division of Purchasing and General Services that:
(i) the analysis required in Subsection (2)(a) was completed; and
(ii) based on the analysis, the proposed purchase, lease, rental, or master contract of services, products, or supplies is practical, efficient, and economically beneficial to the state and the executive branch agency or subscriber of services.
(3) In approving an acquisition described in Subsections (1) and (2), the chief information officer shall:
(a) establish by administrative rule, in accordance with Section 63A-16-205, standards under which an agency must obtain approval from the chief information officer before acquiring the items listed in Subsections (1) and (2);
(b) for those acquisitions requiring approval, determine whether the acquisition is in compliance with:
(i) the executive branch strategic plan;
(ii) the applicable agency information technology plan;
(iii) the budget for the executive branch agency or department as adopted by the Legislature;
(iv)Title 63G, Chapter 6a, Utah Procurement Code; and
(v) the information technology accessibility standards described in Section 63A-16-209; and
(c) in accordance with Section 63A-16-206, require coordination of acquisitions between two or more executive branch agencies if it is in the best interests of the state.
(4) Each executive branch agency shall provide the chief information officer with complete access to all information technology records, documents, and reports:
(a) at the request of the chief information officer; and
(b) related to the executive branch agency's acquisition of any item listed in Subsection (1).
(5)
(a) In accordance with administrative rules established by the department under Section 63A-16-205, an executive branch agency and the department may not initiate a new technology project unless the technology project is described in a formal project plan and a business case analysis is approved by the chief information officer and the highest ranking executive branch agency official.
(b) The project plan and business case analysis required by this Subsection (5) shall include:
(i) a statement of work to be done and existing work to be modified or displaced;
(ii) total cost of system development and conversion effort, including system analysis and programming costs, establishment of master files, testing, documentation, special equipment cost and all other costs, including overhead;
(iii) savings or added operating costs that will result after conversion;
(iv) other advantages or reasons that justify the work;
(v) source of funding of the work, including ongoing costs;
(vi) consistency with budget submissions and planning components of budgets; and
(vii) whether the work is within the scope of projects or initiatives envisioned when the current fiscal year budget was approved.
(c) The chief information officer shall determine the required form of the project plan and business case analysis described in this Subsection (5).
(6) The chief information officer and the Division of Purchasing and General Services within the department shall work cooperatively to establish procedures under which the chief information officer shall monitor and approve acquisitions as provided in this section.