RFP-2026-0911.pdf

Request for Proposals

RFP-2026-0911

Washington State

Roadway Toll Systems

Modernization Programs

Offered by

Washington State Department of

Transportation

Roadway Toll Systems Project Request for Proposals RFP-2026-0911 i State of Washington Department of Transportation

Table of Contents

1. REQUEST FOR PROPOSALS AVAILABILITY

1.1 Electronic Availability

1.2 Alternative Formats

2. DEFINITIONS

3. INTRODUCTION

3.1 Authorization

3.2 Contract Terms

3.3 No Obligation

3.4 RFP Materials Summary

4. ORT AND SIDE-FIRE PROGRAM DESCRIPTIONS

5. OVERALL PROGRAM GOALS

6. PROCUREMENT PROCESS

6.1 RFP Schedule

6.2 Selection Process

7. CONTACT INFORMATION AND TERMS AND CONDITIONS

7.1 WSDOT Procurement Coordinator

7.2 Communications

7.3 WSDOT Consultant/Technical Support

7.4 Complaint Process

7.5 Organizational Conflicts of Interest

7.6 Equal Employment Opportunity

7.7 Wage Theft Prevention Certification

7.8 Workers’ Rights Certification

7.9 Prevailing Wages

7.10 Client References

8. LETTER OF INTENT

9. MANDATORY BIDDERS MEETING AND REGISTRATION

10. QUESTIONS AND ANSWERS

11. PROPOSAL SUBMITTAL INSTRUCTIONS AND FORMAT

11.1 Time and Manner of Submission

11.2 Bidder’s Acknowledgement

11.3 Bidder Expenses

11.4 Proprietary Information and Public Disclosure

11.5 Irregularities or Defects

11.6 Rejection of Proposals/Cancellation of RFP

11.7 Proposal Organization and Format

12. PROPOSAL DOCUMENT

12.1 Page Limits

12.2 Proposal Section 1: Letter of Submittal

12.3 Proposal Section 2: Table of Contents

ii State of Washington Department of Transportation

12.4 Proposal Section 3: Executive Summary

12.5 Proposal Section 4: Proposal Narrative ORT RTS Contract:

12.6 Proposal Section 4: Proposal Narrative Side-Fire RTS Contract:

12.7 Proposal Section 5: Technical Requirements Compliance Matrix

12.8 Proposal Section 6: Key Personnel Resumes

12.9 Proposal Section 7: Cost Proposal

12.10 Proposal Section 8: Required Documents and Documentation

12.11 Proposal Section 9: Corporate Financial Information

12.12 Proposal Section 10: Bidder's Contract Issues List

13. PROPOSAL EVALUATION AND SELECTION

13.1 Overview

13.2 Pass/Fail Screening Criteria

13.3 Minimum Qualifications Pass/Fail Screening Criteria

13.4 Technical Proposal Scoring

13.5 Interviews

13.6 Technical Scoring Update

13.7 Cost Proposal Scoring

13.8 Total Score Determination

13.9 BAFO (at WSDOT’s option)

13.10 Best Value Proposal Determination

13.11 Financial Stability Assessment

13.12 Selection of Apparent Successful Bidder

13.13 Contract Negotiations

14. NOTIFICATIONS AND DEBRIEFING

14.1 Notification of Successful Bidder

14.2 Notification to Unsuccessful Bidders

14.3 Debriefing of Unsuccessful Bidders

15. PROTESTS

15.1 Grounds for Protest

15.2 Protest Bond Requirement

15.3 Procedure for Protest

15.4 Protest Review Process

TABLES

Table 6-1. RFP Procurement Schedule Table 12-1. Proposal Page Limits Table 12-2. ORT RTS Contract Key Personnel Qualifications Table 12-3. Side-Fire RTS Contract: Key Personnel Qualifications Table 12-4. Performance Measures Table 13-1. ORT RTS Proposal Scoring Table Table 13-2. Side-Fire RTS Proposal Scoring Table Table 13-3. Pass/Fail Criteria Table 13-4. ORT RTS Contract Minimum Qualifications Pass/Fail Criteria iii State of Washington Department of Transportation

EXHIBIT LIST

• Exhibit 1: Bidders Certification

• Exhibit 2: Compliance Matrix

• Exhibit 3A: ORT RTS Contract Cost Proposal

• Exhibit 3B: Side-Fire RTS Contract Cost Proposal

• Exhibit 4: Bidder's Contract Issues List

• Exhibit 5: Subcontractor Inclusion Plan

• Exhibit 6A: ORT RTS Contract Proposer Checklist

• Exhibit 6B: Side-Fire RTS Contract Proposer Checklist

• Exhibit 7: Key Personnel Resume Template

• Exhibit 8: Washington State Prevailing Wage Rates

• Exhibit 9: Organizational Conflicts of Interest Certification, Disclosure and

Avoidance/Neutralization Plan (OCOI)

• Exhibit 10A: ORT RTS Contract

• Exhibit 10B: Side-Fire RTS Contract

APPENDIX LIST

• Appendix 1: Definitions

• Appendix 2A: ORT RTS Project Overview

• Appendix 2B: Side-Fire RTS Project Overview

• Appendix 3: Design, Installation, and Testing

• Appendix 4: Toll Technical Requirements

• Appendix 5: Operations and Maintenance

• Appendix 6: List of Mandatory Standards

• Appendix 7: Lane Side Operations Business Rules

• Appendix 8: Roadside ICD

• Appendix 9: Information Technology Security

• Appendix 10: Plate Type Reference Guide

• Appendix 11: Supplemental Manuals From WSDOT

• Appendix 12: Toll Sign Display File ICD

State of Washington Department of Transportation

1. REQUEST FOR PROPOSALS AVAILABILITY

1.1 Electronic Availability

The contents of this Request for Proposals (RFP), and any RFP Amendments and written answers to questions, will be available on Washington’s Electronic Business Solution (WEBS) website at https://pr-webs-vendor.des.wa.gov/.

Bidders are solely responsible for:

• Properly registering with WEBS at https://fortress.wa.gov/ga/webs/ and maintaining an accurate Bidder profile in WEBS.

• Downloading the RFP packet, consisting of the RFP, all Exhibits and Appendices, and incorporated documents related to the RFP for which the Bidder is interested in submitting.

• Downloading all current and subsequent RFP Amendments to ensure receipt of all

RFP documents.

Notification of RFP Amendments will only be generated by the WEBS system and will be provided only to those Bidders who have registered with WEBS and have downloaded the

RFP from WEBS. Failure to register and download the RFP from WEBS may result in a Bidder having incomplete, inaccurate, or otherwise missing information and RFP documents. RFP

Amendments and requests for Best and Final Offers (BAFO) that occur after Proposals are submitted will be emailed directly to the designated point of contact for all remaining Bidders.

1.2 Alternative Formats

Persons with disabilities may request information contained within this RFP and subsequent

RFP Amendments to be prepared and supplied in alternative formats by contacting the

WSDOT Procurement Coordinator.

2. DEFINITIONS

All capitalized terms used in this RFP, but not expressly defined herein, have the respective meanings set forth in Appendix 1.

3. INTRODUCTION

The Washington State Department of Transportation (WSDOT) is soliciting Proposals from interested Bidders to design, develop, implement, operate, and maintain four or more Roadway

Toll Systems (RTS) in Washington State. WSDOT will be awarding two contracts through this single RFP. The Contracts have distinct scopes, as discussed in Exhibit 10A, Open Road

Tolling (ORT) RTS Contract and Exhibit 10B, Side-Fire RTS Contract of this RFP.

https://pr-webs-vendor.des.wa.gov/ https://fortress.wa.gov/ga/webs/

State of Washington Department of Transportation

ORT RTS Contract includes a mix of replacement and new projects that are both Single-Point and Express Toll Lane (ETL) Open Road Tolling facilities. The four toll facilities included, in addition to shared-host and program-level work, are:

• RTS Program and Host (ORT RTS Contract, Exhibit A)

• Replacement of the existing SR 520 Toll Facility (ORT RTS Contract, Exhibit B)

• Installation of the new SR 167 East of I-5 Toll Facility (ORT RTS Contract, Exhibit

C)

• Replacement of the existing SR 99 Toll Facility (ORT RTS Contract, Exhibit D)

• Replacement of the existing I-405 Bellevue to Lynnwood ETL Facility (ORT RTS

Contract, Exhibit E)

Side-Fire RTS Contract includes an initial scope for a Side-Fire Only RTS project Proof of

Concept (POC). The distinct POC Statement of Work (SOW) is discussed in Side-Fire RTS

Contract, Exhibit A. At WSDOT’s discretion, standalone facilities may be added to the Side-Fire

RTS Contract in future Statements of Work.

ORT RTS Contract will be eligible to be awarded future projects statewide, while Side-Fire RTS

Contract will only be eligible for future work based on the results of the POC. The intent is to empower WSDOT to select either or both of the ORT RTS Contract Response or the Side-Fire

RTS Contract Response for future projects (beyond the four initial facilities included in ORT

RTS Contract).

Each contract will be awarded and evaluated independently. The ORT RTS Contract and the

Side-Fire RTS Contract may be awarded to the same or different Bidders. Bidders may propose overlapping key personnel team members in their ORT RTS Contract and Side-Fire RTS

Contract.

Future projects that may potentially be added include the following (further described in ORT

RTS Contract Exhibit H and Side-Fire RTS Contract Exhibit C, Hypothetical Future Systems):

• ORT RTS Contract Hypothetical Systems:

− System 1: Single Point 3 lanes, 2 Toll Zones

− System 2: Single Point 2 lanes, 2 Toll Zones

− System 3: Single Point 1 lane, 4 Toll Zones

− System 4: ETL Single lane, 20 Toll Points

− System 5: ETL Dual lane, 20 Toll Points

• Side-Fire RTS Contract Hypothetical Systems:

− System 1: Side-Fire Program

− System 2: Single Point 2 lanes, 2 Toll Zones

State of Washington Department of Transportation

− System 3: Single point 1 lane, 4 Toll Zones

− System 4: ETL Single lane, 20 Toll Points

− System 5: ETL Dual lane, 20 Toll Points

The RTS projects may also be referred to in this RFP as the “RTS Program.”

Bidders shall satisfy all requirements specified in this RFP. Failure of the Bidder to meet these requirements may result in rejection of the Proposal. By submitting a Proposal, Bidders agree to be bound by the requirements outlined in this RFP.

3.1 Authorization

The Washington State Department of Enterprise Services (DES) has authority over goods and services under Chapter 39.26 RCW and sets processes for procuring information technology based on the policies and standards set by the Washington State Technology Services Board

(TSB). Chapter 43.105 RCW as amended establishes the TSB. While the TSB does not purchase for agencies, it establishes policies and standards addressing the way State agencies may acquire information technology equipment, software, and services. Chapter

39.26 RCW and Chapter 43.105 RCW WSDOT issues this RFP acting under the delegated authority of DES and consistent with the policies and standards of Washington Technology

Solutions (WaTech).

3.2 Contract Terms

The term of the ORT RTS Contract shall commence upon the last Contract signature date

(Effective Date) and terminate 10 years after System Acceptance by WSDOT on the last

System SOW issued under this Contract, unless terminated early as provided elsewhere in the Contract. The Work for each System will include 10 years of Operations and Maintenance, unless specifically modified by an applicable SOW. This term may be further extended upon the mutual written agreement of the parties.

The term of the Side-Fire RTS Contract shall commence upon the last Contract signature date

(Effective Date) and terminate five years after the POC Decommissioning milestone approval date unless a System SOW is issued within that five-year term. In the event one or more

System SOWs are issued, the Contract shall terminate 10 years after System Acceptance by

WSDOT on the last System SOW issued under this Contract, unless terminated early as provided elsewhere in the Contract. The Work for each System will include 10 years of

