Lecture 3 Data Needs
Lecture 3 Data Needs
• Expensive (time/effort/money)
• Should not be a wish list
• Should not implement with what is currently available
• The approach should not be too expensive or data
intensive
• Ask?
▪ What are the decisions to be made? (Network
level/project level)
▪ What data is required to support these
decisions?
▪ Affordability – initially and in future?
Data Needs: What to collect?
• Good practices
▪ Confirm whether the data are actually required
▪ Consider the total cost
▪ Minimize data collection
▪ Consider pilot studies
• Guiding principles
▪ Collect only the data you need;
▪ Collect data to the lowest level of detail sufficient
to make appropriate decisions
▪ Collect data only when they are required
Pavement Management: Decision Levels
Strategic Level
• Decisions that are made at the highest level within an organization
• Reflect agency and stakeholder priorities
• Establishing targeted performance levels
Network Level
• Strategies are identified to achieve the agency’s goals
• Overall needs of the entire road network are considered
• Multi-year improvement programs are developed
Project Level
• Decisions are very specific
• Concentrated on a particular portion of the network
Decision Levels and levels of data details
Decision Types of Decisions Level of Level of
Level Details Influence
Strategic • Performance targets Low Broad
• Funding allocations
• Pavement preservation strategy
Network • Project and treatment Moderate Moderate
recommendations for a multi-
year plan
• Funding needed to achieve
performance targets
• Consequences of different
investment strategies
Project • Maintenance activities for current High Focused
funding year
• Pavement rehabilitation thickness
design
• Material type selection
• Life cycle costing
Data Needs
Data Needs: Degree of Details
Degree of Details
• Network-level
• Project Level
• Operational Level
• Research and Development
Data Needs: Degree of Details
Aspect Network level Project Level
Uses • Planning and • Treatment Design
Programming • Material Selection
• Identify Budget needs • Value Engineering
• Network Level
condition reporting
Data IRI, Rut Depth, Faulting, • Detailed crack mapping
Items Cracking, Punchouts, and other distresses
Typically Patching, Joint condition, • Structural capacity (eg.
Collected Raveling, Bleeding, FWD)
Surface texture • Joint load transfer
• Base/soils
characterization (GPR,
cores, trenches)
Data Needs: Frequency of collection
• Inventory data
▪ typically collected in a once-off exercise
▪ updated when changes are made
▪ usually updated every five years or so
• Condition data
▪ Frequency depends on the pavement category. (Eg:
highways are monitored at frequent intervals, often
1-2 years, while minor roads may be monitored at 2
– 5 year intervals)