Text Size:   A+ A- A   •   Text Only
Site Image
OAR Development - GIS Software Standard

  • Why is DAS establishing an Enterprise GIS Software Standard?
Oregon Revised Statute (ORS) 291.038 directs the Oregon Department of Administrative Services (DAS) to develop and establish information resources and information technology standards, including standards for software utilized by Oregon state agencies.
In this context information resources means: media, instruments and methods for planning, collecting, processing, transmitting and storing data and information, including telecommunications, which includes Geographic Information Systems (GIS) software.  Information technology means, but is not limited to all present and future forms of hardware, software and services for data processing, which includes GIS software.
  • Why is DAS establishing this Enterprise GIS Software Standard via an Oregon Administrative Rule (OAR)?
Oregon Revised Statute (ORS) 291.038 requires DAS to adopt standards by administrative rule.
  • Why is DAS proposing the establishment of ESRI as the state’s Enterprise GIS Software Standard?
DAS is proposing the establishment of the Environmental Systems Research Institute, Inc (ESRI) scalable suite of software applications as the state’s Enterprise GIS Software Standard because DAS believes that action will enable the most integrated, economic and efficient acquisition, installation and use of GIS software by Oregon state agencies.  DAS believes a compelling set of information resource management benefits (people, process, and technology) can be gained by adopting this Enterprise GIS Software Standard due to the:
(a) Current installed base of GIS software and trained expertise within state agencies.
(b) General technical benefits associated with the use of standardized software, including but not limited to:
  • Simplified software and application infrastructure configurations.
  • Ease of software installations and upgrades.
  • Simplified application connectivity, security and data distribution architectures.
  • The capacity for simultaneous multi-user editing, dataset versioning, and history retention.
  • The ability to utilize existing geospatial business intelligence to ensure data integrity and consistency via the establishment of topology rules, data attribute domain rules, and data validation rules.
(c) Enterprise-oriented data and application accessibility offered by the use of common GIS software deployed across state agencies.
(d) Enhanced functionality and interoperability of related software components within a suite of software applications including the reduction of costly data translations between diverse software products and the ability to leverage data modeling and processing efforts for reuse between agencies.
(e) Ease of sharing geospatial data among agencies and with the public based on a common GIS software infrastructure.
  • How are "GIS" and "GIS Software" defined within the proposed OAR?
For the purposes of this rule:
(a) “GIS” means geographic information systems which comprise the hardware, software, network, data, and human resources involved in creating, maintaining, managing, and distributing data, information, and knowledge about spatial objects and their relative positions in the human and natural environment.
(b) “GIS Software” means computer-language coding created specifically to facilitate the creation, management, distribution, accessibility, and promulgation of Spatial Data. For the purposes of this rule, “GIS Software” does not mean computer-language coding used for the purposes of computer aided design (CAD), simple address list management or similar business processes unless the purpose is to establish inter-agency Spatial Data.
(c) “Spatial Data” means digital information that identifies the geographic location of features and boundaries that are usually stored as coordinates and topology that can be mapped or used for comparative spatial analysis.
  • Does the OAR apply to local governments, other non-state agencies or private sector entities doing business in Oregon?
No.  The OAR applies only to Oregon state agencies. 
For the purposes of this rule,  “State Agency” or “Agency” means every state officer, board, commission, department, institution, branch or agency of the state government, whose costs are paid wholly or in part from funds held in the State Treasury, except:
(a) The Legislative Assembly, the courts and their officers and committees;
(b) The Public Defense Services Commission;
(b) The Secretary of State and the State Treasurer in the performance of the duties of their constitutional offices;
(d) The State Board of Higher Education or any state institution of higher education within the Oregon University System; and
(e) The State Lottery.
  • Will state agencies who utilize non-standard GIS software be required to purchase ESRI software products?
No.  The proposed OAR does not mandate the purchase of ESRI software products by state agencies who currently utilize non-ESRI software.   Further, the proposed OAR includes an exception process that recognizes the existence and potential persistence of non-ESRI legacy software use and that a business rationale may exist for future state agency investments in non-ESRI GIS software.
  • Can state agencies continue to use or purchase non-standard GIS software?
Yes.  By following the exception process outlined within the proposed OAR.
  • Who can grant or deny an exception request?
The State Chief Information Office or his/her designee.
  • How do I get a copy of the proposed OAR and other documents that were submitted to the Secretary of State?
Draft Administrative Rule (pdf)
Hearing Notice (pdf)
Need and Fiscal Impact (pdf)
  • What process is being used to establish the OAR?
Administrative Rulemaking is proscribed by Oregon law, specifically the Oregon Administrative Procedures Act (Oregon Revised Statute, chapter 183).  Administrative rules adopted by state agencies are published by the Administrative Rules Unit, Archives Division, Secretary of State, and can be accessed electronically via the Archives Web site (http://arcweb.sos.state.or.us/).  Rulemaking overview and checklist documents are also available at the Archives Web site.
  • What is the Rulemaking Timeline?
OAR Rulemaking Timeline (pdf)

  • How do I provide comments or other feedback about the proposed OAR?

Comments and feedback on the proposed OAR are welcome using three different methods:
  1. Send written comment to: Cheryl Knottingham, DAS Operations Division, 155 Cottage St. NE, U90, Salem, Oregon 97301
  2. Send written comment via e-mail to: cheryl.knottingham@state.or.us
  3. Present oral comments at the hearing scheduled for 9:30 to 11:00 a.m., Thursday, September 27, 2007, in the Fishbowl Room, Revenue Bldg.,955 Center St. NE, Salem, Oregon.

Written comments are welcome until 5 p.m., Thursday, September 27, 2007, the same day as the hearing.  At that time the public comment period will end.

Please cc: our Division Policy/Rule Coordinator on comments or feedback you may submit:

Scott Riordan
Enterprise IT Policy Coordinator
IT Investment and Planning Section
Enterprise Information Strategy and Policy Division
Department of Administrative Services
955 Center Street NE, Room 470
Salem, Oregon 97301
Phone: 503.378.3385
Email: scott.riordan@state.or.us