State of Wisconsin/Department of Transportation RESEARCH PROGRESS REPORT FOR THE QUARTER ENDING: March 31, 2007

Transcription

1 tate of Wisconsin/Department of Transportation REEARCH PROGRE REPORT FOR THE QUARTER ENDING: March 31, 2007 Program: PR-0010(36) FFY99 Part: II Research and Development Project Title: Database Development for a Hot-Mix Asphalt Pavement Performance Analysis ystem Project ID: Administrative Contact: Jason Bittner ponsor: MRUTC WisDOT Technical Contact: James McDonnell Approved tarting Date: November 16, 2006 Approved by COR/teering Committee: FY07, $50,000, 12 months Approved Ending Date: November 15, 2007 Project Investigator (agency & contact): Robert chmitt, UW-Platteville Description: Total study budget Current FFY budget Expenditures for current Total Expenditures to Percent Complete quarter date $50,000 $50,000 $6,500 $13, 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. urvey and Review of Pavement Management ystems 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 ynthesis 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, oil upport 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 () or non-spatial (). patial 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 File, AC Project IRI, AC Office File, AC Office Nochange,, 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 1

2 and 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 patial () or Name Non-patial () District/County Project # Hwy General Location Contractor Length Weighted IRI Pavement Thickness Hv,Mv,Lv Mill Depth New Base Paved Over * Exact Width is unknown at this time Table 2. New Construction Report AC File Query Name patial () or Non-patial () ite q no RP Contract Hwy urlen Lane Dir A or P et Iri Rut * Exact Width is unknown at this time 2

3 Table 3. New Construction Report AC Project IRI Query patial () Name or Non- patial () Contract 2 Wtd Len Len 3 Wt diri Deviation * Exact Width is unknown at this time Table 4. New Construction Report AC Office File Query patial () or Name Non-patial () Pvmnt Location tyle Distri County Contract1 Contract2 Hwy Gen loc Contractor Length mi Pv Thick HvMvLv Mill Depth 22 Base Pvdovr Pvmntyr Pvtno pcicase EAL * Exact Width is unknown at this time 3

4 Table 5. New Construction Report AC Office Nochange Query patial () or Name Non-patial () Pvmnt Location tyle Distri County Contract1 Contract 2 Hwy Gen loc Contractor Length mi Pv Thick HvMvLv Mill Depth 22 Base Pvdovr Pvmntyr Pvtno pcicase EAL * Exact Width is unknown at this time Table 6. New Construction Report Query patial () or Name Non-patial () ite eq no RP Contract Hwy urlen Lane Dir A or P et Iri Rut * Exact Width is unknown at this time 4

5 Table 7. New Construction Report General Query patial () or Non- Name patial () Contractor Location Type Thickness HvMvLv pecial District County Base Pvdovr Jt angle lab Center Dowel Pave yr EAL * Exact Width is unknown at this time Table 8. New Construction Report Asphalt Project Query patial () or Name Non-patial () urvey Yr From Feature To Feature Test egment Dist to eg ection length From RP Plus Dist To RP Plus Dist Alligcr Block CR Edge Rav Flush LongCr Rut urfrav Transcr TransDis Patch Pothole * Exact Width is unknown at this time 5

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 ystem (MT). The first two databases use Microsoft Excel, while the MT is accessed in PDF format. The HMA Mix Design Log is maintained by the Bureau of Technical ervices (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) Name patial () or Nonpatial () Pre Test Number Year Type EALs Contractor Project Number District Number Agg. ourse 1 Agg. ourse 2 Hwy Number County * Exact Width is unknown at this time Both the HMA Mix Properties files and MT 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 MT 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 () or non-spatial () data. The shown fields were extracted from the file name Data xls. 6

7 Table 10. Contents of the HMA Mix Properties file (Data xls) Name Width patial () or Nonpatial () Pre Test Number Year Type Contractor % AC % VMA 3/4" 1/2" 3/8" #4 #8 #16 #30 #50 #100 #200 Number Aggs. % RAP Gse Gsb Gmm Gmb Dryback Correction MA Flow TAB TR Blows Anti-TR AC-Type AC ource AC pgr * Exact Width is unknown at this time 7

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 () or non-spatial () data in Metamanager. 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 s Name Width patial () or Nonpatial () IEQNO 6 PDP_ID 6 TRAF_EG_ID 4 PDP_MILE 4.2 HWY_NUM 3 DIRECTION $CHAR1. TPTNDIT 1 NUMLANE 1 FCLA 2 AADTYR_1 6 TRKYR_1 2 IPDI_BY 3 IRUTAV_BY 5.3 IIRIAV_BY 5.3 IPIE_BY 3.1 URFAGE_BY 3 IPVMTT_BY 1 WI_CNTY_NM $CHAR11. TERMINI $CHAR40. 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 A 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. 8

