Michigan Department CHECKLIST TO DESIGNATE AREAS OF ... · E-Verify system is operated by the...

Michigan Department Of Transportation

5100B (09/16) CHECKLIST TO DESIGNATE AREAS OF EVALUATION

FOR REQUESTS FOR PROPOSAL (RFP) of 2

REQUISITION NUMBER DUE DATE TIME DUE

MDOT PROJECT MANAGER JOB NUMBER (JN) CONTROL SECTION (CS)

DESCRIPTION

MDOT PROJECT MANAGER: Check all items to be included in RFP

WHITE = REQUIRED ** = OPTIONAL

Check the appropriate Tier in the box below

CONSULTANT: Provide only checked items below in proposal When applicable, Best Value scoring criteria is listed separately in the RFP.

TIER 1 ($50,000 - $150,000)

TIER II ($150,000-$1,000,000)

TIER III (>$1,000,000)

Understanding of Service **

Innovations

Organizational Chart

Qualifications of Team

Quality Assurance/Quality Control **

Location: The percentage of work performed in Michigan will be used for all selections unless the project is for on-site inspection or survey activities, then location should be scored using the distance from the consultant office to the on-site inspection or survey activity.

N/A N/A Presentation **

N/A N/A Technical Proposal (if Presentation is required)

7 pages (MDOT Forms not counted)

14 pages (MDOT forms not counted)

Total maximum pages for RFP not including key personnel resumes. Resumes limited to 2 pages per key staff personnel.

PROPOSAL AND BID SHEET E-MAIL ADDRESS – [email protected]

GENERAL INFORMATION

Any questions relative to the scope of services must be submitted by e-mail to the MDOT Project Manager. Questions must be received by the Project Manager at least five (5) working days prior to the due date and time specified above. All questions and answers will be placed on the MDOT website as soon as possible after receipt of the questions, and at least three (3) days prior to the RFP due date deadline. The names of vendors submitting questions will not be disclosed.

MDOT is an equal opportunity employer and MDOT DBE firms are encouraged to apply. The participating DBE firm, as currently certified by MDOT’s Office of Equal Opportunity, shall be listed in the Proposal.

MDOT FORMS REQUIRED AS PART OF PROPOSAL SUBMISSION

5100D – Request for Proposal Cover Sheet 5100J – Consultant Data and Signature Sheet (Required for all firms performing non-prequalified services on this project.)

(These forms are not included in the proposal maximum page count.)

3 pages (MDOT Forms not counted) Resumes will only be accepted forBest Value Selections

N/A

N/A N/A

mailto: [email protected]

MDOT 5100B (09/16) REQUEST FOR PROPOSAL of 2

The Michigan Department of Transportation (MDOT) is seeking professional services for the project contained in the attached scope of services.

If your firm is interested in providing services, please indicate your interest by submitting a Proposal, Proposal/Bid Sheet or Bid Sheet as indicated below. The documents must be submitted in accordance with the latest (Consultant/Vendor Selection Guidelines for Services Contracts.”

RFP SPECIFIC INFORMATION

ENGINEERING SERVICES BUREAU OF TRANSPORTATION PLANNING OTHER THE SERVICE WAS POSTED ON THE ANTICIPATED QUARTERLY REQUESTS FOR PROPOSALS

NO YES DATED____________________ THROUGH ________________

Prequalified Services – See the attached Scope of Services for required Prequalification Classifications.

Non-Prequalified Services – If selected, the vendor must make sure that current financial information, including labor rates, overhead computations, and financial statements, is on file with MDOT’s Office of Commission AuditsThis information must be on file for the prime vendor andall sub vendors so that the contract will not be delayed.Form 5100J is required with proposal for all firmsperforming non-prequalified services on this project.

For all Qualifications Based Selections, the selection team will review the information submitted and will select the firm considered most qualified to perform the services based on the proposals. The selected firm will be asked to prepare a priced proposal. Negotiations will be conducted with the firm selected.

For a cost plus fixed fee contract, the selected vendor must have a cost accounting system to support a cost plus fixed fee contract. This type of system has a job-order cost accounting system for the recording and accumulation of costs incurred under its contracts. Each project is assigned a job number so that costs may be segregated and accumulated in the vendor’s job-order accounting system.

Qualification Based Selection / Low Bid – Use Consultant/Vendor Selection Guidelines. See Bid Sheet instructions for additional information.

For Qualification Review/Low Bid selections, the selection team will review the proposals submitted. The vendor that has met established qualification threshold and with the lowest bid will be selected.

Best Value – Use Consultant/Vendor Selection Guidelines, See Bid Sheet Instructions below for additional information. The bid amount is a component of the total proposal score, not the determining factor of the selection.

Low Bid (no qualifications review required – no proposal required.)

BID SHEET INSTRUCTIONS

Bid Sheet(s) are located at the end of the Scope of Services. Submit bid sheet(s) with the proposal, to the email address: [email protected]. Failure to comply with this procedure may result in your bid being rejected from consideration.

MDOT and ACEC created a Partnership Charter Agreement which establishes guidelines to assist MDOT and Consultants in successful partnering. Both the Consultant and MDOT Project Manager are reminded to review the ACEC-MDOT Partnership Charter Agreement and are asked to follow all communications, issues resolution and other procedures and guidance’s contained therein.

Qualification Based Selection - Use Consultant/Vendor Selection Guidelines.

PARTNERSHIP CHARTER AGREEMENT

http://www.michigan.gov/documents/mdot/ACEC_PartnershipCharterAgreement_1-27-12_399925_7.pdf

http://www.michigan.gov/documents/mdot/ACEC_PartnershipCharterAgreement_1-27-12_399925_7.pdf

mailto:[email protected]

PROPOSAL REQUIREMENTS

Proposals must be submitted for this project electronically. Proposal submittal requirements are

listed in PART IV – INSTRUCTION FOR SUBMITTING PROPOSALS

at the following link http://www.michigan.gov/documents/MDOT_Consultant-

Vendor_Selection_Guidelines-0106_145222_7.pdf?20150707153457

FINANCIAL REQUIREMENTS FOR NON-PREQUALIFIED VENDORS

http://www.michigan.gov/documents/mdot/Financial_Requirements_for_Non_Prequalified_Ven

dors_605817_7.pdf

E-VERIFY REQUIREMENTS

E-Verify is an Internet based system that allows an employer, using information reported on an

employee’s Form I-9, Employment Eligibility Verification, to determine the eligibility of that

employee to work in the United States. There is no charge to employers to use E-Verify. The

E-Verify system is operated by the Department of Homeland Security (DHS) in partnership with

the Social Security Administration. E-Verify is available in Spanish.

The State of Michigan is requiring, under Public Act 200 of 2012, Section 381, that as a

condition of each contract or subcontract for construction, maintenance, or engineering services

that the pre-qualified contractor or subcontractor agree to use the E-Verify system to verify that

all persons hired during the contract term by the contractor or subcontractor are legally present

and authorized to work in the United States.

Information on registration for and use of the E-Verify program can be obtained via the Internet

at the DHS Web site: http://www.dhs.gov/E-Verify.

The documentation supporting the usage of the E-Verify system must be maintained by each

consultant and be made available to MDOT upon request.

It is the responsibility of the prime consultant to include the E-Verify requirement documented in

this NOTIFICATION in all tiers of subcontracts.

DIGITAL SIGNATURE OF CONTRACTS

On January 1, 2018, Contract Services Division intends to fully implement the use of CoSign as

the exclusive software for digitally signing all consultant contracts and consultant contract

related documents. All other digital signing methods will no longer be accepted.

Prior to using CoSign, all external partners must apply for a free digital signature user account by

submitting a MDOT Digital Signature Certificate Request Form.

http://www.michigan.gov/documents/MDOT_Consultant-Vendor_Selection_Guidelines-0106_145222_7.pdf?20150707153457

http://www.michigan.gov/documents/MDOT_Consultant-Vendor_Selection_Guidelines-0106_145222_7.pdf?20150707153457

http://www.michigan.gov/documents/mdot/Financial_Requirements_for_Non_Prequalified_Vendors_605817_7.pdf

http://www.michigan.gov/documents/mdot/Financial_Requirements_for_Non_Prequalified_Vendors_605817_7.pdf

https://mdotjboss.state.mi.us/webforms/GetDocument.htm?fileName=2122.pdf

2017 Insurance Update – MDOT 3.9.17

At a minimum, the insurance types and limits identified below, may be required from the selected consultant, prior to contract award.

.

Required Limits Additional Requirements

Commercial General Liability Insurance

Minimal Limits:

$1,000,000 Each Occurrence Limit

$1,000,000 Personal & Advertising Injury Limit

$2,000,000 General Aggregate Limit

$2,000,000 Products/Completed Operations

Consultants must have their policy endorsed

to add “the State of Michigan, its

departments, divisions, agencies, offices,

commissions, officers, employees, and

agents” as additional insureds

Automobile Liability Insurance

Minimal Limits:

$1,000,000 Per Occurrence

Workers' Compensation Insurance

Minimal Limits:

Coverage according to applicable laws

governing work activities.

Waiver of subrogation, except where waiver is

prohibited by law.

Employers Liability Insurance

Minimal Limits:

$500,000 Each Accident

$500,000 Each Employee by Disease

$500,000 Aggregate Disease

Professional Liability (Errors and Omissions) Insurance

Minimal Limits:

$1,000,000 Per Claim

The Insurer shall provide at least thirty (30) days written notice of cancellation. The Prime Consultant will be responsible to verify subconsultant(s) compliance with MDOT’s insurance requirements.

Revised Final Posted Scope: 12/11/2017 Page 1 of 108

Michigan Department of Transportation

SCOPE OF SERVICE

For

SPECIALTY SERVICE

Pavement Condition Data Collection and Processing

Years 2018 – 2021

Revised 12/14/2017

CONTROL SECTION(S): Statewide

JOB NUMBER(S): Not Applicable

PROJECT LOCATION: Not Applicable

PROJECT DESCRIPTION:

Collection & processing of detailed pavement surface condition metrics (distress type/extent/severity

identification per MDOT definitions; International Roughness Index measurement; wheelpath rut

depth measurement; transverse joint fault height measurement), roadway imagery, and horizontal

alignment/longitudinal grade measurement.

ANTICIPATED SERVICE START DATE: Spring 2018

ANTICIPATED SERVICE COMPLETION DATE: Winter 2021

PRIMARY PREQUALIFICATION CLASSIFICATION(S): Not Applicable

SECONDARY PREQUALIFICATION CLASSIFICATION(S): Not Applicable

PREFERRED QUALIFICATIONS AND CRITERIA (FOR NON-CLASSIFIED SERVICES):

Vendors with a minimum of 10 years of experience in providing network-level pavement condition

data collection services to state transportation agencies.

Engineering expertise is required.

Selection Criteria:

Understanding of Service (as defined in this MDOT Scope-of-Service document)

Technical Proposal

Innovations

Organizational Chart

Qualifications of Team

Past performance in servicing state agencies with comparably-sized roadway networks

Quality Assurance/Quality Control

Location


Presentation

MDOT PROJECT MANAGER:

Daniel J. Sokolnicki, P.E.

425 W. Ottawa St.

P.O. BOX 30050

Lansing, MI 48909

517/241-0736

[email protected]

CONSULTANT PAYMENT – Unit Price:

Compensation for this project shall be on a unit price basis. This basis of payment includes an

estimated quantity of units and a maximum reimbursable cost per unit. Total yearly data-item mileage

quantities stated in this Scope of Service document are estimates; actual finally-determined quantities

will be established by MDOT prior to each collection season and will likely vary (increase or decrease

- to a minor degree) from those in this document.

All billings for services must be directed to the Department and follow the current guidelines.

Payment may be delayed or decreased if the instructions are not followed.

Payment to the Consultant for services rendered shall not exceed the maximum amount unless an

increase is approved in accordance with the contract with the Consultant. Typically, billings must be

submitted within 60 days after the completion of services for the current billing. The final billing

must be received within 60 days of the completion of services. Refer to your contract for your

specific contract terms.

Refer to the following two areas of this Scope of Service document for further details:

ATTACHMENT D (Vendor Pay Item Bid Sheet) - **FOR QUANTITY INFORMATION ONLY:

NO BIDS SHALL BE PROVIDED WITH THE

PROPOSAL. PROVISION OF BIDS WITH

THE PROPOSAL WILL BE CONSIDERED

NON-RESPONSIVE AND THE PROPOSAL

WILL BE NOT BE REVIEWED.**

ATTACHMENT E (Payment Structure & Criteria)


SUMMARY OF MAJOR SCOPE CHANGE FOR 2018-2021 SERVICES

(Listed in no particular order.)

1. Shortened collection completion and data delivery timeframes (including 2018 special schedule

to first focus on NHS collection/data delivery).

2. Included penalty stipulation for collection completion timeframes.

3. Specified 100% length-sampling of collection lane for distress (crack) surveying (including

elimination of PD0909 use).

4. Shortened data-correction delivery timeframes and changed penalty structure stipulations for

late collection completions and late data deliveries to per-day assessments.

5. Modified “20%-Limit” note for Field Data Collection price within Attachment D (Bid Sheet).

6. Added bridge/box-culvert deck areas to occurrences required for exclusion from rut-depth

analysis/reporting.

7. Within Attachment G (Distress Survey Manual), added text to certain longitudinally oriented

Primary Distress type definitions to clarify that any 0.001-mile segment along the lane having

at least 50% of its length covered by the subject distress type shall be recorded by the Vendor.

8. Added an updated version of the Primary Distress (PD) Translation table to the end of

Attachment G (Distress Survey Manual).

9. Within Attachment G, added text to pertinent load-related Primary Distress (PD) definitions -

defining requirement of Vendor to assume the wheelpath’s lateral location as located 34.5 inches

from the center of lane (in order to conform with HPMS Field Manual).

10. Within Attachment G, specified additional instructions within Primary Distress 0231 definition

(center-of-lane longitudinal crack) for that code to also be recorded to identify detected

deterioration of a center-of-lane longitudinal joint (within rarely existing thin concrete-overlay

segments).

11. Shortened the maximum allowable longitudinal distance interval for the Vendor’s

capture/storage of transverse surface profiles (for rut-depth determination) to 1 foot (which,

though more stringent than that stated within the referenced AASHTO standard listed within

Attachment B, is required to conform to the HPMS Field Manual rut-depth metric specification).


12. Added text to more explicitly require that fault-metric data shall only be based on Vendor

measurements across constructed transverse joints.

13. Removed requirements for roadside asset extraction services.

14. Within Attachment F (File Formats), changed requirements of how “0-values” are to be

populated in the Fault metric fields. Also added clarification text for required “null-entry”

population of certain sensor-data fields for locations designated as “Not-Surveyed” areas.

15. Within Attachment H (Distress Survey Data Acceptance Criteria), increased the minimum

passing score required per lot for MDOT acceptance.

16. Removed requirement for Vendor collection/provision of a rear-view roadway image.

17. Specified that Vendor’s weekly IRI-certification site profile data (.erd files) shall be

accompanied by lead-in/lead-out length information.

18. Within Attachment G (Distress Survey Manual), added clarifying information to Associated

Distress (AD) matrices relative to expected content of submitted distress survey data files.

19. Changed content of banner to be superimposed on top of each delivery image .jpeg file.

20. Changed (scaled-back) the content requirements for submitted image .jpeg file’s EXIF data.

21. Specified required datums and ellipsoid for GPS lat./long. data, and also changed data-correction

system requirements from utilization of WAAS to the MDOT CORS.

22. Specified that MDOT has yearly discretion to remove horizontal curvature/longitudinal grade

data collection/delivery requirement per each collection year.

23. Specified in Attachment A (Field Collection Procedures) that Vendor shall report to MDOT in

a timely manner any observed errors in the MDOT-provided route shapefile line topology’s

representation of actual in-field route alignment.

24. Removed requirement for Vendor to submit final collection log records. (Weekly collection log

records submittals shall still be required.)

25. Renamed the MDOT-provided TapeLog file’s “Region 8” column to “NonTrunkline”.

26. Eliminated the TapeLog file’s “images2” and “route order” columns.

27. Split the TapeLog file’s “CS_PR” column into two columns: “CS and “PR”

28. Added new Vendor measurement/reporting requirement for lane width, to be reported as an

additional column in the annually submitted statewide final sensor data file.


29. Added to the TapeLog file a column to indicate yearly requirement of lane width data per route

segment (TRUE or FALSE).

30. Changed the required format of Vendor’s weekly-submitted 0.1-mile IRI/rut/fault data (which

shall be consulted/clarified-with MDOT prior to each collection season).

31. Added language to discern between jointed and unjointed concrete pavement (JPCP v. CRCP)

relative to data recording/reporting requirements. (All distress survey calls for concrete shall be

used commonly between jointed and unjointed concrete (as defined by MDOT); fault-detection

across constructed transverse joints shall be provided only for jointed concrete.)


Vendor Selection Proposal Evaluations The MDOT Selection Team will used the following criteria to score submitted proposals.

Understanding of Service: Described understanding of the service and proposed applicable innovations shall be included. The information shall be based on the scope of services. Possible Points: 35 Qualifications of Team: Shall include an organization chart and description of project team structure including roles of all key personnel and sub-vendors, including percentage of work expected by each sub-vendor. Resumes for each of the key staff of the prime and sub-vendors stated above shall be included. Possible Points: 35 Past Performance: Performance evaluations performed in CTRAK software by MDOT staff will be used. The CTRAK average project score for the past three years will be doubled to arrive at the past-performance score. If no CTRAK performance evaluations exist, the Selection Team will perform reference checks. Possible Points: 25 Quality Control/Quality Assurance Process: Shall include description of the QC/QA plan for these services including background information of selected manager for such. The person performing the quality control review must have extensive experience with MDOT standards and practices. Possible Points: 20 Location: The percentage of work performed in Michigan will be used for all selections unless the project is for on-site inspection or survey activities, whereupon location will be scored using the distance from the consultant office to the on-site inspection or survey activity. Total Possible Points: 5

=====================================================

Minimum required points for advancement to presentation and technical proposal stage: 85 out of 120 ===================================================== Presentation (including Technical Proposal if Required): General evaluation of quality based upon - a) Description of collection equipment/process in relation to scope of service. b) Demonstration of collected-location/imagery-viewing software access/operation in relation to scope of service requirements. c) Description/demonstration of other process or system features, enhancements, or capabilities applicable to the scope of service requirements. Possible Points: 40 ===================================================== Final points required: 115 out of 160


TABLE OF CONTENTS

1. GENERAL INFORMATION

1.A. Introduction 10

1.B. Data Collection and Hardware/Software Needs 10 1.C. Summary of Michigan Routes to be Collected 12

2. DETAILED INFORMATION

2.A. Collection 13

A.1. Description 13

A.2. Collection, Deliverable Time Frames, and Associated Penalties 13

A.3. Collection Protocols 15

A.4. FrameID/Location Reference Identification and Weekly Reporting 18

2.B. Data Requirements 19

B.1. Roadway & Pavement Imagery 19

B.1.1. Description 19

B.1.2. Collection & Imaging QA 22

B.1.3. Final Submittal and Acceptance 22

B.2. Distress Type/Severity/Extent Identification 23

B.2.1. Processing 23

B.2.2. Survey Technique 23

B.2.3. Survey Technique Flexibility 23

B.2.4. Quality Control Plan 23

B.2.5. Delivery 24

B.2.6. MDOT Quality Assurance and Acceptance 24

B.2.7. Software 25

B.3. Transverse and Longitudinal Profiles 25


B.3.2. Equipment, Measurement, Operation, and Computation 26

B.3.3. Software and Documentation 27

B.3.4. Quality Control/Calibration 27


B.4. Grade and Curvature 29


B.4.2. Equipment and Measurement 29

B.4.3. Quality Control and Documentation 29

B.4.4. MDOT Quality Assurance 29

B.4.5. Reporting Format 29


B.4.6. Final Submittal and Acceptance 29


TABLE OF CONTENTS, con’t.

B.5. Global Positioning System (GPS) Data 27

B.5.1. Description and Standards 27

B.5.2. Corrections 27

B.5.3. Accuracy 28

B.5.4. Quality Control Plan 28

B.5.5. Deliverables 28


B.6. Lane Width 29 B.6.1. Description 29 B.6.2. Quality Control and Documentation 29 B.6.3. MDOT Quality Assurance 29 B.6.4. Reporting 29 B.6.5. Final Submittal and Acceptance 29

ATTACHMENT A - Required Field Collection Procedures 31

ATTACHMENT B - Applicable AASHTO Standard Specifications 35

ATTACHMENT C - 2018 – 2021 Collection & Delivery Schedule 36

ATTACHMENT D - Vendor Pay Item Bid Sheet (2018-2021) *For Quantity Reference *For Quantity Reference OnlyOnlyOn OnlyOnlyOn

37

ATTACHMENT E - Payment Structure & Criteria 41

ATTACHMENT F - File Formats of Location Referencing, Distress, and Sensor Data 44

ATTACHMENT G - Distress Manual for Surveying of Pavement Surfaces 63

ATTACHMENT H - Distress Survey Call Sampling, Testing, & Acceptance Criteria 103

APPENDIX - Definitions 105


1. GENERAL INFORMATION

A. Introduction

The State of Michigan, as represented by Michigan Department of Transportation

(MDOT), intends to use this Scope of Work to provide the Service Vendor

(Vendor) with information to enable them to prepare and submit a proposal for

pavement surface condition data & roadway imaging collection during the four-

year period of 2018 through 2021, inclusive. The Vendor’s proposal must include

a plan for accomplishing the collection, processing, reporting, and delivery of data

in compliance with the required specifications and procedures defined in this

document and clarified by the MDOT Project Manager, or his representative, as

needed. All necessary hardware and software must be supplied by the Vendor.

B. Data Collection and Hardware/Software Needs

The Vendor shall collect, process, report, and deliver seven general categories of data:

*Digital imaging of forward perspective view and pavement down view

*Surface distress (cracking) type/severity/extent identification and processing

*Longitudinal profile measurement (with IRI calculation and

detection/measurement of transverse constructed-joint faults)

*Transverse profile measurement (with wheelpath rut measurement)

* Longitudinal grade & horizontal alignment curvature measurement

