The City of Seattle is issuing this Request for Information (RFI) to better understand the parking enforcement technology solutions currently available in the marketplace. This RFI is intended to gather information regarding product capabilities, implementation approaches, integration strategies, commercial models, and industry best practices.This RFI is for information-gathering purposes only and does not constitute a solicitation for bids or proposals, nor does it obligate the City to procure any products or services. Information received through this process may be used to refine the City’s requirements, inform future procurement strategies, and evaluate potential approaches to modernizing parking enforcement operations.Respondents are encouraged to describe innovative capabilities and recommend approaches that address the City’s operational objectives, including features or solutions that may not be explicitly requested within this document.

If you have not previously done so, register at: https://procurement.opengov.com/portal/seattle, then subscribe to the City’s Procurement Portal. The Procurement Portal is used by City staff to identify companies for future solicitation lists and check certifications. Women- and minority-owned firms are asked to self-identify their business as such in OpenGov. Registration in the City's Procurement Portal is required to submit a response to this solicitation.

The Seattle Police Department (SPD) is issuing this Request for Information (RFI) to gather information about commercially available technologies that support modern parking enforcement operations.This RFI is intended solely for information gathering and market research purposes. It is not a solicitation for proposals, bids, pricing, or contractual commitments. Information received may be used to help define future procurement strategies and requirements.SPD is seeking to better understand available technologies, implementation approaches, integration capabilities, and innovative solutions that improve parking enforcement operations while supporting future operational needs.

Washington’s ESSB 6002, codified as chapter 10.130 RCW, establishes statewide requirements governing the use of automated license plate reader technology. The City is also subject to Seattle’s Surveillance Ordinance, SMC 14.18, and applicable City-approved ALPR policies. The City intends to provide and maintain mapping of designated no-collection zones around sensitive facilities.Any proposed ALPR solution must support configurable geofencing and no-collection-zone controls, audit trail logging, configurable data-retention and deletion requirements, and controls governing system access and data sharing.Please describe how your solution:Configures and applies City-provided maps of designated no-collection zones.Prevents ALPR data collection when equipment is operating within a designated no-collection zone.Updates designated no-collection zones as legal requirements and City mapping evolves.Validates that geofencing and no-collection-zone controls are functioning correctly after implementation and following subsequent mapping or configuration updates.Supports auditing and exportable reporting of geofencing and no-collection-zone compliance.Supports configurable data-retention schedules and automated deletion. Under ESSB 6002, ALPR data retained for parking enforcement must be deleted no later than 12 hours after final disposition of a parking-enforcement case, including exhaustion of any applicable appeals process (section 4(2)).Supports technical controls against unauthorized access or use, including unauthorized data sharing, secondary transfer, or access by nonauthorized agencies (section 5(6)).Prevents the selling, leasing, renting, or otherwise allowing access to ALPR data by any nonauthorized agency, person, or entity (section 5(7)).Logs every access to or query of the ALPR system, including the user’s identity and affiliation, date and time, query data elements, purpose, associated call-for-service or case number, and camera location. Describe how the solution also logs exports, downloads, and sharing; makes vendor-generated audit trail data available to the City; and retains audit trail data for at least two years (section 8).Allows authorized users to manually suspend and resume ALPR data collection when operationally necessary. Include any associated permissions, supervisory controls, and audit logging.Limits ALPR data collection to the intended enforcement area and prevents the capture of license plates from private parking lots, designated no-collection zones, or other locations where collection is not authorized, including when the ALPR-equipped vehicle is operating near the boundary of a zone. Include any associated configuration or control capabilities.Defaults all data-sharing settings to prevent unauthorized sharing and requires the City’s knowledge and explicit consent before the vendor makes any change, including a software update, that may affect sharing permissions (section 5(8)).

The City will evaluate proposals using the criteria specified below. Responses will be evaluated and ranked or scored.

