Public Safety Common Operating Platform

The Vendor is required to provide 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.
- Requirement:
•    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.
- Mandatory functional requirements
1. Common operating picture and map interface
•    Provide a map-based operating interface showing integrated public safety assets in a single view.
•    Display camera locations, automated license plate reader assets, calls for service, alerts, and connected systems on one map.
•    Provide real-time alerting for watch list hits, sensor activations, or similar events.
•    Include traffic or routing context to support response decisions.
•    Allow custom map layers, floor plans, school safety plans, critical infrastructure references, or similar overlays to be associated with locations.
•    Support role-based access to the operating map from desktop, MDT, tablet, and mobile devices.
•    Support controlled multi-agency collaboration and shared situational awareness views where authorized by policy.
2. Automated license plate reader integration
•    Integrate with existing and future ALPR and LPR systems.
•    Display reader locations and related alerts within the operating map.
•    Allow authorized users to review relevant plate-reader activity near incidents and investigative events.
•    Support watch list and hotlist alerting.
•    Support vehicle-attribute or vehicle-fingerprint style search capabilities where offered.
•    Support shared or federated watch lists and hotlists and NCIC or equivalent alerting where authorized.
•    Clearly identify any optional proactive analytics such as plate-swap detection, convoy detection, hotspot alerts, or similar advanced LPR functions.
3. CAD, 911, and call-for-service integration
•    Support cad integration so calls for service may appear automatically on the map.
•    Allow users to select a call and identify nearby relevant resources.
•    Support 911 caller-location and associated call information where technically feasible.
•    Present operational data in one interface to improve situational awareness.
•    Support live or near-real-time 911 event updates, audio, and transcript information where technically feasible.
•    Automatically surface nearby cameras, sensors, units, and other relevant resources in connection with calls for service or active incidents where supported.
4. Emergency call, sensor, and drone integration
•    Support integration with gunshot detection, audio detection, panic alarm, duress, or similar sensor systems where technically feasible.
•    Support integration with drone operations or drone-as-first-responder workflows where offered.
•    Automatically associate incident events with nearby cameras, sensors, or aerial assets when technically feasible.
•    Clearly identify whether such capabilities are included in base pricing or require optional modules or third-party services.
5. Officer and vehicle location integration
•    Support officer or vehicle geolocation from compatible AVL, MDT, body-worn camera, dash camera, mobile router, or similar sources.
•    Display unit location in relation to calls, cameras, and incidents.
•    Support supervisory response coordination.
•    Support historical playback or incident playback of unit movement where available from integrated sources.
6. Video integration and unification
•    Support integration of existing and future city-owned or approved partner camera systems.
•    Allow authorized users to view third-party video streams within the platform, subject to compatibility.
•    Support expansion into downtown areas, parks, facilities, schools, intersections, and critical infrastructure.
•    Support gateway-based, VMS-based, direct-stream, or equivalent video integration methods.
•    Support community-partnership or approved shared-camera programs where authorized by policy.
•    Support public/private/community camera sharing with granular permission controls.
•    Clearly identify supported ingestion methods, latency considerations, and any transcoding, gateway, or bandwidth dependencies.
7. Records management system (RMS) and data-fusion integration
•    Support RMS integration for incident, person, vehicle, address, case, or call context where technically feasible.
•    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.
•    Identify supported connectors, implementation dependencies, and any data normalization or licensing requirements.
8. Capacity and scalability
•    Provide meaningful baseline deployment capacity.
•    Provide a growth path for additional users, streams, cameras, gateways, retention, or other capacity.
•    Allow phased deployment without replacing the platform.
•    Clearly identify licensing tiers, minimum quantities, and limitations.
•    Clearly identify what is included in the base deployment, including user counts, cameras, streams, gateways, storage, retention, or similar capacity metrics.
•    Describe software update cadence, release management practices, and how feature changes are communicated to administrators.
9. Investigative search and case support
•    Provide advanced search capability across available LPR, video, and related data where applicable.
•    Include efficient investigative search tools, including natural-language or equivalent search if available.
•    Allow users to organize alerts, reads, clips, calls, or related artifacts for case-support purposes.
•    Support export or handoff of evidentiary artifacts to external systems where technically feasible.
•    Support cross-system investigative search across integrated LPR, video, CAD, RMS, and related data where available.
•    Support saved searches, shared bolos, collaborative case workspaces, or similar investigative workflow tools where offered.
•    Support case-number tagging, reason-for-search entry, or similar accountability controls where available.