510003 Addendum 1.pdf

STATE OF WISCONSIN

DEPARTMENT OF TRANSPORTATION

PURCHASING

REQUEST FOR BID ADDENDUM

Bid No. 510003

Addendum Number o 1

WISDOT-CENTRAL PURCHASING

Pavement Condition and Photolog Data Collection Equipment (2 vans), Data Processing System, and Data Viewing System

Bid Must Be Received No Later Than

Date 09/21/2017 Time 2:00 PM

PLEASE READ ALL INSTRUCTIONS CAREFULLY

THE FOLLOWING CHANGES ARE HEREBY ADDED TO AND MADE A PART OF (REQUEST FOR BID NUMBER 5100004)

Please see attached question and answer pages. There is now a cost proposal spreadsheet that must be completed with each proposal.

BIDDERS MUST SIGN AND SUBMIT WITH THIS SIGNED COVER PAGE WITH THEIR BID SUBMISSION.

I/We certify that we have not, either directly or indirectly, entered into any agreement or participated in any collusion or otherwise taken any action in restraint of free competition; that no attempt has been made to induce any other person or firm to submit or not to submit a bid; that this bid has been independently arrived at without collusion with any other bidder, competitor, or potential competitor; that this bid has not been knowingly disclosed prior to the opening of bids of any other bidder or competitor; that the above statement is accurate under penalty of perjury.

We will comply with all terms, conditions, and specifications required by the State of Wisconsin in this request for bid and all terms of our bid.

(Authorized Name - Type or Print) (Authorized Signature)

(Title) (Telephone) (Date)

T202 10/2002

Date Issued 09/06/2017

Purchasing Agent Deb Adamski-Pavloski

Buyer Telephone (608} 267-2972

510003 Questions and Answers:

Q1: Whether companies from Outside USA can apply for this? (like, from India or Canada)

A1: As long as they can perform the work within the USA.

Q2: Whether we need to come over there for meetings?

A2: See Section 3.7

Q3: Can we perform the tasks (related to RFP) outside USA? (like, from India or Canada)

A3: See page 2 #21.

Q4: Can we submit the proposals via email?

A4: See Section 2.3

Q5: “4.5.1 - Vehicle Customization: Carpeted floors” Is this required? We suggest industrial rubber floors for safety (reduce static) and cleanliness.

A5: No, industrial rubber floors are acceptable.

Q6: Can the department provide sample imagery from their historical photolog to ensure we understand the requirements and can match the historical images accordingly?

A6: WisDOT will provide a PDF on VendorNet showing imagery, directory structure, and log/GPS/nod files associated with imagery.

Q7: 4.1.19 Desktop Viewing Application, is a web based viewing application that meets the specification acceptable?

A7: WisDOT doesn’t require a specific desktop application, but the ability to view a subset of the data while NOT connected to the internet/offline is required.

Q8: In Section 1.3.2, pg 6, it states “Software for editing and compiling digital perspective imagery including integration with on board distance measurement, GPS and inertial data”, can WisDOT provide further explanation or use cases on how this software will be used?

A8: Whatever software tools may be required to compile collected data into seamless routes for distribution to business partners as a final product. If portions of routes are collected in separate sessions at different times, in our current experience software tools are required to compile the imagery, DMI, GPS and inertial data into a single continuous route structure. Depending on your solution, software to facilitate this route editing and compilation may or may not be necessary, but WisDOT does require segments of routes collected independently to be viewable as a seamless route.

Q9: In Section 2.5, pg 12, are there any requirements for what would constitute submitting multiple proposals? Do there have to be substantial differences in the solution that is being proposed to WisDOT?

A9: If there is more than one solution, then multiple proposals would be submitted as each proposal may have different cost elements.

dotd3a Highlight

WisDOT Photolog directory structure:

Route file (011E_R1_2016) contains Front/Side imagery directories and .GPS .LOG .NOD files associated with this route

