9 Network-Level Pavement Management Inventory and Condition Reporting

This chapter presents typical reporting of inventory and condition for network-level management. The reports answer questions such as: what is the pavement inventory by use (e.g., roadway, parking); what is the pavement condition in terms of the PCI, ACN/PCN, roughness, skid, etc.; how does the condition now compare to x years ago; and what would it be y years in the future if only stop-gap (safety) M&R is performed. Example Micro PAVER (ERDC-CERL 2004) reports are presented throughout the chapter.

9.1 Summary of Pavement Inventory and Condition at Last Inspection

This type of report is beneficial for quickly becoming familiar with the pavement network(s). The Micro PAVER "Summary Charts" report performs this function. In this report, a user is allowed to select a different variable for each of the x and y-axis, and the desired chart along with a summary table is automatically produced. The variables for the x and y axis are shown in Figure 9-1. Figure 9-2 is an example report output for a civil aviation airport showing the area-weighted average PCI vs. pavement use. The report can be generated for any selected condition (e.g. PCI, ACN/PCN) and for the entire database or any selected subset.

185

186/ Pavement Management for Airports, Roads, and Parking Lots X-Axis Variables Network ID Branch Use Section Rank Surface Type Section Category Zone Age at Time Report Age at Last Inspection Condition at Last Inspection Y-Axis Variables PCI FOD NEW 60% (AC) FOD PCC 7 Condition Index Cracking Index Distress Index Friction Index Patching Index Roughness Index Rutting Index Structural Index AVG FOD RATING FOD MOD FOD A C L Crack Surface Deformation

Figure 9-1. X and Y-axis Variables in the Micro PAVER "Summary Charts" Report.

