Attachment_F_Technical_Specifications.xlsx

XLSX spreadsheet 61 KB Posted Aug 24, 2026

Attached to: RFP - PW - Curb Management Technology
Solicitation number: 0000004185
Issued by: Hennepin County, Minnesota

About this file

Written by GovTribe AI · Aug 26, 2026

This file is a technical specifications worksheet for a Request for Proposals (RFP) issued jointly by the City of Minneapolis and the City of Seattle to procure curb management technology and related services. The RFP seeks qualified vendors across seven primary technology categories: Fixed Traffic Sensors, Fixed Curb Sensors, Mobile Sensor Systems, Emergency and Dynamic Curb Control Integration Systems, Dynamic Curb Communication and Display Systems, Curb and Mobility Data Aggregation Systems, and Freight and Commercial Vehicle Data Packages. Vendors are required to complete applicable tabs corresponding to their proposed technology solutions, with questions designated as either "Required" (pass/fail) or "Scored" (evaluation criteria). The specification document provides detailed technical requirements across operational, deployment, performance, and data management dimensions for each technology category, enabling vendors to demonstrate compliance with minimum functional requirements and differentiate their solutions through scored responses.

The technical specifications establish rigorous evaluation criteria addressing hardware compatibility with the Build America, Buy America (BABA) Act, data output standards including the Curb Data Specification (CDS) and Mobility Data Specification (MDS), sensor accuracy metrics, communication protocols, cybersecurity requirements including NIST framework compliance, and data ownership provisions stipulating that the City retains ownership of all generated data. Required specifications include API integration capabilities, support for data export in non-proprietary formats, personally identifiable information (PII) controls, and English-language documentation. Vendors must address warranty periods, technical support availability including 24/7 emergency support options, installation requirements, power consumption specifications, maintenance protocols, and system uptime commitments. The framework accommodates diverse deployment modalities—from fixed roadside sensors to vehicle-mounted and aerial systems—with specific operational constraints, accuracy thresholds, and environmental performance parameters tailored to each technology category.

View the file

Other files

File	Type	Posted
Attachment_L_-_Phase_One_Evaluation_Criteria_Score_Sheet.xlsx	XLSX spreadsheet	Aug 24, 2026
Attachment I.2 Disclosure-of-lobbying-activities-form.docx	DOCX document	Aug 24, 2026
eSupplier_Bidding_Guide.pdf	PDF	Aug 24, 2026
Attachment I.4 Debarment_and_Suspension_Certification.docx	DOCX document	Aug 24, 2026
Attachment_J_-_SMART_Grant_Stage_2_Agreement.pdf	PDF	Aug 24, 2026
RFP_-_PW_-_Curb_Management_Technology.pdf	PDF	Aug 24, 2026
Attachment I.1 Questionnaire for Federal Contracts.docx	DOCX document	Aug 24, 2026
Attachment I.3 Lobbying Certification.docx	DOCX document	Aug 24, 2026
2026_44_RFP_PW_Curb_Management_Technology.pdf	PDF	Aug 24, 2026
Attachment I.5 City_of_Seattle_Technology_Contract 8.5.docx	DOCX document	Aug 24, 2026

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Instructions Overview and Instructions

Each tab in this workbook corresponds to a specific technology category described in the RFP. Vendors must complete the tab(s) applicable to each proposed technology solution.

If proposing multiple solutions across different technology categories, vendors must complete a separate tab for each applicable category.

Responses should be specific to the proposed solution and consistent with the information provided in the main body of the proposal.

Vendors may copy tabs to provide the required information for multiple technology solutions within the same category.

Vendors may rename tabs corresponding to each specific technology solution for clarity.

Only complete tabs relevant to the proposed technologies; tabs that do not apply may be left blank.

Each question within this workbook is designated as either “Required" (Pass/Fail) or “Scored" (Evaluation).

Questions identified as "Required" represent minimum functional or technical requirements and are structured as Yes/No questions.

Questions identified as "Scored" will be used to comparatively evaluate proposals and differentiate between solutions.

Failure to meet "Required" criteria may result in disqualification from further consideration for that technology category.

1 FixedTrafficSensors

Question ID	Question Format	Required / Scored	Question	Response
			Fixed (Static) Data Collection Sensors (complete once for each proposed technology solution)	Please respond directly in this column, or reference the relevant page of your proposal that answers the given question.
			General
1.1	Multiple Choice	Scored	Specify if the hardware is offered for purchase or for rent or other hybrid model
1.2	Y/N	Required	Equipment is compliant with the Build America, Buy America (BABA) Act
1.3	Y/N	Scored	Capable of measuring pedestrian traffic volumes
1.4	Y/N	Scored	Capable of measuring bike traffic volumes
1.5	Y/N	Scored	Capable of measuring vehicle traffic volumes
1.6	Short Answer	Scored	Describe directional flow measurement capabilities (e.g., turning movements, corridor directionality)
1.7	Y/N	Scored	Capable of measuring vehicle speeds
1.8	Y/N	Scored	Capable of identifying FHWA vehicle category classifications 1-13 or classifications as defined by the University of Washington Freight Lab		CurbOccupancyToolkit_rev.pdf
1.9	Y/N	Scored	Capable of continuous (24/7) monitoring across defined corridor or intersection
1.10	Numeric	Scored	Define maximum detection range for each applicable target type (vehicles, pedestrians, etc.) (feet or meters)
1.11	Numeric	Scored	Define maximum coverage area per unit (by square feet at intersections and linear feet midblock)
1.12	Numeric	Scored	Define sensor optimal field of view (degrees)
1.13	Short Answer	Scored	Describe the optimal and maximum areas for data collection (e.g. single parking stall, block face etc.)
1.14	Short Answer	Scored	Describe the process through which the sensor processes the collected data, including where the data is primarily processed (e.g. edge processesing, cloud, etc.)
1.15	Short Answer	Scored	Decscribe the communication methods (e.g. cellular data, Ethernet over twisted pair, Ethernet over fiber, WiFi, etc.) and data rates typically needed.
1.16	Short Answer	Scored	Describe the available data collection intervals of the proposed sensor (e.g. real time/near-real time video, 1 second, 5 seconds, 30 seconds etc.)
1.17	Multiple Choice	Scored	List all applicable compliance certifications (FCC certification for radio frequency compliance, UL, CE, NTCIP, other)
			Warranty and Technical Support
