Amendment-0003-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/20220003

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 .

1. The RFP calls for yearly collection between 2500-3000 miles (12,000-15,000 total over five years), but when totaling the single collection and twice collection sites the average yearly collection would be 2,187 miles (10,936 total miles). What is the cause for this discrepancy?

- We anticipate around 11,000 miles of collection over the life of the contract. See the introduction on page 8 of solicitation. For the base year we are planning for less collection (possibly around 1,000 miles), to ensure the consultant is up to speed and collecting correctly/accurately. After that we would anticipate 2,500 to 3,000 miles/year for the reminder of the contract.

2. Can you provide a shapefile for all sites to aid in our planning calculations?

- Please see amendment, we have shared a file geodatabase containing a vast majority of the anticipated paved routes to be collected. We are only looking for collection of routes within the lower 48 states. We have included more features/attributes in the geodatabase for reference only (parking, unpaved roads, boundary layer,etc).

3. Do you have the pavement composition percentage of asphalt, concrete and unpaved throughout the system?

- Of the routes to be collected, it would be approximately 98% asphalt, 2% concrete. This information can be obtained in the geodatabase on a route by route basis as well.

4. Are the route lists per cycle set, yet to be set, or would the vendor have some control on route collection?

- We are open to vendor recommendations for collection schedule on some routes. However, we do have some requirements for how often some routes are collected and the spacing between each collection.

5. Is the goal of the software to mimic our in-house rating processes?

- For the software, we are looking to perform randomized checks on the consultant’s ratings of cracking identification and severity. If necessary, depending on web display options, the software could also be used solely as a viewer of the collected roadway cameras and pavement cameras/sensors.

6. What would be the most common uses of the editing functionality of the software?

- We are not sure we would be editing much in the software, possibly to shorten a route or rename/renumber a route. We could work with the consultant and possible/necessary editing capabilities.