The City strongly prefers that all vendor communications concerning this acquisition be submitted through the Procurement Portal. If necessary, you may also direct your communications to the contact below. The RFI Coordinator is:Elena Blackmore(206) 883-6405elena.blackmore2@seattle.govUnless authorized by the RFI Coordinator, no other City official or City employee is empowered to speak for the City regarding this acquisition. Any Responder seeking to obtain information, clarification, or interpretations from any other City official or City employee (other than the RFI Coordinator) is advised that such material is used at the Responder’s own risk. The City will not be bound by any such information, clarification, or interpretation.

SPD currently operates within an environment that includes multiple independent systems supporting:Parking citation issuanceAutomated License Plate Recognition (ALPR)GIS and curb regulationData analyticsResidential and commercial permit programsParking payment systemsPhysical chalking for time limit enforcementCourt case processingScofflaw enforcementHotsheet and officer safety alertsCustomer service requestsReporting and analyticsVehicle towing and impound workflowsDaily report of activities by the enforcement officer

Parking Enforcement currently utilizes a combination of multiple systems, data sources, and manual processes to support citation issuance, Automated License Plate Recognition (ALPR), permit validation, parking payment verification, GIS-based enforcement, court workflows, customer service requests, reporting, and other operational functions.As operational needs continue to evolve, SPD is evaluating opportunities to modernize these processes by reducing manual work, improving interoperability between systems, increasing operational efficiency, and providing enhanced tools for field staff and supervisors.SPD is interested in understanding how available vendor solutions streamline parking enforcement operations, and what other innovative capabilities are available to improve enforcement operations, operational decision-making, and future service delivery.

Responders must complete the attached RFI Response Template and submit the completed template, along with any optional supporting documentation.

A. Solution OverviewPlease provide an overview of your solution, including:Primary capabilitiesOverall system architectureDeployment model (e.g., Saas, cloud, on-premises, hybrid)Mobile capabilities (iOS vs Android, cell phone vs dedicated ticket writer)Describe the types of agencies currently using your solution. Where applicable, include examples of organizations of similar size and operational scope.How your solution differs from traditional parking enforcement platformsB. Parking Enforcement ModernizationDescribe how your solution modernizes parking enforcement operations.Examples may include:Reducing manual processes and paperworkStreamlining officer workflowsImproving operational efficiencyImproving officer safetyIncreasing data qualitySupporting future operational growthSeamlessly integrating with other softwareProtecting privacy of the publicPlease describe any capabilities that distinguish your platform from traditional parking enforcement solutions.C. Citation and ALPR WorkflowDescribe how your solution supports the complete parking enforcement lifecycle, including:License plate recognitionCitation issuanceEvaluation of multiple parking restrictions simultaneouslyPermit verificationParking payment verificationScofflaw identificationOfficer safety alertsCitation lifecycle managementMobile workflowsDescribe the operator controls available during ALPR enforcement, including any capabilities to configure or select the capture area, side of the street, direction of travel, or parking restrictions being enforced.D. GIS, Mapping, and GeofencingDescribe how your solution supports:GIS-based enforcementDynamic curb regulationsBlockface and side-of-street restrictionsResidential permit zonesTemporary parking restrictionsTemporary No Parking ZonesPermit layersGeofencingGIS visualizationPlease describe:How GIS information is maintainedHow updates are appliedHow quickly changes become available in the fieldHow users verify GIS accuracyE. System IntegrationDescribe your platform’s integration capabilities with municipal systems such as:Permit managementCourt systemsGIS platformsParking payment systemsCustomer service request systemsCAD or dispatch systemsReporting platformsBusiness intelligence platformsPlease describe:Standard APIsAvailable integration methodsSupport for batch and real-time integrationsTypical implementation approach for new integrationsSupport for future system integrationsIf your solution requires third-party products or services to provide functionality described in this RFI, please identify those products and explain how they are licensed, supported, and integrated.F. Reporting and AnalyticsDescribe the reporting and analytical capabilities available within your solution.Examples include:Operational dashboardsManagement reportingGIS visualizationCompliance analysisDeployment analysisEnforcement trend analysisOperational performance metricsBusiness intelligenceLogging and audit trailsPlease provide examples of how agencies use these capabilities to improve operations.G. Towing and Impound WorkflowsDescribe how your solution supports electronic towing and impound workflows.Examples may include:Electronic tow requestsTow status updatesElectronic documentationImpound trackingIntegration with third-party towing softwareIntegration with future towing platformsThe City does not currently utilize an integrated electronic towing workflow for Parking Enforcement. Please describe how your solution could support or integrate with future electronic towing processes and identify any technical or operational dependencies required.H. Future InnovationSPD is interested in understanding capabilities that extend beyond current operational needs.Please describe any existing or planned capabilities related to:Parking occupancy analysisCurb utilization analysisTransportation planningSign inventory or sign validationOperational planningWorkforce deployment optimizationArtificial intelligenceMachine learningOther innovative capabilities that may improve municipal parking enforcement or transportation operationsInclude any additional capabilities you believe the City should consider, even if they were not specifically requested in this RFI.I. Solution DemonstrationIf selected for a future demonstration, what capabilities would you demonstrate to best showcase your solution?Examples may include:Citation issuanceALPR enforcementGIS and mappingPermit validationParking payment verificationReporting and dashboardsMobile workflowsAdministrative functionsPlease identify any capabilities that are unique or differentiate your solution.

