streamlining workflows with gis - amazon s3...opelika utilities • system overview – governed by...

36
Streamlining Workflows with GIS Streamlining Workflows with GIS Alan Lee, Opelika Utilities Grant Mullins, GISi April 28, 2009

Upload: others

Post on 29-Mar-2020

4 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Streamlining Workflows with GISStreamlining Workflows with GIS

Alan Lee, Opelika UtilitiesGrant Mullins, GISi

April 28, 2009

Page 2: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated
Page 3: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Agenda

• Introduction• Challenges• Solutions• What’s Next?

Page 4: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Opelika, Alabama

Page 5: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Introduction – Site & Situation

• Opelika, Alabama – Railroad Town– Population: 30,000– Customers: 13,000– Near Auburn University– Home of RTJ’s Grand

National Golf Course

Page 6: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Opelika Utilities

• System Overview– Governed by Board of Directors (not a city

department)– Created in 1948– Revenues generated solely by water sales

– 2 Surface Water Treatment Plants– 155 Miles of Water Main– 14,000+ Water Meters– 2,000 Fire Hydrants– 8,000 Valves

Page 7: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Opelika Utilities GIS Overview

• GIS Staff– Project Manager, Alan Lee

• Project Coordinator• Project Inspector – GPS Operator

• Utilizing mapping & GIS technology for over 15 years• Initially utilized Microstation, Geographics and Oracle Database

– Why not ESRI?• Decision Time

– Landbase file was provided by others• Map was moved and stretched to match NAD 83

– Decided to Start Over

Page 8: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Challenge: Starting Over

• What GIS Platform– ESRI Selected – Why?

• Industry Standard• Used by most governmental and related agencies• Training readily available

• Can we do this alone?– Consultant– Other agencies

• Landbase data– City of Opelika– Lee County

• Other utility data

Page 9: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

The Vision…

• Pilot Project– Gain the knowledge and tools to complete our

entire network– A to Z: Data capture thru geometric network

• GPS all water facilities– Meters, valves, fire hydrants, water mains, tanks, etc

• Utilize automated data model and database• Set-up network analysis to isolate mains for maintenance

– Which valves need to be shut – Have ability to trace the affects of isolation

» Who will not have water» What fire hydrants will be out of service

Page 10: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Solution: Custom Data Model

• GISi created a custom data model– Conducted interviews with GIS staff– Started with ESRI’s water utility data model– Added needed feature classes: extended the

standard model• Water model is available online

Page 11: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Solution: Custom Data Model

Page 12: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Solution: GPS Workflow

• Utilized Leica System 1200 GPS (Rover)– Continuous operating reference station

(CORS)– Sub centimeter accuracy, no post processing

• GISi created customized code list within the Leica unit– Provided on-the-fly data entry– Required entry of critical field data

• Real-time GPS data uploaded to geodatabase– Uploaded utilizing ESRI’s Data Interoperability

Tool

Page 13: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Solution: Data Translation - ETL

• ETL tools were created and applied to transform GPS data into the standard model GDB

Page 14: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Solution: Meter Reading

• Wireless meter reading system– New technology results in loss of knowledge

• GIS & GPS captures the knowledge before it is lost– Critical and time sensitive

Page 15: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Solution: GPS Workflow

Page 16: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Solution: System Integration

• Connections to other departmental data sources– Billing system– Hydraulic model– Hydrant flow data– Water quality data

Page 17: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

• Teamwork– Opelika had the domain and business knowledge– GISi had the GIS and technical skills– GISi provided the tools, we did the work– Teamwork resulted in success

Result: Success

Page 18: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Result: Additional Data

• Discovered ways to utilize archived GPS data

Page 19: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

• Leveraged relationships with other agencies– Watershed– Basemap– Planning

Result: External Data

Page 20: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Development Projects

Page 21: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Watershed Hazards Assessment

Page 22: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Impervious Surface Analysis

Page 23: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Record Drawing Access

Page 24: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Water Quality Sample Sites

Page 25: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Watershed Stream Buffers

Page 26: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Service Areas

Page 27: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Comprehensive Plan

Page 28: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Challenge: Hydrant Flow Testing

• Hydrant Flow Test Data– Needed by Opelika Utilities

• Data used in Hydraulic Modelling• Data provided to engineers

– Collected by Opelika Fire Department• Paper-Based• Slow Turnaround• Inconsistent Entry

Page 29: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Solution: Web GIS

• Enterprise GIS Implementation– ArcGIS Server– ArcSDE

• Web Based Flow Entry• Mobile Based Flow Entry

Page 30: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Web Solution

• Web application created for flow data entry– ArcGIS Server 9.3 Application

• Rich Internet Application• Built on the ArcGIS API for Flex• Custom web service• SQL Based Security

– Flow Entry Module• Data entered and stored into SQL database• Realtime availability to web and mobile users

– Routine Maintenance Module• Maintenance requests entered and stored into SQL

database

Page 31: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Web Based Flow Entry

Page 32: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Mobile Solution

• Mobile Application for Flow Entry– ArcGIS Mobile Application

• Windows Mobile application• Real time connectivity via Cell Network• Using same custom web service as Web App

– Flow Entry Module• Data entered and stored in SQL database• Edits are pushed back continuously

– Routine Maintenance Module• Maintenance requests can be entered in field

Page 33: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Mobile Solution

Page 34: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

What’s Next

• Cityworks Implementation• Water Plant GIS Modeling• Water Quality Mobile Application• ???

Page 35: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Acknowledgements

• Opelika Utilities– Alan Lee & Staff– (334) 705-5527– [email protected]

• Geographic Information Services, Inc. – Booth 218– Grant Mullins– (205) 941-0442 ext.35– [email protected]

Page 36: Streamlining Workflows with GIS - Amazon S3...Opelika Utilities • System Overview – Governed by Board of Directors (not a city department) – Created in 1948 – Revenues generated

Questions?