Step by Step PMS User Guide PDF

Republic of the Philippines
Department of Public Works and Highways
Pavement Management System
Step by Step User Guide
Version 5
March 2015
Pavement Management System Step By Step User Guide
Contents
A. Introduction ............................................................................................................ 5
A.1 Pavement Management System (PMS) .......................................................... 5
A.2 Strategic Planning Analysis Procedure ........................................................... 9
A.3 Programme Analysis Process ........................................................................10
B. Prepare Named Selection for Strategy Planning Analysis .................................11
C. Create and Analyse Homogenous Data Report ..................................................14
C.1 Set Parameters of Confirm (HDM-4 Interface) ...............................................14
C.2 Create Homogenous Data Report ..................................................................17
C.3 Analysis of HDR in Microsoft Excel ................................................................19
C.4 Definition of NSM-SPA...................................................................................23
D. Update HDM-4 Workspace and Export Network and Strategy Input Files ........30
D.1 Update Strategy File ......................................................................................30
D.2 Update Traffic Growth Rate ...........................................................................33
D.3 Update Road User Costs (RUC) ....................................................................35
D.4 Update Construction Costs ............................................................................37
D.5 Export Network and Strategy Input Files ........................................................38
E. Update Network Input File ....................................................................................41
E.1 Prepare Network State Matrix (NSM) Populating Tool - SECTION.................41
E.2 Prepare Network State Matrix (NSM) Populating Tool - TRAFFIC .................45
E.3 Update NSM Attributes ..................................................................................47
F. Identify Optimum Alternative for Each PRS ........................................................50
F.1 Run unconstrained Strategy Analysis of NSM in HDM-4 ................................50
F.2 Assign optimum alternative to PRS ................................................................56
G. Run Strategy Analysis Interface ..........................................................................60
G.1 Set Parameters of Confirm (HDM-4 Interface) – Criteria for NSM-SPA ..........60
G.2 Strategy Analysis Interface ............................................................................61
H. Review Strategy Analysis Interface Outputs ......................................................64
H.1 Check total number of NSM cells ...................................................................64
H.2 Correction of clones length ............................................................................64
H.3 Update of Strategy Input File .........................................................................66
I. Run strategy analysis in HDM-4 and Perform Budget Optimization .................67
I.1 Import revised Strategy Analysis Interface Outputs into HDM-4 .....................67
I.2 Run Strategy Analysis in HDM-4 ....................................................................68
I.3 Perform Budget Optimization .........................................................................71
J. Import HDM-4 result into SETH and prepare SPA visuals .................................74
J.1 Import HDM-4 result into SETH......................................................................74
J.2 Prepare SPA Report visuals for the National Network ....................................74
J.3 Prepare SPA Report visuals per Planning Unit, Region and Road Class .......75
K. Preparation of SPA Report ...................................................................................83
K.1 Analysis of SETH Output ...............................................................................83
K.2 Prepare SPA Report ......................................................................................83
L. Update Budget Optimization in HDM-4 with Defined Budget .............................84
M. Import HDM-4 result into SETH and determine budget per Planning Unit ........85
2
M.1 Import HDM-4 result into SETH......................................................................85

M.2 Determine Budget Scenario per Planning Unit ...............................................85
N. Run Programme Analysis Interface .....................................................................87
N.1 Configure HDM-4 Interface – Check Exclusion Settings ................................87
N.2 Define Current Planning Unit .........................................................................88
N.3 Programme Analysis Interface .......................................................................89
O. Run Programme Analysis with Budget Constraint in HDM-4 ............................91
O.2 Run Programme Analysis ..............................................................................91
O.3 Impose Defined Budget Constraint ................................................................94
P. Prepare Programme Analysis Outputs ................................................................96
Appendix A – List of Congressional Districts with Reference No. ..........................98
Appendix B – Strategic Planning Analysis Report – Template..............................101
Introduction ...........................................................................................................101
B. Network Analysis ..............................................................................................101
Parameters and settings .......................................................................................104
SPA Output Analysis – National Network ..............................................................106
SPA Output Analysis – Regional Level .................................................................109
Annex 1 - Vehicle Operating Costs (VOC) and Road User Costs (RUC)...............119
Annex 2 – Traffic Growth Rates (TGR) .................................................................120
Annex 3 – Capital and Recurrent Construction Costs ...........................................121
3
Glossary of Terms
AADT Annual Average Daily Traffic
DPD Development Planning Division
DPWH Department of Public Works and Highways
FY Financial Year
HDM-4 Highway Development and Management (version 4)
HDR Homogeneous Data Report
IMS Information Management Service
IRI International Roughness Index
MYPS Multi-Year Programming and Scheduling Application
NSM Network State Matrix
NSM ID Network State Matrix Identification Code
NSM-SPA Network State Matrix Strategic Planning Analysis
PAGASA Philippines Atmospheric, Geophysical & Astronomical Services Administration
PMS Pavement Management System
PS Planning Service
PRS Planning Road Section
RBIA Road and Bridge Information Application
RTIA Road Traffic Information Application
SD Statistics Division
SETH Strategic Evaluation Tool for HDM-4
SPA Strategic Planning Analysis
TGR Traffic Growth Rate
4
A. INTRODUCTION
A.1 Pavement Management System (PMS)
1. The objective of this User Guide is to describe, step by step, the procedure to operate the Pavement
Management System (PMS), which corresponds to the two steps Input Data Preparation and Run
HDM-4 Analysis in the Planning and Programming overall process (see Figure 3 overleaf). The
analysis of HDM-4 output to prepare the Long Term Plan and subsequent programs is covered in the
Planning and Programming Procedures Manual. (See PMS Documentation Map Figure 2).
2. The process actually involves several back and forth between the Confirm (HDM-4 Interface) and
HDM-4 System (see Figure 1 below), and this document was structured to follow this logical
sequence of steps. Therefore, its structure may differ slightly from Figure 3.
Figure 1
PMS System Components
3. The starting point is the creation of HDR. It does NOT require input files exported from HDM-4, but
requires the specification of Network State Matrix (NSM) that represents the national road network
by a small number of representative sections or NSM cells. Currently, NSM is defined by pavement
type, traffic volume, direction, roughness and pavement condition.
4. The main task of Confirm (HDM-4 Interface) at the first stage is to chop the defined national road
network into homogeneous road sections referred to as PRS and produce HDR. HDR summarizes,
PRS by PRS, all relevant information available from Road and Bridge Information Application
(RBIA) and Road Traffic Information Application (RTIA) applicable for running HDM-4. Each PRS
is associated with a unique NSM cell identifier that represents the PRS.
5
Figure 2 PMS Documentation Map
6
Figure 3
Planning and Programming Overall Process
7
5. Strategic Planning Analysis (SPA) studies National State Matrix (NSM). HDM-4 workspace must be
configured for the defined NSM by means of network file and strategy file. The strategy file defines a
set of section alternatives for each NSM cell.
6. The configured NSM network file is exported from HDM-4 and populated with the information
contained in HDR by using Excel spreadsheet tools.
7. The populated network file and strategy file that have been exported from the configured HDM-4
workspace are imported to Strategy Analysis Interface of Confirm (along with the user defined
maximum NSMSPA cell length) to prepare HDM-4 input data (i.e., HDM-4 workspace) for SPA.
8. Program Analysis studies individual PRS by Planning Unit (PU). Program Analysis Interface of
Confirm defines the road network as all PRS’s belonging to a given Planning Unit (PU) and prepares
HDM-4 workspace that is populated with section alternatives for each PRS based on the NSM cell
that represents the PRS.
9. The output of HDM-4 strategy analysis are used with the Strategic Evaluation Tool for HDM-4
(SETH) to provide information for decision makers to decide upon the optimal scenario and obtain a
budget per Planning Unit (to be used for the programme analysis).
10. The output of HDM-4 program analysis under the defined budget scenario are then used in the Multi-
Year Programming and Scheduling Application (MYPS) to follow up the implementation of the
works.
8
A.2 Strategic Planning Analysis Procedure