1.18	Numeric	Scored	Define standard warranty period (years)
1.19	Short Answer	Scored	Describe warranty coverage terms and exclusions
1.20	Short Answer	Scored	Describe technical support availability (hours, response time, service level agreements)
1.21	Y/N	Scored	Is 24/7 emergency technical support available
1.22	Y/N	Required	User manuals and technical documentation available in English
			Deployment and Operations
1.23	Short Answer	Scored	Define typical installation location(s) (midblock, intersection, overhead, roadside, other)
1.24	Short Answer	Scored	Describe installation options and requirements (external installation crews, internal installers, reliance on City crews, etc.).
1.25	Numeric	Scored	Define typical hardware mounting height (feet or meters)
1.26	Numeric	Scored	Define the lead time (in days/weeks) needed to acquire and transport hardware between contract agreement and deployment
1.27	Short Answer	Scored	Describe any potential delays in receiving units, and potential remedies to reduce lead time
1.28	Numeric	Scored	Define time required for system calibration after installation (business days)
1.29	Y/N	Scored	Requires lane or roadway closure for installation
1.30	Y/N	Scored	Equipment meets IP (Ingress Protection) rating of IP66 of higher
1.31	Y/N	Short Answer	Can the device be powered by hardwired connections? If so, describe connector type and power requirements
1.32	Numeric	Scored	Describe power consumption requirements (watts or amp draw at voltage)
1.33	Numeric	Scored	Battery backup duration in hours (if applicable)
1.34	Numeric	Scored	Expected hardware lifespan or replacement cadence in years (Mean Time Between Failure (MTBF))
1.35	Y/N	Scored	If batteries are used, are they replaceable without the need to replace the entire unit?
1.36	Short Answer	Scored	Define recommended annual maintenance requirements, and who is responsible
1.37	Y/N	Scored	Capable of using solar power options
1.38	Short Answer	Scored	Describe alerting mechanisms for sensor failure or anomolies
1.39	Short Answer	Scored	Describe or document estimated level of effort to decommission the system, including any vendor support dependencies
			Performance
1.40	Numeric	Scored	Define the vehicle count accuracy of the proposed technology (%)
1.41	Numeric	Scored	Define the pedestrian or bicycle count accuracy of the proposed technology (%)
1.42	Numeric	Scored	Define the mode classification accuracy of the proposed technology (%)
1.43	Numeric	Scored	Define the directional flow accuracy of the proposed technology (%)
1.44	Short Answer	Scored	Describe validation methodology used to establish accuracy metrics
1.45	Numeric	Scored	Define the minimum detectable object size at typical installation distance (feet or meters)
1.46	Numeric	Scored	Define any performance degradation in high density corridors or detection saturation points (%)
1.47	Numeric	Scored	Define the object detection latency (time for event to system record) in seconds or hertz
1.48	Numeric	Scored	Define the object detection minimum confidence threshold of level used, if applicable (%)
1.49	Numeric	Scored	Percent of target occulsion that will result in a missed detection by applicable target category (vehicle, pedestrian, etc.) (%)
1.50	Short Answer	Scored	Describe operability and peformance in low-light or streetlight conditions
1.51	Short Answer	Scored	Describe operability in adverse weather or precipitation (rain/snow)
1.52	Short Answer	Scored	Define temperature, ingress protection rating, humidity, and vibration specifications
			Data
1.53	Y/N	Scored	Capable of outputting data in accordance with the Curb Data Specification (CDS) or that can be transformed into CDS format
1.54	Y/N	Scored	Capable of outputting data in accordance with the Mobility Data Specification (MDS) or that can be transformed into MDS format
1.55	Y/N	Scored	Vendor includes or supports application programming interface(s) (APIs) for ingesting and exporting data
1.56	Multiple Choice	Scored	Technology supports various data formats (e.g. JSON, CSV, GeoJSON, etc.)
1.57	Y/N	Required	Technology supports data export without any proprietary software dependencies
1.58	Y/N	Scored	Sensor hardware information (e.g. battery level, system health, network strength) can be received and communicated by a 3rd party platform?
1.59	Y/N	Scored	Technology supports export of directional flow data
1.60	Numeric	Scored	Maximum data throughput (records or detected objects per second)
1.61	Short Answer	Scored	Describe the technology solution's data encryption (at rest and in transit), if applicable
1.62	Short Answer	Scored	Describe the technology solution's authentication methods
1.63	Short Answer	Scored	Capable of sending and receiving data with an integrated cellular router, SIM, or eSIM, or other
1.64	Multiple Choice	Scored	Define the mobile network classes available (e.g. 3G, 4G, 5G)
1.65	Short Answer	Scored	Describe other data storage and/or transmission options. (e.g. local storage, LAN)
1.66	Short Answer	Scored	In the event of a communication (not power) outage, describe how collected data is handled until communication is restored (e.g. queued, overwritten, lost)
1.67	Y/N	Required	Sensor system supports secure firmware updates (signed/encryted)
1.68	Short Answer	Scored	Describe vulnerability management and security patch processes
1.69	Y/N	Scored	Device is compliant with NIST cybersecurity framework or equivalent standards
1.70	Y/N	Required	City retains ownership of all data generated by the system
1.71	Y/N	Required	Sensor is able to disallow the collection or storage of personally identiable information (PII) that permits the identify of an individual to be determined or inferred (this can be accomplished via post-processing)

