7._RFI_CHP_CISS-25-001_-_Combined.pdf

REQUEST FOR INFORMATION

1 | P a g e

TO: All Interested Suppliers

RE: Request for Information RFI_CISS-25-001

DATE: June 1, 2026

The California Highway Patrol (CHP) Communications Infrastructure & Support Section (CISS) is providing the opportunity for interested suppliers to participate in a Request for Information (RFI).

PLAN OVERVIEW

This RFI will aid the CHP in identifying potential software solutions available to meet the objectives of CISS. Once RFI responses are received, they will be reviewed by the CHP. Invitations may be sent to respondents to participate in demonstrations and pilots and will be based on the completeness and relevance of the RFI response.

RFI RESPONSES

Interested respondents are requested to submit Attachment A, B, C, and D, and any additional comments or documents via e-mail on or before June 30, 2026.

Submitting a response to this RFI will not enhance the review of that Respondent’s proposal(s) to any future solicitations. Failure to submit a response to this RFI will not prohibit a response to any future solicitation, nor disadvantage the evaluation of a response to any future solicitation. By submitting a response to this RFI a Respondent is implicitly agreeing with these conditions.

Questions regarding this RFI should be directed to CISS via the contact information below.

Although providing feedback is important and strongly encouraged, the State makes no commitment to make changes based on the feedback it receives.

TEMPLATE FOR RESPONSE SUBMITTAL

There are four (4) attachments to be completed for this RFI:

• Attachment A – Vendor Profile

• Attachment B – Questionnaire

• Attachment C – Rough Order of Magnitude (ROM)

• Attachment D – SIMM 5305-F Generative Artificial Intelligence Risk Assessment (Required for all GenAI products and services presented by respondents)

CONTACT

CISS-California Highway Patrol

CCSS@chp.ca.gov

DISCLAIMER

This RFI is issued for informational and planning purposes only and does not constitute a solicitation. A response to this RFI is not an offer and cannot be accepted by the CHP to form a binding contract. Interested suppliers are solely responsible for all expenses associated with responding to this RFI.

mailto:CCSS@chp.ca.gov

California Highway Patrol (CHP)

Event Number: RFI_CISS-25-001

Artificial Intelligence Solutions for Public Safety Communications RFI Page 1

CALIFORNIA HIGHWAY PATROL

For

Artificial Intelligence Solutions for Public Safety Communications

Artificial Intelligence Solutions for Public Safety Communications RFI Page 2

Table of Contents 1 Introduction

1.1 Overview

2 Disclaimer 3 Key Action Dates 4 Contact Information 5 Submission of Questions 6 Vendors Declining to Respond 7 RFI Response Instructions

7.1 Cost Information

8 Product/Solution Demonstration

8.1 Vendor Demonstration Days

9 Pilot of Selected Products

9.1 Pilot Requirements

10 Terms and Conditions 11 Generative Artificial Intelligence 12 Project Description and Requirements

12.1 Background

12.2 Operational Objectives

12.3 Additional Considerations

ATTACHMENT A – VENDOR PROFILE

ATTACHMENT B – QUESTIONNAIRE

ATTACHMENT C – ROUGH ORDER OF MAGNITUDE COST ESTIMATE

ATTACHMENT D – SIMM 5305-F, GENERATIVE ARTIFICIAL INTELLIGENCE RISK

ASSESSMENT

Artificial Intelligence Solutions for Public Safety Communications RFI Page 3

Request for Information

DATE: June 1, 2026 TO: All Interested Parties FROM: California Highway Patrol, Communications Infrastructure & Support Section SUBJECT: Event Number: RFI_CISS-25-001

1 Introduction This Request for Information (RFI) is being released by the California Highway Patrol (CHP), Communications Infrastructure & Support Section (CISS). This RFI is not a solicitation. The intention of this RFI is to aid the CHP in determining what is currently available in the marketplace based on the project objectives and requirements as described within this document. Additionally, the CHP would like to evaluate existing product information and feature functionality for possible future solicitations.

1.1 Overview

The purpose of this RFI is to solicit information, suggestions, best practices, and cost estimates from qualified vendors regarding artificial intelligence (AI) based solutions capable of assisting with or automating various responsibilities within CHP’s Public Safety Answering Points (PSAPs). As mentioned, the intent of this RFI is not to select a proposed solution or vendor. This request is being conducted as part of the CHP’s business process review and market research efforts to acquire the necessary information on available products.

To further inform this effort, the CHP is requesting information from vendors about their ability to meet the proposed project requirements and to provide CHP with Rough Order of Magnitude (ROM) budgetary estimates. Additionally, the CHP is requesting information from vendors regarding potential modifications and improvements to the proposed project scope and requirements that may better align with the CHP’s project goals.

As part of the RFI process, collected information provided by the vendor community may be used to develop or identify solution alternatives, specifications, and/or cost estimations necessary to acquire systems, solutions, and/or software. The CHP is asking for cost estimates to be broken down into specific component categories where possible. The CHP understands that data provided in this RFI may not be sufficient to enable detailed analysis and costing by vendors. Provide your response based on your experience with other organizations and initiatives of this kind. Responses to this RFI should adhere to the questions listed in the included attachments. Include estimates for items that may need to be sourced to third party vendors if those items fall outside of your organization’s line of business.