11. The Procedure for conducting SPA is described in the flowchart below. Each step represented by an
individual box in the flowchart is described in in a separate Section in this document.
Figure 4 -
SPA Procedure
Tasks Software Description
Confirm (HDM-4 Prepare Named Selection in Confirm (HDM-4 Interface) by

Interface selecting all roads at the cut-off date of RBIA + 1 day.
Confirm (HDM-4 Create HDR of the above Named Selection: HDRYY_01.xls. In

Interface) Excel, check PRS attributes and determine NSM-SPA
Microsoft Excel parameters by calculating length of NSM cells.
Update RUC in Vehicle fleet file (Philippines12.mdb), Works

HDM-4 Unit Costs (WorkStds.mdb) and Traffic Growth Rates directly
Microsoft Access in HDM-4. Update Section Alternatives if needed. Export
NSM_Network_YY_01.mdb and NSM_Strategy_YY_01.mdb
files from HDM-4
Microsoft Excel Update NSM_Network_YY_01.mdb with NSM Populating

Microsoft Access Tool spreadsheets. Save as NSM_Network_YY_02.mdb and
NSM_Strategy_YY_02.mdb.
Run a Strategy analysis in HDM-4 with the updated input files

HDM-4
to identify optimum alternatives for NSM cells. Deduct
Microsoft Excel
optimum alternative for each PRS via the HDR.
Confirm (HDM-4 Set the appropriate parameters in Confirm (Homogenisation

Interface) System and HDM-4 System Settings) and run Strategy
Analysis Interface on above Named Selection. Outputs:
NSMSPA_RN_YY_01.mdb and NSMSPA_STR_YY_01.mdb.
Check that the number of NSM cells in NSM-SPA is smaller

Microsoft Excel
than 400. Redistribute length of cloned cells. Outputs:
Microsoft Access
NSMSPA_RN_YY_02.mdb and NSMSPA_STR_YY_02.mdb.
Import NSMSPA_RN_YY_02.mdb and

NSMSPA_STR_YY_02.mdb in HDM-4. Run the Strategy
HDM-4 Analysis module of HDM-4 with a study period of 20 years.
Identify the Unconstrained Capital Cumulated Cost at 6 year to
derive the optimal yearly capital expenditure during the 6 year
planning period. Prepare budget scenarios with 100%. 90%.
75% and 50% of this capital cost. Output: rundata.mdb
Import rundata.mdb into SETH_template.mdb. Set SETH
parameters and evaluate scenarios. From SETH tables, prepare
Microsoft Excel
graphs to represent the different output of each budget scenario
in terms of capital expenditure, economic return and average
roughness of the network.
Microsoft Word Analyze SPA output and prepare SPA Report using the
template in Appendix B.
9
A.3 Programme Analysis Process
12. At the end of the Strategic Planning Analysis, an annual budget is decided for the asset preservation
of the national network for the next Financial Year (FY). The objective of the programme analysis is
to translate this budget in a prioritized list of works for each Planning Unit (PU). The Procedure of the
Programme Analysis is described in the flowchart below
Figure 5 -
Programme Analysis Procedure
Tasks Software Description
In HDM-4 Strategy Analysis module, create one additional budget

scenario corresponding to the defined annual budget decided for the
HDM-4
next financial year. Repeat this budget for the 6 years of the
planning period.
Import rundata.mdb into SETH_YY_01.xls. Set SETH parameters,

Microsoft Excel evaluate scenarios and define NSM length per PU. Output:
SETH_YY_02.xls. In the worksheet “Output per Planning Unit”,
identify a 6 year budget scenario for each PU.
Set the exclusion settings, then select the appropriate Planning Unit
Confirm (HDM-4 and create the corresponding Named Selection with the queries
Interface) PMS_06, PMS_02 and PMS_03. Then run the Programme Analysis
on this Named Selection. Outputs: PRS_RN_YY_XXXX_01.mdb
and PRS_PRG_YY_XXXX_01.mdb.
HDM-4 Import PRS_RN_YY_XXXX_01.mdb and

PRS_PRG_YY_XXXX_01.mdb in HDM-4 and run the Programme
Analysis module of HDM-4. Set the budget constraint as per the PU
budget identified with SETH. Output: rundata.mdb.
HDM-4 Export HDM-4 Programme Analysis in Excel via the “export” tool.
Microsoft Excel Output: PRS_PRG_YY_XXXX_01.xls.
10
B. PREPARE NAMED SELECTION FOR

STRATEGY PLANNING ANALYSIS
1. Select the Confirm Enterprise icon from the desktop to launch Confirm.
2. Login to Confirm using your User ID and password.
3. Open the Data Query Qualification form (Reporting > Data Queries) or using the search tool: Ctrl+F,
“queries”:
4. Open the data source filter by hitting the filter button

5. In “Name Contains”, enter “PMS” then hit “OK”
6. Select “PMS_01 – All Live Road Sections”, then hit “OK”
11
7. In Data Query Qualification, set the “Effective Date” (double click on ‘Effective Date) as the RBIA
cut-off date plus one day (to make sure that data entered during the last day is included) then hit
“OK”.
8. Run the query by hitting the “OK” button
9. This will create a selection with all the live road sections of the national network as per the cut-off
date. Click on the “Save Named Selection” icon
12
10. Define the Code and Name of the Named Selection:

STRYY_01
Where:
• YY: Year of the analysis
• 01 Sequential Number
11. Define “Where Selection already exists as “Replace”, then hit “OK”
13
C. CREATE AND ANALYSE HOMOGENOUS DATA

REPORT
C.1 Set Parameters of Confirm (HDM-4 Interface)
C.1.1 HDM-4 Settings
1. Open the HMD-4 Interface and go first to HDM-4 System Settings
2. Open the “General” tab and check that the Maximum NSM length is left blank.
Not relevant at
Maximum NSM section
this stage
length should be left
blank
14
3. The three other fields should not be changed at this stage:

• The NSM ID expression defines the code of the section ID (e.g. AVH21GF for Asphalt road,
with Very High traffic, 2 lanes and 1 traffic flow direction, Good IRI and Fair surface
condition).
• Traffic Growth Set defines the attribution of the Traffic Growth rates as seen above (Only
used at Programme Analysis Stage).
• Exclude if true enables to exclude roads defined via another expression (see below). By
default, it excludes urban roads and gravel roads.
4. “Sections” and “Traffic” tabs of HDM-4 Systems Settings should not be changed either as part of the
regular planning procedure.
C.1.2 Homogenization Systems Settings
1. Open Homogenization Systems Settings, at Computed Columns Tab
Not relevant at
this stage
15
2. Make sure the settings are as follow:

Expression Name Setting/Expression Description
Feature Road Section
Minimum Section Length 500 m Sets Minimum PRS length
Maximum Section Length 1,500m Sets Maximum PRS length
PLANNING_UNIT {RCON_RI01} Sets congressional district as PU
CURRENT_PU “” No PU is selected
Sections outside of selected PU are not
GENERAL_EXCLUSIONS “N”
excluded
GRAVEL_EXCLUDE “Y” Gravel and Earth roads are excluded
URBAN_EXCLUDE “Y” Urban Metropolitan roads are excluded
NSM_LEN 7 Number of characters of NSMID
NSM_ORIG “” No substitution of NSMID (See G.1.1)
NSM_ALT “” No substitution of NSMID (See G.1.1)
3. All the other parameters are configured and should not require any change at this stage.
Select the Feature Inventory Tab and review the Inventory Items. This tab lists the features which are
being used and how they are used to determine the homogenous sections. Check that the parameters
follow the PMS interface Configuration Report (2014).
16
4. Select the Survey Tab and review the selected items (Ditto previous step).
C.2 Create Homogenous Data Report

1. Prepare a Named Selection
2. Open the HDM-4 Interface in the RBIA Explorer: Network Manager > HDM-4 Interface
3. Open the Homogenous Data Report module
17
4. The Homogenous Data Report exports in a Microsoft Excel spreadsheet the result of the chopping of
the network. It can be “unmerged”, where each row represents a truly homogenous section or
“merged”, where each row represents a Planning Road Section (PRS). The configuration of the
parameters of the chopping are described in the PMS Interface Configuration Report (2014).
5. Set the Effective date at the RBIA cut-off date plus one day (Use the same date as the one defined in
Section B).
6. Select the Named Selection representing the strategy analysis scope of analysis created in Section B.
7. Define the name of the HDR file (csv format) as

HDRYY_01
With:
• YY: Year of the study
• 01: Serial number
8. Click on the “Merge” Option and hit the “OK” button.
Merge Box to be
checked
18
C.3 Analysis of HDR in Microsoft Excel
1. Open the csv file in Microsoft Excel:
2. Save the HDR as Excel workbook (xls or xlsx) with the same name, freeze the first row and apply
general filters (Select all and Ctrl + Shift + L) on all columns.
C.3.1 Review PMS road related data

1. The HDR is a very convenient tool to cross-check PMS related data.
2. Check for missing and null values (a large quantity of zeros might indicate that missing data was
entered as zero in the RBIA, which bias the average values) for the following items. Report to SD if
any issues are identified:
• Average Width (RCWW_WDTH)
• Environment (RENV_RI07)
• Directional Flow of Traffic (RNLN_RI04)
• Number of Lanes (RNLN_RI21)
• Surface Type (RPVT_RI34)
• AADT (RAAD_RI41)
• IRI (RR_RC05)
• All RCONDA and RCONDC columns (RoCond values, see PMS Design Report, 2014)
19
3. For the above columns, check outstanding values by sorting from largest to smallest, then smallest to
largest. Check if the following RoCond values, corresponding to percentages, exceed 100:
• Edge Break Extent (RCONDA_RC13)
• Wearing Surface (RCONDA_RC48)
• Cracking Extent (Asphalt) (RCONDA_RC10)
• Joint Faulting (RCONDC_RC19)
• Joint Spalling (RCONDC_RC18)
• Cracking (Concrete)(RCONDC_RC16)
4. Check extreme AADT figures against the number of lanes
C.3.2 PRS Review

1. Identify PRS with incomplete data:
• In the NSM_ID column, filter to select PRS including “– incomplete NSM ID” and note
their section IDs. These sections do not have roughness and RoCond data. Send the list to
the Statistics Division (SD) for information and update when possible. If the RBIA is not
updated, these sections will not be included in the analysis.
• In the NSM_ID column, filter to select PRS including "-Traffic Data Missing-" and note
their section IDs. Send the list to SD for information and update when possible. If the
RBIA is not updated, these sections will not be included in the analysis.
2. Perform a random check of NSM_ID. NSM-ID are assigned as follows:
A 21 HG F G
Pavement type: Traffic/Flow: Traffic: Roughness: Visual Condition:
A: Asphalt 21: 2 lanes 1 VL: Very Low G: Good G: Good
C: Concrete direction LW: Low F: Fair F: Fair
(G: Gravel 22: 2 lanes 2 MD: Medium P: Poor P: Poor
E: Earth) directions HG: High B: Bad B: Bad
42: 4 lanes VH: Very HIgh
2directions
With :
Asphalt and Concrete
AADT Band
Roads
VH Very High AADT > 20,000
HG High AADT > 8,000 & ≤ 20,000
MD Medium AADT > 2,500 & ≤ 8,000
LW Low AADT > 750 & ≤ 2,500
VL Very Low AADT > 0 & ≤ 750
20
And
Machine Condition Asphalt and
Band Concrete Roads
G Good IRI > 0 & ≤ 3
F Fair IRI > 3 & ≤ 5
P Poor IRI > 5 & ≤ 7
B Bad IRI > 7
(Visual Condition score is given following a combination of all the defects and cannot be checked as
part of this step)
Select a few NSM_ID and check the corresponding key features (i.e. RPVT_RI34, RNLN_RI21,
RNLN_RI04, RR_RC05):
3. Calculate the sum of the column “SubSection_Length”
4. Check that the total length of PRS matches the length of the named selection:
• In the Confirm, open the “Named Selection” module:
21
• Search and select the Named selection created in Section B. Selections are sorted by
“name” and not by “code” by default)
• Check the length against the sum of the column “SubSection_Length”
Note: A difference of a few meters may appear due to the rounding of the length of each PRS
5. Perform a random check on the column “Exclude_If_True” against the columns Surface Type
(RPVT_RI34) and Environment (RENV_RI07). Exclude_if_True must be “True” when:
• Surface Type is “G” or “E”
• Environment is “UM”
22
6. Check if any PRS is longer than the defined maximum length (1,500m). This may happen when both
roughness and RoCond data are missing on a long section. Prepare a list of these sections and report
them to SD.
C.4 Definition of NSM-SPA

C.4.1 Calculate length of NSM cells
1. Select the entire table by clicking on the top left corner
2. Go to Insert > Pivot Table
23
3. Leave the default options and click “OK”
4. In the “Pivot Table Fields”, drag and drop “NSM_ID” to the “ROWS” box
5. Then drag and drop “SubSection_Length” in the “VALUES” box:
24
6. In the drop list menu of “Count of SubSection…”, click on “Value Field Settings…”
7. Replace “Count” with “Sum”
8. Back in “Pivot Table Fields”, drag and drop “Exclude_if_True” and “AADT(RAAD_RI41)” in the
“FILTERS” box
9. Close the “Pivot Table Fields” window and, in the drop list menu of “Exclude_if_True”, check
“Select Multiple Items” and unselect “True”
10. In the drop list menu of “AADT(RAAD_RI41), check “Select Multiple Items” and unselect “Blank”
25
11. Select the two columns of the Pivot Table and copy them
12. Open a new Worksheet and “Paste Values”
13. Apply a filter on the table: Select all the cells and click on Data > Filter
14. Note the number of rows in the table (make sure not to count the row “Grand Total”)
C.4.2 Determine the Maximum NSM length
1. Sort the column “Total” from “Largest to Smallest”