Front and Side directories contain dir_XXX subdirectories each with .jpg images, both full resolution (F_) and thumbnails

(R_). Dir subdirectories contain 100 F_ and 100 R_ jpgs as we currently collect 100 pictures per mile for each camera

510003 Response to Question 6

.Log file is a tab delimited text file our current software reads to display the data at the bottom of the Roadview Player software screen associated with each image.

.Nod file is a tab delimited text file our current software reads to facilitate a search by feature function allowing a user to jump to an image for an intersection location based on interpretation of a mileage value

.GPS file is in a proprietary binary format which contains data for each image consisting of GPS file name, GPS frame, Latitude, Longitude, Elevation, Collection date, Collection time and Heading. The screenshot below shows this binary data converted to text

Current software for viewing WisDOT photolog:

Roadview Player screenshot- data display under images comes from .Log and .GPS files

Screenshot of PDF exported from Roadview Player software:

Roadview Player screenshot with Search By Feature function accessing data in .Nod file

Q10: In Section 4.5.26, pg. 32, Phased Payment Plan, when putting together a payment plan to propose, is WisDOT open to a plan that would include a percentage payment after contract signing but before delivery to help pay for vehicles and some of the equipment, etc.?

A10: A payment plan will be tied to the completion of work and that will be established as part of the Statement of Work to the awarding contractor.

Q11: In Attachment E, WisDOT suggests several line items to be listed in Part A. Will WisDOT accept other (more or less) line items that more directly correlate to their costs for this proposal?

A11: To facilitate uniform responses, WisDOT has created a cost proposal spreadsheet to indicate requested line item costs. Each vendor should utilize the cost proposal spreadsheet WisDOT has posted to VendorNet. Because we’re requesting 2 vans, both a unit price and total price should be indicated.

Additional items not listed in the spreadsheet that will impact the cost proposal SHOULD be added as separate line items to illustrate total WisDOT costs for the proposed solution. If there is no additional cost for any of the listed items you can indicate “included”.

Q12: In Attachment E, WisDOT suggests using the costs form Part A to provide a line item quote and total cost for implementation and 5 years of operation of the system. Would WisDOT accept a pricing table that combine parts A and B to generate the total cost to be used for the basis of awarding the cost points (similar to the attached image below)?

A12: To facilitate uniform responses, WisDOT has created a cost proposal spreadsheet to indicate requested line item costs. Each vendor should utilize the cost proposal spreadsheet WisDOT has posted to VendorNet. Because we’re requesting 2 vans, both a unit price and total price should be indicated.

Additional items not listed in the spreadsheet that will impact the cost proposal SHOULD be added as separate line items to illustrate total WisDOT costs for the proposed solution. If there is no additional cost for any of the listed items you can indicate “included”.

Q13: In Attachment E, WisDOT suggests listing line item costs for the added options outlined in section

4.2. Does WisDOT expect additional costs for each of the items listed (4.2.1-4.2.11) even if no additional costs are to be incurred?

A13: If no additional costs are to be incurred for any of the value added items in section 4.2, please indicate that the functionality for any item listed will be “included” in the proposed solution. For example, we realize a LiDAR system will have additional costs, but flexible collection options may already be a part of the solution and additional costs would be null.

Q14: For any Value Added and Optional Features that we cannot provided at this time without more information, is WisDOT planning on negotiating a price with the vendor for any item they want to add in the contract? Or does a price have to be included with the proposal for WisDOT to add Optional Features?

A14: Provide the best information you have for value added options at this time. If your proposed solution cannot accommodate any of the value added items, simply indicate what items you cannot address. Any pricing for value added items will be negotiated during contract establishment. A price range for value added features that require additional detail can be indicated. Costs for value added features should be indicated in the cost proposal spreadsheet.

dotd3a Highlight

Sample Pricing Tables

Sample submitted by Vendor part of Question 12