*Global Positioning System (GPS) latitude/longitude data-tagging and

MDOT linear referencing system mileage

*Lane width

All pavement condition information for each specified pavement segment shall be

collected in one continuous pass at posted highway speeds, not to exceed 65 mph.

The relationships among the above six categories of data must be designed by

the Vendor according to relational database principles so that a record of each data

category shall contain unique referencing data values which are also in the

corresponding record of the other data categories. The Vendor shall provide

access to, and maintenance/support of, all hardware and software needed to meet the

specifications outlined in this document including association of pavement condition

data with collected roadway/pavement images.

The Vendor shall provide the necessary training to operate and troubleshoot any

software. All software and licenses necessary for MDOT to view, reduce, retrieve,

and analyze data shall be included in the contract price associated with software.

The Vendor shall provide upgrades of all software to MDOT at no charge. Any

software licensing rights granted by the Vendor shall be provided to all potential

users deemed necessary by MDOT in order to achieve its business objectives.

The users to be granted licensing rights shall include, but not be limited to, the


following groups located at any MDOT location at any time during the contract:

All MDOT permanent employees

All MDOT interns and temporary employees

All MDOT vendors

All MDOT partners

Any other group/individual necessary to achieve MDOT’s business objectives

Any group or individual not granted rights to use the software under this contract

will be directed by MDOT to purchase a legal copy and/or licensing rights from the

Vendor.

The Vendor shall provide comprehensive, readable user-manual and technical-

training documentation for all software/hardware including any updates.

All deliverables within this contract shall be covered by a warranty. This warranty

shall begin on the day the first deliverable is received by MDOT and shall conclude

three (3) years after the end of the contract.

Any upgrades to the system within the warranty period shall be performed at the

Vendor’s expense. Hardware and software shall be, and shall remain, compliant

with the Michigan Department of Technology, Management, and Budget operating

system standards. The applicable technical policies and procedures can be found at

http://www.michigan.gov/dmb/0,1607,7-150-56355---,00.html

All software and data shall continue to run despite any MS Windows operating

system standard changes or updates effected by MDOT. Currently, MDOT is

using Windows 7 Professional and will be moving to the Windows 10 standard

during the term of this contract. Vendor-supplied software or hardware malfunctions

experienced by MDOT shall be corrected within one week from the time of

notification by the MDOT Project Manager. The Vendor shall incur a penalty of

$1,000 per each calendar day late that the correction is delayed.

Data submitted for weekly MDOT quality assurance purposes shall be via either

external storage media (equipped with USB 3.0 interface) or a vendor-provided FTP

site from which MDOT would retrieve the data. Final submittals of non-imagery data

shall be via FTP upload. The Vendor shall inform MDOT via e-mail of each/all data

submittals with reference to the delivery platform used.

The Vendor shall possess and maintain, for a period of seven years after the

contract expiration date, backup copies of all collected/processed data at the same

quality level as that of the originally submitted data.

http://www.michigan.gov/dmb/0%2C1607%2C7-150-56355---%2C00.html


C. Summary of Michigan Routes to be Collected For the 2018-2021 collection contract period, there will be an estimated 33,920

miles of statewide data collection to be performed by the Vendor. Typically, data

shall be collected on both directions of divided routes (mainly freeways and

boulevards) and on a single, MDOT- specified direction of undivided routes. The

following table contains total collection mileage estimates for each of the four

contract years. (Refer to this Scope’s accompanying GIS shapefiles for further data-

collection location information):

Collection Mileage Estimates

Route Classification 2018 2019 2020 2021

State Trunkline - I & US Routes 1,620 5,080 1,620 5,080

State Trunkline - M (Mich.) Routes 5,510 610

5,510 610

State Trunkline – Bus. Loops/Spurs,Other 300 220 300 220

Local NHS 1,400 20 1,400 20

Local Non-NHS 400 1,800 400 1,800

Total 9,230 7,730 9,230 7,730

Collection mileage estimates per data type are outlined in ATTACHMENT D:

VENDOR PAY ITEM BID SHEET (2018-2021). MDOT will annually

provide the Vendor with a TapeLog file and supporting files defining the specific

route segments to be collected and the specific data types required for each

location.

Downview imaging, longitudinal profile measuring, and surface distress surveying

shall be continuous along the entire mileage for each specified route segment (no

sampling).

Surface distress surveying shall include identifying Principle Distress type and

length/width/type of Associated Distress (additional cracking, missing pavement,

etc.). The surface distress locations shall be recorded to the nearest 0.001 mile and

referenced to MDOT’s linear referencing system mileposts within each defined

pavement segment. Latitude/Longitude data corresponding to the nearest 0.001 mile

shall also be provided within the submitted distress survey data.

Transverse and longitudinal profile measurements are to be obtained and processed

by the Vendor using technology that meets Class 1 specification requirements

defined within ASTM E-950 (active version) in compliance with applicable

AASHTO standards (listed in ATTACHMENT B - APPLICABLE AASHTO

STANDARD SPECIFICATIONS). Raw profiles (.erd format for longitudinal as

requested per roadway segments) are to be delivered to MDOT in addition to


reduced 0.1-mile summary data reports. The Vendor shall supply software to

convert transverse profile measurements into average and maximum rut depth data

for each wheelpath, processed at any interval, but normally 10 feet, 50 feet, and

0.1-mile. The Vendor’s software shall also calculate from collected longitudinal

profile measurements the IRI (International Ride Index) in English units per the

current ASTM standard, and have functionality to vary the pavement length

reporting interval (but most frequently 0.1-mile).

2. DETAILED INFORMATION

A. COLLECTION

1. Description

A.1.1. The Vendor shall collect, process, and deliver pavement surface distress

survey data, images (pavement downview and right-of-way perspective

view), longitudinal profile (.erd format as requested per location by

MDOT, and IRI), transverse profile (Rut), transverse constructed-joint

fault, grade & curvature, GPS, and lane width. Data types and associated

annual mileage estimates are outlined in ATTACHMENT D: VENDOR

PAY ITEM BID SHEET (2018-2021).

A.1.2. The Vendor’s vehicle shall contain Geographic Information System (GIS)

navigation capability that allows pre-collection loading of both MDOT-

provided network segment location data defined in terms of Geographic

Positioning System (GPS) latitude/longitude pairs (extracted from MDOT’s

GIS environment) and MDOT provided shapefile of to-be-collected roadway

segment linework.

2. Collection, Deliverable Time Frames, and Associated Penalties

A.2.1. With the exception of Year 2018, each year’s roadway itinerary collection

shall not commence prior to April 15, and shall be completed within 1 1

weeks from that date in Years 2018 & 2020, and within 9 weeks from that

date in Years 2019 & 2021. Additionally for Year 2018, the HPMS-

inventory direction of all Michigan NHS routes shall be collected within

the first 5 weeks. In no case shall work commence prior to the contract

execution date. The Vendor shall incur a $1,000 penalty per each calendar

day beyond the above-defined timeframe that a given year’s collection is

actually completed as verified by MDOT. Granting of extensions for

collection completion due to delays reasonably beyond the Vendor’s control

(bad-weather days, as example, but not equipment failures) will be

considered by MDOT upon review of the Vendor’s explanation.


A.2.2. With the exception of 2018 collection, the Vendor shall annually collect

data by MDOT Region boundaries (fully completing one Region

before continuing to the next) in the Region order specified by

MDOT. All processed data shall be organized and submitted by full

MDOT Region boundaries per the delivery schedules defined in

ATTACHMENT C – 2018-2021 COLLECTION & DELIVERY

SCHEDULE. Annually processed full-Region surface distress survey data

submittals shall occur on a two-week interval starting no later than five weeks

after the collection start date, with the exception of the last submittal (Non-

Trunkline segments), which shall be due three weeks after the penultimate Region

submittal. The Region order of submittals shall match the order of e a c h

season’s collection as defined in ATTACHMENT C, with the exception of

the last full submittal (Non-Trunkline segments) that presumably would be

collected throughout the season intermixed with Trunkline segments.

2018 field collection and data-delivery order shall follow the special NHS-

prioritized schedule defined in ATTACHMENT C. Instead of full

MDOT-Region-by-Region order, collection will first focus on the HPMS-

inventory direction of all NHS routes across the state (by Region), and

then proceed to combinations of the remaining routes amongst the

Regions. 2018 data delivery, therefore, will require a mixed collection

and delivery of both state-jurisdiction and local-jurisdiction together to

address the NHS data priority.

As creation of distress survey data is contingent upon successful field

collection of raw data, granting of extensions to these defined data delivery

schedules due to delays reasonably beyond the Vendor’s control (bad-weather

collection days, as example, but not equipment failures) will be considered by

MDOT upon review of the Vendor’s explanation. The Vendor shall incur a

$1,000 penalty per each calendar day of delay for any related single per-

Region (or per-grouping for Year 2018) dataset submittal.

On an annual basis, finally processed/reported images, IRI, rut, fault, GPS,

grade/curvature, and lane width data for all annually required segments –

conforming to specifications and reporting formats defined in this document

- shall be submitted within three weeks after the required collection

completion date specified in this document. For Year 2018, there shall be

two separate submissions for such data – one three weeks after the required

completion date of HPMS-Inventory direction of all NHS routes, and another

three weeks after the required completion date for all other annually-specified

route segments. The Vendor shall incur a $1,000 penalty per each calendar

day of delay for any related single dataset submittal. (Imagery & associated

cross-reference table considered one single dataset submittal;

IRI/rut/fault/lane-width a second single submittal (considered as two separate

submittals for Year 2018); grade/curvature a third single submittal.)


Submittal due dates (as determined from time period requirements stated

herein) falling on weekends or MDOT holidays will be pushed back to the

next MDOT business work date.

On a weekly basis during collection, the Vendor shall provide MDOT

a weekly collection log file, vendor-hosted-website software access to

collected/location-referenced images (see Section B.1.1. for requirements),

GPS data, and tenth-mile processed IRI, rut, and fault data. This will

facilitate MDOT QA sampling review and commentary for acceptance of

the previous week’s collection (proper route, direction, location

referencing begin/end points, proper environment criteria, acceptable image

quality, and verification of reasonable IRI/rut/fault values).

All data submittals shall be performed in a consistent, logically organized

manner and shall be accompanied by a sufficiently descriptive cover

communication. The same shall be required for any resubmittals of data.

FTP site-facilitated data submittals shall be preceded by descriptive Vendor

e-mail notification to the MDOT Project Manager and his named staff.

3. Collection Protocols

A.3.1. The Vendor shall continuously record synchronized digital images of the

collection lane’s pavement surface (downview) and the forward perspective

view where specified. The image taking device(s) shall provide clear digital

images without sun glare under natural lighting conditions for the forward

perspective view. The downview shall be recorded in black-and-white; the

forward perspective view in color. The vehicle shall utilize artificial

illumination to sufficiently enhance downview images where natural

lighting is inadequate (under bridges, in areas shadowed by trees, buildings,

etc.).

A.3.2. The Vendor’s utilized downview imagery equipment shall ensure continuous

full-lane-width coverage: the collection lane’s width-limit demarcations

(both the left-side centerline and right-side edge line) shall be continuously

visible in the single downview image in order to ensure MDOT’s ability to

review the entire lane width (12 feet maximum). The aiming of the forward

view device shall be as directed by the MDOT Project Manager or his

representative.

A.3.3. All data within an MDOT-defined pavement segment shall be collected in one

continuous, unbroken pass and shall cover the entire length of the segment.

Otherwise, the Vendor shall discard all collected data for the subject segment

and recollect it to achieve continuity and completeness. Also, when at any

time during a segment’s collection, any data collection/measurement-

supporting device malfunctions, all data collected to that point for t he

segment shall be discarded and the Vendor shall start again from the


segment’s beginning point.

Maximum vehicle speed during collection shall be 65 mph. Areas where

collection speed is less than 15 mph shall be readily noted in the processed

data submitted to MDOT and removed from final-data calculations as

indicated elsewhere in this document.

A.3.4. Data shall be collected/processed on the right outside thru lane (truck lane).

Allowed exceptions on a case-by-case basis will be for required traffic

detours, traffic shifts in construction zones, instances where merging traffic

creates safety issues, and locations where right outside lanes are

dropped/added. Temporary auxiliary or weave/merge lanes between closely-

located interchanges, right-turn lanes, flares, and "Exit Only” lanes shall not

be considered thru lanes. For instances of traffic safety shifts or lane

drops/adds, a reasonable distance will be allowed by MDOT during QA

review for the Vendor’s vehicle to adjust to merging traffic or relocate back

into the thru traffic/truck lane. (Refer to ATTACHMENT A - REQUIRED

FIELD COLLECTION PROCEDURES - for more details regarding

collection requirements.) MDOT reserves the option of rejecting all data

linked to a given pavement segment’s collection (without payment)

and requiring recollection based on reasonable evidence during QA review

that the Vendor’s vehicle operator disregarded the requirements as stated here

and elsewhere in this document.

A.3.5. Data collection shall take place only when the pavement surface is dry and

free of water staining, fog is not present, the existing natural lighting is

adequate for good viewing of images (including minimal sun glare for

forward-view imagery), outside temperature is within collection equipment’s

recommended operating ranges, and no snow is present on the pavement and

shoulder surfaces. These conditions shall be met for the entire length of a

subject pavement segment’s collection. Otherwise, the Vendor shall discard

all collected data for the subject segment and recollect when all of the

required conditions exist. During MDOT QA review, reasonable allowance

will be provided for highly localized instances of water, fog, bad lighting, or

snow depending on location of such in relation to the MDOT-defined

segment’s boundaries.

A.3.6. Individually defined MDOT roadway segments shall be collected with the

sun behind the vehicle or high in the sky for a predominant percentage of

the segment’s total length. Every effort by the Vendor shall be made to

avoid windshield or roadway glare as collection is scheduled from day to

day. Collected imaging determined from MDOT QA review to have glare

that hampers viewing of roadway features and condition will result in re-

collection requirement.

A.3.7. All data files shall be identified with a naming convention that ties the


related data together for each pavement segment.

A.3.8. The Vendor shall replace, at its expense and within one week of discovery or

notice by MDOT, any data storage devices which are damaged or lost during

or upon delivery to MDOT.

A.3.9. The perspective and downview images shall be continuously monitored by

the Vendor’s operators in real time during collection to ensure proper

camera angles, image clarity, and coverage completeness.

A.3.10. Each Vendor longitudinal profiler shall comply with the Michigan Test

Method for Certification of Profilers (MTM 730).

(http://www.michigan.gov/documents/mdot_MTM_CombinedManual_835

01_7.pdf) prior to the start of each year's data collection, and after certain

Vehicle-change instances during collection whereupon profile measurement

equipment performance could be affected. The certification process will be

administered in the Lansing area by MDOT staff and takes up to half a day to

conduct for each collection vehicle.

Additionally during collection, each Vendor vehicle shall a) on a weekly basis,

run through one of the various MDOT-established statewide IRI certification

sites and electronically submit results to MDOT, and b) visit the MDOT

Lansing Office every three weeks to perform verification tests on the vehicle’s

distance measuring instrument, accelerometers, laser sensors (measured-mile,

bounce test, ride and/or rut measure verification, etc.), and cameras under

MDOT staff supervision and monitoring.

A.3.11. An annual kick-off meeting shall be scheduled by the Vendor to discuss

and clarify with MDOT requirements of each season’s collection before

commencement. The meeting can take place in Lansing or via web/phone

communication.

A.3.12. MDOT reserves the right to periodically send an MDOT employee in the

Vendor’s vehicle during production collection for Quality Assurance checks.

The Vendor shall maintain, document, and follow a plan to thoroughly train

and certify its collection vehicle operation personnel in, at a minimum,

familiarization & operation of on-board hardware/software, operation of

rapid-travel inertial profiling systems, and conformance to MDOT collection-

requirement protocols defined in this document. The plan shall be provided

to MDOT upon contract execution.

http://www.michigan.gov/documents/mdot_MTM_CombinedManual_83501_7.pdf

http://www.michigan.gov/documents/mdot_MTM_CombinedManual_83501_7.pdf


4. FrameID/Location Reference Identification and Weekly Reporting

A.4.1. The vendor shall accommodate, utilize, and provide a Set/FrameID raw-data

referencing system to link all collected data together during collection in order

to facilitate MDOT’s subsequent management of the data. A “Set” is used by

MDOT to group together consecutively collected data within an additional

reference system (separate from linear mileage measurement) for organization

and management purposes. Each Set shall have a SetID number (3 or 4 digits)

unique to each collection year and each collection vehicle. Additionally, each

single Set shall be limited in assignment to data collected on the same day. A

Set can be assigned to multiple MDOT pavement segments (LocIDs, as

defined in the TapeLog file). A FrameID shall be a non-negative numeric

value unique within a single Set. (Acceptable FrameID values range from 0

to 999999999, inclusive.) FrameID values are expected to increase with the

orderly progression through an MDOT pavement segment’s collected dataset

as the offset distance of collection (from the segment’s start location)

increases. A structured relationship shall be created by the Vendor between a

Set’s increasing FrameID values, increasing offset distance (inches) from the

Set’s beginning location, and the MDOT-defined milepoints (to nearest 0.001-

mile) for any single MDOT pavement segment assigned to the Set. Refer to

ATTACHMENT F – FILE FORMATS OF LOCATION REFERENCING,

DISTRESS, AND SENSOR DATA for further details.

A.4.2. Collected data shall be linked to the MDOT-defined starting mileage point

for a given pavement segment’s beginning location, yet the Vendor’s length

measurement from that beginning point shall be used to define the ending

mileage point of the pavement segment.

NOTE: This assumes that the Vendor’s collection system has accurately

marked the start/end limits at the proper physical location points defined

by MDOT for each pavement segment, and that the Vendor’s collection

progress along the route segment is appropriate. Weekly MDOT QA will

review such. (See ATTACHMENT A - REQUIRED FIELD COLLECTION

PROCEDURES.)

Example:

A pavement segment is defined as starting at milepoint 0.000 and ending at

milepoint 10.000 as provided by MDOT. Yet, the Vendor measures

10.100 miles between the proper start/end reference points during collection.

Subsequent collection review by MDOT finds sufficient accuracy in the

Vendor’s marking of the segment collection’s start/end points. The

submitted data shall, therefore, be labeled from milepoint 0.000 to 10.100.

Example:

A pavement segment is MDOT-defined from milepoint 10.000 to milepoint

0.000. The Vendor’s collection measures 10.100 miles between the proper


start/end reference points and MDOT QA review finds sufficiently accurate

start/end definition during the collection. Therefore, the submitted data shall

be labeled from milepoint 10.000 to milepoint -0.100.

A.4.3. As collection progresses, the Vendor shall maintain a collection log

file linking collected data Set/FrameID information to each MDOT-

defined pavement segment and to MDOT’s linear referencing (mileage)

system. The Vendor shall provide ready association of any particular data

type to other simultaneously collected data types through use of the

Vendor’s Set/FrameID referencing, MDOT’s linear referencing system, and

GPS referencing. The Vendor shall supply to MDOT on a weekly basis a

collection log file unique to each week’s collected segments. (Set 999 shall

be exclusively used to designate within the weekly submitted collection log

file any record segment for which the vendor could not perform any

collection due to route closures, construction detours, etc.) (Refer to

ATTACHMENT F – FILE FORMATS OF LOCATION

REFERENCING, DISTRESS, AND SENSOR DATA.)

A.4.4. The Vendor shall submit to the MDOT Project Manager on a weekly basis a

cumulative collection progress report describing, at a minimum, mileage

percentages collected per MDOT Region for the latest week and overall,

dates, Sets collected, and weather-delay claim information (including

vehicle, date, example LocID(s), and an accompanying captured image of

the weather environment situation on a road surface per each day, per each

vehicle).

B. DATA REQUIREMENTS

1. Roadway & Pavement Imagery

B.1.1. Description:

The Vendor shall collect and provide digital images of the pavement down

view and forward perspective view. Images shall be in .jpeg format and

shall contain within the EXIF data GPS latitude/longitude (conforming to

this documents specified datum, correctional, and precision standards),

collection date, and route name (contained in the annual MDOT-provided

TapeLog file). The images shall have a minimum resolution of 1440 x

1080.

The Vendor shall provide a managed hosting service via the Internet to

facilitate MDOT employee QA checks of Vendor collection and data, where


a user can view the images by selecting the desired network segment via

MDOT region, county, route, Set/FrameID referencing, MDOT linear

referencing ID & milepoints, and via a GIS map displaying the same.

Storage and management of the imagery for the host site shall be the

Vendor’s responsibility. In addition, the Vendor shall provide MDOT with

“full rights” to the submitted final image data files for unlimited use and

reproduction. A database table cross-referencing .jpeg image file names to

GPS referencing and MDOT linear mileage referencing system data shall be

provided to MDOT at the end of each annual collection season at the same

time as the final imaging submittal.

The Vendor’s hosted Internet service software shall provide simulated

“driving” of the selected network roadway segment by consecutive in-motion

displaying of the sequentially collected images at user-defined “speed”. The

user shall be able to examine a single image and print it. The images shall be

indexed per MDOT linear referencing and easily retrievable.

The software shall display the digital images of the forward perspective view

(color) and vertical downview (black-and- white) of all designated collection

mileage. Forward perspective-view images shall be displayed at 20-foot

intervals. Individual downview images shall continuously cover the traveled

pavement with each image displaying 20 feet of pavement length. (However,

finally submitted .jpeg images – to be purchased by MDOT - shall be provided

at 40-foot intervals for forward perspective views and continuously for

pavement down views.) The software interface shall display MDOT linear

referencing and geo-referencing (GPS) information simultaneously with the

imaging. Individual image files shall be readily extractable (independent from

the Vendor-provided software). Finally submitted images shall contain an

informational header superimposed within the image itself in the following

manner and including the described contents:


Prior to collection commencement, the Vendor shall discuss and confirm/

finalize with the MDOT Project Manager the configuration of metadata

attributes to be provided within the .jpeg image header (above), within each

.jpeg’s EXIF data, and on-screen within the web-interface software.

The Vendor shall provide on the hosted service weekly updated access to

collected/location-referenced imagery for the MDOT Project Manager and

his staff during collection to facilitate MDOT weekly QA reviews of