Operations and Maintenance (commencing upon System Acceptance), unless specifically modified by an applicable SOW. This term may be further extended upon the mutual written agreement of the parties.

WSDOT may later add or modify Roadway Toll Systems to the Project. WSDOT may add a

Roadway Toll System to the Project no later than 10 years from the Effective Date of the respective Contract. This term may be further extended upon the mutual written agreement of the parties.

State of Washington Department of Transportation

3.3 No Obligation

This RFP does not obligate WSDOT to award a Contract to any Bidder. WSDOT reserves the right to amend, modify, cancel, or reissue this RFP, in whole or in part, without prior notice, at any time, and at its sole discretion.

WSDOT reserves the right to modify the scope and requirements of the Program, including adding and/or deleting functionality, throughout the procurement process.

Any Contract awarded as a result of this RFP is contingent upon the availability of funding.

3.4 RFP Materials Summary

As this RFP will procure two contracts there are some materials that apply to both and some that apply only to one or the other. Unless otherwise noted, Appendices and Exhibits apply to both contracts. Appendices and Exhibits appended with “A” pertain to the ORT RTS Contract only. Appendices and Exhibits appended with “B” pertain to the Side-Fire RTS Contract only.

Please review the lists below to ensure you have downloaded all of the relevant materials for the respective contract(s) of interest.

RFP Exhibits:

• Exhibit 1: Bidders Certification

• Exhibit 2: Compliance Matrix

• Exhibit 3A: ORT RTS Contract Cost Proposal

• Exhibit 3B: Side-Fire RTS Contract Cost Proposal

• Exhibit 4: Bidder's Contract Issues List

• Exhibit 5: Subcontractor Inclusion Plan

• Exhibit 6A: ORT RTS Contract Proposer Checklist

• Exhibit 6B: Side-Fire RTS Contract Proposer Checklist

• Exhibit 7: Key Personnel Resume Template

• Exhibit 8: Washington State Prevailing Wage Rates

• Exhibit 9: Organizational Conflicts of Interest Certification, Disclosure and

Avoidance/Neutralization Plan (OCOI)

• Exhibit 10A: ORT RTS Contract

• ORT RTS Exhibit A: RTS SOW #1 RTS Program and Host

• ORT RTS Exhibit B: RTS SOW #2 SR 520 Replacement

• ORT RTS Exhibit C: RTS SOW #3 Gateway SR 167 East of I-5

State of Washington Department of Transportation

• ORT RTS Exhibit D: RTS SOW #4 SR 99 Replacement

• ORT RTS Exhibit E: RTS SOW #5 I-405 Bellevue to Lynnwood Replacement

• ORT RTS Exhibit F: Labor Rates

• ORT RTS Exhibit H: RTS Hypothetical Facilities

• ORT RTS Exhibit I: Minor System Enhancements and Facility Repairs

• ORT RTS Exhibit J: Performance Measures/KPIs

• ORT RTS Exhibit K: Bond Templates

• ORT RTS Exhibit L: Software License (for Vendor Proprietary Software)

• ORT RTS Exhibit M: Software Escrow Agreement

• Exhibit 10B: Side-Fire RTS Contract

• Side-Fire RTS Exhibit A: Side Fire SOW #1 Proof of Concept

• Side-Fire RTS Exhibit B: Preliminary Coordination for Additional Systems

• Side-Fire RTS Exhibit C: Side Fire Hypothetical Facilities

• Side-Fire RTS Exhibit D: Minor System Enhancements and Facility Repairs

• Side-Fire RTS Exhibit E: Performance Measures/KPIs

• Side-Fire RTS Exhibit F: Bond Templates

• Side-Fire RTS Exhibit G: Labor Rates

• Side-Fire RTS Exhibit H: Software License (for Vendor Proprietary Software)

• Side-Fire RTS Exhibit I: Software Escrow Agreement

Appendices:

• Appendix 1: Definitions

• Appendix 2A: ORT RTS Project Overview

• Appendix 2B: Side-Fire RTS Project Overview

• Appendix 3: Design, Installation, and Testing

• Appendix 4: Toll Technical Requirements

• Appendix 5: Operations and Maintenance

• Appendix 6: List of Mandatory Standards

• Appendix 7: Lane Side Operations Business Rules

• *Appendix 8: Roadside ICD

• Appendix 9: Information Technology Security

• *Appendix 10: Plate Type Reference Guide

State of Washington Department of Transportation

• *Appendix 11: Supplemental Manuals From WSDOT

• *Appendix 12: Toll Sign Display File ICD

*Documents not provided via WEBS and will be provided separately on an as-needed basis to Bidders who submit Letters of Intent.

4. ORT AND SIDE-FIRE PROGRAM DESCRIPTIONS

The RTS Program comprises the design, installation, integration, testing, operation, and maintenance of Single-Point Toll and ETL systems that will be a mix of Brownfield Projects and

Greenfield Projects. The scope of work for the Program comprises multiple facilities and systems that will be executed in separate SOWs.

The plan for both Programs consists of the following components:

• Design, supply, install, field test, commission, operate, and maintain RTS.

• Coordinate with WSDOT Groups and Subject Matter Experts (SMEs) as required to design, plan, and execute field work throughout the life of the Program.

• Coordinate with WSDOT’s separately contracted Design Builder teams (on

Greenfield Projects) responsible for delivering toll facility infrastructure, including toll signs, striping, toll gantries, roadside cabinets, and required power and communication connections.

• For Brownfield Projects, coordinate with WSDOT and WSDOT’s legacy Toll Vendor to effectively and efficiently plan transition and execute conversion of existing systems within the Replacement Projects.

• Support succession plans and decommissioning activities at end of life.

The RTS Program will include electronic equipment for Transponder (optional for Side-Fire

RTS) and Image-based Tolling. The RTS will also include a Digital Video Audit System (DVAS) to provide camera monitoring of the Toll Zones. The purpose of the RTS is to detect, identify, and classify (as required) vehicles passing through toll zones to allow accurate transaction creation and to support revenue collection on the WSDOT Tolling System.

