My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
03/13/2017 City Council Agenda
COE
>
City of Eugene
>
Public Meetings
>
CMO
>
2017
>
03-13-2017
>
03/13/2017 City Council Agenda
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/10/2017 9:26:29 AM
Creation date
3/10/2017 9:18:58 AM
Metadata
Fields
Template:
City Council
City_Council_Document_Type
Agenda
CMO_Meeting_Date
3/13/2017
CMO_Effective_Date
3/13/2017
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
251
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
PAVEMENT MANAGEMENT SYSTEM <br />A Pavement Management System (PMS) performs analysis of collected rating data and reports <br />on the current and projected conditions of the street system. In addition, it is used to evaluate the <br />effectiveness of planning and funding priorities, and provides guidance in the decision making <br />process. The goal of the decision making process is to prevent pavement failures through <br />judicious maintenance. <br />City of Eugene implemented MicroPaver in 2013. MicroPaver combines visual field inspection <br />ratings, compiled under strict criteria, with computer tracking and condition analysis. Beginning <br />in 2010 the rating methodology was revised to the WDOT's Extended (WSEXT) method, <br />collection of deterioration values by area, lineal footage thus keeping the program consistent <br />with industry standards. This also allowed for smoother transition to MicroPaver with the ability <br />to migrate three years of rating data with some modifications. With this migrated condition data, <br />rating the entire asphalt street system the last three years plus construction history we are able to <br />perform an analysis with rational accuracy to report financial needs and road conditions. There <br />will be some variation in the outcomes of the analysis due to slight differences in rating and <br />calculation methodology but overall the data is consistent. <br />Pavement Inspection Frequency <br />Two predominant work efforts required to maintain the PMS are updating the street inventory <br />and performing the annual inspection of surface conditions. <br />City streets are divided into segments based on their Functional Classification (FC), pavement <br />type, and geometric design. Segments are the basic unit for evaluating streets and surface <br />conditions. A segment is defined as a portion of a street with a beginning and ending description. <br />Changes in geometric features are used as a guide for determining segments. Examples of <br />geometric differences are surface type, segment width, surface age, and extent of past <br />rehabilitations. <br />Field inspections are conducted by pavement raters who walk each individual street segment <br />evaluating the pavement surface for signs of distress. City arterial and collector streets are <br />inspected annually; residential streets inspections are completed in a three-year cycle; and off- <br />street shared -use path inspections are completed in a two-year cycle. <br />Staff performed inspections on the entire street system using MicroPaver for the first three years <br />after implementation 2013-2015. Inspection data was evaluated for accuracy with the assistance <br />from an outside consultant in 2014. It was determined that three years of street inspection <br />provided an accurate baseline in MicroPaver for analysis. In 2015 staff completed inspections of <br />shared -use paths. In 2016, staff returned to the standard inspection cycle inspecting arterial and <br />collector streets plus two residential areas, South Hills and Coburg. Staff managed to inspect all <br />concrete residential streets as well as alleys. <br />
The URL can be used to link to this page
Your browser does not support the video tag.