collection adequacy.

Images finally provided to MDOT at each annual season’s end shall be

delivered via portable, reliable, durable media maximizing storage and

transfer efficiency in relation to current industry standards. The imagery files

delivered on the external media shall be organized in a folder structure

according to the following hierarchy:

MDOT Region# \ ImageType (ROW or Pavement) \ LocID

The associated cross-referencing table delivered by the Vendor shall be

organized in the following manner:


Any managed hosting service, software, or hardware shall conform to State of

Michigan Department of Technology, Management, and Budget IT network

standards and requirements. The Vendor shall be responsible for all software,

hardware, and shipping necessary to support image access and delivery for

MDOT.

B.1.2. Collection & Imaging QA:

From MDOT’s weekly QA review of the Vendor’s previous-week

collected imaging and GPS data, collection location- and image-check

status will be reported to the Vendor within one week after data receipt.

Pavement segments found to have collection location, environment, or

image quality errors will be reported to the Vendor as needing re-collection.

Segment collections found to have correctable issues will be reported to the

Vendor as needing adjustment prior to final data submittals.

Collection location issues to be checked will include, but not be limited to,

proper route segment, accuracy of segment start/end locations, collection

lane, and need for data elimination (due to construction zones, etc.).

Collection environment review issues will include presence of fog, snow, or

wet pavement. Image-quality review issues will include, but not be limited

to, coverage completeness along the route segment, view angle, down view

coverage width, brightness (lighting adequacy, presence of glare, or

shadowing excess), contrast, clarity, and color.

B.1.3. Final Submittal and Acceptance:

The Vendor shall submit to MDOT finally-processed forward perspective and

pavement down view images (with accompanying cross-reference table previously

described in Section B.1.1.) for the entire statewide annual collection within three

weeks after the date of each year’s collection completion. The data shall

pass through an MDOT sequential system of final verification and quality

assurance checks for proper storage formatting, location referencing, coverage

completeness, adjustments per MDOT’s supplied Outstanding Collection

Issues reports, and displayed header content/accuracy. An initial dataset

found upon submittal to have not substantially met this document’s

formatting or coverage-comprehensiveness requirements will be considered

by MDOT to not have satisfied the associated delivery timeframe

requirement.

Results of MDOT’s final QA review & testing will be provided to the Vendor

within six weeks after receipt of the Vendor’s data submission. The Vendor


shall resubmit corrected data (as required) within one week after MDOT has

communicated its initial QA status results or its subsequent QA status results

after further resubmittals. The Vendor shall incur a $1,000 penalty per each

calendar day of delay for each of the dataset’s initial and subsequent

submittals. The entire annual statewide dataset shall receive written approval

for payment from the MDOT Project Manager based on status of MDOT QA

findings.

2. Distress Type/Severity/Extent Identification

B.2.1. Processing:

Pavement surface distress surveying (type/severity/extent identification) shall

be conducted in accordance with ATTACHMENT G – DISTRESS

MANUAL FOR SURVEYING OF PAVEMENT SURFACES. The

delivered data files shall conform to format and logic requirements described

in both ATTACHMENT G and ATTACHMENT F – FILE FORMATS OF

LOCATION REFERENCING, DISTRESS, AND SENSOR DATA.

B.2.2. Survey Technique:

The Vendor shall use distress pattern recognition technology adequate to

identify and record distress type, severity, and extent characteristics in

conformance with the methodology outlined in ATTACHMENT G.

Each pavement segment’s distress survey file created by the Vendor shall

account for the entire associated mileage range (as measured by the Vendor)

between the MDOT defined start and end locations. Weekly collection

location review b y M D O T will p e r i o d i c a l l y require the Vendor

to insert a “Not Surveyed” ( P D 0 9 0 8 ) coding record for locations

where construction or detouring has hindered data collection on the desired

pavement segment or survey lane.

B.2.3 Survey Technique Flexibility:

MDOT might require modifications to its defined surface distress data

formatting or type/severity/extent identification methodology during the

period of the contract in order to stay current with MDOT business needs.

The Vendor’s survey process shall possess reasonable flexibility in order to

adapt to such potential modification requirements.

B.2.4 Quality Control Plan:

The Vendor shall maintain and follow a documented quality control plan that

addresses the accuracy, consistency and completeness of the created distress

survey data, and includes description of the process utilized to train staff that

are directly involved with distress survey data generation. The plan shall be


provided to MDOT upon contract execution.

B.2.5. Delivery:

Every pavement segment distress survey data file shall be processed and

delivered to MDOT in the format specified within ATTACHMENT F.

Delivery timeframe and method requirements have been defined previously

in Section A.2.2.

B.2.6. MDOT Quality Assurance and Acceptance:

The distress survey data shall pass through an MDOT sequential process of

quality assurance checks for proper f i l e format, coding logic, and survey

call accuracy. MDOT will verify Vendor survey call accuracy via

comparison of submitted file content to the collected pavement images. For

such, MDOT will utilize the Vendor’s hosted-site-provided access for

simultaneous viewing of forward perspective and pavement downview

images via MDOT’s location mileage reference system and the Vendor’s

created Set/FrameID referencing system.

Additionally, MDOT will perform various global-level checks (such as total-

quantity and severity-level trend analyses) upon the Vendor’s submitted-per-

Region distress survey data sets. The Vendor shall respond, in a timely

manner and with adequate explanation, to any subsequent observational

questions from MDOT.

The MDOT Project Manager must provide written approval prior to

payment for received and accepted data. Payment will be made as a

percentage of the unit price as follows:

Phase 1: 50% of the unit price per mile for distress survey data will be paid

for each LocID passing initial logic check (further described below).


for each LocID passing survey call quality level check (further described

below).


for each LocID within a Region when all LocIDs within the Region have

passed both initial logic check and survey call quality level check.

Phase 1: MDOT will supply the Vendor with FTP-site access to MDOT-

developed distress survey data file logic checking software. This will provide

the Vendor the opportunity to preliminarily check data format and logic

prior to final submittal. MDOT will then, upon receipt of finalized data

via the FTP site, process the data with the same software to determine format

and logic acceptability. Data submittal timing compliance will be based on

the expectation that each individual LocID distress survey file is properly


submitted as “final data” within the MDOT FTP structure and successfully

passes the logic-check routine by the submittal due date.

Phase 2: MDOT will sample (by mileage) the Vendor’s surface distress

survey calls and test them as described in ATTACHMENT H - DISTRESS

SURVEY CALL SAMPLING, TESTING, & ACCEPTANCE CRITERIA.

Individual files shall meet quality levels defined therein for acceptance and

payment. Files that fail to meet those MDOT quality assurance accuracy

requirements will be rejected. Results of MDOT distress data QA will be

communicated back to the Vendor per each full Region. Once MDOT has

completed its initial QA reporting (or its subsequent QA reporting after

further resubmittals) of a given Region’s distress survey dataset status, the

Vendor shall have one week to complete corrections and resubmit all

distress data reported by MDOT as failing. The Vendor shall incur a $1,000

penalty per each calendar day of delay for any single dataset initial submittal

or resubmittal.

B.2.7. Software:

The Vendor’s software used for recognition and recording of pavement

distress survey data (with MDOT’s linear location and Set/FrameID

referencing system) shall be provided to MDOT for use in its QA review.

3. Transverse and Longitudinal Profiles

B.3.1. Description:

The longitudinal profile points for IRI and fault shall be captured/stored at

a longitudinal distance interval not to exceed 1.5 inches in both the right and

left wheel paths of the lane for which the data are being collected. Rut

measurement calculations shall be performed for each wheel path of the

lane for which the data are being collected – from transverse profiles

collected/stored at a maximum longitudinal distance interval of one foot.

Fault detection measurements across transverse joints shall be performed in

both the left and right wheelpaths. Rut data collection will be required only

on flexible (full-depth asphalt) and composite (asphalt over concrete)

pavement surfaces; fault data collection will be required only on jointed rigid

pavement surfaces. Vendor fault reporting shall be comprised only of detected

faults at constructed transverse joints; measurement of faults across random

transverse cracks or other surface distresses shall not be included in the finally

reported fault data values. MDOT will specify pavement type locations for

the Vendor – see ATTACHMENT F for example file format that will be

provided annually.


B.3.2. Equipment, Measurement, Operation, and Computation:

The measuring vehicle shall be capable of collecting longitudinal profile data

at posted highway speeds (65 mph maximum) via an inertial profiling

system using line-laser measurement technology that meets Class 1

specification requirements defined within ASTM E-950 (active version).

The vehicle shall be equipped with all necessary transducers, computing and

recording equipment to measure and record elevation data from the pavement

surface as specified within ASTM E950 (active version) and as defined

herein. Equipment, methodology, and operators shall comply with the

noted applicable AASHTO specifications listed in ATTACHMENT B of this

document.

Wheelpath rut depth determination shall be accomplished through

measurement of the transverse profile with technology that provides more

than 1000 data points across the entire collection lane width – collected/stored

at a maximum distance interval of one foot along the road (which is a shorter

spacing requirement than the referenced AASHTO specification below). The

methodology shall utilize algorithms to remove surface texture effects,

compensate for vehicle lateral wander, and resolve a string-line rut value for

each wheelpath. The methodology shall comply with applicable

AASHTO specifications listed in ATTACHMENT B unless otherwise

specified herein.

Profile measurement processing and computation for determination of the

International Roughness Index (IRI) shall comply with applicable

AASHTO specifications listed in ATTACHMENT B.

The record file for the longitudinal profile data (including processed 0.1-

mile data files) shall be embedded with coding to distinguish the location of

occurrences that interrupt the continuity of the profile within a segment.

The following occurrences shall be identified with reference coding within

the submitted data file (including 0.1-mile aggregated file) that includes

both their starting and ending MDOT location referencing mileage points.

a. bridge/culvert decks

b. railroad crossing

c. construction zone (travel required outside the designated

collection lane - e.g.: detour or traffic shift)

d. where collection occurs outside the right thru lane.

e. low travel speeds (vehicle speed is below 15 mph)

-Segment collection locations associated with occurrences “c” and

“e” above shall be excluded from reported IRI calculations.

-Segment collection locations associated with occurrences “a”, “b”, and

“c” shall be excluded from calculations for wheel path rut.

-Segment collection locations associated with occurrences “a”, “b”, “c”,


and “e” shall be excluded from calculations for fault.

B.3.3. Software and Documentation:

All software to process the collected profiles into International

Roughness Index (IRI), rut, and fault measurements as specified shall

be provided by the Vendor. Submitted final data for IRI, rut, fault, grade,

and lane-width measurements shall include processed 1/10-mile summary

formatting, but Vendor software shall provide capability for processing

summary data at any longitudinal interval length (0.1-mile, 0.5-mile, etc.).

Within each 0.1-mile report file, in addition to fields for MDOT location

reference begin/end mile points and the subject measurement values, indices

and/or statistics, there shall be separate fields displaying the route name, date

of collection, pavement surface temperature, begin/end GPS (lat./long.), and

instances “a” through “e” noted in Section B.3.2. Individual data

measurement or statistic record cells (location referencing cells excluded) for

mileage ranges that MDOT, from weekly QA review, has directed the Vendor

to mark as “Not Surveyed” (due to construction, detour, non-applicable

pavement type, etc.) shall be left blank.

The Vendor shall provide documentation of the rutting measurement

method used, including the algorithms and settings. Rut depth average and

maximum values for each wheel path shall be processed by the Vendor and

reported for every 0.1-mile. Methodology shall comply with applicable


The Vendor shall provide documentation of the transverse-joint fault

detection/measurement method used, including algorithms and settings.

Total number of faulted transverse joints detected (above 0.04 inch),

maximum absolute fault height (to nearest 0.04-inch), and average absolute

fault height (to nearest 0.04 inch) for each wheelpath shall be processed and

reported for every 0.1-mile. Methodology shall comply with applicable


B.3.4. Quality Control/Calibration:

The Vendor shall maintain and follow a documented plan for controlling

accuracy quality of the measured profile data, including daily field procedures

for checking and calibrating its collection sensor, transducer, and recording

equipment in compliance with equipment manufacturers’ and system

architects’ recommendations. The plan shall include an estimate of the

precision of the measurement process, and description of a real-time, onboard

verification practice to assure that valid data are being recorded. The plan

shall be submitted to MDOT upon contract execution.


MDOT will execute weekly verification checks of Vendor-collected


location, distance, ride, rut, imagery, and fault data using Vendor

equipment manufacturer specifications, MDOT hand- or equipment-

collected data, required Vendor test-runs, and/or historically collected

data. The Vendor collection vehicle(s) shall begin each annual season in

Lansing with MDOT staff to perform various QA verification tests on each

vehicle’s distance measuring instrument, accelerometers, laser sensors

(measured-mile, bounce test, ride and/or rut measure verification, etc.), and

cameras. Subsequently, each vehicle shall return to Lansing every three

weeks to repeat the same procedures. Additionally, at the beginning of each

non-Lansing-visit week, each Vendor collection vehicle shall perform three

separate longitudinal profile measurements on one of the various MDOT-

established statewide IRI certification sites (described at

http://www.michigan.gov/mdot/0,1607,7-151-9625_57294---,00.html). In an

expedient manner thereafter, results of the runs shall be labeled with the

MDOT site name and electronically provided to MDOT including sample

forward perspective images, GPS, and .erd files from the three runs per each

collection vehicle. The Vendor shall include profile lead-in and lead-out

information relative to the specified test site’s beginning/end for each of the

three run’s provided .erd data.

The Vendor’s vehicle operators shall have the ability while in Lansing to

readily provide MDOT with collected longitudinal/transverse profile raw data

and processed pavement-metric values (IRI, rut, fault) data for QA purposes.

As stated previously (Section A.2.2.), the Vendor shall submit final-formatted

profile data to MDOT within three weeks after the date of each year’s

collection completion. The final data shall pass through an MDOT

sequential system of verification and quality assurance checks for proper

formatting, coverage completeness, and reasonably expected value ranges.

An initial dataset found upon submittal to have not substantially met this

document’s formatting or coverage-comprehensiveness requirements will be

considered by MDOT to not have satisfied the associated delivery timeframe

requirement. Results of MDOT’s quality assurance review & testing will be

provided to the Vendor within six weeks after receipt of the Vendor’s data

submission. The Vendor shall resubmit corrected data (as required) within

one week after MDOT has communicated its initial QA status results or

its subsequent QA status results after further resubmittals. The Vendor shall

incur a $1,000 penalty per each calendar day of delay for each of the profile

dataset’s initial and subsequent submittals. The entire annual statewide

profile dataset shall receive written approval for payment from the MDOT

Project Manager based on status of MDOT QA findings.

http://www.michigan.gov/mdot/0,1607,7-151-9625_57294---,00.html


4. Grade and Curvature ***

*** MDOT reserves the right to remove this data item’s collection/delivery/payment from any single year’s scheduling.

B.4.1. Description:

The Vendor shall measure, calculate, and report survey lane

longitudinal grade and horizontal alignment curvature.

B.4.2. Equipment and Measurement:

The Vendor’s vehicle shall be equipped with all necessary receiver, transducer,

and computer equipment to measure and record grade and curvature data.

State-of-the-practice gyroscope and/or differential GPS inertial navigation

equipment and methodologies shall be utilized. The vehicle

shall be capably equipped to collect the data at posted highway speeds (65

mph maximum).

B.4.3. Quality Control and Documentation:

The Vendor shall provide documentation of the g r ad e / cu r v a t u r e

measurement and analysis methods used, including the algorithms, settings

specific to the MDOT service, and statements of precision and accuracy levels

of the finally reported data. Additionally, the Vendor shall maintain and follow

a quality control plan that addresses, as a minimum, the accuracy of the

measured and reported data and lists sufficient calibration procedures for the

equipment and algorithms. Both documents shall be submitted to MDOT upon

contract execution.

B.4.4. MDOT Quality Assurance:

MDOT reserves the right to use MDOT equipment and resources for

verification of the Vendor’s data quality. MDOT reserves the right to require

the Vendor’s collection vehicle(s) to collect specific roadway sections

statewide on a weekly basis and in Lansing every third week for such

verification. Equipment manufacturer specifications, MDOT-collected

measurements, State of Michigan Geographic Framework data, and/or as- built

design details will be utilized for quality assurance checks of the Vendor data.

B.4.5. Reporting Format:

Generated longitudinal grade measurement reports shall utilize a reporting

interval specified by MDOT. While an interval of 0.1-mile is typical, the

vendor shall have the ability to vary the reporting interval to meet MDOT

special-report needs. Each reporting interval record shall include Grade

(percent – average for reporting interval) and other metadata including MDOT

linear referencing and GPS (lat./long.) data – See ATTACHMENT F for

further details.

The generated horizontal curvature measurement report shall describe a


continuous progression of mileage with each separately detected alignment

feature type occupying a single report record. Each horizontal alignment

report record shall include feature type (either angle point, independent horz.

curve, component of compound curve, component of reverse curve, or tangent

section), start of feature, end of feature, radius, degree of curvature, maximum

superelevation, length of curve, spiral transition presence, deflection angle,

and direction of curve or deflection angle. The report shall also contain other

metadata including MDOT linear referencing and GPS (lat./long.) data - See

ATTACHMENT F for further format details.


The Vendor shall submit to MDOT processed measurement data for the entire

state in the specified report formats within three weeks after the date of each

year’s collection completion. An initial dataset found upon submittal to have

not substantially met this document’s formatting or coverage-

comprehensiveness requirements will be considered by MDOT to not have

satisfied the associated delivery timeframe requirement. The data shall pass

through an MDOT sequential system of final verification and quality

assurance checks for proper formatting, coverage completeness, and

reasonably expected value ranges.

Results of MDOT’s final QA review will be provided to the Vendor within six

weeks after receipt of the Vendor’s data submission. The Vendor shall

resubmit corrected data (as required) within one week after MDOT has

communicated its initial or subsequent QA status results. The Vendor shall

incur a $1,000 penalty per each calendar day of delay for each of the


dataset shall receive written approval for payment from the MDOT Project

Manager based on status of MDOT QA findings.

5. Global Positioning System (GPS) Data

B.5.1. Description and Standards:

The Vendor shall collect and provide Inertial Differential GPS latitude

and longitude values along all MDOT-defined pavement segments. The

reported data shall adhere to the following standards:

Horizontal Datum: North American Datum of 1983 (NAD83)

Vertical Data: North American Vertical Datum of 1988 (NAVD88)

Ellipsoid: GRS 1980

B.5.2. Corrections:

The Vendor shall real-time correct the GPS data via Real-Time Kinematic

(RTK) technique through utilization of the MDOT CORS (Continuously

Operating Reference Stations), or post-process correct the data using a


minimum of 4 sites from the MDOT CORS sites (https://mdotcors.org) or

other Published NGS foundation CORS sites

(https://www.ngs.noaa.gov/CORS). (Use of temporary sites or local bases

is not allowed.) Therefore, the Vendor shall utilize, at a minimum, a dual

frequency (L1 & L2), NTRIP-capable GPS receiver. When using RTK

method with the MDOT CORS, the vendor shall use the Network Solution

option for all operations (Mountpoint NETWORK_SOLUTION_RTCM3-

GG, available on port 10000). The Vendor shall establish its own account

and notify the MDOT CORS administrator at [email protected] if

special considerations are required for NTRIP access. If none are

requested, MDOT will assume that the Vendor’s equipment needs no

special consideration.

B.5.3. Accuracy:

The vendor shall provide latitude/longitude accuracy as expected from

utilization of corrections via RTK with the MDOT CORS. The Vendor’s

corrected data shall be visible as its own map layer within the Vendor’s

hosted website software for MDOT QA review of routes collected,

captured imagery, etc. (See Section B.1.1.) The Vendor shall maintain

correction accuracy documentation and shall supply if MDOT requests

such for QA purposes.

B.5.4. Quality Control Plan:

The Vendor shall have a documented plan addressing the management of

collection frequency, comprehensiveness, correction, accuracy, and precision

specifications for the finally reported data. The plan shall be provided to

MDOT upon contract execution.

B.5.5. Deliverables:

The corrected GPS lat./long. data shall be readily linkable and reported along

with all other Vendor-delivered image and roadway alignment/condition

measurement data. Delivered data shall be in standard geographic data format

and compatible with MDOT’s geographic mapping programs (Esri-based).

Additionally, the corrected data shall be included within all processed 1/10-mile

and other-formatted data files required for submittal to MDOT. (See

ATTACHMENT F for GPS data-reporting format and precision

requirements.)


The Vendor shall provide previous-collection-week corrected GPS lat./long.

data to MDOT on a weekly basis during collection. MDOT will review the

data for location coverage frequency, completeness, and accuracy. Resultant

issues found with the data will be reported to the Vendor within one week of

data receipt.

After post-collection receipt of finally reported IRI, rut, fault, grade/curvature,

https://mdotcors.org/

https://www.ngs.noaa.gov/CORS

mailto:[email protected]


and lane-width data, any further MDOT verification-check issues found with

the GPS data will be reported to the Vendor within six weeks after data receipt.

The Vendor shall correct the dataset (as required) and resubmit to MDOT

within one week after communication of MDOT’s verification results. The

Vendor shall incur a $1,000 penalty per each calendar day of delay for each

of the dataset’s initial and subsequent submittals (to be treated as a

subcomponent to the individual requirements for each of the

transverse/longitudinal profile, pavement imagery, and Grade/Curvature

datasets, respectively). The entire annually collected statewide GPS dataset

shall receive written approval for payment from the MDOT Project Manager

based on status of MDOT QA findings.

6. Lane Width

B.6.1. Description:

The Vendor shall measure and report survey lane width to the nearest

whole foot. Lane width shall be defined as the shortest lateral distance

between the lane’s left and right pavement-marking delineations.

B.6.2. Quality Control and Documentation:

The Vendor shall provide documentation of the l an e - w i d t h

measurement method used and the accuracy level of the finally reported data.

Additionally, the Vendor shall maintain and follow a quality control plan that

addresses, as a minimum, the accuracy of the measured and reported data and

lists sufficient control and/or calibration procedures for the process and

equipment. All such documentation shall be submitted to MDOT upon contract

execution.

B.6.3. MDOT Quality Assurance:

MDOT reserves the right to use MDOT equipment and resources for

verification and acceptance of the Vendor’s data quality. Equipment

manufacturer specifications, MDOT-collected measurements, State of Michigan

Geographic Framework data, and/or as- built design details will be utilized for

quality assurance checks of the Vendor data.

B.6.4. Reporting:

Generated lane-width measurement reports shall provide the predominant lane-

width value over a reporting interval specified by MDOT. While an interval of

0.1-mile is typical, the vendor shall have the ability to vary the reporting

interval to meet MDOT special-report needs.


The Vendor shall submit to MDOT lane-width measurement data for the

pavement segments specified for such within the annual MDOT-provided

TapeLog file. The data shall be in the specified report format and submitted


within three weeks after the date of each year’s collection completion. An

initial dataset found upon submittal to have not substantially met this

document’s formatting or coverage-comprehensiveness requirements will be

considered by MDOT to not have satisfied the associated delivery timeframe

requirement. The data shall pass through an MDOT sequential system of

final verification and quality assurance checks for proper formatting,

coverage completeness, and reasonably expected value ranges.

Results of MDOT’s final QA review will be provided to the Vendor within six

weeks after receipt of the Vendor’s data submission. The Vendor shall

resubmit corrected data (as required) within one week after MDOT has

communicated its initial or subsequent QA status results. The Vendor shall

incur a $1,000 penalty per each calendar day of delay for each of the


dataset shall receive written approval for payment from the MDOT Project

Manager based on status of MDOT QA findings.


ATTACHMENT A


2018 – 2021

REQUIRED FIELD COLLECTION PROCEDURES

1. Segment Start and End Locations:

The beginning and ending locations of a MDOT-defined pavement segment shall be properly

demarcated as data are collected in the field through utilization of MDOT-provided

GPS latitude/longitude pairs and accompanying roadway location descriptions. Typical

MDOT pavement segment beginning and ending point descriptions include references to

cross road intersections, county line signs, junctions with other routes, or gore points of

ramps.

While the begin and end location descriptions provided by MDOT are for Vendor general

guidance, the Vendor shall use the MDOT-provided GPS lat/long data to locate the exact

begin or end point of a segment’s collection. (Instances of significant disagreement between

MDOT-provided begin/end descriptions & lat/long data shall be discussed with MDOT.)

Lat/long information for the beginning and end of to-be-collected route segments will be

contained within MDOT’s annually provided TapeLog file. Additionally, MDOT will

provide an accompanying GIS shapefile containing the linework of those specific route

segments expected for collection. During any specific year’s collection process, if the

Vendor observes apparent errors in the MDOT-provided linework, they shall, in a timely

manner, notify MDOT of the specific segment and details of the observed error.

If the vehicle is to turn directly around to pick up the opposite direction of a roadway

segment direction just completed, the start of that opposite direction’s collection shall not be

marked by the operator until the vehicle is actually turned around and is at the MDOT-

defined start location for that direction’s collection.

If one defined pavement segment ends and another begins at the same intersection/point, yet

a turn must be made in order to follow the next segment, then the vehicle shall first pass

straight through and demarcate the end of the first segment data as close as possible to the

MDOT provided GPS point. Then, the vehicle shall be positioned on the intersection leg

opposite of the next segment and the start of its collection shall be demarcated at the same

point. Segment start and end points that are simply demarcated as the vehicle turns the

corner will be considered by MDOT for rejection and re-collection requirement.

MDOT’s acceptance tolerance for each collection begin/end point demarcation will be +/-

35 feet (straight-line measured from MDOT’s provided GPS point to the Vendor’s


provided field-collected GPS point). MDOT reserves the options of either rejecting

collection (or data) that show reasonable evidence that the tolerance is not being met, or

specifying data adjustment by the Vendor for correction. MDOT will execute this tolerance

checking procedure during its weekly QA reviews of both the Vendor’s collected GPS and

forward-perspective/pavement image data.

2. Incorrect or Incomplete Collection:

When the Vendor field operators have collected a pavement segment’s data incorrectly

location-wise (improper route, direction, beginning point, or ending point, etc.), or with some

malfunctioning piece of equipment, or within unacceptable circumstances (wet weather,

excessive speeds, etc.), steps shall be immediately taken to purge the affected data and re-

collect with proper locationing, properly operating equipment and/or proper circumstances.

This shall be done in order to obtain MDOT’s desired continuous, unbroken, complete and

accurate dataset for the pavement segment. The Vendor operators’ strict compliance to

these required collection details will be most advantageous by minimizing both the need

for post-edit tracking and the additional chance of associated human error introduction.

3. Collection Lane, Passing & Merging:

Collection shall be performed in the far right thru lane (truck lane) where the most severe

pavement distress predominantly exists. Temporary auxiliary or weave/merge lanes between

closely-located interchanges, right-turn lanes, flares, and "Exit Only” lanes shall not be

considered thru lanes. Passing shall be done only for necessary traffic safety purposes.

When there are vehicles merging from a ramp, the Vendor vehicle should move to the inside

(left) lane as safety necessitates, and either speed up or slow down in order to safely return to

the far right lane as soon as safely possible. The Vendor operator shall maintain a minimum

distance between the collection van and any preceding vehicle. Also, the Vendor operator

shall minimize travel time spent alongside large trucks that may be passing on the van’s left.

These actions are required during collection to provide sufficient forward perspective view

imaging of the roadway and pavement surface ahead to facilitate:

a) Proper distress characterization during MDOT’s subsequent QA checking

of the Vendor’s submitted pavement distress survey data

b) Various imagery-viewing needs of MDOT customers