WSDOT provides and operates Toll Rate Signs on all WSDOT tolling facilities announcing current toll rates. WSDOT generates Toll Sign Display Files (TSDF) that capture effective toll rates and other WSDOT-posted messages on Toll Rate Signs on ETL facilities. TSDF files are transmitted to the Bidder for correct rate assignment during the Trip-building process. Single-point toll facilities employ a variable time-of-day toll rate schedule that is determined by

WSDOT.

WSDOT provides a Back Office System (BOS) for back-office functions but does not complete

Trip building. The Bidder will be responsible for building complete Trips for all WSDOT facilities and providing all Trip data associated with each vehicle passage in accordance with the BOS

Interface Control Document (ICD).

State of Washington Department of Transportation

No manual image review is explicitly required under the Contract; however, the Bidder may choose to perform image review for certain Transactions in order to meet Key Performance

Indicators (KPIs).

More detailed project descriptions are described in the Contract Exhibits.

The main business requirements for the Program are contained within the following Appendices:

• Appendix 3, Design, Installation, and Testing Requirements

• Appendix 4, Toll Technical Requirements

• Appendix 5, Operations and Maintenance Requirements

The Work for this Program includes all services, labor, material, and equipment necessary to design, develop, implement, operate, and maintain the RTS Projects in accordance with the

Contracts.

5. OVERALL PROGRAM GOALS

• Goal 1: Safe and Smooth Transition:

− Execute a safe and smooth transition to the RTS that minimizes impacts to operations and customers. This goal will be met, in part, through a combination of each of the subsequent goals. Where roadside facilities are replaced, the

Bidder should leverage technology options and transition approaches to maintain business continuity and aid in revenue loss prevention. Transitions will be deployed with the customer in mind so they are not unduly burdened.

Ensure safety for all staff and the traveling public.

• Goal 2: Leverage Technology:

− Utilize innovation, advanced technology and industry best practices to deliver schedule and cost savings while achieving high performance. Solutions should require less roadside infrastructure than previous generations and have less equipment in or over the roadway to install and maintain. Solutions should be faster to deploy and provide efficiencies over previous generations. Solutions should mitigate future cost risk by providing scalability and building in flexibility to leverage improvements or efficiencies due to new technologies, processes, or systems as they become available.

• Goal 3: System Resiliency and Transparency:

− Provide resilient, flexible, and adaptable solutions to streamline implementation and operations while providing a high degree of transparency into current conditions and performance data. Systems will minimize downtime due to failures and environmental conditions and they will store, transmit, and back up data appropriately for business needs moving forward. Solutions will be flexible and adaptable to encompass both full roadway and express toll lane applications, and will be expandable depending on volume and new

State of Washington Department of Transportation deployments, as well as any new functionality desired by WSDOT, such as interoperability. Solutions will provide thorough and timely reporting of system performance data and will remove barriers to communication and understanding, improving time to resolution and supporting clear auditability.

• Goal 4: Partnership and Delivery:

− Strong partnership between WSDOT and the Bidder, supported by rigorous

Project management, accountability, and transparency. Work hand-in-hand with WSDOT to collaboratively plan work, resolve issues, and foster regular and transparent communications. Provide efficient project delivery through flexible resource planning and partner fairly with WSDOT if flexibility is needed to navigate enhancements or potential unknowns.

• Goal 5: Maximize Value and Efficiency:

− Minimize implementation cost, operational cost, and potential lost revenue while optimizing business value through programmatic efficiencies and improvements that provide benefit to customers and across toll division.

Leverage economies of scale and seek efficiencies to reduce operational costs as volumes grow. Help mitigate risks of rising infrastructure costs. Enact a partnering approach to change and change management.

6. PROCUREMENT PROCESS

6.1 RFP Schedule

All Bidders shall adhere to the schedule of activities set forth in Table 6-1. WSDOT reserves the right to modify dates and times related to this solicitation. Changes will be posted on WEBS as RFP Amendments and sent electronically to all users of WEBS who downloaded this RFP.

RFP Amendments and requests for BAFOs that occur after Proposals are submitted will be emailed directly to the designated point of contact for all remaining Bidders. Late Proposals will not be accepted, nor will time extensions be granted.

Table 6-1. RFP Procurement Schedule

Activity Due Date Time

(Pacific)

Official Release of the RFP September 11, 2026 4:00 p.m.

Mandatory Bidders Meeting Registration September 25, 2026 Noon

Mandatory Bidders Meeting October 8, 2026 12:30 p.m.

Letter of Intent October 16, 2026 Noon

Bidder Written Questions Due October 16, 2026 Noon

WSDOT Written Answers to Written Questions (estimated)

October 30, 2026 Noon

Deadline for Bidder Submittal of Complaints November 6, 2026 Noon

Proposals Due December 9, 2026 Noon

Invitation to Bidder Interviews (estimated) January 22, 2027 Noon

State of Washington Department of Transportation

Activity Due Date Time

(Pacific)

Bidder Interviews February 8, 2027 – February 11, 2027 Varies

Request for BAFO (at WSDOT’s option) If requested, would follow Interviews Varies

BAFO Submittals, If Required Request for BAFO + 4 weeks Noon

Determine Best Value Proposal (if no BAFO) February 12, 2027 Internal

Financial Stability Assessment February 16, 2027 – February 22, 2027 Internal

Identify The Apparent Successful Bidder (ASB) February 22, 2027 4:00 p.m.

Bidder Request for Optional Debriefing Due Debrief must be requested no later than 3 Business Days after the ASB is announced

4:00 p.m.

Bidder Debriefing (if any) No later than 5 Business Days after debriefing request

Varies

Protests Due No later than 5 Business Days after debriefing conference

2:00 p.m.

Begin Contract Negotiations (if any) March 3, 2027 Internal

Estimated Contract Execution March 25, 2027 Internal

6.2 Selection Process

WSDOT will use the following multi-step evaluation process to select a Bidder to deliver the

