biddoc.pdf

REQUEST FOR INFORMATION (RFI)

Transportation Data Analytics Platform City of Steamboat Springs – Public Works/Engineering Division

Release Date: 08.11.2026

1. Purpose The City of Steamboat Springs, Colorado (“the City”) is seeking information from vendors offering transportation data analytics platforms capable of providing historical and real time multimodal transportation insights without the need for City-owned sensors or field hardware. The City intends to better understand today’s market, capabilities, and typical pricing models for tools that support traffic engineering, mobility planning, safety analysis, and complaint validation.

This RFI is exploratory and may inform a future Request for Qualifications (RFQ) or Request for Proposals (RFP). Depending on feasibility and cost, the City may proceed directly to procurement without issuing further solicitation.

2. Background Steamboat Springs is a mountain community with a multimodal transportation network that experiences seasonal peaks, event-driven congestion, variable speeds, multimodal travel patterns, and unique operational challenges. City engineering staff receive periodic concerns related to speeding, congestion, school-area safety, turning movement conflicts, and pedestrian/bicyclist activity.

The City currently relies solely on manual counts, consultant studies, and anecdotal feedback; no in-house sensors or automated traffic data systems exist today.

The City is evaluating third party platforms and other industry solutions capable of supplying robust transportation datasets without local hardware installation.

3. Desired Capabilities The City seeks information about platforms offering the following functionality:

3.1. Core Data & Analytics

• Historical traffic data (multi-year, intersection-level preferred)

• Real-time or near-real-time data (hourly or finer)

• Turning movement counts

• Speed trends and speeding identification

• Congestion levels and travel-time reliability

• Volume trends by season, event, corridor, or intersection

• Origin–destination patterns

3.2. Multimodal Coverage

• Pedestrian activity

• Bicycle activity

• Micro mobility (e-scooters, etc.)

• Transit movement analytics

• Freight movement

• Parking utilization, access patterns, or curb activity

3.3. Safety Analytics

• Conflict analysis/near-miss detection

• High-injury network support

• Tools supporting complaint validation (speeding, school zone concerns)

• Crash prediction modeling, risk scoring, or contributing factors

3.4. Geographic & Spatial Requirements

• Strong coverage for the City of Steamboat Springs, including core corridors

• Optional broader Routt County coverage

• Intersection level granularity

• Ability to analyze specific problem locations (school zones, downtown, US 40, ski resort base area, and development-area intersections)

3.5. Output & User Experience

• Easy-to-use dashboards

• Exportable datasets (CSV, GIS-compatible formats)

• API access (optional)

• Clear visualization tools suitable for public meetings and reporting

• Workflows that reduce staff burden and avoid overly complex interfaces

• Ability to support both engineering and planning use cases

3.6. Technical Requirements

• Cloud-hosted platform

• Authentication via single sign-on using Microsoft Entra ID and/or multifactor authentication

• Accessibility conformance report readily available using the latest

Voluntary Product Accessibility Template Web Content Accessibility Guidelines edition demonstrating compliance with essential WCAG 2.1 Level A/AA criteria

4. Additional Considerations

4.1. No Hardware Integration

The City does not require vendor-supplied sensors, cameras, counters, or roadside hardware. Platforms relying fully on third party datasets are preferred.

4.2. Privacy Expectations

The City does not require inclusion of license plate recognition or personally identifiable information. Vendors should describe any privacy protections inherent to their platform.

4.3. Cost Transparency

Vendors should provide ballpark cost estimates (annual subscription ranges, levels of service tiers, expected startup fees) to help determine feasibility.

4.4. Implementation Timeline

The City desires solutions that can be adopted with minimal setup, ideally with onboarding measured in days rather than months.

5. Vendor Response Instructions Responses should include the following sections:

1. Company & Platform Overview

2. Data Sources & Coverage

• Describe geographic coverage for Steamboat Springs; note any gaps.

3. Capabilities & Features

• Address each item in Section 3, above

4. Sample Dashboards/Reports

• Screenshots or narrative descriptions acceptable.

5. Pricing Structure

• Provide general or tiered cost ranges; no binding quotes necessary.

6. Implementation Requirements

• Note any dependencies, required integrations, or optional hardware.

7. Customer Support & Training

• Describe onboarding and ongoing support.

8. Optional Enhancements

• Forecasting, AI-based analysis, school zone monitoring, event analytics, etc.

9. References

• Other municipal or mountain-town clients.

6. Submission Process Because responses will be submitted to a Colorado public official and may be subject to release under the Colorado Open Records Act (CORA), vendors who wish to request confidentiality for any portion of their submission must provide two versions:

1. Complete Version (with proprietary content marked) – A full, unredacted proposal. Any proprietary or confidential sections must be clearly identified.

Blanket confidentiality statements (e.g., marking the entire document as confidential) may be disregarded.

2. Redacted Version (for potential public release) – A version of the proposal with all marked proprietary or confidential content removed. This version should be suitable for release in response to a CORA request.

The City’s records custodian is responsible for determining whether materials marked as proprietary or confidential must be disclosed under CORA.

Response Format: PDF or link to online materials

Submission Method: All questions and proposal submissions must be completed electronically through BidNet. Upload all materials via BidNet at www.bidnetdirect.com/colorado/cityofsteamboatsprings.

Optional Demonstration: Vendors may offer demo sessions, but such offers are not required and do not guarantee future procurement.

7. RFI Schedule The following schedule is provided to ensure a clear and transparent information gathering process. All dates are subject to change at the City’s discretion. If changes occur, the City will issue an addendum.

7.1. Anticipated RFI Timeline

Because this RFI is exploratory, the City may adjust these dates or steps to suit the level of vendor interest and internal capacity

• RFI Release Date: 08.11.2026

• Deadline for Vendor Questions: 09.01.2026 5 PM local time

• City Response to Questions/Final Addendum Issued: 09.03.2026 5 PM local time

• Deadline for RFI Submissions: 09.10.2026 5 PM local time

• City Review Period: 10.01.2026

• Optional Vendor Demonstrations, if requested: At City’s discretion following review period

7.2. Instructions Regarding Questions and Addenda

• Vendors must submit all questions in writing via BidNet by the stated deadline.

• Questions received after the deadline may not be addressed.

• The City will issue consolidated responses and any necessary clarifications or addenda by the “Final Addendum Issued” date.

• Vendors are responsible for reviewing all addenda to ensure complete responses.

8. Terms This RFI is issued solely for information-gathering purposes. It does not commit the City to any future contract, solicitation, or procurement. The City reserves the right to continue investigating options through additional RFQ/RFP processes or move directly to procurement depending on cost, feasibility, and internal needs.

8. Terms