NOTE: Post-collection distress surveying shall properly identify which lane is being

surveyed. (Lane #1 is far right thru lane, with lane numbering increasing as collection

moves to the left across the roadway. Far-right auxiliary or weave/merge lanes between

closely spaced exits and entrances to a roadway facility, right-turn lanes, flares, and "Exit

Only” lanes are not be considered thru lanes by the Vendor for collection purposes.) The

following images provide example scenarios


4. Measurement Verification Testing:

In addition to MDOT expectations for the Vendor’s own execution of daily and weekly

quality control validation procedures on its collection vehicle equipment operation, the

Vendor operators shall run verification tests for collection equipment measurement weekly at

one of various statewide locations, and in Lansing every third week as directed by MDOT. These

tests shall include, but not be limited to, distance, longitudinal profile, and camera alignment

measurements.

5. Construction and Detour Areas - Data Collection and Processing Requirements:

When the collection vehicle traverses an ongoing construction project (or detour), or a

location where it is evident that collection on the proper roadway and/or in the proper lane

is impossible (traffic shifts), final data shall be edited per MDOT guidance feedback by:

insertion of PD Code 0908 (Not Surveyed Area) within the distress survey data file and

provision of null (blank) IRI, rut, fault, grade, and lane-width values within submitted

laser sensor data report for the MDOT location referencing mile point range (measured

along the MDOT route; not along a potential detour) associated with the construction

event.

Example of Required Mileage Adjustment within Final Data Submission:

A pavement segment to be collected is defined by MDOT location referencing from mile

point 0.000 to 10.000. However, during collection the vehicle was detoured starting at mile

point 4.000, traveled 4.000 miles until it was back on the proper route, and from there

collected another 4.000 miles before reaching the proper ending point. That’s 12.000

miles actually traveled, but the data must be referenced only to the proper location referencing

mileage range along the proper route (0.000 to 10.000). Therefore, the Vendor will be

directed by MDOT to edit final data by marking exactly what MDOT location referencing

mileage range (along proper roadway) was missed due to the construction zone and modify

the data accordingly for submittal:

The vehicle collected from 0.000 to 4.000 along the proper route before the detour, then

made 4.000 more miles of collection on the proper route once off of the detour before

reaching the ending reference point. Therefore, 2.000 miles along the proper route (mile

point 4.000 to 6.000) was not collected due to construction, and shall be marked by the Vendor

in distress survey data as PD0908 and nulled/blanked-out in the sensor data report accordingly for

final submittal.

MDOT will, upon initially reviewing the Vendor’s collected GPS and imagery data for

weekly acceptance during collection, indicate to the Vendor the start & end locations

associated with detour and/or construction limits for the Vendor to ut i l ize for

preparat ion of f inal data .


ATTACHMENT B


2018 – 2021

APPLICABLE AASHTO STANDARD SPECIFICATIONS

The Vendor shall comply with the following AASHTO Standard & Provisional

Specifications as applicable to data collection & processing required within this contract. Generally,

where disagreement possibly exists between MDOT requirements elsewhere in this document and

these AASHTO documents, the MDOT language shall take priority. In any such case observed,

however, the Vendor shall first seek prior clarification from MDOT:

AASHTO Standard Specifications

M 328-14 (Pub. May 2016) Inertial Profiler

R 36-17 (Pub. April 2017) Evaluating Faulting of Concrete Pavements

R 43-13 (Pub. April 2017) Quantifying Roughness of Pavements

R 56-14 (Pub. May, 2016) Certification of Inertial Profiling Systems

(Michigan Test Method 730 will serve in this capacity)

R 57-14 (Pub. May, 2016) Operating Inertial Profiling Systems

AASHTO Provisional Standards PP 68-14 (Pub. April, 2017) Collecting Images of Pavement Surfaces for Distress Detection

PP 69-14 (Pub. April, 2017) Determining Pavement Deformation Parameters and Cross

Slope from Collected Transverse Profiles

PP 70-14 (Pub. April, 2017) Collecting the Transverse Pavement Profile


ATTACHMENT C

2018 - 2021 Collection & Delivery Schedule*

ITEM COVERAGE (2018)

2018 Due Date

COVERAGE (2019/2020/2021)

2019 Due Date

2020 Due Date

2021 Due Date

Collection Start - 15-Apr - 15-Apr 15-Apr 15-Apr

Collection End a) All NHS Inv. Dir. b) All Remainders

a) 20-May (NHS) b) 1-July (All)

- 17-June 1-July 17-June

Distress Survey Data

Delivery

Metro Region NHS Inv. Dir.

20-May

University Trunk. (Region 1)

20-May

20-May

20-May

Univ. & SW NHS Inv. Dir. 3-June

Metro Trunk. (Region 7)

3-June 3-June 3-June

Bay & Grand NHS Inv. Dir. 17-June

Southwest Trunk. (Region 5)

17-June 17-June 17-June

Superior & North NHS Inv. Dir. + Univ. Remainder

1-July Bay Trunk. (Region 4)

1-July 1-July 1-July

Metro & SW Remainders

15-July Grand Trunk. (Region 3) 15-July 15-July 15-July

Bay Remainder

29-July Superior Trunk. (Region 1) 29-July 29-July 29-July

Grand Remainder

12-Aug North Trunk. (Region 2) 12-Aug 12-Aug 12-Aug

Superior & North Remainders

2-Sept

Statewide Non-Trunkline (Local Jurisdict.)

2-Sept 2-Sept 2-Sept

Laser Sensor Data

(IRI, Rut, Fault,

Grade, Lane-

Width) Delivery

a) All NHS Inv. Dir. b) All Remainders

a) 10-June (NHS) b) 22-July (All)

All Regions 8-July 22-July 8-July

GPS Delivery (Integrated into other Deliverable Schedules)

All Regions - All Regions - - -

Imagery Data Delivery All Regions 22-July All Regions 8-July 22-July 8-July

Curvature Data Delivery All Regions 22-July All Regions 8-July 22-July 8-July

“NHS Inv. Dir.” indicates HPMS inventory direction segments on the National Highway System, TBD by MDOT. * Granting of extensions due to collection delays reasonably beyond the Vendor’s control (bad-weather days,

as example, but not equipment failures) will be considered by MDOT upon review of the Vendor’s explanation.


DO NOT PROVIDE COSTS WITH YOUR PROPOSAL! THIS IS FOR INFORMATION ONLY! ** ATTACHMENT D


VENDOR PAY ITEM BID SHEET (2018-2021)

1. Field Data Collection (Vehicle Operation)*:

Total 4-Year Estimated Miles = 33,880 miles (Year 2018 = 9,230 miles; 2019 = 7,710 miles; 2020 = 9,230 miles; 2021 = 7,710 miles)

Proposed 2018-2021 Cost per Mile*

=

Proposed 4-Year Subtotal Contract Cost* =

*This Item’s 4-Year Subtotal cost shall not exceed 20% of the Total 4-Year Contract Cost

2. Processed Data:

A. Digital Imagery (Forward R.O.W. View & Pavement Down View):

Total 4-Year Estimated Miles = 31,420 miles

(Year 2018 = 8,000 miles; 2019 = 7,710 miles; 2020 = 8,000 miles; 2021 = 7,710 miles)

(Forward view images delivered at 40-foot spacing along route; downview images delivered providing continuous pavement-length coverage, with each image covering 20 feet of pavement length.)

Proposed 2018-2021 Cost per Mile =

Proposed 4-Year Subtotal Contract Cost =

B. Longitudinal Surface Profile - IRI Data:



To include: a) Line-laser-based elevation capture and .erd format

b) 0.1-mile segment calculations & statistics for each wheelpath




C. Transverse Surface Profile – Wheelpath Rut Data:



To include: a) Raw Transverse Profile Measurements

b) 0.1-mile segment calculations & statistics for each wheelpath



D. Surface Profile – Faulted Transverse Joint Data:



To include: a) Analysis of line-laser-based longitudinal elevation capture

b) Detection of faults ONLY AT TRANSVERSE JOINTS

c) 0.1-mile segment calculations & statistics for each wheelpath



E. Global Positioning System (GPS) Latitude/Longitude Pair Data:

Total 4-Year Estimated Miles = 33,880 miles (Year 2018 = 9,230 miles; 2019 = 7,710 miles; 2020 = 9,230 miles; 2021 = 7,710 miles)

(Data to be real-time corrected via RTK with the MDOT CORS)



F. Surface Distress Survey Data:






G. Longitudinal Grade and Horizontal Curvature Data***:

Total 4-Year Estimated Miles= 2,400 miles

(Year 2018 = 1,000 miles; 2019 = 1,000 miles; 2020 = 200 miles; 2021 = 200 miles)

To include: a) Longitudinal Grade Measurement per 0.1-mile

b) Horizontal Alignment Features Detection/Measurement



3. Software for MDOT Data Quality Assurance and Data Management

Supply & Operation/Maintenance Support for up to 8 MDOT staff licenses

Proposed 2018-2021 Cost per Year =


PROPOSED TOTAL 4-YEAR CONTRACT COST

=

*** MDOT reserves the right to remove this data item’s collection/delivery/payment from any

single year’s scheduling.

**This Attachment is for informational purposes only during the Qualifications-Based

Selection (QBS) process. This bid sheet shall be filled out ONLY by the winner of the

QBS. Any bids provided with the initial proposal will be considered non-responsive

and the proposal will be not be reviewed.


Vendor Pay Item Bid Sheet Validation Authorized Vendor Representative:

Printed Name

Signature

Date

Full Address:


ATTACHMENT E


Years 2018 – 2021

PAYMENT STRUCTURE & CRITERIA

1. Review/Acceptance of Field Data Collection (Vehicle Operation)

Criteria: All annually scheduled statewide collection segments must be validated as

properly collected or justifiably uncollectable via the MDOT review/acceptance

process as defined in this Scope of Services.

Payment: After MDOT determines criteria are met by Vendor, one single payment (in

dollars) will be made per year. The payment amount will be the calculated product

of the annual statewide mileage specified*** (estimated in Attachment D - Item 1)

and the Vendor’s bid unit price per mile for Field Data Collection. There will be four

separate payments of this type over the life of the contract.

2. Submittal/Acceptance of Processed Data

A) Digital Imagery (Forward R.O.W. View & Pavement Down View)

Criteria: All digital images associated with annually scheduled statewide collection

segments shall be determined, at the discretion of the MDOT Project Manager, to have

substantially passed through the MDOT review & acceptance process as defined in

this Scope of Services.

Payment: After MDOT determines criteria are met by Vendor, one payment (in dollars) will

be made per year. Each payment amount will be the calculated product of the

respective annual statewide mileage specified*** (estimated in Item 2A within Attachment D) and the Vendor’s bid unit price per mile for the Item. There will be

four separate payments of this type over the life of the contract.

B) Longitudinal Surface Profile – IRI Data

Criteria: All processed IRI-related measurement/reporting data associated with annually

scheduled statewide collection segments shall be determined, at the discretion of the

MDOT Project Manager, to have substantially passed through the MDOT review &

acceptance process as defined in this Scope of Services.



of the annual statewide mileage specified*** (estimated in Attachment D - Item

2B) and the Vendor’s bid unit price per mile for the Item. There will be four separate

payments of this type over the life of the contract.

C) Transverse Surface Profile – Wheelpath Rut Data


Criteria: All processed wheelpath rut-related measurement/reporting data associated with

annually scheduled statewide collection segments shall be determined, at the

discretion of the MDOT Project Manager, to have substantially passed through the

MDOT review & acceptance process as defined in this Scope of Services.



of the annual statewide mileage specified*** (estimated in Attachment D – Item

2C) and the Vendor’s bid unit price per mile for the Item. There will be four


D) Surface Profile – Faulted Transverse Joint Data

Criteria: All processed transverse joint fault measurement/reporting data associated with

annually scheduled statewide collection segments shall be determined, at the

discretion of the MDOT Project Manager, to have substantially passed through the

MDOT review & acceptance process as defined in this Scope of Services.




2D) and the Vendor’s bid unit price per mile for the Item. There will be four


E) Global Positioning System (GPS) Lat./Long. Pair Data

Criteria: All processed GPS-related measurement data associated with annually scheduled

statewide collection segments shall be determined, at the discretion of the MDOT

Project Manager, to have substantially passed through the MDOT review &

acceptance process as defined in this Scope of Services. Payment: After MDOT determines criteria are met by Vendor, one single payment (in dollars)

will be made per year. The payment amount will be the calculated product of the

annual statewide mileage specified*** (estimated in Attachment D – Item 2E) and

the Vendor’s bid unit price per mile for the Item. There will be four separate

payments of this type over the life of the contract.

F) Surface Distress Survey Data

Criteria: All surface distress survey data shall pass through the MDOT review & acceptance process as defined in this Scope of Services. Payment:

Payment eligibility will be determined as a percentage of units costs as indicated

below:

Phase 1: 50% of the unit price per mile for Surface Distress Survey Data will be eligible

for payment for each LocID passing initial logic check.

Phase 2: 35% of the unit price per mile for Surface Distress Survey Data will be eligible

for payment for each LocID passing survey call quality-level check.

Phase 3: 15% of the unit price per mile for distress survey data will be eligible for payment

for each LocID within an MDOT Region when all LocIDs within the Region have passed


both initial logic check and survey call quality level check.

After MDOT determines that phase criteria are met by the Vendor for each yearly-indicated

LocID’s surface distress survey data, payment (in dollars) will be made per LocID mileage,

per phase. The payment amount will be the calculated product of the annual LocID mileage

specified*** for Vendor surface distress survey performance (total yearly estimates in

Attachment D – Item 2F) and the phase percentage of the Vendor’s bid unit price per mile

for the Item. There will be a variable number of separate payments of this type per year over

the life of the contract due to the phase eligibility criteria described above.

G) Longitudinal Grade and Horizontal Curvature Data

Criteria: All processed Grade and Curvature data associated with annually scheduled

statewide collection segments shall be determined, at the discretion of the MDOT

Project Manager, to have substantially passed through the MDOT review &

acceptance process as defined in this Scope of Services.

Payment: After MDOT determines criteria are met by the Vendor, one single payment (in



2G) and the Vendor’s bid unit price per mile for the Item. There will be four


3. Software for MDOT Data Quality Assurance and Data Management

Criteria: All Vendor software to facilitate MDOT data QA and management functions

shall be received, reviewed, determined to be operationally sufficient, and accepted

by MDOT.

Payment: After MDOT determines criteria are met by Vendor, the first collection year’s

(2018’s) annual payment (in dollars) will be made in the amount equal to the

Vendor’s associated bid price per year (Attachment D – Item 3). Subsequent

single annual payments of the same amount will be made at the completion of

collection within the three remaining years. There will be four separate payments

of this type over the life of the contract.

*** Pavement segment mileages used for payment bases will be those defined by the MDOT linear

location referencing system within the annual TapeLog file that will be provided to the Vendor to

designate each year’s collection segments.


ATTACHMENT F

MDOT

PAVEMENT CONDITION DATA SYSTEM

FILE FORMATS

OF

LOCATION REFERENCING, DISTRESS, AND SENSOR DATA

FOR

PAVEMENT CONDITION MONITORING UTILIZING VEHICLE-COLLECTED DATA

(2018 – 2021 Collection Years)

Updated November, 2017

D. Sokolnicki, Data Collection & Reporting Section

Bureau of Transportation Planning


This document specifies the data formats for the MDOT-provided TapeLog, Pavement Type Location,

and Rut/Fault Location-Specification files, as well as required formats for the Vendor Data Collection

Log, Distress Survey Data, Offset-Distance, and Sensor Data/Grade/Curvature files that shall be

submitted by the Vendor.

The TapeLog file contains key attributes of each pavement section to be collected. This file will be

provided by MDOT to the vendor and is discussed in Section I of this document.

The Pavement Type Locations & Rut/Fault Data Specification file defines the mileage ranges of

pavement types within each pavement segment to be collected and whether or not wheelpath rut and or

transverse joint fault data are to be provided by the Vendor. This file will be provided by MDOT to the

vendor and is discussed in Section II of this document.

The Vendor Data Collection Log links the MDOT TapeLog file’s location referencing data to the

Vendor’s collection data’s Set/FrameID-based referencing and GPS referencing. This file will be discussed in

Section III of this document.

The Distress Survey Data are to be generated according to the MDOT Distress Manual for Surveying

of Pavement Surfaces. These data shall be delivered to MDOT by the Vendor. The details of these data

will be discussed in Section IV of this document.

The Offset-Distance data shall be created by the Vendor during collection, logging accumulated

distance against increasing FrameIDs. The Vendor shall deliver these data to MDOT prior to having

the ability to run the MDOT-provided distress survey data logic-checking functionality via the

MDOT-established FTP site. The details of these data are discussed in Section IV of this document.

