3-SLCI27013 Attachment 2 -Scope of Work.docx

DOCX document 30 KB Posted

Attached to
Salt Lake City Request for Proposals SLCI27013 - AI Enabled Non-Emergency Public Safety Call Handling and Assistive Solution
Solicitation number
SLCI27013
Issued by
Salt Lake County, Salt Lake City, Utah

About this file

This is a Scope of Work document for Salt Lake City Corporation's Request for Proposals (RFP No. SLCI27013) seeking qualified vendors to provide an AI-enabled non-emergency public safety call handling and assistive solution for the City's Emergency 911 Department. The solution is designed to enhance operational efficiency and improve caller experience through AI-assisted call handling, routing, transcription, and escalation capabilities while operating exclusively on designated non-emergency (10-digit) and administrative public safety lines. The proposed solution must continuously monitor caller interactions for emergency indicators and support immediate escalation to live 911 telecommunicators when necessary, with the critical stipulation that the solution shall under no circumstances replace, delay, or interfere with primary 911 emergency call handling operations. Callers must be able to request transfer to a live operator at any point during the interaction.

The vendor must deliver a comprehensive solution including all labor, software, licensing, implementation services, support services, maintenance, integrations, training, and related resources necessary for deployment and ongoing operation. The solution shall integrate with Salt Lake City's existing Motorola Vesta communications infrastructure and CAD systems, while incorporating advanced AI functionality such as conversational AI, real-time transcription and translation, intelligent call routing, and documented AI safety controls including hallucination mitigation and bias monitoring. The selected vendor must provide detailed implementation and deployment plans, onboarding and configuration services, ongoing technical support and maintenance, configurable analytics and reporting dashboards, administrative tools allowing authorized personnel to independently modify call flows and workflows without vendor intervention, and must demonstrate prior experience supporting public safety agencies and PSAPs with high call volumes and operational continuity requirements.

View the file

Other files

File Type Posted
5-SLCI27013 Attachment 4 Score Sheet.xlsx XLSX spreadsheet
1-Confidential+and+Proprietary+Info+Declaration+Form.pdf PDF
2-SLCI27013 Attachment 1 - Sample Agreement.docx DOCX document
6-SLCI27013.docx DOCX document
4-SLCI27013 Attachment 3 Cost Sheet.xlsx XLSX spreadsheet

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

Salt Lake City Corporation Request for Proposals, RFP No. SLCI27013 AI-enabled non-emergency public safety call handling and assistive solution Emergency 911

Scope of Work

1. Project Overview Salt Lake City Corporation (“City”) is seeking proposals from qualified vendors to provide an AI-assisted non-emergency call handling solution for designated non-emergency (10-digit) and administrative public safety lines. The solution is intended to enhance operational efficiency, improve caller experience, and support public safety communications personnel through AI-assisted call handling, routing, transcription, and escalation capabilities.

The proposed solution shall support public safety operational environments while ensuring that emergency calls and emergency-related situations are appropriately identified and escalated to live 911 telecommunicators when necessary. Under no circumstances shall the solution replace, delay, or interfere with primary 911 emergency call handling operations.

The selected vendor shall provide all labor, software, licensing, implementation services, support services, maintenance, integrations, training, and related resources necessary to deploy and support the solution.

2. Scope of Services

2.1 Emergency Detection and Escalation

The solution shall continuously monitor caller interactions for indicators of potential emergency situations and support immediate escalation workflows when emergency conditions are identified.

The solution shall:

i. Interrupt AI interaction upon detection of a potential emergency event

ii. Transfer callers directly to a live 911 telecommunicator without requiring the caller to redial, where technically feasible

iii. Allow callers to request transfer to a live operator at any point during the interaction

iv. Support configurable escalation rules, thresholds, workflows, and operational criteria

v. Operate solely on designated non-emergency and administrative lines and shall not replace or delay primary 911 operations

2.2 Integration with Existing Systems

The vendor shall provide a solution capable of integrating with the City’s existing public safety communications and operational systems, currently Motorola Vesta.

The solution shall:

i. Support integration with telephony and public safety communications infrastructure

ii. Support integration with CAD systems, where applicable

iii. Support real-time information sharing with telecommunicators and dispatch personnel

iv. Support operational workflows where traditional 911 location data may be unavailable or incomplete

v. Utilize scalable cloud-native or cloud-enabled architecture compatible with City operational environments

2.3 AI Functionality and Operational Performance

The vendor shall provide advanced AI-assisted non-emergency call handling capabilities designed for public safety operational environments.

The solution shall:

i. Support AI-assisted or automated handling of non-emergency calls

ii. Support conversational AI capable of dynamic caller interactions

iii. Provide real-time transcription, translation, and summarization capabilities

iv. Support intelligent call routing based on jurisdiction, call type, operational criteria, and configured workflows

i. Include AI safety controls, including hallucination mitigation and bias monitoring capabilities

ii. Demonstrate documented operational performance metrics, including diversion rates, escalation accuracy, and deployment outcomes from existing operational environments

2.4 Analytics and Reporting

The vendor shall provide configurable analytics, reporting, and operational monitoring capabilities.

The solution shall:

i. Provide real-time operational dashboards and reporting tools

ii. Support reporting related to call volumes, diversion rates, escalation events, wait times, and overall system performance

iii. Maintain audit logs and historical reporting capabilities

iv. Allow export of operational data and reports for internal analysis, compliance, and records management purposes

v. Support quality assurance and performance monitoring workflows

2.5 Administrative Functionality

The vendor shall provide administrative tools and controls that allow authorized agency personnel to independently manage operational configurations.

The solution shall:

i. Allow authorized personnel to modify call flows, prompts, routing logic, escalation criteria, and operational workflows without requiring vendor intervention

ii. Support role-based administrative access controls with configurable permissions

iii. Provide user-friendly administrative interfaces and configuration tools

iv. Support configurable workflows and operational scalability

v. Maintain change tracking and audit logging for administrative modifications

2.6 Implementation, Support, and Maintenance

The vendor shall provide all implementation, onboarding, training, maintenance, and support services necessary for successful deployment and ongoing operation of the solution.

The vendor shall:

i. Provide a detailed implementation and deployment plan

ii. Provide onboarding, configuration, testing, and training services

iii. Provide ongoing technical support, maintenance, updates, and system optimization services

iv. Demonstrate experience supporting public safety agencies, PSAPs, or similarly complex operational environments

v. Demonstrate the ability to support high call volumes, surge events, and operational continuity requirements

vi. Identify dedicated support resources, communication procedures, and escalation processes for operational or technical issues image1.png

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