https://depts.washington.edu/toolkit/sites/default/files/toolkit_downloads/CurbOccupancyToolkit_rev.pdf 2 FixedCurbSensors

Question ID	Question Format	Required / Scored	Question	Response
			Fixed (Static) Data Collection Sensors (complete once for each proposed technology solution)	Please respond directly in this column, or reference the relevant page of your proposal that answers the given question.
			General
2.1	Multiple Choice	Scored	Specify if the hardware is offered for purchase or for rent or other hybrid model
2.2	Y/N	Required	Equipment is compliant with the Build America, Buy America (BABA) Act
2.3	Short Answer	Scored	Describe the optimal use case(s) for the proposed sensor technology (e.g. single space occupancy detection, vehicle counts, violation detection etc.)
2.4	Y/N	Scored	Capable of capturing data to measure curb occupancy and dwell time (by space or zone, day and time)
2.5	Short Answer	Scored	Is data for object recgonition or other detection functions processed on the field device or by a separate, remote system? Please describe.
2.6	Short Answer	Scored	Describe the available data collection intervals of the proposed sensor (e.g. real time/near-real time video, 1 second, 5 seconds, 30 seconds etc.)
			Fixed Mountable Sensors (not In-Ground) (skip if not applicable)
2.7	Y/N	Scored	Capable of detecting a violation of curb regulations in the area it monitors (by space or zone, day and time)
2.8	Y/N	Scored	Capable of detecting a violation of curb regulations proximally outside the area it monitors (e.g. double parking)
2.9	Y/N	Scored	Capable of identifying FHWA vehicle category classifications 1-13 or classifications as defined by the University of Washington Freight Lab		CurbOccupancyToolkit_rev.pdf
2.10	Y/N	Scored	Capable of detecting pedestrians, bicycles, or other multi-modal curb users
2.11	Short Answer	Scored	Describe maximum area covered by a single detection device when providing >95% accuracty for vehicle/bicycle/pedestrian detection
			Warranty and Technical Support
2.12	Numeric	Scored	Define standard warranty period (years)
2.13	Short Answer	Scored	Describe warranty coverage terms and exclusions
2.14	Short Answer	Scored	Describe technical support availability (hours, response time, service level agreements)
2.15	Y/N	Scored	Is 24/7 emergency technical support available
2.16	Y/N	Required	User manuals and technical documentation available in English
2.17	Multiple Choice	Scored	List all applicable compliance certifications (FCC certification for radio frequency compliance, UL, CE, NTCIP, other)
			Deployment and Operations
2.18	Short Answer	Scored	What is the recommened distance from a detection area? What angle offset from the detectors centerline for a target will still produce >95% detection accuracy?
2.19	Short Answer	Scored	Describe installation options and requirements (external installation crews, internal installers, reliance on City crews, etc.).
2.20	Numeric	Scored	Define the lead time (in days/weeks) needed to acquire and transport between contract agreement and deployment
2.21	Short Answer	Scored	Describe any potential delays in receiving units, and potential remedies to reduce lead time
2.22	Y/N	Scored	Requires lane or curb closure for installation
2.23	Y/N	Short Answer	Can the device be powered by hardwired connections? If so, describe connector type and power requirements
2.24	Numeric	Scored	Describe power consumption requirements (watts or amp draw at voltage)
2.25	Numeric	Scored	Battery backup duration in hours (if applicable)
2.26	Y/N	Scored	If batteries are used, are they replaceable without the need to replace the entire unit?
2.27	Y/N	Scored	Equipment meets IP (Ingress Protection) rating of IP66 of higher
2.28	Numeric	Scored	Expected hardware lifespan or replacement cadence in years (Mean Time Between Failure (MTBF))
2.29	Numeric	Scored	Recommended routine maintenance frequency in cycles per year
2.30	Y/N	Scored	Capable of using solar power options
2.31	Short Answer	Scored	Describe or document estimated level of effort to decommission the system, including any vendor support dependencies
			Performance
2.32	Numeric	Scored	Define the curb space vehicle occupancy detection accuracy of the proposed technology (%)
2.33	Numeric	Scored	Define the dwell time accuracy of the proposed technology, if computed by sensor (%)
2.34	Numeric	Scored	Define the vehicle or pedestrian classification accuracy of the proposed technology (%)
2.35	Numeric	Scored	Define the curb violation detection accuracy of the proposed technology (%)
2.36	Short Answer	Scored	Describe validation methodology used to establish accuracy metrics
2.37	Numeric	Scored	Define the event detection latency (time between event and classification by the device) in seconds or hertz
2.38	Numeric	Scored	Define the event detection minimum confidence threshold of level used, if applicable (%)
2.39	Numeric	Scored	What % occlusion of a detection target will cause the systyemt to fall below 95% detection accuracy?
2.40	Short Answer	Scored	Describe operability in low-light conditions
2.41	Short Answer	Scored	Describe operability in adverse weather or precipitation (rain/snow)
2.42	Short Answer	Scored	Define temperature, ingress protection rating, humidity, and vibration specifications
			Data
