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 33
Developing an Implementation Plan 33
applications and systems both inside and outside the agency through desktop, notebook,
handheld, or other mobile computing devices. If interagency agreements are in place to allow
it, your system could seamlessly access tax records directly from the source or business data
for relocation planning, etc.
To include geospatial enablement, you also have several strategies:
· You include it in the initial design and implementation--The geospatial functionality is
included in the use case and business process models and the data are included in the data
architecture. The geospatial capability can be built into the system or linked to an external GIS
software package.
· You have an existing information management system and you want to add geospatial
enablement--The 8-55A logical model includes specific locations in the model where data are
obtained from or entered in the system as well as activities that could be geospatially enabled.
You would identify these areas in your system and expand the capability to provide the necessary
functionality.
· You have access to an enterprise GIS and want to incorporate it into your information
management system--As with the previous strategy, the 8-55A logical model provides specific
data locations where data are obtained from or entered in a system. Linkages to the GIS would
be included in the system design.
Two possible options for adding a GIS are porting the appropriate information to an existing
GIS package or programming geospatial capabilities within the information management system.
The first approach would establish a method of passing information between the system and GIS
software. If staff members are familiar with GIS, they could then use it as desired. If they are not,
you could include a macro to perform the desired GIS functionality in the GIS software. The GIS
can be launched from within the information management system or as a separate application.
The second approach is to build the GIS functions in the system either by using the GIS software
application programming interface (API), which allows you to use the functionality of the
software but in the system interface without the overhead of the complete GIS package, or by
programming the geospatial capabilities directly in the system. It should be noted that there are
GIS software packages that are designed to support land management and can be modified to
meet the information management needs of your office.
Feasibility
You will need to determine the feasibility of implementing the various components of your
system. If you determine that implementation of a component is not feasible for some reason,
you will need to find a strategy to overcome the difficulty or barrier or pursue a redesign that
does not require that component. The following types of feasibility should be considered:
· Managerial
· Organizational
· Staffing and other resources
· Technical
· Financial
Implementation Timeline and Milestones
Once you have decided whether you will need to phase your implementation, you will want
to develop a schedule that shows each phase and the major milestone that will be achieved in the
short, mid, and long term. Using a Gantt chart or other project management software to lay out
OCR for page 34
34 Guide for Implementing a Geospatially Enabled Enterprise-wide Information Management System
the major implementation activities within the schedule will help you and the developers stay on
track. This schedule will also help to control project creep once development has started because
not only does creep affect the cost but also deadlines. Activities should include the following:
· Implementation of major layers or modules of the system
· Actions to secure resources for implementation including funding, staff, consultants, hardware,
and software
· Actions associated with software development, testing, and implementation
· Training
