9-RFP 541086 Gunshot Detection.pdf

City of Detroit Office of Contracting and Procurement (OCP)

Request for Proposal – 541086 Gunshot Detection

Revised 12/2/2025 Page 1 of 21

CITY OF DETROIT

OFFICE OF CONTRACTING AND PROCUREMENT

REQUEST FOR PROPOSALS

RFP NO. 541086

Gunshot Detection Solution

Buyer: Eric Cooper

EVENT / ACTIVITY DUE DATE / TIME

ADVERTISEMENT DATE 2/9/2026

PRE-PROPOSAL

CONFERENCE

Thursday 2/26/2026 11 am EST Microsoft Teams

Microsoft Teams meeting Join: https://teams.microsoft.com/meet/28574883875253?p=2Cr1WRai5vbCCw5FkG Meeting ID: 285 748 838 752 53 Passcode: Qh2N5HY6

Need help? | System reference Dial in by phone +1 469-998-6602,,869539392# United States, Dallas Find a local number Phone conference ID: 869 539 392# For organizers: Meeting options | Reset dial-in PIN

QUESTIONS DUE 3/5/2026 on or before 3pm EST

All questions must be submitted online in the Supplier Portal as indicated in Section

3.3 of this RFP.

PROPOSAL DUE DATE * 3/17/2026 @ 3pm EST In the Supplier Portal as specified in Section 4.5 of this RFP.

* Respondents must register in EUNA Bonfire to download bid documents and submit bids. The City cannot guarantee the accuracy of any bid documents obtained from outside of EUNA, and bids submitted outside of EUNA Bonfire will not be accepted. Detailed resources about registering and bidding, including video tutorials and live, virtual office hours, are available at www.detroitmi.gov/suppliersupport.

Questions about the specifics of this RFP must be asked within the EUNA Bonfire Messages interface for the bid on or before the date and time indicated above. Questions asked via phone, email, and/or other means will not be answered.

https://teams.microsoft.com/meet/28574883875253?p=2Cr1WRai5vbCCw5FkG https://aka.ms/JoinTeamsMeeting?omkt=en-US https://teams.microsoft.com/l/meetup-join/19%3ameeting_YzU2OTRhMDItNGZjOC00NDllLThmOWItODJjN2I0NmRkZDJm%40thread.v2/0?context=%7b%22Tid%22%3a%22e154a760-1d2d-4ef6-8fd3-ebc8b4ef31fd%22%2c%22Oid%22%3a%2290574fc0-50a2-4e9a-a90f-f9b6f305b092%22%7d tel:+14699986602,,869539392 https://dialin.teams.microsoft.com/d8d2f7a3-2364-4c9b-ab3d-7f613057a66c?id=869539392 https://teams.microsoft.com/meetingOptions/?organizerId=90574fc0-50a2-4e9a-a90f-f9b6f305b092&tenantId=e154a760-1d2d-4ef6-8fd3-ebc8b4ef31fd&threadId=19_meeting_YzU2OTRhMDItNGZjOC00NDllLThmOWItODJjN2I0NmRkZDJm@thread.v2&messageId=0&language=en-US https://dialin.teams.microsoft.com/usp/pstnconferencing https://detroit.bonfirehub.com/ http://www.detroitmi.gov/suppliersupport

Revised 12/2/2025 Page 2 of 21

Proposals must be uploaded in EUNA Bonfire on or prior to the date and time indicated above. Late and/or emailed proposals will not be accepted.

Revised 12/2/2025 Page 3 of 21

TABLE OF CONTENTS

Section 1. Project Summary and Background

1.1. PROJECT REQUEST

1.2. BACKGROUND/DESCRIPTION OF ENVIRONMENT

1.3. AWARD CLAUSE INCLUDING RENEWAL OPTIONS

Section 2. Statement of Work

2.1. SERVICES TO BE PERFORMED

2.2. OPERATIONAL INFORMATION

2.3. TECHNICAL INFORMATION

2.4. PAYMENT & PERFORMANCE BOND (Construction) . Error! Bookmark not defined.

Section 3. Proposal Evaluation and Selection Process

3.1. MINIMUM QUALIFICATIONS

3.2. ADHERENCE TO TERMS OF PROPOSALS

3.3. QUESTION DEADLINE

3.4. EVALUATION CRITERIA

3.5. EVALUATION PROCEDURE

3.6. ORAL PRESENTATION/DEMONSTRATION

3.7. REJECTIONS, MODIFICATIONS, CANCELLATIONS

3.8. PROTESTS

Section 4. Required Proposal Content and Submission Process

4.1. ACCURACY AND COMPLETENESS OF INFORMATION

4.2. REQUIRED PROPOSAL CONTENT AND FORMAT

4.3. REQUIRED COST PROPOSAL

4.4. ECONOMY OF PREPARATION

4.5. SUBMITTAL INSTRUCTIONS

Section 5. General Conditions and Requirements for RFP

5.1. CONTRACT APPROVAL

5.2. PAYMENT

5.3. INVOICES

5.4. ASSIGNMENT

