Public Safety Technology

Finance Department
General Services Division
REQUEST FOR PROPOSALS (RFP)
Specification No. 26-11794-C
FOR
Public Safety Technology
PROPOSALS WILL NOT BE OPENED AND READ PUBLICLY
Dear Proposer:
The City of Berkeley is soliciting written proposals from qualified firms or individuals for (1) Automated License
Plate Recognition (ALPR); (2) Fixed Video Surveillance Cameras (Pan-Tilt-Zoom); (3) Drone as First
Responder (DFR); (4) Field-Deployed Drones (Unmanned Aerial Systems); (5) Community Video Stream
Integration; and (6) Investigative Software. As a Request for Proposal (RFP) this is not an invitation to bid and
although price is very important, other factors will be taken into consideration.
The project scope, content of proposal, and vendor selection process are summarized in the RFP (attached).
Proposals must be received no later than 2:00 pm, on Thursday, August 20, 2026. Proposals are to be sent via
email with "Specification No. 26-11794-C" and "Public Safety Technology" clearly indicated in the subject line
of the email. Please submit one (1) PDF of the technical Proposal with the filename saved as, "Proposal: Vendor
Name - #26-11794-C Public Safety Technology." Corresponding pricing proposal shall be submitted as a separate
document with the filename saved as, "Pricing: Vendor Name - #26-11794-C Public Safety Technology."
Email Proposals to:
City of Berkeley
Finance Department/General Services Division
Solicitations@berkeleyca.gov
Proposals will not be accepted after the date and time stated above. Incomplete proposal or proposals that do not
conform to the requirements specified herein will not be considered. Issuance of the RFP does not obligate the City
to award a contract, nor is the City liable for any costs incurred by the proposer in the preparation and submittal of
proposals for the subject work. The City retains the right to award all or parts of this contract to several bidders, to
not select any bidders, and/or to re-solicit proposals. The act of submitting a proposal is a declaration that the
proposer has read the RFP and understands all the requirements and conditions.
For questions concerning the anticipated work, or scope of the project, please contact (Project Managers) Deputy
Chief Jen Tate and Arlo Malmberg, Strategic Planning and Accountability Manager, via email at
jtate@berkeleyca.gov no later than July 20th, 2026. Answers to questions will not be provided by telephone or
email. Answers to all questions or any addenda will be posted on the City of Berkeley's site at Bid & Proposal
Opportunities | City of Berkeley (berkeleyca.gov). It is the vendor's responsibility to check this site. For general
questions concerning the submittal process, contact purchasing at 510-981-7320.
We look forward to receiving and reviewing your proposal.
Sincerely,
Henry Oyekanmi
Finance Director
2180 Milvia Street, Berkeley, CA 94704 Tel: 510.981.7320 TDD: 510.981.6903
E-mail: purchasing@berkeleyca.org Website: cityofberkeley.info/finance/