Additionally, in this RFI the CHP is asking vendors targeted questions related to the overall implementation and design of an AI solution to ensure an environment that effectively supports the required environment. Thus, CHP has prepared a supplemental questionnaire (Attachment B) related to the program concepts discussed in this RFI to obtain feedback from the vendor community on ways that CHP can develop a potential solicitation and to better understand the current capabilities that vendors possess related to the implementation of an AI solution for public safety operations.

This effort is informed by the State of California’s evolving policies on the responsible use of AI, including the Governor’s direction to ensure that AI technologies are deployed in a manner

Artificial Intelligence Solutions for Public Safety Communications RFI Page 4 that enhances public service delivery while protecting privacy, civil liberties, and public trust.

The CHP seeks to evaluate solutions that align with these principles by demonstrating transparency, accountability, and appropriate safeguards to prevent misuse or unintended harm.

Completion of this RFI shall be performed at no cost to the State of California or the CHP.

The intent of this RFI is solely for information and planning purposes and does not constitute a solicitation. A contract will not be awarded based on this RFI.

Please read this RFI document thoroughly and adhere to the response submission guidelines.

2 Disclaimer A. This RFI is issued for information and planning purposes only and does not constitute a solicitation or a contract. This RFI nor any information provided by any Respondents hereto shall be deemed to create any legally binding agreement or obligations upon the CHP. This RFI is solely designed to provide the CHP with meaningful information to enable the CHP to determine how to proceed with a possible upcoming project. A response to this RFI is not an offer and cannot be accepted by the state to form a binding contract.

B. Preliminary Solution Requirements: Note that the requirements listed in this RFI are preliminary and may not represent all requirements eventually determined for this system. They are included in this RFI for informational purposes only to provide additional context and promote subsequent questions and clarifications.

C. Respondents are solely responsible for all expenses associated with responding to this

RFI.

D. Respondents are advised that all documents submitted in response to this RFI will not be returned and become the property of the State of California and will be regarded as public records under the California Public Records Act (CPRA) pursuant to Government Code Section 6250 et seq. and subject to review by the public.

E. Respondents are instructed not to include any proprietary information in their response to this RFI as it may be disclosed or be subject to a CPRA request.

F. The CHP reserves the right to modify or cancel this RFI in its entirety or in part at any time.

G. All data collected during this project is owned by the CHP and must be deleted once the demos and pilot/field trials have concluded.

H. Information provided in response to this RFI will not be considered when evaluating bidders responding to any future procurement.

I. Responding to this RFI creates no obligation on the part of any Respondent to the CHP.

Conversely, issuing this RFI and considering the responses creates no obligation on the part of the CHP to any Respondent.

J. The CHP will consider vendor responses in developing a bid such as, but not limited to, a Request for Quotation (RFQ), Invitation for Bid (IFB), Request for Proposal (RFP), or other action.

K. Submitting a response to this RFI will not enhance the review of that Respondent’s proposal(s) to any future solicitations. Failure to submit a response to this RFI will not

Artificial Intelligence Solutions for Public Safety Communications RFI Page 5 prohibit a response to any future solicitation, nor disadvantage the evaluation of a response to any future solicitation. By submitting a response to this RFI a Respondent is implicitly agreeing with these conditions.

L. If this RFI results in a future procurement, bidders must agree to the State’s requirements, terms, and conditions.

3 Key Action Dates Listed below are the RFI Key Action Dates and times (all times noted are Pacific Time) by which actions should be taken or completed. If the CHP finds it necessary to change any of these dates, an Addendum to this RFI will be posted on the California State Contracts Register (CSCR) Webpage: https://caleprocure.ca.gov under the event number of this RFI. Interested parties are urged to check periodically to determine whether an Addendum has been issued.

Event Date / Time

Release RFI June 1, 2026

Intent to Respond (optional) Due June 10, 2026

Last Day to Submit Questions Due June 14, 2026, by 12:00 p.m. PT

Release of Answers and/or Addenda June 22, 2026

RFI Response* Due June 30, 2026, by 5:00 p.m. PT **State Invitations sent to Selected Vendors for Demonstration Day July 9, 2026

**Vendor Demonstration Day presentations July 20 – 31, 2026

**State Invitations sent to Selected Vendors for Pilot Testing August 6, 2026

**Pilot Testing of Selected Vendors (schedule based on 3 selected products, 90 days each pilot)

Pilot #1: September 1, 2026 – November 30, 2026

Pilot #2: January 18, 2027 – April 18, 2027

Pilot #3: May 17, 2027 – August 15, 2027

*Please note that the completeness and relevance of your RFI response to Attachment B will determine selection of vendors who will be invited to the Demonstration Day presentations as shown in the Key Actions Dates.

**These dates may shift based on the number of submissions and other outside factors.

4 Contact Information Vendors must submit their written response via e-mail to the State contact listed below:

Contact: Communications Infrastructure & Support Section (CISS) Agency: California Highway Patrol https://caleprocure.ca.gov/

Artificial Intelligence Solutions for Public Safety Communications RFI Page 6

E-mail: CCSS@chp.ca.gov Respondents are directed to submit questions or clarification inquiries in writing in accordance with the instructions detailed in RFI Section 5, Submission of Questions. No other representative of CHP is authorized to communicate with respondents with respect to this

RFI.