Project:

• Step 1: Pass/Fail. WSDOT evaluates the Proposals against the Pass/Fail screening criteria in accordance with Section 13.2 herein.

• Step 2: Minimum Qualifications. Those Bidders that pass Step 1 will advance to the second step in which the Minimum Qualifications Pass/Fail criteria will be evaluated in accordance with Section 13.3 herein.

• Step 3: Technical Proposal Scoring. Those Bidders that pass Step 2 will advance to the third step in which the Proposals are evaluated and scored on the technical sections of the Proposal in accordance with Section 13.4 herein.

• Step 4: Interviews. Following the completion of Step 3, WSDOT will conduct in-person interviews with the Bidders, with the top scoring Proposals, or, at WSDOT’s sole discretion, all remaining Bidders, in accordance with Section 13.5 herein.

• Step 5: Technical Proposal Scoring Update. Following completion of Step 4, WSDOT will score the interview and update the technical score for each interviewed

Bidder based upon the interview responses in accordance with Section 13.6 herein.

• Step 6: Cost Proposal Scoring. Following completion of Step 5 or in parallel with the technical reviews, WSDOT will open and evaluate the Cost Proposals in accordance with Section 13.7 herein.

State of Washington Department of Transportation

• Step 7: Total Score Determination. The technical score and price score will be combined to establish the total score for each remaining Bidder in accordance with

Section 13.8 herein. Upon calculation of the total score, WSDOT may, at its sole discretion, implement Step 9, Step 10, or Step 11.

• Step 8: Best and Final Offers (optional). Following the completion of Step 7, WSDOT may, at its sole discretion, issue a notice for a BAFO to the top scoring Step

7 Bidders, or at WSDOT’s sole discretion, all remaining Bidders, in accordance with

Section 13.9 herein.

• Step 9: Best Value Determination. Following the completion of Step 6, Step 7, or

Step 8, if implemented, WSDOT will determine the Best Value Proposal in accordance with Section 13.10 herein.

• Step 10: Financial Stability Assessment. Following the completion of Step 9, WSDOT will perform a Financial Stability Assessment of the Bidder with the Best

Value Proposal in accordance with Section 13.11 herein.

• Step 11: Apparent Successful Bidder. Following the successful completion of Step

10, WSDOT will identify the Apparent Successful Bidder in accordance with Section

13.12 herein.

• Step 12: Contract Negotiations. Following the successful completion of Step 11, WSDOT will enter into contract negotiations with the Apparent Successful Bidder in accordance with Section 13.13 herein.

The steps of the evaluation process are summarized in the following sections and described in detail in Section 13.

7. CONTACT INFORMATION AND TERMS AND CONDITIONS

7.1 WSDOT Procurement Coordinator

The WSDOT Procurement Coordinator is the sole point of contact in WSDOT for this RFP.

Upon issuance of this RFP and until WSDOT and the Apparent Successful Bidder have executed the Contract, all communication between Bidders and WSDOT shall be with the

WSDOT Procurement Coordinator, as follows:

Tariq Ohab, WSDOT Procurement Coordinator

Phone: (360) 972-5245

Email: ACOAcquisitionSubmittal@wsdot.wa.gov and

Cc to: Tariq.Ohab@wsdot.wa.gov

Persons with a hearing or speech disability may contact the Procurement Coordinator by dialing 711 to connect with a Telecommunications Relay Services operator for assistance.

mailto:ACOAcquisitionSubmittal@wsdot.wa.gov mailto:Tariq.Ohab@wsdot.wa.gov

State of Washington Department of Transportation

7.2 Communications

Upon receipt of this RFP and until WSDOT has executed the Contract, the Bidders may not approach any WSDOT employee or consultant other than the WSDOT Procurement

Coordinator regarding this procurement. All RFP-specific inquiries and other correspondence concerning this RFP shall be addressed to the WSDOT Procurement Coordinator.

Communication regarding this RFP with any other WSDOT or State employee or consultant will be considered unofficial and non-binding to WSDOT. Bidders are expected to conduct themselves with professional integrity and to refrain from lobbying activities. Solicitation to WSDOT employees or consultants is prohibited in any form.

Any verified allegation of an attempt to unduly influence the selection or communication by a

Bidder or its employees, agents, Subcontractors, or consultants directed to parties other than the WSDOT Procurement Coordinator may result in disqualification of the Bidder, all at the sole discretion of WSDOT.

Verbal responses to questions will be considered unofficial and non-binding. Only written responses posted to WEBS will be considered official and binding.

Bidders must use email for any communication required in this RFP. Bidders must submit protests in writing via email to the email address indicated in Section 7.1 herein.

7.3 WSDOT Consultant/Technical Support

WSDOT has retained the consulting firms of Jacobs Engineering, WSP USA, and Silicon

Transportation Consultants to assist in developing the RFP. Each of these firms is prohibited from joining or otherwise assisting any Bidder in connection with the procurement process.

7.4 Complaint Process

7.4.1 GENERAL

The complaint process occurs during the solicitation portion of the procurement process prior to submitting a Proposal to a competitive solicitation. Complaints are designed to improve and clarify the competitive solicitation process. The purpose of a complaint process is to settle unresolved Bidder issues or concerns that either were not or could not be resolved during the question-and-answer period or the pre-proposal conference. The complaint process allows Bidders to focus on the solicitation requirements and the evaluation process and raise issues early enough in the process to allow WSDOT to correct a problem before bids are submitted and time is expended on evaluations. The compliant process helps mitigate the need for protests.

Bidders are expected to raise any questions they have concerning the RFP early in the RFP process. If a Bidder believes the RFP unnecessarily restricts competition, contains inadequate or insufficient requirements, or utilizes an evaluation process that

State of Washington Department of Transportation is unfair or flawed, the Bidder may submit a formal written complaint to the WSDOT

Procurement Coordinator identified in this RFP.

7.4.2 DEADLINE FOR FILING COMPLAINTS

