indianapolis/marion county gis & digsmart ryan r. johnson march 8, 2006

Post on 29-Dec-2015

213 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Indianapolis/Marion County GIS & DigSmart

Ryan R. Johnson

March 8, 2006

Overview

DigSmart Basics Operational Overview Reporting Data Preparation/Implementation Implementation Issues Future of DigSmart

DigSmart Basics

DigSmart Basics

DigSmart is an extension to ArcMap, designed to automate utility locates, or the “Call Before You Dig” process

DigSmart is produced by Bergmann PC, Inc. of Rochester, NY, winner of the 2005 ESRI Business Partner of the Year award

Benefits of DigSmart Electronic ticket processing Digital maps showing the utility location and

the ticket information on the same screen The ability to zoom to and measure the

exact location of each ticket, improving accuracy and efficiency

Graphically represent linear address ranges

Benefits of DigSmart Creating work orders directly from the

map Consolidated ticket management and

reporting Adding overlay data to perform analysis Emergency ticket notification via cell

phone and on the local PC Field Client Module for ticket updates

from the field

DigSmart and Marion County

The City of Indianapolis/Marion County purchased DigSmart for use in the Department of Public Works

The system is currently used to automate Sanitary and Storm Line locates

Implemented in August 2005

Operational

Overview

DigSmart Operation Requests originate at the Indiana

Underground Plant Protection Service (IUPPS) call center

The locate request is sent via e-mail to the DigSmart system

DigSmart system parses data from the e-mail, geocodes the address, and determines if a locate is required

System administrator is notified of emergency locates via cell phone

Sample IUPPS E-mail

IUPPS Data Imported Ticket Info Window The Ticket Info

Window is dockable, and the data can be edited

It includes all relevant data from the IUPPS e-mail

DigSmart Toolbar

Ticket download and navigation

Historical ticket retrieval

Location editing Reporting

Sample PDF Locate Document Sent as an e-mail

attachment to the appropriate coordinator

Contains contact and locate information, description of the job and duration, and geographic data

Currently printed and taken to the field

DigSmart Operation Locates are performed, and the

status is updated in the database via a Field Application Module

The updates are currently processed by a single dispatcher, but could potentially be updated in the field and synchronized with the SDE database

DigSmart Field Module

Process Review

2. DigSmartProcessed

4. SystemUpdated

1. LocateRequest

To IUPPS

3. FieldLocate

Reporting

DigSmart Reports

The DigSmart system is installed with 5 reports, plus an export option Volume Company Type of Ticket Ticket Status Street Name Ticket Report

Additional Reports Additional reports can be created within

Crystal Reports Data is stored in SDE tables, and field

documentation is available

Additional Reports

Date/Time Comparison Tickets by District Tickets Closed by District Tickets by Township Emergency Tickets Processed Emergency Tickets – Time to Be

Processed

Data Preparation

and Implementati

on

System Preparation

The DigSmart system is essentially a turn-key solution, although some data preparation and planning is required of end users

DigSmart Data Preparation Determine the geographic areas of

support and the responsible parties The service area was divided into 11

DigSmart Districts, by consolidating zip code polygons

The initial districting was based upon population and geographic dispersion

DigSmart Districts

DigSmart Data Preparation

Once the districts were determined, a new Storm and Sanitary layer was created for each district The DigSmart system requires a separate

layer for each district, in order to e-mail specific coordinators

DigSmart Data Preparation

Additional Layers Once the districts and utilities for locates are

determined, additional relevant layers can be added Storm Sewer Structures Sanitary Sewer Structures Street Centerlines Parcels Buildings Traffic Signal Boundaries

DigSmart Data Preparation

Determine Buffer Size Currently set to 100’

Determine Geocoding Requirements Composite Geocoder

Right of Way Addresses Parcels Street Centerlines

Implementation Issues

Implementation Issues

Determine Process and Responsibilities

Personnel Training and Adjustment to a New System

DigSmart Configuration and Modification

Data Selection/Creation

Future of DigSmart

Future of DigSmart Increase number of DigSmart

Field Module licenses to allow for updates to be made directly from the field

Use historical data and density analysis, along with employee feedback, to revise DigSmart Districts

Add additional utilities for locates

Thanks!

Questions?

top related