The Requirements Analysis serves as the overall project framework by defining who the users will be, what applications are suitable for immediate implementation by the GIS, and what GIS data and base mapping requirements are needed to support those applications. The Requirements Analysis provides an initial understanding of the level of effort and realistic schedule required to implement the GIS environment envisioned by users. The document forms the initial framework for a common understanding between the client and the consultant in terms of breadth and scope of the envisioned GIS system.
Following the Requirements Analysis, it is possible to acquire the appropriate base map, select and purchase GIS software and hardware, develop detailed system architecture designs for user applications and data bases, write the applications, and convert the data. None of the tasks can be accomplished nor can the level of effort associated with the tasks be determined until the Requirements Analysis has been completed and some of the initial design and data structure has been investigated. From the analysis of the GIS related functions within an organization, it is then possible to define the GIS applications categories. Clear definition of these categories will allow an identification of the requirements of the system for the data, hardware and software, and network configuration and specification. In other words, the applications drive the system. Many organizations under pressure from the hardware and software vendors invest immensely on the technology without even knowing their needs and requirements. They are oversold regarding the capabilities of the technology. When reality sets in, organizations find that they have spent a lot, but have nothing to show for those expenses except for hardware and boxes of software sitting on the shelves.
In this presentation I will address the following topics that cover from the definition of a GIS to its final successful implementation. I will try to portray a true picture, the good, the bad and the evil, based on my 20 years of hands on experience in the GIS field. The attendees will get a clear understanding of GIS technology, will get a taste of reality and will learn about doing it the correct way. My presentation will cover the "Ways to success" and will also point out the traps and miss-conceptions about the technology.
A Proven Approach to a Successful GIS Implementation:
- What is a GIS?
- Why A GIS?
- Components Of A GIS
- Is There A GIS In Your Future?
- Planning The Next Step
- Requirements Analysis: What should be in a Requirements Analysis?
- Organizations' goals and objectives
- Analysis of current practices, problems encountered and redundancies
- Organizational issues - management structure, resources, staff training
- Applications
- Base map requirements
- Conceptual data base design
- Hardware and Software requirements
- System integration
- Cost of GIS implementation- applications development, data conversion, hardware, software, resources, training, update and maintenance
- The Strategic Implementation Plan
over a period of 3-5 years
- Implementation
- Base map development
- Geodetic monumentation
- Map scales, accuracy, projections
- Operational standards and procedures
- Hardware and software acquisition
- Organizational setup, staffing
- Management and staff training
- System Design and Database design
- Applications development
- Data conversion
- Data, map, hardware and software maintenance
- Metadata standards
- Key issues need to be addressed
before implementation
- New Technologies- Looking into the future
Just as Delhi was not built in one day, neither was the "Accounting System" that prepares your paycheck regularly once a month, with proper deductions, taxes, etc. (almost flawlessly). Similarly, a GIS system can not be built in one day. The design, development and implementation of a multi-user, enterprise-wide GIS in an organization are complex undertakings. Full implementation of a GIS will take a long period of time. Depending on the size of the organization it may require 3 to 6 years. In order to keep the enthusiasm alive, you need to plan a "Phased Approach" to ensure successful GIS implementation. In each of these phases you must achieve "incremental victories". Instead of waiting for three to four years for a complete system implementation, applying the phased approach, you should be able to develop GIS applications early on so that the program is rapidly able to demonstrate results - even before full conversion of all data is complete.