5.5. MODIFICATION OF SERVICES AFTER CONTRACT APPROVAL

5.6. NEWS RELEASE

5.7. MISCELLANEOUS

5.8. OFFICE OF INSPECTOR GENERAL

RFP Attachments List

Revised 12/2/2025 Page 4 of 21

Section 1. Project Summary and Background

1.1. PROJECT REQUEST

The City of Detroit Office of Contracting and Procurement (OCP) on behalf of the Detroit Police Department (DPD) requests proposals from qualified and experienced respondents to provide a Gunshot Detection System for deployment across targeted zones within the City of Detroit. The respondent’s Gunshot Detection System must be able to seamlessly integrate with the City of Detroit’s existing public safety technology infrastructure. The system should support real-time data exchange, alerting, and interoperability with the following applications and platforms currently in use by DPD:

1. Video Management System (VMS)/CCTV Infrastructure (Genetec)

2. Computer Aid Dispatch (CAD) (Central Square One Solution)

3. Motorola License Plate Reader System (Motorola Vigilant)

4. Flock’s License Plate Reader System (Flock Safety Falcon)

5. The City’s Real-Time Crime Center Solution (Motorola Aware)

The Gunshot Detection System shall be accessible and fully functional across multiple platforms, including:

1. Windows-based desktop and laptop computers

2. Apple iOS devices (iPhone, iPad, Mac)

3. Android mobile devices and tablets

The system should include a secure web-based or application-based interface that allows authorized DPD users to:

1. View real-time alerts, incident locations, and mapped data.

2. Access historical event data, analytics, and reports.

3. Receive push notifications and audible alerts for gunfire activations.

The platform should support role-based user access and comply with City of Detroit cybersecurity standards, ensuring data encryption, authentication, and secure communication protocols.

As part of the evaluation process, the City of Detroit requires all shortlisted vendors to demonstrate their Gunshot Detection System in a real-world environment.

• Location: The demonstration will take place at a location designated by DPD within the City of Detroit limits.

• Purpose: The purpose of this demonstration is to validate system performance, including:

o Real-time detection and classification of gunshots o Accurate geolocation of the incident o System-generated alerts and notifications o Integration capabilities with existing DPD systems (if applicable)

• Setup: Vendors will be responsible for all setup, configuration, and testing required for the demonstration.

Revised 12/2/2025 Page 5 of 21

• Requirements: The demonstration must occur under normal working conditions and reflect the real-time operational performance of the proposed system. At a minimum, the system must demonstrate the following capabilities:

o Sensor range and responsiveness o Detection accuracy and false positive/negative handling o System interface (dashboard, maps, alerts) o Live integration with all DPD Public Safety Applications (if available)

• Scheduling: Demonstration dates will be coordinated after proposal review and vendor shortlisting. The City will provide reasonable notice and logistical support for site access. The demonstration period will last approximately 12 weeks.

Failure to participate in or successfully complete the demonstration may result in disqualification from further consideration

1.2. BACKGROUND/DESCRIPTION OF ENVIRONMENT

The Detroit Police Department and its more than 2,600 officers and 900 non-sworn professionals are responsible for policing and supporting Detroit’s 139 square miles. The Department receives over 1.3 million calls for service every year. Through data-informed policing strategies, collaborative partnerships, and innovative programs with high levels of community engagement, Detroit has seen sustained reductions in nearly every category of crime. The Detroit Police Department is committed to transparency, professionalism and 21st-century policing excellence informed by community input and civic leadership.

The Detroit Police Department (DPD) currently operates an acoustic gunshot detection system supplied by SoundThinking, Inc. (product name: ShotSpotter). DPD first acquired the technology in 2020 and began deployment in limited areas of the 8th and 9th Precincts in March 2021, later expanding coverage with City Council approval on October 11, 2022.

Today, DPD operates a gunshot detection system spanning approximately 39 square miles across 9 of the city’s 11 precincts. In 2024, the system generated 14,695 published alerts associated with roughly 54,000 detected rounds, contributing directly to 373 arrests and the recovery of 596 firearms (These numbers are estimates) .

Revised 12/2/2025 Page 6 of 21

The following map illustrates the current ShotSpotter coverage areas within the City of Detroit

Current 6.48 N/A N/A Area 1 8.54 Area 7 3.89 Area 2 1.70 Area 9 3.08 Area 3 2.22 Area 10 1.05 Area 4 4.23 Area 11 0.88 Area 5 2.45 Area 12 3.75

1.3. AWARD CLAUSE INCLUDING RENEWAL OPTIONS

If a contract is awarded as a result of this RFP, it will be a City of Detroit IT Contract (Attachment E). All objections to the Standard Contract must be submitted with the proposal.

The nature and volume of the changes requested may impact on the proposal’s overall score.

Changes not submitted with the proposal will not be considered.

The term of the contract will be for 5 years. Any renewal option exercised under this contract is effective only after the approval of the Detroit City Council and signed by the Chief Procurement Officer. The City anticipates one award as a result of the RFP.

Revised 12/2/2025 Page 7 of 21