The (laser) Sensor Data related to pavement surface longitudinal and transverse profile measurements are to

be obtained according to requirements stated throughout this Scope document. Corresponding summary

data formats submitted by the Vendor shall conform to Section VI of this document.

To facilitate later discussions on the above subjects, the location referencing system for MDOT Trunkline

(state jurisdiction) pavements is described as follows:

When a non-divided pavement section (two-way traffic) or a pair of divided pavement sections (one-way

traffic) is constructed, a 5-digit number such as 02011 is assigned to the constructed pavement section(s).

This number is termed as the Control Section (CS) of a constructed pavement section. A linear and

increasing milepost system is used to assign mileposts to a constructed pavement section according to the

construction direction. Although the starting milepost is typically zero, it can be any


positive number. These mileposts are termed as the CS Mileposts of a constructed pavement section. The

construction direction is defined as the CS Direction of a constructed pavement section. The end point

with the lowest CS Milepost is defined as the CS Beginning Point of a constructed pavement section and

the end point with the highest CS Milepost is defined as the CS Ending Point of a constructed pavement

section. Some important further points:

1. CS Direction and traffic direction may be opposite. Therefore, the CS Beginning Point

and CS Ending Point may be the ending point and beginning point, respectively, in terms

of traffic direction.

2. CS, CS Direction, and CS Mileposts cannot uniquely identify a pavement section.

3. CS (Control Section) and pavement section are often interchangeable terms.

Each pavement section is also assigned with an additional location referencing number (PR or Physical

Reference) which has 7 digits. (All Michigan roads have PR identification, while only MDOT-

jurisdiction roads also have CS identification.) To prepare for MDOT’s potential future complete

conversion from CS to PR, two zeros are inserted at the front of a CS. However, for the purpose of

explanation within this document, the expanded CS will still be referred to simply as CS.

A Route may be composed of multiple Control Sections and is assigned with a name, such as I96. The

Route Direction of a route is the majority of the traveling directions of its CS members. CS Direction

may or may not match Route Direction. For a fully or partially divided Route, the two divided portions

have the same Route Direction (such as EB), the same CS Direction, but have opposite traffic/collection

directions (such as EB and WB). For a non-divided Route, the Route Direction and CS Direction may or

may not match and, as well, the traffic/collection direction may either match or be opposite of either the

Route Direction or CS Direction. ( Route Direction is primarily used for administrative purpose only.)

In summary, a CS (or PR) has the following attributes:

ROUTE: Route Name of Its Associated Route

ROUTE_DIR: Route Direction of Its Associated Route (NB, SB, EB, WB)

CS or PR: Control Section or Physical Reference Number

(5 to 7-digit number)

CS_DIR: CS or PR Direction (NB, SB, EB, WB)

CS_BMP: Segment’s Beginning CS or PR Milepost (to nearest 0.001mile)

CS_EMP: Segment’s Ending CS or PR Milepost (to nearest 0.001 mile)

The collection vehicle must travel according to the traffic direction which may not agree with the CS

Direction. To avoid confusion, the following terms are defined for collection and data processing

purposes:

Traf_DIR: Traveling direction of the collection vehicle.

This will be referred to as the collection direction throughout this document.

BMP: CS milepost of the beginning point of a pavement section to be


collected.

EMP: CS milepost of the ending point of a pavement section to be collected.

For the purpose of using shorter identification in the data processing, the following Location ID

(LOC_ID) is defined to uniquely define a pavement section to be collected:

LOC_ID = <CSorPR><#1><#2><#3><#4>

where

<#1> = the first character of CS_DIR (E of EB, for example)

<#2> = the first character of Route_DIR (E of EB, for example)

<#3> = the first character of TRAFDIR (W of WB, for example)

and

<#4> = 2-character code to ensure that LOC_ID is a unique key for identifying a

pavement section.

The typical convention for <#4> is as follows:

For any CS that belongs to a single route, the <#4> is 00. For a CS that is partitioned into several

sections and each section belongs to a different route, <#4> is an unique positive number (within a CS)

assigned to each section. Typically in such instances, <#4> will have the value of 01 assigned to the

pavement section with the lowest CS Milepost numerical range; 02 assigned to the next highest CS

Milepost range, etc.

The above Location ID for each pavement section to be collected is defined in the annual MDOT TapeLog

file provided to the Vendor each year. The Vendor shall incorporate the provided Location ID (LocID)

into the detailed data files (to be explained later in this document).


I. TapeLog File for Data Collection This file contains information for each pavement section to be collected. This information is also needed

for Vendor data-record creation to be defined later in this document. MDOT will provide a unique annual

version of the TapeLog file to the vendor prior to each year’s collection season.

File Format Each record in this file defines a pavement section to be collected and has the following data fields:

LOCID : Location ID

ROUTE : Route name

RTEDIR : Route direction

CS: MDOT Control Section Number

PR: State of Michigan Physical Reference Number

CSDIR: Control Section or Physical Reference Number mileage-order direction

TRAFDIR: Collection (Traffic) Direction

BMP: Beginning CS or PR milepost

EMP: Ending CS or PR milepost

LENGTH: Collection length in miles

REGION: Number designation of associated MDOT Region (1 through 7)

NONTRUNK: Indication of segment as a local-jurisdiction road (“True” or “False”)

START DESC: Descriptor of location where vehicle shall start collection

END DESC: Descriptor of location where vehicle shall stop collection

SUFFIX: Last two characters of LOCID

COUNTY_NAME: Name of county this location lies within

LANE: Collection lane designation

DISTRESS: Distress survey data requirement (“True” or “False”)

IRI: Long. profile data (International Roughness) required (“True” or “False”) RUT: Wheelpath rut data required (“True”, “False”, or “Partial”)

FAULT: Trans. joint fault-detect data required ((“True”, “False”, or “Partial”)

IMAGES: Forward perspective and downview requirement (“True” or “False”)

Grad/Curv: Grade & Horizontal Curvature data required (“True” or “False”)

LaneWidth: Lane width measurement data required (“True” or “False”)

CollDir: “I” for Increasing CS/PR mileage dir; “D” for Decreasing CS/PRmileage dir.

BMP_LAT: Latitude which corresponds to BMP

BMP_LONG: Longitude which corresponds to BMP

EMP_LAT: Latitude which corresponds to EMP

EMP_LONG: Longitude which corresponds to EMP

Example Record (Fictitious):

0082111EEE00,I375,EB,82111,4378953,EB,EB,3.044,4.001,0.957,7,T,175Jnct.,MapleSt.,00,Wayne,1,T,T,F,T,T,F,F,D,44.

85871055,-83.42400432,45.06225655,-83.43338034


II. Pavement Type Locations and Rut/Fault Data Specification

The Vendor shall provide distress survey codes that are compatible with the MDOT-specified pavement

type for a given LocID’s mileage range. (See PD Code/Pavement Type compatibility definitions within

ATTACHMENT G.) Additionally, laser measurement data for transverse joint faulting and wheelpath

rutting will be required only on certain pavement types. The following file format is a fictitious example

of the file that MDOT will provide annually to the Vendor defining such locations:

LOCATION_ID PAVE_TYPE_CD PAVE_TYPE_DESC BMP EMP RUT FAULT

0001051NNN00 3 COMPOSITE 0 6.194 TRUE FALSE

0001051NNN00 2 FLEXIBLE 6.194 9.846 TRUE FALSE

0001051NNN00 3 COMPOSITE 9.846 10.426 TRUE FALSE






0002041EEE00 2 FLEXIBLE 0 22.549 TRUE FALSE

0002041EEE00 1 RIGID (JOINTED) 22.549 26.76 FALSE TRUE

0002042EEE00 3 COMPOSITE 0 0.537 TRUE FALSE

0002042EEE00 2 FLEXIBLE 0.537 0.836 TRUE FALSE

0002042EEE00 3 COMPOSITE 0.836 1.204 TRUE FALSE

0002042EEE00 2 FLEXIBLE 1.204 15.694 TRUE FALSE

0003032NNN00 1 RIGID (UNJOINTED) 0 2.013 FALSE FALSE


0003032NNS00 3 COMPOSITE 4.159 2.29 TRUE FALSE

0003032NNS00 1 RIGID (JOINTED) 2.29 0 FALSE TRUE

0003033NNN00 1 RIGID (UNJOINTED) 0 9.37 FALSE FALSE


0003033NNS00 3 COMPOSITE 12.454 9.37 TRUE FALSE

0003033NNS00 1 RIGID (JOINTED) 9.37 0 FALSE TRUE


0003034NNN00 1 RIGID (JOINTED) 3.352 10.573 FALSE TRUE


III. Vendor Weekly-Submitted Data Collection Log

The Vendor shall maintain and appropriately update a log relating the MDOT TapeLog information to

corresponding data collected in the field. A weekly collection log shall be provided containing only those

TapeLog LocID segments actually collected/attempted each week. The weekly log shall not be

cumulative for the collection season. Once a given TapeLog segment has been accounted for within a

submitted weekly collection log, subsequently submitted records for the LocID within a later-week’s

collection log will be rejected by MDOT’s system if the previously submitted record for the LocID was

found by MDOT to represent an adequate collection attempt (that is, not requiring recollection). (Set 999

shall be exclusively used by the Vendor to designate within the weekly submitted collection log file any

record segment for which the vendor could not perform any collection due to route closures, construction

detours, etc.) The collection log shall contain a header row and, verbatim, all data fields from the MDOT

TapeLog along with, at least, the following additional attribute fields:

- Date/time of collection

- Vendor-measured length of pavement segment to the nearest 0.001 mile

- Set identification # (Each TapeLog LocID record shall have only one Set #)

- Pavement Segment Beginning & Ending FrameIDs

- Pavement Segment Beginning & Ending GPS lat/long pair

IV. Vendor Weekly-Submitted 0.1-mile IRI, Rut, & Fault Data

To facilitate MDOT quality assurance checks of data measurements during the collection season, the

Vendor shall submit on a weekly basis a file containing 0.1-mile-segmented IRI, rut, and fault-detection

measurements for the LocIDs listed in the weekly-submitted collection log file. The weekly-submitted

file shall contain only data for those TapeLog LocID segments actually collected/attempted each week –

the file shall not be cumulative for the collection season. Formatting of the file content shall include a

combination of fields from both the separately submitted weekly collection log and the specified format

for the final (statewide) sensor data reporting (described in Section VI of this Attachment). Prior to each

annual season’s collection start, the Vendor shall consult with the MDOT Project Manager to determine

and confirm the specific format required for weekly delivery.

V. Distress Survey Data Files and Their Companion Files The Vendor shall survey pavement segments to identify surface distress conditions and organize such data

according to the formatting specified in this section and in compliance the MDOT Distress Manual for

Surveying of Pavement Surfaces (ATTACHMENT G). The distress survey data of each pavement

segment (defined in the annual MDOT-provided TapeLog file) shall be provided to MDOT in both a

Detailed Distress Survey Data file and its companion, an Offset-Distance file. These files are defined

below.

V-1. Set, FrameID, and Offset-Distance


A “Set” is used by MDOT to group together consecutively collected data within an additional reference

system (separate from linear mileage measurement) convenient for organization and management purposes. Each Set shall have a SetID number (3 or 4 digits) unique to each collection year and each collection vehicle. Additionally, each single Set shall be limited in assignment to data collected on the same day. A Set can be assigned to multiple LocIDs (defined in the TapeLog file). A FrameID shall be a non-negative numeric value unique within a single Set. (Acceptable FrameID values range from 0 to 999999999, inclusive.) FrameID values are expected to increase with the orderly progression through a LocID’s collected dataset as the offset distance of collection (from the LocID’s start location) increases. A structured relationship shall be created by the Vendor between a Set’s increasing FrameID values, increasing offset distance (inches) from the Set’s beginning location, and the MDOT-defined milepoints (to nearest 0.001-mile) for any single LocID assigned to the Set.

The vendor shall provide offset distance data according to the following file specifications:

The accumulated distance of all FrameIDs for each Set shall be stored in a file (and delivered to MDOT)

titled OffsetDis.<#>, where <#> is the 3- or 4-digit Set ID. As FrameID increases, the offset distance,

reported in inches, shall not decrease. This file will be referred to as an Offset-Distance file. The file

shall not include a header record. Each record in this file shall have two fields (separated by a comma)

as follows:

Field 1: Frame ID

Field 2: Distance (offset in inches from the Set’s beginning location)

Example Offset-Distance File Content:

289560,0

289566,63

289572,127

289578,190

289584,253

289592,317

289599,380

289606,444

289613,507

289621,570

289629,634

289636,697

The data in an Offset-Distance file are used by the MDOT system to compute mileposts for distress survey

data quality assurance checks and for other data processing applications.

V-2. Distress Survey Data Files Within each file, the distress survey data shall be stored in the order of collection (traffic) direction


mileage. The entire mileage of a LocID shall be comprehensively covered by the records within the

associated file – no mileage gaps. Each record provides the data for the unique pavement surface

condition type (conforming to the MDOT Distress Manual – Attachment G) as observed/detected by the

Vendor’s survey process, and shall contain the following fields (separated by commas, ordered left to

right):

LOCID (12 characters):

The data value in this field is constant across all records in a single file and shall

correspond to the MDOT-defined LOCID as provided in the TapeLog file.

Set_ID (3 or 4 characters):

The 3- or 4-digit Set ID. The data value in this field is constant across all records in a

single file.

FID_LOCID_START (6 characters max):

FrameID which corresponds to the beginning descriptor for a given LOCID. The data

value in this field is constant across all records in a single file.

FID_LOCID_END (6 characters max):

FrameID which corresponds to the ending descriptor for a given LOCID. The data value

in this field is constant across all records in a single file.

CS_PR_BMP (6 characters max):

MDOT Control Section (CS) or Physical Reference Number (PR) Milepost corresponding

to the beginning of the pavement distress condition in this record.

CS_PR_EMP (6 characters max):

MDOT Control Section (CS) or Physical Reference Number (PR) Milepost

corresponding to the ending of the pavement distress condition in this record.

Coll_Date (8 characters):

Date of field collection from which the Vendor distress survey data is generated.

Survey_Lane_Number (1 character):

Numbered designation of the lane in which this distress condition is observed.

The lane number is 1 for the far right (traffic/truck) thru lane and increases for each


adjacent lane to the left (while facing the direction of collection travel). Temporary

auxiliary or weave/merge lanes between closely-located interchanges, right-turn

lanes, flares, and "Exit Only” lanes shall not be considered thru lanes.

PD_Code (4 characters, including a leading zero):

Code of a Principal Distress (PD) condition.

This code is defined in the MDOT Distress Manual for Surveying of Pavement

Surfaces.

AD1_SL_Index

AD2_SL_Index (2 characters max each):

Indices of severity level of AD (Associated Distress)

These two indices define severity and/or extent of a principal distress condition based on

the corresponding Associated Distress matrix . Note that a value of -1 is used to indicate

“not applicable”. The details are defined in the MDOT Distress Manual for Surveying

of Pavement Surfaces.

AD_Type_Index (2 characters max) :

This is the index of the associated distress type. A value of -1 is used to indicate “not

applicable”. The details are defined in the MDOT Distress Manual for Surveying of

Pavement Surfaces.

FID_RECORD_START (6 characters max):

FrameID corresponding to the beginning of the pavement distress condition in this

record.

FID_RECORD_END (6 characters max):

FrameID corresponding to the ending of the pavement distress condition in this

record.

The data records in this file must be organized in the order of the collection (traffic) direction. For the

transverse-oriented distresses, each principal distress (PD) identified must be recorded one-per- record.

(See the MDOT Distress Manual for allowed longitudinal proximity of consecutive transversely

oriented distress types and data-file recording of such.) For the longitudinal-oriented distresses, a

continuous distress (such as Alligator Cracking) with the same associated distress level (same

extent/severity level), may be recorded as one record that covers from the distress type occurrence’s

beginning milepoint to its ending milepoint.

The naming convention for a distress survey data file is <main title>.<file extension> where


<main title> is the first 8 characters of the LOC_ID and <file extension> is the last 3 characters of the LOC_ID. Examples:

LOC_ID 0023058NNN00

Distress survey data file name = 0023058N.N00

LOC_ID 1649638EEW01

Distress survey data file name = 1649638E.W01

Sample internal records of a detailed distress data file are shown below:

0002042EEE00,2816,880393,914427,0.078,0.078,06/26/2015,1,110,5,3,-1,880794,880794

0002042EEE00,2816,880393,914427,0.078,0.080,06/26/2015,1,326,1,1,-1,880794,880803

0002042EEE00,2816,880393,914427,0.080,0.080,06/26/2015,1,110,5,2,-1,880803,880803

0002042EEE00,2816,880393,914427,0.080,0.083,06/26/2015,1,326,1,1,-1,880803,880815

0002042EEE00,2816,880393,914427,0.083,0.084,06/26/2015,1,326,1,1,-1,880815,880819

0002042EEE00,2816,880393,914427,0.084,0.086,06/26/2015,1,326,1,1,-1,880819,880828

0002042EEE00,2816,880393,914427,0.085,0.085,06/26/2015,1,110,1,1,-1,880824,880824

0002042EEE00,2816,880393,914427,0.086,0.087,06/26/2015,1,326,1,1,-1,880828,880832

0002042EEE00,2816,880393,914427,0.087,0.088,06/26/2015,1,501,-1,-1,-1,880832,880836

0002042EEE00,2816,880393,914427,0.088,0.136,06/26/2015,1,326,1,1,-1,880836,881029

0002042EEE00,2816,880393,914427,0.136,0.137,06/26/2015,1,501,-1,-1,-1,881029,881034

0002042EEE00,2816,880393,914427,0.137,0.137,06/26/2015,1,114,-1,-1,-1,881034,881034

0002042EEE00,2816,880393,914427,0.137,0.139,06/26/2015,1,501,-1,-1,-1,881034,881042

0002042EEE00,2816,880393,914427,0.139,0.140,06/26/2015,1,202,5,-1,-1,881042,881046

0002042EEE00,2816,880393,914427,0.140,0.140,06/26/2015,1,114,-1,-1,-1,881046,881046

0002042EEE00,2816,880393,914427,0.140,0.152,06/26/2015,1,501,-1,-1,-1,881046,881095

0002042EEE00,2816,880393,914427,0.152,0.152,06/26/2015,1,110,5,2,-1,881095,881095

0002042EEE00,2816,880393,914427,0.152,0.156,06/26/2015,1,501,-1,-1,-1,881095,881112

0002042EEE00,2816,880393,914427,0.156,0.204,06/26/2015,1,326,1,1,-1,881112,881304

0002042EEE00,2816,880393,914427,0.204,0.205,06/26/2015,1,501,-1,-1,-1,881304,881308

0002042EEE00,2816,880393,914427,0.205,0.205,06/26/2015,1,110,5,2,-1,881308,881308

0002042EEE00,2816,880393,914427,0.205,0.211,06/26/2015,1,501,-1,-1,-1,881308,881332

0002042EEE00,2816,880393,914427,0.211,0.215,06/26/2015,1,204,1,-1,-1,881332,881347

0002042EEE00,2816,880393,914427,0.212,0.213,06/26/2015,1,236,1,-1,-1,881335,881339


Overview of MDOT’s Distress Survey Data File Logic-Checking Routine

The Vendor’s submitted distress survey data files shall individually pass through an automated logic-

checking routine provided by MDOT. Prior to being able to run the routine on any specific distress survey

data file, the Vendor shall first supply MDOT with the Offset-Distance file (for the corresponding Set),

which must pass its own adequacy checks to gain successful loading to the MDOT database.

The MDOT Database System then repeats the following steps for each LocID’s distress survey file:

(Listing order herein does not necessarily match order of actual check execution.)

1. System sorts the distress survey file data records by increasing order of FID_RECORD_START

(primary) and by increasing order of FID_RECORD_END (secondary).

2. System checks that a corresponding record for the LocID/Survey Year exists within the TapeLog file for

the given collection year. The file is rejected if a TapeLog record is not found.

3. System compares the LocID-specific distress data file content against expected Coll_Date, Set_ID,

FID_LOCID_START, and FID_LOCID_END to make sure they match information originally received in

the Vendor’s submitted weekly collection log record (plus any required changes communicated to Vendor

via the Outstanding Collection Issues report), otherwise the file is rejected.

4. System makes sure there are no unresolved issues from MDOT Collection Review (described in

Outstanding Collection Issues reports sent to Vendor) other than “Not-Surveyed” (PD908) section

requirements. (All Outstanding Collection Issues report items other than “Not-Surveyed section required”

must be resolved before distress survey data file load-check. “Not-Surveyed section” issues are checked

further on in this distress file load-check.) The file is rejected if unresolved issue is found.

5. System checks that Not-Surveyed section requirement(s) are provided in file. (Not-Surveyed sections on

brick pavement are allowed by the System without checking against the Outstanding Collection Issues

report requirements.) The file is rejected if it does not contain the proper Not-Surveyed section

requirements.

6. System checks for previous existence of distress survey data for the LocID and Survey Year in the

database. If same-year distress survey data already exists, System checks to see if it had failed on PD/AD

Call Quality Level check or had been rejected. The file is rejected if neither of those two situations exist.

7. System compares the FID_LOCID_START of the distress survey file with the FID_RECORD_START

of the file’s first record to make sure they are same. If that is not the case, the file is rejected.

8. With Vendor required to provide PD 501 (No Distress Area) record for all pavement ranges where no

distresses observed, the System checks to make sure that the largest FID_RECORD_END value within the

file is equal to the FID_LOCID_END of the file. The file is rejected if that is not the case.

9. System checks that FID_LOCID_START is less than FID_LOCID_END. Otherwise, the file is rejected.

10. System compares absolute-value difference between file’s first record CS_PR_BMP and last record


CS_PR_EMP to LocID length value reported in TapeLog file. The file is rejected if the two lengths differ

by more than MDOT’s established database tolerance.

11. System checks for PD incompatibilities within the file – per the PD Incompatibility Table definitions of

this Scope’s Distress Manual attachment. The file is rejected if any incompatibility is found.

12. System repeats the following check steps for each record in the file, and rejects the file if any error is

found:

(Listing order herein does not necessarily match order of actual check execution.)

a) System checks all 14 columns of each record for required non-blank values.