2.43	Y/N	Scored	Capable of outputting data in accordance with the Curb Data Specification (CDS) or that can be transformed into CDS format
2.44	Y/N	Scored	Capable of outputting data in accordance with the Mobility Data Specification (MDS) or that can be transformed into MDS format
2.45	Y/N	Scored	Technology includes or supports application programming interface(s) (APIs) for exporting data
2.46	Multiple Choice	Scored	Technology supports various data formats (e.g. JSON, CSV, GeoJSON, etc.)
2.47	Y/N	Required	Technology supports data export without any proprietary software dependencies
2.48	Short Answer	Scored	Describe the technology solution's data encryption (at rest and in transit), if applicable
2.49	Short Answer	Scored	Describe the technology solution's authentication methods
2.50	Short Answer	Scored	Capable of sending and receiving data with an integrated cellular router, SIM, or eSIM, or other
2.51	Short Answer	Scored	Describe the mobile network classes available (e.g. 3G, 4G, 5G)
2.52	Short Answer	Scored	Describe other data storage and/or transmission options. (e.g. local storage, LAN)
2.53	Y/N	Scored	Sensor hardware information (e.g. battery level, system health, network strength) can be received and communicated by a 3rd party platform?
2.54	Short Answer	Scored	Describe what data is produced and retained by the sensor as well as options for retention periods and any limitations on storage of data
2.55	Short Answer	Scored	In the event of a communication (not power) outage, describe how collected data is handled until communication is restored (e.g. queued, overwritten, lost)
2.56	Y/N	Required	City retains ownership of all data generated by the system
2.57	Y/N	Required	Sensor is able to disallow the collection or storage of personally identiable information (PII) that permits the identify of an individual to be determined or inferred (this can be accomplished via post-processing)

https://depts.washington.edu/toolkit/sites/default/files/toolkit_downloads/CurbOccupancyToolkit_rev.pdf 3 MobileSensorSystems

Question ID	Question Format	Required / Scored	Question	Response
			Mobile or Portable Curb Data Collection Systems (complete once for each proposed technology solution)	Please respond directly in this column, or reference the relevant page of your proposal that answers the given question.
			General
3.1	Multiple Choice	Scored	Specify if the hardware is offered for purchase or for rent or other hybrid model
3.2	Y/N	Required	Equipment is compliant with the Build America, Buy America (BABA) Act
3.3	Multiple Choice	Scored	Primary deployment modality (vehicle-mounted, handheld, trailer, aerial, temporary pole, other)
3.4	Short Answer	Scored	Describe effects of horizontol and vertical offset on data collection accuracy
3.5	Y/N	Scored	Is the sensor capable of measuring curb occupancy (by space or zone, day and time)?
3.6	Y/N	Scored	Is the sensor capable of measuring dwell time or collecting data to calculate dwell time (by space or zone, day and time)?
3.7	Y/N	Scored	Capable of measuring dwell time (by space or zone, day and time)?
3.8	Y/N	Scored	Capable of collecting curb asset inventory data (signs, markings, meters, obstructions)
3.9	Y/N	Scored	Capable of geolocating curb assets during mobile data collection
3.10	Short Answer	Scored	Describe curb inventory data elements that can be captured, if any
3.11	Y/N	Scored	Capable of identifying FHWA vehicle category classifications 1-13 or classifications as defined by the University of Washington Freight Lab		CurbOccupancyToolkit_rev.pdf
3.12	Y/N	Scored	Capable of detecting stopped and moving vehicles in traveled lanes
3.13	Numeric	Scored	Maximum coverage area per deployment (linear miles per hour or square miles per deployment)
3.14	Short Answer	Scored	Describe the optimal and maximum areas for data collection (e.g. single parking stall, block face, driving route, broad geographic area etc.)
3.15	Numeric	Scored	Maximum data capture speed, if applicable (mph at which system maintains stated accuracy)
3.16	Short Answer	Scored	Detail the mobility of the proposed sensor, such as how it can be deployed, redeployed, required support personnel, and the modality (e.g. battery powered temporary pole-mount, car-mounted, aerial, etc.).
3.17	Short Answer	Scored	Describe the available data collection intervals of the proposed sensor (e.g. real time video, 1 second, 3 seconds, etc.).
			Aerial Data Collection Operations (skip if not applicable)
3.18	Short Answer	Scored	Describe cadence of aerial data collection operations required (in-air time, frequency of deployments, number of times a space is covered per hour)
3.19	Short Answer	Scored	Describe personnel required to conduct aerial data collection operations, including any required pilots, observers, or support staff
3.20	Short Answer	Scored	Describe flight duration, altitude limits, and airspace restrictions
3.21	Y/N	Required	Is an FAA Part 107 compliant operation
3.22	Y/N	Scored	Capable of beyond-visual-line-of-sight (BVLOS) operations
3.23	Short Answer	Scored	Describe training requirements for operations
			Ground Vehicle-Mounted Data Collection Systems (skip if not applicable)
3.24	Short Answer	Scored	Describe the operational cadence required, including collection frequency, required driving routes, average revisit frequency for each curb space, and estimated vehicle hours per unit area
3.25	Short Answer	Scored	Describe personnel required to conduct vehicle-mounted data collection operations, including driver and operator requirements
3.26	Short Answer	Scored	Describe vehicle mounting requirements, including compatible vehicle types, installation requirements, calibration procedures, and any permanent or temporary modifications required
3.27	Short Answer	Scored	Describe operating constraints, including minimum or maximum travel speeds, weather limitations, roadway restrictions, or other operational considerations affecting data collection
3.28	Short Answer	Scored	Describe training requirements for personnel responsible for operating and maintaining the vehicle-mounted system	nauer
			Warranty and Technical Support