5 Submission of Questions Vendors must submit questions about this RFI, via e-mail, by the specified date and time stated in the Key Action Dates to the e-mail contact stated in Section 4, Contact Information.

What to include in the Inquiry:

1. Include in the subject line of the e-mail: RFI_CISS-25-001 Question(s)

2. Vendor name and contact, telephone number, e-mail address.

3. A description of the subject or issue in question, or discrepancy found in the RFI.

4. The RFI section, page number, and/or other information useful in identifying the specific problem or issue stated in the question.

At its discretion, the State may contact Respondents to seek clarification of any inquiry received. The State may respond to questions directly to the Respondent or if deemed necessary, release an addendum or updated RFI.

Questions will be compiled without identifying the party submitting the question(s), and answers will be e-mailed to all companies who receive this RFI. Questions not submitted via e-mail by the Key Action Date specified above shall be answered at CHP’s discretion.

Responses to questions submitted timely will be provided to all Vendors.

6 Vendors Declining to Respond The CHP is interested in learning the reason(s) a vendor chooses not to respond to this RFI.

If applicable, please submit an e-mail to CCSS@chp.ca.gov by the Response Due Date and include in the subject line of the e-mail: Declining to Respond to RFI_CISS-25-001 in addition to the following in the e-mail body:

• RESPONDENT’s BUSINESS NAME has declined to respond to RFI_CISS-25-001 for the following reason(s):

o Reason A o Reason B, etc.

• Name of person sending declination:

o Title and First/Last Name:

o Legal Business Name:

o Address:

o Phone:

7 RFI Response Instructions Responses to this RFI must be submitted to the e-mail address listed in Section 4. Acceptable formats include Microsoft Word and/or an Adobe Acrobat (must be a searchable pdf). Please include the following in the e-mail submission:

• Subject line: RFI_CISS-25-001

Artificial Intelligence Solutions for Public Safety Communications RFI Page 7

• Contact Information: Name, Title, Address, Phone Number, and E-mail Address of the primary contact person for the RFI.

Vendors should respond to all applicable information using the following Attachments:

• Attachment A: Vendor Profile

• Attachment B: Questionnaire

• Attachment C: Rough Order of Magnitude Cost Estimate

• Attachment D: SIMM 5305-F, Generative Artificial Intelligence Risk Assessment

Responses must be submitted by the date and time stated in the Key Action Dates.

Vendors must submit a signed cover letter with their response to the RFI that also includes a statement by the individual certifying the information in the response is true and accurate to the best of their knowledge at the time of submittal.

RFI responses may not exceed fifty (50) pages in length. Submissions that exceed this length may not be reviewed in its entirety. Responses must be thorough and concise.

7.1 Cost Information

As previously stated, the CHP is requesting ROM cost estimate information from all RFI respondents. The CHP understands that the cost estimates provided are non-binding and will be used for informational and project budgeting purposes only. Vendors are encouraged to provide a general cost value (or range of costs) for each product or solution identified in the RFI Response.

Instructions for completing cost information can be found in Attachment C, Rough Order of Magnitude Cost Estimate.

8 Product/Solution Demonstration Respondents will be notified by e-mail, according to the key action dates, if invited to participate in vendor demonstrations and pilots based on the completeness and relevance of the RFI response. The schedule will be selected on a first-come basis. The CHP reserves the right to extend the demonstration schedule should the quality and quantity of the responses warrant additional demonstrations.

8.1 Vendor Demonstration Days

The Demonstration Days vendor presentations will be conducted in-person or via Microsoft Teams and will be up to 8 hours in duration.

Anticipated Agenda:

• 1.5 Hours: Arrival and Set Up/Introductions/Executive Summary Broad introductions from both the Respondent and CHP teams. Product introduction at an Executive Summary level to provide the CHP team with a brief overview of the product.

• 4 Hours: Product Demonstration and Alignment/Technical Discussion Respondents will highlight how the presented software product meets the CHP’s high-level requirements, discuss future enhancements, and explain how the solution specifically addresses CHP’s needs. Please include information about implementation support and training options.

Artificial Intelligence Solutions for Public Safety Communications RFI Page 8

• 1 Hour: CHP Questions & Answers Dedicated time to CHP team members to ask questions.

• 15 Minutes: Pricing Structure and Estimated Costs Respondents will discuss the pricing structure and provide estimated costs for all licenses, support/maintenance, and recommended services over a three-year period.

• 45 Minutes: Closing Discussion/Breakdown and Departure Discussion regarding next steps and time for Respondent and/or CHP team final questions and comments.

The CHP expects each demonstration to clearly illustrate how the chosen software product can best meet the current and expanding needs related to the project, including its operational service requirements. The presentation should focus specifically on how the solution directly addresses these needs.

9 Pilot of Selected Products Based on the results of the Demonstration Day, the CHP anticipates inviting up to three Respondents to participate in a pilot test in a live environment. Each pilot will be held for 90 calendar days and assigned to a CHP selected communications center. Pilots will be 13 weeks (approximately 90 days) each and will not be held concurrently.

9.1 Pilot Requirements

A. The pilot will be provided by the selected Respondents at no-cost to the State.

B. The pilot will be provided for a minimum of 13 weeks.

C. The live environment will require the software be connected to or interface with CHP systems, to include but not limited to, the computer aided dispatch, 9-1-1 call handling, and radio console system and the CHP network.

