Pavement Management System

By: Bishnu Prasad

Devkota
 Course Contents
1. Introduction to Pavement Management (2hrs)
2. Pavement Management Methods (2hrs)
3. Management Information & Data Management (2hrs)
4. Pavement Defects in Flexible & Rigid Pavement (4hrs)
5. Pavement Evaluation (12hrs)
6. Pavement Condition Prediction Models (3hrs)
7. Defects and Remedy Measures (2hrs)
8. Treatment Selection (2hrs)
9. Importance of Maintenance (2hrs)
10. Financing of Roads for Maintenance(2hrs)
11. Prioritization(2hrs)
12. Road Investment Model (The HDM-IV) (2hrs)
13. Airport Pavement Management System(2hrs)
14. Network-Level PMS - M&R Work Planning(2hrs)
15. Project-Level Management (2hrs)
16. Ride Quality and Safety and Case Studies(2hrs)
2
 Lecture-3
Ch-3, Management Information
and Data Management

By: Bishnu Prasad

Devkota
 Lecture Outlines

 Introduction
 Information groups
 Data design
 Data management
 DoR Guidelines for Pavement Management
Data/Information

4
 MIS: Introduction

 The effective management requires

appropriate and up-to-date information
 Information is needed on following items :
 network details,
 traffic and axle loads,
 costs, and
 road conditions etc.

5
 MIS: Introduction

 Definition:
– For the construction of transport infrastructure and
appropriate management of maintenance work,
there should be a provision of computer
based/paper based information system in order to
support for appropriate decision making; which is
called as management information system.

6
 MIS: Introduction

 Importance:
– Management information sits at the heart of the
management cycle.
– All management decisions rely on there being
appropriate and up-to-date information to support
them.
– The widely recognized need of MIS is to assess:
1. physical condition,
2. safety,
3. level of service, and
7 4. efficiency of operation of road system
 MIS: Introduction

 Importance:
– It provides the quantitative basis of dialogue
between technical departments and ministries of
finance during the fund allocation process
– It can also provide the basis of a dialogue with
elected representatives, the road users, farmers and
others, and for monitoring departmental
performance and the meeting of policy objectives

8
 MIS: Management Decisions

 Data are needed to provide the basis for

management decisions on such aspects as
– Determining optimum road condition, and the
maintenance strategies and expenditures needed to
achieve this
– Determining optimum road condition within actual
budget constraints
– Assessing current levels of road and bridge
condition
– Determining appropriate levels of investment
9
 MIS: Management Decisions

 Data are needed to provide the basis for

management decisions on such aspects as
– Prioritizing capital improvements and investments in
maintenance
– Simulating the effects of any improvements on the
future condition and performance of the road system
– Estimating the cost of improvements
– Controlling on-going expenditures

10
 MIS: Information Groups

 It is convenient to discuss management

information using the concept of information
groups.
1. Road inventory
2. Traffic
3. Pavement
4. Finance
5. Activities
6. Resources
11
 MIS: Information Groups

Information Information
Aspects Aspects
Group Group
Road Network/location Finance Costs
inventory Geometry Budget
Furniture/appurtenances Revenue
Environs Activities Projects
Traffic Volume Interventions/treat
Loadings ments
Accidents Commitments
Pavement Pavement structure Resources Personnel
Pavement condition Materials
Structures Structures inventory Equipment
12 Structure condition
 Information Groups: Inventory Data

 In PMS, inventory data is the detailed list of

various data related with pavement
management.
 Decisions on how and when the various
activities of PMS are based on these data.
 Types of road inventory and road references
1. Network referencing- concerned with the location
of road together with alignment and geometry.
2. Item inventory – concerned with the physical
13 characteristics of road.
 Information Groups: Traffic Data

 Traffic data fulfill several important roles in

pavement management, both on the project
level and the network level.
 The types of traffic data that are needed:
1. Traffic characteristics and volume
2. Axle Loading
3. Accident data

14
 Information Groups: Traffic Data

 On the project level,

– traffic data are used for the design of new and
rehabilitated pavement structures.
– As such, they are used for structural strength
design and the design of pavement surface
properties.
– Traffic volume and composition are used to
determine pavement maintenance and
rehabilitation priorities in order to minimize user
costs.
15
 Information Groups: Pavement Data

 Basically pavement data includes (Peterson,

1987)
– Roughness
– Surface distress
– Structural capacity of pavement
– Pavement texture and friction

16
 MIS in Nepal for SRN

– The Department of Road (DoR) has established a

planning branch in DoR headquarters which is
developing a Highway Management Information
System (HMIS) for strategic network.
– Although the HMIS is divided into two levels, both
levels are interdependent.
1. Network level
2. Operation level

17
 MIS in Nepal for SRN

 Network level data covers

– road/bridge inventory,
– pavement condition (Roughness and SDI),
– traffic, and
– construction and maintenance costs.
 Operation level
– Operational level data will kept by Divisions using
paper-based systems and by regions using paper-
based or computer based system as appropriate.
18
 MIS in Nepal for LRN

 DoLIDAR has started computer based Central

Statistics System in order to manage the road
information under the heading of Rural
Transport Management Information System
(RuTMIS).

19
 MIS: Data Design

 Criteria for data design----(RARA)

1. Relevance
2. Appropriateness
3. Reliability
4. Affordability

20
 Data Design: Relevance

 Every data item collected should be desirable,

interesting or possibly useful in the future.
 Individual data items may be used for more
