8-Attachment F - Gunshot Detection System Functional Requirements.xlsx
XLSX spreadsheet 17 KB Posted
- Attached to
- City of Detroit Gunshot Detection System
- Solicitation number
- 541086
- Issued by
- Wayne County, Detroit City, Michigan
About this file
This is a Functional Requirements document for a Gunshot Detection System being procured by the City of Detroit Office of Contracting and Procurement on behalf of the Detroit Police Department. The document establishes 28 specific functional requirements organized into ten categories: Detection System, Performance, Event Classification, Alerting, Visualization, Integration, Digital Evidence, Analytics, Security, Audit, Availability, Scalability, Administration, Maintenance, Training, and Future Capability. Core detection requirements mandate real-time gunfire detection with the ability to differentiate gunshots from fireworks, vehicle backfire, and construction noise, along with detection confidence scoring and triangulated geolocation of events. The system must achieve detection latency of 60 seconds or less with location accuracy within 25 meters as a preferred specification.
The proposed system must integrate with the RTCC monitoring stations and CAD/dispatch systems, display events on GIS-enabled maps with historical event replay and heat map capabilities, and automatically cue nearby cameras through RTCC integration. Additional integration requirements include compatibility with Genetec Security Center or equivalent video management systems and mobile access for field officers. The system must comply with CJIS Security Policy, implement role-based access control, encrypt data in transit and at rest, and maintain audit logging for all access and changes. Performance and operational requirements include 99.9% system uptime, support for phased deployment and expansion, centralized administration, remote sensor health monitoring, and operator and administrator training. An optional future capability includes support for integration with drone response workflows.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 7-Attachment A - Respondent Questionnaire RFP 541086.docx | DOCX document | |
| 1-Equalization Credit Statement.pdf | ||
| 9-RFP 541086 Gunshot Detection.pdf | ||
| 6-Attachment B - Respondent Proposal Introduction and Solution Approach (2).docx | DOCX document | |
| 2-Attachment D-1 Required Forms Affidavits.pdf | ||
| 5-Attachment C - Price Sheet.xlsx | XLSX spreadsheet | |
| 3-Attachment D-2 - Conditions of Award.pdf | ||
| 4-1.23.26 NO AI UPDATED TECH CONTRACT TEMPLATE (1).docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Gunshot Detection Requirements
| Requirement ID | Category | Requirement Description | Vendor Response (Yes/No) | Notes/Comments |
| GDS-001 | Detection | System shall detect gunfire events in real time. | ||
| GDS-002 | Detection | System shall differentiate gunshots from fireworks, vehicle backfire, and construction noise. | ||
| GDS-003 | Detection | Provide detection confidence scoring. | ||
| GDS-004 | Detection | Provide triangulated geolocation of events. | ||
| GDS-005 | Performance | Detection latency ≤ 60 seconds. | ||
| GDS-006 | Performance | Location accuracy within 25 meters preferred. | ||
| GDS-007 | Event Classification | Identify number of shots fired. | ||
| GDS-008 | Event Classification | Assign event severity levels. | ||
| GDS-009 | Alerting | Send alerts to RTCC monitoring stations. | ||
| GDS-010 | Alerting | Integrate with CAD/dispatch systems. | ||
| GDS-011 | Visualization | Display events on GIS-enabled map. | ||
| GDS-012 | Visualization | Provide historical event replay and heat maps. | ||
| GDS-013 | Integration | Automatically cue nearby cameras (RTCC integration). | ||
| GDS-014 | Integration | Integrate with Genetec Security Center or equivalent VMS. | ||
| GDS-015 | Integration | Support mobile access for field officers. | ||
| GDS-016 | Digital Evidence | Store audio and metadata for events. | ||
| GDS-017 | Digital Evidence | Maintain chain-of-custody records. | ||
| GDS-018 | Analytics | Provide shot density analysis and reporting. | ||
| GDS-019 | Security | CJIS Security Policy compliance. | ||
| GDS-020 | Security | Role-based access control (RBAC). | ||
| GDS-021 | Security | Encrypt data in transit and at rest. | ||
| GDS-022 | Audit | Provide audit logging for access and changes. | ||
| GDS-023 | Availability | System uptime ≥ 99.9%. | ||
| GDS-024 | Scalability | Support phased deployment and expansion. | ||
| GDS-025 | Administration | Centralized administration portal. | ||
| GDS-026 | Maintenance | Remote sensor health monitoring. | ||
| GDS-027 | Training | Provide operator and administrator training. | ||
| GDS-028 | Future Capability | Support integration with drone response workflows (optional). |
File details come from the government source that posted it. Updated .