D. All data collected by the software product during the pilot must be deleted after a data transfer from the Respondent to the State has been completed.

10 Terms and Conditions The following terms and conditions, or their successor, will be incorporated into any solicitation resulting from this RFI. The State will not modify these terms and conditions.

• Information Technology – General Provisions – Non-Cloud Goods & Services (DGS PD 403-ITGP Non-Cloud), revised and effective 2/20/25.

• Information Technology – General Provisions – Cloud Computing Services (DGS PD 402-ITGP Cloud), revised and effective 2/20/25.

In the event of any inconsistency between articles, attachments, specifications, or provisions which constitute the contract, the state’s General Provisions order of precedence shall apply.

11 Generative Artificial Intelligence The State of California seeks to realize the potential benefits of GenAI, through the development and deployment of GenAI, while balancing the risks of these technologies.

https://www.dgs.ca.gov/-/media/Divisions/PD/Acquisitions/Solicitation-Document-Attachments/IT-General-Provisions-NonCloud-DGS-PD-403ITGP-Revised-02202025.pdf https://www.dgs.ca.gov/-/media/Divisions/PD/Acquisitions/Solicitation-Document-Attachments/IT-General-Provisions-NonCloud-DGS-PD-403ITGP-Revised-02202025.pdf https://www.dgs.ca.gov/-/media/Divisions/PD/Acquisitions/Solicitation-Document-Attachments/IT-General-Provisions-Cloud-DGS-PD-402ITGP-Revised-02202025.pdf https://www.dgs.ca.gov/-/media/Divisions/PD/Acquisitions/Solicitation-Document-Attachments/IT-General-Provisions-Cloud-DGS-PD-402ITGP-Revised-02202025.pdf

Artificial Intelligence Solutions for Public Safety Communications RFI Page 9

Bidder/Offeror must notify the State in writing if it: (1) intends to provide GenAI as a deliverable to the State; or (2), intends to utilize GenAI, including GenAI from third parties, to complete all or a portion of any deliverable that materially impacts: (i) functionality of a State system, (ii) risk to the State, or (iii) Contract performance. For avoidance of doubt, the term "materially impacts" shall have the meaning set forth in State Administrative Manual (SAM) 4986.2.

Failure to report GenAI to the State may result in disqualification. The State reserves its right to seek any and all relief it may be entitled to as a result of such non-disclosure.

Upon notification by a Bidder/Offeror of GenAI as required, the state reserves the right to incorporate GenAI Special Provisions into the final contract or reject bids/offers that present an unacceptable level of risk to the state.

Government Code 11549.64 defines “Generative Artificial Intelligence (GenAI)” as an artificial intelligence system that can generate derived synthetic content, including text, images, video, and audio that emulates the structure and characteristics of the system’s training data.

12 Project Description and Requirements

12.1 Background

The CHP is a statewide law enforcement agency that employs nearly 11,000 personnel (approximately 7,600 uniformed and 3,300 non-uniformed). The mission of the CHP is to provide the highest level of Safety, Service, and Security to the people of California every day.

The Department’s primary jurisdiction is State of California buildings, unincorporated roadways, and all freeway systems in California; however, the CHP takes appropriate enforcement action statewide.

The CHP provides security protection for the Governor, state constitutional officers, State Supreme Court Justices, Appellate Courts, and various dignitaries. The CHP is also often given specialized initiatives directed by the Governor such as organized retail crime task forces, law enforcement surge operations, and special response teams.

The CHP operates a large and complex statewide emergency communications system consisting of 24 communications centers that serve as a primary PSAPs. These centers handle legacy 9-1-1, Next Generation 9-1-1 (NG9-1-1), administrative calls, and a toll-free information line, as well as dispatch calls for service for uniformed officers. In calendar year 2025, CHP received approximately 2.9 million 9-1-1 calls, and 893,000 administrative and toll-free calls, placing substantial demand on dispatch personnel.

The CHP currently utilizes the Central Square Computer Aided Dispatch (CAD) system, Motorola Vesta 9-1-1 call handling system, Rapid Deploy Text-to-9-1-1, and InterTalk radio consoles to support dispatch operations. Like many large public safety organizations, CHP faces ongoing challenges related to staffing constraints, increasing service demands, manual data entry requirements, and the need to maintain consistent service delivery across geographically distributed communications centers. Additionally, language access needs and data fragmentation across multiple PSAPs represent operational considerations that CHP seeks to better address through AI-enabled technology solutions.

12.2 Operational Objectives

Through this RFI, the CHP seeks to better understand the capabilities of AI-enabled technologies that can assist and support dispatch personnel. The primary objective is to

Artificial Intelligence Solutions for Public Safety Communications RFI Page 10 identify solutions that can enhance operational efficiency, reduce manual workload, and improve service accessibility without compromising public safety.

The CHP is particularly interested in both Agentic and Generative AI solutions that can support or automate the intake and handling of non-emergency calls, contact rotational tows when requested, enter information regarding persons, vehicles, or property into California Law Enforcement Telecommunications System databases, provide real-time transcription and summarization of calls and radio traffic, and offer multilingual communication capabilities, such as translation of emergency calls. Additionally, CHP seeks solutions that can intelligently route or escalate calls to live dispatchers when necessary, ensuring that any potential emergency situations are promptly identified and handled by trained personnel.

