Gunfire Detection System

The City of Tampa is soliciting proposals under RFP 25-P-00097 for a subscription-based gunfire location, alert, and analysis service for the Tampa Police Department, with final proposals due March 13, 2025 at 3:00 p.m. That deadline has passed, so the solicitation is closed as of November 9, 2026. Participation by WMBE and SLBE firms is a scored evaluation factor carrying 20% weighting, not a set-aside. Certification must be completed before the RFP opening date for point eligibility. Bidders using WMBE or SLBE subcontractors must submit Form MBD-40 letters of intent within ten work days of bid opening, and failure to provide them may result in bid disqualification or award delay.

The City prefers not to acquire hardware. The vendor must own, install, operate, and maintain all sensors on a 24/7 basis. The system must detect unsuppressed outdoor gunfire across multiple square miles, geolocate it within 90 feet, and deliver forensic-level data for legal proceedings. Alerts go to command staff and field personnel, and proposers must demonstrate capability in urban environments, supply multiple audio snippets, and support dispatcher and field user roles. Vendors must also meet City policy for cloud and hosted services, including an information security program, encryption of non-public data, criminal background checks on staff, Florida public records compliance, City audits, breach notification, and business continuity and disaster recovery plans. Accessibility conformance must be documented through a VPAT-based Accessibility Conformance Report against WCAG 2.1 Level AA and Section 508.

The contract term is three years with one additional one-year renewal option. Evaluation is points-based across six criteria: firm experience (30%), responsiveness to scope (20%), WMBE/SLBE participation (20%), project team qualifications (15%), cost (10%), and criminal history screening practices (5%). A pre-proposal conference was held February 25, 2025 at 1:00 p.m., and questions were due March 5, 2025, per Addendum #2 Revision, the most recent update in the file.