b) System uses MDOT-defined pavement type-change milepoints and the Vendor’s provided offset-

distance file to determine FrameID associated with each pavement type-change location. System then

compares those FrameID(s) to each PD record’s FID_RECORD_START and FID_RECORD_END to

ensure no overlap exists, as PD calls cannot cross PAVEMENT TYPE boundary defined by Offset-

Distance/FrameID.

c) System checks to ensure all FID-related columns contain numeric values >= 0.

d) System compares LOCID column’s CS Direction and TrafDir (Collection) Direction characters, then

checks the CS_PR_BMP against the CS_PR_EMP: Where LOCID defines increasing mileage direction,

CS_PR_BMP must be <= CS_PR_EMP for the record. Where LOCID defines decreasing mileage

direction, CS_PR_BMP must be >= CS_PR_EMP for the record.

e) System checks that FID_RECORD_START is greater than or equal to the file’s FID_LOCID_START.

f) System checks that the record’s FID_RECORD_START is not greater than its FID_RECORD_END.

g) System checks that the record’s FID_RECORD_END is not greater than the file’s FID_LOCID_END.

h) System checks that the record’s CS_PR_BMP and CS_PR_EMP are equal when the

FID_RECORD_START is equal to the FID_RECORD_END.

i) System checks that if FID_RECORD_START is >= FID_RECORD_END of previous record, then

CS_PR_BMP is >= CS_PR_EMP of the previous record.

j) System checks compatibility of the record’s PD Code and the pavement type defined in the MDOT-

provided PaveTypeFile for the record’s mileage location (per Distress Manual’s compatibility definitions).

k) System checks the Survey_Lane_Number value to ensure >= 1 and < 10.

l) For records containing longitudinally oriented PDs (except for PD0326 or PD0327), system checks to

make sure the FID_RECORD_START does not equal the FID_RECORD_END and that the CS_PR_BMP

does not equal the CS_PR_EMP. For transversely oriented PDs, the FID_RECORD_START must match

the FID_RECORD_END and the CS_PR_BMP must match the CS_PR_EMP.

m) System checks to ensure no mileage gap exists between the record’s CS_PR_EMP and the next record’s


CS_PR_BMP.

n) System utilizes the record’s FID_RECORD_START and FID_RECORD_END and computes expected

associated milepoints from offset lengths found in the Vendor’s submitted Offset-Distance file for the

associated Set#. Those calculated milepoints are then checked against the record’s CS_PR_BMP and

CS_PR_EMP values using a +/- 0.002-mile tolerance.

o) System checks that values in the record’s AD1_SL_Index, AD2_SL_Index, and AD_Type_Index fields

fall within acceptable and/or expected respective ranges according to AD matrix definitions (per PD Type)

within the Scope’s Distress Manual attachment.


VI. Final IRI, Rut, Fault, Lane-Width, Grade/Curvature Data (“Sensor

Data”) Summary Files Formats The following pages contain specifications of the two individual summary file layouts for the sensor data

types to be submitted by the Vendor on an annual basis after all statewide collection is completed.

(Weekly-submitted sensor data shall also conform to this format. The Vendor shall verify such prior to

be beginning of each collection season.) Each file shall be in .csv format without tab or space characters,

and shall cover all statewide segments specified by MDOT for each year.


IRI / FAULTING / RUTTING / GRADE/LANE-WIDTH* Attributes Example data Definition

Locid 0009111NNN00 The alpha-numeric twelve character unique identifier per 1/10 mile segment

CS_PR 09111 The numeric Control Section or Physical Reference number per 1/10 mile segment (integer value between five and seven digits in length)

Direction I The alpha single-character control section or physical reference segment’s mileage direction for a segment. Values entered in this field are I (increasing) or D (decreasing).

Start-Mi 0.000 The numeric beginning mile point for segment. (Decimal value precise to the nearest 0.001 mile.)

End-Mi 0.100 The numeric ending mile point for segment. (Decimal value precise to the nearest 0.001 mile.)

Set 1111 The numeric Set ID associated with this segment (3- or 4-digit integer value)

BegFrameID 12345 The numeric beginning FrameID for a segment (integer value)

EndFrameID 67890 The numeric ending FrameID for a segment (integer value)

SurveyDateTime 04/07/2004 12:00 Numeric collection date & start-time for a segment. Format: mm/dd/yyyy hh:mm, 24-hr, rounded to nearest minute**

Region 4 Region number for a segment (integer value - 1 through 7)

StaLatitude +43.6126442 GPS latitude for the beginning of the segment (decimal value precise to the nearest 7th decimal place)

StaLongitude -83.9473419 GPS longitude for the beginning of the segment (decimal value precise to the nearest 7th decimal place)

EndLatitude +43.6140938 GPS latitude for the ending of the segment (decimal value precise to the nearest 7th decimal place)

EndLongitude -83.9472427 GPS longitude for the ending of the segment (decimal value precise to the nearest 7th decimal place)

AvgSp 55.0 Average speed (MPH) the collection vehicle was traveling for the segment (decimal value precise to the nearest 0.1 MPH) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

