Gunfire_Detection_System_(Addendum_#2_Revision).pdf

For more information, please visit our online supplier portal, located at https://procurement.opengov.com/portal/cityoftampa

City of Tampa

REQUEST FOR PROPOSALS (RFP) FOR

Gunfire Detection System

25-P-00097

Police

Celeste Gibbons-People, Certified Senior Procurement Analyst

2555 East Hanna Ave

Tampa, FL 33610

Phone: (813) 274-8834

Table Of Contents

1. NOTICE

2. SCOPE OF SERVICES

3. GENERAL CONDITIONS

4. INSURANCE REQUIREMENTS

5. CONTENT OF PROPOSALS

6. EVALUATION

7. PROPOSER’S QUESTIONNAIRE, FORMS, AND ACKNOWLEDGEMENTS

8. ATTACHMENTS & EXHIBITS

Attachments:

A - Form MBD-30 Payments

B - Form MBD-50 GFECP Guidelines

C - Form MBD-70 Procurement Guidelines

D - Form MBD-40 Letter of Intent

E - EBO-Form-71-for-RFQ-Evaluation-Points-V2

F - ADA Requirements

G - CITY OF TAMPA CLOUD HOSTING POLICY

1. NOTICE

1.1. REQUEST FOR PROPOSALS

Sealed proposals for Gunfire Detection System, RFP # 25-P-00097 will be received by the Director of Purchasing, City of Tampa, until Thursday, March 13, 2025; then to be opened.

In accordance with the Americans with Disabilities Act (“ADA”) and Section 286.26, Florida Statutes, persons with disabilities needing a reasonable accommodation to participate in these public hearings or meetings should contact the City of Tampa’s ADA Coordinator at least 48 hours prior to the proceeding. The ADA Coordinator may be contacted by phone at 813-274-3964, email at

TampaADA@tampagov.net, or by submitting an ADA - Accommodations Request online form available at https://tampagov.net/ADARequest. Please note that the City of Tampa may not be able to accommodate any request received less than 48 hours before the scheduled hearing or meeting.

Attached are important instructions and specifications regarding responses to this Request for Proposals. Failure to follow these instructions may result in Proposer’s disqualification.

Questions regarding Vendor Registration, accessing RFP documents or submission assistance within the OpenGov eProcurement Portal shall be directed to procurement-support@opengov.com. Reference RFP # and name in email subject line. Questions pertaining to the

RFP document/specifications will be accepted up to ten days prior to the scheduled opening date and time and shall be submitted within the OpenGov Portal. Per the City of Tampa’s Communication Policy during any solicitation period including any protest and/or appeal, there should be no contact with City officials or employees, other than Celeste Gibbons-People (celeste.gibbons-peoples@tampagov.net) permitted from any Proposer. Such communication shall result in an automatic disqualification for selection in the pending solicitation and any subsequent City solicitations for a period of six (6) months, no matter the outcome of the solicitation or any protest and/or appeal.

Proposals shall be accepted no later than the time and date specified above. The RFP Opening shall be thereafter and published on the

OpenGov portal. All proposals received after the due date and time shall be rejected. Offers by mail, hand delivery or express mail, telephone, email or transmitted by facsimile (FAX) machine are not acceptable. All submittals are uploaded electronically into the OpenGov eProcurement Portal. No file shall have a special character. No proposal may be withdrawn or modified after the time fixed for the opening of proposals.

Electronic submittals shall be performed in the OpenGov Portal via link https://procurement.opengov.com/portal/cityoftampa. To ensure that an electronic submittal is received by the opening date and time, it is recommended that the Proposer submit their documents with adequate time allowed prior to the deadline. Proposer shall receive an email confirmation of their proposal submittal after clicking on the "Submit" button in the portal. The Proposer shall be responsible for confirming that their submittal is received by the deadline. Any submittal received after the closing date and time will not be considered.

1.2. PRE-PROPOSAL CONFERENCE

A PRE-PROPOSAL CONFERENCE will be held at 1:00 pm,Tuesday, February 25, 2025, at 2555 East Hanna Avenue, Purchasing Department 2nd Floor, Tampa, Florida 33610 to discuss the above referenced subject.

BRING A COPY OF THIS RFP TO THE MEETING.

City of Tampa buildings are controlled access buildings, and all visitors are required to obtain a Visitor's Pass prior to entering.

1.3. INSTRUCTIONS

City of Tampa solicitations are issued electronically via the OpenGov eProcurement Portal. Obtaining solicitations through the portal will ensure that proposers will have the following capabilities: receipt of solicitation documents electronically, track the status of solicitation award activity, receive addenda, receive the results of solicitation awards and view plans and blueprints online electronically. Proposers who obtain specifications and plans from sources other than OpenGov are cautioned that the solicitation packages may be incomplete.

The City will not accept incomplete proposals. Contact OpenGov at procurement-support@opengov.com for more information.

The City is not responsible for errors and omissions occurring in the transmission or downloading of any solicitation documents, plans, or specifications from the OpenGov eProcurement Portal. OpenGov has no affiliation with the City of Tampa other than as a service that facilitates communication and solicitation submittals between the City and its proposers. OpenGov is an independent entity and is not an agent or representative of the City. Communications to OpenGov does not constitute communications to the City. Contact OpenGov at procurement-support@opengov.com for more information.

mailto:TampaADA@tampagov.net https://tampagov.net/ADARequest mailto:procurement-support@opengov.com https://procurement.opengov.com/portal/cityoftampa https://procurement.opengov.com/portal/cityoftampa https://procurement.opengov.com/portal/cityoftampa mailto:procurement-support@opengov.com

Proposers discovering any ambiguity, conflict, discrepancy, omission, or other error in this RFP, shall immediately notify the City of such error in writing and request modification or clarification of the RFP within the OpenGov eProcurement Portal. Modifications will be made by issuing an addendum and will be given by written notice to all prospective Proposers who received an original RFP from OpenGov

(those who are on the Plan Holders List). Addenda will be posted and disseminated by OpenGov at least five days prior to this RFP opening date. The Proposer is responsible for clarifying any ambiguity, conflict, discrepancy, omission, or other error in the RFP prior to submitting the offer or it shall be deemed waived.

Tabulations (results) will be posted in the OpenGov eProcurement Portal and made available to proposers after the scheduled public opening of the sealed proposals.

The Proposer shall comply with the applicable requirements of Federal and state laws, all Codes and Ordinances of the City of Tampa as amended from time to time and any applicable professional regulations.

The Proposer is expected to carefully examine the entire solicitation package, including but not limited to all the provisions, terms, and conditions. Failure to do so will be at the Proposer’s risk.

2. SCOPE OF SERVICES

2.1. INTRODUCTION

The City of Tampa is seeking proposals for a Gunfire Location, Alert, and Analysis Service, leveraging a Wide-Area Acoustic Monitoring

System, that detects gunfire and conveys incident alerts to our desired endpoints (e.g., command staff desks and field-based response personnel).

The City of Tampa prefers not to acquire any system hardware, but instead is seeking a subscription-based service. The equipment used for this Service must be installed, operated, managed, and maintained by a qualified, capable, and reputable vendor.

Timeline:

Release Project Date: February 5, 2025

Pre-Proposal Conference (Non-Mandatory): February 25, 2025, 1:00pm

2555 East Hanna Avenue, Purchasing Department

2nd Floor, Tampa, Florida 33610

Question Submission Deadline: March 5, 2025, 5:00pm

Response Submission Deadline: March 13, 2025, 3:00pm

2.2. BACKGROUND

NO VALUE

2.3. SCOPE OF WORK

The City of Tampa (the City) requires a detection system that detects gunfire, locates its origin, and conveys that information, in an actionable form, to multiple designated end-points. The City does not wish to design or implement any aspect of the coverage provided, and explicitly does not wish to be responsible for recommending the placement or re-placement of sensors or any other equipment.

All field-deployed acoustic sensors should be inconspicuous to minimize vandalism and intentional damage. Also, the deployed apparatus (sensor plus mounting hardware) shall be small in size (sensor itself must be smaller than 1 cubic foot), and use non-penetrating mounting methods where possible. All sensors shall be owned, installed and maintained by the Successful Proposer providing this detection system.

Please note, for the required narrative responses, the Proposer shall respond point by point to the RFP requirements using the following response terminology:

Response Terminology Definition Understood Proposer has read and understands the requirement.

Complies Proposer’s response complies with the requirement.

Partially Complies Proposer’s response partially complies with the requirement; specific exceptions or deviations are described in detail.

Exception Proposer’s response does not comply with the requirement.

Alternative Method Proposer’s response provides an alternative methodology, described in detail, which meets the intent of the requirement.

This detection system must be a proven tool that aids law enforcement and first responders in its awareness of and response to incidents of gunfire enabling the suppression of gunfire-related violent crime, where such proof includes a proven history of:

• Detecting and providing a geo-location of gunfire events

• Operating in a complex and loud urban environment with dense buildings, foliage, and topography obscures line-of-sight from a shooting location to acoustic sensors

• Delivering a guaranteed detection and location performance in aggregate throughout an entire coverage area

• History of contributing to reductions in gunfire-related violent crime

• Successfully contributing to convictions (when incident alert data is used in trials and plea bargains as forensic evidence)

• Enabling increased and safer responsiveness to incidents of gunfire

2.3 ACOUSTIC SURVEILLANCE/ACOUSTIC SENSING

ACOUSTIC RANGE; NON LINE-OF-SIGHT OPERATION

RFP Requirement:

2.3.2 The City of Tampa expects a form of wide-area acoustic monitoring to meet the requirements set forth herein.

2.3.3 The City of Tampa expressly needs to detect incidents of gunfire that occur outdoors, often in inconspicuous locations. The technology underlying the detection system desired by The City must be able to detect and locate outdoor gunfire throughout entire areas up to multiple square miles. A requirement for proximity to a surveillance sensor (audio, video, or combined) is expressly not desired. Rather what is required is omnipresent wide-area acoustic sensing tuned to detect and locate gunfire, provided to The City of

Tampa on an annual subscription basis, with no capital equipment to be purchased by The City of Tampa.

2.3.4 Each acoustic sensor must be capable of detecting gunfire at an acceptable non-line-of-sight straight line distance from the origin of gunfire in, urban environments where intervening buildings, topography, and foliage are present. The detection system must operate 24 x 365, necessitating that it must detect during periods of typical urban ambient noise. Preference shall be given to acoustic sensors with proven histories of long-range in urban environments. The acoustic sensors must also be capable of conveying the actual audio received by the sensor causing it to trigger. All acoustic sensors must also have retrievable time-stamped audio, time-stamped with UTC time to be available for follow-up investigative and forensic analysis. All audio snippets must also have a mechanism that validates the integrity of the audio snippet for chain of custody matters (i.e., the audio is authentic and unaltered since it was originally stored by the detection system).

2.3.5. RESILIENT OVERLAPPING ACOUSTIC COVERAGE

The City requires a detection system which can perform at the guaranteed detection rate throughout the coverage area. Because numerous factors can often cancel acoustic energy, the Successful Proposer’s detection system shall be designed such that every outdoor location within the coverage area is covered by an appropriate number of acoustic sensors to provide the guaranteed detection rate.

2.3.6. PLACEMENT OF SENSORS

Due to the complexity and ongoing reliability of dedicated data networks, the City prefers a Successful Proposer and a detection system that uses wireless cellular networks for data communications from field-based assets (i.e., the acoustic sensors). The detection system’s field-based assets (i.e., acoustic sensors) shall be capable of being placed for optimal acoustic detection and for optimal transmission of data via cellular networks. The City prefers the placement of sensors as high as possible above street-level. Successful

Proposer is responsible for all costs associated with the placement of sensors; including obtaining authorization to place sensors on property.

2.3.7 ENVIRONMENTAL ENDURANCE

The components of the Successful Proposer's detection system deployed outdoors must operate 24 x 365 and therefore must withstand typical outdoor conditions that include: sunlight, rain, hail, wind, and both daily and seasonal temperature extremes. Successful

Proposer should have components deployed outdoors and in similar conditions for at least 1 full year in each of the following: coastal areas subject to fog; areas where relative humidity exceeds 80%; where temperatures are between 5 degrees C and +35 degrees C.

2.3.8 DETECTION

Detectable gunfire is defined as outdoor gunfire from unsuppressed weapons fired without obstruction of the muzzle. Examples of undetectable gunfire incidents include: use of a "silencer", extreme point-blank range, firing inside of a vehicle, firing from a partially enclosed and/or roofed area (e.g., a porch or patio).

2.3.9 DETECTION VERSUS LOCATION (GEO-LOCATION)

2.3.9.1 The City desires a detection system that distinguishes between detection geolocation of incidents. Products that provide only detection of an incident without providing a precise geographic location within a defined circular error of probability shall be deemed insufficient and will not be considered. Products that detect incidents via proximity or simply provide a range and bearing relative to the sensor shall be deemed insufficient and will not be considered.

2.3.9.2 The Successful Proposer’s detection system shall deploy a sensor network over the agreed upon coverage area with a design to detect at least 90% of the unsuppressed outdoor gunfire, with a location accuracy to the shooter’s location within 90 feet.

2.3.10 GUNFIRE CLASSIFICATION ACCURACY

The Successful Proposer's detection system shall employ technology that ensures that other sounds, especially those that are similar in nature to gunfire, are minimized to avoid spurious false triggering. The Successful Proposer's detection system shall have the unique ability to detect gunfire that occurs within a distributed network of sensors.

The City seeks to minimize the disruptions that result from other noises that may be considered false alerts and therefore shall give preference to a detection system that includes all of the following:

• Reviewed Alerts shall place a “dot on the map” and report the closest address denoting the location of the incident.

• Reviewed Alert will include Qualitative Severity information indicating: number of shots, fully automatic weapons, possible multiple shooters, and other informative comments as necessary.

• Data shall be robust enough to support a forensic level analysis to include (but not limited to): sequence of fire, caliber of each round of fire, location of each round of fire, and the exact time (in fractions of a second) of each round.

• A robust classification process that consistently traps and dismisses obvious false alerts.

• Classification and filtering algorithms adaptable to each unique deployment environment.

• Filtering alerts, temporarily or permanently within specific geographic areas to squelch temporary or ongoing impulsive noise problems (e.g., gun range, heavy construction activity, etc.).

• Filtering all alerts during periods of common and/or anticipated high activity, such as July 4th and New Year’s Eve.

2.3.11 LOCATION DETERMINATION: LOCATION ACCURACY

The City requires a detection system capable of calculating a precise geographic location of each detected incident using the standard latitude and longitude geographic coordinate system. Latitude and longitude reported must be accurate to within a circle radius of 90 feet, anywhere within the coverage area in 90% of detections. These locations must be presented to the Tampa Police Department’s end-user(s) such that each incident is visibly plotted and displayed as an aerial view on Successful Proposer's supplied visualization software. Multiple-round incidents must be distinguished from single-round incidents, and the detection system must be capable of

“bundling” multiple-round shootings such that only a single alert is presented to users. This alert must specify and convey whether one or more rounds were fired.

2.3.12 FULLY MANAGED SERVER INFRASTRUCTURE: HOSTED SERVER/COMPUTING INFRASTRUCTURE The Successful Proposer’s detection system including all servers and centrally located processing shall be in a reliable and secure

(“cloud”) hosting facility. Implicit in this requirement is all platform and application software, whether Successful Proposer’s or from third parties, shall be installed and running within the hosted infrastructure. This must be in compliance with the City of Tampa’s cloud-hosted server policy.

2.3.13 SERVICE ACCESS VIA SECURE (HTTPS) DATA COMMUNICATIONS CONNECTIONS

The City shall be able to access and use the detection system using industry standard computers (Apple or Windows) and smartphones (iPhone or Android). Preference shall be for browser-based software and purpose-built smartphone applications written and supported by the Successful Proposer. Usage shall consist of administrative access to set preferences, access to receive alerts for dispatch, command staff access for activity awareness, investigations access for investigative follow-up, crime analysis access for analysis and correlation with complementary data. Secure communications (HTTPS) is required to accommodate the abovementioned end-users using and accessing the detection system from any location. The detection system must support role-based logins so that any authorized end-user accessing the detection system is presented with the views, tools, and data relevant to their job functions.

2.3.14 DATA STORAGE AND ACCESS

2.3.14.1 The City requires that the Successful Proposer’s detection system permanently archive all data and information pertaining to incidents, system operating settings, workstation interactions, end-user activity logs, etc. The Tampa Police Department shall have the ability to access incident data records singularly and in aggregate for the entire subscription period.

2.3.14.2 Upon termination or expiration of this Agreement, the Successful Proposer shall provide the City with access to all City Data stored in the Successful Proposer's systems for a period of ninety (90) days. During this period, the City shall have the ability to download all City Data in commonly accessible formats, including but not limited to CSV (Comma-Separated Values). The Successful

Proposer shall maintain the functionality necessary for such data retrieval and ensure the data remains complete, unaltered, and accessible throughout the post-termination period.

2.3.15 DATA INTEGRITY

Incident data including audio snippets shall be secured in a tamper evident data format so that it provides a proven secure chain of custody and that there has been no subsequent modification. Event audio snippets may be introduced as evidence, provided to prosecutors and played for jurors when permissible. For data security reasons, none of the permanent data above may be stored solely on the sensors deployed in the field and instead shall be stored on the cloud server.

2.3.15.1. PERMANENT INFORMATION SHALL MINIMALLY INCLUDE:

• All incident information defined below under dispatcher-role and responder-role software (i.e., incident date/time, geo-location, street address, sensors participating, end-user notes, etc.)

• Audio recordings with GPS derived universal time code (UTC) timestamps from all sensors participating in a location, with anti-tamper awareness, such as an MD5 hash, attached to such recordings at the time of storage such that they can later be proven to be authentic and safeguarded from tampering

• All incident “metadata” (dispatcher/end-user actions, workflow steps, comments, tag numbers and/or keywords, etc.)

• Sensor telemetry and status data

• The number and type of client workstations accessing and the types of users authorized to use the detection system

2.3.15.2. ALERTING, REPORTING, AND FORENSICS: DISPATCHER-ROLE AND RESPONDER-ROLE SOFTWARE Successful Proposer must provide dispatcher-role and responder-role access and/or software that minimally supports the functionality listed below. Preference shall be given to browser-based software and purpose-built smartphone applications written and supported by the Successful Proposer. The software must explicitly support user roles of either dispatchers or field-based response personnel (police officers).

• Visible and audible (annunciation) of the arrival of new alerts

• Display a scalable aerial map image

• Overlay an incident geo-location marker (“dot”) at a specific latitude-longitude coordinate

• Display the address of the parcel containing the latitude-longitude coordinate, or otherwise and if available display a nearest address; The City understands that some parcels, such a public parks and wooded areas may not have a nearest address; however, this highlights the need for the placement of a marker (dot) on an aerial map image

• Date and time of the incident

• Delineate between single-round incidents and multiple-round incidents

• Convey the possibility of multiple shooters involved when multiple-round incidents are detected

• Automatic and manual zooming to view incident geo-location (latitude/longitude) relative to nearby landmarks (e.g. buildings, streets, etc.) to provide responding officers with situational awareness and improve approach and containment

• Display relevant “beat,” “region” or other geographic groupings, based on The City’s existing geographic areas, with no limit to the number of areas, and a maximum of three (3) hierarchical levels of grouping (i.e., multiple beats in a district)

• Record Computer Aided Dispatch Identification (CAD ID) or other incident-specific details while an alert is displayed

• Incident details should be able to be easily placed into a computer’s clipboard for pasting into a CAD event record’s description/synopsis field

• Responder-role Software should be able to receive and play audio snippets (i.e., only the gunfire sound duration, not a lengthy audio stream somewhere within which gunfire is found).

2.3.16 ADDITIONAL SOFTWARE FEATURES

Successful Proposer must provide the following additional software features:

• Ability to search for and review any past incident by Incident number, CAD ID, incident type, or date before or after, comments, street address, or coverage area (in the case of multiple coverage areas).

• Ability to display a list of incidents which meet one or more criteria chosen from: start date (of a date range), end date (of a date range), type of incident, content of comments, content of address, incident ID (range), content of CAD ID field, and/or coverage area

(in the case of multiple coverage areas).

• Print an incident-specific report containing an aerial map and all incident specific details (including all criteria listed above).

• Print a report listing all incidents which match one or more criteria chosen from: start date (of a date range), end date (of a date range), type of incident, content of comments, content of address, incident ID (range), content of CAD ID field, and/or coverage area

(in the case of multiple coverage areas).

• Export a file to the user’s local computer in comma-separated values format (CSV) containing all incidents matching one or more criteria chosen from: start date (of a date range), end date (of a date range), type of incident, content of comments, content of address, incident ID (range), content of CAD ID field, and/or coverage area (in the case of multiple coverage areas).

• Detection system will store (pursuant to the desire of the Tampa Police Department and Florida Public Records laws) every incident ever generated and provide software for users and staff to view historical timelines of each incident showing the meaningful state changes of the incident, add comments, attach metadata, and print out incident reports showing all of this information.

• The view of an incident should show a timeline for every event, comment, and state change associated with that incident. By acting as a repository for everything related to a gunfire incident, the software should provide access to deep knowledge about an incident.

2.3.17 INCIDENT ALERTING TO FIELD-BASED PERSONNEL

The Successful Proposer’s detection system shall support conveyance of alerts (in accordance with the immediately preceding criteria) to any compatible computer anywhere so long as that computer can establish a secure IP data connection to the hosted detection system software. Alerts to field-based personnel must operate seamlessly and cooperatively with alerts to office-based personnel.

2.3.18 INCIDENT AUDIO SNIPPETS

Audio captured and conveyed to the Tampa Police Department’s software must be in the form of snippets. Entire streams are not acceptable. Having snippets enables personnel to instantly play and audition the incident without having to seek or search. Snippets from different acoustic sensors deployed at different locations provide different perspectives that can be invaluable for post event forensic analysis, therefore the City shall give preference to Proposer's whose detection system can offer multiple audio snippets from different locations and perspectives.

2.3.19 INCIDENT TYPE CLASSIFICATION

The Successful Proposer’s detection system must minimize occurrences of false alarms. Acceptable techniques include methods previously mentioned herein. However, it is a requirement that a report can be generated on all other incidents (such as fireworks) to include time of activation, locations and the audio snippet associated with the event(s).

2.3.20 DATA ACCESS & REPORTS

2.3.20.1 The City requires that the Successful Proposer provide a data store to house all incident data information to facilitate the generation of summary and detail reports and activity reports. The data store shall provide the ability to download data in CSV (comma separated value) via secure access (e.g., HTTPS) for use with reporting and analysis tools.

2.3.20.2 The Successful Proposer's detection system should minimally include reports for specific incidents that include a map image denoting the exact parcel and latitude-longitude coordinate, as well as activity summary reports suitable for intelligence-led policing needs. Reports must be visible on the computer screen and must also be able to be printed.

2.3.21 FORENSIC ANALYSIS & WITNESS TESTIMONY

2.3.21.1 The Successful Proposer's detection systems data must be admissible as trial evidence. Therefore, strong preference shall be given to proposers providing examples of objective and accurate forensics data used in court cases. Specifically, the forensic data must provide details essential for assisting investigators to reconstruct an exact timeline of a shooting as well as enable them to corroborate or refute testimony from perpetrators, victims, and witnesses.

2.3.21.2 Tampa Police Department investigators must be able to access or otherwise create reports and audio snippets from the detection system for inclusion in their investigative reports in support of court trials. Investigators shall be trained to access the detection system to perform the following functions:

• Generate single and aggregated Incident Reports (geo-location, street address, location on map)

• Review and playback audio snippets

• Evaluate the sequence of each round discharged

• Recall and review Incidents

• Export Incident data to third party reporting and analytics application software

2.3.21.3 In situations where physical evidence is insufficient to positively implicate more than one shooter, the detection system shall be capable of providing evidentiary information that may assist in the potential identification of the number of shooters along with the distance between the origins of shots (i.e., the location of each shooter), and a sequenced timeline of each shot from each specific shooting location. This information along with all captured incident details must be available to the City via any combination of automated and manually generated reports that include critical detailed timelines and data that reveal the sequence of a shooting incident, identify individual shots fired by multiple shooters, and possibly provide the precise location of involved persons during the incident.

2.3.22 TRAINING AND CUSTOMER SUPPORT: PROGRAM DEVELOPMENT, TRAINING & CUSTOMER SUCCESS

2.3.22.1. A proven customer success program is expected to identify the challenges, successes and solutions of all customers in an effort to identify best practices that can be shared across all agencies. The Successful Proposer must have developed a comprehensive list of “best practices” compiled from their installed base’s experience with utilizing the detection system within a Public Safety

Answering Point (PSAP) (dispatch center), by investigators, patrol and field-based personnel, prosecutors, and crime analysts.

2.3.22.2 The Proposer shall provide an outline or overview of their training program(s) and also identify the number of years their program has been in existence, the frequency and methods of training, and the credentials of the trainers and customer success directors.

2.4. PROPOSER SUBMITTALS AND QUALIFICATIONS

The following must be submitted in the proposal:

A. Contract Termination for Default. Has the Proposer’s company had a contract terminated for default in the last five years? Termination for default is defined as notice to stop performance which was delivered to the Proposer due to the Proposer's non-performance or poor performance and the issue of performance was either not litigated due to inaction on the part of the

Proposer; or litigated and determined that the Proposer was in default.

If the company has had a contract terminated for default in this period, submit full details including the other party's name, address, and the phone number. Present the company’s position on the matter. City Representative will evaluate the facts and may, at its sole discretion, reject the RFP on the grounds of its past experience.

B. Contract Litigation/Legal Proceedings. The Proposer shall identify any pending lawsuits, past litigation relevant to subject matter of this RFP, providing a statement of any litigation or pending lawsuits that have been filed against the Company in the last five years.

If an action has been filed, state and describe the litigation or lawsuit filed, and identify the court or agency before which the action was instituted, the applicable case or file number, and the status or disposition for such reported action. If no litigation or lawsuit has been filed against the company, provide a statement to that effect.

C. PROPOSER QUALIFICATIONS

2.4.1 REFERENCES

An important consideration of The City will be the depth and breadth of customer references. Proposer's will be required to provide references to prove any claims made in response to our request. References may be requested to substantiate any and all of the following aspects of the Proposer and its detection system: deployment, maintenance, forensic and court testimony, training, and crime reduction metrics.

2.4.2 SIZE OF EXISTING DEPLOYMENTS

Proposer must provide references to at least three (3) deployments, each of which provides a performance guarantee level within a coverage area of at least four (4) contiguous square miles.

2.4.3 MONITORING AND MAINTENANCE

The Successful Proposer’s ability to monitor and maintain this detection system is a critical component of our evaluation. The

Successful Proposer should have continuous independent monitoring of each sensor that will alert them to potential malfunctions that may impact the detection rate and accuracy of their detection system. Successful Proposer is responsible for any and all costs associated with repair and replacement of sensors or any other infrastructure provided for the detection system.

2.4.4 FORENSICS AND COURT TESTIMONY

Proposer must provide references to instances in which its data have been admitted as scientific evidence in a criminal court. Such evidence must include at least three (3) separate trials, with preference given to criminal cases in the State of Florida.

2.4.5 PRIVACY POLICY

2.4.5.1 All data collected with the Successful Proposer's system shall be considered the sole property of the City. It may not be released to any source outside of the City without prior written authorization.

2.4.5.2 The Proposer's shall have experience in providing detailed forensic reports following chain of custody rules and then providing expert witness testimony as required in support of prosecutions. The Successful Proposer must provide expert witness testimony from industry specific experts having reviewed as many incidents and authored forensic reports based on data from Successful Proposer’s detection system. The Successful Proposer shall include one sample or redacted detailed forensic report. The vendor shall have a history of testimony in forensic documentation and expert witness inclusive of evidentiary forensic information having been accepted as scientific evidence and used in each of the following scenarios; pre-trial processes, trials and courtroom sessions.

2.5. MANAGEMENT

If, during the course of the project, the Successful Proposer makes personnel changes, the City has the right of review, acceptance, and/or reject proposed substitute(s). The City will make available the City’s management team for interview and consultation during plan(s) development and for review of the draft and final plans.

2.6. IMPLEMENTATION, TIMELINE, MILESTONES, AND/OR EXECUTION STRATEGY

*Explain how the work outlined in the scope of work will be carried out by the Successful

Proposer, including the timeline, resources, and steps required to achieve the desired outcomes. This section needs to explain the process or how the scope of work is to be accomplished.*

2.7. COORDINATION WITH THE CITY

The Successful Proposer shall identify the Project Manager to work in close coordination with the City. The City’s Project Manager shall be the City’s point of contact. The City shall approve any changes to the Project Manager or personnel assigned to the project.

During the term of the contract, the Project Manager shall meet on-site with the City’s Project Manager and/or other designated City officials as necessary, for the purpose of discussing and coordinating work to be performed, or performance of work.

3. GENERAL CONDITIONS

3.1. PROPOSAL DUE DATE

Sealed proposals will be received no later than the date and time indicated on page one of this document. Proposals will not be accepted after this time. All proposals shall be submitted through the OpenGov eProcurement Portal (electronically). File name should not have special characters. Proposer must wait for confirmation of successful upload.

City of Tampa Requests for Proposals are issued electronically via the OpenGov Portal. Obtaining proposals through OpenGov will ensure that proposer will have the following capabilities: receipt of proposal documents electronically, track the status of award activity, receive addenda, receive the results of awards and view plans and blueprints online electronically. Proposers who obtain specifications and plans from sources other than OpenGov are cautioned that the proposal packages may be incomplete. The City will not accept incomplete proposals. Contact OpenGov at procurement-support@opengov.com for more information.

The City is not responsible for errors and omissions occurring in the transmission or downloading of any solicitation documents, plans, or specifications from the OpenGov eProcurement Portal. OpenGov has no affiliation with the City of Tampa other than as a service that facilitates communication and proposal submittals between the City and its vendors. OpenGov is an independent entity and is not an agent or representative of the City. Communications to OpenGov does not constitute communications to the City. Contact OpenGov at procurement-support@opengov.com for more information.

3.2. ADDENDUM AND AMENDMENT TO RFP

If it becomes necessary to revise or amend any part of this RFP, OpenGov will provide notification of the Addendum to all prospective

Proposers who received an original RFP notification making them a plan-holder. Addenda will be posted and disseminated by OpenGov at least five days prior to the RFP opening date.

It will be the responsibility of the Proposer to review OpenGov prior to submitting a proposal to ascertain if any addenda has been issued, to obtain all such addenda, and to return the executed addenda with the proposal.

3.3. ERRORS AND OMMISSIONS

Proposers discovering any ambiguity, conflict, discrepancy, omission, or other errors in this RFP, shall immediately notify the City of such error via email within the OpenGov eProcurement Portal and request modification or clarification of the RFP. Modifications will be made by issuing an addendum and will be given by written notice to all prospective Proposers who queried the solicitation in the

OpenGov Portal. Addenda will be posted and disseminated by OpenGov at least five days prior to the RFP opening date. The Proposer is responsible for clarifying any ambiguity, conflict, discrepancy, omission, or other error in this RFP prior to submitting the proposal or it shall be deemed waived.

3.4. FLORIDA PUBLIC RECORDS LAW

In accordance with Chapter 119 of the Florida Statutes, and, except as may be provided by Chapter 119 of the Florida Statutes and other applicable State and Federal Laws, all Proposers should be aware that the Proposal and the responses thereto are in the public domain and are available for public inspection and copying. Proposer is required to acknowledge whether or not they are asserting that certain information in its proposal is confidential and/or proprietary and/or exempt from public disclosure. If the Proposer is asserting that certain information in its Proposal is confidential and/or proprietary and/or exempt from public disclosure, then the

Proposer is required to do the following:

A. Identify, with specificity, the information which the Proposer asserts is confidential and/or proprietary and/or exempt from public disclosure, B. Place such information in a separate file labeled “REDACTED, EXEMPT FROM PUBLIC DISCLOSURE” this uploaded document must be separate from the Proposer's other Proposal documents, C. Specifically cite the applicable Florida Statute(s) that exempts such information from public disclosure - such citation must be placed within the redacted file. The “REDACTED” file that contains the Proposer's confidential/proprietary/exempt information must be submitted with the Proposer's other Proposal documents. Proposer is advised that failure to follow the aforementioned instructions may result in Proposer's alleged confidential/proprietary/exempt information being disclosed to the public. This will be the Proposer’s “REDACTED” copy. All submittals received in response to this Proposal will become the property of the City of Tampa and will not be returned. In the event of an award, all documentation produced as part of the contract will become the exclusive property of the City.*

Be aware that the designation of an item as exempt from public disclosure by a Proposer may be challenged in court by any person or entity. By designation of material in your Proposal submittal as exempt from public disclosure, Proposer agrees to defend the City of

Tampa (and its employees, agents and elected and appointed officials) against all claims and actions (whether or not a lawsuit is commenced) related to Proposer’s designation of material as exempt from public disclosure and to hold harmless the City of Tampa

(and its employees, agents and elected and appointed officials) for any award to a plaintiff for damages, costs and attorneys’ fees, and for costs and attorneys’ fees incurred by the City by reason of any claim or action related to your designation of material as exempt from public disclosure.

*Note: The City will not accept Proposal submittals when the entire submittal is labeled as exempt from public disclosure and the proposal will be deemed non-responsive. Proposer’s References and Cost or Price information will be deemed a public record, and if a claim of confidentiality/proprietary information is made, the City may deem the

Proposal submittal as “non-responsive”.

A. In accordance with Section 119.071(1)(b)2, Florida Statutes, sealed bids, proposals, or replies received by the City of Tampa pursuant to a competitive solicitation are exempt from section 119.07(1), Florida Statutes and section 24(a), Art. I of the State

Constitution until such time as the City of Tampa provides notice of an intended decision or until 30 days after opening the bids, proposals, or final replies, whichever is earlier.

B. In accordance with Section 119.071(1)(b)3, Florida Statutes, if the City of Tampa rejects all bids, proposals, or replies submitted in response to a competitive solicitation and the City of Tampa concurrently provides notice of its intent to reissue the competitive solicitation, the rejected bids, proposals, or replies remain exempt from section 119.07(1), Florida Statutes and section 24(a), Art. I of the State Constitution until such time as the City of Tampa provides notice of an intended decision concerning the reissued competitive solicitation or until the City of Tampa withdraws the reissued competitive solicitation. A bid, proposal, or reply is not exempt for longer than 12 months after the initial City of Tampa notice rejecting all bids, proposals, or replies.

C. The City of Tampa is a public agency subject to Chapter 119, Florida Statutes. In accordance with Florida Statutes, 119.0701, Successful Proposer agrees to comply with Florida’s Public Records Law, including the following:

1. Successful Proposer shall keep and maintain public records required by the City to perform the services;

2. Upon request from the City, Successful Proposer shall provide the City with copies of the requested records, having redacted records in total or in part that are exempt from disclosure by law or allow the records to be inspected or copied within a reasonable time (with provision of a copy of such records to the City) on the same terms and conditions that the

City would provide the records and at a cost that does not exceed that provided in Chapter 119, Florida Statutes, or as otherwise provided by law;

3. Ensure that public records, in part or in total that are exempt or that are confidential and exempt from public record requirements are not disclosed except as authorized by law for the duration of the contract term and following completion

(or early termination) of the contract if the Contractor does not transfer the records to the City;

4. Upon completion (or earlier termination) of the award, Successful Proposer shall within 30 days after such event either transfer to the City, at no cost, all public records in possession of the Successful Proposer or keep and maintain the public records in compliance with Chapter 119, Florida Statutes. If Successful Proposer transfers all public records to the City upon completion (or earlier termination) of the award, Successful Proposer shall destroy any duplicate records that are exempt or confidential and exempt from public records disclosure requirements. If Successful Proposer keeps and maintains public records upon completion (or earlier termination) of the award, Successful Proposer shall meet all applicable requirements for retaining public records. All records stored electronically must be provided to the City in a format that is compatible with the information technology systems of the agency.

5. The failure of Successful Proposer to comply with Chapter 119, Florida Statutes, and/or the provisions set forth above shall be grounds for immediate unilateral termination of the contract by the City; the City shall also have the option to withhold compensation due Successful Proposer until records are received as provided herein.

6. IF THE SUCCESSFUL PROPOSER HAS QUESTIONS REGARDING THE

APPLICATION OF CHAPTER 119, FLORIDA STATUTES TO THE

SUCCESSFUL PROPOSER’S DUTY TO PROVIDE PUBLIC RECORDS

RELATING TO THIS AWARD, CONTACT THE CUSTODIAN OF PUBLIC

RECORDS AT 813/274-8351, AND MAILING ADDRESS OF PURCHASING

DEPARTMENT, HANNA CITY CENTER BUILDING, 2ND FLOOR, 2555 E.

HANNA AVE, TAMPA, FL 33610.

Note: Acknowledgement of the Florida Public Records Law must be submitted with the proposal, under PROPOSER’S

QUESTIONNAIRE, FORMS, AND ACKNOWLEDGEMENTSCONDITIONS.

3.5. CITY OF TAMPA ETHICS CODE

The Proposer shall comply with all applicable governmental and city rules and regulations including the City's Ethics

Code which is available on the City's Website. (City of Tampa Code, Chapter 2, Article VIII. - Section 2-522)

Moreover, each Proposer responding to this Request for Proposal acknowledges and understands that the City's Charter and Ethics

Code prohibit any City employee from receiving any substantial benefit or profit out of any contract or obligation entered into with the

City, or from having any direct or indirect financial interest in effecting any such contract or obligation. The Successful Proposer shall ensure that no City employee receives any such benefit or interest as a result of the award of this Request for Proposal. (City of Tampa

Code, Chapter 2, Article VIII. - Section 2-514(d))

Please note that the City's Ethics Code may be accessed on the Internet by utilizing the website link http://www.tampagov.net/human-resources/info/lobbyist-information or can be found in the City of Tampa’s municipal codes published online by the Municipal Code Corporation at the website link https://www.municode.com/library/fl/tampa/codes/code_of_ordinances. Printed copies of the Ethics Code can also be obtained from the City Clerk's Office for a fee of $0.15 cents a page.

3.6. WARRANTIES AND GUARANTEE

The City of Tampa will not accept any disclaimer of the warranties of merchantability and fitness for a particular purpose for the products offered. Proposals will clearly state any additional warranties and guarantees against defective materials and workmanship. A copy of the complete manufacturer's warranty statement is to be submitted with the proposal.

The material(s) supplied shall be guaranteed to be free from defect of composition, conception, and workmanship for a minimum period one-year from the date of installation and final acceptance by the City. Any parts or portions found not in accordance with this

RFP will be rejected by the City and returned to the Successful Proposer at the Successful Proposer’s expense for immediate replacement.

3.7. COPYRIGHTS AND PATENT RIGHTS

Proposer warrants that there has been no violation of copyrights, patent or other intellectual or proprietary rights in manufacturing, producing and/or selling the item(s) ordered or shipped as a result of this Proposal, and Successful Proposer agrees to indemnify, defend and hold the City harmless from any and all liability, loss or expense by any such violation including litigation costs and attorneys' fees through the appellate process, and damages which may be incurred by reason of any infringement at any time during the prosecution or after the completion of work.

3.8. PROCUREMENT PROTEST PROCEDURES

A protest must be filed with the Director of the soliciting Department within five (5) business days of posting the City’s intent to award and may be filed by an actual Proposer, who is allegedly aggrieved in connection with the issuance of a proposal solicitation or pending award of any contract in any competitive process utilized by the City of Tampa for procurements of supplies, materials or services and construction of public improvements and has standing to protest under Florida Law. Any protest must be filed in accordance with the

City of Tampa Code, Chapter 2, Article V, Division 3, Purchases and Contracts, Section 2-282, Procurement Protest Procedures. Protests not complying with the provisions of this Section shall not be reviewed.

All dates and times specified in the Protest Procedures in Section 2-282 are calculated as city business days. A City business day shall mean 8:00 am to 5:00 pm Monday through Friday, with the exception of city holidays. In all instances any document required to be transmitted by a certain date must be received in the required office by 4:30 pm. An envelope which is postmarked by the required date is not sufficient. Transmittal by fax, email or other electronic means may be accepted.