Any proposed solution must be designed to augment and support dispatch staff rather than replace them, maintaining the critical human role in public safety communications while leveraging technology to improve efficiency and consistency.

The technology must function in a manner that improves public safety communications operations while maintaining transparency, accountability, privacy protections, and appropriate human oversight and intervention. Consistent with the State’s evolving policies regarding responsible AI adoption, CHP intends to identify solutions that enhance service delivery, improves operational efficiency, and supports dispatch personnel without compromising civil liberties or public trust.

The AI solution must demonstrate responsible governance practices, including safeguards against misuse, mechanisms to mitigate bias and inaccuracy, transparency in automated processes, and the ability to maintain meaningful human involvement in operational decision-making. Vendors should describe how their solutions support ethical and responsible deployment of AI technologies within a public safety environment, including protections against inappropriate surveillance, unauthorized data use, or unintended operational impacts.

Additionally, CHP seeks solutions that align with modern public sector technology principles by supporting secure integration, auditability, data protection, and operational resiliency across a statewide emergency communications environment. The CHP’s objective is to ensure that any future AI-enabled capability functions as a trusted assistive tool that strengthens public safety operations while safeguarding the rights, privacy, and confidence of the people of California.

12.3 Additional Considerations

Current staffing allotment levels in CHP’s 24 communications centers is about 922 full-time dispatchers. In addition to dispatchers, the CHP is allotted 147 dispatch supervisors across the communications centers.

Although this solution will be used primarily by dispatch staff, CHP recognizes that ancillary staff may also require access to the AI solution as part of their operational responsibilities.

The CHP estimates that approximately 200 additional users, including supervisory, training, technical, quality assurance, records, and administrative personnel, may require role-based access to the system. Vendors should describe how their solution supports up to 1,500 total users, role-based access and user-specific functionality across multiple operational and administrative roles.

Vendors should also provide information regarding available training approaches, including initial implementation training, ongoing user education, role-specific instruction, train-the-

Artificial Intelligence Solutions for Public Safety Communications RFI Page 11 trainer models, and resources designed to support adoption. Users will have varying technical backgrounds and operational responsibilities statewide.

All proposed solutions and services must be Criminal Justice Information Systems (CJIS) compliant, and vendors will be asked to attest as to how they meet such compliance. All data being exchanged with cloud environments must be encrypted both in transit and at rest to ensure Personally Identifiable Information is not reaching unauthorized parties.

Administrative users of the solution must have access to auditing or other types of accountability controls that record all access to CJIS data that traverses the platform. This must include the identity of the user accessing the information, the time of access, and the data accessed. To maintain compliance and hold staff accountable, the CHP will regularly review this information to identify any suspicious activity and keep the public’s data safe.

Artificial Intelligence Solutions for Public Safety Communications RFI Page 12

ATTACHMENT A – VENDOR PROFILE

[Included as a separate file - see attached document]

ATTACHMENT B – QUESTIONNAIRE

[Included as a separate file - see attached document]

ATTACHMENT C – ROUGH ORDER OF MAGNITUDE COST ESTIMATE

[Included as a separate file - see attached document]

ATTACHMENT D – SIMM 5305-F, GENERATIVE ARTIFICIAL

INTELLIGENCE RISK ASSESSMENT

[Included as a separate file - see attached document]

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment A Page 1

Artificial Intelligence Solutions for Public Safety Communications

ATTACHMENT A – VENDOR PROFILE

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment A Page 2

Attachment A - Vendor Profile

Company/Firm Legal Name:

1. List all alternative business names used by this vendor, including but not limited to fictitious business names. If not applicable, write “N/A”.

2. Business address (Street, City, State, Zip) for number 1 above.

3. Name and title/position of the individual submitting the response for number 1 above.

4. Is number 3 an owner or employee of number 1? Check one:

☐ YES If you checked “Yes”, continue to number 6 below.

☐ NO If you checked “No”, stop. Do not continue and do not submit a response for the entity in number 1 above.

5. Contact information including a telephone number(s) and e-mail address for number 4 above.

6. In bullet format, very briefly describe company’s products and/or services focus.

A. Products B. Services

7. In bullet format, list and briefly describe the projects and/or activities the company was/is engaged in within the last ten (10) years that are like the project description and CHP size identified in the RFI Section, Project Description and Requirements.

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment B Page 1

ATTACHMENT B – QUESTIONNAIRE

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment B Page 2

Attachment B - Questionnaire

Respondents shall provide detailed information on the following sections. Each section and sub-section must have a separate response, and responders are encouraged to provide a level of thoroughness that will enable the CHP to achieve the RFI objectives. Provide concise and complete responses to all items, and clearly articulate those that may not be applicable.

I. Solution Overview

a. Type of AI used (e.g., Generative, Assistive, Agentic, machine learning).

b. Description of AI capabilities (e.g., conversational AI, voice automation, NLP).

c. System architecture (cloud, hybrid, or on-premises).

d. Maturity of the solution and current deployments (particularly in public safety).

e. Ability to function as an overlay to existing systems without requiring full replacement of existing systems or infrastructure.

II. Non-Emergency Call Handling and Triage

a. Ability to answer and manage administrative calls.

b. Conversational AI capabilities (natural language interaction).

c. Ability to:

i. Resolve routing inquiries.

ii. Provide automated responses (e.g., directing to online services).

d. Multilingual support, including real-time translation.

