|
1
|
- Ryan R. Johnson
- March 8, 2006
|
|
2
|
- DigSmart Basics
- Operational Overview
- Reporting
- Data Preparation/Implementation
- Implementation Issues
- Future of DigSmart
|
|
3
|
|
|
4
|
- 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
|
|
5
|
- 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
|
|
6
|
- 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
|
|
7
|
- 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
|
|
8
|
|
|
9
|
- 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
|
|
10
|
|
|
11
|
|
|
12
|
|
|
13
|
|
|
14
|
- 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
|
|
15
|
|
|
16
|
|
|
17
|
|
|
18
|
- The DigSmart system is installed with 5 reports, plus an export option
- Volume
- Company
- Type of Ticket
- Ticket Status
- Street Name
- Ticket Report
|
|
19
|
- Additional reports can be created within Crystal Reports
- Data is stored in SDE tables, and field documentation is available
|
|
20
|
- Date/Time Comparison
- Tickets by District
- Tickets Closed by District
- Tickets by Township
- Emergency Tickets Processed
- Emergency Tickets – Time to Be Processed
|
|
21
|
|
|
22
|
- The DigSmart system is essentially a turn-key solution, although some
data preparation and planning is required of end users
|
|
23
|
- 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
|
|
24
|
|
|
25
|
- 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
|
|
26
|
- 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
|
|
27
|
- Determine Buffer Size
- Determine Geocoding Requirements
- Composite Geocoder
- Right of Way Addresses
- Parcels
- Street Centerlines
|
|
28
|
|
|
29
|
- Determine Process and Responsibilities
- Personnel Training and Adjustment to a New System
- DigSmart Configuration and Modification
- Data Selection/Creation
|
|
30
|
|
|
31
|
- 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
|
|
32
|
|
Notes