SPD will host a pre-response virtual information session on August 13, 2026 at 11:30 a.m. PT via MS Teams and will be 60-90 minutes in duration. At this conference, potential respondents may ask questions about the RFI process. Participants are reminded that no answers issued verbally at the session are binding on the City and any information provided at the session, unless it is later issued in writing, also is not binding on the City.

Please describe:Typical implementation methodologyTypical implementation timelineCustomer responsibilitiesVendor responsibilitiesData migration approachUser trainingTesting approachPost-implementation supportIdentify any implementation dependencies involving third-party systems such as permitting, GIS, court, payment, towing, or other municipal systems.

Responses to this RFI will be reviewed by a committee consisting of representatives from the Seattle Police Department, the Seattle Department of Transportation, and other relevant City stakeholders. The City’s intent is to better understand the parking enforcement technology solutions, capabilities, and commercial approaches currently available in the market.During its review, the City may request clarification or additional information from respondents and may conduct oral or written follow-up discussions. Following review of the written responses, the City may invite selected respondents to participate in scripted product demonstrations or other follow-up sessions. The City may determine which respondents are invited based on the relevance and completeness of their RFI responses. Participation in this RFI does not guarantee an invitation to demonstrate, nor does it guarantee participation in any future procurement. To support a consistent review, the City will provide substantially equivalent demonstration instructions and scenarios to invited respondents.The City may consider the following general areas when reviewing responses:Completeness, clarity, and relevance of the response.Ability to support the scope and complexity of the City’s parking enforcement operations.Parking citation, ALPR, permitting, payment, GIS, towing, reporting, and related workflow capabilities.Compliance with applicable ALPR, privacy, security, retention, audit, and surveillance requirements.Integration capabilities and interoperability with existing and future City systems.User experience for parking enforcement personnel, administrators, supervisors, and other stakeholders.Implementation, data migration, training, support, and ongoing service approach.Experience supporting public-sector organizations of similar size and complexity.Licensing, hosting, pricing, and commercial models.Financial stability, product roadmap, and ability to adapt to future operational, technical, and legislative changes.

All communications and/or questions regarding this RFI must be directed to Elena Blackmore, Strategic Advisor, SPD.EMAIL: Elena.Blackmore2@seattle.gov PHONE: 206-883-6405

Please provide:Company overviewRelevant municipal experienceNumber of parking enforcement implementationsReferences from similar agencies (if available)Typical customer sizeProduct roadmap (optional)