2. The standard and absolute maximum for a NSM is 800 km (Not that lengths in the HDR are in
meters). The following is recommended to determine the maximum NSM length:
26
• Plot the distribution of NSM cell length by selecting the entire table, then Insert>Insert
Column Chart>Clustered Column
• Increase the size of the graph and identify any break in the “curve” of the distribution of
NSM length. In the example above, such a break occurs between the lengths of 516 km
and 647 km:
• Hence, in the example above, 600km is a more appropriate maximum than 800km.
3. NSM cells whose length is longer than the set maximum will be “cloned” by Confirm (HDM-4
Interface) through the Strategic Analysis module (see section below): New NSM cells with the same
characteristics will be created to distribute the total length into smaller items with a length smaller
than the set maximum.
27
C.4.3 Control the total number of NSM cells
1. Calculate the total number of resulting NSM cells by calculating the number of clones to be created.
It can be rapidly estimated with the following formula:
௡
‫ݐ݃݊݁ܮ‬ℎ ܰܵ‫ ܦܫ ܯ‬௜
෍ ‫(ݎ݁݃݁ݐ݊ܫ‬ )+1
‫ݐ݃݊݁ܮ ݉ݑ݉݅ݔܽܯ‬ℎ
௜ୀଵ
2. If the total is smaller than 400, no need to proceed to any change
3. If the total is greater than 400, the appropriate number of cells (Total number – 400) will need to be
removed:
1. The “elimination” of the cells is done by substituting the NSM ID of sections (i.e. PRS) with
another NSM ID. In other words, it is done by merging the NSM cell with another cell
associated to a longer length.
2. Therefore, for each identified cell with a length inferior to the limit, a cell with similar
attributes should be selected, with which the cell will be merged. The following should be
followed to identify the substitution:
a. Sort the column “Total” from “Smallest to Largest
b. Identify the NSM ID of the smallest cells that need to be removed.
c. Example for AHG42BG: Filter the column NSM_ID to select only NSM IDs with the
same 6 first characters (i.e. same pavement type, traffic direction/number of lane,
traffic volume category and roughness).
d. If available, select the NSM ID with the surface condition score (last letter of NSM
ID) in the next category (G > F > P > B). If not available, take the closest one.
28
e. If no other NSM ID are available in this selection, repeat Step c. by selecting all
NSM IDs with the same 5 first characters, then repeat step d with the roughness
score.
f. A list as follows should then be transmitted to HDM-4 Interface administrator (IMS),
who will amend the NSMID expression accordingly.
NSM_ORIG* Length (m) NSM_ALT** Length (m)

AHF42BG 23.00 AHG42BF 802.00
AVH21BG 33.00 AVH21BF 141.00

CVL42BB 54.00 CVL42PP 506.00
Etc.
* NSM_ORIG: NSM to be removed
** NSM_ALT: Alternative NSM
29
D. UPDATE HDM-4 WORKSPACE AND EXPORT

NETWORK AND STRATEGY INPUT FILES
1. In HDM-4, open the HDM-4 Workspace containing the NSM network and strategy files.
2. There should be:

• 1 Vehicle Fleet file, named “Philippines12”
• 1 Road Networks file, named “NSM_Network”
• 1 Strategies file named “NSM_Strategy”
• A set of maintenance standards
• Sets of Configuration files
D.1 Update Strategy File

1. Note: to display the strategy window as HDM-4 1.3, go to HDM-4 Options in Programme
Files/HDM-4 version 2:
30
2. Then select “Classic (version 1x style)
3. Open the NSM_Strategy file
4. Verify that the Strategy file is connected to the right network file and vehicle fleet. Analysis period
should remain of 20 years and discount rate of 15%, unless otherwise stated.
5. Go to the “Study Sections” tab and check that all “Sections” are selected (red tick box) and have
“ALL” as Traffic Growth
31
6. Go to the “Specify Alternative” Module:
7. Each alternative is composed of works standards which are already predefined in the strategy file.
Check that all sections have more than one alternative (base alternative), and correspond to the HDM-
4 Configuration Report (2014).
8. Update Alternatives if needed.
32
D.2 Update Traffic Growth Rate
1. In HDM-4, open the file Vehicle Fleet (Philippines12) composed of 12 vehicles.
2. Open the “Edit Traffic Growth Sets…” Option
3. The list of Traffic Growth Rates (TGR) should include a National Average (ALL), used for the
Strategic Planning Analysis, and one set per Region. Select the first Set of TGR and hit the “Edit…”
button.
33
4. Update the TGR for each vehicle type and each time period based on values calculated as per the
Procedures Manual for Updating Vehicle Costs and User Costs, Work Unit Costs, Asset Values,
Traffic Growth Rates (2014).
5. Repeat Steps 3 and 4 to update all the sets of TGR
34
D.3 Update Road User Costs (RUC)
1. IN HDM-4, Select the file “Philippines12” and hit the “Export” button
2. Save file under the same name: Philippines12.mdb

3. Open the file Philippines12.mdb in Microsoft Access and Open the table “VEHICLES”
4. Update all attributes with the values received from the Statistics Division (SD) as per the Procedures
Manual for Updating Vehicle Costs and User Costs, Work Unit Costs, Asset Values, Traffic
Growth Rates (2014). Note that “EUC” corresponds to “Economic Unit Cost” and “FUC”
corresponds to “Financial Unit Cost”. “FUC” column should be left blank as HDM-4 does not
conduct financial analyses of Road User Costs.
5. Save Changes and close the file
6. In HDM-4, hit the “Import” button and select the file updated in the previous steps
35
7. Click “Next” and “Yes” when prompted whether to overwrite existing vehicle fleet
36
D.4 Update Construction Costs
1. In HDM-4, Select the folder “Work Standards” and hit the “Export” button
2. Save file under the same name: “WorkStds.mdb”.

3. Open the file WorkStds.mdb in Microsoft Access and open the table “Works”
4. Select all values by clicking on the top left corner and paste values in a new Microsoft Excel
spreadsheet.
37
5. Freeze the top row and apply Filter on the table

6. Sort the column “WORK_CODE” from “A to Z” to gather identical Work types.
7. Based from data received from Bureau of Construction (BOC) and Bureau of Maintenance (BOM),
update the columns FIN_COST (Financial Cost), ECON_COST (Economic Cost) for each work.
8. For works related to asphalt overlay only, update values for preparatory works: PAT_ECOST,
EDGE_ECOST. CRKS_ECOST and : PAT_FCOST, EDGE_FCOST and CRKS_FCOST
(respectively economic and financial unit cost of patching potholes, edge repair and cracks sealing)
9. Copy the entire table (without the top row) and paste it back in the Table “Works” in the
WorkStds.mdb file
10. Hit “Yes”, then save and close the file

11. In HDM-4, hit the “import” button and follow steps 6 and 7 from Section D.3 to overwrite existing
Work Standards.
D.5 Export Network and Strategy Input Files
1. IN HDM-4 workspace, select the network (NSM_Network file) and click on Export:
38
2. Create an appropriate folder and save the file under the name NSM_Network_YY_01 with:
• YY: Year of the study
• 01: Sequential number
3. Select the strategy file NSM_Strategy and hit the “Export” button:
39
4. Save the NSM_Strategy file in the same folder as the NSM_Network file and under the name
NSM_Strategy_YY_01.mdb.
Where:
o YY: Year of the study
o 01: Sequential number
40
E. UPDATE NETWORK INPUT FILE

E.1 Prepare Network State Matrix (NSM) Populating Tool - SECTION
1. Open the Excel Spreadsheet named “NSM Populating Tool_SECTIONS”
2. Go to the HDR-Extract worksheet and clear all the content under the top row (which is protected)
41
3. Open the HDR created in Section C.2 in Excel and copy/paste the columns with the corresponding
headers using Paste Special… > Paste Value.
4. Go back to “Introduction” worksheet and in step 3:
• Enter the appropriate Start Year (i.e. the first year of the study period)
• Enter the AADT Year which corresponds to the biggest percentage of traffic data of the
HDR (usually study year minus 2)
• Confirm the option to exclude Gravel and Urban Road (by default it should be yes)
• Confirm whether Rutting is considered as Type A or Type B variable (by default it
should be Type B).
5. Go to “Type A Variables” worksheet.
6. Type A variables have been computed based on the imported data from HDR and appear in the cells
highlighted in light yellow. Depending on the relevant attributes of the NSM cells, they have been
sorted in different tables.
7. Look for outliers and any missing data in the tables. If sets of data are considered as biased or non-
representative of the network, default values should be applied (See PMS Configuration Report).
42
8. Go to the Type B & C Variables worksheet. These values should only be updated (or reconfirmed)
every 3 to 5 years.
9. Go to SECTIONS worksheet and check that no column includes an error (e.g. #N/A), blank cells
apart from “LINK_ID” and “LINK_NAME” columns, or “no data available”)
43
10. Go to the Network Analysis worksheet. Check graphs of the network for visual condition. If the
categories are not representative (e.g., if more than 90% of the roads are scored as “good”), the
Machine Condition Band formula may need to be reviewed.
11. Update Section B of the SPA Report (See Appendix B).
12. Save Spreadsheet 1 under the name:

NSM Populating Tool_SECTIONS_YY_01.xls(x)
Where:
44
E.2 Prepare Network State Matrix (NSM) Populating Tool - TRAFFIC
1. Open the Excel Spreadsheet named “NSM Populating Tool_TRAFFIC”
2. Enter the same AADT Year and as defined in Section E.1 and confirm that the same options for the
exclusion of gravel roads and urban roads have been selected.
3. Go to HDR – Extract tab and. Open the HDR created in Section C.2 in Excel and copy/paste the
columns with the corresponding headers using Paste Special… > Paste Value
45
4. Go to Type A variables tab and check the values calculated as the average of AADTs of all PRSs
belonging to the same NSM cell:
5. Go to TRAFFIC tab and check that there is no cell with error (e.g. #N/A) or “no data available”.
6. Save Spreadsheet under the name:

NSM Populating Tool_TRAFFIC_YY_01.xls(x)
Where:
46
E.3 Update NSM Attributes
1. Open with Microsoft Access the input file NSM_Network_YY_01.mdb exported from HDM-4 in
Section D.
2. The file is composed of 4 tables. The Tables FILETYPE and ROADNET only include generic
information for HDM-4 purpose and should not be changed. The Table SECTIONS contains all the
information related to the NSM cells.
3. Open the SECTIONS table

4. The table shows all the NSM cells with all their attributes. It is the same as the tab SECTIONS of the
Populating Tool.
5. Go back to the NSM Populating Tool_SECTIONS spreadsheet in Excel and copy cells G2:GN481
from the SECTIONS tab and paste them in this table.
6. Click “yes” to the pop-up window. Then save the changes and close the mdb file.
47
7. Open the TRAFFIC table:
8. The table shows all the NSM cells in column (the NSM ID is replaced by a serial number) with an
AADT value for each of the 12 vehicles. It is the same as the tab TRAFFIC of the Populating Tool.
9. Copy cells C2:H5761 from the TRAFFIC tab of the NSM Populating Tool_TRAFFIC spreadsheet
and paste them in this table.
10. Click yes to the pop-up window.
11. Save updated database as NSM_Network_YY_02.mdb
48
12. Open the NSM_Strategy_YY_01.mbd file extracted in Step D.5. and open the table “Strategy”
13. Update the following columns:
• NAME: NSM_Strategy_YY_02
• NETWORK: NSM_Network_YY_02
14. “Save as” the file under the name NSM_Strategy_YY_02.
49
F. IDENTIFY OPTIMUM ALTERNATIVE FOR EACH

PRS
1. One of the output of the Strategy Analysis is the list of unconstrained optimum alternatives for all
road sections (i.e. PRS), which allows the implementing offices to verify the relevance of HDM-4
recommendations against the actual condition of the road in the field.
2. This can be done by running an unconstrained strategy analysis in HDM-4 with the NSM network file
updated in the previous section. This allows to extract the optimum alternative for each NSM cell. As
the HDR provides the link between all PRS and their NSM ID, the optimum alternative for each PRS
can therefore be deducted.
F.1 Run unconstrained Strategy Analysis of NSM in HDM-4
1. Import in HDM-4, hit the “Import” button and select the file NSM_Network_YY_02
created in Section E.3.
2. Hit the button “Next” until the following windows:
50
3. Repeat the same operation to import the file NSM_Strategy_YY_02.
4. Open the NSM_Strategy_15_02 item in HDM-4

5. Verify that the strategy file is linked to the right network file, the start year and analysis period (20
years) and set the discount rate at 15%.
51
6. In “Study Sections”, check that all the sections are selected and that the traffic growth set is “ALL”
for all NSM cells.
52
7. Go to “Generate Strategy” and hit the “Run Setup” button

• Select a folder to save HDM-4 output (rundata.mdb file)
• Check the boxes to exclude annual vehicle data and vehicle period data
53
8. Hit the “Start” button and run the analysis

9. At the end of the analysis, go to “Generate Report” and open the Report named “Optimum Sections
Alternatives”
54
10. Click on the “Export” button and select the following options:
11. Save the Excel Spreadsheet under the name Optimum Section Alternatives (Unconstrained
Budget)_YY_02.xls.
55
F.2 Assign optimum alternative to PRS
1. Open the file Optimum Section Alternatives (Unconstrained Budget)_YY_02.xls created in

Section F.1.
2. Delete the rows from 1 to 16 and restructure the header to enter in a single row. Apply a filter to mask
empty rows:
3. Insert one column after the Column “Section” with the header “NSM ID”
56
4. Open the spreadsheet NSM Populating Tool_SECTIONS used in Section E.1 and open the worksheet
“SECTIONS”. Copy and Paste the columns G and H in a worksheet of the spreadsheet created in Step
1 in the order SECT_NAME, SECT_ID.
5. In the new column “NSM ID” of the worksheet created in step 1, apply a “vlookup” formula on the
table created in step 4 to collect the corresponding SECT_ID.
6. Open the HDR created in Section C.2.

7. Apply a filter and unselect the rows with “TRUE” in the column “Exclude if True”
57
8. Unselect rows with no traffic data
9. Hide columns between the column “Location” and the column “NSM_ID”, then all columns after the
column “NSM_ID”
10. Insert a new column named “Optimum Alternative” and apply a vlookup formula in the table created
in step 5 to collect the column “Alternative Desc.”
58
11. Repeat the step above to insert a column which collects values from the column “Net Present Value”
of the table created in step 5:
59
G. RUN STRATEGY ANALYSIS INTERFACE

G.1 Set Parameters of Confirm (HDM-4 Interface) – Criteria for NSM-
SPA
G.1.1 HDM-4 System Settings
1. Open Confirm (HDM-4 Interface), and open the HDM-4 System Settings, General tab.
2. Set the maximum NSM length as per Section C.4 (note that in Confirm (HDM-4 Interface), like in
RBIA, lengths are expressed in meters)
Length in
meters
3. The substitution of short NSM cells is done via the Homogenization System Settings > Computed
Columns window. Check that the correct substitutions (if needed) were entered by the HDM-4
Interface administrator (IMS).
60
No substitution
required in the
present example
Note: The operation is performed as follows:
• The NSM_ORIG Compute Column defines the NSM ID to be replaced by the alternative
defined in the NSM_ALT Computed Column. They must be updated together as their content
is related by position.
• The contents of the Computed Columns are structured as follows:
NSM_ORIG = "ORIGINAL_NSM1 , ORIGINAL_NSM2 , ORIGINAL_NSM3 ,….”
NSM_ALT = "ALTERNATIVE_NSM1 , ALTERNATIVE _NSM2 , ALTERNATIVE _NSM3
,….”
• In the following example the first NSM ID in the NSM_ORIG list, “AHG21FF”, would be replaced
by "AHG21FP” and the third NSM ID in the NSM_ORIG list, “CMD22FG”, would be replaced by
“CMD22FF”.
NSM_ORIG = ............... "AHG21FF, AHG21FG ,CMD22FG ,CMD22FP, AHG42PG , AHG42FG"
NSM_ALT = ................. "AHG21FP , AHG21FP , CMD22FF , CMD22FB , AHG42PF, AHG42FF"
G.2 Strategy Analysis Interface

G.2.1 Strategy Analysis Interface
1. When this is done, go back to the Strategy Analysis Interface
61
2. Select the NSM input file updated in Section E.3: NSM_Network_YY_02.mdb

3. Set the NSM output File name as: NSMSPA_ RN_YY_02.mdb.
4. Check the Maintenance Alternatives box
5. Set the start year as the first year of the planning period
6. Set the three drop box menus as follows:
o Number of budget periods: 11
o Budget Period Length: 20
o Delay maintenance by: 0
7. Select the Strategy Input File created in Section D: NSM_Strategy_YY_01.mdb
8. Select the Strategy Output File name as: NSMSPA_STR_YY_01
9. Hit the “Run” button

10. In the message at the end of the process, the number of NSM cells which have been split (or
“cloned”) is given.
1
Note: The definition of Number of Budget Period and Budget Period Length at this stage only affects the
multiplication of alternatives by the Confirm Interface (refer to the PMS Design Report, 2014 for more
details). Hence, it is not connected to the number and length of budget periods used to perform the
strategy analysis in HDM-4. As the Strategy Input File does not require any multiplication of alternatives,
the Number of Budget Periods is set at 1.
62
63
H. REVIEW STRATEGY ANALYSIS INTERFACE

OUTPUTS
H.1 Check total number of NSM cells
1. First, save a backup version of the files NSMSPA_RN_YY_01.mdb and
NSMSPA_STR_YY_01.mdb in a “Backup” folder in order to keep an original copy of the SPA
Interface outputs.
2. Open the file named NSMSPA_ RN_YY_01.mdb in Access and open the SECTIONS table. NSM
cells which were longer than the specified “NSM maximum section length” have now been split into
two or more NSM cells with the same characteristics (or clones).
3. Check that:
• NSM cells longer than the set maximum have been cloned properly (i.e. there is no more
NSM cells longer than the set maximum)
• Clones have the same properties as original cell
• All cells programmed for substitution have been substituted properly
• The number of NSM cells is smaller than 400.
H.2 Correction of clones length

1. Confirm (HDM-4 Interface) clones the NSM cells longer than the set maximum by creating as many
similar cells (clones) as required with the maximum length, and one cell with the remaining length.
For instance:
• 1,205km long CMD22BF with a maximum length of 600km would be cloned as follows:
i. CMD22BF: 600km
ii. CMD22BF-1: 600km
iii. CMD22BF-2: 5km
2. The lengths of the clones have therefore to be corrected to be evenly distributed. However, clones
cannot have the exact same length. The following method should therefore be followed:
64
3. Sort from “A to Z” the SECT_ID column to make sure that clones are on top of
each other.
4. Copy the SECT_ID and LENGTH cells of all cloned cells and paste them on a new spreadsheet
5. Create a new column named “Corrected Length” and calculate the new length as per the following
procedure:
• If 2 clones only (for example AMD22FG and AMD22FG-1):
(௅௘௡௚௧௛ಲಾವమమಷಸ ା ௅௘௡௚௧௛ಲಾವమమಷಸషభ )ିଵ
i. Corrected Length of AMD22FG:
ଶ
ii. Corrected Length of AMD22FG-1: (LengthAMD22FG + LengthAMD22FG-1)-Corrected LengthAMD22FG

• If 3 clones (for example CMD22GP, CMD22GP-1 and CMD22GP-2):
(௅௘௡௚௧௛ి౉ీమమృౌ ା ௅௘௡௚௧௛ి౉ీమమృౌషభ ା ௅௘௡௚௧௛ి౉ీమమృౌషమ )ିଶ
i. Corrected Length of CMD22GP:
ଷ
(௅௘௡௚௧௛ి౉ీమమృౌ ା ௅௘௡௚௧௛ి౉ీమమృౌషభ ା ௅௘௡௚௧௛ి౉ీమమృౌషమ )ାଶ
ii. Corrected Length of CMD22GP-1: ଷ
iii. Corrected Length of CMD22GP-2: Total LengthCMD22GP clones - Corrected LengthCMD22GP - Corrected
LengthCMD22GP-1
6. Replace the values from “corrected length” in the corresponding LENGTH column of the SECTION
table of NSMSPA_RN_YY_01.mdb.
65
7. Save and close the mdb file under the name NSMSPA_RN_YY_02.mdb
H.3 Update of Strategy Input File

1. Open the file NSMSPA_STR_YY_01.mdb in Microsoft Access and open the table “Strategy” (end of
the list of tables).
2. Update the following entries:

• NAME: Change “NSMSPA_STR_YY_01” with “NSMSPA_STR_YY_02”
• NETWORK: Change “NSMSPA_RN_YY_01” with “NSMSPA_RN_YY_02”
3. Save and close the mdb file under the name NSMSPA_STR_YY_02.mdb
66
I. RUN STRATEGY ANALYSIS IN HDM-4 AND

PERFORM BUDGET OPTIMIZATION
I.1 Import revised Strategy Analysis Interface Outputs into HDM-4

1. Go back to the HDM-4 Workspace
2. Click on the Import button , then Browse

3. Select the file NSMSPA_ RN_YY_02.mdb created in Section H.2
4. Click “Next” then “Finish”
5. Repeat steps 2 to 4 with NSMSPA_STR_YY_02.mdb created in Section H.3.
67
I.2 Run Strategy Analysis in HDM-4

1. Open NSMSPA_STR_15_01 within HDM-4.
2. Check that:
• The correct road network is assigned
• Tec correct Vehicle Fleet is assigned
• Start Year
• Analysis Period of 20 years (default SETH study period)
• Discount rate of 15% (unless otherwise specified)
3. Go to study section and make sure that:

• All sections (NSM cells) are selected for the study
68
• All sections have “ALL” traffic growth type

• The total number of sections does not exceed 400
4. Go to “Specify Alternatives”. Check that all sections have works alternatives, corresponding to the
Strategy Input file (perform a random check on a couple of sections).
5. Go to “Generate Study” and open the “Run Setup” Menu.
69
• Create a directory for Run Data Export Directory with the name SPA_STR_YY_01
• Check “Exclude annual vehicle data” and “Exclude vehicle period data” (these data will
not be reported in the rundata file, which avoids reaching the Microsoft Access limit of 2
GB).
To be checked
6. Hit the “Start” button

7. Once the study is completed, go to “Unconstrained Programme” and check the capital cumulated cost
at the end of the 6-year period. Note this value as the Unconstrained Capital Cumulated Cost at 6 year
(UCCC6).
70
I.3 Perform Budget Optimization

1. Go to “Perform Budget Optimisation” and create the following scenarios (use the option “Copy
budget scenario…” after creating the “100% capital cost scenario”):
• Unconstrained Optimum:
Start of Year End of Year Capital Budget
1 20 9999999.000000
• Practical Optimum:
1 1 UCCC6/6
2 2 UCCC6/6
3 3 UCCC6/6
4 4 UCCC6/6
5 6 2*UCCC6/6
7 20 9999999.000000
• 90% Optimum:
1 1 90%* UCCC6/6
2 2 90%* UCCC6/6
71
3 3 90%* UCCC6/6
4 4 90%* UCCC6/6
5 6 2*90%* UCCC6/6
7 20 9999999.000000
• 75% Optimum:
1 1 75%* UCCC6/6
2 2 75%* UCCC6/6
3 3 75%* UCCC6/6
4 4 75%* UCCC6/6
5 6 2*75%* UCCC6/6
7 20 9999999.000000
• 50% Optimum:
1 1 50%* UCCC6/6
2 2 50%* UCCC6/6
3 3 50%* UCCC6/6
4 4 50%* UCCC6/6
5 6 2*50%* UCCC6/6
7 20 9999999.000000
2. Select all scenarios and hit the “Perform Budget Optimization” Button
72
3. Then save the Strategy analysis and close HDM-4
73
J. IMPORT HDM-4 RESULT INTO SETH AND

PREPARE SPA VISUALS
J.1 Import HDM-4 result into SETH
1. Open the SETH spreadsheet (Excel file named SETH_Template)
2. In the Main Menu worksheet:

• Enter in step 1) the discount rate used for the HDM-4 study
• Enter in step 2) the directory where the rundata file created in Step 5 of Section I.1 was saved
• Hit the “Collect Results button (This operation takes more than one hour and Excel may be
“not responding”)
• Go to “Evaluation Options”
3. Note that there is no need to update the worksheet “Evaluation Option”
4. Go back to the “Main Menu” tab and hit the “Evaluate Scenarios” button
5. Save the SETH file as SETH_YY_01.
J.2 Prepare SPA Report visuals for the National Network