i. Type of AI used for translation.

e. Critical Requirements:

i. Detection of potential emergency indicators (e.g., distress, injury, threats).

ii. Immediate escalation (“warm transfer”) to a live dispatcher.

II. Assistive Call Taking Capabilities

a. Real-time call transcription.

b. Automated incident summarization.

c. Location validation and mapping support.

d. Reduction of manual data entry.

III. Integration Capabilities

a. CAD systems.

b. Call handling solutions.

c. Radio consoles.

d. NG9-1-1 environments.

e. Logging/recording systems.

f. Real-Time Crime Centers.

g. Data sharing platforms.

IV. Reliability and Continuity of Operations

a. Performance during:

i. High call volume events.

ii. Network disruptions.

b. Failover and redundancy capabilities.

c. Offline or degraded-mode operation.

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment B Page 3

V. Customer Service/Support/Maintenance

a. Please discuss your organizations model for providing customer support including multi-tiered maintenance charges for contacting Customer Support.

b. Describe your incident/problem reporting and tracking systems, including the ability for authorized customer staff to access those systems directly.

c. What level of automatic alerting can you provide to CHP’s staff in the event of software or hardware failure, degraded service, or exceeded planned utilization?

d. What is your standard maintenance agreement for providing customer support both on weekdays and after hours (nights, weekends, and holidays)?

e. What is your standard maintenance agreement for providing administrator and end user training to customers?

f. Describe your standard process for providing software and hot fix upgrades to customers.

g. Describe your standard process to resolve critical system outages.

h. Describe your extended maintenance model for support and warranty coverage.

VI. Cost and Timeframe

a. The CHP needs to understand approximately how much your solution would cost given the size of the current CHP system (described in the RFI), the complexities of multi-facility rollout, and the thousands of users that need to be trained. Please estimate the cost of hardware, software, services, and maintenance separately and include the prospective cost to design or put in place a system. This includes:

i. Anticipated costs for a complete solution and implementation.

ii. Anticipated costs for ongoing maintenance and operations of the system.

iii. Include any key assumptions used to craft the potential costs.

iv. Expected timeframe needed to deploy the outlined system to not exceed the designated costs as defined in the ROM.

VII. Approach and Work Plan

a. Describe your project implementation approach for providing the installation and configuration of the hardware and software, all necessary testing, administrator training, and supporting of all Go-Live events at all locations.

b. What are the types of issues experienced by your organization in past large-scale implementations and how were they overcome?

c. Describe the CHP’s responsibilities, requirements, and supporting efforts needed for meeting your effort and delivery of services.

d. Describe in detail your company’s Disaster Recovery plan, including requirements for as close to zero-downtime as possible.

VIII. Event and Administrative Reports

a. Describe how your solution produces standard reports of individual hardware and network issues, collection of calls, summary of activity logs, and other pertinent information gathered by the system. Additionally, please provide examples of event and administrative reports.

IX. Compliance and Security

a. Does the proposed solution support integration with the CHP Active Directory?

b. Does your solution allow for Two-Factor/Multi-Factor Authentication for login?

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment B Page 4

c. Describe your security procedures and policies for deploying and updating virus prevention, patch management, antivirus, worm, spyware, malware, other malicious software, and any additional PSAP or system threats.

d. Is your system compliant with current State of California CJIS requirements?

e. Is your system compliant with current NENA i3 standards?

f. Data encryption and storage practices.

g. Data retention and audit capabilities.

h. Describe your organization’s framework for responsible AI use.

i. What safeguards are in place to prevent misuse of your technology, including unlawful surveillance or inappropriate data use?

j. How does your solution mitigate bias and ensure equitable outcomes?

k. Describe how AI-driven decisions can be audited, reviewed, or explained.

l. What human oversight mechanisms are included in your system?

m. Do you maintain any certifications, policies, or third-party validations or civil liberties protections?

X. Data Ownership and Access

a. Describe the types of data generated, collected, processed, or stored by your solution, including but not limited to audio recordings, transcripts, metadata, analytics, summaries, logs, and AI-generated outputs.

b. Confirm whether CHP retains full ownership rights to all data generated, collected, processed, or stored through use of the proposed solution.

c. Describe the mechanisms available for CHP to access and retrieve raw data generated by the system. Include available export formats, delivery methods, frequency of availability, and any associated limitations or costs.

d. Describe whether data can be exported in non-proprietary or industry standard formats to support long-term retention, migration, reporting, or integration with other systems.

XI. Data Privacy & Use Restrictions

a. Confirm whether any CHP data, including audio, transcripts, metadata, analytics, or AI-generated outputs, is used for any purpose outside of CHP operations, including but not limited to:

i. AI model training.

ii. Product development.

iii. Analytics aggregation.

iv. Marketing.

v. Sale or sharing with third parties.

b. If any CHP data is used for product improvement, machine learning, analytics, or model training purposes, describe:

i. What data elements are used.

ii. Whether the data is anonymized or de-identified.

iii. Opt-out capabilities available to CHP.

iv. Governance and approval controls associated with such use.

c. Describe the safeguards implemented to ensure CHP data remains private, secure, and isolated from other customers, tenants, or external entities.

d. Describe your organization’s policies regarding data confidentiality, access controls, subcontractor success, and third-party data sharing.

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment B Page 5

XII. Data Retention & Contract Termination

