FINAL_Vendor_-_SF_DEM_RFI_0000012230_Requirements.xlsx

XLSX spreadsheet 69 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

Summary

This is a vendor requirements document for a Request for Information (RFI 0000012230) issued by the San Francisco Department of Emergency Management (DEM) in collaboration with the California Governor's Office of Emergency Services (Cal OES) for a next-generation Call Processing Equipment (CPE) solution. The RFI seeks detailed vendor responses regarding the capabilities and maturity levels of proposed NG9-1-1 call handling systems that will transition the City and County of San Francisco from legacy E9-1-1 to NG9-1-1 operations. Vendors must provide narrative responses and assign Capability Maturity Classifications (GA, CFG, CD, RM, or NA) for each of over 200 requirements organized into categories including Critical Requirements, Compliance and Standards, Interface Requirements, Functionality, Network Operations, Security, Service Management, Testing and Validation, Configuration Management, Cloud-Specific Technology, and On-Premises General requirements. The document specifies that any requirements marked as Custom Development (CD) or Roadmap (RM) must include planned version/release information and estimated availability dates. Responses should address system resilience, redundancy, NENA i3 compliance, FedRAMP High certification for cloud providers, integration with existing Computer-Aided Dispatch systems, support for multimedia emergency communications, failover capabilities maintaining 99.999% availability, and comprehensive security controls aligned with NIST 800-53 and NENA i3 cybersecurity standards.

The requirements emphasize that the proposed solution must support both current E9-1-1 CAMA/PSTN operations and future NG9-1-1 IP-based services simultaneously during transition periods, with seamless migration capabilities without requiring CPE replacement. DEM seeks cloud-native, geographically diverse deployments across multiple Tier 3 data centers with dedicated single-tenant California isolation, advanced features including AI-assisted call handling with transcription and translation capabilities, configurable automatic call distribution with role-based routing, integrated mapping and video support, and comprehensive data integration through standardized APIs. The vendor must commit to extensive testing and validation in DEM-approved facilities, provide dedicated trainers and cutover support over multiple days with 24/7 coverage, establish a 24/7/365 Network Operations Center for monitoring and support, support rollback procedures within 30 minutes of authorization, maintain detailed audit logs and reporting capabilities with raw data API access, and preserve all operational data ownership by DEM. Training materials must be provided 2–4 months before cutover, and workstations with vendor-supplied peripherals require replacement every five years minimum with optional two-year extended maintenance grace periods thereafter.

View the file

Other files

File Type Posted
FINAL__DEM_CHE_RFI_0000012230.docx DOCX document
DEM___IT_9-1-1_Call_Handling_System.pdf PDF
DEM___IT_9-1-1_Call_Handling_System.xml XML file

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

Vendor Instructions

RFI 0000012230 - SAN FRANCISCO DEM CHE VENDOR RESPONSE INSTRUCTIONS

Purpose
Vendors must provide a narrative response and a Capability Maturity Classification for each requirement. The classification is intended to distinguish production-ready functionality from configurable features, custom development, roadmap items, or unavailable capabilities.
Vendor Response Column
Use the Vendor Response column to describe how the proposed solution satisfies the requirement. Include assumptions, dependencies, limitations, configuration needs, optional modules, licensing considerations, and any relevant implementation notes. Do not use a separate comments column. All vendor narrative information should be included in Vendor Response.

Capability Maturity Classification Dropdown

CodeClassificationDefinition / Required DetailAll CodesCodes Allowed Before Planned Release Is Entered
GAGenerally AvailableAvailable today in production.GAGA
CFGAvailable Through ConfigurationAvailable today through configuration without custom development.CFGCFG
CDRequires Custom DevelopmentRequires custom development before use. Provide anticipated software version/release and estimated availability date.CDNA
RMProduct Roadmap / Future ReleasePlanned for a future release. Provide anticipated software version/release and estimated availability date.RM
NANot AvailableCapability is not available in the proposed solution.NA
CD and RM Follow-Up Requirement
For any requirement classified as CD or RM, vendors must complete Planned Version / Release and Estimated Availability Date. These fields are not required for GA, CFG, or NA unless additional clarification is helpful.

CAL OES + DEM Requirments

State of California Exhibit B Baseline with San Francisco DEM Supplemental RequirementsVendor Response
Requirement NumberNarrative RequirementUser StoryVendor Response
Microsoft Copilot: Vendor narrative response. Describe how the proposed solution meets the requirement, including assumptions, limitations, references to existing deployed functionality, and any required services or dependencies.Capability Maturity Classification
Microsoft Copilot: Select GA, CFG, CD, RM, or NA. CD and RM require planned version/release and estimated availability date.Planned Version / Release
Microsoft Copilot: Required for CD or RM responses.Estimated Availability Date

Microsoft Copilot: Required for CD or RM responses.