than one function.
– For example, traffic data may by needed to enable a
safety objective to be met, and may also be needed
to assign pavement strengthening treatments.
 The data relevance will depend on ultimate
use, including the managerial level at which
21 this use occurs.
 Data Design: Appropriateness

 The technology and resources involved in

acquiring, processing and managing the data
should be appropriate to administration’s
capacity for maintaining the equipment,
conducting the surveys and sustaining the data
processing.
 Trade-offs need to be made between precise
data collected infrequently on the other hand,
and less precise data, which are updated more
22 frequently, on the other hand.
 Data Design: Reliability

 It is important to ensure consistency of data

over time and between locations.
 Reliability of data is determined based on:
1. Accuracy: Relation between measured and real value
2. Spatial Coverage: For network level planning low
intensity sampling is appropriate but for engineering plan
wide area should be covered.
3. Completeness: Items should not be missed
4. Currency: Time to time renew for data update

23
 Data Design: Affordability

 Available resources and skills vary between

road administrations.
 As administrations develop over time and as
their resources expand and improve, improved
data collection methods can be adopted.
 But in order to do this, rational relationships
between required and available resources is
important.

24
 Data Design: Information Quality Level

 Information Quality levels (IQL)

– It is define as structure road management
information into different levels that correlate to the
degree of sophistication required for decision
making and methods for collecting and processing
data.
– In IQL theory, very detailed data (‘low-level data’)
can be condensed or aggregated into progressively
simpler forms (higher-level data), as shown in
Figure.
25
26
 Data Design: Information Quality Level

 Five levels of road management have been

identified for general use.
– IQL-1 represents fundamental, research, laboratory,
theoretical, or electronic data types, where
numerous attributes may be measured or identified.
– IQL-2 represents a level of detail typical of many
engineering analyses for a project-level decision.
– IQL-3 is a simpler level of detail, typically two or
three attributes, which might be used for large
production uses like network-level survey or where
27 simpler data collection methods are appropriate.
 Data Design: Information Quality Level

 Five levels of road management have been

identified for general use.
– IQL-4 is a summary or a key attribute which has use
in planning, senior management reports, or in low
effort data collection.
– IQL-5 represents top level data such as key
performance indicators, which typically might
combine key attributes from several pieces of
information. Still higher levels can be defined as
necessary.
28
 Data Design: Information Quality Level

 Application of IQL
– The higher the decision-level, the higher the IQL.
– Information at IQL-4 or IQL-5 is appropriate for
performance indicators and road statistics that are
of interest to senior management and the public,
because they tend to be, or should be, easily
understood without much technical background.

29
 Data Design: Information Quality Level

– At the project-level, however, the appropriate IQL

depends much more on the standard of the project
and the resources of the agency. For example, IQL-
3 is usually sufficient for a rural road or a small local
agency.
– For most agencies and main roads, IQL-2 is typical,
but for expressways or high-level, well-funded
agencies, IQL-1 may be used in some instances.
– The criterion to use in selecting the appropriate IQL
is to ask, “Is the decision likely to be altered by
having more detailed information?”
30
 Strategies for Data Collection

 Strategies for data collection are as following:

– In one approach, high level condition data (typically
IQL-IV) are collected for whole road network each
year.
– These data are used for planning and programming
purposes.
– The programming exercise then collect more
detailed data (typically IQL-III) on those sections
where works are under taken.

31
 Strategies for Data Collection

 Strategies for data collection are as following:

– In an alternative approach, relatively detailed data
(typically IQL-II/III) are collected across the part of
network on a rolling program, with a cycle of three to
five years.
– Each year programming decisions are taken either
using current data for individual sections.

32
 Strategies for Data Collection

– Other combinations of the above are also used,

including the following example:
– Annual data collection on the primary road network
,where as a cycle of data collection may be used on
the lower road in the hierarchy.
– Cyclic approach used for the whole network, but
with data collected at a lower level of detail(IQL-
III/IV).
– Cyclic collection methods can also be used without
projection of condition.
33
 Data Management: Information System

 Road information system

– These collect, organize and store data about the
road network, and provide facilities for reports to be
produced on these data, in a variety of formats
– Information systems have no ability to process
these data, although, in order to produce reports,
selections from among different types of data and
summaries of data may be used.

34
 Data Management: Information System

 Information system

Input Data Output

Bank

35
 Data Management: Decision-Support System

 Decision-support system
– This differ from information systems in having the
ability to process input data, using functions or
algorithms, before producing reports; such
processing enables analysis to be carried out which
can guide and assist users making management
decisions about the network.

36
 Data Management: Decision-Support System

 Decision-support system

Input Data Output

Bank

Processing
37
 DoR Guidelines for Pavement
Management Data/Information

 Network Level Data/Information

38
 DoR Guidelines for Pavement
Management Data/Information

39
 DoR Guidelines for Pavement
Management Data/Information

 Operational Level Data/Information

40
 DoR Guidelines for Pavement
Management Data/Information

41
 DoR Guidelines for Pavement
Management Data/Information

42
 Model Questions

8. What is management Information System?

Highlight the criteria for data design.
9. Define the Information Quality levels (IQL).
Differentiate IQL for pavement management
system levels.
10. What do you mean by Inventory data for Pavement
management? What types of strategies are taken
for data collection?
11. What types of traffic data are needed for pavement
management? Illustrate effect of axle loading on
43 performance of pavements.
44