3.29	Numeric	Scored	Define standard warranty period (years)
3.30	Short Answer	Scored	Describe warranty coverage terms and exclusions
3.31	Short Answer	Scored	Describe technical support availability (hours, response time, service level agreements)
3.32	Y/N	Scored	Is 24/7 emergency technical support available
3.33	Y/N	Required	User manuals and technical documentation available in English
3.34	Short Answer	Scored	Describe alerting mechanisms for sensor failure or anomolies
3.35	Multiple Choice	Scored	List all applicable compliance certifications (FCC certification for radio frequency compliance, UL, CE, NTCIP, other)
			Deployment and Operations
3.36	Numeric	Scored	Define the lead time (in days/weeks) needed to acquire and transport hardware between contract agreement and deployment
3.37	Short Answer	Scored	Describe any potential delays in receiving units, and potential remedies to reduce lead time
3.38	Numeric	Scored	Define number of personnel required for deployment and operation (personnel/sensor or unit area)
3.39	Y/N	Scored	Can be deployed and operated by City Staff without vendor support
3.40	Y/N	Scored	Technology requires specialized vehicle or platform for operation
3.41	Multiple Choice	Scored	Describe how device is powered (solar, battery, vehicle plugin, hybrid)
3.42	Y/N	Scored	Technology requires unique or proprietary connector or equipment to receive power from vehicle or other source
3.43	Y/N	Scored	Technology requires lane or curb closure during deployment
3.44	Numeric	Scored	Define maximum daily operational duration per deployment (hours)
3.45	Numeric	Scored	Define maximum continuous operating time (hours)
3.46	Numeric	Scored	Define recommended frequency of redeployment for effective coverage (days or weeks)
3.47	Short Answer	Scored	Describe system calibration requirements and frequency
3.48	Y/N	Scored	If batteries are used, are they replaceable without the need to replace the entire unit?
3.49	Short Answer	Scored	Describe downtime requirements between deployments
3.50	Y/N	Scored	Equipment meets IP (Ingress Protection) rating of IP65 of higher
3.51	Numeric	Scored	Expected hardware lifespan or replacement cadence in years (Mean Time Between Failure (MTBF))
3.52	Numeric	Scored	Recommended routine maintenance frequency in cycles per year
			Performance
3.53	Numeric	Scored	Define the occupancy detection accuracy of the proposed technology (%)
3.54	Numeric	Scored	Define the vehicle classification accuracy of the proposed technology (%)
3.55	Short Answer	Scored	Describe validation methodology used to establish accuracy metrics
3.56	Numeric	Scored	Define the event detection latency (time for event to system record) in seconds or minutes
3.57	Numeric	Scored	Define the event detection minimum confidence threshold of level used, if applicable (%)
3.58	Numeric	Scored	Define accuracy impacts of operations and detection under partial occlusion (%)
3.59	Short Answer	Scored	Describe operability in low-light conditions
3.60	Short Answer	Scored	Describe operability in adverse weather or precipitation (rain/snow)
3.61	Short Answer	Scored	Define temperature, ingress protection rating, humidity, and vibration specifications
			Data
3.62	Y/N	Scored	Capable of outputting data in accordance with the Curb Data Specification (CDS) or that can be transformed into CDS format
3.63	Y/N	Scored	Capable of outputting data in accordance with the Mobility Data Specification (MDS) or that can be transformed into MDS format
3.64	Y/N	Required	Technology includes or supports application programming interface(s) (APIs) exporting data
3.65	Y/N	Required	Technology supports various data formats (e.g. JSON, CSV, GeoJSON, etc.)
3.66	Y/N	Required	Technology supports data export without any proprietary software dependencies
3.67	Short Answer	Scored	Describe the mobile network classes available (e.g. 3G, 4G, 5G)
3.68	Short Answer	Scored	Describe other data storage and/or transmission options. (e.g. local storage, LAN)
3.69	Y/N	Required	Sensor data outputs can be received and ingested by a 3rd party platform
3.70	Y/N	Scored	Sensor hardware information (e.g. battery level, system health, network strength) can be received and communicated by a 3rd party platform
3.71	Y/N	Required	Technology supports geospatial tagging of collected data
3.72	Numeric	Scored	Define spatial resolution of data (feet, meters, other unit)
3.73	Short Answer	Scored	Describe the technology solution's data encryption (at rest and in transit), if applicable
3.74	Short Answer	Scored	Describe the technology solution's authentication methods
3.75	Short Answer	Scored	If applicable, in the event of a communication (not power) outage, describe how collected data is handled until communication is restored (e.g. queued, overwritten, lost)
3.76	Y/N	Required	City retains ownership of all data generated by the system
3.77	Y/N	Required	Sensor is able to disallow the collection or storage of personally identiable information (PII) that permits the identify of an individual to be determined or inferred (this can be accomplished via post-processing)

https://depts.washington.edu/toolkit/sites/default/files/toolkit_downloads/CurbOccupancyToolkit_rev.pdf 4 EmergencyDynamicCurbControl

Question ID	Question Format	Required / Scored	Question	Response
			Emergency and Dynamic Curb Control Integration Systems (complete once for each proposed technology solution)	Please respond directly in this column, or reference the relevant page of your proposal that answers the given question.
			General