Critical Requirement (CR)
CR-1The Call Processing Equipment (CPE) solution shall be commercially available and proven, with a verifiable installed base and supportable by certified local technicians. Any Bidder who has had call processing equipment removed from installation in the State of California (CA) due to technical issues within the last five (5) years does not have viable CPE.
CR-2Cloud native solution shall utilize a cloud service provider that holds a verified FedRAMP High certification.
Compliance and Standards Requirements (CS)
CS-3Shall follow the NENA i3 standard for call handling as defined by the Cal OES Interface Control Document (ICD).
CS-4Shall follow the Cal OES ICD for all connectivity, interfaces, and network architecture.
CS-5Shall use the PSAP Credentialing Agency (PCA), the top-level certificate authority for NG9-1-1 in California, which is administered by the CA 9-1-1 Branch and is implemented by the NG Bidder.
CS-6Shall have redundant components such that no single component failure results in a loss of service or capability.
CS-7Shall ingress, display, and send Real Time Text (RTT).
CS-8Shall support integrated text-to-9-1-1, as defined by the Cal OES Interface Control Document (ICD).
CS-9Shall ensure that proprietary standards and or protocols are minimized within the proposed CPE system. Where systems utilize customized solutions, the Contractor shall identify the standard or protocol substituted and provide a narrative with regard to meeting the NENA i3 requirement.
CS-10Shall implement new industry standards in accordance with the Cal OES ICD, within the timeline directed by the CA 9-1-1 Branch. For most, but not necessarily all updates, the CA 9-1-1 Branch will direct a minimum timeline of 6 months.
CS-11Shall process and deliver all potential NENA i3 9-1-1 traffic from multiple NG 9-1-1 service providers per the Cal OES ICD.
CS-12Shall use the California Next Gen Service Provider’s core services for all transfers of i3 calls in accordance with the Cal OES ICD.
CS-13Shall process SIP, CAMA, and analog traffic for both emergency and administrative call types.
CS-14Shall be designed to FCC best practices and NENA i3 standards, including NENA STA-040 (NG-SEC) and 75-502 (NG Security Audit Checklist).
CS-15CPE ANI/ALI display and refresh shall meet the minimum requirements in the NENA standard.
CS-16Shall accommodate the most current Statewide ALI format and must be configurable at no cost for any future changes.
CS-17Shall be NENA i3 compliant as defined by the Cal OES ICD at the time of NG network go-live. If call handling is not i3 compliant, Bidder will be provided 6 months to bring the call handling into compliance, at no cost to the State of California.
CS-18Any component (e.g. routers, firewalls, gateways, switches, servers, etc.) that has been announced as end-of-sale within one year of installation is not acceptable. If a device or software goes into end-of-maintenance/support status within the contract period, its equivalent or better current manufacture will be installed at the contractor’s expense unless agreed otherwise.
CS-19Shall be capable of requesting location from any LIS using HELD or SIP Presence Subscription as described in NENA-STA-010.3.
CS-20Shall support STIR/SHAKEN. Attestation level, as determined by the STI-AS in the NGCS will be visually displayed to the call taker, and if less than “A” level, highlighted.
DEM Supplemental Requirements for Review - Compliance and Standards Requirements (CS)
CS-DEM-1Describe how the CPE shall support a direct interface to the

NG911 network in California. Description shall include how CPE solution will interface to the PNSP and RNSP in a NENA i3 compliant format and how the connections will be redundant and geographically diverse.

CS-DEM-2 Describe how the CPE shall be configured to avoid all single points of failure within the system and to ensure 99.999% availability.

Description shall include integration of IP phone sets.

CS-DEM-3Vendor shall demonstrate preservation of active emergency and administrative calls, queued calls, text messages, and all associated call data during an active-component failure, server switchover or planned restart. Identify any interruption, requeue, disconnect, or manual action and validate results in DEM acceptance testing.
CS-DEM-4Describe how CPE shall deliver and display secure NG9-1-1 traffic

from RNSP and PNSP. Information included should contain, but not be limited to, accurate ANI/ALI information as well as supplemental data (Z axis coordinates, information from IOT devices, as well as pictures and video).

CS-DEM-5 Describe how CPE will utilize an open standards methodology wherever possible. Description shall include how proprietary standards and/or protocols are minimized within the proposed CPE system and shall address any limitations that may result from those proprietary components. Finally, where systems utilize customized solutions, the description shall identify the standard or protocol substituted and provide a descriptive narrative with regard to meeting NENA i3 standards.

CS-DEM-6 Bidder to describe how their solution and leadership is flexible to accommodate minor variations in functionality or PSAP needs that demonstrates a commitment to transparency within bidder's Exhibit 22 MRCs. For example: NENA updates the i3 specification for EIDO or requirement to comply with PSAP (Public Safety Answering Point) Credentialing Agency (PCA).

CS-DEM-7Describe the vendor’s recommended deployment architecture for the San Francisco Department of Emergency Management (DEM), including primary site, secondary/alternate site, and any cloud or hosted components. The description shall explain how the recommended architecture supports system resiliency, redundancy, and continuity of operations.
CS-DEM-8CPE shall support all current and future NENA i3 standards at no additional cost.
CS-DEM-9CPE shall support the current operational needs of the PSAP as

identified in the NENA i3 standard and the SOW.

CS-DEM-10Support integrated inbound and outbound text workflows.
CS-DEM-11Support RTT workflows as prescribed by CALOES and NGCS provider.
CS-DEM-12The Vendor shall describe how the proposed solution maintains continuity of chat-based communications across call transfers, position changes, user sign-ins, system failovers, and transitions between primary and backup facilities. The response shall explain how the solution preserves conversation history, participant information, timestamps, attachments, and associated incident or call data without requiring the telecommunicator or caller to restart the conversation. The Vendor shall identify any limitations, dependencies, or circumstances that may result in the loss of chat content or context.
CS-DEM-13CPE shall support interoperability with the San Francisco Department of Emergency Management (DEM) emergency communications environment for both current E9-1-1 and future NG9-1-1 operations. The solution shall interoperate, as applicable, with authorized E9-1-1 service providers, legacy CAMA/PSTN infrastructure, Emergency Services IP Networks (ESInets), NG9-1-1 service providers, and other authorized public safety systems through industry-standard interfaces. CPE shall interface with CAMA and NG 9-1-1 connectivity simultaneously.
CS-DEM-14CPE shall support highly available, resilient connectivity for both current E9-1-1 and future NG9-1-1 operations. The solution shall interface with authorized E9-1-1 service providers, legacy CAMA/PSTN infrastructure, Emergency Services IP Networks (ESInets), and authorized NG9-1-1 service providers, as applicable, through a minimum of two (2) logically and physically diverse network connections. The proposed solution shall support an overall system availability of at least 99.999%.
CS-DEM-15Data center/cloud shall comply with NENA i3 cyber security