This RFI is for market research only, and SPD is not requesting formal pricing proposals. Instead, the City is seeking implementation approaches, support offerings and other commercial considerations.Deployments, Licensing, and Commercial Model Please describe:How your solution is licensed or priced (e.g., subscriptions, perpetual license, transaction-based, etc.).Primary pricing drivers (e.g., users, vehicles, hardware, storage, transactions, modules).If multiple deployment options are available, describe differences in licensing, functionality, maintenance responsibilities, or support.Solution ComponentsPlease identify:Functionality included in the standard offeringOptional modules or separately licensed capabilitiesThird-party products commonly requiredImplementation CostsDescribe:Activities that commonly generate implementation costsTypical customer effort during implementationTypical integration effortSupport and MaintenanceDescribe:Support modelMaintenance modelSoftware update processUpgrade policySystem uptime percentage (excluding scheduled maintenance)IntegrationsDescribe:How integrations are licensed or pricedWhether APIs are includedAny additional costs associated with custom integrations or ongoing maintenanceCooperative PurchasingPlease identify whether your solution is currently available through cooperative purchasing vehicles (e.g., NASPO ValuePoint or other cooperative contracts).Budgetary Information (Optional)If available, please provide representative pricing ranges, budgetary estimates, or examples from similar municipal implementations. These estimates are requested solely for planning purposes and will not be considered binding.

The City will not be liable for any costs incurred by the Responder in the preparation and presentation of materials submitted in response to this RFI including, but not limited to, costs incurred in connection with the Responder’s participation in demonstrations and the pre-information conference.

Please provide any additional information that would help SPD better understand your solution, implementation approach, future product direction, or capabilities that may benefit Parking Enforcement but were not specifically requested in this RFI.The City welcomes recommendations regarding industry best practices, emerging technologies, and innovative approaches that may improve municipal parking enforcement operations.

Prior to the closing date and time established for this RFI, a Vendor may change or correct its submission by following the Instructions here: https://opengov.my.site.com/support/s/article/4f4218bf-7da6-4fc6-b0c3-7eade0776ebe. No change to response shall be made after the RFI closing date and time.

The State of Washington’s Public Records Act (Release/Disclosure of Public Records) Under Washington State Law (reference RCW Chapter 42.56, the Public Records Act) all materials received or created by the City of Seattle are considered public records. These records include but are not limited to bid or proposal submittals, agreement documents, contract work product, or other bid material.The State of Washington’s Public Records Act requires that public records must be promptly disclosed by the City upon request unless that RCW or another Washington State statute specifically exempts records from disclosure. Exemptions are narrow and explicit and are listed in Washington State Law (Reference RCW 42.56 and RCW 19.108). Marking Your Records Exempt from Disclosure (Protected, Confidential, or Proprietary)As mentioned above, all City of Seattle offices (“the City”) are required to promptly make public records available upon request. However, under Washington State Law some records or portions of records are considered legally exempt from disclosure and can be withheld. A list and description of records identified as exempt by the Public Records Act can be found in RCW 42.56 and RCW 19.108.If you believe any of the records you are submitting to the City as part of your bid/proposal or contract work products, are exempt from disclosure you can request that they not be released before you receive notification. To do so you must complete the City Non-Disclosure Request Form (“the Form”) provided by Purchasing and Contracting (see attached Form as part of the Vendor Questionnaire), very clearly and specifically identify each record and the exemption(s) that may apply, and submit a copy of your records with the specified exemptions redacted. (If you are awarded a City contract, the same exemption designation will carry forward to the contract records.)The City will not withhold materials from disclosure simply because you mark them with a document header or footer, page stamp, or a generic statement that a document is non-disclosable, exempt, confidential, proprietary, or protected. Do not identify an entire page as exempt unless each sentence is within the exemption scope; instead, identify paragraphs or sentences that meet the specific exemption criteria you cite on the Form. Only the specific records or portions of records properly listed on the Form will be protected and withheld for notice. All other records will be considered fully disclosable upon request.If the City receives a public disclosure request for any records you have properly and specifically listed on the Form, the City will notify you in writing of the request and will postpone disclosure. While it is not a legal obligation, the City, as a courtesy, will allow you up to ten business days to file a court injunction to prevent the City from releasing the records (reference RCW 42.56.540). If you fail to obtain a Court order within the ten days, the City may release the documents.The City will not assert an exemption from disclosure on your behalf. If you believe a record(s) is exempt from disclosure you are obligated to clearly identify it as such on the Form and submit it with your solicitation. Should a public record request be submitted to Purchasing and Contracting for that record(s), you can then seek an injunction under RCW 42.56 to prevent release. By submitting a bid document, the bidder acknowledges this obligation; the proposer also acknowledges that the City will have no obligation or liability to the proposer if the records are disclosed.