Attachment C Technical Requirements

Type/print full legal name of bidder company

Instructions:

Bidders submitting a proposal must complete and submit Attachment C for evaluation purposes.

Technical Requirements: Bidder must respond to each requirement as noted in the instructions below.

Review Sections C1 to C3 and provide answers to the questions posed in sections C2 and C3.

Review Section C4 requirements and provide level of compliance with the requirement as follows:

Using the Bidder’s Compliance column, Bidder must respond either “Compliant” or “C” (2 points), “Partially Compliant” or “PC” (1 point) or “Non-compliant” or “NC” (0 points) to indicate the Bidder's ability to meet the requirement. In order to respond “Compliant” a Bidder must meet the requirement as written in its entirety and the associated functionality be available at the start of the contract.; “Partially Compliant” – a Bidder must provide a written explanation as to the exceptions to the requirement and any functionality that will not ready in the initial release, but will be provided in future releases (i.e., after contract start but before contract end) is permissible.

Section C1: Introduction The objective of this project is to establish a data exchange hub to connect and make interoperable the CAD systems of participating agencies. The project’s intent is that the CAD-to-CAD system enables participating agencies to increase operational efficiency, enhance regional situational awareness, and decrease response times.

This RFP seeks proposals from qualified firms to implement a fully functional vendor hosted CAD-to-CAD solution. The application should be flexible and scalable in design and architecture. The application should also pass information without logging the contents of the messages being exchanged; logging should be at the syslog level for troubleshooting and auditing only.

The awarded contractor will be responsible for the following project components including but not limited to:

1. Providing a system that meets the technical and functional specifications of this RFP.

2. Interfacing and implementing each of the participating entities’ CAD systems into the CAD-to-CAD system in a planned approach.

3. Complying with all requirements and proper protocol concerning the collection of CAD information as well as abiding by the Criminal Justice Information Services (CJIS), National Information Exchange Model (NIEM), and other applicable public safety information security and data requirements. Providing professional project management services including developing and executing a detailed project schedule, and the delivery of regularly scheduled status reports and identifying and managing project risks and issues.

4. Implementing a system utilizing standard information technology project phases to include:

a. System design

b. System installation and configuration

c. Integration and testing of the CAD interfaces

d. System acceptance testing to include performance and load testing for all PSAPs

e. End-user training

f. Go-live planning and migration

g. Post go-live system reliability and maintenance

h. Development and delivery of non-proprietary technical and operational documentation to be used for new user orientation and training

Section C2: Solution Architecture (50 points) A. Describe the proposed solution’s ability to automatically transfer associated incidents to appropriate agencies based on geography, agency, business process, and incident type. (5 points) Enter Response Below:

B. Describe the system administration tools that are used to manage the application including any data archival tools, tools for managing application updates, online help management tools, etc. (5 points)

C. Proposers shall provide network connectivity requirements including recommended bandwidth, latency, and throughput utilization to ensure optimal performance of the proposed solution. (5 points)

D. Provide the response times for the proposed solution in the column labeled “Solution Response Time”:

Processing time of data from: CAD A to CAD B (one to one transfer)

Processing time of data from: CAD A to CAD Many (one to many transfer)

(5 points)

E. Does the proposed solution utilize open APIs? (5 points)

F. Does the proposer provide API’s or other tools to build and support interfaces using utilities? (5 points)

G. Please indicate vendor’s preferred methodology utilized for third party interfaces. I.e., REST, .NET etc. (5 points)

H. Describe how the proposer’s solution complies with NENA’s ANSI-Approved Emergency Incident Data Object (EIDO) Standard (NENA-STA-021.1a EIDO JSON_20220419) that defines a standardized, industry-neutral format for exchanging emergency incident information between disparate manufacturer’s systems located within one or more public safety agencies. If the solution is not currently compliant, describe the proposer’s roadmap and timeline to support this standard. (5 points)

I. Describe how the proposer’s solution complies with NENA’s ANSI-Approved Conveyance of Emergency Incident Data Objects (EIDO) between Next Generation (NG9-1-1) Systems and Applications NENA-STA-024.1a-2023 that defines how EIDOs are conveyed between agencies. If the solution is not currently compliant, describe the proposer’s roadmap and timeline to support this standard. (5 points)

J. Identify any existing CAD systems (Vendor, model) for which the Bidder has already developed interfaces using the Bidders API. (5 points)

Section C3: Supplemental CAD-to-CAD Optional Offerings (20 points) The SECO and PSAPs seek to implement a system with initial functionality, but desire to have supplemental functionality as funding and participants grow. This supplemental functionality closely parallels the EIDO subscription and notification process described in the APCO and NENA standards.

Please describe the CAD-to-CAD system’s ability to support the following situations including any costs associated with the solution:

A. View only access of real time CAD-to-CAD incidents either across the region or with specific agencies and or non-Public Safety Agencies. (5 points)

B. The ability for an agency to receive real-time alerts and/or notifications if it has a CAD system that does not have the ability to support an API interface. (5 points)

C. The ability for a non-Public Safety agency to receive real time alerts or notifications if it does not have a CAD system. (5 points)

D. If an agency is in the middle of changing CAD vendors or conducting a major CAD upgrade and do not wish to create a bi-directional interface until its CAD project is complete. What are its options for CAD-to-CAD during this interim period? (5 points)

Notes: Washington State Patrol, Ambulance users, Department of Natural Resources, Washington Department of Transportation, and other dispatching centers need clearly defined ideas about what gets seen, by whom, (e.g. Public Utility District seeing CJIS info). System could dynamically change the shared view based on the changing type/nature of the incident or the types of units responding.

Section C4: Detailed System Requirements (252 points) Compliant = 2 points, Partially Compliant = 1 point, Non-Compliant = 0 points

(PC requires a written response) Bidder's Score

Capability 1: System will plot incidents on the map view with abbreviated description of the incident.

Capability 2: System will plot resources on the map view with abbreviated description of the resource.

Basic Data Set (Minimum)

While use of the NENA EIDO is the desired mechanism to exchange data, the following generic elements are required. Bidder should map to the equivalent EIDO element/description if EIDO is supported.

Mapping Data Set (Minimum)

While use of the NENA EIDO is the desired mechanism to exchange data, the following generic elements are required. Bidder should map to the equivalent EIDO element/description if EIDO is supported.

Based on agency/group/user permissions and filter settings, the CAD-to-CAD System GUI application shall be capable of showing the following real-time information:

1. Shared incident/calls (including assigned units, status, call comments/narrative based on opt-in by sharing agency)

2. Units (location based on AVL/GPS, availability, call assignment, status, pending requests)

3. Pending resource and capability requests associated with a shared incident that have not yet been granted or denied by the requested agency or CAD

4. Live map view, based on Esri map layers (or other commercially available mapping system) of all shared calls and units/vehicles; the map display must conform to the same filters and sharing limitations established in the agency/group/user settings

Return this attachment to Procurement Coordinator at:

contracts.office@mil.wa.gov