standards and industry best practices for cyber security.

CS-DEM-16CPE shall support standards-based interfaces for the receipt, processing, routing, transfer, and management of emergency communications for both current E9-1-1 and future NG9-1-1 operations. The solution shall interoperate with authorized E9-1-1 service providers, NG9-1-1 service providers, Emergency Services IP Networks (ESInets), and other authorized public safety systems, as applicable, and shall comply with current published NENA i3 standards and subsequent applicable revisions; shall support secure, resilient call delivery for both current E9-1-1 and future NG9-1-1 operations. The solution shall support logical connectivity between the call delivery network and the DEM Public Safety Answering Point (PSAP), including legacy E9-1-1/CAMA infrastructure, SIP-based NG9-1-1 services, Emergency Services IP Networks (ESInets), and authorized E9-1-1 and NG9-1-1 service providers, as applicable to the proposed deployment architecture.
CS-DEM-17CPE shall support all elements of NENA i3. Any components

that are implemented within the CPE shall not compromise the ability to support NENA i3 and the ability for the PNSP or RNSP to deliver the call to the PSAP, or to support transfers from one PSAP to another, regardless of CPE vendor.

CS-DEM-18CPE shall support implementation of applicable industry standards, including current published NENA i3 standards and subsequent applicable revisions, in accordance with a mutually agreed-upon implementation plan approved by the San Francisco Department of Emergency Management (DEM). The vendor shall notify DEM of applicable standards updates, identify operational impacts, document system changes, and provide an implementation schedule, testing plan, rollback procedures, and deployment recommendations prior to production implementation. The solution shall support both current E9-1-1 operations and future NG9-1-1 operations throughout the standards transition process.
CS-DEM-19CPE shall support rollback to the previously validated software or firmware version if an update, patch, or upgrade results in unintended operational failures, degraded performance, or loss of functionality. Upon DEM authorization, the vendor shall initiate rollback procedures as soon as practicable, with rollback completed within thirty (30) minutes unless otherwise approved by DEM. The vendor shall document rollback procedures, recovery steps, configuration preservation, and post-rollback verification as part of the software maintenance process.
CS-DEM-20CPE shall support manual and configurable automatic location refresh for voice and text calls, display location source and timestamp, and preserve values. Updated location shall not overwrite a manually entered CAD incident location. Vendor shall state supported refresh intervals and demonstrate behavior with current and future CAD interfaces.DEM would like the ability to turn on and off this feature, as well as the ability to manually rebid for an updated location. Any updated location after the initial ANI/ALI delivery should not automatically push to CAD, but should support a manual CAD dump initiated by the call taker.
CS-DEM-21CPE shall support secure authentication, trust, identity management, and digital certificate services necessary for interoperability with both current E9-1-1 and future NG9-1-1 environments. For NG9-1-1 operations, the solution shall support interoperability with authorized Public Key Infrastructure (PKI), certificate authorities, and trust management services in accordance with current published NENA i3 standards and applicable industry security practices.
CS-DEM-22The CPE shall support migration from legacy E9-1-1 to NG9-1-1 without requiring replacement of the CPE.
CS-DEM-23CPE system shall support BGP interfaces to state NG 9-1-1

service provider and comply with the IP addressing scheme provided by CA 9-1-1 Branch.

CS-DEM-24 CPE shall have the capability to terminate native IP telephony as well as CAMA/analog emergency and administrative traffic.