Section 2. Statement of Work

2.1. SERVICES TO BE PERFORMED

The Respondent shall furnish all labor, materials, equipment, supervision, project management, and technical expertise necessary to design, install, test, and commission a Gunshot Detection System (GDS) within designated areas of the City of Detroit. The work will include, but is not limited to, the following tasks:

1. System Design and Planning

• Conduct site surveys and acoustic modeling to determine optimal sensor placement.

• Coordinate with DPD, Department of Innovation and Technology (DoIT), Detroit Public Lighting Authority (PLA) and Detroit Public Works (DPW) to confirm coverage boundaries, infrastructure access, and power/network requirements.

• Develop detailed engineering and installation plans, including sensor locations, connectivity diagrams, and mounting specifications.

• Provide documentation outlining system capacity, coverage area, and anticipated performance metrics (e.g., detection radius, alert latency, accuracy rate).

2. Equipment Procurement and Configuration

• Supply and configure all hardware and software components required for the system, including:

• Acoustic sensors and mounting assemblies.

• Network communication equipment (e.g., routers, cellular modems, cabling).

• Power supplies and backup systems.

• Monitoring, alerting, and data management software.

• Ensure all equipment meets or exceeds industry standards and DPD technical requirements.

3. Installation and Integration

• Install acoustic sensors and associated infrastructure in the approved coverage zones.

• Integrate the system with existing DPD platforms and technology, including:

o Video Management System (VMS)/CCTV Infrastructure (Genetec) o Computer Aid Dispatch (CAD) (Central Square One Solution) o Motorola License Plate Reader System (Motorola Vigilant) o Flock’s License Plate Reader System (Flock Safety Falcon) o The City’s Real-Time Crime Center Solution (Motorola Aware)

• Perform all necessary testing to verify detection accuracy, location precision, and reliable communication of alerts

4. System Testing and Commissioning

• Conduct acceptance testing in coordination with DPD to verify system functionality and performance.

• Document and certify all installations.

• Provide final as-built drawings and configuration documentation.

Revised 12/2/2025 Page 8 of 21

• Deliver system activation and performance reports.

5. Maintenance and Support

• Offer ongoing technical support, system monitoring, performance reporting.

• Provide preventive maintenance at regularly scheduled intervals

• Provide rapid response for equipment or software issues

• Ensure compliance with data retention and privacy policies established by DPD Project Details:

Respondents are requested to perform the required services within the areas where gunshot detection coverage currently exists, as well as in additional areas identified for system expansion.The map below illustrates new areas designated for expansion of the gunshot detection system within the City of Detroit.

Respondents should review the map to understand current deployment boundaries and proposed expansion zones to ensure accurate planning, resource allocation, and installation logistics.

2.2. OPERATIONAL INFORMATION

Awarded Contractor(s) will work closely with City agency staff.

The Respondent is expected to provide service in accordance with the terms of the executed contract and under the rules, regulations, and supervision of the City.

Equipment Shipping Equipment should not be shipped to the installation location prior to installation. Vendor should anticipate storing any equipment that will arrive prior to installation and relocating it to the installation location.

2.3. TECHNICAL INFORMATION

City Data Standards

Maps of Gunshot Detection Areas

Revised 12/2/2025 Page 9 of 21

The City is committed to centralizing and warehousing Data for the purpose of improving service delivery and enabling cross departmental analytics. The System must enable Data access, Data interoperability, warehousing of resulting Data, and adherence to City data standards which the City has provided to the Contractor for review.

Specifically, the System requires:

• We require access to all System data for automated data warehousing purposes, provided through at least one of the following machine-readable methods:

o Preferred: Direct database access, or access to a reporting database (ODBC-compatible) o Alternative: API access providing data in one or more of the following formats: JSON, CSV, or XML

• Full documentation of APIs (including field names and objects) and the database schema used by the application.

• Ability for City to programmatically update data within the System as needed via API

• Any location-based data or platform utilizes the City’s base units geocoder, Base Units

Database, and/or address Data standards as applicable.

• The ability for the City to use and govern Data as it deems necessary-- centralizing it, porting it into other systems, and using it for additional and future organizational needs.

• Data collected, transferred and stored meet minimum standards to ensure confidentiality, integrity and availability.

• Data to meet compliance rules / regulations in order to ensure the sensitive digital assets are guarded against loss, theft and misuse. These rules come in a number of forms including applicable industry compliance / standards (i.e. HIPAA, PII, PCI-DSS, NIST, ISO), state or federal-level laws or even supra-national regulations.

• The System must have the capacity to store field-level metadata and display it in the user interface when appropriate

• API is able to provide Data in a JSON format.

The City of Detroit maintains a diverse technical environment that supports a range of computing and mobile platforms. City users primarily operate on HP-branded desktops and laptops, supplemented by Android and Windows-based mobile tablets and cellphones.

Two web browsers are utilized across DPD Microsoft Edge, and Google Chrome.

While the City of Detroit’s Department of Innovation and Technology (DoIT) has broadly adopted a “cloud-first” strategy for the selection and procurement of new software solutions, the Detroit Police Department (DPD) has not fully adopted this approach.