The deadline for filing complaints regarding this solicitation is by the date and time specified in Section 6.1 herein.

Bidders may submit a complaint based only on the following:

• The solicitation unnecessarily restricts competition;

• The solicitation evaluation or scoring process is unfair or flawed; or

• The solicitation requirements are inadequate or insufficient to prepare a

Proposal.

7.4.3 FORM OF BIDDER COMPLAINTS

• The complaint must be in writing;

• The complaint must be sent via email to the WSDOT Procurement Coordinator, by the due date set forth in Section 6.1 herein;

• The complaint must clearly articulate the basis for the complaint; and

• The complaint must include a proposed remedy.

The WSDOT Procurement Coordinator will review and evaluate the complaint and provide a written response. WSDOT reserves the right to modify the RFP if it is determined, at WSDOT’s sole discretion, that the complaint is valid or the recommended change is in the best interest of WSDOT. WSDOT’s decision is final, and no appeal process will be available to the Bidder once a decision has been made.

WSDOT’s response to the complaint, including any resulting changes to the RFP, will be posted on WEBS. The Washington State Secretary of Transportation will be notified of the complaint and provided with a copy of WSDOT’s response.

7.5 Organizational Conflicts of Interest

Organizational conflict of interest means that because of other activities or relationships with other people or entities, a person or entity:

• Is unable or potentially unable to render impartial assistance or advice to WSDOT; or

• Is or might be otherwise impaired in its objectivity in performing the Contract work; or

• Has an unfair competitive advantage.

Attention is directed to the requirement for disclosure of organizational conflicts of interest set forth in 23 CFR Section 636.116(a)(2) (applicable to federal aid procurements), WSDOT

State of Washington Department of Transportation

Secretary’s Executive Order E-1059.00, and WSDOT Organizational Conflicts of Interest

Manual (M 3043).

Bidders are required to disclose all relevant facts concerning any past, present, or currently planned interests, activities, or relationships that may present an organizational conflict of interest. Bidders shall state how their interests, activities, or relationships, or those of the chief executives, directors, Key Personnel, or any proposed consultant, sub-consultant at any tier, Contractor, or Subcontractor at any tier may result or could be viewed as an organizational conflict of interest, in accordance with Secretary’s Executive Order E-1059.00 and WSDOT

Organizational Conflicts of Interest Manual (M 3043). Bidders shall submit the Organizational

Conflicts of Interest Certification and Organizational Conflicts of Interest Disclosure and

Avoidance/Neutralization Plans (forms contained in Exhibit 9) as described elsewhere in this

RFP.

If an Organizational Conflict of Interest is determined to exist, WSDOT may, at its sole discretion: offer the Bidder the opportunity to avoid or neutralize the Organizational Conflict of

Interest; disqualify the Bidder from further participation in the RFP; or cancel this RFP.

WSDOT will take steps to ensure that individuals that are involved in the procurement package and evaluation of Proposals are not influenced by organizational conflicts of interest, and that no Bidder is given an unfair competitive advantage over another.

7.6 Equal Employment Opportunity

Discrimination in all phases of contracted employment, consultant activities, contracting activities, and training is prohibited by Title VI of the Civil Rights Act, 42 U.S.C. § 2000d et seq.; Title 49 CFR, Subt. A, Part 21, Nondiscrimination in Federally Assisted Programs of the

Department of Transportation - Effectuation of Title VI of the Civil Rights Act; Title VII of the

Civil Rights Act, 42 U.S.C. § 2000e et seq.; Americans with Disabilities Act, 42 U.S.C. § 12101 et seq.; Washington Law Against Discrimination, Chapter 49.60 RCW; and other Laws and

Regulations. The referenced legal citations establish the minimum requirements for affirmative action efforts and define the basic nondiscrimination provisions as further detailed in the Contract.

7.7 Wage Theft Prevention Certification

Bidder must represent and warrant that neither it nor its principals or affiliates have, within the three-year period prior to the date of this solicitation, been determined, by a final order of the

Washington Department of Labor and Industries or a court of competent jurisdiction, to be in willful violation of state wage laws. Said certification shall be made in Exhibit 1, Bidders

Certification.

State of Washington Department of Transportation

7.8 Workers’ Rights Certification

Pursuant to the Washington State Governor’s Executive Order 18-03, Supporting Workers’

Rights to Effectively Address Workplace Violations (dated June 12, 2018), to the extent permissible under state and federal law, WSDOT is seeking to contract with qualified entities and business owners who certify that their employees are not, as a condition of employment, subject to mandatory individual arbitration clauses and class or collective action waivers. Said certification shall be made in Exhibit 1, Bidders Certification. All Bidders that certify that their employees are not required, as a condition of employment, to sign or agree to mandatory individual arbitration clauses or class or collective action waivers will be given preference over

Bidders that do not make that certification in the event of a tie score.

7.9 Prevailing Wages

Bidder shall ensure that it is familiar with, and complies with, the requirements of Chapter

39.12 RCW and that the Prevailing Wage is paid to workers under the Contract (including by any Subcontractors) where such payment is required by Washington law.

7.10 Client References

Bidder shall submit three references listed in Exhibit 1, Bidders Certification. WSDOT will contact the references directly. Bidders are encouraged to confirm the submitted references are willing and able to provide a reference. WSDOT may request additional references from

Bidders if any of their original references are unresponsive or unable to provide a reference.

WSDOT may follow up with questions relative to the references during the Bidder interviews.

8. LETTER OF INTENT

A letter indicating the Bidder's intent to propose in response to this RFP is requested to be transmitted to the WSDOT Procurement Coordinator at the email address specified in Section

7.1 herein no later than the date and time listed in Section 6.1 herein. The Bidder shall submit the Letter of Intent by email. The WSDOT Procurement Coordinator will confirm by email receipt of Bidder’s Letter of Intent.

A Letter of Intent to Propose does not obligate the Bidder to submit a Proposal.

Only Bidders who have submitted a Letter of Intent will be eligible to receive subsequent limited appendices or materials issued as part of this RFP. These materials should be treated as and considered confidential and not to be further disseminated.

