FINAL__DEM_CHE_RFI_0000012230.docx

DOCX document 275 KB Posted

Attached to
DEM | IT 9-1-1 Call Handling System
Solicitation number
SFGOV-0000012230
Issued by
San Francisco County, San Francisco City, California

About this file

Request for Information (RFI) Summary

This is a Request for Information (RFI) document issued by the San Francisco Department of Emergency Management (DEM) soliciting information regarding Next Generation 9-1-1 (NG9-1-1) Call Handling System solutions. The RFI is restricted to vendors with approved contracts under the California Governor's Office of Emergency Services (Cal OES) 9-1-1 Systems and Services Contract Agreement, specifically those responsive to Invitation for Bid (IFB) 26-16743. DEM seeks detailed information on commercially available call handling solutions, deployment models, implementation approaches, operational capabilities, and lifecycle support services to inform a modernization evaluation of its legacy 9-1-1 infrastructure. The RFI was issued on November 6, 2026, with questions due by November 22, 2026, and responses to questions provided by December 4, 2026. The deadline for vendors to submit RFI responses is January 8, 2027. DEM may invite selected vendors to demonstrations scheduled for February 8-12, 2027, with invitations issued by January 15, 2027. The response should be submitted via email to DEM-PMO@sfgov.org in electronic format on a USB drive organized in separate files by section.

DEM currently operates the primary Public Safety Answering Point for San Francisco City and County, processing more than 1.3 million calls annually across 55 VIPER phone positions and 41 9-1-1 trunks, supplemented by 11 10-digit emergency lines and 31 10-digit non-emergency lines. The existing system uses an Intrado VIPER call handling platform with NICE logging recorder solution and integrates with CentralSquare Total Command CAD; DEM is planning migration to Motorola PremierOne CAD. DEM maintains a backup PSAP at One South Van Ness and is evaluating relocation of backup operations to 1455 Market Street by mid-2027 to support a minimum of 36 call-taking/dispatcher positions. Vendors must address pricing through the Cal OES Contract cost workbook, identify Cal OES contract numbers and authorized products, and clarify any components or services not included under the Cal OES vehicle. The RFI emphasizes security requirements including CJIS compliance, NG-SEC principles, NIST Cybersecurity Framework alignment, and comprehensive information regarding AI-enabled capabilities, governance, transparency, and responsible use in emergency and non-emergency call handling operations. References from at least two large metropolitan PSAPs where the vendor has implemented solutions within the last ten years are required.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Daniel Lurie Mayor

Department of Emergency Management 1011 Turk Street, San Francisco, CA 94102 Phone: (415) 558-3800 Fax: (415) 558-3843

Mary Ellen Carroll Executive Director

REQUEST FOR INFORMATION (RFI)

9-1-1 Call Handling System

RFI# 0000012230

CONTACT: DEM-PMO@sfgov.org

Contents

I.Background.3
II.RFI Schedule5
III.Current Environment5
IV.Current State of the Call Handling System6
A.Call Flow Description7
V.Purpose of RFI10
VI.RESPONSE REVIEW10
VII.PREPARING A RESPONSE11
VIII.RESPONSE SUBMISSION REQUIREMENTS20
Vendor Response Checklist21
IX.TERMS AND CONDITIONS OF THIS RFI21
X.SUBMITTING A RESPONSE TO THE RFI22

The Department of Emergency Management (DEM), by way of this Request for Information (the “RFI”), is requesting responses from qualified firms and parties who have a 9-1-1 Systems and Services Contract Agreement with California Office of Emergency Services (CaL OES) those Contractors who were responsive to the Invitation for Bid (IFB) 26-16743 technical and administrative to inform an industry review regarding a 9-1-1 Call Handling System.

I. Background.

The San Francisco Department of Emergency Management (DEM) serves as the primary Public Safety Answering Point (PSAP) for DEM and County of San Francisco. It is responsible for answering and processing emergency and non-emergency calls for police, fire, and medical services. The Department currently operates a legacy 9-1-1 call handling environment that supports one of the busiest emergency communications centers in the United States, processing more than 1.3 million calls annually, including wireline, wireless, Text-to-911, and administrative calls.

As part of its long-term strategic technology roadmap, DEM is evaluating options to replace its existing call handling platform with a modern, Next Generation 9-1-1 (NG9-1-1) compliant Call Handling System (CHS). The future solution must support evolving operational requirements, integration with California's NG9-1-1 program and Emergency Services IP Network (ESInet), enhanced resiliency and continuity of operations capabilities, cybersecurity best practices, and emerging technologies that improve emergency communications services to the public and first responders.

