Upload
trannguyet
View
212
Download
0
Embed Size (px)
Citation preview
1
State of Wisconsin/Department of Transportation RESEARCH PROGRESS REPORT FOR THE QUARTER ENDING: March 31, 2007
Program: SPR-0010(36) FFY99 Part: II Research and Development
Project Title: Database Development for a Hot-Mix Asphalt Pavement
Performance Analysis System Project ID: 0092-06-13
Administrative Contact: Jason Bittner Sponsor: MRUTC
WisDOT Technical Contact: James McDonnell Approved Starting Date: November 16, 2006
Approved by COR/Steering Committee: FY07, $50,000, 12 months Approved Ending Date: November 15, 2007
Project Investigator (agency & contact): Robert Schmitt, UW-Platteville
Description:
Total study budget Current FFY budget Expenditures for current
quarter
Total Expenditures to
date
Percent Complete
$50,000 $50,000 $6,500
$13,000
20
Progress This Quarter:
(Includes project committee mtgs, work plan status, contract status, significant progress, etc.)
Task 1. Literature review
The objective of Task 1 is to identify, collect, review, and synthesize literature and research to understand all relevant literature on the
relationship of pavement performance to design, construction, maintenance, and environmental variables. Task 1 is 50% complete, and a
full literature review will be presented in the next quarterly report.
Task 2. Survey and Review of Pavement Management Systems
The objective of Task 2 is to survey state highway agencies to acquire information on their pavement management systems. From the
literature review in Task 1 it was learned that a synthesis of current practices from all states was published in 2004, as NCHRP Synthesis
Report #335. Thus, the survey was suspended.
During this quarter, the latest available WisDOT HMA databases were collected for performance, design, traffic, and construction data.
Then, each database was broken down by field name, field length, and whether the field was spatial or not. The following sections describe
the contents of each database, and the potential to merge them in Task 3.
A. Design Data
Currently, there does not exist a single database containing a range of traditional design parameters and measures, such as base strength
(e.g., Modulus, Soil Support Value) of pavement structural numbers (e.g., layer coefficients). Rather, several design-related measures can
be found in the New Construction Report; a report that is prepared annually to describe all new and rehabilitated pavements that were
constructed in a given year.
The software platform for New Construction Report is Microsoft Access, and allows user-defined queries to acquire and assemble
meaningful groups of data. To develop a detailed understanding of this database, several queries were made, then the queried data were
broken down by field name, field width, and whether the field was considered spatial (S) or non-spatial (NS). Spatial data possess the
capability to identify the location of the collected data, with the potential for merging with other databases. Tables 1 through 7 provide a
break down of the respective queries for From Program, AC Field File, AC Project IRI, AC Office File, AC Office Nochange, Field,
and General. Table 8 provides a Microsoft Excel database in the New Construction Report, called Asphalt Project. The specific
character width of each field is unknown at this time, and will be further researched. Also, as the research progresses, the designation of S
2
and NS may change. The purpose of presenting the database in these tables is to understand their basic contents and the potential to
develop a merge function for performance modeling in Tasks 3 and 4.
Table 1. New Construction Report – From Program Query
Field Name
Field
Width*
Spatial (S) or
Non-Spatial
(NS)
District/County S
Project # S
Hwy NS
General Location NS
Contractor NS
Length NS
Weighted IRI NS
Pavement Thickness NS
Hv,Mv,Lv NS
Mill Depth NS
New Base NS
Paved Over NS
* Exact Field Width is unknown at this time
Table 2. New Construction Report –AC Field File Query
Field
Name
Field
Width*
Spatial (S) or
Non-Spatial (NS)
Site NS
Sq no S
RP S
Contract NS
Hwy NS
Surlen NS
Lane NS
Dir NS
A or P NS
Set NS
Iri NS
Rut NS
* Exact Field Width is unknown at this time
3
Table 3. New Construction Report – AC Project IRI Query
Field Name
Field
Width*
Spatial (S)
or Non-
Spatial (NS)
Contract 2 NS
Wtd NS
Len NS
Len 3 NS
Wt diri NS
Deviation NS
* Exact Field Width is unknown at this time
Table 4. New Construction Report – AC Office File Query
Field Name
Field
Width*
Spatial (S) or
Non-Spatial
(NS)
Pvmnt NS
Location S
Style NS
Distri S
County S
Contract1 NS
Contract2 NS
Hwy NS
Gen loc NS
Contractor NS
Length mi NS
Pv Thick NS
HvMvLv NS
Mill Depth NS
Field 22 NS
Base NS
Pvdovr NS
Pvmntyr NS
Pvtno NS
Spcicase NS
ESALS NS
* Exact Field Width is unknown at this time
4
Table 5. New Construction Report – AC Office Nochange Query
Field Name
Field
Width*
Spatial (S) or
Non-Spatial
(NS)
Pvmnt NS
Location S
Style NS
Distri S
County S
Contract1 NS
Contract 2 NS
Hwy NS
Gen loc NS
Contractor NS
Length mi NS
Pv Thick NS
HvMvLv NS
Mill Depth NS
Field 22 NS
Base NS
Pvdovr NS
Pvmntyr NS
Pvtno NS
Spcicase NS
ESALS NS
* Exact Field Width is unknown at this time
Table 6. New Construction Report – Field Query
Field Name
Field
Width*
Spatial (S) or
Non-Spatial
(NS)
Site S
Seq no S
RP S
Contract NS
Hwy NS
Surlen NS
Lane NS
Dir NS
A or P NS
Set NS
Iri NS
Rut NS
* Exact Field Width is unknown at this time
5
Table 7. New Construction Report – General Query
Field Name
Field
Width*
Spatial (S)
or Non-
Spatial
(NS)
Contractor NS
Location S
Type NS
Thickness NS
HvMvLv NS
Special NS
District S
County S
Base NS
Pvdovr NS
Jt angle NS
Slab NS
Center NS
Dowel NS
Pave yr NS
ESALS NS
* Exact Field Width is unknown at this time
Table 8. New Construction Report – Asphalt Project Query
Field Name
Field
Width*
Spatial (S) or
Non-Spatial
(NS)
Survey Yr NS
From Feature S
To Feature S
Test Segment NS
Dist to Seg NS
Section length NS
From RP S
Plus Dist NS
To RP S
Plus Dist NS
Alligcr NS
Block CR NS
Edge Rav NS
Flush NS
LongCr NS
Rut NS
Surfrav NS
Transcr NS
TransDis NS
Patch NS
Pothole NS
* Exact Field Width is unknown at this time
6
B. Construction Data
HMA construction data is collected and stored in three separate databases: (1) HMA Mix Design Log files, (2) HMA Mix Properties files,
and (3) Materials Tracking System (MTS). The first two databases use Microsoft Excel, while the MTS is accessed in PDF format.
The HMA Mix Design Log is maintained by the Bureau of Technical Services (Truax Materials Lab) and contains Job Mix Formula (JMF)
entries submitted by the contractor. A presentation of the field names, field width, and spatial or non-spatial designation is shown in Table
9. The shown fields were extracted from the file name ‘GeneralLogs 2005.xls’.
Table 9. Contents of the HMA Mix Design Log file (GeneralLogs 2005.xls)
Field Name
Field
Width*
Spatial (S) or
NonSpatial (NS)
Pre NS
Test Number NS
Year NS
Type NS
ESALs NS
Contractor NS
Project Number S
District Number S
Agg. Sourse 1 S
Agg. Sourse 2 S
Hwy Number S
County S
* Exact Field Width is unknown at this time
Both the HMA Mix Properties files and MTS files contain as-built construction data, including both mix properties and field density test
results. Most HMA contractors maintain spreadsheets of as-built plant-produced mix properties to control material quality and maintain
construction records. The MTS files primarily include Quality Assurance (QA) test results performed by Wisconsin DOT or consultant
technicians. Table 10 presents the data from HMA Mix Properties file, consisting of columns for the field name, field width, and spatial (S)
or non-spatial (NS) data. The shown fields were extracted from the file name ‘Data 1997-2004.xls’.
7
Table 10. Contents of the HMA Mix Properties file (Data 1997-2004.xls)
Field Name Field Width
Spatial (S) or
NonSpatial (NS)
Pre NS
Test Number NS
Year NS
Type NS
Contractor NS
% AC NS
% VMA NS
3/4" NS
1/2" NS
3/8" NS
#4 NS
#8 NS
#16 NS
#30 NS
#50 NS
#100 NS
#200 NS
Number Aggs. NS
% RAP NS
Gse NS
Gsb NS
Gmm NS
Gmb NS
Dryback Correction NS
MA NS
Flow NS
STAB NS
TSR NS
Blows NS
Anti-STR NS
AC-Type NS
AC Source NS
AC SpGr NS
* Exact Field Width is unknown at this time
8
C. Traffic Data
The primary source for traffic data is the MetaManager database. MetaManager includes records describing highway section geometric
features and traffic counts, and is formatted for the 5 WisDOT Regions in Microsoft Excel. Table 11 provides three columns that consist of
field name, field width, and spatial (S) or non-spatial (NS) data in Metamanager. Field width for both numeric and character variables is
expressed as the numeric value preceding the decimal point. The value following the decimal point is number of digits after the decimal.
Table 11. MetaManager Data Fields
Field Name Field Width
Spatial (S)
or
NonSpatial
(NS)
ISEQNO 6 S
PDP_ID 6 S
TRAF_SEG_ID 4 S
PDP_MILE 4.2 S
HWY_NUM 3 S
DIRECTION $CHAR1. NS
TPTNDIST 1 S
NUMLANES 1 NS
FCLASS 2 NS
AADTYR_1 6 NS
TRKYR_1 2 NS
IPDI_BY 3 NS
IRUTAV_BY 5.3 NS
IIRIAV_BY 5.3 NS
IPSISE_BY 3.1 NS
SURFAGE_BY 3 NS
IPVMTT_BY 1 NS
WI_CNTY_NM $CHAR11. S
TERMINI $CHAR40. S
Field Width X.Y, where X = total width and
Y = spaces behind decimal point.
D. Performance Data
The Pavement Inventory File (PIF) database is a comprehensive and detailed pavement performance inventory of all roadway segments in
the state, excluding roadways under local jurisdiction. Generally, each pavement segment is measured on a biennial basis for Pavement
Distress Index (PDI) distresses and International Roughness Index (IRI). PIF data is formatted in Microsoft Excel, however, ‘Readme.txt’
files provide partial data entry code for reading the data into SAS statistical software.
There are 3 primary files within the PIF database as shown in Tables 12 through 14. A description of the roadway segment is shown in
Table 12, with primary fields including the pavement sequence number, highway number, direction, and beginning and ending physical
features. In Tables 13 and 14 are the PDI and IRI data, respectively, for each segment, as designated by the pavement sequence number.
9
Table 12. PIF Description Database
Field Title Field Width
Spatial (S)
or
NonSpatial
(NS)
SEQUENCE NUMBER 6 S
COUNTY NUMBER 2 S
HIGHWAY TYPE 1 NS
HIGHWAY NUMBER 3 NS
HIGHWAY DIRECTION CHAR1 NS
FROM RP CHAR4 NS
FROM RP PLUS DISTANCE 5.3 S
TO RP CHAR4. NS
TO RP PLUS DISTANCE 5.3 S
DISTRICT NUMBER 1 S
COUNTY NAME CHAR11 S
SECTION LENGTH 5.3 NS
DATE OF DESCRIPTION YYMMDD6 NS
SURFACE YEAR 4 NS
PAVEMENT TYPE ALPHA CHAR6 NS
SURFACE TYPE 1 NS
SOIL NAME CHAR20 NS
FROM FEATURE CHAR20 NS
DIVIDED Y OR N CHAR1 NS
CUMMALATIVE MILEAGE 6 NS
JOINT SPACING 2 NS
TESTED FOR PSI CHAR1 NS
PDI RESPONSIBILITY CHAR1 NS
FUNCTIONAL CLASS 2 NS
NHS VALUES CHAR03 NS
ORIGINAL CONSTRUCTION YEAR 4 NS
HPMS SAMPLE KEY CHAR13 NS
10
Table 13. PIF PDI Database
Field Name
Field
Width
Spatial (S)
or
NonSpatial
(NS)
MERGE BY/SEQUENCE # 6 S
INVERSE YEAR MONTH 4 NS
SURVEY TEST YEAR 4 NS
SURVEY TEST MONTH 2 NS
SURVEY TEST DAY 2 NS
SURF YEAR AT SURVEY DATE 2 NS
TENTHS OF MILE FROM FROM RP 1
SURF AT SURVEY DATE 1
BLOCK OR ALLIGATOR TYPE 1 NS
BLOCK 0 % OF AREA 1
BLOCK 1-24 OF AREA 1
BLOCK 25 - 49 OF AREA 1
BLOCK 50 - 74SLAB MVMT 1
BLOCK 75 + % OF AREA 1
TRANS. CRK. 0 STATION 1
TRANS. CRK. 1 - 5 STA 1
TRANS. CRK. 6 - 10 STA 1
TRANS. CRK. 11 + STA 1
LONGI. CRK. 0 LF STA 1
LONGI. CRK. 1-100 STA 1
LONGI. CRK. 101-200 STA 1
LONGI. CRK. 201-300 STA 1
LONGI. CRK. 301 + STA 1
PATCHING NONE % OF LENGTH 1
PATCHING OCCASIONAL 1
PATCHING LT 10 % OF LENGTH 1
PATCHING 10 25 % OF LENGTH 1
PATCHING GT 25 % OF LENGTH 1
FLUSHING 1 NS
EDGE RAVELING 1 NS
SURFACE RAVELING 1 NS
RUTTING 1 NS
LONGI. DISTORTION NONE % LEN 1
LONGI. DISTORTION 1-24 % LEN 1
LONGI. DISTORTION 25-49 % LEN 1
LONGI. DISTORTION 50 + % LEN 1
TRANS. DISTORTION NONE % LEN. 1
TRANS. DISTORTION 1-24 % LEN. 1
TRANS. DISTORTION 25-49 % LEN. 1
TRANS. DISTORTION 50 + % LEN. 1
SEAL COATED 1 NS
CRACK FILLING 1 NS
OVERALL PDI VALUE 3 NS
PDI REMARKS $CHAR40 NS
11
Table 14. PIF IRI Data
Task 2 Summary
As illustrated in the previous sections, the primary HMA databases have several data fields, some that are unique and some that are mutual
to the other databases. In Task 3, the ability to merge the databases is being investigated.
One issue that has surfaced is the ability to merge the design and construction databases with the traffic and performance databases. Both
the MetaManager and PIF databases contain sequence numbers to identify a unique segment of roadway, typically between two reference
points. The design and construction databases contain a field for project I.D., but cannot translate the I.D. to a specific roadway segment
(i.e., Sequence Number). To create a holistic performance database, data from one table must be matched to data in another table using a
linking mechanism called a relational join. The joined data or combined data can then be exported in a spreadsheet or space delimited
format to a statistical software for detail performance modeling. This work is beginning in Task 3.
Task 3. Database System Development.
The objective of Task 3 is the development of a database system including several elements, such as the overall purpose of the system, data
types and formats to be collected and managed, software and hardware requirements, as well as institutional issues involved in the
implementation and use of the system.
During this quarter, the research team obtained GIS Base Maps of four WisDOT Districts. These base maps are capable of illustrating the
Wisconsin highway network by user-defined fields, such as HMA or PCC pavement, or by type of pavement (i.e., HMA Type 1 over PCC,
Type 3 over HMA/CABC, etc.). The ability of opening these maps using a variety of GIS software, such as ArcGIS, is currently being
Field Name
Field
Width
Spatial (S)
or
NonSpatial
(NS)
SEQUENCE NUMBER 6 S
INVERSE YEAR MONTH 4 NS
TEST YEAR 4 NS
TEST MONTH 2 NS
TEST DAY 2 NS
PSI SURFACE YEAR 2 NS
PSI SURFACE TYPE 1 NS
TEST VEHICLE NUMBER 4 NS
TEST SPEED USED 2 NS
FLEX OR RIGID PVMNT CHAR1 NS
AIR TEMP CHAR3 NS
INCHES PER MILE N OR E 3 NS
INCHES PER MILE S OR W 3 NS
PSI N OR E 3 NS
PSI S OR W 3 NS
SECTION PSI AVG 3 NS
INITIAL PSI CHAR1 NS
RUT ENGLISH N OR E 3 NS
RUT ENGLISH S OR W 3 NS
SECTION RUT ENGLISH AVG 3 NS
IRI METRIC N OR E 3 NS
IRI METRIC S OR W 3 NS
IRI IN IPM N OR E 3 NS
IRI IN IPM S OR W 3 NS
IRI IPM SECTION AVG 3 NS
12
investigated. The goal, based upon discussion during the kickoff meeting, is not to create an entirely new database, but to merge existing
databases.
A GIS ties information to location; it allows specific attributes regarding the location to be retrieved and visualized on a dynamic map. In
addition, it allows basic statistics and charts to be created from specific queries about the data for presentation purposes, and can display
photos of the location of interest. To enable the data categories to operate in a GIS, separate simple tables or flat files for elements or
attributes in each category will be developed and related to a dynamic map that shows the network of pavements in Wisconsin.
An important consideration during Task 3, that will lead to work in Task 4, is assigning a variable or attributes designation to the individual
data fields. This work is beginning and no conclusive findings can be reported.
Task 4. Numerical Modeling and Statistical Analysis
The objective of Task 4 is to develop an analysis template for aligning design and construction datasets with the pavement performance
indicator datasets, and demonstrating methodologies for analyzing the data. No work was performed on Task 4 this quarter.
Task 5. Final Report.
The objective of Task 5 is to submit a final report documenting all findings in the project. No work was performed on Task 5 this quarter.
Work Next Quarter:
Task 1. Literature review
Work will continue with a review of all literature related to this topic. A complete synthesis of literature will be provided in the next
quarterly report.
Task 2. Survey and Review of Pavement Management Systems
Work will continue on investigating the data fields of each database, and the ability to merge in Task 3.
Task 3. Database System Development.
It is planned that work will begin on the development of the database system next quarter, concurrent with work in Task 2.
Task 4. Numerical Modeling and Statistical Analysis
No work is planned on Task 4 during the next quarter. However, developments with NCHRP 9-22, Development of Performance-Related
Specifications for Hot Mix Asphalt, will be monitored for application in this project. A product of NCHRP 9-22 is prototype software to
develop performance models of data. How the software aligns itself with comprehensive HMA database will be researched.
Task 5. Final Report.
No work is planned on Task 5 during the next quarter.
Circumstances affecting progress/budget:
None.
13
Gantt
Chart
:
Project Progress Chart
Updated: April 2, 2007
MRUTC Project 0092-06-13
Database Development of an HMA
Pavement Perform
ance Analysis System
Qtr 4
Qtr 5
Percent
Task
Description
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Complete
1Literature Review
60
2PMS Review
25
3System
Development
5
4Statistical M
odeling
0
5Final Report
0
Proposed
Actual
20
Qtr 1
Qtr 2
Qtr 3