City of Berkeley Specification No. 26-11794-C Page 2 of 28
Public Safety Technology Release Date 07/07/26
I. BACKGROUND/SUMMARY/or INTRODUCTION
The Berkeley Police Department (BPD) is advancing a public safety technology program designed to
improve situational awareness, operational efficiency, crime prevention, and investigative capacity while
maintaining civilian oversight, auditability, and data protection.
Through this RFP the City seeks proposals across up to six Technology Areas: (1) Automated License
Plate Recognition (ALPR); (2) Fixed Video Surveillance Cameras (Pan-Tilt-Zoom); (3) Drone as First
Responder (DFR); (4) Field-Deployed Drones (Unmanned Aerial Systems); (5) Community Video
Stream Integration; and (6) Investigative Software. The Technology Areas are described in Section II.
This is a modular solicitation. Proposers may submit on a single Technology Area, any combination of
Areas, or all Areas. The City may make award by individual Area, by combination, or in whole, and may
select more than one vendor. The City will consider the operational, oversight, privacy, auditability, cost
advantages and disadvantages of a consolidated, interoperable solution when comparing single-Area
awards against combined awards. Regardless of the Area(s) proposed, all solutions must satisfy the Cross-
Cutting Requirements in Section II.G.
The technologies sought are governed by the City's Surveillance Technology Ordinance (BMC 2.99), the
Police Equipment Ordinance (BMC 2.100), the Sanctuary City Contracting Ordinance (BMC 13.105), the
Sanctuary City Ordinance (BMC 13.114) and applicable state law including AB 481, SB 34 and SB 54.
Data ownership, privacy protection, alignment with the City's sanctuary policies, restrictive-by-default
configuration, breach accountability, and robust auditing are central to this procurement and are reflected
as scored requirements throughout.
II. SCOPE OF SERVICES
The selected vendor(s) will furnish the equipment, software, installation, integration, training,
maintenance, and support described below for a base term of three (3) years, with extension options to be
exercised at the City's sole discretion. Where hardware is involved, the City prefers an all-inclusive,
vendor-managed (subscription) model. Each Technology Area is independently scoped,
independently scored, and may be independently awarded. A proposer responding to more than one Area
must describe how the proposed components interoperate.
Cross-Cutting Requirements (Apply to All Technology Areas)
The following requirements apply to every proposal regardless of the Technology Area(s) proposed.
Contractual Protections
The following contractual requirements apply to all agreements executed under this RFP. Proposers must
explicitly accept these requirements or clearly identify any proposed exceptions or alternative
formulations in their submission. The City may deem material exceptions to required privacy, data
ownership, data-sharing, security, auditability, sanctuary policy, or breach accountability provisions as
grounds for disqualification or reduced scoring.
* The agreement shall provide for a financial penalty of $290,000 per violation for any unauthorized
sharing, disclosure, or release of City data. This penalty is in addition to, and does not limit, any
other remedies available to the City under contract or applicable law.
* The City shall have the right to terminate the agreement for convenience upon thirty (30) days'
written notice. Fees paid prior to termination shall be non-refundable except as offset by
applicable penalties; the City shall bear no liability for fees or payments that would otherwise
come due after the effective termination date.
RFP Revised Nov2022

City of Berkeley Specification No. 26-11794-C Page 3 of 28
Public Safety Technology Release Date 07/07/26
* Any license granted to the vendor to use anonymized or de-identified data derived from City data
or City-generated data shall be expressly limited in duration to the term of the agreement. No such
license shall survive the termination or expiration of the contract, regardless of how the license
grant is framed.
* The vendor shall not implement any hardware or software modification that alters the scope of
data access, data sharing, or data availability without prior written consent from the City. Routine
maintenance, security patches, and bug fixes that do not affect the scope of data access or sharing
are exempt. Proposers shall describe their standard process for notifying customers of platform
changes and how they will accommodate this requirement.
* Any post-execution modification to provisions governing data ownership, data access, data
sharing, privacy protections, or security requirements shall require affirmative action by the
Berkeley City Council.
* The vendor shall notify the City and obtain the City's written consent before disclosing any City
data in response to any legal request or demand, including subpoenas, court orders, or equivalent
legal process. This notification and consent requirement shall not apply if and only if the vendor is
both (a) legally required to produce the data in response to the specific request and (b) legally
prohibited from informing the City that the request exists.
* The vendor may not assign its rights or obligations under this agreement, in whole or in part,
without the City's prior written consent. Any purported assignment without such consent shall be
null and void and shall constitute a material breach of the agreement.
Data Ownership and Privacy
* The City owns all of its data, including anonymized derivatives. The vendor is prohibited from
selling, sharing, or distributing City data without the City's explicit written authorization.
* The vendor may disclose City data to a government agency only upon a valid legal request and
with the City's written consent. Consistent with the City's sanctuary policies, data and footage may
not be provided to federal immigration authorities in response to an administrative subpoena or
similar request absent a court order.
* Consistent with California law, City data may not be used, shared, or disclosed to support any
investigation, prosecution, or civil action arising under a law of another state that restricts or
criminalizes the provision or receipt of reproductive health care or gender-affirming care that is
lawful in California. The vendor may not provide City data to any out-of-state authority for such a
purpose absent a court order issued by a California court.
* Settings must be restrictive (privacy-protective) by default; no data-sharing defaults may be
enabled without affirmative City action.
* Facial recognition is prohibited and must be unavailable, disabled, or incapable of use unless
expressly authorized by the Berkeley City Council through a future approval process.
* The City's ownership and control of its data survives termination, and the vendor must return or
export City data on termination.
Security and Compliance
* The system must be Criminal Justice Information Services (CJIS) compliant.
* Data must be encrypted in transit and at rest, with role-based access controls.
* The vendor must promptly notify the City of any security incident or data breach, describing
its scope and the corrective steps taken.
* The vendor must agree to contractual financial penalties for data breaches or unauthorized
disclosures.
* The vendor must support the City's reporting obligations under BMC 2.99, BMC 2.100, and AB
481.
Auditing and Reporting
* Granular auditing sufficient to identify and track usage by any user at any time.
RFP Revised Nov2022

