CAD-RMS RFI.docx

STATE OF NEVADA

DEPARTMENT OF PUBLIC SAFETY (DPS)

REQUEST FOR INFORMATION

Specifications, Instructions and Submitting Information for

Computer Aided Dispatch/Records Management System

November 12, 2021 5:00 p.m. PST

Nevada Department of Public Safety RFI: Computer Aided Dispatch/Records Management System Page 1 of 14 Table of Contents

2. Background 3

Client/Project Reference Form 14 1.

2. General Information

2.1 Introduction

The purpose of this Request for Information (RFI) is to allow interested vendors an opportunity to present information of available products and solutions that address the specifications within this RFI. The Nevada Department of Public Safety (DPS), Records Communication and Compliance Division (RCCD) (herein after referred to as “DPS”) is seeking information for identifying Computer Aided Dispatch/Records Management System (CAD/RMS) solutions.

The intent of this RFI is to elicit the advice and the best recommendations of knowledgeable persons in the vendor community. DPS does not intend nor is it allowed by Nevada Revised Statute to select a proposed solution or a vendor based on responses to this RFI. Subsequently, and depending upon knowledge gained from the response to this RFI, DPS may decide to prepare and issue a Request for Proposals (RFP) that will meet the requirements of its stakeholders. The collective information provided by vendors will be used to develop alternatives for consideration and to estimate costs and timeframes related to acquisition and implementation of a future solution. Vendors may respond to this RFI with information about deploying a CAD/RMS solution using the latest data governance practices and budgetary costs DPS should expect to incur when procuring, implementing, and supporting a solution.

2.2 Submission of Questions

Any questions raised must be emailed to mcosta@dps.state.nv.us and msabatini@dps.state.nv.us. Questions must be received by 3:00 p.m. PST, on October 4, 2021. If DPS chooses to respond to written questions, a written response will be returned to the requesting party by DPS on or before October 22, 2021. Only written questions will be considered.

2.3 Vendor Submissions

Vendor responses are due by 5:00 p.m. PST, November 12, 2021. Please include one (1) electronic copy of the RFI response submitted on a USB Flashdrive. If a vendor has multiple solutions, each solution must be submitted separately. Responses should be submitted addressed exactly as follows:

Melissa Costa Department of Public Safety Attn: RFI for Computer Aided Dispatch/Records Management System 333 West Nye Lane #100 Carson City, NV 89706

All responses to this RFI will be considered confidential.

2.4 RFI Schedule

Information submitted in response to this RFI will become the property of DPS. DPS will not pay for any information herein requested, nor will it be liable for any other costs incurred by any respondent related to the preparation or delivery of the response to this RFI or any subsequent presentation. Information submitted in response to this RFI will be treated as confidential.

DPS reserves the right to reject any responses to the RFI, in whole and in part, at any time. This RFI is designed to provide vendors with the information necessary for the preparation of informative response proposals and demonstrations of product. This RFI process is for DPS’s benefit and is intended to provide information to facilitate the potential future selection of goods and/or services. This RFI is not intended to be comprehensive and each vendor is responsible for determining all factors necessary for submission of comprehensive responses and complete product capability demonstration. The RFI response and demonstration will not be subject to an RFP type evaluation, but only to a review of suggested product performance, cost of processes offered, and abilities to perform services that may be of use to DPS. Cost shall be estimated by the vendor. When the estimated cost is submitted, the vendor shall state that it is an estimated or approximated cost.

DPS will not be responsible for any oral exchange or any other information or exchange that occurs outside the official process specified herein.

3. Background DPS is the premiere public safety agency and state police in Nevada and is committed to achieving the highest standards of excellence using comprehensive training programs, progressive technology, federal, state, and local government partnerships with interagency cooperation to ensure the safety of all citizens and visitors in Nevada.

DPS, local law enforcement, emergency management, and criminal justice associated partners use the Spillman FLEX suite (hereinafter SPILLMAN) of products to communicate and exchange information throughout the state of Nevada. SPILLMAN tools have been in use since 2010. SPILLMAN Technologies was acquired by, and has operated as a subsidiary of, Motorola Solutions since 2016 and will be herein after referred to as Motorola.

This RFI is being released in accordance with State statute and procurement policies to determine the feasibility of replacing the SPILLMAN suite of products and the maintenance services and support provided by Motorola.

4. Specifications and Requirements This section is intended to provide a high-level overview of the features, functions, and infrastructure of the SPILLMAN products in use. This overview is not intended to be a comprehensive set of requirements, but it is intended to give knowledgeable parties an idea of what DPS is seeking should it decide to pursue a solution through a comprehensive RFP.

3.1 Users

There are over forty (40) State and local law enforcement agencies using various modules in the SPILLMAN suite of products to communicate with each other. SPILLMAN has a permission based set up – by default, users have no access to data in SPILLMAN until assigned permission groups. Permission groups are built based on job function and are assigned on an as-needed basis. All new users that have access to criminal justice information (CJI) are vetted prior to access being granted through their respective agencies.

The agencies listed below are identified as users on the Motorola contract. These agencies represent over 2,000 active users SPILLMAN.

3.2 System

The below list represents all the active SPILLMAN modules in the contract between DPS and Motorola. Not all the modules are used by DPS. This RFI is intended to identify solutions for only those modules in use by DPS. Vendor shall identify in their submittal if modules not used by DPS are included, at no additional cost to DPS, in the solution being proposed.

3.3 Interfaces and Data Exchanges

SPILLMAN interfaces and/or exchanges information with external systems and third-party applications throughout the state. The table below identifies the known interfaces with external systems and third-party applications.

3.4 Infrastructure