CS-DEM-25The proposed Call Handling System shall provide resilient operation to ensure continuity of emergency communications during equipment failures, network disruptions, and Continuity of Operations (COOP) events. The following requirements establish the minimum survivability capabilities required to maintain emergency call processing and associated operational functionality.
CS-DEM-26Preserve ANI, ALI, PIDF-LO, text history, and transfer metadata during failover from Node (or Site) A to Node (or Site) B.
CS-DEM-27Support operational equivalency during failover conditions from Node (or Site) A to Node (or Site) B.
CS-DEM-28The proposer shall describe how their offering will be compatible with the existing legacy environment and clear transitions to NG as prescribed by CAL OES.
CS-DEM-29The vendor shall describe how system resiliency is achieved across deployment models, including geographic diversity, data replication, failover mechanisms, and operational continuity. The description shall include how active calls, call metadata, and operational workflows are preserved during failover events across deployment environments.
CS-DEM-30Operational queue information shall remain accessible through the call handling interface if the primary dashboard or reader-board display becomes unavailable.
CS-DEM-31Support NG-SEC alignment.
Interface Requirements (INT)
INT-1Shall interface with the existing Computer Aided Dispatch (CAD) system in place at the PSAP regardless of age or interface type (IP or serial). If the CAD supports EIDO, shall support EIDO as defined in the NENA i3 standard.
INT-2Shall interface with analog and digital radio at the PSAP to support consistent audio levels between radio and CPE.
INT-3Shall generate i3 logs in accordance with the NENA i3 standard.
INT-4Shall generate call data record (CDR) in accordance with the CA 9-1-1 Branch defined CDR standard.
INT-5Shall interface with CA 9-1-1 Branch's management information system (MIS) via NENA i3 logging standard and the CA 9-1-1 Branch defined CDR standard.
INT-6Shall provide logging of call-handling activities using a NENA-STA-010.3 conformant logging service.
INT-7Shall interface with the peripheral equipment configurations already in place at all PSAPs at no cost to the state. This equipment includes but is not limited to CAD, logging recorders, radio, mapping, etc.
INT-8Shall provide a SIPREC compliant interface for onsite logging recorder at the PSAP.
INT-9Shall display caller ID from any non 9-1-1 line if provided by the originating service provider and shall be configurable by the PSAP.
INT-10Shall implement standardized Application Programming Interfaces (APIs) for third-party system integration, enabling connection with mapping systems, logging recorders, and other PSAP applications while maintaining security and performance standards as may be directed by Cal OES.
INT-11Shall develop standardized Application Programming Interfaces (APIs) to integrate with any new technologies not outlined in these requirements as agreed upon between Bidder and Cal OES. API development shall align to the contract line items in the cost workbook.
INT-12Shall ingest and display any third party or State provided data via API within 6 months of notification from the CA 9-1-1 Branch.
INT-13Workstations shall support the minimum memory and processing capability to support CPE software and shall be equipped with all necessary audio and video interface equipment, including but not limited to: keyboard, mouse, speakers, audio integration device, keypad dialer, arbitrator, and minimum 22 inch flat panel monitors.
INT-14CPE hardware components installed at the PSAP shall be nonproprietary, with the sole exception of audio control devices, and shall support standard hardware interfaces.
INT-15Shall include a UPS for each workstation and all the backroom equipment that provides power for a minimum of 15 minutes.
INT-16All workstation peripherals shall be supplied by the Contractor and supported at the workstation: auxiliary keypad dialers, arbitrators, keyboard, mouse, and headset box.
INT-17Shall connect to analog or digital audio interface devices at the PSAP, as directed by the PSAP.
INT-18Shall provide all required cabling, which may include cable paths through floors, walls, ceilings, and between buildings. Cabling may include connecting to controllers, NG Service Providers handoffs, demarcation points, CAMA trunks, admin lines, workstation, and ALI sources.
INT-19Electrical components installed at PSAP must run on 120 volt AC power.
INT-20Shall connect to the State’s Automatic Location Identification (ALI) provider for PSAPs accepting CAMA calls. Shall connect and query ALI in accordance with the Cal OES ICD.
DEM Supplemental Requirements for Review - Interface Requirements (INT)
INT-DEM-1Describe how the CPE shall interface with the peripheral analog

and digital equipment configurations already in place at the PSAP. The description shall include the interface to CAD, radio, and logging recorder.

INT-DEM-2Vendor shall describe long-term recording and retention time through the existing NICE environment and SIPREC interface, including supported media, search, export, and access controls. Separately describe authorized playback from all workstations, identifying configuration and licensing requirements.Currently recordings are accessible at the terminal that received the call for 24 hrs, accessible by other terminals for 30 minutes, and accessible via NICE for 3 years. Perhaps it would be useful for CTOs if there is a terminal in the Training Quad that is designated as being able to access recordings for 10 hours, allowing CTOs to review recordings of calls with their trainee within a shift.
INT-DEM-3CPE shall utilize the standardized API developed by the PNSP and

DEM and applicable State NG9-1-1 authorities for all interfaces to deliver 9-1-1 traffic to the

CPE.

INT-DEM-4 CPE shall support a NENA i3 compliant interface to the existing CAD system in operation at the PSAP. All non-i3 ready CAD systems require interface providing serial ANI/ALI spill functionality.

INT-DEM-5 CPE shall connect to analog or digital audio interface devices at the PSAP to support consistent audio levels from radio and CPE for the call taker. Include recommended headsets and adaptors and cabling for consistency.

INT-DEM-6 Describe how CPE will ingest and display statewide GIS data layers, or shape files, and shall provide an interface at the PSAP's request. DEM shall provide database for updated GIS files in a NENA i3 compliant format via secure file or secure web interface.

INT-DEM-7 CPE interface shall comply with NENA i3 standard for the delivery of callback and location information to CAD, mapping applications, and voice recorders.

INT-DEM-8Maintain survivable integration with the Computer-Aided Dispatch (CAD) system by preserving call-related metadata throughout call transfers and failover events, supporting automatic incident correlation and contextual incident presentation, and ensuring continuity of CAD interoperability during normal, degraded, and failover operations.
INT-DEM-9Support integration with supplemental emergency data services, including location information and associated operational workflows, through industry-standard interfaces.
INT-DEM-10CPE shall interface with the peripheral equipment configurations

already in place at all PSAPs: GIS, radio, logging recorder, etc.

INT-DEM-11 CPE shall develop a Basic API that aligns to the State cost workbook at the request of the PSAP with with direction from the San Francisco Department of Emergency Management (DEM), in coordination with applicable State NG911 authorities, if required to support a one time 1-3 month API development outside of NENA i3 and SOW requirements.

INT-DEM-12 CPE shall develop an intermediate API that aligns to the State cost workbook at the request of the PSAP with direction from the San Francisco Department of Emergency Management (DEM), in coordination with applicable State NG911 authorities, if required to support a one time 3-6 month API development outside of NENA i3 and SOW requirements.

INT-DEM-13 CPE shall develop a Complex API that aligns to State cost workbook element at the request of the PSAP with with direction from the San Francisco Department of Emergency Management (DEM), in coordination with applicable State NG911 authorities, if required to support a one time 6-9 month API development outside of NENA i3 and SOW requirements. with direction from the San Francisco Department of Emergency Management (DEM), in coordination with applicable State NG911 authorities, if required.