DPD evaluates technology solutions based primarily on operational and functional requirements specific to law enforcement use cases. As such, preference is not automatically given to fully managed Software-as-a-Service (SaaS) environments.

However, DPD is willing to consider SaaS solutions that demonstrate compliance with the Department’s information security, performance, and scalability standards, and that can be effectively integrated within DPD’s secure network and operational framework.

Revised 12/2/2025 Page 10 of 21

The proposed system shall support Microsoft Azure Multi-Factor Authentication (MFA) and Single Sign-On (SSO) integration.

The solution must:

• Integrate seamlessly with the City of Detroit’s Azure Active Directory (AAD) environment for user authentication.

• Support federated identity management to allow secure, centralized access control.

• Comply with DPD and City of Detroit information security and access control policies.

• Provide role-based permissions and audit logging to ensure proper access management and accountability.

Specifications, Change of Specification, and Errors or Omission. Specifications which refer to brand names are given for reference. Respondents may quote on equivalent articles, provided that brand name and catalog number(s) and any deviations are noted on the bid form and complete descriptive literature is furnished. Exceptions will state “Do Not Substitute.”

The decision of the City shall be final.

PURCHASING AND DEMO OPTIONS

Respondents shall provide a detailed description of all plans and pricing structures available for the proposed Gunshot Detection System. This information must clearly identify the terms, conditions, and costs associated with each option offered.

All pricing shall be itemized and broken down by square miles of coverage, including costs for:

• System installation and configuration.

• Hardware, software, and licensing fees.

• Network or communication infrastructure (if applicable).

• Maintenance, support, and renewal terms.

• Optional features or system enhancements.

The Respondent’s proposal must clearly demonstrate how all project phases, subscription terms, maintenance agreements, and renewal periods will be made coterminous with the overall contract end date.

Respondents shall ensure that all services, including installation, implementation, software licensing, hosting, maintenance, and support— are structured to expire or renew on the same end date established for the primary contract term.

The proposal should outline the methodology and schedule for aligning all project components under a unified contract timeline to ensure administrative consistency, and budget clarity to DPD.

Revised 12/2/2025 Page 11 of 21

Section 3. Proposal Evaluation and Selection Process

3.1. MINIMUM QUALIFICATIONS

Proposals will only be accepted from those firms demonstrating a minimum of 5 years of experience providing the services requested in the RFP for projects of similar scope and size.

Vendor Experience and Qualifications Respondents must provide detailed information on previous projects in which they served as the primary vendor for the implementation of a gunshot detection system or similar technology solution. Projects must be of comparable size and scope to the Detroit Police Department’s Gunshot Detection System project and demonstrate the respondent’s ability to perform all required services, including system design, installation, integration, and support.

For each project, respondents shall include:

• Client name and jurisdiction.

• Description of project scope (coverage area, technology deployed, integration components).

• Project duration and implementation timeline.

• Respondent’s role and responsibilities.

• Performance outcomes (system uptime, detection accuracy, etc.).

• Client references with contact information.

3.2. ADHERENCE TO TERMS OF PROPOSALS

A proposal once accepted by the City of Detroit, may become a binding contractual obligation of the Respondent. The failure of a successful Respondent to accept this obligation and to adhere to the terms of the Respondent’s proposal may result in rejection of the proposal and the cancellation of any provisional award to the respondent. Respondents are not permitted to take advantage of any errors or omissions in specifications since full instructions will be given should they be discovered before bid submission date.

3.3. QUESTION DEADLINE

All questions regarding the RFP shall be submitted through the Supplier Portal no later than the time and date specified in the solicitation. In the interest of transparency, only written questions will be accepted. Answers to questions will be posted within the Supplier Portal. The City of Detroit does not guarantee a response to questions submitted after the question deadline.

Should a Respondent be in doubt as to the true meaning of any portion of this RFP or find any patent ambiguity, inconsistency, or omission herein, the Respondent must make a written request for an official interpretation or correction in accordance with the instructions for submitting questions as specified in this RFP.

Respondents are advised that no oral interpretation, information or instruction by an officer or employee of the City of Detroit shall be binding upon the City of Detroit.

Respondents requesting changes to the RFPs terms and conditions, specifications, quantities, etc.; or if clarifications are needed, must make the request in writing by the stated bid submission deadline.

3.4. EVALUATION CRITERIA

Technical Proposals will be evaluated before Cost Proposals are reviewed.

http://www.michigan.gov/SIGMAVSS

Revised 12/2/2025 Page 12 of 21

PHASE ONE CRITERIA – NON-ECONOMIC DEVELOPMENT

Proposal Evaluation Criteria Possible Points

1. Technical Approach Implementation, Project Management and System Design

• Demonstrated understanding of DPD’s objectives and operational environment.

• Technical soundness of the proposed system design and configuration.

• Coverage capability, detection accuracy, alert speed, and data reliability.

• Integration capabilities with DPD’s mobile platforms.

• System scalability and flexibility for future expansion.