a. Describe the vendor’s data retention policies, including configurable retention periods and deletion procedures.

b. Upon contract termination or expiration, describe:

i. How CHP data will be returned.

ii. Available export formats and methods.

iii. Timeframes for data retrieval.

iv. Procedures for permanent deletion of CHP data from vendor systems, backups, and subcontractor environments.

c. Confirm whether CHP data will be permanently deleted following contract termination and describe how deletion is verified or certified.

d. Describe any circumstances under which vendor systems may retain CHP data after contract termination, including retention required for legal, regulatory, backup, or disaster recovery purposes.

XIII. General Questions

a. How does your solution ensure no emergency call is misclassified or delayed?

b. What mechanisms are in place for human oversight?

c. What is your accuracy rate for call classification and transcription?

d. How does your system handle language translation in real time?

e. Can your solution operate as an overlay to existing telephony systems?

f. What public safety agencies are currently using your solution and how?

g. How does your platform support statewide data aggregation across multiple

PSAPs?

h. How are audio logs and decision transparency maintained?

i. What are the risks and limitations of your solution?

XIV. Solution Procurement Approach and Vehicle

a. Are there any requirements that would preclude you from competing should an RFP be released? If yes, what suggested changes would allow you to compete?

b. Are the goods, products, or services you have identified in your RFI response available on a Federal General Services Administration (GSA) or State of CA Leveraged Procurement Agreement (LPA)? If yes, please identify the contract type, name, and number.

c. What is the model/approach for the license fees for the Vendor Software?

XV. Vendor Assumptions

a. What assumptions were made in preparing a response to this RFI?

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment C Page 1

ATTACHMENT C – ROUGH ORDER OF MAGNITUDE COST ESTIMATE

Artificial Intelligence Solutions for Public Safety Communications RFI – Attachment C Page 2

Attachment C - Rough Order of Magnitude Cost Estimate

Level of Effort/Rough Order of Magnitude (LOE/ROM) Check the appropriate LOE/ROM designation

(all are expressed in terms of person-hours for the combined roles detailed below):

Small 0 – 4,999

Medium 5000 – 9,999

Large 10,000 – 19,999

Jumbo 20,000 – 30,000

Vendor Defined Please enter LOE/ROM

Implementation and Initial Configuration Labor/Services/Fees Insert additional lines as needed. Information below is suggested information only.

List the major roles/tasks needed to implement the solution.

Estimated range of cost for total implementation services, based upon the metrics below.

Project Costs:

Please add task lines for all estimated costs and include the number of hours needed per task and by role. The tasks and roles provided below do not necessarily represent all tasks and roles that may be required to perform the necessary work; please add, remove, and elaborate with tasks as needed.

Estimated costs for each listed task

Estimated Service Hours

(if applicable)

1. System Software

2. System Hardware

3. Services (Implementation)

4. Ongoing Yearly Maintenance or Subscription Fee

5. Other: Please Describe

Answers and Assumptions used in Cost Estimate

Please answer, in as much detail as possible, the questions below.

Provide details pertaining to the assumptions, expectations, and/or performance parameters used as the basis of the cost estimate.

1. What is the estimated timeframe that the solution will take to initially build, configure, and implement?

2. Are there external system requirements the CHP needs to consider for successful integration of this solution?

3. For your company, would this proposal necessitate an annual maintenance agreement, or would it be subscription based? If neither, define ongoing pricing model.

4. Are there any assumed/unidentified dependencies for this implementation?

State of California Department of Technology

Office of Information Security

Generative Artificial Intelligence Risk Assessment

SIMM 5305-F

August 2025

REVISION HISTORY

Revision Date of Release Owner Summary of Changes Initial Release January 2024 California Office of

Information Security

- Payam Hojjat

Initial Release of SIMM 5305-F Generative Artificial Intelligence Risk Assessment

Minor Update July 2024 California Office of Information Security

- Payam Hojjat

Added clarifying questions for GenAI regarding:

• Review and consultation.

• State entity policies.

• User training.

Major Update February 2025 California Office of Information Security

- Kory Fesliyan

• Updated Format

• Restructured and revised questions

• Added a new section to document safeguards

• Added a new section for data types

• Updated risk assessment table

Minor Update August 2025 California Office of Information Security

- Kory Fesliyan

• Added Labor Relations Engagement

Office of Information Security Generative Artificial Intelligence Risk Assessment August 2025 SIMM 5305-F (Confidential and Exempt - Government Code Section 7929.210(a)) Page 2 of 28

Table of Contents

I. Introduction

II. Risk Assessment - Part 1 Data Types

III. GenAI Risk Table Assessment Scale Risk Assessment Questionnaire Signatures and Acknowledge (Required Completion)

IV. Risk Assessment - Part 2 Signatures and Acknowledge (Required Completion)

V. GenAI Use Cases & Safeguard Samples Safeguards (Common) Safeguards (Use-Case Specific)

VI. Definitions

VII. References

VIII. Questions

Office of Information Security

SIMM 5305-F (Confidential and Exempt - Government Code Section 7929.210(a)) Page 3 of 28

I. Introduction