INT-DEM-14CPE shall support integration with the San Francisco Department of Emergency Management’s (DEM) current Computer-Aided Dispatch (CAD) system (CentralSquare Total Command) and future CAD system (Motorola PremierOne). The solution shall maintain full operational functionality and interoperability with both environments during any transition period.
INT-DEM-15CPE shall generate NENA i3 Call Detail Record (CDR)

automatically, and store all available information pertaining to all 9-1-1 traffic, on a server that allows access by or connectivity for state-wide reporting purposes.

INT-DEM-16The Vendor shall describe how the proposed solution supports the receipt, presentation, management, storage, and transfer of multimedia communications, including images, video, documents, chat content, and other supplemental incident information. The solution shall maintain the association between multimedia content and the related call or incident throughout processing, transfer, failover, and archival. The solution shall support Emergency Incident Data Object (EIDO)-based exchange with CAD systems, other authorized public-safety systems, and external agencies in accordance with applicable NENA i3 standards. The Vendor shall identify supported EIDO interfaces, data elements, transfer methods, security controls, dependencies, and known limitations.
INT-DEM-17CPE shall deliver location information to CAD and mapping

applications via an IP connection and/or serial connection.

INT-DEM-18The vendor shall describe how recording services will be maintained during system implementation and cutover, including integration continuity with NICE logging recorder systems, recording failover behavior, data retention compatibility, and migration considerations.
INT-DEM-19The vendor shall demonstrate compatibility with DEM-approved headsets, amplifiers, handsets, adapters, and future headset technologies as part of system acceptance testing.
INT-DEM-20CPE shall be compatible with the San Francisco Department of Emergency Management's (DEM) existing uninterruptible power supply (UPS), automatic transfer switch (ATS), and emergency power infrastructure. The vendor shall identify any additional power protection requirements necessary to support the proposed solution. If additional UPS or power conditioning equipment is required as part of the proposed solution, the vendor shall identify and provide such equipment. All solution components shall support an orderly shutdown and recovery following extended power interruptions, where applicable.
INT-DEM-21Contractor shall provide cabling at install, which may include

cable paths through floors, walls, and ceilings.

INT-DEM-22The vendor shall describe the approach to supporting CAD system transition from the current environment to the future CAD platform. This shall include coexistence strategies, data integration, interface continuity, cutover approach, and any required changes to workflows or system configuration during transition. Identify any feature not supported in either environment.
INT-DEM-23CPE shall support standards-based application programming interfaces (APIs) and interfaces necessary to receive, process, and manage emergency communications for both current E9-1-1 and future NG9-1-1 operations.
INT-DEM-24CPE shall support standards-based interfaces for the exchange of operational, administrative, and call detail reporting data with DEM-authorized reporting, analytics, and management information systems. The solution shall support current E9-1-1 and future NG9-1-1 operations and shall utilize applicable NENA standards, open interfaces, and documented data formats for the exchange of call detail records (CDRs), operational statistics, event logs, and other reporting information, as applicable.
INT-DEM-25CPE interface shall comply with NENA i3 standard for the delivery of

call data to CAD, mapping applications, and voice recorders where applicable.

INT-DEM-26CPE shall provide secure, standards-based, well-documented Application Programming Interfaces (APIs) to support integration with authorized third-party systems. The solution shall support both current E9-1-1 and future NG9-1-1 operations and enable the secure exchange of operational, administrative, and system data with authorized applications, including CAD, logging recorders, GIS, analytics, reporting systems, identity management services, and other authorized public safety systems. APIs shall utilize open, documented, non-proprietary interfaces where industry standards exist and shall support appropriate authentication, authorization, encryption, version management, and lifecycle support. The vendor shall identify all available APIs, supported standards, licensing requirements, and any limitations associated with their use.We currently use a Single Sign On (Universal Log IN) between CAD and CPE. This functionality needs to be available.
INT-DEM-27CPE shall ingest and display any third party or State provided data via API (RapidSOS etc.) as requested by DEM.
INT-DEM-28Describe the available data transfer capabilities between CPE and CAD for additional data outside of CDR including EIDO.
INT-DEM-29Vendor shall propose workstation monitor size, resolution, quantity, mounting, and accessibility compatible with DEM console dimensions and approved layout while retaining the state 22-inch minimum. Identify options and costs.
INT-DEM-30Vendor shall document compatibility, power draw, runtime, and redundancy with DEM's existing workstation UPS/ATS and backroom power infrastructure.We already have UPS and ATS at workstations.
INT-DEM-31Electrical components must run on 120 volt AC power at 60Hz.
INT-DEM-32Contractors installing 9-1-1 systems will be required to connect to

ALI databases of all regional ALI providers. When installing 9-1-1 systems, it shall be the responsibility of the Contractor to contact the regional ALI provider to obtain specific connection requirements. Automatic Location Identifier (ALI) Database Connection – Contractors will connect their equipment to an ALI router to request data from the ALI database. CPE must make an ALI request based on the ANI provided with the call.

INT-DEM-33 CPE must conform to the state defined management information system CDR and i3 logs output format.

INT-DEM-34 Contractor is responsible for the following:

•All cabling for connectivity among the controllers •All cabling for connectivity to the demarcation point for Centralized Automatic Message Accounting (CAMA) trunk, NG 9-1-1 Circuit (IP) and admin line connections •All cabling for connectivity to the NG ALI source.

