HDM-4 Institutionalization

Vision and Aims

• HDM is for decision-support tool; not decision-

making
• Institutionalization process should ensure that
outcome is:
 sustainable, affordable, appropriate
• Implementation should achieve:
 Independence from external support
 System is mainstreamed into regular road
management practice

2
 Users & Customers

• Policy level
 Economic Development/Planning Departments;
Finance/Treasury/Budget Ministries; IFIs; Dir-General
Highways/Infra; Road Fund Board; Transport Planning
& Road Management Units
• Network planning
 Director-Gen, Road Board Exec Director, Dept.
Treasury/Budget; Dir. Planning, Regional Operations
Dir., Road or Pavement Mgt Unit, Road Authority
Program Div.
• Project level
 Dir. Planning, Dir. Technical/Design, Feasibility Unit,
RMU-PMU-PIU
3
 Levels of HDM-4 Technology

Knowledge Base

Models
Software
Models

RDWERUE SEE

4
 HDM-4 System Architecture
Data Managers Analysis Tools

Road Vehicle Road HDM Project Program Strategy

Network Fleet Works Config.

Core Data Model libraries

File Converter Models can be used in
Vehicle Fleets
Road Networks other systems
transfer data Road Works
to external Projects
systems Programmes RDWE RUE SEE
Strategies

RDWE : Road Deterioration and Works Effects

External
Systems RUE : Road User Effects
Databases, SEE : Safety, Energy and Environmental Effects
PMS, etc.
PMS
5
: Pavement Management System
 Road Management Systems

Data Decision Management

Database
Collection Support Information

Inventory RDBMS Life Cycle Standard

Condition (RIMS) Analysis & Custom
Structures (HDM-4) Reports
Traffic
Furniture
Unit Costs
Standards

6
 Link between HDM-4 with
RMS Systems

HDM4

HDM4
HDM4 File Software
External Converter
Databases
7
 Decision Support System

• Important to have transparency of analysis

• Life cycle analysis capable of:
 Short, Medium & Long term analyses
 What-if analysis, Performance indicators

• Management must understand analysis framework

• Availability of local technical expertise
• Default data sets

HDM-4
8
 Modes of Implementation

• New RMS built around HDM-4

• Interface local RMS or DBMS with HDM-4
• Incorporate parts of HDM-4 into local RMS or
generic RMS (usually VOC, RDWE)
• Modify local RMS from HDM-4 knowledge base,
e.g. improving predictive relationships, adding
economic calculations

9
 System Architecture

• Prefer open architecture;

 Several applications operating under
common platform with shared data
 Can substitute and update applications
easily
• Incorporate HDM-4 through an interface;
ensure on-going international support and
updates
• Custom-built systems; become outdated
rapidly and are expensive to upgrade

10
 Procurement Options

• Departmental
• In-source expertise
• Out-source monitoring surveys
• Out-source analysis and program drafting

11
 Risks & Constraints

• Interruption to establishment, adaptation

(reassignment, leadership change, etc.)
• Slow or lacking updating of IT or HDM
s/ware
• Perception of complexity, reliability, or local
validity

12
 Communication & Messages

• Report high-level information on future

projections to stimulate interest and
champions
• Use Performance Indicators like:
 Impacts of varying budget levels
 return on projects and programs
• Visits to/from countries with successful
implementation

13
 Key Considerations

• Tailor outputs and messages to key audiences

• Keep data and reporting practical, affordable and
reliable – choose appropriate level of data detail
(Information Quality Level)
• Incorporate into enterprise IT architecture
• Mainstream analyses and surveys into regular road
management processes
• Utilize international user support opportunities

14
 HDM-4 Implementation Steps

• Raise awareness - demos, training, etc.

• Appraisal of IT and RMS
• Design enhancement of RM in agency
• Establish standards for use of HDM-4 by
consultants & agency
• Conduct Calibration Level 1 to get started

15