[Rev. 11/21/2013 3:58:03 PM--2013]

[NAC-242 Revised Date: 4-12]

CHAPTER 242 - INFORMATION SERVICES

242.010            Definitions.

242.015            “Administrator” defined.

242.020            “Division” defined.

242.040            “Feasibility study” defined.

242.050            “Information system” defined.

242.060            “Project” defined.

242.070            “Requesting agency” defined.

242.080            “Resources for an information system” defined.

242.090            “State agency” defined.

242.100            “Vendor” defined.

242.110            Adoption by reference of Nevada Information Systems Policies and Standards Manual.

242.120            Feasibility study: Completion or waiver required before state agency may begin project.

242.130            Feasibility study: Determination of requirement; contents; participation by Division.

242.140            Feasibility study: Maintenance of documentation.

242.150            Request for assistance from Division; submission of services for approval of requesting agency; charging for services.

242.160            Contract between Division and vendor: Procedure.

 

 

 

      NAC 242.010  Definitions. (NRS 242.111)  As used in this chapter, unless the context otherwise requires, the words and terms defined in NAC 242.015 to 242.100, inclusive, have the meanings ascribed to them in those sections.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.015  “Administrator” defined. (NRS 242.111)  “Administrator” means the Administrator of the Division.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)—(Substituted in revision for NAC 242.030)

      NAC 242.020  “Division” defined. (NRS 242.111)  “Division” means the Division of Enterprise Information Technology Services of the Department of Administration.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.040  “Feasibility study” defined. (NRS 242.111)  “Feasibility study” means the definition and examination of alternative methods to meet a requesting agency’s business needs in determining whether a course of action based on the needs, priorities and capabilities of a project is possible.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.050  “Information system” defined. (NRS 242.111)  “Information system” means any automated process used for data processing, office automation or communications technology.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.060  “Project” defined. (NRS 242.111)  “Project” means a deployment of resources for an information system.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.070  “Requesting agency” defined. (NRS 242.111)  “Requesting agency” means a state agency which requests resources for an information system or services from the Division.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.080  “Resources for an information system” defined. (NRS 242.111)  “Resources for an information system” means any hardware or software for a computer, data files, hard copy generated by a computer, data facilities, communication lines, modems, multiplexors, concentrators, power sources or any other assets related to a computer-based information system or computer installation, including any services provided by natural persons in connection with that system or installation.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.090  “State agency” defined. (NRS 242.111)  “State agency” means an agency or elected officer within the Executive Branch of State Government who uses or plans to use resources for an information system for electronic processing or storage of public records.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.100  “Vendor” defined. (NRS 242.111)  “Vendor” means a person or a governmental agency, other than a state agency, which provides resources for an information system.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.110  Adoption by reference of Nevada Information Systems Policies and Standards Manual. (NRS 242.111)

     1.  The Nevada Information Systems Policies and Standards Manual is hereby adopted by reference as it existed on September 1, 1992.

     2.  Except as otherwise provided in subsection 3, a copy of:

     (a) The Nevada Information Systems Policies and Standards Manual may be obtained from the Division of Enterprise Information Technology Services, 100 North Stewart Street, Suite 100, Carson City, Nevada 89701, for the price of $25.

     (b) Section 12 of the Nevada Information Systems Policies and Standards Manual may be obtained from the Division of Enterprise Information Technology Services, 100 North Stewart Street, Suite 100, Carson City, Nevada 89701, for the price of $10.

     3.  The Division will provide, without charge, a copy of the Manual to each state agency.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.120  Feasibility study: Completion or waiver required before state agency may begin project. (NRS 242.111)  A state agency shall not begin a project unless a feasibility study of the project has been completed or the requirement for a feasibility study has been waived by the Division.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.130  Feasibility study: Determination of requirement; contents; participation by Division. (NRS 242.111)

     1.  The Division will determine whether a feasibility study is required for each proposed project.

     2.  Each feasibility study must include:

     (a) A description of the problem to be resolved and its origin;

     (b) The objectives, scope and anticipated results of the project;

     (c) Any proposed alternate course of action;

     (d) Sufficient information to allow the requesting agency and the Administrator to make decisions concerning the merits of the proposed project;

     (e) An analysis of the costs and benefits and an assessment of the risks for each proposed alternate course of action; and

     (f) A plan for the management of the project, including a schedule for reporting and reviewing the project.

     3.  Each alternate course of action included in a feasibility study must be consistent with:

     (a) The state agency’s plan for the use of resources for an information system;

     (b) The biennial state plan; and

     (c) The standards set forth in the Nevada Information Systems Policies and Standards Manual.

     4.  A requesting agency may conduct the feasibility study independently or in conjunction with the Division. If the Division participates in the study, it will charge the requesting agency for the cost of the services it provides to the agency.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.140  Feasibility study: Maintenance of documentation. (NRS 242.111)  Each state agency shall maintain sufficient documentation for each feasibility study to ensure the resolution of any questions concerning the purpose, justification, nature or scope of the project.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.150  Request for assistance from Division; submission of services for approval of requesting agency; charging for services. (NRS 242.111)

     1.  A state agency which requests assistance from the Division for an information system must submit a written proposal to the Division. The state agency may develop the proposal independently or in conjunction with the Division.

     2.  Each proposal must:

     (a) Include a feasibility study of the project which complies with the requirements set forth in NAC 242.130;

     (b) Include an estimate of the time and costs of the project;

     (c) Include specifications relating to the information system; and

     (d) Be approved by the Division and the requesting agency before the project may begin.

     3.  The Division will, after completing the request for an information system, submit the service to the requesting agency for its approval. The Division will not release the service to the requesting agency unless the requesting agency signs a statement that the service provided by the Division complies with the requirements of the request.

     4.  The Division will charge the requesting agency for the cost of the services it provides to the agency.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)

      NAC 242.160  Contract between Division and vendor: Procedure. (NRS 242.111)  If the Division wishes to enter into a contract with a vendor on behalf of the requesting agency, it will:

     1.  Review the list of qualified vendors in accordance with the Information System Contracting Standards set forth in section 8 of the Nevada Information Systems Policies and Standards Manual;

     2.  Coordinate the requests for proposals with the requesting agency and the Purchasing Division of the Department of Administration;

     3.  Coordinate and recommend approval of the proposed contract to the Budget Division of the Department of Administration; and

     4.  Manage the project in conjunction with the requesting agency. The Division will be primarily responsible for the technical management of the contract.

     (Added to NAC by Dep’t of Data Processing, eff. 9-16-92)