INT-DEM-35Provide connection (a key in the database) for any calls that generate a new CAD record or are tied to an existing CAD record so that all of those calls can be linked to the CAD number directly.
INT-DEM-36The proposed call-handling solution shall receive, display, preserve, log, transfer, and make available for callback the complete E.164 international callback number associated with an emergency call. The solution shall support telephone numbers of up to 15 digits, including the applicable country code and the “+” international-number indicator.
INT-DEM-37The solution shall support configurable dialing translations that allow authorized personnel to initiate callbacks to domestic and international E.164 telephone numbers using DEM-approved outbound dialing plans. The solution shall preserve the original callback number presented to the call taker and shall support dialing normalization rules configured by DEM.
Functionality Requirements (FUN)
FUN-1Shall include a Graphical User Interface (GUI) that allows PSAP and/or call taker to personalize the CPE screen layout.
FUN-2Bidders who opt to provide automatic call distribution (ACD) shall provide a solution that is configurable by the PSAP. ACD functionality shall support interactive voice response (IVR).
FUN-3Shall allow authorized users with appropriate system permissions in an ACD deployment the ability to temporarily remove themselves from a ring group (call queue) in order to conclude a previous call or perform another task such as radio dispatch.
FUN-4Shall require users to manually log-on with a username/password combination. Two factor authentication must be provided as an option at no additional cost. Password parameters shall be flexible to meet PSAP needs. CA 9-1-1 Branch will validate two factor authentication method. PSAP shall have administrative rights controlling all account credentialing.
FUN-5Shall display live streamed video from IoT, caller, or supplemental data source when available and delivered natively through the NG network.
FUN-6Shall allow the call-taker to stop viewing the video even while the video is still recording when available and delivered natively through the NG network.
FUN-7Shall support instant recall recorder (IRR) play back of the recording of any call from an assigned workstation. The IRR shall interface with the existing operating environment within the PSAPs. IRR includes all 9-1-1 traffic, including calls, text, and video when available and delivered natively through the NG network.
FUN-8Shall provide the PSAP with configurable recording retention for IRR. System shall provide a minimum of 8 hours of recording time.
FUN-9Shall deliver caller ID of originating caller during a transfer from a 9-1-1 line to any non-9-1-1 line.
FUN-10Shall provide IP phone set(s), if requested by PSAP
FUN-11Shall perform language translations of text-to-9-1-1 and RTT for inbound and outbound messages, including languages with non-English characters. If translation is automatic, call taker shall have the ability to toggle the translation on and off during text session.
FUN-12Shall have adjustable audio volume control at the individual workstation.
FUN-13Shall provide notification for abandoned calls for any abandoned call that reached CPE. All available location information needs to be presented.
FUN-14Shall synchronize internal system time to the CA NG 9-1-1 network service provider.
FUN-15Shall define a list of phone numbers that can be entered into the solution to be routed to a specific position or login credential.
FUN-16Shall provide one-button callback as defined by the ICD.
FUN-17Shall provide complete call progress detection including but not limited to idle, ringing, dial tone, ring back, and busy.
FUN-18Shall provide configurable outbound caller-ID and outbound text-ID to the PSAP.
FUN-19Shall have one button transfer capability to other PSAPs, configurable by the PSAP.
FUN-20Shall provide local conferencing consisting of four (4) or more internal and/or external parties (including originator). The system’s conferencing functionality shall allow the conference call to continue when the originating calling party disconnects.
FUN-21Shall provide distinct audible ringing options for all call types configurable by the PSAP.
FUN-22Shall provide speed dial functionality for both hold conference and no-hold conference for 9-1-1 calls as well as non-emergency calls.
FUN-23Shall allow call taker muting capability during conference or transfer.
FUN-24Shall support TDD/TTY functionality until no longer required by the FCC and upon the direction of the CA 9-1-1 Branch.
FUN-25Shall provide an on-line reference manual, user manual, help guide, live chat, or similar feature to PSAP. All reference materials must be continually updated to reflect CPE system updates and new functionality.
FUN-26Shall automatically lock screen layout when user logs in as ready.
FUN-27Shall allow a designated user to modify screen layout.
FUN-28Shall allow a designated user to restore the last saved screen layout.
FUN-29Shall display the information of at least the last 10 calls released at the answering workstation.
FUN-30Shall provide the user with call holding as well as call parking (exclusive/non-exclusive hold) capability.
FUN-31Shall allow designated users the ability to silently listen to another user's telephone conversation from their workstation. Such action shall not cause any audio or visual disturbance at the monitored answering station.
FUN-32Shall allow authorized users the ability to barge into an existing call with one click functionality.
FUN-33Shall support text-from-9-1-1.
FUN-34Shall present historical details linked to a calling number. The details shall include information a call taker has previously entered for that phone number.
FUN-35Shall provide role based/skillset-based profiling for call takers, and the ability to change roles.
FUN-36Shall provide call taker the ability to flag, create, and send out incorrect location (mis-route) reports electronically.
FUN-37Shall support maximum 60 second application start-up from the time user ID and password are entered.
FUN-38Shall interface with a universal log in service at PSAP if available or shall support single sign on. Universal log in shall apply across CAD or other platforms as specified by the PSAP, and support where available.
FUN-39Shall provide status indication ("ready/not ready/wrap up") at the workstation level, number of status states to be configurable by PSAP.
FUN-40Shall allow PSAP personnel to play back a pre-recorded PSAP greeting on call answer and shall be configurable by call taker.
FUN-41Shall provide a clearly visible visual alert to the call taker when 9-1-1 traffic is delivered via a policy-based route.
FUN-42Shall ingest and display Z coordinates in accordance with the Cal OES ICD.
FUN-43If no NG 9-1-1 network or CAMA degradation is present, all audio input/output from the CPE shall meet MOS score requirements via third party verification. 99% of the MOS measurements shall exceed 2.6 and 90% shall exceed 3.8. Degradation caused by NG 9-1-1 network or CAMA shall not impact CPE MOS score.
FUN-44Shall include the following telephony functionality: hold, dial, re-dial, release, transfer, conference, speed dial, ALI request, ANI/ALI display, PSAP defined line appearances, multi-function programmable keys (programmed as telephone line appearance or a feature of the telephone set), headset/handset interface, volume control for inbound audio signal for headset/handset, volume control for outbound signal and sidetone for headset/handset, volume control for the ringer, call status indication (ringing, answered or on hold).
FUN-45Shall allow for communication between workstations via broadcast messaging, or instant messaging from each PSAP workstation and be configurable or disabled according to individual PSAP requirements.
FUN-46For i3 calls, shall be able to mute any participant in a conference and must be able to exclude any participant from hearing/seeing/texting other parties in the conference to allow for private consultation if necessary.
FUN-47All remote workstations must provide the same functionality and access as the current local PSAP positions.
DEM Supplemental Requirements for Review - Functionality Requirements (FUN)
FUN-DEM-1Describe CPE Automatic Call Distribution (ACD) functionality, including ACD for text to 911 .
FUN-DEM-2Describe how unique roles are created and defined. DEM needs to have the ability to control which call queues are answered (including answer order) based on the login role. DEM also requires a role to answer over flow emergency and non-emergency calls, allowing the user to move between queues and access queues on an ad hoc basis.Currently users log in with a specific role (PEC, PNC, PAC, PCC, etc.) which the system uses to prioritize which user should receive the next 9-1-1 call. Some roles will also receive non-emergency calls. One role receives only non-emergency calls. There is also a specific role which is the last to receive all calls (drops). Terminals used as radio positions also have a separate role and are not logged into the ACD queues. All positions are universal. Any role can log in to any position.
FUN-DEM-3Vendor shall demonstrate PSAP-initiated text and supported video-request workflows during an active voice call, including whether one call taker can handle both, caller consent/actions, correlation, delivery status and carrier/device dependencies.
FUN-DEM-4CPE shall provide DEM-configurable ACD and IVR. Vendor shall demonstrate DEM role-based emergency/non-emergency routing, priority order, overflow, and universal-position behavior, with text ACD.
FUN-DEM-5Support distributed handling of emergency communications, including voice calls and Text-to-9-1-1 sessions, across multiple locations while maintaining consistent routing, queue management, operational functionality, and incident continuity.
FUN-DEM-6Support remote call-taking operational equivalency. Explain how you support remote call taking from locations other than main center.
FUN-DEM-7CPE shall display live streamed video from IoT, caller, or