• Realistic and achievable implementation plan and schedule.

• Approach to site assessment, sensor placement, testing, and commissioning.

• Training plan for DPD users and system administrators.

• Risk management strategy and mitigation measures.

2. Technical Compatibility and Security

• Performance in the Demo

• Compatibility with the City and DPD’s technical environments.

• Compliance with DPD’s cybersecurity standards, including support for Azure MFA and Single Sign-On (SSO).

• Availability and accessibility on Windows, Android, and iOS devices.

• Data privacy, encryption, and retention practices.

3. Vendor Experience and Qualifications

• Proven experience as the primary vendor on projects of similar size and scope.

• Demonstrated success in implementing and supporting law enforcement gunshot detection systems

• Quality of client references and documented performance outcomes

• Qualifications and experience of key project personnel.

4. Software maintenance and support. 10

5. Pricing.

• Demonstration of how all contract phases, licenses, and support terms will be made coterminous with the contract end date.

• Proposed service level agreements (SLAs) and performance guarantees.

• Responsiveness to ongoing maintenance, support, and system updates.

Total Points Possible 65

Revised 12/2/2025 Page 13 of 21

Detroit Equalization Credits according to the following table shall be applied after the technical and price evaluation. (Please see Equalization Credit Statement for more information)

Detroit Equalization Credits – Prime Contractor Possible Points

Detroit Headquartered Business 5 Detroit Based Business 2 Detroit Resident Business 5 Construction Workforce Investment Business (Construction over $1M) 3 Construction Workforce Development Business 3 Detroit Small Business 1 Detroit Micro Business Concern 2 Joint Venture 2 Mentor Venture 1

3.5. EVALUATION PROCEDURE

Following the receipt of proposals, a City designated Evaluation Committee will evaluate each response. All PROPOSALS, which meet the required format of this RFP, will be evaluated. Any proposals determined to be non-responsive to the specifications or other requirements of the RFP, including instructions governing submission and format, will be disqualified unless the City determines, in its sole discretion, that non-compliance is not substantial or that an alternative proposed by the Respondent is acceptable.

The City may also at its discretion, request oral presentations, make site visits at Respondent’s facility and may request a demonstration of Respondent’s operations. If scheduled, a final determination will be made after the oral presentations and/or demonstrations are complete.

The City may also at its sole discretion, elect to rank order the qualified proposals, and negotiate with some limited number of the highest scored qualified respondents. A final determination would include the cumulative inputs of this evaluation procedure. All decisions reached by the Evaluation Committee will be by consensus.

Any of the additional data specs and standards described in Section 2.3, that are met will be factored positively into the overall score.

3.6. ORAL PRESENTATION/DEMONSTRATION

The City reserves the right, at its own discretion, to request oral presentations regarding proposals submitted in response to the RFP. Failure to make an oral presentation will be grounds for rejection of your proposal. Respondents will be notified by the Office of Contracting and Procurement of the date, time and location for oral presentations.

3.7. REJECTIONS, MODIFICATIONS, CANCELLATIONS

The City of Detroit expressly reserves the right to:

1) accept or reject, in whole or in part, any and all proposals received;

Revised 12/2/2025 Page 14 of 21

2) waive any non-conformity;

3) re-advertise for proposals;

4) withhold the award for any reason the City determines;

5) cancel and/or postpone the request for proposals, in part or in its entirety, and/or,

6) take any other appropriate action that is in the best interest of the City.

This RFP does not commit the City of Detroit to award a contract, to pay any cost incurred in the preparation of a proposal under this request, or to procure or contract for services.

3.8. PROTESTS

Protests can be filed with the Office of Procurement. Interested parties aggrieved by a solicitation or the award of any resulting contract, may file written notice of protest to the following:

City of Detroit Chief Procurement Officer 2 Woodward Avenue, Suite 1008

Detroit, MI 48226 “Procurement Protest”

At a minimum, such protests shall include:

1) name of protestor.

2) solicitation/contract number and description; and

3) statement of grounds for protest (reference specific text in the solicitation, bid or contract document that is at issue).

An actual or prospective bidder or offeror whose direct economic interest would be affected by the award of a contract or the failure to award a contract has the right to protest any aspect of the solicitation, evaluation, or selection process of a City of Detroit procurement.

A protest by a prospective bidder which challenges the terms of the solicitation itself must be received by the City no later than 4:00 p.m. EST of the business day prior to the date scheduled for the bid closure. Failure to meet this deadline shall result in a protester waiving its ability to challenge the terms of the solicitation.

A protest by a bidder which challenges a contract award must be received no later than 4:00 p.m.

EST five (5) business days after the award of a City procurement. Failure to meet this deadline shall result in a protester waiving its ability to challenge the contract award.

All protests must be submitted in writing and received by the required timeframe.

The Chief Procurement Officer (CPO) or as delegated, the Deputy CPO, has the sole authority to respond to, decide and act upon supplier protests.

The decision of the Chief Procurement Officer and/or the Department Director are final and is not subject to appeal.

