RFP 2026-03 PUBLIC SAFETY COMMON OPERATING PLATFORM

Public Safety Common Operating Platform
RFP 2026-03
April 17, 2026
TO: All Interested Parties
FROM: James Jones, Captain, Criminal Investigations Division
SUBJECT: RFP for Common Operating Platform
The City of Perry, Georgia, invites interested and qualified parties to submit proposals to provide a
Common Operating Platform for the Perry Police Department.
A copy of the RFP is enclosed for your consideration. Questions regarding this solicitation may be
directed to:
James "Jason" Jones, Captain, Criminal Investigations Division
(478) 988-2825
james.jones@perry-ga.gov
Instructions for the preparation and submission of a response are contained in this package. All
submittals are due no later than 4:00 PM on May 8, 2026, and are to be submitted to:
The City of Perry
Attn: Finance Department
1211 Washington Street
P.O. Box 2030
Perry, GA 31069

Public Safety Common Operating Platform
RFP 2026-03
Request for Proposals
The City of Perry, Georgia, through the Perry Police Department, is soliciting sealed proposals from
qualified firms for the furnishing of software, implementation services, integrations, training, support,
and related professional services for a Public Safety Common Operating Platform.
The purpose of this solicitation is to obtain a scalable, map-based public safety platform that can unify
and display operational data from law enforcement systems, including but not limited to cameras,
automated license plate reader systems, dispatch/call information, officer or vehicle location data, and
related public safety technologies, in a common operating environment for authorized users.
The Perry Police Department seeks a public safety operating platform capable of serving as a common
operating picture for patrol, supervisors, investigators, command staff, dispatch, and other authorized
personnel. The platform shall support current operational needs and future growth into expanded
camera coverage, public safety integrations, school or facility coverage, investigative workflows, and
regional collaboration. The requested feature set is based on the Department's required operational
standards for a unified map-based platform with integrated LPR, CAD/911, officer location, video,
search tools, secure access, and scalability.
All submittals are due no later than 4:00 PM on May 8, 2026. Instructions for submitting can be found
in the "Submission Requirements" section of this document.
Scope of Services
The successful proposer shall provide all labor, software, licensing, implementation, configuration,
training, integration, and support necessary to deploy a fully functional system.
At a minimum, the proposer shall provide:
* software subscriptions or licenses,
* implementation and onboarding,
* configuration and role-based access setup,
* integration services,
* administrator and end-user training,
* ongoing maintenance and technical support,
* expansion pricing for future growth.
Page 2 of 10

Public Safety Common Operating Platform
RFP 2026-03
Mandatory Functional Requirements
The proposer shall clearly indicate whether each requirement is Compliant, Partially Compliant, or
Non-Compliant, and shall provide a narrative explanation.
The proposer shall also clearly identify whether each listed capability is included in the proposed base
platform, provided through an optional module, or available through third-party integration and shall identify
any material dependency, limitation, or additional licensing requirement.
Common Operating Picture / Map Interface
The solution shall:
a. Provide a map-based operating interface showing integrated public safety assets in a single view.
b. Display camera locations, automated license plate reader assets, calls for service, alerts, and
connected systems on one map.
c. Provide real-time alerting for watchlist hits, sensor activations, or similar events.
d. Include traffic or routing context to support response decisions.
e. Allow custom map layers, floor plans, school safety plans, critical infrastructure references, or
similar overlays to be associated with locations.
f. Support role-based access to the operating map from desktop, MDT, tablet, and mobile devices.
g. Support controlled multi-agency collaboration and shared situational awareness views where
authorized by policy.
Automated License Plate Reader Integration
The solution shall:
a. Integrate with existing and future ALPR/LPR systems.
b. Display reader locations and related alerts within the operating map.
c. Allow authorized users to review relevant plate-reader activity near incidents and investigative
events.
d. Support watchlist/hotlist alerting.
e. Support vehicle-attribute or vehicle-fingerprint style search capabilities where offered.
f. Support shared or federated watchlists/hotlists and NCIC or equivalent alerting where authorized.
g. Clearly identify any optional proactive analytics such as plate-swap detection, convoy detection,
hotspot alerts, or similar advanced LPR functions.
CAD, 911, and Call-for-Service Integration
The solution shall:
a. Support CAD integration so calls for service may appear automatically on the map.
b. Allow users to select a call and identify nearby relevant resources.
c. Support 911 caller-location and associated call information where technically feasible.
d. Present operational data in one interface to improve situational awareness.
e. Support live or near-real-time 911 event updates, audio, and transcript information where
technically feasible.
f. Automatically surface nearby cameras, sensors, units, and other relevant resources in connection
with calls for service or active incidents where supported.
Page 3 of 10

