Skip to contentU.S. Department of Transportation/Federal Highway Administration
Asset Management | Bridge Technology | Operations | Pavement

Pavement Management Systems Peer Exchange Program

APPENDIX A - PEER EXCHANGE AGENDA

Pavement Management Peer Exchange Program Agenda
February 4-5, 2008 in Maplewood, MN
February 7-8, 2008 in Salt Lake City, UT

Day 1
Welcome introduction - Host Agency 8:00
Peer exchange program- Review agenda- Expected outcome- FHWA 8:10
Expected outcome - All Agencies 8:20
An Overview of the Host Agency's Pavement Management System 8:30
Status of Pavement Management System- Participant Agencies 8:50
Data Collection- Host Agency followed by group discussion
  • Data collection activities
  • Pavement condition data
  • Asphalt
  • Concrete
  • Grouping
  • Pavement Type (Asphalt, Jointed, Composite); Functional Class (Interstate, Arterial, Collector); Climate, etc.
  • Construction and maintenance history
  • Traffic data
  • Optional data
  • Data integration
9:10
Break 10:00
PMS Analysis -Host Agency followed by group discussion
  • Needs Assessment
  • Performance Indices
  • Trigger Values
  • Performance modeling
  • Economic analysis
  • Optimization (detailed)
  • Treatment decision trees
10:15
Lunch 12:00
PMS Analysis continues 1:00
Demo by the Host Agency: Pavement Management System and its Various functions 2:00
It would be ideal to go through a simulated complete cycle - loading data to system; running needs analysis; optimization, developing candidate list of projects; adjusting projects due to schedule, political influences; what-if scenarios and forecasting conditions; graphics and reporting, etc.
Adjournment 4:00
Day 2
Use of Pavement Management System in supporting strategic, network, and project level decisions
Planning - Host Agency followed by group discussion
  • Setting investment levels
  • Help establish agency goals
  • Provide information to support the development of STIP
  • Provide information to support the development of long-term plans
  • Provide information to support HPMS requirements
7:30
Pavement Management System as a Decision Making Tool Host Agency followed by group discussion
  • Decision making Process
  • Communicating the message
  • Determining the message to be sent
  • Who receives the information?
  • What format should be used?
8:30
Break 9:30
Maintenance- Host Agency followed by group discussion
  • Links to maintenance
  • Who is responsible for what (PMS, Planning, Maintenance)
  • Support to pavement preservation programs and improve pavement performance
  • Pavement condition data to support a pavement preservation program
  • Appropriate distress for selecting preventive maintenance treatments incorporating preventive maintenance treatments into analysis models
  • Treatment rules
  • Institutional and organizational strategies (pavement preservation engineer, regional pavement management personnel)
9:45
Lunch 11:45
Reporting- Host Agency followed by group discussion
  • Feedback process
  • Variations in reporting depending on the users
    • District (Current Conditions & Treatments, Roughness Index Maps, Priority Listing)
    • Yearly ( Past 5 Year Pavement Condition Report, Statewide Summary, Budget Analysis)
    • Other Reports
  • Access to data
12:45
PMS and Engineering and economic analysis
Design- Host Agency followed by group discussion
  • Provide support for engineering and economic analyses (e.g., evaluate design effectiveness)
1:45
Break 2:15
Open Discussion

Possible topics
  • What was the implementation procedure like? Were there many modifications and customization required, such as to input and output data file formats and links to existing systems?
  • Procurement of the System
  • What were the vendor responsibilities, and what tasks were performed by the DOT (such as developing models, identifying treatment trigger levels)
  • Is the software run only at the central office, or does each regional office use the system to develop and manage their pavement programs? Is the system used at the residency/county level? How many users? Are the MPO's involved?
  • How was the experience with training and technical support from vendor? What was the training strategy and effort?
  • What level and number of staff are required to operate and maintain the system (technician, administrative type, engineer, computer expert....)?
  • Does the PMS include other assets? How does your PMS tie into other assets?
  • After all the dust settled, does the system do what they need it to do?
2:30
Closing 3:50
Adjournment 4:00
PDF files can be viewed with the Acrobat® Reader®
Updated: 11/01/2012