Government Technology

    Digital Communities
    Industry Members

  • Click sponsor logos for whitepapers, case studies, and best practices.
  • McAfee

Fire Hydrant App Improves Workflow in Philadelphia



A fire hydrant.

August 12, 2013 By

Philadelphia’s process for managing damaged fire hydrants was brought into the digital age late last year with a new reporting app. The city’s Fire Department now transfers data about the condition of hydrants from the new app through mobile data terminals (MDTs), cutting down on processing time and saving money.

The city previously spent $17,000 per year to print out manila survey cards used to notate the condition of the city’s 27,000 hydrants. The cards were given to the Water Department, which spent about a week to manually enter the information into a database. Thanks to the app, the extra data entry step has been eliminated, allowing the Water Department to schedule hydrant repairs sooner.

The JavaScript-based ArcGIS application enables the Fire Department to enter hydrant data once, and it is transferred on a daily basis to the Water Department’s database. According to Charles Zitomer, director of field operations for the Water Department, both departments had been talking about a more modern solution that improved the data entry process for years.

The hydrant application was conceived and developed through inter-departmental cooperation and a strong foundation in GIS.

“We developed a GIS system for our infrastructure that was very, very good,” Zitomer said. “Very accurate, reviewed and scrutinized, and we staffed a GIS team to maintain that database and come up with maintenance procedures and protocols to make sure our GIS system was more and more accurate every day. We then leveraged that GIS system with all our infrastructure for various applications – hydraulic modeling of the system, some security concepts of the system.”

Zitomer added that a hydrant going out of service is a big deal, because it creates a safety hazard to the city. Once the city discovers a hydrant is out of service, the repair goes to the top of the Water Department’s to-do list.

“We have developed strong and good technology and really we’re going to find out about hydrant defects quicker, at a lower cost and really provide a better service to the citizens of Philadelphia in terms of fire protection,” Zitomer said.
 
Development Details

The app took about three months of work to develop. The project began in October 2012 and was finished around Christmas, but additional time was needed to get things configured on the back end, said Grant Ervin, public safety GIS program manager for the city. Ervin explained that the operational gains from the project are hard to quantify, but there are a lot of fringe benefits from digitizing the system and having data on the hydrants on one map.

“When [the Fire Department goes] out to do inspections, they’re not missing anything,” Ervin said, adding that there are no scraps of paper to get lost. “They’re not having to go out and look where they already were. It’s all in the system.”

Philadelphia uses Cityworks, a GIS-centric asset management solution, which was helpful during the project, according to Edward Schaefer, executive assistant for the Water Department. He said the solution is “pretty much an open database” that is easy for the city to connect to, write work orders, service requests, and inspections from outside applications.

Schaefer added that 311 is the next integration for Philadelphia which could help speed up the hydrant repair process. The city’s existing 311 system is already connected to their work order process, but a 311 app could provide another way to speed up the hydrant repair process. For example, if a car backs over a hydrant, a 311 mobile app user could report it and the Water Department would usually verify the report in the same day.


| More

Comments

Add Your Comment

You are solely responsible for the content of your comments. We reserve the right to remove comments that are considered profane, vulgar, obscene, factually inaccurate, off-topic, or considered a personal attack.

In Our Library

White Papers | Exclusives Reports | Webinar Archives | Best Practices and Case Studies
Digital Cities & Counties Survey: Best Practices Quick Reference Guide
This Best Practices Quick Reference Guide is a compilation of examples from the 2013 Digital Cities and Counties Surveys showcasing the innovative ways local governments are using technological tools to respond to the needs of their communities. It is our hope that by calling attention to just a few examples from cities and counties of all sizes, we will encourage further collaboration and spark additional creativity in local government service delivery.
Wireless Reporting Takes Pain (& Wait) out of Voting
In Michigan and Minnesota counties, wireless voting via the AT&T network has brought speed, efficiency and accuracy to elections - another illustration of how mobility and machine-to-machine (M2M) technology help governments to bring superior services and communication to constituents.
Why Would a City Proclaim Their Data “Open by Default?”
The City of Palo Alto, California, a 2013 Center for Digital Government Digital City Survey winner, has officially proclaimed “open” to be the default setting for all city data. Are they courageous or crazy?
View All