Revised 12/2/2025 Page 15 of 21

Section 4. Required Proposal Content and Submission Process

4.1. ACCURACY AND COMPLETENESS OF INFORMATION

All information pertaining to the prospective respondent’s approach in meeting the requirements of the RFP shall be organized and presented in the prospective respondent’s proposal. The instructions contained in this RFP must be strictly followed.

Accuracy and completeness are essential. Omissions and ambiguous or equivocal statements will be viewed unfavorably and may be considered in the evaluation. Since all or a portion of the successful proposal may be incorporated into any ensuing contract, all prospective respondents are further cautioned not to make any claims or statements that cannot be subsequently included in a legally binding agreement.

4.2. REQUIRED PROPOSAL CONTENT AND FORMAT

To be considered responsive, each proposal must, at a minimum, respond to the following RFP sections in their entirety, responses must be uploaded in the Supplier Portal along with the Affidavit of Disclosure Interests Form and Non- Collusion Affidavit found under requirements section of the of RFP#541086:

Respondents must submit a comprehensive proposal that fully addresses all requirements outlined in this Request for Proposal (RFP) for the Gunshot Detection System (GDS). Proposals must be organized, clear, and complete to allow for an objective evaluation by DPD.

1. Cover Letter and Executive Summary

• Briefly introduce the Respondent and summarize the key features of the proposed solution.

• Include the company’s legal name, headquarters address, and the name, title, phone number, and email address of the primary point of contact.

• Acknowledge the Respondent’s understanding of the project objectives and confirm commitment to meeting all requirements.

2. Company Background and Qualifications

• Overview of company history, years in business, and experience in public safety technology.

• Description of organizational structure, key staff, and resources available for this project.

• Documentation of financial stability and ability to fulfill contractual obligations.

3. Vendor Experience

• Detailed description of prior projects where the Respondent served as the primary vendor for gunshot detection or similar systems.

• Projects should be of comparable size and scope to DPD’s proposed deployment.

• Include client names, jurisdictions, project scope, coverage area, system type, implementation dates, outcomes, and references.

4. Technical Proposal

• Detailed description of the proposed Gunshot Detection System, including architecture, detection technology, coverage capabilities, and accuracy.

• Description of integration capabilities with DPD systems (CAD, RMS, RTCC, MDT).

• Demonstration of compatibility with DPD’s technical environment, including Windows, Android, and iOS devices.

Revised 12/2/2025 Page 16 of 21

• Confirmation of support for Azure MFA and Single Sign-On (SSO).

• Description of cybersecurity measures, data retention, and privacy protection

5. Implementation and Migration Plan

• Comprehensive plan outlining the installation, configuration, and commissioning of the proposed system.

• A detailed Migration Plan from DPD’s existing gunshot detection system, including data transfer, continuity of operations, and testing procedures.

• Project schedule with milestones, dependencies, and estimated completion dates.

• Staffing plan identifying key personnel and roles throughout implementation.

6. Training and Support Plan

• Description of training programs for DPD personnel (end users, administrators, and technical staff).

• Outline of ongoing maintenance, technical support, and system monitoring services.

• Escalation procedures and service response time commitments.

7. Pricing and Purchasing Options

• Detailed cost proposal broken down by square mile of coverage.

• Itemized pricing for hardware, software, installation, support, and optional features.

• Terms, conditions, and length of any demo programs offered.

• Description of how all contract phases will be made coterminous with the contract end date.

8. Service Level Agreements (SLAs)

• Proposed SLAs outlining system uptime, alert accuracy, response time, and maintenance standards.

• Description of performance monitoring and reporting processes.

9. Additional Information (Optional)

• Any other information the Respondent believes may assist the City in evaluating the proposal, such as innovation, added value, or community engagement initiatives.

Required Response Item

1. Attachment A – Respondent Questionnaire

Respondent shall provide their Organization Experience and Capacity/Staffing, per the requirements provided in Attachment A.

2. Attachment B – Proposal Introduction and Solution / Approach Respondent shall provide their Proposal Introduction and Solution / Approach per the requirements provided in Attachment B.

3. Attachment C – Pricing Respondent shall provide their Pricing proposal, per the requirements provided in Attachment C.

4. Attachment D1 – Forms, Affidavits and Documents – Bid Requirements Respondent shall provide their completed Certificate of Authority, Non-Collusion Affidavit, and Affidavit of Disclosure of Interests, in Attachment D1.

5. Attachment D2 – Conditions of Award - Award Winners Only Respondent will be required to provide their completed Forms, Affidavits, Insurance and Documents, if they are selected as the award winner provided in Attachment D.

6. Attachment E – Model Information Technology Services Contract Respondent shall provide their agreement to the Model Information Technology Services Contract or note any exceptions provided in Attachment E.

Revised 12/2/2025 Page 17 of 21

Required Response Item

7. Attachment F.1, F.2, F.3 – Technical and Functional Requirements Matrixes (if applicable) Respondent shall fully complete one or all Attachments F.1, F.2, F.3 to this RFP and submit with their proposal.

4.3. REQUIRED COST PROPOSAL

