Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.
Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.
OCR for page 28
28 Guide for Implementing a Geospatially Enabled Enterprise-wide Information Management System · Accessibility standards compliance · Use of non-proprietary/portable software code, such as Java or .Net, where possible. Other factors you should consider in defining your system include the following: · Every agency starts at a different point in the development process and approaches that process differently. · Building a system using internal resources has different constraints and requirements than working with a consultant to build a system. · Where your agency is with respect to the use of technology and willingness to embrace new approaches, hardware, and software will impact how you move forward. Starting Point Although not exhaustive, the following cases present some common starting points: I. Your office does not have centralized information management capability and is developing a full geospatially enabled enterprise information management system or is totally replacing an existing system that is no longer responsive to current needs. II. Your office wants to add geospatial capabilities to an existing enterprise information management system. III. Your agency has an enterprise geospatial capability (a GIS warehouse, agency-wide geo- database, or geospatial data service) and you want to incorporate it into your information management system. In this case, the term enterprise indicates the ability to access geospatial data through the Internet/intranet. Case I For the first case, you are starting, more or less, from scratch. This case gives you the most flexibility. Following the guidance provided in Appendix B, you can use all or part of the 8-55A logical model as the backbone to build your system. If you are creating your own business processes, you have the ability to extract activities from the model with their corresponding components to incorporate in your process. Case II The second case is a common condition for states that have an information management system in place. The 8-55A logical model provides a specific component that includes just the geospatial functionality, called "geospatial decision making activities" (GDMA). Although it is impractical to provide a step-by-step link from this model to an existing information management system, the structure clearly identifies the data necessary to support status tracking and activities that could benefit from geospatial analysis. These data elements and activities are connected back to the overall model in the 8-55A logical model so that the source is identifiable for inclusion in your system design. Case III The third case can be considered from two perspectives. One perspective is similar to the first case in that you are designing your system and linking to the agency geospatial system. As with the first case, you will work closely with the manager of the GIS data to provide the appropriate connections from the data to your functionality. The second perspective is from