City of Berkeley Specification No. 26-11794-C Page 4 of 28
Public Safety Technology Release Date 07/07/26
* Permission/security levels defining user rights and access.
* Administrator visibility into deployments, queries and hotlists/alerts for all users including date
and time, and reason for query or deployment.
* Predesignated reports plus ad-hoc reporting from the collected data, and export of audit data.
* Configurable retention parameters for access logs, including retention period, what data is
captured per log entry, whether the City can configure retention duration, and whether logs are
exportable.
Installation, Training, Maintenance, and Support
* For Areas involving hardware, an all-inclusive solution: hardware, installation, software,
connectivity, cloud storage, maintenance, support, and a warranty covering the contract term, with
City permitting and inspection fees included. The vendor shall not use third-party installers or
maintenance providers unless disclosed and approved.
* Training for administrators, supervisors, and end-users, including training on system features,
usage, maintenance, and auditing.
* Ongoing maintenance, software updates, and technical support.
Interoperability
* Every component must expose or support documented integrations so the City can correlate data
across systems even where Areas are awarded to different vendors. Proposers bidding multiple
Areas must describe native interoperability among the proposed components; proposers bidding a
single Area must describe the published integrations and APIs available to connect to other
systems and to the RTIC.
* Every component must support integration with Axon Evidence.com via the Axon Partner API or,
at minimum, export of evidentiary files in a format suitable for direct upload to Evidence.com;
proposers must describe their current pathway and disclose any dependency on a third-party
partnership agreement with Axon that is not fully executed at time of proposal. Exported files
shall preserve original metadata and a documented chain of custody suitable for evidentiary use.
Artificial Intelligence and Human-in-the-Loop Operation
* All AI-generated output including automated alerts, matches, classifications, and
recommendations shall be treated as an investigative lead only and must be independently
corroborated before any enforcement, charging, or detention decision. No investigative action may
be initiated or executed solely on the basis of AI output without affirmative human review and
authorization.
* Proposers must identify every action or automated function their system is capable of executing
without real-time human authorization including but not limited to automated alerts, cross-system
queries, data sharing, and any output routed to officers or dispatchers, and describe the controls
available to the City to restrict, audit, or disable those functions.
* Proposers must describe how their system is designed to support human-in-the-loop operation,
including what interface features, access controls, and workflow configurations are available to
ensure that automated outputs are reviewed before action is taken.
* Default system configurations must not enable automated enforcement-adjacent actions (e.g.,
automatic hotlist sharing, automatic case flagging, or automatic inter-agency notification) without
affirmative City configuration.
Technology Area 1- Automated License Plate Recognition (ALPR)
License plate recognition for fixed and/or mobile deployment supporting real-time alerting and
investigative search, integrated into the City's real-time information center. Proposers must respond
to each specification listed below. If a proposer cannot meet a specification, the proposal must
clearly state that limitation and describe any alternative approach.
* Be deployable at locations where no existing City electrical power or network infrastructure is
available. Proposers shall describe how their solution achieves and sustains power and
RFP Revised Nov2022

