U.S. Department of Transportation
Federal Highway Administration
1200 New Jersey Avenue, SE
Washington, DC 20590
202-366-4000
Federal Highway Administration Research and Technology
Coordinating, Developing, and Delivering Highway Transportation Innovations
 |
| This report is an archived publication and may contain dated technical, contact, and link information |
|
Publication Number: FHWA-HRT-06-068 Date: March 2006 |
This chapter provides data sheets and instructions for their use in collecting information concerning maintenance applications and treatments on LTPP monitored test sections. The maintenance data collection plan addresses two separate time periods referred to as: (1) historical data and (2) LTPP accumulated data. Historical data consists of information collected on or near the monitoring site up to the time that site specific maintenance data collection using LTPP guidelines begins. Maintenance data sheet No. 1 is used for this period. Maintenance data sheets Nos. 2 through 19 are used for the period dating from the time monitoring of the test section begins. In brief, it is the intent that these sheets be used to record those data items during maintenance activities that reasonably identify existing pavement conditions before treatment, properties and quantities of materials used, and construction techniques applied during treatment. The data collection sheets are listed in table 1. Copies appear below.
| Description | Sheet Number |
|---|---|
| Historical Maintenance Information | 1 |
| Maintenance Location Summary | 2 |
| Seal Coat AC Pavement | 3–4 |
| Crack Sealing AC Pavement | 5 |
| Patching AC Pavement | 6 |
| Partial Depth Patching PCC Pavement | 7–9 |
| Joint Resealing PCC Pavement | 10–1 |
| Grinding, Milling, and Grooving | 12 |
| Full Depth Repair of PCC Pavement | 13–6 |
| Cost Data | 17 |
| Crack Sealing PCC Pavement | 18 |
| Improvement Listing | 19 |
AC – Asphalt Concrete
PCC – Portland Cement Concrete
As noted previously, a maintenance control zone has been established around each test section. Any application of treatments within this zone will require certain data to be entered into the database, including IMS form 1 described in chapter 2.
For each specific type of treatment (or work type) the appropriate data sheets should be completed (see table 2). Work type codes presented in appendix A, table A.16 and not listed in table 2 are considered rehabilitation activities and will be covered in chapter 4.
The maintenance data sheets provided do not include descriptions of pavements to be repaired; however, the "State Code" and the "Strategic Highway Research Program (SHRP) ID" connect this information to other descriptive data (e.g., inventory, distress, materials sampling, etc.) for the test section.
| Work Item | Work Type Code* | Maintenance Data Sheets** |
|---|---|---|
| Crack Sealing (linear ft) | 01 | 5 or 18, 19 |
| Transverse Joint Sealing (linear ft) | 02 | 10–1, 19 |
| Lane-Shoulder, Longitudinal Joint Sealing (linear ft) | 03 | 10–1, 19 |
| Full Depth Joint Repair Patching of PCC (sq. yards) | 04 | 13–6, 19 |
| Full Depth Patching of PCC Pavement Other than at Joint (sq. yards) | 05 | 13–6, 19 |
| Partial Depth Patching of PCC Pavement Other than at Joint (sq. yards) | 06 | 7–9, 19 |
| PCC Slab Replacement (sq. yards) | 07 | 13–6, 19 |
| Grinding/Milling Surface (sq. yards) | 12 | 12, 19 |
| Grooving Surface (sq. yards) | 13 | 12, 19 |
| Mechanical Premix Patch (using motor grader and roller) (sq. yards) | 21 | 6, 19 |
| Manual Premix Spot Patch (hand spreading and compacting with roller) (sq. yards) | 22 | 6, 19 |
| Machine Premix Patch (placing premix with paver, compacting with roller) (sq. yards) | 23 | 6, 19 |
| Full Depth Patch of AC Pavement (removing damaged material, repairing supporting material, and repairing) (sq. yards) | 24 | 6, 19 |
| Patch Pot Holes—Hand Spread, Compacted with Truck (no. of holes) | 25 | 6, 19 |
| Skin Patching (using spreader and distributor to apply hot liquid asphalt and aggregate) (sq. yards) | 26 | 6, 19 |
| Strip Patching (using spreader and distributor to apply hot liquid asphalt and aggregate) (sq. yards) | 27 | 6, 19 |
| Surface Treatment, single layer (sq. yards) | 28 | 3–4, 19 |
| Surface Treatment, double layer (sq. yards) | 29 | 3–4, 19 |
| Surface Treatment, three or more layers (sq. yards) | 30 | 3–4, 19 |
| Aggregate Seal Coat (sq. yards) | 31 | 3–4, 19 |
| Sand Seal Coat (sq. yards) | 32 | 3–4, 19 |
| Slurry Seal Coat (sq. yards) | 33 | 3–4, 19 |
| Fog Seal Coat (sq. yards) | 34 | 3–4, 19 |
| Prime Coat (sq. yards) | 35 | 3–4, 19 |
| Tack Coat (sq. yards) | 36 | 3–4, 19 |
| Dust Layering (sq. yards) | 37 | 3–4, 19 |
| Partial Depth Patching of PCC Pavement at Joints (sq. yards) | 54 | 7–9, 19 |
* Work Type Codes are taken from appendix A, table A.16.
** Maintenance data sheets 2 and 17 should be completed for all maintenance activities.
On many of the data sheets, "other" codes are provided for cases where a product or technique that is not identified is used. As maintenance practices change and new materials become available, it will be necessary to record their use and performance. Therefore, where it is necessary to use an "other" code, sufficient information should be provided to identify what material or technique was used. A manufacturer or reference is also highly desirable.
The data sheets provide for a broad array of data elements. It is recognized that much of the data will not be available. However, available data should be entered and every effort should be made to obtain data indicated by an asterisk (*). When the data element is not applicable to the test section or represents something that does not exist on the section, enter an "N." If the data element is applicable, but the value is unknown (e.g., not available in project records), enter a "U" to indicate that the value is unknown. Many data items will require codes to be entered. Unless otherwise noted in the following instructions, the codes are listed or referenced on the data sheets.
Routine or corrective maintenance activities that may be performed on the monitoring sites include crack sealing, joint cleaning/sealing, and isolated spot pavement repairs such as patching. These activities may be performed without previous communication with the LTPP RSC.
There are other maintenance activities that are permitted; however, notification to the RSC before their application is requested. These include seal coats, sand seal, cape seal, aggregate/chip seal, slurry seal, fog seal, and milling or grinding for safety. Since the application of these types of treatments alter the pavement surface of the entire test section, their placement should be coordinated with the RSC before conducting the work.
The purpose of this contact is to coordinate appropriate surveys that are required to adequately measure the pavement condition before and after treatment. Ideally, these before and after measurements will be taken by the RSCs as close to application as possible. The following types of measurements are required: deflection, distress survey, and longitudinal profile. Guidelines on the timing of these monitoring events are contained in a separate operational memorandum.
As noted in section 1.1.1, a maintenance control zone has been established around each test section and treatments within this zone should be limited as much as possible.
It is anticipated that LTPP maintenance data will be collected from several possible sources of information. To ensure a relative level of confidence in the reported maintenance information, the source of this data is considered to be of great importance.
Of all the possible sources of information, the most desirable is data collection sheets filled out in the field by a maintenance engineer or inspector. This activity would be performed at the actual time of treatment application. If this is not possible or practical, then field notes or project diaries from each maintenance project should be used. These sources of data would most accurately reflect the actual materials and treatments placed on each monitoring site. It is strongly recommended that these actual sources be used whenever possible.
If project diaries or field notes are not available, then maintenance construction plans or as-built plans should be used. If these exist, they will give a relative idea of what has been done, but usually show only typical cross sections or plan quantities. Due to potential differences between what is actually in the field and what has been planned, this source is less desirable.
Some of the parameters requested in the maintenance data collection guide may not be available from plans and also may not have been recorded in a project diary. One example is air content. This value is usually specified by a State highway agency (SHA), the American Association of State Highway and Transportation Officials (AASHTO), or by industry standard. If no specific records of this type are available for a project, the most likely source for this data would be an applicable specification. It can be assumed that if the work performed is to specifications, then these values will nominally be representative of that found in the field. Because this information is less specific to the individual monitoring sites, it is also less desirable.
If all other sources of data are exhausted, the only remaining way to obtain this information would be from engineering judgment of usual maintenance practices. This is highly subjective and would depend greatly on the knowledge and experience of each individual maintenance engineer or data collector. The use of the engineering judgment source is strongly discouraged and would be considered the least desirable alternative, as it may not reflect actual treatments or materials applied in the field.
In an attempt to define the overall quality of data collected, identifying these sources is necessary. Space is provided for indicating the source of each applicable item on the data collection sheets. This information will help establish a level of confidence to promote proper use of the data. To facilitate the reporting of the source of information, three categories have been provided. These appear on the data collection sheets as "actual," "plans/specs," and "judgment" and are as described above.
As maintenance data is collected and completed data sheets are sent to the RSC, it will be imperative that the RSC review these initial submissions. If sheets submitted from each SHA appear to be completed as described in this chapter, then only spot checking of additional data by the RSC will be required. If problems are apparent in the data, however, then additional communication and coordination will be required between the SHA and RSC to resolve the questions.
A common set of project identification data appears in the upper right corner of every data sheet. These data items are described below.
State Code: The State code is a number that identifies the State or Canadian Province in which the pavement section is located. Codes are provided in appendix A, table A.1.
SHRP ID: The SHRP ID is a four-digit identification number assigned by LTPP. This number is used to facilitate the computer filing of the projects and will identify the section in the field.
Date Completed: The month, day, and year that the pavement improvements were finished and the project was subsequently opened to traffic (not the date when the project was accepted). The first set of two digits represents the numerical sequence of the month as it occurs during the year; the second set of two digits represents the day within the month; and the last set of four digits represents the year.
Historical maintenance information consists of data collected on or near the monitoring site up to the time that monitoring of the specific site began. These data will frequently be very difficult to obtain from existing records for pre-LTPP monitoring work, but it is extremely important that every effort be made to retrieve them.
Space is provided for identifying a maximum of six maintenance activities by the year in which they were accomplished. If more than six maintenance activities have been performed since pavement construction, this sheet must be repeated.
Individual data elements are:
Year (Item 1): The year in which the maintenance activity occurred.
Maintenance Case Number (Item 2): The SHA-assigned case number for the specific maintenance being reported. If no number has been assigned, leave this space blank.
Work Type Code (Item 3): A code to identify the type of maintenance activity accomplished. The work type codes appear in appendix A, table A.16.
Maintenance Location Code (Item 4): A code entered to identify where on the roadway the maintenance has been conducted. These codes appear in appendix A, table A.17.
Maintenance Material Code (Item 5): A code entered for identifying the maintenance materials used (such as preformed joint fillers, hot liquid asphalt, etc.). These codes appear in appendix A, table A.18.
Work Quantity (Item 6): The quantity of work performed within the test section in the appropriate units as listed in appendix A, table A.16 (See item 3).
Thickness (Item 7): The thickness entered to the nearest tenth of an (0.1 inch) (2.5 mm) for those maintenance activities that increase the thickness of the pavement structure (such as "surface treatment, single layer," or "surface treatment, double layer," etc.). Localized treatments (such as patching) should be marked as to average depth of material placed. Leave this space blank for treatments that do not increase the pavement thickness (such as fog seal).
Total Cost (Item 8): The total costs for the maintenance work, reported in thousands of dollars per lane-mile. This should be calculated using the number of lanes and estimated total length over which the maintenance treatment has been applied. All nonpavement items (guardrails, lighting, etc.) should be excluded. To be consistent with other cost data, this information should include only cost of materials. Labor, traffic control, or other incidental costs should be excluded.
This data sheet provides space for recording in the field all maintenance activities performed on the LTPP monitoring site. SHAs can use this sheet to sketch the approximate location and extent of all treatment applications. This sheet gives data collectors the ability to summarize all activities for which more extensive data are recorded on sheets 3 to 17. The purpose of this sheet is to facilitate collection of all maintenance information.
Data sheets 3 and 4 are for recording data on seal coat and surface treatment applications. If more than one seal coat or surface treatment is applied, then one set (sheets 3 and 4) should be completed for each coat or layer. That is, repeat sheets 3 and 4 for each coat or layer.
Individual data elements are:
Date Work Began (Item 1): The month, day, and year the maintenance operation began.
Primary Reason for Seal Coat (Item 2): Identify the primary purpose for placing the seal on the test section. Codes are provided on the data sheet, and space is provided for entering a reason other than those for which codes are provided.
Percent of Test Section Sealed (Item 3): The percent of the test section surface area over which the seal coat has been placed. For LTPP test sections, the percent of the monitored test section in the outside lane is to be entered.
Type of Seal Coat (Item 4): The type of seal coat (slurry, aggregate, fog, etc.) that has been applied to the pavement surface. Codes are provided on the data sheet. Space is provided to specify a different type of seal coat, where applicable. If more space is needed, attach a separate piece of paper to this form. If multiple coats are applied, repeat sheets 3 and 4 for each seal.
Type/Grade of Bituminous Material in Seal Coat (Item 5): Appendix A, table A.15 provides a comprehensive list of possible types and grades, as taken from information published by the Asphalt Institute.
Application Rate for Bituminous or Other Cementing Material (Item 6): The amount of bituminous material, to the nearest tenth of a gallon, placed per square yard (0.1 gal/yd2 (3.8 liters/0.84 m2) of pavement (water added to emulsified asphalt is included).
Application Rate for Aggregate (Item 7): The amount by weight of aggregate, to the nearest tenth of a pound (0.1 lb) (0.045 kg) including mineral filler, placed per square yard of pavement (0.1 lb/yd2 (45g/0.84 m2).
Approximate Finished Surface Treatment Thickness (Item 8): The approximate thickness of the applied seal coat, to the nearest tenth of an inch (0.1 inch) (2.5 mm).
Ambient Conditions at Time Seal Coat Applied (Item 9): Air temperature in degrees Fahrenheit (°F) and a code entered to indicate whether the surface was dry or wet at the time the seal coat was applied.
Average Crack Severity Level (Item 10): The average severity level of the cracks in the test section. The codes are provided on the data forms. The Distress Identification Manual should be used to identify the definitions for the severity levels.
Primary Type of Cracks (Item 11): A code entered to describe the primary type of cracking prevalent in the test section and evaluated in item 10 (above). Codes are provided in appendix A, table A.21. A complete description of each crack type listed in table A.21 is available in the Distress Identification Manual.
This data sheet is a continuation of the seal coat data recorded on sheet 3.
Individual data elements are:
Gradation of Aggregate (Item 1): The percent of aggregate (including mineral filler) passing various standard sieve sizes, to the nearest one percent. Values will likely not be available for all 13 sieve sizes listed. The objective of this list is to provide space for a sufficient number of sieve sizes to accommodate testing and specification practice for most State and Provincial agencies.
Aggregate Precoated (Item 2): A code entered to indicate whether or not the aggregate used in the seal coat was coated with bituminous material before placement. Codes are provided on the data sheet.
Roller Used for Seating Aggregate (Item 3): A code entered for indicating what type of roller was used for seating the aggregate into the asphalt. Codes appear on the data sheet.
Estimated Time Allowed for Seal Coat to Cure Prior to Traffic Application (Item 4): A code, as provided on the data sheet, used to identify the approximate length of time between application of the seal coat and opening the section to traffic (usually from completion of rolling or seating the aggregate; if no aggregate was placed, then from the time the liquid was applied).
Condition of Surface Before Sealing (Item 5): A code entered to indicate whether the surface of the existing pavement was clean, moderately clean, or dirty when the seal coat was placed.
Initial Existing Pavement Surface Preparation (Item 6): A code entered to indicate the method of initial preparation for the existing pavement surface. The codes appear on the data sheet, and space is provided to describe a method not coded, where applicable. Attach a separate piece of paper if more space is needed.
Final Preparation of Existing Pavement Surface (Item 7): A code entered to record the final surface preparation used on the existing AC surface before seal coat application. The codes for various surface preparation methods appear on the data sheet.
This data sheet is for reporting the details of sealing individual cracks to prevent moisture intrusion into the underlying layers. If a seal coat is used over a broad area for crack sealing, it should be reported on maintenance data sheets 3 and 4.
Individual data elements are:
Date Work Began (Item 1): The month, day, and year the maintenance activity began.
Average Crack Severity Level (Item 2): The average severity level of the cracks in the test section. Codes are provided on the data forms. The Distress Identification Manual should be used to determine the definition of the various severity levels.
Primary Type of Cracks (Item 3): A code entered to describe the primary type of cracking prevalent over the monitored test section and evaluated in item 2 above. Codes are provided in appendix A, table A.21. A complete description of each type of crack listed in table A.21 is available in the Distress Identification Manual.
Type of Material Used to Seal Cracks (Item 4): A code entered to record the type of material used to seal the cracks in the pavement surface. Codes are provided on the data sheet. If a proprietary crack/joint sealant or some other type not coded is used, spaces are provided to record additional information to identify the material.
Ambient Conditions at Time of Crack Sealing (Item 5): The low and high air temperatures observed during crack sealing activities in degrees Fahrenheit (ºF), and a code entered to indicate whether the surface was dry or wet at the time the cracks were sealed.
Approximate Total Length of Cracks Sealed (Item 6): The approximate total linear feet of individual cracks sealed within the test section to the nearest foot. For LTPP studies, only the total linear feet of cracks sealed within the limits of the test section in the outer lane are to be recorded.
Method Used to Clean Crack Prior to Sealing (Item 7): A code entered to record the procedure used to clean the debris from cracks before sealing. Codes are provided on the data sheet.
This data sheet is for reporting data on patches within a test section with an AC surface, which includes only the outside lane used by LTPP for monitoring.
Individual data elements are:
Date Work Began (Item 1): The month, day, and year that the maintenance work began.
Primary Reason for Patches (Item 2): A code entered for indicating the primary distress requiring patching. Where patching was required for more than one reason or distress, enter the cause resulting in the greatest area of patching. Codes appear in appendix A, table A.21, and space is provided for writing in a reason for which no code is provided. For a complete description of each distress type, see the Distress Identification Manual.
Secondary Reason for Patches (Item 3): A code entered for indicating a second reason for patching using codes as discussed under item 2.
Patches (Item 4): The number and square feet (ft²) of patches, differentiated by vertical extent of the patch: whether only the surface was replaced, the surface and a pavement layer that had been overlaid, all AC and PCC layers and part of the base, or all AC and PCC layers and the full depth of the base. Full depth patching refers to total replacement of the pavement materials at a particular location. There is no intention to imply a registered term certifying replacement of all materials with asphalt bound material.
If Patched Pavement is AC Overlay of PCC, Was Patch (Item 5): A code entered to indicate whether the pavement patched is an AC overlay of a PCC pavement, and whether the patch material is all AC or AC over PCC to match existing materials. If the pavement structure is not AC overlay of PCC, leave the space blank. Codes appear on the data sheet.
Surface Material(s) Used to Patch Pavement (Item 6): A code to identify the type of surface material(s) used for patching. Spaces are provided on the data form for up to two material types. Where a material other than those listed is used, space is given for providing additional detail. If more than two types of surface material are used, specify the two used in the greatest area of patching.
Method of Compaction (Item 7): A code entered to specify the method used for compacting the new patch material. Codes are provided on the data sheet.
Method Used to Determine Location and Sizes of Patches Required (Item 8): A code entered to specify the means of locating areas requiring patching and identifying the limits of the areas to be patched. Codes are provided on the data form. Where some method other than those listed was used, space is provided to specify that method.
Method Used to Cut Boundaries (Item 9): A code entered to indicate the method used for cutting the existing pavement at the patch boundary. Codes are provided on the data form.
This data sheet is for reporting on patches within a test section with a PCC surface, which includes only the outside lane used by LTPP for monitoring. Partial depth patching includes replacing only a portion of the total pavement and base structure. It does not include replacing all pavement and base courses down to the subgrade.
Individual data elements are:
Date Work Began (Item 1): The month, day, and year that performance of the maintenance activity began.
Primary Reason for Patches (Item 2): A code entered to indicate the primary distress requiring patching. Where patching was required for more than one reason or distress, enter the cause resulting in the greatest area of patching. Codes appear in appendix A, table A.21, and space is provided for writing in a reason for which no code is provided. For a complete description of each distress type listed in table A.21, see the Distress Identification Manual.
Secondary Reason for Patches (Item 3): A code entered to indicate a second reason, or distress, for patches using codes as discussed above.
Patches (Item 4): The approximate area patched in square feet (ft2), the number of patches, and the average depth of the patches to the nearest tenth of an inch (0.1 inch) (2.5 mm).
Method Used for Patch Boundary Determination (Item 5): A code entered to provide the method used to identify the limits of the areas to be patched. Codes are provided on the data form.
Method Used to Cut Boundaries (Item 6): A code entered to indicate the method used for cutting the existing pavement at the patch boundary. Codes are provided on the data form.
Method Used to Break Up and/or Remove Deteriorated Concrete (Item 7): A code entered to identify the method used to break up and/or remove the existing PCC materials. Codes are provided on the data sheet.
Method for Final Cleaning of Patch Area (Item 8): A code entered to specify the means of final surface preparation used to prepare the area to be patched. Codes are provided on the data form.
This data sheet is a continuation of the partial depth patching data recorded on data sheet 7.
Individual data elements are:
Patch Material Used (Item 1): A code entered to record the type of surface material used to patch the pavement. Codes are provided on the data form. Where a material other than those specified is used, it should be described in the space provided.
Bonding Agent (Item 2): A code entered to identify the material used to bond the patch material to the existing PCC. Codes are provided on the data form.
Mixture Design for Patch Material (Item 3): The pounds per cubic yard (lbs/yd³) of coarse aggregate, fine aggregate, cement, and water (report gallons per cubic yard (gals/yd³) in the patch mixture. Coarse aggregate is aggregate retained on the No. 4 (4.75-mm) sieve. Appropriate entries are to be made depending on the type of patch material (AC, PCC, etc.) used. For AC patch material, leave the space for "water" blank.
Type Cement Used (Item 4): A code entered to record the type of cement used in the patch mix. Types of cement and associated codes are shown in appendix A, tables A.10 and A.14, for portland and asphalt cements, respectively.
Air Content (Item 5): The mean air content in percent by volume and range of air contents in the PCC mix to the nearest tenth of 1 percent (0.1 percent). Where AC is used as the patch material, these spaces are to be left blank.
Admixtures (Item 6): This item covers admixtures added to the concrete mix for whatever reason necessary. Spaces are provided to list up to two types of admixtures. Codes are provided in appendix A, table A.11. Where AC has been used as the patch material or where admixtures have not been used, these spaces are to be left blank.
Slump (Item 7): The mean and range (minimum and maximum measure values) of the slump for the PCC patch material to the nearest tenth of an inch (0.1 inch) (2.5 mm). Where AC is used as the patch material, these spaces are to be left blank.
Compressive Strength of Patch Material (Item 8): The compressive strength of a standard cylinder of PCC patch material in pounds per square inch (psi) after a certain curing period in days. Where AC is used as the patch material, these spaces are to be left blank. If compression tests were not performed and some other strength test (such as the indirect tensile test) was performed, space is provided to identify the type of testing performed on the patch material, type of loading, age at testing, and measured strength. Refer to the test designation by AASHTO, American Society for Testing and Materials (ASTM), or other agency.
Maximum Size of Coarse Aggregate (Item 9): The maximum size of coarse aggregate used in the patch material to the nearest tenth of an inch (0.1 inch) (2.5 mm).
This data sheet is for continuation of the partial patching data recorded on data sheets 7 and 8.
Individual data elements are:
Curing Method (Item 1): Space is provided to identify up to two methods, if any, used for curing the patch material. Codes are provided on the data form. Space is also provided to specify some other method if the method used is not shown . Where AC is used as the patch material, these spaces are to be left blank. Where only one method is used, enter code for "Method 1" and leave "Method 2" blank.
Approximate Time Between Patching and Opening to Traffic (Item 2): The approximate time in hours from placement of materials until traffic was allowed on the patch surface.
Ambient Conditions at Time of Patching (Item 3): The low and high air temperatures observed during patching activities in degrees Fahrenheit (ºF), and a code entered to indicate whether the surface was dry or wet at the time of patching.
Method of Consolidating Materials (Item 4): A code entered for identification of the means of consolidating the patch materials. Codes are provided on the data form.
Finishing Method (Item 5): A code entered to record the method used to finish the patch surface. Codes are provided on the data form. Where AC is used as the patch material, this space is to be left blank.
Joint Forming Method (Item 6): Codes entered to specify the method used for forming contraction joints in the patched concrete pavement surface for longitudinal, transverse, and shoulder joints where they may be present. Codes are provided on the data form. Where AC is used as the patch material, these spaces are to be left blank.
This data sheet is for recording details of replacement of joint seals in PCC pavements. If more than one material or method is used for different joints, repeat sheets 10 and 11 for each type.
Individual data elements are:
Date Work Began (Item 1): The month, day, and year the maintenance activity began.
Method of Removing Old Sealant (Item 2): A code entered to identify the method used for removing any old or existing joint sealant. Codes are provided on the data form.
New Sealant Reservoir Dimensions (Item 3): The width and depth of the sealant reservoir to the nearest tenth of an inch (0.1 inch) (2.5 mm).
Bond Breaker Under Sealant (Item 4): A code entered to identify the material used to prevent an adhesive bond between the sealant and the bottom of the reservoir. Codes are provided on the data form. Space is also provided to specify another material or method, where applicable.
Were Jointed Sidewalls Refaced (Item 5): A code entered to specify whether none, one, or both sidewalls were refaced during the joint resealing process. Codes are provided on the data form.
Cleaning of Sidewalls (Item 6): A code entered to specify the means of cleaning the sidewalls prior to resealing. Codes are provided on the data form.
This data sheet is a continuation of the data recorded on sheet 10. If more than one material or method is used for different joints, repeat sheets 10 and 11 for each type.
Individual data elements are:
Type of Contraction Joint Sealant (Item 1): A code entered to specify the AASHTO/ASTM designation of the type of joint sealant material used. Codes are provided on the data form. Space is also provided to include information regarding the manufacturer and the product's specific name, where a joint sealant is used for which no code is provided.
Average Depth of Top of Sealant Placement (Item 2): The depth to the nearest tenth of an inch (0.1 inch) (2.5 mm) from the top of the slab to the top of the joint sealant material.
Are Expansion Joints Sealed Differently than Contraction Joints (Item 3): A code entered to indicate differences in sealing materials used for contraction and expansion joints. Codes are provided on the sheet.
Total Linear Feet of Joints Sealed (Item 4): The total linear feet to the nearest tenth of a foot (0.1 ft) (0.03 m) of joints sealed on the monitoring site. These are to be recorded as quantity of transverse and longitudinal joints.
This data sheet is for providing information regarding grinding or milling for safety reasons.
Individual data elements are:
Date Work Began (Item 1): The month, day, and year the maintenance activity began.
Pavement Surface Type (Item 2): A code entered to report whether the surface material was AC or PCC. Codes are provided on the data form.
Method Used (Item 3): A code entered to report whether the surface material was removed by diamond grinding or milling equipment. Codes appear on the data sheet.
Reason for Grinding, Milling, or Grooving (Item 4): The primary reason for grinding or milling the pavement section. Codes are provided on the data form. Space is provided to indicate another reason if an appropriate code has not been provided.
Extent of Grinding, Milling, or Grooving (Item 5): A code entered to indicate whether the grinding or milling has been performed only over individual joints or patches, or has been performed over the entire section. Codes are provided on the data form.
Average Depth of Cut (Item 6): The average depth of the cut in the surface material to the nearest tenth of an inch (0.1 inch) (2.5 mm).
Cutting Head Width (Item 7): The approximate width to the nearest tenth of an inch (0.1 inch) (2.5 mm) of the machine cutting head.
Average Groove Width (Item 8): The average groove width to the nearest tenth of an inch (0.1 inch) (2.5 mm). Leave these spaces blank if diamond grinding or grooving is not the method used.
Average Spacing Between Blades (Item 9): The average spacing between the grinding blades to the nearest tenth of an inch (0.1 inch) (2.5 mm). Leave these spaces blank if diamond grinding or grooving is not the method used.
This data sheet is for reporting details of full depth repair, including either full depth patches or complete slab replacement, for pavements with PCC surfaces.
Individual data elements are:
Date Work Began (Item 1): The month, day, and year the maintenance activity began.
Primary Reason for Patches or Slab Replacement (Item 2): A code entered for indicating the primary distress requiring patching or slab replacement. Where patching or slab replacement is required for more than one reason or distress, enter the distress resulting in the greatest repair area. Codes appear in appendix A, table A.21, and space is provided for writing in a reason for which no code is provided. For a complete description of each distress type, see the Distress Identification Manual.
Secondary Reason for Patches or Slab Replacement (Item 3): A code entered for indicating a second type of distress requiring patching or slab replacement, using codes as discussed above.
Patches (Item 4): The number and square feet (ft²) of patches differentiated by depth of material replaced whether only the slab has been replaced, or both the slab and the base.
Patch Material Used (Item 5): A code entered to record the type of surface material used to patch the pavement. Codes are provided on the data form.
Slabs Replaced (Item 6): The number and square feet (ft²) of slabs replaced, differentiated by whether only the slab has been replaced or both the slab and part of the base.
Base Replaced By (Item 7): The materials used to replace the base for patches and slab replacement, respectively. Codes appear on the data form. Leave this space blank if the base has not been replaced.
Method for Patch Boundary Determination (Item 8): A code entered to indicate the means of determining the extent of the area to be patched, or whether entire slabs should be replaced. Codes are provided on the data form.
Cutting Instrument (Item 9): A code entered to specify the instrument used to cut the boundaries of the area to be patched. Codes are provided on the data form.
This data sheet is a continuation of the full depth repair data for PCC pavements recorded on sheet 13.
Individual data elements are:
Type of Joint Load Transfer System Used for Repaired Areas (Item 1): The type of joint load transfer systems used for the transverse and longitudinal joints in the newly repaired area, respectively. Codes are provided on the data form, and space is included for entering a type for which no code is provided.
Securing Load Transfer Devices (Item 2): A code entered to indicate the material used to grout or epoxy load transfer devices into drilled or preformed holes. Codes are provided on the data form.
Reinforcing Steel Placed in Patch (Item 3): A code entered to indicate whether or not the patched area contains reinforcing steel. Codes are provided on the data form.
Bar Diameters (Item 4): The rebar numbers of the longitudinal and transverse bars or wire mesh (tied or untied to old concrete) in the full-depth repair. If neither longitudinal nor transverse bars are used, the appropriate spaces may be left blank for these and the next three items.
Bar Lengths (Item 5): The lengths of longitudinal and transverse bars or wire mesh, to the nearest tenth of an inch (0.1 inch) (2.5 mm).
Bar Spacings (Item 6): The approximate center-to-center spacing of adjacent longitudinal and transverse bars or wire mesh, to the nearest tenth of an inch (0.1 inch) (2.5 mm).
Dowel Coatings (Item 7): Codes entered to record the coatings used on longitudinal and transverse dowel bars. Codes are provided on the data sheet. If dowel bars were not used, leave this space blank.
Number of Saw Cuts per Patch (Item 8): The number of saw cuts required per patch, if any.
Depth of Typical Boundary Saw Cut (Item 9): The depth, to the nearest tenth of an inch (0.1 inch) (2.5 mm), of the average boundary saw cut.
Concrete Breakup (Item 10): A code entered to specify the means of breaking up the existing concrete to be removed. Codes are provided on the data form.
Removal of Concrete (Item 11): A code entered to indicate the method of material removal from the area patched.
This data sheet is a continuation of the full depth repair data recorded on sheets 13 and 14.
Individual data elements are:
Method of Reinforcing Steel Placement (Item 1): A code entered to indicate the means of placing the reinforcing steel. Codes are provided on the data form. If reinforcing steel is not included, this space should be left blank.
Mixture Design for Patch Material (Item 2): The pounds per cubic yard (lbs/yd³) of coarse aggregate, fine aggregate, cement, and water (report gallons per cubic yard) in patch mixture. Coarse aggregate is aggregate retained on a No. 4 (4.75-mm) sieve. For AC patch material, leave the space for "water" blank.
Type Cement Used (Item 3): A code entered to indicate the type of cement used in the patch mix. Types of cement and associated codes are provided in appendix A, tables A.10 and A.14, for portland and asphalt cements, respectively.
Air Content (Item 4): The mean air content and the range of the measured values (in percent by volume) in the PCC mix, to the nearest one-tenth of 1 percent (0.1 percent). Where AC is used as the patch material, leave these spaces blank.
Admixtures (Item 5): Admixtures added to the PCC mix for whatever purpose necessary. Space is provided to list up to two types of admixtures. A list of admixtures is provided in appendix A, table A.11. Where AC is used as the patch material, leave these spaces blank.
Slump (Item 6): The mean slump and the range (minimum and maximum measured value) for PCC patch material, to the nearest tenth of an inch (0.1 inch) (2.5 mm). Where AC is used as the patch material, leave these spaces blank.
Flexural Strength (Modulus of Rupture) (Item 7): The mean flexural strength of the PCC mix used in the patch in pounds per square inch (psi), based on third-point loading (ASTM C78), and the number of days the beam was cured before testing. If third-point beam tests have not been performed and some other strength test (such as compressive or indirect tensile tests) has been used, space is provided to identify the type of strength testing performed on the concrete mixture, the type of loading, age at testing, and measured strength. Refer to a test designation by AASHTO, ASTM, or other agency. Where AC is used as the patch material, leave these spaces blank.
Ambient Conditions at Time of Patching (Item 8): The low and high air temperatures observed during patching activities in degrees Fahrenheit (ºF) and a code entered to indicate whether the surface was dry or wet at the time of patching.
Maximum Size of Coarse Aggregate (Item 9): The maximum size of the coarse aggregate in the patch material to the nearest tenth of an inch (0.1 inch) (2.5 mm).
This data sheet is a continuation of full depth repair data recorded on sheets 13, 14, and 15. Where AC is used as the patch material, the only data entered on this sheet are for "Item 4: Approximate Time Between Patching and Opening to Traffic" and "Item 5: Consolidation of Materials."
Individual data elements are:
Joint Forming Method (Item 1): Codes entered to specify the method used for forming contraction joints in the shoulder, transverse direction, and longitudinal direction. Codes are provided on the data form. Where some method other than those listed has been used, space is provided to identify specifics.
Was Bond Breaker Used Between Adjacent Lanes? (Item 2): A code entered to indicate whether a bond breaker has been used to discourage bonding between the new patch and an adjacent lane. Codes are provided on the data form.
Curing Method (Item 3): Space is provided to identify up to two methods used for curing the patch material. Codes are provided on the data form. Where only one method is used, enter code for "Method 1" and leave "Method 2" blank.
Approximate Time Between Patching and Opening to Traffic (Item 4): The approximate time in hours from placement of materials until traffic was allowed on the patch surface.
Consolidation of Materials (Item 5): A code entered to indicate the means of consolidating patch materials into the area patched. Codes are provided on the data form.
Finishing (Item 6): A code entered to indicate the means of finishing the surface of the patched area or new slab. Codes are provided on the data form.
Type of Transverse Joints in Patches or Slabs (Item 7): Codes entered to indicate the type of joints used adjacent to or inside the patches or new slabs, including expansion joints, contraction joints, or a mixture of the two. Codes are provided on the data form. Leave code for patches blank if no patches are adjacent to or include joints. Leave code for slabs blank if no full slabs have been replaced.
Were Old Joints Matched (Item 8): A code entered to indicate whether joints in the patch have been matched with the old existing joints in the pavement. Codes are provided on the data form.
This data sheet provides spaces for recording measured or estimated quantities of materials used on the test section in units specified; and for recording average costs per unit in dollars and total costs in thousands of dollars for each maintenance type for which data sheets have been provided. Spaces are also provided for entering the length of the test section treated. This figure will be used to convert the total cost of the maintenance on the test section to cost per lane-mile to provide compatibility with other cost data collected. All non pavement items (guardrails, lighting, etc.) should be excluded. To be consistent with other cost data, this information should include only cost of materials. Labor, traffic control, or other incidental costs should be excluded.
This data sheet is used for recording data for sealing of cracks in PCC pavements. If more than one material or method is used for different cracks, complete sheet 18 for each type.
Individual data elements are:
Date Work Began (Item 1): This is the date on which crack sealing operations began.
New Sealant Reservoir Dimensions (Item 2): The width and depth of sealant reservoir to the nearest tenth of an inch (0.1 inch) (2.5 mm).
Bond Breaker Under Sealant (Item 3): A code entered to identify the material used to prevent an adhesive bond between the sealant and the bottom of the reservoir. Codes are provided on the data form. Space is also provided to identify other materials used.
Cleaning of Cracks (Item 4): A code to specify the means of cleaning the cracks before sealing. Codes are provided on the data form.
Type of Sealant (Item 5): A code to specify the AASHTO/ASTM designation of the type of crack sealant material used. Codes are provided on the data form. Space is also provided to enter information on the manufacturer and the product's specific name, if no code is provided for the crack sealant used.
Average Depth of Top of Sealant Placement (Item 6): The depth to the nearest tenth of an inch (0.1 inch) (2.5 mm) from the top of the slab to the top of the crack sealant material.
Total Linear Feet of Cracks Sealed (Item 7): The total linear feet to the nearest tenth of a foot (0.1 ft) (0.03 m) of cracks sealed on the test section.
This data sheet is to be completed each time maintenance activities are performed on a test section.
Individual data elements are:
Date Completed (Item 1): The month, day, and year that the pavement improvements were finished and the project was subsequently opened to traffic (not the date when the project was accepted).
Work Type Code (Item 2): A code to identify the type of maintenance work accomplished (appendix A, table A.16).
Copies of LTTP maintenance data sheets 1 through 19 are included below.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
NOTES: |