Respondents are requested to make a firm cost proposal to the City of Detroit, through the completion of Attachment C. If a contract is entered into as a result of this RFP, it will be a contract for fees as related to providing all requested services, with a price not to exceed the total price quoted in the proposal. The City of Detroit reserves the right to select proposals from the most responsible Respondents with the most reasonable costs. The City reserves the right to select one or more firms to perform all or separate parts of this function.

4.4. ECONOMY OF PREPARATION

Proposals should be prepared simply and economically providing a straightforward, concise description of the Respondent’s ability to meet the requirements of the RFP. Emphasis should be on the completeness and clarity of content.

4.5. SUBMITTAL INSTRUCTIONS

All proposals must be submitted through the Bonfire/EUNA Procurement Supplier Portal at detroit.bonfirehub.com. Each Respondent is responsible for ensuring that its proposal is received by the City on a timely basis. Faxed or mailed proposals will not be accepted.

Firms shall not distribute their proposals to any other City office or City employee. Proposals received become the property of the City. The City is not responsible for any costs associated with preparation or submission of proposals. All proposals submitted by the due date will be recorded in the Supplier Portal. Responses received will not be available for review. Proposals received will be subject to disclosure under the state of Michigan’s Freedom of Information Act. An officer of the company authorized to bind the company to a contractual obligation with the City must sign the proposals in the Supplier Portal. The successful respondent will receive an award letter. Respondents who are not awarded will receive a notification that the award decision has been made.

Support Channels for Technical Difficulties and Questions Visit https://detroitmi.gov/suppliersupport for:

- Guides on how to register in EUNA

- Guides on how to submit a response to the solicitation

- FAQs

Contact Bonfire’s technical support in the portal for:

- Technical issues with the e-bidding portal

- Registration problems

- Help submitting responses through the system

Contact the City (eprocurement@detroitmi.gov) for:

- General procurement process questions

- City-specific requirements and policies

For Solicitation/Project-Specific Questions:

https://detroitmi.gov/suppliersupport https://detroit.bonfirehub.com/portal/support mailto:eprocurement@detroitmi.gov

Revised 12/2/2025 Page 18 of 21

- Submit all solicitation-related questions through the Public Q&A tab in the Bonfire/EUNA Procurement portal. This ensures all vendors receive the same information and maintains transparency in the bidding process. Emails and calls regarding solicitation-specific questions will not receive a response.

Section 5. General Conditions and Requirements for RFP

5.1. CONTRACT APPROVAL

Upon contract award, the City and the successful Respondent shall execute a professional services contract, which shall contain all contractual terms and conditions in a form provided by the City. No contract shall become effective until the contract has been approved by the required City Departments and Detroit City Council and signed by the City of Detroit Chief Procurement Officer. Prior to the completion of this approval process, the successful Respondent shall have no authority to begin work under the contract. The Chief Financial Officer shall not authorize any payments to the successful Respondent prior to such approvals; nor shall the City incur any liability to reimburse the successful Respondent regarding any expenditure for the purchase of materials or the payment of services.

5.2. PAYMENT

All properly executed invoices submitted by the successful Respondent will be paid in accordance with the City of Detroit Prompt Payment Ordinance.

5.3. INVOICES

Vendors must be registered in City of Detroit Vendor Portal and be a registered vendor with the City of Detroit to submit invoices and receive payments. Go to http://www.detroitmi.gov/Supplier to register.

AUTHORIZATION TO COMMENCE WORK OR SHIP GOODS – READ

CAREFULLY!!!

Contractors may begin work or ship goods upon receipt of the required authorization, which is the CPA (Contract Purchase Agreement), in addition to SPO (Standard Purchase Order), from Procurement.

The CPA (City Council Approved and Awarded Contract Purchase Agreement) alone is NOT authorization to begin work! NO letter of Intent, or Letter to Commence Work will be issued.

**Work commencing without issuance of the SPO is subject to Payment Delays and/or Non- Payment! **

Required vendor steps to invoice:

1) Vendors should submit their invoices via City of Detroit Oracle Vendor Portal.City of Detroit Oracle Vendor Portal. Portal invoice amount and creation date must match the date on attached invoice. Please follow the below invoice requirements:

Invoice MUST contain or have as attachment:

• Vendor Name and address on Invoice

• Contact Info on Invoice (Accounts Receivable contact with phone and email) http://www.detroitmi.gov/Supplier https://ebkk.login.us8.oraclecloud.com/oam/server/obrareq.cgi?ECID-Context=1.006GbR8nJ1j0zkVay1Na6G001bnV0000sM%3BkXjE

Revised 12/2/2025 Page 19 of 21