Each Bidder must include the following information in the Letter of Intent:

• Bidder name;

State of Washington Department of Transportation

• Statement that the Bidder intends to submit a proposal to RFP-2026-0911 and for which contracts the Bidder intends to submit (i.e., ORT RTS Contract, Side-Fire

RTS Contract, or both); and

• Bidder’s authorized representative for this RFP (Bidder Representative), who will be available as the primary contact throughout the RFP process, with contact information as follows:

− Name of Bidder Representative

− Title of Bidder Representative

− Address

− Telephone number

− E-mail address

9. MANDATORY BIDDERS MEETING AND REGISTRATION

WSDOT will conduct a mandatory pre-proposal Bidders Meeting on the date indicated herein in

Section 6.1, Table 6-1: RFP Procurement Schedule. Only those that attend the mandatory

Bidders Meeting will be eligible to submit proposals. The Bidders Meeting will allow for both in person and remote attendees. In person attendance will be held at the following location:

2901 3rd Avenue

Suite 500

Seattle, WA 98121

Rainier Room

In person attendance will be limited to two individuals per organization.

Virtual attendance will be conducted via MS Teams. A link to the virtual attendance will be provided to those upon registration with the WSDOT Procurement Coordinator.

Each Bidder shall confirm it will participate in the mandatory pre-proposal Bidders Meeting by registering with the WSDOT Procurement Coordinator via email at the email address specified in Section 7.1 herein by the date and time shown in Section 6.1 herein. The WSDOT

Procurement Coordinator will confirm by email receipt of Bidder’s registration. All conversations that take place during the pre-proposal Bidders Meeting are considered informal and are not contractually binding. Bidders desiring a formal response to their questions shall submit questions in writing to the WSDOT Procurement Coordinator as described in Section 7 herein.

10. QUESTIONS AND ANSWERS

WSDOT must receive all written inquiries from Bidders by the date and time shown in Section

6.1 herein. Questions may be submitted in advance of the questions deadline. Any inquiries, suggestions, or requests concerning interpretation, clarification, or additional information shall

State of Washington Department of Transportation be made in writing and delivered to the WSDOT Procurement Coordinator via email at the email address as specified in Section 7.1 herein. WSDOT will not respond to Bidder questions submitted or received after said date and time. WSDOT will provide written answers by the date shown in Section 6.1 herein.

It is incumbent upon each Bidder to carefully examine the RFP requirements, terms, and conditions. Should any Bidder find discrepancies, omissions, or ambiguities in this RFP, the

Bidder shall at once request, via email at the email address as specified in Section 7.1 herein, an interpretation from the WSDOT Procurement Coordinator.

Written answers to Bidder questions and amendments, if any, will be posted on WEBS.

The Bidder that submitted the question(s) will not be identified in the answer. Verbal responses to questions will be considered unofficial and non-binding. Only written answers and amendments to the RFP, if any, posted to WEBS will be considered official and binding.

11. PROPOSAL SUBMITTAL INSTRUCTIONS AND FORMAT

11.1 Time and Manner of Submission

The Bidder’s electronic bid must be emailed to the Procurement Coordinator at the following email address: acoacquisitionsubmittal@wsdot.wa.gov and tariq.ohab@wsdot.wa.gov.

Separate emails with complete bid materials shall be provided for the ORT RTS Contract and the Side-Fire RTS Contract, in the event a Bidder is proposing on both contracts.

Note: Bidder emails (including attachments) CANNOT exceed 30 MB in size (emails that exceed 30 MB in size will not be delivered). Accordingly, Bidders are cautioned to keep email sizes to less than 25 MB to ease delivery. Zipped files cannot be accepted. WSDOT will send an acknowledgement email of bid receipt. Acknowledgement of bid receipt is not a determination on the bid’s responsiveness. If the Bidder does not receive an acknowledgement within a reasonable time, it is the responsibility of the Bidder to contact

WSDOT for acknowledgement of bid receipt. Bidders shall submit proposals electronically no later than the date indicated in Section 6.1 herein.

Bidders shall submit their Proposals in the format set forth in Section 11.7 herein.

Any Proposal received after the prescribed deadline will be marked as “Late” and will not be considered.

Bidders will not be allowed to make changes to their Proposal after the Proposal submission deadline unless they receive a request for a BAFO from WSDOT.

mailto:acoacquisitionsubmittal@wsdot.wa.gov mailto:tariq.ohab@wsdot.wa.gov

State of Washington Department of Transportation

11.2 Bidder’s Acknowledgement

By submitting a Proposal in response to this RFP, each Bidder unequivocally acknowledges that the Bidder has read and fully understands this RFP and any amendments hereto, and that the Bidder has asked questions and received answers from WSDOT regarding any provisions of this RFP with regard to the Bidder’s desired clarification.

11.3 Bidder Expenses

WSDOT will not assume any expense incurred by the Bidder for, or related to, responding to this RFP. Bidders are solely responsible for their own expenses in preparing, delivering, and/or presenting a Proposal, including but not limited to expenses incurred to attend and participate in the pre-proposal Bidders Meeting, Bidder Interview, Bidder Discussions, and the

Contract negotiations.

11.4 Proprietary Information and Public Disclosure

Materials submitted in response to this RFP shall be deemed public records as defined by

Chapter 42.56 RCW. All Proposals and accompanying documentation shall become the property of WSDOT upon receipt and will not be returned. Additionally, pursuant to RCW

39.26.030, materials submitted in response to this RFP along with any evaluation materials are exempt from disclosure until WSDOT announces the Apparent Successful Bidder.

In the event a Bidder desires to claim portions of its Proposal as exempt from public disclosure, the Bidder shall identify those portions in the Letter of Submittal and provide the legal basis for the exemption. In addition, each sentence, paragraph, table, graphic, or similar individual element of the Proposal claimed to be exempt shall be clearly identified as “PROPRIETARY.”