City of Berkeley Specification No. 26-11794-C Page 5 of 28
Public Safety Technology Release Date 07/07/26
connectivity independent of wired infrastructure, and shall address expected uptime, maintenance
intervals, and performance under the operational conditions typical of an urban environment.
* Include vendor installation, mounting, City permitting and inspection, maintenance, and support
for the contract term, with City permitting and inspection fees included in the cost.
* Provide remote health monitoring and self-diagnostics for each device.
* Provide a map-based locator of camera positions and support publication of camera locations on
the City website.
* Provide secure access via PC and iOS/Android apps.
* Support remote configuration, search, and alert management through the vendor interface.
* Capture at least two lanes of traffic simultaneously from a single camera.
* Provide real-time alerts to a user or group via mobile app, email, and text message when a plate on
a hotlist enters the database.
* Support hotlist management- view, add to, and remove from alert lists; manual entry of any
number of plates of interest.
* Allow expiration dates on alerts, with notice to the user before an alert is set to expire, and notify
users of duplicate entries or alerts.
* Provide search by: full or partial plate with wildcard support; start/end date and time; contributing
device or camera name (multi-select); and location with proximity range (geocoded address,
latitude/longitude, or map-drawn area).
* Allow manual search and alerting based on a vehicle's physical description, with or without plate
information.
* Include a mapping utility presenting a geographic overlay of hit data on a user-defined map.
* Disclose all cross-jurisdictional access networks (statewide lookup, national lookup, and
equivalent) and confirm participation in any such network is opt-in only.
* Support a configurable data retention period that conforms to the City's ALPR Use Policy and
applicable law (currently 30 days), with automatic purge of records upon expiration.
BPD currently operates a network of approximately 52 ALPR cameras. Proposers shall provide pricing
for a network of 52 cameras and shall provide unit pricing for additional cameras beyond that baseline.
Proposers shall describe how their platform licensing and management infrastructure scales as camera
count increases, including whether additional licensing tiers or fees apply.
Technology Area 2- Fixed Video Surveillance Cameras (Pan-Tilt-Zoom)
Solar-powered pan-tilt-zoom (PTZ) fixed video cameras installed and maintained by the vendor, with live
and recorded video accessible within the RTIC. Proposers must respond to each specification listed
below. If a proposer cannot meet a specification, the proposal must clearly state that limitation and
describe any alternative approach.
* Be able to operate on battery and solar power without tapping into wired power or network
infrastructure, using cellular connectivity.
* Include vendor installation, mounting, City permitting and inspection, maintenance, and support
for the contract term, with City permitting and inspection fees included in the cost.
* Provide remote health monitoring and self-diagnostics for each device.
* Provide a map-based locator of camera positions and support publication of camera locations on
the City website.
* Provide secure access via PC and iOS/Android apps.
* Support remote configuration, search, and alert management through the vendor interface.
* Provide pan, tilt, and zoom control, high-resolution day/night imaging, and configurable fields of
view.
RFP Revised Nov2022