supplemental data source.

FUN-DEM-8 CPE shall allow the call-taker to initiate the viewing of video via a process initiated and controlled by the PSAP. Video should start recording immediately during transmission, but the call-taker should not be required to initiate viewing in order for the recording to begin.

FUN-DEM-9 CPE shall allow call taker to send video to any PSAP authorized first responder or recipient outside of dispatch with a device that can play video. Explain how it is viewable outside the department, ideally on a smartphone, tablet or MDT in a patrol car.

FUN-DEM-10 CPE short term video storage shall be configurable by the PSAP.

Video shall be locked so that it can only be viewed by authorized users. Additionally, metadata shall be made readily available to the PSAP in order to see a list of all viewers of any video.

FUN-DEM-11Vendor shall size recording storage for DEM-approved media, workload, retention, and growth; identify included capacity, limits, expansion method, and charges. Retention will align with the approved recording schedule.
FUN-DEM-12CPE shall display the CA 9-1-1 Branch statewide alert and warning

system. Explain types of messages and how it will display on the CPE.

FUN-DEM-13CPE shall synchronize to the authorized California NG9-1-1 time source in accordance with FUN-14 and support DEM-approved fallback time services. Store timestamps consistently and display local time as configured; vendor shall describe time-source hierarchy, failure behavior, and accuracy.
FUN-DEM-14CPE shall support DEM-configurable automated abandoned call back/text back with authorized enable/disable controls, retry limits, duplicate suppression, delivery status and complete audit logs. Vendor shall demonstrate behavior under queue load.
FUN-DEM-15CPE shall provide DEM-configurable one-button transfers for supported legacy and NG9-1-1 paths. Vendor shall demonstrate ANI/ALI, text history, and transfer metadata preservation for in-network, off-network, and out of state destinations, identifying unsupported paths and upstream dependencies. Describe directory updates and alternate numbers.
FUN-DEM-16A designated user shall have the ability to restore to last saved

screen layout as well as default screen layout while making modifications.

FUN-DEM-17Authorized users shall be able to change role/skill profile without logging out and signing in again. Vendor shall demonstrate the effect on active calls, queued assignments, status, and audit records.
FUN-DEM-18CPE shall support maximum 10 second system operation start-up

from the time user ID and password are entered or received from CAD via a Universal Login API.

FUN-DEM-19 CPE shall provide MIS functionality and shall provide call taker details. CPE shall provide remote access to PSAP defined MIS metrics.