Public Safety Common Operating Platform
RFP 2026-03
Emergency Call, Sensor, and Drone Integration
The solution shall:
a. Support integration with gunshot detection, audio detection, panic alarm, duress, or similar sensor
systems where technically feasible.
b. Support integration with drone operations or drone-as-first-responder workflows where offered.
c. Automatically associate incident events with nearby cameras, sensors, or aerial assets when
technically feasible.
d. Clearly identify whether such capabilities are included in base pricing or require optional modules
or third-party services.
Officer / Vehicle Location Integration
The solution shall:
a. Support officer or vehicle geolocation from compatible AVL, MDT, body-worn camera, dash
camera, mobile router, or similar sources.
b. Display unit location in relation to calls, cameras, and incidents.
c. Support supervisory response coordination.
d. Support historical playback or incident playback of unit movement where available from integrated
sources.
Video Integration and Unification
The solution shall:
a. Support integration of existing and future city-owned or approved partner camera systems.
b. Allow authorized users to view third-party video streams within the platform, subject to
compatibility.
c. Support expansion into downtown areas, parks, facilities, schools, intersections, and critical
infrastructure.
d. Support gateway-based, VMS-based, direct-stream, or equivalent video integration methods.
e. Support community-partnership or approved shared-camera programs where authorized by policy.
f. Support public/private/community camera sharing with granular permission controls.
g. Clearly identify supported ingestion methods, latency considerations, and any transcoding, gateway,
or bandwidth dependencies.
Records Management System (RMS) and Data-Fusion Integration
The solution shall:
a. Support RMS integration for incident, person, vehicle, address, case, or call context where
technically feasible.
b. Support optional federated or unified search across integrated sources, including CAD, RMS, LPR,
video, jail records, public records, and other approved investigative data sources where offered.
c. Identify supported connectors, implementation dependencies, and any data normalization or
licensing requirements.
Page 4 of 10

Public Safety Common Operating Platform
RFP 2026-03
Capacity and Scalability
The solution shall:
a. Provide meaningful baseline deployment capacity.
b. Provide a growth path for additional users, streams, cameras, gateways, retention, or other capacity.
c. Allow phased deployment without replacing the platform.
d. Clearly identify licensing tiers, minimum quantities, and limitations.
e. Clearly identify what is included in the base deployment, including user counts, cameras, streams,
gateways, storage, retention, or similar capacity metrics.
f. Describe software update cadence, release management practices, and how feature changes are
communicated to administrators.
Open Architecture / Interoperability
The proposer shall:
a. Provide documented APIs, SDKs, webhooks, or equivalent integration tools.
b. Identify third-party systems currently supported through native, partner, API-based, or custom
integrations.
c. Not require replacement of existing compatible systems solely to achieve core platform
functionality.
d. Provide an integration matrix identifying native integrations, partner integrations, API-based
integrations, and custom integration options.
Investigative Search and Case Support
The solution shall:
a. Provide advanced search capability across available LPR, video, and related data where applicable.
b. Include efficient investigative search tools, including natural-language or equivalent search if
available.
c. Allow users to organize alerts, reads, clips, calls, or related artifacts for case-support purposes.
d. Support export or handoff of evidentiary artifacts to external systems where technically feasible.
e. Support cross-system investigative search across integrated LPR, video, CAD, RMS, and related
data where available.
f. Support saved searches, shared BOLOs, collaborative case workspaces, or similar investigative
workflow tools where offered.
g. Support case-number tagging, reason-for-search entry, or similar accountability controls where
available.
Security, Access, and Auditability
The solution shall:
a. Support role-based permissions.
b. Support single sign-on or equivalent enterprise authentication.
c. Maintain user activity or audit logging where applicable.
d. Support controlled information sharing with approved outside agencies.
e. Describe hosting, encryption, security controls, and CJIS-related safeguards where applicable.
Page 5 of 10

Public Safety Common Operating Platform
RFP 2026-03
f. Describe customer ownership and exportability of agency data.
g. Support configurable retention settings and administrative control over data-sharing permissions.
h. Support supervisor review, purpose logging, or similar accountability controls for searches and information
sharing where offered.
i. Describe any public transparency, audit reporting, or equivalent accountability features.
Training and Support
The proposer shall provide:
a. Initial administrator training
b. End-user training
c. User guides and support documentation
d. Support procedures and escalation paths
e. Project implementation timeline and milestones
f. Administrator documentation for integrations, permissions, and system configuration.
g. Support hours, service-level expectations, and after-hours escalation procedures.
h. Release-note communication, update management, and notice of material functionality changes.
Proposal Format
Proposals shall be organized in the following order:
Tab 1 - Cover Letter and Authorized Signature
Tab 2 - Executive Summary
Tab 3 - Company Qualifications and Experience
Tab 4 - Technical Approach and Solution Narrative
Tab 5 - Response to Mandatory Functional Requirements
Tab 6 - Implementation Plan and Project Schedule
Tab 7 - Training and Support Plan
Tab 8 - Security and Data Protection
Tab 9 - References
Tab 10 - Exceptions and Deviations
Tab 11 - Cost Proposal*
Tab 12 - Integration Matrix
Tab 13 - Optional Modules / Alternate Pricing
*Cost Proposal shall clearly separate:
* one-time implementation costs,
* recurring annual subscription or maintenance costs,
* integration costs,
* training costs,
* optional expansion costs,
* any hardware, gateway, connector, retention, or add-on pricing.
* per-user licensing or access costs,
* per-camera, per-stream, per-gateway, or per-site pricing where applicable,
pricing for optional advanced analytics, DFR, 911, sensor, RMS, search, or other add-on
Page 6 of 10