Stops 0 Number of occurrences the collection vehicle stopped for segment (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

Bridge 0 Number of bridge decks the collection vehicle passed over for the segment (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

RR 0 Number of railroad crossings the collection vehicle passed over for the segment (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

Constr 0 Number of construction zones collection vehicle encountered for the segment (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

Detour 0 Number of detours collection vehicle encountered for the segment (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas


L1 56 Percent of segment length spent in Lane #1 (far-right thru lane) (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

Slow 36 Percent of segment length collection where collection vehicle speed was less than 15 MPH (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

Temp 56 Average pavement surface temperature for Segment (°F, integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

IRILeft 69 IRI Average (inches per mile) in Left Wheelpath for Segment (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

IRIRight 82 IRI Average (inches per mile) in Right Wheelpath for Segment (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

FaultNumLeft (>=0.04 Inches)

7 Number of Faults >= 0.04 inch Detected Only at Constructed Joints in LWP for segment (integer value, shall be populated with “0” when no faulted joints detected; shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas) (Jointed Rigid Pavements Only)

FaultAveLeft 0.08 Average Absolute Fault Value Detected Only at Constructed Joints in LWP for segment, to nearest 0.04 inch. Shall be populated with “0.00” when FaultNumLeft field is populated with “0”, and shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas) (Jointed Rigid Pavements Only)

FaultMaxLeft 0.12 Maximum Absolute Fault Value Detected Only at Constructed Joints in LWP for segment, to nearest 0.04 inch Shall be populated with “0.00” when FaultNumLeft field is populated with “0”, and shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas) (Jointed Rigid Pavements Only)

FaultNumRight (>=0.04 Inches)

7 Number of Faults >= 0.04 inch Detected Only at Constructed Joints in RWP for segment (integer value) Shall be populated with “0” when no faulted joints detected; shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas) (Jointed Rigid Pavements Only)

FaultAveRight 0.08 Average Absolute Fault Value Detected Only at Constructed Joints in RWP for segment, to nearest 0.04 inch. Shall be populated with “0.00” when FaultNumRight field is populated with “0”, and shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas) (Jointed Rigid Pavements Only)

FaultMaxRight 0.12 Maximum Absolute Fault Value Detected Only at Constructed Joints in RWP for segment, to nearest 0.04 inch Shall be populated with “0.00” when FaultNumRight field is populated with “0”. Shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas) (Jointed Rigid Pavements Only)

RutAveLeft 0.04 Average Rut Value in LWP for segment, to nearest 0.01 inch (Flexible and Composite Pavements Only) Shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas


RutMaxLeft 0.07 Maximum Rut Value in LWP for segment, to nearest 0.01 inch (Flexible and Composite Pavements Only) Shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas

RutAveRight 0.11 Average Rut Value in RWP for segment, to nearest 0.01 inch (Flexible and Composite Pavements Only) Shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas

RutMaxRight 0.15 Maximum Rut Value in RWP for segment, to nearest 0.01 inch (Flexible and Composite Pavements Only) Shall be blank/null for non-applicable pavement-type areas or MDOT-defined “Not-Surveyed” areas

Heading (degrees)

241 (or Azimuth) - The average horizontal angle of the vehicle’s directional bearing (measured clockwise from due North) for segment (integer value) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

Grade (+/- %) 3.03 Average longitudinal grade of pavement surface (in collection travel direction) for segment (decimal value precise to nearest 0.01 %) Shall be blank/null for MDOT-defined “Not-Surveyed” areas

LaneWidth 10 Numeric value of measured lane width, precise to nearest whole foot Shall be blank/null for MDOT-defined “Not-Surveyed” areas

*Note: Individual data measurement or statistic record cells (location referencing cells excluded) for

mileage ranges that MDOT has directed to be marked as “Not Surveyed” (due to construction, detour,

non-applicable pavement type, etc.) shall be left blank.

Additionally, for reporting of data across MDOT-defined pavement-type-change milepoints or

required “Not-Surveyed” area boundary breaks when such fall within 0.1-mile segmentation, the

vendor shall begin/end (a) new record(s) of data defined by the MDOT-specified milepoint(s) in order

to properly display required nulled-out data measurement or statistic record cells accordingly.

**Note: The date/time reported across multiple 0.1-mile records within a LocID shall be the same;

listing only the starting time of the LocID’s collection.


HORIZONTAL CURVATURE

Attributes Example data Definition

locid 0009111NNN00 The alpha-numeric twelve character unique identifier

CS_PR 09111 The numeric seven-digit Control Section or Physical Reference number number (integer value between five and seven digits in length) Direction I The alpha single-character control section or physical reference segment’s mileage direction. Values entered in this field are I (increasing) or D (decreasing).

Start-Mi 0.000 The numeric beginning mile point for the curvature feature (Decimal value precise to the nearest 0.001 mile.)

End-Mi 0.100 The numeric ending mile point for the curvature feature (Decimal value precise to the nearest 0.001 mile.)

Set 111 Numeric Set ID associated with segment (3- or 4-digit integer value)

BegFrameID 12345 Numeric beginning FrameID for the curvature feature (integer value)

EndFrameID 67890 The numeric ending FrameID for the curvature feature (integer value)

SurveyDateTime 04/07/2004 12:04 Numeric collection date & start-time for the segment Format: mm/dd/yyyy hh:mm, 24-hr, rounded to nearest minute**

region 4 Region number (integer value between 1 and 7)

StaLatitude +43.6126442 GPS latitude for the beginning of the curvature feature (decimal value precise to the nearest 7th decimal place)

StaLongitude -83.9473419 GPS longitude for the beginning of the curvature feature (decimal value precise to the nearest 7th decimal place)

EndLatitude +43.6140938 GPS latitude for the ending of the curvature feature (decimal value precise to the nearest 7th decimal place)

EndLongitude -83.9472427 GPS longitude for the ending of the curvature feature (decimal value precise to the nearest 7th decimal place)

AlignFeatureType Ind Curve Populate with either “angle point”, “independent curve”, “component of compound curve”, “component of reverse curve”, or “tangent section”

Radius (ft.) 7202 Radius of curve (integer value)

Degree 2.50 Degree of curvature (per 100-ft chord length) (decimal value precise to nearest 0.01 degree)

Length (ft.) 1820 Length of feature (integer value)

MaxSuperElev (+/- %)

6.8 Maximum transverse grade of survey lane pavement surface (measured left-to-right while facing direction of collection travel) measured within length of curve (decimal value precise to nearest 0.1 %)

SpiralTrans N Existence of spiral transitions between entrance/exit tangents and curve (value = Y or N)

Deflection Angle 25.6 Alignment deflection measured in degrees (positive decimal value precise to nearest 0.1 degree)

Deflection Direction

L Feature’s alignment deflection with respect to direction of travel (value = “L” for Left or “R”)

**Note: The date/time reported across multiple 0.1-mile records within a LocID shall be the

same; listing only the starting time of the LocID’s collection.


ATTACHMENT G

MDOT

PAVEMENT CONDITION DATA

SYSTEM

DISTRESS SURVEY MANUAL

FOR SURVEYING

OF

PAVEMENT SURFACES

(2018 - 2021 Data Collection)

Detailed Pavement Surface Condition Data Unit

Data Collection & Reporting Section

Bureau of Transportation Planning

(November, 2017)


This document contains the Michigan Department of Transportation’s (MDOT’s) surface distress

type definitions and their associated description methods to be utilized by the Vendor. The pavement

surface distresses defined in this document shall be observed/detected and recorded by type, extent, and

severity (as described herein) via the Vendor’s technology-based process. These data are called Distress

Survey Data.

The Vendor shall classify surface distresses into two categories: primary and secondary distresses.

Throughout this document, a primary distress is called a Principal Distress. For most of the Principal

Distresses, the secondary distresses around a Principal Distress shall also be observed/detected and

recorded in addition to the Principal Distress. The secondary distresses are called the Associated

Distresses of a Principal Distress and are usually measured by the length and width of their surface area.

The Associated Distresses are used to estimate the severity level and/or extent of a Principal Distress.

Associated Distress Type (AD Type) shall also be recorded in certain instances.

The following abbreviations are used throughout this document:

MDOT: Michigan Department of Transportation

PD : Principal Distress

PDs : Principal Distresses

AD : Associated Distress

ADs : Associated Distresses

This document provides a list of PDs that shall be recorded by the Vendor for MDOT. For each PD, the

following items are defined:

1. Title And Code

Each PD has a title and a unique 4-digit code. As an example, Partial Width Patch (w) designates

the title of a PD that is assigned with a code 0326. Throughout this document, the notation

PD<code #> designates a PD identified by code <code #>. For the above example, PD0326

designates Partial Width Patch (w).

2. Definition

This defines the properties or qualifications of a PD.

3. Survey

This defines the method that shall be used by the Vendor to record a PD’s occurrence.


4. Severity / Extent

This defines the criteria for estimating the severity and extent of a PD. Extent usually is the

width of a distress area in the transverse direction (across the survey lane) and can be

considered as a severity level of a PD. Thus, severity and extent are often interchangeable.

(For a longitudinal-oriented PD, however, the extent in the longitudinal direction – along the

roadway - is the PD’s length. This length shall be computed from the Vendor’s location- and

linear-referencing technologies.)

5. Associated Distress Matrix (AD1 & AD2)

This defines which ADs of a PD shall be recorded by the Vendor.

Each PD can have up to two ADs that are used to measure the severity level and extent of the

PD. An AD consists of a title and several items for measuring PD severity (or extent). As an

example, the two ADs of PD0326 are presented and described here:

The First AD of PD0326 - Partial Width Patch (W) – AD1:

This AD1 is shown below in table format. The title of this AD is WIDTH, shown as

the table header. This AD has 5 rows, each is the range of patch width in the transverse

direction (across the survey lane). Thus, this AD measures the extent of this PD in the

transverse direction. However, the extent in the longitudinal direction can be also

considered as severity of this PD because it also contributes to the definition of the

distress area boundary.

WIDTH (Across Lane)

0 - 2 ft. (AD1=1)

> 2 - 4 ft. (AD1=2)

> 4 - 6 ft. (AD1=3)

> 6 - 8 ft. (AD1=4)

> 8 - < 12 ft. (AD1=5)

The Second AD of PD0326 – AD2:

This AD2 is shown below in table format. The title of this AD is CONDITION, shown

as the table header. This AD has 3 rows; each is a condition rating of the pavement within a

partial-width patch.


CONDITION

GOOD (AD2=1)

FAIR (AD2=2)

POOR (AD2=3)

The above two ADs of PD0326 are combined into the following 2-dimensional table:

CONDITION (AD2)

WIDTH Across Lane (AD1) GOOD FAIR POOR

0 - 2 ft. (1,1) (1,2) (1,3)

>2 - 4 ft. (2,1) (2,2) (2,3)

>4 - 6 ft. (3,1) (3,2) (3,3)

>6 - 8 ft. (4,1) (4,2) (4,3)

>8 < 12 ft. (5,1) (5,2) (5,3)

The above 2-dimensional table is referred to as the AD Matrix of PD0326. When a Partial

Width Patch (w) is identified, the Vendor’s survey process must determine to which cell of the above

AD Matrix the associated distresses belongs. The Code of this PD along with the row (AD1) and

column (AD2) numbers of the identified cell shall be recorded in the Vendor’s submitted distress

survey data file. (For data file format, see both the last section of this document entitled “Format

Layout of Condition-Specific Data within a Distress Survey File” and the separate document, File

Formats of Location Referencing, Distress, and Sensor Data) As an example, for a Partial Width

Patch (w) that is 5 feet wide (in the transverse direction) and is in fair condition, 0326 is recorded as

PD and (3 , 2) is recorded as its associated distresses (AD1,AD2). As mentioned previously, the extent

of this PD in the longitudinal direction is the linear referencing length enclosing this PD and, therefore,

is not part of the AD Matrix. The above AD-recording explanation is applied to any PD that has a 2-

dimensional AD Matrix.

Not every PD has two ADs. As an example, PD0341 (Delaminated Area) has only one AD as

shown below in its AD Matrix:

MAXIMUM WIDTH (Across Lane)

>0 - 2 ft. (AD1=1; AD2= -1)

>2 - 3 ft. (AD1=2; AD2= -1)

>3 - 6 ft. (AD1=3; AD2= -1)

>6 - 8 ft. (AD1=4; AD2= -1)

>8 - 12 ft. (AD1=5; AD2= -1)

This AD Matrix measures the extent (and in this case, therefore, also severity) of this PD as the


MAXIMUM WIDTH (across the survey lane), which is shown as the matrix title.

When a Delaminated area is identified, the Vendor’s survey process must determine to which

cell of the above AD Matrix the associated distress belongs. The Code of this PD along with

the row (AD1) number of the identified cell is recorded into a data file. As an example, for a

Delaminated area that can be enclosed by a rectangle of width 7 feet in the transverse

direction, 0341 is recorded as the PD<code #> and (4, -1) is recorded as its associated distress.

The number -1 is used as the value for AD2, indicating that for this PD, AD2 does not apply.

The above explanations are applied to any PD that has only one AD.

Some PDs do not have an AD. As an example, PD0405 (Raveling) is to have 0405 recorded as

its PD<code #> and (-1, -1) recorded as its associated distress. (-1,-1) means that both AD1

and AD2 do not apply for this PD. The above explanations are applied to any PD that does not

have an AD.

6. ASSOCIATED DISTRESS TYPE (AD3)

Some PDs require that a corresponding associated distress type be recorded. Similar to AD1

and AD2 matrices, MDOT’s system has three distinct AD Type Tables (displayed below and

identified by unique code numbers – referenced later in this document) with each containing

multiple AD Type descriptions from which a single one shall be selected/recorded per each

applicable PD.

AD 0083:

ASSOCIATED DISTRESS TYPE (AD3)

Punch-Out Area (AD3 = 1)

None of Above (AD3 = 2)

AD 0082:


Associated Cracking (AD3 = 1)

Irregular Surface (AD3 = 2)



AD 0081:


D-Cracking (AD3 = 1)

Map Cracking (AD3 = 2)

Spalled (AD3 = 3)

High Steel (AD3 = 4)

Punch-Out (AD3 = 5)

Corner Crack (AD3 = 6)

Delamination (AD3 = 7)


If AD Type identification is required for a PD, the Vendor’s survey process shall utilize the

appropriate AD Type Table above (as specified per each PD’s definition later in this document)

and determine the proper cell of the Table to which the observed AD Type description belongs.

The row number of the identified cell shall be recorded in the AD Type (AD3) field of the

Vendor’s submitted distress survey data file. When multiple types of AD are observed, the

Vendor’s survey process shall record only the predominant type.

Summary of PD-specific data on each record within the submitted distress survey data file:

(1) MDOT Control Section (CS) or Physical Reference Number (PR) Milepost corresponding to

the beginning of the PD

(2) MDOT Control Section (CS) or Physical Reference Number (PR) Milepost corresponding to the

ending of the PD (for a transverse-oriented PD, this shall be the same as 1 above)

(3) PD Code

(4) Row Number of AD Matrix - AD1 (-1 for not applicable)

(5) Column Number of AD Matrix – AD2 (-1 for not applicable)

(6) Row Number of AD Type Table – AD3 (-1 for not applicable)

(7) FrameID corresponding to the beginning of the PD

(8) FrameID corresponding to the ending of the PD (for a transverse-oriented PD, this shall be

the same as 7 above)


PRINCIPAL & ASSOCIATED DISTRESSES

UNDER THE CURRENT

MDOT SURFACE DISTRESS SURVEY SYSTEM


Table 1 below lists all unique PDs that shall be observed/detected and recorded by the Vendor.

(Individual PD descriptions follow the table.) Table 1 column definitions:

Column 1 : PD Code

Column 2 : PD Title

Column 3 : Applicability of a PD to Rigid Pavement

Column 4 : Applicability of a PD to Flexible Pavement

Column 5 : Applicability of a PD to Composite Pavement

Column 6 : Applicability of a PD to Brick Pavement

Column 7 : Applicability of a PD to Bridge Deck Surfaces

TABLE 1

PRINCIPAL DISTRESSES (PD) PD CODE, PD TITLE, AND APPLICABLE PAVEMENT TYPES

PD

CODE

PD TITLE RIGID

(Jointed &

Unjointed)

FLEX. COMP. BRICK * BRIDGE

DECK **

0106 Transverse Joint - TJ Yes --- --- --- ---

0113 Transverse Crack - TC Yes --- --- --- ---

0208 Longitudinal Joint - Left Yes --- --- --- ---

0232 Longitudinal Crack - LC

(Left WheelPath – WP)

Yes — — --- ---


(Center of Lane)

Yes --- --- --- ---

0230 Longitudinal Crack – LC

(Right WheelPath - WP)

Yes --- --- --- ---

0209 Longitudinal Joint - Right Yes --- --- --- ---

0341 Delaminated Area Yes --- --- --- ---

0342 Map Cracking Yes --- --- --- ---

0343 High Steel Yes --- --- --- ---

0344 Shattered Area Yes --- --- ---

0402 Popouts Yes --- --- --- ---


PD

CODE

PD TITLE RIGID

(Jointed &

Unjointed)

FLEX. COMP. BRICK * BRIDGE

DECK **

0403 Scaling Yes --- --- --- ---

0103 Transverse Crack - TC

(Straight)

— Yes --- --- ---

0104 Transverse Crack - TC

(Irregular)

— Yes --- --- ---

0234 Alligator Cracking - Right WP --- Yes --- --- ---

0235 Alligator Cracking – Left WP --- Yes --- --- ---

0345 Block Cracking --- Yes --- --- ---

0114 Transverse Tear — Yes Yes --- ---


(Left Edge)

--- Yes Yes --- ---


(Left WheelPath - WP)

--- Yes Yes --- ---


(Center of Lane)

--- Yes Yes --- ---


(Right WheelPath - WP)

--- Yes Yes --- ---


(Right Edge)

--- Yes Yes --- ---

0405 Raveling --- Yes Yes --- ---

0406 Flushing --- Yes Yes --- ---

0110 Transverse Crack - TC --- --- Yes --- ---

0346 Reflective Shattered Area --- --- Yes --- ---

0326 Partial-Width Patch (White) Yes Yes Yes --- ---

0327 Partial-Width Patch (Black) Yes Yes Yes --- ---

0501 No-Distress Area Yes Yes Yes --- Yes

0908 * Not Surveyed Yes Yes Yes Yes ---

* The Vendor shall place a PD Code 0908 (Not Surveyed) within the finally submitted distress

survey data for locations specified within the weekly MDOT-provided Outstanding Collection

Issues reports and for brick pavement locations encountered during the survey process.

** The Vendor shall place a PD Code 0501 (No-Distress Area) within the finally submitted distress

survey data for all bridge deck surfaces encountered during the survey process.


TRANSVERSE JOINT - PD0106 (Jointed & Unjointed Rigid Pavements)

DEFINITION:

A Transverse Joint (TJ) is a regularly spaced saw cut across the slab width.

Typical spacings between two Transverse Joints are 12 - 16, 27, 41, 70, or 100 feet.

SURVEY:

A TJ that has no associated distress shall not be recorded.

Record every observable TJ that has associated distress unless the pavement location can be

identified as a Shattered Area (PD0344). In the case of intersecting transverse and longitudinal

cracks and/or joints, an area of associated distress identified with either the longitudinal or

transverse PD shall be recorded for only one of those PDs per location.

SEVERITY / EXTENT:

The severity of a Transverse Joint is estimated by Transverse Length (total accumulated length

along joint alignment where associated distress observed), and Maximum Width (at any single

location along joint alignment) of the associated distresses that occurs within 4 feet of the joint.

ASSOCIATED DISTRESS MATRIX (AD1,AD2): AD12 0001 x 0011

M A X I M U M W I D T H (Perpendicular to Transvers Joint) (AD2)

TRANSVERSE LENGTH

Across Lane (AD1)

No Distress >0 - 1 ft. >1 - 3 ft. >3 - 6 ft. >6 - 8 ft.

No Distress xxxxxxxx xxxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

>0 - 1 ft. xxxxxxxx (2,2) (2,3)

(2,4) (2,5)

>1 - 3 ft. xxxxxxxx (3,2) (3,3) (3,4) (3,5)

>3 - 6 ft. xxxxxxxx (4,2) (4,3) (4,4) (4,5)

>6 - 12 ft. xxxxxxxx (5,2) (5,3) (5,4) (5,5)

Note that cells marked with xxxxx are not applicable.

ASSOCIATED DISTRESS TYPE (AD3): Use Table AD0081 located previously in this Manual.


TRANSVERSE TEAR - PD0114 (Flexible & Composite Pavements)

DEFINITION:

A Transverse Tear is a transverse-oriented short crack (4” to ½ of lane width) that appears in any location across the survey lane.

Note that any such short crack shall not be recorded as a Transverse Tear if it can be claimed as

AD of other PDs such as TC, LC, Alligator Crack, and Block Cracking for flexible pavement or

TC, LC, and Reflective Shattered Area for composite pavement.

SURVEY:

A Transverse Tear PD shall be recorded at locations where the above definition and constraints are observed. For a given mile point location (0.001 mile), if multiple unconnected Transverse

Tears are present across the lane width (without presence of other PDs listed above), there shall

be only one Transverse Tear record made for the mile point location.

SEVERITY / EXTENT: None

ASSOCIATED DISTRESS MATRIX (AD1,AD2): None (AD1 = -1; AD2 = -1)

ASSOCIATED DISTRESS TYPE (AD3): None (AD3 = -1)


TRANSVERSE CRACK (TC) - PD0113 (Jointed & Unjointed Rigid Pavement)

TRANSVERSE CRACK (TC) - PD0110 (Composite Pavement) DEFINITION:

TC stands for a Transverse Crack that meets the following criteria:

(1) It extends more in the transverse direction than the longitudinal direction. That is, the angle

between the overall crack line and the transverse line is less than 45 degrees. (2) It is visible for at least one half of the lane width.

SURVEY:

Record every observable TC unless the pavement location can be identified as a Shattered Area (PD0344) for all rigid pavement or Refl. Shattered Area (PD0346) for composite pavement.

SEVERITY / EXTENT: The severity of a TC is estimated by Transverse Length (total accumulated length along crack alignment where associated distress observed), and Maximum Width (at any single location along

crack alignment) of the associated distresses that occur within 4 feet of the TC. In the case of intersecting transverse and longitudinal cracks and/or joints, an area of associated distress identified with either the longitudinal or transverse PD shall be recorded for only one of those PDs per

location. For a clean TC with sealant present, “No Distress - Seal (open)” shall be recorded when sealant present for less than 50% of the TC length.


M A X I M U M W I D T H (Perpendicular to Transverse Crack) (AD2)

TRANSVERSE LENGTH

Across Lane (AD1)

No Assoc.

Distress

>0 - 1 ft. >1 – 3 ft. >3 – 6 ft. >6 – 8 ft.

No Assoc. Distress – No Seal (1,1) xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

No Assoc. Distress – Seal (full) (2,1)

xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

No Assoc. Distress – Seal (part) (3,1) xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

No Assoc.Distress– Seal (open) (4,1) xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

>0 - 1 ft. xxxxxxxx (5,2) (5,3) (5,4) (5,5)

>1 - 3 ft. xxxxxxxx (6,2) (6,3) (6,4) (6,5)

>3 - 6 ft. xxxxxxxx (7,2) (7,3) (7,4) (7,5)

>6 - 12 ft. xxxxxxxx (8,2) (8,3) (8,4) (8,5)


ASSOCIATED DISTRESS TYPE (AD3): For PD0113 (Jointed & Unjointed Rigid pavement), use Table AD0081 located previously in this Manual;

For PD0110 (Composite pavement), AD3 does not apply (AD3= -1)


TRANSVERSE CRACK (TC) - STRAIGHT - PD0103 TRANSVERSE CRACK (TC) - IRREGULAR - PD0104

(Flexible Pavement)

DEFINITION:

TC stands for a Transverse Crack that meets the following criteria:

(1) It extends more in the transverse direction than the longitudinal direction. That is, the

angle between the overall crack line and the transverse line is less than 45 degrees. (2) It must be visible for at least ½ of the lane width. (3) For TC (straight), crack must be straight for entire length and not change direction.

For TC (irregular), crack must change direction as it progresses across the lane.

SURVEY:

Record every observable TC unless the pavement area can be identified as a Block Cracking (PD0345).

SEVERITY / EXTENT:

The severity of a TC is estimated by Transverse Length (total accumulated length along crack

alignment where associated distress observed), & Maximum Width (at any single location along crack alignment) of the ADs that occur within 2 feet of the TC. In the case of intersecting transverse and longitudinal cracks and/or joints, an area of associated distress identified with either

the longitudinal or transverse PD shall be recorded for only one of those PDs per location.


MAXIMUM WIDTH (Perpendicular To Transverse Crack) (AD2)

TRANSVERSE LENGTH

Across Lane (AD1)

No Assoc.

Distress

>0 - 1 ft. >1 – 2 ft. >2 – 4 ft.

No Assoc. Distress – No Seal (1,1) xxxxxxxx xxxxxxxx xxxxxxxx

No Assoc. Distress – Seal (full) (2,1) xxxxxxxx xxxxxxxx xxxxxxxx

No Assoc. Distress – Seal (part) (3,1) xxxxxxxx xxxxxxxx xxxxxxxx

No Assoc. Distress – Seal (open) (4,1) xxxxxxxx xxxxxxxx xxxxxxxx

>0 - 1 ft. xxxxxxxx (5,2) (5,3) (5,4)

>1 - 3 ft. xxxxxxxx (6,2) (6,3) (6,4)

>3 - 6 ft. xxxxxxxx (7,2) (7,3) (7,4)

>6 - 12 ft. xxxxxxxx (8,2) (8,3) (8,4)




LONGITUDINAL JOINT (LC) - RIGHT - PD0209

LONGITUDINAL JOINT (LC) - LEFT - PD0208 (Jointed & Unjointed Rigid Pavements)

DEFINITION:

L. JOINT stands for Longitudinal Joint. The above two PDs are the right and left Longitudinal Joints, respectively, of the survey lane.

A Longitudinal Joint is the sawed or formed joint between two lanes or between the pavement

lane and shoulder.

SURVEY: A Longitudinal Joint that has no associated distress shall not be recorded.

Record every observable Longitudinal Joint that has associated distress unless the pavement area

can be identified as a Shattered Area (PD0344).

Minimum recorded length shall be 0.001 miles (absolute value of begin milepoint – end milepoint)

SEVERITY / EXTENT: The severity of a Longitudinal Joint is estimated by Maximum Width (at any single location

along joint alignment) of the associated distresses that occur within 2 feet (either side) of the joint. In the case of intersecting transverse and longitudinal cracks and/or joints, an area of associated distress identified with either the longitudinal or transverse PD shall be recorded for only one of

those PDs per location.

ASSOCIATED DISTRESS MATRIX (AD1): AD1 0012

MAXIMUM WIDTH (Perpendicular to Longitudinal Joint)

If No Distress Along Joint, Do Not Record as a PD

>0 - 1 ft. (AD1=2; AD2= -1) (Notice that there is no AD1=1 call (See above row)

>1 - 2 ft. (AD1=3; AD2= -1)

>2 - 4 ft. (AD1=4; AD2= -1)

ASSOCIATED DISTRESS TYPE (AD3) : Use Table AD 0081 located previously in this

Manual.


LONGITUDINAL CRACK (LC) - RIGHT WP - PD0230

LONGITUDINAL CRACK (LC) - CENTER OF LANE - PD0231 LONGITUDINAL CRACK (LC) – LEFT WP - PD0232

(Jointed & Unjointed Rigid Pavement)

DEFINITION:

LC is a Longitudinal Crack. Each of the above PDs is an LC, located laterally across the survey

lane, that meets the following criteria: (1) It extends more in the longitudinal direction than the transverse direction. That is, the angle

between the overall crack line and the paved lane’s edge line is less than 45 degrees.

(2) Any 0.001-mile segment along the lane has at least 50% of its length covered by the distress-

type occurrence.

The center of each wheelpath shall be assumed to be located 34.5 inches from center of the lane.

SURVEY:

Record every observable LC unless pavement location can be identified as a Shattered Area (PD0344). Note that each lateral lane location can have at most one LC recorded for the same

0.001 milepoint.

Special-Case Use of PD0231 for center-of-lane long. joints (thin concrete overlay areas):

Isolated locations of Michigan routes have thin concrete overlay surfaces, wherein a longitudinal

joint has been constructed in the center of the lane. The Vendor shall record deteriorated sections

of such joints as PD0231. Similar to the surveying directions for constructed joints elsewhere in

this Manual, longitudinal joint segments that have no deterioration (no associated distress) shall

not be recorded.


SEVERITY / EXTENT:

The severity of an LC is estimated by Maximum Width (at any single location along crack alignment) of the associated distresses that occur within 2 feet of the LC. In the case of intersecting

transverse and longitudinal cracks and/or joints, an area of associated distress identified with either the longitudinal or transverse PD shall be recorded for only one of those PDs per location.


MAXIMUM WIDTH (Perpendicular to Longitudinal Crack)

No Associated Distress - No Seal (AD1=1;AD2= -1)

No Associated Distress - Seal (full) (AD1=2;AD2= -1)

No Associated Distress - Seal (part) (AD1=3;AD2= -1)

No Associated Distress - Seal (open) (AD1=4;AD2= -1)


>0 - 1 ft. (AD1=5;AD2= -1)

>1 - 2 ft. (AD1=6;AD2= -1)

>2 - 4 ft. (AD1=7;AD2= -1)

ASSOCIATED DISTRESS TYPE (AD3): Use Table AD0081 located previously in this

Manual.


LONGITUDINAL CRACK (LC) - LEFT WP - PD0205 LONGITUDINAL CRACK (LC) - CENTER OF LANE - PD0202

LONGITUDINAL CRACK (LC) - RIGHT WP - PD0204 (Flexible & Composite Pavements)

DEFINITION: LC designates Longitudinal Crack. Each of the above PDs is an LC, located laterally across the survey lane, that meets the following criteria: (1) It extends more longitudinally than transversely. That is, the angle between the overall crack

line and the paved lane’s edge line is less than 45 degrees.

(2) Any 0.001-mile segment along the lane has at least 50% of its length covered by the distress-

type occurrence.

The center of each wheelpath shall be assumed to be located 34.5 inches from the center of the

lane.

SURVEY: Record every observable LC unless the pavement location can be identified as Block Cracking

(PD0345) for flexible pavement or Refl. Shattered Area (PD0346) for composite pavement. Each

lane location (either wheelpath -WP or center) can have at most one LC recorded for the same

0.001 milepoint.


SEVERITY / EXTENT: The severity of an LC is estimated by Maximum Width (at any single location along crack alignment) of the associated distresses that occur within 2 feet (either side) of the LC. In the case of

intersecting transverse and longitudinal cracks and/or joints, an area of associated distress identified with either the longitudinal or transverse PD shall be recorded for only one of those PDs per location.


MAXIMUM WIDTH (Perpendicular to Longitudinal Crack)

No Associated Distress - No Seal (AD1=1;AD2= -1)

No Associated Distress - Seal (full) (AD1=2;AD2= -1)

No Associated Distress - Seal (part) (AD1=3;AD2= -1)

No Associated Distress - Seal (open) (AD1=4;AD2= -1)

>0 - 1 ft. (AD1=5;AD2= -1)

>1 - 2 ft. (AD1=6;AD2= -1)

>2 - 4 ft. (AD1=7;AD2= -1)



LONGITUDINAL CRACK (LC) - LEFT EDGE - PD0236

LONGITUDINAL CRACK (LC) - RIGHT EDGE - PD0237 (Flexible & Composite Pavements)

DEFINITION:

LC designates Longitudinal Crack. Each of the above PDs is an LC, located laterally across the survey lane, that meets the following criteria:

(1) It extends more longitudinally than transversely. That is, the angle between the overall crack line and the paved lane’s edge line is less than 45 degrees.

(2) Any 0.001-mile segment along the lane has at least 50% of its length covered by the

distress-type occurrence.

SURVEY:

An LC (left edge) or LC (right edge) with no associated distress shall not be recorded. These

are predominantly paving seams appearing as cracks, but are not to be recorded until deterioration

occurs along such (indicating it is becoming an actual crack).

Record every observable LC unless the pavement location can be identified as Block Cracking

(PD0345) for flexible pavement or Refl. Shattered Area (PD0346) for composite pavement. Each

lane location (either edge) can have at most one LC recorded for the same 0.001 milepoint.

Minimum recorded length shall be 0.001 miles (absolute value of begin MP – end MP)

SEVERITY / EXTENT:

Severity of an LC is estimated by Maximum Width (at any single location along crack alignment)

of the associated distresses that occur within 2 feet (either side) of the LC. In the case of intersecting transverse and longitudinal cracks and/or joints, an area of associated distress identified with either the longitudinal or transverse PD shall be recorded for only one of those PDs per location.


MAXIMUM WIDTH Perpendicular to Longitudinal Crack

Do Not Record as a PD until these (predominantly paving seams) begin to deteriorate into actual long. cracks.

>0 to 1 ft. (AD1=1;AD2= -1)

>1 to 2 ft. (AD1=2;AD2= -1)

>2 to 4 ft. (AD1=3;AD2= -1)



ALLIGATOR CRACKING (Right WP) - PD0234

ALLIGATOR CRACKING (Left WP) - PD0235 (Flexible Pavement)

DEFINITION:

Alligator Cracking is two or more parallel longitudinal cracks (originating in a wheel path – WP)

with transverse tears running between them, displaying a pattern similar to an alligator hide. The

center of each wheelpath shall be assumed to be located 34.5 inches from the center of the

lane. Alligator Cracking may extend laterally to other lane locations as severity increases.

SURVEY:

An Alligator Cracking PD shall be recorded individually per wheelpath when the defined

condition covers at least 50% of the length of any 0.001-mile segment along the wheelpath unless

the location meets the condition definition for Block Cracking (PD0345). Each lane location

(across the lane) may have at most one LC or Alligator Cracking record for the same 0.001

milepoint.

Minimum recorded length shall be 0.001 miles (absolute value of begin milepoint – end

milepoint)

SEVERITY / EXTENT:

The severity of Alligator Cracking is estimated by the Maximum Width (at any single location along cracking alignment) of all combined associated distresses occurring within 2 feet from the outermost of the parallel longitudinal cracks. Therefore, Maximum Width shall be at least the

lateral distance between the two outermost longitudinal cracks (if all visible associated distresses are contained between them).


MAXIMUM WIDTH (Perpendicular to the Longitudinal Alligator Cracking)

>0 - 2 ft. (AD1=1;AD2= -1)

> 2 - 4 ft. (AD1=2;AD2= -1)

> 4 - 6 ft. (AD1=3;AD2= -1)



DELAMINATED AREA – PD 0341 MAP CRACKING – PD 0342

HIGH STEEL – PD 0343 (Jointed & Unjointed Rigid Pavement)

DEFINITION: A Delaminated Area has partial-depth pieces of concrete broken out from the surface (usually beginning with circular-shaped edges) and may reach down to the reinforcing steel.

A Map Cracking area is typically one with a honeycomb pattern of very tight, intensely

crisscrossing short (0.5 - 1.0 ft) cracks.

A High Steel area has either missing concrete in the pattern of the reinforcing steel grid or

actually visible bare steel at the surface (typically accompanied by rust stains).

The above PDs shall not be recorded at a given location if some other PD is observed.

That is, if there is another observed PD at the same location, the location shall be recorded

as that other PD, and the observed delaminated area, map cracked area, or high steel area

shall instead be used to define AD extent & AD Type (if required) of the other PD.

SURVEY:

A pavement location shall be recorded as a Delaminated, Map Cracking, or High Steel

Area when the respective definitions above are observed (and no other PDs are present).

The Vendor’s survey process shall review an adequate amount of pavement length in

order to properly identify these distress types.

Minimum recorded length shall be 0.001 miles (absolute value of begin milepoint –

end milepoint)

SEVERITY / EXTENT:

Recorded as the Maximum Width (measured across the lane) of the qualified area.

ASSOCIATED DISTRESS MATRIX (AD1): AD1??? (Undefined yet for internal use)

MAXIMUM WIDTH (Across Lane)

>0 - 2 ft. (AD1=1;AD2= -1)

>2 - 3 ft. (AD1=2;AD2= -1)

>3 - 6 ft. (AD1=3;AD2= -1)

>6 - 8 ft. (AD1=4;AD2= -1)

>8 - 12 ft. (AD1=5;AD2= -1)



SHATTERED AREA - PD0344 (Jointed & Unjointed Rigid Pavements)

DEFINITION:

A Shattered Area typically has a pattern of diagonal and/or looping cracks which may intersect some or all transverse joints/cracks and longitudinal joints/cracks. Typically this distress is caused

by a lack of sub-grade support, and is characterized by a broken pattern of multiple individual

pavement pieces which may be depressed in relation to the surrounding pavement surface.

SURVEY:

A Shattered Area shall be recorded if observation of the pavement location meets the above definition.

The Vendor’s survey process shall review an adequate amount of pavement length in order to

properly identify this distress type.

No other PD shall be recorded at the same pavement location as an identified Shattered Area.


milepoint)


ASSOCIATED DISTRESS MATRIX (AD1, AD2): None (AD1 = -1; AD2 = -1)

ASSOCIATED DISTRESS TYPE (AD3): Use Table AD0083 located previously in this Manual.


BLOCK CRACKING - PD0345 (Flexible Pavement)

DEFINITION: A Block Cracking area is where transverse and longitudinal cracking have progressed to a point

where at least 6 individual blocks (each less than 12' by 12' in size) are visible. The shape of each

block may be irregular because of the form of the initial transverse cracking and later-induced

longitudinal cracking.

SURVEY:

The Vendor’s survey process shall review an adequate amount of pavement length in order

to properly identify this distress type.

No other PD shall be recorded at the same pavement location identified as Block Cracking.


milepoint)

SEVERITY: None

ASSOCIATED DISTRESS MATRIX (AD1,AD2): None (AD1 = -1; AD2 = -1)



REFLECTIVE SHATTERED AREA - PD0346 (Composite Pavement)

DEFINITION:

A Reflective Shattered Area consists of observed cracking in the asphalt surface that reflects a

deteriorated area in the underlying concrete pavement. This area has a pattern ranging from small

"Y" shaped tears to larger diagonal and/or looping cracks that outline large broken pieces.

SURVEY:

The Vendor’s survey process shall review an adequate amount of pavement length in order

to properly identify this distress type.

No other PD shall be recorded at the same pavement location identified as a Reflective

Shattered Area.


milepoint)





POPOUTS - PD0402 (Jointed & Unjointed Rigid Pavements)

DEFINITION:

A Popout is a void in the pavement surface caused by soft material or aggregate absorbing water and then “popping” out of the concrete upon freezing. Popouts are typically less than 2” in

diameter and resemble a small bowl-shaped depression or crater in the pavement surface.

SURVEY:

A Popouts PD shall be recorded when an observed pavement location’s average number of Popouts per linear foot (along the survey lane alignment) is at least 1.

Other observed PDs are to be recorded regardless of the presence of Popouts.






SCALING - PD0403 (Jonted & Unjointed Rigid Pavements)

DEFINITION:

A Scaling area is where the top (smooth-finish) layer of concrete is separated and displaced from the inner aggregate, leaving aggregate exposed and creating a rough surface texture.

In general, Scaling is caused by exposure, wear, over-finishing, or too much water in the mix.

SURVEY:

A Scaling PD shall be recorded when at least 50% of the survey lane width is covered by the

condition stated in the above definition.

Other observed PDs are to be recorded regardless of the presence of Scaling.


milepoint)





RAVELING - PD0405 (Flexible & Composite Pavements)

DEFINITION:

A Raveling area is where the original smooth surface has partially or entirely eroded away in more areas than just the wheelpaths, leaving the inner aggregate of the bituminous mixture exposed and creating a rough surface texture.

Raveling may be caused by low asphalt content, mix segregation, or improper placement

technique.

SURVEY:

A Raveling PD shall be recorded when the condition described above covers at least 50% of the survey lane width.

Other observed PDs are to be recorded regardless of the presence of Raveling.






FLUSHING - PD0406 (Flexible & Composite Pavements)

DEFINITION:

A Flushing area is where the pavement is noticeably darker due to asphalt cement being squeezed to the top of the pavement mixture and deposited on the surface. It usually occurs in the

wheel paths and may appear shiny in the perspective view.

Flushing may result from too high an asphalt content for the mixture’s void volume.

SURVEY:

A Flushing PD shall be recorded when at least 50% of the survey lane width meets the above

definition.

Other observed PDs are to be recorded regardless of the presence of Flushing.


milepoint)