9 Table 12. PIF Description Database Title Width patial () or Nonpatial () EQUENCE NUMBER 6 COUNTY NUMBER 2 HIGHWAY TYPE 1 HIGHWAY NUMBER 3 HIGHWAY DIRECTION CHAR1 FROM RP CHAR4 FROM RP PLU DITANCE 5.3 TO RP CHAR4. TO RP PLU DITANCE 5.3 DITRICT NUMBER 1 COUNTY NAME CHAR11 ECTION LENGTH 5.3 DATE OF DECRIPTION YYMMDD6 URFACE YEAR 4 PAVEMENT TYPE ALPHA CHAR6 URFACE TYPE 1 OIL NAME CHAR20 FROM FEATURE CHAR20 DIVIDED Y OR N CHAR1 CUMMALATIVE MILEAGE 6 JOINT PACING 2 TETED FOR PI CHAR1 PDI REPOIBILITY CHAR1 FUNCTIONAL CLA 2 NH VALUE CHAR03 ORIGINAL COTRUCTION YEAR 4 HPM AMPLE KEY CHAR13 9

10 Table 13. PIF PDI Database patial () or Name Width Nonpatial () MERGE BY/EQUENCE # 6 INVERE YEAR MONTH 4 URVEY TET YEAR 4 URVEY TET MONTH 2 URVEY TET DAY 2 URF YEAR AT URVEY DATE 2 TENTH OF MILE FROM FROM RP 1 URF AT URVEY DATE 1 BLOCK OR ALLIGATOR TYPE 1 BLOCK 0 % OF AREA 1 BLOCK 1-24 OF AREA 1 BLOCK OF AREA 1 BLOCK 50-74LAB MVMT 1 BLOCK 75 + % OF AREA 1 TRA. CRK. 0 TATION 1 TRA. CRK. 1-5 TA 1 TRA. CRK TA 1 TRA. CRK TA 1 LONGI. CRK. 0 LF TA 1 LONGI. CRK TA 1 LONGI. CRK TA 1 LONGI. CRK TA 1 LONGI. CRK TA 1 PATCHING NONE % OF LENGTH 1 PATCHING OCCAIONAL 1 PATCHING LT 10 % OF LENGTH 1 PATCHING % OF LENGTH 1 PATCHING GT 25 % OF LENGTH 1 FLUHING 1 EDGE RAVELING 1 URFACE RAVELING 1 RUTTING 1 LONGI. DITORTION NONE % LEN 1 LONGI. DITORTION 1-24 % LEN 1 LONGI. DITORTION % LEN 1 LONGI. DITORTION 50 + % LEN 1 TRA. DITORTION NONE % LEN. 1 TRA. DITORTION 1-24 % LEN. 1 TRA. DITORTION % LEN. 1 TRA. DITORTION 50 + % LEN. 1 EAL COATED 1 CRACK FILLING 1 OVERALL PDI VALUE 3 PDI REMARK $CHAR40 10

11 Table 14. PIF IRI Data patial () or Name Width Nonpatial () EQUENCE NUMBER 6 INVERE YEAR MONTH 4 TET YEAR 4 TET MONTH 2 TET DAY 2 PI URFACE YEAR 2 PI URFACE TYPE 1 TET VEHICLE NUMBER 4 TET PEED UED 2 FLEX OR RIGID PVMNT CHAR1 AIR TEMP CHAR3 INCHE PER MILE N OR E 3 INCHE PER MILE OR W 3 PI N OR E 3 PI OR W 3 ECTION PI AVG 3 INITIAL PI CHAR1 RUT ENGLIH N OR E 3 RUT ENGLIH OR W 3 ECTION RUT ENGLIH AVG 3 IRI METRIC N OR E 3 IRI METRIC OR W 3 IRI IN IPM N OR E 3 IRI IN IPM OR W 3 IRI IPM ECTION AVG 3 Task 2 ummary 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., equence 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 ystem 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 GI 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 GI software, such as ArcGI, is currently being 11

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 GI 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 GI, 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 tatistical 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. urvey and Review of Pavement Management ystems Work will continue on investigating the data fields of each database, and the ability to merge in Task 3. Task 3. Database ystem 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 tatistical Analysis No work is planned on Task 4 during the next quarter. However, developments with NCHRP 9-22, Development of Performance-Related pecifications 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. 12

13 Gantt Chart: Project Progress Chart Updated: April 2, 2007 MRUTC Project Database Development of an HMA Pavement Performance Analysis ystem Qtr 1 Qtr 2 Qtr 3 Qtr 4 Qtr 5 Percent Task Description Nov Dec Jan Feb Mar Apr May Jun Jul Aug ep Oct Nov Complete 1 Literature Review 60 2 PM Review 25 3 ystem Development 5 4 tatistical Modeling 0 5 Final Report 0 Proposed Actual 20 13