Public Safety Common Operating Platform
RFP 2026-03
modules, and a clear statement identifying which capabilities are included in the base proposal
versus optional alternates.
Proposal Evaluation and Criteria
Proposals will be evaluated by an internal review panel based on the following factors:
Cost and Value (25 pts)
Relevant Project Experience (references) (25 pts.)
Clarity of Submittal (25 points)
Ability to Meet/Address Mandatory Functional Requirements (25 points)
The City of Perry will award a contract to the qualified individual or firm whose proposal has the highest
number of cumulative points issued by the selection committee and determined to be the most
advantageous to the City of Perry, price and other factors considered.
In evaluating proposals, the City may consider the proposer's clarity regarding included
versus optional functionality, openness of integrations, and long-term scalability within
the scored evaluation factors above.
The City of Perry is an Equal Opportunity Employer and encourages Minority-Owned Business
Enterprises (MBEs) and Woman-Owned Business Enterprises (WBEs) to submit proposals.
Insurance Requirements
Workers' Compensation Insurance:
* State: $100,000 or state required coverage, whichever is greater
* Federal: $200,000 or federally required coverage, whichever is greater
Employer's Liability Insurance:
* $200,000 or the statutorily required coverage, whichever is greater
Comprehensive General Liability Insurance:
* Combined single limit for bodily injury and property damage: $1,000,000 each occurrence;
$2,000.000 combined single limit.
* General aggregate- $2,000,000
* Operations aggregate - $2,000,000
Personal Injury Insurance:
* $1,000,000 each occurrence
Excess/Umbrella Policy:
* $1,000,000 each occurrence; $2,000,000 general aggregate
Comprehensive Automobile Liability Insurance:
Page 7 of 10

Public Safety Common Operating Platform
RFP 2026-03
* Bodily Injury: $1,000,000 each person; $1,000,000 each occurrence
* Property damage: $100,000 each occurrence; combined single limit of $200,000
* Combined single limit per accident for property damage and bodily injury- $2,000,000
The City of Perry retains the right to reject any and all proposals.
It is the policy of the City of Perry to foster, maintain, and promote equal opportunities for all. The City
of Perry does not discriminate on the basis of age, sex, race, color, creed, religion, national origin,
military status, or any other characteristic protected by law.
Submission Requirements
Offerors must submit one (1) original proposal and one (1) USB flash drive (with .pdf copy) of the
complete submittal.
All proposals must be received by May 8, 2026, by 4:00 PM Local Time. Submissions must be
submitted in a sealed box/package either by USPS Mail, FedEx, UPS or Hand Delivered and
identified/labeled on the outside with The Offeror's name and address and project title as follows:
"RFP 2026-03: Public Safety Common Operating Platform" and addressed to:
The City of Perry
Attn: Finance Department
1211 Washington Street
P.O. Box 2030
Perry, GA 31069
Submissions may be hand delivered to the above address only between the hours of 8:00AM and
5:00PM local time Monday through Friday, excluding Holidays observed by the Owner.
Offerors are responsible for informing any commercial delivery service, if used, of all delivery
requirements and for ensuring the required address information appears on the outer
wrapper or container used by such service. Submissions received after said date and time will not be
considered. Having the container postmarked by May 8, 2026, does not meet the requirements of this
RFP. Delivering the document to a commercial delivery service is also not sufficient until the
submittal is actually received at the designated location.
The submissions must be signed by an officer or employee of the company, legally authorized to
enter into a contractual relationship in the name of the Offeror.
Page 8 of 10

Public Safety Common Operating Platform
RFP 2026-03
RFP Questions
Any inquiries regarding this RFP must be submitted in writing no later than 4:00 PM local time April
29, 2026 to:
The City of Perry
Attn: Captain James "Jason" Jones
Captain, Criminal Investigations Division
1207 Washington Street
P.O. Box 2030
Perry, GA 31069
or via e-mail: james.jones@perry-ga.gov. Questions will be answered in writing by addendum.
Questions received after this time will not receive a response.
Additional Information/Addenda
Answers to questions submitted that materially change the conditions and specifications of this RFP
will be distributed to all addressees as an addendum. Any discussions or documents will be
considered non-binding unless incorporated and distributed in an addendum.
Proposers should check with the City of Perry Finance Department frequently during the time that this
solicitation is open to Offerors to verify that they have received all issued addendums. Addendums will
be posted on the City of Perry website (https://perry-ga.gov/business-services/finance/bids-
proposals). While every attempt is made to make sure that registered proposers receive notice of
addendums, proposers have the responsibility of making sure that they have received all issued
addendums.
Page 9 of 10

Public Safety Common Operating Platform
RFP 2026-03
Page 10 of 10