SPILLMAN is hosted on premise in Nevada Enterprise IT Services (EITS) facilities located in Carson City, NV (primary), and Las Vegas, NV, which serves as the disaster recovery site. Servers are provisioned by DPS and supported by Motorola partner Solutions II. EITS provides rack space, power, and connections to the state network.

3.5 Security

SPILLMAN maintains compliance with the most current version of the U.S. Department of Justice, Federal Bureau of Investigation, Criminal Justice Information Services Division, Criminal Justice Information Services (CJIS) Security Policy (at the time of RFI release, the current version is Version 5.9, 06/01/2020, CJIS-ITS-DOC-08140-5.9).

SPILLMAN maintains compliance with State of Nevada, State Information Security Policies, Standards, and Procedures:

(https://it.nv.gov/Governance/Security/State_Security_Policies_Standards___Procedures/

3.6 Operations, Maintenance, and Support

Motorola, with its partner Solutions II, is the sole operator of the SPILLMAN system and its component modules. They provide maintenance and support including:

1. Scheduled and as-needed maintenance on hardware and software (all modules and interfaces) hosted in the EITS facilities.

2. Software updates, releases, and enhancements as they become available and are successfully tested.

3. 24-7-365 technical support.

4. Provide and maintain anti-virus/anti-malware software on all hardware and software associated with SPILLMAN in compliance with CJIS Security Policy and State of Nevada, State Information Security Policies, Standards, and Procedures.

5. Vulnerability scanning in compliance with CJIS Security Policy State of Nevada, State Information Security Policies, Standards, and Procedures.

6. Provide and maintain scheduled backups.

7. Maintain a disaster recovery (DR) plan.

8. Ensure system will operate on the most current Windows operating systems and future releases when they become available.

9. Provide annual certification training for Application Administrators.

10. Provide initial and on-going training for all users.

11. Provide an on-site Administrator.

12. Exit and transition planning and management.

3.7 Business Needs

As indicated in Section 1.8, this RFI is not intended to be comprehensive. The list in the table below is not intended to be all inclusive, but to provide knowledgeable vendors an opportunity to describe how their proposed solutions may meet some of DPS’s business needs.

Description

3.8 Terms/Acronyms and Definitions

5. Vendor Responses

5.1 Section 1 – Executive Summary

Vendors shall provide an executive summary written in non-technical language to summarize the overall capacity and recommended approaches for a CAD/RMS.

5.2 Section 2 – Implementation Approach

This section should describe recommended implementation strategies for the CAD/RMS solution including a recommended rollout strategy and potential project plan indicating timeframes for phases as well as the entire project. A suggested resource matrix should be included with defined roles for potential project participants. This will help DPS determine project member needs and availability of project resources.

5.3 Section 3 – Proposed Solution

Vendors should provide detailed information on their proposed solution(s). The information should include recommendations taking into consideration DPS’s initially documented business needs – found in Section 3.7.

5.4 Section 4 – Concept of Operations

Describe how the solution would satisfy DPS’s CAD/RMS needs based on background information, and any recommended implementation strategies.

5.5 Section 5 – Cost

While this RFI will not result in an award, DPS needs cost estimates to proceed with an RFP if it so chooses. DPS asks vendors to respond with typical costs for similar implementations. If the proposed solutions are modular in nature, DPS asks vendors to respond with costs for each module offered. Cost estimates should include other implementation, maintenance and support costs (e.g., hardware, application software licenses, third-party licenses, system maintenance).

5.6 Section 6 – Past Performance

Provide a list of agencies that have implemented the solution and three (3) client references. The descriptions should include current references in the user organizations and sufficient information for DPS to understand the vendor’s capabilities and experience in designing, configuring, and implementing a CAD/RMS solution. Vendors shall submit the client references using the form on page 14 of this RFI.

5.7 Section 7 – Vendor Questions

5.7.1 Technology Model - Describe your licensing model: Site license with maintenance, SaaS, both, or Other (please describe)?

5.7.2 Hardware Environment - Describe the supported computer hardware environment in which the proposed software will run (e.g., Cloud, on-premise). In the event there are multiple computer systems available? Please list all options.

5.7.3 Operating System – Identify the operating system that is supported by the proposed applications software and the proposed database management system in the hardware environment recommended above. In the event there are multiple operating systems available, list all options (e.g., Linux, Windows).

5.7.4 Database Software – Describe the database in use. Provide a description of the Relational Database Management System (RDMS) required to support the computing environment.

5.7.5 Middleware Software – Please list any middleware your system requires (e.g., Web Methods, JBoss, WebLogic)

5.7.6 Third Party Software – Please list all third-party software required to use your system (e.g., Crystal Reports).

5.7.7 User Interface(s) – What browsers and browser versions are supported by your system?

5.7.8 Information Sharing and Integration Capabilities - Explain considerations for sharing information, receiving information, or the continuation of information sharing with other agencies or information exchanges. Describe your system’s flexibility and ability to support future information sharing needs using industry standards.

RFI: Computer Aided Dispatch/Records Management System

SUBMITTING VENDOR:

Client Name:

Project Name:

Name:

Name:

Street Address:

Street Address:

City:

City:

State:

State:

Zip:

Zip:

Phone:

Phone:

Email address:

Email address:

Fax:

Fax:

Description of Project:

Brief description of project/contract:

Project/contract start date:

Project/contract end date:

Length of project/contract:

Project/contract value:

Size and complexity of the project/contract:

Application software (i.e., Java, .NET)

Operating System Software (i.e., UNIX, MS)

Hardware Platform (i.e., IBM RISC 6000)

DBMS and Size of Database:

Other Details: (optional)

Nevada Department of Public Safety RFI: Computer Aided Dispatch/Records Management System Page 2 of 15 image1.png