City of Berkeley Specification No. 26-11794-C Page 6 of 28
Public Safety Technology Release Date 07/07/26
* Support live streaming and retrieval of recorded video, with remote operation of camera controls.
* Audio recording is prohibited; cameras must either lack audio capability entirely or provide an
administrator-controlled setting to disable audio recording permanently, off by default.
The City anticipates initial deployment at 16 locations approved by the City Council. Proposers shall
provide all-inclusive per-location pricing for 16 camera installations and shall provide unit pricing
for additional locations. Proposers shall describe any cost or configuration differences based on site
conditions, mounting requirements, or connectivity constraints.
Technology Area 3- Drone as First Responder (DFR)
A drone-as-first-responder capability integrated into the City's real-time platform, with launch from fixed
docking stations, detect-and-avoid for safe operation, and real-time aerial video delivered to dispatchers
and responding officers and in appropriate cases arriving on scene before ground units. This Area covers
the fixed-site, dock-based DFR program; officer-deployed portable drones are addressed separately in
Area 4. Proposers must respond to each specification listed below. If a proposer
cannot meet a specification, the proposal must clearly state that limitation and describe any
alternative approach.
* Provide drone(s) with docking/charging station(s) supporting launch and return from fixed sites.
* Provide detect-and-avoid capability sufficient for safe beyond-visual-line-of-sight (BVLOS)
operation under appropriate authorizations.
* Stream real-time video and telemetry to dispatch and field personnel, with integration to
computer-aided dispatch (CAD) where available.
* Support configurable privacy protections during transit to a call, including the ability to elevate
camera angle, restrict the field of view, or otherwise limit incidental capture of persons and
property not associated with the incident to which the drone is responding; such transit-mode
configurations shall be available as a default operating mode.
* Offer a National Defense Authorization Act (NDAA)-compliant hardware pathway. Proposers
must state whether currently offered hardware is NDAA-compliant and, if not, the specific
migration path and timeline.
* Support recording, retention, and redaction consistent with City policy, with complete flight
logging and an audit trail.
* Provide role-based operator controls, operator/pilot training, and maintenance and support for the
term.
* Support the City's reporting obligations under BMC 2.100 and AB 481 for controlled equipment.
* Proposers must identify all applicable regulatory prerequisites, including FAA Part 107
certification, Certificate of Waiver (COW), or other applicable FAA authorization for BVLOS or
nighttime operations, and must describe the vendor's role and track record in supporting agencies
through the current FAA approval process.
* Be all-inclusive (airframes, docks, software, connectivity, maintenance, and warranty).
* Audio recording is prohibited; drone must either lack audio capability entirely or provide an
administrator-controlled setting to disable audio recording permanently, off by default.
The City anticipates an initial deployment of 2 docking stations with associated aircraft. Proposers shall
price for a 2-unit deployment and shall provide optional pricing for a third docking station and aircraft.
Proposers shall clearly identify any cost differences between the first and subsequent units, including any
shared infrastructure, software licensing, or connectivity costs that do not scale linearly. The City may
expand the fleet subject to City Council approval under BMC 2.100.
RFP Revised Nov2022

City of Berkeley Specification No. 26-11794-C Page 7 of 28
Public Safety Technology Release Date 07/07/26
Technology Area 4- Field-Deployed Drones (Unmanned Aerial Systems)
Portable, officer-deployed unmanned aerial systems (UAS) transported in patrol or supervisor vehicles
and launched manually by a trained pilot at an incident scene. Unlike the dock-based DFR capability in
Area 3, these aircraft require no fixed infrastructure and support on-demand aerial assessment for tactical
operations, critical incidents, building searches, crowd and traffic-collision documentation, and natural-
disaster response, including in indoor and GPS-denied environments. Proposers must respond to each
specification listed below. If a proposer cannot meet a specification, the proposal must
clearly state that limitation and describe any alternative approach.
* Provide drone(s) suitable for rapid field deployment from a vehicle, including transport cases,
spare batteries, and field-charging equipment; the proposed suite shall include both outdoor
airframes and at least one indoor-capable airframe designed for GPS-denied interior operations.
* Support manual, pilot-operated visual-line-of-sight (VLOS) flight, with optional payloads such as
high-resolution zoom and thermal/infrared imaging as proposed; indoor drones shall support
obstacle avoidance and stable flight in confined, GPS-denied spaces.
* Stream real-time video and telemetry to dispatch and field personnel, with integration to
computer-aided dispatch (CAD) where available.
* Offer a National Defense Authorization Act (NDAA)-compliant hardware pathway. Proposers
must state whether currently offered hardware is NDAA-compliant and, if not, the specific
migration path and timeline.
* Support recording, retention, and redaction consistent with City policy, with complete flight
logging and an audit trail.
* Provide role-based operator controls, operator/pilot training, and maintenance and support for the
term.
* Support the City's reporting obligations under BMC 2.100 and AB 481 for controlled equipment.
* Identify all regulatory prerequisites (e.g., FAA Part 107, applicable waivers) and the vendor's role
in helping the City obtain them.
* Be all-inclusive (airframes, payloads, batteries, transport cases, software, connectivity,
maintenance, and warranty).
The City anticipates an initial deployment of 4 outdoor field-deployable airframes and 4 indoor airframes
designed for GPS-denied interior operations. Proposers shall price these as two distinct line items and
shall provide unit pricing for each airframe type separately.
Technology Area 5- Community Video Stream Integration
Software enabling BPD to view live or recorded video from privately owned cameras whose owners
voluntarily register and opt in to share access. The City does not purchase or install any cameras under
this Area. Proposers must respond to each specification listed below. If a proposer
cannot meet a specification, the proposal must clearly state that limitation and describe any alternative
approach.
* Provide camera registration and mapping, with owner opt-in required before any access and the
ability for owners to revoke access at any time; owners retain full ownership of their cameras and
footage.
* Route a registered feed to the department only with the camera owner's explicit permission.
* Facial recognition is prohibited and must be unavailable, disabled, or incapable of use unless
expressly authorized in writing by the Berkeley City Council through a future approval process..
* Apply restrictive (privacy-protective) settings by default.
* The platform shall not ingest, transmit, or store audio from registered community cameras; audio
capture by participating camera owners is outside the scope of this program and BPD access to
any audio feed is prohibited.
RFP Revised Nov2022