4.1	Multiple Choice	Scored	Please specify if the system is provided as software, platform, or integrated solution (software-only / software + hardware / SaaS / hybrid)
4.2	Short Answer	Scored	Where is the system hosted (cloud provider, on-premise, hybrid)?
4.3	Y/N	Required	Capable of storing data in accordance with the Curb Data Specification (CDS)
4.4	Y/N	Required	Capable of storing data in accordance with the Mobility Data Specification (MDS)
4.5	Y/N	Required	Capable of transmitting and receiving data in accordance with the Curb Data Specification (CDS)
4.6	Y/N	Required	Capable of transmitting and receiving data in accordance with the Mobility Data Specification (MDS)
4.7	Y/N	Required	Equipment is compliant with the Build America, Buy America (BABA) Act
4.8	Y/N	Required	System supports creation and management of geofenced curb zones (polygon-based)
4.9	Y/N	Scored	System supports real-time updates to curb regulations and zone status
4.10	Numeric	Scored	Maximum number of concurrent active geofenced zones supported
4.11	Numeric	Scored	Minimum geofence resolution (smallest definable area in feet or meters)
			Deployment and Operations
4.12	Numeric	Scored	Define time required to configure and activate a new geofenced zone (minutes)
4.13	Numeric	Scored	Define time required to update an existing zone with modified closure or regulation (seconds or minutes)
4.14	Y/N	Scored	System allows City staff to define and update geofence parameters without vendor intervention
4.15	Y/N	Scored	System can be operated entirely by City staff without vendor support
4.16	Y/N	Scored	Can be deployed and operated by City Staff without vendor support
4.17	Y/N	Scored	System includes user roles and permissions management
4.18	Y/N	Scored	System supports audit logging of changes to curb zones and regulations
4.19	Numeric	Scored	Define system uptime commitment on a monthly basis
4.20	Short Answer	Scored	Describe system redundancy and failover architecture
			Performance
4.21	Numeric	Scored	Define time from zone update to system-wide database propagation (seconds)
4.22	Numeric	Scored	Define time from zone update to external system availability (API latency) (seconds)
4.23	Numeric	Scored	Define maximum supported event or closure update frequency (updates per minute)
4.24	Numeric	Scored	Define accuracy of geofence representation relative to defined boundaries (%)
4.25	Y/N	Scored	System supports real-time event triggering (e.g. emergency closures, temporary restrictions)
			Data
4.26	Y/N	Required	System supports API-based integration with external systems (e.g. 911, permitting, traffic management systems)
4.27	Y/N	Scored	System supports bidirectional data exchange via API
4.28	Multiple Choice	Scored	Supported API formats (REST, GraphQL, other)
4.29	Y/N	Scored	System supports webhook or event-based notifications
4.30	Y/N	Scored	System supports real-time data streaming (e.g. event feeds)
4.31	Y/N	Scored	System supports export of geofence and regulation data in non-proprietary formats
4.32	Multiple Choice	Scored	Supported export formats (JSON, CSV, GeoJSON, other)
4.33	Y/N	Required	System supports data export without proprietary software dependencies
4.34	Short Answer	Required	Describe authentication and authorization methods (e.g. OAuth, API keys)
4.35	Short Answer	Scored	Describe data encryption methods (at rest and in transit)
4.36	Y/N	Required	System is able to disallow the collection or storage of personally identiable information (PII) that permits the identify of an individual to be determined or inferred (this can be accomplished via post-processing)

5 DynamicCurbCommsDisplay

Question ID	Question Format	Required / Scored	Question	Response
			Dynamic Curb Communication and Display Systems (complete once for each proposed technology solution)	Please respond directly in this column, or reference the relevant page of your proposal that answers the given question.
			General
5.1	Multiple Choice	Scored	Please specify if the system is provided as hardware, software, or integrated solution (hardware-only, software-only, integrated, SaaS, hybrid)
5.2	Y/N	Required	Equipment is compliant with the Build America, Buy America (BABA) Act
5.3	Short Answer	Scored	Display type (VMS board, digital signage, e-ink, LCD, LED, other)
5.4	Multiple Choice	Scored	Define system display type (color, monochrome)
5.5	Multiple Choice	Scored	Define display format (character-based, bitmap, hybrid, other)
5.6	Numeric	Scored	Define display resolution (horizontol x vertical)
5.7	Numeric	Scored	Define display size (width x height)
5.8	Numeric	Scored	Define pixel pitch (mm)
5.9	Y/N	Scored	System is capable of rendering symbols, icons, or graphics
5.10	Y/N	Scored	Capable of displaying regulatory information (e.g. restrictions, time-based rules)
5.11	Y/N	Scored	Capable of displaying wayfinding or availability information
5.12	Y/N	Scored	Capable of supporting multiple message formats (text, symbols, icons)
			Deployment and Operations
5.13	Multiple Choice	Scored	Select typical installation type(s) (fixed roadside, pole-mounted, signal arm, trailer-mounted, portable, other)
5.14	Numeric	Scored	Define display size (width x height)
5.15	Numeric	Scored	Define display weight (lbs or grams)
5.16	Y/N	Scored	Requires lane or curb closure for installation
5.17	Y/N	Required	Capable of direct power connection from light pole or other power source
5.18	Numeric	Scored	Battery backup duration in hours (if applicable, zero hours if not applicable)
5.19	Numeric	Scored	Expected hardware lifespan or replacement cadence in years (Mean Time Between Failure (MTBF))
5.20	Numeric	Scored	Recommended routine maintenance frequency in cycles per year
5.21	Numeric	Scored	Describe power consumption requirements (watts or amp draw at voltage)
5.22	Y/N	Scored	Capable of receiving all or some power via solar panel
5.23	Y/N	Scored	Can be installed and operated by City staff without vendor support
5.24	Short Answer	Scored	Describe mounting requirements and site constraints
			Performance
