Embed Size (px)
Citation preview
Implementing a GIS-Based Pavement
Assessment and Management System
Candice Ottley-Francois, GISP, CAPM
GIS Project Manager & Analyst
GIS-T
April 17, 2012
- Challenges & Successes -
Project Overview
Case study using Prince George’s County
Background
Project Phases
Methods
Project Successes
Challenges Encountered
Next Steps
Questions
Agenda
Project Overview
Spearheaded by Prince George’s County DPW&T
Office of Highway Maintenance
Utility Division
Engineering Inspections Services Division
Traffic Safety
GIS
OBJECTIVE: Establish a decision support system for
pavement management
Understand current condition of network Countywide
Develop justifiable projects given limited funding
Project Overview
Pavement Assessment and Management System (PAMS)
Pavement Layer Creation
•Data Conflation
•Pavement Sectioning
Pavement Condition Survey
•Semi -automated data collection
•4,350 lane miles
•Progress Mapping
Pavement Data Analysis
•Raw data analysis
•MicroPAVER analysis
•Reporting
GIS Application Development
•Silverlight Viewer
•Data Management Tools
•Data Analysis Tools
2007 2008 2009 2010 - Present
Phase I Objectives
Determine current condition of County roads
Determine immediate and future maintenance & repair
requirements of County roads
Funding requirements
Countywide vs. District level
Implement PAMS
PAMS Pavement Layer Development
Data Conflation
Requirements driven by MicroPAVER & inspection software
ArcGIS Server editing application for attribute conflation
9 datasets in various formats
County Edge of Pavement
Pre-sectioned
Area readily available
Pavement Sectioning
Unique Pavement ID
Automated section ID assignment
Pavement Condition Survey
Pavement Inspection in Spring 2008
Over 4,350 lane miles
County Maintained Roadway ONLY
Multi-Function Vehicle
Pavement Roughness
Photos – Pavement & Right of Way
Post Processing
Extract distress data from photos
Import to MicroPAVER for assessment
Pavement Analysis & Reporting
MicroPAVERTM Pavement Management System
Developed by US Army Corps of Engineers
PAMS Applications:
Pavement Condition Index
(PCI) determination
Budget Analysis
Reporting
Pavement Condition by
Classification, District
Rehabilitation Requirements and Costs
PAMS Web Viewer
Provides broad access and print functionality of road
network data including PCI scores and photos
ArcGIS Server
Microsoft .NET framework
Silverlight API
Custom map services
Custom photo viewer
Phase I Challenges
Maintaining pavement data
Inspection data outdated
Work History records
Roadway additions/annexations
End user buy-in
Lack of familiarity with GIS and its applications
ArcGIS availability
Learning curve with PAMS components
Budget constraints
Phase I Challenges
ArcView Licensing
Multiple GIS data sources
Limited functionality
MicroPAVER usage
Single user license
User Interface
Multiple data sources
MicroPAVER database
File Geodatabase
ArcSDE for web services
Phase I Successes
Implemented Pavement Management System
GIS feature class identifying 2008 pavement conditions for
entire County
MicroPAVER analysis software
Web Viewer - broad access to condition data and photos
State of Streets Report
Benchmark used to make informed decisions
Identification of “Shovel Ready Projects”
Used to identify candidates for Stimulus Package funding
Phase I Successes
Continued Use of System
Exposure to GIS and PAMS
Custom Training Sessions
Incorporation of PAMS into daily business processes
Schedule A development
Coordination of Utility Activities
Development of reports and maps for upper management
Use of GIS for other DPW&T processes
Snow routing
Street Lighting program
Phase II Objectives
Maintain pavement data in a central location GIS vs. MicroPAVER
Upgrade to ArcGIS 10
Facilitate data management across multiple divisions File geodatabase vs. SDE
Desktop tools vs. web tools
Perform basic condition analysis in GIS
Create projects in GIS Condition
Needs lists
PAMS Database Design
Versioned ArcSDE Oracle database
PAMS feature dataset Pavements FC
Deleted pavements FC
Related Tables Work History: Many-to-Many
Condition (PCI): One-to-Many
Edit log: One-to-Many
Complaints: Many-to-Many
Look up Tables
PAMS Desktop Tools
ESRI Add-In and Extension
Built with ArcObjects
Data Maintenance Tools Pavement ID Management
Work History Management
Edit Tracking Capabilities
Complaints
Data Analysis Tools PCI Management
Project Formulation
PAMS Desktop Components
Set Data Sources
Selected Segments
View Basic Attribute Data
Pavement ID is the unique identifier for MicroPAVER Alpha-numeric
Network ID, Branch ID and Section ID
County managed segments only
Initiate pavement ID generation for new segments Single or multiple segments
Automate pavement ID generation for split segments Manage related records during splits
Pavement ID Management
View Work History
Work History Management
Add new work history
Single or multiple segments
Managed or unmanaged segments
Edit existing work history
Related data management
Many to Many relationship
Propagate data due to pavement edits
Trigger updates to pavement condition (PCI)
Update construction/inspection dates
View PCI Scores
PCI Management
PCI scores were previously derived from MicroPAVER
Update PCI when work history is added or modified
Reset to 100 if Major Work is completed
Update PCI when changes are made to management
Deteriorate PCI annually
View Complaints
Complaints and Inspections
Log citizen
complaints/requests for work
Previously logged in a
spreadsheet and manually
correlated with pavement data
Log Field Visit results
View Edit Log
Edit Tracking
Maintain related tables when changes are made to
pavement segment
Track changes for MicroPAVER
Phase II Challenges
Maintaining MicroPAVER
User Interface not conducive to daily operations
Out of sync with geodatabase
Pavement distress data is outdated
Complexity of system
Work History and PCI components
Changing priorities at County
Budget Constraints
Project Formulation component delayed to the next phase
Phase II Successes
Versioned, enterprise geodatabase established Updates reflected in web viewer
Shapefile to relational geodatabase
GIS Data Maintenance and Analysis Data is current as of April 2012 Added 70 miles of roadway to network
Added backlogged work history data
Identified pavement segments with citizen complaints
Pavement Condition is recalculated in GIS
Major M&R and Preventative Maintenance work programmed using GIS
End user buy-in
Next Steps – Phase III
Identify projects for FY2013
Formulating projects using PAMS geodatabase
Storing as “Proposed” work
Update MicroPAVER database
Biannual event
Automate data transfer between SDE and MicroPAVER
Develop PAMS data migration tool MicroPAVER 7
Generate State of Streets reports using updated data
Biannual reports
FY 2013 Baseline report
Next Steps – Phase III
Perform pavement re-inspection
Obtain updated pavement distress data
Track pavement conditions over time
Refine deterioration formula to better predict future
pavement conditions
Better assess future funding needs
Assess performance of M&R activities
Incorporate roadway project data into ENVISTA
Coordination with other agencies in the region
Next Steps – Phase III
Develop Project Formulation tools
Based on condition (PCI) or complaints
Update PCI algorithm based on new deterioration formula
Provide recommendations of segments for projects
Residential – Assume segments within the same subdivision
Non-Residential – connect sections along length of arterial/collector
Dynamically calculate the cost of projects
Algorithm based on unit costs for rehabilitative processes, area,
percentages for contingencies etc.
Assign fiscal year budget to projects
Track budgets and cap recommendations
Next Steps – Phase III
Web Viewer Updates
Display FY2013 inspection data
Updated PCI scores and photos
Add new themes to display
Work Data – Completed/Ongoing/ Programmed work
Needs List Data
Other DPW&T data
Training
Connect with us…
Web | www.jmttg.com Twitter | @JMTTG LinkedIn | JMT Technology Group Phone | (410) 316-2280 Email | [email protected]