DEM is seeking information from qualified vendors regarding commercially available call handling solutions, deployment models, implementation approaches, operational capabilities, and lifecycle support services. Information gathered through this Request for Information (RFI) will assist DEM in evaluating available technologies, identifying industry best practices, understanding implementation and operational considerations, and refining future procurement requirements and evaluation the qualified CalOES contractors identified in the CalOES contract.

Questions and Communications To ensure fair and equal access to information about this RFI, all questions, requests for clarification, and requests for additional information must be submitted to: DEM RFI Team at email: DEM-PMO@sfgov.org

DEM is particularly interested in understanding how vendors support Next Generation 9-1-1 capabilities, including NENA i3-compliant call processing, Real-Time Text (RTT), Text-to-911, GIS-based call routing, cybersecurity, cloud and hybrid deployment architectures, continuity of operations, disaster recovery, and integration with existing and future public safety technologies.

II. RFI Schedule

RFI Issuance
November 6, 2026
Deadline for Questions
November 22, 2026
Deadline to respond Questions
December 4, 2026
Deadline to Submit Responses
January 8, 2027
Invitations for Demonstrations, if deemed appropriate
January 15, 2027
Demonstrations
February 8-12, 2027
Contract Administrator:
DEM PMO

Department of Emergency Management 1011 Turk Street, San Francisco, CA 94102 Email: DEM-PMO@sfgov.org

III. Current Environment

