STATE OF OHIO[rj1]

DEPARTMENT OF TRANSPORTATION

SUPPLEMENT 11110033

SUBMITTAL AND APPLICATION REQUIREMENTS FOR ProVAL PAVEMENT SMOOTHNESS SOFTWAREHIPERPAV REQUIREMENTS FOR CONCRETE PAVEMENT

September July 15714, 20057April 18, 2008

1110.01Scope

1110.02Acquiring Software

1110.03Contractor submittal Requirements for identifying localized roughness with ProVAL

1110.04Contractor Requirements for IRI 0.1 mile interval HIPERPAV II 3.0calculation with ProVAL

1110.05Contractor Submittal To ODOT from ProVAL

1110.031110.06Engineer verification of the smoothness data.standard input requirements for HIPERPAV II 3.0

1110.04Input example for HIPERPAV II 3.0 including standard inputs

1110.05Analysis of Additional Strategies

1110.06Required Submittal of Outputs

10XX1110.01 Scope. This supplement provides guidelines tofor use of ProVAL software for measuring and evaluating pavement smoothness.

1110.02Acquiring Software.

A.ProVAL HIPERPAV II 3.0 software is a computer program initially developed by FHWA researchthe Long Term Pavement Performance Program. The software provides users the ability to view and analyze roadway pavement profiles.

Acquire a copy of the software from

The Transtec Group, Inc.

1012 East 38 ½ Street

Austin, Texas78751

Web Page:

There is no Ccost for the softwareof the software is incidental to 451.

B.Microsoft Office software with Excel to be able to download data from ProVAL software in the form the Department wants the information submitted.

11001110.03 Contractor Requirements for identifying localized roughness with ProVAL

  1. Install ProVAL version 2.72 or later and open.

2B. Open ProVAL compatible profile and load

3C.

Go to the Analysis drop down box and select Rolling Straightedge

  1. To find 0.3 inch deviations in 25 feet or less [bumps and dips in the pavement]

Select both left and right wheel path profiles

Make sure the Straightedge Length is set to 25 feet

  1. Then hit the Analyze button.

User information. Why do we use a +/- inch deviation band in ProVAL? The Department specifications require repair of any bumps/dips over 0.3 inches in 25 feet (7.6 mm in 7.6 m). This control was beyond the old .20 inch blanking band. ProVAL uses the two numbers together to create a +/- 0.25 inch in 25 feet (6.3 mm in 7.6 m) deviation band that is run against the measured profile to determine where bumps/dips required for repair are.

  1. The ProVAL screen will show the completed analysis

  1. Zoom in on the plot from +-0.25 inch deviation on the vertical scale across the entire length of the ProVAL.

  1. After zooming in you will see a graph like below. Now look for anyplace in the graph where the red (right wheel path) or blue (left wheel path) line exceeds + or – 0.25. These are deviations that must be corrected.

8H. You can place your cursor on any location to see if it exceeds the limit or not.

  1. After corrections are made, you collect new profiles over the section and repeat the steps above. If all deviations are successfully corrected, you will see a results screen that looks similar to the following.

1110.04Contractor Requirements for IRI 0.1 mile interval calculation with ProVAL

  1. Open collected profile(s) in ProVAL.

If there were bump corrections under 11001110.03 you will want to make sure you are running the collected profile that was taken after the bumps/dips were corrected.

EXERCISE 2: SMOOTHNESS REPORTING REQUIREMENTS

Open AC overlay Intestate Examp-C.pv2 from the “More Examples” file folder.

  1. Select the Analysis tab and then select Ride Statistics at Intervals.

Figure 1: Ride Statistics at Intervals Analysis

  1. Click on both left and right elevation boxes

a. .and

Mamake sure the Segment Length is set at 528 feet or 0.1 mile. (Under Viewer you can choose feet or miles. Use the same units you put in the viewer screen)

b.Check “apply 250 mm filter”

c.Click on the Analyze button

Click on the Analyze button.

D.

Figure 2: Ride Statistics at Intervals Analysis

  1. Your ProVAL results would look like this

NOTE: Review the results of the MRI values and if any 0.1 mile sections have a value above 95 inches per mile those tenth mile lots require correction. Make the field repairs and/or modifications, re-profile and re-run the information for bump/dip 11001110.03 and for analysis 11001110.04. If no MRI values are greater than 95 inches per mile, you are ready to move on to 11001110.04.5

5E.When the results don’t require field correction and repairs, export the ride statistics at intervals (11001110.04.4D) Select the Edit drop down menuto Excel for calculating pay levels..

  1. Select the Edit drop down menu Then
  2. select the Export option and
  3. export grid to Excel.

Figure 3: Exporting Grid to Excel

76F.Data is displayed in Excel as shown below.

11001110.05Contractor Submittal To ODOT from ProVAL

Provide a complete submittal to the Engineer. The submittal will include:

  1. a completed log sheet(s) (see appendix A for standard form in legal size sheet format) following the requirements listed in appendix B for completing the log sheet(s). A separate log sheet will be completed for each different day profiles are collected on any given project.
  1. an electronic storage media (i.e. CD, thumb drive) that includes:
  1. An electronic folder named with the project number
  2. Sub folder(s) under the project number folder named with the date the road profile was collected.
  3. In each subfolder the road profiles taken on that subfolder’s date and listed on the completed log sheet(s):
  1. Each road profile file will have a naming convention chosen by the contractor and the naming convention will
  2. provide enough information to tie the road profile file to the project, route, lane, and location.
  3. Whatever the naming convention used, the file name will exactly match the name on the completed log sheet.
  1. All the pay adjustment excel file summary sheets created according to 11001110.04.6 and adjusted with the specification’s pay adjustment table for each 0.1 mile lots