1. In the SETH_YY_01.xls file, go to the “Charts” worksheet
74
2. Copy and paste the charts to update the SPA Report (See Appendix in Appendix B)
J.3 Prepare SPA Report visuals per Planning Unit, Region and Road
Class
J.3.1 Calculate NSM length per Planning Unit
1. Open the HDR extracted in Section C
2. Go to Insert > Pivot Table (See Section C.4.1)
3. Set the PivotTable Fields as follows:
• Drag and Drop “PLANNING_UNIT” to the “ROWS” box
• Drag and Drop “NSM_ID” in the “ROWS” box (under “PLANNING_UNIT”)
• Drag and drop “SubSections_Length” to the “VALUES” box and change “Count” to
“Sum” in “Value Field Settings”
• Drag and Drop “Exclude_If_True” in the “FILTER” box
• Drag and Drop “AADT(RAAD_RI41)” in the “FILTER” box
75
4. Close PivotTable Fields and in the drop list menu of “Exclude_If_True”, check “Select Mupltiple
Items” and uncheck “True”
5. In the drop list menu of “AADT(RAAD_RI41)”, check “Select Multiple Items” and unselect “Blank”
6. Click anywhere in the pivot table and go to Design. Set the following parameters:
• Subtotals > Do not show subtotals
76
• Grand Totals > Off for Row and Columns
• Report Layout > Repeat All Item Labels
7. Select the resulting table, copy and paste the values in a new worksheet
8. Create a new column and calculate the total length in kilometers (divide the column “Total” by 1,000)
77
9. Copy the column D (Total in km) and paste it over the column “Total” using “Paste Value”
10. Delete column D and save the worksheet as LengthNSM_PU_YY_01.xls.
J.3.2 Calculate NSM length per Region

1. Repeat the steps of Section J.3.1 with the item “Area_Code” instead of “PLANNING_UNIT” in the
box “ROWS”:
78
2. Save the table with the corrected length (per km) under LengthNSM_Reg_YY_01.xls
J.3.3 Calculate NSM length per Road Class

3. Repeat Section J.3.1 with the item “Classification” instead of “PLANNING_UNIT” in the box
“ROWS”:
79
4. Save the table with the corrected length (per km) under LengthNSM_Class_YY_01.xls
J.3.4 Prepare Visuals with SETH
1. Open the file SETH_YY_01.xls created in Section J.1.
2. Copy and paste the tables created in Sections J.3.1, J.3.2 and J.3.3 respectively in the worksheets
NSM Length per PU, NSM Length per Region and NSM Length per Class (note that the road
classification system is being updated at the time of this report and the categories will need to be
updated).
3. In the worksheet “Budget Scenario Data”, Select the “Unconstrained Scenario” in the corresponding
box, and Select "Roughness After Works (IRI, m/km)” as Indicator
4. Go to “Output per Region” and select the entire table from the column “Planning Unit”
5. Go to Insert > Insert Scatter (X,Y) or Bubble Chart > Scatter with Straight Lines and Markers
80
6. Resize the chart appropriately and change the vertical axis bounds to fit the scale and update chart in
the SPA Report.
81
7. Repeat Steps 3 to 6 with the other Budget Scenarios and with “Output per Road Class” worksheet.
8. Note that the worksheet “Output per Planning Unit” is used in the Programme Analysis process to
obtain the capital expenditure per Planning Unit for the defined budget.
82
K. PREPARATION OF SPA REPORT

K.1 Analysis of SETH Output
1. The key output from SETH is the curve presenting the evolution of the average roughness of the
network for each budget scenario. The following elements should be noted:
• Indicate the evolution of roughness after 6 years and after 20 years for the “base
alternative”
• Identify or estimate the minimum budget to maintain the network in its current condition
(In the example above, it is the “50% capital cost” budget scenario. If not clear from
SPA, other budget scenarios should be tested)
• Identify the minimum budget scenario which allows the network to reach the “Optimal
Steady State”, where it is maintainable at a lower roughness as the current one. (In the
example below, 90%). Note the differences in the 6 first years.
• Note the impact of other budget scenarios
2. Following this analysis, the Net Present Value (NPV) of each budget scenario and corresponding
Annual Capital Expenditures should be analyzed.
K.2 Prepare SPA Report

1. Update the template given in Appendix B and distribute to the relevant decision makers (See
Planning and Programming Procedures Manual, 2015)
83
L. UPDATE BUDGET OPTIMIZATION IN HDM-4

WITH DEFINED BUDGET
1. In HDM-4, open the strategy file NSMSPA_STR_YY_01 and go to “Perform Budget Optimisation”
window.
2. Create a new budget scenario with the following structure:
1 1 Defined Budget for next FY
5 6 2 * Defined Budget for next FY
7 20 9999999.000000
3. Hit the “Perform Budget Optimisation” button

4. Save and close NSMSPA_STR_15_01 in HDM-4 and close HDM-4.
84
M. IMPORT HDM-4 RESULT INTO SETH AND

DETERMINE BUDGET PER PLANNING UNIT
M.1 Import HDM-4 result into SETH
1. Open the file SETH_YY_01 created in Section J.
2. Enter the directory of the HDM-4 rundata.mdb file (same as in Section J.1) and hit the “Collect
Results” button
3. Go back to the “Main Menu” tab and hit the “Evaluate Scenarios” button.
4. Save the SETH file as SETH_YY_02.xls.
M.2 Determine Budget Scenario per Planning Unit

1. In SETH_YY_02, go to “Budget Scenarios Data” worksheet and set “Defined Budget” as Budget
Scenario and “Financial Capital Cost (MPhP)” as Indicators.
2. Go to “Output per Planning Unit” worksheet
85
3. The Budget Scenario for each PU is to be built as follows:

1 1 Sum of Financial Capital Cost for the
relevant PU from Year 1 to 6 divided by 6
7 12 9999999 (no constraint).
4. The list of PU in the worksheet “Output per Planning Unit” is the comprehensive list of
Congressional Districts. Therefore some PU may not have any budget allocated, e.g. because their
network is entirely composed of Urban Metropolitan roads. These PU should be discarded from the
study.
5. If HDM-4 does not allocate any budget for the first 6 years, a solution should be discussed by DPD
on a case by case basis.
86
N. RUN PROGRAMME ANALYSIS INTERFACE

N.1 Configure HDM-4 Interface – Check Exclusion Settings
1. Open the Homogenisation System Settings tab in the RBIA HDM-4 Interface. In CURRENT_PU,
Select the code of the Planning Unit to be analyzed (See Appendix A for the full list).
2. Check the following settings:
Expression Name Setting/Expression Description
PLANNING_UNIT {RCON_RI01} Sets congressional district as PU
GENERAL_EXCLUSIONS “Y” Exclude all segments outside selected PU
GRAVEL_EXCLUDE “Y” Gravel and Earth roads are excluded
URBAN_EXCLUDE “Y” Urban Metropolitan roads are excluded
3. The other fields should not be changed as part of the regular planning process.
87
N.2 Define Current Planning Unit
1. Open the Data Query Qualification and look for the Data Source: PMS_07 – Sections in
Current Planning Unit.
2. Double click on “Named Selection” and select the SPA Named Selection prepared in
Section B. Set the Effective date as per Section B Step 7.
3. Click “OK”. The list of all the PRS included in the selected PU is displayed. Click on the
Named Selection icon
88
4. Define the Code and Name of the Named Selection following instructions from the Appendix G of
PMS Operations Guide, August 2014:
PUXXXX01
Where:
• XXXX: Congressional District Attribute Value Code (Planning Unit)
• 01 Sequential Number
5. Define “Where Selection already exists” as “Replace”, then hit “OK”
N.3 Programme Analysis Interface

1. Open the Programme Analysis Interface
2. Select Named Selection created in Section N.2.
3. NSM Input File: Select the NSM_Network_YY_02.mdb file that was updated in Step E (Do not use
the NSM-SPA_Network file).
4. Name the Ouput file: The output file will be a HDM-4 network file containing all the PRS for the
selected Planning Unit (PU). In accordance with the naming conventions, it should be:
PRS_RN_YY_XXXX_01.mdb
With:
• YY: Year of the Study
• XXXX: Code of the Current Planning Unit
5. Check the Programme box
6. Set the three drop box menus as follows:
o Number of budget periods: 1
o Budget Period Length: 20
o Delay maintenance by: 0
7. Strategy Input File: Select the NSM_Strategy_YY_02.mdb file that was created in Step in Step E.
8. Name the Ouput file: The output file will be a HDM-4 Programme file related to the newly created
network. The following naming convention should be applied:
PRS_PRG_YY_XXXX_01.mdb
With:
• YY: Year of the Study
89
• XXXX: Code of the Current Planning Unit

9. Run the Analysis

10. At the end of the analysis, a window similar to the following is displayed:
Number of generated PRS
PRS with missing traffic

data not exported
90
O. RUN PROGRAMME ANALYSIS WITH BUDGET

CONSTRAINT IN HDM-4
O.1.1 Import Network and Programme files
1. Open the HDM-4 Workspace and import the file
2. Import in that order the newly created PRS_RN_YY_XXXX_01.mdb (remember to always import
the Network File first) and PRS_PRG_YY_XXXX_01.mdb
O.2 Run Programme Analysis

1. Check the Start Year and Road Network and set:
• Start Year: Start of the analysis period (Ditto Section I.2).
• Analysis Period at 12 years
• Discount Rate at 15%
91
2. Check that the Traffic Growth Rate corresponding to the relevant Region has been applied and that all
the sections are selected.
3. Check that the Maintenance Alternative of the PRS have been properly populated.
92
4. Go to “Generate Programme” and open the “Run Setup” menu:

• Create a directory with the name of the programme file (here PRS_PRG_15_2312_01)
• Check “Exclude annual vehicle data” and “Exclude vehicle period data” (these data will
not be reported in the rundata file, which fastens the processing time and limit the size of
the final rundata.mdb).
5. Hit the “Start” button
93
O.3 Impose Defined Budget Constraint

1. Go to “Perform Budget Optimization” and create a new budget scenario as per Section M.2.
2. Hit “Perform Budget Optimisation”
3. The list of priority works under the Defined budget is given in “Optimised Programme” window.
94
95
P. PREPARE PROGRAMME ANALYSIS OUTPUTS

