RFI 2024 0625 WSDOT SSC Average Speed.pdf

WSDOT Page 1 of 4

June 25, 2024

REQUEST FOR INFORMATION (RFI)

Highway Speed Camera Pilot Program

ANNOUNCEMENT

The State of Washington is in the process of developing specifications for deploying speed safety camera (SSC) systems using average, or “point-to-point”, speed systems and is requesting input from the vendor community.

This RFI is not a formal solicitation. This RFI is intended solely to obtain information to assess the technical feasibility for potential future projects. Any potential procurement or implementation of recommended solutions will take place in a future Request for Proposal (RFP). Some respondents may be requested to provide a presentation and/or demonstration of their point-to-point SSC system.

BACKGROUND

WSDOT is interested in understanding the opportunities and challenges associated with point-to-point SSC systems for use on the interstate/freeway system. Point-to-point enforcement systems calculate average speed by measuring travel time over a predefined distance to enforce the speeding violation at selected segments.

QUESTIONS

Respondents should provide answers for each of the prompts/questions below to the best of their ability. Please reply “N/A” for any information that cannot be provided or is not applicable. Please include an explanation for any “N/A” response if possible.

1. Respondent Information

a) Organization name

b) Organization type

c) Organization address

d) Contact person name, email address, phone number

e) Organization website

2. Explain how the system works, including but not limited to the following:

a) Describe the equipment and technology used.

b) Describe equipment mounting options. For each mounting option, describe how long it takes to set-up and take-down the equipment and the skill level/training required.

a. Please provide a rough description on how an installation is priced (per day, per install, time and materials, etc.)

c) Describe the vehicle matching technology used (e.g., license plate matching, use of optical character recognition (OCR) technology, use of vehicle signatures, confidence levels, manual reviews, etc.).

d) How many lanes of traffic can the system enforce?

e) What range of speeds can the system capture?

f) Do time of day/ambient light/weather conditions impact system performance?

Request for Information (RFI) Speed Safety Camera (SSC) – Average Speed (Point-to-Point)

WSDOT Page 2 of 4

g) What is the required minimum/maximum distance between measuring points?

h) How do you determine what is a violation and what is not a violation?

a. What factors might make you throw out a potential violation?

i) Can you describe how the system can adapt to capture different classifications of vehicles

(standard sedans and pickup trucks through buses and semi-tractors), and if the system can classify vehicles by vehicle class?

j) Can databars be embedded in images? If yes, what data do they typically include?

k) With your system, could multiple enforcement zones be established over a segment (e.g., point-to-point-to-point)? Describe challenges with measuring speeds and issuing citations for multiple segments.

l) Understanding that this request goes beyond the expected scope of this proviso, can you elaborate on your company’s ability to collect additional data above and beyond that related to speed, such as seat belt usage or distracted driving?

3. Average speed calculations are heavily dependent on the accuracy of the time and distance measurements.

a) How are time and distance measurements calculated and ensured to be accurate?

b) What is the accuracy of the speed measurements within your operating range? How was this accuracy determined? If not fully answered by other questions, describe the operating range/limitations of the system.

c) Explain whether any of the equipment mounting options impact accuracy of the system (e.g., movement of equipment on an overhead arm mount).

d) Explain any other factors that may impact the accuracy of your system.

4. Describe requirements and challenges with deploying point-to-point SSC systems for a permanent installation.

a) Describe any infrastructure, power, and communication requirements that may be needed to set up the system.

b) Can the system be deployed in multiple segments where the detection needs to be set-up and taken down, for multiple ‘hot spots’ within a corridor?

c) Would the presence of multiple vehicles adjacent to each other in passing potentially obscure detection capabilities and/or violation determination?

5. Describe challenges with deploying point-to-point SSC systems for a temporary installation.

a) How long does it take to fully set-up and take down the system, including equipment, software, testing, etc.?

b) Can the system be deployed in multiple segments where the detection needs to be set-up and taken down on a frequent basis, ie, for multiple ‘hot spots’ within a corridor?

c) Would the presence of multiple vehicles adjacent to each other in passing potentially obscure detection capabilities and/or violation determination?

6. Describe the collected evidence packet in support of generating a violation:

a) Video/Photographs/Data Used

b) Calculations/Average Speed Determination

c) Driver License/Vehicle Identification

d) Proof of Initial Review

e) Final Approval of Violation Prior to Distribution

f) Other information, as appropriate

WSDOT Page 3 of 4

a. Are there customer service options for contacted vehicle owners to access with questions regarding their violation?

7. Have there been any judicial concerns or issues with this type of speed measurement in jurisdictions where you have it deployed?

a) On programs you have worked on in the past, what reasons have been used in court to overturn a citation from a point-to-point SSC system?

b) Has there been a significant percentage of challenges to the issued violations from the identified vehicle owners?

8. Provide up to three examples of your organization’s specific experience in deploying, managing and operating point-to-point SSC systems and programs. Provide the following for each example:

a) Location(s).

b) Agency/Client.

c) Reference person and contact information (email address and phone number).

d) Number of enforced lanes (range for the program).

e) Number of enforced segments (point-to-point, point-to-point-to-point, etc.)

f) Length of enforced segment (in miles)

g) Posted speed limit (range for the program)

a. Indicate whether enforced speed limit differs from posted speed limit.

h) Traffic volume (range for the program).

i) Number and type of implementations.

9. Current Automated Speed Enforcement operations are covered under Washington RCW 46.63.170 and RCW 46.63.200. WSDOT and partner agencies were instructed to evaluate the potential of using automated enforcement to slow speeds on critical freeway segments. What, if any, elements of this legislation would need to be modified for your point-to-point ASE system to be used in Washington?

a) Are there other barriers to implementation of your system in the State of Washington?

10. Indicate whether your organization would be willing to provide a demonstration of your system in Washington.

11. Please provide any additional information you believe would be beneficial for WSDOT to consider regarding the use of point-to-point SSC systems. Please do not include marketing materials.

RFI PROCESS

Responses to this RFI should be submitted electronically to the RFI Coordinator listed below no later than Tuesday, July 16, 2024, 4 pm Pacific.

A response to this RFI is not a mandatory requirement for participation in any subsequent solicitations released by the State of Washington. The results of this RFI may be used in development of future solicitations. All vendor communications concerning this RFI must be directed to the RFI Coordinator.

Schatzie Harvey RFI Coordinator WSDOT Contract Services 360-705-7106 Schatzie.harvey@wsdot.wa.gov mailto:Schatzie.harvey@wsdot.wa.gov

WSDOT Page 4 of 4

PUBLIC RECORDS

The vendor acknowledges that state agencies are subject to Chapter 42.56 RCW, the Public Disclosure Act.

Vendor responses to this RFI will become public record as defined in the RCW. For the purposes of this RFI no information considered confidential or proprietary should be included.

NO OBLIGATION TO CONTRACT

Release of this RFI in no way obligates the State of Washington to award a contract.

WSDOT will review all prospective RFI responses and will not review any supplementary information that does not pertain to this RFI. WSDOT may contact the Respondents to follow up with additional questions and/or clarifications.

TO SUMMARIZE

The state of Washington appreciates your thoughts and input and would also welcome any additional thoughts and comments related to provision of this service.

http://apps.leg.wa.gov/RCW/default.aspx?cite=42.56