FUN-DEM-20CPE bidder shall provide reader boards to PSAPs upon request.
FUN-DEM-21CPE solution shall provide an integrated mapping application.
FUN-DEM-22CPE solution should have ability to inject recorded message into emergency queue based on location in geofenced area.
FUN-DEM-23CPE shall support phone-number-based hazard and caution indicators that automatically present to the call taker whenever a configured telephone number contacts the PSAP, regardless of the caller's current location.
FUN-DEM-24The solution shall support sufficient user, agent, profile, and role capacity to accommodate DEM operational growth without requiring reuse or reassignment of unique agent identifiers during the operational life of the system.
FUN-DEM-25The vendor shall identify support for Rich Communication Services (RCS) and successor messaging technologies, including limitations and CAD integration impacts.
FUN-DEM-26The solution shall support authorized playback or controlled distribution of call recordings to approved public safety personnel, with full audit logging.
FUN-DEM-27CPE shall receive, ingest, display, and maintain vertical location (Z-axis) information for both current E9-1-1 and future NG9-1-1 operations whenever such information is available from authorized E9-1-1 service providers, NG9-1-1 service providers, or other authorized location information sources. The solution shall present vertical location information to the call taker in a clear, usable, and standards-compliant manner and preserve the information during call transfer, conferencing, and Continuity of Operations (COOP) events, where applicable.
FUN-DEM-28Enterprise Identity Management, Single Sign-On (SSO), and Multifactor Authentication (MFA)The CPE solution shall support centralized identity and access management through integration with DEM's enterprise identity provider, including Microsoft Entra ID or an equivalent identity provider. The solution shall support industry-standard G) - Centralized authentication and administrative activity logging to support security monitoring and auditing. federated authentication protocols, including SAML 2.0 and/or OpenID Connect (OIDC), with OAuth 2.0 support where applicable. A) Single Sign-On (SSO) for administrative and user-facing interfaces. B) Multifactor Authentication (MFA), including enforcement through DEM's enterprise identity provider. C) Role-Based Access Control (RBAC) with configurable permissions based on assigned roles. D) Centralized user provisioning, modification, and deprovisioning. E) - Enforcement of DEM's enterprise authentication, password, and access control policies. F) - DEM administrative control over user accounts, authentication methods, roles, permissions, and credential management.
FUN-DEM-29API between CAD and phone system for single sign on (Universal Logon).
FUN-DEM-30CPE system shall retain State minimum 8 hour IRR recording time. Vendor shall describe DEM configurable playback windows, authorized access, and available extensions.DEM desires the ability to listen to any call from any workstation for longer than 8 hours.
FUN-DEM-31CPE shall retain baseline FUN-11. Vendor shall describe delivery of original text, translated text, RTT content, timestamps, sender identity, and session identifiers to CAD, with live versus final transcript behavior, field mapping, limitations, and demonstrations.
FUN-DEM-32CPE shall provide abandoned call detail. Vendor must describe ability to manage abandoned Emergency calls.
FUN-DEM-33CPE shall provide complete call progress detection including but not limited to
idle, ringing, dial tone, ring back, and busy. The offeror shall describe how these different call states are made visible to the call taker.The current system does not always recognize busy/other tones that identify a caller as 'unavailable' and instead sends a pop-up message to the GUI stating something to the effect 'ISDN timeout'.
FUN-DEM-34Need different audible tones for CT to identify type of incoming call received.
FUN-DEM-35Authorized users shall be able to monitor another call taker silently, view associated ANI/ALI, and monitor active text sessions according to DEM permissions.In addition to silently listening, current system allows the person listening in to view ANI/ALI data that is currently showing on call taker's phone screen and to send same ANI/ALI data to CAD, if needed. Current system also allows another user to view text conversation live if user is monitoring the call taker who is receiving a text-to-9-1-1 call. (Current system allows ANY user to view active text-to-9-1-1 calls)
FUN-DEM-36Users with appropriate system permissions in an ACD deployment shall have the

ability to temporarily remove themselves from a ring group (call queue).

FUN-DEM-37 CPE shall present historical details linked to the calling number. This feature shall accommodate information that call-takers have saved from previous calls, but should also include system generated (machine learned) information.

FUN-DEM-38 CPE shall allow PSAP personnel to play back a pre-recorded PSAP message during the 9-1-1 call.

FUN-DEM-39CPE shall display DEM-configurable workstation/user states and state duration and integrate with approved console lighting. Audible alerts shall support queued 9-1-1 calls and low logged-in call taker thresholds.Currently have audible 911 call waiting bell and alert when down to one call taker logged into 911 and non emergency lines.
FUN-DEM-40CPE solution shall provide an configurable integrated mapping application. Feature shall be configurable with the PSAP ability to turn on and off without vendor intervention.
FUN-DEM-41Remote users shall maintain access to operational dashboards and workflows.
FUN-DEM-42The Solution shall provide automatic real-time transcription of all voice calls, with transcripts displayed to the call taker during the active call and retained as part of the incident record.
FUN-DEM-43The Solution shall provide AI-generated transcription and translation with measurable accuracy levels and allow correction of transcripts by authorized personnel.
FUN-DEM-44The Solution shall automatically identify and flag key information during a call, including:
•Caller location
•Call-back number
•Incident type
•Weapons references
•Medical concerns
•Suspect descriptors
•Vehicle descriptors
•Officer safety concerns.
FUN-DEM-45The Solution shall provide AI-assisted prompts and recommended questioning paths based on the reported incident type while allowing the call taker to maintain full control of the interaction.
FUN-DEM-46The Solution shall function as a decision-support tool only and shall not make operational decisions without human authorization.
FUN-DEM-47The Solution shall generate a proposed incident summary at the conclusion of a call for review, modification, and approval by the call taker.
FUN-DEM-48The Solution shall provide language detection and transcription support for multiple languages commonly encountered by the agency.
FUN-DEM-49The Solution should provide real-time translation assistance while preserving the original call transcript in the native language.

This is the start of the file's text. The full file is on GovTribe.

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