1. Go to “Generate Reports” and open Programme and Strategy Analysis > Work Programme Optimised
by Year
96
2. Click on the “Export” button and select “Excel 8.0 (XLS) (Extended) as format and “Disk file”
as Destination:
3. Save the file under the name PRS_PRG_YY_XXX_01.xls in the eponymous folder (i.e. with the
corresponding rundata.mdb file)
4. Open the PRS_PRG_YY_XXX_01.xls file and use the table to prepare the Programme for the
corresponding Planning Unit (Note that the “Surface Class” column refers to the model used in
HDM-4, and therefore is “Bituminous” for all roads. This column should be removed).
97
APPENDIX A – LIST OF CONGRESSIONAL

DISTRICTS WITH REFERENCE NO.
Region Code Name Region Code Name
CAR 78 ABRA (LONE DISTRICT) CAR 111 APAYAO (LONE DISTRICT)
CAR 124 BAGUIO CITY (LONE DISTRICT) CAR 126 BENGUET (LONE DISTRICT)
CAR 144 IFUGAO (LONE DISTRICT) CAR 178 KALINGA (LONE DISTRICT)
CAR 165 MOUNTAIN PROVINCE (LONE DISTRICT) I 193 ILOCOS NORTE (FIRST DISTRICT)
I 206 ILOCOS NORTE (SECOND DISTRICT) I 223 ILOCOS SUR (FIRST DISTRICT)
I 235 ILOCOS SUR (SECOND DISTRICT) I 264 LA UNION (FIRST DISTRICT)
I 274 LA UNION (SECOND DISTRICT) I 324 PANGASINAN (FIFTH DISTRICT)
I 292 PANGASINAN (FIRST DISTRICT) I 318 PANGASINAN (FOURTH DISTRICT)
I 303 PANGASINAN (SECOND DISTRICT) I 334 PANGASINAN (SIXTH DISTRICT)
I 312 PANGASINAN (THIRD DISTRICT) II 351 BATANES (LONE DISTRICT)
II 364 CAGAYAN (FIRST DISTRICT) II 375 CAGAYAN (SECOND DISTRICT)
II 388 CAGAYAN (THIRD DISTRICT) II 403 ISABELA (FIRST DISTRICT)
II 435 ISABELA (FOURTH DISTRICT) II 414 ISABELA (SECOND DISTRICT)
II 426 ISABELA (THIRD DISTRICT) II 462 NUEVA VIZCAYA (LONE DISTRICT)
II 453 QUIRINO (LONE DISTRICT) III 656 AURORA (LONE DISTRICT)
III 484 BATAAN (FIRST DISTRICT) III 491 BATAAN (SECOND DISTRICT)
III 503 BULACAN (FIRST DISTRICT) III 525 BULACAN (FOURTH DISTRICT)
III 510 BULACAN (SECOND DISTRICT) III 518 BULACAN (THIRD DISTRICT)
III 536 NUEVA ECIJA (FIRST DISTRICT) III 563 NUEVA ECIJA (FOURTH DISTRICT)
III 546 NUEVA ECIJA (SECOND DISTRICT) III 555 NUEVA ECIJA (THIRD DISTRICT)
III 578 PAMPANGA (FIRST DISTRICT) III 595 PAMPANGA (FOURTH DISTRICT)
III 582 PAMPANGA (SECOND DISTRICT) III 589 PAMPANGA (THIRD DISTRICT)
III 8135 SAN JOSE CITY (LONE DISTRICT) III 609 TARLAC (FIRST DISTRICT)
III 620 TARLAC (SECOND DISTRICT) III 625 TARLAC (THIRD DISTRICT)
III 635 ZAMBALES (FIRST DISTRICT) III 640 ZAMBALES (SECOND DISTRICT)
IV-A 840 ANTIPOLO CITY (FIRST DISTRICT) IV-A 3080 ANTIPOLO CITY (SECOND DISTRICT)
IV-A 672 BATANGAS (FIRST DISTRICT) IV-A 702 BATANGAS (FOURTH DISTRICT)
IV-A 683 BATANGAS (SECOND DISTRICT) IV-A 691 BATANGAS (THIRD DISTRICT)
IV-A 8137 CAVITE (FIFTH DISTRICT) IV-A 715 CAVITE (FIRST DISTRICT)
IV-A 8136 CAVITE (FOURTH DISTRICT) IV-A 721 CAVITE (SECOND DISTRICT)
IV-A 8139 CAVITE (SEVENTH DISTRICT) IV-A 8138 CAVITE (SIXTH DISTRICT)
IV-A 729 CAVITE (THIRD DISTRICT) IV-A 747 LAGUNA (FIRST DISTRICT)
IV-A 764 LAGUNA (FOURTH DISTRICT) IV-A 751 LAGUNA (SECOND DISTRICT)
IV-A 756 LAGUNA (THIRD DISTRICT) IV-A 788 QUEZON (FIRST DISTRICT)
IV-A 822 QUEZON (FOURTH DISTRICT) IV-A 802 QUEZON (SECOND DISTRICT)
IV-A 809 QUEZON (THIRD DISTRICT) IV-A 838 RIZAL (FIRST DISTRICT)
IV-A 844 RIZAL (SECOND DISTRICT) IV-B 859 MARINDUQUE (LONE DISTRICT)
98

IV-B 871 MINDORO OCCIDENTAL (LONE DISTRICT) IV-B 877 MINDORO ORIENTAL (FIRST DISTRICT)
IV-B 3878 MINDORO ORIENTAL (SECOND DISTRICT) IV-B 883 PALAWAN (FIRST DISTRICT)
IV-B 899 PALAWAN (SECOND DISTRICT) IV-B 9271 PALAWAN (THIRD DISTRICT)
IV-B 918 ROMBLON (LONE DISTRICT) IX 1679 ISABELA CITY (LONE DISTRICT)
IX 3064 ZAMBOANGA CITY (FIRST DISTRICT) IX 3065 ZAMBOANGA CITY (SECOND DISTRICT)
IX 1692 ZAMBOANGA DEL NORTE (FIRST IX 1701 ZAMBOANGA DEL NORTE (SECOND
DISTRICT) DISTRICT)
IX 1709 ZAMBOANGA DEL NORTE (THIRD IX 1729 ZAMBOANGA DEL SUR (FIRST DISTRICT)
DISTRICT)
IX 1742 ZAMBOANGA DEL SUR (SECOND IX 1758 ZAMBOANGA SIBUGAY (FIRST DISTRICT)
DISTRICT)
IX 3075 ZAMBOANGA SIBUGAY (SECOND NCR 20 KALOOKAN CITY (FIRST DISTRICT)
DISTRICT)
NCR 21 KALOOKAN CITY (SECOND DISTRICT) NCR 42 LAS PINAS CITY (LONE DISTRICT)
NCR 60 MAKATI CITY (FIRST DISTRICT) NCR 61 MAKATI CITY (SECOND DISTRICT)
NCR 4188 MALABON CITY (LONE DISTRICT) NCR 64 MANDALUYONG CITY (LONE DISTRICT)
NCR 71 MANILA CITY (FIFTH DISTRICT) NCR 67 MANILA CITY (FIRST DISTRICT)
NCR 70 MANILA CITY (FOURTH DISTRICT) NCR 68 MANILA CITY (SECOND DISTRICT)
NCR 72 MANILA CITY (SIXTH DISTRICT) NCR 69 MANILA CITY (THIRD DISTRICT)
NCR 24 MARIKINA CITY (FIRST DISTRICT) NCR 3082 MARIKINA CITY (SECOND DISTRICT)
NCR 45 MUNTINLUPA CITY (LONE DISTRICT) NCR 4189 NAVOTAS CITY (LONE DISTRICT)
NCR 48 PARANAQUE CITY (FIRST DISTRICT) NCR 3079 PARANAQUE CITY (SECOND DISTRICT)
NCR 51 PASAY CITY (LONE DISTRICT) NCR 27 PASIG CITY (LONE DISTRICT)
NCR 4682 QUEZON CITY (FIFTH DISTRICT) NCR 14 QUEZON CITY (FIRST DISTRICT)
NCR 17 QUEZON CITY (FOURTH DISTRICT) NCR 15 QUEZON CITY (SECOND DISTRICT)
NCR 3571 QUEZON CITY (SIXTH DISTRICT) NCR 16 QUEZON CITY (THIRD DISTRICT)
NCR 30 SAN JUAN CITY (LONE DISTRICT) NCR 4187 TAGUIG (SECOND DISTRICT)
st
NCR 4186 TAGUIG-PATEROS – 1 DISTRICT NCR 39 VALENZUELA CITY (FIRST DISTRICT)
NCR 3040 VALENZUELA CITY (SECOND DISTRICT) V 974 ALBAY (FIRST DISTRICT)
V 981 ALBAY (SECOND DISTRICT) V 987 ALBAY (THIRD DISTRICT)
st nd
V 8144 CAMARINES NORTE – 1 DISTRICT V 8145 CAMARINES NORTE – 2 DISTRICT
V 8146 CAMARINES SUR (FIFTH DISTRICT) V 1019 CAMARINES SUR (FIRST DISTRICT)
V 1052 CAMARINES SUR (FOURTH DISTRICT) V 1030 CAMARINES SUR (SECOND DISTRICT)
V 1041 CAMARINES SUR (THIRD DISTRICT) V 1064 CATANDUANES (LONE DISTRICT)
V 1080 MASBATE (FIRST DISTRICT) V 1087 MASBATE (SECOND DISTRICT)
V 1095 MASBATE (THIRD DISTRICT) V 1109 SORSOGON (FIRST DISTRICT)
V 1117 SORSOGON (SECOND DISTRICT) VI 1133 AKLAN (LONE DISTRICT)
VI 1155 ANTIQUE (LONE DISTRICT) VI 3054 BACOLOD CITY (LONE DISTRICT)
VI 1178 CAPIZ (FIRST DISTRICT) VI 1186 CAPIZ (SECOND DISTRICT)
VI 1201 GUIMARAS (LONE DISTRICT) VI 1251 ILOILO (FIFTH DISTRICT)
VI 1215 ILOILO (FIRST DISTRICT) VI 1242 ILOILO (FOURTH DISTRICT)
VI 1223 ILOILO (SECOND DISTRICT) VI 1232 ILOILO (THIRD DISTRICT)
VI 3047 ILOILO CITY (LONE DISTRICT) VI 1295 NEGROS OCCIDENTAL (FIFTH DISTRICT)
99