mm
^ ^ g - ; ^ - ^ ^ ^ ^ : : g ; 5K{iJ8>*hy*ss

^.^JSSSM

^[v^v^^^^i^^-^j^^B^tSv^^^i^M^^?^.'^-;^*^;; -!V;>' Y'J^J-;,~;' ',y-"\ ?'7<<it *$%$>&{ vYv-<?"v;Y YY?Y;?^iYK'..\Yo>m''xc!^\;-Y'r;:^cY^!^?Y\j

fSiiiag^^
ti^iiWiJNia fTgwre 9-2. Example Micro PAVER "Summary Charts" Output for a Civil Aviation Airport.

9 Network-Level Pavement ManagementInventory and Condition Reporting/187

9.2 Tabular Presentation of Pavement Condition at Last Inspection. This provides a quick tabular presentation of pavement condition at last inspection. The condition presentation can be either at the Section or Branch level along with other relevant data. Micro PAVER reports that address these presentations are the "Section Condition Report" and "Branch Condition Report" shown in Figures 9-3 and 9-4a, respectively. Micro PAVER also provides a summary for all selected data such as shown in Figure 9-4b for the "Branch Condition Report." In this example, one can observe the clear difference between the arithmetic average PCI for the entire selected pavement (79.8) and the area weighted average PCI (62.8). The difference is due to the lower PCI for the runway, which represents about half the pavement area of the airfield pavement. Both the Section and the Branch condition reports can be generated for any selected condition such as FOD, SCI, ACN/PCN and IRI.

Figure 9-3. Example "Section Condition Report."

188 / Pavement Management for Airports, Roads, and Parking Lots

1
I
1

Date:6/8/2004
Branch ID

Branch Condition Report

Pavement Database: NetworkID: Neil Arms
Number of Sum Section Avg Section (R) (Ft) True Area (SqFt)

1 of 2

pa
Use ****** ** standard Deviation

vwm*i
Awre *Ct \

B-26 (RUNWAY 8-26)

5.000.00

100.00

500,000.00

RUNWAY

'

*&&0

150

4140 J

U P R O N (APRON)

2,010.00

88.88

211,459.00

APRON

$2$9

13 65

%%,$<*

iTAXIW(Taxiway)

6.885.00

48.38

302.411.00

TAXIWAY

7?M

21.64 ^

7$.5

Figure 9-4a. Example "Branch Condition Report."

Number of Sections Total Area (SqFt) Arithmetic Average pa Average PCI STO. Weighted Average pa

Use Category

APRON RUNWAY TAXIWAY

8 2 8 18

211,459.00 500,000.00 302,411.00 1,013,870.01

92.00 40.50 77.50 79.83

13.65 1.50 21.64 23.05

91.31 41.40 78.55 62.89

All

Figure 9-4b. Example ''Branch Condition Report" Summary Data.

9 Network-Level Pavement ManagementInventory and Condition Reporting/189

9.3 User-Defined Reports

The Micro PAVER "User-Defined Reports" allow the user to define any desired report and save it for future use. The report can be defined in terms of columns, selected subset of data (rows), and the order of the rows to appear in the report. Also, the generated reports can be exported to Microsoft Excel for further processing or graphing. Figure 9-5 is an example user-defined report showing the PCI, SCI, and FOD at last inspection for the runway and taxiway sections at a civil aviation airport. Such a report is beneficial in analyzing causes of pavement deterioration and correct M&R action. For example, it can be seen that for Section "B" of runway 8-26, the PCI is 39 and the SCI is 100. It is therefore concluded that the major cause of distress is not structural. In this Section, the predominant distresses observed at inspection were raveling and block cracking.
^t^li-lli;ll|lilli|liI^^M

1 m MS User~De$med Reports; Too! -W^: Mmsxseed Heports Jpa-SCI-FOD Network ID | Branch ID NeilArms 1828 Neifefms 18-26 NeflAims APRON NeiiAims APRON NeitArros lAPRON NetlArms APRON NeilAiros I'APRON NeilArms fAPBON NeilAtms APRON NeHArms lAPRON NeilArm* JTAXIW NeiiAims ' ilAXIW NcMirms ^TfAXlW"~ NetlArms !TAXIW NeilArros JTAXIW NeflArms IlAXIW NeiiAims [TAXiW NeilArms j TAXIW Section ID A B A B C D E F 8 H A1 A2 81 B2 83 !C D IE

i^J^
~3
sci|
73. 100. 100 39/ 100. 100. 73. 100/ 100. 100. 100. too/ "72/" 95. 100. 74/' 93/ 82.

\LJBUsi|
FOD 58. 61. 2. 9. 2. 8. 43.

1 1 i

! | ! I i~~

PCI PCI Category j 42. Poor 39. Poor 98 Good 91. Good """98? Hood' ~~~ ~* 32. Good 57 Fair 100. Good 100. Good 100. Good 100. Good 100 Good 65. Fa*r 86. Good 98. Good 6 1 . fair 78. Good ~ 347 Poor

] I
15. 12. 4. 22. 18. 57.

E< Current Report

Deate New Report

Dose

Figure 9-5. Example "User-Defined Report" Showing PCI.

190 / Pavement Management for Airports, Roads, and Parking Lots

9.4 GIS Presentations

Inventory variables and conditions can be presented in a map format. Example inventory variables for map presentations are pavement surface type and pavement rank (e.g. arterial, collector, residential). Example condition indicators are PCI, SCI, FOD, ACN/ PCN, and IRI. When presenting pavement condition indices, the condition ranges and labels need to be defined. For example, the PCI ranges could be 0-55,56-70, and 71-100 with the corresponding labels poor, fair, and good, respectively. An example PCI at last inspection presentation for a small road network is shown in Figure 9-6.

Figure 9-6. Example PCI at Last Inspection.

9 Network-Level Pavement ManagementInventory and Condition Reporting/191

9.5 Pavement Condition Analysis, Past and Future The main purpose of pavement condition analysis is to determine changes in pavement condition. Primarily, how is the pavement condition now compared to the condition x years in the past and what would it be y years in the future if no preventive or major M&R is performed? Past pavement condition (prior to last inspection date) is determined by interpolation using last construction date (last major M&R date) and previous inspections as demonstrated in Figure 9-7. Future pavement condition (after last inspection date) is determined using condition prediction techniques. In Micro PAVER, this is performed using the pavement's assigned condition deterioration family as described in Chapter 7. Condition Analysis is very beneficial to pavement managers since it provides feedback on pavement condition performance (condition over time) as a result of previous M&R budget spending and management policies. Also, being able to compare the condition of pavement sections at a selected date is an important feature since the pavement sections may have been inspected at different times. Figures 9-8a and 9-8b are example condition analyses performed for a civil aviation airport showing both afrequencydiagram and map presentation of PCI condition categories at different dates.

D o A

Inspection Values Interpolated Values Predicted Values

Last Inspection Date Last Construction Date

Year

Figure 9-7. Computation of Past and Future Section PCI.

192 / Pavement Management for Airports, Roads, and Parking Lots

kmMtoFmtmwtoiJMui
EDJ5* I

"'r'''""ll''''"v

*""""

""""""*""

"^

ssL, rM4-

6/t */><*? IWtV*9* S><1$/S58S i>/!?i/?$ft B/VJ*81

^ < r* > ^

-IT" n
s&
M>

\Sd*rif 84 R)

Condition Distribution Graph {% Area)

h

w
33

4?

,
13 1$ 18 8

g/is/aao?

*3

IS' 18 .85

$/*/?ft3 g/tV/WW

**
&4 M U 4 W

Miwimh
S>/lVKi>

:>.>

*< %
3S

8/i vase/
S/t&ttttM W1V#&<1 rj!j>'ti/^{o

g 8 f-

*< >

. ' i' r

Aft*

^^^^^^^^^^^^m ^^^^^^^^^^m * ^^^^^^^^^^m

j^^^^^^^^^^^^m ^^^^^^^^^B ^^^^^^^^HK

i^^^^^^^^^Bj

i^^^^^^^^^Bt

****

*****

*$&*

'

I!

Cmjtim

F/gwre 9-8a. Condition Analysis- Frequency Diagram.

i5SST^iSw'','(S^'''''1

<**ox< <f^:<x$fexc i*3(f?

Figure 9-8b. Condition Analysis- GIS Map Display.

9 Network-Level Pavement ManagementInventory and Condition Reporting /193

References
American Public Works Association (APWA), 2004. e-mail: paver@apwa.net web: www.apwa.net/about/SIG/MicroPAVER University of Illinois at Urbana-Champaign (UIUC) Technical Assistance Center (TAC), 2004. e-mail: techctr@uiuc.edu web: www.tac.uiuc.edu U.S. Army Engineering Research and Development Center-Construction Engineering Research Laboratory (ERDC-CERL). Micro PAVER Pavement Management System, 2004. e-mail: paver@cecer.army.mil web: www.cecr.army.mil/paver