5.25	Numeric	Scored	Define message update latency (time from system command to display update) (seconds or hertz)
5.26	Numeric	Scored	Define visibility distance (feet or meters under standard conditions)
5.27	Numeric	Scored	Define maximum and minimum brightness (nits or equivalent)
5.28	Y/N	Scored	Technology supports automatic brightness adjustment based on ambient light
5.29	Y/N	Scored	Technology supports manual brightness adjustment
5.30	Numeric	Scored	Define recovery time from power interruption (minutes or seconds)
5.31	Y/N	Scored	Capable of confirming message delivery and display status back to central system
5.32	Short Answer	Scored	Describe operability in adverse weather or precipitation (rain/snow)
5.33	Short Answer	Scored	Define temperature, ingress protection rating, humidity, and vibration specifications
			Data
5.34	Short Answer	Scored	Describe technology update control protocol
5.35	Y/N	Scored	Technology supports integration with emergency or dynamic curb control systems
5.36	Y/N	Required	Technology supports remote configuration and management
5.37	Short Answer	Scored	Define available or included communication interfaces
5.38	Y/N	Scored	System supports operation without requiring proprietary software for functionality
5.39	Short Answer	Scored	If an internal cellular router is used, describe the mobile network classes available (e.g. 3G, 4G, 5G)
5.40	Y/N	Scored	Sensor hardware information (e.g. battery level, system health, network strength) can be received and communicated by a 3rd party platform?
5.41	Y/N	Required	System is able to disallow the collection or storage of personally identiable information (PII) that permits the identify of an individual to be determined or inferred (this can be accomplished via post-processing)

6 CurbMobilityDataAggregation

Question ID	Question Format	Required / Scored	Question	Response
			Curb and Mobility Data Aggregation System (complete once for each proposed technology solution)	Please respond directly in this column, or reference the relevant page of your proposal that answers the given question.
			General
6.1	Multiple	Scored	Please define the system deployment model (cloud-hosted, on-premise, hybrid, SaaS)
6.2	Short Answer	Scored	Where is the system hosted (cloud provider, on-premise, hybrid)?
6.3	Y/N	Required	Capable of outputting data in accordance with the Curb Data Specification (CDS)
6.4	Y/N	Required	Capable of outputting data in accordance with the Mobility Data Specification (MDS)
6.5	Y/N	Required	System can integrate with 3rd party sensor technologies
6.6	Y/N	Required	System capable of ingesting meter payment events and data from Flowbird and IPS Group
6.7	Y/N	Scored	System includes a real-time or near real-time spatial mapping interface
6.8	Y/N	Scored	System can process and visualize real time CDS Events and Metrics feeds (e.g. occupancy status, violations, revenue etc.)
6.9	Y/N	Scored	System facilitates aggregation of data across multiple vendors, APIs, and/or data feeds
6.10	Y/N	Required	System can represent curb assets, zones, spaces, and regulations consistent with CDS Curbs API
6.11	Multiple Choice	Scored	Specify use of a 3rd-party mapping service (ESRI, OpenStreetMap, QGIS, Mapbox, Google Maps, CARTO, other) for spatial visualization
6.12	Y/N	Required	Systems allows project team and City staff to create, edit, and manage curb zones, areas, and regulations
			General
6.13	Short Answer	Scored	Describe onboarding process, tutorials, and training available for City staff on system operation and platform navigation
6.14	Short Answer	Scored	Describe technical support availability (hours, response time, service level agreements)
6.15	Y/N	Scored	Is 24/7 emergency technical support available
6.16	Y/N	Required	User manuals and technical documentation available in English
6.17	Y/N	Scored	System is accessible via mobile devices (responsive web or native web)
6.18	Y/N	Scored	System support field-based data entry or verification
6.19	Multiple Choice	Scored	List applicable security/compliance certifications (SOC 2, FedRAMP, ISO 27001, other)
			Deployment and Operations
6.20	Numeric	Scored	Define estimated time required to configure and deploy the system for initial operation (days or weeks) on the study area corridors described in Attachment B of the RFP
6.21	Numeric	Scored	Define time required to onboard a new data source via a typical vendor API (hours or days)
6.22	Y/N	Scored	System can be operated by City staff without vendor support
6.23	Y/N	Scored	Project team and City staff can configure dashboard displays without vendor intervention
6.24	Short Answer	Scored	Describe the process for requesting and implementing dashboard tools and visual changes
6.25	Y/N	Scored	System supports role-based user access and permissions
6.26	Y/N	Scored	System supports audit logging of configuration changes and data access
6.27	Short Answer	Scored	Describe software system maintenance requirements and update processes
6.28	Short Answer	Scored	Describe vendor support requirements for ongoing operations
6.29	Short Answer	Scored	Describe procedures for data migration or export upon contract termination
			Performance
6.30	Numeric	Scored	Define maximum data ingestion rate (records per second)
6.31	Numeric	Scored	Define maximum number of connected data sources supported (e.g. CAD, unique vendor APIs)
6.32	Y/N	Scored	System supports real-time event triggering and alerting
6.33	Numeric	Scored	Define time required to publish or update curb regulation changes system-wide (seconds)
6.34	Numeric	Scored	Define API response latency for dynamic communications and signage (milliseconds or seconds)
6.35	Numeric	Scored	Define system uptime commitment or benchmark (%)
6.36	Numeric	Scored	Define recovery time after power restoration following an interruption (minutes or seconds)
6.37	Short Answer	Scored	Describe alerting mechanisms and notification delivery methods (email, SMS, in-app, webhook, etc.)
			Data
