Click for next page ( 33


The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement



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 32
CHAPTER VI Developing an Implementation Plan If you have the resources and commitment to implement your system in a single phase, you can skip the next section. Often, however, you are constrained by resources or having to coordinate with other efforts necessary to support right-of-way activities, such as development of the necessary geospatial layers, i.e., statewide parcel layers. Depending on the reason for phasing your implementation, you will need to determine the appropriate functionality to assign to each phase. If you are coordinating with another effort, you should structure your phases such that one phase consists of the coordinating functions while the other(s) consist of functions that are mostly independent. If you are constrained by resources, you will probably want to group functions by enterprise-wide functionality--data management, document management, geospatial enablement, expanded reporting--rather than by functional area--appraisal, acquisition, etc. Phasing Options Because of the interconnectedness of information in right-of-way offices, an information management system should cover all the functions of the office when it is implemented. However, there are some strategies for this implementation that allow you to phase in some aspects, such as adding geospatial capabilities or electronic document management, after the system is in place. Similarly, modules or tools that improve how certain aspects are performed, such as a contract management module for lease agreements, can be added later. When you perform your capabilities assessment, you will identify what your agency already has and the environment that exists for local versus centralized and distributed systems. Based on this assessment, you will decide which of the following strategies to follow: Local information management system--This system would consist of a database and the front-end software on a desktop computer or server on a local area network (LAN) that supports staff activities including data access and entry, document generation, and reporting. This configuration would potentially require coordinating the data from different locations. However, given the current state of technology, this strategy would probably be used only if the agency does not yet have an enterprise database system that is accessible throughout the agency. Centralized information management system--This system would consist of an enterprise database system and either an Internet-based front end or locally installed front end that accesses the database through the Internet/intranet. This configuration is probably the most common for systems that have been implemented over the past decade or are under design. Distributed information management system--This system would consist of one or more distributed enterprise database systems, an Internet-based front end, and access to other 32