• Remittance information (MUST be included, or the invoice is subject to rejection

• City of Detroit contact (person who authorized work to commence)

• Invoice Date

• Date of service/delivery

• Contract number

• Purchase order number

• Total Invoice amount

• The wording “ Goods/Services” (must be noted on every invoice)

Other invoice requirements:

• Invoice must be billed based on Purchase Order rates

• Total invoice amount must tie to the total supporting documents

• Supporting documentation must be attached to the invoice in the portal

Terms are standard NET 30 Days, unless otherwise negotiated, and start from the invoice receipt date, provided that the invoice is submitted timely to our AP department with the necessary supporting documentation.

If you need payment assistance, please contact the Office of Departmental Financial Services

(ODFS) 313-410-7804.

For technical assistance, please visit detroitmi.gov/suppliersupport.

5.4. ASSIGNMENT

The services to be performed by the successful Respondent shall not be assigned, sublet, or transferred, nor shall the successful Respondent assign any monies due or to become due to him under any contract entered into with the City pursuant to these specifications, without prior written approval of the City.

5.5. MODIFICATION OF SERVICES AFTER CONTRACT APPROVAL

The City reserves the right to modify the services provided by the successful Respondent awarded a contract. Any modification and resulting changes in pricing shall be made by amendment to the contract by the successful Respondent and the City.

5.6. NEWS RELEASE

News releases pertaining to these proposal specifications or the provisions to which they relate shall not be made without prior approval of the City and then only in coordination with the City.

5.7. MISCELLANEOUS

It shall be the responsibility of the Respondent to thoroughly familiarize themselves with the provisions of these specifications. After executing the contract, no consideration will be given to any claim of misunderstanding.

The Respondent agrees to abide by the rules and regulations as prescribed herein by the City as the same now exists or may hereafter from time to time be changed in writing.

Contractors are encouraged to contract with small and minority businesses, women's business enterprises, labor surplus area firms and Detroit businesses. The City strongly

Revised 12/2/2025 Page 20 of 21 encourages the hiring of Detroit residents whenever possible by contacting Detroit At Work for your hiring needs. Visit the Detroit At Work website for specific contact information regarding these opportunities.

Contractors are encouraged to employ innovative approaches, including ethically and responsibly leveraging artificial intelligence and advanced technologies, to enhance goods delivery, services, and operational performance. Vendors using AI solutions will be asked to provide information on how the AI solution functions.

5.8. OFFICE OF INSPECTOR GENERAL

5.8.1. In accordance with Section 2-106.6 of the City Charter, this Contract shall be voidable or rescindable at the discretion of the Mayor or Inspector General at any time if a Public Servant who is a party to the Contract has an interest in the Contract and fails to disclose such interest.

5.8.2. This Contract shall also be voidable or rescindable if a lobbyist or employee of the contracting party offers a prohibited gift, gratuity, honoraria or payment to a Public Servant in relation to the Contract.

5.8.3. A fine shall be assessed to the Contractor in the event of a violation of Section 2-106.6 of the

City Charter. If applicable, the actions of the Contractor, and its representative lobbyist or employee, shall be referred to the appropriate prosecuting authorities.

5.8.4. Pursuant to Section 7.5-306 of the City Charter, the Inspector General shall investigate any

Public Servant, City agency, program or official act, contractor and subcontractor providing goods and services to the City, business entity seeking contracts or certification of eligibility for City contracts and person seeking certification of eligibility for participation in any City program, either in response to a complaint or on the Inspector General’s own initiative in order to detect and prevent waste, abuse, fraud and corruption.

5.8.5. In accordance with Section 7.5-310 of the City Charter, it shall be the duty of every Public

Servant, contractor, subcontractor, and licensee of the City, and every applicant for certification of eligibility for a City contract or program, to cooperate with the Inspector General in any investigation pursuant to Article 7.5, Chapter 3 of the City Charter.

5.8.6. Any Public Servant who willfully and without justification or excuse obstructs an investigation of the Inspector General by withholding documents or testimony, is subject to forfeiture of office, discipline, debarment or any other applicable penalty.

5.8.7. As set forth in Section 7.5-308 of the City Charter, the Inspector General has a duty to report illegal acts. If the Inspector General has probable cause to believe that any Public Servant or any person doing or seeking to do business with the City has committed or is committing an illegal act, then the Inspector General shall promptly refer the matter to the appropriate prosecuting authorities.

For purposes of this Article: “Public Servant” means the Mayor, members of City Council, City Clerk, appointive officers, any member of a board, commission or other voting body established by either branch of City government or the City Charter, and any appointee, employee or individual who provides services to the City within or outside of its offices or facilities pursuant to a personal services contract.

https://urldefense.com/v3/__https:/descmiworks.org/business-services/__;!!NcXZSU8rfchoEksI!efgwb7Az7YQ1WNYz08X3skt7ah9Lt0tZnoFrliM4GlUH9iYP4Dtz_l03Xya-8iVDi2esZRdC59m0O9Xl8DlelS4a5w$

Revised 12/2/2025 Page 21 of 21

RFP Attachments List

The following Attachments are available to download on the Supplier Portal.

Attachment A - Respondent Questionnaire Attachment B - Proposal Introduction and Solution / Approach Attachment C - Pricing Attachment D - Forms, Affidavits and Documents-(Award winner only) Attachment E - Model Information Technology Services Contract Attachment F – Technical and Functional Requirements

RFP Attachments List