The Department of Emergency Management: (https://sfdem.org/) Mission The San Francisco Department of Emergency Management (DEM) leads the City and County of San Francisco in planning, preparedness, communication, response, and recovery for daily emergencies, large scale citywide events, and major disasters. DEM is the vital link in emergency communication between the public and first responders, and provides key coordination and leadership to City departments, stakeholders, residents, and visitors.

History . The headquarters building for DEM at 1011 Turk Street opened in 2000 to house a new, combined 9-1-1 call-taking and dispatch center for Police, Fire, and Emergency Medical Services, as well as DEM’s Emergency Operations Center.

The Division of Emergency Services (DES) Watch Center works with the PSAP Dispatch Center to issue emergency notifications to city agencies, partners, and the public through the Emergency Alert System (EAS).

DEM currently operates its primary communications center at 1011 Turk Street and maintains continuity of operations capabilities at a secondary facility located at One South Van Ness Avenue. DEM is evaluating future operational models that further enhance resiliency, continuity of operations, and operational flexibility

IV. Current State of the Call Handling System The San Francisco Department of Emergency Management (DEM) operates the primary Public Safety Answering Point (PSAP) for DEM and County of San Francisco and serves as the central hub for emergency communications, incident processing, dispatch coordination, and the deployment of public safety resources. DEM supports emergency communications operations for law enforcement, fire suppression, emergency medical services, and other public safety agencies serving residents, businesses, visitors, and critical infrastructure throughout DEM and County.

As one of the largest urban emergency communications centers in California, DEM processes a substantial volume of emergency and non-emergency communications annually. The operational environment supports a dense urban population, major tourist destinations, significant transportation infrastructure, high-rise occupancies, critical government facilities, healthcare institutions, higher education campuses, sporting and entertainment venues, and a large daily commuter population. The communications center must maintain continuous operations while supporting complex multi-agency response coordination and regional interoperability requirements.

The table below identifies the public safety agencies currently supported by DEM PSAP.

Table 1 – PSAP Supported Agencies PSAP Supported Agencies

Agency Type
Agency
Law Enforcement
San Francisco County Sheriff

San Francisco Police Department

Fire
San Francisco Fire Department
EMS
San Francisco Fire Department

King American

AMR

The volume and diversity of communications processed by DEM require a highly available, resilient, and scalable call handling environment capable of supporting both routine operations and major incidents. Historical call volume statistics are provided below:

Table 2 – PSAP Call Volume Statistics Call Volume Statistics

Call Type
2022
2023
2024
2025
Average
Total Wireline 9-1-1 Calls
99,340
97,070
90,499
71,453
89,590
Total Wireless 9-1-1 Calls
476,957
489,969
462,882
450,550
470,089
Total Non-Emergency (admin) & 10-digit Emergency
611,114
589,614
516,681
494,793
554,050
Text-to-911 Calls
5,979
5,867
8,766
11,234
7,961
Outgoing Calls
data not collected
data not collected
343,990
332,007
337,999
Totals
1,193,390
1,182,520
1,422,818
1,360,037
1,459,689

The call volume data demonstrates the significant operational demands placed on the communications center, including large wireless call volumes, increased use of Text-to-911 services, substantial non-emergency call activity, and a consistently high workload across all communications disciplines. These operational requirements drive the need for a call-handling environment capable of supporting current operations while providing a foundation for future Next Generation 9-1-1 (NG9-1-1) capabilities.

Table 3 – Phone Positions

Phone
Ops Floor
Back Up at 1 SVN
Viper
55
N/A
Avaya
55
26-36
Supervisor Phones (IP Admin Phones connected to the CHE)
4
N/A

A. Call Flow Description The analog 9-1-1 CAMA trunks are routed through the Millbrae Selective Router to the VIPER system at DEM. The CAMA trunks integrate into the current Viper system via a CIM (CAMA Interface Module) gateway and deliver both wireline and wireless 9-1-1 calls. The 9-1-1 calls are routed via an ESN (Emergency Services Number), which identifies which PSAP receives the call.

DEM is the primary PSAP in San Francisco City and County, with three secondary PSAPs in the county – United States Park Police (USPPD), University of California, San Francisco (UCSF), and San Francisco State University (SFSU).

Table 4 – Phone Counts

Phone Trunks
Count
911 Trunks
41
10-digit Emergency Lines
11
10-digit Non-Emergency Lines
31

All wireless 9-1-1 calls within the county limits are routed to DEM, except for the Golden Gate and Bay Bridges and some county freeways, which route to the California Highway Patrol (CHP). All landline and VoIP 9-1-1 calls are routed via ESN to the appropriate PSAP within the county.

The following is a high-level overview of the PSAP call flow:

· Call-takers answer all 9-1-1 voice and text calls and non-emergency police/fire calls for service. Call-takers interrogate callers using standardized case entry questions that include location, callback number, and a description of the incident. On calls involving fire/medical incidents, call-takers follow industry established protocols via ProQA software modules.

· Calls that require action or some form of response are entered into the Computer-Aided Dispatch (CAD) system.

· Based on the incident location, nature of the event, and required response discipline, the CAD system routes incidents to the appropriate dispatch position and recommends available response resources.

· Once an incident has been created, call-takers can continue to update and supplement incident information through the CAD system for use by dispatchers and responding field personnel.

· Dispatch personnel coordinate and manage field response activities through the CAD and radio communications systems.

· Transfers to other PSAPs occur for out-of-jurisdiction events. This includes incidents occurring on freeways and bridges, which are handled by CHP (California Highway Patrol).

The current call handling environment supports emergency voice calls, Text-to-911 communications, and non-emergency public safety calls. The existing call handling platform interfaces with DEM's CAD system, emergency medical and fire call processing protocols, public safety radio dispatch systems, logging recorder systems, and administrative telephone services.

DEM maintains a backup call processing capability utilizing an Avaya telephone system at 1011 Turk and One South Van Ness that supports continuity of operations during failures of the primary call handling platform.

In the event of a major system failure, 911 calls can be manually redirected to the Avaya environment through alternate-answer switching infrastructure located at the PSAP. The 10-digit Emergency and Non-emergency and administrative lines can also be rerouted to support continued operations. The rerouting of these lines are done through the ATT Resolution Center.

DEM's continuity of operations strategy includes the ability to relocate call-taking functions to DEM's secondary facility at One South Van Ness. While the backup environment provides essential call-answering capabilities, it does not currently provide ANI/ALI, CAD integration, or integrated call recording functionality.

DEM currently uses the Intrado VIPER call handling platform and the NICE logging recorder solution to support emergency communications operations. The current CAD platform is CentralSquare Total Command; however, DEM is actively planning a migration to the Motorola PremierOne CAD platform. Vendors should describe both current and future CAD integration capabilities and identify any considerations for supporting a transition from the existing CAD environment to PremierOne throughout the lifecycle of the proposed solution.

As California continues the deployment of statewide NG9-1-1 services and the Emergency Services IP Network (ESInet) infrastructure, DEM is evaluating technologies to support long-term modernization of its emergency communications environment. DEM seeks to better understand available solutions that support migrating from legacy call-delivery methods to standards-based IP communications while enhancing resiliency, interoperability, cybersecurity, operational flexibility, and continuity of operations.

DEM is particularly interested in understanding how vendors support NENA i3 standards, ESInet integration, GIS-based routing and location services, Real-Time Text (RTT), Text-to-911, supplemental data delivery, multimedia communications readiness, cybersecurity best practices, cloud and hybrid deployment models, and geographically diverse continuity of operations capabilities.

DEM is also interested in understanding how vendors support non-emergency call management through AI-powered agents, interactive voice response (IVR), automated call routing, and call tree functionality to improve customer service, provide self-service options, and reduce call-taker workload while preserving rapid access to emergency communications personnel when required.

In addition to traditional call handling functionality, DEM is evaluating future-state operational models that may incorporate primary on-premises operations, cloud-based resiliency capabilities, warm backup site operations, distributed call-taking capabilities, enhanced disaster recovery strategies, and improved operational continuity during technology failures, facility disruptions, or other emergency conditions.

V. Purpose of RFI This RFI is being issued by DEM to gather information regarding commercially available NG9-1-1 Call Handling System solutions. Responses are requested only from vendors that have been awarded and are authorized to provide Call Handling System solutions under the Cal OES Call Handling Equipment contract. DEM intends to utilize the Cal OES contract vehicle for future acquisition of a Call Handling System and is seeking information from those approved vendors regarding available technologies, implementation approaches, operational capabilities, and support services.

Through this RFI, DEM aims to gather information on the capabilities, costs, installation requirements, and maintenance needs of available systems on the market. Once the RFI responses are received, subject matter experts will review and determine next steps, including possible product solution demonstrations. DEM may also choose to meet with respondents to better understand the scope, budget, and timeline for implementing their proposed solutions.

Vendors should identify the applicable Cal OES contract, contract number, authorized products and services available under that contract, and any options, configurations, or professional services relevant to the proposed solution. Vendors should also identify any costs, services, or components not included within the Cal OES contract offering and explain the vendor’s procurement process, as applicable.

VI. RESPONSE REVIEW

The purpose of this RFI is to solicit information from market participants regarding available Call Handling System solutions, NG9-1-1 capabilities, deployment models, resiliency strategies, and associated implementation services. DEM intends to use the information received to evaluate available technologies, understand industry’s best practices, and support future procurement via the Cal OES Contract.

DEM may invite selected vendors to make oral presentations and demonstrate their experience and capabilities for the purpose of allowing DEM to review and better understand the range and quality of available solutions. In addition, DEM may invite vendors to a designated location in San Francisco to showcase their products or to host a virtual review session. All such invitations will be issued in writing on or before the date listed in the schedule listed above. Firms that are selected to make presentations will receive questions, a written description of the demonstration format, and meeting location details on or before that date.

DEM may utilize audio/visual and webinar technologies to record vendor demonstrations to reach the widest possible distribution to City staff. The goal of any vendor demonstrations is to better understand Call Handling System capabilities, NG9-1-1 functionality, operational workflows, resiliency features, and integration capabilities.

Providing references with other jurisdictions using the proposed products is highly encouraged. DEM may contact these references to better understand the system user/owner experience with the product.

This RFI is to be used solely for the purpose of this industry review and DEM assumes no responsibility for any other use of this document. DEM will independently review and evaluate any information submitted as part of this process. Participation in this industry review is strictly voluntary, and DEM will not reimburse participants for any costs in connection therewith. The submission of responses to this RFI does not guarantee the respondent of any future business with DEM.

VII. PREPARING A RESPONSE

Respondents must submit the requested information in the format specified below.

Required Format All respondents shall provide the written responses in the following format:

Section 1: Primary Response The objective of the Primary Response is to provide City staff with sufficient information to evaluate the vendor's Call Handling System capabilities, NG9-1-1 readiness, deployment options, resiliency features, operational workflows, and long-term support model. Responses to the following items are suggested to meet this objective.

A: Company Information:

· Provide company name, address, contact name, title, phone number, and email address.

· Provide a brief letter of introduction with a brief description of your business including company history, size, organizational structure/chart, skill sets, vision and mission.

· Provide firm’s principal place of business and location of “lead office”.

· Describe available local or regional support resources, including staffing locations, response model, and availability of on-site technical support personnel to support implementation, maintenance, and incident response.

· Describe firm’s customer service (and/or “customer success”) values and how those values are reflected in the firm’s capabilities.

B: Product Information:

Provide an overview of your firm's Call Handling System solution and describe how the proposed system would support the operational, technical, and resiliency objectives of the San Francisco Department of Emergency Management.

· System Architecture and Solution Design: Describe the overall architecture of the proposed solution, including major hardware, software, network, cloud, and hosted components. Include information regarding deployment options, system resiliency, redundancy, disaster recovery capabilities, continuity of operations support, and integration with NG9-1-1 and ESInet environments. Provide a high-level architecture diagram illustrating major system components and interfaces. Vendors shall describe supported deployment models, including on-premises, cloud-hosted, and hybrid architectures. Responses shall include a comparison of these models and a recommended deployment architecture for the San Francisco Department of Emergency Management (DEM), including considerations for resiliency, redundancy, and continuity of operations.

· Vendors shall describe system limitations and scalability related to users, agent profiles, roles, permissions, and administrative accounts. Responses should identify any limitations associated with user identifiers and describe how historical recordings, reports, audit logs, and operational records maintain user attribution throughout applicable retention periods.

· Vendors should identify any dependencies on third-party services, cloud providers, carrier services, or state-managed NG9-1-1 infrastructure required to support the proposed solution.

· Hardware and Software Components: Provide an overview of the hardware and software required to implement and operate the proposed solution. Include workstation requirements, server infrastructure, cloud-hosted components, software applications, licensing requirements, management tools, and any third-party services necessary to support the solution.

· Integration Capabilities: Describe the solution's ability to integrate with public safety technologies commonly utilized within a large metropolitan PSAP environment. This should include CAD systems, logging recorder platforms, administrative telephony systems, GIS services, Text-to-911, Real-Time Text (RTT), emergency dispatch protocols, radio communications systems, and NG9-1-1 services. Vendors should specifically address integration capabilities with CentralSquare Total Command, Motorola PremierOne CAD and NICE recording platforms.

· Vendors shall describe their approach to supporting transition between DEM’s current Computer-Aided Dispatch (CAD) system (CentralSquare Total Command) and future CAD system (Motorola PremierOne), including coexistence strategies, interface continuity, and cutover considerations.

· Vendors shall describe integration with the DEM NICE logging recorder platform, including how recording continuity will be maintained during implementation, cutover, failover, and ongoing operations.

· Operational and NG9-1-1 Capabilities: Describe the operational capabilities of the proposed solution, including support for emergency call processing, NG9-1-1 services, NENA i3 standards, ESInet connectivity, GIS-based location services, Text-to-911, RTT, multimedia readiness, reporting, supervisory functions, and remote or distributed operations.

· Vendors shall describe support for caller history management, phone-number-based hazard or caution indicators, and other caller safety information that can be presented to call takers during active emergency and non-emergency communications. Responses should identify how such information is created, maintained, displayed, audited, and retained.

· Vendors shall describe abandoned-call management capabilities, including callback workflows, status tracking, supervisory visibility, audit logging, and reporting. Responses should identify how the solution prevents duplicate processing of abandoned calls and how call status information is shared among authorized users.

· Resiliency and Future-State Operations: DEM is evaluating future-state operational models intended to enhance resiliency, continuity of operations, and operational flexibility. Describe how the proposed solution supports cloud, on-premises, and hybrid deployment models; geographically diverse operations; warm backup sites; failover capabilities; data replication; disaster recovery; and continuity of operations during technology failures, facility disruptions, or other emergency events. Additionally, describe your recommended future-state architecture for a large metropolitan PSAP such as San Francisco, including considerations for primary operations, backup operations, cloud resiliency, geographic redundancy, continuity of operations, and integration with California's NG9-1-1 environment.

Vendors shall describe how their solution supports the development and execution of a comprehensive Continuity of Operations (COOP) plan, including operational procedures, dependencies, and testing considerations necessary to maintain emergency communications during disruptions.

· Future Technology Roadmap: Describe how the proposed solution supports future NG9-1-1 capabilities and emerging technologies, including multimedia communications, supplemental data delivery, advanced location services, artificial intelligence-assisted workflows, cloud-native services, and other innovations that may enhance emergency communications operations over the next five to ten years.

· Artificial Intelligence (AI) Capabilities and Governance: As part of DEM's evaluation of next-generation Call Handling System technologies, DEM seeks information regarding available AI capabilities that may enhance emergency and non-emergency communications operations while maintaining appropriate human oversight, operational control, security, transparency, and compliance.

· AI-Assisted Emergency Call Handling: Vendors shall describe all AI-enabled emergency call processing capabilities available within the proposed solution. Responses should address, at a minimum:

· Real-time transcription of 9-1-1 voice calls and presentation of transcripts to call takers during active calls.

· Transcription accuracy rates, confidence scoring mechanisms, and processes for correcting or modifying AI-generated transcripts.

· Automatic extraction and presentation of key information, including caller location, callback number, incident type, weapons references, medical concerns, suspect descriptions, vehicle descriptions, and officer safety concerns.

· AI-assisted prompts, call guidance, and recommended questioning paths available to call takers.

· Automated generation of incident summaries for review, modification, and approval by call takers.

· Language identification, multilingual transcription, and real-time translation capabilities.

· Methods used to transfer AI-generated notes, summaries, and extracted information into CAD workflows and incident records.

· Human oversight controls ensure AI functions operate solely as decision-support tools and cannot autonomously dispatch resources or make operational decisions without user authorization.

· AI-Assisted Non-Emergency Call Management: Vendors shall describe all AI-assisted non-emergency call processing capabilities available within the proposed solution. Responses should address, at a minimum:

· AI-powered virtual agents capable of interacting with non-emergency callers.

· Intent recognition and classification capabilities.

· Collection of caller information for reports, complaints, service requests, and other non-emergency interactions.

· Escalation processes that automatically transfer callers to live personnel when emergency conditions or elevated risk factors are detected.

· Support for AI-assisted interactions utilizing voice, web applications, mobile applications, SMS/text messaging, and other digital channels.

· Reporting and analytics capabilities that measure call deflection, workload reduction, queue reduction, customer service improvements, and other operational performance metrics.

· Responsible AI Governance: Vendors shall describe their approach to responsible AI governance and provide information regarding all AI-enabled functionality included within the proposed solution. Responses should address, at a minimum:

· Inventory and description of AI-enabled functions.

· Known limitations, failure conditions, dependencies, and operational constraints associated with AI features.

· AI training methodologies, public safety-specific model development considerations, and measures implemented to minimize bias and improve accuracy.

· User controls that allow personnel to review, validate, edit, approve, reject, or override AI-generated outputs.

· Processes used to monitor AI performance, confidence levels, accuracy, and operational effectiveness.

· Model maintenance procedures including updates, retraining, version control, testing, change notification, and rollback capabilities.

· AI Data Governance and Security: Vendors shall describe how AI-generated and AI-processed information is secured, governed, and managed throughout its lifecycle. Responses should address, at a minimum:

· Data ownership.

· Data residency.

· Data retention.

· Data disposal.

· Access control mechanisms.

· Audit controls.

· Encryption methods used to protect AI-generated information.

· Security controls protecting AI processing environments, AI services, and associated data.

· Logging, monitoring, and auditing capabilities related to AI activity.

· AI Transparency, Auditability, and Compliance: Vendors shall describe how the proposed solution provides transparency into AI-generated recommendations, classifications, summaries, and outputs. Responses should address, at a minimum:

· User visibility into the source and confidence of AI-generated outputs.

· Audit logging of AI-generated content, user modifications, approvals, and system actions.

· Compliance with applicable privacy, cybersecurity, records retention, public safety, and regulatory requirements.

· Methods used to support informed operational decision-making by personnel utilizing AI-generated recommendations.

C: Implementation Approach:

Vendors shall describe their proposed system transition approach, including implementation methodology, cutover strategy, rollback procedures, and contingency planning necessary to maintain uninterrupted 9-1-1 operations during system migration.

D: Training:

Describe available implementation, project management, testing, training, and transition services. Identify any costs associated with initial deployment, administrator training, end-user training, and ongoing training opportunities.

Describe the firm’s training, not limited to but including specifics on the following:

· Installation

· System Admin

· End Users tailored to their roles

E: Maintenance and support:

Describe available maintenance, support, software assurance, and managed service offerings. Include service level commitments, software updates, security patching, technical support options, and any recurring annual costs associated with maintaining the proposed solution.

Describe the firm’s support and maintenance programs, not limited to but including specifics on the following:

· 24/7/365 Support: Highlight the commitment to providing round-the-clock support services.

· Technical Support: Outline the technical support services provided by the vendor, including the availability of help desk support, response times, and escalation procedures for resolving technical issues.

· Maintenance services included in the vendor's offering, such as software updates, patches, and hardware maintenance. Provide information on the frequency of updates and upgrades to ensure the system remains up-to-date with evolving technologies and security standards.

· Warranty and Lifecycle Support: Describe warranty coverage, equipment replacement options, software support periods, end-of-life policies, technology refresh programs, and other lifecycle support services available to DEM.

F: Security and Resiliency:

As DEM evaluates future-state NG9-1-1 and emergency communications technologies, DEM seeks solutions that provide robust cybersecurity protections, operational resiliency, and continuity of operations capabilities. Vendors shall describe the security architecture, redundancy features, disaster recovery capabilities, and operational safeguards incorporated into their proposed solution.

· Cybersecurity Measures: Describe the cybersecurity controls, policies, and technologies utilized to protect the system from cyber threats, unauthorized access, ransomware, data compromise, and service disruptions. Include information regarding authentication, access controls, encryption, monitoring, vulnerability management, and incident response capabilities.

· Artificial Intelligence Security Controls: If AI-enabled functionality is included within the proposed solution, describe the controls implemented to secure AI models, AI-generated data, prompts, logs, interfaces, training processes, and associated services. Include information regarding access controls, encryption, monitoring, auditing, model governance, and protection against unauthorized use or manipulation.

· Security Certifications and Compliance: Identify any security certifications, audits, assessments, or compliance frameworks applicable to the proposed solution, including third-party security reviews and adherence to applicable industry standards and public safety security best practices.

· Business Continuity and Disaster Recovery: Describe the vendor's approach to resiliency, disaster recovery, and continuity of operations, including procedures and technologies used to maintain emergency communications operations during system failures, network disruptions, cyber incidents, or facility outages. DEM currently utilizes alternate-answer switching capabilities that allow emergency calls to be redirected to a backup call-answering environment during failures of the primary call handling system. Vendors shall describe how their proposed solution will support, replace, or improve upon this functionality, including failover procedures, continuity of emergency and non-emergency call processing, and maintenance of operational capabilities during degraded or backup operations.

· Redundancy and Availability: Describe the backup, redundancy, failover, and geographic resiliency capabilities of the proposed solution. Include information regarding high-availability architecture, cloud resiliency options, warm backup site support, data replication, and continuity of operations capabilities. Vendors shall identify all third-party dependencies associated with the proposed solution, including cloud service providers, telecommunications carriers, NG9-1-1 service providers, and other external systems. Vendors shall describe the role of each dependency and its impact on system availability, failover, and continuity of operations.

· Recovery Objectives: Provide Recovery Time Objectives (RTO) and Recovery Point Objectives (RPO) for all major system components and describe how these objectives will be achieved and validated during testing, failover, disaster recovery, and continuity of operations scenarios.

· Monitoring and Alerting: Describe system monitoring, health monitoring, notification, and alerting capabilities available to support operational awareness, fault detection, and system recovery activities.

Public Safety Security Standards: Describe support for CJIS security requirements, NG-SEC principles, NIST Cybersecurity Framework alignment, role-based access control, multifactor authentication, and audit logging capabilities.

Section 2: Pricing DEM seeks information regarding available pricing models, implementation costs, and long-term support costs associated with the proposed Call Handling System solution. Vendors should provide sufficient detail to assist DEM in understanding total cost of ownership and evaluating alternative deployment and contracting approaches.

CAL OES Contract Information: DEM anticipates acquiring the Call Handling System through the California Governor’s Office of Emergency Services (Cal OES) a 9-1-1 Systems and Services Contract Agreement with California Office of Emergency Services (CaL OES) those Contractors who were responsive to the Invitation for Bid (IFB) 26-16743 technical and administrative vehicle. Vendors shall identify the applicable Cal OES contract under which their solution is offered and describe the products, services, implementation support, maintenance, training, and optional features available through that contract. Vendors should also identify any components or services not included under the Cal OES contract and explain any associated considerations for DEM.

Cost Breakdown: Provide a high-level breakdown of anticipated costs associated with implementation and operation of the proposed solution. Include hardware, software, licensing, professional services, implementation, integration, training, project management, cybersecurity services, cloud-hosted services, and any other significant cost component.

See Attachment 1 Optional Features and Services: Identify any optional capabilities, modules, integrations, resiliency features, cloud services, reporting tools, analytics platforms, cybersecurity enhancements, or other value-added services that may be procured separately from the base solution. Vendors shall identify all AI-enabled modules, features, licensing options, hosted services, consumption-based services, and professional services associated with AI functionality. Vendors shall clearly identify whether AI functionality is included within the base solution, available as an optional capability, or licensed separately under the applicable Cal OES contract.

Section 3: References:

Submit up to three (3) to five (5) references from public safety agencies or PSAPs where your firm has implemented or currently supports a Call Handling System solution in the last ten years. At least two references should represent large metropolitan or regional PSAP environments if available. Please include:

· Name

· Contact information (name, address, phone, email)

· Dates of Services

· Project name

· Brief project scope description

Section 4: Back Up PSAP Relocation:

DEM is evaluating a relocation of the backup Public Safety Answering Point (PSAP) from One South Van Ness to 1455 Market Street, in mid-2027.

As part of this initiative, DEM requires a fully functional backup E911 communications center with a minimum of 36 Call Taking/Dispatcher positions.

DEM requests that vendors describe their proposed solution for supporting backup operations, including the following:

· A backup 911 location capable of supporting a minimum of 36 workstations.

· The facility must be capable of operating with minimum essential 911 functionality for a duration ranging from one hour to one year following activation.

· Vendors should describe deployment timelines, available functionality, resiliency, connectivity, and any operational limitations during short-term use.

Vendors should also identify any facility, infrastructure, network, power, environmental, security, or telecommunications requirements necessary to support both backup scenarios, as well as any ongoing maintenance or readiness activities required to ensure the facility can be activated within the required timeframes.

Section 5: CALOES and DEM Requirements See Attachment 2.

Section 6: Optional - Submit additional information such as specification sheets, product brochures, etc. Please provide documentation relevant to your company’s response, and the nature of this RFI and this project.

VIII. RESPONSE SUBMISSION REQUIREMENTS

All questions, requests for clarification, and requests for additional information regarding this RFI must be submitted to DEM-PMO@sfgov.org. All such questions and requests must be submitted by e-mail. Responses to such questions and requests shall be at DEM’s sole discretion and nothing in this RFI shall create an obligation by DEM to provide any response to the submitting party. Responses may, at DEM’s sole discretion, be posted as addenda to this RFI on DEM’s website.

Responses must be submitted by e-mail to the following address and received by 5:00 pm PT on the Response Due Date.

Email: DEM-PMO@sfgov.org City & County of San Francisco Department of Emergency Management 1011 Turk Street San Francisco, CA 94102 Submission format: one electronic file (USB drive).

ELECTRONIC FORMAT NOTE: PLEASE CREATE ONE (1) SEPARATE FILE PER SECTION AND SAVE ALL FILES IN A SINGLE FOLDER. Thank you.

Vendor Response Checklist ☐ Section 1 – Primary Response ☐ A. Company Information:

☐ B. Product Information:

☐ C. Implementation Approach ☐ D. Training ☐ E. Maintenance and Support ☐ F. Security and Resiliency ☐ Section 2 – Pricing (Attachment 1) ☐ Section 3 – References ☐ Section 4 – Back Up PSAP Relocation ☐ Section 5 – Requirements (Attachment 2) ☐ Section 6 – Additional Materials (optional)

IX. TERMS AND CONDITIONS OF THIS RFI

Responses to this RFI become the exclusive property of DEM and subject to the California Public Records Act and the City's Sunshine Ordinance. Please be aware that any information submitted, even personal identifying information, may be disclosed to the public.

The Respondent shall be solely and fully responsible for all costs associated with the development, preparation, transmittal, and submission of any material in response to this RFI. DEM may, in its sole discretion, ask selected Respondents to present their material in person to City’s representatives at DEM’s offices, and the costs of such presentations shall be solely the responsibility of the Respondent. DEM assumes no contractual or other obligations as a result of the issuance of this RFI, the preparation or submission of materials by a Respondent, the evaluation of materials, the Respondent’s conducting of presentations, or the selection of any Respondent for further negotiations. There may be no claims whatsoever for reimbursement from DEM for such costs.

RFI – Call Handling System

CCSF Department of Emergency Management ● 1011 Turk Street ● San Francisco, CA 94102 1 | Page

X. SUBMITTING A RESPONSE TO THE RFI

The submittal of a response to this RFI does not guarantee use of the information provided. This is not a Request for Proposals (RFP). DEM, at its sole discretion, will determine if a RFP or other competitive solicitation may be issued at a later date. Any RFP issued by DEM may differ significantly in content from the applications and services described in this RFI. This RFI is to be used solely for the purpose of this industry review and DEM assumes no responsibility for any other use of this document. It is not a requirement to participate in this industry review process to be considered by any competitive solicitation arising out of this process. Participation in this industry review is strictly voluntary, and DEM will not reimburse participants for any costs in connection therewith. Submission of the RFI does not guarantee any future business with DEM. The issuance of this RFI does not constitute agreement by DEM that any contract will be entered into by DEM. DEM expressly reserves the rights to:

1. Waive or correct any defect or informality in any proposal, response or response procedure.

2. Prior to submission deadline for responses, modify all or any portion of the schedule for receiving responses.

3. Procure any materials, equipment, products, or services specified in this RFI by any other means; or

4. Determine that no project will be pursued.

CCSF Department of Emergency Management ● 1011 Turk Street ● San Francisco, CA 94102 21 | Page

Attachment 1 – Price Proposal

Please use Cost Workbook from CalOES Contract as noted on their website https://www.caloes.ca.gov/office-of-the-director/operations/public-safety-communications/ca-9-1-1-emergency-communications-branch/ca-911-services-contracts/

Attachment 2 –: Cal OES Exhibit B Technical Requirements (Invitation for Bid (IFB) 26-16743) and DEM Requirements

The DEM requirements reference both PNSP and RNSP networks, which is the current deployment model in California. DEM understands that the Rand Institute is currently in the process of evaluating the deployment of NG-911 in California, and the current design architecture might change in the future. DEM expects that the selected vendor will work with just a single PNSP ESINET, or a PNSP and RNSP solution, depending on the future deployment model that is chosen

PLEASE See Excel spread sheet Attachment 2

Attachment 3 – 1011 Turk Floor Layout

Request from: DEM-PMO@sfgov.org image1.png image2.wmf

File details come from the government source that posted it. Updated .