DAR File No. 32704

Technology Services, Administration

R895-6

IT Plan Submission Rule for Agencies

NOTICE OF PROPOSED RULE

DAR File No.: 32704
Filed: 06/03/2009, 06:11
Received by: NL

RULE ANALYSIS

Purpose of the rule or reason for the change:

The purpose of this amendment is to update the rule to match with the needs of Department of Technology Services (DTS). The current rule was written under the Division of Information Technology Services.

Summary of the rule or change:

The amendment: changes the time frame from two to one fiscal year; makes wording changes in the format sections; adds performance measures section; removes information technology (IT) assets inventory; changes in budget and planning fiscal year details; and adds IT alignment with business objectives.

State statutory or constitutional authorization for this rule:

Section 63F-1-204

Anticipated cost or savings to:

the state budget:

None--This is a function that is currently provided by the DTS IT Directors for the agencies they support. It is a part of their job function with no additional costs associated with these changes.

local governments:

None--This rule does not have any affect on local government because it is for executive branch agencies.

small businesses and persons other than businesses:

None--This rule does not have any affect on small business or persons outside state government.

Compliance costs for affected persons:

None--This rule does not have any affect on other persons.

Comments by the department head on the fiscal impact the rule may have on businesses:

The modification to the IT Plan submission process are being made to reflect the changes made with the creation creation of the Department of Technology Services and its operations of the IT plans for the agencies. J Stephen Fletcher, CIO and Executive Director

The full text of this rule may be inspected, during regular business hours, at the Division of Administrative Rules, or at:

Technology Services
Administration
Room 6000 STATE OFFICE BUILDING
450 N STATE ST
SALT LAKE CITY UT 84114

Direct questions regarding this rule to:

Russell Smith at the above address, by phone at 801-514-3125, by FAX at 801-538-3622, or by Internet E-mail at [email protected]

Interested persons may present their views on this rule by submitting written comments to the address above no later than 5:00 p.m. on:

07/31/2009

This rule may become effective on:

08/07/2009

Authorized by:

J Stephen Fletcher, CIO and Executive Director

R895. Technology Services, Administration.

R895-6. IT Plan Submission Rule for Agencies.

R895-6-2. Authority.

This rule is issued by the Chief Information Officer under the authority of Section 63F-1-206 of the Technology Governance Act, in accordance with Section [63-46a-3]63G-3-201 of the Utah Rulemaking Act, Utah Code Annotated, and section 63F-1-204 of the Utah code, Agency Information Technology Plans.

 

R895-6-4. Definitions.

(1) "Project" Investment in development of a new application/system or to upgrade or enhance an[d] existing information system.

(2) Plan Timeframe: [Two]One fiscal years into the future[; i.e., 1) Budget fiscal year and 2) Planning fiscal year].

(3) Severity level: Severity level is rated on four categories: impact on citizens, visibility to the public and Legislature, impact on state operations, and the consequences of doing nothing. The severity rating reflects the impact on external stakeholders.

(4) Risk level: The risk criteria measure the impact of the project on the organization, the effort needed to complete the project, the stability of the proposed technology, and the agency preparedness. The risk rating reflects the impact on the internal stakeholders.

 

R895-6-6. Agency IT Plan Format.

The following is the IT plan format:

(1) SUBMIT AN EXECUTIVE SUMMARY.

(a) Department/Agency Mission Statement.

(b) Department/Agency Business Objectives that have IT projects supporting them.

(c) Statement of IT Vision/Mission.

(d) Description of accomplishments of past calendar year.

[(e) Description of IT alignment with business objectives.

(f)](e) IT Budget Summary for Department/Agency.

[(g)](f) Verification of compliance procedures for information technology policies, administrative rules, and statutes.

(g) Describe performance measures used by the agency for implementing the agency's information technology objectives.

(2) IT PLAN DETAILS.

[(a) IT Assets Inventory.

(b)](a) Security Plan Documentation.

[(c)](b) Disaster Recovery/Business Resumption Plan Documentation.

[(d)](c) [Budget Fiscal Year : ]If a supplemental IT appropriation is anticipated, describe.

[(e)](d) [Planning Fiscal Year: ]Describe anticipated changes in objectives, projects or initiatives.

[(f)](e) [Planning Fiscal Year: ]If a building block request for an IT appropriation is anticipated, describe.

(3) PROPOSED PROJECT DESCRIPTION

Complete a project description for each IT project including the following information:

(a) Project organizational impact:

(i) Division (or other dept. sub-unit) project; identify:

(ii) Department project.

(iii) Cross-department project.

(b) Project Name.

(c) Project Manager.

(d) Project Purpose (check all that apply):

(i) Maintain/enhance existing infrastructure.

(ii) New infrastructure.

(iii) Maintain/enhance existing application/product.

(iv) Develop new application/product.

(v) Support of UCA 46-4-503.

(vi) Pilot project.

(vii) Implement/enhance GIS.

(viii) Collaboration with local government.

(ix) Public/private partnership.

(x) Other, please specify.

(4) DOCUMENT SUPPORT OF EXECUTIVE BRANCH STRATEGIC GOALS.

(5) DESCRIBE PROPOSED PROJECT AND ITS ANTICIPATED BENEFITS.

[(6) DESCRIBE PERFORMANCE MEASURES USED BY THE AGENCY FOR IMPLEMENTING THE AGENCY'S INFORMATION TECHNOLOGY OBJECTIVES.

(7)](6) IDENTIFY THE IMPACT ON [ITS ]DTS SERVICES THAT MAY RESULT WITH THE DEVELOPMENT OF THIS PROJECT.

[(8)](7) LIST ESTIMATED START AND END DATE FOR PROJECT.

[(9)](8) ESTIMATE PROJECT COSTS INCLUDING LABOR, HARDWARE, SOFTWARE, CONTRACT SERVICES AND OTHER.

[(10)](9) ESTIMATE ANNUAL OPERATION/MAINTENANCE COSTS.

[(11)](10) DESCRIBE RISK LEVEL OF PROJECT FOLLOWING CIO INSTRUCTION FOR FORMAT.

[(12)](11) DESCRIBE SEVERITY LEVEL OF PROJECT FOLLOWING CIO INSTRUCTION FOR FORMAT.

(12) DESCRIPTION OF IT ALIGNMENT WITH BUSINESS OBJECTIVES.

 

KEY: IT planning

Date of Enactment or Last Substantive Amendment: [June 28, 2004]2009

Authorizing, and Implemented or Interpreted Law: 63F-1-206; 63F-1-204; [63-46a-3]63G-3-201