The Excel Pay Adjustment file(s) should look similar to the below example.

A.Using the applicable specification Pay Adjustment Table, modify the Excel file created and saved in 11001110.04 to include:

a.The pay adjustment for each .1 mile lot

b.The total pay adjustment for the lane

You will need to do this for each lane.

Figure 13: Microsoft Excel Printout

Name the Excel Pay Adjustment files to match the profile they were created from and stored in a separate sub folder called “project pay adjustments”.

Either provide hard copies of Project Road Profile Log Sheet(s) [Appendix A] with the road profile files and the pay adjustment excel files or provide electronic copies of the log sheets stored in the same subfolders as their road profile files listed on the log sheet. Name any electronic log sheets with both project number and date to match the subfolder it is stored in.

Project engineers may require hard copies of the Excel Pay Adjustment files for 0.1 mile lots, complete with incentive/disincentive calculations, along with the electronic copies stored on the electronic storage media.

Provide the Office of Pavement Engineering with a dublicateduplicate copy of any submitted electronic storage media with the road profile file(s), the Project Road Profile Log Sheets, and the 0.1 mile lot excel file pay adjustment file(s).

11001110.06 Engineer verification of the smoothness data

The Engineer will randomly select one of the road profile files as follows:

1A. Open ProVAL and load the selected road profile file

  1. Select the Report button
  2. select “files to Print”
  3. select the create button
  4. and a Report will be shown on the screen similar to the report on the next page

8. Click on the Report tab at the top.

Figure 14: Report Screen

9.Make certain that the Profilograph Simulation and Ride Statistics at Intervals boxes are checked.

10.Select the Files to Print box. If you do not select this box, ODOT will not accept your results.

11. Click the Create button.

Figure 15: ProVAL Report

The Engineer should check that the History of the report shows no use of filters. If it does reject all data and require the contractor to rerun all profiles.

If no filters are shown, the Engineer should verify the MRI + IRI table created through ProVAL for the profile file loaded match the MRI-IRI table in the “Pay Adjustment file”.

Follow the procedures listed under 11001110.04 and recreate the MRI + IRI table in ProVAL. Check the table against the Excel pay adjustment file information submitted to see if the IRI for the 0.1 mile Lots are the same. If they are accept the data submitted in the electronic media. If not reject all the submitted data and require the contractor to rerun all profiles.

Appendix A

Ohio Department of Transportation
Project Road Profile Log Sheet
Contractor / Company Name / Profile Operator Name
Profile Make / ODOT Cert. Device # / Date
Project Number / County / Route Number
Bounce Test Performed (Y/N) / Block Check Performed (Y/N) / Check Long. Distance (Y/N)
File Name / Dir / Lane / Beginning Mile Point / Ending Mile Point / Beginning GPS Coordinate / Ending GPS Coordinate / Beginning Station / Ending Station / Beginning Physical Feature / Ending Physical Feature
Notes:

Appendix B

Instructions for Completing ODOT’s, “Project Road Profile Log Sheet”

This log sheet may be printed and completed by hand so long as it is legible or it may be completed electronically. This form is available on the ODOT Pavement Engineering website. A separate log sheet will be completed for each different day profiles are collected on any given project.

Contractor/Company Name – self explanatory

Profiler Operator Name – First and Last

Profiler Make – Ex Ames, Dynatest, KJLaw, SSI

ODOT Certification Device Number – number assigned by ODOT during certification

Date – Date you collected the profiles PROVIDE A PROJECT ROAD PROFILE LOG SHEET FOR EACH DATE PROFILES ARE COLLECTED.

Project Number – self explanatory

County – County or Counties where the project is located

Route Number – Route Number(s) of completed work, Ex. US 33, SR 128, I 271

Bounce Test Performed – Required at the beginning of the project and also recommend performing daily. If equipment fails a bounce test you should not collect profiles until remedied.

Block Check Performed – Required at the beginning of the project and also recommend performing daily. If equipment fails a block test you should not collect profiles until remedied

Check Longitudinal Distance – Required at the beginning of the project. If equipment fails the longitudinal distance test you should not collect profiles until remedied

File Name – This is at the contractor’s discretion. It must exactly match the name of the electronic profiles given to ODOT including extensions.

Direction – This will be either U for Up or D for Down according to ascending or descending direction of mile markers. Routes are either signed Up for predominately Northbound or Eastbound and Down for predominately Southbound and Westbound travel directions.

Lane – Lane Number, Lanes will be numbered from the outside to the inside by direction. [Example: A 6 lane divided section of I-71 will have the outside driving lane in each direction labeled lane number 1, the center lane in each direction will be labeled lane number 2, and the inside lanes in each direction will be labeled lane number 3.

For beginning and ending descriptions, at a minimum one pair of the following four sets must be completed. Please complete all that you are able.

Beginning Milepoint – The beginning of data collection to the nearest 0.01 mile if known.

Ending Milepoint – The ending of data collection to the nearest 0.01 mile if known.

Beginning GPS – The GPS coordinates at the beginning of a data collection run if known.

Ending GPS – The GPS coordinates at the end of a data collection run if known.

Beginning Station – Station location at the beginning of a data collection run if known.

Ending Station – Station location at the end of a data collection run if known.

Beginning Feature – Description of the point where the data collection run began. Examples may include: Began at structure over County Road 110; Began at bridge over Wolfe Creek, Began 250 feet west of Junction SR 607, etc. Do your best to describe where you began.

Ending Feature – Similar to beginning features.

Notes – Any additional notes to help describe profile file names with location information will be appreciated. Feel free to turn the paper over and draw maps if that helps describe the data that you collect.

[rj1]ODOTQC check completed 6/22/2005