VI 1272 NEGROS OCCIDENTAL (FIRST DISTRICT) VI 1288 NEGROS OCCIDENTAL (FOURTH DISTRICT)
VI 1278 NEGROS OCCIDENTAL (SECOND VI 1302 NEGROS OCCIDENTAL (SIXTH DISTRICT)
DISTRICT)
VI 1282 NEGROS OCCIDENTAL (THIRD DISTRICT) VII 1317 BOHOL (FIRST DISTRICT)
VII 1333 BOHOL (SECOND DISTRICT) VII 1348 BOHOL (THIRD DISTRICT)
VII 1415 CEBU (FIFTH DISTRICT) VII 1374 CEBU (FIRST DISTRICT)
VII 1405 CEBU (FOURTH DISTRICT) VII 1381 CEBU (SECOND DISTRICT)
VII 1427 CEBU (SIXTH DISTRICT) VII 1397 CEBU (THIRD DISTRICT)
VII 2331 CEBU CITY (FIRST DISTRICT) VII 2332 CEBU CITY (SECOND DISTRICT)
VII 8140 LAPU-LAPU CITY (LONE DISTRICT) VII 1443 NEGROS ORIENTAL (FIRST DISTRICT)
VII 1453 NEGROS ORIENTAL (SECOND DISTRICT) VII 1462 NEGROS ORIENTAL (THIRD DISTRICT)
VII 1475 SIQUIJOR (LONE DISTRICT) VIII 1490 BILIRAN (LONE DISTRICT)
VIII 1503 EASTERN SAMAR (LONE DISTRICT) VIII 1574 LEYTE (FIFTH DISTRICT)
VIII 1536 LEYTE (FIRST DISTRICT) VIII 1566 LEYTE (FOURTH DISTRICT)
VIII 1545 LEYTE (SECOND DISTRICT) VIII 1560 LEYTE (THIRD DISTRICT)
VIII 1589 NORTHERN SAMAR (FIRST DISTRICT) VIII 1604 NORTHERN SAMAR (SECOND DISTRICT)
VIII 1620 SAMAR (FIRST DISTRICT) VIII 1631 SAMAR (SECOND DISTRICT)
VIII 1652 SOUTHERN LEYTE (LONE DISTRICT) X 1782 BUKIDNON (FIRST DISTRICT)
X 4752 BUKIDNON (FOURTH DISTRICT) X 1791 BUKIDNON (SECOND DISTRICT)
X 1798 BUKIDNON (THIRD DISTRICT) X 1859 CAGAYAN DE ORO CITY (FIRST DISTRICT)
X 3081 CAGAYAN DE ORO CITY (SECOND X 1811 CAMIGUIN (LONE DISTRICT)
DISTRICT)
X 8141 ILIGAN CITY (LONE DISTRICT) X 1995 LANAO DEL NORTE (FIRST DISTRICT)
X 2004 LANAO DEL NORTE (SECOND DISTRICT) X 1821 MISAMIS OCCIDENTAL (FIRST DISTRICT)
X 1832 MISAMIS OCCIDENTAL (SECOND X 1846 MISAMIS ORIENTAL (FIRST DISTRICT)
DISTRICT)
X 1858 MISAMIS ORIENTAL (SECOND DISTRICT) XI 1879 COMPOSTELA VALLEY (FIRST DISTRICT)
XI 1885 COMPOSTELA VALLEY (SECOND XI 2312 DAVAO CITY (FIRST DISTRICT)
DISTRICT)
XI 2313 DAVAO CITY (SECOND DISTRICT) XI 2319 DAVAO CITY (THIRD DISTRICT)
XI 1976 DAVAO DEL NORTE (FIRST DISTRICT) XI 2299 DAVAO DEL NORTE (SECOND DISTRICT)
XI 1907 DAVAO DEL SUR (FIRST DISTRICT) XI 1915 DAVAO DEL SUR (SECOND DISTRICT)
XI 1929 DAVAO ORIENTAL (FIRST DISTRICT) XI 1936 DAVAO ORIENTAL (SECOND DISTRICT)
XII 2050 COTABATO (FIRST DISTRICT) XII 2060 COTABATO (SECOND DISTRICT)
XII 1153 COTABATO (THIRD DISTRICT) XII 2222 MAGUINDANAO (FIRST DISTRICT)
XII 1947 SARANGANI (LONE DISTRICT) XII 1960 SOUTH COTABATO (FIRST DISTRICT)
XII 1965 SOUTH COTABATO (SECOND DISTRICT) XII 1813 SULTAN KUDARAT (FIRST DISTRICT)
XII 1814 SULTAN KUDARAT (SECOND DISTRICT) XIII 2079 AGUSAN DEL NORTE (FIRST DISTRICT)
st
XIII 2082 AGUSAN DEL NORTE (SECOND DISTRICT) XIII 8142 AGUSAN DEL SUR – 1 DISTRICT
nd
XIII 8143 AGUSAN DEL SUR – 2 DISTRICT XIII 2118 SURIGAO DEL NORTE (FIRST DISTRICT)
XIII 2135 SURIGAO DEL NORTE (SECOND DISTRICT) XIII 2153 SURIGAO DEL SUR (FIRST DISTRICT)
XIII 2168 SURIGAO DEL SUR (SECOND DISTRICT)
100
APPENDIX B – STRATEGIC PLANNING

ANALYSIS REPORT – TEMPLATE
Introduction
1. Strategic Planning Analysis (SPA) clarifies the long term impact of different budget scenarios and
maintenance/rehabilitation policies on the performance of the National Road Network. The
performance that can be analyzed includes the average pavement conditions of the network, costs to
the road agency and the users, and to the society as a whole. Such information is essential in devising
long term and medium term investment and management strategies for road network assets.
2. SPA deals only with the Asset Preservation of the paved National Road Network and does not deal
with Network Development such as paving of gravel roads or construction of new road links.
3. The National Road Network is analyzed through a Network State Matrix (NSM), which is composed
of “cells” representing each category of roads based on their pavement type, traffic flow pattern and
volume, roughness and pavement condition.
4. The role of SPA can be summarized as follows:
• SPA clarifies the relationship between what we can buy with how much we spend
(investment for road asset preservation vs. network performance and user costs), and
facilitates the decision about how much to spend;
• For a given budget scenario, identifies the optimum maintenance strategy (solution catalogue)
for the network;
• Calculates approximate quantities, costs and benefits;
• Identifies the most efficient allocation of resources among planning units (such as Regions or
Districts), or road classes or work categories; and
• Provides guidance for medium-term planning and annual programming.
• SPA is the first step of the Pavement Management process in DPWH. The budget constraints
and maintenance standards defined at this stage will be applied to the program analysis.
5. This report presents the main findings and recommendations of the Strategic Planning Analysis for
the Financial Year 2016, along with the assumptions and hypotheses which were taken to run it.
B. Network Analysis
6. SPA is conducted on the national network, minus the following exclusion (See PMS Operations
Guide):
• Abandoned road sections
• Road sections without following essential data:
a. Traffic data
b. Pavement type data
c. Condition data (Roughness and Surface Condition)
d. Number of lanes
e. Directionality
• Road sections with a Surface Type of ‘Gravel’ or ‘Earth’
• Road sections with an Environment of “Urban (Metropolitan)”
• This was done by preparing a Named Selection in the RBIA with the Data Source:
PMS_01 - All Live Road Sections.
101
7. December 15th, 2014 was considered as the cut-off date for RBIA data (and therefore December 16th,
2014 was considered as the “Effective Date” when preparing the Named Selection).
8. This Named Selection was used to run the Confirm (HDM-4 Interface). It was then cut into
homogenous sections (Planning Road Sections, PRS), which are assigned to a cell in the Network
State Matrix (NSM). PRS with the characteristics presented in paragraph 5 are excluded of the
analysis. Table 1 and Figure 6 present the characteristics of the resulting “SPA Network” after
running Confirm (HDM-4 Interface).
9. It can be noticed that 22% of the network of the Named Selection are further excluded of the analysis
(more than 7,000 km). The total length of the network covered by SPA is therefore 25,500
kilometers. Traffic data is missing for 3% of the network, i.e. excluding almost 1,000km. Finally,
concrete roads represent more than 66% of the studied network.
Table 1 -
SPA Network characteristics
Total Length of Named Selection (in km): 32,527
Total Length of Excluded PRS: 7,027
Gravel and Earth roads 4,770
Urban (Metropolitan Roads) 1,272
Traffic Data missing 985
Surface Condition and Roughness missing 0
Total Length of Non Excluded PRS (in km): 25,500
Total length Concrete PRS (in km) 16,719
Total Length Asphalt PRS (in km) 8,781
Figure 6 -
SPA Network characteristics
10. PRS are assigned to NSM cells according to (inter alia) their roughness and surface condition. Two
scores from “Good” to “Bad” are given to each PRS in accordance to their IRI (roughness score) and
a set of thresholds of pavement defects (surface condition score). See PMS Configuration Report -
Homogenization and HDM-4 System Settings for more details.
11. Figure 7 and Figure 8 present the distribution of the roughness and surface condition score for each
pavement type. The following can be observed:
102
• 88% of the asphalt network is scored as “fair” or “good”, i.e. with an IRI smaller than 5
• Only 2% of the asphalt network is scored as “bad”, i.e. with an IRI greater than 7.
• 63% of the concrete network is scored as “poor” or “bad”, i.e. with an IRI greater than 5.
• Only 8% of the concrete network if considered as good
• Both the asphalt and concrete network and relatively proportionally distributed among
the four categories of surface condition, which is the objective when defining the scoring
thresholds.
Figure 7 -
Distribution of Roughness Score (in km)
Asphalt Concrete
893 217 1,426
3,638 2,998
5,016
4,199 8,097
Good Fair Poor Bad Good Fair Poor Bad
Figure 8 -
Distribution of Surface Condition Score (in km)
Asphalt Concrete
1,366 2,703 5,435

4,005
1,474 3,421
2,103 5,978
Good Fair Poor Bad Good Fair Poor Bad
12. Although the thresholds to determine the surface condition scores were specified so as to distribute
the network among the four categories (and hence differs from the VCI), they provide a relevant tool
to estimate the condition of the pavement. Figure 9 below compares the distribution of roughness
scores against surface condition scores. It can be observed that:
• A significant length of the concrete network (almost 700km) is scored as “good” for its
surface condition, and “bad” for its roughness. This was observed in 2013 and was
explained by inadequate construction methods. This issue was therefore not entirely
addressed in 2014.
103
• A significant length of the asphalt network (more than 550 km) is scored as “good” for its
roughness and “bad” for its surface condition. This incoherency is harder to justify, as a
road in poor condition can reasonably be expected to present a high IRI. These roads
require further investigation, and a revision of the thresholds to assign surface condition
scores may be necessary.
Figure 9 -
Distribution of Roughness vs. Surface Condition scores (in km)
Concrete
3,000,000
2,500,000
2,000,000
B
1,500,000
P
1,000,000
F
500,000
G
0
G F P B
Asphalt
2,000,000
1,500,000
B
1,000,000
P
500,000 F
G
0
G F P B
Vertical: Total Length | Horizontal: Surface Condition Score | Depth: Roughness Score
Parameters and settings
Confirm (HDM-4 Interface)

13. The following Settings were used to run the Confirm (HDM-4 Interface):
104
Table 2 -
Confirm (HDM-4 Interface) Settings
Setting Description
Effective Date 12/16/2014
Named Selection STR15_01
Minimum PRS length (m) 500
Maximum PRS length (m) 1,500
Exclude Gravel (and Earth) Yes
Exclude Urban (Metropolitan) Yes
Maximum NSM length (m) 600,000
Start Year 2016
Number of Budget Periods 1
Budget Period Length (Yrs) 20
Delay Maintenance By (Yrs) 0
HDM-4
14. The following inputs were updated in HDM-4 to run the SPA for FY 2016:
• Vehicle Operating Costs (VOC), Road User Costs (RUC): See Annex 1
• Traffic Growth Rates: See Annex 2
• Capital and Recurrent Construction Costs: See Annex 3
15. The Strategy Analysis in HDM-4 was run with the following parameters:
Table 3 -
HDM-4 Parameters
Setting Description
Start Year 2016
Analysis period 20 years
Optimisation method Maximise NPV
Currency Philippine Peso
Discount rate 15%
105
16. The following budget scenarios were then tested:

Budget
Description
Scenario
Unconstrained Optimised HDM-4 Scenario, without budget constraints over the study period (20
Optimum years)
Budget constraint of 34,000 million pesos per year* during the planning period (6
Practical years), then unconstrained for the rest of the study period. 34,000 was calculated by
Optimum dividing the total capital expenditure of the unconstrained scenario at the end of the
planning period, divided by 6.
Budget constraint of 30,600 million (90% of 34,000) pesos per year* during the
90% Optimum
planning period (6 years), then unconstrained for the rest of the study period.
75% Optimum
50% Optimum
* A single budget constraint for years 5 and 6 of the planning period was prepared (set as twice the annual
budget constraint) due to HDM-4 model limits.
SPA Output Analysis – National Network

17. Figure 10 and Figure 11 overleaf present the evolution of the average network roughness and the
annual capital expenditure for each budget scenario. The following can be observed:
• The Base alternative, which consists of applying routine maintenance and reconstructing
pavement, involves a rapid deterioration of the average network roughness in the next 12
years, at the end of which the average roughness of the network reaches 7, i.e.
categorized as “bad”. It is also noted that it involves high expenditures in the later stage
of the study period, due to the reconstruction works.
• The “50% optimum” budget scenario is the minimum required to maintain the network in
its current condition over the study period. It improves the average roughness by 0.3 IRI
(i.e. 6%) over the 6 first years of the study (planning period), before it deteriorates back
to 5 over the rest of the study period.
• The “unconstrained optimum”, “Practical optimum” and “90% optimum” scenarios all
reach an “Optimal Steady State” at the end of the planning period (in 2021), at an IRI of
around 3.6 / 3.8, from where the average roughness of the network can be maintained
until the end of the study period. The major difference between the three scenarios is the
speed at which this Steady State is attained. This only translates in a difference of 1% of
the total NPV between the “Practical” and “90% optimum” scenarios (See Figure 12).
• The “75% optimum” scenario is too restrictive and does not allow to reach the same
“Optimal Steady State”. The main constraint appears to be in the last year of the planning
period (2020 – 2021), where Figure 11 shows a big drop in capital expenditures. This
only translates in a difference of 4% of the total NPV between the “Practical” and the
“75% optimum” budget scenarios (See Figure 12).
• It is noted that due to the modeling of the budget scenarios, HDM-4 tends to allocate
most of the funds of the years 5 and 6 to a single year (year 5 for “50%” and “75%
optimum” budget scenarios and year 6 for “Practical” and “Unconstrained Optimum”).
106
Figure 10 -
Average Network Roughness Weighted by km
8.0
7.5
7.0
6.5
6.0
IRI
5.5
5.0
4.5
4.0
3.5
3.0
Unconstrained Optimum Practical Optimum 90% Optimum

75% Optimum 50% Optimum Base Alternative
Figure 11 -
Total Financial Road Agency Capital Costs (M PhP)
120,000.0
100,000.0
80,000.0
60,000.0
40,000.0
20,000.0
0.0
Unconstrained Optimum Practical Optimum 90% Optimum

75% Optimum 50% Optimum Base Alternative
107
Figure 12 -
Net Present Value of Economic Society Benefits, NPV (M PhP) and Internal Rate of
Return (%)
390,000.0 70.0%
380,000.0
60.0%
370,000.0
50.0%
360,000.0
350,000.0 40.0%
340,000.0 30.0%
330,000.0
20.0%
320,000.0
310,000.0 10.0%
300,000.0 0.0%
Unconstrained Practical 90% Optimum 75% Optimum 50% Optimum
Optimum Optimum
Net Present Value (M US$) Internal Rate of Return (%)
18. Figure 13 below shows the annual financial capital costs for each budget scenario for the planning
period (6 first years), the rest of the study period and the total study period. The annual investment
after the planning period increases in proportion to the constraint applied on the budget during the
first 6 years. For instance, the annual investment between 2022 and 2035 is 25% more important for
the “75% optimum” budget scenario than for the “Practical optimum” budget scenario. As a result,
the average annual expenditure over the entire study period (i.e. the total investment over the 20 year
study period) is almost similar for the “Practical”, “90%” and “75% optimum” budget scenarios.
Figure 13 -
Annual Financial Road Agency Capital Costs (MPhP/year)
40,000.0
35,000.0
30,000.0
25,000.0
20,000.0
15,000.0
10,000.0
5,000.0
0.0
Unconstrained Practical 90% Optimum 75% Optimum 50% Optimum
Optimum Optimum
2016-2021 2022-2035 2016-2035
108
19. The recommendation would therefore be to define the annual budget for 2016 and onward within the
range of 75% to 90% of the optimal budget as per HDM-4 analysis, i.e. between 25,600 and 30,600
million Pesos. This would allow a significant improvement of the national network over the next 6
years, while guaranteeing reasonable economic and financial performances.
SPA Output Analysis – Regional Level

20. Figure 14 to Figure 18 represent the average IRI after work for each regional network. The following
can be observed:
• CAR has an average roughness significantly higher than the other regions. At the end of
the 6 first years (planning period), this gap between CAR and the other regions is greatly
reduced with all budget scenarios but the “50% optimum”.
• At the end of the planning period, with the “Unconstrained optimum”, “Practical” and
“90% optimum” scenarios, all Regions have an average IRI comprised between 3 and
4.5, i.e categorized as “Fair”. With the “75% optimum Scenario”, all Regions have an
average IRI comprised between 3.5 and 5, i.e. categorized as “fair” as well. In return,
with the “50% optimum” scenario, three regions have an average IRI categorized as
“poor” in 2021: CAR, Region IV-B and Region V.
• Over the planning Period for “Practical optimum” scenario, the regions with the most
important improvement of their average roughness are CAR and Region X (-29%) and
Region VI (-28%). NCR and Region IV-A, in return, have their IRI only reduced by
11%.
• Over the planning Period for “75% optimum” scenario, the regions with the most
important improvement of their average roughness are also CAR (-24%), Region X and
Region VI (-18%). Region IV-A, in return, has its IRI only reduced by 5%.
• Over the planning Period for “50% optimum” scenario, the regions with the most
important improvement of their average roughness are NCR (-14%), and CAR (-10%).
The IRI of Region IV-A, in return, increases by 2%.
21. Figure 20 to Figure 24 represent the average roughness after work (IRI) per road class. The following
can be observed:
• East-West Lateral network, in spite of being the second most important class of roads,
has the worst IRI, at the same level as “Secondary Roads”. The average roughness of
these two classes decrease the most significantly during the first six years of the study.
• All the budget scenarios reduce the difference of average roughness between the different
categories over the first six years of the study, except the “50% optimum” budget
scenario.
• This translates a major investment in Secondary Roads (more than 40% of the Financial
Capital Cost) while less than 10% of the capital budget goes to North-South Backbone
roads (see Figure 25).
• Roughness of North-South Backbone is only maintained to its standard during the six
first years with the “50% optimum” budget scenario.
109
Figure 14 -
Average roughness after works (IRI) per Region – Unconstrained Optimum
110
Figure 15 -
Average roughness after works (IRI) per Region – Practical Optimum
111
Figure 16 -
Average roughness after works (IRI) per Region – 90% Optimum
112
Figure 17 -
113
Figure 18 -
114
Figure 19 -
Distribution of Financial Capital Cost (MPhP) per Region over the first six years of the study (2016 - 2021)
115
Figure 20 -
Average roughness after works (IRI) per Road Class – Unconstrained Optimum
Figure 21 -
Average roughness after works (IRI) per Road Class – 100% Optimum
116
Figure 22 -
Figure 23 -
117
Figure 24 -
Figure 25 -
Distribution of Financial Capital Cost (MPhP) per road class over the first six years of the study (2016 - 2021)
118
Annex 1 - Vehicle Operating Costs (VOC) and Road User Costs (RUC)
Insert table
119
Annex 2 – Traffic Growth Rates (TGR)
Insert table
120
Annex 3 – Capital and Recurrent Construction Costs
Insert table
121

Step by Step PMS User Guide PDF

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Step by Step PMS User Guide PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Republic of the Philippines

Department of Public Works and Highways

Pavement Management System

Step by Step User Guide

M.1 Import HDM-4 result into SETH......................................................................85

Figure 2 PMS Documentation Map

A.2 Strategic Planning Analysis Procedure

Confirm (HDM-4 Prepare Named Selection in Confirm (HDM-4 Interface) by

Confirm (HDM-4 Create HDR of the above Named Selection: HDRYY_01.xls. In

Update RUC in Vehicle fleet file (Philippines12.mdb), Works

Microsoft Excel Update NSM_Network_YY_01.mdb with NSM Populating

Run a Strategy analysis in HDM-4 with the updated input files

Confirm (HDM-4 Set the appropriate parameters in Confirm (Homogenisation

Check that the number of NSM cells in NSM-SPA is smaller

Import NSMSPA_RN_YY_02.mdb and

A.3 Programme Analysis Process

In HDM-4 Strategy Analysis module, create one additional budget

Import rundata.mdb into SETH_YY_01.xls. Set SETH parameters,

HDM-4 Import PRS_RN_YY_XXXX_01.mdb and

B. PREPARE NAMED SELECTION FOR

4. Open the data source filter by hitting the filter button

6. Select “PMS_01 – All Live Road Sections”, then hit “OK”

date. Click on the “Save Named Selection” icon

10. Define the Code and Name of the Named Selection:

C. CREATE AND ANALYSE HOMOGENOUS DATA

1. Open the HMD-4 Interface and go first to HDM-4 System Settings

3. The three other fields should not be changed at this stage:

C.1.2 Homogenization Systems Settings

1. Open Homogenization Systems Settings, at Computed Columns Tab

2. Make sure the settings are as follow:

C.2 Create Homogenous Data Report

3. Open the Homogenous Data Report module

7. Define the name of the HDR file (csv format) as

C.3 Analysis of HDR in Microsoft Excel

1. Open the csv file in Microsoft Excel:

C.3.1 Review PMS road related data

C.3.2 PRS Review

3. Calculate the sum of the column “SubSection_Length”

• Check the length against the sum of the column “SubSection_Length”

C.4 Definition of NSM-SPA

2. Go to Insert > Pivot Table

3. Leave the default options and click “OK”

5. Then drag and drop “SubSection_Length” in the “VALUES” box:

7. Replace “Count” with “Sum”

12. Open a new Worksheet and “Paste Values”

C.4.2 Determine the Maximum NSM length

1. Sort the column “Total” from “Largest to Smallest”

C.4.3 Control the total number of NSM cells

NSM_ORIG* Length (m) NSM_ALT** Length (m)

AVH21BG 33.00 AVH21BF 141.00

D. UPDATE HDM-4 WORKSPACE AND EXPORT

2. There should be:

D.1 Update Strategy File

2. Then select “Classic (version 1x style)

3. Open the NSM_Strategy file

6. Go to the “Specify Alternative” Module:

D.2 Update Traffic Growth Rate

1. In HDM-4, open the file Vehicle Fleet (Philippines12) composed of 12 vehicles.

2. Open the “Edit Traffic Growth Sets…” Option

5. Repeat Steps 3 and 4 to update all the sets of TGR

D.3 Update Road User Costs (RUC)

2. Save file under the same name: Philippines12.mdb