Bidder’s marking of the entire Proposal or entire sections of the Proposal as proprietary will not be accepted nor honored. WSDOT will not accept Proposals in which pricing is marked PROPRIETARY, and the Proposal will be rejected. While total implementation and operations pricing cannot be treated as proprietary, the milestone detail and annual operations pricing will be treated as confidential.

To the extent consistent with Chapter 42.56 RCW, the Public Records Act, WSDOT shall maintain the confidentiality of Bidder’s information marked PROPRIETARY. If a request is made to view the portions of the Proposal a Bidder has marked as PROPRIETARY, WSDOT will notify the Bidder of the request and of the date that the records will be released to the requester unless the Bidder obtains a court order enjoining that disclosure. If the Bidder fails to obtain the court order enjoining disclosure, WSDOT will release the requested information on the date specified.

WSDOT’s sole responsibility shall be limited to maintaining the Bidder’s identified information in a secure area and to notify the Bidder of any request(s) for disclosure for as long as WSDOT retains the Bidder’s information in WSDOT records. Failure to so label such materials or failure

State of Washington Department of Transportation to timely respond after notice of request for public disclosure has been given shall be deemed a waiver by the Bidder of any claim that such materials are exempt from disclosure.

11.5 Irregularities or Defects

WSDOT may, at its sole discretion, waive minor irregularities or defects in a Proposal, or accept or reject any item or combination of items, when to do so would be to the advantage of the State. WSDOT reserves the right to seek clarification of a Bidder’s Proposal from the

Bidder or verification of information contained in a Bidder’s Proposal from any other source.

11.6 Rejection of Proposals/Cancellation of RFP

WSDOT reserves the right to reject any or all Proposals. It is also within the right of WSDOT to reject Proposals that do not contain all elements and information requested in this RFP or

RFP Amendments. WSDOT reserves the right to cancel this RFP at any time for any reason.

11.7 Proposal Organization and Format

This Section contains and describes the specific information that is to be provided in a

Proposal in order to be considered by WSDOT. The Proposal shall contain all required information and address all requirements specified within this RFP. Failure to respond or provide required information may result in a determination by WSDOT, in its sole discretion, that a Proposal is non-responsive and may be disqualified from further consideration.

Proposals shall be organized into the Proposal sections and subsections set forth in

Section 12 herein. The section and subsection numbers and titles must be restated in the

Bidder’s Proposal Narrative Section 4 in the order specified. Proposal Narrative files shall be in a searchable, unlocked PDF format. The proposal narrative shall use no smaller than 11-point font for general text and no smaller than 8-point font for proposal tables and graphics, headers, footers, and footnotes. Proposal content may be in portrait or landscape format, or a mixture of the two. If the Bidder elects to include technical or equipment performance data, that should be organized within the technical solution portion of its proposal.

Resumes shall use no smaller than 10-point font. Any signatures required in the submitted files may be digital signatures.

The response should be submitted in two separate electronic files. The separation of the documentation protects the integrity of the State’s evaluation process. No mention of the cost response/Cost Proposal may be made in File 1. Separate emails with separate File 1 and

File 2 materials shall be provided for the ORT RTS Contract and the Side-Fire RTS Contract respectively, in the event a Bidder is proposing on both contracts.

State of Washington Department of Transportation

11.7.1 ELECTRONIC FILE 1

1. Letter of Submittal (with a copy in File 2)

2. Proposal Document

3. Exhibit 2, Compliance Matrix

4. Exhibit 7, Key Personnel Resume Template

5. Exhibit 9, Organizational Conflicts of Interest Certification, Disclosure and

Avoidance/Neutralization Plan (OCOI)

11.7.2 ELECTRONIC FILE 2

1. Letter of Submittal (Copy)

2. Exhibit 1, Bidders Certification: This Exhibit gathers essential details about potential Bidders, including their legal business information, tax identification numbers, and registration details. The references identified in this Exhibit will be contacted.

3. Exhibit 3A (ORT RTS Contract) or Exhibit 3B (Side-Fire RTS Contract) –

Cost Proposal

4. Exhibit 4, Bidder's Contract Issues List: This Exhibit outlines the Bidder’s issues, if any, and proposed resolution for Bidders who have business concerns with the form of the Contract. Note, however, that WSDOT reserves the right not to modify the Contract and to award the Contract based on a Bidder’s willingness to agree to the Contract.

− Redlined documents will NOT be reviewed.

− Do not provide a copy of Bidder's standard contract.

− WSDOT cannot and will not accept a bid or enter a Contract that substantially changes the material terms and conditions set forth in this Competitive Solicitation.

5. Exhibit 5, Subcontractor Inclusion Plan: This Exhibit’s purpose is to encourage and track the participation of Subcontractors on the Project. This form is required for Bidders that plan to utilize Subcontractors.

6. Exhibit 6A, ORT RTS Contract Proposer Checklist

7. Exhibit 6B, Side-Fire RTS Contract Proposer Checklist

8. Exhibit 8, Washington State Prevailing Wage Rates

State of Washington Department of Transportation

12. PROPOSAL DOCUMENT

12.1 Page Limits

Proposals shall be limited to page numbers as shown in Table 12-1. Only material included in the Proposal will be considered. Links and references to other external documents not included with the proposal will be disregarded. Section dividers and navigational guides will not count towards the page limits.

Table 12-1. Proposal Page Limits

Section Number Title Page Limit

1 Letter of Submittal 4 pages

2 Table of Contents No Limit

3 Executive Summary 5 pages

4 Proposal Narrative ▪ ORT RTS Contract: 120 pages

▪ Side-Fire RTS Contract: 100 pages

5 Compliance Matrix No Limit

6 Key Personnel Resumes 2 pages per person

7 Cost Proposal No Limit

8 Required Documents and Documentation, including RFP Exhibits

No Limit

9 Corporate Financial Information No Limit

10 Bidder's Contract Issues List No Limit

12.2 Proposal Section 1: Letter of Submittal

The Letter of Submittal must include an Electronic Signature of a…