Amendment-0004-693C7322R000014 .pdf

(x)

693C7322R000014 x x

1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted ; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGEMENT TO BE

RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR

OFFER. If by virtue of this amendment you desire to change an offer already submitted , such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

x

ASHBURN VA 20147

693C73

SUITE E2-3-300

QUANTUM PARK, 22001 LOUDOUN COUNTY PKWY

EASTERN FEDERAL LANDS HIGHWAY DIVISION

FEDERAL HIGHWAY ADMINISTRATION

See Block #1404/06/20220004

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

12. ACCOUNTING AND APPROPRIATION DATA (If required) is not extended.is extended, Items 8 and 15, and returning

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended , by one of the following methods: (a) By completing

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

FACILITY CODE CODE

10B. DATED (SEE ITEM 13)

10A. MODIFICATION OF CONTRACT/ORDER NO.

9B. DATED (SEE ITEM 11)

9A. AMENDMENT OF SOLICITATION NO.

CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code)

7. ADMINISTERED BY (If other than Item 6)CODE 6. ISSUED BY

PAGE OF PAGES

4. REQUISITION/PURCHASE REQ. NO.3. EFFECTIVE DATE2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO. (If applicable)

1. CONTRACT ID CODE

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

03/03/2022

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

E. IMPORTANT: Contractor is not is required to sign this document and return __________________ copies to the issuing office.

ORDER NO. IN ITEM 10A.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Road Inventory Services IDIQ SATOC

The purpose of this amendment is to update the current solicitation to include:

1. Providing answers to questions and other government provided data for RIP Data

Collection.

2. All other terms and conditions remain the same.

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)15A. NAME AND TITLE OF SIGNER (Type or print)

15C. DATE SIGNED 16B. UNITED STATES OF AMERICA 15B. CONTRACTOR/OFFEROR 16C. DATE SIGNED

(Signature of person authorized to sign) (Signature of Contracting Officer)

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

Previous edition unusable

Except as provided herein, all terms and conditions of the document referenced in Item 9 A or 10A, as heretofore changed, remains unchanged and in full force and effect .

693C7322R000014 – Amendment 0004: "Road Inventory Program Data Collection, Processing, and Viewing"

Questions - 05052022

1. Is there an existing format, or spreadsheet shell, for the HPMS deliverable that vendors should populate? Template for HPMS format is include as an amendment.

2. How should the Appendix L spreadsheet or the HPMS report deliverables handle bridges or other assets? Should certain information/data/metrics be excluded? We aren’t aware of any bridges or special assets that need to be treated differently. For this data submittal just focus on the surface distresses. If a unique situation needs to be noted, then note it as a comment in the Appendix L spreadsheet.

3. How should the rut average field of the HPMS deliverable be calculated? For instance, should it include left and right values averaged together, or just one wheel path? Per the HPMS guide, Rutting is the Average Rutting (average of both wheel paths over the reporting section)

4. Is it preferable to include IRI values in one of the deliverables? Not necessary for HPMS submittal. Include IRI-Left and IRI-Right in Appendix L spreadsheet.

5. How many decimal places should be reported for Appendix L distress values and lane widths?

and for the HPMS deliverable length of cracking and cracking percent fields?

a. HPMS requirements are length to the nearest foot and cracking percent to the nearest percent.

b. FHWA-EFL requirements to the nearest foot for this submittal.

6. In Appendix L the “PATCH” field description mentions including potholes and classifying by severity. Given that the spreadsheet only contains one field, should that field include both patches and potholes? and how should severity be classified? An updated spreadsheet for Appendix L showing patching severity level is provided as an amendment. Appendix L was also updated to include a “Comments” field and eliminate Section 5 due to road closure.

7. Are Appendix L and the HPMS deliverables the only sensor/cracking deliverables required for the proposal response? Sensor deliverables are required for the TPP test results in addition to the sensor/cracking results for Appendix L and HPMS deliverables.