Q15: Page 6 – 1.3.2 – “to meet WisDOT’s Pavement Condition Index (PCI) rating criteria” Can WisDOT provide this document as it is not included or listed in the Appendix or any part of this RFP.

A15: WisDOT’s rating criteria uses the standard practice for pavement condition index surveys outlined in ASTM D6433.

WisDOT currently identifies and rates the following distresses and incorporates them into a PCI rating.

The following distresses must be able to be automatically collected and/or identified and rated manually based on the judgment of a WisDOT pavement rater.

- Alligator Cracking

- Bleeding

- Block Cracking

- Edge Cracking

- Longitudinal Cracking

- Patching

- Pot Holes

- Rutting

- Slippage Cracking

- Transverse Cracking

- Weathering and Raveling

- Blowup / Buckling

- Corner Break

- Corner Spalling

- “D” Cracking

- Divided Slab

- Faulting

- Joint Spalling

- Linear Cracking

- Patching – Large

- Patching – Small

- Popouts

- Punchout

- Scaling, Map Cracking, and Crazing

- Shrinkage Cracks

Q16: Page 7 – 1.3.3 – “and WisDOT protocols” – Can WisDOT provide this document as it is not included or listed in the Appendix or any part of this RFP.

A16: The referenced sentence in the RFP can be revised to read as follows by eliminating any reference to “WisDOT protocols”: The next generation of pavement condition data collection equipment must obtain the necessary information to extract ride quality and pavement distress following FHWA protocols and standards outlined in section 4.5.2.

Q17: Page 15 – 4.1.4 – “DMI data shall be integrated with GPS and IMU data – Can WisDOT explain or elaborate what level of integration is required?

A17: Data from the DMI must facilitate a LRS reference for the GPS and IMU data so that it can be accurately associated with the imagery and other sensor data to facilitate a relationship with WisDOT corporate data.

Q18: Page 17 - 4.1.12 “On-board Hardware” – “In vehicle storage” Please state how many miles of collection is required for the vehicle either per week or in terms of hard drive capacity in TB.

A18: Removable hard drives should be capable of storing at least 2000 miles of data.

Q19: Page 17 - 4.1.12 “On-board Hardware” – “Transferring data from the collection vehicle to Computer storage” Please state how the weekly collection data is uploaded out of the van to the computer network storage. Whose responsibility does this fall under?

A19: Transferring data from the collection vehicle to computer storage will in part depend on your proposed solution. Van data will likely need to be transferred to a WisDOT network prior to being uploaded to a hosted solution. Current workflows for data transfer are the responsibility of WisDOT staff and our current system is connected to the WisDOT network via a fiber-optic connection in our garage. Photolog data is currently transferred from the van to the WisDOT network using external fire wire hard drives.

Q20: Page 17 – 4.1.1.13 – “On-board Software” – Can WisDOT specify the requirements for “Database management system”.

A20: Must be able to download a WisDOT created database to be used directly in the van or to output a route collection file for use in the van. Database and route collection file format will vary by vendor solution. Must have the ability to edit the collection database or route file in the van to facilitate changes in the field.

Q21: Page 18 – 4.1.17 - “Data Storage” – Can WisDOT specify what is it's existing infrastructure to transfer data from the garage to a network.

A21: Currently data is transferred from the pavement van to the WisDOT network using a fiber-optic connection in the garage. Photolog data is currently transferred from the van to the WisDOT network using external fire wire hard drives.

Q22: Page 21 - 4.2.9 – “WisCors compatibility” The link that is listed in the RFP does not work saying this site can’t be reached. Can WisDOT provide an active link?

A22: WisCORS home page: https://wiscorsweb.dot.wi.gov/TrimblePivotWeb/

WisCORS FAQ link: https://wiscorsweb.dot.wi.gov/TrimblePivotWeb/documents/wiscors-faq.pdf https://wiscorsweb.dot.wi.gov/TrimblePivotWeb/ https://wiscorsweb.dot.wi.gov/TrimblePivotWeb/documents/wiscors-faq.pdf