6.38	Y/N	Required	System provides API access for data ingestion and export
6.39	Short Answer	Scored	System may support integration with external systems (e.g., permitting, enforcement, traffic systems) (reference case study or experience)
6.40	Multiple Choice	Scored	Data can be filtered or queried (timeframe, zone, area, neighborhood, corridor, vehicle class, permit type, paid, dwell time, other)
6.41	Short Answer	Scored	Describe methodology for comparing curb events data from sensors with meter payment data
6.42	Y/N	Required	System supports data export in non-proprietary formats
6.43	Multiple Choice	Scored	Supported data formats (JSON / CSV / GeoJSON / other)
6.44	Short Answer	Scored	Describe data backup frequency and recovery procedures
6.45	Y/N	Scored	System supports bidirectional API communication
6.46	Y/N	Scored	System supports real-time data streaming (event feeds or webhooks)
6.47	Numeric	Scored	Define API rate limits (requests per second or minute)
6.48	Y/N	Required	System allows full data extraction without vendor intervention
6.49	Y/N	Required	City retains ownership of all data generated by the system
6.50	Y/N	Scored	System supports database schema versioning and backward compatibility
6.51	Y/N	Scored	System provides documentation for all APIs and data schemas
6.52	Short Answer	Scored	Describe data encryption methods (at rest and in transit)
6.53	Short Answer	Scored	Describe authentication and authorization methods
6.54	Y/N	Scored	System supports multi-tenant or multi-jurisdictional department configurations (role, department, or jurisdiction-based data access)
6.55	Y/N	Scored	System includes pre-built reports for curb utilization, violations, and revenue capture
6.56	Y/N	Scored	System supports custom report generation by City staff
6.57	Y/N	Scored	System supports scheduled/automated report delivery
6.58	Short Answer	Scored	Describe approach to maintaining compatibility with future CDS schema updates
6.59	Short Answer	Scored	Describe data retention policies and limitations
6.60	Y/N	Required	System is able to disallow the collection or storage of personally identiable information (PII) that permits the identify of an individual to be determined or inferred (this can be accomplished via post-processing)

7 FreightVehicleData

Question ID	Question Format	Required / Scored	Question	Response
			Freight and Commercial Vehicle Data Package	Please respond directly in this column, or reference the relevant page of your proposal that answers the given question.
			General
7.1	Y/N	Required	System is compliant with the Build America, Buy America (BABA) Act
7.2	Multiple Choice	Scored	Data source type (telematic, GPS probe, fleet data, delivery platform, aggregated 3rd-party, other)
7.3	Short Answer	Scored	Describe the primary source(s) of the data (e.g. fleet operators, mobile devices, third-party aggregators)
7.4	Y/N	Scored	Data includes FHWA vehicle category classifications 1-13
7.5	Y/N	Scored	Data includes stop or dwell activity
7.6	Y/N	Scored	Data includes curbside activity indicators (e.g. loading, unloading, parking)
7.7	Multiple Choice	Scored	Specify geographic coverage and granularity (citywide, corridor-level, neighborhood-level, other)
7.8	Short Answer	Scored	Describe technical support availability (hours, response time, service level agreements)
7.9	Y/N	Scored	Is 24/7 emergency technical support available
7.10	Y/N	Required	User manuals and technical documentation available in English
7.11	Y/N	Reviewed if available	Vendor can provide sample dataset or proof-of-concept for evaluation prior to contract
			Deployment and Operations
7.12	Numeric	Scored	Define time required to provision and deliver initial dataset (days)
7.13	Multiple Choice	Scored	Define update frequency of data delivery (minutes, hours, daily, weekly)
7.14	Y/N	Scored	Data is available via API
7.15	Y/N	Scored	Data can be accessed and used by City staff without vendor-managed interface
7.16	Y/N	Scored	Dataset requires ongoing vendor-managed processing or enrichment
7.17	Short Answer	Scored	Describe any dependencies on 3rd-party data providers or partnerships
7.18	Short Answer	Scored	Describe licensing or usage restrictions associated with the dataset
			Performance
7.19	Numeric	Scored	Define temporal resolution of data (seconds, minutes, or hours)
7.20	Numeric	Scored	Define spatial resolution of data (feet, meters, or block-level granularity)
7.21	Numeric	Scored	Define percent of freight or commercial vehicle activity captured relative to estimated total activity or other data capture metric (%)
7.22	Numeric	Scored	Define average data latency (time from activity occurrence to database availability) in minutes or hours
7.23	Numeric	Scored	Define accuracy of vehicle classification (%)
7.24	Numeric	Scored	Define accuracy of trip or stop detection (%)
7.25	Y/N	Scored	Data may support identification of recurring patterns (e.g., frequent delivery locations, peak times)
7.26	Short Answer	Scored	Describe validation methodology used to establish accuracy metrics
			Data
7.27	Y/N	Required	Data can be exported in non-proprietary formats
7.28	Multiple Choice	Scored	Supported data formats (CSV, JSON, GeoJSON, other)
7.29	Y/N	Required	Data can be integrated with external systems via API
7.30	Y/N	Scored	Data supports geospatial referencing (coordinates, segments, or zones)
7.31	Short Answer	Scored	Describe known data limitations or geographic coverage gaps
7.32	Short Answer	Scored	Describe authentication and authorization methods for data access
7.33	Y/N	Scored	Specify historical data access window (years)
7.34	Numeric	Scored	Define maximum historical data retention period available (months or years)
7.35	Y/N	Required	City retains rights to use data for planning, policy, and operational purposes
7.36	Short Answer	Scored	Describe available analytics capabilities beyond raw data delivery
7.37	Y/N	Required	Data does not include personally identifiable information (PII), or is anonymized to prevent identification
7.38	Short Answer	Scored	Describe anonymization and privacy protection methods
7.39	Short Answer	Scored	Describe any limitations on data sharing, redistribution, or publication. Provide sample licensing agreement if applicable

File details come from the government source that posted it. Updated Aug 26, 2026.