City of Berkeley Specification No. 26-11794-C Page 8 of 28
Public Safety Technology Release Date 07/07/26
The number of registered community cameras will vary based on voluntary owner participation.
Proposers shall provide tiered pricing at defined increments (for example: up to 50 cameras, 51-150, 151-
300, and 300+) and shall describe any platform costs that are fixed regardless of camera count. Proposers
shall also provide unit pricing for registered feeds beyond the highest proposed tier.
Technology Area 6- Investigative Software
A data-analysis and real-time integration platform that both (a) centralizes records from the department's
computer-aided dispatch (CAD), records management system (RMS), and digital evidence to support
case-linking and investigative resolution, and (b) functions as the City's public safety technology platform
offering a single pane of glass that correlates ALPR reads, fixed-camera video, drone video, community
streams, and analytics into one dashboard with a single sign-on, one set of access logs, and one audit trail.
Because the City may award individual Technology Areas to different vendors, the platform proposed
under this Area must be capable of integrating with third-party systems across all other Areas, not only
with the proposer's own products. Proposers may offer this Area as a combined platform, as a standalone
investigative-analytics tool, or as a standalone aggregation/integration platform that ingests third-party
sensors via published integrations and APIs, and/or as the native platform underlying other Areas they
propose. Proposers must respond to each specification listed below. If a proposer cannot meet
a specification, the proposal must clearly state that limitation and describe any alternative approach.
Investigative analytics:
* Ingest and integrate structured and unstructured data from CAD, RMS, and digital evidence;
proposers must identify supported systems and the integration approach.
* Provide auto-refresh of CAD calls for service to ensure up-to-date operational awareness.
* Enable case-linking and entity resolution across all connected data sources and support the ability
to cross-reference vehicle and person information across sources.
* Provide access to open-source intelligence and shared inter-agency data, with configurable access
controls, audit logging, and security measures for all shared information.
* Provide comprehensive search, data visualization, dashboards, and both predesignated and ad-hoc
reporting.
* Capable of alerts when other users search on same criteria (i.e.: deconfliction)
* Provide a "breadcrumbs" or equivalent workflow feature that
allows operators to document the steps taken to reach a conclusion or investigative action.
* Provide description of granular inter-agency access controls and confirmation that inter-agency
sharing and deconfliction features are off by default.
Technology integration platform:
* Present a single dashboard that correlates multiple live and recorded data sources (ALPR, fixed-
camera video, drone video, and community streams) in real time, with single sign-on
and consolidated alerts across source types.
* Ability to customize and "drag and drop" data/views from maps, camera views, search results,
tables, documents, etc.
* Ability to pop-up/highlight a specific camera when a CAD call falls within a viewshed of that
camera.
* Real-time alert capabilities based on keywords or criteria.
* Provide open, documented integrations and APIs to third-party ALPR, fixed-camera, drone,
analytics, and CAD/RMS systems. Proposers must list known/allowed integrations with real-time
crime center and CAD platforms.
* Provide geospatial mapping, location/radius search, map-drawn search areas, and alert routing via
app, email, and text.
* Provide a dashboard of system productivity (alert volumes, detection and hit volumes, and
accuracy ratios) presented as charts or raw data with filters by source, user, or system.
RFP Revised Nov2022