Generative Artificial Intelligence (GenAI) has the potential to improve the delivery of government services and operations. GenAI enables enhancements to the development, adoption, and implementation of new technologies to streamline and optimize business operations and state services to Californians. With that, it is critical for entities to be cognizant to ensure that GenAI does not lead to a state in which human life, health, property, or the environment is endangered, nor have public services be solely contingent upon these systems. GenAI systems are to be used only to augment and improve workflows, not to replace or impair the services received by the public.

As described in the State of California Report: Benefits and Risks of GenAI report, GenAI offers a wide variety of potential applications with varying impacts. Any application of GenAI tools within the California state government will adhere to appropriate protocols and testing procedures. To proactively address potential threats to state-owned information assets, privacy, and the welfare of California's citizens, the Statewide Information Management Manual (SIMM) 5305-F, GenAI Risk Assessment introduces a risk assessment methodology that will aid state entities in evaluating the risks associated with GenAI systems.

This SIMM is to ensure alignment with:

• Executive Order (EO) N-12-23

• NIST Artificial Intelligence Risk Management Framework

Please note that a completed SIMM 5310-C Privacy Threshold Assessment and Privacy Impact Assessment must be accessible upon request.

Office of Information Security Generative Artificial Intelligence Risk Assessment August 2025 SIMM 5305-F (Confidential and Exempt - Government Code Section 7929.210(a)) Page 4 of 28 https://www.govops.ca.gov/wp-content/uploads/sites/11/2023/11/GenAI-EO-1-Report_FINAL.pdf https://www.gov.ca.gov/wp-content/uploads/2023/09/AI-EO-No.12-_-GGN-Signed.pdf https://www.nist.gov/itl/ai-risk-management-framework

II. Risk Assessment - Part 1

Generative Artificial Intelligence Risk Assessment Part 1:

This section completed by the Chief Information Officer (CIO) Instructions:

• This risk assessment is required for all GenAI procurements, acquisitions, renewals and internally developed systems.

• This risk assessment applies to free GenAI products and services, defined as any free software or service that interacts with state data. Examples include users entering state data into conversational GenAI platforms or installing GenAI plugins and extensions. However, this assessment does not apply in cases where state data is not being used, such as browsing the web with search engine GenAI results or using conversational GenAI systems where no state data is entered.

• This risk assessment is required for existing GenAI tools that were acquired prior to the release of this document. These assessments must be retained and accessible by the entity as it may be requested during an information security program audit or assessment.

• State entities complete SIMM 5305-F, Risk Assessment Part 1 to determine the level of risk associated with a GenAI system.

• After completion, submit a Case via the New Technology Consultation and Assessment request, in the CDT IT Service Portal for all risk levels. When the request has been processed, a CDT Customer Engagement Services (CES) representative will reach out to provide a secure location to upload the required documents.

• CDT reserves the right to audit and consult on "Low" GenAI Risk Levels with potential higher risk concerns.

• Only complete SIMM 5305-F, Risk Assessment Part 2 if the GenAI system risk level is rated Moderate or High.

• Important: Once completed, this form is confidential and may be exempt from disclosure pursuant to

Government Code sections 7929.210 and 8592.45.

Office of Information Security

SIMM 5305-F (Confidential and Exempt - Government Code Section 7929.210(a)) Page 5 of 28

Data Types Select all that apply to identify the data types at risk. Take into account the potential impact to data types in this risk assessment questionnaire (note: data types may overlap across categories).

☐ Personal Information (Privacy) or PII - Information ☐ Confidential - Information maintained by state agencies that is that can be used to distinguish or trace an individual’s exempt from disclosure under the provisions of the California Public identity, including those in accordance with Civil Code Records Act (Government Code Sections 7923.75-7923.55, 7929.210,

1798.3 & 1798.29. 7930.000-7930.005, 7930.100-7930.215) or has restrictions on disclosure in accordance with other applicable state or federal laws.

1. ☐ Individual’s first name or initial and last name

1. ☐ Intelligence information in support of Homeland Security and National Defense

2. ☐ Date of Birth

3. ☐ Social Security Number

2. ☐ Attorney/Client Privileged and/or Work Product 4. ☐ Physical description

3. ☐ Controlled Technical Information (CTI) (e.g., Network security5. ☐ Home address info, diagrams, security & transaction logs, encryption keys)6. ☐ Telephone number

4. ☐ Intellectual property, such as patents, copyright, trade secrets7. ☐ Education

5. ☐ Proprietary8. ☐ Financial matters, including financial/bank

6. ☐ Electronic Health Record (EHR) information subject to Healthaccount number, credit or debit card number, or any

Insurance Portability and Accountability Act (HIPAA) Privacy andcode that would permit access to an individual’s Security Rulesfinancial account

7. ☐ Protected Health Information (PHI) subject to HIPAA Privacy or9. ☐ Medical history and medical information Security Rules10. ☐ Health data – other identifiable medical data not

8. ☐ Medical information as defined by the California Confidentialitycovered by Health Insurance Portability and of Medical Information Act (CMIA)Accountability Act (HIPAA). (e.g., occupational health, services qualification, personal health record) 9. ☐ Family Educational Rights and Privacy Act (FERPA) data

10. ☐ Federal Tax Information (FTI) subject to Internal Revenue

Service (IRS) Publication 1075 requirements

11. ☐ Employment history

12. ☐ Statements made by & attributed to an individual

11. ☐ Controlled Unclassified Information (CUI)13. ☐ Driver’s license number

12. ☐ Criminal Justice Information Services (CJIS)…