Click for next page ( 12

The National Academies of Sciences, Engineering, and Medicine
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 11
Introduction 11 goals. Procedures are outlined that incorporate the unique characteristics of your agency, including the technical environment in which your agency operates and your agency's plans to accommodate technological change. Important considerations for using the guide include the following: Pay particular attention to getting started and achieving buy-in. This process includes gener- ating awareness and support in upper levels of the agency, enlisting a champion, obtaining funding, establishing a task force, and deciding whether the agency will develop the system on its own or in partnership with others. Develop a clear understanding of the ultimate concept for the system. Different aspects to consider include defining the enterprise and identifying where in the process your agency is. Understand requirements for bringing a new system into your agency and work with your information technology (IT) office to meet these requirements while also meeting your needs and goals. Identify where your agency has evolved toward the ultimate concept, identify a path to develop and implement the desired concept, and set short-term and intermediate implementation goals. Carefully consider the information on system design, development, implementation, operations, and maintenance, including use of best practices for life cycle management of systems and software. Understand that content management is crucial to system success and that data and information must be properly managed over its life cycle. The most important thing to keep in mind is that this process is not linear. Throughout and particularly at the beginning, you will reassess, redefine, and restructure. This is an important aspect of successfully implementing any system based on current technology since a technology's half-life is generally less than the time necessary to follow agency policies to implement that technology. The process for implementing an information management system has been well defined in the literature for general business applications (Marks and Bell 2006, Harmon and Anderson 2003) and for different activities within transportation agencies (Booz and Baker 2003, Zhang et al. 2002). Organization of the Implementation Guide The remainder of the guide is organized according to the activities summarized in Table 2, which provides a summary of generally accepted steps. The order of these steps and substeps is not prescriptive and should be performed according to the culture of the agency. Where applicable, the guide explains how the 8-55A logical model can be used or how it fits into the implementation process. At the end of the guide are a list of references that were explicitly cited in the guide and the appendices, a list of acronyms and abbreviations, and a list of standard terminology from FHWA's Project Development Guide with some alternative terminology that was identified during NCHRP Project 8-55A. The following additional information is provided on the NCHRP Report 695 summary web page ( Appendix A: Two executive summaries designed to highlight why and how to implement a geospatially enabled information management system. Appendix B: A guide on how to use the 8-55A logical model, which includes a description of the model and guidance on how to use it as a starting point in your system development. Appendix C: UML diagram documentation of the complete 8-55A logical model. Appendix D: 8-55A logical model data model. Appendix E: Annotated bibliography of documents that could be helpful.

OCR for page 11
12 Guide for Implementing a Geospatially Enabled Enterprise-wide Information Management System Table 2. Summary of implementation process. Activity Steps 1 Recruit a champion 2 Obtain leadership, stewardship, management support Building Support: 3 Appoint an initial working group Chapter II 4 Establish linkage to agency performance measures and goals 5 Research related efforts (internal and external) 1 Define your enterprise 2 Identify needs Assessing Your 3 Identify use cases Requirements: Chapter III 4 Review business processes 5 Evaluate best practices for incorporation 6 Review legal and regulatory requirements 1 Assess existing right-of-way systems 2 Identify existing database structure(s) Assessing Your Capabilities: 3 Identify existing geospatial capabilities (GIS tools) Chapter IV 4 Identify related existing information systems 5 Assess current policies for IT deployment 1 Define type of system 2 Determine a starting point 3 Define data structure Defining the System: 4 Define geospatial capabilities Chapter V 5 Define document management 6 Define reporting requirements 7 Define links to other systems Developing an 1 Identify phasing options Implementation Plan: 2 Evaluate feasibility Chapter VI 3 Develop timelines with milestones 1 Confirm/revise requirements 2 Secure resources 3 Develop detailed design 4 Develop test plan Implementation: Establish procedures for configuration management-- Chapter VII 5 Versioning 6 Develop software 7 Develop training plan 8 Train users