Logo GISdevelopment.net

GISdevelopment > Proceedings > GITA > 1997


GITA 2002 | GITA 2001 | GITA 2000 | GITA 1999 | GITA 1998 | GITA 1997
Sessions

Advanced Technical Topics

Building & Supporting Applications

Business Evolution & Platform Migration

Expanding the User Base -- Non-Traditional Applications

From the office to the Field

Fundamental & Economic Issues of AM/FM/GIS

Lessons Learned

Major Technology Trends and their Impacts

Project Planning, Implementation and Management

Re-Engineering and Integration Issues

Scada and Real-Time Systems

User Project Presentations

Best of the Rest

Invited Presentation


GITA 1997


From the Office to the field
Printer Friendly Format

Page 1 of 2
| Next |


Empowering Field Crews with AM/FM

Wayne Homer
City of Tallahassee Utility Services GIS
2602 Jackson Bluff Road Tallahassee, FL 32304


The City of Tallahassee Utilities Services GIS is responsible for the implementation and support of the Utility Enterprise GIS Database. We provide application development and support for Electric, Water, Sewer, Gas, Stormwater Management, and Solid Waste Operations. We serve over 90,000 electric, 62,000 water and sewer, 54,000 solid waste, and 16,000 natural gas customers.

Historical Information
ln 1985 Hurricane Kate came through Tallahassee and devastated several sections of town. The City’s Electric Department estimated system damage to be approximately $900,000. When the reconstruction was complete, the cost totaled over $2.9 million. This underestimation was primarily due to the lack of adequate system maps and facility inventory information. In 1988 the Electric Department began investigation of AM/FM/GIS technology.

The City of Tallahassee, Leon County, and the Leon County Property Appraiser formed an Interlocal Agreement in 1989 to share costs in the development of a common GIS. A central GIS group was formed to develop the base map so the various Interlocal participants could begin data conversion and develop their respective GIS data sets and applications.

Base Map Creation Timeline

1986: A fly over to produce dxf vector data was completed. Map layers consist of planimetric and topo.
1990: Interlocal selected GIS vendor and began to design the common GIS
1991: Edgematching of dxf files to knit fly over data into a seamless database
1991: Began Parcel map conversion with external contractor
1992: Interlocal staff underestimated effort to perform adequate quality control on Parcel
data. A new in house parcel conversion effort is currently underway with completion estimated in 1998.
1993: The base map data was finally consolidated on one system.
1994: Due to lack of parcel data and the poor condition of existing electric maps, the Electric departm-ent began to develop the MDCS (mobile data collection system) concept and ramp up for a field inventory.
1996: New Digital Ortho Photo (DOP) effort to replace the 1986 base data.
1997: DOP vector data available

Existing Electric Data - Single line Drawings
In 1990 the Electric Department had limited data to load into the GIS. The existing paper maps for overhead and underground facilities were drawn on parcel maps, which were sometimes not to scale and out of date. Index cards for transformers and other electric facilities had no coordinate location information to tie them spatially to the GIS. Most of the available information was unsuitable for classic data conversion methods such as digitizing or scanning. These circumstances led us to re-think the data development of the GIS project and elect to proceed with a field inventory. This inventory is estimated to require about 2 years of field work with an outside vendor at a cost of over $1 million.

One thing that could be done in the short term was to digitize the single line drawings (SLD) into the GIS and begin using the GIS as a map production system to maintain and print map books for the service vehicles.

We developed a SLD graphic and data maintenance tool to edit and update the SLD data in the GIS. The overhead facility drawings were entered into the GIS by eye-balling the line work as close as possible to base map features. This was not spatially accurate, but would give us GIS map data that was at least as accurate as the existing paper maps. The resulting data would display the SLD features on the correct side of the street and display circuit types. This new SLD data would not only replace the old map books in the vehicles, it would also help familiarize our users with GIS and its capabilities. By adding the SLD information to the database we could begin using the GIS immediately, and have some data to begin application development and testing.

Utility Enterprise Database and GIS Requirements
One of the main requirements of the Utility Enterprise Database (UEDB) is to provide field and service personnel with current facility and electric system information. This will enhance customer service, restoration response, and provide for cost effective facilities maintenance.

We believe the solution to building a successful UEDB requires 4 basic components.
  1. Seamless All Relational GIS Database
  2. GIS Maintenance Tool
  3. Work Order Management System
  4. Mobile Data Collection Tool
Utility Enterprise GIS Database
In a non-digital mapping environment there is a problem with duplication of data sets. We have chosen to develop a single Utility Enterprise Database (UEDB) on an all relational seamless model. A single UEDB is required to eliminate the problems of the proliferation of duplicate data sets. All facility information is maintained through a single user interface. By using a single all relational system we have addressed the issues of data integrity, the real location of the most current data, and have helped ensure user confidence in the database. Additionally, we have multi-user real time concurrent access to information for all Utilities on the same system.

Page 1 of 2
| Next |

Applications | Technology | Policy | History | News | Tenders | Events | Interviews | Career | Companies | Country Pages | Books | Publications | Education | Glossary | Tutorials | Downloads | Site Map | Subscribe | GIS@development Magazine | Updates | Guest Book