PARTIAL WIDTH PATCH (w) - PD 0326

PARTIAL WIDTH PATCH (b) - PD 0327 (All Pavement Types)

DEFINITION:

The (w) and (b) above stand for white patch (concrete) and black patch (asphalt), respectively.

A Partial Width Patch is a repaired section where the original pavement has been removed and

replaced.

A Partial Width Patch can have any width (transversely measured - across the survey lane)

up to, but not equal to, the full lane width, and can have any length greater than or equal to

0.001 miles in longitudinal direction. FULL-LANE-WIDTH PATCHES AND BRIDGE

APPROACH SLABS SHALL NOT BE IDENTIFIED/RECORDED.

Utility access holes with patching around them and pavement coring holes shall be

considered as Partial Width Patches.

Traffic signal detection loop (sealed) cuts shall not be considered Partial Width Patches

(but as other cracking PDs based upon observed deterioration if present).

SURVEY: A Partial Width Patch PD shall be recorded when a pavement location meets the conditions defined above, with the following exception:

If there is another PD crossing through the patch area, the patch shall not be recorded as a

Partial Width Patch but, instead, the distresses located within and around the patch shall be

treated as AD of the other PD.

Otherwise, the distresses within a Partial Width Patch shall exclusively be used to estimate and

record its condition (Good, Fair, or Poor) as defined further below.


milepoint)

SEVERITY / EXTENT:

The extent of a Partial Width Patch is its Width (dimension in the transverse direction across the

lane) of the patch itself.


PARTIAL WIDTH PATCH (w) - PD 0326, Con’t.

PARTIAL WIDTH PATCH (b) - PD 0327, Con’t. (All Pavement Types)

SEVERITY / EXTENT: continued

The pavement condition (Good, Fair, or Poor) of a Partial Width Patch shall be rated as

follows:

GOOD: the patch is unbroken and contains distress occurring at a rate less than 3 ft. per each

10 ft. of its length.

FAIR: the patch is moderately broken into pieces by open cracks or contains distress

occurring at a rate of 3 – 6 ft. per each 10 ft. of its length.

POOR: the patch is open or significantly broken into several pieces by open cracks or

contains distress occurring at a rate greater than 6 ft. per each 10 ft. of its length.

ASSOCIATED DISTRESS MATRIX (AD1, AD2): (unspecified yet for internal use)

CONDITION (AD2)

WIDTH Across Lane (AD1) GOOD FAIR POOR

>0 - 2 ft. (1, 1) (1,2) (1,3)

>2 - 4 ft. (2,1) (2,2) (2,3)

>4 - 6 ft. (3,1) (3,2) (3,3)

>6 - 8 ft. (4,1) (4,2) (4,3)

>8 - <12 ft. (5,1) (5,2) (5,3)



NOT SURVEYED - PD0908 (All Pavements)

DEFINITION:

A pavement section that shall not be surveyed due to construction, detouring, brick surface, etc.

SURVEY:

Consecutive, uninterrupted pavement locations that are identified as NOT SURVEYED areas

shall be combined and recorded as one continuous NOT SURVEYED area.

Other PDs shall not be recorded in NOT SURVEYED areas.


milepoint)





NO DISTRESS - PD0501 (All Pavements)

DEFINITION:

A pavement section that has no observable distress as defined in this Manual shall be recorded as a NO DISTRESS area. Bridge decks shall also be recorded as NO DISTRESS areas.

SURVEY:


milepoint)





INCOMPATIBLE

PRIMARY DISTRESS RECORDINGS

AT

THE SAME MILE POINT LOCATION In addition to the description within this document’s previous section of constraints on simultaneous

recording of multiple PDs at the same location, the following is a listing of PD incompatibilities at any

given linear referencing mile point (0.001 mile) within the distress survey data.

Subject

PD

Code

PD Codes That Cannot Be Additionally Recorded

At The Same Mile Point Range As the Subject PD Code

0103 0106,0110,0113,0208,0209,0230,0231,0232,0341,0342,0343,0344,0345,0346,0402,

0403,0501,0908

0104 0106,0110,0113,0208,0209,0230,0231,0232,0341,0342,0343,0344,0345,0346,0402,

0403,0501,0908

0106 0103,0104,0106,0110,0113,0114,0236, 0202,0237, 0204,0205,0234,0235,0341,0342, 0343,0344,0345,0346,0405,0406,0501,0908

0110 0103,0104,0106,0113,0208,0209,0234,0235,0230,0231,0232,0341,0342,0343,0344, 0345,0346,0402,0403,0501,0908

0113 0103,0104,0106,0110,0114,0236, 0202,0237, 0204,0205,0234,0235,0341,0342,0343,

0344,0345,0346,0405,0406,0501,0908

0114 0106,0113,0114, 0208,0209,0230,0231,0232,0341,0342,0343,0344,0345,0346,0402, 0403, 0501,0908

0236 0106,0113,0236, 0208,0209,0230,0231,0232,0341,0342,0343,0344,0345,0346,0402, 0403,0501,0908


Subject

PD

Code


At The Same Mile Point Range As Subject PD Code

0202 0106,0113,0202,0208,0209,0230,0231,0232,0341,0342,0343,0344,0345,0346,0402,

0403,0501,0908

0237 0106,0113,0237, 0208,0209,0230,0231,0232,0341,0342,0343,0344,0345,0346,0402, 0403,0501,0908

0204 0106,0113,0204,0208,0209,0234,0230,0231,0232,0341,0342,0343,0344,0345,0346, 0402,0403,0501,0908

0205 0106,0113,0205,0208,0209,0235,0230,0231,0232,0341,0342,0343,0344,0345,0346,040

2,0403,0501,0908

0208 0103,0104,0110,0114,0236, 0202,0237, 0204,0205,0208,0234,0235,0344,0345,0346,

0405,0406,0501,0908

0209 0103,0104,0110,0114,0236, 0202,0237, 0204,0205,0209,0234,0235,0344,0345,0346, 0405,0406,0501,0908

0234 0106,0110,0113,0204,0208,0209,0234,0230,0231,0232,0341,0342,0343,0344,0345, 0346,0402,0403,0501,0908

0235 0106,0110,0113,0205,0208,0209,0235,0230,0231,0232,0341,0342,0343,0344,0345,

0346,0402,0403,0501,0908

0230 0103,0104,0110,0114,0236, 0202,0237, 0204,0205,0234,0235,0230,0344,0345,0346,

0405,0406,0501,0908

0231 0103,0104,0110,0114,0236, 0202,0237, 0204,0205,0234,0235,0231,0344,0345,0346, 0405,0406,0501,0908

0232 0103,0104,0110,0114,0236, 0202,0237, 0204,0205,0234,0235,0232,0344,0345,0346,

0405,0406,0501,0908

0326 0344,0345,0346,0501,0908

0327 0344,0345,0346,0501,0908

0341 0103,0104,0106,0110,0113,0114,0236, 0202,0237, 0204,0205,0234,0235,0344,0345, 0346,0405,0406,0501,0908

0342 0103,0104,0106,0110,0113,0114,0236, 0202,0237, 0204,0205,0234,0235,0344,0345,

0346,0405,0406,0501,0908

0343 0103,0104,0106,0110,0113,0114,0236, 0202,0237, 0204,0205,0234,0235,0344,0345, 0346,0405,0406,0501,0908

0344 0103,0104,0106,0110,0113,0114,0236, 0202,0237, 0204,0205,0208,0209,0234,0235, 0230,0231,0232,0326,0327,0341,0342,0343,0344,0345,0346,0402,0403,0405,0406, 0501,0908


Subject

PD

Code


At The Same Mile Point Range As Subject PD Code

0345 0103,0104,0106,0110,0113,0114,0236, 0202,0237, 0204,0205,0208,0209,0234,0235,

0230,0231,0232,0326,0327,0341,0342,0343,0344,0345,0346,0402,0403,0405,0406, 0501,0908

0346 0103,0104,0106,0110,0113,0114,0236, 0202,0237, 0204,0205,0208,0209,0234,0235, 0230,0231,0232,0326,0327,0341,0342,0343,0344,0345,0346,0402,0403,0405,0406,

0501,0908

0402 0103,0104,0110,0114,0236, 0202,0237, 0204,0205,0234,0235,0344,0345,0346,0402, 0405,0406,0501,0908

0403 0103,0104,0110,0114,0236, 0202,0237, 0204,0205,0234,0235,0344,0345,0346,0403,

0405,0406,0501,0908

0405 0106,0113,0208,0209,0230,0231,0232,0341,0342,0343,0344,0345,0346,0402,0403,

0405,0406,0501,0908

0406 0106,0113,0208,0209,0230,0231,0232,0341,0342,0343,0344,0345,0346,0402,0403, 0405,0406,0501,0908

0501 0103,0104,0106,0110,0113,0114,0236, 0202,0237, 0204,0205,0208,0209,0234,0235, 0230,0231,0232,0326,0327,0341,0342,0343,0344,0345,0346,0402,0403,0405,0406,

0501,0908

0908 0103,0104,0106,0110,0113,0114,0236,0202,0237,0204,0205,0208,0209,0234,0235, 0230,0231,0232,0326,0327,0341,0342,0343,0344,0345,0346,0402,0403,0405,0406,

0501,0908


FORMAT LAYOUT

OF

CONDITION - SPECIFIC DATA

WITHIN A

DISTRESS SURVEY FILE


The format of records in a detailed distress survey data file is defined in the MDOT document FILE

FORMATS OF LOCATION REFERENCING, DISTRESS, AND SENSOR DATA (ATTACHMENT

F). Each record has 14 data fields that are separated by commas. This section is devoted to providing the

exact layout of the following portion (Data Fields 9 -14) of a distress condition data record for each PD:

PD_Code (4 characters, including a leading zero):

Code of a principal distress condition.

AD1_SL_Index

AD2_SL_Index (2 characters max each):

Indices of severity level of AD (Associated Distress) These two indices define severity and/or extent of a principal distress (PD) condition

based on the PD’s corresponding Associated Distress matrix.

AD_Type_Index (2 characters max):

This is the index of the associated distress type as applicable per PD.

FID_RECORD_START (6 characters max):

FrameID corresponding to the beginning of the pavement distress condition in this record.

FID_RECORD_END (6 characters max):

FrameID corresponding to the ending of the pavement distress condition in this record.

For transverse-oriented PDs (such as a Transverse Crack or Transverse Joint),

FID_RECORD_START and FID_RECORD_END shall be the same Frame ID.

For longitudinal-oriented PDs (such as a Longitudinal Crack or Block Cracking),

FID_RECORD_END shall have a value greater than the value of FID_RECORD_START.

Data fields 9 - 14 in a distress condition data record shall be of the following form:

<PD_Code>, <AD1_SL_Index>, <AD2_SL_Index>, <AD_Type_Index>,<FID_RECORD_START>, <FID_RECORD_END>

Allowable field values (or value ranges) of the above portion of a distress survey data record for all PDs:


(1) TRANSVERSE JOINT - PD0106

0106, < 2-5>, < 2-5>, <1-8>, <FID_RECORD_START>, <FID_RECORD_END>

(2) TRANSVERSE TEAR - PD0114

0114, -1, -1, -1, <FID_RECORD_START>, <FID_RECORD_END>

(3) TC - PD0113

113, <1-8>, <1-5>, <1-8>, <FID_RECORD_START>, <FID_RECORD_END>

(4) TC - PD0110 for Composite Pavements

110, <1-8>, <1-5>, -1, <FID_RECORD_START>, <FID_RECORD_END>

(5) TC (straight) - PD0103


(6) TC (irregular) - PD0104


(7) L. JOINT (right) - PD0209 , L. JOINT (left ) - PD0208

<209 or 208>, <2 -4>, -1, <1-8>, <FID_RECORD_START>, <FID_RECORD_END>

(8) LC (right WP) - PD0230 , LC (center of lane) - PD0231, LC

(left WP) - PD0232

<230-232>, <1-7>, -1, <1-8>, <FID_RECORD_START>, <FID_RECORD_END>

(9) LC (left edge) - PD0236, LC (left WP ) - PD0205, LC

(center of lane) - PD0202 , LC (right WP) - PD0204, LC

(right edge) - PD0237

<202,204,205>, <1-7>, -1, -1, <FID_RECORD_START>, <FID_RECORD_END>

<236,237>, <1-3>, -1, -1, <FID_RECORD_START>, <FID_RECORD_END>

(10) ALLIGATOR CRACKING (right WP or left WP) - PD0234 or PD0235

<234 or 235>, <1-3>, -1, -1, <FID_RECORD_START>, <FID_RECORD_END>

(11) DELAMINATED AREA - PD0341 , MAP CRACKING - PD0342, HIGH

STEEL - PD0343


<341-343>, <1-5>, -1, -1, <FID_RECORD_START>, <FID_RECORD_END>

(12) SHATTERED AREA - PD0344

344, -1, -1, <1-2>, <FID_RECORD_START>, <FID_RECORD_END>

(13) BLOCK CRACKING - PD0345


(14) REFL. SHATTERED AREA - PD0346


(15) POPOUTS - PD0402


(16) SCALING - PD0403


(17) RAVELING - PD0405


(18) FLUSHING - PD0406


(19) PARTIAL WIDTH PATCH (w) - PD0326

PARTIAL WIDTH PATCH (b) - PD0327

<326 or 327>, <1-5>, <1-3>, -1, <FID_RECORD_START>, <FID_RECORD_END>

(20) NOT SURVEYED - PD0908

NO-DISTRESS AREA - PD0501

<908 or 501>, -1, -1, -1, <FID_RECORD_START>, <FID_RECORD_END>


PROCEDURE FOR

TRANSLATING

DISTRESS-SURVEY PRIMARY DISTRESS TYPE

WHEN

FIELD COLLECTION PAVEMENT TYPE

DOES NOT MATCH

MDOT-DEFINED PAVEMENT TYPE


As described previously in this document, some PD codes are applicable to only certain pavement type(s)

utilized by MDOT for surface distress identification. As MDOT’s distress data management system

requires data generated by the Vendor to contain PDs applicable to the MDOT-defined pavement type for a

given mileage range, MDOT will annually provide the Vendor with pavement type data for routes needing

surveying. For certain locations, however, the MDOT-provided pavement type data could be in error. In

those potential situations, the Vendor shall utilize the following “PD Translation” Table to still ensure its

generated distress survey data file contains only PDs applicable to the MDOT-defined pavement type:

Viewed

Pavement

Type

From

Collection

Observed PD

Code

in

Viewed

Pavement

Type

Observed PD Title

in

Viewed Pavement Type

PD Code

to be Recorded

when MDOT-Defined

Pavement Type =

RIGID

PD Code

to be Recorded

when MDOT-Defined

Pavement Type =

FLEXIBLE

PD Code

to be Recorded

when MDOT-Defined

Pavement Type =

COMPOSITE

Rigid 106 Transverse Joint 106 103 110

Rigid 113 TC 113 103 110

Rigid 208 L. Joint - left 208 236 236

Rigid 209 L. Joint - right 209 237 237

Rigid 230 LC - right WP 230 204 204

Rigid 231 LC - center of lane 231 202 202

Rigid 232 LC - left WP 232 205 205

Rigid 326 Partial Width Patch (W) 326 326 326

Rigid 327 Partial Width Patch (b) 327 327 327

Rigid 341 Delaminated Area 341 405 405

Rigid 342 Map Cracking 342 501 501

Rigid 343 High Steel 343 501 501

Rigid 344 Shattered Area 344 345 346

Rigid 402 Popouts 402 501 501

Rigid 403 Scaling 403 405 405

Rigid 501 No-Distress Area 501 501 501

Rigid 908 Not Surveyed 908 908 908

Flexible 103 TC (straight) 113 103 110

Flexible 104 TC (irregular) 113 104 110

Flexible 114 Transverse Tear 501 114 114

Flexible 236 LC - left edge 208 236 236

Flexible 202 LC - center of lane 231 202 202

Flexible 237 LC - right edge 209 237 237

Flexible 204 LC - right WP 230 204 204

Flexible 205 LC - left WP 232 205 205

Flexible 234 Alligator Crack - right WP 230 234 204

Flexible 235 Alligator Crack - left WP 232 235 205

Flexible 326 Partial Width Patch (W) 326 326 326

Flexible 327 Partial Width Patch (b) 327 327 327

Flexible 345 Block Cracking 344 345 346

Flexible 405 Raveling 403 405 405

Flexible 406 Flushing 501 406 406

Flexible 501 No-Distress Area 501 501 501

Flexible 908 Not Surveyed 908 908 908

Composite 110 TC 113 103 110

Composite 114 Transverse Tear 501 114 114

Composite 236 LC - left edge 208 236 236

Composite 202 LC - center of lane 231 202 202

Composite 237 LC - right edge 209 237 237

Composite 204 LC - right WP 230 204 204

Composite 205 LC - left WP 232 205 205

Composite 326 Partial Width Patch (W) 326 326 326

Composite 327 Partial Width Patch (b) 327 327 327

Composite 346 Refl. Shattered Area 344 345 346

Composite 405 Raveling 403 405 405

Composite 406 Flushing 501 406 406

Composite 501 No-Distress Area 501 501 501

Composite 908 Not Surveyed 908 908 908


ATTACHMENT H


Years 2018 - 2021

DISTRESS SURVEY CALL SAMPLING, TESTING, & ACCEPTANCE CRITERIA

(Note: This document solely describes MDOT’s procedure for review and acceptance of distress survey call quality. Other

MDOT checks on the same vendor distress survey data files - automated checking of file format / location referencing / entry

logic – are separate procedures and have separate acceptance rules of their own.)

Definition of Lot and Sample Unit:

A single lot will be comprised of a single distress survey data file corresponding to a single record listed

within the MDOT-provided annual TapeLog file identified for distress survey data submittal.

A single sample unit will be comprised of a single Primary Distress/Associated Distress (PD/AD) call

recorded within a distress survey data file (lot).

Lot Sampling Method:

A variation of a systematic sampling procedure with a random start will be utilized.

Selection of sample units from a lot will be based on randomly located segments (sample sub-sections).

There will be one sub-section per each mile, with a minimum length equal to 0.5% (26.4 feet).

Step 1 - A random milepoint within the first mile of the data file will be generated to determine the start

of the first sample sub-section.

Step 2 - Subsequent sample sub-sections will be located by successively adding 1.0 miles to the initial

randomly generated milepoint.

The entire lot sample will consist of the sum of sample units (PD/AD calls) contained within all of the

file’s randomly selected sub-sections.

Lot Testing Method:

All PD/AD calls located within each sample sub-section will be individually verified for accuracy by an

MDOT QA Officer who will simultaneously view the vendor’s provided pavement imaging.

Correct PD/AD Call - Both the PD and AD are properly recorded in the data.


Incorrect PD/AD Call – Any of the following:

1. A PD call is not recorded in the data.

2. A PD call is incorrectly recorded in the data as another PD.

3. A PD call is correctly recorded, but AD call is incorrectly recorded.

The PD call “No Distress” is the correct call for pavement imaging where no distress

exists.

Computation of Lot Quality Level:

MDOT QA Officer verification results from all sub-sections will be used to estimate lot quality

level (QL) based on the following equations:

Variables:

N = No. of PD/AD Calls Made by MDOT QA Officer

K = No. of PD/AD Calls Made by Vendor Survey

M = No. of Correct PD/AD Calls Made by Vendor Survey

QL = Estimated Quality Level of Lot

Quality Level Equations:

If K ≤ N, QL = (M / N) x 100%

If K > N, QL = [(M - (K - N)) / N] x 100%

Lot Acceptance/Rejection Decision Rules:

A single lot’s distress survey quality will be accepted when QL meets the following criteria:

For K > 20, QL ≥ 88%

For 15 < K ≤ 20, QL ≥ 87%

For 10 < K ≤ 15, QL ≥ 86%

For 5 < K ≤ 10, QL ≥ 85%

For 1 ≤ K ≤ 5, QL ≥ 84%

Rejected lots shall be corrected and resubmitted by the Vendor as described in Section B.2.6 of this

Scope of Work. MDOT will then perform a new sampling/checking of each resubmitted lot.


APPENDIX

DEFINITIONS

The following definitions are used throughout the Scope:

MDOT means Michigan Department of Transportation

File(s) means electronic data files.

Vendor means party awarded the contract.

State means State of Michigan.

FHWA means Federal Highway Administration

HPMS means (FHWA) Highway Performance Monitoring System

NHS means National Highway System

AASHTO means American Association of State Highway and Transportation Officials

QA means (MDOT) Quality Assurance

QC means (Vendor) Quality Control

Michigan Department CHECKLIST TO DESIGNATE AREAS OF ... · E-Verify system is operated by the...

Documents

Transcript of Michigan Department CHECKLIST TO DESIGNATE AREAS OF ... · E-Verify system is operated by the...