City of Berkeley Specification No. 26-11794-C Page 9 of 28
Public Safety Technology Release Date 07/07/26
* Ability to draw a geo-fence using a shape tool for easily configurable alerts.
* Ability to easily turn live layers on and off for different visualization schemas.
Proposers shall provide tiered pricing by user count at defined increments (for example: up to 25 users,
26-75, 76-150, and 150+) and shall separately identify any costs that are fixed regardless of user count,
including platform, integration, or data ingestion fees. Where pricing varies by data volume or connected
source type, proposers shall describe that structure and provide pricing at comparable tiers.
III. SUBMISSION REQUIREMENTS
All proposals shall include the following information, organized as separate sections of the proposal. The
proposal should be concise and to the point.
1. Contractor Identification:
Provide the name of the firm, the firm's principal place of business (see section VII, F. - Local Vendor
Preference), the name and telephone number of the contact person and company tax identification
number.
2. Client References:
Provide a minimum of five (5) client references. References should be California cities or other large
public sector entities. Provide the designated person's name, title, organization, address, telephone
number, and the project(s) that were completed under that client's direction.
3. Price Proposal:
The proposal shall include pricing for all services for the base contract term of three (3) years, with
separately itemized optional pricing for an additional one-year extension period. Pricing shall be all
inclusive unless indicated otherwise. Pricing proposals shall be a separate document. The Proposal
shall itemize all services, including hourly rates for all professional, technical and support personnel,
and all other charges related to completion of the work shall be itemized. Evaluation of price
proposals are subject to the local vendor business preference (see section VII.F.).
RFP Revised Nov2022

City of Berkeley Specification No. 26-11794-C Page 10 of 28
Name of RFP Release Date 7/7/26
4. Contract Terminations and Security Incidents:
If your organization has had a contract terminated in the last five (5) years or experienced a
data security incident or data-sharing violation, describe such incident. Termination for default is
defined as notice to stop performance due to the vendor's non-performance or poor performance and
the issue of performance was either (a) not litigated due to inaction on the part of the vendor, or (b)
litigated and such litigation determined that the vendor was in default.
Submit full details of the terms for default including the other party's name, address, and phone
number. Present the vendor's position on the matter. The City will evaluate the facts and may, at its
sole discretion, reject the proposal on the grounds of the past experience.
If the firm has not experienced any such termination for default or early termination in the past five
(5) years, so indicate.
5. (Other submission requirements needed to evaluate proposals and determine if contractor is
qualified to do project.)
IV. SELECTION CRITERIA
* Effective 1/1/2022. Local Vendor Preference. For the purposes of comparing pricing as part of this
competitive RFP for goods up to $100,000 or non-professional services up to $250,000, 5% shall be
deducted from the bid price proposal from any local Berkeley vendor.
A selection panel of City staff will evaluate and score proposals. Each Technology Area
is scored independently on a 100-point scale using the criteria below. The City may award by individual
Area, by combination, or in whole.
Based on the contents of the proposal, a live or virtual demonstration may or may not be requested by the
selection panel and considered within the criteria below.
Data Security, Privacy, and Compliance - 30 points
* Security and privacy features in alignment with the relevant requirements in Section II.
* CJIS compliance; City data ownership; restrictive-by-default configuration.
* Alignment with the City's sanctuary policies and limits on federal/immigration access; breach
notification and contractual financial penalties for unauthorized disclosure.
* Strength of auditing, access controls, and City-controlled retention, and exportable audit data.
* Acceptance of required City contractual terms related to data ownership, privacy, security,
auditability, breach notification, sanctuary policy compliance, and restrictions on unauthorized
disclosure.
* Responsiveness to relevant specifications detailed in the Scope of Services.
Technical Solution and Functional Capabilities - 30 points
RFP Revised Nov2022